Quick-Starting Your. Regional ITS Architecture Update

Transcription

1 Personal Information Access Transit Management Traffic Management Communications Fixed Point-to-Fixed Point Communica Vehicle Roadway Quick-Starting Your Systems Engineering For ITS Regional ITS Architecture Update 4: Starting at the Finish Line Architecture Use (& Maintenance)

2 The Ultimate Measure of Success - Productive Architecture Use 5. Plan 3E. Architecture Assessment 4. Architecture Use 3. Regional ITS Architecture Components 2. National ITS Architecture 4-2

3 Session Outcomes Identify how the regional architecture can support long range planning activities Describe how an architecture can be used to program/budget ITS projects Describe the relationship between architecture and systems engineering 4-3

4 Architecture Use in Project Life Cycle Monitoring & Evaluation Planning Identified Project Operations & Maintenance Programming/ Budgeting Implemented Project Implementation Funded Project Regional = Architecture Use 4-4

5 Reasons for Architecture Use in Transportation Planning Architecture represents a consensus vision of Operations and Planning stakeholders for deployment of ITS systems Addresses both short range projects and long range strategies 4-5

6 Connecting Stakeholder Visions Regional architecture development and update can expand the interaction of planning and operations Planners Long Range Plan Regional ITS Architecture Operations Projects 4-6

7 Transportation Planning Process Regional Goals and Objectives Alternate Improvement Strategies Operations Capital Evaluation & Prioritization of Strategies Development of Long-Range Transportation Plan Development of Transportation Improvement Programs (TIP/STIP) Feedback Project Development System Operations Monitor System Performance 4-7

8 Architecture Development is a Planning Process STEP #1: GET STARTED Need Scope Champions Stakeholders STEP #2: GATHER DATA Inventory Needs and Services Operational Concept Functional Requirements STEP #3: DEFINE INTERFACES Interconnects Information Flows STEP #4: IMPLEMENTATION Project Sequencing ITS Standards List of Agency Agreements 4-8

9 Regional Architecture and Transportation Planning Regional Goals and Objectives Alternate Improvement Strategies Operations Capital Evaluation & Prioritization of Strategies Regional ITS Architecture Development of Long-Range Transportation Plan (LRTP) Development of Transportation Improvement Programs (TIP/STIP) Project Development Feedback System Operations Monitor System Performance 4-9

10 Transportation Goals and Objectives Goals e.g., Improve transportation system reliability Objectives Regional Goals and Objectives e.g., By 2020, decrease average annual traveler delay associated with road closures, major incidents, and weather-related conditions on interstate highways by 20 percent from 2005 levels. 4-10

11 Goals and Objectives and the Architecture Regional Goals and Objectives Regional architecture should be based on operations-related goals and objectives Regional ITS Architecture Ensure architecture and long range plan are guided by the same operations objectives Leverage architecture traceability Use Architecture to identify associated performance measures and define a framework for performance monitoring 4-11

12 Operational Strategies Regional Goals and Objectives Alternate Improvement Strategies Operations Capital Asset Management Access Management Traffic Signal Timing Congestion Mitigation Corridor Traffic Management Emergency Transportation Operations Freeway Management Freight Operations and Technology Real Time Traveler Information Road Weather Management Tolling and Pricing Program Travel Demand Management Traffic Incident Management Work Zone Management 4-12

13 Objectives and Strategies- Example Objective Improve traffic flows by 50% in peak traffic periods. Operations Strategies Regional Goals and Objectives Alternate Improvement Strategies Operations Capital Continue maintaining and updating traffic signal coordination in response to changes in traffic patterns Use changeable message signs to reroute traffic in high-volume corridors Reference: Champaign County Long Range Transportation Plan 4-13

14 Operational Strategies and the Architecture Regional ITS Architecture ITS Services (Service Packages) Alternate Improvement Strategies Operations Capital Architecture services can point to operational strategies Facilitate use by mapping operational strategies from the LRTP to architecture services Look for gaps and inconsistencies 4-14

