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

·<