IEC 62290-2-2014: Urban Guided Transport Management and Command/Control Systems โ€” Functional Requirements

💡 Scope: IEC 62290-2-2014 specifies the functional requirements for Urban Guided Transport Management and Command/Control Systems (UGTMS), covering all automation grades from GoA0 (manual) to GoA4 (unattended train operation) for metro, light rail, and automated people mover systems.

1. 🏗️ UGTMS Architecture and Automation Grades

IEC 62290-2-2014 is part of the 62290 series that defines the framework for modern urban rail control systems. Part 2 focuses specifically on the functional requirements that apply across the system lifecycle, from concept design through operational deployment. The standard defines four Grades of Automation (GoA) that form the foundation for classifying urban guided transport systems:

GoA Category Train Operation Door Closure Incident Mgmt
GoA 0 On-sight manual Driver Driver Driver
GoA 1 Manual with ATP Driver with ATP supervision Driver Driver
GoA 2 Semi-automatic (STO) Automatic with driver Driver Driver
GoA 3 Driverless (DTO) Automatic Attendant Attendant
GoA 4 Unattended (UTO) Automatic Automatic Automatic
Key Contribution: The GoA framework in IEC 62290-2 provides a universal classification language that enables transit authorities, system integrators, and suppliers to unambiguously specify the level of automation required for a given project, forming the basis for safety cases and operational concepts.

2. ⚙️ Core Functional Requirements

The standard organizes functional requirements into several domains, each specifying mandatory and optional functions depending on the target GoA:

2.1 Train Protection Functions

Train protection encompasses all functions that ensure safe train operation, including automatic train protection (ATP), overspeed detection, safe braking profiles, door interlock, and rollback protection. These functions must be realized with SIL 4 integrity (Safety Integrity Level 4 per IEC 61508) for all GoA levels above 0.

2.2 Traffic Management Functions

Traffic management includes automatic route setting, headway regulation, dwell time management, and service regulation. The standard specifies that traffic management systems must support both time-based and headway-based operation, with the ability to automatically adjust running times to recover from service disruptions.

2.3 Operational Modes

The standard defines a comprehensive set of operational modes that the system must support:

  • Normal Operation: Fully automatic or manual according to the specified GoA
  • Degraded Operation: Mode transitions when failures occur (e.g., GoA2 falling back to GoA1)
  • Emergency Operation: Including emergency brake application, evacuation management, and fire mode
  • Maintenance Mode: For track and vehicle maintenance activities with protection
  • Shunting/Depot Mode: Low-speed manual or automatic operation within depot areas
⚠️ Engineering Challenge: Mode transitions are among the most complex aspects of UGTMS design. When a system degrades from GoA4 to GoA3 or lower, the transition must be seamless and safe. The standard requires that all mode transitions be formally specified using state-machine diagrams and verified through systematic testing, including fault injection scenarios.

3. 🔄 Communication and System Interfaces

IEC 62290-2-2014 defines critical interfaces between the UGTMS subsystems: the Traffic Management System (TMS), the Automatic Train Control (ATC) system, and the Human-Machine Interface (HMI). The standard mandates specific data exchange requirements:

Interface Data Elements Update Rate Criticality
TMS → ATC Route commands, timetable, speed profiles ≤ 1 s SIL 2
ATC → TMS Train position, speed, mode, alarms ≤ 0.5 s SIL 2
HMI → ATC Driver commands, mode selection Event-driven SIL 4
ATP → Interlocking Movement authority, emergency stop ≤ 200 ms SIL 4
Train → Wayside Position, integrity, health status ≤ 250 ms SIL 4
💡 Engineering Insight: The interface specification in IEC 62290-2 emphasizes that safety-critical communications (ATP commands, emergency stops) must use SIL 4-rated communication channels with end-to-end integrity protection. Non-safety traffic management data can use lower-integrity channels. This separation of safety and non-safety data flows is a fundamental principle for cost-effective UGTMS architecture.

4. ❓ Frequently Asked Questions

Q1: What is the relationship between IEC 62290 and IEEE 1474 (CBTC)?

IEC 62290 provides a higher-level functional framework for urban guided transport management, while IEEE 1474 specifically addresses Communications-Based Train Control (CBTC) system requirements. The standards are complementary—IEC 62290 covers operational and system-level functions, while IEEE 1474 focuses on the train control technology implementation.

Q2: Is IEC 62290-2 applicable to mainline railway systems?

No. The standard is specifically scoped for urban guided transport systems (metros, light rail, automated people movers). Mainline and heavy rail systems are covered by EN 50126 / IEC 62425 (RAM and safety for railway signalling) and the ERTMS/ETCS framework.

Q3: How are safety requirements allocated between Part 2 and Part 3 of the series?

Part 2 (this standard) defines the functional requirements from an operational perspective. Part 3, IEC 62290-3, then maps these functions to safety integrity levels (SIL) and specifies the safety-related system requirements. Both parts together provide a complete specification framework.

Q4: What are the main challenges in upgrading from GoA2 to GoA4?

The primary challenges include: (1) platform screen door integration and obstacle detection, (2) onboard passenger monitoring systems, (3) degraded mode management without onboard staff, (4) fallback braking systems that operate without driver intervention, and (5) regulatory approval for unattended operation, which varies significantly by jurisdiction.

© 2026 TNLab — Technical Navigation Laboratory

Leave a Reply

Your email address will not be published. Required fields are marked *