Which CSI Divisions a Controls Integrator Actually Owns

Every spec book is organized by CSI MasterFormat divisions, and a controls integrator's scope is scattered across several of them. Knowing which divisions to open, and which sections inside them are yours versus somebody's else's, is the first skill of bid review and the foundation of every submittal obligation that follows. Miss a section at bid time and you either eat the scope or fight about it.

This is a working map, not a MasterFormat lecture.

Where controls scope lives

Division 40, Process Interconnections (older books: Process Integration). The home division for process control in water, wastewater, and industrial process work. The 40 61 through 40 79 range carries process control systems: general provisions (40 61 13 is a common anchor), control descriptions, instrumentation devices, panels, and network equipment. If you integrate in the municipal world, this is usually your primary division in newer books.

Division 26, Electrical. Even when the controls scope lives elsewhere, Division 26 constrains you: panelboards and feeders your equipment connects to, the 26 09 sections on low-voltage controllers, VFDs when the spec puts them electrical-side, and wiring methods your panel wiring must follow. Whether the VFD submittal is yours or the electrical contractor's is a question worth settling in writing before either of you submits anything.

Division 25, Integrated Automation. Building automation territory: integrated automation networks, instrumentation, and control sequences for facility systems. Integrators who touch commercial buildings meet Division 25 alongside Division 23's controls sections (23 09) for HVAC.

Division 13, Special Construction, in older books. MasterFormat 1995 put instrumentation and controls in the 13400 series, and a great many specs still in circulation, especially municipal ones built from old masters, keep it there. A 13491 or 13500 section can be the entire controls scope of a job whose book otherwise looks modern.

Division 01, General Requirements. Not controls scope, but it governs you anyway: submittal procedures, closeout requirements, O&M data format, record documents. Every obligation about how you submit and close out comes from here. Read it once per job; the details are in how to read a spec section for submittal requirements.

Why the numbers refuse to stay put

MasterFormat was overhauled in 2004 from five-digit numbers (16 divisions) to six-digit numbers (49 divisions), and real spec books are messier than either edition:

• Old masters survive. Specs written from a firm's 1995-era boilerplate still ship with 13400-series and 17000-series controls sections today.
• Hybrids are everywhere. A book can carry a 2004-numbered Division 40 next to a Division 01 whose sections are 1995 numbers with a space added.
• Firms invent. "Division 17" for instrumentation and controls was never official MasterFormat, and you'll still find it in the wild.

The practical consequence: find your sections by title, not by number. Search the table of contents for "instrumentation," "control," "SCADA," "process control," and "submittal," whatever the digits say. A section numbering scheme is a filing system, not a promise.

Claiming sections: the bid-time discipline

For each section in the book, decide and record one of three answers:

1. Ours. We furnish this scope and owe its submittals.
2. Interface. Someone else furnishes it, but it touches us: the MCC we wire into, the network the electrician pulls. We coordinate, and we should read it even though we don't submit against it.
3. By others. Not ours, no interface. Skip it with a clear conscience.

Write the answers down as a list with a line of reasoning per claim. Ambiguities surface immediately ("the spec puts VFDs in both 26 29 23 and the process control section, who submits?"), and every unresolved one is a future dispute you can instead settle now with one RFI or a clarification in the bid. The claimed list then becomes the spine of the whole documentation job: each claimed section gets the submittal-requirements read, and the union of those reads is your submittal register for the project.

The traps that recur:

• Procedural sections claimed by nobody. Submittal procedures, closeout, O&M data. They belong to every trade, so each trade assumes another one owns them. They're yours too.
• The controls section hiding outside the controls division. A chemical feed or packaged equipment section that quietly includes "control panel by supplier" language, with submittal demands you'd never find reading only Division 40.
• Coordination sections skipped as "by others." The section covering the plant network or the MCC is exactly where the interface requirements that bite you at startup live.

Disclosure: I build Submittal Kit, which indexes uploaded spec books by section and tracks claims (ours, interface, by others) with the reasoning attached. The bid-time discipline above works just as well in a spreadsheet, as long as it happens.