< < DM01 : DM02 : MC01 > >

DM02: Performance Monitoring

The Performance Monitoring service package uses information collected from detectors and sensors, connected vehicles, and operational data feeds from centers to support performance monitoring and other uses of historical data including transportation planning, condition monitoring, safety analyses, and research. The information may be probe data information obtained from vehicles in the network to determine network performance measures such as speed and travel times, or it may be information collected from the vehicles and processed by the infrastructure, e.g. environmental data and infrastructure conditions monitoring data. Additional data are collected including accident data, road condition data, road closures and other operational decisions to provide context for measured transportation performance and additional safety and mobility-related measures. More complex performance measures may be derived from the collected data.

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

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

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Archived Data System Developer	Archived Data 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.
Archived Data System Developer	Archived Data User 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.
Archived Data System Developer	Government Reporting Systems 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.
Archived Data System Developer	Other Archived Data Systems 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.
Archived Data User System Developer	Archived Data 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.
Archived Data User System Developer	Archived Data User 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.
Government Reporting Systems Developer	Archived Data 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.
Government Reporting Systems Developer	Government Reporting Systems	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.
Other Archived Data Systems Developer	Archived Data 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.
Other Archived Data Systems Developer	Other Archived Data Systems	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
Archived Data System Installer	Archived Data 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.
Archived Data System Owner	Archived Data System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Archived Data System Owner	Archived Data 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.
Archived Data User System Installer	Archived Data User 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.
Archived Data User System Owner	Archived Data User System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Archived Data User System Owner	Archived Data User 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.
Government Reporting Systems Installer	Government Reporting Systems	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.
Government Reporting Systems Owner	Government Reporting Systems Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Government Reporting Systems Owner	Government Reporting Systems 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.
Other Archived Data Systems Installer	Other Archived Data Systems	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.
Other Archived Data Systems Owner	Other Archived Data Systems Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Archived Data Systems Owner	Other Archived Data Systems 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
Archived Data Administrator	Archived Data 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.
Archived Data System Maintainer	Archived Data 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.
Archived Data System Manager	Archived Data Administrator	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.
Archived Data System Manager	Archived Data 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.
Archived Data System Owner	Archived Data 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.
Archived Data System Owner	Archived Data 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.
Archived Data System Owner	Archived Data User 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.
Archived Data System Owner	Archived Data User System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Archived Data System Owner	Archived Data User 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.
Archived Data System Owner	Government Reporting Systems 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.
Archived Data System Owner	Government Reporting Systems Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Archived Data System Owner	Government Reporting Systems User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Archived Data System Owner	Other Archived Data Systems 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.
Archived Data System Owner	Other Archived Data Systems 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.
Archived Data System Owner	Other Archived Data Systems User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Archived Data System Supplier	Archived Data 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.
Archived Data User System Maintainer	Archived Data User 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.
Archived Data User System Manager	Archived Data User 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.
Archived Data User System Owner	Archived Data Administrator	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.
Archived Data User System Owner	Archived Data 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.
Archived Data User System Owner	Archived Data System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Archived Data User System Owner	Archived Data 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.
Archived Data User System Owner	Archived Data User 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.
Archived Data User System Owner	Archived Data User 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.
Archived Data User System Supplier	Archived Data User 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.
Government Reporting Systems Maintainer	Government Reporting Systems	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.
Government Reporting Systems Manager	Government Reporting Systems	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.
Government Reporting Systems Owner	Archived Data Administrator	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.
Government Reporting Systems Owner	Archived Data 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.
Government Reporting Systems Owner	Archived Data System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Government Reporting Systems Owner	Archived Data 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.
Government Reporting Systems Owner	Government Reporting Systems 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.
Government Reporting Systems Owner	Government Reporting Systems Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Government Reporting Systems Supplier	Government Reporting Systems Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other Archived Data Systems Maintainer	Other Archived Data Systems	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.
Other Archived Data Systems Manager	Other Archived Data Systems	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.
Other Archived Data Systems Owner	Archived Data Administrator	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.
Other Archived Data Systems Owner	Archived Data 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.
Other Archived Data Systems Owner	Archived Data System Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Other Archived Data Systems Owner	Archived Data 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.
Other Archived Data Systems Owner	Other Archived Data Systems 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.
Other Archived Data Systems Owner	Other Archived Data Systems Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Archived Data Systems Supplier	Other Archived Data Systems 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
Archived Data System	Archive Data Repository	8.1	Get Archive Data
		8.2	Manage Archive
		8.3	Manage Archive Data Administrator Interface
		8.4	Coordinate Archives
		8.5	Process Archived Data User System Requests
		8.7	Process On Demand Archive Requests
	Archive Government Reporting	8.8	Prepare Government Reporting Inputs
	Archive On-Line Analysis and Mining	8.6	Analyze Archive
	Archive Situation Data Archival	8.1	Get Archive Data
	Archive Situation Data Archival	8.9	Manage Roadside Data Collection

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
Archived Data Administrator	Support	'Archived Data Administrator' represents the human operator who provides overall data management, administration, and monitoring duties for the ITS data archive. Unlike the manager of the operational databases, the archive data administrator's role is focused on the archive and covers areas such as establishing user authentication controls, monitoring data quality, and initiating data import requests.
Archived Data System	Support	The 'Archived Data System' collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. The data received is formatted and tagged with attributes that define the data source, conditions under which it was collected, data transformations, and other information (i.e. meta data) necessary to interpret the data. The archive can fuse ITS generated data with data from non-ITS sources and other archives to generate information products utilizing data from multiple functional areas, modes, and jurisdictions. The archive prepares data products that can serve as inputs to federal, state, and local data reporting systems. The 'Archived Data System' may reside within an operational center and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct center that collects data from multiple agencies and sources and provides a general data warehouse service.
Archived Data User System	Center	'Archived Data User System' represents the systems users employ to access archived data. The general interface provided allows a broad range of users (e.g. planners, researchers, analysts, operators) and their systems (e.g. databases, models, analytical tools, user interface devices) to acquire data and analyses results from the archive.
Government Reporting Systems	Center	'Government Reporting Systems' represents the system and associated personnel that prepare the inputs to support the various local, state, and federal government transportation data reporting requirements (e.g. Highway Performance Monitoring System, Fatality Analysis Reporting System) using data collected by ITS systems. It represents a system interface that provides access to the archived data relevant to these reports. In most cases, this system will combine data collected from ITS archives with data from non-ITS sources to assemble the required information.
Other Archived Data Systems	Support	'Other Archived Data Systems' represents distributed archived data systems whose data can be accessed and shared with a local archive. The interface with the Archived Data System allows data from multiple archives to be accessed on demand or imported and consolidated into a single repository.

