SunGuide SM : Software Test Procedures SunGuide-STP-1.1.0

Transcription

1 SunGuide SM : Software Test Procedures SunGuide-STP Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee Street, M.S. 90 Tallahassee, Florida (850) June 6, 2005

2 Doument Control Panel File Name: File Location: SunGuide-STP doc SunGuide CM Repository CDRL: Name Initial Date Created By: Robert Heller, SwRI RWH 05/31/05 Steve Dellenback, SwRI SWD 05/31/05 Stephen E. Novosad SEN 06/06/05 Reviewed By: Steve Dellenback, SwRI SWD 06/06/05 Modified By: Completed By: SunGuide-STP i

3 Table of Contents Page List of Acronyms... iv Revision History... vi 1.0 Scope Document Identification Project Overview Related Documents Contacts Test Preparations SunGuide SM System Installation SunGuide SM System Configuration Test Procedures Core Processes User Administration (AS-1) Display Software Version / System Health (SL-5) Starting and Stopping SunGuide SM Services (EH-1) SunGuide SM Auto Restart (EH-3) Dynamic Message Sign Map Access to DMS (DMS-1) Send DMS Message (DMS-2) Support Message Libraries (DMS-4) High Level DMS Status Support (DMS-5) DMS Sequences. (DMS-8) Message Priority Queue 1.1 (DMS-10) Alphabetized Message Library Management (DMS-11) Multi Page Message Timing (DMS-13) Video Map Access to Cameras (CCTV-1) IP Video Switching (CCTV-2) CCTV GUI High Level Status (CCTV-3) Video Tours and Error Logging (CCTV-4) CCTV Auto Lock Request (CCTV-8) American Dynamics 300 MCP Support (CCTV-9) Device Failure & Device Status Reporting (CCTV-10) Transportation Sensor Subsystem (TSS) TSS Data Updates (TSS-2) TSS Generated Alarms (TSS-4) Incident Management SunGuide-STP ii

4 3.5.1 Event Creation (IM-1) Event Management (IM-2) Response Plan Implementation (IM-5) Response Plan Generation (IM-7) Decreasing IM Message Priority with Distance (IM-10) Incident Closure and Response Plan Cancellation (IM-11) Notes SunGuide-STP iii

5 List of Acronyms API...Application Program Interface AS...Administrative Subsystem ASCII...American Standard Code for Information Interchange C2C...Center to Center CCTV...Closed Circuit Television DMS...Dynamic Message Sign DOM...Document Object Model DOT...Department of Transportation EH...Executive Handler FDOT...Florida Department of Transportation GUI...Graphical User Interface HAR...Highway Advisory Radio HKLM...HKey Local Machine ICD...Interface Control Document IE...Internet Explorer IIS...Internet Information Service IM...Incident Management IP...Internet Protocol ITN...Invitiation to Negotiate ITS...Intelligent FTransportation Systems LAN...Local Area Network MAS...Message Arbitration Subsystem NTCIP...National Transportation Communications for ITS Protocol PMTC...Portable Transportation Management Center RDBMS...Relational Database Management System RTMC...Regional Transportation Management Center RWIS...Roadway Weather Information System SICP...Software Integration Case Procedures SL...Status Logger SRS...Software Requirements Specification SunGuide-STP iv

6 STMC...Satellite Transportation Management Center STMCSLS...Statewide Transportation Management Center Software Library System TCP/IP...Transport Control Protocol / Internet Protocol TSS...Traffic Sensor Subsystem VS...Video Switching VTMC...Virtual Transportation Management Center W3...World Wide Web Wide Web XML...Extensible Markup Language SunGuide-STP v

7 Revision History Revision Date Changes Draft May 31, 2005 Initial Release June 6, 2005 Updated for Disrtrict 4 deployment SunGuide-STP vi

8 1.0 Scope 1.1 Document Identification This document is the Software Test Procedure (STP) for the SunGuide SM software. The purpose of this document is to provide a set of tests that can be executed to verify the installation of the SunGuide SM software. 1.2 Project Overview The Florida Department of Transportation (FDOT) is conducting a program that is developing SunGuide SM software. The SunGuide SM 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 SunGuide SM software is to have a common software base that can be deployed throughout the state of Florida. The SunGuide SM 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 High-Level Architectural Concept SunGuide-STP

