How It All Works

Plain-language explanations of data centre terms, power, cooling, water, noise, Alberta regulators, project stages, and ADCW evidence labels.

Understanding data centres

Key concepts about data centres and their local impacts.

The basics

What kind of facility is this?

Data centre (data center)

A facility that houses computer systems and the power, cooling and networking equipment needed to operate them.

Hyperscale

A very large data centre designed to grow by adding standardized blocks of computing capacity. For a practical comparison, the International Energy Agency uses 100 MW for a hyperscale data centre and notes that large hyperscale facilities can demand 100 MW or more. These figures are useful reference points, not formal Alberta regulatory thresholds.

AI and high-performance computing (HPC)

Computing workloads that use large numbers of powerful processors at once. They can require much more electricity and cooling than ordinary business computing.

Cryptocurrency mining and ASIC compute

Cryptocurrency mining uses specialized computers to perform repeated calculations that help operate a blockchain network. An application-specific integrated circuit, or ASIC, is hardware built for a narrow computing task; in the facilities ADCW tracks, that task is usually Bitcoin mining.

ADCW does not exclude a facility because its workload is cryptocurrency. Inclusion is based on whether the physical data centre, electricity demand, power infrastructure, water use or other local footprint meets the same evidence and materiality standard applied to AI, colocation and other facilities. The workload is labelled separately and is not treated as AI unless the evidence supports that description.

Colocation

A data centre where multiple customers rent space, power, cooling, and network connections from the facility operator. Think of it as a heavily fortified apartment building for servers.

Cooling and water

What does the cooling claim actually mean?

Waterless cooling

“Waterless” usually means the facility rejects heat without routinely evaporating water in cooling towers. It may use dry coolers or air-cooled chillers, sometimes with sealed liquid cooling at the servers. That can greatly reduce local water consumption, but it does not mean chemical-free or impact-free.

Depending on the design, sealed systems may contain refrigerant, a water-glycol mixture, mineral oil, or another engineered dielectric fluid. Fans, pumps, and compressors still use electricity. A properly contained closed loop should not routinely release these fluids, but refrigerant leaks can add potent greenhouse gases, while coolant spills, servicing, and disposal need proper controls. The exact fluid and environmental tradeoffs cannot be known from the word “waterless” alone.

Closed-loop cooling

Fluid circulates repeatedly through a contained cooling loop. The term describes that loop, not all water use at the site. Heat can pass to a separate system that uses evaporation; filling, servicing, and leaks also matter.

Dry cooling and dry coolers

Heat is released to air without relying on water evaporation. Fans still need power and can produce sound. Some designs combine dry equipment with wet or water-assisted equipment for hot weather, so the complete design matters.

Liquid cooling and direct-to-chip cooling

Liquid carries heat away from computing equipment, including through cold plates at chips. This does not identify the outside heat-rejection system or establish total water use.

Immersion cooling

Equipment is submerged in a fluid designed not to conduct electricity. Fluid management and outside heat rejection remain separate questions.

N+1 mechanical cooling

Mechanical cooling uses powered equipment such as chillers, pumps, fans, or computer-room cooling units to remove heat. “N” is the number of units needed to carry the design load; “+1” means one extra unit is installed so cooling can continue if a unit fails or is being serviced. If three units are required, an N+1 design installs four.

N+1 describes redundancy, not the exact cooling technology, water use, or environmental performance.

Refrigeration ton

A refrigeration ton is a measure of cooling capacity, not the weight of the equipment and not a volume of water. It tells readers how quickly a system can remove heat. It does not reveal whether the system uses cooling towers, dry coolers, refrigerant, or routine water consumption.

Cubic metre (m³) and litre (L)

One cubic metre equals 1,000 litres. ADCW presents the conventional or source unit first, then adds litres in brackets for context. For example: 5,000 m³/day (5 million L/day). The conversion does not change whether a figure is a projection, licence limit or measured use.

Withdrawal, consumption and discharge

Withdrawal is water taken from a source. Consumption is the portion not returned to the same water system, often because it evaporates or becomes part of a product. Discharge is water released after use or treatment. These figures are not interchangeable, and ADCW does not assume a withdrawal volume is entirely consumed.

