1. Los Angeles County Metropolitan Transportation Authority (LACMTA) Caltrans Traffic Signal Management and Surveillance System (CTNET) Presented by Metro

2. Overview Introduction –CTNET –Regional Integration of Intelligent Transportation Systems (RIITS) Available Data Data Sharing Next Steps Questions

3. Introduction Presenter –Kali Fogel, Metro, Regional Integration of Intelligent Transportation Systems (RIITS) Organizations –LACMTA also known locally as Metro –State of California, Department on Transportation (Caltrans) Developers –Jorge S. Fuentes, Caltrans –Dr. Xudong Jia, Ph.D., P.E., Metro

4. CTNET Background –Caltrans system controlling intersections at freeway crossings and off ramps. Stakeholders What is CTNET? What is RIITS? Connecting CTNET to RIITS

5. Stakeholders Metro- www.metro.netwww.metro.net RIITS- www.riits.netwww.riits.net Los Angeles County, Department of Public Works, Information Exchange Network (IEN)

6. What is CTNET physically? 170E TRFM 2070 TSCP 170E C8v4

7. CTNET field example CaltransCity of Diamond Bar City of Diamond Bar 170/2070 Controller 170/2070 Controller

8. What is RIITS?

9. Connecting CTNET to RIITS CTNET Data discussion on what is available and current limitations. CTNET Data is not TMDD 3.1 complaint but it identifies some CTNET Data available for inter-agency traffic signal coordination. CTNET Data content development began before TMDD 3.0 was available. Old field names remained but some field names were added per TMDD.

10. CTNET Data Available Congestion Detector Inventory ◦ Provide information on organization, center, contacts, and system detector inventory. Congestion Detector Dynamic ◦ Provide time stamp, detector data, and performance measures Signal Inventory ◦ Provide information on organization, center, contacts, and signal inventory. Signal Dynamic ◦ Provide time stamp, signal status, and traffic signal coordination data Current Limitations ◦ Identify future work and other limitations on current CTNET Data

11. Detector Inventory Data Information on Organization, centers and contacts based on TMDD 3.0. Included data used to: –Determine detector location –Unique detector identification –Find detector entry from AB3418E GetLongStatus message –Update detector inventory from CTNET County databases: Cabinet, Detector, and Leg attributes.

12. Detector Inventory Data Cont. Information includes direction of traffic, number of lanes of traffic and detection lane. Data type is provided to identify valid parameters and invalid data Data is provided to identify configuration of detector installation Information includes longitude and latitude for use in map display Information is updated periodically from offline databases

13. Congestion Detector Dynamic Data Includes: –Volume and Occupancy –Detector failure status –Performance Measures –Time Stamp

14. Signal Inventory Data Information on Organization, centers and contacts based on TMDD 3.0. Included data used to: ◦ Determine signal location ◦ Unique signal identification ◦ Find signal entry from AB3418 GetStatus message ◦ Find signal entry from AB3418E GetStatus8, GetLongStatus, and GetControllerTimingData messages. ◦ Update signal inventory data from CTNET County database Cabinet table and CTNET Signal Inventory database Location Table

15. Signal Inventory Data Cont. Information includes IEN signal types full actuated and semi actuated Information includes controller type for AB3418E controller timing data message decoding Information is updated periodically from offline databases

16. Signal Dynamic Data Includes data used for: ◦ Signal coordination ◦ IEN signal status ◦ Time stamp ◦ Unique signal identification IEN signal status is updated when change occurs from AB3418E status messages processed every second Signal coordination is updated either from AB3418E status messages processed every second or from online signal coordination timing database periodically

17. Current Limitations CTNET Data presented is not TMDD complaint CTNET Data is derived from AB3418 and AB3418E messages, and not NTCIP 1202 and 1210. AB3418E status is available every second Field communications uses 9600 bps closed-loop Existing detectors provide spot speed

18. Current Use Limitations Only Congestion Detector Inventory and Dynamic data can be used as historical data and storage. Inter-agency agreement is needed for Signal Dynamic data. Signal Inventory and Dynamic data is only available to local agencies.

19. RIITS Integration CTNET

20. RIITS System Integration

21. CTNET Client Detector Inventory

22. CTNET Client Detector Data

23. CTNET Client Signal Inventory

24. CTNET Client Signal Data

25. RIITS Network Routing Current Basic Path of Data Through the RIITS Network

26. Next Steps Add Time Stamp Information Congestion Detector Inventory Data Feed Congestion Detector Dynamic Data Feed Signal Inventory Data Feed Signal Dynamic Data Feed Change Windows Console Server to Windows Services Deploy CTNET

27. Questions ? Contact –Kali Fogel –Motorist Services Technical Administrator –Telephone: 213.922.2665 –Mobile: 213.361.0223 –Email: fogelk@metro.net