The Context for ITS Architecture 1999 APTA Annual Meeting Orlando, Florida

1. The Context forITS Architecture1999 APTA Annual MeetingOrlando, Florida Dr. Christine M. Johnson Director ITS Joint Program Office U.S. Department of Transportation

2. Transportation is Vital to the Fabric of our Communities • High quality network and efficiency are essential • Healthy economies • Happy citizens

3. National Challenges • Congestion will increase by 50% in 10 years • 4.2 trillion ton-miles of freight each year • 5.2 million injuries; 41,000 fatalities

4. Local Challenges • Running out of land • Environmental constraints • Money • Citizens are demanding solutions!

5. We Have the Technology The Information Age Changes Everything!

6. From Building MoreTo Managing Better Whether it’s traffic operations... …or transit operations, The challenge is to operate and manage the transportation network as a whole -- as a system of systems.

7. Integration is the Key • Components working together • Better use of resources • Sharing data across modes and jurisdictions

8. TEA21: ITS Funding Figures shown in Billions TEA-21 clarified NHS, STP and CMAQ funding for ITS activities

9. TEA21: Key ITS Provisions • Develop and maintain National ITS Architecture and standards • Ensure all ITS projects using Highway Trust Funds conform to the National ITS Architecture and standards

10. ITS Standards • We hear: Standards are good but don’t mandate! • Will likely go forward with a period of “best practices” • Some may require a clear mandate for interoperability (e.g. DSRC)

11. From Building MoreTo Managing Better Whether it’s traffic operations... …or transit operations, The challenge is to operate and manage the transportation network as a whole -- as a system of systems.

12. Integration is the Key • Components working together • Better use of resources • Sharing data across modes and jurisdictions

13. The Opportunities • ITS enables: • An infrastructure to manage systems • An infrastructure to communicate with customers • A way to bridge modes and jurisdictions • A way to create seamless functionality

14. The Risks • ITS also brings risks: • Information revolution is happening fast • Continue legacy system paradigm • Separate systems cannot communicate Electronically hardened systems risk deferring the intermodal vision for 10-15 years

15. Why Integration? • The time to act is now! • ITS components are being built today • They are in the legacy system paradigm • Five years from now the pattern will have been set

16. Consistency with the National ITS Architecture and Standards: FHWA FTA ITS Joint Program Office

17. National ITS Architecture ConsistencyDriving Forces From TEA-21: • “The Secretary shall ensure that intelligent transportation system projects carried out using funds made available from the Highway Trust Fund, . . . conform to the national architecture, applicable standards or provisional standards, and protocols developed under subsection(a). ” • -TEA-21 Title V, Sec. 5206(e)

18. National ITS Architecture ConsistencyDriving Forces (continued) Good Practice Benefits: • Lower cost • Reduced development time • Future expansion • Evolutionary deployment • Enhanced system performance • Risk reduction

19. National ITS Architecture Consistency Policy Goals • Achieve system integration • Foster interoperability • Engage stakeholders • Tailor ITS to meet local needs • Enable electronic information sharing among stakeholders • Facilitate future expansion capability

20. National ITS Architecture ConsistencyIdeology Minimize Adding “Processes” • Examine and build on existing • Funds allotted through planning processes • Existing Federal Oversight Balance Between Technical Practicality and “Real-World” Feasibility Phased in over time

21. National ITS Architecture Consistency USDOT Approach • Interim Guidance - First step towards incremental implementation of TEA-21 conformity requirement • Final Policy - Developed through formal rulemaking

22. National ITS Architecture Consistency Final Policy: Thinking to Date • Applicability: • Funding Source: • All ITS projects receiving funds in whole or in part from the Highway Trust Fund, including the • Mass Transit Account

23. National ITS Architecture Consistency Final Policy: Thinking to Date The following presentation represents USDOT thinking to date It does not represent a final decision on a policy approach

24. National ITS Architecture Consistency Final Policy: Thinking to Date Two Notice of Proposed Rulemakings Statewide Transportation Planning; Metropolitan Transportation Planning National Intelligent Transportation Systems Architecture and Standards

25. National ITS Architecture Consistency Final Policy: Thinking to Date • Three key parts: • Transportation Planning • Regional Architecture • Project Development

