Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

(ATS6-APP05) Deploying Contur ELN to large organizations


Published on

Introducing new IT systems that affect many users could be challenging, in particular for large organizations. This session will describe how Contur ELN has been deployed to 1000+ users in different fields of R&D. Case studies will be used to illustrate strategies and practical considerations.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

(ATS6-APP05) Deploying Contur ELN to large organizations

  1. 1. (ATS6-APP05) Deploying Contur ELNto Large OrganizationsMats KihlénDirector R&D and Pre-salesStockholm,
  2. 2. The information on the roadmap and future software development efforts areintended to outline general product direction and should not be relied on in makinga purchasing decision.
  3. 3. Content• The role of ELNs• On premise vs. Cloud• Large organization challenges• Standardization and system evolution• Deployment process• Case study
  4. 4. • ELN is only one of several Research Informatics systems– No consensus vocabulary in RI (e.g. ”LIMS”, ”Data warehouse” have differentmeanings)– Expectations will differ also within the organization• Possible expectations– System for mining of assay data– Repository of raw data– Logistics – request samples for analysis– Notebook for experimental observationsWhat role should ELN have?Don’t let ELN represent all good thingsyou don’t have yet
  5. 5. • Improve documentation quality– Readable experiments!– Make sure everything is captured– Prove inventive steps for future patenting• Facilitate project work– Easy overview of all activities– Improve communication and avoid extra reporting• Enable data sharing– Avoid repeating experiments– Less time chasing necessary information from others• Provide easier data capturing– Copy and paste from instruments and applications– Save time and frustration for the scientistsWhy an Electronic Lab Notebook?
  6. 6. Quick Demo
  7. 7. On premise vs. Cloud ELN• Large customers all use on premise systems– The Cloud is used by small biotechs and academic groups• Using Cloud as a collaboration platform looks very promising– Easy to add collaboration partners - no Central IT involvement needed– Full access to CRO data, compliance monitoring– Data may be imported into the central system at any time using theAPI, also into non-Accelrys systems
  8. 8. Large organization challenges• Wide variety of disciplines– Requirements from discovery to regulated• Large number of different workflows– Legacy systems– Different business units– System/vendor dependencies• Incomplete or conflicting roadmaps– Mixed expectations and opinions• Lack of global metadata– Projects, systems, entities ...– Hard to agree on standards
  9. 9. Consequences• No Big Bang– Gradual deployment - let the organization mature– Instrument and workflow specifics should be handled separate from the core ELNproject– Different ”must haves” before and after deployment• Apply ”80 – 20 rule”– Satisfy 80% of the users first– Don’t let the needs of the 20% jeopardize the entire project
  10. 10. Possible high level architectureELN – common to all scientistsMaster Data Management –common identifiers for key objectsAccelrys Enterprise Platform – datatransformation and connectionsPLMSystem IIIVarious data systemsLocal standardsConnected via PLM/MDM/AEPSystem IVSystem I System II...
  11. 11. Deployment process• Proof of Concept– Real system – no sandbox– 20-50 users for 2-3 months– Corporate IT on board– Outline access model and configuration• Expanded pilot– Involve more business units– Build internal organization (SOPs, support, training, records management etc)– Finalize access model and configuration– Appr. 300 users• Full roll-out– 1000+ users– Production mode– Corporate servers and IT support
  12. 12. Case Study - Background• ELN is part of a Global Digital Initiative• Leadership team graded ELN as largest productivity gain from acorporate function perspective• Already invested in PLM and been searching for a light notebookfor some time – but not found much...
  13. 13. Case Study - Requirements• Any solution must scale to 4-5000 users• Seeking a solution which is easy to use, yet possible to validate• Strong legal and QA requirements• Previous attempts not endorsed by end users and managers– Failed in-house development project of an ELN based onSharePoint
  14. 14. Case Study - Contur ELN pilot implementationDec•Demo•WebEx for Core team on Dec 2Jan•Cloud trial•3 weeks for Core Team, starting on Dec 15Feb•Pilot Project PlanningMar•Decision 220 user pilot, contract signedApr•Implementation•LDAP integration, access model, validation scripts etcMay•Validation and Vendor auditJun•Pilot launch•On-site + WebEx user training7 months(Initiationto Go Live)220 users across 5 sites running ELNUsability verifiedScalability verifiedTurning pointUsers go live
  15. 15. Case Study - User comments“Its very useful for me. It is the first time in 1.5 years in thecompany that I have an updated LNB. It is very simple toadd all the information about the products, the instrumentsused, to add Excel Worksheet. I dont want to go back forthe paper LNB.”“Best ELN tool I have seen (and I’ve seen almost all).”“After using ELN I will NEVER go back to the paper LNBversions anymore :-). ELN is very user friendly, self-intuitive.”
  16. 16. Case Study – Global roll out• Decision to continue with global roll-out in December 2013– Out-of-the-box ELN– Low risk based on extended pilot• Minor changes from pilot setup– New server environment– Internal training and support resources– Distributed administration• Production launch on May 6– Gradual increase to 3000 users during 2013– US, Europe, AsiaFrom Pilotinstallation toglobal launch in12 months
  17. 17. Questions?