case study in implementing a global transparency ... · case study in implementing a global...
TRANSCRIPT
Disclosure Summit
Case Study in Implementing a GlobalCase Study in Implementing a GlobalCase Study in Implementing a GlobalCase Study in Implementing a Global
Transparency Transparency Transparency Transparency Solution Solution Solution Solution –––– BI Steps to SuccessBI Steps to SuccessBI Steps to SuccessBI Steps to Success
7 February, 2014
Step 1: Streamline Cross-Border Engagements of HCPs
HCP Engagement June 2013 2
The ChallengeThe ChallengeThe ChallengeThe Challenge
• Increasing country-specific legislation
and Code of Conduct
• Legislation and codes include cross-
border reporting
• BI recognized the need for revised
internal policies / processes
ApproachApproachApproachApproach
• Performed a global assessment of the
current cross-border engagement
landscape
• Developed a Global Corporate Policy
and Process
• Developed and deliver comprehensive
training sessions
BenefitsBenefitsBenefitsBenefits
• Quantified volume and size of cross-
border transactions
• Approved new corporate policy and
procedure
• Implemented a short-term solution
• Initiated an RFI for long-term
technology solution
Fully DistributedFully DistributedFully DistributedFully Distributed SemiSemiSemiSemi----DistributedDistributedDistributedDistributed Single InstanceSingle InstanceSingle InstanceSingle Instance
• Unique codebase / database per country
• Shared CM / SAP
• Unique front end for each country
• Shared code / database / CM / SAP
• Unified front end for all countries
• Shared code / database / CM / SAP
Key benefitsKey benefitsKey benefitsKey benefits
• Fully customized for each country (fields, workflows,
etc.)
• Minimal systems interdependence
• Supports country-specific roll-outs
• Uniform processes / reporting capabilities while
maintaining unique “look and feel”
• Supports country-specific roll-outs
• Lower cost to implement and maintain than “fully
distributed”
• Uniform processes / reporting capabilities
• Satisfies basic language requirements and easily
supports future translation needs
• Least costly option to implement and maintain
What to What to What to What to
considerconsiderconsiderconsider
• Potential for disparate processes / reporting
capabilities
• Increased time / cost for implementation and
maintenance
• Consensus required on data-capture and process
elements
• Future customizations and system updates affect all
countries
• May not achieve “ultimate” end-user experience
• Consensus required on data-capture and process
elements
For ea
Step 2: Sample Global Models to Consider
DB DB DBDB
DB
Default language with scroll-over
translations
DB
Agg Spend ERPCM Agg Spend ERPCM Agg Spend ERPCM
Global Governance – 80/20 Standardization
Process and Technology Standardized across GlobeProcess and Technology Standardized across GlobeProcess and Technology Standardized across GlobeProcess and Technology Standardized across Globe
COECOECOECOE
Key Challenges for BI
1. Global buy-in, especially in regions without existing/pending transparency drivers
2. Terminology / Taxonomy Harmonization
3. Identification of Global Business Owners
4. Identification of Owner(s) of Spend Overlapping Regions
5. Process Integration
6. System integration, including:
• Data standardization
• Harmonization (ERP, CRM, CTMS, 3rd Party Reporting, etc.)
• MDM / Customer Master
• Data Storage (Privacy concerns)
Step 3: Expand HCP Platform
Deployment Strategies Deployment Strategies Deployment Strategies Deployment Strategies ---- Better PracticesBetter PracticesBetter PracticesBetter Practices
• Expand platform into countries with greatest Compliance riskExpand platform into countries with greatest Compliance riskExpand platform into countries with greatest Compliance riskExpand platform into countries with greatest Compliance risk
• US
• UK
• Add’l. expansion within Germany
• Leverage Fixed Duration Pilot or Proof of ConceptLeverage Fixed Duration Pilot or Proof of ConceptLeverage Fixed Duration Pilot or Proof of ConceptLeverage Fixed Duration Pilot or Proof of Concept
• Single region, all (or most) transaction types
• Single transaction type, all (or most) regions
• Expedited SDLC
• Key stakeholders engaged
• Rapid prototyping
• Requirements Tend to Change During Long Projects AnywayRequirements Tend to Change During Long Projects AnywayRequirements Tend to Change During Long Projects AnywayRequirements Tend to Change During Long Projects Anyway
• Consider CrossConsider CrossConsider CrossConsider Cross----Border and Other Global Groups FirstBorder and Other Global Groups FirstBorder and Other Global Groups FirstBorder and Other Global Groups First
• Consider Foundational Technology (MDM, ERP, CRM, etc.)Consider Foundational Technology (MDM, ERP, CRM, etc.)Consider Foundational Technology (MDM, ERP, CRM, etc.)Consider Foundational Technology (MDM, ERP, CRM, etc.)
David J. EibenDavid J. EibenDavid J. EibenDavid J. Eiben
Director, IS Business Partnering