9 The SunGuide SM development effort spans approximately two years. After the development, the software will be deployed to a number of Districts and Expressway Authorities, counties throughout Florida, and enhancement 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/ RR, SwRI Proposal No , dated: November 18, SwRI Technical Proposal: Technical Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN-DOT-02/ RR, SwRI Proposal No , dated: January 31, SwRI Cost Proposal: Cost Proposal for Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Negotiation Number: ITN- DOT-02/ RR, SwRI Proposal No , dated: January 31, SwRI BAFO letter: Southwest Research Institute Proposal No , Invitation to Negotiate (ITN): Statewide Transportation Management Center Software Library System, Reference: Negotiation Number: ITN-DOT-02/ RR, dated: May 5, FDOT procurement document: Invitation To Negotiate (ITN), Negotiation Number: ITN- DOT-02/ RR, Statewide Transportation Management Center Software Library System, dated: October 21, FDOT Scope of Services: Statewide Transportation Management Center Software Library System: Scope of Services, September 22, FDOT Requirements Document: Statewide Transportation Management Center Software Library System: Requirements Specification, June 3, Southwest Research Institute, TMC Software Study, November 15, Southwest Research Institute, Introduction to an Operational Concept For the Florida Statewide Library, FDOT OCD 1.0, March 31, Southwest Research Institute, Statewide Transportation Management Center Software Library System: Software Requirements Specification, STMCSLS-SRS-1.0.2, April 2, Southwest Research Institute, SunGuide SM Software Integration Case Procedures, SunGuide-SICP-1.1.4, May 27, Southwest Research Institute, SunGuide SM Version Description Document, SunGuide VDD-1.104, May 20, Southwest Research Institute, SunGuide SM Software User Manual, SunGuide-SUM-1.1.0, May 26, SunGuide-STP

10 World Wide Web Consortium (W3) website: SunGuide SM Project website: Contacts The following are contact persons for the SunGuide SM software project: Elizabeth Birriel, ITS Central Office, Liang Hsia, FDOT Project Manager, John Bonds, Senior ITS Specialist, David Chang, ITS Specialist, Steve Dellenback, SwRI Project Manager, Robert Heller, SwRI Software Project Manager, The following are contacts that will be used by the SunGuide SM software project team to assure consistency with other FDOT projects and FDOT procedures: Jim Mosser, PB Farradyne, FDOT C2C Project, David Lambert, University of North Florida, RWIS, Bob Colins, PBS&J, Emergency Evacuation, John Fain, FDOT, Comptroller, Leslie Jacobson, PB Farradyne, Ramp Metering, SunGuide-STP

11 2.0 Test Preparations Prior to execution of the test procedures in Section 3, the SunGuide SM software needs to be installed and configured. 2.1 SunGuide SM System Installation The test cases are intended to be run against an installed and running SunGuide SM software system. Instructions for installation of the SunGuide SM software are contained in the SunGuide SM Version Description Document and are not repeated here. An Implementation Plan is also provided with each deployment and the steps in the Implementation Plan need to be followed prior to the testing in this document being performed. 2.2 SunGuide SM System Configuration The test cases are intended to be run against a configured SunGuide SM software system. System configuration follows the installation of the software is the second step of software deployment. Configuration of the software includes but is not necessarily limited to: Generation of local map features from shape files Configuration of local users Configuration of field devices 1 o DMS (Dyanmic Message Sign) o CCTV cameras (Closed Curciit Television Camera) o Traffic detectors Configuration of TMC devices o Barco wall o IP video decoders and monitors o Other video sources Configuration of highway topology Configuration of DMS sequencing tree 1 These activities exercise the Administrative editor, and for that reason, few tests are included within the test cases for the configuration of devices using the administrative editor. SunGuide-STP

12 3.0 Test Procedures The test procedures contained in this section are excerpts from the Software Integration Case Procedures (SICP) that were developed to provide extensive testing of the software requirements. The tests in the following sections perform high level testing that is used to assure the software is installed and configured properly, for detailed requirements testing the SICP should be utilized. The procedures have a number of sections that will state SELECTED CAMERA or SELECTED SIGN ; the intent of these procedures is that the test executors will identify the name (based on what was configured during the installation) of a device that should be used for the test. 3.1 Core Processes The core processes tested include system health monitoring, status logging, and user management. The functionality tested is divided into three groups which reflect which SunGuide SM subsystem provides the required functionality. These are: AS Administrative Subsystem provides a collection of editors to create or modify the configuration of the SunGuide SM software. This configuration information is stored in an Oracle database and consists of user, user privileges, devices, roadways, etc. SL Status Logger Service provides a logging service for the SunGuide SM software. Messages can be generated by the SunGuide SM services and written to the SunGuide SM log. The Status Log Viewer application provides a user interface to the status log. The Status Log Viewer would normally be used by system administrators to analyze problems that might arise during the operation of the SunGuide SM software. EH Executive Handler Service provides a method of starting, monitoring and stopping the other services within the SunGuide SM software. The Executive Handler is started by the windows operating system at boot-time, and then inspects a configuration file to determine if other SunGuide SM servers need to be started. The SunGuide SM software services are written to provide a heartbeat to the Executive Handler. The Executive Handler Viewer displays the heartbeat information, as well as providing a method for manually starting, stopping and restarting monitored processes. SunGuide-STP

