2. TRAFFIC SIGNAL EQUIPMENT

9 ITEM 9. MASTER CONTROLLER

9.1 GENERAL

9.1.1 The master controller shall control and supervise a group of local controllers and provide the communication link between the local controllers and a central computer system.

9.1.2 The on-street master controller shall provide:

Traffic plan selection by time-of-day or traffic responsive
Crossing arterial synchronization
Diagnostics
Events
Logs
Reports
Data Entry

9.2 ENVIRONMENTAL STANDARDS

9.2.1 The master controller unit shall meet or exceed the applicable sections and clauses of NEMA Standards Publication No. TS 2-1992, with respect to the following:

Operating Voltage
Operating Frequency
Power Interruption
Temperature and Humidity
Transients, Power Service
Transients, Input-Output Terminals
Non-destruct Transient Immunity
Vibration and Shock

9.3 HOUSING AND COMPONENTS

9.3.1 The master controller shall be a shelf-mounted unit of modular design. The chassis shall be designed for easy access during maintenance, allowing for ease of testing without requiring disassembly or extender boards. All fuses, connectors, and controls shall be accessible from the front of the controller unit.

9.3.2 Display: A liquid crystal display (LCD) shall be provided on the front panel of the master controller to display programming and operational status information. The display shall be clearly readable in both bright sunlight and total darkness. It shall contain a minimum of 4 lines with 40 alphanumeric characters per line.

9.3.3 Operating Display: The display shall have two modes of operation, dynamic and program. The dynamic mode shall display operational status information, while the programming mode shall display user-programming information.

9.3.4 Keyboard: A single keyboard shall be provided on the front of the intersection controller. The keyboard shall be used to enter all user-programmable data, as well as vehicle, pedestrian, and preemptor calls during test. The function of each key shall be clearly shown.

9.3.5 Capacity: The master controller shall have the following minimum capacities:

2 groups
32 total intersections
64 system detectors
48 timing patterns (Cycle, Split, Offset combinations)

9.4 SYSTEM CONTROL

9.4.1 The master controller shall be capable of operating in the following modes:

Manual control
Remote (external control)
Time-based control
Traffic responsive control

9.4.2 Manual Control: The master shall be capable of being set manually to any cycle, split, offset pattern through an entry on the keyboard or through system software. Manual control shall override time-based or traffic responsive control.

9.4.3 Remote Control: The master controller shall be capable of being set to operate in any cycle/split /offset combination based on external inputs from the external interface. Remote control commands shall override time-based coordination and traffic responsive programs.

9.4.4 Time-Based Control: Time-based control shall provide for pattern selection based on time-of-day, day-of-week, and week -of-year with automatic adjustment for daylight savings time and leap year.

9.4.4.1 Time-based control shall provide a minimum of 180 events. An event shall consist of:

A pattern (C,S,O) or Free and time-of-day, or
An auxiliary event consisting of a special function output, sample interval time, log interval time and time-of-day, or
A time-of-year event consisting of a special day and/or special week plus the date of occurrence (year, month and month day).

9.4.4.2 It shall be possible to define a minimum of 99 program days and it shall be possible to equate and to copy program days.

9.4.4.3 It shall be possible to call the following based on time-of-day:

Flashing
Free operation
Standby
Traffic responsive
Traffic responsive override enable

9.4.5 Clock Calendar: The time based control shall provide a 99 year calendar (including accounting for the transition into the new millennium) for automatically determining the current day of week, day of month, month of year, and year based on the data set as the starting point. The calendar shall provide for automatic adjustment for leap years.

9.4.6 Daylight Savings Time: Time based control shall provide for automatic adjustment for Daylight Savings Time on user specified month and week.

9.4.6.1 Traffic Responsive Control: In traffic responsive control, pattern selection by the on-street master controller shall be in response to dynamic traffic conditions as measured by the system detectors.

9.4.6.2 The master controller derives a set of system pattern commands from volume and occupancy data from system detectors. Threshold values used to determine pattern selection shall be provided with hysteresis decision points to prevent oscillation. There shall be a user selectable minimum time between pattern changes.

9.5 OTHER CONTROL

9.5.1 Mode of Operation: It shall be possible for the operator to select the following mode of operation for a group under control of the master.

Intersection Flash
Standby Operation (Under control of the local controller, but monitored by the master controller.)
Free

9.5.2 Crossing Artery Control: The master shall have the capability to provide for coordinated traffic flow when two groups cross at a common intersection.

9.6 SYSTEM DETECTOR DATA

9.6.1 Each system detector input shall be capable of selective weighting. System detector data shall be smoothed or filtered on a moving basis, using a user programmable time.

9.6.2 Pattern Selection Routines: Pattern selection shall be based on analysis of sampling detector volume and occupancy data by the master controller. Up to eight system detectors may be assigned to a computational channel. Detectors may be assigned to multiple channels.

9.6.2.1 The master controller shall provide routines for the following minimum pattern selections:

Free or coordinated operation
Cycle (Four cycles)
Directionality of offset selection (In, out, or average)
Split Selection
Special plan selection based on detector occupancy only

9.7 MODEMS

9.7.1 Internal Modem: The master controller shall be provided with an internal communication modem and interface equipment which will enable transmission of all required commands and data to the local controllers.

9.7.1.1 Operational indications shall be available on the front panel of the master controller to indicate when a carrier signal is being received, valid data is being received, and when the unit is transmitting.

9.7.2 External Modem: An external auto/dial answer modem with modem cable shall be provided with each master controller ordered under this contract.

9.7.2.1 The modem shall automatically answer calls from the central computer and transmit data to the central office computer via standard voice grade telephone lines. The modem shall be a Hayes Smart modem 1200 or EQUAL. Configuration settings shall be set by DIP switches, or must be duplicated in non-volatile memory.

9.8 SYSTEM DIAGNOSTICS

9.8.1 The master shall perform diagnostics on system detectors, communications, and intersection operation and shall maintain a history of all failures.

9.8.2 Each system detector shall be monitored for absence of calls, constant occupancy, and erratic operation. If a detector fails , it shall be automatically disconnected from the assigned channel and calculations.

9.8.3 Improper or insufficient detector data needed for automatic traffic responsive pattern selection shall cause the master to go to time-based coordination mode.

9.8.4 The following intersection status conditions shall be available for display:

Intersection status
Controller Unit status
Coordination timing status
preemption timing status
Phase and detector status

9.9 COMMUNICATION ALARMS

9.9.1 The master controller shall have the ability to record the time and data , local intersection address, and the failure mode of the communications interface.

9.10 CRITICAL ALARMS

9.10.1 Critical alarms shall be user-definable. The defined critical alarms are monitored by the master controller and the occurrence of any critical alarms is logged. The master controller shall be capable of dialing up the central computer on identification of any critical; alarm.

9.11 HISTORIC REPORTS

9.11.1 The master controller shall be capable of generating a report of traffic pattern changes by group, containing the following information:

Beginning time and date
Group Number
Pattern selected

9.11.2 The master shall be capable of generating a report of the data base used to determine the traffic responsive system program.

9.12 METHOD OF MEASUREMENT

Master Controllers shall be measured for payment by the number of units each, complete with all components provided as specified herein and delivered to the Department.

9.13 BASIS OF PAYMENT

Master Controllers will be paid for at the contract unit price each, which will be payment in full for furnishing a complete Master Controller as specified herein and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.

10 ITEM 10. MASTER CONTROLLER SYSTEM SOFTWARE

10.1 GENERAL

10.1.1 The central computer system shall be a traffic management program for hard-disk supported IBM personal computers and compatibles. The central office software shall receive system and intersection data from the on-street master controller and shall tabulate format, and output reports and alarms at the central office e site.

10.2 OPERATOR INTERFACE

10.2.1 The software shall use a color monitor and extensive menu formats to provide ease of use and convenient system access. The menus provide a listing of appropriate selections, ending in a prompt for a response.

10.2.2 Actual data entry and editing are performed using a form filling technique. Prompting in traffic engineering language and highlighted entry fields allow an operator untrained in computer operations to successfully use the program.

10.3 COMMUNICATION INTERFACE

10.3.1 The software shall be capable of receiving and transmitting data over dedicated or dial-up telephone lines. Capability for communicating via coax/RF networks shall be possible by use of optional RF modems.

10.3.2 Over dial-up lines, the software shall be capable of accessing from 1 to 256 on-street master controllers.

10.3.3 Where local controllers exist that are not part of an on-street system, access capability over dial-up lines shall be provided for 1 to 8192 local controllers.

10.4 MASTER CONTROLLER MONITORING

10.4.1 The software shall be capable of tabulating, formatting, and outputting real time data as obtained by or available at on-street master controllers. At a minimum, the following data is required:

Group Active Status - The central office operator may view the current operating mode data for both groups.
Intersection And Detector Status - The central office operator may view the current status of all intersections and system detectors.
Master Controller Time Base Status - The central office operator may view the current status of the master time base functions.
Traffic Responsive - The central office operator may view the current status of the master traffic responsive computational channel outputs and the pattern select inputs plus outputs.
Local Coordinated Greens - The central office operator may view the current status of the coordinated green for the running pattern at all local controllers.

10.5 LOCAL CONTROLLER MONITORING

10.5.1 The software shall be capable of tabulating, formatting, and outputting real time data as obtained by or available at local intersection controllers. At a minimum, the following data is required:

10.5.2 Intersection Status - Current status of the intersection signals, detectors, and mode. The intersection status (graphic) display shall provide for up to eight vehicle phases, eight pedestrian phases, and four overlaps on numerous background (crossing, tee, etc). Red, Yellow, Green, and phase detector indications are identified by the phase number. The text portion of the display presents data relevant to the operation of the intersection.

