training progress report - sunguide® softwaresunguidesoftware.com/sunguidesoftware... · training...

SunGuideSM: Training Progress Report SunGuide-TPR-1.1.0

Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee Street, M.S. 90 Tallahassee, Florida 32399-0450 (850) 410-5600 June 30, 2005

Training Progress Report

SunGuide-TPR-1.1.0 i

Document Control Panel

File Name: SunGuide-TPR-1.1.0.doc File Location: SunGuide CM Repository CDRL: 5-1.4

Name Initial Date

Steve Dellenback, SwRI SWD 06/29/05 Created By: Susan B. Crumrine, SwRI SBC 06/30/05

Reviewed By:

Modified By:

Completed By:


SunGuide-TPR-1.1.0 ii

Table of Contents

Page List of Acronyms.......................................................................................................... iii Revision History........................................................................................................... iv 1. Scope.................................................................................................. 1

1.1 Document Identification .......................................................................... 1 1.2 Training Summary ................................................................................... 1 1.3 Document Overview ................................................................................ 1

2. SunGuideSM Training ......................................................................... 2 2.1 Classroom Environment and Instructors .............................................. 2 2.2 Classed Provided and Attendance......................................................... 2 2.3 Issues Identified....................................................................................... 2

Attachments

A – Training Attendance Sign-in Sheets


SunGuide-TPR-1.1.0 iii

List of Acronyms

DMS...........................Dynamic Message Sign FDOT .........................Florida Department of Transportation SwRI ..........................Southwest Research Institute TPR ............................Training Progress Report


SunGuide-TPR-1.1.0 iv

REVISION HISTORY

Revision Date Changes 1.1.0 June 30, 2005 Initial Release.


SunGuide-TPR-1.1.0 1

1. Scope

1.1 Document Identification This document serves as the Training Progress Report (TPR) for the SunGuideSM software Release 1.1.

1.2 Training Summary A detailed Training Plan was provided to the Florida Department of Transportation (FDOT) in both draft form and final form by Southwest Research Institute® (SwRI®). The document was reviewed by FDOT while in draft form and the final version was provided to FDOT on October 21, 2004. The document identifier of the final Training Plan was SunGuide-TP-1.0.0.

The Training Plan outlined three courses:

• Operator/User Interface Training Course

• System Administration/Deployment Training Course

• Software Design and Maintenance Training Course

By FDOT’s direction, SwRI provided the first two courses in District 4 on June 27-28, 2005 in the District 4 facilities.

1.3 Document Overview The remainder of this document provides the following:

• Class environment and instructors

• Classes provided and attendance

• Issues identified that FDOT would like addressed



2. SunGuideSM Training The following sections describe the training activities that occurred during the training sessions held at District 4.

2.1 Classroom Environment and Instructors The Training Plan had described an environment of dual LCD projectors with one being used for instruction and one being used for live software demonstrations. District 4 had requested that SwRI utilize multiple workstations (for student hands-on training) as opposed to the laptop version of SunGuideSM software.

The actual training occurred in the second floor training room at District 4 that had no wired access to District 4 (only access to Broward County network is provided in the room); the room did have wireless access to the District 4 network but the reliability of the wireless network was low and the connection could not be maintained throughout the day. As a result, the training slides were briefed in the second floor training room and the entire class moved down to the operational floor for hands-on training.

The SwRI instructors included:

• Robert Heller • Roger Strain • Bret Sadler

2.2 Classed Provided and Attendance The following classes were offered:

• SunGuideSM Release 1.1 Operator Training: June 27, 2005 – 1:00 p.m. to 5:00 p.m.

o 8 students o 3 SwRI instructors

• SunGuideSM Release 1.1 Administrator Training: June 28, 2005 – 9:00 a.m. to 12:00 p.m.


• SunGuideSM Release 1.1 Operator Training: June 28, 2005 – 1:00 p.m. to 5:00 p.m.


Attachment A of this document contains the sign-in sheets signed by the students.

2.3 Issues Identified There were several issues raised during the training sessions that may result in feature requests (these issues were captured by Mr. Walt Townsend and Dr. Robert Heller):

(1) A DMS (Dynamic Message Sign) Sequence can only be set up to put a message on signs for up to 12 hours per day. If a user wants to run a message for an entire day, it is necessary to set up two schedule entries, one for the first 12 hours and one for the



second 12 hours. SwRI note: this is because of a limitation in the Mark IV signs that do not allow a message to be displayed for more than 18 hours.

(2) There is no way to restrict an operator from editing the content of a message being sent to a sign. There is a permission that allows operators to send messages to signs, and a permission that allows operators to approve messages that have words that are not in the approved list. The District 4 SunGuideSM Administrator is requesting that a permission be added to control the ability to edit a message – they want most operators to be able to send messages from libraries or the Incident Management system to signs, but not be allowed to edit the content of the messages. SwRI note: this needs to be requested as an enhancement by FDOT.

(3) Names of streets in the database need to be reviewed. These names are used by Incident Management to construct the messages for the signs, and some of the names in the database are too long. SwRI note: this is a software configuration issue that should be addressed by the District 4 SunGuideSM Administrator.

(4) The District 4 SunGuideSM Administrator requested that no “two phased” DMS messages should ever be recommended by the Incident Management subsystem. This would require the Incident Management subsystem to substitute in “abbreviations” when messages are recommended that exceed the geometry of the sign. SwRI note: this needs to be requested as an enhancement by FDOT.

(5) The District 4 SunGuideSM Administrator would like the ability to “drag” or move device icons on the map. Right now the only way to move devices once they are placed is to edit the latitude and longitude values in the admin editor. SwRI note: this needs to be requested as an enhancement by FDOT.

(6) When detector links are configured in the system, a “speed limit” can be configured for the maximum speed that can be reported by the link. This is intended to prevent the travel time module from reporting travel times that are faster than possible with posted speed limits. District 4 SunGuideSM Administrator is requesting that the speed not be limited at the detector, so that actual data is logged in the system and reported to the operators. Any limitation of speeds reported to the public should be done in the appropriate subsystem, such as the travel time subsystem or the web server. SwRI note: this needs to be requested as an enhancement by FDOT.

(7) The District 4 SunGuideSM Administrator requested clarification on the polling rates from the vehicle detectors, how the information is aggregated or averaged, and the units it is reported in. SwRI note: the SwRI on-site support staff member will work with District 4 to address this need.


SunGuide-STR-1.1.0

Attachment A

Training Attendance Sign-In Sheets

training progress report - sunguide® softwaresunguidesoftware.com/sunguidesoftware... · training...

Documents