Connect981 – Content Dev

RSC Topic: Operational Performance Metrics (OEE, NPT, COPQ)

KPI definition, measurement logic, and financial impact modeling.

first-pass yield

Core meaning

First-pass yield (FPY) is a quality and efficiency metric that measures the percentage of units that pass through a process correctly the first time, without requiring any rework, repair, or additional processing to meet specifications.

In simple terms, FPY answers the question: *Of everything we processed, how many met all requirements on their first pass through the defined process step or value stream?*

A common calculation is:

– **FPY = (Units exiting the process with no rework or repair) ÷ (Total units entering the process)**

FPY is typically expressed as a percentage.

Use in manufacturing and industrial operations

In manufacturing environments, FPY is commonly applied at multiple levels:

– **Workstation or operation level**: How many units pass a specific operation (e.g., soldering, filling, packaging) the first time without needing rework.
– **Line or area level**: First-pass performance for an entire line or work cell over a shift, day, or batch.
– **End-to-end process level**: First-pass performance from raw materials to finished goods, sometimes called rolled-throughput yield when compounded across steps.

Typical uses include:

– Monitoring process stability and capability over time.
– Comparing performance across lines, shifts, or products.
– Identifying where rework, scrap, and delays are being introduced.
– Supporting continuous improvement and root-cause investigations.

In regulated environments, FPY is often tied to documented inspection points, electronic batch records, or formal deviation and nonconformance processes.

Boundaries and what FPY is not

To avoid confusion, FPY is understood to:

– **Include only units meeting all defined acceptance criteria** on their first pass through the measured process segment.
– **Exclude units that needed any form of rework, repair, or re-inspection**, even if they eventually became good product.
– **Exclude scrapped units** from the numerator; scrap is counted in the denominator but not as first-pass good.

FPY is **not**:

– **Overall yield**: Overall yield usually counts good units after rework, repairs, and multiple passes.
– **OEE (Overall Equipment Effectiveness)**: OEE incorporates availability, performance, and quality; FPY focuses only on first-pass quality performance.
– **A defect rate metric by itself**: FPY may be complemented by defect rates, defect per million opportunities (DPMO), or similar measures to describe the type and severity of issues.

Relationship to MES and quality systems (site context)

In environments using a Manufacturing Execution System (MES) or similar shop-floor systems, FPY is often:

– **Calculated from real-time production and quality data** captured at each operation (e.g., pass/fail results, defect codes, hold/rework flags).
– **Segmented by product, batch, lot, or work order** for more detailed analysis.
– **Linked to rework and nonconformance records**, enabling traceability of where first-pass failures occur.

When MES enforces checks, data collection, and process controls, an initial decrease in reported FPY may occur as more defects are detected at the source rather than escaping downstream. Over time, FPY trends are frequently used to assess whether process corrections and corrective actions are effectively reducing rework and improving right-first-time performance.

Common confusion and related terms

Common points of confusion include:

– **First-pass yield vs. rolled throughput yield (RTY)**:
– FPY usually refers to a single process step or clearly defined segment.
– RTY multiplies FPY across multiple steps to show the cumulative probability that a unit passes the entire value stream without rework.
– **First-pass yield vs. final yield**:
– FPY counts only first-pass good units.
– Final yield reflects product that is conforming at the end of the process, including units recovered by rework.
– **First-pass yield vs. right-first-time (RFT)**:
– The concepts are closely related and sometimes used interchangeably.
– RFT is often used more broadly to indicate doing work correctly the first time across processes, while FPY is a specific quantitative metric.

Clarity about the process boundary (which steps are included), treatment of rework loops, and unit counting rules is important when comparing FPY across lines, plants, or systems.

March 25, 2026
cycle time

Core meaning

Cycle time commonly refers to the elapsed time needed to complete one unit of work, batch, or order from a clearly defined start point to a clearly defined end point in a process.

In industrial and manufacturing environments, cycle time is usually measured for:

– A single operation (e.g., time to fill and cap one bottle)
– A process segment (e.g., time from order release to finished lot on a specific line)
– An end‑to‑end flow (e.g., time from production order release to goods receipt in ERP)

Cycle time includes all time between the defined start and end, which may incorporate both value‑adding and non‑value‑adding time, depending on the definition used locally.

Usage in manufacturing and regulated environments

In regulated and complex plants, cycle time is often tracked at several levels:

– **Machine or operation cycle time**: Time to execute one machine cycle or unit operation, sometimes derived from PLC or MES event data.
– **Lot or batch cycle time**: Time from batch start (e.g., first material charged, order released) to batch end (e.g., last QC result approved, batch closed).
– **Order or work order cycle time**: Time from order release in the planning system (ERP/MES) to confirmation or goods receipt.

Cycle time is used to:

– Characterize process capability and stability
– Compare actual performance to routings, standards, or planning assumptions
– Support capacity analysis, debottlenecking, and scheduling models
– Provide inputs to inventory and safety stock calculations when combined with variability and reliability data

Boundaries and what cycle time is not

Because the term is used differently across disciplines, local definitions matter. Common distinctions include:

