Agenda

SunGuideSunGuideSMSM Software Development Project Software Development Project

Release 3.0 (Follow-up) Design ReviewRelease 3.0 (Follow-up) Design ReviewGeneral SunGuideGeneral SunGuideSMSM Components - Components -

May 31, 2007May 31, 2007

May 31, 2007Design Review (SunGuide Components Follow-up) 2

AgendaAgenda

Time Item Lead

8:00 – 8:10 Introductions and Opening Remarks Tillander

8:10 – 8:20 High Level Overview – meeting objectives Heller

8:20 – 8:30 Configuration Editor Clauss

8:30 – 8:50 Event Viewer Clauss

8:50 – 9:30 Incident Detection Clauss

9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch

1:00 – 3:00 Event Management Barbosa

3:00 – 3:15 Break

3:15 – 4:45 Reporting Barbosa

4:45 – 5:00 Open Discussion / Action Item Summary All


Introductions


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Meeting ObjectivesMeeting Objectives

Discuss:

– Issues raised in the original Design Review

– Scope discussion:

• What can be absorbed in the current effort

• What needs to be deferred to future releases

Not an objective:

– Revise requirements


Release 3.0 Development Release 3.0 Development ActivitiesActivities


Action Items – recapAction Items – recapSwRI AIs will be throughout slidesSwRI AIs will be throughout slides

Issue # Assigned To Action Item Due Date

136 CO/DistrictsProvide icon ideas (10) to be used for managed vehicle groups

137 SwRI Will Event Viewer have inactivity timeout? May 31, 2007

138 SwRISwRI will propose a pared list of browsers to be supported (tested).

May 31, 2007

139 SwRIHow does the “blocked” status of a CCTV effect the C2C interface?

May 31, 2007

140 FDOT

Should adding contacts to an agency via the Responder List also add to the ‘permanent’ list normally editable via Admin Editor? If yes, this needs to be logged to the chronology report.

141 FDOT

Manny/Corbin – Responder list - allow multiple ‘notification’ times to be specified. Need an update button to allow multiple notifications of contacts. IBI will contact Manny for further investigation.

142 SwRISwRI will propose method of logging who changed when and what files were changed

May 31, 2007

143 FDOTFDOT needs to identify data that cannot be viewed by the public using event viewer

144 FDOT Review alert processing summary table


Action Items – recap: con’tAction Items – recap: con’tSwRI AIs will be throughout slidesSwRI AIs will be throughout slides

Issue # Assigned To Action Item Due Date / Comment

145 FDOT D-4 Provide SSL license cost and information.

D4 provided: SSL certificate can be purchased from VeriSign, valid for three years at a cost of $795 total

146 FDOT Review alert processing summary table

147 FDOT Provide feedback on the aesthetics of the reports.

148 IBI Report back on issues associated with incident, head and tail.

149 FDOT D-4Develop a CONOPS regarding an incident located on both sides of a freeway.

D4 provided: a bidirectional incident ConOps is under development

150 SwRI Derive requirements for two levels of view in the Event Viewer May 24, 2007

151 SwRIResearch the integration of the AVL and RR GUI’s and propose design concept

May 31, 2007

152 SwRIRevised IDS screen to utilize description text location rather than latitude/longitude for location.

May 31, 2007

153 FDOT D4Requirement FEAT 22.3.4, needs to filter out some information to the general public. District can make their own decisions, Steve Corbin will provide suggestions.

D4 suggests removing the vehicle tag and injury information

154 FDOTGene, Trey, and Erik will review the Data Fusion requirements: C2C for Event Viewer by leveraging the ATIS data fusion requirement.


Action Items – recap: con’tAction Items – recap: con’tSwRI AIs will be throughout slidesSwRI AIs will be throughout slides

Issue # Assigned To Action Item Due Date

155 FDOT Trey will get RR trucks photo from Charlie Creel for SwRI as a reference of RR icon creation.

May 24, 2007

156 FDOT Trey will re-send Milepost Converter file (from Prof. Ken Courage) to SwRI.

