Florida Department of Transportation District Five Transportation Systems Management & Operations (TSM&O)

Active Arterial Management Traffic Management Center Standard Operating Guidelines

Version 1.0

ii

Active Arterial Management TMC Standard Operating Guidelines

Updates to the Standard Operating Guidelines

Updates to the Active Arterial Management TMC Standard Operating Guidelines will not be considered final until approved by the District Active Arterial Management Engineer or designee.

DOCUMENT CONTROL PANEL

File Name:

AAM D5 SOG

File Location:

R:\AAM\SOG

Version Number: 1.0 Name Date

Created By: Steven Mikesell / Dan D’Antonio, HNTB 5/18/2016

Reviewed By: Ray Marlin (FDOT D5)

Jim Stroz (FDOT D5)

Manny Rodriguez (FDOT D5)

Orange County Seminole County

City of Orlando

City of Maitland

City of Winter Park

Modified By:

Completed By:

iii

Active Arterial Management TMC Standard Operating Guidelines

TABLE OF CONTENTS INTRODUCTION ............................................................................................................................................................... 1 1.

GENERAL OVERVIEW ....................................................................................................................................................... 2 2.

2.1. RTMC AAM Mission Statement .......................................................................................................................... 2

2.2. Scope of Work .................................................................................................................................................... 2

2.3. RTMC AAM Layout ............................................................................................................................................. 3

2.4. RTMC AAM Operations Managers ..................................................................................................................... 4

2.5. RTMC AAM Signal Timing Engineer .................................................................................................................... 4

2.6. RTMC AAM Operator.......................................................................................................................................... 5

OPERATIONS ROOM MANAGEMENT .............................................................................................................................. 6 3.

3.1. Rules & Guidelines.............................................................................................................................................. 6

Smoking Policy ................................................................................................................................................ 7 3.1.1.

Drug-Free Workplace ...................................................................................................................................... 7 3.1.2.

Operator Conduct ........................................................................................................................................... 7 3.1.3.

Appearance Guidelines ................................................................................................................................... 8 3.1.4.

3.2. RTMC AAM Control Room Staffing ..................................................................................................................... 8

3.3. Scheduling .......................................................................................................................................................... 8

Time off Requests ........................................................................................................................................... 9 3.3.1.

Sick Leave ........................................................................................................................................................ 9 3.3.2.

Shift Change .................................................................................................................................................... 9 3.3.3.

Breaks and Lunch .......................................................................................................................................... 10 3.3.4.

Overtime ....................................................................................................................................................... 10 3.3.5.

3.4. Operator Shift Start Up ..................................................................................................................................... 10

3.5. Operator Shift Close Out ................................................................................................................................... 11

3.6. Access Requirements ........................................................................................................................................ 11

FHP Regulations on RTMC/COMM Center Access ........................................................................................ 11 3.6.1.

Incident Command System and the National Incident Management System .............................................. 12 3.6.2.

Florida State Statute 119 (FSS 119): Florida’s Public Record Laws ............................................................... 12 3.6.3.

Cameras and Public Record........................................................................................................................... 13 3.6.4.

Internet ......................................................................................................................................................... 14 3.6.5.

Telephone Etiquette ..................................................................................................................................... 15 3.6.6.

Contact with Media and the Public ............................................................................................................... 15 3.6.7.

iv

Active Arterial Management TMC Standard Operating Guidelines

Social Media Sites .......................................................................................................................................... 16 3.6.8.

Physical Security and Access to Data Processing Facilities ............................................................................ 16 3.6.9.

Logical and Data Access Controls .................................................................................................................. 16 3.6.10.

Network Security ........................................................................................................................................... 17 3.6.11.

Protection Against Loss ................................................................................................................................. 17 3.6.12.

3.7. Quality Control ................................................................................................................................................. 17

Software Applications and ITS Monitoring ................................................................................................................... 20 4.

4.1. ATMS Infrastructure Preservation and Work Zone Monitoring ....................................................................... 20

4.2. AAM Software & Devices ................................................................................................................................. 21

SunGuide ....................................................................................................................................................... 21 4.2.1.

ITS Devices..................................................................................................................................................... 23 4.2.2.

Websites ........................................................................................................................................................ 31 4.2.3.

MIMS ............................................................................................................................................................. 32 4.2.4.

ATMS.now ..................................................................................................................................................... 33 4.2.5.

Tactics............................................................................................................................................................ 33 4.2.6.

InSync ............................................................................................................................................................ 33 4.2.7.

SynchroGreenTM ............................................................................................................................................ 34 4.2.8.

4.3. System Review.................................................................................................................................................. 34

Event Evaluation ........................................................................................................................................................... 35 5.

5.1. Personal Injury or Public Safety Concerns ........................................................................................................ 35

5.2. Severity Levels .................................................................................................................................................. 36

5.3. Unique and Unusual Incidents ......................................................................................................................... 37

5.4. Event Status Groups ......................................................................................................................................... 37

5.5. Secondary Events ............................................................................................................................................. 38

Communication Systems ............................................................................................................................................... 40 6.

6.1. Arterial Dynamic Message Signs ...................................................................................................................... 40

ADMS Messaging Priority Levels ................................................................................................................... 40 6.1.1.

Two-Phase Messaging & Message Limits ...................................................................................................... 41 6.1.2.

Travel Time Messages ................................................................................................................................... 41 6.1.3.

ADMS Critical Errors ...................................................................................................................................... 42 6.1.4.

Documentation ............................................................................................................................................. 42 6.1.5.

Notification ................................................................................................................................................... 42 6.1.6.

v

Active Arterial Management TMC Standard Operating Guidelines

6.2. The Florida Automated Traveler Information System (FLATIS – 511) .............................................................. 43

The Florida 5-1-1 System (FL-ATIS) ............................................................................................................... 43 6.2.1.

Florida 5-1-1 Website .................................................................................................................................... 44 6.2.2.

Maintenance and System Failures ................................................................................................................................ 44 7.

7.1. System Failures ................................................................................................................................................. 44

Traffic Signals ................................................................................................................................................ 46 7.1.1.

ITS Field Devices Damage .............................................................................................................................. 46 7.1.2.

Documentation ............................................................................................................................................. 46 7.1.3.

7.2. SunGuide Failure .............................................................................................................................................. 46

Documentation ............................................................................................................................................. 47 7.2.1.

7.3. ADMS Equipment Failure ................................................................................................................................. 47

Documentation ............................................................................................................................................. 48 7.3.1.

7.4. Internet Failures ............................................................................................................................................... 48

7.5. 511 FLATIS Failures ........................................................................................................................................... 48

7.6. Failure of External Agencies’ Equipment ......................................................................................................... 49

Traffic Signal Failure....................................................................................................................................... 50 7.6.1.

Reporting and Documentation ..................................................................................................................................... 51 8.

8.1. Aides and Binders ............................................................................................................................................. 51

AAM Console Directory ................................................................................................................................. 51 8.1.1.

Maps .............................................................................................................................................................. 51 8.1.2.

8.2. Shift Reports & Operator Logs ......................................................................................................................... 51

8.3. Performance & Maintenance Reports ............................................................................................................. 52

ATMS.now and Tactics System Health .......................................................................................................... 52 8.3.1.

Operator Call Log ........................................................................................................................................... 53 8.3.2.

ATMS Infrastructure Preservation ................................................................................................................ 53 8.3.3.

MIMS ............................................................................................................................................................. 53 8.3.4.

8.4. Reports (Deliverables) ...................................................................................................................................... 53

8.5. Monthly Dashboard .......................................................................................................................................... 54

8.6. Progress Meeting Requirements ...................................................................................................................... 54

Regional Coordination .................................................................................................................................................. 55 9.

9.1. Partner Agency DMS Notification ..................................................................................................................... 55

ADMS Messaging for Freeway Events ........................................................................................................... 55 9.1.1.

vi

Active Arterial Management TMC Standard Operating Guidelines

Documentation ............................................................................................................................................. 56 9.1.2.

9.2. Interagency Coordination ................................................................................................................................. 56

Clear Speak/Plain Language .......................................................................................................................... 56 9.2.1.

Detection & Monitoring Plan ........................................................................................................................... 57 10.

10.1. Applications and Systems ................................................................................................................................. 57

CCTVs ............................................................................................................................................................. 57 10.1.1.

ITS Field Device Security Monitoring ............................................................................................................. 57 10.1.2.

Motorist Calls ................................................................................................................................................ 58 10.1.3.

Travel Time Subsystems (TTS) ....................................................................................................................... 59 10.1.4.

ATMS.now and Tactics Advanced Signal Management Software ................................................................. 60 10.1.5.

10.2. Active Signal Timing Plan Adjustments ............................................................................................................ 61

InSync Adaptive Signal Systems .................................................................................................................... 63 10.2.1.

Event Management .......................................................................................................................................... 64 11.

11.1. Incident Management Protocol ....................................................................................................................... 64

11.2. Roadwork Event Management ......................................................................................................................... 64

11.3. Hurricane/Emergency Preparedness ............................................................................................................... 66

11.4. Severe Weather ................................................................................................................................................ 68

11.5. Data Entry ......................................................................................................................................................... 70

11.6. Police-Escorted Motorcades ............................................................................................................................ 74

11.7. Interagency Event Management ...................................................................................................................... 75

Notification & Incident Response Plan ............................................................................................................. 76 12.

12.1. Emergency Agencies ......................................................................................................................................... 76

12.2. AAM Management ........................................................................................................................................... 77

High Profile Events ........................................................................................................................................ 77 12.2.1.

Signal Timing Plan Library ............................................................................................................................. 77 12.2.2.

12.3. FDOT Maintenance ........................................................................................................................................... 78

Traffic Signals ................................................................................................................................................ 78 12.3.1.

Documentation & Reporting ......................................................................................................................... 79 12.3.2.

12.4. External Agencies ............................................................................................................................................. 80

Railroad Agencies .......................................................................................................................................... 80 12.4.1.

Transit Agencies ............................................................................................................................................ 80 12.4.2.

12.5. Documentation................................................................................................................................................. 80

vii

Active Arterial Management TMC Standard Operating Guidelines

List of Tables

Table 1. AAM CCTV List ........................................................................................................................................................ 25 Table 2. AAM ADMS List ....................................................................................................................................................... 26 Table 3. AAM MVDS List ....................................................................................................................................................... 28 Table 4. AAM Bluetooth List ................................................................................................................................................ 29

List of Figures

Figure 1. AAM Room Layout ................................................................................................................................................... 4 Figure 2. Example of Incident Screenshot............................................................................................................................. 14 Figure 3. Example iNWS Alert ............................................................................................................................................... 68 Figure 4. Example iNWS Map and Description ..................................................................................................................... 69

Appendices

Appendix A SunGuide v6.0 Operator Training Slides Appendix B SunGuide v6.0 Administrator Training Slides Appendix C Sample Shift Report Appendix D Sample Citizen Complaint Forms Appendix E Active Arterial Management Dashboard Appendix F Maintenance Checklist & Work Order Forms Appendix G New Hire Access Forms

viii

Active Arterial Management TMC Standard Operating Guidelines

List of Acronyms

AAM …………………………………………………………………...……………………………………………Active Arterial Management ADMS ……………………………………………….……………...……………………………………………Arterial Dynamic Message Sign AAM …………………………………………………..……………...……………………………………………Active Arterial Management ATE ………………………………………………………………………………...……………………………………………Active Traffic Event ATMS …………………………………………………………………………………………………Advanced Traffic Management System AVI …………………………………………………………………..……………………………………..Automatic Vehicle Identification CCTV ……………………………………………………………………………………………………………………….Closed Circuit Television CFX ……………………………………………………………………………………………………Central Florida Expressway Authority DMS …………………………………………………………………..…………………………………………………….Dynamic Message Sign DSS …………………………………………………………………..………………………………………………… Decision Support System FD ..………………….…………………………………………………………………………………………………………… Fire Department FDLE ………………………………………………………………………………………………Florida Department of Law Enforcement FDOT ………………………………………………………………………………………………….Florida Department of Transportation FHP …………………………………………………………………….……………………………………………………Florida Highway Patrol FLATIS ……………………………………………………………………………………….Florida Advanced Traffic Information System FMP ……………………………………………………………………………………………………………Freeway Management Program FTE ………………………………………………………………………………………………………………..Florida’s Turnpike Enterprise HAZMAT …………….……………………………………………………………………………………………………………. Hazardous Materials ITS …………………………………………………………………………………………………………Intelligent Transportation System ITMS …………………………………………………………………………………………………….Interim Traffic Management System IVEDDS ………………………………………………………………………..Interagency Video and Event Data Distribution System LLC …………………………………………………………………………………………………………………….Limited Liability Company MOU ………………………………………………………………………………………………………….Memorandum of Understanding MIMS …………………………………………………………………………………..Maintenance Information Management System MUTCD ………………………………………………………………………………………….Manual on Uniform Traffic Control Devices MVDS …………………………………………………………………………………………………..Microwave Vehicle Detection System NMS …………………………………………………...................………………………………………..Network Management System PDF …………………………………………………………………………………………......………………….Portable Document Format RISC ……………………………………………………………………………………………………………Rapid Incident Scene Clearance RTMC ……………………………………………………………………………………………………Regional Traffic Management Center SIRV ………………………………………………………………………………………………………..Severe Incident Response Vehicle SO ……………………….…………………………………………………………………………………………………………… Sheriff’s Office SOG …………………………………………………………………………………………………………….Standard Operating Guidelines SIRV ………………………………………………………………………………………………………..Severe Incident Response Vehicle TIM ……………………………………………………………………………………………………………….Traffic Incident Management TMC ………………………………………………………………………………………………………………….Traffic Management Center TSM&O …………………………………………………………………………Transportation Systems Management and Operations TTS ………………………………………………………………………………………………………………………………Travel Time System

1

Active Arterial Management TMC Standard Operating Guidelines

INTRODUCTION 1. These Standard Operating Guidelines are for the Orlando Regional Traffic Management Center (RTMC) Active Arterial Management (AAM). They are intended to be supplemented by more detailed instructions provided in SunGuide training and supporting documents and other reference material such as the Manual on Uniform Traffic Control Devices (MUTCD). These guidelines should be referenced regularly by operations staff.

NOTE: This guide will often refer to concepts by established acronyms or short names. For a complete list of acronyms and short names, please reference the List of Acronyms.

2

Active Arterial Management TMC Standard Operating Guidelines

GENERAL OVERVIEW 2.

2.1. RTMC AAM Mission Statement The Active Arterial Management program is designed to provide a higher level of service, accurate traveler information and safer arterial roadways for the motorists in Central Florida by dedicating human and technology resources through different avenues using Intelligent Transportation Systems, signal system control, and other management and operational strategies to monitor, identify and address the causes of congestion on a real-time basis.

2.2. Scope of Work The Orlando RTMC AAM is tasked with the monitoring and reporting of traffic conditions on important arterial roadways within the Florida Department of Transportation’s (FDOT) District 5, which includes the following counties: Orange, Osceola, Seminole, Volusia, Brevard, Flagler, Lake, Marion and Sumter. This facility operates in conjunction with a state law enforcement communications center, and as such, it operates at from 6:00 AM to 10:00 PM on weekdays, and 8:00 AM to 8:00 PM on weekends for all days of the year.

Work is performed using a variety of devices, systems, and software to detect and respond to planned and unplanned events that arise on the roadways, and to mitigate their effects. Because roadways in the district are the primary source of conveyance for goods and people, it is imperative to the economic vitality and general wellbeing of the region to ensure that traffic flows safely and efficiently.

The Orlando RTMC AAM provides coverage for critical FDOT-selected arterial roadways within District 5 including, but not limited to State Roads. Several other counties and municipalities operate their own Traffic Management Centers, handling their own important thoroughfares. Currently, the Orlando RTMC AAM provides real-time traffic information for:

HNTB AAM Corridor Limits

Corridor Jurisdiction Mile Posts

SR 50 Kirkman Rd. – Ferguson Dr. (12 – 14)

Kirkman Rd. Carrier Dr. – SR 408 (0 – 7)

John Young Pkwy. Sand Lake Rd. – Hardwood St. (0 – 40)1

Orange Blossom Tr. W Taft Vineland Rd. – Amelia St. (5 – 14)

Sand Lake Rd./McCoy Rd. Turkey Lake Rd. – Jetport Dr. (0 – 8)

US 17/92 Firehouse Rd. – Beresford Ave. (10 – 12)

1 John Young Parkway, from Sand Lake Road to Church Street is maintained by Orange County and does not have Mile Post designations.

3

Active Arterial Management TMC Standard Operating Guidelines

Atkins AAM Corridor Limits

Corridor Jurisdiction Mile Posts

SR 436 SR 434 – US 17/92 (3 – 7)

SR 50 Old Cheney Hwy. - SR 423 (5 – 15)

SR 46 International Pkwy. - Airport Blvd. (4 - 7)

US 17/92/Mills Ave. SR 50 - Airport Blvd. (3 - 10)

SR 424 SR 50 – John Young Pkwy. (0 - 5)

SR 414 US 17/92 - Bear lake Rd (2 - 37)

SR 434 Calumet Dr. - US 17/92 (7 - 9)

SR 423 SR-50 - Orange Ave. (0 - 10)

Orange Blossom Tr. SR 50 - Lee Rd. (0 - 3)

2.3. RTMC AAM Layout The RTMC AAM occupies a separate room across the hallway from the Orlando RTMC. The Orlando RTMC is collocated at the Florida Highway Patrol (FHP) center for state law enforcement dispatch, an entity consisting of dispatchers for FHP Troop D, Florida Fish and Wildlife Commission (FWC), the State Fire Marshall, and the Florida Department of Law Enforcement (FDLE). The AAM room has a total of six computer workstations, two are operator workstations and four computer workstations are dedicated to the individual agency ATMS systems as shown in the room layout diagram in Figure 1. The video wall has two television monitors along the far side wall above the agency workstations.

4

Active Arterial Management TMC Standard Operating Guidelines

Figure 1. AAM Room Layout

2.4. RTMC AAM Operations Managers Steven Mikesell and Paul Mannix, the RTMC AAM Operations Managers, are responsible for overseeing the daily operations of the RTMC AAM. Their responsibilities consist of all work necessary to provide for the general management, oversight, QA/QC, and administration of the contract by the Vendor’s management and management support personnel.

2.5. RTMC AAM Signal Timing Engineer The RTMC AAM Signal Timing Engineer oversees operations, directing RTMC Operators and assures all incidents are handled according to FDOT and CFX policies. The AAM Traffic Signal Timing Engineer manages the daily operational activities of the AAM in accordance with the AAM SOG, protocols and policies, and is responsible for the overall operations and functionality of the AAM. They are required to make decisions pertaining to the AAM operations requiring a high degree of experience and judgment, and must facilitate the smooth and balanced operation of the TMC. They are responsible for the development of training manuals, updating the SOG manual, coordination with the RTMC, and determining and using existing measures of effectiveness for the TMC in terms of efficiency and effectiveness in providing transportation management, traveler information and incident management.

Pertaining to signal operations, the Signal Timing Engineer is required to provide services in timing plan development/refinement following maintaining agency protocol and practice, development/refinement of special event

AAM Operator Workstation 1

AAM Operator Workstation 2

Video Wall

Orange CountyWorkstation

Osceola CountyWorkstation

Seminole CountyWorkstation

City of OrlandoWorkstation

5

Active Arterial Management TMC Standard Operating Guidelines

timing plans to be implemented as part of the AAM and review signal operations in AAM control sections (left turn phase warrant analyses, queue analyses, etc.).

The Signal Timing Engineers for the HNTB team are Dan D’Antonio and Steven Mikesell. The Atkins team has two subconsultant teams for Signal Timings: 1) Helmuth Arens & Pete Yauch with Albeck Gerken, Inc (AGI), which manages all of the Seminole County corridors, and 2) Doug Petty, Nick Spatola, Kevin Carey, and Rich Jardim with Faller Davis Associates (FDA), which manages the remaining corridors for the Atkins team within Orange County, City of Orlando, City of Maitland and City of Winter Park.

2.6. RTMC AAM Operator The RTMC AAM Operator is responsible for operating the various RTMC system workstations and monitoring traffic conditions. They assist in the development of protocols, standard operating procedures, and ensuring compliance with the FDOT and CFX guidelines and practices.

The AAM Operators are scheduled to work scheduled shifts during the weekdays (Monday – Friday) between the hours of 6:00 AM – 2:00 PM and 2:00 PM – 10:00 PM respectively and on weekends (Saturday – Sunday) between the hours of 8:00 AM – 8:00 PM

For detailed information related to the RTMC AAM and Operator’s duties please see the Appendix G associated with Employment Related Documents.

6

Active Arterial Management TMC Standard Operating Guidelines

OPERATIONS ROOM MANAGEMENT 3.This manual serves as the Standard Operating Guidelines (SOG) for all Active Arterial Management (AAM) Operations in FDOT District 5. AAM staff will refer to this manual for instructions regarding position expectations and requirements. Any issues not covered by this document should be addressed to the appropriate section of the SOGs.