13 3.1.1 User Administration (AS-1) The Administrative Subsystem is utilized to create a user and assign a default set of privileges to the user based on group membership. It is then used to modify the privileges of the created user and to modify the privileges of a default group. If a user does not have privileges associated with a type of field device (DMS), then icons representing those field devices do not appear on the Operator Map when that user logs into the system. This allows a method to verify that a user has or lacks those privileges. One of the test steps relies on that. For example, a user is created without DMS privileges, and then that user logs into the operator map. There will be no DMS icons displayed. The user logs off. DMS privileges are added to the user and the user logs into the system. This time, the DMS icons will be displayed. No special test preparation is necessary. Test Steps Test Result P F Workstation A. Start the administrative editor on workstation A. Log into the administrative editor using Windows credentials for a user that is a member of the SunGuideAdmin 2 group. Expand the User Management subtree. Open groups, the groups Administrator, Manager, Operator, Local Guest, and Remote Guest should all appear. Did the administrative editor require you to log in? Did the group editor display the groups: administrator, manager, operator, local guest and remote guest? Workstation A. Open Users, Select Add, Complete the form, and select a group. The group should disallow use of the cameras. Save and Exit. Workstation B. Open the operator GUI login as the newly created user. Verify no DMS icons appear on the map. Logout. Workstation A. Start the administrative editor. Expand the User management subtree. Open Users. Select the user that was just added and edit the user. Verify the privileges of the user are the same as those of the group. Did the privileges of the added user match those of the group selected for membership? 2 This group is configurable by setting the permissions on the directory that contains the SunGuide SM Admin tool. This is the recommended group, but the actual group may differ from installation to installation. SunGuide-STP

14 3.1.2 Display Software Version / System Health (SL-5) In order for personnel responsible for SunGuide SM system operation knowing what SunGuide SM software is running, the SunGuide SM services send a message to the Status Logger when they start that includes version number (this is analogous to the help about box in a windows application GUI). At each major release, the services will be changed to reflect the release number (1 for Release 1, 2 for Release 2, etc.), but software maintenance and configuration management practices will assign new number to services that are modified to correct latent defects or in response to minor enhancements. A log file exists from the previous testing (specifically SL-3) and contains a system restart within it. Open the Status Log Viewer and position the viewer to the most recent (or otherwise) system restart. Verify that each subsystem and driver running logged its software version (for SunGuide SM Release 1, these are all version 1 applications) upon startup. Verify the status log contains a record of subsystem and driver starts and stops as well as messages regarding the health of each process. Open the Executive Handler Viewer, note that the health of each SunGuide SM monitored process is contained in the Executive Handler Viewer window. Do the started processes log their version numbers upon startup? Does the status log contain a history of health of the processes? Does the Executive Handler Viewer display current system health? SunGuide-STP

15 3.1.3 Starting and Stopping SunGuide SM Services (EH-1) Executive Handler Viewer provides a user interface into the Executive Handler. The view can be organized by host or by subsystem (processes not assigned to a subsystem will not be displayed in the subsystem view). The Executive Handler Viewer also provides commands to start and stop processes and adjust the logging level. Using the task manager on the SunGuide SM Application Server, check that Data Bus, DMS Polling and CCTV processes are running, if not then use the Executive Handler Viewer to start them. Verify that the DMS Polling and CCTV processes are not set to automatically restart. Start the Executive Handler Viewer. Modify the configuration of the viewer to display the processes hierarchically by subsystem then back to host. Right click on Data Bus, and select the Set Log Level menu item. Adjust the logging level to debug. Use the Status Log Viewer to confirm that the process is logging messages at the DEBUG log level. Set the Data Bus log mode back to INFO level. Using the Executive Handler Viewer, stop DMS Polling and CCTV Subsystem processes on the SunGuide SM Application Server. Observe the status of both applications in the Executive Handler Viewer. On the SunGuide SM Application Server, display the process status by using Task Manager. Note the processes have been stopped. (May have to utilize Task Manager on multiple systems depending on how the software is actually installed.) Restart DMS Polling and CCTV subsystem using the Executive Handler Viewer. Stop the DMS Polling and CCTV processes by using the task manager on the SunGuide SM Application Server. Notice the status changes on the Executive Handler Viewer. Note that once the DMS Polling and CCTV processes failed outside of Executive Handler control, Executive Handler did not attempt to restart them. Use the Status Logger Viewer and note that messages regarding the stopped processed have been logged. Was the Executive Handler Viewer able to display the processes in a hierarchy by subsystem? Did the logging level change to DEBUG? Did both processes stop as expected? Did DMS Polling and CCTV restart? Did the Executive Handler system indicate the lack of heartbeat when the processes were terminated? Executive Handler did not attempt restart. Did a message regarding the stopped processes appear in the status log? SunGuide-STP

16 Start the Executive Handler Editor. Use the editor to set some of the SunGuide SM Application Services to not automatically start on reboot [dmspolling, statewide driver, dms xml interface]. Restart Windows. Using Executive Handler, note that those processes were not restarted. Use the editor to set those processes to automatically start on reboot. Restart Windows. Note that those processes were started. On Windows restart make sure that those applications removed from the SunGuide SM startup were not started. On the second Windows restart make sure that they were restarted. SunGuide-STP

