1. urban landbuilding facilitiestransportation networkssystems technology National and Regional ITS Architectures Bart Cima, IBI Group February 26, 2007

2. Overview What is the National ITS Architecture? User Services Logical Architecture Physical Architecture Market Packages Developing a Regional ITS Architecture Information Sources

3. urban landbuilding facilitiestransportation networkssystems technology What is the National ITS Architecture?

4. Provides a structured approach for planning, defining, and integrating intelligent transportation systems that meet national and regional needs Defines: –Types of systems to be deployed –Functionality of the systems –Information exchanged between the systems

5. The National ITS Architecture Is a “Tool” Framework –Identifies ITS components and interconnections Vocabulary –Uses specific terms for clear communications Guidance –For development of ITS project –For early identification of integration opportunities –For compliance with ITS Standards –For customized development of a Regional ITS Architecture

6. Continuing evolution of the architecture over 13 years National ITS Architecture is a “Living Document” MCO Update Ver 4.0 1993 1993-6 1996 1997 1999 2002 User Services Phase I & II Development Architecture Published HRI Update ADUS Update Ver 3.0 1998 Version 2.0 Transportation Security Update Version 5.0 2003 Current Version: 5.1.1

7. Federal Regulations FHWA Rule and FTA Policy Regions deploying ITS projects shall use the National ITS Architecture to develop a Regional ITS Architecture All ITS projects shall subsequently adhere to the Regional ITS Architecture and ITS Standards Applies to all ITS projects that are funded in whole or in part with the Highway Trust Fund (including Mass Transit Account)

8. Entry Points Into the Architecture Source: National ITS Architecture – Version 5

9. urban landbuilding facilitiestransportation networkssystems technology User Services

10. What is a User Service? Defines What ITS Should Do From the User's Perspective Represents a Broad Range of Users Allows Project Definition to Begin –By Establishing the High Level Services –To Address Identified Problems and Needs

11. User Services Bundles 1.Travel and Traffic Management 2.Public Transportation Management 3.Electronic Payment 4.Commercial Vehicle Operations 5.Emergency Management 6.Advanced Vehicle Safety Systems 7.Information Management 8.Maintenance and Construction Operations

12. Travel and Traffic Management 1.1 Pre-trip Travel Information 1.2 En-route Driver Information 1.3 Route Guidance 1.4 Ride Matching And Reservation 1.5 Traveler Services Information 1.6 Traffic Control 1.7 Incident Management 1.8 Travel Demand Management 1.9 Emissions Testing And Mitigation 1.10 Highway Rail Intersection

13. Transit and E-Payment 2.0 Public Transportation Management 2.1 Public Transportation Management 2.2 En-route Transit Information 2.3 Personalized Public Transit 2.4 Public Travel Security 3.0 Electronic Payment 3.1 Electronic Payment Services

14. urban landbuilding facilitiestransportation networkssystems technology Logical Architecture

15. Defines the Processes (the Activities and Functions) That Are Required to Provide the Required User Services Many Different Processes Must Work Together and Share Information to Provide a User Service Can Be Implemented Via Software, Hardware, or Firmware Independent of Technologies and Implementations  More of Systems Development Approach

16. Data Flow Diagram Show the Functions That Are Required for ITS and the Information That Moves Between These Functions –Circles Represent the Processes or Functions –Arrows Represent the Data Flows –Parallel Lines Represent Data Stores –Rectangles Represent the Terminators (not shown)

17. Manage ITS Data Flow Diagram Source: Version 5 National ITS Architecture Travel & Traffic Management Public Transportation Management Electronic Payment Commercial Vehicle Operations Emergency Management Advanced Vehicle Safety Systems Information Management M&C Ops

18. Manage Traffic – User Services 1.1 Pre Trip Travel Information 1.2 En-Route Driver Information 1.5 Traveler Services Information 1.6 Traffic Control 1.7 Incident Management 1.8 Travel Demand Management 1.9 Emission Testing and Mitigation 1.10 Highway Rail Intersections 3.1 Electronic Payment Services 5.3 Disaster Response and Evacuation 7.1 Archived Data Function 8.1 Maintenance and Construction Operations

19. Breakdown of Manage Traffic 1.1 Provide Traffic Surveillance 1.2 Provide Device Control 1.3 Manage Incidents 1.4 Manage Travel Demand 1.5 Manage Emissions 1.6 Manage Highway Rail Intersections

20. 1.2 Provide Device Control 1.2.1 Select Strategy 1.2.2 Determine Road and Freeway State 1.2.3 Determine Ramp State 1.2.4 Output Control Data 1.2.5 Manage Parking Lot State 1.2.6 Maintain Static Data for TMC 1.2.7 Provide Roadside Control Facilities 1.2.8 Collect and Process Indicator Fault Data

21. Source: Version 5 National ITS Architecture

22. Process Specification Provides an Overview of the Process Set of Functional Requirements Complete Set of Inputs and Outputs –Data Dictionary

23. 1.2.7.1-Process Indicator Output Data for Roads Implement the indicator output data Provide control at intersections or pedestrian crossings Provide the interface for data for units that manage multimodal crossings or highway-rail intersections Monitor the status of the indicator equipment and provide fault status Includes list of Data Inputs and Outputs

