< < WX03 : WX04 :

WX04: Roadway Micro-Prediction

This service package supports advanced systems which use environmental information collected from ITS roadway equipment or from the Surface Transportation Weather Service, along with advanced algorithms, to create micro-predictions of roadway conditions which can support improved safety warnings and maintenance planning and dispatch.

Origin: Canada

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

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
ITS Roadway Equipment Developer	ITS Roadway Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
ITS Roadway Equipment Developer	Maint and Constr Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
ITS Roadway Equipment Developer	Surface Transportation Weather Service Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
ITS Roadway Equipment Developer	Traffic Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Maint and Constr Management Center Developer	ITS Roadway Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Maint and Constr Management Center Developer	Maint and Constr Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Maint and Constr Management Center Developer	Surface Transportation Weather Service Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Maint and Constr Management Center Developer	Traffic Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Surface Transportation Weather Service Developer	ITS Roadway Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Surface Transportation Weather Service Developer	Maint and Constr Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Surface Transportation Weather Service Developer	Surface Transportation Weather Service	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Surface Transportation Weather Service Developer	Traffic Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	ITS Roadway Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	Maint and Constr Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	Surface Transportation Weather Service Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	Traffic Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
ITS Roadway Equipment Installer	ITS Roadway Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
ITS Roadway Equipment Owner	ITS Roadway Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
ITS Roadway Equipment Owner	ITS Roadway Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Maint and Constr Management Center Installer	Maint and Constr Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Maint and Constr Management Center Owner	Maint and Constr Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Maint and Constr Management Center Owner	Maint and Constr Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Surface Transportation Weather Service Installer	Surface Transportation Weather Service	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Surface Transportation Weather Service Owner	Surface Transportation Weather Service Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Surface Transportation Weather Service Owner	Surface Transportation Weather Service Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Traffic Management Center Installer	Traffic Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Traffic Management Center Owner	Traffic Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traffic Management Center Owner	Traffic Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Driver	Roadway Owner	Expectation of Roadway Condition Management (hide) An expectation whereby one party expects the other to maintain the condition of the roadway environment to a level sufficient for the trusting partner to operate safely.
ITS Roadway Equipment Maintainer	ITS Roadway Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
ITS Roadway Equipment Manager	ITS Roadway Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
ITS Roadway Equipment Owner	ITS Roadway Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
ITS Roadway Equipment Owner	ITS Roadway Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
ITS Roadway Equipment Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
ITS Roadway Equipment Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
ITS Roadway Equipment Owner	Maint and Constr Management Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
ITS Roadway Equipment Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
ITS Roadway Equipment Owner	Surface Transportation Weather Service Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
ITS Roadway Equipment Owner	Surface Transportation Weather Service Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
ITS Roadway Equipment Owner	Surface Transportation Weather Service User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
ITS Roadway Equipment Owner	Traffic Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
ITS Roadway Equipment Owner	Traffic Management Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
ITS Roadway Equipment Owner	Traffic Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
ITS Roadway Equipment Owner	Traffic Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
ITS Roadway Equipment Supplier	ITS Roadway Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Maint and Constr Center Personnel	Maint and Constr Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Management Center Maintainer	Maint and Constr Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Maint and Constr Management Center Manager	Maint and Constr Center Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Maint and Constr Management Center Manager	Maint and Constr Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Maint and Constr Management Center Owner	ITS Roadway Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	ITS Roadway Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Maint and Constr Management Center Owner	ITS Roadway Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Maint and Constr Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Maint and Constr Management Center Owner	Maint and Constr Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Maint and Constr Management Center Owner	Surface Transportation Weather Service Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Surface Transportation Weather Service Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Maint and Constr Management Center Owner	Surface Transportation Weather Service User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Traffic Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Traffic Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Maint and Constr Management Center Owner	Traffic Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Traffic Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Maint and Constr Management Center Supplier	Maint and Constr Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Roadway Maintainer	Roadway Environment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Roadway Manager	Roadway Environment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Roadway Owner	Roadway Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Roadway Owner	Roadway Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Surface Transportation Weather Service Maintainer	Surface Transportation Weather Service	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Surface Transportation Weather Service Manager	Surface Transportation Weather Service	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Surface Transportation Weather Service Owner	ITS Roadway Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Surface Transportation Weather Service Owner	ITS Roadway Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Surface Transportation Weather Service Owner	ITS Roadway Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Surface Transportation Weather Service Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Surface Transportation Weather Service Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Surface Transportation Weather Service Owner	Maint and Constr Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Surface Transportation Weather Service Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Surface Transportation Weather Service Owner	Surface Transportation Weather Service Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Surface Transportation Weather Service Owner	Surface Transportation Weather Service Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Surface Transportation Weather Service Owner	Traffic Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Surface Transportation Weather Service Owner	Traffic Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Surface Transportation Weather Service Owner	Traffic Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Surface Transportation Weather Service Owner	Traffic Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Surface Transportation Weather Service Supplier	Surface Transportation Weather Service Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traffic Management Center Maintainer	Traffic Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Traffic Management Center Manager	Traffic Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Traffic Management Center Manager	Traffic Operations Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Traffic Management Center Owner	ITS Roadway Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Traffic Management Center Owner	ITS Roadway Equipment Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Traffic Management Center Owner	ITS Roadway Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Traffic Management Center Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Traffic Management Center Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Traffic Management Center Owner	Maint and Constr Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Traffic Management Center Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Traffic Management Center Owner	Surface Transportation Weather Service Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Traffic Management Center Owner	Surface Transportation Weather Service Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Traffic Management Center Owner	Surface Transportation Weather Service User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Traffic Management Center Owner	Traffic Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Traffic Management Center Owner	Traffic Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Traffic Management Center Supplier	Traffic Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traffic Operations Personnel	Traffic Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
ITS Roadway Equipment	Roadway Environmental Monitoring	1.1.1.3	Process Environmental Sensor Data
		1.2.7.1	Process Indicator Output Data for Roads
		1.2.7.16	Process Signal Control Conflict Monitoring
		1.2.7.2	Monitor Roadside Equipment Operation
		1.2.7.8	Provide Device Interface to Other Roadway Devices
		1.2.7.9	Process Roadway Information Data
		9.2.3.6	Collect Field Equipment Status for Repair
		9.3.3.1	Collect Vehicle Speed