May 23, 2007

157 FDOT D4, D7D4 and D7 will look into the impact of geo-fencing and truck beat assignment impact.

158 SwRI SwRI will evaluate the RR bi-directional communication. May 31, 2007

159 SwRISwRI will assess the blockage of video feed (when marked as restricted) and put into Footprints.

May 31, 2007

160 IBI Research “floating list” technology for alert message list June 15, 2007

161 SwRI / IBIUse “crash” terminology rather than “accident” throughout SunGuide application

July 1, 2007

162 SwRI / IBIDevelop recommendation on how to handle a large number of alerts (in the alert window)

May 31, 2007

163 SwRI Add “CCTV blocked flag” to the Operator map. July 1, 2007


Summary Of IssuesSummary Of Issues

“Preserve the look and feel of R2.2”– Based on SUM 2.2.2– Alert bar across the top– Alert sub-window with event list– Incorporating functionality and changes based on

May 8-9 Review

“Multi-function interface” of PM window preserved– Event list with alert sub-window– Road Rangers (with AVL)– CCTV Blocking– Audit function– Reporting


Summary Of Issues – con’tSummary Of Issues – con’t

Map window on right monitor, EM window on left– Preserved ability to place windows, SunGuide can

“remember” placement– Opening multiple EM windows presents technical

challenges, being addressed

Road Rangers with EM– Implement D4 ICD (bi-directional IP communication)– Implement D7 ICD (URL file access)

Integration of AVL with Road Rangers– Reconsidered separate subsystems– Coalesced into one

• Reduced some complexity• Introduced some complexity


Operator GUIs:Operator GUIs:FDOT Direction for Future GUIsFDOT Direction for Future GUIs

For GUIs in development for 3.0:

– Device GUIs (e.g. VSL) will be in SEPARATE windows in a “grid style”

– GUIs specifically related to “Event Management” will be in a SINGLE window with “Tabs”

– Will use the R2.2 “blue/green” color scheme IS THIS CORRECT???

D4 Comment: Will the tabs be implemented like the green menu bar in the EMPM GUI or will it simply be a collection of pages opened using IE7 tabbed browsing? Should we take the screenshot as an example or an implementation possibility? If it uses IE7 tabs, will operators need to open each tab one at a time or will all relevant tabs be opened at once automatically? What happens if an operator closes these tabs, how do they get them back, and how would they be prevented from accidentally opening the tab in another IE window?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Issues from Initial Design ReviewIssues from Initial Design Review

Logging to record file changes upon saving– User account name and timestamps– XML file contents– Previous XML file contents will be preserved

Filtering open file dialog to show XML files only

Warn users before closing file without saving


Config Editor: Scope QuestionsConfig Editor: Scope Questions

Included in R3 Scope or Requirements and will be implemented:– Filter for Open dialog– Warning message

Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule:– Logging to Status Logger and preserving previous contents

Not included in R3 Scope or Requirements and will require additional budget and/or schedule:– None identified


Config Editor: Scope QuestionsConfig Editor: 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



Configuration Editor Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break





Will Event Viewer have an inactivity timeout?

– Microsoft IIS session timeouts will serve as inactivity timeout

Internet browser derived requirement:

– FEAT22.1.3 (SV002B):The SunGuide Event Viewer Web site shall be accessible through at least the following browsers: AOL, AOL CompuServe, AOL Netscape, Open Ride, Internet Explorer, MSN Explorer, Firefox, Mozilla, Sea Monkey and Opera.

– Reworded requirement:The SunGuide Event Viewer Web site shall be accessible through at least the following browsers: Internet Explorer 6

and 7, Firefox, Opera, Netscape, and AOL.



Need permissions to restrict data displayed– Two levels of data: public, non-public view– Separate permission for viewing non-public data– FEAT22.1.1 (SV001):

SunGuide shall provide a read-only Web site application for TMC personnel that runs on Windows servers and is viewed with modern internet browsers.

– Reworded requirement:The SunGuide Event Viewer Web site shall not display identified sensitive data to restricted users (e.g. license plate information, crash data, etc).

