TABLE OF CONTENTS

Page

VERSION CONTROL.................................................................................................................................................................. 1

1. Introduction............................................................................................................................................................ 1-1

1.1 Executive Summary......................................................................................................................................... 1-1

1.1.1 TMC Operations................................................................................................................................................ 1-1

1.1.2 Maintenance Operations................................................................................................................................. 1-2

1.1.3 Management...................................................................................................................................................... 1-2

1.2 Stakeholder Identification..................................................................................................................... 1-2

1.3 Goals and Objectives...................................................................................................................................... 1-3

1.4 Typical Scenario – Day in the Life......................................................................................................... 1-4

1.5 STRENGTHS & WEAKNESSES.............................................................................................................................. 1-4

2. TMC Operations....................................................................................................................................................... 2-1

2.1 SYSTEM LOGON/SECURITY................................................................................................................................. 2-1

2.2 Graphical user interface........................................................................................................................... 2-3

2.3 COMMANDS............................................................................................................................................................... 2-7

2.4 REPORTS...................................................................................................................................................................... 2-8

2.5 TYPICAL OPENING OPERATION......................................................................................................................... 2-9

2.5.1 Typical Opening – Single Commands........................................................................................................... 2-9

2.5.2 Typical Opening – Macro Commands........................................................................................................ 2-12

2.5.3 Typical Opening – Super Macro Commands............................................................................................ 2-14

2.6 General Coordination................................................................................................................................ 2-15

2.7 Support.................................................................................................................................................................... 2-16

2.7.1 Simulator.......................................................................................................................................................... 2-16

2.7.2 Documentation................................................................................................................................................ 2-16

2.7.3 Training............................................................................................................................................................ 2-16

2.8 Coordination with Other Systems..................................................................................................... 2-16

2.8.1 Advance Traffic Management System (ATMS).......................................................................................... 2-17

2.8.2 Congestion Pricing System........................................................................................................................... 2-18

2.8.3 Special Projects.............................................................................................................................................. 2-18

2.8.4 Other systems................................................................................................................................................... 2-19

3. Maintenance Operations................................................................................................................................ 3-1

3.1 MODES OF OPERATIONS........................................................................................................................................ 3-1

3.1.1 Opening/Closing Operations......................................................................................................................... 3-1

3.1.2 Emergency.......................................................................................................................................................... 3-2

3.1.3 Non-Typical....................................................................................................................................................... 3-2

3.1.4 Maintenance Functions................................................................................................................................... 3-2

3.2 Coordination........................................................................................................................................................ 3-3

3.2.1 Opening/Closing Operations......................................................................................................................... 3-3

3.2.2 Emergency Operations..................................................................................................................................... 3-4

3.2.3 Preventative/Corrective On-Lane Maintenance......................................................................................... 3-4

3.2.4 Installation of New Devices............................................................................................................................ 3-4

3.2.5 Special Projects or Operations...................................................................................................................... 3-4

3.3 Reports...................................................................................................................................................................... 3-4

3.3.1 Routine Maintenance....................................................................................................................................... 3-4

3.3.2 Failure................................................................................................................................................................ 3-5

3.3.3 Logistics/Inventory........................................................................................................................................... 3-5

3.3.4 Scheduling......................................................................................................................................................... 3-5

3.3.5 Incident............................................................................................................................................................... 3-5

3.4 USER INTERFACE..................................................................................................................................................... 3-5

3.4.1 Access.................................................................................................................................................................. 3-5

3.4.2 Verification........................................................................................................................................................ 3-6

3.4.3 Coordination..................................................................................................................................................... 3-6

3.4.4 Alarms................................................................................................................................................................. 3-6

3.4.5 GUI....................................................................................................................................................................... 3-6

3.4.6 Daily Diary......................................................................................................................................................... 3-6

3.4.7 Security............................................................................................................................................................... 3-6

3.4.8 Workorder Entry............................................................................................................................................... 3-6

3.4.9 Expert Guidance System.................................................................................................................................. 3-7

3.5 Support...................................................................................................................................................................... 3-7

3.5.1 Hardware............................................................................................................................................................ 3-7

3.5.2 Simulator............................................................................................................................................................ 3-7

3.5.3 Documentation.................................................................................................................................................. 3-7

3.5.4 Training.............................................................................................................................................................. 3-7

4. SIMULATOR.................................................................................................................................................................... 4-1

4.1 Overview.................................................................................................................................................................. 4-1

4.2 Functionality...................................................................................................................................................... 4-1

4.3 Location................................................................................................................................................................... 4-2

5. Management.............................................................................................................................................................. 5-1

5.1 management INFORMATION.......................................................................................................................... 5-1

5.1.1 Information On The Safety.............................................................................................................................. 5-1

5.1.2 Information On The Facility Benefits........................................................................................................... 5-1

5.1.3 Information On The Labor Hours.................................................................................................................. 5-2

5.1.4 Information on the Facility Usage................................................................................................................ 5-2

5.1.5 Information On Significant Maintenance Issues........................................................................................ 5-2

5.1.6 Inventory Tracking Of Facility Equipment.................................................................................................. 5-3

5.1.7 Expansion And Enhancement Plans For The Facility............................................................................... 5-3

5.2 MANAGEMENT ACTIVITIES................................................................................................................................ 5-3

5.2.1 Labor Resources................................................................................................................................................ 5-3

5.2.2 Facilities & Equipment.................................................................................................................................... 5-3

5.2.3 Training.............................................................................................................................................................. 5-4

5.2.4 Growth Path For Personnel............................................................................................................................ 5-4

5.2.5 Promotion Of The Facility.............................................................................................................................. 5-4

5.2.6 Expansion And Enhancement Budget Planning......................................................................................... 5-5

1. Introduction

1.1 Executive Summary

This document articulates the User Requirements for the I-15 Reversible Lane Control Systems Upgrade and Modernization. The form of this document is a free form non-structured narrative that reflects the needs, expectations, and desires of the Stakeholders involved in the System. It will be the task of the development team to take these User Requirements and translate them into the Technical System Requirements. The User Requirements is a synthesis of several interviews and workshops that were held with the Stakeholders and with the consultant for District 11 for the broader Advanced Traffic Management System (ATMS) currently under development. This document lays out the User Requirement from the following three prospectives:

1.1.1 TMC Operations

The needs and desires of the TMC Operations identified, without any reduction in the safety or security of the system, are as follows:

· Maintain the standalone environment of the I-15 Reversible Lane Control System,

· Operate the I-15 system more effectively and efficiently by providing the TMC Operators with better visual verification of field devices,

· Ease the operations process by an improved Graphical User Interface (GUI) for the TMC Operators,

· Improve the coordination with other systems through electronic data interfaces,

· Improve the coordination with maintenance in the area of troubleshooting and preventive maintenance,

· Improve the administration of the I-15 Reversible Lane Control System including security, report generation and system configuration.