Includes Functional Objects:

Functional Object	Description	Physical Object
Archive Data Repository	'Archive Data Repository' collects data and data catalogs from one or more data sources and stores the data in a focused repository that is suited to a particular set of ITS data users. It includes capabilities for performing quality checks on the incoming data, error notification, and archive to archive coordination. It includes the capability to define a data registry that allows registration of data identifiers or data definitions for interoperable use throughout a region. It supports a broad range of implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region. Repositories may be established to support operations planning, performance monitoring and management, and policy and investment decisions.	Archived Data System
Archive Government Reporting	'Archive Government Reporting' selects and formats data residing in an ITS archive to facilitate local, state, and federal government data reporting requirements. It provides transportation system statistics and performance measures in required formats to support investment and policy decisions.	Archived Data System
Archive On-Line Analysis and Mining	'Archive On-Line Analysis and Mining' provides advanced data analysis, summarization, and mining features that facilitate discovery of information, patterns, and correlations in large data sets. Multidimensional analysis, selective summarization and expansion of data details, and many other advanced analysis services may be offered. Complex performance measures that are derived from multiple data sources may also be produced.	Archived Data System
Archive Situation Data Archival	'Archive Situation Data Archival' collects and archives traffic, roadway, and environmental information for use in off-line planning, research, and analysis. It controls and collects information directly from equipment at the roadside, reflecting the deployment of traffic detectors that are used primarily for traffic monitoring and planning purposes, rather than for traffic management. It also collects situation data from connected vehicles. The data collected, quality checks performed, and aggregation strategies are defined to support transportation system performance monitoring and management.	Archived Data System

Includes Information Flows:

Information Flow	Description
archive analysis requests	A user request that initiates data mining, analytical processing, aggregation or summarization, report formulation, or other advanced processing and analysis of archived data. The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
archive analysis results	Processed information products, supporting meta data, and any associated transaction information resulting from data mining, analytical processing, aggregation or summarization, report formulation, or other on-line processing and analysis of archived data.
archive coordination	Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests.
archive management data	Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and any special requests that require direct action by the administrator (e.g., requests for access to new data sources).
archive management requests	User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive.
archive request confirmation	Confirmation that an archive request has been received and processed with information on the disposition of the request.
archived data product requests	A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
archived data products	Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
government reporting data receipt	The acknowledgement of satisfactory receipt of information used as input to government data systems or a report identifying problems or issues with the data submittal.
government reporting system data	Information provided by an ITS archive, formatted as appropriate, that can be used as input to government data reporting systems.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight;	Enhance integration and connectivity
G. Promote efficient system management and operation;	Improve efficiency
J. Enhance travel and tourism.	Support travel and tourism

Associated Objective Categories

Objective Category
Arterial Management: Traffic Monitoring and Data Collection
Integration: Transportation Data Collection
Traveler Information: Data Collection and Sharing on Travel Conditions

Associated Objectives and Performance Measures

Objective	Performance Measure
Enhance planning with better data	Amount of data gathered from ITS enhancements used in infrastructure and operations planning
Enhance planning with better data	Number of planning activities using data from ITS systems
Enhance planning with better data	Years of data in database that is easily searchable and extractable
Field data collection is conducted either through floating car studies or other methods at least once every Y years on major signalized arterials and X years on minor signalized arterials.	Number of field data collection studies performed every Y and X years on major and minor signalized arterials, respectively.
Increase the percent of modes in the region that share their traveler information with other modes in the region to 100 percent by Y year.	Percent of modes in the region that share their traveler information with other modes.
Increase the percent of the transportation system in which travel conditions can be detected remotely via CCTV, speed detectors, etc. to X percent by Y year.	Percent of the transportation system in which travel conditions can be detected remotely via CCTV, speed detectors, etc.
Increase the percent of transportation facilities whose owners share their traveler information with other agencies in the region to X percent by Y year.	Percent of transportation facilities whose owners share their traveler information with other agencies in the region.
X percent of intersections in the region are equipped and operating with traffic signals that enable real-time monitoring and management of traffic flows by year Y.	Percent of intersections in the region equipped and operating with traffic signals that enable real-time monitoring and management of traffic flows.
X percent of major and minor arterials are equipped and operating with arterial link traffic data detection stations (appropriate technology) per Z distance by year Y.	Percent of major and minor arterials equipped and operating with arterial link traffic data detection stations (appropriate technology) per Z distance.
X percent of major and minor arterials are equipped and operating with closed circuit television (CCTV) cameras per Z distance by year Y.	Percent of major and minor arterials equipped and operating with closed circuit television (CCTV) cameras per Z distance.

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need		Functional Object	Requirement
01	System operators need to be able to store vehicle data, transit data, weather data, freight data and other transportation-related data to support traffic data analysis, transportation network performance monitoring, transportation planning, safety analyses and research.	Archive Data Repository	06	The center shall include capabilities for archive to archive coordination.
		Archive Situation Data Archival	04	The center shall collect vehicle traffic probe data for performance monitoring and analysis.
		Archive Situation Data Archival	05	The center shall be capable of archiving vehicle traffic probe data.
02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.	Archive Government Reporting	01	The center shall provide archive data to federal, state, and local government reporting systems.
			02	The center shall respond to requests for government report data.
			03	The center shall provide the capability to format data suitable for input into government reports.
			04	The center shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
		Archive On-Line Analysis and Mining	02	The center shall provide the capability to perform activities such as data mining, data fusion, summarizations, aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and expansion of data details, and many other advanced analysis services.
			05	The center shall be capable of processing vehicle probe data into transportation network performance measures.
			06	The center shall be capable of processing vehicle probe data to support infrastructure conditions monitoring performed by Archived Data User Systems including maintenance and construction management centers.
			07	The center shall be capable of processing vehicle probe data to determine roadway environmental conditions for non operational uses such as maintenance planning and research.

Related Sources

