Phoenix International Raceway Phoenix International Raceway (PIR)(PIR)

Presented By:Presented By:

Nicolaas SwartNicolaas SwartTraffic Engineering & ITS Program ManagerTraffic Engineering & ITS Program Manager

Maricopa County DOTMaricopa County DOT

April 26, 2006April 26, 2006

Presented By:Presented By:

Nicolaas SwartNicolaas SwartTraffic Engineering & ITS Program ManagerTraffic Engineering & ITS Program Manager

Maricopa County DOTMaricopa County DOT

April 26, 2006April 26, 2006

Traffic ManagementTraffic Management

Background Traffic Management Benefits & Successes Lessons Learned

OverviewOverview

4th largest & one of the fastest-growing counties in the nation

More than 3 million people 24 cities and towns

Maricopa County

Southwest of Phoenix metropolitan area 400-acre, multi-purpose facility Attendance 200,000 over 3-day event; 100,000 on

the day of main event On-site parking for 28,000 vehicles, 4,000 overflow 4,000 off-site parking park-n-ride

Phoenix International Raceway

Size and duration of events Reduce Travel Time to and from event Incident Management during event ingress and

egress Reliability of traffic information to motorists (parking,

access, etc.) Roadway capacity

Challenges

Challenges

Access (freeway and arterial) - few alternate inbound/outbound routes

2 Hours Prior to Event

Improve freeway and arterial access to PIR Improve parking guidance and circulation Centralize traffic management functions Coordinate incident management Improve traveler information Minimize impacts on nearby neighborhoods

Goals

Program Planning Event Operations Planning Implementation Activities Day-of-Event Activities Post Event Activities

Comprehensive PIR Event Management Plan

Regional Level (PIR, ADOT, DPS, Cities, Sheriff, ALERT, REACT, PIO, ITC)

Local Level (jurisdictions of signalized intersections)

Agreements Permits

Program Planning

Performance goals & objectives (Attendee, non-attendee, transit)

Measures of effectiveness for assessing performance objectives (parking, intersections, freeways, streets)

Design Parameters (traffic lanes, ramp capacity, emergency vehicle lanes, lane capacity)

Event Operations Planning

Traffic Management Plan―Site Access & Parking Plan―Traffic Flow Plan―Traffic Control Plan―Traveler Information Plan―Local Resident Information Plan―Traffic Surveillance Plan―Incident Management & Safety Plan―Staffing Assignment Plan, Contact List―Contingency Plan

Event Operations Planning

Equipment Personnel Assignment Testing & Verification

Implementation Activities

Monitoring Unified Command Communications & Coordination Manage change – Adjustments (though the overall

planned goal remains paramount) Media interaction Traveler Information Dissemination

Day-of-Event Activities

Evaluation (planned framework, measure of effectiveness)

Analyze surveys Stakeholder debriefing Post event plan amendments Recommend potential applications for future events

Post Event Activities

Key Features AZTech Institutional Framework Capacity Enhancements Application of ITS (cameras, DMS – fixed/portable,

TMC) Rental Car Center Displays Marketing (511 on information brochures)

TM

Key Features –

Unified Command Organization EVENT COMMANDER

DPS

MCSO

AVONDALE

POLICE DEPT.

PIR EVENT ORGANIZER

GOODYEAR

POLICE DEPT.

INTERSECTION

CONTROL OFFICERS

INTERSECTION

CONTROL OFFICERS

INTERCHANGE

OFF RAMP CONTROL OFFICERS

ALERT

INFORMATION OFFICER

BRANCHES

GROUPS

UNITS

TRAFFIC

CONTROL CREWS

REACT

MCSO

INSIDE

SECURITY

COUNTY PARKS CAMPGROUND

INTERSECTION

CONTROL OFFICERS

PARKING CONTROL

PRIVATE TOWING

COMPANY

PARK-N-RIDEBUSES

ENFORCEMENTACCIDENT CONTROL

MCSO

MCDOT

AlternateEvent Commander

PARKINGLOT

STAFF

PARKINGCOMMAND(PIR Contractor)

OFFICERSIN

FIELD

TRAFFICCOMMAND

(MCSO)

COMMUNICATION CENTER

511Phone*/

Fax/E-Mail**

Nextel

Clear ChannelPhone*

OTHER RADIOFax/E-Mail **

TVFax/E-Mail **

NEWSPAPERFax/E-Mail **

MCDOT/PIR COMMUNICATION PLAN

Information FlowApril 5, 2006

* Phone = Hard line & Cell** Fax/E-Mail = electronic, simultaneous, immediate

Key Features – Communications Plan

Travel Time Savings (outbound: 5.5 hours in 1998 to 2.5 hours in 2005)

First such application on 511 Collaborative efforts marketing efforts (logo in

exchange for services) 99% parked 1 hour before race began Rental Car Center Displays Marketing (511 on information brochures)

Highway Advisory Radio may not work (frequency conflicts)

ITS elements are good tools but cannot replace experienced judgment

Dedicated Project Manager Involve public safety/emergency personnel early on Begin PR and media campaign early Conduct regularly scheduled meetings and debriefings

with all public and private partners Collect data for evaluation

―Video and traffic volumes Plan a post-event meeting with all partners to review

what worked, what didn’t, and what to improve

Phoenix International Raceway Phoenix International Raceway (PIR)(PIR)

Traffic ManagementTraffic Management