SunGuide TM Software Development Project Release 3.1: I-95 Express Lanes GUI Design Review March 10,...

SunGuideSunGuideTMTM Software Development Project Software Development Project

Release 3.1: I-95 Express Lanes Release 3.1: I-95 Express Lanes GUI Design ReviewGUI Design Review

March 10, 2008March 10, 2008

March 10, 2008R3.1 Express Lanes GUI Design Review 2

AgendaAgenda

Time Item Lead

3:00 – 3:05 Introductions and Opening Remarks Tillander

3:05 – 3:10 Project Update Santana

3:10 – 3:15 High Level Overview – meeting objectives Heller

3:15 – 3:40 Action Item Review Misra

3:40 – 4:15 Final Toll Viewer Design Misra

4:15 – 5:00 Final Admin Editor Design Misra

5:00 – 5:15 Break

5:15 – 5:45 Final Express Lanes GUI Misra

5:45 – 6:00 Open Discussion All


Introductions


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




District 6 Update


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Purpose of this Design ReviewPurpose of this Design Review

SwRI Requirements have been contractually updated in SWAM #15

The GUIs presented in this DR are SwRI’s “interpretation” of how the user interface will be implemented:

– Administrator Editor (not used often, used for configuration and setup)

– Operator User Interface (what they see all the time)

– Toll Viewer


Current Architectural DrawingCurrent Architectural Drawing


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Action ItemsAction Items

After published in minutes, they are maintained on the project web site and reported on in each status report

Express Lanes related Action Items:

– January 9-10, 2008 Design Review: #237 - #277

– January 29, 2008 Follow-up DR: #278 - #289

Following slides show:

– Open: some may be complete, simply need an update

– Closed: task has been complete


AI Review - OpenAI Review - Open

Num Date Who Action Item Due Date Comments

268 1/07/08 PBS&JRevise requirement TM006T2 to

remove third meta-rule.Feb 1, 2008

269 1/07/08 FDOT CO

Determine from the districts what the software should assume when there are no matches detected. Should SwRI assume either stopped traffic or night time conditions? What should be reported in both cases? Should ‘no data available’ or the optimum time be reported?

Feb 1, 2008

274 1/09/08 D6/Santana

District 6 (Rory Santana) to investigate the proper way of handling of Toll Rate DMS's (update rate on the bricks, individual sign delays, redundancy of signs)

Jan 22, 2008

277 1/09/08 D6/Santana

District 6 (Rory Santana) to find out the decision of maximum toll that can be charged and how fast it can be increased

Jan 28, 2008

280 1/29/08IBI / D4 / D6 /

FTE

Turnpike will need to provide the range of IP addresses used by its workstations when accessing Toll Viewer.

Feb 15, 2008


AI Review – Open – continuedAI Review – Open – continued

Num Date Who Action Item Due Date Comments

281 1/29/08 FTE / FDOTDiscuss connectivity issues to allow for

SwRI/FTE Middleware testing.Feb 11, 2008

282 1/29/08 IBIDescribe method for how to secure access

using IIS between Turnpike/District networks

Feb 29, 2008


AI Review - ClosedAI Review - Closed

Num Date Who Action Item Due Date Comment

237 1/09/08 SwRISubmit waiver to FDOT to waiver

SunGuide Security requirement in SWAM#14

Jan 22, 2008 Submitted and approved.

238 1/09/08 IBI

Remove the ML007D2 requirement from SWAM#14 which specifies the use of message scheduling features of the Toll Rate DMS.

Jan 22, 2008Requirements updated and included in

SWAM #15

239 1/09/08 IBI

For requirements ML008I and ML002I in the SWAM#14, IBI will remove “Variable Rate” message from corresponding requirement so it is not specific since WSDL can change.


SWAM #15

240 1/09/08 IBI

IBI to clarify what “all” means in the following requirement “SunGuide shall maintain history records in the database of all configuration changes.” – ML001S


SWAM #15

241 1/09/08 SwRI / FDOT

A modification to SWAM#14 will be needed once high level requirements are solidified for this phase.

Jan 22, 2008 Modifications are in SWAM #15


AI Review – Closed - continuedAI Review – Closed - continued


242 1/09/08 Khue NgoKhue to provide Visio drawing of

Phase 1A layout to all participants.

Jan 22, 2008 Provided on 1/29/08

243 1/09/08 Rory Santana

Rory indicated that he will be updating Con-ops and release a new version due to modified business rules.

Jan 22, 2008 Completed.

244 1/09/08 SwRISwRI to update design per new

terminology for Express Lanes. Jan 22, 2008 Completed.

245 1/09/08 IBIRemoval of Informational DMS for

alternate name for Lane Status DMS from requirements

Jan 22, 2008 Completed.

246 1/09/08 SwRIAddress Admin Editor changes as

