A framework within which a system can be built. Requirements dictate what functionality the architecture must satisfy. An architecture functionally defines what the pieces of the system are and the information that is exchanged between them. An architecture is functionally oriented and not technology-specific which allows the architecture to remain effective over time. It defines "what must be done," not "how it will be done."

Information that is exchanged between subsystems and terminators in the physical architecture view of the National ITS Architecture. Architecture flows are the primary tool that is used to define the Regional ITS Architecture interfaces. These architecture flows and their communication requirements define the interfaces which form the basis for much of the ongoing standards work in the national ITS program. The terms "information flow" and "architecture flow" are used interchangeably.

Communications paths that carry information between subsystems and terminators in the physical architecture view of the National ITS Architecture. Several different types of interconnects are defined in the National ITS Architecture to reflect the range of interface requirements in ITS. The majority of the interconnects are various types of communications links that are defined in the communications layer. Four different types of communications links are defined: Fixed Point - Fixed Point Communications, Wide Area Wireless (Mobile) Communications, Field - Vehicle Communications, and Vehicle - Vehicle Communications. In addition to these types, several specialized interconnects are also defined to reflect other interface requirements. These include human interface (e.g., what the system user sees and hears) and physical/environmental (e.g., what the ITS sensors sense).

A term used in transit operations to describe a vehicle work assignment.

A type of software that allows viewing of and navigation through HTML pages.

Subsystems that provide management, administrative, and support functions for the transportation system. The center subsystems each communicate with other centers to enable coordination between modes and across jurisdictions. Some examples of center subsystems are Traffic Management, Transit Management, Commercial Vehicle Administration, Archived Data Management, Emissions Management, Toll Administration, Emergency Management, Information Service Provider, and Fleet and Freight Management. One of four general subsystem classes defined in the National ITS Architecture.

A network for sharing and exchanging surface weather data and relevant surface transportation conditions.

This document provides a thorough analysis of the communications requirements of the National ITS Architecture, and ITS in general, and includes a discussion of options for implementing various communications links. It is an important document for those involved in detailed design and integration during the systems engineering process.

One of three layers (along with the transportation and institutional layers) defined by the National ITS Architecture. The communications layer includes all of the communications equipment (e.g., wireline and wireless transmitters and receivers) and the information management and transport capabilities necessary to transfer information among entities in the transportation layer. The application data content and the transportation application requirements are generally transparent to the communications layer. The communication layer's view of ITS is that of many distributed users, some of them mobile, which require communication services.

The Cost Analysis document has two purposes. First, it develops a high level cost estimate of the expenditures that are associated with implementing ITS components. Second, it is a costing tool for implementers, by providing unit prices and systems costs of ITS subsystems. There is significant correlation between the Cost Analysis and the Evaluatory Design documents; the cost analysis is based largely on the assumptions made for the three deployment scenarios (urban, interurban, and rural).

Every data flow included in the logical architecture view of the National ITS Architecture is defined in a data dictionary entry. Each data dictionary entry contains a textual description of the data flow and identifies any lower level data elements that make up the data flow.

Data flows represent a pipeline along which information of known composition is passed. Data flows are modeled in the logical architecture view of the National ITS Architecture. Data flows represent data flowing between processes or between a process and a terminator. A data flow is shown as an arrow on a data flow diagram and is defined in a data dictionary entry in the logical architecture. Data flows are aggregated together to form high-level architecture flows in the physical architecture view of the National ITS Architecture.

The diagrams in the logical architecture view of the National ITS Architecture that show the functions that are required for ITS and the information that moves between these functions. Only four different symbols are used on the diagrams. Circles represent the processes or functions that do the work. Arrows represent the data flows that show how data moves through the system. Parallel lines represent data stores that represent "data at rest" in the system. Finally, rectangles represent the terminators that define the architecture boundary. A hierarchy of these diagrams depict the ITS functionality and data flow requirements in successively greater detail until "primitive" processes are defined.

A data store represents a reservoir in which data can be held for an indefinite period. Data stores are shown on the data flow diagrams where data repositories are required to support data aggregation or archival services.

This is the basic building block of Regional ITS Architectures and Project ITS Architectures. It is the name used by stakeholders to describe a system or piece of a system.