17 3.1.4 SunGuide SM Auto Restart (EH-3) The Executive Handler Service is started by Windows whenever Windows restarts. In turn, the Executive Handler Service reads the executive Handler startup file and starts the other SunGuide SM services and applications. Each of the services managed by Executive Handler may be set for auto restart in the event that Executive Handler detects they have terminated. The services and applications controlled by Executive Handler may be modified by the Executive Handler Editor. This activity may be monitored by the Executive Handler Viewer. Open the Executive Handler Editor and change DMS Polling and Statewide Driver to not automatically restart. Verify that the CCTV Subsystem is marked to restart automatically. Verify all three processes are currently running. Verify that at least one user is configured to receive notification on process termination. Verify the automatic and manual initiation, termination and reinitiation of the system processes by: Restart the SunGuide SM application server and allow the SunGuide SM software to restart automatically. Stop the CCTV Subsystem (marked to restart) using the Windows Task Manager. Note that it restarts. Stop DMS Polling and Statewide Driver using the Task Manager. Note they did not automatically restart. Then restart them using the Executive Handler Viewer. Start the SunGuide SM Executive Handler Editor application on the SunGuide SM Application Server and note the order that processes are listed. Mark all processes to restart automatically. Stop CCTV and DMS subsystems using the task manager. Note the order in which they restart. Use the Admin Editor system to identify the users which are listed for notification on a process error. Did the SunGuide SM system restart automatically? Did the selected processes stop? Did the processes marked for auto restart, automatically restart? Did the manually restarted processes restart? Does the Executive Handler Editor allow specifying the order of the processes to be restarted? Did the processes restart in the order specified by the executive handler viewer? Was an sent to the notify person for the stopped process? SunGuide-STP

18 3.2 Dynamic Message Sign The SunGuide SM DMS subsystem implements the capabilities to control Dynamic Message Signs. The DMS subsystem receives DMS requests in the form of XML messages and processes them through to the signs Map Access to DMS (DMS-1) The Operator Map displays icons representing DMSs within the system. The icons are color coded to represent the current status. Mousing over an icon displays the DMS name as well as its status. Clicking on a sign icon will display the sign status GUI. From the sign status GUI, the extended status GUI can be displayed from which the user is presented with a list of DMS commands that can be issued from the GUI. The SunGuide SM operator GUI is running and user is logged into the system. The map is zoomed to an appropriate location known to represent an area where DMS are located and entered into the SunGuide SM database. \Test Steps Expected Result P F Observe the DMS icons on the map. Move the mouse pointer over the top of a DMS icon on the map. A status window will appear giving the ID of the DMS as well as its status. Click on a DMS, the DMS short status GUI will be displayed. Open the detailed status dialog. Confirm that a selection of commands may be sent to the DMS; notice that an option on the status GUI includes sending a message. Do icons representing DMSs appear on the map display? Did a message box appear indicating the DMS name and overall status of the DMS appear when the mouse pointer was positioned over the DMS? When a DMS icon was clicked, did the DMS status GUI appear on the display? Does the GUI have a method of sending commands to the DMS? SunGuide-STP

19 3.2.2 Send DMS Message (DMS-2) DMS-2 exercises a number of different capabilities, but most notably the ability to display messages. The DMS GUI is also used to set control modes of the signs (Active vs. Out of Service), exercise shutters, control brightness, reset controllers, check messages for approved words, etc. The DMS Send / Compose message GUI allows a user to compose a message in a What You See Is What You Get (WYSIWYG) format by typing directly into a representation of a sign. The user does not have direct access to MULTI, but the GUI composes a MULTI text string and sends that to the DMS subsystem for processing and conveyance to the sign. The user has logged into the SunGuide SM system, initiated the SunGuide SM GUI, and has the privileges to modify one or more DMSs. The approved word list has been pre-loaded from installation without the words : Happy, Birthday, Steve The phrase A SELECTED SIGN means to select a sign and use it throughout a single test. Test Steps Expected Result P F Workstation A. Locate A SELECTED SIGN on the Operator Map. Position the mouse over the icon. The status is displayed. Left click on the sign; click detailed status. Set operational status to Out of Service. Roll the mouse back over the sign, and notice that its status is out of service Using the Detailed Status GUI set the status back to Active. Click on the icon to display the DMS status GUI, click on the Send message button to display the DMS send / compose message GUI. Use the GUI to compose the message FDOT Testing\nDMS-2. Set the time duration for the message to 2 minutes, set the priority to 1, and send the message. Note the time. Click on Echo Message to retrieve the message being displayed on the DMS. The message FDOT Testing\nDMS-2 should be echoed. Open the Status Logger search for the message previously sent. Note within the message that the message is formatted as a MULTI text message. Wait until the message FDOT Testing\nDMS-2 no longer is displayed. Note the time. Two minutes should have elapsed since the message was posted. Did the sign status change from Active to Out of Service and back to Active? Did the multi-text message properly display on the selected sign? Did the message appear in the DMS status GUI? Did the message appear in the status log as a MULTI string sent to the DMS? Has it been 2 minutes since the message was posted? SunGuide-STP

