Connect981 – Content Dev

Glossary Tag: leading indicators

  • bottleneck analysis

    Bottleneck analysis is the systematic identification and evaluation of the process step, resource, equipment, material flow, or decision point that limits overall throughput. In manufacturing, it is used to understand where work is waiting, capacity is constrained, or production flow is being slowed.

    The analysis commonly uses data such as cycle time, queue time, work-in-process, downtime, changeover time, labor availability, yield loss, and schedule adherence. It may be performed with shop-floor observations, value stream mapping, MES data, ERP schedule data, or operational performance metrics such as OEE and non-production time.

    A bottleneck is not always a permanently fixed asset or workstation. It can shift by product mix, staffing, material availability, inspection load, engineering holds, or maintenance conditions. Bottleneck analysis should also not be confused with root cause analysis, although the two are often connected. Bottleneck analysis identifies where flow is constrained; root cause analysis examines why that constraint exists.

    In industrial systems, bottleneck analysis is commonly applied in capacity planning, scheduling, line balancing, continuous improvement, and performance monitoring. For example, an inspection station with long queues may be the current bottleneck even if upstream machining equipment has lower nominal capacity.

  • Process Parameter

    A process parameter is a measurable or controllable condition that defines how a manufacturing or industrial process is run. It commonly refers to variables such as temperature, pressure, speed, feed rate, torque, time, humidity, flow rate, or setpoint values.

    Process parameters are used in work instructions, recipes, routings, control plans, MES records, SCADA systems, quality records, and equipment settings. They help describe the conditions under which an operation was performed and may be recorded for traceability, troubleshooting, process monitoring, or product quality review.

    A process parameter should not be confused with a product characteristic. A process parameter describes the process input or operating condition, while a product characteristic describes the resulting part, material, or assembly feature. For example, oven temperature is a process parameter; coating thickness after curing is a product characteristic.

    Some parameters may be identified as critical process parameters when variation in the parameter can materially affect quality, yield, safety, or process capability. The broader term process parameter does not imply that the parameter is critical unless that status is defined by the applicable process, control plan, or quality system.

  • bill of materials

    Core meaning

    A **bill of materials** (BOM) is a structured list that specifies all components, raw materials, subassemblies, and sometimes services required to manufacture a defined product or execute a defined batch, including their quantities and basic identifying information.

    In industrial and regulated manufacturing environments, the BOM commonly:

    – Is defined and maintained in ERP, PLM, or product definition systems
    – Includes material identifiers, descriptions, units of measure, and required quantities
    – References engineering or product revisions to tie materials to a specific version of the product
    – Serves as a reference for planning, procurement, inventory management, and production execution

    A BOM describes **what** is needed to build a product, not **how** or **when** work is performed.

    Typical structure and levels

    BOMs are often hierarchical and may include:

    – **Top-level (finished good) BOM**: Lists main subassemblies and key materials that make up the final product
    – **Subassembly BOMs**: Define components for intermediate assemblies used within the top-level product
    – **Phantom or logical BOMs**: Groupings used for planning or design that may not exist as separate stocked items

    Depending on system and practice, BOMs may also identify alternates or substitutes, packaging materials, and labeling components when they are explicitly required to produce or release the product.

    Use in manufacturing workflows

    In integrated manufacturing environments, BOMs are used to:

    – Drive **material requirements planning** (MRP) and procurement in ERP systems
    – Define expected material consumption for **costing** and financial tracking
    – Inform **MES** or other shop-floor systems of required components for an order or batch
    – Support **traceability** by providing the expected structure against which actual material lots or serials are recorded

    During production, the BOM is typically linked to:

    – A **routing** or process definition (how work is done)
    – **Work orders**, production orders, or batch records (what is executed and when)
    – **Material master** data for each item listed

    Site context: BOM in MES–ERP integration and costing

    For program or product cost tracking across MES and ERP, the BOM commonly:

    – Resides and is maintained in ERP or PLM as the **authoritative product structure**
    – Provides the expected component list and standard quantities used to calculate standard or planned costs
    – Acts as the reference against which MES reports **summarized actual consumption** (by material ID and quantity) back to ERP at defined intervals

    In this context, MES usually does not author the BOM but uses it to validate material usage and ensure that recorded consumption aligns with the qualified product definition.

    Boundaries and exclusions

    A bill of materials **includes**:

    – Physical components, raw materials, and subassemblies
    – Sometimes non-stock items when they are integral to product composition (e.g., labels, certain consumables)

    A bill of materials **does not inherently include**:

    – Detailed work instructions, sequence of operations, or cycle times (these belong to routings or manufacturing instructions)
    – Real-time production data or yield results
    – Quality tests and acceptance criteria (these are typically defined in specifications or control plans)

    Some organizations maintain separate BOM types, such as **engineering BOM (EBOM)** and **manufacturing BOM (MBOM)**, to distinguish design intent from the structure used for actual manufacturing and sourcing.

    Common confusion and related terms

    – **BOM vs. recipe/formula**: In process industries, a *recipe* or *formula* includes process parameters and instructions in addition to material quantities. The BOM portion is the structured list of materials and quantities.
    – **BOM vs. routing**: A BOM defines *what materials* are required; a routing defines *how and in what sequence* operations are performed.
    – **BOM vs. product specification**: Specifications describe properties and performance requirements; the BOM lists the materials that make up the product.

    Understanding these distinctions helps ensure that BOMs are used consistently for planning, costing, and execution across ERP, MES, and quality systems.

  • control family

    A control family is a grouped set of related security, privacy, quality, or safety controls that share a common objective or topic within a formal framework or standard. Control families provide a structured way to organize individual controls so that organizations can plan, implement, and assess them systematically.

    What a control family includes

    In practice, a control family typically includes:

    • A collection of individual controls that address a similar risk area, process, or function, such as access control, configuration management, or incident response.
    • Sometimes, control enhancements or sub-controls that refine or strengthen a base control.
    • Framework-specific identifiers and labels that help with documentation, traceability, and audits.

    Control families appear in many frameworks used in industrial and regulated environments, including cybersecurity, information security, and quality management standards. They are used to organize requirements across OT and IT systems, MES/ERP integrations, data integrity, and other operational processes.

    Examples in common frameworks

    Examples of control families include:

    • NIST SP 800-53: Families such as Access Control (AC), Configuration Management (CM), System and Information Integrity (SI), and Audit and Accountability (AU). Each family contains multiple numbered controls and enhancements.
    • Other security and privacy frameworks: Similar groupings like identity and access management, change management, business continuity, or vendor management.
    • Quality and operational frameworks: Groupings such as document control, nonconformance and CAPA, equipment maintenance, or training and competence, even if they are not always labeled explicitly as “families.”

    How control families are used operationally

    In industrial and manufacturing contexts, control families are used to:

    • Structure policies and procedures (for example, a set of OT access control procedures aligned to an Access Control family).
    • Map technical and procedural controls in MES, ERP, QMS, and OT systems to specific framework requirements.
    • Plan assessments and audits by reviewing each family to confirm that required controls are defined, implemented, and evidenced.
    • Support risk analysis by viewing gaps and treatment plans by family (for example, all gaps in configuration management).

    Common confusion

    • Control family vs. control: A control is a single requirement or safeguard. A control family is a group of such controls organized around a shared topic.
    • Control family vs. baseline: A baseline is a selected set or level of controls (often across many families) for a given risk profile. A family is a topic-based grouping within the overall catalog of controls.
    • Control family vs. process area or domain: Some standards use terms like “domains” or “process areas” instead of “families.” These often serve the same organizational purpose but may be defined differently by each framework.

    NIST SP 800-53 context

    In NIST SP 800-53, a control family is a labeled group of security and privacy controls (for example, AC, AU, CM) that organizes the catalog. When counting or scoping controls for an implementation, organizations often determine which control families and corresponding baselines apply to their environment, including IT and OT systems that support manufacturing operations.

  • GRC

    GRC stands for governance, risk, and compliance. It commonly refers to a coordinated approach, set of processes, and supporting tools used by an organization to direct and control operations, manage risks, and meet regulatory and internal policy requirements in a consistent and traceable way.

    Core components of GRC

    In industrial and manufacturing environments, GRC typically includes:

    • Governance: How decisions are made and overseen. This covers roles, responsibilities, policies, standards, and escalation paths that direct how OT, IT, quality, safety, and security are managed.
    • Risk: Identification, assessment, treatment, and monitoring of risks, such as cyber risks in OT/ICS, safety risks, supply chain risks, and quality or compliance risks.
    • Compliance: Processes to interpret and implement external requirements (laws, regulations, standards) and internal policies, along with evidence management to show that required controls and procedures are followed.

    Operational meaning in manufacturing and OT

    In regulated manufacturing and industrial operations, GRC activities commonly include:

    • Defining and maintaining policies and standards for OT and IT systems, including security baselines and change control.
    • Maintaining control frameworks mapped to regulations and standards (for example mapping NIST SP 800-53 controls to the NIST Cybersecurity Framework for OT/ICS environments).
    • Conducting risk assessments for production systems, MES/ERP integrations, data flows, and third-party services.
    • Tracking issues, exceptions, and remediation actions (for example for cyber findings, audit findings, or quality deviations that have compliance impact).
    • Collecting and organizing audit-ready evidence from shop-floor systems, quality systems, and enterprise platforms.
    • Reporting risk posture, control coverage, and compliance status to leadership and regulators.

    Organizations may use dedicated GRC platforms or integrate GRC practices with existing tools such as ticketing systems, document control systems, MES, and cybersecurity monitoring solutions.

    Common confusion

    • GRC vs. cybersecurity: Cybersecurity is one risk domain managed within GRC. GRC is broader and also includes financial, operational, safety, and compliance risks.
    • GRC vs. quality management: Quality management focuses on product and process quality. GRC focuses on organizational governance, risk, and compliance. In regulated manufacturing, quality systems often feed evidence and risk data into the broader GRC framework.
    • GRC as a tool vs. a discipline: GRC is a management discipline and set of processes. GRC software tools support these processes but do not define them by themselves.

    Relation to the source context

    In the context of using NIST SP 800-53 to show NIST Cybersecurity Framework posture for OT/ICS, GRC provides the structure to map controls, aggregate risk and maturity information, maintain evidence for assessments, and report cybersecurity posture to leadership as part of an overall risk and compliance program.

  • real-time visibility

    Real-time visibility is the continuous access to current operational data as it is generated, presented in a form that can be monitored or analyzed without delay. In manufacturing and production environments, it means that machine status, work-in-progress, material movements, quality checks, and downtime events are captured, updated, and displayed as they occur, rather than in batches or after a shift.

    Operationally, real-time visibility typically involves:

    • Automatic data collection from equipment, systems, and manual inputs
    • Instant updating of dashboards, reports, and alerts when a status changes
    • A single, consolidated view of current conditions across lines, cells, or sites
    • Standard rules for how events (such as deviations, delays, or failures) are detected and surfaced

    In the context of a Manufacturing Execution System (MES), real-time visibility is achieved when the MES continuously aggregates and displays live production data so that supervisors, operators, and support teams see the same up-to-date information at the same time.

  • EAM

    Core meaning

    EAM (enterprise asset management) commonly refers to the coordinated management of an organization’s physical assets, associated maintenance activities, and lifecycle information. In industrial and manufacturing environments, it is usually implemented as a software system that supports planning, executing, and documenting maintenance work on equipment, utilities, and infrastructure.

    EAM focuses on keeping assets available, safe to operate, and cost-effective over their lifecycle, from acquisition and commissioning through operation, maintenance, modification, and retirement.

    Typical scope in manufacturing

    In regulated or complex manufacturing operations, an EAM system typically manages:

    – **Asset registry and hierarchy**: Machines, lines, utilities, building systems, tools, and instrumentation, often structured by site, area, line, and equipment level.
    – **Maintenance planning and scheduling**: Preventive, predictive, and condition-based maintenance tasks, including calendars, usage-based triggers, and resource planning.
    – **Work management**: Creation, approval, assignment, execution, and closure of work orders for maintenance, inspections, and calibrations.
    – **Spare parts and materials**: Tracking of critical spares, consumables, and repair materials, often linked to inventory systems or ERP.
    – **Asset history and documentation**: Maintenance records, failures, repairs, modifications, and associated documents (drawings, manuals, procedures, change records).
    – **Cost and performance tracking**: Labor, material, and downtime coding against assets for analysis of reliability and lifecycle cost.

    EAM may be integrated with plant control systems, MES, ERP, and quality systems so that asset status and maintenance events are visible across operations.

    Boundaries and what EAM is not

    – **Not only CMMS**: A computerized maintenance management system (CMMS) is often narrower, centered on work orders and maintenance scheduling. EAM typically includes CMMS functions plus broader asset lifecycle and cost tracking.
    – **Not a production control system**: EAM does not control production sequencing, recipes, or batch execution. Those are typically handled by MES or other operations systems, although EAM can expose equipment availability to them.
    – **Not purely financial asset management**: In finance, “asset management” can refer to managing portfolios of financial assets. EAM in manufacturing is about physical, operational assets, not investments.

    Use in real workflows

    In day-to-day plant operations, EAM is commonly used to:

    – Register and classify new equipment when it is installed.
    – Plan preventive maintenance for critical machines, utilities, and safety systems.
    – Generate and track work orders in response to breakdowns or condition-based alerts.
    – Record root cause, parts used, time spent, and asset downtime for each maintenance event.
    – Coordinate with stores or ERP when spare parts reach reorder thresholds.
    – Provide asset maintenance history during investigations, audits, or risk assessments.

    Data from EAM is frequently used for reliability analysis, risk assessments, and continuous improvement of maintenance strategies.

    Relation to MES and unplanned downtime (site context)

    When integrated with MES and other operations systems, EAM data contributes to reducing unplanned downtime by:

    – Making **equipment condition and maintenance status** visible alongside production status.
    – Allowing **maintenance work orders** to be triggered based on MES or sensor data (for example, alarms, performance degradation, or quality events).
    – Providing **structured history** to support root cause analysis of recurring failures and line stoppages.

    In such setups, MES typically captures and classifies downtime events on the shop floor, while EAM manages the maintenance responses, work planning, and asset history. The impact on downtime depends heavily on data quality, integration, and consistent use of maintenance and investigation workflows.

    Common confusions and naming

    – **EAM vs CMMS**: CMMS is often used informally as a synonym, but EAM usually implies a broader scope across the asset lifecycle, with tighter integration to finance and operations.
    – **EAM vs asset performance management (APM)**: APM tools focus on analytics, modeling, and performance optimization of assets. EAM is the system of record for maintenance and lifecycle data that APM may consume.
    – **EAM vs ERP**: Some ERP systems include EAM modules. In those cases, EAM is a functional area within ERP, still focused specifically on physical asset management and maintenance.

  • Ramp-up

    Ramp-up is the controlled increase of production volume, staffing, equipment use, or system activity from an initial level toward a planned operating rate. In manufacturing, it commonly refers to the period after a product launch, line start, process change, or capacity addition when output is increased while performance is monitored.

    During ramp-up, teams typically track whether materials, work instructions, labor, equipment, quality checks, and system transactions can support the higher rate. In MES, ERP, and planning contexts, ramp-up may affect routings, work orders, schedules, inventory demand, inspection load, and throughput assumptions.

    Ramp-up is not the same as startup, which usually refers to the initial act of bringing a process, line, or system into operation. It is also different from capacity, which describes the amount of output a process can support under defined conditions. Ramp-up is the transition toward that expected operating level.

  • Industrialization

    Industrialization commonly refers to the process of converting a design, prototype, laboratory method, or pilot process into a repeatable manufacturing operation that can run at commercial or operational scale. In manufacturing, it includes the work needed to make production stable, documented, resource-supported, and suitable for routine execution.

    The term usually covers more than simply increasing output. It often includes defining manufacturing methods, equipment, workflows, quality controls, training, data flows, and supply chain readiness so that a product can be built consistently. In regulated environments, industrialization may also involve aligning production processes with documented procedures, traceability needs, validation or qualification activities, and change control practices where applicable.

    What it includes

    • Translating product design into manufacturable process steps

    • Establishing routings, work instructions, tooling, and equipment setups

    • Preparing production lines, cells, or work centers for routine execution

    • Defining inspection points, quality records, and traceability requirements

    • Connecting operational systems such as MES, ERP, PLM, or quality systems where needed

    • Supporting operator training, material flow, and production readiness

    What it does not mean

    Industrialization does not mean industrialization in the broad economic or historical sense of a society shifting from agriculture to industry, unless that wider meaning is clearly intended. In operations contexts, it also does not mean mass production by default. A high-mix, low-volume environment can still undergo industrialization if its processes are made controlled and repeatable.

    How it appears in operations

    In practice, industrialization often appears as a transition phase between development and full production. Examples include releasing a digital traveler, qualifying a process route, defining BOM and routing structures in ERP and MES, preparing inspection criteria, and confirming that materials, equipment, and documentation are ready for regular use.

    For example, when a new aerospace assembly moves from engineering build to shop-floor execution, industrialization may involve creating controlled work instructions, linking design revisions to manufacturing records, setting up traceability checkpoints, and defining how nonconformances will be recorded.

    Common confusion

    Industrialization vs. scale-up: Scale-up focuses on increasing capacity or throughput. Industrialization is broader and includes making the process consistently executable, not just larger.

    Industrialization vs. commercialization: Commercialization concerns bringing a product to market. Industrialization concerns making it manufacturable and operable in production.

    Industrialization vs. digitization: Digitization may support industrialization through MES, digital work instructions, or integrated records, but industrialization can also include physical process design, tooling, and workforce preparation.