Urban landbuilding facilitiestransportation networkssystems technology National and Regional ITS Architectures Bart Cima, IBI Group February 26, 2007

urban land building facilitiestransportation

networkssystems technology

National and Regional ITS Architectures

Bart Cima, IBI Group

February 26, 2007

Overview

• What is the National ITS Architecture?

• User Services

• Logical Architecture

• Physical Architecture

• Market Packages

• Developing a Regional ITS Architecture

• Information Sources



What is the National ITS Architecture?

What is the National ITS Architecture?

• Provides a structured approach for planning, defining, and integrating intelligent transportation systems that meet national and regional needs

• Defines:– Types of systems to be deployed– Functionality of the systems– Information exchanged between the systems

The National ITS Architecture Is a “Tool”

• Framework– Identifies ITS components and interconnections

• Vocabulary– Uses specific terms for clear communications

• Guidance– For development of ITS project– For early identification of integration opportunities– For compliance with ITS Standards– For customized development of a Regional ITS

Architecture

Continuing evolution of the architecture over 13 years

National ITS Architecture is a “Living Document”

MCO Update Ver 4.0

1993 1993-6

1996

19971999 2002

UserServices

Phase I & IIDevelopment

ArchitecturePublished HRI

UpdateADUSUpdateVer 3.0

1998

Version2.0

Transportation Security Update

Version 5.0

2003Current Version: 5.1.1

Federal Regulations

• FHWA Rule and FTA Policy• Regions deploying ITS projects shall use the

National ITS Architecture to develop a Regional ITS Architecture

• All ITS projects shall subsequently adhere to the Regional ITS Architecture and ITS Standards

• Applies to all ITS projects that are funded in whole or in part with the Highway Trust Fund (including Mass Transit Account)

Entry Points Into the Architecture

Source: National ITS Architecture – Version 5



User Services

What is a User Service?

• Defines What ITS Should Do From the User's Perspective

• Represents a Broad Range of Users

• Allows Project Definition to Begin – By Establishing the High Level Services – To Address Identified Problems and Needs

User Services Bundles

1. Travel and Traffic Management

2. Public Transportation Management

3. Electronic Payment

4. Commercial Vehicle Operations

5. Emergency Management

6. Advanced Vehicle Safety Systems

7. Information Management

8. Maintenance and Construction Operations

Travel and Traffic Management

• 1.1 Pre-trip Travel Information • 1.2 En-route Driver Information • 1.3 Route Guidance • 1.4 Ride Matching And Reservation • 1.5 Traveler Services Information • 1.6 Traffic Control • 1.7 Incident Management • 1.8 Travel Demand Management • 1.9 Emissions Testing And Mitigation • 1.10 Highway Rail Intersection

Transit and E-Payment

2.0 Public Transportation Management

• 2.1 Public Transportation Management

• 2.2 En-route Transit Information

• 2.3 Personalized Public Transit

• 2.4 Public Travel Security

3.0 Electronic Payment

• 3.1 Electronic Payment Services



Logical Architecture

Logical Architecture

• Defines the Processes (the Activities and Functions) That Are Required to Provide the Required User Services

• Many Different Processes Must Work Together and Share Information to Provide a User Service

• Can Be Implemented Via Software, Hardware, or Firmware

• Independent of Technologies and Implementations

More of Systems Development Approach

Data Flow Diagram

• Show the Functions That Are Required for ITS and the Information That Moves Between These Functions– Circles Represent the Processes or Functions– Arrows Represent the Data Flows – Parallel Lines Represent Data Stores – Rectangles Represent the Terminators (not shown)

Manage ITS Data Flow Diagram

Source: Version 5 National ITS Architecture

Travel & Traffic Management

Public Transportation Management

Electronic Payment

Commercial Vehicle Operations

Emergency Management

Advanced Vehicle Safety SystemsInformation Management M&C Ops

Manage Traffic – User Services

• 1.1 Pre Trip Travel Information• 1.2 En-Route Driver Information• 1.5 Traveler Services Information• 1.6 Traffic Control• 1.7 Incident Management• 1.8 Travel Demand Management• 1.9 Emission Testing and Mitigation• 1.10 Highway Rail Intersections• 3.1 Electronic Payment Services• 5.3 Disaster Response and Evacuation• 7.1 Archived Data Function• 8.1 Maintenance and Construction Operations