Maint and Constr Management Center	MCM Environmental Information Collection	9.2.3.7	Process Environmental Probe Data for Maintenance
		9.2.5	Provide M&C Center Personnel Interface for Maint
		9.4.2	Collect Environmental Data
		9.4.5	Provide M&C Center Personnel Interface for Environment
	MCM Road Weather Micro-Prediction	9.4.2	Collect Environmental Data
Traffic Management Center	TMC Environmental Monitoring	1.1.2.5	Process Vehicle Situation Data
		1.1.2.8	Process Roadway Environmental Data
		1.1.4.1	Retrieve Traffic Data
		1.1.4.2	Provide Traffic Operations Personnel Traffic Data Interface
		1.1.4.4	Manage Traffic Archive Data
		1.1.5	Exchange Data with Other Traffic Centers
		1.2.4.3	Output In-vehicle Signage Data
		1.2.4.7	Manage Roadway Warning System
		1.2.8	Collect Traffic Field Equipment Fault Data
	TMC Road Weather Micro-Prediction	1.1.2.8	Process Roadway Environmental Data

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
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.
Roadway Environment	Field	'Roadway Environment' represents the physical condition and geometry of the road surface, markings, signs, and other objects on or near the road surface. It also represents the environmental conditions immediately surrounding the roadway. The roadway environment must be sensed and interpreted to support automated vehicle services. Surrounding conditions may include fog, ice, snow, rain, wind, etc. which will influence the way in which a vehicle can be safely operated on the roadway. The roadway environment must be monitored to enable corrective action and information dissemination regarding roadway conditions which may adversely affect travel. Infrastructure owner/operators can improve the roadway environment to improve the performance and accuracy of vehicle-based sensors that must sense and interpret this environment. Improvements could include changes in the shape, size, design, and materials used in signs, pavement markings, and other road features.
Surface Transportation Weather Service	Center	The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions.
Traffic Management Center	Center	The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Traffic Operations Personnel	Center	'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand 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.

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 Road Weather Micro-Prediction	'MCM Road Weather Micro-Prediction' uses road weather data and advanced algorithms to create micro-predictions of roadway conditions, or receives micro-predictions from external sources, which can support improved maintenance planning and dispatch.	Maint and Constr Management Center
Roadway Environmental Monitoring	'Roadway Environmental Monitoring' measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed or to other field devices to support communications to vehicles. A broad array of weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other metrics.	ITS Roadway Equipment
TMC Environmental Monitoring	'TMC Environmental Monitoring' assimilates current and forecast road conditions and surface weather information using a combination of weather service provider information, information collected by other centers such as the Maintenance and Construction Management Center, data collected from environmental sensors deployed on and about the roadway, and information collected from connected vehicles. The collected environmental information is monitored and presented to the operator. This information can be used to issue general traveler advisories and support location specific warnings to drivers.	Traffic Management Center
TMC Road Weather Micro-Prediction	'TMC Road Weather Micro-Prediction' uses road weather data and advanced algorithms to create micro-predictions of roadway conditions, or receives micro-predictions from external sources, which can support improved traffic management.	Traffic Management Center

