EN 50463-3:2012

SLOVENSKI STANDARD
01-marec-2013
1DGRPHãþD
SIST EN 50463:2008
Ž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: Daten-Behandlung
Applications ferroviaires - Mesure d'énergie à bord des trains - Partie 3 : Traitement des
données
Ta slovenski standard je istoveten z: EN 50463-3:2012
ICS:
45.060.10 9OHþQDYR]LOD Tractive stock
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 50463-3
NORME EUROPÉENNE
December 2012
EUROPÄISCHE NORM
ICS 45.060.10 Supersedes EN 50463:2007 (partially)

English version
Railway applications -
Energy measurement on board trains -
Part 3: Data handling
Applications ferroviaires -  Bahnanwendungen -
Mesure d'énergie à bord des trains - Energiemessung auf Bahnfahrzeugen -
Partie 3 : Traitement des données Teil 3: Daten-Behandlung

This European Standard was approved by CENELEC on 2012-10-15. 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.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the CEN-CENELEC Management Centre or to any CENELEC member.

This European Standard exists 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, Former Yugoslav Republic of Macedonia, France, Germany,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Management Centre: Avenue Marnix 17, B - 1000 Brussels

© 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 50463-3:2012 E
Contents
Foreword . 3
Introduction . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions and abbreviations . 6
3.1 Terms and definitions . 6
3.2 Abbreviations . 8
4 Requirements . 9
4.1 General . 9
4.2 Time data . 9
4.3 Energy data . 10
4.4 Location data . 11
4.5 Other received or produced data . 12
4.6 Consumption point ID . 12
4.7 Production of CEBD . 12
4.8 DHS data storage . 14
4.9 Transmission of CEBD from DHS to DCS . 14
4.10 Marking and essential information . 15
4.11 Event recording . 15
4.12 DCS . 16
5 Conformity assessment . 16
5.1 General . 16
5.2 Testing framework . 17
5.3 Design review . 18
5.4 Type testing . 19
5.5 Routine testing . 27
Annex ZZ (informative) Coverage of Essential Requirements of EU Directives . 28
Bibliography . 29

Figures
Figure 1 - EMS functional structure and dataflow diagram . 5
Figure 2 – Example of energy index value . 7

Tables
Table 1 − Location data formats . 11

- 3 - EN 50463-3:2012
Foreword
This document (EN 50463-3:2012) has been prepared by CLC/TC9X "Electrical and electronic applications
for railways".
The following dates are proposed:
• latest date by which this document has to be
(dop) 2013-10-15
implemented at national level by publication of
an identical national standard or by
endorsement
• latest date by which the national standards
(dow) 2015-10-15
conflicting with this document have to
be withdrawn
This document (EN 50463-3:2012), together with parts 1, 2, 4 and 5, supersedes EN 50463:2007.
 this the series is based on and supersedes EN 50463:2007;
 the scope is extended, new requirements are introduced and conformity assessment arrangements
are added.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission and
the European Free Trade Association, and supports essential requirements of EU Directive(s).
For relationship with EU Directive 2008/57/EC amended by Commission Directive 2011/18/EU, see
informative Annex ZZ, which is an integral part of this document.
This document is Part 3 of EN 50463 which consists of the following parts, under the common title Railway
applications — Energy measurement onboard trains:
Part 1, General;
Part 2, Energy measuring;
Part 3, Data handling;
Part 4, Communication;
Part 5, Conformity assessment.
This series of European Standards follows the functional guidelines description in Annex A “Principles of
conformity assessment” of EN ISO/IEC 17000 tailored to the Energy Measurement System (EMS).
The requirements for Energy Measurement Systems in the relevant Technical Specifications for
Interoperability are supported by this series of European Standards.

