Skip to content

Search ARSTEMA

Type a chapter, term, symptom, or tool.

    Buildings & Facilities · Chapter 32Applied

    By Kurnia · Published November 13, 2026 · Version 1 · 21 min read

    Building management system (BMS)

    three-layer architecture, field controllers and operator workstations, data points and the points list, input and output types, point naming, and the limits of technician authority

    At seven in the evening, the BMS screen of a hotel shows the supply fan of the ballroom air handling unit as running, while the wedding guests are getting hot and the fan belt has snapped. What the screen shows is the command, not the feedback, because the points list contains no airflow status point. This chapter covers the building management system from the building technician’s side: what a BMS does and what it does not, the three-layer architecture from the operator workstation down to the sensor, field controllers that keep working when the network fails, data points and input and output types, the points list and the handover documents, point naming, and basic security habits. Its basis is NIST and GSA guidance on building automation systems, the NIST SP 800-82 guide to operational technology security, and the DOE FEMP operations and maintenance guide, all United States documents. Changing controller programs, safety settings, accounts, passwords, and network configuration is set out as the authority of the systems integrator or the IT manager.

    Section you’re reading: Chapter opening

    At 19:10, a wedding reception in a hotel ballroom has just started and the head waiter reports that the room is getting hotter. The duty technician opens the BMS screen in the control room. The graphic of the ballroom air handling unit shows the supply fan in green with the word “running”, the chilled water valve 100 percent open, and the room temperature at 27.5 °C and rising. In the plant room, the fan turns out to be still: its belt has snapped, while the motor spins without load.

    The screen is not lying, but it shows something other than what the operator assumes. The point displayed as “running” is the command from the controller to the fan contactor, not proof that air is moving. The points list for that unit contains no fan differential pressure switch, so no point at all can tell a turning fan from a still one. A technician who understands the BMS architecture, the point types, and the points list will be suspicious as soon as the temperature rises while the fan is “running”, and will look for evidence in the field before concluding anything.

    Scope

    This chapter covers the building management system from the building technician’s side: what a BMS does, its architecture, field controllers and operator workstations, data points and input and output types, the points list, point naming, and the limits of authority. The technician reads, records, reports, and carries out the work that is assigned. The documents used are guidance from United States agencies (NIST, GSA, and DOE); in Indonesia, the system layout and the authority in a given building follow that building’s handover documents and the procedures of its building management.

    PLCs are covered in Chapter 63 · Electrical & Control to Chapter 66 · Electrical & Control, discrete sensors in Chapter 59 · Electrical & Control, process sensors, transmitters, and the 4 to 20 mA loop in Chapter 60 · Electrical & Control, final control elements and PID in Chapter 62 · Electrical & Control, air handling units in Chapter 16 · Fluids & Thermal, and chillers in Chapter 17 · Fluids & Thermal. Fire alarms in Chapter 19 to Chapter 23 are a separate system that the BMS does not replace. The BACnet and Modbus protocols are in Chapter 104 · Electrical & Control on building communication protocols, alarms, trends, schedules, and manual overrides in Chapter 33 on alarms, trends, and schedules in the BMS, and energy meters in Chapter 34 on building energy dashboards.

    Work outside the building technician’s authority: changing controller programs and sequences of operation, changing settings related to safety, creating or changing accounts and passwords, changing network configuration and device addresses, taking points out of service, and disabling, delaying, or hiding alarms. That work belongs to the systems integrator and the building’s IT manager. Opening a controller panel that contains 230 V terminals is work for an electrician with energy isolation as in Chapter 76 · Electrical & Control on safe work.

    What a BMS does

    A building management system (BMS) is a network of microprocessor-based controllers that monitors and controls building equipment, mainly air conditioning, together with data logging and notification of staff. Other documents call it a building automation system (BAS) or an energy management and control system. NIST SP 800-82 classifies building automation systems as operational technology, that is, systems that control physical processes, and lists their most common functions: maintaining room conditions for occupant comfort, reducing energy use and operating costs, recording historical data such as temperature and humidity, and monitoring equipment and alerting staff when there is a failure or an alarm.

    The core of a BMS is direct digital control (DDC): the controller measures a quantity, compares it with a setpoint, and then sends a signal to the controlled equipment. The DOE FEMP operations and maintenance guide names three hardware elements of a building control system, namely sensors, controllers, and controlled devices such as dampers, control valves, fans, and pumps. The same guide states that installing a system alone does not guarantee savings; correct installation and commissioning are prerequisites, and sensors out of calibration can waste energy for years without being noticed.

    There are things a BMS does not do in the buildings this chapter covers. A BMS does not replace the fire alarm panel, high-temperature cutouts, safety pressure switches, or emergency stop buttons. Protection of that kind is built into the equipment hardware, as covered in Chapter 65 · Electrical & Control on hardware interlocks and fail-safe inputs, and the BMS at most reads its status. When the BMS displays a fire alarm status, the source of truth is still the fire alarm panel.

    Three-layer architecture

    A BMS is usually arranged in three layers. The names differ between documents, but the division of work is similar.

    1. Management layer: operator workstations, servers, and the trend database. This is where graphics, alarm lists, schedules, and reports are displayed.
    2. Automation layer: building controllers that run the sequences of operation of large equipment such as the chiller plant and air handling units, collect data from the controllers below them, and hold schedules.
    3. Field layer: field controllers for small equipment such as VAV boxes or fan coil units, together with the sensors and actuators connected to their inputs and outputs.

    The GSA guide prepared by NIST for specifying BACnet systems describes device profiles that fit this division: the operator workstation as the operator’s window into the system, not intended to perform direct digital control, the building controller as a general-purpose, field-programmable controller, the advanced application controller and the application specific controller with increasingly limited resources, and then the smart actuator and smart sensor as the simplest devices. That guide also states that, because of its cost, Ethernet is generally used as the backbone network connecting workstations and supervisory controllers, while the slower MS/TP network is used for unitary controller networks. The 2024 GSA technical guide names an IP-based automation level and a field level as two separate levels in the scope of its system replacement.

    This division decides what happens when something fails. A field controller holds its own program and keeps controlling its equipment when the link to the upper layer is lost. The GSA technical guide asks for unitary controllers to be tested by shutting down their supervisory controller and observing that the air handling unit or plant keeps operating at the defined last known safe state. Conversely, an operator workstation that fails does not stop room cooling, but it leaves staff blind: alarms do not appear and trends stop being recorded. A value that is still shown on the screen after communication is lost is stale data, as covered in Chapter 5 · Computational on field device data communication.

    Field controllers and operator workstations

    A field controller is a controller mounted near the equipment that reads sensors through its input terminals, drives actuators through its output terminals, and runs the control program for that equipment. Field controllers usually sit in a small panel in the plant room, above the ceiling near a VAV box, or in the air handling unit panel.

    An operator workstation is a computer with software that displays BMS data to staff and accepts commands from staff. The operator workstation profile in the GSA guide includes presenting data in reports and graphics, monitoring the values of all objects, changing setpoints and parameters, acknowledging alarms, changing schedules and trend parameters, and even backing up and restoring the configuration of other devices. The software can do far more than any one person sitting in front of it is allowed to do.

    For that reason the system distinguishes levels of operator authority. The GSA guide notes that assigning different levels of authority to different personnel is mainly a matter of configuring the workstation software, and that devices can be configured to accept alarm acknowledgments only from specific personnel. A duty technician’s account is usually enough to view graphics, read values, acknowledge alarms according to procedure, and print reports. Functions that appear in the menu but are not part of the technician’s duties are still not used, even if the account does not refuse them.

    Data points and input and output types

    A point is a single quantity that the BMS reads or writes, for example the supply air temperature, the fan run command, or the valve position. The term point is used for sensor inputs, control outputs, and control values alike, with characteristics that differ by manufacturer; BACnet replaces it with standard objects, each with a set of standard properties, and it is through those properties that an object is read and controlled by other devices. Chapter 104 · Electrical & Control on building communication protocols covers objects and properties from the protocol side; here the point types that appear in a points list are enough.

    Point typeBACnet object abbreviationExample in a building
    Analog inputAIsupply air temperature from a thermistor, duct static pressure
    Analog outputAOchilled water valve position 0 to 100 percent
    Binary inputBIfan differential pressure switch, pump status contact
    Binary outputBOfan run command to the contactor
    Analog value and binary valueAV, BVroom temperature setpoint, occupancy mode
    Multi-stateMI, MO, MVunit mode: off, cooling, ventilation

    The example uses of each object type in the table follow the description of the standard BACnet objects. Analog and binary inputs and outputs are hardware points, because they are connected to controller terminals and wired to the field. Analog, binary, and multi-state values are software points, that is, values inside the program, such as a setpoint or a mode, with no wire to the field. The physical signal behind an analog input, for example a 4 to 20 mA loop, is covered in Chapter 60 · Electrical & Control on process sensors and transmitters.

    The difference that most often misleads is the one between command and feedback. The binary output “fan run command” only states what the controller is asking for. Evidence that the fan is moving air comes from a separate binary input, for example a differential pressure switch across the fan, or from the motor current. BACnet provides a feedback value property on binary outputs for this purpose, and the GSA guide asks designers to specify it where appropriate for the application. The opening case happened because that feedback point never existed.

    Every object carries more than one number. Besides the present value (Present_Value), an analog input object carries units, a description, status flags that mark the in-alarm, fault, overridden, and out-of-service conditions, and an out-of-service property (Out_Of_Service). When an object is taken out of service, its present value is decoupled from the process it represents and can be forced to another number. The GSA guide calls this capability useful during commissioning and diagnosis. For the technician, an out-of-service or overridden flag is a sign that the number on the screen is not a sensor reading. Taking a point out of service is work for the integrator, not for the technician.

    The points list and handover documents

    A points list is a table of all the points of a BMS, one row per point, that serves as the dictionary between the screen, the program, and the wiring in the field. The GSA guide asks for the points list from the controls contractor to contain point names that follow the specified convention, as well as a BACnet object description giving the object ID and device ID for each point. For the handover documents, the guide asks for a points list that contains the name and description, display units, alarm limits and definitions, and the object description, together with as-built drawings showing the architecture, configuration, and input and output points, documentation of non-standard objects, and program descriptions. Those documents are updated every time the system is changed.

    For the technician, the points list answers questions that the screen cannot: which sensor this point comes from, on which terminal, in which units, and whether it has feedback. Columns that are useful when working in the field:

    1. Point name and a description in words.
    2. Point type (AI, AO, BI, BO, AV, BV, or multi-state) and object number.
    3. The controller and its physical terminal, for hardware points.
    4. Units and range, for example °C, Pa, or percent.
    5. State texts for binary points, for example “running” and “stopped”.
    6. Alarm limits, if the point has an alarm.
    7. Field device: the type of sensor or actuator and its location.

    The points list is also used to work out the size of the system and the spare capacity of the controllers. The sample scope of work in the GSA technical guide for an eight-story building contains one chiller and boiler plant with 175 data points, 9 air handling units with 40 data points each, and 340 VAV boxes with 12 data points each. The same guide asks for a record showing that 30 percent spare capacity remains on the DDC controllers for future expansion, as required by the GSA P-100 facilities standard. That figure is a requirement of a United States agency; in other buildings, spare capacity is set in the project specification.

    Point naming

    The GSA guide recommends names that are as meaningful as possible within the available length, so that a name such as AHU1.STEMP is better than A1ZXC5, and recommends names built from facility, system, and point components. The example in that guide, BLDG226.AHU1.MA_TEMP, means building 226, air handling unit 1, mixed air temperature, and the convention can be extended with areas within the facility and subsystems within a system. The same guide asks that names can hold at least 50 characters, use standard abbreviations set for all vendors, and be assigned according to the facility manager’s convention rather than left for the manufacturer to choose. GSA now sets out its point naming and tagging convention in a data normalization document for building automation systems that contractors are required to follow.

    A good point name meets three conditions. First, it is unique: two points must not have the same name anywhere in the building, because alarms and reports use that name. Second, it is readable: someone who has never seen the system can guess its location and quantity with the help of the abbreviation list. Third, it is consistent: the supply air temperature of every air handling unit uses the same abbreviation, so reports can be built by filtering names.

    The building technician does not rename points, because names are used by programs, graphics, alarms, and trends. What the technician does is record names that are misleading, duplicated, or do not match the field, and report them so that the integrator corrects them through change control.

    Limits of technician authority and basic security habits

    The division of work around the BMS can be summarized in one table. The table is built from the boundaries of the building automation chapter series; the procedures of a given building can be stricter.

    WorkBuilding technicianSystems integrator or IT manager
    Reading graphics, values, status, and trendsyesyes
    Comparing BMS readings with field instrumentsyesyes
    Recording and reporting findingsyesyes
    Acknowledging alarms according to procedureyes, when assignedyes
    Replacing a failed sensor with the same type, after isolationwhen assigned and with a work permitsets up and rechecks it in the system
    Changing programs, sequences of operation, or safety settingsnoyes
    Taking points out of service or forcing valuesnoyes
    Creating accounts, changing passwords, changing access rightsnoyes
    Changing device addresses and network configurationnoyes
    Disabling, delaying, or hiding alarmsnoaccording to building management procedure

    Sensor calibration is an area that is often overlooked. The DOE FEMP guide lists the sensors that most need calibration, including outside air, mixed air, return air, supply air, chilled water, and space temperature, humidity sensors, and static pressure transmitters, and asks for sensor and actuator calibration to be part of every maintenance program. The technician compares the BMS reading with a reference instrument and reports the difference; setting a correction value in the controller is done by whoever has authority over the program.

    Cybersecurity in this chapter is limited to basic habits. NIST SP 800-82 notes that vendor default passwords are easy to find in product manuals that are also available to attackers, so using them greatly increases vulnerability, and that unsecured USB ports allow unauthorized devices to be connected. The habits that follow are simple: passwords are not stuck on panels or shared through messages, accounts are not lent, the operator workstation session is locked when left, and USB media or personal laptops are not connected to the operator workstation or the BMS network. A default password still in use, a shared account, or a modem connected to a panel is reported to the IT manager, not fixed by the technician.

    Worked example

    The numbers in the examples below are practice figures unless their origin is stated.

    Example 1: number of points from the GSA scope of work. The GSA sample scope of work contains a chiller and boiler plant with 175 points, 9 air handling units with 40 points each, and 340 VAV boxes with 12 points each. The total is 175+9×40+340×12=175+360+4,080=4,615175 + 9 \times 40 + 340 \times 12 = 175 + 360 + 4{,}080 = 4{,}615 points. The VAV boxes contribute 4,080/4,615=0.8844{,}080/4{,}615 = 0.884, that is, 88.4 percent of the points, even though each box is small. The field controllers for this large number of small units are what make the field layer the largest part of the system.

    Example 2: controller spare capacity. The controller of a hotel air handling unit has 32 input and output terminals, and its points list uses 23 of them. The rest is 32−23=932 - 23 = 9 terminals, or 9/32=0.2819/32 = 0.281, that is, 28.1 percent. If the project specification asks for 30 percent spare capacity as in the GSA guide, the largest number of terminals that may be used is ⌊0.7×32⌋=22\lfloor 0.7 \times 32 \rfloor = 22, so the controller is one terminal short of the requirement. The technician records this figure at handover; adding a module is the integrator’s decision.

    Example 3: command and feedback. In the opening case, the fan command point has been at running since 18:00. If a feedback point from the differential pressure switch existed, and the sequence of operation allowed a 60-second delay for the fan to reach flow, then by 18:05 the feedback should have been running. Feedback still at stopped 5×60−60=2405 \times 60 - 60 = 240 seconds after the delay limit means that command and reality do not match. Without a feedback point, the mismatch only shows up in the rising room temperature, more than an hour later.

    Example 4: building and checking a point name. The east building uses the abbreviation GTM, floor 3 is written L03, the second air handling unit AHU02, and the supply air temperature SAT. The point name is GTM.L03.AHU02.SAT, which is 3+1+3+1+5+1+3=173 + 1 + 3 + 1 + 5 + 1 + 3 = 17 characters, far below the 50 characters recommended by the GSA guide. If another vendor names the same point AHU-2-SAT without building and floor, that name will be the same as the second unit in the west building, and the alarms of the two cannot be told apart.

    Example 5: comparing the BMS reading with a reference instrument. The meeting room temperature sensor reads 23.8 °C in the BMS, while a reference thermometer placed next to the sensor shows 25.1 °C after settling. The difference is 23.8−25.1=−1.323.8 - 25.1 = -1.3 K, so the BMS reads low. With a difference limit of 0.5 K set by the building’s maintenance procedure, this finding is reported for calibration. Because the controller holds the room at a setpoint of 24 °C according to that sensor, the actual temperature is about 24+1.3=25.324 + 1.3 = 25.3 °C, which explains the guests’ complaint.

    Example 6: a field controller that drops off. One hotel floor is served by 36 VAV boxes with 12 points each. If the network on that floor fails, 36×12=43236 \times 12 = 432 points become stale data at the operator workstation. Out of the 4,615 points in Example 1, that is 432/4,615=0.094432/4{,}615 = 0.094, that is, 9.4 percent. The VAV boxes keep controlling the rooms with their own programs, but while the link is down, the values on the screen for that floor are not used for decisions; the technician checks the rooms directly.

    Stop conditions

    1. The BMS screen shows equipment running, but field measurement or observation shows the equipment still or not moving air or water: do not rely on the screen; report to the supervisor, and the equipment check is handed to a mechanical technician.
    2. The task would require changing a controller program, a sequence of operation, a protection setting, or a forced value: stop and hand it over to the systems integrator.
    3. The technician is asked to create an account, use someone else’s account, disclose a password, or connect a laptop, modem, or USB media to the operator workstation or the BMS network: refuse and report to the IT manager.
    4. The technician is asked to disable, delay, or hide an alarm, including an alarm considered a nuisance: do not do it; hand it over to the supervisor and the integrator according to the building’s alarm procedure.
    5. A point on the screen relates to the fire alarm, smoke control fans, or life safety equipment: do not issue commands from the BMS; the status is checked at the fire alarm panel and handed over to the fire system technician.
    6. The points list, point names, or as-built drawings do not match the equipment in the field: do not guess the connections; record and report to the integrator for updating.
    7. The check would require opening a controller panel that contains 230 V terminals or the contactor supply: hand it over to an electrician with energy isolation and a work permit.

    Common misinterpretations

    Guess what’s wrong first, then open the explanation.

    Common misconception

    A running status on the screen means the machine is running.

    Why is it wrong?

    That point may be a command, and only a feedback point or a field observation proves flow. The points list shows which points are commands and which are feedback.

    Common misconception

    If the operator workstation fails, the building is out of control.

    Why is it wrong?

    Field controllers and building controllers hold their own programs and keep working. What is lost is the staff’s view: alarms, graphics, and trends.

    Common misconception

    A BMS can replace the fire alarm panel.

    Why is it wrong?

    Fire alarms and equipment protection are separate systems with their own rules. The BMS at most reads their status.

    Common misconception

    If the menu opens, it may be changed.

    Why is it wrong?

    Operator workstation software can do far more than the duties of any one user. Authority is set by procedure and role, not by what the account does not refuse.

    Common misconception

    A point name only needs to make sense to whoever created it.

    Why is it wrong?

    Names are read by everyone who receives an alarm or a report, including the next vendor. A name that is not unique or not readable makes two pieces of equipment impossible to tell apart.

    The sensors and transmitters behind analog inputs are covered in Chapter 60 · Electrical & Control, final control elements and PID in Chapter 62 · Electrical & Control, and PLCs in Chapter 63 · Electrical & Control to Chapter 66 · Electrical & Control. The equipment that a BMS most often controls is covered in Chapter 16 · Fluids & Thermal on air handling units and Chapter 17 · Fluids & Thermal on air-cooled chillers. How points move between devices is covered in Chapter 104 · Electrical & Control on building communication protocols, while alarms, trends, schedules, and manual overrides are in Chapter 33 on alarms, trends, and schedules in the BMS, and energy meters in Chapter 34 on building energy dashboards. Stale data and basic communication diagnosis are in Chapter 5 · Computational on field device data communication, and the reliability and access of control software in Chapter 6 · Computational.

    Exercises and worked solutions

    The numbers in the exercises are for practice.

    Try to answer first, then open the worked solution.

    1. A building has 4 air handling units with 38 points each, 120 fan coil units with 8 points each, and a pump plant with 60 points. How many points are there, and which layer is the largest?

      Check my answer
      See the worked solution

      The total is 4×38+120×8+60=152+960+60=1,1724 \times 38 + 120 \times 8 + 60 = 152 + 960 + 60 = 1{,}172 points. The fan coil units contribute 960 points, so the field layer is the largest, just like the VAV boxes in Example 1.

    2. A controller with 24 terminals uses 18 of them. Does its spare capacity meet 30 percent?

      Check my answer
      See the worked solution

      The spare is 24−18=624 - 18 = 6 terminals, that is, 6/24=256/24 = 25 percent, below 30 percent. At most ⌊0.7×24⌋=16\lfloor 0.7 \times 24 \rfloor = 16 terminals may be used, so the finding is recorded and handed to the integrator as a design decision.

    3. The screen shows a chilled water pump as “running”, but the pump differential pressure reads 0 kPa. What is suspected, and what does the technician do?

      Check my answer
      See the worked solution

      The “running” status is most likely a command, while a differential pressure of 0 kPa shows that the pump is not moving water. The technician checks the pump in the field, matches the point type in the points list, and reports to the supervisor without forcing a value in the BMS.

    4. A VIP guest complains of being cold, and the manager asks the duty technician to raise that room’s setpoint through the integrator’s account, whose password is written in the duty logbook. What is the technician’s position?

      Check my answer
      See the worked solution

      The technician refuses to use the integrator’s account, because accounts are not lent and a password written in the duty logbook is a security finding. The technician reports the complaint and the written password, and the setpoint change is made by whoever holds the authority according to the building’s procedure.

    5. The point name “TEMP1” is used in three different controllers. What does this do to alarms and reports, and what does the technician do?

      Check my answer
      See the worked solution

      Alarms and reports with the name TEMP1 do not show which controller has the problem, so staff may go to the wrong room. The technician records all three points with their locations and reports them to the integrator, because names are used by programs, graphics, and trends and may only be changed through change control.

    6. The operator workstation is down for two hours because the server has failed. Do the rooms lose cooling, and what needs attention after the server is restored?

      Check my answer
      See the worked solution

      The rooms do not lose cooling, because the building controllers and field controllers run their own programs. What is lost for two hours is alarms and trends, so after the restoration the technician checks the alarms that occurred during the outage in the controllers and records the gap in the trends in the report.

    References

    External sources

    • Guide to Operational Technology (OT) Securitynvlpubs.nist.gov
    • GSA Guide to Specifying Interoperable Building Automation and Control Systems Using ANSI/ASHRAE Standard 135-1995, BACnetnvlpubs.nist.gov
    • Operations & Maintenance Best Practices Guide: Release 3.0energy.gov
    • Building Technologies Technical Reference Guide Version 3.0gsa.gov
    • The Language of BACnet-Objects, Properties and Servicesbacnet.org

    Revision history

    DateVersionChange
    November 13, 20261First published

    How to cite

    Kurnia (2026). Building management system (BMS): three-layer architecture, field controllers and operator workstations, data points and the points list, input and output types, point naming, and the limits of technician authority. ARSTEMA Academy. Revised November 13, 2026. arstema.com/en/academy/konsep/sistem-manajemen-gedung-bms-arsitektur-tiga-lapis-pengendali-lapangan-dan-stasiun-operator-titik-data-dan-daftar-titik-jenis-masukan-dan-keluaran-penamaan-titik-serta-batas-kewenangan-teknisi

    Self-check · 3 questions

    Check your understanding before moving on

    Write your answer in your own words, then compare it with the worked solution from this chapter’s exercises. The system doesn’t judge open answers as right or wrong; you decide which parts you’ve understood.

    0/3rated
    1

    A building has 4 air handling units with 38 points each, 120 fan coil units with 8 points each, and a pump plant with 60 points. How many points are there, and which layer is the largest?

    2

    A controller with 24 terminals uses 18 of them. Does its spare capacity meet 30 percent?

    3

    The screen shows a chilled water pump as “running”, but the pump differential pressure reads 0 kPa. What is suspected, and what does the technician do?

    Self-assessment progress0%

    Nearby chapters