IEEE Recommended Practice for [621092]

IEEE Recommended Practice for
Functional Testing of a
Communications-Based Train
Control (CBTC) System
IEEE Vehicular Technology Society
Sponsored by the
Rail Transportation Standards Committee

IEEE
3 Park Avenue
New York, NY 10016-5997
USA

16 September 2011 IEEE Std 1474.4™-2011

IEEE Std 1474.4™-2011
IEEE Recommended Practice for
Functional Testing of a
Communications-Based Train
Control (CBTC) System
Sponsor
Rail Transportation Standards Committee
of the
IEEE Vehicular Technology Society
Approved 16 June 2011
IEEE-SA Standards Board

Abstract: A preferred approach for functional testing of a communications-based train control
(CBTC) system, based on the CBTC system design and functional allocations as defined in
IEEE Std 1474.3™-2008, is established in this recommended practice.
Keywords: automation, communication, IEEE 1474.4, signaling, testing, train control

/g120

The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA

Copyright © 2011 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 16 September 2011. Printed in the United States of America.

IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and Electronics
Engineers, Incorporated.

PDF: ISBN 978-0-7381-6667-4 STD97118
Print: ISBN 978-0-7381-6668-1 STDPD97118

IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html .
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior wr itten permission
of the publisher.

IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of
the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus
development process, approved by the American National Standards Institute, which brings together volunteers
representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the
Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote
fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy
of any of the information or the soundness of any judgments contained in its standards.
Use of an IEEE Standard is wholly voluntary. The IEEE discl aims liability for any personal injury, property or other
damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly
resulting from the publication, use of, or relian ce upon this, or any other IEEE Standard document.
The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly
disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific
purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents
are supplied “ AS IS .”
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase,
market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint
expressed at the time a standard is approved and issued is subject to change brought about through developments in the
state of the art and comments received from users of the st andard. Every IEEE Standard is subjected to review at least
every five years for revision or reaffirmation, or every ten years for stabilization. When a document is more than five
years old and has not been reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to
conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are
cautioned to check to determine that they have the latest edition of any IEEE Standard.
In publishing and making this document available, the IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other
person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or
her independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the
advice of a competent professional in determining the appropriateness of a given IEEE standard.
Interpretations: Occasionally ques tions may arise regarding the meaning of porti ons of standards as they relate to
specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate
action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is
important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason,
IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant
response to interpretation requests except in those cases where the matter has previously received formal consideration.
A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual
shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be
relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an
individual presenting information on IEEE standards shall make it clear that his or her views should be considered the
personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation
with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Recommendations to change the status of a stabilized standard should include a
rationale as to why a revision or withdrawal is required. Comments and recommendations on standards, and requests
for interpretations should be addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854-4141
USA
Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute
of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center.
To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood
Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for
educational classroom use can also be obtained through the Copyright Clearance Center.

Introduction
This introduction is not part of IEEE Std 1474.4-2011, IEEE Recommended Practice for Functional Testing of a
Communications-Based Train Control (CBTC) System.
The characteristics of a communications-based train control (CBTC) system are very different from that of
a more conventional track circuit-based signaling/train control system and these characteristics can have a
fundamental impact on the approach to system testi ng and verification. CBTC field test requirements in
particular can be significantly more onerous in a resignaling application than signaling for a new line,
primarily because of the need to maintain revenue operations du ring the migration to the new CBTC
system, which in turn results in track access limitations.
Against this background, this document provides a recommended practice for the functional testing of
CBTC systems, from factory tests thro ugh test track tests to field tests, with a goal of maximizing the
effectiveness and efficiency of the test procedures at each stage. This recommended practice considers
CBTC performance and functional requirements as defined in IEEE Std 1474.1™-2004 and the CBTC
recommended system design and functional allo cations as defined in IEEE Std 1474.3™-2008.a
Notice to users
Laws and regulations
Users of these documents should consult all applicab le laws and regulations. Compliance with the
provisions of this standard does not imply compliance to any applicable regu latory requirements.
Implementers of the standard are responsible for observing or referring to the applicable regulatory
requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
This document is copyrighted by the IEEE. It is ma de available for a wide variety of both public and
private uses. These include both use, by reference, in laws and regulations, and use in private self-
regulation, standardization, and the promotion of engineering practices and methods. By making this
document available for use and adoption by public aut horities and private users, the IEEE does not waive
any rights in copyright to this document.

a Information on references can be found in Clause 2.
iv
Copyright © 2011 IEEE. All rights reserved.

Updating of IEEE documents
Users of IEEE standards should be aware that these documents may be superseded at any time by the
issuance of new editions or may be am ended from time to time th rough the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigend a, or errata then in effect. In order to determine whether
a given document is the current edition and wh ether it has been amended through the issuance of
amendments, corrigenda, or errata, visit the IEEE Standards Association web site at
http://ieeexplore.ieee.org/xpl/standards.jsp , or contact the IEEE at th e address listed previously.
For more information about the IEEE Standards Association or the IEEE standards development process,
visit the IEEE-SA web site at http://standards.ieee.org .
Errata
Errata, if any, for this and all other standards can be accessed at the following URL:
http://standards.ieee.org/reading/ieee/updates/errata/index.html . Users are encouraged to check this URL
for errata periodically.
Interpretations
Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/
index.html .
Patents
Attention is called to the possibility that implementa tion of this recommended practice may require use of
subject matter covered by patent rights. By publi cation of this recommended practice, no position is taken
with respect to the existence or validity of any patent rights in connection therewith. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims or determining whether an y licensing terms or
conditions provid ed in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this recommended practice are expressly
advised that determination of the valid ity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from the IEEE Standards
Association.

v
Copyright © 2011 IEEE. All rights reserved.

vi
Copyright © 2011 IEEE. All rights reserved. Participants
At the time this recommended practice was submitted to the IEEE-SA Standards Board for approval, the
Communications-Based Train Control Working Group had the following membership:
Alan Rumsey , Chair
Norman May , Vice Chair

Frederick Childs
Michael Crispo
Stephane Dubois
Tom Eichorn
Nicolas Estivals
Steve Farrell
Nabil Ghaly Harvey Glickenstein
Kenneth Karg
Andrei Kukushkin
John LaForce
Bob MacDonald
Dave Male
Lou Sanders
George Simon
Jeffrey Smith
Carl Thompson
David Thurston
Robert Walsh
Firth Whitwam

The following members of the ind ividual balloting committee vo ted on this recommended practice.
Balloters may have voted for approva l, disapproval, or abstention.

Ronald Birkelbach
Stephane Bois
William Byrd
Frederick Childs
Keith Chow
Timothy Cramond
Michael Crispo
Douglas Dorr
Jeff Eilenberg
Christian Girard
Harvey Glickenstein
David Gregson
Randall Groves
James R. Hoelscher
Werner Hoelzl
Ronald W. Hotchkiss
Paul Jamieson
Andrew Jones
Kenneth Karg
Piotr Karocki
Walter Keevil
Thomas Kurihara
Norman May
Daniel McFadden
Michael S. Newman
William Petit
D. Phelps Edward Rowe
Alan Rumsey
Bartien Sayogo
Gil Shultz
Alexander Sinyak
Jeffrey Sisson
James Smith
David Thurston
Gary Touryan
John Vergis
Robert Walsh
Stephen Webb
Jian Yu

