1. SunGuide SM Software Development Project Status Meeting (via teleconference) October 4, 2005 CDRL 1-8.3.22

2. October 4, 2005SunGuide Status Meeting (teleconference) 2 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

3. October 4, 2005SunGuide Status Meeting (teleconference) 3 Introductions

4. October 4, 2005SunGuide Status Meeting (teleconference) 4 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

5. October 4, 2005SunGuide Status Meeting (teleconference) 5 License Updates - continued FDOT / WsDOT Term of Use (TOU): –WsDOT provided FDOT with standard TOU on February 11, 2004. –FDOT provided recommendation on to WsDOT on March 13, 2004. –FDOT provided comments to the WsDOT’s Office of General Counsel’s August 21, 2004. –WsDOT began working on FDOT’s comments on August 26, 2004. –FDOT requested status on September 14, 2004, October 7, 2004 and November 5, 2004. –FDOT & WsDOT attorneys and project managers had teleconference on November 30, 2004. –New Option: WsDOT would license to “Southwest Patents” “Southwest Patents” would license to FDOT This resolves the indemnification issue July 12, 2005 Letter to Gummada Murthy, WsDOT Director, Maintenance &Operations August 1, 2005 Letter from WsDOT WSDOT provided SwRI with draft license on September 12, 2005 that had some very “tough” insurance clauses SwRI returning recommended language to WSDOT during week of October 3, 2005

6. October 4, 2005SunGuide Status Meeting (teleconference) 6 License Updates - continued FDOT / MDX Joint Program Agreement (JPA) –FDOT provided MDX with preliminary JPA on December 3, 2003. –MDX provided FDOT with draft final JPA on June 23, 2004. –FDOT worked on Locally Funded Agreement and MDX JPA. –FDOT forwarded updated JPA and sublicense to MDX on October 26, 2004 –FDOT developed a draft Software General and On-Site Support Agreement to address MDX’s software support concerns on February 11, 2005. –FDOT forwarded the updated JPA to MDX on June 7, 2005.

7. October 4, 2005SunGuide Status Meeting (teleconference) 7 License Updates - continued SwRI / FDOT / Lee County Sublicense –Lee County provided FDOT with official letter for participation on July 27, 2004 –FDOT and SwRI started documentation preparation on July 30, 2004 –SwRI provided FDOT with draft language on September 10, 2004 –FDOT forwarded sublicense to Lee County on October 26, 2004 FDOT issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, 2004. Dynamap License: –System Planning Office and Office of Information Systems are finalizing the license agreement on September 14, 2004. –Kevin Thibault approved the $130,000 GDT Procurement on October 19, 2004. –Statewide license effective on March 31, 2005.

8. October 4, 2005SunGuide Status Meeting (teleconference) 8 License Updates - continued FDOT / SwRI SunGuide License –August 12, 2005 FDOT Office of General Counsel completed preliminary review of draft final version.

9. October 4, 2005SunGuide Status Meeting (teleconference) 9 License Updates - Oracle continued Transportation Management CenterDate RequiredOIS Licensed ProcessorCurrent License Duration District 1 Ft. Myers RTMCSun 12/31/062 District 1 Sarasota RTMCSat 12/31/11 District 2 Jacksonville RTMCSun 12/31/06210/3/03 to 10/3/08 District 3 Pensacola RTMCMon 12/31/07 District 3 Tallahassee RTMCWed 12/31/08 District 4 Ft. Lauderdale RTMCMon 1/31/05210/3/03 to 10/3/08 District 4 West Palm RTMCMon 12/31/12 District 5 Orlando RTMCMon 12/31/0746/6/05 to 6/6/10 District 6 Miami RTMCThu 6/30/05210/3/03 to 10/3/08 District 7 Tampa RTMCSun 4/30/06210/3/03 to 10/3/08 Lee County RTMCSat 12/31/05 Miami-Dade Expressway RTMCThu 6/30/052 Statewide TMC & Testing LabTue 5/31/05210/3/03 to 10/3/08 Turnpike Pompano RTMCMon 12/31/12 Turnpike Turkey Lake RTMCMon 12/31/12

10. October 4, 2005SunGuide Status Meeting (teleconference) 10 License Updates – Support Agreement Software general and on-site support requirements were discussed on December 7, 2004 Draft final Software General and On-Site Support Agreement has been forwarded to SwRI on February 11, 2005 SwRI returned comments to FDOT on April 20, 2005 Summary and updated Support document were distributed on July 1, 2005 CMB approved support (for one year) on July 19, 2005