Introduction
The Energy Measurement System provides measurement and data suitable for billing and may also be used
for energy management, e.g. energy saving.
This series of European Standards uses the functional approach to describe the Energy Measurement
System. These functions are implemented in one or more physical devices. The user of this series of
standards is free to choose the physical implementation arrangements.
Structure and main contents of the EN 50463 series
This series of European Standards is divided into five parts. The titles and brief descriptions of each part are
given below:
EN 50463-1 – General
The scope of EN 50463-1 is the Energy Measurement System (EMS).
EN 50463-1 provides system level requirements for the complete EMS and common requirements for all
devices implementing one or more functions of the EMS.
EN 50463-2 – Energy measuring
The scope of EN 50463-2 is the Energy Measurement Function (EMF).
The EMF provides measurement of the consumed and regenerated active energy of a traction unit. If the
traction unit is designed for use on a.c. traction supply systems, the EMF also provides measurement of
reactive energy. The EMF provides the measured quantities via an interface to the Data Handling System.
The EMF consists of the three functions: Voltage Measurement Function, Current Measurement Function
and Energy Calculation Function. For each of these functions, accuracy classes are specified and associated
reference conditions are defined. This part also defines all specific requirements for all functions of the EMF.
The Voltage Measurement Function measures the voltage of the Contact Line system and the Current
Measurement Function measures the current taken from and returned to the Contact Line system. These
functions provide signal inputs to the Energy Calculation Function.
The Energy Calculation Function inputs the signals from the Current and Voltage Measurement Functions
and calculates a set of values representing the consumed and regenerated energies. These values are
transferred to the Data Handling System and are used in the creation of Compiled Energy Billing Data.
The standard has been developed taking into account that in some applications the EMF may be subjected
to legal metrological control. All relevant metrological aspects are covered in this part of EN 50463.
EN 50463-2 also defines the conformity assessment of the EMF.
EN 50463-3 – Data handling
The scope of EN 50463-3 is the Data Handling System (DHS).
The on board DHS receives, produces and stores data, ready for transmission to any authorised receiver of
data on board or on ground. The main goal of the DHS is to produce Compiled Energy Billing Data and
transfer it to an on ground Data Collection Service (DCS). The DHS can support other functionality on board
or on ground with data, as long as this does not conflict with the main goal.
EN 50463-3 also defines the conformity assessment of the DHS.
EN 50463-4 – Communication
The scope of EN 50463-4 is the communication services.
This part of EN 50463 gives requirements and guidance regarding the data communication between the
functions implemented within EMS as well as between such functions and other on board units where data
are exchanged using a communications protocol stack over a dedicated physical interface or a shared
network.
- 5 - EN 50463-3:2012
It includes the on board to ground communication service and covers the requirements necessary to support
data transfer between DHS and DCS.
EN 50463-4 also defines the conformity assessment of the communications services.
EN 50463-5 – Conformity assessment
The scope of EN 50463-5 is the conformity assessment procedures for the EMS.
EN 50463-5 also covers re-verification procedures and conformity assessment in the event of the
replacement of a device of the EMS.
EMS functional structure and dataflow
Figure 1 illustrates the functional structure of the EMS, the main sub-functions and the structure of the
dataflow and is informative only. Only the main interfaces required by this standard are displayed by arrows.
Because the communication function is distributed throughout the EMS, it has been omitted for clarity. Not all
interfaces are shown.
Time Reference Source
Location Reference Source
Current Measurement Function
Voltage Measurement Function
Data
Data Handling System
Energy Calculation Function
Collection
Service
Energy Measurement Function Data Handling System
(DCS)
(EMF) (DHS)
EN 50463-2 (Energy Measuring) EN 50463-3 (Data Handling)
Energy Measurement System (EMS)
EN 50463-1 (General), EN 50463-4 (Communication), EN 50463-5 (Conformity Assessment)

On board (Traction Unit)
On ground
Figure 1 - EMS functional structure and dataflow diagram

