Parent Service Package: MC10
< < MC10.2 : MC10.3 : MC10.4 > >

MC10.3: Active RFID Technologies and Remote Control

Use remote controlled aerial drones or surface vehicles to collect asset data remotely, using active RFID tags to track assets.

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

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

Enterprise

Development Stage Roles and Relationships
(hide)

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

Installation Stage Roles and Relationships
(hide)

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

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Asset Management System Maintainer	Asset Management System	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Asset Management System Manager	Asset Management System	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Asset Management System Manager	Asset Management System Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Asset Management System Operator	Asset Management System	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Asset Management System Owner	Asset Management System Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Asset Management System Owner	Asset Management System Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Asset Management System Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Asset Management System Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Asset Management System Owner	Maint and Constr Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Asset Management System Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Asset Management System Supplier	Asset Management System Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Field Maintainer	Field	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Field Manager	Field	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Field Manager	Maint and Constr Field Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Field Owner	Field Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Field Owner	Field Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Field Owner	Maint and Constr Vehicle OBE Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Field Owner	Maint and Constr Vehicle OBE Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Field Owner	Maint and Constr Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Field Owner	Maint and Constr Vehicle Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Field Supplier	Field Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Maint and Constr Center Personnel	Maint and Constr Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Field Personnel	Field	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Field Personnel	Personnel Device	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Management Center Maintainer	Maint and Constr Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Maint and Constr Management Center Manager	Maint and Constr Center Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Maint and Constr Management Center Manager	Maint and Constr Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Maint and Constr Management Center Owner	Asset Management System Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Asset Management System Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Maint and Constr Management Center Owner	Asset Management System Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Maint and Constr Management Center Owner	Asset Management System User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Maint and Constr Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Maint and Constr Management Center Owner	Maint and Constr Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Maint and Constr Management Center Supplier	Maint and Constr Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Maint and Constr Vehicle OBE Maintainer	Maint and Constr Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Maint and Constr Vehicle OBE Manager	Maint and Constr Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Maint and Constr Vehicle OBE Manager	Maint and Constr Vehicle Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Maint and Constr Vehicle OBE Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Maint and Constr Vehicle OBE Owner	Maint and Constr Field Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Maint and Constr Vehicle OBE Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Vehicle OBE Owner	Maint and Constr Management Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Maint and Constr Vehicle OBE Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Vehicle OBE Owner	Maint and Constr Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Maint and Constr Vehicle OBE Owner	Maint and Constr Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Maint and Constr Vehicle OBE Owner	Personnel Device Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Vehicle OBE Owner	Personnel Device Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Maint and Constr Vehicle OBE Owner	Personnel Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Vehicle OBE Supplier	Maint and Constr Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Maint and Constr Vehicle Operator	Maint and Constr Vehicle OBE	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Personnel Device Maintainer	Personnel Device	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Personnel Device Manager	Maint and Constr Field Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Personnel Device Manager	Personnel Device	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Personnel Device Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personnel Device Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personnel Device Owner	Maint and Constr Management Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personnel Device Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personnel Device Owner	Maint and Constr Vehicle OBE Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personnel Device Owner	Maint and Constr Vehicle OBE Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Personnel Device Owner	Maint and Constr Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personnel Device Owner	Maint and Constr Vehicle Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personnel Device Owner	Personnel Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personnel Device Owner	Personnel Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personnel Device Supplier	Personnel Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Field	Field Asset Identification	10.5.3.5	Monitor Field Device Diagnostics
Maint and Constr Management Center	MCM Field Asset Tracking	9.2.3.4	Manage M&C Resource Needs
		9.2.5	Provide M&C Center Personnel Interface for Maint
		9.2.6.5	Manage Infrastructure Asset Data
Maint and Constr Vehicle OBE	MCV Field Asset Locating	9.1.6	Provide M&C Vehicle Operator Interface for Maint
Maint and Constr Vehicle OBE	MCV Field Asset Locating	9.3.1.2	Operate WZ Devices On-Board
Personnel Device	Personnel Field Asset Locating	9.3.4.6	Monitor Work Zone Assets
Personnel Device	Personnel Remote Vehicle Control	9.3.4.7	Control Remote Devices

Physical

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

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
Asset Management System	Center	'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies.
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.
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.

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
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
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

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 locations	Aggregate collected data including identified assets and their locations.
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.
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

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Document Name	Version	Publication Date
None

Security

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

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Asset Management System	Moderate	Moderate	Moderate	Class 2
Field	Low	Moderate	Moderate	Class 1
Maint and Constr Management Center	Moderate	Moderate	Moderate	Class 2
Maint and Constr Vehicle OBE	Moderate	Moderate	Moderate	Class 2
Personnel Device	Moderate	Moderate	Moderate	Class 2

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

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Asset Management System	Maint and Constr Management Center	asset inventory	Moderate	Moderate	Low
Asset Management System	Maint and Constr Management Center	asset inventory	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.
Field	Maint and Constr Vehicle OBE	asset ID	Low	Moderate	Moderate
Field	Maint and Constr Vehicle OBE	asset ID	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
Maint and Constr Center Personnel	Maint and Constr Management Center	maint and constr center personnel input	Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH.	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.	Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Maint and Constr Field Personnel	Personnel Device	personnel input	Low	Moderate	Low
Maint and Constr Field Personnel	Personnel Device	personnel input	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
Maint and Constr Management Center	Asset Management System	asset inventory locations	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	Maint and Constr Center Personnel	maint and constr operations information presentation	Not Applicable	Moderate	Moderate
Maint and Constr Management Center	Maint and Constr Center Personnel	maint and constr operations information presentation	System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment	Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation.	The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Maint and Constr Vehicle OBE	Maint and Constr Management Center	asset locations	Moderate	Moderate	Moderate
Maint and Constr Vehicle OBE	Maint and Constr Management Center	asset locations	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	asset locations	Moderate	Moderate	Moderate
Maint and Constr Vehicle OBE	Personnel Device	asset locations	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
Maint and Constr Vehicle OBE	Personnel Device	remote vehicle status	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.
Personnel Device	Maint and Constr Field Personnel	personnel updates	Low	High	Moderate
Personnel Device	Maint and Constr Field Personnel	personnel updates	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
Personnel Device	Maint and Constr Management Center	asset locations	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
Personnel Device	Maint and Constr Vehicle OBE	remote vehicle control commands	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.

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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

System Requirements

No System Requirements