Home / Knowledge / Vertical Integration

What is vertical integration in manufacturing?

Short answer

In manufacturing, vertical integration means the end-to-end connection of all levels of a plant: from sensors and controllers through supervisory systems and MES to the ERP. Data from the equipment reaches planning and order management without manual steps, and orders and specifications travel back to the equipment. It is one of the three characteristics of Industrie 4.0. It does not refer to the business strategy of the same name, in which a company takes over upstream or downstream stages of its supply chain.

Reading time 6 minutesEditorial team, inray Industriesoftware
Levels of a plant from the equipment to the ERP, connected through a continuous data flow in both directions

Definition: vertical integration

The recommendations for implementing the strategic initiative Industrie 4.0 (Forschungsunion and acatech, final report of 8 April 2013) name three characteristics of Industrie 4.0. One of them is vertical integration and networked manufacturing systems: the plant connects its levels end to end, from sensors to enterprise management, and thereby becomes flexible and reconfigurable. The other two characteristics are horizontal integration through value networks and end-to-end digital engineering.

Characteristic Separate levels Vertically integrated
Order confirmation Manual or by export at the end of the shift Automatically from the equipment, linked to the order
Specifications for the equipment Printed, retyped or maintained locally Passed directly from MES or ERP to the line
Key figures Delayed and often calculated differently per department From the same data for all levels
Changes Affect many individual interfaces Through defined transitions between levels
Troubleshooting Comparing lists from several systems Data flow traceable from the equipment to the ERP

Why the levels are being connected

The level model itself is older than Industrie 4.0. The Purdue reference model for computer-integrated manufacturing (CIM) was published by the Instrument Society of America in October 1989. The ANSI/ISA-95 standard builds on it; its first part appeared in 2000 and was adopted internationally as IEC 62264-1 in 2003.

The levels differ above all in cycle time and data volume. A single signal recorded ten times per second produces 10 · 86,400 = 864,000 values per day. With 500 signals in a plant, that is 432 million values daily. The ERP needs only a few aggregated figures per order, such as quantity, scrap and duration. The calculation is an example. It shows why vertical integration does not mean sending all data upwards, but aggregating it and adding context along the way.

The levels of vertical integration

ISA-95 describes five levels. The standard deals mainly with the interface between level 3 and level 4.

Level Content Typical systems
Level 0 Physical production process Machines, equipment, workpieces
Level 1 Sensing and manipulating the process Sensors, actuators, valves
Level 2 Monitoring and control PLC, distributed control systems, SCADA
Level 3 Manufacturing operations management MES, quality and maintenance systems
Level 4 Business planning and logistics ERP

The Reference Architecture Model Industrie 4.0 (RAMI 4.0, DIN SPEC 91345, April 2016) adopts this hierarchy from IEC 62264 and adds the product itself and the connected world outside the plant.

How vertical integration works technically

Four mechanisms carry the connection between levels.

  • Open protocols at the equipment: Controllers deliver data through standards such as OPC UA (IEC 62541) or MQTT (OASIS standard since 29 October 2014) instead of proprietary individual interfaces.
  • Aggregation and context: Between equipment and MES, raw values are condensed into events and key figures and assigned to orders, material and equipment.
  • Shared data model: Terms such as order, equipment and material are defined the same way across all levels. ISA-95 provides a widely used vocabulary for this.
  • Data flow in both directions: Confirmations go up, orders, recipes and parameters go down. Both directions are secured and monitored.

Four steps to vertical integration

The sequence is similar in most plants.

  1. Map the data flows

    Which information moves between equipment, MES and ERP today, through which path and with what delay?

  2. Define the transitions

    For each transition between two levels, it is decided which data flows, at which level of aggregation and at which rate.

  3. Start with one process

    A clearly bounded process, such as automatic reporting of quantities to the ERP, is implemented and measured.

  4. Extend step by step

    Further equipment and processes follow. Manual confirmations and individual exports are replaced deliberately.

What vertical integration is not

Four distinctions prevent false expectations.

  • Not the business strategy: In economics, vertical integration means taking over upstream or downstream stages of the supply chain. That is a different topic with the same name.
  • Not all data upwards: The ERP needs aggregated information, not raw signals at millisecond intervals.
  • Not a replacement for MES: Vertical integration connects the levels. The tasks of each level remain.
  • Not the end of network segmentation: Levels stay separated for security reasons. They are connected through controlled transitions, not through an open network.

Typical hurdles in practice

These points slow down vertical integration projects most often.

  • Grown equipment landscape: Controllers from different vendors and years deliver data in different forms or not at all.
  • Missing context: A counter value without reference to order and material is worthless to the ERP.
  • Separate responsibilities: Automation, MES and ERP often sit with different teams with different priorities.
  • Security requirements: Every connection between the production network and the office network has to be planned, secured and monitored.
The honest part

Vertical integration makes processes faster and more accurate, but also more dependent on the data connection. If a transition fails, confirmations are missing in planning and accounting. Buffering, monitoring and a fallback with manual confirmation are therefore part of the implementation.

How pronubes supports

pronubes addresses the transitions between equipment, MES and ERP. The product components have different tasks.

  • pronubes Edge: Edge runs in the plant and connects machines, controllers and IT systems via protocols such as OPC UA, MQTT, REST and SQL. Raw values are aggregated and given context where they are created, and reach MES and ERP in structured form.
  • pronubes Zones: Zones maps sites, production areas and systems as a structure. This structure mirrors the level and equipment hierarchy and keeps the assignment of data consistent across all levels.
  • pronubes Insights: Insights makes the data flows between levels visible during operation. Interruptions and delays become apparent before confirmations are missing in the ERP.
Glossary
Vertical integration
End-to-end connection of the levels of a plant from the equipment to the ERP.
ISA-95
Series of standards for integrating enterprise and control systems, internationally IEC 62264.
Purdue model
Reference model for computer-integrated manufacturing from 1989, basis of the level model.
PLC
Programmable logic controller that controls machines and equipment.
SCADA
System for supervising and controlling technical processes.
MES
Manufacturing execution system for controlling and reporting production.
ERP
Enterprise resource planning, system for business planning and logistics.
RAMI 4.0
Reference Architecture Model Industrie 4.0 according to DIN SPEC 91345.
Asked and answered

Frequently asked questions

What is the difference between vertical and horizontal integration?

Vertical integration connects the levels within a plant, from the equipment to the ERP. Horizontal integration connects process steps, sites and partners along the value chain. Both are characteristics of Industrie 4.0 and complement each other.

What does the automation pyramid have to do with vertical integration?

The automation pyramid shows the levels of a plant, and vertical integration connects them. Modern architectures partly dissolve the rigid pyramid, but the functional levels remain.

Does vertical integration require an MES?

Not necessarily, but often. The MES takes on many tasks between equipment and ERP, such as order management and confirmation. Without an MES, these tasks have to be handled elsewhere.

What role does OPC UA play?

OPC UA is a widely used open standard for providing data from controllers in a structured way. It simplifies the lowest connection in vertical integration, but it does not replace the data model of the upper levels.

How do you start with vertical integration?

With an inventory of today’s data flows between equipment, MES and ERP and a clearly bounded process such as automatic quantity reporting. Further equipment and processes follow.

Get started

From the machine to the ERP, without media breaks.

pronubes connects machines, controllers and business applications and brings production data with context to where it is needed.

pronubes by inray

pronubes is a product of inray Industriesoftware GmbH. Over 30 years of industrial software from Germany. Innovative and reliable for manufacturing companies.

inray