Parent Service Package: MC09
< < MC08.1 : MC09.1 : MC09.2 > >

MC09.1: Sensor-Based Monitoring Implementation

This service package monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., embedded track, culverts) using both fixed and vehicle-based infrastructure monitoring sensors. This implementation monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., embedded track, culverts) using both fixed and maintenance vehicle-mounted infrastructure monitoring sensors. Fixed sensors monitor vibration, stress, temperature, continuity, and other parameters and mobile sensors and data logging devices collect information on current infrastructure condition.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Asset Management System MaintainerAsset Management System Maintains
Asset Management System ManagerAsset Management System Manages
Asset Management System ManagerAsset Management System Operator System Usage Agreement
Asset Management System OperatorAsset Management System Operates
Asset Management System OwnerAsset Management System Maintainer System Maintenance Agreement
Asset Management System OwnerAsset Management System Manager Operations Agreement
Asset Management System OwnerMaint and Constr Center Personnel Application Usage Agreement
Asset Management System OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Asset Management System OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Asset Management System OwnerMaint and Constr Management Center User Service Usage Agreement
Asset Management System SupplierAsset Management System Owner Warranty
ITS Roadway Equipment MaintainerITS Roadway Equipment Maintains
ITS Roadway Equipment ManagerITS Roadway Equipment Manages
ITS Roadway Equipment ManagerMaint and Constr Field Personnel System Usage Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment OwnerMaint and Constr Center Personnel Application Usage Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center Owner Information Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center User Service Usage Agreement
ITS Roadway Equipment OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Vehicle OBE Owner Expectation of Information Provision
ITS Roadway Equipment OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
ITS Roadway Equipment OwnerMaint and Constr Vehicle Operator Application Usage Agreement
ITS Roadway Equipment SupplierITS Roadway Equipment Owner Warranty
Maint and Constr Center PersonnelMaint and Constr Management Center Operates
Maint and Constr Field PersonnelITS Roadway Equipment Operates
Maint and Constr Management Center MaintainerMaint and Constr Management Center Maintains
Maint and Constr Management Center ManagerMaint and Constr Center Personnel System Usage Agreement
Maint and Constr Management Center ManagerMaint and Constr Management Center Manages
Maint and Constr Management Center OwnerAsset Management System Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerAsset Management System Operator Application Usage Agreement
Maint and Constr Management Center OwnerAsset Management System Owner Information Exchange Agreement
Maint and Constr Management Center OwnerAsset Management System User Service Usage Agreement
Maint and Constr Management Center OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerITS Roadway Equipment Owner Information Exchange Agreement
Maint and Constr Management Center OwnerITS Roadway Equipment User Service Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Field Personnel Application Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center OwnerMaint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE Owner Information Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Maint and Constr Management Center SupplierMaint and Constr Management Center Owner Warranty
Maint and Constr Vehicle OBE MaintainerMaint and Constr Vehicle OBE Maintains
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle OBE Manages
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle Operator System Usage Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Center Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Field Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Maintainer System Maintenance Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Manager Operations Agreement
Maint and Constr Vehicle OBE SupplierMaint and Constr Vehicle OBE Owner Warranty
Maint and Constr Vehicle OperatorMaint and Constr Vehicle OBE Operates

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Asset Management System Center 'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Maint and Constr Center Personnel Center The people that directly interface with a Maintenance and Construction Management Center. These personnel interact with fleet dispatch and management systems, road maintenance systems, incident management systems, work plan scheduling systems, and work zone management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Maint and Constr Management Center Center 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.
Maint and Constr Vehicle OBE Vehicle The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.
Maint and Constr Vehicle Operator Vehicle The operator of maintenance, construction, or other specialized service vehicles or equipment. Represents the maintenance and construction vehicle operators. The operator provides input specific to maintenance and construction vehicle operations, including the status of maintenance actions. Information provided to the operator includes dispatch requests and maintenance and construction actions to be performed.

Includes Functional Objects:

Functional Object Description Physical Object
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. Maint and Constr Management Center
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. Maint and Constr Management Center
MCV Infrastructure Monitoring 'MCV Infrastructure Monitoring' monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., culverts). It includes vehicle-based sensors that directly monitor the infrastructure, communications that allow roadway-based infrastructure monitoring sensors to be controlled and read, and data communications that allows collected infrastructure condition information to be reported back to a center. Maint and Constr Vehicle OBE
Roadway Infrastructure Monitoring 'Roadway Infrastructure Monitoring' monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., culverts). It includes sensors that monitor the infrastructure and the communications necessary to report this data to a center or vehicle-based maintenance system. ITS Roadway Equipment

