Commissioning Specifications, Contractor Procurement, and Submittals
Cx in the specifications
The commissioning specification defines scope, roles, deliverables, and the contractor's Cx responsibilities. It should appear in Division 01 (general requirements) with system-specific details in the technical sections. Key content: definition of systems commissioned, CxA authority, contractor submittal and documentation requirements, pre-functional checklist obligations, FPT participation, training, and schedule impacts. Trap: questions imply Cx is only Division 01 - the correct answer is that Cx requirements belong in Division 01 and are referenced in relevant technical sections.
Procurement
During procurement, the CxA helps ensure bidders understand Cx obligations so bids price them. Contract documents should clearly assign responsibility for pre-functional checklists, test procedures, and correcting deficiencies found during testing.
Submittals
Submittals are reviewed against the BOD and specifications. The CxA's submittal role is to verify that equipment and controls documentation supports later testing and that OPR/BOD criteria are addressed. The designer (not the CxA) typically approves submittals; the CxA checks Cx-relevant content such as sequences, control diagrams, and testability.
Rule of thumb
If a requirement is not written into the contract documents, it is hard to enforce. Good Cx specs make contractor obligations explicit and measurable.
Worked example
A controls submittal lacks a written sequence of operation. The CxA flags it because FPT depends on a documented sequence; without it, functional testing cannot be objectively verified.