Connect981 – Content Dev

RSC Topic: Manufacturing Execution Systems (MES)

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

  • Backflushing

    Operational meaning

    Backflushing is an inventory accounting method in which the consumption of components and materials is recorded automatically when a production operation or finished good is reported as complete, rather than when the materials are physically picked or used.

    In a typical backflushing setup:
    – The bill of materials (BOM) and routing define which components are assumed to be consumed by a given operation or finished unit.
    – When operators or the system declare that an operation or order has produced a certain quantity, the system automatically “flushes” (issues) the corresponding quantities of components from inventory.
    – Labor or machine time may also be backflushed, based on standard times in the routing, instead of being captured manually.

    The method relies on accurate master data (BOMs, routings, scrap factors) and relatively stable, repeatable processes.

    Use in manufacturing and regulated environments

    In manufacturing execution systems (MES) and enterprise resource planning (ERP) systems, backflushing commonly refers to automated posting of:
    – Component issues from stock to work-in-process (WIP) or directly to finished goods
    – Standard labor or machine time against production orders or operations

    Typical workflow:
    1. Materials are staged or kitted to the line without detailed transactional booking at pick time.
    2. The operator reports production completion (e.g., units good, units scrapped) in the MES or ERP.
    3. The system calculates and posts component consumption and time based on BOM and routing standards.

    In regulated or highly traceable environments, backflushing may be restricted to:
    – Low-risk, low-cost consumables
    – Non-serialized items
    – Operations where exact component-to-lot traceability is not required at unit level

    Where detailed traceability is required, systems may combine backflushing for some materials with explicit lot selection and scanning for critical, serialized, or compliance-relevant components.

    Boundaries and exclusions

    Backflushing:
    – **Is** an inventory and production accounting technique in IT/OT systems (ERP, MES, MRP).
    – **Is not** a physical material handling process; it does not describe how items are moved, only how usage is recorded.
    – **Is not** the same as real-time scanning of each component; it assumes consumption based on standards.
    – **Does not** by itself ensure regulatory or quality compliance; it is one possible transaction method within a broader control system.

    Backflushing can be applied at different levels of granularity (per operation, per order, per reporting period), but always with the characteristic that posting happens after the fact, triggered by a completion event, not at the exact moment of use.

    Common confusion and misuse

    Backflushing is often confused with:

    – **Issue on pick / manual issuing**: Materials are deducted from inventory when a warehouse or line-side operator records a pick or issue transaction. With backflushing, deductions are triggered by production reporting, not by picking.
    – **Real-time consumption tracking**: Systems that scan every component at the workstation can post consumption in real time and with specific lot/serial data. Backflushing usually uses standard quantities and may not capture every unit-level variation or scrap event unless specifically modeled.
    – **Automatic replenishment (e.g., Kanban)**: Kanban or similar pull systems govern when materials are replenished; backflushing governs how consumption is recorded in the system. The two can be used together but are conceptually distinct.

    Site context application

    In the context of industrial operations and manufacturing systems:
    – Backflushing is configured in MES/ERP integration to simplify data entry and align inventory movements with production reporting.
    – It interacts with quality systems and traceability rules, which may limit where and how backflushing can be used.
    – Operations and IT teams must align BOM and routing data, scrap handling logic, and reporting points so that backflushed quantities reasonably reflect actual shop-floor consumption.

    Backflushing is thus a key concept when designing transaction models, shop-floor visibility, and inventory accuracy strategies in both discrete and process manufacturing.

  • Electronic Batch Record (eBR)

    An Electronic Batch Record (eBR) is a digital version of the batch production record that documents all relevant manufacturing steps, parameters, materials, checks, and approvals associated with producing a specific batch or lot. It replaces or augments paper batch records with data captured and managed in electronic systems, such as a manufacturing execution system (MES) or specialized batch record software.

    What an Electronic Batch Record includes

    While implementations vary by industry and plant, an eBR commonly includes:

    • Product, batch, and lot identifiers
    • Manufacturing instructions and recipes executed for the batch
    • Material genealogy, including raw materials, intermediates, and components used
    • Equipment used, status checks, and setpoints where applicable
    • In-process measurements, test results, and key process parameters
    • Operator actions such as sign-offs, inspections, and verifications
    • Deviations, exceptions, holds, and associated investigations or comments
    • Review and approval records, often including electronic signatures

    In regulated environments, eBRs are often structured to align with applicable quality and record-keeping requirements, but the core concept of a complete, batch-specific manufacturing record applies across both regulated and non-regulated manufacturing.

    Operational use in manufacturing systems

    Operationally, eBR functionality is frequently provided by an MES that coordinates production between planning systems (such as ERP) and the shop floor. In this context, the eBR acts as the central, execution-level record for:

    • Driving and enforcing step-by-step workflows and recipes
    • Collecting real-time production and quality data from operators, equipment, and connected systems
    • Tracking work-in-process (WIP), materials consumption, and batch status
    • Providing traceability and genealogy across batches, lots, and components
    • Supporting batch review by exception and batch release processes

    Data stored in an eBR is often integrated with ERP, LIMS, quality management systems, and historians to support traceability, investigations, audits, and continuous improvement activities.

    What an Electronic Batch Record is not

    An eBR is:

    • Not just a scan or PDF of a paper batch record; it typically involves structured, queryable data.
    • Not the full quality management system, though it connects to quality processes such as nonconformance handling and CAPA.
    • Not the same as a device history record or electronic device history record in discrete medical device manufacturing, although the concepts are related.

    Common confusion

    • eBR vs. paper batch record: A paper batch record is a physical document package. An eBR is stored and managed electronically, often allowing automated data capture, checks, and reporting.
    • eBR vs. eDHR: An electronic Device History Record (eDHR) focuses on the history of an individual device or serial number. An eBR focuses on the batch or lot, more common in process industries and any batch-oriented production.
    • eBR vs. MES: The MES is the system or platform that may generate and manage eBRs. The eBR is the record itself, not the system.

    Context from manufacturing execution

    In many plants, especially in regulated or highly traceable environments, the eBR is one of the central outcomes of MES deployment. The MES coordinates work orders, enforces workflows and specifications, collects data, and ultimately assembles that information into an electronic batch record that can be used for batch review, release decisions, investigations, and audits.

  • overhead

    Operational meaning

    In industrial and manufacturing contexts, **overhead** commonly refers to ongoing indirect costs required to run operations that cannot be easily or economically traced to a specific product unit, batch, or job.

    These are costs that support production and business activity but are not directly embedded as distinct line items in a unit’s material or direct labor cost.

    Typical manufacturing-related overhead categories include:

    – **Indirect labor**: supervisors, planners, maintenance, quality engineers, custodial staff
    – **Indirect materials and supplies**: lubricants, cleaning agents, tooling wear, general consumables
    – **Facilities and utilities**: plant rent or depreciation, lighting, HVAC, water, compressed air, general power
    – **Equipment-related costs**: depreciation, calibration, non-project maintenance, insurance
    – **Shared services**: production planning, scheduling, IT/OT support, health and safety, HR for the plant
    – **General administrative allocation**: accounting, legal, corporate functions allocated to the manufacturing site

    In cost accounting, these costs are typically accumulated in overhead cost pools and then allocated to products, processes, or contracts using defined allocation bases (for example, machine hours, labor hours, or cost drivers defined in activity-based costing).

    Use in manufacturing workflows and systems

    Overhead is used as a distinct cost category in:

    – **Standard costing**: overhead rates are set and applied to planned production volumes to estimate unit cost.
    – **Job and contract costing**: overhead is allocated to specific jobs, product families, or customers using a chosen allocation basis.
    – **Variance analysis**: actual overhead is compared with allocated or absorbed overhead to identify over- or under-absorption.
    – **Budgeting and forecasting**: fixed and variable overhead components are planned, then monitored during execution.

    In OT/IT environments (MES, ERP, and related systems), overhead:

    – Is usually modeled at work center, cost center, or plant level rather than at individual operation records.
    – May be allocated automatically during order confirmation or period-end closing based on production quantities or time.
    – Can be analyzed alongside direct costs to understand true product or line-level economics.

    Boundaries and exclusions

    Within this site context, **overhead**:

    – **Includes**: indirect, supporting costs necessary for operations but not directly tied to a single unit (for example, supervision, planning, utilities, plant depreciation).
    – **Excludes**:
    – **Direct materials** (raw and component materials directly incorporated in the product).
    – **Direct labor** that can be clearly tracked to a unit, batch, or job.
    – **Capital investments themselves** (though the depreciation of capital assets is usually treated as overhead).

    Overhead also differs from **waste** in lean manufacturing. Overhead may contain wasteful elements but, as a category, it is not synonymous with waste. Some overhead is necessary to operate safely, compliantly, and reliably.

    Common distinctions and confusion

    The term **overhead** is sometimes used imprecisely, so several distinctions are useful:

    – **Fixed vs. variable overhead**
    – *Fixed overhead*: costs that do not change significantly with short-term production volume (for example, base facility rent, some salaried staff).
    – *Variable overhead*: costs that change with production activity (for example, some utilities, indirect materials consumption, certain support labor).

    – **Manufacturing overhead vs. administrative overhead**
    – *Manufacturing overhead*: indirect costs tied to running the plant and production processes.
    – *Administrative or general overhead*: corporate-level or non-plant functions (for example, corporate finance, executive management) that may be partially allocated to plants or products.

    – **Overhead vs. margin erosion**
    – Overhead is a cost category; margin erosion is an outcome where total costs (including overhead) reduce profitability. Overhead may contribute to margin erosion if it is high relative to revenue or poorly allocated.

    Site-context application: overhead in fixed-price and MES discussions

    In discussions of **fixed-price contracts** and **MES-driven improvements**:

    – Overhead is part of the **total delivered cost** for a contract or product line.
    – MES or other OT/IT systems may reduce apparent unit costs (for example, via less scrap or rework) but can also unintentionally **add overhead** (for example, additional coordination, reporting, or support burden).
    – An improvement is often evaluated by whether it reduces or stabilizes total cost, including any **incremental overhead** created by new processes, systems, or compliance activities.

    This makes overhead a key consideration when assessing whether changes in a regulated manufacturing environment truly improve margins rather than shifting costs between direct and indirect categories.

  • operation

    In industrial and manufacturing contexts, an operation is a defined segment of work performed to achieve a specific outcome within a larger process or procedure. It typically groups related tasks or actions that transform materials, data, or equipment states in a controlled and repeatable way.

    General meaning in manufacturing

    On the shop floor, an operation commonly refers to a specific step in a routing, work order, or job sequence. Each operation usually has:

    • A defined purpose (for example, machining, assembly, inspection, cleaning)
    • Assigned resources (equipment, tools, materials, and personnel or role)
    • Execution conditions and parameters (such as speeds, temperatures, or tolerances)
    • Start/finish criteria and recorded results (quantities produced, scrap, measurements)

    In IT/OT systems, operations are often represented as records or objects in MES, ERP, or scheduling systems, with identifiers (such as operation numbers) that link to work instructions, recipes, or control logic.

    Operation in ISA-88 (S88) batch control

    Within the ISA-88 batch control framework, an operation is a level in the procedural hierarchy used to describe how a batch is executed. The procedural model is commonly expressed as:

    • Procedure
    • Unit procedure
    • Operation
    • Phase

    In this hierarchy, an operation is a logical grouping of phases that carry out a coherent portion of the unit procedure. For example, in a mixing unit procedure, operations might include “charge materials,” “mix,” and “discharge.” Each operation is more detailed than the unit procedure but less granular than the individual phases (such as open valve, start agitator, or start heating).

    Operations in ISA-88 are typically modeled in the control system or batch management system and linked with MES recipe management and electronic records for traceability and validation.

    What an operation is not

    • It is not the entire process or batch on its own; it is one step or segment within a higher-level procedure or routing.
    • It is not necessarily a single manual action; operations often contain multiple detailed actions or phases.
    • It is not limited to physical equipment steps; data processing, quality checks, and documentation steps can also be modeled as operations in MES or workflows.

    Operational use in systems and workflows

    Across OT and IT systems, operations appear as:

    • Routings and work orders: Each operation has planned duration, required resources, and completion tracking.
    • MES execution steps: Operations may be the units for electronic work instructions, data collection, and electronic signatures.
    • Control system logic: In batch systems following ISA-88, operations organize the phases executed by controllers and units.
    • Reporting and KPIs: OEE, cycle time, and nonproductive time are frequently analyzed at the operation level.

    Common confusion

    • Operation vs. process: A process is the overall sequence that delivers a product or outcome; operations are the individual steps within that sequence.
    • Operation vs. phase (ISA-88): A phase is the most granular, equipment-oriented step executed by the control system. An operation groups multiple phases into a meaningful functional segment of the unit procedure.
    • Operation vs. activity or task: Activities or tasks are often used for more detailed, human-level actions inside an operation, especially in digital work instructions.

    Relation to the ISA-88 procedure context

    In the ISA-88 view of a procedure, the operation serves as an intermediate level of detail that connects high-level unit procedures to low-level phases. Modeling operations clearly helps align batch control logic with MES recipe structures, quality records, and validation documentation in regulated manufacturing environments.

  • area

    In manufacturing and industrial operations, an area commonly refers to a defined part of a site that groups related production, processing, or support activities and the equipment used for those activities.

    Core meaning in manufacturing

    Within the context of standards such as ISA-95, an area is typically a physical and organizational subdivision of a site. It is used to group:

    • Related production lines or process cells (for example, a filling and packaging area)
    • Support functions (for example, a utilities area or warehouse area)
    • Equipment and personnel that share similar processes, hazards, or control strategies

    An area is usually larger than a single line, unit, or cell, but smaller than an entire site or enterprise. It may span one or more buildings or floors as long as it is treated as a coherent operational segment.

    Operational use

    In day-to-day operations, the term area is used to:

    • Define scope for production scheduling and dispatching in MES or ERP
    • Segment alarm, event, and historian data (for example, by plant area)
    • Structure access control, maintenance responsibilities, and work permits
    • Organize quality records, deviations, and batch documentation by where work was performed

    In ISA-95-style models, areas often appear in master data and hierarchies that link enterprise, site, area, line or process cell, unit, and equipment modules.

    What an area is not

    • It is not necessarily a formal legal entity or company; that role is usually the enterprise.
    • It is not the same as a specific machine or unit; those are typically modeled as units, equipment modules, or individual assets.
    • It is not always identical to a department or cost center, although organizations may align them.

    Common confusion

    Area vs. site: A site generally represents a full plant or location, often corresponding to a postal address or campus. An area is a subdivision of that site used for organizing operations.

    Area vs. production line or process cell: A line or process cell is usually a more detailed element within an area, representing a specific flow path or unit operation sequence. An area can contain multiple lines or cells.

    Relation to ISA-95 context

    In ISA-95-style hierarchies, area is one level in the physical and organizational breakdown between the site and lower-level elements such as production lines, process cells, and units. Implementations may vary by manufacturer, but area is consistently used as an intermediate grouping that helps align OT structures with MES and ERP models.

  • work in process

    Operational meaning

    Work in process (often abbreviated WIP) refers to all partially completed products, subassemblies, or lots that are currently moving through a manufacturing process but have not yet been converted into finished goods. It includes:

    – Material that has been released to production and undergone at least one value-adding step
    – Units or lots waiting at intermediate steps (queues, buffers, inspection points)
    – Items temporarily held for rework, additional operations, or in‑process testing

    In most accounting and planning usages, work in process sits between raw materials and finished goods in inventory classifications.

    Use in manufacturing and operations

    In industrial and regulated environments, work in process commonly refers to:

    – **Shop floor status:** What is actively being manufactured on lines, cells, and work centers.
    – **Production control:** The quantity and location of in‑process units for each order, batch, or lot.
    – **Traceability:** The link between materials, process steps, parameters, and quality records for items that are not yet finished.
    – **Execution systems:** Items represented as in‑process operations or steps in MES, LIMS, or batch systems.

    Systems may model work in process at different levels of granularity, such as individual serial numbers, containers, pallets, or process orders.

    Boundaries and exclusions

    Work in process generally **includes**:

    – Released orders, batches, or lots that have started at least one operation
    – In‑process inventory held between operations (queues, staging areas)
    – Units undergoing rework or additional processing steps

    It typically **excludes**:

    – Raw materials and purchased components that have not entered a production operation
    – Finished goods that have completed all required processing and are available for shipment
    – Tools, fixtures, and spare parts (these are not WIP inventory)

    In some accounting practices, very short‑cycle or continuous processes may treat all production as work in process until formal transfer to finished goods, but the conceptual boundary remains the same: items are in an incomplete manufacturing state.

    Common confusion and terminology

    Two similar phrases are used:

    – **Work in process (WIP):** More common in discrete and assembly manufacturing, and in operations/lean discussions.
    – **Work in progress:** Often used interchangeably, especially in accounting, though some organizations reserve it for long‑duration projects.

    In most manufacturing and MES/ERP contexts, the two terms are treated as synonyms. When precision matters, organizations may define them differently in internal procedures or accounting policies.

    Work in process is also sometimes confused with:

    – **Workload or labor capacity:** WIP refers to physical product inventory in process, not staff utilization.
    – **Backlog:** Backlog is ordered work not yet started. Once material is released and processing begins, it becomes WIP rather than backlog.

    Site context: work in process and mid‑shift changes

    In regulated operations, work in process is a key concept when handling mid‑shift engineering changes or specification updates. At the change cutover point, teams typically:

    – Identify which units or lots are **existing work in process** under the old configuration
    – Segregate or label new work in process started under the new configuration
    – Ensure MES/ERP, batch records, and labels distinguish old vs. new WIP for traceability

    Accurately defining and controlling work in process at the moment of change helps maintain clear genealogy and avoid mixing configurations, especially when batches, orders, and documentation states overlap on the shop floor.

  • Work-in-Progress (WIP) Location

    Core meaning

    A **Work-in-Progress (WIP) location** is a defined physical or logical place where partially completed materials, products, or batches are stored or held between processing steps. It is used to track items that have been started but are not yet finished goods or scrap.

    In manufacturing and industrial operations, WIP locations are configured so that systems and people can see where an in-process order currently resides, how much WIP exists, and what stage of the routing it is in.

    Typical characteristics

    A WIP location commonly:

    – Holds items that are **partially processed** (not raw material, not finished goods)
    – Is associated with one or more **operations, work centers, or production lines**
    – Has a defined **capacity or handling rule** (e.g., number of pallets, lot size, queue limits)
    – Is represented in systems as a **stock location, bin, or buffer** dedicated to in-process items
    – Participates in **material movements, reservations, and inventory valuation** as WIP inventory

    WIP locations can be:

    – **Physical**: racks, carts, staging areas, kanban squares, intermediate tanks, curing rooms
    – **Logical/system-only**: virtual buffers or queues in MES/ERP that do not map 1:1 to a single physical spot but represent a stage in the process

    Use in digital systems (MES, ERP, WMS)

    In OT/IT and integrated manufacturing systems, a WIP location commonly refers to:

    – **MES**: the intermediate state or buffer where a production order, lot, or batch is recorded as waiting, running, or held between operations
    – **ERP**: an inventory location type used for valuation and planning of WIP inventory, distinct from raw materials and finished goods locations
    – **WMS**: a bin or zone where in-process material is stored and moved under warehouse control but classified as WIP

    Transactions such as **issue to WIP**, **move to next operation**, or **confirm operation** typically move quantities in and out of WIP locations so that systems can show current WIP balance and route status.

    Boundaries and exclusions

    A WIP location:

    – **Includes**: queues in front of machines, staging between operations, curing/aging areas, in-process tanks, inspection hold areas for in-process lots
    – **Excludes**:
    – Raw material or component storage that has not yet entered the production process
    – Finished goods locations used for saleable, released product
    – Scrap or quarantine locations used exclusively for nonconforming or rejected items

    It is possible for a single physical space to serve multiple logical purposes, but in systems the **WIP location role** is distinct from raw, finished, or scrap locations for tracking and accounting clarity.

    Common confusion and related terms

    – **WIP location vs. WIP inventory**: WIP inventory is the quantity and value of in-process items; the WIP location is where those items are recorded as being held.
    – **WIP location vs. work center**: A work center is a resource or group of resources performing operations. A WIP location is a storage or queue point where material waits before, after, or between operations, and may or may not be physically at the work center.
    – **WIP location vs. buffer/queue**: In many MES and scheduling tools, buffers or queues are implemented as WIP locations. However, “buffer” emphasizes flow and sequencing, while “WIP location” emphasizes inventory tracking.

    Application in regulated and quality-focused environments

    In regulated manufacturing environments (e.g., life sciences, food, specialty chemicals), WIP locations are often used to:

    – Maintain **traceability** of lots and batches between processing steps
    – Enforce **status control** (e.g., in-process, on hold, awaiting QC sample, under investigation)
    – Support **electronic batch records (EBR)** and audit trails by recording exactly where and when product moved between operations
    – Align with **master data** such as routing steps, equipment lists, and sampling points for in-process testing

    Here, WIP locations are tightly controlled so that any in-process material can be identified by location, status, and history at any time.

  • Kit

    Operational meaning

    In industrial and manufacturing contexts, a **kit** commonly refers to a predefined set of components, materials, documents, or tools that are grouped together for a specific and repeatable purpose. The items in a kit are typically:

    – Defined by a part number, BOM, or standard list
    – Collected and controlled as a single logical unit
    – Prepared in advance for a specific product, work order, or task

    Kits are used to reduce on-line picking, standardize work, and support traceability by ensuring that all required items for a defined activity are available together.

    Typical uses in manufacturing and operations

    Common forms of kits include:

    – **Production kits (material kits)**: Pre-picked sets of components, subassemblies, and consumables required to complete a specific operation, work order, or batch.
    – **Service or maintenance kits**: Pre-defined sets of spare parts, gaskets, fasteners, and tools needed to perform a standard maintenance task or repair.
    – **Quality or test kits**: Grouped measurement devices, gauges, reagents, or sample containers defined for a particular inspection or test method.
    – **Documentation kits**: Bundled work instructions, batch records, labels, and checklists prepared for a job or batch.

    In many plants, a kit is physically packaged (e.g., in bins, totes, or bags) and also represented digitally in ERP, MES, or inventory systems as a distinct item or structure.

    Use in digital systems (ERP, MES, inventory)

    In OT/IT and manufacturing systems, **kit** may be represented in several ways:

    – As a **phantom part or virtual item** in ERP, defined by a bill of materials that lists all kit contents.
    – As a **pre-assembly or pick list** generated for a work order, which warehouse or stores staff use to collect kit items.
    – As a **kit transaction type** in MES or WMS, recording kit creation, issuance to production, and (in some cases) de-kitting or returns.
    – As part of **traceability records**, where the kit ID or lot is linked to specific batches, serial numbers, or equipment.

    In regulated environments, kit definitions and contents are often controlled documents, managed under change control, and tied to validated procedures.

    Boundaries and exclusions

    In this context, a kit:

    – **Includes**: Any structured, predefined grouping of items intended to be handled as a unit for production, maintenance, quality, or similar operations.
    – **Can be**: Physical (packaged together), logical (defined only in systems), or both.
    – **Is not**:
    – A single component or SKU with no defined multi-item structure.
    – An ad-hoc collection of materials picked on the fly without a defined list or standard.
    – A full product line or assortment intended for sales/marketing bundles without a specific operational task.

    Common confusion and related terms

    – **Kit vs. BOM (bill of materials)**: A BOM defines the structure of a product or assembly. A kit is a grouping of items for a task; it may be defined by its own BOM, but it is not necessarily a finished product.
    – **Kit vs. assembly/subassembly**: An assembly is a product configuration created by joining parts. A kit groups items that may or may not be assembled; they are simply prepared together for use.
    – **Kit vs. pack or bundle**: In commercial contexts, “bundle” or “pack” may refer to sales configurations. In manufacturing, “kit” is usually tied to production, maintenance, or quality tasks and internal logistics.

    Site context application

    In industrial operations and regulated manufacturing systems, kits are a key element of material management and execution:

    – In **ERP and MES integration**, kit structures can drive automated picking, staging, and issuance to work centers.
    – In **quality and compliance**, controlled kit definitions help ensure that correct, qualified materials and tools are used and that usage can be traced.
    – In **lean and shop-floor visibility**, kitting supports standardized work, reduces line-side inventory complexity, and simplifies visual control of readiness for production or maintenance tasks.

  • inventory item

    Core meaning

    An **inventory item** is a distinct, trackable record that represents a material, component, kit, or finished product in an inventory management or execution system. It combines an identifier (such as a part number or material code) with attributes like description, unit of measure, and status, and is used to track on‑hand quantities and movements across locations.

    In industrial and regulated manufacturing environments, inventory items are defined consistently across ERP, warehouse management, and MES or other OT systems so that physical materials can be traced and controlled digitally.

    Typical characteristics

    An inventory item commonly includes:

    – A unique identifier (item code, part number, material ID)
    – A description and item type (raw material, intermediate, kit, finished good, spare part, etc.)
    – Unit of measure (e.g., kg, L, each)
    – Inventory status (e.g., released, quarantined, blocked, expired)
    – Basic logistical data (storage conditions, lot/serial tracking flags, shelf life)
    – Commercial or planning attributes (where managed, such as ERP/MRP)

    Execution systems then track **instances** of that item as stock records, often by lot, batch, or serial number.

    Use in MES and ERP workflows

    In ERP and warehouse systems, inventory items are the basis for:

    – Maintaining stock balances by location and status
    – Planning and procuring materials (MRP)
    – Valuing inventory for financial reporting
    – Defining bills of materials (BOMs) and routings

    In MES and other manufacturing systems, inventory items are used to:

    – Identify what material is consumed or produced on each operation step
    – Enforce material selection rules (correct item, correct revision)
    – Attach traceability data (lot, batch, or serial genealogy) to a standard item definition
    – Align shop‑floor transactions with ERP or warehouse transactions

    The inventory item record itself is relatively stable; day‑to‑day movements update stock quantities and statuses associated with that item.

    Kits as inventory items (site context)

    In some plants, **kits** (pre‑assembled sets of components) are modeled as separate inventory items in ERP and/or MES. In that case, the kit has its own item code and attributes, and stock is tracked for the kit in addition to its components.

    Other plants keep only the individual components as inventory items and treat kit building as an operational step without a distinct kit item in MES. The choice typically depends on:

    – Whether kits are physically built and stored before use
    – How traceability is organized (to kit level vs. component level)
    – How closely MES inventory structures must match ERP and warehouse structures

    Both approaches rely on the same underlying concept: an inventory item is the master data object that standardizes how a material or structure (including a kit) is referenced and tracked.

    Boundaries and common confusion

    – An **inventory item is not the same as on‑hand stock**. The item is the master data record; stock represents current quantities of that item at specific locations and statuses.
    – It is distinct from a **lot, batch, or serial number**. Those identify specific instances of an inventory item.
    – It is not a **BOM**. A BOM describes how multiple inventory items are combined to make another inventory item.

    In some organizations, terms like *material*, *material number*, *part*, or *SKU* may be used instead of *inventory item*. These usually refer to the same underlying concept but can differ in scope (for example, commercial SKUs vs. internal material numbers).