![](media/image1.png)coordinated Highways Action Response Team

state highway administration

CHART II System Requirements

Contract DBM-9713-NMS

**TSR \# 9901961**

**Document \# M361-RS-002R2**

**May 5, 2000**

**By**

**Computer Sciences Corporation and PB Farradyne Inc**

![](media/image2.wmf){width="0.9666666666666667in" height="0.4in"}

  ---------------------------------------------------------------------------
  **Revision**   **Description**          **Pages           **Date**
                                          Affected**        
  -------------- ------------------------ ----------------- -----------------
  0              Initial Release -- R1B2  ALL               February 25, 2000
                 Baseline                                   

  1              Signature Copy -- R1B2   See Appendix B    March 24, 2000
                 Baseline                 for changes       
                                          affecting the     
                                          R1B2 Baseline     
                                          requirements      

  2              Signature Copy -- full   See Appendix B    May 5, 2000
                 system                   for changes from  
                                          Revision 1        

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            
  ---------------------------------------------------------------------------

**Contents**

1 Introduction [1](#introduction)

2 Reference [1](#reference)

3 Requirements [2](#requirements)

3.1 System Administration, Configuration, and Operation
[3](#system-administration-configuration-and-operation)

3.2 Device Management [22](#device-management)

3.3 Display Management [38](#display-management)

3.4 Message Management [46](#message-management)

3.5 Plans [54](#plans)

3.6 Traffic and Roadway Monitoring [57](#traffic-and-roadway-monitoring)

3.7 Activity Management [60](#activity-management)

3.8 Web [77](#web)

3.9 System Maintainability and Availability
[79](#system-maintainability-and-availability)

3.10 Simulation [80](#simulation)

Appendix A - Initial R1B1 to CHART II Requirements Matrix
[1](#appendix-a---initial-r1b1-to-chart-ii-requirements-matrix)

Appendix B -- Document Update History
[1](#appendix-b-document-update-history)

Appendix B.1 -- M361-RS-002R1 [1](#appendix-b.1-m361-rs-002r1)

Appendix B.2 -- M361-RS-002R2 [5](#appendix-b.2-m361-rs-002r2)

Acronyms [1](#acronyms)

Glossary [2](#glossary)

# 1 Introduction

The CHART II System Requirements Specification has been developed based
on the requirements for the CHART Release 1Build 1 (R1B1) initial system
(see DOORS module R1B1 and Appendix A of this document) and the CHART II
Business Area Architecture Report. This document presents the full CHART
II system requirements and supercedes the R1B1 requirements. The R1B1
initial system is to be replaced by a CHART II system meeting the
requirements described in this document. Until such time that a release
of the CHART II system replaces capabilities or functionality described
by an R1B1 requirement the R1B1 requirement is considered in effect.
Traceability from the R1B1 requirements to the CHART II System
Requirements is provided through the DOORS requirements management tool.
Appendices to this document present tables listing the R1B1 initial
system requirements and mappings to the CHART II requirements.

# 2 Reference

Reference materials supporting the specification or derivation of
requirements are listed below.

1\) Letter dated September 1, 1998, from Mike Zezeski, CHART Program
Manager, to Ben Gianni, Operations Director, CSC, Sub: Request for Time
and Cost Proposal.

2\) Telecommunications Service Request (TSR) 9901961 dated September 14,
1998.

3\) CHART II Process Design Meeting Minutes for work session on April
15, 1999, April 22, 1999.

4\) CHART II Process Design Meeting Minutes for work session on April
29, 1999, May 3, 1999.

5\) CHART II Process Design Meeting Minutes for work session on May 13,
1999.

6\) Functional Specification for the FP9500ND-MDDOT Display,
A316111-080, June 16, 1998, Revision: A6.

7\) Maintenance Manual For The FP1001 Display Controller, 316000-443,
January 30, 1987, Revision: E.

8\) Application Guide For The FP2001 Display Controller, A317875-012,
May 14, 1991Revision: 8.

9\) National Transportation Communications for ITS Protocol (NTCIP)
GUIDE(Draft), Prepared by The NTCIP Joint Standards Committee, March 3,
1997.

10\) The Windows Interface Guidelines for Software Design, Copyright ©
1995 by Microsoft Corporation.

11\) The CHART II Requirements Prototype.

12\) CHART II Business Area Architecture/Accelerated Business Area
Architecture Principles, Constraints, and Assumptions Workshop Minutes
on March 19, 1999, March 31, 1999.

13\) CHART II Business Area Architecture Report, April 30, 2000,
M361-BA-005.

# 3 Requirements

The requirements specification has been divided into nine major sections
to logically group requirements. The sections are:

System Administration, Configuration, and Operations

Device Management

Display Management

Message Management

Plans

Traffic and Roadway Monitoring

Activity Management

Web

Reliability, Maintainability, Availability

Simulation

The tables that follow consist of four columns. The first column
contains the requirements organized in sections for ease of reading. The
second and third columns are the system release and build to which the
requirement has been allocated. The fourth column is the unique object
identifier for the requirement. When requirements are added the section
headings for existing requirements may change however the object
identifiers will not.

+------------------------------------------------------+---+---+-----+
| **CHART System Requirements**                        | * | * | **  |
|                                                      | * | * | Obj |
|                                                      | R | B | ect |
|                                                      | e | l | I   |
|                                                      | l | d | d** |
|                                                      | * | * |     |
|                                                      | * | * |     |
+======================================================+===+===+=====+
| ## 3.1                                               |   |   | 5   |
|  System Administration, Configuration, and Operation |   |   |     |
|                                                      |   |   |     |
| This section lists requirements for the              |   |   |     |
| administration, configuration, and operation of the  |   |   |     |
| CHART II system.                                     |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.1.1 Administration                             |   |   | 6   |
|                                                      |   |   |     |
| The system will rely on underlying network,          |   |   |     |
| operating system and physical access controls for    |   |   |     |
| basic security. CHART II system specific access      |   |   |     |
| control and system administration requirements are   |   |   |     |
| listed in this section.                              |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.1 The system shall provide a mec          | 1 | 1 | 7   |
| hanism to define and enforce user functional rights. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.1.1 The system shall suppor              | 1 | 1 | 359 |
| t the grouping of user functional rights into roles. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.1.1.1 There shall be at lea             | 1 | 1 | 8   |
| st one user of the system, with the role of administ |   |   |     |
| rator, who shall have full system functional rights. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.1.1.2 The system shall allow an admi    | 1 | 1 | 14  |
| nistrator to modify the functional rights of a role. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.1.1.3 There shal                        |   |   | 967 |
| l be a role/Center for users belonging to the media. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.1.1.1.3.1 The media role/Cent            |   |   | 968 |
| er shall filter out National Weather Service alerts. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.1.1.1.3.2 The media role/Cente           |   |   | 969 |
| r shall have limited access to Incident information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.1.2 The sy                               | 1 | 1 | 9   |
| stem shall support the assignment of roles to users. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.2 The system shall require a user         | 1 | 1 | 10  |
|  to provide a userid and password in order to login. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 374 |
| #### 3.1.1.2.1 The system shall disable a user\'s ac |   |   |     |
| count after three consecutive failed login attempts. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              | 1 | 1 | 21  |
| .1.1.2.2 The system shall not exceed 15 seconds to c |   |   |     |
| omplete the user login function to the point where t |   |   |     |
| he system is ready to accept commands from the user. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    | 1 | 1 | 11  |
| ### 3.1.1.3 The system shall allow a user to logoff. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.3.1 The system shall not exc             | 1 | 1 | 22  |
| eed 15 seconds to complete the user logout function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.3.2 The system shall                     | 1 | 1 | 23  |
|  not exceed 3 seconds after initiation of the user l |   |   |     |
| ogout function to notify the user of any conditions  |   |   |     |
| that prohibit the completion of the logout function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.4 The system shall                        | 1 | 1 | 12  |
| allow an administrator to create a new user account. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.5 The system sh                           | 1 | 1 | 13  |
| all allow an administrator to delete a user account. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.6                                         | 1 | 1 | 361 |
|  The system shall support the definition of Centers. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.1 A Center shall have a name.          | 1 | 1 | 369 |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.2 A Center shall have a location.      |   |   | 370 |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.3 A Center shall                       |   |   | 362 |
|  have a defined geographical area of responsibility. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.6.3.1 T                                 |   |   | 368 |
| he geographical area of responsibility shall define  |   |   |     |
| the area from which the Center is to receive alerts. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 372 |
| #### 3.1.1.6.3.2 The system shall support the defini |   |   |     |
| tion of geographical area of responsibility for spec |   |   |     |
| ific types of alerts from specific types of devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.4 A Center shal                        |   |   | 363 |
| l have a defined set of functional responsibilities. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.6.4.                                    |   |   | 365 |
| 1 A Center\'s functional responsibilities shall incl |   |   |     |
| ude the functions that Center is allowed to perform. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.6.                                      |   |   | 366 |
| 4.2 A Center\'s functional responsibilities shall in |   |   |     |
| clude the types of alerts that Center is to receive. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.5 A Center shall have a h              |   |   | 364 |
| ierarchical relationship with other Centers for the  |   |   |     |
| purpose of establishing a path for alert escalation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.6.5.                                    |   |   | 371 |
| 1 An alert shall be passed up to the next Center in  |   |   |     |
| the heirarchy if the Center that currently has the a |   |   |     |
| lert does not respond in a specified amount of time. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.6.6 The system sha                       | 1 | 1 | 15  |
| ll assign an operations center to a user upon login. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.1.6.6.1 The ass                           | 1 | 1 | 16  |
| igned operations center shall be the logical site of |   |   |     |
|  the workstation where the user logged into the GUI. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.7 The system s                            | 1 | 1 | 402 |
| hall not allow the last user logged in to a Center t |   |   |     |
| o logoff while that Center has control of resources. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.7.1 The system shall not                 | 1 | 2 | 17  |
|  allow the last user logged in to a Center to logoff |   |   |     |
|  while that Center has an open event assigned to it. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.7.2 The system shall not allow a user    |   |   | 384 |
| to logoff while that user is in control of a camera. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 18  |
| # 3.1.1.8 The system shall provide a change user dia |   |   |     |
| log that allows a new user to logon and an old user  |   |   |     |
| to logoff at the same Center in a single operation.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.8.1 The change user f                    | 1 | 1 | 19  |
| unction shall transfer the old user\'s responsibilit |   |   |     |
| ies to the new user before logging off the old user. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.1.8.2 The system shall not exc             | 1 | 1 | 20  |
| eed 15 seconds to complete the change user function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.1.9 The system shall not excee              | 1 | 1 | 24  |
| d 3 seconds to notify the user that they lack the ap |   |   |     |
| propriate functional rights to perform an operation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.1.2 System Operations                          |   |   | 25  |
|                                                      |   |   |     |
| This section lists requirements for the operation of |   |   |     |
| the system. Requirements listed here are general     |   |   |     |
| requirements for the system as a whole. Requirements |   |   |     |
| specific to one part of the system will be found in  |   |   |     |
| their respective sections.                           |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.1 The system shall provide an online C    |   |   | 373 |
| enter notepad supporting the freeform entry of text. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 376 |
| ### 3.1.2.1.1 A sufficiently privileged user shall b |   |   |     |
| e able to enter information into the Center notepad. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.1.2 The Center notepad s                 |   |   | 377 |
| hall be viewable by any user logged into the Center. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.2 The system shall provide an online ope  |   |   | 375 |
| rator notepad supporting the freeform entry of text. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.2.                                       |   |   | 378 |
| 1 A sufficiently privileged user shall be able to en |   |   |     |
| ter information into a personal operator\'s notepad. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.2.2 An operator notepad s                |   |   | 379 |
| hall be accessible only by the user that created it. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.2.3 A user shall be able to use t        |   |   | 380 |
| heir operator notepad from any Center they log into. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.                                          |   |   | 381 |
| 3 The system shall provide a chat function to allow  |   |   |     |
| users to communicate interactively over the network. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.4 The system shall provide the            |   |   | 387 |
|  capability to define and maintain link information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 389 |
| ## 3.1.2.5 The system shall support the definition a |   |   |     |
| nd maintenance of electronic versions of FITM plans. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.6 Th                                      |   |   | 404 |
| e system shall provide a system monitoring function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.1 T                                    |   |   | 405 |
| he system shall monitor the status of CHART servers. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.2 T                                    |   |   | 406 |
| he system shall monitor the status of CHART clients. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.3 The system sh                        |   |   | 407 |
| all monitor the status of CHART software components. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.4 The system sha                       |   |   | 408 |
| ll monitor the status of CHART communications links. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.5 The syst                             |   |   | 409 |
| em shall monitor the status of CHART legacy systems. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.6.                                       |   |   | 1   |
| 6 The system shall provide the capability to automat |   |   | 067 |
| ically restart selected processes when they go down. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.7 The system                              | 1 | 1 | 26  |
|  shall not exceed 5 seconds to notify the user throu |   |   |     |
| gh the use of an appropriate cursor change (hourglas |   |   |     |
| s or watch) that the system is processing a command  |   |   |     |
| whenever completion of the command is not immediate. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.8 The system shall return contr           | 1 | 1 | 27  |
| ol to the user after the initiation of a command in  |   |   |     |
| a window such that the user is not prevented from pe |   |   |     |
| rforming activities in other windows on the desktop. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.9 The system shall not exc                | 1 | 1 | 28  |
| eed 5 seconds to provide the initiating user with a  |   |   |     |
| list of all operations centers with logged in users. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.1                                         | 1 | 2 | 29  |
| 0 The system shall provide an on-line Help function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.1                                         |   |   | 445 |
| 1 The system shall provide the capability to automat |   |   |     |
| ically notify individuals of specific system events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11.1 The system s                        |   |   | 446 |
| hall support the notification of individuals by FAX. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.1.1 The system shall supp            |   |   | 1   |
| ort the sending of at least four simultaneous FAXes. |   |   | 033 |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.1.2                                  |   |   | 1   |
| The FAX capability shall support distribution lists. |   |   | 037 |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11.2 The system sha                      |   |   | 447 |
| ll support the notification of individuals by email. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.2.1                                  |   |   | 1   |
|  The email package shall support distribution lists. |   |   | 034 |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11.3 The system shal                     |   |   | 448 |
| l support the notification of individuals by paging. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.3.1 The paging capability shal       |   |   | 1   |
| l support paging through multiple service providers. |   |   | 035 |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.                                          |   |   | 1   |
| 2.11.3.2 The paging capability shall support groups. |   |   | 036 |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.3.3 The system shall supp            |   |   | 1   |
| ort the sending of at least four simultaneous pages. |   |   | 038 |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.11.3.4 The paging capability shall not  |   |   | 1   |
| be limited by the number paging service subscribers. |   |   | 039 |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              |   |   | 449 |
| .1.2.11.4 The system shall support the management of |   |   |     |
|  distribution lists of individuals for notification. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11                                       |   |   | 450 |
| .5 The system shall provide the capability to specif |   |   |     |
| y the notification method(s) on an individual basis. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11.6 The system shall provide the        |   |   | 451 |
| capability to associate system events with lists of  |   |   |     |
| individuals to receive notification of those events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.11.7 The system shall record individ     |   |   | 453 |
| ual level notification events in the Operations log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.1                                         | 1 | 1 | 247 |
| 2 The system shall maintain a system operations log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.12.1 The sy                              | 1 | 1 | 479 |
| stem shall have the capability to store at least 14  |   |   |     |
| days of operations log entries in the online system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 480 |
| #### 3.1.2.12.2 All operations log information shall |   |   |     |
|  be retained in an offline searchable archival form. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.12.3 The system s                        |   |   | 481 |
| hall provide the capability to view operations logs. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12.3.1 The                              |   |   | 482 |
|  system shall provide a search capability allowing a |   |   |     |
|  user to search for a specific operations log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12.3.2 The system s                     |   |   | 483 |
| hall provide a filtering capability to allow a user  |   |   |     |
| to select a specified set of operations log entries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.12.4 The system shall store ide          | 1 | 1 | 469 |
| ntifying information with each operations log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.1                                       | 1 | 1 | 470 |
| 2.4.1 The system shall store the Date/time the opera |   |   |     |
| tion was performed with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12                                      | 1 | 1 | 471 |
| .4.2 The system shall store the Workstation Identifi |   |   |     |
| er (if applicable) with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12.4.3 The syste                        | 1 | 1 | 472 |
| m shall store a searchable category type identifying |   |   |     |
|  the type of entry with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12.4.4 The                              | 1 | 1 | 473 |
|  system shall store the User name of initiating user |   |   |     |
| , or the identifier of the initiating application if |   |   |     |
|  system generated, with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.12.4.5 The system shall store the       |   |   | 474 |
|  associated Center with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2                                         | 1 | 1 | 475 |
| .12.4.6 The system shall store the Textual descripti |   |   |     |
| on of action taken with each operations log message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.13 The system shal                        | 1 | 1 | 274 |
| l log messages generated from operations activities. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2                                          | 1 | 1 | 275 |
| .13.1 The system shall log a message for User login. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.13.2 The system                          | 1 | 1 | 276 |
|  shall log a message for Failed user login attempts. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.                                         | 1 | 1 | 277 |
| 13.3 The system shall log a message for User logout. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.1                                        | 1 | 1 | 278 |
| 3.4 The system shall log a message for Adding users. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.13.5                                     | 1 | 1 | 279 |
|  The system shall log a message for Modifying users. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.13.                                      | 1 | 1 | 280 |
| 6 The system shall log a message for Deleting users. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.14 The system shall log operations messa  |   |   | 410 |
| ges associated with the monitoring of system status. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.14.1 The                                 |   |   | 425 |
| system shall log a message for server status change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.14.2 The                                 |   |   | 426 |
| system shall log a message for client status change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.14.3 The system shall                    |   |   | 427 |
|  log a message for software component status change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.14.4 The system s                        |   |   | 428 |
| hall log a message for communications status change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.14.5 The system                          |   |   | 429 |
| shall log a message for legacy system status change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.15                                        | 1 | 2 | 250 |
| The system shall maintain a user communications log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.1 The sy                              | 1 | 2 | 561 |
| stem shall record the communications log entry type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.15.1.1 The choice                       | 1 | 2 | 562 |
| s for communications types shall include In Service. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.15.1.2 The choices fo                   | 1 | 2 | 563 |
| r communications types shall include Out of Service. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.2 The system shall reco               | 1 | 2 | 660 |
| rd the date/time with each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 2 | 752 |
| # 3.1.2.15.3 The system shall store the User name of |   |   |     |
|  initiating user with each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.4 The system shall store the Workst   | 1 | 2 | 750 |
| ation Identifier with each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.5 The system shall store the a        | 1 | 2 | 753 |
| ssociated Center with each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.1                                        | 1 | 2 | 754 |
| 5.6 The system shall allow the user to enter a freef |   |   |     |
| orm text comment with each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.7 The system shall store an identifi  | 1 | 2 | 755 |
| er for the source for each communications log entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.15.8 The system shall provi              | 1 | 2 | 789 |
| de the capability for a user to select one or more c |   |   |     |
| ommunication log entries for conversion to an event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.16 The                                    |   |   | 827 |
|  system shall support an alert capability to display |   |   |     |
|  alert dialogs on user workstations logged in at Cen |   |   |     |
| ters identified to receive the specified alert type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 828 |
| ### 3.1.2.16.1 The system shall support alert types. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.1 The system                       |   |   | 829 |
|  shall support an \"Action from open report\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.2                                  |   |   | 830 |
| The system shall support an \"Alarm timeout\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.3                                  |   |   | 831 |
| The system shall support a \"Device failure\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.4 The system shall supp            |   |   | 832 |
| ort an \"Equipment request from open report\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.5 The sys                          |   |   | 833 |
| tem shall support a \"Transfer of Resources\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.6 The system s                     |   |   | 834 |
| hall support an \"Incident from Open Report\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.7 The syste                        |   |   | 835 |
| m shall support an \"Incident from Detector\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.8 The system shall                 |   |   | 844 |
|  support an \"Incident from External Source\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.9 The                              |   |   | 836 |
| system shall support an \"Incident from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.10 The                             |   |   | 837 |
|  system shall support a \"Disabled from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.11 T                               |   |   | 838 |
| he system shall support a \"Mayday from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.12 The system                      |   |   | 839 |
|  shall support a \"Congestion from Detector\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.13 The system                      |   |   | 840 |
|  shall support a \"Response Plan Generation\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.14 Th                              |   |   | 841 |
| e system shall support a \"Weather Forecast\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.15                                 |   |   | 842 |
| The system shall support a \"Weather Sensor\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.16 The system shall                |   |   | 843 |
| support a \"CHART II Infrastructure Failure\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.1.17 The system sh                   |   |   | 845 |
| all support a \"Delinquent Equipment Status\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #####                                                |   |   | 848 |
| 3.1.2.16.2 The system shall record an alert failure  |   |   |     |
| in the operations log if no users with the correct f |   |   |     |
| unctional rights to receive the alert are logged on. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.16.3 The system shall escalate an alert  |   |   | 849 |
| to the next Center if indicated by the alert type an |   |   |     |
| d no users are logged in that may receive the alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 |   |   | 850 |
| # 3.1.2.16.4 The system shall support the capability |   |   |     |
|  to hold alert types that do not require escalation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.4.1 The system shall disp            |   |   | 851 |
| lay pending alerts to a user with the appropriate fu |   |   |     |
| nctional rights when that user logs into the Center. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              |   |   | 852 |
| .1.2.16.5 The system shall escalate and alert to the |   |   |     |
|  next Center if indicated by the alert type and the  |   |   |     |
| alert is not responded to in a specified time frame. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.16.6 The system shall log a messa        |   |   | 853 |
| ge to the operations log for escalation of an alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              |   |   | 855 |
| .1.2.16.7 The system shall take appropriate action w |   |   |     |
| hen a user acknowledges a \"Mayday from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.7.1 The system shall o               |   |   | 856 |
| pen an Action event for a \"Mayday from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.16.7.2 The system shall display inf     |   |   | 857 |
| ormation on the map for a \"Mayday from AVL\" alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.2.16.7.2.1 The system                    |   |   | 858 |
|  shall display an icon showing the vehicle location. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.2.16.7.                                  |   |   | 859 |
| 2.2 The system shall display the operator call sign. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.2.16.7                                   |   |   | 860 |
| .2.3 The system shall display the vehicle ID number. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.2.                                       |   |   | 861 |
| 16.7.2.4 The system shall display the Mayday status. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1                                          |   |   | 862 |
| .2.16.7.2.5 The system shall display the time and te |   |   |     |
| xt of the last message transmitted from the vehicle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.17 T                                      |   |   | 899 |
| he system shall provide the capability to view the C |   |   |     |
| HART phone book (CHART phone book provided by EORS). |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.18 The system shall support the c         |   |   | 900 |
| apability to periodically download EORS information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.18.1 The system shall support t          |   |   | 901 |
| he capability to download EORS lane closure permits. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.1.1 The system                       |   |   | 903 |
|  shall download EORS lane closure permit attributes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.1.2 The system shall downloa         |   |   | 904 |
| d EORS lane closure permit schedule dates and times. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.1.3 The system shall download EORS   |   |   | 905 |
| lane closure permits at a system specified interval. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.1.4 The syst                         |   |   | 906 |
| em shall support a parameter specifying the number o |   |   |     |
| f days of EORS lane closure permit data to retrieve. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.1.5 The system                       |   |   | 907 |
| shall determine if a conflict exists between an EORS |   |   |     |
|  lane closure permit and a CHART special event item. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.1.2.18.1.5.1                               |   |   | 908 |
| The system shall store lane closure permit conflict  |   |   |     |
| information with the construction permit attributes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.18.2 The sys                             |   |   | 909 |
| tem shall support a parameter specifying the interva |   |   |     |
| l to check EORS construction permits for activation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.2.1 The syst                         |   |   | 910 |
| em shall create a map icon for an EORS permit that i |   |   |     |
| s within a specified time period of becoming active. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.2.2 Right clicking                   |   |   | 911 |
| on an EORS construction permit icon shall provide th |   |   |     |
| e user with the option of opening an Incident event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.18.3 The system shall                    |   |   | 912 |
|  notify EORS when an EORS permit has been activated. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.18.4 The system shall support the cap    |   |   | 902 |
| ability to download EORS snow emergency information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.4.1 The system shall download snow e |   |   | 913 |
| mergency information at a system specified interval. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.4.2 The system sh                    |   |   | 914 |
| all update a county-based snow emergency map layer w |   |   |     |
| hen the county declares or cancels a snow emergency. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.18.4.3 The system shall send notificat  |   |   | 915 |
| ions as specified when a snow emergency is declared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.2.19 The system shall support the capabilit |   |   | 917 |
| y to monitor National Weather Service data as provid |   |   |     |
| ed through the WSI, Inc Weather for Windows package. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.19.1 The system sha                      |   |   | 918 |
| ll provide the capability for a user to view Nationa |   |   |     |
| l Weather Service data stored on the CHART web site. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2                                          |   |   | 919 |
| .19.2 The system shall provide the capability to mon |   |   |     |
| itor National Weather Service severe weather alerts. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.1.2.19.2.1                                  |   |   | 920 |
|  The system shall generate an alert to CHART users i |   |   |     |
| f a new or updated severe weather alert is detected. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.2.19.3 The system                          |   |   | 921 |
|  shall provide the capability to periodically distri |   |   |     |
| bute weather reports to specified recipients by Fax. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 922 |
| ##### 3.1.2.19.3.1 The frequency to distribute weath |   |   |     |
| er reports shall be specified by a system parameter. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.1.3 Equipment Inventory                        |   |   | 814 |
|                                                      |   |   |     |
| The equipment inventory is a list of SHA equipment   |   |   |     |
| used in connection with CHART response to incidents. |   |   |     |
| The system provides functions to maintain the        |   |   |     |
| inventory, equipment status, and to generate alerts  |   |   |     |
| for delinquent equipment.                            |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.3.1 The system shall provide                |   |   | 815 |
|  the capability to maintain the equipment inventory. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.3.1.1 The system shall support the         |   |   | 816 |
|  addition of new equipment entries to the inventory. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.3.1.2 The system shall support the m       |   |   | 817 |
| odification of existing equipment inventory entries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.3.1.3 The system shall                     |   |   | 818 |
| support the deletion of equipment inventory entries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.3.1.4 The system                           |   |   | 820 |
| shall support the allocation of equipment to events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.3.2 The sy                                  |   |   | 819 |
| stem shall provide the capability to periodically sc |   |   |     |
| an the equipment inventory for delinquent equipment. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.3.2.1 The syst                             |   |   | 821 |
| em shall generate an alert for delinquent equipment. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.1.4 Report Generation                          |   |   | 940 |
|                                                      |   |   |     |
| This section lists requirements for the generation   |   |   |     |
| of reports from the CHART system and archive data.   |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.1 The system shall provide the capabilit  |   |   | 941 |
| y to generate reports from online and archived data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.2 The system                              |   |   | 942 |
| shall support the generation of operational reports. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.2.1 The system shall                     |   |   | 945 |
| support the generation of a Center Situation report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.2.2 The system shall suppo               |   |   | 946 |
| rt the generation of a Disable Vehicle event report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.2.3 The system shall                     |   |   | 947 |
|  support the generation of an Incident event report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.2.4 The system sha                       |   |   | 1   |
| ll support the generation of traffic volume reports. |   |   | 068 |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.3 The system sha                          |   |   | 943 |
| ll support the generation of administrative reports. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.1 The sys                              |   |   | 948 |
| tem shall support the generation of a Device report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.2 The system shal                      |   |   | 949 |
| l support the generation of a Device Failure report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.3 The system sha                       |   |   | 950 |
| ll support the generation of a User Activity report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.4 The system shall                     |   |   | 951 |
|  support the generation of a Center Activity report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.5 The system shall su                  |   |   | 952 |
| pport the generation of a Communications log report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.3.6 The system shall supp                |   |   | 953 |
| ort the generation of a Device Configuration report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.4 The system                              |   |   | 944 |
|  shall support the generation of management reports. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.1 The system shall support             |   |   | 954 |
| the generation of a DMS Usage Classification report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.2 The system shall suppor              |   |   | 955 |
| t the generation of a DMS Usage Message Type report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.3 The system shall support the g       |   |   | 956 |
| eneration of a HAR Usage Classification Type report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.4 The system shall suppor              |   |   | 957 |
| t the generation of a HAR Usage Message Type report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.5 The system shall supp                |   |   | 958 |
| ort the generation of an ERU/ETP Assist Type report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.6 The system shall suppor              |   |   | 959 |
| t the generation of an ERU/ETP Total Assists report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.7 The system shall support the gen     |   |   | 960 |
| eration of an ERU/ETP Average Response Times report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.8 The system shall support             |   |   | 961 |
| the generation of an Incident Clearance Time report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  |   |   | 962 |
| ## 3.1.4.4.9 The system shall support the generation |   |   |     |
|  of an Incident Roadway Capacity Restoration report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.10 The system shall support th         |   |   | 963 |
| e generation of an Incident Duration by Type report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.11 The system shall suppor             |   |   | 964 |
| t the generation of an Alarm Acknowledgement report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.12 The system shall sup                |   |   | 965 |
| port the generation of a Detection Subsystem report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.4.4.13 The system shal                     |   |   | 966 |
| l support the generation of a Shop Equipment report. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.5 The system shall provi                  |   |   | 1   |
| de an ad hoc reporting capability for archived data. |   |   | 088 |
+------------------------------------------------------+---+---+-----+
| #### 3.1.4.6 The system shall pr                     |   |   | 1   |
| ovide the capability for users to customize reports. |   |   | 089 |
+------------------------------------------------------+---+---+-----+
| ### 3.1.5 Schedule Management                        |   |   | 869 |
|                                                      |   |   |     |
| This section lists requirements for the management   |   |   |     |
| and execution of scheduled system functions.         |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.1 The system shall all                    |   |   | 870 |
| ow a suitably priviledged user to create a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.1 The system shall a                   |   |   | 874 |
| llow a suitably priviledged user to name a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.2 The system shall allow a su          |   |   | 875 |
| itably priviledged user to specify a begin timestamp |   |   |     |
|  for starting the automatic execution of a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.3 The system shall al                  |   |   | 876 |
| low a suitably priviledged user to specify an ending |   |   |     |
|  timestamp for stopping the execution of a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.4 The system shall su                  |   |   | 887 |
| pport timestamps based on an absolute time and date. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.5 The s                                |   |   | 888 |
| ystem shall support timestamps based on time of day. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.6 The s                                |   |   | 889 |
| ystem shall support timestamps based on day of week. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.7 The sy                               |   |   | 890 |
| stem shall support timestamps based on day of month. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.8 The sy                               |   |   | 892 |
| stem shall support timestamps based on a delta time. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.9 The syst                             |   |   | 891 |
| em shall support timestamps for each scheduled item. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.1.10 The system s                        |   |   | 898 |
| hall delete a schedule with an absolute timestamp af |   |   |     |
| ter the completion of the execution of the schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.2 The system shall all                    |   |   | 871 |
| ow a suitably priviledged user to modify a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.3 The system shall all                    |   |   | 872 |
| ow a suitably priviledged user to delete a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.4 The syste                               |   |   | 885 |
| m shall support the manual initiation of a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.5 The system                              |   |   | 886 |
|  shall support the manual termination of a schedule. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.6 The system shall support t              |   |   | 873 |
| he scheduling of device online and offline commands. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.7 The system s                            |   |   | 877 |
| hall support the scheduling of DMS message commands. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.8 The system s                            |   |   | 878 |
| hall support the scheduling of HAR message commands. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.9 The                                     |   |   | 879 |
| system shall support the scheduling of AVCM presets. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.10 The syst                               |   |   | 880 |
| em shall support the scheduling of camera (source) t |   |   |     |
| o wall monitor (destination) configuration commands. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.11 The                                    |   |   | 881 |
| system shall support the scheduling of camera tours. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.12 The system shall suppo                 |   |   | 882 |
| rt the scheduling of plan activations/deactivations. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.13 The s                                  |   |   | 883 |
| ystem shall support the scheduling of notifications. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.14 The syste                              |   |   | 884 |
| m shall support the scheduling of report generation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.15                                        |   |   | 893 |
| The schedule shall include an associated event type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.15.1 T                                   |   |   | 894 |
| he schedule event types shall include Special Event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.15.2 The sche                            |   |   | 895 |
| dule event types shall include Recurring Congestion. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.1.5.15.3 The                                 |   |   | 896 |
|  schedule event types shall include Safety Messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.1.5.16                                        |   |   | 897 |
| The system shall open a new event corresponding to t |   |   |     |
| he schedule event type when a schedule is activated. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.2 Device Management                             |   |   | 30  |
|                                                      |   |   |     |
| This section lists requirements for the management   |   |   |     |
| and control of CHART remote devices. CHART remote    |   |   |     |
| devices consist of DMSs, HARs, SHAZAMS, AVL units,   |   |   |     |
| CCTV devices, traffic detectors, signals, and        |   |   |     |
| weather stations.                                    |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.1 General Remote Device                      |   |   | 31  |
|                                                      |   |   |     |
| This section lists general requirements that apply   |   |   |     |
| to all remote devices.                               |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.1 The system shall maintain               |   |   | 411 |
|  device attribute information for all CHART devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.1.1 Device attribute information         |   |   | 412 |
| shall include the geographic location of the device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.1.2 Device attribute information s       |   |   | 1   |
| hall include the owning organization for the device. |   |   | 028 |
+------------------------------------------------------+---+---+-----+
| #### 3                                               | 1 | 1 | 32  |
| .2.1.2 The system shall provide a mechanism to poll  |   |   |     |
| devices for status on a configurable interval basis. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.2.1                                      | 1 | 1 | 385 |
| The system shall support the polling of DMS devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.2.2 The system sha                       |   |   | 386 |
| ll support the polling of traffic detection devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.3                                         | 1 | 1 | 33  |
|  The system shall allow a suitably privileged user t |   |   |     |
| o force a status poll of a selected pollable device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.4 The syste                               | 1 | 1 | 34  |
| m shall allow a suitably privileged user to force a  |   |   |     |
| status poll of a selected group of pollable devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.5 The sy                                  | 1 | 1 | 35  |
| stem shall allow a suitably privileged user to alter |   |   |     |
|  the polling interval of a selected pollable device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1                                          | 1 | 1 | 36  |
| .5.1 The minimum polling interval shall be 1 minute. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1                                          | 1 | 1 | 37  |
| .5.2 The maximum polling interval shall be 24 hours. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.5.3 The minimum                          | 1 | 1 | 38  |
|  increment for a polling interval shall be 1 minute. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.6 The system shall inform operators of    | 1 | 1 | 39  |
|  a device communications failure if it is unable to  |   |   |     |
| communicate with a particular device during polling. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.7 The sy                                  | 1 | 1 | 416 |
| stem shall inform the operators of a device failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.1 The                                  | 1 | 1 | 417 |
|  system shall inform the operators of a DMS failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.7.1.1 The syste                         | 1 | 1 | 669 |
| m shall mark a DMS as blank after a timeout threshol |   |   |     |
| d is reached following a DMS communications failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.2.1.7.1.1.1                                |   |   | 1   |
|  The system shall return the current message to the  |   |   | 032 |
| device queue following a DMS communications failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.                                        | 1 | 1 | 670 |
| 7.1.2 The system shall blank a DMS when successful c |   |   |     |
| ommunication with the DMS is resumed after the DMS c |   |   |     |
| ommunications failure timeout threshold has expired. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.7.1.3 The system shall supp             | 1 | 1 | 671 |
| ort a DMS communications failure timeout threshold e |   |   |     |
| xpressed in minutes from 1 minute and 16535 minutes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.2.1.7.1.3.1 The DMS communi                | 1 | 1 | 672 |
| cations failure timeout default shall be 10 minutes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.2 The                                  | 1 | 2 | 418 |
|  system shall inform the operators of a HAR failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.3 The                                  |   |   | 419 |
|  system shall inform the operators of a AVL failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.4 The sys                              |   |   | 420 |
| tem shall inform the operators of a signals failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.5 The syst                             |   |   | 627 |
| em shall inform the operators of a detector failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.6 The system shal                      |   |   | 628 |
| l inform the operators of a weather station failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.7 The                                  |   |   | 824 |
| system shall generate an alert for a device failure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.                                        |   |   | 826 |
| 7.7.1 The system shall open an Action event for the  |   |   |     |
| device failure when the user acknowledges the alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.7.8 The system shall log the devi        |   |   | 825 |
| ce failure status information to the operations log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.8 The system shall allow a suitabl        | 1 | 1 | 40  |
| y privileged user to place an online device offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.9 The system shall allow a suitabl        | 1 | 1 | 41  |
| y privileged user to place an offline device online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.9.1 All commands to onli                 | 1 | 2 | 978 |
| ne devices shall be performed through an open event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.10 The system shall allow a suitably pr   | 1 | 2 | 413 |
| ivileged user to place a device in maintenance mode. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.10.1 Placing a device in                 | 1 | 2 | 414 |
|  maintenance mode shall limit access to the device t |   |   |     |
| o only those users with maintenance mode privileges. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.10.2 Placing a device in ma              | 1 | 2 | 415 |
| intenance mode shall disable polling of that device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.10.3 The system shall restrict c         | 1 | 2 | 972 |
| ertain commands to devices in maintenance mode only. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1                                         | 1 | 2 | 973 |
| .10.3.1 \"Reset DMS\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.2 \"R                              | 1 | 2 | 974 |
| eset HAR controller\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.1                                       | 1 | 2 | 975 |
| 0.3.3 \"Forced Poll\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.4 \"S                              | 1 | 2 | 976 |
| etup HAR controller\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.5 \"Reb                            | 1 | 2 | 977 |
| uild HAR controller\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.6 \"Set HAR                        | 1 | 2 | 994 |
|  transmitter on/off\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.7 \"Change d                       | 1 | 2 | 995 |
| evice configuration\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.8 \"S                              | 1 | 2 | 996 |
| tore message in HAR controller slot\" (except the im |   |   |     |
| mediate message slot) is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.10.3.9 \"Delete message from            | 1 | 2 | 997 |
| HAR controller slot\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.1.1                                       | 1 | 2 | 998 |
| 0.3.10 \"Pixel test\" is a maintenance mode command. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.11 The system sh                          | 1 | 1 | 42  |
| all allow a suitably privileged user to add a new de |   |   |     |
| vice which communicates via an implemented protocol. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.12 The system shall allo                  | 1 | 1 | 43  |
| w a suitably privileged user to specify the necessar |   |   |     |
| y configuration information to make a device usable. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.13 The system shall allow a suitably priv | 1 | 1 | 44  |
| ileged user to change the name of a selected device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.14                                        | 1 | 1 | 45  |
|  The system shall allow a suitably privileged user t |   |   |     |
| o modify the configuration information for a device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.15 The system shall allow a suitably      | 1 | 1 | 46  |
|  privileged user to delete a device from the system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.15.1                                     | 1 | 2 | 1   |
| The system shall not allow a device to be deleted un |   |   | 000 |
| less the device is first placed in an offline state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3                                               | 1 | 1 | 47  |
| .2.1.16 The system shall not exceed 3 seconds to not |   |   |     |
| ify a user that a shared resource they have requeste |   |   |     |
| d is under the control of another operations center. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.17 T                                      | 1 | 1 | 48  |
| he system shall not exceed 12 seconds to complete a  |   |   |     |
| command to a field device (excluding POTS devices).  |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.18 The system shall not                   | 1 | 1 | 49  |
| exceed 15 seconds to notify the user of the completi |   |   |     |
| on status of a command to control a shared resource. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 1 | 50  |
| 3.2.1.19 The system shall not exceed 15 seconds to c |   |   |     |
| hange the status of a device from offline to online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 1 | 51  |
|  3.2.1.20 The system shall not exceed 5 seconds to c |   |   |     |
| hange the status of a device from online to offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.21                                        | 1 | 1 | 52  |
|  The system shall not exceed 5 seconds to notify the |   |   |     |
|  initiating user of the failure to add a new device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.22 The sys                                | 1 | 1 | 53  |
| tem shall not exceed 5 seconds to notify the initiat |   |   |     |
| ing user of the successful addition of a new device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.23 Th                                     | 1 | 1 | 54  |
| e system shall not exceed 3 seconds to display curre |   |   |     |
| nt device configuration data to the initiating user. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.24 The system shal                        | 1 | 1 | 55  |
| l not exceed 5 seconds to notify the initiating user |   |   |     |
|  of the failure to modify device configuration data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.25 The system shall not exc               | 1 | 1 | 56  |
| eed 5 seconds to notify the initiating user of the s |   |   |     |
| uccessful modification of device configuration data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.2                                         | 1 | 1 | 57  |
| 6 The system shall not exceed 3 seconds to notify th |   |   |     |
| e initiating user of the failure to delete a device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.27 The                                    | 1 | 1 | 58  |
|  system shall not exceed 5 seconds to notify the ini |   |   |     |
| tiating user of the successful deletion of a device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.28                                        | 1 | 1 | 281 |
| The system shall log operations messages associated  |   |   |     |
| with the management and control of shared resources. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.1 The system                          | 1 | 1 | 282 |
| shall log a message for Change shared resource name. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.2 The system sha                      | 1 | 1 | 283 |
| ll log a message for Place a shared resource online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.3 The system s                        | 1 | 1 | 284 |
| hall log a message for Take shared resource offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.4 The system shall log a mess         | 1 | 2 | 747 |
| age for Place a shared resource in maintenance mode. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.5 The system shall log a              | 1 | 1 | 285 |
| message for Change shared resource polling interval. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.6 The system shall log a me           | 1 | 1 | 286 |
| ssage for Change in shared resource hardware status. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.7 The system shall log a              | 1 | 1 | 287 |
|  message for Adding a shared resource Configuration. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.8 The system shall log a me           | 1 | 1 | 288 |
| ssage for Modifying a shared resource Configuration. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.28.9 The system shall log a m            | 1 | 1 | 289 |
| essage for Deleting a shared resource Configuration. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 1   |
| ## 3.2.1.29 Data from detection devices shall be mad |   |   | 086 |
| e available to requesting systems on an equal basis. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.29.1 Servi                               |   |   | 1   |
| cing a request for detection data from one system sh |   |   | 087 |
| all not affect the data requested by another system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.1.30 The system shall provide a             |   |   | 1   |
| capability for users to exercise specified system fu |   |   | 090 |
| nctions without affecting operational field devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.1.30.1                                     |   |   | 1   |
|  The system shall provide the capability for a user  |   |   | 091 |
| to perform DMS-related functions on a simulated DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.2 Dynamic Message Signs                      |   |   | 59  |
|                                                      |   |   |     |
| This section lists requirements for the control of   |   |   |     |
| Dynamic Message Signs.                               |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3                                               | 1 | 1 | 60  |
| .2.2.1 The system shall allow a suitably privileged  |   |   |     |
| user to set the current message for a selected DMS.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.2 The system sh                           | 1 | 1 | 61  |
| all allow a suitably privileged user to specify the  |   |   |     |
| beacon state on the selected DMS, if it has beacons. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.3 Th                                      | 1 | 1 | 62  |
| e system shall allow a suitably privileged user to s |   |   |     |
| et the current message for a selected group of DMSs. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.4 The system shall allow a suitably pri   | 1 | 1 | 64  |
| vileged user to blank the display of a selected DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.4.1 If the beacons of a DMS are o        | 1 | 1 | 65  |
| n when the DMS is blanked, they shall be turned off. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 |   |   | 1   |
| # 3.2.2.4.2 Blanking the display of an online DMS sh |   |   | 029 |
| all preempt the currently displayed message, if any. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2                                             | 1 | 1 | 66  |
| .2.5 The system shall allow a suitably privileged us |   |   |     |
| er to blank the display of a selected group of DMSs. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 1 | 68  |
| ## 3.2.2.6 The system shall allow a suitably privile |   |   |     |
| ged user to reset the controller for a selected DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.6.1 The system shall log a mes           | 1 | 1 | 293 |
| sage to the operations log for Reset DMS controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.6.2 The system shall blank the displ     | 1 | 1 | 69  |
| ay of the selected DMS when the controller is reset. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 70  |
| ## 3.2.2.6.3 If the DMS has beacons, the system shal |   |   |     |
| l turn the beacons off when the controller is reset. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.                                             |   |   | 793 |
| 2.2.6.4 The Reset command for a DMS controller shall |   |   |     |
|  preempt any message currently displayed on the DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.7                                         | 1 | 1 | 71  |
|  The system shall allow a suitably privileged user t |   |   |     |
| o reset the controller for a selected group of DMSs. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.                                            | 1 | 1 | 74  |
| 2.8 The system shall support multiple DMS protocols. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.1 The system shall support the         | 1 | 1 | 75  |
| Mark IV FP9500 \"Maryland\" DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.2 The system shall                     | 1 | 1 | 76  |
|  support the Mark IV FP2001 DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.3 The system shall                     | 1 | 1 | 77  |
|  support the Mark IV FP1001 DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.4 The system                           | 1 | 1 | 78  |
|  shall support the Telespot DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.5 The sy                               | 1 | 2 | 79  |
| stem shall support the ADCO DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.6 The system shall su                  | 1 | 2 | 80  |
| pport the Display Solutions DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.8.7 The syst                             | 1 | 2 | 81  |
| em shall support the Sylvia DMS protocol. (Actual pr |   |   |     |
| otocol support is carried out by the FMS subsystem.) |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.9 The system shall provide an applic      | 1 | 1 | 82  |
| ation program interface (API) to implement DMS funct |   |   |     |
| ionality specified in the NTCIP standard NEMA TS3.6. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.10 The system shall al                    | 1 | 1 | 83  |
| low a suitably privileged user to set a DMS offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.10.1 The system shal                     | 1 | 1 | 667 |
| l blank the display of a DMS that is set to offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.11 The system shall a                     | 1 | 1 | 745 |
| llow a suitably privileged user to set a DMS online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.11.1 The system shall immediate          | 1 | 1 | 668 |
| ly blank the display of a DMS that is set to online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.2.11.2 The system shall enabl              |   |   | 797 |
| e the message queue for a DMS that is set to online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.12 The system shall check known error in  | 1 | 1 | 84  |
| dicators in the status packet as specified by the DM |   |   |     |
| S protocol and shall inform operators of a DMS hardw |   |   |     |
| are failure should an error condition be discovered. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.2.13 The sys                                | 1 | 2 | 999 |
| tem shall allow a suitably privileged user to comman |   |   |     |
| d a pixel test on a DMS that supports this function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.3 Highway Advisory Radios                    |   |   | 85  |
|                                                      |   |   |     |
| This section lists requirements for the control of   |   |   |     |
| Highway Advisory Radios.                             |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.                                              | 1 | 2 | 86  |
| 2.3.1 The system shall allow a suitably privileged u |   |   |     |
| ser to set the broadcast message for a selected HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 2 | 459 |
| 3.2.3.2 The system shall allow a suitably privileged |   |   |     |
|  user to set the default message for a selected HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.3 The system shall allow a suitabl        | 1 | 2 | 87  |
| y privileged user to specify the SHAZAM state for ea |   |   |     |
| ch SHAZAM associated with a HAR, if it has a SHAZAM. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.4 The system                              | 1 | 2 | 88  |
|  shall set the default message as the broadcast mess |   |   |     |
| age for a HAR if the current message is inactivated. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.5 Th                                      | 1 | 2 | 89  |
| e system shall allow a suitably privileged user to s |   |   |     |
| et the current message for a selected group of HARs. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.6 The system shall support se             | 1 | 2 | 91  |
| nding messages to at least four HARs simultaneously. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.7 The system shal                         | 1 | 2 | 458 |
| l allow a suitably privileged user to designate from |   |   |     |
|  zero to at least eight SHAZAMs for a specified HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.8 The system shall allow a suitably p     | 1 | 2 | 457 |
| rivileged user to designate from zero to at least ei |   |   |     |
| ght DMSs to be used as a SHAZAM for a specified HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.9 If a HAR has SHAZAMs associated wi      | 1 | 2 | 92  |
| th it and a message that requires SHAZAMs on is sent |   |   |     |
|  to it then the specified SHAZAMs shall be turned on |   |   |     |
|  only after a message has been activated on the HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.10 If                                     | 1 | 2 | 93  |
| a HAR has active SHAZAMs then the SHAZAMs shall be t |   |   |     |
| urned off before the current message is deactivated. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.11 The system                             | 1 | 2 | 94  |
|  shall allow a suitably privileged user to issue the |   |   |     |
|  reset command to the controller for a selected HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.11.1 The system shall log a mes          | 1 | 2 | 297 |
| sage to the operations log for Reset HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.11.2                                     | 1 | 2 | 710 |
|  The system shall issue the setup command immediatel |   |   |     |
| y after a reset command is sent to a HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.12 The system                             | 1 | 2 | 460 |
|  shall allow a suitably privileged user to issue the |   |   |     |
|  setup command to the controller for a selected HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.12.1 The system shall log a mes          | 1 | 2 | 465 |
| sage to the operations log for Setup HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.13 The system s                           | 1 | 2 | 461 |
| hall allow a suitably privileged user to issue the r |   |   |     |
| ebuild command to the controller for a selected HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.13.1 The system shall log a messa        | 1 | 2 | 464 |
| ge to the operations log for Rebuild HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.1                                         | 1 | 2 | 703 |
| 4 The system shall allow a suitably privileged user  |   |   |     |
| select the HAR controller slot number for a message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.14.1 The default                         | 1 | 2 | 708 |
| slot number for the default message shall be slot 2. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.14.2 The default                         | 1 | 2 | 709 |
| slot number for the dynamic message shall be slot 7. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.15 The system                             | 1 | 2 | 713 |
| shall allow a suitably privileged user to delete a m |   |   |     |
| essage from a designated slot in the HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.15                                       | 1 | 2 | 714 |
| .1 The system shall log a message to the operations  |   |   |     |
| log for deletion of a message from a HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2                                             | 1 | 2 | 711 |
| .3.16 The system shall support a SHAZAM device reset |   |   |     |
|  command that sets a SHAZAM to its last known state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.                                         | 1 | 2 | 712 |
| 16.1 The system shall provide the capability to peri |   |   |     |
| odically issue the SHAZAM reset command to a SHAZAM  |   |   |     |
| based on a SHAZAM specific reset interval parameter. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.17 The sys                                | 1 | 2 | 715 |
| tem shall allow a suitably privileged user to play a |   |   |     |
|  message from a selected slot in the HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.18 The system sha                         | 1 | 2 | 726 |
| ll provide the capability for a user at a workstatio |   |   |     |
| n to listen to a message stored in a HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.19 The system shall allow a suitably pr   | 1 | 2 | 716 |
| ivileged user to turn off the transmitter for a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.                                             | 1 | 2 | 717 |
| 2.3.19.1 The system shall log a message to the opera |   |   |     |
| tions log for turning off the transmitter for a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.20 The                                    | 1 | 2 | 725 |
|  system shall support the capability to set SHAZAM d |   |   |     |
| evices offline without affecting the associated HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.20.1 The system shal                     | 1 | 2 | 724 |
| l set to off a SHAZAM device that is placed offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.21 The system shall al                    | 1 | 2 | 743 |
| low a suitably privileged user to set a HAR offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.21.1 The system shall turn               | 1 | 2 | 738 |
| off the transmitter of a HAR that is set to offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.21.2                                     | 1 | 2 | 740 |
|  The system shall place offline all SHAZAM devices a |   |   |     |
| ssociated with a HAR when the HAR is set to offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.3.22 The system shall a                     |   |   | 847 |
| llow a suitably privileged user to set a HAR online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.22.1 The system shall tu                 | 1 | 2 | 739 |
| rn on the transmitter of a HAR that is set to online |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.3.22.2 The system shall allow              | 1 | 2 | 741 |
| the user to selectively place online SHAZAM devices  |   |   |     |
| associated with a HAR when the HAR is set to online. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.4 CCTV Cameras                               |   |   | 619 |
|                                                      |   |   |     |
| This section lists requirements for the control and  |   |   |     |
| management of traffic monitoring video cameras.      |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.4.1 The system shall                        |   |   | 620 |
| allow a suitably privileged user to control cameras. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.4.1.1 The                                  |   |   | 778 |
|  system shall allow a camera user to block/unblock m |   |   |     |
| edia and web access to the video output of a camera. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.4.1.2 The system shall bl                  |   |   | 1   |
| ock camera video from the media and web automaticall |   |   | 040 |
| y when specified users types open a control session. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.4.2 The system shall allow a suitably       |   |   | 621 |
| privileged user to control wall monitor assignments. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.4.3 The system shall                        |   |   | 622 |
|  allow a suitably privileged user to activate tours. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.4.4 The system shall allow a suitably priv  |   |   | 625 |
| ileged user to maintain the camera tour information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.4.5 The system shall allow                  |   |   | 623 |
| a suitably privileged user to maintain CCTV presets. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2                                            |   |   | 624 |
| .4.5.1 The system shall support resetting a camera t |   |   |     |
| o its original default position at a scheduled time. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.5 Detectors                                  |   |   | 629 |
|                                                      |   |   |     |
| This section lists requirements for the receipt of   |   |   |     |
| data from traffic detectors and the management and   |   |   |     |
| control of the detectors.                            |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.5.1 The system shall provide the cap        |   |   | 626 |
| ability to receive detector traffic monitoring data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.5.1.1 The system                           |   |   | 631 |
|  shall archive all detector traffic monitoring data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.5                                           |   |   | 630 |
| .2 The system shall allow a suitably privileged user |   |   |     |
|  to reset a detector, if supported by that detector. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.5.2.1 The system shall log                 |   |   | 823 |
|  a message to the operations log for reset detector. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.5.3 The system shall provide the            |   |   | 1   |
|  capability to assess the validity of detector data. |   |   | 069 |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.5.3.1 The system                           |   |   | 1   |
|  shall determine the validity of loop detector data. |   |   | 070 |
+------------------------------------------------------+---+---+-----+
| ### 3.2.6 Signals                                    |   |   | 632 |
|                                                      |   |   |     |
| This section lists requirements for the receipt of   |   |   |     |
| data from traffic signal devices.                    |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 |   |   | 633 |
| 3.2.6.1 The system shall provide the capability to r |   |   |     |
| eceive traffic monitoring data from traffic signals. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.6.1.1 The system shall                     |   |   | 634 |
|  archive all traffic signal traffic monitoring data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.2.7 Automatic Vehicle Location                 |   |   | 677 |
|                                                      |   |   |     |
| This section lists requirements for Automatic        |   |   |     |
| Vehicle Location (AVL) devices.                      |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.7.1 The system shall                        |   |   | 678 |
| support the receipt of information from AVL devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #####                                                |   |   | 1   |
|  3.2.7.1.1 The system shall archive AVL information. |   |   | 050 |
+------------------------------------------------------+---+---+-----+
| #### 3                                               |   |   | 756 |
| .2.7.2 The system shall provide the capability for a |   |   |     |
|  user to send a message to an AVL equippped vehicle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.7.3 An AVL device shall                     |   |   | 686 |
| be capable of providing status information to CHART. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.3.                                       |   |   | 687 |
| 1 The AVL device shall support sending a vehicle id. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.3.2 The AVL                              |   |   | 688 |
|  device shall support sending an operator call sign. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.3.3                                      |   |   | 691 |
| The AVL device shall support sending vehicle status. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.3.4 Th                                   |   |   | 689 |
| e AVL device shall support sending vehicle location. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.3.4.1 The AVL vehicle l                 |   |   | 690 |
| ocation shall be accurate to better than 100 meters. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.7.4 An AVL dev                              |   |   | 679 |
| ice shall be capable of providing messages to CHART. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.4.1 The AV                               |   |   | 680 |
| L device shall support an In/Out of Service message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.1.1 The system shall record an        |   |   | 685 |
| In/Out of Service message in the Communications log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.                                           |   |   | 681 |
| 7.4.2 The AVL device shall support a Mayday message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.2.1 The syst                          |   |   | 692 |
| em shall record a Mayday message as an Action event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 854 |
| #### 3.2.7.4.2.2 The system shall post a \"Mayday fr |   |   |     |
| om AVL\" alert in response to an AVL Mayday message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.4.3 The A                                |   |   | 682 |
| VL device shall support an Arrival On-Scene message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.3.1                                   |   |   | 693 |
| The system shall record an Arrival On-Scene message  |   |   |     |
| with the event for which the vehicle was dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.3.                                    |   |   | 760 |
| 2 The system shall prompt the user to open a new eve |   |   |     |
| nt or associate the vehicle with an existing open ev |   |   |     |
| ent if an AVL Arrival On-Scene message is received a |   |   |     |
| nd the vehicle is not associated with an open event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.4.4 The AVL device                       |   |   | 683 |
| shall support an Assisting Disabled Vehicle message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.4.1 The system shall record an        |   |   | 761 |
| Assisting Disabled Vehicle message with the Disabled |   |   |     |
|  Vehicle event for which the vehicle was dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7.4.4.2 The sys                           |   |   | 762 |
| tem shall prompt the user to open a new Disabled Veh |   |   |     |
| icle event or associate the vehicle with an existing |   |   |     |
|  open Disabled Vehicle event if an AVL Assisting Dis |   |   |     |
| abled Vehicle message is received and the vehicle is |   |   |     |
|  not associated with an open Disabled Vehicle event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.2.7.4.                                       |   |   | 684 |
| 5 The AVL device shall support an Available message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.2.7                                         |   |   | 763 |
| .4.5.1 The system shall record an Available message  |   |   |     |
| with the event for which the vehicle was dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.2.7.5 The syste                               |   |   | 759 |
| m shall record all AVL communications to an AVL log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.3 Display Management                            |   |   | 95  |
|                                                      |   |   |     |
| This section lists requirements for the management   |   |   |     |
| and presentation of information displayed to the     |   |   |     |
| users. The main display management components are    |   |   |     |
| the map display and the device navigator.            |   |   |     |
|                                                      |   |   |     |
| While some functions can be invoked from the command |   |   |     |
| line the CHART GUI is the primary interface between  |   |   |     |
| the user and the CHART system. The GUI map display   |   |   |     |
| provides an updating multi-layered visual            |   |   |     |
| representation of the status of monitored roadways   |   |   |     |
| and devices. The user can exercise control over zoom |   |   |     |
| levels, panning, selecting map layers for display,   |   |   |     |
| and can access monitored object status and           |   |   |     |
| characteristics directly from the display.           |   |   |     |
|                                                      |   |   |     |
| The device navigator provides a hierarchical view of |   |   |     |
| the CHART devices. Device control functions and      |   |   |     |
| device status information are available through the  |   |   |     |
| navigator.                                           |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.3.1 Device Navigator                           |   |   | 96  |
|                                                      |   |   |     |
| The device navigator provides the user with a GUI    |   |   |     |
| for managing and controlling devices.                |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.1 The navig                               | 1 | 1 | 97  |
| ator shall provide a device group in the tree view.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| #####                                                | 1 | 1 | 98  |
|  3.3.1.1.1 Clicking on the device group shall cause  |   |   |     |
| all system devices to be displayed in the list view. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.2 The navigator shall show the up         | 1 | 1 | 99  |
| dating attributes and status of each of the devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.1 The naviga                           | 1 | 1 | 100 |
| tor shall show the Name/description for each device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.2 The navigator shall show the         | 1 | 1 | 101 |
|  date/time of last change in status for each device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.3 The na                               | 1 | 1 | 102 |
| vigator shall show the Object type for each device.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.4 The navigator                        | 1 | 1 | 103 |
|  shall show the Operational Status for each device.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.4.1 Operational statu                 | 1 | 1 | 104 |
| s shall indicate if the device is Online or Offline. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.4.2 Operat                            | 1 | 1 | 105 |
| ional status shall indicate Hardware Failure values. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.4.3 Operational                       | 1 | 1 | 106 |
| status shall indicate Communications Failure values. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.5 The naviga                           | 1 | 1 | 107 |
| tor shall show the DMS geometry for each DMS device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.6 The navigator                        | 1 | 1 | 108 |
|  shall show the current message for each DMS device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.7 The navigator sha                    | 1 | 2 | 109 |
| ll identify the current message for each HAR device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.8 The navigator                        | 1 | 2 | 727 |
|  shall show the phone numbers associated with a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.8.1 The navigator                     | 1 | 2 | 728 |
|  shall show the phone number for the HAR controller. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.8.2 The navigator s                   | 1 | 2 | 729 |
| hall show the phone number for the HAR monitor line. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.2.8.3 The navigator shall show the p    | 1 | 2 | 730 |
| hone number for each SHAZAM associated with the HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.9 The GUI shall p                      | 1 | 1 | 795 |
| rovide the capability to show the id of each device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.2.10 The GUI shall provide the capabili  | 1 | 1 | 796 |
| ty to show the network connection site for a device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.3 The navigator shall al                  | 1 | 1 | 110 |
| low a user to right click on a device in the list vi |   |   |     |
| ew to display a pop-up control menu for that device. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.4 The navigator shall allow an user       | 1 | 1 | 111 |
| to right click on a selected group of devices to dis |   |   |     |
| play a pop-up control menu for the selected devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.5 The                                     | 1 | 1 | 112 |
|  navigator shall allow a user to sort the informatio |   |   |     |
| n in the list view by clicking on the column header. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 113 |
| # 3.3.1.6 The system shall provide a DMS message edi |   |   |     |
| tor which will allow a user to format a DMS message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.6.1 The DMS message editor shall a       | 1 | 1 | 114 |
| llow a user to enter message text into a text field. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.6.2 The DMS message editor sha           | 1 | 1 | 115 |
| ll show the operator an updating view of the message |   |   |     |
|  text formatted for the smallest DMS being altered,  |   |   |     |
| with the option to view the other selected formats.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.6.3                                      | 1 | 1 | 116 |
| The DMS message editor shall inform the operator if  |   |   |     |
| the entered message text would be truncated when for |   |   |     |
| matted to fit any of the selected DMS being altered. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.6.4 When a group of DMSs are selec       | 1 | 1 | 117 |
| ted to receive the same message, the message editor  |   |   |     |
| shall format the message for each DMS type selected. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.6.5 The system sha                       | 1 | 1 | 118 |
| ll not allow truncated messages to be sent to a DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 2 | 119 |
| ## 3.3.1.7 The system shall provide a HAR message ed |   |   |     |
| itor that will allow a user to format a HAR message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.1 For t                                | 1 | 2 | 120 |
| ext messages the HAR message editor shall display th |   |   |     |
| e message header, message body, and message trailer. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.2 The HAR message editor shall a       | 1 | 2 | 121 |
| llow a user to enter message text into a text field. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              | 1 | 2 | 122 |
| .3.1.7.3 The HAR message editor shall allow a user t |   |   |     |
| o hear the result of text to speech conversion of th |   |   |     |
| e message header, message body, and message trailer. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              | 1 | 2 | 123 |
| .3.1.7.4 The HAR message editor shall display the ru |   |   |     |
| n time of the spoken message in minutes and seconds. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 2 | 124 |
| ### 3.3.1.7.4.1 The HAR message editor shall alert t |   |   |     |
| he user if the message run time exceeds two minutes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.5 The HAR message e                    | 1 | 2 | 694 |
| ditor shall support the recording of voice messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.6 The                                  | 1 | 2 | 695 |
| HAR message editor shall provide audio control funct |   |   |     |
| ions for controlling the playback of audio messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.7.6.1 The HAR message edito             | 1 | 2 | 696 |
| r shall provide a PLAY button to play an audio file. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 2 | 697 |
| ## 3.3.1.7.6.2 The HAR message editor shall provide  |   |   |     |
| a STOP button to stop the playback of an audio file. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               | 1 | 2 | 698 |
|  3.3.1.7.6.3 The HAR message editor shall provide a  |   |   |     |
| PAUSE button to pause the playback of an audio file. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.7 The HAR message editor shall provide | 1 | 2 | 699 |
|  the capability to construct a single continuous mes |   |   |     |
| sage from any of a message header, body and trailer. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.                                            | 1 | 2 | 718 |
| 3.1.7.7.1 The HAR message editor shall provide the c |   |   |     |
| apability to insert delays between message segments. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #####                                                | 1 | 2 | 720 |
| # 3.3.1.7.7.2 The HAR message editor shall provide t |   |   |     |
| he capability to construct a message for broadcast f |   |   |     |
| rom messages currently residing in controller slots. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.7.8 The HAR message editor shall suppor  | 1 | 2 | 721 |
| t an optional time/date field in the message header. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 2 | 722 |
| ### 3.3.1.7.8.1 The system shall support the automat |   |   |     |
| ic update of the HAR message header time/date field. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.1.7.8.2 The H                             | 1 | 2 | 723 |
| AR message header time/date field shall support cust |   |   |     |
| omizable generalized time periods relating time of d |   |   |     |
| ay to a period of day (e.g. 1200-1700 as afternoon). |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.8 The system shall provide a DMS          | 1 | 1 | 125 |
|  show display window, which will show a graphical de |   |   |     |
| piction of the current message for a particular DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.                                          | 1 | 1 | 126 |
| 9 The navigator shall provide a DMS message library  |   |   |     |
| group in the tree view for each DMS message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 127 |
| ## 3.3.1.9.1 Clicking on the DMS Message Library gro |   |   |     |
| up shall cause all DMS library messages stored in th |   |   |     |
| e selected library to be displayed in the list view. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.10 The navigator                          | 1 | 1 | 128 |
|  shall show the attributes for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.10.1 The navigator shall sh              | 1 | 1 | 129 |
| ow the Message description for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.10.2 The navigator s                     | 1 | 1 | 130 |
| hall show the Message text for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.10.3 The navigator sha                   | 1 | 1 | 131 |
| ll show the Topic/Category for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 1 | 132 |
| ### 3.3.1.10.4 The navigator shall show the Required |   |   |     |
|  sign length in characters for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.1.10.5 The navigator shall                 | 1 | 1 | 133 |
|  show the Beacon indicator for each library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.11 The                                    | 1 | 1 | 134 |
|  navigator shall allow a suitably privileged user to |   |   |     |
|  drag a DMS message from a message library to a DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.12 The                                    | 1 | 2 | 135 |
|  navigator shall allow a suitably privileged user to |   |   |     |
|  drag a HAR message from a message library to a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.13 The syst                               | 1 | 2 | 462 |
| em shall allow a suitably privileged user to specify |   |   |     |
|  the message header and trailer for a specified HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.14 The navigator shall allow              | 1 | 1 | 136 |
|  a suitably privileged user to drag a DMS message fr |   |   |     |
| om a message library to a group of DMSs for display. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.15 The system shall notify the initiati   | 1 | 1 | 137 |
| ng operator should an attempt to control a DMS fail. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.16 The system shall notify the initiati   | 1 | 2 | 138 |
| ng operator should an attempt to control a HAR fail. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 2 | 719 |
| ## 3.3.1.17 The navigator shall provide the capabili |   |   |     |
| ty to display the controller slots in use for a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3                                             | 1 | 1 | 139 |
| .1.18 The system shall notify all operators of succe |   |   |     |
| ssful DMS control activities by updating the run-tim |   |   |     |
| e status information displayed in the navigator, and |   |   |     |
|  any windows that currently display the DMS message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.19 The system shall not exceed 20 secon   | 1 | 1 | 140 |
| ds to update all active displays on the state of a d |   |   |     |
| isplayed object after a state change in that object. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.20 The sys                                | 1 | 1 | 141 |
| tem shall not exceed 20 seconds to update all active |   |   |     |
|  displays after a new display object has been added. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.1.21 The s                                  | 1 | 1 | 142 |
| ystem shall not exceed 20 seconds to update all acti |   |   |     |
| ve displays after a display object has been deleted. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.3.2 Map Display                                |   |   | 143 |
|                                                      |   |   |     |
| The map display provides the user with a visual      |   |   |     |
| representation of the status of the monitored        |   |   |     |
| roadways and devices.                                |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.2.1 The map display shall show links.       |   |   | 388 |
+------------------------------------------------------+---+---+-----+
| #### 3.3.2.2 The system shall provide the capability |   |   | 403 |
|  to update the CHART map from the MDOT GIS Map data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.2.3 The sy                                  |   |   | 440 |
| stem shall provide a Map position location function. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.3.1                                      |   |   | 441 |
|  The system shall provide the capability for the use |   |   |     |
| r to move the mouse over the Map and view an updatin |   |   |     |
| g display of the cursor position in map coordinates. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.3.2 The system shall p                   |   |   | 443 |
| rovide the capability for the user to view position  |   |   |     |
| (distance and bearing) relative to a selected point. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.3.3 The system shall provide the         |   |   | 442 |
|  capability for the user to select the displayed pos |   |   |     |
| ition information for inclusion with an event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.3.4 The system shall                     |   |   | 444 |
| provide the capability to build a database of map co |   |   |     |
| ordinates for selected landmarks along each highway. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.3.5 The system shall p                   |   |   | 603 |
| rovide the capability to capture a selected portion  |   |   |     |
| of the display for inclusion with an incident event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.2.3.5.1 The captured displ                |   |   | 604 |
| ay graphic shall show the direction of travel lanes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.2.3.5.2 The capt                          |   |   | 605 |
| ured display graphic shall show the number of lanes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.2.3.5.3 Th                                |   |   | 606 |
| e captured display graphic shall show ramps, if any. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.3.2.3.5.4 The captured                      |   |   | 607 |
| display graphic shall show collection lanes, if any. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              |   |   | 496 |
| .3.2.3.6 The system shall provide the capability for |   |   |     |
|  a user to select from a list of landmarks and have  |   |   |     |
| the cursor move to that position on the map display. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.2.4 The map display shall have the c        |   |   | 757 |
| apability to show the location of all CHART devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 |   |   | 758 |
|  3.3.2.5 The map display shall provide the capabilit |   |   |     |
| y to show the location of all AVL equipped vehicles. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.3.2.6 The map display                         |   |   | 1   |
| shall support the display of independent map layers. |   |   | 071 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6.1 The map display shall suppo          |   |   | 1   |
| rt a base map layer showing major Maryland highways. |   |   | 072 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6                                        |   |   | 1   |
| .2 The map display shall support a device map layer. |   |   | 073 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6.                                       |   |   | 1   |
| 3 The map display shall support a weather map layer. |   |   | 074 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6.4                                      |   |   | 1   |
| The map display shall support an incident map layer. |   |   | 075 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6.5 The                                  |   |   | 1   |
|  map display shall support a lane closure map layer. |   |   | 076 |
+------------------------------------------------------+---+---+-----+
| ##### 3.3.2.6.6 The map di                           |   |   | 1   |
| splay shall provide the capability for the user to f |   |   | 077 |
| ilter a map layer in order to customize the display. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.4 Message Management                            |   |   | 144 |
|                                                      |   |   |     |
| This section presents requirements for the           |   |   |     |
| construction and management of messages to be        |   |   |     |
| displayed or broadcast on CHART devices. Message     |   |   |     |
| management requirements are divided into three       |   |   |     |
| areas. Requirements for supported protocols and the  |   |   |     |
| formatting of messages are covered in Message        |   |   |     |
| Formats. The system will support the grouping of     |   |   |     |
| messages into libraries as an aid to users in        |   |   |     |
| organizing messages. Requirements for message        |   |   |     |
| libraries are presented the the section titled       |   |   |     |
| Message Libraries. The system will support           |   |   |     |
| dictionaries for checking the spelling and content   |   |   |     |
| of messages. Requirements for dictionary support are |   |   |     |
| presented in the section titled Dictionaries.        |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.4.1 Message Formats                            |   |   | 145 |
|                                                      |   |   |     |
| This section presents requirements for the           |   |   |     |
| formatting of messages.                              |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.1.1 The system shall for                    | 1 | 1 | 146 |
| mat DMS messages using the MULTI DMS mark-up languag |   |   |     |
| e as specified in the NTCIP document ISO/WD 14823-2. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3                                               | 1 | 1 | 156 |
| .4.1.2 The system shall support MULTI language tags. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #####                                                | 1 | 1 | 157 |
| 3.4.1.2.1 The system shall support the New Page \[np |   |   |     |
| \] MULTI language tag. Used to specify a phase break |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.                                         | 1 | 1 | 158 |
| 2.2 The system shall support the New Line \[nlx\] MU |   |   |     |
| LTI language tag. Used to specify a new line of text |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 1 | 159 |
| ### 3.4.1.2.3 The system shall support the Justifica |   |   |     |
| tion -- line \[jlx\] MULTI language tag. Used to spe |   |   |     |
| cify the justification for the current line of text. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.2.4 The system sha                       | 1 | 1 | 160 |
| ll support the Page timing \[ptxoy\] MULTI language  |   |   |     |
| tag. Used to specify the time-on and time-off in ten |   |   |     |
| ths of a second for a particular phase of a message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.1.3 The sy                                  | 1 | 1 | 147 |
| stem shall format message text for display on a DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.1 All t                                | 1 | 1 | 148 |
| ext lines shall be centered horizontally on the DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              | 1 | 1 | 149 |
| .4.1.3.2 Any phase (page on a sign display) with one |   |   |     |
|  line of text shall be displayed on the center line. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.3 Any phas                             | 1 | 1 | 150 |
| e (page on a sign display) with two lines of text sh |   |   |     |
| all have that text displayed on lines one and three. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.4 The phrase \                         | 1 | 1 | 151 |
| "Expect Delays\" may be broken up between two lines. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.5 The DMS message format The phras     | 1 | 1 | 154 |
| e \"Stay Alert\" may be broken up between two lines. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.6 The system shall employ rules for    | 1 | 1 | 152 |
|  formatting route type and route number information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.1 Th                                | 1 | 1 | 390 |
| e system shall format onto one line the route inform |   |   |     |
| ation that contains the route type "MD" followed by  |   |   |     |
| a space and another continuous string of characters. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.2 Th                                | 1 | 1 | 391 |
| e system shall format onto one line the route inform |   |   |     |
| ation that contains the route type "I" followed by a |   |   |     |
|  space and another continuous string of characters.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.3 Th                                | 1 | 1 | 392 |
| e system shall format onto one line the route inform |   |   |     |
| ation that contains the route type "US" followed by  |   |   |     |
| a space and another continuous string of characters. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.4 Th                                | 1 | 1 | 393 |
| e system shall format onto one line the route inform |   |   |     |
| ation that contains the route type "Ex" followed by  |   |   |     |
| a space and another continuous string of characters. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.5 The                               | 1 | 1 | 394 |
| system shall format onto one line the route informat |   |   |     |
| ion that contains the route type "Exit" followed by  |   |   |     |
| a space and another continuous string of characters. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.                                      | 1 | 1 | 395 |
| 6.6 The system shall keep the route direction " N" o |   |   |     |
| n the same line as the preceding route information.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.                                      | 1 | 1 | 396 |
| 6.7 The system shall keep the route direction " S" o |   |   |     |
| n the same line as the preceding route information.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.                                      | 1 | 1 | 397 |
| 6.8 The system shall keep the route direction " E" o |   |   |     |
| n the same line as the preceding route information.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.                                      | 1 | 1 | 398 |
| 6.9 The system shall keep the route direction " W" o |   |   |     |
| n the same line as the preceding route information.  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.                                    | 1 | 1 | 399 |
| 10 The system shall place on a new line any route in |   |   |     |
| formation that is lead by the route indicator "AT".  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.11                                  | 1 | 1 | 400 |
|  The system shall place on a new line any route info |   |   |     |
| rmation that is lead by the route indicator "PRIOR". |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.6.12                                  | 1 | 1 | 401 |
|  The system shall place on a new line any route info |   |   |     |
| rmation that is lead by the route indicator "PAST".  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.7 Each DMS                             | 1 | 1 | 155 |
| shall use only one font for displaying DMS messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.1.3.8 The system shall en                  | 1 | 2 | 731 |
| force a default limit of two pages for DMS messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.1.3.8.1 A suitably privileged user sha    | 1 | 2 | 732 |
| ll be able to create messages longer than two pages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.1.4                                         | 1 | 2 | 161 |
|  The system shall support the conversion of text to  |   |   |     |
| speech files compatible with standard audio formats. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4                                             | 1 | 2 | 454 |
| .1.5 The system shall support the recording of speec |   |   |     |
| h into files compatible with standard audio formats. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.4.2 Message Libraries                          |   |   | 162 |
|                                                      |   |   |     |
| This section presents requirements for the           |   |   |     |
| management of message libraries.                     |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 1 | 163 |
|  3.4.2.1 The system shall support message libraries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.1.1 The sys                              | 1 | 1 | 164 |
| tem shall support libraries containing DMS messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.1.2 The sys                              | 1 | 2 | 165 |
| tem shall support libraries containing HAR messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.1.2.1 The system shall suppo            | 1 | 2 | 455 |
| rt storing HAR messages in libraries in text format. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    | 1 | 2 | 456 |
| ##### 3.4.2.1.2.2 The system shall support storing H |   |   |     |
| AR messages in libraries in a standard audio format. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.2 The system shall allow a suita          | 1 | 1 | 166 |
| bly privileged user to create a new message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.3 The system shall allow a s              | 1 | 1 | 167 |
| uitably privileged user to delete a message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 1 | 168 |
| ### 3.4.2.3.1 The deletion of a message library shal |   |   |     |
| l delete all messages stored in the library as well. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.4 The system shall allow a suitably priv  | 1 | 1 | 169 |
| ileged user to change the name of a message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.5 The system shall allow a suita          | 1 | 1 | 170 |
| bly privileged user to create a new library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.5.1 The system shall support             | 1 | 1 | 674 |
|  setting the beacon state for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.5.2 The system shall support a messa     |   |   | 1   |
| ge attribute indicating that a message is sign-speci |   |   | 066 |
| fic and is only to be displayed on a specified sign. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.6 The system shall allow a s              | 1 | 1 | 171 |
| uitably privileged user to delete a library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 172 |
| # 3.4.2.7 The system shall allow a suitably privileg |   |   |     |
| ed user to modify the contents of a library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.8 The system shall allow a suitably priv  | 1 | 1 | 173 |
| ileged user to change the name of a library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 1 | 673 |
|  3.4.2.9 The system shall allow a suitably privilege |   |   |     |
| d user to display the contents of a library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.9.1 The system shall allow the           | 1 | 1 | 798 |
| user to display attributes of a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.1.1 The system shall displa           | 1 | 1 | 800 |
| y the message description for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.1.2 The system shall                  | 1 | 1 | 801 |
|  display the message text for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.1.3 The system shall dis              | 1 | 1 | 802 |
| play the message category for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.1.4 The system shall display the req  | 1 | 1 | 803 |
| uired message sign length for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.1.5 The system shall display the      | 1 | 1 | 804 |
|  message beacon indicator for a DMS library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.9.2 The system shall allow the           | 1 | 2 | 799 |
| user to display attributes of a HAR library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.2.1 The system shall displa           | 1 | 2 | 805 |
| y the message description for a HAR library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.9.2.2 The system shall dis              | 1 | 2 | 806 |
| play the message category for a HAR library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3                                             | 1 | 2 | 807 |
| .4.2.9.2.3 The system shall display the message leng |   |   |     |
| th in minutes and seconds for a HAR library message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.10 The system shall al                    | 1 | 1 | 174 |
| low a suitably privileged user to set a message on a |   |   |     |
|  DMS from a message stored in a DMS message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.11 The system shall al                    | 1 | 2 | 175 |
| low a suitably privileged user to set a message on a |   |   |     |
|  HAR from a message stored in a HAR message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.12 The system                             | 1 | 1 | 176 |
| shall not exceed 3 seconds to notify the initiating  |   |   |     |
| user that the library message could not be modified. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.13 The system                             | 1 | 1 | 177 |
|  shall not exceed 3 seconds to notify the initiating |   |   |     |
|  user that the library message could not be deleted. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.14 The sy                                 | 1 | 1 | 178 |
| stem shall not exceed 3 seconds to notify the initia |   |   |     |
| ting user on an attempt to delete a library message  |   |   |     |
| that the message is being used in one or more plans. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.15 The system shal                        | 1 | 1 | 179 |
| l not exceed 3 seconds to notify the initiating user |   |   |     |
|  that the message could not be added to the library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.16 The sys                                | 1 | 1 | 180 |
| tem shall not exceed 3 seconds to notify the initiat |   |   |     |
| ing user that the library name could not be changed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.17 Th                                     | 1 | 1 | 181 |
| e system shall not exceed 3 seconds to notify the in |   |   |     |
| itiating user that the library could not be deleted. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.18 Th                                     | 1 | 1 | 182 |
| e system shall not exceed 3 seconds to notify the in |   |   |     |
| itiating user that the library could not be created. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.2.19 The system shall log operations        | 1 | 1 | 298 |
| messages associated with Message Library management. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.19.1 The syst                            | 1 | 1 | 299 |
| em shall log a message for Message Library creation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.19.2 The syst                            | 1 | 1 | 300 |
| em shall log a message for Message Library deletion. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.2.19.3 The system shal                     | 1 | 1 | 301 |
| l log a message for Change to the Message Libraries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.19.3.1 The system shall log a message   | 1 | 1 | 302 |
|  for the addition of a message to a Message Library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.2.19.3.2 The system shall log a message f | 1 | 1 | 303 |
| or the deletion of a message from a Message Library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.4.3 Dictionaries                               |   |   | 183 |
|                                                      |   |   |     |
| This section presents requirements on the use of     |   |   |     |
| dictionaries for checking message content.           |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.1 The system shall support the            | 1 | 1 | 184 |
|  use of dictionaries for checking words in messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.3.1.1                                      | 1 | 1 | 185 |
|  The system shall support a banned words dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.3.1.1.1 The system shal                   | 1 | 1 | 772 |
| l support a banned words dictionary for DMS devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.3.1.1.2 The system shal                   | 1 | 2 | 773 |
| l support a banned words dictionary for HAR devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.3.1.2 The system sha                       | 1 | 2 | 186 |
| ll support a dictionary for spell checking messages. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.3.1.2.1 The system sha                    | 1 | 2 | 774 |
| ll support a spell check dictionary for DMS devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.3.1.2.2 The system sha                    | 1 | 2 | 775 |
| ll support a spell check dictionary for HAR devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    | 1 | 2 | 187 |
| #### 3.4.3.1.3 The system shall support the option o |   |   |     |
| f enabling a dictionary on an individual user basis. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.3.1.4 Messages checked against             | 1 | 1 | 188 |
| a banned words dictionary shall be rejected if any w |   |   |     |
| ord in the message matches a word in the dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.4.3.1.5 A word checke                        | 1 | 2 | 189 |
| d against a spell check dictionary shall be flagged  |   |   |     |
| if the word does not match a word in the dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.4.3.1.5.1 A flagged word sha                | 1 | 2 | 704 |
| ll require user action before a message is accepted. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               | 1 | 2 | 705 |
| # 3.4.3.1.5.1.1 User action for a flagged word shall |   |   |     |
|  include the option of selecting a word from a pick  |   |   |     |
| list of suggested words to correct the flagged word. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    | 1 | 2 | 706 |
| ###### 3.4.3.1.5.1.2 User action for a flagged word  |   |   |     |
| shall include allowing a suitably privileged user to |   |   |     |
|  add the flagged word to the spell check dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.4.3.1.5.1.3                                | 1 | 2 | 707 |
|  User action for a flagged word shall include allowi |   |   |     |
| ng the user to ignore the flagged word and continue. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.2 The system shall have the capa          | 1 | 1 | 190 |
| bility to check all text messages on input against a |   |   |     |
|  dictionary before sending the message to the field. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.3 The system shall have the capability t  | 1 | 1 | 191 |
| o check all text messages on input against a diction |   |   |     |
| ary before storing the message in a message library. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   | 1 | 1 | 192 |
| ## 3.4.3.4 The system shall allow a suitably privile |   |   |     |
| ged user to add a new list of words to a dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.5 The system shall allow a suitably       | 1 | 1 | 193 |
|  privileged user to remove a word from a dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 1 | 195 |
| # 3.4.3.6 The system shall not exceed 3 seconds to n |   |   |     |
| otify the user that a message contains banned words. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.7 The system shall                        | 1 | 1 | 196 |
| not exceed 3 seconds to provide the suitably privile |   |   |     |
| ged initiating user with a list of dictionary words. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.8                                         | 1 | 1 | 197 |
|  The system shall not exceed 5 seconds to notify the |   |   |     |
|  user that the word(s) were added to the dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.9 Th                                      | 1 | 1 | 198 |
| e system shall not exceed 3 seconds to notify the us |   |   |     |
| er that a word could not be added to the dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.4.3.10 The system shall                       | 1 | 1 | 676 |
|  require a user with privileges to access the banned |   |   |     |
|  words dictionary to re-enter their password prior t |   |   |     |
| o allowing them to view the banned words dictionary. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.5 Plans                                         |   |   | 199 |
|                                                      |   |   |     |
| Plans are collections of actions to be executed as a |   |   |     |
| group. The CHART II system will support the creation |   |   |     |
| of plan libraries and the execution of plans by      |   |   |     |
| users, and automatically in response to system       |   |   |     |
| events.                                              |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.5.1 Plan Management                            |   |   | 200 |
|                                                      |   |   |     |
| This section present requirements on the management  |   |   |     |
| of plan libraries.                                   |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.1 The system shal                         | 1 | 1 | 201 |
| l allow a suitably privileged user to create a plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.                                             | 1 | 1 | 202 |
| 5.1.1.1 The plan shall include the plan description. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.1.2 Th                                   | 1 | 1 | 203 |
| e plan shall include a list of actions to implement. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.1 The allowable plan item actio     | 1 | 1 | 204 |
| ns shall include putting a library message on a DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.2 The allowable plan item actio     | 1 | 2 | 205 |
| ns shall include putting a library message on a HAR. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.3 The allowab                       |   |   | 1   |
| le plan item actions shall include sending an email. |   |   | 078 |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.4 The allow                         |   |   | 1   |
| able plan item actions shall include sending a page. |   |   | 079 |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.5 The allo                          |   |   | 1   |
| wable plan item actions shall include sending a fax. |   |   | 080 |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.1.1.2.6 The allowable                     |   |   | 1   |
| plan item actions shall include generating a report. |   |   | 081 |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.2 The system shal                         | 1 | 1 | 206 |
| l allow a suitably privileged user to modify a plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.3 The system shal                         | 1 | 1 | 207 |
| l allow a suitably privileged user to delete a plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.4                                         | 1 | 1 | 208 |
|  The system shall not exceed 5 seconds to notify the |   |   |     |
|  initiating user that a plan was successfully added. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.5 Th                                      | 1 | 1 | 209 |
| e system shall not exceed 5 seconds to notify the in |   |   |     |
| itiating user that a plan was successfully modified. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1                                           | 1 | 1 | 210 |
| .6 The system shall not exceed 5 seconds to notify t |   |   |     |
| he initiating user that a plan could not be created. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.                                          | 1 | 1 | 211 |
| 7 The system shall not exceed 3 seconds to notify th |   |   |     |
| e initiating user that a plan could not be modified. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3                                               | 1 | 1 | 212 |
| .5.1.8 The system shall not exceed 5 seconds in disp |   |   |     |
| laying a list of messages and message libraries to t |   |   |     |
| he initiating user when the user creates a new plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.9                                         | 1 | 1 | 213 |
| The system shall not exceed 3 seconds in displaying  |   |   |     |
| a list of messages and message libraries to the init |   |   |     |
| iating user when the user modifies an existing plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.1.10 The system shall log                   | 1 | 1 | 304 |
| operations messages associated with Plan management. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.10.1 The system shall lo                 | 1 | 1 | 305 |
| g a message to the operations log for Adding a Plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.10.2 The system shall log a              | 1 | 1 | 306 |
|  message to the operations log for Modifying a Plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.10.3 The system shall log                | 1 | 1 | 307 |
| a message to the operations log for Deleting a Plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.10.4 The system shall log a mes          | 1 | 1 | 308 |
| sage to the operations log for Activation of a Plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.1.10.5 The system shall log a message      |   |   | 309 |
|  to the operations log for the Completion of a Plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.5.2 Plan Activation                            |   |   | 214 |
|                                                      |   |   |     |
| This section presents requirements on the execution  |   |   |     |
| of plans. Plans are executed either manually by a    |   |   |     |
| user or automatically by the system in response to   |   |   |     |
| an event.                                            |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2.1 The system shall                        | 1 | 1 | 215 |
| allow a suitably privileged user to activate a plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2.2                                         | 1 | 1 | 216 |
|  The system shall not exceed 3 seconds to notify the |   |   |     |
|  initiating user that a plan could not be activated. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2.3 Upon plan activation t                  | 1 | 1 | 675 |
| he system shall sequentially execute each plan item. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2.4 T                                       |   |   | 782 |
| he system shall support the automatic initiation of  |   |   |     |
| an associated response plan, if any, when detector d |   |   |     |
| ata indicate congested flow or a potential incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2                                          |   |   | 784 |
| .4.1 The system shall support the dynamic creation o |   |   |     |
| f messages for broadcast as part of a response plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.4.                                       |   |   | 785 |
| 2 The system shall include DMS and HAR devices in th |   |   |     |
| e response plan based on distance from the detector. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.4.3 The system shall support a configu   |   |   | 787 |
| ration parameter specifying that an operator is to b |   |   |     |
| e alerted that a response plan has gone into effect. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2                                           |   |   | 786 |
| .5 The system shall support a configuration paramete |   |   |     |
| r specifying whether a response plan requires operat |   |   |     |
| or confirmation before being executed by the system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.5.1 If                                   |   |   | 788 |
| operator confirmation is required for a response pla |   |   |     |
| n the system shall send an alert to the Center respo |   |   |     |
| nsible for the detector that triggered the response. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.5.2 The system shall provide the capa    |   |   | 809 |
| bility for the operator to modify the response plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.5.3 The system                           |   |   | 808 |
| shall display the open congestion event when the ope |   |   |     |
| rator acknowledges a congestion response plan alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.5.2.5.4 The syst                             |   |   | 811 |
| em shall display the open incident event when the op |   |   |     |
| erator acknowledges an incident response plan alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.5.2.5.4.1 The system shall transfer contr   |   |   | 813 |
| ol and video of the nearest camera to the incident t |   |   |     |
| o the operator that acknowledges the incident event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.5.2.6 The system shall al                     |   |   | 866 |
| low a suitably privileged user to deactivate a plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 867 |
| ## 3.5.2.7 Upon plan deactivation the system shall r |   |   |     |
| emove device queue entries associated with the plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.6 Traffic and Roadway Monitoring                |   |   | 217 |
|                                                      |   |   |     |
| Traffic and roadway monitoring includes the          |   |   |     |
| monitoring of traffic speeds and volumes and the     |   |   |     |
| monitoring of roadway weather conditions.            |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.6.1 Detector Data Monitoring                   |   |   | 218 |
|                                                      |   |   |     |
| This section lists requirements for the handling of  |   |   |     |
| detector data. Detector data consists of the data    |   |   |     |
| received from traffic monitoring detectors as well   |   |   |     |
| as the traffic data received from traffic signal     |   |   |     |
| devices.                                             |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.1.1 The system sha                          |   |   | 421 |
| ll provide the capability to display a comparison of |   |   |     |
|  current detector data and historical detector data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.1.1.1 The user shal                        |   |   | 422 |
| l be able to select the time period for the comparis |   |   |     |
| on of current detector and historical detector data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.1.1.2 The user sh                          |   |   | 423 |
| all be able to select the detectors for the comparis |   |   |     |
| on of current detector and historical detector data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.1.2 The system shall have the capa          |   |   | 613 |
| bility to calculate queue length from detector data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.1.2.1                                      |   |   | 615 |
| The system shall support calculating queue length in |   |   |     |
|  real time at the polling frequency of the detector. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.1.3                                         |   |   | 779 |
| The system shall provide the capability to evaluate  |   |   |     |
| detector data for congestion and incident detection. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.1.3.1 The system shall open a congestio    |   |   | 780 |
| n event when detector data indicates congested flow. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 781 |
| ### 3.6.1.3.2 The system shall open an incident even |   |   |     |
| t when detector data indicates a potential incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.1.3.3 The system shall provide the capabil |   |   | 810 |
| ity for the operator to specify a delay period befor |   |   |     |
| e another alert is triggered from the same detector. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              |   |   | 783 |
| .6.1.3.4 The system shall close a system-generated c |   |   |     |
| ongestion event when the evaluation of detector data |   |   |     |
|  indicates that traffic flow is no longer congested. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.1.4 The system                              |   |   | 1   |
| shall provide the capability to evaluate probe data. |   |   | 082 |
+------------------------------------------------------+---+---+-----+
| #### 3.6.1.5 The system shall provide the            |   |   | 1   |
|  capability to evaluate vehicle classification data. |   |   | 083 |
+------------------------------------------------------+---+---+-----+
| ### 3.6.2 Weather Sensor Data Monitoring             |   |   | 219 |
|                                                      |   |   |     |
| This section lists requirements for the handling of  |   |   |     |
| weather sensor data.                                 |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.2.1 The                                     |   |   | 923 |
| system shall support the capability to periodically  |   |   |     |
| retrieve weather sensor data from the SCAN database. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.2.1.                                       |   |   | 1   |
| 1 The system shall archive SCAN weather sensor data. |   |   | 051 |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.                                           |   |   | 926 |
| 2.1.2 The system shall provide the capability to gen |   |   |     |
| erate alerts for poor weather or roadway conditions. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.2.1.3 The system shall provide the c       |   |   | 927 |
| apability to generate a weather sensor response plan |   |   |     |
|  if poor weather or roadway conditions are detected. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.6.2.1.3.1 The system shall suppo            |   |   | 929 |
| rt the dynamic creation of weather condition specifi |   |   |     |
| c messages for broadcast as part of a response plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.2.1.4 The system                           |   |   | 928 |
|  shall support the automatic initiation of an associ |   |   |     |
| ated weather sensor response plan, if any, when sens |   |   |     |
| or data indicate poor weather or roadway conditions. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.6.2.1.4.1                                   |   |   | 930 |
| The system shall support including DMS and HAR messa |   |   |     |
| ges associated with the sensor in the response plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.6.2.1.4                                     |   |   | 931 |
| .2 The system shall support a configuration paramete |   |   |     |
| r specifying that an operator is to be alerted that  |   |   |     |
| a weather sensor response plan has gone into effect. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.2.1.5 The system s                         |   |   | 932 |
| hall support a configuration parameter specifying wh |   |   |     |
| ether a weather sensor response plan requires operat |   |   |     |
| or confirmation before being executed by the system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.6.2.1.5.1 If operat                         |   |   | 933 |
| or confirmation is required for a response plan the  |   |   |     |
| system shall send an alert to the Center responsible |   |   |     |
|  for the weather sensor that triggered the response. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.6.2.1.5.2 The system shall di               |   |   | 934 |
| splay the open weather sensor event when the operato |   |   |     |
| r acknowledges a weather sensor response plan alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.6.2.1.5.                                   |   |   | 935 |
| 2.1 The system shall provide the capability for the  |   |   |     |
| operator to modify the weather sensor response plan. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.6.2.1.5.2                                  |   |   | 936 |
| .2 The system shall provide the capability for the o |   |   |     |
| perator to specify a delay period before another wea |   |   |     |
| ther sensor alert is triggered from the same sensor. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.6.2.2                                         |   |   | 924 |
| The system shall support the capability to retrieve  |   |   |     |
| weather sensor device status from the SCAN database. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.6.2.2.1 The system shall log weather sens    |   |   | 925 |
| or device failure information to the operations log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.7 Activity Management                           |   |   | 220 |
|                                                      |   |   |     |
| One of the primary responsibilities of the CHART II  |   |   |     |
| system is to assist the operators in traffic         |   |   |     |
| management activities and to maintain a record of    |   |   |     |
| system and operator actions associated with these    |   |   |     |
| activities. The repository for this information is   |   |   |     |
| the event log. An event log entry is a collection of |   |   |     |
| system or user generated messages that result from   |   |   |     |
| managing some event (e.g. clearing a disabled        |   |   |     |
| vehicle).                                            |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.7.1 Activity Queues                            |   |   | 221 |
|                                                      |   |   |     |
| This section lists requirements for the management   |   |   |     |
| and control of queues for prioritizing activities.   |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.1 The system sh                           |   |   | 222 |
| all support the queueing of messages to DMS devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.2 The system sh                           |   |   | 223 |
| all support the queueing of messages to HAR devices. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.3 Messages                                |   |   | 224 |
| shall be ordered in a queue based on their priority. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.4 A message entering a devic              |   |   | 225 |
| e queue with a higher priority than the current mess |   |   |     |
| age on the device shall preempt the current message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.5 A message entering a device queue wit   |   |   | 771 |
| h the same priority as the current message shall pre |   |   |     |
| empt the current message if the associated event is  |   |   |     |
| closer to the device than the current message event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.6 A pree                                  |   |   | 226 |
| mpted message shall be returned to the device queue. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.6.1 The system shall log a messag        |   |   | 794 |
| e to the operations log when a message is preempted. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.7 The system shall                        |   |   | 790 |
|  maintain attributes for messages in a device queue. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.7.1 Device queue message attributes sha  |   |   | 791 |
| ll include the event the message is associated with. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.7.2 Device queue message attributes s    |   |   | 792 |
| hall include the Center responsible for the message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.8 Th                                      |   |   | 227 |
| e system shall support the assignment of priorities  |   |   |     |
| to queued messages based on the message type/source. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.1 The system shall support a           |   |   | 228 |
|  message type/source of Incident - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.2 The system shall support             |   |   | 229 |
|  a message type/source of Incident - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.3 The system shall support a           |   |   | 230 |
|  message type/source of Roadwork - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.4 The system shall support a m         |   |   | 231 |
| essage type/source of Congestion - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.5 The system shall support a mess      |   |   | 232 |
| age type/source of Weather Alert - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.6 The system shall support a mess      |   |   | 233 |
| age type/source of Special Event - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 234 |
| ### 3.7.1.8.7 The system shall support a message typ |   |   |     |
| e/source of Recurring Congestion - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.8 The system shall support a           |   |   | 235 |
|  message type/source of Congestion - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.9 The system shall support a me        |   |   | 236 |
| ssage type/source of Weather Alert - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.10 The system shall support a me       |   |   | 237 |
| ssage type/source of Special Event - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 238 |
| #### 3.7.1.8.11 The system shall support a message t |   |   |     |
| ype/source of Recurring Congestion - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.12 The system shall support a messa    |   |   | 239 |
| ge type/source of Safety Message - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.13 The system shall support a mes      |   |   | 240 |
| sage type/source of Safety Message - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.14 The system shall support a mess     |   |   | 241 |
| age type/source of DMS as SHAZAM - Operator Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.1.8.15 The system shall support a me       |   |   | 242 |
| ssage type/source of DMS as SHAZAM - System Control. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.9 The assignment of priorities            |   |   | 243 |
| to event types shall be a system configuration item. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.1.10 A suitably privileged user shall be    |   |   | 244 |
| able to modify the priority of a message in a queue. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.7.2 Events                                     |   |   | 245 |
|                                                      |   |   |     |
| The system provides logging capabilities for         |   |   |     |
| operators to record and share information about      |   |   |     |
| communications, disabled vehicles, required actions, |   |   |     |
| congestion, and incidents. Logs may be system or     |   |   |     |
| operator initiated.                                  |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.2.1 Event Management                        |   |   | 246 |
|                                                      |   |   |     |
| This section presents general requirements related   |   |   |     |
| to the management of events.                         |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.1 The system                           | 1 | 2 | 268 |
| shall store identifying information with each event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.1 The sys                           | 1 | 2 | 269 |
| tem shall store the Date/time with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.1.1.1 The system shall stor          | 1 | 2 | 735 |
| e the system date/time of the creation of the entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.                                     | 1 | 2 | 736 |
| 1.1.2 The system shall store the operator entered da |   |   |     |
| te/time for an entry (defaults to system date/time). |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7                                           | 1 | 2 | 270 |
| .2.1.1.2 The system shall store the source Workstati |   |   |     |
| on Identifier (if applicable) with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.                                    | 1 | 2 | 271 |
| 3 The system shall store a searchable category type  |   |   |     |
| identifying the type of entry with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.                                          | 1 | 2 | 272 |
| 2.1.1.4 The system shall store the User name of init |   |   |     |
| iating user, or the identifier of the initiating app |   |   |     |
| lication if system generated, with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.5 The system shal                   | 1 | 2 | 433 |
| l store the associated Center with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.6 The system shall store the Textua | 1 | 2 | 273 |
| l description of action taken with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.7                                   | 1 | 2 | 466 |
| The system shall store location information identify |   |   |     |
| ing the location of the event with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3                                            | 1 | 2 | 467 |
| .7.2.1.1.7.1 The system shall support capturing even |   |   |     |
| t location information in a descriptive text format. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               |   |   | 468 |
| # 3.7.2.1.1.7.2 The system shall support capturing e |   |   |     |
| vent location information in latitude and longitude. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.1.8                                   | 1 | 2 | 485 |
|  The system shall store an identifier for the source |   |   |     |
|  of notification of the event with each event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3                                              | 1 | 2 | 248 |
| .7.2.1.2 The system shall have the capability to sto |   |   |     |
| re events in the online system for at least 14 days. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.2.1 Open                              | 1 | 2 | 657 |
|  events shall not be removed from the online system. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.2.2 Closed                            | 1 | 2 | 658 |
|  events shall be removed from the online system afte |   |   |     |
| r a system specified time has elapsed since closure. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.3 All event informat                   |   |   | 249 |
| ion shall be retained in a searchable archival form. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.4 The system shall all                 | 1 | 2 | 260 |
| ow a suitably privileged user to create a new event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.4.1 The system                        | 1 | 2 | 659 |
|  shall record the date/time of creation of an event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.5 The system shall allo                | 1 | 2 | 262 |
| w a suitably privileged user to close an open event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.1 The system                        | 1 | 2 | 263 |
|  shall record the date/time of closure for an event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.2 The system shall allow a user     | 1 | 2 | 264 |
|  to append additional information to a closed event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.5.2.1 Information app                | 1 | 2 | 737 |
| ended to a closed event shall be identified as such. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.3 When an event                     |   |   | 265 |
| is closed the system shall remove all messages from  |   |   |     |
| devices and device queues associated with the event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.4 When an event is closed the       |   |   | 463 |
| system shall release all allocated camera resources. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.5 An open event shall be closed onl | 1 | 2 | 437 |
| y by the Center having responsibility for the event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.5.6 The system shall send a           |   |   | 438 |
| message to EORS on closure of an EORS-related event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.6 The system shall support ch          | 1 | 2 | 266 |
| anging an event from one event type to another type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.6.1 The system shall record a message | 1 | 2 | 267 |
|  associated with the event for change of event type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.7 The management of an open event s    | 1 | 2 | 382 |
| hall be under the control of the responsible Center. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.7                                     | 1 | 2 | 383 |
| .1 The system shall support the transfer of responsi |   |   |     |
| bility for an open event from one Center to another. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  | 1 | 2 | 484 |
| ### 3.7.2.1.7.2 The system shall support the capabil |   |   |     |
| ity for more than one user to work on an open event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.8 The current stat                     | 1 | 2 | 525 |
| e of an event in the online system shall be preserve |   |   |     |
| d through a system shutdown/crash and startup cycle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.9 The system shall prov                | 1 | 2 | 434 |
| ide the capability to view stored event information. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.                                        | 1 | 2 | 435 |
| 1.9.1 The system shall provide a search capability a |   |   |     |
| llowing a user to search for a specific event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.9.2 The                               | 1 | 2 | 436 |
|  system shall provide a filtering capability to allo |   |   |     |
| w a user to select a specified set of event entries. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.9.2.1 The filtering ca               | 1 | 2 | 635 |
| pability shall include event state (open or closed). |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.                                     |   |   | 636 |
| 9.2.2 The filtering capability shall include Center. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.1.9.2.                                 |   |   | 637 |
| 3 The filtering capability shall include event type. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.10 Th                                  | 1 | 2 | 558 |
| e system shall provide the capability for the user t |   |   |     |
| o record freeform text comments with an event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.11 The system shall prov               |   |   | 569 |
| ide the capability for the user to select the Notifi |   |   |     |
| cation function from within an event management GUI. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.11.1 The sys                          |   |   | 452 |
| tem shall record individual level notifications asso |   |   |     |
| ciated with an event in the corresponding event log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.1.12 The system shall have the cap       |   |   | 616 |
| ability to generate a reminder alert when an event h |   |   |     |
| as remained open past a system specified time limit. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.12.1 The reminder alert for an ope    |   |   | 617 |
| n event shall be displayed on workstations logged in |   |   |     |
| to the Center that has responsibility for the event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.1.12.2 The system                       |   |   | 618 |
| shall provide the user with the capability to change |   |   |     |
|  the reminder timing from the reminder alert dialog. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 | 1 | 2 | 777 |
| # 3.7.2.1.13 The system shall provide the capability |   |   |     |
|  to associate one or more events with another event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.2.2 Event Types                             |   |   | 595 |
|                                                      |   |   |     |
| This section presents requirements for specific      |   |   |     |
| event types and the information to be recorded for   |   |   |     |
| each type of event.                                  |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.1 The system                           | 1 | 2 | 251 |
|  shall maintain a record of disabled vehicle events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.1.1 The sy                            | 1 | 2 | 577 |
| stem shall record disabled vehicle event attributes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.1 The list of disabled           | 1 | 2 | 585 |
|  vehicle event attributes shall include Tire Change. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.2 The list of disab              | 1 | 2 | 586 |
| led vehicle event attributes shall include Hot Shot. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.3 The list of di                 | 1 | 2 | 587 |
| sabled vehicle event attributes shall include Water. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.4 The list of                    | 1 | 2 | 588 |
| disabled vehicle event attributes shall include Gas. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.5 The list of disable            | 1 | 2 | 589 |
| d vehicle event attributes shall include Directions. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.6 The list of disabled veh       | 1 | 2 | 590 |
| icle event attributes shall include Own Disposition. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.7 The list of disabled vehi      | 1 | 2 | 591 |
| cle event attributes shall include Call for Service. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.8 The list of disabled veh       | 1 | 2 | 592 |
| icle event attributes shall include Gone on Arrival. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.9 The list of disabled ve        | 1 | 2 | 733 |
| hicle event attributes shall include Relay Operator. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.10 The list of disabled vehic    | 1 | 2 | 734 |
| le event attributes shall include Abandoned Vehicle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.1.11 The list of di                | 1 | 2 | 593 |
| sabled vehicle event attributes shall include Other. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.1.2 The s                             | 1 | 2 | 578 |
| ystem shall record the disabled vehicle event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.2.1                                | 1 | 2 | 579 |
| The disabled vehicle event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.2.2 The disabled                   | 1 | 2 | 580 |
|  vehicle event state shall include Units Dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.2.3 The disabl                     | 1 | 2 | 581 |
| ed vehicle event state shall include Units On Scene. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.2.4 The disab                      | 1 | 2 | 582 |
| led vehicle event state shall include Scene Cleared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.1.2.5 Th                             | 1 | 2 | 584 |
| e disabled vehicle event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.1.3 The system shall provi            | 1 | 2 | 594 |
| de the capability to record the identification of th |   |   |     |
| e unit(s) dispatched for the disabled vehicle event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.1.4 The system sha                    | 1 | 2 | 700 |
| ll provide the capability to record the state of iss |   |   |     |
| ue and license plate number of the disabled vehicle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.2                                      | 1 | 2 | 252 |
| The system shall maintain a record of action events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.                                            | 1 | 2 | 564 |
| 7.2.2.2.1 The system shall record action attributes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.2.1.1                                | 1 | 2 | 565 |
|  The list of action attributes shall include Signal. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.2.1.2                                | 1 | 2 | 566 |
|  The list of action attributes shall include Debris. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.2.1.3                                | 1 | 2 | 567 |
| The list of action attributes shall include Utility. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.2.1.                                 | 1 | 2 | 568 |
| 4 The list of action attributes shall include Other. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3                                             | 1 | 2 | 570 |
| .7.2.2.2.2 The system shall record the action state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               | 1 | 2 | 571 |
| # 3.7.2.2.2.2.1 The action state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.2.                                   | 1 | 2 | 572 |
| 2.2 The action state shall include Units Dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.                                     | 1 | 2 | 573 |
| 2.2.3 The action state shall include Units On Scene. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2                                      | 1 | 2 | 574 |
| .2.2.4 The action state shall include Scene Cleared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2                                      | 1 | 2 | 575 |
| .2.2.5 The action state shall include Delay Cleared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #######                                              | 1 | 2 | 576 |
| 3.7.2.2.2.2.6 The action state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.3 Th                                   | 1 | 2 | 253 |
| e system shall maintain a record of incident events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.                                          | 1 | 2 | 424 |
| 2.2.3.1 The system shall record incident attributes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.1 The list of in                 | 1 | 2 | 533 |
| cident attributes shall include Disabled in Roadway. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.2 The list o                     | 1 | 2 | 534 |
| f incident attributes shall include Personal Injury. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.3 The list o                     | 1 | 2 | 535 |
| f incident attributes shall include Property Damage. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.4 The                            | 1 | 2 | 536 |
|  list of incident attributes shall include Fatality. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.5 The list of                    | 1 | 2 | 537 |
| incident attributes shall include Debris in Roadway. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.6 The                            | 1 | 2 | 538 |
|  list of incident attributes shall include Roadwork. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.7 The lis                        | 1 | 2 | 539 |
| t of incident attributes shall include Vehicle Fire. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.8 The li                         | 1 | 2 | 540 |
| st of incident attributes shall include Maintenance. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.9 The li                         | 1 | 2 | 541 |
| st of incident attributes shall include Signal Call. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.10 The list o                    | 1 | 2 | 542 |
| f incident attributes shall include Police Activity. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.11 The list of                   | 1 | 2 | 543 |
| incident attributes shall include Off Road Activity. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.12 The list of inciden           | 1 | 2 | 544 |
| t attributes shall include Declaration of Emergency. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.13 Th                            | 1 | 2 | 545 |
| e list of incident attributes shall include Weather. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.1.14                               | 1 | 2 | 546 |
| The list of incident attributes shall include Other. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7                                           | 1 | 2 | 526 |
| .2.2.3.2 The system shall record the incident state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #######                                              | 1 | 2 | 527 |
| 3.7.2.2.3.2.1 The incident state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.2.                                 | 1 | 2 | 528 |
| 2 The incident state shall include Units Dispatched. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.                                   | 1 | 2 | 529 |
| 2.3 The incident state shall include Units On Scene. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3                                    | 1 | 2 | 530 |
| .2.4 The incident state shall include Scene Cleared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3                                    | 1 | 2 | 531 |
| .2.5 The incident state shall include Delay Cleared. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.                                           | 1 | 2 | 532 |
| 7.2.2.3.2.6 The incident state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.3 The system shall r                | 1 | 2 | 547 |
| ecord which agencies are involved with the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.1 The system shall re            | 1 | 2 | 548 |
| cord whether an agency was notified of the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.2 The system shall               | 1 | 2 | 549 |
|  record whether an agency responded to the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.3 The list of agencies in        | 1 | 2 | 550 |
| volved with an incident shall include CHART Vehicle. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.4 The list of agencie            | 1 | 2 | 551 |
| s involved with an incident shall include Fireboard. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.5 The list of agencies i         | 1 | 2 | 552 |
| nvolved with an incident shall include Local Police. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.6 The list of a                  | 1 | 2 | 553 |
| gencies involved with an incident shall include MDE. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.7 The list of agencies involve   | 1 | 2 | 554 |
| d with an incident shall include MDTA - Maintenance. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.8 The list of agencies involv    | 1 | 2 | 555 |
| ed with an incident shall include SHA - Maintenance. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.9 The list of agencies i         | 1 | 2 | 556 |
| nvolved with an incident shall include State Police. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.3.10 The list of agencies          | 1 | 2 | 557 |
| involved with an incident shall include MDTA Police. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.4 The system shall record whe       | 1 | 2 | 489 |
| ther HAZMAT materials were involved in the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.5 The system shall record           | 1 | 2 | 490 |
|  whether traffic lanes were closed for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.5.1 The                            | 1 | 2 | 491 |
|  system shall record the date/time a lane is closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.5.2 The                            | 1 | 2 | 492 |
|  system shall record the date/time a lane is opened. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2                                         |   |   | 493 |
| .2.3.6 The system shall provide the capability to di |   |   |     |
| splay a roadway graphic for an incident event entry. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.6.1 The roadway graph              |   |   | 494 |
| ic shall support displaying the status of each lane. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.                                       |   |   | 495 |
| 2.3.6.2 The system shall provide the capability for  |   |   |     |
| the user to make annotations on the roadway graphic. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.6.3 The system shall provide the   |   |   | 519 |
| capability for the user to click on areas of the roa |   |   |     |
| dway graphic in order to change the state of a lane. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.7 The                               | 1 | 2 | 497 |
|  system shall record the types of vehicles involved. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.7.1 T                              | 1 | 2 | 498 |
| he system shall record if a vehicle was jack-knifed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3                                    | 1 | 2 | 499 |
| .7.2 The system shall record if a vehicle lost load. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.7.3                                | 1 | 2 | 500 |
| The system shall record if a vehicle was overturned. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.8 The system shal                   | 1 | 2 | 520 |
| l record the type of special needs for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.8.1 The list of                    | 1 | 2 | 521 |
|  special needs for an incident shall include HAZMAT. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.8.2 The list of                    | 1 | 2 | 522 |
| special needs for an incident shall include Medivac. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.8.3 The list of specia             | 1 | 2 | 523 |
| l needs for an incident shall include Investigation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.8.4 The list of special ne         | 1 | 2 | 524 |
| eds for an incident shall include Signal Operations. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.8.5 The syst                       | 1 | 2 | 501 |
| em shall include the special needs section from SHA  |   |   |     |
| Incident Report Form SHA.52.4-1 in the incident log. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.9 The system shall record           | 1 | 2 | 502 |
|  the weather conditions at the time of the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.10 The system shall                 | 1 | 2 | 503 |
| record the types of resources used for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    | 1 | 2 | 504 |
| ###### 3.7.2.2.3.10.1 The system shall record the nu |   |   |     |
| mber of each type of resource used for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.                                | 1 | 2 | 505 |
| 2 The system shall record the date/time of notificat |   |   |     |
| ion of need for each resource used for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3                                    | 1 | 2 | 506 |
| .10.3 The system shall record the date/time of arriv |   |   |     |
| al on scene for each resource used for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.                                | 1 | 2 | 507 |
| 4 The system shall record the date/time of departure |   |   |     |
|  from scene for each resource used for the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.5 The list of resource          | 1 | 2 | 508 |
| s for use for an incident shall include Arrow Board. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.6 The list of resourc           | 1 | 2 | 509 |
| es for use for an incident shall include Dump Truck. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.7 The list of                   | 1 | 2 | 510 |
| resources for use for an incident shall include ERU. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.8 The list of reso              | 1 | 2 | 511 |
| urces for use for an incident shall include ETP/VRT. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.9 The list of resource          | 1 | 2 | 512 |
| s for use for an incident shall include Light Plant. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.10 The list of res              | 1 | 2 | 513 |
| ources for use for an incident shall include Loader. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.11 The list of resources        | 1 | 2 | 514 |
|  for use for an incident shall include Portable DMS. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.12 The list of resourc          | 1 | 2 | 515 |
| es for use for an incident shall include Sand Truck. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.13 The list of reso             | 1 | 2 | 516 |
| urces for use for an incident shall include Sweeper. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.14 The list of r                | 1 | 2 | 517 |
| esources for use for an incident shall include FITM. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.10.15 The list of re               | 1 | 2 | 518 |
| sources for use for an incident shall include Other. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.11 The system shall                 | 1 | 2 | 439 |
|  record the date/time that traffic flow is restored. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.3.12 The system shall pr              |   |   | 608 |
| ovide the capability to record traffic queue length. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.12.1 The system sha                |   |   | 609 |
| ll support the manual entering of queue length data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.12.2 The system shall s            |   |   | 610 |
| upport the automatic recording of queue length data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.12.3 The                           |   |   | 611 |
| system shall support recording of queue length data  |   |   |     |
| in the direction of the roadway having the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.3.12.4 The system sh                 |   |   | 612 |
| all support recording of queue length data in the op |   |   |     |
| posite direction of the roadway having the incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               |   |   | 614 |
| # 3.7.2.2.3.12.5 The system shall support an updatin |   |   |     |
| g display of queue length data for an open incident. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.4 The system shall m                   | 1 | 2 | 254 |
| aintain a record of non-recurring congestion events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.4.1 The system sh                     | 1 | 2 | 638 |
| all record the non-recurring congestion event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.4.1.1 The non-                       | 1 | 2 | 639 |
| recurring congestion event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.4.1.2 The non-re                     | 1 | 2 | 640 |
| curring congestion event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.5 The system sha                       | 1 | 2 | 255 |
| ll maintain a record of recurring congestion events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.5.1 The syste                         | 1 | 2 | 641 |
| m shall record the recurring congestion event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.5.1.1 The                            | 1 | 2 | 642 |
| recurring congestion event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.5.1.2 The re                         | 1 | 2 | 643 |
| curring congestion event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.6 The system shall maintain a reco     | 1 | 2 | 256 |
| rd of National Weather Service weather alert events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.6.1 Th                                | 1 | 2 | 644 |
| e system shall record the weather alert event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.6.1                                  | 1 | 2 | 645 |
| .1 The weather alert event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.6.1.2                                | 1 | 2 | 646 |
|  The weather alert event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.7 The system sha                       | 1 | 2 | 257 |
| ll maintain a record of weather sensor alert events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.7.1 The syste                         | 1 | 2 | 647 |
| m shall record the weather sensor alert event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.7.1.1 The                            | 1 | 2 | 648 |
| weather sensor alert event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.7.1.2 The we                         | 1 | 2 | 649 |
| ather sensor alert event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.8 T                                    | 1 | 2 | 258 |
| he system shall maintain a record of special events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.                                      | 1 | 2 | 650 |
| 8.1 The system shall record the special event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.8.1.1 The                            | 1 | 2 | 651 |
|  special event alert event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.8.1.2 The s                          | 1 | 2 | 652 |
| pecial event alert event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2.9 The syst                             | 1 | 2 | 259 |
| em shall maintain a record of safety message events. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.9.1 The                               | 1 | 2 | 653 |
|  system shall record the safety message event state. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.9.1.                                 | 1 | 2 | 654 |
| 1 The safety message event state shall include Open. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####### 3.7.2.2.9.1.2                                | 1 | 2 | 655 |
| The safety message event state shall include Closed. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.2                                        |   |   | 863 |
| .10 The system shall provide the capability for a us |   |   |     |
| er to send a manual alert from within an open event. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.2.10.1 The system shall provide         |   |   | 864 |
|  the user with a list of event types to select from. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ######                                               |   |   | 865 |
|  3.7.2.2.10.2 The system shall provide the user with |   |   |     |
|  the option of entering text to accompany the alert. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.7.2.3 General Event Messages                  |   |   | 596 |
|                                                      |   |   |     |
| The display of messages on DMSs, the broadcast of    |   |   |     |
| messages from HARs, and the activation of plans are  |   |   |     |
| all actions associated with the response to an       |   |   |     |
| event. All such actions are recorded in the          |   |   |     |
| appropriate event log.                               |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.3.1 The system shal                      | 1 | 2 | 290 |
| l log event messages associated with DMS activities. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.1.1 The system shall log a m          | 1 | 2 | 291 |
| essage associated with an event for Set DMS message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.1.2 The system shall log a mes        | 1 | 2 | 292 |
| sage associated with an event for Blank DMS display. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.3.2 The system shal                      | 1 | 2 | 294 |
| l log event messages associated with HAR activities. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.2.1 The system shall log a m          | 1 | 2 | 295 |
| essage associated with an event for Set HAR message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.2.2 The system shall log a message    | 1 | 2 | 296 |
| associated with an event for inactivate HAR message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.7.2.3.3 The system shall                     | 1 | 2 | 486 |
|  log event messages associated with plan activities. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.3.1 The system shall log a m          | 1 | 2 | 487 |
| essage associated with an event for plan activation. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.7.2.3.3.2 The system shall log a m          | 1 | 2 | 488 |
| essage associated with an event for plan completion. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.8 Web                                           |   |   | 971 |
|                                                      |   |   |     |
| This section contains requirements for the           |   |   |     |
| distribution of SHA information through the Web.     |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.8.1 The system sha                             |   |   | 980 |
| ll support the display of data through a WWW server. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ####                                                 |   |   | 1   |
|  3.8.1.1 The system shall provide public WWW access. |   |   | 054 |
+------------------------------------------------------+---+---+-----+
| #### 3                                               |   |   | 1   |
| .8.1.2 The system shall provide intranet WWW access. |   |   | 055 |
+------------------------------------------------------+---+---+-----+
| #### 3.8.1.3 The system s                            |   |   | 981 |
| hall provide access to video through the WWW server. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.8.1.4 T                                       |   |   | 985 |
| he system shall provide the capability to view a res |   |   |     |
| tricted set of incident data through the WWW server. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 1   |
| ### 3.8.1.5 The system shall provide the capability  |   |   | 052 |
| to view EORS Operations data through the WWW server. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.8.1.6 The system shall provide                |   |   | 1   |
|  the capability to view maps through the WWW server. |   |   | 053 |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.1 The system shall                     |   |   | 1   |
|  provide a zoom and pan capability for viewing maps. |   |   | 060 |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.2 The                                  |   |   | 1   |
|  web map interface shall display a highway base map. |   |   | 058 |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.3 The web                              |   |   | 984 |
| map interface shall display road segment speed data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.4 The web                              |   |   | 987 |
|  map interface shall display EORS road closure data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.5 The web map                          |   |   | 1   |
|  interface shall display snow emergency plan status. |   |   | 061 |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.6 The web map                          |   |   | 1   |
| display shall show device locations using map icons. |   |   | 056 |
+------------------------------------------------------+---+---+-----+
| ###### 3.8.1.6.6.1 Clicking on a                     |   |   | 1   |
| device icon shall display device detail information. |   |   | 059 |
+------------------------------------------------------+---+---+-----+
| ###### 3.8.1.6.6.2 Clicking                          |   |   | 983 |
| on a DMS icon shall display the current DMS message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.8.1.6.6.3 Clicking on a HAR icon shall prov |   |   | 982 |
| ide the capability to listen to current HAR message. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###### 3.8.1.6.                                      |   |   | 986 |
| 6.4 Clicking on a pavement sensor shall provide the  |   |   |     |
| capability to view the current pavement sensor data. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.8.1.6.7 The map view shall be printable.     |   |   | 1   |
|                                                      |   |   | 057 |
+------------------------------------------------------+---+---+-----+
| #                                                    |   |   | 990 |
| ### 3.8.1.7 Content provided through the WWW server  |   |   |     |
| shall be viewable using Microsoft Internet Explorer. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.8.1.8 Content provided thro                   |   |   | 991 |
| ugh the WWW server shall be viewable using Netscape. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ###                                                  |   |   | 988 |
|  3.8.2 The system administrator shall have control o |   |   |     |
| ver which data are available through the WWW server. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.8.                                             |   |   | 989 |
| 3 Dynamic information available through the WWW serv |   |   |     |
| er shall be updated at least once every two minutes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.9 System Maintainability and Availability       |   |   | 764 |
|                                                      |   |   |     |
| The overall CHART II system must provide 24          |   |   |     |
| hours/day 7 days/week operations with no single      |   |   |     |
| point of failure. This section presents requirements |   |   |     |
| for the reliability, maintainability, and            |   |   |     |
| availability of the system.                          |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.9.1 Maintainability                            |   |   | 766 |
|                                                      |   |   |     |
| This section lists system maintainability            |   |   |     |
| requirements.                                        |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.1.1 The system administrator sha            |   |   | 769 |
| ll be able to perform remote software installations. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.1.2 The system administrator shall be a     |   |   | 970 |
| ble to start and stop remote CHART system processes. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.1                                           |   |   | 992 |
| .3 The system shall support the capability to backup |   |   |     |
|  operational data files while the system is running. |   |   |     |
+------------------------------------------------------+---+---+-----+
| ##### 3.9.1.3.1 The system shall                     |   |   | 993 |
| support the remote backup of operational data files. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.1.4 An system                               |   |   | 1   |
|  operations and maintenance guide shall be provided. |   |   | 063 |
+------------------------------------------------------+---+---+-----+
| ##                                                   |   |   | 1   |
| ## 3.9.1.5 A system user\'s guide shall be provided. |   |   | 064 |
+------------------------------------------------------+---+---+-----+
| ### 3.9.2 Availability                               |   |   | 767 |
|                                                      |   |   |     |
| This section lists system availability requirements. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.2.1 The CHART II system at the SO           |   |   | 768 |
| C shall support operations 24 hours/day 7 days/week. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.2.2 The CHART II system shall s             |   |   | 770 |
| upport a failover capability whereby operations at o |   |   |     |
| ne location can be transferred to a second location. |   |   |     |
+------------------------------------------------------+---+---+-----+
| #### 3.9.2.3 The C                                   |   |   | 1   |
| HART II system shall support distributed operations. |   |   | 084 |
+------------------------------------------------------+---+---+-----+
| ##### 3.9.2.3.1 The CHART II                         |   |   | 1   |
| system shall include multiple locations capable of p |   |   | 085 |
| erforming all CHART functions (excluding archiving). |   |   |     |
+------------------------------------------------------+---+---+-----+
| ## 3.10 Simulation                                   |   |   | 1   |
|                                                      |   |   | 041 |
| This section presents system requirements for the    |   |   |     |
| support of simulation tools. The University of       |   |   |     |
| Maryland has responsibility for the development of   |   |   |     |
| simulation tools for use in the CHART II system. The |   |   |     |
| CHART II system will provide the input to the        |   |   |     |
| simulation tools and receive the simulation results  |   |   |     |
| for display to CHART users.                          |   |   |     |
+------------------------------------------------------+---+---+-----+
| ### 3.10.1 The system sh                             |   |   | 1   |
| all provide monitoring data to the simulation tools. |   |   | 044 |
+------------------------------------------------------+---+---+-----+
| #### 3.10.1.1 The data provided                      |   |   | 1   |
| to the simulation tools shall include detector data. |   |   | 046 |
+------------------------------------------------------+---+---+-----+
| #### 3.10.1.2 The data provided to the               |   |   | 1   |
|  simulation tools shall include traffic signal data. |   |   | 047 |
+------------------------------------------------------+---+---+-----+
| #### 3.10.1.3 The data provid                        |   |   | 1   |
| ed to the simulation tools shall include event data. |   |   | 048 |
+------------------------------------------------------+---+---+-----+
| ### 3.10.2 The system shall provid                   |   |   | 1   |
| e real-time monitoring data to the simulation tools. |   |   | 045 |
+------------------------------------------------------+---+---+-----+
| ### 3.10.3 The system shall provi                    |   |   | 1   |
| de archived monitoring data to the simulation tools. |   |   | 043 |
+------------------------------------------------------+---+---+-----+
| ### 3.10.4 The system shall provide the capability   |   |   | 1   |
| to display the simulation results to the CHART user. |   |   | 049 |
+------------------------------------------------------+---+---+-----+

# Appendix A - Initial R1B1 to CHART II Requirements Matrix

This appendix contains a table showing the initial R1B1 requirements and
a mapping to the corresponding CHART II System Requirement(s). Shaded
requirements indicate those R1B1 requirements that have not been
superceded by an allocated CHART System requirement and remain in effect
for this release.

+---+------------------------------------------------+-----------------+
| R | **Release 1 Build 1 Requirement**              | Chart II        |
| 1 |                                                | Requirement     |
| B |                                                |                 |
| 1 |                                                |                 |
| I |                                                |                 |
| D |                                                |                 |
+===+================================================+=================+
| 2 | # 3 Requirements                               |                 |
| 3 |                                                |                 |
| 7 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 2 | ## 3.1 Users/Security                          |                 |
| 4 |                                                |                 |
| 0 | The system will rely on underlying network,    |                 |
|   | operating system and physical access controls  |                 |
|   | for basic security. Release 1 Build 1          |                 |
|   | applications will provide only application     |                 |
|   | level security aimed at controlling which      |                 |
|   | functions an operator may perform based on     |                 |
|   | his/her login id and access level assignments. |                 |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.1.1 The system shall provide a mechanism | CHART-7         |
| 4 |  to define and enforce two user access levels. |                 |
| 2 |                                                | The system      |
|   |                                                | shall provide a |
|   |                                                | mechanism to    |
|   |                                                | define and      |
|   |                                                | enforce user    |
|   |                                                | functional      |
|   |                                                | rights.         |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.1.1.1 The ad                            | CHART-8         |
| 6 | ministrator shall be the highest access level. |                 |
| 3 |                                                | There shall be  |
|   |                                                | at least one    |
|   |                                                | user of the     |
|   |                                                | system, with    |
|   |                                                | the role of     |
|   |                                                | administrator,  |
|   |                                                | who shall have  |
|   |                                                | full system     |
|   |                                                | functional      |
|   |                                                | rights.         |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.1.1.2 The administrator sha             | CHART-8         |
| 4 | ll have full system capabilities. An administr |                 |
| 3 | ator has a greater privilege level than an ope | There shall be  |
|   | rator and as such is allowed to perform all ac | at least one    |
|   | tions an operator may perform plus all actions | user of the     |
|   |  that explicitly require administrator access. | system, with    |
|   |                                                | the role of     |
|   |                                                | administrator,  |
|   |                                                | who shall have  |
|   |                                                | full system     |
|   |                                                | functional      |
|   |                                                | rights.         |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.1.1.3                                   | CHART-9         |
| 6 | The operator shall be the lowest access level. |                 |
| 4 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the assignment  |
|   |                                                | of roles to     |
|   |                                                | users.          |
+---+------------------------------------------------+-----------------+
| 2 | #                                              | CHART-10        |
| 4 | ## 3.1.2 The system shall require a user to pr |                 |
| 5 | ovide a userid and password in order to login. | The system      |
|   |                                                | shall require a |
|   |                                                | user to provide |
|   |                                                | a userid and    |
|   |                                                | password in     |
|   |                                                | order to login. |
+---+------------------------------------------------+-----------------+
| 2 | ###                                            | CHART-11        |
| 4 | 3.1.3 The system shall allow a user to logoff. |                 |
| 6 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | user to logoff. |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.1.4 The system shall allow               | CHART-12        |
| 4 | an administrator to create a new user account. |                 |
| 7 |                                                | The system      |
|   |                                                | shall allow an  |
|   |                                                | administrator   |
|   |                                                | to create a new |
|   |                                                | user account.   |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.1.5 The system shall al                  | CHART-13        |
| 4 | low an administrator to delete a user account. |                 |
| 8 |                                                | The system      |
|   |                                                | shall allow an  |
|   |                                                | administrator   |
|   |                                                | to delete a     |
|   |                                                | user account.   |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.1.6 The system shall allow an adminis    | CHART-9         |
| 4 | trator to modify the access of a user account. |                 |
| 9 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the assignment  |
|   |                                                | of roles to     |
|   |                                                | users.          |
|   |                                                |                 |
|   |                                                | CHART-14        |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall allow an  |
|   |                                                | administrator   |
|   |                                                | to modify the   |
|   |                                                | functional      |
|   |                                                | rights of a     |
|   |                                                | role.           |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.1.7 The system shall ass                 | CHART-15        |
| 6 | ign an operations center to a user upon login. |                 |
| 5 |                                                | The system      |
|   |                                                | shall assign an |
|   |                                                | operations      |
|   |                                                | center to a     |
|   |                                                | user upon       |
|   |                                                | login.          |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.1.7.1 The assigned operat               | CHART-16        |
| 6 | ions center shall be the logical site of the w |                 |
| 6 | orkstation where the user logged into the GUI. | The assigned    |
|   |                                                | operations      |
|   |                                                | center shall be |
|   |                                                | the logical     |
|   |                                                | site of the     |
|   |                                                | workstation     |
|   |                                                | where the user  |
|   |                                                | logged into the |
|   |                                                | GUI.            |
+---+------------------------------------------------+-----------------+
| 6 | ### 3.1.                                       | CHART-402       |
| 6 | 8 The system shall not allow the last user at  |                 |
| 2 | an operations center to logoff while that oper | The system      |
|   | ations center is responsible for DMS messages. | shall not allow |
|   |                                                | the last user   |
|   |                                                | logged in to a  |
|   |                                                | Center to       |
|   |                                                | logoff while    |
|   |                                                | that Center has |
|   |                                                | control of      |
|   |                                                | resources.      |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.1.8.1 The system                        | CHART-17        |
| 7 |  shall detect if no users are logged in at the |                 |
| 3 |  control center that is listed as the responsi | The system      |
|   | ble control center for a DMS and shall generat | shall not allow |
|   | e an alert to a logged-in administrator or ope | the last user   |
|   | rator at the SOC if the condition is detected. | logged in to a  |
|   |                                                | Center to       |
|   |                                                | logoff while    |
|   |                                                | that Center has |
|   |                                                | an open event   |
|   |                                                | assigned to it. |
+---+------------------------------------------------+-----------------+
| 6 | ##                                             | CHART-18        |
| 6 | # 3.1.9 The system shall provide a change user |                 |
| 3 |  dialog that allows a new user to logon and an | The system      |
|   |  old user to logoff. This will alleviate the n | shall provide a |
|   | eed for the last user at an op center to tempo | change user     |
|   | rarily transfer responsibility for DMS message | dialog that     |
|   | s so the operator may log off at shift change. | allows a new    |
|   |                                                | user to logon   |
|   |                                                | and an old user |
|   |                                                | to logoff at    |
|   |                                                | the same Center |
|   |                                                | in a single     |
|   |                                                | operation.      |
+---+------------------------------------------------+-----------------+
| 2 | ## 3.2 DMS Control                             |                 |
| 5 |                                                |                 |
| 0 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.1 The system                           | CHART-60        |
| 5 |  shall allow an operator to set the current me |                 |
| 2 | ssage for a selected DMS that is the responsib | The system      |
|   | ility of the operator\'s operations center or  | shall allow a   |
|   | does not have a responsible operations center. | suitably        |
|   |                                                | privileged user |
|   |                                                | to set the      |
|   |                                                | current message |
|   |                                                | for a selected  |
|   |                                                | DMS.            |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.1.1 The                               | CHART-61        |
| 6 | system shall allow an operator to specify the  |                 |
| 7 | beacons on the selected DMS, if it has beacons | The system      |
|   | , should be turned on when the message is set. | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to specify the  |
|   |                                                | beacon state on |
|   |                                                | the selected    |
|   |                                                | DMS, if it has  |
|   |                                                | beacons.        |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.2 The system shall al                  | CHART-62        |
| 6 | low an operator to set the current message for |                 |
| 8 |  a selected group of DMSs that are the respons | The system      |
|   | ibility of the operator\'s operations center o | shall allow a   |
|   | r do not have a responsible operations center. | suitably        |
|   |                                                | privileged user |
|   |                                                | to set the      |
|   |                                                | current message |
|   |                                                | for a selected  |
|   |                                                | group of DMSs.  |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.2.1 The system shall allow the op     | CHART-61        |
| 6 | erator to specify the beacons, for all signs i |                 |
| 9 | n the selected group of DMSs that have beacons | The system      |
|   | , should be turned on when the message is set. | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to specify the  |
|   |                                                | beacon state on |
|   |                                                | the selected    |
|   |                                                | DMS, if it has  |
|   |                                                | beacons.        |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.3                                      | CHART-64        |
| 5 | The system shall allow an operator to blank th |                 |
| 3 | e display of a selected DMS that is the respon | The system      |
|   | sibility of the operator\'s operations center. | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to blank the    |
|   |                                                | display of a    |
|   |                                                | selected DMS.   |
+---+------------------------------------------------+-----------------+
| 4 | ##                                             | CHART-65        |
| 7 | ## 3.2.3.1 If the beacons of a DMS are on when |                 |
| 0 |  the DMS is blanked, they shall be turned off. | If the beacons  |
|   |                                                | of a DMS are on |
|   |                                                | when the DMS is |
|   |                                                | blanked, they   |
|   |                                                | shall be turned |
|   |                                                | off.            |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.4 The system                           | CHART-66        |
| 7 | shall allow an operator to blank the display o |                 |
| 1 | f a selected group of DMSs that are the respon | The system      |
|   | sibility of the operator\'s operations center. | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to blank the    |
|   |                                                | display of a    |
|   |                                                | selected group  |
|   |                                                | of DMSs.        |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.4.1 If the beac                       | CHART-65        |
| 7 | ons of a DMS in the selected group are on when |                 |
| 2 |  the DMS is blanked, they shall be turned off. | If the beacons  |
|   |                                                | of a DMS are on |
|   |                                                | when the DMS is |
|   |                                                | blanked, they   |
|   |                                                | shall be turned |
|   |                                                | off.            |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.5 The sys                              | CHART-68        |
| 5 | tem shall allow an operator to reset the contr |                 |
| 4 | oller for a selected DMS that is the responsib | The system      |
|   | ility of the operator\'s operations center or  | shall allow a   |
|   | does not have a responsible operations center. | suitably        |
|   |                                                | privileged user |
|   |                                                | to reset the    |
|   |                                                | controller for  |
|   |                                                | a selected DMS. |
+---+------------------------------------------------+-----------------+
| 4 | ####                                           | CHART-69        |
| 7 | 3.2.5.1 The system shall blank the display of  |                 |
| 3 | the selected DMS when the controller is reset. | The system      |
|   |                                                | shall blank the |
|   |                                                | display of the  |
|   |                                                | selected DMS    |
|   |                                                | when the        |
|   |                                                | controller is   |
|   |                                                | reset.          |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.5.2                                   | CHART-70        |
| 7 |  If the DMS has beacons, the system shall turn |                 |
| 4 |  the beacons off when the controller is reset. | If the DMS has  |
|   |                                                | beacons, the    |
|   |                                                | system shall    |
|   |                                                | turn the        |
|   |                                                | beacons off     |
|   |                                                | when the        |
|   |                                                | controller is   |
|   |                                                | reset.          |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.6 T                                    | CHART-71        |
| 7 | he system shall allow an administrator to rese |                 |
| 5 | t the controller for a selected group of DMSs. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to reset the    |
|   |                                                | controller for  |
|   |                                                | a selected      |
|   |                                                | group of DMSs.  |
+---+------------------------------------------------+-----------------+
| 4 | #### 3                                         | CHART-69        |
| 7 | .2.6.1 The system shall blank the display of a |                 |
| 6 | ll selected DMSs when the controller is reset. | The system      |
|   |                                                | shall blank the |
|   |                                                | display of the  |
|   |                                                | selected DMS    |
|   |                                                | when the        |
|   |                                                | controller is   |
|   |                                                | reset.          |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.6.2 If a s                            | CHART-70        |
| 7 | elected DMS has beacons, the system shall turn |                 |
| 7 |  the beacons off when the controller is reset. | If the DMS has  |
|   |                                                | beacons, the    |
|   |                                                | system shall    |
|   |                                                | turn the        |
|   |                                                | beacons off     |
|   |                                                | when the        |
|   |                                                | controller is   |
|   |                                                | reset.          |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.7 The system shall allow an oper       | CHART-33        |
| 5 | ator to force a status poll of a selected DMS. |                 |
| 6 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to force a      |
|   |                                                | status poll of  |
|   |                                                | a selected      |
|   |                                                | pollable        |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 4 | ###                                            | CHART-34        |
| 8 | 3.2.8 The system shall allow an operator to fo |                 |
| 1 | rce a status poll of a selected group of DMSs. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to force a      |
|   |                                                | status poll of  |
|   |                                                | a selected      |
|   |                                                | group of        |
|   |                                                | pollable        |
|   |                                                | devices.        |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.9 The system shall allow an admin      | CHART-44        |
| 5 | istrator to change the name of a selected DMS. |                 |
| 7 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to change the   |
|   |                                                | name of a       |
|   |                                                | selected        |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2                                        | CHART-35        |
| 5 | .10 The system shall allow an administrator to |                 |
| 8 |  alter the polling interval of a selected DMS. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to alter the    |
|   |                                                | polling         |
|   |                                                | interval of a   |
|   |                                                | selected        |
|   |                                                | pollable        |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.10.1 T                                | CHART-36        |
| 8 | he minimum polling interval shall be 1 minute. |                 |
| 2 |                                                | The minimum     |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 1 minute.    |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.10.2 T                                | CHART-37        |
| 8 | he maximum polling interval shall be 24 hours. |                 |
| 3 |                                                | The maximum     |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 24 hours.    |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.10.3 The minimum incre                | CHART-38        |
| 8 | ment for a polling interval shall be 1 minute. |                 |
| 4 |                                                | The minimum     |
|   |                                                | increment for a |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 1 minute.    |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.11                                     | CHART-82        |
| 8 | The system shall provide an application progra |                 |
| 5 | m interface (API) to implement DMS functionali | The system      |
|   | ty specified in the NTCIP standard NEMA TS3.6. | shall provide   |
|   |                                                | an application  |
|   |                                                | program         |
|   |                                                | interface (API) |
|   |                                                | to implement    |
|   |                                                | DMS             |
|   |                                                | functionality   |
|   |                                                | specified in    |
|   |                                                | the NTCIP       |
|   |                                                | standard NEMA   |
|   |                                                | TS3.6.          |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.                                         | CHART-75        |
| 5 | 2.12 The system shall support the Mark IV FP95 |                 |
| 9 | 00 \"Maryland\" DMS protocol. (Actual protocol | The system      |
|   |  support is carried out by the FMS subsystem.) | shall support   |
|   |                                                | the Mark IV     |
|   |                                                | FP9500          |
|   |                                                | \"Maryland\"    |
|   |                                                | DMS protocol.   |
|   |                                                | (Actual         |
|   |                                                | protocol        |
|   |                                                | support is      |
|   |                                                | carried out by  |
|   |                                                | the FMS         |
|   |                                                | subsystem.)     |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.13 The system shall support the        | CHART-76        |
| 8 |  Mark IV FP2001 DMS protocol. (Actual protocol |                 |
| 6 |  support is carried out by the FMS subsystem.) | The system      |
|   |                                                | shall support   |
|   |                                                | the Mark IV     |
|   |                                                | FP2001 DMS      |
|   |                                                | protocol.       |
|   |                                                | (Actual         |
|   |                                                | protocol        |
|   |                                                | support is      |
|   |                                                | carried out by  |
|   |                                                | the FMS         |
|   |                                                | subsystem.)     |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.14 The system shall support the        | CHART-77        |
| 8 |  Mark IV FP1001 DMS protocol. (Actual protocol |                 |
| 7 |  support is carried out by the FMS subsystem.) | The system      |
|   |                                                | shall support   |
|   |                                                | the Mark IV     |
|   |                                                | FP1001 DMS      |
|   |                                                | protocol.       |
|   |                                                | (Actual         |
|   |                                                | protocol        |
|   |                                                | support is      |
|   |                                                | carried out by  |
|   |                                                | the FMS         |
|   |                                                | subsystem.)     |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.15 The system shall suppo              | CHART-78        |
| 8 | rt the Telespot DMS protocol. (Actual protocol |                 |
| 8 |  support is carried out by the FMS subsystem.) | The system      |
|   |                                                | shall support   |
|   |                                                | the Telespot    |
|   |                                                | DMS protocol.   |
|   |                                                | (Actual         |
|   |                                                | protocol        |
|   |                                                | support is      |
|   |                                                | carried out by  |
|   |                                                | the FMS         |
|   |                                                | subsystem.)     |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.16 The system s                        | CHART-792       |
| 6 | hall provide a mechanism to establish and main |                 |
| 4 | tain a responsible operations center of a DMS. | Device queue    |
|   |                                                | message         |
|   |                                                | attributes      |
|   |                                                | shall include   |
|   |                                                | the Center      |
|   |                                                | responsible for |
|   |                                                | the message.    |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.2.16.1 The system sh                    | CHART-382       |
| 6 | all designate the operations center where the  |                 |
| 5 | operator is logged in as the responsible opera | The management  |
|   | tions center of the DMS when the operator sets | of an open      |
|   |  a message or enables the beacons on that DMS. | event shall be  |
|   |                                                | under the       |
|   |                                                | control of the  |
|   |                                                | responsible     |
|   |                                                | Center.         |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.2.16.2 Th                               | CHART-265       |
| 6 | e system shall clear the responsible operation |                 |
| 6 | s center of a DMS when its display is blanked. | When an event   |
|   |                                                | is closed the   |
|   |                                                | system shall    |
|   |                                                | remove all      |
|   |                                                | messages from   |
|   |                                                | devices and     |
|   |                                                | device queues   |
|   |                                                | associated with |
|   |                                                | the event.      |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.2.16.3 The                              | CHART-383       |
| 8 | system shall provide a mechanism to transfer a |                 |
| 9 |  DMS to another responsible operations center. | The system      |
|   |                                                | shall support   |
|   |                                                | the transfer of |
|   |                                                | responsibility  |
|   |                                                | for an open     |
|   |                                                | event from one  |
|   |                                                | Center to       |
|   |                                                | another.        |
+---+------------------------------------------------+-----------------+
| 4 | ####                                           | CHART-225       |
| 9 | 3.2.16.4 The system shall clear the responsibl |                 |
| 0 | e operations center of a DMS when it is reset. | A message       |
|   |                                                | entering a      |
|   |                                                | device queue    |
|   |                                                | with a higher   |
|   |                                                | priority than   |
|   |                                                | the current     |
|   |                                                | message on the  |
|   |                                                | device shall    |
|   |                                                | preempt the     |
|   |                                                | current         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 6 | #### 3.2.16.5 Th                               | CHART-792       |
| 6 | e system shall not allow a DMS to display a me |                 |
| 4 | ssage without a responsible operations center. | Device queue    |
|   |                                                | message         |
|   |                                                | attributes      |
|   |                                                | shall include   |
|   |                                                | the Center      |
|   |                                                | responsible for |
|   |                                                | the message.    |
+---+------------------------------------------------+-----------------+
| 6 | #### 3.2.16.6 The system shall not             | CHART-226       |
| 6 | hold an op center responsible for a blank DMS. |                 |
| 5 |                                                | A preempted     |
|   |                                                | message shall   |
|   |                                                | be returned to  |
|   |                                                | the device      |
|   |                                                | queue.          |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.2.17 The system shall allow an administr | CHART-244       |
| 6 | ator to override the current message on a DMS  |                 |
| 8 | assigned to any responsible operations center. | A suitably      |
|   |                                                | privileged user |
|   |                                                | shall be able   |
|   |                                                | to modify the   |
|   |                                                | priority of a   |
|   |                                                | message in a    |
|   |                                                | queue.          |
+---+------------------------------------------------+-----------------+
| 7 | ####                                           | CHART-244       |
| 6 | 3.2.17.1 The system shall set the controlling  |                 |
| 8 | operations center for the DMS to the operation | A suitably      |
|   | s center where the administrator is logged in. | privileged user |
|   |                                                | shall be able   |
|   |                                                | to modify the   |
|   |                                                | priority of a   |
|   |                                                | message in a    |
|   |                                                | queue.          |
+---+------------------------------------------------+-----------------+
| 2 | ### 3                                          | CHART-225       |
| 6 | .2.18 The system shall not allow an operator t |                 |
| 9 | o override the current message on a DMS assign | A message       |
|   | ed to a different operations center than the o | entering a      |
|   | perations center the operator is logged in to. | device queue    |
|   |                                                | with a higher   |
|   |                                                | priority than   |
|   |                                                | the current     |
|   |                                                | message on the  |
|   |                                                | device shall    |
|   |                                                | preempt the     |
|   |                                                | current         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.19 The system shall not allo           | CHART-225       |
| 9 | w an operator logged in at an operations cente |                 |
| 1 | r to blank the display of a DMS that is the re | A message       |
|   | sponsibility of a different operations center. | entering a      |
|   |                                                | device queue    |
|   |                                                | with a higher   |
|   |                                                | priority than   |
|   |                                                | the current     |
|   |                                                | message on the  |
|   |                                                | device shall    |
|   |                                                | preempt the     |
|   |                                                | current         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.2.20 The system shall allow an a         | CHART-244       |
| 9 | dministrator logged in at any operations cente |                 |
| 2 | r to blank the display of a DMS that is the re | A suitably      |
|   | sponsibility of a different operations center. | privileged user |
|   |                                                | shall be able   |
|   |                                                | to modify the   |
|   |                                                | priority of a   |
|   |                                                | message in a    |
|   |                                                | queue.          |
+---+------------------------------------------------+-----------------+
| 4 | ## 3.3 DMS Navigator                           |                 |
| 6 |                                                |                 |
| 0 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3.1 The navigato                         | CHART-97        |
| 7 | r shall provide a DMS group in the tree view.  |                 |
| 3 |                                                | The navigator   |
|   |                                                | shall provide a |
|   |                                                | device group in |
|   |                                                | the tree view.  |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.3.1.1                                   | CHART-98        |
| 9 |  Clicking on this group shall cause all system |                 |
| 6 |  DMS devices to be displayed in the list view. | Clicking on the |
|   |                                                | device group    |
|   |                                                | shall cause all |
|   |                                                | system devices  |
|   |                                                | to be displayed |
|   |                                                | in the list     |
|   |                                                | view.           |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3                                        | CHART-99        |
| 7 | .2 The navigator shall show the updating statu |                 |
| 4 | s of each of the following attributes for each | The navigator   |
|   |  DMS device at the maximum rate of the current | shall show the  |
|   | ly defined status polling rate for the device: | updating        |
|   |                                                | attributes and  |
|   |                                                | status of each  |
|   |                                                | of the devices. |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.1 Name/description                  | CHART-100       |
| 7 |                                                |                 |
| 5 |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | N               |
|   |                                                | ame/description |
|   |                                                | for each        |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.2 Object type (DMS)                 | CHART-102       |
| 7 |                                                |                 |
| 6 |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | Object type for |
|   |                                                | each device.    |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.3 Operational Status                | CHART-103       |
| 7 |                                                |                 |
| 7 |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | Operational     |
|   |                                                | Status for each |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 4 | ##### 3.3.2.3.1 Operational s                  | CHART-106       |
| 9 | tatus shall have one of the following values:  |                 |
| 7 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate        |
|   |                                                | Communications  |
|   |                                                | Failure values. |
|   |                                                |                 |
|   |                                                | CHART-105       |
|   |                                                |                 |
|   |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate        |
|   |                                                | Hardware        |
|   |                                                | Failure values. |
|   |                                                |                 |
|   |                                                | CHART-104       |
|   |                                                |                 |
|   |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate if the |
|   |                                                | device is       |
|   |                                                | Online or       |
|   |                                                | Offline.        |
+---+------------------------------------------------+-----------------+
| 5 | Online                                         | CHART-104       |
| 0 |                                                |                 |
| 0 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate if the |
|   |                                                | device is       |
|   |                                                | Online or       |
|   |                                                | Offline.        |
+---+------------------------------------------------+-----------------+
| 5 | Offline                                        | CHART-104       |
| 0 |                                                |                 |
| 2 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate if the |
|   |                                                | device is       |
|   |                                                | Online or       |
|   |                                                | Offline.        |
+---+------------------------------------------------+-----------------+
| 5 | Hardware failure                               | CHART-105       |
| 0 |                                                |                 |
| 4 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate        |
|   |                                                | Hardware        |
|   |                                                | Failure values. |
+---+------------------------------------------------+-----------------+
| 5 | Software Communications failure                | CHART-106       |
| 0 |                                                |                 |
| 6 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate        |
|   |                                                | Communications  |
|   |                                                | Failure values. |
+---+------------------------------------------------+-----------------+
| 5 | Communications failure                         | CHART-106       |
| 0 |                                                |                 |
| 8 |                                                | Operational     |
|   |                                                | status shall    |
|   |                                                | indicate        |
|   |                                                | Communications  |
|   |                                                | Failure values. |
+---+------------------------------------------------+-----------------+
| 5 | ##### 3.3.2.3.2 The ascend                     | CHART-112       |
| 1 | ing sort order of operational status shall be: |                 |
| 0 |                                                | The navigator   |
|   |                                                | shall allow a   |
|   |                                                | user to sort    |
|   |                                                | the information |
|   |                                                | in the list     |
|   |                                                | view by         |
|   |                                                | clicking on the |
|   |                                                | column header.  |
+---+------------------------------------------------+-----------------+
| 5 | Hardware Failure                               |                 |
| 1 |                                                |                 |
| 3 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | Software Communications Failure                |                 |
| 1 |                                                |                 |
| 5 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | Communications Failure                         |                 |
| 1 |                                                |                 |
| 7 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | Online                                         |                 |
| 1 |                                                |                 |
| 9 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | Offline                                        |                 |
| 2 |                                                |                 |
| 1 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.4 DMS geometry                      | CHART-107       |
| 8 |                                                |                 |
| 3 |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | DMS geometry    |
|   |                                                | for each DMS    |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3                                       | CHART-792       |
| 8 | .2.5 DMS Message responsible operations center |                 |
| 5 |                                                | Device queue    |
|   |                                                | message         |
|   |                                                | attributes      |
|   |                                                | shall include   |
|   |                                                | the Center      |
|   |                                                | responsible for |
|   |                                                | the message.    |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.6 Current message                   | CHART-108       |
| 8 |                                                |                 |
| 6 |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | current message |
|   |                                                | for each DMS    |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.2.7 Date/time of last status ch       | CHART-101       |
| 8 | ange (message change, operational status chang |                 |
| 7 | e, responsible operations center change, etc.) | The navigator   |
|   |                                                | shall show the  |
|   |                                                | date/time of    |
|   |                                                | last change in  |
|   |                                                | status for each |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.3.2.8 DMS ID                            | CHART-795       |
| 7 |                                                |                 |
| 6 |                                                | The GUI shall   |
|   |                                                | provide the     |
|   |                                                | capability to   |
|   |                                                | show the id of  |
|   |                                                | each device.    |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3.3 The navigator shall allow an oper    | CHART-110       |
| 8 | ator to right click on a DMS in the list view  |                 |
| 8 | to display a pop-up control menu for that DMS. | The navigator   |
|   |                                                | shall allow a   |
|   |                                                | user to right   |
|   |                                                | click on a      |
|   |                                                | device in the   |
|   |                                                | list view to    |
|   |                                                | display a       |
|   |                                                | pop-up control  |
|   |                                                | menu for that   |
|   |                                                | device.         |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3.                                       | CHART-111       |
| 8 | 4 The navigator shall allow an operator to rig |                 |
| 9 | ht click on a selected group of DMSs to displa | The navigator   |
|   | y a pop-up control menu for the selected DMSs. | shall allow an  |
|   |                                                | user to right   |
|   |                                                | click on a      |
|   |                                                | selected group  |
|   |                                                | of devices to   |
|   |                                                | display a       |
|   |                                                | pop-up control  |
|   |                                                | menu for the    |
|   |                                                | selected        |
|   |                                                | devices.        |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.3.5 The navigator shall                  | CHART-112       |
| 2 | allow an operator to sort the information in t |                 |
| 3 | he list view by clicking on the column header. | The navigator   |
|   |                                                | shall allow a   |
|   |                                                | user to sort    |
|   |                                                | the information |
|   |                                                | in the list     |
|   |                                                | view by         |
|   |                                                | clicking on the |
|   |                                                | column header.  |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3.6 The system shall p                   | CHART-113       |
| 9 | rovide a DMS message editor which will allow a |                 |
| 0 | n operator to format a DMS message as follows: | The system      |
|   |                                                | shall provide a |
|   |                                                | DMS message     |
|   |                                                | editor which    |
|   |                                                | will allow a    |
|   |                                                | user to format  |
|   |                                                | a DMS message.  |
+---+------------------------------------------------+-----------------+
| 2 | ####                                           | CHART-114       |
| 9 |  3.3.6.1 The message editor shall allow an ope |                 |
| 1 | rator to enter message text into a text field. | The DMS message |
|   |                                                | editor shall    |
|   |                                                | allow a user to |
|   |                                                | enter message   |
|   |                                                | text into a     |
|   |                                                | text field.     |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.                                        | CHART-115       |
| 9 | 3.6.2 The message editor shall show the operat |                 |
| 2 | or an updating view of the message text format | The DMS message |
|   | ted for the smallest DMS being altered, with t | editor shall    |
|   | he option to view the other selected formats.  | show the        |
|   |                                                | operator an     |
|   |                                                | updating view   |
|   |                                                | of the message  |
|   |                                                | text formatted  |
|   |                                                | for the         |
|   |                                                | smallest DMS    |
|   |                                                | being altered,  |
|   |                                                | with the option |
|   |                                                | to view the     |
|   |                                                | other selected  |
|   |                                                | formats.        |
+---+------------------------------------------------+-----------------+
| 2 | #### 3.3.6.3 The message ed                    | CHART-116       |
| 9 | itor shall inform the operator if the entered  |                 |
| 3 | message text would be truncated when formatted | The DMS message |
|   |  to fit any of the selected DMS being altered. | editor shall    |
|   |                                                | inform the      |
|   |                                                | operator if the |
|   |                                                | entered message |
|   |                                                | text would be   |
|   |                                                | truncated when  |
|   |                                                | formatted to    |
|   |                                                | fit any of the  |
|   |                                                | selected DMS    |
|   |                                                | being altered.  |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.3.                                      | CHART-117       |
| 7 | 6.4 When a group of DMSs are selected to recei |                 |
| 1 | ve the same message, the message editor shall  | When a group of |
|   | format the message for each DMS type selected. | DMSs are        |
|   |                                                | selected to     |
|   |                                                | receive the     |
|   |                                                | same message,   |
|   |                                                | the message     |
|   |                                                | editor shall    |
|   |                                                | format the      |
|   |                                                | message for     |
|   |                                                | each DMS type   |
|   |                                                | selected.       |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.3.6.5 The system shall not              | CHART-118       |
| 7 |  allow truncated messages to be sent to a DMS. |                 |
| 0 |                                                | The system      |
|   |                                                | shall not allow |
|   |                                                | truncated       |
|   |                                                | messages to be  |
|   |                                                | sent to a DMS.  |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.                                         | CHART-125       |
| 9 | 3.7 The system shall provide a DMS show displa |                 |
| 4 | y window, which will show a graphical depictio | The system      |
|   | n of the current message for a particular DMS. | shall provide a |
|   |                                                | DMS show        |
|   |                                                | display window, |
|   |                                                | which will show |
|   |                                                | a graphical     |
|   |                                                | depiction of    |
|   |                                                | the current     |
|   |                                                | message for a   |
|   |                                                | particular DMS. |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.                                         | CHART-137       |
| 9 | 3.8 The system shall notify the initiating ope |                 |
| 5 | rator should an attempt to control a DMS fail. | The system      |
|   |                                                | shall notify    |
|   |                                                | the initiating  |
|   |                                                | operator should |
|   |                                                | an attempt to   |
|   |                                                | control a DMS   |
|   |                                                | fail.           |
|   |                                                |                 |
|   |                                                | CHART-417       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall inform    |
|   |                                                | the operators   |
|   |                                                | of a DMS        |
|   |                                                | failure.        |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.3.9 The system shall n                   | CHART-290       |
| 5 | otify all operators of successful DMS control  |                 |
| 1 | activities by updating the run-time status inf | The system      |
|   | ormation displayed in the navigator, and any w | shall log event |
|   | indows that currently display the DMS message. | messages        |
|   |                                                | associated with |
|   |                                                | DMS activities. |
|   |                                                |                 |
|   |                                                | CHART-99        |
|   |                                                |                 |
|   |                                                | The navigator   |
|   |                                                | shall show the  |
|   |                                                | updating        |
|   |                                                | attributes and  |
|   |                                                | status of each  |
|   |                                                | of the devices. |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.3.10                                     | CHART-792       |
| 7 |  The Graphical User Interface shall display th |                 |
| 8 | e following information upon operator request: | Device queue    |
|   |                                                | message         |
|   |                                                | attributes      |
|   |                                                | shall include   |
|   |                                                | the Center      |
|   |                                                | responsible for |
|   |                                                | the message.    |
|   |                                                |                 |
|   |                                                | CHART-796       |
|   |                                                |                 |
|   |                                                | The GUI shall   |
|   |                                                | provide the     |
|   |                                                | capability to   |
|   |                                                | show the        |
|   |                                                | network         |
|   |                                                | connection site |
|   |                                                | for a device.   |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.3.10.1 The Graphical                    | CHART-796       |
| 8 | User Interface shall display the DMS network c |                 |
| 0 | onnection site of a DMS upon operator request. | The GUI shall   |
|   |                                                | provide the     |
|   |                                                | capability to   |
|   |                                                | show the        |
|   |                                                | network         |
|   |                                                | connection site |
|   |                                                | for a device.   |
+---+------------------------------------------------+-----------------+
| 7 | #### 3.3.10.2 The Gr                           | CHART-792       |
| 7 | aphical User Interface shall display the ownin |                 |
| 9 | g organization of a DMS upon operator request  | Device queue    |
|   |                                                | message         |
|   |                                                | attributes      |
|   |                                                | shall include   |
|   |                                                | the Center      |
|   |                                                | responsible for |
|   |                                                | the message.    |
|   |                                                |                 |
|   |                                                | CHART-1028      |
|   |                                                |                 |
|   |                                                | Device          |
|   |                                                | attribute       |
|   |                                                | information     |
|   |                                                | shall include   |
|   |                                                | the owning      |
|   |                                                | organization    |
|   |                                                | for the device. |
+---+------------------------------------------------+-----------------+
| 2 | ## 3.4 DMS Polling                             |                 |
| 9 |                                                |                 |
| 6 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.4.1 The system sha                       | CHART-32        |
| 9 | ll provide a mechanism to poll each DMS for st |                 |
| 8 | atus on a configurable interval basis. (Actual | The system      |
|   |  polling is carried out by the FMS subsystem.) | shall provide a |
|   |                                                | mechanism to    |
|   |                                                | poll devices    |
|   |                                                | for status on a |
|   |                                                | configurable    |
|   |                                                | interval basis. |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.1.1 T                                 | CHART-36        |
| 2 | he minimum polling interval shall be 1 minute. |                 |
| 4 |                                                | The minimum     |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 1 minute.    |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.1.2 T                                 | CHART-37        |
| 2 | he maximum polling interval shall be 24 hours. |                 |
| 5 |                                                | The maximum     |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 24 hours.    |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.1.3 The minimum incre                 | CHART-38        |
| 2 | ment for a polling interval shall be 1 minute. |                 |
| 6 |                                                | The minimum     |
|   |                                                | increment for a |
|   |                                                | polling         |
|   |                                                | interval shall  |
|   |                                                | be 1 minute.    |
+---+------------------------------------------------+-----------------+
| 2 | ### 3.4.2 The system shall allow an opera      | CHART-83        |
| 9 | tor to place an online DMS offline that curren |                 |
| 7 | tly has no responsible operations center or th | The system      |
|   | e responsible operations center is the operati | shall allow a   |
|   | ons center currently assigned to the operator. | suitably        |
|   |                                                | privileged user |
|   |                                                | to set a DMS    |
|   |                                                | offline.        |
|   |                                                |                 |
|   |                                                | CHART-40        |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to place an     |
|   |                                                | online device   |
|   |                                                | offline.        |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.2.1 Placing a                         | CHART-667       |
| 2 | DMS offline shall blank the displayed message. |                 |
| 7 |                                                | The system      |
|   |                                                | shall blank the |
|   |                                                | display of a    |
|   |                                                | DMS that is set |
|   |                                                | to offline.     |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.2.2 Placing a DMS offline             | CHART-667       |
| 2 | shall clear the responsible operations center. |                 |
| 8 |                                                | The system      |
|   |                                                | shall blank the |
|   |                                                | display of a    |
|   |                                                | DMS that is set |
|   |                                                | to offline.     |
|   |                                                |                 |
|   |                                                | CHART-225       |
|   |                                                |                 |
|   |                                                | A message       |
|   |                                                | entering a      |
|   |                                                | device queue    |
|   |                                                | with a higher   |
|   |                                                | priority than   |
|   |                                                | the current     |
|   |                                                | message on the  |
|   |                                                | device shall    |
|   |                                                | preempt the     |
|   |                                                | current         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.2.3 If the DMS has beacons, placi     | CHART-65        |
| 2 | ng the DMS offline shall turn the beacons off. |                 |
| 9 |                                                | If the beacons  |
|   |                                                | of a DMS are on |
|   |                                                | when the DMS is |
|   |                                                | blanked, they   |
|   |                                                | shall be turned |
|   |                                                | off.            |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.4.3 The system shall all                 | CHART-745       |
| 3 | ow an operator to place an offline DMS online. |                 |
| 0 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to set a DMS    |
|   |                                                | online.         |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.3.1 Placing a                         | CHART-668       |
| 3 |  DMS online shall blank the displayed message. |                 |
| 1 |                                                | The system      |
|   |                                                | shall           |
|   |                                                | immediately     |
|   |                                                | blank the       |
|   |                                                | display of a    |
|   |                                                | DMS that is set |
|   |                                                | to online.      |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.3.2 Placing a DMS online              | CHART-797       |
| 3 | shall clear the responsible operations center. |                 |
| 2 |                                                | The system      |
|   |                                                | shall enable    |
|   |                                                | the message     |
|   |                                                | queue for a DMS |
|   |                                                | that is set to  |
|   |                                                | online.         |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.4.3.3 If the DMS has beacons, plac      | CHART-65        |
| 3 | ing the DMS online shall turn the beacons off. |                 |
| 3 |                                                | If the beacons  |
|   |                                                | of a DMS are on |
|   |                                                | when the DMS is |
|   |                                                | blanked, they   |
|   |                                                | shall be turned |
|   |                                                | off.            |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.4.4 The syste                            | CHART-84        |
| 3 | m shall check known error indicators in the st |                 |
| 4 | atus packet as specified by the DMS protocol a | The system      |
|   | nd shall inform operators of a DMS hardware fa | shall check     |
|   | ilure should an error condition be discovered. | known error     |
|   |                                                | indicators in   |
|   |                                                | the status      |
|   |                                                | packet as       |
|   |                                                | specified by    |
|   |                                                | the DMS         |
|   |                                                | protocol and    |
|   |                                                | shall inform    |
|   |                                                | operators of a  |
|   |                                                | DMS hardware    |
|   |                                                | failure should  |
|   |                                                | an error        |
|   |                                                | condition be    |
|   |                                                | discovered.     |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.                                         | CHART-39        |
| 3 | 4.5 The system shall inform operators of a DMS |                 |
| 5 |  communications failure if it is unable to com | The system      |
|   | municate with a particular DMS during polling. | shall inform    |
|   |                                                | operators of a  |
|   |                                                | device          |
|   |                                                | communications  |
|   |                                                | failure if it   |
|   |                                                | is unable to    |
|   |                                                | communicate     |
|   |                                                | with a          |
|   |                                                | particular      |
|   |                                                | device during   |
|   |                                                | polling.        |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.4.6 When a DMS communications failur     | CHART-669       |
| 8 | e has occurred, the system shall mark the DMS  |                 |
| 5 | as blank after a timeout threshold is reached. | The system      |
|   |                                                | shall mark a    |
|   |                                                | DMS as blank    |
|   |                                                | after a timeout |
|   |                                                | threshold is    |
|   |                                                | reached         |
|   |                                                | following a DMS |
|   |                                                | communications  |
|   |                                                | failure.        |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.4.7                                      | CHART-670       |
| 8 |  The system shall execute a blank message comm |                 |
| 4 | and for the DMS when successful communications | The system      |
|   |  with the DMS is resumed after the DMS communi | shall blank a   |
|   | cations failure timeout threshold has expired. | DMS when        |
|   |                                                | successful      |
|   |                                                | communication   |
|   |                                                | with the DMS is |
|   |                                                | resumed after   |
|   |                                                | the DMS         |
|   |                                                | communications  |
|   |                                                | failure timeout |
|   |                                                | threshold has   |
|   |                                                | expired.        |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.4.8 The system shall allow set           | CHART-671       |
| 8 | ting of a configuration parameter to set the D |                 |
| 3 | MS communications failure timeout threshold us | The system      |
|   | ing a value expressed in minutes using any int | shall support a |
|   | eger value between 1 minute and 16535 minutes. | DMS             |
|   |                                                | communications  |
|   |                                                | failure timeout |
|   |                                                | threshold       |
|   |                                                | expressed in    |
|   |                                                | minutes from 1  |
|   |                                                | minute and      |
|   |                                                | 16535 minutes.  |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.4.9 The DMS communications failure t     | CHART-672       |
| 8 | imeout threshold shall default to 10 minutes.  |                 |
| 2 |                                                | The DMS         |
|   |                                                | communications  |
|   |                                                | failure timeout |
|   |                                                | default shall   |
|   |                                                | be 10 minutes.  |
+---+------------------------------------------------+-----------------+
| 7 | ### 3.4.10 When a DMS communi                  | CHART-1032      |
| 8 | cations failure has occurred, the system shall |                 |
| 1 |  clear the controlling operations center for t | The system      |
|   | hat DMS after a timeout threshold is reached.  | shall return    |
|   |                                                | the current     |
|   |                                                | message to the  |
|   |                                                | device queue    |
|   |                                                | following a DMS |
|   |                                                | communications  |
|   |                                                | failure.        |
|   |                                                |                 |
|   |                                                | CHART-670       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall blank a   |
|   |                                                | DMS when        |
|   |                                                | successful      |
|   |                                                | communication   |
|   |                                                | with the DMS is |
|   |                                                | resumed after   |
|   |                                                | the DMS         |
|   |                                                | communications  |
|   |                                                | failure timeout |
|   |                                                | threshold has   |
|   |                                                | expired.        |
+---+------------------------------------------------+-----------------+
| 2 | ## 3.5 DMS Messages Formats                    |                 |
| 9 |                                                |                 |
| 9 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.5.1 The system shall format DMS mess     | CHART-146       |
| 0 | ages using the MULTI DMS mark-up language as s |                 |
| 1 | pecified in the NTCIP document ISO/WD 14823-2. | The system      |
|   |                                                | shall format    |
|   |                                                | DMS messages    |
|   |                                                | using the MULTI |
|   |                                                | DMS mark-up     |
|   |                                                | language as     |
|   |                                                | specified in    |
|   |                                                | the NTCIP       |
|   |                                                | document ISO/WD |
|   |                                                | 14823-2.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.5.2 The system shall format all DMS      | CHART-147       |
| 0 |  messages for display according to the algorit |                 |
| 2 | hm provided on page 20 of the initial RFP and  | The system      |
|   | as demonstrated in the requirements prototype. | shall format    |
|   |                                                | message text    |
|   |                                                | for display on  |
|   |                                                | a DMS.          |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5                                       | CHART-148       |
| 0 | .2.1 All lines shall be centered horizontally. |                 |
| 3 |                                                | All text lines  |
|   |                                                | shall be        |
|   |                                                | centered        |
|   |                                                | horizontally on |
|   |                                                | the DMS.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.2 Any                               | CHART-149       |
| 0 |  phase (page on a sign display) with one line  |                 |
| 4 | of text shall be displayed on the center line. | Any phase (page |
|   |                                                | on a sign       |
|   |                                                | display) with   |
|   |                                                | one line of     |
|   |                                                | text shall be   |
|   |                                                | displayed on    |
|   |                                                | the center      |
|   |                                                | line.           |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5                                       | CHART-150       |
| 0 | .2.3 Any phase with two lines of text shall ha |                 |
| 5 | ve that text displayed on lines one and three. | Any phase (page |
|   |                                                | on a sign       |
|   |                                                | display) with   |
|   |                                                | two lines of    |
|   |                                                | text shall have |
|   |                                                | that text       |
|   |                                                | displayed on    |
|   |                                                | lines one and   |
|   |                                                | three.          |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.4 The phrase \"Expec                | CHART-151       |
| 0 | t Delays\" may be broken up between two lines. |                 |
| 6 |                                                | The phrase      |
|   |                                                | \"Expect        |
|   |                                                | Delays\" may be |
|   |                                                | broken up       |
|   |                                                | between two     |
|   |                                                | lines.          |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.5 Route t                           | CHART-152       |
| 0 | ypes and Route numbers shall not be broken up. |                 |
| 7 |                                                | The system      |
|   |                                                | shall employ    |
|   |                                                | rules for       |
|   |                                                | formatting      |
|   |                                                | route type and  |
|   |                                                | route number    |
|   |                                                | information.    |
|   |                                                |                 |
|   |                                                | CHART-390       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall format    |
|   |                                                | onto one line   |
|   |                                                | the route       |
|   |                                                | information     |
|   |                                                | that contains   |
|   |                                                | the route type  |
|   |                                                | "MD" followed   |
|   |                                                | by a space and  |
|   |                                                | another         |
|   |                                                | continuous      |
|   |                                                | string of       |
|   |                                                | characters.     |
|   |                                                |                 |
|   |                                                | CHART-391       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall format    |
|   |                                                | onto one line   |
|   |                                                | the route       |
|   |                                                | information     |
|   |                                                | that contains   |
|   |                                                | the route type  |
|   |                                                | "I" followed by |
|   |                                                | a space and     |
|   |                                                | another         |
|   |                                                | continuous      |
|   |                                                | string of       |
|   |                                                | characters.     |
|   |                                                |                 |
|   |                                                | CHART-392       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall format    |
|   |                                                | onto one line   |
|   |                                                | the route       |
|   |                                                | information     |
|   |                                                | that contains   |
|   |                                                | the route type  |
|   |                                                | "US" followed   |
|   |                                                | by a space and  |
|   |                                                | another         |
|   |                                                | continuous      |
|   |                                                | string of       |
|   |                                                | characters.     |
|   |                                                |                 |
|   |                                                | CHART-393       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall format    |
|   |                                                | onto one line   |
|   |                                                | the route       |
|   |                                                | information     |
|   |                                                | that contains   |
|   |                                                | the route type  |
|   |                                                | "Ex" followed   |
|   |                                                | by a space and  |
|   |                                                | another         |
|   |                                                | continuous      |
|   |                                                | string of       |
|   |                                                | characters.     |
|   |                                                |                 |
|   |                                                | CHART-394       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall format    |
|   |                                                | onto one line   |
|   |                                                | the route       |
|   |                                                | information     |
|   |                                                | that contains   |
|   |                                                | the route type  |
|   |                                                | "Exit" followed |
|   |                                                | by a space and  |
|   |                                                | another         |
|   |                                                | continuous      |
|   |                                                | string of       |
|   |                                                | characters.     |
|   |                                                |                 |
|   |                                                | CHART-395       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall keep the  |
|   |                                                | route direction |
|   |                                                | " N" on the     |
|   |                                                | same line as    |
|   |                                                | the preceding   |
|   |                                                | route           |
|   |                                                | information.    |
|   |                                                |                 |
|   |                                                | CHART-396       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall keep the  |
|   |                                                | route direction |
|   |                                                | " S" on the     |
|   |                                                | same line as    |
|   |                                                | the preceding   |
|   |                                                | route           |
|   |                                                | information.    |
|   |                                                |                 |
|   |                                                | CHART-397       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall keep the  |
|   |                                                | route direction |
|   |                                                | " E" on the     |
|   |                                                | same line as    |
|   |                                                | the preceding   |
|   |                                                | route           |
|   |                                                | information.    |
|   |                                                |                 |
|   |                                                | CHART-398       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall keep the  |
|   |                                                | route direction |
|   |                                                | " W" on the     |
|   |                                                | same line as    |
|   |                                                | the preceding   |
|   |                                                | route           |
|   |                                                | information.    |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.6 Directions containing the route   | CHART-152       |
| 0 | and direction of the incident may be broken up |                 |
| 8 |  as shown in the examples provided in the RFP. | The system      |
|   |                                                | shall employ    |
|   |                                                | rules for       |
|   |                                                | formatting      |
|   |                                                | route type and  |
|   |                                                | route number    |
|   |                                                | information.    |
|   |                                                |                 |
|   |                                                | CHART-399       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall place on  |
|   |                                                | a new line any  |
|   |                                                | route           |
|   |                                                | information     |
|   |                                                | that is lead by |
|   |                                                | the route       |
|   |                                                | indicator "AT". |
|   |                                                |                 |
|   |                                                | CHART-400       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall place on  |
|   |                                                | a new line any  |
|   |                                                | route           |
|   |                                                | information     |
|   |                                                | that is lead by |
|   |                                                | the route       |
|   |                                                | indicator       |
|   |                                                | "PRIOR".        |
|   |                                                |                 |
|   |                                                | CHART-401       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall place on  |
|   |                                                | a new line any  |
|   |                                                | route           |
|   |                                                | information     |
|   |                                                | that is lead by |
|   |                                                | the route       |
|   |                                                | indicator       |
|   |                                                | "PAST".         |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.7 The phrase \"St                   | CHART-154       |
| 0 | ay Alert\" may be broken up between two lines. |                 |
| 9 |                                                | The DMS message |
|   |                                                | format The      |
|   |                                                | phrase \"Stay   |
|   |                                                | Alert\" may be  |
|   |                                                | broken up       |
|   |                                                | between two     |
|   |                                                | lines.          |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.8 Each DMS shall                    | CHART-155       |
| 1 | use only one font for displaying DMS messages. |                 |
| 0 |                                                | Each DMS shall  |
|   |                                                | use only one    |
|   |                                                | font for        |
|   |                                                | displaying DMS  |
|   |                                                | messages.       |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.5.2.9 The system sha                    | CHART-156       |
| 1 | ll support the following MULTI language tags:  |                 |
| 1 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | MULTI language  |
|   |                                                | tags.           |
+---+------------------------------------------------+-----------------+
| 5 | *New Page \[np\]*                              | CHART-157       |
| 3 |                                                |                 |
| 8 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the New Page    |
|   |                                                | \[np\] MULTI    |
|   |                                                | language tag.   |
|   |                                                | Used to specify |
|   |                                                | a phase break   |
+---+------------------------------------------------+-----------------+
| 5 | *New Line \[nlx\]*                             | CHART-158       |
| 4 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the New Line    |
|   |                                                | \[nlx\] MULTI   |
|   |                                                | language tag.   |
|   |                                                | Used to specify |
|   |                                                | a new line of   |
|   |                                                | text            |
+---+------------------------------------------------+-----------------+
| 5 | *Justification -- line \[jlx\]*                | CHART-159       |
| 4 |                                                |                 |
| 4 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the             |
|   |                                                | Justification   |
|   |                                                | -- line \[jlx\] |
|   |                                                | MULTI language  |
|   |                                                | tag. Used to    |
|   |                                                | specify the     |
|   |                                                | justification   |
|   |                                                | for the current |
|   |                                                | line of text.   |
+---+------------------------------------------------+-----------------+
| 5 | *Page timing \[ptxoy\]*                        | CHART-160       |
| 4 |                                                |                 |
| 7 |                                                | The system      |
|   |                                                | shall support   |
|   |                                                | the Page timing |
|   |                                                | \[ptxoy\] MULTI |
|   |                                                | language tag.   |
|   |                                                | Used to specify |
|   |                                                | the time-on and |
|   |                                                | time-off in     |
|   |                                                | tenths of a     |
|   |                                                | second for a    |
|   |                                                | particular      |
|   |                                                | phase of a      |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ## 3.6 DMS Message Libraries                   |                 |
| 1 |                                                |                 |
| 6 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.1 The system shall                     | CHART-174       |
| 1 |  allow an operator to set a message on a DMS f |                 |
| 8 | rom a message stored in a DMS message library. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to set a        |
|   |                                                | message on a    |
|   |                                                | DMS from a      |
|   |                                                | message stored  |
|   |                                                | in a DMS        |
|   |                                                | message         |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.2 The system shall allow an            | CHART-166       |
| 1 |  operator to create a new DMS message library. |                 |
| 9 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to create a new |
|   |                                                | message         |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.3 The system shall allo                | CHART-167       |
| 2 | w an operator to delete a DMS message library. |                 |
| 0 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to delete a     |
|   |                                                | message         |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.6.3.1 This action shall dele            | CHART-168       |
| 5 | te all messages stored in the library as well. |                 |
| 0 |                                                | The deletion of |
|   |                                                | a message       |
|   |                                                | library shall   |
|   |                                                | delete all      |
|   |                                                | messages stored |
|   |                                                | in the library  |
|   |                                                | as well.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.4 The system shall allow an operato    | CHART-169       |
| 2 | r to change the name of a DMS message library. |                 |
| 2 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to change the   |
|   |                                                | name of a       |
|   |                                                | message         |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.5 The system shall allow an            | CHART-170       |
| 2 |  operator to create a new DMS library message. |                 |
| 3 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to create a new |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.6 The system shall allo                | CHART-171       |
| 2 | w an operator to delete a DMS library message. |                 |
| 4 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to delete a     |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #                                              | CHART-172       |
| 2 | ## 3.6.7 The system shall allow an operator to |                 |
| 5 |  modify the contents of a DMS library message. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to modify the   |
|   |                                                | contents of a   |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.8 The system shall allow an operato    | CHART-173       |
| 2 | r to change the name of a DMS library message. |                 |
| 6 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to change the   |
|   |                                                | name of a       |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.6.9 The naviga                           | CHART-164       |
| 5 | tor shall provide a DMS message library group  |                 |
| 6 | in the tree view for each DMS message library. | The system      |
|   |                                                | shall support   |
|   |                                                | libraries       |
|   |                                                | containing DMS  |
|   |                                                | messages.       |
|   |                                                |                 |
|   |                                                | CHART-126       |
|   |                                                |                 |
|   |                                                | The navigator   |
|   |                                                | shall provide a |
|   |                                                | DMS message     |
|   |                                                | library group   |
|   |                                                | in the tree     |
|   |                                                | view for each   |
|   |                                                | DMS message     |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 4 | #### 3.6.9.1 Clicking on this group shall cau  | CHART-673       |
| 5 | se all DMS library messages stored in the sele |                 |
| 7 | cted library to be displayed in the list view. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to display the  |
|   |                                                | contents of a   |
|   |                                                | library         |
|   |                                                | message.        |
|   |                                                |                 |
|   |                                                | CHART-127       |
|   |                                                |                 |
|   |                                                | Clicking on the |
|   |                                                | DMS Message     |
|   |                                                | Library group   |
|   |                                                | shall cause all |
|   |                                                | DMS library     |
|   |                                                | messages stored |
|   |                                                | in the selected |
|   |                                                | library to be   |
|   |                                                | displayed in    |
|   |                                                | the list view.  |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.10 The navigator shall show the        | CHART-798       |
| 2 | following attributes for each library message: |                 |
| 8 |                                                | The system      |
|   |                                                | shall allow the |
|   |                                                | user to display |
|   |                                                | attributes of a |
|   |                                                | DMS library     |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.6.10.1 Message description              | CHART-800       |
| 2 |                                                |                 |
| 9 |                                                | The system      |
|   |                                                | shall display   |
|   |                                                | the message     |
|   |                                                | description for |
|   |                                                | a DMS library   |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.6.10.2 Message text                     | CHART-801       |
| 3 |                                                |                 |
| 0 |                                                | The system      |
|   |                                                | shall display   |
|   |                                                | the message     |
|   |                                                | text for a DMS  |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.6.10.3 Topic/Category                   | CHART-802       |
| 3 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall display   |
|   |                                                | the message     |
|   |                                                | category for a  |
|   |                                                | DMS library     |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ##                                             | CHART-803       |
| 3 | ## 3.6.10.4 Required sign length in characters |                 |
| 2 |                                                | The system      |
|   |                                                | shall display   |
|   |                                                | the required    |
|   |                                                | message sign    |
|   |                                                | length for a    |
|   |                                                | DMS library     |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.6.10.5 Beacon indicator                 | CHART-804       |
| 3 |                                                |                 |
| 3 |                                                | The system      |
|   |                                                | shall display   |
|   |                                                | the message     |
|   |                                                | beacon          |
|   |                                                | indicator for a |
|   |                                                | DMS library     |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ###                                            | CHART-134       |
| 3 |  3.6.11 The navigator shall allow an operator  |                 |
| 4 | to drag a DMS message from a library to a DMS. | The navigator   |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to drag a DMS   |
|   |                                                | message from a  |
|   |                                                | message library |
|   |                                                | to a DMS.       |
|   |                                                |                 |
|   |                                                | CHART-174       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to set a        |
|   |                                                | message on a    |
|   |                                                | DMS from a      |
|   |                                                | message stored  |
|   |                                                | in a DMS        |
|   |                                                | message         |
|   |                                                | library.        |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.6.11.1 If the D                         | CHART-674       |
| 4 | MS has beacons and the beacon indicator in the |                 |
| 9 |  library message is true then the system shall | The system      |
|   |  turn the beacons on when setting the message. | shall support   |
|   |                                                | setting the     |
|   |                                                | beacon state    |
|   |                                                | for a DMS       |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.6.12 The navigator                       | CHART-62        |
| 1 | shall allow an operator to drag a DMS message  |                 |
| 7 | from a library to a group of DMSs for display. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to set the      |
|   |                                                | current message |
|   |                                                | for a selected  |
|   |                                                | group of DMSs.  |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.6.12.1 If any DMS in the gro            | CHART-674       |
| 5 | up has beacons and the beacon indicator in the |                 |
| 0 |  library message is true then the system shall | The system      |
|   |  turn the beacons on when setting the message. | shall support   |
|   |                                                | setting the     |
|   |                                                | beacon state    |
|   |                                                | for a DMS       |
|   |                                                | library         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ## 3.7 Operations log                          |                 |
| 3 |                                                |                 |
| 5 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.7.1 The system                           | CHART-274       |
| 3 |  shall generate a message in the operations lo |                 |
| 7 | g for each of the following system operations: | The system      |
|   |                                                | shall log       |
|   |                                                | messages        |
|   |                                                | generated from  |
|   |                                                | operations      |
|   |                                                | activities.     |
|   |                                                |                 |
|   |                                                | CHART-247       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall maintain  |
|   |                                                | a system        |
|   |                                                | operations log. |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.1 User login                        | CHART-275       |
| 3 |                                                |                 |
| 8 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | User login.     |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.2 Failed user login attempts        | CHART-276       |
| 5 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Failed user     |
|   |                                                | login attempts. |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.3 User logout                       | CHART-277       |
| 3 |                                                |                 |
| 9 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | User logout.    |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.4 Set DMS message                   | CHART-291       |
| 4 |                                                |                 |
| 0 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message         |
|   |                                                | associated with |
|   |                                                | an event for    |
|   |                                                | Set DMS         |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.5 Blank DMS display                 | CHART-292       |
| 4 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message         |
|   |                                                | associated with |
|   |                                                | an event for    |
|   |                                                | Blank DMS       |
|   |                                                | display.        |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.6 Reset DMS controller              | CHART-293       |
| 4 |                                                |                 |
| 2 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | for Reset DMS   |
|   |                                                | controller.     |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.7 Change DMS name                   | CHART-282       |
| 4 |                                                |                 |
| 3 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Change shared   |
|   |                                                | resource name.  |
+---+------------------------------------------------+-----------------+
| 3 | #### 3.7.1.8 Change DMS polling interval       | CHART-285       |
| 4 |                                                |                 |
| 4 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Change shared   |
|   |                                                | resource        |
|   |                                                | polling         |
|   |                                                | interval.       |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.9 Take DMS offline                  | CHART-284       |
| 5 |                                                |                 |
| 2 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Take shared     |
|   |                                                | resource        |
|   |                                                | offline.        |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.10 Place a DMS online               | CHART-283       |
| 5 |                                                |                 |
| 3 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Place a shared  |
|   |                                                | resource        |
|   |                                                | online.         |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.11 Adding users                     | CHART-278       |
| 5 |                                                |                 |
| 4 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Adding users.   |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.12 Modifying users                  | CHART-279       |
| 5 |                                                |                 |
| 5 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Modifying       |
|   |                                                | users.          |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.13 Deleting users                   | CHART-280       |
| 5 |                                                |                 |
| 6 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Deleting users. |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.14 Change in DMS hardware status    | CHART-286       |
| 5 |                                                |                 |
| 7 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Change in       |
|   |                                                | shared resource |
|   |                                                | hardware        |
|   |                                                | status.         |
+---+------------------------------------------------+-----------------+
| 5 | ###                                            | CHART-298       |
| 5 | # 3.7.1.15 Change to the DMS Message Libraries |                 |
| 8 |                                                | The system      |
|   |                                                | shall log       |
|   |                                                | operations      |
|   |                                                | messages        |
|   |                                                | associated with |
|   |                                                | Message Library |
|   |                                                | management.     |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.16 Cha                              | CHART-794       |
| 5 | nge in responsible operations center for a DMS |                 |
| 9 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | when a message  |
|   |                                                | is preempted.   |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.17 Adding a DMS Configuration       | CHART-287       |
| 6 |                                                |                 |
| 0 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Adding a shared |
|   |                                                | resource        |
|   |                                                | Configuration.  |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.18 Modifying a DMS Configuration    | CHART-288       |
| 6 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Modifying a     |
|   |                                                | shared resource |
|   |                                                | Configuration.  |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.19 Deleting a DMS Configuration     | CHART-289       |
| 6 |                                                |                 |
| 2 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message for     |
|   |                                                | Deleting a      |
|   |                                                | shared resource |
|   |                                                | Configuration.  |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.20 Adding a DMS Plan                | CHART-305       |
| 6 |                                                |                 |
| 3 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | for Adding a    |
|   |                                                | Plan.           |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.21 Modifying a DMS Plan             | CHART-306       |
| 6 |                                                |                 |
| 4 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | for Modifying a |
|   |                                                | Plan.           |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.22 Deleting a DMS Plan              | CHART-307       |
| 6 |                                                |                 |
| 5 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | for Deleting a  |
|   |                                                | Plan.           |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.7.1.23 Activation of a DMS Plan         | CHART-308       |
| 6 |                                                |                 |
| 6 |                                                | The system      |
|   |                                                | shall log a     |
|   |                                                | message to the  |
|   |                                                | operations log  |
|   |                                                | for Activation  |
|   |                                                | of a Plan.      |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.7.2 The system shall store the followi   | CHART-469       |
| 4 | ng information with each operations log entry: |                 |
| 5 |                                                | The system      |
|   |                                                | shall store     |
|   |                                                | identifying     |
|   |                                                | information     |
|   |                                                | with each       |
|   |                                                | operations log  |
|   |                                                | entry.          |
+---+------------------------------------------------+-----------------+
| 7 | *Workstation Identifier*                       | CHART-471       |
| 7 |                                                |                 |
| 5 |                                                | The system      |
|   |                                                | shall store the |
|   |                                                | Workstation     |
|   |                                                | Identifier (if  |
|   |                                                | applicable)     |
|   |                                                | with each       |
|   |                                                | operations log  |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 5 | *Date/time the operation was performed*        | CHART-470       |
| 6 |                                                |                 |
| 9 |                                                | The system      |
|   |                                                | shall store the |
|   |                                                | Date/time the   |
|   |                                                | operation was   |
|   |                                                | performed with  |
|   |                                                | each operations |
|   |                                                | log message.    |
+---+------------------------------------------------+-----------------+
| 5 | *User name of initiating operator*             | CHART-473       |
| 7 |                                                |                 |
| 1 |                                                | The system      |
|   |                                                | shall store the |
|   |                                                | User name of    |
|   |                                                | initiating      |
|   |                                                | user, or the    |
|   |                                                | identifier of   |
|   |                                                | the initiating  |
|   |                                                | application if  |
|   |                                                | system          |
|   |                                                | generated, with |
|   |                                                | each operations |
|   |                                                | log message.    |
+---+------------------------------------------------+-----------------+
| 5 | *Textual description of action taken which     | CHART-475       |
| 7 | will include identification information for    |                 |
| 3 | any affected field device and the text of a    | The system      |
|   | DMS message if appropriate*                    | shall store the |
|   |                                                | Textual         |
|   |                                                | description of  |
|   |                                                | action taken    |
|   |                                                | with each       |
|   |                                                | operations log  |
|   |                                                | message.        |
+---+------------------------------------------------+-----------------+
| 3 | ### 3.7.3 Th                                   | CHART-479       |
| 4 | e system shall store operations log entries in |                 |
| 9 |  the database utilized by the service applicat | The system      |
|   | ion (DMS service, etc.) performing the action. | shall have the  |
|   |                                                | capability to   |
|   |                                                | store at least  |
|   |                                                | 14 days of      |
|   |                                                | operations log  |
|   |                                                | entries in the  |
|   |                                                | online system.  |
+---+------------------------------------------------+-----------------+
| 4 | ## 3.8 Banned Word List                        |                 |
| 4 |                                                |                 |
| 5 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.8.1 The system shall check al            | CHART-187       |
| 4 | l DMS messages against a dictionary of banned  |                 |
| 7 | words before sending the message to the field. | The system      |
|   |                                                | shall support   |
|   |                                                | the option of   |
|   |                                                | enabling a      |
|   |                                                | dictionary on   |
|   |                                                | an individual   |
|   |                                                | user basis.     |
|   |                                                |                 |
|   |                                                | CHART-190       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall have the  |
|   |                                                | capability to   |
|   |                                                | check all text  |
|   |                                                | messages on     |
|   |                                                | input against a |
|   |                                                | dictionary      |
|   |                                                | before sending  |
|   |                                                | the message to  |
|   |                                                | the field.      |
|   |                                                |                 |
|   |                                                | CHART-185       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall support a |
|   |                                                | banned words    |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.8.2 The system shall check all DMS me    | CHART-191       |
| 7 | ssages against a dictionary of banned words be |                 |
| 4 | fore storing the message in a message library. | The system      |
|   |                                                | shall have the  |
|   |                                                | capability to   |
|   |                                                | check all text  |
|   |                                                | messages on     |
|   |                                                | input against a |
|   |                                                | dictionary      |
|   |                                                | before storing  |
|   |                                                | the message in  |
|   |                                                | a message       |
|   |                                                | library.        |
|   |                                                |                 |
|   |                                                | CHART-185       |
|   |                                                |                 |
|   |                                                | The system      |
|   |                                                | shall support a |
|   |                                                | banned words    |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+
| 5 | ###                                            | CHART-192       |
| 7 | 3.8.3 The system shall allow an administrator  |                 |
| 5 | to add a new word to the list of banned words. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to add a new    |
|   |                                                | list of words   |
|   |                                                | to a            |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+
| 4 | ### 3.8.4 The                                  | CHART-192       |
| 4 |  system shall allow an administrator to add a  |                 |
| 8 | new list of words to the list of banned words. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to add a new    |
|   |                                                | list of words   |
|   |                                                | to a            |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+
| 4 | ### 3                                          | CHART-193       |
| 4 | .8.5 The system shall allow an administrator t |                 |
| 9 | o remove a word from the list of banned words. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to remove a     |
|   |                                                | word from a     |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+
| 4 | ## 3.9 DMS Message Plans                       |                 |
| 5 |                                                |                 |
| 8 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.9.1 T                                    | CHART-201       |
| 7 | he system shall allow an operator to create a  |                 |
| 6 | DMS message plan which includes the following: | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to create a     |
|   |                                                | plan.           |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.9.1.1 Plan Description                  | CHART-202       |
| 7 |                                                |                 |
| 7 |                                                | The plan shall  |
|   |                                                | include the     |
|   |                                                | plan            |
|   |                                                | description.    |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.9.1.2 One or more of the following:     | CHART-203       |
| 7 |                                                |                 |
| 8 |                                                | The plan shall  |
|   |                                                | include a list  |
|   |                                                | of actions to   |
|   |                                                | implement.      |
+---+------------------------------------------------+-----------------+
| 5 | DMS to display a message on                    | CHART-204       |
| 8 |                                                |                 |
| 6 |                                                | The allowable   |
|   |                                                | plan item       |
|   |                                                | actions shall   |
|   |                                                | include putting |
|   |                                                | a library       |
|   |                                                | message on a    |
|   |                                                | DMS.            |
+---+------------------------------------------------+-----------------+
| 5 | DMS library message to display                 | CHART-204       |
| 8 |                                                |                 |
| 8 |                                                | The allowable   |
|   |                                                | plan item       |
|   |                                                | actions shall   |
|   |                                                | include putting |
|   |                                                | a library       |
|   |                                                | message on a    |
|   |                                                | DMS.            |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.9.2 The system shall a                   | CHART-206       |
| 8 | llow an operator to modify a DMS message plan. |                 |
| 9 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to modify a     |
|   |                                                | plan.           |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.9.3 The system shall a                   | CHART-207       |
| 9 | llow an operator to delete a DMS message plan. |                 |
| 0 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to delete a     |
|   |                                                | plan.           |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.9.4 The system shall                     | CHART-215       |
| 9 |  allow an operator to activate a message plan. |                 |
| 1 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to activate a   |
|   |                                                | plan.           |
+---+------------------------------------------------+-----------------+
| 5 | #### 3.9.4.1 Activati                          | CHART-675       |
| 9 | on of a message plan shall involve activating  |                 |
| 2 | the specified library message on the specified | Upon plan       |
|   |  device for each DMS/Message pair in the plan. | activation the  |
|   |                                                | system shall    |
|   |                                                | sequentially    |
|   |                                                | execute each    |
|   |                                                | plan item.      |
+---+------------------------------------------------+-----------------+
| 4 | ## 3.10 DMS Configuration and Administration   |                 |
| 5 |                                                |                 |
| 9 |                                                |                 |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.10.1 The system s                        | CHART-42        |
| 9 | hall allow an administrator to add a new DMS w |                 |
| 3 | hich communicates via an implemented protocol. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to add a new    |
|   |                                                | device which    |
|   |                                                | communicates    |
|   |                                                | via an          |
|   |                                                | implemented     |
|   |                                                | protocol.       |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.10.2 The system shall all                | CHART-43        |
| 9 | ow an administrator to specify the necessary c |                 |
| 4 | onfiguration information to make a DMS usable. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to specify the  |
|   |                                                | necessary       |
|   |                                                | configuration   |
|   |                                                | information to  |
|   |                                                | make a device   |
|   |                                                | usable.         |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.10.                                      | CHART-45        |
| 9 | 3 The system shall allow an administrator to m |                 |
| 5 | odify the configuration information for a DMS. | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to modify the   |
|   |                                                | configuration   |
|   |                                                | information for |
|   |                                                | a device.       |
+---+------------------------------------------------+-----------------+
| 5 | ### 3.10.4 The system shall allow an           | CHART-46        |
| 9 | administrator to delete a DMS from the system. |                 |
| 6 |                                                | The system      |
|   |                                                | shall allow a   |
|   |                                                | suitably        |
|   |                                                | privileged user |
|   |                                                | to delete a     |
|   |                                                | device from the |
|   |                                                | system.         |
+---+------------------------------------------------+-----------------+
| 7 | #                                              | CHART-676       |
| 7 | ## 3.10.5 The system shall require the adminis |                 |
| 7 | trator to re-enter their password prior to all | The system      |
|   | owing them to view the banned word dictionary. | shall require a |
|   |                                                | user with       |
|   |                                                | privileges to   |
|   |                                                | access the      |
|   |                                                | banned words    |
|   |                                                | dictionary to   |
|   |                                                | re-enter their  |
|   |                                                | password prior  |
|   |                                                | to allowing     |
|   |                                                | them to view    |
|   |                                                | the banned      |
|   |                                                | words           |
|   |                                                | dictionary.     |
+---+------------------------------------------------+-----------------+

# Appendix B -- Document Update History

This appendix contains a history of updates to requirements in this
document.

# Appendix B.1 -- M361-RS-002R1

The following tables detail the changes made in response to comments
received on the CHART II System Requirements Specification Release 1
Build 2. These include changes made in response to comments on R1B1 and
R1B2 requirements only.

+------------------------------------------+-------+-------------------+
| **Changes to R1B1 Requirements**         | **O   | **Comments**      |
|                                          | bject |                   |
|                                          | ID**  |                   |
+==========================================+=======+===================+
| ###### 3.2.2.11.                         | 668   | Added             |
| 1 The system shall immediately blank the |       | "immediately"     |
|  display of a DMS that is set to online. |       |                   |
+------------------------------------------+-------+-------------------+
| ###                                      | 795   | Changed           |
| ## 3.3.1.2.9 The GUI shall provide the c |       | "navigator" to    |
| apability to show the id of each device. |       | "GUI".            |
+------------------------------------------+-------+-------------------+
| ##### 3.3.1.2.10 The GU                  | 796   | Changed           |
| I shall provide the capability to show t |       | "navigator" to    |
| he network connection site for a device. |       | "GUI".            |
+------------------------------------------+-------+-------------------+

+------------------------------------------+-------+------------------+
| **Changes to R1B2 Requirements**         | **O   | **Comments**     |
|                                          | bject |                  |
|                                          | ID**  |                  |
+==========================================+=======+==================+
| Section 2                                |       | Added to list of |
|                                          |       | references.      |
| 14\) MDSHA CHART Software Functional     |       |                  |
| Requirements Document.                   |       |                  |
+------------------------------------------+-------+------------------+
| ##                                       | 562   | Changed "list"   |
| #### 3.1.2.15.1.1 The choices for commun |       | to "choices".    |
| ications types shall include In Service. |       |                  |
+------------------------------------------+-------+------------------+
| ######                                   | 563   | Changed "list"   |
|  3.1.2.15.1.2 The choices for communicat |       | to "choices".    |
| ions types shall include Out of Service. |       |                  |
+------------------------------------------+-------+------------------+
| ##### 3.                                 | 978   | New requirement  |
| 2.1.9.1 All commands to online devices s |       |                  |
| hall be performed through an open event. |       |                  |
+------------------------------------------+-------+------------------+
| ##### 3.2.1.10.3                         | 972   | New requirement  |
|  The system shall restrict certain comma |       |                  |
| nds to devices in maintenance mode only. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.1 \"Re                 | 973   | New requirement  |
| set DMS\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.2 \"Reset HAR con      | 974   | New requirement  |
| troller\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.3 \"Forc               | 975   | New requirement  |
| ed Poll\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.4 \"Setup HAR con      | 976   | New requirement  |
| troller\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.5 \"Rebuild HAR con    | 977   | New requirement  |
| troller\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| #                                        | 994   | New requirement  |
| ##### 3.2.1.10.3.6 \"Set HAR transmitter |       |                  |
|  on/off\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ##                                       | 995   | New requirement  |
| #### 3.2.1.10.3.7 \"Change device config |       |                  |
| uration\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ######                                   | 996   | New requirement  |
| 3.2.1.10.3.8 \"Store message in HAR cont |       |                  |
| roller slot\" (except the immediate mess |       |                  |
| age slot) is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.1                           | 997   | New requirement  |
| 0.3.9 \"Delete message from HAR controll |       |                  |
| er slot\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| ###### 3.2.1.10.3.10 \"Pix               | 998   | New requirement  |
| el test\" is a maintenance mode command. |       |                  |
+------------------------------------------+-------+------------------+
| #                                        | 1000  | New requirement  |
| #### 3.2.1.15.1 The system shall not all |       |                  |
| ow a device to be deleted unless the dev |       |                  |
| ice is first placed in an offline state. |       |                  |
+------------------------------------------+-------+------------------+
| ####                                     | 999   | New requirement  |
| 3.2.2.13 The system shall allow a suitab |       |                  |
| ly privileged user to command a pixel te |       |                  |
| st on a DMS that supports this function. |       |                  |
+------------------------------------------+-------+------------------+
| ##### 3.2.3.22.2 The sys                 | 741   | Modified to      |
| tem shall allow the user to selectively  |       | state that the   |
| place online SHAZAM devices associated w |       | user can         |
| ith a HAR when the HAR is set to online. |       | "selectively"    |
|                                          |       | mark SHAZAM      |
|                                          |       | devices online.  |
+------------------------------------------+-------+------------------+

The following items were added to the glossary:

  -------------------- --------------------------------------------------
  Event                An occurrence or activity of concern to the CHART
                       system and the recording of information about that
                       occurrence or activity.

  Functional Right     The right to perform a specified function.

  Open Event           An event which the CHART system is currently
                       engaged in monitoring or managing.

  Pollable Device      A device that supports returning its status on
                       request.

  Resources            Any of the SHA devices, detectors, and equipment
                       available to the CHART system.

  Role                 A collection of zero or more function rights.
                       Users are assigned roles and thereby obtain
                       functional rights for performing system functions.

  Suitably Privileged  A user with the appropriate functional rights to
  User                 perform an action.
  -------------------- --------------------------------------------------

# Appendix B.2 -- M361-RS-002R2

The following tables detail the changes made in response to comments
received on the CHART II System Requirements Specification.

+------------------------------------------+-------+-------------------+
| **Changes to Requirements**              | **O   | **Comments**      |
|                                          | bject |                   |
|                                          | ID**  |                   |
+==========================================+=======+===================+
| ##### 3.1.2.6.6 The system shall provi   | 1067  | New requirement.  |
| de the capability to automatically resta |       |                   |
| rt selected processes when they go down. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.1.2.18.                          | 901   | Changed           |
| 1 The system shall support the capabilit |       | "construction     |
| y to download EORS lane closure permits. |       | permit" to "lane  |
|                                          |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ##                                       | 903   | Changed           |
| #### 3.1.2.18.1.1 The system shall downl |       | "construction     |
| oad EORS lane closure permit attributes. |       | permit" to "lane  |
|                                          |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ###### 3.1.2.18.                         | 904   | Changed           |
| 1.2 The system shall download EORS lane  |       | "construction     |
| closure permit schedule dates and times. |       | permit" to "lane  |
|                                          |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ###### 3.1.2.18.1.3 The                  | 905   | Changed           |
|  system shall download EORS lane closure |       | "construction     |
|  permits at a system specified interval. |       | permit" to "lane  |
|                                          |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ###### 3.1.2                             | 906   | Changed           |
| .18.1.4 The system shall support a param |       | "construction     |
| eter specifying the number of days of EO |       | permit" to "lane  |
| RS lane closure permit data to retrieve. |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ###### 3.1.2.18                          | 907   | Changed           |
| .1.5 The system shall determine if a con |       | "construction     |
| flict exists between an EORS lane closur |       | permit" to "lane  |
| e permit and a CHART special event item. |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| #######                                  | 908   | Changed           |
|  3.1.2.18.1.5.1 The system shall store l |       | "construction     |
| ane closure permit conflict information  |       | permit" to "lane  |
| with the construction permit attributes. |       | closure permit".  |
+------------------------------------------+-------+-------------------+
| ##                                       | 1068  | New requirement.  |
| ### 3.1.4.2.4 The system shall support t |       |                   |
| he generation of traffic volume reports. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.                                  | 1088  | New requirement.  |
| 1.4.5 The system shall provide an ad hoc |       |                   |
|  reporting capability for archived data. |       |                   |
+------------------------------------------+-------+-------------------+
| ####                                     | 1089  | New requirement.  |
|  3.1.4.6 The system shall provide the ca |       |                   |
| pability for users to customize reports. |       |                   |
+------------------------------------------+-------+-------------------+
| ## 3.2 Device Management                 | 30    | Added CCTV        |
|                                          |       | devices to text.  |
| This section lists requirements for the  |       |                   |
| management and control of CHART remote   |       |                   |
| devices. CHART remote devices consist of |       |                   |
| DMSs, HARs, SHAZAMS, AVL units, CCTV     |       |                   |
| devices, traffic detectors, signals, and |       |                   |
| weather stations.                        |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.2.1.29 Data from de               | 1086  | New requirement.  |
| tection devices shall be made available  |       |                   |
| to requesting systems on an equal basis. |       |                   |
+------------------------------------------+-------+-------------------+
| #####                                    | 1087  | New requirement.  |
| 3.2.1.29.1 Servicing a request for detec |       |                   |
| tion data from one system shall not affe |       |                   |
| ct the data requested by another system. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.2.1.30 The system                 | 1090  | New requirement.  |
| shall provide a capability for users to  |       |                   |
| exercise specified system functions with |       |                   |
| out affecting operational field devices. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.2.1.30.1 The system shall provid | 1091  | New requirement.  |
| e the capability for a user to perform D |       |                   |
| MS-related functions on a simulated DMS. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.2.5.3                             | 1069  | New requirement.  |
| The system shall provide the capability  |       |                   |
| to assess the validity of detector data. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.2.5.3.1 The system shall deter   | 1070  | New requirement.  |
| mine the validity of loop detector data. |       |                   |
+------------------------------------------+-------+-------------------+
| #                                        | 1071  | New requirement.  |
| ### 3.3.2.6 The map display shall suppor |       |                   |
| t the display of independent map layers. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.2.6.1                          | 1072  | New requirement.  |
|  The map display shall support a base ma |       |                   |
| p layer showing major Maryland highways. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.2.6.2 The map d                | 1073  | New requirement.  |
| isplay shall support a device map layer. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.2.6.3 The map di               | 1074  | New requirement.  |
| splay shall support a weather map layer. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.2.6.4 The map disp             | 1075  | New requirement.  |
| lay shall support an incident map layer. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.2.6.5 The map display          | 1076  | New requirement.  |
|  shall support a lane closure map layer. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.3.                               | 1077  | New requirement.  |
| 2.6.6 The map display shall provide the  |       |                   |
| capability for the user to filter a map  |       |                   |
| layer in order to customize the display. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.4.2.5.2 The system shall         | 1066  | New requirement.  |
|  support a message attribute indicating  |       |                   |
| that a message is sign-specific and is o |       |                   |
| nly to be displayed on a specified sign. |       |                   |
+------------------------------------------+-------+-------------------+
| ##                                       | 1078  | New requirement.  |
| #### 3.5.1.1.2.3 The allowable plan item |       |                   |
|  actions shall include sending an email. |       |                   |
+------------------------------------------+-------+-------------------+
| ###### 3.5.1.1.2.4 The allowable plan it | 1079  | New requirement.  |
| em actions shall include sending a page. |       |                   |
+------------------------------------------+-------+-------------------+
| ###### 3.5.1.1.2.5 The allowable plan i  | 1080  | New requirement.  |
| tem actions shall include sending a fax. |       |                   |
+------------------------------------------+-------+-------------------+
| #####                                    | 1081  | New requirement.  |
| # 3.5.1.1.2.6 The allowable plan item ac |       |                   |
| tions shall include generating a report. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.6.1.4 The system shall provid     | 1082  | New requirement.  |
| e the capability to evaluate probe data. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.6.1.5                             | 1083  | New requirement.  |
| The system shall provide the capability  |       |                   |
| to evaluate vehicle classification data. |       |                   |
+------------------------------------------+-------+-------------------+
| #### 3.9.2.2 The CHART I                 | 770   | Modified to       |
| I system shall support a failover capabi |       | remove "without   |
| lity whereby operations at one location  |       | loss of           |
| can be transferred to a second location. |       | functionality".   |
+------------------------------------------+-------+-------------------+
| #### 3.9.2.3 The CHART II syst           | 1084  | New requirement.  |
| em shall support distributed operations. |       |                   |
+------------------------------------------+-------+-------------------+
| ##### 3.9.2.3                            | 1085  | New requirement.  |
| .1 The CHART II system shall include mul |       |                   |
| tiple locations capable of performing al |       |                   |
| l CHART functions (excluding archiving). |       |                   |
+------------------------------------------+-------+-------------------+

# Acronyms

CHART Coordinated Highways Action Response Team

COTS Commercial-Off-The-Shelf

CSC Computer Sciences Corporation

DMS Dynamic Message Sign

EORS Emergency Operations Reporting System

ERU/ETP Emergency Response Unit/ Emergency Traffic Patrol

FITM Freeway Incident Traffic Management

FMS Field Management Station

GUI Graphical User Interface

HAR Highway Advisory Radio

ITS Intelligent Transportation System

NTCIP National Transportation Communications for ITS Protocol

RFP Request for Proposal

TSR Telecommunications Service Request

VRT Vehicle Recovery Tech

# Glossary

  ------------------ ----------------------------------------------------
  Logical Site       A conceptual division of a physical site. A physical
                     site may contain 0 or more logical sites.

                     

  Event              An occurrence or activity of concern to the CHART
                     system and the recording of information about that
                     occurrence or activity.

                     

  Functional Right   The right to perform a specified function.

                     

  Open Event         An event which the CHART system is currently engaged
                     in monitoring or managing.

                     

  Owner              A static property that defines the organization who
                     owns the hardware.

                     

  Physical Site      The actual geographic location where a resource is
                     located.

                     

  Pollable Device    A device that supports returning its status on
                     request.

                     

  Resources          Any of the SHA devices, detectors, and equipment
                     available to the CHART system.

                     

  Responsible        The operations center that is currently responsible
  Operations Center  for the management of a device.

                     

  Role               A collection of zero or more function rights. Users
                     are assigned roles and thereby obtain functional
                     rights for performing system functions.

                     

  Suitably           A user with the appropriate functional rights to
  Privileged User    perform an action.
  ------------------ ----------------------------------------------------