**TENNESSEE DEPARTMENT OF TRANSPORTATION**

**REGION 3 -- NASHVILLE**

***Transportation Management Center Operations Policy Manual***

**DRAFT**

27 December 2002

![](media/image1.png){width="6.496527777777778in" height="4.33125in"}

**Prepared by:**

**PB Farradyne,**

**PB Alltech, Inc.,**

**And**

**Gresham Smith & Partners**

[]{#__RefHeading___Toc25378168 .anchor}*Transportation Management Center
Operations Policy Manual*

**Table of Contents**

[Topic]{.underline} [Page]{.underline}

*Transportation Management Center Operations Policy Manual*
[2](#__RefHeading___Toc25378168)

1 INTRODUCTION [5](#introduction)

2 EMERGENCY AND OTHER CONTACT NUMBERS
[6](#emergency-and-other-contact-numbers)

3 GENERAL POLICIES [9](#general-policies)

3.1 Update Status and Record [9](#update-status-and-record)

3.2 Change Policy [12](#change-policy)

3.3 Visitor and Tour Policy [12](#visitor-and-tour-policy)

3.4 ATMS Hardware and Software [12](#atms-hardware-and-software)

3.4.1 General Equipment [12](#general-equipment)

3.4.2 Operator Specific Equipment [13](#operator-specific-equipment)

3.4.3 General TMC Property [13](#general-tmc-property)

3.4.4 Telephone and Fax Usage [13](#telephone-and-fax-usage)

3.5 TMC Cleaning and Maintenance [13](#tmc-cleaning-and-maintenance)

3.6 Pass Keys and Controlled Access
[13](#pass-keys-and-controlled-access)

3.7 MIST™ Software [13](#mist-software)

3.8 Building Security and Parking [14](#building-security-and-parking)

3.9 Staff Meetings [14](#staff-meetings)

3.10 Smoking Policy [14](#smoking-policy)

3.11 Uniform and Dress Code [14](#uniform-and-dress-code)

3.12 Drug-Free Workplace [15](#drug-free-workplace)

3.13 Breaks and Lunch [15](#breaks-and-lunch)

3.14 Work Shifts, Organization Chart and Training
[15](#work-shifts-organization-chart-and-training)

3.15 Incident Command System [16](#incident-command-system)

3.16 Homeland Security [16](#homeland-security)

3.17 Severe Weather Conditions [16](#severe-weather-conditions)

4 DAILY OPERATION [16](#daily-operation)

4.1 Management Center Functions [16](#management-center-functions)

4.2 Personnel [16](#personnel)

4.3 Hours of Operation [17](#hours-of-operation)

4.4 Staffing [17](#staffing)

4.5 After Hours On-Call Roster [17](#after-hours-on-call-roster)

4.6 Remote Operation [17](#remote-operation)

4.7 Security Policy [18](#security-policy)

4.8 Maintenance Checklist [18](#maintenance-checklist)

4.9 Startup/Shutdown [18](#startupshutdown)

4.10 Failure Recovery [18](#failure-recovery)

4.11 Agency/Jurisdictional Contacts [18](#agencyjurisdictional-contacts)

4.12 Telephone Call Etiquette and Notification Policy
[19](#telephone-call-etiquette-and-notification-policy)

4.13 Contact with Media and the Public
[19](#contact-with-media-and-the-public)

4.14 Coordination with HELP Program
[19](#coordination-with-help-program)

4.15 Dispatch of HELP Vehicles [19](#dispatch-of-help-vehicles)

5 CONTROL SYSTEM OPERATION POLICIES
[20](#control-system-operation-policies)

5.1 Operator Interface [20](#operator-interface)

5.2 Operational Procedures [20](#operational-procedures)

5.3 Incident Management [20](#incident-management)

5.3.1 Incident Classification Policy
[20](#incident-classification-policy)

5.3.2 Incident Response [21](#incident-response)

5.3.3 Incident Detours [21](#incident-detours)

5.3.4 Incident Information [21](#incident-information)

5.3.5 Incident Tracking [21](#incident-tracking)

5.3.6 Data Entry [22](#data-entry)

5.3.7 Incident Paging and Call-Out [22](#incident-paging-and-call-out)

5.3.8 Post Incident De-briefs [22](#post-incident-de-briefs)

6 MAINTENANCE POLICY [22](#maintenance-procedures)

6.1 Routine Maintenance [22](#routine-maintenance)

6.2 Preventative Maintenance [22](#preventative-maintenance)

6.3 Spare/Backup Equipment [22](#sparebackup-equipment)

6.4 Emergency [23](#emergency)

6.5 Contract Maintenance [23](#contract-maintenance)

7 SYSTEM OPERATION LOGS [23](#system-operations-logs)

7.1 Operations [23](#operations)

7.2 Maintenance [23](#maintenance)

7.3 Events [23](#events)

7.4 System Reports [23](#system-reports)

7.5 Traffic Data [23](#traffic-data)

7.6 Risk Management [23](#risk-management)

8 OPERATIONAL CONCEPTS [23](#operational-concepts)

8.1 Traffic Monitoring [23](#traffic-monitoring)

8.1.1 Speed Detector Monitoring and Response
[24](#speed-detector-monitoring-and-response)

8.1.2 CCTV Image Viewing [24](#cctv-image-viewing)

8.1.3 Video Wall [24](#video-wall)

8.1.4 Video Sequences [24](#video-sequences)

8.1.5 Recording Video Images [24](#recording-video-images)

8.1.6 Road Construction Monitoring [25](#road-construction-monitoring)

8.1.7 Road Construction Reporting [25](#road-construction-reporting)

8.1.8 Diversion Route Planning [25](#diversion-route-planning)

8.1.9 Highway Maintenance Activity [25](#highway-maintenance-activity)

8.2 Traffic Response [25](#traffic-response)

8.2.1 Use of Dynamic Message Signs (DMS)
[26](#use-of-dynamic-message-signs-dms)

8.2.2 Operation of DMS by Law Enforcement Personnel
[26](#operation-of-dms-by-law-enforcement-personnel)

8.2.3 Blank Signs [26](#blank-signs)

8.2.4 Messages during Peak Periods [26](#messages-during-peak-periods)

8.2.5 Display of Upcoming Roadwork [26](#display-of-upcoming-roadwork)

8.2.6 Display of Upcoming Special Events that Adversely Affect Travel
[27](#display-of-upcoming-special-events-that-adversely-affect-travel)

8.2.7 Display of Travel Times [27](#display-of-travel-times)

8.2.8 Traffic Diversion (General) [27](#traffic-diversion-general)

8.2.9 Traffic Diversion (Full Highway Closure)
[27](#traffic-diversion-full-highway-closure)

8.2.10 Traffic Diversion to Roadways Not Under the Jurisdiction of TDOT
[27](#traffic-diversion-to-roadways-not-under-the-jurisdiction-of-tdot)

8.2.11 DMS Messages for Adverse Weather, Environmental, and Roadway
Conditions
[28](#dms-messages-used-for-adverse-weather-environmental-and-roadway-conditions)

8.2.12 Limits of DMS Influence for Incidents
[28](#limits-of-dms-influence-for-incidents)

8.2.13 DMS Message Priority [28](#dms-message-priority)

8.2.14 Other DMS [28](#other-dms)

8.2.15 DMS Message Confirmation [28](#dms-message-confirmation)

8.2.16 Use of Highway Advisory Radio (HAR)
[29](#use-of-highway-advisory-radio-har)

8.2.17 HAR Messages [29](#har-messages)

8.2.18 HAR Message Format [29](#har-message-format)

8.2.19 HAR Message Confirmation [29](#har-message-confirmation)

8.3 Miscellaneous Concepts and Policy
[29](#miscellaneous-concepts-and-policy)

8.3.1 Media/Interagency Image Requests
[29](#mediainteragency-image-requests)

8.3.2 Web Site Images [30](#web-site-images)

8.3.3 DMS for Special Events [30](#dms-for-special-events)

8.3.4 DMS Regulatory Speed Messages [30](#dms-regulatory-speed-messages)

8.3.5 Advertising [30](#advertising)

8.3.6 Public Service Announcements [30](#public-service-announcements)

8.3.7 Display of Amber Alerts [31](#display-of-amber-alerts)

8.3.8 Intermodal Information [31](#inter-modal-information)

8.3.9 DMS Test Messages [31](#dms-test-messages)

8.3.10 Ramp Metering [31](#ramp-metering)

8.4 Data Analysis And Warehousing [32](#data-analysis-and-warehousing)

8.5 Interagency and Inter- Jurisdictional Coordination
[32](#interagency-and-inter--jurisdictional-coordination)

9 CONTROL CENTER DESCRIPTION/SYSTEM FIELD DEVICES
[32](#control-center-description-system-field-devices)

9.1 Location [32](#location)

9.2 Access/Security [32](#accesssecurity)

9.3 Layout [33](#layout)

9.4 Fire Suppression [33](#fire-suppression)

9.5 Power Source/Location [33](#power-sourcelocation)

9.6 HV/AC [33](#hvac)

9.7 Data Communications [33](#data-communications)

9.8 Voice Communications [33](#voice-communications)

9.9 Network Communications [33](#network-communications)

9.10 Field Device Descriptions [33](#field-device-descriptions)

10 SYSTEM DOCUMENTATION [33](#system-documentation)

# INTRODUCTION

This document is a high-level gathering of operational policies that
have been created and approved by the Tennessee Department of
Transportation (TDOT) for the TDOT, Region 3 Transportation Management
Center (TMC) serving the Nashville Metropolitan Area. The policies
described in this manual are divided into functional area/grouping.

Since this document is a living document and policies will change over
time based on conditions found in effect at the time the policy was
written, the individual policies have been numbered for tracking
purposes. During the Policy Manual and Operations Manual update cycles
(Quarterly or as directed by TDOT) each manual will be reviewed and
updated as required. The responsible person for making and monitoring
the updates is the operation manager acting under the direction of the
TMC manager. This document is set up so that the last two updates can be
tracked. This will ensure that revisions to each policy are documented
and the most current edition of this document is being utilized. A
summary table follows this section and will be the first place to look
when checking on the status of the current policies.

All policies contained in this document have been reviewed and approved
by TDOT management. Any changes, additions or deletions of policies
noted in the document have received TDOT approval before they were
printed and included in this manual. This manual deals with global
policy, more specific operational details can be found in the Operations
Manual and also the MIST™ User's Manual, these manuals contain specific
Operational Procedures for daily operations, control of specific
devices, etc.

The following individuals have been involved in the creation of this
manual:

-   Mr. Paul Degges -- Region 3 Director, TDOT

```{=html}
<!-- -->
```
-   Mr. Ali Farhangi -- TMC Manager, TDOT

```{=html}
<!-- -->
```
-   Mr. Don Dahlinger -- ITS Program Manager, TDOT

-   Mr. Bill Jacobs -- Incident Management, TDOT

-   Mr. Frank Horn -- Incident Management, TDOT

-   Mr. Gary Ogletree -- Incident Management, TDOT

-   Mr. Mike Tugwell -- Highway Maintenance, TDOT

-   Mr. Michael Smart -- ITS Engineer, FHWA

-   Mr. Walter Kraft, Vice President, PB Farradyne

```{=html}
<!-- -->
```
-   Mr. Kenny Voorhies -- Project Manager, PB Farradyne

-   Mr. H. Gupta Borra -- Project Engineer, PB Farradyne

```{=html}
<!-- -->
```
-   Mr. Wayne White -- Project Manager, PB Alltech

```{=html}
<!-- -->
```
-   Mr. Cliff Conklin -- Operations Manager, PB Alltech

-   Mr. Rodney Chester -- ITS Engineer, Gresham Smith & Partners

# Emergency And Other Contact Numbers

Cliff Conklin 615-350-3437 Office

Operations Manager 615-542-4360 Cell

615-539-0926 Pager

615-799-6079 Home

Ali Farhangi 615-350-4189 Office

TMC Manager 615-405-7778 Cell

1-888-365-1552 Pager

615-373-7398 Home

Gary Ogletree 615-350-4272 Office

HELP Supervisor 615-aaa-bbbb Cell

615-aaa-bbbb Pager

615-aaa-bbbb Home

Paul Deggs 615-350-4300 Office

Region Director 615-aaa-bbbb Cell

615-aaa-bbbb Pager

615-aaa-bbbb Home

TDOT Public Affairs Office 615-741-2331 Office

Public Information Officer 615-aaa-bbbb Cell

615- aaa-bbbb Pager

Kenneth Haile 615- aaa-bbbb Office

Regional Maintenance Supervisor 615- aaa-bbbb Cell

615- aaa-bbbb Pager

Jerry Cato 615- aaa-bbbb Office

Regional Construction Supervisor 615- aaa-bbbb Cell

615- aaa-bbbb Pager

Mike Brown 615-350-4333 Office

Assistant Regional Traffic Engineer 615- aaa-bbbb Cell

615- aaa-bbbb Pager

Mark Smith 615-350-3428 Office

Shift Supervisor #1 128 Intercom

615-708-5865 Cell

615-aaa-bbbb Pager

615-672-5865 Home

Cory Mock 615-350-3427 Office

Shift Supervisor #2 127 Intercom

615-aaa-bbbb Cell

615-aaa-bbbb Pager

615-599-8199 Home

Fred Littrell 615-350-3323 Office

Shift Supervisor #3 (PT) 119 Intercom

615-aaa-bbbb Cell

615-aaa-bbbb Pager

270-586-5751 Home

Operator Console Position #1 615-350-3423 Console

Shift Supervisor Duty Position 120 Intercom

Operator Console Position #2 615-350-3424 Console

FT Operator Position 124 Intercom

Operator Console Position #3 615-350-3425 Console

Peak Hour Operator Position 125 Intercom

Operator Console Position #4 615-350-3426 Console

Operations Manager Position 126 Intercom

HELP Dispatcher #1 615-350-4344 Console

Dispatcher #1 003 Intercom

HELP Dispatcher #2 615-350-4511 Console

002 Intercom

HELP Dispatcher #3 615-350-4540 Console

008 Intercom

MIST™ Help Desk 1-800-aaa-bbbb

David Fields 615-350-4370 Office

TDOT IT Support 615-aaa-bbbb Cell

TDOT IT Help Desk 615-350-4581 During Work Hours

615-aaa-bbbb After Work Hours

Paul Sexton 615-350-4377 Office

TDOT Bldg. Maintenance 615-aaa-bbbb Cell

Carolyn Carter 615-401-4213 Office

BellSouth Project Manager 1-877-920-2424 Pager

***Other Agencies (Metro, Transit, Towing, County, City, etc.)***

Break Room 615-350-3368

Large Conference Room 615-350-3436

121 Intercom

Small Conference Room 615-350-

000 Intercom

# general policies

## Update Status and Record

The following Table is to be maintained and updated as changes are made
to policy and procedures noted in this manual.

  ---------- ---------- ----------- ---------------------------------------
  CURRENT    LAST       POLICY IDEX POLICY TITLE
  REVISION   REVISION   NUMBER      
  DATE       DATE                   

  26 Dec 02  24 Nov 02  2.0         Emergency Contact List

  26 Dec 02  24 Nov 02  3.1         Update Status and Record

  26 Dec 02  24 Nov 02  3.2         Change Policy

  26 Dec 02  24 Nov 02  3.3         Visitor and Tour Policy

  26 Dec 02  24 Nov 02  3.4         ATMS Hardware and Software

  26 Dec 02  24 Nov 02  3.4.1       General Equipment

  26 Dec 02  24 Nov 02  3.4.2       Operator Specific Equipment

  26 Dec 02  24 Nov 02  3.4.3       General TMC Property

  26 Dec 02  24 Nov 02  3.4.4       Telephone and Fax Usage

  26 Dec 02  24 Nov 02  3.5         TMC Cleaning and Maintenance

  26 Dec 02  24 Nov 02  3.6         Pass Keys and Controlled Access

  26 Dec 02  24 Nov 02  3.7         MIST™ Software

  26 Dec 02  24 Nov 02  3.8         Building Security and Parking

  26 Dec 02  24 Nov 02  3.9         Staff Meetings

  26 Dec 02  24 Nov 02  3.10        Smoking Policy

  26 Dec 02  24 Nov 02  3.11        Uniform and Dress Code

  26 Dec 02  24 Nov 02  3.12        Drug-Free Workplace

  26 Dec 02  24 Nov 02  3.13        Breaks and Lunch

  26 Dec 02  24 Nov 02  3.14        Work Shifts, Organization Chart and
                                    Training

  26 Dec 02  24 Nov 02  3.15        Incident Command System

  26 Dec 02  24 Nov 02  3.16        Homeland Security

  26 Dec 02  24 Nov 02  3.17        Severe Weather Conditions

  26 Dec 02  24 Nov 02  4.0         Daily Operations

  26 Dec 02  24 Nov 02  4.1         Management Center Functions

  26 Dec 02  24 Nov 02  4.2         Personnel

  26 Dec 02  24 Nov 02  4.3         Hours of operation

  26 Dec 02  24 Nov 02  4.4         Staffing

  26 Dec 02  24 Nov 02  4.5         After Hours On-Call Roster

  26 Dec 02  24 Nov 02  4.6         Remote Operation

  26 Dec 02  24 Nov 02  4.7         Security Procedures

  26 Dec 02  24 Nov 02  4.8         Maintenance Checklist

  26 Dec 02  24 Nov 02  4.9         Startup / Shutdown

  26 Dec 02  24 Nov 02  4.10        Failure Recovery

  26 Dec 02  24 Nov 02  4.11        Agency / Jurisdictional Contacts

  26 Dec 02  24 Nov 02  4.12        Telephone Call Etiquette & Notification
                                    Procedures

  26 Dec 02  24 Nov 02  4.13        Contact with Media and the Public

  26 Dec 02  24 Nov 02  4.14        Coordination with HELP Program

  26 Dec 02  24 Nov 02  4.15        Dispatch of HELP Vehicles

  26 Dec 02  24 Nov 02  5.0         Control System Operational Procedures

  26 Dec 02  24 Nov 02  5.1         Operator Interface

  26 Dec 02  24 Nov 02  5.2         Operational Procedures

  26 Dec 02  24 Nov 02  5.3         Incident Management

  26 Dec 02  24 Nov 02  5.3.1       Incident classification Policy

  26 Dec 02  24 Nov 02  5.3.2       Incident Response

  26 Dec 02  24 Nov 02  5.3.3       Incident Detours

  26 Dec 02  24 Nov 02  5.3.4       Incident Information

  26 Dec 02  24 Nov 02  5.3.5       Incident Tracking

  26 Dec 02  24 Nov 02  5.3.6       Data Entry

  26 Dec 02  24 Nov 02  5.3.7       Incident Paging and Call-Out

  26 Dec 02  24 Nov 02  5.3.8       Post Incident De-briefs

  26 Dec 02  24 Nov 02  6.0         Maintenance Procedures

  26 Dec 02  24 Nov 02  6.1         Routine Maintenance

  26 Dec 02  24 Nov 02  6.2         Preventative Maintenance

  26 Dec 02  24 Nov 02  6.3         Spare / Backup Equipment

  26 Dec 02  24 Nov 02  6.4         Emergency

  26 Dec 02  24 Nov 02  6.5         Contract Maintenance

  26 Dec 02  24 Nov 02  7.0         System Operations Logs

  26 Dec 02  24 Nov 02  7.1         Operations

  26 Dec 02  24 Nov 02  7.2         Maintenance

  26 Dec 02  24 Nov 02  7.3         Events

  26 Dec 02  24 Nov 02  7.4         System Reports

  26 Dec 02  24 Nov 02  7.5         Traffic Data

  26 Dec 02  24 Nov 02  7.6         Risk Management

  26 Dec 02  24 Nov 02  8.0         Operational Concepts

  26 Dec 02  24 Nov 02  8.1         Traffic Monitoring

  26 Dec 02  24 Nov 02  8.1.1       Speed Detector Monitoring and Response

  26 Dec 02  24 Nov 02  8.1.2       CCTV Image Viewing

  26 Dec 02  24 Nov 02  8.1.3       Video Wall

  26 Dec 02  24 Nov 02  8.1.4       Video Sequences

  26 Dec 02  24 Nov 02  8.1.5       Recording Video Images

  26 Dec 02  24 Nov 02  8.1.6       Road Construction Monitoring

  26 Dec 02  24 Nov 02  8.1.7       Road Construction Reporting

  26 Dec 02  24 Nov 02  8.1.8       Diversion Route Planning

  26 Dec 02  24 Nov 02  8.1.9       Highway Maintenance Activity

  26 Dec 02  24 Nov 02  8.2         Traffic Response

  26 Dec 02  24 Nov 02  8.2.1       Use of Dynamic Message Signs (DMS)

  26 Dec 02  24 Nov 02  8.2.2       Operation of DMS by Law Enforcement
                                    Personnel

  26 Dec 02  24 Nov 02  8.2.3       Blank Signs

  26 Dec 02  24 Nov 02  8.2.4       Messages during Peak Periods

  26 Dec 02  24 Nov 02  8.2.5       Display of Upcoming Roadwork

  26 Dec 02  24 Nov 02  8.2.6       Display of Upcoming Special Events

  26 Dec 02  24 Nov 02  8.2.7       Display of Travel Times

  26 Dec 02  24 Nov 02  8.2.8       Traffic Diversion (General)

  26 Dec 02  24 Nov 02  8.2.9       Traffic Diversion (Full Closure)

  26 Dec 02  24 Nov 02  8.2.10      Traffic Diversion to Other Roadways

  26 Dec 02  24 Nov 02  8.2.11      DMS Messages for Adverse Weather

  26 Dec 02  24 Nov 02  8.2.12      Limits of DMS Influence for Incidents

  26 Dec 02  24 Nov 02  8.2.13      DMS Message Priority

  26 Dec 02  24 Nov 02  8.2.14      Other DMS

  26 Dec 02  24 Nov 02  8.2.15      DMS Message Confirmation

  26 Dec 02  24 Nov 02  8.2.16      Use of Highway Advisory Radio (HAR)

  26 Dec 02  24 Nov 02  8.2.17      HAR Messages

  26 Dec 02  24 Nov 02  8.2.18      HAR Message Format

  26 Dec 02  24 Nov 02  8.2.19      HAR Message Confirmation

  26 Dec 02  24 Nov 02  8.3         Miscellaneous Concepts and Policy

  26 Dec 02  24 Nov 02  8.3.1       Media/Interagency Image Requests

  26 Dec 02  24 Nov 02  8.3.2       Web Site Images

  26 Dec 02  24 Nov 02  8.3.3       DMS for Special Events

  26 Dec 02  24 Nov 02  8.3.4       DMS Regulatory Speed Messages

  26 Dec 02  24 Nov 02  8.3.5       Advertising

  26 Dec 02  24 Nov 02  8.3.6       Public Service Announcements

  26 Dec 02  24 Nov 02  8.3.7       Display of Amber Alerts

  26 Dec 02  24 Nov 02  8.3.8       Inter-modal Information

  26 Dec 02  24 Nov 02  8.3.9       DMS Test Messages

  26 Dec 02  24 Nov 02  8.3.10      Ramp Metering

  26 Dec 02  24 Nov 02  8.4         Data Analysis and Warehousing

  26 Dec 02  24 Nov 02  8.5         Interagency and Inter- Jurisdictional
                                    Coordination

  26 Dec 02  24 Nov 02  9.0         Control Center Description / System
                                    Field Devices

  26 Dec 02  24 Nov 02  9.1         Location

  26 Dec 02  24 Nov 02  9.2         Access / Security

  26 Dec 02  24 Nov 02  9.3         Layout

  26 Dec 02  24 Nov 02  9.4         Fire Suppression

  26 Dec 02  24 Nov 02  9.5         Power Source / Location

  26 Dec 02  24 Nov 02  9.6         HV/AC

  26 Dec 02  24 Nov 02  9.7         Data Communications

  26 Dec 02  24 Nov 02  9.8         Voice Communications

  26 Dec 02  24 Nov 02  9.9         Network Communications

  26 Dec 02  24 Nov 02  9.10        Field Device Descriptions

  26 Dec 02  24 Nov 02  10.0        System Documentation

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

## Change Policy

The purpose of this specific policy is to recognize that the policies
and procedures that govern the operation of the TMC will change as the
system is used and deployed in new geographic areas. The new policy to
be created or the existing policy to be changed will be documented and
presented to TDOT for review and approval. When the policy is accepted
as written, then TDOT will provide a brief, informal written acceptance
for the operations historical file and the policy will be added to this
manual. If the policy is not acceptable as written, then the person(s)
presenting the policy will meet with TDOT to modify the policy for
future approval or file the policy with a non-concurrence decision. It
is expected that the Operations Manual will be reviewed and updated at
least on a quarterly basis. The responsibility for making these updates
and changes to policy and procedure is found with the operations manager
and the TMC manager.

## Visitor and Tour Policy

The TDOT ITS program is just beginning and it is expected that numerous
visitors will require meetings with TMC staff members and that requests
for tours of the TMC will occur almost daily. Past experience with other
states has shown that numerous groups, ranging from local Boy Scout
Troops to Federal Authorities, will request scheduled tours and
unscheduled tours will happen also of the TMC. The administrative
assistant assigned to the front desk will be the initial contact person
for these individuals and groups when they arrive at the TMC. The
administrative assistant will introduce themselves to the group and ask
them to remain in the lobby area and contact the person who will be
meeting the visitor(s)/tour group and then return to other assigned
duties after the visitor(s) have met their staff contact. Generally the
TDOT TMC manager, the operations manager or the shift supervisor on
duty, will conduct tours. The length and coverage of the tour is at the
discretion of the tour conductor, however, the tour will be responsive
to the audience. All TMC staff members will be pleasant and thoughtful
of visitors and will conduct themselves in a professional manner at all
times.

## ATMS Hardware and Software

All hardware/software connected to the ATMS is for the exclusive use of
TDOT in conducting ITS related work. Use of ATMS equipment not related
to the regional ITS/transportation program shall not be allowed. The
primary point of abuse under this policy will be the ATMS workstations,
which potentially could be used for purposes other than ATMS work. No
unauthorized software or hardware shall be connected to or installed on
any ATMS equipment. Authorization for installation of additional
hardware/software must come through TDOT. Technical clarification on
specific items may also be required from TDOT personnel, and
installation of all such hardware/software items shall be conducted by
TDOT personnel or by an authorized contracted service at the discretion
of the TDOT. This policy is to protect the system from viruses, from
overloading, and to protect the agency from any software licensing
liability concerns. In general, software needs should be addressed to
the ATMS network administrators.

### General Equipment

TDOT may assign equipment, such as two-way radios, pagers, computers,
cell phone devices, etc to operators, shift supervisors and others
responsible for TMC operations. It is the responsibility of the
individual to safeguard, maintain and protect all of their assigned
equipment from inappropriate use, abuse or theft. This equipment shall
be returned to TDOT in the event of termination, transfer or other
condition where the individual no longer has an official need for the
equipment.

### Operator Specific Equipment

The TDOT will provide an operator console work location which includes a
computer workstation/software. This equipment is the property of TDOT
and no software will be installed without TDOT permission. Internet
access will be in strict accordance with the written TDOT policy, "TDOT
Policy on Use of the Internet"; a copy will be provided for each
individual. Individuals will be required to read and sign a statement
that acknowledges they will follow the guidelines stated in this policy
and will use this Internet access for official use only. This equipment
will not be used to "surf" the Internet, play games or act in an
inappropriate manner.

### General TMC Property

The TDOT has provided a clean, neat work facility. It is the
responsibility of all TMC employees to keep the TMC neat and clean. The
operator workstations, copy room, break room and restrooms will be kept
clean and neat at all times. It is everyone's responsibility to clean up
after himself or herself. No food or drinks will be allowed at the
console workstations at any time.

### Telephone and Fax Usage

The telephones and fax machines provided by TDOT are the property of
TDOT and shall be utilized for official communications only. It is
understood that telephones and fax machines may be needed for personal
communications between spouses and parents and children occasionally to
coordinate child-care or other non-work related activity, but this must
be limited to the absolute minimum and not abused. Inappropriate use or
abuse of this equipment will not be tolerated and repeated abuse of this
policy could be grounds for termination.

## tmc cleaning and maintenance

All cleaning and building maintenance (including generator testing and
similar activities) will be coordinated through the operations manager
and the TDOT TMC Manager. The operational nature of the TMC requires
special attention be paid to any work to be performed as well as the
time when the work can be performed. All work to be conducted on the
operations floor will be coordinated through the operations manager or
shift supervisor on duty. No cleaning or maintenance will be conducted
during peak rush hour periods or while serious incidents are being
handled.

## Pass keys and controlled access

The operations room located on the first floor of the TMC is a secure
area and entrance requires the use of an electronic door passkey. No
keys will be issued to non-operational personnel. For visitors and other
personnel to enter the control room, communications room or equipment
maintenance room they will be required to contact the administrative
assistant or call the shift supervisor for access. If the operational
situation allows, the visitor or maintenance worker will be given entry
to the control room. If you lose your electronic passkey and/or standard
door key (if issued), immediately notify your supervisor so the card can
be deactivated and you will be charged \$5.00 for a replacement card.

## mist™ software

The MIST™ control software and database systems shall be copied to a
tertiary media format and backed-up once per day by operations staff. No
other personnel shall attempt to backup any portion of the ATMS on their
own, nor attempt to re-install any portion of the ATMS from a tertiary
or backup source. The backup process for the MIST™ Software system is
automated and is run as required. System administrators at the PB
Farradyne Helpdesk should be contacted with any questions regarding
system backup or re-installation of some portion of the system.
Operations Status Reports are to be generated on a monthly basis and
distributed to select staff members of TDOT and the TMC. This activity
is the responsibility of the TMC operations manager and the shift
supervisors. This report is submitted to the TDOT TMC Manager by the
second week of each month, presenting the previous month's operational
statistics.

## building security and parking

The operators and others working and using the TMC should feel secure in
their work environment. The method used to provide initial security is
conducted with TDOT personnel staffing the main gate at the entrance to
the facility. Second level security is done by placing an administrative
assistant who acts as a receptionist in the TMC building lobby during
normal work hours to greet individuals wishing to enter the building and
a pass key system is in place for the operations floor. The parking lot
is located on the TDOT complex and parking is afforded the same level of
security as other TDOT employees, including the HELP Program dispatchers
and vehicle operators who work during the same operational time periods.

Bomb Threats or similar threats to the staff and/or facility will be
handled utilizing the existing TDOT procedures. In the event the
procedure does not cover the crisis, the senior staff person on duty
shall take care of the staff and take action necessary for their
protection using sound, logical judgement. The Metro 911 center should
be called as quickly as possible to handle an emergency and the
operations manager and the TDOT TMC manager should be called
immediately.

## staff meetings

It is expected that weekly staff meetings will be conducted to keep the
operational and administrative staff informed regarding activities at
the TMC and within the TDOT ITS program. It is expected that this
meeting will be conducted on Wednesday's during the middle of the day
when the TDOT TMC Manager, the operations manager and the two weekday
shift supervisors will be present. It will be the responsibility of the
operations manager to brief the weekend shift supervisor of any changes
in operational policy or procedures.

## Smoking Policy

The smoking policy in effect for TDOT employees is in effect for TMC
employees. There will be no smoking in, near or around the TMC building.
Smoking is allowed in the smoking area located in the main complex
building's "smoking area". Smokers will not be afforded extra break time
to smoke in excess of the normally allowed times. Additional detail can
be provided upon request.

## Uniform and Dress code

Dress for all TMC personnel on the operations floor will be professional
and appropriate for the work environment. Generally the TDOT dress code
rules will apply. The operations staff will be provided collared shirts
(polo style) with the TDOT logo to wear on duty. Employees will be
required to wear khaki style or dress style clothing and dress shoes.
Sneakers and denim jeans are not allowed unless a dress down day is
authorized in advance.

Employees are also required to maintain a clean, groomed and manicured
appearance. Hair styles, hair color, moustaches, sideburns and other
appearance related items shall present a conservative style and not be
considered offensive given current business appearance standards.

If in doubt, ask the operations manager for clarification before wearing
the article of clothing. This policy includes tattoos, body accessories,
etc. that are not normally covered by the business style clothing
described in this policy.

## Drug-Free Workplace

TDOT policy regarding providing and maintaining a drug free work place
will be in effect. Operators and supervisors are expected to remain
alert during their shifts at all times. No employee shall arrive at the
work place under the influence of any controlled or over-the-counter
drug that will impact his or her performance. Failure to follow this
policy will result in disciplinary action and may include termination.

## Breaks and lunch

Employees are encouraged to take breaks and lunch during the course of
their shift. The break policy is that employees may take up to a 15
minute break before their lunch period (first four hours of the shift)
and one 15 minute break following their lunch period (second four hour
period). This period can not be combined with lunch to extend the lunch
period. The break period can be broken into smaller, more frequent
periods, but shall not exceed the total 15-minute limit. Breaks maybe
restricted only during incident response or similar emergency
situations. The lunch period is 30 minutes and shall be taken by all
full time employees during their shift. The break and lunch periods will
be restricted to the TMC area due to the immediate availability required
of the position and nature of the job duties.

## work shifts, organization chart and training

The current schedule for operations is defined as Monday through Friday
from 5:30am to 10:00pm and the weekend hours are from 8:00am to 8:00pm.

![](media/image3.wmf)The following basic organization chart shows the
reporting relationships of staff assigned to the TMC and should be
utilized as a guide when dealing with personnel assigned to the TMC.

**Sample Organization Chart for the TMC -- 26 December 2002**

The operations staff will be provided the training required to conduct
their duties and will be appropriate for their duty position. The
purpose of this training is to provide them the means to effectively
operate the hardware and software located at the TMC. Individuals who
would like additional training or would like to suggest additional
Courses/training opportunities should approach the operations manager
for authorization and approval

## incident command system

The TMC staff will work with emergency responders in accordance with the
Incident Command System (ICS) and will be an active partner in managing
traffic during incidents and assisting as needed in planning and
recovery efforts. The TMC staff will assist as required to maintain and
update the Metro Nashville Emergency Operations Plan.

## homeland security

This policy will include efforts to coordinate with the State of
Tennessee Office of Homeland Security and the development of policies to
enhance and reinforce the efforts of Homeland Security.

## Severe Weather conditions

This policy is related to the impact that severe weather events may have
on the ability of the TMC to effectively operate and manage the
transportation network. The operators and shift supervisors are expected
to report to work during their assigned shift regardless to weather
conditions and should plan accordingly. In the event that the weather
event occurs during the shift, the operator shall be released following
the shift and/or provided instruction on remaining overnight at a local
hotel or the complete evacuation of the facility in the event of a
tornado or similar severe weather event.

# Daily Operation

The following policies refer to the basic conduct of daily duties and
operation of the TMC.

## Management Center Functions 

The Tennessee Department of Transportation Regional Transportation
Management Center shall be staffed 361 days per year (except New Year's
Day, July 4^th^, Thanksgiving Day and Christmas Day) during the
following hours: Weekdays from 5:30am to 10:00pm and weekends from
8:00am to 8:00pm, unless extended or shortened by TDOT directive.
Special staffing considerations will be made for providing operational
coverage for major events, such as Tennessee Titans Football Games.

## Personnel 

The Following list shows the staff of the TMC as of November 2002:

Operations Manager: Cliff Conklin

Receptionist: Vacant

Shift Supervisor #1: Mark Smith

Shift Supervisor #2: Cory Mock

Shift Supervisor #3: Fred Littrell

Full Time Operator #1: Ray Hallavant

Full Time Operator #2: Monica Kalbarczyk

Part Time Operator #1: Danny Kistner

Part Time Operator #2: Terri Kane

Part Time Operator #3: Lisa Morrow

Part Time Operator #4: Vacant

Part Time Operator #5: Vacant

Part Time Operator #6: Vacant

## Hours Of Operation 

Weekday Hours 5:30am to 10:00pm, Except for the four holidays noted
above

Weekend Hours 8:00am to 8:00pm

Special Events will be considered on an individual basis and coverage
adjusted accordingly.

Operational hours may be modified to cover response to major incidents
on an as needed basis.

## Staffing 

The initial staffing will include a shift supervisor and operator during
the morning and evening shifts. The weekday shifts are generally defined
as 5:30am to 2:00pm and 1:30pm to 10:00pm with a part time operator to
cover the morning and evening peak hours and are generally defined as
6:30am to 9:30am and 4:00pm to 7:00pm. The initial weekend staffing will
include a shift supervisor and four (4) part time operators to cover the
morning and evening shift. The weekends shift are generally defined as
8:00am to 2:00pm and 2:00pm to 8:00pm.

The work schedule for operations personnel will be posted in the break
room and/or other appropriate bulletin board areas on a weekly basis.

The operations manager will report to the TMC for the following work
shift, weekdays between 7:00am to 4:00pm, unless called to report early
and/or required to work beyond this time.

## After Hours On-Call Roster 

The following is the routine and emergency after hours call out list,
the phone numbers are listed in the previous section:

Primary: Cliff Conklin 615-799-6079 (Residence)

615-542-4360 (Cell)

615-539-0926 (Pager)

Ali Farhangi 615-373-7398 (Residence)

615-405-7778 (Cell)

888-365-1552 (Pager)

Gary Ogletree 615- (Residence)

615- Cell)

Secondary: Mark Smith 615-672-5865 (Residence)

615-708-5865 (Cell)

615- (Pager)

Third: Cory Mock 615-599-8199 (Residence)

615- (Cell)

615- (Pager)

## Remote Operation 

Initial remote operation will be granted to the Operations Manager only.
In the event that the system must be operated remotely until the next
shift will arrive at the TMC, the operations manager should be called to
log in remotely. This section will be further defined, as operational
procedures are further refined.

Currently there are no plans for non-TDOT personnel to operate the MIST™
Software via remote interface.

## Security Policy 

Currently, background checks will not be required, but new hires will be
screened for work performance. In addition, please review the section
above regarding passkeys and parking.

## Maintenance Checklist 

The shift supervisor on duty shall start their shift with a daily check
of operational equipment to include field devices and communications
links. Equipment and maintenance activity will utilize the MIST™
Maintenance Module for tracking and scheduling. Issues concerning the
physical operation of the building shall be immediately reported to the
operations manager who will coordinate repair(s) or emergency repair(s)
of the affected equipment.

## Startup/Shutdown 

The reader is directed to the MIST™ User Manual for correct procedures.

## Failure Recovery 

The reader is directed to the MIST™ User Manual for correct procedures.

## Agency/Jurisdictional Contacts 

The following people are listed as normal points of contact for their
respective agencies. This list will be utilized for routine calls during
business hours:

  ------------------------ -------------------------- -----------------------
  **[NAME]{.underline}**   **[AGENCY]{.underline}**   **[PHONE
                                                      NUMBER]{.underline}**

  SGT J.R. Perry           THP                        615-741-3181

  LT Glenn Yates           Metro Police               615-862-7738

  Devin Doyle              Metro Public Works         615-880-3262

  Joe Birge                Nashville Airport          615-275-1643
                           Authority                  

  John Autry               MTA                        615-862-6165

  Bill Sewell              Tenn. Div of EMS           615-650-7010

  Edwin Hogan              Cheatham County EMS        615-792-3443

  Jackie Coulon            Cheatham County 911        615-792-3221

                           Rutherford County          

                           Rutherford County          

  Dennis Wallace           Sumner County EMS          615-451-0429

                           Sumner County              

  Greg Galfano             Williamson County EMS      

                           Williamson County          

  Doug McQuary             Wilson County EMS          615-444-8779

                           Wilson County              

                           Davidson County            

                           Davidson County            

  Larry Poole              NFD -- EMS                 615-862-5350

  Stan McCutchen           Dickson County EMS         615-446-3702

                           Dickson County             

  Jackie Wilkerson         Robertson County EMS       615-384-2186

                           Robertson County           

  Joe Leffelman            Medic One                  615-843-1580

  Linda Passini            Vanderbilt Life Flight     615-936-0770

  Karen Brunelle           FHWA                       615-781-5772

  Mike Smart               FHWA                       615-781-5775

  Jack Carter              TEMA                       615-741-1221

  Jerri Powell             TBI -- Amber Alert         615-744-4558
  ------------------------ -------------------------- -----------------------

## Telephone Call etiquette and Notification Policy 

The staff of the TMC has access to telephones and therefore could
receive calls from the TDOT staff, the media and/or the public. The
operator often becomes the source of information and also a place to
file complaints for various groups of people. The operator/shift
supervisor who takes the call shall attempt to solve the problem or
answer the question for the caller; the goal is a "one-stop shop"
approach for callers to receive assistance or information without
getting transferred to others. All callers will be handled in a
courteous and professional manner regardless to the content of the call
and/or the attitude of the caller. If the staff is not able to answer
the question, it will be transferred to the administrative assistant and
that person will make sure the call is transferred to the appropriate
person(s).

## Contact With Media and the Public

The objective of the ITS is to gather, conduct data analysis, determine
action required and provide accurate information to the public. The
method utilized to provide this information includes DMS, HAR, Media
reports and response to telephone calls. Media outlets that have
partnered with TDOT will be supplied all the information available under
the terms of their agreement with TDOT. The funding for the TMC is
public funds so the information gathered is also public and must be made
available in as many forms as possible to drivers and travelers
throughout the region. Comments or questions raised in regard to other
travel or transportation issues should be passed to the appropriate TDOT
official for response. Operators and shift supervisors should avoid
making comments or statements outside of their area of expertise and
only after approval from TDOT.

## Coordination with HELP Program

The HELP dispatchers will be co-located with the TMC operators on the
control room floor. The purpose of this co-location is to foster
cooperation and coordination between the programs. TMC operators will
work with and share information as required for efficient and timely
response to incidents and to plan upcoming activities. Any issues that
arise during operations (personal, coordination, equipment, software,
etc.) should be handled at the lowest level possible. Issues that remain
unsettled should be reported to the shift supervisor for follow-up. The
operation manager will attend TMC staff meetings and will be responsible
to inform the operators should a change in policy be initiated.

## Dispatch of HELP Vehicles

The HELP dispatchers are responsible for dispatching their own
personnel. HELP dispatchers will coordinate with TDOT Region 3
Maintenance for dispatching of maintenance crews to respond to incidents
and dispatching by TMC operators should be avoided. TMC operators will
not dispatch HELP operators or call them directly on their cell phones
unless directed by the operations manager or HELP Program supervisor.
When required, any communication will be completely professional
communication, using common language and wording as required to transmit
the message and then the communication will be ended. Chatting or
similar communication is not allowed.

# Control System Operation Policies

The reader is encouraged to read the Operations Manual and the MIST™
User Manual for additional detail for this section. These documents may
also include specific public agency policies and procedures.

## Operator Interface

See the MIST™ User Manual for further guidance and information.

## Operational Procedures

The specific operational procedures noted in this document are detailed
in the Operations Manual.

## Incident Management 

The ATMS system provides an incident management and tracking tool for
the use of all operations staff in the TMC. The on-duty operator shall
enter all incidents regardless to size into the software to ensure the
data is tracked, it is available for future reference and for analysis.
Specific details regarding the correct incident data entry procedure is
contained in the Operations Manual.

### Incident Classification Policy

The operator is required to determine what level of incident has
occurred once they have verified the incident location. The following
information will be used to make incident classification decisions
easier. There are two classes of incident, major and minor, and within
this class there are two additional divisions. The operator will assign
the higher incident level if an incident appears to fall in between two
different levels.

The four basic incident levels begin at an Incident Level 1 and reach
the highest at Incident Level 4. A minor incident is one with minor
impact on traffic flow. A major incident has more long-term impacts on
travel and generally is used for serious incidents. Any incident can
also classify in several incident levels based on its current status in
the clearance process.

Incident Level 1 (Minor), includes one or more of the following
conditions, No injuries, Blocking part or all of one lane of travel,
Disabled vehicle(s) on the shoulder with occupants, Minor collisions
moved off the road. Incident Level 2 (Minor), includes one or more of
the following conditions, Minor injuries, Requires Emergency personnel
to respond, Blocking more than one lane of travel, Expected to last more
than 10 minutes. Incident Level 3 (Major), includes one or more of the
following conditions, Serious injuries, Involves several vehicles,
Vehicles or debris blocking multiple lanes, Minor HAZMAT spill, Expected
to last more than 30 minutes. Incident Level 4 (Major), includes one or
more of the following conditions, Multiple fatalities, Serious HAZMAT
spill or cleanup, Closure of the highway, Structural or other damage to
the roadway requiring immediate response, Expected to last more than one
hour.

### Incident Response

The operator shall respond to known incidents, found in locations
covered by ITS devices, and/or the region covered by the HELP patrols in
a timely manner to ensure the incident is located, confirmed and an
appropriate response is started to clear the incident. Response
procedures based on the policies noted in this document are detailed in
the Operations Manual. In general the operator is required to monitor
traffic conditions on the highway, identify any changes in condition,
locate the suspected incident, confirm the incident by moving a CCTV or
by other means (IE HELP report, reports from other Traffic Operation
Centers in operation in the region, Police Computer Aided Dispatch
(CAD), etc.), log the incident in the software, utilize the correct
incident response plan and notify the correct individuals or groups on
the call out list. The operator shall monitor the incident and make
corrections to the incident status, response plan or system data as
required and shall close the incident when the incident has been cleared
and traffic has returned to travel flow conditions that a motorist would
expect to find at that time of day, in that location given the existing
weather condition(s). When ITS devices are being used for other actions,
they shall be commandeered for incident response, including construction
work zone support efforts. Following the incident response, ITS
equipment will be returned to service for other activities as required.

### Incident Detours

The response to a major incident (Incident Level 4) may require the use
of a detour. It is the policy of TDOT to utilize the existing limited
access highway network for detour routing. The use of surface streets to
support incident detour routing shall be avoided. Should the surface
street network be utilized, the action shall be coordinated through the
operations manager for approval and coordination with the Metro Police
for traffic control at important intersections to ensure safe and
effective traffic control on the surface streets.

Construction detours shall be tracked as closely as possible by the TMC
operators and mapped if possible to assist operators with developing or
authorizing a suggested response plan generated by the ATMS. Since
Construction detours are expected to operate during specific times of
the day and for a specific duration, operators must know their status
daily. Detouring incident traffic onto a construction detour can
potentially overload the detour route and the surrounding street network
creating a larger problem.

More detailed criteria for determining the detour criteria can be found
in the Operations Manual.

### Incident Information

The objective of collecting and analysis of incident information is to
provide complete, detailed information in real-time to the public which
will allow them to make informed travel decisions. All information
outlets will be utilized to get the word out to inform the traveling
public, including DMS, HAR and the media.

### Incident Tracking

The operator will be required to enter data into the ATMS software for
record tracking and to assist with incident monitoring by providing them
with a visual reference and reminder to monitor the incident. The
current incident(s) will be actively monitored by the on-duty operator
and shift supervisor to ensure accurate information is provided to all
concerned and that the response is occurring in a manner to clear the
incident it as quickly as possible. The operator will update status in
the software as well as updating information outlets as required.
Incident information will be provided to the incoming operator if an
incident spans one or more shift rotations.

### Data Entry

The operator will record all activities in the software for tracking and
activation of response plans. The information shall be recorded using
the appropriate graphical user interface to document the actions taken
and the time they were taken. This data will be utilized to produce a
monthly report to report actions and activities taken in response to
incidents.

### Incident Paging and Call-Out

The TMC will utilize pagers and cell phones to notify individuals and
groups of individuals who may have a need to know when an incident
occurs (IE -- Regional Director, TMC Manager, Director of Community
Relations, Operations Manager, Maintenance Crew Foreman, HELP
Supervisor, etc.). This procedure will be utilized to provide general
information regarding the type of incident, location of the incident and
expected impact and outcome. This system may also be utilized to call in
workers who may be off-duty or otherwise away from the TMC but are
needed to assist with the handling of the incident.

### Post Incident De-briefs

The staff of the TMC, within the limit of their assignments, will
participate in any after incident drills and exercises as required by
the State or Local Offices of Emergency Management. These after incident
de-briefs or after action reviews will be held following large highway
incidents as well as large local incidents that effected highway traffic
to provide a forum to share lessons learned and to foster interagency
communication.

# Maintenance Procedures

See the MIST™ User Manual for specific computer software procedures
regarding system maintenance procedures. Field equipment is maintained
via separate contract between TDOT and the contractor. The field
contractor will work with the operations staff to promptly repair or
replace broken or malfunctioning equipment. Specific questions regarding
the detailed procedures should be directed to the Operations Manual.

## Routine Maintenance

See the MIST™ User Manual for specific procedures for software
maintenance. Contract Maintenance provider is responsible for field
devices and the operations manager will coordinate maintenance
scheduling and tracking.

## Preventative Maintenance

See the MIST™ User Manual for specific procedures related to the
computer system and software maintenance. Contract Maintenance provider
is responsible for field devices and the operations manager will
coordinate maintenance scheduling and tracking.

## Spare/Backup Equipment 

See the MIST™ User Manual for specific procedures related to the
computer system. Contract maintenance provider is responsible for field
devices and the operations task manager will coordinate maintenance
scheduling and tracking.

## Emergency 

See the MIST™ User Manual for specific procedures related to the
computer system. Contract Maintenance provider is responsible for field
devices and the operations manager will coordinate an emergency
maintenance schedule and tracking policy when the maintenance period
begins.

## Contract Maintenance 

See the MIST™ User Manual for specific procedures related to the
computer system and software maintenance.

Contract maintenance provider is responsible for field devices and the
operations task manager will coordinate an emergency maintenance
schedule and tracking policy when the maintenance period begins. The
term and conditions of the maintenance response will be determined based
on the official contract in effect with TDOT and the contractor(s).

The maintenance provider is required to coordinate routine maintenance
activity with the TMC to limit the disruption of service that may be
required from work on one or more field devices. The contractor will
provide a weekly work schedule to the operations manager at least 5 days
before the routine work will commence.

# System Operations Logs

See the MIST™ User Manual for specific procedures related to the
computer system.

## Operations

See the MIST™ User Manual for specific procedures related to the
computer system.

## Maintenance 

See the MIST™ User Manual for specific procedures related to the
computer system.

## Events 

See the MIST™ User Manual for specific procedures related to the
computer system.

## System Reports 

See the MIST™ User Manual for specific procedures related to the
computer system.

## Traffic Data

See the MIST™ User Manual for specific procedures related to the
computer system.

## Risk Management 

See the MIST™ User Manual for specific procedures related to the
computer system.

# Operational Concepts

## Traffic Monitoring

The basic concept of traffic monitoring relates to monitoring the
roadway system via CCTV image viewing, traffic flow detector monitoring
using the MIST™ Software and listening to the HELP radio dispatchers for
signs that an incident has occurred. The operations staff will monitor
the system and take the appropriate action once an incident is detected
or based on the needs of traffic management for special events.

This section will be more fully defined once the software is delivered
and is operational. Also, further guidance from TDOT will be required as
we determine the appropriate methodology to utilize for Nashville, based
on agency relationships and the needs of the traveling public.

### Speed Detector Monitoring and Response

The speed detectors installed along the highways in the Nashville area
are for the detection of speed for traffic use only. The detectors
utilize various technologies to detect speed, volume and occupancy data.
The data is collected locally at the device controller in the field and
transmitted as a binned data packet to the central communication server
at the TMC. This data is then utilized by an incident detection
algorithm in the MIST™ Software to produce an alarm for the operator
when congestion is detected due to an incident. The data is also stored
for a short period for use by the algorithm and is transmitted to the
TDOT Planning Division in minute data "buckets" for analysis into
historic trends in travel patterns and population growth.

### CCTV Image Viewing

The use of all system CCTV cameras shall be confined to viewing
highways. No off-highway viewing of any kind shall be permitted. No CCTV
camera shall ever be used to 'zoom in' or to specifically focus on an
individual, private vehicle, or group of individuals either on or off
the roadway. Due to potential liability to TDOT, camera views shall be
kept on the roadway at all times while moving or re-positioning the
camera. The camera views are linked to the TDOT Web site and therefore
images taken from improperly aimed cameras may be posted to the Internet
and will be available for viewing by the public and the media. Any
operator who improperly uses a CCTV camera will be disciplined and
possibly dismissed immediately following the incident or as soon as
possible once management is informed and has investigated the suspected
abuse.

### Video Wall

The video wall as currently configured contains 12 monitoring devices or
screens in a 4 x 3 grid combined to create one large viewing area. The
wall can be configured into multiple viewing regions or up to
approximately 48 separate, individual regions. It is expected that the
initial configuration will include video sequencing, a regional map
display and several individual cameras that are being used for specific
monitoring. The exact configuration will be determined by usage and will
be further defined in the future.

### Video Sequences

The use of pre-set camera sequences is important to monitor current
roadway conditions since all cameras can not be monitored continuously.
The sequences are to be checked daily to verify that the cameras are
correctly focused and viewing the proper direction. This monitoring will
also allow operators to detect possible video and control communication
failures that may have occurred with each CCTV. If a camera is found to
be not functional it shall be removed from any sequence it was is
included in and a troubleshooting work order will be completed and given
to the maintenance team to repair.

### Recording Video Images

The TMC will not regularly create VCR tapes containing CCTV images.
Tapes will be created in special circumstances for training purposes
only and only after the TDOT TMC Manager or his designated
representative has granted permission. The recorded tape or its contents
may not be shared, copied, or in any other way distributed or used for
any purpose outside of that for which it was created. This policy is to
prevent unauthorized distribution of taped material, no matter how
harmless or ordinary the content may be to reduce TDOT liability in the
event an individual was ever identified from a taped image. This issue
applies especially to tapes that may include accident footage useful in
litigation.

### Road Construction Monitoring

The active monitoring of road construction and maintenance activities
will be conducted by the operations manager, shift supervisors and
operators for the purpose of knowing the condition of the highway
network at all times they are on duty. The data regarding specific
conditions that could impact traffic will be monitored daily and action
taken as needed to insure coordination occurs between the specific
project engineer and the TMC to insure correct traffic information is
provided to the motorist.

### Road Construction Reporting

It is expected that as the public and especially the media become aware
of the TMC, the TMC will receive telephone calls regarding road
conditions. It is important that the engineers responsible for road
construction and maintenance keep the TMC informed regarding their
project status so questions can get answered correctly and in
coordination with the region public affairs officer.

### Diversion Route Planning

It is the mission of the TMC to provide accurate and timely information
to the traveling public in near real-time. Since this may require the
utilization of diversion routes, the TMC must know the traffic impacts
of highway work activities, including but not limited to guide rail
repair, mowing, striping, etc. These activities may be suspended if
diversion routing will increase the likelihood of potential hazardous
conditions for highway workers.

### Highway Maintenance Activity

The TMC operators and shift supervisors will make every effort to assist
the Highway Maintenance workers with Maintenance and Protection of
Traffic (MPT) duties in the work zone by using DMS and HAR to warn and
advise motorists of travel conditions in the work zone. The Maintenance
Supervisors in charge of the individual crews will assist this effort by
providing calls or e-mails to the TMC before beginning work to provide
work location and hours of operation in a timely manner. This policy
also applies to prison labor groups working along the road shoulder
picking up litter.

## Traffic Response

The basic concept of traffic response relates to responding to incidents
found on the roadway system via getting information to the traveler and
responders as quickly and effectively as possible. Tools utilized for
this information dissemination include Dynamic Messages Signs (DMS),
Highway Advisory Radio (HAR) transmitters, and in the future other means
of getting information out of the TMC to people that can use the data.
The operations staff will respond to incidents within the coverage area
of the system and based on the needs of traffic management for keeping
the traffic moving.

This section will be more fully defined once the software is delivered
and is operational. Also, further guidance from TDOT will be required as
we determine the appropriate methodology to utilize for Nashville, based
on agency relationships and the needs of the traveling public.

### Use of Dynamic Message Signs (DMS)

The use of all DMS, fixed location and portables assigned to the TMC is
limited to TDOT TMC Operators unless they are being used to support part
of an interagency pre-approved response plan. TDOT maintains authority
to control these DMS at any time. TDOT is the "owner" of all limited
access highway DMS and is responsible for all activities impacting
travelers along these corridors and has precedence and final authority
over any use of these signs and message content approval. The specific
usage and message formats can be found in the Operations Manual or the
system user guide for typical application, sign characteristics, message
format, message panel flash times, etc. The operator that responded to
the incident shall be responsible for validating the continuance and
finally clearing the message unless it is needed for an extended period.
Shift supervisors are responsible to make sure that all messages posted
or active during their shift are accurate/appropriate and removed when
no longer needed.

Only real-time information about incidents and roadway, and about
traffic, roadway, environmental, or pavement conditions that could have
an effect on driver safety and traffic efficiency shall be displayed on
the DMS, with the exception that the following may occasionally be
displayed: a) advance notification of roadwork requiring lane closures
as described in the policy and b) advance notification of special events
that will adversely affect travel either because of added traffic
generated or the requirement to close street or highways as described in
the policy. Occasional messages associated with Amber Alerts or other
Public Safety issues as described in this policy manual will be
permitted.

Note that "Incidents" includes crashes, disabled vehicles, debris,
utility line breaks or other activities or actions that interrupt or
otherwise impact traffic flow.

### Operation of DMS by Law Enforcement Personnel

Control of DMS during TMC off-hours may be arranged with the applicable
law enforcement or 911 agencies provided that appropriate agreements are
developed. Authorized law enforcement personnel may operate DMS
identified by the TMC Manager for emergency situations during TMC
off-hours. Messages may be displayed for the following situations: a)
major incidents as defined above, b)-spilled loads, and c) severe
weather or pavement conditions. Law enforcement personnel shall only
display messages contained in a message library developed by the TMC
Manager.

### Blank Signs

DMS *may* be in blank mode when traffic, roadway, environmental, or
pavement conditions do not warrant the display of a message. However,
travel time messages will be displayed throughout much of the peak and
non-peak periods when other messages are not warranted. The default
message for most DMS will be the travel time information rather than a
blank sign.

### Messages during Peak Periods 

During daily peak traffic periods, messages shall be used to advise
motorists of unusual conditions (e.g. crashes, lane blockages etc.) and
travel times. Congestion descriptor (e.g., CONGESTION NEXT 2 MILES)
shall *not* be used to advice motorist of normal daily recurrent peak
traffic congestion conditions.

### Display of Upcoming Roadwork

Traffic-related information that provides advance notice of upcoming
roadwork may be displayed, but should be replaced by current information
whenever applicable. The upcoming roadwork must be on a freeway or other
access controlled facility that could possibly affect the drivers'
trips. The advance notification should not be given more than 7 days
prior to the roadwork. Calendar dates should not be used in the message,
rather the days of the week should be indicated. Messages that impact
the safety and operations of the roadway shall have priority over
advance notice messages.

### Display of Upcoming Special Events That Adversely Affect Travel 

Traffic-related information that provides advance notice of upcoming
special events that will adversely affect travel by generating major
traffic or requiring street or highway closures may be displayed. The
advance notification should not be given more than 7 days prior to the
special event. Calendar dates should not be used in the message, rather
the days of the week should be indicated. Messages that impact the
safety and operations of the roadway shall have priority over advance
notice messages.

### Display of Travel Times

The system is designed to automatically calculate travel times from each
DMS to selected destinations using the speed detectors along the
freeway. Travel time messages may be displayed at anytime when traffic
conditions do not warrant the use of other messages. Specific sign
locations to be utilized to display travel times will be determined by
TDOT.

### Traffic Diversion (General)

When incidents occur that do not require the full closure of the roadway
but it is still desirable to divert traffic from the freeway, DMS
messages shall *not* divert motorists to specific alternative routes
unless positive guidance is available along the alternative route in the
form of a) guide signs and/or trailblazers to the major destination, or
b) law enforcement or traffic control personnel are positioned at
critical locations long the alternative route to control and guide
traffic. Furthermore, both of the following conditions must be met:

-   The DMS operator has current and continuously-updated knowledge of
    the traffic conditions on the alternative route; and

```{=html}
<!-- -->
```
-   The alternative route will result in a significant savings in time
    for the motorists.

### Traffic Diversion (Full Highway Closure)

DMS Messages will be utilized to divert traffic off of the highway
network when required by a response to an incident classified as a Level
3 or Level 4. The message library will provide a pre-configured message
telling motorists that they must exit. No traffic will be told to exit
the highway until the necessary coordination with the local agencies
have been made to ensure a detour route has been authorized and clearly
indicated. When the detour route is no longer a viable option, the
message will be changed on the DMS to another incident related message
based on the situation.

### Traffic Diversion to Roadways Not Under the Jurisdiction Of TDOT

Messages directing motorists to a specific alternative route may be
displayed. The alternate route may not always be a state route. Specific
messages recommending that motorists divert to specific roadways and/or
local streets that are not within the jurisdiction of TDOT are not
permitted unless severe conditions exist and the appropriate agencies
are involved. Messages supporting preplanned diversion routes
established via written agreements with the local transportation agency
are permitted at all times. "Soft" diversion messages (i.e., USE OTHER
ROUTES or CONSIDER OTHER ROUTES) may be displayed when conditions
warrant.

### DMS Messages used for Adverse Weather, Environmental, and Roadway Conditions

DMS may be used to display adverse weather, environmental, or roadway
conditions downstream that may impact driver visibility and safety
(e.g., fog, major snow storms, sand storms, icy roadway, high cross
winds, broken pavement etc.), or advise motorists of specific
regulations due to the weather or roadway conditions.

Messages, when used, are restricted to a specific location and a
specific DMS. The roadway condition must be in the vicinity of the sign
in use. General weather, environmental, or roadway condition information
(ICY ROAD CONDITIONS AHEAD) is not permitted.

### Limits of DMS Influence for Incidents

Messages should be displayed for all verified *major* incidents (Level 3
or Level 4 incidents -- i.e. multi-vehicle accident affecting several
lanes, truck overturn, etc.) that occur on the freeway a far away as 5
miles downstream (and/or the resulting traffic que) from the DMS
location where the message is placed. The message should include the
location of the incident (or closure) and the number of lanes closed.

Information concerning verified *minor* incidents and lane closures
should be displayed for incidents occurring up to 5 miles downstream
from the DMS, provided that information about the location and number of
lanes closed can also be given.

Information concerning verified lane-blocking incidents that occur on an
intersecting freeway may be displayed on DMS that are located upstream
of the interchange with that freeway depending on the location, severity
and duration of the incident.

### DMS Message Priority

The DMS messages shall be prioritized in the following order: traveler
safety functions, vehicle delay and/or travel times, public safety or
service messages and all other approved uses. DMS are to be used to
enhance or promote motorist safety. Incident related messages have
precedence over any other use of a DMS sign.

### Other DMS

Other agencies and private concerns may use DMS that they own without
prior authorization from TDOT, except when they are employed along state
highway corridors or create an unsafe condition along the roadway. In
the event that use of a DMS will impact an agency or then TDOT
jurisdiction, the agency that desires to post a DMS message shall
coordinate the schedule, message and limits of its use with the impacted
jurisdiction prior to posting the message.

### DMS Message Confirmation

The operator who posted a message is responsible to check the system as
soon as possible following the posting and confirm that the message is
being displayed correctly. This confirmation will occur using system
software or if possible by visual means (visual confirmation is the
desired methodology when available to the operator). This policy also
applies when messages are removed from DMS.

In the event a message is needed for a Level 3 or Level 4 incident that
will impact the highway for longer than 6 hours in duration, the
operator on duty will check the message at least every three- (3) hours
or as the situation requires, whichever will require the operator to
confirm the messages more frequently while they are on duty.

### Use of Highway Advisory Radio (HAR)

TDOT has installed several Highway Advisory Radio Station transmitters
in the region under license with the FCC to broadcast traveler
information in real-time. The system is to be utilized to provide
real-time travel information regarding response to incidents and events
that impact the use of the highway by the traveling public and may also
be used to provide related public service announcements via AM radio
frequency broadcast. The use of the HAR recording system is limited to
the TMC Operators or others as designated by the operations manager.
This policy will ensure consistent recording voices are utilized for the
recorded messages. Other agencies may request to utilize the HAR, but
will be required to contact the TMC Manager for approval. Recorded
messages for the HAR must be clear and understandable by the public.

### HAR Messages

The HAR will be utilized to provide traveler information in real-time.
Therefore, the message being broadcast must be updated as required or at
least once every hour during normal operating hours at the TMC. More
frequent message updates may be required during serious incidents and
shall be utilized in coordination with DMS and other traveler
information methods. The use of HAR will also support the Amber program
as required. The HAR transmitters will remain on at all times and
provide station identification and public information/safety messages
unless preempted by incident or Amber Alert information.

### HAR Message Format

The HAR messages shall conform to the textual outlines contained in the
Operations Manual and shall be updated as required to maintain
operational effectiveness. Introductory message and station
identification shall be read verbatim from the Operations Manual.
Individual messages and updates shall conform to the textual based
templates developed to ensure consistency. The templates can be found in
the Operations Manual.

### HAR Message Confirmation

The operator or shift supervisor responsible for completion of a message
recording on the HAR shall check the recording for content and accuracy.
This review will check the message content for clear, easy to understand
information spoken in a clear, professional manner and shall avoid the
use of slang, excessive pauses, slurred words, and/or complex language.
Messages that are unclear shall be re-recorded.

## Miscellaneous Concepts and Policy

This section is the catch all section for policy items that may not fit
neatly in Sections 8.1 or 8.2.

This section will be more fully defined once the software is delivered
and is operational. Also, further guidance from TDOT will be required as
we determine the appropriate methodology to utilize for Nashville, based
on agency relationships and the needs of the traveling public.

### Media/Interagency Image Requests

TDOT maintains the cameras as part of a system of traffic management
tools. Requests by the news media or other end users to tape or
otherwise view specific CCTV images/scenes shall only be complied with
the prior approval of the TDOT TMC Manager or his authorized
representative. The policy of the TMC is that no images taken will
violate the image viewing policy described in the signed interagency
agreement or as noted above. Other agencies that have signed an
interagency agreement may be granted pan, tilt, zoom control of cameras,
but will be restricted if the TMC needs to use the camera and will
exercise higher level user control to "take" the camera control from the
other user.

When the media requests a different viewing area on the camera (the
media does not have pan, tilt, zoom control), the operator will
determine that the camera is not needed for other purposes to monitor
traffic conditions and he/she has the time to move the camera based on
the operational requirements of the current operational situation before
moving the camera. It is expected that numerous requests to move a
camera will remain un-granted due to operational constraints.

The TMC also reserves the ability to transmit a blank image to outside
sources if the image being viewed is determined to be not appropriate
for the outside viewer(s) and/or would interfere with the TMC's ability
to manage an incident. This blanking policy may also be enforced/in
effect during the hours when the TMC is not staffed and/or in full
operation.

### Web Site Images

The policy of TDOT is that all camera images will be available to the
public via the TDOT web site and/or the media. It is the duty of the
operators, shift supervisors and operations manager to ensure the images
supplied to the web site/media are of the highest quality and only show
appropriate video images. Any camera found to be incorrectly focused
will be adjusted and removed from the web site or blocked from public
viewing as required by policy.

### DMS for Special Events

DMS may be used to accommodate motorists traveling to special events
when the anticipated attendance exceeds 40,000 patrons. The messages may
be used to direct motorists from the primary route to an alternative
route that will eventually lead to a parking area. Trailblazers shall be
used on the alternative route to direct motorists to the special event
parking areas. Messages such as this shall be displayed no more than 3
hours prior to the start of the event. Messages that impact the safety
and operations of the roadway shall have priority over special event
messages.

Coordination and meetings with Metro Police should be developed to occur
quarterly to review and refine this policy. These meetings will allow
the Metro Police to see how they could better utilize the tools the TMC
could provide. This meeting should be held at the special event venue
and include a tour and should also be held at the TMC to raise
awareness.

### DMS Regulatory Speed Messages

The DMS message can be displayed to *supplement* existing static speed
limit signs. The DMS message is not enforceable and shall not be used in
place of a static sign. However, the DMS can be used to display
*advisory* speed limits without static advisory speed limit signs.

### Advertising

Messages advertising a product, service, campaign or political party is
prohibited. Messages for special events should be designed such that
advertising is not embedded in the messages.

### Public Service Announcements

Messages designed to relay a public service announcement (ridesharing,
enforcement actions, air quality alerts, telephone hotlines, potential
transit strike notices, etc.) are *not* generally permitted on DMS, nor
are messages designed to increase public awareness of a specific topic
not associated with traffic or transportation. The TDOT Commissioner
through direction to the TDOT TMC Manager may override this policy.

### Display of Amber Alerts

DMS messages may be displayed for AMBER Alerts. Only credible real-time
information, where it is crucial to the safety of the victim to
disseminate the information to the public in the near term, will be
displayed on DMS signs. Law enforcement activates an Amber Alert when
circumstances meet the following criteria: the missing child is of a
pre-determined age; the law enforcement agency believes the child has
been kidnapped; the agency believes the missing child is under the
threat of serious bodily harm or death.

The law enforcement agency will consult with the investigating agency
prior to requesting DMS sign activation. TDOT will only respond to AMBER
alert requests from the Metro Police. The TMC staff and local police
staff shall jointly agree upon the most appropriate DMS message
content(s). TMC staff shall also consult with Metro Police staff
regarding the length of time to display messages (initially 2-3 hours),
and extent of roadway system to display the messages (i.e. radius and/or
directions and specific routes).

TMC personnel should discuss with the requestor the limitations on
message content, the number of signs that can be deployed within a given
time period, conflicts with other necessary sign messages, etc. There is
a concern that messages that are too general in describing vehicles
might result in inappropriate vigilantism against innocent persons
driving similar vehicles described in the alert message. The preferred
response is to display a radio frequency (thus referring the public
elsewhere for details) -- that is utilized for Highway Advisory Radio
(HAR) broadcasts or appropriate commercial radio. Alternatively, a
license plate number (or partial number) might be displayed along with a
vehicle description. The display of any contact phone number is
discouraged.

Nothing in this policy suggests a requirement to pre-empt true motorists
safety messages, e.g. unexpected "end of queue" motorist alerts, severe
weather advisories (fog, smoke, ice), road closure and detour
information, etc. It may be necessary to turn off an AMBER alert sign if
that creates a traffic hazard.

### Inter-modal Information

DMS may be used to display messages to inform motorists of conditions to
assist them with inter-modal travel. For example, DMS may display
messages to inform motorists of a) the availability of parking at
Park-and-Ride facilities, b) whether commuter rail trains are running on
schedule, or other applicable inter-modal information as approved by
TDOT. This information is of a lower priority than information
concerning roadway incidents and other situations that affect motorist
safety. The priority for displaying messages shall remain in the control
of TDOT.

### DMS Test Messages

It is sometimes necessary to display messages on a DMS to assure correct
operations, to "burn-in" a new signs, or for special studies. Acceptable
test messages should either state TEST-MESSAGE, display a portion of the
alphabet, a sequence of numbers, or a non-message test pattern such as
moving columns or rows, etc. (Note: SIGN UNDER TEST may be a suitable
option to TEST-MESSAGE). Other test messages shall be reviewed and
approved by the TMC Manager before they are displayed.

### Ramp Metering

This policy section will be added when ramp-metering operations begin in
the future.

## Data Analysis And Warehousing

Traffic data, incident data, operational data, and other data and
information is to be analyzed and saved. The standard data archiving
feature of the MIST™ software will be maintained, see User Guide for
detail. In addition, traffic data will be fed to the TDOT Planning
Division for analysis and long term storage. The exact method of storage
and the transmission process has not yet been defined, but it is
expected to be an automated process and little or no operator
involvement is expected.

Initially the data to be archived includes: Volume per lane, speed per
lane, occupancy per lane, estimated travel times and traffic density.

Specific performance measures have not yet been defined. The needs of
TDOT for data and how it will best be presented to decision-makers,
policy makers (if different), budgetary requirements and the needs of
the public must be developed once we have data to analyze. The policy in
this section will be developed once the software and field equipment is
operational and producing data. The consultant staff will work with TDOT
and assist with the development of how data will be collected and
analyzed to calculate those yet undetermined performance measures. A
reporting system will be defined at that time, either a monthly report
type format or similar report can be produced.

## Interagency and Inter- Jurisdictional Coordination

This process has yet to be defined and further dialog is required to
determine specific procedures and will be defined in detail in the
Operations Manual and following the beginning of actual operations. In
general, the TMC will gather transportation data and pass this
information to concerned agencies (as determined by the scope of the
incident or event) by methods yet to be defined.

The operations manager is available to assist with briefing other
interested parties from the public or private sectors. The support may
include development of briefing documents and/or electronic documents,
preparing for and hosting meetings and training classes and may also be
a class or meeting presenter as required. This activity may include
development of orientation classes and presentations for TDOT and other
public sector personnel.

Staff from other agencies that may be working at the TMC to support
operations will be under the operational control of the operations
manager. This control does not include actual supervision activities,
but is required for effective operational coordination activities.

# Control Center Description / System Field Devices

## Location

The TMC is located on the TDOT Region 3 complex at 6601 Centennial Blvd.
in Nashville. Centennial blvd. is located off of the Briley Parkway on
the West Side of the city and is near the John C. Tune Airport.

## Access/Security

Building access is limited to authorized personnel, approved guests or
persons on official business with TDOT, especially to the Operations
Room. The administrative assistant located at the front desk will query
all visitors and ensure they see the correct individuals or that they
are in the correct building on the complex.

Visitors that need to see a TDOT person located on the second floor will
be asked to wait and the person will call ahead to ensure the employee
is expecting them and also to inform them that they are here. Staff will
either direct that the person be directed to their desk or told to wait
until they are available to greet them themselves in the common area.

Authorized users will be issued either a standard door key and/or a
passkey that will allow access to the area of the building where they
are required to have access based on their job duties. Access to
personnel to areas they are not normally allowed access will be granted
by the operations manager or the TMC manager. Questions regarding access
should be directed to one of these two individuals.

## Layout

See the attached plan view of control center.

## Fire Suppression

See the attached plan view of control center for location of controls,
cutoffs, etc.

## Power Source/Location

See the attached plan view of control center for location of controls,
cutoffs, etc.

## HV/AC

See the attached plan view of control center for location of controls,
cutoffs, etc.

## Data Communications

See the attached plan view of control center for location of controls,
cutoffs, etc.

## Voice Communications

See the attached plan view of control center for location of controls,
etc.

## Network Communications

See the attached plan view of control center for location of controls,
other networks, etc.

## Field Device Descriptions

See the attached plan view of different ITS project phase maps for
location of devices and other sections of this policy for specific
information regarding devices.

# System Documentation

The operations manager, TMC manager and the contract maintenance
provider are responsible for maintaining vendor maintenance
documentation securing documentation revisions, procedures for updating
maintenance documents, etc. The documents will be stored in file
cabinets in the Operations Room Copy Room, the Maintenance Room and the
storeroom located outside the entrance door to the Operations Room.
Storage location will be determined by need to secure the information
and required access by engineers and technicians.