1 / 39

SunGuide TM Software Development Project Release 4.0 Kick-off Meeting October 15, 2007

SunGuide TM Software Development Project Release 4.0 Kick-off Meeting October 15, 2007. Agenda. Introductions. Agenda. Meeting Objectives. Provide overview of: Development Team Software Architecture Components being implemented Schedule Not an objective: Discuss specific design details.

gareth-kaufman
Download Presentation

SunGuide TM Software Development Project Release 4.0 Kick-off Meeting October 15, 2007

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. SunGuideTM Software Development ProjectRelease 4.0 Kick-off MeetingOctober 15, 2007

  2. Agenda Release 4.0 Kickoff Meeting

  3. Introductions Release 4.0 Kickoff Meeting

  4. Agenda Release 4.0 Kickoff Meeting

  5. Meeting Objectives • Provide overview of: • Development Team • Software Architecture • Components being implemented • Schedule • Not an objective: • Discuss specific design details Release 4.0 Kickoff Meeting

  6. Release 4.0 Development Activities(includes 3.1 Managed Lane activities) Release 4.0 Kickoff Meeting

  7. Agenda Release 4.0 Kickoff Meeting

  8. Project Team Release 4.0 Kickoff Meeting

  9. Agenda Release 4.0 Kickoff Meeting

  10. What is the Data Fusion Effort(From the FDOT FLATIS 511 DFS Specification) Release 4.0 Kickoff Meeting

  11. Release 4.0 Development Activities Release 4.0 Kickoff Meeting

  12. SunGuide Modifications / Data Fusion: GUI / Map • Floodgate Message Editor • Reports Query & Display • Updated TSS Link Data & Editor • Event Management: • SAE J2540: Local phrase to code mapping • Duplicate/Conflicting event resolution • External Data Edits Release 4.0 Kickoff Meeting

  13. Adding SAE J2540 to EM • EM GUI will be modified so the operator can select SAE ITIS (International Traveler Information Systems) codes • ITIS codes provide efficient “coding” for transmission to wireless devices (e.g. automobile) • 2047 “entries” (not all used) Release 4.0 Kickoff Meeting

  14. J2540: Extended Phrases • 253 Phrases Release 4.0 Kickoff Meeting

  15. SunGuide Modifications: Admin Editor • Data Fusion Configuration • Select data types to be archived • Confidence Index Value editor • TVT link configuration • Wind Gust threshold editor • SAE J2540 Phrase Mapping Support • Updated TSS Link Editing Release 4.0 Kickoff Meeting

  16. SunGuide Modifications: TSS • Add support for geographical information about links • Geographical information will be in Data Bus and published via C2C Release 4.0 Kickoff Meeting

  17. Reporting Subsystem • New Data Fusion reports Release 4.0 Kickoff Meeting

  18. C2C Plugin Tasks • Updated C2C Link and Node data • New C2C Travel Time data type • New C2C Floodgate Message data type • New C2C Event data type using SAE J2540 • New C2C Location Table data type using FDOT-provided data Release 4.0 Kickoff Meeting

  19. Data Fusion Subsystem:General Subsystem Tasks • Create a new subsystem (schemas and objects) • SunGuide event and travel time retrieval • Weather information retrieval (NWS RSS feeds) • District EOC data retrieval • Strategic Intermodal System data retrieval convert to Location table • New handlers for new weather and event data sources (4 handlers) • FDOT Location table format, parsing and storage • Input data sanity checking • Metadata and data source support • Performance monitoring and status reporting Release 4.0 Kickoff Meeting

  20. Data Fusion Subsystem:Data Fusion Engine Tasks • External weather data • External TSS and TVT data • FHP CAD data • District EOC data • FDOT Location Table data • Fused event information • Data archiving Release 4.0 Kickoff Meeting

  21. Data Fusion Subsystem:Database Tasks • Fused event tables • Location data tables • New data archiving tables • Update tables for Data Fusion Support • Develop scripts for installation upgrades • Generate new DBDD Release 4.0 Kickoff Meeting

  22. Agenda Release 4.0 Kickoff Meeting

  23. Agenda Release 4.0 Kickoff Meeting

  24. Travel Time Modifications Overview • The FDOT CO is planning to deploy an LPR system along Interstate 10 around the Tallahassee area in early 2008. The LPR system will collect probe data for the SunGuide Software System to calculate travel times and post on Dynamic Message Signs (DMS). • The enhancement of existing TvT subsystem to include the message template consists of two phases with different destinations. This requirement stems from the SunGuide Footprint issue #51 and 224, and SwRI will implement this as enhancement. • Travel time calculation will allow probe based and station based calculation for a single segment. • Add capability for SunGuide to acquire data from AVI and LPR devices. Release 4.0 Kickoff Meeting

  25. Travel Time: Major Activities • Least squares trending analysis: involves changing the structure of TVT to now store past travel times and perform computations. • Allowing 5 alternate routes and doing comparisons of travel times on routes to determine the message: this involves storing alternate route messages (involved extensive database and schema changes).  The upper/lower bounds also has alternate route messages.  • Probe fusion: • AVI and LPR drivers • Dynamic link redefinition Release 4.0 Kickoff Meeting

  26. Modifications to Travel Time Subsystem • Functionality: • Allow grouped TvT tags • Alternate routes • Formatting message based on sign characteristics • Calculate delay time and allow use in messages • Display travel times on GUI • Least-squares trending • Support for either probe or station based computation for a single segment • Limit Travel time to single source of data • Display Multiple times on GUI • GUI Alert for no data Release 4.0 Kickoff Meeting

  27. Modifications to Travel Time Subsystem – con’t • Specific changes: • Database Modifications • Existing schema Modifications • Add type of link to TSS (AVL, LPR, or other detector): • Limit travel time links to one type of detection link • Allow multiple links to be defined for each travel time segment (mark one as primary) • Modify database tables to store links differently • Change schema structure o Change admin editor for setting up TvT links Release 4.0 Kickoff Meeting

  28. Probe Fusion Driver • General capabilities: • Configure system parameters • Archive tag read data • Tag Matching/Filtering • Fusion aspect • Dynamic link redefinition Release 4.0 Kickoff Meeting

  29. Probe Fusion Driver – con’t • Probe Fusion Input Driver (a driver to TSS) • Driver will “pair up” reads to determine travel times • Travel times will be published to Data Bus (which TvT can then access for generating messages) • AVI Drivers: • TransCore Allegro IT2020 • Sirit Identity Flex Title 21 • LPR Drivers: • PIPS P357 Video Processor • I-10 Tallahassee [TBD] • Note: SunGuide will talk to the above devices using a TCP/IP socket (implies terminal server connection) Release 4.0 Kickoff Meeting

  30. Probe Fusion Driver – con’t • TSS Modifications: • Add ability to store number of vehicles • Add new device types • Add notification of no data Release 4.0 Kickoff Meeting

  31. Agenda Release 4.0 Kickoff Meeting

  32. ATIS Coordination Tasks • Coordination with Districts • 12 meetings (teleconference) • Action item follow-up • ATIS Contractor Coordination meetings: • C2C Interface management: • 6 one hour teleconferences • 6 one day meetings in Florida • Action item follow-up • Additional “general” teleconferences: • 12 two hour teleconference • Action item follow-up • 6 one day meetings in Florida Release 4.0 Kickoff Meeting

  33. Documentation • Documents to be updated: • Software Requirements Specification (SRS) • Software Design Document (SDD) • Interface Control Documents (ICDs) • Version Description Document (VDD): • Release 4.0 specific implementation notes as appropriate • Software User’s Manual (SUM) • Database Design Document (DBDD) • Software Integration Plan (SIP) • Software Integration Case Procedures (SICP) • Administrator training material • Other: • Rational RequisitePro (requirements) Database Release 4.0 Kickoff Meeting

  34. Factory Acceptance Testing (FAT) • Steps: • Functional Configuration Audit (FCA) • Test Readiness Review (TRR) • FAT Execution: • April 7-11, 2008 in San Antonio (dates will be solidified by January 15, 2008 • Software will be installed at TERL for IV&V and deployed to existing RTMCs after the IV&V Release 4.0 Kickoff Meeting

  35. Deployments Planned • Deployment to existing installations (dates can be adjusted): • D1 • D2 • D3 • D4 • D5 • D6 • D7 • TERL • Considerations • TVT usable on installation • DFS coordinated with Statewide ATIS Release 4.0 Kickoff Meeting

  36. Agenda Release 4.0 Kickoff Meeting

  37. Schedule • Important dates: • Design Reviews: • Design Reviews: • In person design reviews (Orlando): • Travel Time Nov 6-7 • Data Fusion Nov 7-8 • Follow-up (teleconference): • Travel Time Dec 11 • Data Fusion Dec 13 • FAT: April 7-11, 2008 – SwRI, San Antonio • IV&V: May 5-9, 2008 – TERL, Tallahassee • Post-development dates: • Deployment: • Districts (order TBD): May 2008 • Coordinated with Statewide ATIS deployment Release 4.0 Kickoff Meeting

  38. Agenda Release 4.0 Kickoff Meeting

  39. Discussion ? Release 4.0 Kickoff Meeting

More Related