1. Role of the Highway-Rail Intersection in the National ITS Architecture IEEE WG14 June 20, 2000 Bruce Eisenhart Lockheed Martin Architecture Development Team

2. Architecture Development Team Agenda u What is the National ITS Architecture u Highway Rail User Service/ User Service Requirements u Support of HRI in the National ITS Architecture u What can the National ITS Architecture provide to HRI standards development process?

3. Architecture Development Team What is an architecture? u Identifies boundaries and participants u Describes activities or functions u Provides framework for planning, defining, and integrating your ITS

4. Architecture Development Team Why was the National ITS Architecture needed? u Interface standards identification/coordination u ITS complexity u ITS integration CONGESTION AHEAD

5. Architecture Development Team What does the National ITS Architecture Consist of? User Services Logical Architecture Physical Architecture National ITS Architecture Requirements eg. Incident Management, HRI What functions? eg. Detect Incident Verify Incident Where are the functions? E.g. Traffic Management Center

6. Architecture Development Team Physical Architecture Interfaces Objectives & Requirements Solutions Communications Transportation Institutional u Defines physical entity interfaces u Distributes functionality u 3 layers u Communications Layer u How information is transferred between transportation systems u Transportation Layer u What transportation systems transfer what information u Institutional Layer u Supporting institutional structure, policy, and strategies

7. Architecture Development Team Physical Architecture Entities u What is a Physical Architecture Entity? u Major “building block” of the architecture u What “types” of entities are there? u Terminator: u Users or institutions on the edge of the Architecture u Subsystem: u Collection of functions within a single institutional boundary

8. Architecture Development Team Terminators Establish the Architecture Boundary Related Systems Environment 8 Terminators Including: Environment Roadway Potential Obstacles Users 19 Terminators Including: Driver Traffic Operations Personnel Emergency System Operator 29 Terminators Including: DMV Financial Institution Other Vehicle The Rest of the World ITS Terminators

9. Architecture Development Team Physical Architecture Subsystems Travelers Vehicles Roadside Centers Commercial Vehicle Administration Archived Data Management Vehicle Transit Vehicle Commercial Vehicle Emergency Vehicle Remote Traveler Support Personal Information Access Toll Administration Emergency Management Traffic Management Fleet and Freight Management Transit Management Emissions Management Information Service Provider Roadway Toll Collection Parking Management Commercial Vehicle Check

10. Architecture Development Team Physical Architecture Subsystems and Interconnects Travelers Vehicles Roadside Centers Wide Area Wireless Communications Vehicle to Vehicle Communications Commercial Vehicle Administration Archived Data Management Dedicated Short Range Communications Vehicle Transit Vehicle Commercial Vehicle Emergency Vehicle Remote Traveler Support Personal Information Access Toll Administration Emergency Management Traffic Management Fleet and Freight Management Transit Management Emissions Management Information Service Provider Roadway Toll Collection Parking Management Commercial Vehicle Check Wireline Communications

11. Architecture Development Team Connecting Entities: Architecture Flows Traffic Management RoadwayVehicle signal control status local traffic flow environmental conditions signal control data vehicle probe data vehicle signage data Architecture Flows (456 Total) –High-level subsystem information exchange –Considerations for integration

12. Architecture Development Team Subsystems are made up of functions Centers Commercial Vehicle Administration Archived Data Management Toll Administration Emergency Management Traffic Management Fleet and Freight Management Transit Management Emissions Management Information Service Provider Logical Architecture elements are processes and data flows Traffic Management Subsystem Provide Device Control Manage Travel Demand Manage Incidents Provide Traffic Surveilla nce u Logical Architecture defines the functionality required by each subsystem

13. Architecture Development Team Logical Architecture u Logical Architecture Defines u The Functions To Be Performed u The Information Transfers Between Functions u It Does NOT Define: u Where the Functions are Performed u This is the Role of the Physical Architecture u How the Functions are Implemented u This isn’t done anywhere in the National ITS Architecture Select Route Direct Driver destination current position traffic conditions directions selected route map data Route Guidance - Logical View