– **Cycle time vs. takt time**: Takt time is a target pace derived from customer demand; cycle time is the actual time the process takes per unit or batch.
– **Cycle time vs. lead time**: Lead time usually spans a broader order lifecycle, often from customer request to delivery, including waiting, planning, and logistics. Cycle time may be limited to manufacturing or a particular segment.
– **Cycle time vs. processing time**: Processing time may refer only to value‑adding time at a machine or workstation. Cycle time may include handling, minor waits, and transitions, depending on definition.

A rigorous use of the term always specifies:

– The **object** (unit, batch, order, operation)
– The **start event** (e.g., order release, first unit processed)
– The **end event** (e.g., QC release, last unit packed)

Common measurement approaches

In integrated OT/IT and MES environments, cycle time may be derived from:

– **Equipment signals and events**: Start/stop events, product counters, and state changes recorded by PLCs, SCADA, or equipment interfaces
– **MES records**: Operation start/finish, batch records, electronic work instructions, and operator log entries
– **ERP or planning systems**: Order release and confirmation timestamps when MES detail is not available

Cycle time is often analyzed as a distribution (average, variance, percentiles) rather than a single number, especially in regulated plants where changeovers, approvals, and testing can introduce variability.

Relation to safety stock and planning (site context)

In planning and inventory calculations, cycle time is one of several parameters used to characterize how long it takes to convert planned work into available stock. When actual cycle times are:

– **Longer or more variable** than assumed, they can justify higher safety stock levels.
– **Stable and predictable**, they can support lower buffers, provided that data quality, process reliability, and planning integration are strong.

MES and related shop‑floor systems often expose the true distribution of cycle times, which may reveal previously hidden variability and lead to adjustments in safety stock rather than immediate reductions.

Typical sources of confusion

Common points of confusion include:

– Using “cycle time,” “takt time,” and “lead time” interchangeably, which can obscure whether the discussion is about actual performance, customer‑driven demand pace, or total order duration.
– Failing to define start and end points, leading to inconsistent measurements across lines, shifts, or sites.
– Mixing **designed/standard cycle time** (used for planning and routings) with **actual measured cycle time** (from MES/OT data) without stating which is being referenced.

Clear documentation of scope and measurement rules is essential when cycle time is used in comparisons, KPIs, or regulatory submissions.

March 25, 2026
rework rate

Core meaning

Rework rate commonly refers to the proportion of production output that must be reprocessed in order to meet defined specifications or release criteria. It is typically expressed as a percentage or ratio over a defined volume or time period.

In manufacturing and industrial operations, rework rate usually measures:

– The number of units sent to rework divided by total units produced, or
– The amount of time, labor, or operations spent on rework divided by total time, labor, or operations for the product or line.

Rework in this context means additional processing performed on nonconforming or incomplete items to bring them back into compliance with requirements, without scrapping them.

Typical calculation approaches

Common ways to calculate rework rate include:

– **Unit-based rework rate**
(text{Rework rate} = frac{text{Units reworked}}{text{Total units produced}})

– **Operation or step-based rework rate**
(text{Rework rate} = frac{text{Rework operations or passes}}{text{Total operations or passes}})

– **Time- or effort-based rework rate**
(text{Rework rate} = frac{text{Rework hours}}{text{Total production hours}})

The exact definition used in a plant depends on how MES, ERP, and QMS systems capture nonconformance and routing data (for example, whether rework has explicit routes or is logged as additional passes on the same operation).

Use in industrial and regulated environments

In regulated or quality-critical manufacturing, rework rate is used to:

– Quantify how often products fail initial processing and must be corrected
– Characterize process capability and stability at line, work center, or product level
– Feed cost and performance models that distinguish between first-pass work and rework
– Support investigations into recurring nonconformances and process deviations

Rework rate is often tracked alongside scrap rate, first pass yield (FPY), and overall yield. Systems such as MES and QMS may record rework through specific rework orders, nonconformance records, or rework routing steps.

Boundaries and what it is not

Rework rate:

– **Includes**: Effort applied to previously produced units that did not initially meet requirements but are still recoverable.
– **Excludes**:
– Scrapped units that cannot be brought back into spec
– Planned multi-step routing that is part of normal processing (not correction)
– Routine adjustments or in-process tuning that is not triggered by product nonconformance

Rework rate does not, by itself, indicate cost, risk, or regulatory impact; those require additional data such as material cost, labor rates, batch impact, and documentation requirements.

Common confusion and related terms

Rework rate is frequently confused with:

– **Scrap rate** – measures the proportion of material or units that are discarded and not recovered. Scrap may occur instead of rework or after unsuccessful rework.
– **Repair rate** – sometimes used for field or post-delivery fixes. In some plants, “repair” is used for certain categories of rework, but repair can also refer to equipment maintenance, not product reprocessing.
– **Defect rate** – measures the frequency of defects detected; some defects are corrected through rework, others lead to scrap or deviation.

When defining KPIs or dashboards, it is important to distinguish:

– First-time nonconforming units that are recovered via rework
– Units that ultimately become scrap after attempted rework
– Units that pass on first attempt (for FPY metrics)

Site context: material waste and performance measurement

Within material waste and performance measurement, rework rate is one of the indicators used to understand how much production effort is spent correcting nonconforming output rather than producing conforming units the first time.

