Enquire

CAP-04Capability

Industrial System Integration

Instruments, controllers, analyzers, panels, networks and legacy systems engineered to operate as one coordinated system — across vendors and across generations of equipment.

Request a Technical ReviewView the Engineering Scope
Multi-vendor integration on a supervisory networkSCADA and HMI sit on a supervisory network. Connected to it: a PLC from one vendor and a DCS from another, an analyzer over Modbus, a package unit from a third vendor and a legacy PLC through a gateway. The PLC and the package unit also share a hardwired interface for critical signals, independent of the network. The supervisory network carries protocols such as OPC UA and Modbus TCP, alongside vendor drivers.SCADA / HMISUPERVISIONPLCVENDOR ADCSVENDOR BAnalyzerMODBUSHardwiredinterfaceCRITICALSIGNALSPackage unitVENDOR CLegacy PLCVIA GATEWAYSUPERVISORY NETWORKOPC UA · MODBUS TCPVENDOR DRIVERS
Fig. 04Multi-vendor systems joined on a supervisory network, with a gateway for legacy equipment and hardwired links for critical signals.

01What it covers

One system, built from parts that were never designed together.

Integration scope connects what already exists with what is being added, so that data, control and alarms move reliably across the plant.

A

Field & equipment

  • A.1

    Instruments

    Field signals brought into the control system with correct ranges, units and tags.

  • A.2

    Analyzers

    Values, alarms and status integrated so operators know when a reading can be used.

  • A.3

    Panels

    Control, marshalling and analyzer panels as the physical interface to the system.

B

Control & supervision

  • B.1

    PLC

    Controllers from different vendors exchanging data with each other and with supervision.

  • B.2

    SCADA

    One supervisory view across units, packages and sites.

  • B.3

    HMI

    Operator interfaces consistent with the underlying control and alarm design.

  • B.4

    DCS

    Package units, PLCs and analyzers connected into the distributed control system.

C

Infrastructure

  • C.1

    Networks

    Industrial networks designed for determinism, segmentation and maintainability.

  • C.2

    Legacy systems

    Existing equipment connected through gateways or staged migration instead of forced replacement.

  • C.3

    Plant automation

    Coordinated control and data across the plant rather than islands of automation.

02Why it matters

Industrial performance comes from how systems are engineered and connected.

  • Reduced project fragmentation

    When instruments, controllers, analyzers and networks are engineered together, interfaces are defined once instead of negotiated between separate suppliers.

  • Operational visibility

    Integrated data gives operators one consistent view of the process instead of separate screens for separate packages.

  • Coordinated control

    Systems that share data reliably can act together — interlocks and sequences that span more than one unit or package.

  • Maintainability

    Documented interfaces, consistent tags and a structured network keep the integrated system diagnosable and extendable.

03How Spaaronn approaches it

Understand. Engineer. Integrate. Commission. Support.

Integration begins with an honest picture of what is already installed, and is engineered so the result can be maintained after handover.

  1. 01Understand

    Existing architecture

    Survey the installed systems: controllers, networks, protocols, versions, documentation and the constraints of the running plant.

    Output

    System audit and interface list

  2. 02Engineer

    Interfaces & network

    Define the integration architecture, data exchange, tag structure and network design — including gateways where legacy equipment remains.

    Output

    Integration architecture and data map

  3. 03Integrate

    Configuration & testing

    Configure communication, gateways, controllers and supervisory systems, and test the interfaces before they reach site.

    Output

    Tested interfaces

  4. 04Commission

    Cut-over & verification

    Execute the planned cut-over, verify every exchanged signal end to end and confirm behaviour with operations.

    Output

    Verified system and as-built records

  5. 05Support

    Changes & expansion

    Support troubleshooting, changes and future expansion of the integrated system.

    Output

    Maintainable integrated system

04Project paths

Greenfield and brownfield, engineered differently.

A new plant and an operating plant need different engineering. One is set out from a clean datum; the other is modernized inside a running process, around production.

Greenfield

Build the control and measurement foundation from the start.

On a new plant, instrumentation and control are engineered alongside the process design. The instrument index, I/O list, control philosophy and panel design develop together, so measurement and control are part of the plant rather than added to it later.

SchematicNew site
LTFTPLC
New site — the system is laid out on a clean grid. Clean gridNew systemSignal

Sequence

  1. 01Concept
  2. 02Engineering
  3. 03Procurement
  4. 04Installation
  5. 05Automation
  6. 06Integration
  7. 07Testing
  8. 08Commissioning
  9. 09Training
  10. 10AMC

Engineered in from the start

Typical practice on a new plant:

  • Instrument index and datasheets developed with the process design
  • I/O list and control philosophy agreed before panel build
  • Spare capacity planned into panels and networks
  • Documentation structured for the team that will maintain it
Discuss a Greenfield Project