The RTMC AAM for FDOT District 5 operates from the following location:

Orlando RTMC FDOT D5 Urban Office 133 S. Semoran Boulevard, Orlando, FL 32807

The operations control room is the focal point of each facility’s operations. This central position is subject to regular tours and meetings and warrants guidelines in order to maintain professionalism at all times. The commission or omission of any act which constitutes a violation of any of the regulations, directives, policies, or procedures contained herein will be grounds for disciplinary action.

3.1. Rules & Guidelines • No food or drinks are allowed in the control room; only water in a container with a secured lid is

permitted. All food shall be eaten in designated areas at the TMC. • Control room telephones are not to be used for personal phone calls, except under emergency situations. • Personal cell phones and other electronic devices are to be used by operators only during breaks outside

the control room unless otherwise directed by management. • During tours or meetings within the control room, the highest level of professionalism and diligence

to operations is mandatory. • Visitors are not permitted within the control room unless permitted by management, and are only

permitted during break hours. • Standard Operating Guidelines (SOG), reference materials, and equipment are to be kept neatly in place

and readily available at each console. • All consoles must be kept clean and organized. Any work-related items that are normally stored in cabinets

or drawers must be stored properly when not in use. Only work-related material should be visible at each console.

• No profanity or foul language is permitted; proper business etiquette should be upheld at all times. • No sleeping is allowed. If you are unable to stay awake, contact the AAM Operations Manager

immediately. • Only white list approved websites should be accessed. • Removal of any panels at the workstations is prohibited. This should be handled by authorized personnel

only for the purpose of maintaining computer equipment. • Operators are required to come into work with a neat and professional appearance. Any deviation

from the accepted attire must be approved by the AAM Operations Manager.

7

Active Arterial Management TMC Standard Operating Guidelines

Smoking Policy 3.1.1.The Orlando RTMC is a non-smoking facility. No one is allowed to smoke inside the center. However, a smoking patio is located outside the Center. Operators are allowed to smoke only during scheduled breaks.

Drug-Free Workplace 3.1.2.The AAM committed to providing a safe work environment, fostering the well-being and health of its employees. That commitment is jeopardized when any AAM employee illegally uses drugs or alcohol on the job, comes to work with these substances present in his/her body, or possesses, distributes, or sells drugs in the workplace. Therefore, the AAM has established the following drug-free procedures:

VIOLATION STATEMENT It is a violation of Orlando Traffic Signal Operations procedures for any employee to possess, sell, trade, or offer for sale illegal drugs or otherwise engage in the illegal use of drugs, intoxicants, or alcohol on the job. It is a violation of Orlando Traffic Signal Operations procedures for anyone to report to work under the influence of illegal drugs, intoxicant or alcohol. It is a violation of the Orlando Traffic Signal Operations procedures for anyone to use prescription drugs illegally. However, nothing in this procedure precludes the appropriate use of legally prescribed medications. A violation of this procedure is subject to disciplinary action up to and including termination of employment.

Operator Conduct 3.1.3.Employees of the AAM are expected to present a professional image and demeanor. Common courtesy and respect for all personnel within the building is expected of all AAM employees. Loud talking, yelling, and other disruptive behaviors are not permitted at any time. Remember the AAM is co-located with a state law enforcement dispatch center and such disruptive behaviors can have serious implications on dispatch operations.

HNTB expects all employees to behave in a professional manner and demonstrate respect for others at all times. HNTB prohibits unlawful harassment, whether based on race, color, religion, gender, national origin, disability, citizenship status, marital status, age, sexual orientation or other legally protected status. Harassment in all forms, whether verbal, written or physical, is strictly prohibited. All RTMC employees are required to read and follow Core Integrity Policy 103. HNTB Business Integrity Program.

Atkins Code of Conduct for business ethics and compliance has been developed to provide practical guidance and procedures that each employee needs in order to make good business decisions and address the increasingly complex business environment.

The Code of Conduct has been adopted as a statement of our core ethical standards and business values. It addresses general ethics and compliance concepts and gives employees a broad outline of acceptable behavior. The policies and procedures that apply to your job are based on the concepts in the Code.

Every Atkins employee, including the staff that is working within a client office is required to behave in a manner that is consistent with the standards set forth in the code. For further information, please refer to the Atkins Code of Contact portion of the employee handbook.

8

Active Arterial Management TMC Standard Operating Guidelines

Appearance Guidelines 3.1.4.The RTMC AAM is a professional environment, and employees are expected at all times to present a professional, business-like image, and shall exercise good sound judgment in carrying out their duties. Acceptable personal appearance, as well as proper maintenance of work area is an ongoing requirement of employment at the RTMC AAM.

In general, RTMC AAM staff will: • Wear clean and appropriate attire at all times. • Be well groomed. • Be courteous at all times. • No personal cell phones will be used in the TMC. • Wear a picture ID at all times.

3.2. RTMC AAM Control Room Staffing All AAM staff shall work together with all agencies collocated at their respective TMC to effectively manage the transportation infrastructure as specified within this document.

New Hires Due to the exposure of potentially sensitive information within the TMCs as well as TMC security, new employees of all levels are required to fulfill the following requirements and paperwork before reporting for work.

All new hires must complete and submit the following to the FDOT District Arterial Management Systems Engineer or designee:

• Criminal Justice Information System (CJIS) Security & Awareness Training (www.cjisonline.com) o Complete the Level 3 CJIS Security Test & provide certification

• Driver’s License style photograph of the employee • Joint Task Force Law Enforcement Communications State Law Enforcement Radio System (SLERS) clearance

packet: o Application for Security Clearance o HSMV Fingerprint Confirmation (select SLERS) o Personal Inquiry Waiver (Authority for Release of Information)

• Must be completed before a commissioned notary o Non-Disclosure Agreement o Request for Security Level

• FDOT District 5 ITS ID Badge and RTMC AAM Access Card: o All requests are to be coordinated with the RTMC Office Manager or designee

3.3. Scheduling Schedules are created by the RTMC AAM managers. All employees are responsible for knowing when they are to report for work. Scheduling is typically done on a monthly basis and in most cases there will be 2 months’ worth of scheduling available at a time. Each week’s schedule will be posted on the center column for quick reference, and the full-month’s schedule will be available on the R-Drive.

9

Active Arterial Management TMC Standard Operating Guidelines

Time off Requests 3.3.1.RTMC AAM employees who plan on taking time off must complete a Day Off Request Form. The form must be completed at least two weeks prior to the time off and must be approved by the Operations Manager. Requests for time off less than two weeks prior to the time off may not be approved. Time off will be approved on a case-by-case basis within two days of the submittal.

Time off during Holidays, or when multiple operators request the same period of time, will be decided by the Operations Manager. Time off may be canceled if a significant event (such as a hurricane) is forecasted within 24 hours of the beginning of the time off.

Unplanned time off, such as for a death in the family, must be brought to the Manager’s attention immediately. If the Manager observes abuse in unplanned time off requests, documentation may be requested.

For detailed information regarding HNTB’s policies on Leave/Time Off please access the HNTB Intranet under the Human Resources sections for Policies and Procedures. You can also find relevant information for HNTB’s Timekeeping policies in the Appendix G under Employment Related Documents.

The Atkins North America Holdings Corporation and its subsidiaries (the Company) acknowledges the need for employees to balance their time among work, family, personal obligations and other outside commitments, and provides Company-paid time away from work for such reasons. While employees have the freedom to manage the use of their paid time off benefit according to their needs, it is expected that the needs of the Company be also taken into consideration when using this benefit.

To use PTO for scheduled absences, employees must notify their managers as early as possible. To use PTO for unscheduled absences, employees must notify their managers within the first two hours of their expected report to work time, or as soon as possible. The use of PTO is subject to management approval. For further information, please refer to the Atkins Paid Time Off policy #213.0.

Sick Leave 3.3.2.Operators who are ill must call the Operations Manager at least 8 hours before the beginning of their shift. Operators who call in before, during, or after a Holiday or those who call in sick less than 8 hours prior to the beginning of their shift are required to provide documentation of their illness.

Shift Change 3.3.3.A smooth and seamless transition between shift changes is critical to the RTMC AAM operations. The transition of shifts includes a 15 minute overlap at the beginning/end of each shift.

From Sunday Night to Friday Afternoon, the shifts are: 1st Shift is from 6:00 AM to 2:00 PM 2nd Shift is from 2:00 PM to 10:00 PM From Friday Night to Sunday Afternoon, the shifts are: Shift is from 8:00 AM to 8:00PM

10

Active Arterial Management TMC Standard Operating Guidelines

Breaks and Lunch 3.3.4.Employees are encouraged to take breaks and lunch during the course of their shift. Employees may take up to one 15 minute break before their lunch and one 15 minute break following the lunch period. This period cannot be combined with lunch to extend the lunch period. Breaks may be restricted during peak hours, 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 Traffic Signal Operations area due to the immediate availability required of the position and nature of the job duties unless leaving is approved by the Operations Manager.

Overtime 3.3.5.Employees may be required to remain past their regularly assigned schedule if their replacement has not yet reported to work. If this results in overtime, then the employee is compensated at time-and-one-half. All overtime must be approved by the Operations Manager prior to working the overtime hours.

3.4. Operator Shift Start Up Shift start-up procedures ensure that AAM Operators are aware of existing traffic events, unexpected tasks to be completed during their shift, status of all equipment and systems, and any changes to AAM policies and procedures.

• Log into workstation computers using username and password. • Log any active events, issues and changes in policy into the Operator Log for the next Operator to review. If

applicable, brief the arriving Operator. • On Workstation Computer 1 or 2:

o Open the pages from bookmarks to verify any pertinent events and monitor traffic conditions: • Google Maps (https://www.google.com/maps) • Open My Florida 511 website (http://www.FL511.com) • Open the FHP Website (http://www.fhp.state.fl.us/traffic) • Open Waze Map (https://www.waze.com/)

• On Workstation Computer 1 or 2, log into InSync using username and password to verify traffic signal system health

• On Workstation Computer 1 or 2, log into BlueMAC and review the status of the connectivity of all Bluetooth devices,

• Status of the Bluetooth device is shown on the left side. This information lets the user know which devices are active and which are not active.

• The following chart shows the Communication Legend that is associated with the color.

• Check for active status and create MIMS tickets for issues if needed. • Create a MIMS ticket for all Error and Failed Detectors and choose Issue/Task Description.

• On the local agency Workstations, log into ATMS.now and Tactics using username and password to verify traffic signal system health

• On City of Orlando & Seminole County workstations – ATMS.now o Run daily reports,

11

Active Arterial Management TMC Standard Operating Guidelines

• Detector Failure Report • Ped Failure Report • Field Alarms

o Communicate failures determined by reports using the e-mail address established. See Section 10.1.5. • On Orange County workstation – SIEMENS Tactics Central

o Run daily reports, • Local Alarms • Communications Faults • Detector Faults

o Communicate failures determined by reports using the e-mail address established. See Section 10.1.5. NOTE: THIS SECTION WILL BE EXPANDED UPON WITH ADDITIONAL INSTRUCTIONS ONCE THE AAM IS FULLY OPERATIONAL.

3.5. Operator Shift Close Out The shut-down procedures herein ensure that AAM Operators are aware of tasks to be completed at the end of their shift. In addition this procedure will provide the necessary steps required should there be a severe event ongoing at the end of their shift.

• If applicable, brief the arriving AAM Operator regarding any change in policy and active events. • Log any active events, issues, and changes in policy into the Operator Log. • Verify active traffic events, applicable ADMS messages, and FL 511 information for accuracy. Update

active events to reflect their current status. • Log out of all computer applications and systems. (SunGuide, ATMS.now, Tactics, InSync, etc.) • Log out of the computers at their workstation • Enter your hours worked on your timecard, this should be done every day per ATKINS/HNTB policy.

3.6. Access Requirements The Orlando RTMC AAM is a secure area and entrance requires the use of an electronic passkey. No keys will be issued to non-operational personnel. Lost passkeys shall be reported immediately to the Operations Manager so that the card can be deactivated. For visitors and other personnel (contractors, consultants, etc.) to enter the communications or equipment rooms, they will be required to contact FDOT or the appropriate FDOT representative for access. Visitors and/or other personnel must be escorted by someone from FDOT. Appointments shall be made for all maintenance and installation work involving the equipment or communications rooms. All visitors to the equipment or communications rooms must sign in and sign out.

FHP Regulations on RTMC/COMM Center Access 3.6.1.Effective January 1, 2013 an escort is required for any non-approved personnel entering the Regional Communications Center (RCC). Those individuals who have completed the JTF Background Check and the CJIS online awareness training are considered approved personnel and do not need an escort.

When personnel come to the RTMC AAM, they must be identified with credible identification and have their name run through the JTF security website by FHP to confirm that unescorted access is permitted. When more than one person

12

Active Arterial Management TMC Standard Operating Guidelines

arrives together, that will stay together while in the center, only one of the persons needs to be checked. The other personnel will be considered as escorted by the person verified as approved.

Example: If someone from LTG arrives, they must be escorted because we have not performed a background check on LTG personnel, however, if the LTG person is working with a HNTB employee and the HNTB employee has been approved, the HNTB employee is permitted to escort the LTG person in the RTMC AAM. In this situation ALL (including the approved person) must sign the log to enter into the facility.

All RTMC AAM staff, ITS Group employees, FHP and FWC personnel have completed the background investigation and can enter the room without signing the log. All other non- RTMC AAM/FHP/FWC personnel must log in when entering the facility even if an escort is not required.

Location of the log in sheet:

The log in sheet is posted on the outside of the cubicle wall where the FHP Duty Officer Supervisors sit; to the right of their closet doors, near the fire extinguisher.

**If you are ever unsure on what to do please consult the RTMC AAM Managers or FHP for guidance.

To obtain an electronic passkey, each employee must complete the Joint Task Force Security Clearance documents for their FHP background check. All employees must also complete the Criminal Justice Information Services (CJIS) online certification. The CJIS certification ensures that all employees are properly trained on appropriate behavior associated with being exposed to sensitive information that can be transmitted from FHP or other law enforcement agencies. These documents are included in Appendix G under Employment Related Documents.

Incident Command System and the National Incident Management System 3.6.2.All employees working for the State of Florida, any of its 67 counties, or any of its 400+ municipalities, must receive training from the FEMA Institute on the Incident Command System (ICS) and the National Incident Management System (NIMS). These topics were developed in the 1970’s during a reign of destructive wildfires in California as a way of keeping large-scale incidents manageable. Although ICS and NIMS were born from large- scale events, they have been refined over the years to become scalable. ICS and NIMS can be used for any response, no matter how large or small.

Operators are responsible for the following FEMA Institute Courses:

• IS 100 – Introduction to the Incident Command System • IS 200 – ICS for Single Resources and Initial Action Incidents • IS 700 – National Incident Management System • IS 800 – National Response Framework, An Introduction

Florida State Statute 119 (FSS 119): Florida’s Public Record Laws 3.6.3.Pursuant to Florida State Statute 119 (FSS 119)

FSS 119.01 (1): It is the policy of this state that all state, county, and municipal records are open for personal inspection and copying by any person. Providing access to public records is a duty of each agency.

13

Active Arterial Management TMC Standard Operating Guidelines

FSS 119.011 (12): “Public records” means all documents, papers, letters, maps, books, tapes, photographs, films, sound recordings, data processing software, or other material regardless of physical form, characteristics, or means of transmission, made or received pursuant to law or ordinance or in connection with the transaction of official business by any agency. Rule Chapter 71A-1, F.A.C., requires: agency computer users follow agency established guidelines for acceptable use of email and other messaging resources. Furthermore, Policy number 001-325-060, Security and Use of Information Technology Resources prohibits the use of non-departmental email systems (ie AOL, MSN, Yahoo mail) through the department’s network, unless it is specifically approved with Form 325-080-001., Acquiring Information Technology Resources. It also states that in cases where personal e mail accounts are utilized for Department business purposes, copies of any email must be forwarded to an official e-mail account.

Employees of the RTMC AAM will be using Department computers and interacting on phone lines which are recorded. It is of the utmost importance that each individual employee familiarizes themselves with the broad and sweeping public records laws of the State of Florida. Any phone contact with the co-located state law enforcement dispatch center is recorded and subject to disclosure to the public. When calling other agencies by phone, be conscious of the fact that their line may also be recorded. Files stored on Department computers become public record which must be retained by the state for inspection by the public upon demand. Emails sent using the FDOT email system are also considered public record.

While the Department expects users to adhere to the requirements regarding confidential data and information, users should have no expectation of privacy since the data they create or receive on the state network system is the property of the State of Florida and is subject to the requirements of Chapter 119, Florida Statutes, Public Records.

Cameras and Public Record 3.6.4.It is the policy of the Department that cameras are not to be recorded for any reason. Any type of video recording may also be considered public record, furthermore recordings depicting an incident as it happens can be subpoenaed during a civil or criminal proceeding, and the operator in question may be called to testify. In order to avoid the costs and duties associated with retaining video recordings, no employee at any time, or for any reason, may record any video from a Department camera. Incident screenshots, however, are an excellent tool in deciphering positive and negative aspects of incident response and management, and are often used during meetings with other agencies to point out key strengths and areas for improvement (see Figure 2). While incident screenshots are also public record, their retention and maintenance is much simpler.

14

Active Arterial Management TMC Standard Operating Guidelines

Figure 2. Example of Incident Screenshot

Internet 3.6.5.Employees are granted use of state computers and the Internet to carry out the mission of the Department and to promote efficiency and improved communications with our internal and external customers. The Internet should be used for business purposes only and should fall within compliance with the expectations described in the Department’s security policy. Internet access is only authorized through the Department’s proxy server unless specifically approved and documented by the Information Security Manager.

In accordance with Policy Number 001-325-060 Security and Use of Information Technology Resources, employees are prohibited from using IT resources for accessing, sending, storing, creating or displaying inappropriate materials including, but not limited to gambling, illegal activity, sexually explicit materials or materials that include profane, obscene or inappropriate language, or discriminatory, racial, or ethnic content.

Whitelist of Approved Websites • BlueTOAD Bluetooth (TrafficCast Server) • Consultant-related websites (www.hntb.com, owa.hntb.com, wtc.hntb.com, webmail.atkinsglobal.com

connect.na.atkinsglobal.com) • CJIS Online • FL511

15

Active Arterial Management TMC Standard Operating Guidelines

• FLHSMV • Florida's Turnpike • Google • Here.com • INRIX • SIGALERT.com • TrafficCast • Waze • Weather.com

The Office of Information Systems will maintain detailed records of all internet usage for use in detecting abuse or misuse of this resource without notice to employees. For more detailed information please read through the FDOT Security Policy.

DEPARTMENT’S POLICY Each individual accessing Department information technology resources is expected to use good judgment and common sense to avoid abuse and inappropriate use of resources. Employees shall not access, send, store, create, or display inappropriate materials including but not limited to, gambling, any illegal activity, sexually explicit materials, or materials that include profane, obscene, or inappropriate language, or discriminatory racial or ethnic content. STATEMENT ON EXTERNAL DEVICES Any individual authorized to use department computers, and who does so use a department computer, may not insert/connect an unapproved external device. Unapproved external devices include, but are not limited to items such as USB storage devices and phone chargers. Any individual who inserts/connects an unapproved device violates department policy.

Telephone Etiquette 3.6.6.The staff of the RTMC AAM will receive calls from a variety of sources including agencies and the public. All calls will be handled in a courteous and professional manner, regardless of the content of the call and/or the attitude of the caller.

When answering any incoming calls from the outside line, the operator should answer: “Orlando RTMC AAM, this is __________. How may I help you?”

Calls will also be received from the dispatch center co-located with the RTMC. These calls come in through a separate phone line, informally known as the “FHP phone.” This line may be answered simply with “Front desk” and all conversations should be kept short and professional as they are recorded.

Contact with Media and the Public 3.6.7.At no time is it permissible for RTMC AAM staff to comment to the media without the express permission of the RTMC AAM Manager. All media inquiries shall be forwarded to the FDOT Project Manager. Please see the Media Contact document for the procedure on how to handle media contacting the RTMC AAM.

16

Active Arterial Management TMC Standard Operating Guidelines

Social Media Sites 3.6.8.The Department’s Public Information Office is responsible for administering the Department’s social media outreach program and establishing the Department’s social media accounts.

Access to social media sites such as YouTube, Facebook, and Twitter is provided for business purposes. No employee may post content related to Department business except through Department approved accounts and subscription logon credentials.

Any personal use of social media sites must utilize personal account credentials that are not affiliated with the Department. Access to personal accounts must be brief, infrequent, and in compliance with the expectations described previously.

Physical Security and Access to Data Processing Facilities 3.6.9.Information shall be created and maintained in a secure environment. The cost of security shall be commensurate with the value of the information, considering value to both Department and to a potential intruder. Measures with respect to the creation and maintenance of information will be taken to ensure against the unauthorized modification, destruction, or disclosure of information by any person at any location, whether accidental or intentional. Safeguards will be established to ensure the integrity and accuracy of Department information that supports critical functions of the Department, and for which processing capabilities must be provided in the case of a disaster.

Logical and Data Access Controls 3.6.10.Access to and use of the Department’s information technology resources is authorized for a specific individual and must be used exclusively by that individual. This access is managed by assigning authentication controls, a unique user id and password, to each authorized individual who needs access to the Department’s information technology resources.

Access passwords must not be shared or entered by any automatic means, such as with macros. It is the user’s responsibility to protect all of his or her passwords from being disclosed and to refuse identification of any other user’s password.

Passwords which prevent workstations from booting or powering up shall not be used on any Department owned or leased microcomputers or workstations without specific Office of Information Systems (OIS) approval, documentation and control.

Controls shall be established to maximize the accuracy and completeness of data.

Adequate separation of functions must be maintained to help prevent fraud or other unauthorized activity. Test functions shall be kept either physically or logically separate from production functions. Copies of production data shall not be used for testing unless the data has been desensitized or unless all personnel involved in testing are otherwise authorized access to the data.

After a new system has been placed in operation, all program changes shall be approved before implementation to determine whether they have been authorized, tested, and documented.

17

Active Arterial Management TMC Standard Operating Guidelines

Network Security 3.6.11.Computer hardware shall not establish simultaneous network connections between a DOT network and any other non-DOT network unless it is specifically approved with an Information Resource Request, Form No. 325‐005‐01, in accordance with Procedure No. 325‐080‐001, Acquiring Information Technology Resources. Unauthenticated access is prohibited.

Any request to connect an external network to the Department’s data communications network must be documented and approved by the Chief Information Officer. Before connecting, appropriate security controls, such as firewalls, must be implemented to protect the Department’s network from unauthorized access.

Only individuals authorized by a District Information Systems Manager (DISM), the Manager of the Computer Services Office (CSO), and the Manager of the District Information Systems Office (DISO), the Office of Inspector General (OIG), or the Chief Information Officer (CIO) can use voice and data telecommunications diagnostic hardware and software, such as communications line monitors. Use is restricted to testing, monitoring, and troubleshooting, unless specifically authorized in writing for other business related activities by the CIO.

Protection Against Loss 3.6.12.Where technology permits, all Department-owned, leased or managed microcomputers, servers and mobile computing devices must have an anti-virus software program installed, operating, and appropriately updated at all times. The Department provides software for this purpose and distributes updates. Appropriate configurations include real-time protection to support ongoing or background scans whenever a “create, open, move, copy or run” command is performed. This configuration should not be altered by any user. The anti-virus software is identified in the Information Technology Resource Standards, Topic No. 325‐080‐050, available on the Department’s intranet (Infonet). Only outside electronic data, software, or documents that have been approved for use by the Department are permitted. In all instances, electronic data, software, or documents must be scanned for viruses before being used on a Department computer. It is the responsibility of vendors, consultants, or contractors to ensure that electronic media provided to the Department is not infected. Infected electronic media will be returned and will not be accepted by the Department.

Data and software essential to the continued operation of critical agency functions shall be backed up. The security controls over the backup resources shall be as stringent as the protection required of the primary resources.

All information resources identified as critical to the continuity of governmental operations shall have written and cost effective contingency plans to provide for the prompt and effective continuation of critical state missions in the event of a disaster, and these contingency plans shall be tested at least annually.

3.7. Quality Control Quality Control (QC) can be defined as the actions performed to ensure the desired level of quality of a product, service, or process. The goal of high quality is reached by careful planning, proper use of equipment, continued inspection, and corrective action as required. By assessing the quality errors which occur in the TMC, there lies an opportunity to eliminate steps that do not add value and to improve the efficiency of those that do.

18

Active Arterial Management TMC Standard Operating Guidelines

The QC process is an essential task of AAM Operations. Errors which occur in day-to-day tasks need to be identified, collected, reviewed, addressed and corrected. In order to appropriately establish an effective quality control process, the TMC has developed a process to ensure the quality of services and the information provided:

Hourly Checks Every hour a complete quality control check must be done for all roads monitored. This includes the following:

• Visual check of all displayed messages on DMS • Call and listen to all 511 messages • Check Event List for open EMs • Visual check of SunGuide devices on Operator Map • Visual check of all DMS via camera • Monitor CF511 website

For assistance in completing the Quality Control checks, please use the different checklists created for the different roadways available in the RTMC AAM Information folder.

Secondary Traffic Information Sources Throughout District 5 there are several roadways where ITS Devices are no available to verify possible incidents. Because of this fact, the use of secondary traffic information sources is required. These sites are:

Google Traffic

Google Traffic is the use of the Google Maps website while enabling their traffic feature. This traffic data comes from GPS enabled Google Maps for mobile phone users. All of the motorists driving send anonymous bits of data back to Google describing average speed and location.

WAZE.com

The WAZE.com site gathers traffic information from mobile app users as they commute around the Central Florida region. App users can input incident information and provide traffic data as they drive around the city. There is a direct connection available to incorporate Waze data into SunGuide so Operators can use this as a secondary resource for incident notification. Operators are presented with an icon on the Operator Map that indicates a new Waze incident. By clicking on the Waze icon Operators are presented with incident details that they can use to try and verify the event. For a complete look at Waze Standard Operating Guidelines please see the Waze Phase 1 – D5 SOG as of 9- 17-14 on the R-Drive.

For more information on how to register for these sites, please click here.

19

Active Arterial Management TMC Standard Operating Guidelines

MIMS: Maintenance Inventory Management Subsystem

(Click on the icon above for information on how to use the MIMS software.)

MIMS is used by FDOT’s Maintenance Contractor to track all device issues. The RTMC AAM completes a nightly system check of all devices for which it will create MIMS tickets for issues found. MIMS is also used to report network outages throughout the system. FDOT requires the AAM to complete a full system check of all ITS Devices to ensure the stability of the network. The AAM’s ability to operate efficiently requires that we have consistent, sustainable usage of devices. By completing daily checks of all ITS Devices we are consistently informing FDOT and the Maintenance Contractors of problems in our system. We are also tracking the operational status of all devices in our network, which allows both FDOT and the Maintenance Contractor to retain historical data of problem areas and learn what types and brands of devices are better than others. Lastly, FDOT uses the MIMS software to monitor the performance of the Maintenance Contractor. The tickets that we enter on a daily basis along with our comments regarding status updates and the Maintenance Contractor’s response to these tickets record their performance on each device’s issue. FDOT monitors the length of time a MIMS ticket is open and the Maintenance Contractor’s response to ensure that they are abiding by the policies set forth in their contact with FDOT.

To ensure proper notification of device issues, please reference the document titled Notifying Transcore of FDOT Device Issues (SYS Emails).

20

Active Arterial Management TMC Standard Operating Guidelines

Software Applications and ITS Monitoring 4.The following systems and applications are at the disposal of the AAM staff to support their efforts in Active Arterial Management. The following policies should be applied when using these tools.

4.1. ATMS Infrastructure Preservation and Work Zone Monitoring The Florida Department of Transportation (FDOT) has invested in ATMS infrastructure throughout the District and the preservation of this property is a priority for FDOT District 5. ATMS infrastructure includes miles of fiber optic cable, CCTV, ADMS, MVDS, Bluetooth Readers (Bluetooth), AVI, among many others. In order to preserve this infrastructure, a list of projects (with their locations) that can potentially damage ATMS Infrastructure will be provided by FDOT on a weekly basis. It is the responsibility of the AAM Operators to be conscientious of these projects, their respective locations, monitor construction activities, as well as reporting any damage and the party responsible for the damage. In addition to monitoring for preservation purposes, it is important for the AAM Operators to monitor project activity and the impacts on mobility. FDOT will also include weekly updates on the Maintenance of Traffic (MOT) plans within the AAM corridors.

The weekly reports for monitoring work zone mobility and ATMS preservation will include the following information:

• State Road and Local Name • Approximate Location • Direction of Lane Closures • Approved Hours & Dates • Contact Information (if available) • Type of Work – Activity

Proactive use of any available CCTV system can assist in the protection of ATMS infrastructure while monitoring traffic conditions. The CCTV system is intended to ensure safety and mobility to the public and protect FDOT assets by preventing and detecting traffic incidents and infrastructure damages. If construction crews are detected in proximity of ATMS infrastructure along AAM corridors, AAM Operators shall identify and record the time, date, and the name of the company or agency present in the field.

If network failure or damage of infrastructure is detected due to construction crews, the AAM Operator shall position the camera overviewing the construction crew and their equipment to take a screen capture of this image while the contractor is present and proceed to notify the AAM Operations Manager immediately. This screen capture shall be emailed to the FDOT District Arterial Management Systems Engineer and AAM Operations Manager (add other staff as applicable) with a description of the potential system failure or infrastructure damage, name of construction crew’s company or agency, location, date and time of the event.

The CCTV system should only be used to identify incidents occurring within the defined operational area and it should not be used to monitoring outside its operational requirements. The AAM Operator shall be aware that he/she is accountable for the operation of the CCTV system. Any use of the system that is frivolous or for private purposes, or is inconsistent with the SOG is to be considered an act of misconduct.

21

Active Arterial Management TMC Standard Operating Guidelines

Once the AAM Operator has reported the network failure or damage of infrastructure done by a construction crews via email, the AAM Operator shall cross-reference the weekly list of potential projects to identify if the work was an approved lane closure. The AAM Operator will provide this information to the AAM Operations Manager and in turn, the ATMS Program Engineer. This information will be used by FDOT personnel to identify and locate the responsible party at fault.

It is the responsibility of the AAM IT Network Manager to follow the procedures indicated in the Troubleshooting section once he/she receives the email from the AAM Operator.

Weekly reports shall include any ATMS Infrastructure Preservation events reported during the week with their respective information (description of the potential system failure or infrastructure damage, name of construction crew’s company or agency, location, date and time of the event, troubleshooting response and status).

4.2. AAM Software & Devices

SunGuide 4.2.1.The RTMC AAM uses SunGuide, the statewide ITS software platform, as the primary means of collecting, storing, and disseminating information about events on the arterial and freeway networks. SunGuide is a modular system comprised of several subsystems that are integrated to allow for event management, data collection, and field device control.

The main objectives of SunGuide are:

• Traffic Event and Incident Management • Reporting and Tracking Impacts on Roadways • Event Email Alert Notifications • Posting ADMS when applicable • Posting FLATIS Notifications

AAM Operators should refer to Appendix A for Operator Training Slides for SunGuide v6.0.

AAM Administrators should refer to Appendix B for Administrative Training Slides for SunGuide v6.0. The following is a breakdown of the various subsystems that comprise the SunGuide System.

C2C The Center to Center subsystem is currently used to communicate with the 511 FLATIS and BlueMAC/TrafficCast Bluetooth systems. Both incident data and Floodgate recording files are sent via the C2C Module, as well as data collected by the Bluetooth system. The C2C subsystem may also be used to share data between TMCs. The extent of this capability is not yet defined.

CCTV The Closed Circuit Television subsystem allows for control of CCTV cameras on AAM corridors.

22

Active Arterial Management TMC Standard Operating Guidelines

DMS The Dynamic Message Sign subsystem allows for control of the ADMS devices on AAM corridors.

EM The Event Manager subsystem controls the main graphic user interface for AAM Operators to use SunGuide.

GUI Prefs The Graphic User Interface Preferences subsystem collects data regarding each AAM Operators’ SunGuide display preferences.

HAR The Highway Advisory Radio subsystem provides motorist with pertinent and current traveler information through their AM radios. The HAR subsystem is not available at this time.

IDS The Incident Detection System subsystem coordinates systems for event/incident detection within SunGuide. This automated system compares real-time data to established thresholds to detect potential disruptions to traffic conditions.

MAS The Message Arbitration System subsystem organizes incident information to be posted on ADMS signs.

RS The Report System subsystem allows incident and device data to be retrieved using a variety of different filters and queries such as dates, times, and device types.

TSS The Transportation Sensor System subsystem collects and organizes data from vehicle detection sensors on AAM corridors.

TVT The Travel Time subsystem coordinates and calculates the creation of travel times which are posted on ADMS based on TSS data.

VS The Video Switching subsystem allows for control of CCTV video on AAM monitors through the V-Brick System. The VS subsystem is currently unavailable.

VW The Video Wall subsystem coordinates control of the TMC Video Wall inside the RTMC control room. The AAM Room has a video wall with 2 monitors. Camera feeds can be changed on the video wall by using the Video Wall Control in SunGuide. To do this, an operator selects a camera they wish to view on the wall, and drops it into the square they choose.

23

Active Arterial Management TMC Standard Operating Guidelines

ITS Devices 4.2.2.AAM Operators use SunGuide Subsystems for CCTV, ADMS, and TSS to detect, monitor and disseminate event information to the public.

Closed Circuit Television The AAM Room operates 2 CCTV’s on the video wall. CCTV operations are particularly useful in determining the details of traffic incidents, and to monitor scenes to identify and help mitigate the effects of incidents on roadway traffic. The Orlando RTMC operates over 500 Closed Circuit Television Cameras (CCTV). Some cameras which are directly available to the RTMC AAM have pan, tilt, and zoom features, as well as aperture and focus controls. GENERAL CAMERA POLICIES

• Do not direct the camera towards a light source, such as the sun or highway luminaries. This will damage the camera after prolonged or repeated occurrences.

• The height and zoom level of a camera will alter the operator’s perception of how fast traffic is moving. • When using CCTV cameras and working with other operators, do not override a camera without asking

permission from the operator who is currently using that camera. • FDOT’s D5 Headquarters in DeLand are able to view camera feeds. Whenever a viewable incident of

moderate to severe impact occurs, it is necessary to switch these feeds into the DeLand office. CCTV PROTECTION OF PRIVACY POLICY The Protection of Privacy Policy predominantly addresses the usage of CCTV camera images but is not meant solely for this purpose. Usage of the CCTV cameras is the most visible and remains the highest concern regarding the collection and dissemination of the general public’s personal identifying information. The Protection of Privacy Policy creates a set of specific rules, that when implemented, provide a high standard of professionalism in managing personal information profiles. These rules are important to RTMC AAM Operations, because they apply to the collection, use and disclosure of any personal information that may be present in normal RTMC AAM operations with or without CCTV cameras. The Privacy Policy is based upon two principles:

• That an individual has a right to control the dissemination of his/her own personal information. • That standards and controls in the collection, retention, use and disclosure of personal information are

mandatory.

The following is the Orlando RTMC Protection of Privacy Policy as it relates to CCTV Camera Usage:

1. The CCTV system shall be operated by authorized operators only. Operation of this equipment when in service by any other person is strictly prohibited.

24

Active Arterial Management TMC Standard Operating Guidelines

2. Closed Circuit Television (CCTV) cameras and related equipment (surveillance equipment) in the RTMC AAM shall be used for traffic and incident management and information purposes only. This includes, but is not limited to, verification of incidents and traffic congestion, maintenance of traffic, disabled vehicles, environmental conditions, and emergency assistance. No one, including RTMC operators and their managers, shall use the system for any other purpose.

3. The authorized operators shall obey all federal and state privacy laws. For example, surveillance of private property and use of the system with the intent of invading privacy of those individuals that could be observed through surveillance cameras is strictly prohibited, even as a demonstration of the system’s technical capabilities.

4. All requests from the media or general public for incident information shall be forwarded to the FDOT Project Manager.

5. Recording of CCTV video is not permissible. No recording devices shall be allowed to be connected to computer equipment or raw video feeds. The following are general guidelines to assist staff in the implementation of this policy:

Zooming in of CCTV Cameras:

• CCTV cameras must not be zoomed in during routine traffic monitoring to the extent that license plates and persons are identifiable.

• When personal injuries or a hazardous materials spill are suspected in a traffic accident, zoom in to collect the information required by FHP and EMS operators.

• Immediately after an incident is cleared, return camera to a wide-angle view to observe traffic conditions. Return to Pre-Set image.

Click here for an informational document on using the USB Joysticks. Click here for an informational document on how to set a camera preset. As part of the day-to-day operational procedures, AAM Operators are required to turn the CCTV cameras frequently for increased panoramic view and coverage of the roadway. Through the SunGuide interface, the Surveyor Direct Control Software allows AAM Operators to also perform tours based on preset camera views. Presets are used to complement the AAM Operator’s physical and routine manipulation of the cameras.

Proactive use of CCTV cameras helps to improve the AAM’s incident management productivity, dispatch, response times, and performance measures by providing early detection, incident verification, and increased visual coverage.

By using the SunGuide Camera Control and Video on Display, AAM Operators can move a camera, check the operational status of the camera, store presets, and lock the camera preventing others from using the camera.

Video monitors in the TMC allow the operators to visually verify traffic incidents. CCTV cameras must be properly operated at all times to maintain agency performance and credibility. The public may be viewing still-frame images and video feeds from the media and/or internet on a regular basis. The following procedures shall be adhered to unless specific approval is granted by the AAM Operations Manager to alter.

25

Active Arterial Management TMC Standard Operating Guidelines

When incidents have been verified via the monitors or when a report of an incident has been received, the TMC will determine what initial response is needed. After initial evaluation of the scene, the cameras will be used to monitor incident related congestion and lane blockage by incident responders. TMC may continue to control the cameras during the incident and it may be necessary to zoom into the scene for more specific evaluation. If needed, the Operator can block the camera via SunGuide to the 511 site and other external agencies.

The following are all of the CCTVs deployed and utilized as part of the AAM with their associated SunGuide ID numbers and locations:

Table 1. AAM CCTV List Device ID Roadway Cross Street

C-D1 I-4 EB SR 482 (Sand Lake Rd) C-D2 I-4 WB SR 482 (Sand Lake Rd) C-D3 I-4 WB W of Universal Blvd C-D4 I-4 Universal Blvd EB C-D5 I-4 Universal Blvd WB C-D6 I-4 EB SR 435 (Kirkman Rd) C-D7 I-4 EB W of SR 91 (FL Turnpike) C-D8 I-4 EB SR 91 (FL Turnpike) MM 76.3 C-D9 I-4 WB Conroy Rd MM 77.7

C-D10 I-4 WB W of CR 423 (JYP) C-D11 I-4 EB CR 423 (JYP) C-D12 I-4 WB W of US 441 (OBT) MM 80.2 C-D13 I-4 EB US 441 (OBT) MM 80.5 C-D14 I-4 EB Michigan Ave MM 81.0 C-D15 US 441 (OBT) 39th Street C-D16 US 441 (OBT) South Street C-D17 SR 50 US 441 (OBT) C-D18 SR 423 NB SR 50 C-D19 SR 423 NB Millenia Blvd

C-OC20 McCoy/Boggy Creek Rd Jetport Dr C-OC21 SR 50 Pine Hills Rd C-OC22 SR 424 (Edgewater Dr) Clarcona Ocoee C-OC23 SR 424 (Edgewater Dr) Fairbanks Ave C-OC24 SR 434 (Forest City Rd) All American/Kennedy Blvd C-OC25 CR 423 (JYP) Consulate Dr C-OC26 CR 423 (JYP) Oak Ridge Rd C-OC27 CR 423 (JYP) SR 482 (Sand Lake Rd) C-OC28 CR 423 (JYP) SR 528 W C-OC29 SR 435 (Kirkman Rd) Old Winter Garden Rd

26

Active Arterial Management TMC Standard Operating Guidelines

Device ID Roadway Cross Street C-OC30 SR 423 (Lee Rd) SR 424 (Edgewater Dr)

C-OC31 US 441 (OBT) SR 482 (Sand Lake Rd) C-OC32 US 441 (OBT) Holden Ave C-OC33 US 441 (OBT) Oak Ridge Rd C-OC34 SR 482 (Sand Lake Rd) International Dr C-OC35 SR 482 (Sand Lake Rd) SR 527 (Orange Ave) C-OC36 SR 482 (Sand Lake Rd) Turkey Lake Rd C-OC37 SR 482 (Sand Lake Rd) Universal Blvd

C = CCTV, D = FDOT D5, OC = Orange County

Arterial Dynamic Message Signs Motorists need to be informed of real-time incidents and confirmed lane blockage, such as crashes, disabled vehicles, and work zones so that they can consider alternate routes to avoid delays. ADMS are strategically located throughout the AAM corridors to disseminate information to motorists. The messaging matrix is based on two main criteria: structure and content. It is critical to develop and use consistent messaging that will allow quicker recognition by passing motorists over time. Structure and content are based on what can be read by the lowest denominator, in this case, the motorist driving at the highest rate of speed. The structure and content of the developed library matrix was based on using the ADMS for dual phase messaging. The message content must contain enough information that enables the motorist to make an informed decision, while still fitting on the sign. The following are all of the ADMS that can be utilized as part of the AAM with their associated SunGuide ID numbers and locations:

Table 2. AAM ADMS List

Device ID Roadway Cross Street D-SC1 EB SR 436 W of SR 434

D-SC2 WB SR 436 E of SR 434

D-SC3 EB SR 436 E of Montgomery

D-SC4 WB SR 436 E of Hattaway

D-SC5 EB SR 436 E of Hattaway

D-SC6 EB SR 436 W of Anchor

D-SC7 WB SR 436 E of Oxford

D-SC8 EB SR 436 S of Wilshire

D-SC9 NB US 17/92 S of Fernwood

27

Active Arterial Management TMC Standard Operating Guidelines

Device ID Roadway Cross Street D-SC10 SB US 17/92 N of Live Oak

D-SC11 SB US 17/92 N of SR 434

D-SC12 NB US 17/92 S of Lake Mary

D-SC13 NB US 17/92 S of SR 434

D-SC14 WB SR 434 E of Raymond

D-SC15 EB SR 434 W of Douglas

D-SC16 EB SR 434 W of US 17/92

D-SC17 WB SR 434 E of US 17/92

D-SC19 EB SR 46 W of International

D-SC20 WB SR 46 E of Rinehart

D-SC21 EB CR 46A W of International

D-SC22 WB CR 46A E of Rinehart

D-SC26 EB Lake Mary Blvd W of US 17/92

D-SC27 SB US 17/92 S of Airport

D-SC28 WB SR 434 N of SR 414

D-SC29 EB SR 436 W of CR 427

D-SC30 WB SR 436 E of CR 427

D-CO1 SB Hughey Ave W of SR 50

D-CO2 SB SR 527 E of Concord St

D-CO3 WB South St Liberty Ave

D-CO4 I-4 WB Off-ramp Anderson St

D-CO5 I-4 EB Off-ramp South St

D-CO6 EB Anderson St I-4 EB On-ramp

D-CO7 WB South St E of Garland Ave

D-CO8 WB South St Boone Ave

D-CO9 NB Universal Blvd S of International Dr

D-CO10 SB Kirkman Rd N of International Dr

D-CO11 WB Oak Ridge Rd E of International Dr

D-OC1 EB SR 482 (Sand Lake Rd) W of I-4

D-OC2 WB SR 482 (Sand Lake Rd) E of I-4

D-OC3 NB CR 423 (JYP) S of I-4

D-OC4 NB US 441 (OBT) S of I-4

D-OC5 EB SR 423 (Lee Rd) W of I-4

D-OC6 WB SR 423 (Lee Rd) E of I-4

D = ADMS, SC = Seminole County, OC = Orange County

28

Active Arterial Management TMC Standard Operating Guidelines

Transportation Sensor Subsystem FDOT District 5 AAM has deployed above ground roadway detectors. These detectors are strategically placed based on type and detection radius throughout the AAM corridors to detect incidents and variations in traffic conditions.

SunGuide allows AAM Operators to view real-time average roadway speed and occupancy on the SunGuide Operator Map by translating data collected by the sensors into colored bands on the corresponding roadways. The operator may view the current traffic conditions for a specific link by double clicking on a link in the SunGuide Operator Map. The TSS Details panel will open and display the appropriate information for that particular device “link.” The TSS Subsystem collects and stores this data and in conjunction with the TVT subsystem, provides travel time information.

The three types of devices deployed are as follows:

MICROWAVE VEHICLE DETECTION SYSTEMS

MVDS use constant microwaves to determine speed and occupancy within a programmed detection zone for up to eight lanes. Within the TSS Details panel for MVDS, the top number represents the “rolling average” and the bottom number represents the most recent value from the detector.

The following are all of the MVDS deployed and utilized as part of the AAM with their associated SunGuide ID numbers and locations:

Table 3. AAM MVDS List Device ID Roadway Cross Street

M-D14 US 17/92 SR-50 M-D25 US 441 W Taft Vineland Rd M-D41 Kirkman Rd Between SR 408 and Florida Turnpike M-D44 US 441 W Taft Vineland Rd WB app. M-D45 US 441 W Taft Vineland Rd EB app. M-D46 SR 414 Magnolia Homes Rd. M-D47 SR 414 CR 427 M-D48 SR 423 N/O SR 50

M-D49 SR 50 Between Kirkman Rd and SR 423 M-D50 SR 50 W/O US 17/92

M = MVDS, D = FDOT D5

BLUETOOTH

Bluetooth readers work exactly the same as the AVI, but instead of a toll road reader, works off of select Bluetooth activated devices within the vehicle. The following are all of the Bluetooth deployed and utilized as part of the AAM with their associated SunGuide ID numbers and locations.

29

Active Arterial Management TMC Standard Operating Guidelines

Table 4. AAM Bluetooth List Device ID Roadway Cross Street

FDOT Devices B-D1 SR-482 I-4 EB Entrance Ramp B-D2 SR-482 Universal Boulevard EB B-D3 SR-482 Universal Boulevard WB B-D4 SR-482 Fire Station 52 B-D5 SR-482 CR 423 (JYP) B-D6 SR-435 Carrier Drive B-D7 SR-435 International Drive B-D8 SR-435 Eaglesmere Drive B-D9 SR-435 L.B. McLeod Road

B-D10 SR-435 Raleigh Street B-D11 SR-435 Old Winter Garden Road B-D12 SR-435 SR 408 WB Ramp B-D13 SR-435 SR-50 (Colonial Drive) B-D14 CR-423 33rd Street B-D15 CR-423 First Baptist Church B-D16 CR-423 C.R. Smith Street B-D17 SR-423 W.D. Judge Drive B-D18 SR-423 Heatherington Road B-D19 SR-423 US-441 (OBT) B-D20 SR-423 SR-424 (Edgewater Drive) B-D21 SR-423 Adanson Street B-D22 SR-423 Aldrich Avenue B-D23 US-441 Americana Boulevard B-D24 US-441 Redman Street B-D25 US-441 43rd Street B-D26 US-441 35th Street B-D27 US-441 22nd Street B-D28 US-441 Grand Street B-D29 US-441 South Street B-D30 US-441 Country Club Drive B-D31 SR-414 Rose Avenue B-D32 SR-414 SR-434 (Forest City Rd) B-D33 SR-414 SR-400 (I-4) B-D34 SR-414 W. of Maitland Avenue B-D35 SR-414 E. of Maitland Avenue B-D36 SR-434 SR-424 (Edgewater Drive) B-D37 SR-434 Faulkner Road

30

Active Arterial Management TMC Standard Operating Guidelines

Device ID Roadway Cross Street B-D38 SR-434 Lotus Landing /Trailwood Drive B-D39 SR-434 Orange Avenue B-D40 SR-50 Hastings Street B-D41 SR-50 Fairvilla Avenue B-D42 SR-50 Ferguson Drive B-D43 SR-50 North Tampa Avenue/Country Lane B-D44 SR-50 I-4 WB Exit Ramp B-D45 SR-50 Highland Avenue B-D46 SR-50 Bumby Avenue B-D47 SR-50 Bennett Road/Rickenbacker Drive B-D48 SR-50 SR-436 (Semoran Blvd) B-D49 US-17/92 SR-50 (Colonial Drive) B-D50 US-17/92 Lake Highland Drive B-D51 US-17/92 Camellia Avenue B-D52 US-17/92 W. Canton Avenue B-D53 US-17/92 Monroe Avenue B-D54 US-17/92 Maitland Avenue B-D55 US-17/92 Mayo Avenue/Greenwood Drive B-D56 US 17/92 S/O Firehouse Rd B-D57 US 17/92 S/O Taylor Rd B-D58 US 17/92 Carroll Ave.

Seminole County Devices 1026 SR 434 South of Trailwood Dr 1042 SR 434 North of Orange Ave 1390 SR 434 SR 436 1419 SR 434 North of Sand Lake Rd 1433 SR 434 Wekiva Springs Rd 1397 SR 434 Douglas Ave – Markham Woods Rd 1049 SR 434 (low) I-4 West 1440 SR 434 (high) I-4 West 1402 SR 434 Springwood Cir 1449 SR 434 Rangeline Rd 1418 SR 434 Ronald Reagan Blvd 1453 SR 434 US 17-92 1399 SR 436 Montgomery Rd 1412 SR 436 East of Montgomery Rd 1427 SR 436 Westmonte Dr 1406 SR 436 I-4 West

31

Active Arterial Management TMC Standard Operating Guidelines

Device ID Roadway Cross Street 1441 SR 436 East of I-4 1431 SR 436 East of Festival Dr 1457 SR 436 Palm Springs Dr 1423 SR 436 Maitland Ave 1035 SR 436 East of Hermits Trl 1387 SR 436 Ronald Reagan Blvd 2959 SR 436 Anchor Rd 1451 SR 436 US 17-92 1411 US 17-92 Spartan Dr 1443 US 17-92 North of North ST 1439 US 17-92 Sunnytown Rd 1429 US 17-92 Dog Track Rd 1392 US 17-92 Silkwood Ct 1424 US 17-92 Lake Mary Blvd 1416 US 17-92 Airport Blvd 1039 SR 46 West of Bernini Way 1040 SR 46 I-4 West 1444 SR 46 West of Elder Rd 1051 SR 46 East of W 1st St

B = Bluetooth, D = FDOT D5

Websites 4.2.3.The AAM uses various websites to assist with day to day activities within the control room. Each of these sites provides useful information which enables the AAM Operators to effectively manage their responsibilities. The following websites are utilized every day within the AAM:

My Florida 511 The My Florida 511 site is an essential resource of the AAM. By periodically checking this site, the AAM Operators can check on live traffic alerts and information on the interstates surrounding the AAM corridors.

• http://fl511.com

Waze The Waze 511 site is another essential resource of the AAM. By periodically checking this site, the AAM Operators can check on live traffic alerts that are submitted by the public to investigate potential impacts on AAM corridors.

• https://www.waze.com

32

Active Arterial Management TMC Standard Operating Guidelines

FHP Event List The FHP Event list provides useful information on incidents that were responded to and assisted by the Florida Highway Patrol. The main purpose of the site is to inform Operators of possible events and to obtain the FHP Incident Number of these incidents.

IVEDDS The Interagency Video and Data Distribution System (IVEDDS) site allows AAM partner agencies to view active traffic events. Since this site mirrors the AAM event list, it is crucial that the quality of the data being presented is entered correctly and checked regularly. The AAM Operator should ensure that dispatch times, comments, and general specifics associated with an event are completely accurate at all times.

• https://smartsunguide.com/ivedds/

TrafficCast – BlueTOAD The TrafficCast BlueTOADTM bluetooth website allows AAM Operators to access traffic information collected by the Bluetooth subsystem outside of SunGuide. It allows operators to generate reports, monitor device functionality, and create new content (nodes, pairs, OD studies, etc.)

• (Server IP Address) – http://XX.XXX.XX.XX/

INRIX The INRIX website publishes traffic conditions and events similar to the SunGuide interface. The system reads real-time travel time information from various probe vehicles along major roadways.

• http://i95.inrix.com/I95/Login.aspx?ReturnUrl=%2fi95

MIMS 4.2.4.The Maintenance and Inventory Management Systems (MIMS) is used to automate, centralize and streamline the maintenance of ITS devices and respective AAM subsystems. MIMS was designed to facilitate the highest levels of system uptime and to be the liaison between operations and maintenance staff.

Upon detection of a new ITS Device failure, a MIMS Trouble Ticket will be created. Click on the MIMS icon, and then log in using your Operator username and password information from SunGuide. Operators will click on the MIMS tab to view current MIMS tickets, check ticket status, and or “Create a Trouble Ticket.”

In the Create Trouble Ticket Screen you will have the choice of selecting:

• Device Type • Device Name • Description • Additional Comments • Weather Conditions and Comments • Device Not Operational

Voiding a Ticket MIMS now allows operations staff to void a trouble ticket if mistakes were made upon entry or a device

33

Active Arterial Management TMC Standard Operating Guidelines

becomes functional again. The creator of the ticket can void the ticket before it has been verified – when the ticket is still in the ‘unconfirmed’ state and has not yet been moved to the ‘unresolved’ state.

• Within the Unconfirmed Trouble Tickets list, the Void Ticket option will be available on the right hand side of all Trouble Tickets the user has created.

• Selecting ‘Void Ticket’ will display the ‘Void Trouble Ticket’ panel. • To void the relevant ticket, select an appropriate comment from the ‘Status Change Description’ drop down

menu, add any additional comments within the ‘Additional Comments’ text box and select ‘Void.’ • To close the ‘Void Trouble Ticket’ panel without voiding the ticket, select ‘Cancel.’

ITS Field Device Damage In the event a field device is hit by a vehicle or is damaged by other means, making the device inoperable, the AAM Operator should notify FDOT Maintenance immediately.

Motorist Call This section of the MIMS page is utilized to document any motorists’ calls about events, such as disabled vehicles, crashes, pedestrians walking, etc. After entering all the appropriate fields in this section, the AAM Operator can create a new event within SunGuide. All calls should be logged within each day’s Shift Report.

Documentation After a MIMS ticket is created or closed in SunGuide, the information must also be logged in the Shift Report.

ATMS.now 4.2.5.Trafficware’s ATMS.now (formerly Streetwise) advanced signal software is used by the City of Orlando and Seminole County to monitor and operate their extensive signal system from the TMC. The software allows Traffic Division staff to actively monitor all online signals’ status and implement timing patterns remotely.

Tactics 4.2.6.SIEMENS Tactis Central is an advanced signal software is used by Orange County to monitor and operate their extensive signal system from the TMC. The software allows Traffic Division staff to actively monitor all online signals’ status and implement timing patterns remotely.

InSync 4.2.7.InSync is an adaptive traffic control system first released by Rhythm Engineering in 2008 which uses artificial intelligence to optimize traffic signals at individual intersections and coordinate signals along arterial corridors to reduce traffic congestion. InSync measures traffic demand, then adapts in real-time by adjusting signal timing each second using global and local optimization logic to move traffic in the most efficient manner possible. InSync systems were deployed by FDOT along two AAM corridors: 1) US 17/92 with 5 traffic signals between Firehouse Road and Beresford Avenue in DeLand, FL (to be managed by the HNTB team), and 2) SR 46 with 10 traffic signals between International Parkway and Airport Boulevard in Sanford, FL (to be managed by the Atkins team). Note: Another corridor recently had InSync deployed, US 92 (International Speedway Boulevard) in Daytona Beach with 22 signals, and will also be managed by one of the AAM teams in the future.

