Skip to content
Back to Energy Efficiency
Energy Efficiency

Deep Lake Water Cooling for Buildings: Understand Toronto’s Shared System

Assess deep lake water cooling for buildings through Toronto’s district-energy example, with a network-to-building interface and service-feasibility checklist.

Arshia Jahangiri
3 min

Table of contents

Deep Lake Water Cooling for buildings is a shared-infrastructure option for a building owner to assess with the network operator. Toronto’s system uses the cold resource of Lake Ontario as part of a district system serving buildings in downtown Toronto. It is an example of meeting cooling demand through shared infrastructure rather than installing a separate conventional cooling plant in every connected building.

Enwave's Toronto overview describes the network and examples of hospitals, offices, campuses and residential buildings it serves. Availability depends on the network and building connection; a household cannot assume eligibility because it lives near a lake or in Toronto.

How to understand the heat transfer

Cooling means removing heat from occupied spaces. In a district system, a network and building-side heat-exchange arrangement transfer that heat to the cooling source. This is not the same as pumping untreated lake water through apartment radiators or delivering lake water as a household appliance service.

Enwave's district-energy explanation describes multiple buildings connected to a central energy source and the development of its Toronto system. The actual arrangement includes infrastructure, pumping, controls and building interfaces, so it should not be described as independent of electricity or automatically free of all refrigerants throughout every connected building.

What can change for a building owner?

A district connection may change the need for on-site cooling equipment, mechanical-room space and maintenance responsibilities. Evaluate these as part of a complete service proposal rather than assuming a fixed percentage saving. Enwave identifies Brookfield Place and the TD Centre as examples; those operator accounts are not a guarantee of another property's costs.

Questions before considering a connection

  • Is the building within a feasible service area?
  • What cooling capacity and temperature conditions are offered?
  • What modifications are needed inside the building?
  • Which party owns and maintains each component?
  • How are service charges, peak demand and future changes handled?
  • What redundancy and outage arrangements apply?

Map the network-to-building interface

Interface question Evidence for the building owner
Service availability Operator’s feasibility response and proposed connection route.
Delivered conditions Capacity, temperatures, seasonal requirements and measurement basis.
Building modifications Mechanical, electrical and control scope prepared by the qualified team.
Ownership and service Boundary between operator and owner equipment and maintenance duties.
Reliability Defined outage response, redundancy and service responsibilities.
Cost Connection work and service-charge structure, including relevant demand terms.

Keep the existing building’s cooling requirement and condition in the assessment. A service connection may avoid some equipment work while adding other interfaces and obligations. Request the complete alternative, including any on-site equipment that remains.

Do not assume a cold-water source makes the system off-grid. Pumps, controls and building systems still need a supported operating arrangement. Have the designer explain the actual system boundaries rather than extending an operator’s case example to every component in another building.

Can another city copy it?

A suitable cold-water resource is only one requirement. Demand density, pipe routes, environmental approvals, capital cost and long-term operation also matter. Other district approaches can use different energy sources, but they need their own engineering and business case.

For a condo or building owner, the next step is a feasibility discussion with the operator and qualified designers. The proposal needs to describe the building connection and the service it would actually receive.

Close the feasibility decision with a record

Retain the service proposal, building-side design assumptions, commercial conditions and unresolved questions together. Identify which party must supply the next piece of evidence before a connection decision can be made. A district-energy example is most useful when it clarifies those interfaces, rather than suggesting every building beside a lake can purchase the same result.

Share this article