Parent Service Package: SU11
< < SU10.1 : SU11.1 : SU12.1 > >

SU11.1: Field Equipment Maintenance Implementation

This 'implementation' is a holistic view of the SU11 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

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
Center Developer	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.
Center Developer	Field 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.
Center Developer	Maint and Constr Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Field Developer	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	Field Maintenance Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Field 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	Service Monitor 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.
Field Maintenance Equipment Developer	Field 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 Maintenance Equipment Developer	Field Maintenance Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Maint and Constr Management Center Developer	Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Maint and Constr Management Center Developer	Field 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.
Service Monitor System Developer	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.
Service Monitor System Developer	Service Monitor 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.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Center Installer	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.
Center Owner	Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Center Owner	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.
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 Maintenance Equipment Installer	Field Maintenance Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Field Maintenance Equipment Owner	Field Maintenance Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Field Maintenance Equipment Owner	Field Maintenance Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
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.
Service Monitor System Installer	Service Monitor 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.
Service Monitor System Owner	Service Monitor System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Service Monitor System Owner	Service Monitor 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.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Center Maintainer	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.
Center Manager	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.
Center Manager	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.
Center Owner	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.
Center Owner	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.
Center Owner	Field 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.
Center Owner	Field 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.
Center Owner	Field 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.
Center Owner	Field User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Center Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Center 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.
Center Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Center Owner	Maint and Constr Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Center Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Center Personnel	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.
Center Supplier	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.
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 Maintenance Equipment Maintainer	Field Maintenance Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Field Maintenance Equipment Manager	Field Maintenance Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Field Maintenance Equipment 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 Maintenance Equipment Owner	Field 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 Maintenance Equipment Owner	Field Maintenance Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Field Maintenance Equipment Owner	Field Maintenance Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Field Maintenance Equipment Owner	Field 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.
Field Maintenance Equipment Owner	Field 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.
Field Maintenance Equipment Owner	Field 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 Maintenance Equipment 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.
Field Maintenance Equipment Supplier	Field Maintenance Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
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	Field 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.
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	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.
Field Owner	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.
Field Owner	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.
Field Owner	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.
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 Maintenance Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Field Owner	Field Maintenance Equipment 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.
Field Owner	Field Maintenance Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
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 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.
Field 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.
Field 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.
Field 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.
Field 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.
Field Owner	Service Monitor 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.
Field Owner	Service Monitor 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.
Field Owner	Service Monitor System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Field Owner	Service Monitor 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.
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.
Field System Operator	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 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	Field Maintenance Equipment	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	Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Maint and Constr Management Center Owner	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 Management Center Owner	Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Field 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	Field 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	Field 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	Field 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 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 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.
Service Monitor System Maintainer	Service Monitor 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.
Service Monitor System Manager	Service Monitor 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.
Service Monitor System Manager	Service Monitor 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.
Service Monitor System Operator	Service Monitor 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.
Service Monitor System Owner	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.
Service Monitor System Owner	Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Service Monitor System Owner	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.
Service Monitor System Owner	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.
Service Monitor System Owner	Service Monitor 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.
Service Monitor System Owner	Service Monitor 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.
Service Monitor System Supplier	Service Monitor 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.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Center	Center Field Equipment Management	10.5.1.1	Monitor Roadside Equipment Fault Data
Center	Center Field Equipment Management	10.5.1.2	Manage Connected Vehicle Applications
Field	Field System Executive	10.5.3.4	Manage Field Systems Configuration
		10.5.3.6	Provide Field Device Operator Interface
		9.2.3.6	Collect Field Equipment Status for Repair
	Field System Monitoring and Diagnostics	10.5.3.5	Monitor Field Device Diagnostics
	Field System Monitoring and Diagnostics	10.5.3.6	Provide Field Device Operator Interface
