BCxA ACP cheat sheet

Commissioning (Cx) is a quality-focused process for enhancing the delivery of a project, verifying that all systems perform interactively according to the owner's project requirements (OPR) and basis of design (BOD).

The OPR documents the owner's intended use, functional needs, and performance criteria; the BOD records how the design team translates those needs into design decisions.

New building commissioning applies to new construction; retro-commissioning applies to existing buildings without documented OPR; ongoing commissioning uses continuous monitoring to sustain performance.

Commissioning differs from testing, adjusting, and balancing (TAB): TAB quantifies and adjusts flows, while Cx verifies integrated performance against documented intent.

Core Cx team roles: commissioning authority (CxP/CA), owner, design team, contractor, and manufacturers' representatives; the Cx authority leads but does not assume design or construction responsibility.

Commissioning begins in pre-design and continues through occupancy; the greatest cost-effectiveness comes from early involvement because issues found late cost more to correct.

Key Cx deliverables include the OPR, Cx plan, Cx specifications, pre-functional checklists, functional performance tests, issues log, and final Cx report.

Benefits attributed to Cx include reduced change orders, improved energy performance, better indoor environmental quality, and documented operator training and turnover.

Pre-design Cx activities include selecting the Cx authority, defining the Cx scope, developing the initial OPR, and establishing the Cx budget and schedule.

The Cx plan defines scope, team roles and responsibilities, deliverables, schedule, communication protocols, and the testing and verification strategy.

The Cx authority should be independent of the design and construction teams to preserve objectivity; independence requirements are stated in the Cx plan and contract documents.

The Cx plan is a living document updated at each phase gate (pre-design, design, construction, acceptance, occupancy) to reflect scope and schedule changes.

Cx scope decisions address which systems are commissioned: typically HVAC, controls, electrical, plumbing, fire protection, and renewable energy systems, plus envelope where specified.

The Cx schedule must align with design reviews, submittal reviews, construction milestones, functional testing windows, and owner training and turnover dates.

The Cx budget covers Cx authority fees, testing labor, specialized instrumentation, retesting, documentation, and contingency for issue resolution.

Early OPR development establishes measurable performance targets (e.g., energy use intensity, ventilation rates, temperature tolerances) that later verification tests measure against.

Design-phase Cx activities include reviewing the OPR, reviewing design documents for Cx-related issues, updating the Cx plan, and incorporating Cx requirements into specifications.

The design review verifies that the BOD is consistent with the OPR and that the design is commissionable: systems are testable, accessible, and have adequate controls and monitoring.

Cx specifications should define contractor responsibilities, submittal requirements, pre-functional checklist requirements, functional test procedures, and training and documentation deliverables.

Cx specifications should require contractor participation in Cx meetings, timely issue resolution, and a designated Cx coordinator on the contractor's team.

Design review should identify O&M accessibility issues (e.g., equipment clearances, valve and damper access, sensor locations) that affect future maintenance and testing.

The Cx authority should review controls sequences of operation for clarity, completeness, and testability, since functional tests are written directly from these sequences.

Design-phase deliverables include design review comments, updated OPR and BOD as needed, updated Cx plan, Cx specifications, and the draft functional test plan.

Construction-phase Cx activities include submittal review, Cx meetings, witnessing pre-functional checklists, verifying TAB, and conducting functional performance tests.

Pre-functional checklists verify that equipment is installed correctly and is ready for functional testing; they precede and are prerequisites for functional tests.

TAB verification confirms that air and water flows meet design values; TAB must be completed and documented before functional performance testing begins.

The issues log records each deficiency with description, location, responsible party, date identified, and resolution status; it is closed out before final acceptance.

Acceptance-phase activities include functional performance testing, seasonal testing where required, operator training verification, O&M manual review, and the final Cx report.

Seasonal or deferred testing is scheduled when systems cannot be fully tested under design conditions during initial testing (e.g., heating in summer, cooling in winter).

Substantial completion is not the end of Cx: verification continues through acceptance, training, and the warranty or post-occupancy phase.

The contractor's Cx coordinator tracks and closes issues, coordinates test scheduling, and ensures the Cx authority has access to systems and documentation.

Functional performance testing (FPT) verifies that systems and components function interactively as specified, using documented test procedures and acceptance criteria.

Each FPT procedure should state the system tested, prerequisite conditions, test steps, expected results, acceptance criteria, and the responsible party.

Tests should verify normal operation, setpoint response, alarm and safety responses, failure modes, and interaction between systems (e.g., economizer and cooling).

Test instrumentation must be calibrated and recorded; data collected during testing supports the pass/fail determination and is included in the final report.

A test is failed when measured performance does not meet the documented acceptance criteria; the issue is logged, corrected, and the test is repeated.

Trend logging and building automation system data can supplement or substitute for manual verification where the data is reliable and documented.

Verification includes reviewing the completed pre-functional checklists, TAB reports, and controls point-to-point checks before integrated system tests.

The final Cx report documents tests performed, results, unresolved issues, and a statement of whether systems meet the OPR and BOD.

Core Cx documents include the OPR, BOD, Cx plan, Cx specifications, pre-functional checklists, FPT procedures and results, issues log, and final Cx report.

The issues log should be maintained throughout the project and closed out with documented resolutions; open issues are listed in the final report.

The final Cx report summarizes the Cx process, tests performed, results, deficiencies and their resolution, and any deferred or seasonal testing.

The O&M manual set should be organized by system and include manufacturer literature, as-built drawings, controls sequences, and maintenance schedules.

Documentation should be stored in a format and location accessible to the owner after turnover, including electronic copies of test records and trend data.

Systems manual is a consolidated reference combining OPR, BOD, sequences of operation, test records, and O&M information for ongoing operation.

Documentation must be complete before final acceptance; incomplete documentation is a common source of withheld acceptance and warranty disputes.

Records of operator training, including attendance and content, are part of the Cx documentation and support the owner's operational readiness.

Operator training should cover system operation, controls sequences, alarm response, maintenance procedures, and safety, and should be verified by the Cx authority.

Training should occur after systems are functional and before owner occupancy, and should be documented with attendance, content, and duration.

O&M manuals should be delivered and reviewed before training so that operators can reference them during instruction.

Maintenance planning should include preventive maintenance schedules, spare parts lists, and equipment access requirements identified during design review.

The Cx authority verifies that the owner's staff can demonstrate correct operation of systems before handover is considered complete.

Post-occupancy activities include warranty-phase reviews, seasonal testing, and performance monitoring against the OPR targets.

Handover includes as-built drawings, controls documentation, warranty information, training records, and the final Cx report.

A post-occupancy review can identify operational issues that were not apparent during construction-phase testing and should be documented for follow-up.

The Cx authority reports to the owner and maintains independence from the contractor and design team to preserve objectivity and credibility.

Cx meetings should have documented agendas, minutes, action items, and responsible parties with due dates.

Communication protocols in the Cx plan define who receives which documents, how issues are escalated, and how conflicts are resolved.

Ethical practice requires disclosing conflicts of interest, avoiding undisclosed financial relationships with tested parties, and documenting all findings accurately.

The Cx authority should not certify performance it has not verified; test results must be based on documented evidence.

Schedule management requires coordinating Cx activities with construction milestones and anticipating delays in testing due to incomplete prerequisites.

Change management requires updating the Cx plan, OPR, and test plans when scope or design changes affect commissioned systems.

Records of communication, including emails and meeting minutes, support accountability and are part of the project record.