Information date: 27 October 2026 — In one siting review, a foreign-funded operator compared a western computing hub against Shanghai. The western site offered large-user power reported in the 0.3 to 0.4 yuan per kWh band, long industrial land grants with local incentives and headroom under efficiency rules; Shanghai offered latency and customer proximity but an efficiency ceiling around 1.25 to 1.3 PUE for new large projects. Knowing that statement is not enough for an operating, research or compliance decision. The team must first establish who and what it applies to, how the effect reaches the real process, and which evidence would justify action.
Verified facts and scope
In one siting review, a foreign-funded operator compared a western computing hub against Shanghai. The western site offered large-user power reported in the 0.3 to 0.4 yuan per kWh band, long industrial land grants with local incentives and headroom under efficiency rules; Shanghai offered latency and customer proximity but an efficiency ceiling around 1.25 to 1.3 PUE for new large projects.
Applies to latency-tolerant workloads — batch training, backup, archival, rendering — where the operator can split its footprint. Confirm the latency budget, the province's efficiency and water caps, whether the site qualifies for hub incentives, the land grant term and delivery conditions, and cross-region network capacity and price.
How the effect reaches operations
Power dominates a data centre's operating cost, so a tariff gap compounds over a ten-year horizon and can outweigh a modest land-price difference. Efficiency caps push the other way: a tighter PUE ceiling raises cooling capex and can force liquid cooling, eroding the western advantage where high-density racks cannot be supported locally.
Comparing headline tariffs without transmission, capacity and demand-charge components; assuming hub incentives are contractual before they appear in the land or investment agreement; underweighting latency and cross-region bandwidth cost; and treating an efficiency cap as advisory when it actually gates permitting.
For “Case: A Foreign-Funded Data Centre Chooses a Western Computing Hub Over Shanghai — Power Tariff, PUE Cap and Land Terms Compared”, official rules or published findings, direct evidence from the relevant product or process, and assumptions that remain untested should be recorded separately. A broad source defines the external boundary; it does not replace batch records, protocols, contracts, labels or direct observations.
Decision
If more than roughly 70% of the workload is latency-tolerant, a dual-site split — bulk in the west, edge near Shanghai — usually beats a single eastern build. If the customer base is financial or interactive, stay near Shanghai and buy efficiency through design rather than geography.
Implementation checklist
- Model ten-year power cost at the delivered tariff, not the headline rate.
- Get efficiency and water caps in writing before signing land terms.
- Stress-test the network path and its cost for a split workload.
- Assign one decision owner, one implementation owner and a dated review point for “Case: A Foreign-Funded Data Centre Chooses a Western Computing Hub Over Shanghai — Power Tariff, PUE Cap and Land Terms Compared”.
- For “Case: A Foreign-Funded Data Centre Chooses a Western Computing Hub Over Shanghai — Power Tariff, PUE Cap and Land Terms Compared”, archive the source page, access date, applicable population or entity, and internal evidence both supporting and opposing the current decision.
- When a rule, formulation, supplier, protocol or observed result changes, reopen only the affected question in “Case: A Foreign-Funded Data Centre Chooses a Western Computing Hub Over Shanghai — Power Tariff, PUE Cap and Land Terms Compared”.
Evidence and review
For “Case: A Foreign-Funded Data Centre Chooses a Western Computing Hub Over Shanghai — Power Tariff, PUE Cap and Land Terms Compared”, start with one real case rather than an abstract checklist. Record the input version, responsible owner, start time, observed result and stop condition. If the team cannot complete “Model ten-year power cost at the delivered tariff, not the headline rate.” with current evidence, it should not expand the process to more products, patients, suppliers or markets. The first review should focus only on facts capable of changing the decision.
The second control follows “Get efficiency and water caps in writing before signing land terms.”. Keep the source date, applicable population or entity, deadline, cost effect and owner in the same evidence file. A wording preference does not justify a new version. A repeated discrepancy, an unsupported health claim or a regulatory mismatch does: correct that point and hold release until the evidence is available.
After “Stress-test the network path and its cost for a split workload.”, compare the intended outcome with what actually happened. Apply the same success criteria to each later expansion. If only one number, date or responsibility changes, update that field and the affected conclusion instead of recreating evidence that remains valid. This keeps the decision traceable without turning review into an open-ended rewrite cycle.
Limits of the conclusion
An illustrative case construction, not investment, energy or planning advice. Tariffs, caps and land terms change per province and per project negotiation.