In integrated MES/ERP/QMS environments, rework rate may be:

– Calculated at part, line, batch, or plant level
– Segmented by cause (e.g., equipment, material, procedure) through nonconformance or deviation records
– Combined with cost data to quantify the impact of rework on material usage, labor, and capacity

In this context, rework rate is a key input to analyses that link yield losses and quality issues to actual cost and capacity constraints.

March 25, 2026
scrap rate

Core meaning

Scrap rate commonly refers to the proportion of material or units that are discarded (scrapped) during a manufacturing or industrial process, expressed as a ratio, percentage, or parts-per-million.

It typically compares a defined quantity of scrap to a defined production or consumption base, for example:

– **Scrap units / total units produced**
– **Scrap weight / total material input weight**
– **Scrap cost / total material cost**

The exact denominator and measurement basis are usually defined locally in plant procedures, KPIs, or MES/ERP reports.

Use in manufacturing and operations

In industrial and regulated environments, scrap rate is used to:

– Quantify material waste at part, batch, line, or plant level
– Monitor process capability and quality performance over time
– Compare performance across shifts, products, equipment, or suppliers
– Feed cost and variance calculations in ERP or finance systems

Operational systems (MES, SCADA, data historians) often capture scrap events by reason code (e.g., dimension out of spec, contamination, label error). Scrap rate may then be:

– Calculated in MES or data platforms for real-time dashboards
– Reconciled with ERP inventory and costing records
– Correlated with other KPIs such as yield, first pass yield, and rework rate

What scrap rate includes and excludes

Scrap rate typically **includes**:

– Nonconforming units or material that cannot be reworked or reused in the intended product
– Material lost due to defects, process errors, damage, or obsolescence
– In some definitions, unavoidable process loss that is systematically scrapped (e.g., trim, edge scrap), when it is tracked as scrap

Scrap rate typically **excludes**, unless explicitly defined otherwise:

– **Reworkable** units that are successfully repaired and accepted (these are usually reflected in rework or first pass yield metrics)
– Planned setup material or trial runs not counted as normal production
– Normal, allowed process consumption that is not tracked as scrap (e.g., purge, cleaning materials), unless a site defines them as scrap for KPI purposes

Because boundaries vary across plants, formal KPI definitions usually document:

– What counts as scrap
– What period, product set, and denominator are used
– Whether scrap is measured by count, weight, volume, or cost

Relation to yield, waste, and cost

Scrap rate is related but not identical to several other measures:

– **Yield**: Often defined as good output / total input. A high scrap rate usually implies lower yield, but yield may also be affected by rework and other losses.
– **Waste rate**: In some sites, includes scrap plus additional non-value-adding losses (e.g., energy waste, waiting time). Scrap rate focuses on discarded material or units.
– **Material cost of scrap**: Converts scrap quantities into monetary value for costing and profitability analysis.

In regulated industries, scrap rate may also tie into material traceability, batch record review, and deviation or nonconformance management.

Site context: material waste reduction KPIs

Within material waste reduction initiatives, scrap rate is commonly used alongside:

– **Rework rate** (portion of units requiring additional processing)
– **Yield or first pass yield** (portion of units meeting requirements without rework)
– **Scrap cost per unit or per batch** (financial view of waste)

Manufacturing and quality teams may track scrap rate at different levels (part, operation, routing step, line, plant) based on how well MES, ERP, and QMS systems are integrated and how precisely material movements and nonconformances are recorded.

Common confusion and misuse

Common points of confusion include:

– **Scrap rate vs. defect rate**: Defect rate may count any nonconformity found, including defects later reworked. Scrap rate normally counts only material that is ultimately discarded.
– **Scrap rate vs. yield**: Yield is a positive measure of good output; scrap rate is a negative measure of discarded material. They are related but not interchangeable.
– **Unit vs. cost basis**: A low scrap rate by unit count can still represent a high cost if high-value materials are scrapped. KPI definitions should clarify whether the rate is unit-, mass-, or cost-based.

Clear, documented definitions help ensure that scrap rate trends are comparable over time and across systems and reports.

March 25, 2026
KPI Mapping
KPI mapping is the structured process of linking key performance indicators (KPIs) to the underlying processes, systems, data sources, and organizational roles that create and influence those metrics. It is used to clarify what each KPI measures, where the data comes from, who owns it, and how it relates to operational and business objectives.

What KPI mapping includes

In industrial and manufacturing environments, KPI mapping commonly involves:
- Defining each KPI in precise terms, including calculation logic and units of measure
- Linking KPIs to specific processes, equipment, production lines, or value streams
- Identifying source systems for data (for example MES, ERP, LIMS, QMS, historians)
- Assigning data ownership and accountability for monitoring and maintenance
- Connecting KPIs to standards or models, such as ISA-95 levels or OEE components
- Documenting reporting frequency, aggregation level, and intended audience
Effective KPI mapping typically results in a documented map or catalog that shows how high-level business and quality objectives are supported by operational metrics collected on the shop floor and in supporting systems.

Operational context

