Connect981 – Content Dev

Glossary Tag: leading indicators

  • First time yield

    First time yield commonly refers to the percentage of units, assemblies, or process steps that pass through a manufacturing process correctly on the first attempt, without needing rework, repair, retest, or scrap handling before moving forward. It is used as a quality and process performance measure in production, test, inspection, and packaging workflows.

    In practical terms, first time yield shows how often work is done right the first time at a defined point in the process. Depending on how an organization measures it, the denominator may be all units started at an operation, all units completed, or all opportunities at a specific step. Because calculation methods vary, the exact formula should be defined locally when comparing lines, plants, suppliers, or reporting periods.

    What it includes and excludes

    First time yield usually includes output that meets requirements at the initial pass of a process step or route. It generally excludes units that only pass after correction activities such as rework, adjustment, troubleshooting, retest, or repair.

    • Includes: conforming output accepted on the initial run through a defined operation or sequence
    • Excludes: parts or lots that require rework, repair, deviation handling, or repeated testing before acceptance

    Some organizations also exclude scrapped units entirely, while others count them as failed first-pass attempts. That difference can materially change reported values.

    How it appears in operations

    First time yield is commonly tracked in MES, quality systems, test systems, or production reporting dashboards. It may be measured at several levels, such as a single work center, a test station, a routing step, a production line, or an end-to-end build process.

    Examples in manufacturing include a board that passes electrical test on its first run, a machined part that meets dimensional requirements without rework, or a batch record step completed without correction.

    Common confusion

    First time yield is often confused with first pass yield. In many organizations the terms are used interchangeably, but some teams define first pass yield more narrowly for one station or inspection point, while first time yield may refer to a broader process or completed workflow. The terms should not be assumed to be identical unless the local definition is stated.

    It is also different from rolled throughput yield, which combines yields across multiple sequential steps to show the probability that a unit moves through an entire process without defects or rework.

  • APQP (Advanced Product Quality Planning)

    APQP commonly refers to Advanced Product Quality Planning, a structured method for planning and coordinating the activities needed to bring a new product or changed product into production with defined quality controls. It is used to organize cross-functional work across product design, process design, risk review, validation, supplier inputs, and production readiness.

    In manufacturing, APQP is not a single form, software module, or inspection step. It is a planning framework that links product requirements to process definition, control methods, and evidence generated before and during launch. It is most often associated with automotive supply chains, but the underlying approach is also relevant in other regulated or quality-sensitive manufacturing environments where design transfer and production readiness need to be controlled.

    What APQP includes

    • Planning product and process requirements before production release

    • Coordinating activities across engineering, quality, manufacturing, supply chain, and suppliers

    • Identifying risks and special controls early in development and industrialization

    • Defining validation and readiness activities such as process capability, measurement planning, and production trial outputs

    • Creating the records and deliverables used to show that the product and process were prepared for launch

    In practice, APQP often connects to documents and workflows such as design reviews, process flow diagrams, PFMEA, control plans, MSA, capability studies, PPAP-related outputs, and launch checklists. The exact deliverables can vary by industry, customer, and internal quality system.

    What APQP does not mean

    APQP does not mean final product approval by itself, and it is not the same as PPAP. APQP covers the broader planning and execution process that leads up to production readiness, while PPAP commonly refers to a submission package or approval process used to demonstrate that readiness. APQP is also not equivalent to project management in general, although project management methods are often used to track APQP activities.

    How it appears in operations and systems

    Operationally, APQP appears as a staged set of quality planning tasks tied to product introduction, engineering change, supplier qualification, or process transfer. In digital environments, these activities may be distributed across PLM, QMS, ERP, MES, and supplier collaboration systems. For example, product characteristics may originate in design systems, risk and control definitions may be managed in quality records, and production validation evidence may be captured from shop floor or supplier processes.

    APQP is often used to create alignment between design intent and manufacturing execution by making sure required controls, inspection methods, documentation, and release criteria are defined before routine production begins.

    Common confusion

    APQP is commonly confused with:

    • PPAP: PPAP is typically the evidence or submission process used to demonstrate that product and process requirements have been met. APQP is the broader planning framework.

    • Control Plan: A control plan is usually one APQP output, not the full APQP process.

    • PFMEA: PFMEA is a risk analysis tool often used within APQP, not a synonym for APQP.

    • NPI or product launch: New product introduction and launch management are broader business processes. APQP is the quality planning discipline within that broader effort.

  • KPI specification

    A KPI specification is a documented definition of a key performance indicator that explains exactly what the metric measures, how it is calculated, what data it uses, and how it should be interpreted. It is used to make sure the same KPI is measured consistently across teams, systems, time periods, and reporting views.

    In manufacturing and regulated operations, a KPI specification commonly includes the metric name, business purpose, formula, unit of measure, time basis, inclusion and exclusion rules, source systems, refresh frequency, and ownership. It may also define thresholds, targets, and drill-down dimensions, but it is not the performance result itself.

    A KPI specification is not a dashboard, chart, or report. It is the underlying metric definition that allows dashboards, MES reports, ERP analytics, and quality reviews to use the same logic. For example, if a site tracks first pass yield, schedule attainment, or nonconformance rate, the KPI specification defines what counts in the numerator and denominator and which transactions or events are in scope.

    What it usually includes

    • Metric name and plain-language definition

    • Formula or calculation logic

    • Unit of measure and reporting cadence

    • Scope, boundaries, and exclusions

    • Source data and system of record

    • Data quality or timing assumptions

    • Owner or steward responsible for maintaining the definition

    • Target, threshold, or alert criteria when applicable

    Operational meaning

    Operationally, KPI specifications are used when metrics are implemented in MES, ERP, historian, BI, or quality systems. They help align operators, supervisors, engineers, quality teams, and analysts on the same definition so that shift reviews, management reporting, and continuous improvement activities are based on comparable numbers.

    They are also useful when integrating data across systems. If production counts come from MES, scrap events from quality records, and labor time from ERP, the KPI specification documents how those sources are combined and which timestamps, statuses, or transaction types are valid for the metric.

    Common confusion

    KPI specification is often confused with a KPI target or KPI dashboard. A target is the expected value or threshold for a metric. A dashboard is the visual presentation of one or more metrics. The KPI specification is the controlled definition behind both.

    It can also be confused with a data definition or report requirement. Those are related, but a KPI specification focuses on the business meaning and calculation rules of the metric, not only the technical structure of the data or the layout of a report.

  • FPY (First Pass Yield)

    FPY (First Pass Yield) commonly refers to the percentage of units, assemblies, or process steps that meet requirements the first time they pass through a process, without rework, repair, or retesting caused by a failure.

    It is a quality and execution metric used to show how often work is done right the first time. In manufacturing, FPY may be calculated at a single operation, a line, or across a defined sequence of steps, depending on how the organization structures its measurement.

    What it includes and excludes

    FPY includes items that successfully pass a defined process or inspection point on the initial attempt. It excludes items that only become acceptable after rework, repair, troubleshooting, retest, or repeated processing. Scrap is also not counted as first-pass success.

    The exact calculation boundary matters. Some teams measure FPY at one workstation, while others measure it across an end-to-end routing. Because of that, FPY values are only comparable when the process scope and counting rules are defined the same way.

    How it appears in operations

    In shop floor and quality systems, FPY is often tracked by work order, operation, product family, line, shift, supplier source, or defect category. MES, QMS, and ERP-linked reporting may use FPY to highlight where defects, setup issues, material problems, or instruction gaps are causing avoidable rework.

    For example, if 100 units enter an assembly step and 92 pass that step the first time while 8 require rework, the FPY for that step is 92%.

    Common confusion

    FPY is often confused with related yield and performance metrics:

    • FPY vs. Rolled Throughput Yield (RTY): FPY may describe one step or a defined stage, while RTY reflects the combined first-pass performance across multiple sequential steps.

    • FPY vs. final yield: Final yield can include items that eventually pass after rework. FPY does not.

    • FPY vs. OEE: FPY is a quality-focused metric. OEE combines availability, performance, and quality into a broader equipment and production metric.

    Why the term matters in regulated manufacturing

    In regulated and high-traceability environments, FPY is commonly used as an operational signal for process stability and workmanship quality. It can also help teams identify where nonconformances, repeat inspections, or documentation errors are entering the process. However, FPY by itself does not prove compliance, capability, or product conformity.

  • Critical process parameter (CPP)

    A critical process parameter (CPP) is a measurable operating condition or setting in a manufacturing or processing step whose variation can have a meaningful effect on product quality or process outcome. It commonly refers to a parameter that must be defined, monitored, and controlled because it is linked to one or more critical quality attributes or other important acceptance criteria.

    A CPP is part of the process, not the product itself. Examples can include temperature, mixing speed, pressure, pH, dwell time, torque, line speed, or fill volume setpoint, depending on the operation. Not every process parameter is critical. A parameter is generally considered critical only when changes in that parameter can materially change the result.

    How it is used in operations

    In regulated and quality-controlled manufacturing, CPPs are typically identified during process development, validation, risk assessment, or ongoing process monitoring. They may appear in batch records, recipes, work instructions, MES workflows, historian tags, alarm limits, trend reports, or exception reviews.

    Operationally, a CPP is often associated with:

    • defined target values or ranges
    • upper and lower operating limits
    • monitoring frequency or automated data capture
    • documentation of excursions, deviations, or interventions
    • links to investigations, CAPA, or process improvement activities when control is lost

    What it includes and excludes

    CPP commonly includes process inputs, machine settings, environmental conditions, and step-level operating values that can influence the output of a process. It does not usually mean a final product specification or finished-good test result. It also does not automatically include every parameter collected by equipment or software.

    In some organizations, the threshold for calling a parameter critical is formal and risk-based. In others, the term may be used more broadly for highly important settings. The exact classification method can vary, but the core meaning is consistent: it is a process variable important enough to require defined control.

    Common confusion

    CPP vs. critical quality attribute (CQA): a CPP is a process setting or condition, while a CQA is a property of the product or output that must meet defined expectations.

    CPP vs. key process parameter (KPP): some organizations use KPP for important parameters that are monitored closely, while reserving CPP for parameters with stronger evidence of direct impact on quality. Usage varies by industry and company.

    CPP vs. control limit: a control limit is a boundary used to manage variation. The CPP is the parameter being controlled, not the limit itself.

    Manufacturing example

    If a curing process depends on oven temperature and dwell time to achieve the required material properties, those settings may be treated as CPPs when variation in either can produce out-of-spec or nonconforming results.

  • Scorecard

    A scorecard commonly refers to a structured way of summarizing performance against a defined set of measures, targets, or evaluation criteria. In manufacturing and regulated operations, it is often used to monitor how a process, supplier, production line, team, or program is performing over time.

    A scorecard is not the same as a single KPI. It brings multiple indicators together so performance can be reviewed in one place. Depending on the use case, a scorecard may include quality, delivery, cost, responsiveness, safety-related observations, training status, audit findings, downtime, yield, or other operational signals.

    How it is used in operations

    Scorecards appear in both manual and digital workflows. They may be maintained in spreadsheets, BI tools, ERP or MES reports, supplier portals, or quality systems. Common examples include supplier scorecards, departmental performance scorecards, production scorecards, and management review scorecards.

    In practice, a scorecard often includes:

    • Defined metrics or rating criteria
    • A time period such as daily, weekly, monthly, or quarterly
    • Targets, thresholds, or expected ranges
    • Actual results or ratings
    • Trend status or exceptions that need review

    Some scorecards are purely quantitative, while others combine numeric measures with qualitative assessments or review comments.

    What it includes and excludes

    A scorecard includes the presentation and evaluation of selected measures. It does not, by itself, define how the data was collected, whether the metrics are standardized across systems, or what action must be taken when results are off target.

    It is also separate from the underlying transaction records or evidence. For example, a supplier scorecard may summarize on-time delivery and defect rates, but the scorecard itself is not the purchase order history, inspection record, or nonconformance record.

    Common confusion

    Scorecard vs. dashboard: A dashboard usually emphasizes live or near-real-time visibility. A scorecard more often emphasizes evaluation against goals, thresholds, or criteria over a defined review period. In practice, some tools combine both.

    Scorecard vs. KPI: A KPI is one measure. A scorecard is a grouped set of measures or ratings.

    Scorecard vs. report: A report may present detailed data. A scorecard usually condenses that data into a summary used for review or comparison.

    Manufacturing-relevant examples

    • A supplier scorecard tracking on-time delivery, quality escapes, and response time to corrective actions
    • A production scorecard showing output, scrap, downtime, and schedule attainment by shift
    • A quality scorecard summarizing audit findings, CAPA aging, and first-pass yield

  • cross-site benchmarking

    Cross-site benchmarking commonly refers to the structured comparison of performance, process, quality, cost, capacity, or compliance-related measures across multiple facilities, lines, plants, or operating sites using a shared basis for measurement.

    In manufacturing, it is used to identify differences in outcomes or operating methods between sites so teams can understand variation, investigate causes, and evaluate whether a practice, control, or workflow is consistently applied. The term includes both metric comparison, such as yield, scrap, OEE, cycle time, deviation rates, or schedule attainment, and process comparison, such as how work instructions, approvals, material handling, or quality checks are executed.

    It does not mean comparing raw numbers without context. Meaningful cross-site benchmarking usually depends on normalized definitions, comparable time periods, and awareness of differences in product mix, routing complexity, automation level, staffing model, and regulatory constraints. It also does not automatically imply external benchmarking against other companies. Cross-site benchmarking is usually internal, across sites within the same organization or network, though some organizations extend it to contract manufacturers or partner operations when data definitions are aligned.

    How it appears in operations

    Cross-site benchmarking often shows up in dashboards, KPI reviews, continuous improvement programs, quality reviews, and network-level operational governance. Data may be pulled from MES, ERP, QMS, historian, CMMS, or reporting tools and then mapped into common definitions for comparison.

    • Comparing first-pass yield across plants making similar products

    • Reviewing nonconformance rates by site and by product family

    • Comparing changeover time, schedule adherence, or labor utilization across lines

    • Assessing whether CAPA closure timing or document approval cycles differ by location

    Common confusion

    Cross-site benchmarking is often confused with benchmarking more broadly. Benchmarking can include comparison against industry peers, published standards, or competitors. Cross-site benchmarking is narrower and usually refers to comparisons among internal sites or closely connected operating entities.

    It can also be confused with scorecarding or reporting. A scorecard presents measures, while cross-site benchmarking emphasizes comparability, variance analysis, and interpretation across locations. It is also different from standardization. Standardization defines the intended method; benchmarking compares how sites actually perform or operate.

    Why comparability matters

    The main challenge in cross-site benchmarking is not collecting numbers but ensuring they mean the same thing. For example, one site may classify rework separately while another includes it in scrap, or one site may calculate downtime from machine states while another uses manual entries. Without consistent definitions, the comparison can be misleading.

    For regulated manufacturing environments, this is especially relevant when comparing quality signals, traceability completeness, training status, deviation handling, or audit evidence readiness across sites. The term refers to the comparison activity itself, not to any conclusion that one site is compliant or better managed.