1.1.2 Maintenance Operations

Maintenance is a critical concern of the system. The following are results of the workshops and interviews.

· Improve the maintenance of the system by providing better troubleshooting aides and tools from the system,

· Improve the field operations on opening and closing of the facility by better field device verification by the TMC and Maintenance Operations,

· Improve the mean time to repair by providing on-line maintenance support in the form of electronic problem reports and improved fault identification from the system.

1.1.3 Management

The management of the system had the following needs and desires:

· Improved reporting on system benefits,

· Improved visibility on system performance such as maintenance, safety, and security,

· Recognizing the potential as the testbed for advancing the Intelligent Transportation Initiatives.

1.2 Stakeholder Identification

The following Stakeholders and Consultants were part of the Requirements Working Group that participated in the development of the User Requirements through a number of interview and workshops.

I-15 Reversible Lane Control Systems Requirements Working Group
Position	Name	Company/Department	Phone/E-Mail
Stakeholder	Lynn Barton	Caltrans AHS	(619) 688-6088
Stakeholder	Don Day	Caltrans Software	(619) 467-3072
Stakeholder	Herb Patchel	Caltrans Chief Electrical/ Project Manager	(619) 467-3025
Stakeholder	Ernesto Fermin	Caltrans – Project Engineer	(619) 467 3058
Stakeholder	Dave Pham	Caltrans – I-15 Reversible Lane Maintenance	(619) 467-3041
Stakeholder	Stu Harvey	Caltrans – District Division Chief, Operations	(619) 467-3000
Stakeholder	Dave Dutcher	Caltrans – Communications	(619) 467-4330
Stakeholder	Barbara Rinkleib	Caltrans – I-15 Reversible Lane Operator	(619) 467-3032
Stakeholder	Debra Warnholtz	Caltrans – I-15 Reversible Lane Operator	(619) 467-3200
Stakeholder	Marcus Cinco	Caltrans – I-15 Reversible Lane Operator	(619) 467-3201
Stakeholder	Shahin Sepassi	Caltrans - ATMS	(619) 467-3054
Stakeholder	Benny Herrera	Caltrans - Maintenance	(619) 467-4007
Stakeholder	Bill Tanner	Caltrans - Maintenance	(619) 467-4010
Stakeholder	Dave Porter	Caltrans – Maintenance	(619) 467-4010
Stakeholder	Harrison Makau	Caltrans - Software	(619) 467-3064
Stakeholder	Susie Martin	Caltrans - Software	(619) 467-3068
Stakeholder	Greg Gastelum	Caltrans – Program Manager	(619) 688-0262
Stakeholder	Ross Cather	Caltrans – Chief of Traffic Special Studies	(619) 467-3022
Stakeholder	Chris Thomas	Caltrans – Chief of Advanced Planning	(619) 688-3671
Stakeholder	Tarbell Martin	Caltrans – I-15 Reversible Lane Operations Manager	(619) 467-3204
Stakeholder	Karen Wallace	Caltrans – I-15 Reversible Lane Operations Supervisor	(619) 467-3203
Stakeholder	John Waddell	Caltrans - Maintenance	(619) 467-4007
Consultant	Chuck Dankocsik	TransCore	(626) 585-0365
Consultant	Moojan Khazra	TransCore	(626) 585-0365
Consultant	Ken Johnson	TransCore	(714) 758-0019
Consultant	Teresa Squires	TransCore	(714) 758-0019
Consultant	Michael E. Krueger	TransCore	(714) 758-0019
Consultant	Bruce Churchill	NET	(619) 467-4323

Exhibit 1.1: Working Group Lists

1.3 Goals and Objectives

The goals of the new I-15 Reversible Lane Control System are:

· To maintain the current standalone control operation,

· To maintain the current level of safety,

· Upgrade and modernize the existing system to improve both, the reliability of operational commands and command sequence recovery,

· To use existing field equipment such as the gates, the pop-ups, the CMS, the CCTV, the air supply system, the power system, the lighting, and the communications lines between the FCUs and the individual DCUs,

· To improve the user interface,

· To have an open system design for easy integration with existing and future systems.

1.4 Typical Scenario – Day in the Life

For further information about a typical scenario, please refer to Chapter 5 of the Existing Control Systems Report.

1.5 STRENGTHS & WEAKNESSES

The following table shows the current existing Strengths and Weaknesses of the I-15 Reversible Lane Control System and the recommended enhancements to the system.

Strengths: Descriptions: Section:

Architecture	Current architecture should be carried over to the new upgraded systems with some enhancements on communications connectivity among the processing levels	General
Safety of the System	Should maintain the safety of the facility and improve areas that may improve the safety where appropriate by better organizational coordination	General
Field Devices	Field devices such as the pop-ups, CMS, gates, air supply system, and CCTV should be used wherever possible but may be enhanced or improved wherever possible. Additional devices should be added if appropriate.	General
Operation procedures and personnel	Current operation procedures and personnel should be maintained and augmented with improved tools for the operations of the system. These include sequencing, overrides, levels of command, such as individual device commands, macro commands, security procedures, scheduling etc. Enhancements should be made such that the system can off-load the operator in some of these areas where appropriate.	General
Dedicated maintenance	Should maintain the current dedicated maintenance personnel who understand and are responsible for the day-to-day maintenance of the facility. Enhanced tools should be made available to ease the maintenance and troubleshooting of the system.	General

Weaknesses: Descriptions: Section:

Single user system	Should have multi user access, with only one operator control	2.1
Textual based menu interface	Should be a graphical user interface	2.2
Minimal and cryptic report capability	Should have multiple reports with exportable capability to commercial Word Processing, Database and Spreadsheet packages	2.4
Safety features are highly manual with limited assistance from the system other then alarms and limited field verification	Should maintain the safety features of the system – Improve system trust and verification feedback.	General
Multiple terminals needed to maintain safety of the system	Should be a Integrated Workstation that provides needed information of Operations	2.1
Logon features cumbersome	Should have an improved logon procedure	2.1
Intensive maintenance support	Should install workstation for the Maintenance personnel, so that they can view the system.	3
Simulator and training capabilities limited	Should install a workstation that is dedicated to simulation/training. Have simulated or duplicated set of field training devices to test and train personnel with.	4
Macro and device level commands available to the operators.	Should implement the super macro level control to the set of tools for the operators at this level.	2.3
Limited and manual visual confirmation of the reversible roadway device status.	Should use the fixed CCTV images for final verification of the roadway devices.	2.2
Macro command sets prone to system hang-ups	Should enhance the reliability of the single, macro and supermacro command capabilities and improve error checking and verification	2.3
Override capabilities limited	Should improve override capabilities by improved error checking, auto-retries and verification	2.3
System administration is difficult e.g. reprogramming EPROMs in the field	Should have an improved system administration with a stand-alone GUI, which has configuration option. Configuration option should have functions to add, delete, and modify users and devices. No reprogramming of EPROMs necessary.	2.1
General reliability of the system is low due to factors including comm. faults, command sequencing and error checking.	Should improve the general reliability of the system. Should improve error checking, improve the window timing for commands, immediate feedback on errors, and non-responsive devices	General
Help capabilities limited	Should improve help facility with on-line feature	2.2
Limited CCTV coverage of roadway	Should enhance CCTV coverage of roadway – (Not a Substitute for Manual “Sweeping of the Roadway”)	General
Many features physically implemented but not operational due to non-implemented software	Should implement the features that are physically implemented, but not operational in software	General
System is currently isolated from other systems that need to exchange information	Should develop interfaces to these systems through a “Firewall” at all levels.	2.7
Limited upper management reporting and system visibility	Should improve management reporting	5
Awareness of activities on the facility and coordination with other departments difficult, e.g. scheduling activities, current activities etc.	Should provide system e-mail and or groupware to enhance the coordination activities on the facility	2.6
Operations of the Opening and Closing of the facility are intense and critical. An operator can easily get overloaded during these critical times	Should improve GUI to integrate needed information and filter non-essential information (reduce false alarms) to the operators, improve the operators interface such that less experienced operators may effectively operate the facility without sacrifice in the safety of the facility.	2.2
System is outdated and not easily expandable.	Should upgrade the processing hardware, operating system and application software, interfaces, and communications.	2.5.1
Support	Should improve As-built documentation and training.	2.5.3

2. TMC Operations

TMC operations are the heart of the I-15 Reversible Lane Control System. These operations are categorized into 6 distinct groups:

· System Logon

· System Security

· GUI

· Commands

· Reports

· General Coordination

The last sections in this chapter will show an example of a typical morning opening of the I-15 Reversible Lane Control System lanes, using the three command groups. These command groups are discussed in the command section.

2.1 SYSTEM LOGON/SECURITY

The overall I-15 Reversible Lane Control System should be capable of multi-users. The current system allows only one user at a time and requires the user to enter the terminal type before logging on. The system should not require the user to enter the terminal type and should handle, at a minimum, the following users concurrently:

· TMC user workstation

· Maintenance workstation

· Simulator/training workstation

· Software development/testing workstation

· FCU North workstation

· FCU South workstation

· Remote dial-in user

· Emergency users at the individual device locations

Any user currently logged onto the system should be able to view all other users from the Current Users Report. This report is discussed later. Only two workstations, the simulator/training and the software development/testing workstation, should not be connected to the actual I-15 Reversible Lane Control System. These two workstations should contain the exact software and GUI as the regular workstations, but should primarily be used for training and testing. These workstations should be networked to the other workstations and should be able to become a working workstation if an emergency arises and the workstation is needed. As stated above, the system should allow multiple users to be logged on, but only one user should have control capability over the system. Further discussion of control is in Section 2.3.

The security levels should be as follows:

Operator # 5	Lowest level. Operator # 5 level should only review and print reports, navigate through the display, and view system statuses. Mainly used on the simulator for training purposes.
Operator # 4	Maintenance personnel. Operator # 4 level should have same capabilities of operator # 5, but can also review and generate problem work order forms, send/receive e-mail and make entries into the Daily Diary. Should have no control over the system.
Operator # 3	Operator level # 3 should have the capabilities of lower operator levels and be able to perform the super macro command set. Also has the capability to review and generate Daily Diary entries, as well as problem work order forms. The user also has the abort functionality capability.
Operator # 2	Operator level # 2 should have the capabilities of lower operator levels, but also do the macro command set.
Operator # 1	Operator level # 1 should have all the capabilities of the system, except the configuration option. User has single (device), macro, and super macro command sets capabilities, the abort capability, and the override capability.
System Administrator	System administrator level should have all the system capabilities, including the configuration option. The option includes addition, modification, deletion of users and devices, configuration of color status displays, and the addition, modification, and deletion of the paging profile list. Rules of the roadway can also be configured from this option.

Configuration and security should only be handled by the designated system administrator. If for some reason the designated system administrator is absent, a backup system administrator should be appointed and should be aware of what actions the system administrator had been performing. The system administrator should have access to the entire system. An important file for the administrator is the logon file. Currently this file is included in the software that is “burned into” the EPROMs at each device location. Also included in the file is the security level for each user. The administrator, working with the operator supervisor, should assign the correct security level for the individual users. The user must enter a valid username and password, which is verified by the software searching the logon file. This system administrator should be able to do the following to the logon file:

· modify the file easily,

· modify the file interactively (system is on-line and does not require restart, but user must log off before modifications are effected),

· no “reburn” of EPROMs for the devices,

· expandable to allow for more users,

· maintain existing security levels of individual users.

2.2 Graphical user interface

GUI encompasses several things: logon, security, status display, and menu display. Once the user is successfully logged onto the system and the security level known, the system displays the main menu and the graphical representation of the system area. Dependent upon the security level, menu options are highlighted if the user is allowed to perform those operations. The security level assignment is discussed in the previous section.

The display should include all existing menu options, as well as new options, and those options that are available to the user should be highlighted. For example, the configuration option should be available only to the system administrator, but should be seen by all users as an option.

After successful logon, the system should display graphically, an overall view of the system area. This graphical display should encompass the system to the existing boundaries and should be expandable for future growth in both devices and boundaries. This display should also include the volume and speed information for the parallel mainline, as well as the ramp meters and their information for this display. The display boundaries should extend at minimum, an additional mile past the current system boundaries.

The graphical display should indicate the direction of the traffic flow if the reversible roadway is in operation. If it is not in operation, no indication of traffic flow should be shown on the display. An indicator should be displayed showing the overall status (open or closed), of the reversible roadway. The graphical display should indicate the current status of all system devices. The status color code of all devices should be a user configurable item accessible only to the system administrator in the configuration menu option. The devices shown on the display should include:

· TSU

· FCUs

· DCUs (Locations)

· Gates

· Pop-ups

· Draw lights

· Wrong way lights

· CMSs

· CCTVs

· Air Supply systems

The status should include as appropriate for the devices:

· On-line

· Off-line

· Failed

· Message

· Up

· Down

· Open

· Closed

The main display window should include the user name, current date, and current time. Also shown on the display of the system area should be icon indicators to allow for the zoom in and zoom out functions. These icons should be readily identifiable and accessible to the user. A general message line should also be shown on the display. This message line should be current and show the last executed command operation of the user for this session.

Movement through the display should be done in either of two ways. The first way should be “point and click” method. The user selects a specific device by a single click on it. The device should indicate, by flashing, that it has been selected. The user should then select from the menu options, the status option. A separate window should appear with the following information about the specific device: device name, device number, device location, device status, and any specific device information. For example, a CMS status window should indicate the current message being displayed, while the pop-up status window should also indicate air pressure minimum and maximum values, as well as the above mentioned status information.