24. Source: Version 5 National ITS Architecture

25. urban landbuilding facilitiestransportation networkssystems technology Physical Architecture

26. Forms a high-level structure around the processes and data flows in the Logical Architecture Defines the Physical Entities and Their Connections Relates to Solutions as Implemented

27. Subsystems Individual physical systems that comprise the overall ITS program Four Types –Center –Field –Vehicle –Traveler

28. National ITS Architecture Subsystems Source: Version 5 National ITS Architecture

29. Key Terms Equipment Packages: The building blocks of subsystems. –Examples: “Onboard Transit Signal Priority”, “Roadway Basic Surveillance” Architecture Flows: Data exchanged between ITS subsystems. –Examples: “signal control data”, “traffic images” Market Packages: –Links needs to appropriate solutions provided by ITS applications –Define the components (equipment packages and subsystems) and interfaces (architecture flows) needed to implement a particular solution

30. Market Package Service Areas MARKET PACKAGES 1.Advanced Traveler Information Systems 2.Advanced Traffic Management Systems 3.Advanced Public Transportation Systems 4.Emergency Management 5.Maintenance and Construction Management 6.Archived Data Management 7.Commercial Vehicle Operations 8.Advanced Vehicle Safety Systems USER SERVICES 1. Travel and Traffic Management 2. Public Transportation Management 3. Electronic Payment 4. Emergency Management 5. Maintenance and Construction Operations 6. Information Management 7. Commercial Vehicle Operations 8. Advanced Vehicle Safety Systems

31. Market Package Example Equipment Package Subsystem Architecture Flow Source: Version 5 National ITS Architecture

32. Market Package Example APTS7–Multi-modal Coordination Source: Version 5 National ITS Architecture

33. Market Package Example

34. Consolidated View of the Architecture Source: City of Seattle ITS Master Plan (IBI Group)

35. urban landbuilding facilitiestransportation networkssystems technology Developing a Regional Architecture

36. What is a Regional ITS Architecture? Framework for implementing and integrating ITS with a region Planning tool for identifying gaps in existing and planned ITS deployments versus transportation needs Involves working with agencies to document partnerships, roles, and responsibilities.

37. Developing a Regional ITS Architecture Source: Regional ITS Architecture Guidance: Developing, Using and Maintaining an ITS Architecture For Your Region (October 2001)

38. urban landbuilding facilitiestransportation networkssystems technology Puget Sound Regional ITS Architecture

39. Puget Sound Regional ITS Architecture Project Conduct Stakeholder Outreach Efforts Compile Regional ITS Inventory Develop Regional ITS Architecture Incorporate ITS into Regional Planning Process Provide Guidance on Federal ITS Requirements

40. Puget Sound Regional ITS Architecture Framework for Planning and Coordinating How ITS Projects Are Implemented in the Central Puget Sound Region Provides Guidance and Resource for Local ITS Project Development Addresses Both Technical and Intuitional Coordination Based on National ITS Architecture but Tailored to Address Specific Regional Needs

41. Stakeholder Involvement Project Oversight – Regional ITS Advisory Panel Local, County, and State Traffic Managers Regional Transit Agencies Technology Managers Freight Community Emergency Management Coordinators Private Sector Traveler Information Providers FHWA and FTA Federal Land Agencies

42. Regional ITS Architecture Elements Description Of The Region Identification Of Stakeholders Operational Concept Required Agreements System Functional Requirements Interface Requirements And Information Exchanges Identification Of ITS Technical Standards Sequence Of Projects Required For Implementation

43. Operational Concept Development Operational Concept Defines: Institutional Relationships Among Organizations Roles And Responsibilities Information Exchange

44. Agreements Between Organizations Documents Current Status of ITS Agreements Identifies Needed Agreements as New Projects are Deployed Provides Guidance on Elements of New Agreement

45. Technical Framework Provides Guidance For Defining System Functional Requirements Interface Requirements Information Exchanges Based on Market Packages

46. ITS Technical Standards –Allows systems to “talk to each other” –Removes dependency on one vendor –FHWA will tie funding to use of standards Identifies Key Regional ITS Technical Standards Provides Guidance on Use of Standards

47. Fitting It Together

48. Why Develop a Regional ITS Architecture? Saves Time and Money During Project Development Guides Coordination Among Individual Projects Sets Direction for Improving Efficiency of Transportation System Provides Framework for Sharing Information Among Agencies and General Public Reduces Cost of Implementation Conformance With the Federal ITS Requirements Is Required to Receive Federal Highway Trust Funds

49. Trubo Architecture Tool for Development & Maintenance Provides Database Maps Relationships

50. Information Sources National ITS Architecture: –http://www.iteris.com/itsarch/ US DOT ITS Program: –http://www.its.dot.gov/index.htm ITS Standards: –http://www.standards.its.dot.gov/default.asp ITS Benefits and Costs –http://www.benefitcost.its.dot.gov/ ITS America –http://www.itsa.org/ ITS Washington –http://depts.washington.edu/itswa/

51. Does Any One Use This? SR 167 HOT Lanes Project Example

52. Contact Information Bart Cima, PE Director IBI Group 206-521-9091 bcima@ibigroup.com