The Transportation Management Center (TMC) is the central site for collecting and disseminating data received from traffic cameras and vehicle detection devices throughout the City. Essentially, the TMC is the brain of the entire SFgo program. Operators at the TMC will monitor real-time data and video, and have the necessary tools on hand to manage the city's road network.


CONCEPT OF OPERATIONS

November 27, 2001

Table of Contents

Introduction
Mission and Vision Of The Transportation Management Center
Assumptions and Constraints
Functions to be Performed Within the TMC
Types of Operations
Condition Scenarios
Real-Time Operations Sequence
Operation Scenarios

Tools For Operations
TMC Equipment Needs and Constraints

Staffing

INTRODUCTION

This report presents the Concept of Operations of the Transportation Management Center (TMC) for the San Francisco Integrated Transportation Management System (ITMS). It was prepared primarily based on discussions with City staff. For the remainder of this report, the San Francisco ITMS will hereafter be referred to as `SFgo". The purpose of the Concept of Operations is to fully define the operational and institutional relationships, as well as the communication elements of SFgo for all probable functions within the TMC.

MISSION AND VISION OF THE TRANSPORTATION MANAGEMENT CENTER

The TMC for SFgo will enhance the environment, safety and livability of San Francisco by facilitating efficient and effective real-time management of the City"s road network serving transit vehicles, automobiles, bicycles, pedestrians, and commercial vehicles.

The TMC will disseminate and receive real-time information to and from travelers and partner transportation agencies within and beyond the City. The TMC will serve as a place for the public to visit and see first-hand the activities and tools the City is applying to transportation management. The TMC will also serve other functions including maintenance support, a training facility for city transportation management personnel, and a backup emergency response center.

ASSUMPTIONS AND CONSTRAINTS

The following is a list of the assumptions that were developed for the Concept of Operations:

Everything in the system and TMC will have to be continually upgraded over time as technology changes and project opportunities arise.

The initial phase of the TMC will probably cost less than $1M.

The ultimate, fully built out TMC could cost as much as $8M.

Since San Francisco is a transit- first city, one of the primary functions of the TMC will be to facilitate improved transit operations.

All functionality provided at the TMC will also be available at the PacBell Park satellite TMC, the Signal Shop or other satellite TMCs.

Real-time traffic operations will be conducted mainly in the control room of the TMC, not at an engineer"s normal office.

FUNCTIONS TO BE PERFORMED WITHIN THE TMC

This section lists and describes the various functions that are anticipated to be conducted within the TMC.

Coordination of activities with other agencies within the city (e.g., Muni, police, fire, EMS, PacBell Park, etc.) - Collecting and disseminating information for transportation and emergency services performed by agencies that provide services within the City.

Coordination of activities with external transportation agencies (e.g., Caltrans, TravInfo, Daly City, SamTrans, AC Transit, BART, MTC, CHP, Golden Gate Transit, GGHBTD, etc.) - Collecting and disseminating information for transportation and emergency services performed by agencies that provide services within the City.

Transit Preferential Services - Collecting and processing information from Muni for granting transit priority requests and confirmation.

Traffic Signal Timing Adjustments (e.g., manual, time-of-day, traffic responsive) - Allowing the system operator manually change signal timings, or have the system automatically change signal timings based on fluctuations in traffic volumes.

Collecting Data from Field Devices - Having the system manually or automatically collect information from field devices including detection, traffic controllers, and variable message signs.

Remote Control of Field Devices - Allowing the system operator the ability to control field devices from the TMC including traffic controllers, variable message signs and closed circuit television cameras.

Incident and Special Events Management - Allow the system and system operator to manage incidents and special events through monitoring and implementing appropriate plans including coordinating with other agencies.

Freeway Operations Support - Allowing the system operator the ability to coordinate with Caltrans and their Freeway Operations System.

Traffic Detection - Ability of the system to collect traffic information including traffic volumes and occupancy on a real-time basis.

Data Collection, Warehousing, and Analysis (electronic) - Having the ability to process he real-time data that is collected and store it for retrieval as needed.

Enforcement Division Support - Provide support to the City"s Enforcement Division during incidents, congestion and special events.

Street/Lane Closures - Ability to receive information on, and visual monitoring of street and lane closures.

Parking Management - Ability to monitor the status and availability of spaces in parking garages and notify motorists when these garages are full, or what number of spaces are available.

Maintenance Management - Ability to perform maintenance functions including field equipment failure monitoring, automatic notification/dispatch of field technicians, and maintenance activity tracking.

Training - Ability to conduct training sessions with the TMC.

System Administration - Ability to have a system administrator and perform system administration duties for the equipment within the TMC.

Network Management - Ability to have a system administrator perform network management duties including monitoring of the system and perform any troubleshooting.

Facilities Status Monitoring - Ability to monitor the status of all field devices and facilities (e.g. fiber, traffic controllers, middle switches, message signs).

Configuration Management - Have procedures in place to ensure proper configuration management of the system including system troubleshooting, expansion, modifications, and administration of hardware and software.

Physical Storage Space - Designating a portion of the TMC for storage.

Filing System (paper) - Designating a portion of the TMC for a cabinets for filing.

Equipment Setup and Testing - Setting aside a portion of the TMC for setup and testing of equipment including new software, fiber optics, traffic controllers, cameras and message signs.

Group or Team Work Areas and Displays - Setting aside an area for working groups and displays.

Meetings - Setting aside an area for formal and informal meetings.

Display of Equipment Status and Camera Feeds - Having displays (large and small) that indicate the status of equipment within the TMC and in the field. Additionally, have displays for the camera feeds that come back to the TMC.

Commercial Vehicle Access Control/Permitting - Have the ability to gather information on commercial vehicle operations including access and control.

Public Relations - Have a procedure in place for managing public relations including visitors, press releases, and website maintenance utilizing a Public Outreach Plan. Some of these elements include canned presentations about the SFgo for public briefings, and presentations about the SFgo for visiting transportation professionals.

Traveler Information Management - Have a procedure in place to properly manage traveler information including message that appear on variable message signs, highway advisory radios and websites.

Emergency Vehicle Support - Provide the ability to support to the emergency vehicles through preemption and through coordination with the Office of Emergency Services.

TYPES OF OPERATIONS

The TMC will be the focal point for many different types of functions and operations for SFgo. Discussed below are some of the types of operations and functions that are envisioned to be conducted within the TMC.

Real-time Traffic and Transportation Management. This involves the collecting, processing and disseminating of traffic and traveler information on a real-time basis.

Historical Data Processing and Storage. As the real-time information is collected, there will be a need to store the information, including time and date stamps for later retrieval and processing.

Maintenance. There will be a need to maintain the equipment and field devices deployed as part of SFgo. Detecting faults or equipment failures will be performed within the TMC, and dispatching maintenance personnel could be carried out from within the TMC as well.

Setup and Testing. As new equipment, hardware and software is delivered for SFgo, it will be necessary to setup and test the new products within the TMC. This would include a separate test console with network connections and appropriate hardware to setup different devices for testing.



Configuration Management. The ability to properly manage all of the existing and new hardware and software that is added to SFgo as the system expands will be a key function for the System Administrator. This will be accomplished through Configuration Management.

Performance Evaluation and Enhancement of Procedures. As new field devices are deployed including traffic controllers, cameras and variable message signs, there will be a need to evaluate the performance and effectiveness of these devices and its overall effect on the street network. Based on these evaluations, enhancements to certain procedures will need to identified and implemented.

Traffic Engineering Planning and Design. With the collection of real-time traffic information, this information could be used by traffic engineers and planners for planning and design studies.

Training. As SFgo grows and new staff are hired, or new products/technologies are deployed, there will be a need to conduct training sessions within the TMC. Combined with the setup and testing operation, the TMC will be the focal point for SFgo.

Visitors. This operation would consist of accommodating and educating visitors on the various functions and operations that are performed within the TMC.

CONDITION SCENARIOS

The TMC will provide the system operators with the tools to effectively and efficiently monitor traffic and transportation operations from a central facility. While the tools will be available to the system operators, there will be a finite set of conditions that will require the operator to take action utilizing "pre-defined" procedures depending on the condition that needs action. With this in mind, a preliminary listing of the different conditions that will require action from the system operator has been identified and are as follows:

• Incident on a freeway closes lanes or entire freeway
• Incident on a street closes lanes or entire street
• Special event attracts a lot of traffic to one area
• Parking garage/lot fills up
• Major disaster occurs (e.g., earthquake, fire)
• Power outage
• Muni service disruption
• Strike by transit employees
• Recurring conditions
  • Traffic volume changes volume and direction during day
  • Traffic backs up through next intersection
  • Double parking
  • Traffic is diverting around congestion
• Normal traffic and transportation operations
• Multiple incidents occur simultaneously
• Construction closes lanes over a long period of time
• A signal fails (flash or dark)
• Citizen reports a signal out of service
• Citizen reports poor signal timing
• Office engineering needs information about the system, traffic flow, or field conditions
• Transit vehicle running behind schedule needs priority at signal
• Police need surveillance of streets during unusual events
• Critical mass type unplanned/roaming parade
• Fog, smoke or other serious reduction in visibility
• Hardware or software needs setup and/or testing
• Public group wants to see the TMC
• SFgo system suffers security breach
• Major SFgo network/system failure
• TMC is being modified/upgraded (construction activity)

There may be situations where one or more of these conditions would occur. This list identifies the possible conditions. Described below are several of the proposed actions to several of these scenarios.

REAL-TIME OPERATIONS SEQUENCE

In the event condition scenario occurs that requires action from a system operator, a sequence of steps have been identified that should follow. These steps are listed and discussed in brief below.

Collect and Monitor - This is the normal monitoring operations performed by the operator(s).

Alert/Alarm - Once a condition has occurred, an alarm or indication will alert the operator of the situation.

Verify - The operator will need to confirm that the condition is real through verifying the alarm and utilizing Once the condition has been identified, the operator will need to notify the appropriate personnel and divisions which may include Enforcement, Signal Technicians (Signal Shop), Caltrans, Muni, or OES. These agencies may serve to further verify the condition.

Analyze - Once the operator has confirmed that the alarm represents a real condition, he will observe and note any volume/occupancy information that is near the condition and bring up any cameras that can give a visual of the condition. Upon bringing up the nearest real-time transportation information, the operator will need to analyze the effects of the condition on the local streets. Based on this analysis, the operator will need to determine the most proper course of action which may include signal timing adjustments and displaying messages on variable message signs. If available, the operator will need to review any available incident response plans for the area that might be relevant.

Execute Actions - Upon determining the condition and its effects on the local street network, the operator will utilize any procedures that have been set in place including placing messages on variable message signs that will notify motorists of the condition and any action they might consider (e.g., diversion routes), informing other divisions and traveler information services such as the Enforcement Division, OES, and/or TravInfo of the condition, implement signal timing adjustments, and place information on the condition into the SFgo"s website.

Confirm Success - Upon implementing the appropriate response plans and procedures for the condition, the operator will need to monitor the operation to confirm its effectiveness and perform further adjustments as necessary by utilizing the traffic cameras and the traffic volume and occupancy reports

Resume Normal Operation - Once the condition has been taken care of by field personnel, the operator will be responsible for returning the SFgo to normal operations which could include removing the messages from the variable message signs, restoring the signal timings to normal operation, and logging the information on the condition and the actions taken. This logging procedure will eventually need to be automated as much as possible in future phases of SFgo.

OPERATION SCENARIOS

This section illustrates three different condition scenarios that may occur in San Francisco, and describes in detail the necessary actions and procedures that would take place in the event the subject condition did occur.

CONDITION 1: Freeway incident affecting local streets

Collect and Monitor

• Automatic data stream from Caltrans is being monitored by software for serious incidents.
• Caltrans cameras available to city have an icon on a TMC map.
• Caltrans signs in the city have an icon on a TMC map.
• Caltrans generated incident information have an icon on a TMC map.
• Caltrans freeway detector data is used to color freeway links on a TMC map

Alert/Alarm

• Incident occurs and triggers an alarm that pops up an alarm window on workstations and sends a page/call to selected mobile phones.

Verify

• Read text of incident report, view cameras in the area, see what message is on any dynamic message signs in the area
• Ensure it is easy to identify which cameras, signs, etc. are close to the incident. Ideally, the software should automatically bring up cameras in the area, or at least highlight them for manual selection. Could also have an icon to select multiple nearby cameras with one click.
• Use cameras and other available information to verify that the incident is real and as serious as thought.

Analyze

• Analyze effects on local streets by viewing cameras and traffic volume/occupancy on nearby streets.
• Determine which signals need adjustment and which signs need a message placed.
• Review available incident response plans for the area that might be relevant.

Execute actions

• Place message on variable message signs.
• Disseminate information to TravInfo, website, media.
• Adjust signal timing.
• Develop and implement detour routing plan.
• Contact emergency service personnel, Enforcement Division, Office of Emergency Services, Muni, etc.

Confirm success

• View cameras
• View traffic volume and occupancy reports

Resume normal operation

• Blank signs
• Restore normal signal timings
• Log incident info and actions taken (automated as much as possible)

CONDITION 2: Real-time management of recurring congestion south of Market

• Reallocate green time at signals as backup prevents use of green time. Give more time to transit routes where possible.
• Use signal timing adjustments for queue management.
• Implement pedestrian scramble to clear pedestrians and help right turns.
• Give travelers congestion information to influence their time and route of travel
• Guide enforcement personnel to hotspots where they can help free up traffic
• Display message on signs informing approaching motorists of conditions ahead
• Manually control signals while viewing on camera.

CONDITION 3: Earthquake

• Investigate health of SFgo system and communications network.
• Watch TV for information
• Use prearranged contact at other agencies to assess status of other facilities and services.
• Evacuation plans - city areas to be evacuated, TMC to be evacuated.
• Direct maintenance personnel to most critical areas for assessment and fixes.
• Run system diagnostics.
• Identify where power is on and off.
• Communicate with OES.
• Create new signal timings to accommodate closures and rerouting.
• Activate emergency response plan - designated contacts, chain of command.
• If system down, use physical map and white boards to track status of field facilities.

Note: The information inflow could overwhelm available communications capacity, and that much of the informal information could be misleading for the operator.

CONDITION 4: Develop improved operating procedures

• Analyze current performance and effectiveness of current operations.
• Identify changes to procedures that could help.
• Refine signal timings and coordination plans.
• Update operations and maintenance manual.

TOOLS FOR OPERATIONS

In order for the SFgo system operator(s) to be effective and efficient with the system and its operation, they need sufficient tools both within the TMC and out in the field. In addition, they need other tools over and above hardware and software tools. Both of these types of tools are described below.

• Detectors - to collect traffic volumes and occupancy.
• Cameras - To provide visual monitoring of transportation conditions.
• Variable Message Signs - To inform motorists of transportation conditions.
• Signal controllers - To properly manage traffic, including during response modes.
• Software and hardware - To properly operate and communicate with field devices, other TMC"s and personnel.
• Computers - To operate the Integrated Transportation Management System.
• Communications network - To communicate with the field devices and other agencies and divisions.
• Displays - To properly display visual images within the TMC.
• Furniture - For the system operators and engineers within the TMC.
• Trained personnel - To maintain an efficient and effective SFgo operation.
• Response Plans - To be able to properly respond to conditions that require a change from normal operation.
• Internet access - To disseminate real-time transportation information to the public.
• Web site - To give the public information on the SFgo, its functions and real-time information.
• Communications testing and troubleshooting instruments - To properly operate and maintain the SFgo and all of its components.
• Fax - For exchange of hardcopy information.
• Printers - For exchange of hardcopy information.
• Pagers - For effectively locating the proper personnel in the event of an alarm or emergency.
• Telephones - For voice communications between personnel.
• Voice radio on city maintenance, Muni, and police channels - For voice communications to San Francisco personnel involved in transportation management and maintenance.
• Mobile phones - For mobile voice communications between personnel.
• Alarm/PA in office area to request help in the TMC - To notify personnel within and outside of the TMC.
• Designated mobile phones (primary and backup) - For other agencies to contact TMC personnel.
• Cable TV - For display of real-time visual images from the field cameras to the public.
• VCR - For capturing any necessary visual information for later processing and review.
• Speakers - For voice announcements within the TMC.
• Dial-in modems and other remote access means - For wide area network access to other computers and the Internet.
• Red phone to OES - For emergency access to the OES.
• Satellite TMCs at Signal Shop, OES and PacBell Park - For system backup of the TMC at 25 VanNess Avenue, and for information to be provided directly to appropriate DPT personnel.
• AM/FM/weather radio - For real-time announcements of conditions that are received via other sources not directly linked to the TMC.
• White boards - For working sessions, training and during emergency management.
• Wall maps (physical) - metal for magnets - For static display of maps for use by the system operators within the TMC.
• Colored stick-on dots/pins/magnets - For indicating key elements on the static maps.
• Map highlighting location of emergency services including hospitals - For quick locating of appropriate facilities in San Francisco.
• As-built design drawings (streets, signals, equipment) - For retrieval and evaluation of existing infrastructure for planning and design purposes.
• Operations & Maintenance (O&M) Manual - For proper maintenance procedures performed by DPT personnel on SFgo.
• Evacuation Plan - For use during a massive City emergency.
• GIS access - For effectively monitoring and updating information for the SFgo.
• Base maps - For retrieval and evaluation of existing infrastructure for planning and design purposes.
• Central control of field devices - For the system operators to monitor and control all field devices from within the TMC.
• Camera control and video feed access privileges and overrides - To properly assign access to video feeds and control of field cameras by appropriate personnel and to gain back control in the event of a condition requiring visual confirmation.
• Asset Management software - To properly track and manage the assets of SFgo for seamless troubleshooting, expansion and upgrades.

TMC EQUIPMENT NEEDS AND CONSTRAINTS

This section describes some of the basic and detailed needs and requirements as input to the design of the TMC. These needs and requirements provide general guidance on the thinking for the design of the TMC in attempting to accommodate all of the anticipated functions. As more information is received, including more accurate cost estimates and TMC visualization layouts, it is anticipated that some of these requirements will need to be revised.

1. It is preferable to have workstations situated on wheels.
2. The furniture should consist of stackable chairs for flexibility.
3. Since there is a raised floor consisting of replacement panels available with trapdoors, the layout should include provisions for many patch panels for flexible connections of equipment throughout the TMC.
4. It will be important to use relatively flat tables rather than traditional consoles for better functionality and flexibility.
5. It is desirable to use two (2) flat panel displays at workstations. The displays would be on swing arms which will allow them to swing out of sight if necessary. This will allow the number and size of workstation display screens to be changed over time.
6. The design should allow for one workstation to be spread across two screens at the desktop.
7. The design should allow for up to two (2) computers at each workstation.
8. The TMC should have bookshelves and file cabinets on wheels that would enable them to be rolled up to any workstation.
9. The design should include provisions for adding VCRs and other peripheral equipment and other rack/shelf mounted equipment for users.
10. The initial design could perhaps consist of a front projection system, projecting images onto a curved rigid screen (wall). This will facilitate resizing and rearranging displays without any changes to the screen (wall). The front projectors would hang from the ceiling -- can have a door in it to get behind?
11. Another design could have a rear projection system like Caltrans. This could take up too much space, but may able to be accommodated within the TMC design.
12. The design should consider flat panel plasma displays. However, these units would be to be resized easily. They can be more expensive than other displays of comparable size and they also utilize a 16:aspect ratio which distorts images not produced in this format.
13. The raised air conditioning unit and lights may enable the screen to extend all the way to the beams providing additional vertical viewing area.
14. The display units shall allow formats of NTSC, S-Video, VGA, SVGA, XGA, SXGA, digital or analog on main video wall.
15. If HDTV screens are not used in the large video displays, the design should provide separate plasma display(s) for HDTV-compatible feeds.
16. In accordance with ADA requirements, it will be necessary to keep things moveable within the TMC.
17. The design should provide at least three (3) workstation desks, a group worktable and a setup/test area.
18. The design should accommodate at least six (6) computers with two (2) monitors per workstation.
19. Dual monitors will be needed on the existing computer in each existing office and cubicle.
20. The lighting design should include provisions to accommodate the general area, the work area, and the test/setup area
21. All of the equipment will need to be tied down in the event of earthquakes.
22. The design could include setup and test benches that may able to be located behind a visual screen.
23. The design should include a plasma display in the conference room.
24. The design should include a workstation in the conference room.
25. The design should include a group worktable with a workstation in the TMC control room.

Other issues

Investigate adequacy/suitability of air conditioners, sprinklers, etc.

Is there enough space for ultimate build out?

STAFFING

This section briefly describes the proposed staffing types for SFgo. It does not include a detailed analysis of the required staffing needs for the overall program, but identifies the relative staff positions that will be necessary for the successful and seamless operation of the system. The overall Strategic Plan will identify the appropriate staffing levels over the course of SFgo"s 20-year program.

TMC Operators - These are the individuals who will be stationed within the TMC control room and be responsible for monitoring of the system.

Network/system administrator - This individual will be responsible for the maintenance of the network within the TMC. In addition, this person will be responsible for overseeing the access privileges and ensuring that all equipment and devices are functioning properly primarily within the TMC. Utilizing the asset management strategies and tools, this person will need to ensure that new system components are properly documented and kept up to date.

Supervisor - This individual will be responsible for overseeing all of the system operators and as well as the System Administrator. Other duties may include coordinating the public relations functions and ensuring that policies and procedures are maintained and followed by all TMC personnel.

Maintenance technicians - These individuals will be primarily responsible for maintaining the ITMS field components, including responding in the field to troubleshooting calls, overseeing field construction activities associated with the ITMS and performing routine operations in the field.

System engineers - These individuals will be responsible for the design of the system and and enhancements/modifications. Utilizing Configuration Management procedures, these individuals will be able to design components for the ITMS which will ensure some form of interoperability and continuously allows for expansion for the system.

Clerical - These individual"s primary responsibility is to properly maintain the archive system and any hardcopy materials that are to be stored within the TMC.

Public relations - This individual will be responsible for overseeing the public relations component of the ITMS.

Return to About

• Links to our partner Web sites:
  • Caltrans
  • California DMV
  • SF Traffic Court
• Also on sfmta.com:
  • About Us
  • Enforcement
  • Parking Information
  • Parking Tickets
  • Residential Parking Permits
  • ISCOTT
  • Street Closures
  • Traffic Projects & Planning
• Livable Streets links:
  • Top
  • Updates
  • Traffic Calming
  • SFgo
  • School Area Safety Program
  • Better Streets
• Sitewide links:
  • SFMTA Home
  • Search sfmta.com
  • Site Map
  • Legal
  • About sfmta.com
  • Contact Us
  • 511.org
  • SF City & County website

• Top
• SFMTA Home
• Webmaster
• Site Map
• Legal

• About sfmta.com
• Contact Us
• 511.org
• SF City & County website

Copyright © 2000-2008 SFMTA. All rights reserved. Updated July 29, 2008