SunGuideSunGuideSMSM Software Development Project Software Development Project
Release 3.0 Kick-off MeetingRelease 3.0 Kick-off MeetingApril 5, 2007April 5, 2007
April 5, 2007Release 3.0 Kickoff Meeting 2
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 3
Introductions
April 5, 2007Release 3.0 Kickoff Meeting 4
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 5
Meeting ObjectivesMeeting Objectives
Provide overview of:
– Development Team
– Software Architecture
– Components being implemented
– Budget
– Schedule
Not an objective:
– Discuss specific design details
April 5, 2007Release 3.0 Kickoff Meeting 6
Release 3.0 Development Release 3.0 Development ActivitiesActivities
April 5, 2007Release 3.0 Kickoff Meeting 7
Software OwnershipSoftware Ownership
April 5, 2007Release 3.0 Kickoff Meeting 8
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00
General activities:DocumentationFAT Deployments
Dellenback
3:00 – 3:15 Break
3:15 – 3:30 Budget / Schedule Dellenback
3:30 – 4:00 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 9
Project TeamProject Team
April 5, 2007Release 3.0 Kickoff Meeting 10
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 11
Release 3.0 Development Release 3.0 Development ActivitiesActivities
April 5, 2007Release 3.0 Kickoff Meeting 12
AVLAVL
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
April 5, 2007Release 3.0 Kickoff Meeting 13
AVL: continuedAVL: 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
April 5, 2007Release 3.0 Kickoff Meeting 14
Event ManagementEvent 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”
April 5, 2007Release 3.0 Kickoff Meeting 15
Event Management: continuedEvent 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
April 5, 2007Release 3.0 Kickoff Meeting 16
Event Management:Event Management:Response Plan GenerationResponse 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
April 5, 2007Release 3.0 Kickoff Meeting 17
Road RangerRoad 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
April 5, 2007Release 3.0 Kickoff Meeting 18
Road Ranger: continuedRoad 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
April 5, 2007Release 3.0 Kickoff Meeting 19
Incident DetectionIncident 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
April 5, 2007Release 3.0 Kickoff Meeting 20
Event Viewer (EV)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
April 5, 2007Release 3.0 Kickoff Meeting 21
Configuration EditorConfiguration 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
April 5, 2007Release 3.0 Kickoff Meeting 22
Operational Interface (GUI Mods)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
April 5, 2007Release 3.0 Kickoff Meeting 23
American Dynamics CCTV DriverAmerican 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)
April 5, 2007Release 3.0 Kickoff Meeting 24
Message Arbitration System ModsMessage Arbitration System Mods
Optionally combine messages in a queue (specifically Travel Time with another message)
April 5, 2007Release 3.0 Kickoff Meeting 25
EH / SL EnhancementsEH / 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
April 5, 2007Release 3.0 Kickoff Meeting 26
Variable Speed Limit Signs (VSLs)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
April 5, 2007Release 3.0 Kickoff Meeting 27
511511
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
April 5, 2007Release 3.0 Kickoff Meeting 28
Web ServerWeb 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
April 5, 2007Release 3.0 Kickoff Meeting 29
Web Server: continuedWeb 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
April 5, 2007Release 3.0 Kickoff Meeting 30
Reporting SubsystemReporting 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
April 5, 2007Release 3.0 Kickoff Meeting 31
Operational Data StoreOperational 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)
ReportsTraffic Detector Data Tables Traffic Speed Graphs by Segment
Toll Tag Reader Data Tables Daily Summary of Suspect Data
Travel Time Data Tables Typical Volumes by Detector
Summary Count Tabulations by Detector Summary Report Tabulations by RWIS
Traffic Volume Graphs by Detector Road Weather Graphical Data Reports
Summary Count Tabulations by Segment 511 Messages and Traffic Conditions
Traffic Volume Graphs by Segment Post-Incident Analysis
Spot Speed Tabulations by Detector Daily Incident Report
Traffic Speed Graphs by Detector Traveler Information Web Site Usage
Average Speed Tabulation by Segment DMS / VSL Usage
April 5, 2007Release 3.0 Kickoff Meeting 32
Combined Reporting ConceptCombined 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
Reporting / ODS GUI
Data Bus
Reporting Subsystem
Data Archive
CSV Data Archive Flat
FileSunGuide Database
Operational Data Store
April 5, 2007Release 3.0 Kickoff Meeting 33
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 34
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 35
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 36
Factory Acceptance Testing (FAT)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
April 5, 2007Release 3.0 Kickoff Meeting 37
Deployments Planned 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
April 5, 2007Release 3.0 Kickoff Meeting 38
DocumentationDocumentation
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
April 5, 2007Release 3.0 Kickoff Meeting 39
SunGuideSunGuideSMSM Upgrades 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”
April 5, 2007Release 3.0 Kickoff Meeting 40
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 41
BudgetBudget
AVL $234,792.00
Event Management $263,512.00
Reporting Subsystem $157,181.00
Road Ranger $131,023.00
Incident Detection $66,483.00
Event Viewer $49,951.00
Configuration Editor $25,005.00
Operational Interface $34,548.00
American Dynamics CCTV Driver $37,900.00
Message Arbitration System Modifications $17,444.00
EH / SL Enhancements $32,383.00
Variable Speed Limit Signs $24,574.00
511 $193,960.00
Web Server $93,111.00
Operational Data Store Build $216,587.00
FAT $55,085.00
Documentation $34,402.00
D5 Testing / Documentation / Deployment $51,133.00
Deployments $164,563.00
April 5, 2007Release 3.0 Kickoff Meeting 42
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 43
ScheduleSchedule
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)
April 5, 2007Release 3.0 Kickoff Meeting 44
Detailed Schedule ReviewDetailed Schedule Review
April 5, 2007Release 3.0 Kickoff Meeting 45
AgendaAgenda
Time Item Lead
1:00 – 1:10 Introductions and Opening Remarks Tillander
1:10 – 1:20 High Level Overview – meeting objectives Dellenback
1:20 – 1:30 Project Team Dellenback
1:30 – 2:45
High level discussion of work items:AVLEvent ManagementReporting SubsystemRoad RangerIncident DetectionEvent ViewerConfiguration EditorOperational InterfaceAmerican Dynamics CCTV DriverMessage Arbitration System modificationsEH / SL EnhancementsVariable Speed Limit Signs511Web ServerOperational Data Store Build
Heller
2:45 – 3:00 Overlap of Reporting Subsystem and Operational Data Store Heller
3:00 – 3:15 Break
3:15 – 3:30General activities:DocumentationFAT Deployments
Dellenback
3:30 – 3:45 Budget Dellenback
3:45 – 4:15 Schedule Dellenback
4:15 – 4:45 Open Discussion / Action Item Summary All
April 5, 2007Release 3.0 Kickoff Meeting 46
Discussion ?