outline project background its architecture overview gvmc its architecture deployment plan

Outline

• Project Background• ITS Architecture Overview• GVMC ITS Architecture• Deployment Plan

Project Background

• Funded by MDOT• Revision of current Regional ITS Architecture• Includes the geographic area covered by the GVMC

MPO boundary• Project started June 2010, will complete April 2011

Why Develop a Regional Architecture?

• Deploy Integrated Systems• Deploy with Regional Needs in Mind• Manage Complexity• Match Needs with ITS Components• FHWA and FTA requirement for projects using

federal funds

National ITS Architecture• Processes and Data Flows

1.3-Manage Incidents

defined_incident_response_changes

To_MediaTo_Traffic_Operations_Personnel

To_Map_Update_Provider

From_Map_Update_Provider

From_Traffic_Operations_Personnel

defined_incident_response_updates

defined_incident_response_data

defined_incident_response_data_request

tep-event_confirmation

fcm-incident_information

tcm-incident_confirmation

incident_details_request

current_incident_data

pollution_incident

fws-current_weather

incident_details

fep-event_information

logged_special_vehicle_route

predicted_incidents

predicted_incident_data

incident_response_status

fws-predicted_weather

tcm-request_incident_change

possible_incidents_data_output

request_possible_incidents_data operations_

incident_data_updates

current_incidentsmedia_

incident_data_updates

reclassify_incidents

current_incidents_request

predicted_incidents_data_output

current_incidents_data_output

possible_defined_responses_output

possible_defined_responses_output_request

defined_incident_response_update_request

possible_defined_responses_data

request_local_current_incidents_data

request_other_predicted_incidents_data other_

current_incidents

request_local_predicted_incidents_data other_

predicted_incidents

predicted_incidents_local_data

request_other_current_incidents_data

undefined_incident_response

incident_alert

incident_strategy_override

vms_updates_for_roads

incident_response_clear

cv_incident_override

predicted_incident_data_for_vehicle_signage

vms_updates_for_highways

current_incident_data_for_vehicle_signage

current_incident_static_data

static_data_request

unusual_data

current_road_network_use

incident_analysis_data

ft-traffic_images

possible_detected_incidents

supply_incident_static_data

incident_video_image

incident_video_image_control

hri_incident_data

hri_strategy_override

resource_request

resource_deployment_status

To_C_and_M

From_C_and_M

incident_video_for_emergency_services

From_Mediareversible_lane_data

video_camera_control_strategy

remote_video_image_control

wrong_way_vehicle_detection

possible_defined_responses

incident_response_log

defined_responses_data

Provide Operator

Interfaces for Incidents

.4

Manage Predetermined

Incident Response

Data.6

Analyze Incident Response

Log.7

Review and Manage Incident

Data.2

Manage Possible

Predetermined Responses

Store.5

Respond to Current Incidents

.3

Traffic DataAnalysis for

Incidents.1

Complex!

• 375 Processes

• 2500 Data Flows

• 91 DFD’s

T r a ff icM a n a g e m e n t

E m e r g e n c yM a n a g e m e n t

M ed ia

E ven tP rom oter

W eath erS erv ice

O th er T M

C on stru ction &M ain ten an ce

T rafficO p eration sP ersonn el

O th erE M

B asic V eh ic le D river

R oadw ayE n viron m en t

tra ff ic f lo w

tra ffic im a g e s

fre e w a y c o n tro l d a ta

fre e w a y c o n tro l s ta tu s

ro a d w a y in fo rm a tio n sy s te m d a ta

ro a d w a y in fo rm a tio n sy s te m s ta tu s

se n so r a n d su rv e illa n c e c o n tro l

se n so r a n d su rv e illa n c e d a ta

in c id e n t d a ta

e n v iro n m e n ta l c o n d itio n s

b road castad v iso ries

d riverin fo rm a tion

w ea th ercon d ition s

tra ff icin fo rm a tio nfo r tra n s it

re q u e s t fo rtra ff ic

in fo rm a tio n

tra ff icin fo rm a tio n

