1. Implementation: Results from the Using Your Regional ITS Architecture Peer Exchange Network Workshop Mac Lister FHWA Resource Center ITS America Annual Meeting Session 20 May 2, 2005

2. 2 Outline Peer Exchange Background Peer Exchange Background Peer Exchange Topic Areas Peer Exchange Topic Areas Meeting Results by Major Topic Area Meeting Results by Major Topic Area –Overview –Key Findings Summary Summary

3. 3 Peer Exchange Background Kansas City, MO Kansas City, MO 7-8 December 2004 7-8 December 2004 24 Participants 24 Participants 8 Regions 8 Regions

4. 4 Participants Included Regional Transportation Planners Regional Transportation Planners State ITS Engineers & Program Specialists State ITS Engineers & Program Specialists ITS Project Engineers ITS Project Engineers City and State Traffic Engineers City and State Traffic Engineers FHWA Area Engineers FHWA Area Engineers

5. 5 Regions Participating Amarillo Amarillo Binghamton Binghamton Northeastern Illinois Northeastern Illinois Central Ohio Central Ohio Southeast Michigan Southeast Michigan Kansas City Kansas City Sacramento Sacramento Puget Sound Puget Sound

6. 6 Purpose of the Peer Exchange Share experiences Share experiences Gather lessons learned Gather lessons learned Document findings Document findings Aid regions in earlier stages of deployment/use Aid regions in earlier stages of deployment/use

7. 7 Peer Exchange Topic Areas Linking the Regional ITS Architecture and the Transportation Planning Process Linking the Regional ITS Architecture and the Transportation Planning Process Using The Regional ITS Architecture for Project Development Using The Regional ITS Architecture for Project Development Maintaining the Regional ITS Architecture Maintaining the Regional ITS Architecture

8. 8 Regional ITS Architecture Connection to the Transportation Planning Process The development of the Regional ITS Architecture is in collaboration with the formal transportation planning process The development of the Regional ITS Architecture is in collaboration with the formal transportation planning process Integration with the planning process is key to meeting the intent of the FHWA rule and FTA policy Integration with the planning process is key to meeting the intent of the FHWA rule and FTA policy Local stakeholders must decide how to bring both processes together to best serve the region Local stakeholders must decide how to bring both processes together to best serve the region

9. 9 Where Can the Regional ITS Architecture be Applied ? ITS Project Implementation (SE Process) Funding Region description Region description Stakeholder identification Stakeholder identification System inventory System inventory Needs and services Needs and services Operational concept Operational concept Functional requirements Functional requirements Interfaces / Information flows Interfaces / Information flows Maintenance plan Maintenance plan Agreements Agreements Standards identification Standards identification Project sequencing Project sequencing Regional ITS Architecture Products Concept of Operations High Level Requirements Detailed Requirements High Level Design Detailed Design Implementation Operations & Maintenance System Verification Subsystem Verification Integration & Test ITS Strategic Planning Needs ID Regional Integration Planning Project Definition ITS Related Project Transportation Planning Process Long Range Transportation Plan State Transportation Improvement Program Goals Objectives Policies Projects

10. 10 Key Findings: Linking the Architecture and the Transportation Planning Process The RA development process fosters involvement of operators/project developers in the larger transportation planning process The RA development process fosters involvement of operators/project developers in the larger transportation planning process The RA process has helped to get relevant stakeholders from a variety of modes involved in the ITS planning process The RA process has helped to get relevant stakeholders from a variety of modes involved in the ITS planning process Posting the RA on the Internet is useful for information sharing, gathering updates, and making changes to both the RA and other transportation plans Posting the RA on the Internet is useful for information sharing, gathering updates, and making changes to both the RA and other transportation plans

11. 11 Key Findings: Linking the Architecture and the Transportation Planning Process The RA is useful for transportation planning in that it provides a complete inventory of ITS project elements, a description of how projects are integrated, and stakeholder agreement on project deployment needs The RA is useful for transportation planning in that it provides a complete inventory of ITS project elements, a description of how projects are integrated, and stakeholder agreement on project deployment needs Some regions use their ITS Deployment Plan as a vehicle for including RA project needs in the transportation planning process Some regions use their ITS Deployment Plan as a vehicle for including RA project needs in the transportation planning process Different regions have their own way of approving their RA and considering it ready for use Different regions have their own way of approving their RA and considering it ready for use Integrating the RA project sequencing list with the TIP project list can help reduce redundancy and aid funding decisions Integrating the RA project sequencing list with the TIP project list can help reduce redundancy and aid funding decisions

