Glossary Tag: leading indicators

  • WIP exposure

    WIP exposure commonly refers to the amount of operational, quality, scheduling, and financial risk tied to work-in-process inventory, meaning material, assemblies, or jobs that have started production but are not yet complete. It is not simply the same as WIP volume. The term focuses on how much unfinished work is at risk of delay, rework, scrap, obsolescence, handling loss, or reporting distortion if conditions change.

    In manufacturing, WIP exposure is often discussed when teams want to understand how much partially completed product is tied up between steps, across long cycle times, or at bottleneck operations. Higher exposure can mean more material and labor are committed before a product is finished, inspected, shipped, or converted into recognized output.

    What it includes

    • Partially completed units or batches on the shop floor

    • Open jobs waiting at queues, bottlenecks, or outside processing steps

    • Accumulated labor and material already applied to unfinished work

    • Risk of quality issues spreading across multiple in-process units before detection

    • Schedule and capacity risk caused by blocked or aging WIP

    Depending on the organization, the term may be used in a mainly financial sense, a mainly operational sense, or both.

    What it does not mean

    WIP exposure does not usually mean finished goods inventory, raw material on hand, or a formal accounting valuation by itself. It also does not automatically indicate nonconformance. It is a way to describe how much unfinished work is currently vulnerable to disruption or loss.

    How it appears in systems and workflows

    In ERP, MES, and production reporting, WIP exposure may be inferred from open work orders, queue lengths, aging lots, partially issued material, incomplete routings, or jobs with significant cost posted before completion. Teams may track it by line, work center, product family, batch, or program to understand where unfinished work is accumulating.

    For example, if many assemblies have completed early routing steps but are waiting on a constrained inspection resource, the plant may describe that condition as increased WIP exposure at that point in the process.

    Common confusion

    WIP exposure vs. WIP inventory: WIP inventory is the unfinished work itself. WIP exposure emphasizes the associated risk or value at risk.

    WIP exposure vs. throughput: Throughput measures completed output over time. WIP exposure concerns unfinished output still in process.

    WIP exposure vs. inventory turns: Inventory turns are a broader inventory efficiency metric. WIP exposure is narrower and focused on in-process work.

  • Cp

    Cp is a process capability index used in statistical process control and quality engineering. It commonly refers to the ratio between the allowed specification width and the natural spread of a process, typically estimated as six standard deviations.

    In practical terms, Cp indicates the potential capability of a process to fit within upper and lower specification limits if the process is stable and centered between those limits. A higher Cp value means the process variation is small relative to the tolerance range.

    Cp does not show whether the process average is actually centered on target. Because of that, it does not by itself describe the actual defect risk when the process mean is shifted. For that reason, Cp is often reviewed alongside Cpk, which accounts for centering.

    What Cp includes and excludes

    • Includes: comparison of process variation to specification limits.
    • Assumes: a reasonably stable process and a meaningful estimate of variation.
    • Excludes: process centering, special-cause instability, and broader system issues such as measurement error unless those are addressed separately.

    How it appears in manufacturing

    Cp is commonly used for critical dimensions, fill volumes, torque values, temperature-controlled steps, and other measurable characteristics in production and quality workflows. It may appear in SPC software, MES-connected quality records, capability studies, control plans, supplier quality reviews, and continuous improvement reporting.

    For example, a machining process may show a high Cp for a diameter tolerance, meaning the observed variation is narrow compared with the specification band. If the process mean drifts toward one limit, however, actual performance may still be unacceptable even though Cp remains high.

    Common confusion

    Cp vs. Cpk: Cp measures potential capability based on spread only. Cpk measures capability while also considering how centered the process is within the specification limits.

    Cp vs. Pp: Cp is commonly associated with short-term or within-process variation in a stable process. Pp commonly uses overall performance variation across a broader time window.

    Cp vs. control limits: Cp uses specification limits set by design or customer requirements, not control limits calculated from process behavior.

  • Governance artifacts

    Governance artifacts commonly refers to the documented items used to define, authorize, monitor, and evidence how a process, system, or organization is controlled. In industrial and regulated environments, these artifacts often include policies, procedures, standards, work instructions, approval records, risk assessments, change records, access reviews, training records, and audit evidence.

    The term includes both the content that sets expectations and the records that show those expectations were reviewed, approved, communicated, or followed. It does not usually refer to the operational transaction itself, such as a production order or machine event, unless that record is being used as formal control evidence.

    How the term is used in operations

    In practice, governance artifacts appear across quality systems, IT and OT change control, document management, training administration, supplier oversight, and system validation activities. They are the materials people use to answer questions such as:

    • What rule or requirement applies?
    • Who approved it and when?
    • What version was in effect?
    • What evidence shows the control was executed?

    For example, a controlled SOP, its revision history, the approval workflow, and the training acknowledgement tied to that SOP can all be considered governance artifacts.

    What governance artifacts typically include

    • Policies and standards
    • Procedures and work instructions
    • Templates and controlled forms
    • Approval and review records
    • Risk assessments and mitigation records
    • Change requests and change impact assessments
    • Role definitions, access matrices, and segregation of duties records
    • Training completion records
    • Audit logs, exception records, and investigation documentation

    Common confusion

    Governance artifacts are often confused with general documentation. Not all documentation is a governance artifact. A casual note, draft analysis, or informal email may support work, but it is not usually treated as a governance artifact unless it is part of a defined control process.

    The term is also sometimes confused with master data or transactional data. Master data defines business objects such as parts, suppliers, or equipment. Transactional data records events such as production, inspection, or shipment. Governance artifacts instead focus on the rules, approvals, and evidence used to control those activities.

    Why the distinction matters

    In manufacturing systems, governance artifacts help maintain document control, version governance, traceability of decisions, and evidence trails across MES, ERP, QMS, and related platforms. They support controlled operations, but they are not the same as the control mechanism itself.

  • Supplier Approval

    Supplier approval commonly refers to the documented process used to evaluate, qualify, and authorize a supplier to provide specific materials, components, services, or outsourced operations. In regulated and quality-sensitive manufacturing, it usually includes checks on the supplier’s capability, quality controls, documentation, and any requirements tied to the product, process, or customer.

    It is not simply adding a company to a vendor list for purchasing convenience. Supplier approval is narrower and more controlled: a supplier may be approved only for certain part families, processes, sites, or service types, and that approval may be conditional, time-limited, or subject to ongoing review.

    What it typically includes

    • initial evaluation of the supplier’s capabilities and scope

    • review of quality records, certifications, questionnaires, or audit results where applicable

    • assessment of process controls, traceability, and documentation practices

    • formal decision to approve, conditionally approve, or reject the supplier for a defined scope

    • maintenance of an approved supplier list or equivalent master record

    • periodic re-evaluation based on performance, changes, or risk

    How it appears in operations and systems

    Operationally, supplier approval often connects purchasing, quality, engineering, and supplier management workflows. It may appear in ERP, QMS, SRM, or supplier portal processes as approval status, approved supplier lists, qualification records, required documents, performance history, and reapproval triggers. For example, a buyer may be blocked from issuing a purchase order for a special process unless the supplier is approved for that exact service.

    Common confusion

    Supplier approval is often confused with supplier onboarding, vendor setup, and supplier qualification.

    • Supplier onboarding usually covers administrative setup such as tax, payment, and contact data.

    • Vendor setup often means creating the supplier record in an ERP or procurement system.

    • Supplier qualification is sometimes used interchangeably, but in many organizations it refers more specifically to the assessment phase before formal approval.

    • Supplier certification generally implies a separate formal designation or external status and should not be assumed from approval alone.

    Manufacturing context

    In manufacturing, supplier approval is especially relevant for raw materials, critical components, calibration providers, contract manufacturers, and outside processing such as plating, heat treatment, or nondestructive testing. The level of review commonly varies with risk, product criticality, regulatory expectations, and customer requirements.

  • Maturity assessment

    A maturity assessment is a structured evaluation of how developed, repeatable, controlled, and measurable a process, system, function, or organizational capability is. In manufacturing and regulated operations, it commonly refers to reviewing current practices against a defined set of maturity levels, criteria, or capabilities rather than checking whether a single requirement is simply met or not met.

    The term usually includes an appraisal of process definition, execution consistency, governance, data quality, roles, documentation, integration, and performance monitoring. It can be applied to areas such as quality management, MES usage, digital work instructions, cybersecurity, maintenance, supplier management, or ERP and shop floor integration.

    A maturity assessment is not the same as a certification, formal audit result, or pass/fail compliance determination. It is generally a diagnostic tool used to describe the current state and identify gaps between ad hoc practice and more standardized or optimized operation.

    How it is used in operations

    In practice, a maturity assessment often looks at whether work is informal or documented, whether execution varies by shift or site, whether records are complete and traceable, and whether systems are integrated or reliant on manual workarounds. Results are commonly summarized by capability area and maturity level, with examples of observed strengths, weaknesses, or dependencies.

    • Example: assessing whether nonconformance handling is paper-based, partially digital, or fully integrated with quality records and corrective action workflows.
    • Example: assessing whether production instructions are tribal knowledge, controlled documents, or role-based digital work instructions tied to execution data.

    Common confusion

    Maturity assessment vs. audit: An audit compares evidence against specific requirements or internal procedures. A maturity assessment compares current capability against a progression model or operating-state framework.

    Maturity assessment vs. gap assessment: A gap assessment focuses on what is missing relative to a target state or requirement set. A maturity assessment usually goes further by characterizing the degree of development across multiple levels.

    Maturity assessment vs. KPI review: KPI review looks at performance results. A maturity assessment looks at the underlying management system, practices, controls, and consistency that shape those results.

    What it typically includes and excludes

    It typically includes interviews, document review, workflow observation, scoring criteria, and comparison across functions, sites, or capability domains.

    It does not necessarily include detailed system validation, legal interpretation, or an official finding of compliance status unless those activities are separately defined.

  • layered process audit

    A layered process audit commonly refers to a structured, recurring check of whether defined process steps, standard work, and key controls are being followed on the shop floor or in operational support processes. The “layered” part means the audit is performed by different levels of the organization, such as team leads, supervisors, managers, and sometimes quality or plant leadership, using aligned audit questions at different frequencies.

    In manufacturing, the term usually applies to routine verification of process discipline rather than a one-time system audit. It focuses on whether critical operating conditions are present and sustained, for example whether the right work instruction is in use, required checks are completed, tools are set correctly, materials are identified properly, and escalation steps are followed when something is out of condition.

    What it includes

    • Brief, repeated audits tied to a process, line, cell, area, or support function

    • Standardized questions or check points based on process risks or known failure modes

    • Participation by multiple management layers with defined cadence

    • Documentation of findings, follow-up actions, and closure status

    • Use as an operational control to detect drift from standard work

    It does not usually mean a financial audit, a certification audit, or a full quality management system audit. It is narrower and more operational than those activities.

    How it appears in workflows and systems

    Layered process audits may be managed on paper, in spreadsheets, or in MES, QMS, mobile audit, or digital work instruction platforms. In digital environments, an LPA program often includes scheduled audit tasks, role-based assignments, evidence capture, timestamps, exception logging, and action tracking. Results may also be reviewed alongside nonconformance, CAPA, scrap, rework, or training records to identify recurring process weaknesses.

    Common confusion

    Layered process audit is often confused with product inspection. They are related but not the same. Product inspection checks whether the output meets requirements. A layered process audit checks whether the process conditions and behaviors intended to produce conforming output are actually being followed.

    It is also commonly confused with an internal quality audit. An internal audit typically reviews broader system conformance, procedures, or compliance against an audit scope. A layered process audit is usually shorter, more frequent, and focused on day-to-day execution at the point of use.

    Manufacturing example

    On an assembly line, an operator lead might verify each shift that the current work instruction revision is posted and torque checks are recorded. A supervisor might review the same area daily for material identification and reaction-plan compliance. A manager might audit weekly for sustained adherence and closure of prior findings. Together, those checks form the layered approach.

  • supplier performance rating

    A supplier performance rating is a structured assessment of how well a supplier performs against defined business and operational criteria. In manufacturing, it commonly refers to a score, ranking, or status based on measures such as on-time delivery, product quality, responsiveness, documentation accuracy, and adherence to purchasing or quality requirements.

    The term is often used in procurement, supplier quality, ERP, and supplier management workflows. Ratings may be calculated from scorecards, incoming inspection results, nonconformance data, corrective action history, lead-time performance, and service levels. Some organizations express the result as a numeric score, while others use classes such as approved, conditional, preferred, or probationary.

    Supplier performance rating is broader than a single KPI. It is not limited to on-time delivery or defect rate alone, and it is not the same as formal supplier qualification or certification. In practice, it helps compare suppliers, monitor risk, and support sourcing, corrective action, and supplier development decisions.