Controller Unit Status - Current status of the controller ring timers and phase states.
Coordination Status - Current status of the controller coordination timers and states.
Preemption Status - Current status of the controller preemption timers and states.
Local Time Base Status - Current status of the local time base function.
Detector Status - Current status of the phase and special detectors as determined by the local detector diagnostics.

10.6 MASTER CONTROLLER ADMINISTRATION

10.6.1 The software shall be capable of tabulating, formatting, outputting, and editing parameter data as available on disk or obtained from on-street masters. At a minimum, the following functions are required:

View/edit disk resident data
Upload data from a master controller
1. View/edit uploaded data
2. Save uploaded data to same master
3. Save uploaded data to another master
4. Compare upload data to disk data
Download disk data to a master
Print disk resident data
Copy disk resident data

10.6.2 In this mode of operation the central-office micro-computer acts as a data terminal interfacing with the on-street master controller data entry routines. In effect, the central-office operator shall be capable of performing functions normally performed at the on-street master's keypad. The operator may request specific data be displayed on the screen, modify that data, and then send it back to be entered into the on-street master.

10.6.3 The configuration data for each on-street master controller in the system is maintained on a disk file. The operator may create or modify the files using English language prompts with help and error validation.

10.6.4 It shall be possible to transfer the configuration data from and to the on-street masters.

10.6.5 The data transferred from the on-street master controller may be displayed in the same manner provided (tabular) for file manipulation, saved to the same or another master, or it may be compared with the configuration data on the disk file. The uploaded data can be stored (saved) in a disk file as the masters configuration, or disregarded.

10.7 LOCAL CONTROLLER ADMINISTRATION

10.7.1 The software shall be capable of tabulating, formatting, outputting, and editing parameter data as available on disk or obtained from local intersection controllers.

Enter local data and store on disk
Upload data from a master
1. View/edit uploaded data
2. Save uploaded data to same master controller
3. Save uploaded data to another master controller
4. Compare upload data to disk data
Download disk data to a master
Print disk resident data
Copy disk resident data

10.7.2 In this mode of operation the central-office micro-computer acts as a data terminal interfacing with the local controller unit data entry routines. In effect, the central-office operator shall be capable of performing functions normally performed at the local controller unit's keypad. The operator may request specific data be displayed on the screen, modify that data, and then send it back to be entered into the local controller unit.

10.8 MASTER CONTROLLER REPORTS

10.8.1 The software shall be capable of tabulating, formatting, and outputting report data as obtained by on-street master controllers. Such data shall be obtainable on demand or automatically output on a time-of-day basis specified by the user. The on demand reports are output via hard copy or on the CRT (as selected by the user) and can be saved on disk.

10.8.2 The automatic (Time-Of-Day) reporting is output via hard copy or saved on disk.

10.8.3 The reporting operation provided allows the on-street master to auto-dial the central-office facility to transfer critical events as they occur.

10.8.4 The central-office micro-computer receives master report data from the on-street master and tabulates, formats, and outputs the reports noted below. The operator may view, print or save to disk the following:

System Critical Alarms - The log shall include date, time, place, and mode of local and/or on-street master controller critical alarm.
Master Alarms - Master controller alarm history. The log shall include date, time, place, and mode of on-street master alarm.
Communications Failures - The log shall include date, time, place, and mode of on-street master communications failure.
Group Pattern Changes - The log shall include date, time, place, and mode of on-street master group pattern change.
Traffic Responsive Pattern Changes - The log shall include date, time, place, and mode of on-street master traffic responsive pattern change.
System Detector Logs - The log shall include date, time, and values of each detector input to each channel.
Off-line/Online History - The log shall include date, time, and intersection along with the appropriate transition.

10.9 LOCAL CONTROLLER REPORTS

10.9.1 The software shall be capable of tabulating, formatting, and outputting report data as obtained by local intersection controllers. Such data are obtainable on demand or automatically output on a Time-Of-Day basis specified by the user. The on demand reports are output via hard copy or on the CRT (as selected by the user) and can be saved on disk. The automatic (Time-Of-Day) reporting is output via hard copy or saved on disk.

10.9.2 The central-office micro-computer receives local report data from the local intersection controller and tabulates, formats, and outputs the reports noted below. The operator may view, print or save to disk the following:

Local Alarms - The log shall include date, time, place, and mode of local intersection alarm.
Measurements Of Effectiveness (MOEs) - The log shall include date, time, and values of volume, stops, delay, and utilization.
Communications Failures - The log shall include date, time, place, and mode of local intersection communications failure.
Detector Failures - The log shall include date, time, place, and mode of local intersection detector failure.
System Detector Logs - The log shall include date, time, and values of each detector input.

10.10 SOFTWARE UPDATES

All software changes and updates applicable to the equipment furnished under this contract shall be provided to the Department at no charge for a period of three (3) years.

10.11 METHOD OF MEASUREMENT

Master Controller System Software shall be measured as a Lump Sum. This measurement shall include all development, encoding, compiling, and requirements as specified herein.

10.12 BASIS OF PAYMENT

Master Controller System Software shall be paid for at the contract unit price Lump Sum as measured above, which price shall be payment in full for furnishing a complete Master Controller System Software full functional, free of all defects; and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.

11 ITEM 11. NEMA TS2 CONTROLLER - TYPE A1, Salt Lake Valley Region

11.1 INTRODUCTION

11.1.1 This specification sets forth the minimum requirements for a shelf-mountable, multi-phase, fully-actuated, digital, solid-state traffic controller. The controller shall meet, as a minimum, all applicable sections of the NEMA Standards Publication No. TS2-1992. Where differences occur, this specification shall govern. Controller versions shall be available to comply with NEMA TS2 Type 1 standards.

Note: Throughout this specification the term system master is used. This term can apply to either a vendor supplied on-street master with a pc interface, or a central computer running software supplied by others.

11.2 HARDWARE

11.3 ENCLOSURE

11.3.1 The controller shall be compact so as to fit in limited cabinet space. It shall be installable on a shelf that is not more than 7" deep. External dimensions shall not be larger than 10" x 16" x 9 " (H x W x D).

11.3.2 The enclosure shall be constructed of sheet metal and shall be finished with an attractive and durable protective coating.

11.3.3 The controller unit shall be of modular design. The chassis shall be metal and shall be designed for easy access during maintenance, allowing for ease of testing without requiring disassembly or extender boards.

11.4 ELECTRONICS

11.4.1 A microprocessor shall be used for all timing and control functions. Continuing operation of the microprocessor shall be verified by an independent monitor circuit, which shall set an output to FALSE and indicate an error message if a pulse is not received from the microprocessor within a defined period.

11.4.2 Sockets shall only be used for components with 20 pins or more.

11.4.3 A built-in, high-efficiency power supply shall generate all required internal voltages. All voltages shall be regulated and shall be monitored with control signals. All fuses, connectors and controls shall be mounted on the front of the controller unit.

11.4.4 Timing of the controller shall be derived from the 120 VAC power line. A 10-year lithium battery shall maintain the time-of-day clock and digital data during a power outage lasting up to 30 days. Lead-acid, nickel-cadmium, or alkaline batteries shall not be acceptable.

11.4.5 All printed circuit boards shall meet the requirements of the NEMA Standard plus the following requirements to enhance reliability:

All plated-through holes and exposed circuit traces shall be plated with solder.
Both sides of the printed circuit board shall be covered with a solder mask material.
The circuit reference designation for all components and the polarity of all capacitors and diodes shall be clearly marked adjacent to the component. Pin 1 for all integrated circuit packages shall be designated on all printed circuit boards.
All electrical mating surfaces shall be gold-plated.

11.5 FRONT PANEL & CONNECTORS

11.5.1 The front of the controller shall consist of a panel for the display and keyboard plus a separate panel for the connectors.

11.5.2 An 8-line by 40-character/line alphanumeric liquid crystal display (LCD) shall show program and status information. The display area shall have nominal measurements of 1 1/2" x 5 1/4" (H x W) or larger. For ease of viewing, backlighting and multiple levels of contrast adjustment shall be provided.

