Trinvis implementering af fuld integreret IT system - MES SESAM Presentation March 31st 2011

Transcription

1 Trinvis implementering af fuld integreret IT system - MES SESAM Presentation March 31st 2011 Kasper Malthe Larsen Sr. Solution Architect, Global MES Novo Nordisk

2 Trinvis implementatering af IT system Slide no 2 Topics to be addressed ISA-95 Functionality coverage (Scope) Tangible benefits or not (Our business drivers) Vendor selection (Drivers for Novo Nordisk) Global deployment / Central development Support setup (Centralised) Integration between MES and Equipment Benefits we aim for Harmonisation of processes (Recipes) Review by exception ASK QUESTIONS DURING THE PRESENTATION

3 Trinvis implementatering af IT system Slide no 3 ISA-95 and Scope History Many legacy systems at Novo Nordisk Global Roll-Out Timeline: Scope: 8 sites, 20 plants, 70 production lines in Product Supply (PS) Defined as a Level 3 system in our Enterprise architecture Product definitions (Recipes, Materials, Resources) Production Capacity (Limited to verify cleaning status) Production Schedule (Done by ERP, no finite scheduling in our scope) Production Performance (Documentation of process execution Batch reporting only)

4 Trinvis implementatering af IT system Slide no 4 MES Elements at Novo Nordisk The implementation of MES in NN is categorised into three elements A full MES implementation is consisting of all three elements as illustrated below The three elements are MES Warehouse MES Material MES Batch Legend Warehouse Main Warehouse Management & SAP Interface Material PO Execution & Material Management Full PAS-X Implementation (site-by-site) Batch Batch Execution

5 Trinvis implementatering af IT system Slide no 5 Scope of Novo Nordisk MES Elements Main Warehouse Management & SAP Interface The MES Warehouse and MES Material is designed to replace existing ERP functionality not available in SAP out-of-box MES Warehouse is always in scope of the PS@SAP PE implementations and includes interface to SAP and main warehouse functionalities PO Execution and Material Management MES Material includes material control and management of local production warehouses, and is a prerequisite when implementing MES Batch MES Material is also in scope of the PS@SAP PE implementations unless already implemented by another MES project Batch Execution MES Batch covers MES functionality beyond the MES Warehouse and MES Material elements, e.g. Electronic Batch Records (EBR) MES Batch is in scope for the MES Programme, but not as part of the PS@SAP implementations If MES Batch is implemented prior to the PS@SAP PE implementation on a site, then MES Material will be in scope of the MES Batch implementation with a manual interface to exiting ERP

6 Trinvis implementatering af IT system Slide no 6 Business Drivers Efficiency Standardisation Necessity Flexibility Excellence Improve lead time, Right First Time, review by exception and minimise unit cost Support process harmonisation across sites, accelerate better practice sharing and support the clean operation Replace MES functionalities from current ERP within discrete production as part of PS@SAP Handle increased production volumes and review by exception with a flexible system scalable to business needs Create transparency, ensure extended analyses, and embed best practises

7 Trinvis implementatering af IT system Slide no 7 Vendor selection criteria's Checks we did URS fulfillment Access to Resources Support service proximity Software Development Life Cycle (QMS) References at similar customers License costs and support service fees Long term Contract deals Checks I wish we had done more of System Architecture (Global vs. Local) Project Service Capabilities

8 Trinvis implementatering af IT system Slide no 8 Global MES Programme Standard MES for all discrete production plants (API not concluded yet) Central ownership of Core Solution MES Programme to control implementations and establish Organisation MES Programme Steering Committee to ensure MES Strategy fulfilment PAS-X Core Solution guidelines Central ownership Harmonised processes Global URS aligned across projects One version Unified infrastructure setup (but local instances) Central maintenance and upgrade coordination Global support organisation

9 Trinvis implementatering af IT system Slide no 9 Global impl. / Central dev. Implementation Project Scope Alignment VPL, RAR, Contracts etc. Core Project (E.g. NN Version 1.5) Development and configuration NN Specific Configuration and Qualification MBR Qualification Infrastructure Training Installation, configuration and qualification of P-Env. Handover from project Support SLA s Operation SLA CAB/SAB Technical input and clarification, Reviews, MBR/BRR design, User workshops Initiate & Analyse Execution (Core) Execution (Site) Operation & Maintenance Legend IT PMM Phase Core Manager Supplier Project Manager System Manager

10 Trinvis implementatering af IT system Slide no 10 Support Model Daily Issues Functional Support Technical Support 3. party Support End-Users organisation Super Users Support Local IT Support NN MES Hotline SI Site Denmark (Danish) Site France (French) Site US (English) 4 5 Service Desk Vendor Support Problem Investigation & Resolution Identity Management (USERAR2) 2 MES Vendor Local IT Support Hot fixes Code Debugging Taskforce Infrastructure Supplier Platform Support Support Agreements 6 Shop floor Systems Integration Vendors 7 DB OS Clients 8 System Governance & Change Management System Owner / SAB PS-IT NN CRS Local IT LSM

11 Trinvis implementatering af IT system Slide no 11 Integration to Equipment Leverage OPC AE and DA AE not securing message delivery (ETL solution at some sites) Simulators leveraged Transaction protocol for integration to MES All equipment suppliers are given the same specification Variance in OPC interpretation from equipment suppliers Supplier Standard Interface was limited to tag read and writes executed manually

12 Trinvis implementatering af IT system Slide no 12 Principal Interface Sketch MES MODE DB DOWNLOAD UPLOAD SAMPLE OPC Client OPC Client LOAD_CARRIER_ARRIVED DA AE ETL LOAD_CARRIER_INFO OPC PICK_UP_LOAD OPC DA Server OPC AE Server ALARM (ETL or OPC) WATCHDOG PCS Data Storage

13 Trinvis implementatering af IT system Slide no 13 Learning's Harmonisation learning's AQL Sample points are different across sites Interlock req. are different across sites Local QA interpretations are varying We see our MES programme as the Harmonisation Police (not the judge) Usage of same Recipes are possible (Governance) Review by exception It is a paradigm shift for us not done over night It is a question of trust Support model Not trivial Dedicated communication to stakeholder (Video s) SAP integration is not Standard (We use SAP s PI platform Service Buss)

14 Trinvis implementatering af IT system Slide no 14 Contact Kasper Malthe Larsen (Solution Architect, Global MES)