SunGuide SM Software Development Project Release 3.0 Kick-off Meeting April 5, 2007

1. SunGuideSM Software Development ProjectRelease 3.0 Kick-off MeetingApril 5, 2007

2. Agenda Release 3.0 Kickoff Meeting

3. Introductions Release 3.0 Kickoff Meeting

4. Agenda Release 3.0 Kickoff Meeting

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

6. Release 3.0 Development Activities Release 3.0 Kickoff Meeting

7. Software Ownership Release 3.0 Kickoff Meeting

8. Agenda Release 3.0 Kickoff Meeting

9. Project Team Release 3.0 Kickoff Meeting

10. Agenda Release 3.0 Kickoff Meeting

11. Release 3.0 Development Activities Release 3.0 Kickoff Meeting

12. AVL • Data Driver Development; note that this provides “generic” support for any class of vehicle that has “AVL capability” that can be reported (e.g. Road Ranger, Maintenance Vehicle, etc.): • D4 Tablet • XML Interface (based on D7’s efforts) • Subsystem Development • Design new database tables • Subscribe for RR location data from RR subsystem • Subscribe for AVL location data from External Data driver • Publish location update data to subscribers • Store location update data to database • Develop queries for retrieving vehicle track records • Develop geo-location queries for geo-fence violations Release 3.0 Kickoff Meeting

13. AVL: continued • GUI Development • Develop vehicle icon selector • Develop geo-fence creation and editing functionality • Develop vehicle status and position updates for display • Develop vehicle list, summary, and detail dialogs • Develop “Find Vehicle on Map” functionality • Develop “breadcrumb track” data retrieval and display • Develop Admin Editor screen for add and deleting tracked vehicles • Develop Admin Editor screen for maintaining AVL data source locations Release 3.0 Kickoff Meeting

14. Event Management • Migrating Release 2.2.0 to “SunGuideSM Compliant”; implies building an “EM Subsystem” that is compliant to the SunGuideSM Architecture Guidelines • EM will be based on the requirements used to build Release 2.2.0 • Release 2.2.0 had two methods of “event management”: • HTML GUI that supports single incident management • Tabular GUI that supports multiple “events” • Features will be combined into a SINGLE GUI and termed “event management” Release 3.0 Kickoff Meeting

15. Event Management: continued • Manage events and EM user permissions • Users may add, modify, delete events • Users may associate related events, contacts • Activate and deactivate response plans • Send DMS, HAR, remote messages to MAS as recommended • Send recommended email messages • Process event data subscriptions • GUI enables input for Road Ranger performed activities Release 3.0 Kickoff Meeting

16. Event Management:Response Plan Generation • “Old” Incident Management subsystem is migrating to a “Response Plan Generator” (i.e. all incident/event management will be combined in the EM subsystem) • Generate response plans • Messages generated as specified by: • Message templates • Abbreviations • Device linking information • Event parameters (location, severity, etc.) • Suggest applicable email alert messages when generating a response plan • Recommend predefined response plans as appropriate • Manage message and device templates • Add, modify, and delete message templates • Manage device templates • Manage predefined plans • Add, modify, and delete predefined plans Release 3.0 Kickoff Meeting

17. Road Ranger • The RR subsystem will be used to manage, dispatch, collect data and coordinates of RR Service Patrols. • Collect and provide vehicle status information • Vehicle and beat identification • Status (e.g. patrolling assist-motorist, etc) • Collect and provide shift information • Shift start and end times. • Vehicle mileage. • Driver, vehicle, radio, and route identification Release 3.0 Kickoff Meeting

18. Road Ranger: continued • Collect and provide service call information • Dispatch, arrival, and departure times • Location • Reason for stop • Services rendered • Lane blockages • Drivers: • District 4 Tablet PC • XML based interface Release 3.0 Kickoff Meeting

19. Incident Detection • Subsystem Development • Design new database tables • Subscribe for TSS alarms from TSS • Subscribe for VisioPaD alarms from driver • Publish combined alarms to subscribers • Log alarms to database • VisioPaD Driver Development • Accept incident data from CitiLog TCP Server • Publish incident alarms to ID subsystem • GUI Development • Adapt current TSS Alarm handling to include VisioPaD alarms • Send Alarm Dismissed or Accepted message to IDS • Create and send new Event message to EM Release 3.0 Kickoff Meeting

20. Event Viewer (EV) • The EV will be a read only web site that displays the following: • Active events with a lane blockage • Active events without a lane blockage • Recently inactive events • The site will provide an "Event Details" page that will display details about a specific event record • The EV web site runs on a Windows IIS server • The EV web site will prompt for a username and password • An administrative application will also be provided to set up accounts for the web site Release 3.0 Kickoff Meeting

