Connect981 – Content Dev

RSC Cluster: Performance Visibility (OEE, NPT, Shift Variance)

The Performance Visibility cluster translates execution data into outcomes leadership actually cares about. It focuses on OEE, nonproductive time, downtime, and shift-to-shift variance, with an emphasis on high-mix, low-volume aerospace environments. The content clearly distinguishes meaningful metrics from vanity KPIs and explains how to calculate, interpret, and act on performance data. The goal is to help teams move from anecdotal explanations to evidence-based improvement tied directly to execution reality.

  • KPI steward

    A KPI steward is the person or role accountable for maintaining the integrity of a key performance indicator (KPI) over time. This commonly includes owning the KPI definition, calculation logic, data sources, update rules, and documentation so the metric is interpreted consistently across teams and systems.

    The term usually refers to governance of the metric, not day-to-day operational performance against the metric. A KPI steward may not be the process owner, department manager, or system administrator, although one person can hold more than one of those roles in practice.

    What a KPI steward typically covers

    • Defines what the KPI measures and what it does not measure

    • Maintains calculation rules, units, time windows, and thresholds

    • Identifies the approved system(s) of record and source data

    • Controls changes to the KPI so historical reporting remains understandable

    • Helps resolve disputes about interpretation, lineage, or reporting differences

    • Supports documentation used in dashboards, MES, ERP, QMS, BI, or reporting workflows

    In manufacturing environments, a KPI steward often helps keep measures such as OEE, scrap rate, first pass yield, schedule attainment, nonconformance rate, or on-time delivery aligned across production, quality, and enterprise reporting.

    What it is not

    A KPI steward is not automatically the person entering data, building every dashboard, or approving management decisions based on the KPI. The role is centered on metric governance and consistency. It also does not necessarily mean legal ownership of the underlying data platform.

    Common confusion

    KPI steward vs. KPI owner: A KPI owner is often the person accountable for business results tied to the metric. A KPI steward is commonly responsible for metric definition, lineage, and consistency. Some organizations combine these roles, but they are not the same by default.

    KPI steward vs. data steward: A data steward usually governs data elements or datasets more broadly. A KPI steward focuses on a specific business metric, including how multiple data elements are combined and interpreted.

    KPI steward vs. report owner: A report owner may maintain a dashboard or report format, while a KPI steward maintains the meaning and logic of the KPI itself.

    Why the role appears in regulated operations

    In regulated or highly controlled manufacturing, the same KPI may appear in MES, ERP, QMS, spreadsheet reports, and management reviews. A KPI steward helps reduce ambiguity when teams compare values across systems, time periods, or sites. This is especially relevant when a metric is used for performance review, quality trending, escalation, or audit evidence preparation.

  • MTBF

    MTBF stands for Mean Time Between Failures. It is a reliability metric that estimates the average time a repairable asset or component operates before an inherent (not human-induced) failure occurs. In industrial and manufacturing environments, MTBF is commonly used for equipment, production lines, control systems, and automation components.

    What MTBF represents

    MTBF is typically expressed as hours of operation between failures and is calculated over a defined observation period or based on reliability modeling. It assumes that:

    • The asset is repairable and returned to service after each failure.
    • Failures are random and occur under stated operating conditions.
    • The failure rate is approximately constant within the considered time window.

    In formula form, MTBF commonly refers to total operating time divided by the number of failures in that time period, for the population or single asset under analysis.

    Use in manufacturing and operations

    In regulated and high-uptime manufacturing environments, MTBF is used to describe and track the reliability of:

    • Production equipment (e.g., CNC machines, ovens, assembly cells).
    • Automation and control hardware (PLCs, drives, sensors, HMIs).
    • OT and IT infrastructure supporting MES, SCADA, and data collection.

    Operationally, MTBF can feed into:

    • Availability and OEE calculations as an input to planned/unplanned downtime analysis.
    • Maintenance planning and spare parts strategies for critical assets.
    • Risk and reliability assessments when qualifying equipment or processes.

    In KPI frameworks such as ISO 22400, MTBF is part of the broader set of availability and reliability indicators that support performance visibility and root cause investigations for downtime.

    What MTBF does not cover

    MTBF does not measure:

    • How long it takes to repair equipment after failure (this is typically MTTR).
    • Process yield, product quality, or scrap rates.
    • Operator errors, changeovers, or planned shutdowns unless they are explicitly defined as failures in the data model.

    MTBF is a statistical indicator, not a guaranteed minimum life or warranty period. It should be interpreted alongside other metrics such as MTTR, availability, and quality KPIs.

    Common confusion

    • MTBF vs. MTTF: MTTF (Mean Time To Failure) is usually used for non-repairable items that are discarded after failure, while MTBF is used for repairable assets returned to service.
    • MTBF vs. MTTR: MTTR (Mean Time To Repair or Restore) describes the average time required to repair or restore a failed asset, not the time between failures.
    • MTBF vs. Availability: Availability depends on both MTBF and MTTR. High MTBF with long MTTR can still result in low availability.

    Context in KPI and reliability programs

    In a reliability-centered maintenance or asset management program, MTBF may be trended over time per asset, asset class, or line, often integrated into MES, CMMS, or operations-intelligence tools. In regulated industries, consistent definitions of what constitutes a failure, how operating time is measured, and how data is captured are important for using MTBF as a reliable KPI.

  • KPI ownership

    KPI ownership commonly refers to the clear assignment of responsibility for a specific key performance indicator (KPI) to an individual role, team, or function. The KPI owner is accountable for how the metric is defined, how data is collected, and how the organization responds when performance varies.

    What KPI ownership includes

    In industrial and regulated manufacturing environments, KPI ownership typically covers:

    • Definition and scope: Ensuring the KPI has a clear definition, formula, units, and data sources (for example, defining how OEE or on-time delivery is calculated across plants).
    • Data quality and integrity: Working with IT/OT, MES, ERP, and quality systems to confirm that input data is available, consistent, and traceable.
    • Monitoring and review: Regularly reviewing KPI results, trends, and variation across shifts, lines, suppliers, or sites.
    • Escalation and action: Initiating investigations, corrective actions, or continuous improvement activities when targets are missed or unusual variation appears.
    • Governance and communication: Keeping documentation, dashboards, and reporting rules current so that different stakeholders interpret the KPI consistently.

    Where KPI ownership shows up operationally

    In practice, KPI ownership often appears in:

    • Production and operations: Line or value stream managers owning KPIs such as throughput, OEE, scrap rate, and changeover time, typically fed by MES or OT data.
    • Quality management: Quality leaders owning defect rates, CAPA cycle time, first-pass yield, or supplier quality metrics from QMS and inspection systems.
    • Supply chain and planning: Materials or planning teams owning KPIs such as on-time delivery, schedule adherence, shortages, and inventory turns, often driven by ERP/MRP data.
    • Compliance and audit readiness: Designated owners for KPIs that support quality system performance, audit findings, or regulatory reporting.

    In many organizations, KPI ownership is documented in RACI charts, management review procedures, or metric governance standards so that there is no ambiguity about who maintains each KPI and who is accountable for results.

    What KPI ownership does not mean

    • It does not mean the owner personally performs all work that affects the KPI.
    • It does not guarantee that the KPI meets any external standard or certification requirement.
    • It does not replace cross-functional responsibility for performance; it clarifies who coordinates and stewards the metric.

    Common confusion

    • KPI ownership vs. KPI visibility: Many people may see a KPI on dashboards, but there is usually one defined owner accountable for its definition and performance management.
    • KPI ownership vs. data ownership: Data ownership focuses on who manages the underlying data assets and systems (for example, MES or ERP). KPI ownership focuses on the metric built from that data and the operational response.

  • Performance indicator

    A performance indicator is a defined metric used to measure how effectively a process, asset, team, or organization is achieving specific objectives. In industrial and regulated manufacturing environments, performance indicators are typically numeric values calculated in a consistent way over time so that trends, variances, and issues can be identified and investigated.

    Performance indicators may describe efficiency, quality, safety, delivery, cost, or compliance. They are often tracked at different levels, such as plant, line, workcenter, product family, supplier, or shift. In information systems, performance indicators are commonly implemented as data fields, calculations, and dashboards in MES, ERP, QMS, and operations intelligence tools.

    Types of performance indicators in manufacturing

    In regulated and industrial operations, common categories of performance indicators include:

    • Operational efficiency: metrics such as OEE, throughput, cycle time, changeover time, and non-productive time (NPT).
    • Quality and compliance: first-pass yield, defect rate, scrap and rework, cost of poor quality (COPQ), nonconformance rates, and closure time for CAPA or MRB actions.
    • Delivery and supply chain: on-time delivery (OTD), schedule adherence, lead time, backlog, and supplier performance indicators such as supplier OTD and defect rates.
    • Asset and maintenance: equipment availability, mean time between failures (MTBF), mean time to repair (MTTR), and maintenance schedule adherence.
    • Workforce and training: training completion, certification currency, operator utilization, and cross-skill coverage on critical operations.

    Operational use

    In day-to-day operations, performance indicators are used to:

    • Monitor process stability and detect abnormal variation across shifts, lines, or sites.
    • Support problem-solving methods such as 8D, root cause analysis, and continuous improvement projects.
    • Provide evidence for internal and external audits, including quality and regulatory audits.
    • Align shop-floor activities with business objectives, such as cost reduction, lead-time reduction, or improved delivery reliability.
    • Feed management reviews and regular performance reviews at plant or enterprise level.

    Performance indicators are often configured in MES, ERP, and analytics platforms by defining data sources (for example, machine signals, work orders, inspection results), calculation logic, aggregation rules, and visualization (reports, scorecards, or dashboards).

    Common confusion

    The term is closely related to several others:

    • Key Performance Indicator (KPI): a KPI is typically a subset of performance indicators that are considered most critical for achieving strategic or regulatory objectives. All KPIs are performance indicators, but not all performance indicators are KPIs.
    • Metric or measure: any numeric value can be a metric, but it is usually called a performance indicator only when it is intentionally linked to a goal, target, or performance standard.

    Relationship to standards and frameworks

    In manufacturing, performance indicators are often aligned with industry frameworks and standards that define standardized metrics. For example, OEE, availability, performance, and quality measures are widely used as standardized operational performance indicators, and some standards describe families of manufacturing KPIs to support benchmarking and consistent reporting. Organizations may adapt or extend these indicators to reflect their specific processes, regulatory context, and system landscape.

  • Utilization

    Utilization commonly refers to how much of a resource’s available time or capacity is actually used for productive work over a defined period. In industrial operations, it is typically expressed as a percentage and applied to machines, production lines, work centers, tooling, or labor.

    At its simplest, utilization answers the question: “Out of all the time this resource could have been running or working, how much time was it actually in use?” It indicates loading and capacity usage, not whether that usage was efficient or of good quality.

    How utilization is typically calculated

    A common operational formula is:

    Utilization (%) = (Actual run time or use time / Available time) × 100

    Key points for manufacturing contexts:

    • Actual run time or use time usually means time spent performing scheduled production or value-adding work (for example, machine cutting time, assembly work, inspection time), sometimes including setup depending on local definitions.
    • Available time is the time the resource is planned or staffed to be available, which may exclude planned shutdowns (holidays, major maintenance) or not, depending on the site’s standard.
    • Utilization can be calculated per shift, day, week, or over longer periods for capacity planning.

    Role in industrial and regulated environments

    In regulated manufacturing, utilization is commonly used to:

    • Assess how fully machines, lines, or specialized equipment (for example, ovens, autoclaves, test stands) are being used relative to schedule.
    • Support capacity and staffing decisions, such as when to add shifts or re-balance work centers.
    • Provide input to higher-level metrics like Overall Equipment Effectiveness (OEE), where utilization is related to the availability and performance components.
    • Evaluate impact of non-productive time such as waiting for material, changeovers, unplanned maintenance, or quality holds.
    • Feed MES, ERP, or operations dashboards for shop-floor visibility and bottleneck analysis.

    Utilization is descriptive rather than prescriptive. Different plants may include or exclude certain time categories (for example, setups, minor stops, meetings) as long as their definitions are documented and used consistently.

    What utilization includes and excludes

    Typically included in utilization calculations:

    • Time the resource is actively performing planned work orders or production tasks.
    • In some sites, time for setups, changeovers, or cleaning between lots, if considered part of normal productive use.

    Typically excluded (or sometimes tracked separately):

    • Planned downtime such as scheduled preventive maintenance, holidays, or plant shutdowns, when defined as not available.
    • Unplanned downtime, waiting for materials, quality holds, or administrative delays, when these are tracked as separate loss categories.
    • Scrap and rework themselves do not directly change utilization, although they may increase or decrease run time.

    The exact boundaries depend on local data collection standards, MES configuration, and reporting requirements. In regulated settings, definitions are often documented in procedures or work instructions for consistency and auditability.

    Utilization vs. related performance metrics

    Utilization is often considered alongside other operational metrics:

    • Availability: In OEE terms, availability measures the proportion of planned production time during which the equipment is actually running. Utilization and availability are closely related but may be defined using different time bases.
    • OEE (Overall Equipment Effectiveness): OEE combines availability, performance, and quality. Utilization by itself does not account for speed losses or quality yield.
    • Throughput: Throughput is the rate of product output (for example, parts per hour). High utilization does not guarantee high throughput if there are speed losses, rework, or frequent stops.
    • Capacity: Capacity is the theoretical or planned maximum output over time. Utilization describes how much of that capacity is being used, not how much exists.

    Common confusion

    • Utilization vs. efficiency: Utilization measures how much of the available time a resource is used, regardless of whether it is running at the ideal rate. Efficiency, performance, or productivity metrics look at how well that time converts into expected output.
    • Utilization vs. utilization of labor: Some organizations track machine utilization and labor utilization separately. Labor utilization may include time spent on indirect tasks (training, meetings, 5S) that are not captured in machine utilization.
    • Utilization vs. schedule adherence: A line can have high utilization but low adherence to the production schedule if it is producing different work orders than planned or running at different times than planned.

    Use in MES, ERP, and operations intelligence

    Utilization often appears as a derived KPI within MES, SCADA, and operations dashboards. Systems may capture:

    • Automatic states such as running, idle, faulted, or changeover from machine signals.
    • Operator-coded reasons for downtime or idle time.
    • Planned versus unplanned gaps between work orders.

    ERP or planning systems may then use historical utilization to refine capacity models, lead times, and staffing assumptions. In regulated environments, clear definitions and traceable data sources support consistent reporting, internal reviews, and external audits.

  • indicator

    An indicator is a calculated or context-enriched value that interprets raw data to describe the state or performance of a process, resource, or system. In industrial and manufacturing environments, indicators are typically derived from one or more measurements (raw data) and are used to monitor conditions, detect trends, and support operational decisions.

    Key characteristics

    In manufacturing and operations, an indicator commonly:

    • Is derived from raw data using a defined calculation, aggregation, or classification rule
    • Has clear units, context, and scope (for example, per line, per shift, per batch)
    • Describes a specific aspect of performance, quality, utilization, or compliance
    • Is used for monitoring and analysis, and may feed into higher-level KPIs

    Examples include:

    • Average cycle time per work center over a shift
    • First-pass yield for a product family in a day
    • Machine availability percentage for a line in the last hour
    • Number of deviations opened in a week, grouped by type

    Indicators vs raw data and KPIs

    In models such as ISO 22400 for manufacturing operations management:

    • Raw data are basic measurements or events (for example, sensor readings, start/stop timestamps, counts) without additional processing.
    • Indicators are context-enriched or calculated values derived from raw data (for example, utilization rate, mean time between failures, scrap ratio).
    • Key Performance Indicators (KPIs) are a subset of indicators selected as especially important for tracking business or operational objectives and are often used for formal reporting.

    In practice, whether a metric is treated as a general indicator or as a KPI depends on local governance, management focus, and how it is used in decision-making, not just on the formula.

    Operational usage in manufacturing systems

    Indicators appear across OT and IT systems such as MES, historians, SCADA, and analytics platforms. They may be:

    • Calculated in real time for dashboards and shop floor visibility
    • Stored for historical analysis, trend evaluation, and investigations
    • Used as inputs to composite metrics like Overall Equipment Effectiveness (OEE)
    • Aligned to data models or standards (for example, ISA-95 role- or level-based views)

    Clear definition and governance of indicators are important for consistent use across sites, systems, and reports, especially in regulated environments where traceability of calculations and versions may be required.

    Common confusion

    • Indicator vs KPI: All KPIs are indicators, but not all indicators are KPIs. Indicators become KPIs when they are explicitly selected and governed for critical performance tracking.
    • Indicator vs raw measurement: A single sensor reading (for example, temperature at a timestamp) is raw data. An indicator applies logic or context (for example, average temperature during a batch, or percentage of time within a specified range).
    • Indicator vs alarm: An alarm is a notification based on a condition or threshold. The underlying monitored value is often an indicator, while the alarm is the event triggered when that indicator crosses defined limits.

  • time categories

    Time categories are standardized buckets used to classify how time is spent in a manufacturing or maintenance, repair and overhaul (MRO) environment. They provide a structured way to break total calendar time into meaningful segments, so that systems and analysts can measure utilization, performance, and causes of delay in a consistent way.

    In industrial operations, time categories are commonly applied to equipment, production lines, assets, or work orders. They appear in MES, CMMS/EAM, and analytics tools as coded states or event types that describe what is happening during a given time interval.

    Typical structure of time categories

    While naming varies by organization and standard, time categories often follow a hierarchy, for example:

    • Calendar / total time: 24/7 time, including both working and non-working periods.
    • Available vs. non-available time:
      • Available time: Time when an asset or resource is scheduled or allowed to run.
      • Non-available time: Time when it is not expected to run (e.g., holidays, long-term shutdowns).
    • Within available time:
      • Operating / productive time: Time spent executing value-adding production or maintenance work.
      • Planned loss: Scheduled activities that stop normal operation, such as planned maintenance, changeovers, inspections, or training.
      • Unplanned loss: Unscheduled events that reduce output, such as breakdowns, waiting for material, rework, or quality inspections triggered by issues.

    Each high-level time category can be further split into more detailed subcategories, such as specific types of downtime, setup, quality-related delays, or logistics-related waiting time.

    Operational use in systems and KPIs

    Time categories are used to:

    • Map MES or CMMS event codes (e.g., machine state, work order status) into standardized buckets.
    • Calculate KPIs such as OEE, non-productive time (NPT), utilization, and turnaround time (TAT) components.
    • Enable cross-site comparisons by normalizing different local codes into a shared time model.
    • Support root cause and bottleneck analysis by linking delays to clear, agreed categories.

    Standards such as ISO 22400 describe reference time category models for manufacturing KPI calculation. Organizations often use these as a starting point and extend them with sector-specific categories, for example detailed MRO turnaround states.

    Use in MRO and turnaround management

    In MRO, time categories are frequently applied at the work-package or asset level to break down turnaround time into events such as induction, inspection, teardown, repair, test, rework, waiting for parts, and customer hold. These detailed events are then aligned with more generic time categories in plant-wide KPI models so that MRO performance can be compared to other manufacturing operations.

    Common confusion

    • Time categories vs. event codes: Event codes are the raw labels or status values recorded by systems (for example, “Setup”, “Waiting for QC”). Time categories are the standardized buckets those events are mapped into for analysis.
    • Time categories vs. shifts or calendars: Shifts and calendars define when work is planned. Time categories describe what actually happened during that time.
    • Time categories vs. KPIs: KPIs are metrics (for example, OEE or TAT). Time categories are an input structure that supports calculating and interpreting those metrics.

  • TEEP

    TEEP stands for Total Effective Equipment Performance. In industrial and manufacturing environments it is a utilization metric that extends OEE by including all calendar time, not just planned production time.

    Core definition

    TEEP commonly refers to the percentage of total calendar time that an asset, line, or plant actually uses to produce good product at the target rate. A typical high-level formula is:

    • TEEP = OEE × Loading

    Where, in many TPM and ISO 22400 style interpretations:

    • OEE (Overall Equipment Effectiveness) measures effectiveness during planned production time only (availability, performance, and quality losses within that window).
    • Loading (sometimes called utilization) measures what share of total calendar time is designated as planned production time.

    Under this view, TEEP expresses how close the equipment is to its theoretical maximum output if it were available and scheduled to run 24 hours a day, 7 days a week.

    Operational meaning in manufacturing

    In practice, TEEP is used to provide visibility into both:

    • How intensively equipment is scheduled (loading across shifts, weekends, holidays).
    • How effectively equipment runs when scheduled (the OEE components of availability, performance, and quality).

    On many shop floors, TEEP appears in performance dashboards, MES or operations intelligence systems as a high-level capacity and utilization indicator. Typical usage includes:

    • Comparing effective utilization across lines, plants, or assets that run on different shift patterns.
    • Assessing whether to add shifts, re-balance loading, or pursue continuous improvement on existing shifts.
    • Separating business decisions about scheduling and demand from technical or process losses inside scheduled time.

    Because TEEP is based on calendar time, it is sensitive to how an organization defines total time, planned downtime, and non-production days. These definitions need to be documented in systems and reports, especially in regulated environments.

    Relationship to OEE and ISO 22400

    In many TPM-style implementations, TEEP is described alongside OEE as part of a family of equipment-related KPIs. ISO 22400 series standards describe related concepts such as availability, utilization, and other manufacturing performance indicators, but terminology and formulas may differ from legacy TPM practices.

    Where both TPM-style OEE and ISO 22400 terminology are used, organizations commonly:

    • Map TEEP clearly to the underlying ISO 22400 metrics (for example, which time categories are included in loading and availability).
    • Document any alternate formulas or naming used locally so that system reports and audit evidence remain consistent.

    What TEEP includes and excludes

    In its typical manufacturing usage, TEEP:

    • Includes all calendar time for the measurement period (for example, 24×7 over a week or month).
    • Includes both production and non-production periods when calculating loading.
    • Excludes any notion of theoretical design limits beyond the chosen reference speed and quality assumptions already embedded in OEE.

    TEEP does not by itself distinguish between different reasons for low utilization (such as low demand, maintenance strategy, staffing limits, or technical downtime). Those factors are usually tracked in supporting loss or time models linked to OEE and scheduling.

    Common confusion

    • TEEP vs. OEE: OEE looks only at effectiveness during planned production time. TEEP extends this by considering how much of total calendar time is actually planned and used for production. High OEE with low TEEP often indicates under-loading or limited shift patterns rather than poor equipment performance.
    • TEEP vs. utilization or capacity utilization: Some plants use “utilization” to mean loading, and others use it to mean something closer to TEEP. To avoid confusion, it is helpful to specify the exact formula used for TEEP and any related utilization metric in performance reports and MES configurations.

    Derived-from context: TPM-style and ISO 22400 usage

    In TPM-style OEE environments, TEEP is often presented as a legacy or local KPI that complements OEE by revealing calendar-based capacity use. When organizations adopt ISO 22400 terminology, they frequently keep TEEP as an internal indicator while explicitly documenting how its formula maps to the standard’s time and performance definitions so that reports, system integrations, and audits remain clear.