11.5.3 Front-panel operator inputs shall be via clearly labeled and environmentally-sealed keys. These shall include a 12 position (0-9, plus * and #) telephone-type keypad, four-arrow cursor control keys plus four additional keys (E, F, + and -).

11.5.4 All interface connectors shall be accessible from the front of the controller.

11.5.5 The Port 3 connector shall be mounted on the front of the CU and shall be an RS-232C Data Terminal Equipment (DTE) interface for interconnecting the CU to the system master.

11.5.6 The Port 3 connector shall be a 9 pin metal shell “D” subminiature type connector. The connector shall utilize male contacts and shall be equipped with latching blocks.

11.5.7 The CU shall be furnished with a Port 4 which shall be an RS232C Date Terminal Equipment (DTE) interface for communicating with auxiliary equipment in the cabinet assembly.

11.5.8 The port 4 connector shall be a 9 pin metal shell “D” subminiature type connector. The Connector shall utilize male contacts and shall be equipped with latching springs.

11.6 SERVICEABILITY

11.6.1 All electronic modules other than the power supply shall be easily removable from the front of the controller using a standard screwdriver as the only tool. All power and signal connections to the circuit boards shall be via plug-in connectors.

11.6.2 The controller layout shall allow the removal and replacement of any circuit board without unplugging or removing other circuit boards. No more than two boards shall be attached together to form a circuit assembly. Attaching hardware shall use captive screws or 1/4-turn fasteners to secure circuit assemblies to the enclosure.

11.6.3 The controller enclosure shall allow complete disassembly using a standard screwdriver. It shall be designed so that one side of any circuit board is accessible for troubleshooting and testing while the controller is still in operation. This capability shall be accomplished without the use of extender cards or card pullers.

11.7 OPERATING DISPLAYS

11.7.1 The dynamic displays listed below shall be provided to show the operational status of the controller. Additional displays shall be offered for programming.

11.7.2 An intersection status display shall indicate the active status of all signal driver outputs and vehicle plus pedestrian calls. When this display is active, vehicle and/or pedestrian calls may be placed from the keyboard.

11.7.3 An active timer display shall show a summary of ring, phase, coordination, preemption and time-based control status. The menu shall provide for the selection of any combination of the rings for display (R1 + R2, R3 + R4, R1 + R3, etc.).

11.7.4 This status display shall indicate current interval, pedestrian, density, maximum, and maximum extension timing by phase and ring. The status of vehicle and pedestrian phases shall be displayed in combination with vehicle and pedestrian calls. Operational modes shall also be displayed e.g. Time Base, Interconnected, System, Backup, Manual, System Flash, Start Flash, Stoptime, Preempt, Priority, TS2 Diagnostic Flash, etc.

11.7.5 When this display is active vehicle and/or pedestrian calls may be placed from the keyboard.

11.7.6 A coordination timers display shall allow viewing of the real time status of coordination timer(s) and parameters for the active pattern. Indicate the command source, current pattern information, local/system cycle count, offset mode, offset correction, time-based control status, coordinated mode, max mode, force-off mode, phase pattern & mode and permitted phase & control data.

11.7.7 A preempt timers display shall indicate preemption (railroad, fire, emergency, bus) and priority status. When a preemptor is active, the display shall also indicate preemptor interval and timer countdown as well as priority lockout and max call time out.

11.7.8 A time base status display shall indicate the current time and date, the current day and week program, the active programmed selections of the coordination pattern and auxiliary functions.

11.7.9 A comm status display shall indicate the current status of communications on Port 2 (RS232 connector), Port 3 (systems interface connector) and Port 4 (equipment interface connector). The display shall include the settings (speed, data bits, parity and stop bits) programmed for each port.

11.7.10 A detector status display shall indicate the current status for up to 64 detectors. The display shall show the status as determined by the detector diagnostics capability of the controller. The condition will be reported as one of the following states: on-line, failed open loop, failed shorted loop, failed excessive inductance change, failed max presence diagnostic, failed no activity diagnostic, failed erratic counts diagnostic, BIU frame fault, not supported or "LWD" (not TS2 detector, detector failure or detector watchdog timeout).

11.7.11 The detector activity display shall show the current cumulative volume and occupancy values for the system detectors connected to the CU. These values shall be updated in real-time, and shall reset to zero after the information has been uploaded to the central computer or master.

11.7.12 The detector activity display shall also provide the average speed for all speed traps connected to the CU. The value displayed shall be the average speed during the sample period and shall be updated in real-time. The display shall reset to zero after the information has been uploaded to the central computer or master.

11.8 PROGRAMMING

11.8.1 PROGRAMMING DISPLAYS

11.8.1.1 All programming parameters shall be accessible and capable of being programmed through the front-panel keyboard. Programming displays in the form of menus shall aid the operator in entering data from the front-panel keyboard.

11.8.1.2 A main menu shall allow the user to select a major function of the controller. A sub-menu shall then be displayed to allow the user to select a sub-function within the major function. Cursor keys shall allow the user to scroll through all menus and sub-menus.

11.8.1.3 English language and traffic engineering terminology shall be used throughout to facilitate programming. The display organization shall allow traffic personnel to program the controller without using reference cards or manuals.

11.8.1.4 Programming entries shall consist of alpha or numerical values. During program entry, the new data shall be displayed as it is entered. Values shall only be validated and stored when entered by the user.

11.8.2 PROGRAMMING METHODS

11.8.2.1 The methods listed below shall be available for controller programming. It shall be possible to program all CU parameters through each of the following methods. The manufacturer shall be able to provide as off-the-shelf items all of the firmware and software required to effect the listed programming methods and to implement network operation with system masters and host PC's.

a. Manual data entry via the front panel keyboard

b. Data downloading, through the system interface, via telemetry from a system master.

c. Data downloading from a portable PC-compatible computer, through the port 2 connector, via null-modem cable.

d. Data downloading from a PC-compatible computer, through the Port 2 connector, via modem.

e. Data downloading from one controller to another using a Port 2 on each controller.

11.8.3 PROGRAMMING SECURITY

11.8.3.1 The controller unit shall prevent the alteration of keypad set unit variables prior to the user having entered a specific code. No access code shall be required to display data. Access codes shall initially be set at "0000" and shall be definable by the user. The controller shall allow entry of a code of to prevent access from being turned off.

11.8.4 PROGRAMMING UTILITY FUNCTIONS

11.8.4.1 A copy function shall permit copying all timing data from one phase to another. It shall also permit copying all coordination pattern data from one pattern to another. This feature will facilitate data entry when programming any two or more phases with the same timing values and/or two or more coordination patterns with the same pattern data.

11.8.4.2 The controller unit shall contain a backup data base stored in nonvolatile memory. A copy function shall permit transferring the backup data base to the active data base. An alternate data base for interchange control operation shall be selectable from the keyboard.

11.8.4.3 A print function shall allow the printing of controller unit data and detector count, detector failure, and event logs. The controller shall be capable of interfacing with any printer with an RS-232 interface and capable of a minimum width of 80 columns. The communication rate shall be 1200 bps minimum.

11.8.4.4 A sign-on message shall allow the user to view the controller software version number. This message shall be displayed upon power-up until a key is depressed.

11.9 ACTUATED CONTROL FUNCTIONS

The controller shall provide all actuated control functions and operations required by the NEMA TS2 Standard. In addition, it shall provide the features described in the following paragraphs.

11.9.1 PHASE SEQUENCE

11.9.1.1 The phase sequence of the controller shall be programmable in any combination of sixteen phases, eight concurrent groups and four timing rings.

11.9.1.2 Phase sequence information shall be changeable from the keyboard and stored in EEPROM data memory.

11.9.1.3 The standard phase sequence of the controller shall also be capable of being altered by coordination, time-of-day or external alternate sequence command. The alternate sequence commands shall allow reversing the normal phase sequence of each phase pair as shown below:

a. Command A reverses phases 1 and 2.

b. Command B reverses phases 3 and 4.

c. Command C reverses phases 5 and 6.

d. Command D reverses phases 7 and 8.

e. Command E reverses phases 9 and 10.

f. Command F reverses phases 11 and 12.

11.9.2 TIMING INTERVALS

11.9.2.1 Timing intervals shall be programmable from 0-99 in one second increments, 0-999 in one second increments or from 0-9.9 in one-tenth second increments, depending on the function.

11.9.2.2 Guaranteed minimum interval values of 3.0 seconds shall be set for all yellow clearance timings (normal and preempt routines).

11.9.2.3 Cars before reduction shall provide a user-specified number of actuations, or cars waiting, that must occur before starting gap reduction. Gap reduction shall be initiated by either time before reduction or cars before reduction, whichever reaches its maximum value first.

11.9.2.4 During non-coordinated operation the controller shall be capable of dynamically extending the maximum green time for each phase based on vehicle demand. Up to three dynamic maximum green intervals shall be selectable per phase based on time-of-day. The initial interval shall be selectable as either Max 1 or Max 2. If the phase terminates due to max-out for two successive cycles, then the maximum green time in effect shall automatically be extended by one dynamic step interval on each successive cycle until it is equal to the dynamic Max value. If the phase gaps out for two successive cycles, then the maximum green time shall be reduced by one dynamic step interval until such subtraction would mean the adaptive max was less than the smaller of the normal max or the dynamic max. value.

11.9.2.5 During coordinated operation, the controller unit shall be capable of dynamically adjusting the phase splits (Critical Intersection Control). This dynamic adjustment shall be performed such that the offset and cycle length of the current timing plan are preserved, and phase minimums are not violated.

11.9.2.6 Critical Intersection Control shall only be performed by the CU if that function has been enabled by the system master for the controller unit and timing plan in use.

11.9.2.7 Prior to initiating Critical Intersection Control, the CU shall verify that all required detectors are functioning properly, and that volume conditions at the intersection are such that CIC can provide a benefit to the traffic flow.

11.9.2.8 When CIC is enabled, all of the necessary detectors are functioning, and the proper traffic flow conditions are met, CIC shall dynamically adjust the vehicular phase splits on a cycle-by-cycle basis based on the demand for each phase. Phase demand shall be based on smoothed volume and occupancy data collected by the system detectors. Exclusive pedestrian phases shall be excluded from the calculations.

11.9.2.9 The calculation of phase splits shall be performed in the following manner:

First, the total computed green demand and cycle length are reduced by the amount of time necessary to satisfy all phase minimum durations specified for the timing plan.

Second, the remaining green time is allocated based on the percentage of green demand for each phase versus the total green demand.

Any remaining time (due to round off errors) is divided equally among the phases according to the phase length in descending order.

11.9.2.10 The calculation of green demand for each phase shall be computed based on the following equation:

D=R(A1*O+A2*V+A3*O*V) where

D=computed green demand

R=vehicle release rate (user specified between 0-5)

A1= CIC coefficient 1 (user specified between 0-5)

A2= CIC coefficient 2 (user specified between 0-5)

A3= CIC coefficient 3 (user specified between 0-5)

O= smoothed occupancy

V= smoothed volume

11.9.3 OVERLAPS

11.9.3.1 The controller shall provide eight internally-generated overlaps (A,B,C,D, E, F, G and H). These shall be individually programmable as standard or protected/permissive. The green, yellow and red intervals shall be individually programmable following termination of the parent phase.

11.9.3.2 Overlap functions shall be programmable from the controller keyboard.

11.9.4 CONDITIONAL SERVICE

11.9.4.1 The controller shall provide a programmable conditional service feature. When selected, the controller shall service an odd-numbered phase once normal service to that phase has been completed and enough time for additional service exists on the concurrent even phase.

11.9.5 ADDITIONAL FEATURES

11.9.5.1 The following features shall be programmable for each phase:

Phase in use

Locking/non-locking detector memory

Vehicle recall

Pedestrian recall

Maximum recall

Soft recall

11.9.5.2 Soft recall shall return the controller to the programmed phase in the absence of other calls.

11.9.5.3 The controller shall permit power-up start and external start to be individually programmed by phase and interval. Start intervals shall be green, yellow or red.

11.9.5.4 During a power-up start condition, the controller shall be capable of timing an all-red or flash interval before the power-up start phase(s) and interval are displayed.

11.9.5.5 The controller shall provide last-car passage operation on a per phase basis. When selected, this feature shall provide a full passage (vehicle extension) interval when a phase gaps out with a gap in effect less than the vehicle extension interval (preset gap).

11.9.5.6 The controller shall provide both single and dual entry operation. When selected, dual entry shall cause the controller to ensure that one phase is timing in each ring.

11.9.5.7 It shall be possible via keyboard selection to inhibit the service of a phase with other phase(s) within the same concurrent group.

11.9.5.8 The controller shall provide the following additional selectable pedestrian functions:

a. Actuated phase rest in WALK.

b. Flashing WALK output.

c. Pedestrian clearance protection during manual control.

d. Pedestrian clearance through yellow.

11.9.5.9 The controller shall provide a programmable simultaneous gap termination feature. When programmed, phases in both rings shall gap out together in order to terminate the green interval and cross the barrier.

11.9.5.10 The controller shall provide control of five-section, protected/permissive left turn heads. When selected, this feature shall cause the through (even) phase yellow to inhibit display of the left turn (odd) phase yellow.

11.9.5.11 The controller shall provide automatic flash selection per the requirements of the MUTCD. Both the flash entrance and exit phases shall be programmable through the keyboard, and flashing shall be controlled by either setting the fault/voltage monitor output to be FALSE or by flashing through the load switch driver outputs. Automatic flash shall be selectable by external input, system command, or time of day.

11.9.5.12 The controller shall provide dimming for selectable load switch outputs. Dimming shall be accomplished by inhibiting the selected outputs for alternate half cycles of the 120 VAC line. Dimming shall be controllable by time of day and an external input. Programming shall permit individual dimming of the Green/Walk, Yellow/Ped Clear, Red/Don't Walk outputs for each load switch.

11.10 COORDINATION

Coordination functions to control intersection cycle lengths, system offset relationships, and phase split percentages shall be provided as a standard feature, with no need for additional modules or software.

11.10.1 COORDINATION MODES

11.10.1.1 Permissive Mode - The coord phase(s) shall operate as non-actuated when coordinated. The coordinator shall provide for a controlled release (permissive period) from the coord phase(s) to each of the remaining phases in sequence. When a call is not present for the phase to be serviced next in sequence, the coordinator shall re-allocate that phase’s time to the end of the coord phase.

11.10.1.2 The first part of each permissive period shall consist of a vehicle permissive period. The length of the period shall be determined by the phase split and the vehicle minimum service time.

11.10.1.3 The second part of each permissive period shall consist of a pedestrian permissive concurrent with the vehicle permissive. The length of this period shall be determined by the phase split and the pedestrian minimum service time.

11.10.1.4 Prior to the beginning of the first permissive period, the coord phase pedestrian shall display the ped clear indication and dwell “Don’t Walk. This will expand each subsequent phase permissive due to the absence of coord phase ped clear time in each. The coord phase pedestrian shall dwell Don’t Walk until such time as the coord phase terminates and returns to green or the last permissive period in the cycle is complete without the coord phase terminating.

11.10.1.5 Yield Mode - The coord phases(s) shall operate as non-actuated when coordinated. The coordinator shall provide for a single release from the coord phases(s) to the remaining phases in sequence.

11.10.1.6 Permissive Yield Mode - The operation shall be similar to Permissive Mode above with the following exceptions:

The coord phase pedestrian shall be actuated.

Immediately prior to the first permissive, the coordinator will provide a variable period for the coord phase extension (Permissive Yield Point).

The amount of coord phase extension shall be distributed proportionally .

11.10.1.7 Permissive Omit Mode - The operation shall be equal to Permissive Yield Mode above except that once the coord phase has terminated to service a call, it shall not occur again until rafter the last phase permissive has terminated or a phase is on that is compatible with the coord phase.

11.10.1.8 Sequential Omit Mode - The operation shall be equal to Permissive Yield Mode with the following exceptions:

Sequential Omit Mode provides a phase by phase sliding window of service (lifted omit). One and only one phase in a ring will have the omit lifted at any time.

Following the Permissive Yield Period, the coord phase shall be omitted until the last permissive is over.

Following the Permissive Yield Period, the opening of a permissive shall occur concurrent with the closing of the prior permissive. The closing of each permissive shall occur at its normal position in the cycle.

11.10.1.9 A limitation shall be set on Sequential Omit coord Mode in that it shall apply only to units running with no more than two rings in a cluster.

11.10.1.10 Full Actuated Mode - the operation shall be as defined in Permissive Yield Mode with the following exceptions:

Following the Permissive Yield Period, any phase may be served in the standard sequence provided the permissive period for that phase has not expired.

Following the Permissive Yield Period, any phase may be re-serviced in the standard sequence provided the permissive period for that phase has not expired.

Following the Permissive Yield Period and prior to the end of the permissive for the phase before the first coord phase, the coord phase shall operate as an actuated phase.

11.10.1.11 A limitation shall be set on Full Actuated coord Mode in that it shall apply only to units running with no more than two rings in a cluster.

11.10.1.12 A minimum of 16 Timing Plans (Cycle/Split) shall be provided. The Timing Plans shall be selected using telemetry (system), hardwire, or non-interconnected (time base) commands.

11.10.1.13 A minimum of four (4) offsets shall be provided for each timing plan.

11.10.2 CYCLE LENGTH

11.10.2.1 One cycle length shall be provided for each Timing Plan. The cycle shall be adjustable over a range of 30-999 seconds in 1 second increments.

11.10.2.2 The cycle time of each Timing Plan should be equal to the sum of the phase times of the longest path between barriers in all rings in the controller.

11.10.3 SYNCHRONIZATION

11.10.3.1 For systems with a single system sync pulse, coordination timing shall be synchronized to the leading edge of that pulse, which shall serve as the master zero reference for all offset timing.

11.10.3.2 For hardwire systems with multiple sync pulses, the coordinator shall lock onto the correct sync by trying different syncs and checking for reoccurrence during successive cycles.

11.10.3.3 After a valid system sync pulse has been received the coordinator shall check for the proper occurrence of the system sync pulse during each subsequent cycle. If a sync pulse does not occur for three consecutive cycles, the coordinator shall revert to “sync monitor free” operation (may be replaced by a TBC event).

11.10.4 OFFSET

11.10.4.1 Offset shall normally be defined as the time period from the system sync pulse to the beginning of the leading coordinated phase green (local zero). The coordinator shall also be capable of referencing the offset to either the coordinated phase yield or force off point.

11.10.4.2 Offsets shall be programmable using in seconds. The range shall be from 0-999 seconds in 1 second increments. The coordinator shall provide four (4) offsets per Timing Plan.

11.10.4.3 Offset changes shall be achieved by adding or subtracting cycle time over a maximum of three cycle periods to allow a smooth transition to the new offset. Offset correction using dwell shall also be selectable.

11.10.5 SPLIT

11.10.5.1 Each split shall provide a split interval for each phase. The split interval shall be programmable using seconds. The range shall be from 0-999 seconds in 1 second increments.

11.10.5.2 Split interval settings shall determine the maximum time, including vehicle clearance (yellow and red), for a non-coordinated phase, or the minimum time for a coordinated phase.

11.10.5.3 During coordination, it shall be possible to operate a coordinated phase as actuated or non-actuated. If a coordinated phase is actuated, vehicle detections shall permit the coordinator to extend a phase beyond the normal yield point. Extended coordinated phase green shall be selectable using the same range as split interval settings (percent or seconds). If actuated coordinated phases are used they shall be able to have actuated or non-actuated (walk rest) pedestrian movements.

11.10.6 PHASE RE-SERVICE

11.10.6.1 If actuated coordinated phases are in use it shall be possible to re-service non-coordinated phases within the same cycle if sufficient time remains. A phase shall be re-serviced only if the permissive period for the phase indicates there is sufficient time remaining in the cycle to service the phase.

11.10.6.2 Phase re-service shall be capable of being enabled/ disabled in each coordination pattern. During phase re-service the coordinated phase pedestrian timing shall be inhibited until local zero.

11.10.7 TRANSITION CYCLES

11.10.7.1 The controller shall provide a smooth and orderly transition when changing from free operation to coordinated operation and from one coordination command to another.

11.10.7.2 During a free-to-coordinated transition, the controller shall initiate a pick-up cycle beginning upon receipt of a sync pulse and a valid coordination command. The controller shall then enter coordination mode upon crossing a barrier or if resting in the coordinated phases.

11.10.7.3 Each coordination command shall select a cycle, offset and split. A command change shall be implemented concurrent with a sync pulse. Cycle, offset and split changes shall not take effect until local zero.

11.10.7.4 For each timing plan the user shall be able to specify the transition method (dwell or shortway) and the maximum adjustment time per cycle.

11.10.7.5 During transition minimum green intervals, pedestrian walk and clearance intervals and vehicular clearance intervals shall not be shortened.

11.10.8 LOCAL SPLIT DEMAND

11.10.8.1 The coordinator shall provide a minimum of two split demand detector inputs (assigned from system detectors) which shall allow the selection of a preferred coordination pattern based on intersection demand.

11.10.9 FREE MODE

11.10.9.1 The coordinator shall provide a free mode of operation, where all coordination control is removed.

11.10.9.2 Free mode operation shall be selectable by coordination commands, by external input or by keyboard entry.

11.10.9.3 The coordinator shall revert to the free mode when active controller inputs or functions would interfere with coordination. Such inputs or functions shall include the following:

Manual control enable

Stop time

Automatic flash

Preemption

11.10.10 MANUAL CONTROL

11.10.10.1 The controller shall allow manual override of the current coordination command from the keyboard. The manual command shall allow selection of any coordination pattern to be in effect.

11.10.11 INTERCONNECT MODES

11.10.11.1 The coordinator shall be capable of operating with any of the following interconnect types:

Non-interconnected coordination (time-based)

Telemetry

Hardwired

11.10.11.2 The coordinator shall be compatible with fixed-time interconnect, which provides the sync pulse superimposed on the offset lines. The non-interconnected coordination mode shall serve as a backup when using telemetry or hardwired interconnect.

11.10.12 MASTER COORDINATOR

11.10.12.1 The coordinator shall output the coordination command, including sync pulse. This feature shall permit the controller to be used as a time-of-day master in a hardwired interconnected system.

11.10.13 PREEMPTION

11.10.13.1 The controller shall provide a minimum of preemption six (6) sequences. Preemption capability shall be standard and shall not require additional modules or software.

11.10.14 RAILROAD-FIRE-EMERGENCY VEHICLE PREEMPTION

11.10.14.1 The six preemptors shall be selectable as a priority or non-priority type. Priority preemptor calls shall override non-priority preemptor calls. Low-numbered priority preemptors shall override higher-numbered priority preemptor calls. Non-priority preemptor calls shall be serviced in the order received.

11.10.14.2 Each preemptor shall provide a locking and non-locking memory feature for preemptor calls. If a preemptor is in the non-locking mode and a call is received and dropped during the delay time, the preemptor shall not be serviced.

11.10.14.3 Preemptor timing intervals shall be programmable from 0-999 in one second increments or 0-9.9 in one-tenth second increments, depending on function.

11.10.14.4 A programmable delay time interval shall be provided to inhibit the start of the preemption sequence. This interval shall begin timing upon receipt of a preemption call.

11.10.14.5 An inhibit time shall be provided as the last portion of the delay time interval. During this time, phases that are not part of the preempt sequence shall be inhibited from service.

11.10.14.6 A programmable duration time shall be provided to control the minimum time that a preemptor remains active. This time shall be programmable from 0-999 in one second increments.

11.10.14.7 A programmable maximum time shall be provided to control the maximum time that a preemptor remains in the hold interval. The preemptor maximum time interval shall be inhibited if the preemptor is programmed as a priority preemptor.

11.10.14.8 Phases timing at the beginning of a preemption sequence shall remain in effect for a minimum time before the controller advances to the next sequential interval. If the phase has been timing for longer than the programmed preemptor minimum time, the controller shall immediately advance to the next sequential interval. Minimum times shall be programmable for the green/walk interval.

11.10.14.9 A phase shall advance to pedestrian clearance if it has timed the minimum WALK interval at the beginning of a preemption sequence. The programmed minimum pedestrian clearance will then be timed . During preemption, pedestrian indicators shall be selectable as being a solid DON’T WALK, OFF (blank) or fully operational.

11.10.14.10 If an overlap is in effect when the preemption sequence begins, it shall be possible to terminate the overlap so that it remains red for the remainder of the preemption sequence. Overlaps terminating or forced to terminate shall time the preemptor minimum yellow and red clearance times.

11.10.14.11 Each preemptor shall provide user-programmable green, yellow and red track clearance intervals. These shall begin timing immediately after the preemptor minimum red interval.

11.10.14.12 During the track clearance period, the selected preempt timers shall time the track clearance green, yellow and red intervals once, and then advance to the dwell interval. If track clearance timings are not selected the track clearance interval shall be omitted from the preempt sequence.

11.10.14.13 The preemption dwell interval shall begin immediately after track clearance. It shall remain in effect until the preemptor duration time and minimum hold times have elapsed and the preemptor call has been removed or the preemptor maximum time has been exceeded. During the preemption hold interval, any one of the following conditions shall be selectable:

Selected signal display

Limited phase service

All red

Flash

11.10.14.14 Any valid signal display may be selectable as a “dwell” display. Each individual signal set is programmable to indicate green, red, flashing yellow or flashing red during the track green and dwell intervals.

11.10.14.15 Each preemptor shall provide a user-programmable green, yellow and red dwell interval, during which selected phases shall operate normally, except that the minimum green interval time shall equal the hold green time. At the completion of the hold green interval, the controller shall time the hold yellow and red clearance intervals prior to transfer to the exit phases.

11.10.14.16 Up to two permissive exit phases shall be selectable to time after the preemption sequence has been completed. These shall serve as transition phases to return the controller to normal operation. It shall also be possible to place calls on selected phases upon exiting preemption.

11.10.14.17 Each preemptor shall provide a user-programmable exit maximum time. Upon exiting the preemption sequence, this time shall serve as the maximum green time in effect for one controller cycle for all phases except hold phases.

11.10.14.18 Preemptor linking shall permit preemption sequences, where lower-priority preemptors may call the higher-priority preemptors upon termination of their preemption sequence.

11.10.14.19 Preemptor active outputs shall be provided for each of the preemptors. The output shall be set to ON when the preemption sequence begins and shall remain ON for the duration of the sequence. It shall also be possible to program preempt active outputs to be ON only during preempt hold intervals. Additionally, it shall be possible to program the non-active, non-priority preemptor outputs to flash while another preemptor is active.

11.10.14.20 Preemptors shall normally override automatic flash. It shall be possible to inhibit this feature for each preemptor.

11.10.15 LOW PRIORITY ROUTINES

11.10.15.1 Six low-priority routine handlers shall provide control for bus or other low-priority vehicles. The low-priority handlers shall be overridden by railroad-fire-emergency vehicle preemptor calls.

11.10.15.2 A 6.25 pulse-per-second signal with a 50% duty cycle shall identify a low-priority call. Low-priority calls shall be capable of call memory and shall be served in the order received.

11.10.15.3 Low-priority timing intervals shall be programmable from 0-999 in one second increments or 0-9.9 in one-tenth second increments depending on the function.

11.10.15.4 A re-service time shall be provided to avoid excessive utilization of the same low-priority handler. If a call is received before the re-service time has elapsed, the handler shall not be re-serviced. If re-service time has not been entered then all phases with a call when leaving the sequence shall be serviced before the low-priority handler may be served again.

11.10.15.5 Low-priority handlers shall provide delay, inhibit, and maximum time functions similar to those for railroad-fire-emergency vehicle preemptors described above.

11.10.15.6 Low-priority handlers shall provide the following entrance intervals:

Green/pedestrian clearance
Yellow
Red

11.10.15.7 At the completion of the entrance red clearance, the low-priority routine shall advance to the hold green interval. During this interval, up to two permissive phases shall be selectable to remain green until the minimum hold time has elapsed and the low-priority routine call has been removed or the preemptor maximum time has been exceeded.

11.10.15.8 It shall be possible to program the controller to allow concurrent phases to be serviced for a low-priority routine with only one phase selected as the hold interval phase.

11.10.15.9 Preemptor active outputs shall be provided for each of the preemptors. The output shall be set to flash when the preemption sequence begins and shall remain in flash for the duration of the sequence. It shall also be possible to program preempt active outputs to flash only during preempt hold intervals.

11.10.15.10 PREEMPTION SAFEGUARDS

11.10.15.11 If a preemptor call is active when power is restored to a controller, the controller unit shall maintain the start-up condition for the duration of the preempt input and start-up time. Similarly, if external start is applied during a preemption sequence, the controller shall revert to Start-up rather than the initialization condition. The start-up condition shall remain in effect for the duration of the external start, preempt input and /or start-up time.

11.11 TIME-BASED CONTROL & NON-INTERCONNECTED COORDINATION

The controller shall include time-based control. This capability shall be a standard feature and shall not require additional modules or software.

11.11.1 CLOCK/CALENDAR FUNCTIONS

11.11.1.1 The controller shall provide a time-of-day (TOD) clock, which shall be used for all time-based control functions. The only required clock settings shall be the current time (hour, minute and second) and date (month, day and year). Day of week and week of year shall be automatically computed from the date setting.

11.11.1.2 During normal operation, the TOD clock shall use the power line frequency as its time base. When power is removed, the time shall be maintained by a crystal oscillator for up to 30 days. In the battery backup mode time is maintained to within +/- 0.005% as compared to WWV time standard.

11.11.1.3 In addition to entering time and date via the keyboard, it shall be possible to download the information from another controller, a computer or a system master.

11.11.1.4 The controller shall include a time reset input. This feature shall reset the TOD clock to 04:00:00 whenever the time reset input is TRUE.

11.11.1.5 The TOD clock shall automatically compensate for leap year and shall be programmable to automatically switch to daylight savings time. The TOD clock shall maintain correct time and date with the change of the millennium.

11.11.2 TIME-BASED CONTROL

11.11.2.1 A minimum of 250 different traffic and/or auxiliary events shall be capable of being programmed over a 99 year time frame.

11.11.2.2 A program day is the list of traffic and/or auxiliary events to occur in a 24 hour period. The TBC program shall provide for 99 program days to be defined.

11.11.2.3 The normal day-of-week (Sunday through Saturday) event listing will utilize program days 01 through 07 with Sunday being program day 01.

11.11.2.4 The exceptions to the normal day-of-week event listings (special days) will utilize program days 01 through 99. Program days 01 through 49 will be utilized for special day programs which occur on the same date (month and month day) every year. Program days 50 through 99 shall be utilized for special days which occur on one date (year, month and month day) with program days 98 and 99 being utilized for the user-defined Daylight Savings Time increment and decrement.

11.11.2.5 It shall be possible to equate program days which require the same event listing to effectively multiply the event capacity. It shall be possible to transfer (copy) an entire program day event listing to another program day to permit data editing to create a similar but different program day event listing.

11.11.3 NON-INTERCONNECTED COORDINATION

11.11.3.1 The TBC scheduler shall provide for the programming of traffic and auxiliary events to implement non-interconnected coordination. These shall not have to be entered in any special sequence. Each of the traffic events shall permit selection of the following functions:

Time of occurrence (Hour, minute and program day)
Coordination pattern
Flashing
Maximum 2 timing by phase
Phase omit by phase

11.11.3.2 Selection of TBC on-line by external input shall allow the coordination pattern selected by the TBC to override the current telemetry or hardwire system commanded coordination pattern.

11.11.3.3 When operating in the non-interconnected coordination mode the synchronization point for all cycles shall be referenced to a user selected reference time (sync reference) or the event time. The sync reference time is that time at which all cycles shall be reset to zero.

11.11.3.4 If the sync reference time is selected, the synchronization point for the cycle selected by the current event, shall be computed using the present time, sync reference time, and cycle length. The synchronization point shall occur whenever the present time is such that an even number of cycle length periods have occurred since the sync reference time.

11.12 AUXILIARY FUNCTIONS

11.12.1 These events shall be separate from the non-interconnected coordination events described above. Auxiliary events shall not have to be entered in any special sequence. Each of the events shall permit selection of the following functions:

Day program assignment
Start time
Auxiliary outputs
Dimming
Detector logging
Detector diagnostic plan
Control of eight special functions

11.13 DETECTOR FUNCTIONS

11.13.1 The controller shall provide a minimum of 64 vehicle detector inputs. Each input shall be assignable to any phase and be programmable as to detector function. Extend and delay timing shall be provided for each detector. Each detector shall be capable of operating in a lock or non-lock mode.

11.13.2 The controller shall provide detector cross switching, which permits all vehicle detectors to alternately place calls on their assigned phases and their assigned cross-switch phases. If the assigned phase is not green and the cross-switch phase is green, the detector shall place calls on the cross switch phase.

11.13.3 Each vehicle detector shall be user-programmable to operate as one of the following 7 detector types:

Type 0 (VEH) - Detector shall operate as a standard detector providing one call per actuation.
Type 1 (PED): The detector input operates as a standard pedestrian detector.
Type 2 (ONE): The detector input operates as a vehicle detector that is operational while the phase is not green until a call is received on the assigned phase.
Type 3 (SBA): Detector shall operate as follows: Vehicle calls shall be accepted only when the phase is not green. When a call is detected, it shall be held until the detection area is empty. The extend timer shall begin timing with the phase green. Once the extend timer times-out OR the detection area is empty, no further calls shall be accepted until the phase is again not green.
Type 4 (SBB): Detector shall operate as follows: Vehicle calls shall be accepted only when the phase is not green. When a call is detected, it shall be held until the detection area is empty (if the extend timer is set to zero). The extend timer shall begin timing with the phase green. If a call is received before the extend timer has timed-out, the timer shall be reset. Timer reset shall occur until a gap between the calls is large enough to allow the extend timer to time-out. Once time-out has occurred, no further calls shall be accepted until the green terminates.
Type 5 (PPL): The detector input operates as a turn vehicle detector Adaptive Protected/Permissive routine.
Type 6 (PPT): The detector input operates as a through vehicle detector Adaptive Protected/ Permissive routine.

11.13.4 Each detector input shall be capable of functioning as one of 16 system detectors.

11.13.5 Vehicle detectors shall be capable of being assigned to a minimum of 8 speed trap detector sets. Speed shall be detected using a two detector configuration. The loop spacing, used for the calculation of vehicle speeds, shall be definable by the user through the front panel keyboard.

11.13.6 Detectors that are operating as a speed trap shall also provide volume and occupancy data.

11.13.7 For system detectors the CU shall accumulate volume and occupancy data on a per cycle basis for uploading to the system master.

11.13.8 The CU shall calculate the average speed for each of the speed traps on a per cycle basis for uploading to the system master.

11.13.9 The controller shall provide a minimum of 8 hardware-denoted pedestrian detector inputs. Each pedestrian detector shall be assignable to any phase.

11.14 SYSTEM COMMUNICATIONS

The controller shall be capable of communicating with an on-street system master or directly to a central office computer-based system. This capability shall be provided through Port 3 of the controller. The controller shall receive system commands and data transmissions. In addition, it shall transmit the controller status, data base and system detector information to the system master or central computer.

11.14.1 SYSTEM COMMANDS

11.14.1.1 The system interface shall allow the controller to receive, as a minimum, the following commands:

Cycle, offset, and split (coordination pattern)
Timing parameter downloading and verification
Special function commands minimum of eight)
Coordinated, Free, standby and flash mode commands
Time and date
Request for local status