12. 12 Using The Regional ITS Architecture for Project Development FHWA Final Rule 940.11/FTA Policy and ITS Project Implementation FHWA Final Rule 940.11/FTA Policy and ITS Project Implementation –Requires all ITS projects be based on a systems engineering analysis on a scale commensurate with the project scope –All ITS projects shall accommodate the interface requirements and information exchanges as specified in the Regional ITS Architecture

13. 13 Concept of Operations High Level Requirements Detailed Requirements High Level Design Detailed Design Implementation Operations & Maintenance System Verification Subsystem Verification Integration & Test Systems Engineering Lifecycle

14. 14 Where can the Regional ITS Architecture be Applied ? Concept of Operations High Level Requirements Detailed Requirements High Level Design Detailed Design Region description Region description Stakeholder identification Stakeholder identification System inventory System inventory Needs and services Needs and services Operational concept Operational concept Functional requirements Functional requirements Interfaces / Information flows Interfaces / Information flows Maintenance plan Maintenance plan Agreements Agreements Standards identification Standards identification Project sequencing Project sequencing Regional ITS Architecture Products

15. 15 Key Findings: Using The Regional ITS Architecture for Project Development The RA development process allows operators/project developers to understand how a project fits in the overall deployment vision for a region/state The RA development process allows operators/project developers to understand how a project fits in the overall deployment vision for a region/state Having an identified RA coordinator helps ensure that ITS and/or enabling technologies are considered in capital projects Having an identified RA coordinator helps ensure that ITS and/or enabling technologies are considered in capital projects State DOT project development manuals need to be updated to reflect ITS, RA and systems engineering State DOT project development manuals need to be updated to reflect ITS, RA and systems engineering

16. 16 Key Findings: Using The Regional ITS Architecture for Project Development State IT departments can be engaged as partners/stakeholders in project development State IT departments can be engaged as partners/stakeholders in project development FHWA assistance welcomed in getting the RA and systems engineering message out to other stakeholders FHWA assistance welcomed in getting the RA and systems engineering message out to other stakeholders Training is a key to widespread acceptance and using the RA and systems engineering Training is a key to widespread acceptance and using the RA and systems engineering

17. 17 Key Findings: Using The Regional ITS Architecture for Project Development Setting aside project money for training can help minimize project risk Setting aside project money for training can help minimize project risk RA and systems engineering benefits need to be documented and shared RA and systems engineering benefits need to be documented and shared Methods need to be found to encourage RA and systems engineering for projects where no federal funds are used Methods need to be found to encourage RA and systems engineering for projects where no federal funds are used

18. 18 Maintaining the Regional ITS Architecture Maintenance procedures needs to be developed and implemented (per the Rule) to Maintenance procedures needs to be developed and implemented (per the Rule) to –Keep RA current as needs and plans evolve within the region –Expand the RA to include new stakeholders as they are identified or engaged –Reflect changes as projects are designed and implemented –Reflect changes in project priority or status

19. 19 Key Drivers of Regional ITS Architecture Maintenance Transportation Planning ITS Project Implementation Regional ITS Architecture Other Drivers (technology, new service, political etc.) Border RA & Statewide Architecture

20. 20 Key Findings: Regional ITS Architecture Maintenance In-house RA development may provide some maintenance benefits, although staff turnover could be an issue. Consultants can be considered In-house RA development may provide some maintenance benefits, although staff turnover could be an issue. Consultants can be considered Changes in the National ITS Architecture and Turbo Architecture do not require a change the RA unless the changes affect the components in the RA Changes in the National ITS Architecture and Turbo Architecture do not require a change the RA unless the changes affect the components in the RA RA maintenance needs to be carried out through a well defined configuration management process RA maintenance needs to be carried out through a well defined configuration management process All sources for changes should be considered All sources for changes should be considered

21. 21 Key Findings: Regional ITS Architecture Maintenance Tracking changes on a project by project basis and correspondingly updating the RA is a challenge Tracking changes on a project by project basis and correspondingly updating the RA is a challenge Some agencies have had success in funding RA maintenance from SPR or MPO work plan funds Some agencies have had success in funding RA maintenance from SPR or MPO work plan funds Finding funding and resources for RA maintenance is a common issue Finding funding and resources for RA maintenance is a common issue

22. 22 Summary Lots of valuable information and lessons learned resulted from workshop Lots of valuable information and lessons learned resulted from workshop Workshop summary will be made available Workshop summary will be made available DOT is factoring findings into future programs/efforts DOT is factoring findings into future programs/efforts Contact Mac Lister for more information Contact Mac Lister for more information –Mac.Lister@fhwa.dot.gov Mac.Lister@fhwa.dot.gov –Phone 708-283-3532