11. October 4, 2005SunGuide Status Meeting (teleconference) 11 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

12. October 4, 2005SunGuide Status Meeting (teleconference) 12 Reports by Deployment and Possible Integration Schedule District 4 District 2 District 6 MDX District 7 District 1 Lee County District 5 District 3 Turnpike Enterprise

13. October 4, 2005SunGuide Status Meeting (teleconference) 13 District 4 Schedule June 13-17, 2005: SunGuide SM software deployed at D4 TMC August 12, 2005: 45 CCTV available August 16 Software Design & Maintenance Training October 2005: Complete I/95/I595 Video Monitor System

14. October 4, 2005SunGuide Status Meeting (teleconference) 14 District 6 RTMC August 29, 2005: Milestone Demonstration November 1-3, 2005: FAT November 7-11, 2005: SunGuide SM software deployment November 15-16: Administrator and Operator Trainings November 9, 2005: I-95 Package B project completion 1 st Quarter 2006: Ramp Meters, C2C

15. October 4, 2005SunGuide Status Meeting (teleconference) 15 MDX Schedule March 2006 SunGuide SM Software Release 2 deployment at MDX March 2006 MDX TMC Operational

16. October 4, 2005SunGuide Status Meeting (teleconference) 16 District 7 RTMC June 2006Building Construction Finish SunGuide 3 rd Quarter 2006SunGuide SM Software Deployment

17. October 4, 2005SunGuide Status Meeting (teleconference) 17 District 2 RTMC Sep 6-9, 2005SunGuide Deployment Sep 6-9, 2005SunGuide SM Deployment

18. October 4, 2005SunGuide Status Meeting (teleconference) 18 District 5 RTMC FY 2004 Orlando RTMC retrofit and upgrade September 8, 2004 - iFlorida Data Collection Process December 2005 FY 2004-2005 iFlorida C2C between Districts 2 and 5

19. October 4, 2005SunGuide Status Meeting (teleconference) 19 Turnpike RTMC SunNav SM Development April-December 2004: SunNav 1.2 Release NTCIP Drivers for DMS DMS GUI Field Sorting November 2005 SunNav 2.0 (Final Completion) Web-based XML Release NTCIP Camera Driver Replication of Data Incident Management Dynamic Expansion Response Plan Upgrades 1 st Qaurter 2006 SunGuide SM Software Center-to-Center Interface Module

20. October 4, 2005SunGuide Status Meeting (teleconference) 20 District 1 May 2005 I-75 Safety Barrier System upgrade December 2006 SunGuide SM Deployment at Ft. Myers RTMC FY 2011 (2005) Sarasota RTMC

21. October 4, 2005SunGuide Status Meeting (teleconference) 21 District 3 FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMC

22. October 4, 2005SunGuide Status Meeting (teleconference) 22 Lee County Bridge Incident Management July 27, 2004 Lee County Public Works sent letter to FDOT indicating Lee County’s participation in SunGuide Software Project TBDSunGuide Software deployment

23. October 4, 2005SunGuide Status Meeting (teleconference) 23 C2C Schedule February 16, 2004SunGuide SM and C2C Project Team completed Interface Control Document (ICD) February 20, 2004SunGuide SM and C2C Project Coordination Teleconference March 9, 2004SunGuide SM & C2C Project Coordination Meeting 1 st Quarter 2006C2C deployment among Districts 4, 6, and Turnpike

24. October 4, 2005SunGuide Status Meeting (teleconference) 24 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

25. October 4, 2005SunGuide Status Meeting (teleconference) 25 Project Web Site http://sunguide.datasys.swri.edu

26. October 4, 2005SunGuide Status Meeting (teleconference) 26 Release-Oriented Development Approach

27. October 4, 2005SunGuide Status Meeting (teleconference) 27 Status of Release 1.1 Software deployed in District 4 Issues that have occurred: –Patch 4 has been released and installed to address several bugs and operational improvements requested –Meeting on October 11, 2005 to discuss additional enhancements to messaging requirements –Vicon CCTV issue (being worked by Vicon with SwRI input) Milestone Demonstration: –SunGuide R1.1 (Patch 4) was installed and demonstrated in Miami, included: DMS CCTV TSS Video Wall

