Connect981 – Content Dev

RSC Topic: Manufacturing Execution Systems (MES)

How production work is routed, tracked, and controlled on the shop floor.

  • MES

    A Manufacturing Execution System (MES) is a software application or suite of applications used to manage, monitor, and track production activities within a manufacturing facility. In the ISA‑95 model, MES typically operates at Level 3, between enterprise business systems and shop‑floor control systems.

    MES systems collect and use real-time and historical production data from equipment, operators, and other systems to coordinate and record manufacturing operations. Common MES functions include:

    • Dispatching and sequencing production orders to specific equipment or work centers
    • Tracking work-in-progress (WIP), including lot, batch, and unit genealogy
    • Capturing production events such as start, stop, downtime, and changeovers
    • Recording material consumption, yields, scrap, and rework
    • Managing electronic work instructions, recipes, and routings
    • Recording operator actions, labor time, and resource utilization
    • Collecting quality-related data such as measurements, test results, and checks
    • Maintaining electronic production records, such as batch records or device history records

    MES often interfaces upward with enterprise systems such as ERP for order, material, and master data exchange, and downward with shop-floor automation such as SCADA, PLCs, and DCS for equipment and process data. Within ISA‑95, MES functionality is described using standardized models for production, quality, maintenance, and inventory operations.

  • AI

    Core meaning

    AI (artificial intelligence) commonly refers to computer-based techniques that enable systems to perform tasks that typically require human intelligence. In industrial and manufacturing contexts, this usually means software that can:

    – Detect patterns in data (for example, sensor streams or quality records)
    – Make predictions (such as equipment failure risk or batch outcomes)
    – Classify situations or states (like defect types or process conditions)
    – Generate recommendations (for setpoints, schedules, or workflows)

    AI in this sense includes modern machine learning approaches as well as more traditional rule-based or expert systems, as long as the system is performing a task that mimics or augments human reasoning or decision-making.

    Use in manufacturing and regulated operations

    In industrial and regulated manufacturing environments, AI is typically embedded into existing OT and IT systems rather than deployed in isolation. Common uses include:

    – **Process optimization:** Proposing parameter adjustments for reactors, filling lines, or packaging equipment based on historical and real-time data.
    – **Predictive maintenance:** Estimating remaining useful life of assets and flagging equipment at risk of failure.
    – **Quality analytics:** Identifying factors associated with deviations, nonconformances, or out-of-spec results.
    – **Computer vision:** Classifying visual defects or verifying assembly and packaging steps using camera systems.
    – **Planning and scheduling:** Assisting with production sequencing, changeover planning, and resource allocation.

    These AI capabilities are often surfaced through MES, LIMS, historian, or analytics platforms as insights, alerts, or suggested actions rather than fully autonomous control.

    AI and MES/ERP/OT integration (site context)

    Within MES and related shop-floor systems, AI is commonly applied as:

    – **Decision support inside workflows:** The AI engine suggests next actions (for example, recommended hold, rework, or release decisions) that operators or supervisors approve in the MES.
    – **Constraint-based recommendations:** AI proposes parameter ranges or routing options that must still comply with configured master data, recipes, and business rules.
    – **Automated checks:** AI flags unusual patterns in batch records, equipment states, or operator actions for review.

    Direct, fully automatic enforcement of AI recommendations in MES workflows—without human oversight or strong safeguards—is uncommon in regulated environments. When used in control loops or automated enforcement, AI behavior is typically constrained, monitored, and validated for a narrow, well-characterized use case with traceability of decisions.

    Boundaries and what AI is not

    In this context, AI generally **includes**:

    – Statistical and machine learning models (regression, classification, clustering, time-series models)
    – Deep learning models (for example, for image or signal processing)
    – Rule-based or expert systems when they automate reasoning-like tasks

    It generally **does not refer to**:

    – Simple, static calculations or thresholds (for example, a fixed SPC control limit)
    – Basic automation logic (PLCs, interlocks, ladder logic) that does not adapt or infer new patterns
    – Generic data processing or ETL pipelines without any predictive, inferential, or decision-making component

    In manufacturing discussions, using “AI” to describe any automated script or report can cause confusion; the term is more precise when reserved for systems that infer, predict, or generalize from data or encoded knowledge.

    Common confusion and terminology

    The term AI is often used interchangeably with or in contrast to related concepts:

    – **Machine learning (ML):** A subset of AI that focuses on models learned from data. Many industrial AI applications are specifically ML-driven, but in practice people may use “AI” as the umbrella term.
    – **Advanced analytics:** A broader label that may include AI/ML, statistical analysis, and other quantitative methods. Not all advanced analytics are AI.
    – **Automation:** Refers to execution of tasks without manual intervention. AI may inform or drive automation, but automation can also be purely rule-based or deterministic without any AI component.

    In regulated environments, this distinction matters because AI-driven behavior may require different validation, monitoring, and governance than deterministic logic.

    AI in validation and compliance discussions

    When AI is deployed in GxP or otherwise regulated operations, discussions typically focus on:

    – **Explainability and traceability:** How AI reached a recommendation or classification, and how that is captured in audit trails and batch records.
    – **Change control:** How model updates, retraining, and configuration changes are governed in line with existing quality systems.
    – **Scope and limits of use:** Clearly defining which decisions the AI may support, which it may automate under constraints, and where human review is required.

    These considerations shape how AI outputs are integrated into MES workflows, electronic signatures, and release decisions, without changing the fundamental definition of AI itself.

  • cycle count

    Core meaning

    A **cycle count** is a recurring, sample-based physical inventory check in which a subset of stock (items, locations, or both) is counted and reconciled against the recorded inventory in a system such as ERP, WMS, or MES.

    Unlike a full physical inventory, which attempts to count all stock at once, cycle counting spreads counting activities over time according to a defined schedule or sampling strategy.

    How cycle counts are used in manufacturing

    In industrial and regulated manufacturing environments, cycle counts commonly:

    – Focus on specific **locations** (e.g., high-velocity racks, quarantine areas, kitting zones)
    – Focus on specific **materials** (e.g., high-value APIs, controlled components, serialized parts)
    – Are triggered by **time**, **transaction volume**, or **risk category** (e.g., ABC classification)
    – Are executed via **scanners, mobile terminals, or MES/WMS terminals** on the shop floor
    – Result in **reconciliations**: adjusting system records, investigating discrepancies, and documenting reasons (e.g., scrap not recorded, mis-picks, unit-of-measure errors)

    Cycle counts can be planned (on a defined schedule), event-driven (triggered by anomalies), or both.

    Relationship to MES and inventory accuracy

    In the context of MES- and ERP-integrated operations, cycle counts:

    – Provide the **ground truth** used to measure inventory accuracy KPIs
    – Are often initiated or recorded in MES or WMS, then reconciled back to **ERP/MRP** stock records
    – Help validate that **transaction logic, scanning workflows, and master data** correctly represent real movements and consumption on the shop floor
    – Are used as a **statistical sampling method** to assess whether an MES inventory-accuracy pilot is producing stable and auditable improvements

    A well-defined cycle count program typically specifies scope (materials, locations), frequency, counting method (blind vs. guided), and rules for investigating and documenting discrepancies.

    Boundaries and exclusions

    A cycle count **includes**:

    – Physical verification of quantities (and sometimes status or condition) of selected inventory
    – Comparison of the physical result with the system on-hand balance
    – Documentation and processing of necessary adjustments or investigations

    A cycle count **does not necessarily include**:

    – Counting all inventory across the entire site in one event (that is a full physical inventory)
    – Valuation or costing calculations beyond updating quantities
    – Broader process-improvement activities, although findings may later be used for root-cause analysis

    Common variants and methods

    Common cycle counting approaches include:

    – **ABC cycle counting**: higher-frequency counts for A-class (high-value/critical) items; lower frequency for B/C items
    – **Location-based cycle counting**: rotating through storage locations (bins, racks, zones) on a schedule
    – **Event-based cycle counting**: triggered by stockouts, negative inventory, or system exceptions
    – **Blind counting**: counters do not see the system quantity before counting, to reduce bias

    These methods can be combined and configured based on risk, regulatory requirements, and operational constraints.

    Common confusion and misuse

    Cycle count is often confused with:

    – **Full physical inventory**: a one-time, comprehensive count of all stock, often requiring production shutdown or system freeze. Cycle counts are ongoing and partial.
    – **Inventory audit**: a formal, often external assessment that may use cycle counts as evidence but has a broader assurance objective.

    In manufacturing IT/OT contexts, “cycle count” refers specifically to the **inventory counting activity**, not to:

    – Production machine cycles
    – Maintenance cycles
    – Process control loop cycles

    Site-context application

    Within MES- and ERP-integrated manufacturing systems, cycle counts are a key mechanism for:

    – Verifying that **system-recorded inventory** reflects physical reality at selected points
    – Providing **statistically sound stock checks** for pilots and ongoing operations
    – Supplying data to measure whether changes to MES workflows genuinely improve **inventory accuracy** and stay stable under day-to-day operating conditions.

  • shop traveler

    A shop traveler is a document or packet of documents that physically or digitally accompanies a work order, batch, or unit through all required steps in a manufacturing process. It provides the routing, key instructions, and data collection points needed to execute and record the work on the shop floor.

    What a shop traveler includes

    While formats vary, a shop traveler commonly contains:

    • Basic identifiers, such as work order number, part number, revision, quantity, due date, and customer or program
    • Process routing, listing each operation, required sequence, and responsible work center or machine
    • Reference to applicable specifications, drawings, and work instructions, often by document number and revision
    • Space for recording actual start/finish times, operator IDs, and quantities good/scrap at each step
    • Check boxes, sign-offs, or stamps for inspections, in-process checks, and quality verifications
    • Fields for recording nonconformances, rework, deviations, or concessions tied to the work order
    • In some environments, traceability data such as lot numbers, serial numbers, and material/consumable identifiers

    In paper-based environments, the traveler is usually a printed multi-page form that physically moves with the parts. In digital or MES-driven environments, the same concept is implemented as a digital traveler or electronic routing tied to the work order.

    Role in industrial and regulated operations

    In regulated manufacturing, the shop traveler is often a central record used to demonstrate that required steps were followed and documented. It helps coordinate:

    • Execution, by telling operators what operation to perform next, where, and under which conditions
    • Scheduling, by showing current operation status and remaining steps for planning and dispatching
    • Quality assurance, by capturing in-process inspections, measurements, and sign-offs for later review
    • Traceability, by linking a specific part or batch to its process history, operators, and materials used

    In some industries the data originally collected on shop travelers is later summarized into device histories, batch records, or as-built records maintained in quality or manufacturing systems.

    Paper travelers vs. digital travelers

    A traditional shop traveler is paper-based. A digital traveler or electronic traveler is a system-based representation of the same concept within a manufacturing execution system (MES) or similar platform. The digital traveler:

    • Uses screens instead of printed packets to present routing and instructions
    • Captures operator inputs, inspection results, and timestamps directly into a database
    • Is often integrated with ERP, QMS, and other systems for real-time status and traceability

    Organizations may run hybrid approaches where a core routing is controlled in an ERP or MES, but printed travelers are still used as the primary shop-floor artifact.

    Common confusion

    • Shop traveler vs. work order: A work order authorizes and plans the work (what to build, how many, by when). The shop traveler is the execution packet and record that follows the work across the shop, often referencing the work order number.
    • Shop traveler vs. work instructions: Work instructions describe how to perform a specific task or operation. The shop traveler references those instructions and collects data but generally does not replace detailed instructions.
    • Shop traveler vs. route sheet or routing: A routing defines the sequence of operations, usually in ERP or MES. The traveler includes that routing plus identifiers, data fields, and sign-off areas used during execution.

  • production visibility

    Production visibility commonly refers to how clearly and how quickly an organization can see what is happening in its manufacturing operations, from order release through execution, quality checks, and shipment. It is about having accurate, timely, and usable information on the status of work, equipment, materials, and quality on the shop floor and connected processes.

    What production visibility includes

    In industrial and regulated environments, production visibility typically covers:

    • Real-time work status: knowing which orders, lots, or serial numbers are running, waiting, or blocked at each operation or cell.
    • Material and WIP status: tracking where material is, how much work-in-process exists, and whether shortages or holds are affecting production.
    • Equipment and line performance: seeing utilization, downtime, speed, and basic performance indicators such as OEE or NPT drivers.
    • Quality status: visibility into inspections, test results, nonconformances, rework, and holds tied to specific operations or units.
    • Schedule and promise alignment: comparing actual progress to planned schedules, customer due dates, and capacity assumptions.
    • Traceability context: linking what is happening now to the related travelers, work instructions, revisions, batches, and serials.

    Production visibility is usually enabled by systems such as MES, SCADA/ICS, quality systems, and ERP, combined with data collection at machines and workstations. In regulated sectors, visibility also depends on disciplined document control, traceability, and event logging.

    What production visibility does not include

    The term generally does not refer to:

    • Detailed supply chain visibility beyond the plant or immediate suppliers, which is often discussed separately as multi-tier or supply chain visibility.
    • Purely financial visibility, such as accounting-only views of cost or margin, unless directly tied to operational performance data.
    • High-level BI dashboards only without a clear link to actual shop floor states, events, and identifiers.

    Operational meaning in manufacturing systems

    From a systems perspective, production visibility usually means that operational data is:

    • Timely: updated close to real time as operators, equipment, or sensors report events.
    • Granular: available at the level of work order, operation, batch, or serial number, not just at an aggregated shift or plant level.
    • Contextualized: linked to work instructions, revisions, part numbers, routings, and quality records so events can be understood and audited.
    • Accessible: visible to the relevant roles (operators, supervisors, planners, quality, maintenance, and management) through appropriate interfaces.

    Examples include a supervisor seeing which jobs on a line are causing non-productive time, or quality teams seeing open NCRs by operation and their impact on throughput.

    Use in regulated environments

    In regulated manufacturing, production visibility is closely tied to:

    • Traceability and genealogy of parts, assemblies, and repairs.
    • Evidence for audits, including time-stamped events, approvals, and deviations connected to specific production steps.
    • Exception management, such as early detection of nonconformance trends, scrap drivers, and process drifts.

    Here, visibility is not only about performance; it is also about being able to reconstruct what happened, where, when, and under which controlled documents or revisions.

    Common confusion

    • Production visibility vs. supply chain visibility: Production visibility focuses on internal manufacturing execution and immediate supporting processes. Supply chain visibility extends upstream and downstream across suppliers, logistics, and customers.
    • Production visibility vs. reporting: Static or delayed reports can describe what happened, but production visibility usually implies near real-time, operations-level information that reflects current conditions.
    • Production visibility vs. control: Having visibility does not automatically provide control. Control requires the ability to intervene in processes, adjust plans, or change system behavior; visibility is about seeing reliable information to support those decisions.

  • 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.

  • Operations layer

    The operations layer commonly refers to the functional level in an industrial or manufacturing environment where production activities are planned, executed, monitored, and controlled. It sits between high-level business planning systems and low-level control systems, and focuses on how work actually flows through the plant.

    Position in typical manufacturing architectures

    In multi-layer manufacturing and industrial IT/OT reference models, the operations layer usually maps to:

    • Manufacturing execution and operations management systems, such as MES and MOM
    • Production scheduling and dispatching functions
    • Quality execution, data collection, and nonconformance handling on the shop floor
    • Material movement, WIP tracking, and work order progression

    It is typically located:

    • Below the enterprise or business layer (ERP, financials, long-term planning)
    • Above the control and field layers (PLCs, SCADA, DCS, sensors, and actuators)

    What the operations layer includes

    Within industrial operations, the operations layer generally includes:

    • Execution of production orders and routing steps
    • Real-time visibility of work-in-progress, machine status, and operator activity
    • Collection and contextualization of production, quality, and traceability data
    • Enforcement of work instructions, process parameters, and inspection plans
    • Short-interval scheduling, rescheduling, and response to disruptions
    • Interfaces between enterprise systems (ERP/PLM/QMS) and shop-floor control systems

    In regulated or high-compliance environments, the operations layer is also where many records that support traceability, device history, and audit evidence are generated and governed.

    What the operations layer does not cover

    The term usually excludes:

    • Enterprise-level processes such as financial accounting, HR, high-level sales & operations planning
    • Low-level control logic within PLCs or embedded controllers
    • Pure infrastructure services like networking hardware, storage, or generic cloud hosting

    Operational usage

    In practice, organizations use “operations layer” to describe the systems and teams that coordinate daily production activity. Examples include:

    • MES coordinating work orders, sequences, and electronic travelers
    • Quality execution capturing inspections, measurements, and nonconformances as work is performed
    • Real-time dashboards providing supervisors with status of lines, cells, and shifts
    • Integration services that translate ERP plans into executable jobs at machines and workstations

    Common confusion

    • Operations layer vs. business layer: The business layer focuses on planning, finance, and enterprise-wide decisions. The operations layer focuses on day-to-day production execution and short-horizon scheduling.
    • Operations layer vs. control layer: The control layer deals with direct machine and process control (PLCs, SCADA). The operations layer coordinates what work should be done, tracks it, and records results, but does not directly control actuators or write PLC logic.
    • Operations layer vs. network layers: In networking, “layer” often refers to OSI or TCP/IP layers. The operations layer is an application and process concept, not a network protocol layer.

  • Aircraft-on-Ground (AOG)

    Aircraft-on-Ground (AOG) commonly refers to an unplanned situation in which an aircraft is unable to depart due to a technical fault, missing or nonconforming part, documentation issue, or other condition that prevents safe and compliant operation. The aircraft is grounded until the issue is resolved, and this status typically triggers expedited maintenance, logistics, and decision making.

    Scope and usage in industrial and regulated environments

    In aerospace and other highly regulated manufacturing and maintenance environments, AOG is used to describe:

    • An operational status where an in-service aircraft cannot fly and requires immediate corrective action.
    • A priority level applied to maintenance tasks, parts orders, and engineering support for that aircraft.
    • A driver for rapid coordination across maintenance, supply chain, quality, and engineering functions, including OT/IT and MES/ERP processes.

    AOG conditions may be caused by issues such as unavailable spare parts, nonconforming components, incomplete or inconsistent maintenance records in digital systems, unresolved findings from inspections, or system failures detected by onboard monitoring.

    Operational and systems implications

    In operations and manufacturing systems that support airlines, MROs, and aerospace OEMs, an AOG event can affect:

    • Maintenance execution: Work is re-prioritized, often requiring immediate work orders, deviations, or concessions managed through maintenance or MES systems.
    • Supply chain and inventory: Parts movements, reservations, and procurement may be escalated, with AOG-specific order types or priority flags in ERP systems.
    • Quality and compliance: Documentation, release records, and configuration control must be verified quickly to return the aircraft to service in a compliant manner.
    • Data and integration: Accurate and timely information exchange between maintenance systems, MES, ERP, and airline operations is critical to track status, approvals, and traceability related to the AOG event.

    Common confusion

    • AOG vs routine maintenance: Routine or scheduled maintenance is planned and typically does not place the aircraft in an urgent grounded status. AOG specifically refers to unplanned grounding that requires immediate attention.
    • AOG vs non-operational for commercial reasons: An aircraft that is parked or not in use for scheduling or commercial reasons is not necessarily in AOG status. AOG is tied to a technical, safety, or compliance-related inability to fly.

    Context in manufacturing and MRO operations

    Within manufacturing plants and maintenance, repair, and overhaul (MRO) facilities that support fleets, AOG conditions influence production priorities, capacity planning, and expediting rules. For example, a component repair order may be flagged as AOG, causing it to bypass standard queues, with additional documentation and digital tracking to maintain configuration and traceability requirements while responding quickly.