BMS Commissioning Forms

Point to point commissioning (Cx) of a building automation system is key to quality control on any system.  This is often overlooked by contractors.  Failing to fully test the system results in higher warranty callbacks and customer dissatisfaction all while tarnishing a contractor’s reputation.

Benefits for contractors

Fully documenting the Cx process gives solid warranty date information, helps ease the transfer of projects between techs and provides clear initial system condition for end users that like to “tinker”.  Service is much easier if your techs are documenting site conditions in the Cx forms.  When the service tech is looking for a problem device later they will be able to find it quickly instead of searching for a long time. Any mechanical/equipment problems will be identified at startup and would prevent warranty callbacks.

Results of failing to 100% test

Benefits for owners

Failure to require your BMS contractor to document point to point Cx potentially leads to years of building issues/failures. Documented Cx doesn’t guarantee a problem-free system but it does set a minimum bar.  As an owner spend a little time to verify the dates, it becomes a bigger hassle to fake the forms than completing them. Requiring Cx documentation on bid day is unlikely to add costs to the project.  Good contractors will be doing this internally already.  Poor contractors will ignore the requirement.

Tools

The link below is a commissioning form for documenting point to point checkout.  It supports templates for unitary devices making it easy to generate all the required forms.  Scripts automatically create forms for each device and hyperlinks to the index page.   All forms can be quickly checked and the status is updated on the index worksheet.  When a project passes between techs, this gives clear indication where the project stands.

Typical workflow to implementing Cx forms:

  • Create templates for each common program or device
  • Save in a master form and distribute
  • During startup create forms based on project requirements
  • Document signal types and pass / fail per point during startup
  • At final closeout verify forms for completeness
  • Include in as-built documentation

Macros must be enabled after opening to allow scripts to run.  These are well commented and easy to modify.

Generic-Cx-Form-Public

Look for a video outlining the use of the spreadsheet soon.

Leave a Reply