lo g g e dsp e c ia lv e h ic le ro u te

tra ff ic in fo rm a tio n fo r m e d ia

w e a th e r in fo rm a tio n

e v e n t p la n s

tra ff ic in fo rm a tio n c o o rd in a tio n

tra ff ic o p e ra tio n s d a ta

in c id e n tn o tif ic a tio n

in c id e n tin fo rm a tio n

c u rre n tn e tw o rkc o n d itio n s

in c id e n t c o m m a n din fo rm a tio n

in c id e n ts ta tu s

in c id e n tre p o r t

in c id e n t re sp o n sec o o rd in a tio n

m a in te n a n c e re so u rc e re q u e s t

m a in te n a n c e re so u rc e re sp o n se

ro a d c lo su re re q u e s t

c lo su re c o o rd in a tio n

E m e rg e n c y R e s p o n s eM a n a g e m e n t

R oad w ay B asicS u rveillan ce

R oad w ayFreew ay C on tro l

R oad w ay T ra ffic In foD issem in a tion

R oad w ay In c id en tD etec tion

R oad w ay E n v iron m en ta lM on ito rin g

R o a d w a y

C ollec t T ra fficS u rveillan ce

T M C Freew ayM an agem en t

T ra ffic M a in ten an ce

T M C T ra ffic In foD issem in a tion

T M C In c id en tD etec tion

T M C In c id en t D isp a tchC oord /C om m u n ica tion

T M C R oad W ea th erM on ito rin g

tra ff ic o p e ra tio n s re q u e s t

E m erg en cyV eh ic le

T ran sitM an ag em en t

In form ationS erv ice P rov ider



M ed ia

E ven tP rom oter

W eath erS erv ice

O th er T M



O th erE M



tra ffic f lo w

tra ffic im a g e s












tra fficin fo rm a tio nfo r tra n s it

re q u e s t fo rtra ffic

in fo rm a tio n

tra fficin fo rm a tio n


tra ffic in fo rm a tio n fo r m e d ia


e v e n t p la n s

tra ffic in fo rm a tio n c o o rd in a tio n

tra ffic o p e ra tio n s d a ta


















R o a d w a y


T M C Freew ayM a n agem en t

T ra ffic M a in ten an c e




T M C R oa d W ea th erM on ito rin g

tra ffic o p e ra tio n s re q u e s t




Information From Emergency Mgt to Traffic Mgt

• Incident_Duration• Incident_Location• Incident_Number• Incident_Severity• Incident_Type

Incident Type

• “This data flow is used within both the Manage Traffic and Manage Emergency Services functions and defines an incident type using a three character code. This will use a standard set of character codes to uniquely define the type of incident. “



M ed ia

E ven tP rom oter

W eath erS erv ice

O th er T M



O th erE M



tra ff ic f lo w

tra ffic im a g e s












tra ff icin fo rm a tio nfo r tra n s it

re q u e s t fo rtra ff ic

in fo rm a tio n

tra ff icin fo rm a tio n


tra ff ic in fo rm a tio n fo r m e d ia


e v e n t p la n s

tra ff ic in fo rm a tio n c o o rd in a tio n

tra ff ic o p e ra tio n s d a ta


















R o a d w a y


T M C Freew ayM an agem en t

T ra ffic M a in ten an ce




T M C R oad W ea th erM on ito rin g

tra ff ic o p e ra tio n s re q u e s t




Information From Traffic Mgt to Emergency Mgt

• Incident_Video_For_Emergency_Services• Traffic_Data_For_Emergency_Services

What Traffic Data?

• Link_List• Link_Size• Vehicle_Count• Vehicle_Headway• Vehicle_Occupancy• Vehicle_Queue Length• Vehicle_Speed

Using the Regional Architecture

• Supports Varying Levels of Sophistication• Supports Varying Levels of Inter-Agency

Integration

ITS Architecture Development Process

Final

Report

Draft Fi

nal Rep

ort

Draft A

rchite

cture

Docu

men

t

IDAS A

nalysis

& D

eploym

ent

Plan D

evelo

pmen