Breakdown of Manage Traffic

1.1 Provide Traffic Surveillance

1.2 Provide Device Control

1.3 Manage Incidents

1.4 Manage Travel Demand

1.5 Manage Emissions

1.6 Manage Highway Rail Intersections

1.2 Provide Device Control

1.2.1 Select Strategy

1.2.2 Determine Road and Freeway State

1.2.3 Determine Ramp State

1.2.4 Output Control Data

1.2.5 Manage Parking Lot State

1.2.6 Maintain Static Data for TMC

1.2.7 Provide Roadside Control Facilities

1.2.8 Collect and Process Indicator Fault Data

1.2.7-Provide Roadside Control Facilities

vehicle_sign_data

vehicle_signage_data

indicator_control_monitoring_data_for_roads

indicator_control_monitoring_data_for_highways

emergency_vehicle_preemptions

transit_vehicle_roadway_priorities

indicator_monitoring_suspend

local_sensor_data_for_roads

intersection_collision_avoidance_data

vehicle_sign_data_status

vehicle_smart_probe_data_indication

vehicle_smart_probe_data_output

smart_probe_reader_status

traffic_control_device_status

fors-sensor_data

local_sensor_data_for_highways

indicator_control_data_for_highways

indicator_input_data_from_highways

td-ramp_state_indication

td-lane_use_indication_for_highways

indicator_response_data_for_highways

indicator_override_for_highways

tmmc-crossing_clear_at_highways

tmmc-highway_equipment_status

tmmc-stop_alternate_mode_at_highways

fmmc-crossing_status_for_highways

f_other_rw_sensor_to_fc

dms_data_from_m_and_c

speed_warning_for_display

dms_status_for_m_and_c

har_data_from_m_and_char_status_for_m_and_c

dms_auto_treat_data_from_roadway

dms_auto_treat_data_from_maint

signal_override_equip_status_for_m_and_c

smart_probe_equip_status_for_m_and_c

vehicle_sign_equip_status_for_m_and_c

indicator_equip_status_from_highways_for_m_and_c

har_data

dms_statusf_other_rw_roadway_info_data

tp-dms_indication

td-dms_indication

t_other_rw_env_sensor_control_by_auto_treat_device

f_other_rw_env_sensor_data_for_auto_treat_device

tors-sensor_control

t_other_rw_dms_auto_treat_data_from_roadway

fors-roadway_info_data_from_devices

fors-sensor_status

tors-roadway_info_data_from_devices

fors-device_status

fors-device_control

tors-device_status

tors-device_control

t_other_rw_fc_to_fc

tmmc-crossing_clear_at_roads


tp-cross_road

indicator_control_data_for_roads

indicator_input_data_from_roads

td-lane_use_indication_for_roads

td-signal_indication

tp-cross_request_received

tmmc-road_equipment_status

tmmc-stop_alternate_mode_at_roads

indicator_response_data_for_roads

indicator_override_for_roads

intersection_state_data

train_sense_data

hri_device_control

hri_device_sense

fmmc-crossing_status_for_roads

f_other_rw_ic_to_ic

indicator_equip_status_from_roads_for_m_and_c

t_other_rw_ic_control_to_traffic_sensor

t_other_rw_ic_to_ic

signal_override_status

f_other_rw_sensor_to_ic

f_other_rw_fc_to_fc

t_other_rw_fc_control_to_traffic_sensor

f_other_rw_work_zone_intrusion_detection

fors-roadway_info_data_from_sensors

vehicle_pollution_message

dms_barrier_activated_from_roadway

t_other_rw_dms_barrier_activated_from_roadway

barrier_system_status

t_other_rw_dms_safeguard_activated_from_roadway

tbv-har_broadcastindividual_vehicle_speed_for_display

dms_data

work_zone_info_for_display

dms_status_for_mcv

dms_safeguard_activated_from_roadway

har_equip_status_for_m_and_c

dms_equip_status_for_m_and_c

har_status

dms_data_from_mcv

barrier_system_control