Brownfield

Modernize existing infrastructure without treating the existing plant as disposable.

On an operating plant, the work starts with what is already there. The existing system is surveyed and assessed as found, and the retrofit and migration are planned around production rather than the other way round.

SchematicOperating plant
LTFTPLCLTFTPLC
Operating plant — the as-found system is migrated in phases. As foundModernizedCut-over

Sequence

  1. 01Survey
  2. 02Assess
  3. 03Plan
  4. 04Retrofit
  5. 05Migrate
  6. 06Integrate
  7. 07Test
  8. 08Commission
  9. 09Support

Minimising disruption

Typical practice on a running plant:

  • Phased cut-over, one area or system at a time
  • Parallel running of old and new systems where feasible
  • Cut-over windows aligned to planned shutdowns
  • A tested fallback to the existing system at every step
Request a Brownfield Review

05Technical translation

Technologies & interfaces

Protocols and interfaces are listed as supported technology families. The right combination depends on the installed base and the plant's network policy.

Protocols

OPC UA
Vendor-neutral, secure data exchange between control, supervisory and information systems.
Modbus RTU / TCP
Widely supported register-based exchange with instruments, analyzers and packages.
PROFINET / PROFIBUS
Industrial Ethernet and its established fieldbus predecessor, common in PLC-based plants.
EtherNet/IP
CIP-based industrial Ethernet used in many PLC architectures.
HART
Device configuration and diagnostics over existing 4⁠–⁠20 mA wiring.

Integration methods

Protocol gateways
Connect serial or legacy devices to Ethernet-based systems without replacing them.
Hardwired interfaces
Simple, deterministic exchange of critical signals between independent systems.
Controller-to-controller
Peer data exchange between PLCs, package units and the DCS.

Network infrastructure

Industrial Ethernet
Managed switches and structured topologies suited to control traffic.
Segmentation
Separating control networks from business networks limits fault propagation and supports security policy.

Technology families describe typical engineering scope. They are not statements of brand partnership, approval or certification.

06What to share with us

Start with what you know.

A complete specification is not required. These details let our team respond with an engineering approach instead of a generic answer — send what you have, and the gaps are closed together.

Discuss This Requirement
Requirement sheet — System Integration6 inputs

  1. Q01Systems to integrate

    Make, model and version of each controller, package or analyzer, where known.

  2. Q02Data to exchange

    Signals, alarms and commands — and the direction each one travels.

  3. Q03Existing network

    Topology, protocols in use and any existing drawings.

  4. Q04Legacy constraints

    Equipment that must stay in service, and why.

  5. Q05Network policy

    IT/OT boundaries and security requirements set by the plant.

  6. Q06Cut-over windows

    When systems can be taken out of service, and for how long.

07Applications & industries

Where it applies.

Process environments and applications where system integration is commonly part of the engineering scope.

Applications

Industries

08Products

Related product categories

Measurement, analytical, final-control and control-system categories commonly specified within this scope.

09Engineering knowledge

Technical resources

Engineering notes on the decisions that commonly come up within this scope.

10Questions

Frequently asked questions

Questions engineers commonly ask about system integration.

What does a typical SCADA integration project involve?

An audit of the controllers and data sources, a defined tag and alarm structure, communication configuration, screen development, testing against the live controllers and a planned cut-over. Most of the effort goes into consistent data definition rather than screens.

Can equipment from different vendors be integrated into one system?

In most cases, yes. Open protocols such as OPC UA and Modbus, protocol gateways and hardwired interfaces allow controllers, packages and analyzers from different vendors to exchange data. The integration design decides which method suits each interface.

How are legacy systems connected without replacing them?

Common approaches are protocol gateways that translate older serial or fieldbus communication, hardwired signals for critical points, and staged migration where parts of the system are replaced over planned shutdowns. The choice depends on the equipment's condition, its support status and its importance to the process.

Should control networks be separated from the business network?

Generally, yes. Segmenting control networks from office and business networks, with controlled points of data exchange, limits the spread of faults and supports the plant's security policy. The design should follow the plant's own IT/OT requirements.

Next steps

Where to go next

  1. 01Related capabilityIndustrial AutomationPLC, HMI, SCADA and DCS engineering for process and machine control, from control panels to plant-wide supervision.
  2. 02Related capabilityInstrumentationProcess measurement and final control elements — selected for the process conditions, installed, calibrated and loop-checked.
  3. 03Solution discoveryStart with the processNot sure which capability fits? Start from what the process needs to measure, control or change.
  4. 04Engineering proofProject record formatThe engineering file each project record follows — from the requirement to what was confirmed at handover.

Integration enquiry

Connecting systems that were never designed to work together?

Share what is installed today, what needs to exchange data and when the plant can accept a cut-over. Our team can help plan the integration or modernization path.

Request a Technical ReviewView All Solutions