28. October 4, 2005SunGuide Status Meeting (teleconference) 28 Status of Release 2 Activities Ramp Metering: –Complete: Subsystem Drivers: –TSS driver complete –RM driver complete GUI –Undergoing integration testing in San Antonio –Issues: Deployment timing (to occur in 2006): –Training –Software support

29. October 4, 2005SunGuide Status Meeting (teleconference) 29 Status of Release 2 Activities: continued Emergency Evacuation: –Design initiated –Development initiated –SwRI has determined that a number of existing web sites provide what was asked for in the SunGuide requirements –SwRI has been provided with “Evacuation Zone” shape files –SwRI is progressing along developing a web site with links to available web site –FDOT Change requested: discussed later in the presentation

30. October 4, 2005SunGuide Status Meeting (teleconference) 30 Status of Release 2 Activities: continued Emergency Evacuation: –Complete (based on FDOT’s approval of requirement modifications) Data Archive: –Complete –Integration testing Web Server: –Complete –“C2C Powered”

31. October 4, 2005SunGuide Status Meeting (teleconference) 31 Status of Release 2 Activities: continued Center-to-Center: –Complete –Integration testing –Testing labs: D4 deployment D6 deployment –Note: FDOT has recommended additional requirements that will be part of Release 2.1 (or greater) – discussion about the requirements will occur later

32. October 4, 2005SunGuide Status Meeting (teleconference) 32 Status of Release 2 Activities: continued HAR: –Complete –Integration Testing Trailblazer –Complete –Integration Testing –Need to test with a unit in the field (potential “crc” issue) Safety Barrier –Complete –Integration Testing

33. October 4, 2005SunGuide Status Meeting (teleconference) 33 Status of Release 2 Activities: continued Inventory and Maintenance (IMS): –Complete –Integration Testing

34. October 4, 2005SunGuide Status Meeting (teleconference) 34 Deliverable Status SwRI waiting for FDOT comments: –None critical Future documents to be provided by SwRI: –Updated testing documents: SIP SICP –Updated development documents: SDD SUM VDD All documents delivered to FDOT are available on the project web site. http://SunGuide.datasys.swri.edu

35. October 4, 2005SunGuide Status Meeting (teleconference) 35 Cost Status (as of 9/30/05) Note: numbers approximate due to end of FY Release 1: –Allocated: $4,335,554 –Spent: $4,316,560 Release 2: –Allocated: $2,732,303 (includes Travel Time) –Spent: $2,068,527 Deployments: –Allocated: $282,303 –Spent: $76,798 Support - on-site support and FDOT directed support (thru 6/2008): –Allocated: $548,219 –Spent: $175,045

36. October 4, 2005SunGuide Status Meeting (teleconference) 36 Spending Curves (only funds approved through June 2006)

37. October 4, 2005SunGuide Status Meeting (teleconference) 37 Schedule Status Current areas of concern: –Documents: None –Software: Ramp Meter is significantly over-budget –Contractual: ECO is in the process of being developed (authorizes 24x7 support and Travel Time subsystem) –Release 2.0: FAT Deployment To be scheduled: –Trailblazer testing (during deployment) –Ramp Metering testing (early 2006)

38. October 4, 2005SunGuide Status Meeting (teleconference) 38 Schedule Status - continued Current Reporting Period

39. October 4, 2005SunGuide Status Meeting (teleconference) 39 24x7 Support SwRI will utilize professional staff –Hector Imuguez –Brent Becker –SunGuide developers Process: –A “SunGuide” number will be provided –Either SwRI staff or answering service will answer –Issues tracked using “Footprints” Web based issue tracking, allows: –FDOT review of issues –FDOT submittal of issues Web based FAQ

40. October 4, 2005SunGuide Status Meeting (teleconference) 40 Events to Be Scheduled/Confirmed Future status meetings that need to be confirmed: –November status meeting will occur during FAT Testing: –Release 2 FAT: November 1 st, 2 nd and 3 rd Milestone Demonstrations: –Milestone Demo #3: D4, D6 and MDX Functionality of C2C, CCTV and DMS to be demonstrated

41. October 4, 2005SunGuide Status Meeting (teleconference) 41 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

42. October 4, 2005SunGuide Status Meeting (teleconference) 42 District 2 Deployment Status D2 Servers (Dell) provided to SwRI: –Database loaded and configured –Applications loaded and configured –Extensive “stress testing” of 125+ TSS sensors –American Dynamics (AD) CCTV: protocol problem that had to be resolved by AD Installation: –Started week of October 3 rd –CCTVs must be retrofited –DMS devices with IDI translators to be re-configured Training: –October 5 th and 6th