In regulated manufacturing environments, KPI mapping often appears as part of:
- MES and ERP integration projects, to ensure consistent definitions across systems
- Operations intelligence and performance dashboards, to validate that each metric is traceable to reliable data
- Quality and compliance reporting, where audit trails and evidence for metrics need to be demonstrated
- Continuous improvement and lean initiatives, to align improvement actions with measurable outcomes
The mapping may be maintained as a controlled document or configuration record, especially when KPIs are used in regulated reports, product release decisions, or management reviews.

What KPI mapping is not
- It is not the same as selecting which KPIs to use, although KPI selection usually precedes mapping.
- It is not only a dashboard design activity; it focuses on the underlying logic and data lineage, not just visualization.
- It is not limited to financial metrics; it typically includes safety, quality, delivery, cost, and productivity KPIs.
Common confusion
- KPI mapping vs. process mapping: Process mapping describes how work flows. KPI mapping describes how performance is measured against that work, including data sources and calculations.
- KPI mapping vs. data mapping: Data mapping typically focuses on how fields align between systems. KPI mapping starts from the metric definition and traces back to the relevant data fields and processes.
March 24, 2026
performance ratio
Performance ratio commonly refers to a calculated indicator that compares actual performance to a defined reference value, typically expressed as a percentage or dimensionless number. In manufacturing and industrial operations, it is used to quantify how closely a process, asset, or organization is performing relative to a target, design point, or theoretical limit.

General meaning

A performance ratio is usually defined as:
- Actual result (e.g., produced quantity, achieved rate, realized output, or measured value)
- divided by a reference result (e.g., planned quantity, rated capacity, design rate, or baseline value)
- sometimes multiplied by 100 to express it as a percentage.
It is a derived measure, not raw sensor data. It becomes meaningful only once the reference and calculation rule are clearly defined and governed.

Use in manufacturing and operations

Within manufacturing systems, a performance ratio can be applied at different levels:
- Machine or line level: comparing actual output rate to the equipment’s rated speed, or actual energy use to a reference profile.
- Shift or order level: comparing produced good units to the planned quantity in a shift, or actual cycle time to standard cycle time.
- Plant or value stream level: comparing actual throughput, yield, or on-time performance to targets defined in planning or budgeting systems.
In MES and operations intelligence environments, performance ratios are often implemented as indicators or KPIs. For example, a system might compute a performance ratio for each production order to show whether it ran faster or slower than the defined standard.

Relationship to indicators and KPIs (ISO 22400 context)

In the context of ISO 22400 and similar standards, a performance ratio is a type of indicator derived from basic measurements (such as counts, times, or energy readings). Whether a given performance ratio is treated as a key performance indicator (KPI) depends on local modeling and governance. The same mathematical ratio might be an internal diagnostic indicator in one plant and a top-level KPI in another.

Examples
- Production rate performance ratio: actual units per hour divided by the standard units per hour for a product code.
- Schedule adherence ratio: actual completed quantity for an order divided by the planned quantity in the schedule.
- Energy performance ratio: actual energy used per batch divided by the reference energy use for that batch type.
Each example requires a clearly defined numerator, denominator, and calculation period. Different sites may calculate the same named ratio differently, so documentation and version control of the definition are important.

What it is not
- It is not a raw measurement like a single temperature reading or cycle count.
- It is not limited to any specific asset type or industry; it is a general comparison metric.
- It is not inherently standardized across organizations unless explicitly defined in a standard or internal specification.
Common confusion
- Performance ratio vs. OEE performance factor: In Overall Equipment Effectiveness (OEE), the “Performance” component is itself a specific kind of performance ratio relating actual speed to design speed. However, the term “performance ratio” is broader and may refer to many other comparisons that are not part of OEE.
- Performance ratio vs. yield or quality rate: Yield and first-pass yield are also ratios, but they usually compare good to total units. A performance ratio often compares actual to planned, rated, or theoretical values.
- Performance ratio vs. efficiency: Efficiency is sometimes used informally as a synonym, but in some disciplines “efficiency” has a stricter thermodynamic or energy meaning. When precision matters, it is better to use the locally defined term and formula.
Operational considerations

For reliable use of performance ratios in regulated or audited environments, organizations typically:
- Document the exact definition, including reference values and data sources.
- Manage changes to the formula or reference baselines under version control.
- Ensure that upstream raw data (counts, time stamps, sensor readings) are accurate and traceable.
March 24, 2026
cost of non-quality
Cost of non-quality commonly refers to the total cost a company incurs because products, processes, or services do not meet specified quality requirements. It focuses on the negative financial impact of defects, errors, and nonconformities, rather than on the base cost of doing work correctly the first time.

What it includes

In industrial and regulated manufacturing environments, cost of non-quality typically includes:
- Internal failure costs: Scrap, rework, re-inspection, troubleshooting, machine re-setup, and yield loss detected before product leaves the plant.
- External failure costs: Customer complaints, returns, field failures, service calls, warranty handling, product recalls, and concessions.
- Process deviation costs: Time and resources spent managing deviations, nonconformance reports, investigations, and corrective actions related to defects.
- Compliance and regulatory impacts: Additional testing, containment actions, extended reviews, and documentation work triggered by nonconforming product in regulated sectors.
- Indirect or hidden impacts: Unplanned downtime, production rescheduling, expedited shipments, extra inventory, and overtime linked directly to quality issues.
In many organizations, cost of non-quality is treated as the observable or measurable part of the broader “cost of poor quality” concept, used as a financial key performance indicator to track the impact of defects over time.

