Professional Documents
Culture Documents
ICS
English Version
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee CEN/TC 256.
If this draft becomes a European Standard, CEN 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 CEN in three official versions (English, French, German). A version in any other language
made by translation under the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the
same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and 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.
© 2009 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 15380-4:2009: E
worldwide for CEN national Members.
prEN 15380-4:2009 (E)
Contents Page
Foreword ..............................................................................................................................................................3
Introduction .........................................................................................................................................................4
1 Scope ......................................................................................................................................................5
2 Normative references ............................................................................................................................5
3 Terms and definitions ...........................................................................................................................5
4 Symbols and abbreviated terms ..........................................................................................................9
5 Functional structure ..............................................................................................................................9
5.1 General remarks.....................................................................................................................................9
5.2 Indication systematic ............................................................................................................................9
5.3 Code letters ......................................................................................................................................... 10
st
5.3.1 Code letters used to designate 1 level function groups............................................................... 10
st rd
5.3.2 Code letters used to designate function groups from the 1 to the 3 level ............................... 12
5.4 Transverse functions ......................................................................................................................... 21
Annex A (informative) Functions on level 4 and level 5 ............................................................................... 24
Annex B (informative) Interrelation between EN 15380-2 and EN 15380-4 ................................................. 50
Annex C (informative) Elementary functions ................................................................................................ 52
Annex D (informative) Code letters used to designate detail properties ................................................... 58
D.1 General ................................................................................................................................................. 58
D.2 Indication systematic ......................................................................................................................... 58
Annex E (informative) Example for a complete structure of function groups ........................................... 62
Annex F (normative) Rules to define the function level ............................................................................... 64
Annex G (informative) Rules to create function names ............................................................................... 65
G.1 General ................................................................................................................................................. 65
G.2 Function terms .................................................................................................................................... 65
G.3 Rules for creating function short names ......................................................................................... 65
Bibliography ................................................................................................................................................... 101
2
prEN 15380-4:2009 (E)
Foreword
This document (prEN 15380-4:2009) has been prepared by Technical Committee CEN/TC 256 “Railway
Applications”, the secretariat of which is held by DIN.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association, and supports essential requirements of EC Directive(s).
For relationship with EC Directive(s), see informative Annex ZA, which is an integral part of this document.
This series of European Standards “Railway applications — Classification system for rail vehicles" consists of
the following parts:
Part 1: General
3
prEN 15380-4:2009 (E)
Introduction
The functional breakdown structure is used by all parties involved in the rolling stock product definition phase
and the following processes to structure the functional requirements and use cases according to a standardized
list of functions. It starts with the concept and spreads across the whole product life cycle. During this period the
level of detail of the structure could be adapted according to the project progress. This means that functions in
a product concept catalogue mainly are described by requirements. The transfer into implementable hard- and
software takes place later.
The product breakdown structure according to EN 15380-2 of this standard series and the functional
breakdown structure according to part 4 of this standard are not in contradiction to each other but they
complement each other. While the PBS, consisting of the standardized list of subsystems and devices, is used
for structuring system requirements and related use cases the FBS standard describes the functions of a
vehicle and is used to get a correlation between functional requirement and the structure of functions even as
for the related use cases. These structures describe different views on the rolling stock product. The
importance of the two structures may be different according to the users’ tasks as well the project stage (see
also EN 15380-1, Annex C).
The FBS can also be for specifying tasks as well as for analysing tasks.
The functional assessment especially affects the field of RAMS / LCC (Reliability, Availability, Maintainability,
Safety / Life-Cycle Costs). Often during the project process values have to be given at a stage when insufficient
information regarding the technical solution is available. At this stage EN 15380-2 is not applicable.
In all cases in which functionality is a key issue (e.g. safety and reliability analyses, inspections and testing,
maintenance programmes, field data acquisition and related documentation) communication is based on a
functional vehicle structure composed of functional groups – particularly when cross-system or interdisciplinary
considerations are important.
Functions are grouped into levels regardless of their vehicle specific technical realization. In designating the
functions, attention was paid to respect the general considerations to express the functions themselves and not
to designate the function carrier. This is coherent with EN 61346.
This applies similarly when the functional vehicle breakdown structure is met in tracing vehicle properties for
example during validation phase. A lot of required properties fixed in the product concept catalogue are
realized, diagnosed and rated as functioning or malfunctioning during operation. Only afterwards the link is
made to the physical structure and respectively to the assessment of the function of technical solutions.
There is not necessarily an unequivocal relationship between function and its technical realization. A unit of
observation can be a function carrier for different functions at the same time or in sequence. This means that a
entity can be related to different functions and even from different levels (see Annex A).
Assignment of examples for well known function carriers are given for easier understanding.
4
prEN 15380-4:2009 (E)
1 Scope
This standard forms the basis for the generation and interpretation of railway specific functional structures
during the life cycle of a railway vehicle or its assemblies. This standard also is applicable to specific vehicles
like track machines snow ploughs etc. The specific functions of their specific work process are not included in
describing this standard; they have to be added for the individual project.
EN 15380-4 also covers the requirements of the TSIs (Technical Specifications for Interoperability of Rolling
stock) described in chapter 2.1 and the requirements of TR 50126-3 and completes these documents.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced document
(including any amendments) applies.
EN 15380-1, Railway applications — Designation systematic for railway vehicles — Part 1: General principles
EN 15380-2, Railway applications — Designation system for railway vehicles — Part 2: Product groups
EN 61346-1, Industrial systems, installations and equipment and industrial products — Structuring principles
and reference designations — Part 1: Basic rules (IEC 61346-1:1996)
EN 61346-2, Industrial systems, installations and equipment and industrial products — Structuring principles
and reference designations — Part 2: Classification of objects and codes for classes (IEC 61346-2:2000)
EN 50129, Railway applications — Communication, signalling and processing systems — Safety related
electronic systems for signalling
IEC 61226:2005, Nuclear power plants — Instrumentation and control systems important to safety -
Classification of instrumentation and control functions
3.1
function
specific purpose or objective to be accomplished, that can be specified or described without reference to the
physical means of achieving it (IEC 61226:2005)
NOTE A function transfers (considered as a black-box) input parameters (material, energy, information) into aim
related output parameters (material, energy, information).
3.2
transverse function
destined for the use together with several level 2 and level 3 functions of the FBS at the same time
NOTE The transverse functions are not part of the FBS but are implicit for example ”provide diagnosis” or
“communicate with train bus”
5
prEN 15380-4:2009 (E)
3.3
Functional Breakdown Structure (FBS)
hierarchical structure summarizing a set of functions leading to the same general focus or service
3.4
function level
level to group functions of equal purpose
3.4.1
st
1 level function
functional domain that encompasses a set of functions related to a same general focus or service for the
considered (rolling stock) system
st
NOTE Example for a 1 level function is:
3.4.2
nd
2 level function
related to a specific set of activities which contributes to the completion of the functional domain defined at the
first level
nd
NOTE 1 Examples for 2 level function are:
nd
NOTE 2 At this level, it is not said how a 2 level function is to be implemented.
nd
NOTE 3 A specific 2 level function often is related to an engineering discipline and might be supported by one or a
minimum number of subsystems.
NOTE 4 Each function at level 2 or level 3 has one or several transverse functions as sub-functions.
3.4.3
rd
3 level function
related to a specific activity within the related set of interconnected activities, it encompasses a set of tasks
NOTE 1 A function at least at level 3 should be supported as much as possible by one single subsystem.
rd
NOTE 2 An example for 3 level function is:
NOTE 3 Each function at level 2 or 3 has one or several transverse functions as sub-functions.
3.4.4
th
4 level function
rd
usually related to a task, which performs discrete actions necessary for performing a 3 level activity
3.4.5
th
5 level function
related to a task, which performs discrete actions necessary for performing a 4th level activity
6
prEN 15380-4:2009 (E)
3.5
requirement
necessary condition or ability to constrain the solutions of a task or an aim
NOTE 1 A requirement describes for example, performance characteristics, operational conditions and quality attributes,
expressed as measurable and testable technical parameters or indicators.
NOTE 3 Beside requirements allocated to functions are additional requirements allocated to other features (e.g. design,
manufacturing).
3.5.1
functional requirement
expresses the requirements on a certain functionality
NOTE 1 Functional requirements and use cases come from passenger / pay load and operator request than from
integrator and supplier. They are expressing the requirements on a certain functionality given in the FBS regarding
interoperability (with other functions), operation, function/ behaviour, or functional architecture/design constraints.
The functional designation usually is additionally stated more precisely by detail properties (see also Annex D)
that provide more information referring to reliability, availability, performance, quality, documentation, input,
output, realtime.
These higher-level functional goals pointed out for ambient conditions, design features and selected target
groups / target objects are “requirements to a function”.
NOTE 2 In the FRS associated to a function at level 2 or 3 the requirements met by the transverse functions are listed
for each transverse function.
3.5.2
system requirement
requirement on a subsystem or device
NOTE Requirement on a subsystem or device regarding the requested technical compatibility, reliability, availability,
maintainability, environmental impact/conditions (recyclables, emissions, EMC, climate, vibration), LCC, performance,
quality, documentation, realtime behaviour, physical limits (dimension, weight), electrical interface (plugs, voltage, physical
layer), or mechanical interface (fixing points, fixing method).
3.6
scenario
possible transient, unsteady or steady states of the regarded system or of system-user interaction including
environmental or other influences
3.7
use case
describes what a system does from the view of an exterior observer
3.8
object
component, element, device, subsystem, functional unit, operating medium or system that can be observed in
its own right
3.9
error
deviation from the intended design which could result in unintended system behaviour or failure
7
prEN 15380-4:2009 (E)
[EN 50129]
NOTE An error needs corrective action, is caused by defect component and can be displayed to the driver or
workshop. An error can lead to a failure
3.10
fault
an abnormal condition which could lead to an error in the system. A fault can be random or systematic
[EN 50129]
3.11
failure
deviation from specified performance of a system. A failure is the consequence of a fault or error in the system
[EN 50129]
3.12
event
occurrence of a state at a defined precondition and time
3.13
monitoring
independent real-time observation of system, consist and train states (in cases also based on combinatory
logic) for manual or automatic action
3.14
protocol event
event which is not result of a fault, failure or error
3.15
alarm
event requiring driver interaction, with a defined priority
NOTE 2 "Man" in this specific context means passenger, train crew or maybe control operator.
3.16
elementary function
an elementary function is an indivisible, universally valid, basic function
3.17
detail property
provides information that supplements the functional designation using the format shown in Figure 1
NOTE Relevance for higher-level functional goals, ambient conditions, design features and target group / target object
are set out in Annex D.
3.18
function carrier
physical unit of observation to fulfil or partly fulfil one or more required functions
8
prEN 15380-4:2009 (E)
NOTE function carriers have to be considered as black box while describing the function
HMI Human-Machine-Interface
5 Functional structure
The hierarchy of the functional groups serves as a guideline when creating functional structures. Functions are
realized at the technical level as hardware and software within hierarchically structured units. Although the units
interact at the functional level, they may be spatially separate from one another.
Expanding the functions, elementary functions and characteristic features is possible within the scope of this
standard. Whether it is necessary to make use of this option will depend on the specific application being
considered.
Functional units can be associated with several functions. A single function can be distributed over several
functional units.
Functions are designated using letters of the alphabet only, as set out in Table 1, Table 2 and Table 3. The use
of the letters I and O, as well as special characters and separators, is not permitted.
st
The 1 -level functions, functions on lower levels and transverse functions are coded in their respective levels
using a single letter. The transverse functions are arranged in the order they are listed in Table 3. A block of n
transverse functions is started and closed by a dot. Elementary functions are two-letter coded. The detail
properties are three letters coded and will be arranged in the order they are listed in Annex D. The detail
properties are separated each other by dots.
The indication systematic can be used either in whole or in part. As a minimum it is recommended to use it from
level 1 to level 5 without the following indication blocks as defined in Annex C and Annex D.
9
prEN 15380-4:2009 (E)
The first level functions are specified using the letters as listed in Table 1.
10
prEN 15380-4:2009 (E)
11
prEN 15380-4:2009 (E)
st rd
5.3.2 Code letters used to designate function groups from the 1 to the 3 level
The functions and function levels are specified using the letters as shown in Table 2.
st rd
Table 2 — Listing of the level functions from the 1 level to the 3 level
Provide appropriate conditions to passenger, Includes equipment for service, comfort and
C
train crew and load climatization
Provide safe and comfortable sitting, lying and Seats, couchettes, measures taken to ensure
C B
standing positions safe standing room
Support straps, handles and rails, occupant
C B B Provide support for standing
restraint systems
C B C * Provide seating possibilities Seats, benches, Stools
C B D * Provide lying possibilities
C C Provide external view
C C B * Ensure outside passenger view By windows
12
prEN 15380-4:2009 (E)
Table 2 (continued)
13
prEN 15380-4:2009 (E)
Table 2 (continued)
14
prEN 15380-4:2009 (E)
Table 2 (continued)
F Provide energy
F B Provide electrical energy for traction
Configure high voltage system with respect to
F B B * Manage electrical energy for traction
the line voltage
Transmission of the power set value from the
F B C Acquire energy demand for traction system
propulsion system to the supply system
F B D * Generate electrical energy for traction on board
F B E * Collect electrical energy for traction Energy collection via pantograph
F B F * Transform electrical energy for traction Transformer and input converter (rectifier)
Distribution facility for parallel intermediate
F B G * Distribute electrical energy for traction
circuits
F B H Store electrical energy onboard for traction Fly-wheel system or double-layer capacitors
Dissipate losses of electrical traction energy Cooling systems for transformer and input
F B J
provision converter
F C Provide electrical energy for auxiliaries
F C B * Manage electrical auxiliary energy provisioning Configure the auxiliary power supply system
Adapt electrical auxiliary energy
F C C *
provisioning according to load
Generate electrical energy for auxiliaries on
F C D diesel-electric generated auxiliary power
board
F C E * Collect electrical auxiliary energy workshop supply
Transform electrical energy to auxiliary Energy transformation from the line voltage
F C F *
energy to 3AC auxiliary supply voltage
Distribution facility in a train including
F C G * Distribute electrical auxiliary energy
protection devices contactors etc.
F C H * Store electrical auxiliary energy Energy storage with battery
Dissipate losses of electrical auxiliary energy
F C J Cooling system for the auxiliary converter
provision
15
prEN 15380-4:2009 (E)
Table 2 (continued)
16
prEN 15380-4:2009 (E)
Table 2 (continued)
17
prEN 15380-4:2009 (E)
Table 2 (continued)
18
prEN 15380-4:2009 (E)
Table 2 (continued)
19
prEN 15380-4:2009 (E)
Table 2 (continued)
20
prEN 15380-4:2009 (E)
Transverse functions affect most of the level 2 and level 3 functions of the FBS at the same time. So they will
not be inserted in the FBS as subfunctions of the functions; they are not part of the FBS. The requirements
related to these transverse functions for a given function will have an attribute stating the relationship.
In a FRS dedicated paragraphs for these transverse functions describing the requirements associated to them
should be integral part of it.
21
prEN 15380-4:2009 (E)
1 2 3
U Display information
22
prEN 15380-4:2009 (E)
Table 3 (continued)
Level Transverse function description / remark
1 2 3
23
prEN 15380-4:2009 (E)
Annex A
(informative)
To promote a better common understanding of the upper functions, further sub-functions on lower levels are
provided to the user of this standard. It is strongly recommended to use these further sub functions before
defining new sub-functions which are not listed in this Annex. In the cases where this Annex doesn’t provide
any further sub-functions at the relevant level, the table cells are empty.
For the definition of new function terms the rules for creation of function terms as given in Annex G should be
applied.
Carry and protect passengers, train crew and ride comfort is not considered here
B
payload
..............
Manage signalling of fire Management of fire alert (system), fire
B E D
warning (system), notification of fire
B E E * Manage / Provide fire extinguishment
B E E * B manage automatic fire extinguish system
B E E * C Monitor volume of extinguishing agent
B E E * D Provide manual fire extinguish facilities
Provide appropriate conditions to passenger, Includes equipment for service, comfort and
C
train crew and load climatization
..............
Provide support for standing Support straps, handles and rails, occupant
C B B
restraint systems
C B C * Provide seating possibilities Seats, benches, Stools
C B C * B Provide ergonomic seating conditions
C B C * C Provide adjustments of position
C B C * D Provide storage space
C B C * E Provide tables
C B D * Provide lying possibilities
C B D * B Provide ergonomic lying conditions
C B D * C Provide adjustments of lying positions
C B D * D Provide storage space
C C Provide external view
C C B * Ensure outside passenger view By windows
24
prEN 15380-4:2009 (E)
25
prEN 15380-4:2009 (E)
26
prEN 15380-4:2009 (E)
27
prEN 15380-4:2009 (E)
28
prEN 15380-4:2009 (E)
29
prEN 15380-4:2009 (E)
C K B * C punch ticket
C K C * Provide miscellaneous service functions
Provide automatic vending of goods and
C K C * B
services
C K D Count passengers
C L Provide tilting ability tilting ability to improve comfort
C L B * Control tilting
C L B * B detect train position/speed/…
30
prEN 15380-4:2009 (E)
31
prEN 15380-4:2009 (E)
Enable external door opening in emergency mechanical lever with cutout for drive and
while driving door control, but registering opening and
D B N * B
derive signal to train control to start
emergency brake sequence/prevent start
Enable external door opening in emergency mechanical lever to couple out door leaves
D B N * C
while standing from drive, open directly
Reduce the gap between vehicle and as well distance reduction as height
D B P * platform reduction between platform and train floor
level
D B P * B Manage steps Control system for movable steps
D B P * B B Enable steps deployment
D B P * B C Enable step withdrawal
D B P * B D Enable manual step locking
D B P * B E Adapt step height to the platform
Ensure passenger access by external doors
D B Q *
for people with reduced mobility
D B Q * B Manage ramp
D B Q * B B Detect opening request By push button
D B Q * B C Enable ramp deployment Release ramp after opening request
Enable ramp withdrawal Release after weight sensor, light barrier or
D B Q * B D movement detector detected nothing after
defined time
Detect obstacle in ramp Needed current or force is measured. If too
D B Q * B E
high then reverse
Detect obstruction in ramp If malfunction or failure in mechanism/control
D B Q * B F
is diagnosed
32
prEN 15380-4:2009 (E)
33
prEN 15380-4:2009 (E)
F Provide energy
F B Provide electrical energy for traction
Manage electrical energy for traction Configure high voltage system with respect
F B B *
to the line voltage
F B B * B Sense catenary current
F B B * C Sense catenary voltage
F B B * D Configure input energy system
Acquire energy demand for traction system Transmission of the power set value from the
F B C
propulsion system to the supply system
Generate electrical energy for traction on
F B D *
board
Transform fuel cell energy into electrical
F B D * B
energy
F B E * Collect electrical energy for traction Energy collection via pantograph
F B E * B Manage Collection device
Ensure good electrical contact on high
F B E * B B
voltage side
Ensure good electrical contact on current
F B E * B C
return
F B E * C Protect collection devices and catenary
F B E * C B Prevent damage to the catenary
F B F * Transform electrical energy for traction Transformer and input converter (rectifier)
34
prEN 15380-4:2009 (E)
35
prEN 15380-4:2009 (E)
36
prEN 15380-4:2009 (E)
F G C * B C Alternator control
37
prEN 15380-4:2009 (E)
38
prEN 15380-4:2009 (E)
39
prEN 15380-4:2009 (E)
40
prEN 15380-4:2009 (E)
41
prEN 15380-4:2009 (E)
42
prEN 15380-4:2009 (E)
43
prEN 15380-4:2009 (E)
H G Provide diagnostics
H G B * Initiate diagnostics
H G B * B Clear database
H G B * C Create new database
H G B * D Update database
H G B * D B Set event state
H G B * D C Get event state
44
prEN 15380-4:2009 (E)
H G D * E C Read failure
H G D * E D Read error
H G D * E E Read protocol event
H G D * F Read condition data Also in UIC format
H G D * F B Read counter
H G D * F C Read parameter
H G D * G Upload events All actions to upload events
45
prEN 15380-4:2009 (E)
H G D * H Delete events
H G D * J Upload / Download parameters All actions to upload/download parameters
Process on diagnostic data Process event and condition data for
H G E *
indication and monitoring
Process condition data Regarding vehicle configurations/operational
H G E * B
limits
H G E * C Monitor train status
Indicate events Indicate events using filters regarding
H G E * D
active/passive, acknowledgement, …
H G E * E Prioritise events
H G E * F Filter and sort events
H H Assist Troubleshooting
H H B Manage events according to their priority
H H C * Allow detailed event analysis
H H C * B Provide cause of event
H H C * C Provide consequence of event
J B D * B Detect obstacles within clearance gauge Capture the external signals by sensors
Signal obstacles within clearance gauge Signal to the external monitoring system the
J B D * C
obstacle
46
prEN 15380-4:2009 (E)
Remove obstacle on the track Protect the bogie and its equipment from
damage caused by a collision with obstacles
J B E lying on top of the rails
Remove snow from the area in front of the
train
Lubricate wheel flange Lubricate wheel flange for excessive wheel
J B F wear and signal wheel flange lubricator
information status
Ride at specified track conditions Allow free motion of the bogies in respect to
the carbody by riding in all configurations of
J B G * the track that can be encountered in the
operation complying with the gauge
concerned
J B G * B Negotiate horizontal curves
J B G * C Negotiate vertical curves
J B G * D Run on a twisted track
J B G * E Run across special trackwork
J B G * F Negotiate S curves
J B H Restrict movement in gangways (Comfort only)
Monitor wheelset bearing status Define criteria, corresponding threshold and
J B J * response time to define necessity of
maintenance or operating measures
Detect hot axle box bearing temperature Detect unusual temperature increase of an
J B J * B
axle box
Signal hot axle box bearing temperature Send to the driver reliable information or alert
message in order to trigger a speed
J B J * C
reduction or a stop according to heating
values
J B K * Monitor gearbox status
J B K * B Detect gear box hot oil temperature
J B K * C Signal gear box hot oil temperature
...
J C Transmit forces
J C B * Transmit longitudinal forces
Transmit longitudinal forces at secondary Transmit traction, braking and shunting effort
J C B * B
level between carbody and bogie frame
Transmit longitudinal forces at primary level Transmit traction, braking and shunting effort
J C B * C
between bogie frame and wheelset
Transmit longitudinal forces at track level Transmit traction, braking and shunting effort
J C B * D
between wheelset and track
J C C * Transmit transversal forces
Transmit transversal forces at secondary Transmit transversal effort (curve, trackwork,
J C C * B level track irregularity) between carbody and bogie
frame
47
prEN 15380-4:2009 (E)
Transmit transversal forces at primary level Transmit transversal effort (curve, trackwork,
J C C * C track irregularity) between bogie frame and
wheelset
Transmit transversal forces at track level Transmit transversal effort (curve, trackwork,
J C C * D
track irregularity) between wheelset and track
J C D * Support vertical dynamic and static load
Support vertical dynamic and static load at Transmit vertical load (curve, track
J C D * B secondary level irregularity, trackwork, passenger load)
between carbody and bogie frame
Support vertical dynamic and static load at Transmit vertical load (curve, track
J C D * C primary level irregularity, trackwork, passenger load)
between bogie frame and wheelset
Support vertical dynamic and static load at Transmit vertical load (curve, track
J C D * D track level irregularity, trackwork, passenger load)
between wheelset and track
Transmit traction and brake effort Transfer the mechanical torque/force from
J C E * the vehicle to the track and vice versa during
traction and braking condition
J C E * B Transmit traction forces to the rail
J C E * C Transmit torque to the motor in electric brake
Transmit reaction forces of the motor on its
J C E * D
support
Transmit reaction forces of the gearbox on its
J C E * E
support
J C E * F Transmit electromagnetic brake effort
Limit x-y-z acceleration Assessment of the ride characteristics "ride
quality" of the vehicle in conformity with the
J D EN 14363 (or UIC 518)
Assessment of the passenger comfort in
conformity with EN 12299 (or UIC 513)
Limit acceleration in interior for running
J D B *
quality and passenger comfort
J D B * B Limit y acceleration
J D B * C Limit z acceleration
J D B * D Limit x acceleration
Integrate the vehicle into the complete also trainset or vehicle (smallest unit)
K
system railway
..............
Ensure data interface to trackside signalling
K D B
system
K D C * Provide train to ground communication
48
prEN 15380-4:2009 (E)
49
prEN 15380-4:2009 (E)
Annex B
(informative)
Figure B.1 is a schematic representation that shows how functional structure and product structure relate to
one another and indicates the interaction between the functional-structure perspective specified in EN 15380-4
and the product-structure view in EN 15380-2.
Using this approach, the functional structure of a vehicle can be created without having to specify its technical
realisation in any detail. The resulting structure can then be used, for instance, to conduct initial (functionally
related) reliability and safety analyses.
As the design phase proceeds, the specified functions are assigned to definite components.
It should be noted that several functions can be assigned to a single component and that a single function can
be realised by several different components. It is therefore particularly important that all relevant
interrelationships are taken into account if the perspective from which the system is viewed (functional aspect
or product aspect) is changed.
It should also be noted that field data for RAMS / LCC analyses are always assigned to the component
structure (in the form of a quality parameter such as a failure rate). If certain data need to be assigned to the
functional structure as part of a quantitative functional analysis, it is important to realise that the sum of the
quantitative data is not necessarily equal to the corresponding value for the overall system (as one component
can perform several functions and vice versa). For example, the sum of the life-cycle costs of the individual
functions (systems) will not normally equal the life-cycle cost of the overall function (i.e. the vehicle).
As the structuring set out in this standard allows properties to be assigned to functions, appropriate coding
allows users to carry out very specific analyses (e.g. thermal load analyses, analyses in terms of specific
passenger groups, etc.).
50
prEN 15380-4:2009 (E)
The product structure results from the physical implementation of the functional structure
Figure B.1 — Interrelation between function breakdown structure according to EN 15380-4 and product
breakdown structure according to EN 15380-2
51
prEN 15380-4:2009 (E)
Annex C
(informative)
Elementary functions
The applicable elementary functions are listed in Table C.1 and correspond to those in EN 61346-2.
Supplementary terms have been introduced wherever the functions in EN 61346-2 were too general. Table 4
below shows the relationship between the code letters in Table 1 of EN 61346-2 and the relevant ‘Examples of
terms describing purpose or task of objects and functions’ that are listed in column 3 of Table C.1.Each term
has been allocated a code letter that is listed in Table C.1 in the column headed ‘Code letter according to EN
15380-4. Any extension or supplement to EN 61346-2 is marked as such in column 4 of Table C.1 by an
asterisk. Functional units that serve as examples of the relevant elementary functions can be found in
EN 61346-2 and have not been transferred into this standard.
Table C.1a — Elementary functions for level 3 based on EN 61346-2 (sorted by code letter)
Code letter according to EN 61346-2 Code letter according to EN 61346-2
Code letter according to EN 15380-4 Code letter according to EN 15380-4
Elementary function Elementary function
B Converting an input variable (physical property, F C Preventing
condition or event) into a signal for further
processing F D Protecting
B D Sensing F H Insulating * x
B F Counting * x F K Lining * x
52
prEN 15380-4:2009 (E)
K A Switching R J Setting/Adjusting * x
53
prEN 15380-4:2009 (E)
V Q Stirring W P Rolling * x
V R Surface treatment W Q Feeding * x
V S Wrapping * x W R Drawing / pulling * x
W Guiding or transporting energy, signals, material or W S Pressing / Compressing * x
products from one place to another
X Connecting objects
W A Conducting / Transferring * x
X A Connecting
W B Distributing
X B Coupling
W C Guiding
X C Jointing
W D Positioning
W E Transporting
54
prEN 15380-4:2009 (E)
Table C.1b — Elementary functions for level 3 based on EN 61346-2 (sorted alphabetically by name)
Code letter according to EN 61346-2 Code letter according to EN 61346-2
Code letter according to EN 15380-4 Code letter according to EN 15380-4
Elementary function Elementary function
F A Absorbing W B Distributing
M A Actuating R H Dosing * x
P A Alerting / Warning W G Draining / emptying * x
T A Amplifying W R Drawing / pulling * x
F F Armouring M B Driving/Moving * x
G A Assembling V E Drying
U A Bearing T J Expanding
R A Blocking W Q Feeding * x
U B Carrying/Securing * x W J Filling * x
T D Casting V F Filtering
W M Charging * x U F Fixing / Fastening * x
V B Cleaning T K Forging
K B Closed-loop controlling T F Forming
K E Closing G E Fractionating
Q B Closing G D Generating
V A Coating T L Grinding
P B Communicating F B Guarding
T E Compressing W C Guiding
W A Conducting / Transferring * x V G Heat treating
X A Connecting E B Heating
K G Controlling/Actuating * x U C Holding
E A Cooling / Heat dissipation * x S A Influencing
B F Counting * x P E Informino * x
Q D Coupling F H Insulating * x
G B Crushing X C Jointing
T G Cutting R D Limiting
R B Damping F K Lining * x
P C Displaying G H Mixing
55
prEN 15380-4:2009 (E)
Q A Opening U D Supporting
K D Opening (control circuits) V R Surface treatment
V H Packing K A Switching
W D Positioning Q C Switching
V J Preconditioning K F Synchronising
P G Presenting K H Testing/Comparing * x
56
prEN 15380-4:2009 (E)
57
prEN 15380-4:2009 (E)
Annex D
(informative)
D.1 General
The achievement of certain functions often depends on properties (demands) the function carrier has to meet.
That’s the motivation to predefine a list of properties that shall be used before redefining or adding other
properties or attributes.
The arrangement of detail properties has to follow the intention to define the functions from abstract level to
detailed level. Also the definition of functional requirements has to start with more common specifications and
has to be made more precisely aiming for detailed specifications.
The following arrangement shows 5 classes of detail properties; further detailed classification of detail
properties is shown in Table 1; the detail classifications could be used as support for structuring and analysing
tasks. It is shown beyond how the properties listed in Table D.2 could be arranged to the proposed classes of
detail properties; the classifications are listed as follows:
1. Relevance for superordinated (higher level) functional goals (based on customers/ operators -/ or interoper-
abilty requests or other design features);
2. Tolerance against ambient conditions, influences and interferences from operating and surroundings (What
is influencing the function carrier;
3. Relevance to target group /target object /interaction (is the function relevant fort he target group because of
special demands);
4. Impact characteristics of the function associated mechanism with regard to the function carrier
(classification of impact characteristics);
NOTE The two classifications mentioned before are used for detailing the properties of the function carriers within the
development process. Functions are described more precisely by using detail properties and attributes in general; these
properties are related to functional goals e.g. superior goals like design. As the example below shows the same attribute
can be used for different classes / aspects of describing detail properties:
58
prEN 15380-4:2009 (E)
Figure D.1 — Precept detail properties indication in combination with the function group indication
59
prEN 15380-4:2009 (E)
A B C D E
Stability/tolerance against
Impact characteristics of the
ambient conditions, Characteristics of the
Relevance for superordinated Relevance to target group / function associated
influences and interferencies physical construction/ design
(higher level) functional goals target object /interaction mechanism with regard to the
from operating and features/ interfaces
function carrier
surroundings
60
prEN 15380-4:2009 (E)
A B C D E
Stability/tolerance against
Impact characteristics of the
ambient conditions, Characteristics of the
Relevance for superordinated Relevance to target group / function associated
influences and interferencies physical construction/ design
(higher level) functional goals target object /interaction mechanism with regard to the
from operating and features/ interfaces
function carrier
surroundings
Operator needs/ requests O tribological stress (abrasion/ V Software related realisation of S pneumatical P Operational, process, control O
(spec. operating tasks/field, friction) functions technology parameters
maintenance cycles, range, (realtime, continuous, tunable,
interfaces to infrastructure, adjustable.)
voltage supply, ...)
Performance and quality of P weather and operating W function carrier (e.g. hardware) T radiation/ thermal R Performance characteristics P
function/ construction conditions/climate (incl.
(including aspects like stability, Thermal/aerodynamical/
redundancy, fall back-levels hydraulical load or forces)
and performance aspects like
stereo, power ...)
Cleaning R function (directly/indirectly U software-/signal-/ data-based S Reliability/availability requests R
effecting)
Safety/ safety at work/ fire S interaction (between functions) Z tribological/ abrasion- T Safety requests S
protection mechanical
Environmental impact/ U Integrated transversal function/ T
sustainability choice of function characteristics
materials/ ecological (cooling / voltage
objectives, …) transformation/ control
parameters/…)
61
prEN 15380-4:2009 (E)
Annex E
(informative)
Table E.1 below shows the functional structure of the main functional group F with the sub-function ‘Provide electrical energy for traction’. The initial focus is
on the main functions for transferring power between the contact wire or rail and the vehicle without specifying the detailed technical realisation of the
functional unit.
Functions, transverse functions, elementary functions detail properties and attributes are entered in the sequence given in 5.3 and Annex A, Annex C and
Annex D. It is important that this sequence is observed if incorrect machine processing and machine evaluation of data fields is to be avoided. In contrast,
attribute designators can be specified in any order within the corresponding column, though if the information is to be machine processed the attribute code
letters shall be separated on additional lines. Table E.1 shows the general procedure to specify a function down to the attributes and the transition to the
function carrier, listed in EN 15380-2. This example is not exhaustive.
The ‘Product structure EN 15380-2’ column is included to make clear the interrelationships shown schematically in Figure B.1.
Table E.1 — Example illustrating the structuring of a functional group (functional aspect / pantograph)
Transverse Transverse
Function Function Function Function Detail Properties
Function Function
Level Level Level Level Function (level 1 to Product structure
Level Level
level 5) (EN 15380-2)
1 2 1 2 3 3 1 2 3 4 5 A B C D E
62
prEN 15380-4:2009 (E)
Transverse Transverse
Function Function Function Function Detail Properties Function (level 1 to Product structure
Function Function
Level Level Level Level level 5) (EN 15380-2)
Level Level
Power measurement
F B B W A B O O Sense catenary current GE
(Current)
Power measurement
F B B W A C O O Sense catenary voltage GE
(Voltage)
.. .. .. .. ..
Generate electrical
Generator (diesel
F B D W E O, P E, M R energy for traction on FC
generator)
board
Spring-loaded contact
strips, supported by a
static speed-
Ensure good electrical independent contact
F B E W E B B O V E G, O contact on high voltage FB force (pantograph
side cylinder,
aerodynamically
optimised pantograph
design)
63
prEN 15380-4:2009 (E)
Annex F
(normative)
Each function shall be considered regarding its generality. The most general functions are located at level 1.
At this level, at least on level 2 the main functions as listed in the TSI rolling stock shall be covered. However it
is not necessary that the correspondence between the two sets of functions is “one to one”
These functions may be split into sub-functions, which may be further split into sub-functions of the next lower
level.
To determine which level a function has to be assigned, in order to meet the adequate level within the function
hierarchy, the following rules apply:
Rule 1:
At level 1 the focus of the functional domain shall be the intended functional purpose, not the means of
realization.
NOTE Several verbs and object complements may be used in the description of such a functional area.
Rule 2:
Specification of a first level function is called Main Rolling Stock Requirement Specification.
The preferred level for definition of a FRS document is level 2 but there could be FRS for level 3 functions.
Rule 3:
If an application of a function on level 2 or level 3 is not influenced by the target group of the function then
there is no criterion to extend the number of functions.
Rule 4:
Within a given FBS level, functions shall not overlap.
Rule 5:
The functions shall be defined in order to reduce the interfaces between themselves particularly at level 2 and
level 3.
Rule 6:
A function shall be defined independently from the architecture.
Rule 7:
A function is not a requirement.
NOTE Example for the difference between a function and a requirement: A function is: to accelerate the train, a
2
requirement is: accelerate at 1,5 m/s .
Rule 8:
Each function shall be fully defined by its sub-functions.
Rule 9:
There shall be no space holder functions at level 2 and level 3. Each function shall have more than one sub-
function (otherwise the sub-function is the function on the level above).
64
prEN 15380-4:2009 (E)
Annex G
(informative)
G.1 General
To ensure an unambiguous definition of each function it is necessary to define rules for creating the function
terms and their abbreviation. These processes are realized in English language only independent from the
mother tongue of this standard’s user.
Rule 1:
Each function shall consist of at least one verb in its verbal form and an object complement.
Rule 2:
The verb is defined in a dictionary. Preferred verbs are: to provide, to enable, to ensure, to command, to
access.
Rule 3:
The function name shall start with the verb.
Rule 4:
Negative definition shall be avoided.
Rule 5:
The function name shall be unambiguous.
Rule 6:
Function names shall have an unambiguous abbreviation unless it is unavoidable.
EXAMPLE 1: communication -> com
EXAMPLE 2: command -> cmd
The identifier of the metadata element is a string of characters, based on the English language. The identifier
shall be unambiguous in the document management context.
T he id e nt ifier is composed of one or more terms, each starting with an upper case letter, followed by lowe
r-case letters. Characters are limited to upper case and lower-case Latin letters (A . Z, a . z). The differ
ent te rm s are c o nc a te n at e d wi t ho ut a n y i nt erm ed i at e character.
65
prEN 15380-4:2009 (E)
The information model provides entities with associated attributes. In order to reflect the different context-
dependent semantics , t he metadata identifier is in most cases composed of the entity name followed by the
relevant attribute name, concatenated without any intermediate character. Each term starts with an upper-ca
s e l et te r.
Rule 1:
If there are common international abbreviations (speed: v, electric: el, acceleration: a, force: f, passenger: pax,
transmit: tx, …) these shall be used . The series of ISO 31 shall apply.
Rule 2:
Binding words like and, or, with, ... shall be suppressed.
Rule 3:
For terms consisting of different words each individual word will be treated according the defined rules.
Rule 4:
For the same word always the same abbreviation shall be used even if it is used in different meanings.
Whenever possible different terms shall be used for different meanings instead.
Rule 5:
Words not covered by rule 1 and having less than 6 letters shall not be abbreviated.
EXAMPLE Light -> Light
Rule 6:
Each function shall be abbreviated by the first letter and the following 2 consonants of each word. The words
are concatenated using capital letter.
EXAMPLE Ensure -> Ens, communication -> com, command >cmd
Rule 7:
If there is no unique or clear identification possible with rule 6 also the 3rd consonant shall be used.
EXAMPLE Provide -> Prvd, Inside -> Insd, Supply -> Sply, Access -> Accs, Accelerate -> Accl, Accumulate -> Accm
Rule 8:
If there is no unique or clear identification possible with rule 7 additionally the first different consonant of the
word shall be used.
EXAMPLE Presence-> Prsnc (Person->Prsn), Acoustic -> Acstc (acustom -> acstm), Protect -> Prtct (protocol ->
prtcl).
Rule 9:
If there is no unique or clear identification possible with rule 7 or rule 8 additionally to rule 6 the first 1 or two
vowels /additionally to rule 7 the first vowel of the word shall be used.
Listing of function term abbreviations
Table G.1 lists all function term abbreviations of functions from level 1 to level 5 as shown in this document.
66
prEN 15380-4:2009 (E)
67
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
68
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
69
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
70
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
71
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
72
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
73
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
74
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
75
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
76
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
77
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
78
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
E B E * C CnctSnglSmpCnsts Connect signals, utilities and power service lines for consists
79
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
80
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
81
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
82
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
83
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
G B C * E AcqrDmnDynBrakeFBrakeCtrl Acquire demand for dynamic brake force from brake control
84
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
G B G * B ConvElNrgTrcnFViceVersa Convert electrical energy into traction force and vice versa
G B G * C ConvFluidNrgTrcnFViceVisa Convert fluid energy into traction force and vice versa
G B G * D ConvMechNrgTrcnFViceVersa Convert mechanical energy into traction force and vice versa
G B G * E ConvChemNrgTrcnFViceVersa Convert chemical energy into traction force and vice versa
85
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
86
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
87
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
88
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
89
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
90
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
H E B * F PrvtMstrCnflctMoreThanOneActCab Prevent master conflict due to more than one activated cab
91
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
H E C * C C Trnsmt Transmit
H E C * D C Trnsmt Transmit
92
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
93
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
94
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
95
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
96
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
97
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
98
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
99
prEN 15380-4:2009 (E)
Level Level
Abbreviation Function (level 1 to level 5)
1 2 3 4 5
100
prEN 15380-4:2009 (E)
Bibliography
[1] TSI 02/735/EC Commission Decision of 30 May 2002 concerning the technical specification for
interoperability relating to the rolling stock subsystem of the trans-European high-speed rail system
referred to in Article 6 (1) of Directive 96/48/EC
[2] CLC/TR 50126-3, Railway Applications — The specification and demonstration of reliability,
availability, maintainability and safety (RAMS) — Part 3: Guide to the application of the EN 50126-1 for
rolling stock RAM
101