Connect981 – Content Dev

Glossary Tag: signal detection

  • 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.

  • 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.

  • 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

  • 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.

  • 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.

  • Inclusion/exclusion rules

    Inclusion/exclusion rules are documented criteria used to determine what should be included and what should be excluded within a defined scope. In manufacturing and regulated operations, the term commonly refers to boundary-setting rules for records, events, materials, transactions, inspection results, products, suppliers, or process steps.

    These rules help make scope decisions explicit and repeatable. They do not describe the full process by themselves. Instead, they define the conditions for whether something belongs inside or outside a stated category, workflow, calculation, report, or review.

    Where the term applies

    In operational and quality systems, inclusion/exclusion rules may be used in areas such as:

    • Reporting and analytics: deciding which work orders, lots, downtime events, or defects count in a KPI.
    • Quality records: defining which nonconformances, deviations, or inspection observations must be captured in a specific log or review.
    • Traceability and genealogy: determining which materials, serialized parts, or process steps are part of the as-built record.
    • System integrations: specifying which master data, transactions, or document revisions should pass between ERP, MES, QMS, or PLM systems.
    • Document control: clarifying which documents fall under a given procedure and which do not.

    What it includes and excludes

    Inclusion rules describe the characteristics that qualify an item for scope. Exclusion rules describe the characteristics that remove an item from scope, even if it appears related.

    For example, a production dashboard might include only released manufacturing orders for a specific plant and exclude canceled orders, simulation records, and test transactions. A quality review might include all shop-floor nonconformances opened during a date range and exclude supplier-owned issues tracked in a separate workflow.

    Common confusion

    Inclusion/exclusion rules vs. requirements: Requirements state what must be done. Inclusion/exclusion rules state what falls within the defined boundary of that requirement, report, or process.

    Inclusion/exclusion rules vs. permissions: Permissions control who can view, edit, approve, or execute actions. Inclusion/exclusion rules control what objects or cases are considered in scope.

    Inclusion/exclusion rules vs. filters: A filter is often a system-level implementation of the rules. The rules are the underlying criteria; the filter is the mechanism used to apply them.

    Operational meaning

    In practice, inclusion/exclusion rules often appear in procedures, report definitions, validation logic, interface mappings, and review checklists. Clear rules reduce ambiguity when multiple teams need to classify the same data or records the same way across systems.