Transcript Slide 1
Manufacturing Execution Systems Why MES? • Missing link between PCS and corporate systems (typically ERP) • PCS attached to devices on factory floor – – – – – – Often proprietary technologies Export data as text Often left unconnected Or managed by specialists (non-IT) Critical systems (eg: BGE) Requirement for compliance • ERP does not finish where PCS begins • Invoke different competences Who? • A different set of vendors • Specialising in manufacturing systems (exCIM vendors) – eg: Camstar • Different philosophy – Attention to local differences – Used to dealing with production managers – More of a “front end” system – Market still relatively under-equipped (unlike ERP) InSite Enterprise Applications LIVESYNC LIVEALERT LIVEVIEW LIVECONNECT Other System LIVERELAY PLANT A PLANT B PLANT C InSite Total Solution Enterprise Integration Paperless DHR/EBR Plant 1 Maintenance & Calibration Paperless DHR/EBR CAPA Supplier Quality Electronic Signature (Camstar’s LiveConnect) Training Production Document Control Global Manufacturing Data RMA SPC Enterprise Business Intelligence (Camstar’s LiveView and LiveAlert) Plant 2 CAPA Supplier Quality Electronic Signature Maintenance & Calibration > Reporting > Alerts > Dashboard > Corporate Portal Training Production Document Control RMA SPC Workflow Modeling A workflow consists of multiple process steps, each of which references a specification or … … another workflow which consists of its own steps • • • InSite XML Connect – Publishes XML documents from any transaction – Processes all inbound transactions from XML Business Process Integration (BPI) Center – Based on Microsoft's BizTalk Server EAI framework – Business logic and process flows – Best practices for data integration between the InSite and ERP applications ERP Application Adapter – Transforms and processes inbound transactions to ERP – Produces and transforms outbound transactions from ERP InSite and ERP Processing Touch Points ERP Planning Finished Goods Mfg Order, Material List Raw Materials WIP Quantity Change WIP Move WIP Completions WIP Starts WIP LiveRelay Summary Plant A Ship units Plant B Receive units LiveRelay Process Plant A Ship units to Plant B Plant B Start units from Plant A Send XML with units Execute Instructions Receive XML and units Routing Server Deliver XML Documents Reply Instructions Typical Multi-Site Processes • Plants have same capability • Utilize capacity when needed • Information from each plant transferred and returned with units Plant A Plant B Typical Multi-Site Processes • Plants have specialized capability • Units are transferred to multiple plants sequentially • Information from all preceding plants stays with units Plant A Plant B Plant C Typical Multi-Site Processes • Units are transferred to a sub contractor, then continue at new plant • Information from all preceding plants stays with units if sub contractor using InSite Plant A Sub Contractor Plant C Conclusion on MES • At present only manufacturing sites • No critical mass in the market • Not really competitors of ERP vendors but have power to change the market • No notion of a single instance anywhere • Maintains local power but provide powerful linkages