ARCHITECTURE / OPEN COMMUNICATION

Plan the links
between systems.

A conceptual view of how supervisory systems, controllers, field devices and third-party equipment may communicate. Final topology must be designed and validated for the actual project.

FNG / ARCHITECTURECONCEPTUAL OVERVIEW · NOT FOR CONSTRUCTION

REFERENCE TOPOLOGY / 01

A layered view
of integration.

Protocol choice depends on device capability, distance, network design, cybersecurity policy and the required data points. A gateway does not automatically make every function interoperable.

01 / SUPERVISORY
▤BMS / IBMSOperator workstation · alarms · trends
BACnet/IP · Modbus TCP · approved APIs
02 / CONTROL
⌘HVAC DDCControllers · schedules · sequences
⇄Protocol gatewayOnly where required and validated
BACnet MS/TP · Modbus RTU · hardwired I/O
03 / FIELD & SUBSYSTEMS
❄HVAC plantAHU · chiller · pumps
⌁MetersEnergy · status
▣AccessReaders · door states
◉Video securityCameras · recorder
Conceptual diagram only. Confirm point lists, addressing, segmentation, wiring and fail-safe behavior during detailed design.
A

BACnet IP

Supervisory network

Commonly used to exchange building-automation data over an IP network. Plan device discovery, addressing, BBMD needs where applicable, segmentation, time synchronization and access controls with the network team.

Typical planning questions: Who owns the VLAN? Which devices initiate communication? Which objects and write permissions are required?
B

BACnet MS/TP

Serial field bus

A master-slave/token-passing serial network often used for field controllers. Trunk layout, polarity, termination, biasing, baud rate, device instance and MAC planning all matter.

Typical planning questions: What is the bus length? How many devices? Where are repeaters or end-of-line components needed?
C

MODBUS TCP / RTU

Equipment data

Modbus is frequently used for meters, drives and packaged equipment. Integration depends on the register map, data types, scaling, byte order, polling rate and read/write permissions.

Typical planning questions: Is the register map supplied? What values and units are expected? Who validates the mapping?

BEFORE PROCUREMENT

Start with the interface schedule.

List each subsystem, protocol, device, points, direction of control, owner and acceptance test. This reduces surprises during commissioning.

Discuss an interface review ↗