XRPM PPM 4.0 upgrade at Eli Lilly

1. xRPM (PPM) 4.0 upgrade at Eli Lilly  Dr. Christian Wolf, Eli Lilly and Company Raj Una, GyanSys Inc.

2. Learning Points What is the business case for upgrading xRPM ? What are the enhancements in functionality? How does the migration from 2.0 to 4.0 work ? What is the effort required ? What are lessons learned ?

3. Eli Lilly and Company Leading pharmaceutical company Net sales 2006 about $ 15.7 billion A heritage more than 130 years strong Products marketed in 143 countries More than 41,000 employees worldwide Approx. 8,200 employees in R & D Headquartered in Indianapolis, IN

4. Eli Lilly and Company - Products Byetta®, a first in a new class of medicines known as incretin mimetics to treat type 2 diabetes Cialis®, a distinctive new treatment for erectile dysfunction Zyprexa®, breakthrough product for schizophrenia and acute mania associated with bipolar disorder Cymbalta®, for major depressive disorder and diabetic peripheral neuropathic pain Gemzar®, for the treatment of pancreatic and non-small-cell lung cancer Evista®, the first in a new class of drugs to be used for the prevention and treatment of postmenopausal osteoporosis Prozac®, which revolutionized the treatment of depression Humulin®, human insulin, the first human-health-care product created by biotechnology

6. xRPM 2.0 system Landscape

7. Drivers for Upgrade Technical Consolidate to Enterprise Portal 7.0 between R/3 and xRPM Consolidate to common BI version of 3.X between R/3 and xRPM Eliminate separate BI server SAP stopped support of xRPM 2.0 as of Dec 2006 Business Multiple Lilly enhancement requests were realized with 4.0 Heavy customization of xRPM 2.0 can be replaced by standard 4.0 system - e.g. custom fields for financial planning

8. Path to Upgrade May 2004: Live with 100 users on xRPM 2.0 Aug 2006: Start of xRPM Upgrade project planning Nov 2006: Install of 4.0 in Development environment Apr 2007: Migration and Final Integration test May 2007: Planned Go-Live for xRPM 4.0 with 350 users

9. xRPM 4.0 System landscape

11. SAP Functionality Improvements(of which currently in scope at Lilly) Multiple Portfolios Bucket hierarchy (flexible without limitation) Portfolio Items (Proposal, Projects) Option for automatic creation of cProjects Decision Points Item Status What If Review Snapshot Collections Dashboards (Portfolio, Item, My Review, My Collection etc..) Task Upload Financial and Capacity Planning by Category Groups and Views

12. Custom Functionality Enhancements Automatic internal number generation for Portfolio Items Custom Fields at Portfolio Items, Financial and Capacity Group Custom search help Sponsor Collections by Bucket (Planned) Item Custom Fields (Planned) Custom Tool for Financial and Capacity data Update Create / Change / Delete Download to Excel File Upload the data from Excel File Online vs. Background Option Test Mode vs. Update Mode

13. Migration steps Technical upgrade Configure system for new objects Item type, portfolio type, decision points,… Run migration programs Migration of 2.0 configuration tables (location, unit of measure,….) Bucket migration Portfolio Item migration and item attachment migration Objects migrated via migration programs Configuration Project Category and Sub-Category to Bucket Hierarchy Projects to Portfolio Items Custom Fields, Comments, Execution and Approval Status Project Stakeholders to ACL (Access control list) Documents attached to projects

14. Migration – special considerations Migration can be revoked and then repeated Old 2.0 data remains stored in tables BW data fully reloaded post migration Lilly custom changes to migration Delete and update ACL after bucket migration Update bucket settings after bucket migration Move some item standard fields to custom fields after migration

15. BW Analytics – new 4.0 features Majority of reports are created in Bex Analyzer and published in Portal iViews More delivered business content (Cubes, ODS & Queries) Easily exportable to Excel Extended SAP delivered cubes with custom fields instead of custom cubes / ODS Portal Publishing is different and does not require Web Application Designer Delta load is more robust and faster than full load Role based menu is no longer supported

16. Portal and Security – new features Navigational and Dashboard configuration Cache Administration to synch-up the backend configuration ACL access – Admin/Change/Read/Display/None Role Group / Business partner assignment Portal Roles WorkSet -> Page -> iViews

17. Resources utilized for project Lilly: 1 Project manager 2 Power users (part-time) Steering committee 3rd party consulting (4 to 6 months) 1.5 xRPM Configuration Analysts 1 ABAP Consultant 1 BW consultant Heavy leveraging of Basis, Enterprise Portal, Security and Documentation/Validation resources Adherence to Implementation Methodology of Lilly’s SAP project

18. Collaboration with SAP Labs Lilly is first customer to migrate from 2.0 to 4.0 Regular consultation with SAP’s xRPM product team Prompt responses from SAP on OSS messages Lilly Influence on 4.0 development Communicated functionality Gaps in 2.0 Unit testing on 4.0 beta client in Palo Alto Financial and Capacity Planning Usability feedback (mass data entry)

19. Short-term possibilities post go-live Switch to standard interface to load HR employee masters MS Project Server Upload/Download Workflow for project stages What-if Scenarios Resource management by employee BI 7.0 front end Web Analyzer for ad-hoc reporting Exception reporting, Alerts and Information Broadcasting

20. Long-term possibilities Integration with R/3 CO/PS for planned & actual costs cProjects for IT projects cProjects, PPM for R&D projects Scoring models / questionnaires for investment selection Monetary and non-monetary value assessment

21. Benefits Achieved Better communication with customers Alignment of portfolio with corporate objectives Visibility across entire IT project portfolio Operational excellence among project managers (e.g. Stage-Gate Methodology) Faster response to changing priorities

22. Key Learnings Need at least two test cycles for migration using production data Can’t assume that migration tools work if you are the 1st customer to use Migration of master projects from 2.0 to 4.0 not compatible with 4.5 design Hard to find xRPM consultants in the marketplace

23. 3811