SunGuide SM Software Development Project Release 3.0 Design Review May 2-3, 2007

1. SunGuideSM Software Development ProjectRelease 3.0 Design ReviewMay 2-3, 2007

2. Agenda Design Review

3. Introductions Design Review

4. Agenda Design Review

5. Meeting Objectives • Requirements: • Provide a high level review • Provide SwRI’s interpretation (via a design) of the requirements • Design • High level architectural overview • Operator actions and reactions • Prototype screens / reports • Not an objective: • Revise requirements Design Review

6. Release 3.0 Development Activities Design Review

7. SRS Discussion • SwRI’s interpretation of FDOT’s requirements • FDOT “system” requirements assigned as “FEAT” requirements • SwRI “derived” requirements listed as “SUB” requirements • Document contains requirements from < R3.0 • The text of “FEAT” requirements is contractually limited (i.e. do not edit) Design Review

8. Agenda Design Review

9. Variable Speed Limit Signs (VSLs) • Using TSS data as a basis, recommendations for new speed limits will be “displayed” (prompted) to the user • “Thresholds” will be configurable by the system administrator • Will require user interaction to be displayed • Messages will go through MAS to VSL devices • VSLs will be displayed on the map • Any changes will be logged Design Review

10. VSL Requirements • List of links monitored by a VSL configured in Admin Editor • Each VSL may have a different recommended speed limit associated to it • Minimum speed and maximum occupancy thresholds also specified per VSL Design Review

11. VSL Requirements – con’t • Utilizes configured DMS devices • Speed limit recommendations presented to operators for approval Design Review

12. VSL: Administrative Editor Add a VSL through the DMS configuration page Configure a VSL Associate links that are to be used to generate speed with a VSL Design Review

13. VSL: Operator GUI VSL icons will be displayed on the map (they will look different than a DMS icon) VSL Status Screen VSL Speed Recommendation (Operator verification required) Design Review

14. VSL Questions? Design Review

15. Agenda Design Review

16. American Dynamics CCTV Driver • District 5 requirement • Develop a CCTV Driver: • For a American Dynamics SpeedDome camera: RAS917-OPC Speed Dome ultra 7 version 11) • The driver will implement the communications protocol defined by American Dynamics for that camera • The driver WILL NOT implement two way communication Design Review

17. AD Driver Requirements • Control of devices will be through existing CCTV GUI in SunGuideSM Operator Map Design Review

18. Commands to be Supported • Commands: • Pan • Tilt • Zoom • Focus • Iris • Set Preset Design Review

19. AD CCTV Driver Questions? Design Review

20. Agenda Design Review

21. EH / SL Enhancements • Status Logger (performance enhancement) • Develop C# client library • Develop Java client library • Executive Handler • Convert binary EH data types to XML format • Add EH process list editing to SunGuideSM installer Design Review

22. Requirements • Status Logger serves as central logging location for applications • Executive Handler provides application control (starting, stopping, etc) Design Review

23. Status Logger Viewer • Ability to configure SunGuideSM process log their “status” the Status Logger • Level of detail can be dynamically altered • Typically one instance of Status Logger per deployment • Note: High levels of details should not be the normal mode of operation (performance implications) Design Review

24. Executive Handler Viewer • Viewer provides various ways to observe process activity • Capabilities: • Start/stop • Alter log level Design Review

25. EH / SL Questions? Design Review

26. Agenda Design Review

27. Agenda Design Review

28. MAS: High Level Overview • Optionally combine messages in a queue (specifically Travel Time with another message) • Support “merging” and “unmerging” messages • Merged messages uses the “highest” priority from the messages that were merged Design Review

29. MAS: RequirementsYellow highlighted are new requirements • Operators merge any two messages in a device queue • The page representing the travel-time message will still continue to update without requiring operator interaction • Operator can unmerge messages; highest priority message remains on sign Design Review

30. MAS: Requirements – con’tYellow highlighted are new requirements • Existing MAS functionality preserved (priorities, editing messages, etc) Design Review

31. MAS: GUI Prototypes Selecting Message “Test Merge” and the Merge button would provide list of OTHER messages available to merge… MAS Device Queue with “New Button” Merged messages would be displayed in a “combo box” – highest priority takes precedence Design Review

32. MAS Questions? Design Review

33. Agenda Design Review

34. 511 • 511 Messages (simple view): • Floodgate • Link Condition • Travel Times • 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 • Message library management tools will be developed Design Review

