| 2.0 | PUBLIC TRANSPORTATION MANAGEMENT |
| 2.1 | PUBLIC TRANSPORTATION MANAGEMENT |
| 2.1.0 | ITS shall include a Public Transportation Management (PTM) function. |
| 2.1.1 | PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities. |
| 2.1.1.1 | To enable the automation of the vehicle and facilities operations OVF shall provide the capability to gather the needed data to include, but not be limited to, the following: |
| 2.1.1.1(a) | Vehicle passenger loading by bus stop and trip segment. |
| 2.1.1.1(b) | Bus running times between time points. |
| 2.1.1.1(e) | Mileage accumulated by individual buses. |
| 2.1.1.2 | OVF shall include a Command and Control (CC) capability. |
| 2.1.1.2.1 | CC shall provide the capability for real-time Vehicle Command and Control (VCC). |
| 2.1.1.2.1.1 | VCC shall provide the capability to compare received information with predetermined operating condition specifications and note any deviations. |
| 2.1.1.2.1.4 | VCC shall provide the capability to automatically issue corrective instructions to the operator including, but not limited to, the following: |
| 2.1.1.2.2 | When CC detects a vehicle(s) has deviated from schedule it shall provide the capability to automatically determine the optimum scenario for returning the vehicle or fleet to schedule. |
| 2.1.1.2.3 | CC shall include an integrated traffic control capability that provides traffic signal preemption when required for schedule adjustment to Transit Vehicles at traffic signals (i.e., centralized or distributed). |
| 2.1.1.2.4 | CC shall include the capability for its computational capabilities to be located either on-vehicle and/or at remote locations. |
| 2.1.2 | PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations. |
| 2.1.2.1 | The PSS shall include a Planning capability. |
| 2.1.2.1.1 | PSS Planning shall be performed off-line from stored data that were collected in real-time. |
| 2.1.2.1.2 | PSS Planning shall include processing of the data in a manner that will permit improvements in routes and services. |
| 2.1.2.2 | The PSS shall include a Schedule Generation capability. |
| 2.1.2.2.1 | The PSS Schedule Generation function shall collect data for schedule generation including, but not limited to, the following: |
| 2.1.2.2.1(c) | Revenue information. |
| 2.1.2.2.2 | The PSS Schedule Generation function shall use the collected data in the automatic or semiautomatic development of transportation system schedules. |
| 2.1.2.2.3 | The PSS Schedule Generation function shall provide the capability to print schedules. |
| 2.1.2.2.4 | The PSS Schedule Generation function shall provide the capability to disseminate schedules to, but not be limited to, the following: |
| 2.1.2.2.4(a) | Kiosks. |
| 2.1.2.2.4(b) | Transportation Management Centers. |
| 2.1.2.2.5 | The PSS Schedule Generation function shall provide the capability to automatically update the customer service operator system with the most current schedule and schedule adherence information. |
| 2.1.3 | PTM shall include a Personnel Management (PM) function to facilitate the management of operator, and maintenance personnel. |
| 2.1.3.2 | PM shall include an Operator Personnel Management (OPM) function. |
| 2.1.3.2.2 | OPM shall assign vehicle operators to routes and runs in a fair manner while minimizing labor and overtime costs. |
| 2.1.3.2.3 | In generating fair vehicle operator assignments, OPM shall include factors relating to operators' preferences and qualifications to include, but not be limited to, the following: |
| 2.1.3.2.3(a) | Seniority. |
| 2.1.3.2.3(b) | Operator schedule preference. |
| 2.1.3.2.3(c) | Garage assignment. |
| 2.1.3.2.3(d) | Vehicle qualification. |
| 2.1.3.2.4 | OPM shall automatically track and validate the number of work hours performed by each individual vehicle operator. |
| 2.1.3.2.5 | OPM shall provide the capability for authentication of vehicle operators prior to operating a transit bus or rail vehicle. |
| 2.2.0 | ITS shall include an En-Route Transit Information (TI) function. En-Route Transit Information provides travelers with real-time transit and high-occupancy vehicle information allowing travel alternatives to be chosen once the traveler is en-route. It consists of three major functions, which are, (1) Information Distribution, (2) Information Receipt, and (3) Information Processing. This capability integrates information from different transit modes and presents it to travelers for decision making. |
| 2.2.1 | TI shall include an Information Distribution function that disseminates information to travelers. |
| 2.2.1.1 | Information Distribution shall include an Information Network capability. |
| 2.2.1.1.4 | The Information Network shall provide all users with information that is from a single source in order to ensure consistency across all users. |
| 2.3.0 | ITS shall include a Personalized Public Transit (PPT) function. |
| 2.3.2 | The PPT shall include a Vehicle Assignment function. |
| 2.3.2.2 | For random route operations Vehicle Assignment shall assign trip origin and destination. |
| 2.3.2.3 | For flexible route operations Vehicle Assignment shall control how fixed route buses are detoured. |
| 2.3.4 | The PPT shall include an Information Processing function. |
| 2.3.4.3 | Information Processing shall provide the capability to automate the assignment of drivers to vehicles. |
| 2.4 | PUBLIC TRAVEL SECURITY |
| 2.4.4 | PTS shall include a Security Management and Control (SMC) function. |
| 2.4.4.7 | SMC shall include the capability to identify when a transit vehicle has deviated from its assigned route. |
| 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.1.5 | ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive. |
| 5.1.5.1 | PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted. |
| 5.1.5.2 | The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected. |
| 5.1.5.3 | PSTI shall restrict access to traveler information for the affected area until access restrictions are removed. |
| 5.1.5.4 | PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed. |
| 8.0 | MAINTENANCE AND CONSTRUCTION MANAGEMENT |
| 8.1 | MAINTENANCE AND CONSTRUCTION OPERATIONS |
| 8.1.0 | ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities. |
| 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.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.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.2 | MVFM shall be capable of filtering, fusing, processing, and presenting data from multiple weather and environmental sources. |
| 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.6 | MVFM shall support transmission of fleet operations data to other Operations centers. |
| 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.2 | RWM shall support provision of efficient and effective roadway operations during normal and severe weather or adverse travel conditions. |
| 8.1.2.4 | RWM shall determine the need for forecasted and scheduled roadway treatment. |
| 8.1.2.4.1 | RWM shall be capable of filtering, fusing, processing and presenting data from multiple weather and environmental sources. |
| 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.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.1.3 | WZMS shall be able to divert vehicles around work zones via automated lane changing techniques. |
| 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.3.2.4 | WZMS shall provide information on work zone activities to other agencies, including but not limited to: |
| 8.1.3.2.4(e) | Traffic management systems |
| 8.1.3.3 | WZMS 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.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(c) | Transit |
| | |
Web Spinner Technology.