What it usually excludes

Cost of non-quality generally does not include:
- Planned costs for prevention and appraisal, such as training, audits, standard work development, and routine inspections (these are often categorized separately).
- Normal operating expenses not directly attributable to a failure or nonconformance.
- Intangible effects that are difficult to quantify, such as long-term brand damage, unless an organization chooses to estimate them explicitly.
How it is used operationally

Operationally, cost of non-quality is often calculated by linking quality events to financial data in systems such as MES, ERP, and quality management systems. Examples include:
- Capturing scrap and rework quantities at machines and multiplying by material and labor costs.
- Logging deviations and nonconformance records, then assigning time, resource, and material costs to each event.
- Aggregating warranty returns or complaint data from customer systems and applying standard cost models.
Plants may monitor cost of non-quality at different levels, such as per product family, line, shift, or supplier, and may report it as an absolute value or as a ratio to sales, output, or total manufacturing cost.

Relation to standards and KPI frameworks

In KPI frameworks for manufacturing, including those aligned with standards such as ISO 22400, cost of non-quality is often grouped under cost or quality-related performance indicators. It serves as a financial view of quality performance that can be compared alongside metrics like scrap rate, rework rate, or first-pass yield.

Common confusion
- Cost of non-quality vs. cost of poor quality (COPQ): Many organizations treat these terms as equivalent. Some, however, use “cost of non-quality” to emphasize direct, measurable failure costs, while “COPQ” may include a broader set of hidden or opportunity costs.
- Cost of non-quality vs. total quality cost: Total quality cost models include prevention, appraisal, and failure costs. Cost of non-quality typically focuses only on failure-related portions.
Derived from context

In the context of ISO 22400 KPI domains, cost of non-quality is a cost and efficiency metric that translates quality performance into financial impact. It is commonly used alongside utilization, throughput, and defect-related indicators to provide a more complete view of manufacturing performance.
March 24, 2026
Can I add domain-specific KPIs on top of ISO 22400 categories?
Yes. ISO 22400 is explicitly designed to be extendable, so you can add domain-specific KPIs as long as you keep a clear and traceable relationship to the standard categories and objects.

How to layer domain-specific KPIs on ISO 22400

In practice, most regulated and high-mix environments do not stop at the base ISO 22400 indicators. They:
- Use ISO 22400 KPI groups and objects (e.g., availability, performance, quality; equipment, order, material) as a common backbone.
- Define domain- or product-specific KPIs (e.g., “first-pass yield for titanium structural parts,” “batch right-first-time for sterile fill,” “NPT per engine program”).
- Map each custom KPI back to one or more ISO 22400 indicators and base measures where possible.
This mapping is important for comparability across plants, suppliers, and systems, and for explaining your metrics to auditors and customers.

Key constraints and risks

Simply adding more KPIs tends to create confusion unless you address these points explicitly:
- Definition control: Each domain-specific KPI needs a precise, version-controlled definition: scope, units, inclusions/exclusions, time basis, and data sources. Without this, discrepancies between MES, data warehouse, and local Excel calculations will accumulate.
- Double-counting and overlap: Custom KPIs often partially duplicate ISO 22400 ones. If you are not explicit about which KPI is the “authoritative” one for a decision, you can end up with conflicting numbers in management reviews.
- Traceability: For regulated environments, you should be able to trace a reported KPI value back to raw events and master data: which equipment, which production order, which time window, and which transformation logic.
- Change control: KPI formula changes, new filters, or data model changes should go through formal change control, especially when metrics drive release decisions, batch disposition, or capacity planning.
- Validation and testing: Where metrics are used in validated processes or electronic records, new KPIs and changes to them typically require documented testing and sometimes revalidation of MES, historian interfaces, and reporting tools.
Practical integration in brownfield environments

In mixed, legacy-heavy landscapes, adding domain-specific KPIs on top of ISO 22400 is feasible but rarely plug-and-play:
- MES and historian limits: Older MES or SCADA systems may not natively support ISO 22400 semantics. You can still implement the logic in a data warehouse or analytics layer, but you must be clear where the “system of record” for each KPI lives.
- Multiple calculation engines: Plants often have calculations in MES, historian, custom middleware, and BI tools. If you add a domain-specific KPI, decide where it is calculated and prevent alternative, unsanctioned versions in local spreadsheets.
- Long lifecycle assets: Some equipment or legacy interfaces cannot be changed easily without qualification or downtime. In those cases, you may need to compute both ISO 22400 and domain-specific KPIs externally, leaving the core control systems untouched.
- Avoiding full replacement: Attempting to replace all legacy KPI logic with a single new platform at once often fails due to downtime risk, integration complexity, and validation burden. Incremental layering on top of existing systems, with clear mapping to ISO 22400, is usually more realistic.
Suggested governance approach