35. 511: Requirements • SunGuideSM will manage a minimum of • 100 Central Florida reporting routes • 150 FIHS 511 reporting routes • 200 override messages • Clarification on adding roadways? • The SunGuideSM operator map will show 511 reporting routes • Reports (link summaries, drive time summaries, etc.) will not represented on the map Design Review

36. 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 override scenarios • Operators will be prompted to approve/override the automatically selected scenario if there is an event associated with the 511 reporting segment Design Review

37. 511: Requirements – con’t • If there is no pre-recorded .wav file for a scenario, operators will be prompted until a message is recorded • SunGuideSM will share .wav files with the Statewide 511-telephone service: • Within one minute of being recorded • According to the current (Logictree) ICD • The SunGuideSM Operator Interface will allow operators to add, remove, and preview Floodgate messages Design Review

38. 511: Requirements – con’t • SunGuideSM operators with appropriate permissions will be able to use the Admin Editor to: • record 511 scenario .wav files, and • associate the .wav file with a 511 reporting segment • SunGuideSM will be able to manages a minimum of 1000 pre-recorded .wav files Design Review

39. 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 override messages and incident link reports will have a maximum length of 60 seconds Design Review

40. 511: Requirements – con’t • The SunGuideSM Operator interface will allow operators to the current scenario/override for a 511 reporting segment. • SunGuideSM will generate three types of travel time reports: • Link Reports • Link Summaries • Drive-Time Summaries • Incident link reports, if any exist, will be included in all three types of reports • Incident link reports will be saved for management review Design Review

41. 511: Requirements – con’t • A single, concatenated .wav file will be sent to the 511 telephone system for each report • SunGuideSM will allow at most one incident link report to be associated with a 511 reporting segments • Requirements describing the format of Link Reports and Link Summaries Design Review

42. 511: Requirements – con’t • Requirements describing the format of Link Reports and Drive-Time Summaries • SunGuideSM will support two drive-time summaries – AM and PM - one of which will be active at any given time • Midnight to noon: AM • Noon to midnight: PM • The AM drive-time summary will provide drive-times to downtown Orlando • The PM drive-tie summary will provide drive-times out fro downtown Orlando Design Review

43. 511: Requirements – con’t • Requirements describing the format of Drive-Time Summaries • Are “drive-time summaries”, “drive-time comparisons”, and “summary comparisons” all the same report type? • Should Drive-Time Summaries contain scenario (travel time) information for both directions or travel time information only in one direction, and incidents in both directions? Design Review

44. 511: Requirements – con’t • The SunGuideSM Operator interface will allow operators with appropriate permissions to enable/disable “routes” within a drive-time summary • 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

45. 511: Requirements – con’t • Reports will have an “upper bound” travel time • If the actual travel time is higher than the upper bound, the upper bound will be reported • Requirements for Link Report formatting Design Review

46. 511: Requirements – con’t • Requirements for Link Report formatting Design Review

47. 511: Derived Requirements • Incident association strategy: • Closest reporting segment (by lat/lon) on the same roadway as the incident • Clarification of relationship between 511 “reports” and 511 reporting segments • Clarification of Incident Link Reports: • At most one (1) per reporting segment • Saved for management review for a configurable number of days • Reviewable from SunGuideSM Operator GUI Design Review

48. 511: Derived Requirements – con’t • Clarification of Incident Link Reports (con’t): • Incident Link Reports are associated with a 511 reporting segment, and will be considered applicable to reports that contain the reporting segment • Travel time rounding: • will be performed on the total time for a report, not on any travel times that are added into the total • Times will be rounded up or down based on the recent trend Design Review

49. 511: Derived Requirements – con’t • A scenario .wav file contains: • A description of the roadway segment, a travel time (5 mins, 10 mins, etc.), and possibly a delay. • The SunGuideSM Administrative editor will allow .wav files to be associated with roadway segments and travel times • The SunGuideSM 511 system will select the appropriate scenario .wav file for a segment based on travel times. • A text description of a scenario .wav file will be derived from the file name and associated segment Design Review

50. Design: GUI • GUI • The GUI will provide a status manager that will allow an operator to manage the current state of the 511 system. • The GUI will allow an operator to create new .wav sound files to be used to override the default auto-generated travel time files, or to supplement the auto-generated files with incident information • The GUI will allow an operator to create floodgate messages that can be used to override large parts of the 511 system allowing important information to replace standard messages. Design Review