1. Experiences with EP 5.0 Lessons Learned

2. Johnson & Johnson - J&J Consumer - Neutrogena - ROC - McNeil Consumer Healthcare Co. - McNeil Specialty - Ethicon - Ethicon Endo Surgery - Ortho-Clinical Diagnostics - Janssen Pharmaceutica - Janssen-Cilag - Ortho-McNeil Pharmaceuticals - Ortho Biotech - Centocor - Alza - J&J PRD

3. J&J PRD Global Operating Model

4. A Pharmaceutical Drug Approved Today… Costs $800 million over 10+ years to discover and develop, and Is projected to generate $500 to $700 million in peak year sales Preclinical  Toxicology  Screening Phase I  First human dose  Drug safety Phase II  First patient dose  Efficacy with dose-ranging  Safety Phase III  First pivotal dosing and efficacy Reg  Submission Drug Evaluation Full Development Line Extensions  New Indications  New Formulations Discovery

5. Business Case – SAP Portal Hard Benefits –Reduced Infrastructure Costs –Fewer Helpdesk / Security resource needs –SAP Portal provided built in integration to SAP R/3 & BW Soft Benefits –Single point of access –Platform for enhanced usability Combine content & functionality Simplify transactions Better end-user experience –Single Sign On –Portal will help user acceptance; speed realization of benefits from other J&JPRD software implementations –Powerful communication tool

6. Project Scope Role Based Accessibility Usability Application Integration Security Globalization Compliance Beacon Portal Branding

7. Strategic Portal Approach Internet J&J Intranet BW / SEM Ariba SAP R/3 J&J Web Apps Beacon Portal

8. Challenges Lack of Desired Functionality –Unifiers –Role Migration –PLM package –Composite roles in iPanel –ITS functionality Balancing portal modifications Chasing a Moving target –EP 5.0 SP?? –Unifiers –Hot fixes vs. patches Defining system architecture –LDAP selection –High availability

9. Challenges (cont.) Dealing with GUI trained users –Losing functionality perception Cutting edge technology –Need to make “gut” decisions –Can’t follow standard SAP methodologies Requirement gathering from key users –Overwhelmed feeling

10. Lessons Learned Best approach is not always the latest & greatest –Architecture, patches, etc… Technical landscape needs to mirror production –Flush out hidden problems Importance of Promote to Production –Managing development –Managing software changes Functionality is more important that technology Strong project management required –Detail oriented –Scope creep is common

11. Lessons Learned (cont.) Defining governance model –User / role maintenance –Content publishing Quick wins are great to have –Leverage existing content –Personalization options –User Mapping for low budget Single Sign On WebEx is a life-saver –SAP troubleshooting / OSS messages –End User Support –Training Need monitoring / tracking data

12. Recommendations Identify stakeholders early Define & lock down scope early Proper resource selection –Use SAP consultant on your team –SAP savvy, Java, ASP, general NT, ITS Multi-generation approach for roll out (baby steps) –Less can be more –SAP Portal is not an R/3 implementation Include “sticky” applications to attract users Determine versions & go with it

13. Recommendations (cont.) Do not underestimate role mapping process Watch out for small “gotchas” –Proxy settings, save as favorite, outlook access, languages –Field testing important / pilot studies Don’t let software limitations limit you –Centralized admin privileges Remember your business case –Don’t get lost in the technology –Usability

14. Final Thoughts Portal technology is a platform to fix your current issues

15. Thank you for attending! Please remember to complete and return your evaluation form following this session. Session Code: 704