03Commissioning documents: OPR, BOD, Cx plan, specification, checklists, scripts, reports and systems manual

03.0Scope of this chapter

This chapter describes every document of the commissioning process on a hyperscale data-centre campus. For each document it states what it is for, who writes, reviews and approves it, when it is produced, what it contains, its usual length and which faults are common. It gives a full table of contents for the commissioning plan and the anatomy of a test script. It also gives a filled 20-step Level 4 chiller staging script and a filled Level 3 checklist for an uninterruptible power supply (UPS) module. It ends with the rules for naming, numbering, version control, signing and closing test records.

1. Document set. The list of commissioning documents and how they depend on each other.
2. Requirement documents. Owner's project requirements (OPR) and basis of design (BOD).
3. Plan and specification. The commissioning plan (Cx plan) and the commissioning specification (CSI MasterFormat 01 91 13 and the Division 23, 26 and 28 commissioning sections).
4. Test documents. Level 1 factory acceptance test (FAT) procedures and reports, Level 2 installation checklists, Level 3 pre-functional checklists, Level 4 functional performance test (FPT) scripts and Level 5 integrated systems test (IST) scripts.
5. Tracking and reporting documents. Issues log, progress reports and the final commissioning report.
6. Operation documents. Systems manual, training plan, seasonal test records and the lessons-learned log.
7. Control rules. Naming, numbering, version control, signature, closure and dependencies.

Documents and sources used: ASHRAE Guideline 0-2019 and Standard 202-2024 (through the 2020 ASHRAE course), ASHRAE Guideline 1.4-2019, BSRIA BG 8/2009, CSI MasterFormat section 01 91 13 as used in owner master specifications. The chapter also uses Schneider Electric White Paper 148, the Archdesk test register schema, IEC 62040-3:2021, chapter 04 (document control) and chapter 02 (levels) of this manual, research note RF-03, and the MSC-1 case ledger.

03.1The commissioning document set

03.1.1Document list

The ASHRAE course on Guideline 0 lists the formal commissioning process documents (source 1). They are the OPR, BOD, Cx plan, design checklists, construction checklists and test procedures. They also include the commissioning requirements in the construction documents, the systems manual, the training plan, the issues log and the commissioning process report. Data-centre projects add the level structure of chapter 02. Figure F03-1 shows when each document is produced.

03.1.2Who writes each document according to ASHRAE

The ASHRAE course gives the following allocation as a suggestion (source 1).

On hyperscale programmes the owner CxM is accountable for all commissioning documents except the BOD, as the responsibility (RACI) matrix in chapter 02 shows.

03.2Owner's project requirements (OPR)

03.2.1Purpose

The OPR states the minimum characteristics that define a successful project from the owner's view. ASHRAE states that it must address quality and quantity, must include verifiable benchmarks, is completed in pre-design and becomes the basis for all commissioning verification (source 1). Every acceptance criterion in an L4 or L5 script should trace to an OPR clause, a specification clause or both.

Owner: Owner project director; written with the CxM and the data-centre operations (DCOps) lead.

Trigger: Project approval.

03.2.2Contents of an OPR for a hyperscale campus

03.2.3How to write a verifiable OPR criterion

1. State the quantity. "The UPS shall support full block load for at least 5 min on battery at end of life" is verifiable. "The UPS shall be reliable" is not.
2. State the condition. Give the load, the ambient condition and the configuration under which the criterion applies.
3. State the verification method. Name the level and the test: "verified at L4 by full-load battery discharge test".
4. Avoid design content. The OPR states what is needed. The BOD and the design state how.
5. Number every criterion. Use a stable number (OPR-4.3) so scripts can cite it.

03.2.4Common faults in OPRs

1. No numbers. Criteria written as aims without values. Detect it by checking that every criterion has a value and a unit.
2. Design written as a requirement. "Provide four chillers" in the OPR prevents the designer from meeting the need another way. Move it to the BOD.
3. No update after changes. A change in rack density is made in the design but not in the OPR. Detect it at each design review by comparing the OPR revision date with the change register.
4. No owner acceptance. The OPR is issued without the owner's signature. The CxA must not use an unaccepted OPR as the benchmark.

