Connect981 – Content Dev

Glossary Tag: leading indicators

  • OTD (On-time Delivery)

    OTD (On-time Delivery) commonly refers to a performance measure showing how often a supplier, production operation, or logistics process delivers an order, job, or shipment on or before its committed due date. It is typically expressed as a percentage over a defined period.

    In manufacturing and supply chain operations, OTD is used to track schedule reliability rather than product quality, cost, or overall throughput. It applies to internal production orders, customer shipments, supplier deliveries, repair turnarounds, and other commitment-based workflows where a promised delivery date exists.

    How it is used in operations

    OTD is commonly monitored in ERP, MES, planning, shipping, and supplier management processes. For example, a manufacturer may track whether finished goods shipped to the customer by the requested date, or whether a supplier delivered material in time to support a work order release.

    The exact calculation can vary by organization. Common variations include whether early deliveries count as on time, whether partial shipments qualify, which date field is authoritative, and whether the metric is based on lines, orders, quantities, or value. Because of this, OTD should be interpreted together with the local business rule used to calculate it.

    What OTD includes and excludes

    • Includes delivery performance against a defined commitment date.

    • May include customer orders, purchase orders, production jobs, service events, or repair completions.

    • Does not by itself measure conformance, yield, cost, or completeness unless those are explicitly built into the metric definition.

    • Does not explain why a delivery was late. Root causes may come from planning, shortages, capacity constraints, rework, logistics, or data issues.

    Common confusion

    OTD is often confused with OTP (On-time Performance), OTR (On-time Release), and OEE. These are not the same. OTD focuses on meeting a delivery commitment. OEE measures equipment effectiveness. A process can have high OEE and still miss OTD if planning, materials, quality holds, or downstream constraints delay shipment.

    OTD is also sometimes confused with OTIF (On Time In Full). OTIF is narrower and usually requires both timeliness and complete fulfillment. OTD may count a delivery as on time even when the shipment is partial, depending on the local definition.

    Manufacturing example

    If a supplier is expected to deliver machined parts by Friday and the shipment arrives Friday under the agreed rule, that order may count as on time for OTD. If it arrives Monday, it would typically count as late, even if the parts meet all quality requirements.

  • OEE (Overall Equipment Effectiveness)

    OEE (Overall Equipment Effectiveness) is a manufacturing performance metric used to describe how effectively a machine, line, or other production asset is being used during planned production time. It commonly combines three factors: availability, performance, and quality.

    In practical terms, OEE is used to show the gap between actual productive output and the output that would be achieved if the process ran as planned, at the intended rate, with only good units produced. It is a measurement framework, not a machine setting, maintenance method, or quality standard.

    What OEE includes

    • Availability: whether the equipment was running when it was supposed to be running, accounting for downtime and stoppages.
    • Performance: whether the equipment ran at its expected speed or cycle rate while it was operating.
    • Quality: whether the units produced met acceptance criteria without scrap or rework being counted as good output.

    These factors are often multiplied together to produce a percentage or index for a defined asset, line, product family, shift, or reporting period.

    How it is used in operations

    OEE commonly appears in MES, SCADA, historian, or production reporting systems as a KPI for equipment and line performance. Teams may use it to review downtime losses, speed losses, and quality losses by shift, order, work center, or product. In regulated or traceable environments, the underlying data often comes from production events, machine states, counts, and quality dispositions recorded in connected systems.

    Because OEE depends on how planned production time, ideal cycle time, and good count are defined, organizations often document calculation rules so results are consistent across assets and sites.

    What OEE does not mean

    OEE does not, by itself, explain why performance was low. It is a summary metric, not a root cause analysis method. It also does not directly measure schedule adherence, labor efficiency, overall plant profitability, or asset health, although those may be analyzed alongside it.

    OEE is also not the same as utilization in the broad financial sense. A machine can show low OEE because of speed loss or quality loss even if it appears heavily used.

    Common confusion

    OEE vs utilization: utilization usually focuses on how much an asset is used over time, while OEE focuses on productive effectiveness during planned production time.

    OEE vs throughput: throughput measures output volume over time; OEE reflects losses that reduce effective output.

    OEE vs TEEP: TEEP extends the concept to all calendar time, not just planned production time.

    OEE vs maintenance metrics: measures such as MTBF or MTTR focus on reliability and repair behavior, while OEE is a broader production effectiveness metric.

  • Global KPI

    A global KPI is a key performance indicator defined at an enterprise or multi-site level so it can be measured and compared consistently across plants, lines, departments, or business units. It commonly refers to a metric with a shared definition, calculation method, scope, and reporting logic.

    In manufacturing and regulated operations, a global KPI is used to create a common view of performance across distributed operations. Examples may include on-time delivery, scrap rate, first pass yield, schedule adherence, or overall equipment effectiveness when those measures are governed with the same business rules everywhere they are reported.

    A global KPI is not just any metric that appears on an executive dashboard. The term usually implies standardization. If each site calculates the metric differently, it may be a corporate report metric, but it is not functioning as a true global KPI.

    How it shows up in operations and systems

    Global KPIs often sit above local operational measures. They may be rolled up from MES, ERP, QMS, CMMS, historian, or reporting platforms and used in enterprise dashboards, review meetings, and cross-site performance analysis.

    • At the site level: teams collect and validate source data.

    • At the enterprise level: organizations apply common definitions and aggregation rules.

    • In governance: owners typically define who can change the formula, time basis, exclusions, and data source hierarchy.

    This helps distinguish a global KPI from a local KPI, which may be useful for a single process or facility but not suitable for enterprise comparison.

    What it includes and excludes

    A global KPI commonly includes:

    • a standard metric name and definition

    • a documented formula or calculation logic

    • defined scope, such as site, line, product family, or enterprise

    • consistent time periods and units of measure

    • rules for exceptions, exclusions, and rollups

    It does not automatically include the full operational context behind performance. Supporting drill-down metrics, event data, and local process indicators are usually still needed to explain why the KPI moved.

    Common confusion

    Global KPI vs local KPI: A local KPI is optimized for a specific process, team, or asset. A global KPI is standardized for enterprise-level consistency.

    KPI vs metric: A metric is any measurable value. A KPI is a metric considered important enough to track against business or operational objectives.

    Global KPI vs benchmark: A global KPI is an internally defined measure used across the organization. A benchmark is a reference point, often external or historical, used for comparison.

    Global KPI vs OEE: OEE is a specific performance metric. It can be a global KPI only if the organization standardizes how it is calculated and interpreted across sites.

  • process validation

    Core meaning

    Process validation commonly refers to the documented, systematic demonstration that a manufacturing or service process, when operated within defined parameters, can consistently produce outputs that meet predetermined specifications and quality attributes.

    In regulated manufacturing (such as pharmaceuticals, medical devices, and certain food or chemical sectors), process validation is a formal requirement and is closely linked to product quality, patient or user safety, and regulatory compliance.

    Key elements in industrial and regulated manufacturing

    Process validation typically includes:

    – **Defined process and inputs**: A clear description of the process steps, equipment, materials, and environmental conditions.
    – **Critical parameters and attributes**: Identification of critical process parameters (CPPs) and critical quality attributes (CQAs) that affect product quality.
    – **Planned studies and protocols**: A validation plan or protocol that defines the scope, methods, sampling, acceptance criteria, and responsibilities.
    – **Data collection across runs**: Execution of validation studies, often over multiple batches or lots, to demonstrate consistency and reproducibility.
    – **Analysis and justification**: Statistical and technical evaluation showing that the process is capable and under control.
    – **Documented conclusion**: A validation report or other records concluding whether the process is validated, including any conditions or limitations.

    Process validation is often supported by related activities such as equipment qualification, method validation, and ongoing process monitoring.

    Use in real workflows and systems

    In industrial operations, process validation is commonly applied to:

    – **Core manufacturing processes**: Mixing, filling, sterilization, assembly, coating, packaging, etc.
    – **Automated systems and OT/IT workflows**: Validating automated sequences controlled by PLCs, DCS, MES, or integrated MES–ERP workflows that influence product quality.
    – **Computerized systems (CSV/CSA context)**: While computer system validation focuses on software and systems, results feed into overall process validation when those systems control or record critical process steps.

    Data used for process validation may be generated and managed via MES, historians, LIMS, QMS, and ERP systems, and is subject to change control and configuration management.

    Boundaries and what process validation is not

    To reduce confusion, process validation:

    – **Is about the process**, not individual units or batches. It demonstrates that the process design and control strategy are capable, rather than merely testing outputs.
    – **Is not routine quality control**: QC tests verify that a specific batch meets requirements; process validation justifies that the underlying process can reliably produce conforming batches.
    – **Is broader than equipment qualification**: Equipment qualification (IQ/OQ/PQ) focuses on installation and operation of equipment; process validation covers the overall process using that equipment, including materials, methods, and controls.
    – **Is not limited to initial startup**: It often includes lifecycle activities such as revalidation, continuous verification, and periodic review when changes occur or performance shifts.

    Common stages and lifecycle view

    Many regulated environments describe process validation as a lifecycle that may include:

    – **Process design**: Defining the process, control strategy, and understanding sources of variability.
    – **Process qualification**: Confirming the process design at commercial or routine scale, often via a defined number of PPQ (process performance qualification) batches.
    – **Continued or ongoing process verification**: Monitoring the validated process during routine production to ensure it remains in a state of control.

    The specific terminology and required documentation vary by sector and regulator, but the lifecycle concept is broadly used.

    Relation to rework and repair (site context)

    In the context of rework and repair of nonconforming products:

    – **Rework** typically uses the original, approved manufacturing process or a pre-defined, validated variant. That means the rework process itself should be covered by process validation or equivalent documented studies.
    – **Repair** may involve ad hoc or limited-use modifications that do not fully restore original specifications. These activities may be controlled by different procedures and risk assessments and are not always treated as part of the validated manufacturing process.

    Thus, whether an activity is considered rework within a validated process, or a separate repair activity, can affect which validation, documentation, and approval requirements apply.

    Related terms and common confusion

    Process validation is often discussed alongside, but is distinct from:

    – **Method validation**: Demonstrating that an analytical or test method is suitable for its intended use.
    – **Computer system validation (CSV)** or **computer software assurance (CSA)**: Demonstrating that software and computerized systems are fit for intended use and operate as specified.
    – **Cleaning validation**: Demonstrating that a cleaning process consistently removes residues to an acceptable level.

    All of these may interact with process validation but address different scopes of risk and control.

  • Work In Process (WIP)

    Work In Process (WIP) commonly refers to all partially completed products within a manufacturing or industrial process that have started production operations but are not yet finished goods. WIP includes materials, subassemblies, and units currently being processed, queued between steps, or undergoing inspection or testing.

    Scope and what WIP includes

    In regulated and industrial environments, WIP typically includes:

    • Raw materials that have been issued to a work order or batch and had at least one value-adding operation performed
    • Parts or subassemblies located at workstations, in test cells, or between routing steps
    • Batches or lots in intermediate states, such as curing, cleaning, or environmental conditioning
    • Units on hold or under review that have not yet been scrapped or reclassified

    WIP usually excludes:

    • Unissued raw materials in warehouse or stockroom
    • Completed products that are in finished goods inventory or shipping
    • Tools, fixtures, and consumables that are not part of the bill of materials for the product

    WIP in systems and operations

    In manufacturing execution systems (MES), ERP, and other production IT/OT systems, WIP is represented as open work orders, batches, or units that have not yet reached a defined completion state. Typical operational representations include:

    • Open operations or routing steps on a work order or batch record
    • Units or lots with in-process status codes (for example: running, waiting, on-hold, under inspection)
    • Quantities physically located in production areas, test labs, cleanrooms, or outside processing

    WIP levels are often monitored for planning, capacity management, and compliance with internal procedures or industry standards. In regulated environments, WIP may require documented traceability, genealogy, and evidence of each processing step, including operator, equipment, materials, and test results.

    Financial and planning perspective

    From an accounting and planning viewpoint, Work In Process is a category of inventory that has accumulated direct materials, labor, and a portion of overhead but is not yet recorded as finished goods. It is used to:

    • Calculate inventory value and cost of goods manufactured
    • Support material requirements planning (MRP) and capacity planning
    • Analyze flow, lead time, and bottlenecks on the shop floor

    Common confusion and variants

    Work In Process vs. Work In Progress: In many manufacturing and industrial contexts, these terms are used interchangeably and both abbreviated as WIP. Some accounting practices use “Work In Process” for manufacturing and “Work In Progress” more broadly for long-term projects, but the distinction is not universal.

    WIP vs. finished goods: WIP covers items still in production, while finished goods are completed products ready for sale, shipment, or distribution.

    WIP vs. raw material inventory: Raw material inventory refers to materials not yet issued or processed. Once materials are issued to a job and processing begins, they typically become WIP.

    WIP in regulated and quality-focused environments

    In regulated manufacturing, managing WIP often involves:

    • Maintaining batch records or electronic device history records for in-process units
    • Tracking hold, rework, and deviation status at the unit, lot, or batch level
    • Ensuring traceability of materials, equipment, and process parameters during all in-process stages

    Operational controls on WIP, such as limits on in-process quantity or formal release steps between stages, are sometimes used to support consistent quality and audit readiness.

  • Pareto Analysis

    Pareto Analysis is a method for prioritizing issues, causes, defects, or cost drivers by ranking them from highest to lowest impact. It is commonly based on the Pareto principle, often summarized as the idea that a relatively small number of causes account for a large share of the effect.

    In manufacturing and quality contexts, Pareto Analysis is used to organize data such as defect types, downtime reasons, scrap causes, complaint categories, or nonconformance sources so teams can see which categories contribute the most. The output is often shown as a Pareto chart, which combines bars in descending order with a cumulative percentage line.

    Pareto Analysis does not by itself identify root cause, prove causation, or determine the correct corrective action. It is a prioritization and visibility tool. It helps answer which problems are most significant in the data, not why they occur.

    How it is used in operations

    Operationally, Pareto Analysis appears in continuous improvement, CAPA, NCR review, yield analysis, and production reporting. Teams may use it to compare:

    • top defect codes by frequency
    • largest scrap categories by cost
    • most common downtime reasons by minutes lost
    • highest-volume supplier nonconformance types

    The choice of measurement matters. A Pareto based on event count may lead to a different priority list than one based on cost, time lost, severity, or units affected.

    Common confusion

    Pareto Analysis is commonly confused with root cause analysis. Pareto Analysis ranks what matters most; root cause analysis investigates why it happens. It is also related to, but not the same as, a Pareto chart. The chart is the visual format, while the analysis is the underlying method of categorizing and prioritizing data.

    Example in manufacturing

    A plant may review one month of scrap data and find that three defect categories account for most total scrap cost. That result supports prioritization of improvement work, but further investigation is still needed to confirm process, material, training, or equipment causes.

  • warehouse management system

    Core meaning

    A warehouse management system (WMS) is specialized software used to control, execute, and track warehouse and distribution center operations. It manages how inventory is stored, moved, counted, and picked within one or more physical warehouse locations.

    A WMS commonly:

    – Maintains inventory records at detailed location levels (e.g., aisle, rack, bin)
    – Directs receiving, put-away, picking, packing, shipping, and internal transfers
    – Supports barcode/RFID scanning and mobile devices on the warehouse floor
    – Enforces warehouse rules such as FEFO/FIFO, lot rotation, or storage constraints
    – Records traceable stock movements (who moved what, where, when, and why)
    – Interfaces with higher-level systems such as ERP, MES, and transportation systems

    Use in manufacturing and regulated operations

    In industrial and regulated environments, a WMS is used to manage raw materials, intermediates, and finished goods across warehouses and staging areas. It typically:

    – Integrates with ERP for orders, material masters, and financial posting
    – Integrates with MES or production systems for material consumption and production receipts
    – Maintains lot/batch, serial, and sometimes status information (e.g., released, quarantined)
    – Provides transaction histories that support traceability and investigations
    – Supplies operational data for inventory accuracy KPIs and cycle counting performance

    In some plants, WMS functionality may be embedded within an ERP or MES rather than deployed as a standalone system.

    Boundaries and scope

    A WMS generally includes:

    – Physical inventory control and real-time stock visibility inside warehouses
    – Operational task management (e.g., work queues for pickers, put-away tasks)
    – Location and capacity management for storage areas

    A WMS typically does **not** include:

    – Enterprise-level planning (handled by ERP, APS, or planning tools)
    – Shop-floor process control or detailed production routing (handled by MES/SCADA)
    – Transportation planning and optimization beyond basic shipping interfaces (handled by TMS)

    Common confusion and related terms

    – **WMS vs. ERP:** An ERP system holds financial, purchasing, and high-level inventory data. A WMS handles the detailed, physical execution of warehouse operations and location-level movements. In some solutions, WMS is a module within ERP.
    – **WMS vs. inventory management:** General inventory management refers to policies, planning, and accounting for stock. A WMS is a specific software system that executes and records physical inventory movements and storage.
    – **WMS vs. MES:** MES focuses on production execution (work orders, process steps, equipment states). WMS focuses on warehouse and material storage operations, even when located near or inside the plant.

    Site-context application: inventory accuracy KPIs

    In the context of inventory accuracy and KPI reviews, the WMS is often the system of record for:

    – On-hand quantities at bin or location level
    – Historical movement transactions used to analyze discrepancies
    – Cycle count results and variance records

    Inventory accuracy KPIs (e.g., location accuracy, count accuracy, value accuracy) are usually derived from data maintained and time-stamped in the WMS and reconciled against ERP or financial systems.