When the IEEE-SA Standards Board approved this recommended practice on 16 June 2011, it had the
following membership:
Richard H. Hulett , Chair
John Kulick , Vice Chair
Robert M. Grow , Past Chair
Judith Gorman , Secretary

Masayuki Ariyoshi
William Bartley
Ted Burse
Clint Chaplin
Wael Diab
Jean-Philippe Faure
Alexander Gelman
Paul Houzé Jim Hughes
Joseph L. Koepfinger*
David J. Law
Thomas Lee
Hung Ling
Oleg Logvinov
Ted Olsen
Gary Robinson
Jon Walter Rosdahl
Sam Sciacca
Mike Seavey
Curtis Siller
Phil Winston
Howard L. Wolfman
Don Wright
*Member Emeritus

Also included are the following nonvoting IEEE-SA Standards Board liaisons:

Satish K. Aggarwal, NRC Representative
Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative

Lisa Perry
IEEE Standards Program Manager, Document Development

Michael D. Kipness
IEEE Standards Program Manager, Technical Program Development

vii
Copyright © 2011 IEEE. All rights reserved.

Contents
1. Overview …………………………………………………………………………………………………….. ………………………….. 1
1.1 Scope ………………………………………………………………………………………………………………………………… 1
1.2 Purpose ……………………………………………………………………………………………………………………………… 1
1.3 General …………………………………………………………………………………………………….. ………………………. 1
1.4 Application …………………………………………………………………………………………………. …………………….. 2
2. Normative references………………………………………………………………………………………….. …………………….. 2
3. Definitions, acronyms, and abbreviations ………………………………………………………………………… ………….. 2
3.1 Definitions …………………………………………………………………………………………………. ……………………… 2
3.2 Acronyms and abbreviations ……………………………………………………………………………………. ………….. 2
4. CBTC characteristics and applications…………………………………………………………………………… ……………. 3
4.1 CBTC ch aracteristics…………………………………………………………………………………………. ……………….. 3
4.2 CBTC applications ……………………………………………………………………………………………. ……………….. 4
5. Overall te st process………………………………………………………………………………………….. ……………………….. 4
5.1 General …………………………………………………………………………………………………….. ………………………. 4
5.2 Functional test prerequisites …………………………………………………………………………………. ……………… 6
5.3 Database verification ………………………………………………………………………………………… ………………… 7
6. Factory functional tests………………………………………………………………………………………. ……………………… 8
6.1 Factory integrated system test facility ………………………………………………………………………… …………. 8
6.2 Factory test plan……………………………………………………………………………………………. ………………….. 10
7. CBTC test tr ack functional tests……………………………………………………………………………….. ………………. 22
7.1 CBTC te st track ……………………………………………………………………………………………… ………………… 22
7.2 CBTC test tr ack test plan…………………………………………………………………………………….. …………….. 23
8. Field func tional te sts………………………………………………………………………………………… ……………………… 28
8.1 Field te st plan ……………………………………………………………………………………………… …………………… 28
9. Summary ……………………………………………………………………………………………………… ……………………….. 32

vii i
Copyright © 2011 IEEE. All rights reserved.

IEEE Recommended Practice for
Functional Testing of a
Communications-Based Train
Control (CBTC) System
IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or
environmental protection. Implementers of the standa rd are responsible for determining appropriate
safety, security, environmental, and health practi ces or regulatory requirements.
This IEEE document is made available for use subj ect to important notices and legal disclaimers.
These notices and disclaimers appear in all public ations containing this document and may
be found under the heading “Important No tice” or “Important Notices and Disclaimers
Concerning IEEE Documents.” They can al so be obtained on request from IEEE or viewed at
http://standards.ieee.org/IPR/disclaimers.html .
1. Overview
1.1 Scope
This recommended practice establishes a preferred appro ach for functional testing of a communications-
based train control (CBTC) system.
1.2 Purpose
The purpose of this recommended practice is to define a preferred sequence and extent of off-site and on-
site functional testing for CBTC systems with the objectiv e of maximizing test efficiency and effectiveness.
1.3 General
This recommended practice establishes a preferred approach for functional testing of a CBTC system.
Clause 1 describes the scope and purpose of this recommended practice. Clause 2 lists normative references
that are useful in applying this recommended practice. Clause 3 provides definitions that are either not
1
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
found in other IEEE standards or have been modified for use with this recommended practice. Clause 1
describes the basic characteristics of CBTC systems and typical applications. Clause 5 provides an
overview of the overall test process. Clause 6 provides recommended practices for factory tests, and
Clause 7 provides recommended practices for test track tests. Clause 8 provides recommended practices for
field tests.
1.4 Application
The extent to which this recommended practice would be applicable to a specific CBTC installation/project
should be determined by th e authority ha ving jurisdiction.
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so each referenced document is cited in text and its relationship to this document is
explained). For dated references, only the edition cited applies. For undated references, the latest edition of
the referenced document (including any amendments or corrigenda) applies.
IEEE Std 1474.1™-2004 (Reaff 2009), IEEE Standard for Co mmunications-Based Train Control (CBTC)
Performance and Functional Requirements.1, 2
IEEE Std 1474.3™-2008, IEEE Recommended Practice for Communications-Based Train Control (CBTC)
System Design and Fu nctional Allocations.
3. Definitions, acronyms, and abbreviations
3.1 Definitions
The IEEE Standards Dictionary: Glossary of Terms & Definitions should be consulted for terms not
defined herein.3 See also IEEE Std 1474.1-2004 fo r other CBTC-related definitions.4
3.2 Acronyms and abbreviations
ATO automatic train operation
ATP automatic train protection
ATS automatic train supervision
CBTC communications-based train control