20 Terminate the message being displayed on A SELECTED SIGN. Compose a message Happy Birthday Steve for display on the sign. Send it. An unapproved words conflict dialog should appear indicating that the message contains words that are not in the approved words list. Choose to go ahead and accept the original message. Did the unapproved words in message dialog box appear? Did the message get posted after the user overrode the error? Observe that the message with the unapproved words is displayed on the DMS. Use the GUI to terminate the message by blanking the sign. Start the Status Log Viewer. Check the status log and verify the communications with the DMS signs have been logged. The log messages should include user name, DMS, message, and the status of the event. Did the DMS cease displaying the message? Did the status log contain the messages posted to the signs with user name, DMS, message, and the status of the event? SunGuide-STP

21 3.2.3 Support Message Libraries (DMS-4) The SunGuide SM DMS subsystem supports creation and deletion of message libraries, as well as the ability to add and delete individual messages from libraries. The requirements in this test require the ability to send ALL messages in a SunGuide SM maintained message library. Due to the number of messages that might be stored in the library, it is impractical to exhaustively test this requirement. The test will create a message library, add five messages to it, delete a message then send each of the messages to one of each of four different signs. The user has logged into the SunGuide SM system, initiated the SunGuide SM GUI, and has privileges to use the DMS. Right click on the map, select DMS/Message Libraries from the menu. Create the message library ATP DMS-4. Add the following messages to the message library: DMS-4 Test 1 DMS-4 Test 2 FDOT ITS Restart the GUI. Display the contents of the ATP DMS-4 message library. Delete the DMS-4 Test 2 message. Did the GUI create the message library? Did the GUI save each of the messages in the message library? Did the GUI delete the DMS- 4 Test 4 message? Restart the GUI. Display the contents of the ATP-DMS-4 message library. Using the ATP-DMS-4 message library in the Send Message Dialog, send each message (if sign supports the length of the message) to the four different signs. Make sure to terminate existing message in between sending new message. Observe that the messages are displayed on the signs. Did the messages get displayed on the selected signs? Terminate all messages. SunGuide-STP

22 3.2.4 High Level DMS Status Support (DMS-5) These tests confirm the ability to exercise numerous control and status Features of the DMS through the DMS GUI. These Features are all located on the DMS extended status GUI. The extended status GUI is accessible either through selecting a specific sign (left click, then clicking the extended status GUI), or by right clicking on the map and selecting DMS Device Status. The user has logged into the SunGuide SM system, initiated the SunGuide SM GUI, and has privileges to use the DMS. The phrase A SELECTED SIGN means to select a sign and use it throughout a single test. Workstation A. Open the DMS Detailed Status GUI, select sign A SELECTED SIGN. Synchronize the clock. From Workstation B, select the same sign. Send a message to the sign. Observe from Workstation A that the status GUI updates to reflect the message now displayed on the sign. Verify through the status logger that no CRC errors are being reported by the DMS subsystem or the DMS driver. Verify the sign is responsive to DMS commands. Verify the sign status is displayed on the GUI. Verify the GUI implements a message library feature in lieu of utilizing the message library feature of the sign. Verify the GUI will cause messages to be displayed on the sign and the status log contains messages indicating the messages were displayed. Verify the GUI implements an exercise shutter command for the DMS. Verify the GUI implements a message priority queue. Check the message dialog box to make sure the command completed successfully. Did the message and updated status appear on Workstation A that did not send the message? Did the command complete without CRC errors? Did the sign respond to commands? Did the GUI display the sign status? Did the GUI implement a message library? Does the GUI cause messages to be displayed on the sign and does the status log contain messages indicating the messages were displayed? Does the GUI implement an exercise shutter command mode? Does the GUI implement a message priority queue? SunGuide-STP

23 Verify the status log contains a log of the communication events to the DMS (from the driver). Utilizing the Executive Handler verify the ability to stop the DMS driver. From the status GUI, select pixel status for A SELECTED SIGN. Observe that the pixel status of the sign is displayed. Does the status log contain a log of the communication events to the DMS (from the driver)? Did the DMS driver successfully accept start and stop commands from the Executive Handler? Was the pixel status correctly displayed? SunGuide-STP

24 3.2.5 DMS Sequences. (DMS-8) DMS sequences are a mechanism to schedule messages for display on DMS at specific times. Specification of DMS sequences consists of selecting a set of DMSs, specifying when and on what repetition cycle, and finally what messages are to be displayed. The phrase A SELECTED SIGN means to select a sign and use it throughout a single test. Right click on the Operator Map background, and select DMS Sequence Libraries. Create a sequence library named ATP, then create a DMS Sequence in that library named ATP- DMS-8. Set the sequence to activate all days of the week. Adjust the start time of the sequence to begin 5 minutes from the current system time. Set the end date to today s date. Add two signs A SELECTED SIGN and A SECOND SELECTED SIGN to the sequence. Edit the item for A SELECTED SIGN. Set the message to FDOT\nDMS 1, and the duration to 2 minutes. Save the item. Did the two messages in the created sequence display at the correct time on the correct signs? Edit the item for A SECOND SELECTED SIGN. Set the message to FDOT Testing\nDMS 2, and the duration to 2 minutes. Save the item. Confirm the creation of the sequence, and then activate the sequence. Wait for 5 minutes or for the messages to be displayed. SunGuide-STP

