140 likes | 648 Views
Johnson and Johnson OneSource 2.0. Scott Jaworski IM Manager/Project Manager. Johnson and Johnson Background.
E N D
Johnson and Johnson OneSource 2.0 Scott Jaworski IM Manager/Project Manager
Johnson and Johnson Background • Johnson & Johnson, through its operating companies, is the world's most comprehensive and broadly based manufacturer of health care products, as well as a provider of related services, for the consumer, pharmaceutical, and medical devices and diagnostics markets. • The more than 200 Johnson & Johnson operating companies employ approximately 113,800 men and women in 57 countries and sell products throughout the world.
PSGA Background • Our Vision • To Provide Competitive Advantage for Johnson & Johnson by Becoming the Industry Leader in Supply Chain Excellence • Our Mission • We will anticipate and meet critical customer needs and fuel business growth by simultaneously: • Ensuring that the quality of our products and the operation of our facilities are in full compliance with all regulatory requirements. • Continuously reducing unit cost and optimizing capital utilization. • Operating a flexible and responsive manufacturing organization and Supply Chain network with highly skilled and motivated people. • Rapidly launching new products / technologies and integrating new company acquisitions to secure and shape our future supply chain environment.
Scott Jaworski Background • Johnson & Johnson Operating Companies • Janssen Pharma • Project Lead for the MARKUS application • J&J Gateway • Project Lead for customized web content authoring application • PSGA • IM Manager/Project Manager for OneSource document management application • Been involved with Documentum for over 6 years
OneSource Functions • Manage Controlled Documentation • Change Request and Documents (SOPs, BOM, Specs, tech docs) • Document Lifecycle • Workflow • Route for review • Route for approval • eSigs • Reports (business metrics) • Delegation & Inbox Reassign • Approximately 1,500 users across 6 sites (3 in NJ, 3 in PR) • Plans to significantly increase user base • PSGA West Project in 2006 • Beyond Puerto Rico and US • Current technologies: DCM, Rightsite, v 4.2.8
OneSource Background • OneSource 1.0 Originally Released in 2003 • Based on DCM • Extensive Customizations by Glemser to DCM Components • Every piece of code was customized, over 70% of the application • OneSource 1.1 Released in January 2005 • Enhancements to 1.0 code base, release because OS 2.0 was delayed • Added InfoPath to support Creation of Change Requests • InfoPath used to add more flexibility to the form (XML editor vs. Word Template)
Why we are upgrading to OneSource 2.0 • Plans for Expansion • Packet Routing (Multi-Documents – Routing a CR and Documents together) • Wanted a more “configurable” approach • Other additions based on new platform • Performance, Performance, Performance • OneSource currently on unsupported Documentum platform • DCM • RightSite/Significant Performance Problems • Difficult to Support Technical Implementation • Database Calls • Custom code • Rightsite • Loss of Resources (J&J and Glemser)
OS 2.0 Project Timeline • Project Starts May 2004 • Initial Review of DCM and Upgrade June 2004 • Prototype from Glemser and Implementation scheduled • Project gets delayed because of DCM 5.2.5 delay • OneSource 1.1 is released Jan 05 • OS 2.0 work is resumed Mar 05 • Scott Jaworski enters Project April 2005 • Decision to not utilize DCM April, 2005 • Too much customization, plus latest version of documentum is available • Decision by Glemser not to be involved April, 2005 • The ‘letter’ • Revised Approach and Work plan • TSG/Active Wizard • Project is back on track with new dates but is able to stay on budget
Why not DCM? • Number of Customizations didn’t make cost attractive • Increased productivity of End Users • Increased performance (searching) • Better web navigation with 5.3 WebTop • More configurable interface • Business agility • Reduced system complexity • Reduced skill set requirement for support • Easier to enhance • Upgradeable • Simpler upgrade path, no need to consider DCM releases • Historically, new releases of WebTop available at same time as the core product.
Why we are upgrading to 2.0 • While we are still customizing… • Project Philosophy • Customize in order to make configurable!
System Components • Webtop 5.3 SP1 (when it comes out mid September) • Wanted to be on the latest version • Wanted to be able to maintain customizations • Components of System • PDF Aqua – controlled printing • Annodoc – annotating documents • Liquent RenderPerfect/ARP • TSG Active Wizard • Form, Routing and Workflow Approval Components • Launched from Webtop – Version Neutral (Supports 5.1, 5.2.5, 5.3, 6.x?) • Dynamic Form – old version was static pages – difficult to change and maintain • Dynamic Workflow – old version was template rather than user driven • Approval Interface – form approval interface
Timeline • Project is on schedule for deliver - Dec. 18th 2005
Questions? Thank You, Scott Jaworski Johnson & Johnson Sjawors2@psgus.jnj.com Thanks to our technology partners TSG and CYA