150 likes | 541 Views
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)
E N D
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 (ex-CIM 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)
LIVEALERT LIVESYNC LIVEVIEW LIVECONNECT LIVERELAY InSite Enterprise Applications COLLABORATION LEVEL Other System SITE LEVEL PLANT A PLANT B PLANT C
InSite Total Solution Enterprise Integration (Camstar’s LiveConnect) Plant 1 Plant 2 Paperless DHR/EBR CAPA Paperless DHR/EBR CAPA Global Manufacturing Data Supplier Quality Training Supplier Quality Training Electronic Signature RMA Electronic Signature RMA Production Production Maintenance &Calibration Document Control SPC Maintenance &Calibration Document Control SPC EnterpriseBusiness Intelligence (Camstar’s LiveView and LiveAlert) >Reporting > Alerts > Dashboard > Corporate Portal
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
ERP Planning Finished Goods Mfg Order, Material List Raw Materials WIP Quantity Change WIP Move WIP Completions WIP Starts WIP InSite and ERP Processing Touch Points
LiveRelay Summary Plant A Ship units Plant B Receive units
LiveRelay Process Plant A Plant B Ship units to Plant B Start units from Plant A Send XML with units Receive XML and units Routing Server Execute Instructions Reply Instructions Deliver XML Documents
Plant A Plant B 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 Plant C 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 C Sub Contractor 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
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