15 Strategies and Services- Example Alternate Improvement Strategies Operations Capital Objective: Improve traffic flows by 50% in peak traffic periods. Strategies a. Continue maintaining and updating traffic signal coordination in response to changes in traffic patterns. b. Educate residents about alternative forms of transportation and alternative routes c. Use changeable message signs to reroute traffic in high-volume corridors. Service Packages ATMS03: Traffic Signal Control ATMS07: Regional Traffic Management (?) Education initiatives not covered by ITS, but traveler information service packages could augment that outreach ATMS06: Traffic Information Dissemination 4-15

16 Strategy Evaluation and Prioritization Potential Strategies Regional Goals and Objectives Alternate Improvement Strategies Operations Capital Evaluation & Prioritization of Strategies Evaluation and prioritization of strategies are key planning activities Selected Strategies LRTP 4-16

17 Strategy Evaluation and Prioritization Regional ITS Architecture Project Sequencing Evaluation & Prioritization of Strategies Project Sequencing output contains info useful to evaluation/prioritization Stakeholders Benefits Mapping to service packages Define mid-long term projects in language suitable for the plan (e.g. as strategies ) 4-17

18 LRTP and Architecture Comparison Development of Long-Range Transportation Plan (LRTP) LRTP Goals, objectives, strategies, and projects to achieve it Covers at least the next 20 years Leads to an intermodal system Fiscally constrained Must be updated every 4-5 years Architecture ITS Services and projects Long term timeframe Covers multiple modes Not fiscally constrained Updated per maintenance plan 4-18

19 Architecture Use in LRTP Development of Long-Range Transportation Plan (LRTP) Architecture output could be used directly in LRTP Executive summary material/graphics from the architecture could be appropriate for the LRTP The Regional Intelligent Transportation Systems (ITS) Architecture for the Kansas City metropolitan region is a specific regional framework for documenting and ensuring institutional agreement and technical integration for the implementation of ITS projects in the region. The documentation of the regional integration among transportation systems enables comprehensive planning and deployment activities while also supporting the sharing of information and coordination of activities that enables efficient and effective operations. Kansas City Transportation Outlook

20 Monitor System Performance 4-20

21 Architecture Use in Performance Monitoring Architecture defines collection of data from operational systems to support performance monitoring Consider regional examples of Archived Data Management Subsystem (ADMS) to automate collection of data from: Traffic Transit Emergency Services Traveler Information Monitor System Performance Archived Data Management Regional Data Warehouse 4-21

22 Architecture Use in Planning for Operations Applying the Regional ITS Architecture to Support Planning for Operations A Primer Timing of Updates: Architecture updated prior to LRTP update Architecture updated after LRTP update Both updates at same time 4-22

23 Usefulness of the Regional Architecture In supporting long range plan development Current regional architecture may have limited usefulness Revise architecture outputs during update cycles to increase usefulness Updated outputs Original outputs Long Range Plan Regional Architecture Strategies, Evaluations, Documentation 4-23

24 Regional Architecture - Making it Useful Explicitly connect architecture needs and services to objectives and strategies Describe mid-long term projects in language suitable for the plan (e.g. as strategies ) Create executive summary material/ graphics as part of architecture that would be appropriate for the LRTP Formally approve architecture 4-24

25 ITS Strategic Plan Regions may also develop ITS specific plans (e.g. ITS Strategic Plan) to support planning incident response coordination incident status Regional Architecture Other EMC Emergency Management Center incident command information Emergency Vehicles Maint. and Const. Center Personnel incident report Traffic Information Service incident Provider information logged special vehicle route incident information incident information maint. and constr. resource request maint. and constr. operations information presentation maint. and constr. center personnel inputs incident information Traffic Management Center Maintenance & Construction Management road network conditions traffic flow traffic images video surveillance control roadway information system data traffic information coordination maint. and constr. resource request maint. and constr. resource coordination TMC Roadway Devices Other TMC event plans Event Promoter Other MCM incident response coordination incident status ITS Strategic Plan Regional Architecture Other EMC Emergency Management Center incident command information Emergency Vehicles Maint. and Const. Center Personnel incident report incident information incident information incident information maint. and constr. resource request maint. and constr. operations information presentation maint. and constr. center personnel inputs logged special vehicle route incident information Traffic Information Service Provider Traffic Management Center Maintenance & Construction Management road network conditions traffic flow traffic images video surveillance control roadway information system data maint. and constr. resource request traffic information coordination maint. and constr. resource coordination event plans TMC Roadway Devices Other TMC Event Promoter Other MCM Short Term Projects Mid Term Projects Long Term Projects 4-25

