Reference Materials
GridCore Model Reference Architecture and Framework Documents.
Reference materials covering campus architecture, offering models, interface matrices, operations boundaries, safety frameworks, connectivity planning, load release procedures, tenant onboarding, and visitor access. These are framework documents — final implementation is project-specific, subject to diligence, engineering, permitting, and regulatory approvals.
Framework Reference Only. These materials describe a model architecture and operating framework. No content on this page constitutes a commitment of capacity, an offer of services, a representation of regulatory status, a claim of carrier availability, or confirmation that any specific project is currently operational, permitted, or contractually committed. All implementation is project-specific, subject to diligence, engineering, permitting, contracting, and applicable regulatory approvals.
Reference Index
All Reference Documents
Each reference document describes how the GridCore Model addresses a specific domain. Actual implementation details vary by site, project, and commercial scope.
Campus Architecture Reference
Site-level power architecture: generation, MV distribution, campus topology, critical paths, grid interface strategy, and phased capacity delivery.
Colocation Service Model Reference
Managed space, power, cooling, connectivity, monitoring, and operations framework for high-load compute tenants on an integrated campus.
Powered Shell Model Reference
Commissioned compute-ready building delivery: scope, power paths, cooling basis of design, handover package, and customer operating interface.
Powered Land Interface Matrix
Defines responsibility boundaries for powered land: parcel, power delivery, metering, fiber, access, security, utilities, maintenance, and emergency response.
Operations Boundary Matrix
Operating domains, owners, scopes, escalation paths, and cross-domain interfaces for integrated campus operations.
Safety, Security & Compliance Framework
EHS, PTW/LOTO, emergency response, PSM, environmental compliance, physical security, OT/IT cybersecurity, audits, and corrective actions.
Connectivity Planning Reference
Carrier entry, route diversity, meet-me room placement, cross-connect process, tenant demarcation, inter-building fiber, and OT/IT network segmentation.
Tenant Onboarding Reference
Staged technical onboarding from capacity discussion through load release and steady-state operations handoff. Includes dynamic power capability framework.
Load Release & Readiness Review Reference
Formal load release gates: construction completion, safety verification, electrical and cooling commissioning, controls, security, tenant installation, and step approvals.
Visitor Access & Site Conduct Reference
Visitor categories, pre-arrival registration, check-in requirements, escort rules, restricted zone definitions, conduct rules, and recordkeeping.
Community & First Responder Engagement Reference
Stakeholder engagement, emergency coordination, hazard communication, tabletop exercises, environmental planning, and workforce development framework.
Data Center Agreement Framework Reference
How the Universal Data Center Agreement Framework structures customer MSAs, Service Orders, schedules, vendor agreements, procurement orders, operating exhibits, and project-specific contracting workflows.
Interface Matrix — Powered Land
Define the Boundary Before Construction Begins.
Powered Land only works when the campus operator and customer understand exactly where responsibility transfers. The matrix below illustrates the framework — actual assignments are defined in the project-specific agreement.
| Topic | Campus Platform | Customer | Joint / Coordinated |
|---|---|---|---|
| Parcel boundary | Define and convey | — | Survey and acceptance |
| Access roads | Campus roads to parcel | Internal facility roads | Access point coordination |
| Construction logistics | Campus site rules and safety | Facility construction management | Contractor access, PTW, safety induction |
| MV power delivery point | Deliver to defined interface point | — | Metering and protection coordination |
| Transformers and switchgear | — | Customer-side equipment | Protection coordination with campus |
| Metering | Campus delivery point metering | Internal metering if required | Reconciliation and billing |
| Internal electrical distribution | — | Full customer responsibility | — |
| Cooling systems | — | Full customer responsibility | Water supply interface where applicable |
| Fiber pathway | Campus fiber to parcel entry | — | Route coordination and splice point |
| Carrier procurement | — | Customer direct with carriers | Campus demarcation access |
| Building demarcation | Campus-side demarcation | Building MDF and internal cabling | Cross-connect process |
| Physical security perimeter | Campus perimeter and gates | Internal facility security | Access protocols and credential standards |
| Internal security systems | — | Full customer responsibility | Integration with campus visitor log |
| Visitor management | Campus check-in and log | Internal facility visitor rules | Escort standards and badge protocol |
| Emergency response | Campus SERP and first responder interface | Facility emergency procedures | Joint drills and hazard communication |
| Maintenance windows | Campus power and utility maintenance notice | Facility maintenance scheduling | Advance coordination and impact review |
| Environmental compliance | Campus-level permits | Facility-level permits where separate | Joint reporting where applicable |
| Permits | Campus infrastructure permits | Facility building and electrical permits | Shared utility corridor permits |
| Commissioning | Campus delivery point commissioning | Facility commissioning | Interface point joint testing |
| Load release | Campus readiness review and approval | Facility readiness certification | Joint load step sign-off |
| Operational escalation | Campus ops team for delivery point issues | Facility ops team for internal issues | Cross-boundary incident coordination |
Illustrative framework only. Actual responsibility assignments are defined in the project-specific Powered Land agreement.
Load Release Reference
No Load Without Evidence.
The GridCore Model treats load release as a formal operating decision requiring documented readiness across all relevant domains before tenant load is accepted.
01
Construction Completion Review
Scope confirmation, punch list resolution, and as-built documentation review.
02
Safety Program Verification
EHS program, PTW system, LOTO program, and emergency procedures active and staffed.
03
Electrical Commissioning Review
Protection relay testing, switchgear verification, UPS commissioning, and MV system validation.
04
Cooling Commissioning Review
Cooling system at setpoint, redundancy tested, monitoring integrated, and thermal performance validated.
05
Controls and Monitoring Verification
SCADA/BMS/monitoring systems live with alarming active across all critical systems.
06
Security and Access Readiness
Access controls active, CCTV commissioned, visitor management operational, and zone definitions enforced.
07
Tenant Installation Readiness
Equipment installed per plan, cabling complete, and customer sign-off on installation scope.
08
Initial Energization Approval
All domain leads sign off on readiness before first energization event.
09
Incremental Load Step Approval
Each load step requires monitoring confirmation and sign-off before proceeding to the next.
10
Steady-State Transition Approval
Full load stable, all systems within parameters, and customer operations formally confirmed.
Required Sign-Off Domains
Tenant Onboarding Reference
A Controlled Path from Capacity Interest to Live Load.
Tenant onboarding is where marketing commitments become operational reality. Each stage must be completed before the next is started.
01
Initial Capacity Discussion
Confirm power, density, cooling, network, security, timeline, and commercial fit.
02
NDA and Technical Exchange
Execute NDA. Exchange detailed technical and commercial requirements under confidentiality.
03
Load Profile and Dynamic Power Review
Document ramp rates, workload scheduling, max load steps, power-quality sensitivity, and restart behavior.
04
Power and Cooling Requirements Review
Confirm density, redundancy, cooling approach, UPS, and capacity allocation.
05
Connectivity and Security Review
Confirm network requirements, demarcation, OT/IT boundaries, and security posture.
06
Commercial Scope and SLA Alignment
Align service model, SLA structure, maintenance windows, and dynamic power schedule.
07
Installation Logistics Plan
Define delivery schedule, staging areas, equipment routing, safety induction, and access requirements.
08
Infrastructure Readiness Review
Review commissioning records, monitoring status, safety program, and operational support plan.
09
Equipment Delivery and Installation
Coordinate delivery and installation under campus access, logistics, and safety rules.
10
Staged Load Release
Introduce load per approved procedure with monitoring confirmation at each step.
11
Steady-State Operations Handoff
Formal transition to steady-state with defined support interfaces and escalation paths.
12
Post-Go-Live Review
Confirm performance, document lessons, and align on ongoing reporting and SLA tracking.
Dynamic Power Capability
High-Density AI/HPC Workloads Require Dynamic Power Planning.
High-density AI and HPC workloads can create large and rapid load changes. Onboarding should capture expected ramp rates, workload scheduling behavior, maximum load steps, power-quality sensitivity, restart behavior, and any customer-side controls that limit abrupt demand changes. These assumptions should be reflected in the applicable SOW, SLA, or Dynamic Power Capability Schedule.
Visitor Access Reference
Visitor Access Is an Operational Control.
Energy-integrated compute campuses include high-voltage systems, fuel systems, active construction zones, restricted compute areas, and operational technology environments. Visitor access must be controlled, documented, and aligned with site safety and security rules.
Visitor Categories
Check-In Requirements
Site Conduct Rules
Framework Disclaimer
This is a reference framework. Final visitor access procedures must be adapted to the specific site, applicable law, customer requirements, security posture, and safety program.
Applying the GridCore Model
These reference materials are starting points, not finished specifications.
Each ECC implementation requires site-specific engineering, permitting, contracting, and regulatory work. Use these frameworks to structure the conversation — then engage directly with our team to develop project-specific materials.