03.3Basis of design (BOD)

03.3.1Purpose and content

The BOD records the assumptions, methods, selections and decisions behind the design. ASHRAE lists the typical BOD content (source 1). The content starts with the codes, standards and guidelines used, the basis for system and assembly selection, the options considered and the calculation and analysis methods. It continues with the key inputs to calculations (data and assumptions), the narrative descriptions of system operation and of control sequences, and the equipment used as the basis of design.

03.3.2Common faults in BODs

1. No failure narratives. The BOD describes normal operation only. The IST scripts cannot be written without the failure narratives. Request them at the 60 % design review.
2. Sequences not numbered. Scripts cannot cite a sequence clause. Ask for numbered sequences.
3. BOD not updated for substitutions. An approved equipment substitution changes the ratings. ASHRAE lists BOD updates for owner change orders and contractor substitutions in the construction phase (source 1).

03.4Commissioning plan

03.4.1Purpose

The Cx plan is the plan for the commissioning process: what is commissioned, by whom, in which order, with which documents and records. ASHRAE describes it as a plan for upcoming activities and a record of completed activities (source 1). It is started in pre-design and updated in design with construction details and the training plan. BSRIA BG 8/2009 provides a model commissioning plan template (source 3).

Owner: CxM (author when the owner runs commissioning in-house) or CxA.

Trigger: Pre-design (revision 0); updated at each design stage, at contract award, before L4 and before L5.

03.4.2Full table of contents for a hyperscale campus Cx plan

1. Document control. Title, document number in the common data environment (CDE), revision history, approval signatures, distribution list.
2. Introduction. Purpose of the plan, project description, campus phases, references to the OPR and BOD revisions used.
3. Commissioning scope. List of commissioned systems by building and hall; systems excluded and why; owner-furnished equipment.
4. Commissioning objectives. The OPR criteria to be verified and the level at which each is verified.
5. Reference documents. Standards with editions (from the reference register), contract documents, OEM documents.
6. Commissioning team. Names, companies, roles, contact details, authority of each role.
7. Roles and responsibilities. RACI per level and per document (chapter 02).
8. Commissioning levels. Definitions of L0 to L5 (and L6), entry and exit criteria, gates, tag scheme.
9. Sampling and coverage rules. Which items are tested at 100 % and where sampling applies, with sample sizes.
10. Communication. Meetings (Cx meeting weekly, test-readiness meetings, gate reviews), reports, escalation path, request for information (RFI) route (chapter 05).
11. Document management. Naming, numbering, CDE folders, status codes, version control, redlines (chapter 04 and section 03.16).
12. Design phase process. Design review stages, review periods, comment log, OPR traceability.
13. Submittal review process. Which submittals the Cx team reviews and the review period.
14. Factory testing (L1). Equipment list, FAT procedure approval, witness rules, shipping release.
15. Installation verification (L2). Checklist templates, inspection process, pre-energisation tests.
16. Start-up and pre-functional checks (L3). OEM start-up, settings management, point-to-point checks, calibration, testing, adjusting and balancing (TAB).
17. Functional performance testing (L4). Script list, load bank plan, instrument list, witness notice periods.
18. Integrated systems testing (L5). Scenario list, IST readiness review, load plan, observers, abort criteria.
19. Issues management. Issues log fields, categories, ageing limits, closure rules.
20. Retest rules. When a retest is required, who pays, how the retest record links to the failed record.
21. Safety during commissioning. Permit to work, lockout and tagout (LOTO), energisation rules, load bank and heater skid safety, live-site rules (chapter 10).
22. Instruments and calibration. Instrument list, calibration certificates, accuracy requirements.
23. Schedule. Commissioning schedule by building and hall, linked to the construction programme; IST windows.
24. Training. Training plan or reference to the separate training plan.
25. Systems manual. Structure, champion, responsibilities, deadlines.
26. Handover. Acceptance criteria, record set, open item lists, deferred and seasonal tests.
27. Reporting. Weekly progress report, level completion reports, final Cx report.
28. Lessons learned. Log, workshop, use in the next building.
29. Appendices. Templates (checklists, scripts, issues log, gate record), sample filled forms, system lists, contact list, schedule.

