Powered Land Interface Matrix — GridCore Reference

1. Purpose and Scope

This reference defines the responsibility boundary framework for Powered Land as a structured infrastructure delivery model within a GridCore campus. It is not a final lease, sale agreement, easement, interconnection agreement, utility agreement, construction contract, operating agreement, service level agreement, or permit document.

It is intended to align the customer, campus operator, developer, EPC contractor, utility, carrier, security team, safety team, and operations teams before construction begins. Actual responsibility allocation must be documented in project-specific agreements, exhibits, site rules, and approved operating procedures.

Powered Land should be treated as an interface-controlled delivery model, not as a loose real estate transaction. Every boundary left undefined before construction is a risk that will be resolved under pressure.

2. Powered Land Definition

Powered Land is a project-specific development model in which the customer receives rights to use or develop a defined parcel or pad within a larger GridCore campus, together with defined access to campus-side infrastructure interfaces such as power delivery, fiber pathway, roads, security perimeter, emergency response coordination, and shared utility corridors.

What the Customer Receives

Rights to build and operate a customer-owned data center or compute facility on a defined parcel
Access to a campus-side power delivery point at a defined capacity reservation and voltage
Access to fiber pathway, conduit, or demarcation support as scoped per project
Site access under campus rules — roads, security perimeter, emergency coordination
Defined interface with campus operations for maintenance windows, load release, and escalation

What the Customer Remains Responsible For

Internal facility design, structural engineering, and construction management
Internal electrical systems downstream of the defined delivery point
Internal cooling systems, heat rejection equipment, and fluid management
IT deployment, racking, networking, and compute operations
Customer-side commissioning, maintenance programs, and facility operations
Facility-specific permits, environmental obligations, and code compliance unless otherwise agreed

3. Why the Interface Matrix Matters

Powered Land delivers significant development efficiency — customers can bypass many site acquisition, permitting, and power infrastructure steps. That efficiency creates risk if boundaries are assumed rather than documented. Common failure modes include:

Customer assumes powered land equals energized, fully released load — it does not
Campus assumes customer understands switching authority and safety limits — they may not
Carrier availability is assumed but not verified before construction commitments
Construction logistics are not coordinated with active campus operations
Emergency response boundary is unclear between campus and customer facility
Shared utility corridors are damaged or blocked during customer construction
Metering and billing boundaries are undefined, creating disputes at commissioning
Security rules differ between campus perimeter and customer facility
Environmental obligations are not clearly assigned, creating regulatory exposure

The matrix is the control document that turns a parcel into an operable infrastructure interface. Powered Land without a defined interface matrix is an informal arrangement that will fail at the first boundary event.

4. Powered Land vs. Powered Shell vs. Colocation

Model	Customer Receives	Campus / Platform Role	Customer Role	Boundary Complexity	Best Fit
Powered Land	Parcel rights, power delivery point, site interfaces	Deliver power to defined point, govern shared infrastructure and rules	Design, build, operate own facility	High — customer manages own building, systems, operations	Hyperscale build-to-suit, large HPC, AI campus, industrial compute
Powered Shell	Pre-engineered building, commissioned base systems, power and cooling to customer boundary	Deliver commissioned building and defined building systems	Deploy IT, operate IT environment, maintain customer-owned systems	Medium — building delivered, customer operates within defined scope	Colocation-adjacent customer wanting to control their facility without building from scratch
Turnkey Colocation	Managed data center service: space, power, cooling, connectivity, monitoring, support	Operate all campus and facility infrastructure	Deploy and operate IT equipment	Low for customer — all campus/facility obligations sit with operator	Enterprises, AI workloads, carriers, hyperscale overflow needing immediate capacity

5. Interface Domains Overview