Environmental and regulatory terms

Area, air, noise and consultation

Hectare (ha) and square kilometre (km²)

One square kilometre equals 100 hectares. When a source reports land in hectares, ADCW leads with square kilometres and preserves hectares in brackets. For example: 3.83 km² (383 ha). Areas originally reported in acres remain in acres.

Modelled versus measured

A modelled result predicts conditions from inputs and assumptions. A measured result records observations under particular conditions. For sound, emissions, or water, check the location, period, and operating scenario before comparing numbers. A prediction of compliance does not verify operating performance.

Air-dispersion modelling

A computer estimate of where air pollution may travel and how much could build up nearby. It uses assumptions about emissions, weather, terrain and how equipment will operate. It predicts possible conditions; it does not measure pollution from an operating site.

Air-quality objective and modelled exceedance

Alberta sets air-quality benchmarks for different pollutants and time periods. A modelled exceedance means a computer estimate went above one of those benchmarks. It is not a reading taken from the air, but it flags a result that should be explained.

NO₂, PM₂.₅ and CO

These are common pollutants checked in air studies. NO₂ is nitrogen dioxide, a gas created when fuel burns. PM₂.₅ means very small particles that can travel deep into the lungs. CO is carbon monoxide, a colourless gas created when fuel does not burn completely. Each can have a different limit depending on how long people are exposed.

dBA

dBA is a way of measuring sound that roughly reflects how loud it seems to the human ear. The scale does not rise evenly: an increase of 10 dBA is generally heard as about twice as loud. A machine's rating, a predicted sound level at a nearby home and the allowed limit are different numbers.

Proposed commitment versus approval condition

A proposed commitment is something a proponent says it intends to do. An approval condition is a requirement imposed by the responsible authority. A commitment should not be described as enforceable until it is included in an approval, agreement or other binding instrument.

Treaty geography and project-specific effects

Treaty boundaries help place a project in its historical and geographic setting. They do not, on their own, tell us which First Nations or Métis communities may be affected, whether consultation occurred, or how a community views a project. ADCW adds those details when they appear in a public record.

Sound and community impact

What about noise?

Noise does not have to be deafening to affect daily life. A steady mechanical hum, tonal whine, low-frequency sound, or repeated generator testing can disturb sleep, interfere with conversation, and make homes and outdoor spaces less comfortable.

The effect depends on the equipment, operating schedule, distance to nearby communities, surrounding background sound, weather, terrain, and mitigation. ADCW therefore reports noise project by project rather than reducing it to a provincial total.

Data centres are not silent buildings

Potential sources include cooling fans, dry coolers, chillers, pumps, transformers, substations, on-site power generation, backup generators, construction, deliveries, and traffic.

Some equipment may operate continuously. Other sources, such as generator testing or equipment cycling, may start and stop. Several sources may also operate at the same time.

One number cannot describe the whole experience

A brief loud event and a lower sound that continues throughout the night can affect people differently. The same overall dBA value can also describe sounds with very different characteristics.

When ADCW publishes a noise value, it identifies whether the number is:

  • A modelled level at a residence or boundary
  • A proponent's operational target
  • An equipment sound rating
  • A regulatory limit
  • A measurement taken after operations began

These values should not be treated as interchangeable.

Tonal and low-frequency noise

Tonal noise contains a noticeable hum, whine, or other distinct pitch. Low-frequency noise has more energy at the lower end of the sound spectrum and may be experienced differently indoors and outdoors.

A sound can therefore be noticeable or disruptive even when its overall dBA value appears modest. Alberta's utility-noise rules include methods for assessing tonal and low-frequency characteristics, but those characteristics are not always summarized in public project materials.

Potential health and community effects

Environmental noise can cause annoyance, interrupt sleep, interfere with conversation and concentration, and affect how people use their homes and outdoor spaces.

The likelihood and severity of an effect depend on the level, duration, timing, sound character, and local setting. A model predicting regulatory compliance does not establish that a project will be inaudible or that nobody will experience disturbance.

How Alberta regulates noise

