ATMS13-Standard Railroad Grade Crossing (Market Package*)

Market Package Graphic       Transaction Set Diagram

Description

This market package manages highway traffic at highway-rail intersections (HRIs) where operational requirements do not dictate more advanced features (e.g., where rail operational speeds are less than 80 miles per hour). Both passive (e.g., the crossbuck sign) and active warning systems (e.g., flashing lights and gates) are supported. (Note that passive systems exercise only the single interface between the roadway subsystem and the driver in the architecture definition.) These traditional HRI warning systems may also be augmented with other standard traffic management devices. The warning systems are activated on notification by interfaced wayside equipment of an approaching train. The equipment at the HRI may also be interconnected with adjacent signalized intersections so that local control can be adapted to highway-rail intersection activities. Health monitoring of the HRI equipment and interfaces is performed; detected abnormalities are reported to both highway and railroad officials through wayside interfaces and interfaces to the traffic management subsystem.

Includes Equipment Packages and Subsystems:

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Pedestrians crossing call Roadway Subsystem Yes
Roadway Subsystem driver information Driver Yes
Roadway Subsystem crossing permission Pedestrians Yes
Roadway Subsystem hri status Traffic Management Yes
Roadway Subsystem hri operational status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Wayside Equipment Yes
Traffic traffic characteristics Roadway Subsystem Yes
Traffic Management hri advisories Rail Operations Yes
Traffic Management hri control data Roadway Subsystem Yes
Traffic Management hri request Roadway Subsystem Yes
Wayside Equipment track status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Subsystem Yes
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Early Deployment

This market package has been identified as an early deployment due to a promising combination of low risk implementation characteristics, developing public or private markets for the package, and tangible system or user benefits. Passive warning systems and active warning devices may be augmented with standard traffic control devices and interconnected with adjacent intersections to provide safer and more efficient management of highway traffic at highway-rail intersections. Each of these capabilities can be implemented with today’s technology and without need for major new standardization efforts or institutional change.

Rural Development

For the Crash Prevention and Security Rural Development Track, this market package is highly applicable to rural user needs and suitable for the rural environment. It addresses the needs of the broad rural development track by the following: Systems that manage highway rail intersections by warning vehicle operators of train proximity and providing traffic control through barriers to prevent vehicle from entering rail/roadway to prevent accidents from occurring. Data from the intersection is shared with the local traffic management agency.

ITS Goals Supported

    ITS Goal Satisfaction Level
    Improve Safety * * *
    Create an Environment for an ITS Market *
    * Features that marginally satisfy the goals
    * * Features that almost satisfy every aspect of the goals
    * * * Features completely satisfy every aspect of the goals

User Services related to this Market Package:

Problem / Solution Pairs this Market Package Addresses


Hypertext Architecture Version 6.1 generated on 1/7/2009 from the following databases
Physical Architecture dated 12/15/2008,
Logical Architecture dated 12/2/2008,
Market Packages dated 12/14/2008,
Security dated 11/13/2008,
User Services dated 4/9/2007,
Theory of Operations dated 12/14/2008,
AppMap dated 12/19/2008 and the
SDOMAP dated 12/12/2008