Domain	Campus / Platform Scope	Customer Scope	Joint / Coordinated Scope	Required Exhibit
Parcel boundary	Define and maintain campus boundary	Comply with parcel limits	Survey coordination	Parcel / legal description exhibit
Access roads	Maintain campus roads	Use per site rules	Heavy haul routing	Access exhibit
Construction logistics	Approve and coordinate	Manage and execute	Logistics plan	Construction plan exhibit
Site safety	Enforce campus safety rules, PTW	Comply with all campus rules, maintain own program	Joint inductions, incident reporting	Site safety rules exhibit
Power delivery point	Design, build, commission to defined point	Connect downstream of delivery point	Delivery point definition, protection coordination	Power delivery exhibit
Metering	Install and maintain revenue meter at defined point	Install and maintain customer sub-metering	Meter validation	Metering exhibit
Customer electrical systems	Review designs for campus interface impact	Design, build, commission, operate	Protection coordination	Customer electrical design review
Cooling systems	Review heat rejection impacts	Design, build, commission, operate	Water use, plume, noise review	Cooling review
Fiber pathway	Provide conduit, splice, MMR access	Procure carriers and circuits	Pathway and demarcation coordination	Fiber demarcation exhibit
Carrier procurement	Facilitate access	Procure independently	Access coordination	Carrier exhibit
Security perimeter	Maintain campus perimeter	Maintain internal facility security	Incident escalation	Security exhibit
Visitor management	Enforce campus visitor rules	Pre-register and sponsor visitors	Shared log where required	Access and visitor exhibit
Emergency response	Campus emergency plan, coordinate first responders	Customer facility emergency plan	Joint drills, muster coordination	Emergency response exhibit
Maintenance windows	Define planned outage windows	Align customer maintenance	Advance notice, coordination	Operations escalation exhibit
Environmental compliance	Campus-level permits	Customer facility permits	Shared reporting where required	Environmental matrix exhibit
Load release	Campus delivery readiness	Customer facility readiness package	Joint inspection and approval	Commissioning and load release exhibit

6. Parcel, Easements, and Civil Interface

The parcel and civil interface must be defined before customer construction begins. Shared infrastructure — utility corridors, access roads, drainage, fiber pathways — can be permanently damaged or disrupted if customer construction is not coordinated with the campus. Key civil items include:

Civil Item	Definition Required	Typical Campus Responsibility	Typical Customer Responsibility	Evidence / Approval Required
Parcel survey	Legal boundary, corners, easements	Maintain master survey	Commission customer survey	Stamped survey on file
Access road connection	Entry point, route, load rating	Maintain campus roads	Comply with routing, manage haul	Route approval
Laydown area	Location, duration, restoration obligation	Approve location	Maintain and restore	Approved logistics plan
Utility corridor crossing	Route, depth, protection method	Define corridor zones	Submit for approval, protect in place	Excavation approval, as-builts
Drainage tie-in	Connection point, capacity, permit	Define connection options	Design, permit, execute	Drainage approval
Excavation permit	Utility locate, dig safe process	Define campus utility maps	Obtain permits, perform locates	Permit and locate records
Heavy equipment route	Load limits, bridge ratings, restrictions	Define campus limits	Plan haul routes in advance	Route approval
Site restoration	Pre-construction baseline, obligation scope	Define baseline	Execute and fund restoration	Restoration sign-off

7. Power Delivery Interface

The power delivery interface is the most consequential boundary in the Powered Land model. Every element below must be defined in project-specific exhibits before construction and commissioning. Commercially reserved capacity is not the same as energized, commissioned, released load.

Commercially reserved capacity does not become usable customer load until the applicable delivery infrastructure, customer-side systems, commissioning records, safety procedures, controls, monitoring, and operating approvals support load release.

Power Interface Element	Required Definition	Typical Campus Responsibility	Typical Customer Responsibility	Required Before Load Release
Capacity allocation	MW reserved, voltage level, contract term	Confirm available capacity	Accept allocation terms	Yes — capacity reservation must be confirmed
Delivery voltage	kV level at delivery point	Design and build to agreed voltage	Design customer system for delivery voltage	Yes — voltage confirmed at point
Delivery point	Physical location, switchgear bay, bus designation	Define and build	Accept and record	Yes — delivery point as-built
Feeder route	Path from campus source to delivery point	Design, build, commission	Provide access for inspection	Yes — feeder as-built
Switchgear / breaker boundary	Which breaker is campus-owned; which is customer-owned	Define, label, document	Accept demarcation	Yes — boundary labeled and documented
Protection settings	Relay coordination, trip settings	Define campus-side relay settings	Coordinate customer-side protection	Yes — protection coordination study on file
Metering point	Physical meter location, metering class	Install and commission revenue meter	Accept metering point	Yes — meter commissioned and verified
Power quality monitoring	PQ monitoring scope, recording requirements	Provide baseline PQ data	Monitor customer-side quality	Yes — baseline monitoring active
Grounding interface	Grounding system boundary, bonding	Campus ground grid design	Customer grounding design coordination	Yes — grounding coordination documented
Arc flash / labeling	Incident energy study, labeling at delivery point	Provide arc flash study for delivery point	Conduct study for customer-side systems	Yes — labels installed
Switching procedure	Step-by-step switching for normal and emergency conditions	Campus-side switching procedure	Customer-side switching procedure	Yes — both procedures on file
LOTO procedure	Energy isolation steps, boundary definition	Campus LOTO for delivery point	Customer LOTO for customer-side systems	Yes — LOTO procedures reviewed
Maintenance coordination	Planned outage windows, notice periods	Define planned maintenance schedule	Accept windows, align customer maintenance	Yes — maintenance process agreed
Emergency trip / shutdown	Campus emergency stop, customer emergency stop, authority	Define campus emergency shutdown	Define customer emergency shutdown	Yes — both shutdown procedures documented
Staged load step approval	Step size, observation period, approval gate	Define load step procedure	Submit load step requests	Yes — load step process agreed

