Start here
What makes a heat customer worth investigating?
A promising match has an identifiable heat use, compatible temperature requirements, overlapping hours of supply and demand, and a feasible connection with named owners. Establish those conditions together. Recoverable heat is the potential at a stated boundary; heat actually used is the quantity accepted by a customer over time. A large annual heat total alone does not establish the second quantity.
Start with a named use and someone who can confirm it
Replace “nearby buildings” in the project brief with a specific prospective customer and use. That could be a building heating system or an industrial process, but the customer must provide the requirements. A map pin does not tell you its heating schedule, receiving temperature or willingness to participate. Record who controls the receiving system and who can release its demand information.
Open Compute Project's heat-reuse reference designs distinguish stakeholders across the data center, recovery station, transmission and delivery station. The paper also addresses seasonal and daily demand variation. Use those distinctions to organize an initial conversation; they do not establish that a particular connection is feasible.
At a leased NYC or Northern New Jersey property, the prospective customer and the owner of the connecting space may be different parties. Put both contacts in the brief. An interested tenant cannot by itself resolve an interbuilding route, shared mechanical-space access or the owner's project decision.
References: [1]
Ask both parties for comparable evidence
Use the same units, periods and boundary descriptions on both sides. Mark measured information, estimates and future projections separately. If a source figure represents full future IT occupancy while the customer's figure represents last year's actual operation, preserve that difference instead of presenting them as a matched pair.
A temperature request needs a location. “Warm water available” is incomplete without identifying where the figure applies and what conditions produced it. Likewise, a customer's equipment nameplate does not establish its hourly demand. Ask the respective technical reviewers which records can support the proposed comparison.
| Question | Data-center evidence | Customer evidence | Decision it supports |
|---|---|---|---|
| Temperature match | Supply/return records at the proposed recovery boundary | Required receiving temperatures and conditions | Whether direct transfer or further design investigation is relevant |
| Quantity and timing | Available duty with timestamps and occupancy basis | Demand profile over the same periods | How much overlap merits detailed study |
| Physical connection | Proposed boundary and available drawings | Receiving location and route constraints | Who must investigate the connecting works |
| Evidence ownership | Data owner and technical reviewer | Demand owner and approving contact | Who can resolve the next missing fact |
Worked example: a winter match leaves a summer gap
Assume a fictional source offers 800 kW of recoverable thermal duty for two simplified periods of 1,000 hours each. A fictional customer needs 600 kW during the first period and 100 kW during the second. For this arithmetic only, assume the temperatures match, supply and demand coincide throughout each period, and transfer losses and auxiliary energy are excluded. These are invented planning values, not an Airplex project.
The source offers 1,600 MWh across those periods: 800 kW × 2,000 hours ÷ 1,000. The coincident customer demand is only 700 MWh: 600 MWh plus 100 MWh. Thus even this simplified comparison leaves 900 MWh without a customer. Calling all 1,600 MWh “heat reused” would overstate what the example supports.
The 700 MWh is still a theoretical overlap, not measured use. The next study must address temperature variation, transfer arrangements and actual availability. If either period contains shutdowns or different hourly profiles, split it into smaller intervals. Do not multiply the winter demand across the whole year or treat this two-period example as an annual forecast.
| Period | Source available | Customer demand | Maximum coincident overlap | Unmatched source heat |
|---|---|---|---|---|
| Winter-like: 1,000 h | 800 MWh | 600 MWh | 600 MWh | 200 MWh |
| Summer-like: 1,000 h | 800 MWh | 100 MWh | 100 MWh | 700 MWh |
| These two periods only | 1,600 MWh | 700 MWh | 700 MWh | 900 MWh |
Define where delivery becomes an accountable quantity
OCP discusses recording temperatures to and from the reuse system and flow, with reporting requirements depending on the application and stakeholders. Agree a measurement boundary before turning potential recovery into a claimed delivery quantity. Keep any metered delivery separate from the customer's own evidence of useful consumption.
For the initial sheet, ask who owns the meters, who receives the records, what period a report covers and how missing data will be identified. These are questions for the parties developing the project, not a meter specification. Record the document that will resolve each one.
Also request a description of the site's heat-rejection arrangement when the customer cannot receive heat, and the customer's heating arrangement when the source is unavailable. The responsible designers must assess those conditions. A useful customer match does not authorize removing existing cooling equipment or treating the customer's demand as a guaranteed cooling service.
References: [1]
Use the sheet to decide the next study
Conclude the first review with a specific decision: request a missing demand record, investigate the connecting route, obtain a temperature-matching assessment, or pause this customer pairing. Attach an owner and evidence requirement. A pause can be the correct result when a customer cannot substantiate its demand.
Only a developed project basis can support economic or emissions analysis. That later work needs the actual equipment and auxiliary energy, capital and operating assumptions, delivery arrangements and comparison basis. This matching sheet supplies no payback period, energy-price assumption or carbon benefit. Its value is identifying a credible pair and the question that must be answered next.
Put this guide to work
Heat source and customer match sheet
Complete both sides of each row for one proposed customer. Use consistent units and time periods. Add document names, dates and a named reviewer; leave unsupported values blank. This sheet is separate from the fictional example above.
Open each item to add your notes, then download the CSV to keep a copy. This tool does not save or submit your entries; do not rely on your browser restoring them.
Identity / heat use / system boundary
Supply and return temperatures / units
Available or required duty / units
Seasonal demand and source profile
Hourly profile / shutdown periods
Route distance / location / access
Metering and useful-use evidence boundary
Unavailability / alternative arrangement
Continue with a related decision
Questions & answers
Is the nearest building necessarily the best heat customer?
No. Proximity helps define a route question, but it says little about temperatures, timing or demand. Compare the proposed use and evidence before assuming that a short connection creates a good match. An adjacent building with seasonal demand may leave much of the source heat unused.
Can a heat pump solve a temperature mismatch?
It may be a design option for the responsible engineers to investigate. The matching sheet should record the mismatch and the proposed receiving duty first. Adding equipment introduces another scope and energy requirement; it does not by itself establish a suitable project or a financial result.
Does an available-megawatt figure show annual heat reuse?
No. Megawatts describe a rate at a stated condition. An energy quantity also needs time, and reuse needs a customer accepting that heat. Retain the underlying profiles and distinguish a predicted overlap from measured delivery and useful consumption.
Sources & technical references
- OCP: Reference Designs for Data Center Heat Reuse, revision 1.0
Reviewed November 16, 2026: stakeholder boundaries (page 9), measurement/reporting (page 26), and demand matching (pages 32–33). Cover updated March 3, 2025; revision history first publication March 6, 2025. Planning guidance, not a site feasibility result.
NYC & Northern New Jersey
Bring a defined heat-reuse question
Airplex Mechanical's in-house Critical Cooling Division can discuss the liquid-cooling and mechanical interface for an NYC or Northern New Jersey project. Share the proposed source, customer and unresolved interface; engineering, metering and commercial commitments need a defined project scope.
Discuss the mechanical interfaceCall (347) 627-7146