Define the data
Agree the points, units, status values, alarms and trends that need to be exposed.
Connect compatible plant and systems with a clear purpose, a defined data set and an operator view.
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.
Agree the points, units, status values, alarms and trends that need to be exposed.
Distinguish read-only monitoring from command and control, including permissions and failure behaviour.
Create an understandable navigation structure, plant graphics and alarm priorities.
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.
Use our guide to bring the existing controls, operating objectives and changeover requirements into the project brief.
Have a specific site or building in mind? Start with a conversation.
Talk to the teamWhere the platforms and project requirements support it, selected integration can be considered. The data, permissions, software and responsibilities must be defined before implementation.
Not necessarily. Monitoring another system can leave its native control and safety functions in place. The project needs to define the boundary explicitly.
Tell us the location, the task and the timescale. We’ll connect you with the relevant team.