barrier_system_equip_status_for_m_and_c

dms_auto_treat_status_to_maint

dms_control_data

reversible_lane_control

dms_wide_area_alert_informationhar_wide_

area_alert_information

vehicle_signage_wide_area_alert_information

Process In-vehicle

Signage Data.4

Process Vehicle Smart

Probe Data for Output

.7

Monitor Roadside Equipment Operation for Faults

.2

Manage Indicator Preemptions

.3Provide Intersection

Collision Avoidance

Data.6

Provide DeviceInterface to Other

Roadway Devices.8

ProcessIndicator

OutputData for Freeways

.5

ProcessRoadway

InformationData.9

Process Indicator

Output Data for Roads

.1

ControlBarrierSystems

.10


Process Specification

• Provides an Overview of the Process

• Set of Functional Requirements

• Complete Set of Inputs and Outputs– Data Dictionary

1.2.7.1-Process Indicator Output Data for Roads

• Implement the indicator output data • Provide control at intersections or pedestrian

crossings• Provide the interface for data for units that

manage multimodal crossings or highway-rail intersections

• Monitor the status of the indicator equipment and provide fault status

• Includes list of Data Inputs and Outputs

1.2.7-Provide Roadside Control Facilities

vehicle_sign_data

vehicle_signage_data

indicator_control_monitoring_data_for_roads

indicator_control_monitoring_data_for_highways

emergency_vehicle_preemptions

transit_vehicle_roadway_priorities

indicator_monitoring_suspend


intersection_collision_avoidance_data

vehicle_sign_data_status

vehicle_smart_probe_data_indication

vehicle_smart_probe_data_output

smart_probe_reader_status

traffic_control_device_status

fors-sensor_data

local_sensor_data_for_highways

indicator_control_data_for_highways

indicator_input_data_from_highways

td-ramp_state_indication

td-lane_use_indication_for_highways

indicator_response_data_for_highways

indicator_override_for_highways

tmmc-crossing_clear_at_highways

tmmc-highway_equipment_status

tmmc-stop_alternate_mode_at_highways

fmmc-crossing_status_for_highways

f_other_rw_sensor_to_fc

dms_data_from_m_and_c

speed_warning_for_display

dms_status_for_m_and_c

har_data_from_m_and_char_status_for_m_and_c

dms_auto_treat_data_from_roadway

dms_auto_treat_data_from_maint

signal_override_equip_status_for_m_and_c

smart_probe_equip_status_for_m_and_c

vehicle_sign_equip_status_for_m_and_c

indicator_equip_status_from_highways_for_m_and_c

har_data

dms_statusf_other_rw_roadway_info_data

tp-dms_indication

td-dms_indication

t_other_rw_env_sensor_control_by_auto_treat_device

f_other_rw_env_sensor_data_for_auto_treat_device

tors-sensor_control

t_other_rw_dms_auto_treat_data_from_roadway

fors-roadway_info_data_from_devices

fors-sensor_status

tors-roadway_info_data_from_devices

fors-device_status

fors-device_control

tors-device_status

tors-device_control

t_other_rw_fc_to_fc

tmmc-crossing_clear_at_roads


tp-cross_road

indicator_control_data_for_roads

indicator_input_data_from_roads

td-lane_use_indication_for_roads

td-signal_indication

tp-cross_request_received

tmmc-road_equipment_status

tmmc-stop_alternate_mode_at_roads

indicator_response_data_for_roads

indicator_override_for_roads

intersection_state_data

train_sense_data

hri_device_control

hri_device_sense

fmmc-crossing_status_for_roads

f_other_rw_ic_to_ic

indicator_equip_status_from_roads_for_m_and_c

t_other_rw_ic_control_to_traffic_sensor

t_other_rw_ic_to_ic

signal_override_status

f_other_rw_sensor_to_ic

f_other_rw_fc_to_fc

t_other_rw_fc_control_to_traffic_sensor

f_other_rw_work_zone_intrusion_detection

fors-roadway_info_data_from_sensors

vehicle_pollution_message

dms_barrier_activated_from_roadway

t_other_rw_dms_barrier_activated_from_roadway

barrier_system_status