A simple governance model makes domain-specific extensions workable:
- KPI catalog: Maintain a central catalog listing each KPI, whether it is ISO 22400-based or domain-specific, with owner, purpose, formula, and mapping to ISO 22400 indicators.
- Tiering: Separate global KPIs (based directly on ISO 22400) from domain/plant-specific ones to avoid endless debates about which number is “right” at corporate vs site level.
- Standard interfaces: Where possible, expose both standard and domain-specific KPIs via a common data model or API, even if the underlying systems are heterogeneous.
- Documentation for audits: Keep evidence of how KPIs are calculated, tested, and changed over time. This helps when auditors question why your internal metrics differ from generic OEE benchmarks.
In summary, adding domain-specific KPIs on top of ISO 22400 is not only allowed but often necessary. The value comes from disciplined definition, mapping, and governance so that extensions improve insight instead of increasing confusion.
March 24, 2026
Why is MRB cycle time a critical indicator of operational health?
MRB (Material Review Board) cycle time is critical because it connects quality, operations, supply chain, and engineering in one metric. It measures how long it takes to detect, evaluate, decide, and disposition nonconforming material. When that cycle is slow or erratic, it usually reflects deeper issues in operational discipline, system integration, and organizational alignment.

What MRB cycle time actually tells you

MRB cycle time is not just an administrative lag. It is a proxy for how well the organization can respond to quality events without destabilizing production or compromising compliance. Specifically, it indicates:

In practice, this connects to non-conformance management when teams need to turn the answer into repeatable execution habits.
- Speed of risk assessment: How quickly safety, regulatory, and reliability risks are identified, analyzed, and escalated.
- Effectiveness of cross-functional collaboration: How well quality, engineering, operations, and supply chain can converge on a decision.
- Data accessibility: How easily relevant drawings, specs, history, supplier data, and test results can be retrieved with appropriate traceability.
- Decision discipline: The consistency of criteria used for use-as-is, repair, rework, scrap, or return to supplier.
- System maturity: How well QMS, MES, ERP, PLM and document control systems support the MRB process rather than obstruct it.
Operational impacts of long or unstable MRB cycle times

When MRB cycle time is excessive or highly variable, it tends to show up in several operational pain points:
- Hidden WIP and inventory distortion: Nonconforming material often sits in limbo, physically on the floor but logically unusable. This obscures true WIP, inflates inventory, and complicates planning and MRP.
- Schedule and capacity risk: Late MRB decisions can strand work orders, delay builds, and force out-of-sequence work, increasing changeovers and setup waste.
- Firefighting and workarounds: Planners and supervisors may pressure for expedites or informal “pre-decisions,” creating variance from standard process and exposing audit risk.
- Rework loops and re-introduction errors: The longer material is in MRB, the higher the chance of misplacement, mislabeling, or reintroduction to the line without complete, traceable disposition.
- Supplier and customer friction: Slow MRB flow delays supplier feedback and chargebacks, and can ripple into missed customer commitments or late configuration changes.
Quality and compliance signals embedded in MRB cycle time

In regulated environments, MRB cycle time also reflects how robustly you manage traceability and documented decision-making:
- Traceable rationale: Short cycle times with good documentation suggest a mature process with clear acceptance criteria and accessible evidence. Short times with poor documentation are a red flag.
- Consistency of dispositions: Wide variability can indicate inconsistent risk tolerance between MRB members, plants, or shifts, which can be problematic under scrutiny.
- Audit resilience: Long queues, missing signatures, or backdated MRB closures often show up in audits as systemic issues rather than isolated events.
- Linkage to CAPA and root cause: If MRB is used purely for transactional decisions, with no linkage to CAPA or trend analysis, recurring issues will inflate both MRB volume and cycle time.
Why MRB cycle time is a better health metric than raw defect counts

Defect rates and nonconformance counts are important, but they can be misleading on their own. MRB cycle time adds critical context:
- Responsiveness vs. absolute quality: Even high-performing lines will have nonconformances. The question is how quickly and consistently they are handled without compromising safety or specs.
- System performance, not just process yield: MRB touches QMS, MES, ERP, PLM, document control, and sometimes LIMS or SPC. Cycle time reveals how well these systems and teams actually work together.
- Stability over time: Stable, predictable MRB timing supports planning and risk assessment. Volatile MRB timing forces buffers and contingency plans.
Typical drivers of poor MRB cycle time in brownfield environments

In mixed-system, long-lifecycle plants, MRB cycle time is often constrained by factors beyond the MRB team itself:
- Fragmented data sources: Drawings in PLM, routings in MES, supplier info in ERP, inspection data in QMS or spreadsheets, with no single view. Each MRB case becomes a manual data-gathering exercise.
- Manual and paper-heavy workflows: Physical MRB boards, paper tags, and wet signatures introduce delays, especially across shifts or buildings.
- Limited availability of decision-makers: MRB often depends on a few key engineers or quality leaders who are split across programs, plants, or time zones.
- Weak standard work: Ambiguous criteria for what goes to MRB vs what can be dispositioned locally, and no clear SLA targets by risk category.
- Tool replacement attempts: Full replacement of QMS or MES solely to “fix” MRB often stalls due to validation burden, integration complexity, and downtime risk, leaving process issues unresolved.
How to use MRB cycle time as a leading indicator

