Physical Object: Transportation Information Center
TIC Data Collection
Overview
'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers.
This functional object is included in the "Transportation Information Center" physical object.
This functional object is included in the following service packages:
- CVO09: Freight-Specific Dynamic Travel Planning
- PM01: Parking Space Management
- PM02: Smart Park and Ride System
- PM04: Regional Parking Management
- PM05: Parking Reservations
- PM06: Loading Zone Management
- PS10: Wide-Area Alert
- PS14: Disaster Traveler Information
- PT03: Dynamic Transit Operations
- PT04: Transit Fare Collection Management
- PT08: Transit Traveler Information
- ST10: Low Emissions Zone Management
- TI01: Broadcast Traveler Information
- TI02: Personalized Traveler Information
- TI03: En-Route Guidance
- TI04: Trip Planning and Payment
- TI06: Shared Use Mobility and Dynamic Ridesharing
- TI08: Personal Wayfinding
- TI09: Travel Services Information and Reservation
- TM09: Integrated Decision Support and Demand Management
- TM10: Electronic Toll Collection
- TM11: Road Use Charging
- TM15: Railroad Operations Coordination
- TM23: Border Management Systems
- VS07: Road Weather Motorist Alert and Warning
- VS18: Vulnerable Road User Clustering
- WX01: Weather Data Collection
- WX02: Weather Information Processing and Distribution
This functional object is mapped to the following Functional View PSpecs:
- 6.2.1: Collect Misc Traveler Information
- 6.2.2: Collect Traffic Data
- 6.2.3: Collect Transit Operations Data
- 6.2.4: Collect Multimodal Data
- 6.2.5: Collect Situation and Sensor Data From Vehicles
- 6.2.6: Collect Emergency Traveler Data
- 6.5.4: Process Travel Services Provider Data
- 6.6.2.3: Provide Route Segment Data for Other Areas
- 7.4.2: Collect Price Data for Traveler Information Use
Requirements
| # | Requirement |
|---|---|
| 01 | The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. |
| 02 | The center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information. |
| 03 | The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. |
| 04 | The center shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information. |
| 05 | The center shall collect, process, and store parking information, including location, availability, and fees. |
| 06 | The center shall collect, process, and store toll fee information. |
| 07 | The center shall collect, process, and store current and forecast road conditions and surface weather conditions. |
| 08 | The center shall collect, process, and store event information. |
| 09 | The center shall collect, process, and store air quality information. |
| 10 | The center shall collect, process, and store freight specific traveler information. |
| 11 | The center shall collect, process, and store border crossing information. |
| 12 | The center shall collect information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation. |
| 13 | The center shall collect evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information. |
| 14 | The center shall collect evacuation information including evacuation zones, evacuation times, and reentry times. |
| 15 | The center shall collect alert information and status from emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. |
| 16 | The center shall collect road condition information for freeways, arterials, and secondary roads that are used as freight routes. |
| 17 | The center shall collect emissions information, including information from low emission zone operations. |
| 18 | The center shall collect information concerning members of the population that may require additional assistance in the event of an evacuation, including the names of household members, address, special needs, and any care giver information (nurse or hospice service that may want to keep track of their patient’s status). |
| 19 | The center shall collect, store and process multimodal transportation service information (for example, from ferry, rail and airline operators), including current ferry and rail schedule and airport status information and transfer points. |
| 20 | The center shall collect, store and process information related to service providers, such as hospitals, auto-repair, dining, fueling and emergency services. |
| 21 | The center shall provide environmental road data to other transportation centers and weather processing systems. |
| 22 | The center shall collect, store and exchange transportation-related regulations with other transportation centers. |
| 23 | The center shall acquire environmental data from vehicles. |
| 24 | The center shall collect, process, and store pathway information. |
Information Flows
Standards
Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.