Type: Support
Groups:- Core Services
Infrastructure Management
Infrastructure management is a support application that maintains and monitors the performance and configuration of the infrastructure portion of connected vehicle. This includes tracking and management of the infrastructure configuration as well as detection, isolation, and correction of infrastructure service problems. The application also includes monitoring of performance of the infrastructure equipment, which includes the RSE as well as the communication link to back office functions.
Enterprise
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification
Business Interaction Matrix:
Infrastructure Management Operations Stage | |||||||
---|---|---|---|---|---|---|---|
RSE Owner | Maint and Constr Field Personnel | Maint and Constr Manager | Center Owner | Center Connected Vehicle Infrastructure Management Provider | RSE Device Management Provider | Field Support Provider | |
RSE Owner | Information Exchange and Action Agreement | Application Usage Agreement | |||||
Maint and Constr Field Personnel | Employment Agreement | ||||||
Maint and Constr Manager | Information Exchange and Action Agreement | Employment Agreement | Information Exchange and Action Agreement | Application Usage Agreement | |||
Center Owner | Information Exchange and Action Agreement | Application Usage Agreement | |||||
Center Connected Vehicle Infrastructure Management Provider | Application Usage Agreement | ||||||
RSE Device Management Provider | Application Usage Agreement | ||||||
Field Support Provider | Application Usage Agreement |
Includes Enterprise Objects:
Enterprise Object | Description |
---|---|
Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
Center Connected Vehicle Infrastructure Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Center Connected Vehicle Infrastructure Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Center Connected Vehicle Infrastructure Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Center Owner | General representation of the owner of the general "Center" physical object. |
Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
Field Support Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Field Support Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Field Support Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Maint and Constr Field Personnel | 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 Manager | The organization responsible for maintenance and construction activities. |
MCM Roadway Maintenance Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Roadway Maintenance Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
MCM Roadway Maintenance Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Roadway Owner | The owner of the roadway proximate to which roadside equipment will be/is installed. |
RSE Deployer | The entity responsible for the deployment, operations and maintenance of roadside equipment. |
RSE Device Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
RSE Device Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
RSE Device Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
RSE Owner | The owner of roadside equipment. |
RSE Provider | The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research. |
State Regulatory | State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies. |
Includes Resources:
Resource | Description |
---|---|
Alternate Mode Transportation Center | The 'Alternate Mode Transportation Center' provides the interface through which non-ITS transportation systems (e.g., airlines, ferry services, passenger-carrying heavy rail) can exchange data with ITS.. This two-way interface enables coordination for efficient movement of people across multiple transportation modes. It also enables the traveler to efficiently plan itineraries which include segments using other modes. |
Application Component Certification Requirements | The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE. |
Backoffice Service Development System | The systems used to develop backoffice (center) hardware and software components of applications. |
Backoffice Service Installation System | The systems used to install and configure backoffice (center) hardware and software components. |
Backoffice Service Maintenance System | The systems used to maintain and upgrade backoffice (center) hardware and software components. |
Center | This general physical object is used to model core capabilities that are common to any center. |
Center Connected Vehicle Infrastructure Management | "Center Connected Vehicle Infrastructure Management" is the back office application that supports monitoring and maintenance of the Connected Vehicle infrastructure (RSEs, support systems, and associated communications links). It monitors the performance and configuration of the infrastructure portion of the Connected Vehicle Environment. This includes tracking and management of the infrastructure configuration as well as detection, isolation, and correction of infrastructure service problems. The application also includes monitoring of performance of the infrastructure equipment, including RSEs and communications links. |
Device Certification Requirements | The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment. |
Emissions Management Center | The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment in CVRIA) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications. |
Field Component Development System | The system used in a backoffice environment to develop and test the field component of the application. |
Field Component Installation System | The system used to install a field component of a connected vehicle application. |
Field Component Maintenance System | The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
Field Support | "Field Support" 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 Support Equipment | 'Field Support 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. |
Fleet and Freight Management Center | The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. |
Maint and Constr Management Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
MCM Roadway Maintenance | "MCM Roadway Maintenance" provides overall management and support for routine maintenance on a roadway system or right-of-way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. |
Roadside Equipment | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
RSE Development System | The system used in a backoffice environment to develop and test the roadside equipment. |
RSE Device Management | "RSE Device Management" provides executive control and monitoring of the RSE hardware and installed software applications. It monitors the operational status of the hardware and other attached field devices and detects and reports fault conditions. A back office interface supports application installation, upgrade, and configuration as well as remote control of the operating mode and hardware configuration settings and initiation of remote diagnostics. A local interface is provided to field personnel for local monitoring and diagnostics, supporting field maintenance, repair, and replacement. |
RSE Installation System | The system used to install and configure the roadside equipment. |
RSE Maintenance System | The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance. |
Traffic Management Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Transit Management Center | The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems. |
Transportation Information Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
Includes Roles:
Role | Description |
---|---|
Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
Member | An Enterprise is part of another larger, target Enterprise. |
Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
Coordination | Type | Description |
---|---|---|
Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
Application Interface Specification | Agreement | The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
Application Usage Agreement | Agreement | An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
Backoffice Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Device Placement and Operations Agreement | Agreement | An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity. |
Employment Agreement | Agreement | An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance. |
Extends | Includes | Indicates that one component includes all of the functionality of another component, and in provides additional functionality beyond that other component's. |
Field Component Installation Agreement | Agreement | An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party. |
Field Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Includes | Includes | Indicates that one component is entirely contained within another component. |
Information Exchange and Action Agreement | Agreement | An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
RSE Deployment Agreement | Agreement | Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions. |
RSE Installation Data | Information Sharing | Data necessary to configure and make RSE operational. Uni-directional. |
RSE Maintenance Data | Information Sharing | Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional. |
RSE Performance Data | Information Sharing | Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures. |
RSE Procurement Agreement | Agreement | An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process. |
Warranty | Agreement | A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component. |
Functional
Includes Processes:
Level | Name | Type | Allocated to Application Object |
---|---|---|---|
9.2 | Manage Roadway M&C Activities | Collection | |
9.2.2 | Status Current M&C Activities and Transportation Infrastructure | Pspec |
- MCM Roadway Maintenance |
9.2.3 | Determine M&C Needs | Collection | |
9.2.3.2 | Determine Roadway M&C Needs | Pspec |
- MCM Roadway Maintenance |
9.2.3.5 | Collect Roadside Equipment Status | Pspec |
- MCM Roadway Maintenance |
9.2.3.8 | Collect Connected Vehicle Field Equipment Status | Pspec |
- RSE Device Management |
10.4.1 | Monitor Roadside Equipment Fault Data | Pspec |
- Center Connected Vehicle Infrastructure Management |
10.4.2 | Manage Connected Vehicle Applications | Pspec |
- Center Connected Vehicle Infrastructure Management |
10.4.3 | Manage Connected Vehicle Field Applications | Pspec |
- RSE Device Management |
10.4.4 | Control Roadside Equipment | Pspec |
- RSE Device Management |
10.4.5 | Provide Field Equipment Maintenance | Pspec |
- Field Support |
Includes Data Flows:
Physical
SVG Diagram
PNG Diagram
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. |
Field Support Equipment | Field | 'Field Support 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. |
Maint and Constr Field Personnel | Vehicle | 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. |
Roadside Equipment | Field | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
Includes Application Objects:
Application Object | Description | Physical Object |
---|---|---|
Center Connected Vehicle Infrastructure Management | "Center Connected Vehicle Infrastructure Management" is the back office application that supports monitoring and maintenance of the Connected Vehicle infrastructure (RSEs, support systems, and associated communications links). It monitors the performance and configuration of the infrastructure portion of the Connected Vehicle Environment. This includes tracking and management of the infrastructure configuration as well as detection, isolation, and correction of infrastructure service problems. The application also includes monitoring of performance of the infrastructure equipment, including RSEs and communications links. | Center |
Field Support | "Field Support" 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 Support Equipment |
MCM Roadway Maintenance | "MCM Roadway Maintenance" provides overall management and support for routine maintenance on a roadway system or right-of-way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g., signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. | Maint and Constr Management Center |
RSE Device Management | "RSE Device Management" provides executive control and monitoring of the RSE hardware and installed software applications. It monitors the operational status of the hardware and other attached field devices and detects and reports fault conditions. A back office interface supports application installation, upgrade, and configuration as well as remote control of the operating mode and hardware configuration settings and initiation of remote diagnostics. A local interface is provided to field personnel for local monitoring and diagnostics, supporting field maintenance, repair, and replacement. | Roadside Equipment |
Includes Information Flows:
Information Flow | Description |
---|---|
application install/upgrade | This flow supports remote installation and update of software applications residing in the RSE. It supports transmission of the secure software installation files, including executable application code and associated support files. |
equipment configuration settings | Control settings and parameters that are used to configure roadside equipment. |
equipment control commands | Equipment control commands such as application reset, remote diagnostics… |
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. |
equipment status | Status reported by the RSE identifying current mode, operational status, and configuration settings. |
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. |
Application Interconnect Diagram
SVG Diagram
PNG Diagram
Application Triples
Requirements
Need | Requirement | ||
---|---|---|---|
N4.001 | Applications need to protect data they handle from unauthorized access. This is required to support applications that exchange sensitive information, such as personally identifying or financial information, which if intercepted could compromise the privacy or financial records of the user. | 4.001 | Applications that function by exchanging data between entities shall be able to exchange encrypted data between those entities. |
N4.002 | Applications need to establish trust between entities that operate components of the application. Such trust relationships are necessary so that applications can be assured that entities are who they say they are, and therefore trust the source and data it receives. | 4.002 | Applications shall verify that, for each entity on which an application component is installed, that entity is trusted by the provider of the application. |
4.003 | Applications shall be able to digitally sign all messages sent between entities. | ||
4.004 | Applications shall be able to verify the digital signature of received messages. | ||
4.005 | Digital signatures used to ensure trust shall be generated independently of the application sending the message to be signed. | ||
N4.003 | Applications need to revoke the trust relationship they have between entities when necessary. A trusted entity may operate in a fashion that indicates it should no longer be trusted, in which case applications must have a way of revoking that trust. | 4.006 | Applications shall identify entities that provide messages to the application that are improperly formatted. |
4.007 | Applications shall identify entities that provide messages to the application that are logically inconsistent. | ||
4.008 | Applications shall revoke personal trust (trust by the application) when a repeated pattern of messages from a given entity falls outside of the applications tolerances. | ||
4.009 | Applications shall be able to report suspicious behavior to third party authentication providers. | ||
4.010 | Applications shall be able to accept messages from the third party authentication provider that identifies entities unworthy of trust. | ||
4.011 | Applications shall be able to revoke trust between itself and an entity if that entity is identified by the third party authentication provider as untrustworthy. | ||
N4.004 | All participants in the Connected Vehicle Environment need to operate on a common time base. Coordination of time between the entities that operate applications as well as those providing Core services prevents internal errors and enables time-sensitive interactions between application components. | 4.012 | All applications shall use the same time source as the basis for timing. |
N4.048 | Infrastructure management needs to track and manage of the configuration of infrastructure equipment. | 4.116 | Infrastructure management shall be capable of determining the configuration of infrastructure equipment. |
4.117 | Infrastructure management shall be capable of changing the configuration settings of infrastructure equipment | ||
N4.049 | Infrastructure management needs to detect, isolate and correct infrastructure service problems. | 4.118 | Infrastructure management shall be capable of determining the status of infrastructure equipment. Needs to detect, isolate and correct infrastructure service problems. |
4.119 | Infrastructure management shall be capable of detecting and isolating infrastructure equipment faults or service problems. | ||
4.120 | Infrastructure management shall be capable of remotely correcting faults or service problems in the infrastructure equipment | ||
N4.050 | Infrastructure management needs to monitor the performance of the infrastructure equipment, which includes the RSE as well as the communication link to back office functions. | 4.121 | Infrastructure management shall be capable of monitoring the performance of the infrastructure equipment. |
Related Sources
- Southeast Michigan Test Bed 2014 Concept of Operation, Draft, 12/29/2014
Security
In order to participate in this application, each physical object should meet or exceed the following security levels.
Physical Object Security | ||||
---|---|---|---|---|
Physical Object | Confidentiality | Integrity | Availability | Security Class |
Security levels have not been defined yet. |
In order to participate in this application, each information flow triple should meet or exceed the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
Basis | Basis | Basis | |||
Security levels have not been defined yet. |