1 IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 0885 4-
4141, USA ( http://standards.ieee.org ).
2 The IEEE standards or products referred to in this clause are trademarks of the Institute of Electrical and Electronic Enginee rs, Inc.
3 The IEEE Standards Dictionary: Glossary of Terms & Definitions is available at http://shop.ieee.org/ .
4 Information on references can be found in Clause 2.
2
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
4. CBTC characteristics and applications
4.1 CBTC characteristics
The primary characteristics of a CBTC system, as defined in IEEE Std 1474.1-2004, include the following:
a) High-resolution train location determina tion, independent of track circuits
b) Continuous, high capacity, bidirectional train-to-ways ide data communications
c) Train-borne and wayside processor s performing vital functions
The influence of these primary characteristics on the fun ctional test process is summarized as follows.
4.1.1 Train location determination, independent of track circuits
With train location determination independent of fixe d-block track circuits, a lternative control strategies
become possible (where movement authority limits ar e not constrained by physical fi xed-block track circuit
boundaries) that should be reflected in the CBTC functional test process. Certain test practices for fixed-
block, track circuit-based signaling systems may no long er be applicable or practicable, and alternative test
procedures are necessary to reflect the specific principl es of operation of CBTC systems.
4.1.2 Bidirectional train-to-wayside data communications
The performance and availability of a geographi cally continuous train-to -wayside and wayside-to-train data
communications network is critical to CBTC operations. Hence, as an element of the system level
functional testing, the network performance and availability (incl uding network stability, data-link
bandwidth, and message latency) should be verified, supported by analysis, as necessary, of worse-case
conditions that cannot be easily duplicated in the factory or in the field.
4.1.3 Train-borne and wayside vital processors
The distributed CBTC wayside and train-borne vital proce ssors that process the train status and control data
and provide continuous automatic train protec tion (ATP), automatic tra in operation (ATO), and automatic
train supervision (ATS) functions are typically highly integrated. As a conseque nce, the final functional
testing can only be performed at a systems level with all major CBTC su bsystems operational and with
multiple vehicles operating. CBTC systems also typi cally include significant levels of equipment
redundancy to achieve the h igh system availability required . The need to verify th e overall stability of such
a distributed computer system and the need to verify switchover capabilities between redundant sets of
wayside and/or train-borne CBTC equipment also should be reflected in the functional test process.
CBTC systems/g650typical of other advanced tech nology systems/g650are software/database driven. In such
complex software-based systems it is important to understand that whereas the majority of software
development often occurs prior to field testing, the software development process does not end until the
system is verified to be operating correctly in the field. Multiple software releases are also typically
required in a given application (specifically for co mplex cut-overs in a resigna ling application) resulting in
a need for a defined level of regression testing following each software update.
3
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
4.1.4 Application-specific requirements
The correctness of application-specific data (i.e., infrastructure data, such as curves, grades, station
locations, etc., and train-specific data, such as braking rates and response times, etc.) and that this data has
been correctly implemented within the system da tabases, should also be verified as an element of the
functional test process.
When resignaling with a CBTC system, application-specific external (legacy) equipment interfaces,
application-specific operating modes, and application-specific func tional requirements are common. This
can result in application-sp ecific designs that should be reflected in the application-specific functional test
process. To exploit the operationa l capabilities of CBTC systems, the design of a CBTC system is often
integrated with the design of other fixed operating el ements of a rapid transit system such as traction power
systems, tunnel and station ventilation systems, passenger information and security systems, and backbone
communications networks, for example. In addition, the designs of the onbo ard train location/speed
measurement subsystems are also often application-specific due to vehicle-specific interfaces. As such, the
performance of these appli cation-specific designs should be verifi ed through the functional test process.
4.2 CBTC applications
The CBTC functional test process for resignaling ap plications can be significantly more onerous than
signaling new lines, primarily because of the need to maintain revenue operations and the integrity of the
existing signaling system during the migration to the new CBTC system, which in turn results in track
access limitations and the need to support mixed modes of operation. In addition, the specific
signaling/train control system being replaced is typ ically different from one application to another.
NOTE—For the purposes of this recommended practice, and for consistency with IEEE Std 1474.3-2008, the CBTC
system is assumed to interface with an external separate interlocking subsystem, which is more common for resignaling
applications. As a consequence, this recommended practice does not include testing of interlocking functions, but does
include the testing of functional interfaces between CBTC and external interlockings.5
5. Overall test process
5.1 General
This recommended practice addresses system-level functional testing only, as an integr al element of the
overall test process, to verify in the factory, on a CBTC test track, and in the field that the CBTC system
functional requirements have been satisfied, as highlighted in Figure 1.
This recommended practice does not address unit tes ting at a module level, subsystem tests, hardware
qualification tests, hardware post-installation check-o ut testing, and data comm unications coverage testing,
which are all necessary prerequisites to system-level functional testing. Trial operations,
reliability/availability/maintainability demonstrations and other customer-specific final acceptance testing
are also not included.
If a function/sub-function has been previously verified in one applica tion, it may not be necessary to retest
the function/sub-function in a subsequent application, based on consid eration of any differences in
hardware, software, sy stem databases, and operating environment.

5 Notes in text, tables, and figures of a standard are given for information only and do not contain requirements needed to impl ement
this standard.
4
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System

Figure 1 —CBTC system design/verification
IEEE Std 1474.1-2004 defines the CBTC system-level functional requirements addressed by this
recommended practice.
A CBTC system comprises the following major subsystems:
a) CBTC ATS equipment
b) CBTC wayside equipment
c) CBTC train-borne equipment
d) CBTC data communications equipment
The recommended allocation of ATP, ATO, and ATS sub-functions to the preceding major CBTC
subsystems is defined in IEEE Std 1474.3-2008.
A CBTC system also interfaces to ex ternal interfaces such as the following:
/g127 Interlockings and secondary train detection systems
/g127 Train subsystems (propulsion/brak ing systems, train doors)
/g127 Platform edge doors (if provided)
/g127 Highway grade crossing warning devices (if provided)
/g127 Passenger information systems (if provided)
/g127 User interfaces
/g127 Other external interfaces as may be specified by the authority having jurisdiction
5
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
Figure 2 summarizes the recommended functional test process to verify that all of these functional
requirements have been satisfied.

