1 / 78

Agenda

SunGuide SM Software Development Project Status Meeting (via teleconference) October 4, 2005 CDRL 1-8.3.22. Agenda. Introductions. Agenda. License Updates - continued. FDOT / WsDOT Term of Use (TOU): WsDOT provided FDOT with standard TOU on February 11, 2004.

ginata
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SunGuideSM Software Development ProjectStatus Meeting (via teleconference)October 4, 2005CDRL 1-8.3.22

  2. Agenda SunGuide Status Meeting (teleconference)

  3. Introductions SunGuide Status Meeting (teleconference)

  4. Agenda SunGuide 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 SunGuide 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. SunGuide 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. SunGuide 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. SunGuide Status Meeting (teleconference)

  9. License Updates - Oracle continued SunGuide 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 SunGuide Status Meeting (teleconference)

  11. Agenda SunGuide 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 SunGuide Status Meeting (teleconference)

  13. District 4 Schedule • June 13-17, 2005: SunGuideSM 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 SunGuide Status Meeting (teleconference)

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

  15. MDX Schedule • March 2006 SunGuideSM Software Release 2 deployment at MDX • March 2006 MDX TMC Operational SunGuide Status Meeting (teleconference)

  16. District 7 RTMC June 2006 Building Construction Finish 3rd Quarter 2006 SunGuideSM Software Deployment SunGuide Status Meeting (teleconference)

  17. District 2 RTMC Sep 6-9, 2005 SunGuideSM Deployment SunGuide 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 SunGuide Status Meeting (teleconference)

  19. Turnpike RTMC SunNavSM 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 1st Qaurter 2006 SunGuideSM Software • Center-to-Center Interface Module SunGuide Status Meeting (teleconference)

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

  21. District 3 FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMC SunGuide 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 TBD SunGuide Software deployment SunGuide Status Meeting (teleconference)

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

  24. Agenda SunGuide Status Meeting (teleconference)

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

  26. Release-Oriented Development Approach SunGuide Status Meeting (teleconference)

  27. 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 Status of Release 1.1 SunGuide Status Meeting (teleconference)

  28. 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 Status of Release 2 Activities SunGuide Status Meeting (teleconference)

  29. 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 Status of Release 2 Activities: continued SunGuide Status Meeting (teleconference)

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

  31. 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 Status of Release 2 Activities: continued SunGuide Status Meeting (teleconference)

  32. 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 Status of Release 2 Activities: continued SunGuide Status Meeting (teleconference)

  33. Inventory and Maintenance (IMS): Complete Integration Testing Status of Release 2 Activities: continued SunGuide 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 SunGuide 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 SunGuide Status Meeting (teleconference)

  36. Spending Curves (only funds approved through June 2006) SunGuide 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) SunGuide Status Meeting (teleconference)

  38. Schedule Status - continuedCurrent Reporting Period SunGuide 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 SunGuide 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 1st, 2nd and 3rd • Milestone Demonstrations: • Milestone Demo #3: D4, D6 and MDX Functionality of C2C, CCTV and DMS to be demonstrated SunGuide Status Meeting (teleconference)

  41. Agenda SunGuide 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 3rd • CCTVs must be retrofited • DMS devices with IDI translators to be re-configured • Training: • October 5th and 6th SunGuide Status Meeting (teleconference)

  43. Agenda SunGuide 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 SunGuide Status Meeting (teleconference)

  45. Agenda SunGuide Status Meeting (teleconference)

  46. Agenda SunGuide 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 SunGuide 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) SunGuide 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 SunGuide 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): SunGuide Status Meeting (teleconference)

More Related