t

Syste

m In

vento

ryITS

Arch

itectu

re D

evelo

pmen

t

ITS A

rchite

cture

Work

shop

ITS D

eploym

ent P

lan

Work

shop

June 2010 August 2010 January 2011 March 2011

GVMC Boundary

Concurrent Projects

• Regional ITS Architectures and Deployment Plans– Statewide; Grand Region; Southwest and Portions of

University– SEMCOG; Bay Region; North Region; Superior Region;

TCRPC

• Statewide ATMS Software• STOC Implementation • Other ITS Projects in GVMC area

– GVMC Expansion Project– West Michigan TMC

Review of User Needs

• Expanded surveillance on freeways• Improved coordination with media• AVL technology for maintenance vehicles• Improved coordination between 911 dispatch

facilities• Signal Priority for Transit Vehicles• Better access to crash data

ITS Architecture Program Areas

• Traffic Management (ATMS)• Emergency Management (EM)• Maintenance and Construction Management (MC)• Public Transportation (APTS)• Commercial Vehicle Operations (CVO)• Traveler Information (ATIS)• Archived Data Management (AD)• Advanced Vehicles Safety Systems (AVSS)

Market Package Components

• 91 possible MP choices • Identify connections between agencies• Visual representation of the layout of a system that

is constructed using:– Subsystem– Element– Terminator– Architecture Flow

• GVMC has a total of 104 Market Packages

Sample Market Package Customization

planned/future flow

existing flow

user defined flow

Note: MDOT Field Sensors include VIVDS, RTMS, and any other type of vehicle detection.

road network conditions

Media

Local Print and Broadcast Media


ATMS01 – Network SurveillanceMDOT

Information Service Provider

MDOT MI Drive Website

Roadway

MDOT CCTVCameras

Traffic Management

MDOT WMTOC

Roadway

MDOT Field Sensors

traffic images

traffic flow

traffic sensor control

video surveillancecontrol

Sample Market Package Customization

planned/future flow

existing flow

user defined flow

Note: Field Sensors include VIVDS, RTMS, and any other type of vehicle detection.


Media

Local Print and Broadcast Media


ATMS01 – Network SurveillanceGrand Rapids

Information Service Provider

Grand Rapids Traveler Information

Website

Roadway

Grand Rapids CCTVCameras

Traffic Management

Grand Rapids TMC

Roadway

Grand Rapids Field Sensors

traffic images

traffic flow

traffic sensor control

video surveillancecontrol

Interconnect Diagram

From User Needs to Projects

• Refined List of User Needs Is Developed• Market Packages Are Selected To Address User

Needs• Projects Are Developed Based On Market Packages

– Geographically defined– Technologically defined as needed

• Projects Feed The Deployment Plan– Evaluated for Benefit / Cost impact – Segmented to phases for the region

Draft Project List

• MDOT 5-year ITS Plan• ITS Deployment Plan – 2006• Analysis of regional and technological gaps• Stakeholder feedback

Draft Project: Arterials

Draft Project: Freeway

Preliminary Project Listing

• Total of 170 projects– 9 Freeway projects– 41 Arterial projects– 2 Transit projects

• Total of 7 Freeway Service Patrol projects covering approximately 70 miles

Deployment Plan Methodology and IDAS Results

• Alternatives developed based on architecture and stakeholder input

• GVMC Model validated and converted to ITS Deployment Analysis System (IDAS)

• Cost and benefit parameters based on those used in previous MDOT Predeployment studies– Combination of local and national data

• Model run to estimate benefits and costs for 2010 and 2020

• Benefits and costs are annualized

Final Steps

• Addressing Feedback from Deployment Plan Workshop

• Refining Analysis Results from IDAS • Packaging Projects for Deployment Plan• Review by Stakeholders• Submit Final Regional ITS Architecture and

Deployment Plan

outline project background its architecture overview gvmc its architecture deployment plan

Documents

regional needs

emergen traffic data

analysis of regional

data flowscomplex

planits deployment plan

deployment planevaluated

list of user needs

emergency mgtincident