Connect981 – Content Dev

Glossary Tag: process monitoring

  • Manufacturing work instructions

    Manufacturing work instructions are controlled documents that describe, step by step, how to perform specific production, inspection, or test activities to make a defined product or component. They translate higher-level process descriptions and product specifications into clear, executable tasks for operators and technicians on the shop floor.

    Manufacturing work instructions typically include the sequence of operations, required tools and materials, key parameters and setpoints, inspection or measurement steps, and acceptance or rejection criteria. In regulated or quality-critical environments, they are subject to document control, version management, and formal review and approval.

    How manufacturing work instructions are used

    In industrial and regulated manufacturing environments, manufacturing work instructions commonly:

    • Guide operator actions for assembly, machining, mixing, packaging, testing, or inspection
    • Reference related documents such as drawings, specifications, recipes, bills of materials, and standard operating procedures
    • Capture critical quality steps, sign-offs, and required checkpoints
    • Provide visual aids such as diagrams or photos to clarify tasks
    • Serve as a basis for training and qualification on specific operations
    • Record production data or confirmations when implemented digitally through MES or electronic work instruction systems

    What manufacturing work instructions are not

    • They are not high-level policies or quality manuals, which describe overarching requirements.
    • They are not full process descriptions or SOPs when those focus on broader procedures rather than task-level steps.
    • They are not engineering drawings or specifications, although they often reference those documents.

    Common confusion

    The term “manufacturing work instructions” is sometimes used interchangeably with:

    • Standard operating procedures (SOPs): SOPs usually describe how to perform a class of activities at a procedural level. Manufacturing work instructions tend to be more detailed and operation-specific.
    • Work orders or production orders: These authorize and schedule work for specific quantities and time periods. Manufacturing work instructions describe how to do the work but do not schedule or authorize it.
    • Digital work instructions: Digital work instructions are an electronic implementation of manufacturing work instructions within MES or other systems, but the underlying concept of task-level guidance is the same.

    Context: MWI acronym

    In many manufacturing environments, the acronym “MWI” is commonly used to mean “manufacturing work instructions.” Sites may use different acronyms or document types, so the meaning should be verified against local document control practices and system configuration.

  • Concession Volume

    Concession volume commonly refers to the quantity of material, parts, assemblies, or finished units covered by an approved concession. In manufacturing and quality contexts, a concession is a documented acceptance of a specified nonconformance under defined conditions, and the concession volume sets the numerical scope of that acceptance.

    This term helps define boundaries. It indicates how many affected items may be shipped, used, processed, or accepted under the concession. It does not, by itself, describe the technical deviation, the reason for acceptance, or the disposition decision criteria. Those details are usually recorded elsewhere in the concession or related quality records.

    How it is used in operations

    In practice, concession volume may appear as a count of pieces, batches, serial-numbered units, lots, or another controlled quantity measure. The exact unit depends on how the product is identified and controlled in the organization.

    • For discrete manufacturing, it may be the number of parts or assemblies covered.

    • For lot-controlled material, it may be a lot, batch, or a defined subset of that lot.

    • For serialized products, it may refer to specific serial numbers rather than a general count.

    Systems such as QMS, MES, or ERP may reference concession volume when tracking nonconforming product, release decisions, genealogy, and downstream use restrictions.

    What it includes and excludes

    Concession volume includes only the quantity explicitly authorized by the approved concession. It does not automatically extend to future production, similar parts, or additional nonconforming units unless those are also documented and approved.

    It also should not be confused with broader production volume, shipment volume, rework volume, or scrap volume. The term is limited to the quantity within the approved scope of concession treatment.

    Common confusion

    Concession volume is often confused with concession rate or concession frequency. Concession volume is the amount of product covered by a specific concession, while concession rate refers to how often concessions occur or what share of output they represent.

    It can also be confused with deviation quantity. In some organizations the terms are used similarly, but a deviation often refers to permission before manufacture or processing, while a concession commonly refers to acceptance of a known nonconformance after it exists. Usage varies by company and industry.

    Example

    If 25 parts in a lot have a minor documented nonconformance and quality approval allows those 25 specific parts to be accepted for use, the concession volume is 25 parts, not the full lot unless the full lot is explicitly included.

  • Mapping table

    A mapping table is a structured list that shows how one set of values, fields, identifiers, or codes corresponds to another set. In manufacturing and enterprise systems, it commonly refers to configuration or reference data used to translate information between applications, data models, or process steps.

    A mapping table can be as simple as linking an ERP item code to an MES material identifier, or as detailed as converting defect codes, unit-of-measure values, work center names, status codes, or supplier IDs across systems. It is used to support consistent data exchange, reporting, and system interoperability.

    What it includes

    • Field-to-field relationships between systems

    • Code translations, such as status, reason, defect, or location codes

    • Value normalization rules, such as standard names or approved abbreviations

    • Cross-reference records used in integrations, migrations, or reporting layers

    What it does not mean

    A mapping table is not the same thing as the integration logic itself. It usually holds the reference relationships that the integration, ETL process, middleware, MES, ERP, or analytics layer uses. It is also not necessarily a full data model, master data record, or transaction history.

    Operational meaning in manufacturing systems

    In regulated and multi-system environments, mapping tables often appear wherever data must stay aligned across MES, ERP, PLM, QMS, LIMS, or warehouse systems. Examples include mapping part revisions between PLM and ERP, associating shop-floor equipment IDs with enterprise asset records, or translating nonconformance codes into reporting categories.

    Because mapping tables influence how records are interpreted, they are often treated as controlled configuration data. Changes to them can affect traceability, reporting consistency, interface behavior, and downstream business rules.

    Common confusion

    Mapping tables are commonly confused with lookup tables, crosswalks, and master data:

    • Lookup table: usually provides allowed values or descriptive labels within one system.

    • Crosswalk: often means a direct correspondence list between two coding schemes and may be used as a synonym for mapping table.

    • Master data: is the authoritative business data itself, while a mapping table links or translates between representations of that data.

  • Labeling

    Labeling commonly refers to the process of creating, approving, printing, and applying identifiers or required information to materials, components, finished goods, samples, containers, and shipping units. In manufacturing and regulated operations, a label is not just a sticker or printed tag. It is a controlled carrier of information used to identify an item, communicate status, support handling, and maintain traceability.

    Depending on the operation, labeling can include human-readable text, barcodes, 2D codes, serial numbers, lot or batch numbers, part numbers, revision levels, dates, storage conditions, quality status, and shipping data. The term can apply to both physical labels and directly marked identifiers when they serve the same operational purpose.

    What it includes

    • Item, material, lot, batch, or serial identification
    • Status labels such as quarantine, accepted, rejected, or in-process
    • Packaging and shipping labels
    • Work-in-process and kitting labels
    • Labels generated from ERP, MES, WMS, LIMS, or quality systems
    • Controlled templates, approval logic, and print records where used

    What it does not mean

    Labeling does not usually mean product branding, marketing design, or consumer-facing package artwork unless the discussion is specifically about commercial packaging operations. In industrial settings, the term usually refers to operational identification and traceability rather than promotional labeling.

    Operational meaning

    In day-to-day workflows, labeling appears at receiving, inventory moves, production issue, kitting, work order execution, inspection, nonconformance handling, packaging, and shipment. A labeling process may pull master and transaction data from business or shop-floor systems so that the label reflects the current item identity and status. Because labels often drive scanning and downstream decisions, errors in labeling can affect traceability, inventory accuracy, routing, and release controls.

    For example, a lot label on raw material may link the received material to supplier data and inspection status, while a finished-goods label may carry serial, revision, and shipment information needed by downstream systems.

    Common confusion

    Labeling is often confused with marking, identification, and packaging.

    • Labeling usually means applying a separate information carrier such as a printed label or tag.
    • Marking often refers to direct identification placed on the item itself, such as laser etching or ink marking.
    • Identification is broader and includes any method used to distinguish an item, whether by label, mark, record, or system reference.
    • Packaging refers to the physical containment or protection of goods, while labeling communicates information on or with that package.

    Why it matters in regulated manufacturing

    In regulated and quality-controlled environments, labeling is commonly tied to document control, revision management, approved data sources, and traceability records. The exact content and control level vary by industry, process, and product risk, but the general purpose remains consistent: to ensure the right item carries the right information at the right point in the workflow.

  • Formula versioning

    Formula versioning is the controlled tracking and management of changes to a manufacturing formula over time. A formula version identifies a specific approved or recorded state of a recipe, blend, bill of ingredients, or process formula so the organization can distinguish one definition from another.

    In manufacturing, this commonly includes changes to ingredient or material quantities, units of measure, processing parameters, yield assumptions, substitutions, specifications, effective dates, and approval status. It may also include links to related records such as work instructions, quality documents, ERP or MES master data, and change control records.

    Formula versioning is not the same as simply overwriting a formula master record. The key distinction is that prior states remain identifiable, and each version can be tied to when it was created, who changed it, why it changed, and where it was used. In regulated or traceability-sensitive environments, this supports consistent execution, review, and historical reconstruction.

    How it appears in operations

    Formula versioning often appears in ERP, MES, LIMS, PLM, or quality systems as version numbers, revisions, effective dates, status labels, and approval workflows. For example, a plant may release a new formula version for a coating mix with an updated solvent ratio while keeping the prior version available for historical batch records and investigation.

    • Current version: the formula presently released for use
    • Pending version: a change under review or not yet effective
    • Obsolete or retired version: no longer released for execution but retained for history
    • Effective dating: controls when a version may be used in production

    What it includes and excludes

    Formula versioning commonly refers to the version control of product formulations or process formulas used to manufacture a material or product. It may apply to discrete, batch, and process manufacturing, especially where composition matters.

    It does not usually mean versioning of every related document or every production instruction, although those items may be governed alongside the formula. A formula version can be linked to document revisions, but it is not identical to document control in general.

    Common confusion

    Formula versioning vs. recipe versioning: These terms are sometimes used interchangeably, but they are not always identical. A formula usually focuses on composition or material relationships, while a recipe may also include sequence, timing, equipment steps, and execution logic.

    Formula versioning vs. BOM revision: A bill of materials revision is usually associated with product structure in discrete manufacturing. A formula version is more often used where proportions, yields, or batch scaling are central.

    Formula versioning vs. document revision control: Document revision control manages files such as SOPs or specifications. Formula versioning manages the manufacturing definition itself, even when related documents are attached.

  • Transition period

    A transition period is a defined span of time during which an organization, process, system, or controlled activity moves from one state to another. In industrial and regulated environments, it commonly refers to the interval used to shift from an old method, version, supplier, equipment state, or compliance approach to a new one while maintaining continuity of operations and records.

    The term describes the time window itself, not the final target state and not the detailed plan used to get there. A transition period may be formal, with documented start and end conditions, or informal, but in controlled environments it is often tied to approvals, effective dates, training completion, document revisions, system cutover steps, or inventory depletion.

    How it appears in operations

    In manufacturing and quality workflows, a transition period may apply to:

    • changeover from one work instruction revision to another
    • migration from paper records to electronic records
    • cutover from a legacy MES, ERP, or quality system to a new platform
    • introduction of a new supplier, material, or process routing
    • phased enforcement of updated internal procedures or customer requirements

    During this interval, both old and new states may coexist under defined controls. For example, a plant may allow existing inventory labeled to an earlier specification to be consumed until a stated date while all newly released work orders use the updated revision.

    What it includes and excludes

    A transition period commonly includes timing boundaries, interim rules, and criteria for when the old state is no longer allowed. It may also include temporary controls such as dual documentation, added review steps, or restricted user access during a system rollout.

    It does not necessarily mean a shutdown, a maintenance outage, or a probationary period for personnel. It is also not the same as the change request, validation package, or project plan, although those may define or govern the transition period.

    Common confusion

    Transition period is often confused with implementation period. The implementation period is the time used to put a change in place, while the transition period focuses on the managed overlap or shift from old to new.

    It is also sometimes confused with grace period. A grace period usually emphasizes temporary tolerance after a deadline, while a transition period is broader and usually includes the controlled move before full adoption.

    In quality and compliance discussions, it can overlap with terms like effective date, cutover window, and phase-in period, but those are narrower. An effective date is a point in time, a cutover window is usually a short technical switchover interval, and a phase-in period emphasizes gradual adoption.

  • Shadow mode

    Shadow mode commonly refers to operating a new system, application, model, rule set, or workflow in parallel with a live production process while preventing it from directly affecting real-world outcomes. It allows the new logic to observe the same inputs as the active system and produce outputs for comparison, validation, or monitoring, but those outputs are not used to control equipment, release transactions, or make official process decisions.

    In manufacturing and regulated operations, shadow mode is often used when introducing analytics, scheduling logic, alerting rules, inspection models, MES changes, or integrations between OT and IT systems. For example, a new downtime-classification model might process live machine events and generate classifications in the background while the current reporting method remains the official source.

    What it includes

    • Parallel processing of live or near-live data
    • Output generation for comparison, testing, or performance evaluation
    • Isolation from production actions such as equipment control, inventory updates, quality disposition, or official record changes
    • Use during rollout, validation, tuning, or migration activities

    What it does not mean

    Shadow mode does not usually mean that a system is partially controlling production. If the new system can directly trigger actions, write to the system of record, or change operator instructions in effect, it is generally no longer operating only in shadow mode. It is also not the same as a software sandbox with synthetic data, because shadow mode typically uses real operational inputs.

    Common confusion

    Shadow mode is commonly confused with pilot, simulation, and parallel run.

    • Pilot: a limited live deployment where the new system may actually be used in production for a subset of lines, users, or processes.
    • Simulation: testing with modeled or historical data rather than live production inputs.
    • Parallel run: can mean two systems are both active for business continuity, and in some organizations both may influence operations. Shadow mode usually implies the new side is non-controlling.

    Operational relevance

    In plant and enterprise systems, shadow mode is used to compare outputs before cutover, measure variance from current logic, detect data-mapping issues, and understand whether a new process would behave acceptably under real conditions. It can apply to MES workflows, ERP integrations, quality event classification, predictive maintenance alerts, scheduling recommendations, and other decision-support or execution-adjacent functions.

    Because definitions vary by team, organizations often document exactly what is shadowed, what data is read, what outputs are stored, and which systems remain authoritative during the shadow period.