Document Name	Version	Publication Date
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods		8/15/2014

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
Archived Data System	High	High	High	Class 5
Archived Data User System	High	High	Moderate	Class 4
Government Reporting Systems	Low	High	Low	Class 3
Other Archived Data Systems	Moderate	High	High	Class 5

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
Archived Data Administrator	Archived Data System	archive management requests	Moderate	Moderate	Moderate
Archived Data Administrator	Archived Data System	archive management requests	Human readable information intended for the administrator only. No PII, mostly performance data, but observation provides information that should not be viewable outside the operating agency. Compromise allows a third party to potentially manipulate the archive.	System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money.	System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money.
Archived Data System	Archived Data Administrator	archive management data	Moderate	Moderate	Moderate
Archived Data System	Archived Data Administrator	archive management data	Human readable information intended for the administrator only. No PII, mostly performance data, but observation provides information that should not be viewable outside the operating agency. Compromise allows a third party to potentially manipulate the archive.	System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money.	System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money.
Archived Data System	Archived Data User System	archive analysis results	High	High	Low
Archived Data System	Archived Data User System	archive analysis results	Data may include sensitive information which should not be casually viewable. As many requests could be quite large, the cost of compromise will be corresponding ly high.	Since the whole point of an archived data request is some sort of data analysis, the contents of that data must be intact or the effort is wasted. Such requests can be for very large data sets, the effective cost of which is high.	While the data sets are large, requests should be infrequent, and can be managed with interruptions in service.
Archived Data System	Archived Data User System	archive request confirmation	Low	Moderate	Moderate
Archived Data System	Archived Data User System	archive request confirmation	Status response should not have any sensitive information.	Response needs to be correct or the originator might choose an alternate mechanism or take other action to investigate.	Response needs to arrive or originator might take other action.
Archived Data System	Archived Data User System	archived data products	High	High	Low
Archived Data System	Archived Data User System	archived data products	Data may include sensitive information which should not be casually viewable. As many requests could be quite large, the cost of compromise will be corresponding ly high.	Since the whole point of an archived data request is some sort of data analysis, the contents of that data must be intact or the effort is wasted. Such requests can be for very large data sets, the effective cost of which is high.	While the data sets are large, requests should be infrequent, and can be managed with interruptions in service.
Archived Data System	Government Reporting Systems	government reporting system data	Low	High	Low
Archived Data System	Government Reporting Systems	government reporting system data	Data to be used as the basis for published reports probably does not need obfuscation. The cost of exposing this data is minimal, as it presumably should be publicly accessible through some means.	Given that the data will be used to produce public reports upon which policy may be enacted, its accuracy is critically important, as any misrepresentation could lead to public distrust or decisions based on incorrect data.	Should not often be sent, so intermittent connectivity should be sufficient.
Archived Data System	Other Archived Data Systems	archive coordination	Moderate	High	High
Archived Data System	Other Archived Data Systems	archive coordination	Archive coordination may involve substantial meta data that indicates how users are using archived data systems, and may include queries that betray intent. Observation of this information provides a third party with intelligence about system users that should not be observable.	Incorrect coordination could lead to substantial performance challenges for the archive systems, degrading overall performance which affects all users. Depending what the archive is used for, this might be reduced to MODERATE	Without this flow, archive usage that spans multiple systems will be impossible, making archive requests unusable. Depending on what the archive is used for, this might be reduced to MODERATE.
Archived Data User System	Archived Data System	archive analysis requests	Moderate	Moderate	Low
Archived Data User System	Archived Data System	archive analysis requests	User login information must be kept confidential. Depending on the sensitivity of the archive data and resulting utiltity of access, this may be HIGH.	An incorrect data request will be incovenient, resulting in error or useless responses, but not catastrophic.	Not a real time service, so intermittent availability should suffice.
Archived Data User System	Archived Data System	archived data product requests	Moderate	Moderate	Low
Archived Data User System	Archived Data System	archived data product requests	User login information must be kept confidential. Depending on the sensitivity of the archive data and resulting utiltity of access, this may be HIGH.	An incorrect data request will be incovenient, resulting in error or useless responses, but not catastrophic.	Not a real time service, so intermittent availability should suffice.
Government Reporting Systems	Archived Data System	government reporting data receipt	Low	High	Low
Government Reporting Systems	Archived Data System	government reporting data receipt	Data to be used as the basis for published reports probably does not need obfuscation. The cost of exposing this data is minimal, as it presumably should be publicly accessible through some means.	Integrity must be managed to the same degree as the originating data or the completion of data provision is in jeopardy. That has been assessed as HIGH, so this must be as well.	Intermittent in tandem with the data that prompts this response; needs to be equal to that flow.
Other Archived Data Systems	Archived Data System	archive coordination	Moderate	High	High
Other Archived Data Systems	Archived Data System	archive coordination	Archive coordination may involve substantial meta data that indicates how users are using archived data systems, and may include queries that betray intent. Observation of this information provides a third party with intelligence about system users that should not be observable.	Incorrect coordination could lead to substantial performance challenges for the archive systems, degrading overall performance which affects all users. Depending what the archive is used for, this might be reduced to MODERATE	Without this flow, archive usage that spans multiple systems will be impossible, making archive requests unusable. Depending on what the archive is used for, this might be reduced to MODERATE.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name	Title	Physical Object
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	Archived Data System