11.14.1.2 In the absence of being polled by the system master, within a user-defined period (1-255 minutes), the local will revert to backup TBC and coordination mode. When again polled by the master the local will return to the system mode and transition to the master-called program.

11.14.2 STATUS DATA

11.14.2.1 The status of each of the following functions shall be transmitted to the system master on a once-per-second basis:

Green and yellow status for all phases and overlaps
Walk and pedestrian clearance status for all phases
Vehicle and pedestrian detector status
Phase termination status
Local time
Coordination status
1. Command source
2. Sync or transitioning status of coordinator
Conflict flash status
Local flash status
Automatic flash status
Local Free
Preempt activity and calls
Status of six user-defined alarms

11.14.2.2 The following information shall be transmitted to the system master on a once-per-cycle or once per minute basis:

Cumulative volume and occupancy data for each system detector for the last sample period.

Average speed data for each speed trap for the last sample period.

When the intersection is operating in a programmed flash mode, this information shall be transmitted on a once per minute basis. During normal operation, the user shall be able to specify whether the information is transmitted on a once-per-cycle or once-per-minute basis.

11.14.2.3 The status of each of the following parameters on a per-phase basis shall be calculated on a pattern (Dial/Split/Offset) basis and transmitted to the system master:

Volume (Per cycle average number of actuations)
Stops (Per cycle average of the number of actuations received during the non-green time of the phase)
Delay (Per cycle average time of the delay on each phase. Delay accumulates based on cars waiting and elapsed time)
Utilization (Per cycle average green time used on each phase)
Number of times that each phase "gapped-out"
Number of times that each phase "maxed-out" or was "forced off"