1 Scope
This European Standard covers the requirements applicable to the Data Handling System (DHS) of an
Energy Measurement System.
This document also includes the basic requirements for the Data Collection Service on ground, relating to the
acquisition and storage of Compiled Energy Billing Data.
The Conformity Assessment arrangements for the DHS are specified in this document.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
CEN/TS 45545-2:2009, Railway applications — Fire protection on railway vehicles — Part 2: Requirements
for fire behaviour of materials and components
CLC/TS 45545-5:2009, Railway applications — Fire protection on railway vehicles — Part 5: Fire safety
requirements for electrical equipment including that of trolley buses, track guided buses and magnetic
levitation vehicles
EN 50121-3-2:2006, Railway applications — Electromagnetic compatibility — Part 3-2: Rolling stock —
Apparatus
EN 50155:2007, Railway applications — Electronic equipment used on rolling stock
EN 50463-1:2012, Railway applications — Energy measurement on board trains — Part 1: General
EN 50463-2:2012, Railway applications — Energy measurement on board trains — Part 2: Energy
measuring
EN 50463-4:2012, Railway applications — Energy measurement on board trains — Part 4: Communication
EN 50463-5:2012, Railway applications — Energy measurement on board trains — Part 5: Conformity
assessment
EN 60529, Degrees of protection provided by enclosures (IP Code) (IEC 60529)
EN 61373:2010, Railway Applications — Rolling stock equipment — Shock and vibration tests
World Geodetic System, revision WGS 84
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in EN 50463-1:2012 and the following
apply.
NOTE When possible, the following definitions have been taken from the relevant chapters of the International Electrotechnical
Vocabulary (IEV), IEC 60050-311, IEC 60050-312, IEC 60050-313, IEC 60050-314, IEC 60050-321 and IEC 60050-811. In such cases,
the appropriate IEV reference is given. Certain new definitions or modifications of IEV definitions have been added in this standard in
order to facilitate understanding. Expression of the performance of electrical and electronic measuring equipment has been taken from
EN 60359.
- 7 - EN 50463-3:2012
3.1.1
Coordinated Universal Time
UTC
time scale which forms the basis of a coordinated radio dissemination of standard frequencies and time
signals, and corresponds exactly in rate with international atomic time, but differs from it by an integral
number of seconds
Note 1 to entry: Coordinated universal time is established by the International Bureau of Weights and Measures (BIPM) and the
International Earth Rotation Services (IERS).
Note 2 to entry: The UTC scales is adjusted by the insertion or deletion of seconds, so called positive or negative leap seconds, to
ensure approximate agreement with UT1.
[SOURCE: ITU-R Recommendation TF.686, modified]
3.1.2
energy delta value
energy consumed and/or regenerated during a time period
Note 1 to entry: See Figure 2 for example.
3.1.3
energy index value
total accumulated energy consumption and/or energy regeneration at the end of a time period
Note 1 to entry: See Figure 2 for example.
energy index value: 2350 2360 2372 2379 2393 2404
10 12 7 14 11
energy delta value:
Timeline:
10:35 10:40 10:45 10:50 10:55 11:00

Figure 2 – Example of energy index value
3.1.4
flag
code indicating information relevant to the functioning of the EMS
Note 1 to entry: Examples include data quality, operational status, etc.
3.1.5
index value overrun
return to zero of the index value after reaching the maximum value allowed by the register
3.1.6
k-factor
multiplicand necessary to convert a secondary value into a primary value
Note 1 to entry: Each Voltage Measurement Function and/or Current Measurement Function can have a specific k-
factor. If the k-factor is applied to Energy Data, this factor is the product of the k-factors of the Voltage Measurement
Function and/or Current Measurement Function used.

3.1.7
location data
data describing the geographical position of the traction unit
3.1.8
log
list of recorded events
3.1.9
primary value
value referred to the measuring inputs of an EMF
3.1.10
secondary value
value of current, voltage, power or energy which needs to be multiplied by a k-factor to become a primary
value
3.1.11
time data
data describing a time and date of a defined time source
3.1.12
time period
period of time for which energy data is produced
3.1.13
Time Reference Period
TRP
time period for which CEBD is produced
3.2 Abbreviations
For the purposes of this document, the following terms and definitions apply.
CEBD Compiled Energy Billing Data
CL Contact Line
DCS Data Collection Service
DHS Data Handling System
ECF Energy Calculation Function
EMF Energy Measurement Function
EMS Energy Measurement System
RAMS Reliability, Availability, Maintenance and Safety
TRP Time Reference Period
UTC Coordinated Universal Time

