INDUSTRIAL DATA ARCHITECTURE · PLANT FLOOR · MES/MOM · ERP · ANALYTICS

Industrial data architecture: connecting the plant floor, MES, ERP and analytics.

Sensors, data acquisition, PLCs, SCADA, historians, IIoT, MES/MOM, ERP, PLM, QMS, CMMS/EAM and analytics serve different purposes. The architecture works best when physical plant data retain their context and reach the people and systems that can use them to make decisions.

This guide places KERN IoP within that landscape: plant-floor data acquisition, operational context, process analytics and delivery of useful information to the people and systems making decisions.

GENERAL OVERVIEW

Manufacturing generates data across different time and decision horizons.

A pressure value sampled every second, a machine alarm, a production-order status and a product’s accounting cost are all valid data, but they support different decisions. Industrial architecture needs to retain these distinctions and connect the data.

Key point: an integrated architecture distributes responsibilities across specialised systems. Relevant data must reach the appropriate system with asset identification, time, operating state, order, product, batch or cycle whenever that context is needed.

ISA-95 / IEC 62264

A shared language for understanding responsibilities.

ISA-95 and the corresponding IEC 62264 series organise manufacturing functions from the physical process to business planning. The model describes five levels: physical process (0), sensing and manipulation (1), supervision and control (2), manufacturing operations management (3), and business planning and logistics (4). Its central purpose is to support integration and information exchange between control and enterprise functions.

LEVELS 0–2

Process, sensing and control

Machines, sensors, actuators, PLCs, DCS, HMI and supervisory systems operate close to the physical process and require short response times.

LEVEL 3

Manufacturing operations

MES/MOM and related applications manage production execution, quality, inventory, maintenance and other operational activities.

LEVEL 4

Business and logistics

ERP and enterprise systems manage planning, materials, purchasing, sales, finance and other corporate functions.

Functional level and commercial product scope are separate dimensions. Modern suites can cover several functions and connect directly through APIs, OPC UA, MQTT or other mechanisms. This guide uses ISA-95 as a functional map, complemented by modern networked integration patterns.

MAIN FUNCTIONS

What each family of systems contributes.

SystemMain questionTypical dataMain usersTime horizon
ERPWhat does the business need to plan and manage?Orders, materials, purchasing, inventory, costs, finance, resources.Management, finance, purchasing, logistics, planning.Days to months.
PLMWhat is the current definition of the product and its process?Design, BOM, revisions, specifications, changes, documentation and engineering data.Engineering, product development, quality, manufacturing.Months to the full life cycle.
APSHow should demand and capacity be scheduled?Orders, constraints, resources, times, capacity and priorities.Planning and scheduling.Hours to months.
MES / MOMHow should manufacturing be executed and recorded?Orders, operations, states, materials, genealogy, quality, performance.Production, supervision, operations.Minutes to days.
QMSHow should quality and compliance be managed?Inspections, nonconformities, CAPA, audits, specifications, traceability.Quality, engineering, compliance.Single events to the full life cycle.
LIMSHow should laboratory samples, methods and results be managed?Samples, tests, instruments, results, specifications and analytical traceability.Laboratory, quality, R&D, process engineering.Minutes to years.
CMMS / EAMHow should maintenance and assets be managed?Assets, work orders, preventive maintenance plans, spare parts, failures, maintenance history.Maintenance, reliability, asset management.Hours to years.
WMSWhere is the material and how does it move through the warehouse?Locations, stock, receipts, dispatches, picking, replenishment and supply to production.Logistics, warehousing, materials.Minutes to days.
SCADA / HMIWhat is happening in the process and how is it supervised?Process variables, alarms, states, setpoints and events.Operators and supervisors.Milliseconds to hours.
PLC / DCSHow is the physical process controlled?Inputs/outputs, logic, sequences, control loops and interlocks.Automation and operations.Milliseconds to seconds.
Industrial historianWhich signals occurred, and when?Time series, events, alarms and process tags.Engineering, operations, analytics.Seconds to years.
IIoT / edge / data platformHow are data acquired, transported, contextualised and distributed?Telemetry, asset metadata, semantic models and event streams.OT, IT, engineering and analytics.Real-time to historical.
BI / analyticsWhich patterns, indicators and decisions emerge from the data?KPIs, consolidated data, analytical models and reports.Management, engineering, continuous improvement.Minutes to years.