What is the list of “sensitive” data that cannot be viewed by the public using the event viewer? (NEED BY June 15, 2007)


EV: Scope QuestionsEV: Scope Questions


Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule:– Two viewing levels for public and non-public data



Event Viewer Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break





Displaying incident detection data – On both map and EM GUI?

SwRI has CitiLog simulator– Version provided to SwRI does not

support the snapshot feature– Request FDOT help to resolve the issue

(by June 15, 2007)

Display incident alert bar on map– Conflicts with the current map

implementation– Option of using on-top window

D4 comment: There are two types of images displayed on the VisioPaD alert screen: live JPEG snapshots and a bitmap image received from VisioPaD depicting the snapshot of the incident with an arrow pointing at the stopped vehicle? The existing VisioPaD subsystem receives the name of the bitmap image file through the "TCP Server" interface, and EMPM accesses the file from the "supervisor" server on a windows file share. The live JPEGs are fetched from the supervisor from a different share, using the citilog camera id to identify the correct file.

D4 Comment: No mention of the operator interface for any of the incident detection data. Will it be consistent with 2.2?


CitiLog Camera ConfigurationCitiLog Camera Configuration

New location description field added


IDS: Scope QuestionsIDS: Scope Questions

Included in R3 Scope or Requirements and will be implemented:– Displaying incident detection data in alert bar and alert box

on EM GUI– Displaying incident detection data as flashing icon on map

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:– Floating alert bar over map


Incident Detection Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Major Design DecisionMajor Design Decision

At first review: AVL and RR were separate because:– Road Ranger data CONTAINS AVL data– AVL data does not necessarily contain RR data– “Two way” communication need to RR was not

understood

After extensive internal discussions, SwRI has modified the design:– RR and AVL will be combined into a single subsystem– Drivers for D4 and D7 formatted data will be developed– Subsystem structure will support the addition of future

“AVL only” drivers


AVL / RR Functionality:AVL / RR Functionality:High Level Summary – Vehicle DataHigh Level Summary – Vehicle Data

Vehicle tracking:– Icon positioning on map with breadcrumbs– Update based on data received from field

Status:– Icon color changes based on status (Does FDOT want to combine

these for color purposes?)• Patrolling• Dispatched• Assisting

– Motorist– FHP– Other RR

• Meals• Base• Inspection• Mechanical• Out-of-Service

– Summary, rollover tool-tip (details shown in later slide) per vehicle– Detailed status per vehicle


AVL / RR Functionality:AVL / RR Functionality:High Level SummaryHigh Level Summary

Summary data via the GUI

– Vehicle list

– Rollover tool-tip on Map Location playback via the Map

– Historical tracking with breadcrumbs

– Single vehicle Status data

– RR status data

– RR shift data

– Incident data


AVL / RR Functionality:AVL / RR Functionality:High Level Summary – Geo-fencingHigh Level Summary – Geo-fencing

Capabilities:

– To define a geo-fence, select poly-line with configurable “offset width” on map

– Optionally associate a beat with a geo-fence

Geo-fencing alerts

– Icon will flash on Map

– Will be displayed on alert box in EM


AVL / RR Functionality:AVL / RR Functionality:High Level – Admin EditorHigh Level – Admin Editor

Use Admin Editor to define:

– Vehicle groups

– Tracked vehicles

– Availability status

– Vehicle operators

Note: Icons are NOT configurable per FDOT direction


AVL / Road Ranger DesignAVL / Road Ranger Design



Playback to be displayed in existing or pop-up map?– Pop-up map not possible due to technical limitations– Provide existing map display with other icons hidden– Map will center and zoom appropriately

• Original view will be restored when exiting playback mode

AV004L (Feat24.3.2) states “As a minimum, the XML data file shall contain the following information: …area of responsibility for the vehicle (zone ID or area ID)…”

– Is this the same as “beat”?– What is the source for this data?

D4 Comment: We believe this should be by beat.



Standardized icons for AVL– The following requirements contradict a decision made in the