The second method of movement is the “double-click” method. The user should be able to “double-click” on the specific device and the status window should appear. The status window should be the default window for this method.

The user should be able to select a single CCTV device and the roadway video image should be shown in a new window. These images should allow the user to view the system area and assist in the verification process of the determination that the roadway is clear. These images should not be considered a substitute for the manual “Sweeping” of the roadway to ensure that it is clear. Maintenance personnel should still be available to confirm for the system user the state of the area. The purpose of these CCTV images should be to support the system user and the maintenance personnel. The CCTV images should not be available to any other user except the TMC workstation.

A set of fixed CCTV Cameras should be deployed to view each of the field devices. This would allow the TMC operator to verify the status of every field device without manual observation. This system should be integrated into the current CCTV system.

The menu items should be menu options and should include the existing functions, like the diagnostics menu, the time menu, and system shutdown. Other menu options should include control, reports, “System Information”, status, help, and configuration option. Further discussion of the report option is in a later section.

The “System Information” option should contain “Daily Diary”, “Problem Work Order form”, and “Scheduler” options. These options are the only options that allow the user to enter information to the system. The “Daily Diary” should allow the user to enter free form text comments. It should automatically show the user name, current date, and current time in the window and this information, as well as the comments, should become part of the information added to the Event Log Report. The “Problem Work Order form” should appear when the system has indicated a failure. This form should contain the current date, time, problem name, location, description, problem status, comment section, and personnel assigned to review the problem. The “Scheduler” option should allow the user to enter events that affect the reversible roadway facility. These events should include maintenance work and special project work.

The status option should contain a general categorization of the devices. This option should allow the user to view the status. For example, one option should be for CMS. If selected, the user should see the status of all the system’s CMSs. This status window should contain the device number, location, current message, current status, date, and time. Another option should be for device location, like DCU #1. This status window should show the user the status on the gate, the pop-ups, and the lights. Again, this window should quickly show the user the status of this device.

The configuration option should include the functions to add, delete, and modify users, devices and the paging profile; configuration of status color display; and other general configuration parameters. The paging profile should be a table that will indicate appropriate emergency personnel information. This information should contain name, pager number, and email address. This paging profile should be used by the user, when a system failure occurs and emergency personnel must be contacted.

The help option should contain several options. These options should include I-15 command definition and description, I-15 parameter definition and description, and a general GUI command definition and description.

2.3 COMMANDS

At any time, the command control capability of the system should be with only one user. If another user with a higher security level logs on, the new user should be prompted for control access. If control is taken by the new user, the previous user must be alerted that control has been taken and who has taken it. If at the time of logon, control is not taken, the user can take control at any time during that session. That option should be included in the control menu option. If the user decides to take control of the system, the current control user should be alerted to the fact that control is to be taken and by who.

Command control of the I-15 system can be achieved through several command sets. These are: single command, macro commands, which are sequentially executed single commands, and super macro commands. This feature should remain the same. The command set should be determined by the user’s security level.

Once the user has determined which device to perform the operation on, the user should “point and click” on the device icon on the graphical display screen. The user should then select the “control” menu option and should then view a separate window with the valid list of operations for that device. The user should then “double-click” on the desired operation for execution. After selection has been double-clicked upon, the user should receive a command action confirmation window. After confirmation has been received, the system should execute the command. If negative confirmation is received from the user, the system should discard the requested operation.

If the user determines that an operation should not be executed, the user should be able to select the operation from the Current Command Report and then should be able to perform the abort function. The system should acknowledge the abort command and should include in the Event Log Report, those portions of the command that were executed prior to the abort operation.

The user should be able to select a device from the system display and if desired, override the command for that device only. The override function should be available only to those users with the appropriate security level. The override function should be able to be performed on a system level as well as an individual device level. As a safety feature, the override function should have a limited time period. This time period should be a user configurable item that is accessible only to the system administrator.

With both the abort and the override operations, the user should be prompted for confirmation of these operations. The confirmation, as well as the actual operation command should be included in the Event Log Report and the Current Command Report.

2.4 REPORTS

It is envisioned that reports should be generated by the system. All data within the system should be exportable, and can be captured by a commercial word processing, spreadsheet or database software. Once the exporting is completed, both standard reports and templates for custom reports should be developed using one of the many commercial database tools available.

As an option, the report menu item should include the following:

· Current Command Summary Report – should show the time and result of the user commands issued during the current session for which this report is opened.

· Event Log Report – should show all system events that have occurred since midnight. These events should include logon and logoff, all system commands, and system failures.

· Current System Status Report – should show the current status of all the devices in the system.

· Schedule Report – should show all events scheduled for the system

· Failure Summary Report – should show all system failures since midnight

· HOV Lane Count Report – should show the counts per HOV lane by hour (vehicle per hour).

· Current Command Report – should show only those commands executed in the previous 5 minutes

· Current Users Report – should show all users currently logged onto the system. This report should contain the date and time, as well as the user name and indicate which user has command control of the system

All of the above listed reports should be displayed on the workstation in a separate window display, as well as be directed to a file. This file should then be able to be edited and/or exported to another software package if so desired by the user. The report window should be able to be minimized or closed by the user.

All the reports except the Current Command Summary Report, the Current System Status Report, the Current Command Report, and the Current Users Report should be on a daily basis and should start at midnight of the current day. The previous day’s report file should be saved and should be able to be retrieved by the system administrator at another date and time. The file name of the report should contain the date and some indication of the name of the report.

The Current Command Summary Report, the Current System Status Report, and the Current Users Report should be for the current date and time. Information on these reports should also be included in the Event Log Report, and if necessary, the Failure Summary Report.

2.5 TYPICAL OPENING OPERATION

The following section describes a typical opening with the features discussed in the previous sections. This opening sequence is taken from the Existing Systems Document, Chapter 5. Several assumptions, valid logon and security level, should be made for this discussion. This section describes a typical opening using single executed commands, a typical opening using the existing macro commands, and a typical opening using the “super macro” commands.

2.5.1 Typical Opening – Single Commands

For this section, the security level for this user is operator #1 level. At the beginning of the opening shift, the user has logged on and clicked on the “System Information”, the “Daily Diary” option. Another window should open for that diary entry. The user should minimize that window or “move” it to the background so that the overall system graphical display is the focus. At that time, the user should see what the overall status of each device is. If there is an uncertain status, the user should select that device and review the status information. For example, if a bank of pop-ups for location 1 is indicating a failed status, the user should double-click on that device and review the status information. The user should also select the CCTV device near that location and view the pop-ups. If necessary, the user should then contact the maintenance personnel to go on-site. Comments concerning the state of the system should then be entered into the daily diary window.