MRB cycle time becomes most useful when it is treated as a structured, risk-aware metric rather than a single aggregate number:
- Segment by risk and origin: Track MRB time for safety-critical vs cosmetic nonconformances, and by source (internal process, design, supplier). Expect different targets for each.
- Distinguish queue time from value-added time: Separate “waiting for data/decision” from actual evaluation work. Queue time is usually where systemic issues hide.
- Correlate with schedule and inventory impacts: Link MRB cases to affected work orders, customer orders, or lots to quantify how MRB timing influences OTIF, NPT, or COPQ.
- Tie to CAPA and continuous improvement: Persistent long MRB times for certain materials, programs, or suppliers should trigger structured root cause analysis, not just local firefighting.
Improving MRB cycle time without destabilizing the plant

In regulated, brownfield environments, improving MRB cycle time usually requires incremental, validated changes rather than wholesale system replacement:
- Clarify policies and thresholds: Define what must go to MRB vs what can be dispositioned under predefined local authority with clear criteria and documentation.
- Standardize MRB workflows: Document standard work, including required evidence, decision trees, and routing. Align it across sites where practical, while allowing for product-specific differences.
- Integrate data access first: Even light integration or shared views between QMS, MES, and PLM can significantly reduce hunt time for drawings, specs, and history, if properly validated and controlled.
- Define and monitor SLAs: Set target MRB times by risk category and track adherence, with clear escalation paths when cases exceed thresholds.
- Use pilots and phased rollout: Test workflow and integration changes on selected product families or lines before scaling, to manage validation, change control, and training.
When treated as a cross-functional performance metric, MRB cycle time provides a realistic view into the health of your operations, data flows, and decision-making discipline. Improving it sustainably requires attention to process design, system integration, and governance, not just new tools.
March 24, 2026
Which leading indicators should executives track weekly to prevent scrap from compounding into margin erosion?
Executives trying to prevent scrap from eroding margin should focus weekly reviews on a small set of leading indicators that expose quality drift and process instability before they appear in financials. The exact numbers and thresholds will be plant-specific, but the structure below is generally applicable in regulated, mixed-system environments.

1. First-pass yield on critical value streams

Rather than a global yield number, track first-pass yield (FPY) on the few value streams or product families that drive most contribution margin.

In practice, this connects to scrap and rework reduction when teams need to turn the answer into repeatable execution habits.
- Metric: FPY by value stream / product family / key line.
- Why it is leading: FPY deterioration often appears weeks before formal scrap write-offs hit the P&L.
- What to watch weekly:
  - Trend vs a 4–12 week baseline, not just week-over-week changes.
  - FPY for high-risk operations (special processes, tight tolerances, final assembly/test).
- Dependencies/risks: FPY reliability depends on how well rework loops are captured in MES/LIMS/QMS and whether inspection data is complete and timely.
2. Early defect signals and nonconforming material

Executives do not need every Pareto chart, but they do need early visibility into nonconformances before they become large scrap events.
- Metric: Count and rate of new nonconformances / defects opened, segmented by severity, operation, and source (in-process, final, customer, supplier).
- Why it is leading: Rising minor or in-process defects often precede major scrap or recalls.
- What to watch weekly:
  - New nonconformances per 1,000 units or per production hour on top-margin products.
  - Repeat issues by defect code, operation, or component over the last 4–8 weeks.
  - Defects emerging after process changes, new tooling, or new suppliers.
- Dependencies/risks: Requires consistent coding of nonconformances in QMS and linkage to lot/batch, operation, and part numbers. In many brownfield sites, this linkage is partial and will need improvement over time.
3. Rework and deviation usage

Rising rework and reliance on deviations or concessions are strong leading indicators that processes are operating out of control, even if scrap is temporarily contained.
- Metrics:
  - Rework rate (rework hours or quantity as a percentage of total production).
  - Number of active deviations / concessions and their aging.
  - Units shipped under deviation vs total shipments for key customers or programs.
- Why they are leading: Plants often choose rework and deviations to protect service levels, allowing scrap risk to accumulate in WIP and latent defects.
- What to watch weekly:
  - Upward trends in rework on any high-margin product line.
  - Any deviation older than a defined threshold (for example, >30 days) that has not been fully addressed by engineering or process changes.
- Dependencies/risks: Many sites track rework and deviations inconsistently across MES, QMS, and paper travelers. Expect gaps and be explicit about them in executive reviews.
4. Scrap in WIP and quarantine, not just final write-offs

Waiting for formal scrap disposition guarantees that executives will see the problem late. Earlier stages are more predictive.
- Metrics:
  - Value of material in quarantine / hold status by week, especially for key products or processes.
  - WIP at-risk: lots tagged with quality concerns, rework pending, or engineering review.
  - Number and size of emerging scrap events (for example, lots where more than a defined percentage has already failed in-process checks).
- Why they are leading: Quarantine stocks and at-risk WIP are often a 2–8 week leading signal for margin impact, depending on lead times and disposition cycles.
- Dependencies/risks: Requires at least partial integration between ERP inventory, MES status, and QMS nonconformances. In brownfield settings, this may start as a partially manual weekly roll-up.
5. Schedule impact from quality issues