14. Architecture Development Team Focused Architecture Views Vehicle to Vehicle Communications Commercial Vehicle Check Vehicle Subsystems Roadside Subsystems Parking Management Toll CollectionRoadway Emergency Vehicle Commercial Vehicle Transit Vehicle Remote Traveler Support Wide Area Wireless Communications Commercial Vehicle Administration Freight and Fleet Management Toll Administration Emergency Management Traffic Management Transit Management Emissions Management Information Service Provider Traveler Subsystems Center Subsystems Personal Information Access Planning Wireline Communications Short Range Wireless Communications “Technical Framework” “Transportation Services” ?

15. Architecture Development Team Travelers Vehicles Roadside Centers Archived Data Management Vehicle Transit Vehicle Commercial Vehicle Emergency Vehicle Remote Traveler Support Personal Information Access Toll Administration Emergency Management Traffic Management Fleet and Freight Management Transit Management Emissions Management Information Service Provider Roadway Toll Collection Parking Management Commercial Vehicle Check Commercial Vehicle Administration Next Level of Detail: Equipment Packages Subsystems are comprised of Equipment Packages Equipment Packages TMC Basic Signal Control TMC Based Freeway Control HRI Traffic Management Traffic Management Subsystem TMC Incident Detection

16. Architecture Development Team Market Packages u Identify the Pieces of the Architecture Required to Implement a Particular Service u Physical Architecture subsets with multiple, related equipment packages from one or more subsystems” u More Specific Than User Services u Segregate Potential Early Deployments From Higher Risk Services u Defined To Support Benefits Analysis with Clear Ties to Transportation Problems

17. Architecture Development Team Focused Architecture View: Market Packages Focused Architecture View: Market Packages Traffic Management Subsystem Roadway Subsystem TMC Incident Detection TMC Based Freeway Control TMC Basic Signal Control Roadway Signal Control Roadway Basic Surveillance Roadway Incident Detection Surface Street Control Equipment Packages Market Package Subsystems Traffic Maintenance

18. Architecture Development Team Version 2.0 1993 1994 1995 1996 1997 1998 User Services Phase I Competition Phase II Architecture Published HRI Update Current Architecture Version Published December 1999 Version 3.0 1999

19. Architecture Development Team National ITS Architecture Release 3.0 u Where to find it u CD-ROM u Web Page: http://www.iteris.com/itsarch

20. Architecture Development Team HRI in ITS HRI User Service HRI User Service Reqmts Nat’l ITS Arch Update Developed 2/96 by FRA, Volpe, and JPL Created 6/96 by FRA and JPL Completed 1/97

21. Architecture Development Team HRI User Service Requirements u Key areas of User Service Requirements u Types of Users u Interfaces u Non-Real-time u Real-time u Active Warning Systems u Augment Intersection with Highway traffic control devices u Automated Collision Avoidance Function u Intelligent Intersection Controller u Standard Crossing (Standard Speed Rail) u Advanced Crossing (High Speed Rail) u Collision Notification

22. Architecture Development Team Example User Service Requirements

23. Architecture Development Team The National ITS Architecture: Consensus Process u The National ITS Architecture is based on Stakeholder Consensus u Developing HRI consensus: u Architecture HRI Kickoff and Special Program Review (FRA, FHWA, FTA, Volpe, AAR, Canac, American Shortline Railroad Association, NCDOT, AASHTO, ITE, ITS America) u Site Visits (Union Pacific, Norfolk Southern/NCDOT) u Key Meetings (HRI Technical Working Group, TRB HRI Session) u Direct Discussion and Feedback (Volpe, Canac, AAR, TTI, UP)

24. Architecture Development Team Some Drivers for Physical Architecture Decisions u What are the Existing System Boundaries? u What are the Crucial Interfaces? u Does the Interface: u Span Agencies? u Connect Public and Private Sectors? u Require Broad and Interoperable Implementation? u Are (Inter)National Standards Desirable? u Where are the Key Performance and Functional Requirements?

25. Architecture Development Team The National ITS Architecture: HRI User Service Addition (1) Wayside Equipment Intelligent Controller Automatic Gates/Barriers Traffic Signals Variable Message Signs Surveillance Short Range Communications Track Circuits TRAIN APPROACHING Rail OperationsTraffic Management What are the current and potential entities and how do they or might they interface ?

26. Architecture Development Team The National ITS Architecture: HRI User Service Addition (2) Wayside Equipment Intelligent Controller Automatic Gates/Barriers Traffic Signals Variable Message Signs Surveillance Short Range Communications Track Circuits TRAIN APPROACHING Rail OperationsTraffic Management Traffic Management Subsystem Vehicle Subsystem Wayside Equipment Terminator Rail Operations Terminator Roadway Subsystem

