Embed Size (px)
Citation preview
Driving Business Agility at Pfizer Driving Business Agility at Pfizer
Martin BrodbeckMartin Brodbeck
Application Architecture Director
Pfizer Global Pharmaceuticals
June 7, 2004
AgendaAgenda
Pfizer Overview
Enterprise Architecture & SOA
Steps to Success
Use Case: Approvals Pathway
Pfizer OverviewPfizer Overview
#1 pharmaceutical company in every major market around the world
Combined Revenue in 2003 was $45 Billion
Our portfolio includes 14 number one medicines across several major therapeutic categories
We invest over $20 million every business day in discovering and developing new medicines
Business EnvironmentBusiness Environment
• Growing amount of information
• Number of products increasing
• Transactions and Information are distributed across a complex web of applications and networks
• Relationships becoming more varied and dynamic
Products Core Business Processes
CustomerRelationships
• Evolving regulatory and legal requirements
• Increasing privacy concerns
Security
Business DriversBusiness Drivers
Take advantage of our scale
Visibility into product performance and sales across markets and therapeutic areas
Creation of standard product views across business areas and functions
Flexibility to change criteria for reporting and analysis based on changes within business environment
Integrated Business ApproachIntegrated Business Approach
Common View of Product Performance
Integration of Business Processes
Across Applications
Products CustomersBusiness Processes
Security
Common View of Customers
Identity and Access Management
Pfizer Global Pharmaceuticals
Architecture as a Key EnablerArchitecture as a Key Enabler
Real time access and visibility of information across applications and databases– Information lives in different applications and databases across the
enterprise– No authoritative source for product performance and information– High level of complexity and cost for integrating disparate data
sources
Agility through de-coupling of business functionality and processes from underlying technologies
Integration across business groups, functions and processes
Common governance and management model
PGP’s Enterprise Architecture = SOAPGP’s Enterprise Architecture = SOA
Phase I Phase II Phase IIIn = 10 - 30 n = 20 - 200 n = 500 - 10,000
DevelopmentDiscovery
CH3
C1
R1-10
CH3
C1
R4
DiscoveryResearch Team
Many Compounds
In vitro & in vivo Screening
Drug Candidate Selection
Scale Up & Animal Tox
File IND
++ Regulatory Regulatory
Approval Approval and Launch!and Launch!
Regulatory ReviewRegulatory ReviewRegulatory ReviewRegulatory ReviewPhase IV
File NDA
Commercialization
SOA is our Enterprise Architecture
Global-scale opportunity
Business Process and Information Integration– Not on a bus– Not in an app server– Not in a packaged app– Lives within and between all of these systems
Enables horizontal application development
SOA calls for a Paradigm Reversal:SOA calls for a Paradigm Reversal:
Business drives the technologyBusiness drives the technology
Accidental ArchitectureAccidental Architecture
Silos of information and Pockets of integration Tightly-bound relationships; no flexibilityDifficult or impossible to monitor and troubleshootComplexity of inter-organizational collaboration
Rigid, Costly and Difficult to Operate
Leverage XMLLeverage XML
Wraps fixed formats
Makes files self-describing
Can be extended without breaking
Universally understood
Normalize Data Representation Between Applications
SOA Infrastructure is RequiredSOA Infrastructure is Required
Reliable communications backboneService-oriented architecture (SOA)Intelligent routingXML transformationConfiguration-driven
Reliably Connect and Coordinate Interaction of Services
PGP’s Enterprise SOA FabricPGP’s Enterprise SOA Fabric
ApprovalsPortal
Sales ForceApplication
ManagementDashboard
Auditing
Data
Approval
SLA
Customer
Product
PolicyEnforcement
Routing
Shared Business Services
Service-basedApplications
Shared Infrastructure Services
Evolution of SOA ArchitectureEvolution of SOA Architecture
Portals
Application ServersEAI
Databases ERP Systems
Today Tomorrow
SmartClients
Service-OrientedProcess
Orchestration
Web Services
Front End
Middle Tier
Back End
SOA Guiding PrinciplesSOA Guiding Principles
Service orientation is a first-order principal– Loosely coupled – Shared services – Federated – Standards-based
Scale is Critical– Horizontal scale– Global
SOA = Independence– Language, programming model, platform, tooling– Implementation – Vendor – Inclusive, not exclusive
PGP’s Pragmatic AdoptionPGP’s Pragmatic Adoption
Today’s project success…
– High impact, strategic use cases – Process-centric applications– Reusable services for portals & dashboards
…tomorrow’s architectural change
– Enterprise-wide sharing and reuse– Semantic integration – Federated business processes – Service-oriented mobility
Steps to SuccessSteps to Success
Business
1. Drive dialogue around the business process
2. Get the governance right
3. Drive strategic use cases
4. Push collaboration with trusted advisors
Steps to SuccessSteps to Success
Technical
1. Connect business to technical architecture
2. Invest in technology-independent SOA infrastructure
3. Show me your WSDLs
4. Good Enough
Technical use case:Technical use case:
PGP’s Approvals PathwayPGP’s Approvals Pathway
Approvals Pathway: BackgroundApprovals Pathway: Background
Centralize approvals functionality from multiple source applications available to audiences via the web– Expense reports– Project invoices– Travel requests– Requisitions
A unified user interface acting as a “dashboard” into source applications– Provide just the right amount of information for users to perform
common tasks– Hide the complexity of source applications– Provide easy access to additional information
Web services for applications with approvals functions: bring products from multiple vendors and software manufacturers onto the same platform
Approvals Pathway – Technology StackApprovals Pathway – Technology Stack
Approvals PathwayApprovals Pathway
Results
Saves time for managers & executives
Approvals done faster across multiple systems
SOA Infrastructure encourages scalability to more systems & more users
SOA Infrastructure means projects take less than half the time to complete
Next steps: stepping on the accelerator
From 3 20+ backend systems
From 2 to 5+ consuming applications
Extend Approvals Pathway to mobile users
Questions?Questions?
