1. Adaptive Signal Control Technology: Bringing a Systems Approach to Implementation and Evaluation October 18, 2011 Kevin Fehon, P.E., PTOE DKS Associates

2. Overview n The past 40 years of adaptive signal systems n The last five years in the USA n Breaking out in 2011 n Bringing a structure to system selection n Performance Evaluation 2

3. First a definition n ASCT – Adaptive Signal Control Technology u Terminology adopted by FHWA u Used to refer generically to adaptive traffic signal systems u Avoids confusion with ACS-Lite

4. The past 40 years n It all started with SCATS in 1973 and SCOOT in 1975 n Two fundamentally different but practically- oriented approaches n Both widely accepted outside the USA by 1985 n Different approach attempted in USA, reflecting different administrative and economic environment 4

5. 5 SCOOT 2009

6. 6 SCATS 2009 53 Cities; 179 Signal Regions

7. 7 What has held up acceptance in the USA? n Agency capability and willingness n System performance and benefits n Lack of understanding n Cost n Availability of US-based systems

8. Growing acceptance in the USA. n ASCT is an important element of FHWA’s Every Day Counts (EDC) program n Increasing number of jurisdictions considering ASCT n Modern equipment with more processing power n New ASCT systems emerging n Still less than 1% of USA signals 8

9. US Adaptive Systems, April 2011 9

10. Systems currently available in USA n SCOOT/TACTICS n SCATS n InSync n LADOT ATSC n ACS-Lite n OPAC n KHAdence n QuicTrac n RHODES n Balance n Synchro Green n RHODES n ATMS.now n Delcan & Intellight 10

11. Introducing a structured approach to ASCT system selection 11

12. What is an appropriate definition of “adaptive”? n Many different definitions are acceptable n The definition you choose should be the one that suits your circumstances n How do you define real-time? Is it predictive or reactive or both? n What parameters are “adaptive”? 12

13. What are you trying to achieve with ASCT?

14. Different coordination strategies n Most coordination strategies can be categorized in one of the following four ways: u Pipeline along a route (arterial or within grid) u Progression in two directions along a route u Equitable service for adjacent land uses u Queue management 14

15. Non-coordination strategies n Some adaptive strategies do not involve coordination u Optimal operation of an isolated intersection u Optimal operation of a single critical intersection within a coordinated area 15

16. Why use a systematic process?

17. Why SE? n Understanding the problem n Managing risk u Projects getting bogged down with shifting requirements u Acquisitions being challenged by unsuccessful bidders/proposers/vendors u Projects not meeting agency needs n (and it is mandatory for federal-aid projects)

18. Are you fully expressing your desires? n Is ASCT really what you need? n Can you clearly document the deficiencies of your existing system that you wish to overcome with adaptive? n Can you clearly document the existing capabilities of your system that must be retained with adaptive operation? 18

19. Can you clearly verify that you got what you asked for? n Are your needs clearly expressed? n Is each need translated into a requirement n Is every requirement actually satisfying an expressed need? n How is each requirement tested, so the that the vendor can verify it is satisified? 19

20. Can you validate that you got what you needed? n Have your organization’s goals and objectives been clearly defined? n Are measures of performance clearly defined? n Can you test the operation against the measures of performance? 20

21. What is the purpose of the Model Systems Engineering Documents?

22. Provide a framework to guide agencies to the most appropriate solution n Provide sample statements that can be used in a Concept of Operation n Provide sample requirements that can be used to select/purchase/design a system n Describe appropriate verification and validation plans 22

23. How should your process work?

24. Overview n First pass in half to one day, by experienced agency staff n Identify additional information you need in order to make appropriate decisions and document the basis of those decisions 24

25. Work Flow 25

26. 26

27. What are the pitfalls of not following a structured approach?

28. Pitfalls n You don’t get the most suitable system n You may lose some capabilities n You may not get the system you want n Making a constraint a requirement at the outset distorts the outcome. You can’t quantify the trade-offs you are making 28

29. The structured approach will result in the most appropriate ASCT selection n Required capabilities will be clearly stated n Assumptions will be explicit, so requirements won’t fall through the cracks n Trade-offs to satisfy real and perceived constraints will be explicit and justified n Expectations are more likely to be met 29

30. Is it worth the effort? n Emphatically yes! n Some ASCT systems that have not fulfilled expectations are falling by the wayside n The established systems have strongly documented benefits and high B/C ratios n Much misinformation, both positive and negative 30

31. Gresham PM Peak TT (Eastbound Burnside) 405 368 424 393 349 373 314 0 100 200 300 400 500 Travel Time (sec) 1997 Free 1998 TOD 2004 Free 2004 (1998 TOD) 2004 TOD 2007 (2004 TOD) 2007 SCATS Legend

32. Evaluation techniques often hide the truth n Travel time per direction does not show system- wide effects, and confuses positive and negative impacts. n Travel time per period do not show effects of varying demand levels. n Volume-weighted, system-wide evaluation allows differentiation of conditions. 32

33. Sunnyvale: System Expansion 33

34. Questions? 34