Article
Consolidating scattered equipment data into a single operating system
FMS Connecting Power, HVAC, Environment, and Safety Facilities
The More Equipment There Is, the More Complex Operations Become
Various facilities and control systems already exist on site. Switchboards and Power Meters manage power status, DDCs and BMSs handle HVAC, fire receivers monitor disaster prevention events, and PLCs and WCSs manage automation facilities. While each system performs its role well, operators must switch between multiple screens to combine different alarms and metrics.
The issue is that the overall operational status cannot be explained solely by whether individual equipment is normal. When the temperature on a specific floor rises, it is difficult to determine from a single screen whether the cause is an indoor unit, a shared outdoor unit, the HVAC main distribution panel, an open door, or a sensor error. Even if conveyor throughput decreases, operators must separately check whether the cause lies with the motor, VFD, sensor, PLC, power supply, or queue.
As facility data becomes scattered across multiple systems and it becomes difficult to link how failures affect space and tasks, the need for a Facility Management System (FMS) has emerged. An FMS does not unconditionally replace existing control systems. Instead, it receives data from each facility, organizes it within the same asset framework and time axis, and connects it so that operators can make decisions at a glance.
Key Change in Operational Perspective |
A Single Operational Model Created by FMS
The basic flow of FMS connects on-site facilities, the control layer, the collection layer, the data layer, and operational screens. It utilizes existing control points such as Power Meters, UPSs, HVAC Controllers, fire receivers, and PLCs, and places RTUs or gateways in required segments. Collected values are stored along with equipment names, locations, importance, and connection relationships, which are then used for alarms, trends, reports, and analysis.
FMS Adds an Operational Perspective on Top of Existing Systems
System | Key Role | Typical Targets |
FMS | Integrated facility/equipment monitoring and operational analysis | Power, HVAC, Environment, Safety, Automation |
BMS | Central control and scheduled operation of building facilities | HVAC, Lighting, DDC, some Power |
SCADA | Real-time monitoring and control of industrial/utility facilities | PLC, Process, Power, Pumps/Valves |
EMS | Energy usage and efficiency management | kW, kWh, Peak, Cost, Carbon |
DCIM | Data center physical infrastructure and capacity management | Rack, UPS, PDU, Cooling, IT Assets |
WMS/WCS | Logistics operations and automation flow management | Inventory, Work Orders, Conveyor, Sorter |
FMS is not a system designed to eliminate BMS or SCADA. BMS excels in HVAC operation and control, while SCADA and PLC handle fast control cycles and safety logic. WMS/WCS are aware of order and logistics flows. FMS receives the necessary data from these systems and reconnects it from a facility and operational perspective.
· Control can maintain the safety logic of existing PLCs, DDCs, and BMSs, while FMS is designed primarily for read-only collection.
· Equipment capable of direct integration is collected via standard protocols, while segments with dry contacts, serial communication, or proprietary protocols are supplemented with RTUs or gateways.
· Even for the same event, the impact on facilities, spaces, and tasks must be displayed together to determine action priorities.
The Route of Facility Data to the FMS
Layer | Key Components | Role |
1. Field | Sensors, Meters, Motors, Circuit Breakers | Generates temperature, power, contacts, and operating status. |
2. Control | PLC, DDC, Power Meter, Fire Receiver, ACP | Organizes on-site signals into control information and equipment status. |
3. Collection | FMS AP, RTU, Protocol Gateway | Performs protocol collection, unit conversion, buffering, and communication failure monitoring. |
4. Data | PG, VM, CH, or Time-series DB | Stores configuration information, events, performance, trends, and statistics. |
5. Operation | Web Dashboard, Mobile Notifications, Reports | Provides operators with current status, failure impact, and action priorities. |
Example of integrating facility data around the FMS collection AP and data layer
Direct Collection and Relay Collection are Used Together
Collection Method | Typical Examples | Application Significance |
Direct Collection | UPS SNMP, BMS BACnet/IP, PLC OPC UA, NVR API | The structure is simple and utilizes the standard features of the equipment |
RTU Collection | Modbus RTU Power Meter, Contact-type Leak/Door sensors, 4–20mA sensors | Aggregates distributed signals locally and transmits them via TCP/IP |
Gateway Collection | Proprietary PLC Protocol, Vendor Serial, Protocol Conversion | Connects segments without standard interfaces to upper systems |
Understanding Protocols Reveals the Collection Structure
In facility monitoring, protocols must be distinguished from physical transmission methods. Modbus RTU typically operates on RS-485 Serial, while Modbus TCP uses TCP/IP over Ethernet. BACnet is also divided into BACnet/IP and BACnet MS/TP, and SNMP is widely used in UPSs, PDUs, and network equipment.
Protocol | Transmission Method | Mainly Used Equipment | Features |
Modbus RTU | RS-485/RS-232 | Power Meters, AHF, Generators, ATS, Sensors | Register-based, simple and universal |
Modbus TCP | Ethernet / TCP | Power Meters, PLCs, Gateways, UPSs | Collects Modbus data over IP networks |
BACnet/IP | Ethernet / UDP | BMS, DDC, AHU, Chillers, HVAC | Object-based building automation standard |
BACnet MS/TP | RS-485 | DDC, HVAC Controllers, Sensors | Local BACnet Serial network |
SNMP | Ethernet / UDP | UPS, PDU, RTU, Switches, Servers | Collects status, performance, and trap events |
OPC UA | Ethernet / TCP | PLC, SCADA, Logistics Automation | Integrates tags and events in a vendor-neutral manner |
REST API / MQTT | HTTPS / TCP | NVR, WCS, AGVs, IoT Platforms | Integrates with upper systems, Cloud, and events |
DI/DO·AI | Dry Contact / 4–20mA / 0–10V | Leak, Door, Fire, Pressure/Flow Sensors | Collects digital and analog signals from RTU/PLC |
Communication ports alone are not enough |
How Power and Power Quality are Read
A distribution panel does not generate power data on its own. A Power Meter installed in the panel receives CT and voltage signals to calculate voltage, current, active power, energy consumption, power factor, frequency, and more. For distribution panels without a Power Meter, measurement points can be created by adding CTs and Digital Power Meters.
Peak and load factors can use Demand values provided by the meters, or the FMS can store time-series data to calculate daily, weekly, and monthly maximum values and utilization rates relative to the rated capacity. In terms of power quality, AHF's THD-V, THD-I, TDD, compensation status, and Faults must be viewed together to distinguish harmonic mitigation effects from equipment status.
Example configuration for collecting distribution panel Power Meter and AHF data into RTU/FMS
Target | Key Metrics | Operational Meaning |
Distribution Panel/Power Meter | V, A, kW, kWh, PF, Hz, Demand, Peak, Load Factor | Overload, voltage anomaly, and energy usage analysis |
AHF | THD-V, THD-I, TDD, Compensation Current, Run/Stop, Fault, Internal Temp | Distinguishing harmonic mitigation effects from equipment anomalies |
UPS/PDU | In/Output V & A, Load Factor, Battery, Bypass, Runtime | Verifying the stability of uninterruptible power and downstream loads |
Generator/ATS | Operating Status, Source, V & Hz, Fuel, Transfer Status | Verifying the emergency power transition process during outages |
Monitoring Constant Temperature and Humidity Equipment
Constant temperature and humidity air conditioners are used in electrical rooms, telecom rooms, server rooms, and critical equipment spaces where more precise temperature and humidity control is required compared to general HVAC. Rather than displaying only the current temperature and humidity, control performance and maintenance needs must be assessed by looking at deviations from setpoints, Compressor/Fan operating status, humidification/dehumidification status, run time, starts count, and recurring alarms.
Examples of key status and control metrics for constant temperature and humidity units
Metric/Calculation | Formula or Judgment Criteria | Operational Utilization |
Temperature Deviation | Current Temp - Setpoint Temp | Verifying cooling/heating control performance and sensor anomalies |
Humidity Deviation | Current Humidity - Setpoint Humidity | Verifying humidification/dehumidification performance and condensation risk |
Supply/Return ΔT | Return Temp - Supply Temp | Tracking changes in heat exchange and cooling capacity |
Runtime / Starts Count | Accumulated Compressor/Fan hours and Start Count | Analyzing preventive maintenance cycles and short-cycling |
Availability | Normal Runtime / Total Operating Time × 100 | Evaluating environmental maintenance reliability in critical spaces |
Condensation and Leak Risk Monitoring
It is recommended to manage condensation and leaks separately from the perspective of equipment protection rather than just the working environment. Condensation risk is determined by comparing the Dew Point, calculated from air temperature and relative humidity, with the surface temperatures of distribution panels, ducts, and pipes. The FMS manages the difference between the surface temperature and the dew point as the Condensation Margin, and actual moisture occurrence is verified alongside condensation/leak sensors or Leak Cable Events.
Recommended Derivative Metric |
Example of dew point and condensation risk calculation using temperature, humidity, and surface temperature
Working Environment, Temperature, and Humidity Monitoring
Working environment monitoring is the area of measuring spatial conditions. The Heat Index, calculated from temperature and relative humidity, is useful for comparing the working environment during hot seasons with the effects of HVAC application. Incorporating CO₂, fine dust, and airflow allows for a more multi-dimensional evaluation of environmental quality by zone. If airflow velocity, mean radiant temperature, clothing insulation, and metabolic rate are secured, this can be expanded to thermal comfort indices such as PMV and PPD.
Derivative Metric | Input Data | Utilization |
Heat Index | Temperature + Relative Humidity | Comparing hot-season working environments and cooling effectiveness |
Dew Point | Temperature + Relative Humidity | The temperature at which moisture in the air begins to condense |
Condensation Margin | Surface Temp - Dew Point | Pre-judging condensation risk on distribution panels, ducts, and pipes |
Temp/Humidity Deviation | Current Value - Setpoint | Verifying constant temperature and humidity unit control performance and sensor anomalies |
Supply/Return ΔT | Return Temp - Supply Temp | Checking HVAC heat exchange and cooling capacity trends |
PMV / PPD | Temp, Humidity, Airflow, Radiant Temp, Clothing, Activity | Evaluating complex thermal comfort and predicted percentage of dissatisfied occupants |
Example of calculating thermal comfort indices using complex environmental data such as temperature, humidity, and airflow
HVAC and Cooling Facility Monitoring
HVAC monitoring is not just about checking the operating status of a single indoor unit. In a system air conditioner environment, IDU, ODU, PI485, ACP, and TMS (Total Maintenance System) should be viewed together. For large HVAC facilities, AHU, Chiller, FCU, and Fan/Pump must be interpreted as a single cooling system.
ACP aggregates the status of multiple indoor and outdoor units, and the on-site TMS manages remote maintenance, errors, and operation history. If the TMS provides an external API or a standard interface, it can be integrated into the FMS through it; otherwise, the ACP's BACnet/IP or Modbus TCP interface is utilized directly. In environments without ACP/TMS, a separate collection path using PI485 and LG Modbus Gateway is considered.
Example of HVAC data integration depending on the presence of ACP and TMS
Target | Key Metrics | Operational Meaning |
IDU | Run/Stop, Mode, Room Temp, Setpoint Temp, Air Volume, Filter, Error | Checking cooling status and working environment by zone |
ODU | Operating Status, Compressor/Fan, Outdoor Temp, Capacity, Defrost, Error | Understanding the shared refrigerant system and the impact scope of multiple IDUs |
ACP/TMS | Number of connected devices, Comms Status, Run/Error History, Remote Check Status | Verifying whether central control and maintenance data are collected normally |
AHU/Chiller | Supply/Return Temp, Valves, Fan/Pump, Chilled Water Temp, Pressure, Fault | Checking heat source and airflow of large HVAC systems |
Environmental Sensor | Temp, RH, CO₂, Fine Dust, Heat Index | Analyzing working environment, ventilation, and cooling effectiveness |
Integrated Control Including Logistics Automation Facilities
In distribution centers, a stoppage of conveyors and sorters goes beyond a facility failure and leads directly to shipping delays. Photo Sensors, Jam Sensors, Encoders, Motors, VFDs, and E-Stops are connected to the PLC, which handles the fast control cycle and safety logic. The FMS collects status and operational metrics from the PLC or WCS in a read-only manner and analyzes them alongside facility data.
The FMS does not need to directly access PROFINET or EtherNet/IP control traffic deeply. Whenever possible, it uses the PLC's OPC UA/Modbus TCP interface or an Industrial Gateway as a boundary to protect the stability of the control network and isolate failure domains.
Example of integrated control of automation facilities connecting Conveyor, PLC, Gateway, and FMS
Perspective | Key Metrics | Operational Meaning |
Line/Zone | Run/Stop, Line Speed, Queue, Jam | Checking line operating status and bottleneck zones |
Motor/VFD | Current, Frequency, RPM, Overload, Fault Code | Analyzing drive unit anomalies and causes of stoppage |
Sensor | Photo/Jam/Proximity Status, Count, Comms Status | Verifying material flow and sensor malfunctions |
PLC/Safety | CPU Run, Program Fault, E-Stop, Safety Relay | Checking the control layer and safety status |
Operational KPI | Throughput, Availability, MTBF, MTTR | Converting facility failures into logistics operational impact |
From Alarms to Root Causes and Impacts
The value of FMS is not just in reducing the number of alarms. It lies in connecting events from different facilities with time, location, power systems, HVAC systems, and automation lines to explain "what occurred first and how far the impact reaches."
Phenomenon | Verification Flow | Operational Interpretation |
3F High Temp | IDU Stop → Shared ODU Error → HVAC Main Power → Door Open → Sensor Error | Simultaneously verifying the cause of the zone temperature rise in HVAC, power, and environment |
Conveyor Throughput Drop | Jam Sensor → VFD Overcurrent → Motor Overload → PLC Fault → Power Quality | Analyzing the correlation between facility stoppage and logistics queue growth |
Power Peak Rise | Automation Utilization → HVAC Load → Hourly Power → Outdoor Temp | Identifying causes of peak occurrence and optimizing operational schedules |
Fire Event | AI CAM/NVR → Fire Receiver → Zone → Adjacent Electrical/Automation Facilities | Verifying false alarms and determining affected zones, evacuation, and shutdown scopes |
Basic Condition for Event Correlation Analysis |
Distinguishing Between Communication Failures and Facility Failures
Just because collected values are interrupted does not mean the facility has stopped. The FMS must distinguish and display Equipment Faults, Controller Faults, Network Down, Polling Timeouts, and degraded data quality. Without this distinction, actual facility failures and monitoring blind spots will be treated as the same alarm.
Configuring a Logistics Center as a Single Site Topology
The example below is a conceptual diagram representing the facilities of a logistics center with 5 floors and basement mechanical/electrical rooms as a single Site Topology. Rooftop HVAC outdoor units and cooling towers; working floor FCUs, constant temperature and humidity units, temperature/humidity/smoke/heat detectors, sprinklers, and conveyors; and 1st floor and basement switchboards, UPS, AHF, generators, pumps, fire pumps, PDU/RPP, and battery facilities are connected spatially and systematically.
The goal is not to convert all facilities on-site to the same protocol. The core is to accommodate BACnet/IP, Modbus RTU/TCP, SNMP, OPC UA, DI/AI, and APIs according to facility characteristics, and to standardize data provided by ACP, TMS, DDC, PLC, RTU, and Gateway into the FMS asset model.
Example of logistics center FMS integrated control representing power, HVAC, environment, safety, and automation together
Modeling Perspective | Included Facilities | FMS Representation |
Space | Rooftop, Work Areas, Facility Rooms, Electrical Rooms, Mechanical Rooms, Automation Lines | Displays the actual location and affected zone of facility events |
Power | Switchboards, UPS, Generators, AHF, PDU/RPP, Batteries | Power flow, peaks, power quality, emergency power status |
HVAC/Environment | HVAC, ACP/TMS, AHU, Constant Temp & Humidity units, Temp/Humidity, CO₂, Leaks, Condensation | Analyzes working environment and facility environment together |
Safety | Fire Receivers, Smoke/Heat/Flame Detectors, Sprinklers, Fire Pumps, Doors | Connects detection to disaster prevention facility operation and response actions |
Automation | Conveyors, Sorters, PLCs, VFDs, Sensors | Links facility operation with throughput, jams, and failure history |
Prediction and Optimization Created by Time-Series Data
When power, temperature/humidity, harmonics, operating status, faults, and throughput are accumulated over time in the FMS, patterns can be compared beyond simple threshold monitoring. By learning the normal range for each facility and looking at changes in multiple metrics together, anomalies can be found earlier and inspection priorities can be established.
Expansion Area | Analysis Content | Utilization |
Anomaly Detection | Detects current, temperature, and operating status deviating from usual patterns | Captures early changes that fixed thresholds might miss |
Predictive Maintenance | Analyzes motor current, vibration, temperature, and fault patterns | Establishes inspection and parts replacement plans before failures occur |
Peak Prediction | Combines time of day, workload, outdoor temperature, and HVAC load | Manages contract power exceedance and energy costs |
Condensation Risk | Analyzes Dew Point, surface temperature, and leak events | Pre-detects condensation risks around distribution panels and ducts |
Root Cause | Performs correlation analysis of power, HVAC, comms, and automation events | Consolidates redundant alarms focusing on root-cause facilities |
Operational Optimization | Compares throughput, environmental, and power data together | Balances cooling effectiveness with energy usage |
The Operational Dashboard Must Answer Questions
Rather than just listing facility types, the initial screen must answer: "Is the center operating normally right now?" The top section should feature Site Health, Critical Alarms, power/peak, HVAC normal rate, automation utilization, and working environment risk zones. The center represents the floors, zones, lines, and facility relationships, while the bottom connects trends, alarm timelines, MTBF/MTTR, and energy analysis.
Screen Area | Displayed Content |
Top KPI | Site Health, Critical Alarms, Current Power, Peak, HVAC/Automation Normal Rate |
Space/Topology | Floor, Zone, Line, Power System, HVAC System, Facility Connection Relationships |
Trend | Power, THD/TDD, Temp/Humidity, Throughput, Utilization |
Event | Occurrence/Acknowledge/Recovery Time, Severity, Assignee, Affected Facilities |
Analysis | Candidate Causes, Recurring Failures, MTBF/MTTR, AI Insights |
Polestar FMS Dashboard Examples
Conclusion
The starting point of facility monitoring is not about collecting as much data as possible. It is about first defining which facilities support which spaces and tasks, and then selecting data that can explain those relationships. When power, HVAC, environment, safety, and automation are connected as a single Site Topology, alarms cease to be simple numbers and become the basis for operational decision-making.
FMS is also not a system designed to unify different protocols into one. It must accommodate Modbus, BACnet, SNMP, OPC UA, API, and DI/AI suitable for each facility, and combine direct collection with RTUs and gateways appropriately. Time-series data accumulated this way can be expanded to anomaly detection, predictive maintenance, peak prediction, and energy optimization.
Ultimately, the purpose of FMS does not stop at just looking at facilities. It lies in helping operators determine more quickly and accurately whether facilities are operating stably, where a failure originated, what operations it affects, and what needs to be inspected next.
References
· Modbus Organization — Modbus Application Protocol Specification
· ASHRAE Standard 135 — BACnet, A Data Communication Protocol for Building Automation and Control Networks
· OPC Foundation — OPC Unified Architecture Specifications
· IETF RFC 3411–3418 — SNMP Architecture and Protocols
· LG Electronics / Maintenance Operation Data — Installation and integration documents related to ACP, PI485, TMS, and Modbus Gateway
· NOAA/NWS — Heat Index Calculation
· ASHRAE Handbook — Dew Point and Condensation Fundamentals
Author: DW Jang | NKIA Lab
