DESIGN GUIDELINE 4.3.6 - GENERAL COMMISSIONING PROCEDURES - Requirements and documentation

Oct 23, 2026

Design Guideline 4.3.6 sets minimum commissioning requirements for conducting Cx meetings, providing Cx reports, obtaining owner O&M manuals, and managing owner training. It defines how to schedule and run kick-off and subsequent meetings, track system status, assign action items with dates and responsible parties, and issue meeting minutes. It also specifies electronic Cx report content, including report data, executive summaries, issue tracking, QC handling, periodic distribution, and final commissioning report labeling.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages9

Reading Time23 min

AccessFree to download

Scope

Related Documents

Commissioning Meetings

Kick-off and scheduling

Ongoing status and issue discussions

Minutes and escalation

Commissioning Reports

Report structure and data

Executive summary and issue tracking

Quality control and scope changes

Final commissioning report

DESIGN GUIDELINE 4.3.6 GENERAL COMMISSIONING PROCEDURES Scope This procedure covers the minimum commissioning requirements for: • Conducting commissioning (Cx) meetings • Providing Cx reports • Obtaining operation and maintenance (O&M) manuals for the Owner • Managing and conducting Owner training Related Documents U-M Design Guidelines: DG 4.3-Building Commissioning DG 4.3.3-Full Construction-Phase Commissioning Procedure DG 4.3.4-Reduced Scope Construction-Phase Commissioning Procedure DG 4.3.5 – Commissioning Plan Procedure U-M Master Specification Sections: MS 017823 – Operation and Maintenance Manuals MS 019100 – Project Commissioning Commissioning Meetings Soon after becoming assigned or hired as the project’s Commissioning Authority (CxA), contact the U-M Project Manager and schedule a Cx kick-off meeting. • On large projects, the Cx meetings shall be separate from but perhaps directly after the Project Manager’s construction meetings. • On reduced scope construction-phase Cx projects, the Cx meetings should be held as part of the regular project construction meetings. Commissioning meetings should have the entire Cx Team in attendance: U-M Project Manager, Construction Manager (CM) or General Contractor (GC), and the applicable contractors. Invite U-M trades (such as U-M Plant DDC Shop) that are performing work on the project when their responsibilities will be discussed at the meeting. Take attendance at the Cx meetings. At the Cx kick-off meeting, give an overview of the Cx process including reviewing the Cx specification and all the requirements outlined in the Cx Plan. Establish the reoccurrence of the Cx meetings. At subsequent meetings, discuss the current status of each system being commissioned. Utilize the project’s Cx Status Check Sheet as a guide. • Discuss design, construction, and equipment issues affecting Cx. • Discuss the Cx schedule. Identify issues that may prevent completion of Cx before Substantial Completion. • Establish clear action items, dates, and responsible parties. • Periodically review the progress of assembling the project O&M. • Finalize Cx event dates, [e.g. equipment](e.g. equipment) start-ups, functional testing, owner training sessions, etc. • Generally limit discussion to resolving issues that will allow each system to progress to functional testing and ultimately to final CxA sign-off. • For design and construction issues that impact Cx and require lengthy discussion, schedule separate meetings inviting only those parties that need to be directly involved in theresolution. Within a few days after the meeting, issue meeting minutes to the Cx team. • List the Cx team and identify who attended the meeting. • Organize the minutes to match the meeting agenda. • Summarize the meeting discussions • Include an action items list with responsible party and completion date. Alert the U-M Project Manager of critical issues that are preventing the execution of the Cx process in a timely manner or that could prevent successful final commissioning and sign-off; do not rely entirely on meeting minutes for this purpose. Commissioning Reports Prepare an electronic Cx report and update it periodically. See the last pages of the Design Guideline for a suggested Cx report format (for interim and final reports) . Other formats are acceptable if they present the information in a similar manner and contain the same information. Each Cx report shall include the following: • Report Data o Sequential report number and date of report o Building Name o Project Name o U-M Project Number o Report author and distribution list • Executive Summary-Each report shall begin with an executive summary that indicates, since the last report issued: o The functional tests that have occurred o Major issues discovered o Any new or on-going impediments to commissioning o the overall Cx progress • Issues Discovered-This sh

FAQs

What does Design Guideline 4.3.6 cover as a scope of work?

It covers the minimum commissioning requirements for conducting Cx meetings, providing Cx reports, obtaining operation and maintenance (O&M) manuals for the owner, and managing and conducting owner training.

What should be included and handled during commissioning meetings?

Cx meetings should involve the full Cx Team, include kick-off process overview and recurrence, discuss system status and issues affecting Cx, review the Cx schedule, establish action items with dates and responsible parties, and limit discussions to enabling progression to functional testing and final sign-off.

What are the required elements in a commissioning report and what is required for the final report?

Cx reports must include report data and an executive summary covering functional tests, major issues, impediments, and overall progress, followed by a list of discovered issues (with handling for QC items). A draft final commissioning report is issued immediately before Substantial Completion and must be labeled “Final” and “Preliminary and Advisory,” or “Provisional Final Report” when Cx continues afterward, with grouped outstanding and open issues plus recommendations beyond the project scope.

Oct 23, 2026

Upload by Pentious