FprEN 50600-3-1:2026

SLOVENSKI STANDARD
01-december-2024
Informacijska tehnologija - Naprave in infrastruktura podatkovnega centra - 3-1.
del: Informacije o upravljanju in obratovanju
Information technology - Data centre facilities and infrastructures - Part 3-1:
Management and operational information
Informationstechnik - Einrichtungen und Infrastrukturen von Rechenzentren - Teil 3-1:
Informationen für das Management und den Betrieb
Technologie de l'information - Installation et infrastructures de centres de traitement de
données - Partie 3-1: Informations de gestion et de fonctionnement
Ta slovenski standard je istoveten z: prEN 50600-3-1:2024
ICS:
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD DRAFT
prEN 50600-3-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2024
ICS 35.020; 35.110; 35.160 Will supersede EN 50600-3-1:2016
English Version
Information technology - Data centre facilities and infrastructures
- Part 3-1: Management and operational information
Technologie de l'information - Installation et infrastructures Informationstechnik - Einrichtungen und Infrastrukturen von
de centres de traitement de données - Partie 3-1: Rechenzentren - Teil 3-1: Informationen für das
Informations de gestion et de fonctionnement Management und den Betrieb
This draft European Standard is submitted to CENELEC members for enquiry.
Deadline for CENELEC: 2025-01-10.

It has been drawn up by CLC/TC 215.

If this draft becomes a European Standard, CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which
stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CENELEC in three official versions (English, French, German).
A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to
the CEN-CENELEC Management Centre has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to
provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without notice and
shall not be referred to as a European Standard.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Project: 79741 Ref. No. prEN 50600-3-1:2024 E

