What a Commissioning Plan Should Contain: A Checklist
A commissioning plan explains how a data center will be tested before it goes live. This checklist covers the sections a useful plan should include.
Key takeaways
- A commissioning plan sets out who tests what, in what order, and what counts as a pass.
- Clear roles, written scripts and measurable acceptance criteria prevent arguments later.
- A deficiency log with owners and dates keeps problems from being forgotten.
A commissioning plan is the document that explains how a facility will be tested to prove it works as designed. A good plan names the people involved, lists the tests in order, states what counts as a pass, and describes how problems are tracked until they are fixed. Use the checklist below to review one.
1. Purpose and scope
The plan should say what systems are covered. For a data center, that usually includes electrical distribution, standby generators, uninterruptible power supplies, cooling plant, controls and monitoring, and fire and leak detection. It should also say what is not covered and who handles it.
- Is each system listed by name?
- Are the project goals stated in plain words?
- Are the standards or owner requirements that apply referenced?
2. Roles and responsibilities
Many commissioning problems come from unclear roles. The plan should name each party and what they do. Typical parties are the owner, the commissioning agent, the general contractor, the trade contractors, the equipment suppliers and the operations team.
- Who writes the test scripts?
- Who performs the tests?
- Who witnesses and signs?
- Who can approve a change to the plan?
3. Phases and sequence
Commissioning is normally done in stages. Early stages check that equipment arrived as specified and was installed correctly. Later stages start equipment and test it alone. The final stages test systems working together, including failure cases. The plan should show the order and what must be finished before the next stage can begin.
4. Test scripts
A script is a written step by step procedure for a test. A good script states the starting condition, the action, the expected result, a space to record the actual result, and a pass or fail mark. Scripts should be written in advance and reviewed by the people who will run them.
- Do scripts include failure tests, such as loss of utility power or loss of a cooling pump?
- Do they cover safety steps?
- Can a person who did not write them follow them?
5. Acceptance criteria
Acceptance criteria define what counts as success. They should be measurable. "The system works" is not a criterion. "The backup source takes load within the time stated in the design documents" is closer. If the design documents do not state a number, the plan should say who will decide and when.
6. Prerequisites and readiness
Before a test begins, certain things must be true. Equipment is installed and inspected. Safety checks are done. Permits are in place. Fuel, water or other supplies are available. Temporary equipment, such as load banks (devices that simulate electrical load), is on site. The plan should list these items as a readiness checklist.
7. Deficiency tracking
Every failed test or open issue goes into a log. A deficiency log entry should include a description, the system, who is responsible, the date found, the target date and the status. The plan should say how issues are ranked, who confirms a fix, and whether a test must be repeated afterward.
8. Documentation and records
The plan should state what records will be kept and in what format. These include signed scripts, test data, photos, the deficiency log and a final report. It should also say who receives copies and how long the records are stored.
9. Schedule and coordination
Show when each stage starts and ends, which tests need outside parties and which need building systems to be available. Include time for retesting. Plans that assume everything passes the first time are rarely realistic.
10. Training and turnover
Commissioning is a good time to train the operations team. The plan should list training sessions, manuals, as built drawings and any spare parts to be handed over.
Final check
Ask three questions. Could a new team member run the program from this plan? Does every test have a clear pass mark? Does every problem have an owner? If yes, the plan is in good shape.
Keeping the plan alive
A plan that sits in a folder does not help. Review it at kickoff with every party. Update it when the design, schedule or equipment changes. Record the version and the date on each revision. At the end of the job, note which parts of the plan worked and which did not, so the next project starts with a better version. A plan that is short, clear and used is better than a long one that is not.
This article is general information for public education. It is not legal, tax, financial or engineering advice. Rules and conditions differ by location, so check with qualified local professionals. Spot an error? Write to info@datacenteroutreach.com and we will correct it.