Includes Information Flows:

Information Flow	Description
environmental conditions	Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that are measured by environmental sensors.
environmental conditions data	Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included.
environmental conditions data status	Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided.
environmental sensor control	Data used to configure and control environmental sensors.
environmental sensor data	Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors. Operational status of the sensors is also included.
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.
qualified environmental conditions data	Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included.
roadway micro forecast	Forecast of weather and roadway conditions at a fine level of resolution (e.g. for individual links in the road network).
traffic operator data	Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input	User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users;	Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight;	Enhance integration and connectivity

Associated Objective Categories

Objective Category
Travel Weather Management: Detours for Impacted Roadways
Travel Weather Management: Disseminating Information
Travel Weather Management: Road Weather Information System Coverage

Associated Objectives and Performance Measures

Objective	Performance Measure
Increase by X percent of significant travel routes covered by weather-related diversion plans by year Y.	Percent of significant travel routes covered by weather-related diversion plans.
Increase the percent of agencies that have adopted multi-agency weather-related transportation operations plans and that are involved in transportation operations during weather events to X percent by year Y.	Percent of agencies involved in transportation operations during weather events that have adopted multi-agency, weather-related transportation operations plans.
Increase the percent of major road network (or transit network or regional bicycle network) covered by weather sensors or a road weather information system (RWIS) by X percent in Y years as defined by an RWIS station within Z miles.	Percent of major road (transit or bicycle) network within Z miles of an RWIS station.
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years.	Time from beginning of weather event to posting of traveler information on (variable message signs, 511, Road Weather Information Systems, public information broadcasts etc.).
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years.	Time from beginning of weather event to posting of traveler information on agency website.

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need		Functional Object	Requirement
01	Traffic operations or maintenance and construction operations need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.	MCM Environmental Information Collection	10	The center shall collect environmental data from sensors that measure road surface temperature, moisture, icing, salinity, and other measures.
		Roadway Environmental Monitoring	04	The field element's environmental sensors shall be remotely controlled by a traffic management center.
		TMC Environmental Monitoring	06	The traffic center shall share the collected environmental data with Maintenance and construction operations.
02	Weather Systems need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.	Roadway Environmental Monitoring	02	The field element shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
02		TMC Environmental Monitoring	01	The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures.
03	Maintenance and construction operations need to process collected environmental information to develop detailed micro-predictions to support maintenance planning and operations.	MCM Environmental Information Collection	11	The center shall provide weather and road condition information to traffic management operations.
		MCM Road Weather Micro-Prediction	01	The center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), and environmental data collected from sensors deployed on and about the roadway.
			02	The center shall receive road condition information from weather service providers.
			03	The center shall provide value-added sector specific meteorological services with information on basic road facility and treatment information that supports forecasts for road conditions.
			04	The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current and micro-predicted road weather and road conditions.
04	Traffic operations need to process collected environmental information to develop detailed micro-predictions to support accurate local advisory systems.	TMC Road Weather Micro-Prediction	01	The center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), and environmental data collected from sensors deployed on and about the roadway.
			02	The center shall receive road condition information from weather service providers.
			03	The center shall provide value-added sector specific meteorological services with information on basic road facility and treatment information that supports forecasts for road conditions.
			04	The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current and micro-predicted road weather and road conditions.

Related Sources