Includes Information Flows:

Information Flow Description
asset status update Changes to status of pavement, bridges, signs and other assets resulting from maintenance or construction activities or infrastructure monitoring. The updates may include changes in installation information, materials information, vendor/contractor information, condition, and current maintenance status. In addition to infrastructure asset updates, the information provided may also include status of the maintenance and construction support assets, including vehicle and equipment utilization and repair records.
infrastructure conditions data Current condition of pavement, bridges, culverts, signs, and other roadway infrastructure as measured by on-board sensors or read from infrastructure-based sensors. The data may include raw data or images (e.g., photo logs) that indicate the current status of the infrastructure.
infrastructure monitoring sensor control Data used to configure and control infrastructure monitoring sensors.
infrastructure monitoring sensor data Data read from infrastructure-based sensors that monitor the condition or integrity of transportation infrastructure including bridges, tunnels, interchanges, pavement, culverts, signs, transit rail or guideway, and other roadway infrastructure. Includes sensor data and the operational status of the sensors.
maint and constr center personnel input User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination.
maint and constr operations information presentation Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning.
maint and constr vehicle operational data Data that describes the maintenance and construction activity performed by the vehicle. Operational data includes materials usage (amount stored and current application rate), operational state of the maintenance equipment (e.g., blade up/down, spreader pattern), vehicle safety status, and other measures associated with the operation of a maintenance, construction, or other special purpose vehicle. Operational data may include basic operational status of the vehicle equipment or a more precise record of the work performed (e.g., application of crack sealant with precise locations and application characteristics).
maint and constr vehicle operator input User input from field personnel including current maintenance and construction status information as well as on-board device control.
maint and constr vehicle operator presentation Information presented to maintenance and construction field personnel including vehicle routing and traffic information, road restrictions, environmental information, decision support information, maintenance schedules, dispatch instructions, maintenance personnel assignments, vehicle maintenance information, work zone status information, and corrective actions.
maint and constr vehicle system control Configure and control data that supports remote control of on-board maintenance and construction vehicle systems and field equipment that is remotely controlled by the vehicle. For example, the data can be used to adjust material application rates and spread patterns.
maintenance and repair needs Recommended strategies and schedules for maintenance of the transportation infrastructure.

Needs and Requirements

Need Functional Object Requirement
01 Maintenance and construction operations need to be able to monitor the condition of transportation-related infrastructure using both fixed and vehicle-based infrastructure monitoring sensors. MCM Environmental Information Collection 02 The center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
03 The center shall remotely control environmental sensors on-board maintenance and construction vehicles that measure road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and other measures.
04 The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from short range communications equipment that communicates with appropriately equipped probe vehicles.
07 The center shall respond to control data from center personnel regarding environmental sensor control and weather data collection.
08 The center shall collect operational status for the roadside and vehicle-based environmental sensor equipment.
10 The center shall collect environmental data from sensors that measure road surface temperature, moisture, icing, salinity, and other measures.
11 The center shall provide weather and road condition information to traffic management operations.
MCM Infrastructure Monitoring 01 The center shall remotely control and collect data from fixed infrastructure monitoring sensors that monitor vibration, stress, temperature, surface continuity, and other condition measures.
02 The center shall monitor maintenance vehicle-based mobile sensors and data logging devices that collect information on current infrastructure conditions.
03 The center shall remotely collect data from vehicle probes using short range communications equipment and process this data to identify potential pavement degradation, potholes, and other rough or adverse road surface conditions.
04 The center shall process the collected infrastructure information and use it to monitor the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure.
05 The center shall collect current maintenance and repair needs from the asset management system and correlate this data with data collected through infrastructure monitoring systems.
06 The center shall provide current infrastructure conditions information to the asset management system.
07 The center shall report infrastructure repair needs to the maintenance center personnel.
08 The center shall accept maintenance/construction vehicle operational data from maintenance/construction vehicles.
MCV Infrastructure Monitoring 01 The maintenance and construction vehicle shall collect infrastructure data from on-board sensors relating to the physical characteristics of the roadway infrastructure, including pavement, bridges, culverts, signs, etc.
02 The maintenance and construction vehicle shall collect infrastructure data from sensors located along the roadway relating to the physical characteristics of the roadway infrastructure, including pavement, bridges, culverts, signs, etc.
03 The maintenance and construction vehicle shall provide control signals to infrastructure monitoring sensors located at the roadway.
04 The maintenance and construction vehicle shall send current condition of pavement, bridges, culverts, signs, and other roadway infrastructure as measured by on-board sensors or read from infrastructure-based sensors to the center. The data may include raw data or images (e.g., photo logs) that indicate the current status of the infrastructure.
05 The maintenance and construction vehicle shall respond to control information from the center to allow remote operation of the on-board vehicle systems.
06 The maintenance and construction vehicle shall provide infrastructure sensor equipment operational status to the center.
07 The maintenance/construction vehicle shall provide maintenance vehicle operational data to the center.
Roadway Infrastructure Monitoring 02 The field element shall include infrastructure condition monitoring sensors that monitor the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., culverts), under maintenance vehicle control.
03 The field element shall provide operational status for the infrastructure condition monitoring sensors to the maintenance center.
04 The field element shall provide operational status for the infrastructure condition monitoring sensors to the maintenance vehicle.
05 The field element shall provide fault data for the infrastructure condition monitoring sensors to the maintenance center for repair.

