Regional ITS Architecture Guidance Document
Table of Contents
List of Figures
Figure 1: Regional ITS Architecture Development Process
Figure 2: Regional ITS Architecture scope for the Delaware Valley RPC
Figure 3: Adjacent/Overlapping Regions
Figure 4: Stakeholder Identification and Involvement Over Time
Figure 5: Grouping ITS Elements into General Inventory Elements
Figure 6: Florida DOT District 3 Inventory by Stakeholder Excerpt
Figure 7: Inventory Details for a Florida DOT District 3 ITS Element
Figure 8: Florida DOT District 3, Extended Subsystem Diagram
Figure 9: Example list of Regional Needs
Figure 10: ATMS Market Packages Identified to Support Needs
Figure 11: ITS Element Report with Market Package Instances
Figure 12: Roles and Responsibilities View in Turbo Architecture
Figure 13: Equipment Package Report showing Functional Requirements
Figure 14: Functional Areas Selection in Turbo Architecture
Figure 15: Functional Requirements Selection in Turbo Architecture
Figure 16: Turbo Architecture Functional Requirements Report (partial)
Figure 17: Greater Yellowstone Rural ITS Architecture Interconnect Diagram
Figure 18: Albuquerque Regional ITS Architecture Interconnect Diagram
Figure 19: DVRPC Regional ITS Architecture Flow Diagram
Figure 20: Example of an Information flow Diagram Interface Specification
Figure 21: Information Flows in a Market Package Instance Diagram
Figure 22: Georgia Statewide Architecture Project Sequencing Report
Figure 23: Market Package Instance for Project 3
Figure 24: Regional Standards Plan Content
Figure 25: Candidate ITS Standards Excerpt for
road network condition
Figure 26: Vermont ITS Standards Plan Excerpt
Figure 27. Project Plans Excerpt for Eugene-Springfield
Figure 28: Using the Regional Architecture
Figure 29: ITS Architecture and the Transportation Planning Process
Figure 30: San Diego Long Range Plan Excerpt - IMTMS
Figure 31: Enhancing Regional ITS Architecture Use over Time
Figure 32: ITS Architecture and ITS Strategic Plans
Figure 33: Other Planning Activities
Figure 34: Congestion Management Process
Figure 35: Safety Planning and the ITS Architecture
Figure 36: ITS Project Programming/Budgeting/Capital Planning
Figure 37: Metropolitan Transportation Commission ITS Projects Designation
Figure 38: AMATS Project Sponsor Checklist
Figure 39: Rhode Island State Planning Commission ITS Project Scoring
Figure 40: NYSDOT Project Programming Process
Figure 41: Using the ITS Architecture in Project Implementation
Figure 42: Architecture and Location-Specific Projects
Figure 43: Systems Engineering Approach
Figure 44: Systems Engineering and Traditional Project Development
Figure 45: Rule/Policy Systems Engineering Analysis Requirements
Figure 46: Using the Architecture to Support Systems Engineering
Figure 47: Example Maine DMS Project Architecture Subset
Figure 48: Architecture Use for Concept of Operations
Figure 49: DMS Project Example Diagram
Figure 50: Architecture Use in System Requirements Development
Figure 51: Project System Requirements Analysis
Figure 52: Architecture Use in Project Design
Figure 53: Example DMS Project Architectural Design
Figure 54: Providing Feedback to the Regional ITS Architecture
Figure 55: VDOT Project Architecture Submittal Form
Figure 56. Process for Change Identification
Figure 57. Sample Configuration Identification Document
Figure 58: Index Page of the National ITS Architecture Hypertext View
Figure 59: Diagram of Entry Points to the National ITS Architecture
Figure 60: Representative Market Package Graphic
Figure 61: Turbo Architecture Customize Tab
Figure 62: Sample Architecture Flow Diagram
Figure 63: Sample Turbo Architecture Report
Table of Contents
