Connecticut Statewide ITS Architecture Stakeholder Meetings - - PowerPoint PPT Presentation

Connecticut Statewide ITS Architecture

Stakeholder Meetings January 2005

2

Goals

Of this project:

• Develop a Statewide ITS

Architecture for Connecticut

– Conformance with the National ITS Architecture and Standards – Satisfy Federal requirements for Regional ITS Architecture development

• Facilitate interagency coordination

– Necessary for effective delivery of ITS services

Of this meeting:

• Introduce the project
• Collect information

– ITS in the region (existing and planned) – Regional needs

3

Presentation Outline

• ITS Architecture Background

– Federal Requirements – Relevance and Benefits

• Statewide Architecture Project

– Approach – Involvement Plan

ITS Architecture Background

5

ITS Architecture Definition

• National ITS Architecture

– A general framework for planning, defining, and integrating ITS – Defines the component systems and their interconnections and information exchanges

• Regional ITS Architecture

– A specific regional framework for ensuring institutional agreement and technical integration for the implementation of ITS projects in a particular region

6

Federal Requirements

• All ITS projects funded through the Highway Trust Fund (in whole or in

part) must conform with the National ITS Architecture and applicable standards.

• FHWA Rule and FTA Policy:

– Conformance with the National ITS Architecture defined as the use of the National ITS Architecture to develop a Regional ITS Architecture. – Regions with ITS projects (as of 2001) must develop a Regional ITS Architecture by April 8, 2005.

7

Benefits of a Regional ITS Architecture

• Access to Federal Funding
• Cost Savings

– Coordination of capital investment among agencies leads to lower

• verall costs

– Adherence to standards leads to long-term maintenance cost savings – Future system upgrades and expansion facilitated by use of standards

8

Benefits of a Regional ITS Architecture (cont’d.)

• Improved Interagency Coordination

– Communication facilitated in architecture development process – Operational concept established – Necessary agreements identified

• Better Services to Public

– Consistency across jurisdictional boundaries – Examples:

• VMS messages
• Travel information websites
• Electronic fare collection

Statewide ITS Architecture Project

10

Study Area

Initial scope: Greater Hartford Current scope: Statewide

11

Previous and Ongoing Studies

• Intelligent Transportation Systems "ITS”: A Strategic Plan for the Capitol

Region (1997)

• ConnDOT ITS Implementation Plan (June 1999)
• ITS Strategic Deployment Plan for the New Haven-Meriden Metropolitan

Area (1999)

• Greater Bridgeport Regional ITS Study and Concept Design (June 2001)
• ITS Strategic Deployment Plan: Southeast Connecticut (Dec. 2002)
• Hartford Area Regional ITS Architecture (2004)
• Regional ITS Architecture/Advanced Concept Plan for Greater

Bridgeport Planning Region (ongoing)

• Intelligent Transportation Systems Plan: South Western Region

(ongoing)

12

Architecture Development Approach

• Previous studies to be used as starting point

– Updating based on current deployment and needs assessment

• Top-down approach to development:

Functional Requirements Systems and Technologies Needs

• Stakeholder participation

essential for:

– Identification of needs – Identification of existing systems to integrate – Interagency coordination

• The end result is only as good as the input received!

13

Expected Outcome of Project

• ITS Architecture

– Updated documentation of needs, inventory, etc. – Interactive website

• Implementation Plan

– Deployment-oriented approach – Recommendations for ITS initiatives

14

15

16

17

Project Tasks

• 1. Data Collection & Stakeholder Identification
• Stakeholder Involvement Plan
• ITS Inventory
• Compilation of Needs/Functional Requirements
• 2. Definition of ITS Interfaces
• Architecture Development Workshop
• Regional ITS Architecture Website
• 3. Implementation of ITS Projects
• Implementation Plan
• Operational Considerations
• 4. Development of ITS Architecture Document

18

Participants

• Core Project Team:

– Connecticut Department of Transportation – Federal Highway Administration / Federal Transit Authority – Regional Planning Organizations

• Other Stakeholders:

– Transit Operators – Municipalities

• Public Works
• Fire/Police

– CT Department of Public Safety

19

Stakeholder Involvement

• Initial Individual Meetings

– Provide background on project – Develop ITS inventory – Obtain information on needs, current activities, and planned projects

• Architecture Development Workshop

– Obtain input on architecture elements and interfaces – Includes follow-up review of Draft Architecture Website

• Review Meeting for Draft Architecture

– Presentation of draft Final Report

20

Schedule

2005 2004 Apr Dec Jan Feb Mar Oct Nov

Data Collection & Stakeholder Identification Definition of ITS Interfaces Implementation of ITS Projects Development of ITS Architecture Document

Initial Meetings Architecture Workshop (2/7/05) Review Meeting

21

Questions for Discussion

• 1. What ITS elements have been implemented by your

agency/organization?

• 2. Which of your upcoming or planned projects have ITS components?
• 3. With what other organizations do you share data/information?
• 4. What information from other organizations would be valuable for your
• perations?
• 5. What are your organization’s current investment priorities (not

necessarily ITS-related)?

• 6. What are the key issues or concerns that your organization is currently

facing?

22

Contact Information

• ConnDOT:

– Hal Decker: (860) 594-3431 harold.decker@po.state.ct.us – Bob Kennedy: (860) 594-3458 robert.kennedy@po.state.ct.us

• FHWA:

– Bob Ramirez: (860) 659-6703 x3004 robert.ramirez@fhwa.dot.gov

• IBI Group:

– Angus Davol: (617) 450-0701 adavol@ibigroup.com