Presentation is loading. Please wait.

Presentation is loading. Please wait.

ITS America Annual Meeting Jane White – LA County June 4 th, 2007 Standard ATMS Interfaces – Lessons Learned Los Angeles County Regional Traffic Forum.

Similar presentations


Presentation on theme: "ITS America Annual Meeting Jane White – LA County June 4 th, 2007 Standard ATMS Interfaces – Lessons Learned Los Angeles County Regional Traffic Forum."— Presentation transcript:

1 ITS America Annual Meeting Jane White – LA County June 4 th, 2007 Standard ATMS Interfaces – Lessons Learned Los Angeles County Regional Traffic Forum Program

2 2 Los Angeles Countywide Information Exchange Network Los Angeles County Regional Traffic Forums Program Components  Traffic Signal Synchronization  Intelligent Transportation Systems (ITS)  Funding  Over $200 million since 1995  $170 million in grant funds  $30 million in matching funds provided by LA County Public Works

3 3 Los Angeles Countywide Information Exchange Network Los Angeles County Regional Traffic Forums ITS Components  Advanced Transportation Management System (ATMS)  Traffic Control Systems (TCS)  Closed Circuit Television Cameras (CCTV)  Communications System  Information Exchange Network (IEN)

4 4 Los Angeles Countywide Information Exchange Network Los Angeles County Regional Traffic Forums ITS Projects  Gateway Cities  I-105 Corridor  I-5/Telegraph Rd. Corridor  I-710/Atlantic Blvd. Corridor  San Gabriel Valley  Pomona Valley  San Gabriel Valley  South Bay

5 5 Los Angeles Countywide Information Exchange Network Gateway Cities I-105 Corridor (Delcan)  Traffic Control Systems  Norwalk (ICONS – Installation Underway)  South Gate (ICONS – In Negotiations)  Fiber-Optic Communications  Imperial Hwy. (Paramount Ave. to Bellflower Blvd.)  Imperial Hwy. (Firestone Blvd. to Carmenita Rd.)  Firestone Blvd. (Stewart/Gray Rd. to Imperial Hwy.)  CCTV Cameras (21 Locations)  On Firestone Blvd., Imperial Hwy., & Rosecrans Ave.

6 6 Los Angeles Countywide Information Exchange Network Gateway Cities I-5/Telegraph Rd. Corridor (Siemens)  Traffic Control Systems  Commerce (QuicNet Upgrade – In Negotiations)  Downey ( i2tms – Installation Underway)  Santa Fe Springs (including Pico Rivera & Paramount – RFP being prepared)  Fiber-Optic Communications  Telegraph Rd. (Paramount Blvd. to Carmenita Rd.)  Carmenita Rd. (Telegraph Rd. to Imperial Hwy.)  CCTV Cameras (6 Locations)  Telegraph Rd. (5 Locations)  Lakewood Blvd. at I-5 Fwy.

7 7 Los Angeles Countywide Information Exchange Network Gateway Cities I-710/Atlantic Blvd. Corridor (Siemens)  Traffic Control Systems  Vernon  Fiber-Optic Communications  Alameda St.  CCTV Cameras (6 Locations)

8 8 Los Angeles Countywide Information Exchange Network Pomona Valley (Kimley Horn)  Traffic Control Systems  Diamond Bar ( TransSuite ® )  Claremont (KITS)  La Verne (ICONS)  San Dimas (KITS)  Pomona (QuicNet – Existing)  Fiber-Optic Communications  Colima Rd. (Nogales St. to Stoner Creek Rd.)  CCTV Cameras (16 Locations)

9 9 Los Angeles Countywide Information Exchange Network San Gabriel Valley (TransCore)  Traffic Control Systems  Alhambra  Arcadia ( TransSuite ® – Installation June 2007)  Covina  Glendora  Irwindale  Pasadena ( i2tms )  Rosemead  West Covina  CCTV Cameras (8 Locations)

10 10 Los Angeles Countywide Information Exchange Network South Bay (MMA & PB Farradyne)  Traffic Control Systems  Gardena (QuicNet – Existing)  Torrance (ICONS)  Inglewood (QuicNet – Existing)  Fiber-Optic Communications  Hawthorne Blvd.  CCTV Cameras (4 Locations)

11 11 Los Angeles Countywide Information Exchange Network Los Angeles County Regional Traffic Forums Communications  Initial plan to use telephone company leased lines determined to be cost prohibitive  Switched to wireless broadband radios (currently being installed)  Backhaul via leased T1 lines

12 12 Information Exchange Network (IEN)

13 13 Los Angeles Countywide Information Exchange Network Information Exchange Network (IEN)