Figure 2 —Functional test process
The objective of the factory functional testing should be to verify to the maximum extent possible that all
of the CBTC functional requirements have been satisfied. When testing a specific funct ional requirement, if
the test outcome cannot be affected by factors outside of the test environment, it should not be necessary to
have to repeat this test on the test track or in the field, i.e., such requirements should be fully verified
through the factory testing. Where a factory test outcome is depend ent upon simulated interfaces to the
CBTC system, it would generally be necessary to repeat such tests either on the test track or in the field
with the real interfaces, depending on the complexity of the interface and the ability to simulate the
interface in the factory.
5.2 Functional test prerequisites
The following subclauses define the prerequisites to system-level functional testing.
5.2.1 Design baseline and configuration control
The current design baseline in terms of documented system functional requirements and system design
should be available. A configuration control management plan should also be in place to include a
definition of regression test requirements following changes to the CBTC system.
6
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
5.2.2 Subsystem testing
All lower-level testing at the subsystem level should be completed. In addition, prior to test track and field
functional testing, the post installation check-out of all applicable hardware should be completed, to include
both wayside and train-borne CBTC equipment.
For the CBTC data communications subsystem, the network performance and availability should be
verified, supported by analysis, as necessary, of worse-case conditions that cannot be easily duplicated in
the factory or in the field.
5.2.3 Documentation requirements
Documentation requirements with respect to system-level test plans (including migrati on strategy, extent of
testing, and responsibilities of all parties involved in the test pr ocess), test procedures, pass/fail criteria, and
test results should be defined.
5.2.4 Simulation facility verification
Any simulation facilities that are to be used for factory or CBTC test track testing should be verified as
being appropriately representative of the equipment and interfaces being simulated.
5.3 Database verification
Correct functioning of a CBTC system is critically dependen t upon application-sp ecific databases that
include infrastructure data, train data, and CBTC data. Infrastructure data and vehicle data is specific to the
particular application. CBTC data is specific to the particular CBTC system design for that application.
5.3.1 Verifying infrastructure data
Any infrastructure input data required by the CBTC system such as a lignment data (location and value of
all grades, curves, civil speed limits, etc.), track layout (location of switches and terminal track
configuration), and location of all stations and platform st opping positions, for example, should be verified
against appropriate survey data at a level of precision appropriate to the application-specific CBTC
performance requirements. The party responsible for verifying infrastructure data should be clearly
identified.
5.3.2 Verifying train data
Any train-specific input data required by the CBTC system such as acceleration and deceleration rates and
equipment reaction times, for example, should be verified against certified train characteristics at a level of
precision appropriate to the application-specific CBTC performance requirements. This should specifically
include verifying any train-related assumptions in the CBTC safe-braki ng model. The party responsible for
verifying train data shou ld be clearly identified.
7
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
5.3.3 Verifying CBTC data
Application specific CBTC data, such as the required location of any wayside devices used to provide an
absolute position reference (e.g ., transponder locations) should be verified as an element of the CBTC
system design.
5.3.4 Verifying CBTC databases
The infrastructure, train-specific, and application-specific CBTC data also should be verified as having
been correctly implemented in the CBTC databases (correspondence check). This would also include, for
example, verifying that any wayside devices used to provide an absolu te position reference (e.g.,
transponders) have been correctly installed at the required locations, within the CBTC system design
tolerances.
While CBTC databases can be partially verified to a level to support factory an d test track functional
testing, full verification of CBTC databa ses would require testing in the field.
6. Factory functional tests
6.1 Factory integrated system test facility
6.1.1 Capabilities
A factory integrated system test facility should include the following capabilities:
a) Testing every CBTC function/sub-func tion with a goal of eliminating CB TC test track and field tests
where practical, or providing a high degree of confidence that such tests will be completed
successfully
b) Testing every internal and external interface to the maximum degree practical
c) Replicating field problems identified during field functional testing or after equipment is cut-over
into revenue service
d) Simulating a realistic range of data communications message latencies and internal/external
equipment response times
e) Performing stress testing to be as representative as practical of the CBTC system controlling the
maximum number of trains that could be in operation at any one time
f) Running a range of operating scenarios consistent with anticipated operati ng procedures, including
mixed-mode operations where applicable
g) Simulating a range of failure modes including switc hover between redundant sets of ATS, wayside
and train-borne equipment
h) Ability to prepare test scenarios off-line and then run test scen arios automatically
i) Ability to capture and record test results and prov ide an automatic determination of pass/fail
The factory integrated system test facility capabilities should be documen ted in the system test plan.
8
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.1.2 Configuration
A factory integrated system test facility should therefore include the following:
a) Complete or partial set of actual CBTC ATS equipment (complete in terms of functionality, with a
representative set of equipment, e.g., full set of workst ations may not be required); CBTC ATS
equipment configuration should permit verification of switchove r between redundant equipment
sets, if provided.
b) Partial or simulated CBTC wayside and train-bo rne data communications eq uipment (to include
accurate representation of the anticipated range of message latencies and the hand-over from one
communications zone to the next); CBTC data communications equipment configuration should
permit verification of switchover between redundant equipment sets, if provided.
c) At least two sets of actual CBT C wayside equipment (to permit testing of hand-over from one
geographic zone to a neighboring geographic zone) with additional simulated CBTC wayside
equipment sets; in addition, CBTC wayside equipment configuration shou ld permit verification of
switchover between redundant equipment sets, if redundant e quipment is to be provided in the field.
d) Simulated (or, where practical, actual) external interfaces to CBTC wayside equipment. Per
IEEE Std 1474.3-2008, those external interfaces should include the following:
1) External interlockings
2) Secondary train detection systems
3) Wayside passenger information systems
4) Platform doors
5) Intrusion detection devices and other devices capable of indicati ng hazards or other conditions
that affect train operations
6) Other systems as may be specified for the site-specific application
e) One or more sets of actual CBTC train-borne equip ment with additional simulated CBTC train-
borne equipment sets; for variable-length trai n configurations, the CBTC train-borne equipment
configuration should permit verification of multi-v ehicle trains; in a ddition CBTC train-borne
equipment configuration should perm it verification of switchover bet ween redundant equipment sets
within a train, if redundant equ ipment is to be provided.
f) Simulated (or, where practical, actual) external interfaces to CBTC train-borne equipment. Per
IEEE Std 1474.3-2008, as a minimum this should include the following:
1) Wayside transponders
2) Emergency brakes
3) Train doors
4) Train-user interface
5) Propulsion system
6) Service brakes
7) Train-borne passenger information systems
8) Othe r train-borne equipment as may be specified for the site-specific application.
g) Synchronization am ong simulato rs to reflect train movements.
9
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
The factory integrated system test facility confi guration should be documented in the system test plan.
NOTE—The “value” of an integrated system test facility in minimizing field test problems is largely driven by the
extent to which the various simulators accurately represent the real ope rating environment (to include applicable
communication and response delays) and by the time allocated for factory integration testing.
6.2 Factory test plan
Within IEEE Std 1474.3-2008, for each identified CBTC sub-function, the following information is
provided:
a) A summary definition of the sub-function (it is these summary sub- function definitions that are used
throughout th is document).
b) Whether performing the sub-function is mandatory or optional [herein, an optional sub-function is
identified by (*)].
c) The CBTC subsystem/subsystems and/or external equipment providing inpu t data for the sub-
function and the CBTC subsystem/subsystems and/or external equipment receiving output data from
the sub-function (herein, if no external interface is identified as providing input data to the sub-
function or receiving output data from the sub-function, then it is assumed that the sub-function can
be fully verified in the factory).
For example, sub-function 6.1.2.4 (part ed-train detection) in IEEE Std 1474.3-2008 detects when a train of
two or more vehicles or units has parted. An external interface is defined for this sub-function (train
integrity inputs from train subs ystems that provide an indication of parted consist). As such, in this
recommended practice it is assumed th at this sub-function cannot be fully verified in the factory.
However, for sub-function 6.1.4.3 (parted-train protection) in IEEE Std 1474.3-2008, no external interface
is defined. As such, in this recommended practice it is assumed that this sub-function can be fully verified
in the factory. [This sub-functio n obtains its input from sub-function 6.1.2.4 to prevent movement
authorities from being issued to other trains into the section(s) of track that could be occupied by the parted
train.]
IEEE Std 1474.3-2008 is therefore indispensable for the application of this document and should be
referenced for a full understanding of each CBTC sub-function.
6.2.1 ATP functional testing
As defined in IEEE Std 1474.3-2008, ATP sub-functions have been grouped under the following primary
functions:
a) Train location determination
b) Limit of safe route determination
c) Limit of movement protection and target point determination
d) ATP profile determination
e) Authorized speed determination
f) Actual train speed/travel direction determination
g) Supervise/enforce authorized speed
h) Door control interlocks
10
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
i) External interlocking commands
j) Highway grade crossing warning device control/supervision
k) Train-borne ATP user interfaces
l) Fixed ATP data management
6.2.1.1 Train location determination function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.1.1.1 CBTC train location
initialization on entry to
CBTC territory Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to track-mounted and train-
mounted components; see 7.2.1.1.
6.1.1.2 CBTC train location
initialization on recovery
from CBTC equipment
failure Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to track-mounted and train-
mounted components; see 7.2.1.1.
6.1.2.1 Train length determination Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to track-mounted and train-
mounted components; see 7.2.1.1.
6.1.2.2 CBTC train location
determination Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to track-mounted and train-
mounted components; see 7.2.1.1.
6.1.2.3 Position uncertainty
compensation Full
6.1.2.4 Parted train detection Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interface that provides the parted train
indication; see 7.2.1.1.
6.1.3.1 Occupancy status of track
sections (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to track-mounted components
(e.g., track circuits/axle counters); see 7.2.1.1.
6.1.4.1 Protection of train with loss
of train location report Full
6.1.4.2 Interlocking protection with
loss of CBTC train location
report Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.1.1.
6.1.4.3 Parted train protection Full
6.1.4.4 Movement of train with
inoperable CBTC equipment Full
6.1.4.5 Train with inoperable CBTC
equipment at entry point Full

11
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.2 Limit of safe route determination function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.2.1.1 Occupied track ahead Full
6.2.1.2 End of track Full
6.2.1.3 Interlocking ahead where
route not verified Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.2.1.
6.2.1.4 Opposing traffic direction
ahead Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.2.1.
6.2.1.5 Blocked track ahead Full
6.2.2.1 Limit of safe route Full
6.2.3.1 Route status information (*) Full

6.2.1.3 Limit of movement protection and target point determination function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.3.1.1 Location of CBTC train
ahead Full
6.3.1.2 Limit of safe route ahead Full
6.3.1.3 Broken rail condition (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external device capable of
detecting broken rail; see 7.2.2.1.
6.3.1.4 Track section not confirmed
safe for train travel (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external devices capable of
detecting a hazardous condition; see 7.2.2.1.
6.3.1.5 Loss of switch status Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external device capable of
determining switch status; see 7.2.2.1.
6.3.2.1 Limit of movement
protection determination Full
6.3.3.1 Limit of target point
determination Full

12
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.4 ATP profile determination function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.4.1.1 Permanent infrastructure
speed limits Full
6.4.1.2 Permanent train speed limits Full
6.4.2.1 Temporary infrastructure
speed limits Full
6.4.2.2 Temporary train speed limits
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces from train subsystems; see
7.2.1.1.
6.4.3.1 Braking profile to target
point Full
6.4.3.2 Braking profile to speed
restriction Full
6.4.4.1 ATP profile Full

6.2.1.5 Authorized speed determination function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.5.1.1 Authorized speed
determination Full

13
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.6 Actual train speed/train travel direction determination
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.6.1.1 CBTC train speed
determination Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to train-mounted components; see
7.2.1.1.
6.6.1.2 Speed uncertainty
compensation Full
6.6.1.3 Zero speed state
determination Full
6.6.2.1 CBTC train travel direction
determination Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to train-mounted components; see
7.2.1.1.
6.2.1.7 Supervise/enforce authorized speed and travel direction function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.7.1.1 Supervise/enforce
authorized speed Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
6.7.1.2 Include worse-case
tolerance Full
6.7.2.1 Supervise/enforce travel
direction Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
6.7.3.1 Response to more restrictive
limit of movement authority Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
6.7.3.2 Response to lack of updated
movement authority data Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
6.7.3.3 Operation beyond limit of
movement protection (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
6.7.3.4 Reset of emergency brakes Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
the actual interface to the train’s emergency
brakes; see 7.2.1.2.
14
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.8 Door control interlocks function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.8.1.1 Door open interlocks/g650
train doors Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
6.8.1.2 Door open interlocks/g650
platform edge doors (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.
6.8.2.1 Departure interlock/g650
train doors Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
6.8.2.2 Departure interlock/g650
platform doors (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.
6.8.3.1 Response to loss of train
door status Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
6.8.3.2 Response to loss of platform
door status (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.
6.8.3.3 Door open interlock
override (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train and platform doors;
see 7.2.1.3.
6.8.3.4 Departure interlock override
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train and platform doors;
see 7.2.1.3.

15
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.9 External interlocking commands function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.9.1.1 CBTC equipped train approaching (*) Partial All of the requirements of this sub-
function can be fully verified in the
factory with the exception of those
requirements that are dependent upon
the actual interfaces to external
interlocking; see 7.2.1.1.
6.9.1.2 Approach/time locking override (*) Partial All of the requirements of this sub-
function can be fully verified in the
factory with the exception of those
requirements that are dependent upon
the actual interfaces to external
interlocking; see 7.2.2.1.
6.9.1.3 Traffic locking override (*) Partial All of the requirements of this sub-
function can be fully verified in the
factory with the exception of those
requirements that are dependent upon
the actual interfaces to external
interlocking; see 7.2.2.1.
6.9.1.4 Route locking override (*) Partial All of the requirements of this sub-
function can be fully verified in the
factory with the exception of those
requirements that are dependent upon
the actual interfaces to external
interlocking; see 7.2.2.1.
6.2.1.10 Highway grade crossing warning device control/supervision function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.10.1.1 Highway grade crossing
warning device control (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the highway grade crossing
warning device; see 7.2.2.3.
6.10.2.1 Warning activation signal
confirmation supervision (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the highway grade crossing
warning device; see 7.2.2.3.
6.2.1.11 Train-borne ATP user interfaces function
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.11.1.1 CBTC train-borne ATP
display data Partial All of the requirements of this sub-function could
be fully verified in the factory if an actual train
operator display were available for factory
verification; see 7.2.1.4.
6.11.2.1 CBTC train-borne ATP
input data Partial All of the requirements of this sub-function could
be fully verified in the factory if an actual train
operator display were available for factory
verification; see 7.2.1.4.
16
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.1.12 Fixed ATP data management function
Databases required to support th e factory testing should be as representative as possible of the actual field
conditions.
6.2.2 ATO functional testing
As defined in IEEE Std 1474.3-2008, ATO sub-functions have been grouped under the following primary
functions:
a) Determine ATO profile
b) Determine train berthing location
c) Regulate train speed
d) Door control
e) Train-borne display data interface
As defined in IEEE Std 1474.3-2008, for operation of trains with crews, ATO functions are optional and
would be as specified by th e authority having jurisdiction. Fo r operation of trains without crews, ATO
functions would be mandatory.
6.2.2.1 Determine ATO profile function
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.1.1.1 Determine train’s ATO
profile (*) Full
6.2.2.2 Determine train berthing position function
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.2.1.1 Determine train berthing
location/g650platform length
longer than train length (*) Full
7.2.1.2 Determine train berthing
location/g650platform length
supports multiple
berthing (*) Full
7.2.1.3 Determine train berthing
location/g650platform length
shorter than train length (*) Full
7.2.2.1 Train entry into station
platform (*) Full

17
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.2.3 Regulate train speed function
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.3.1.1 Train speed regulation (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train’s propulsion and
braking systems; see 7.2.1.5.
6.2.2.4 Door control function
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.4.1.1 Door opening/g650train doors
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
7.4.1.2 Door opening/g650platform
edge doors (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.
7.4.2.1 Door closing/g650train doors
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
7.4.2.2 Door closing/g650platform
edge doors (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.
7.4.3.1 Train door operation disable
(with no platform edge
doors) (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the train doors; see 7.2.1.3.
7.4.3.2 Train door operation disable
(with platform edge doors)
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to the platform edge doors; see
7.2.2.2.

18
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System

6.2.2.5 Train-borne ATO user interfaces function
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.5.1.1 CBTC train-borne ATO
display data (*) Partial All of the requirements of this sub-function could
be fully verified in the factory if an actual train
operator display were available for factory
verification; see 7.2.1.4.
7.5.2.1 CBTC train-borne ATO
input data (*) Partial All of the requirements of this sub-function could
be fully verified in the factory if an actual train
operator display were available for factory
verification; see 7.2.1.4.
6.2.3 ATS functional testing
As defined in IEEE Std 1474.3-2008, ATS sub-functions have been grouped under the following primary
functions:
a) Train identification
b) Train tracking
c) Train routing
d) Automatic train regulation
e) Station stop functions
f) Restricting train operations
g) Passenger information system interfaces
h) Fault reporting
i) ATS user interfaces
As defined in IEEE Std 1474.3-2008, all ATS functions are considered optional.
6.2.3.1 Train identification function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.1.1.1 CBTC operating train
identification (*) Full
6.2.3.2 Train tracking function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.2.1.1 CBTC ATS train tracking
(*) Full

