Rail Operations (Terminator*)

Terminator Interfaces Diagram

Inputs/Outputs: Architecture Flows* and Data Flows*

Emergency Management Rail Operations

• emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
  Data Flows*:
  • tro-disaster_response_plan_coordination
  • tro-evacuation_plan_coordination

• evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows*:
  • tro-evacuation_information_for_rail

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • tro-incident_information

• incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
  Data Flows*:
  • tro-incident_response_status

• threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
  Data Flows*:
  • tro-threat_info

• transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • tro-transportation_system_status_for_disaster
  • tro-transportation_system_status_for_evacuation

Maintenance and Construction Management Rail Operations

• maint and constr work plans (Architecture Flow*) - Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
  Data Flows*:
  • tro-m_and_c_work_plans_for_rail

• road weather information (Architecture Flow*) - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
  Data Flows*:
  • tro-road_weather_info

• work plan feedback (Architecture Flow*) - Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system.
  Data Flows*:
  • tro-railroad_schedule_feedback

Rail Operations Emergency Management

• emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
  Data Flows*:
  • fro-disaster_response_plan_coordination
  • fro-evacuation_plan_coordination

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • fro-rail_incident_information

• rail incident response status (Architecture Flow*) - Status of the rail system’s response to current incidents.
  Data Flows*:
  • fro-rail_incident_response_status

• rail system status assessment (Architecture Flow*) - Assessment of damage sustained by rail lines and associated railroad infrastructure including location and extent of the damage, impact on current operations and necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • fro-rail_system_status_for_disaster
  • fro-rail_system_status_for_evacuation

• railroad schedules (Architecture Flow*) - Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
  Data Flows*:
  • fro-railroad_schedules_for_emergency

Rail Operations Maintenance and Construction Management

• railroad schedules (Architecture Flow*) - Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
  Data Flows*:
  • fro-railroad_schedules

• work plan feedback (Architecture Flow*) - Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system.
  Data Flows*:
  • fro-m_and_c_plan_feedback_from_rail

Rail Operations Traffic Management

• railroad advisories (Architecture Flow*) - Real-time notification of railway-related incident or advisory.
  Data Flows*:
  • fro-incident_notification

• railroad schedules (Architecture Flow*) - Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
  Data Flows*:
  • fro-maintenance_schedules
  • fro-train_schedules

Traffic Management Rail Operations

• hri advisories (Architecture Flow*) - Notification of Highway-Rail Intersection equipment failure, intersection blockage, or other condition requiring attention, and maintenance activities at or near highway rail intersections.
  Data Flows*:
  • tro-equipment_status
  • tro-event_schedules
  • tro-incident_notification