21. Configuration Editor • ‘config.xml’ file is the master configuration file for all SunGuideSM processes • If an error is made in editing the XML file it can cause serious side effects • Windows based editor will be developed that simplifies the editing process (and make it less error prone) • Will be rarely used Release 3.0 Kickoff Meeting

22. Operational Interface (GUI Mods) • Modify functionality to support District 5 requirements: • Record and Preview .wav files (used in conjunction with 511) • Generate alerts when incidents are “over” • Modify the display of TSS data • Provide additional capability to alter the color coding scheme used by an operator Release 3.0 Kickoff Meeting

23. 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 allow for configuration via XML file of the standard CCTV subsystem camera commands (pan, tilt, zoom, focus iris) to allow for adding other camera types via configuration file RATHER than developing custom drivers (does not work for NTCIP devices) Release 3.0 Kickoff Meeting

24. Message Arbitration System Mods • Optionally combine messages in a queue (specifically Travel Time with another message) Release 3.0 Kickoff Meeting

25. 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 Release 3.0 Kickoff Meeting

26. 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 Release 3.0 Kickoff Meeting

27. 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 create 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 Release 3.0 Kickoff Meeting

28. Web Server • “Clickable” 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 Release 3.0 Kickoff Meeting

29. 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 Release 3.0 Kickoff Meeting

30. Reporting Subsystem • Migrating Release 2.2.0 to “SunGuideSM Compliant” based on the requirements provided (i.e. same functionality) • Generate reports for the following: • Performance measures • Road Ranger activities and status • SunGuideSM software availability: • Central computer system • Information portal • Video Wall • Device availability • Camera usage • Incident management monthly report • Traveler information monthly report • Traffic flow monthly report • Vehicle and position report Release 3.0 Kickoff Meeting

31. 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 SunGuideSM “Data Archive” (flat file based) • Reports Release 3.0 Kickoff Meeting

32. Combined Reporting Concept • Motivation • Requirements review identified 7 common reports • Common interface • Common GUI • User presented with report selection • Report parameter input • Reporting subsystem • Crystal Report Template • Retrieves data • SunGuideSM Database • ODS • Formats report • Data archive writes • ODS tables • CSV archive file Release 3.0 Kickoff Meeting

33. Agenda Release 3.0 Kickoff Meeting

34. Agenda Release 3.0 Kickoff Meeting

35. Agenda Release 3.0 Kickoff Meeting

36. Factory Acceptance Testing (FAT) • Steps: • Functional Configuration Audit (FCA) • Test Readiness Review (TRR) • FAT Execution: • Planned for Aug 6-10, 2007 • Software will be installed at TERL for IV&V and deployed to existing RTMCs after the IV&V Release 3.0 Kickoff Meeting

37. Deployments Planned • Deployment to existing installations: • D2 • D4 • D5 • D6 • D7 • TERL • New Deployments • Palm Beach • Ft. Myers • One site TBD • Staff: combination of SwRI (TERL and SA) and IBI staff Release 3.0 Kickoff Meeting

38. Documentation • Documents to be updated: • Software Requirements Specification (SRS) • Software Design Document (SDD) • Interface Control Documents (ICDs) • Version Description Document (VDD) • 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 3.0 Kickoff Meeting

39. SunGuideSM Upgrades • Upgrade: • “Turning on” a new subsystem: run the installer and install just the new subsystem • Major releases can potentially require significant upgrades to many components • Installer: • No confidence in running installer in “repair mode” (little success in getting it to work in a complex environment such as SunGuideSM) • For release 3.0: SwRI will develop script to copy critical files and restore after “upgrade” Release 3.0 Kickoff Meeting

40. Agenda Release 3.0 Kickoff Meeting

41. Budget Release 3.0 Kickoff Meeting

42. Agenda Release 3.0 Kickoff Meeting

43. Schedule • Important dates: • Design Reviews: • “iFlorida” related activities: May 2-3, 2007, D5 Headquarters, Deland • EM / PM / RR / AVL: May 8-9, 2007 – D6 RTMC, Miami • FAT: Aug 6-10, 2007 – SwRI, San Antonio • IV&V: Aug 29-30, 2007 – TERL, Tallahassee • Post-development dates: • Source code, installers, documentation to FDOT by September 3, 2007 • Deployment: • Districts (order TBD): early October (note: this date could be accelerated based on the “speed” of IV&V) Release 3.0 Kickoff Meeting

44. Detailed Schedule Review Release 3.0 Kickoff Meeting

45. Agenda Release 3.0 Kickoff Meeting

46. Discussion ? Release 3.0 Kickoff Meeting