• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

System Monitoring

The System Monitoring application provides 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.

• Enterprise
• Functional
• Physical
• A-Interconnect
• Communications
• Requirements
• Sources
• Security

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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

Hide Legend

Business Interaction Matrix:

System Monitoring Operations Stage
	Vehicle Owner	Vehicle OBE Owner	RSE Owner	Traveler	Center Owner	Data Distribution System Owner	Service Monitor System Operator	Network Manager	WAIDS Manager
Vehicle Owner		Vehicle OBE Usage Agreement
Vehicle OBE Owner	Vehicle OBE Usage Agreement							System Monitoring Agreement
RSE Owner								System Monitoring Agreement
Traveler								System Monitoring Agreement
Center Owner								System Monitoring Agreement
Data Distribution System Owner								System Monitoring Agreement
Service Monitor System Operator								Employment Agreement
Network Manager		System Monitoring Agreement	System Monitoring Agreement	System Monitoring Agreement	System Monitoring Agreement	System Monitoring Agreement	Employment Agreement		System Monitoring Agreement
WAIDS Manager								System Monitoring Agreement

Includes Enterprise Objects:

Enterprise Object	Description
Center Owner	General representation of the owner of the general "Center" physical object.
Data Distribution System Owner	The enterprise charged with providing data distribution services in the connected vehicle environment. This enterprise serves as broker between information and data providers and consumers.
Network Manager	The "Network Manager" represents the entity responsible for operating and maintaining the connected vehicle infrastructure including RSE and DDS, charged with monitoring its operational status and responding to operational issues related to monitored applications.
RSE Owner	The owner of roadside equipment.
Service Monitor System Operator	The 'Service Monitor System Operator' represents the person or people that monitor and manage the Service Monitor System.
Traveler	The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle OBE Owner	The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner	The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.
WAIDS Manager	The "WAIDS Manager" represents the entity responsible for operating and maintaining the Wide Area Information Disseminator, charged with monitoring its operational status and responding to operational issues related to it.

Includes Resources:

Resource	Description
Center	This general physical object is used to model core capabilities that are common to any center.
Center Support Services	'Center Support Services' provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.
Commercial Vehicle OBE	The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles.
Data Distribution System	The 'Data Distribution System' collects, processes, and distributes connected vehicle data, connecting data producers with data consumers and facilitating data exchange in the Connected Vehicle Environment.
DDS Support Services	"DDS Support Services" provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment. It also provides an overall service monitoring function.
Emergency Vehicle OBE	The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
Maint and Constr Vehicle OBE	The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment and supervisory vehicles. The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself and include sensors that monitor environmental conditions such as road condition and surface weather information. This can include a diverse set of mobile environmental sensing platforms, including wheeled vehicles and any other vehicle that collects and reports environmental information. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general applications with applications that are specific to maintenance and construction vehicles.
Personal Information Device	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Personal Support Services	'Personal Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.
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 Support Services	'RSE Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.
Service Monitor System	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.
SM Device Management	'SM Device Management' provides the functions necessary to manage devices, including network management, operational status monitoring, and application performance monitoring.
Transit Vehicle OBE	The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Vehicle	The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types.
Vehicle OBE	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Vehicle Support Services	'Vehicle Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to acquire necessary communications information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.
WAID Support Services	"WAID Support Services" provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment. It also provides an overall service monitoring function.
Wide Area Information Disseminator	The 'Wide Area Information Disseminator' represents the Connected Vehicle center based systems and communications equipment that is used to send messages to equipped vehicles using wide-area wireless communications such as satellite radio, terrestrial FM broadcast subcarrier, or cellular data networks.

Includes Roles:

Role	Description
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
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.
Includes	Includes	Indicates that one component is entirely contained within another component.
System Monitoring Agreement	Agreement	An agreement in which a connected vehicle device owner grants permission for another entity to remotely monitor the status of applications and services operating on that device.
Vehicle OBE Usage Agreement	Agreement	An agreement that grants one entity permission to use a Vehicle OBE that the other party controls.

Functional

Includes Processes:

Level	Name	Type	Allocated to Application Object
6	Provide Driver and Traveler Services	Collection
6.11.2	Manage Dissemination of Traveler Information	Pspec
10.1.5.2	Support Connected Vehicle Field Communications	Pspec	- RSE Support Services
10.1.5.3	Support Connected Vehicle Vehicle Communications	Pspec	- Vehicle Support Services
10.1.5.4	Support Connected Vehicle Mobile Communications	Pspec	- Personal Support Services
10.4.2	Manage Connected Vehicle Applications	Pspec
10.4.7	Provide Support Services Operator Interface	Pspec	- SM Device Management
10.4.8	Monitor System Activities	Pspec	- SM Device Management
10.6.4	Support Data Distribution Services	Pspec	- DDS Support Services

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Manage Connected Vehicle Applications	center_system_monitoring_data	Monitor System Activities
Manage Dissemination of Traveler Information	wide_area_dissemination_system_monitoring_data	Monitor System Activities
Monitor System Activities	system_monitoring_data_for_display	Provide Support Services Operator Interface
Provide Support Services Operator Interface	system_monitoring_configuration_data	Monitor System Activities
Support Connected Vehicle Field Communications	roadside_system_monitoring_data	Monitor System Activities
Support Connected Vehicle Field Communications	roadside_personal_connected_vehicle_data	Support Connected Vehicle Mobile Communications
Support Connected Vehicle Field Communications	roadside_vehicle_connected_vehicle_data	Support Connected Vehicle Vehicle Communications
Support Connected Vehicle Mobile Communications	mobile_system_monitoring_data	Monitor System Activities
Support Connected Vehicle Mobile Communications	personal_roadside_connected_vehicle_data	Support Connected Vehicle Field Communications
Support Connected Vehicle Mobile Communications	personal_vehicle_connected_vehicle_data	Support Connected Vehicle Vehicle Communications
Support Connected Vehicle Mobile Communications	personal_vehicle_connected_vehicle_data	Support Connected Vehicle Vehicle Communications
Support Connected Vehicle Vehicle Communications	vehicle_system_monitoring_data	Monitor System Activities
Support Connected Vehicle Vehicle Communications	vehicle_roadside_connected_vehicle_data	Support Connected Vehicle Field Communications
Support Connected Vehicle Vehicle Communications	vehicle_personal_connected_vehicle_data	Support Connected Vehicle Mobile Communications
Support Data Distribution Services	data_distribution_system_monitoring_data	Monitor System Activities

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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

