Archived Architecture Documents
These architecture documents made up a comprehensive and critical resource listing the different components of ITS and the many connections that unite them into an overall framework for deployment. These documents offer thousands of pages of information to help in designing intelligent transportation systems.
The entire suite of core architecture documents was published in June 1996 with the exception of the Market Packages (now called Service Packages) document, which was published in December 1999 for Version 3.0 and Security Document which was published in October 2003 for Version 5.0.
The documents were last updated with Version 7.0 of the National ITS Architecture. Changes were incorporated into the logical architecture, physical architecture, and several other key architecture definition documents. Documents that provide performance, cost, and benefits assessments were not updated. The revision dates next to the document titles indicate which documents were updated for Version 7.0 (January 2012).
The User Services (January 2005 release) document provides an overview of current ITS User Services. This Document consolidates the descriptions of all 33 current user services into a single document.
There are six documents that provide architecture definition:
The Mission Definition (May 2007 update) is one of the original architecture program documents and was developed to explain the original mission of the architecture development effort. It also contains an operational concept for the original architecture development effort tied to the original categorization of urban, interurban, and rural needs. The third major section of the document is a set of operational requirements that define a functional, performance, and data requirements for systems that provide the functionality described in the architecture. While the document has been updated over the years to include the revisions to user services and service packages in the architecture, it basically represents a description of the original architecture development effort, and as such will not be further updated, but retained as an expression of the original mission, needs, and requirements that drove the original development of the architecture.
The Logical Architecture (January 2012 update) document is made up of three volumes:
The Physical Architecture (January 2012 update) document describes the transportation and communications layers resulting from the partitioning of the processes within the logical architecture, presents architecture flow diagrams that show data passing among physical subsystems, and provides characteristics and constraints on the data flows.
The Service Packages (previously called Market Packages) (January 2012 update) document expands upon the Service Package discussion in the Implementation Strategy by providing a comprehensive review of each of the Service Packages describing how Service Packages can be used to plan and implement integrated transportation systems customized to local needs.
The Theory of Operations (January 2012 update) document provides a detailed narrative of the manner in which the architecture supports the ITS user services, described in the Mission Definition document.
There are six documents that pertain to architecture evaluation:
The Communications Document (January 1997 update) provides a thorough analysis of the communications requirements of the National Architecture, and ITS in general, and includes a discussion of options for implementing various communications links.
The Evaluatory Design (June 1996 release) document is intended to evaluate the National 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 Cost Analysis (June 1996 release) 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.
The Risk Analysis (June 1996 release) document presents an analysis of potential critical risks that may delay or prevent the deployment of ITS technologies, and recommends mitigation plans which will eliminate of reduce these risks to the deployment process.
The Evaluation Results (June 1996 release) document contains a concise summary of the various evaluations that were performed in five other National Architecture documents: Evaluatory Design, Communications Analysis, Cost Analysis, Performance and Benefits, and Risk Analysis.
The Implementation Strategy (September 1998 update) document presents a process for implementing ITS services in a phased approach. The process is part of an overall strategy that includes recommendations for future research and development, operational tests, standards activities, and training.
The Standards Development Plan (June 1996 release) discusses the issues that were involved in the development of system interface standards and the relationship of ITS standards to the architecture. It was created as a guide for standards developers during the initial stages of the ITS standards program, and has led to many new ITS standards since then (See www.standards.its.dot.gov for more information on ITS Standards). As a result of enhancements to the architecture since this document was published, there are now additional candidate architecture flows to be considered for future standardization.
SE Michigan Testbed
The SOUTHEAST MICHIGAN TEST BED 2014 CONCEPT OF OPERATIONS (December 2014 release) describes the Concept of Operations (ConOps) for the U.S. Department of Transportation (USDOT) Southeast Michigan Test Bed supporting connected vehicle research and development. This test bed serves as an example of how to deploy connected vehicle applications in a real setting that uses the supporting infrastructure of the modern cooperative or connected environment, including data distribution, system monitoring, and security credentials management.