Related Sources

Document Name Version Publication Date
None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Asset Management System Moderate Moderate Moderate Class 2
ITS Roadway Equipment High Moderate Moderate Class 4
Maint and Constr Management Center High High Moderate Class 4
Maint and Constr Vehicle OBE High High Moderate Class 4



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Asset Management System Maint and Constr Management Center maintenance and repair needs Low Moderate Moderate
Transportation system status information is observable information. If this data is incorrect or unavailable then maintenance transportation maintenance actions may not be properly taken address system problems, resulting in lower overall transportation system performance and in some cases an increased safety risk for users of the affected infrastructure. If this data is incorrect or unavailable then maintenance transportation maintenance actions may not be properly taken address system problems, resulting in lower overall transportation system performance and in some cases an increased safety risk for users of the affected infrastructure.
ITS Roadway Equipment Maint and Constr Management Center infrastructure monitoring sensor data High Moderate Moderate
Includes asset status and security-related monitoring both of which if available to a hostile third party would be useful in developing targets and inflicting damage. May be MODERATE if little such data is available or assets and potential impact is limited. Real-time monitoring of transportation asset data should be accurate and timely to protect the monitored assets. Given that the destintation of this flow cannot act directly, it is difficult to justify HIGH, unless 'infrastructure situation data' does not exist. As this flow includes data that reflects the condition of transportation assets, and can be used to infer the safety of use of those assets, loss of this flow means loss of asset safety monitoring, which has a potentially significant impact.
ITS Roadway Equipment Maint and Constr Vehicle OBE infrastructure monitoring sensor data High Moderate Moderate
Includes asset status and security-related monitoring both of which if available to a hostile third party would be useful in developing targets and inflicting damage. May be MODERATE if little such data is available or assets and potential impact is limited. Real-time monitoring of transportation asset data should be accurate and timely to protect the monitored assets. Given that the destintation of this flow cannot act directly, it is difficult to justify HIGH, unless 'infrastructure situation data' does not exist. As this flow includes data that reflects the condition of transportation assets, and can be used to infer the safety of use of those assets, loss of this flow means loss of asset safety monitoring, which has a potentially significant impact.
Maint and Constr Center Personnel Maint and Constr Management Center maint and constr center personnel input High High High
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Maint and Constr Management Center Asset Management System asset status update Moderate Moderate Low
Linked to the asset inventory, so the same concerns with this flow as that one, namely that when placed in one spot becomes a "one stop shop" for a nefarious person looking for infrastructure targets. Given the narrow focus of this flow it might be LOW, except that it infers information about specific targets. Infrastructure information should be correct or maintenance assets may be inappropriately assigned. While this changes more than other asset flows, the impact should still be minimal.
Maint and Constr Management Center ITS Roadway Equipment infrastructure monitoring sensor control Moderate High Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: NYC believes this to be low: "This information is directly observable." Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed “announcement”. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From NYC: The ITS-RE can work accordingly or in fail-safe if information is not available.
Maint and Constr Management Center Maint and Constr Center Personnel maint and constr operations information presentation Not Applicable Moderate Moderate
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Maint and Constr Management Center Maint and Constr Vehicle OBE maint and constr vehicle system control Moderate High Moderate
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. There should be multiple mechanisms for this information to arrive at the end recipient. If this is the only mechanism, should be raised to MODERATE.
Maint and Constr Vehicle OBE ITS Roadway Equipment infrastructure monitoring sensor control Moderate High Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: NYC believes this to be low: "This information is directly observable." Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed “announcement”. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From NYC: The ITS-RE can work accordingly or in fail-safe if information is not available.
Maint and Constr Vehicle OBE Maint and Constr Management Center infrastructure conditions data Moderate Moderate Moderate
Infrastructure sensor data may or may not be sensitive. Performance of sensors should be limited to maintenance personnel in case someone with hostile intent would monitor this data looking for particular conditions. This is a tenous leap in need for confidentiality; depending on the potential for conditions that can be sensed that might be abused for damage, this might be reduced to LOW. Sensor status, sensor data should have some degree of confidence, or decisions attached to this data may be erroneous. Assessment of MODERATE assumes sensors identifying conditions that move actions on the part of the M&CMC. For instance, icing, or radical changes in atmospheric condistions suggestion traffic management or road maintenance challenges.
Maint and Constr Vehicle OBE Maint and Constr Management Center maint and constr vehicle operational data Moderate Moderate Moderate
Contains information indicating the activity of the maintenance vehicle, which if public could be used against the vehicle or the infrastructure, depending on the hostile party's intent. Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money. Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money.
Maint and Constr Vehicle OBE Maint and Constr Vehicle Operator maint and constr vehicle operator presentation Moderate High High
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over the MCV. System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken. System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken.
Maint and Constr Vehicle Operator Maint and Constr Vehicle OBE maint and constr vehicle operator input Not Applicable Moderate High
Observation of control or status information is unlikely to have any value to a third party; actions of field personnel should be observable anyway. Any driver/operator interaction with vehicle systems needs some assurance of correctness; corruption of this information could lead to unexpected vehicle behavior which poses a limited safety risk. Without direct local control of vehicle systems the vehicle is essentially uncontrolled.