Hide Legend

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.
Data Distribution System	Support	The 'Data Distribution System' collects, processes, and distributes connected vehicle data, connecting data producers with data consumers and facilitating data exchange in the Connected Vehicle Environment.
Personal Information Device	Traveler	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
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.
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.
Service Monitor System Operator	Support	The 'Service Monitor System Operator' represents the person or people that monitor and manage the Service Monitor System.
Vehicle OBE	Vehicle	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Wide Area Information Disseminator	Support	The 'Wide Area Information Disseminator' represents the Connected Vehicle center based systems and communications equipment that is used to send messages to equipped vehicles using wide-area wireless communications such as satellite radio, terrestrial FM broadcast subcarrier, or cellular data networks.

Includes Application Objects:

Application Object	Description	Physical Object
Center Support Services	'Center Support Services' provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.	Center
DDS Support Services	"DDS Support Services" provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment. It also provides an overall service monitoring function.	Data Distribution System
Personal Support Services	'Personal Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.	Personal Information Device
RSE Support Services	'RSE Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.	Roadside Equipment
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
Vehicle Support Services	'Vehicle Support Services' provides foundational functions that supports data collection, management, and distribution. It coordinates with Object Registration and Discovery to acquire necessary communications information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment.	Vehicle OBE
WAID Support Services	"WAID Support Services" provides foundational functions that support data collection, management, and distribution. It coordinates with Object Registration and Discovery to maintain its registration with respect to location/geographic scope and credentialing information. It maintains the necessary security credentials, authorizations, and associated keys to support communications in the connected vehicle environment. It also provides an overall service monitoring function.	Wide Area Information Disseminator

Includes Information Flows:

Information Flow	Description
service monitor information presentation	Presentation of information to the System Monitoring Operator including current operational status of the System Monitoring function and the connected vehicle environment that is monitored.
service monitor operator input	User input from the SMS operator including requests to monitor current system operation and inputs to affect system operation.
system monitoring	Represents the interactive monitoring of system operations by the Service Monitor. It includes device housekeeping/heartbeat monitoring and network monitoring information, the status of installed applications, and the configuration of managed devices.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
	Center	Service Monitor System	system monitoring
	Data Distribution System	Service Monitor System	system monitoring
	Personal Information Device	Service Monitor System	system monitoring
	Roadside Equipment	Service Monitor System	system monitoring
None: Human interface	Service Monitor System	Service Monitor System Operator	service monitor information presentation
None: Human interface	Service Monitor System Operator	Service Monitor System	service monitor operator input
	Vehicle OBE	Service Monitor System	system monitoring
	Wide Area Information Disseminator	Service Monitor System	system monitoring

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.060	System Monitoring (SM) needs to track and manage the configuration of infrastructure-based System Elements, which includes the RSE as well as the communication link to back office functions.	4.136	System Monitoring shall be capable of determining the configuration of infrastructure-based System Elements, which includes the RSE as well as the communication link to back office functions.
		4.137	System Monitoring shall be capable of changing the configuration settings of infrastructure-based System Elements, which includes the RSE as well as the communication link to back office functions.
N4.061	SM needs to detect, isolate and correct infrastructure service problems of infrastructure-based System Elements.	4.138	SM shall be capable of determining the status of infrastructure-based System Elements.
		4.139	SM shall be capable of remotely correcting faults or service problems in the infrastructure-based System Elements.
N4.062	SM needs to monitor the performance of infrastructure-based System Elements.	4.140	SM shall be capable of monitoring the performance of the infrastructure-based System Elements.
N4.063	SM needs to monitor the physical and cyber security of infrastructure-based System Elements.	4.141	SM shall monitor the physical security of infrastructure-based System Elements.
		4.142	SM shall monitor the information systems of infrastructure-based System Elements.
N4.065	SM needs to have sufficient internal operations and diagnostic message generation and logging capabilities to allow for operational monitoring, troubleshooting, and control.	4.143	SM shall support message generation and logging capabilities.
N4.066	SM needs to provide accurate status information to System Users and notify operations personnel when a service operates in abnormal or degraded fashion.	4.144	SM shall provide status information to operations personnel.
		4.145	SM shall notify operations personnel when a service operates in abnormal or degraded fashion.

Related Sources

• Core System Concept of Operations (ConOps), Final revE, 10/24/2011
• Core System System Architecture Document (SAD), Final revC, 10/14/2011
• 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.