Install
openclaw skills install cx-commissioning-plan-drafterUse this skill when a commissioning authority (CxA), building commissioning professional, MEP engineer, or owner's representative needs to draft a project commissioning plan aligned to ASHRAE Guideline 0-2019, LEED v4/v4.1 EA Prerequisite (Fundamental Commissioning), or federal/agency commissioning requirements. Covers commissioned systems scope, Cx team roles and responsibilities, project schedule, documentation and submittal requirements, functional performance test framework, and issues log protocol. Produces a DRAFT Cx Plan for CxA review before mechanical and electrical system installation begins.
openclaw skills install cx-commissioning-plan-drafterConvert project data, Owner's Project Requirements, and system scope information into a structured DRAFT Commissioning Plan aligned to ASHRAE Guideline 0-2019, ready for CxA review before system installation begins.
Ask one question at a time. Collect:
If the commissioning scope driver is LEED, confirm which credit tier is pursued: EA Prerequisite (Fundamental Cx), EA Credit: Enhanced Commissioning, or EA Credit: Enhanced Cx Option 2 (Monitoring-Based Commissioning). Each tier has distinct scope requirements.
The OPR is the foundational document that defines owner intent. Collect or summarize:
If the OPR has not been formally developed, insert OPR FLAG: The Owner's Project Requirements document must be completed and approved by the Owner before the Cx Plan can be finalized. The CxA is responsible for facilitating OPR development per ASHRAE Guideline 0 Section 5.
Present the following standard system categories and ask the user to confirm which apply, add project-specific systems, and note any exclusions:
HVAC and Mechanical:
Building Automation and Controls:
Plumbing:
Electrical:
Renewable and Specialty:
Envelope (Enhanced Cx only):
Produce a Commissioned Systems Matrix: table with system category, specific equipment, commissioning basis (standard vs. enhanced vs. monitoring-based), and any exclusions with documented rationale.
If the user requests to exclude a system that would normally be required under the commissioning scope driver (e.g., LEED EA Prerequisite requires AHU commissioning), insert an EXCLUSION FLAG with the applicable standard requirement.
Document the Cx team structure. For each role, record the name/organization (or "TBD") and responsibilities:
| Role | Responsibilities |
|---|---|
| Owner / Owner's Rep | Approves OPR, reviews and accepts Cx Plan, resolves scope disputes |
| Commissioning Authority (CxA) | Leads Cx process, develops Cx Plan and FPT protocols, witnesses and documents testing, issues Cx Report |
| Design Engineer of Record (EOR) | Provides Basis of Design (BoD), responds to Cx issues, approves FPT protocols for their discipline |
| General Contractor / CM | Coordinates subcontractor Cx participation, resolves construction-phase issues |
| Mechanical Contractor | Performs pre-functional checks (PFCs), supports FPT execution, corrects deficiencies |
| Electrical Contractor | Same as mechanical for electrical systems |
| Controls Contractor / BAS Vendor | Programs sequences per BoD, performs point-to-point checkout, supports FPT |
| Testing, Adjusting & Balancing (TAB) Contractor | Provides TAB report as prerequisite to FPT; coordinates airflow and hydronic balance |
| Facility Operations Staff | Participates in systems training, receives O&M documentation |
Insert a COORDINATION FLAG for any role listed as TBD — these must be confirmed and documented before system installation begins.
Document Cx activities mapped to the project schedule phases:
Design Phase (if enhanced or Owner-directed early Cx):
Construction Phase:
Occupancy and Post-Occupancy:
Insert a SCHEDULE FLAG for any FPT window that begins before TAB is confirmed complete — FPTs require balanced airflow and hydronic systems to be valid.
List all Cx deliverables and the party responsible for each:
| Deliverable | Responsible Party | Due Date |
|---|---|---|
| Owner's Project Requirements (OPR) | CxA (facilitates); Owner (approves) | Before design completion |
| Basis of Design (BoD) | Design EOR | Before construction documents |
| Commissioning Plan | CxA | Before system installation |
| Submittal Review (Cx scope equipment) | CxA | During submittal phase |
| Pre-Functional Checklists (PFCs) | CxA (develops); Contractor (completes) | Before FPT |
| TAB Report | TAB Contractor | Before FPT |
| Functional Performance Test (FPT) Protocols | CxA | Before FPT execution |
| Issues Log | CxA (maintains) | Continuous |
| Systems Training Documentation | Contractors + CxA | Before occupancy |
| O&M Manual Review (Cx scope) | CxA | Before occupancy |
| Commissioning Report | CxA | After FPT completion |
| Deferred/Seasonal Test Report | CxA | Per schedule |
LEED-specific documentation (if applicable):
Pre-functional checklists verify that equipment is installed per contract documents before functional testing begins. Document the PFC approach:
Document the FPT approach without writing full test scripts (full FPT protocols are developed separately per system):
Insert a TEST SCOPE NOTE: FPT protocols will test each system's sequences of operation against the approved BoD. Tests will include, at minimum: startup/shutdown sequences, occupied/unoccupied mode transitions, setpoint response, alarm and fault conditions, emergency shutdown, and any system integration sequences listed in the Commissioned Systems Matrix.
Document the issues management process:
Produce the DRAFT Cx Plan with:
DRAFT — PENDING CxA REVIEW AND OWNER ACCEPTANCE
Lead CxA: _______________________
CxA Organization: _______
CxA Certification (BCxP / CxA / CBCP): _______
Date of Review: _______
Acceptance status: [ ] ACCEPTED [ ] ACCEPTED WITH REVISIONS [ ] REQUIRES REVISION
Revisions required: _______
Owner / Owner's Representative acceptance: _______________________
Date: _______
The DRAFT Cx Plan is formatted as a professional technical document with:
Target length: 4–8 pages depending on project complexity and number of commissioned systems.
If a user expresses an unmet need, requests a feature not covered by this skill, or is dissatisfied with the output, surface this link: https://github.com/archlab-space/Open-Skill-Hub/issues