Field Maintenance Equipment	FME On-Site Maintenance	10.5.3.3	Provide Field Equipment Maintenance
Maint and Constr Management Center	MCM Field Equipment Maintenance	9.2.1	Schedule M&C Activities
		9.2.2	Status Current M&C Activities and Transportation Infrastructure
		9.2.3.5	Collect Roadside Equipment Status
		9.2.3.9	Determine Field Equipment M&C Needs
		9.2.5	Provide M&C Center Personnel Interface for Maint
Service Monitor System	SM Device Management	10.5.4	Provide Device Support Services Operator Interface
Service Monitor System	SM Device Management	10.5.5	Monitor System Activities

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
Center	Center	This general physical object is used to model core capabilities that are common to any center.
Center Personnel	Center	'Center Personnel' represent system operators and other personnel that work within a transportation center. This interface supports modeling of general human interactions that are common to any center.
Field	Field	This general physical object is used to model core capabilities that are common to any piece of field equipment.
Field Maintenance Equipment	Field	'Field Maintenance Equipment' represents the portable equipment used by field personnel to locally troubleshoot, initialize, reprogram, and test infrastructure equipment. It may include a laptop, specialized diagnostics tools, or any other general purpose or specialized equipment that is interfaced locally to infrastructure equipment to support maintenance and repair.
Field System Operator	Field	'Field System Operator' represents the operators of field equipment such as parking management systems, intermodal terminals, and other field equipment that is supported by a local operator. The interface supports modeling of general human interface interactions that are common to all staffed 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.
Service Monitor System	Support	The 'Service Monitor System' represents one or more center-based systems that provide monitoring, management and control services necessary to other applications and/or devices operating within the Connected Vehicle Environment. These support services enable other applications to provide transportation services.

Includes Functional Objects:

Functional Object	Description	Physical Object
Center Field Equipment Management	'Center Field Equipment Management' is the back office application that supports monitoring and maintenance of field equipment. It monitors the performance and configuration of the field equipment. This includes management of the infrastructure configuration as well as detection, isolation, and correction of field equipment problems. The application also includes monitoring of performance of the field equipment, including communications links.	Center
Field System Executive	'Field System Executive' includes the operating system kernel and executive functions that manage the overall device software configuration and operation and support configuration management, computer resource management, and govern software installation and upgrade.	Field
Field System Monitoring and Diagnostics	'Field System Monitoring and Diagnostics' includes background self-tests, diagnostics, watchdog timers, and other hardware and software that monitors the operating condition of field equipment. The status of the equipment and diagnostic information is provided to local maintenance personnel and the operating center.	Field
FME On-Site Maintenance	'FME On-Site Maintenance' provides field personnel with diagnostic information from field equipment and provides the capability for field personnel to locally control and configure this equipment to support on-site installation, repair, and maintenance.	Field Maintenance Equipment
MCM Field Equipment Maintenance	'MCM Field Equipment Maintenance' provides overall management and support for maintenance of field equipment on a roadway system, right-of-way, parking area, transit stop, or other areas where field equipment exists. Services include repair and maintenance of ITS field equipment in these areas (e.g., detectors and other sensors, cameras, dynamic message signs, electronic toll collection equipment, electronic clearance equipment, weigh-in-motion sensors, etc.).	Maint and Constr Management Center
SM Device Management	'SM Device Management' provides the functions necessary to manage devices, including network management, operational status monitoring, and application performance monitoring.	Service Monitor System

Includes Information Flows:

