| 1.0 | TRAVEL AND TRAFFIC MANAGEMENT |
| 1.1 | PRE-TRIP TRAVEL INFORMATION |
| 1.1.0 | ITS shall include 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.2 | PTTI shall provide the capability for users to access the Current Situation Information on transportation systems. |
| 1.1.2.1 | PTTI shall provide the latest available information on the current status of transportation services. |
| 1.1.2.1.1 | Real-time information provided by PTTI shall include the current condition of any incidents, including rural incidents such as high winds, extreme temperature, and falling rocks. |
| 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.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 major trip generation sites. |
| 1.1.4.1.4 | PTTI shall provide the capability for users to access the system from personal portable devices. |
| 1.2 | EN-ROUTE DRIVER INFORMATION |
| 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 | DI shall include a Driver Advisory function, which 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 information to travelers required for them to avoid areas of congestion. |
| 1.2.2.1.2.1 | DI shall provide information needed for travelers to select 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 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(b) | Status of transit systems. |
| 1.3.1.2.1(c) | Schedules of transit systems. |
| 1.3.1.2.1(d) | Events taking place that influence travel routes. |
| 1.3.1.2.1(d).1 | Street closures. |
| 1.3.1.2.1(d).2 | Pedestrian events. |
| 1.3.1.2.1(d).3 | No pedestrian zones. |
| 1.3.1.3 | The Provide Directions function shall issue traveler directions that are simple and easy to understand, providing turning instructions on which way to turn onto including, but not limited to, the following: |
| 1.3.1.3(c) | Walkways. |
| 1.3.1.3(d) | Transit facilities. |
| 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.2.2 | Static Mode infrastructure systems shall provide the capability to have two-way communications between the traveler and the infrastructure. |
| 1.3.2.2.2 | The two-way communications shall provide the capability to provide directions back to the traveler that are based on the infrastructure's calculated routing. |
| 1.3.3 | RG shall include a Real-Time Mode for issuing information to travelers. |
| 1.3.3.1 | The Real-Time Mode shall utilize current travel condition information to provide performance that is enhanced over the Static Mode performance, to include, but not be limited to, the following: |
| 1.3.3.1(b) | Dynamic transit schedule information. |
| 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 Mode Mobile Based systems shall include the capability to receive infrastructure information and use it in determining routing. |
| 1.3.3.2.2 | If current real-time information is included in route determination, the system shall be denoted as an Infrastructure-based real-time system. |
| 1.3.4 | RG shall include a User Interface function. |
| 1.3.4.2 | Mobile systems shall use the best information available to provide routing instructions. |
| 1.3.4.2.1 | Mobile systems shall provide the capability for individual travelers to customize the routing selected for them. |
| 1.3.4.3 | Infrastructure-based systems shall permit individual travelers to customize their routing selection. |
| 1.3.4.3.1 | Infrastructure-based systems shall use the traveler's destination information to estimate extra demand on the transportation system and then provide routing to the traveler based on this predicted demand. |
| 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.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 a 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.2 | Transportation Provider Services shall include electronic safeguards against fraud and abuse. |
| 1.4.2.3 | Transportation Provider Services shall automatically generate needed reports and financial documentation. |
| 1.4.3 | RMR shall include an Information Processing function. |
| 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(f) | Specialized service. |
| 1.4.3.3(g) | Carpools. |
| 1.4.3.5 | Information Processing shall provide the capability to gather market information to assist in the planning of service improvements. |
| 1.4.3.6 | Information Processing shall provide the capability to gather market information to assist in operations. |
| 1.5 | TRAVELER SERVICES INFORMATION |
| 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 information to be 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 current 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 the 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 and centers to request and receive information about the location of facilities and the quality of specific services provided in an area to include but, not be limited to, the following: |
| 1.5.2.2(b) | Food 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 shelter/medical facility availability information including level of service provided. |
| 1.5.2.2(i) | Local care facility 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.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.0 | ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control. |
| 1.6.3 | TC shall include a Device Control function. |
| 1.6.3.4 | Device Control shall communicate control data to the following devices. |
| 1.6.3.4.1 | Traffic Surveillance shall include a data process function to process the traffic data which are acquired. |
| 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. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) 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.4 | IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident. |
| 1.8 | TRAVEL DEMAND MANAGEMENT |
| 1.8.0 | ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options. |
| 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(g) | Ridesharing 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(d) | Employment sites. |
| 1.8.1.3(g) | Ridesharing facilities. |
| 1.8.2 | TDM shall include a processing function. |
| 1.8.2.1 | The processing function shall provide the capability to generate management and control strategies that facilitate the implementation of policies and regulations designed to address the following: |
| 1.8.2.1(d) | Ridesharing and transit. |
| 1.8.2.4 | The processing function 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(d) | Employment sites. |
| 1.8.2.4(g) | Ridesharing facilities. |
| 2.0 | 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.2 | PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations. |
| 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.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.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 associated 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. |
| 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 the data 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 usage data 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. |
| 5.0 | EMERGENCY MANAGEMENT |
| 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. |
| 5.2.0 | ITS shall include an Emergency Vehicle Management (EVM) Service. |
| 5.2.2 | EVM Service shall include a Route Guidance System. |
| 5.2.2.1 | Route Guidance System shall maintain real-time information on traffic conditions in urban and rural areas, emergency response vehicle locations, and emergency response vehicle destinations. |
| 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.10 | Evacuation Coordination shall include an Evacuation Traveler Information (ETI) function. |
| 5.3.10.1 | ETI shall be accessible to users from multiple distributed locations, including, but not limited to: |
| 5.3.10.1(a) | homes, |
| 5.3.10.1(b) | public buildings, |
| 5.3.10.1(c) | evacuation shelters, |
| 5.3.10.1(d) | rest areas, |
| 5.3.10.1(e) | hotels, |
| 5.3.10.1(f) | restaurants, |
| 5.3.10.1(g) | airports and other mode terminals, and |
| 5.3.10.1(h) | wireless devices (in-vehicle and handheld). |
| 5.3.10.2 | ETI shall identify mandatory and voluntary evacuation zones and any special evacuation requirements for each zone. |
| 5.3.10.3 | ETI shall provide a list of alternative evacuation destinations. |
| 5.3.10.4 | ETI shall provide shelter information including: |
| 5.3.10.4(a) | Location |
| 5.3.10.4(b) | Time of operation |
| 5.3.10.4(c) | Vacancy |
| 5.3.10.4(d) | Available facilities including accommodations for people with special needs, such as pets, disabilities and elderly. |
| 5.3.10.5 | ETI shall provide recommended evacuation and reentry route(s) based on: |
| 5.3.10.5(a) | Real-time and forecast traffic and road conditions. |
| 5.3.10.5(b) | Traveler-specified route parameters. |
| 5.3.10.6 | ETI shall provide the recommended evacuation start time for a selected evacuation origin and destination based on: |
| 5.3.10.6(a) | The travel time required for the trip. |
| 5.3.10.6(b) | The capability of the evacuation network to handle evacuation demand based on current and future network conditions. |
| 5.3.10.6(c) | The existing and forecast conditions at the evacuation origin and destination. |
| 5.3.10.7 | ETI shall identify reentry times for those jurisdictions that have cleared an area for reentry. |
| 5.3.10.8 | ETI shall provide road and traffic conditions on evacuation routes including: |
| 5.3.10.8(a) | Current and forecast speed and travel times |
| 5.3.10.8(b) | Incident information |
| 5.3.10.8(c) | Current and forecast road, bridge and lane closure information. |
| 5.3.10.8(d) | Advisories of hazardous conditions such as flooding, malfunctioning traffic signals, debris and falling objects. |
| 5.3.10.8(e) | Current and forecast weather information |
| 5.3.10.9 | ETI shall provide information for transportation modes including buses, airlines, trains, ferries, and ships Including: |
| 5.3.10.9(a) | The availability of transportation mode services. |
| 5.3.10.9(b) | Arrival and departure information for available transportation services. |
| 5.3.10.10 | ETI shall provide general evacuation guidance information to travelers, including guidance/tips for trip preparation, trip duration and trip return. |
| 5.3.10.11 | ETI shall provide information regarding traveler services available along evacuation routes and at evacuation destinations including: |
| 5.3.10.11(a) | Lodging, |
| 5.3.10.11(b) | Restaurants, |
| 5.3.10.11(c) | Stores, |
| 5.3.10.11(d) | Hospitals and medical services |
| 5.3.10.11(e) | Rest areas |
| 5.3.10.11(f) | Vehicle fueling stations |
| 5.3.10.12 | ETI shall provide emergency public information including diversion information and information on refuges of last resort and other safe havens if emergency termination of an in-progress evacuation is necessary. |
| 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.4 | DIV shall be capable of importing ITS Transit and Ridesharing data to include: |
| 7.1.3.1.4(c) | Rideshare requests. |
| 7.1.3.1.8 | DIV shall be capable of importing ITS Vehicle and Traveler data to include: |
| 7.1.3.1.8(c) | Vehicle trajectories. |
| 7.1.3.1.8(f) | Origin/destination trip data. |
| 7.1.3.1.8(g) | Service requests |
| 7.1.3.1.8(h) | Information utilization |
| | |
Web Spinner Technology.