34

Active Arterial Management TMC Standard Operating Guidelines

SynchroGreenTM 4.2.8.SynchroGreen is adaptive traffic signal software used by Seminole County to optimize signal timing for arterials, side streets, and pedestrians through real-time adaptive traffic control. SynchroGreen optimizes for balanced service, maximum progression, and critical movements. The SynchroGreen adaptive system was designed by Trafficware and Naztec, two companies with decades of experience in the traffic industry. Trafficware’s SynchroGreen software solution is designed to reduce motorist travel time, delays, and stops. SynchroGreen maximizes the use of available roadway capacity, while also decreasing fuel consumption and reducing idle times that reduce emissions.

4.3. System Review To ensure adequate functionality, it is the responsibility of all AAM Operators to conduct a complete system review of all software and hardware at the start of their shift. Until the MIMS database can be populated and fully developed, Operators should fill out the daily ITS Device Checklist for all devices monitored. If any problems are detected, a work order form (attached to spreadsheets) should be filled out accordingly and sent to the AAM Operations Manager. Use the following statuses to indicate device conditions:

• Up – fully functional • Down – cannot be accessed/offline • No PTZ – Pan-tilt-zoom features unavailable • Error – any other conditions – provide comments

Once the MIMS database is functional, the following shall apply:

Any system malfunction must be reported in the Help Desk Portal and Equipment (Helpdesk/MIMS Tickets) section of the Shift Report. Operators should note the date & time, system and/or device, error, notified personnel and any general comments.

If the malfunction(s) is a system wide issue, notify the AAM Operations Manager immediately and continue operations normally to the full extent possible.

35

Active Arterial Management TMC Standard Operating Guidelines

Event Evaluation 5.The first step in managing an active traffic event (ATE) detected on the AAM corridors is to determine the severity of the event.

5.1. Personal Injury or Public Safety Concerns The most critical thing to determine when evaluating event severity is whether there is personal injury or risk to public safety, so that the appropriate emergency agencies are advised. In practice, it is not always possible to thoroughly and accurately evaluate event severity. In the event that personal injuries or public risk are suspected but cannot be confirmed, proceed as if they had been confirmed, advising the emergency agencies that are contacted of any assumptions that have been reported to the TMC.

The following are indications to look for when evaluating the severity of an event:

Personal Injuries When a vehicle has evidently just been involved in an accident, assume there is a personal injury if:

• The vehicle has rolled • An occupied vehicle is on fire • The passenger compartment is crushed or dented • A pedestrian or cyclist has been hit • A passenger has been thrown from the vehicle • A passenger is obviously bleeding • Any passengers have not left the vehicle, and one or more are not moving • Someone appears to be trying to help or move a passenger

For an occupied vehicle which does not appear to have been in an accident, assume a medical emergency if: • The vehicle pulls over or stops erratically and the driver appears to be in medical distress.

Risk to Public Safety Consider any of the following on-street situations a risk to public safety.

• An individual in a dangerous position outside of a vehicle, such as: o Attempting to repair a vehicle in a travel lane o An individual walking in the road (not crossing the street)

• A hazard to other road users o A stopped vehicle or object in a travel lane o A vehicle that is being operated in an unsafe manner o A vehicle or roadside fire

• Spills of hazardous materials o Fluid leaked from a vehicle following an accident that could be considered hazardous o If a tanker truck is leaking its contents, look for identification of the substance written on the

36

Active Arterial Management TMC Standard Operating Guidelines

vehicle. • Other circumstances which pose an immediate risk to public safety.

5.2. Severity Levels Some events will involve person injury, risk to the public safety or extensive lane blockage, and will warrant the assistance of multiple agencies, such as local police and fire and rescue. There are three classification levels used in the AAM. When assigning a severity level classification, it is important to take into consideration the total number of travel lanes at the location of the incident. (The SunGuide software automatically generates the Incident Severity depending on the impact to traffic or the total number of travel lanes affected.)

Level 1 – Minor A Level 1 severity event is categorized as minor impact to a roadway. The AAM does not send email Incident Notification for Level 1 severity events. There is no need to alert AAM Management of a Level 1 Incident. Examples are:

• A disabled vehicle located out of the travel lanes • An incident detected in travel lanes, but is in the process of moving out of the roadway.

Level 2 – Intermediate A Level 2 severity event is categorized as impact to the traveled roadway which is estimated to be less than 2 hours with lane blockages, but not a full closure of the roadway. Examples are:

• Vehicle crash in a travel lane(s) • An event involving injuries

Level 3 ‐ Major A Level 3 severity event is categorized as impact to the traveled roadway which is estimated to be more than 2 hours and/or the roadway is fully closed in any single direction. The main distinction of a Level 3 event is the likeliness of significant area-wide congestion. Examples are:

• An event with a fatality • An event involving a Hazmat spill • An event with full roadway blockage

On many occasions the level of severity of an incident will escalate to the next level; however, incidents can never decrease in severity. In the event an Operator is unsure regarding the severity of an event, seek the judgment of the AAM Operations Manager.

Within SunGuide Within SunGuide, an event’s severity is computed automatically by the system and cannot be modified by an operator. Severity is determined by:

• Minor – lane blockage less than ½ hour • Intermediate – lane blockage between ½ hour and 2 hours • Major – lane blockage over 2 hours or a full closure

37

Active Arterial Management TMC Standard Operating Guidelines

5.3. Unique and Unusual Incidents Unique or unusual events are defined as events which are not typical in characteristic to common incidents documented in the AAM. Due to the infrequency of these types of occurrences, it is of the utmost importance that the Operator notifies the TMC Management immediately upon detection or being notified of an incident that falls under this scope. Examples are:

• Natural disaster • Terrorist activity • Suicide attempts

Whether or not an event is determined after the evaluation to fit this guideline, two criteria should be involved: whether there is a personal injury and/or a public safety risk. In these instances, immediately contact the first available TMC Management Official and provide the following information:

• Date and time event was detected/reported and verified • Type of event • Location • Lane blockage • What is involved (vehicles, buildings, bridges, ships, trains) • Emergency vehicles on scene • Estimation of event duration • Who was contacted and/or notified • External devices currently available and being used for the event

o Any CCTVs currently locked for this event should be unlocked

After contacting management, the Operator may be asked to contact FDOT District 5 Public Information Office with the same information.

Following all pertinent notifications, the AAM Operator shall input the event information into SunGuide or the Incident Management Database as an event type “Other.” After the data has been entered, the next step is to obtain approval form the same manager to create a Level 3 Incident Email Alert Notification and a High Profile Event Alert Notification. These notifications are intended to alert partnering agencies that a traffic event has occurred, and to give them the option to respond to the situation earlier than necessary.

5.4. Event Status Groups There are six status groups in which the AAM categorizes events to. It is acceptable to change the status of an event as it progresses. The six status groups are:

Active (with travel lane blockage) An active event with travel lane blockages is an event with lane blockage(s) that has been confirmed via CCTV or local responder. The AAM Operator must have this confirmation from one of these sources before the event can be considered active.

38

Active Arterial Management TMC Standard Operating Guidelines