Commercial product boundaries overlap. A MES may include quality or maintenance functions; an ERP may include scheduling; SCADA may retain historical data; and an IIoT platform may include analytics. The useful question is which function needs to be performed and which data it requires.

Data granularity is another important distinction.

ERP

Transactional data

An order may specify the product, planned quantity, required date and cost. This can support business management, while explaining changes in process performance may require additional data.

MES / MOM

Execution data

The same order may include start and end times, produced quantity, rejects, the resource used, status and genealogy. This supports management of actual execution.

PROCESS / ANALYTICS

Operational data

Explaining variation may require cycle times, pressure, temperature, energy, alarms, environmental conditions or peripheral signals linked to the cycle and product.

KERN IoP’S ROLE

Operational data with context for understanding the process.

Within this architecture, KERN IoP is best described as a platform for operational data acquisition, contextualisation and manufacturing analytics. It works close to the physical process, records relevant signals and events, relates them to production context and turns them into information that plant teams can use directly or other systems can consume.

ACQUISITION

Actual plant variables

KERN IoP | SMARTHUB brings together data from sensors, meters and controllers through the interfaces specified for the project. It also integrates the records that operators enter on SMARTPRO.

CONTEXT

Data linked to operations

Orders, moulds, materials, states, events, parts and other production references allow a signal to be interpreted within the conditions in which it was generated.

ANALYSIS

Histories, indicators and behaviour

KERN IoP | MONITOR provides access to histories, dashboards, reports and exports according to the integrated variables and configured application.

STRATEGIC VALUE

Data resolution determines which questions a plant can answer.

01 · DETAIL

Brings analytics closer to the physical process

A completed order or daily total supports delivery tracking. Cycle, energy, machine and peripheral signals make it possible to investigate how the result was achieved and which condition changed.

02 · CONTEXT

Connects signals to manufacturing

A time series becomes more useful when linked to the asset, product, mould, material, batch, shift, state or event. That context supports comparisons of equivalent conditions.

03 · INTEGRATION

Makes plant data a shared resource

Production, engineering, energy, quality and maintenance teams can consult the same operational data, while MES, ERP and other applications receive the information needed for their own processes.

This approach supports incremental digitalisation: start with a measurable plant need, retain data traceability and later extend the scope to new variables, machines, cells or enterprise integrations.

INTEGRATION SCENARIOS

KERN IoP can work alongside the plant’s existing architecture.

The plant already has an ERP

The ERP retains orders, materials, costs and business transactions. KERN IoP can capture actual machine and process operation, generate indicators and prepare information that complements ERP data for production, energy or process analysis.

The plant has ERP + MES

The MES can coordinate orders, operations, traceability and execution. KERN IoP can contribute specialised machine, peripheral, environmental and energy variables, along with process-focused analytics. Integration allows context already held in the MES to be reused.

The plant has SCADA or a historian

SCADA and historians provide a valuable source of signals and time series. KERN IoP can use these sources or instrument additional variables, linking them to cycles, products, states and manufacturing events for engineering and improvement applications.

The plant is starting its digitalisation

KERN IoP can start as a stand-alone monitoring and analysis system for a specific problem, such as energy, productivity or process variables, while retaining an architecture that allows later integration.

Design principle: when another system already holds data of suitable quality and context, integration is preferable to recapturing it. Define an authoritative source for each master-data item and avoid unnecessary duplication.

PLASTICS PROCESSING

Machine–MES integration already has an injection moulding-specific model.

The OPC Foundation publishes OPC 40077, an OPC UA Companion Specification for data exchange between injection moulding machines and MES. It covers machine information, configuration, status, power units, moulds, injection units, cyclic jobs and production dataset management. This standardisation reflects the distinct responsibilities of machines and MES and their need for structured information exchange.

FROM THE MACHINE

Operational data

States, configuration, cycles, parameters, events and other variables describe how the process ran and help relate its behaviour to the product and outcome.

FROM HIGHER-LEVEL SYSTEMS

Manufacturing context

Orders, products, batches, recipes, priorities and master data provide the business and execution context needed to interpret process records correctly.

In an actual installation, available interfaces depend on the machine, controller, manufacturer, software version and installed configuration. Verify the architecture case by case before defining the integration route.

