Skip to content

Manufacturing & Distribution

Write the AHU/BMS interface schedule before tender

  • Manufacturing & Distribution
  • 1 min read

Filter pressure transmitters on a new AHU get bought twice, or not at all, when the tender never says who supplies them.

The AHU vendor expects the BMS contractor to provide field devices; the BMS contractor priced a points list and assumed the unit arrives instrumented. The gap surfaces at commissioning, as a variation.

An interface schedule closes it: one line per item, and four columns for who supplies, who mounts, who wires and who configures. The lines that start most arguments:

  1. Sensors in the unit: supply temperature and humidity, filter differential pressure, airflow measurement at the fan. Factory-fitted ones can be wired and tested at FAT.
  2. Fan drives or EC controllers: hardwired start, stop, run and fault, plus a communication link. Name the protocol and attach the register map, or the integrator finds it out on site.
  3. Actuators on dampers and coil valves: signal type, spring return or not, and the position they fail to.
  4. Fire alarm shutdown: a hardwired contact, and whose panel it lands in.

Attach the same schedule to both tenders, so one line reads the same way in two bids.

Every AeroSano AHU is FAT-witnessed, which is where factory-fitted sensors and wiring get tested before the BMS contractor arrives.

Related

More on this subject