MC10: Asset Tracking
This service package supports asset tracking using RFID technologies to maintain accurate inventory status that includes asset locations. The full range of RFID technologies are supported from passive technologies supporting near field communications through active tags that support additional storage and greater communications range. Support for handheld/portable readers, fixed RSE-based readers, and vehicle-based readers including both wheeled and aerial (e.g., drone) vehicles is provided. The collected asset location data is made available to other maintenance and construction applications and asset management.
Complete, up-to-date knowledge of deployed maintenance and construction asset locations can also be used to provide better information to approaching vehicles. If asset tracking identifies assets in travel lanes or other safety issues, this service package can issue warnings to drivers and work crews in the area. This information is specifically useful to automated vehicles, which also need to assess whether road segments with active construction and maintenance activities are within their operational design domain. If not, automated vehicles can begin the process of notifying drivers and preparing them to take over driving responsibility as road segments with deployed work zone assets are approached.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
- Implementations
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Asset Management System Maintainer | Asset Management System | Maintains |
| Asset Management System Manager | Asset Management System | Manages |
| Asset Management System Owner | Asset Management System Maintainer | System Maintenance Agreement |
| Asset Management System Owner | Asset Management System Manager | Operations Agreement |
| Asset Management System Owner | Maint and Constr Center Personnel | Application Usage Agreement |
| Asset Management System Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
| Asset Management System Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
| Asset Management System Owner | Maint and Constr Management Center User | Service Usage Agreement |
| Asset Management System Supplier | Asset Management System Owner | Warranty |
| Connected Vehicle Roadside Equipment Maintainer | Connected Vehicle Roadside Equipment | Maintains |
| Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment | Manages |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Maintainer | System Maintenance Agreement |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Manager | Operations Agreement |
| Connected Vehicle Roadside Equipment Owner | Maint and Constr Center Personnel | Application Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Maint and Constr Management Center Owner | Information Exchange and Action Agreement |
| Connected Vehicle Roadside Equipment Owner | Maint and Constr Management Center User | Service Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Vehicle Owner | Information Exchange and Action Agreement |
| Connected Vehicle Roadside Equipment Owner | Vehicle User | Service Usage Agreement |
| Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
| Field Maintainer | Field | Maintains |
| Field Manager | Field | Manages |
| Field Manager | Maint and Constr Field Personnel | System Usage Agreement |
| Field Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
| Field Owner | Connected Vehicle Roadside Equipment Owner | Information Exchange and Action Agreement |
| Field Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
| Field Owner | Field Maintainer | System Maintenance Agreement |
| Field Owner | Field Manager | Operations Agreement |
| Field Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Field Owner | Maint and Constr Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
| Field Owner | Maint and Constr Vehicle OBE Owner | Information Exchange and Action Agreement |
| Field Owner | Maint and Constr Vehicle OBE User | Service Usage Agreement |
| Field Owner | Maint and Constr Vehicle Operator | Application Usage Agreement |
| Field Owner | Personnel Device Maintainer | Maintenance Data Exchange Agreement |
| Field Owner | Personnel Device Owner | Information Exchange and Action Agreement |
| Field Owner | Personnel Device User | Service Usage Agreement |
| Field Supplier | Field Owner | Warranty |
| Maint and Constr Center Personnel | Maint and Constr Management Center | Operates |
| Maint and Constr Field Personnel | Field | Operates |
| Maint and Constr Field Personnel | Personnel Device | Operates |
| Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
| Maint and Constr Management Center Manager | Maint and Constr Center Personnel | System Usage Agreement |
| Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
| Maint and Constr Management Center Owner | Asset Management System Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Asset Management System Owner | Information Exchange Agreement |
| Maint and Constr Management Center Owner | Asset Management System User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Connected Vehicle Roadside Equipment Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Vehicle OBE Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Vehicle OBE User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Vehicle Operator | Application Usage Agreement |
| Maint and Constr Management Center Owner | Personnel Device Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Personnel Device Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Personnel Device User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Transportation Information Center User | Service Usage Agreement |
| Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
| Maint and Constr Vehicle OBE Maintainer | Maint and Constr Vehicle OBE | Maintains |
| Maint and Constr Vehicle OBE Manager | Maint and Constr Vehicle OBE | Manages |
| Maint and Constr Vehicle OBE Manager | Maint and Constr Vehicle Operator | System Usage Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Center Personnel | Application Usage Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Center Personnel | Vehicle Operating Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Field Personnel | Vehicle Operating Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Management Center Owner | Expectation of Data Provision |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Management Center User | Service Usage Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Vehicle OBE Maintainer | System Maintenance Agreement |
| Maint and Constr Vehicle OBE Owner | Maint and Constr Vehicle OBE Manager | Operations Agreement |
| Maint and Constr Vehicle OBE Owner | Personnel Device Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Vehicle OBE Owner | Personnel Device Owner | Expectation of Data Provision |
| Maint and Constr Vehicle OBE Owner | Personnel Device User | Service Usage Agreement |
| Maint and Constr Vehicle OBE Supplier | Maint and Constr Vehicle OBE Owner | Warranty |
| Maint and Constr Vehicle Operator | Maint and Constr Vehicle OBE | Operates |
| Personnel Device Maintainer | Personnel Device | Maintains |
| Personnel Device Manager | Maint and Constr Field Personnel | System Usage Agreement |
| Personnel Device Manager | Personnel Device | Manages |
| Personnel Device Owner | Maint and Constr Center Personnel | Application Usage Agreement |
| Personnel Device Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
| Personnel Device Owner | Maint and Constr Management Center Owner | Information Provision and Action Agreement |
| Personnel Device Owner | Maint and Constr Management Center User | Service Usage Agreement |
| Personnel Device Owner | Maint and Constr Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
| Personnel Device Owner | Maint and Constr Vehicle OBE Owner | Information Provision and Action Agreement |
| Personnel Device Owner | Maint and Constr Vehicle OBE User | Service Usage Agreement |
| Personnel Device Owner | Maint and Constr Vehicle Operator | Application Usage Agreement |
| Personnel Device Owner | Personnel Device Maintainer | System Maintenance Agreement |
| Personnel Device Owner | Personnel Device Manager | Operations Agreement |
| Personnel Device Supplier | Personnel Device Owner | Warranty |
| Transportation Information Center Maintainer | Transportation Information Center | Maintains |
| Transportation Information Center Manager | Transportation Information Center | Manages |
| Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
| Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
| Transportation Information Center Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
| Transportation Information Center Owner | Vehicle Owner | Information Provision Agreement |
| Transportation Information Center Owner | Vehicle User | Service Usage Agreement |
| Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
| Vehicle Maintainer | Vehicle | Maintains |
| Vehicle Manager | Vehicle | Manages |
| Vehicle Owner | Vehicle Maintainer | System Maintenance Agreement |
| Vehicle Owner | Vehicle Manager | Operations Agreement |
| Vehicle Supplier | Vehicle Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Asset Management System | Center | 'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies. |
| Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
| Field | Field | This general physical object is used to model core capabilities that are common to any piece of field equipment. |
| 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 Field Personnel | Field | Represents the people that perform maintenance and construction field activities including vehicle and equipment operators, field supervisory personnel, field crews, and work zone safety personnel. Information flowing from the Maintenance and Construction Field Personnel will include those system inputs specific to maintenance and construction operations, such as information regarding work zone status, or the status of maintenance actions. The field personnel are also monitored within the work zone to enhance work zone safety. Information provided to Maintenance and Construction Field Personnel includes dispatch requests, maintenance and construction actions to be performed, and work zone safety warnings. |
| Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| Maint and Constr Vehicle OBE | Vehicle | The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles. |
| Maint and Constr Vehicle Operator | Vehicle | The operator of maintenance, construction, or other specialized service vehicles or equipment. Represents the maintenance and construction vehicle operators. The operator provides input specific to maintenance and construction vehicle operations, including the status of maintenance actions. Information provided to the operator includes dispatch requests and maintenance and construction actions to be performed. |
| Personnel Device | Personal | 'Personnel Device' represents devices used by emergency personnel or maintenance and construction personnel in the field. In the case of emergency personnel, the devices would include body cameras or smartphones (and their peripherals) that can be used by emergency personnel to provide images or video as well as send or receive data regarding the incident. The devices could also be used for incident scene safety messages to the personnel. In the case of maintenance and construction field personnel, the devices could be cellular phones or specialized safety devices that would be used for work zone safety messages to the personnel. |
| Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
| Vehicle | Vehicle | This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Field Asset Identification | 'Field Asset Identification' stores and provides a unique identifier on request. The full range of RFID solutions are covered ranging from passive tags that support only near-field communications to active tags that support longer read ranges and writeable storage options. More advanced implementations can store and provide additional asset information in addition to the ID such as a lot number, production date, or last service date. | Field |
| MCM Field Asset Tracking | 'MCM Field Asset Tracking' maintains a database of field assets and their locations. It shares this asset tracking data with other maintenance and construction applications that monitor and use the assets. It also identifies assets in travel lanes that may pose a safety hazard and shares this information for use in mitigating the safety risk through local vehicle warnings and maintenance crew notification. | Maint and Constr Management Center |
| MCM Remote Vehicle Control | 'MCM Remote Vehicle Control' provides the capability for center personnel to control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. The remote control capability includes the capability to control the vehicles location, trajectory, and velocity and additional application-specific controls that control the operations and maintenance capabilities provided by the remote controlled vehicle. Note that center-based control relies on sophisticated automated control capabilities on-board the vehicle with a sufficient operational design domain so the vehicle can operate safely without second-by-second control in most environments and scenarios. | Maint and Constr Management Center |
| MCV Field Asset Locating | 'MCV Field Asset Locating' scans RFID-equipped assets and records their location relative to the scanning device. In this case, the scanning device is housed in a vehicle that may be controlled directly by a human driver or controlled remotely. The asset locating system must know its location in 3D coordinates and calculate a range vector to the RFID tag. It can then provide the location and RFID ID to a back office service. | Maint and Constr Vehicle OBE |
| MCV Vehicle Location Tracking | 'MCV Vehicle Location Tracking' monitors vehicle location and reports the position and timestamp information to the dispatch center. | Maint and Constr Vehicle OBE |
| Personnel Field Asset Locating | 'Personnel Field Asset Locating' scans RFID-equipped assets and records their location relative to the scanning device. In this case, the scanning device is a handheld or portable system that is physical carried and used by field personnel. The asset locating system must know its location in 3D coordinates and calculate a range vector to the RFID tag. It can then provide the location and RFID ID to a back office service. | Personnel Device |
| Personnel Remote Vehicle Control | 'Personnel Remote Vehicle Control' provides the capability for field personnel to control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. The remote control capability includes the capability to control the vehicles location, trajectory, and velocity and additional application-specific controls that control the operations and maintenance capabilities provided by the remote controlled vehicle. | Personnel Device |
| RSE Field Asset Locating | 'RSE Field Asset Locating' scans RFID-equipped assets and records their location relative to the scanning device. In this case, the scanning device is a fixed piece of field equipment that monitors RFID tags within range. The asset locating system must know its location in 3D coordinates and calculate a range vector to the RFID tag. It can then provide the location and RFID ID to a back office service. | Connected Vehicle Roadside Equipment |
| RSE Traveler Information Communications | 'RSE Traveler Information Communications' includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles. | Connected Vehicle Roadside Equipment |
| TIC Traffic Control Dissemination | 'TIC Traffic Control Dissemination' disseminates intersection status, lane control information, special vehicle alerts, and other traffic control related information that is real-time or near real-time in nature and relevant to vehicles in a relatively local area on the road network. It collects traffic control information from Traffic Management and other Center(s) and disseminates the relevant information to vehicles and other mobile devices. | Transportation Information Center |
| Vehicle Traveler Information Reception | 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. | Vehicle |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| asset ID | A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID. |
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. |
| asset inventory locations | Current location and status of tracked asset inventory items. |
| asset location safety warning | Notification that asset locations have been identified that are either in or too close to designated travel lanes. This flow identifies the assets and their locations to work crews that can address the detected asset location issues. |
| asset locations | Aggregate collected data including identified assets and their locations. |
| infrastructure safety warning | Identified infrastructure issues such as objects in travel lanes, damaged or compromised safety features, and other safety issues with potential road safety impacts that are identified and reported by the infrastructure. |
| infrastructure safety warning notification | Notification of infrastructure issues such as objects in travel lanes, damaged or compromised safety features, and other field infrastructure issues with potential road safety impacts that are identified and reported by the infrastructure. |
| maint and constr center personnel input | User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination. |
| maint and constr operations information presentation | Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning. |
| maint and constr vehicle location data | The current location and related status (e.g., direction and speed) of the maintenance/construction vehicle. |
| maint and constr vehicle operational data | Data that describes the maintenance and construction activity performed by the vehicle. Operational data includes materials usage (amount stored and current application rate), operational state of the maintenance equipment (e.g., blade up/down, spreader pattern), vehicle safety status, and other measures associated with the operation of a maintenance, construction, or other special purpose vehicle. Operational data may include basic operational status of the vehicle equipment or a more precise record of the work performed (e.g., application of crack sealant with precise locations and application characteristics). |
| maint and constr vehicle operator input | User input from field personnel including current maintenance and construction status information as well as on-board device control. |
| maint and constr vehicle operator presentation | Information presented to maintenance and construction field personnel including vehicle routing and traffic information, road restrictions, environmental information, decision support information, maintenance schedules, dispatch instructions, maintenance personnel assignments, vehicle maintenance information, work zone status information, and corrective actions. |
| maint and constr vehicle system control | Configure and control data that supports remote control of on-board maintenance and construction vehicle systems and field equipment that is remotely controlled by the vehicle. For example, the data can be used to adjust material application rates and spread patterns. |
| personnel input | Field personnel input to a Personnel Device. This flow may provide input to applications operating on the Personnel Devices. This flow also establishes the settings that tailor each application to suit the user's needs. |
| personnel updates | Alerts and warnings provided to emergency personnel or work crew members. This includes visual, audio, and haptic outputs that may be customized to support individual needs. |
| remote vehicle control commands | Commands provided to control an unmanned vehicle's location and motion and it's application specific capabilities (e.g., environmental monitoring, asset tracking, mowing, lane striping,...) |
| remote vehicle status | Current status provided back from a remotely controlled vehicle including operational status (e.g., battery/fuel status), location, heading, and current actuator/control status. |
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
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 | Maintenance and constructions operations need to be able to maintain inventory status of maintenance and construction assets. | MCM Field Asset Tracking | 02 | The center shall maintain accurate inventory status of maintenance and construction asset. |
| MCV Field Asset Locating | 01 | The field device housed in a vehicle shall scan MC assets and record their location relative to the scanning device. | ||
| Personnel Field Asset Locating | 01 | The field device operated by field personnel shall scan MC assets and record their location relative to the scanning device. | ||
| RSE Field Asset Locating | 01 | The field device shall scan MC assets and record their location relative to the scanning device. | ||
| 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. | Field Asset Identification | 01 | The field device shall provide a unique identification number that is used for identification and tracking of assets. |
| MCM Field Asset Tracking | 01 | The center shall monitor the locations of all maintenance and construction assets under its jurisdiction. | ||
| MCM Remote Vehicle Control | 01 | The center shall remotely control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. | ||
| MCV Vehicle Location Tracking | 01 | The maintenance and construction vehicle shall track its current location. | ||
| 02 | The maintenance and construction vehicle shall send the time stamped vehicle location to the controlling center. | |||
| Personnel Field Asset Locating | 02 | The personnel device shall accept inputs from the user to manipulate field asset location activities. | ||
| 03 | The personnel device shall provide status information related to field asset locations to the user. | |||
| Personnel Remote Vehicle Control | 01 | The field device shall remotely control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. | ||
| 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. | MCM Field Asset Tracking | 03 | The center shall provide notification to work crew when assets are either in or too close to designated travel lanes. |
| RSE Traveler Information Communications | 14 | The field element shall warn drivers of field equipment in or near travel lanes and shoulders. | ||
| TIC Traffic Control Dissemination | 01 | The center shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. | ||
| 05 | The center shall be able to disseminate notification of infrastructure issues such as objects in or near travel lanes and shoulders. | |||
| Vehicle Traveler Information Reception | 02 | The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, border crossing advisories, and other special information. | ||
| 06 | The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information | |||
| 15 | The vehicle shall receive roadway safety information of infrastructure issues such as objects in or near travel lanes. | |||
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Asset Management System | Moderate | Moderate | Moderate | Class 2 |
| Connected Vehicle Roadside Equipment | Moderate | Moderate | Moderate | Class 2 |
| Field | Low | Moderate | Moderate | Class 1 |
| Maint and Constr Management Center | Moderate | High | Moderate | Class 3 |
| Maint and Constr Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
| Personnel Device | Moderate | Moderate | Moderate | Class 2 |
| Transportation Information Center | Low | Moderate | Moderate | Class 1 |
| Vehicle | Low | Low | Moderate | Class 1 |
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Asset Management System | Maint and Constr Management Center | asset inventory | Moderate | Moderate | Low |
| All observable information, but when placed in one spot becomes a "one stop shop" for a nefarious person looking for infrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately assigned. | Probably does not change very often, so the impact of loss of connectivity should be minimal. | |||
| Connected Vehicle Roadside Equipment | Maint and Constr Management Center | asset locations | Moderate | Moderate | Moderate |
| All observable information, and not easy to observe given that one end of the flow is moving around a construction site. However, observation at the non-moving end of the flow creates the "one stop shop", so should be protected from the nefarious for person looking for intrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Connected Vehicle Roadside Equipment | Vehicle | infrastructure safety warning notification | Low | Moderate | Moderate |
| This information is directly observable. | This information may be used to alert the driver or as input to autonomous safety systems. Incorrect data could cause unproductive analysis, additional processing and decrease overall trust in the system. | If the containing service is deployed the satisfaction of this flow is critical to its performance, so MODERATE to ensure a reasonable likelihood of overall performance. If both WAW and short range communications are used, one can be reduced to LOW. | |||
| Field | Connected Vehicle Roadside Equipment | asset ID | Low | Moderate | Moderate |
| Unlikely that the ID of a particular asset, or even a group of assets would be useful to an attacker. Slight possibility, which is why Low vs. N/A. | Infrastructure information should be correct or maintenance assets may be inappropriately assigned, located or otherwise referenced. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Field | Maint and Constr Vehicle OBE | asset ID | Low | Moderate | Moderate |
| Unlikely that the ID of a particular asset, or even a group of assets would be useful to an attacker. Slight possibility, which is why Low vs. N/A. | Infrastructure information should be correct or maintenance assets may be inappropriately assigned, located or otherwise referenced. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Field | Personnel Device | asset ID | Low | Moderate | Moderate |
| Unlikely that the ID of a particular asset, or even a group of assets would be useful to an attacker. Slight possibility, which is why Low vs. N/A. | Infrastructure information should be correct or maintenance assets may be inappropriately assigned, located or otherwise referenced. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Maint and Constr Center Personnel | Maint and Constr Management Center | maint and constr center personnel input | High | High | High |
| Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
| Maint and Constr Field Personnel | Personnel Device | personnel input | Low | Moderate | Low |
| Input related to Emergency-related application. There could be sensitive information depending on the application, particularly regarding the health of someone involved in an incident the emergency personnel is responding to, in which case this rating might increase. | This data should be correct to enable accurate application functionality, but is likely not critical and easily corrected. | There should generally other ways to accomplish this flow. | |||
| Maint and Constr Management Center | Asset Management System | asset inventory locations | Moderate | Moderate | Moderate |
| All observable information, but when placed in one spot becomes a "one stop shop" for a nefarious person looking for infrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. | |||
| Maint and Constr Management Center | Connected Vehicle Roadside Equipment | infrastructure safety warning | Low | Moderate | Moderate |
| This information is directly observable. | This information may be used to alert the driver or as input to autonomous safety systems. Incorrect data could cause unproductive analysis, additional processing and decrease overall trust in the system. | If the containing service is deployed the satisfaction of this flow is critical to its performance, so MODERATE to ensure a reasonable likelihood of overall performance. | |||
| Maint and Constr Management Center | Maint and Constr Center Personnel | maint and constr operations information presentation | Not Applicable | Moderate | Moderate |
| System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment | Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. | The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take. | |||
| Maint and Constr Management Center | Maint and Constr Vehicle OBE | asset location safety warning | Low | Moderate | Moderate |
| Should be directly observable data; remote observation would be of limited value to a would-be attacker. | A few false warnings should not have a bad consequence. When field personnel receive a warning they can look around and verify whether or not the situation warrants action. | It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more field personnel can rely on it. | |||
| Maint and Constr Management Center | Maint and Constr Vehicle OBE | maint and constr vehicle system control | Moderate | High | Moderate |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | There should be multiple mechanisms for this information to arrive at the end recipient. If this is the only mechanism, should be raised to MODERATE. | |||
| Maint and Constr Management Center | Personnel Device | asset location safety warning | Low | Moderate | Moderate |
| Should be directly observable data; remote observation would be of limited value to a would-be attacker. | A few false warnings should not have a bad consequence. When field personnel receive a warning they can look around and verify whether or not the situation warrants action. | It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more field personnel can rely on it. | |||
| Maint and Constr Management Center | Transportation Information Center | infrastructure safety warning | Low | Moderate | Moderate |
| This information is directly observable. | This information may be used to alert the driver or as input to autonomous safety systems. Incorrect data could cause unproductive analysis, additional processing and decrease overall trust in the system. | If the containing service is deployed the satisfaction of this flow is critical to its performance, so MODERATE to ensure a reasonable likelihood of overall performance. | |||
| Maint and Constr Vehicle OBE | Maint and Constr Management Center | asset locations | Moderate | Moderate | Moderate |
| All observable information, and not easy to observe given that one end of the flow is moving around a construction site. However, observation at the non-moving end of the flow creates the "one stop shop", so should be protected from the nefarious for person looking for intrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Maint and Constr Vehicle OBE | Maint and Constr Management Center | maint and constr vehicle location data | Moderate | Moderate | Moderate |
| This is effectively a tracking flow, which if intercepted would provide a third party with the ability to track maintenance and construction vehicles, which could enable nefarious and illegal activities. | Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator. | Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator. | |||
| Maint and Constr Vehicle OBE | Maint and Constr Management Center | maint and constr vehicle operational data | Moderate | Moderate | Moderate |
| Contains information indicating the activity of the maintenance vehicle, which if public could be used against the vehicle or the infrastructure, depending on the hostile party's intent. | Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money. | Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money. | |||
| Maint and Constr Vehicle OBE | Maint and Constr Vehicle Operator | maint and constr vehicle operator presentation | Moderate | High | High |
| System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over the MCV. | System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken. | System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken. | |||
| Maint and Constr Vehicle OBE | Personnel Device | asset locations | Moderate | Moderate | Moderate |
| All observable information, and not easy to observe given that one end of the flow is moving around a construction site. However, observation at the non-moving end of the flow creates the "one stop shop", so should be protected from the nefarious for person looking for intrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Maint and Constr Vehicle OBE | Personnel Device | remote vehicle status | Moderate | Moderate | Moderate |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. While this flow does not control the device, it provides feedback to that control, and so should be similarly protected. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed "announcement". | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
| Maint and Constr Vehicle Operator | Maint and Constr Vehicle OBE | maint and constr vehicle operator input | Not Applicable | Moderate | High |
| Observation of control or status information is unlikely to have any value to a third party; actions of field personnel should be observable anyway. | Any driver/operator interaction with vehicle systems needs some assurance of correctness; corruption of this information could lead to unexpected vehicle behavior which poses a limited safety risk. | Without direct local control of vehicle systems the vehicle is essentially uncontrolled. | |||
| Personnel Device | Maint and Constr Field Personnel | personnel updates | Low | High | Moderate |
| This data is informing the user of safety-related issues in the local transportation environment. It probably does not contain anything sensitive, and should not matter if another person can observe it. | This is the information that is presented to the individual in a work zone or incident response area that may be unpredictable in its formation. If the user receives incorrect information, they may act in an unsafe manner. | If this information is not made available to the pedestrian, then the user may be endangered. This is the not only mechanism the user may have to avoid potential dangers (they can observe directly). | |||
| Personnel Device | Maint and Constr Management Center | asset locations | Moderate | Moderate | Moderate |
| All observable information, and not easy to observe given that one end of the flow is moving around a construction site. However, observation at the non-moving end of the flow creates the "one stop shop", so should be protected from the nefarious for person looking for intrastructure targets. | Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. | Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance. | |||
| Personnel Device | Maint and Constr Vehicle OBE | remote vehicle control commands | Moderate | Moderate | Moderate |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed "announcement". | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
| Transportation Information Center | Vehicle | infrastructure safety warning notification | Low | Moderate | Moderate |
| This information is directly observable. | This information may be used to alert the driver or as input to autonomous safety systems. Incorrect data could cause unproductive analysis, additional processing and decrease overall trust in the system. | If the containing service is deployed the satisfaction of this flow is critical to its performance, so MODERATE to ensure a reasonable likelihood of overall performance. If both WAW and short range communications are used, one can be reduced to LOW. | |||
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 |
|---|---|---|
| CTI 4001 RSU | Roadside Unit (RSU) Standard | Connected Vehicle Roadside Equipment |
System Requirements
| System Requirement | Need | ||
|---|---|---|---|
| 001 | The system shall monitor the locations of all maintenance and construction assets under its jurisdiction. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 002 | The system shall provide notification to work crew when assets are either in or too close to designated travel lanes. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 003 | The system shall maintain accurate inventory status of maintenance and construction assets. | 01 | Maintenance and constructions operations need to be able to maintain inventory status of maintenance and construction assets. |
| 004 | The system shall remotely control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 005 | The system shall be able to disseminate notification of infrastructure issues such as objects in or near travel lanes and shoulders. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 006 | The system shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 007 | The system shall provide a unique identification number that is used for identification and tracking of assets. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 008 | The system shall scans MC assets and records their location relative to the scanning device. | 01 | Maintenance and constructions operations need to be able to maintain inventory status of maintenance and construction assets. |
| 009 | The system shall warn drivers of field equipment in or near travel lanes and shoulders. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 010 | The system shall scan assets and record their location relative to the scanning device. | 01 | Maintenance and constructions operations need to be able to maintain inventory status of maintenance and construction assets. |
| 011 | The system shall accept inputs from the user to manipulate field asset location activities. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 012 | The system shall remotely control unmanned surface and aerial vehicles that support surface transportation operations and maintenance. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 013 | The system shall provide status information related to field asset locations to the user. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 014 | The system shall track the current location of maintenance and construction vehicles. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 015 | The system shall send the time stamped vehicle location to the controlling center. | 02 | Maintenance and construction operations need to be able to track the location of maintenance and construction assets. |
| 016 | The system shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special information. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 017 | The system shall present to the driver a visual display of static sign information or dynamic roadway conditions information | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
| 018 | The system shall receive roadway safety information of infrastructure issues such as objects in or near travel lanes. | 03 | Maintenance and construction operations need to be able to warn drivers and work crews of field assets in or near travel lanes and shoulders. |
Implementations
- MC10.1 Passive RFID Technologies
- MC10.2 Active RFID Technologies
- MC10.3 Active RFID Technologies and Remote Control
- MC10.4 Active RFID Technologies and Automated Vehicle Collection
- MC10.5 Asset Tracking Based Infrastructure Warnings
Display:
Implementation legend
or
Service Package legend
MC10.1 Passive RFID Technologies Implementation
Implement an Asset Tracking system using passive RFID tags that are read by portable readers. Current asset data is collected and made available to Maintenance and Construction Center personnel.
Passive RFID Technologies Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| asset ID | A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID. | Fundamental |
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. | Fundamental |
| asset inventory locations | Current location and status of tracked asset inventory items. | Fundamental |
| asset locations | Aggregate collected data including identified assets and their locations. | Fundamental |
| 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. | Optional |
| 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. | Optional |
| personnel input | Field personnel input to a Personnel Device. This flow may provide input to applications operating on the Personnel Devices. This flow also establishes the settings that tailor each application to suit the user's needs. | Optional |
| personnel updates | Alerts and warnings provided to emergency personnel or work crew members. This includes visual, audio, and haptic outputs that may be customized to support individual needs. | Optional |
Passive RFID Technologies Implementation Functional Objects
| Functional Object |
|---|
| Field Asset Identification |
| MCM Field Asset Tracking |
| Personnel Field Asset Locating |
Back to Implementation List
MC10.2 Active RFID Technologies Implementation
Implement an Asset Tracking system using active RFID tags with greater range, allowing supervisory vehicles and field equipment in the area to track assets within a local area.
Active RFID Technologies Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| asset ID | A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID. | At Least One |
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. | Fundamental |
| asset inventory locations | Current location and status of tracked asset inventory items. | Fundamental |
| asset locations | Aggregate collected data including identified assets and their locations. | At Least One |
| 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. | Optional |
| 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. | Optional |
| maint and constr vehicle operator input | User input from field personnel including current maintenance and construction status information as well as on-board device control. | Optional |
| maint and constr vehicle operator presentation | Information presented to maintenance and construction field personnel including vehicle routing and traffic information, road restrictions, environmental information, decision support information, maintenance schedules, dispatch instructions, maintenance personnel assignments, vehicle maintenance information, work zone status information, and corrective actions. | Optional |
Active RFID Technologies Implementation Functional Objects
| Functional Object |
|---|
| Field Asset Identification |
| MCM Field Asset Tracking |
| MCV Field Asset Locating |
| RSE Field Asset Locating |
Back to Implementation List
MC10.3 Active RFID Technologies and Remote Control Implementation
Use remote controlled aerial drones or surface vehicles to collect asset data remotely, using active RFID tags to track assets.
Active RFID Technologies and Remote Control Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| asset ID | A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID. | Fundamental |
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. | Fundamental |
| asset inventory locations | Current location and status of tracked asset inventory items. | Fundamental |
| asset locations | Aggregate collected data including identified assets and their locations. | At Least One |
| 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. | Optional |
| 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. | Optional |
| personnel input | Field personnel input to a Personnel Device. This flow may provide input to applications operating on the Personnel Devices. This flow also establishes the settings that tailor each application to suit the user's needs. | Optional |
| personnel updates | Alerts and warnings provided to emergency personnel or work crew members. This includes visual, audio, and haptic outputs that may be customized to support individual needs. | Optional |
| remote vehicle control commands | Commands provided to control an unmanned vehicle's location and motion and it's application specific capabilities (e.g., environmental monitoring, asset tracking, mowing, lane striping,...) | Fundamental |
| remote vehicle status | Current status provided back from a remotely controlled vehicle including operational status (e.g., battery/fuel status), location, heading, and current actuator/control status. | Fundamental |
Active RFID Technologies and Remote Control Implementation Functional Objects
| Functional Object |
|---|
| Field Asset Identification |
| MCM Field Asset Tracking |
| MCV Field Asset Locating |
| Personnel Field Asset Locating |
| Personnel Remote Vehicle Control |
Back to Implementation List
MC10.4 Active RFID Technologies and Automated Vehicle Collection Implementation
Active RFID tags are used to track assets. The aerial drone or surface vehicle used to track assets includes on-board sensors and intelligence so second-by-second remote control by a remote operator is not required. With this implementation, the center operator can interact with the automated asset tracking vehicle to set operating parameters and monitor operations.
Active RFID Technologies and Automated Vehicle Collection Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| asset ID | A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID. | Fundamental |
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. | Fundamental |
| asset inventory locations | Current location and status of tracked asset inventory items. | Fundamental |
| asset locations | Aggregate collected data including identified assets and their locations. | Fundamental |
| 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. | Optional |
| 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. | Optional |
| maint and constr vehicle location data | The current location and related status (e.g., direction and speed) of the maintenance/construction vehicle. | Fundamental |
| 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). | Fundamental |
| 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. | Fundamental |
Active RFID Technologies and Automated Vehicle Collection Implementation Functional Objects
| Functional Object |
|---|
| Field Asset Identification |
| MCM Field Asset Tracking |
| MCM Remote Vehicle Control |
| MCV Field Asset Locating |
| MCV Vehicle Location Tracking |
Back to Implementation List
MC10.5 Asset Tracking Based Infrastructure Warnings Implementation
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.
Asset Tracking Based Infrastructure Warnings Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| asset inventory | Information on pavement, bridges, signs and other assets. This includes asset location, installation information, materials information, vendor/contractor information, current maintenance status, and a variety of other information (e.g., video logs) that define the transportation infrastructure. | Fundamental |
| asset inventory locations | Current location and status of tracked asset inventory items. | Fundamental |
| asset location safety warning | Notification that asset locations have been identified that are either in or too close to designated travel lanes. This flow identifies the assets and their locations to work crews that can address the detected asset location issues. | At Least One |
| infrastructure safety warning | Identified infrastructure issues such as objects in travel lanes, damaged or compromised safety features, and other safety issues with potential road safety impacts that are identified and reported by the infrastructure. | At Least One |
| infrastructure safety warning notification | Notification of infrastructure issues such as objects in travel lanes, damaged or compromised safety features, and other field infrastructure issues with potential road safety impacts that are identified and reported by the infrastructure. | At Least One |
| 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. | Optional |
| 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. | Optional |
Asset Tracking Based Infrastructure Warnings Implementation Functional Objects
Back to Implementation List