noted in Item # 7Jan 22, 2008 Completed.

247 1/09/08 SwRI

Consider storing the current state of the software in the event of power failure. SwRI will investigate adding appropriate handling.

Mar 1, 2008 Closed - Per SWAM #15, software will

restart in "normal mode".

248 1/09/08 SwRI

Investigate how the DMS layout in GUI Option #2 will look with additional signs (first segment will have 6 signs). With the current layout, the 6 signs will not show on one line.

Feb 1, 2008

SwRI presented an updated GUI Option #2 during the Jan. 29 follow-up design review and group agreed this was okay to move forward for the first release of Express Lanes (3.1)




249 1/09/08 SwRIInvestigate addition of “map graphic”

on the express lanes tab.Feb 1, 2008

SwRI has investigated this and determined that it is cost prohibitive to add this to the express lanes tab.

250 1/09/08 SwRI

Investigate if feasible to display a short description of the event in the “Select Associated Events” drop down box in the “Lane Override Controls” box.

Mar 1, 2008 This is feasible and will be added.

251 1/09/08 SwRIAdditional material be added to the

Admin training on the DMS “yellow” status

Apr 30, 2008SwRI acknowledges and will be updated in the

documentation.

252 1/09/08 SwRIInvestigate how “yellow” status error

(fan, pixel, etc.) is logged in status logger.

Jan 22, 2008 They are logged as “Info” messages logged by

DmsPolling indicating “pixel:error”, etc.

253 1/09/08 SwRI

Investigate if manual control of DMS messages can be implemented in express lanes tab and without user going back to the map ?

Mar 1, 2008

Access to the DMS control will be available by clicking on the DMS icon on the Express Lanes tab which will bring up the detailed DMS dialog which will allow them to send a message assuming the operator has correct permissions.

254 1/09/08 SwRISwRI will investigate if calendar

control could be used on the Toll Viewer search screen.

Mar 1, 2008 A calendar control does exist and will be

implemented in Toll Viewer.




255 1/09/08 SwRI

SwRI to add “plaza/gantry”id for what names the CSRs should see in the drop-down to select segments.

Mar 1, 2008Acknowledged. This will be implemented as

shown on Toll Viewer mockup slides presented during Jan. 29 design review.

256 1/09/08 SwRISwRI to change time stamp to be in

AM/PM rather than 24 hr.Mar 1, 2008

Acknowledged. This will be implemented as shown on Toll Viewer mockup slides presented during Jan. 29 design review.

257 1/09/08 SwRIToll Viewer detailed view is missing

location and lanes blocked which are required.

Mar 1, 2008

Acknowledged. SwRI added this to the design and it will be implemented as shown on Toll Viewer mockup slides presented during Jan. 29 design review.

258 1/09/08SwRI / FTE /

FDOT

SwRI to send Trey Toll Viewer mock-up screens so he can send to Scot Orman to have business users provide feedback by January 17, 2008.

Jan 17, 2008Provided in design review slides. Final GUI to

be presented in March.

259 1/09/08 Khue Ngo

Provide a schematic of the roadway and segment showing the location of equipment. This will allow a CSR can match the equipment names with the actual locations on the segment.

Jan 22, 2008 Closed: duplicate of Action Item #242




260 1/09/08 SwRI

Investigate if speed alerts (if/when use of TSS is a required) would also be shown on the toll viewer. Scot asked that a note be made that this is desired in the toll viewer.

Jan 22, 2008Screens have been reviewed by FDOT, final

GUI review planned in early March.

261 1/09/08 PBS&JPBS&J will handle training for

Express Lanes.Jan 22, 2008 NOted.

262 1/09/08FDOT / FTE /

SwRINeed requirement and design freeze

ASAPJan 22, 2008 Requirements have been finalzied

263 1/09/08 SwRI

SwRI to investigate the Steve Corbin’s modified GUI Option #2 for impact to cost/schedule (see notes in Item#17)

Jan 22, 2008Revised requirements are in being included in

SWAM #15

264 1/09/08 SwRI / FTE Resolve WSDL questions and issues. Jan 22, 2008WSDL interfaces have been finalized - testing

phase in process.

265 1/09/08FTE / FDOT /

SwRI

Work out the networking connection for testing Turnpike Middleware interface with SwRI. David Harkcom will need support from Jennifer for this.

Jan 28, 2008As of Feb 18, 2008; the middleware will be

provided to SwRI for installation in the SwRI development labs.

266 1/09/08 SwRISwRI will review requirement change

#1 and #2 to determine impact to schedule and cost.

Jan 22, 2008Requirements have been updated and will be

provided in SWAM #15




267 1/09/08 FDOTTrey to arrange requirements follow

up telecom with all parties to finalize requirements.

