Connect981 – Content Dev

Glossary Tag: process monitoring

  • factory data integration

    Factory data integration commonly refers to the coordinated exchange, synchronization, and use of data between equipment, operational technology (OT) systems, and information technology (IT) or business systems within a manufacturing facility. It focuses on connecting machines, sensors, MES, SCADA, historians, PLCs, and enterprise platforms such as ERP, PLM, QMS, and analytics tools so that production data can be captured, shared, and used consistently.

    Scope of factory data integration

    In regulated and complex manufacturing environments, factory data integration typically includes:

    • Connecting shop-floor assets such as CNC machines, test stands, assembly stations, and inspection equipment to data collection systems
    • Linking OT systems such as MES, SCADA, historians, and industrial control systems with IT systems such as ERP, PLM, QMS, and warehouse management
    • Standardizing data structures and identifiers so work orders, parts, tools, and measurements can be correlated across systems
    • Exchanging production events and status, for example routing steps, completions, nonconformances, and equipment states
    • Integrating quality and traceability records, such as inspection results, genealogy, and as-built data, with design and planning records
    • Feeding performance and operations data into reporting, OEE dashboards, and operations intelligence platforms

    Factory data integration usually involves industrial connectivity technologies (such as OPC UA, MTConnect, fieldbus gateways, APIs, and message queues), data transformation and mapping, and governance of master data so that different systems interpret records in the same way.

    Operational meaning

    Operationally, factory data integration shows up in workflows such as:

    • Automatic download of NC programs, process parameters, or test limits from PLM or MES to machines
    • Real-time feedback of machine states, cycle counts, and alarms from OT systems into MES or operations dashboards
    • Bidirectional synchronization of work orders, material consumption, and completion confirmations between MES and ERP
    • Transfer of measurement data from gauges, CMMs, or inspection stations into QMS or SPC tools with traceability to specific parts and operations
    • Consolidation of data from multiple lines or plants into a common data model for analytics, reporting, and audit evidence

    The focus is on establishing reliable, consistent data flows so that different factory and enterprise systems can operate on a shared, up-to-date view of production and quality.

    What factory data integration is not

    Factory data integration:

    • Is not limited to a single software product; it usually spans multiple vendors and architectures
    • Is not only about networking hardware; it also involves data modeling, mapping, and governance
    • Is not the same as basic machine connectivity; raw connectivity is one component, while integration implies aligned context and usage across systems

    Common confusion

    Factory data integration vs. MES: A manufacturing execution system (MES) is an application that manages and tracks production. Factory data integration is a broader concept that may include MES but also covers how data moves between MES, ERP, PLM, QMS, machines, and analytics platforms.

    Factory data integration vs. IIoT platform: An industrial IoT (IIoT) platform often provides connectivity, data ingestion, and analytics capabilities. Factory data integration focuses on the end-to-end, structured exchange of production data across operational and business systems. An IIoT platform can be one of the enabling components within a factory data integration strategy.

    Relation to standards and architectures

    Factory data integration is often discussed in the context of reference models such as ISA-95, which distinguishes between control systems on the shop floor and enterprise systems. The integration work typically aligns with linking Level 2 and 3 systems (controllers, SCADA, MES) to Level 4 systems (ERP, planning, and business applications) through defined interfaces and data structures.

    Regulated manufacturing context

    In regulated industries, factory data integration is closely related to traceability, digital records, and audit support. Reliable integration helps ensure that production, quality, and configuration data are consistently associated with specific parts, lots, and work orders across systems, and that changes are visible in appropriate audit trails and version-controlled records.

  • IoT (Internet of Things)

    IoT (Internet of Things) commonly refers to networks of physical objects that are equipped with sensors, actuators, and connectivity so they can collect data, exchange information, and sometimes take actions without direct human intervention. In industrial and manufacturing environments, IoT typically focuses on equipment, tools, and infrastructure that are connected to plant networks or the internet to support monitoring, control, and data-driven decision making.

    Key characteristics

    • Physical assets with sensors: Machines, tools, fixtures, environmental monitors, energy meters, and vehicles that capture data such as temperature, vibration, pressure, cycle counts, or location.
    • Connectivity: Use of wired or wireless communication (for example Ethernet, Wi‑Fi, cellular, LPWAN, industrial fieldbuses with gateways) to send data to gateways, edge devices, or cloud platforms.
    • Data and event processing: Local or remote applications that consume sensor data, generate alerts, visualize conditions, or trigger workflows in systems such as MES, ERP, CMMS, or QMS.
    • Actuation and control: In some cases, IoT devices can receive commands (for example changing setpoints, stopping a machine, or updating firmware) under defined control and safety constraints.

    Industrial and manufacturing context

    In regulated and complex manufacturing, IoT is often discussed under the more specific term Industrial IoT (IIoT). It focuses on connecting operational technology (OT) assets to IT systems in a controlled, secure, and traceable way.

    Typical uses include:

    • Condition and performance monitoring: Streaming machine status, cycle counts, and downtime reasons into MES or operations dashboards to track OEE, NPT, and bottlenecks.
    • Environmental and facility monitoring: Logging temperature, humidity, pressure, or differential air flow in clean or controlled areas and linking the records to quality and compliance evidence.
    • Asset tracking and utilization: Tracking location and usage of tools, fixtures, containers, or high-value parts across work centers and warehouses.
    • Digital traceability: Capturing sensor events (for example torque from a smart screwdriver, cure times, or sterilization profiles) and associating them with specific lots, serial numbers, or work orders.
    • Remote diagnostics and maintenance: Collecting operational data to support predictive or condition-based maintenance through CMMS or maintenance workflows.

    What IoT includes and excludes

    IoT includes:

    • Networked sensors and actuators on production equipment.
    • Edge gateways and devices that aggregate shop-floor data and connect it to higher-level systems.
    • Cloud or on-premise platforms that store and analyze IoT data for operational and business processes.

    IoT does not automatically imply:

    • A full MES or SCADA system, although it can supply data into those systems.
    • Autonomous decision making; many deployments are focused on monitoring and alerts rather than closed-loop control.
    • Compliance or cybersecurity; any regulatory alignment or security posture depends on the broader architecture and controls applied.

    Common confusion

    • IoT vs IIoT: IoT is the broad term for connected devices in any domain (consumer, home, medical, industrial). Industrial IoT (IIoT) focuses on manufacturing, utilities, logistics, and similar industrial settings, usually with stricter requirements for reliability, safety, and security.
    • IoT vs OT networks: Traditional OT networks (PLC networks, fieldbuses, SCADA) can exist without IoT. IoT typically adds IP-based connectivity, additional sensors, and data services that bridge OT with IT and cloud systems.
    • IoT vs MES: IoT captures and transports data from devices. MES uses that and other data to manage production execution, work instructions, traceability, and quality workflows. IoT is an enabler for MES, not a substitute.

    Operational considerations in regulated environments

    When IoT is applied in regulated or defense-related manufacturing, organizations often consider:

    • Data integrity: Ensuring sensor data is accurate, time-stamped, and traceable to specific assets, batches, and work orders.
    • System integration: Mapping IoT data into MES, ERP, QMS, or PLM using defined interfaces so records can support audits and investigations.
    • Network segregation and security: Using segmentation, access control, and monitoring to connect IoT devices without exposing critical OT systems unnecessarily.
    • Device lifecycle management: Managing firmware, calibration status, and change control for IoT devices that support quality or production records.

  • MRO System

    An MRO system is the software and related tooling used to plan, execute, track, and document maintenance, repair, and operations activities for assets and equipment. In industrial and aerospace environments, it commonly refers to digital systems that manage the full lifecycle of maintenance and repair work, including work orders, parts usage, labor, and compliance records.

    Scope and core functions

    MRO systems typically cover some or all of the following areas:

    • Maintenance planning and scheduling: Creating and prioritizing preventive, predictive, and corrective maintenance tasks for production equipment, facilities, or fleets.
    • Work order management: Generating, assigning, updating, and closing maintenance and repair work orders, often with digital work instructions and checklists.
    • Asset and equipment records: Maintaining histories of maintenance performed, configuration changes, usage hours, and condition for tools, machines, or vehicles.
    • Spare parts and materials: Tracking MRO inventory, reservations, consumption, and reordering of spare parts, consumables, and tools.
    • Labor tracking: Recording technician assignments, time spent, qualifications, and required signoffs.
    • Compliance and traceability: Capturing inspection results, repair data, and approvals needed to support regulated environments, audits, and customer or airworthiness requirements.

    Types of MRO systems in industrial and aerospace settings

    The term “MRO system” can refer to different, but related, solution types:

    • Enterprise MRO / EAM systems: Focus on plant and facility assets, production equipment, utilities, and supporting infrastructure. Often described as Enterprise Asset Management (EAM) or Computerized Maintenance Management Systems (CMMS) when centered on maintenance operations.
    • Aerospace and aviation MRO systems: Focus on aircraft and component maintenance, repair, and overhaul, including heavy checks, line maintenance, and component shops. These systems manage work packages, configuration, life-limited parts, airworthiness records, and integration with aviation ERP and quality systems.

    In both cases, the MRO system may integrate with MES, ERP, PLM, and QMS platforms to share asset structures, parts data, work history, and nonconformance information.

    Operational use in regulated manufacturing

    In regulated industrial environments, an MRO system commonly appears in workflows such as:

    • Initiating and routing maintenance work orders that impact production schedules or aircraft availability.
    • Recording inspections, repairs, and part replacements with operator or technician signatures and timestamps.
    • Ensuring that only calibrated tools, approved parts, and qualified personnel are used on specific tasks.
    • Providing traceable maintenance histories for audits, customer reviews, or regulatory oversight.

    Common confusion

    • MRO vs. CMMS: A CMMS is a specific type of MRO-focused system centered on maintenance work orders and assets. “MRO system” is broader and may include materials management, cost tracking, and integration with ERP and MES.
    • MRO vs. MES: MES primarily manages production execution on the shop floor. An MRO system focuses on maintenance and repair activities. In some operations, the two are integrated so that maintenance events and repair work are visible in production and quality records.
    • MRO vs. ERP: ERP handles enterprise-level planning, finance, and inventory. An MRO system provides the operational detail for maintenance and repair activities and often feeds summarized data back to ERP.

    Relation to site context

    On this site, an MRO system most often refers to digital solutions used in aerospace and industrial maintenance, repair, and overhaul environments, including aircraft and component MRO operations, as well as plant and equipment maintenance that must meet quality, traceability, and regulatory expectations.

  • Product Manufacturing Information (PMI)

    Product Manufacturing Information (PMI) commonly refers to the structured set of annotations and data attached to a digital product definition (often a 3D CAD model) that specify how a part or assembly must be manufactured, inspected, and verified.

    PMI typically includes information such as dimensions and tolerances, geometric dimensioning and tolerancing (GD&T), surface finish, material specifications, welding symbols, notes, and other manufacturing and inspection requirements. Instead of existing only on 2D drawings, PMI is embedded directly into the model or associated files so that downstream systems can consume it.

    Where PMI is used in industrial and regulated environments

    In manufacturing operations, PMI is used to transfer design intent into production and quality workflows. Common uses include:

    • Driving CAM programming and CNC toolpath generation from a model with tolerances and features defined
    • Feeding MES, PLM, and QMS systems with critical characteristics and inspection requirements
    • Supporting model-based definition (MBD) and model-based enterprise (MBE) practices, where the 3D model plus PMI act as the authoritative product definition
    • Populating digital inspection plans and first article inspection (FAI) characteristics
    • Providing the basis for ballooned characteristics, measurement plans, and data collection in regulated sectors such as aerospace and medical devices

    Operationally, PMI may be consumed by:

    • CAD and PLM systems that author and manage the product definition
    • MES and digital traveler systems that translate PMI into work instructions, operation steps, and inspection points
    • Metrology and inspection software that uses PMI to automatically generate CMM, vision, or other measurement programs

    What PMI includes and excludes

    PMI generally includes:

    • Dimensional data and tolerances (including GD&T)
    • Surface finish and coating requirements that affect manufacturing and inspection
    • Material specifications as referenced on the model or product definition
    • Feature control frames, datum definitions, and related notes
    • Annotation of critical, key, or safety-related characteristics when defined at the design level

    PMI typically does not include:

    • Detailed routing, sequencing, or resource assignments used by MES or ERP (these are usually derived from PMI plus process planning)
    • Commercial data such as pricing, supplier contracts, or customer order information
    • Plant-specific work instructions that go beyond design intent (these may reference or be configured from PMI, but are separate artifacts)

    PMI and digital thread integration

    In integrated environments, PMI is a key element of the digital thread. By embedding manufacturing and inspection requirements in the product definition, PMI can be exchanged between CAD, PLM, MES, CAM, and metrology systems without reinterpreting or manually re-entering design intent.

    Examples of digital integrations using PMI include:

    • Automatically generating operation characteristics in MES from CAD/PLM so that inspection plans remain aligned with the latest revision
    • Using PMI to define which dimensions must be reported for first article inspection or batch release
    • Driving automated ballooning and characteristic numbering in inspection planning tools

    Common confusion

    PMI vs. 2D drawings: Traditional 2D drawings can contain the same types of requirements, but PMI usually refers to the data embedded in or associated with a digital 3D model. A model-based definition can replace or supplement 2D drawings by using PMI as the authoritative source.

    PMI vs. work instructions: PMI expresses design-level requirements (what must be achieved and controlled), while work instructions describe how operators should perform the work. Work instructions may reference or derive from PMI but are not the same thing.

    PMI vs. MES master data: PMI is product definition data; MES master data covers routings, operations, resources, and control logic. MES may consume PMI to create or update operation characteristics and inspection steps.

  • FAIR Lineage

    FAIR lineage refers to documenting and tracing how data is created, transformed, moved, and used over time in a way that aligns with the FAIR data principles: Findable, Accessible, Interoperable, and Reusable. In industrial and regulated manufacturing environments, it is used to understand where critical data came from, how it has changed, and which systems, processes, or decisions have relied on it.

    Key elements

    FAIR lineage typically includes:

    • Provenance information: the original source of the data, such as a machine, test stand, inspection station, or external supplier system.
    • Transformation history: records of calculations, aggregations, mappings, and edits applied to the data in systems like MES, ERP, PLM, QMS, or analytics tools.
    • System and workflow context: where the data was stored and used, including applications, interfaces, and integration points.
    • Reference and versioning: identifiers, timestamps, and version numbers that make specific datasets findable and distinguishable over time.

    When implemented, FAIR lineage information is often captured through audit trails, event logs, integration metadata, and standardized identifiers across OT and IT systems. This supports traceability of product genealogy, quality records, and compliance evidence without being limited to any one software product or platform.

    Operational relevance in manufacturing

    In manufacturing operations, FAIR lineage commonly appears as:

    • Linking sensor or machine data to specific work orders, lots, or serial numbers used in traceability and genealogy.
    • Showing how inspection results flow from metrology equipment into FAI reports, AS9102 forms, or electronic DHR records.
    • Tracking how routing, work instructions, or specifications from PLM or ERP are transformed before being displayed in MES or digital traveler systems.
    • Providing evidence of which data and versions were used during analysis, CAPA investigations, or audits.

    FAIR lineage does not require that all data be publicly shared. It focuses on structured, well-documented metadata and traceability so that authorized stakeholders can reliably discover, interpret, and reuse data across systems and over time.

    Common confusion

    • FAIR lineage vs. product genealogy: Product genealogy describes the physical history of a part or assembly (materials, processes, and operations). FAIR lineage describes the history of the data about that part, often used to support or explain the genealogy.
    • FAIR lineage vs. simple audit logs: An audit log may show who changed a record and when. FAIR lineage emphasizes a more complete, structured view of data sources, transformations, and relationships so data remains findable, interpretable, and reusable across tools.

    Relation to FAIR principles

    FAIR lineage is one practical way to apply FAIR principles in regulated operations. By maintaining clear data lineage, organizations make it easier to:

    • Locate specific datasets and their origins (Findable).
    • Retrieve them through documented systems and formats (Accessible).
    • Use them across heterogeneous OT/IT platforms (Interoperable).
    • Reanalyze or repurpose them with confidence in their history (Reusable).

  • Master Data Management (MDM)

    Master Data Management (MDM) is the combination of governance practices, data standards, and technical processes used to define, maintain, and synchronize an organization’s core business data across systems. In manufacturing and industrial operations, it focuses on ensuring that foundational data such as materials, parts, equipment, products, recipes, customers, and suppliers is consistent, accurate, and controlled across ERP, MES, PLM, quality, and other OT/IT systems.

    MDM typically covers the creation, approval, change control, distribution, and retirement of master records so that different systems reference the same agreed source of truth. It may be implemented using dedicated MDM platforms, or through coordinated processes and integrations between existing enterprise systems.

    What master data includes in manufacturing

    While exact scope varies by organization, MDM in an industrial context commonly includes:

    • Material and product master data such as item codes, revisions, units of measure, product families, and regulatory attributes.
    • Bill of materials (BOM) and routings including structure, operation sequences, and key parameters referenced by MES and planning systems.
    • Equipment and asset records such as machine identifiers, locations, capabilities, and maintenance classifications.
    • Customer and supplier data including identifiers, sites, and key contractual or regulatory attributes.
    • Reference and code sets such as reason codes, status codes, test codes, and standardized attribute lists.

    MDM usually excludes highly transactional data like individual work orders, production events, or sensor readings, although those transactions rely on consistent master data values.

    Operational role in regulated manufacturing

    In regulated or highly controlled manufacturing environments, MDM commonly supports:

    • Data governance by defining ownership, approval workflows, and change control of master records across functions such as engineering, quality, operations, and supply chain.
    • System integration by providing harmonized identifiers and attributes so ERP, MES, LIMS, QMS, PLM, and data historians can exchange and interpret data consistently.
    • Traceability and genealogy by ensuring that part numbers, batch identifiers, and configuration data are unambiguous when linking production, quality, and supply-chain records.
    • Reporting and analytics by standardizing core dimensions (for example, product, plant, line, customer) used in OEE, NPT, COPQ, and other operational performance metrics.

    Common components of an MDM approach

    A typical MDM approach in manufacturing environments may include:

    • Data model and standards defining required attributes, naming conventions, code sets, and validation rules for each master data domain.
    • Governance and stewardship roles that assign responsibility for creating, reviewing, and approving master data changes.
    • Workflows and controls for requests, reviews, and releases of new or changed master data, often integrated with document control or PLM processes.
    • Integration and synchronization mechanisms (for example, APIs, middleware, or MDM hubs) that distribute approved master data to ERP, MES, QMS, and other consuming systems.
    • Data quality monitoring for detecting duplicates, conflicts, missing values, and misaligned codes across systems.

    Common confusion

    • MDM vs. data warehouse / data lake: A data warehouse or lake stores consolidated data for analysis. MDM governs and synchronizes the core reference records that operational and analytical systems use. They are complementary but not the same.
    • MDM vs. ERP or MES master data modules: ERP and MES often contain master data, but MDM refers to the broader, cross-system governance and harmonization of that data, which may involve multiple platforms.
    • MDM vs. document management: Document management controls documents such as work instructions or procedures. MDM controls structured data elements (for example, item codes, attributes) that may be referenced within those documents and systems.