If the system statuses are normal and functioning correctly, the user selects CMS #1 and should review the status window to confirm that the correct message (“Express Lanes Closed”) appears on the sign. This should be done for CMS #2, #3, and #4. The user should also be able to select the CCTV device closest to that device and confirm the message. After confirmation has been completed, the user should select location #1 by clicking on the icon. The user should then select the control option from the menu option and view the valid operations for that location. One of the valid operations should be “Close South 15 Gate”. This should be the single command (operation) to close the gate. The user double-clicks on this operation and the system prompts the user for command action confirmation. After confirmation, the system executes the operation. Each command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

The user then selects the status menu option. Under that window, the user should see a listing of devices. The user should double-click on CMS. At that time, another window should open and display the current status of all the CMS devices. For this opening, the message to be placed on the signs #5-8, is the “Express Lanes Closed” message. That should already be on the signs, as that is the default message.

The user should then select location 2. Again the user should select the control option and should double-click on the valid operation (“Close South 163 Gate”), which should then close the gate. The user double-clicks on this operation and the system prompts the user for confirmation. After confirmation, the system executes the operation. The command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

The next location selected should be location #4. The user should select the control option and should double-click on the valid operation (“Open North 15 Wrong Way”) which should open the wrong way pop-ups at that location. The user double-clicks on this operation and the system prompts the user for confirmation when the confirmation window appears. Again, after confirmation, the system executes the operation. The next operation selected and should be double-clicked upon is (“Open North 15 Draw”), which should illuminate the draw lights. The user double-clicks on this operation and the system prompts the user for confirmation. Again, the command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

Location #5 is the next location. The user should select the control option and should double-click on the valid operation (“Open North 15 Entrance”) which should open the entrance pop-ups at that location. The user double-clicks on this operation and the system prompts the user for confirmation. Again, the command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

If desired, the user could review the status of the CMS signs again. If the status window was left open, the user should review that window. If the window was minimized, the user should maximize it and review the status. Else, the user should select the status menu option and should double-click on CMS. At that time, another window should open and display the current status of all the CMS devices. From the main graphical display, the user should now select CMS #9. The user should select the control option and should double-click on the valid operation (“Open North 15 CMS”). This should be a macro command and should put the correct messages onto the CMS signs #9, #10, #11, and #12. These commands and acknowledgements of successful completion of the operations should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

At this time, the graphical display should show that the starting status of the devices has changed to indicate the new statuses. The graphical display should also indicate the direction of traffic flow for the reversible roadway. The user should be able to view the status of the devices by either using the status option or selecting the Event Log Report and reviewing the operations and acknowledgements received as part of the Southbound opening of the I-15 Reversible Lane Control System.

2.5.2 Typical Opening – Macro Commands

There are several macro commands that should be used for the morning opening. For this example, the user should have at minimum, operator level #2. Like the single command example, the user has logged on and clicked on the “Daily Diary” option. Another window should open for that diary entry. The user should minimize that window or “move” it to the background so that the overall system graphical display is the focus. At that time, the user should see what the overall status of each device is. If there is an uncertain status, the user should select that device and review the status information. For example, if a bank of pop-ups for location 1 is indicating a failed status, the user should double-click on that device and review the status information. The user should also select the CCTV device near that location and view the pop-ups or the system automatically displays a window view the appropriate pop-up bank with the status and nature of the error. If necessary, the user should then contact the maintenance personnel to go on-site. Comments concerning the state of the system should then be entered into the diary window.

If the system status are normally and functioning correctly, the user should select from the desired operation from the control menu option. For this opening, there should be four macro operations executed by the user. Each macro operation should generate a confirmation request window. The first operation selected should be “Close South End 15”. The user double-clicks on this operation and the system prompts the user for confirmation. After confirmation, the system executes the operation. The following operations (commands) should be a part of this sequence:

“Close South End 15 CMS”

The next macro executed should be:

“Close South End 15 Gate”

“Delay minutes number=15”

At this time, the operator selects from the control menu, the next operation to be executed. After confirmation is received, the system should execute the following operations for the macro “Open North End 15”:

“Open North End 15 Wrong Way Pop Ups Transverse Bank=0”

“Delay seconds number=05”

“Open North End 15 Wrong Way Pop Ups Longitudinal Bank=0”

“Open North End 15 Draw Lights”

“Delay minutes number=12”

“Open North End 15 Entrance Pop Ups Transverse”

“Open North End 15 Entrance Pop Ups Longitudinal Bank=0”

“Delay seconds number=10”

The final macro for this opening should be “Open North End 15 CMS”. This operation should be selected and double-clicked upon. After the user receives the confirmation window and accepts the operation, the system should execute the macro.

Confirmation should not be requested for the individual operations. The only confirmation request should be at the actual macro operation. Each command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

At this time, the graphical display should show that the starting statuses of the devices has changed to indicate the new statuses. The user should also be able to view the Event Log Report and review the operations and acknowledgements received as part of the Southbound opening of the I-15 Reversible Lane Control System.

2.5.3 Typical Opening – Super Macro Commands

For this example, the user should have at minimum, operator level #3. Again like the other previous examples, the user has logged on and clicked on the “Daily Diary” option. Another window should open for that diary entry. The user should minimize that window or “move” it to the background so that the overall system graphical display is the focus. At that time, the user should see what the overall status of each device is. If there is an uncertain status, the user should select that device and review the status information. For example, if a bank of pop-ups for location 1 is indicating a failed status, the user should double-click on that device and review the status information. The user should also select the CCTV device near that location and view the pop-ups or the system automatically displays a window view the appropriate pop-up bank with the status and nature of the error. If necessary, the user should then contact the maintenance personnel to go on-site. Comments concerning the state of the system should then be entered into the diary window.

If the system statuses are normally and functioning correctly, the user should select from the desired operation from the control menu option. The operation selected should be “Open North End” or “AM Opening”. The existing system has “Open North End” as a TSU macro, but for the enhanced system, it can be altered to be “AM Opening”. The user double-clicks on this operation and the system prompts the user for confirmation. After confirmation, the system executes the operation. The following operations (commands) should be a part of the super macro.

“Close South End 15 Gate”

“Delay minutes number=1”

“Close South End 163 Gate”

“Delay minutes number=15”

“Open North End 15 Wrong Way Pop Ups Transverse Bank=0”

“Delay seconds number=05”

“Open North End 15 Wrong Way Pop Ups Longitudinal Bank=0”

“Open North End 15 Draw Lights”

“Delay minutes number=12”

“Open North End 15 Entrance Pop Ups Transverse”

“Open North End 15 Entrance Pop Ups Longitudinal Bank=0”

“Delay seconds number=10”

“Open North End 15 CMS”

Confirmation should not be requested for each operation. The only confirmation request should be at the actual operation. Each command and acknowledgement of successful completion of the operation should be logged to the Event Log Report and the Current Command Report. Should the user have the Current Command Summary Report window active, these commands and acknowledgements should also appear in that window. If there should be a problem with the completion of the operation, this should be logged to the above mentioned reports, as well as the Failure Summary Report.

