The functional layers
CAD defines geometry; CAM creates manufacturing strategy and toolpaths; DNC and program management control distribution; MES coordinates work and execution; monitoring captures states and events; quality systems preserve requirements and results. ERP remains the commercial and planning backbone for many shops. Product names overlap, so compare the exact workflow rather than the category label.
Identifiers make the thread
Define stable identifiers for customer, part, revision, routing, operation, machine, program, tool, fixture, material lot, inspection result and shipment. Integrations cannot repair ambiguous identity after the fact.
Machine connectivity
Document controller, protocol, available signals, time basis, network boundary, read/write permissions, buffering and failure behavior. Read-only monitoring and control-changing integrations have very different risk profiles.
Ownership and security
Assign owners for master data, interfaces, alerts, backups, patches and incident response. Segment operational technology appropriately, use least privilege and test restore procedures. A connected machine should not depend on an undocumented personal account or unsupported workstation.
Questions manufacturers ask
Do we need an MES?
Only if the use cases justify it. First define the decisions and gaps that current ERP, scheduling, DNC, monitoring and quality tools do not solve.
What should connect first?
Choose one high-value workflow with stable identifiers and a measurable response, then expand from the proven pattern.
Can monitoring be read-only?
Yes, and read-only is often the right starting boundary when the goal is visibility rather than control.
Primary sources and further reading
MBB uses these sources for general process and safety context. A link is not an endorsement, affiliation or substitute for current manufacturer documentation.