Enhanced Metafile. A graphics file format, originated by Microsoft Corporation, that has many advantages over the older Windows metafiles (WMF). Images in EMF format can be resized without distortion and loss of detail. Available for download for selected diagrams (e.g., subsystem and terminator diagrams). Many diagrams displayed on the National ITS Architecture CD-ROM and web site are actually in GIF format.

Equipment packages are the building blocks of the physical architecture subsystems. Equipment Packages group similar processes of a particular subsystem together into an “implementable” package. The grouping also takes into account the user services and the need to accommodate various levels of functionality. The equipment packages were used as a basis for estimating deployment costs (as part of the evaluation that was performed). Since equipment packages are both the most detailed elements of the physical architecture view of the National ITS Architecture and tied to specific market packages, they provide the common link between the interface-oriented architecture definition and the deployment-oriented market packages.

This document contains a concise summary of the various evaluations that were performed in five other National ITS Architecture documents: Evaluatory Design, Communications Document, Cost Analysis, Performance and Benefits Study, and Risk Analysis.

The Evaluatory Design document is intended to evaluate the National ITS Architecture's performance, benefits, and costs for three conceptual scenarios at various points in time. The scenarios consist of "typical" deployment environments: urban, inter-urban, and rural. The entire document will assist you in developing an evaluation methodology for the architecture that you have developed for your particular region.

This document provides an overview of the most important aspects of the National ITS Architecture including the logical architecture, physical architecture and the implementation strategy.

An agency of the United States Department of Transportation that funds highway planning and programs.

An agency of the United States Department of Transportation that funds transit planning and programs.

A wireless communications channel used for close-proximity communications between vehicles and the immediate infrastructure. It supports location-specific communications for ITS capabilities such as toll collection, transit vehicle management, driver information, and automated commercial vehicle operations. One of the types of architecture interconnects defined in the National ITS Architecture.

Intelligent infrastructure distributed along the transportation network which perform surveillance, information provision, and plan execution control functions and whose operation is governed by center subsystems. Field subsystems also directly interface to vehicle subsystems. One of the four general subsystem classes defined in the National ITS Architecture.

A communication link serving stationary entities. It may be implemented using a variety of public or private communication networks and technologies. It can include, but is not limited to, twisted pair, coaxial cable, fiber optic, microwave relay networks, spread spectrum, etc. In Fixed Point - Fixed Point (FP2FP) communication the important issue is that it serves stationary entities. Both dedicated and shared communication resources may be used. One of the types of architecture interconnects defined in the National ITS Architecture.

A statement that specifies WHAT a system must do. The statement should use formal “shall” language and specify a function in terms that the stakeholders, particularly the system implementers, will understand. In the National ITS Architecture, Functional Requirements have been defined for each Equipment Package that focus on the high-level requirements that support regional integration.

Graphic Interchange Format. A widely used graphics file format, developed by CompuServe. Many images found on the National ITS Architecture CD-ROM and web site are in GIF format and can be typically be copied by right-clicking on them with your mouse. Unlike WMF files, GIF files are not well suited for resizing or other modifications.

HyperText Markup Language. A language for marking up documents with a set of tags that designate the design and display intention of the author and how sections or documents are linked together. These documents are displayed as pages with text and graphics that can be viewed through the use of a browser.

The Implementation Strategy document presents a scheme for implementing ITS services in a phased approach. This is part of an overall strategy that includes recommendations for future research and development, operational tests, standards activities, and training. The Implementation Strategy analysis and guidance is all based on market packages. It identifies the market packages that provide certain ITS services and recommends a phased deployment of those market packages to provide the most needed and most feasible user services initially, and less needed/feasible user services at a later date. The Implementation Strategy considers several items and issues regarding deployment, such as legacy systems, politics, funding, market package synergy, technology requirements, and standards requirements. Much of the market package-related analysis that is contained in the Implementation Strategy has been updated and included in the new Market Packages Document. The Market Packages Document is the authoritative source for all current information on the National ITS Architecture market packages.

Information that is exchanged between subsystems and terminators in the physical architecture view of the National ITS Architecture. These information flows are normally identical to the architecture flows in the National ITS Architecture. The terms "information flow" and "architecture flow" are used interchangeably.