8. Customer Facility Electrical Responsibilities

The customer owns and operates all electrical systems downstream of the defined delivery point. Campus may require design review where customer systems affect shared infrastructure, protection coordination, power quality, safety interfaces, or load release gates.

Typical Customer Electrical Scope

Customer-side transformers, if downstream of delivery point
Customer switchgear, distribution boards, and panelboards
UPS systems and battery energy storage if deployed
Internal power distribution: busbars, RPPs, PDUs, busway
Grounding and bonding within the customer facility
Branch circuits and rack power infrastructure
Customer EPMS, DCIM, or power monitoring systems
Internal maintenance and electrical safety programs
Customer-side commissioning, testing, and documentation
Compliance with applicable electrical codes and campus site rules

Campus may reserve the right to review customer-side designs that affect shared protection coordination, power quality on the campus distribution system, campus safety compliance, or load release eligibility. Review rights should be defined in project-specific exhibits.

9. Cooling and Thermal Responsibility

Powered Land typically leaves internal cooling design and operation to the customer unless a separate thermal utility or shared cooling interface is specifically scoped. However, customer cooling decisions can affect campus operations — water use, power demand profiles, environmental permitting, heat rejection siting, noise, and load release readiness must all be coordinated.

Cooling / Thermal Topic	Typical Owner	Campus Review Trigger	Evidence Needed
Heat rejection equipment	Customer	Siting, noise, plume impact on campus	Thermal study, noise assessment
Cooling water use	Customer	Water rights, permit thresholds, shared source	Water use plan, permit review
Chemical treatment	Customer	Environmental permit, spill risk, shared drainage	Chemical management plan
Fluid loop	Customer	Leak risk to shared infrastructure	System design, leak detection evidence
Mechanical yard layout	Customer	Campus clearances, maintenance access, fire access	Layout drawing approval
Noise assessment	Customer	Campus environmental permit, neighbor impact	Noise study
Plume / discharge impact	Customer	Permit threshold, air quality, visual impact	Plume review where applicable
Customer thermal commissioning	Customer	Load release readiness gate	Commissioning report, test records
Cooling monitoring	Customer	Load step observation period	DCIM or monitoring evidence
Emergency cooling response	Customer (internal) + Campus (coordination)	Campus emergency response plan integration	Emergency plan cross-reference

10. Fiber, Carrier, and Network Interface

The campus may provide conduit pathway, handhole access, splice points, MMR or demarcation support to the parcel boundary. Carrier availability is not assumed unless verified against the specific site, and carrier procurement is typically a customer responsibility unless otherwise scoped.

Connectivity Item	Campus Scope	Customer Scope	Coordination Requirement
Carrier entry	Provide or facilitate campus entry point	Obtain campus access approval	Access coordination, campus rules
Pathway to parcel	Conduit, handhole, splice access to parcel boundary	Internal fiber distribution from demarcation	As-built documentation, pathway capacity
Fiber demarcation	Define MMR or splice point location	Accept demarcation point, install customer fiber	Demarcation exhibit on file
Cross-connect process	Define campus cross-connect procedure if applicable	Request and fund cross-connects	Process documentation
Customer circuit procurement	Facilitate carrier access, not guarantee service	Independently procure carrier circuits	Carrier contracts are customer-owned
Route diversity	Document available entry paths	Specify diversity requirements, validate	As-builts and route documentation
Splice records	Maintain campus fiber records	Maintain customer fiber records	Records on file at commissioning
Network security boundary	Campus OT, security, and IT networks are isolated	Customer networks remain separate	No cross-connection without explicit approval
Out-of-band management	If scoped, define access and control boundary	Operate within defined scope	Access controls and audit logs

11. Security and Access Boundary

Campus security rules apply to all personnel on campus including customer employees, contractors, vendors, and visitors. The customer is responsible for internal facility security within their leasehold, consistent with campus perimeter and site rules.

