software users manual - sunguide®...

SunGuideSM: Software Users Manual SunGuide-SUM-1.0.0-Draft

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

Software Users Manual

SunGuide-SUM-1.0.0-Draft i

Document Control Panel

File Name: SunGuide-SUM-1.0.0-Draft.doc File Location: SunGuide CM Repository CDRL: 6-7.1

Name Initial Date

Steve Dellenback, SwRI SWD 8/24/04 Created By: Tammy Duncan, SwRI TD 8/24/04 Steve Dellenback, SwRI SWD 11/29/04 Steve Novosad, SwRI SEN 11/29/04

Reviewed By:

Steve Dellenback, SwRI SWD 11/22/04

Modified By:

Completed By:


SunGuide-SUM-1.0.0-Draft ii

Table of Contents

Page

List of Figures .............................................................................................................. iv List of Acronyms........................................................................................................ viii Revision History........................................................................................................... ix

1. Scope.................................................................................................. 1 1.1 Document Identification .......................................................................... 1 1.2 Project Overview...................................................................................... 1 1.3 Related Documents ................................................................................. 2 1.4 Contacts ................................................................................................... 2

2. Software Summary ............................................................................ 4 2.1 Software Application ............................................................................... 4 2.2 Software Organization and Overview of Operation .............................. 4 2.3 Contingencies and Alternate States and Modes of Operation............. 4

2.3.1 Regional Transportation Management Center...........................5 2.3.2 Satellite Transportation Management Center ............................5 2.3.3 Virtual Transportation Management Center..............................6 2.3.4 Portable Transportation Management Center............................6

2.4 Security and Privacy................................................................................ 7 3. System Administration ..................................................................... 8

3.1.1 Executive Handler Editor...........................................................8 3.1.2 Executive Handler Server ........................................................10 3.1.3 Executive Handler Viewer.......................................................11 3.2.1 Status Logger Server................................................................18 3.2.2 Status Logger Control Panel Applet ........................................18 3.2.3 Status Logger Viewer ..............................................................20 3.3.1 Software Familiarization..........................................................25 3.3.2 Processing Procedures .............................................................26 3.4.1 Software Familiarization..........................................................66 3.4.2 Processing Procedures .............................................................67

4. Map Operation ................................................................................. 81 4.2.1 Control Panel and Context Menu ............................................82 4.2.2 Map Controls ...........................................................................83 4.2.3 Context Menu ..........................................................................84 4.2.4 Links ........................................................................................87 4.2.5 Dynamic Message Signs..........................................................89 4.2.6 Cameras....................................................................................97


SunGuide-SUM-1.0.0-Draft iii

4.2.7 Video Switching ......................................................................99 4.2.8 Video Wall Control................................................................101 4.2.9 Incident Management ............................................................102

5. Notes............................................................................................... 131


SunGuide-SUM-1.0.0-Draft iv

List of Figures

Page Figure 1.1 - High-Level Architectural Concept.............................................................................. 1 Figure 2.1 - Relationship Between an RTMC and STMC............................................................. 6 Figure 3.1 - Process List Editor ...................................................................................................... 8 Figure 3.2 - Add Process – Blank ................................................................................................... 9 Figure 3.3 - Add Process – Detail................................................................................................. 10 Figure 3.4 - Executive Handler Service........................................................................................ 11 Figure 3.5 - Executive Handler Viewer ........................................................................................ 12 Figure 3.6 - File Menu .................................................................................................................. 12 Figure 3.7 - Add New Host........................................................................................................... 13 Figure 3.8 - Host Menu................................................................................................................. 13 Figure 3.9 - Delete Host Confirmation ......................................................................................... 14 Figure 3.10 - Sub-system Menu.................................................................................................... 14 Figure 3.11 - Process Menu .......................................................................................................... 15 Figure 3.12 - Log Level ................................................................................................................ 15 Figure 3.13 - View Menu.............................................................................................................. 16 Figure 3.14 - Window Menu......................................................................................................... 16 Figure 3.15 - Subsystem List View............................................................................................... 17 Figure 3.16 - Help Menu............................................................................................................... 17 Figure 3.17 - Status Logger Service ............................................................................................. 18 Figure 3.18 - Control Panel........................................................................................................... 19 Figure 3.19 - Status Logger Control Panel Applet ....................................................................... 20 Figure 3.20 - Status Logger .......................................................................................................... 21 Figure 3.21 - File Menu ................................................................................................................ 21 Figure 3.22 - Connect ................................................................................................................... 22 Figure 3.23 - Edit Menu................................................................................................................ 22 Figure 3.24 - View Menu.............................................................................................................. 23 Figure 3.25 - Refresh Options....................................................................................................... 23 Figure 3.26 - Filter Options .......................................................................................................... 24 Figure 3.27 - Help Menu............................................................................................................... 25 Figure 3.28 - Status Interface Test Client after Startup ................................................................ 26 Figure 3.29 - User List .................................................................................................................. 27 Figure 3.30 - Add User ................................................................................................................. 28 Figure 3.31 - Edit User.................................................................................................................. 29 Figure 3.32 - Group List ............................................................................................................... 30 Figure 3.33 - Edit Group............................................................................................................... 31 Figure 3.34 - Workstation List...................................................................................................... 32 Figure 3.35 - Edit Workstation ..................................................................................................... 33 Figure 3.36 - Sign List .................................................................................................................. 34 Figure 3.37 - Edit Sign.................................................................................................................. 35 Figure 3.38 - Approved Word List ............................................................................................... 36 Figure 3.39 - Edit Approved Word ............................................................................................... 37


SunGuide-SUM-1.0.0-Draft v

Figure 3.40 - Camera List ............................................................................................................. 38 Figure 3.41 - Edit Camera............................................................................................................. 39 Figure 3.42 - Edit Camera with Encoder ...................................................................................... 40 Figure 3.43 - Edit Camera with Switch ........................................................................................ 41 Figure 3.44 - Video Destination List ............................................................................................ 42 Figure 3.45 - Edit Video Destination............................................................................................ 43 Figure 3.46 - Roadway List .......................................................................................................... 44 Figure 3.47 - Edit Roadway .......................................................................................................... 45 Figure 3.48 - Detector List............................................................................................................ 46 Figure 3.49 - Edit Detector ........................................................................................................... 47 Figure 3.50 - Detector List............................................................................................................ 48 Figure 3.51 - Edit Detector Mapping............................................................................................ 49 Figure 3.52 - Edit Detector Mapping – Select Link...................................................................... 50 Figure 3.53 - Edit Detector Mapping – Add Link ........................................................................ 51 Figure 3.54 - Edit Detector Mapping – Select Lane ..................................................................... 52 Figure 3.55 - Edit Detector Mapping – Add Lane ........................................................................ 53 Figure 3.56 - Highway List.......................................................................................................... 54 Figure 3.57 - Define Highway ..................................................................................................... 55 Figure 3.58 - Highway Defined with Links ................................................................................. 56 Figure 3.59 - Travel Time Link List ............................................................................................. 57 Figure 3.60 - Edit Travel Time Link............................................................................................. 58 Figure 3.61 - Edit Travel Time Link – Select Link ...................................................................... 59 Figure 3.62 - Contact List ............................................................................................................. 60 Figure 3.63 - Add Contact - Blank................................................................................................ 61 Figure 3.64 - Add Contact - Filled................................................................................................ 61 Figure 3.65 - Add Contact – Field Entry Error............................................................................. 62 Figure 3.66 - Add Contact – Page Error ....................................................................................... 63 Figure 3.67 - Edit Contact............................................................................................................. 64 Figure 3.68 - Updated Contact List............................................................................................... 65 Figure 3.69 - Confirm Delete........................................................................................................ 66 Figure 3.70 - Link Editor Login Dialog........................................................................................ 67 Figure 3.71 - Select Network ........................................................................................................ 67 Figure 3.72 - Add Network........................................................................................................... 68 Figure 3.73 - Link Editor Control Panel ....................................................................................... 69 Figure 3.74 - Links........................................................................................................................ 70 Figure 3.75 - Add Nodes............................................................................................................... 71 Figure 3.76 - Available Links ....................................................................................................... 72 Figure 3.77 - Select Start Node..................................................................................................... 72 Figure 3.78 - Northbound Link Placed ......................................................................................... 73 Figure 3.79 - Southbound Link Placed ......................................................................................... 74 Figure 3.80 - Add Midpoint .......................................................................................................... 75 Figure 3.81 - Reposition Midpoint 1............................................................................................. 76 Figure 3.82 - Reposition Midpoint 2............................................................................................. 77 Figure 3.83 - Shape File Conversion Tool: Initial Screen ............................................................ 79 Figure 3.84 - Shape File Conversion Tool: County Selector........................................................ 79 Figure 3.85 - Shape File Conversion Tool: County Selected ....................................................... 80


SunGuide-SUM-1.0.0-Draft vi

Figure 4.1 - Operator Map Login Dialog...................................................................................... 81 Figure 4.2 - Loading Status Screen............................................................................................... 82 Figure 4.3 - Operator Map Control Panel ..................................................................................... 82 Figure 4.4 - Map With Rubber Band Zoom.................................................................................. 83 Figure 4.5 - Map After Rubber Band Zoom Completes ............................................................... 84 Figure 4.6 - Context Menu............................................................................................................ 84 Figure 4.7 - Incident Management Context Menu........................................................................ 85 Figure 4.8 - Video Switching Context Menu................................................................................ 85 Figure 4.9 - Video Wall Context Menu ........................................................................................ 86 Figure 4.10 - Preferences Context Menu ...................................................................................... 86 Figure 4.11 - DMS Context Menu ................................................................................................ 86 Figure 4.12 - TSS Context Menu.................................................................................................. 86 Figure 4.13 - CCTV Context Menu .............................................................................................. 86 Figure 4.14 - User Preference Selector ......................................................................................... 87 Figure 4.15 - Color Preference Selector ....................................................................................... 87 Figure 4.16 - Background Map Selection ..................................................................................... 87 Figure 4.17 - Link and Lane Name............................................................................................... 88 Figure 4.18 - Link Detail on Map ................................................................................................. 88 Figure 4.19 - Link Detail .............................................................................................................. 89 Figure 4.20 - TSS Detector Status ................................................................................................ 89 Figure 4.21 - DMS Control........................................................................................................... 89 Figure 4.22 - Detailed DMS Status............................................................................................... 90 Figure 4.23 - Detailed DMS Group Status.................................................................................... 91 Figure 4.24 - Detailed Pixel Status ............................................................................................... 91 Figure 4.25 - Detailed Lamp Status .............................................................................................. 92 Figure 4.26 - Detailed Fan Status ................................................................................................. 92 Figure 4.27 - Changing a DMS’s Operational Status ................................................................... 92 Figure 4.28 - Set Brightness.......................................................................................................... 93 Figure 4.29 - Send DMS Message ................................................................................................ 93 Figure 4.30 - Spelling Conflict ..................................................................................................... 94 Figure 4.31 - Managed Stored DMS Sequence ............................................................................ 95 Figure 4.32 - Manage Sequence – Sequence Selected.................................................................. 95 Figure 4.33 - Edit DMS Sequence ................................................................................................ 96 Figure 4.34 - Create Sequence Item.............................................................................................. 96 Figure 4.35 - New Sequence......................................................................................................... 97 Figure 4.36 - Camera Control ....................................................................................................... 98 Figure 4.37 - Set Operation Status................................................................................................ 99 Figure 4.38 - Video Switching - blank.......................................................................................... 99 Figure 4.39 - Video Switching - filled ........................................................................................ 100 Figure 4.40 - Video Tour Editor – blank .................................................................................... 100 Figure 4.41 - Video Tour Editor – filled..................................................................................... 101 Figure 4.42 - Video Wall Switching ........................................................................................... 101 Figure 4.43 - Manage Video Wall Layouts ................................................................................ 102 Figure 4.44 - Create New Event – blank..................................................................................... 103 Figure 4.45 - Create New Event -- filled .................................................................................... 103 Figure 4.46 - New Event Messages ............................................................................................ 103


SunGuide-SUM-1.0.0-Draft vii

