1 / 22

Mac Lister FHWA Resource Center ITS America Annual Meeting Session 20 May 2, 2005

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. Outline. Peer Exchange Background Peer Exchange Topic Areas Meeting Results by Major Topic Area

Download Presentation

Mac Lister FHWA Resource Center ITS America Annual Meeting Session 20 May 2, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  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. Outline • Peer Exchange Background • Peer Exchange Topic Areas • Meeting Results by Major Topic Area • Overview • Key Findings • Summary

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

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

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

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

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

  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 • 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

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

  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 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

  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 • 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 • Integrating the RA project sequencing list with the TIP project list can help reduce redundancy and aid funding decisions

  12. Using The Regional ITS Architecture for Project Development • 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. Systems Engineering Lifecycle Concept of Operations Operations & Maintenance High Level Requirements System Verification Detailed Requirements High Level Design Subsystem Verification Detailed Design Integration & Test Implementation

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

  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 • 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

  16. Key Findings:Using The Regional ITS Architecture for 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 • Training is a key to widespread acceptance and using the RA and systems engineering

  17. Key Findings:Using The Regional ITS Architecture for Project Development • Setting aside project money for training can help minimize project risk • 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

  18. Maintaining the Regional ITS Architecture • 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. Key Drivers of Regional ITS Architecture Maintenance Transportation Planning Border RA & Statewide Architecture ITS Project Implementation Regional ITS Architecture Other Drivers (technology, new service, political etc.)

  20. Key Findings:Regional ITS ArchitectureMaintenance • 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 • RA maintenance needs to be carried out through a well defined configuration management process • All sources for changes should be considered

  21. Key Findings:Regional ITS ArchitectureMaintenance • 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 • Finding funding and resources for RA maintenance is a common issue

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

More Related