System Requirements

System Requirement		Need
001	The system shall include capabilities for archive to archive coordination.	01	System operators need to be able to store vehicle data, transit data, weather data, freight data and other transportation-related data to support traffic data analysis, transportation network performance monitoring, transportation planning, safety analyses and research.
002	The system shall provide archive data to federal, state, and local government reporting systems.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
003	The system shall respond to requests for government report data.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
004	The system shall provide the capability to format data suitable for input into government reports.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
005	The system shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection o	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
006	The system shall provide the capability to perform activities such as data mining, data fusion, summarizations, aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and expansion of data deta	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
007	The system shall process vehicle probe data into transportation network performance measures.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
008	The system shall process vehicle probe data to support infrastructure conditions monitoring performed by Archived Data User Systems including maintenance and construction management centers.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
009	The system shall process vehicle probe data to determine roadway environmental conditions for non operational uses such as maintenance planning and research.	02	System operators need to be able to process vehicle data sourced by themselves and other system operators to support performance monitoring, infrastructure conditions reporting, and environmental monitoring. This supports system operator reporting needs and provides the source data and metrics for government reports.
010	The system shall collect vehicle traffic probe data for performance monitoring and analysis.	01	System operators need to be able to store vehicle data, transit data, weather data, freight data and other transportation-related data to support traffic data analysis, transportation network performance monitoring, transportation planning, safety analyses and research.
011	The system shall archive vehicle traffic probe data.	01	System operators need to be able to store vehicle data, transit data, weather data, freight data and other transportation-related data to support traffic data analysis, transportation network performance monitoring, transportation planning, safety analyses and research.

Implementations

DM02.1 Automated Traffic Signal Performance Measures (ATSPM)

Display: Implementation legend or Service Package legend

DM02.1 Automated Traffic Signal Performance Measures (ATSPM) Implementation

Share current traffic data and traffic control system status for signalized intersections, providing query-based reporting for a range of traffic signal performance metrics for a range of selected locations and timeframes. See also the DM01 'Traffic Data Mart' implementation for the associated traffic data collection implementation that collects the data that is reported by this implementation. Together, the DM01 and DM02 implementations for ATSPM cover a complete ATSPM application that includes raw data collection through query-based distribution of filtered results to end users. (Note this implementation includes the entire SP and practically speaking, would allow someone searching ATSPM on our site or in the tools to find SP implementations for DM01 and DM02. This could be done instead of, or in addition to, our traditional approach of putting popular names for our SPs in the base SP descriptions.)

Automated Traffic Signal Performance Measures (ATSPM) Implementation Flows

Information Flow	Description	Inclusion Status
archive analysis requests	A user request that initiates data mining, analytical processing, aggregation or summarization, report formulation, or other advanced processing and analysis of archived data. The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.	Fundamental
archive analysis results	Processed information products, supporting meta data, and any associated transaction information resulting from data mining, analytical processing, aggregation or summarization, report formulation, or other on-line processing and analysis of archived data.	Fundamental
archive coordination	Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests.	Optional
archive management data	Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and any special requests that require direct action by the administrator (e.g., requests for access to new data sources).	Optional
archive management requests	User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive.	Optional
archive request confirmation	Confirmation that an archive request has been received and processed with information on the disposition of the request.	Optional
archived data product requests	A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.	Fundamental
archived data products	Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.	Fundamental
government reporting data receipt	The acknowledgement of satisfactory receipt of information used as input to government data systems or a report identifying problems or issues with the data submittal.	Optional
government reporting system data	Information provided by an ITS archive, formatted as appropriate, that can be used as input to government data reporting systems.	Optional

Automated Traffic Signal Performance Measures (ATSPM) Implementation Functional Objects

Functional Object
Archive Data Repository
Archive Government Reporting
Archive On-Line Analysis and Mining
Archive Situation Data Archival

Back to Implementation List