How to commission AI, DI, AO, and DO points in BMS?

Commissioning AI, DI, AO, and DO points is like a doctor checking your vital signs — verifying each input and output works correctly before the system can manage the building's health.

Every BMS project, whether it's a new IT park in Bengaluru or a retrofit in a Chennai hospital, relies on its Analog Inputs (AI), Digital Inputs (DI), Analog Outputs (AO), and Digital Outputs (DO). These are the eyes, ears, hands, and mouth of your BMS controller. If they don't work, the controller is blind, deaf, and mute. I've seen projects delayed by weeks because a junior engineer missed a single wire or a sensor was wired backwards.

Think of it like checking the electrical system of your home. Before you switch on the main power, you'd want to make sure every light switch, fan regulator, and power socket is wired correctly and safely.

Scaling to a Building

In a small home, you might have 20-30 electrical points. In a 10-storey commercial building in Mumbai, you could have thousands of BMS IO points: hundreds of temperature sensors (AI), dozens of fan status feedback (DI), scores of VAV damper actuators (AO), and hundreds of light relays (DO). Each one needs to be meticulously checked.

The Commissioning Engineer's Truth

What junior engineers always miss is the sequence and documentation. You can't just randomly check points. A systematic approach saves days. Also, never trust the wiring diagram blindly; always verify on site. I've seen cases where the physical wiring didn't match the drawing, leading to endless troubleshooting during functional testing.

Here's a practical approach I've used on countless sites, from pharma plants in Vizag to data centres in Hyderabad:

#### 1. Pre-Commissioning Checks (Before Power On)

• Visual Inspection: Before applying power, physically inspect every wire. Is it terminated correctly? Are the cable glands tightened? Is the shielding properly grounded? Check for loose strands, incorrect colour coding, or damaged insulation. This is where an IO list with proper colour-code discipline, as described in the library's IO List Best Practices entry, saves you. Without it, every wire is a guess.
• Continuity Test: Use a multimeter to check for continuity on each wire from the field device to the controller terminal. This verifies the physical connection and checks for breaks or short circuits. For DI points, short the wires at the sensor end and check for continuity at the controller. For AI points, check resistance (for NTC/PT1000) or voltage/current loop (for 0-10V/4-20mA) at the sensor end and verify at the controller.
• Power Supply Verification: Confirm that the correct power supply (24V AC/DC, 230V AC) is available at the controller and at any powered field devices (e.g., actuators, transmitters).

#### 2. Power On & Controller Configuration

• Controller Power Up: Power on the DDC controller. Observe status LEDs. Any error lights need immediate investigation.
• Network Connectivity: Ensure the controller is communicating on the BMS network (BACnet/IP, MS/TP, Modbus). Use a network scanner tool like EnSmart Scanner or Yabe (for BACnet) to confirm the controller is visible and responding.
• IO Mapping: Verify that the physical IO points on the controller are correctly mapped to the software points in the controller's program. This means AI-1 on the hardware matches AHU-1_SAT in the software, for example.

#### 3. Individual Point Testing (The Core of Commissioning)

This is where you systematically verify each point.

• Digital Inputs (DI):

1. Simulate State Change: Manually activate the field device (e.g., press a push button, open a damper to trigger an end switch, manually trip a motor overload relay). If it's a flow switch, blow into it or manually depress the paddle. 2. Verify Controller Status: Observe the DI status on the controller's software interface (or physically on the controller's LEDs if available). It should change from OFF to ON (or 0 to 1) instantly. 3. Check Alarms: Confirm that any associated alarms (e.g., Motor Trip) are generated in the BMS software when the DI changes state.

• Digital Outputs (DO):

1. Command DO: From the BMS software, manually command the DO point ON. 2. Verify Field Device: Physically observe the field device. Does the fan start? Does the pump run? Does the light turn on? Use a multimeter to confirm voltage at the device terminals. 3. Command DO OFF: Command the DO point OFF and verify the device stops.

• Analog Inputs (AI):

1. Simulate Input: This is crucial. For temperature sensors (NTC/PT1000), use a resistance decade box to simulate different temperatures. For 0-10V or 4-20mA sensors, use a signal generator or a calibrated loop calibrator to inject known values. 2. Verify Reading: Observe the AI reading in the BMS software. It should accurately reflect the simulated value. For example, if you inject 5V into a 0-10V input scaled for 0-100%, the BMS should read 50%. 3. Check Scaling & Calibration: Ensure the scaling (e.g., 0-10V = 0-1000 Pa) is correct and the reading is within acceptable tolerance. If not, adjust the scaling in the controller or calibrate the sensor.

• Analog Outputs (AO):

1. Command AO: From the BMS software, manually command the AO point to a specific percentage (e.g., 0%, 25%, 50%, 75%, 100%). 2. Verify Field Device: Use a multimeter to measure the voltage (for 0-10V) or current (for 4-20mA) at the AO terminal on the controller and at the field device (e.g., VFD, damper actuator, valve actuator). The measured value should correspond to the commanded percentage. 3. Observe Device Response: Visually check if the damper opens, the valve modulates, or the VFD frequency changes as commanded. For example, a 50% command on a 0-10V AO should result in 5V and the damper should be halfway open.

#### 4. Documentation

• Test Sheets: Maintain detailed test sheets for every single point. Record the date, time, simulated value, actual reading, and your initials. This is critical for validation, especially in pharma projects.
• Punch List: Any issues found must be added to a punch list, assigned to the relevant contractor, and tracked until resolved.

This systematic approach, though time-consuming, ensures reliability. Skipping steps here will inevitably lead to headaches during functional testing and system operation.

A properly commissioned IO point is a reliable data point — the foundation for all intelligent building control.