t_other_rw_dms_safeguard_activated_from_roadway

tbv-har_broadcastindividual_vehicle_speed_for_display

dms_data

work_zone_info_for_display

dms_status_for_mcv

dms_safeguard_activated_from_roadway

har_equip_status_for_m_and_c

dms_equip_status_for_m_and_c

har_status

dms_data_from_mcv

barrier_system_control

barrier_system_equip_status_for_m_and_c

dms_auto_treat_status_to_maint

dms_control_data

reversible_lane_control

dms_wide_area_alert_informationhar_wide_

area_alert_information

vehicle_signage_wide_area_alert_information

Process In-vehicle

Signage Data.4

Process Vehicle Smart

Probe Data for Output

.7

Monitor Roadside Equipment Operation for Faults

.2

Manage Indicator Preemptions

.3Provide Intersection

Collision Avoidance

Data.6

Provide DeviceInterface to Other

Roadway Devices.8

ProcessIndicator

OutputData for Freeways

.5

ProcessRoadway

InformationData.9

Process Indicator

Output Data for Roads

.1

ControlBarrierSystems

.10




Physical Architecture

Physical Architecture

• Forms a high-level structure around the processes and data flows in the Logical Architecture

• Defines the Physical Entities and Their Connections

• Relates to Solutions as Implemented

Subsystems

• Individual physical systems that comprise the overall ITS program

• Four Types– Center– Field– Vehicle– Traveler

National ITS Architecture Subsystems


Key Terms

• Equipment Packages: The building blocks of subsystems. – Examples: “Onboard Transit Signal Priority”, “Roadway

Basic Surveillance”

• Architecture Flows: Data exchanged between ITS subsystems. – Examples: “signal control data”, “traffic images”

• Market Packages:– Links needs to appropriate solutions provided by ITS

applications – Define the components (equipment packages and

subsystems) and interfaces (architecture flows) needed to implement a particular solution

Market Package Service Areas

MARKET PACKAGES1. Advanced Traveler

Information Systems2. Advanced Traffic

Management Systems3. Advanced Public

Transportation Systems4. Emergency Management5. Maintenance and

Construction Management6. Archived Data Management7. Commercial Vehicle

Operations8. Advanced Vehicle Safety

Systems

USER SERVICES1. Travel and Traffic

Management2. Public Transportation

Management3. Electronic Payment4. Emergency Management5. Maintenance and

Construction Operations6. Information Management7. Commercial Vehicle

Operations8. Advanced Vehicle Safety

Systems

Market Package Example

Equipment Package

SubsystemArchitecture Flow



APTS7 – Multi-modal Coordination


ParkingManagement

transit servicecoordination

parking lotdata request

parkinginformation

Transit Vehicle

On-board TransitSignal Priority

Roadway

Roadway SignalPriority

traffic control priority status +request transit information

TrafficManagement

TMC MultimodalCoordination

TMC SignalControl

traffic control priority request +transit system data

local signalpriorityrequest

request forright of way

signal control status

signal control data

Other TransitManagement

transit vehicleschedule

performance

MultimodalTransportation

Service provider

transitmultimodalinformation

TransitManagement

Transit CenterMultimodal Coordination


ParkingManagement

transit servicecoordination

parking lotdata request

parkinginformation

Transit Vehicle

On- board TransitSignal Priority

Roadway

Roadway SignalPriority

TrafficManagement

TMC MultimodalCoordination

TMC SignalControl

local signalpriorityrequest

request forright of way

signal control status

signal control data

Other TransitManagement

transit vehicleschedule

performance

MultimodalTransportation

Service provider

transitmultimodalinformation

TransitManagement

Transit CenterMultimodal Coordination

traffic control priority request +transit system data

traffic control priority status +request transit information

APTS7 King County Metro Multi-modal Coordination

Consolidated View of the Architecture

User ServiceBundles

User Services

Logical Processes Physical Channels

Data Flows Architectural Flows

P-Specs

Subsystems

Communications

EquipmentPackages

Data Dictionary

User ServicesRequirements

Logical Physical

Market Packages

Source: City of Seattle ITS Master Plan (IBI Group)



Developing a Regional Architecture

What is a Regional ITS Architecture?