11.14.3 UPLOAD/DOWNLOAD CAPABILITY

11.14.3.1 The system interface shall provide the capability to upload/download the entire intersection data base to/from the system master.

11.14.4 TELEMETRY

11.14.4.1 The system interface shall utilize RS-232C Data Terminal Equipment communications through Port 3 of the controller front panel.

11.14.4.2 There shall be a communications status display to show telemetry activity as follows: on or off line, carrier active or inactive, transmit active/inactive and response returned (ACK or NAK), receive active and data valid or invalid.

11.14.5 COMMUNICATIONS PROTOCOL

11.14.5.1 The vendor shall utilize a NTCIP compatible protocol for all system communications. The vendor shall fully document and publish the protocol. The vendor shall give the Utah Department of Transportation unrestricted rights to the protocol for use by the Department, their agents and other vendors.

11.15 DIAGNOSTIC FEATURES

11.15.1 The controller shall include both automatic and operator-initiated diagnostics. This capability shall be a standard feature and shall not require additional modules or software.

11.15.2 Automatic diagnostics shall verify memory, MMU compatibility programming, and microprocessor operation each time power is reapplied to the controller. After power has been applied, diagnostics shall continually verify the operation of essential elements of the controller including at a minimum: PROM, EEPROM, communications, and the microprocessor.