May 8th-9th DR.• FEAT24.1.2 (AV002V):

The icon symbol for each vehicle shall be able to be selected by an operator with administration rights on SunGuide and with appropriate permission for the subsystem.

• FEAT24.6.4 (AV004V):If position reports are received for different service vehicles … the operator with appropriate privileges shall be able to assign an icon to represent the type of vehicle for the type of position reports received.

Action Item #136:– FDOT to provide icon ideas to be used for managed vehicle

groups


Managed Vehicle Group and Managed Vehicle Group and Availability Status ConfigurationAvailability Status Configuration


Vehicle ConfigurationVehicle Configuration

Is “Road Ranger” the Is “Road Ranger” the correct term? correct term? (Default to checked).(Default to checked).


Road Ranger ConfigurationRoad Ranger Configuration


Operator Map ScreensOperator Map Screens

Change Change Vehicle Vehicle State State control is control is disabled disabled for non-RR for non-RR vehiclesvehicles


AVL PlaybackAVL Playback


Geo-Fence EditorGeo-Fence Editor


AVL / RR: Scope QuestionsAVL / RR: Scope Questions

Included in R3 Scope or Requirements and will be implemented:– Playback on existing map with icons hidden

Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule:– Managed vehicle groups– Two way communication to RR devices using the D4-XML

protocol– Ability to globally enable/disable geo-fences

Not included in R3 Scope or Requirements and will require additional budget and/or schedule:– Dispatch of Road Rangers from RR Vehicle List GUI

D4 Comment: Is dispatching from the RR Vehicle List required or desired? The current system does not allow this, you must first open the event data edit window and dispatch vehicles to the event from that screen. The RR/SIRV list is not used to dispatch vehicles at all.


AVL / RR Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Issues from Initial Design ReviewIssues from Initial Design ReviewEvent Manager (Event List)Event Manager (Event List)

Event Manager (Event List)– Alert Bar – display multiple alerts– Alert List – display multiple alert types in a single list

(color coded) including the following Alert Types:• Road Ranger Messages• Blocked CCTV Messages• TSS Alerts• VisioPaD Alerts• GeoFence Alerts• C2C Alerts• Etc.

– Menu structure– Filter fields identified (green column header)– Floating Alert List, stays on the screen during scrolling


Issues from Initial Design ReviewIssues from Initial Design ReviewEvent Manager (Event List)Event Manager (Event List)


Issues from Initial Design ReviewIssues from Initial Design ReviewAlert Bar & Alert ListAlert Bar & Alert List

Color coding of Alert Types

Filtering of alerts by Alert Type

Access to alert directly through the Alert Bar

Sorting by alert name or time

Legend


Issues from Initial Design ReviewIssues from Initial Design ReviewAdd New Event DialogAdd New Event Dialog

Same as existing EMPM Event Location

removed to simplify and speed up data entry

Status:

– Unconfirmed

– Active


Event Details GUIEvent Details GUI

Maintain look of the EMPM GUI

Changes include:– Lane Blockage

& DMS Assignment

– Responder List

– Nearest CCTV timestamp

– Event Location & Congestion


Issues from Initial Design ReviewIssues from Initial Design ReviewAdministrative Details SubsectionAdministrative Details Subsection

No Change


Issues from Initial Design ReviewIssues from Initial Design ReviewEvent Location / CongestionEvent Location / Congestion

Ability to define Congestion Head & Tail


Issues from Initial Design ReviewIssues from Initial Design ReviewLane BlockageLane Blockage

Consolidation of the Lane Blockage & DMS Assignment subsections

X – used for lane blockage 2 new lane types: HOT, Gore (not shown) Larger Lane Map symbols ? – unknown Lane Blockage status does not

activate “All Lanes Cleared” in Chronology Report


Issues from Initial Design ReviewIssues from Initial Design ReviewReporting & DispatchingReporting & Dispatching

No Change


Issues from Initial Design ReviewIssues from Initial Design Review Road Ranger Procedural ErrorRoad Ranger Procedural Error

No Change


