| Functional Object | Description | User Defined |
|---|
| Center Data Collection | 'Center Data Collection' collects and stores information that is created in the course of center operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | False |
|---|
| ITS Security Support | 'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base. | False |
|---|
| MCM Automated Treatment System Control | 'MCM Automated Treatment System Control' remotely monitors and controls automated road treatment systems that disperse anti–icing chemicals or otherwise treat a road segment. The automated treatment system may be remotely activated by this object or it may include environmental sensors that activate the system automatically based on sensed environmental conditions. This object monitors treatment system operation, sets operating parameters, and directly controls system activation if necessary. | False |
|---|
| MCM Environmental Information Collection | 'MCM Environmental Information Collection' collects current road and weather conditions using data collected from environmental sensors deployed on and about the roadway. In addition to fixed sensor stations at the roadside, this functional object also collects environmental information from sensor systems located on Maintenance and Construction Vehicles. It also collects current and forecast environmental conditions information that is made available by other systems. The functional object aggregates the sensor system data and provides it, along with data attributes to other applications. | False |
|---|
| MCM Incident Management | 'MCM Incident Management' supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations. | False |
|---|
| MCM Vehicle Tracking | 'MCM Vehicle Tracking' tracks the location of maintenance and construction vehicles and other equipment. Vehicle/equipment location and associated information is presented to the operator. | False |
|---|
| MCM Winter Maintenance Management | 'MCM Winter Maintenance Management' manages winter road maintenance, tracking and controlling snow plow operations, roadway treatment (e.g., salt spraying and other material applications), and other snow and ice control operations. It monitors environmental conditions and weather forecasts and uses the information to schedule winter maintenance activities, determine the appropriate snow and ice control response, and track and manage response operations. | False |
|---|
| TMC Data Collection | 'TMC Data Collection' collects and stores information that is created in the course of traffic operations performed by the Traffic Management Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | False |
|---|
| TMC Evacuation Support | 'TMC Evacuation Support' supports development, coordination, and execution of special traffic management strategies during evacuation and subsequent reentry of a population in the vicinity of a disaster or major emergency. A traffic management strategy is developed based on anticipated demand, the capacity of the road network including access to and from the evacuation routes, and existing and forecast conditions. The strategy supports efficient evacuation and also protects and optimizes movement of response vehicles and other resources that are responding to the emergency. | False |
|---|
| TMC Traffic Information Dissemination | 'TMC Traffic Information Dissemination' disseminates traffic and road conditions, closure and detour information, incident information, driver advisories, and other traffic–related data to other centers, the media, and driver information systems. It monitors and controls driver information system field equipment including dynamic message signs and highway advisory radio, managing dissemination of driver information through these systems. | False |
|---|
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| NEMA TS 8 | Cyber and Physical Security for Intelligent Transportation Systems | This specification describes how agencies and other transportation infrastructure owner/operators should implement cyber– and physical–security for ITS. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|