43. October 4, 2005SunGuide Status Meeting (teleconference) 43 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

44. October 4, 2005SunGuide Status Meeting (teleconference) 44 Next Three Months October 2005 –All release 2.0 development is complete: Design Code Unit Test –Integration testing –Initiate 24x7 support November: –FAT (Nov 1-3) –D6 Install / Training –Final R2.0 cleanup December –Future enhancments

45. October 4, 2005SunGuide Status Meeting (teleconference) 45 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

46. October 4, 2005SunGuide Status Meeting (teleconference) 46 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

47. October 4, 2005SunGuide Status Meeting (teleconference) 47 C2C Requirements Discussed in previous status meetings: –C2C #1: The CCTV switching function shall support the switching of C2C video sources to a Barco Video Wall. –C2C #2: SunGuide shall provide a mechanism to include DMS devices from available from the C2C interface when generating a IM response plan. –C2C #3: When SunGuide receives a DMS request from another center a configurable parameter shall be provided as to whether or not an operator has to approve the posting of the DMS request to the MAS subsystem. –C2C #4: Device requests received via the C2C interface shall be validated

48. October 4, 2005SunGuide Status Meeting (teleconference) 48 New C2C Functionality Implications Barco Wall viewing: –No SunGuide software implication –Configuration of wall (the SunGuide software retrieves the configuration for display to the operator)

49. October 4, 2005SunGuide Status Meeting (teleconference) 49 New C2C Functionality Implications – con’t DMS Devices from other centers: –Link Editor: Retrieve C2C devices (aka remote devices) Allow users to select either local or remote devices –IM: Need to subscribe for C2C DMS and HAR devices When traversing a “device link tree” will need to check status of local and remote devices (if remote is not available, skip the node but do NOT stop traversing the link tree) Commands will need to be sent to either MAS (if local devices) or to C2C (if remote devices) when the following occur: –Plan execution –Plan modification (see issue below) –Plan termination –GUI: Need to be able to distinguish between local and remote devices when a response plan is displayed

50. October 4, 2005SunGuide Status Meeting (teleconference) 50 New C2C Functionality Implications – con’t Prompt option for remote centers: –Startup up option that will require C2C DMS/HAR requests (received from other centers) to be “manually” approved –Sample screen (design not finalized):

51. October 4, 2005SunGuide Status Meeting (teleconference) 51 Road Ranger Requirements Requirements derived from “Road Ranger Procedure Draft Version 6”, Traffic Operations Driven by statewide data collection requirements Does not address data collection mechanism Interface is at computer-to-computer level

52. October 4, 2005SunGuide Status Meeting (teleconference) 52 Road Ranger Subsystem Concept D4 SMART software Wireless data receiver SunGuide Software C2C reports Data warehouse Stat Offices Others Road Ranger ICD (XML Schema)

53. October 4, 2005SunGuide Status Meeting (teleconference) 53 Road Ranger Data Requirements TM001DSunGuide shall acquire and store the following data that is collected at the beginning of the Road Ranger Service Patrol Vehicle Operator's shift: A. Date B. Shift start time C. Operator name D. Truck number E. Route F. Beginning vehicle mileage This data shall be available to support the generation of reports concerning Road Ranger operations. Traceability:A001->S006->TM001->TM001D

54. October 4, 2005SunGuide Status Meeting (teleconference) 54 Road Ranger Data Requirements TM002DThe following data collected at each stop shall be stored by SunGuide and made available for report generation and reviewing through the SunGuide GUI: A. Dispatch time B. Arrival time C. License number D. State E. Vehicle type F. Direction of travel (NB, SB, EB, WB) G. Mile marker H. How discovered I. Lanes/Shoulder blocked J. Cause for stop K. Services provided L. Depart time M. Comment card (Y/N) Traceability:A001->S006->TM001->TM002D

55. October 4, 2005SunGuide Status Meeting (teleconference) 55 Road Ranger Data Requirements TM002D1The following data collected about the vehicle type at each stop shall be stored and linked to the road ranger report containing the data: a. Passenger b. Pickup or van c. RV or bus d. Single-unit truck e. Tractor trailer f. Motorcycle g. N/A Traceability: A001->S006->TM001->TM002D- >TM002D1