26 ITS Strategic Plan (cont.) Contains elements that go beyond the regional architecture requirements Vision, Goals, and Objectives Strategies for ITS deployment Funding considerations Detailed project definitions Gaps in planned projects Benefits analysis Communications Plan 4-26

27 ITS Strategic Plan (cont.) Connects the regional architecture with the strategies and projects in the long range plan/transportation improvement program Regional Architecture ITS Strategic Plan LRTP/TIP 4-27

28 Architecture Use in Project Life Cycle Monitoring & Evaluation Planning Identified Project Operations & Maintenance Programming/ Budgeting Implemented Project Implementation Funded Project Regional = Architecture Use 4-28

29 Architecture Use in Programming/Budgeting Development of Long-Range Transportation Plan Regional Architecture Regional Architecture Development of Transportation Improvement Programs (TIP/STIP) Project Development Project w/its Project Project Project Project Project w/its ITS Project ITS Project Planning Agency 1. Project 2. Project 3. ITS Project 4. Project w/its 4-29

30 Benefits of Architecture Use in Programming/Budgeting Link objectives and needs of the region with ITS deployed in the field Take a regional view Begin coordination of projects of various organizations by defining from the same reference point 4-30

31 Architecture Provides a Regional Context for Planned Projects Regional Architecture Transportation Improvement Program Other Systems City TMC Agency Number Project Funding City C City TMC $400K Bus Rapid Transit CTrans T Bus Rapid Transit Ph1 $1.4M Other Systems Regional 511 DOT D Regional 511 Ph2 $600K 4-31

32 Project Sponsors Many agencies identify and plan projects simultaneously: Cities Counties Transit Agencies Toll Authorities State DOTs MPOs Project Sponsors 4-32

33 Programming/Budgeting Process Project Sponsors 1 Identify Projects 2 Scope Projects 3 Submit Project Applications MPO/State DOTs 4 Prioritize Projects Create TIP, STIP, Other Programming documents Project Sponsors 4-33

34 Use to Identify Projects 1 Identify Projects incident response coordination incident status Other EMC Emergency Management Center Emergency Vehicles incident report incident command information Maint. and Const. Center Personnel incident information logged special vehicle route incident information incident information maint. and constr. resource request maint. and constr. operations information presentation maint. and constr. center personnel inputs Traffic Information Service Provider Traffic Management Center incident information Maintenance & Construction Management road network conditions traffic flow traffic images video surveillance control roadway information system data traffic information coordination maint. and constr. resource request event plans maint. and constr. resource coordination TMC Roadway Devices Other TMC Event Promoter Other MCM Integration Opportunities ITS ITS ITS Project Project Project 4-34

35 Use to Identify Projects 1 Identify Projects ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan ITS Projects 4-35

36 Project Identification from Architecture 1 Identify Projects Project C City Police Agencies City Police Dispatch Centers State DOT and State Department of... State Police Dispatch Center road network conditions road network conditions road network conditions road network conditions Project B road network conditions State DOT First Division State DOT TMC Field Equipment State DOT First Division State DOT Traffic Management Center County Traffic Engineering Department County Traffic Operations Center roadway information system data roadway information system status road network conditions Project A City Traffic Engineering Department City Traffic Management Center 4-36

37 Use to Define Project Details 2 Scope Projects ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Project Scoping Project Description Stakeholders involved Stakeholder roles & responsibilities Potential partners Elements involved Integration opportunities Dependencies Budget estimate 4-37