Active (without travel lane blockage) An active event with travel lane blockages is an event without lane blockage(s) that has been confirmed via CCTV or local responder. The AAM Operator must have this confirmation from one of these sources before the event can be considered active.

Unconfirmed An unconfirmed event is any event that has not been verified via CCTV or local responder.

Unresolved An unresolved event is one that the AAM has managed, but the vehicle remains. Once the vehicle is removed from the scene, its status should be changed to “closed.” Abandoned vehicles are examples of unresolved events.

Closed A closed event is one that the AAM has managed and all vehicles, including responders, have departed the scene. One closed, the event cannot be accessed from the Event List window (SunGuide only).

Other

False Alarm A false alarm event is one that the AAM attempted to locate, but was not found when notified by an outside source.

Void A voided event is one that was created in error or the motorist did not require assistance.

Audit (SunGuide only) An event in the audit status is currently being reviewed and/or amended to correct an error in the event details. This status is used primarily by Managers.

5.5. Secondary Events A crash that occurs because of the congestion or distraction from a prior incident is referred to as a “secondary crash.” An incident is considered secondary if it occurs upstream from the primary incident as is within the duration and queue of the primary incident. Examples include:

• Queue formation at the scene of the event • Driver distraction (rubbernecking) • Emergency Vehicle maneuvers (vehicle placement) Non-recurring congestion is the most common form of

secondary event.

Proactive Action To reduce the chance of secondary crashes, it is the responsibility of the incident response team on scene to direct traffic and removed obstructions from the area as efficiently and safely as possible. By clearing the roadway, the event will create less of a distraction to drivers.

39

Active Arterial Management TMC Standard Operating Guidelines

Traveler information systems such as ADMS, 511, email and text alerts, and other websites help inform drivers of events, providing them with the opportunity to detour the affected area. It is the responsibility of the AAM Operators to continually monitor the triggered traffic queues in all directions and provide regular updates for these systems.

Creating a Secondary Event Secondary events of all kinds require their own event to be created and updated to reflect the appropriate information (i.e. crash vs congestion). Secondary Events should be linked to Primary Events using the appropriate fields (see Appendix A). In SunGuide only, the “Clone Event” option streamlines this process by making an exactly duplicate of the primary event.

40

Active Arterial Management TMC Standard Operating Guidelines

Communication Systems 6.There are multiple ways to communicate incident and traffic information to the traveling public from the AAM. These guidelines will ensure proper and efficient utilization of these systems to provide the most advanced and accurate information to the public. Current systems are:

6.1. Arterial Dynamic Message Signs The ADMS along AAM corridors display incident messages, travel time information, and general public service announcements (PSA) in line with the AAM Operations. They provide motorists with the forewarning to potentially detour lane blocking events, traffic delays, construction work zones, etc. The following procedures are in place to ensure proper usage of the ADMS subsystem within SunGuide:

To Activate Basic instructions to activate ADMS signs consist of a seven step process:

1. Enter the event information into SunGuide 2. Verify the sign message in the prepared Response Plan 3. Verify which signs are chosen & that they are pertinent 4. Activate the Response Plan 5. Review the public website 6. Check the ADMS via CCTV feed(s) 7. Note any errors in the procedures above, if applicable

Whenever possible, SunGuide Response Plans must be used to generate ADMS messages. In absence of an appropriate Response Plan, messages must be selected from the approved message library, or approved by the AAM Operations Manager. In addition, ADMS messages should be posted only for active (confirmed) traffic events.

Monitor Upon activation of an ADMS message, Operators are required to regularly verify that the sign(s) are activated and consistent across the SunGuide website, SunGuide queue manager, and at the ADMS controller (CCTV view) throughout the duration of the event the sign is displaying for.

Update Update event information promptly and renew the Response Plan and ADMS message(s) accordingly. The integrity and accuracy of the ADMS system relies on timely updates that reflect real-time conditions.

Message Removal Once the AAM Operator has confirmed that the event is clear, the ADMS should be cleared immediately. The ADMS message should be cleared prior to closing the event in SunGuide Event Manager. Verify across SunGuide website, queue manager, and at the sign itself that the message has been cleared.

ADMS Messaging Priority Levels 6.1.1.ADMS selections within the SunGuide Response Plans are determined by proximity to the event. In the event of two events on the same roadway, the ADMS should be utilized for the event closest to the sign. In the event of two

41

Active Arterial Management TMC Standard Operating Guidelines

events at the same locations, AAM Operators should use their judgment based on events’ potential effect to traffic conditions on which event to display on ADMS messages.

In general, the priority levels for ADMS messages are as follows:

1. Full freeway closure 2. Full arterial closure 3. Multi-lane blockage on arterial 4. Single lane blockage on arterial 5. Construction Work zones 6. Special events (for appropriate time frame) 7. Travel time information 8. Public service announcements

Two-Phase Messaging & Message Limits 6.1.2.All AAM ADMS in FDOT D5 are limited by two lines, two phases, and 13 characters across (sign pixel ratings allows for 15 but character spaces at the edge must remain blank) due to their size and MUTCD standards; ADMS in XXXXXXXXXX have 3 lines instead if two lines. In the event a message must be created outside of the ADMS Library (AAM Operations Managers alone have this ability), the content should be clear and concise to avoid confusion.

Travel Time Messages 6.1.3.Whenever possible, the default display during AAM hours of operations on ADMS shall be travel time information. Travel time messages will be preempted with other messages based on MAS priority: as follows:

1. Conditions which require motorists to take action or alter their driving, such as emergency events including evacuations or closures required by FDOT, the State Emergency Operations Center, or Homeland Security.

2. Traffic incidents, hazardous and/or uncommon road conditions, severe weather conditions and work zone activities.

Travel time messages are automatically generated, updated and displayed on ADMS by SunGuide and should require no operator intervention. As with any display, is it the responsibility of the Operator to verify all information is accurate and displayed correctly.

In the event inaccurate information is detected, immediately blank the appropriate sign(s) by right clicking on the ADMS icon in the SunGuide map and selecting ‘Disable Travel Time Messages for this Device.” Wait approximately 5 minutes and reactivate the messages via the same steps. If the information is still inaccurate, disable the sign again and create a help desk ticket within MIMS.

Troubleshooting • If travel times are not displayed on any signs – right click on the SunGuide map and select “Travel Times.”

Confirm that the system is not disabled. If the Travel Time screen does not appear, notify a manager and create a detailed help desk ticket within MIMS.

42

Active Arterial Management TMC Standard Operating Guidelines

• If travel times are not displaying on an individual sign – right click on the ADMS icon for the appropriate sign on the SunGuide map, click on TVT Message Generation and confirm that the travel time messages have not been disabled. If they have been disabled, select ‘On’ and confirm a message is properly displayed.

• As all device failures, create Help Desk tickets for problems that cannot be corrected using the protocols above.

ADMS Critical Errors 6.1.4.An ADMS Critical error occurs when the contents of the message displayed are incorrect. Examples of critical errors are signs activated in the wrong direction/location, spelling errors, unusual characters, failing to blank the sign after event closure, and improper content being posted to the sign. When it is discovered that an ADMS is experiencing any critical errors, the following procedures should be followed:

• Immediately clear the sign message • Notify the AAM Operations Manager as soon as possible with a description of the error • If the sign will not clear, notify FDOT Maintenance immediately

Documentation 6.1.5.When an ADMS message has been posted, Operators are required to log the usage and all relevant details in SunGuide and on the Shift Report.

Notification 6.1.6.The AAM generates the contents of the SMART Alert Notifications through the Response Plan Email editor in SunGuide. There are several fields that can be modified within the editor; all information should be verified and accurate to the highest degree before sending these alerts.

• Select the appropriate Subject from the drop-down list in SunGuide o Cleared o Congestion cleared o Active Level 1 o Active Level 2 o Active Level 3 o Active Level 1: Update o Active Level 2: Update o Active Level 3: Update o [Incident Alert] AMBER Alert – future use o [Incident Alert] LEO Alert – future use o [Incident Alert] SILVER Alert – future use

• The Title field should only be changed for Vehicle Alerts (AMBER, LEO, SILVER) or if the event type is Other. • The appropriate event level must be selected from the following All E-mail Groups drop-down list in SunGuide:

o Congestion o Construction o Minor Event o Major Event

43

Active Arterial Management TMC Standard Operating Guidelines

o Significant Event o HAZMAT* o Weather o Special Event o Transit o City/Municipality o Vehicle Alert o Testing

*For Hazmat related events, it is only required to add Hazmat email group to the initial and clearance emails. The email group “Public” is automatically selected for all SMART Alert emails and text messages that are sent out. The only time an Operator should remove the Public Group form the SMART Alert are for alerts that contain sensitive information (if an operator is unsure whether information is classified as ‘sensitive,’ they should check with the AAM Operations Manager).

• Messages must be updated as significant changes occur: o Changes in lane blockage o Congestion extending to the next reference location o Event clearance

• Insignificant updates are unnecessary as it is more important to get real-time information out to the traveling public

• Important details should be added to the Sensitive portion of the email in order to provide additional information to internal partners and management

Each message should be reviewed for accuracy and should be rejected if incorrect. The Operator has the authority to reject any such message within SunGuide. If the Response Plan continues to generate improper messages, notify the AAM Operations Manager and log the instance into the Shift Report.

6.2. The Florida Automated Traveler Information System (FLATIS – 511) Florida’s statewide 511 phone and web based system provides information on roadway conditions such as commuter travel times, construction, lane closures, rashes, congestion and severe weather.

The Florida 5-1-1 System (FL-ATIS) 6.2.1.The Florida 5-1-1 System is a free service provided by the Florida Department of Transportation. Real time traffic information is disseminated to motorists in a variety of ways. Motorists can dial 5-1-1 from any phone and be connected to real time traffic conditions. Callers navigate their way to the information they are seeking by way of voice recognition.

Information becomes available on the Florida 5-1-1 system when an operator at any of the RTMCs in the state activates a response plan with the FL-511 element selected. Therefore, only those events which are published to the Florida 5-1-1 System are relayed to motorists using the service, this helps to cut down on unnecessary information such as disabled vehicles.

The system also has a feature which allows callers to leave feedback about the service, or to report incidents which are not currently published to the system. When a feedback is received for an incident within District 5, the RTMC will receive a call from the office handling caller feedbacks (currently Jacksonville TMC/District 2) with the information.

44

Active Arterial Management TMC Standard Operating Guidelines

Florida 5-1-1 Website 6.2.2.FL511.com is essentially the Florida 5-1-1 System available via an internet browser. This allows motorists to plan ahead before leaving home by checking the website. The focal point of the website is a map which displays all published events as well as estimated travel speeds similar to the speed map on the SunGuide operator map.

FL511.com also allows visitors to see snapshots of camera feeds, updated every 10 to 20 minutes. Message boards and travel times are also displayed with real time information, giving motorists all the tools they need to plan smart.

For motorists who want a customized report every time they use the service, there is My Florida 511. This section of the website allows users to register with a login and password to access customized routes and alert settings. Users can specify which routes they want to hear information for and set alert preferences such as text message or email alerts.

Users can also register their mobile or land-line phone number and hear customized reports while calling from that number.

Maintenance and System Failures 7.The AAM requires reliable performance of all subsystems, communications, and software. An effective failure management plan begins with a maintenance program that deals with the prevention of problems and the rapid resolution when malfunctions occur.

Maintenance is categorized as follows:

• Preventative Maintenance – scheduled actions to keep equipment in good working conditions • Remedial Maintenance – addresses known malfunctions with low priority • Emergency Maintenance – responds to and repairs critical system failures

7.1. System Failures In most cases, AAM Operators will notice an equipment error first, and therefore have a critical role in the maintenance of the system’s equipment. It is the AAM Operators’ responsibility to report equipment failures to AAM Management so that equipment downtime can be minimized. Errors can be detected during established Device Checks, via ATMS alarms or during routine checks. Checks and issues will run from the AAM Operator to the AAM Operations Manager to the appropriate Network Manager to troubleshoot before being sent to the FDOT ITS Maintenance Engineer via a MIMS trouble ticket.

Primary ITS units, such as CCTV, ADMS, and detectors (Bluetooth/ MVDS) are those that are in fixed locations, generally attached to a stationary sign structure, fixed pole, or other permanent mounting system. These devices communicate across the FDOT network to interface with the SunGuide software system. SunGuide maintains a communication link with these devices, and reports errors and failures, graphically and in near real-time. At the beginning of each shift change, AAM Operators should make a full visual examination of these subsystems via SunGuide software (when applicable), and document any noted errors, system failures or other abnormal behaviors. Checks will then be done every shift, as needed. These error reports will then be forwarded to the AAM Operations Manager and/ or AAM IT Network Manager for detailed analysis and troubleshooting, if necessary.

45

Active Arterial Management TMC Standard Operating Guidelines

Secondary ITS units, such as mobile wireless cameras, or other non-fixed devices, may or may not connect directly to SunGuide, and should be checked at least once at the beginning of each shift change by the AAM Operators and checked every two hours subsequent to. Any issues can be logged as above, for reporting and troubleshooting purposes.

Upon discovery of a nonfunctional device, the AAM IT Network Manager will begin troubleshooting the device following these steps. Failure at a step precludes further testing, and thus will require notification and communication with the appropriate FDOT maintenance teams. The AAM IT Network Manager will:

• Ascertain whether there is a network or power interruption at the location. • Check the SunGuide→ Systems Logs to try to fix an incident start time, and any information that the

logs may have. • If it appears that the problem is software related, local SunGuide→ troubleshooting will be

attempted, with escalation to the software vendor (SWRI) if necessary. • If the problem is in fact hardware- related, taking the unit Out Of Service in SunGuide→, and then

attempting to communicate with it using vendor software (when applicable). • Run several diagnostic exercises to test the device, and to see if the error is recoverable. • Attempt to set device back to Active status in SunGuide→. • If any of these steps fail, the Network Manager will coordinate with the contracted maintenance

groups in order to have the unit replaced in the field. Once a replacement device is in the field, the faulty unit can either be returned to the DOT for further diagnostics, or handed over to the warranting entity for replacement.

In case of multiple simultaneous system or device failures, repair prioritization will occur in this order:

• Network Devices [Switches/ Port Servers/ etc.] (failure of communication will mean no communication with devices).

• CCTV (ability to see the roadway is critical in identifying traffic incidents and dispatching assistance). • ADMS (ability to report a major incident to the public is critical to avoiding further delays or incidents). • Detector Devices (detection devices, when taken together, are important to detecting traffic trends

across roadway zones, but are not detailed enough to show specific incident details).

In general, the steps for managing and reporting a system failure are:

• Evaluate the impact of the failure o Identify the problem o Date and time error occurred/was discovered o Note any other equipment problems that might be related

• Take corrective action o Follow troubleshooting procedures in place for known faults o For failures that significantly impair the operations, contact AAM Operations Manager

immediately (i.e. fiber cut).

46

Active Arterial Management TMC Standard Operating Guidelines

• For issues dealing with ITS devices, create a MIMS Ticket in SunGuide.

Traffic Signals 7.1.1.Notify Local Agency per section 12.3.1 Notification.

ITS Field Devices Damage 7.1.2.In the event a field device is physically damaged the AAM Operator shall file a MIMS Ticket and notify FDOT Maintenance immediately.

Documentation 7.1.3.When and equipment failure has been detected and/or reported, it is required to document all details in affected events in SunGuide. In addition, the Shift Report should be updated to reflect occurrence, including error specifics, remedial action attempted, what personnel have been contacted, and the time the equipment became operational (if applicable).

7.2. SunGuide Failure If the SunGuide software system is not operating correctly, traffic events cannot be logged, and ADMS plans and SMART Alerts will not be generated. Different circumstances can result in the system not functioning properly. These include problems with both the hardware and software.

The impact these database problems can have on operations can range in severity; entire system crashes generally require immediate notification, while system errors are usually reported via an Internal Help Desk Ticket and documented in the Shift Report.

In general the steps for managing and reporting a problem or failure within SunGuide are:

• Evaluate the impact of the failure o Determine whether it is the workstation or the software that is malfunctioning o Determine which operational function(s) and other devices are impaired o For minor problems that do not impair operation, log the details and continue to work on the

system • Take corrective action as appropriate

o Follow troubleshooting procedures for known faults o Attempt to clear the problem by:

• Restarting SunGuide • Restarting the computer

• Notify the AAM Operations Manager of occurrence o Depending on the severity of the problem and time of day, the AAM Operations Manager shall

contact the appropriate personnel to ensure the issues is resolved o Upon direction of the AAM Operations Manager, the Operator may be requested to open an Internal

Help Desk Ticket o In most cases, errors which occur in SunGuide are managed by the RTMC AAM IT Network

Manager.

47

Active Arterial Management TMC Standard Operating Guidelines

Documentation 7.2.1.When a SunGuide error has been detected and/or reported, it is required to document all details. In addition, the Shift Report should be updated to reflect the occurrence, including error specifics, remedial action attempted, what personnel have been contacted, and the time the equipment became operational (if applicable).

7.3. ADMS Equipment Failure ADMS are the most visible component of the AAM ITS system. The operational status of a sign is critical and can affect the motorists overall perception of the AAM’s operations. Various sign and message problems can be caused by the SunGuide System and/or by failures of the electrical and mechanical components of the sign.

The AAM considers an ADMS operational failure critical when a message does not respond to the request of the Operators. Some examples are when an ADMS doesn’t activate, the message does not blank or clear, there is an unscheduled loss of communication to the sign, there is an unscheduled system failure, and extensive pixel failure.

In the event an Operator experiences a critical ADMS failure, follow the proceeding steps:

• Evaluate the impact of the failure. By periodically checking the GUI map, scanning the icon colors, this will help alert the operator that there is an issue with a particular sign. Refer to the icon legend for color definitions. The following determinations should be addressed in order to evaluate the impact of the failure: o Has control of the sign been lost, and if so has the sign reverted to an innocuous default display

and/or o Has the software or hardware posted an incorrect message, with no apparent reason or have pixels

stuck on or off making the message erroneous. o Have multiple signs adjacent to one another become disabled simultaneously. In this case contact a

Manager immediately. o Determine and document which signs are affected, when it was noticed that the signs became

disabled, and the number of devices involved. • Notify the AAM Operations Manager and take corrective action as appropriate:

o If the color determination in the icon legend indicates an issue, go to the Detail Status section o If the detail status section displays the error, simply create a MIMS Trouble Ticket in SunGuide

with as many details and references to the issue, including detail status information, as possible o If the error information is NOT in the detail status, go to the MAS Queue, look for signs with a

failed status – they will be outlined in red. o The message indicates ‘failed’ in the MAS Queue, make certain that all signs show either failed

(outlined in red) or completed (outlined in green). o The message still does not initiate, create a MIMS Trouble Ticket in SunGuide with as much

detail about the issue as possible, including the unsuccessful attempt to resend the message through the MAS Queue.

o If the sign is blank but the message is indicated on the public website, notify the AAM Operations Manager.

• Notify the AAM Operations Manager of the occurrence when: o If after the above steps have been executed, a sign does not appear to be communicating with or

48

Active Arterial Management TMC Standard Operating Guidelines

responding to SunGuide, and a critical message cannot be displayed or an erroneous message cannot be removed.

o Multiple signs adjacent to one another became disabled simultaneously. o The system does not have an appropriate message in the message library suitable for a significant

traffic event such as an emergency roadway closure. • Upon direction from the AAM Management, you may be asked to create a MIMS Trouble Ticket in

SunGuide.

Documentation 7.3.1.When an ADMS Equipment Failure has been detected and/or reported, it is required to print the MIMS Ticket Report. The Shift Report shall contain documentation as well.

7.4. Internet Failures In the event the internet connection fails at any workstation, the error will likely be first recognized by the AAM Operators. Upon losing connection, Operators should notify the AAM IT Network Manager and the AAM Operations Manager immediately. The following should be taken into consideration when the TMC internet connection is lost:

• Event Email Alert Notifications should not be generated. • Critical notifications will need to be made via the landline or cell phone.

When an internet failure has been detected and/or reported, AAM Operators should report the conditions including duration within their Shift Report.

7.5. 511 FLATIS Failures Active Level 2 and Level 3 events must have a 511 FLATIS message published to the IVR and 511 web site, and unpublished when lane blockage and congestion has cleared. Messages sent to the 511 system should appear no later than five minutes from publishing to the IVR and 511 website.

There are six critical processes that can potentially fail when dealing with 511 FLATIS:

1. SunGuide Response Plan Generator publish 2. SunGuide Response Plan Generator un-publish 3. Add to the IVR System 4. Remove from the IVR 5. Post to the website 6. Remove from the website

In general, the steps for managing and reporting a 511 FLATIS problem are:

• Evaluate the impact of the failure o Determine whether it is the SunGuide response plan generator, the IVR system, the FL511.com web

site, or a combination of any of these that had failed. o For minor problems that do not impair operations, log the details and continue to work on the system.

49

Active Arterial Management TMC Standard Operating Guidelines