56. October 4, 2005SunGuide Status Meeting (teleconference) 56 Road Ranger Data Requirements TM002D2The following data collected by the Road Ranger about how it was discovered at each stop shall be stored and linked to the road ranger report containing the data: a. Drive up b. Saw and changed route c. Road Ranger dispatch d. Notified by other Road Ranger operator/supervisor e. FHP dispatch/officer f. Other Traceability: A001->S006->TM001->TM002D->TM002D2

57. October 4, 2005SunGuide Status Meeting (teleconference) 57 Road Ranger Data Requirements TM002D3The following data collected about the cause for the stop shall be stored and linked to the road ranger report containing the data: a Accident (crash) b. Vehicle fire c. Disabled d. Abandoned e. Debris f. Pedestrian g. Other Traceability: A001->S006->TM001->TM002D->TM002D3

58. October 4, 2005SunGuide Status Meeting (teleconference) 58 Road Ranger Data Requirements TM002D4The following data collected about what services were provided at each stop shall be stored and linked to the road ranger report containing the data: a. Extinguish fire b. First aid c. Absorbent d. Remove debris e. Relocate (to safer location)(> 250 feet) f. Tire g. Fuel h. Fluids i. Mechanical j. Jump start k. Called wrecker l. Secure load m. Mobile phone call n. Directions o. Transported p. Unable to locate q. Blocked lane/traffic control r. Tagged abandoned vehicle s. Relocate vehicle from travel lane (< 250 feet) t. Notify FDOT for road repair u. Other - describe v. No service - occupied w. No service - abandoned Traceability: A001->S006->TM001->TM002D->TM002D4

59. October 4, 2005SunGuide Status Meeting (teleconference) 59 Road Ranger Data Requirements TM002D5The following data collected at the end of each road ranger shall be stored by SunGuide and linked to the road ranger reporting the data. A. Shift end time B. Ending vehicle mileage Traceability: A001->S006->TM001->TM002D- >TM002D5 TM003DThe road ranger operator data shall be collected monthly and be able to be exported to Microsoft Excel or other compatible format. Traceability: A001->S006->TM001->TM003D

60. October 4, 2005SunGuide Status Meeting (teleconference) 60 Road Ranger Data Requirements TM004DSunGuide shall support the compilation and report generation quarterly. Traceability: A001->S006->TM001->TM004D TM005DSunGuide shall store the road ranger data for a minimum of 12 months and have it available for review and report generation within 120 seconds of when a specific piece of data is requested. Traceability: A001->S006->TM001->TM005D

61. October 4, 2005SunGuide Status Meeting (teleconference) 61 Road Ranger Data Requirements TM006DSunGuide shall interface with and be able to download road ranger data collected by road rangers using a portable device. The data shall be exported from the portable device in comma delimitated text format (CSV) as a flat file and transfer shall be through a serial RS-232 interface. Traceability: A001->S006->TM001->TM006D

62. October 4, 2005SunGuide Status Meeting (teleconference) 62 Toll Tag Reader requirements Derived from: ODSI-SRS-1.2 Software Requirements Specification Version 1.2 December 7, 2004 ORLANDO-ORANGE COUNTY EXPRESSWAY AUTHORITY 525 South Magnolia Avenue Orlando, Florida 32801-4414

63. October 4, 2005SunGuide Status Meeting (teleconference) 63 Toll Tag Reader requirements TM018SunGuide shall accept data from toll tag readers and use that data to calculate the elapsed time of travel between the geographic location where the tag was initially read and the geographic location where the tag was read again. TM001SProcessing associated with collection, fusion, and dissemination of real-time toll tag data feeds shall introduce a latency of no more than two (2) minutes. TM002SSunGuide shall allow users to perform system configuration activities without introducing latency greater than 2 minutes in the real-time processing of the toll tag with the exception of the addition, removal, or modifications to AVI collection

64. October 4, 2005SunGuide Status Meeting (teleconference) 64 Toll Tag Reader requirements TM003SThe Toll Tag reader function shall be operational 99.9% the time, measured annually. TM003S1Operational shall be defined as that the system is running and that no internal errors have occurred. TM004SThe Toll Tag reader function shall report and archive speed and travel time calculations to three decimal places of precision.