Standards

The diagram here shows the primary standards associated with the physical objects and information flows in this service package. Click on the standard # to go to the page explaining that standard in more detail. The tables that follow the diagram list the standards associated with the information flows in this service package that should drive development decisions. Click on the standard name for more information from the Communications View about a particular standard, including the solutions and information flow triples associated with the standard and any gaps or overlaps. This table is based primarily on standards used in North America. For information concerning standards and communications solutions in other regions consult the Communications View.

This material should be considered 'draft for review' and may change separately from ARC-IT version revisions. The date on the diagram relates to the date of the physical service package diagram on which this is based; standards-related information should be considered up-to-date as of the 'last updated' date on this page.

Communication Standards: Standards associated with data, message or dialog definitions, communications protocols and management and security of data exchanges. All standards here are also illustrated in information flow triple communications view diagrams.

NameTitle
ITS Application Entity
NTCIP 1204 Weather Station Objects NTCIP Environmental Sensor Station Interface Standard
Facilities Layer
Bundle: ISO 15784-2 Intelligent transport systems (ITS) -- Data exchange involving roadside modules communication -- Part 2: Centre to field device communications using SNMP
Security Entity
Bundle: IEEE 1609.2 IEEE 1609.2 Security Bundle
IETF RFC 6353 TLS for SNMP Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)
IETF RFC 9456 TLS Updates for SNMP Updates to the TLS Transport Model for SNMP
Secure Session Alternatives Secure Session Alternatives
Management Entity
Bundle: SNMPv3 MIB SNMPv3 & Networking MIBs
NTCIP 1201 Global Objects NTCIP Global Object (GO) Definitions
Networking and Transport Layer
IEEE 1609.3 WAVE - Networking Services IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Networking Services
Internet Transport Alternatives Internet Transport Alternatives
IP Alternatives Internet Protocol Alternative Set
Access Layer
Bundle: Local Unicast Wireless SubNet (US) Bundle: Local Unicast Wireless SubNet
Internet Subnet Alternatives Internet Subnet Alternatives
Wireless Internet Alternatives (NA) Wireless Internet Alternatives according to North American standards

Physical Standards: Standards associated with device physical, environmental or performance requirements.

The following table lists the standards associated with physical objects in this service package. Click on the standard name for more information about a particular standard.

NameTitle
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems
SAE J3361 Antenna requirements V2X Antenna Coverage and Test Requirements for US FHWA Class 1 and Class 3-13 Class Vehicles
SAE J5001 OBU Standard Onboard Unit Standard for Connected Vehicles

Service-Level Standards: Standards associated service package structure, messaging patterns, user needs, requirements or similar systems-engineering content that describe one or more use cases satisfied by the service package.

No service-level standards have been identified for this service package.





System Requirements

No System Requirements