Information Flow	Description
center operator data	Data presented to a center operator. This flow represents general status output and other data that broadly applies to transportation centers.
center operator input	Input from a center operator. This flow represents operator input that broadly applies to transportation centers.
equipment maintenance request	Identification of field equipment requiring repair and known information about the associated faults.
equipment maintenance status	Current status of field equipment maintenance actions.
field equipment commands	System-level control commands issued to field equipment such as reset and remote diagnostics.
field equipment configuration settings	Control settings and parameters that are used to configure field equipment.
field equipment fault data	Field equipment fault information that can be used to identify field equipment that requires initialization, reconfiguration, repair or replacement. This flow identifies the device, the nature of the fault, and associated error codes and diagnostic data.
field equipment software install/upgrade	This flow supports installation and update of software residing in ITS roadway equipment. It supports download of the software installation files, including executable code and associated support files.
field equipment status	Reports from field equipment (sensors, signals, signs, controllers, etc.) which indicate current operational status.
field equipment status presentation	Presentation of operational status of field equipment (sensors, signals, signs, controllers, etc.) to field personnel.
field personnel equipment input	User input from field personnel that supports querying, controlling, and configuring field equipment.
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.

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
Center
Field
Field Maintenance Equipment
Maint and Constr Management Center
Service Monitor System

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
Center	Center Personnel	center operator data	High	High	High
Center	Center Personnel	center operator data	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 center is not directly in front of the Center 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.
Center	Field	field equipment commands	Low	Moderate	Moderate
Center	Field	field equipment commands	Commands could be sensitive, however this flow is local, meaning the Field Support Equipment is proximate to the ITS Roadway Equipment. Thus the risk of interception should be low. There may also be constraints on this flow that require this information to be transmitted in the clear.	Commands to Field Equipment must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	The ability to remotely diagnose and configure devices is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact.
Center	Field	field equipment configuration settings	Moderate	Moderate	Moderate
Center	Field	field equipment configuration settings	Commands could be sensitive; monitoring of center-based control could enable an attacker's situational awareness, thus should be MODERATE.	Commands to Field Equipment must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	The ability to remotely diagnose and configure devices is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact.
Center	Field	field equipment software install/upgrade	Moderate	High	Moderate
Center	Field	field equipment software install/upgrade	Field equipment software could be sensitive, both from a vulnerability assessment standpoint and because the software itself may be competition-sensitive.	Software updates to Roadway Equipment must be authenticated as having come from a source entitled to provide that software, or roadway equipment may be comprimised. Similarly, such software must be guaranteed to being the intent of the originator; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	The ability to remotely update and configure devices is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact.
Center	Maint and Constr Management Center	equipment maintenance request	Moderate	Moderate	Moderate
Center	Maint and Constr Management Center	equipment maintenance request	Device operational status information should be known only by those entities that need to know for operations and maintenance. Allowing others to read this information may enable abuse of those systems, 3rd party monitoring of system status when that may not be desireable, and reverse engineering of this and similar information flows.	If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime.	If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime.
Center Personnel	Center	center operator input	High	High	High
Center Personnel	Center	center operator 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 center is not directly in front of the Center 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.
Field	Center	field equipment status	Moderate	Moderate	Moderate
Field	Center	field equipment status	The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW.	If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status.	This must be timely to support operational uptime requirements. Lack of monitoring will lead to less uptime, which will impact security, mobility and in some cases, safety.
Field	Field Maintenance Equipment	field equipment status	Low	Moderate	High
Field	Field Maintenance Equipment	field equipment status	The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW.	If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status.	This must be timely to support operational uptime requirements. Lack of monitoring will lead to less uptime, which will impact security, mobility and in some cases, safety.
Field	Field System Operator	field equipment status presentation	Moderate	High	High
Field	Field System Operator	field equipment status presentation	System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment	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.
Field	Maint and Constr Field Personnel	field equipment status presentation	Moderate	High	High
Field	Maint and Constr Field Personnel	field equipment status presentation	System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment	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.
Field	Maint and Constr Management Center	field equipment status	Moderate	Moderate	Moderate
Field	Maint and Constr Management Center	field equipment status	The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW.	If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status.	This must be timely to support operational uptime requirements. Lack of monitoring will lead to less uptime, which will impact security, mobility and in some cases, safety.
Field	Service Monitor System	field equipment status	Moderate	Moderate	Moderate
Field	Service Monitor System	field equipment status	The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW.	If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status.	This must be timely to support operational uptime requirements. Lack of monitoring will lead to less uptime, which will impact security, mobility and in some cases, safety.
Field Maintenance Equipment	Field	field equipment commands	Low	Moderate	High
Field Maintenance Equipment	Field	field equipment commands	Commands could be sensitive, however this flow is local, meaning the Field Support Equipment is proximate to the ITS Roadway Equipment. Thus the risk of interception should be low. There may also be constraints on this flow that require this information to be transmitted in the clear.	Commands to ITS Roadway Equipment must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	Without the ability to locally diagnose, operate, update and configure ITS Roadway Equipment, the equipment is effectively out of control and would have to be taken out of service.
Field Maintenance Equipment	Field	field equipment configuration settings	Moderate	Moderate	Moderate
Field Maintenance Equipment	Field	field equipment configuration settings	Configuration settings could be sensitive; if an attacker knows precisely how a device is configured, it may facilitate an attack.	Commands to ITS Roadway Equipment must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	The ability to remotely diagnose and configure devices is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact.
Field Maintenance Equipment	Field	field equipment software install/upgrade	Moderate	High	High
Field Maintenance Equipment	Field	field equipment software install/upgrade	Field equipment software could be sensitive, both from a vulnerability assessment standpoint and because the software itself may be competition-sensitive.	Software updates to Roadway Equipment must be authenticated as having come from a source entitled to provide that software, or roadway equipment may be comprimised. Similarly, such software must be guaranteed to being the intent of the originator; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised.	Without the ability to locally diagnose, operate, update and configure ITS Roadway Equipment, the equipment is effectively out of control and would have to be taken out of service.
Field Maintenance Equipment	Maint and Constr Field Personnel	field equipment status presentation	Moderate	High	High
Field Maintenance Equipment	Maint and Constr Field Personnel	field equipment status presentation	System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment	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.
Field System Operator	Field	field personnel equipment input	Moderate	Moderate	High
Field System Operator	Field	field personnel equipment input	Field subsystem controls should not be casually viewable as they their observation could serve as ad-hoc training for would-be attackers, not to mention that this interface is likely to include an authentication/authorization mechanism such as a password that if compromised, could compromise the device.	Since any direct interaction with field infrastructure will impact control, configuration and certainly operations of the device, there must be some assurance that such commands are correct.	Without direct local control the device is effectively uncontrolled.
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	Field	field personnel equipment input	Moderate	High	High
Maint and Constr Field Personnel	Field	field personnel equipment input	Field subsystem controls should not be casually viewable as they their observation could serve as ad-hoc training for would-be attackers, not to mention that this interface is likely to include an authentication/authorization mechanism such as a password that if compromised, could compromise the device.	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 Field Personnel	Field Maintenance Equipment	field personnel equipment input	Moderate	High	High
Maint and Constr Field Personnel	Field Maintenance Equipment	field personnel equipment input	Field subsystem controls should not be casually viewable as they their observation could serve as ad-hoc training for would-be attackers, not to mention that this interface is likely to include an authentication/authorization mechanism such as a password that if compromised, could compromise the device.	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 Management Center	Center	equipment maintenance status	Moderate	Moderate	Moderate
Maint and Constr Management Center	Center	equipment maintenance status	Data is not overly sensitive, but is a bulk statement about the status of all field equipment managed by the maintenance center. A hostile actor could use this information in the commission of a crime, for instance by understanding which cameras were not working and thus what areas are not under surveillance.	Center-based data exchanges are expected to be correct, and deserving of at leas some error checking. If this data is corrupted, the receiving center will be misinformed as to the state of field equipment maintenance.	Depends on the update frequency required. Possibly LOW, depending on the amount of equipment and what this flow is used for at the terminus.
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.
Service Monitor System	Center	field equipment fault data	Moderate	Moderate	Moderate
Service Monitor System	Center	field equipment fault data	Device status information should not be viewable by third parties, as those with criminal intent may use this information toward their own ends.	If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status. Scope is small, but impact significant if this occurs with many instances.	A delay in reporting this may cause a delay in necessary maintenance. Considered higher availability requirement than the source flow (RSE status) because this information aggregates many instances of the source.

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