Major problems may need additional steps to rectify. • Minor Problems:

• Information entered is incorrect • Less than 15 minute delay in posting

• Major Problems: • IVR is not accessible (try multiple lines) • Information is not publishing at all • Properly entered information is appearing incorrectly • Delay in posting is greater than 15 minutes

• Take corrective action as appropriate o Re-publish or un-publish through the response plan generator o Wait 5 minutes and re-check the FL 511 website and/or IVR o If the system is still not functioning correctly, contact another FDOT District TMC

• Determine whether the problem is isolated to District 5 or widespread • If problem is widespread notify the RTMC Operations Manager.

Any and all FL 511 major failures and/or malfunctions should be included within each Shift Report.

7.6. Failure of External Agencies’ Equipment AAM Operators will be notified or detect problems with equipment or structures that are the responsibility of a different agency. When an external agency’s equipment failure has been detected, follow the proceeding steps:

• Notify and report the following details to FDOT Maintenance o Any associated debris within the roadway o Large potholes o Structural damage o HAZMAT o Flooding o Other problems which may affect public safety or traffic conditions

• Notify and report the following details to CSX and SunRail o Malfunctioning crossing guard rails o Malfunctioning signals adjacent to at grade crossings o Any event/debris on an at grade crossing o Other problems which may affect public safety or traffic conditions

• Notify and report the following details to the appropriate utility company o Events involving contact with a utility line/structure o Malfunctioning utility lines (downed power lines, flooding water mains, etc.) o Other problems which may affect public safety or traffic conditions

50

Active Arterial Management TMC Standard Operating Guidelines

When a failure of an external agency’s equipment has been detected and reported, it is required to document all details in affected events within SunGuide/IMD. In addition, the Shift Report should be updated to reflect the occurrence, including specific details, remedial action attempted, personnel contacted, and the time the equipment became operational (if applicable).

Traffic Signal Failure 7.6.1.AAM Operators should monitor the overall functionality and system health of the AAM Corridor’s traffic signal network. Traffic signal malfunctions include flash, loss of power, bulbs out, detector malfunctions, etc.* Traffic signal malfunctions should be relayed to the proper agency when they occur. When reporting traffic signal malfunctions, follow the proceeding steps:

• Collect appropriate information: o Intersection o Type of malfunction/failure o Impact to traffic conditions/public safety o Notification source o Date and time of detection

• Evaluate the impact of the failure/malfunction o Is all power lost to the intersection? o Is the signal in flash? o Does the signal appear to be collecting excessive congestion as a result?

During business hours, the corresponding county traffic division should be contacted immediately upon detection of a traffic signal malfunction or failure. For failures or malfunctions resulting in significant congestion, the AAM Operations Manager should be notified immediately.

*For more information regarding monitoring the traffic signal network, refer to Section 10.1.5 detailing monitoring of ATMS.now and Tactics.

51

Active Arterial Management TMC Standard Operating Guidelines

Reporting and Documentation 8.

8.1. Aides and Binders There are many useful aides and binders that help assist the AAM Operators with their day-to-day activities. The following is a list of aides with information on their purpose and use.

AAM Console Directory 8.1.1.Located at each AAM Operator console, there is a main directory which contains the following:

• AAM Operations Schedule • FDOT Telephone Directory

• County Telephone Directory – Orange, Seminole, and Volusia • City of Orlando Telephone Directory • Frequently used numbers • Exit number and state road number reference for all major roadways within Central Florida:

Orange, Seminole, and Volusia County. • Map of FDOT District 5 • Emergency Notification / Procedure Reference

Maps 8.1.2.Located at each AAM Operator Console, there are a series of maps which detail the AAM coverage areas. These maps are separated by jurisdiction.

8.2. Shift Reports & Operator Logs Shift Reports & Operator Logs are one of the essential reports the AAM uses. It is the one report that communicates all relevant details of the shift completed for the upcoming shift. It is the responsibility of the AAM Operators to continuously update and maintain the accuracy of their shift reports.

There are seven main sections to the shift report:

• Active Traffic Events (ATE) o This section summarizes active events at the time of the shift change. This area should reference

the Event ID and relevant details regarding the status of the event(s). • Shift Change Information

o On many occasions, the AAM Operator will be asked to relay miscellaneous information to the upcoming shift. This area of the report should be updated to reflect any relevant shift change information.

• Event History with ADMS Usage o The event history area simply lists events with ADMS usage. The Event ID, event type, location,

and lane blockage is specifically noted. • Event History with Active Signal Timing Adjustments

52

Active Arterial Management TMC Standard Operating Guidelines

o The event history area simply lists events which warranted the adjustment of one or more traffic signals. The Event ID, event type, location, and lane blockage is specifically noted.

• Helpdesk Tickets Opened/Closed o Management is responsible for providing additional information for anything greater than 30 days.

• MIMS Tickets Opened/Closed o Management is responsible for providing additional information for anything greater than 30 days.

• Other o The Other section is used for other areas that need to be documented, but do not necessarily fall into

one of the above categories.

At the start of each shift, the AAM Operator is required to review all areas of the shift report and discuss any discrepancies with the AAM Operator they are relieving, when applicable. Likewise, at the end of each shift, the AAM Operator is required to review all areas of the shift report and discuss any areas that may require clarification with the AAM Operator coming to relieve them, when applicable.

All shift reports should be emailed to the AAM Operations Manager before the AAM Operator leaves the TMC.

In addition to the Shift Report, throughout the day AAM Operators shall be required to accumulate and log data from multiple sources for the purposes of performance evaluation, archiving, and system upkeep. FDOT and its contractors will discuss the effectiveness and feasibility of the program’s reports to ensure they are obtaining the maximum value.

8.3. Performance & Maintenance Reports Monthly, quarterly, and annual performance reports should be generated by the AAM Operations Managers and submitted within seven business days after the end of the respective reporting period. These reports are intended to document the benefits of the AAM operations program. Additionally, maintenance reports on AAM and signal system infrastructure should be provided at these same intervals. Each report should summarize the information submitted within each AAM Operator’s Shift Report. At a minimum, each Weekly Report should also include the following:

ATMS.now and Tactics System Health 8.3.1.ATMS.now and Tactics are advanced traffic signal management software held and maintained by all City/County Traffic Engineering Departments. To aid the cities and counties in monitoring their own system, and to manage the effects of system malfunctions to traffic conditions, AAM Operators shall monitor and log information from the software daily. All information shall be logged within the weekly ATMS.now and Tactics System Health Reports.

Signal Controller Field Alarms • AAM Operators shall log all critical field alarms that occur during their shift. Each alarm should be

documented using the time, duration, controller name and/or ID number, and alarm type. • Critical Alarms are as follows:

o Signals in flash o Signals out of synchronization o Stuck Pedestrian Call Buttons o Malfunctioning detectors

53

Active Arterial Management TMC Standard Operating Guidelines

Signal Controller Preemption Calls • AAM Operators shall log all controller preemption calls that occur during their shift. Each call should be

documented using the time, duration, controller name and/or ID number, and preemption type.

Signal Controller Uptime • AAM Operators shall log the total operational controller count at 7:00 AM and 7:00 PM. Operator should

take the Total Controller count from the top right of the ATMS.now and Tactics home screens and subtract the devices that are not online yet, this provides the total online controllers. Operators should then sort the status column and total up the failed devices and subtracts that from the online controller count to provide the Operational Controller count.

Signal Timing Adjustments • AAM Operators should track and log any signal timing adjustments made by City and County Engineers.

The information can be retrieved from the “Transactions” report generated by ATMS.now and Tactics. Controller ID/name, time, and associated event ID should be logged.

Operator Call Log 8.3.2.All calls made and received by AAM Operators should be recorded within each week’s Operator Call Log. At a minimum the operator should log the date, time, agency, and call detail.

ATMS Infrastructure Preservation 8.3.3.Performance reports will include tracking of any possible damage to the ATMS Infrastructure from construction projects and incidents, as well as network failures. Information will include events reported during the week with their respective information (description of the potential system failure or infrastructure damage, name of construction crew’s company or agency, location, date and time of the event, troubleshooting response and status).

MIMS 8.3.4.The Maintenance and Inventory Management Systems (MIMS) is used to automate, centralize and streamline the maintenance of ITS devices and respective AAM subsystems. A Maintenance Log of Activity will be generated to track ITS Device Issues and Trouble Tickets.

8.4. Reports (Deliverables) The following reports shall be submitted within their respective time frames as required by the AAM Operations Contract Scope of Services, to be reviewed and approved by the Department:

• The VENDOR shall provide summary of all meetings’ minutes • The VENDOR’s Project Manager will prepare and submit monthly invoices and progress reports • AAM performance reports are submitted to the Department monthly, quarterly and annual • The Strategic Business Plan for the AAM is updated and submitted to the Department quarterly • Project Budget and tasks list monthly updates and status of work and cost summaries. • Monthly report with recommendations of the current time tracking system’s data analysis to assist the

Department in monitoring the operations staff activities. • The VENDOR shall prepare monthly reports summarizing the business plan results

54

Active Arterial Management TMC Standard Operating Guidelines

• A more comprehensive report shall be prepared yearly. • The VENDOR will provide for all employees supplied under this CONTRACT / AGREEMENT weekly time

sheet depicting hours worked including overtime attached to each monthly invoice. • The VENDOR shall provide a management and operational staffing plan for TMC operations which

includes at a minimum, an outline of the number of personnel working during all shifts, type of staff (classification, title, etc.), and a Staff Structure (organization chart).

8.5. Monthly Dashboard Dashboards are an accepted vernacular for reports that include all relevant information for a particular initiative, summarized into an easily understandable and brief format. The AAM Dashboard (AAMD) is under development by EPIC Engineering and Consulting Group, LLC; a sample of this report and the methodology used to develop it can be found in Appendix E. The AAMD application will provide the accessibility and analysis capabilities for the datasets identified by the technical and management stakeholders to capture, track, analyze and visualize the key performance metrics set up for the successful implementation of the AAM project. The proposed AAMD Application will be a web application that will reside in the FDOT IT infrastructure. It will be designed in a modular and scalable manner in order to support FDOT’s project information management needs for many years to come. This application will be designed in adherence to FDOT IT standards and security protocols and will support integration with key project information sources within FDOT. It will also be architected using Service Oriented Architecture (SOA) to support access through FDOT-approved mobile devices such as tablets and smart phones as applicable accordingly. Reports are an important component of the planned AAM solution. The design of reports will facilitate the visualization and reporting of the data. These reports will have the functionality to apply filters and perform analysis such as trends and statistical averages. The specific design of the reports will be determined through user requirements and documented in the functional specifications document. These reports are to be prepared and submitted to the FDOT TSM&O Program Manager and D5 AAM Project Managers by the seventh business day of each month for the previous month.

8.6. Progress Meeting Requirements The VENDOR’s Project Manager will meet on a monthly basis with the DEPARTMENT’s Project Manager and Maintaining Agency representative to review and discuss tasks completed during the previous period, task assignments for the current period and the one-month “look ahead” schedule. Also, the VENDOR’s Project Manager will participate in monthly progress meetings with DEPARTMENT staff and provide the Department with meeting minutes and a task list.

The VENDOR’s Project Manager attends meetings as directed by the DEPARTMENT to include District 5, MetroPlan Orlando and others.

55

Active Arterial Management TMC Standard Operating Guidelines

Regional Coordination 9.MetroPlan Orlando was formed in 1997 and is the metropolitan planning organization for Orange, Osceola, and Seminole Counties. MetroPlan Orlando provides a forum for effective dialogue and decision-making to accomplish the ultimate goal of providing an efficient and effective transportation system in Central Florida. The organization is ultimately responsible for implementing transportation plans. Also known as the Orlando Urbanized Area Metropolitan Planning Organization, MetroPlan Orlando is one of 26 MPO’s in the State of Florida and was one of the first multi-county MPO’s in the state. With 19 members, the MetroPlan Orlando Board includes representation from three counties, the largest cities in the region, officials from transportation operating agencies and representatives from several advisory committees. This composition provides an inclusive and deliberative planning process to determine how federal and state transportation dollars are spent in the three-county area.

MetroPlan Orlando along with the AAM plays a vital role in the Central Florida transportation system management. Regional cooperation and partnerships are essential to the transportation planning process.

9.1. Partner Agency DMS Notification During AAM Operations, there will be times when it will be appropriate and necessary to contact a partner agency to request activation of their freeway DMS to assist with public awareness of an arterial event. The appropriate agency (based on location) should only be contacted for DMS Messaging based on the following criteria:

• Any full closures within three miles of a freeway access ramp. • Any Level 3 Event within one mile of a freeway access ramp. If an event occurs within one mile of multiple

freeways, contact all relevant agencies. • Any Level 2 Event within ½ mile of a freeway access ramp. • Any event on a freeway access ramp.

All event information should be accurate and verified prior to contacting any partnering agency TMC. Each TMC has their own priorities and traffic events and may not choose to post messages for arterial events. Regardless of their decision to post message, unless directed by that TMC, updates should be provided at least every 30 minutes to the appropriate agency and at the event conclusion.

ADMS Messaging for Freeway Events 9.1.1.Partnering Agency TMCs have their own ADMS posted before access ramps to warn travelers of significant traffic events prior to accessing their freeway network(s); however, for severe freeway incidents, it would be beneficial for travelers to receive even more advanced warning through the use of the AAM’s ADMS.

If the following criteria are met, AAM Operators should create an event (Interagency Coordination event type) and only post messages for all ADMS approaching access ramps within two miles of the associated freeway (SunGuide email alerts and 511 incident information are not necessary for dissemination by AAM staff):

• Full Freeway Closure within 20 miles of the AAM Coverage Areas • Freeway Access ramp closures on AAM Coverage Area arterials • Any Level 3 event within 5 miles of the AAM Coverage Areas

56

Active Arterial Management TMC Standard Operating Guidelines

• Any Level 2 event within 1 mile of the AAM Coverage Areas

Active arterial traffic events take precedent over all levels of freeway events. Freeway events should only be posted to ADMS in the event there are no relevant active arterial events for the selected ADMS. AAM Operators shall seek approval of the AAM Operations Manager prior to posting.

Documentation 9.1.2.In addition to logging the event in SunGuide, any instances of partnering agency TMC coordination should be documented within the AAM Operator Shift Report.

9.2. Interagency Coordination

Clear Speak/Plain Language 9.2.1.Employment at the RTMC AAM exposes one to a system of codes and signals used by law enforcement and dispatchers. It is acceptable to speak in codes and signals within the bounds of the RTMC, some codes and signals are almost necessary to know. However, when interacting with other agencies outside of the RTMC, it is absolutely necessary to use what is known as clear speak or plain language, that is, speaking without codes or signals, in plain language that anyone could understand.

The reason for using clear speak or plain language when communicating with other agencies is because there is no uniform standard for codes and signals, and one code or signal used by the RTMC may mean something completely different to a local police or fire department. Clear Speak or Plain Language is a requirement of the National Incident Management System and the Incident Command System when agencies communicate with each other.

For purposes of clarification, the code and signal system used by the RTMC is the same code and signal system used by FHP.

57

Active Arterial Management TMC Standard Operating Guidelines

Detection & Monitoring Plan 10.The following procedures ensure that the AAM Operator is aware of traffic events, conditions, and device statuses. AAM Operators are expected to remain at their workstations throughout the duration of their shift unless on break. During this time Operators shall spend time monitoring the following computer applications and systems:

10.1. Applications and Systems

CCTVs 10.1.1.CCTV cameras are to be used to determine the details of traffic events along AAM corridors. In addition, they are a useful tool for detecting and verifying incidents and damage to the roadway. When monitoring CCTV camera feeds, care must be taken to comply with the Protection of Privacy Act.

The following are guidelines for CCTV traffic monitoring:

• For routine monitoring, use the predefined presets which have been identified as the ideal tour views. • At least twice per hour during the peak periods and once per hour during off peak, the AAM

Operator(s) is required to scan the complete coverage area for events/incidents. • Whenever cameras are not being used for scanning, they should be returned to a relevant preset

position. • Look for the following visual clues indicating a traffic event:

o Very light flow or no flow, at locations and times when heavy traffic is expected. o All of most vehicles changing lanes at a particular location. o Vehicles slowing or stopping at an unorthodox location.

• Increase attention should be given to areas where queues typically build up, including bottlenecks, busy on ramps, and construction work zones.

ITS Field Device Security Monitoring 10.1.2.There are dozens of ITS field cabinets with thousands of dollars’ worth of communications equipment along the AAM corridors monitored by the TMC. Additionally, copper wire thefts have been prevalent along FDOT right-of-way. Maintaining physical and electronic security is part of the ITS Devices’ responsibilities to keep equipment operational at all times. If an intrusion or suspicious situation is detected, TMC Operations staff will assist in the process to notify the appropriate staff and/or law enforcement to investigate.

If at any time suspicious activity is detect by CCTV, follow the proceeding steps:

1. Contact local police to respond 2. Notify the AAM Maintenance Contractor and the AAM Operations Manager 3. Continue monitoring until given the all clear by Maintenance, law enforcement, or a manager. 4. Document on shift report and weekly reports.

58

Active Arterial Management TMC Standard Operating Guidelines

Motorist Calls 10.1.3.

An event reported by a motorist requires the AAM Operator to collect and log specific information into SunGuide. This information is critical to incident management, specifically for information dissemination.

• AAM Operators should write down all information received from the motorists. • The information that is collected should be as follows:

o Type of incident o Location o Direction o Lane closure information o Additional information (fire, hazmat, etc.)

• AAM Operators should never directly advise any caller of actions they should take regarding any incident. • Enter the “Unconfirmed” event information into SunGuide. (The status of any event notified via phone

shall be logged as “unconfirmed” until the event is viewed via CCTV, or a responder verifies the event.)

• Attempt to locate the event using CCTV and collect further information and details of the incident to document in SunGuide.

• Follow standard incident management procedures. • Develop and provide outreach material describing how traffic signals function and the benefits of active

arterial operations. • Monitor number of calls, time to respond to calls and outcome of complaints received.

Seminole County Citizen calls are tracked in the County’s system, Mainstar. Robert Fitzgerald (407-665-5698 or cell 321-377-1971)) screens calls and determines if they are maintenance or engineering related, and will then deliver them to the appropriate AAM staff. The typical contact time period is 24 hours for elected officials and 48 hours for citizen calls, although it may longer to address problem. Items to track are:

o Citizen contacted o Contact date/time, o Resolution description o Closeout date/time

City of Orlando Citizen calls are received at the City’s TMC directly (407) 246-2020, or transferred to the TMC if received by another City Department/Division. They also have a mailbox (orlando-traffic-concerns@cityoforlando.net) that is listed on the City’s website (www.cityoforlando.net/transportationengineering). The City is looking into developing a “311” like system in the future to handle calls and complaints. Orange County Citizen calls are received via email and the County’s 311 system. Any Orange County complaints call (407) 836-3111 or visit the Customer Service 311 webpage. Citizens talk to live operators when they call, Mon-Fri from 7 am – 9 pm

59

Active Arterial Management TMC Standard Operating Guidelines

and from 9:00 am – 5:00 pm on Sat and Sun. AAM Operators will receive complaint calls filtered by Orange County for AAM monitored corridors from the County’s system. One e-mail has been setup for AAM to receive complaints from Orange County. A County technician will review the complaint in-house and then go to field to diagnose the issue. Each trouble ticket created is tracked and information that is provided to the citizen to close out. AAM Operators should provide the resolution information about the issue back to Orange County. City of Maitland A form is filled out to document information about the traffic signal or school beacon malfunction or complaint (see Appendix F). AAM staff can contact Control Specialists directly at (407) 628-1965 to report emergency repairs after hours provided an email is sent to the City/Transportation Engineer (Cristina Torres-Reyes, creyes@itsmymaitland.com) notifying the nature of the problem. City staff conducts a field review and, if appropriate, forwards the information to the City’s signal maintenance contractor (Control Specialists) to address the issue.