19
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.3.3 Train routing function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.3.1.1 Route train/g650automatically
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.2.1.
8.3.1.2 Route train/g650manually (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.2.1.
6.2.3.4 Train regulation function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.4.1.1 Automatic dispatching (*) Partial While all of the requirements of this sub-function
can be fully verified in the factory, overall system
performance can only be confirmed through
system-level performance tests in the field; see
8.1.2.7.
8.4.1.2 Schedule/headway
regulation (*) Partial While all of the requirements of this sub-function
can be fully verified in the factory, overall system
performance can only be confirmed through
system-level performance tests in the field; see
8.1.2.7.
8.4.1.3 Service brake adjustments
(*) Full
8.4.1.4 Junction management (*) Partial While all of the requirements of this sub-function
can be fully verified in the factory, overall system
performance can only be confirmed through
system-level performance tests in the field; see
8.1.2.7.
8.4.1.5 Energy optimization (*) Partial While all of the requirements of this sub-function
can be fully verified in the factory, overall system
performance can only be confirmed through
system-level performance tests in the field; see
8.1.2.7.

20
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.3.5 Station stop functions
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.5.1.1 Enforce stop at next station
(*) Full
8.5.2.1 Hold at station (*) Full
8.5.3.1 Bypass station (*) Full
8.5.4.1 Inhibit automatic door
operation (*) Full
6.2.3.6 Restricting train operations function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.6.1.1 Stop immediate (*) Full
8.6.2.1 Temporary speed
restrictions (*) Full
8.6.3.1 Route/section blocking (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external interlocking; see
7.2.2.1.
8.6.4.1 Work zones (*) Full
6.2.3.7 Passenger information system interfaces function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.7.1.1 Wayside passenger
information message
triggers (*) Partial All of the requirements of this sub-function could
be fully verified in the factory if actual passenger
information equipment were available for factory
verification; see 7.2.2.4.
8.7.2.1 Train-borne passenger
information message
triggers (*) Partial All of the requirements of this sub-function could
be fully verified in the factory if actual passenger
information equipment were available for factory
verification; see 7.2.1.6.
6.2.3.8 Fault reporting function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.8.1.1 Failure and out-of-tolerance
condition reporting (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external devices; see 7.2.2.5.
8.8.2.1 Train health data reporting
(*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external devices; see 7.2.1.7.
21
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
6.2.4 ATS user interfaces function
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.9.1.1 ATS display data (*) Partial All of the requirements of this sub-function can be
fully verified in the factory with the exception of
those requirements that are dependent upon the
actual interfaces to external devices; see 7.2.2.6.
8.9.2.1 CBTC input data (*) Full
7. CBTC test track functional tests
7.1 CBTC test track
7.1.1 Capabilities
A CBTC test track (or test tracks) should be capable of the following:
a) Confirming vehicle interfaces/characteristics (including multi-vehicle trains)
b) Confirming wayside interfaces/characteristics (e.g., interfaces to external equipment such as
interlockings and platform edge doors)
c) Verifying vehicle/ wayside data communication links
d) Dry-running tests to be pe rformed on revenue track
e) Testing cut-over between existing and new systems (where test track is a dedicated section of
revenue track)
The CBTC test track capabilities should be do cumented in the system test plan.
7.1.2 Configuration
A CBTC test track should therefore be as representative as possibl e of the actual operating environment
and of sufficient length for ATO testing . This should include represen tative external interfacing equipment.
Ideally, the CBTC test track should be a dedicated stand-alone test track, isolated from revenue service
operations, but as a minimum should be a dedicated section of revenue track to verify interfaces in one area
before rolling out CBTC system-wide.
A combination of different CBTC test tracks may be required to provide all of the capabilities of 7.1.1.
ATS functionality may be desirable to a lev el to support th e above capabilities.
The CBTC test track configuration should be documented in the system test plan.
22
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
7.2 CBTC test track test plan
When testing a specific requirement in the factory is dependent upon simulated interfaces, it would be
necessary to fully verify the interface assumptions on the test track or in the field. The test track tests
should therefore include the following functional tests to the extent practical. (If the test track does not have
the required capabilities, it may not be possible to fully ve rify the defined sub-functions.)
7.2.1 Interfaces to train subsystems
7.2.1.1 Train location and speed determination interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.1.1.1 CBTC train location
initialization on entry to
CBTC territory Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual entry points; see 8.1.1.1.
6.1.1.2 CBTC train location
initialization on recovery
from CBTC equipment
failure Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual reentry points along the revenue alignment;
see 8.1.1.1.
6.1.2.1 Train length determination Full
6.1.2.2 CBTC train location
determination Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon
actual transponder locations; see 8.1.1.1.
6.1.2.4 Parted train detection Full
6.4.2.2 Temporary train speed limits
(*) Full
6.6.1.1 CBTC train speed
determination Full
6.6.2.1 CBTC train travel direction
determination Full
7.2.1.2 Train emergency brake system interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.7.1.1 Supervise/enforce
authorized speed Full
6.7.2.1 Supervise/enforce travel
direction Full
6.7.3.1 Response to more restrictive
limit of movement
protection Full
6.7.3.2 Response to lack of updated
movement authority data Full
6.7.3.3 Operation beyond limit of
movement protection (*) Full
6.7.3.4 Reset of emergency brakes Full

