1 / 85

Agenda

SunGuide SM Software Development Project Release 3.0 (Follow-up) Design Review iFlorida Components - May 22, 2007. Agenda. Introductions. Agenda. Meeting Objectives. Discuss: Issues raised in the original Design Review that were not addressed

prince
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 ProjectRelease 3.0 (Follow-up) Design ReviewiFlorida Components - May 22, 2007

  2. Agenda Design Review (iFlorida Components Follow-up)

  3. Introductions Design Review (iFlorida Components Follow-up)

  4. Agenda Design Review (iFlorida Components Follow-up)

  5. Meeting Objectives • Discuss: • Issues raised in the original Design Review that were not addressed • Issues that were discussed and addressed (and captured in the minutes) will not be discussed • Scope discussion: • What will be absorbed in the current effort • What needs to be deferred to future releases • Not an objective: • Revise requirements Design Review (iFlorida Components Follow-up)

  6. Release 3.0 Development Activities Design Review (iFlorida Components Follow-up)

  7. Action Items – recapSwRI AIs will be throughout slides Design Review (iFlorida Components Follow-up)

  8. Action Items – recap: con’tSwRI AIs will be throughout slides Design Review (iFlorida Components Follow-up)

  9. Operator GUI Mock-upsColor Preferences? • Which color scheme would FDOT like to see used? Traditional SunGuide Colors EM / PM Colors Design Review (iFlorida Components Follow-up)

  10. Agenda Design Review (iFlorida Components Follow-up)

  11. Variable Speed Limit Signs (VSLs) • Review of • iFlorida CRS System Design Document • iFlorida CRS User Guide / Training Manual • I-4 divided into two segments • From Exit 90 to Exit 85 (414 to Princeton) • From Exit 84 to Exit 79 (Ivanhoe to JYP) • Four groups of signs • Two east bound groups • Two west bound groups • Non-overlapping groups • Plans are based on groups of signs Design Review (iFlorida Components Follow-up)

  12. SDD Described Functionality • Heavy Traffic • Four plans; one for each segment for each direction • Recommended when occupancy exceeds 12% (settable) • Recommended when occupancy will exceed 12% • Adverse Weather • Based on adverse weather reported by Meteorlogix • Two plans, one for each segment of I-4 • Incident • Up to 22 different plans for each possible location • Invoked by phrase matching in incident description • Construction • Handled by manual posting Design Review (iFlorida Components Follow-up)

  13. VSL Questions • Recommended speeds • Maximum speed set by sign (50 or 55) • Minimum speed set for system • Speed delta for adjacent signs controlled by regulation • Heavy traffic plan • Single plan for each set of VSLs • I-4 VSL segments include multiple TSS detectors • Aggregate occupancy from multiple detectors? • TSS computes rolling average, is that sufficient? • Other issues • Examine status of VSL • Force normal condition, defined plan • Suspend recommendations • VSL status (active, error, failure, out of service) Design Review (iFlorida Components Follow-up)

  14. Implementation Options • Single step implementation • Each sign configurable within plan • Trigger and recovery occupancy configurable • Consistency checking intra- & inter- plan • Multiple step implementation • Each sign configurable within plan • Trigger and recovery occupancies configurable • Level of “idiot checking” • Adjacent signs within a group • Adjacent signs between groups • Trigger & recovery conflicts Design Review (iFlorida Components Follow-up)

  15. SunGuide Limitations • Will implement • Single or multiple steps • Varying level of error checking • Will not implement • Predictive occupancies • Adverse weather plans (no Meteorlogix data) • Incident based plans • Manual postings Design Review (iFlorida Components Follow-up)

  16. Admin Editor for VSL Plans • Able to define four plans with multiple steps Design Review (iFlorida Components Follow-up)

  17. VSL Recommendation • VSL recommendation for operator approval • Whole plan / no changes • Date & time stamped Design Review (iFlorida Components Follow-up)

  18. VSL: Scope Questions • Included in R3 Scope or Requirements and will be implemented: • None identified • Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule: • Multiple stepping for plans • Manage recommendations in groups • Not included in R3 Scope or Requirements and will require additional budget and/or schedule: • VSL plans for incidents, weather, construction, manual Design Review (iFlorida Components Follow-up)

  19. VSL Questions? Design Review (iFlorida Components Follow-up)

  20. Agenda Design Review (iFlorida Components Follow-up)

  21. AD CCTV Driver / EH / SL • American Dynamics CCTV Driver: • SwRI asked to investigate an “early deployment”: • driver should be ready by June 30, 2007 • Executive Handler (EH) modifications: • No issues from first design review • Status Logger modifications: • No issues from first design review Design Review (iFlorida Components Follow-up)

  22. AD/EH/SL: Scope Questions • Included in R3 Scope or Requirements and will be implemented: • None identified • Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule: • None identified • Not included in R3 Scope or Requirements and will require additional budget and/or schedule: • None identified Design Review (iFlorida Components Follow-up)

  23. AD CCTV Driver / EH / SL Questions? Design Review (iFlorida Components Follow-up)

  24. Agenda Design Review (iFlorida Components Follow-up)

  25. MAS Issues Identified • Would like to merge more than one sign at a time (current approach is to have an operator select messages on ONE sign at a time to merge) Design Review (iFlorida Components Follow-up)

  26. MAS: Scope Questions • Included in R3 Scope or Requirements and will be implemented: • None identified • Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule: • None identified • Not included in R3 Scope or Requirements and will require additional budget and/or schedule: • Merge messages on multiple signs at one time (unknown effort) Design Review (iFlorida Components Follow-up)

  27. MAS Questions? Design Review (iFlorida Components Follow-up)

  28. Agenda Design Review (iFlorida Components Follow-up)

  29. 511 • 511 Messages: • Floodgate • Link Report • Link Summary • Drive Time Comparisons • Will gather travel time information (sensor independent) from the Travel Time subsystem via the data bus • Messages will be created based on the Travel Time data • WAV files will be created in accordance with D5 “rules” (established as part of the iFlorida project) • Interface to Logictree will be developed to place WAV files on the “live” 511 telephonic system Design Review (iFlorida Components Follow-up)

  30. 511 Requirements Review • The following slides were “augmented” to highlight where issues arose during the first Design Review. • Discussion will be limited to the “underlined” comments Design Review (iFlorida Components Follow-up)

  31. 511: Requirements • SunGuideSM will manage a minimum of • 100 Central Florida reporting routes • 150 FIHS 511 reporting routes • 200 override messages • The SunGuideSM operator map will show icons representing 511 reporting segments • Reports (link summaries, drive time summaries, etc.) will not represented on the map Design Review (iFlorida Components Follow-up)

  32. 511: Requirements – con’t • Scenarios are composed of pre-recorded .wav files • SunGuideSM will automatically select and concatenate scenario .wav files based on current travel times • Operators will be allowed to enable/disable reporting of automatically selected scenarios • Operators will be prompted to approve the selected scenario, and/or record an incident message, if there is an event associated with the 511 reporting segment Design Review (iFlorida Components Follow-up)

  33. 511: Requirements – con’t • SunGuideSM will prompt operators to record an incident link report if: • A new incident is associated with the 511 reporting segment, or • An incident already associated with the reporting segment is updated • Both pre-recorded messages and incident link reports will have a maximum length of 60 seconds (any further feedback on this?) Design Review (iFlorida Components Follow-up)

  34. 511: Requirements – con’t • The SunGuideSM Operator interface will allow operators to review current scenario and incident messages for a 511 reporting segment. • SunGuideSM will generate three types of travel time reports: • Link Reports • Link Summaries • Drive-Time Comparisons • Incident link reports, if any exist, will be included in Link Reports and Link Summaries, but NOT Drive-Time Comparisons • Incident link reports will be saved for management review Design Review (iFlorida Components Follow-up)

  35. 511: Requirements – con’t • Requirements describing the format of Link Reports and Drive-Time Comparisons– These will be updated for Drive-Time Comparisons. • SunGuideSM will support drive-time comparisons between 7 points around Orlando – for example between the airport and downtown. • The SunGuideSM Administrative Editor will allow users to configure alternate routes to be reported between two destinations - for example, two routes from the airport to downtown Design Review (iFlorida Components Follow-up)

  36. 511: Requirements – con’t • Requirements describing the format of Drive-Time Comparisons – these will be changed Design Review (iFlorida Components Follow-up)

  37. 511: Requirements – con’t • The SunGuideSM Operator interface will allow operators with appropriate permissions to enable/disable automatic travel time reporting for Link Report, Link Summaries, and “routes” within a drive-time comparison • Travel times reported by 511 will be rounded to 5-minute increments: • Whether to round up/down will be determined by the trend of recent travel times. • Travel times will not be updated until the cross the next 5-minute threshold for a minimum detection period Design Review (iFlorida Components Follow-up)

  38. 511: Requirements – con’t • Reports will have a “lower bound” and an “upper bound” travel time • If the actual travel time is less than the lower bound, the lower bound will be reported • If the actual travel time is higher than the upper bound, a message indicating that the travel time is in excess of the upper bound will be reported • Requirements for Link Report formatting Design Review (iFlorida Components Follow-up)

  39. Design: 511 Segment Location • The SunGuideSM Administrative editor will have users enter segment location information: • Roadway - same roadways used for incidents) • Direction(s) - selected from the directions configured for the roadway • Start point (lat/lon) • End point (lat/lon) • Mid point (lat/lon) • This location information will be used to: • Display 511 reporting segment icons on the operator map • Associate Incidents/Events with the correct 511 reporting segment Design Review (iFlorida Components Follow-up)

  40. Design: 511 Incident/Event Association • Incidents/Events will be associated with a 511 reporting segment by: • Roadway - events will only be associated with 511 reporting segments on the same roadway • Direction(s) - events will only be associated with 511 reporting segments that contain the same direction • For example, if the reporting segment is north/south, and the event is entered as eastbound, it will not be associated • Lat/Lon – Once segments with the same roadway and direction are identified, events will be associated with the closest reporting segments by lat/lon Design Review (iFlorida Components Follow-up)

  41. Design Change: Default Incident Link Reports • The SunGuideSM Administrative editor will allow one reusable default incident link report to be recorded and associated with a 511 reporting segment • Typically, the default message will be normal travel time for the segment • The default Incident Link Report will be used automatically whenever there is no custom, operator-recorded Incident Link Report Design Review (iFlorida Components Follow-up)

  42. Design Change: Link Summaries • A Link Summary will represent travel times for an entire roadway in a single direction • For example: I4 northbound and I4 southbound would be two separate Link Summary reports • A Link Summary will include Incident Link reports for both directions. • For example, an incident on I4 northbound would be reported in both the I4 northbound and I4 southbound Link Summary reports • This is necessary because there is only one incident link report per segment, covering incidents in both directions Design Review (iFlorida Components Follow-up)

  43. Design Change: Drive-Time Comparisons • Drive-Time comparisons can be reported between up to seven configurable locations (e.g. Airport, Downtown Orlando) • The SunGuideSM Admin editor will allow users to configure: • The seven location names • Which comparisons to offer (example, from airport to downtown), • Two or more alternate “routes” for each comparison Design Review (iFlorida Components Follow-up)

  44. Design Change: Drive-Time Comparisons (con’t) • Drive-Time comparison route can include portions of one or more roadways, calculated in a single TvT route • A Drive-Time comparison may also include a configurable offset (for example +5 mins) • Incident Link reports are not included Design Review (iFlorida Components Follow-up)

  45. Design: 511 Travel Time Calculation • Travel times for a 511 report will be calculated using one or more TvT “routes”. • Link Reports – have four TvT routes • Link Summaries – one TvT route • Drive-Time Comparisons – have one TvT route per configured alternate route between destinations • Travel times are calculated separately for each report, not “built up” from smaller reports. • This is easier • Allows for greater flexibility • Should be more accurate • Avoids rounding errors Design Review (iFlorida Components Follow-up)

  46. Design Change: Disabling 511 Travel Times • The SunGuideSM Operator GUI will allow operators to with appropriate permissions to enable/disable reporting automated 511 scenarios (travel times) • Travel Times can be disabled/enabled for: • Link Reports (individual reporting segments) • Link Summaries • Individual Drive-Time Routes • If Travel Times are disabled for a Link Report, other reports that include the same reporting segment will also be disabled • Disabling Travel Times for Link Summary or Drive-Time Route affects only that individual report Design Review (iFlorida Components Follow-up)

  47. 511: GUI Mockups: Mapping Reporting Segments • A speaker icon on the map will represent the midpoint of the 511 reporting segment • Can display the ends of the reporting segment if desired (triangle icons on the mock-up) • The phone icon will change color and/or flash to indicate that there is a new/updated incident on the segment • Hovering over the phone icon will display the name of the current 511 scenario .wav file • Clicking on the phone icon will open the Segment Manager GUI Screen Design Review (iFlorida Components Follow-up)

  48. 511: GUI Mockups:Map Design Review (iFlorida Components Follow-up)

  49. 511: GUI Mockups:Link Report (Reporting Segment) • Left side lists segments • Right side allows for management of the selected segment • User can: • Review playing .wav files • Record Incident Link Report • Enable/Disable travel time reporting (if operator has sufficient permissions) Design Review (iFlorida Components Follow-up)

  50. 511: GUI Mockups – con’tLink Summaries • Left side lists summaries • Right side allows for management of the selected summary • User can: • Review playing .wav files • Delete Incident Link Reports • Enable/Disable travel time reporting (if operator has sufficient permissions) • User must go to the Reporting Segment manager to add/edit Incident Link Reports Design Review (iFlorida Components Follow-up)

More Related