- 9 - EN 50463-3:2012
4 Requirements
4.1 General
The requirements in EN 50463-1:2012, Clause 4 apply to any device containing one or more functions of the
DHS where applicable. EN 50463-3 defines additional requirements specific to the DHS and basic
requirements for the DCS.
The DHS shall comply with the following requirements except for 4.12.
The DCS shall comply with the requirements in 4.12 only.
4.2 Time data
4.2.1 Source
The DHS shall produce time data using an internal time source (clock).
4.2.2 Reference time source
The internal time source shall use as its reference Standard UTC time/date (UTC +0).
4.2.3 Format
The time data shall have the following format: YYYYMMDDHHmmss:
a) YYYY : Year;
b) MM : Month;
c) DD: Day;
d) HH : Hour;
e) mm : Minute;
f) ss: Second.
4.2.4 Resolution level
The time data shall have resolution of 1 s.
4.2.5 Stability
-6
The internal time source shall have a stability of 20 x 10 or better.
4.2.6 Synchronisation
The internal time source shall not deviate from the reference time source by more than 2 s. This shall be
ensured by checking the synchronisation between the internal time source and one or more external time
source(s) on a regular basis.
All synchronisation events shall be logged.
Where applicable, the DHS shall be able to undertake correction to account for leap second off-set if not
already undertaken at source.
4.2.7 Flags for time data
A quality flag shall be attached to the time data if a change (i.e. synchronisation, manual adjustment, error
etc.) has resulted in a change of the DHS internal time source by 2 s or more.
This is necessary to highlight a change in time data (e.g. resulting in an abnormal TRP length which may
affect the subsequent processing and use of the associated data).

