Regional Architecture Logo
 

Send Your Comments

E-Mail

MCM Incident Management Equipment Package

Architecture Geographic Scope

Description:

Supports coordinated response to incidents - share incident notifications, manage incident response resources, and coordinate overall incident situation and response among allied response organizations.

 

Included in:

City of Sherman Maintenance Division
City of Sherman Traffic Operations Center
County Road and Bridge
Municipal PWD
Oklahoma DOT Maintenance Sections
Other TxDOT District Maintenance Sections
TxDOT Highway Conditions Reporting System
TxDOT Paris District Area Engineers Office
TxDOT Paris District Maintenance Sections

Functional Requirements:

1The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
2The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, etc.
3The center shall exchange incident and threat information with emergency management centers as well as traffic management centers; including notification of existence of incident and expected severity, location, time and nature of incident.
4The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
5The center shall respond to requests from emergency management to provide maintenance and construction resources to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic management centers and other maintenance centers.
6The center shall exchange road network status assessment information with emergency management and traffic management centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
7The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
8The center shall receive information indicating the damage sustained by transportation assets, derived from aerial surveillance, field reports, inspections, tests, and analyses to support incident management.
  

User Service Requirements (fully or partially addressed):

5.0EMERGENCY MANAGEMENT
5.1EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.4ENPS shall include a Wide Area Alert (WAA) function to notify the public in emergency situations using ITS driver information and traveler information capabilities.
5.1.4.1WAA shall notify transportation operators and information providers when an emergency situation occurs that requires public notification.
5.1.4.1.1The WAA notification shall identify the originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert.
5.1.4.1.2The WAA shall provide necessary information for emergencies including, but not limited to, child abductions, severe weather watches and warnings, military activities, civil emergencies, other natural and human-caused disaster advisories, and law enforcement warnings.
5.1.4.2WAA shall use available dynamic message signs, highway advisory radio, in-vehicle displays, 511 and other telephone information systems, traveler information web sites, transit vehicle information systems, message display boards, and other information systems to provide the WAA information to the public.
5.1.4.2.1WAA shall tailor the information provided for individual driver and traveler information systems, limiting messages to short notifications for human-factors limited devices like dynamic message signs.
5.1.4.3WAA shall keep the WAA initiator apprised of the current status of public notification, including an accounting of the driver and traveler information resources that are being utilized.
5.1.4.4WAA shall notify transportation operators and information providers when public notification is no longer required.
5.3DISASTER RESPONSE AND EVACUATION
5.3.0ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.2Disaster Response shall provide a Monitor Alert Levels (MAL) function.
5.3.2.2MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.2.2(c)Review and update resource inventories
5.3.2.2(f)Clear obstructions
5.3.4Disaster Response shall provide an Assess Infrastructure Status (AIS) function.
5.3.4.1AIS shall assess the impact of the disaster on the transportation infrastructure and associated ITS systems using:
5.3.4.1(a)Asset Management Systems
5.3.4.1(b)Surveillance systems and sensors
5.3.4.1(c)Built-in-test of electronic systems
5.3.4.1(d)On-scene reports and inspections
5.3.4.1(e)Information gathered by aerial surveillance.
5.3.4.2AIS shall provide an assessment of transportation infrastructure damage to transportation, emergency management, public safety, and other allied agencies.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.1Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.2MVFM shall be capable of supporting route scheduling and dispatching of public and contracted fleets of maintenance, construction, and specialized service vehicles.
8.1.1.3MVFM shall be capable of supporting interactive data communications between dispatchers and operators of public and contracted maintenance, construction, and specialized service vehicles.
8.1.1.3.1MVFM shall be capable of communicating information to vehicle operators, including but not limited to:
8.1.1.3.1(a)Routing information
8.1.1.3.1(b)Scheduling data
8.1.1.3.1(c)Dispatch instructions
8.1.1.3.1(d)Corrective actions
8.1.1.3.1(e)Environmental information (road and weather conditions)
8.1.1.6MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a)Congestion
8.1.1.6.1(b)Incidents
8.1.1.6.1(c)Roadway restrictions
8.1.1.6.5MVFM shall provide information to the vehicle operators concerning roadway problem spots and alternate routes because of potential or actual roadway problems.
8.1.1.6.6MVFM shall support transmission of fleet operations data to other Operations centers.
8.1.1.6.7MVFM shall support transmission of fleet operations data to archives.
8.1.2Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations.
8.1.2.1RWM shall support a number of different services, including but not limited to:
8.1.2.1(a)Winter maintenance (plowing, treating, anti-icing, de-icing, etc.)
8.1.2.1(b)Hazard removal (removing trash, animals, etc.)
8.1.2.1(c)Emergency activities (incident response, planning, alternate routing, etc.)
8.1.2.1(d)Routine maintenance activities (cleaning, cutting, etc.)
8.1.2.1(e)Repair activities
8.1.2.1(f)Other weather related activities (fog dispersion, etc.)
8.1.2.4RWM shall determine the need for forecasted and scheduled roadway treatment.
8.1.2.4.4RWM shall make use of information on usage of treatments and materials.
8.1.2.5RWM shall support management of resources to perform hazardous road condition remediation.
8.1.2.5.1RWM shall support application of materials, plowing, and other means to counteract adverse winter weather conditions.
8.1.2.5.2RWM shall support appropriate responses to other environmental conditions that effect travel.
8.1.2.6RWM shall track the amount of materials applied to the roadway for comparison to planned / forecasted requirements.
8.1.2.7RWM shall monitor the amount and availability of materials at storage facilities.
8.1.2.9RWM shall monitor, manage, and control remotely located, automated systems, that affect the roadway surface (e.g. de-icing/anti-icing applications).
8.1.3Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers.
8.1.3.1WZMS shall monitor, control, and direct activity in the vicinity of work zones.
8.1.3.1.1WZMS shall provide information about work zones, including but not limited to:
8.1.3.1.1(a)Anticipated delays
8.1.3.1.1(b)Alternate routes
8.1.3.1.1(c)Suggested speed limit
8.1.3.2WZMS shall support the management of data about work zones.
8.1.3.2.1WZMS shall collect information concerning work zone activities, including but not limited to:
8.1.3.2.1(a)Location
8.1.3.2.1(b)Nature / type
8.1.3.2.1(c)Scheduled start time
8.1.3.2.1(d)Duration
8.1.3.2.1(e)Lane shifts
8.1.3.2.1(f)Staging areas
8.1.3.2.1(g)Length of work zone
8.1.3.2.1(h)Scheduled phases of work zone configuration
8.1.3.2.1(i)Alternate routes
8.1.3.2.1(j)Anticipated delays for travel route
8.1.3.2.1(k)Anticipated delays for diversion route
8.1.3.2.2WZMS shall correlate planned activities with actual work.
8.1.3.2.3WZMS shall support preparation of reports on work zone activities.
8.1.3.2.4WZMS shall provide information on work zone activities to other agencies, including but not limited to:
8.1.3.2.4(a)Other maintenance and construction operations systems
8.1.3.2.4(b)Commercial vehicle fleets
8.1.3.2.4(c)Emergency vehicle fleets
8.1.3.2.4(d)Traveler information systems
8.1.3.2.4(e)Traffic management systems
8.1.3.3WZMS shall provide systems that communicate reliable, accurate, and timely traveler information, including but not limited to:
8.1.3.3(a)Location, including lane closure information
8.1.3.3(b)Alternate route / detour
8.1.3.3(c)Work zone speed limit
8.1.3.3(d)Delay
8.1.4Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers.
8.1.4.1RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished.
8.1.4.2RMCWP shall support inter-agency coordination of response and scheduling of resources for significant events with broad impact, like natural disasters, major incidents, and large planned or seasonal events.
8.1.4.3RMCWPD shall coordinate information with other transportation agencies, including but not limited to:
8.1.4.3(a)Public Safety
8.1.4.3(b)Emergency Medical Management
8.1.4.3(c)Transit
8.1.4.3(d)Traffic Management
8.1.4.3(g)Information Service Providers
8.1.4.3(h)Transportation Asset Management (Pavement management, bridge management, etc)
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.