26. National ITS Architecture ConsistencyFinal Policy: Thinking to Date Transportation Planning: (contained in a separate NPRM) ITS Integration Strategy • ITS Integration Strategy developed by multiple stakeholders • Includes roles and responsibilities • Key system functions and information sharing • Policy agreement on interoperability, standards & operation • Identification of major ITS projects, regional ITS initiatives or projects that support national interoperability • Documented as part of the Transportation Plan,

27. National ITS Architecture ConsistencyFinal Policy: Thinking to Date Regional Architecture: • ITS Regional architecture developed initially or incrementally (consistent with ITS integration strategy) • Regional architecture contains: 1. Concept of Operations - Roles & Responsibilities; - Existing or required agreements to support operations; - Resources to support the project(s)

28. National ITS Architecture ConsistencyFinal Policy: Thinking to Date Regional Architecture: Regional Architecture contains (continued): 2. Conceptual Design - Functional requirements; - Information exchanges with planned & existing systems; - Interface requirements; - Key standards identification supporting national & regional interoperability including equipment compatibility, functions & operating procedures; - Prioritization of phases, steps or projects for implementation. National ITS Architecture is a resource

29. National ITS Architecture ConsistencyFinal Policy: Thinking to Date Project Development: • ITS projects based on a systems engineering analysis • Systems engineering analysis: 1. Identify applicable parts of Regional Architecture and/or ITS Integration Strategy 2. Preliminary analysis, including project objectives,existing system resources, existing personnel & budget resources for operations, management & maintenance

30. National ITS Architecture ConsistencyFinal Policy: Thinking to Date • Project Development: • Systems engineering analysis (continued): • 3. Alternative systems analysis, including functional • requirements, alternative system configurations, • technology options • 4. Procurement analysis • 5. Identification of applicable standards, particularly those • that support national interoperability • National ITS Architecture is a resource • Project specification ensures that design is consistent with Regional Architecture and/or Integration Strategy

31. National ITS Architecture ConsistencyFinal Policy: Thinking to Date • Project Development: • Projectsuse ITS standards adopted by USDOT through rulemaking • - None are currently adopted • - Many are written and being tested • ITS/CVO projects conduct USDOT adopted interoperability tests • - No tests are currently adopted • - Will be adopted through formal rulemaking

32. National ITS Architecture ConsistencyFinal Policy: Thinking to Date • Project Development • Project Administration • Demonstrated linkage between the project and the regional architecture and/or the ITS integration strategy • Documentation includes: • Identification of relevant parts of the regional architecture • Identification of applicable standards • Interagency coordination & rationale for changes contrary to regional architecture

33. National ITS Architecture ConsistencyFinal Policy: Thinking to Date • Proposed Phasing • All ITS projects comply with project development criteria at date of final rule • All provisions apply two years after date of final rule

34. National ITS Architecture ConsistencyFinal Policy: Thinking to Date • After Issuance of Final Regulations, FTA Proposes to Reference the National ITS Architecture By: • Adding it to the annual list of certifications and assurances for FTA grants and cooperative agreements • Updating these FTA circulars: • 5010- Grant Management Guidelines • 9030- Urbanized Area Formula Program • 9300- Capital Programs • Updating the triennial review to assess grantee’s consistency with applicable ITS integration / implementation strategy(ies)

35. National ITS Architecture ConsistencyPolicy Development Schedule • Policy Development Schedule: • - October 1998: Release of Interim Guidance • - Fall 1999: Notice of Proposed Rulemaking (NPRM) on • Conformity with the National ITS Architecture and • Standards • Public Comment Opportunities: • - During NPRM Official Comment Period

36. National ITS Architecture ConsistencySupport Activities • Architecture training course (2 & 3-day versions) • Architecture case studies (fall) • Turbo Architecture (early 2000) • Consultant sessions on Interim Guidance (fall) • Architecture Workshops - Tier I & II (fall)

37. National ITS Architecture ConsistencySupport Activities • Consistent Interpretation within FHWA Divisions • Train-the-Trainer sessions (complete) • Advanced training on National ITS Architecture (fall) • Interim Guidance Workshops (fall) • Deployment Task Force