Energy overhead. Made visible.
From meter exports to a controlled PUE dataset.
Transform BMS, DCIM, utility and spreadsheet sources while preserving measurement boundaries, units, periods and data quality.
Collect meter registers, transformer readings, IT switchboard readings and target definitions. Add cooling readings only when dedicated meters are available.
Use controlled prompts. Never invent readings or silently convert kW to kWh.
Check meter IDs, units, periods, parent-child overlaps, missing readings and IT energy greater than facility energy.
Create related METER, READING, BOUNDARY and TARGET tables with Meter_ID as the stable business key.
// QUICK START
1. Download the master template. 2. Complete METERS. 3. Define BOUNDARIES. 4. Add READINGS. 5. Define TARGETS. 6. Import the workbook. 7. Review the PUE Calculator.
// WHAT PUE MEASURES
PUE is Total Facility Energy divided by IT Equipment Energy. PUEscope uses energy in kWh for the selected period.
// INFRASTRUCTURE OVERHEAD
Infrastructure Overhead is Total Facility Energy minus IT Equipment Energy. It can include cooling, pumps, fans, electrical distribution losses, transformers, UPS losses, lighting, security and auxiliary services, depending on the measurement boundary. Infrastructure Overhead is not automatically waste. Part of it is necessary to operate the Data Center.
// HOW TO COMPLETE METERS
Register general transformers or utility meters as TOTAL_FACILITY. Register IT-only switchboards, PDUs or UPS outputs as IT_ENERGY. Cooling meters are optional. Register dedicated cooling meters as COOLING only when a breakdown of Infrastructure Overhead is available. Keep Meter_ID unique and use kWh as the energy unit.
// HOW TO COMPLETE READINGS
Use one row per meter and period. Keep the same start and end dates across meters used in one calculation. Do not mix daily and monthly data. Do not convert kW to kWh without a known duration. Mark estimates as ESTIMATED and uncertain data as REVIEW.
// HOW TO COMPLETE BOUNDARIES
Assign required PUE meters to TOTAL_FACILITY or IT_ENERGY. COOLING is optional and is used only to explain part of Infrastructure Overhead. Do not include a parent meter together with child meters that represent the same energy flow.
// OPTIONAL COOLING BREAKDOWN
Dedicated cooling readings are not required to calculate PUE. When available, PUEscope can show Known Cooling Energy and Other Infrastructure as an optional explanation of Infrastructure Overhead. If cooling meters do not exist, PUEscope keeps the overhead total without estimating its composition.
// DATA STATUS
Complete means all required Total Facility and IT Energy readings exist for the period. Incomplete means at least one required reading is missing. Review means the calculation includes ESTIMATED or REVIEW readings. No Data means there is not enough information to calculate PUE.
// MONTHLY AND ANNUAL REPORTING
Monthly PUE is monthly Total Facility Energy divided by monthly IT Energy. Annual PUE is the sum of annual Total Facility Energy divided by the sum of annual IT Energy. Do not calculate annual PUE as a simple average of monthly PUE values.
// SCENARIOS
Scenarios are estimates, not measured results. They show the Infrastructure Overhead reduction required to reach a target PUE and the estimated PUE after reducing overhead.
// ONLINE DATABASE
The workbook is a staging source. Move METER, READING, BOUNDARY and TARGET into related online tables for multi-user operation.