14 14 Los Angeles Countywide Information Exchange Network Information Exchange Network (IEN)  Enables each local Agency to operate & maintain its own TCS independently  Provides for data exchange among Agencies to enhance coordination  Ability to monitor traffic signal operations & congestion in adjacent jurisdictions  Ability to relinquish control if so desired  Enables a multi-jurisdictional coordinated response to incidents & special events

15 15 Los Angeles Countywide Information Exchange Network IEN – System Architecture (High-Level)

16 16 Los Angeles Countywide Information Exchange Network IEN – System Design  IEN system developed in late 1990s  Used then current NTCIP center-to-center standards  Based on CORBA (Common Object Request Broker Architecture)  IEN uses the TAO ORB  CORBA necessary to support once-per-second data transmissions to/from TCS

17 17 Los Angeles Countywide Information Exchange Network IEN – CDI System Interfaces Current Status  Series 2000  Pasadena (Operational)  QuicNet IV  Inglewood, West Hollywood, & Pasadena (Operational)  Glendale & Burbank  i2tms  Downey (Under Development)

18 18 Los Angeles Countywide Information Exchange Network IEN – CDI System Interfaces Current Status (cont.)  TransSuite ®  Arcadia (Installation July 2007)  Diamond Bar (Installation April 2008)  KITS  LA County (In Negotiations)  ICONS  South Gate, Torrance, La Verne, & Norwalk (In Negotiations)

19 19 Los Angeles Countywide Information Exchange Network IEN – System Interfaces Current Status (cont.)  LADOT-to-IEN XML Interface  Under development by TransCore  1-way interface that brings ATSAC data into the IEN via LADOT’s Web Services  IEN-to-LADOT Interface  Under development by LADOT staff  1-way interface that brings IEN CORBA data into ATSAC  Includes fiber-optic connection

20 20 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lessons Learned  Lesson 1 – There is no such thing (unless you have lots & lots of money)  Lesson 2 – Be willing to change & re-define  “Data” wants vs. needs vs. desires  “Frequency” wants vs. needs vs. desires  Lesson 3 – Be willing to change to keep up with current standards  Lesson 4 –Take what you can get  Lesson 5 – Let folks know what you are doing

21 21 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 1  Lesson 1 – There is no such thing (unless you have lots & lots of money)  IEN developed using CORBA  NTCIP migration to XML (“death of CORBA”)  LA County decision made to keep IEN’s CORBA-based system intact, but allow front-end XML interfaces with “translation” to CORBA  LADOT Interfaces  LADOT getting IEN data via CORBA, translating to ATSAC format  LA County getting LADOT data via XML, translating to CORBA

22 22 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 2  Lesson 2 – Be willing to change & re-define  “Data” wants vs. needs vs. desires  “Frequency” wants vs. needs vs. desires  IEN developed based on TransCore’s Series 2000 & UTCS  “Provides all data, all the time, second-by-second”  QuicNet & KITS expressed concern over communications requirements for data/frequency

23 23 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 2 (cont.)  Lesson 2 – Be willing to change & re-define  “Data” wants vs. needs vs. desires  “Frequency” wants vs. needs vs. desires  Re-visited “IEN Data List” & determined  Which elements were really needed  Which elements were needed second-by-second, cycle-by-cycle, or less  i2tms & ICONS systems closely matched revised list

24 24 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 3  Lesson 3 – Be willing to change to keep up with current standards  Original IEN CDI developed using CORBA  LADOT & Econolite wanted to use existing XML interfaces  LADOT & Econolite interfaces will be passing data via XML, with a translation to CORBA to incorporate into the IEN System

25 25 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 4  Lesson 4 – Take what you can get  Interfaces to IEN developed based on available data  Inglewood  BI Tran 200 firmware provides limited data  City communications may also be limiting  Working with BI Tran & City to replace 200 firmware & upgrade communications  LADOT  XML interface has limited data  LADOT interface will not provide the same amount of data that other systems will (e.g., detector data)

26 26 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lesson 5  Lesson 5 – Let folks know what you are doing  Current TMDD (Traffic Management Data Dictionary) did not include traffic signal data  Working with NTCIP C2C working group to ensure data that is required for the IEN is defined in latest version of TMDD

27 27 Los Angeles Countywide Information Exchange Network Standard ATMS Interfaces – Lessons Learned  Lesson 6 – Don’t Start!!  Lesson 7 – Retire!!

28 28 Los Angeles Countywide Information Exchange Network THANK YOU FOR YOUR INTEREST!! QUESTIONS??


Download ppt "ITS America Annual Meeting Jane White – LA County June 4 th, 2007 Standard ATMS Interfaces – Lessons Learned Los Angeles County Regional Traffic Forum."

Similar presentations


Ads by Google