25 3.2.6 Message Priority Queue 1.1 (DMS-10) The Message Arbitration Subsystem (MAS) implements a priority (1..256) based message queue for controlling DMS and HAR messages. Blank the DMS signs to be used in this test. Open the send DMS message GUI for an active DMS. Compose a message and set the priority to 128. Send the message. Open the MAS queue GUI for the selected sign. Open the send DMS message GUI for the same DMS. Compose a message and set the priority to the lower value of 130. Send the message. Open the send DMS message GUI for the same DMS. Compose a message and set the priority to the higher value of 125. Send the message. Remove the highest priority message from the queue. Remove the first message from the queue. Click the blank queue button. The message should display. See the message is in the queue and is displayed on the sign. Display has Message Priority Expiration Event id (only if a message is associated with an event) Buttons allowed: Edit Change priority Remove Resend top message Find on map Blank queue Note the message is queued for display (see the MAS queue GUI) after the higher priority message. Note the message becomes the active message and is displayed on the sign. Note the first message is now displayed. Note the next highest priority message is now displayed. Message queue is emptied and sign is blanked. SunGuide-STP

26 Go to the map and locate a DMS icon and right click and select Send Message - note the default priority is 1. Using the context menu from the map, go to DMS and Sequence Libraries. Create a new sequence and add a sequence item - note the default priority is 256. Default priority is 1. Note its priority is set to 256. SunGuide-STP

27 3.2.7 Alphabetized Message Library Management (DMS-11) Message libraries are sorted alphabetically for display. A user may type the first few letters of the message name to help locate it within the message library. A message library needs to be configured with multiple messages within it. Display the contents of a message library. Add a new message to the message library. Select a message by typing a few characters of its name into the Search Message Names field. Note the messages are sorted alphabetically by name. Note the library remains sorted. Note the way the selected message is changed to match the typing. SunGuide-STP

28 3.2.8 Multi Page Message Timing (DMS-13) Sign manufacturers differ in the way they implement some commands. While some sign manufacturers build in default timing for multiple page messages, others do not. Furthermore, for those that do implement default timing for multiple page messages, their default times may vary. The system operator may configure the SunGuide SM drivers to default page times. Each driver may have different defaults. No special test preparation is necessary. Inspect the Config.xml file for default page time. This is located in dataproviders dms pollservers pollserver defaultpageontime defaultpageofftime. Compose a multi-page message for a sign. Check the box for default page timing. Post the message. Change the values of defaultpageontime defaultpageofftime Restart the DMS driver. Blank the previous message. Compose a multi-page message for a sign. Check the box for default page timing. Post the message. Note the timing matches the changes made by observing the sign. Results can also be verified by viewing the log files and note that the message contains a [ptxxoyy] message (xx is page on time in seconds times 10 and YY is page off time in seconds times 10). SunGuide-STP

29 3.3 Video There are three SunGuide SM subsystems (and associated drivers) that are part of these tests. These are the CCTV subsystem that implements CCTV (NTCIP 1208 camera) control, Video Switching (VS) that implements IP video switching (control of IP video decoders), and Video Wall that implements the ability to control display to a Barco Argus controller with the Apollo API. Specific devices supported by these subsystems are: NTCIP cameras Impath, vbrick, cortec and teleste video decoders Barco Argus controller with Apollo API Map Access to Cameras (CCTV-1) CCTV (camera) icons appear on the Operator Map at locations approximating where they appear along the roadway. Cameras can be accessed through selecting their respective icons. Once a camera is selected, the CCTV GUI is displayed. Through the CCTV GUI, camera operations can be performed. The system must be running normally with cameras configured within the device database. The workstations should have logged into the SunGuide SM GUI with the map displayed using two user accounts of which both have camera access, but one of which does not have lock break permission while the other does. For sake of reference the workstation logged in without lock override is workstation A, and the workstation with lock override permission is workstation B. Workstation A has a joystick attached to it. The phrases A SELECTED CAMERA or A SECOND SELECTED CAMERA should indicate a camera should be selected and utilized through this test. A SELECTED CAMERA should be displayed on a monitor within the test environment to confirm its selection and control. Using Workstation A, observe the map icons displaying camera locations. Mouse over the camera A SELECTED CAMERA, the GUI displays the current camera status. Click on A SELECTED CAMERA, the camera control GUI will be displayed. Toggle the state of the camera between ACTIVE and OUT OF SERVICE, leaving it in the ACTIVE state. Confirm each change of state in the camera by checking it on Workstation B. View the camera image on the display monitor. Did the map display camera icons? Did the camera status display when moused over? Did the camera status display change when it was changed from the GUI? Is the camera image displayed on the monitor? SunGuide-STP

