manufacturing execution systems. why mes? missing link between pcs and corporate systems (typically...
Post on 21-Dec-2015
213 views
TRANSCRIPT
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 (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)
InSite Enterprise Applications
PLANT APLANT A PLANT BPLANT B PLANT CPLANT C
LIVERELAYRELAYLIVERELAYRELAY OtherSystemOther
System
LIVEALERTALERTLIVEALERTALERTLIVESYNCSYNCLIVESYNCSYNC LIVEVIEWVIEWLIVEVIEWVIEW
LIVECONNECTCONNECTLIVECONNECTCONNECT
SITE L
EVEL
SITE L
EVELCO
LLABO
RATIO
N LEVEL
COLL
ABORATI
ON L
EVEL
InSite Total SolutionInSite Total Solution
Enterprise Integration (Camstar’s LiveConnect)Enterprise Integration (Camstar’s LiveConnect)
EnterpriseBusiness Intelligence(Camstar’s LiveView and LiveAlert)
EnterpriseBusiness Intelligence(Camstar’s LiveView and LiveAlert)
> Reporting > Alerts > Dashboard > Corporate Portal
Plant 1 Plant 1
SPC
PaperlessDHR/EBR
CAPA
Training
RMA
Supplier Quality
Electronic Signature
Maintenance &Calibration
DocumentControl
Production
Plant 2 Plant 2
SPC
PaperlessDHR/EBR
CAPA
Training
RMA
Supplier Quality
Electronic Signature
Maintenance &Calibration
DocumentControl
Production
Global Manufacturing
Data
Global Manufacturing
Data
Workflow ModelingA 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
Mfg Order, Material List
InSite and ERP Processing Touch Points
InSite and ERP Processing Touch Points
Planning
Raw Materials
WIP Starts
WIP
WIP Completions
Finished Goods
WIP Move WIP QuantityChange
ERP
LiveRelay Summary
Ship unitsShip units
Receive units
Receive units
Plant APlant A
Plant BPlant B
LiveRelay Process
Send XML with unitsSend XML with units
Plant APlant A
Receive XML and units
Receive XML and units
Plant BPlant B
Deliver XML DocumentsDeliver XML Documents
Reply Instructions
Reply Instructions
Execute Instructions
Execute Instructions
Ship units to Plant BShip units to Plant B
Start units from Plant AStart units
from Plant A
Routing Server
Routing Server
Typical Multi-Site Processes
• Plants have same capability
• Utilize capacity when needed
• Information from each plant transferred and returned with units
Plant APlant A
Plant BPlant 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 APlant A Plant BPlant B Plant CPlant 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 APlant A
Sub Contractor
Sub Contractor
Plant CPlant 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