03.4.3Comparison with BSRIA BG 8 and ASHRAE Guideline 0

The Cx plan is revised at the triggers named in 03.4.1. Figure F03-6 shows, for each trigger, which of the 29 sections of 03.4.2 are completed or updated and who approves the revision. The table compares the plan content with Guideline 0 and BG 8.

03.4.4Common faults in Cx plans

1. Plan written once. The plan is not updated after design. Detect it by comparing the plan revision with the phase.
2. Levels not defined. Detect it by searching the plan for an entry and exit criteria table.
3. No sampling rule. Detect it by searching for the coverage section.
4. No retest cost rule. Detect it by reading section 20 of the plan and the matching clause in 01 91 13.

03.5Commissioning specification

03.5.1Section 01 91 13 General Commissioning Requirements

Section 01 91 13 is the Division 01 section that sets the administrative and procedural commissioning rules for every trade. Owner master specifications follow the three-part format and refer to related sections such as 01 78 23 Operation and Maintenance Data and 01 79 00 Demonstration and Training (source 4). The articles below are the usual content on a data-centre project.

03.5.2Discipline commissioning sections

03.5.3Common faults in Cx specifications

1. No witness notice period. Detect it in article 1.6.
2. Load banks not assigned. Detect it in article 2.2; if missing, the load bank becomes a variation.
3. OEM attendance limited to start-up. Detect it by reading the OEM supply clause for L4 and L5 days.
4. No retest cost rule. Detect it in article 1.7.

03.6Level 1 FAT procedure and FAT report

03.6.1FAT procedure contents

03.6.2FAT report and shipping release

The FAT report contains the completed procedure with measured values, the punch list and the deviation acceptances. The shipping release is a one-page record signed by the OEM quality lead, the CxA and the owner. Equipment ships only with a signed release.

03.7Level 2 installation checklists

03.7.1Structure

ASHRAE describes the recommended sequence of construction checklist verifications (source 1). The sequence is: correct and undamaged delivery; pre-installation condition; quality of installation; operation of the element in isolation; record of negative findings to the issues log; and links to test data forms. On data-centre projects the first two are L2A and the third is L2B; operation in isolation is L3.

03.7.2Checklist item fields

Each checklist item is one row with the fields below. Figure F03-7 shows a filled L2 checklist for CRAH B2-DH3-CRAH-14: 11 items, 10 answered "yes" and item 11 (unit label missing) answered "no" with issue ISS-B2-1301 (category C).

03.8Level 3 pre-functional checklists

03.8.1Structure

An L3 checklist records the start-up and the component-level checks of one item. It contains the OEM start-up content, the settings record, the point checks and the measured values. It is signed by the OEM, the contractor and the CxA.

03.8.2Filled L3 checklist for a UPS module

Worked example: L3 checklist ELE-L3-UPS-B2-DH3-A1-M2-01 rev 0 for UPS module 2 of block B2-DH3-A1. The block UPS system is 2.5 MW (MSC-1 ledger). The values below are examples; the approved OEM start-up procedure and specification 26 33 53 govern. In the Initials column, CON is the electrical contractor.

All 28 items passed. The checklist is signed by the OEM start-up engineer, the electrical contractor and the CxA on 2027-02-24. The CxA requests the L3 gate (chapter 02) and hangs the green tag after the gate record GATE-L3-B2-DH3-UPS-A1-M2 is signed.

Common errors:

1. Settings file version not recorded. A later setting change cannot be traced. Detect it by checking item 12 on every L3 checklist.
2. Alarm checked on the display only. The EPMS and BMS paths are not proved. Detect it by checking the arrival time column.
3. Ohmic values without a baseline. The values are recorded without the string average. Detect it by checking that the acceptance rule is stated.