11.15.3 Operator initiated diagnostics shall allow the operator to verify proper operation of all controller input, output, communications, keyboard, and display functions. Both manual and automatic test modes shall be provided.

11.16 DETECTOR DIAGNOSTICS

11.16.1 Time-of-day controlled detector diagnostics shall be provided that allow testing vehicle and pedestrian detectors for no activity, maximum presence, and erratic output.

11.16.2 A minimum of two detector diagnostic plans shall be provided. These plans shall be selectable on a time-of-day basis. This shall allow varying the detector diagnostic values to correspond with changes in detector activity.

11.16.3 If a detector is diagnosed as failed, the associated phase shall be placed on minimum recall until such time as the detector is classified as “on-line”.

11.16.4 Diagnostics for NEMA TS2 detectors connected to the controller using a Bus Interface Unit (BIU) shall also include detection of watchdog, open and shorted loop, and excessive inductance change failures.

11.17 LOGGING FEATURES

The controller shall be capable of logging and reporting detector activity, detector failures, and the occurrence of selected events or alarms. Logs shall be capable of being printed or displayed on the front of the controller.

11.17.1 DETECTOR FAILURE LOGGING

11.17.1.1 The controller shall include a detector failure log buffer capable of storing a minimum of 20 time and date-stamped detector failure events. Once logged, detector failure events shall remain in the log until cleared or the log buffer capacity is exceeded at which time the oldest detector failure events shall be overwritten.

11.17.1.2 All detector diagnostic failures shall be recorded in the detector failure log including: no activity, maximum presence, erratic counts, watchdog failure, open loop, shorted loop, and excessive inductance change. If a detector recovers after a diagnostic failure, a detector on-line event shall be stored in the detector failure log.

11.17.2 EVENT LOGGING

11.17.2.1 The controller shall include an event log buffer capable of storing a minimum of 120 time and date-stamped events or alarms. Once logged, events shall remain in the buffer until cleared or the log buffer capacity is exceeded at which time the oldest events shall be overwritten.

11.17.2.2 At a minimum the following events shall be logged: communication failures, coordination faults, MMU and local flash status, preempt, power ON/OFF, low battery, data change (from keyboard), data change (from remote), processor faults, EPROM and EEPROM diagnostic faults, invalid TS2 configuration. Up to 86 different messages shall be available. An event shall be logged when an event or alarm returns to normal status.