Security Domain	Campus / Platform	Customer	Joint / Coordinated
Campus perimeter	Design, maintain, operate	—	—
Parcel access	Gate authorization	Sponsor and manage own personnel	Shared access log
Customer facility access	—	Design and operate internal access	Align with campus perimeter rules
Visitor pre-registration	Campus pre-approval required	Customer sponsor	Shared visitor log where required
Contractor onboarding	Induction and badging	Manage own contractor program	Campus safety induction required for all
Delivery route	Define approved route	Schedule and manage deliveries	Advance notice requirement
Emergency responder access	Coordinate and grant	Coordinate internal response	Joint emergency response plan
Badge administration	Campus badge issuance	Customer badge issuance for internal spaces	Coordinated where interface areas overlap
CCTV	Campus perimeter coverage	Internal facility coverage	Incident investigation coordination
Incident reporting	Campus incident report	Internal incident report	Shared escalation path
Access log retention	Campus retains campus access logs	Customer retains internal logs	Available on request for incident review

12. Construction Logistics and Site Rules

Powered Land customers may be constructing inside an active infrastructure campus with energized power systems, operating cooling infrastructure, live carrier networks, and tenant operations. Construction must be controlled to protect shared infrastructure and ongoing campus operations.

Construction Activity	Campus Approval Required?	Customer Responsibility	Reason for Control
Excavation	Yes — permit and utility locate	Execute to approved plan	Underground utilities and campus infrastructure
Crane lift	Yes — lift plan review	Submit lift plan, execute safely	Overhead lines, campus infrastructure, adjacent operations
Electrical energization	Yes — load release gate	Submit readiness package	Campus protection coordination, safety
Hot work	Yes — hot work permit	Execute with fire watch per campus rules	Fire risk to shared structures
Utility tie-in	Yes — coordination required	Submit design, schedule with campus	Live campus utilities
Road closure	Yes — traffic management plan	Manage and restore	Campus access, emergency vehicle routes
Delivery convoy	Yes — advance notice	Schedule and manage	Campus security, road capacity
Temporary power	Yes — approve source and installation	Install and maintain safely	Generator placement, fuel storage, safety rules
Temporary fencing	Yes — location approval	Install and maintain	Campus access routes, visibility, fire access
Night work	Yes — noise and light management plan	Execute to approved plan	Campus operations, environmental, neighbor impact

13. Environmental, Permitting, and Regulatory Boundaries

Campus-level permits and customer facility permits are typically separate instruments issued to separate entities. Regulatory status depends on jurisdiction, utility arrangement, generation configuration, fuel systems, and customer operations. This framework does not constitute legal or regulatory advice.

Compliance Area	Potential Campus Responsibility	Potential Customer Responsibility	Coordination Requirement
Building permits	—	Customer facility permits	Campus construction rules compliance
Electrical permits	Campus electrical systems	Customer electrical systems	Protection coordination review
Environmental permits	Campus site permits	Customer facility permits where required	Shared reporting where triggered
Stormwater	Campus SWPPP	Customer construction SWPPP	Combined review where applicable
Air emissions	Campus permit if generation present	Customer facility air obligations	Combined thresholds where applicable
Water use	Campus water rights	Customer cooling water use	Water use coordination
Chemical storage	—	Customer chemical management	Secondary containment, spill plan coordination
Fuel storage	Campus fuel systems if present	Customer emergency fuel if applicable	SPCC and permit coordination
Waste management	Campus waste program	Customer construction and operating waste	Approved disposal routes
Noise	Campus noise permit if required	Customer construction and operating noise	Combined assessment where required
Safety programs	Campus EHS program	Customer safety program	Interface at campus entry and shared areas
Utility / interconnection requirements	Campus interconnection agreement	Customer connection to campus-side system	Defined in power delivery exhibit

14. Emergency Response Interface

The campus and customer must align on emergency response before customer occupancy and load energization. Life safety authority takes precedence over commercial operations, schedules, and load delivery in all emergency scenarios.

Emergency Scenario	Campus Lead	Customer Lead	Joint Action
Fire alarm	Campus incident command	Customer facility response	Evacuation, first responder coordination, muster
Electrical fault	Campus power team	Customer electrical team	Isolation, protection review, coordinated restoration
Cooling failure	Campus operations	Customer cooling team	IT load shedding, thermal management, escalation
Security incident	Campus security	Customer security	Incident command, law enforcement coordination
Injury / medical event	Campus EHS	Customer EHS	First aid, EMS access, incident report
Severe weather	Campus operations	Customer facility team	Pre-event preparation, muster, post-event inspection
Environmental spill	Campus EHS	Customer EHS	Containment, regulatory notification, cleanup coordination
Carrier outage	Campus connectivity team	Customer network team	Escalation to carrier, customer communication
Customer equipment incident	Campus notified	Customer incident command	Shared infrastructure protection, EHS coordination
Evacuation	Campus incident command	Customer evacuation lead	Campus muster points, accounting, all-clear process