30 Workstation A. From the operator map, select camera A SECOND SELECTED CAMERA. Click on its icon. This displays the camera control GUI. Attempt any PTZF operation with the camera. This locks the camera. Notice the camera icon has been replaced with a camera and lock icon. Workstation B. From the camera GUI, select camera A SECOND SELECTED CAMERA, note that the camera GUI displays an override button. Do not override the lock at this time. Workstation B. From the camera GUI, select A SECOND SELECTED CAMERA, override the camera lock. Use PTZ controls to confirm the camera lock. Workstation A. Notice the lock has been broken. Notice PTZ controls are disabled. Workstation B. Unlock the camera. Workstation A. Verify the lock has been released by exercising the PTZ controls. Release the lock. Physically examine the cameras being controlled by the GUI, check the model numbers, and verify they conform to NTCIP protocol standards. Workstation A. Using the attached joystick, pan and tilt the camera. Notice the changes to the display monitor as the camera is moved. Physically examine the cameras being controlled by the GUI; there should be multiple vendors under control. Did the camera selected and locked have its icon replaced with the locked camera icon? Did the GUI display an Override instead of a Lock? Did the break lock attempt succeed? Did the Workstation B PTZ control succeed? Did the Workstation A PTZ control fail? Was Workstation A able to acquire a lock? Are the cameras NTCIP cameras? Did the camera move? Are multiple vendors cameras represented by the cameras used in the test? SunGuide-STP

31 3.3.2 IP Video Switching (CCTV-2) Display of video images within the TMC is accomplished by commanding display devices to decode one of the available digital video streams available. Note that there is no support for analog switching within the SunGuide SM software. Display monitors are not directly controlled, but rather decoders attached to those monitors are controlled. They are controlled to the extent that commands are issued to decode specific IP video streams. As the decoders decode the IP video steams, the video represented by the video stream appears on the monitor. Similar to the commanding of IP video decoders, the SunGuide SM software controls a Barco Argus controller with the Apollo interface. The Apollo interface provides a method that external software (SunGuide SM ) can control the layout of an attached wall and the decoding of video streams by available viewers within the layout Test Procedure No special test preparation is necessary. Open the video switching GUI, select the digital video stream from the VBrick encoder and drag it to the VBrick decoder. Open the VBrick Stream Viewer 3, configure it to display a known VBrick video source. Did the selected video stream display on the monitor to which it was dragged? Did the selected video stream display in the Windows Media Viewer? 3 The VBrick Stream Viewer is a commercial available application from VBrick that is compatible with both VBrick and Cortec MPEG2 video streams. It is not compatible with the impath and Teleste streams. Viewers are available from those companies that will display those streams. SunGuide-STP

32 3.3.3 CCTV GUI High Level Status (CCTV-3) Presets, camera availability, and blackout destinations are tested through the use of the GUI. The phrases A SELECTED CAMERA or A SECOND SELECTED CAMERA should indicate a camera should be selected and utilized through this test. The same is true for A SELECTED VIDEO MONITOR. Using the camera GUI, select A SELECTED CAMERA. Change the status to out of service. Check the camera status on another workstation. Change the camera status to Active. Check the camera status on another workstation. Open the administrative GUI. Select video destinations off the CCTV/VS equipment tab. Select A SELECTED VIDEO MONITOR and edit and click the restricted checkbox. Open a video source, select the restricted box. Did the camera status change on the second workstation? Was the switching operation prohibited? Open the video switching control and try to drag the restricted video source to the restricted video destination. Using the camera GUI, select the A SECOND SELECTED CAMERA camera. Position the camera to point at a known object. Save as a preset. Move the camera away from the preset position. Select the preset. The camera should move to the stored preset. Was the preset stored? Did the camera return to the stored preset location? SunGuide-STP

33 3.3.4 Video Tours and Error Logging (CCTV-4) The SunGuide SM software supports the creation and invocation of video tours by issuing commands to display devices to decode appropriate IP video data streams. This limits a video tour to consist of video streams compatible with the video stream decoder (all streams in a tour must be compatible with the decoder being used). As an example, a video tour on a Barco wall cannot consist of a mix of MPEG2 and MPEG4 video streams. The SunGuide SM software logs communication errors and device failures to the Status Logger; these are a subset of the information within the Status Logger, though applying filters can help to isolate these errors. Furthermore, actions taken by users to control cameras and video switching are logged to status logger as well (e.g. camera locks and unlocks). The phrases A SELECTED CAMERA, A SECOND SELECTED CAMERA and A THIRD SELECTED CAMERA indicate a camera should be selected and utilized through this test. Using the Status Log Viewer on one workstation, filter on CCTV subsystem and driver processes. Select NNN - A SELECTED CAMERA from the camera GUI. Start the camera in PTZ motion. While it is moving, power the camera off. Did the CCTV error appear in the status log? Wait for an automatic update or force a manual update within Status Log Viewer. Observe the error within the status log. Use the video switching GUI to establish a video tour consisting of A THIRD SELECTED CAMERA and A SECOND SELECTED CAMERA with each being displayed for 10 seconds. Invoke the tour. Stop the tour. Delete the tour. Use Status Log Viewer and establish a filter to display only CCTV and VS events. Was video tour demonstrated as stored? Did the tour stop? Was the tour deleted? Does Status Log Viewer display CCTV and VS logged events? SunGuide-STP

