Quick-Starting Your. Regional ITS Architecture Update

(1)

Traffic Management Transit

Management

Fixed Point-to-Fixed Point Communica

Roadway Personal Information Access Communications Vehicle ITS Architecture Workshop

Systems Engineering For ITS Workshop

Quick-Starting Your

Regional ITS Architecture Update

4: Starting at the Finish Line – Architecture Use (& Maintenance)

(2)

ITS Architecture Workshop

The Ultimate Measure of Success

- Productive Architecture Use

2. National ITS Architecture

3. Regional ITS Architecture Components 3E. Architecture Assessment 4. Architecture Use 5. Plan

(3)

ITS Architecture

Workshop

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

(4)

Architecture Use in Project Life

Cycle

Planning Programming/ Budgeting Operations & Maintenance Identified Project Implementation Funded Project Monitoring & Evaluation Implemented Project Regional Architecture Use =

(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

(6)

Workshop

Connecting Stakeholder Visions

 Regional architecture development and update can expand the interaction of

planning and operations

0 ₅ 10 15 20

Long Range Plan

Projects

Regional ITS Architecture

Planners

(7)

Workshop

Transportation Planning Process

Evaluation & Prioritization of Strategies

Development of Long-Range Transportation Plan

Development of Transportation Improvement Programs (TIP/STIP)

Project Development

System Operations

Monitor System Performance Alternate Improvement Strategies

Operations Capital

Feedback

(8)

ITS Architecture Workshop Need Scope Stakeholders Champions Inventory

Needs and Services

Operational Concept Functional Requirements

Project Sequencing

List of Agency Agreements

ITS Standards Interconnects Information Flows

STEP #1: GET STARTED

STEP #2: GATHER DATA

STEP #3: DEFINE INTERFACES

STEP #4: IMPLEMENTATION

Architecture Development is a

Planning Process

(9)

Regional Architecture and

Transportation Planning

Development of Long-Range Transportation Plan (LRTP) Development of Transportation Improvement Programs (TIP/STIP)

Project Development

System Operations

Monitor System Performance Alternate Improvement Strategies

Feedback

Regional ITS Architecture

(10)

Transportation Goals and

Objectives

 Goals

• e.g., Improve transportation system reliability

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

(11)

Goals and Objectives and the

Architecture

 Regional architecture should be based on operations-related goals and objectives

▬ 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

(12)

Workshop

Operational Strategies

 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

Alternate Improvement Strategies

Capital

Regional Goals and Objectives

(13)

Objectives and

Strategies-Example

 Objective

▬ Improve traffic flows by 50%

in peak traffic periods.

 Operations Strategies

▬ 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

(14)

Operational Strategies and the

Architecture

 Architecture services can point to operational strategies

 Facilitate use by mapping operational strategies from the LRTP to architecture services

▬ Look for gaps and inconsistencies

ITS Services (Service

Packages)

(15)

Workshop

Strategies and Services- Example

Objective: Improve traffic flows by 50% in peak traffic periods.

Strategies Service Packages

a. Continue maintaining and updating traffic signal coordination in response to changes in traffic patterns.

ATMS03: Traffic Signal Control ATMS07: Regional Traffic

Management (?)

b. Educate residents about alternative forms of transportation and alternative routes

Education initiatives not covered by ITS, but traveler information service packages could augment that outreach c. Use changeable message signs to

reroute traffic in high-volume corridors.

ATMS06: Traffic Information Dissemination

(16)

Strategy Evaluation and

Prioritization

 Evaluation and prioritization of

strategies are key planning activities

Potential Strategies

LRTP

Selected Strategies

(17)

Strategy Evaluation and

Prioritization

 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”)

Project Sequencing

(18)

LRTP and Architecture

Comparison

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

Development of Long-Range Transportation Plan (LRTP)

(19)

Workshop

Architecture Use in LRTP