prEN 50600-3-1:2024 (E)
1 Contents Page
2 European foreword . 6
3 Introduction . 7
4 1 Scope . 10
5 2 Normative references. 10
6 3 Terms, definitions and abbreviations . 10
7 3.1 Terms and definitions . 10
8 3.2 Abbreviations . 12
9 4 Conformance . 13
10 5 Data centre strategy . 14
11 5.1 Purpose . 14
12 5.2 Activities . 15
13 5.2.1 Assess current capabilities . 15
14 5.2.2 Implement processes and KPI . 15
15 5.2.3 Review of the strategy . 15
16 5.2.4 Sourcing strategy . 16
17 5.2.5 Strategy agreement . 16
18 5.3 KPI: Actuality of agreed strategy . 16
19 6 Organization . 16
20 6.1 Purpose . 16
21 6.2 Organizational duties, tasks and responsibilities . 16
22 6.3 Human resources . 16
23 6.4 Organizational Structure . 16
24 6.5 Management of processes . 18
25 6.5.1 Purpose . 18
26 6.5.2 Monitoring and control of Processes . 18
27 7 Data centre management . 19
28 7.1 Purpose . 19
29 7.2 Basic organization and role model . 19
30 7.3 Management Objectives . 20
31 7.3.1 Management duties, tasks and responsibilities . 20
32 7.3.2 Management of Strategies and standards . 20
33 7.3.3 Management of governance and compliance . 21
34 7.3.4 Management of services and service levels . 21
35 7.3.5 Management of processes . 21
36 7.3.6 Management of Key Performance indicators . 21
37 7.3.7 Management of Quality . 21
38 7.3.8 Management of threats and risks . 21
39 7.3.9 Management of data centre continuity . 21
40 7.3.10 Management of sustainability . 22
41 7.3.11 Management of customer obligation . 22
42 7.3.12 Supply management process. 22
43 7.3.13 Management of providers, internal and external resources . 22
44 8 Operational Processes . 23
prEN 50600-3-1:2024 (E)
45 8.1 Operational management process . 23
46 8.1.1 Purpose . 23
47 8.1.2 Activities . 23
48 8.1.3 Setpoint and airflow control . 27
49 8.1.4 Fire compartments . 28
50 8.1.5 Maintenance . 28
51 8.2 Operational information and parameters . 34
52 8.2.1 General . 34
53 8.2.2 Building construction as per EN 50600-2-1 . 34
54 8.2.3 Power distribution as per EN 50600-2-2 . 34
55 8.2.4 Environmental control as per EN 50600-2-3 . 35
56 8.2.5 Telecommunications cabling infrastructure as per EN 50600-2-4 . 36
57 8.2.6 Security systems as per EN 50600-2-5 . 37
58 8.3 Acceptance test . 37
59 8.3.1 General . 37
60 8.3.2 Building construction (EN 50600-2-1) tests . 39
61 8.3.3 Power supply and distribution (EN 50600-2-2) tests . 39
62 8.3.4 Environmental control (EN 50600-2-3) tests . 39
63 8.3.5 Telecommunications cabling infrastructure (EN 50600-2-4) tests . 40
64 8.3.6 Security systems (EN 50600-2-5) tests . 40
65 8.3.7 Energy efficiency tests . 40
66 8.4 Asset and configuration management . 40
67 8.4.1 Purpose . 40
68 8.4.2 Activities . 41
69 8.4.3 KPI for asset and configuration management . 41
70 8.5 Documentation . 41
71 8.5.1 General . 41
72 8.5.2 Design and construction documents . 41
73 8.5.3 Insurance requirement reports . 41
74 8.5.4 Security handbook . 42
75 8.5.5 Building permit . 42
76 8.5.6 Operational handbook . 42
77 8.5.7 Installation handbook . 42
78 8.5.8 Administration manual and software application settings . 42
79 8.5.9 Housekeeping manual . 43
80 8.5.10 Customer information portal . 43
81 8.6 Incident management . 43
82 8.6.1 Purpose . 43
83 8.6.2 Activities . 43
84 8.6.3 KPI for incident management . 43
85 8.7 Problem management . 44
86 8.7.1 Purpose . 44
87 8.7.2 Activities . 44
88 8.7.3 KPI: Ratio of solved problems . 45
89 8.8 Change management . 45
90 8.8.1 Purpose . 45
91 8.8.2 Activities . 45
92 8.8.3 KPI for change management . 46
prEN 50600-3-1:2024 (E)
93 9 Management Processes . 46
94 9.1 Capacity management . 46
95 9.1.1 Purpose . 46
96 9.1.2 Activities . 47
97 9.1.3 KPI: Balance of actual usage and capacity reserve . 48
98 9.2 Availability management . 48
99 9.2.1 Purpose . 48
100 9.2.2 Activities . 48
101 9.2.3 KPI for availability management . 49
102 9.3 Security management . 49
103 9.3.1 Purpose . 49
104 9.3.2 Activities . 50
105 9.3.3 KPI: number of security incidents . 51
106 9.4 Resource management . 51
107 9.4.1 Purpose . 51
108 9.4.2 Activities . 52
109 9.4.3 KPI for resource management . 52
110 9.5 Energy management . 52
111 9.5.1 Purpose . 52
112 9.5.2 Activities . 52
113 9.5.3 KPI for energy management . 53
114 9.6 Product lifecycle management . 54
115 9.6.1 Purpose . 54
116 9.6.2 Activities . 55
117 9.6.3 KPI: Deviation from expected product properties . 55
118 9.7 Cost management . 56
119 9.7.1 Purpose . 56
120 9.7.2 Activities . 56
121 9.7.3 KPI for cost management . 57
122 9.8 Service level management . 57
123 9.8.1 Purpose . 57
124 9.8.2 Activities . 57
125 9.8.3 KPI: Discrepancy between service quality and SLA . 57
126 9.9 Customer management . 58
127 9.9.1 General . 58
128 9.9.2 Purpose . 58
129 9.9.3 Activities . 58
130 9.9.4 KPI for customer management . 59
131 10 Risk management . 59
132 10.1 Purpose . 59
133 10.2 Activities . 59
134 10.2.1 General . 59
135 10.2.2 Risk List . 60
136 10.2.3 Categorization . 61
137 10.3 KPI for risk management . 62
138 10.3.1 Number of open risks . 62
139 10.3.2 Duration from register to completion . 62
140 11 Quality management . 62
prEN 50600-3-1:2024 (E)
141 11.1 Purpose . 62
142 11.2 Activities . 62
143 11.2.1 Quality methodologies . 62
144 11.2.2 Quality plan and objectives . 62
145 11.2.3 Quality assessment . 63
146 11.3 Quality improvement . 63
147 Annex A (informative) Example for process implementation . 64
148 A.1 Prioritization of processes . 64
149 A.2 Maturity . 64
150 Annex B (informative) Security systems . 66
151 B.1 Access to the data centre premises . 66
152 B.1.1 Manned guarding . 66
153 B.1.2 Employees and other authorized personnel . 66
154 B.1.3 Visitors . 67
155 B.1.4 Deliveries . 68
156 B.1.5 Examples for security controls . 69
157 B.2 Fire suppression systems . 70
158 B.3 Management of electrical interference. 70
159 Bibliography . 71
162 Figures
163 Figure 1 — Schematic relationship between the EN 50600 series of documents . 8
164 Figure 2 — Data centre management overview . 9
165 Figure 3 — Example of the elements of data centre strategy . 15
166 Figure 4 — Process organization . 18
167 Figure 5 — Examples for process modelling . 19
168 Figure 6 — Example for a basic model for a data centre management organization . 19
169 Figure 7 — Risk Management process according to ISO 31000 . 60
171 Tables
172 Table 1 — Examples of methodologies and practices . 17
173 Table A.1 — Prioritization of processes . 64
174 Table A.2 — Operational levels . 65
175 Table B.1 — Examples for preventive controls . 69
176 Table B.2 — Examples for detective controls . 69
177 Table B.3 — Examples for predictive controls . 69
178 Table B.4 — Examples for reactive and corrective controls. 70
prEN 50600-3-1:2024 (E)
180 European foreword
181 This document prEN 50600-3-1:2024 has been prepared by CLC/TC 215 “Electrotechnical aspects of
182 telecommunication equipment”.
183 This document is currently submitted to the Enquiry.
184 The following dates are proposed:
• latest date by which the existence of this (doa) dor + 6 months
document has to be announced at national
level
• latest date by which this document has to be (dop) dor + 12 months
implemented at national level by publication of
an identical national standard or by
endorsement
• latest date by which the national standards (dow) dor + 12 months
conflicting with this document have to be (to be confirmed or
withdrawn modified when voting)
185 This document will supersede EN 50600-3-1:2016 and all of its amendments and corrigenda (if any).
186 prEN 50600-3-1:2024 includes the following significant technical changes with respect to
187 EN 50600-3-1:2016:
188 a) the document has been completely revised and restructured;
189 b) new clauses on data centre strategy, organisation, data centre management, risk management and
190 quality management have been added;
191 c) existing clauses on operational information and parameters and on acceptance test have been included
192 in the clause on operational processes.
193 This document has been prepared under a standardization request addressed to CENELEC and ETSI by the
194 European Commission. The Standing Committee of the EFTA States subsequently approves these requests
195 for its Member States.
prEN 50600-3-1:2024 (E)
196 Introduction
197 The unrestricted access to internet-based information demanded by the information society has led to an
198 exponential growth of both internet traffic and the volume of stored/retrieved data. Data centres are housing
199 and supporting the information technology and network telecommunications equipment for data processing,
200 data storage and data transport. They are required both by network operators (delivering those services to
201 customer premises) and by enterprises within those customer premises.
202 Data centres need to provide modular, scalable and flexible facilities and infrastructures to easily
203 accommodate the rapidly changing requirements of the market. In addition, energy consumption of data
204 centres has become critical both from an environmental point of view (reduction of carbon footprint) and with
205 respect to economic considerations (cost of energy) for the data centre operator.
206 The implementation of data centres varies in terms of:
207 a) purpose (enterprise, co-location, co-hosting, or network operator facilities);
208 b) security level;
209 c) physical size;
210 d) accommodation (mobile, temporary and permanent constructions).
211 The needs of data centres also vary in terms of availability of service, the provision of security and the
212 objectives for energy efficiency. These needs and objectives influence the design of data centres in terms of
213 building construction, power distribution, environmental control, telecommunications cabling and physical
214 security as well as the operation of the data centre. Effective management and operational information is
215 required to monitor achievement of the defined needs and objectives.
216 Recognizing the substantial resource consumption, particularly of energy, of larger data centres, it is also
217 important to provide tools for the assessment of that consumption both in terms of overall value and of
218 source mix and to provide Key Performance Indicators (KPIs) to evaluate trends and drive performance
219 improvements.
220 At the time of publication of this document, the EN 50600 series is designed as a framework of standards
221 and other documents covering the design, the operation and management, the key performance indicators
222 for energy efficient operation of the data centre as well as a maturity model for energy management and
223 environmental sustainability.
224 This series of European Standards specifies requirements and recommendations to support the various
225 parties involved in the design, planning, procurement, integration, installation, operation and maintenance of
226 facilities and infrastructures within data centres. These parties include:
227 1) owners, operators, facility managers, IT managers, project managers, main contractors;
228 2) consulting engineers, architects, building designers and builders, system and installation designers,
229 auditors, test and commissioning agents;
230 3) facility and infrastructure integrators, suppliers of equipment;
231 4) installers, maintainers.
232 This document is intended for use by and collaboration between facility managers, ICT managers, and main
233 contractors.
234 The inter-relationship of the documents within the EN 50600 series is shown in Figure 1.
prEN 50600-3-1:2024 (E)
236 Figure 1 — Schematic relationship between the EN 50600 series of documents
237 EN 50600-1 introduces the general concepts relevant for the design and operation of data centres.
238 The EN 50600-2 series of documents define the requirements for the data centre design and specify
239 requirements and recommendations for particular facilities and infrastructures to support the relevant
240 classification for “availability”, “physical security” and “energy efficiency enablement” selected from
241 EN 50600-1.
242 The EN 50600-3 series of documents specify requirements and recommendations for data centre
243 operations, processes and management.
244 The EN 50600-4 series of documents specify requirements and recommendations for key performance
245 indicators (KPIs) used to assess and improve the resource usage efficiency and effectiveness, respectively,
246 of a data centre.
247 CLC/TS 50600-5-1 specifies the maturity model for energy management and environmental sustainability
248 and refers amongst others to EN 50600-4-X KPIs as appropriate.
249 The CLC/TR 50600-99 series of Technical Reports cover guidance for specific topics around data centre
250 operation and design.
251 Secretary note: Verify this sentence during enquiry.
252 This document addresses the operational and management information (in accordance with the
253 requirements of EN 50600-1). A data centre’s primary function typically is to house large quantities of
254 computer and telecommunications hardware which affects the construction, operation, and physical security.
255 Most of the data centres may impose special security requirements. Therefore, it is important that the
256 planning of a data centre by the designer and the various engineering disciplines that will assist in the
257 planning and implementation of the design of the data centre i.e. electrical, mechanical, security, etc. are
258 carried out in cooperation with the IT and telecommunications personnel, network professionals, the facilities
259 manager, the IT end users, and any other personnel involved.
260 Figure 2 shows an overview of the document:
261 • The organization provides the data centre strategy and resources for data centre management and
262 operation.
263 • Data Centre management organizes all process and resources for data centre operation.
prEN 50600-3-1:2024 (E)
264 • Operational information and documentation support all data centre activities.
266 Figure 2 — Data centre management overview
267 The transition from planning and building to operation of a data centre is considered as part of the
268 acceptance test process in 8.3.
269 This series of European Standards does not address the selection of information technology and network
270 telecommunications equipment, software and associated configuration issues.
prEN 50600-3-1:2024 (E)
271 1 Scope
272 This document specifies processes for the management and operation of data centres. The primary focus of
273 this document is the processes necessary to deliver the expected level of resilience, availability, risk
274 management, risk mitigation, capacity planning, security and resource and energy efficiency.
275 The secondary focus is on organization and data centre management to align the actual and future
276 demands. Only processes specific for data centres are in the scope of this document.
277 Business processes like people management, financial management, etc. are out of scope.
278 2 Normative references
279 The following documents are referred to in the text in such a way that some or all of their content constitutes
280 requirements of this document. For dated references, only the edition cited applies. For undated references,
281 the latest edition of the referenced document (including any amendments) applies.
282 EN 50174-1, Information technology — Cabling installation — Part 1: Installation specification and quality
283 assurance
284 EN 50174-2, Information technology — Cabling installation — Part 2: Installation planning and practices
285 inside buildings
286 EN 50600-1:2019, Information technology — Data centre facilities and infrastructures — Part 1: General
287 concepts
288 EN 50600-2 (all parts), Information technology — Data centre facilities and infrastructures
289 EN 50600-2-2:2019, Information technology — Data centre facilities and infrastructures — Part 2-2: Power
290 supply and distribution
291 EN 50600-4 (all parts), Information technology — Data centre facilities and infrastructures
292 CLC/TS 50600-5-1, Information technology — Data centre facilities and infrastructures — Part 5-1: Maturity
293 Model for Energy Management and Environmental Sustainability
294 3 Terms, definitions and abbreviations
295 3.1 Terms and definitions
296 For the purposes of this document, the terms and definitions given in EN 50600-1, the EN 50600-2 series
297 and the following apply.
298 ISO and IEC maintain terminological databases for use in standardization at the following addresses:
299 — IEC Electropedia: available at https://www.electropedia.org/
300 — ISO Online browsing platform: available at https://www.iso.org/obp
301 3.1.1
302 availability management
303 process for monitoring, analysis, reporting and improvement of availability
304 3.1.2
305 capacity management
306 process for monitoring, analysis, reporting and improvement of capacity
prEN 50600-3-1:2024 (E)
307 3.1.3
308 change management
309 process for recording, coordination, approval and monitoring of all changes
310 3.1.4
311 configuration item
312 entity managed by configuration management
313 3.1.5
314 configuration management
315 process for logging and monitoring of configuration items
316 3.1.6
317 cost distribution model
318 model to distribute costs that cannot be directly related to an infrastructure item
319 3.1.7
320 cost management
321 process for monitoring, analysis and reporting of all infrastructure related costs
322 3.1.8
323 customer management
324 process for management of customers responsibilities
325 3.1.9
326 data centre strategy
327 process for alignment of actual data centre’s capabilities and future demands of data centre’s users and
328 owners
329 3.1.10
330 energy management
331 process for monitoring, analysis, reporting and improvement of energy efficiency
332 3.1.11
333 event
334 something that happens and leads to one or more failures or faults
335 [SOURCE: CLC/TS 50600-4-31:2024, 3.1.7]
336 3.1.12
337 incident management
338 process for responding to unplanned events and recovery of normal operation condition
339 3.1.13
340 incident severity
341 incident category according to the four impact categories described in EN 50600-1:2019, 5.3
342 3.1.14
343 key performance indicator
344 parameter used to evaluate performance
345 3.1.15
346 operations management
347 process for infrastructure maintenance, monitoring and event management
348 3.1.16
349 product lifecycle management
350 process for managing the timely renewal of infrastructure components and review of product lifecycle costs
prEN 50600-3-1:2024 (E)
351 3.1.17
352 provisioned capacity
353 capacity of the data centre’s actual installed infrastructure
354 3.1.18
355 resilience
356 ability to withstand and reduce the magnitude and/or duration of disruptive events, including the capability to
357 anticipate, absorb, adapt to, and/or rapidly recover from such an event
358 [SOURCE: IEEE Task Force on Definition and Quantification of Resilience, PES-TR65:2018-04]
359 3.1.19
360 resilience level
361 enumeration of attributes for the determination of resilience aspects of a defined service at a defined
362 operation point (OP)
363 [SOURCE: CLC/TS 50600-4-31:2024, 3.1.26]
364 3.1.20
365 security incident
366 unplanned event resulting in an actual or potential breach of security
367 3.1.21
368 security management
369 process for design and monitoring of security policies, analysis, reporting and improvement of security
370 3.1.22
371 service level management
372 process for monitoring, analysis and reporting of service level compliance
373 3.1.23
374 service level agreement
375 agreement defining the content and quality of the service to be delivered and the timescale in which it is to
376 be delivered
377 3.1.24
378 total capacity
379 maximum capacity the data centre was designed for at full use in terms of e.g. space, power and cooling
380 3.1.25
381 used capacity
382 data centre’s current capacity used by the IT and facility in terms of e.g. space, power and cooling
383 3.2 Abbreviations
384 For the purposes of this document, the abbreviations given in EN 50600-1 and the following apply:
AHU Air Handling Unit
BIM Building Information Management
BMS Building Management System
CAB Change advisory board
CBM Condition-based Maintenance
CFR Cabinet/Frame/Rack
CIP Commissioning Implementation Plan
CRAC Computer Room Air Conditioning (unit)
prEN 50600-3-1:2024 (E)
CRAH Computer Room Air Handler units
CUE Carbon Usage Effectiveness
CER Cooling Efficiency Ratio
DCIM Data Centre Infrastructure Management
EMC Electromagnetic Compatibility
EMS Energy Management System
EOP Emergency Operating Procedure
ERF Energy Re-use Factor
HVAC Heating, Ventilation and Air Conditioning
IRL Issue Resolution Log
ISMS Information Security Management System
IST Integrated Systems Test
IT Information techology
KPI Key Performance Indicator
LOTO Lock Out, Tag Out
MOP Method of Procedure
OLA Operation Level Agreement
PDCA Plan Do Check Act
PCI-DSS Payment Card Industry Data Security Standard
PUE )
Power Usage Effectiveness
pPUE 1)
Partial Power Usage Effectiveness
RACI Responsible, Accountable, Consulted, Informed
RCA Root Cause Analysis
REF Renewable Energy Factor
SCP Site Configuration Procedure
SLA Service Level Agreement
SOC Service Organizations Controls
SOP Standard Operating Procedure
TCO Total Cost of Ownership
WUE Water Usage Effectiveness
385 4 Conformance
386 For a data centre to conform to this European Standard it shall have at least:
387 a) an implemented data centre strategy defined by stated business requirements (see 5.1);
———————
1) It is recognized that the term “efficiency” should be employed for PUE but “effectiveness” provides continuity with earlier market
recognition of the term.
prEN 50600-3-1:2024 (E)
388 b) an implemented data centre management (see Clause 7);
389 c) an implemented set of management policies and procedures covering the following:
390 1) operations management (see 8.1);
391 2) incident management (see 8.6);
392 3) change management (see 8.8);
393 4) capacity management (see 9.1);
394 5) security management (see 9.3);
395 6) resource management (see 9.4);
396 7) customer management (see 9.9);
397 d) an environmental control policy (see 8.2);
398 e) an asset management policy (see 8.4);
399 f) an energy management policy (see 9.5)
400 g) a monitored PUE KPI (see 9.5);
401 h) a lifecycle management policy (see 9.6).
402 5 Data centre strategy
403 5.1 Purpose
404 A data centre strategy shall be defined by the owner and reflect the requirements of the stakeholders. The
405 data centre strategy shall describe the following aspects, but not limited to:
406 a) availability and resilience;
407 b) physical security;
408 c) energy and resource efficiency;
409 d) maintainability;
410 e) governance.
411 At the beginning of the initial planning of a data centre there is a clear idea of the owner about the needs the
412 data centre shall serve and the identified stakeholders that are relevant to the operation. During the long
413 lifetime of a data centre, the needs will change and thus the strategy of operation. Power density, cooling
414 strategy and even the desired level of resilience can change during a data centre’s lifetime due to new
415 technologies in IT and facility. Also the level of desired operational maturity (see Table A.2) can change
416 according to
...