Document Name	Version	Publication Date
ITS User Services Document		1/1/2005
ITS Architecture for Canada - Version 3

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
ITS Roadway Equipment	Moderate	High	Moderate	Class 3
Maint and Constr Management Center	Moderate	Moderate	Moderate	Class 2
Roadway Environment	Not Applicable	Low	Low	Class 1
Surface Transportation Weather Service	Moderate	Moderate	Moderate	Class 2
Traffic Management Center	Moderate	Moderate	Moderate	Class 2

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
Source	Destination	Information Flow	Basis	Basis	Basis
ITS Roadway Equipment	Maint and Constr Management Center	environmental sensor data	Low	High	Moderate
ITS Roadway Equipment	Maint and Constr Management Center	environmental sensor data	Little to no impact if this data is observed	WYO believes this to be MODERATE or HIGH depending on the application	Updates are valuable only if they are timely.
ITS Roadway Equipment	Surface Transportation Weather Service	environmental sensor data	Low	Moderate	Moderate
ITS Roadway Equipment	Surface Transportation Weather Service	environmental sensor data	Little to no impact if this data is observed	This data should be correct, as it may be used to establish safe speeds and determine road treatments.	Updates are valuable only if they are timely.
ITS Roadway Equipment	Traffic Management Center	environmental sensor data	Low	Moderate	Moderate
ITS Roadway Equipment	Traffic Management Center	environmental sensor data	Little to no impact if this data is observed	info should be correct to determine safe speeds etc.; DISC: WYO believes this to be HIGH	Updates are desireable but slightly outdated information will not be catastrophic.
Maint and Constr Center Personnel	Maint and Constr Management Center	maint and constr center personnel input	High	High	High
Maint and Constr Center Personnel	Maint and Constr Management Center	maint and constr center personnel input	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	ITS Roadway Equipment	environmental sensor control	Moderate	Moderate	Moderate
Maint and Constr Management Center	ITS Roadway Equipment	environmental sensor control	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: WYO believes this to be MODERATE.	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.	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.
Maint and Constr Management Center	Maint and Constr Center Personnel	maint and constr operations information presentation	Not Applicable	Moderate	Moderate
Maint and Constr Management Center	Maint and Constr Center Personnel	maint and constr operations information presentation	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	Surface Transportation Weather Service	environmental conditions data	Low	Moderate	Low
Maint and Constr Management Center	Surface Transportation Weather Service	environmental conditions data	Little to no impact if this data is observed	This data should be correct, as it may be used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Maint and Constr Management Center	Traffic Management Center	environmental conditions data	Low	Moderate	Low
Maint and Constr Management Center	Traffic Management Center	environmental conditions data	Little to no impact if this data is observed	This data should be correct, as it may be used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Roadway Environment	ITS Roadway Equipment	environmental conditions	Not Applicable	Low	Low
Roadway Environment	ITS Roadway Equipment	environmental conditions	Sensor-based information flows by definition have no confidentiality concerns.	While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions.	While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions.
Surface Transportation Weather Service	ITS Roadway Equipment	environmental sensor control	Moderate	Moderate	Moderate
Surface Transportation Weather Service	ITS Roadway Equipment	environmental sensor control	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: WYO believes this to be MODERATE.	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.	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.
Surface Transportation Weather Service	Maint and Constr Management Center	environmental conditions data status	Low	Moderate	Low
Surface Transportation Weather Service	Maint and Constr Management Center	environmental conditions data status	Little to no impact if this data is observed	This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Surface Transportation Weather Service	Maint and Constr Management Center	qualified environmental conditions data	Low	Moderate	Moderate
Surface Transportation Weather Service	Maint and Constr Management Center	qualified environmental conditions data	If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW.	Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data.	This flow is used to help determine what road treatments should be performed. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimatation; if that estimate fails to suggest the correct treatment method, the cost to mobility and maintenance could be signficant.
Surface Transportation Weather Service	Maint and Constr Management Center	roadway micro forecast	Low	Moderate	Low
Surface Transportation Weather Service	Maint and Constr Management Center	roadway micro forecast	Should eventually be public, and regardless it is unlikely that sharing this data will cause any harm.	Could be used to make traffic management and personnel decisions, so some guarantee the data at the destination is what the sender intended is warranted. Still, this flow is a candidate for LOW if the range for integrity is opened up to include it.	Unlikely that the lack of this flow will radically change outcomes.
Surface Transportation Weather Service	Traffic Management Center	environmental conditions data status	Low	Moderate	Low
Surface Transportation Weather Service	Traffic Management Center	environmental conditions data status	Little to no impact if this data is observed	This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Surface Transportation Weather Service	Traffic Management Center	qualified environmental conditions data	Low	Moderate	Moderate
Surface Transportation Weather Service	Traffic Management Center	qualified environmental conditions data	If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW.	Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data.	This flow is used to help determine what road operations actions should be taken. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimation; if that estimate fails to suggest the correct actions, the cost to mobility could be signficant.
Surface Transportation Weather Service	Traffic Management Center	roadway micro forecast	Low	Moderate	Low
Surface Transportation Weather Service	Traffic Management Center	roadway micro forecast	Should eventually be public, and regardless it is unlikely that sharing this data will cause any harm.	Could be used to make traffic management and personnel decisions, so some guarantee the data at the destination is what the sender intended is warranted. Still, this flow is a candidate for LOW if the range for integrity is opened up to include it.	Unlikely that the lack of this flow will radically change outcomes.
Traffic Management Center	ITS Roadway Equipment	environmental sensor control	Moderate	Moderate	Low
Traffic Management Center	ITS Roadway Equipment	environmental sensor control	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: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen	Should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with environmental sensor data received and be detrimental to operations; DISC: WYO believes this may be HIGH for some applications	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 THEAwant updates but delayed information will not be severe; should be able to operate from a previous/default control/config; DISC: WYO believes this to be MODERATE
Traffic Management Center	Maint and Constr Management Center	environmental conditions data	Low	Moderate	Low
Traffic Management Center	Maint and Constr Management Center	environmental conditions data	Little to no impact if this data is observed	This data should be correct, as it may be used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Traffic Management Center	Surface Transportation Weather Service	environmental conditions data	Low	Moderate	Low
Traffic Management Center	Surface Transportation Weather Service	environmental conditions data	Little to no impact if this data is observed	This data should be correct, as it may be used to establish safe speeds and determine road treatments.	There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE.
Traffic Management Center	Traffic Operations Personnel	traffic operator data	Moderate	Moderate	Moderate
Traffic Management Center	Traffic Operations Personnel	traffic operator data	Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available.	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.
Traffic Operations Personnel	Traffic Management Center	traffic operator input	Moderate	High	High
Traffic Operations Personnel	Traffic Management Center	traffic operator input	Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available.	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.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name	Title	Physical Object
ITE 5301 ATC ITS Cabinet	Intelligent Transportation System Standard Specification for Roadside Cabinets	ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	ITS Roadway Equipment
		Maint and Constr Management Center
		Traffic Management Center