Issues from Initial Design ReviewIssues from Initial Design Review Event Details SubsectionEvent Details Subsection

No CCTV checkbox Nearest CCTV Timestamp


Issues from Initial Design ReviewIssues from Initial Design ReviewVehicles InvolvedVehicles Involved

No Change Admin Editor used for editing of state names


Issues from Initial Design ReviewIssues from Initial Design Review Weather ConditionsWeather Conditions

Default options include most common conditions Additional options included N/A option is last Options editable through Admin Editor


Issues from Initial Design ReviewIssues from Initial Design Review Event Comments and HistoryEvent Comments and History

No Change


Issues from Initial Design ReviewIssues from Initial Design Review Responder ListResponder List

Display last added contact only Full contact list is editable using

the Audit functions


Issues from Initial Design ReviewIssues from Initial Design Review Suggest Response PlanSuggest Response Plan

Handle multi-phase DMS signs


Issues from Initial Design ReviewIssues from Initial Design Review Activate Response PlanActivate Response Plan

Handle multi-phase DMS signs Add additional email to the Response Plan


Issues from Initial Design ReviewIssues from Initial Design ReviewEmail EditorEmail Editor

No Change


EM: Scope QuestionsEM: Scope Questions


Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule:– Modifications to Event Location/Congestion, Lane Blockage,

Responder List, Weather Conditions, etc.– Additional Admin Editor functionality

Not included in R3 Scope or Requirements and will require additional budget and/or schedule:– TBD: Elaborate desired presentation of Alerts on Event List?


EM Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Issues from Initial Design ReviewIssues from Initial Design Review Standard ReportsStandard Reports

Ability to manage Report Categories using Admin Editor

Ability to manage Reports and their corresponding categories using the Admin Editor

Only filters pertaining to specific report will be displayed

Alert Bar displayed at the top


Issues from Initial Design ReviewIssues from Initial Design Review Performance Measures (PM) Calculation and Performance Measures (PM) Calculation and Report GenerationReport Generation

Alert Bar added


Issues from Initial Design ReviewIssues from Initial Design Review Responder Notification Timeline AuditResponder Notification Timeline Audit

Ability to add, modify, delete for each contact Dates/times are selectable (no typing)


Issues from Initial Design ReviewIssues from Initial Design Review Notifying Agency and Notifying Contact AuditNotifying Agency and Notifying Contact Audit

No Change


Issues from Initial Design ReviewIssues from Initial Design Review Event Location & Congestion AuditEvent Location & Congestion Audit

Consolidated location & congestion audit


Issues from Initial Design ReviewIssues from Initial Design Review Event Status AuditEvent Status Audit

Dates/times are selectable (no typing)


Issues from Initial Design ReviewIssues from Initial Design Review Lane Blockage AuditLane Blockage Audit

Dates/times are selectable (no typing) Changes reflect the Lane Blockage control


Issues from Initial Design ReviewIssues from Initial Design Review Vehicle Identification AuditVehicle Identification Audit

No change


Issues from Initial Design ReviewIssues from Initial Design Review Road Ranger Dispatch AuditRoad Ranger Dispatch Audit

Ability to add, modify, delete activities Ability to add, modify, delete entire dispatch records


Issues from Initial Design ReviewIssues from Initial Design Review DMS Message TimeDMS Message Time

No change


Reporting: Scope QuestionsReporting: Scope Questions


Not included in R3 Scope or Requirements, but will be implemented within existing budget and schedule:– Date/Time validation for all date/time stamps– Use of the 24 hour clock for all dates– Consolidation of Event Location/Congestion audit

Not included in R3 Scope or Requirements and will require additional budget and/or schedule:– TBD: Secondary Crash Rate related report functionality?


Reporting Questions?


AgendaAgenda

Time Item Lead






9:30 – 9:50 Break

9:50 – 11:45 AVL / RR Heller

11:45 – 1:00 Lunch


3:00 – 3:15 Break




Discussion ?

Date post:	18-Jan-2016
Category:	Documents
Upload:	rosina
View:	18 times
Download:	0 times

Agenda

Documents