03.9Level 4 functional performance test scripts

03.9.1Script anatomy

Figure F03-2 shows the parts of a script. ASHRAE states that test procedures must be scripted and should allow easy recording and archiving of the results for the systems manual (source 1). Schneider White Paper 148 describes an "as built" script report that gives a line-by-line account of how each component passed or failed (source 6).

03.9.2Step table columns

The step table has seven columns. Figure F03-8 shows the four script statuses, the step results and the retest path, with the dates of the UPS worked example in 03.17.3.

The Archdesk test register schema allows four test statuses only and states that "in progress" is not a valid status for a test (source 7). This manual uses four statuses for a script: not started, passed, failed, retest. For a step, the result is pass, fail or not tested.

03.9.3Filled 20-step L4 chiller staging script

Worked example: Script MEC-L4-CHW-B2-STG-01 rev C, chiller staging sequence for the building B2 chilled-water plant. The plant serves the three air halls of B2 on the cold loop at 18 °C supply and 24 °C return. The plant has five chillers CH-01 to CH-05 of 2.5 MW each, four duty and one standby. This is an example value sized from the MSC-1 cold-loop duty of 36.5 MW for the campus, about 9.1 MW per building. The warm-loop trim chillers of chapter 18 are a separate plant of 8 duty and 1 standby units of 2,500 kW. The chilled water supply setpoint is 18.0 °C and the return is 24.0 °C (MSC-1 ledger). Heater skids on the chilled-water loop provide the load. The staging values come from the approved sequence of operation (SOO) SOO-B2-CHW rev C, an example document. The project sequence governs. The plant controls stage up when plant load exceeds 90 % of running capacity for 10 min or when supply temperature exceeds 18.8 °C for 5 min. Stage down when load is below 60 % of the capacity that would remain after stopping one chiller for 15 min. The minimum run time is 30 min and the minimum off time is 15 min. The standby chiller starts within 3 min of a running chiller fault.

The CxA confirms the prerequisites before step 1. L3 is signed for CH-01 to CH-05 and the pumps, and BMS trend group TG-CHW-01 logs at 10 s. Heater skids HS-01 to HS-04 (4 × 2.5 MW) are connected under permit PTW-B2-0662. The plant has no open category A issue. The Initials column holds the role of the step witness.

Figure F03-5 plots the heater load, the running chiller capacity and the chilled water supply temperature recorded during the test. The 20 steps passed at first attempt (first-pass yield 100 % for the script). Trend file TG-CHW-01_2027-04-14.csv and the heater skid log are attached. The script is signed by the controls integrator, the chiller OEM, the mechanical contractor, the CxA, the CxM and the DCOps lead on 14 April 2027.

Common errors:

1. Load changed too slowly or too fast. Step 10 needs a fast load rise to test the temperature-based stage-up; a slow rise tests only the load-based rule. Write the load ramp rate into the step.
2. Timers set short for the test. The integrator shortens the 10 min timer to save time. The test then does not prove the approved sequence. Check the timer values in the controller before step 1 and record them.
3. Simulated fault at the BMS. A fault forced in the BMS software does not test the chiller's own fault output. Use a fault at the chiller (step 13) as stated.

03.9.4Script review procedure

Purpose: Approve a script that can be executed and that proves the OPR and the sequence.

Owner: CxM.

Trigger: Draft script issued by the CxA.

Steps:

1. Check the references. Every acceptance value has a source with edition and clause. Allow 2 working days.
2. Check against the approved sequence. Every sequence clause in scope is tested by at least one step.
3. Check executability. The DCOps lead and the contractor confirm that each action can be performed safely with the equipment installed.
4. Check the instruments. Each measured value has an instrument of adequate accuracy.
5. Return comments. Return within 5 working days.
6. Approve. Approve the script at least 10 working days before the test. The approved script is published in the CDE with status A.

Records: Script review comment sheet; approved script revision.

03.10Level 5 IST scripts

