< < MC10 : MC10 : MC11 > >

MC10: Asset Tracking Based Infrastructure Warnings

MC10 includes the capability to notify passing vehicles and motorists when asset tracking determines that an asset is located on or near the travel lanes and may pose a risk to passing vehicles or impact their operational design parameters. This SPI adds this infrastructure warning capability.

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

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name

Physical

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

Physical diagrams have not been developed for this application yet.


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description

Includes Functional Objects:

Functional Object Description Physical Object

Includes Information Flows:

Information Flow Description

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
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
H. Emphasize the preservation of the existing transportation system; Maintain infrastructure asset system

Associated Objective Categories

Objective Category
Integration: Transportation Data Collection
Preservation: Preserve Existing Infrastructure
Safety: Vehicle Crashes and Fatalities
Work Zone Management: Construction Coordination

Associated Objectives and Performance Measures

Objective Performance Measure
Enhance asset and resource management Extended pavement life due to truck weight enforcement
Enhance asset and resource management Number of assets tracked in real-time
Enhance asset and resource management Percentage of fleet/equipment within lifecycle
Enhance asset and resource management Percentage of geographic jurisdiction covered by agency electronic communications
Enhance asset and resource management Percentage of maintenance activities completed in required time-frame
Enhance asset and resource management Rate at which equipment is utilized
Enhance asset and resource management Vehicle operating costs
Enhance planning with better data Amount of data gathered from ITS enhancements used in infrastructure and operations planning
Enhance planning with better data Number of planning activities using data from ITS systems
Enhance planning with better data Years of data in database that is easily searchable and extractable
Establish a work zone management system within X years to facilitate coordination of work zones in the region. Presence of an established work zone management system.
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries per X VMT.

 
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

Related Sources

  • None


Security

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

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Security levels have not been defined yet.



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

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Security levels have not been defined yet.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.





Needs and Requirements

Need Functional Object Requirement

System Requirements

No System Requirements