Connect981 – Content Dev

RSC Topic: Manufacturing Execution Systems (MES)

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

  • process cell

    A process cell is a defined grouping of production equipment and related resources used to carry out one or more batch processes. The term comes from the ISA-88 (S88) standard, which provides a consistent way to model and name batch manufacturing systems.

    Core meaning

    In an ISA-88 equipment hierarchy, a process cell sits below the site and area, and above the units that perform specific processing steps. A process cell typically includes:

    • One or more units (for example, reactors, mixers, blenders, fermenters)
    • Associated equipment modules and control modules (valves, pumps, scales, drives)
    • Shared resources such as utilities, transfer lines, and storage vessels that are part of the batch flow
    • Defined boundaries for scheduling, control, and tracking of batch activities

    A process cell is often treated as the logical production “line” for a batch process. It provides a scope within which recipes are executed, batches are scheduled, and sequences are coordinated across multiple units.

    How it shows up in operations and systems

    In industrial and regulated environments, a process cell commonly appears as:

    • A named object in a batch DCS or PLC/SCADA system, representing all equipment that participates in a given batch process
    • A planning and scheduling boundary in MES / batch management systems, used to allocate units and manage batch queues
    • A reporting and genealogy boundary for batch records, deviations, and electronic batch documentation
    • A configuration scope for equipment recipes, cleaning procedures, and change control

    The process cell concept helps separate what is being made (process and product recipes) from how the physical equipment is organized and controlled.

    What a process cell is not

    • It is not necessarily a single physical room or building, although it may coincide with one.
    • It is not the individual unit itself; units are components inside a process cell.
    • It is not a generic production line for discrete manufacturing, although the ideas of grouping equipment are similar.

    Common confusion

    • Unit vs. process cell: A unit is the equipment where a specific step of the batch is executed (for example, a reactor). A process cell can contain multiple units and coordinates their combined operation for a batch.
    • Area vs. process cell: An area is a broader logical or physical grouping (for example, “Drug Substance” or “Upstream”). One area may contain multiple process cells, each dedicated to a specific process or product family.
    • Skid/system vs. process cell: A skid or packaged system is a physical assembly of equipment. It can be modeled as part of a process cell, but the process cell is the logical control and scheduling boundary defined in ISA-88.

    Relation to ISA-88 context

    Within the ISA-88 model, process cells are central to how batch processes are structured. Recipes refer to process cells and their units when describing where operations are performed. This allows batch control systems, MES, and documentation tools to manage complex batch flows in a consistent way across equipment and sites.

  • aerospace

    Aerospace commonly refers to the sector that designs, manufactures, operates, and maintains aircraft, spacecraft, and related systems and components. In an industrial and manufacturing context, it focuses on organizations that produce parts, assemblies, and systems for civil and military aviation and space applications.

    Scope and characteristics

    In manufacturing, aerospace typically includes:

    • OEMs and primes that design and assemble complete aircraft, engines, or spacecraft
    • Tiers of suppliers providing structures, avionics, propulsion components, interiors, fasteners, and materials
    • MRO (maintenance, repair, and overhaul) organizations servicing in-use aircraft and components
    • Engineering, testing, and certification activities that support flight-worthy products

    Aerospace operations are usually subject to stringent quality, safety, and regulatory requirements. This often involves detailed configuration control, serial-level traceability, documented processes, and evidence that production and service activities follow approved methods.

    Operational meaning in regulated manufacturing

    Within regulated manufacturing systems, describing a process or standard as “for aerospace” usually implies:

    • Use of aerospace-focused quality standards, such as the AS9100 series
    • Higher expectations for documentation, inspection, and records retention
    • Integration of shop-floor systems (MES, QMS, ERP) to support traceability and configuration management
    • Controls around special processes, nonconformances, and corrective actions that meet aviation authorities and customer requirements

    For example, an aerospace plant may configure its MES to enforce operation-by-operation sign-off, serialized tracking of critical parts, and linkage of test results to each unit shipped.

    Common confusion

    • Aerospace vs. defense: “Aerospace” can include defense programs but is not limited to them. Many aerospace organizations serve commercial aviation only; others operate in combined aerospace and defense markets.
    • Aerospace vs. aviation: “Aviation” generally refers to aircraft and air travel within Earth’s atmosphere. “Aerospace” covers aviation and space-related activities, but in day-to-day manufacturing the terms are sometimes used interchangeably for aircraft-focused work.

    Relation to AS9100 and quality management

    Standards such as AS9100 are widely used aerospace quality management system standards. They define requirements for the processes, procedures, and records that aerospace organizations must operate and maintain. Production and service organizations in the aerospace sector often map these requirements into their existing tools and brownfield systems, including MES, ERP, and document control solutions.

  • work center

    Core meaning

    A **work center** is a defined group of equipment, people, and/or production capability used to perform one or more specific operations in a manufacturing process. It is a logical unit used by planning, scheduling, execution, and cost-accounting systems to represent where and how work is performed.

    Depending on the system, a work center may represent:

    – A single machine or workstation.
    – A production line or cell.
    – A team, shift, or labor pool with a particular skill set.
    – A shared resource such as a test bench or inspection station.

    Work centers are typically configured with attributes such as capacity, shift calendars, cost rates, and allowed operations.

    Use in ERP and planning systems

    In ERP and other planning-level systems, a work center commonly refers to a cost and capacity bucket used for:

    – **Routing and bills of operations:** Identifying where each operation in a routing is planned to occur.
    – **Capacity planning:** Calculating available hours and loading work orders against that capacity.
    – **Costing:** Accumulating labor and machine costs based on standard or actual rates for the work center.
    – **Scheduling:** Sequencing orders or operations to minimize changeovers or meet due dates.

    Here, a work center may be more abstract than a physical machine; multiple machines can roll up into one planning work center if they are interchangeable.

    Use in MES and shop-floor systems

    In MES and other shop-floor control systems, a work center usually has a more granular and physical interpretation, often aligned with actual equipment or cells. It is used for:

    – **Dispatching and execution:** Determining where operations are executed and which tasks appear on operator terminals.
    – **Data collection:** Tagging production results, parametric data, and operator actions with the work center performing the operation.
    – **Genealogy and traceability:** Associating serialized parts or batches with the work center that processed them at each step.
    – **Performance tracking:** Calculating OEE, throughput, downtime, and quality metrics by work center.

    A single ERP work center may map to multiple MES work centers when more detailed tracking is required.

    Boundaries and what it is not

    To avoid confusion, a work center is:

    – **Not always one machine:** It can be a group of machines, a production cell, or a labor pool.
    – **Not necessarily a physical room or area:** Though often mapped to physical locations, it is primarily a logical construct in systems.
    – **Not the same as a work order:** A work order defines *what* is produced; a work center defines *where* and *by whom/what* the work is done.
    – **Not identical to a production line:** A production line may span multiple work centers (e.g., forming, assembly, test), or an entire line may be modeled as a single work center, depending on system design.

    Common confusion and variations

    The term “work center” is used differently across organizations and systems:

    – **Versus machine / equipment:**
    – *Machine* usually refers to a single physical asset.
    – *Work center* may refer to a single machine or a group of similar machines treated as one resource for planning.
    – **Versus production cell or line:**
    – *Cell* often emphasizes a lean layout and flow; it can be implemented as one or several work centers in systems.
    – *Line* often spans multiple operations; some ERP configurations group an entire line into one work center for simplicity.
    – **Alternative labels:** Some systems use terms like *resource*, *resource group*, *resource center*, or *workstation* for concepts that overlap with work centers.

    When integrating systems (e.g., ERP with MES), clear mapping rules are needed because each system may use the term at a different level of granularity.

    Site context: serialized tracking and integration

    In contexts where MES differs from ERP in tracking serialized parts, the work center plays a key role:

    – In **MES**, each operation for a serialized part or batch is often recorded against a specific work center and, sometimes, specific equipment within that work center. This supports detailed genealogy, process history, and parametric data capture.
    – In **ERP**, the work center mainly appears on routings and work orders for planning and costing, with less detail about individual serials or parameter values.

    Accurate mapping between ERP work centers and MES work centers is important so that high-level order, inventory, and shipment records can be reliably linked to the detailed execution and genealogy history captured 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.

  • unit

    In manufacturing and automation, a unit commonly refers to a specific piece of equipment or a coordinated group of equipment that can carry out defined process operations under its own control.

    Meaning in batch and process control (ISA-88 context)

    Within ISA-88 and similar batch control models, a unit is an element in the equipment hierarchy. It sits below a process cell and above equipment modules and control modules. A unit has:

    • A clear process role, such as reactor, mixer, blender, or filling station
    • Dedicated or logically dedicated equipment needed to execute one or more operations
    • Its own control strategy, interlocks, and status, often managed by a unit controller
    • The ability to be scheduled to run a unit procedure or operation independently of other units

    In practice, a unit might be a single physical vessel with associated valves and instruments, or a tightly integrated skid that always runs as one functional block. Units are referenced in recipes, electronic batch records, MES routes, and scheduling systems to indicate where specific steps are executed.

    What a unit is not

    • It is not the whole production line or plant; those are modeled as process cells, areas, or sites.
    • It is not a low-level device like a single valve or sensor; those are typically control modules or part of equipment modules.
    • It is not the product or batch itself; it is the equipment used to process the product or batch.

    Operational use

    In day-to-day operations, units show up in:

    • DCS/PLC control: operators start, stop, and monitor unit phases, alarms, and modes.
    • MES and scheduling: units are resources that can be loaded with work, sequenced, and tracked for capacity and utilization.
    • Quality and traceability: electronic batch records and genealogy logs reference the unit where each critical operation occurred.
    • Maintenance and reliability: work orders and downtime events are recorded against specific units, improving root-cause analysis.

    Common confusion

    • Unit vs. equipment module: A unit is a higher-level functional block that may contain one or more equipment modules. Equipment modules are reusable subfunctions (for example, a dosing skid) that can be combined within a unit.
    • Unit vs. line or cell: In discrete manufacturing, people may informally call an entire line a “unit”. In ISA-88 terminology, that broader grouping is closer to a process cell or line, while a unit is a more focused functional equipment block.
    • Unit as measurement: Outside of control models, “unit” can mean a unit of measure (for example, kg, L) or an individual product item. In manufacturing control and ISA-88 discussions, “unit” almost always means an equipment element, not a measure.

    Link to ISA-88

    ISA-88 defines standard terminology and models for batch control. In that framework, the unit is a key building block in the equipment model, providing a consistent way to define where batch operations run and how recipes are mapped to physical equipment. This separation of recipes from equipment control relies on well-defined units so that different systems can coordinate execution and traceability across vendors and sites.

  • equipment module

    An equipment module is a logical grouping of physical equipment, instrumentation, and control logic that performs a defined set of functions as a unit. The term is commonly used in the context of ISA‑88 batch control, but the concept also applies in other automated manufacturing and process control environments.

    In practical terms, an equipment module represents the combination of hardware and software needed to carry out a specific operational capability, such as dosing, mixing, heating, or filling. It is more detailed than a process cell or unit, but typically higher level than an individual control module like a single valve or motor.

    Key characteristics

    An equipment module commonly:

    • Groups together related devices, sensors, and control modules that work toward a specific function
    • Has clearly defined capabilities (for example, “add material,” “heat to setpoint,” or “transfer to tank”)
    • Executes procedural logic, often through phases or steps, that can be invoked by higher-level recipes or control strategies
    • Is modeled in control systems and MES in a reusable, modular way so that recipes are separated from the underlying equipment implementation
    • Provides status, alarms, and data points that can be consumed by batch engines, MES, historians, and quality systems

    Examples in manufacturing include a dosing skid in a pharmaceutical suite, a CIP (clean-in-place) module for cleaning vessels, or a blending module in a food or specialty chemical plant.

    Role in ISA‑88 and automation architectures

    Within ISA‑88, equipment modules sit in the physical model below units and above control modules. They are a primary building block for structuring batch control, because they allow:

    • Separation of product recipes from equipment-specific control logic
    • Standardized interfaces between procedural control (recipes, operations, phases) and the underlying automation layer
    • Consistent modeling across different vendors and sites when integrating batch systems, DCS/PLC control, and MES

    In MES or higher-level systems, equipment modules are often represented as addressable resources with defined capabilities and capacity, which can be scheduled, allocated, and monitored for execution and traceability.

    What an equipment module is not

    • It is not just a single device. A single valve, pump, or sensor is typically handled as a control module or device-level object.
    • It is not the entire production line or process cell. Those are higher-level aggregations and may contain multiple units and equipment modules.
    • It is not a product recipe. Equipment modules enable recipe execution but do not define product formulations or process instructions by themselves.

    Common confusion

    Equipment module vs unit: A unit is a larger logical section of a process (for example, a reactor or granulation unit). A unit may contain multiple equipment modules that each carry out specific actions within that unit.

    Equipment module vs control module: A control module usually represents a single controllable element, such as a valve, motor, or PID loop. An equipment module orchestrates multiple control modules and procedural logic to perform a higher-level operation.

    Context from ISA‑88

    In the ISA‑88 framework, the equipment module concept is central to creating modular, vendor-neutral batch control designs. By defining standard boundaries and capabilities for equipment modules, organizations can integrate batch controllers, DCS/PLCs, and MES in a way that makes recipes more portable and changes to equipment less disruptive to validated or qualified processes.

  • Partial Kit

    Core meaning

    A **partial kit** in manufacturing commonly refers to a production order, work order, or job where only a subset of the required materials, components, or subassemblies has been picked, staged, or issued to production. The kit is therefore not yet fully complete according to the bill of materials (BOM) or routing requirements.

    A partial kit may be:

    – **Physically partial**: only some of the physical items are present at the line or staging area.
    – **System-partial**: only some items are issued in the MES/ERP, even if additional materials are physically present but not yet booked in the system.

    The term is usually applied to discrete and batch manufacturing environments that use kitting or work order–based material staging.

    Use in manufacturing workflows

    In typical workflows, a MES, ERP, or warehouse system:

    – Compares required materials from the BOM to available inventory.
    – Allocates and picks what is available.
    – Flags the order or kit as **partial** when one or more required items are missing or not yet issued.

    On the shop floor, a partial kit may lead to different operational behaviors depending on local rules, such as:

    – Holding the order until the kit is complete.
    – Starting early steps that do not depend on missing components.
    – Reprioritizing procurement or internal transfers to complete the kit.

    In regulated or traceability-focused environments, system status for partial kits is often explicitly tracked so that:

    – It is clear which materials have been issued and which are pending.
    – Material genealogy and lot/serial trace information remain consistent.
    – Quality or compliance checks can verify that critical items are not bypassed.

    Boundaries and what it is not

    A partial kit **is**:

    – A state or status of a work order or material kit, indicating incomplete material availability.
    – A term tied to material readiness for production, relative to the defined BOM or manufacturing recipe.

    A partial kit **is not**:

    – A substitute or alternative BOM; that is typically called an alternate or substitute material setup.
    – A permanent reduction in required materials; requirement changes are usually handled by engineering change or master data updates.
    – A generic stock shortage; the term is used specifically in the context of a given order, kit, or job.

    Relationship to MES and ERP systems

    In MES/ERP and warehouse management systems, partial kits are often represented through:

    – **Status codes** such as “Partially kitted,” “Partially issued,” or “Shortage.”
    – **Exception lists** or shortage reports that show missing items per work order.
    – **Material availability checks** run during scheduling or release that identify which orders would start with partial kits.

    These systems may enforce or report rules such as:

    – Whether an order is allowed to start if it has partial kit status.
    – Which components are considered critical and must be present before release.
    – How backflushing or consumption posting handles components not yet fully issued.

    Common confusion and related terms

    Partial kit is sometimes confused with:

    – **Backorder**: usually refers to customer-facing orders where the customer demand cannot be fully shipped. Partial kit focuses on internal production material readiness.
    – **Shortage**: a broader term for any lack of materials. Partial kit describes a more specific situation for a particular order or kitting activity.
    – **Incomplete assembly**: refers to the product state after manufacturing has started. Partial kit is about the pre-production material staging state.

    Using the specific term “partial kit” helps distinguish situations where some, but not all, required materials are ready for a specific job, which is important for planning, scheduling, and shop-floor control.