AUC Rule 012 applies to facilities under the Alberta Utilities Commission's jurisdiction, including regulated power plants and related utility infrastructure. It establishes permissible sound levels, noise-impact-assessment requirements, and a process for investigating complaints.

It does not automatically regulate every sound source at the associated data centre. Cooling equipment, building systems, traffic, construction, and other sources may instead fall under municipal permits, approval conditions, land-use rules, or nuisance bylaws.

A filed noise-impact assessment is still a prediction. Its conclusion depends on the equipment, operating assumptions, receptor locations, background sound, and mitigation used in the model.

Mitigation and monitoring

Possible measures include greater setbacks, acoustic enclosures, silencers, barriers, quieter equipment, fan-speed controls, restrictions on generator testing, receptor monitoring, and a documented complaint-response process.

Mitigation is meaningful only if it addresses the actual sources, is installed and maintained, and is verified after operations begin. ADCW distinguishes between a proposed measure, an enforceable approval condition, and measured operating performance.

How to read a project Noise fieldStart with three questions: What does the number represent? Where does it apply? Is it modelled, targeted, specified, or measured? A regulatory limit, an equipment rating, and a predicted level at someone's home are three different things.

Power, infrastructure & approvals

How data centres connect to Alberta’s electricity system and who regulates them.

Power and scale

MW, GW, load, and generation

Watt (W)

A watt measures the rate at which electricity is being used or produced. It measures power at a point in time, not the total energy used over a day, month, or year.

Megawatt (MW) and gigawatt (GW)

One megawatt is one million watts. One gigawatt is 1,000 megawatts, or one billion watts. On ADCW, always check what the number describes. It may refer to data centre demand, grid connection capacity, on-site generation, or backup generators.

1 MW× 1,0001 GW
Capacity versus energy use

Capacity describes how much power a facility could use or produce at one time. Energy use describes how much it actually uses over a period of time and is measured in units such as megawatt-hours (MWh) or gigawatt-hours (GWh). A 1 GW capacity claim does not prove that a facility will continuously consume 1 GW.

Data centre load versus power generation

Load is the electricity the data centre demands. Generation is electricity produced by a power plant. A project can propose both, and the figures are not interchangeable. ADCW labels them separately.

Interconnection

In electricity records, interconnection is the physical and contractual connection that lets a facility draw power from, or send power to, the grid. It can require transmission or distribution lines, a substation, technical studies, agreements, and regulatory approvals. An interconnection request or study does not by itself approve the data centre or guarantee that the requested capacity will be available. Data centre operators also use “interconnection” for private network links between customers, carriers, and cloud services, which is a separate meaning.

Grid-connected versus non-grid-connected

A grid-connected data centre can exchange electricity with Alberta's interconnected system. On-site generation does not establish that it is off-grid. A non-grid-connected facility has no electrical connection to that system; its supply must be available to the site. Its power plant can still require AUC approval, and local impacts remain relevant.

AUC example of a proposed non-grid-connected power plant

Behind-the-meter generation

Generation supplies electricity on the customer's side of the meter, reducing some or all of the site's grid draw. The facility can still be grid-connected. Behind-the-meter describes the electrical arrangement, not an exemption from approvals or proof of zero grid demand.

AESO distributed energy resources roadmap, printed page 5

Tethered generation / Bring Your Own Generation (BYOG)

Under Alberta's 2026 Data Centre Regulation, AESO can link a large data centre's grid-access request with qualifying generation or storage requests. The resource supports supply to the transmission system. This regulatory pairing does not require an on-site plant or direct wire and is different from behind-the-meter generation.

The regulation's large-data-centre threshold is generally 75 MW of maximum demand directly from transmission; AESO can lower it. A nearby plant or a developer's BYOG claim does not establish formal tethered designation.

Data Centre Regulation, sections 2 and 5

Bridged data centre

Bridging permits conditional grid service before paired supply receives its required grid service. It is temporary, subject to AESO requirements, and can require demand reductions. It does not guarantee unrestricted electricity.

As of September 30, 2026, AESO's latest update, dated September 8, 2026, says the detailed BYOG process is still being finalized, with intake expected in fall 2026. Draft process limits are not settled requirements.