03.10.1Structure

The IST script contains, for each scenario, the expected response of every system, the observers, the time stamps to collect, the abort criteria and the restoration steps. Chapter 28 gives the scenarios.

03.10.2Scenario sheet columns

03.11Issues log

03.11.1Purpose and fields

The ASHRAE course describes the issues log as the shared record of the commissioning team (source 1). The log should be easy to use and should show every issue resolved by occupancy. Standard 202 calls it the issues and resolution log.

03.11.2Rules

1. One issue per fault. Do not combine faults in one entry.
2. Closure needs evidence. An issue is closed only with a record ID that shows the fault no longer exists.
3. Retest links. A retest record references the issue ID and the failed record.
4. Weekly export. The log is exported weekly at status S2 for the Cx meeting (chapter 04).

03.12Progress reports and the final commissioning report

03.12.1Weekly progress report contents

1. Summary. Progress against the Cx schedule by building and hall.
2. Level completion. Count of items or systems passed per level against plan.
3. Issues. Open issues by category and age; issues closed this week.
4. Tests next week. Planned tests with witness notices.
5. Risks. Items that block the next gate.
6. Key performance indicators (KPI). First-pass yield, issue ageing, gate turnaround, tag accuracy (chapter 02).

03.12.2Final commissioning report contents

The final report has 11 sections. Figure F03-9 shows the records that feed each section and the party that provides them.

Schneider White Paper 148 lists three report types from integrated commissioning: the "as built" script report, the component error log and a trending report with a management summary of system performance trends (source 6). They map to sections 5, 6 and 4 of the final report.

03.13Systems manual

03.13.1Purpose and content

ASHRAE Guideline 1.4-2019 gives the guidance and procedures for producing a systems manual as a resource for training, operation, maintenance and upgrading. Addendum a (2024) adds detail to section 4.1 on the required information (source 2). The ASHRAE course states that the systems manual needs a champion and input from the design team, the contractor and the commissioning provider (source 1).

03.14Training plan

The ASHRAE course states that the training plan lays out the training needs (source 1). It lists the intended audience, expected outcomes, venue or approach, time allocations and verification requirements, in enough detail for bidding and scheduling.

03.15Seasonal tests and lessons learned

1. Seasonal tests. Tests that need a particular weather condition. In Jakarta the condition is high wet bulb and dry bulb (34.0 °C and 27.5 °C design in the MSC-1 worked example). The test checks plant capacity and dry cooler performance near design ambient.
2. Deferred tests. Tests that need conditions not available before handover, such as full tenant IT load.
3. Lessons-learned log fields. ID, building, phase, level, what happened, effect, cause, action for the next building, owner of the action, status.

03.16Naming and numbering of commissioning documents

03.16.1Two identifiers per document

Each commissioning record has two identifiers. The CDE container number follows the ISO 19650 naming rules of chapter 04 (for example MSC1-CXA-B2-01-RP-CX-4031). The test record ID is the identifier written on the record and used in the issues log and gate records.

03.16.2Test record ID format

Examples: MEC-L4-CHW-B2-STG-01 rev C; ELE-L3-UPS-B2-DH3-A1-M2-01 rev 0; BMS-L4-B2-DH3-CDU-SEQ-01-RT1.

03.16.3Rules

1. Templates and executed records are different documents. A template has its own ID (T-MEC-L2-CRAH rev C). Each executed record names the template ID and revision. The template is never overwritten with test data (chapter 04).
2. One executed record per asset per level. Repetitive items each get their own record.
3. IDs never reused. A cancelled ID stays cancelled.
4. Retest is a new record. A retest has the original ID with RT1, RT2 and references the failed record and the issue.

03.17Version control, signing and closing a test record

03.17.1Version rules

03.17.2Record approval workflow

Figure F03-3 shows the workflow from execution to closure.

Purpose: Turn an executed script into a closed record that the owner can rely on.

Owner: CxA for the record; CxM for approval.

Trigger: End of test execution.

Steps:

