iPEAK: Implementation of ELN & LIMS in a R&D environment March 31st, 2015 Author: Jasper Huiskamp 2 About the speaker… Jasper Huiskamp System Designer / R&D Information Analyst @ Teijin Aramid Professional Scrum Product Owner Background: organic chemistry 3 Content • • • • • About Teijin Aramid R&D organization iPEAK explanation Project approach: SCRUM Tips & Tricks About Teijin Aramid Our products Our product portfolio Para-aramid • Twaron • Sulfron • Technora Meta-aramid • Teijinconex • Poly-ethylene Endumax Serving key global markets • Automotive • Protection & Defense • Telecom • Oil & Gas • Mining Facts & Figures • Global market leader • Serving the industry for over 30 years • Global presence - 1,400 employees worldwide • Sustainable products & solutions • More than 80 patent positions • 5% of turnover invested in R&D • Dedicated converting facilities • Member of the Teijin Group Global presence 10 R&D: organization (1) • Located in Arnhem • Around 100 co-workers. • The objective and responsibility of research is to supply, maintain, and expand the knowledge in the area of: • the product and process optimization. • the product and process development. • the production of small test samples for marketing purposes. • Working in close collaboration with / delivering support to: • Sales & marketing departments. • Production plants in Emmen, Delfzijl and Arnhem. • Product test labs in Germany and Asia. 11 R&D: organization (2) • The research institute is subdivided in 8 groups with their own specialization / expertise: • Analytical Chemistry • Fiber Physics • Finishes • Mechanical Technology • Monomers & Polymers • Pulp & Shaping • Technical Fiber Applications • Wet Spinning • Many projects are handled by multidisciplinary teams throughout the R&D organization. 12 integration of Projects Experiments Analysis and Knowledge 13 R&D: current fragmented information resources 14 R&D: main objective – what is the problem? • The main objective of R&D is delivering knowledge Request for new project, support, R&D etc. R&D activities Data and results Process data and results Bottleneck Optimization point Knowledge 15 iPEAK: why this project? • Current situation: patchwork of IT systems Unable to support business goals and needs (overview / efficiency / integration). Increasing maintenance without significant future developments. • iPEAK is the ultimate solution to achieve an integrated and professional system architecture: • Lean: optimized and streamlined processes and workflows (less man hours and • • • • higher efficiency). Liability: overview and traceability of samples and results. Value: improve connection to production by speeding up product development. Solid base for future expansion. Based on SIMATIC IT R&D Suite; fits the Teijin Aramid IT system architecture. 16 SIMATIC IT R&D Suite • R&D Suite • Unilab 6.4 (advanced server) • Electronic Lab Notebook 6.5.1 • Report Manager 6.5 • Integration between ELN and Unilab is very important to support the R&D workflows: • Directly accessible data objects by all departments, thus • • • • • discarding the need to exchange information via word/excel/e-mail. Analysis requests. Correlate experiment/process data to analysis results. Support standardization. 75-100 users >80 instrument connections iPEAK: data model Model Data layers Current systems Digital archive: ZyImage / Share-Point · · · · Ideas Planning / progress tracking Reports Literature Conclusions ELN Aggregated data (= results) Validated data Calculated data · Experiments and process data (lab journal) · Explorative analysis/evaluation LIMS · Analysis request/applications · Analysis data · Evaluation data Report Manager Project Knowledge Planning M604 R&D Suite Electronic Lab Notebook QRA Labjournals QRP shields (various docs) Aralisa QRA application form QRS application form MAS (QRA) QRS Opdrachten DB QRF Finish DB YES QRM DB R&D Suite Unilab WRA QRS Tech GT DB (Data) Raw data · Instrument data · Machine / process data PI Local instrument data QRI paper lab notebook 18 R&D: activities and workflow (1) • ELN activities: product- and technology development, open research. • Examples: • Conducting laboratory experiments for e.g. creating physical samples. • Designing/testing equipment and technology. • Literature research. • Data characteristics: from very generic without specific format to very complex and more structured. • Experimental data, machine setup and settings. • Process parameters, observations, conclusions/discussions. • Images, pictures, graphs. • Documents. • In ELN the data is structured in R&D projects 19 R&D: activities and workflow (2) • LIMS activities: analytical measurements and method development. • Examples: • • • Laboratory analyses on samples. • Analysis method development/optimization. Data characteristics: highly structured, from routine to explorative. • Analytical results (parameters). • Images, spectra, chromatograms, graphs. • Interpretations / conclusions on results. Reporting: • Various objectives: • Correlate experimental (process) data with sample properties and analysis results. • Analysis results from series of measurements (e.g. within an analysis request). • Work-lists. • Workload monitoring. Often used for internal exchange of information, but can also be used for communicating results to business units, plants etc. 20 R&D data structure in ELN and Unilab R&D Project q q q q Task Agreement Project Info Milestones/results ... Notebook q q q q Personal Team Machine ... Experiment q q q q Info/Description Experimental data / Results Machine parameters/Settings ... Material Sample q q q q Sample Info Experimental data Results from Unilab … Material Samples Unilab (LIMS) Analysis Request Request Info: Samples, problem description, requested analysis etc. Analysis Request Analysis Samples 21 R&D: flexibility is key • Total freedom has resulted in this fragmented information landscape. • Research employees love this kind of ‘flexibility’. Flexibility = ultimate challenge in iPEAK: • Flexibility in capturing results from both standard and non-standard • • • measurements/experiments (numbers and not-numbers). Flexibility in capturing results from different areas of expertise in a standard way. Flexibility in adding new configuration templates without external help. Flexibility in creating new data report templates with the same tools. How do you implement one R&D-wide system without compromising flexibility in research processes? Not possible without major customizations. iPEAK: phasing 2011 August 2012 – May 2013 2012 2013 2014-2015 Gap analysis Prototyping Information Plan QRI High Level Assessment Prototype: Pilot Go Finalize pilot Gap analysis Go Go • Prototyping Pilot & Gap analysis in collaboration with Siemens. • Create user acceptance. • Determine scope / budget / global planning. • Roll out in collaboration with CGI • Customizations, configuration support. • Power user training. • Business consultancy. R&D Suite Roll out 23 iPEAK: Creating user acceptance • Implementation pitfalls: • Kingdoms / resistance to change. • Fall back into old habits / lack of discipline. • Try to implement advanced processes while the basics are not right yet. • Power Users from the R&D organization play an important role: • Trained in configuration of templates in ELN/Unilab create ownership. • Ambassadors towards the organization soften resistance. • Part of the iPEAK Development Team deliver valuable input and contribution. • All departments will eventually face process changes; power users play an important role in supporting this process. Power Users are a must-have for this kind of projects. Using SCRUM highly contributes to user acceptance. 24 How does SCRUM work? 25 iPEAK & SCRUM • SCRUM within Prince2 framework • Timebox: 4 weeks. • Power Users participate 2 days per week in the development team. • Major updates / new functionalities are released every 2-3 months. • Smaller updates can be released almost instantaneously when important. • Major benefits of using SCRUM: • We deliver user-approved increments = delivering quality! • By delivering and releasing finished work in smaller increments, we learn from • • • users and immediately incorporate enhancements in future sprints. The team has focus on the tasks at hand. We know exactly what the others are doing (Daily scrum). Organization is already using parts of the new system before the project has finished = delivering business value! 26 iPEAK: tips and tricks (1) • Involving Power Users for configuration creates acceptance! • SCRUM is highly beneficial to non-standard implementation projects. • Make sure your team members are available! • Not having enough time-capacity is killing, even with SCRUM. • Be prepared to create temporary workarounds when using SCRUM. • Delivering small increments will create a cut-over period until the project is finished. • A well-experienced implementation partner can deliver valuable support during change processes. • “Outsider” role. 27 iPEAK: tips and tricks (2) • Don’t underestimate time and effort required for supporting users. • Give hands-on training sessions in small groups (4-8 pers.). • Create quick-manuals and hand-out cards for your users as visual support. • Have someone with both business and IT-knowledge play a central role in the project. • This kind of projects should be both business- and IT-driven! 28 iPEAK: challenge goal met? Did we succeed in our challenge to implement one R&D-wide system without compromising flexibility in research processes? (note: the project is still ongoing at the time of this presentation) 29 Questions? Thank you for your attention!
© Copyright 2024