Data Centre Regulation, sections 9 and 10; AESO process update

Backup generation

Generators intended to supply electricity during an outage or other interruption. They are often diesel or natural-gas units. Their combined nameplate capacity does not mean they normally run all the time.

Power usage effectiveness (PUE)

A common efficiency ratio: total facility energy divided by the energy used by computing equipment. A PUE of 1.2 means the facility uses another 0.2 units for cooling, power conversion, lighting, and other support systems for every 1 unit used by the computers. Lower is better, but a projected PUE is still a projection.

Map context

How to read the electricity map layers

The transmission and generation layers add physical-system context to the project map. They do not identify confirmed data centre connections, available supply, or electricity flows.

Schematic transmission line

Each line is drawn straight between the starting and ending network nodes recorded by CODERS. It shows a network relationship, not the exact physical route of towers, poles, or wires. Line colours group the CODERS-reported voltage. Any segment length shown in a popup is also reported by CODERS and should not be read as the length of the straight line on the map.

Network node

A node is a mapped point used to describe where parts of an electricity network connect, change, begin, or end. It is not necessarily a substation, and its coordinates should not be treated as a surveyed equipment location.

Industrial node

CODERS uses this type for a network node associated with a large industrial electricity customer or facility. It does not mean a general industrial district, identify the facility's workload, or prove that a nearby data centre connects there.

Other node types

Generation nodes are associated with electricity production. Distribution nodes connect to a distribution network. Junction, switching, and terminal nodes describe connection, control, or endpoint roles in the network. Intertie nodes connect Alberta's system with another province, territory, or country.

Nearest mapped node

When the transmission layer is on, an ADCW project popup may show the geographically nearest CODERS node to the project's displayed location. This is proximity context only. It does not establish an electrical, contractual, or planned connection.

Power generation facility

The generation layer shows Alberta facilities in the CODERS generator snapshot. ADCW groups multiple generator-unit rows into one facility point and reports the CODERS facility-level installed capacity once. Installed capacity is a nameplate figure, not real-time output, available supply, or proof that electricity can serve a nearby data centre.

Generation facility location

When all CODERS units at a facility share a point, ADCW uses that coordinate. When a facility has several unit coordinates, ADCW maps the centroid of those source points. The popup identifies the facility, but the marker should not be treated as a surveyed equipment location.

Generation snapshot status

CODERS does not provide a separate operating-status field in this response. ADCW labels a facility “Current in CODERS snapshot” when at least one grouped unit has no closure year or a closure year in or after the snapshot year. It is labelled “Closed in CODERS snapshot” only when every grouped unit has an earlier closure year. This is a display rule for the source data, not a new operating-status finding.

Source and licence

Source: Canadian Open-source Database for Energy Research and Systems (CODERS), licensed under CC BY 4.0. ADCW filtered the source data to Alberta, normalized selected fields, created schematic straight-line geometry, and grouped generator units by facility identity. The transmission snapshot was retrieved September 22, 2026; the generation snapshot was retrieved September 22, 2026. CODERS does not endorse ADCW.

Alberta approvals

Who approves what?

Alberta Utilities Commission (AUC)

Alberta's independent utilities regulator. The AUC does not approve the data centre building itself. It reviews regulated utility infrastructure that may support a project, such as power plants, transmission lines, substations, and some natural-gas pipelines.

Alberta Electric System Operator (AESO)

The organization that operates and plans Alberta's interconnected power grid, manages the wholesale electricity market, and handles transmission connection requests. The AESO and AUC have different jobs: the AESO operates and plans the system, while the AUC makes regulatory decisions.

Development permit

A municipal approval that allows a proposed use or development on a specific site, subject to the local land-use bylaw and any conditions. A project may need municipal permits as well as separate provincial or utility approvals.

AUC proceeding

The formal public record used to review an application. It can include the application, information requests, responses, submissions, hearings, and the final decision. A proceeding number helps people find the record in the AUC's eFiling system.

Public consultation versus public hearing