Figure 4.47 - New Event in Event Manager List ........................................................................ 104 Figure 4.48 - Event Icon ............................................................................................................. 104 Figure 4.49 - Event Manager ...................................................................................................... 104 Figure 4.50 - Pre-defined Plans .................................................................................................. 105 Figure 4.51 - Edit Plans – pre-filled............................................................................................ 106 Figure 4.52 - Edit Plans – blank.................................................................................................. 107 Figure 4.53 - Available Plans...................................................................................................... 108 Figure 4.54 - Search for Resources............................................................................................. 109 Figure 4.55 - Available Resources.............................................................................................. 109 Figure 4.56 - Resource Editor with Contact ............................................................................... 110 Figure 4.57 - Contact Selection .................................................................................................. 110 Figure 4.58 - Route Selection ..................................................................................................... 111 Figure 4.59 - Edit Plans – blank.................................................................................................. 111 Figure 4.60 - General Tab – New Incident ................................................................................. 113 Figure 4.61 - Confirm False Alarm............................................................................................. 114 Figure 4.62 - General Tab – Confirmed Incident ....................................................................... 115 Figure 4.63 - Confirm Close Event............................................................................................. 116 Figure 4.64 - Location Tab ......................................................................................................... 116 Figure 4.65 - Select Route .......................................................................................................... 117 Figure 4.66 - Lane Configuration ............................................................................................... 117 Figure 4.67 - Weather Conditions............................................................................................... 118 Figure 4.68 - Type Specification Tab ......................................................................................... 119 Figure 4.69 - Vehicles Involved.................................................................................................. 120 Figure 4.70 - Type Specification Tab with Modifications.......................................................... 120 Figure 4.71 - Response Plans Tab............................................................................................... 121 Figure 4.72 - DMS Equipment List ............................................................................................ 122 Figure 4.73 - Edit DMS .............................................................................................................. 123 Figure 4.74 - Pre-defined Plans List ........................................................................................... 124 Figure 4.75 - Response Plans Tab............................................................................................... 125 Figure 4.76 - Associations Tab ................................................................................................... 126 Figure 4.77 - Event Selection...................................................................................................... 127 Figure 4.78 - Resources Tab ....................................................................................................... 128 Figure 4.79 - Contact Notification Option.................................................................................. 128 Figure 4.80 - Set Participant Status............................................................................................. 129 Figure 4.81 - History Tab............................................................................................................ 130


SunGuide-SUM-1.0.0-Draft viii

List of Acronyms

CCTV.........................Closed Circuit Television CPA............................Control Panel Applet DMS...........................Dynamic Message Sign EH ..............................Executive Handler FDOT .........................Florida Department of Transportation GDT ...........................Geographic Data Technologies GUI ............................Graphical User Interface HAR ...........................Highway Advisory Radio IP ................................Internet Protocol ITS..............................Intelligent Transportation Systems ITN.............................Invitation to Negotiate LAN ...........................Local Area Network PTMC.........................Portable Transportation Management Center RTMC ........................Regional Transportation Management Center RWIS..........................Roadway Weather Information System SL...............................Status Logger STMC.........................Satellite Transportation Management Center SUM...........................Software Users Manual SVG............................Scalable Vector Graphics TCP\IP........................Transmission Control Protocol/Internet Protocol TMC...........................Transportation Management Center TSS.............................Transportation Sensor Subsystem URL............................Uniform Resource Locator VS ..............................Video Switch VTMC........................Virtual Transportation Management Center WYSIWYG ………... What You See Is What You Get XML...........................eXtensible Markup Language


SunGuide-SUM-1.0.0-Draft ix

Revision History Revision Date Changes

1.0.0-Draft November 29, 2004 Initial Release


SunGuide-SUM-1.0.0-Draft 1

1. Scope

1.1 Document Identification This document serves as the Software Users Manual (SUM) for the SunGuideSM software.

1.2 Project Overview The Florida Department of Transportation (FDOT) is conducting a program that is developing SunGuideSM software. The SunGuideSM software is a set of Intelligent Transportation System (ITS) software that allows the control of roadway devices as well as information exchange across a variety of transportation agencies. The goal of the SunGuideSM software is to have a common software base that can be deployed throughout the state of Florida. The SunGuideSM software development effort is based on ITS software available from both the states of Texas and Maryland; significant customization of the software is being performed as well as the development of new software modules. The following figure provides a graphical view of the software to be developed:

Figure 1.1 - High-Level Architectural Concept



The SunGuideSM development effort spans approximately two years. After the development, the software will be deployed to a number of Districts and Expressway Authorities throughout Florida and support activities will be performed.

1.3 Related Documents The following documents were used to develop this document:

SwRI Qualification Response: Response to the Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: November 18, 2002.

SwRI Technical Proposal: Technical Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31, 2003.

SwRI Cost Proposal: Cost Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31, 2003.

SwRI BAFO letter: Southwest Research Institute® Proposal No. 10-35924, “Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System”, Reference: Negotiation Number: ITN-DOT-02/03-9025-RR, dated: May 5, 2003.

FDOT procurement document: Invitation To Negotiate (ITN), Negotiation Number: ITN-DOT-02/03-9025-RR, Statewide Transportation Management Center Software Library System, dated: October 21, 2002.

FDOT Scope of Services: Statewide Transportation Management Center Software Library System: Scope of Services, September 22, 2003.

FDOT Requirements Document: Statewide Transportation Management Center Software Library System: Requirements Specification, June 3, 2003.

Southwest Research Institute, TMC Software Study, November 15, 2001. Southwest Research Institute, Introduction to an Operational Concept For the Florida

Statewide Library, FDOT-OCD-1.0, March 31, 2002. World Wide Web Consortium (W3) website: http://www.w3.org. SunGuideSM Project website: http://sunguide.datasys.swri.edu.

1.4 Contacts The following are contact persons for the SunGuideSM software project:

Elizabeth Birriel, ITS Central Office, [email protected], 850-410-5606 Liang Hsia, FDOT Project Manager, [email protected], 850-410-5615 John Bonds, Senior ITS Specialist, [email protected], 408-873-2514 David Chang, ITS Specialist, [email protected], 850-410-5622 Steve Dellenback, SwRI Project Manager, [email protected], 210-522-3914 Robert Heller, SwRI Software Project Manager, [email protected], 210-522-3824



Charlie Wallace, PB Faradyne Deputy Project Manager, [email protected], 352-374-6635

John Schumitz, PB Faradyne Software Project Manager, [email protected], 301-816-1852

The following are contacts that will be used by the SunGuideSM software project team to assure consistency with other FDOT projects and FDOT procedures:

Dan Baxter, PB Farradyne, FDOT C2C Project, [email protected], 407-587-7809 David Lambert, University of North Florida, RWIS, [email protected], 904-620-3881 Bob Colins, PBS&J, Emergency Evacuation, [email protected], 850-575-1800 John Fain, FDOT, Comptroller, [email protected], 850-921-7332 Leslie Jacobson, PB Farradyne, Ramp Metering, [email protected], 206-382-5290



2. Software Summary

2.1 Software Application The SunGuideSM software is a set of Intelligent Transportation System (ITS) software that allows the control of roadway devices as well as information exchange across a variety of transportation agencies. The goal of the SunGuideSM software is to have a common software base that can be deployed throughout the state of Florida.

The various software applications utilize socket connections to communicate with each other, and transfer data via a standard format (Extensible Markup Language [XML]). Data is stored in an underlying Oracle database.

2.2 Software Organization and Overview of Operation The SunGuideSM software is comprised of various subsystems that interact with each other in a cooperative environment. Users will interact with these subsystems and the database through both browser- and Windows-based applications, described below.

• Executive Handler is a Windows-based application that enables execution control of other SunGuideSM subsystems, and operational status reporting from subsystem processes under its control.

• Status Logger is a set of Windows-based software tools that allows SunGuideSM applications to send status information to a central archive server, and display this information to the user within a viewer.

• The Administrative Editor is a web-based application (meaning it is accessible from a web browser) that provides an interface to the database, allowing the user to add, modify, and delete user- and equipment-related data to/from the database.

• The Operator Map is a browser-based application and the primary user-interface, providing a means by which SunGuideSM software users may observe current traffic operations and field equipment status and manipulate field equipment to both gather and disseminate pertinent data.

• The Link Editor is a browser-based application that works in conjunction with the Operator Map, providing a means for configuring the map interface with respect to roadway links and shield icons.

2.3 Contingencies and Alternate States and Modes of Operation FDOT has defined four types of Traffic Management Centers (TMCs) that will operate the SunGuideSM software:

• RTMC: Regional Transportation Management Center • STMC: Satellite (or Secondary) Transportation Management Center • VTMC: Virtual Transportation Management Centers • PTMC: Portable Transportation Management Centers



The following table provides a brief comparison of the four types of TMC configurations possible with the SunGuideSM software:

Table 2.1 - SunGuideSM Deployment Alternatives

Data Bus Number of

Devices Controlled

Supports GUI

Access Platform Subsystems

Deployed

Device Driver

Deployment

RTMS Uses own Large Yes Multi Server typical

All All

STMC Shares RTMC

Data Bus Moderate No

Single or multiple Server

Single or multiple One or two

VTMC None. None No Desktop / Laptop None None

PTMC Uses own Small Yes Laptop All All

The following sections describe how the SunGuideSM software would be deployed in each of these four types of centers.

2.3.1 Regional Transportation Management Center RTMCs will serve as hubs for command and control decisions for deployments that have significant amounts of ITS field devices deployed. An RTMC will typically have multiple SunGuideSM application servers that are connected to a Local Area Network (LAN) within the RMTC that provides access to the various ITS devices deployed in the field. It is expected that an RTMC will have an operations room that has a number of operator workstations deployed. An RTMC is distinguished from other types of centers in that it will typically control the network access to a number of ITS field devices.

2.3.2 Satellite Transportation Management Center STMCs are deployments where ITS field equipment is connected to the network local to the STMC. STMCs would be deployed when device connectivity is centered on remote buildings and the cost of extending the network to the RTMC outweighs the deployment of SunGuideSM servers in an STMC to provide local communications to the devices. An STMC does not provide a user interface, it is simply a device collection implementation of SunGuideSM.

The STMC will utilize the Data Bus of an RTMC as its master data repository and the STMC will simply be an extension of the RTMC. When an STMC is deployed, the subsystem and drivers required to operate the equipment connected to the STMC should be deployed on a SunGuideSM application server physically in the STMC. The SunGuideSM application server



would then make a connection to an RTMC for its central data services. In this context, the STMC does not require a database locally within the STMC. The following figure depicts the relationship between an RTMC and STMC:

Figure 2.1 - Relationship Between an RTMC and STMC

2.3.3 Virtual Transportation Management Center VTMCs are deployments that utilize the SunGuideSM browser interface to perform SunGuideSM operations from other facilities. Although the user is physically located outside the RTMC, the browser access makes his/her location transparent.

2.3.4 Portable Transportation Management Center PTMCs are deployments that utilize laptop computers to provide “mini” SunGuideSM deployments that are used for demonstration, interim operations or field debugging of software. The SunGuideSM software can operate on a single computer; the limiting factors are the size of the database and the number of ITS field devices that the PTMC is attempting to control.

When deploying a PTMC, the number of ITS devices should be limited to twenty and minimal data archiving should be initiated. When using a PTMC, all of the configuration that must be performed for an RTMC must be performed for the PTMC (there should be less of it since fewer devices are supported).

As an example, an operational use of a PTMC may include a construction project where it is known that network connectivity to the RTMC will be lost from a cluster of devices. In this situation, the operational staff will know what devices will be isolated so that the PTMC may be configured prior to deploying in the field. This type of configuration includes device addresses, type, attributes, etc. The PTMC will have its own database and if standard messages are desired, the message database would need to be populated with these messages.

