| 1.0 | TRAVEL AND TRAFFIC MANAGEMENT |
| 1.1.0 | ITS shall provide a Pre-Trip Travel Information (PTTI) capability. to assist travelers in making mode choices, travel time estimates, and route decisions prior to trip departure. It consists of four major functions, which are, (1) Available Services Information, (2) Current Situation Information, (3) Trip Planning Service, and (4) User Access. Information is integrated from various transportation modes and presented to the user for decision making. |
| 1.1.1 | PTTI shall provide travelers with information on those travel services available for their use. |
| 1.1.1.1 | PTTI shall provide users with available services information that is timely. |
| 1.1.1.1.1 | PTTI shall provide users the latest available information on transit routes. |
| 1.1.1.1.2 | PTTI shall provide users the latest available information on transit schedules. |
| 1.1.1.1.3 | PTTI shall provide users with real time schedule adherence information. |
| 1.1.1.1.4 | PTTI shall provide users the latest available information on transit transfer options. |
| 1.1.1.1.5 | PTTI shall provide users the latest available information on transit fares. |
| 1.1.1.1.6 | PTTI shall provide users information on accessing ridematching services. |
| 1.1.2 | PTTI shall provide the capability for users to access information on the current condition of transportation systems. |
| 1.1.2.1 | PTTI transportation services current situation information shall be provided in real-time. |
| 1.1.2.1.1 | Real-time information provided by PTTI shall include the current condition of any incidents. |
| 1.1.2.1.2 | Real-time information provided by PTTI shall include the current status of any accidents or incidents. |
| 1.1.2.1.3 | Real-time information provided by PTTI shall include the current condition of any road construction. |
| 1.1.2.1.4 | Real-time information provided by PTTI shall include any currently recommended alternate routes. |
| 1.1.2.1.5 | Real-time information provided by PTTI shall include the current speeds on specific routes. |
| 1.1.2.1.6 | Real-time information provided by PTTI shall include current parking conditions in key areas. |
| 1.1.2.1.7 | Real-time information provided by PTTI shall include the schedules for any current or soon to start events. |
| 1.1.2.1.8 | Real-time information provided by PTTI shall include the current weather situation. |
| 1.1.3 | PTTI shall include a trip planning service. |
| 1.1.3.1 | PTTI trip planning service shall provide the users with information needed for planning an upcoming trip. |
| 1.1.3.1.1 | Based on user specified parameters PTTI shall provide users with a calculated itinerary. |
| 1.1.3.1.2 | Based on user specified parameters PTTI shall provide users with transportation mode choices. |
| 1.1.3.1.3 | Based on user specified parameters PTTI shall provide users with real-time travel conditions for time of inquiry and estimated conditions for estimated time of travel. |
| 1.1.3.1.4 | Based on user specified parameters PTTI shall provide users with one or more alternate itineraries in addition to the primary calculated itinerary. |
| 1.1.3.2 | PTTI shall provide the capability for users to specify those transportation parameters that are unique to their individual needs. |
| 1.1.3.3 | In addition to the user specified parameters PTTI shall use additional factors when planning trips. |
| 1.1.3.3.1 | PTTI shall consider current travel conditions when calculating a trip itinerary. |
| 1.1.3.3.2 | PTTI shall consider predicted travel conditions when calculating a trip itinerary. |
| 1.1.4 | PTTI shall provide the capability for user access. |
| 1.1.4.1 | PTTI shall provide the capability for users to access the system from multiple distributed locations. |
| 1.1.4.1.1 | PTTI shall provide the capability for users to access the system from their homes. |
| 1.1.4.1.2 | PTTI shall provide the capability for users to access the system from their place of work. |
| 1.1.4.1.3 | PTTI shall provide the capability for users to access the system from other major trip generation sites. |
| 1.2.0 | ITS shall include an En-Route Driver Information (DI) function. Driver Information provides vehicle drivers with information, while en-route, which will allow alternative routes to be chosen for their destination. Driver Information consists of two major functions which are (1) Driver Advisory and (2) In-vehicle Signing. The potential decrease in traffic may also provide benefits in highway safety, reduced air pollution, and decreased congestion. |
| 1.2.2 | Driver advisory shall be implemented in two phases with first a short term capability and later a long term capability. |
| 1.2.2.1 | The short term DI driver information capability shall include the ability to provide information to travelers within the limited area of deployment. |
| 1.2.2.1.1 | DI shall include the capability to provide travelers with accurate information concerning available travel options and their state of operational availability. |
| 1.2.2.1.2 | DI shall provide that information to travelers required for them to avoid areas of congestion. |
| 1.2.2.1.2.1 | DI shall provide that information needed for travelers to select those transportation modes that allow them to avoid congestion. |
| 1.2.2.1.3 | DI shall provide the capability for users to receive travel information in their vehicles. |
| 1.3 | ROUTE GUIDANCE |
| 1.3.0 | ITS shall include a Route Guidance (RG) function. Route Guidance will provide travelers with directions to selected destinations. Four functions are provided which are (1) Provide Directions, (2) Static Mode, (3) Real-Time Mode, and (4) User Interface. |
| 1.3.1 | RG shall include the capability to Provide Directions to travelers. |
| 1.3.1.2 | The Provide Directions function shall issue directions to travelers that is based on information about current conditions of transportation systems. |
| 1.3.1.2.1 | Current transportation system conditions upon which directions to travelers is based shall include, but not be limited to, the following: |
| 1.3.1.2.1(c) | Schedules of transit systems. |
| 1.3.2 | RG shall include a Static Mode for issuing information to travelers. |
| 1.3.2.1 | Static Mode shall provide travelers with information that includes, but is not limited to, the following: |
| 1.3.2.1(a) | Mapping information about roadways. |
| 1.3.3 | RG shall include a Real-Time Mode for issuing information to travelers. |
| 1.3.3.2 | The Real-Time Mode shall include the capability to operate in either or both of the following two configurations: |
| 1.3.3.2.1 | Real-Time Mobile Based systems shall include the capability to receive infrastructure information, when available, and use it in determining routing. |
| 1.4 | RIDE MATCHING AND RESERVATION |
| 1.4.0 | ITS shall include a Ride Matching and Reservation (RMR) function. Ride Matching and Reservation will provide travel users with information on rideshare providers. Three major functions are provided which are (1) Rider Request, (2) Transportation Provider Services, and (3) Information Processing. This will also include a billing service to the providers. |
| 1.4.1 | RMR shall include a Rider Request capability. |
| 1.4.1.1 | Rider Request shall provide the capability for a traveler to request a ride by placing a single request from a facility to include, but not be limited to, the following: |
| 1.4.1.2 | Rider Request shall provide a traveler the capability to request a specific itinerary by specifying, but not be limited to, the following: |
| 1.4.1.2(a) | Date. |
| 1.4.1.3 | Based on the traveler's request and specified itinerary, Rider Request shall provide the traveler with the available ridesharing options. |
| 1.4.1.4 | Rider Request shall also include the capability to perform real-time ridematching by instantly matching rider and driver. |
| 1.4.2 | RMR shall include an Transportation Provider Service function. |
| 1.4.2.1 | Transportation Provider Services shall include the capability for providers to have their billing arranged through a central clearinghouse. |
| 1.4.2.3 | Transportation Provider Services shall automatically generate needed reports and financial documentation. |
| 1.4.2.4 | Transportation Provider Services shall include the capability for commercial operators such as vanpools and taxis to be included as options for requesting travelers. |
| 1.4.3 | RMR shall include an Information Processing function. |
| 1.4.3.1 | Information Processing shall quickly match preferences and demands of requesting travelers with the services available from providers. |
| 1.4.3.2 | Information Processing shall provide a clearinghouse capability for rideshare financial transactions. |
| 1.4.3.3 | Information Processing shall link together the services available from all travel modes including, but not limited to, the following: |
| 1.4.3.3(a) | Bus. |
| 1.4.3.3(b) | Rail. |
| 1.4.3.3(c) | Vanpools. |
| 1.4.3.5 | Information Processing shall provide the capability to gather that market information needed to assist in the planning of service improvements. |
| 1.4.3.6 | Information Processing shall provide the capability to gather that market information needed to assist in maintenance of operations. |
| 1.4.4.3(d) | Express bus. |
| 1.4.4.3(e) | Commercial providers. |
| 1.4.4.3(f) | Specialized service. |
| 1.5.0 | ITS shall include a Traveler Services Information (TSI) function. Traveler Services Information provides travelers with service and facility data for the purpose of assisting prior to embarking on a trip or after the traveler is underway. The functions which are included in this capability are Information Receipt and Information Access. This will provide the traveler with a "yellow pages" type of capability. |
| 1.5.1 | TSI shall include an Information Receipt function for the collection of that information provided to travelers. |
| 1.5.1.1 | Information Receipt shall provide and maintain a database of local area services available to travelers. |
| 1.5.1.2 | Information Receipt provides the capability to acquire up to the minute information relating to traveler services available in the local area. |
| 1.5.1.2.1 | Information Receipt shall acquire information on the condition of local traveler services. |
| 1.5.1.2.2 | Information Receipt shall acquire information on the status of local traveler services. |
| 1.5.1.2.3 | Information Receipt shall acquire information on the availability of local traveler services. |
| 1.5.1.2.4 | Information Receipt shall acquire information on the availability of local motorist services. |
| 1.5.1.2.5 | Information Receipt shall acquire information on the availability of local tourist services. |
| 1.5.1.3 | Information Receipt shall be capable of being integrated with Pre-Trip Planning information. |
| 1.5.1.4 | Information Receipt shall provide the capability to support those financial transactions required for travelers to be billed for the purchase of activity tickets and room reservations. |
| 1.5.1.5 | Information Receipt shall include the capability to have interactive connectivity between users, sponsors and providers of services. |
| 1.5.2 | TSI shall include an Information Access function that allows travelers to access the available information. |
| 1.5.2.1 | Information Access shall provide the capability for travelers to request and receive general information about the local area. |
| 1.5.2.2 | Information Access shall provide the capability for travelers to request and receive information about specific services in an area to include but, not be limited to, the following: |
| 1.5.2.2(a) | Lodging information. |
| 1.5.2.2(b) | Food information. |
| 1.5.2.2(d) | Hours of operation information. |
| 1.5.2.2(e) | Tourist activities information. |
| 1.5.2.2(f) | Daily or special events information. |
| 1.5.2.2(g) | Local hospital information. |
| 1.5.2.2(h) | Nearest gas station information. |
| 1.5.2.3 | Information Access shall provide the capability for travelers to request specific actions of area service providers to include, but not be limited to: |
| 1.5.2.3(a) | Lodging reservations. |
| 1.5.2.3(b) | Dining reservations. |
| 1.5.2.4 | Information Access shall provide the capability for all travelers to access information regardless of their particular mode of travel. |
| 1.6 | TRAFFIC CONTROL |
| 1.6.4 | The Control Function shall provide traffic control information to other elements of the ITS, including but not limited to the following: |
| 1.6.4(b) | Trip planning. |
| 1.6.4(c) | Routing systems. |
| 1.7 | INCIDENT MANAGEMENT |
| 1.7.0 | ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Six major functions are provided which are (1) Scheduled Planned Incidents, (2) Identify Incidents, (3) Formulate response Actions, (4) Support Coordinated Implementation of Response Actions, (5) Support Initialization of Response to Actions, and (6) Predict Hazardous Conditions. |
| 1.7.1 | Incident Management shall provide an incident identification function to identify incidents. |
| 1.7.1.1 | The incident identification function shall include the capability to identify predicted incidents. |
| 1.7.1.1.1 | The incident identification function shall use information from the following types of sources, where available, to identify predicted incidents: |
| 1.7.1.1.1(e) | Weather information sources. |
| 1.7.1.1.1(f) | Transportation providers. |
| 1.7.1.1.1(g) | Sponsors of special events. |
| 1.7.4 | Incident Management shall provide the capability to predict the time and location of hazardous conditions that may cause an incident. |
| 1.8 | TRAVEL DEMAND MANAGEMENT |
| 1.8.1 | TDM shall include a communications function. |
| 1.8.1.2 | The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action: |
| 1.8.1.2(d) | Employment sites. |
| 1.8.1.2(e) | Toll facilities. |
| 1.8.1.3 | TDM shall provide the capability to receive information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action: |
| 1.8.1.3(a) | Parking facilities. |
| 1.8.1.3(e) | Toll facilities. |
| 1.8.1.3(f) | Travel (and traveler) information facilities. |
| 1.8.1.6 | The communications function shall include the capability for two-way communications with other ITS user services including, but not limited to, the following: |
| 1.8.1.6(a) | Pre-Trip Planning. |
| 1.8.2 | TDM shall include a processing function. |
| 1.8.2.3 | Strategies developed by the processing function shall include the guidance for the operation of physical systems that: |
| 1.8.2.3(c) | Collect fees. |
| 1.8.2.4 | The processing shall provide the capability generate guidance for the pricing and control for locations of action that include, but are not limited to, the following: |
| 1.8.2.4(a) | Parking facilities. |
| 1.8.2.4(f) | Travel information facilities. |
| 2.0 | PUBLIC TRANSPORTATION MANAGEMENT |
| 2.2 | EN-ROUTE TRANSIT INFORMATION |
| 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.1 | The Information Network shall provide the capability to furnish users with real-time travel related information while they are traveling. |
| 2.2.1.1.3 | The Information Network shall provide the capability to disseminate information to travelers that will assist them in making decisions in the modification (includes both intermode and intramode) of their trips. |
| 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.2.2 | TI shall include an Information Receipt function for acquiring that data that are used for generation of the En-Route Transit Information. |
| 2.2.2.1 | Information Receipt shall provide the capability to be continuously updated with real-time information from each transit system within the local area of jurisdiction. |
| 2.2.2.2 | Information Receipt shall provide the capability to be updated with information that is inclusive of all possible transportation modes within the local area of jurisdiction. |
| 2.2.2.3 | Information Receipt shall provide the capability to be updated with information from all providers of transportation services in the local area of jurisdiction to include: |
| 2.2.2.3(a) | Regional Paratransit services. |
| 2.2.2.3(b) | Public providers. |
| 2.2.2.3(c) | Private providers. |
| 2.2.3 | TI shall include an Information Processing function for processing that data used for generation of the En-Route Transit Information. |
| 2.2.3.1 | Information Processing shall include an information collection feature. |
| 2.2.3.1.1 | Information Collection shall acquire transit operations information to include, but not be limited to, the following type: |
| 2.2.3.1.1(a) | Schedule. |
| 2.2.3.1.1(b) | Actual service provided. |
| 2.2.3.1.1(c) | Next available vehicle; based on actual operating conditions. |
| 2.2.3.1.1(d) | Transfer options describing available services and their associate schedules. |
| 2.2.3.1.2 | Information Collection shall acquire transit situation conditions to include, but not be limited to, the following type: |
| 2.2.3.2 | Information Processing shall include an information integration feature. |
| 2.2.3.2.1 | Information Integration shall collect data, store it and maintain it on-line. |
| 2.2.3.2.2 | Information Integration shall collect data from traffic and transit systems including, but not limited to, the following: |
| 2.2.3.2.2(a) | Transit systems. |
| 2.2.3.2.2(b) | Traffic management services. |
| 2.2.3.2.2(c) | Rideshare programs. |
| 2.3 | PERSONALIZED PUBLIC TRANSIT |
| 2.3.0 | ITS shall include a Personalized Public Transit (PPT) function. |
| 2.3.1 | The PPT shall include a Rider Request function. |
| 2.3.1.2 | Rider Request shall provide the capability for an individual to specify a rider's special equipment or handling requirements. |
| 2.3.4 | The PPT shall include an Information Processing function. |
| 2.4.0 | ITS shall include a Public Travel Security (PTS) function to create an environment of safety in public transportation. |
| 2.4.3 | PTS shall include a Personal Sensors Items (PSI) function. |
| 2.4.3.1 | PSI for ridematching shall include the capability for participants to be identified. |
| 2.4.3.2 | PSI shall provide the capability for riders to use electronic payment to eliminate the need for passengers to carry cash and to reduce cash handling. |
| 3.0 | ELECTRONIC PAYMENT |
| 3.1 | ELECTRONIC PAYMENT SERVICES |
| 3.1.0 | ITS shall include an Electronic Payment capability. Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions are provided which are (1) Electronic Toll Collection, (2) Electronic Fare Collection, (3) Electronic Parking Payment, and (4) Electronic Payment Services Integration. |
| 3.1.1 | Electronic Payment shall provide an Electronic Toll Collection (ETC) capability. |
| 3.1.1.3 | ETC shall provide confirmation of the transaction to each customer. |
| 3.1.2 | Electronic Payment shall include an Electronic Fare Collection (EFC) capability. |
| 3.1.2.1 | EFC shall be implemented in a manner that the traveler is able to use a compatible fare medium for all applicable surface transportation services. |
| 3.1.2.4 | EFC shall provide the capability for third party payment of transportation services. |
| 3.1.2.6 | EFC shall be implemented in a manner that permits expansion into other uses for the payment medium such as payment of retail, telephone, etc. |
| 3.1.2.7 | EFC shall include the capability to collect that data that are required to determine accurate ridership levels. |
| 3.1.3 | Electronic Payment shall include an Electronic Parking Payment (EPP) capability. |
| 3.1.3.1 | EPP shall provide the capability to pay for parking without the use of cash. |
| 3.1.3.2 | EPP shall include the capability for transit operators to utilize a single medium to charge for both transit related charges and parking charges. |
| 3.1.4 | ITS shall include an Electronic Payment Services Integration (EPSI) feature. |
| 3.1.4.1 | EPSI shall provide the capability to combine electronic payments made for use of various transportation modes into a single integrated system. |
| 3.1.4.2 | EPSI shall provide the capability to integrate fare and toll pricing structures of multiple agencies. |
| 3.1.4.3 | EPSI shall collect and provide that usage data needed to develop pricing strategies that favor certain transportation modes or routes. |
| 3.1.5 | ITS shall provide a Roadway Pricing (RP) capability. |
| 3.1.5.1 | RP shall provide the capability to implement various road pricing policies. |
| 3.1.5.1.1 | Road pricing policies capable of being implemented by RP shall include variable pricing. |
| 3.1.5.2 | RP shall provide the capability to implement roadway pricing strategies, developed by other services, that alleviate congestion. |
| 3.1.5.3 | RP shall provide the capability to implement roadway pricing, developed by other services, that can be used to influence mode selection. |
| 4.0 | COMMERCIAL VEHICLE OPERATIONS |
| 4.1 | COMMERCIAL VEHICLE ELECTRONIC CLEARANCE |
| 4.1.0 | ITS shall include a Commercial Vehicle Electronic Clearance (CVEC) capability. |
| 4.1.2 | CVEC shall include a Vehicle System capability |
| 4.1.2.2 | Vehicle System shall provide the capability for each vehicle to establish two-way communications with fixed facilities. |
| 7.0 | Information Management |
| 7.1 | Archived Data Function |
| 7.1.0 | ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas. |
| 7.1.3 | The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function. |
| 7.1.3.1 | DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories. |
| 7.1.3.1.8 | DIV shall be capable of importing ITS Vehicle and Traveler data to include: |
| 7.1.3.1.8(e) | Parking and roadway pricing change data. |
| 7.1.3.1.8(g) | Service requests |
| 7.1.3.1.8(h) | Information utilization |
| | |