27. Architecture Development Team Standard Railroad Grade Crossing Market Package Subsystem Equipment Package Terminator architecture flow Roadway Standard Speed Rail Crossing Wayside Equipment track status Traffic traffic characteristics Pedestrians Driver crossing permission driver information hri status Rail Operations Traffic Management HRI Traffic Management hri advisories hri status hri control data hri request

28. Architecture Development Team Advanced Railroad Grade Crossing Market Package Subsystem Equipment Package Terminator architecture flow Roadway Advanced Speed Rail Crossing Wayside Equipment track status Traffic traffic characteristics Pedestrians Driver crossing permission driver information hri status Rail Operations Traffic Management HRI Traffic Management hri advisories hri status hri control data hri request Intersection blockage notification Intersection blockage notification arriving train information

29. Architecture Development Team Railroad Operations Coordination Market Package Roadway Rail Operations Traffic Management Rail Operations Coordination hri advisories hri status hri control data hri request railroad advisories railroad schedules Information Service Provider traffic information Subsystem Equipment Package Terminator architecture flow

30. Architecture Development Team The National ITS Architecture: HRI Update Summary u Rail Operations and Wayside Equipment Added as Terminators u Augmented Traffic Management and Roadway Subsystems u New Traffic Management Equipment Packages u HRI Traffic Management u Rail Operations Coordination u New Roadway Equipment Packages u Standard Rail Crossing u Advanced Rail Crossing u New Architecture Flows Defined and Mapped to Communications Interconnects u New Flows Identified (e.g., Rail Operations to Traffic Management) u Existing Supporting Flows Reviewed (e.g., Roadway to Vehicle) u New Market Packages Created

31. Architecture Development Team ITS Standards u Define subsystem interfaces in more detail u Use National ITS Architecture interface definitions as starting point

32. Architecture Development Team Architecture and Standards Traffic Management Subsystem Transit Management Subsystem traffic information request for traffic information transit system data signal priority status NTCIP Center to Center Traffic Management Data Dictionary Transit Communications Interface Profiles ITS Architecture request for signal priority ITS Standards u Message Set u Data Elements u Communications Profile

33. Architecture Development Team Links Between Architecture and Standards TM Data Dictionary EVENT_IncidentSeverity_code Data element incident information Physical Architecture Architecture Flow Traffic Management Subsystem Emergency Management Subsystem incident_alert incident_severity Logical (Leveled) Architecture Dataflow (primitive) Dataflow Contains M A P S T O Incident-Description External TMC Message Set Message Set Event-Incident Severity Message Contains M A P S T O

34. Architecture Development Team How Can Architecture Support Standards Development u Definition of Interfaces in National ITS Architecture serves as starting point for standards effort u Where to find definition of HRI Interfaces: u Standards Requirements Package 12: Highway Rail Intersections u Available on CD-ROM- Archdocs/Standards Requirements Document (pages 640-663) u Essential information also on CD-ROM hypertext under Hypertext View/Standards Requirements

35. Architecture Development Team SR Package 12: Outline 1 Introduction to Standards Requirements Documentation 2 Introduction: Highway Rail Intersections (HRI) 3 Transaction Sets for Highway Rail Intersection Interfaces 3.1 Rail Operations and Traffic Management Subsystem 3.2 Roadway Subsystem and Traffic Management Subsystem 3.3 Roadway Subsystem and Wayside Equipment Terminator 4 Interface Decomposition 4.1 Traffic Management -> Rail Operations 4.2 Traffic Management -> Roadway Subsystem 4.3 Wayside Equipment -> Roadway Subsystem 4.4 Rail Operations -> Traffic Management 4.5 Roadway Subsystem -> Traffic Management 4.6 Roadway Subsystem -> Wayside Equipment 5 Communications Layer Requirements 6 Constraints 7 Data Dictionary Elements

36. Architecture Development Team HRI Interfaces

37. Architecture Development Team HRI Arch Flows

38. Architecture Development Team Summary u National ITS Architecture describes interfaces and information flows critical to HRI as part of ITS u Standards Package 12: HRI is key starting point for development of standards.