1 / 35

SunGuide TM Software Development Project Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008

SunGuide TM Software Development Project Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008. Updated: Jan 4, 2008, 11:00 am. Agenda. 2. Introductions. 3. Agenda. 4. R4.0 Data Fusion Design Follow-up Design Review. Jan 8, 2008. Meeting Objectives. Requirements and Design:

aloha
Download Presentation

SunGuide TM Software Development Project Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008

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 Data Fusion Follow-Up DR Jan. 8, 2008 Updated: Jan 4, 2008, 11:00 am

  2. Agenda 2 R4.0 Data Fusion Design Follow-up Design Review

  3. Introductions 3 R4.0 Data Fusion Design Follow-up Design Review

  4. Agenda 4 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  5. Meeting Objectives • Requirements and Design: • Review high level design • Provide clarification to SwRI’s initial design interpretation • Present revised prototype screens / reports • Not an objective: • Revise requirements 5 R4.0 Data Fusion Design Follow-up Design Review

  6. Release 4.0 Development Activities 6 R4.0 Data Fusion Design Follow-up Design Review

  7. Agenda 7 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  8. C2C XML Schema • Draft schema delivered in December • New Travel Time data type w/ Link inventory • New Floodgate data type • Second language support being added • New Traveler Event data type • Location and Roadway inventory data being added • Actual Lat/Lon instead of/in addition to Location ID • Note: Traveler Event needs to be a new event type because DF005G requires a unique icon for Traveler Events on the map. • Add Offset in miles to Incident, Closure, and Traveler Event data types 8 R4.0 Data Fusion Design Follow-up Design Review

  9. Weather Alerts • SwRI ready to evaluate Meteorlogix alert data • Issues: • SwRI needs active web service to obtain sample data • Meteorlogix needs coverage instructions and geodata for covered roads and areas 9 R4.0 Data Fusion Design Follow-up Design Review

  10. External Events • SwRI ready to accept external event data from C2C feed • SwRI can develop new “plug-in” to publish FHP data, or • SwRI can develop new SunGuide module to retrieve FHP data from FHP web service 10 R4.0 Data Fusion Design Follow-up Design Review

  11. Data To Be Fused • Weather Alerts • Fused to EM Location Code • Location Code checked against existing Events • New Traveler Event presented to operator • External Event Data (e.g. FHP CAD) • Fused to EM Location Code • Location Code checked against existing Events • Event conflict resolution dialog presented to operator 11 R4.0 Data Fusion Design Follow-up Design Review

  12. Data Fusion & FL-ATIS • Extended telecon and e-mail interaction • Resolved: • EM subsystem, GUI, and Admin changes • Location code usage • SAE code usage • Floodgate messages and GUI changes • Unresolved: • Weather alerts 12 R4.0 Data Fusion Design Follow-up Design Review

  13. Event Management Changes • Add new Alternate Route Admin dialog • Add City and Metro Area selections to EM Location Admin dialog • Update EM to include original lat/lon values in schema • Update EM to use configurable “snap-to” radius for Location code selection • Add Traveler Info event type • Add “Publish to ATIS” control • Populate existing Alternate Route ID dropdowns with values from new Alternate Route Admin dialog Note: Prototype EM GUI and Alternate Route dialog on following slides 13 R4.0 Data Fusion Design Follow-up Design Review

  14. EM Changes (cont’d) 14 R4.0 Data Fusion Design Follow-up Design Review

  15. EM Changes (cont’d) 15 R4.0 Data Fusion Design Follow-up Design Review

  16. Agenda 16 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  17. Agenda 17 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  18. Location Codes • SunGuide C2C will publish Location and Roadway inventory data based on EM Location and Roadway data • Data Fusion will use EM Location code if available, and newly available original lat/lon values 18 R4.0 Data Fusion Design Follow-up Design Review

  19. SAE Code Proposed Solution • Requirements directed a GUI based solution where “drop down” were going to be provided to allow operators to select SAE codes. • During design discussions: • It was concluded that this was requesting too much of an operator (they have enough to do) • FDOT wanted a “standard” approach to which SAE codes were selected • Resolution: • SunGuide will use “EM Event Codes” (a combination of SAE codes and FDOT codes) and not claim to adhere to a standard • A EM Event Code “translation” table will be built and event “attributes” will be automatically mapped • SunGuide will distribute EM Event Codes codes via C2C • EM Event Codes will be “transparent” to SunGuide operators R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  20. Implementation of EM Event Codes • A list of “requested” codes was generated by PBS&J (and distributed to the Districts) • District 4 provided additional requests • The following slides show the results, the column “SunGuide Support” is important to review because this could impact cost and schedule (the original approach of “drop downs” was very simple): • Easy translation: can be derived from SG data • EM Event type: data available in SG • Event attribute: data available in SG • Hard translation: algorithm to derive from SG data will need to be created • Set Event type and lane flags: data available in SG • Not found: no data available to support

  21. EM Event Codes:Translation Table for “Event Type” • Issue: “event type” can be edited by the System Administrator – should this edit screen be removed so FDOT can have the SAME event types across all SunGuide deployments? R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  22. EM Event Codes:Location and Lane Blockage • Issue: some “actual” (real) lane configurations may not be captured above R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  23. EM Event Codes:Various fields • Note: “weather conditions” can be edited by the System Administrator – this edit screen be removed by FDOT direction so FDOT can have the SAME weather conditions across all SunGuide deployments. R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  24. EM Event Codes:Proposed Additions (beyond the SAE standards) Theses codes are were requested by District 4 Codes that will not be included (no “travel time” related codes will be provided): R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  25. SAE Codes: Issues to Resolve • Does FDOT wish to “rename”? • Codes will only be included if a “mapping” can be identified between SunGuide and the codes. Some “compaction” of codes may be implemented by using “qualifiers” (e.g. “three” “center lanes blocked”) • Are the lists provided by PBS&J acceptable? • Final tables needed by end of January • Should Admin editor screens be removed? • Should the D4 proposed additions be included? • Once all of the above issues are resolved SwRI will determine the impact to the project. R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  26. Floodgate Messages • Add 2nd language support to GUI and subsystem • Add new GUI fields in support of FL-ATIS • Add Floodgate support to SunGuide plug-in and C2C • SunGuide interaction with 511 remains unchanged 26 R4.0 Data Fusion Design Follow-up Design Review

  27. Floodgate Messages (cont’d) • Alternate language selection scheme 27 R4.0 Data Fusion Design Follow-up Design Review

  28. Reports • Adding Crystal Reports 11 run-time to installer is in progress… 28 R4.0 Data Fusion Design Follow-up Design Review

  29. Agenda 29 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  30. Action Item Summary 30 R4.0 Data Fusion Design Follow-up Design Review

  31. Action Item Summary - continued 31 R4.0 Data Fusion Design Follow-up Design Review

  32. Agenda 32 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  33. Deployments / Schedule Current high-level schedule: Development to complete late March 2008 Integration complete by April 4, 2008 FAT the week of April 7, 2008 IV&V the week of May 5, 2008 Deployments starting week of May 12, 2008 (specific order will need to be verified by FDOT – 3 day installations might cover 2 deployments, assume that SunGuide is already installed) D2 (2 days) D3 (2 days) D4 (3 days) D5 (3 days) D6 (2 days) D7 (2 days) TERL (3 days) Based on the urgency of Release 3.1 (I-95 Express Lanes) the overall development schedule will be pushed 6 to 8 weeks 33 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  34. Agenda 34 R4.0 Data Fusion Design Follow-up Design Review Jan 8, 2008

  35. Discussion ? 35 R4.0 Data Fusion Design Follow-up Design Review

More Related