Connect981 – Content Dev

Glossary Tag: process monitoring

  • Continuous Monitoring

    Continuous monitoring commonly refers to the ongoing, often automated, collection and review of data from systems, equipment, or processes to detect changes, anomalies, or nonconformances in near real time. In industrial and regulated manufacturing environments, it is used both for cybersecurity and for operational or quality oversight.

    Operational meaning in manufacturing

    In manufacturing, continuous monitoring typically includes:

    • Production and process data: Tracking parameters such as temperature, pressure, torque, cycle time, and machine status to identify deviations from defined limits or standard work.
    • Quality indicators: Monitoring defect rates, measurement results, SPC charts, and inspection outcomes to catch emerging nonconformances earlier.
    • Equipment condition and performance: Observing utilization, downtime, alarms, and maintenance indicators to support OEE analysis and reliability programs.
    • Data integrity and traceability: Automatically logging who did what, when, and on which part or lot, including changes to work instructions, routings, and records.

    Continuous monitoring may be implemented through MES, SCADA, historians, machine connectivity, quality systems, or specialized monitoring tools. Alerts, dashboards, and reports are commonly used to surface issues to operators, supervisors, quality engineers, and IT/OT teams.

    Cybersecurity and compliance context

    In cybersecurity and regulated manufacturing, continuous monitoring also refers to ongoing oversight of information systems and networks, for example:

    • Tracking user access, authentication attempts, and privileged activities on OT and IT systems.
    • Monitoring for abnormal network traffic, unauthorized connections, or configuration changes in industrial control systems.
    • Collecting security-relevant logs from MES, ERP, file servers, and other applications for review and correlation.
    • Maintaining evidence that required controls are active and functioning over time, in support of internal policies or external frameworks (such as cybersecurity or data protection requirements).

    In this sense, continuous monitoring supports risk management by helping organizations detect potential security incidents or control failures in a timely manner, rather than relying only on periodic audits.

    What continuous monitoring is not

    • It is not a one-time audit, assessment, or inspection. Those are point-in-time activities, while continuous monitoring is ongoing.
    • It is not limited to a single department. It can span production, maintenance, quality, IT, and OT.
    • It is not a guarantee of compliance or security. It is a method of collecting information to support oversight and decision-making.

    Common confusion

    • Continuous monitoring vs. periodic monitoring: Periodic monitoring uses scheduled checks (for example, weekly or monthly reviews). Continuous monitoring relies on near real-time or high-frequency data collection and alerting.
    • Continuous monitoring vs. control: Monitoring observes and reports on the state of systems or processes. Control functions (such as interlocks, PLC logic, or automated shutdowns) act on that information. Many industrial systems use both, but they are distinct concepts.
    • Continuous monitoring vs. continuous improvement: Continuous improvement focuses on systematically enhancing processes. Continuous monitoring provides data and visibility that can feed those improvement efforts but is not an improvement methodology by itself.

    Use in regulated manufacturing

    In regulated or high-risk environments, continuous monitoring is often applied to:

    • Maintain consistent records of process conditions and product history for traceability.
    • Support detection, investigation, and documentation of nonconformances and CAPA activities.
    • Provide ongoing evidence that certain operational, quality, or cybersecurity controls are functioning as intended.

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

  • rolled throughput yield

    Rolled throughput yield (RTY) is a quality and process performance metric that estimates the probability that a unit will pass through an entire sequence of process steps defect free, without requiring any rework or repair.

    What rolled throughput yield measures

    RTY considers every value-adding and inspection step in a process and multiplies the first-pass yield of each step together. It answers the question: “What fraction of units make it from start to finish with no defects at any step?”

    In many manufacturing and regulated environments, individual steps may show high first-pass yields, but small loss percentages at each step accumulate across a long routing. RTY makes this cumulative effect visible.

    How RTY is typically calculated

    Rolled throughput yield is commonly computed as:

    • Determine the first-pass yield (FPY) or throughput yield for each process step, typically defined as defect-free units out divided by units in, excluding reworked units.
    • Multiply the yields of all steps: RTY = FPY1 × FPY2 × … × FPYn.

    For example, if four steps have FPY values of 0.98, 0.97, 0.99, and 0.96, the RTY is approximately 0.90, meaning about 90% of units pass all four steps without any defects.

    Use in industrial and regulated environments

    In industrial operations, RTY is used to:

    • Quantify the hidden impact of rework and minor defects along complex routings, such as in aerospace assembly or pharmaceutical packaging.
    • Support continuous improvement initiatives (for example, Lean or Six Sigma) by targeting steps that most reduce end-to-end defect-free flow.
    • Complement other metrics like first-pass yield, scrap rate, and cost of poor quality by giving a process-level perspective.
    • Feed into operational performance and quality dashboards in MES, LIMS, or quality systems.

    In regulated environments, RTY is often monitored alongside nonconformance, deviation, and CAPA metrics to understand overall process capability and the effectiveness of defect prevention, rather than only defect detection.

    Operational considerations

    To use RTY reliably, organizations typically need:

    • Consistent definitions of what counts as a defect and what is considered rework, repair, or scrap at each step.
    • Accurate, time-stamped data from shop floor systems or manual logs for units in, units out, and defect counts by operation.
    • Stable process routings or explicit handling of alternate routings in the calculation.

    RTY can be calculated at different scopes, such as for a single line, a particular product family, or a specific process segment (for example, surface treatment or final test).

    Common confusion

    • RTY vs first-pass yield (FPY): FPY usually refers to a single step or a single overall process pass. RTY explicitly reflects the cumulative effect of multiple steps, even if each step’s FPY appears high.
    • RTY vs overall equipment effectiveness (OEE): OEE focuses on equipment utilization and loss categories (availability, performance, quality). RTY focuses specifically on defect-free flow through a sequence of steps, regardless of equipment uptime.
    • RTY vs throughput: General throughput refers to volume or rate of output. RTY is a probability or percentage of defect-free units, not a production rate.

    Link to nonconformance management

    In contexts like aerospace or other highly regulated manufacturing, RTY is often examined alongside nonconformance rates and rework statistics. A low or declining RTY may indicate that nonconformance management is detecting issues late in the process or that process controls are not preventing defects early. RTY does not measure nonconformance handling speed or backlog directly, but it provides a consolidated view of how often nonconformances arise across the full process path.

  • Category metadata

    Category metadata is descriptive information used to assign an item to one or more defined categories so it can be organized, filtered, governed, and retrieved consistently.

    In manufacturing and regulated operations, category metadata commonly refers to labels or fields that indicate what kind of record, document, event, asset, product, or content item something is. Examples can include document type, nonconformance category, equipment class, training record category, or content topic.

    It is metadata about classification, not the underlying item itself. For example, a work instruction is the document; its category metadata may identify it as a controlled procedure, operator training material, or quality document.

    Where it appears

    Category metadata appears in systems that store or exchange structured information, such as:

    • MES, ERP, PLM, QMS, and document management systems
    • Content management systems and knowledge bases
    • Data integration layers, APIs, and reporting models
    • Audit support records, training files, and quality event logs

    It is often used to support search, routing, permissions, retention rules, analytics, and cross-system mapping.

    What it includes and excludes

    Category metadata may include a category name, category ID, taxonomy path, parent-child classification, or related tags used for grouping.

    It does not usually mean all metadata associated with an item. Other metadata fields such as author, revision, timestamp, approval status, or file format are metadata, but they are not category metadata unless they are specifically used as classification fields.

    Common confusion

    Category metadata is often confused with tags, taxonomies, or master data.

    • Tags are usually looser labels and may not follow a controlled hierarchy.
    • Taxonomy is the classification structure itself, while category metadata is the value assigned from that structure.
    • Master data refers to governed core business entities such as parts, suppliers, or customers, not just their classification fields.

    Operational relevance

    When category metadata is defined consistently, it helps systems and teams interpret records the same way across workflows. For example, a quality event categorized as supplier-related can be routed differently from an internal production issue, and a training record categorized as certification-related may be handled differently from general onboarding content.

  • Diagnostic metric

    A diagnostic metric is a measurement used to help determine why a process, machine, system, or business outcome is performing the way it is. In manufacturing and industrial operations, it commonly refers to a metric that supports root-cause analysis, fault isolation, deviation review, or performance troubleshooting rather than simply reporting final results.

    Diagnostic metrics are typically used after a signal, exception, or trend has been observed. For example, if throughput drops or scrap increases, diagnostic metrics may include changeover time, downtime by cause code, first-pass yield by step, alarm frequency, queue time, temperature variance, or operator intervention rate. These measures help connect an outcome to likely contributing factors.

    A diagnostic metric is not the same as an outcome metric or a target itself. It does not directly state whether a business objective was met. Instead, it provides explanatory detail that helps teams understand process behavior and decide where to investigate further.

    Where it appears in operations

    Diagnostic metrics may appear in MES, SCADA, historian, quality, maintenance, or analytics systems. They are often used in:

    • shift and production review dashboards
    • exception and alarm analysis
    • CAPA or deviation investigations
    • equipment troubleshooting
    • process capability and variation analysis
    • continuous improvement and bottleneck reviews

    In regulated environments, these metrics may support investigation and evidence gathering, but they do not by themselves establish compliance or prove conformance.

    Common confusion

    Diagnostic metric is commonly confused with leading indicator and lagging indicator. A leading indicator is intended to signal what may happen next, and a lagging indicator reflects an outcome that has already occurred. A diagnostic metric is different because its main purpose is to explain causes, drivers, or relationships behind observed performance.

    It may also be confused with a predictive metric. Predictive metrics are used to estimate future states, while diagnostic metrics are used to analyze why a current or past condition exists.

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

  • Outcome Category

    An outcome category is a defined grouping used to classify and organize results, impacts, or end states of processes, projects, or systems. In industrial and manufacturing environments, outcome categories help structure how organizations measure performance, risk, quality, and compliance outcomes across operations.

    Outcome categories are typically defined at the management or program level and then used consistently across sites, lines, or value streams. They provide a common language for reporting, analytics, and prioritization.

    How outcome categories are used in manufacturing

    In regulated and industrial operations, outcome categories commonly appear in:

    • Quality and nonconformance management: grouping outcomes such as conforming product, rework required, scrap, deviation accepted, or returned to supplier.
    • Continuous improvement and problem solving: classifying outcomes of improvement actions, for example defect reduction, lead-time reduction, safety incident reduction, or compliance risk reduction.
    • Operational performance reporting: organizing KPIs and metrics into categories like throughput, on-time delivery, cost of poor quality, safety, or asset utilization.
    • Risk and safety management: categorizing outcomes such as near miss, recordable incident, environmental event, or no impact.
    • IT/OT and MES/ERP projects: defining expected business outcomes of digital initiatives, such as improved traceability, reduced manual data entry, or faster audit response.

    Outcome categories can be configured in MES, QMS, ERP, and analytics tools as picklists, tags, or reporting dimensions. Consistent use enables aggregated dashboards, benchmarking across plants, and clearer decision making about where to focus resources.

    What outcome categories typically include and exclude

    Outcome categories typically include:

    • High-level result groupings that are stable over time (for example quality, delivery, safety, cost, compliance).
    • Operationally meaningful labels that can apply across different products, customers, or lines.
    • Definitions that are documented so different teams interpret categories the same way.

    They typically exclude:

    • Individual metrics or raw data points (for example a specific scrap percentage or cycle time at one station).
    • Root causes or corrective actions, which are usually tracked in separate fields or taxonomies.
    • Detailed process steps; those belong to routings, work instructions, or workflows rather than outcome categories.

    Common confusion

    Outcome category vs. metric: A metric is a specific, quantified measure (for example on-time delivery rate). An outcome category is a grouping under which multiple metrics may fall (for example delivery performance).

    Outcome category vs. root cause category: Root cause categories describe why something happened (for example training, method, material). Outcome categories describe what result was observed or achieved (for example scrap generated, rework required, audit finding closed).

    Outcome category vs. risk category: Risk categories focus on potential future events or exposures. Outcome categories focus on actual realized results or states, although in many management systems the two taxonomies are designed to align.

    Link to operational and compliance contexts

    In regulated manufacturing, clearly defined outcome categories support traceable and repeatable reporting for audits, customer reviews, and internal governance. For example, a quality management system might require that each nonconformance be assigned both an outcome category (scrap, rework, use-as-is) and a disposition authority, enabling consistent analysis of how issues are ultimately resolved.

    When integrated across MES, ERP, and QMS, shared outcome categories help ensure that shop-floor events, financial impacts, and compliance records can be reconciled and compared using the same high-level result groupings.

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