Connect981 – Content Dev

RSC Content Type: Glossary

  • Edge Device

    An edge device is hardware located near machines, production lines, sensors, or other industrial assets that collects, processes, stores, or routes data close to where it is generated. In manufacturing, edge devices commonly connect operational technology systems to plant networks, MES, SCADA, historians, cloud services, or analytics platforms.

    Edge devices may include industrial PCs, gateways, embedded controllers, smart sensors, or ruggedized compute modules. They are often used to filter data, translate protocols, buffer records during network interruptions, run local analytics, or support real-time monitoring without sending every raw signal to a central system.

    An edge device is not necessarily the same as a PLC or a sensor, although those devices may have edge capabilities. A PLC primarily controls equipment logic, while an edge device usually focuses on data acquisition, communication, and local computing. The term is also related to edge computing, which refers to the broader architecture of processing data near the source rather than only in a centralized data center or cloud environment.

  • What is MWI in manufacturing?

    In most manufacturing contexts, especially regulated environments, MWI usually means “Manufacturing Work Instructions” (sometimes written as “Manufacturing Work Instruction” or simply “Work Instructions”). These are the controlled documents or digital instructions that tell operators exactly how to perform a manufacturing, assembly, test, or inspection step.

    What are Manufacturing Work Instructions (MWI)?

    Manufacturing work instructions typically include:

    • Step-by-step tasks for a specific operation or workstation
    • Required tools, fixtures, gauges, and materials
    • Key parameters such as torques, temperatures, speeds, or tolerances
    • Inspection and verification points (including who signs off and how)
    • Links or references to higher-level procedures, drawings, and specifications
    • Revision information, approvals, and effective dates controlled through document or change control

    In digital environments, MWI may be delivered through MES or a digital work instruction system, often tied to specific part numbers, configurations, or serials to support traceability.

    Why the meaning of MWI can differ by site

    Acronyms are not fully standardized across industry. At some plants, MWI might be called WI, EWI (electronic work instructions), or SOP, and the acronym MWI may not be used at all. In others, MWI might mean something more specific, such as “Machining Work Instruction” or “Maintenance Work Instruction,” depending on local conventions.

    Because of this, you should always:

    • Check your organization’s quality manual or document control procedures to confirm the exact definition
    • Verify how MWI is represented in your PLM, MES, DMS, or ERP systems
    • Align on terminology in specifications, contracts, and supplier documentation to avoid ambiguity

    How MWI fits into regulated and brownfield environments

    In regulated or safety-critical manufacturing, MWI is tightly linked to:

    • Document control and change management to ensure operators only see the current, approved instructions
    • Traceability, since executed steps and signoffs often form part of the batch or device history record
    • Validation and qualification, because changing how instructions are authored or delivered can trigger revalidation of processes, software tools, and sometimes product qualifications

    In brownfield plants, MWIs commonly coexist across multiple systems: some on paper, some in shared drives, some embedded in legacy MES screens. Replacing them with a single new digital system can be difficult due to validation burden, integration complexity, and downtime risk, so many organizations move incrementally, standardizing formats and links first and then modernizing delivery over time.

    Practical implications when working with MWI

    When you design or change MWIs in a real plant environment:

    • Involve operations, quality, and industrial engineering to ensure instructions are usable, unambiguous, and compliant.
    • Plan for coexistence with legacy instructions and systems during transition, including operator training and clear identification of superseded documents.
    • Ensure that any system used to author, store, or present MWIs is under appropriate configuration and change control and, where applicable, validated.
    • Confirm that revision changes do not unintentionally break links in MES, PLM, QMS, or ERP routing and BOM structures.

    If your site uses the acronym MWI differently, that local definition should take precedence, but you should document it clearly in your internal glossary or procedures to prevent misinterpretation across teams and suppliers.

  • Production Confirmation

    Production confirmation is the recorded update that a production order, work order, or routing operation has been performed. It commonly captures what was completed, when it was completed, who performed it, and the quantities produced, scrapped, or reworked.

    In manufacturing systems, production confirmation is used to close the loop between planned work and actual shop-floor execution. It may be entered in an MES, ERP, digital traveler, or operator interface, and can update order status, labor time, machine time, inventory consumption, produced quantities, and traceability records.

    The exact data included depends on the process and system design. A confirmation may apply to a full production order, a single operation, a batch step, or a serialized unit. In regulated or quality-sensitive environments, it is often linked to operator signoffs, inspection results, material lots, equipment used, and timestamps.

    Production confirmation should not be confused with a customer order confirmation or sales order acknowledgment. In this context, it refers to confirmation of manufacturing execution, not confirmation that a customer order has been accepted.

  • System of Execution

    A system of execution is software used to direct, control, and record operational work while that work is being performed. In manufacturing, it commonly refers to systems that manage shop-floor execution, guide operators, capture production events, and maintain the current state of work in process.

    A system of execution often sits between planning or record systems, such as ERP and PLM, and equipment or OT systems on the production floor. It may dispatch jobs, enforce routings, present work instructions, collect inspection results, record material consumption, capture timestamps, and route exceptions or approvals. A manufacturing execution system, digital traveler platform, electronic batch record system, or electronic DHR workflow can function as a system of execution depending on the environment.

    The term should not be confused with a system of record. A system of record is the authoritative source for a defined set of data, while a system of execution is focused on controlling and documenting the work process as it occurs. A system of execution may create or update records, but its primary role is operational execution rather than long-term master data ownership or reporting alone.

  • Rework Routing

    Rework routing is the defined sequence of operations, checks, and approvals used to correct a nonconforming part, assembly, or batch and determine whether it can return to the normal production flow. In manufacturing systems, it describes where the item goes, what work is performed, what evidence is recorded, and who must review or approve the disposition.

    Rework routing is commonly managed in an MES, digital traveler, quality management workflow, or ERP-connected production system. It may include added work instructions, inspection steps, material review board decisions, quality holds, re-test requirements, and traceability records linking the rework activity to the original work order or serial number.

    The term should not be confused with normal production routing, which defines the planned manufacturing path for conforming work. It also differs from shipping or network routing. Rework routing is specifically tied to correcting or evaluating work that has deviated from the expected process or specification.

  • Tiered Supplier

    A tiered supplier is a supplier classified by its position in a multi-level supply chain, usually based on how directly it supplies an original equipment manufacturer, prime contractor, or final assembler.

    In manufacturing, a Tier 1 supplier typically supplies directly to the OEM or prime. A Tier 2 supplier supplies a Tier 1 supplier, and a Tier 3 supplier supplies a Tier 2 supplier. The same company can occupy different tiers depending on the product, program, or customer relationship.

    Tiered supplier structures are commonly used in procurement, supplier quality, materials planning, traceability, and supply chain risk management. They help describe where parts, materials, outside processing, or technical data move across the extended supply base.

    A supplier tier is not the same as a supplier rating, approval status, or quality score. It describes supply chain position, not necessarily performance, risk level, or certification status.

  • birth-to-grave records

    Birth-to-grave records are the collected lifecycle records that document an item, batch, asset, or work order from its origin through its final disposition. In manufacturing, the term commonly refers to traceable evidence covering creation, receipt, processing, inspection, movement, use, maintenance, rework, shipment, scrap, or retirement, depending on the object being tracked.

    These records may be maintained across MES, ERP, QMS, PLM, EAM, or document control systems. They can include material certifications, lot or serial history, routing steps, operator signoffs, inspection results, nonconformance records, rework activity, maintenance history, and disposition decisions.

    Birth-to-grave records do not usually mean a single document. They are more often a connected record set or evidence trail. The term is also broader than an audit trail: an audit trail records changes and actions in a system, while birth-to-grave records describe the full operational history of the item or process being controlled.

  • Characteristic Ballooning

    Characteristic ballooning is the practice of marking each inspectable requirement on an engineering drawing or model-based definition with a unique identifier, often shown as a numbered balloon or bubble. The identifier links the requirement to inspection records, measurement results, and quality documentation.

    In manufacturing, characteristic ballooning is commonly used for first article inspection, in-process inspection planning, source inspection, and supplier quality review. A balloon may identify a dimension, tolerance, note, material requirement, finish callout, process requirement, or other verifiable characteristic.

    The purpose is to create a clear cross-reference between the design requirement and the evidence that it was checked. For example, a numbered dimension on a drawing may correspond to the same characteristic number in an AS9102 Form 3 or an inspection report.

    Characteristic ballooning should not be confused with measurement itself. Ballooning identifies and organizes the characteristics to be verified; it does not prove conformity unless it is linked to accepted inspection results and supporting records.

  • bottleneck analysis

    Bottleneck analysis is the systematic identification and evaluation of the process step, resource, equipment, material flow, or decision point that limits overall throughput. In manufacturing, it is used to understand where work is waiting, capacity is constrained, or production flow is being slowed.

    The analysis commonly uses data such as cycle time, queue time, work-in-process, downtime, changeover time, labor availability, yield loss, and schedule adherence. It may be performed with shop-floor observations, value stream mapping, MES data, ERP schedule data, or operational performance metrics such as OEE and non-production time.

    A bottleneck is not always a permanently fixed asset or workstation. It can shift by product mix, staffing, material availability, inspection load, engineering holds, or maintenance conditions. Bottleneck analysis should also not be confused with root cause analysis, although the two are often connected. Bottleneck analysis identifies where flow is constrained; root cause analysis examines why that constraint exists.

    In industrial systems, bottleneck analysis is commonly applied in capacity planning, scheduling, line balancing, continuous improvement, and performance monitoring. For example, an inspection station with long queues may be the current bottleneck even if upstream machining equipment has lower nominal capacity.

  • Trace Package

    A trace package is a collected set of records used to show the history and traceability of a manufactured part, assembly, batch, or lot. It commonly includes evidence of what material was used, which operations were performed, who performed or approved them, what inspections or tests were completed, and how the item moved through production or shipment.

    In manufacturing and regulated supply chains, a trace package may contain items such as material certifications, certificates of conformance, shop travelers, inspection results, test records, nonconformance or deviation records, serialization data, lot genealogy, and supplier documentation. The exact contents depend on the product, customer requirements, industry practices, and internal quality procedures.

    A trace package should not be confused with shipment tracking or software execution tracing. It is an evidence package for product and process history, not merely a logistics status record or a system log. In digital manufacturing environments, trace packages may be assembled from MES, ERP, QMS, PLM, inspection, and supplier systems rather than maintained as a single paper folder.