| 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.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. |
| 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(a) | Commercial and non-commercial vehicle probe data. |
| 7.1.3.1.8(c) | Vehicle trajectories. |
| 7.1.3.1.8(d) | Route guidance data. |
| 7.1.3.1.8(e) | Parking and roadway pricing change data. |
| 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.