11.18 METHOD OF MEASUREMENT

NEMA TS2 Type 1 traffic controllers shall be measured for payment by the number of units each, complete with all components provided as specified herein and delivered to the Department.

11.19 BASIS OF PAYMENT

NEMA TS2 Type 1 traffic controllers will be paid at the contract unit price each, which price shall be payment in full, for furnishing a complete NEMA TS2 Type 1 Traffic Controller and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.

12 ITEM 12. NEMA TS2 CONTROLLER - TYPE A2, Salt Lake Valley Region

12.1 INTRODUCTION

12.1.1 This specification sets forth the minimum requirements for a shelf-mountable, multi-phase, fully-actuated, digital, solid-state traffic controller. The controller shall meet, as a minimum, all applicable sections of the NEMA Standards Publication No. TS2-1992. Where differences occur, this specification shall govern. Controller versions shall be available to comply with NEMA TS2 Type 2 standards. TS2 Type 2 controller units shall be capable of operating as TS2 Type 1 controller units.

12.2 HARDWARE

12.2.1 ENCLOSURE

12.2.1.1 The controller shall be compact so as to fit in limited cabinet space. It shall be installable on a shelf that is not more than 7" deep. External dimensions shall not be larger than 10" x 16" x 9 " (H x W x D).

12.2.1.2 The enclosure shall be constructed of sheet metal and shall be finished with an attractive and durable protective coating.

12.2.1.3 The controller unit shall be of modular design. The chassis shall be metal and shall be designed for easy access during maintenance, allowing for ease of testing without requiring disassembly or extender boards.

12.2.2 ELECTRONICS

12.2.2.1 The electronics shall be modular and shall consist of vertical circuit boards.

12.2.2.2 A microprocessor shall be used for all timing and control functions. Continuing operation of the microprocessor shall be verified by an independent monitor circuit, which shall set an output to FALSE and indicate an error message if a pulse is not received from the microprocessor within a defined period.

12.2.2.3 In the interest of reliability, sockets shall only be used for components with 20 pins or more.

12.2.2.4 A built-in, high-efficiency power supply shall generate all required internal voltages. All voltages shall be regulated and shall be monitored with control signals. All fuses, connectors and controls shall be mounted on the front of the controller unit.

12.2.2.5 Timing of the controller shall be derived from the 120 VAC power line. A 10-year lithium battery shall maintain the time-of-day clock and digital data during a power outage lasting up to 30 days. Lead-acid, nickel-cadmium, or alkaline batteries shall not be acceptable.

12.2.2.6 All printed circuit boards shall meet the requirements of the NEMA Standard plus the following requirements to enhance reliability:

All plated-through holes and exposed circuit traces shall be plated with solder.

Both sides of the printed circuit board shall be covered with a solder mask material.

The circuit reference designation for all components and the polarity of all capacitors and diodes shall be clearly marked adjacent to the component. Pin 1 for all integrated circuit packages shall be designated on all printed circuit boards.

All electrical mating surfaces shall be gold-plated.

12.2.3 FRONT PANEL & CONNECTORS

12.2.3.1 The front of the controller shall consist of a panel for the display and keyboard plus a separate panel for the connectors.

12.2.3.2 An 8-line by 40-character/line alphanumeric liquid crystal display (LCD) shall show program and status information. The display area shall have nominal measurements of 1 1/2" x 5 1/4" (H x W) or larger. For ease of viewing, backlighting and multiple levels of contrast adjustment shall be provided.