38 Minnesota Statewide ITS Architecture Example 2 Scope Projects ID: S03 Project Title: Enhance Traveler Information Map for Mobile Devices Timeframe: Short Term Years 0-3 Transportation Policy Area: Traveler Safety, Statewide Connections, Twin Cities Mobility, Greater Minnesota Metropolitan and Regional Mobility ITS Service Area: ATIS Description: A traffic flow map showing real-time traffic conditions of freeways and selected expressways in the metro area is currently available on Mn/DOT s website for use by mobile devices that can access the Internet. This project will Project Champion and Stakeholder: Project Champion: Mn/DOT (RTMC), Private Companies. Stakeholders: Mn/DOT Project Elements: RTMC, 511 Traveler Information Website, User Personal Portable Computing Devices Market Package: ATIS01 Broadcast Traveler Information Interconnects RTMC (website) and User Personal Portable Computing Devices RTMC and 511 Traveler Information Website 511 Traveler Information Website and User Personal Portable Computing Devices Technology Assessment: Traffic flow map for the metro area is already available on the Mn/DOT website. Technology for making information formatted in a way that is usable on handheld devices is readily available. Project Dependency: This project is not dependent upon any other projects. Cost Estimate: $35K Needs and Objectives Addressed Need: TI03 Provide traffic flow maps showing recurring or predicted freeway congestion levels Objectives: O-2 Reduce crashes due to unexpected congestion, O-24 Reduce congestion and delay, Agreement: Agreements may be required for this project between Mn/DOT and Private Companies that distribute handheld devices that disseminate traveler information. 4-38

39 Common Programming Process 3 Submit Projects A- MPO/State DOT issues Request for Projects B- Project Submittals by Project Sponsors Commitment to comply with Rule/Policy Identify components of architecture in project C- Project Prioritization by MPO/State DOT D- Recommend Projects to Project Selection Committee/etc. 4-39

40 Identify Architecture Components 3 Submit Projects MAG ITS Project Application Form FY

41 Common Programming Process 4 Prioritize Projects A- MPO/State DOT issues Request for Projects B- Project Submittals by Project Sponsors C- Project Prioritization by MPO/State DOT Use criteria for architecture/integration D- Recommend Projects to Project Selection Committee/etc. 4-41

42 Example of Use during Project Prioritization 4 Prioritize Projects Rhode Island State Planning Council Addition of new criteria 4-42

43 Use in Programming/Budgeting Keys for Success Define near term projects in more specificity to feed into programming and budgeting processes Promote integration projects in region Establish process that uses architecture 4-43

44 Architecture Use in Project Life Cycle Monitoring & Evaluation Planning Identified Project Operations & Maintenance Programming/ Budgeting Implemented Project Implementation Funded Project Regional = Architecture Use 4-44

45 Traditional Project Development Process Has Led to Success Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance Performance of products and materials well understood Requirements well defined and understood Proven, well-known technology Documented, proven designs Result Long-Lasting Highways are Designed, Built, and Tested 4-45

46 Traditional Process Can Work for Low Risk ITS Projects Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance ITS infrastructure expansion projects Requirements Defined Product Performance Solid Technology Proven Designs Documented 4-46

47 Traditional Process Does NOT Work for Complex ITS Projects Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance 4-47

48 Systems Engineering Project Lifecycle Regional Architecture(s) Feasibility Study / Concept Exploration Operations and Maintenance Changes and Upgrades Retirement/ Replacement Concept of of Operations System Validation Plan System Validation System Requirements High-Level Design Detailed Design System Verification Plan (System Acceptance) Subsystem Verification Plan (Subsystem Acceptance) Unit / Device Test Plan System Verification/ Deployment Subsystem Verification Unit / Device Testing Software / Hardware Development Field Installation Document/Approval Time Line Implementation 4-48