4.3 Energy data
4.3.1 Source
The DHS shall be able to receive energy data from one or more ECF.
If the DHS is capable of interfacing with multiple EMF in an EMS configuration, then the DHS shall be able to
identify each EMF uniquely. It shall be assured that the DHS allocates the energy data to the correct register
and CEBD.
4.3.2 Type
The DHS shall receive energy data from the ECF necessary for the creation of CEBD.
NOTE Each energy data will consist of two mandatory values (active energy consumed/regenerated) and two conditional values
(reactive energy consumed/generated).
4.3.3 Format
The values in the energy data received from an ECF will be in units of Watt-hour (active energy) and var-
hour (reactive energy) or their decimal-multiples.
The energy data received from an ECF is either energy delta values or energy index values or both.
If the only energy data received from an ECF are delta values and the DHS also produces optional index
vales, the DHS shall use these delta values to produce the index values.
If the only energy data received from an ECF are index values, the DHS shall use these index values to
produce the delta values.
If the energy data received from an ECF are index values and delta values, the DHS shall use these inputs
to produce energy data of the same type (e.g. delta inputs are used by the DHS to produce delta values
only).
NOTE The algorithms for producing energy delta values in CEBD are specified in 4.7.3.
4.3.4 Index value overrun
The DHS shall be able to detect any index value overrun in an ECF from the energy data received from the
ECF. When this occurs, the DHS shall still be able to calculate required energy delta values.
4.3.5 Merging with time data
Energy data in the DHS shall be accompanied by time data according to 4.2, where required for the
production of CEBD. If the energy data provided by the ECF does not include time data, the DHS shall add
time data without introducing any time displacement error to the energy data.
4.3.6 Energy data flags
The DHS shall accept any quality flags attached to the energy data received from the ECF.
The DHS shall ensure that all energy data in the DHS carries one the following types of quality flags:
a) Measured (code: 127): based on measurements and calculations in the ECF;
b) Uncertain (code: 61): indicating that the energy data transmitted from ECF may be wrong (e.g.
partially missing energy data, indications of EMF errors, flag “Uncertain” on energy data or time
data);
c) Non-existent (code: 46): no energy data available to DHS.
NOTE The codes are based on the ebIX-code system, UN/CEFACT Data Element 4405 Release D.05A.
4.3.7 k-factor
Any DHS intended to be able to receive energy data as secondary values from one or more ECF, shall be
able to:
- 11 - EN 50463-3:2012
a) convert the secondary values to primary values upon reception of energy data to the DHS, by using
the correct k-factor;
b) store k-factor(s) in a non-volatile access-protected memory;
c) log each change of k-factor.
NOTE An ECF might be configured to send a flag to the DHS for each change of k-factor in the EMF. If not, the k-factor can also be
found in the essential information of the intended ECF.
4.3.8 Accuracy
Energy data production within the DHS shall not introduce errors which degrade the accuracy of the input
data.
4.3.9 Transmission from EMF
The DHS energy data transfer arrangements shall be compatible with its intended EMF(s). The transfer of
energy data from a compatible ECF shall enable the DHS to fulfil the requirements in 4.7.
The transfer arrangements shall ensure the DHS receives a complete set of energy data for each time
reference period before commencing the transfer of energy data for the next time period.
4.4 Location data
4.4.1 Source
The DHS shall be able to receive location data from an on board function providing location data originating
from an external source. It may also be able to receive location data from additional sources of location data
generated on board the traction unit.
4.4.2 Format
Location data shall be based on the World Geodetic System, revision WGS 84.
Location data used in the DHS shall be expressed as Longitude and Latitude in one of the formats in Table
1. The preferred format for CEBD is Decimal degrees with five decimals.
Table 1 − Location data formats
a b
Format Latitude Longitude Minimum number
of decimals
Decimal Degrees +/-DD.XXXXX +/-DDD.XXXXX 5
Degrees, Minutes & Seconds +/-DDMMSS +/-DDDMMSS 0
Degrees & Minutes +/-DDMM.XXX +/-DDDMM.XXX 3
a
Positive values are North, negative are South.
b
Positive values are East, negative are West.
Abbreviations: D= degree digit, M=minute digit, S=seconds digit, X=decimals.
Dividers (characters, letters, space, etc.) can be used between values of Degree, Minute and Second.
4.4.3 Merging with time data
Any location data received by the DHS without time data in compliance with 4.2 shall be compiled with the
corresponding time data by the DHS.
4.4.4 Accuracy
In open air, the location data shall have an accuracy of at least 250 m.
4.4.5 Type
The Location data in the DHS shall have the following ranking order (a = highest rank):