65. October 4, 2005SunGuide Status Meeting (teleconference) 65 Toll Tag Reader requirements TM005SThe Toll Tag reader function shall include an AVI data collection function. TM005S1The AVI data collection system shall be able to process AVI Tag data from Amtech Type II and Type III AVI tags, including "E-PASS", “OPASS”, "SunPass", and “LeeWay” AVI Tags. TM005S2The AVI data collection system shall receive AVI Tag data from the toll collection agency AVI Data Collection Sensors, or alternatively poll the Data Collection Sensors. TM005S3Users shall be able to add AVI Data Collection Sensors to the SunGuide system. Changes will take effect when the system is restarted. TM005S4Users shall be able to modify AVI Data Collection Sensors that have already been added to the SunGuide system. Changes will take effect when the system is restarted. TM005S5The SunGuide system shall interface with Data Collection modules using a standardized interface that is documented and approved by FDOT.

66. October 4, 2005SunGuide Status Meeting (teleconference) 66 Toll Tag Reader requirements TM005S6Raw AVI data collected by SunGuide shall include the following: –Transponder ID - unique AVI tag identifier, –Reader ID - Data collection sensor that made –the tag read, –Lane ID - lane in which the tag was read, –Time stamp - time when the tag was read, –Fault Information - fault information from the –data source. TM006SThe SunGuide system shall gather external AVI collection device status data. TM006S1The SunGuide system shall determine the status of the Toll Collection Agency’s AVI Data Collection Sensors. TM006S2The AVI data collection system shall report errors in AVI Data Collection Sensors.

67. October 4, 2005SunGuide Status Meeting (teleconference) 67 Toll Tag Reader requirements TM007SSunGuide shall ensure that toll tag customers remain anonymous in the system. TM007S1The SunGuide system shall encrypt AVI transponder IDs. TM008S The Data Server shall filter out duplicate tag reads (i.e. reads of the same AVI transponder, at the same data collection site, in a given time.) TM009SSunGuide shall archive AVI Tag read data. TM009S1AVI Tag read data shall be archived with encrypted transponder IDs. TM009S2 Raw AVI Tag read data shall be archived in the same format in which it was received, except that the transponder ID shall be encrypted.

68. October 4, 2005SunGuide Status Meeting (teleconference) 68 Performance Measures Requirements Waiting on FDOT to define

69. October 4, 2005SunGuide Status Meeting (teleconference) 69 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia

70. Video sharing over the ITS WAN for C2C Communications Nick Adams - Central Office Jim Mosser - PB Farradyne

71. Status of the scope modification to accomplish video sharing?

72. Viewing other center’s video Districts will view other center’s video on their video wall via the Barco controller and Universal Decoder. No Trans-coding equipment required and video will be sent in “native format” (Originating District vendor/MPEG 2 or 4) Video will be decoded by the Barco Universal Decoder. SunGuide scope change required as mentioned above.

73. Hardware vs. Software Decoding SunGuide will route video to the Barco controller to be decoded by the Universal Decoder. If software decoding takes place at the Districts, it will occur outside SunGuide

76. Video for the State EOC 8/19/05 meeting Short term goal = “Webserver Video” Snap shots from web-servers as provided by SunGuide (or streaming video provided by District Webserver facilities) Long term goal = “Full Motion Video” EOC to look into MAN link to fiber part of ITS WAN. CO to look into “SunGuide without devices” solution.

77. QUESTIONS? Nick Adams – Central Office (850) 410-5608 or Nick.Adams@dot.state.fl.usNick.Adams@dot.state.fl.us Jim Mosser - PB Farradyne 754-224-6966 or mosser@pbworld.commosser@pbworld.com

78. October 4, 2005SunGuide Status Meeting (teleconference) 78 Agenda Time Item Lead 8:30 – 8:35IntroductionsLiang Hsia 8:35 – 8:45License Update - WsDOT TOU, MDX JPA, SwRI LicenseLiang Hsia 8:45 – 9:00TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDX Turnpike Enterprise Lee County 9:00 – 9:15Project Status ReportSteve Dellenback 9:15 – 9:20District 2 Deployment StatusSteve Dellenback 9:20 – 9:25Next Three Month PlanSteve Dellenback 9:25 – 9:30Break 9:30 – 11:10 Proposed ECO #2.0 requirements:  IM through Center-to-Center  Road Ranger  Toll Tag Reader  Performance Measures John Bonds / Liang Hsia / Steve Dellenback 11:10 – 11:25C2C Project & State EOC Communications UpdateJim Mosser 11:25 – 11:30Closing remarks, action items, and adjournLiang Hsia