Water and cooling approvals

Three separations

Write the cooling balance before you choose the approval route: source, annual volume, peak flow, discharge or evaporation, temperature range, chemicals, backup mode and heat-rejection path. If the system uses air, explain what that means for outdoor plant and noise. If it uses water or liquid loops, name the loop boundary and make-up water.

Heat reuse is a second decision. GleSYS documented a start of heat delivery in Falkenberg in 2020. That is evidence of one commercial and technical interface, not proof that a new municipal network can accept your heat or that water abstraction and discharge are permitted.

• Technical concept versus legal permission.
• Design water use versus measured use.
• Heat pipe versus signed heat-sale contract.
• Site water source versus municipal network capacity.
• Normal, peak, dry-year and failure conditions.

Which files may open

Naturvårdsverket’s Environmental Code guidance is the national starting point for the vocabulary. The actual procedure depends on the activity and its dimensions. Water operations, discharge, chemical handling, noise and land impact can involve different questions and authorities. Do not publish a threshold from memory; ask the competent authority with the design figures attached.

The municipal water-and-sewer company, a district-heating company and an environmental authority may all be relevant, but they do different jobs. A commercial heat discussion is not a water permit. A capacity reply from a utility is not an environmental decision. Keep the counterpart and document type visible.

1. Draw the cooling and water boundary.
2. State annual, peak and failure-mode volumes.
3. Name source, discharge/evaporation and temperature.
4. Ask the authority what procedure applies.
5. Separate heat contract from environmental permission.

How to read project examples

Operator descriptions can show that a design or heat interface exists in one project. They do not create a national model. In the register, GleSYS’s dated delivery start, atNorth’s heat-recovery description and EcoDataCenter Falun’s recovery wording remain project-specific observations. None supplies measured annual heat volume for every Swedish site.

If a source is silent about water intake, discharge, consumption or permit status, leave that cell open. “Research incomplete” means the research task is unfinished; “not publicly disclosed” means the public record was checked and did not state it. Use the narrower status.

Draw the cooling balance before choosing a process

A cooling label is not enough to decide what the project must investigate. Write the full balance: heat entering the cooling loop, heat rejected outdoors or to another system, make-up water, discharge or evaporation, temperature range, chemicals, peak conditions and failure mode. State whether the boundary is the server, the building loop, the external plant or the district-heating interface. The same word, such as liquid cooling, can describe different boundaries.

Air cooling, evaporative cooling, chilled-water systems and liquid loops create different questions. Air systems may shift attention toward outdoor plant, fan sound and heat rejection. Evaporative systems require water quality, drift and discharge questions. Liquid loops may reduce water at one boundary while creating a separate heat-exchanger or facility-loop question. Do not call one principle “waterless” without saying which water uses remain outside the claim.

Use annual, peak, dry-year, maintenance and failure cases. A normal average hides the condition that controls a pipe, permit or local network. If the design is not selected, state the alternatives and the decision date. A conceptual diagram is useful for scoping; it is not evidence of actual consumption or legal permission.

• Cooling-loop and heat-rejection boundary.
• Annual, peak, dry-year, maintenance and failure cases.
• Make-up water, discharge, evaporation, chemicals and temperature.
• Design alternative and decision date if the system is not selected.

Separate source, network and legal questions

The water source may be a municipal supply, a private abstraction, a recirculating system, rainwater or another arrangement. Each has a different evidence trail. Ask who owns the source, who can provide the peak flow, what quality is required, what happens during interruption and where used water goes. A utility’s willingness to discuss a connection is not an environmental decision, and a design flow is not a measured allocation.

Discharge, evaporation and treatment should be described separately. State temperature, chemistry, concentration, volume and receiving system where those values are known. Identify whether the proposal requires a sewer connection, surface-water route, water operation or another review. Do not select a legal category from a generic data-center label; give the competent authority and environmental specialist the actual figures.

Local conditions can change the answer. Capacity in a municipal water or sewer network, a protected water environment, seasonal scarcity, neighbouring users and the receiving body all belong in the site file. A national sustainability claim or a cold climate does not prove that a particular plot has water available. Keep the public guide at the level of questions when the project-specific documents are missing.

1. Source owner, peak flow, quality and interruption case.
2. Discharge, evaporation, treatment and receiving system.
3. Municipal utility capacity and project-specific environmental route.
4. Authority and specialist named without guessing a legal classification.

Treat heat reuse as a separate interface

Heat reuse can be technically plausible and still not be delivered. Name the temperature, flow, seasonal profile, heat exchanger, pipe route, customer, operating responsibility and commercial state. The states are different: prepared connection, expression of interest, letter of intent, contract, first delivery and measured delivery. A drawing or operator sentence may support the first two; it does not automatically prove the last four.

The named customer matters. Stockholm Data Parks describes a public initiative with Stockholm Exergi, Ellevio and Stokab. atNorth and Conapto describe heat-reuse relationships toward Stockholm Exergi. GleSYS documented a dated start of delivery to Falkenberg Energi. EcoDataCenter describes recovery with Falu Energi & Vatten. These are project and municipality-specific counterparts, not one national heat buyer or one universal model.

Keep heat and power on separate rows. A heat customer does not provide the electrical connection. A liquid-cooling design does not prove a heat-sale contract. A city objective does not prove annual delivered energy. If a measured volume is not published for the named hall and period, leave it unknown and say what document would close the gap.

• Temperature, flow, seasonal profile, route and heat customer.
• Prepared, intended, contracted, first delivery and measured states.
• Named municipal counterpart and project scope.
• Power connection, cooling design and heat contract kept separate.

Build a reviewable water and cooling record

Keep a single balance sheet for design assumptions and a separate log for measured operation. The design sheet should carry source, annual and peak water, temperatures, chemistry, discharge route, heat customer, equipment and failure cases. The operating log should carry meter identity, period, boundary, calibration or method and any abnormal event. Do not replace a design assumption with an operating result just because a later page repeats the same number.

Version the file when equipment or workload changes. A new high-density rack, a different coolant, a heat-pump interface, a changed sewer route or a larger phase can alter water, energy, noise and environmental questions. Re-check the affected rows and record what did not change. “Cooling unchanged” is not a sufficient audit trail if the heat-rejection boundary moved.

Before a project is described as water-secure or heat-ready, ask for the named source, the utility response, the competent authority’s position, the contract state and the measurement period. If one is missing, use “not yet checked”, “not publicly disclosed” or “not verified” only when the evidence supports that exact phrase. The guide should make the gap actionable, not turn it into a green status.

1. Design balance and measured operating log separated.
2. Boundary, period, method and meter recorded for results.
3. Equipment, workload and route changes trigger a re-check.
4. Water security and heat readiness claims tied to named evidence.