a) Measured: location data based on coordinates provided from an source external to the traction unit,
giving longitude and latitude coordinates and these coordinates are not older than 15 s;
b) 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;
c) Uncertain: location data older than 15 s.
If the DHS has available more than one source of location data, then location data with highest rank shall
always be used.
4.4.6 Location data flags
Location data shall be tagged with a quality flag based on its type:
a) Measured: 127;
b) Estimated: 56;
c) Uncertain: 61;
d) Non-existent: 46.
NOTE The codes are based on the ebIX-code system, UN/CEFACT Data Element 4405 Release D.05A.
4.5 Other received or produced data
4.5.1 Types
The DHS may also handle and produce other data/datasets associated with other parts of the Energy
Measurement System, and provide support for operational surveillance and maintenance.
NOTE Examples of such data are voltage level, current level and non-mandatory flags from the EMF.
4.5.2 Data handling prioritisation
Any data handling or communication activity linked to such data shall not interfere with the flow and
processing of data associated with CEBD.
4.5.3 Time tag
Data covered by 4.5 is not required to be linked to time data. Any time data attached should be in
accordance with 4.2.3 and 4.2.4.
4.6 Consumption point ID
The DHS shall be capable of accepting, storing and using a consumption point ID.
NOTE Definition and further requirements for the CPID itself can be found in EN 50463-1.
4.7 Production of CEBD
4.7.1 Type of Data
The DHS shall, at the end of each TRP, produce a set of Compiled Energy Billing Data (CEBD), by
assembling the following data:
a) time data;
b) energy data, delta values;
c) location data;
d) consumption point ID;
- 13 - EN 50463-3:2012
e) quality flags;
f) energy data, index values (optional);
g) traction type flag (optional).
4.7.2 Time Reference Period
TRPs shall be consecutive 5 min periods, originating from the time stamp 0000 (mmss, see 4.2.3).
The time data to be used in the CEBD shall be the end time of the TRP.
NOTE It is permitted to transmit energy data of shorter time period from on board to on ground, but this is not regarded as CEBD.
4.7.3 Energy data
Energy values in CEBD shall be of unit kWh for active energy and kvarh for reactive energy.
The energy delta values shall be complete sets of energy data according to sets of energy data received
from ECF.
NOTE 1 Each set of energy data received by the DHS will consist of two mandatory values (active energy consumed/regenerated)
and two conditional values (reactive energy consumed/regenerated).
If the DHS produces delta values for use in CEBD they shall be calculated by one of the following methods:
a) accumulating all the delta values for the time periods covering each 5 min TRP;
b) calculating the difference between the energy index value at the start and the end of each TRP.
The energy delta values to be used in CEBD shall be primary values including the first decimal place, with
any remainder being carried over and included within the next TRP.
NOTE 2 The carry over ensures that no measured energy data is omitted overall, whilst permitting quantities less than 0,1 to be deferred
to a subsequent 5 min TRP.
If energy index values are used to produce the energy delta values in CEBD, and the energy index value for
the start of the TRP is missing, then the latest energy index value used previously in production of the latest
CEBD shall be used as a substitute. The energy delta values created under such conditions shall be flagged
‘Uncertain’ (see 4.3.6).
4.7.4 Location data
The CEBD shall be produced using the location data of highest rank according to 4.4.5.
4.7.5 Format
The DHS shall produce and transmit the CEBD in a format compatible with the intended DCS.
4.7.6 Missing input data
If there is no energy data available at time of CEBD production, then blank values shall be used in place of
the missing data in the CEBD. Under such conditions, a quality flag “Non-existent” (see 4.3.5) shall be added
to the Energy Data.
If there is no location data available at time of CEBD production, then blank values shall be used in place of
the missing data in the CEBD. Under such conditions, a quality flag “Non-existent” (see 4.4.6) shall be added
to the Location Data.
The DHS shall not retrospectively produce or substitute CEBD data for earlier TRPs.
NOTE 1 The format of the blank value should ensure that the value cannot be perceived as a measured value.
NOTE 2 This is required to secure the integrity of the DHS handling of commercial data.
4.7.7 Data integrity
The DHS shall store CEBD complete with measures to safeguard data integrity (e.g. checksum etc.).

4.7.8 Flags
When producing the CEBD, each type of data in the CEBD shall, as a minimum, adopt mandatory flags
attached to the data that it originates from.
When multiple flags are applicable, the flag of lowest quality is adopted (see 4.3.5 and 4.4.6 for details).
4.8 DHS data storage
4.8.1 Storage time
The DHS shall store data for the minimum period indicated below:
 software and system parameters: until replaced by authorised user;
 CEBD: 60 days;
 log-files linked to CEBD and CEBD-related data: 60 days;
 any other data: no minimum requirement.
All data older than the minimum required storage period can be overwritten or deleted.
NOTE 1 A log-file is a register with a list of time-stamped incidents for later review.
NOTE 2 This standard does not define the handling and format of the memory itself.
4.8.2 Memory Capacity
The DHS data storage capacity shall ensure all data storage needs are met without operational problems. It
shall be more than 25 % above estimated maximum memory usage.
4.9 Transmission of CEBD from DHS to DCS
4.9.1 General
This clause describes the basic requirements for the transfer of CEBD to DCS.
NOTE For details of communication service, see EN 50463-4.
4.9.2 Type of information
The required data to be transmitted from the DHS to the DCS shall be the CEBD.
Transmission of other types of data is allowed, but shall not interfere with the transmission of the CEBD.
4.9.3 Time between each transfer
The DHS shall have a procedure for transfer of CEBD from DHS to DCS.
The procedure shall, as a minimum, include all CEBD not previously transferred to DCS.
The procedure shall run automatically, as a minimum, once per 24 h when EMS is fully operational.
The DHS shall also be able to execute the procedure on request from DCS or any intended on board source,
when EMS is fully operational.
The DHS should include an automatic execution of this procedure at DHS intentional power down,
alternatively an automatic execution when EMS is powered up and entering operational mode. This is to
ensure that all untransfered CEBD is sent from on board to on ground in due time for use in settlement.
NOTE On board source could be train management systems, driver-operated push-button systems, etc.
4.9.4 Communication channel
The transmission of CEBD from the DHS to the DCS shall be possible by communication services available
and accessible in the intended geographical area of operation for the EMS. These services used shall
ensure the transfer of CEBD (including the requirements of 4.12.3) when the EMS is in operational mode.