City of Winter Park Citizen calls are typically received from the City’s police, City Hall, or City Manager and are then passed to the City traffic engineer or field technician to respond. GovQA.com is used by the City to receive and track citizen complaints online (https://cityofwinterpark.org/residents/ask-winter-park). Citizen’s login and post questions, concerns or complaints through the website. GovQA is used by the agency for tracking of responses as well. A filed complaint stays open until it is resolved, then they are closed out in GovQA. If complaints don’t come in via GovQA, doesn’t get entered into GovQA by city staff. The City will assess the severity of the issue and forward complaints received on AAM corridors (US 17/92) to AAM staff via email. A group email account will be used by the AAM to coordinate all complaints with Butch Margraf and other City staff. The City had one full time and one part time signal technician. City technicians are on-call through weekend hours. Traffic Control Devices, Inc. (TCD) at (407) 628-1965 handles emergency calls for the City as a backup for their technicians when they are not available. If AAM operators or engineers discover an issue, contact the City staff first via the email group before contacting TCD.

Travel Time Subsystems (TTS) 10.1.4.All travel time subsystems are used to collect real-time traffic information, including speed, travel time, and occupancy. AAM Operators should use the SunGuide Operator Map and programmed alarms to promote incident detection. AAM Operators should look for the following signs of incidents:

• Sudden decrease in speed and/or occupancy • Rise in occupancy accompanied by a decline in speed

All conditions and/or alarms should be verified via CCTV before logging any information into SunGuide.

TrafficCast Speed Map Due to the density of TTS devices deployed along the AAM corridors, Operators will have the TrafficCast Bluetooth speed map (http://XX.XXX.XX.X) open for better access to the speed pairs and reporting functionalities of this technology.

60

Active Arterial Management TMC Standard Operating Guidelines

INRIX A third party traffic information provider, INRIX provides a visual representation of traffic conditions similar to the SunGuide Operator Map. The software has various layers and methods to reading data, and should be utilized to aide in reading traffic conditions.

TTS Alerts SunGuide generates alarms based on established thresholds programmed for TTS devices to alert Operators of potential incidents. Located on the right hand side of the Event List in SunGuide, there is a section which is used for system alerts. When a threshold has been met, the system alerts section will display a blinking alert and emitting an audio sound. The system will list in chronological order from top to bottom, and how many minutes have lapsed since the initial detection. When an alert is selected within the Alert Display, a pop up window will appear. This pop up window will contain the detected information and options to do the following:

• Create New Event • Create Secondary Event • Set Responder Arrival • Dismiss as Already Detected • Dismiss as False Alarm

Once an event has been handled with one of the above options, the event will be removed from the SunGuide system alerts section.

Fiber Cuts Any time a series of multiple devices loses connectivity is generally indicative of a large power outage or a physical cut to the communication infrastructure. In the event of a sudden loss of connectivity to multiple devices in series occurs AAM Operators should check for any power outages in the area using the FPL website (http://www.fplmaps.com/) or Duke Energy (http://outagemap.duke-energy.com/fl/default.html). If no outages are displayed, notify FDOT Maintenance immediately if connectivity is not reestablished after one hour.

ATMS.now and Tactics Advanced Signal Management Software 10.1.5.To aid the local agency’s in monitoring the health of their signal system and to mitigate the effects of signal system malfunctions on traffic conditions, AAM Operators should monitor the signal system to the extent of their access limitations. Operators should look for the following alarms along the AAM corridors:

• Signal Flash • Loss of signal communication • Loss of signal coordination • Stuck pedestrian call buttons • Detector malfunctions

61

Active Arterial Management TMC Standard Operating Guidelines

• Preemption calls o Emergency o Rail

Seminole County Seminole County has staff performing health checks of their overall ATMS.now system on a regular basis. However, AAM Operators should be monitoring Bluetooth devices and looking for arterial congestion and incidents. If an issue is identified, AAM Operators should track the issue and note when the issue is resolved. Contact the Seminole County TMC at (407) 665-5581 or Edgar Principe at (407) 665-5680. City of Orlando The City of Orlando has staff performing system health checks of their overall ATMS.now systems on a weekly basis (currently Sundays). If an issue is identified with The City of Orlando’s ATMS.now system, AAM Operators should contact the City of Orlando TMC at (407) 246-2020 to resolve issues. Trafficware may need to be contacted at 1-800-952-7285 if the issue cannot be resolved by the City. Orange County Orange County has staff performing monitoring alerts from the TMC, consistent with the FDOT maintenance agreement. AAM Operators should be monitoring Orange County’s Tactics system on a regular basis. If an issue is identified, AAM Operators should track the issue and note when the issue is resolved. Contact the Orange County TMC at (407) 837-7777. City of Maitland As part of their planned maintenance, the City of Maitland’s signal contractor performs a monthly inspection of all traffic signal equipment and components and reports any issues to the City, including a cost estimate to correct the issues. Citizens’ calls and complaints are also used to monitor signal equipment and respond to malfunctions. The City does not have a central software system to control the traffic signals. If an issue is identified, AAM Operators should e-mail the City Transportation Engineer (Cristina Torres-Reyes, creyes@itsmymaitland.com), track the issue, and note when the issue is resolved. City of Winter Park The City of Winter Park does not currently use ATMS software. The City’s two technicians perform regular maintenance of their signal equipment. If an issue is identified, AAM Operators should e-mail the City’s group email account to coordinate with Butch Margraf and other City staff. If the City staff are not available, contact Traffic Control Devices, Inc. (TCD) (407-869-5300) for emergency situations.

10.2. Active Signal Timing Plan Adjustments The ATMS.now and Tactics signal software allows engineers to design and implement custom timing patterns in real-time. These plans can be used to accommodate increased traffic demands for a vast variety of events. While local responders are at the event scene to clear the event in an efficient and safe manner, engineers have the ability to remotely adjust adjacent traffic signals to balance out the decreased capacity induced by lane blockages.

62

Active Arterial Management TMC Standard Operating Guidelines

AAM Operators should notify the AAM Operations Manager of all Level 2 & Level 3 severity events for consideration for timing adjustments. It is up to the judgment of the AAM Operations Manager/Timing Engineer whether or not a timing adjustment is necessary and/or beneficial to each situation. Only the AAM Operations Manager/Timing Engineer shall have the ability (other than City and County employees) to implement approved timing adjustments.

Seminole County Signal timing changes should be made using the same process as being used with Albeck Gerken, Inc. (AGI) currently. An engineering analysis and support needs to be provided by the AAM team for the County to review prior to implementing changes. The timing changes should show improvement in travel times and/or an increase in throughput. Synchro v8 files and TruTraffic v10 files should be sent to the County for review. TruTraffic should be used to adjust offsets during timing implementation. The County would like the new timing plans to go into the new FDOT D5 ITS Decision Support System (DSS) & ATMS Software Development. Seminole County staff will implement timing changes between 7:00 AM and 5:00 PM, Monday through Friday. Additional coordination is required outside of those times. Changes to timings should all be logged so that the County knows what changes were made. The only exception to these requirements would be during catastrophic events that would require unplanned changes for the benefit of the traveling public. AAM staff should call or email (using established email group) first on weekdays (7:00 am – 5:00 pm). For corridors with SychroGreen adaptive signal systems AAM staff should coordinate with the Seminole County TMC staff at (407) 665-5581 or contact Edgar Principe at (407) 665-5680 to implement desired timing setting changes. The AAM room does not have the capability to observe SynchroGreen system timings or make adjustments. City of Orlando Signal timing changes should be made using a process similar to FDOT’s annual retiming program. The AAM should submit a draft of proposed timing plans, allow for a City review period, incorporate their comments, field implement the timings (as a test case initially), and issue final timings in an ATMS.now database format. The City would prefer to have City TMC operators initially download pre-developed AAM timing patterns and then switch back to standard patterns following an event. City policy requires a City’s signal technician to be present during any cabinet access. Future alternatives could include replacing existing pad locks with combination locks for those cabinets with CCTV cameras or cyber locks. Orange County Signal timing changes should be made using a process similar to FDOT’s annual retiming program. The AAM should submit a draft of proposed timing plans, allow for a County review period, incorporate their comments, field implement the timings (as a test case initially), and issue final timings in a Tactics database format. Traffic responsive plans are needed because many of the AAM routes are parallel to I-4. For planned events, the County wants a timing plans field testing process performed during off peak time periods, possibly supplemented using microscopic traffic simulation (SimTraffic, VISSIM, CORSIM). County policy requires a City’s signal technician to be present during any cabinet access. Pad locks are currently used to minimize unexpected cabinet access. AAM staff should coordinate with Orange County for technician assistance. There should be no timing implementation without assistance from Orange County with the exception of emergencies between 6:30 and 10:00 PM during catastrophic events that would require unplanned changes for the benefit of the traveling public. Currently, the AAM room has

63

Active Arterial Management TMC Standard Operating Guidelines

read-only access to Tactics databases. It is possible for the Tactics software to allow write access at specific locations with approval from the County. City of Maitland The City prefers to review timing change reports and Synchro files proposed by AAM staff prior to implementation. Relevant files can be emailed to the City/Transportation Engineer (Cristina Torres-Reyes at creyes@itsmymaitland.com) or hard copies of the report and a CD containing relevant files can be sent mail to: Maitland Municipal Complex, 1776 Independence Lane, Maitland, FL. 32751. The City can review Synchro version 9 or older files and would prefer to review hard copy Tru-Traffic reports/diagrams, if supplied. There are currently no security standards for entering City maintained signal cabinets. A standard No. 2 key used is required cabinet access. AAM staff should coordinate with the I-4 Ultimate Concessionaire for traffic signals within Maitland that fall within the I-4 Ultimate project limits (primarily along Maitland Boulevard between Maitland Summit Boulevard and Maitland Concourse Parkway). City of Winter Park The City prefers to review draft timing reports proposed by AAM staff prior to implementation. Relevant files can be emailed to the City Traffic Manager Butch Margraf at bmargraf@cityofwinterpark.org or sent out via mail to: City of Winter Park, 401 South Park Ave., Winter Park, FL. 32789. There are currently no security standards for entering City maintained signal cabinets. A standard No. 2 key used is required cabinet access.

InSync Adaptive Signal Systems 10.2.1.InSync is systems were deployed by FDOT along two AAM corridors: 1) US 17/92 with 5 traffic signals between Firehouse Road and Beresford Avenue in DeLand, FL (to be managed by the HNTB team), and 2) SR 46 with 10 traffic signals between International Parkway and Airport Boulevard in Sanford, FL (to be managed by the Atkins team). Note: Another corridor recently had InSync deployed, US 92 (International Speedway Boulevard between x and x) in Daytona Beach with 22 signals, and will also be managed by one of the AAM teams in the near future.

AAM operations managers, timing engineers and operators have access to view the InSync system detection cameras, timing parameters using the web user interface. Similar to other signal timing changes, It is up to the judgment of the AAM Operations Manager/Timing Engineer whether or not a timing adjustment is necessary and/or beneficial to each situation with InSync systems. In addition, the same protocol used for ATMS system timing changes should be followed with the respective local agency. For US 17/92 in DeLand, Volusia County, FL, FDOT maintains the InSync system and all associated detection equipment. AAM staff should coordinate with Volusia County on any other signal equipment related issues (Jon Cheney 386-295-6016 or Mark Tobin 386-295-6311).

Manny Rodriguez (FDOT contact 386-943-5307 or email Manny.Rodriguez@dot.state.fl.us) has the only administrative access to create any new users. No AAM staff may attempt to modify or create a new user profile.

Users should login to each intersection by entering the associated IP address for each intersection using Internet Explorer. These IP address can be found at the workstations in the AAM room.

64

Active Arterial Management TMC Standard Operating Guidelines

Event Management 11.Due to the vast variety and severity of traffic incidents that may occur on the AAM corridors, it is impossible to provide strict procedures for each individual event. The following is a basic procedure to be used when managing a standard traffic incident. Please refer to these steps when managing traffic incidents.

11.1. Incident Management Protocol

Orlando AAM Upon incident detection:

• Collect information from the notifying source or CCTV • Input the information into SunGuide • Upon verification of the incident, make the event Active within SunGuide if not already so • Enter the camera number and preset into the system • Coordinate with law enforcement and emergency responders to reduce incident response time • Verify all information for accuracy • Generate Response Plan • Check ADMS, Email, and 511 FLATIS • Activate Response Plan • If necessary, notify Engineering staff for timing adjustment consideration • Coordinate with signal operation agencies for signal retiming changes • Disseminate traveler information for better decision making. Make delay reduction decisions that target mass

transit mobility. • Update and confirm information and Response Plan to be consistent with real-time conditions. Once lane

blockage has been confirmed clear: o Update information in SunGuide o Generate Response Plan o Check ADMS, Email, and 511 FLATIS o Activate Response Plan o Monitor secondary incidents/congestion

*For more information regarding SunGuide input and Response Plans, please refer to Appendix A.

11.2. Roadwork Event Management On many occasions, it will be necessary for AAM staff to manage active and anticipated construction work zones. This can be done by posting to ADMS and traffic signal timing plan modifications. There are generally two types of roadwork:

• Emergency Roadwork is that which is resultant of an incident and requires physical repairs to roadway infrastructure such as median, signs, traffic signals, etc.

• Scheduled Roadwork (as far as SunGuide can interpret) is all other detected roadwork along the AAM Project Limits. It includes everything from temporary lane closures for streetlight bulb replacement to indefinite closures for roadway construction projects.

65

Active Arterial Management TMC Standard Operating Guidelines

Procedures for proper Roadwork Incident Management vary depending on how the event was detected or who provided notification; for general purposes however, the following guidelines should be followed:

Policy Upon Detection:

• Create SunGuide/IMD (Active) Event with all relevant information • ADMS

o Post messages with the proper location and lane blockage information o If a sign is located within the work zone limits, do not use it; only use signs that are located before the

roadwork. • When there is an ATE beyond the roadwork, post all applicable sign(s) before the roadwork

for the roadwork event, and the sign within the roadwork limits for the ATE. • If the ATE closes all lanes, priority should be given to the ATE over the roadwork. • If the ATE is located before the roadwork, sign for the ATE, rather than the roadwork,

depending on the distance and significance of the ATE. Once the ATE clears, be sure to sign again for the roadwork incident.

• If the ATE occurs within the roadwork incident, sign for the ATE, but include lane blockages created by the roadwork.

• 511 FLATIS o Select the correct CONSTRUCTION group as recipient

• Confirm and send via the published Response Plan Notify appropriate agencies o ITS Program or FTE if the work zone exists on or near on/off ramps.

• Monitor roadwork limits and update all incident information, ADMS, and 511 FLATIS to reflect real-time conditions.

• Once the roadwork is cleared: o Blank all ADMS o Update incident information within SunGuide o Send message to the CONSTRUCTION group o Removed 511 FLATIS information o Update notified agencies if applicable o Close event Monitoring

Due to the potential length of some roadwork events and the likelihood of varying lane blockage conditions without sufficient notification, the following procedures must be followed to ensure proper management of any and all roadwork incidents:

• At least once every 30 minutes, AAM Operators should visually inspect the full extent of the roadwork incident limits to confirm real-time conditions are up to date as well as to check for any secondary crashes/congestion around the limits.

• If changes have occurred since the last check, update the Incident Information, ADMS, and 511 FLATIS

66

Active Arterial Management TMC Standard Operating Guidelines

accordingly. • Continue monitoring the incident until it is completely cleared.

If the roadwork incident is an expected long term (>1 day in duration) project with long term lane closures, the incident should be left open within SunGuide. If the roadwork is long term but clears all obstructions (equipment, barricades, debris, etc.) by the end of the day from all roadways, shoulders, and sidewalks, the incident may be closed and reopened when blockages resume.

511 FLATIS Reporting • AAM Operators will need to update any long term construction on a daily basis, so that the statewide 511

website and the IVR are updated within every 24 hour period. • AAM Operators may simply use the republish option – right click on map, EM, republish event from drop

menu. AAM Operators should be sure to send an alert when “taking over” an event from another operator or make an update to the incident chronology.

o If no updates are made, then the update alert will be sent based on the last time stamp entered.

Documentation It is required to document all roadwork incident details within SunGuide/IMD; in addition, the Shift Report should include any mitigation efforts (ADMS messaging, timing adjustments, etc.) details for all roadwork incidents.

11.3. Hurricane/Emergency Preparedness The hurricane season for Florida runs from June through November. During any storm, heavy winds, rain, and storm surges may leave debris in the road. Precautions must be taken before, during, and after the storm to assure the safety of the traveling public and to provide the highest level of service possible.

Since an emergency such as a hurricane shall have a regional wide effect on traffic conditions, much of the public notification responsibilities associated with preparation shall be handled by the RTMC ITS Program. AAM staff should assist other TMC staff however possible. The following are preparation and after storm procedures to be followed:

Preseason Before the beginning of the Hurricane Season, the AAM Operations Manager should complete the following:

• Ensure workstations have copies of all emergency telephone numbers. • Email all AAM Operators and see who would be available for pre, imminent, and post storm coverage. • Check and restock TMC food/water supplies (should be stocked for up to 3 days)

Preparation Upon notification of a hurricane watch and/or warning for the area, the following steps should be taken:

• Pay attention to weather reports and patterns • Have a current copy of all emergency telephone numbers readily available • Make certain there are ample hurricane supplies at the TMC

67

Active Arterial Management TMC Standard Operating Guidelines

• Notifications will be made to all staff in advance of anticipated weather to prepare for changes in scheduling. o This could mean extended shifts or the need to stay longer periods of time due to the inability to leave

the AAM once the severe weather arrives. o If an employee has been instructed to prepare for this scenario they should consider bringing with

them the following items: • Personal hygiene effects: It may be necessary to stay overnight and the building has access to

locker room facilities where staff can shower if they choose to do so. • Change of clothing • Bottled water: Enough to last 2 days • Food: Enough to last 2 days • Sleeping necessities: Pillow and/or blanket

Storm Impact Imminent As evacuations may be required for the region, FDOT may request that AAM staff remain at the TMC beyond working hours up to 24/7. Emergency Operations during anticipated severe weather will include the following:

• Once staff is safely inside the AAM they may be instructed to stay until the severe weather has passed. The roadways can become a very dangerous place during severe weather and so the release of staff into such an environment would be against the best interests of our staff. Not only would it be unsafe for current staff to exit the building, it would be unsafe for other staff to travel to the AAM. This is why the emergency supplies are so important. If each employee comes prepared, then there will not be issues if it is required to stay past your regularly scheduled shift.

• Depending on the severity of the forecasted weather, the AAM may go to adjusted work hour shifts. This will help to reduce the amount of staff traveling during the poor weather.

• Continuous communication with FDOT on ITS network, status of roadways and severity of weather throughout the District is to be expected.

• Coordination/Communication with the RTMC staff during the severe weather • Monitoring of local news coverage of the storm will be required.

Regular operations will continue for as long as it is safe (until sustained winds exceed 35 mph). Once this threshold has been met, operations will shift from traffic facilitation to Infrastructure damage identification. Operators, for as long as the power remains, shall scan the AAM Corridors for any debris in the road and damage to any FDOT Infrastructure. After the storm, a report shall be submitted to the FDOT Project Manager.

After the Storm Upon notification/verification of the redeployment, AAM staff on site shall:

• Check all devices for connectivity and errors; submit trouble tickets accordingly • Check the full project limits for debris on the roadway and notify the appropriate agencies. • Issues detected must be disseminated in a timely fashion – potentials after the storm could include flooding

and tornado activity.

68

Active Arterial Management TMC Standard Operating Guidelines

Other Emergency Situations FDOT may request similar support from the AAM Staff for other emergency situations such as wildfires and other unprecedented occurrences that are not covered within this document. In such an event, AAM Staff should act to the best of their ability to serve the public with safety as the number one concern.

11.4. Severe Weather Weather events such as Tropical Storms, Hurricanes, Severe Thunderstorms, and Tornados can have heavy impacts on traffic conditions specifically in regards to travel times and safety. Advanced warning regarding severe weather conditions allow motorists to take action, such as detouring or delaying their trip.

Only weather warnings are to be posted, not weather watches. Weather warnings are imminent or occurring events and weather watches are favorable conditions for an expected event but not occurring. With the present system configuration, messages will be posted by the operator based on information obtained from weather alerts provided by the National Weather Service’s Mobile Decision Support Services (NWS-MDSS) https://inws.ncep.noaa.gov/.

When an alert is received, take the following actions:

• Open the email alert in Microsoft Outlook and click the link for “more information.” This will open the web page with more details on the alert. See the example of the alert in Figure 3.

Figure 3. Example iNWS Alert

• Examine the interactive map and detailed description of the alert and verify that the event is in the area of the AAM Project Corridors. See the example of the map and description in Figure 4.

• Upon verification of event in the area, create a weather event in SunGuide/IMD as “Weather” and select the appropriate notifier.

• Select signs in both directions for affected areas confirmed by CCTV feeds. If possible, choose two signs in each direction for within that area and two signs in each direction for approaching the area. Due to the location or

69

Active Arterial Management TMC Standard Operating Guidelines

size of the warning area, it may not always be possible to have four signs. Operators will need to select the appropriate number of signs at their own discretion.

• Use response plans to add ADMS and select appropriate message from the library for signs within and approaching the warning area.

• Remove email and FLATIS publication from the Response Plan

Figure 4. Example iNWS Map and Description

Notification of outside agencies for severe weather conditions such as Severe Thunderstorms and Tornados isn’t necessary.

Severe weather conditions must be monitored like other events as conditions can change very quickly:

• Continually monitor conditions using CCTV feeds and via weather information websites such as: o https://weather.com/weather/today/l/USFL0372:1:US

• For the mentioned weather information websites, locate the interactive map and zoom into the location approximately in the center of the warning area.

Severe Thunderstorm Warning valid from Aug 20

000

SEVERE THUNDERSTORM WARNING

70

Active Arterial Management TMC Standard Operating Guidelines

• As conditions change, messages should be updated. • When the warning is no longer in effect, the messages should be removed from all ADMS. • Any incidents that occur during severe weather conditions should not be treated as secondary incidents to the

weather event.

Tropical Storms and Hurricanes For weather events such as Tropical Storms and Hurricanes, the aforementioned steps should be followed but some additional ones should be taken as well.

• HAR messages should be selected in both directions approaching and within the warning area using the appropriate message from the template library. Note that the message will be the same on all the transmitters and should match the format of the NWS. For these warnings, the time should be removed from the message.

• Notification of outside agencies for these weather events is necessary. Appropriate partners are to be contacted or advised of the action taken.

*To receive these weather alerts, all FDOT District 5 AAM staff should subscribe to the following services at The National Weather Service’s Mobile Decision Support Services (NWS-MDSS) https://inws.ncep.noaa.gov/.

11.5. Data Entry FDOT District 5 AAM currently uses SunGuide (the statewide ITS software) as the primary means of storing and disseminating information about incidents on the arterial networks. Through various input screens, information about incidents is entered by AAM Operators. The following procedures should be used when inputting new and managing existing event entries.

SunGuide Data Entry Procedures – Orlando AAM There are three guidelines with entering data into SunGuide: Input, Update, and Monitor:

• Input all traffic related events accurately and concisely • Update events as conditions change

o Notification, arrival, and departure of responders o Lane blockage conditions o Closure and termination of event

• Monitor active events regularly and frequently To enter event information into SunGuide, the following information needs to be obtained:

• Event Type • Notifying Agency and Contact • Event Location • Lane Blockages

71

Active Arterial Management TMC Standard Operating Guidelines

• Event Conditions • Specific Attributes

Once an event has been detected and the preceding information has been obtained, being entering the data into SunGuide. The system utilizes primarily drop-down lists, sub forms, and check boxes which enable easy event data entry. Enter a new event using the following process:

• Located on the main screen, click the “Add Event.” A new window will open where the following shall be input:

o Event Type o Notifying Agency o Notifying Contact o Status

• After the preceding information is entered, click the “Create this Event” button. The Operator will be directed to the Event Detail window, which will contain the specifics of the event. Enter the details in the following order:

o Event Location o Lane Blockage o Attributes (HAZMAT, Fire, Rollover) o Vehicle Involved (color, make, model, tag state and ID) o Primary/Secondary Events (if applicable) o Injuries (if applicable) o Weather Conditions o Comments (Additional Event Details) – allow an Operator to record information that cannot be

recorded elsewhere on the Event Details screen • OPERATOR: Document all Operator comments related to the event with this comment field • MANAGER: Operator will document any Manager related comments or instructions within

this field • INFRASTRUCTURE DAMAGE: Any time there is roadway/infrastructure damage recorded in

an event along with details of who was contacted, etc. • FL 511 ERROR: Any time an error/failure is detected on the IVR or website. For IVR issues

please record the number you called from an the path you followed along with details of the error

• AUDIT REQUESTED: Used only when system does not properly reflect actual data that can affect Performance Measure integrity due to system problems or other uncontrollable circumstances.

o After the preceding information is entered, click the “save” button. The Event Details window will refresh with all information logged.

o As there are no Road Rangers or SIRV Vehicles reserved for the arterials, the “Vehicles Dispatch” sub menu will not be utilized at this time.

o Update the Responder Table by clicking in the applicable agency row and status column.

72

Active Arterial Management TMC Standard Operating Guidelines

Make sure the times are accurate o If applicable, “Save, Get Response” to activate the Response Plan Generator for ADMS and Email

Notification Alerts. o Generate the appropriate devices by setting a radius, then select “Get New Suggestion.” Click “Set

as Response” once you determine the appropriate devices or defined plan. o Response Plan Editor allows the operator to add, edit, remove devices, edit or remove email, add

or remove FLATIS, and add a message plan. o Activate Plan will activate the Response Plan o Throughout the duration of the event, input additional event details in the Comments section. o Click the “Save Changes” button each time a new event is added.

It is imperative that events are continuously monitored and updated to reflect real-time conditions. When a notifying and/or responding agency informs the AAM of changes, the AAM Operator is required to immediately update the information within SunGuide. This ensures the accuracy of the event data and ultimately the integrity of the system.

• To modify an event in SunGuide, simply click on the event located in the Event List Window • Make the necessary changes • Click the “Save” button each time you make a change

Once an event has been confirmed cleared, review the Event Detail screen to ensure all required and relevant information has been entered. Before closing an event, make certain all applicable agencies have been notified and documented correctly. By ensuring the Event Detail is complete, the user is enabling the data to be consistent and to accurately be reflected in the TMC’s SunGuide Performance Measures.

• To change the status of an event or to close an event in SunGuide, simply click on the event located in the Event List Window

• Change the Status located under Administrative Details to reflect the current position of the event – unconfirmed, active, closed, unresolved, false alarm, void

• Review the event details. Make any necessary changes. • Click the “Save” button.

The following are additional functions within SunGuide that the AAM Operator will use on a daily basis:

Block CCTV Images On some occasions, it is necessary to block a cameras’ feed from public viewing. This feature becomes a vital feature of SunGuide when the incident involves injuries and the images are sensitive to the public. To block a camera:

• Click the “CCTV” button located on the top menu bar of the Event List Window. You will be directed to a new page which lists all of the AAM Cameras.

• Located the camera that is to be blocked. • Click the “Block” button located to the right of the camera detail. To unblock a camera:

73

Active Arterial Management TMC Standard Operating Guidelines

• Click the “Block CCTV Images” button located on the top menu bar of the Event List Window. You will be directed to a new page which lists all of the AAM Cameras.

• Located the camera that is to be unblocked. • Click the “Unblock” button located to the right of the camera detail.

Reports Located on the top menu bar of the Event List Window, there is a Report feature which offers the AAM Operator the ability to search and analyze event details and trends. Within the Report window, there are a series of filters that can be used to narrow the search parameters. There are seven categories of reports that make up a variety of report types:

• Event List • Event Details • Event Summary Report • Event Chronology • Event Response • Agency Response Times Report • Event Level Report • Event Lane Blockage • DMS Report • SIRV • QA Report • Notifier Contacts • Performance Measures Reports Manager

There are many occasion where printing a hard copy report is required. To access a report, follow the proceeding steps:

• Click the “Reports” button located on the top menu bar of the Event List window. The user will be directed to a new page which lists all of the report types.

• Narrow the search parameters by setting filters, by the range of events, location, and event properties. • After the filters are set, click the desired report type listed to the right of the filters. • The user will be directed to a new window to view and/or print the report.

Audit This section is used to modify event details. Some examples of event details that can be changed are Time Reported to the TMC, Notifying Agency/Contact, and Event Location.

Preferences This portion of SunGuide allows the AAM Operator to create page refresh preferences. The AAM Operator can indicate the exact time the Event List is refreshed. In addition, the Operator can receive a warning on events that have exceeded the indicated time allowance. *For more information on using SunGuide, please refer to Appendices A & B

74

Active Arterial Management TMC Standard Operating Guidelines

11.6. Police-Escorted Motorcades The following guidelines are established in an effort to provide consistency between FDOT District 5 AAM and other partnering TMCs in the management of possible roadway closures in coordination with the police-escorted motorcade for a VIP(s).

If possible, gather as much information as possible from local police and/or FHP prior to the event. Specific information regarding the location and time of any closures may be not be made public until a few hours prior, if at all for security reasons. When possible, identify where the traffic is blocked off to allow the motorcade to travel undisturbed so appropriate TMC responses can be prepared/made.

There are two types of accepted motorcade activities:

• Rolling Road Block – a police escort will stop or slow lanes down and intermittently block roadways to clear the way for the VIP(s) and prevent traffic from disrupting the motorcade.

• Full Closure – police will preemptively close off full sections of roadways often for miles to ensure the highest level of security and will hold all traffic at strategic locations to prevent traffic from entering the blocked off corridors.

Due to the geo-coded location-based SunGuide and IMD systems, it is only possible to enter Full Closures as an active traffic event. No events should be created for a Rolling Road Block, other than resulting congestion; however, the event should be reported to the AAM Operations Manager for consideration for timing adjustments.

The proceeding steps should be followed for proper management of such events:

• Entry into SunGuide: o Only full sustained closures should be entered o The event type should be logged as “Police Activity”

• 511 FLATIS o In an effort to keep the location of the VIP confidential, messages should not include specific

times nor locations of possible closures. o Only confirmed, sustained closures should be reported and should be reported only as “Police

Activity.” • Consideration for Timing Changes

o Both rolling road blocks and full closures are technically considered Level 3 Events by the standards described previously. While only Full Closures should be submitted within SunGuide/IMD, both should be reported to the AAM Operations Manager/Floor Manager.

• Congestion o Monitor congestion that can build up as a result of motorcade activity o Normal congestion data entry procedures are to be applied.

75

Active Arterial Management TMC Standard Operating Guidelines

11.7. Interagency Event Management An Interagency Event is an event where the AAM, upon requests, assists other MetroPlan partners and/or other boarding districts with messaging for traffic related events that occur within their coverage area. When an AAM Operator is notified by another bordering TMC of an ATE with lane blockage that potentially can affect motorists along the arterial network, the following questions should be asked:

• What is the blockage? • Where is the blockage? • What type of event? • Estimate congestion tail? • Name and agency of notifying operator? • Does the agency request message assistance?

If the agency requests message assistance, a new event should be created within SunGuide. All further event management protocols should be followed.

76

Active Arterial Management TMC Standard Operating Guidelines

Notification & Incident Response Plan 12.Occasionally events will warrant informing local responders such as law enforcement, maintenance, and other agencies to respond to an event. The following are guidelines for reporting events to emergency agencies. Refer to the AAM telephone directory for contact information for the appropriate agency.

Any and all available details about each event should be collected and verified (if possible) prior to notifying any local agencies. Only lane blockage events or events that present a threat to public safety should be reported.

12.1. Emergency Agencies

I‐4, SR 408, SR 417, SR 429, SR 528, & Florida’s Turnpike For any verified events located on any of the above and/or associated access ramps, contact the Florida Highway Patrol (FHP) and notify RTMC Freeway Management Program (FMP) Staff. Once FHP is notified they shall contact Emergency Medical Services (EMS), Fire/Rescue, and/or the Medical Examiner if necessary.

Arterial Events For Orange County, contact the Orange County Dispatch Center; from there they shall contact the appropriate and necessary agencies to respond (does not include HAZMAT). For Seminole County, contact the Seminole County Sherriff’s Office Dispatch center; from there they shall contact the appropriate and necessary agencies to respond (does not include HAZMAT). For City of Orlando, contact the City of Orlando Police Department’s Dispatch center; from there they shall contact the appropriate and necessary agencies to respond (does not include HAZMAT). For City of Maitland, contact the City of Maitland Police Department’s Dispatch center; from there they shall contact the appropriate and necessary agencies to respond (does not include HAZMAT). For City of Winter Park, contact the City of Winter Park Police Department’s Dispatch center; from there they shall contact the appropriate and necessary agencies to respond (does not include HAZMAT).

Law Enforcement Agencies: Orlando PD 321-235-5300 Altamonte PD 407-339-2441 Maitland PD 407-539-6262 Winter Park PD 407-644-1313 Longwood PD 407-339-1297 Lake Mary PD 407-585-1330 Osceola Co. SO 407-348-2222 Orange Co. SO 407-836-3900 Seminole Co. SO 407-665-6650 Volusia Co. SO 386-248-1777 Ext. 1630

Fire Departments: Orlando FD 321-235-5200 Osceola Co. FD 407-348-8688 Orange Co. FD 407-737-2450 Seminole Co. FD 407-665-5100 Volusia Co. FD 386-252-4911 DeLand FD 386-626-7328

77

Active Arterial Management TMC Standard Operating Guidelines

12.2. AAM Management If a severe or unusual event occurs that has a significant impact to traffic or poses a threat to public safety, it is important to bring it to the attention of the AAM Operations Manager. In general, the AAM Operations Manager should be notified of all Level 2 and Level 3 events.

During normal business hours, when there is an unusual and/or unscheduled event that has a significant impact on the geographical coverage area, perform all necessary traffic management steps, then advise the AAM Operations Manager with the following details:

• Time event was detected and verified • Type of event • Roadway and location • Lane blockage

Outside of normal business hours, the AAM Operations Manager should be contacted only for High Profile Events.

High Profile Events 12.2.1.A High Profile Event is defined as any news worthy or unusual traffic related incident occurring on AAM Corridors; specifically, events that management should be made aware of. Some examples are: multiple fatalities, shootings, major infrastructure damage, plane crashes evacuations, and system wide failures to name a few.

High profile events should be managed according to standard event management protocol. Time permitting or after the event is closed, an email should be sent to the group High Profile Events with the subject line of the email as High Profile Event. The body of the email should contain the following information:

• Time and date incident occurred • Event Number • Short Description of Event • Link to news story (if available)

Signal Timing Plan Library 12.2.2.To facilitate the efficiency of the Active Arterial Management’s response to severe or unexpected incidents along AAM coverage areas, a Signal Timing Plan Library is in development. The Library will allow the AAM Operations Manager (through the use of ATMS.now and Tactics) and adaptive signal control systems (InSync and Synchro Green) to implement appropriate timing plans to meet the demands of different events based on location, severity, and duration.

All timing plans shall be developed and approved through a combined effort of all AAM participating agencies.

Prior to the finalization of the signal timing library, AAM Operations Managers should evaluate each event and make the appropriate changes accordingly with the permission of City/County Traffic Staff.

78

Active Arterial Management TMC Standard Operating Guidelines

12.3. FDOT Maintenance The AAM Operator should notify FDOT Maintenance of all incidents involving roadway or property damage and fuel spills. AAM Operators should proactively looking for roadway/property damage and not solely rely on outside sources.

From 7:00 AM – 5:00 PM AAM Operators will contact the FDOT Maintenance Engineer, Mark Garcia: Mark.Garcia@dot.state.fl.us and copy the AAM Project Manager for all incidents involving damage to infrastructure (barriers, bridges, median, etc.), substantial fuel spills (>10 gallons), overturned tractor-trailers, damage to state property, or when traffic control/diversion equipment is needed. Some examples are:

• Vehicle Fires • Damaged Delineators • Roadway signs and uprights • Guardrail • Median • Bridge wall or support • Bridge damage • Fences • Attenuators • Lights and poles • Flooding • Debris in roadway • Open manhole covers • Pavement damage • Fuel spill • Vandalism

Traffic Signals 12.3.1.Traffic signal equipment is the property of the county. For any damage to traffic signal infrastructure including signal cabinets, signal heads, span wire, mast arms, uprights, etc. contact the appropriate City or County Traffic Division.

Seminole County Monday-Friday between the hours of 7:00 AM and 5:00 PM, contact Edgar Principe the Seminole County TMC at (407-665-5680). For after hour emergencies (after 5:00 PM) and on weekends, contact Traffic Control Devices (TCD) at 407-869-5300 or Chinchor Electric at 386-774-1020 should be contacted. The County considers emergency items to be: signal power issues or signal in flash, knockdowns, not cycling properly, phases being skipped, etc. For non-emergency items such as timing changes, contact the Seminole County TMC the following morning. A current on-call list is located at each AAM workstation. Seminole County Traffic Engineering Division – County ATMS Timings Coordinator Robert Fitzgerald: (407-665-5698 or cell 321-377-1971) or by email at RFitzgerald@seminolecountyfl.gov or contact signal technician/ATMS Coordinator Chad Dickson: (407-665-5685 or cell 321-377-2394) at CDickson@seminolecountyfl.gov.

79

Active Arterial Management TMC Standard Operating Guidelines

City of Orlando The City’s TMC is operational 24/7, contact the City of Orlando TMC at (407-246-2020). Contact Steve Jones (TMC manager), Chris Tucker (lead technician), or Eddie (construction) at the TMC. The City allows the on-call technician decide what is an emergency versus a non-emergency item. The City’s signal shop has a tech available almost all weekday hours (Monday-Thursday) to take emergency and non-emergency calls. In the near future they will be increasing the size of the signal shop staff to cover all weekday hours and a rotating signal technician will be designated to be on-call for the weekends. City of Orlando Traffic Engineering Division – City Signal System Engineer Cade Braud: (321-235-5350) or by email at cade.braud@cityoforlando.net or the City’s Transportation Systems Engineer Benton Bonney at 407-246-3626 or by email at benton.bonney@cityoforlando.net.

Orange County Monday-Friday between the hours of 6:30 AM and 6:30 PM, contact the Orange County TMC at (407-837-7777). After 6:30 PM on weekdays and on holidays/weekends, the Orange County Sherriff’s Office (407-836-4357) should be contacted. The County considers emergency items to be: signal power issues or signal in flash, knockdowns, not cycling properly, phases being skipped, etc. For non-emergency items, call Customer Service 311 ((407) 836-3111) or visit the Customer Service 311 webpage. Orange County Traffic Engineering Division – County System Operator/Timing Engineer Hector Bertran: (407-836-7763) or by email at Hector.Bertran@ocfl.net or contact lead signal technician Roger Smith at Roger.Smith@ocfl.net.

City of Maitland Contact the City’s maintenance contractor Control Specialists at (407-628-1965) to report emergency repairs provided an email is sent to the City/Transportation Engineer (Cristina Torres-Reyes, creyes@itsmymaitland.com) notifying the nature of the problem. The County considers emergency items to be: knockdowns and significant equipment failure or damage such as downed signal heads, poles, damaged controller and cabinet and other safety related issues. Examples of next morning items or faults not considered to be emergency repair work are: single bulb out, pedestrian LED insert replacement, timing issues, etc. City of Maitland Transportation Engineering Division – City/Transportation Engineer Cristina Torres-Reyes: (407-539-6217) or by email at creyes@itsmymaitland.com.

City of Winter Park Monday-Friday between the hours of 8:00 AM and 5:00 PM, AAM Operators should e-mail the City’s group email account to coordinate with Butch Margraf and other City staff or contact the City’s signal technicians at (407-XXX-XXXX). After 5:00 PM on weekdays and on holidays/weekends or if the City staff is not available, contact Traffic Control Devices, Inc. (TCD) (407-869-5300) for emergency situations. City of Winter Park Transportation Engineering Division – City Traffic Manager Butch Margraf: (407-599-3411) or by email at bmargraf@cityofwinterpark.org or contact the City’s signal technicians at (407-XXX-XXXX).

Documentation & Reporting 12.3.2.When possible, attempt to capture a screen shot of the CCTV feed showing the damage. Pictures should be saved on the workstation.

80

Active Arterial Management TMC Standard Operating Guidelines

In order to provide follow-up documentation of roadway/property damage to FDOT Maintenance, all comments relative to the damage and any notifications made must be entered in the event details using comment type – Infrastructure Damage. At a minimum, the type of damage and who was contacted and at what time should be recorded.

The AAM Operations Manager is responsible for running the Event List Infrastructure Damage Report on a weekly basis. This report and any supporting images should be sent to the FDOT Program Manager.

12.4. External Agencies Occasionally, events will warrant informing agencies other than those responsible for emergency response. The following are guidelines for which agencies are advised for specific types of events.

Railroad Agencies 12.4.1.While conducting routine scans of the AAM coverage area, there are numerous at grade rail road crossings visible. Due to the obvious risk to public safety and limited control over trains’ progress, Railroad agencies should be notified immediately of the following:

• Any event directly on the railroad tracks • Any event within the limits of the crossing gates • Malfunctions of or damages to at grade crossing infrastructure (gates, lights, etc.) • Suspicious activity or vandalism to tracks and other infrastructure (should also notify local law enforcement

dispatch)

Transit Agencies 12.4.2.Each county’s transit authority does what they can to provide accurate travel time and arrival information of all of their vehicles to their patrons. The appropriate transit authority for each county should be notified at the beginning and end of any Level 2 or Level 3 events detected along AAM Corridors.

If an alligator is seen on the roadway, contact the Department of Fish and Wildlife – Gator Hotline.

12.5. Documentation When notifying any agency, all calls and/or notifications must be recorded within SunGuide/IMD and the Operator Daily Call Log. When entering the details into SunGuide/IMD, it is necessary to indicate whether the agency notified the TMC, or the TMC notified the agency. If there is not an area in SunGuide to indicate the AAM notified a particular emergency agency, documentation should be made in the comments section.

Active Arterial Management TMC Standard Operating Guidelines

Appendix A

SunGuide v6.0 Operator Training Slides

Active Arterial Management TMC Standard Operating Guidelines

Appendix B

SunGuide v6.0 Administrator Training Slides

Active Arterial Management TMC Standard Operating Guidelines

Appendix C

Sample Shift Report

Active Arterial Management TMC Standard Operating Guidelines

Appendix D

Sample Citizen Complaint Forms

Active Arterial Management TMC Standard Operating Guidelines

Active Arterial Management TMC Standard Operating Guidelines

Appendix E

Active Arterial Management Dashboard

Active Arterial Management TMC Standard Operating Guidelines

Appendix F

Maintenance Checklist & Work Order Forms

Active Arterial Management TMC Standard Operating Guidelines

Appendix G

New Hire Access Forms