CUSTOMER RESOURCE | DATA-CENTRE ENERGY STRATEGY

Data-centre power & reporting readiness checklist

Use this checklist before committing to a site, connection strategy or reporting workstream. Record what is documented, what remains an assumption and who will close each gap.

Download checklist PDF

Updated 16 October 2026 · Free download, no registration.

For each item, mark documented / needs review / missing. Keep the source, date, responsible person and next action. A public grid dataset can support screening; it cannot establish your connection rights.

01 Define the decision

What decision must be made, by when, and by whom? Compare sites, connection options or upgrades against the same commissioning target.
Record the facility boundary: installed IT power, total facility load, grid import/export capacity and planned expansion. These are different quantities.

02 Establish the route to power

Obtain the connection offer or documented status: capacity, expected date, validity, milestones, costs, dependencies and required works.
Compare firm and flexible options. Identify curtailment limits, notice periods, controllable loads, non-delivery consequences and any contractual compensation.
Test time-to-revenue against the downside of restricted operation. Keep an offered date separate from a verified, deliverable schedule.

03 Test the energy configuration

Compare BESS, generation and operational flexibility using a consistent baseline: capex, energy costs, operating costs, replacement needs and timing.
Model constraints before stacking revenues: power and energy limits, losses, degradation, reserves and availability obligations.
Quantify only supportable cash flows. Keep grid benefits and resilience outcomes visible without counting them as revenue unless a mechanism pays for them.

04 Prepare facility evidence

Map electricity, cooling, water, heat reuse and generation data to meters, owners and reporting periods. Record estimates and gaps.
For PUE (Power Usage Effectiveness) and WUE (Water Usage Effectiveness), confirm definitions, units, facility boundaries and time coverage before comparison. Record the treatment of shared infrastructure.
Separate current reporting requirements from future label readiness. Confirm applicable rules, thresholds and submission responsibilities for the facility and jurisdiction.

05 Review resilience and external dependencies

Map grid dependencies, physical and climate exposures, backup autonomy, redundancy and recovery assumptions. Include water and telecom dependencies.
Check whether dispatch flexibility can coexist with critical-load protection. Identify engineering validation, operational tests and partner expertise required.

06 Agree the next step

Create a short gap register: evidence missing, materiality to the decision, responsible person, cost and deadline to resolve.
Agree a software pilot: scenarios, data access, interfaces, report outputs, acceptance criteria and review checkpoints. Your appointed specialists validate the engineering inputs.

From checklist to software pilot

What a configured software pilot adds: your private project data, tailored scenarios, explicit assumptions and exportable report outputs with supporting data. xIntegra supports software configuration and data integration; your technical specialists validate the engineering inputs. Scope and acceptance criteria are agreed before work starts.

This checklist prepares a commercial and technical discussion. It does not issue an official label, establish eligibility, or guarantee grid access, permits or financing.

Make it specific to your project.

Tell us the decision, asset and timeline. We will agree the data needed, scope and deliverables.

Explore a data-centre pilot Explore data-centre energy strategy