prEN 50463-3:2025

SLOVENSKI STANDARD
01-december-2025
Železniške naprave - Merjenje energije na vlaku - 3. del: Ravnanje s podatki
Railway applications - Energy measurement on board trains - Part 3: Data handling
Bahnanwendungen - Energiemessung auf Bahnfahrzeugen - Teil 3: Datenverarbeitung
Applications ferroviaires - Mesure d'énergie à bord des trains - Partie 3 : Traitement des
données
Ta slovenski standard je istoveten z: prEN 50463-3:2025
ICS:
45.060.10 Vlečna vozila Tractive stock
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD DRAFT
prEN 50463-3
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2025
ICS 45.060.10 Will supersede EN 50463-3:2017; EN 50463-
3:2017/A1:2024
English Version
Railway applications - Energy measurement on board trains -
Part 3: Data handling
Applications ferroviaires - Mesure d'énergie à bord des Bahnanwendungen - Energiemessung auf Bahnfahrzeugen
trains - Partie 3 : Traitement des données - Teil 3: Datenverarbeitung
This draft European Standard is submitted to CENELEC members for enquiry.
Deadline for CENELEC: 2026-01-23.

It has been drawn up by CLC/TC 9X.

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
© 2025 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Project: 81038 Ref. No. prEN 50463-3:2025 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 . 11
7 3.1 Terms and definitions . 11
8 3.2 Abbreviations . 11
9 4 Requirements . 11
10 4.1 General . 11
11 4.2 Time data . 11
12 4.2.1 Source . 11
13 4.2.2 Reference time source . 11
14 4.2.3 Content . 11
15 4.2.4 Resolution . 12
16 4.2.5 Stability . 12
17 4.2.6 Synchronization . 12
18 4.2.7 Quality code for time data . 12
19 4.3 Energy data . 12
20 4.3.1 Source . 12
21 4.3.2 Type . 13
22 4.3.3 Format . 13
23 4.3.4 Index value overrun . 13
24 4.3.5 Merging with time data . 13
25 4.3.6 Quality codes for energy data . 13
26 4.3.7 k-factor . 14
27 4.3.8 Accuracy . 14
28 4.3.9 Transmission from EMF . 14
29 4.4 Location data . 14
30 4.4.1 Source . 14
31 4.4.2 Format . 15
32 4.4.3 Merging with time data . 15
33 4.4.4 Accuracy . 15
34 4.4.5 Quality codes for location data . 15
35 4.5 Other received or produced data . 16
36 4.5.1 Types . 16
37 4.5.2 Data handling prioritization . 16
38 4.5.3 Time tag . 16
39 4.6 Consumption point ID (CPID) . 16
40 4.7 Production of CEBD . 16
41 4.7.1 General . 16
42 4.7.2 Type of Data . 16
43 4.7.3 Time reference period . 17
44 4.7.4 Energy data . 17
45 4.7.5 Location data . 17
46 4.7.6 Missing input data. 17
47 4.7.7 Data integrity . 18
48 4.7.8 Quality codes . 18
49 4.7.9 Electric traction power supply system code . 18
50 4.8 DHS data storage . 18
51 4.8.1 Storage periods . 18
52 4.8.2 Memory Capacity . 19
53 4.9 Transmission of CEBD from DHS to DCS . 19
54 4.9.1 General . 19
55 4.9.2 Type of info . 19
56 4.9.3 Time between each transfer . 19
57 4.9.4 Binding to a DCS . 19
58 4.10 Marking and essential information. 19
59 4.10.1 Marking of the DHS . 19
60 4.10.2 Essential information. 20
61 4.11 Event recording . 20
62 4.11.1 General . 20
63 4.11.2 Type of events . 20
64 4.12 DCS . 21
65 4.12.1 General . 21
66 4.12.2 Reception of CEBD from DHS . 21
67 4.12.3 Request to DHS for CEBD data . 21
68 4.12.4 Storage of CEBD . 21
69 4.12.5 Export of CEBD from DCS . 21
70 4.12.6 Binding the communication with the EMS . 21
71 4.12.7 EMS discovery . 21
72 5 Conformity assessment . 22
73 5.1 General . 22
74 5.1.1 Introduction . 22
75 5.1.2 Applicability . 22
76 5.1.3 Methodology . 22
77 5.2 Testing framework . 23
78 5.2.1 General . 23
79 5.2.2 Reporting . 23
80 5.3 Design review . 24
81 5.3.1 General . 24
82 5.3.2 Interfaces . 24
83 5.3.3 Access control . 24
84 5.3.4 Software . 24
85 5.3.5 RAMS . 24
86 5.3.6 Internal clock . 24
87 5.3.7 Location data source . 24
88 5.3.8 DHS priorities . 24
89 5.3.9 Transmission of CEBD to DCS . 25
90 5.3.10 Dataflow security . 25
91 5.3.11 Event logs . 25
92 5.4 Type testing . 25
93 5.4.1 General . 25
94 5.4.2 Visual inspection . 25
95 5.4.3 Environmental testing . 25
96 5.4.4 Mechanical testing . 26
97 5.4.5 Electrical testing . 27
98 5.4.6 Access control . 28
99 5.4.7 Interfaces . 28
100 5.4.8 Functional testing . 28
101 5.5 Routine testing . 34
102 5.5.1 General . 34
103 5.5.2 Visual inspection . 34
104 5.5.3 Check of marking . 34
105 5.5.4 Functional testing . 34
106 5.5.5 Insulation test . 34
107 5.6 DCS conformity assessment . 34
108 5.6.1 General . 34
109 5.6.2 Design review . 34
110 5.6.3 Functional Testing . 34
111 Annex ZZ (informative) Relationship between this European Standard and the Essential
112 Requirements of Directive 2016/797/EU aimed to be covered . 36
113 Bibliography . 37
115 Figures
116 Figure 1 — EMS functional structure and dataflow diagram .9
118 Tables
119 Table 1 — Time data quality codes . 12
120 Table 2 — Energy data quality codes . 14
121 Table 3 — Location data format . 15
122 Table 4 — Location data quality codes . 15
123 Table 5 — Electric traction power supply system codes . 18
124 Table ZZ.1 — Correspondence between this European Standard, Commission Regulation (EU) N°
125 1302/2014 concerning the Technical Specification for Interoperability relating to the ‘rolling stock
126 — locomotives and passenger rolling stock’ subsystem of the rail system in the European Union*
127 and Directive (EU) 2016/797 . 36
129 European foreword
130 This document (prEN 50463-3:2025) has been prepared by CLC/TC 9X “Electrical and electronic
131 applications for railways”.
132 The following dates are proposed:
— latest date by which the existence of this (doa) dav + 6 months
document has to be announced at national
level
— latest date by which this document has to be (dop) dav + 12 months
implemented at national level by publication of
an identical national standard or by
endorsement
— latest date by which the national standards (dow) dav + 36 months
conflicting with this document have to be (to be confirmed or
withdrawn modified when voting)
133 This document will supersede EN 50463-3:2017 and all of its amendments and corrigenda (if any).
134 prEN 50463-3:2025 includes the following significant technical changes with respect to EN 50463-3:2017:
135 — introduced optional elements regarding hybid energy and use of different types of energy sources;
136 — extended the table of electric traction system power supply system codes to include all codes referred
137 in IEC 62888.
138 This document has been prepared under a standardization request addressed to CENELEC by the
139 European Commission. The Standing Committee of the EFTA States subsequently approves these
140 requests for its Member States.
141 For the relationship with EU Legislation, see informative Annex ZZ, which is an integral part of this
142 document.
143 This document is Part 3 of EN 50463 series which consists of the following parts, under the common title
144 Railway applications — Energy measurement on board trains:
145 — Part 1: General;
146 — Part 2: Energy measuring;
147 — Part 3: Data handling;
148 — Part 4: Communication;
149 — Part 5: Conformity assessment.
150 This series of European Standards follows the functional guidelines description in EN ISO/IEC 17000:2004,
151 Annex A “Principles of conformity assessment”, tailored to the energy measurement system (EMS).
152 Introduction
153 The energy measurement system (EMS) provides measurement and data suitable for billing and may also
154 be used for energy management, e.g. energy saving.
155 This series of European Standards uses the functional approach to describe the EMS and on-ground data
156 collecting system (DCS). These functions are implemented in one or more physical devices. The user of
157 this Series of standards is free to choose the physical implementation arrangements.
158 a) Structure and main contents of EN 50463 series:
159 This series of European Standards is divided into five parts. The titles and brief descriptions of each
160 part are given below:
161 1) EN 50463-1 — General:
162 The scope of EN 50463-1 is the energy measurement system (EMS).
163 EN 50463-1 provides system level requirements for the complete EMS and common
164 requirements for all devices implementing one or more functions of the EMS.
165 2) EN 50463-2 — Energy measuring:
166 The scope of EN 50463-2 is the energy measurement function (EMF).
167 The EMF provides measurement of the consumed and regenerated active energy of a railway
168 traction unit. If the traction unit is designed for use on AC electric traction power supply systems
169 the EMF also provides measurement of reactive energy. The EMF provides the measured
170 quantities via an interface to the data handling system.
171 The EMF consists of the three functions: voltage measurement function, current measurement
172 function and energy calculation function. For each of these functions, accuracy classes are
173 specified and associated reference conditions are defined. EN 50463-2 also defines all specific
174 requirements for all functions of the EMF.
175 The voltage measurement function measures the voltage of the contact line (CL) system and the
176 current measurement function measures the current taken from and returned to the CL system.
177 These functions provide signal inputs to the energy calculation function.
178 The energy calculation function inputs the signals from the current and voltage measurement
179 functions and calculates a set of values representing the consumed and regenerated energies.
180 These values are transferred to the data handling system and are used in the creation of
181 compiled energy billing data (CEBD).
182 The standard has been developed taking into account that in some applications the EMF is
183 subjected to legal metrological control. All relevant metrological aspects are covered in
184 EN 50463-2.
185 EN 50463-2 also defines the conformity assessment of the EMF and the functions of the EMF.
186 3) EN 50463-3 — Data handling:
187 The scope of EN 50463-3 is the data handling system (DHS) and the associated requirements of
188 data collecting system (DCS).
189 The on board DHS receives, produces and stores data, ready for transmission to any authorized
190 receiver of data onboard or on ground. The main goal of the DHS is to produce compiled energy
191 billing data (CEBD) and transfer it to an on ground data collecting system (DCS). The DHS can
192 support other functions on board or on ground with data, as long as this does not conflict with
193 the main goal.
194 The DCS on ground receives CEBD, stores the CEBD and transfer it to upstream servers such
195 as settlement system.
196 EN 50463-3 also defines the conformity assessment of the DHS and for the transfer of CEBD to
197 an on-ground DCS.
198 4) EN 50463-4 — Communication:
199 The scope of EN 50463-4 is the communication services.
200 EN 50463-4 gives requirements and guidance regarding the data communication between the
201 functions implemented within EMS as well as between such functions and other on board units
202 where data are exchanged using a communications protocol stack over a dedicated physical
203 interface or a shared network.
204 It includes the board to ground communication service and covers the requirements necessary
205 to support data transfer between DHS and DCS.
206 EN 50463-4 also defines the conformity assessment of the communications services.
207 5) EN 50463-5 — Conformity assessment:
208 The scope of EN 50463-5 is the conformity assessment procedures for the EMS.
209 EN 50463-5 also covers re-verification procedures and conformity assessment in the event of
210 the replacement of a device of the EMS.
211 b) EMS functional structure and dataflow:
212 Figure 1 illustrates the functional structure of the EMS, the relevant operating dataflow and is
213 informative only. Only the main interfaces required by this EN 50463 series are displayed by arrows.
214 Since the communication function is distributed throughout the EMS, it has been widely omitted for
215 clarity, except for the train to ground communication. Not all interfaces are shown.
217 Figure 1 — EMS functional structure and dataflow diagram
218 1 Scope
219 This part of the EN 50463 series covers the requirements applicable to the data handling system (DHS) of
220 an energy measurement system (EMS).
221 This document also includes the basic requirements for the data collecting system (DCS) on-ground,
222 relating to the acquisition and storage and export of compiled energy billing data (CEBD).
223 The conformity assessment arrangements for the DHS and the DCS are specified in this document.
224 The settlement system is outside the scope of this document, and the specification of the interface between
225 DCS and settlement system is outside the scope of this document.
226 2 Normative references
227 The following documents are referred to in the text in such a way that some or all of their content constitutes
228 requirements of this document. For dated references, only the edition cited applies. For undated references,
229 the latest edition of the referenced document (including any amendments) applies.
230 EN 45545-2:2020+A1:2023, Railway applications - Fire protection on railway vehicles - Part 2:
231 Requirements for fire behaviour of materials and components
232 EN 45545-5:2013+A1:2015, Railway applications - Fire protection on railway vehicles - Part 5: Fire safety
233 requirements for electrical equipment including that of trolley buses, track guided buses and magnetic
234 levitation vehicles
235 EN 50121-3-2:2016, Railway applications – Electromagnetic compatibility – Part 3-2: Rolling stock –
236 Apparatus
237 EN 50155:2021, Railway applications - Rolling stock - Electronic equipment
238 prEN 50463-1:2025, Railway applications - Energy measurement on board trains - Part 1: General
239 prEN 50463-4:2025, Railway applications — Energy measurement on board trains — Part 4:
240 Communication
241 EN 60529:1991, Degrees of protection provided by enclosures (IP Code) (IEC 60529:1989)
242 EN 61373:2010, Railway applications — Rolling stock equipment — Shock and vibration tests
243 (IEC 61373:2010)
244 World Geodetic System, revision WGS 84 (G2139)
———————
As impacted by EN 50121-3-2:2016/A1:2019.
As impacted by EN 60529:1991/corrigendum May:1993, EN 60529:1991/A1:2000, EN 60529:1991/A2:2013,
EN 60529:1991/A2:2013/AC:2019-02, and EN 60529:1991/AC:2016-12.
As impacted by EN 61373:2010/AC:2017-09.
245 3 Terms, definitions and abbreviations
246 3.1 Terms and definitions
247 For the purposes of this document, the terms and definitions given in prEN 50463-1:2025 and the following
248 apply.
249 ISO and IEC maintain terminology databases for use in standardization at the following addresses:
250 — ISO Online browsing platform: available at https://www.iso.org/obp
251 — IEC Electropedia: available at http://www.electropedia.org
252 NOTE When possible, the following definitions have been taken from the relevant chapters of the International
253 Electrotechnical Vocabulary (IEV), IEC 60050-311, IEC 60050-312, IEC 60050-313, IEC 60050-314, IEC 60050-321
254 and IEC 60050-811. In such cases, the appropriate IEV reference is given. Certain new definitions or modifications of
255 IEV definitions have been added in this document in order to facilitate understanding. Expression of the performance
256 of electrical and electronic measuring equipment has been taken from EN 60359.
257 3.1.1
258 location data
259 data describing the geographical position of the traction unit
260 3.1.2
261 log
262 list or set of lists of recorded events
263 3.1.3
264 time data
265 data describing a time and date of a defined time source
266 3.2 Abbreviations
267 For the purposes of this document, the abbreviations given in prEN 50463-1:2025 apply.
268 4 Requirements
269 4.1 General
270 The requirements in prEN 50463-1:2025, Clause 4 apply to any device containing one or more functions of
271 the DHS where applicable. This document defines additional requirements specific to the DHS and basic
272 requirements for the DCS.
273 The DHS shall comply with all subclauses of 4.1 except for 4.12.
274 The DCS shall comply with the requirements in 4.12 only.
275 4.2 Time data
276 4.2.1 Source
277 The DHS shall produce time data using an internal time source (clock).
278 4.2.2 Reference time source
279 The internal time source shall use as its reference standard UTC date/time (UTC +0).
280 4.2.3 Content
281 Each time data shall include year, month, day, hour, minute and second.
282 4.2.4 Resolution
283 The time data shall have resolution of 1 s.
284 4.2.5 Stability
−6
285 The internal time source shall have a stability of 20 × 10 or better.
286 The internal time source shall keep the time for minimum 72 h when powered down.
287 4.2.6 Synchronization
288 The internal time source shall not deviate from the reference time source by more than 2 s. This shall be
289 ensured by check of synchronization between the internal time source and one or more external time
290 source(s) on a regular basis.
291 The following synchronisation events shall be logged:
292 — synchronisation event resulted in a deviation of more than 2 s;
293 — consecutive synchronisation attempts not resulting in a successful synchronisation during a timeframe
294 of 4 h.
295 Where applicable, the DHS shall be able to undertake correction to account for leap second off-set if not
296 already undertaken at source.
297 4.2.7 Quality code for time data
298 Each time data in the DHS shall be accompanied by a time data quality code.
299 One of the following quality codes shall be used with time data (see Table 1):
300 Table 1 — Time data quality codes
Rank Value Read as Interpretation
1 127 Measured There is no indication of a possible error in the time data or time
source
2 61 Uncertain Synchronization has adjusted the clock more than 2 s,
or there is a possible error in:
a) the internal time source or in the time data provided by it or
b) time data attached to other data received by the DHS
The alternatives presented in the above list are ranked from 1 to 2, where 1 is the highest rank.
NOTE The codes are based on the UN/CEFACT/EDED (EDIFACT Data Element Directory), D.14B, Data
Element 4405 (Status description code).
301 A synchronization where the clock is adjusted less than 2 s is not regarded as an error and shall in itself
302 not result in a change of quality code from 127.
303 4.3 Energy data
304 4.3.1 Source
305 The DHS shall be able to receive energy data from one or more ECF (see prEN 50463-2:2025).
306 If the DHS is capable of interfacing with multiple EMF in an EMS configuration, then the DHS shall be able
307 to identify each EMF uniquely. It shall be ensured that the DHS allocates the energy data to the correct
308 register and CEBD.
309 4.3.2 Type
310 The DHS shall receive energy data from the ECF necessary for the creation of CEBD.
311 NOTE Each energy data received from an ECF consist of two mandatory values (active energy
312 consumed/regenerated) and two conditional values (reactive energy consumed/regenerated, if AC electricity type is
313 measured by EMF).
314 4.3.3 Format
315 The values in the energy data received from an ECF will be in units of Watt-hour (active energy) and var-
316 hour (reactive energy) or their decimal-multiples.
317 The energy data received from an ECF are either energy delta values or energy index values or both.
318 If the only energy data received from an ECF are delta values and the DHS also produces optional index
319 values, the DHS shall use these delta values to produce the index values.
320 If the only energy data received from an ECF are index values, the DHS shall use these index values to
321 produce the delta values.
322 If the energy data received from an ECF are index values and delta values, the DHS shall use these inputs
323 to produce energy data of the same type (e.g. delta inputs are used by the DHS to produce delta values
324 only).
325 NOTE The algorithms for producing energy delta values in CEBD are specified in 4.7.4.
326 4.3.4 Index value overrun
327 The DHS shall be able to detect any index value overrun in an ECF from the energy data received from the
328 ECF. When this occurs, the DHS shall still be able to calculate required energy delta values.
329 4.3.5 Merging with time data
330 Energy data in the DHS shall be accompanied by time data according to 4.2, where required for the
331 production of CEBD. If the energy data provided by the ECF does not include time data, the DHS shall add
332 time data without introducing any time displacement error to the energy data.
333 4.3.6 Quality codes for energy data
334 Each energy data in the DHS shall be accompanied by an energy data quality code.
335 One of the following quality codes shall be used with energy data (see Table 2):
336 Table 2 — Energy data quality codes
Rank Value Read as Interpretation
1 127 Measured The energy data are based on measurements and calculations in
the ECF and there is no indication of a possible error
A correctly measured 0 kWh also has this quality code (e.g. in
case of running with pantograph down)
2 61 Uncertain There is a possible error in the energy data received from the ECF
3 46 Non- The DHS has no energy data available for the time period
existent represented by the time data.
The alternatives presented in the above list are ranked from 1 to 3, where 1 is the highest rank.
Examples of situations that when identified by the DHS should result in quality code 61: partially
missing energy data, negative values, extreme values, indication of EMF malfunction, energy data
received with quality code 61, attached time data received with quality code 61.
NOTE The codes are based on the UN/CEFACT/EDED (EDIFACT Data Element Directory), D.14B,
Data Element 4405 (Status description code).
337 If energy data are received from ECF with quality code attached, then these quality codes shall be used as
338 part of the basis for setting the quality code for each energy data when received to the DHS.
339 4.3.7 k-factor
340 Any DHS intended to be able to receive energy data as secondary values from one or more ECF, shall be
341 able to:
342 a) convert the secondary values to primary values upon reception of energy data to the DHS, by using
343 the correct k-factor;
344 b) store k-factor(s) in a non-volatile access-protected memory;
345 c) log each change of k-factor.
346 4.3.8 Accuracy
347 Energy data production within the DHS shall not introduce errors which degrade the accuracy of the input
348 data.
349 4.3.9 Transmission from EMF
350 The DHS energy data transfer arrangements shall be compatible with its intended EMF(s). The transfer of
351 energy data from a compatible ECF shall enable the DHS to fulfil the requirements in 4.7.
352 The transfer arrangements shall ensure the DHS receives a complete set of energy data for each time
353 reference period before commencing the transfer of energy data for the next time period.
354 The energy data might have shorter measurement period than TRP when received to the DHS.
355 See prEN 50463-2:2025, 4.4.8. for requirements of the timelength for which each energy data represents.
356 4.4 Location data
357 4.4.1 Source
358 The DHS shall be able to receive location data from an on-board function providing location data originating
359 from an external source. It may also be able to receive location data from additional sources of location
360 data generated on-board the traction unit.
361 4.4.2 Format
362 Location data shall be based on the World Geodetic System, revision WGS 84.
363 Location data used in the DHS shall be expressed as longitude and latitude using the format in Table 3:
364 Table 3 — Location data format
Format Latitude Longitude Minimum number of decimals
Decimal Degrees ±DD.XXXXX ±DDD.XXXXX 5
Abbreviations: D = degree digit, X = decimals. Positive value is north/west, Negative value is
south/east.
365 4.4.3 Merging with time data
366 Any location data received by the DHS without time data in compliance with 4.2 shall be compiled with the
367 corresponding time data by the DHS.
368 4.4.4 Accuracy
369 In open air the location data shall have an accuracy of at least 250 m.
370 4.4.5 Quality codes for location data
371 Each location data in the DHS shall be accompanied by a location data quality code.
372 One of the following quality codes shall be used with location data (see Table 4):
373 Table 4 — Location data quality codes
Rank Value Read as Interpretation
1 127 Measured the location data received by the DHS is trustworthy, i.e.
location data are based on coordinates provided from a
source external to the traction unit, giving longitude and
latitude coordinates and these coordinates are not older
than 15 s
2 56 Estimated location data based on coordinates from an additional
source on-board the traction unit (see 4.4.1), and these
coordinates are not older than 15 s
3 61 Uncertain location data older than 15 s or the DHS has identified
possible error in the location data
4 46 Non- the DHS has no location data available for the
existent measurement period represented by the time data
The alternatives presented in the above list are ranked from 1 to 4, where 1 is the highest
rank.
Examples of situations that when identified by the DHS should result in quality code 61:
partially missing location data, extreme values, indication of malfunction of location data
source (e.g. GNSS), location data received with too high inaccuracy (see 4.4.4) or with
quality code 61, attached time data received with quality code 61.
NOTE The codes are based on the UN/CEFACT/EDED (EDIFACT Data Element Directory),
D.14B, Data Element 4405 (Status description code).
374 If location data received by the DHS carries quality codes, then these quality codes shall be used as part
375 of the basis for setting the quality code for each location data when received to the DHS.
376 If the DHS has more than one location data available at time of use, then the DHS shall use the location
377 data with the highest rank. If these location data are of equal rank, the location data with newest time data
378 shall be used.
379 4.5 Other received or produced data
380 4.5.1 Types
381 The DHS may also handle and produce other data/data sets associated with other parts of the Energy
382 Measurement System and provide support for operational surveillance and maintenance
383 NOTE Examples of such data are voltage level, current level and non-mandatory flags from the EMF and data
384 from hybrid train-specific sources such as battery status, or other sources activated.
385 4.5.2 Data handling prioritization
386 Any data handling or communication activity linked to such data shall not interfere with the flow and
387 processing of data associated with CEBD.
388 4.5.3 Time tag
389 Data covered by 4.5 is not required to be linked to time data. Any time
...