15. Commissioning and Load Release

Powered Land load release requires two independent readiness layers — campus-side delivery point readiness and customer facility readiness. Construction completion alone is not sufficient. Both layers must be aligned, inspected, and approved before load is released.

Campus Delivery Infrastructure Readiness

Delivery point commissioned, metering validated, protection settings documented, switching procedures approved, arc flash labels installed.

Customer Facility Readiness Package

Customer submits commissioning records, electrical single-lines, protection coordination study, LOTO procedures, and safety program documentation.

Interface Inspection

Campus and customer conduct joint inspection of delivery point, metering, breaker boundary, grounding, and arc flash labeling.

Safety and Switching Procedure Review

Both campus and customer switching procedures reviewed for compatibility. LOTO procedures verified. Emergency shutdown authority confirmed.

Metering and Monitoring Validation

Revenue meter tested and validated. Customer sub-metering active. Power quality baseline established. Alarm escalation paths verified.

Initial Energization Approval

Campus approves initial energization of customer facility. Operating authority confirmed. Contacts and escalation matrix current.

First Load Step

Customer brings load to first approved step. Campus monitors delivery point performance. No anomalies allowed to proceed past first step without resolution.

Performance Observation Period

Defined observation window at first load step. Power quality, thermal performance, cooling readiness, and monitoring all verified.

Subsequent Load Steps

Each additional load step approved by campus operations after review of prior step performance. Thermal, electrical, and monitoring criteria must be met.

Steady-State Operations Handoff

Final load accepted. Operations escalation matrix active. Maintenance coordination process in effect. Ongoing load requests follow change management procedure.

16. Operating Escalation Matrix

Issue Type	Customer First Contact	Campus First Contact	Escalation Trigger	Required Documentation
Power quality issue	Customer ops lead	Campus power team	PQ event logged or customer complaint	PQ data, load profile, event log
Metering dispute	Customer billing contact	Campus commercial team	Billing discrepancy submitted	Meter records, interval data
Planned maintenance	Customer ops scheduler	Campus ops scheduler	Notice required per contract	Maintenance notice, affected systems
Emergency outage	Customer on-call	Campus ops center	Unplanned loss of supply	Incident report, real-time notification
Security event	Customer security lead	Campus security	Incident detected	Incident log, law enforcement record if applicable
Visitor access issue	Customer access sponsor	Campus security	Access denied or policy violation	Access log, incident note
Carrier access issue	Customer network team	Campus connectivity lead	Carrier request or outage	Carrier ticket, campus access log
Environmental incident	Customer EHS lead	Campus EHS	Release, spill, or regulatory trigger	Incident report, regulatory notification if required
Construction safety issue	Customer site safety officer	Campus EHS	Stop-work event, near miss, or injury	Incident report, corrective action record
Load increase request	Customer commercial contact	Campus commercial team	Any increase above approved profile	Formal request, capacity review
Incident requiring first responders	Customer incident command	Campus incident command	Any life safety or major event	Incident report, first responder record

17. Powered Land Exhibits Checklist

The following project-specific exhibits must be completed, reviewed, and executed before the Powered Land interface is considered defined. This list is a framework reference and is not exhaustive for any specific project.

Parcel exhibit and legal description
Survey and boundary documentation
Access and easement exhibit
Power delivery exhibit
Metering exhibit
Protection coordination requirements
Construction logistics plan
Site safety rules exhibit
Security and access rules exhibit
Fiber / carrier demarcation exhibit
Environmental responsibility matrix
Emergency response coordination exhibit
Commissioning and load release procedure
Operations escalation matrix
Maintenance coordination process
Change management procedure
Restoration and decommissioning obligations

This reference describes a Powered Land interface framework only. Actual parcel rights, easements, utility rights, power delivery obligations, customer construction rights, safety obligations, access rights, maintenance obligations, load release criteria, remedies, and commercial terms must be defined in the applicable project agreements and exhibits.

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.

Related References

Architecture

Campus Architecture Reference

Offering Model

Powered Shell Model Reference

Operations

Operations Boundary Matrix

Safety & Compliance

Safety, Security & Compliance Framework

Back to Reference Index