Type: Environmental
Groups:- Road Weather
Road Weather Information for Maintenance and Fleet Management Systems
The Road Weather Information for Maintenance and Fleet Management Systems Application can be viewed as either a stand-alone application and as an adjunct to the Enhanced-MDSS. Vehicle data is collected both from vehicles used during winter maintenance and from other maintenance vehicles and equipment used year round. The data collected is road weather data as well as specialized maintenance information such as status of vehicle systems, material distribution rate, and materials remaining. The data collected can be used by maintenance or fleet dispatchers to monitor the status of the maintenance operations, or the data can be used as an input to the Enhanced-MDSS application.
Enterprise
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification
Business Interaction Matrix:
Road Weather Information for Maintenance and Fleet Management Systems Operations Stage | |||||||||
---|---|---|---|---|---|---|---|---|---|
Maint and Constr Vehicle Owner | Maint and Constr Vehicle Operator | Maint and Constr Center Personnel | Maint and Constr Manager | MCV Winter Maintenance Provider | MCV Roadway Maintenance and Construction Provider | Maintenance and Construction Administrator | Storage Facility Operator | MCV Infrastructure Monitoring Provider | |
Maint and Constr Vehicle Owner | Vehicle Operating Agreement | Information Exchange and Action Agreement | Application Usage Agreement | Application Usage Agreement | Application Usage Agreement | ||||
Maint and Constr Vehicle Operator | Vehicle Operating Agreement | ||||||||
Maint and Constr Center Personnel | Employment Agreement | ||||||||
Maint and Constr Manager | Information Exchange and Action Agreement | Employment Agreement | Information Exchange and Action Agreement | Information Provision Agreement | |||||
MCV Winter Maintenance Provider | Application Usage Agreement | ||||||||
MCV Roadway Maintenance and Construction Provider | Application Usage Agreement | ||||||||
Maintenance and Construction Administrator | Information Exchange and Action Agreement | ||||||||
Storage Facility Operator | Information Provision Agreement | ||||||||
MCV Infrastructure Monitoring Provider | Application Usage Agreement |
Includes Enterprise Objects:
Enterprise Object | Description |
---|---|
Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
Maint and Constr Center Personnel | 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 Manager | The organization responsible for maintenance and construction activities. |
Maint and Constr Vehicle Manufacturer | The manufacturer of maintenance vehicles and/or construction vehicles. |
Maint and Constr Vehicle OBE Manufacturer | The entity that builds the Maint and Constr Vehicle OBE. |
Maint and Constr Vehicle Operator | The individual that operates the MCM vehicle. |
Maint and Constr Vehicle Owner | The individual, group of individuals or corporate entity that owns the maintenance and/or construction vehicle. |
Maintenance and Construction Administrator | This represents the individual or organization that performs non-ITS administrative functions but might need information from, or provide information to, ITS systems. This includes procurement, human resources, certification, contract administration, inspection and similar functions. |
MCM Infrastructure Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Infrastructure Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Infrastructure Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCM Maintenance Decision Support Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Maintenance Decision Support Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Maintenance Decision Support Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCM Roadway Maintenance Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Roadway Maintenance Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Roadway Maintenance Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCM Winter Maintenance Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Winter Maintenance Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Winter Maintenance Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCM Work Zone Safety Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCV Infrastructure Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Infrastructure Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Infrastructure Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCV Roadway Maintenance and Construction Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Roadway Maintenance and Construction Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Roadway Maintenance and Construction Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
MCV Winter Maintenance Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Winter Maintenance Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCV Winter Maintenance Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
State Regulatory | State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies. |
Storage Facility Operator | The organization responsible for operating and maintaining facilities that store and distribute equipment and materials used in maintenance and construction. |
Includes Resources:
Resource | Description |
---|---|
Application Component Certification Requirements | The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE. |
Backoffice Service Development System | The systems used to develop backoffice (center) hardware and software components of applications. |
Backoffice Service Installation System | The systems used to install and configure backoffice (center) hardware and software components. |
Backoffice Service Maintenance System | The systems used to maintain and upgrade backoffice (center) hardware and software components. |
Device Certification Requirements | The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment. |
Maint and Constr Management 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 | This physical object resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the sensory, processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment and supervisory vehicles. The subsystem 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. For example, for a snow plow, the information would include whether the plow is up or down and material usage information. The subsystem may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself and other sensors that monitor environmental conditions including the road condition and surface weather information. This subsystem can represent a diverse set of mobile environmental sensing platforms, including wheeled vehicles and any other vehicle that collects and reports environmental information. |
Maint and Constr Vehicle OBE | 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 and supervisory vehicles. 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 and include sensors that monitor environmental conditions such as road condition and surface weather information. This can include a diverse set of mobile environmental sensing platforms, including wheeled vehicles and any other vehicle that collects and reports environmental information. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general applications with applications that are specific to maintenance and construction vehicles. |
Maintenance and Construction Administrative Systems | 'Maintenance and Construction Administrative Systems' represents the various administrative systems that support the operation of ITS systems for maintenance and construction operations. The interfaces to this object support general administrative data interchanges between ITS and non-ITS systems. This includes: interfaces to purchasing for equipment and consumables resupply, interfaces to human resources that manage training and special certification for field crews and other personnel, and interfaces to contract administration functions that administer and monitor the work performance for maintenance and construction contracts. |
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 application 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 application object aggregates the sensor system data and provides it, along with data attributes to other applications. |
MCM Environmental Information Processing | "MCM Environmental Information Processing" processes current and forecast weather data, road condition information, local environmental data, and uses internal models to develop specialized detailed forecasts of local weather and surface conditions. The processed environmental information products are presented to center personnel and disseminated to other centers. |
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. |
MCM Maintenance Decision Support | "MCM Maintenance Decision Support" recommends maintenance courses of action based on current and forecast environmental and road conditions and additional application specific information. Decisions are supported through understandable presentation of filtered and fused environmental and road condition information for specific time horizons as well as specific maintenance recommendations that are generated by the system based on this integrated information. The recommended courses of action are supported by information on the anticipated consequences of action or inaction, when available. |
MCM Roadway Maintenance | "MCM Roadway Maintenance" provides overall management and support for routine maintenance on a roadway system or right-of-way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. |
MCM Winter Maintenance Management | "MCM Winter Maintenance Management" manages winter road maintenance, tracking and controlling snow plow operations, roadway treatment (e.g., salt spraying and other material applications), and other snow and ice control operations. It monitors environmental conditions and weather forecasts and uses the information to schedule winter maintenance activities, determine the appropriate snow and ice control response, and track and manage response operations. |
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. |
MCV Roadway Maintenance and Construction | "MCV Roadway Maintenance and Construction" includes the on-board systems that support routine non-winter maintenance on a roadway system or right-of-way. Routine maintenance includes landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). |
MCV Winter Maintenance | "MCV Winter Maintenance" supports snow plow operations and other roadway treatments (e.g., salt spraying and other material applications). It supports communications with the center to receive information and instructions that are provided to the vehicle operator and also supports remote control of on-board systems. It tracks operational status of snow and ice control operations and provides this information back to the center. |
Mobile Component Development System | The system used in a backoffice environment to develop and test the mobile component of the application. |
Mobile Component Installation System | The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application. |
Mobile Component Maintenance System | The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
Storage Facility Data Acquisition System | 'Storage Facility Data Acquisition System' represents systems that monitor and report the current status of facilities that provide storage and forward staging for equipment and materials used in maintenance and construction operations. It provides status information on the types and quantities of materials and equipment that are available at the facility. |
Vehicle OBE | The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. |
Includes Roles:
Role | Description |
---|---|
Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
Member | An Enterprise is part of another larger, target Enterprise. |
Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
Coordination | Type | Description |
---|---|---|
Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
Application Interface Specification | Agreement | 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. |
Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
Application Usage Agreement | Agreement | 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. |
Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
Backoffice Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Employment Agreement | Agreement | An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance. |
Includes | Includes | Indicates that one component is entirely contained within another component. |
Information Exchange and Action Agreement | Agreement | 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. |
Information Provision Agreement | Agreement | An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
Interface Description | Agreement | Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator. |
Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Mobile Component Installation Agreement | Agreement | An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application. |
Mobile Component License Agreement | Agreement | An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question. |
Mobile Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Vehicle Data Access Agreement | Agreement | An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data. |
Vehicle Operating Agreement | Agreement | An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
Vehicle Procurement Agreement | Agreement | The exchange of a vehicle for compensation. One entity purchases the vehicle from the other. |
Warranty | Agreement | A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component. |
Functional
Includes Processes:
Includes Data Flows:
Physical
SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
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 and supervisory vehicles. 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 and include sensors that monitor environmental conditions such as road condition and surface weather information. This can include a diverse set of mobile environmental sensing platforms, including wheeled vehicles and any other vehicle that collects and reports environmental information. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general applications with applications that are specific to maintenance and construction vehicles. |
Maintenance and Construction Administrative Systems | Center | 'Maintenance and Construction Administrative Systems' represents the various administrative systems that support the operation of ITS systems for maintenance and construction operations. The interfaces to this object support general administrative data interchanges between ITS and non-ITS systems. This includes: interfaces to purchasing for equipment and consumables resupply, interfaces to human resources that manage training and special certification for field crews and other personnel, and interfaces to contract administration functions that administer and monitor the work performance for maintenance and construction contracts. |
Storage Facility Data Acquisition System | Center | 'Storage Facility Data Acquisition System' represents systems that monitor and report the current status of facilities that provide storage and forward staging for equipment and materials used in maintenance and construction operations. It provides status information on the types and quantities of materials and equipment that are available at the facility. |
Includes Application Objects:
Application Object | Description | Physical Object |
---|---|---|
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 |
MCM Maintenance Decision Support | "MCM Maintenance Decision Support" recommends maintenance courses of action based on current and forecast environmental and road conditions and additional application specific information. Decisions are supported through understandable presentation of filtered and fused environmental and road condition information for specific time horizons as well as specific maintenance recommendations that are generated by the system based on this integrated information. The recommended courses of action are supported by information on the anticipated consequences of action or inaction, when available. | Maint and Constr Management Center |
MCM Roadway Maintenance | "MCM Roadway Maintenance" provides overall management and support for routine maintenance on a roadway system or right-of-way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. | Maint and Constr Management Center |
MCM Winter Maintenance Management | "MCM Winter Maintenance Management" manages winter road maintenance, tracking and controlling snow plow operations, roadway treatment (e.g., salt spraying and other material applications), and other snow and ice control operations. It monitors environmental conditions and weather forecasts and uses the information to schedule winter maintenance activities, determine the appropriate snow and ice control response, and track and manage response operations. | 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 |
MCV Roadway Maintenance and Construction | "MCV Roadway Maintenance and Construction" includes the on-board systems that support routine non-winter maintenance on a roadway system or right-of-way. Routine maintenance includes landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). | Maint and Constr Vehicle OBE |
MCV Winter Maintenance | "MCV Winter Maintenance" supports snow plow operations and other roadway treatments (e.g., salt spraying and other material applications). It supports communications with the center to receive information and instructions that are provided to the vehicle operator and also supports remote control of on-board systems. It tracks operational status of snow and ice control operations and provides this information back to the center. | Maint and Constr Vehicle OBE |
Includes Information Flows:
Information Flow | Description |
---|---|
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. |
maint and constr administrative information | Administrative information that is provided to support maintenance and construction operations. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration. |
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 dispatch information | Information used to dispatch maintenance and construction vehicles, equipment, and crews and information used to keep work zone crews informed. This information includes routing information, traffic information, road restrictions, incident information, environmental information, decision support information, maintenance schedule data, dispatch instructions, personnel assignments, alert notifications, and corrective actions. |
maint and constr dispatch status | Current maintenance and construction status including work data, operator status, crew status, and equipment status. |
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 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. |
maint and constr work performance | Overall project status and work performance information provided to support contract administration. |
maintenance materials storage status | The amount and availability of maintenance materials in storage facilities. |
Application Interconnect Diagram
SVG Diagram
PNG Diagram
Application Triples
Requirements
Need | Requirement | ||
---|---|---|---|
N1.001 | Transportation agencies need to gather data from vehicles or infrastructure to support environmental monitoring. | 1.001 | All environmental applications shall collect data from mobile devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, and other road weather information. |
1.002 | All environmental applications shall collect data from infrastructure devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, wind speed, and other road weather information. | ||
N1.081 | The Road Weather Information for Maintenance and Fleet Management System needs to collect data from private, commercial, specialty and public fleet vehicles to improve year-round maintenance plans and recommendations. | 1.180 | The Road Weather Information for Maintenance and Fleet Management System shall collect environmental data (e.g. ambient air quality, emissions, temperature, wind speed, and other road weather information). |
1.181 | The Road Weather Information for Maintenance and Fleet Management System shall collect pavement status. | ||
1.182 | The Road Weather Information for Maintenance and Fleet Management System shall collect vehicle materials (e.g., chemicals and supplies) status. | ||
N1.082 | The Road Weather Information for Maintenance and Fleet Management System needs to process current and historical data from multiple sources in order to provide enhanced support for year-round maintenance operations. | 1.183 | The Road Weather Information for Maintenance and Fleet Management System shall use historical and processed environmental data to predict environmental conditions. |
1.184 | The Road Weather Information for Maintenance and Fleet Management System shall use historical and processed environmental data to develop recommended treatment plans and response strategies. | ||
N1.083 | The Road Weather Information for Maintenance and Fleet Management System needs to share year-round roadway plans and recommendations to agency maintenance personnel. | 1.185 | The Road Weather Information for Maintenance and Fleet Management System shall disseminate year-round roadway plans to agency personnel. |
N1.084 | The Road Weather Information for Maintenance and Fleet Management Vehicle System needs to provide actionable information and year-round road maintenance recommendations to the driver. | 1.186 | The Road Weather Information Maintenance and Fleet Management Vehicle System shall provide road maintenance recommendations to drivers so they can make informed decisions for roadway maintenance |
Related Sources
- Concept of Operations for Road Weather Connected Vehicle Application, Final, 5/31/2013
- Concept of Operations For Road Weather Connected Vehicle Applications, Draft v1.4.2, 6/26/2012
Security
In order to participate in this application, each physical object should meet or exceed the following security levels.
Physical Object Security | ||||
---|---|---|---|---|
Physical Object | Confidentiality | Integrity | Availability | Security Class |
Security levels have not been defined yet. |
In order to participate in this application, 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 | |||
Security levels have not been defined yet. |