Update on VDOT’s Northern Virginia ITS Architecture Plan
and Integrated Corridor Management (ICM) Activities
MANAGEMENT, OPERATIONS, AND INTELLIGENT TRANSPORTATION SYSTEMS (MOITS)
TECHNICAL SUBCOMMITTEE MEETING, MWCOG
Chris Francis
Operations Division
September 10, 2013
Virginia Northern Region Operations (NRO) ITS
Architecture Update
ITS Architecture Stakeholder Input (many new stakeholders)
Planning
Operations
Transit
Rail
Public Safety
Update of VA NRO ITS Architecture Currently Underway
Expected completion by mid October
Content consistent with other VA ITS Architectures and adjoining ITS
architectures to the extent possible
VA NRO ITS Architecture will be in the same format as the other five VA
ITS Architectures
ITS Architecture Training
Half Day – Late October / Early November
FHWA-sponsored Systems Engineering – Mid November / Early
December
Virginia NRO ITS Architecture Significant Changes

I-495/I-395 Express (HOT) Lanes
 Remove Remote Workstation, add Center-to-Center with MPSTOC
 Add City of Alexandria Public Safety interface
 Add Prince William County Office of Public Safety Communications
 Add Stafford County Public Safety

VA Transportation Emergency Operations Center (TEOC) capability folded into each
VDOT regional TOC including the MPSTOC

VDOT Customer Call Center critical voice communications added to MPSTOC

Plans for a Virginia Transit Information Portal owned by Virginia Department of Rail
and Public Transportation (VDRPT)
 Information sharing potential for all VA transit properties

Integrated Corridor Management (ICM) for Northern Virginia

Update to I-66 Active Traffic and Demand Management System

Addition of Arlington County ITS Architecture
Virginia ITS Architecture Tool

Web-Based Recorded Presentations (Approx 3 hours total)










Introduction
Why is Architecture Useful?
Overview of the National ITS Architecture Version 7.0
Overview of FHWA’s Use and Application of ITS Architecture Primer
Why is Architecture Required?
New Project Development Walk-Through
Demonstration of Systems Engineering Process
How to Manage Architecture Databases using Turbo Architecture
Review of Useful USDOT and Virginia Resources
Each Module will End with an Interactive Quiz
I-95/I-395 ICM Initiative – Key Deliverables
 Concept-of-Operations
 ICM Architecture and Systems Engineering
Management Plan
 Deployment Plan w/Multimodal Works Packages
(Corridor-wide and Segment-based)
 ICM Partnership – Ideas for an Institutional Framework
for ICM Implementation
I-95/I-395 ICM Initiative Activities
I-95/I-395 ICM Project Definition
•
I-95 / I-395 ICM ConOps & Project
Development Task began in
October, 2011
•
Project Limits - Spotsylvania
Interchange to 14th Street Bridge
•
Project Segments
I. US 1/17 to Rt 610 (MM126-144)
II. Rt 610 to I-495 (MM144-170)
III. I-495 to 14th St Br (I-395, MM0-8)
•
Develop ICM application strategies,
and technology-based solutions
ICM Initiative – Stakeholder Engagement
ICM Application Strategies
 Success of ICM depends on
 End-to-End Trip Making
 Intra and Inter Modal Shifts
 Transit/TDM Strategies are the Drivers
 Intra Modal – SOV to HOV
 Inter Modal – Highway to Bus, Rail
 Enablers





Dynamic Ride Share,
Flex Hours/Telework
Ingress Opportunities – Real Time Travel Conditions, Parking
Information (P&R), Transit Info (Next Bus/Rail)/BRT
Last Mile Opportunities – Shuttle/Zip Car/Bike/Walk
ICM Concept Applications
Travel Time Information for All Travel Modes
•
Pre-trip and en-route travel time information for multiple travel
modes along the corridor (95/395. HOT, US1, bus, train)
•
Delays, congestion, restrictions at bases / work locations
•
Personal trip planning tool (end-to-end, compare/mix travel modes)
•
Address road and transit options and available parking should
transit, carpool or slugging option be considered by the traveler
Real-time Parking Management and Guidance
•
Park-and-ride space and guidance information (VDOT, VRE, WMATA
parking facilities near I-95) for travelers entering the corridor via
arterials, where they may have two or more options relative to
parking and either carpooling, slugging or using transit.
•
Comparative travel time information for transit options (including
next bus / train departure) would be presented along with parking
space availability.
ICM Emphasis Areas
 Operations-Related Work Packages
 Segment-based (but includes central hardware/software)
 Infrastructure-oriented
 En-route orientation
 Benefits to various modes
 TMP-related
 Traveler Information-Related Work Packages
 Corridor-wide
 Build on 511 / current rideshare initiatives
 Pre-trip orientation
 Encourage mode shift, moves from SOV to HOV and transit
 Entire investment could qualify as a TMP-related offset
 Decision Support Performance Management Systems are future
elements
ICM Building Blocks
ICM Infrastructure
Freeway
Active
Traffic
Management
ICM Traveler
Information
Personalized
Multi-Modal
Real-Time
Trip Planning
ICM Decision
Support
Modeling and
Decision
Support
Performance
Management
Integrated Single Info Gateway (including kiosks)
Existing Traffic Data
Existing Transit Data
I-95/I-395 ICM Initiative – TDM is Key
•
Achieving the goals to increase dynamic rideshare, change
of mode and time of travel will be facilitated through
improved transparency of information provided:
•
•
•
Travel times for all modes
Real-time availability of parking spaces at existing parking
areas
Better informed travelers will make better decisions on
mode, time and route of travel
The target is to fill every empty seat across modes!
ICM Initiative - Next Steps
 I-95/I-395 Project Specific
 Develop an Implementation Plan (underway)
 Develop Project Sets for specific applications (underway)
 Examples – Enhanced Incident Management, Arterial Management, Ramp
Metering, Parking Management, Traveler Information, etc.
 Establish a ICM Working Group (to be initiated)
 Establish ICM as Program
 Development of an ICM Framework
 Promote application of ICM on other congested corridors