1. Purpose and Scope
This reference defines the load release and readiness review framework for GridCore campuses. It is not a final commissioning plan, energization authorization, operating procedure, safety permit, MSA, SLA, service order, regulatory approval, or certificate of occupancy.
It is intended to align construction, commissioning, engineering, operations, safety, security, network, customer, and commercial teams around a structured approach to determining when capacity is ready for customer load. Actual load release criteria must be project-specific and documented in approved procedures and sign-off records.
2. Load Release Premise
Capacity is not real until it can be safely, reliably, monitored, cooled, supported, and contractually operated. Each of these conditions requires evidence — not assertion. The following distinctions are foundational to the GridCore load release model:
- Raw MW availability is not the same as customer-ready load.
- Installed equipment is not the same as commissioned equipment.
- Commissioned equipment is not always the same as released operating capacity.
- Commercial reservation is not the same as technical load acceptance.
- Customer equipment installation is not the same as go-live approval.
- Dynamic loads require observation and staged approval — not instantaneous release to full contracted capacity.
3. Key Definitions
| Term | Meaning | Why It Matters |
|---|---|---|
| Available power | Power that is physically connected and capable of being delivered | Available ≠ commissioned or released — must not be sold as ready capacity without further verification |
| Reserved capacity | Capacity commercially set aside for a customer pending technical readiness | Creates commercial commitment without necessarily creating operating commitment |
| Installed capacity | Capacity where physical equipment is in place | Installed ≠ commissioned — untested equipment cannot safely receive customer load |
| Commissioned capacity | Capacity that has completed functional testing and sign-off | Commissioned is closer to ready, but still may not equal released without safety and support prerequisites |
| Released load | Load formally approved through the readiness gate process | The only load state that should be treated as customer-ready and SLA-eligible |
| Load step | A discrete increment of customer load added during staged release | Smaller increments allow observation of system behavior before proceeding |
| Initial energization | First application of power to customer equipment under controlled conditions | Not the same as go-live — a controlled test with hold points and rollback plan |
| Dynamic power capability | Characterization of how a customer load changes over time | Determines whether standard monitoring is sufficient or if a dynamic power schedule is required |
| Readiness gate | A defined checkpoint in the release process requiring evidence before proceeding | Prevents premature load acceptance due to schedule or commercial pressure |
| Sign-off domain | An organizational function with authority and responsibility to verify readiness in their area | Distributed sign-off prevents a single authority from approving outside their competence |
| Punch list | Outstanding construction or commissioning items not yet complete | Must be classified as blocking or non-blocking before load release decisions are made |
| Critical open item | A punch list item that creates risk to safety, infrastructure, operations, or customer service if not resolved | Blocks load release until resolved or formally risk-accepted with appropriate authority |
| Operational handoff | The formal transition of a system from commissioning to operations team ownership | Should be documented with evidence — not assumed from project completion date |
| SLA commencement | The point at which service level obligations begin to apply | Must be tied to load release completion, not commercial reservation or installation date |
4. Readiness Review Domains
| Domain | Readiness Question | Typical Evidence | Required Sign-Off |
|---|---|---|---|
| Construction completion | Is construction complete enough to support safe load release? | As-built drawings, punch list, turnover package | Construction manager, commissioning lead |
| Safety program | Is the EHS program active and sufficient for load release operations? | Site safety plan, PTW active, LOTO procedures, emergency response plan | EHS lead, operations director |
| Electrical commissioning | Have all electrical systems been tested and commissioned? | Commissioning reports, relay test records, switching procedures, arc flash labels | Electrical engineer, commissioning authority |
| Cooling commissioning | Have cooling systems been commissioned and load-tested? | Cooling commissioning report, flow/pressure test, CDU commissioning, leak tests | Mechanical engineer, facilities lead |
| Controls and monitoring | Are BMS, EPMS, and alarm systems active and configured? | Controls commissioning report, alarm routing test, dashboard verification | Controls engineer, operations lead |
| Security and access | Are perimeter, access control, and escort procedures active? | Access control commissioning, badge matrix, CCTV operational, visitor process | Security lead, operations lead |
| Connectivity | Are required customer circuits installed, tested, and demarcated? | Circuit delivery records, OTDR tests, cross-connect records | Network lead, campus operations |
| Tenant installation | Is customer equipment installed, connected, and ready for energization? | Installation inspection, leak check, connection verification, customer sign-off | Commissioning lead, customer representative |
| Operations staffing | Is operations staff trained and available for load release? | Training records, shift coverage, escalation matrix active | Operations director |
| Documentation | Is required operating documentation complete and available? | As-builts, operating procedures, customer handbook, emergency contacts | Operations lead, commissioning authority |
| Customer readiness | Is the customer ready for staged energization? | Customer contact confirmed, emergency contacts, workload readiness confirmation | Commercial/account lead, customer representative |
| Commercial/SLA trigger | Is the commercial package defined for SLA commencement post-release? | Service order executed, billing terms confirmed, SLA start criteria documented | Commercial lead, operations director |
5. Readiness Gate Model
6. Gate 1: Construction Completion Review
Construction completion review does not require that every punch item be closed — it requires that the state of completion is documented, open items are classified, and the campus is safe and functional enough to begin commissioning activities. Key evidence includes the as-built drawing set, classified punch list distinguishing critical from non-critical items, commissioning boundary document defining what is within scope for this gate, turnover package from general contractor or construction manager, and field inspection record.
7. Gate 2: Safety Program Verification
Safety program verification confirms that the EHS plan is active and project-appropriate, PTW procedures are operational and understood, LOTO procedures cover the equipment to be energized, qualified electrical persons are identified, PPE is available and specified, the emergency response plan is active and first responders are coordinated, muster points are established and communicated, incident reporting procedures are in place, and stop-work authority is understood and protected.
8. Gate 3: Electrical Commissioning Review
| Electrical Item | Evidence Required | Sign-Off Owner | Blocking Condition Example |
|---|---|---|---|
| Source availability | Utility or generation confirmation, metering active | Electrical engineer | Source not confirmed, metering not verified |
| MV feeder | Cable test report, insulation resistance, continuity | Electrical engineer | Failed cable test, incomplete installation |
| Switchgear | Factory test report, site installation report, trip test | Commissioning authority | Trip function not verified, arc flash label missing |
| Relay/protection | Relay setting sheet, functional test record, coordination study | Protection engineer | Relay not programmed, settings not verified |
| Transformer | Factory test report, oil test, turns ratio, installation inspection | Electrical engineer | Oil not tested, installation inspection incomplete |
| Metering | Meter calibration, CT ratio test, energy management integration | Electrical engineer / operations | Meter not calibrated, customer billing meter unverified |
| UPS | Factory acceptance test, site commissioning, static/dynamic test, battery test | Commissioning authority | Static transfer not tested, battery autonomy not verified |
| Grounding | Ground resistance test, bonding verification | Electrical engineer | Ground resistance exceeds design value |
| Power quality | Power quality baseline measurement, harmonic survey | Electrical engineer | Harmonic levels requiring customer or campus mitigation not resolved |
| Switching procedure | Normal and emergency switching procedure reviewed and approved | Operations lead | No procedure exists for key switching scenarios |
| Arc flash labels | Labels applied per current study at all access points | Electrical engineer / EHS | Labels missing, or study not current to installed configuration |
| Emergency shutdown | EPO function tested, scope confirmed, customer EPO coordinated | Commissioning authority | EPO scope unclear, EPO not tested |
9. Gate 4: Cooling Commissioning Review
| Cooling Item | Evidence Required | Sign-Off Owner | Blocking Condition Example |
|---|---|---|---|
| Heat rejection | Dry cooler/fluid cooler/chiller commissioning report, capacity test | Mechanical engineer | Capacity not verified at design condition |
| Pump skids | Pump commissioning report, flow and pressure test | Mechanical engineer | Flow below design, pump vibration not resolved |
| Loop flow/pressure | Hydraulic balance report, pressure differential at design flow | Mechanical engineer | Flow imbalance to CDU/CRAH units |
| Supply/return temperature | Setpoint verification, control response test | Controls engineer / mechanical | Supply temperature not stable at load |
| CDU/manifold | CDU commissioning report, QD leak test, flow/pressure at each manifold | Mechanical engineer | QD leak detected, flow below design |
| Residual air cooling | CRAC/CRAH commissioning, airflow measurement, containment verification | Facilities lead | Airflow imbalance, containment gaps |
| Leak detection | Leak detection system functional test, alarm routing verified | Facilities / operations | Leak detection not functional, alarm not routed |
| Fluid chemistry | Fluid sample analysis, inhibitor concentration within spec | Mechanical engineer | Inhibitor out of range, corrosion indicators present |
| Controls integration | Cooling controls integrated to BMS, setpoint control verified | Controls engineer | BMS/cooling control integration incomplete |
| Thermal response | Partial load test with monitoring of supply/return delta, response time | Commissioning authority | Thermal response exceeds design parameters at test load |
10. Gate 5: Controls and Monitoring Verification
Controls and monitoring verification confirms that BMS, EPMS, and SCADA where applicable are fully commissioned, all critical points are alarmed, alarm routing to operations staff is tested and verified, trend logging is active, dashboards are functional, customer portal integration where applicable is tested, ticketing integration is active, escalation contacts are configured and confirmed, data historian is recording, and loss-of-communications alarm is functional.
11. Gate 6: Security and Access Readiness
Security readiness confirms that campus perimeter controls are active, gates and access points are operational, the badge matrix is configured for the first tenant load, visitor process is operational and staff are trained, contractor access process is functioning, escort rules are documented and communicated, CCTV is commissioned and recording with defined retention, access logs are active, restricted zone definitions are in place, delivery routes are controlled, emergency responder access procedures are confirmed with local first responders, and photography/device restrictions are communicated.
12. Gate 7: Connectivity and Tenant Demarcation Readiness
Connectivity readiness confirms that carrier circuits required for customer go-live are installed and tested, the MMR is operational, cross-connects are complete per customer order, tenant demarcation is documented and accepted, route diversity verification is complete where required, out-of-band management path is active, customer network separation is confirmed, OT/IT boundaries are active, circuit test records are complete, carrier contact list is available, maintenance notification procedures are established, and network incident escalation paths are tested.
13. Gate 8: Tenant Installation Readiness
Tenant installation readiness confirms that racks are installed in approved positions, cabling is complete per approved plan, power connections are made per approved circuit assignments, liquid cooling connections are complete and leak-checked where applicable, equipment is labeled per campus standard, customer has signed off on installation completeness, firmware or configuration prerequisites are complete or their absence is accepted, load profile and dynamic power capability have been confirmed as current, emergency contacts are documented, support contacts are active, customer operations team is ready for staged energization, and no unauthorized modifications are present.
14. Gate 9: Initial Energization Approval
Initial energization is a controlled, supervised event — not a routine power-on. It requires a pre-energization meeting with all responsible parties, a complete sign-off packet documenting that all preceding gates are satisfied, identified switching authority, active communication bridge between switching authority, operations, and customer representative, defined safe work boundaries, documented test plan and rollback plan, monitoring staff actively watching systems, customer representative available, and defined hold points after each energization step.
15. Gate 10: Incremental Load Step Approval
| Load Step | Objective | Monitoring Focus | Pause / Hold Trigger | Approval Required |
|---|---|---|---|---|
| No-load energized state | Verify power delivery without customer workload | Voltage stability, no trips, cooling idle behavior | Any trip, alarm, or unexpected reading | Electrical engineer, campus operations |
| Low-load validation | Observe system response to initial customer load | Power draw, cooling response, alarm state, customer load behavior | Load step size abnormally large, cooling not responding | Campus operations, EHS confirmation |
| Intermediate load | Confirm sustained performance at partial contracted capacity | Power quality, supply/return temperatures, alarm trends | Temperature rising, power quality degradation, repeat alarms | Campus operations, mechanical engineering |
| High-load validation | Approach contracted operating envelope, observe ramp behavior | Power ramp rate, cooling lag time, load step size, alarm state | Ramp rate exceeds dynamic power schedule, cooling instability | All primary sign-off domains |
| Maximum approved operating load | Confirm operation at full contracted load is stable and sustainable | All metrics, 24+ hour observation window per project requirements | Any metric outside envelope, customer behavior change | Operations director, commissioning authority |
| Steady-state transition | Formally close load release and transition to operations | All systems nominal, no open blocking items | Any unresolved item requiring investigation | Full sign-off domain record, customer acceptance |
16. Gate 11: Steady-State Transition Approval
Steady-state transition confirms that load is stable and within the operating envelope, all monitored systems are within normal parameters, alarm state is clean with no unresolved active alarms, customer workload behavior is consistent with the declared load profile, support channels are active, SLA commencement where applicable is confirmed per contract terms, billing trigger where applicable is documented, maintenance windows and notification process are active, reporting cadence is established, operational handoff is complete, and post-go-live review is scheduled.
17. Sign-Off Domains
| Sign-Off Domain | Sign-Off Responsibility | Typical Evidence | Can Block Load Release? |
|---|---|---|---|
| Plant operations | Operational readiness of all plant and utility systems | System commissioning reports, operating procedure confirmation | Yes — primary blocking authority |
| Facilities operations | Building systems, cooling, environmental, logistics | Cooling commissioning, HVAC reports, loading dock readiness | Yes |
| Electrical engineering | Electrical commissioning, protection, and safety documentation | Commissioning reports, arc flash, switching procedures | Yes — primary blocking authority |
| Mechanical/cooling engineering | Cooling system commissioning and performance | Cooling commissioning report, thermal test results | Yes |
| Controls/monitoring | BMS, EPMS, alarm routing, escalation | Controls commissioning report, alarm test record | Yes |
| EHS | Safety program active, PTW/LOTO, emergency response, training | Safety plan, PTW system active, training records | Yes — primary blocking authority |
| Security | Access control, perimeter, CCTV, visitor process | Security commissioning, badge matrix, CCTV records | Yes |
| Network/connectivity | Customer circuits, cross-connects, demarcation, OT/IT boundary | Circuit delivery records, OT/IT boundary document | Yes for connectivity-dependent tenants |
| Commissioning lead | Overall commissioning completeness and documentation | Commissioning close-out report, punch list final status | Yes |
| Tenant/customer representative | Customer equipment readiness and installation acceptance | Installation sign-off, customer contact confirmation | Yes — customer must accept their installation |
| Operations director | Overall readiness determination and authority to proceed | Review of all domain sign-offs | Yes — final authority for load release |
| Commercial/account lead | SLA and billing commencement confirmation where applicable | Executed service order, SLA/billing trigger defined | Conditional — only if SLA/billing trigger is load-release-dependent |
18. Blocking vs. Non-Blocking Open Items
| Open Item Type | Example | Typical Treatment | Required Approval |
|---|---|---|---|
| Life safety | Fire suppression system not functional, egress blocked | Blocking — must be resolved before any load | EHS lead, AHJ if applicable |
| Electrical safety | Arc flash label missing, relay not tested, LOTO procedure not in place | Blocking — must be resolved before energization | Electrical engineer, EHS lead |
| Cooling capacity | Pump not commissioned, CDU leak unresolved, flow below design | Blocking — must be resolved before load | Mechanical engineer, commissioning authority |
| Monitoring/alarming | Critical alarm not routed, BMS point offline, escalation contact missing | Blocking — must be resolved before load release | Controls engineer, operations lead |
| Security/access | Perimeter not secured, badge access not configured | Blocking — must be resolved before load | Security lead |
| Documentation | As-built not yet complete, operating procedure being finalized | May be conditionally non-blocking with formal risk acceptance and due date | Operations director |
| Cosmetic | Paint not finished, ceiling tile missing in non-critical area | Non-blocking with documented acceptance | Construction manager |
| Commercial/admin | Invoice pending, minor contract exhibit not yet signed | Non-blocking for load release but must be tracked | Commercial lead |
19. Dynamic Power and Load Behavior During Release
| Dynamic Behavior | Risk | Required Review | Operating Control |
|---|---|---|---|
| Rapid ramp-up | Power quality impact, cooling lag, protection trip | Dynamic power schedule, load step plan review | Maximum ramp rate documented and monitored |
| Rapid ramp-down | Overvoltage, reverse power where applicable, cooling overshoot | Ramp-down characterization during low-load validation | Ramp-down behavior confirmed normal before high-load step |
| Simultaneous cluster restart | Large single load step, multiple simultaneous starts | Restart sequence review, sequencing controls | Restart procedure confirmed with customer, staged restart required |
| Power quality sensitivity | Customer equipment sensitive to sag, harmonics, or flicker | Power quality baseline review, equipment specification review | Power quality issue resolved before high-load step |
| Cooling lag | Temperature spike before cooling system responds to load increase | Cooling response time test during intermediate load step | Load step size limited to cooling response capability |
| Workload scheduler change | Job scheduler change creates unexpected large load event | Scheduler notification requirements in dynamic power schedule | Customer notifies campus of major scheduler changes in advance |
| Failover event | System failover may create transient large load change | Failover sequence characterization | Failover procedure documented, campus notification required for planned failovers |
| Demand limit disabled | Customer disables demand limiting, creating overload risk | Demand limiting capability review during onboarding | Demand limiting requirement captured in dynamic power schedule |
20. Offering Model Variations
| Offering Model | Load Release Focus | Customer Evidence | Campus Evidence | Special Boundary |
|---|---|---|---|---|
| Turnkey colocation | Full 11-gate process, all domains | Installation sign-off, load profile, dynamic power schedule | Full commissioning record, sign-off packet | SLA/billing trigger defined at Gate 11 |
| Dedicated suite/building | Building-level gates plus suite/cage commissioning | Installation complete within licensed area | Building systems commissioned, tenant space commissioned | Customer may have more responsibility for within-suite commissioning |
| Powered shell | Shell-level electrical and mechanical commissioning, handover package | Customer fit-out completion within shell | Shell power, cooling, and utilities commissioned to handover point | Load release at shell boundary, customer operates beyond |
| Powered land | Power delivery point commissioning, metering verification | Customer site readiness on parcel | Power delivery to parcel, metering commissioned | Customer responsible for all load release within parcel |
| Carrier/network service | Circuit delivery, MMR commissioning, cross-connect completion | Carrier equipment commissioned | MMR active, circuit delivered, cross-connect complete | Carrier responsible for service activation beyond demarcation |
| Managed connectivity | Circuit delivery and service activation | Customer demarcation acceptance | Full circuit delivery, testing, monitoring | SLA start tied to circuit delivery acceptance |
21. Load Release Record Package
The load release record package is the audit trail that proves the release was evidence-based and properly authorized. It should include, at minimum:
- Readiness checklist with all domain sign-offs
- Sign-off sheet with signatures or equivalent electronic authorization
- Construction completion record and punch list final status
- Safety program verification record
- Electrical commissioning report
- Cooling commissioning report
- Controls and alarm verification record
- Security and access readiness record
- Connectivity readiness record
- Tenant installation acceptance record
- Dynamic power capability schedule where applicable
- Initial energization record
- Load step records for each step with monitoring data
- Trend data for sustained observation period
- Incident and anomaly log from release process
- Customer acceptance record
- Operations handoff record
- SLA/billing commencement confirmation where applicable
22. Pause, Rollback, and Re-Review
Load release can be paused, held, rolled back to a lower load level, or placed under additional monitoring at any point in the process. The ability to pause or roll back is not a failure of the process — it is the process functioning correctly.
Triggers that should initiate a pause or rollback include: any safety issue or near miss, unexpected electrical alarm or trip, power quality event, cooling instability or high-temperature alarm, leak detection alarm, network instability, access or security issue, customer load behavior outside approved profile, customer installation deviation discovered, documentation gap identified, or unresolved critical punch item. Any of these triggers requires a root cause review, corrective action, and a formal re-approval step before load release proceeds. Customer installation or configuration changes may reset one or more gates.
23. Governance and Auditability
Load release decisions must be auditable. Sign-off records must be retained in a retrievable format for the duration required by project agreements, insurance requirements, and regulatory obligations. Changes to the load release plan after initial approval must be version-controlled with timestamps and approver records. Customer acceptance must be documented in writing. Operating teams should have access to the load release record as a reference for future maintenance, incidents, and expansions. Post-go-live reviews should inform future readiness criteria improvements.
Framework Disclaimer: This reference describes a load release and readiness review framework only. Actual load release authority, readiness criteria, commissioning requirements, safety prerequisites, customer obligations, service commencement triggers, operating limits, and sign-off requirements must be defined in approved project-specific procedures, agreements, technical exhibits, commissioning records, and site rules.
Implementation Notice
This reference describes a framework model. It is not a substitute for project-specific engineering, permitting, interconnection approval, environmental review, safety review, legal documentation, procurement, commissioning, or operating procedures. All capacity, availability, timeline, and commercial terms are project-specific and subject to applicable approvals and agreements.