System Requirements

System Requirement		Need
001	The system shall collect environmental data from sensors that measure road surface temperature, moisture, icing, salinity, and other measures.	01	Traffic operations or maintenance and construction operations need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.
002	The system shall provide weather and road condition information to traffic management operations.	03	Maintenance and construction operations need to process collected environmental information to develop detailed micro-predictions to support maintenance planning and operations.
003	The system shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), and environmental data collected from sensors deployed on and about the roadway.	04	Traffic operations need to process collected environmental information to develop detailed micro-predictions to support accurate local advisory systems.
003		03	Maintenance and construction operations need to process collected environmental information to develop detailed micro-predictions to support maintenance planning and operations.
004	The system shall use the various data inputs of environmental sensors and road weather data to develop a view of current and micro-predicted road weather and road conditions.	04	Traffic operations need to process collected environmental information to develop detailed micro-predictions to support accurate local advisory systems.
004		03	Maintenance and construction operations need to process collected environmental information to develop detailed micro-predictions to support maintenance planning and operations.
005	The system shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures.	02	Weather Systems need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.
006	The system shall share the collected environmental data with Maintenance and construction operations.	01	Traffic operations or maintenance and construction operations need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.
007	The system shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.	02	Weather Systems need be able to collect detailed road conditions and weather data from environmental sensors on or in the vicinity of the roadway.