SELECTION CRITERIA

Start with the decision you want to improve.

01Define the decision

Which production, energy, quality, maintenance or business question needs an answer?

02Identify the data

The required variable, temporal resolution, event, asset, product and context.

03Locate the source

Machine, PLC, sensor, ERP, MES, operator, instrument or existing database.

04Define the consumer

The person or system that needs the result, and how often.

This approach establishes requirements before software procurement. It also helps determine whether the project needs ERP, MES, additional instrumentation, an IIoT layer, process analytics or integration between existing systems.

A useful architecture connects business and process while retaining detail.

Value emerges when an order can be linked to what actually happened at the machine, and when a process signal can be interpreted within the product, batch, cycle or condition that generated it. KERN IoP is designed for this operational role: measuring, contextualising and analysing the data needed to understand actual production behaviour.

FREQUENTLY ASKED QUESTIONS

ERP, MES and plant-floor data.

Can an ERP also manage production?
Many ERP systems include planning, orders, materials, costs and even manufacturing modules. Detailed process analysis usually requires plant-floor data, acquired directly or through execution, control or data acquisition systems. The architecture depends on the required level of detail.
What is the main difference between ERP and MES?
ERP focuses on business processes and planning; MES/MOM manages the execution of manufacturing operations and links the plan to actual production. Much of the ISA-95 model structures information exchange between these functions.
Do SCADA and MES perform the same role?
SCADA focuses on supervision, data acquisition and operational control. MES/MOM manages manufacturing execution: orders, operations, materials, traceability and performance. They can exchange information within an integrated architecture.
What is an industrial historian used for?
It retains process time series and events for retrieval and analysis. Its strength lies in preserving the time-dependent behaviour of industrial tags; product, batch or order context can come from other applications or a contextualisation layer.
How does KERN IoP fit alongside a MES?
KERN IoP acquires and contextualises operational data and analyses it for productivity, energy, process, quality and maintenance applications. It can operate independently or integrate with MES to supply specialised plant-floor variables and receive execution context.
Is KERN IoP shop floor software?
In some industrial settings, the term shop floor software is used for solutions that work directly with production, machine and operator information. In this broad sense, KERN IoP includes capabilities that fit the term, although it describes only part of the solution. KERN IoP combines sensors and instrumentation, data acquisition hardware, machine and PLC signals, operating records, monitoring software, histories, contextualisation and analytics for process, production, energy and environmental variables. It can also exchange information with MES/MOM, ERP and other industrial applications. A fuller technical description is therefore a platform for acquiring, contextualising and analysing operational manufacturing data.
Does KERN IoP replace an ERP?
The proposed architecture assigns business management to ERP and operational data capture and analytics to KERN IoP. Integration connects the two perspectives where the use case requires it.
What should be defined before integrating two systems?
The authoritative source for each data item, shared identifiers, temporal resolution, semantic meaning, update frequency, flow direction, data quality rules, cybersecurity, failure handling and responsibility for each interface.

Explore the KERN IoP architecture in more detail.

PROTOCOLS AND INTERFACES

OPC UA, MQTT and EUROMAP

What each technology standardises and how to bring a machine signal into an industrial application.

GLOSSARY

Industrial digitalisation terminology

Definitions of broker, brownfield, edge, OPC UA, MES, MQTT, SCADA and other concepts.

PLATFORM

Monitoring and analytics architecture

The complete path from signal acquisition to historical data, dashboards and plant applications.

HARDWARE

KERN IoP | SMARTPRO

Acquisition of sensor and controller signals and incorporation of operating records.

SOFTWARE

KERN IoP | MONITOR

Access to historical data, dashboards, reports and exports of acquired data.

PRODUCTIVITY

OEE according to ISO 22400

How to structure availability, performance and quality using production data.

ENERGY

Industrial energy measurement

Electrical data from machines and cells for analysing consumption and energy behaviour.

CONTEXT

Industrial digitalisation in the region

Data and sources for interpreting technology adoption and digital maturity in manufacturing.

REFERENCES

Technical sources consulted.

International Society of Automation. (n.d.). ISA-95 series of standards: Enterprise-control system integration. Retrieved 3 October 2026, from https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard

