ITS Architecture Implementation Program
time lapse of traffic traveling down and exiting from a freeway at night
21st Century Operations Using twenty-first Century Technologies

Examples

Home

These example documents from existing regional ITS architectures follow the development process described in the Regional ITS Architecture Guidance Document and meet the requirements of the Final Rule/Final Policy. The Regional ITS Architecture Guidance Document also includes examples from existing regional ITS architectures. Not all elements include provide example documents, and as they become available, they will be added to this web page.


Step 1: Get Started
Development Process Element Example Documents
Architecture Scope: The region is defined geographically. The time frame the regional architecture document covers is defined. The scope of the regional architecture is defined at a high-level (i.e. the range of services, institutions, or jurisdictions are identified).
  • Nashville, TN region–Executive Summary (HTML, DOC - 29KB)
  • Cumberland Gap Tunnel/US 25E region (HTML, DOC - 330KB) - this example includes information from more than one section that together provides a complete architecture scope description.
Stakeholder Identification: Stakeholders are identified in sufficient detail to understand who the players are, what they are responsible for, regional champions, and other descriptive information. A range of stakeholders commensurate with the defined scope of the architecture are involved in the development of the regional ITS architecture.
  • OKI (OH/KY/IN) regional ITS Plan (HTML, DOC - 51KB)
  • Leon County, FL regional architecture (HTML, DOC - 26KB) - this example includes information from more than one section that together provides a complete stakeholder identification description.
  • Northern Virginia Regional ITS Arch (HTML, DOC - 120KB)

Step 2: Gather Data
Development Process Element Example Documents
System Inventory: A system inventory is defined. The system inventory is properly linked to National ITS Architecture market packages and/or subsystems entities. If applicable, user defined entities are described in sufficient detail to understand their function.
  • Leon County, FL regional architecture (HTML, DOC - 63KB)
  • OKI System Inventory (HTML, DOC - 35KB)
Needs and Services: Needs and services are defined and described. Services are connected to the regional ITS architecture through identification of market packages or some similar means. empty cell
Operational Concept: An operational concept is described in sufficient detail to understand the roles and responsibilities of the primary stakeholders and the systems they operate in the region.
Functional Requirements: High-level functional requirements are identified for each regionally significant system that is included in the inventory of the architecture. “Regionally significant systems” are defined as those with interfaces that cross agency boundaries. (So for example, functional requirements for a transit management center would be expected, but not for the systems on board the transit vehicle that primarily interface with the transit management center.)
  • Memphis, TN regional architecture (HTML, DOC - 243KB)

Step 3: Define Interfaces
Development Process Element Example Documents
Interfaces/Flows: Interconnections are identified and information flows are defined for each interface. If applicable, user defined flows are established in sufficient detail to understand the information exchanged.

Step 4: Implementation
Development Process Element Example Documents
Agreements: A list of the agreements and their types (i.e. MOU, letter of agreement, etc.) is identified that will be needed between stakeholders in order to implement the projects that will come out of the regional ITS architecture.
  • I-4 Florida Regional ITS Architecture (HTML, DOC - 34KB)
  • Puget Sound, WA (HTML, DOC - 36KB)
Standards Identification: ITS standards are described that are applicable to the development of projects coming out of the regional ITS architecture. empty cell
Project Sequencing: A plan is established by which projects would be defined and sequenced over time to implement the architecture plan. An initial sequencing of currently defined projects is identified.

Step 5: Use the Regional Architecture
Development Process Element Example Documents
Implementation Plan (use): A plan is defined for incorporating and using the regional ITS architecture as a reference in the planning process for the region. Included in this plan is evidence of a regional stakeholder organization or committee that will monitor and manage the regional architecture considering the planning process. Alternatively, a plan is defined for using the regional ITS architecture in support of project implementation. empty cell

Step 6: Maintain the Regional Architecture
Development Process Element Example Documents
Maintenance Plan: A plan is documented for maintaining the architecture. Included in this plan is the identification of which stakeholder or group has taken responsibility for maintaining the architecture.

Download the free adobe acrobat reader to view PDFs You will need the Adobe Acrobat Reader to view the PDFs on this page.

To view DOC files, you need the Microsoft Word Viewer.