Make connected information useful

BMS integration & operator interfaces

Connect compatible plant and systems with a clear purpose, a defined data set and an operator view.

An interface is an operating decision.

Integration should solve a real operating problem: seeing a plant fault, understanding a meter reading or reducing the number of interfaces an operator has to check. We define what information needs to move, in which direction, how often and who is permitted to change it.

01

Define the data

Agree the points, units, status values, alarms and trends that need to be exposed.

02

Set the boundaries

Distinguish read-only monitoring from command and control, including permissions and failure behaviour.

03

Build the operator view

Create an understandable navigation structure, plant graphics and alarm priorities.

The technical scope

Write the behaviour
into the brief.

Metasys supports integration routes for compatible equipment. Suitability depends on the installed products, versions, protocols and licences. A working network connection does not by itself prove that a system interface behaves correctly. Tests should follow the data from the source equipment to the operator screen and, where commands are authorised, back to the controlled equipment. Any fire or life-safety interface must retain the required specialist design and system independence.

Plan the outputs
  • Interface and protocol review
  • Integration responsibility matrix
  • Point mapping and naming conventions
  • Network and access requirements
  • Operator graphics and permissions
  • End-to-end interface testing
Before the survey

Preparing a BMS upgrade?

Use our guide to bring the existing controls, operating objectives and changeover requirements into the project brief.

Read the planning guide
Before we talk

Useful answers.

Have a specific site or building in mind? Start with a conversation.

Talk to the team
Can security information be shown alongside building information?

Where the platforms and project requirements support it, selected integration can be considered. The data, permissions, software and responsibilities must be defined before implementation.

Does integration replace the original system?

Not necessarily. Monitoring another system can leave its native control and safety functions in place. The project needs to define the boundary explicitly.

SYREX Technologies

Discuss an integration.

Tell us the location, the task and the timescale. We’ll connect you with the relevant team.

Discuss your requirement
Across SYREX Group

Partners, memberships
& affiliations.

Johnson Controls
IPSA Corporate Member
BSIA Probationary Member
SafeContractor Approved
RISQS Verified
Jola Certified Partner — 5+ Years
Dahua Technology Integrator Partner

Product image