Slide 1

SunGuide SM Software Development Project Release 3.0 Design Review May 2-3, 2007 Slide 2 May 2-3, 2007Design Review 2 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 3 May 2-3, 2007Design Review 3 Introductions Slide 4 May 2-3, 2007Design Review 4 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 5 May 2-3, 2007Design Review 5 Meeting Objectives Requirements: Provide a high level review Provide SwRIs interpretation (via a design) of the requirements Design High level architectural overview Operator actions and reactions Prototype screens / reports Not an objective: Revise requirements Slide 6 May 2-3, 2007Design Review 6 Release 3.0 Development Activities Slide 7 May 2-3, 2007Design Review 7 SRS Discussion SwRIs interpretation of FDOTs 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) Slide 8 May 2-3, 2007Design Review 8 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 9 May 2-3, 2007Design 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 Slide 10 May 2-3, 2007Design 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 Slide 11 May 2-3, 2007Design Review 11 VSL Requirements cont Utilizes configured DMS devices Speed limit recommendations presented to operators for approval Slide 12 May 2-3, 2007Design 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 Slide 13 May 2-3, 2007Design 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) Slide 14 May 2-3, 2007Design Review 14 VSL Questions? Slide 15 May 2-3, 2007Design Review 15 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 16 May 2-3, 2007Design 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 Slide 17 May 2-3, 2007Design Review 17 AD Driver Requirements Control of devices will be through existing CCTV GUI in SunGuide SM Operator Map Slide 18 May 2-3, 2007Design Review 18 Commands to be Supported Commands: Pan Tilt Zoom Focus Iris Set Preset Slide 19 May 2-3, 2007Design Review 19 AD CCTV Driver Questions? Slide 20 May 2-3, 2007Design Review 20 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 21 May 2-3, 2007Design 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 SunGuide SM installer Slide 22 May 2-3, 2007Design Review 22 Requirements Status Logger serves as central logging location for applications Executive Handler provides application control (starting, stopping, etc) Slide 23 May 2-3, 2007Design Review 23 Status Logger Viewer Ability to configure SunGuide SM 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) Slide 24 May 2-3, 2007Design Review 24 Executive Handler Viewer Viewer provides various ways to observe process activity Capabilities: Start/stop Alter log level Slide 25 May 2-3, 2007Design Review 25 EH / SL Questions? Slide 26 May 2-3, 2007Design Review 26 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 27 May 2-3, 2007Design Review 27 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 28 May 2-3, 2007Design 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 Slide 29 May 2-3, 2007Design Review 29 MAS: Requirements Yellow 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 Slide 30 May 2-3, 2007Design Review 30 MAS: Requirements cont Yellow highlighted are new requirements Existing MAS functionality preserved (priorities, editing messages, etc) Slide 31 May 2-3, 2007Design Review 31 MAS: GUI Prototypes MAS Device Queue with New Button Selecting Message Test Merge and the Merge button would provide list of OTHER messages available to merge Merged messages would be displayed in a combo box highest priority takes precedence Slide 32 May 2-3, 2007Design Review 32 MAS Questions? Slide 33 May 2-3, 2007Design Review 33 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 34 May 2-3, 2007Design 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 Slide 35 May 2-3, 2007Design Review 35 511: Requirements SunGuide SM will manage a minimum of 100 Central Florida reporting routes 150 FIHS 511 reporting routes 200 override messages Clarification on adding roadways? The SunGuide SM operator map will show 511 reporting routes Reports (link summaries, drive time summaries, etc.) will not represented on the map Slide 36 May 2-3, 2007Design Review 36 511: Requirements cont Scenarios are composed of pre-recorded.wav files SunGuide SM 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 Slide 37 May 2-3, 2007Design Review 37 511: Requirements cont If there is no pre-recorded.wav file for a scenario, operators will be prompted until a message is recorded SunGuide SM will share.wav files with the Statewide 511- telephone service: Within one minute of being recorded According to the current (Logictree) ICD The SunGuide SM Operator Interface will allow operators to add, remove, and preview Floodgate messages Slide 38 May 2-3, 2007Design Review 38 511: Requirements cont SunGuide SM 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 SunGuide SM will be able to manages a minimum of 1000 pre-recorded.wav files Slide 39 May 2-3, 2007Design Review 39 511: Requirements cont SunGuide SM 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 Slide 40 May 2-3, 2007Design Review 40 511: Requirements cont The SunGuide SM Operator interface will allow operators to the current scenario/override for a 511 reporting segment. SunGuide SM 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 Slide 41 May 2-3, 2007Design Review 41 511: Requirements cont A single, concatenated.wav file will be sent to the 511 telephone system for each report SunGuide SM 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 Slide 42 May 2-3, 2007Design Review 42 511: Requirements cont Requirements describing the format of Link Reports and Drive-Time Summaries SunGuide SM 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 Slide 43 May 2-3, 2007Design Review 43 511: Requirements cont 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? Slide 44 May 2-3, 2007Design Review 44 511: Requirements cont The SunGuide SM 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 Slide 45 May 2-3, 2007Design Review 45 511: Requirements cont 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 Slide 46 May 2-3, 2007Design Review 46 511: Requirements cont Requirements for Link Report formatting Slide 47 May 2-3, 2007Design 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 SunGuide SM Operator GUI Slide 48 May 2-3, 2007Design Review 48 511: Derived Requirements cont Clarification of Incident Link Reports (cont): 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 Slide 49 May 2-3, 2007Design Review 49 511: Derived Requirements cont A scenario.wav file contains: A description of the roadway segment, a travel time (5 mins, 10 mins, etc.), and possibly a delay. The SunGuide SM Administrative editor will allow.wav files to be associated with roadway segments and travel times The SunGuide SM 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 Slide 50 May 2-3, 2007Design 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. Slide 51 May 2-3, 2007Design Review 51 Design: Subsystem and Driver Subsystem The subsystem will be responsible for generation of default travel time message based on current driving conditions and the assembly of summary information based on recorded incident messages. The subsystem is responsible for the distribution of approved.wav files to the LogicTree system. Driver There will be no drivers associated with the 511 Subsystem Slide 52 May 2-3, 2007Design Review 52 Design Use Cases: Create Override Message The operator selects to record a new override message. The system allows the user to record the new message. The operator then selects to override an existing message with the new message and selects which message to override. The system checks for approval of the override and if approved then pushes then new override message to the correct locations on the LogicTree system. Slide 53 May 2-3, 2007Design Review 53 Design Use Cases: Create Incident Message The operator selects to record a new incident message. The system allows the user to record the new message. The operator then selects to add the incident to an existing message and selects the message to which the incident message is added. The system checks for approval of the addition and if approved modifies dependent messages and then pushes the new messages to the correct locations on the LogicTree system. Slide 54 May 2-3, 2007Design Review 54 Design Use Cases: Create New Default Message The TvT subsystem indicates to the system that travel time data has changed. The system generates new messages based on the new travel time data and modifies dependent messages based on new information. The system then pushes the new messages to the correct locations on the LogicTree system. Slide 55 May 2-3, 2007Design Review 55 Design Use Cases: Start Subsystem The operator selects to start the system. The system requests subscription to the TvT Subsystem. Slide 56 May 2-3, 2007Design Review 56 Design Use Cases: Create Floodgate Message The operator selects to record a new floodgate message. The system allows the user to record the new message. The operator then selects the level of the floodgate system to which the new message applies. The system checks for approval of the floodgate message and if approved then pushes then new floodgate message to the correct location on the LogicTree system. Slide 57 May 2-3, 2007Design Review 57 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 58 May 2-3, 2007Design Review 58 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 59 May 2-3, 2007Design Review 59 511: GUI Mockups: Drive Time Summary Left side provides list of routes. Clicking a route name will select that route and any activities on the right side panel apply to that route Right side allows for management of the selected route. User can use Record/Play/Save buttons to record, play and save a message creating a new override message Slide 60 May 2-3, 2007Design Review 60 511: GUI Mockups: Drive Time Summary cont The override message can be deleted by clicking the delete button on its entry in the table Incidents are not manageable from here but by clicking the Associated Segment button for that incident, the user is taken to the Reporting Segment page with that segment selected, where it can be managed. Slide 61 May 2-3, 2007Design Review 61 511: GUI Mockups: Drive Time Summary cont Each applicable incident can be played by pressing the play button for it in the table Each incident has a button that will open the EM module and display information about the events that the incident is associated with. The default message currently in use can be listened to by pressing the play button on its entry in the table. Slide 62 May 2-3, 2007Design Review 62 511: GUI Mockups cont Link Summaries Works virtually identically to the Drive-Time-Summary-Left Page On right side, instead of selecting routes, a link is selected for management on the right side. Slide 63 May 2-3, 2007Design Review 63 511: GUI Mockups cont Reporting Segments Works the same as Drive Time Summary page except: Reporting segments are selected on the left side Allows the recording of either override and incident messages. Each segment will have up to one of each. The incident message for the segment CAN be deleted here. Slide 64 May 2-3, 2007Design Review 64 511: GUI Mockups cont Floodgate Same as Drive Time Summary page Selecting a floodgate level allows for recording a message for each of the possible entries at that level. This is reflected in the drop down box for that level when selecting the floodgate name Slide 65 May 2-3, 2007Design Review 65 511: Administrative Editor Record WAV Files Newly recorded files are placed in the waiting Available.wav Files queue Slide 66 May 2-3, 2007Design Review 66 511: Administrative Editor Assign WAV Files Unassigned wav files recorded in the Record Wav Files page appear in the Available.wav Files list. They also appear in the drop down boxes used to assign a message. They are removed from the drop down boxes and the list when they are assigned. The Lower and Upper bounds determine the number of slots in the table of assignments. Users select what they are assigning to with the drop down boxes above the tables. Slide 67 May 2-3, 2007Design Review 67 511: Administrative Editor Drive Time Comparison Add Used to add/remove/order the segments in a drive time route. Associated.wav files list is the list of assigned wav files and is not editable here Slide 68 May 2-3, 2007Design Review 68 511: Administrative Editor Drive Time Comparisons Allows the selection of which routes are in the comparison, and the order they appear in both for the morning and the evening. Slide 69 May 2-3, 2007Design Review 69 511: Administrative Editor Link Support Report Add Allows for the addition of segments to the link summary. Associated.wav files list is the list of assigned wav files and is not editable here. Slide 70 May 2-3, 2007Design Review 70 511: Administrative Editor Link Summary Reports Allows for the creation of new Link Summaries Slide 71 May 2-3, 2007Design Review 71 511: Administrative Editor Link Report Add Allow for the creation of editing of the parameters needed to describe the particular report from the reporting segment in question. Associated.wav files list is the list of assigned wav files and is not editable here. Slide 72 May 2-3, 2007Design Review 72 511 Questions? Slide 73 May 2-3, 2007Design Review 73 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 74 May 2-3, 2007Design Review 74 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 75 May 2-3, 2007Design Review 75 Web Server Regions will be configurable by the administrator Many configurable parameters Map features will include: Traffic information Cameras DMSs Abnormal road conditions Alerts Event Icons All monitored facilities (roadways, ramps, etc) Statewide traffic monitoring sites (as icons) Color-coded roadways Road segments with no data available (if no data is available for that segment) Legend for all colors and icons Slide 76 May 2-3, 2007Design Review 76 Web Server: continued Popups Roadway link travel conditions Current event report (from event icon) Links to Other Web Sites (all configurable) All metro, regional web sites 511 Help page Email to webmaster/customer support Miscellaneous Information Emergency information banner for large/serious conditions Weather information Road closures Major events Construction 511 Logo/Banner/Promotional text Slide 77 May 2-3, 2007Design Review 77 Web Server: Data Sources The web server will be provided data from the Center-to-Center interface Allows regional web servers to be deployed Data in the C2C can come from SunGuide SM or other sources Slide 78 May 2-3, 2007Design Review 78 Web Server: Requirements Yellow highlighted are new requirements Web server shall support the display of snapshots from the C2C interface Web server will designed for fast loads (not a lot of active content to be downloaded) Web site will be designed so that all web links will be relative to the top level name (URL). On pages that list links, these will be configurable by the administrator Slide 79 May 2-3, 2007Design Review 79 Web Server: Requirements cont Yellow highlighted are new requirements Data source will be C2C Icons will be FDOT selectable (easy to change) ADA compliance will be based on iFlorida efforts Typical links (e.g. webmaster) will be provided Pages will not be deeply nested (i.e. easy to get to data) Jargon will not be used (i.e. easy to understand text) Slide 80 May 2-3, 2007Design Review 80 Web Server: Requirements cont Yellow highlighted are new requirements Easy access to regions will be provided Links to various Florida (FDOT and others) will be provided Absence of data will be noted Colors will be used to discriminate roadway conditions Construction and incident information available via C2C will be displayed (implies TMC must maintain this data) Weather data displayed will be limited to RWIS sensor data (for Release 3.0) Slide 81 May 2-3, 2007Design Review 81 Web Server: Requirements cont Yellow highlighted are new requirements Travel times from C2C will be displayed Icons will be easily edited / modified (i.e. no code changes) Web server will be Microsoft IIS compatible Map base will be Google (no map customization will be possible) Easy access to metro areas will be provided via drop downs Tabs will be used to simplify access to various data Slide 82 May 2-3, 2007Design Review 82 Web Server: Requirements cont Yellow highlighted are new requirements The map data will be continuously updated (as soon as it is received from C2C) Pages will auto refresh in an administrator configurable amount of time 511 travel time data will be presented Floodgate message capability will be provided (which can be edited by a SunGuide SM operator with appropriate permissions) Slide 83 May 2-3, 2007Design Review 83 Web Server: Derived Requirements Site will be based on Microsoft IIS and HTML Snapshots will be provided by the C2C interface CCTV control will be provided by the SunGuide SM Operator GUI Based on District 5 and CO direction shape files will NOT be the basis for the map (implies Dynamo will not be used for the web server) Data to be displayed includes DMS, CCTV snapshots, Travel Times, HAR, link speeds and travel times Slide 84 May 2-3, 2007Design Review 84 Web Server: Derived Requirements cont Administrator configurable icons will be used Configuration file will be used to alter web content Data to be displayed: DMS RWIS Speed (link and travel time) Incident Data Snapshots Slide 85 May 2-3, 2007Design Review 85 Base Map Design Decisions Base Map: drive the look and feel Alternatives examined: Pen and ink (aka crayon) approach using Dynamo base map data MapPoint (local version, utilize images) Google Maps or Maptuit (hosted maps) Hosted map issues: The map server is NOT resident at FDOT Hosted map solution for TMC operations not acceptable Hosted map solution for public web site is acceptable (because if the Internet is down the location of the map server is immaterial) Slide 86 May 2-3, 2007Design Review 86 Base Map Design Decisions cont FDOT directed SwRI on April 24, 2007 to use Google Maps for the Release 3.0 web site Comments: FDOT felt that if Google wanted to start charging a fee that FDOT was in a good negotiating position SwRI will put all ITS data in an overlay that is displayed on top of the base map Excellent look and feel will be achieved in a presentation that most users will be used to Slide 87 May 2-3, 2007Design Review 87 Web Server Input The design of the web server was limited until the map selection was provided Design team looking for input (following slides will be used to gather data): What do you like? What do you not like? Remember that the requirements specify WHAT needs to be displayed Web site has ADA requirements Slide 88 May 2-3, 2007Design Review 88 Existing iFlorida Web Site (we can go live to the site if desired) What do you like? What do you not like? Notice ADA compliant text along the bottom http://www.fl511.com.com/ Slide 89 May 2-3, 2007Design Review 89 Existing District 2 Web Site (we can go live to the site if desired) What do you like? What do you not like? http://www.jax511.com/ Slide 90 May 2-3, 2007Design Review 90 Existing District 4 Web Site (we can go live to the site if desired) What do you like? What do you not like? http://www.smartsunguide.com/ Slide 91 May 2-3, 2007Design Review 91 Other sites? http://www.chart.state.md.us/http://www.dfwtraffic.org/ Slide 92 May 2-3, 2007Design Review 92 Other sites? http://trafficinfo.lacity.org/ http://traffic.511.org Slide 93 May 2-3, 2007Design Review 93 Web Server: High Level Design Windows web service Service will include C2C data acquisition application: Connects to C2C infrastructure for data and updates Roadway links based on SunGuide links Base map is Google Maps Traffic information (icons & road segments) on the map will be layered on top of the map Slide 94 May 2-3, 2007Design Review 94 Web Server: High Level Design Cont Map features will include: Traffic information Cameras DMSs Abnormal road conditions Alerts Event Icons All monitored facilities (roadways, ramps, etc) Color-coded roadways Road segments with no data available (if no data is available for that segment) Legend for all colors and icons Slide 95 May 2-3, 2007Design Review 95 Web Server: High Level Design Cont Development of the web site will follow the DOT Internet Guidelines with the following exceptions: FDOT approved template for web pages The standard FDOT banner Limiting the width of the pages to 600 pixels Using the default background color Using the default font Will not be placing text by links that cause another browser window open stating that this link will open in another browser Slide 96 May 2-3, 2007Design Review 96 Web Server Questions? Slide 97 May 2-3, 2007Design Review 97 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 98 May 2-3, 2007Design Review 98 Operational Data Store ODS : A database repository for generating reports contained in the iFlorida CFDW SDD (needed by the iFlorida FOT) The repository maintains three years of data Different than the SunGuide SM Data Archive (flat file based) Reports Traffic Detector Data Tables Toll Tag (Link) Reader Data Tables Travel Time Data Tables Summary Count Tabulations by Detector Traffic Volume Graphs by Detector Summary Count Tabulations by Segment Traffic Volume Graphs by Segment, Spot Speed Tabulations by Detector Traffic Speed Graphs by Detector Average Speed Tabulation by Segment Traffic Speed Graphs by Segment Daily Summary of Suspect Data Typical Volumes by Detector Summary Report Tabulations by RWIS 511 Messages and Traffic Conditions, Post-Incident Analysis Daily Incident Report Traveler Information Web Site Usage Slide 99 May 2-3, 2007Design Review 99 ODS Requirements Flexible: add devices, links, etc. without data loss Notify operations when data not available Based on data in SunGuide SM Data Bus Slide 100 May 2-3, 2007Design Review 100 ODS Requirements cont Reports based on iFlorida CFDW SDD Data time synchronized by NTP server Interface documented in ICD Notify operator / error log when SunGuide SM software not operational Slide 101 May 2-3, 2007Design Review 101 ODS Requirements cont ODS stores raw traffic data For two weeks ODS stores summary traffic data 1 minute rollups 15 minute rollups (Hourly rollups) For three years Slide 102 May 2-3, 2007Design Review 102 ODS Requirements cont Report parameter selection by drop down, calendar controls, etc. Message logs Generate logs Consistent error format Indicate data availability Slide 103 May 2-3, 2007Design Review 103 Combined Reporting Concept Motivation Requirements review identified common reports Common interface Common GUI User presented with report selection Report parameter input Reporting subsystem Crystal Report Template Retrieves data SunGuide SM Database ODS Formats report Data archive writes ODS tables CSV archive file Slide 104 May 2-3, 2007Design Review 104 SunGuide Reporting Subsystem (iFlorida Reports) SunGuide EM/RS reports (from R2.2 or R3.0): Traffic Detector Data Tables ( SunGuide 3.0 Traffic Flow Monthly report ) Travel Time Data Tables ( SunGuide 3.0 Traffic Flow Monthly report ) Toll Tag (Link) Reader Data Tables Post-Incident Analysis ( Existing SunGuide 2.2 Event Management Reports ) Daily Incident Report ( Existing SunGuide 2.2 Event Management Reports ) Reports being added based on iFlorida needs: Summary Count Tabulations by Detector Station Traffic Volume Graphs by Detector Station Summary Count Tabulations by Segment Traffic Volume Graphs by Segment Spot Speed Tabulations by Detector Station Traffic Speed Graphs by Detector Station Average Speed Tabulation by Segment Traffic Speed Graphs by Segment Summary Report Tabulations by RWIS Station Daily Summary of Suspect Data Typical Volumes by Detector Station 511 Messages and Traffic Condition Traveler Information Web Site Usage Slide 105 May 2-3, 2007Design Review 105 ODS: Design Goals Design and develop ODS database structures in order to store a historical repository of: Weather Reporting data Traffic Travel Time 511 Reporting Design and develop ODS data migration scripts for migrating SunGuide data into the ODS structures. Traffic and Weather data from SunGuide will be parsed and migrated into the ODS Database where it will be used for report generation. Slide 106 May 2-3, 2007Design Review 106 ODS Data Storage Provide long-term and short-term ODS data purging capabilities. The following are examples of the types of data that will be purged and the frequency: Disaggregated (raw) data (up to 90 days) Raw traffic data and Action Logs (up to 90 days) Synthesized data (3 years) Incident summaries (up to 120 days) Provide additional data processing functionalities such as ODS database backup and recovery, data transformation and aggregation (i.e., average travel time, average travel speed and typical volumes), and travel time roll-ups. Slide 107 May 2-3, 2007Design Review 107 ODS Architecture Slide 108 May 2-3, 2007Design Review 108 Report Prototypes Design and develop Traffic Counts, RWIS Weather, 511 Reporting, and Travel Time Reports and Graphs from the ODS. The following are examples of the types of reports that will be generated from historical ODS data (sample reports will be provided in upcoming slides: Weather Reports Traffic Reports Travel Time Reports Slide 109 May 2-3, 2007Design Review 109 Weather Reports: Temporal Report to view the changes over time of various weather variables that are affecting a particular station Slide 110 May 2-3, 2007Design Review 110 Weather Reports: Spatial A complete listing of stations within the reporting area for a specific time period. This allows for either the current values or a point in history to be reviewed to determine what the conditions were around the region. Slide 111 May 2-3, 2007Design Review 111 Traffic Reports: Summary Count Tabulation by Detector Station These tabular reports will comprise traffic count summaries by direction and lane. The following 6 options will be available: Following slides show several examples Slide 112 May 2-3, 2007Design Review 112 Traffic Reports: Summary Count Tabulation by Detector Station cont Slide 113 May 2-3, 2007Design Review 113 Traffic Reports: Summary Count Tabulation by Detector Station cont Slide 114 May 2-3, 2007Design Review 114 Traffic Reports: Traffic Volumes Graphs by Detector Station Graphs will show traffic volume summary data, optionally by direction and lane. The following graphs will be available: Each graph comes in six versions: (1) with or without lane counts shown; and (2) including one direction, the other, or both. Examples of the graphs are shown in the following slides Slide 115 May 2-3, 2007Design Review 115 Traffic Reports: Traffic Volumes Graphs by Detector Station cont Slide 116 May 2-3, 2007Design Review 116 Traffic Reports: Traffic Volumes Graphs by Detector Station cont Slide 117 May 2-3, 2007Design Review 117 Traffic Reports: Summary Count Tabulations by Segment Hourly traffic count summaries by direction and by lane. It may comprise tables for successive detector locations within the roadway segment. Slide 118 May 2-3, 2007Design Review 118 Traffic Reports: Traffic Volume Graphs by Segment Hourly traffic volume graphs will be available for each station in the segment, optionally subdivided by lane and by direction, as in the following examples: Slide 119 May 2-3, 2007Design Review 119 Traffic Reports: Traffic Volume Graphs by Segment cont Slide 120 May 2-3, 2007Design Review 120 Traffic Reports: Spot Speed Tabulations by Detector Station These tabular reports will include traffic speed summaries by direction. The following options will be available: Slide 121 May 2-3, 2007Design Review 121 Traffic Reports: Spot Speed Tabulations by Detector Station cont Slide 122 May 2-3, 2007Design Review 122 Traffic Reports: Traffic Speed Graphs by Detector Station Graphs will comprise traffic speed summaries, optionally by direction. Each graph comes in three versions, including one direction, the other, or both. Slide 123 May 2-3, 2007Design Review 123 Traffic Reports: Traffic Speed Graphs by Detector Station Slide 124 May 2-3, 2007Design Review 124 Traffic Reports: Average Speed Tabulation by Segment These tables will comprise average traffic speed summaries, by direction and lane. Each table includes lane and directional data. Slide 125 May 2-3, 2007Design Review 125 Traffic Reports: Traffic Speed Graphs by Segment These graphs will comprise average speed summaries, optionally by direction. Each graph comes in three versions: including one direction, the other, or both. Slide 126 May 2-3, 2007Design Review 126 Travel Time Reports: Travel Time Summary Page For any reader station, a summary table will show the most recently available average speed, drive time, link delay, and link status. Note that positive and negative directions indicate the orientation of the road segment. Slide 127 May 2-3, 2007Design Review 127 Travel Time Reports: Detail Page If the user clicks on a particular link ID, a full data table shall open for that link, showing the average speed, link journey time and link delay for each direction, for all the time periods that were reported over the past 60 minutes (configurable: within the range 15 minutes to 2 hours). The most recent data will be at the top of the table. Older data will be viewable by scrolling down the page. Slide 128 May 2-3, 2007Design Review 128 Daily Summary of Suspect Data This report will be a daily summary of suspect detector data that lists the faulty data values by station within roadway segment Slide 129 May 2-3, 2007Design Review 129 511 Messages and Traffic Conditions 511 Messages / Travel Times Summary Report Calendar controls for date range selection Drop-down box to select a roadway link The report will display Summary of average travel times over the reporting period Both directions of travel shall be presented. The names of the 511 message played for that link during that time shall also be presented Slide 130 May 2-3, 2007Design Review 130 511 Messages / Travel Time Report Slide 131 May 2-3, 2007Design Review 131 Typical Volumes by Detector Station Operator Enter year in future Select month of year Select days of week Enter growth factor Validate days (for which there is data) to be included in report For month / days of week requested will include By hour Minimum, average, and maximum volumes Slide 132 May 2-3, 2007Design Review 132 Traveler Information Website Usage Monthly summary report Distinct hosts requesting data Pages viewed By day of week pages served Peak day and pages served Summary by week Content determined by final web page design Slide 133 May 2-3, 2007Design Review 133 ODS Questions? Slide 134 May 2-3, 2007Design Review 134 Agenda TimeItemLead May 2, 2007 8:30 8:40Introductions and Opening Remarks Tillander 8:40 8:50High Level Overview meeting objectives Heller 8:50 9:30Variable Speed Limit Signs Clauss 9:30 9:45American Dynamics CCTV Driver Clauss 9:45 10:00EH / SL Enhancements Clauss 10:00 10:20Break 10:20 10:50Message Arbitration System modifications Clauss 10:50 11:30511 (includes Operator Interface improvements) Kozlovsky 11:30 1:00Lunch 1:00 2:30511 (includes Operator Interface improvements) continued Kozlovsky 2:30 2:45Break 2:45 5:00Web Server Heller May 3, 2007 8:30 11:00Operational Data Store Build Heller 11:00 11:30Open Discussion / Action Item Summary All Slide 135 May 2-3, 2007Design Review 135 Discussion ?