- 15 - EN 50463-3:2012
4.9.5 Security
The CEBD shall be packed ready for secure transmission. All information necessary for the DCS to unpack
the CEBD without corruption and store an authentic copy, shall be made publicly available by the DHS
supplier to the purchaser of the DHS. The DHS supplier shall also make publicly available the necessary
information to allow the DCS to request CEBD from the DHS, for example where the DCS has missing or
uncertain CEBD.
NOTE The WELMEC Guide (Doc. 7.2, Issue 3) may be helpful in determining appropriate arrangements.
4.10 Marking and essential information
4.10.1 Marking of the DHS
Devices which include a DHS will have marking as specified in EN 50463-1:2012, 4.3.1.1.
4.10.2 Essential information
In addition to the requirements given in EN 50463-1:2012, 4.3.1.2, the following information relevant to
control the behaviour of the DHS shall be available in a format (e.g. hardcopy or electronic) agreed between
supplier and purchaser:
a) the auxiliary voltage and form (e.g. 230 V 50 Hz a.c., 110 V d.c.), together with the maximum power
consumption;
b) main diagrams and drawings (e.g. overall schematics, general arrangements etc.);
c) terminal marking identification information for:
1) all hardware interfaces;
2) auxiliary voltage connections;
d) software version and other information necessary for configuration control;
e) specification of all interfaces, including communication protocols and software used for communications
security.
If different functions are included in one device it is sufficient to list information only once.
4.11 Event recording
4.11.1 General
The DHS shall record all critical events in one or more log-files.
4.11.2 Type of events
The following events shall be stored in a log-file:
 flags, except data quality flags, received from other parts of the EMS;
 configuration change;
 DHS parameter change;
 requests for access to stored data or system (not required for read-only access requests);
 time synchronisation;
 DHS power up/down;
and where applicable:
 traction supply system change;
 k-factor change
and where available:
 error events detected by built-in diagnostics of DHS.