Scrap rarely stays isolated to material cost. Executives should see how quality issues are eroding capacity and on-time performance.
- Metrics:
  - Hours of unplanned downtime / lost capacity due to quality investigations, rework, or containment.
  - Number of rescheduled orders or line changeovers directly attributable to quality problems.
  - On-time delivery for top-margin products, annotated where quality issues were a contributing cause.
- Why they are leading: Capacity disruption and rescheduling costs appear before clear scrap accounting and quickly affect contribution margin.
- Dependencies/risks: Requires reason codes for schedule changes and downtime, which are often missing or free-text in legacy scheduling systems.
6. Containment and CAPA load

Increasing containment and corrective activity is often the first signal that problems are compounding, even when scrap and warranty still look acceptable.
- Metrics:
  - Number of open containment actions and their duration.
  - Number of open CAPAs related to scrap, rework, or customer escapes.
  - Average age of open CAPAs and whether interim risk controls are in place.
- Why they are leading: Rising CAPA and containment workload usually precedes chronic scrap and customer dissatisfaction.
- Dependencies/risks: This depends on disciplined use of QMS workflows and change control. In many organizations, CAPA data quality is variable and needs active governance.
7. Supplier-related scrap risk

Supplier quality problems can silently accumulate as in-process scrap, rework, and schedule risk.
- Metrics:
  - Incoming inspection failure rate by critical supplier or commodity.
  - Supplier-related nonconformances that have reached in-process operations or customers.
  - Use of waivers / deviations against supplier material.
- Why they are leading: Supplier instability often hits margins indirectly via late rework, expedited logistics, and line interruptions rather than immediate scrap recognition.
- Dependencies/risks: Requires consistent supplier identifiers across ERP, QMS, and sometimes PLM. Many brownfield environments have fragmented supplier master data.
8. Financial visibility: trending cost of poor quality

Executives should see scrap within a broader view of cost of poor quality (COPQ), with enough frequency to intervene but not so much that finance spends all week compiling numbers.
- Metrics:
  - Estimated COPQ as a percentage of sales for the last 4–12 weeks, broken into scrap, rework, and warranty/returns where possible.
  - Scrap value trends by key product family or program.
  - Correlation of COPQ trends with specific plants, suppliers, or processes.
- Why it is leading: While scrap value itself is more lagging, weekly trend visibility lets leaders connect operational indicators to financial impact and prioritize action.
- Dependencies/risks: COPQ is often only partially modeled, and allocations may be approximate. It is more useful as a relative trend than an absolute truth, especially early on.
9. How to structure an executive weekly scrap-risk review

The metrics above are most effective when presented as a stable, short deck or dashboard that focuses on trends and exceptions rather than raw data volume.
- Keep it small: 10–15 tiles or views, stable over time, with clear owners.
- Trend-first view: 4–12 week rolling trends, with simple traffic-light thresholds that are periodically recalibrated.
- Explicit connections: For each alert or trend, show which process, supplier, or product line is implicated and whether a CAPA or containment action is active.
- Traceability: From each executive metric, there must be a clear path back to underlying data (lot, batch, work order, nonconformance record) for audit and investigation, even if it requires drilling into multiple systems.
10. Brownfield and regulated environment realities

In most regulated, long-lifecycle environments, these metrics must coexist with existing MES, ERP, PLM, LIMS, and QMS systems.
- Do not assume a full system replacement: Replacing core systems just to improve scrap visibility usually fails due to validation burden, qualification of interfaces, downtime risk, and the need to preserve historical traceability.
- Layered integration: A pragmatic pattern is to pull limited, high-value fields from existing systems into a lightweight analytics layer or report, while keeping source-of-truth systems unchanged and validated.
- Manual bridges where needed: Initially, some leading indicators will rely on manual extracts or structured spreadsheets, especially for WIP-at-risk and containment actions. These can still be valuable if they are repeatable, documented, and under change control.
- Validation and change control: Any automation of metric calculations that feeds formal decision-making should be documented, version-controlled, and, where required, validated to the appropriate level. Changes to metric definitions should be visible in the weekly review so leaders understand discontinuities in trends.
11. How to avoid common failure modes

Several patterns tend to undermine the value of leading scrap indicators at the executive level.
- Too many metrics, not enough action: A large, constantly changing dashboard encourages passive viewing rather than decisions. Limit to a core set tied to specific triggers for investigation or escalation.
- Lagging-only views: Scrap and warranty data alone are too late. Always pair them with FPY, nonconformance, rework, and containment indicators.
- Unclear ownership: Each metric should have an operational owner who can explain movements and outline short-term containment and long-term corrective action.
- Unstable definitions: Redefining metrics frequently without clear history makes year-over-year or even month-over-month comparisons unreliable and undermines trust.
- No link to root cause work: Make sure nonconformances and CAPAs referenced in the weekly review are tied to root cause analysis efforts, not just paperwork closure.
Executives do not need exhaustive detail to prevent scrap from compounding into margin erosion. They need a disciplined, traceable set of leading indicators that connect process behavior, quality risks, and financial impact, built on top of existing systems and constrained by validation and change control realities.
March 24, 2026