1. Sign on the day. All parties sign the executed copy on the test day. Signatures carry name, company and date.
2. Record redlines. Any change to a step during the test is written on the controlled copy and signed by the witness and the contractor (chapter 04).
3. Attach data within 2 working days. Trend files, analyser files and photos are attached in native form and as PDF.
4. Raise issues within 1 working day. Every failed step has an issue ID in the record.
5. CxA review within 3 working days. The CxA checks completeness: every step has a measured value and a result, every failure has an issue, every attachment is present.
6. CxM approval within 2 working days. The CxM approves the record and publishes it at status A.
7. Close the record. The record is closed when all its issues are closed or carried forward with owner acceptance. Closure is recorded in the script register.

Records: Signed executed record; attachments; issues; script register entry.

03.17.3Script register fields

Worked example: Closing the UPS L4 record UPS-L4-B2-DH3-A1-01. The test runs on 2 to 3 March 2027. Step 14 (battery discharge at full load) passes at 5 min 48 s against ≥ 5 min. Step 21 (maintenance bypass) fails: the key interlock sequence differs from the operating procedure. The CxA raises ISS-B2-1188 (category B) on 3 March. Data files are attached on 4 March (1 working day). The CxA review finds one missing power analyser file for step 9 and gets it on 5 March. The CxM approves the record on 8 March with status "failed". The OEM corrects the interlock key sequence and the procedure on 10 March. The retest UPS-L4-B2-DH3-A1-01-RT1 covers steps 20 to 22 on 11 March and passes. ISS-B2-1188 is closed on 11 March, and the script register shows the original record as "failed" and the retest as "passed". Elapsed time from test to closure: 7 working days.

03.18Document dependencies

Figure F03-4 shows which document needs which. A document cannot be approved before the documents it depends on.

Worked example: Late sequence of operation. The EoR issues the chilled-water sequence SOO-B2-CHW rev A at 90 % design with the staging timers marked "to be confirmed". The CxA cannot finalise MEC-L4-CHW-B2-STG-01. The CxM raises RFI-B2-MEC-0280 with a required answer date 30 working days before the planned L4 test. This date leaves time to review the script (5 days), revise it (5 days) and approve it 10 working days before the test. The EoR issues rev C with the timers 34 working days before the test. The CxA issues the finalised draft 22 working days before the test, and review (5 days) and revision (5 days) follow. The script is approved 12 working days before the test.

03.19Common errors in commissioning documents

1. Acceptance values without source. Detect at script review.
2. Scripts written from the specification only. The approved submittal and the sequence are not used. Detect by checking the references section.
3. Template overwritten. Detect by comparing template and executed record IDs in the CDE.
4. Records signed later in the office. Detect by comparing signature dates with the test date.
5. Issues not linked. A failed step without an issue ID. Detect at CxA review.
6. Systems manual left to the end. Detect by checking the systems manual status in the weekly report from the start of construction.
7. OPR not updated. Detect by comparing OPR revision dates with changes.
8. Retest overwriting the original record. Detect by checking the RT suffix.
9. Status "in progress". Detect in the script register; only the four statuses are allowed.
10. Missing native data. Only PDF exports are attached. Detect at CxA review.

03.20Checklist for site use

1. OPR accepted. The current OPR revision is signed by the owner and every criterion has a value and a verification method.
2. BOD current. The BOD includes failure narratives and numbered sequences and is updated for substitutions.
3. Cx plan complete. The plan has all 29 sections of 03.4.2 and the current revision matches the phase.
4. Specification complete. Section 01 91 13 has the witness notice, retest, load bank and OEM attendance articles.
5. FAT procedures approved. Each procedure was approved before the test and the witness points are marked.
6. Templates published. L2 and L3 templates are at status A with revision.
7. Scripts approved in time. Every L4 script was approved at least 10 working days before its test.
8. Script anatomy followed. Every script has the 12 parts of 03.9.1.
9. Sources in every step. Every acceptance value has a source.
10. Records signed on the day. Signatures carry name, company and date.
11. Issues linked. Every failed step has an issue ID; every closed issue has a closure record.
12. Naming followed. Record IDs follow 03.16.2 and are never reused.
13. Versions controlled. Only approved revisions are executed; redlines are signed.
14. Systems manual in progress. A champion is named and the manual status is reported weekly.
15. Training planned. Each system has audience, outcome, duration and verification.
16. Final report outline agreed. The final report structure of 03.12.2 is agreed with the owner before L5.