Since the PTMC is a SunGuideSM implementation, all functionality of SunGuideSM is available within the PTMC. This implies that a C2C connection could be established between the PTMC and the C2C infrastructure, but performance limitations of the PTMC host computer limit how much data is exchanged between the PTMC and the C2C infrastructure (but again, this data is configurable by the SunGuideSM administrator.



2.4 Security and Privacy The SunGuideSM software assumes a network environment that will support the exchange of Transmission Control Protocol/Internet Protocol (TCP/IP) packets between SunGuideSM applications. No specific security (other than the encryption of passwords) is performed by the SunGuideSM software. If additional network security is required by a deploying organization, a careful analysis of how data will be exchanged needs to be made when the implementation plan for the deployment is developed.



3. System Administration The following sections describe the System Administration functions of the SunGuideSM

software. The text in bold is referencing a ‘button’ on the Graphical User Interface (GUI).

3.1 Subsystem Control with Executive Handler Executive Handler (EH) is a set of applications that enables users to control the execution of other SunGuideSM subsystems, and the operational status reporting of these controlled subsystems processes. Specifically, the Executive Handler Server has the following capabilities:

• Automatic execution control of subsystem processes. • On-demand execution control of subsystem processes by an operator. • Viewing of subsystem process operational status, listed by hosting workstation. • On-demand updating of the logging level in use by executing subsystem processes.

Executive Handler is comprised of a Server, Editor, and Viewer, described in the following sections.

3.1.1 Executive Handler Editor The Executive Handler Editor allows the user to specify which processes are to be controlled by the Executive Handler, and to establish the criteria by which these processes will be controlled. The list of processes as well as their control options may be modified via the editor.

3.1.1.1 Software Familiarization The Executive Handler Editor is started by pressing the Windows Start button, selecting the All Programs→ SunGuideSM menu, then selecting Executive Handler Editor application. Figure 3.1 depicts the user interface of the Executive Handler’s Process List Editor upon startup.

Figure 3.1 - Process List Editor



This application may be exited by clicking on either the OK or Cancel button, or by clicking on the ‘X’ at the upper-right corner of the window. Selecting the Add button invokes the add process dialog that is described in Section 3.1.1.2. If process parameters are to be altered then the process is selected (using the left mouse button) and the Edit button should be selected, the dialogs shown in Section 3.1.1.2 will be displayed. If a process is to be deleted, the process should be selected (using the left mouse button) and the Delete button selected. The Up Arrow and Down Arrow keys can be used to move processes up and down in the list, select the process to be moved (using the left mouse button) and press the up and down arrows until it is placed where desired.

3.1.1.2 Processing Procedures Upon starting the application, the editor window displays a list of processes to be controlled by the Executive Handler. Additional processes may be added to this list, and their control options may be modified. From the editor, the user may also discontinue process control for a particular process, as well as order the list of processes. Selecting the Add option in the main editor (see Figure 3.1) window will display the dialog as shown in Figure 3.2.

Figure 3.2 - Add Process – Blank The user should select the Process Type and Subsystem, and fill in the values for Application Executable, Display Name, Working Directory, and Arguments. The Browse button will bring up a file or service list dialog depending on the selected process type, allowing the user to view the directories on the server and select the appropriate executable or Windows service. The Subsystem dropdown will display a list of the systems known to the editor; this list, which will be defined during installation and should not need subsequent modifications, is stored in the SubSystemList.txt file located in the same directory as the Executive Handler Editor application.

The user may specify whether or not the process should startup automatically on server reboot. Reboot refers to the Executive Handler stop and restart, which could occur as a result of the user stopping and restarting the service in the Windows Services applet, or from a hardware reboot.



However, when the Executive Handler Server is started, the EH Server, upon startup, will startup processes under its control that are flagged with the automatic restart option. Such processes should show a Startup Type of Manual in the Windows Services applet.

The user may also specify whether or not to shutdown and restart the process on a timeout. Timeout refers to the SunGuideSM system heartbeat, where processes report to the Executive Handler on a periodic basis. If a subsystem set for restart on timeout fails to report within a specified time period, the process will be stopped and restarted automatically by the Executive Handler. Selecting Cancel will cause the dialog to close without saving any data. An example dialog with data entered is shown in Figure 3.3.

Figure 3.3 - Add Process – Detail The user may choose to cancel this operation, or select OK to save the new settings. After selecting OK, the newly added process will display in the editor’s process list if no errors occur. The user must then stop and restart the Executive Handler Server (service) so that it will recognize these configuration changes. Selecting Cancel will cause the dialog to close without saving data.

Editing a process will display the same dialog as in Figure 3.3. However, the Process Type and Application Executable options will be disabled. Only the remaining fields may be modified.

3.1.2 Executive Handler Server The Executive Handler Server controls other SunGuideSM processes established in the process list of the Executive Handler Editor.

3.1.2.1 Software Familiarization

The Executive Handler Server is started and stopped via the Services window found in the system Control Panel. To open the Services window, press the Windows Start button, select Control Panel, then Administrative Tools, and finally, Services. Executive Handler should be in the Services list, and its Startup Type should be set to Automatic. If needed, the server may be stopped and restarted manually from the Control Panel.



Figure 3.4 - Executive Handler Service

3.1.2.2 Processing Procedures There are no other processing procedures for this application.

3.1.3 Executive Handler Viewer The Executive Handler Viewer allows the user to monitor the various SunGuideSM system processes currently running, and to filter the view of these processes.

3.1.3.1 Software Familiarization The Executive Handler Viewer is started by pressing the Windows Start button, selecting the All Programs→ SunGuideSM menu, then selecting Executive Handler Viewer application. The application may be exited either by selecting the File, Exit menu option, or by clicking on the ‘X’ at the upper-right corner of the window.

Process status and connection information are highlighted in different colors depending on its value. Normal status and connection state are shown on a green background, problem situations are shown on a yellow background, and fatal errors or disconnected states are shown on a red background.

3.1.3.2 Processing Procedures

Figure 3.5 depicts the user interface of the Executive Handler’s Viewer upon startup.



Figure 3.5 - Executive Handler Viewer

By default, the viewer comes up in Host List view. The status and other pertinent information are displayed for each process currently under Executive Handler control.

The viewer provides numerous menu options which are described in detail in the following sections.

3.1.3.2.1 File Menu The File Menu of the Executive Handler Viewer is shown in Figure 3.6, and its options are described in the following sections.

Figure 3.6 - File Menu

3.1.3.2.1.1 Add New Host This option is available only when in the Host List Window view, and it allows the user to add a new host to the list of server/host machines on which controlled processes reside. Selecting this option causes the dialog in Figure 3.7 to be displayed:



Figure 3.7 - Add New Host The user should enter either the host machine name or its Internet Protocol (IP) address in the entry field. Clicking on the Browse button will bring up a directory tree listing so that the desired machine may be found over a network. Entering the data and selecting OK will cause the new host name to appear in the viewer’s host list. The shortcut for this option is Ctrl+A.

3.1.3.2.1.2 Connect/Disconnect All Selecting the Connect All option will cause the Executive Handler Viewer to connect to all of the listed host machines. Conversely, selecting the Disconnect All option will cause the Executive Handler Viewer to disconnect from all of the listed host machines.

3.1.3.2.1.3 Exit Exit may be selected to close the Executive Handler Viewer application.

3.1.3.2.2 Host Menu The Host Menu of the Executive Handler Viewer is shown in Figure 3.8. Options are enabled only if the Window view has been set to Host List, and a host machine has been selected in the viewer. This same menu will popup if, in the same view, the user right-clicks on a host machine’s name.

Figure 3.8 - Host Menu Options for this menu are described in the following sections.

3.1.3.2.2.1 Connect/Disconnect These options are mutually exclusive, and will be enabled appropriately based on the current connection status of the viewer to the selected host machine.



3.1.3.2.2.2 Start/Stop All The user may quickly start or stop the processes related to a specific host machine by selecting the appropriate option here.

3.1.3.2.2.3 Delete This option allows the user to disconnect from the selected host and remove the host name from the list. On choosing this option, the dialog in Figure 3.9 will be displayed:

Figure 3.9 - Delete Host Confirmation The user may press OK to continue this operation, or Cancel to discontinue.

3.1.3.2.3 Sub-system Menu The Subsystem Menu of the Executive Handler Viewer is shown in Figure 3.10. Options are enabled only if the Window view has been set to Sub-system List, and a subsystem has been selected in the viewer. This same menu will popup if, in the same view, the user right-clicks on a subsystem’s name.

Figure 3.10 - Sub-system Menu Options for this menu are described in the following sections.

3.1.3.2.3.1 Start/Stop All Selecting one of these options will cause all processes within each subsystem under Executive Handler control to be either started or stopped.

3.1.3.2.4 Process Menu The Process Menu of the Executive Handler Viewer is shown in Figure 3.11. Options are enabled only if a process has been selected in the viewer. This same menu will popup if the user right-clicks on a process name in the viewer. For running processes, the menu displays as in the figure; however, if the selected process is not currently running, only the Start menu option is enabled.



Figure 3.11 - Process Menu Options for this menu are described in the following sections.

3.1.3.2.4.1 Start/Stop Selecting either of these two mutually exclusive options will start/stop the selected process. Only the applicable option will be enabled.

3.1.3.2.5 Set Log Level This option allows the user to adjust the log level for the selected process. When selected, the dialog in Figure 3.12 is shown:

Figure 3.12 - Log Level Options include: slInfo, slWarn, slError, slDebug, and slDetail. slInfo represents the least amount of detail, and slDetail signifies the greatest amount; other values represent increasing levels of detail from slInfo to slDetail. To set the new logging level, the user clicks the OK button; alternatively, the user may select Cancel to terminate the operation without modifying the log level. Once modified, the new logging level will be picked up automatically by Status Logger.

3.1.3.2.5.1 Enable/Disable Validation These options refer to XML validation, and are used primarily during software development. These features are left in place in the release software to aide in error-tracking if needed.

3.1.3.2.6 View Menu The View Menu of the Executive Handler Viewer is shown in Figure 3.13. All options are always enabled.



Figure 3.13 - View Menu Options for this menu are described in the following sections.

3.1.3.2.6.1 Expand/Collapse All These mutually exclusive options cause the processes under the highest level items, either subsystems or hosts, depending on the view, to either expand so that all can be seen, or collapse so that all are hidden.

3.1.3.2.6.2 Status Bar This option shows or hides the Status Bar from the bottom of the application window.

3.1.3.2.7 Window Menu The Window Menu of the Executive Handler Viewer is shown in Figure 3.14. All options are always enabled.

Figure 3.14 - Window Menu Options for this menu are described in the following sections.

3.1.3.2.7.1 Host List

Selecting this option causes the processes to be listed under their respective host machines.

3.1.3.2.7.2 Sub-system List Selecting this option causes the processes to be listed under their respective subsystems. Figure 3.15 shows an example of this view.



Figure 3.15 - Subsystem List View

3.1.3.2.7.3 Next This option causes the Window List view to alternate between the Host and Sub-System List views. The shortcut for this option is Ctrl+Tab.

3.1.3.2.8 Help Menu The Help Menu of the Executive Handler Viewer is shown in Figure 3.16.

Figure 3.16 - Help Menu Options for this menu are described in the following sections.

3.1.3.2.8.1 About ExecHandler Viewer Select this menu option to view a dialog containing Executive Handler Viewer version and copyright information.

3.2 Subsystem Monitoring with Status Logger Status Logger (SL) is a set of applications that enables subsystems to log status information to a central location, and users to view the logged information. Specifically, Status Logger has the following capabilities:

• Provide client applications with several different “levels” of messages. • Accept messages from client applications and archive (log) them to the server's file

system. • Provide a mechanism for configuring the Status Logger Server, the Status Logger

Configuration component. • Provide a viewer to view the logged messages, the Status Logger Viewer component.

Status Logger is comprised of a Server, Control Panel applet, and Viewer, described in the following sections.



3.2.1 Status Logger Server The Status Logger Service handles the collection of status information received from the various subsystems, and generates log files based on the information gathered.

3.2.1.1 Software Familiarization The Status Logger Service runs as a Windows service. During SunGuideSM installation, the SL Server will have been configured to startup automatically, so the user should not have to start this application. If there is a need to stop and restart the SL Server at any time, it may be accessed through Control Panel, Services, as shown in Figure 3.17.

Figure 3.17 - Status Logger Service

3.2.1.2 Processing Procedures There are no other processing procedures for this application.

3.2.2 Status Logger Control Panel Applet The Control Panel Applet (CPA) handles Status Logger configuration. The following sections describe using the CPA.

3.2.2.1 Software Familiarization The Control Panel Applet is accessible via the Windows Control Panel, as shown in Figure 3.18.



Figure 3.18 - Control Panel

3.2.2.2 Processing Procedures As is shown in Figure 3.19, the CPA allows the user to specify the directory where log files will be located, the frequency within which new log files will be generated, whether or not to reuse log files, and whether or not to use separate log files for each process/subsystem (and to name them according to the process names).



Figure 3.19 - Status Logger Control Panel Applet Selecting OK will save these changes to the Windows Registry; selecting Cancel will exit the application without saving these changes.

3.2.3 Status Logger Viewer The Status Logger handles the display of the various log files generated by the SL Server application, enabling the user to monitor the status of the subsystems.

3.2.3.1 Software Familiarization The SL Viewer is started by pressing the Windows Start button, selecting the All Programs→ SunGuideSM menu, then selecting Status Logger Viewer application. The application may be exited either by selecting the File, Exit menu option, or by clicking on the ‘X’ at the upper-right corner of the window.

Status types are color-coded with informational messages at the highest level of detail in green, warning messages in yellow, error messages in red, detail messages in dark gray, and debugging messages at the lowest level of detail in light gray.

3.2.3.2 Processing Procedures

Upon starting the application, a window similar to that in Figure 3.20 will be shown.



Figure 3.20 - Status Logger

The viewer displays a variety of process/subsystem status information, such as process name, status, host machine, and message. The display may be configured according to user specifications. The SL Viewer provides numerous menu options for configuring the display; these options are described in detail in the following sections.

3.2.3.2.1 File Menu The File Menu of the Status Logger Viewer is shown in Figure 3.21, and its options are described in the following sections.

Figure 3.21 - File Menu

3.2.3.2.1.1 Connect This option allows the user to locate and view log files either on their local computer or a remote one. Selecting this option causes the dialog in Figure 3.22 to be displayed:



Figure 3.22 - Connect If connecting to a remote computer, the user must enter the remote computer name and domain, as well as a valid user account name and password.

3.2.3.2.1.2 Open This portion of the menu enables the user to select a log file by day on the currently connected computer, or to open a specific log file on a network-accessible computer to which the user has access, via an Open File dialog box. The shortcut for this option is Ctrl+O.

3.2.3.2.1.3 Save as Text This portion of the menu enables the user to save a highlighted text in the viewer to a text file. Selecting this option will display a File Dialog window in which the user may select the location and name of the text file to be created.

3.2.3.2.1.4 Exit The user may select this option in order to exit the application.

3.2.3.2.2 Edit Menu The Edit Menu of the Status Logger Viewer is shown in Figure 3.23, and its options are described in the following sections.

Figure 3.23 - Edit Menu

3.2.3.2.2.1 Copy This is currently the only option under this menu, and it allows the user to copy highlighted text from the viewer to the Windows Clipboard. This functions essentially the same as the File, Save



as Text option, but uses the Clipboard as the copy destination rather than a text file. Ctrl-C serves as a shortcut to this menu option.

3.2.3.2.3 View Menu The View Menu of the Status Logger Viewer is shown in Figure 3.24, and its options are described in the following sections.

Figure 3.24 - View Menu

3.2.3.2.3.1 Status Bar This option allows the user to toggle the Status Bar display at the bottom of the Viewer window on or off.

3.2.3.2.3.2 Detail Columns This option allows the user to toggle the display of detail columns in the Viewer window on or off. The detail columns are the Event Description, Event ID, and Code columns.

3.2.3.2.3.3 Refresh This option forces an immediate update of the Viewer display, as opposed to waiting for the automatic update that occurs at a specified time interval. F5 serves as a shortcut to this menu option.

3.2.3.2.3.4 Refresh Options This option causes the dialog shown in Figure 3.25 to display, allowing the user to specify whether or not they want the SL Viewer to automatically update/refresh the content that it displays, and if so, how often.

Figure 3.25 - Refresh Options



3.2.3.2.3.5 Filter Options This option allows the user to filter the display in the Viewer using the dialog shown in Figure 3.26

Figure 3.26 - Filter Options Within this dialog, the user is able to select the following SL Viewer filter options:

• Either ignore the time that a specific message was logged or use a specific time range. • Show messages containing a particular string, and specify whether or not the search is

case-sensitive. • Either ignore the event code for messages or search for messages with event codes within

a specific range. • Show messages containing a particular event ID, and specify whether or not the search is

case-sensitive. • Show messages containing a particular event description, and specify whether or not the

search is case-sensitive. • Select the types of messages to display based on message priority level. • Either ignore process names or specify processes of interest.



• Either ignore host computer names or specify computers of interest. • Either ignore users or specify users of interest.

Note that when an option is ignored above, the option is not used for filtering, therefore all items within that category are displayed. The user may press the OK button to apply the filter, or Cancel to remove the dialog.

3.2.3.2.4 Help Menu The Edit Menu of the Status Logger Viewer is shown in Figure 3.27, and its options are described in the following sections.

Figure 3.27 - Help Menu

3.2.3.2.4.1 About StatusLogViewer Select this menu option to view a dialog containing Status Logger Viewer version and copyright information.

3.3 Data Administration with Administrative Editor

The Administrative Editor is actually a collection of numerous editors allowing the user to manipulate user and equipment data in the database. Specifically, the Administrative Editor application allows operators to:

• Add/delete/modify users. • Add/delete/modify permission groups. • Add/delete/modify permission settings for users and groups. • Add/delete/modify dynamic message signs. • Add/delete approved words. • Add/delete/modify cameras and other video sources. • Add/delete/modify video destinations. • Define traffic sensor links associated with highways/roadways. • Add/delete/modify traffic detectors. • Map detectors to the links and lanes they occupy. • Add/delete/modify travel time links. • Add/delete/modify roadways and their alternate routes. • Add/delete/modify contacts.

The startup page and these various editors are described below.

3.3.1 Software Familiarization

The Administrative Editor is started by opening a web browser and navigating to the appropriate Uniform Resource Locator (URL); it is closed by simply closing the browser window. Figure 3.28 depicts the user interface of the Administrative Editor upon startup. The list frame contains a list tree with the editor categories: User Management, Device Management, and Incident



Management. Under each category are the specific editors that may be chosen. The main editor frame will be blank until a link in the editor list frame is followed.

Figure 3.28 - Status Interface Test Client after Startup On the various editor pages described in the sections below, the Administrative Editor uses a green background on fields that are read-only; editable fields use the same color background as the rest of the page. Informational and error messages are logged to the Status Logger, and are also displayed on the editor page where appropriate.

3.3.2 Processing Procedures

3.3.2.1 User Editor The User Editor enables the system user to manipulate user data in the database. This editor is opened by expanding the User Management element of the Editor List Frame, then clicking on Users (Figure 3.29). The Administrative Editor will query the database and retrieve a list of all users currently in the database.

Main Editor Frame

Editor List Frame



Figure 3.29 - User List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified; the Add and Edit options both route to the same page, with only a few differences in the display.

When adding a new user (see Figure 3.30), the page is initially loaded with the list of permission groups that currently reside in the database, as well as the list of the permissions (by subsystem) that are in the database. The permission settings are initially deselected (or set to false). Once a group is selected, the permission settings are set on or off, based on the default settings for that group. Individual permissions may then be selected/deselected specifically for the current user. Clicking on the Reset Permissions button will cause the permission settings shown on the screen to be reset to the default values for the currently selected group.



Figure 3.30 - Add User

When editing an existing user (see Figure 3.31), the page is initially loaded with the user’s name and other vital information, and with a list of permission groups that currently reside in the database, with the user’s currently assigned group selected. The user's current list of permissions (by subsystem) is also displayed, showing their individual settings. If the user is assigned to a different group, the permission settings are adjusted based on the default settings for the newly selected group. Individual permissions may then be selected/deselected specifically for the current user. Clicking on the Reset Permissions button will cause the permission settings shown on the screen to be reset to the values stored in the database for the current user.



Figure 3.31 - Edit User Operations may be cancelled without altering the database by clicking on the Cancel button; alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. For users, Email and Location fields are optional; all others are required. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. It is important to note that while errors may occur in writing individual permission settings to the database, this is not considered a critical error so processing does not terminate. Other permissions may write to the database successfully, so no rollback occurs on error; successful writes will be committed to the database, while unsuccessful writes will be logged for the user. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new user was created, the user will see the name of this new user in the list on the list page.

3.3.2.2 Group Editor The Group Editor (see Figure 3.32) enables the system user to manipulate permission group data in the database. This editor is opened by expanding the User Management element of the Editor List Frame, then clicking on Groups. The Administrative Editor will query the database and retrieve a list of all groups currently in the database.



Figure 3.32 - Group List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified; the Add and Edit options both route to the same page, with only a few differences in the display.

When adding a new group (see Figure 3.33), the page is initially loaded with the list of all permissions (by subsystem) that are in the database. All permission settings are initially deselected (or set to false). Individual permissions may be selected/deselected specifically for the current group. Selecting the Reset Permissions button will cause the permission settings shown on the screen to be cleared (deselected).



Figure 3.33 - Edit Group

When editing an existing group, the page is initially loaded with the group’s name and description, and a current list of permissions (by subsystem) for this group, showing their individual settings. Individual permissions may be selected/deselected specifically for the current group. Clicking on the Reset Permissions button will cause the permission settings shown on the screen to be reset to the values stored in the database for the current group.

All operations may be cancelled without altering the database by clicking on the Cancel button; alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. It is important to note that while errors may occur in writing individual permission settings to the database, this is not considered a critical error so processing does not terminate. Other permissions may write to the database successfully, so no rollback occurs on error; successful writes will be committed to the database, while unsuccessful writes will be logged for the user. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors



as well as successful database access will result in browser redirection to the previous list page. If a new group was created, the user will see the name of this new group in the list on the list page.

3.3.2.3 Operator Workstation Editor The Operator Workstation Editor (see Figure 3.34) enables the system user to add and remove workstations to/from the database, and to associate monitors (video destinations) with these workstations. This editor is opened by expanding the User Management element of the Editor List Frame, then clicking on Operator Workstations. The Administrative Editor will query the database and retrieve a list of all workstations currently in the database.

Figure 3.34 - Workstation List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.



Whether adding or editing a workstation (see Figure 3.35), the page is initially loaded with a list of available (i.e., not yet associated with a workstation) monitors that are in the database. When adding, the list of associated monitors will be blank; when editing, the list is filled with the names of monitors currently associated with the selected workstation. The Workstation Name field is editable only when adding a new workstation.

Figure 3.35 - Edit Workstation

Operations may be cancelled without altering the database by clicking on the Cancel button; alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new workstation was created, the user will see the name of this new workstation in the list on the list page.

3.3.2.4 Sign Editor The Sign Editor (see Figure 3.36) enables the system user to manipulate Dynamic Message Sign (DMS) data in the database. This editor is opened by expanding the DMS element of the Editor List Frame, then clicking on Signs. The Administrative Editor will query the database and retrieve a list of signs currently in the database.



Figure 3.36 - Sign List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page (see Figure 3.37) allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.



Figure 3.37 - Edit Sign Many of the dropdowns are populated with values from the database. Changes to selections for Address Types 1 and 2 cause dynamic changes to the page below these fields – labels and associated fields will be displayed based on Address Type 1 and 2 selections. The Sign Name field is editable only when adding a new sign.

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new sign was created, the user will see the name of this new sign in the list on the list page.



3.3.2.5 Approved Word Editor The Approved Word Editor (see Figure 3.38) enables the system user to add or remove approved words for DMS messages to/from the database. This editor is opened by expanding the DMS element of the Editor List Frame, then clicking on Approved Words. The Administrative Editor will query the database and retrieve a list of approved words currently in the database.

Figure 3.38 - Approved Word List The Add button is always enabled; once a word is selected in the list, the Delete button is also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting Add, the page will redirect to another page (see Figure 3.39) allowing detailed data to be entered.



Figure 3.39 - Edit Approved Word

The only operation the user may perform here is to enter a new word. This operation may be cancelled without altering the database by clicking on the Cancel button; alternatively, the data on the screen can be submitted to the database via selection of the Save and Exit button. When saving, the required word field will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new word was created, the user will see the name of this new word in the list on the list page.

3.3.2.6 Camera Editor The Camera Editor (see Figure 3.40) enables the system user to manipulate camera (i.e., video source) data in the database. This editor is opened by expanding the Closed Circuit Television (CCTV)/Video Switch (VS) element of the Editor List Frame, then clicking on Cameras. The Administrative Editor will query the database and retrieve a list of cameras currently in the database.



Figure 3.40 - Camera List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.

Many of the dropdowns are populated with values from the database. Changes to selections for Address Types 1 and 2 cause dynamic changes to the page below these fields – labels and associated fields will be displayed based on Address Type 1 and 2 selections. The Camera Name field is editable only when adding a new camera.

Cameras may be attached to video devices. If they are not, the camera’s address must be stored in the database. Figure 3.41 shows the camera editor page when no device is attached.



Figure 3.41 - Edit Camera If the camera is attached to a video device, the user must specify whether this device is an encoder or a switch. Figure 3.42 shows the page when an encoder is attached.



Figure 3.42 - Edit Camera with Encoder Figure 3.43 shows the edit camera page when a switch is attached.



Figure 3.43 - Edit Camera with Switch

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new camera was created, the user will see the name of this new camera in the list on the list page.

3.3.2.7 Video Destination Editor The Video Destination Editor (Figure 3.44) enables the system user to manipulate video destination data in the database. This editor is opened by expanding the CCTV/VS element of the Editor List Frame, then clicking on Video Destinations. The Administrative Editor will query the database and retrieve a list of the video destinations currently in the database.



Figure 3.44 - Video Destination List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.

Figure 3.45 shows an encoder as the video device type, along with encoder-related fields. Selecting a switch device type will cause the display to change dynamically, showing switch-related fields.



Figure 3.45 - Edit Video Destination The Manufacturer and Model dropdowns are populated with values from the database. Selection of a manufacturer causes the model list to be re-populated with values applicable to the current manufacturer selection. The Name field is editable only when adding a new video destination.

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new video destination was created, the user will see the name of this new destination in the list on the list page.

3.3.2.8 Roadway Editor The Roadway Editor (Figure 3.46) enables the system user to manipulate roadway data in the database. This editor is opened by expanding the Transportation Sensor Subsystem (TSS)



element of the Editor List Frame, then clicking on Roadways. The Administrative Editor will query the database and retrieve a list of the roadways currently in the database.

Figure 3.46 - Roadway List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page (see Figure 3.47) allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.



Figure 3.47 - Edit Roadway The Roadway Description field is editable only when adding a new roadway. The user may enter a short name for this roadway, and select alternate routes to be associated with this roadway from the list of available routes. Routes may be moved from the available list to the alternate list, and vice-versa, by selecting the desired route in the list, then clicking on either the left-arrow/Add button or the right-arrow/Remove button.

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new roadway was created, the user will see the name of this new roadway in the list on the list page.



3.3.2.9 Detector Editor The Detector Editor enables the system user to manipulate traffic detector data in the database. This editor is opened by expanding the TSS element of the Editor List Frame, then clicking on Detectors (see Figure 3.48). The Administrative Editor will query the database and retrieve a list of the detectors currently in the database.

Figure 3.48 - Detector List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified (see Figure 3.49). The Add and Edit options both route to the same page, with only a few differences in the display.



Figure 3.49 - Edit Detector Many of the dropdowns are populated with values from the database. Changes to the Address Type selection cause dynamic changes to the page below this field – labels and associated fields will be displayed based on Address Type selection. The Detector Name field is editable only when adding a new detector.

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new detector was created, the user will see the name of this new detector in the list on the list page.

3.3.2.10 Detector Map Editor The Detector Map Editor enables the system user to manipulate detector mapping data in the database. This editor is opened by expanding the TSS element of the Editor List Frame, then clicking on Detector Maps (see Figure 3.50). The Administrative Editor will query the database and retrieve a list of the detectors currently in the database.



Figure 3.50 - Detector List Once a name is selected in the list, the Map button will become enabled. Detector maps may be modified, but not deleted.

Figure 3.51 shows the map detector page for a single detector. Links associated with this detector are shown in the Links list; all other fields are empty since there are no further selections yet. The Detector Name field is read-only.



Figure 3.51 - Edit Detector Mapping If a link is selected, lanes associated with this link will be displayed in the Lanes list, and a speed associated with this link, if any, will be displayed on the page as well (see Figure 3.52).



Figure 3.52 - Edit Detector Mapping – Select Link Clicking on the Add Link button will cause the fields below the Link list to become enabled, and the Add Link button to change to an OK button (see Figure 3.53). A suggested link name is generated and displayed in the New Link Name field. The user should enter a Speed Limit for this link, modify the link name if desired, and then choose OK to save this new data. After a successful add operation, the new link’s name will display in the Link list and the OK button will revert back to an Add Link button. If instead the user wants to cancel the add link operation, they may click the Cancel button.



Figure 3.53 - Edit Detector Mapping – Add Link Selecting a lane will cause the data associated with this lane to be displayed on the page in the fields below the Lane list (see Figure 3.54).



Figure 3.54 - Edit Detector Mapping – Select Lane Clicking on the Add Lane button will cause the fields below the Lane list to become enabled and the Add Lane button to change to an OK button (see Figure 3.55). A suggested lane name is displayed in the New Lane Name field. Users should enter a zone number and description, modify the lane name if desired, and then click on OK to save this data to the database. After a successful add operation, the new lane’s name will display in the Lane list and the OK button will revert back to an Add Lane button. If instead the user wants to cancel the add lane operation, they may click the Cancel button.



Figure 3.55 - Edit Detector Mapping – Add Lane Users are not allowed to modify or delete detector mappings via this editor – such changes require direct manipulation of database tables.

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page.

3.3.2.11 Highway Definition Editor The Highway Definition Editor enables the system user to define a highway by specifying an ordered list of TSS links (see Figure 3.56). This editor is opened by expanding the TSS element of the Editor List Frame, then clicking on Highway Definitions. The Administrative Editor will query the database and retrieve a list of the highways/roadways currently in the database.



Figure 3.56 - Highway List The Define button is always enabled; there are no Add, Edit and Delete buttons for this option. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting Define, the page will redirect to another page allowing detailed data to be entered/modified (see Figure 3.57).



Figure 3.57 - Define Highway

The Highway Name field is always read-only. TSS links may be associated with this highway by selecting them in the available link list and moving them to the associated link list using the left-arrow button; alternatively, links may be moved from the associated list to the available list using the right-arrow button. Links in the associated link list may be ordered using the up-arrow and down-arrow buttons. Figure 3.58 shows an example of a defined highway.



Figure 3.58 - Highway Defined with Links

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page.

3.3.2.12 Travel Time Link Editor The Travel Time Link Editor enables the system user to manipulate travel time link data in the database (see Figure 3.59). This editor is opened by expanding the Travel Time element of the Editor List Frame, then clicking on Travel Time Links. The Administrative Editor will query the database and retrieve a list of the links currently in the database.



Figure 3.59 - Travel Time Link List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display (see Figure 3.60).



Figure 3.60 - Edit Travel Time Link The Travel Time Link Name field is editable only when adding a new travel time link. Selecting a link in the associated list causes the Link Length input field and the Add/Modify Link Length button to become enabled. Clicking on the Add/Modify Link Length button will cause the link length to be modified internally only – changes are not saved to the database until the Save button is clicked.

Links may be moved from the available list to the associated list, and vice-versa, by selecting the desired link in the list (see Figure 3.61), then clicking on either the left-arrow button (to add the item) or the right-arrow button (to remove the item).



Figure 3.61 - Edit Travel Time Link – Select Link

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new travel time link was created, the user will see the name of this new link in the list on the list page.

3.3.2.13 Contact Editor The Contact Editor enables the system user to manipulate contact data in the database. This editor is opened by expanding the Incident Management element of the Editor List Frame, then clicking on Contacts (see Figure 3.62). The Administrative Editor will query the database and retrieve a list of the contacts currently in the database.



Figure 3.62 - Contact List The Add button is always enabled; once a name is selected in the list, the Edit and Delete buttons are also enabled. The Delete operation is the same for all editors, and is discussed in Section 3.3.2.14 below. Upon selecting either Add or Edit, the page will redirect to another page allowing detailed data to be entered/modified. The Add and Edit options both route to the same page, with only a few differences in the display.

Figure 3.63 shows an example of adding a new contact. The page displays with all fields enabled and blank.



Figure 3.63 - Add Contact - Blank The user should enter all information to be stored in the database for this contact, then click the Save and Exit button (see Figure 3.64).

Figure 3.64 - Add Contact - Filled



Entry errors, such as a missing value for a required field, will be displayed on the page (see Figure 3.65). The user should correct these errors and attempt to save again.

Figure 3.65 - Add Contact – Field Entry Error If other errors occur, such as invalid data according to database table constraints, a message will be shown on the page, and a more detailed error message will be sent to Status Logger (see Figure 3.66).



Figure 3.66 - Add Contact – Page Error Once the errors are corrected, the data can be saved successfully to the database, and the new contact is now recognized by the system. When editing an existing contact (see Figure 3.67), the name fields will display as read-only, but all other fields will be editable. The user may edit the values in the editable fields.



Figure 3.67 - Edit Contact

Operations may be cancelled without altering the database by clicking on the Cancel button. Alternatively, the selections on the screen can be submitted to the database via selection of the Save and Exit button. When saving, required fields will be validated, and error messages will be displayed on the page when necessary. Users will be notified of errors encountered in accessing the database via informational messages sent to the Status Logger; messages will also appear on the page when needed. Critical errors will cause this page to remain in focus, forcing the user to manually cancel the operation. (See Section 3.3.2.13 for an example.) Non-critical errors as well as successful database access will result in browser redirection to the previous list page. If a new contact was created, the user will see the name of this new contact in the list on the list page (see Figure 3.68).



Figure 3.68 - Updated Contact List

3.3.2.14 Delete Confirmation All Delete operations route to this same page, filled in appropriately with the name of the current item to be deleted from the database (see Figure 3.69). If the user selects “No”, the delete operation is cancelled, and the page is redirected to the previous list page; if the user selects “Yes”, the selected item is deleted from the associated tables in the database, and then the page is redirected to the previous list page.



Figure 3.69 - Confirm Delete

3.4 Map Administration with Link Editor The Link Editor is a browser-based application that enables administration of the Operator Map’s Graphical User Interface (GUI). The following sections describe the operations that may be performed within the Link Editor.

3.4.1 Software Familiarization The Operator Map application is started by opening a web browser and navigating to the appropriate Operator Map URL. When the Map is initially opened in a browser, the login dialog shown in the middle of the map in Figure 3.70 will be displayed.



Figure 3.70 - Link Editor Login Dialog To complete the login process, the user should enter their username and password, and then click on the OK button. While running the Link Editor, informational and error messages are logged to the Status Logger. Further Link Editor processing is described in the following sections.

3.4.2 Processing Procedures The following sections detail the processing procedures for the Operator Map.

3.4.2.1 Networks After successfully logging in to the system, the user will need to select a network (the network provides a set of TSS detectors that can be used to instrument segments on the map) with which to work from the TSS Network dialog that automatically appears (see Figure 3.71).

Figure 3.71 - Select Network



This window displays a list of roadway networks currently defined in the system; the list will be empty if there are no defined networks. Entries in the list are defined as:

<provider name> - <center ID>.

Only links associated with the specified provider and center will be editable while a particular network is selected. From this window, users may add, edit, and delete networks; this functionality is described in the following sections.

3.4.2.1.1 Add Network To add a network to the system, click the Add button, and the dialog in Figure 3.72 will appear:

Figure 3.72 - Add Network The user should enter a provider name (the default is “tss”) and a center ID for the network, then click on Add Map Network button to complete the add process. Alternatively, the user may select Cancel to return to the map without adding a new network to the system.

The user may opt to work with a different network at any time by clicking on Select Network in the Control Panel, which is described in detail in Section 4.3.4.3.

3.4.2.1.2 Edit Network This option allows the user to edit the links of a network, and is described in detail in Section 4.3.4.4.

3.4.2.1.3 Delete Network To remove a network from the system, select that network in the list and press the Delete button. The user will need to confirm their intent to delete the network, or cancel the operation. If the delete is confirmed, the network will be removed from the system.

3.4.2.2 Control Panel

Users may navigate the map by clicking on an area of the map to re-center it, and using the zoom controls or district selector in the Control Panel (see Figure 3.73) to adjust the magnification of the map. These and other features of the Control Panel are addressed in the following sections.



Figure 3.73 - Link Editor Control Panel The following options are available to the user from the link editor control panel:

• District: Selecting a district in the Control Panel causes the map to be re-centered and magnified based on the location and data associated with the selected district.

• Zoom: The nine horizontal bars on the left side of the Control Panel display the current and available zoom level. Due to limitations of the Scalable Vector Graphics (SVG) Viewer, full magnification is not available in all areas of the map. If a particular magnification is not available in the current location, it will be colored a dark gray. Yellow bars indicate the current magnification level; one yellow bar indicates that the map is zoomed out to its furthest possible view, which should show nearly the entire state. Two yellow bars represent “Zoom Level 1”; three yellow bars represent “Zoom Level 2”, and so on, until “Maximum Zoom” is reached with all nine bars colored yellow.

• Select Network: This option allows the user to work with a different network of links on the map, and is described in detail in Section 3.4.2.3. Selecting this option will display the same window as shown above in Figure 3.71.

• Add Node: This option allows the user to add a new node to the current network of links, and is described in detail in Section 3.4.2.3.1.1.

• Save Map: This option allows the user to save the current network link data, once the link map files are created, the map files must be installed into the Map files directory that is specified in the SunGuideSM Version Description Document for them to become visible to users.

3.4.2.3 Links Links on the link editor map consist of a line segment with nodes at the endpoints. These nodes are displayed as white circles at the endpoints of a line segment. Links may contain midpoints which are represented as smaller green circles. The link itself is represented as a thin black line on top of a light blue arrow (or series of arrows) indicating the direction of travel for the link. Links and their nodes and midpoints can be seen in Figure 3.74.



Figure 3.74 - Links The yellow link in Figure 3.74 indicates that the link has been selected in the Available Links list (at the bottom left corner of the figure). When nodes are shared between links, as in the case where one link ends at a node and another link begins at the same node, the map will attempt to smoothly join the links together on the display so that the roadway appears continuous rather than disjointed.

3.4.2.3.1 Add Link To add a link to the map, the user must mark the endpoints with nodes. Nodes and link placement are described in the following sections.

3.4.2.3.1.1 Nodes Nodes are added to the map by pressing the Add Node button on the Control Panel, and then clicking anywhere on the map. A white circle will appear where the map is clicked. In Figure 3.75, two new nodes have been added along I-95, in the upper-right quadrant of the figure.



Figure 3.75 - Add Nodes Nodes on the map may be moved by holding the left mouse button down while pointing to a node, and dragging the node to a new location. Nodes may be deleted by pointing to the node, pressing the right mouse button, and selecting Delete Node from the menu. The user will need to confirm the deletion, at which point the node will be removed from the map. Removing nodes from the map also causes the links associated with those nodes to be deleted.

3.4.2.3.1.2 Place Links After placing beginning and ending nodes for a link on the map, select the link from the Available Links list and press the Place Link button (see Figure 3.76).



Figure 3.76 - Available Links Next, select the starting node for the link by clicking on it with the left mouse button; the node will change to light blue indicating that it has been selected. In Figure 3.77 below, the node on the northbound side of I-95 just north of the Turnpike interchange has been selected.

Figure 3.77 - Select Start Node



The ending node must now be selected by clicking on it with the left mouse button. Once the ending node is selected, the link will appear on the map between the selected nodes. In Figure 3.78, the northbound link has been placed, and we have started placing its corresponding southbound link using the process described above.

Figure 3.78 - Northbound Link Placed Figure 3.79 shows both of the new links in place on the map.



Figure 3.79 - Southbound Link Placed Be sure to assign the link’s endpoints in order, from start to end, so that the arrow behind the link will display correctly.

3.4.2.3.2 Modify Link

Individual endpoints for a link may be moved, even after a link has been placed on them, by clicking and dragging the node(s) with the left mouse button. The link will be redrawn on the map only after a node has been placed (and the left mouse button has been released) at its new position. To assign a link to a different start or end node, the user must repeat the place link process. A link may be removed either by selecting it from the Available Links list and selecting Remove Link, or by right-clicking the link on the map and selecting Delete Link from the context menu.

3.4.2.3.3 Midpoints While the smoothing algorithm can handle many simple bends in the roadway, it cannot compensate for dramatic curves. Midpoints are used to help fine-tune a link’s path on the map. To add a midpoint to a link, right-click on the link and select the Add Midpoint option from the context menu. A new midpoint will appear as a small green dot on the link, as in Figure 3.80.



Figure 3.80 - Add Midpoint The midpoint may now be positioned by moving the mouse over it, pressing the left mouse button down, and dragging the midpoint to its new position. The link will not be redrawn until the mouse button has been released at the new position (Figure 3.81).



Figure 3.81 - Reposition Midpoint 1 Figure 3.82 shows how links can be adjusted to follow the roadway more closely through the use of midpoints.



Figure 3.82 - Reposition Midpoint 2 A midpoint may be removed by right-clicking on it and selecting Delete Midpoint from the context menu. When a midpoint is removed, the line is redrawn by displaying a straight line from the two nearest points from the midpoint that was removed.

3.4.2.3.4 Link Order In general, links will be displayed on the map in the order in which they were created, so if any links cross over others, the newer links will lie above the older links by default. This order can be adjusted by right-clicking on a link and selecting either the Send to Back or Bring to Front context menu option. Send to Back causes the selected link to display behind the other links at that location, at least until another link at that location is sent to the back. Likewise, Bring to Front will cause the selected link to appear on top of the other links at that location.

3.4.2.3.5 Save Map Once the links are defined, the user must save the new map layout by pressing the Save Map button on the Control Panel; until this option is selected, none of the changes are permanent. Upon saving the new map to the server, the map subsystem will attempt to generate a new



Operator Map link display file. The status of this file will be reported in the Messages window of the screen.

3.4.2.4 Shields Highway shields serve to label the roadways on the map. Actions that may be taken with shields are described below.

3.4.2.4.1 Add Shield Highway shields may be placed at a particular location on the map, and will display only when the user zooms in to a specified level of magnification or closer. This ensures that at low magnification, the map is not completely covered by highway shields, and that at high magnification, enough shields are available to promote quick recognition of the highways.

To place a new highway shield on the map, select a Highway Type from the Edit Shields dialog. Available highway types are: Interstate (normal, business loop, and business spur), US Highway (normal, business, and alternate), Florida State Highway (normal and toll), and Florida’s Turnpike. For all shields except Florida’s Turnpike, a Highway Number, up to four numbers and letters, should then be entered. Finally, a zoom level must be selected for this shield. Note that, once added to the map, the shield will not be visible unless the user is currently zoomed to the selected magnification for this shield, or closer.

Once the entries and selections have been made, the user must press the Place Shield button, and then click the left mouse button on the map at the location where the new shield is to be placed.

3.4.2.4.2 Modify Shield Shields on the map may be moved by dragging them to a new location while holding down the left mouse button. Shields may be removed by right-clicking on the shield and selecting Delete Shield from the context menu. Shields may be temporarily hidden by pressing the Hide Shields button. This button will change to Show Fields, and may then be selected in order to make the shields visible again.

3.4.2.4.3 Save Shields Once shields have been placed as desired, the Save Shields button in the Edit Shields dialog may be pressed. It is important to note that the Save Map button used for saving highway links will not save shield modifications; likewise, the Save Shields button will not affect highway links.

3.5 Shape File Conversion The Shape File Conversion application is a Windows program that allows a user to convert Geographic Data Technologies (GDT) shape files to SVG files that can be displayed n the browser based map. The initial display is shown in Figure 3.83, the user selects the Load Roadway Data which will display a file search dialog that allows the user to select the folder where the GDT data is located.



Figure 3.83 - Shape File Conversion Tool: Initial Screen Once the file location is specified, the screen shown in Figure 3.84 is displayed to the user. On this screen the user can select what type of map data is to be displayed, the choices are: Interstate Map, Highway Map and/or Street Map. The user may select any combination of the map types. The user then selects which counties they wish to load in the list selection box labeled “Unloaded”.

Figure 3.84 - Shape File Conversion Tool: County Selector



After selecting counties (multiple counties may be selected) the user presses the Load button and the screen in Figure 3.85 is displayed. The user then needs to enter the Map Properties (the latitude and longitude offset) that were specified in the Implementation Plan for the SunGuideSM implementation. The Map Properties values are used to appropriate correct the map for the deformation that occurs as the shape file data is mapped to a flat display. The final action for the user is to select the Generate Roadway Links button that will create the SVG files that will be used to display maps on operator workstations.

Figure 3.85 - Shape File Conversion Tool: County Selected Once the SVG files are created, the need to be installed into the Map files directory that is specified in the SunGuideSM Version Description Document.



4. Map Operation The Operator Map is a browser-based application which serves as the primary interface for TMC operators to monitor and manipulate the equipment controlled by the various subsystems of the SunGuideSM software system. The text in bold is referencing a ‘button’ on the GU. The following sections describe the operations that may be performed via the Map.

4.1 Software Familiarization The Operator Map application is started by opening a web browser and navigating to the appropriate Operator Map URL. When the Map is initially opened in a browser, the login dialog shown in the middle of the map in Figure 4.1 will be displayed.

Figure 4.1 - Operator Map Login Dialog To complete the login process, the user should enter their username and password, and then click on the OK button. As the login process progresses, a status screen will be displayed. Figure 4.2 shows an example status screen that is displayed early in the login process. Once the login process is complete, the dialog will be automatically closed.



Figure 4.2 - Loading Status Screen While running the Operator Map, informational and error messages are logged to the Status Logger. Further Map processing is described in the following sections.

4.2 Processing Procedures The following sections detail the processing procedures for the operator map.

4.2.1 Control Panel and Context Menu Users may navigate the map by clicking on an area of the map to re-center it, and using the zoom controls or district selector in the Control Panel (see Figure 4.3) to adjust the magnification of the map. The following sections discuss the control panel features.

Figure 4.3 - Operator Map Control Panel

4.2.1.1 District Selecting a district in the Control Panel causes the map to be re-centered and magnified based on the location and data associated with the selected district.



4.2.1.2 Zoom The nine horizontal bars on the left side of the Control Panel display the current and available zoom level. Due to limitations of the SVG Viewer, full magnification is not available in all areas of the map. If a particular magnification is not available in the current location, it will be colored a dark gray. Yellow bars indicate the current magnification level; one yellow bar indicates that the map is zoomed out to its furthest possible view, which should show nearly the entire state. Two yellow bars represent “Zoom Level 1”; three yellow bars represent “Zoom Level 2”, and so on, until “Maximum Zoom” is reached with all nine bars colored yellow.

4.2.2 Map Controls When the map is present to the user, several options are available based on the placement of the mouse. These operations are:

• Left click on the map: the map will “re-center” to the position selected.

• Right click: the context menu will be displayed (see Figure 4.6), this menu will allow different options to be initiated, and these options are discussed in section 4.2.3.

• Left click, hold mouse and move: once the mouse is moved from its original position (with the left mouse button being held in a depressed position) a rubber-band box will be shown (see Figure 4.4), when the left mouse button is released the map will be zoomed to as near as possible to the rectangle created (note that the map only allows a zoom to a particular level, after this level is reached zoom requests will be ignored. Figure 4.4 shows an example rubber-band zoom box and Figure 4.5 shows the results after the zoom is completed (i.e. the left mouse button is released.

Figure 4.4 - Map With Rubber Band Zoom



Figure 4.5 - Map After Rubber Band Zoom Completes

4.2.3 Context Menu When the mouse pointer is over the graphical map, the user can bring up the SunGuide “context” menu with a click of the right mouse button. The menu is shown in Figure 4.6.

Figure 4.6 - Context Menu The following options are available to the user from the context menu:

• Incident Management Context Menu (see Figure 4.7): This option allows the user to manage incidents in the system; the software is described in detail in Section 4.2.9.

• Video Switching Context Menu (see Figure 4.8): This option allows the user to perform video switching from camera and video tours to select monitors for display and is described in detail in Section 4.2.7.

• Video Wall Context Menu (see Figure 4.9): This option allows the user to control the CCTV images (or tours) displayed on the video wall; the software is described in detail in Section 4.2.8.



• Preferences Context Menu (see Figure 4.10): This option allows the user to select color preferences for various portions of the map. The selection list shown in Figure 4.14 provides the operator with a list of options that can have their color changed. A list can be expanded by selecting the right facing triangle and can be collapsed by selected the down facing triangle.

Once an item is selected, the color is changed by altering the value in the “Choose a Color” selection screen that can be seen in Figure 4.15.

After the various color selections are made, the OK button is selected in the User Preference screen (shown in Figure 4.14). The color preferences are then stored to the database and the color changes are applied immediately to the map that is displayed. The next time the user logs into SunGuideSM the selected colors will be applied. The user can also select which background maps are displayed, Figure 4.16 depicts the background map selection dialog. The user can select multiple counties and/or multiple Districts (which map to counties) to be shown. The for each selection, the user selects Display Highways and/or Display Local Streets selection box. After pressing the OK button the map will be rendered and the settings saved to the database so that the same selections are established the next time the user logs in.

Note that selection the option to Display Local Streets will greatly slow down the map rendering as the street level data files are very large. This level of detail is rarely needed for a majority of the traffic management functions performed by SunGuideSM operators.

• DMS Context Menu (see Figure 4.11): This option allows the user to control DMS devices; the software is described in detail in Section 4.2.5.

• TSS Context Menu (see Figure 4.12): This option allows the user to view traffic conditions data; the software is described in detail in Section 4.2.4.

• CCTV Context Menu (see Figure 4.13): This option allows the user to control CCTV cameras; the software is described in detail in Section 4.2.6.

Figure 4.7 - Incident Management Context Menu

Figure 4.8 - Video Switching Context Menu



Figure 4.9 - Video Wall Context Menu

Figure 4.10 - Preferences Context Menu

Figure 4.11 - DMS Context Menu

Figure 4.12 - TSS Context Menu

Figure 4.13 - CCTV Context Menu



Figure 4.14 - User Preference Selector

Figure 4.15 - Color Preference Selector

Figure 4.16 - Background Map Selection

4.2.4 Links The user may hover (i.e., move the cursor to a location on the map and leave it in place for a period of time) over a link on the map to view the link’s test center, name, and associated lane information. This data will display in a popup window as shown in Figure 4.17 after a short time.



Figure 4.17 - Link and Lane Name The user may view the current traffic conditions for a specific link by double-clicking on that link, and viewing the TSS Details panel that is opened. The panel will display speed, occupancy, and volume information by lane, for a particular link. Examples of these detail panels may be viewed in Figure 4.18.

Figure 4.18 - Link Detail on Map TSS Data for a single link without speed, occupancy, or volume data is shown in Figure 4.19.



Figure 4.19 - Link Detail Selecting Set Op Status for a link brings up the dialog in Figure 4.20.

Figure 4.20 - TSS Detector Status This option allows the user to set the status for a selected TSS detector. Options include: Active, Out of Service, and Error/Failed. The user may select Set Op Status to save these settings, or may cancel this operation by closing this dialog (by clicking on the ‘X’ at the upper right).

4.2.5 Dynamic Message Signs Dynamic Message Signs may be controlled and checked from the map, via various panels. These processes and their associated panels are described in the following sections.

4.2.5.1 DMS Control Panel The DMS Control Panel, shown in Figure 4.21, displays the current message on the sign, and the sign’s current status. This panel is accessed by double-clicking on a DMS icon on the map.

Figure 4.21 - DMS Control



From here, the user may opt to display detailed status information, blank the sign, or send a new message to the sign. These options are described in the following sections.

4.2.5.1.1 Detailed Status This option displays the status of either a single DMS or a group of DMSs. To view a single sign’s status, the DMS tab should be selected in the status panel, and the DMS to be viewed should be selected in the DMS list, as shown in Figure 4.22.

Figure 4.22 - Detailed DMS Status To display the status information for a group of signs, the Group tab should be selected, and a DMS Group should be selected in the list. An example of the Group tab is shown in Figure 4.23.



Figure 4.23 - Detailed DMS Group Status If a message is currently showing on a sign or group of signs, this message will be shown on the What You See Is What You Get (WYSIWYG) display at the upper right side of this tab. If a single sign is being viewed, its status will display just below the message; for a group, the word “Group” will be shown at this location. Further status information is shown, regardless of the tab, such as brightness mode and level, control, temperature, power, and component (pixel, lamp, and fan) status. The other options remaining on the panel also display on both tabs, and are detailed below.

4.2.5.1.1.1 Detailed Pixel Status This option displays a graphical representation of the pixels for a sign, as shown in Figure 4.24.

Figure 4.24 - Detailed Pixel Status The display is used to display pixels in good working order (failed pixels will show up in red).

4.2.5.1.1.2 Detailed Lamp Status This option displays a graphical representation of the lamp status for a sign, as shown in Figure 4.25.



Figure 4.25 - Detailed Lamp Status The display is used to display lamps failed lamps.

4.2.5.1.1.3 Detailed Fan Status Displays a dialog stating the presence or lack of fan failures, as shown in Figure 4.26.

Figure 4.26 - Detailed Fan Status

4.2.5.1.1.4 Set Op Status This option allows the user to set the sign’s or group of sign’s operational status.

Figure 4.27 - Changing a DMS’s Operational Status A sign may be set in-service (active state) or out-of-service, and an error or failed state may be cleared. Note that a sign cannot manually be set to error or failed status. Clicking on the Set Status button saves the new status setting to the system; Cancel terminates this operation without making a change.

4.2.5.1.1.5 Change Brightness The dialog showing in Figure 4.28 allows the user to alter the brightness mode and level for the sign or group of signs.



Figure 4.28 - Set Brightness Brightness settings are: Auto, Day, and Night. Clicking on the Set Brightness button saves the new brightness setting to the system; Cancel terminates this operation without making a change.

4.2.5.1.1.6 Send Message This option displays a message editor window, shown in Figure 4.29.

Figure 4.29 - Send DMS Message From this display, the user may define messages, set their display durations, set their priority, and set pixel service status. Messages may be entered into WYSIWYG displays, which show you here, on screen, what the message will actually look like on the sign. An Amber Alert message is shown in Figure 4.29 as it will display on the actual sign.

Selecting the Close button causes this window to be closed without changing the sign’s message; selecting Send causes the message to be verified against the list of approved words, and the priority to be compared to the priority of a sign’s current message. If no conflicts arise, the message will be changed on this sign; alternatively, if conflicts do arise, the panel in Figure 4.30 will be displayed.



Figure 4.30 - Spelling Conflict Message wording, priority, and duration can be modified here; the message can be approved in either its original or edited form; or it can even be rejected.

4.2.5.1.1.7 Terminate Message Allows the user to clear the message currently displayed on the selected sign or group of signs.

4.2.5.1.1.8 Refresh Status Manually queries the sign for its current status, and refreshes the status information on the screen.

4.2.5.1.1.9 Send Command Other commands may be executed, such as Exercise Shutters and Reset Controller.

4.2.5.1.2 Blank Sign

This option blanks out the display on the selected sign.

4.2.5.1.3 Send Message This option provides the same functionality as that described in Section 4.2.5.1.1.6.

4.2.5.2 DMS Sequences Sequences allow the user to establish a series of messages to display on a sign, and to establish the time and duration during which these messages will be displayed. This panel may be accessed by right-clicking on the map and selecting Sequences [dms]. The dialog in Figure 4.31 displays when the option is first selected.



Figure 4.31 - Managed Stored DMS Sequence If no sequences are listed, the buttons will be disabled. The user must first select a library in the Sequence Library list, at which time the Sequences list will be populated. Once a sequence is selected in this second list, the appropriate buttons will be enabled. An example of the dialog is shown in Figure 4.32.

Figure 4.32 - Manage Sequence – Sequence Selected If the sequence is currently inactive, it may be activated from this window by clicking on the Activate button. The sequence may also be modified by clicking on the Edit Sequence button. When editing a sequence, the dialog shown in Figure 4.33 will be displayed.



Figure 4.33 - Edit DMS Sequence The Figure 4.33 shows an empty sequence. The user may click on the Add New Item button to add items to a sequence; doing so causes the dialog in Figure 4.34 is displayed.

Figure 4.34 - Create Sequence Item Once the user selects either a DMS or a group item to add, the Create New Item button will become enabled. The user may either continue with the add item operation, or may Cancel. If a new item was created, the item will be added to the pane to the left of the WYSIWYG display. Multiple items may be added by repeating the above process.

The user selects the days of the week that the sequence will run, as well as its time frame and duration. The message is entered on this screen as well as the timing for each page of the message and the amount of time between page displays. The message priority is also set on this screen. An example of this screen with selections and page messages is shown in Figure 4.35.



Figure 4.35 - New Sequence The user may click on the Save button to establish the sequence in the system, or may choose to Cancel this operation without saving the sequence.

4.2.6 Cameras Cameras may be controlled via the Camera Control panel, which can be accessed by double-clicking on a camera icon on the map or selecting camera control from the menu displayed when the right mouse button is selected. The Camera Control panel is shown in Figure 4.36.



Figure 4.36 - Camera Control The options on this panel are disabled until a camera is selected in the list. The list of cameras may be filtered via the filter dropdown list box; options include: All cameras, Status: Active, Status: Out of Service, Status: Error/Failed, Blackout: On, and Blackout: Off.

If the camera is not currently locked, the interface tries to acquire a lock by pressing the Lock button. The camera cannot be controlled until a lock is acquired. When the lock is acquired, the control buttons will become active.

When the Power Off button is selected the camera will be powered off, when the Power On button is selected the camera will be powered on.

The user may Pan, Tilt, and Zoom the camera by holding down the left mouse button on the desired controls. If a joystick is connected to the workstation, the joystick will also control the pan and tilt functions. The user can push the Focus and Iris buttons to change the focus and iris of the selected camera.

The user can either select established camera presets or new ones can be defined (if the user has the appropriate privileges to perform this action). The user can select the buttons labeled 1 through 8 and then select the View button to cause the preset command to be sent to the camera. Alternatively, the camera preset drop down list can be used to select a preset. If the user wishes to store the current camera position as a preset, the Store Current Position as Preset is preset. The current preset can be deleted by pressing the Delete button and the text associated by a preset can be altered by typing the text in the description box and pressing the Rename button.

The Set Op Status button allows the user to set the operational status for the selected camera. When this button is clicked, the dialog in Figure 4.37 is displayed.



Figure 4.37 - Set Operation Status Status options that may be selected are: Active and Out of Service.

Setting the blackout option ensures that the video feed originating from this camera will not display on a restricted monitor.

4.2.7 Video Switching Video Switching allows the user to define and modify video tours, and to designate which local monitors to use to view the output from selected cameras and video tours. This functionality is accessible by selecting the Video Switching menu item from the context menu. An example of the video switching panel is shown in Figure 4.38. Note that the number of monitors displayed in this GUI is configured by the SunGuideSM administrator (the number of monitors for each workstation is configured in the SunGuideSM Administrator editor).

Figure 4.38 - Video Switching - blank The output from cameras and video tours may be directed to specific monitors by dragging the camera and video tour icons from their respective lists (by holding down the left mouse button) and dropping them on the desired monitor image (by releasing the mouse button while pointing to the desired monitor). An icon representing either a camera or video tour, whichever is appropriate, will display on the selected monitor image. An example of the Video Switching panel with partial monitor assignments can be seen in Figure 4.39.



Figure 4.39 - Video Switching - filled Clicking on the Edit Tours button of the Video Switching dialog opens the Video Tour Editor as shown in Figure 4.40.

Figure 4.40 - Video Tour Editor – blank To modify an existing tour, select the tour in the list and modify the Name, Dwell Time and Description fields. Cameras may be added by selecting the Add button or removed from the tour by selecting the Remove button. The order in which the cameras are displayed in the tour may be rearranged by pressing the Move Up and Move Down buttons.

To create a new tour, enter the appropriate information on the panel then click on Save. If you have been viewing other pre-existing tours, clicking on the New Tour button will clear out the fields on the display so that data for the new tour may be entered. The Delete Tour button will remove a tour from the system. An example of a video tour is shown in Figure 4.41.



Figure 4.41 - Video Tour Editor – filled Selecting the Save button will save the modifications made in the editor, closes the editor, and returns the user to the previous Video Switching display. If a new tour was created, its name will be shown in the Video Tours list.

4.2.8 Video Wall Control Video Wall Control allows the user to designate which cameras and video tours should be displayed on the video wall (note that a video wall display is made up of a series of objects called “viewers”. This functionality is accessible by selecting the Video Wall Control menu item from the context menu. An example of the video wall GUI is shown in Figure 4.42. The layout of the viewers displayed relates to the current video wall layout that has been programmed on the video wall controller.

Figure 4.42 - Video Wall Switching

The output from cameras and video tours may be directed to specific viewers by dragging the camera and video tour icons from their respective lists (by holding down the left mouse button) and dropping them on the desired viewer image (by releasing the mouse button while pointing to the desired monitor). An icon representing either a camera or video tour, whichever is



appropriate, will display on the selected viewer image. The user also has two options available from this GUI:

• Refresh Geometry: instructs the SunGuideSM software to communicate with the video wall controller to retrieve the most current video wall settings that have been established (this button should be used when the video wall controller software has been used to modify the video wall layout).

• Layout Management: The video wall software allows the user to select which layouts (that are configured using the video wall control software and not the SunGuideSM software) are displayed. The SunGuideSM communicates with the video wall control software and presents a list of layouts to the user, an example of the layouts is presented in Figure 4.43.

Figure 4.43 - Manage Video Wall Layouts

The user can select a wall layout (only one layout may be active at a time) and then select on of the following options to change the layout of the wall:

• Activate: will instruct the video wall controller to switch to the specified layout • Deactivate: will instruct the video wall controller to disable the specified layout

4.2.9 Incident Management Incident Management describes a variety of functionality allowing the user to generate new events in the system, and to manipulate existing ones. Incident Management functionality is further described in the following sections.

4.2.9.1 Create New Event Users may create new events in the system by pointing to a location on the map, right-clicking, and selecting Add New Event from the context menu. This action will cause the dialog in Figure 4.44 to be displayed.



Figure 4.44 - Create New Event – blank Event types include: incident, planned road work, special event, action required, congestion, weather, safety message, disabled vehicle, and unspecified. Source options include: other – no additional info, other – with additional info, cctv, system alarm, state police, local police, citizen, and media. Figure 4.45 shows an example of the create new event dialog with data.

Figure 4.45 - Create New Event -- filled Clicking on Cancel terminates this action without creating a new event; clicking on Create completes this action, sends messages to the Incident Management subsystem, as shown in Figure 4.46, adds the new event to the list in Event Manager, as shown in Figure 4.47, and adds an event icon, as shown in Figure 4.48, to the map at the selected location.

Figure 4.46 - New Event Messages



Figure 4.47 - New Event in Event Manager List

Figure 4.48 - Event Icon

4.2.9.2 Event Manager The Event Manager always opens automatically during normal operation. Its purpose is to warn the user of existing events, enable the user to investigate and manipulate the data for these events, and to provide a means for accessing Response Plan and Resource data. Figure 4.49 shows an example of the Event Manager panel.

Figure 4.49 - Event Manager Note that this panel may be minimized, but not closed. The dropdown list box at the upper right of the window is used to filter the view on the events that display in the list. Options in this list are: All, Active, Closed/False Alarm, Unconfirmed, and Other Centers. Other options may



be exercised via the command buttons on the right side of the window. These options are described in the following sections.

4.2.9.2.1 Edit Event Data The user must make a selection in the event list before choosing this option. Once this button is clicked, the Incident Data Entry panel will be opened for the selected event, as shown in Section 4.2.9.3 Incident Data Entry, Figure 4.62. From here, the user will be allowed to edit the data for the selected event.

4.2.9.2.2 Edit Plans This option allows the user to edit existing pre-defined response plans. A selection in the event list is not required for this option. Once this button is clicked, the Pre-defined Plans list panel is shown, as seen in Figure 4.50.

Figure 4.50 - Pre-defined Plans Once a selection is made in this list and the Ok button is clicked, the Edit Plans panel will be opened, as shown in Figure 4.51. Selecting Cancel will remove the dialog from the screen.



Figure 4.51 - Edit Plans – pre-filled The Edit Plans panel will be pre-filled with options for the selected pre-defined plan. DMSs and HARs can be added to and removed from the equipment list, and routes can be added to and removed from the route list. DMSs and HARs can also be modified by selecting the Edit Item option on this panel. For further detail, see Section 4.2.9.3.4. Type selections, routes, and



direction selections for this plan will be used later by the system when determining which pre-defined plans to use during a Suggest New Plan operation. Changes to the plan may be saved, or this panel may be closed without saving changes.

4.2.9.2.3 Create Plan Selecting this option causes the Edit Plan panel to display without pre-selections having been made, as in Figure 4.52.

Figure 4.52 - Edit Plans – blank The panel options are the same as those described in Section 4.2.9.2.2. However, the plan item section is not available until the new plan data has been saved successfully.

4.2.9.2.4 Delete Plan

Selecting this option causes the dialog in Figure 4.53 to be displayed.



Figure 4.53 - Available Plans Selecting Ok on this panel causes the selected plan to be removed from the system; Cancel closes this panel and cancels the delete operation.

4.2.9.2.5 Find Nearest Camera The user must make a selection in the event list before choosing this option. Once this button is clicked, the CCTV Control Dialog will be opened for the camera nearest the selected event, as shown in Section 4.2.6 Cameras, Figure 4.36. From here, the user will be allowed to edit the data for the selected event.

4.2.9.2.6 Edit Resources Selecting this option causes the Search for Resources panel to be displayed, as shown in Figure 4.54 - Search for Resources



Figure 4.54 - Search for Resources On this panel, the user may specify criteria by which resources will be chosen to populate the Available Resources panel, as in Figure 4.55 - Available Resources

Figure 4.55 - Available Resources Once a selection is made in this list and the Ok button is clicked, the Resource Editor will be opened, as shown in Figure 4.56.



Figure 4.56 - Resource Editor with Contact The Resource Editor will be pre-filled with data for the selected resource. Contacts may be selected from a list, via the Select a Contact button. If this option is chosen, the dialog in Figure 4.57 will be displayed.

Figure 4.57 - Contact Selection



Selecting Ok will cause the selected contact’s data to be written to the Contact output area of the Resource Editor; Cancel will exit the contact selection panel without gathering data.

Selecting Change Route on the Resource Editor will cause the dialog in Figure 4.58 to be displayed.

Figure 4.58 - Route Selection Selecting Ok will cause the selected route’s data to be written to the Route output area of the Resource Editor; Cancel will exit the route selection panel without gathering data.

4.2.9.2.7 Create Resource Selecting this option causes the Resource Editor to display without pre-selections having been made, as in Figure 4.59.

Figure 4.59 - Edit Plans – blank The panel options are the same as those described in Section 4.2.9.2.6.



4.2.9.2.8 Delete Resource Selecting this option causes the Available Resources panel (see Figure 4.55) to be displayed. Selecting Ok on this panel causes the selected resource to be removed from the system; Cancel closes this panel and cancels the delete operation.

4.2.9.3 Incident Data Entry Incidents may be added to the system as well as modified once entered via the Incident Data Entry panel. New incidents may be entered by right-clicking at the appropriate location on the map and selecting Add New Event. As noted in Section 4.2.9.2.1, selecting an item in the event list of the Event Manager and clicking on the Edit Event Data button will open the panel for editing the selected item. The Incident Data Entry panel is further described in the following sections.

4.2.9.3.1 General By default, this tab would be the first one that the user sees when the Incident Data Entry panel is opened (see Figure 4.60). However, if the user has previously entered the Incident Data Entry panel during this session, the panel will reopen to the tab from which the panel was previously closed.

This tab displays general information about the current incident, and allows the user to modify the data shown here.



Figure 4.60 - General Tab – New Incident For new incidents, the False Alarm and Confirm buttons will be enabled, as in the figure above. If an incident is determined to be a false alarm, the user may close it by selecting the False Alarm button, and confirming the false alarm on the dialog shown in Figure 4.61.



Figure 4.61 - Confirm False Alarm If an incident is confirmed as an actual incident, the user may confirm it in the system by selecting the Confirm button; the date and time of the confirmation will display on the panel beside the Confirm button. For existing, confirmed incidents, the Clear Scene, Clear Delay, and Close buttons will be enabled, as shown in Figure 4.62.

Directions that can be set include: Northbound, Southbound, Eastbound, Westbound, Innerloop, and Outerloop. Source options that can be set include: other – no additional info, other – with additional info, cctv, system alarm, state police, local police, citizen, and media. Changes to the data on this panel may be saved by clicking on the Save Changes button.



Figure 4.62 - General Tab – Confirmed Incident For existing incidents, the Clear Scene, Clear Delay, and Close buttons will be enabled. The user would select the Clear Scene button to specify that the scene of the incident has been cleared, and traffic can resume as normal; however, there could be lingering delays in the traffic due to the congestion caused before the incident was cleared. Once traffic returns to normal flow, the user may indicate this state by clicking on the Clear Delay button. Finally, Close displays the dialog in (Figure 4.63).



Figure 4.63 - Confirm Close Event The user is asked to confirm their intent to close the current event. If the user clicks the Yes button, the other buttons on the panel will become disabled, and the incident is considered closed. Alternatively, the user may select the No button in order to leave the current event open.

4.2.9.3.2 Location The Location tab allows the user to enter or update location information for the current incident. Changes to the data on this panel may be saved by clicking on the Save Changes button. This tab is shown in Figure 4.64, and is described in the following sections.

Figure 4.64 - Location Tab



4.2.9.3.2.1 Route To select a route for this incident, the user selects the Change Route button, causing the dialog in Figure 4.65 to display.

Figure 4.65 - Select Route The user selects a route in the list, and clicks Ok to carry the data for the selected route forward to the Location tab; otherwise, the user may click Cancel to terminate the operation.

4.2.9.3.2.2 Landmarks Landmarks may be associated with the current incident via the Landmark Name and Proximity fields. Options for the Landmark Proximity dropdown list are: at, past, and prior to.

4.2.9.3.2.3 Lanes Affected lanes may be associated with this incident graphically. To alter the lane configuration displayed on this tab, click on the Edit Lane Configuration button. The dialog in Figure 4.66 will be displayed.

Figure 4.66 - Lane Configuration



From here, the user may opt to use an existing lane configuration, or may enter a new one. To select an existing configuration, the user selects the desired configuration from the dropdown list at the upper right, and clicks on the Select Existing Configuration button.

To create a new configuration, the user enters a name and description for this configuration, and then adds and removes lanes and corresponding information for those lanes appropriately. The current lane will be highlighted in blue on the image. Options for the Type dropdown list are: on ramp, off ramp, travel lane, shoulder, and collector-distributor. Directions include: Northbound, Southbound, Eastbound, Westbound, Innerloop, and Outerloop. Directions will be notated with a single letter on the lane graphic.

The user may save the new lane configuration to the system by clicking on Save; otherwise, the user may select Cancel to terminate the operation without saving any changes. Note that saving a lane configuration here does not associate this configuration with the incident; this will happen if/when the user clicks the Save button on the Location tab. Once the lane configuration is established and the user has returned to the Location tab, the lanes may be altered graphically by left-clicking on a lane until the desired icon displays. The following icons may be used,

representing an unknown status ( ), open lane ( ), and blocked lane ( ). The lane will cycle to the next state (unknown, then open, then blocked) each time the lane is clicked.

4.2.9.3.2.4 Weather Weather conditions may be the cause of, or a contributing factor to, the incident, in which case the user may want to track related weather conditions. Weather conditions may be added to the list at the bottom of the page by selecting the Add button; the dialog in Figure 4.67 will be displayed.

Figure 4.67 - Weather Conditions Condition Type options include: hurricane, tornado, snow, severe wind, rain, reduced visibility, ozone, high water, flood, and other. Weather condition entries may be carried forward to the list at the bottom of the Location tab by selecting Ok; otherwise, they may be dismissed by selecting Cancel.

4.2.9.3.3 Type Specification

The type of incident may be specified on this tab, shown in Figure 4.68.



Figure 4.68 - Type Specification Tab General incident types include: incident, planned road work, special event, action required, congestion, weather, safety message, disabled vehicle, and unspecified. Specific incident types include: other – no additional info, other – additional info, vehicle fire, debris in roadway, personal injury, property damage, fatality, disabled in roadway, roadwork, police activity, and off-road activity. Pavement condition options are: wet, dry, chemical wet, and ice-snow.

Users may notate the type and count of vehicles involved by clicking on the Add Vehicle button, this will cause the following dialog shown in Figure 4.69 to be displayed.



Figure 4.69 - Vehicles Involved Options for vehicle classification include: car, truck-van-SUV, single unit truck, tractor trailer, motorcycle, loaded commercial bus, unloaded commercial bus, loaded school bus, and unloaded school bus. Involvement options include: involved, overturned, lost load, and jack-knifed. Selecting Ok causes this data to be carried forward to the list at the bottom of the Type Specifications tab; Cancel terminates the operation without saving data. The revised tab showing newly entered data can be seen in Figure 4.70.

Figure 4.70 - Type Specification Tab with Modifications The user must click on the Save Changes button to save the entries on this tab.



4.2.9.3.4 Response Plan This tab allows users to create and execute a response plan for the current incident. Options available on this tab are discussed in the following sections. Figure 4.71 shows the tab before a plan has been associated with this incident.

Figure 4.71 - Response Plans Tab

4.2.9.3.4.1 Suggest New Plan This option generates a suggested response plan, and returns a count of the number of items in the generated plan. The count returned will display beside the View Plan Suggestions button.

4.2.9.3.4.2 View Plan Suggestions Clicking on this button displays a selection list with the suggested plans for this event. Clicking on the OK button will select a suggested plan and add replace the existing plan items with those in the suggestion. Clicking Cancel will close the suggestions list.



4.2.9.3.4.3 Execute Plan Once a plan has been setup as desired, it may be executed by clicking on the Execute Plan button.

4.2.9.3.4.4 Revoke Plan A plan that has been executed may be revoked, or terminated, by clicking on the Revoke Plan button. This cancels the currently active plan for the event, regardless of what items are displayed on the Response Plan tab.

4.2.9.3.4.5 Delete Item Items that have been added to the list may be removed by clicking on the Delete Item button.

4.2.9.3.4.6 Add Highway Advisory Radio (HAR) Item This is a Release 2 feature.

4.2.9.3.4.7 Add DMS Item Clicking on this button allows the user to add a new DMS item to the list by displaying a list of existing DMS equipment, as shown in Figure 4.72.

Figure 4.72 - DMS Equipment List Selecting Cancel terminates this operation without selecting an item; selecting Ok causes the Edit New DMS Item panel, as shown in Figure 4.73, to be displayed.



Figure 4.73 - Edit DMS Messages may be entered here that will display on the DMS once the response plan is executed. Multiple pages may be defined, and display and times may be set for each page. Message duration and priority may be set, pixel service may be turned on/off, and beacons may be enabled/disabled from this panel.

Clicking Save Changes causes the new DMS item to be carried forward and inserted into the item list on the Response Plan tab; clicking Cancel terminates this operation without editing the new DMS’s data.

4.2.9.3.4.8 Edit Item This option allows the user to edit DMS or HAR items in the list and edit its data via either the DMS or HAR editor. The DMS Editor was shown previously in Figure 4.73. The HAR editor is a Release 2 activity.

4.2.9.3.4.9 Add Plan Allows the user to select a plan from a list of pre-defined plans, shown in Figure 4.74, and add that plan to the current response plan. This will append items in the predefined plan to the list. In the case that an item in the plan to be added uses the same DMS or HAR as an existing item, the existing item will be replaced.



Figure 4.74 - Pre-defined Plans List Clicking Ok causes the selected plan to be carried forward and its items to be inserted into the item list on the Response Plan tab; clicking Cancel terminates this operation without selecting the pre-defined plan. An example of a completed plan is shown in Figure 4.75.



Figure 4.75 - Response Plans Tab

4.2.9.3.5 Associations This tab allows the user to associate additional routes (see Figure 4.76) which may be affected by this event, and to associate other events which are related to this event (i.e. congestion caused by an accident, road closures for a special event, etc.)



Figure 4.76 - Associations Tab Association options are described in the following sections.

4.2.9.3.5.1 Add Route Clicking on Add Route causes the Select a Route panel (Figure 4.65) to display. Once the user selects a route and selects Ok, the selected route is immediately associated with this incident; i.e., the user will be returned to the previous screen (Figure 4.76) and will not need to save this association. The newly associated route will be added to the Associated Routes list in the upper portion of the screen. The user may also opt to cancel the route selection operation.

4.2.9.3.5.2 Remove Route This option removes the selected route from the Associated Routes list.



4.2.9.3.5.3 Add Event Clicking on Add Event causes the Select an Event panel (Figure 4.77) to display.

Figure 4.77 - Event Selection Once the user selects an event and selects Ok, the selected event is immediately associated with this incident; i.e., the user will be returned to the previous screen (Figure 4.76) and will not need to save this association. The user may also opt to Cancel the event selection operation.

4.2.9.3.5.4 Remove Event This option removes the selected event from the Associated Events list.

4.2.9.3.6 Resources This tab provides a means for the user to associate contacts and participants with the current incident. Initially, the lists on this tab are blank, as shown in Figure 4.78. Options on this tab are described in the sections below.



Figure 4.78 - Resources Tab

4.2.9.3.6.1 Add Contact This option displays the Contact Selection list panel as shown previously in Figure 4.57. Selecting Cancel from that panel terminates the operation, returning the user to the Resources tab; selecting Ok displays the notification dialog in Figure 4.79.

Figure 4.79 - Contact Notification Option The user may choose to notify the current contact immediately (by selecting Yes), or defer this action until the contact list is complete (by selecting No). Either choice will close this dialog and add this contact to the list of contacts on the Resources tab.

4.2.9.3.6.2 Remove Contact This option removes the selected contact from the list of contacts on this tab.



4.2.9.3.6.3 Notify Contacts This option immediately notifies the contacts in the contact list of the current incident.

4.2.9.3.6.4 Add Participant This option allows the user to associate participants such as police cars, fire trucks, and ambulances with the current incident. These selections will be used to populate a list of available resources, as shown in Figure 4.55.

4.2.9.3.6.5 Remove Participant This option removes the selected participant from the list of participants on this tab.

4.2.9.3.6.6 Set Participant Status This option sets the participation status for a resource attached to the event. The dialog is shown in Figure 4.80. The resource can be notified, can have arrived on scene, and can have departed the scene. The user must check the appropriate boxes and press Ok to save the changes, or Cancel to terminate the operation.

Figure 4.80 - Set Participant Status

4.2.9.3.7 History This tab displays the messages in the system associated with this incident (see Figure 4.81). Messages are generated by the IM Subsystem as well as manually by the user.



Figure 4.81 - History Tab The history list displays the items currently known to the system. Clicking the Refresh History button forces the system to refresh the history list. New entries may be added manually by the user by filling in the data fields at the bottom of the tab and clicking on the Add New Entry button.



5. Notes None.