2.6 General Coordination

The TMC operator must know at all times what the current and scheduled activities are for the reversible lane. Besides the opening and closing activities, the operator is also responsible for the safety of individuals on the facility during special events, maintenance, or other activities that require staff or contractors on the facility. The system should assist in this general coordination. The system should provide for a general email or GroupWare that can be used to coordinate with users on the system. Scheduling, meeting calendar, and email with attachment facilities should be integrated into the workstations.

2.7 Support

The support systems should be designed to provide up-to-date information on any of the operating devices in the system.

2.7.1 Simulator

The simulator should operate new devices, test methods of operation (software and/or roadway “scenarios”), and display system status in order to enable hands-on functional experience with new operations before deployment in the field. The simulator should be designed to operate in a full range of conditions found in the field and provide the necessary training regimen.

2.7.2 Documentation

System and component documentation should be complete and in a form that is rapidly accessible to operations personnel. This should be in the form of a users manual, troubleshooting guidelines, standard operating procedures (SOP), GUI screens, system design documents, and other similarly-related documents.

2.7.3 Training

A process of formal and on-the-job training should be implemented to insure that all operations personnel are familiar with all elements of the system. When a new element is connected to the system, formal training should be provided. It is anticipated that the simulator will be used extensively to conduct the level of “hands-on” training desired.

2.8 Coordination with Other Systems

Currently the I-15 Reversible Lane Control System is a stand-alone system with coordination done verbally at the TMC. There will be benefits to the I-15 Reversible Lane Control system if a certain level of coordination is done with the newly developed ATMS and the Congestion Pricing systems. In addition, the ability to easily coordinate with future testbed applications such as the Automated Highway System, or other emerging systems or technologies, should be done. The user interface should also be easily adaptable to the integration of these new systems. Dependent upon the individual application, the coordination ability should be able to be accomplished at either the TSU level, the FCU level, or the DCU level.

The important issue with coordination is how much is appropriate without impairing the capabilities of the I-15 Reversible Lane Control System or operators to perform their duties effectively and safely. The general user guideline for the I-15 Reversible Lane Control Systems Operations is to integrate to the level that maximizes integration of needed information or benefits to other systems without distractions to the TMC Operations during the critical opening and closing operations. These distractions include both operator and any performance degradation to the system that may create a safety or security hazard for the systems operations.

The second guideline is that the I-15 Reversible Lane Control System should not be dependent on any other system or information from that system, for its ability to operate. The level of operations should be, at a minimum, to the current level of operations and that any system the I-15 is coordinating with or integrated with should, in no way, degrade the operations of the I-15 Reversible Lane Control System below the current level of operations. No I-15 Reversible Lane Control System command should be initiated from any other system.

It is envisioned that all external interfaces to the I-15 Reversible Lane Control System should be through a firewall to preserve the isolation of the system from any unwanted intrusion or unintentional commands being generated to the system.

With the assumptions given above the following are the user requirements for coordination with the following known systems:

2.8.1 Advance Traffic Management System (ATMS)

The definitions of the ATMS System for this section includes:

· Ramp Metering System (SDRMS)

· Incident Management System

· ATMS Workstations

The ATMS will provide the I-15 Reversible Lane Control System information for its operation that is currently being processed manually by the TMC operator. This information includes mainline speed, incident information, and CCTV images and control that relate to the I-15 Reversible Lane Control System.

The I-15 Reversible Lane Control System should have access to this information through a data link between the systems. The speed information and incident information should be processed and filtered by the I-15 Reversible Lane Control System to identify and process the needed information into alerts or triggers for the operator to initiate I-15 Reversible Lane Control System functions.

CCTV cameras on the I-15 Reversible Lane Facility should be fully integrated with the ATMS. The CCTV camera images, relating to the I-15 Reversible Lane facility or its operations, should be able to be viewed and controlled by the I-15 Reversible Lane Control System operators. The I-15 Reversible Lane Control System operators should have priority over the control of the CCTV camera images relating to the I-15 Reversible Lane or its operations above all other ATMS functions during the critical opening and closing functions.

2.8.2 Congestion Pricing System

The I-15 Reversible Lane Control System should have the ability to receive information from the Congestion pricing system. This information should include, volume of tagged vehicles currently using the facility, current fees being paid, and the status of the congesting pricing system.

2.8.3 Special Projects

Standard and published interfaces should be provided at all three levels, e.g. TSU, FCU and DCU. This should insure that special projects such as the Automated Highway System, Congestion Pricing, or any future or emerging technologies may be easily integrated into the I-15 Reversible Lane Control System.

In no situation should any special projects system interfere with the normal operations of the I-15 Reversible Lane Control System. This includes integration at any level and in any distraction to the operator or operations, such as degraded performance of the I-15 Reversible Lane Control system to a point of impairing its safety or security.

At the TSU level, an interface should be developed between the I-15 Reversible Lane Control System and the Special Projects system. This interface should provide the status of the facility and field equipment. In addition to status information, other information such as volume, speed, and any incident information that is normally provided for public consumption should be allowed for in the interface.

CCTV images and control should be provided to special projects on a very limited basis. These projects should have the lowest priority over any ATMS or I-15 Reversible Lane Control activity and the control of the cameras should be confined to a limited time frame in which the special projects have pre-scheduled with HOV personnel and ATMS personnel.

At the FCU and DCU level an interface should be developed such that technologies can easily integrated into the system for evaluation. These new technologies should be evaluated with the I-15 simulator prior to any real world test or evaluation.

2.8.4 Other systems

Other systems should interface with the I-15 Reversible Lane Control System through the ATMS system. Other than the special projects, all other systems should use the ATMS system as the primary interface with the I-15 Reversible Lane Control System.

3. Maintenance Operations

Maintenance is responsible for insuring the correct and safe operation of all devices on the I-15 Reversible Lane System at all times. The maintenance includes mechanical devices, electronic system components, and communications. The following sections describe what is essential for the proper maintenance of the Reversible Lane equipment.

3.1 MODES OF OPERATIONS

There are several modes of operations for the I-15 Reversible Lane Control System. These are:

· Opening/Closing

· Emergency

· Non-typical

· Maintenance

3.1.1 Opening/Closing Operations

The maintenance role in the opening or closing of the Reversible Lane system is to provide reconnaissance of the facility to insure the devices are deployed properly and to identify any unusual conditions on the lanes that may affect safety of the facility. The maintenance personnel effectively form an extra layer of sensors to insure the maximum operating safety of the facility.

3.1.1.1 AM/PM Opening

Facility opening has less potential for accidents than closing of the lanes, since no vehicles are operating on the facility. The opening sequence starts with CMS signs displaying “closed” messages, pop-ups deployed, and gates in the up position. Opening involves closing the wrong way gate(s), raising or lowering pop-ups in the appropriate direction of flow, and changing CMS messages in the direction of traffic flow.