03.21Sources

1. ASHRAE, "Principles of Building Commissioning: ASHRAE Guideline 0 and Standard 202", course slides, 2020, accessed 31 October 2026. https://www.utah.gov/pmn/files/1040363.pdf
2. ASHRAE Guideline 1.4-2019, Preparing Systems Manuals for Facilities, addendum a (15 March 2024), accessed 31 October 2026. https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20errata/guidelines/g1_4_2019_a_20240315.pdf
3. BSRIA BG 8/2009, Model Commissioning Plan, catalogue record, accessed 31 October 2026. https://cis.ihs.com//CIS/document/294607
4. University of Houston master specification, Section 01 91 13 General Commissioning Requirements, accessed 31 October 2026. https://www.uh.edu/facilities-services/departments/fpc/master-specs/01-91-13-fl-general-commissioning-reqmts.pdf
5. Oneida County, Section 01 91 13 General Commissioning Requirements (RFP 2026-454), accessed 31 October 2026. https://oneidacountyny.gov/assets/Purchasing/Docs/RFPs/RFP-2026-454-Building-Commissioning-Services/13-Section-019113-General-Commissioning-Requirements.pdf
6. Schneider Electric, White Paper 148, Data Center Projects: Commissioning, Rev 1, accessed 31 October 2026. https://download.schneider-electric.com/doc/SPD_DBOY-6NJNK6_EN/DBOY-6NJNK6_R1_EN.pdf
7. Archdesk, "Master Data Center Commissioning: L1-L5" (test register schema), accessed 14 October 2026. https://archdesk.com/blog/data-center-commissioning-levels
8. IFMA Facility Management Journal, "Beyond Traditional" (NEBB article on Levels 0 to 6), August 2026, accessed 31 October 2026. https://fmj.ifma.org/beyond-traditional-nebb
9. Uptime Institute Journal, "Improve Project Success Through Mission Critical Commissioning", accessed 14 October 2026. https://journal.uptimeinstitute.com/improve-project-success-through-mission-critical-commissioning
10. ANSI/ASHRAE/IES Standard 202-2024, catalogue entry, accessed 31 October 2026. https://webstore.ansi.org/standards/ashrae/ansiashraeies2022024
11. IEC 62040-3:2021, Uninterruptible power systems, Part 3: Method of specifying the performance and test requirements, IEC. https://webstore.iec.ch/en/publication/62020
12. IEEE 1188, Recommended Practice for Maintenance, Testing, and Replacement of Valve-Regulated Lead-Acid Batteries, IEEE. https://standards.ieee.org/ieee/1188/
13. ANSI/NETA ATS-2025 summary, ANSI Blog, accessed 31 October 2026. https://blog.ansi.org/ansi/ansi-neta-ats-2025-electrical-power-testing/
14. ISO 19650-2:2018, Organization and digitization of information about buildings, Part 2: Delivery phase, ISO. https://www.iso.org/standard/68080.html
15. Data Centre Commissioning Field Manual R01, chapter 04 (document control, sections 04.12.2 and 04.12.3), October 2026.
16. MSC-1 case ledger, ../case_ledger.json, Data Centre Commissioning Field Manual R01 working files, October 2026.

Educational field reference compiled from public standards, guides, manufacturer documents and published incident reports; sources close each chapter. The project specification, the Engineer of Record and the OEM documents govern; check the current edition of every standard before use. Worked examples use an example campus (MSC-1: 4 buildings, 12 halls of 12 MW), not project data. Independent research; not affiliated with any current or former employer. Privacy · Terms.