23
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
7.2.1.3 Train door interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.8.1.1 Door open interlocks/g650train
doors Full
6.8.2.1 Departure interlock/g650train
doors Full
6.8.3.1 Response to loss of train
door status Full
6.8.3.3 Door open interlock
override (*) Full
6.8.3.4 Departure interlock override
(*) Full
7.4.1.1 Door opening/g650train doors
(*) Full
7.4.2.1 Door closing/g650train doors
(*) Full
7.4.3.1 Train door operation disable
(with no platform edge
doors) (*) Full
7.2.1.4 Train operator display interfaces (if not verified in the factory)
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.11.1.1 CBTC train-borne ATP
display data Full
6.11.2.1 CBTC train-borne ATP
input data Full
7.5.1.1 CBTC train-borne ATO
display data (*) Full
7.5.2.1 CBTC train-borne ATO
input data (*) Full
7.2.1.5 Train propulsion/braking system interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.3.1.1 Train speed regulation (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
specific revenue alignment; see 8.1.1.2.

24
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
7.2.1.6 Train-borne passenger information system interfaces (if not verified in the factory)
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.7.2.1 Train-borne passenger
information message
triggers (*) Full
7.2.1.7 Train health data interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.8.2.1 Train health data reporting
(*) Full

7.2.2 Interfaces to wayside subsystems
7.2.2.1 External interlockings
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.1.3.1 Occupancy status of track
sections (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue secondary train detection
equipment; see 8.1.2.1.
6.1.4.2 Interlocking protection with
loss of CBTC train location
report Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.2.1.3 Interlocking ahead where
route not verified Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.2.1.4 Opposing traffic direction
ahead Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.3.1.3 Broken rail condition (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue device capable of detecting broken
rail; see 8.1.2.1.
6.3.1.4 Track section not confirmed
safe for train travel (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue devices capable of detecting a
hazardous condition; see 8.1.2.1.

25
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System

7.2.2.1 External interlockings (continued)
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.3.1.5 Loss of switch status Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue device capable of determining
switch status; see 8.1.2.1.
6.9.1.1 CBTC equipped train
approaching (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.9.1.2 Approach (time) locking
override (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.9.1.3 Traffic locking override (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
6.9.1.4 Route locking override (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
8.3.1.1 Route train/g650automatically
(*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings and ATS equipment;
see 8.1.2.1.
8.3.1.2 Route train /g518manually (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.
8.6.3.1 Route/section blocking (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue interlockings; see 8.1.2.1.

26
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
7.2.2.2 Platform door interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.8.1.2 Door open interlocks/g650
platform edge doors (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
6.8.2.2 Departure interlock/g650
platform doors (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
6.8.3.2 Response to loss of platform
door status (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
7.4.1.2 Door opening/g650platform
edge doors (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
7.4.2.2 Door closing/g650platform
edge doors (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
7.4.3.2 Train door operation disable
(with platform edge doors)
(*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue platform edge doors; see 8.1.2.2.
7.2.2.3 Highway grade crossing warning device interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.10.1.1 Highway grade crossing
warning device control (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual highway grade crossing warning device; see
8.1.2.3.
6.10.2.1 Warning activation signal
confirmation supervision (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual highway grade crossing warning device; see
8.1.2.3.
7.2.2.4 Wayside passenger information system interfaces (if not verified in the factory)
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.7.1.1 Wayside passenger
information message
triggers (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue passenger information system; see
8.1.2.4.
27
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
7.2.2.5 Other external devices
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.8.1.1 Failure and out-of-tolerance
condition reporting (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue wayside devices; see 8.1.2.5.
7.2.2.6 ATS user interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.9.1.1 ATS display data (*) Partial All of the requirements of this sub-function could
be fully verified on a test track with the exception
of those requirements that are dependent upon the
actual revenue wayside devices and ATS display;
see 8.1.2.6.
8. Field functional tests
There will be practical limits as the extent to which CBTC test track is representative of the actual field
operating environment, and as a consequence, many of th e test track tests should be repeated in the field.
However, the goal should be to minimize recommende d field test requirements and to ensure that prior
factory and test track testing would maximize the probability of success of any required field testing.
When verifying a given CBTC function in the field, in general it shoul d not be necessary to repeat the
functional tests for all trains or at all geographic locations. Extent of tests should be defined in the system
test plan.
The authority having jurisdiction can always require additional testing over and above the minimum
recommended testing.
8.1 Field test plan
The field tests should include the following functional tests, as a minimum.
28
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
8.1.1 Interfaces to train subsystems
8.1.1.1 Train location and speed determination interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.1.1.1 CBTC train location
initialization on entry to
CBTC territory Full
6.1.1.2 CBTC train location
initialization on recovery
from CBTC equipment
failure Full
6.1.2.2 CBTC train location
determination Full
8.1.1.2 Train propulsion/braking system interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
7.3.1.1 Train speed regulation (*) Full
8.1.2 Interfaces to wayside subsystems
8.1.2.1 External interlockings
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.1.3.1 Occupancy status of track
sections (*) Full
6.1.4.2 Interlocking protection with
loss of CBTC train location
report Full
6.2.1.3 Interlocking ahead where
route not verified Full
6.2.1.4 Opposing traffic direction
ahead Full
6.3.1.3 Broken rail condition (*) Full
6.3.1.4 Track section not confirmed
safe for train travel (*) Full
6.3.1.5 Loss of switch status Full
6.9.1.1 CBTC equipped train
approaching (*) Full
6.9.1.2 Approach (time) locking
override (*) Full

29
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
8.1.2.1 External interlockings (continued)
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.9.1.3 Traffic locking override (*) Full
6.9.1.4 Route locking override (*) Full
8.3.1.1 Route train/g650automatically
(*) Full
8.3.1.2 Route train/g650manually (*) Full
8.6.3.1 Route/section blocking (*) Full
8.1.2.2 Platform door interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.8.1.2 Door open
interlocks/g650platform edge
doors (*) Full
6.8.2.2 Departure
interlock/g650platform doors
(*) Full
6.8.3.2 Response to loss of platform
door status (*) Full
7.4.1.2 Door opening/g650platform
edge doors (*) Full
7.4.2.2 Door closing/g650platform
edge doors (*) Full
7.4.3.2 Train door operation disable
(with platform edge doors)
(*) Full
8.1.2.3 Highway grade crossing warning device interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
6.10.1.1 Highway grade crossing
warning device control (*) Full
6.10.2.1 Warning activation signal
confirmation supervision (*) Full
8.1.2.4 Wayside passenger information system interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.7.1.1 Wayside passenger
information message
triggers (*) Full
30
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
8.1.2.5 Other external devices
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.8.1.1 Failure and out-of-tolerance
condition reporting (*) Full
8.1.2.6 ATS user interfaces
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.9.1.1 ATS display data (*) Full
8.1.2.7 System level
IEEE 1474.3
reference Sub-function Factory
verification Comments
8.4.1.1 Automatic dispatching (*) Full
8.4.1.2 Schedule/headway
regulation (*) Full
8.4.1.4 Junction management (*) Full
8.4.1.5 Energy optimization (*) Full

31
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
9. Summary
The following table summ arizes the overall functional test plan to verify all of the sub -functions identified
in IEEE Std 1474.3-2008.
IEEE 1474.3
reference Sub-function Factory
verification CBTC test
track
verification Field
verification
6.1.1.1 CBTC train location initialization on
entry to CBTC territory Partial Partial Full
6.1.1.2 CBTC train location initialization on
recovery from CBTC equipment failure Partial Partial Full
6.1.2.1 Train length determination Partial Full
6.1.2.2 CBTC train location determination Partial Partial Full
6.1.2.3 Position uncertainty compensation Full
6.1.2.4 Parted train detection Partial Full
6.1.3.1 Occupancy status of track sections (*) Partial Partial Full
6.1.4.1 Protection of train with loss of train
location report Full
6.1.4.2 Interlocking protection with loss of
CBTC train location report Partial Partial Full
6.1.4.3 Parted train protection Full
6.1.4.4 Movement of train with inoperable
CBTC equipment Full
6.1.4.5 Train with inoperable CBTC equipment
at entry point Full
6.2.1.1 Occupied track ahead Full
6.2.1.2 End of track Full
6.2.1.3 Interlocking ahead where route not
verified Partial Partial Full
6.2.1.4 Opposing traffic direction ahead Partial Partial Full
6.2.1.5 Blocked track ahead Full
6.2.2.1 Limit of safe route Full
6.2.3.1 Route status information (*) Full
6.3.1.1 Location of CBTC train ahead Full
6.3.1.2 Limit of safe route ahead Full
6.3.1.3 Broken rail condition (*) Partial Partial Full

32
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
9. Summary (continued)

IEEE 1474.3
reference Sub-function Factory
verification CBTC test
track
verification Field
verification
6.3.1.4 Track section not confirmed safe for
train travel (*) Partial Partial Full
6.3.1.5 Loss of switch status Partial Partial Full
6.3.2.1 Limit of movement protection
determination Full
6.3.3.1 Limit of target point determination Full
6.4.1.1 Permanent infrastructur e speed limits Full
6.4.1.2 Permanent train speed limits Full
6.4.2.1 Temporary infrastructure speed limits Full
6.4.2.2 Temporary train speed limits (*) Partial Full
6.4.3.1 Braking profile to target point Full
6.4.3.2 Braking profile to speed restriction Full
6.4.4.1 ATP profile Full
6.5.1.1 Authorized speed determination Full
6.6.1.1 CBTC train speed determination Partial Full
6.6.1.2 Speed uncertainty compensation Full
6.6.1.3 Zero speed state determination Full
6.6.2.1 CBTC train travel direction
determination Partial Full
6.7.1.1 Supervise/enforce authorized speed Partial Full
6.7.1.2 Include worse-case tolerance Full
6.7.2.1 Supervise/enforce travel direction Partial Full
6.7.3.1 Response to more restrictive limit of
movement authority Partial Full
6.7.3.2 Response to lack of updated movement
authority data Partial Full
6.7.3.3 Operation beyond limit of movement
protection (*) Partial Full
6.7.3.4 Reset of emergency brakes Partial Full
6.8.1.1 Door open interlocks/g650train doors Partial Full
6.8.1.2 Door open interlocks/g650platform edge
doors (*) Partial Partial Full

33
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
9. Summary (continued)

IEEE 1474.3
reference Sub-function Factory
verification CBTC test
track
verification Field
verification
6.8.2.1 Departure interlock/g650train doors Partial Full
6.8.2.2 Departure interlock/g650platform doors
(*) Partial Partial Full
6.8.3.1 Response to loss of train door status Partial Full
6.8.3.2 Response to loss of platform door status
(*) Partial Partial Full
6.8.3.3 Door open interlock override (*) Partial Full
6.8.3.4 Departure interlock override (*) Partial Full
6.9.1.1 CBTC equipped train approaching (*) Partial Partial Full
6.9.1.2 Approach/time locking override (*) Partial Partial Full
6.9.1.3 Traffic locking override (*) Partial Partial Full
6.9.1.4 Route locking override (*) Partial Partial Full
6.10.1.1 Highway grade crossing warning device
control (*) Partial Partial Full
6.10.2.1 Warning activation signal confirmation
supervision (*) Partial Partial Full
6.11.1.1 CBTC train-borne ATP display data Partial Full
6.11.2.1 CBTC train-borne ATP input data Partial Full
7.1.1.1 Determine train’s ATO profile (*) Full
7.2.1.1 Determine train berthing
location/g650platform length longer than
train length (*) Full
7.2.1.2 Determine train berthing
location/g650platform length supports
multiple berthing (*) Full
7.2.1.3 Determine train berthing
location/g650platform length shorter than
train length (*) Full
7.2.2.1 Train entry into station platform (*) Full
7.3.1.1 Train speed regulation (*) Partial Partial Full
7.4.1.1 Door opening/g650train doors (*) Partial Full
7.4.1.2 Door opening/g650platform edge doors (*) Partial Partial Full
7.4.2.1 Door closing/g650train doors (*) Partial Full

34
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
9. Summary (continued)

IEEE 1474.3
reference Sub-function Factory
verification CBTC test
track
verification Field
verification
7.4.2.2 Door closing/g650platform edge doors (*) Partial Partial Full
7.4.3.1 Train door operation disable (with no
platform edge doors) (*) Partial Full
7.4.3.2 Train door operation disable (with
platform edge doors) (*) Partial Partial Full
7.5.1.1 CBTC train-borne ATO display data (*) Partial Full
7.5.2.1 CBTC train-borne ATO input data (*) Partial Full
8.1.1.1 CBTC operating train identification (*) Full
8.2.1.1 CBTC ATS train tracking (*) Full
8.3.1.1 Route train/g650automatically (*) Partial Partial Full
8.3.1.2 Route train/g650manually (*) Partial Partial Full
8.4.1.1 Automatic dispatching (*) Partial Partial Full
8.4.1.2 Schedule/headway regulation (*) Partial Partial Full
8.4.1.3 Service brake adjustments (*) Full
8.4.1.4 Junction management (*) Partial Partial Full
8.4.1.5 Energy optimization (*) Partial Partial Full
8.5.1.1 Enforce stop at next station (*) Full
8.5.2.1 Hold at station (*) Full
8.5.3.1 Bypass station (*) Full
8.5.4.1 Inhibit automatic door operation (*) Full
8.6.1.1 Stop immediate (*) Full
8.6.2.1 Temporary speed restrictions (*) Full
8.6.3.1 Route/section blocking (*) Partial Partial Full
8.6.4.1 Work zones (*) Full
8.7.1.1 Wayside passenger information
message triggers (*) Partial Partial Full
8.7.2.1 Train-borne passenger information
message triggers (*) Partial Full

35
Copyright © 2011 IEEE. All rights reserved.

IEEE Std 1474.4-2011
IEEE Recommended Practice for Functional Testing of a Communications-Based Train Control (CBTC) System
36
Copyright © 2011 IEEE. All rights reserved. 9. Summary (continued)

IEEE 1474.3
reference Sub-function Factory
verification CBTC test
track
verification Field
verification
8.8.1.1 Failure and out-of-tolerance condition
reporting (*) Partial Partial Full
8.8.2.1 Train health data reporting (*) Partial Full
8.9.1.1 ATS display data (*) Partial Partial Full
8.9.1.2 CBTC input data (*) Full