• Framework for implementing and integrating ITS with a region

• Planning tool for identifying gaps in existing and planned ITS deployments versus transportation needs

• Involves working with agencies to document partnerships, roles, and responsibilities.

Developing a Regional ITS Architecture

Source:

Regional ITS Architecture Guidance: Developing, Using and Maintaining an ITS Architecture For Your Region (October 2001)



Puget Sound Regional ITS Architecture

Puget Sound Regional ITS Architecture Project

• Conduct Stakeholder Outreach Efforts

• Compile Regional ITS Inventory

• Develop Regional ITS Architecture

• Incorporate ITS into Regional Planning Process

• Provide Guidance on Federal ITS Requirements

Puget Sound Regional ITS Architecture

• Framework for Planning and Coordinating How ITS Projects Are Implemented in the Central Puget Sound Region

• Provides Guidance and Resource for Local ITS Project Development

• Addresses Both Technical and Intuitional Coordination

• Based on National ITS Architecture but Tailored to Address Specific Regional Needs

Stakeholder Involvement

• Project Oversight – Regional ITS Advisory Panel• Local, County, and State Traffic Managers • Regional Transit Agencies Technology

Managers• Freight Community• Emergency Management Coordinators • Private Sector Traveler Information Providers • FHWA and FTA• Federal Land Agencies

Regional ITS Architecture Elements

• Description Of The Region• Identification Of Stakeholders• Operational Concept • Required Agreements • System Functional Requirements• Interface Requirements And Information

Exchanges • Identification Of ITS Technical Standards• Sequence Of Projects Required For

Implementation

Operational Concept Development

Operational Concept Defines:• Institutional Relationships

Among Organizations • Roles And Responsibilities • Information Exchange

RoadwayCity Traffic

Management Center

State TrafficManagement Center

Information Sharing

Information Sharing

OperationsMaintenance

CommandRequest

Information Sharing

DataStatusVideo

KEY:RelationshipInformation FlowData

RequestStatusVideo

DataRequestStatusVideo

Agreements Between Organizations

• Documents Current Status of ITS Agreements

• Identifies Needed Agreements as New Projects are Deployed

• Provides Guidance on Elements of New Agreement

Technical Framework

Provides Guidance For Defining• System Functional Requirements• Interface Requirements • Information Exchanges• Based on Market Packages

sensor and surveillance controlroadway information system data

signal control data

traffic control coordinationtraffic information coordination

traffic images

roadway information system statussignal control status

traffic flowtraffic images

State TrafficManagement Center

TMC RegionalTraffic Control

City TrafficManagement Center

Collect TrafficSurveillance

Traffic Maintenance

TMC Signal Control

TMC RegionalTraffic Control

Roadway

Roadway BasicSurveillance

Roadway SignalControls

ITS Technical Standards

• ITS Technical Standards – Allows systems to “talk to each other”– Removes dependency on one vendor– FHWA will tie funding to use of standards

• Identifies Key Regional ITS Technical Standards

• Provides Guidance on Use of Standards

Data Archives

Emergency Management

Fitting It Together

County WSDOT City

Transit

Tolling

Why Develop a Regional ITS Architecture?

• Saves Time and Money During Project Development• Guides Coordination Among Individual Projects• Sets Direction for Improving Efficiency of

Transportation System• Provides Framework for Sharing Information Among

Agencies and General Public• Reduces Cost of Implementation• Conformance With the Federal ITS Requirements Is

Required to Receive Federal Highway Trust Funds

Trubo Architecture

• Tool for Development & Maintenance

• Provides Database

• Maps Relationships

Information Sources

• National ITS Architecture: – http://www.iteris.com/itsarch/

• US DOT ITS Program: – http://www.its.dot.gov/index.htm

• ITS Standards:– http://www.standards.its.dot.gov/default.asp

• ITS Benefits and Costs– http://www.benefitcost.its.dot.gov/

• ITS America– http://www.itsa.org/

• ITS Washington– http://depts.washington.edu/itswa/

Does Any One Use This?

• SR 167 HOT Lanes Project Example

Contact Information

Bart Cima, PE

Director

IBI Group

206-521-9091

[email protected]