The greatest potential for safety problems associated with the opening sequence is unknown objects or vehicles on the roadway and getting the lanes open on time. The “sweep” of the facility is made to insure that the lanes are clear of any object that may interfere with the flow of traffic. The sweep is an important component of the safety inspection of the facility.

3.1.1.2 AM/PM Closing

The lane closure operations inherently have a greater potential for accidents, since vehicles are present on the roadway during changing of the safety devices. It is important to have on-site verification of device operation, as well as verifying the lanes are free of vehicles after closure and before raising the gates. The visual verification of the upstream end of the roadway and the “sweep” operation will continue to be important activities. It is likely that some of the visual verification of device operation should be undertaken via CCTV coverage, particularly at the downstream end of the facility.

3.1.2 Emergency

Emergency conditions involve usage of the facility outside the normal operating times or conditions. Closure of a portion or all of one direction of the mainline lanes, an accident on the Reversible Lanes, or operation of the facility with one or more devices out of operation are examples of abnormality. Maintenance personnel response is a function of the type of emergency operation being performed. The primary responsibility of maintenance in an emergency situation is to insure devices are deployed properly, second, to insure the devices are operating properly, and third, to determine that the facility is operating properly.

3.1.3 Non-Typical

During non-typical operations, the maintenance personnel need to know the precise failure or abnormality in the system, and they must closely coordinate with the TMC operator to resolve the abnormal condition.

3.1.4 Maintenance Functions

Maintenance performs all functions necessary to keep the equipment and devices in good working order. These functions are organized into three main areas:

3.1.4.1 Preventative Maintenance

Preventative maintenance is the routine repairs and checking of equipment to insure better than a minimum defined level of performance. Effective preventive maintenance involves a thorough knowledge of the maintenance history of the equipment and an understanding of its function. The maintenance function should be enhanced if critical information of the equipment were readily available to the field maintenance personnel.

3.1.4.2 Corrective Maintenance

Corrective maintenance is the correction or repair of a device failure that does not affect the safety of the system. The corrective maintenance process involves the notification of the precise problem, the assignment of a priority for repair, access to parts and equipment for the repair, testing, logging of the repair for a repair history, and notification of completion of the repair. These functions should be improved or made more efficient by the new system.

3.1.4.3 Emergency Maintenance

Effective emergency maintenance is dependent upon rapid notification and response to the emergency situation. Close communication with the TMC operator, a quick analysis of the specific problem and effective corrective action is required for emergency situations.

3.2 Coordination

Many of the maintenance functions require a coordinated effort between the system operator and maintenance personnel to effectively complete needed tasks. The system should supply the coordination needed for this work.

3.2.1 Opening/Closing Operations

The maintenance personnel check critical safety devices and observe any unusual activities on the Reversible Lanes. Close communication between system operator and maintenance observer is needed to complete this task.

3.2.2 Emergency Operations

Situations that compromise the safety of the system should be corrected rapidly. Manual operation or repair and testing of the problem devices require close communication between the system operator and repair personnel.

3.2.3 Preventative/Corrective On-Lane Maintenance

Any on-lane maintenance operations should be communicated to the system operator and logged into the system to insure that the maintenance does not interfere with other operations on the lanes and that the safety of the maintenance personnel is not compromised.

3.2.4 Installation of New Devices

New field devices or sensor devices should be integrated into the system without affecting the normal operations of the system. Installation, testing, and integration should involve coordinated efforts of the system operator and maintenance. The system should provide methods of coordination through communications and system logs.

3.2.5 Special Projects or Operations

Special operations on the Reversible Lanes require coordination with Maintenance personnel to insure safety is not compromised. Communications with the TMC and access to activity logs should insure the Maintenance personnel are aware of all activities on the system.

3.3 Reports

Written documentation is very useful in the entire range of maintenance activities on the system, from maintenance histories of devices to daily activities of the Maintenance personnel. Examples of documentation include:

3.3.1 Routine Maintenance

Historical maintenance records are useful in identifying the amount of effort needed to keep each device in good operating condition. This documentation should assist in purchasing components, in the allocation of manpower, the identification of problem components, and budgeting. The system should automatically produce these records.

3.3.2 Failure

Failure reports should identify those components that require excessive repairs or components that may affect the safety of the system. The future system should automatically produce information to monitor system failures to enable allocation of equipment and manpower.

3.3.3 Logistics/Inventory

Inventories of the system components and maintenance equipment should enable improved budgeting and acquisition of supplies and spare parts, and these records should help in the annual budgeting process.

3.3.4 Scheduling

The efficient allocation of Maintenance manpower is important in the effective use of limited resources. The automatic scheduling of routine maintenance should improve the allocation of manpower for all maintenance activities associated with the system.

3.3.5 Incident

Incident Reports record any unusual activities or accidents on the system. This documentation provides a record of the range of events that can occur on the system, and it is valuable in identifying potential corrective measures to the system to reduce incidents.

3.4 USER INTERFACE

The user interface to the system should improve communication between the system operator and maintenance, allow rapid access to historical records and inventories, and record daily maintenance activities. The system should be accessible from all levels of the system TSU, FCU, DCU, and Device.

3.4.1 Access

Access to the system and system records should be simple and fast, so that information can be obtained when and where needed to maintain the system.

3.4.2 Verification

Verification procedures are currently inefficient. Verification of field conditions should be more automatic with better radio communication.

3.4.3 Coordination

Coordination is required between maintenance and the system operator for most functions on the Reversible Lanes system. The coordination mechanism should be precise and require minimal effort to deliver and understand.

3.4.4 Alarms

The user interface should be able to deliver alarms to maintenance personnel precisely, but comprehensively, so that a response can be made quickly with all materials and equipment required to complete the repair.

3.4.5 GUI

The GUI should access data rapidly, and it should be easily used in a range of operating conditions.

3.4.6 Daily Diary

The daily diary should list activities, repairs, equipment used, and hours required for each function on a daily basis.

3.4.7 Security

Access to data in the system should be restricted by an access code. Data restrictions should be programmable.

3.4.8 Workorder Entry

The workorder entry process should improve the scheduling of routine and corrective maintenance to better use the existing manpower, and it will record the effort needed to appropriately maintain each of the system components.

3.4.9 Expert Guidance System

An expert guidance system is a help to facilitate repairs. It should provide a step-by-step process for repair and testing of device components and should contain system schematics.

3.5 Support

The support systems should be designed to provide up-to-date information on any of the operating devices in the system.

3.5.1 Hardware

The System should be upgraded and modernized to include state of the practice hardware and software. It is envisioned that 2070 controllers should be used to replace the current processing in the TSU, FCU and DCU.

3.5.2 Simulator

The simulator should operate new devices or test methods of operation to enable hands-on maintenance experience with new operations before deployment in the field. The simulator should be designed to operate in a full range of conditions found in the field.