12.2.3.3 Front-panel operator inputs shall be via clearly labeled and environmentally-sealed keys. These shall include a 12 position (0-9, plus * and #) telephone-type keypad, four-arrow cursor control keys plus four additional keys (E, F, + and -).

12.2.3.4 All interface connectors shall be accessible from the front of the controller.

12.2.3.5 The Port 3 connector shall be mounted on the front of the CU and shall be an RS-232C Data Terminal Equipment (DTE) interface for interconnecting the CU to the system master.

12.2.3.6 The Port 3 connector shall be a 9 pin metal shell “D” subminiature type connector. The connector shall utilize male contacts and shall be equipped with latching blocks.

12.2.3.7 The CU shall be furnished with a Port 4 which shall be an RS232C Date Terminal Equipment (DTE) interface for communicating with auxiliary equipment in the cabinet assembly.

12.2.3.8 The port 4 connector shall be a 9 pin metal shell “D” subminiature type connector. The Connector shall utilize male contacts and shall be equipped with latching springs.

12.2.3.9 The front panel shall be furnished with A, B & C connectors as specified in the NEMA TS2 specifications. The A, B & C connectors shall be configured for Mode 0, TS1 compatible.

12.2.3.10 The front panel shall also be equipped with a D connector. This connector shall be a 37 pin utilizing female contacts. The connector shall be an AMP #747315-2 or equivalent. The pin functions shall be as follows:

Pin		I/O		Function
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37		I I I I I I I I I I I I I I I I I I I I I O O O O O O O O O O O O O O O O		System Detector 1 System Detector 7 System Detector 8 System Detector 5 System Detector 6 System Detector 2 System Detector 3 System Detector 4 Automatic Flash Preempt 1 Preempt 2 Preempt 3 Preempt 4 MMU/Conflict Flash Status Local Flash Status Special Status 1 Special Status 2 Special Status 3 Special Status 4 Special Status 5 Special Status 6 Special Function 7 Special Function 8 Special Function 5 Special Function 6 Special Function 2 Special Function 3 Special Function 4 Special Function 1 Auxiliary 1 Auxiliary 2 or any Preempt Auxiliary 3 or Detector Reset Logic Common Port 3 Serial Communications 1 Port 3 Serial Communications 1 Reserved Reserved

12.2.4 SERVICEABILITY

12.2.4.1 All electronic modules other than the power supply shall be easily removable from the front of the controller using a standard screwdriver as the only tool. All power and signal connections to the circuit boards shall be via plug-in connectors.

12.2.4.2 The controller layout shall allow the removal and replacement of any circuit board without unplugging or removing other circuit boards. No more than two boards shall be attached together to form a circuit assembly. Attaching hardware shall use captive screws or 1/4-turn fasteners to secure circuit assemblies to the enclosure.

12.2.4.3 The controller enclosure shall allow complete disassembly using a standard screwdriver. It shall be designed so that one side of any circuit board is accessible for troubleshooting and testing while the controller is still in operation. This capability shall be accomplished without the use of extender cards or card pullers.

12.2.5 OPERATING DISPLAYS

12.2.5.1 The dynamic displays listed below shall be provided to show the operational status of the controller. Additional displays shall be offered for programming.

12.2.5.2 An intersection status display shall indicate the active status of all signal driver outputs and vehicle plus pedestrian calls. When this display is active, vehicle and/or pedestrian calls may be placed from the keyboard.

12.2.5.3 An active timer display shall show a summary of ring, phase, coordination, preemption and time-based control status. The menu shall provide for the selection of any combination of the rings for display (R1 + R2, R3 + R4, R1 + R3, etc.).

12.2.5.4 This status display shall indicate current interval, pedestrian, density, maximum, and maximum extension timing by phase and ring. The status of vehicle and pedestrian phases shall be displayed in combination with vehicle and pedestrian calls. Operational modes shall also be displayed e.g. Time Base, Interconnected, System, Backup, Manual, System Flash, Start Flash, Stoptime, Preempt, Priority, TS2 Diagnostic Flash, etc.

12.2.5.5 When this display is active vehicle and/or pedestrian calls may be placed from the keyboard.

12.2.5.6 A coordination timers display shall allow viewing of the real time status of coordination timer(s) and parameters for the active pattern. Indicate the command source, current pattern information, local/system cycle count, offset mode, offset correction, time-based control status, coord mode, max mode, force-off mode, phase pattern & mode and permitted phase & control data.

12.2.5.7 A preempt timers display shall indicate preemption (railroad, fire, emergency, bus) and priority status. When a preemptor is active, the display shall also indicate preemptor interval and timer countdown as well as priority lockout and max call time out.

12.2.5.8 A time base status display shall indicate the current time and date, the current day and week program, the active programmed selections of the coordination pattern and auxiliary functions.

12.2.5.9 A comm status display shall indicate the current status of communications on Port 2 (RS232 connector), Port 3 (systems interface connector) and Port 4 (equipment interface connector). The display shall include the settings (speed, data bits, parity and stop bits) programmed for each port.

12.2.5.10 A detector status display shall indicate the current status for up to 64 detectors. The display shall show the status as determined by the detector diagnostics capability of the controller. The condition will be reported as one of the following states: on-line, failed open loop, failed shorted loop, failed excessive inductance change, failed max presence diagnostic, failed no activity diagnostic, failed erratic counts diagnostic, BIU frame fault, not supported or “LWD” (not TS2 detector, detector failure or detector watchdog timeout).

12.2.5.11 The detector activity display shall show the current cumulative volume and occupancy values for the system detectors connected to the CU. These values shall be updated in real-time, and shall reset to zero after the information has been uploaded to the central computer or master.

12.2.5.12 The detector activity display shall also provide the average speed for all speed traps connected to the CU. The value displayed shall be the average speed during the sample period and shall be updated in real-time. The display shall reset to zero after the information has been uploaded to the central computer or master.

12.3 PROGRAMMING

12.3.1 PROGRAMMING DISPLAYS

12.3.1.1 All programming parameters shall be accessible and capable of being programmed through the front-panel keyboard. Programming displays in the form of menus shall aid the operator in entering data from the front-panel keyboard.

12.3.1.2 A main menu shall allow the user to select a major function of the controller. A sub-menu shall then be displayed to allow the user to select a sub-function within the major function. Cursor keys shall allow the user to scroll through all menus and sub-menus.

12.3.1.3 English language and traffic engineering terminology shall be used throughout to facilitate programming. The display organization shall allow traffic personnel to program the controller without using reference cards or manuals.

12.3.1.4 Programming entries shall consist of alpha or numerical values. During program entry, the new data shall be displayed as it is entered. Values shall only be validated and stored when entered by the user. is pressed.

12.3.2 PROGRAMMING METHODS

12.3.2.1 The methods listed below shall be available for controller programming. It shall be possible to program all CU parameters through each of the following methods. The manufacturer shall be able to provide as off-the-shelf items all of the firmware and software required to effect the listed programming methods and to implement network operation with system masters and host PC's.

Manual data entry via the front panel keyboard.

Data downloading, through the system interface, via telemetry from a system master.

Data downloading from a portable PC-compatible computer, through the port 2 connector, via null-modem cable.

Data downloading from a PC-compatible computer, through the Port 2 connector, via modem.

Data downloading from one controller to another using a Port 2 on each controller.

12.3.3 PROGRAMMING SECURITY

12.3.3.1 The controller unit shall prevent the alteration of keypad set unit variables prior to the user having entered a specific code. No access code shall be required to display data. Access codes shall initially be set at "0000" and shall be definable by the user. The controller shall allow entry of a code to prevent access from being turned off.

12.3.4 PROGRAMMING UTILITY FUNCTIONS

12.3.4.1 A copy function shall permit copying all timing data from one phase to another. It shall also permit copying all coordination pattern data from one pattern to another. This feature will facilitate data entry when programming any two or more phases with the same timing values and/or two or more coordination patterns with the same pattern data.

12.3.4.2 The controller unit shall contain a backup data base stored in nonvolatile memory. A copy function shall permit transferring the backup data base to the active data base. An alternate data base for interchange control operation shall be selectable from the keyboard.

12.3.4.3 A print function shall allow the printing of controller unit data and detector count, detector failure, and event logs. The controller shall be capable of interfacing with any printer with an RS-232 interface and capable of a minimum width of 80 columns. The communication rate shall be 1200 bps minimum.

12.3.4.4 A sign-on message shall allow the user to view the controller software version number. This message shall be displayed upon power-up until a key is depressed.

12.4 ACTUATED CONTROL FUNCTIONS

The controller shall provide all actuated control functions and operations required by the NEMA TS2 Standard. In addition, it shall provide the features described in the following paragraphs.

12.4.1 PHASE SEQUENCE

12.4.1.1 The phase sequence of the controller shall be programmable in any combination of sixteen phases, eight concurrent groups and four timing rings.

12.4.1.2 Phase sequence information shall be changeable from the keyboard and stored in EEPROM data memory.

12.4.1.3 The standard phase sequence of the controller shall also be capable of being altered by coordination, time-of-day or external alternate sequence command. The alternate sequence commands shall allow reversing the normal phase sequence of each phase pair as shown below:

Command A reverses phases 1 and 2.

Command B reverses phases 3 and 4.

Command C reverses phases 5 and 6.

Command D reverses phases 7 and 8.

Command E reverses phases 9 and 10.

Command F reverses phases 11 and 12.

12.4.2 TIMING INTERVALS

12.4.2.1 Timing intervals shall be programmable from 0-99 in one second increments, 0-999 in one second increments or from 0-9.9 in one-tenth second increments, depending on the function.

12.4.2.2 Guaranteed minimum interval values of 3.0 seconds shall be set for all yellow clearance timings (normal and preempt routines).

12.4.2.3 Cars before reduction shall provide a user-specified number of actuations, or cars waiting, that must occur before starting gap reduction. Gap reduction shall be initiated by either time before reduction or cars before reduction, whichever reaches its maximum value first.

12.4.2.4 During non-coordinated operation the controller shall be capable of dynamically extending the maximum green time for each phase based on vehicle demand. Up to three dynamic maximum green intervals shall be selectable per phase based on time-of-day. The initial interval shall be selectable as either Max 1 or Max 2. If the phase terminates due to max-out for two successive cycles, then the maximum green time in effect shall automatically be extended by one dynamic step interval on each successive cycle until it is equal to the dynamic Max value. If the phase gaps out for two successive cycles, then the maximum green time shall be reduced by one dynamic step interval until such subtraction would mean the adaptive max was less than the smaller of the normal max or the dynamic max. value.

12.4.2.5 During coordinated operation, the controller unit shall be capable of dynamically adjusting the phase splits (Critical Intersection Control). This dynamic adjustment shall be performed such that the offset and cycle length of the current timing plan are preserved, and phase minimums are not violated.

12.4.2.6 Critical Intersection Control shall only be performed by the CU if that function has been enabled by the system master, or central computer, for the controller unit and timing plan in use.

12.4.2.7 Prior to initiating Critical Intersection Control, the CU shall verify that all required detectors are functioning properly, and that volume conditions at the intersection are such that CIC can provide a benefit to the traffic flow.

12.4.2.8 When CIC is enabled, all of the necessary detectors are functioning, and the proper traffic flow conditions are met, CIC shall dynamically adjust the vehicular phase splits on a cycle-by-cycle basis based on the demand for each phase. Phase demand shall be based on smoothed volume and occupancy data collected by the system detectors. Exclusive pedestrian phases shall be excluded from the calculations.

12.4.2.9 The calculation of phase splits shall be performed in the following manner:

First, the total computed green demand and cycle length are reduced by the amount of time necessary to satisfy all phase minimum durations specified for the timing plan.

Second, the remaining green time is allocated based on the percentage of green demand for each phase versus the total green demand.

Any remaining time (due to round off errors) is divided equally among the phases according to the phase length in descending order.

12.4.2.10 The calculation of green demand for each phase shall be computed based on the following equation:

D=R(A1*O+A2*V+A3*O*V) where

D=computed green demand

R=vehicle release rate (user specified between 0-5)

A1= CIC coefficient 1 (user specified between 0-5)

A2= CIC coefficient 2 (user specified between 0-5)

A3= CIC coefficient 3 (user specified between 0-5)

O= smoothed occupancy

V= smoothed volume

12.4.3 OVERLAPS

12.4.3.1 The controller shall provide eight internally-generated overlaps (A,B,C,D, E, F, G and H). These shall be individually programmable as standard or protected/permissive. The green, yellow and red intervals shall be individually programmable following termination of the parent phase.

12.4.3.2 Overlap functions shall be programmable from the controller keyboard.

12.4.4 CONDITIONAL SERVICE

12.4.4.1 The controller shall provide a programmable conditional service feature. When selected, the controller shall service an odd-numbered phase once normal service to that phase has been completed and enough time for additional service exists on the concurrent even phase.

12.4.5 ADDITIONAL FEATURES

12.4.5.1 The following features shall be programmable for each phase:

Phase in use
Locking/non-locking detector memory
Vehicle recall
Pedestrian recall
Maximum recall
Soft recall

12.4.5.2 Soft recall shall return the controller to the programmed phase in the absence of other calls.

12.4.5.3 The controller shall permit power-up start and external start to be individually programmed by phase and interval. Start intervals shall be green, yellow or red.

12.4.5.4 During a power-up start condition, the controller shall be capable of timing an all-red or flash interval before the power-up start phase(s) and interval are displayed.

12.4.5.5 The controller shall provide last-car passage operation on a per phase basis. When selected, this feature shall provide a full passage (vehicle extension) interval when a phase gaps out with a gap in effect less than the vehicle extension interval (preset gap).

12.4.5.6 The controller shall provide both single and dual entry operation. When selected, dual entry shall cause the controller to ensure that one phase is timing in each ring.

12.4.5.7 It shall be possible via keyboard selection to inhibit the service of a phase with other phase(s) within the same concurrent group.

12.4.5.8 The controller shall provide the following additional selectable pedestrian functions:

Actuated phase rest in WALK.

Flashing WALK output.

Pedestrian clearance protection during manual control.

Pedestrian clearance through yellow.

12.4.5.9 The controller shall provide a programmable simultaneous gap termination feature. When programmed, phases in both rings shall gap out together in order to terminate the green interval and cross the barrier.

12.4.5.10 The controller shall provide control of five-section, protected/permissive left turn heads. When selected, this feature shall cause the through (even) phase yellow to inhibit display of the left turn (odd) phase yellow.

12.4.5.11 The controller shall provide automatic flash selection per the requirements of the MUTCD. Both the flash entrance and exit phases shall be programmable through the keyboard, and flashing shall be controlled by either setting the fault/voltage monitor output to be FALSE or by flashing through the load switch driver outputs. Automatic flash shall be selectable by external input, system command, or time of day.

12.4.5.12 The controller shall provide dimming for selectable load switch outputs. Dimming shall be accomplished by inhibiting the selected outputs for alternate half cycles of the 120 VAC line. Dimming shall be controllable by time of day and an external input. Programming shall permit individual dimming of the Green/Walk, Yellow/Ped Clear, Red/Don't Walk outputs for each load switch.

12.5 COORDINATION

12.5.1 COORDINATION MODES

12.5.1.1 Permissive Mode - The coord phase(s) shall operate as non-actuated when coordinated. The coordinator shall provide for a controlled release (permissive period) from the coord phase(s) to each of the remaining phases in sequence. When a call is not present for the phase to be serviced next in sequence, the coordinator shall re-allocate that phase’s time to the end of the coord phase.

12.5.1.2 The first part of each permissive period shall consist of a vehicle permissive period. The length of the period shall be determined by the phase split and the vehicle minimum service time.

12.5.1.3 The second part of each permissive period shall consist of a pedestrian permissive concurrent with the vehicle permissive. The length of this period shall be determined by the phase split and the pedestrian minimum service time.

12.5.1.4 Prior to the beginning of the first permissive period, the coord phase pedestrian shall display the ped clear indication and dwell “Don’t Walk. This will exp