1

TempeStreetcar

3

• Tempe is one of the highest public transit ridership centers in the region

• City circulator in one of highest employment & residential density areas in Arizona

• 190K residents; 320K daytime population

• Helps to preserve historic neighborhoods & inspires appropriate redevelopment

• Complements Orbit & bus system;rail attracts new riders

So, Why Streetcar?

Image credits: Arizona State University

• Est 1885• 72,000 Students enrolled• Over 600 acres in Tempe• Center of downtown

5

6

7Source: downtowntempe.com

• MAJOR EMPLOYERSASU, Wells Fargo, State Farm, US Airways, SRP, JP Morgan Chase, Honeywell

• EVENTS & ATTRACTIONSIronman, Rock N Roll Marathon, MLB Spring Training, Tempe Town Lake, Tempe Butte, Papago Park, Mill Ave

• Mill Avenue was named one of America’s Great Streets in 2008 by the American Planning Association

• Tempe Town Lake opened in 1999 after over 30 years of planning and coordination

• Over 2.4 million people visit the lake annually

• 1st Bike Plan in Arizona

• 217 miles of bikeways (lanes, multi-use paths, etc)

• Regional Light Rail System (2008)

• 15 arterial bus routes• 6 Orbit routes• 3 Express routes

City of Tempe: Moving People

9

The Vehicle

Manufactured by BrookvilleOut of Brookville, PA

10

Utility Relocation& CNPA

Track Construction Civil & Roadway Stops & Artwork Operations Training

Vehicle Testing Opening

2018 2019 2020 2021

Design Milestones100% Issued For Construction

May 2018 August 2018

Project Schedule

11

Latest StatusTrack Construction began November 16th!

12

Latest Status

13

Rail delivery January 2018

Each 80’ stick weighs the same as an average car at 1.5 tons each

5 sticks welded together to produce 400’ rail strings weighting 7.6 tons

14

15

Rail welding January 2018

16

17

18

19

20

Rio & AshRoundabout Construction (Feb 2020)

21

University & Ash Construction (April 2020)

22

Construction At-A-Glance

23

• Track Section

• Utility Relocation Requirements• Number and location of TPSS

• Feeder Cables

• Landscaping• Stops

• Alignment• CNPA (Concurrent Non-Project Activity)

Design Challenges

24

Single track – Apache Terminus

26

Single Track – Marina Heights Terminus

27

28

Tempe streetcar roundabout

29

Capability Needs for Day-to-Day Operation• Communications (mix of fiber, wireless,

VDSL, leased lines, none)• Controller HW/SW• Signal Timing/Transit Signal Priority• Situational Awareness

• CCTV Cameras• Real-Time Tracking

• Vehicle Detection• Streetcar Detection

“Value Engineering”

Operational Challenges

30

Tempe Streetcar CIP ProjectsSystems & Communications – AECOM Under Contract• Review streetcar 60/90/100% PSE• Coordination with VMR and BEC

• Identify system alternatives for TSP w/RTT• Evaluate signal controllers• Develop VISSIM model (Baseline/No TSP, With TSP) – Now SOP!• Develop signal timing and phasing Fiber Installation – Final Design• Install fiber along Mill/Ash downtown loop and Rio Salado

ITS Infrastructure – In Progress• TSP w/RTT System (EMTRAC)

• Signal Controllers (McCain ATC eX2 w/D4)• CCTV Cameras, Video Detection

31

EMTRAC – Operation

The EMTRAC system tracks vehicle positions and progress as they travel through their routes. As vehicles move along these routes, they enter pre-defined virtual detection zones and transmit data via secure 900 MHz FHSS radio to appropriate wayside equipment.

32

EMTRAC – Virtual DetectionThe EMTRAC system eliminates the need for embedded loops in the trackway and reduces the need for other wayside detection equipment. This is done by creating virtual detection zones, which are defined by GPS coordinates and allow system data to be sent only when pre-defined conditions (such as position, speed and heading) are met.

33

EMTRAC – Detection ZonesVirtual detection zones have many uses, can be placed anywhere, can be any size, can be used as often as desired, and can be easily moved or changed based on current needs to optimize the system’s operation.

34

EMTRAC – Onboard Equipment

• One Vehicle Computer Unit (VCU) and RF/GPS antenna per cab• VCU requires power, speed sensor, ignition sensor, battery SOC, silent alarm, etc.• Antenna is mounted on roof

35

EMTRAC – Wayside Equipment

• Priority Detector in cabinet (Tx/Rx data, communicates with signal controller)• Omni-directional antenna (mounted at 15’ or higher near signal cabinet)• Existing IR EVP detectors can be wired in and accepted as inputs

36

EMTRAC – Downtown DemoDemo installation includes 6 wayside installations along the TSC alignment and four onboard installations to test out the TSP w/RTT and EVP capabilities. Instrumented vehicles include TFMR E276, 2 Orbit Circulator Buses and a COT Public Works vehicle.

37

EMTRAC FunctionsTransit Signal Priority (TSP)• Priority request monitoring and logging• Traffic signal phase logging

Real-Time Tracking (RTT)• Speed• Latitude and longitude

• BearingBattery State of Charge (SOC) Monitoring and LoggingData ArchivingSilent AlarmVehicle/Station Estimated Time of Arrival (ETA)Communications Backhaul on Tempe Streetcar Alignment

Dual-Alignment Operation

39

Off-wire segments

40

41

OESSTraction Battery SOC vs Time & Location

42