NOTE 1 Flags received from other parts of the EMS can indicate the same type of events as stated in the above bullet list.
NOTE 2 The log-files are intended to assist in activities such as auditing and maintenance.
NOTE 3 Other critical events are also logged depending on implementation.
4.12 DCS
4.12.1 General
This clause describes the basic requirements for a compatible DCS.
For the purpose of this standard, the DCS is considered to be a functional service for the acquisition of
CEBD.
4.12.2 Reception of CEBD from DHS
The DCS shall be able to receive, read and store the CEBD received from a DHS.
The DCS shall be able to handle any authenticity/integrity check implemented in the communication protocol
used by the DHS.
4.12.3 Request to DHS for more CEBD data
The DCS shall be able to request CEBD from the DHS, e.g. when the set of time series of CEBD stored in
DCS is incomplete.
NOTE It is possible to have procedures that manually or automatically request other types of data from the DHS.
4.12.4 Storage of CEBD
Immediately after the DCS has received, read and checked the CEBD, it shall be stored. Any signal from
DCS to DHS to confirm successful transfer of data at application level shall only be sent after the data is
stored.
5 Conformity assessment
5.1 General
Any DHS intended to be used in an EMS, shall be subjected to a conformity assessment as described in
Clause 5. This clause also includes testing for DCS requirements necessary to fulfil the required functions of
the DHS
The conformity assessment in Clause 5 relates to the requirements stated in Clause 4 of this document and
the applicable requirements stated in EN 50463-1:2012, Clause 4.
The conformity assessment requirements in Clause 5 of this document applies only to one part of the EMS.
In the following clauses the numbers in square brackets e.g. [1.2.3.4] indicates the clause in this document
that contains requirement(s) against which conformity is being established.
5.1.1 Applicability
The conformity assessment described in Clause 5 applies to any device performing any function covered by
EN 50463-3.
5.1.2 Methodology
The conformity assessment shall be undertaken using the following methods:
a) device design review;
b) device type test;
- 17 - EN 50463-3:2012
c) device routine test.
It is envisaged that a) and b) have been concluded with positive verdict before c) is undertaken.
All conformity activities of a complete EMS are contained in EN 50463-5.
5.1.2.1 Device design review
An assessment of the adequacy of the technical design of a DHS shall be undertaken, through examination
of technical documentation for the device together with any supporting evidence.
This shall also include examination of documentation detailing integration and installation constraints.
If there is any change to a device that has been previously assessed, the review shall focus on the change
and its impact on other aspects.
5.1.2.2 Device type test
Type tests shall be carried out to verify that each equipment type holding a DHS meets the requirements
contained in EN 50463-3.
Type tests shall be performed on at least one sample of a designated equipment type.
If a previously assessed device is altered, the type test shall focus on the alteration and its impact on other
aspects.
5.1.2.3 Device routine test
Routine tests shall be carried out on each device holding a DHS, to verify that it is in compliance with its
stated equipment type.
5.2 Testing framework
5.2.1 General
Any device(s) holding a DHS shall be tested according to the test procedures defined in this document.
The device shall be tested in its fully assembled state and shall be mounted and connected to simulate the
least favourable arrangement for each test.
Where tests of the DHS require other parts of the EMS to be present, these parts shall form part of the test
assembly. Alternatively, test equipment may be used to simulate these parts of the EMS provided that the
former authentically replicate the latter, so far as is necessary to ensure the test is valid.
The approval is also valid for assemblies where a device/interface has been replaced with a device/interface
having technically equivalent characteristics and is also compliant with EN 50463.
The test assembly shall include a relevant DCS, or equipment configured to authentically simulate it.
All testing shall be undertaken under reference conditions unless otherwise stated.
5.2.2 Reporting
All tests performed on DHS or DCS shall be formally documented. The report shall include all relevant details
of the devices of the complete assembly used in the testing procedure.
The report shall, as a minimum, include the following information:
a) test environment:
1. date and time;
2. location;
3. test authority;
4. parties present;
5. device and test equipment arrangement;
6. environmental conditions;
b) device details:
1. equipment marking details and essential information (see 4.10);
2. functions included in the device;
3. software and firmware versions;
4. specification of all physical interfaces;
c) DCS details:
1. DCS simulation arrangements;
d) test details:
1. type of test and test conditions;
2. test equipment, tools and software used for the test;
3. test circuit arrangement and configuration including interfaces used;
4. test engineer(s);
5. test results.
5.3 Design review
5.3.1 General
An assessment of the adequacy of the technical design of a DHS shall be performed, through examination of
technical documentation for the device and supporting evidence provided by the supplier.
The design review shall take account of the location in to which the device is intended to be installed (e.g.
compliance to safety requirements is in some cases only achieved once the device is installed).
The design review and its outcome shall be documented in a design review report.
5.3.2 Interfaces
Verify that the DHS includes all mandatory interfaces [EN 50463-1:2012, 4.3.2.1] and that these are fully
specified in the accompanying documentation.
Verify that the use of any interface will not degrade the intended performance of other interfaces and the
DHS. If this can only be adequately verified by undertaking testing, then this shall be stated in the design
review report.
5.3.3 Access control
Verify that all requests for access to data, software or system parameters relevant for the production and
storage of CEBD, pass through an authorisation procedure before access is granted, and that all requests
and all changes are logged [EN 50463-1:2012, 4.3.2.2].
5.3.4 Software
Verify that the software in the DHS is in compl
...