49 Systems Engineering and Traditional Project Development Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance Regional Architecture(s) Feasibility Study / Concept Exploration Operations and Maintenance Changes and Upgrades Retirement/ Replacement Concept Concept of of Operations System Validation System Requirements System Verification/ Deployment High-Level Design Subsystem Verification Detailed Design Unit / Device Testing Software / Hardware Development Field Installation 4-49

50 Systems Engineering Reduces Risk of Project Failure Source: Standish Group Extreme Chaos

51 Purpose of Systems Engineering Improve the chances of developing a system on-time and on-budget that meets the users needs Reduce risk Control costs and schedule Satisfy users needs Improve system quality 4-51

52 Systems Engineering Analysis Requirements Rule/Policy requires all Highway Trust Fundfunded projects to be based on a systems engineering analysis Identifies seven requirements at a minimum Scale commensurate with project scope 23 CFR Portion of Regional ITS Architecture 2. Participating agencies roles and responsibilities 3. Requirements definitions 4. Alternatives analysis 5. Procurement options 6. ITS standards and testing procedures 7. Operations and management procedures and resources 4-52

53 Step by Step Architecture Use in Project Development Regional ITS Architecture Concept of Operations 2 1 System Requirements 3 High-Level Design Detailed Design

54 Mapping ITS Project to the Regional Architecture 1 Identify the portion of the regional ITS architecture relevant to the project ITS Services Inventory Elements Functional Requirements Interfaces/Information Flows Should be identified early before firm cost estimates are established 4-54

55 Mapping ITS Project to the Regional Architecture (cont.) 1 The best approach depends on your regional architecture Potential entry points ITS Services Project Sequencing Inventory Stakeholders Project Sequencing Stakeholders ITS Services Develop a roadmap that identifies the best entry point and how to find other related items Inventory 4-55

56 Example Entry Point for Architecture Region Description Stakeholder Identification ITS Elements Functional Requirements Operational Concept ITS Services Interfaces/ Information Flows Agreements Project Sequencing Standards Identification 4-56

57 Mapping ITS Project to the Regional Architecture (cont.) 1 Regional architecture will include more integration opportunities than can be implemented in a single project Account for future integration requirements in current project Consider how current project will support future extensions Phased implementation 4-57

58 Example Maine DOT DMS Project Architecture Subset 1 MEMA EOC Maine Department of Transportation Portable Work Zone Field Devices alert status emergency traffic control information alert notification emergency traffic control request Maine Department of Transportation Maine DOT Field Devices roadway information system data roadway information system status Maine Department of Transportation Maine DOT Communications Center Maine Department of Transportation CARS roadway information system data roadway information system status traffic information coordination road network conditions traffic information coordination Local Traffic Operations Center Maine Turnpike 24HR Communications Center DMS Project Future Project 4-58

59 Step by Step of Architecture Use in Project Development Regional ITS Architecture Concept of Operations 2 1 System Requirements 3 High-Level Design Detailed Design

60 Concept of Operations Concept of Operations 2 Operator User Maintainer * Adapted from ANSI/AIAA G Get agreement on: Goals, objectives, and expectations Project Scope Stakeholder responsibilities How the system will operate Operational and support environment 4-60

61 Architecture Use in a Concept of Operations Concept of Operations 2 ITS Architecture 1. Region description 2. Stakeholder identification 3. Operational Concept 4. Agreements 5. Functional requirements 6. Interfaces / Information flows 7. Standards identification 8. Project sequencing 9. Maintenance plan 10. ITS Elements 11. ITS Services 1. Scope Concept of Operations * 2. Referenced Documents 3. User-Oriented Operational Description 4. Operational Needs 5. System Overview 6. Operational Environment 7. Support Environment 8. Operational Scenarios * Outline per ANSI/AIAA G

62 Example of Architecture Use in Con Ops Concept of Operations 2 Maine DOT DMS Project Roles and Responsibilities Architecture Roles and Responsibilities Maine DOT Local Traffic Departments Provides the roadside elements of traffic information dissemination including DMS and HAR Share traffic information with other transportation agencies Project Roles and Responsibilities Maine DOT M&O Maine DOT (Other Areas) City of Portland Develop DMS System Operate DMS System Maintain DMS System Coordinate with partners Support System Development Coordinate diversion/detours with Maine DOT Adapt signal control (future) 4-62

