execution layer

The execution layer commonly refers to the group of systems, applications, and controls that manage and record real-time production and maintenance activities on the shop floor. It sits between high-level planning or business systems and low-level equipment control, and focuses on making sure work is carried out as specified, captured, and visible.

What the execution layer includes

In industrial and regulated manufacturing environments, the execution layer typically includes:

• Manufacturing Execution Systems (MES) or Manufacturing Operations Management (MOM) systems
• Electronic travelers, work orders, and routing control
• Digital work instructions and data collection at the point of work
• Quality checks during production, including in-process inspections and signoffs
• Traceability and genealogy capture for parts, materials, tooling, and process parameters
• Interfaces to equipment, test stands, and automation for sending setpoints or retrieving results
• Shop floor dispatching, sequencing, and basic scheduling within the day or shift

The execution layer is usually aligned with ISA-95 Level 3 activities, coordinating people, equipment, materials, and instructions to carry out planned work and record what actually happened.

What the execution layer does not include

The execution layer is distinct from:

• Enterprise planning and business systems, such as ERP, advanced planning and scheduling (APS), and financials, which handle long- to medium-term planning, costing, and order management.
• Low-level control systems, such as PLCs, DCS, CNC controllers, and SCADA/ICS, which directly control and monitor machines, process variables, and safety interlocks.
• Standalone engineering tools, such as CAD/PLM, which define product and process but do not typically control daily execution themselves.

Operational role in workflows and systems

In daily operations, the execution layer typically:

• Receives work orders, BOMs, and routings from ERP or planning systems.
• Presents operators with the right work, instructions, and data entry forms at each step.
• Enforces required checks, approvals, and data capture for quality and compliance.
• Collects real-time production and quality data, including nonconformances and rework.
• Reports status, progress, and exceptions back to planning, quality, and maintenance systems.

In regulated industries such as aerospace, defense, and medical devices, the execution layer is often where evidence for traceability, audit trails, and electronic batch or device records is generated and maintained.

Common confusion

• Execution layer vs control layer: The control layer (PLCs, DCS, CNCs) manipulates physical processes in real time, while the execution layer coordinates tasks, instructions, and records across people and equipment.
• Execution layer vs ERP layer: ERP plans and accounts for work at an order and cost level. The execution layer manages how that work is actually performed, step by step, on the shop floor.
• Execution layer vs visualization/analytics: Operations dashboards or analytics tools may show data from the execution layer, but they generally do not control workflows or enforce process steps.

Relation to MES and OT/IT integration

In many architectures, the MES is the primary system in the execution layer. It bridges IT (ERP, PLM, QMS) and OT (machines, test equipment, automation) by:

• Translating engineering and planning data into executable operations for the shop floor.
• Coordinating work across multiple cells, lines, or maintenance areas.
• Providing a consistent place to capture production records and quality evidence.

When discussing OT/IT integration or digital thread initiatives, the execution layer is often the focus because it is where designed processes and plans meet actual production behavior.