Office that handles most of the routine roadway maintenance and responds to incidents when services are requested by local emergency management.
| Functional Object | Description | User Defined |
|---|
| ITS Management Support | 'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol–specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring. | 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 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 Environmental Information Processing | 'MCM Environmental Information Processing' processes current and forecast weather data, road condition information, local environmental data, and uses internal models to develop specialized detailed forecasts of local weather and surface conditions. The processed environmental information products are presented to center personnel and disseminated to other centers. | 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 Infrastructure Monitoring | 'MCM Infrastructure Monitoring' monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation–related infrastructure (e.g., culverts). It monitors the infrastructure, collecting data from both fixed and vehicle–based sensors. In addition to specialized infrastructure monitoring sensors, it also monitors the broader population of equipped vehicles for vertical acceleration data and other situation data that may be used to determine current pavement condition. | False |
|---|
| MCM Roadway Maintenance | 'MCM Roadway Maintenance' provides overall management and support for routine maintenance on a roadway system or right–of–way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of non–ITS equipment on the roadway (e.g., signs, gantries, cabinets, guard rails, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. See also MCM Field Equipment Maintenance for maintenance of ITS field equipment. | False |
|---|
| MCM Work Zone Management | 'MCM Work Zone Management' remotely monitors and supports work zone activities, controlling traffic through dynamic message signs (DMS), Highway Advisory Radio (HAR), gates and barriers, and informing other groups of activity (e.g., traveler information, traffic management, other maintenance and construction centers) for better coordination management. Work zone speeds, and delays, and closures are provided to the motorist prior to the work zones. This application provides control of field equipment in all maintenance areas, including fixed and portable field equipment supporting both stationary and mobile work zones. | 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. |
|---|