International Society of Automation. (2025). ANSI/ISA-95.00.01-2025 (IEC 62264-1 Modified): Enterprise-control system integration — Part 1: Models and terminology. ISA.

MESA International. (2013). Applying manufacturing operations models in a discrete hybrid manufacturing environment. MESA International. https://blog.mesa.org/2013/06/mesa-announces-publishing-of-mesa-white.html

OPC Foundation. (2020). OPC 40077: OPC UA interfaces for plastics and rubber machinery — Data exchange between injection moulding machines and MES (Version 1.01). https://reference.opcfoundation.org/specs/OPC-40077

OPC Foundation. (n.d.). What is OPC? Retrieved 3 October 2026, from https://opcfoundation.org/about/what-is-opc/

National Institute of Standards and Technology. (n.d.). SCADA. Computer Security Resource Center Glossary. Retrieved 3 October 2026, from https://csrc.nist.gov/glossary/term/scada

SAP. (n.d.). What is a manufacturing execution system (MES)? Retrieved 3 October 2026, from https://www.sap.com/latinamerica/products/scm/digital-manufacturing/what-is-mes.html

SAP. (n.d.). What is ERP? Retrieved 3 October 2026, from https://www.sap.com/products/erp/what-is-erp.html

Siemens. (n.d.). Advanced planning and scheduling. Retrieved 3 October 2026, from https://www.siemens.com/es-es/technology/advanced-planning-scheduling-aps/

Siemens. (n.d.). Quality management system (QMS) software. Retrieved 3 October 2026, from https://www.siemens.com/es-es/solutions/quality-management-qms/

IBM. (2026). What is a CMMS? https://www.ibm.com/think/topics/what-is-a-cmms

Microsoft. (n.d.). Connected factory reference architecture. Microsoft Learn. Retrieved 3 October 2026, from https://learn.microsoft.com/es-es/fabric/real-time-intelligence/architectures/connected-factory

Rockwell Automation. (n.d.). FactoryTalk Historian. Retrieved 3 October 2026, from https://www.rockwellautomation.com/es-es/products/software/factorytalk/operationsuite/historian.html

Siemens. (n.d.). PLM software. Retrieved 3 October 2026, from https://www.siemens.com/es-es/solutions/product-lifecycle-management-plm/

SAP. (n.d.). Extended Warehouse Management. Retrieved 3 October 2026, from https://www.sap.com/latinamerica/products/scm/extended-warehouse-management.html

Thermo Fisher Scientific. (n.d.). Manufacturing LIMS. Retrieved 3 October 2026, from https://www.thermofisher.com/es/en/home/digital-solutions/lab-informatics/lims-manufacturing.html

Siemens. (n.d.). Shop floor control. Retrieved 3 October 2026, from https://www.siemens.com/en-gb/technology/shop-floor-control/

Oracle. (n.d.). Overview to Shop Floor Control — Process Guide. Retrieved 3 October 2026, from https://docs.oracle.com/cd/E26228_01/doc.93/e21780/ovr_shop_fl_ctrl.htm

SAP. (n.d.). SAP Digital Manufacturing: Manufacturing execution and operations. Retrieved 3 October 2026, from https://www.sap.com/products/scm/digital-manufacturing.html

Eichenseer, P., & Winkler, H. (2024). A data-oriented shopfloor management in the production context: A systematic literature review. The International Journal of Advanced Manufacturing Technology, 134, 4071–4097. https://doi.org/10.1007/s00170-024-14238-8

Scholten, B., & Brandl, D. (2026). Getting acquainted with ISA-95. In The Road to Integration: A Guide to Applying the ISA-95 Standards in Manufacturing (2nd ed.). Wiley. https://doi.org/10.1002/9781394438501.ch1

The categories shown are functional. Commercial products may cover several categories, so architecture assessment requires a review of the installed system’s specific capabilities and interfaces.

TECHNICAL REVIEW

Dr.-Ing. Miguel Garzón · Technical Director, KERN IoP

Technical content prepared by PM Tec Engineering, through its Industry 4.0 division, KERN IoP. Last reviewed: October 2026. Technical profile and publications →


PM Tec Engineering, through its Industry 4.0 division, KERN IoP.
Cota, Cundinamarca · Colombia.
© 2026 PM Tec Servicios de Ingeniería SAS · Website updated in 2026.

Privacy policy