34 3.3.5 CCTV Auto Lock Request (CCTV-8) Before users can control a camera, a camera lock must be obtained. In this manner, use of cameras by users is serialized only one user may control the camera at any given time. If the user does not request this lock, the system automatically requests the lock at the time the user tries to control the camera. Select a camera which is not locked by another user. From a workstation, a user opens an active camera and tries to move the camera by use of the GUI, joystick, or American Dynamics 300. While that operator is controlling the camera a second operator tries to control the camera. Wait for 120 seconds for the lock to expire. (This value is the timeout value within the CCTV section of the config.xml file.) Note the second operator camera controls are disabled. The second operator should be able to now control the camera. SunGuide-STP

35 3.3.6 American Dynamics 300 MCP Support (CCTV-9) The American Dynamics 300 (AD 300) Master Control Panel is designed to work with an American Dynamics analog video switch. These are rugged devices and have been in use in TMCs for many years. The SunGuide SM system allows use of these devices to control cameras (PTZFI pan, tilt, zoom, focus, iris), issue video switching commands to MPEG decoders and control the Barco video wall. Select a camera that is not locked by another user Using the AD 300, select a camera (type camera number followed by camera button). Control the camera PTZ using the joystick. Using the AD 300, select a camera and switch its display on one of the video monitors (note that not all the camera / encoder pairs are compatible with the decoder / monitor pairs. Using the AD 300, select a camera and switch it to a frame on the layout of the Barco wall. Position the camera, and store a preset (an AD keyboard shortcut list will be provided during the test) (this is an excerpt from the Software Users Manual). Move the camera off the preset. The camera responds as controlled. The camera image appears on the selected monitor. The camera image appears on the selected section of the Barco Wall. The camera should move to the stored preset location. Invoke the preset. SunGuide-STP

36 3.3.7 Device Failure & Device Status Reporting (CCTV-10) Error reporting within the SunGuide SM system is through the system message window. Errors posted to that window include authorization failures and device control command errors. Device status windows show the device status information available through a driver. This test requires the ability to fail a camera. Select an active CCTV. Issue a command to the CCTV and verify that the CCTV is fully operational (no failures). Cause a failure within the CCTV and issue a command to the CCTV. A warning message should appear in the status message window indicating the command failed. SunGuide-STP

37 3.4 Transportation Sensor Subsystem (TSS) The TSS subsystem and its associated drivers control and access traffic sensor data from different sensor technologies. Specific hardware supported in Release 1 includes: 170 controllers running the BiTrans B238 I-4 firmware EIS RTMS devices Wavetronix RTMS devices The devices are polled on a periodic basis and the received traffic data (speed, volume and density) is sent to the Data Bus. The SunGuide SM operator map accesses this data and color codes the represented instrumented segments of highway on the operator map with this information. If traffic speeds fall below a threshold value or traffic densities rise above a threshold, the TSS subsystem will create an alarm that may subsequently become a traffic incident TSS Data Updates (TSS-2) The TSS subsystem collects current traffic data (speed, occupancy, and volume) from traffic field devices. The data is smoothed using a rolling average algorithm with a time period (not sample count) that is configurable for a SunGuide SM installation. The traffic conditions information can be displayed using the operator map GUI by left clicking on an instrumented highway segment. The resulting display contains information about traffic conditions for that segment of highway broken down by lane including: Speed (raw and averaged) Occupancy (raw and averaged) Volume (raw and averaged) Traffic detector / road segment name Time of data collection Detector Latitude and longitude No special test preparation is necessary. Mouse over a roadway link, the name of the roadway link is displayed. Click on a color coded map segment. A detail of the roadway segment is displayed. Using the display, change the operational status of the traffic detector for that roadway segment to out of service, then restore it to active. Is the roadway name displayed? Does the map display roadways and traffic speeds? Did the TSS sensor toggle states between ACTIVE and OUT OF SERVICE? SunGuide-STP

38 Click on one of the freeway segments. The TSS link data GUI displays speed (both raw and smoothed), volume (raw only), and occupancy (both raw and smoothed) on that freeway segment. Observe the link data change over a period of time due to the automatic polling and updates. Open the Status Log Viewer. Place the TSS driver into detailed log mode. Observe the log messages showing the driver is polling the devices on a periodic basis. Does the TSS link data GUI display speed, volume (raw only), and occupancy data in raw and smooth form? Does the displayed data change over time from automatic polling? Does the status log show polling on a periodic basis? SunGuide-STP

39 3.4.2 TSS Generated Alarms (TSS-4) The TSS subsystem will generate an alarm whenever speeds on an instrumented link fall below configurable alarm thresholds, or traffic density on an instrumented link exceeds an alarm threshold. Both of these conditions are used to flag a possible problem on the instrumented link and alert an operator that such a problem may exist. The TSS subsystem does not generate incidents. There is no easy effective manner to generate alarms on command using a live system. No special test preparation is necessary. Observe on the operator GUI that the TSS subsystem generates an alarm. Did the TSS subsystem generate an alarm? The affected traffic segment / lane will begin to flash on the operator map. This will cause the TSS to generate an alarm. Dismiss the alarm. All workstations logged into SunGuide SM will begin to sound an audible alarm. The flashing will stop and audible alarm will stop when the alarm is dismissed. SunGuide-STP