|
MCM Roadway Maintenance and Construction Equipment Package
|
 |
Description:
|
Overall management and support for routine maintenance on the roadway or right-of-way. Includes landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment.
|
Included in:
|
City of Victoria Maintenance Dispatch
County Road and Bridge
Municipal PWD
TxDOT Yoakum District Area Engineers Offices
TxDOT Yoakum District Maintenance Sections
TxDOT Yoakum District Office - Maintenance
|
Functional Requirements:
|
| 1 | The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions. |
| 2 | The center shall respond to requests from emergency management and traffic management centers for hazard removal, field equipment repair, and other roadway maintenance. |
| 3 | The center shall exchange information with administrative systems to support the planning and scheduling of maintenance activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration. |
| 4 | The center shall provide emergency management and traffic management centers with information about scheduled maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. |
| 5 | The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs. |
| 6 | The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs. |
| 7 | The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway infrastructure or on maintenance and construction vehicles. |
| 8 | The center shall receive equipment availability and materials storage status information from storage facilities to support the scheduling of roadway maintenance and construction activities. |
| 9 | The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and construction activities. |
| 10 | The center shall collect current and forecast traffic and weather information from traffic management centers and weather service providers (such as the National Weather Service and value-added sector specific meteorological services). |
| 11 | The center shall dispatch and route maintenance and construction vehicle drivers and support them with route- specific environmental, incident, advisory, threat, alert, and traffic congestion information. |
| 12 | The center shall manage an interface with center personnel to accept vehicle systems control information and remotely control maintenance and construction vehicle on-board equipment. |
| 13 | The center shall track the status of roadway maintenance and construction activities by monioring collected data from the dispatched vehicles and equipment. |
| | |
|
User Service Requirements (fully or partially addressed):
|
| 5.0 | EMERGENCY MANAGEMENT |
| 5.1 | EMERGENCY NOTIFICATION AND PERSONAL SECURITY |
| 5.1.3 | ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas. |
| 5.1.3.4 | RSEM shall include a Monitor Alert Levels (MAL) function. |
| 5.1.3.4.3 | MAL shall increase system preparedness as the likelihood of an incident increases, including: |
| 5.1.4 | ENPS 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.1 | WAA shall notify transportation operators and information providers when an emergency situation occurs that requires public notification. |
| 5.1.4.1.1 | The 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.2 | The 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.2 | WAA 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.1 | WAA 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.3 | WAA 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.4 | WAA shall notify transportation operators and information providers when public notification is no longer required. |
| 5.3 | DISASTER RESPONSE AND EVACUATION |
| 5.3.0 | ITS 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.2 | Disaster Response shall provide a Monitor Alert Levels (MAL) function. |
| 5.3.2.2 | MAL 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.4 | Disaster Response shall provide an Assess Infrastructure Status (AIS) function. |
| 5.3.4.1 | AIS 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.2 | AIS shall provide an assessment of transportation infrastructure damage to transportation, emergency management, public safety, and other allied agencies. |
| 8.0 | MAINTENANCE AND CONSTRUCTION MANAGEMENT |
| 8.1 | MAINTENANCE AND CONSTRUCTION OPERATIONS |
| 8.1.1 | Maintenance 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.1 | MVFM shall be capable of monitoring and tracking the locations of public and contracted fleets of maintenance, construction, and specialized service vehicles to provide current location and status information. |
| 8.1.1.1.1 | MVFM shall be capable of monitoring and tracking the locations of fleets of maintenance, construction, and specialized service vehicles, including but not limited to: |
| 8.1.1.2 | MVFM shall be capable of supporting route scheduling and dispatching of public and contracted fleets of maintenance, construction, and specialized service vehicles. |
| 8.1.1.3 | MVFM 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.1 | MVFM 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.5 | MVFM shall be capable of using on-board vehicle sensors to monitor roadway conditions and vehicle functions, including but not limited to: |
| 8.1.1.5(a) | Environmental conditions |
| 8.1.1.6 | MVFM 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.1 | MVFM 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.1(d) | Environmental conditions |
| 8.1.1.6.3 | MVFM shall be capable of receiving fused weather and roadway information from external sources, including but not limited to: |
| 8.1.1.6.3(a) | Surface transportation sources |
| 8.1.1.6.3(b) | Weather service organizations |
| 8.1.1.6.4 | MVFM shall be capable of using fused weather and roadway information from external sources to aid in scheduling roadway maintenance and construction activities. |
| 8.1.1.6.5 | MVFM 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.6 | MVFM shall support transmission of fleet operations data to other Operations centers. |
| 8.1.1.6.7 | MVFM shall support transmission of fleet operations data to archives. |
| 8.1.1.6.8 | MVFM shall support the comparison of incident data with scheduled fleet activities. |
| 8.1.2 | Maintenance 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.1 | RWM 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.2 | RWM shall support provision of efficient and effective roadway operations during normal and severe weather or adverse travel conditions. |
| 8.1.2.3 | RWM shall plan and forecast, proactive and reactive, year-round roadway management activities. |
| 8.1.2.4 | RWM shall determine the need for forecasted and scheduled roadway treatment. |
| 8.1.2.4.2 | RWM shall be capable of receiving and fusing weather and roadway information from external sources, including but not limited to: |
| 8.1.2.4.2(a) | Surface transportation sources |
| 8.1.2.4.2(b) | Weather service organizations |
| 8.1.2.4.3 | RWM shall make use of information on current and forecast weather. |
| 8.1.2.4.4 | RWM shall make use of information on usage of treatments and materials. |
| 8.1.2.5 | RWM shall support management of resources to perform hazardous road condition remediation. |
| 8.1.2.5.1 | RWM shall support application of materials, plowing, and other means to counteract adverse winter weather conditions. |
| 8.1.2.5.2 | RWM shall support appropriate responses to other environmental conditions that effect travel. |
| 8.1.2.6 | RWM shall track the amount of materials applied to the roadway for comparison to planned / forecasted requirements. |
| 8.1.2.7 | RWM shall monitor the amount and availability of materials at storage facilities. |
| 8.1.2.8 | RWM shall support maintenance crew dispatching. |
| 8.1.2.9 | RWM shall monitor, manage, and control remotely located, automated systems, that affect the roadway surface (e.g. de-icing/anti-icing applications). |
| 8.1.3 | Maintenance 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.1 | WZMS shall monitor, control, and direct activity in the vicinity of work zones. |
| 8.1.3.1.1 | WZMS 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.2 | WZMS shall support the management of data about work zones. |
| 8.1.3.2.1 | WZMS 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.4 | Maintenance 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.1 | RMCWPD 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.2 | RMCWP 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.3 | RMCWPD 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(e) | Railroads |
| 8.1.4.3(f) | Airports |
| 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.
|
|
Web Spinner Technology.