Consultation can happen before or during an application and may be led by a company, municipality, or regulator. A hearing is part of a formal decision process. Attending an open house does not mean a project has been approved, and consultation does not necessarily mean every concern has been resolved.

Reading ADCW

How to interpret project information on our map and in our research.

Project stages

What do the status labels mean?

ADCW uses a short public label on project cards, then gives the exact stage in the status detail. One project can also have different components at different stages.

Announced
A company or government has publicly described the project. A formal application may not exist yet.
Pre-application
Planning, consultation, land work, or early regulatory contact is underway, but a required formal application has not been filed.
Application under review
An authority has received an application and has not made its final decision. This may apply to only one part of the project.
Approved
A required approval has been issued. Other permits may still be needed, and approval does not guarantee construction.
Under construction
Physical construction has been verified. Site clearing or grading alone may be described more precisely in the status detail.
Operating
The facility has entered service. A multi-phase site may be operating at only part of its announced buildout.
Paused
Work or review has been formally put on hold. A pause is not necessarily a cancellation.
Cancelled or refused
The proponent withdrew or cancelled the project, or an approving authority refused it. ADCW keeps these records when they remain relevant to the public history.
Why several stages may appear as "Proposed":The Projects directory uses five simple public labels: Proposed, Approved, Under construction, Operating, and Inactive. "Proposed" can cover an announcement, pre-application work, or an application under review. "Inactive" covers cancelled, withdrawn, or refused proposals that remain relevant to the public history. The status detail tells you the exact stage.

Reading ADCW

Evidence and publication labels

A circled question mark beside a term opens a short explanation where you are reading. It means help, not uncertainty. “Learn more” opens the relevant guide entry; location and source links keep their usual jobs.

Public record
A fact supported by a government, municipal, regulatory, or other official public record.
Proponent statement
Something the company or project proponent says is currently true. The label identifies the speaker and does not turn the claim into independent verification.
Proponent projection
A forecast, target, estimate, or promised future outcome from the project proponent.
ADCW context
ADCW's explanation, comparison, calculation, or identification of a gap based on cited material.
Public records
The total number of project records published in the directory. This includes both evidence profiles and verified listings. It is different from the “Public record” evidence tag, which describes the official source supporting an individual claim.
Evidence profile
A fully reviewed project page with detailed facts, timelines, open questions, and numbered sources.
Verified listing
A shorter public record for a project whose identity, location, status, and source base have been checked, but which does not yet have a full evidence profile.

FAQ

Does "approved" mean the project will definitely be built?

No. An approval permits something to proceed under specified conditions. Financing, contracts, other permits, market conditions, and company decisions can still delay, change, or stop a project.

If the AUC approves a power plant, has it approved the data centre too?

No. The AUC regulates the utility infrastructure within its jurisdiction, not the data centre building itself. Municipal and other approvals may follow separate processes.

Does on-site generation mean a data centre is off-grid?

No. A facility can have its own generators and remain grid-connected. Behind-the-meter generation, non-grid-connected supply, and tethered generation describe different arrangements. Check the project-specific electrical and regulatory records rather than assuming one term means another.

Does a 1 GW project use 1 GW all the time?

Not necessarily. The figure may be a proposed maximum, a full-build target, a grid connection request, or a generation rating. Actual demand can vary and may not be publicly available.

Why can one project have two very different capacity figures?

One number may describe the data centre's electricity demand while another describes an on-site power plant or backup fleet. Figures may also refer to different phases. ADCW labels each number by what it actually measures.

Why does ADCW publish things that are still unknown?

Because missing information is useful information. Keeping a gap visible helps readers distinguish a documented fact from an assumption and gives ADCW something specific to verify later.

Why isn't every rumoured project on the public map?

ADCW publishes a project only after its identity, status, location precision, and source base meet the publication standard. Credible leads can remain in the research ledger until they are ready.

Does ADCW exclude cryptocurrency data centres?

No. ADCW follows the physical infrastructure and public impacts. A large cryptocurrency or ASIC-compute facility can be included when it meets the same evidence and materiality standard as an AI, HPC or colocation project. ADCW identifies the current workload plainly and keeps possible future conversions separate from operating facts.