Architecture output could be used directly in LRTP Development of Long-Range Transportation Plan (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.

(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

Archived Data Management

Regional Data Warehouse Monitor System Performance

(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

(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 Long Range Plan Strategies, Evaluations, Documentation Original outputs Updated outputs Regional Architecture

(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

(25)

Workshop

ITS Strategic Plan

ITS

Strategic

Plan

Short Term Projects Mid Term Projects Long Term Projects Regional Architecture Emergency Management Center Traffic Management Center TMC Roadway Devices Other TMC traffic information coordination incident information traffic flow incident information Traffic Information Service Provider roadway information system data Emergency Vehicles incident status logged special vehicle route traffic images video surveillance control Other EMC incident report Event Promoter event plans incident response coordination incident command information incident information Maintenance & Construction Management incident information maint. and constr. resource request maint. and constr. resource request Maint. and Const. Center Personnel

maint. and constr. operations information

presentation maint. and constr. center personnel inputs

Other MCM maint. and constr. resource coordination road network conditions

 Regions may also develop ITS specific plans (e.g. ITS Strategic Plan) to support planning

Regional Architecture Emergency Management Center Traffic Management Center TMC Roadway Devices Other TMC traffic information coordination incident information traffic flow incident information Traffic Information Service Provider roadway information system data Emergency Vehicles incident status logged special vehicle route traffic images video surveillance control Other EMC incident report Event Promoter event plans incident response coordination incident command information incident information Maintenance & Construction Management incident information maint. and constr. resource request maint. and constr. resource request Maint. and Const. Center Personnel

maint. and constr. operations informationpresentation

maint. and constr. center personnel inputs

Other MCM maint. and constr. resource coordination road network conditions

(26)

Workshop

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

(27)

Workshop

ITS Strategic Plan (cont.)

 Connects the regional architecture with the strategies and projects in the long range

plan/transportation improvement program

R

egional _Architecture

LR

TP/TIP

ITS Strategic Plan ITS Strategic Plan

(28)

Architecture Use in Project Life

Cycle

(29)

ITS Architecture Workshop Regional Architecture

Architecture Use in

Programming/Budgeting

Planning Agency Project Project Project Project Project w/ITS Project w/ITS 1. Project 2. Project 3. ITS Project ITS Project ITS Project 4. Project w/ITS Regional Architecture Development of Transportation Improvement Programs (TIP/STIP)

Project Development Development of Long-Range

(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

(31)

Architecture Provides a Regional

Context for Planned Projects

Regional Architecture Transportation Improvement Program City TMC Regional 511 Bus Rapid Transit Other Systems Other Systems

Agency Number Project Funding

City C11-321 City TMC $400K

CTrans T12-023 Bus Rapid Transit Ph1 $1.4M DOT D11-843 Regional 511 Ph2 $600K

(32)

Workshop

Project Sponsors

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

(33)

Workshop

Programming/Budgeting Process

 Project Sponsors ▬ Identify Projects ▬ Scope Projects

▬ Submit Project Applications  MPO/State DOTs

▬ Prioritize Projects

▬ Create TIP, STIP, Other

Programming documents Project Sponsors 1 2 3 4

(34)

Workshop

Use to Identify Projects

ITS Project Integration Opportunities Emergency Management Center Traffic Management Center TMC Roadway Devices Other TMC traffic information coordination incident information traffic flow incident information Traffic Information Service Provider roadway information system data Emergency Vehicles incident status logged special vehicle route traffic images video surveillance control Other EMC incident report Event Promoter event plans incident response coordination incident command information incident information Maintenance & Construction Management incident information maint. and constr. resource request maint. and constr. resource request Maint. and Const. Center Personnel

maint. and constr. operations information

presentation maint. and constr. center personnel inputs

Other MCM

maint. and constr. resource coordination road network conditions ITS ProjectITS Project

1

ProjectsIdentify

(35)

Workshop

Use to Identify Projects

ITS 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 9. Project sequencing

1

ProjectsIdentify

(36)

Project Identification

from Architecture

State DOT First Division

State DOT Traffic Management Center City Police Agencies

City Police Dispatch Centers

State DOT and State Department of ... State Police Dispatch Center

State DOT First Division State DOT TMC Field Equipment

County Traffic Engineering Department County Traffic Operations Center

City Traffic Engineering Department City Traffic Management Center

road network conditions

roadway information system data roadway information system status road network conditions

road network conditions

Project A

Project C

Project B

(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 Description  Stakeholders involved

 Stakeholder roles &

responsibilities  Potential partners  Elements involved  Integration opportunities  Dependencies  Budget estimate Project Scoping

(38)

Minnesota Statewide ITS

Architecture Example

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.

(39)

Common

Programming Process

C- Project Prioritization by MPO/State DOT B- Project Submittals by Project Sponsors A- MPO/State DOT issues Request for

Projects

D- Recommend Projects to Project Selection Committee/etc.

B- Project Submittals by Project Sponsors

• Commitment to comply with Rule/Policy

• Identify components of architecture in project

(40)

Identify Architecture

Components

MAG ITS Project Application Form FY09-13

(41)

Common

Programming Process

C- Project Prioritization by MPO/State DOT

• Use criteria for architecture/integration

B- Project Submittals by Project Sponsors A- MPO/State DOT issues Request for

Projects

D- Recommend Projects to Project Selection Committee/etc.

(42)

Example of Use during

Project Prioritization

Rhode Island State Planning Council Addition of new criteria

(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

(44)

Architecture Use in Project Life

Cycle

(45)

Traditional Project Development Process Has Led to Success

 Performance of products and materials well understood

 Requirements well defined and understood

 Proven, well-known technology

 Documented, proven designs

Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance Result  Long-Lasting Highways

are Designed, Built, and Tested

(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

(47)

Traditional Process Does NOT Work for Complex ITS Projects

Project Initiation Preliminary Engineering Plans, Specs & Estimates Construction Project Closeout Operations & Maintenance

(48)

ITS Architecture Workshop System Validation Concept of Operations

Systems Engineering

Project Lifecycle

Time Line System Requirements System Verification/ Deployment Subsystem Verification Unit / Device Testing High-Level Design Detailed Design Software / Hardware Development Field Installation System Validation Plan System Verification Plan

(System Acceptance) Subsystem Verification Plan (Subsystem Acceptance) Unit / Device Test Plan Implementation Document/Approval Operations and Maintenance Changes and Upgrades Retirement/ Replacement System Validation Regional Architecture(s) Feasibility Study / Concept Exploration Concept of Operations

(49)

ITS Architecture Workshop System Validation Concept of Operations

Systems Engineering and

Traditional Project Development

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

(50)

Systems Engineering Reduces

Risk of Project Failure

Source: Standish Group Extreme Chaos 2009

(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

(52)

Systems Engineering Analysis

Requirements

 Rule/Policy requires all Highway Trust Fund-funded projects to be based on a systems engineering analysis

▬ Identifies seven requirements “at a minimum” ▬ Scale commensurate with project scope

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

(53)

Step by Step Architecture Use in

Project Development

Regional ITS Architecture Concept of Operations System Requirements High-Level Design Detailed Design 1 2 3 4

(54)

Mapping ITS Project to the

Regional Architecture

 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

(55)

Mapping ITS Project to the

Regional Architecture (cont.)

 The best approach depends on your regional architecture

 Potential entry points ▬ ITS Services

▬ Project Sequencing

▬ Inventory

▬ Stakeholders

 Develop a roadmap that identifies the best entry point and how to find other related

items ITS Services Project Sequencing Inventory Stakeholders 1

(56)

Example Entry Point for

Architecture

Project Sequencing Standards Identification Operational Concept Functional Requirements Interfaces/ Information Flows Stakeholder Identification Region Description ITS Services ITS Elements Agreements

(57)

Mapping ITS Project to the

Regional Architecture (cont.)

 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

(58)

Example Maine DOT DMS

Project Architecture Subset

Maine Department of Transportation Maine DOT Communications Center

MEMA EOC Maine Department of Transportation Portable Work Zone Field Devices

Maine Department of Transportation Maine DOT Field Devices

Maine Department of Transportation CARS

Local Traffic Operations Center _{Maine Turnpike 24HR Communications} Center

alert status

emergency traffic control information alert notification

emergency traffic control request

roadway information system data roadway information system status

road network conditions

traffic information coordination

DMS Project

Future Project

(59)

Step by Step of Architecture Use

in Project Development

Regional ITS Architecture Concept of Operations System Requirements High-Level Design Detailed Design 1 2 3 4

(60)

Workshop

Concept of Operations

 Get agreement on:

▬ Goals, objectives, and

expectations

▬ Project Scope ▬ Stakeholder

responsibilities

▬ How the system will

operate

▬ Operational and support

environment

Operator User Maintainer

* Adapted from ANSI/AIAA G-043-1992

Concept of

(61)

Architecture Use in a

Concept of Operations

Concept of Operations* 1. Scope 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-043-1992 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

(62)

Example of Architecture

Use in Con Ops

Maine DOT DMS Project Roles and Responsibilities

Architecture

Roles and Responsibilities

Project

Roles and Responsibilities

Maine DOT M&O

 Develop DMS System  Operate DMS System  Maintain DMS System  Coordinate with partners Maine DOT (Other Areas)  Support System Development City of Portland  Coordinate diversion/detours with Maine DOT

 Adapt signal control (future)

… …

Maine DOT  Provides the roadside elements of traffic information dissemination including DMS and HAR Local Traffic Departments

 Share traffic information with other transportation agencies

… …

Concept of

(63)

Workshop

System Requirements

Quality Requirements  Necessary  Unambiguous  Complete  Measurable  Consistent  Achievable  Testable  Technology independent

Specify exactly what

is to be accomplished, how well it is to be accomplished, and under what conditions it is to be accomplished System Requirements 3

(64)

Architecture Use in

Requirements

Concept of Operations High-Level Design Detailed Design System Requirements 3 System 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

(65)

Example of Architecture

Use in Requirements

 Maine DMS Architecture Requirements Element Functional Area ID Requirement Maine DOT Communications Center 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

System

(66)

Workshop

System Design

Appropriate selection of system

components and their interconnection to meet the system requirements

and

The preparation of specifications that describe the design

High-Level Design

Detailed Design

(67)

Workshop

Architecture Use in Design

Concept of Operations System Requirements High-Level Design Detailed Design 4 High-Level Design Detailed Design 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

(68)

Example Architecture Use

in Design

High-Level Design Detailed Design 4

Maine Department of Transportation Maine DOT Communications Center

MEMA EOC Maine Department of Transportation Portable Work Zone Field Devices

Maine Department of Transportation Maine DOT Field Devices

Maine Department of Transportation CARS

Local Traffic Operations Center _{Maine Turnpike 24HR Communications} Center

alert status

emergency traffic control information alert notification

emergency traffic control request

road network conditions

traffic information coordination

DMS Project

(69)

Example Architecture Use

in Design (cont.)

 Architecture interfaces are a starting point for project interface design

Communications

Center Cabinet/Sign_Controller Local Computer Sign ICD 123-1 (NTCIP) ICD 123-2 (NTCIP) ICD 123-3 High-Level Design Detailed Design 4 NTCIP 1203, …

Maine Department of Transportation Maine DOT Communications Center Maine Department of Transportation

Maine DOT Field Devices

(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 Concept of Operations System Requirements High-Level Design Detailed Design Architecture Maintainer

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

(72)

Workshop

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

(73)

Workshop

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