Jan 14, 2008 Closed: scheduled and held.

270 1/09/08 SwRI

SwRI to investigate adding a camera-captured image of the DMS to confirm the message was posted in the next release. For this release 3.1, put a place holder for camera image to the Option #2 Express Lanes GUI.

Feb 18, 2008

From a technical standpoint SwRI could show still images for snapshots captured via the IPVideoSwitch driver. Difficult layout-wise to place onto Express Lanes GUI.

271 1/09/08 IBI / PBS&J

IBI (or PBS&J) to modify requirement ML001S (discussed in Item #3: History records of all configuration changes)

Jan 22, 2008

This should be closed because all parties agreed that this requirement could be removed from the new finalized requirements. SwRI believe the most critical archiving (the rate tables themselves) is still covered under 8.2.1 under the final requirements.

272 1/09/08 SwRI

SwRI to investigate how Express Lane-related alerts can be incorporated into the Express Lanes Tab Option #2 screen so operators do not have to look at multiple windows.

Feb 18, 2008

SwRI investigated this and presented a mockup screen shot during the Jan. 29 design review. The group agreed to the suggested design.

273 1/09/08 IBI

IBI to add a requirement for displaying the average speed in 15-minute intervals on the Toll Viewer’s Advanced User screen.

Jan 22, 2008

Closed. This is no longer required since requirement was struck from the first Express Lanes software release. This was agreed to by all parties.




275 1/09/08 IBI

IBI to update the requirement reflecting the removal of Informational DMS for alternative name for Lane Status DMS

Jan 22, 2008 Closed. The new requirements do not contain

the word “Informational DMS”.

276 1/09/08 SwRI

SwRI update Admin Training material to indicate the text "Prefix Text" will be displayed on the Operator GUI on the express lane tab.

April 30, 2008 SwRI acknowledges and will be updated in the

documentation.

278 1/29/08 SwRIAdd link to the static map from Toll

Viewer application.Feb 15, 2008

Complete - included in GUIs that will be reviewed on March 10 at the GUI DR.

279 1/29/08 SwRIAdd event ID and event description of

the event general view to detailed view of Toll Viewer.

Feb 15, 2008 Complete - included in GUIs that will be

reviewed on March 10 at the GUI DR.

283 1/29/08 SwRI

Investigate date for when a final design review showing GUI screens, Toll Viewer and Admin screens can be made available.

Feb 22, 2008 Complete - scheduled for March 10

284 1/29/08 SwRI

Investigate if the left shoulder next to an express lane is blocked – would this show as general lanes affected or as express lanes affected?

Feb 22, 2008

Closed - it will show up as left shoulder blocked in EM. A shoulder is not an attribute of HOT lanes/general purpose lanes, it is treated as a separate lane.




285 1/29/08 SwRIRemove the word “Authorized” from

requirement 7 and requirement 7.2 can be struck entirely.

Feb 1, 2008 Complete – FDOT processing SWAM #15

286 1/29/08 SwRI

Modify requirements per agreed to functionality for 3.1 and send out to the group (with markup of modifications – new phases, etc).

Feb 1, 2008 Complete – FDOT processing SWAM #15

287 1/29/08 SwRISend high-level summary of what

functionality has changed.Feb 1, 2008 Complete - sent to FDOT on 1/31/08

288 1/29/08 IBIReview and finalize requirements

document after SwRI’s modifications.

Feb 4, 2008Complete – FDOT CO has included in

SWAM #15

289 1/29/08 SwRIProvide cost impact for implementing

new requirements to FDOT.Feb 7, 2008 Complete – FDOT processing SWAM #15


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Toll Viewer Search Toll Viewer Search


Toll Viewer Summary Toll Viewer Summary


Toll Viewer Detailed Toll Viewer Detailed


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Express Lanes Admin EditorExpress Lanes Admin Editor

Six items to configure:

– System Configuration

– Holiday / Special Events

– Segments

– Daily Rate Schedules

– Segment / Rate Schedules

– Toll Rate Signs (DMS)


Express Lane System ConfigurationExpress Lane System Configuration


Holidays/Special EventsHolidays/Special Events


SegmentsSegments


Daily Rate SchedulesDaily Rate Schedules


Segment/Rate SchedulesSegment/Rate Schedules


Toll Rate Signs Toll Rate Signs


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Express Lanes TabExpress Lanes Tab


Override Mode DialogOverride Mode Dialog


Alert Acknowledge DialogAlert Acknowledge Dialog


AgendaAgenda

Time Item Lead







5:00 – 5:15 Break




Discussion ?

SunGuide TM Software Development Project Release 3.1: I-95 Express Lanes GUI Design Review March 10,...

Documents

Transcript of SunGuide TM Software Development Project Release 3.1: I-95 Express Lanes GUI Design Review March 10,...