Maint and Constr Management Center --> Transportation Information Center:
work zone information
Definitions
work zone information (Information Flow): Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
Maint and Constr Management Center (Source Physical Object): The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.
The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)
Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Included In
This Triple is in the following Service Packages:
- CVO09: Freight-Specific Dynamic Travel Planning
- MC06: Work Zone Management
- TI01: Broadcast Traveler Information
- TI02: Personalized Traveler Information
- TI03: En-Route Guidance
- TI04: Trip Planning and Payment
- TI08: Personal Wayfinding
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (6)
- US: WZDx - Secure Internet (ITS) (16)
- US: TMDD - NTCIP Messaging (19)
- (None-Data) - Secure Internet (ITS) (43)
- Data for Distribution (TBD) - Apache Kafka (44)
- Data for Distribution (TBD) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
|
Click gap icons for more info.
|
||
Mgmt
|
Facilities
No Standard Needed |
Security
IETF RFC 8446 |
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Moderate | |
Basis | Eventually intended for public distribution, so no need to obfuscate. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.; DISC: WYO believes this to be HIGH. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |