Home / Solutions / Integration with SCADA, BAS, EMS and MES

Integration with SCADA, BAS, EMS and MES

Integration with SCADA, BAS, EMS or MES centres on consistent data semantics and interface responsibility. The edge layer acquires and converts, the platform maintains the device model and data services, and the existing system consumes or issues data. Interface documentation, point lists, data direction, refresh cycles, time basis, network permissions and joint commissioning are all required; a working communication link does not mean the business integration is complete.

Device-Edge-Cloud CollaborationSystem Integration

Solution overview

The solution connects industrial sites with existing upper-level systems and avoids duplicate points and data silos. The work centres on the point dictionary, service interfaces, test environment, exception handling and system boundaries rather than simply enabling a protocol.

Applicable industries

  • Multi-industry industrial sites
  • Manufacturing plants
  • Industrial parks

Primary user roles

  • Automation engineers
  • System integrators
  • O&M staff

Problems addressed

  • Existing systems form data silos
  • Point lists and data dictionaries are inconsistent, so the interface does not support the business even after completion
  • Data direction, refresh cycles and responsibility boundaries between systems are unclear

Recommended product combination

CW

CW Edge Computing Gateway

Handles field device access, protocol conversion, necessary buffering and data or interface provision to northbound systems

FEXLINK

FEXLINK IoT Platform

Maintains device, point and alarm models and provides project-confirmed API, MQTT or local data services

System architecture and data flow

Integration with SCADA, BAS, EMS and MES System TopologyFour-layer data flow across perception, edge control, platform and application for Integration with SCADA, BAS, EMS and MES.01Perception layer
Field instruments, controllers and subsystems connect to the edge layer through project-confirmed protocols
02Edge / control layer
CW performs acquisition, protocol conversion and necessary local rules, and retains communication status
03Platform layer
FEXLINK unifies the device model and data services and provides data to existing systems through API or mess…
04Application layer
SCADA for monitoring and control, BAS for building services, EMS for energy, MES for production;this solutio…

Perception layer

Field instruments, controllers and subsystems connect to the edge layer through project-confirmed protocols

Edge / control layer

CW performs acquisition, protocol conversion and necessary local rules, and retains communication status

Platform layer

FEXLINK unifies the device model and data services and provides data to existing systems through API or messaging services

Application layer

SCADA for monitoring and control, BAS for building services, EMS for energy, MES for production; this solution provides only the data and interface boundary

Data flow

  1. The business party confirms the target system, data purpose, point list, refresh cycle and control direction
  2. The edge gateway acquires data using field protocols and converts it into unified points
  3. The platform provides data to the target system according to permissions, or receives authorized commands
  4. The interface layer records time, device, point, quality and failure reason
  5. After joint commissioning the interface version is frozen, and changes are implemented through version management

Integration and interfaces

  • Project-confirmed Modbus, MQTT or HTTP API can be used with SCADA, BAS or EMS
  • For MES, business keys, work orders, shifts and output definitions usually also need confirmation; raw device values alone are not sufficient
  • The interface must define read/write direction, data rate, timeout, retry and exception handling
  • Cross-network connections must follow the customer's network isolation, firewall and account permission requirements

Applicable standards

  • Applicable project standards for industrial automation, enterprise information system integration and cybersecurity; the final edition is confirmed against project location, industry and project documents
  • Interface protocols use project-confirmed Modbus, MQTT or HTTP API

Acceptance and delivery boundaries

Suggested acceptance dimensions

  • Confirm the target system list, interface documentation, point lists, data direction, refresh cycles and responsible parties
  • In the test environment, verify data type, unit, time zone, quality and abnormal values point by point
  • Jointly verify disconnection, reconnection, data backfill, interface timeout and failure retry
  • Check account permissions, audit records and that the interface version is frozen

Limitations and exclusions

  • A working communication link is not a completed business integration; an interface without verified point lists and business rules cannot enter a formal process
  • The solution does not replace the control logic, alarm management or safety interlocks of the target system
  • Third-party systems decide whether and how to open their interfaces; their cooperation is required before implementation
  • Interface versions and third-party upgrades may change compatibility and require change management

Operational value

  • Lets field data enter existing business systems without building another acquisition layer
  • Reduces cross-vendor commissioning cost through a point dictionary and responsibility boundaries
  • Retains a consistent data model for later device and application expansion

Selection guidance

  • Define first whether the target system only reads data or also requires control write-back; write-back needs separate safety and permission design
  • Estimate interface effort from point lists and data quality, not from protocol names alone
  • Where several systems use the same data, designate the master source and synchronization strategy to avoid conflicts
  • Before customer system upgrades, confirm interface compatibility and regression test responsibility

Typical implementation patterns

  • Typical implementation pattern: a plant connects distribution and energy data to an existing EMS through an edge gateway and also provides shift-aggregated data to MES; all parties freeze the point list and interface version first, then complete acceptance with joint commissioning and disconnection scenarios. This is an anonymized typical pattern and does not represent a specific customer system or rollout scope.

Before retrofit → With the solution

Before retrofit

  • Existing systems form data silos
  • Point lists and data dictionaries are inconsistent, so the interface does not support the business even after completion
  • Data direction, refresh cycles and responsibility boundaries between systems are unclear

With the solution

  • Lets field data enter existing business systems without building another acquisition layer
  • Reduces cross-vendor commissioning cost through a point dictionary and responsibility boundaries
  • Retains a consistent data model for later device and application expansion

How to evaluate the effect

01

Measurable signal

Field instruments, controllers and subsystems connect to the edge layer through project-…

02

Data source

CW Edge Computing Gateway · FEXLINK IoT Platform

03

Review method

Confirm the target system list, interface documentation, point lists, data direction, refresh cycles and responsible parties

04

Acceptance boundary

A working communication link is not a completed business integration; an interface without verified point lists and business rules cannot enter a formal process

Frequently asked questions

Can it connect directly to SCADA?

Yes, through project-confirmed Modbus, MQTT or API, but target system interface documentation, network permissions and joint commissioning are required. The protocol name alone is not sufficient.

Does a working interface mean integration is complete?

No. Point lists, units, time, quality, refresh cycles, exception handling and business rules must also be verified. Business acceptance is usually more important than the communication test.

Can it integrate with several systems at once?

It can be designed according to the architecture and interface capacity, but the master source, synchronization strategy, access permissions and data responsibility of each system must be defined.

Does it support issuing control commands?

If the product, target and permissions support it, controlled issuance can be designed. Control commands require safety review, identity verification, audit and loss-of-contact handling and must not share unlimited permission with ordinary readings.

What data does MES need?

MES usually needs device or line keys, shifts, work orders, output and related energy, not just raw points. The specific model is defined by the production business process.

Request a matched product combination and project review

Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.

Contact FEXLINK