Standard TSP FunctionsEarly Green Return – Terminate conflicting phases early to return to transit phaseGreen Extension – Extend transit phase to provide longer green window for passageLeft Turn Swapping – Move leading left turn to lagging (one cycle only) for earlier return to transit phaseQueue Jump – Provide ~5 sec early green for transit phase to get Streetcar in intersection firstPhase/Ped Omit – Omit phase or ped calls for earlier return to transit phasePhase Insertion – Provide dedicated phases in the ring to serve transit vehicles

43

Selected TSP CapabilitiesEarly Green Return – Terminate conflicting phases early to return to transit phaseGreen Extension – Extend transit phase to provide longer green window for passageLeft Turn Swapping – Move leading left turn to lagging (one cycle only) for earlier return to transit phase

D4 Features• Multiple priority levels• Boolean logic for custom programming• Peer-to-Peer communications using both local and upstream state• Adaptive arrival times compensate for varying station dwell times

44

VISSIM ModellingData• Existing signal timing and phasing, along with streetcar adjustments• Opening day volumes• Pedestrian, bus and LRT traffic are included• In progress/planned development impacts• Streetcar ridership estimates, by station/area• Streetcar headway and layover requirementsThree Time Periods Modelled• AM peak, Mid-Day and PM peakTSP Levels• Baseline – signals optimized, but no TSP• Basic TSP – basic green extension/return• Optimized TSP – advanced TSP options, including upstream P2P data

45

VISSIM Videos Multiple videos were produced from the VISSIM Models

To review intersection operations in detail To show the operations of the streetcar on the network as a whole

46

VISSIM Modelling

47

VISSIM Modelling

48

VISSIM Modelling

49

VISSIM Modelling

50

VISSIM Modelling

51

VISSIM Modelling

52

VISSIM Modelling

53

VISSIM ModellingThe VISSIM model was used to evaluate the ability of the designed system to meet each agency’s operational goals:• VM – 10 minute headways; layover requirements for operators• COT – minimizing delay for all roadway users

VM’s goals were met in nearly every instance across all three time periods modelled with minimal impact to intersection LOS, but only under the Optimized TSP scenario.

The simulation modelling results clearly demonstrated the benefits and the need for a comprehensive TSP solution. The model also provided useful information about upstream peers and detection zone placement TSP configuration.

54

Next Steps• Create D4 controller databases and evaluate in test cabinets• Install EMTRAC onboard equipment• Integrate and test Brookville and EMTRAC onboard systems• Install EMTRAC wayside equipment• Install McCain/D4 controllers• Install EMTRAC Central Monitor software• Test communications link between Tempe TMC and VM OCC• Monitor and test deployed signal timing/TSP and adjust as

necessary• System Extension

55

• Partnership with Valley Metro, Tempe & Mesa

• Investigate and identify high-capacity rail corridors

• Expand on potential extensions identified in 2014

Extension Study

56

Extension Study

Questions?ValleyMetro.org/TempeStreetcar

David Lucas

City of Tempe ITS(480) 350-8666

David_Lucas@tempe.gov

Tempe Streetcar

59

Typical (Shared Thru-Lanes, Center Running, Side Running)

Streetcar shares the Inside-Thru lane in both directions (for single-track sections in 1 direction only).All Transit Priority tools are applicable here (not all sites have protected LT’s).

1. Apache / Rural Rd2. Apache / McAllister3. Apache / Normal Rd4. Apache / College5. Apache / Forrest6. Apache / Mill7. Mill / 7th, 6th, 5th, 4th St8. Rio Salado / Hayden, Salt, MH West9. Ash / 5th St

Apache….

Mill….

60

Mill / Rio SaladoStreetcar travels in multiple lanes in different directions.All Transit Priority tools are applicable here (depending on site-specific phasing differences).Half-Grand Union requires dedicated train phase (service window) during the cycle.Need to determine Hierarchy of importance for various movements…..?Route or Switch input can extend the options for concurrent service (NB right turn….)

61

Rio Salado / Streetcar Crossover & Ped3-phase controller: Autos, Streetcar, Ped XingGreen Extension, Early Return are applicable here.WB autos service as an overlap to the Train movement.Shared track WB dictates reverse-run logic (to prevent stopping EB autos for WB Streetcar move).

62

Things to Consider….1. Use of the EMTRAC system inputs versus Peer-to-Peer inputs.

§ Point inputs can have travel time assignments in D4 for predictive logic.§ Peer to Peer can account for in-between intersections in D4 for predictive logic.

2. Use Aggressive priority feature of D4 at sites that are off-wire.§ This tool attempts to clear the transit vehicle with Priority first.§ If predictive algorithm realizes it can’t be done with Priority, will trigger a preempt.

3. Route or Switch Inputs available at (Rio & Mill) for Half-Grand-Union?• Very different operation required for a NB to WB move; good to identify it.

4. Reverse Run logic operations on single-track sections (Apache, Rio) will require some Boolean Logic to accomplish.

5. What is the desired hierarchy at sites with LRT and Streetcar (or multiple streetcar) crossings?• Do we give equal priority to all moves on first-come / first-serve basis?• Do we identify the desired priority move and the other(s) serve with traffic?

6. Is Coordination or Priority more important? Where?7. Protected-Permitted Left Turn Swapping.

• Swapping not recommended due to yellow-trap concerns (Pro-Perm LT should not lag).• Is omitting an option? Do nothing with this tool at these sites?

8. Shared LT Lane Operation – Preemption to clear?• How aggressive to be in order to clear the lane and proceed the Streetcar in 1 cycle?