3.5.3 Documentation

System and component documentation such as as-builts should be complete, on-line, and in a form that is rapidly accessible to maintenance personnel.

3.5.4 Training

A process of formal and on-the-job training should be implemented to insure that all facility Maintenance personnel are familiar with all elements of the system. When a new element is connected to the system, formal training should be provided.

5. Management

The typical management cycle includes planning, monitoring, and controlling. In addition, management needs to support the operation so that the operations and maintenance can effectively complete the mission set out with the I-15 Reversible Lane Control System. The proactive management of the I-15 Reversible Lane Control System requires timely input of the information identified below. The following is a set of user requirements from the viewpoint of Caltrans Management. Wherever possible, the following information should be generated by the system in the form of reports, or data that can easily be inserted into reports.

The I-15 Reversible Lane Control System provides a benefit to the motoring public during peak hour operations. It provides a “highly visible” facility to the public in advancing Intelligent Vehicle Systems, and provides a testbed for various advance technologies such as the Automated Vehicle Highway System and the Congestion Pricing System. In order to provide appropriate management support for the I-15 Reversible Lane Control System, the following information is essential.

5.1 management INFORMATION

5.1.1 Information On The Safety

Paramount to the operations of the reversible lane is its safety to the public, contractor, Caltrans, or any other Agency personnel. Over the past 10 years of operations no significant safety problem has ever occurred on the facility. This safety record needs to be maintained when the upgraded system is in-place. It is recommended that a safety report should be generated on each incident. This report should include any incident that occurred on the facility that would be deemed a safety hazard to any persons or property and identify any potential safety hazard as a result of any installation, or activity on the facility.

5.1.2 Information On The Facility Benefits

Next to the safety of the public, the identification of benefits to the traveling public is also critical to the management of the system. It is recommended that a summary report should be developed that will include volume and speed information on the facility. This report should include the distinction between the types of users e.g. congestion pricing vehicles and HOV vehicles etc., and that this summary report be provided on a quarterly basis.

5.1.3 Information On The Labor Hours

The other side of the benefit equation is the cost of operating and maintaining the facility. It is recommended that a report to management should identify the hours of labor that is expended on the operations and the maintenance of the facility and that this report be provided on a monthly, quarterly basis.

5.1.4 Information on the Facility Usage

One goal for the I-15 reversible lane facility is provide a testbed for field operational tests for advanced Intelligent Transportation Systems, such as the Automated Highway Systems, Congestion Pricing, and other currently undefined applications. As a measure of benefit, it is recommended that a summary report should be generated on the status of new applications that are being tested using the I-15 reversible lane facility. This report should be generated as a proposal at the beginning of a new application project, monthly during the demonstration, quarterly during the demonstration, and at the conclusion of the demonstration. This report should include a monthly and a quarterly calendar of all activities that are projected for the I-15 Reversible Lane. This report should indicate the benefits that the I-15 Reversible Lane Control System has with the new application, any development time savings, and any potential applications.

5.1.5 Information On Significant Maintenance Issues

To maintain a high level of confidence in the I-15 Reversible Lane Control System, it is important to know the state of the facility. As equipment, air supply system, conduit, electronics etc. need frequent repair, the replacement or difficulty in obtaining replacement parts should be identified. This is a sign of possibly more serious problems that need to be addressed, especially in critical operational areas. It is recommended that a summary report should be developed on the state of the system. This summary report should be updated monthly and provided to management on a monthly and quarterly basis, unless a significant maintenance issue develops, then it should be reported immediately.

5.1.6 Inventory Tracking Of Facility Equipment

One of the products for the I-15 Reversible Lane Control System project was the development of an inventory and bar coding of the all of the field equipment. This can be a valuable management tool for sharing resources with other parts of Caltrans. This would be used to identify spare parts that might be needed in emergency situations and minimize the inventory of spare parts District wide. It is recommended that an inventory list should be reported and changes to this inventory on a semi-annual basis for the I-15 Reversible Lane Control System.

5.1.7 Expansion And Enhancement Plans For The Facility

Enhancements and expansion plans of the I-15 Reversible Lane Control System will be important management information. As needs and technology changes, it will be important that the Control System be keep current with emerging technology and meet the changing needs in the area. It is recommended that an enhancement and expansion plan should be provided on an annual basis. This report should include any new and emerging technology, applications for the facility, coordination with emerging projects that may be affected by the I-15 Reversible Lane Control System, and projects that affect the I-15 Reversible Lane Control System.

5.2 MANAGEMENT ACTIVITIES

There are several management activities that are necessary for the I-15 Reversible Lane Control System. These activities are for the support of the operations and the maintenance of the system.

5.2.1 Labor Resources

It is recommended that management support the operations and maintenance by providing for well-trained personnel in key backup positions in the area of Operations and Maintenance. It is important that key personnel that are required for the opening and closing be fresh and alert for these critical events.

5.2.2 Facilities & Equipment

Dedicated and improvements in facilities and test equipment needed for the training, simulators, testing, and troubleshooting will be important for the upgraded system. This will be important as closer coordination with other systems is mandated. As these other systems become dependent on the I-15 Reversible Lane Control System, then adequate facilities and equipment will be important to its operations and will need to have full management support.

5.2.3 Training

Training will be extremely critical for the upgraded system. As systems, like the Reversible Lane Control System and other Advanced Intelligent Transportation Systems come on-line, the training in cross disciplines from traditional Civil and Electrical into Electronics, Communications, and Systems Engineering will be essential to the well-being of any electronic based system. It is recommended that management support training in these areas to ensure that the quality of Maintenance and Operations personnel keep pace with the evolution of the system.

5.2.4 Growth Path For Personnel

In addition to the training, it is recommended that management support an organizational growth path for the operations and maintenance of the I-15 Reversible Lane Control System. Training good personnel is necessary but not sufficient. It is also imperative that an organizational growth path be supported for disciplines that are not in a traditional growth path within Caltrans and that this growth path is on par with the traditional growth paths within the organization of Caltrans.

5.2.5 Promotion Of The Facility

The I-15 Reversible Lane Control System provides a National Resource for the advancement of the Intelligent Transportation Systems. This has been demonstrated with the Automated Highway System demonstration and with the Congestion Pricing System currently underway. As the interest for the I-15 Reversible Lane facility increases, new opportunities for the facility will grow. It is important that the management recognize this importance and provide support in the promotion of the facility and support the promotion of additional facilities as needed throughout the state.

5.2.6 Expansion And Enhancement Budget Planning

It is recommended that management support an expansion and enhancement budget on an annual basis for upgrading the facility. This facility should be viewed as a living testbed. Looking for new opportunities for the testbed means that the testbed has to be flexible and quickly adaptable to new innovations in the advancement of Intelligent Transportation Systems technologies. The I-15 Reversible Lane Control System can provide a catalyst in the evolution of the ITS technology growth.