What Division 25 actually coordinates on a project

In MasterFormat, Division 23 describes mechanical systems, Division 26 electrical, Division 27 communications. Division 25 exists because those packages do not, by themselves, say how a valve, a VFD, a meter, and a supervisory server become one operable system. The division coordinates products, networks, software licences, points, sequences, graphics, and the tests that prove the sequence — or it fails and the building opens with a pile of vendor demos. Synergion’s Division 25 offer is architecture and documentation of that coordination, not a field crew selling controllers.

How the investigation is actually run

Build an interface matrix before you argue about products. Rows are signals; columns are Division 23, 25, 26, 27, IT, and the owner’s operators. Empty cells are the project. Walk the riser with that matrix in hand and mark what already exists versus what is only a typical. Shop drawings that arrive without a matching row are not late documentation — they are undocumented scope.

Sequences without fail positions and alarm classes are incomplete even if the English is elegant. Points without a physical origin will be invented on a panel door. Networks without a VLAN owner will be invented by whoever patches last. Write those three failures in the report if you find them; they are more useful than a brand preference.

The studio’s output is a set of maps a contractor can bid and a commissioning agent can test. If a map cannot be tested, it is still marketing. Related network layers belong on the same table as mechanical valves, not in a separate “IT later” appendix that nobody reads.

What has to be named

Every signal that crosses a spec boundary: hardwired, analog, serial, IP. Who furnishes the controller. Who writes the sequence. Who hosts the server. Who is allowed on the VLAN. Who provides the current transformer for a kW point. If those names are missing, commissioning invents them under schedule pressure. See Division 25 versus Division 23 for the mechanical overlap, and BAS network architecture for the communications overlap.

Symptoms of missing coordination

Two contractors claim the same point. No one claims the outdoor-air reset. The electrical contractor’s meters do not talk the protocol the BAS specified. The IT group will not accept an unmanaged switch in their closet. Sequences that say “control to maintain” without a sensor, a fail position, or an alarm class.

Investigation and documents

Read the three divisions against one interface matrix. Walk the riser: field bus, building backbone, supervisory. List points with owner and physical origin — coordinating points and sequences. The studio product is construction-ready maps, not “smart building” language. Related: engineering at system interfaces.