1 / 42

SunGuide SM Software Development Project Status Meeting October 13, 2004

SunGuide SM Software Development Project Status Meeting October 13, 2004. Agenda. Introductions. Agenda. License Updates. SwRI / FDOT Sublicense License executed before the contract started. TxDOT informed SwRI on January 22, 2004 that TransGuide software was on “hold”.

jaime-britt
Download Presentation

SunGuide SM Software Development Project Status Meeting October 13, 2004

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 October 13, 2004

  2. Agenda SunGuide Status Meeting

  3. Introductions SunGuide Status Meeting

  4. Agenda SunGuide Status Meeting

  5. License Updates • SwRI / FDOT Sublicense • License executed before the contract started. • TxDOT informed SwRI on January 22, 2004 that TransGuide software was on “hold”. • License amended on April 12, 2004 (to support District 2 and name change) • For a FDOT / TxDOT partnership to occur two things are needed: • MOU: • FDOT provided TxDOT with comments and legal opinion on March 2, 2004 • TxDOT Software License (solves TransGuide license issue) • TxDOT provided FDOT with a license on June 30, 2004 (included previous FDOT requests for content). • FDOT signed license on August 10, 2004. • TxDOT acknowledged the receiving of the FDOT signed license on August 23, 2004. • TxDOT signed license on August 30, 2004 and sent to FDOT on September 20, 2003. • FDOT Requested TransGuide software on October 4, 2004. SunGuide Status Meeting

  6. 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 and October 7, 2004. • 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. SunGuide Status Meeting

  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 issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, 2004. • GDT License: System Planning Office and Office of Information Systems are finalizing the license agreement on September 14, 2004. SunGuide Status Meeting

  8. Agenda SunGuide Status Meeting

  9. Reports by Deployment and Possible Integration Schedule • District 4 • District 6 • MDX • District 7 • District 1 • District 2 • District 5 • District 3 • Turnpike Enterprise SunGuide Status Meeting

  10. Agenda SunGuide Status Meeting

  11. Project Web Site http://sunguide.datasys.swri.edu SunGuide Status Meeting

  12. Release-Oriented Development Approach SunGuide Status Meeting

  13. Project Management: PM / Meetings / Reviews Process documents Interface Control Documents (ICDs) Core software framework: Database User administration Executive handler Status logger User interface Map Data Bus DMS: General Subsystem NTCIP Florida MIB driver Mark IV version 2.5 driver Status of Release 1 Activities SunGuide Status Meeting

  14. CCTV Control: General Subsystem NTCIP 1205 driver Video Switching General Subsystem IP Video switching driver Video Wall General Subsystem Barco/Argus video wall driver Traffic Detection, driver for: General Subsystem Bitrans B238-I4 driver RTMS (EIS and Wavetronix) driver Status of Release 1 Activities - continued SunGuide Status Meeting

  15. Incident Management: GUI Subsystem TIM coordination Training: Training Plan Classes being adjusted Material being developed Testing Integration testing Document development Documents: Software User’s Manual (SUM Version Description Document (VDD) Software Design Document (SDD) Status of Release 1 Activities - continued SunGuide Status Meeting

  16. Ramp Metering: Design activities initiated Initial GUI design completed High level design completed Emergency Evacuation: Requirements refined and provided to FDOT Design initiated Data Archive Requirements refined Design initiated Web Server Requirements refined Design initiated HAR Requirements refined Design initiated Center-to-Center Requirements refined Design initiated RWIS Requirements refined Design initiated Inventory and Maintenance Requirements to be refined Optional Service: iFlorida Data Collection Process (DCP) Status of Release 2 Activities SunGuide Status Meeting

  17. Development Activity • Current major development efforts are focused on: • RTMS Driver (EIS and Wavetronix support) • Map link editor (more later) • User preference editor (more later) • Barco / Argus Video Wall Interface (more later) • IP Video Switching and Snapshots • Other project activities: • Integration • Testing • Documentation (lots of effort here) SunGuide Status Meeting

  18. Map Link Editor • Objective: • Provide an interactive tool to create links to display real-time traffic conditions (from TSS) • Approach: • A “restricted” GUI to edit the links • Background map can be displayed • Tool creates a XML file of the “speed layer” of the map • User specifies: • Points along a line to draw the link • Add highway symbols (e.g. Interstate shield) – shields are “dynamic” (not bit maps) SunGuide Status Meeting

  19. Map Link Editor: Example Screen SunGuide Status Meeting

  20. User Preference Editor • Objective: • Provide the user with a mechanism to change the “look and feel” of the GUI • Approach: • Allow a user to set and save preferences • Preferences are saved to database • User preferences are loaded when user logs in SunGuide Status Meeting

  21. User Preference Editor:Example Screens SunGuide Status Meeting

  22. User Preference Editor:Example Screens SunGuide Status Meeting

  23. Barco / Argus Video Wall • Initial switching being performed using: • Apollo API: 1.6 Beta Service Release 2 • “Official” release of Service Release 2 by mid-October (per Barco) • Current issues: • Cannot determine what video is on a viewer: on startup or when the geometry is refreshed, the video wall GUI will display no sources showing as connected (supposed to be fixed by Barco) • When a layout is activated, takes 3 seconds to respond: GUI has a built in delay to “wait” SunGuide Status Meeting

  24. Barco / Argus Video Wall: Example Screens SunGuide Status Meeting

  25. Deployment Challenges / Issues • Vicon Camera: • Protocol issue: • Vicon is using NTCIP 1205 V01.07, July 12 1999 • SunGuideSM uses NTCIP 1205 V01.08 Amendment 1 v08, August 2004 • Vicon commitment to update: • Letter to FDOT (James Bitting) dated September30, 2004 • Signed by Vice President of Sales: John Whiteman, Jr. • Existing cameras will need to be updated: • District 4 • SwRI SunGuide Status Meeting

  26. Functional Threads SunGuide Status Meeting

  27. Deliverable Status • SwRI waiting for FDOT comments: • Software Integration Case Procedures • Future documents to be provided by SwRI: • SwRI will update the ConOps document and resend to FDOT • Software User’s Manual • Version Description Document • Software Design Document All documents delivered to FDOT are available on the project web site. SunGuide Status Meeting

  28. Cost Status • Release 1: • Budget amount: $3,863,374 • As of 9/24/04, ~$3,040,000 has been expended • Release 2: • Budget amount: $2,568,339 • As of 9/24/04, ~$199,000 has been expended • Cost reductions (funds back to FDOT): • Eliminating DTS Efforts: $75,009.71 • Combining 2a and 2b: $61,676.09 (this includes a “training adjustment” to add classes) SunGuide Status Meeting

  29. Spending Curve SunGuide Status Meeting

  30. Schedule Status • Current areas of concern: • Documents: • None • Software: • None • Baseline software (TransGuide component) SunGuide Status Meeting

  31. Schedule Status – continuedLast Reporting Period SunGuide Status Meeting

  32. Schedule Status - continuedCurrent Reporting Period SunGuide Status Meeting

  33. Schedule Status - continued • Integration: • Proceeding well • Continuing long term “endurance” testing • “Factory” Acceptance Testing: • Tentatively November 17-19 in San Antonio • Future status meetings that need to be scheduled: • November 9, 2004 • December 8, 2004 (“short” meeting in Jacksonville) • Future reviews that need to be scheduled: • Release 2 Software Design Review: needs to occur before December 10, 2004 (might be conducted with NetMeeting or WebEx). SunGuide Status Meeting

  34. Action Items SunGuide Status Meeting

  35. Action Items - continued SunGuide Status Meeting

  36. Agenda SunGuide Status Meeting

  37. John Bonds Presentation SunGuide Status Meeting

  38. Agenda SunGuide Status Meeting

  39. Agenda SunGuide Status Meeting

  40. Milestone Demonstration SunGuide Status Meeting

  41. Agenda SunGuide Status Meeting

  42. Action Item Recap SunGuide Status Meeting

More Related