63 System Requirements System 3 Requirements Specify exactly what is to be accomplished, how well it is to be accomplished, and under what conditions it is to be accomplished Quality Requirements Necessary Unambiguous Complete Measurable Consistent Achievable Testable Technology independent 4-63

64 Architecture Use in Requirements System 3 Requirements ITS Architecture 1. Region description 2. Stakeholder identification 3. Operational Concept 4. Agreements 5. Functional requirements 6. Interfaces / Information flows 7. Standards identification 8. Project sequencing 9. Maintenance plan 10. ITS Elements 11. ITS Services Concept of Operations System Requirements High-Level Design Detailed Design 4-64

65 Example of Architecture Use in Requirements System 3 Requirements Maine DMS Architecture Requirements Element Maine DOT Communications Center Functional Area ID Requirement TMC Traffic Information Dissemination 1 The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers. Maine DMS Project Requirements The center shall remotely control dynamic message signs Add detailed child requirements to: Activate and display a message Prioritize messages Define a message (pick list, spell check) Blank the sign Schedule messages for display 4-65

66 System Design High-Level Design Detailed Design 4 Appropriate selection of system components and their interconnection to meet the system requirements and The preparation of specifications that describe the design 4-66

67 Architecture Use in Design High-Level Design Detailed Design 4 ITS Architecture 1. Region description 2. Stakeholder identification 3. Operational Concept 4. Agreements 5. Functional requirements 6. Interfaces / Information flows 7. Standards identification 8. Project sequencing 9. Maintenance plan 10. ITS Elements 11. ITS Services Concept of Operations System Requirements High-Level Design Detailed Design 4-67

68 Example Architecture Use in Design High-Level Design Detailed Design 4 MEMA EOC Maine Department of Transportation Portable Work Zone Field Devices alert status emergency traffic control information alert notification emergency traffic control request Maine Department of Transportation Maine DOT Field Devices roadway information system data roadway information system status Maine Department of Transportation Maine DOT Communications Center Maine Department of Transportation CARS roadway information system data roadway information system status traffic information coordination road network conditions traffic information coordination Local Traffic Operations Center Maine Turnpike 24HR Communications Center DMS Project Future Project 4-68

69 Example Architecture Use in Design (cont.) High-Level Design Detailed Design 4 Architecture interfaces are a starting point for project interface design Maine Department of Transportation Maine DOT Field Devices Maine Department of Transportation Maine DOT Communications Center Sign roadway information system data roadway information system status Local Computer NTCIP 1203, ICD (NTCIP) ICD Communications Center ICD (NTCIP) Cabinet/Sign Controller 4-69

70 Providing Feedback to the Architecture Maintainer ITS Architecture 1. Region description 2. Stakeholder identification 3. Operational Concept 4. Agreements 5. Functional requirements 6. Interfaces / Information flows 7. Standards identification 8. Project sequencing 9. Maintenance plan 10. ITS Elements 11. ITS Services Architecture Maintainer Concept of Operations System Requirements High-Level Design Detailed Design 4-70

71 A Regional ITS Architecture is a Living Document To remain useful, the architecture must be kept up to date Need a Plan to maintain it Required in the Rule/Policy: The agencies and other stakeholders participating in the development of the regional ITS architecture shall develop and implement procedures and responsibilities for maintaining it, as needs evolve within the region. 4-71

72 Update the Maintenance Plan WHO will be responsible? Suggesting, approving, making changes WHEN will updates occur? How often, under what circumstances WHAT will be maintained? Databases, website, documents HOW will changes be managed? Change management procedures Version controls, naming conventions Stakeholder notification 4-72

73 Session Outcomes Identify how the regional architecture can support long range planning activities Describe how an architecture can be used to program/budget ITS projects Describe the relationship between architecture and systems engineering 4-73