Saudi Arabia / Legislation
Saudi Data-Centre Energy Draft Separates Efficiency Guidance From Mandatory Management
A Saudi consultation draft for data-centre energy efficiency would apply to facilities with a designed IT load of at least 15 megawatts. Listed in the 4 November consultation register, the proposal distinguishes an indicative efficiency target from operational duties; it is not evidence that those proposed duties are already in force.
A proposal with several different clocks
The Saudi Energy Efficiency Center’s text is published on Istitlaa, the official platform for consultation before approval. Bawadir’s register lists publication on 4 November and consultation closing on 3 December 2026; the official draft page records an update on 3 November. The proposed scope begins at 15 megawatts of designed IT load. Its commencement clause would start application 90 days after Official Gazette publication, while an energy-management provision would allow one year from commencement, or from starting operations for a later-opening facility. These are proposed triggers. A consultation listing does not establish that Gazette publication or legal commencement has happened.
For an operator, those distinctions should be recorded before anyone constructs a compliance timetable. Consultation closure, adoption, publication, commencement and an individual facility’s start of operation can be different dates. Converting a draft’s relative period into a calendar deadline without the necessary trigger would create false certainty. The present decision is how to evaluate the proposal and prepare useful comments. Existing obligations under other applicable instruments remain a separate question. This article analyses what the draft would mean if adopted in its present form; it does not describe the consultation text as a new operative licence condition.
An efficiency number is not the whole compliance system
The draft describes a design PUE target of 1.5 at full utilisation as guidance, explicitly saying that missing an indicative target alone would not be a violation. It separately proposes an energy-management system and annual operational reporting. This distinction is the article’s central regulatory point. A target can guide design choices without carrying the same legal function as a duty to measure, manage or report. Conversely, a favourable design estimate would not by itself establish that an operator has implemented the management and reporting processes described elsewhere in the proposed text.
The practical comparison for a project team is between a design claim and an operating evidence trail. A facility may be designed around assumptions about how fully it will be used, while actual occupancy and equipment loading develop over time. Someone reviewing a promotional efficiency figure should ask what period, system boundary and utilisation assumption it represents. These are analytical questions, not additional numerical thresholds invented by this article. They help procurement teams distinguish a comparable measurement from a headline number and determine which records would be needed to explain performance consistently to managers, customers and regulators.
Management options and reporting ownership
The proposal provides different routes for an energy-management system: accredited ISO 50001 certification, the SEEC 50001 Ready programme or an internal system. It also sets out annual data reporting, with a proposed 90-day window after the start of the next calendar year. Facilities regulated by the Communications, Space and Technology Commission would report through that commission, which would share the reports with the energy centre. That arrangement would avoid the direct duplicate submission described in the draft. It does not mean that the facility is excused from maintaining the underlying information or from other applicable regulatory duties.
A useful internal exercise is to trace a hypothetical reporting period from meter readings to a management-approved submission. Identify who controls the measurements, who maintains the facility description and who explains changes in operating conditions. Then identify where records come from external contractors and whether the operator can retrieve them. This exercise can reveal practical gaps without pretending that the proposed report is already due. An outsourced maintenance arrangement, for example, may leave an owner dependent on another business for information. Responsibility for obtaining the records should be understood before it becomes a time-critical reporting problem.
Efficiency changes still have to protect service
The proposed framework connects energy improvements with assessment of safety, security, reliability and service commitments. The significance for a technical team is that an efficiency intervention should be evaluated as an operational change. A setting that saves energy on paper may have consequences during unusual operating conditions, maintenance or a failure elsewhere in the system. A credible change proposal therefore explains the expected saving, the assumptions behind it and how service risks would be checked. This is an operational reading of the draft’s balance; it is not a claim that a particular cooling design or equipment purchase has received regulatory approval.
Consultation comments will be more useful when tied to identifiable implementation problems. An operator can explain where a term needs clarification, show how a proposed reporting boundary interacts with an actual facility arrangement, or identify why a transition period may be difficult for a particular class of site. Suppliers can distinguish technical evidence from sales claims, and customers can ask how reporting would illuminate the service they buy. The next material legal development would be a final approved text and its publication history. Until that is established, the draft should remain labelled as a proposal with conditional future timelines. Gabriel Nicolaev – CyGuru
Gabriel Nicolaev – CyGuru