ITS - Intelligent Transportation Systems Report ITS Home Page

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:

      1. Traffic plan selection by time-of-day or traffic responsive
      2. Crossing arterial synchronization
      3. Diagnostics
      4. Events
      5. Logs
      6. Reports
      7. 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:

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:

9.4        SYSTEM CONTROL

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

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:

          1. A pattern (C,S,O) or Free and time-of-day, or
          2. An auxiliary event consisting of a special function output, sample interval time, log interval time and time-of-day, or
          3. 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:

          1. Flashing
          2. Free operation
          3. Standby
          4. Traffic responsive
          5. 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.

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:

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:

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:

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:

      1. Group Active Status - The central office operator may view the current operating mode data for both groups.
      2. Intersection And Detector Status - The central office operator may view the current status of all intersections and system detectors.
      3. Master Controller Time Base Status - The central office operator may view the current status of the master time base functions.
      4. 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.
      5. 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.

      1. Controller Unit Status - Current status of the controller ring timers and phase states.
      2. Coordination Status - Current status of the controller coordination timers and states.
      3. Preemption Status - Current status of the controller preemption timers and states.
      4. Local Time Base Status - Current status of the local time base function.
      5. 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:

      1. View/edit disk resident data
      2. 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
      3. Download disk data to a master
      4. Print disk resident data
      5. 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.

      1. Enter local data and store on disk
      2. 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
      3. Download disk data to a master
      4. Print disk resident data
      5. 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:

      1. System Critical Alarms - The log shall include date, time, place, and mode of local and/or on-street master controller critical alarm.
      2. Master Alarms - Master controller alarm history. The log shall include date, time, place, and mode of on-street master alarm.
      3. Communications Failures - The log shall include date, time, place, and mode of on-street master communications failure.
      4. Group Pattern Changes - The log shall include date, time, place, and mode of on-street master group pattern change.
      5. Traffic Responsive Pattern Changes - The log shall include date, time, place, and mode of on-street master traffic responsive pattern change.
      6. System Detector Logs - The log shall include date, time, and values of each detector input to each channel.
      7. 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:

      1. Local Alarms - The log shall include date, time, place, and mode of local intersection alarm.
      2. Measurements Of Effectiveness (MOEs) - The log shall include date, time, and values of volume, stops, delay, and utilization.
      3. Communications Failures - The log shall include date, time, place, and mode of local intersection communications failure.
      4. Detector Failures - The log shall include date, time, place, and mode of local intersection detector failure.
      5. 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 protec­tive 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 compo­nents with 20 pins or more.

11.4.3 A built-in, high-efficiency power supply shall generate all re­quired 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 alka­line batteries shall not be accept­able.

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

      1. All plated-through holes and exposed circuit traces shall be plated with solder.
      2. Both sides of the printed circuit board shall be covered with a solder mask material.
      3. 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 desig­nated on all printed circuit boards.
      4. 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 informa­tion. 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 repla­cement 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 acces­sible for troubleshooting and testing while the controller is still in operation. This capa­bi­lity 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 con­trol 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 inter­val, pedestrian, density, maximum, and maximum extension timing by phase and ring. The status of vehicle and pe­destrian 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 cor­rection, 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 (rail­road, 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 enter­ing data from the front-panel keyboard.

11.8.1.2 A main menu shall allow the user to select a major func­tion of the con­trol­ler. A sub-menu shall then be dis­played to allow the user to select a sub-function within the major func­tion. 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 organi­za­tion shall allow traffic personnel to program the controller with­out using refe­rence 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 inter­face 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 con­trol­­ler 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 func­tions 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 pro­gram­mable 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 inter­val 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:

        1. 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.
        2. Second, the remaining green time is allocated based on the percentage of green demand for each phase versus the total green demand.
        3. 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-gene­rated overlaps (A,B,C,D, E, F, G and H). These shall be individually program­mable as standard or protected/permissive. The green, yellow and red intervals shall be individually program­mable 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 condi­tional 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:

        1. Phase in use
        2. Locking/non-locking detector memory
        3. Vehicle recall
        4. Pedestrian recall
        5. Maximum recall
        6. 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 opera­tion 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 con­trol­ler 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 simul­ta­neous 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 moni­tor 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 inhi­biting 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 rela­tion­ships, 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:

      1. The coord phase pedestrian shall be actuated.
      2. Immediately prior to the first permissive, the coordinator will provide a variable period for the coord phase extension (Permissive Yield Point).
      3. 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:

      1. 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.
      2. Following the Permissive Yield Period, the coord phase shall be omitted until the last permissive is over.
      3. 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:

      1. Following the Permissive Yield Period, any phase may be served in the standard sequence provided the permissive period for that phase has not expired.
      2. 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.
      3. 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 coor­dinated 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 program­mable 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 coor­dinated 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 transi­tion 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 imple­mented 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 com­mands, by external input or by keyboard entry.

11.10.9.3 The coordinator shall revert to the free mode when active con­troller inputs or functions would interfere with coor­dina­tion. Such inputs or functions shall include the following:

      1. Manual control enable
      2. Stop time
      3. Automatic flash
      4. 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:

      1. Non-interconnected coordination (time-based)
      2. Telemetry
      3. Hardwired

11.10.11.2 The coordinator shall be compatible with fixed-time inter­­connect, 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 hard­wired inter­connected 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 over­ride non-priority preemptor calls. Low-numbered priority preemptors shall override higher-numbered prio­rity 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 ser­viced.

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 inter­val 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 inhi­bited 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 incre­ments.

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 program­med preemptor minimum time, the controller shall immedia­tely advance to the next sequential interval. Mini­mum 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 select­able as being a solid DON’T WALK, OFF (blank) or fully opera­tional.

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 clear­ance 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 clear­ance. It shall remain in effect until the pre­emptor 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 pre­emp­tion hold interval, any one of the following conditions shall be selectable:

      1. Selected signal display
      2. Limited phase service
      3. All red
      4. 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 control­ler 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 sequen­ces, where lower-priority preemp­tors 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:

      1. Green/pedestrian clearance
      2. Yellow
      3. 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 automati­cally com­puted 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:

          1. Time of occurrence (Hour, minute and program day)
          2. Coordination pattern
          3. Flashing
          4. Maximum 2 timing by phase
          5. 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:

      1. Day program assignment
      2. Start time
      3. Auxiliary outputs
      4. Dimming
      5. Detector logging
      6. Detector diagnostic plan
      7. 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:

      1. Type 0 (VEH) - Detector shall operate as a standard detector providing one call per actuation.
      2. Type 1 (PED): The detector input operates as a standard pedestrian detector.
      3. 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.
      4. 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.
      5. 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.
      6. Type 5 (PPL): The detector input operates as a turn vehicle detector Adaptive Protected/Permissive routine.
      7. 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:

        1. Cycle, offset, and split (coordination pattern)
        2. Timing parameter downloading and verification
        3. Special function commands minimum of eight)
        4. Coordinated, Free, standby and flash mode commands
        5. Time and date
        6. 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:

        1. Green and yellow status for all phases and overlaps
        2. Walk and pedestrian clearance status for all phases
        3. Vehicle and pedestrian detector status
        4. Phase termination status
        5. Local time
        6. Coordination status
          1. Command source
          2. Sync or transitioning status of coordinator
        7. Conflict flash status
        8. Local flash status
        9. Automatic flash status
        10. Local Free
        11. Preempt activity and calls
        12. 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:

      1. Cumulative volume and occupancy data for each system detector for the last sample period.
      2. 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:

      1. Volume (Per cycle average number of actuations)
      2. Stops (Per cycle average of the number of actuations received during the non-green time of the phase)
      3. Delay (Per cycle average time of the delay on each phase. Delay accumulates based on cars waiting and elapsed time)
      4. Utilization (Per cycle average green time used on each phase)
      5. Number of times that each phase "gapped-out"
      6. 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.

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.

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 protec­tive 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 compo­nents with 20 pins or more.

12.2.2.4 A built-in, high-efficiency power supply shall generate all re­quired 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 alka­line batteries shall not be accept­able.

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

      1. All plated-through holes and exposed circuit traces shall be plated with solder.
      2. Both sides of the printed circuit board shall be covered with a solder mask material.
      3. 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 desig­nated on all printed circuit boards.
      4. 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 informa­tion. 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 repla­cement 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 acces­sible for troubleshooting and testing while the controller is still in operation. This capa­bi­lity 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 con­trol 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 inter­val, pedestrian, density, maximum, and maximum extension timing by phase and ring. The status of vehicle and pe­destrian 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 cor­rection, 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 (rail­road, 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 enter­ing data from the front-panel keyboard.

12.3.1.2 A main menu shall allow the user to select a major func­tion of the con­trol­ler. A sub-menu shall then be dis­played to allow the user to select a sub-function within the major func­tion. 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 organi­za­tion shall allow traffic personnel to program the controller with­out using refe­rence 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.

      1. Manual data entry via the front panel keyboard.
      2. Data downloading, through the system interface, via telemetry from a system master.
      3. Data downloading from a portable PC-compatible computer, through the port 2 connector, via null-modem cable.
      4. Data downloading from a PC-compatible computer, through the Port 2 connector, via modem.
      5. 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 inter­face 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 con­trol­­ler 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 func­tions 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 pro­gram­mable 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:

      1. Command A reverses phases 1 and 2.
      2. Command B reverses phases 3 and 4.
      3. Command C reverses phases 5 and 6.
      4. Command D reverses phases 7 and 8.
      5. Command E reverses phases 9 and 10.
      6. 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 inter­val 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:

      1. 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.
      2. Second, the remaining green time is allocated based on the percentage of green demand for each phase versus the total green demand.
      3. 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-gene­rated overlaps (A,B,C,D, E, F, G and H). These shall be individually program­mable as standard or protected/permissive. The green, yellow and red intervals shall be individually program­mable 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 condi­tional 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:

          1. Phase in use
          2. Locking/non-locking detector memory
          3. Vehicle recall
          4. Pedestrian recall
          5. Maximum recall
          6. 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 opera­tion 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 con­trol­ler 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:

      1. Actuated phase rest in WALK.
      2. Flashing WALK output.
      3. Pedestrian clearance protection during manual control.
      4. Pedestrian clearance through yellow.

12.4.5.9 The controller shall provide a programmable simul­ta­neous 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 moni­tor 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 inhi­biting 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

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

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 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.

12.5.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.

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

      1. The coord phase pedestrian shall be actuated.
      2. Immediately prior to the first permissive, the coordinator will provide a variable period for the coord phase extension (Permissive Yield Point).
      3. The amount of coord phase extension shall be distributed proportionally .

12.5.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.

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

      1. 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.
      2. Following the Permissive Yield Period, the coord phase shall be omitted until the last permissive is over.
      3. 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.

12.5.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.

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

      1. Following the Permissive Yield Period, any phase may be served in the standard sequence provided the permissive period for that phase has not expired.
      2. 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.
      3. 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.

12.5.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.

12.5.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.

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

12.5.2 CYCLE LENGTH

12.5.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.

12.5.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.

12.5.3 SYNCHRONIZATION

12.5.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.

12.5.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.

12.5.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).

12.5.4 OFFSET

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

12.5.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.

12.5.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.

12.5.5 SPLIT

12.5.5.1 Each split shall provide a split interval for each phase. The split interval shall be program­mable using seconds. The range shall be from 0-999 seconds in 1 second increments.

12.5.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.

12.5.5.3 During coordination, it shall be possible to operate a coordinated phase as actuated or non-actuated. If a coor­dinated 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.

12.5.6 PHASE RE-SERVICE

12.5.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.

12.5.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.

12.5.7 TRANSITION CYCLES

12.5.7.1 The controller shall provide a smooth and orderly transi­tion when changing from free operation to coordinated operation and from one coordination command to another.

12.5.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.

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

12.5.8 LOCAL SPLIT DEMAND

12.5.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.

12.5.9 FREE MODE

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

12.5.9.2 Free mode operation shall be selectable by coordination com­mands, by external input or by keyboard entry.

12.5.9.3 The coordinator shall revert to the free mode when active con­troller inputs or functions would interfere with coor­dina­tion. Such inputs or functions shall include the following:

      1. Manual control enable
      2. Stop time
      3. Automatic flash
      4. Preemption

12.5.10 MANUAL CONTROL

12.5.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.

12.5.11 INTERCONNECT MODES

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

      1. Non-interconnected coordination (time-based)
      2. Telemetry
      3. Hardwired

12.5.11.2 The coordinator shall be compatible with fixed-time inter­­connect, 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.

12.5.12 MASTER COORDINATOR

12.5.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 hard­wired inter­connected system.

12.5.13 PREEMPTION

12.5.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.

12.5.14 RAILROAD-FIRE-EMERGENCY VEHICLE PREEMPTION

12.5.14.1 The six preemptors shall be selectable as a priority or non-priority type. Priority preemptor calls shall over­ride non-priority preemptor calls. Low-numbered priority preemptors shall override higher-numbered prio­rity preemptor calls. Non-priority preemptor calls shall be serviced in the order received.

12.5.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 ser­viced.

12.5.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.

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

12.5.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 inhi­bited from service.

12.5.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 incre­ments.

12.5.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.

12.5.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 program­med preemptor minimum time, the controller shall immedia­tely advance to the next sequential interval. Mini­mum times shall be programmable for the green/walk interval.

12.5.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 select­able as being a solid DON’T WALK, OFF (blank) or fully opera­tional.

12.5.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.

12.5.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.

12.5.14.12 During the track clearance period, the selected preempt timers shall time the track clear­ance 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.

12.5.14.13 The preemption dwell interval shall begin immediately after track clear­ance. It shall remain in effect until the pre­emptor 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 pre­emp­tion hold interval, any one of the following conditions shall be selectable:

      1. Selected signal display
      2. Limited phase service
      3. All red
      4. Flash

12.5.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.

12.5.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 control­ler shall time the hold yellow and red clearance intervals prior to transfer to the exit phases.

12.5.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.

12.5.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.

12.5.14.18 Preemptor linking shall permit preemption sequen­ces, where lower-priority preemp­tors may call the higher-priority preemptors upon termination of their preemption sequence.

12.5.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.

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

12.5.15 LOW PRIORITY ROUTINES

12.5.15.0.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.

12.5.15.0.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.

12.5.15.0.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.

12.5.15.0.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.

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

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

        1. Green/pedestrian clearance
        2. Yellow
        3. Red

12.5.15.1 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.

12.5.15.2 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.

12.5.15.3 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.

12.5.16 PREEMPTION SAFEGUARDS

12.5.16.1 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.

12.6 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.

12.6.1 CLOCK/CALENDAR FUNCTIONS

12.6.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 automati­cally com­puted from the date setting.

12.6.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.

12.6.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.

12.6.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.

12.6.1.5 The TOD clock shall automatically compensate for leap year and shall be programmable to automatically switch to daylight savings time.

12.6.2 TIME-BASED CONTROL

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

12.6.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.

12.6.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.

12.6.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.

12.6.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.

12.6.3 NON-INTERCONNECTED COORDINATION

12.6.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:

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

12.6.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.

12.6.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.

12.6.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.

12.6.4 AUXILIARY FUNCTIONS

12.6.4.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:

      1. Day program assignment
      2. Start time
      3. Auxiliary outputs
      4. Dimming
      5. Detector logging
      6. Detector diagnostic plan
      7. Control of eight special functions

12.7 DETECTOR FUNCTIONS

12.7.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.

12.7.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.

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

        1. Type 0 (VEH) - Detector shall operate as a standard detector providing one call per actuation.
        2. Type 1 (PED): The detector input operates as a standard pedestrian detector.
        3. 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.
        4. 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.
        5. 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.
        6. Type 5 (PPL): The detector input operates as a turn vehicle detector Adaptive Protected/Permissive routine.
        7. Type 6 (PPT): The detector input operates as a through vehicle detector Adaptive Protected/ Permissive routine.

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

12.7.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.

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

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

12.7.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.

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

12.8 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.

12.8.1 SYSTEM COMMANDS

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

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

12.8.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.

12.8.2 STATUS DATA

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

      1. Green and yellow status for all phases and overlaps
      2. Walk and pedestrian clearance status for all phases
      3. Vehicle and pedestrian detector status
      4. Phase termination status
      5. Local time
      6. Coordination status
        1. Command source
        2. (2) Sync or transitioning status of coordinator
      7. Conflict flash status
      8. Local flash status
      9. Automatic flash status
      10. Local Free
      11. Preempt activity and calls
      12. Status of six user-defined alarms

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

      1. Cumulative volume and occupancy data for each system detector for the last sample period.
      2. 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.

12.8.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:

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

12.8.3 UPLOAD/DOWNLOAD CAPABILITY

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

12.8.4 TELEMETRY

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

12.8.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.

12.8.5 COMMUNICATIONS PROTOCOL

12.8.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.

12.8.6 DIAGNOSTIC FEATURES

12.8.6.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.

12.8.6.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.

12.8.6.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.

12.8.7 DETECTOR DIAGNOSTICS

12.8.7.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.

12.8.7.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.

12.8.7.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”.

12.8.7.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.

12.9 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.

12.9.1 DETECTOR FAILURE LOGGING

12.9.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.

12.9.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.

12.9.2 EVENT LOGGING

12.9.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.

12.9.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.

12.10 METHOD OF MEASUREMENT

NEMA TS2 Type 2 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.

12.11 BASIS OF PAYMENT

NEMA TS2 Type 2 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 2 traffic controller and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.


13    ITEM 13. NEMA TS2 TYPE 1 CABINET - SIZE 5, CONFIGURATION 3

13.1 All requirements for the NEMA TS2 TYPE 1 Cabinet - Size 5, CONFIGURATION 3, are described in ITEM 14, NEMA TS2 TYPE 1 CABINET - SIZE 6, CONFIGURATION 4, of this RFP, below.


14    ITEM 14. NEMA TS2 TYPE 1 CABINET - SIZE 6, CONFIGURATION 4

14.1 GENERAL

14.1.1 This specification sets forth the minimum requirements for a TS2 Type 1 traffic control cabinet assembly. The cabinet assembly shall meet, as a minimum, all applica­ble sections of the NEMA Standard Publication No. TS2-1992. Where differences occur, this specification shall govern.

14.2 CABINET DESIGN AND CONSTRUCTION

14.2.1 The cabinet shall be constructed from type 5052-H32 aluminum with a minimum thickness of 0.125 inches.

14.2.2 The cabinet shall be designed and manufactured with materials that will allow rigid mounting, whether intended for pole, base or pedestal mount­ing. The cabinet must not flex on its mount.

14.2.3 A rain channel shall be incorporated into the design of the main door opening to prevent liquids from entering the enclosure. The cabinet door opening must be a minimum of 80 percent of the front surface of the cabinet.

14.2.4 The top of the cabinet shall incorporate a 1-inch slope toward the rear to prevent rain accumulation.

14.2.5 Unless otherwise specified, the cabinet shall be sup­plied with a natural aluminum finish. Sufficient care shall be taken in handling to ensure that scratches are minimized. All surfaces shall be free from weld flash. Welds shall be smooth, neatly formed, free from cracks, blow holes and other irregularities. All sharp edges shall be ground smooth.

14.2.6 All seams shall be sealed with RTV sealant or equivalent material on the interior of the cabinet.

14.2.7 All cabinets shall be supplied with two removable shelves manufactured from 5052-H32 aluminum. Shelf shall be a minimum of 10 inches deep.

14.2.8 One set of vertical "C" channels shall be mounted on each interior wall of the cabinet for the purpose of mounting the cabinet components. The channels shall accommodate spring mounted nuts or studs. All mounting rails shall extend to within 7 inches of the top and bottom of the cabinets.

14.2.9 The main door and police door-in-door shall close against a weatherproof and dust-proof, closed-cell neoprene gasket seal. The gasket material for the main door shall be a minimum of 0.188 inches thick by 1.00 inch wide. The gasket material for the police door shall be a minimum of 0.188 inches thick by 0.500 inches wide. The gaskets shall be permanently bonded to the cabinet.

14.2.10 The lower section of the cabinet shall be equipped with a louvered air entrance. The air inlet shall be large enough to allow sufficient air flow per the rated fan capacity. Louvers must satisfy the NEMA rod entry test for 3R ventilated enclosures. A non-corrosive, vermin- and insect-proof, removable air filter shall be secured to the air entrance. The filter shall fit snugly against the cabinet door wall.

14.2.11 The roof of the cabinet shall incorporate an exhaust plenum with a vent screen. Perforations in the vent screen shall not exceed 0.125 inches in diameter.

14.2.12 The main door shall be equipped with a three-point latching mechanism.

14.2.13 The handle on the main door shall utilize a shank of stainless steel 3/4 inches minimum diameter. The handle shall include a hasp for the attachment of an optional padlock. The cabinet door handle shall rotate clockwise to open. The lock assembly shall be positioned so that the handle shall not cause any interference with the key when opening the cabinet door.

14.2.14 The main door hinge shall be a one-piece, continuous piano hinge with a stainless steel pin running the entire length of the door. The hinge shall be attached in such a manner that no rivets or bolts are exposed.

14.2.15 The main door shall include a mechanism capable of holding the door open at approximately 90, 120, and 180 degrees under windy conditions.

14.2.16 The main door shall be equipped with a Corbin tumbler lock number 1548-1. Two keys shall be supplied.

14.2.17 The police door-in-door shall be provided with a trea­sury type lock Corbin No. R357SGS or exact equivalent and one key.

14.2.18 Each cabinet shall be of sufficient size to accommodate all equipment. At a minimum, the cabinet sizes are as follows:

- Size 5 (M) cabinets - 51" H x 32" W x 18" D
- Size 6 (P) cabinets - 56" H x 44" W x 24" D
Note: Height measured at front of cabinet.

14.2.19 Size 5 cabinets shall be suitable for base, pole or pedestal mounting. Size 6 cabinets shall be base mounted only.

14.2.20 All base mounted cabinets shall be supplied with anchor bolts to properly secure the cabinet to its base. The cabinet flange for securing the anchor bolts shall not protrude outward from the bottom of the cabinet. When a size 5 cabinet is to be base mounted it shall be furnished with two anchor bolts. Size 6 cabinets shall be provided with four anchor bolts.

14.2.21 Size 5 cabinets shall also be suitable for pole or pedestal mounting. When a pole mounted cabinet is requested, the cabinet shall be supplied with a bottom panel, back wall reinforcing and mounting hardware. When a pedestal mounted cabinet is requested, the cabinet shall be supplied with a reinforced bottom panel and mounting hardware.

14.3 TERMINALS AND FACILITIES/MAIN PANEL DESIGN AND CON­STRUCTION

14.3.1 The main panel shall be constructed from 5052-H32 brushed aluminum of 0.125 inches minimum thickness and formed so as to eliminate any flexing when plug-in components are installed.

14.3.2 The main panel shall be fully wired in the following configurations:

      1. Size 5 Cabinet - Twelve load switch sockets, six flash transfer relay sockets, one flasher socket, three main panel BIU rack slots and two eight slot detector racks (compatible with TS2 Detector Rack Configuration 2).
      2. Size 6 Cabinet - Sixteen load switch sockets, eight flash transfer relay sockets, one flasher socket, three main panel BIU rack slots, two eight slot detector racks (compatible with TS2 Detector Rack Configuration 2) and one four slot detector rack (compatible with TS2 Detector Rack configuration 1).

14.3.3 All 12 and 16 position main panels shall be hinged at the bottom to allow easy access to all wiring on the rear of the panel. It shall not be necessary to remove any shelf-mounted equipment to hinge down the main panel.

14.3.4 All load switch and flash transfer relay socket refer­ence designators shall be silk-screen labeled on the front and rear of the main panel to match drawing designations.

14.3.5 Up to eight load switch sockets may be positioned horizontally or stacked in two rows on the main panel. Main panels requiring more than eight load switch sockets shall be mounted in two horizontal rows.

14.3.6 All load switches shall be supported by a bracket extending at least three inches from the main panel.

14.3.7 Rack style mounting shall be provided to accommodate the required BIUs per the configuration listed in sec­tion 3.2 above. A dual-row, 64‑pin female DIN 41612 Type B connector shall be provided for each BIU rack position. Card guides shall be provided for both edges of the BIU. Terminal and facilities BIU mounting shall be an integral part of the main panel. Detector rack BIU mounting shall be an integral part of the shelf-mounted detector rack.

14.3.7.1 All BIU rack connectors shall have prewired address pins corresponding to the requirements of the TS2 specification. The address pins shall control the BIU mode of operation. BIUs shall be capable of being interchanged with no additional programming.

14.3.8 All main panels shall have all field wires contained within one row of horizontally-mounted terminal blocks.

14.3.9 All field output circuits shall be terminated on an unfused compression type terminal block with a minimum rating of 10 amps.

14.3.10 All field input/output (I/O) terminals shall be identi­fied by permanent alphanumeric labels. All labels shall use standard nomenclature per the NEMA TS2 speci­fication.

14.3.11 All field flash sequence programming shall be accom­plished at the field terminals with the use of a screw­driver only.

14.3.12 Field terminal blocks shall be wired to use three posi­tions per vehicle, pedestrian or overlap phase (green, yellow, red)

14.3.13 The main panel shall contain a flasher socket (silk screen labeled) capable of operating a 15‑amp, 2‑pole, NEMA solid state flasher. The flasher shall be supported by a bracket that extends at least three inches from the backpanel.

14.3.14 One RC network shall be wired in parallel with each flash transfer relay coil.

14.3.15 All logic-level, NEMA-controller and Malfunction Man­agement Unit input and output terminations on the main panel shall be permanently labeled. Cabinet prints shall identify the function of each terminal position.

14.3.16 Terminal blocks for DC signal interfacing shall have a number 6-32 x 7/32 inch screw as minimum. Functions to be terminated shall be as specified in the listing of input/output Terminals in the TS2-1992 Standard document (Section 5).

14.3.17 All main panel wiring shall conform to the following wire size and color:

Green/Walk load switch output - brown wire
- 16 gauge
Yellow load switch output - yellow wire
- 16 gauge
Red/Don't Walk load switch - red wire output
- 16 gauge
MMU (other than AC power) - blue wire
- 22 gauge
Controller I/O
- blue wire
- 22 gauge
AC Line (power panel to - black wire main panel)
- * AC Line (main panel) - black wire
- * AC Neutral (power panel to - white wire main panel)
- * AC Neutral (main panel) - white wire
- * Earth ground - green wire
- *
* gauge varies with power panel/ main panel set

14.3.18 All wiring, 14 AWG and smaller, shall conform to MIL‑W‑16878/1, type B/N, 600V, 19-strand tinned cop­per. The wire shall have a minimum of 0.010 inches thick PVC insulation with clear nylon jacket and rated to 105 degrees Celsius. All 12 AWG and larger wire shall have UL listed THHN/THWN 90 de­grees Celsius, 600V, 0.020 inches thick PVC insula­tion and clear nylon jacketed.

14.3.19 All controller and Malfunction Management Unit cables shall be of sufficient length to allow the units to be placed on either shelf or the outside top of the cabi­net in the operating mode. Connect­ing cables shall be sleeved in a braided nylon mesh. The use of exposed tie-wraps or interwoven cables are unacceptable.

14.3.20 All cabinet configurations shall be provided with enough RS-485 Port 1 communication cables to allow full capabilities of that cabinet. Each communica­tion cable connector shall be a 15‑pin metal shell D subminiature type. The cable shall be a shielded cable suitable for RS-485 communications.

14.3.21 All main panels shall be pre-wired for a Type-16 Mal­function Management Unit.

14.3.22 All wiring shall be neat in appearance. All cabi­net wiring shall be continuous from its point of origin to its termination point. Butt type connec­tions/splices are not acceptable.

14.3.23 All connecting cables and wire runs shall be se­cured by mechanical clamps.

14.3.24 The grounding system in the cabinet shall be divided into three separate circuits (AC Neutral, Earth Ground, and Logic Ground). These ground circuits shall be connect­ed together at a single point as outlined in the NEMA TS2 Standard.

14.3.25 All pedestrian pushbutton inputs from the field to the controller shall be optoisolated through the BIU and operate at 12 VAC.

14.3.26 All wire (size 16 AWG or smaller) at solder joints shall be hooked or looped around the eyelet or terminal block post prior to soldering to ensure circuit integrity. Lap joint soldering is not acceptable.

14.3.27 The main panel shall be provided with output terminals for all of the preemption outputs of the CU. The preemption terminal shall be wired to a relay panel which will provide 120 VAC to illuminate telltale lights when preemption is active.

14.4 POWER PANEL DESIGN AND CONSTRUCTION

14.4.1 The power panel shall consist of a separate module, securely fastened to the right side wall of the cabinet. The power panel shall be wired to provide the necessary power to the cabi­net, controller, Malfunction Management Unit, cabi­net power supply and auxiliary equipment. It shall be manufactured from 0.090-inch, 5052-H32 aluminum. All cabinet wiring shall be sized in accordance with NEC requirements. A 5 amp circuit breaker shall protect all line voltage cabinet wiring of #16 AWG or less.

14.4.2 The power panel shall house the following compo­nents:

      1. A 50-amp main breaker for 12 or 16 position cabi­nets. This breaker shall supply power to the controller, MMU, sig­nals, cabinet power supply and auxiliary panels. Breakers shall be thermal mag­netic type, with a minimum of 10,000 amp inter­rupting capacity. The cabinets shall also be provided with two double pole 20 ampere load bay circuit breakers. The cabinets shall be wired so that the load is essentially equally shared, i.e. with phases 1, 2, 5, and 6 and overlaps A and C on one breaker pole. Phases 3, 4, 7, and 8 and overlaps B and D on the other breaker pole.
      2. A 15-amp auxiliary breaker. This breaker shall supply power to the fan, light and GFI outlet.
      3. A 60 amp, 125 VAC radio interference line filter.
      4. A mercury displacement relay shall be used to interrupt power to load switch bay during flashing operation. This relay shall be a minimum of 60 ampere tungsten load continuous duty, full load rated from -35 C to 60 C ambient temperature. A surge suppression RC network and MOV shall be installed in parallel with the relay coil.
      5. A 13-position neutral bus bar capable of connecting three #12 wires per position.

14.4.3 All cabinet breakers shall be listed by an appropriate testing agency, as defined by the NEC.

14.4.4 The following separate ground connections shall be provided:

      1. Ground bus for driven ground, cabinet frame and equipment grounds (green wiring).
      2. Neutral bus for 120 VAC neutral connections for all line operated equipment (white wiring).
      3. Logic ground for all logic level signals (brown/white wiring).
        These circuits shall remain totally insulated from each other, and shall be bonded only at the AC power input.

14.5 AUXILIARY CABINET EQUIPMENT

14.5.1 The cabinet shall be provided with a thermostatically controlled (adjustable between 80-150 degrees Fahren­heit) venti­lation fan in the top of the cabinet plenum. The fan shall be a ball bearing type fan and shall be capable of drawing a minimum of 100 cubic feet of air per min­ute. The fan shall be provided with elctro-magnetic surge suppression consisting of at least an RC network (.1UF 600 V, 47 Ohms) or MOV across the coil.

14.5.2 An incandescent lamp and socket shall be mounted in the cabinet to sufficiently illuminate the field terminals. The lamp shall be wired to either a 15-amp ON/OFF tog­gle switch mounted on the rear cover of the police panel or to a door activated switch mounted near the top of the door.

Alternately, if specified by the bid document, a fluorescent lighting fixture shall be mounted on the inside top of the cabinet near the front edge. The fixture shall be rated to accommodate a F15T8 lamp. The lamp shall be wired to either a 15-amp ON/OFF toggle switch mounted on the rear cover of the police panel or to a door activated switch mounted near the top of the door.

14.5.3 A 15 amp duplex GFCI convenience outlet shall be provided in each cabinet.

14.5.4 The light and outlet circuit shall utilize 14 AWG wiring and shall be on a separate circuit breaker independent of the main breaker.

14.5.5 A sealable print pouch shall be mounted to the door of the cabinet. The pouch shall be of sufficient size to accommodate one complete set of cabinet prints.

14.5.6 Two sets of complete and accurate cabinet drawings shall be supplied with each cabinet.

14.5.7 One set of manuals for the controller and Malfunction Management Unit shall be supplied with each cabi­net.

14.6 VEHICLE DETECTION

14.6.1 A vehicle detector amplifier racks shall be provided in each cabinet as specified in Section 3.2.

14.6.2 Each cabinet shall also contain a two slot rack for preemption modules. The output from the preemption modules shall be wired to the terminals & facilities panel as per NEMA TS2 specifications.

14.6.3 Each cabinet shall contain detector interface panels for the purpose of connecting field loops and vehicle detector amplifiers. The panels shall be manufactured from .090 minimum thickness 5052-H32 aluminum.

14.6.4 The interface panel shall contain terminal facilities for all detector and preemption channels provided in the cabinet. The terminals for each channel shall be wired independently of one another.

14.6.5 A ground bus terminal shall be provided between each loop pair ter­minals to provide a termination for the loop lead-in cable ground wire.

14.6.6 Lightning protection device mounting holes shall be provided to accommodate an EDCO SRA-16C, or EDCO SRA-6, or EDCO LCA-6, or a varistor lightning protection de­vice. Lightning protection devices shall not be pro­vided unless specifically called for on the intersection plans.

14.6.7 A cable consisting of 22 AWG twisted pair wires (red and orange) shall be provided to connect from the panel to a detector rack.

14.6.8 All termination points shall be identified by a unique number and silk screened on the panel. The identification number shall identify the rack slot and channel.

14.6.9 Each detector rack shall be powered by the cabinet power supply (refer to section 9.6 of this specifica­tion).

14.7 CABINET TEST SWITCHES AND POLICE PANEL

14.7.1 A test switch panel shall be mounted on the inside of the main door. The test switch panel shall provide as a mini­mum the following:

      1. AUTO/FLASH SWITCH. When in the flash posi­tion, power shall be maintained to the con­troller and the in­tersection shall be placed in flash. The con­troller shall not be stop timed when in flash. If required by the plans and specifications, an op­tional RC network shall be provid­ed to give the controller an external start pulse when switch is returned to the auto position. This will force the controller to initiate the start up sequence when exiting flash.
      2. STOP TIME SWITCH. When applied, the controller shall be stop timed in the current interval.
      3. CONTROL EQUIPMENT POWER ON/OFF. This switch shall control the con­troller, MMU, and cabinet power supply AC power.

Momentary test pushbuttons for all vehicle and pedes­trian inputs to the controller are not re­quired. The TS2 controller to be provided with the cabinet assembly shall provide vehicular and pedestrian call inputs from its keyboard while in the standard status display.

14.7.2 The police door switch panel shall contain the follow­ing:

      1. SIGNALS ON/OFF SWITCH. In the OFF position, power shall be removed from signal heads in the intersec­tion. The controller shall continue to operate. When in the OFF position, the MMU shall not con­flict or require reset.
      2. AUTO/FLASH SWITCH. In the flash position, power shall not be removed from the controller and stop time shall be applied. If required by the plans and specifica­tions, an optional RC network shall be provided to give the controller an external start pulse when switch is returned to the auto position. This will force the controller to initiate the start up sequence when exiting flash.
      3. AUTO/MANUAL SWITCH. Cabinet wiring shall include provisions for an AUTO/MANUAL switch and a momen­tary pushbutton or hand cord. The AUTO/MANUAL switch and pushbutton or hand cord shall not be provid­ed unless it is called for in the special provisions of this specification.

14.7.3 All toggle type switches shall be heavy duty and rated 15 amps minimum. Single- or double-pole switches may be provided, as required. All switches shall be rated for a minimum of 30,000 operations.

14.7.4 Any exposed terminals or switch solder points shall be covered with a non-flexible shield to prevent acciden­tal contact.

14.7.5 All switch functions must be permanently and clearly labeled.

14.7.6 All wire routed to the police door-in-door and test switch pushbut­ton panel shall be adequately protected against damage from repetitive opening and closing of the main door.

14.8 CONTROLLER TELEMETRY INTERFACE PANEL

14.8.1 A telemetry interface harness and interface panel for FSK communications over twisted pair cable shall be supplied with each cabinet assembly.

14.8.2 The harness shall be a minimum of 6 feet long and shall consist of two twisted pairs, 22 AWG wire, terminated to a 9-pin "D" type connector at one end. The pin out of the 9‑pin connector shall be in exact accordance with the NEMA TS2 Standard. The opposite end of the har­ness shall be terminated on a 10-position EDCO PCB-1B or exact equal lightning protection socket base.

14.8.3 The interface panel shall be equipped with a 50 row, 6 position 66 block. Each row shall have three two position clips.

14.8.4 A harness, consisting of two twisted pairs, 22 AWG wire shall be provided for connecting the active communications pairs on the 66 block to the lightning protection base specified in Section 8.2.

14.8.5 All terminal block designations and peripheral board-mounted components shall be labeled as to their number and function and shall correspond to the cabinet wiring diagrams.

14.8.6 The following signals shall be accessible from the teleme­try interface panel:

- Local controller command lines 1 & 2.

- Local controller readback lines 1 & 2.

- Master controller command lines 1 & 2.

- Master controller readback lines 1 & 2.

- Earth grounds.

14.8.7 A socket mounted communication line transient protec­tion device shall be supplied with the telemetry inter­face panel. The device shall be an EDCO model PC642C-008D or exact approved equivalent. The transient pro­tection device shall be wired in series with the telem­etry communication circuit.

14.9 AUXILIARY DEVICES

14.9.1 Load Switches

14.9.1.1 Load switches shall be solid state and shall conform to the requirements of Section 6.2 of the NEMA TS2 Stan­dard.

14.9.1.2 Signal load switches shall have a minimum rating of 15 amperes at 120 VAC for an incandescent lamp load. Triac switching devices shall be rated at 600 volts minimum, and have a design life of at least five (5) years.

14.9.1.3 The front of the load switch shall be provided with three indicators to show the input signal from the controller to the load switch.

14.9.1.4 Load switches shall be dedicated per phase. The use of load switches for other partial phases is not accept­able.

14.9.1.5 The full complement of load switches shall be supplied with each cabinet to allow for maximum phase utiliza­tion for which the cabinet is designed (unless otherwise specified by the bid document).

14.9.2 Flasher

14.9.2.1 The flasher shall be solid state and shall conform to the requirements of section 6.3 of the NEMA TS2 Stan­dard.

14.9.2.2 Flashing of field circuits for the purpose of intersec­tion flash shall be accomplished by a separate flasher.

14.9.2.3 The flasher shall be rated at 15 amperes, double pole with a nominal flash rate of 60 FPM.

14.9.2.4 Wiring shall be provided to assign any phase to either circuit of the flasher.

14.9.3 Flash Transfer Relays

14.9.3.1 All flash transfer relays shall meet the requirements of Section 6.4 of the NEMA TS2 Standard.

14.9.3.2 The coil of the flash transfer relay must be deener­gized for flash operation.

14.9.3.3 The full complement of relays shall be supplied with each cabinet to allow for maximum phase utilization for which the cabinet is designed (unless modified by the bid document).

14.9.3.4 The flash transfer relays shall have surge suppression MOV connected in parallel with each of their coils.

14.10 MALFUNCTION MANAGEMENT UNITS

This specification sets forth the minimum requirements for a shelf-mountable, sixteen channel, solid-state Malfunction Management Unit (MMU). The MMU shall meet, as a minimum, all applicable sections of the NEMA Stan­dards Publication No. TS2‑1992. An independent testing laboratory shall verify that the MMU will perform all its defined functions under the conditions set forth in Section 2 of the NEMA STANDARD (Environmental Standards and Test Procedures). Where differences occur, this specification shall govern.

14.10.1 Enclosure

14.10.1.1 The MMU shall be compact so as to fit in limited cabinet space. It shall be installed on a shelf that is at least 7" deep. Overall dimensions, including mating connectors and harness, shall not exceed 10.5" x 4.5" x 11" (H x W x D).

14.10.1.2 The enclosure shall be constructed of sheet aluminum with a minimum thickness of 0.062", and shall be fin­ished with an attractive and durable protective coating. Model, serial number, and program information shall be permanently displayed on the rear surface.

14.10.2 Electronics

14.10.2.1 A microprocessor shall be used for all timing and con­trol functions. Continuing operation of the microproces­sor shall be verified by an independent monitor circuit, which shall force the OUTPUT RELAY to the de-energized "fault" state and indicate an error message if a pulse is not received from the microprocessor within a defined period.

14.10.2.2 In the interest of reliability, only the PROM memory device for the microprocessor firmware shall be socket mounted. The PROM Memory socket shall be a precision screw machine type socket with a gold contact finish providing a reliable gas tight seal. Low insertion force sockets or sockets with "wiper" type contacts shall not be acceptable.

14.10.2.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. Failure of the internal power supply to provide proper operating voltages shall force the OUTPUT RELAY to the de-energized "fault" state and indicate an error mes­sage. A front panel mounted fuse shall be provided for the 120 VAC input.

14.10.2.4 User-programmed configuration settings shall be stored in an electrically erasable programmable read-only memory (EEPROM) or via front panel DIP switches. Designs using a battery to maintain configuration data shall not be acceptable.

14.10.2.5 All 120 VAC field terminal inputs shall provide an input impedance of at least 150K ohms and be terminated with a resistor having a power dissipation rating of 0.5 Watts or greater. Each 120 VAC field terminal input shall be sensed by a separate precision voltage comparator de­vice.

14.10.2.6 All electrical components used in the MMU shall be rated by the component manufacturer to operate over the full NEMA temperature range of -30 deg C to +74 deg C.

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

      1. All plated-through holes and exposed circuit traces shall be plated with solder.
      2. Both sides of the printed circuit board shall be covered with a solder mask material.
      3. 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 desig­nated on both sides of all printed circuit boards.
      4. All electrical mating surfaces shall be gold plated.
      5. All printed circuit board assemblies shall be coated on both sides with a clear moisture-proof and fungus-proof sealant.

14.10.3 Front Panel & Connectors

14.10.3.1 All displays, configuration switches, and connectors shall be mounted on the front panel of the MMU. All MMU configuration inputs beyond those required by the NEMA Standard shall be provided by front panel mounted DIP switches and shall be clearly labeled. Configuration DIP switches shall be provided for the following functions:

          1. Field Check / Dual Enables 1-16
          2. Green/Yellow-Dual Indication Enable
          3. BND Test Disable
          4. External Watchdog Enable

14.10.3.2 The connectors on the MMU shall have a metallic shell and be attached to the chassis internally. They shall be manufactured to meet MIL-C-26482 specifications. The connectors shall be mounted on the front of the unit in accordance with the following: Connector A shall inter­mate with a MS 3116 22-55 SZ, and Connector B shall intermate with a MS 3116 16-26 S.

In the interest of reliability and repairability, printed circuit board mounted MS connectors shall not be acceptable. Internal MS harness wire shall be a minimum of AWG #22, 19 strand. Wiring between the MS connector and pc boards shall be soldered. Friction or crimp style connectors are not acceptable

14.10.3.3 All indicator lights shall be water clear, T‑1 package, Red Super Bright type LEDs. Indicators shall be provided for the following items:

        1. Channel Status 1-16
        2. Conflict
        3. Red Fail
        4. CVM / External Watchdog
        5. 24V-2
        6. 24V-1
        7. Clearance Fail
        8. Port 1 Fail
        9. Diagnostic / Program Card
        10. Field Check Fail
        11. Dual Indication
        12. Type 12 mode
        13. Power
        14. Port 1 Receive
        15. Port 1 Transmit

14.10.4 Operating Modes

14.10.4.1 The MMU shall operate in both the Type 12 mode and Type 16 mode as required by the NEMA Standard.

14.10.5 Monitoring Functions

14.10.5.1 The following monitoring functions shall be provided in addition to those required by the NEMA Standard Section 4.

14.10.6 Dual Indication Monitoring

14.10.6.1 Sixteen switches labeled FIELD CHECK/DUAL ENABLES shall be provided on the MMU front panel to enable Dual Indi­cation Monitoring on a per channel basis. The Dual Indi­cation Monitor function shall provide two modes of oper­ation, Dual Indication Fault and Green/Yellow-Dual Indi­cation Fault.

14.10.6.2 When voltages on two inputs of a channel are sensed as active for more than 1000 msec, the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the DUAL INDICATION indi­cator. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. When voltages on two inputs of a channel are sensed as active for less than 700 msec, the MMU shall not transfer the OUTPUT relay contacts to the Fault position.

14.10.6.3 When operating in the Type 16 mode with Port 1 communi­cations enabled, Bit #68 (Spare Bit #2) of the Type #129 response frame shall be set to indicate a Dual Indica­tion fault has been detected.

14.10.6.4 Dual Indication Monitoring shall be disabled when the RED ENABLE input is not active. When operating in the Type 16 mode with Port 1 communications enabled, Dual Indication Monitoring shall also be disabled if the LOAD SWITCH FLASH bit is set to "1" in the Type #0 message from the Controller Unit.

14.10.7 Dual Indication Monitor

14.10.7.1 Dual Indication monitoring shall detect simultaneous input combinations of active Green (Walk), Yellow, or Red (Don’t Walk) field signal inputs on the same channel. In Type 12 mode this monitoring function detects simul­taneous input combinations of active Green and Yellow, Green and Red, Yellow and Red, Walk and Yellow, or Walk and Red field signal inputs on the same channel.

14.10.8 Green Yellow-Dual Indication Monitor

14.10.8.1 Green Yellow-Dual Indication monitoring shall detect simulta­neous inputs of active Green and Yellow field signal inputs on the same channel. It will be used to monitor channels which have an unused Red field signal input tied to AC LINE such as a five section signal head.

14.10.8.2 Green Yellow‑Dual Indication Monitoring shall be enabled by a front panel option switch. When the Green Yellow‑Dual Indica­tion Monitoring option is enabled, all channels which have the front panel FIELD CHECK/DUAL ENABLE switches OFF shall be individually monitored for simul­taneous active Green and Yellow field signal in­puts. All chan­nels which have the front panel FIELD CHECK/DUAL ENABLE switches ON (i.e., enabled for Dual Indication Monitoring) shall function as described above in Dual Indication Monitoring.

14.10.9 Field Check Monitoring

14.10.9.1 Sixteen switches labeled FIELD CHECK/DUAL ENABLES shall be provided on the MMU front panel to enable Field Check Monitoring on a per channel basis. The Field Check Moni­tor function shall provide two modes of operation, Field Check Fault and Field Check Status.

14.10.9.2 Field Check Monitoring shall be disabled when the RED ENABLE input is not active. When operating in the Type 16 mode with Port 1 communications enabled, Field Check Monitoring shall also be disabled if the LOAD SWITCH FLASH bit is set to "1" in the Type #0 message from the Controller Unit. The Field Check Monitoring function shall be disabled in the Type 12 mode.

14.10.9.3 Field Check Monitor

In the Field Check Fault mode, when the field signal input states sensed as active or inactive by the MMU do not correspond with the data provided by the Controller Unit in the Type #0 message for 10 consecutive messages, the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the FIELD CHECK FAIL indicator. The Channel Status Display shall indicate the channels on which the Field Check fault was detected. Bit #67 (Spare Bit #1) of the Type #129 response frame shall be set to indicate a Field Check fault has been detected. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input.

14.10.9.4 Field Check Status

The Field Check Status mode shall work in combination with the other fault monitoring functions of the MMU. When a Conflict, Red Fail, Clearance Fail, or Dual Indi­cation Fail triggers the MMU, the Channel Status Display and Fault Status Display shall correspond to that de­tected fault. If Field Check errors were detected while the fault was being timed, the FIELD CHECK FAIL indica­tor shall illuminate and double pulse once every 2 sec­onds. The channels on which the Field Check errors were detected shall double pulse at the same time as the FIELD CHECK FAIL indicator. Bit #67 (Spare Bit #1) of the Type #129 response frame shall also be set to indi­cate Field Check errors have been detected.

14.10.10 BND Error Detection Monitoring

14.10.10.1 The BND Error Detection function shall be designed to detect and respond to irregular field input waveforms such as: irregularly blinking (flickering); having con­stant extraneous noise; being dimmed invalidly under Controller Unit software control.

14.10.10.2 Detection of a BND Error shall place the MMU into the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the BND FAIL indicator. The Channel Status display shall indicate the channels on which the fault occurred. When operating in the Type 16 mode with Port 1 communications enabled, Bit #69 (Spare Bit #3) of the Type #129 response frame shall be set to indicate a BND Error Detection fault has been detected. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the BND Fail fault state of the monitor.

14.10.11 External Watchdog Monitor

14.10.11.1 The MMU shall provide the capability to monitor an op­tional external logic level output from a Controller Unit or other external cabinet circuitry. If the MMU does not receive a change in state on the EXTERNAL WATCHDOG input for 1500 msec (100 msec), the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the CVM/WATCHDOG indicator. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the CVM/WATCHDOG fault state of the monitor.

14.10.11.2 When operating in the Type 16 mode with Port 1 communi­cations enabled, Bit #70 (Spare Bit #4) of the Type #129 response frame shall be set to indicate an External Watchdog fault has been detected.

14.10.12 Type Fault Monitor

14.10.12.1 The MMU shall verify at power-up that the Type 12 or Type 16 operating mode as determined by the TYPE SELECT input is consistent with the mode set by the last exter­nal reset.

14.10.12.2 Detection of a Type Fault shall place the MMU into the fault mode, transfer the OUTPUT relay contacts to the Fault position, illuminate the DIAGNOSTIC indicator, and flash the TYPE 12 indicator at a 2Hz rate. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the Type Fault state of the monitor.

14.10.13 Display Functions

The following display functions shall be provided in addition to those required by the NEMA Standard Section 4.

14.10.14 Yellow Plus Red Clearance Interval Display

The MMU Channel Status display shall indicate with a steadily illuminated LED indicator, those channels which had the short Yellow plus Red interval (i.e., those channels which did not meet the minimum Yellow Change plus Red Clearance Interval). The conflicting channel(s) which was sensed active Green causing the Minimum Yellow Change plus Red Clearance Fault shall also be indicated with a single pulsed LED indicator.

14.10.15 Field Check Status Display

14.10.15.1 The FIELD CHECK FAIL indicator shall illuminate when a Field Check Fault is detected. The Channel Status dis­play shall show the channels on which the Field Check fault occurred.

14.10.15.2 If Field Check errors occurred during a Conflict Fault, Red Fail, Clearance Fail, or Dual Indication Fail the FIELD CHECK FAIL indicator shall illuminate and double pulse every 2 seconds. The channels on which the Field Check Status was detected during the fault shall double pulse on the Channel Status Display at the same time as the FIELD CHECK FAIL indicator.

14.10.16 Display Indicators

The following display indicators shall be provided in addition to those required by the NEMA Standard Section 4.

14.10.16.1 Type 12 Mode Indicator

The TYPE 12 indicator shall illuminate when the MMU is programmed for Type 12 operation. If a Type Fault is detected the DIAGNOSTIC/PGM CARD indicator shall illumi­nate and the TYPE 12 indicator shall flash at a rate of 2Hz.

14.10.16.2 BND Fail Indicator

The BND FAIL indicator shall illuminate when a BND Fault is detected. The Channel Status display shall show the channels which were detected as BND Fail.

14.10.16.3 Dual Indication Indicator

The DUAL INDICATION indicator shall illuminate when a DUAL INDICATION Fault is detected. The Channel Status display shall show the channels which were detected as DUAL INDICATION.

14.10.16.4 Power Indicator

The POWER indicator shall flash at a rate of 2Hz when the AC LINE voltage is below the drop‑out level. It shall illuminate steadily when the AC LINE voltage re­turns above the restore level.

14.10.16.5 Port 1 Receive Indicator

The RECEIVE indicator shall illuminate for a 33 msec pulse each time a Port 1 message is correctly received from the Controller Unit.

14.10.16.6 Port 1 Transmit Indicator

The TRANSMIT indicator shall illuminate whenever the MMU has the Port 1 transmitter enabled.

14.10.16.7 Program Card Indicator

The DIAGNOSTIC/PGM CARD indicator shall flash at a 2Hz rate if the Programming Card is absent or not seated properly in its mating connector.

14.10.17 Additional Features

14.10.17.1 The MMU shall include both automatic and operator initi­ated diagnostics.

14.10.17.2 Automatic diagnostics shall verify memory and micropro­cessor operation each time power is reapplied to the MMU. After power has been applied, diagnostics shall continually verify the operation of essential elements of the MMU including at a minimum: PROM, EEPROM, commu­nications, internal power supply, and the microproces­sor.

14.10.17.3 Operator initiated diagnostics shall allow the operator to verify proper operation of all indicator lights, PROM, EEPROM, RAM, and microprocessor.

14.11 BUS INTERFACE UNITS

14.11.1 All Bus Interface Units (BIUs) shall meet the require­ments of Section 8 of the NEMA TS2 Standard.

14.11.2 The full complement of BIUs shall be supplied with each cabi­net to allow for maximum phase and func­tion utilization for which the cabinet is de­signed.

14.11.3 Each Bus Interface Unit shall include power on and trans­mit indicators. All indicators shall be LEDs.

14.12 CABINET POWER SUPPLY

14.12.1 TS2 compliance

This specification sets forth the minimum requirements for a TS2 cabinet power supply that is AC line powered and pro­vides regulated DC power, unregulated AC power and a line frequency reference for TS2 detector racks, Bus Interface Units, load switches, and auxiliary cabinet equipment. As a minimum, the power supply shall meet all requirements of Section 5.3.5 of the NEMA TS2‑1992 Standard plus all other applicable sections of the Standard.

14.12.2 Mechanical

The power supply shall be compact to fit in limited cabinet space. External dimensions shall not exceed 6" x 5.75" x 8.4" (H x W x D) including connectors and protrusions. The power supply shall be mountable on a shelf or, alternately, be wall‑mountable via holes in its rear cover. The power supply enclosure shall be constructed of sheet aluminum.

14.12.3 Electrical

14.12.3.1 Printed Circuit Board

The power supply shall not use more than one printed circuit board. This board shall be made of NEMA FR‑4 glass epoxy or equivalent. Multi-layered pc boards will not be acceptable. Exposed circuit traces shall be plated with solder. The designation of all components and the polarity of all capacitors and diodes shall be clearly marked adjacent to the component.

14.12.3.2 Power Supply Design

In the interest of immunity to variations in incoming AC line voltage, the power supply design shall be based on the use of integrated-circuit voltage regulators for the 12 and 24 volt D.C. supplies.

14.12.3.3 Environmental

The power supply shall meet all applicable requirements from Section 2 of the TS2‑1992 Standard, which covers AC power, temperature, humidity, transients, shock and vibration. These requirements include operation from 89 to 135 VAC power, 60 Hz + 3 Hz. The operating temperature shall be ‑34oC (‑30oF) to +74oC (+165oF).

14.12.3.4 Electrical Outputs

14.12.3.4.1 Electrical outputs shall be as specified in Section 5.3.5.2 of the TS2‑1992 Standard. Outputs shall be as follows:

- +12 VDC + 1 VDC, 2.0 A

- +24 VDC + 2 VDC, 2.0 A

- 12 VAC, 0.25 A

- 60 Hz Line Frequency Reference

14.12.3.4.2 Regulation of DC outputs within the specified limits and DC ripple not exceeding 0.5 V peak‑to‑peak shall be maintained over an AC line variation from 89 to 135 VAC and a load vari­ation from 1/8 load to full load. The 12 VAC output shall be referenced to AC Neutral. It shall be unregulated, but shall not be less than 7.5 VAC at 89 VAC power.

14.12.3.4.3 The line frequency output shall be False when the 60 Hz line is within its negative half cycle and then source a minimum of 50 mA at nominal 24 VDC. It shall be True when the 60 Hz line is within its positive half cycle and then sink a mini­mum of 50 mA. The rise and fall times shall be no greater than 50 microseconds when switching a 10,000 pF load capa­citance.

14.12.3.5 Input & Output Connections

14.12.3.5.1 The power supply connector shall be located on the front panel of the power supply. It shall have a metallic shell connected to chassis ground and mate with an MS3106‑18‑1SW cable connector or equivalent. Pin terminations shall be as follows:

        1. AC Neutral
        2. Line Frequency Reference
        3. AC line
        4. +12 VDC Output
        5. +24 VDC Output
        6. Reserved
        7. Logic Ground
        8. Earth Ground
        9. 12 VAC Output
        10. Reserved

14.12.3.5.2 The AC power input shall be protected against over‑current with a2 amp. slow-blow fuse.

14.12.3.6 Indicators and Test Points

14.12.3.6.1 Three LED indicator lights shall be provided on the front panel of the power supply to indicate the presence of voltage. Outputs with a matching LED indicator light shall be 12 VAC, 24 VDC and 12 VDC.

14.12.3.6.2 Banana jack test points for +24 VDC and Logic Ground shall be provided on the front panel of the power supply.

14.12.3.7 Test and Warranty

14.12.3.7.1 The power supply shall be thoroughly tested to insure com­pli­ance with this specification. Upon completion of initial tests, the unit shall be burned in at 74oC for 48 hours. It shall be retested following burn‑in.

14.12.3.7.2 The power supply shall be warranted to meet this specifi­cation at the time of delivery. It shall be warranted by the supplier against mechanical and electrical defects for a minimum period of one (1) year from date of delivery. Any defects in design, workmanship or material shall be correct­ed by the supplier during the warranty period at no cost to the purchaser.

14.13 TESTING AND WARRANTY

14.13.1 Testing

14.13.1.1 Each cabinet assembly shall be tested as a complete entity under signal load for a minimum of 24 hours.

14.13.1.2 The cabinet shall be assembled and tested by the con­troller manufacturer or authorized local distributor to ensure proper component integration and operation.

14.13.2 Warranty

14.13.2.1 The cabinet assembly and Malfunction Management Unit shall be warranted by the manufacturer against mechanical and electrical defects for a minimum of two years from the date of receipt or one year from the date of installation, whichever comes first. The manu­facturer's warranty shall be supplied in writing with each cabinet and controller. Second party extended warranties are not acceptable.

14.13.2.2 Any minor defects will be corrected by the Utah Department of Transportation at their discretion, with the consent of the manufacturer. All other repairs under warranty will be made by the manufacturer. The manufacturer will bear all costs for making repairs under warranty including labor, parts and shipping.

14.14 METHOD OF MEASUREMENT

NEMA TS2 Type 1 Size 5, Configuration 3 and size 6, Configuration 4 Cabinet Assemblies shall be measured separately for payment by the number of units each, complete with all components provided as specified herein and delivered to the Department.

14.15 BASIS OF PAYMENT

NEMA TS2 Type 1 Size 5, Configuration 3 and Size 6, Configuration 4, Cabinet Assemblies will be paid for separately at the contract unit price each, which price shall be payment in full, for furnishing a complete Cabinet Assembly as specified herein and for all labor, equipment, transportation, and incidentals necessary to complete each item of work.


15 ITEM 15. NEMA TS2 TYPE 2 CABINET - SIZE 5, CONFIGURATION 3

15.1 All requirements for the NEMA TS2 TYPE 2 Cabinet - Size 5, CONFIGURATION 3, are described in ITEM 16, NEMA TS2 TYPE 2 CABINET - SIZE 6, CONFIGURATION 4, of this RFP, below.


16 ITEM 16. NEMA TS2 TYPE 2 CABINET - SIZE 6, CONFIGURATION 4

16.1 GENERAL

16.1.1 This specification sets forth the minimum requirements for a TS2 Type 2 traffic control cabinet assembly. The cabinet assembly shall meet, as a minimum, all applica­ble sections of the NEMA Standard Publication No. TS2-1992. Where differences occur, this specification shall govern.

16.2 CABINET DESIGN AND CONSTRUCTION

16.2.1 The cabinet shall be constructed from type 5052-H32 aluminum with a minimum thickness of 0.125 inches.

16.2.2 The cabinet shall be designed and manufactured with materials that will allow rigid mounting, whether intended for pole, base or pedestal mount­ing. The cabinet must not flex on its mount.

16.2.3 A rain channel shall be incorporated into the design of the main door opening to prevent liquids from entering the enclosure. The cabinet door opening must be a minimum of 80 percent of the front surface of the cabinet.

16.2.4 The top of the cabinet shall incorporate a 1-inch slope toward the rear to prevent rain accumulation.

16.2.5 Unless otherwise specified, the cabinet shall be sup­plied with a natural aluminum finish. Sufficient care shall be taken in handling to ensure that scratches are minimized. All surfaces shall be free from weld flash. Welds shall be smooth, neatly formed, free from cracks, blow holes and other irregularities. All sharp edges shall be ground smooth.

16.2.6 All seams shall be sealed with RTV sealant or equivalent material on the interior of the cabinet.

16.2.7 All cabinets shall be supplied with two removable shelves manufactured from 5052-H32 aluminum. Shelf shall be a minimum of 10 inches deep.

16.2.8 One set of vertical "C" channels shall be mounted on each interior wall of the cabinet for the purpose of mounting the cabinet components. The channels shall accommodate spring mounted nuts or studs. All mounting rails shall extend to within 7 inches of the top and bottom of the cabinets.

16.2.9 The main door and police door-in-door shall close against a weatherproof and dust-proof, closed-cell neoprene gasket seal. The gasket material for the main door shall be a minimum of 0.188 inches thick by 1.00 inch wide. The gasket material for the police door shall be a minimum of 0.188 inches thick by 0.500 inches wide. The gaskets shall be permanently bonded to the cabinet.

16.2.10 The lower section of the cabinet shall be equipped with a louvered air entrance. The air inlet shall be large enough to allow sufficient air flow per the rated fan capacity. Louvers must satisfy the NEMA rod entry test for 3R ventilated enclosures. A non-corrosive, vermin- and insect-proof, removable air filter shall be secured to the air entrance. The filter shall fit snugly against the cabinet door wall.

16.2.11 The roof of the cabinet shall incorporate an exhaust plenum with a vent screen. Perforations in the vent screen shall not exceed 0.125 inches in diameter.

16.2.12 The main door shall be equipped with a three-point latching mechanism.

16.2.13 The handle on the main door shall utilize a shank of stainless steel 3/4 inches minimum diameter. The handle shall include a hasp for the attachment of an optional padlock. The cabinet door handle shall rotate clockwise to open. The lock assembly shall be positioned so that the handle shall not cause any interference with the key when opening the cabinet door.

16.2.14 The main door hinge shall be a one-piece, continuous piano hinge with a stainless steel pin running the entire length of the door. The hinge shall be attached in such a manner that no rivets or bolts are exposed.

16.2.15 The main door shall include a mechanism capable of holding the door open at approximately 90, 120, and 180 degrees under windy conditions.

16.2.16 The main door shall be equipped with a Corbin tumbler lock number 1548-1. Two keys shall be supplied.

16.2.17 The police door-in-door shall be provided with a trea­sury type lock Corbin No. R357SGS or exact equivalent and one key.

16.2.18 Each cabinet shall be of sufficient size to accommodate all equipment. At a minimum, the cabinet sizes are as follows:

- Size 5 (M) cabinets - 51" H x 32" W x 18" D
- Size 6 (P) cabinets - 56" H x 44" W x 24" D

Note: Height measured at front of cabinet.

16.2.19 Size 5 cabinets shall be suitable for base, pole or pedestal mounting. Size 6 cabinets shall be base mounted only.

16.2.20 All base mounted cabinets shall be supplied with anchor bolts to properly secure the cabinet to its base. The cabinet flange for securing the anchor bolts shall not protrude outward from the bottom of the cabinet. When a size 5 cabinet is to be base mounted it shall be furnished with two anchor bolts. Size 6 cabinets shall be provided with four anchor bolts.

16.2.21 Size 5 cabinets shall also be suitable for pole or pedestal mounting. When a pole mounted cabinet is requested, the cabinet shall be supplied with a bottom panel, back wall reinforcing and mounting hardware. When a pedestal mounted cabinet is requested, the cabinet shall be supplied with a reinforced bottom panel and mounting hardware.

16.3 TERMINALS AND FACILITIES/MAIN PANEL DESIGN AND CON­STRUCTION

16.3.1 The main panel shall be constructed from 5052-H32 brushed aluminum of 0.125 inches minimum thickness and formed so as to eliminate any flexing when plug-in components are installed.

16.3.2 The main panel shall be fully wired in the following configurations:

        1. Size 5 Cabinet - Twelve load switch sockets, six flash transfer relay sockets, one flasher socket, and two eight slot detector racks (compatible with TS2 Detector Rack Configuration 2).
        2. Size 6 Cabinet - Sixteen load switch sockets, eight flash transfer relay sockets, one flasher socket, two eight lot detector racks (compatible with TS2 Detector Rack Configuration 2) and one four slot detector rack (compatible with TS2 Detector Rack configuration 1).

16.3.3 All 12 and 16 position main panels shall be hinged at the bottom to allow easy access to all wiring on the rear of the panel. It shall not be necessary to remove any shelf-mounted equipment to hinge down the main panel.

16.3.4 All load switch and flash transfer relay socket refer­ence designators shall be silk-screen labeled on the front and rear of the main panel to match drawing designations.

16.3.5 Up to eight load switch sockets may be positioned horizontally or stacked in two rows on the main panel. Main panels requiring more than eight load switch sockets shall be mounted in two horizontal rows.

16.3.6 All load switches shall be supported by a bracket extending at least three inches from the main panel.

16.3.7 All main panels shall have all field wires contained within one row of horizontally-mounted terminal blocks.

16.3.8 All field output circuits shall be terminated on an unfused compression type terminal block with a minimum rating of 10 amps.

16.3.9 All field input/output (I/O) terminals shall be identi­fied by permanent alphanumeric labels. All labels shall use standard nomenclature per the NEMA TS2 speci­fication.

16.3.10 All main panels shall provide a means of programming the controller phase outputs to load switch inputs with only the use of a screwdriver.

16.3.11 Controller I/O terminals shall be configurable based on the input status of I/O mode pins (I/O Mode Bit A, A-q; I/O Mode Bit B, A-y; and I/O Mode Bit C, A-HH per Section 3.4.5.2.17 of the NEMA TS2 Standard.

16.3.12 All field flash sequence programming shall be accom­plished at the field terminals with the use of a screw­driver only. It shall also be possible to program which flasher circuit the phase shall be assigned to.

16.3.13 Field terminal blocks shall be wired to use three posi­tions per vehicle, pedestrian or overlap phase (green, yellow, red).

16.3.14 The main panel shall contain a flasher socket (silk screen labeled) capable of operating a 15‑amp, 2‑pole, NEMA solid state flasher. The flasher shall be supported by a bracket that extends at least three inches from the backpanel.

16.3.15 One RC network shall be wired in parallel with each flash transfer relay coil.

16.3.16 All logic-level, NEMA-controller and Malfunction Man­agement Unit input and output terminations on the main panel shall be permanently labeled. Cabinet prints shall identify the function of each terminal position. Inputs and outputs that are selectable by I/O mode shall be labeled as Mode (Input or Output) #1-16 or #1-10.

16.3.17 Terminal blocks for DC signal interfacing shall have a number 6-32 x 7/32 inch screw as minimum. Functions to be terminated shall be as specified in the listing of input/output Terminals in the TS2-1992 Standard document (Section 5).

16.3.18 All main panel wiring shall conform to the following wire size and color:

Green/Walk load switch output - brown wire

- 16 gauge

Yellow load switch output - yellow wire

- 16 gauge

Red/Don't Walk load switch - red wire

output - 16 gauge

MMU (other than AC power) - blue wire

- 22 gauge

Controller I/O - blue wire

- 22 gauge

AC Line (power panel to - black wire main panel)

- * AC Line (main panel) - black wire

- * AC Neutral (power panel to - white wire

main panel) - *

AC Neutral (main panel) - white wire

- *

Earth ground - green wire

- *

* gauge varies with power panel/ main panel set

16.3.19 All wiring, 14 AWG and smaller, shall conform to MIL‑W‑16878/1, type B/N, 600V, 19-strand tinned cop­per. The wire shall have a minimum of 0.010 inches thick PVC insulation with clear nylon jacket and rated to 105 degrees Celsius. All 12 AWG and larger wire shall have UL listed THHN/THWN 90 de­grees Celsius, 600V, 0.020 inches thick PVC insula­tion and clear nylon jacketed.

16.3.20 All controller and Malfunction Management Unit cables shall be of sufficient length to allow the units to be placed on either shelf or the outside top of the cabi­net in the operating mode. Connect­ing cables shall be sleeved in a braided nylon mesh. The use of exposed tie-wraps or interwoven cables are unacceptable.

16.3.21 All cabinets shall be furnished with enough cable harnesses and connectors to allow the full capabilities of the cabinet. Harness connectors shall be of the type required to intermate with their respective CU and MMU connectors.

16.3.22 All main panels shall be pre-wired for a Type-16 Mal­function Management Unit.

16.3.23 All wiring shall be neat in appearance. All cabi­net wiring shall be continuous from its point of origin to its termination point. Butt type connec­tions/splices are not acceptable.

16.3.24 All connecting cables and wire runs shall be se­cured by mechanical clamps. Stick-on type clamps are not acceptable.

16.3.25 The grounding system in the cabinet shall be divided into three separate circuits (AC Neutral, Earth Ground, and Logic Ground). These ground circuits shall be connect­ed together at a single point as outlined in the NEMA TS2 Standard.

16.3.26 The main panel shall incorporate a relay to remove +24 VDC from the common side of the load switches when the intersection is placed in flash. The relay shall have a momentary pushbutton to apply power to the load switch inputs for ease of troubleshooting.

16.3.27 All pedestrian pushbutton inputs from the field to the controller shall be optoisolated through a four circuit optical isolation card and operate at 12 VAC.

16.3.28 A 12 VAC power supply shall be incorporated on the pedestrian opto-isolation card.

16.3.29 The opto-isolation components shall be socket mounted for ease of maintenance.

16.3.30 All wire (size 16 AWG or smaller) at solder joints shall be hooked or looped around the eyelet or terminal block post prior to soldering to ensure circuit integrity. Lap joint soldering is not acceptable.

16.3.31 The main panel shall be provided with output terminals for all of the preemption outputs of the CU. The preemption terminal shall be wired to a relay panel which will provide 120 VAC to illuminate telltale lights when preemption is active.

16.4 POWER PANEL DESIGN AND CONSTRUCTION

16.4.1 The power panel shall consist of a separate module, securely fastened to the right side wall of the cabinet. The power panel shall be wired to provide the necessary power to the cabi­net, controller, Malfunction Management Unit, cabi­net power supply and auxiliary equipment. It shall be manufactured from 0.090-inch, 5052-H32 aluminum. All cabinet wiring shall be sized in accordance with NEC requirements. A 5 amp circuit breaker shall protect all line voltage cabinet wiring of #16 AWG or less.

16.4.2 The power panel shall house the following compo­nents:

        1. A 50-amp main breaker for 12 or 16 position cabi­nets. This breaker shall supply power to the controller, MMU, sig­nals, cabinet power supply and auxiliary panels. Breakers shall be thermal mag­netic type, with a minimum of 10,000 amp inter­rupting capacity.
          The cabinets shall also be provided with two double pole 20 ampere load bay circuit breakers. The cabinets shall be wired so that the load is essentially equally shared, i.e. with phases 1, 2, 5, and 6 and overlaps A and C on one breaker pole. Phases 3, 4, 7, and 8 and overlaps B and D on the other breaker pole.
        2. A 15-amp auxiliary breaker. This breaker shall supply power to the fan, light and GFI outlet.
        3. A 60 amp, 125 VAC radio interference line filter.
        4. A mercury displacement relay shall be used to interrupt power to load switch bay during flashing operation. This relay shall be a minimum of 60 ampere tungsten load continuous duty, full load rated from -35 C to 60 C ambient temperature. A surge suppression RC network and MOV shall be installed in parallel with the relay coil.
        5. A 13-position neutral bus bar capable of connecting three #12 wires per position.

16.4.3 All cabinet breakers shall be listed by an appropriate testing agency, as defined by the NEC.

16.4.4 The following separate ground connections shall be provided:

        1. Ground bus for driven ground, cabinet frame and equipment grounds (green wiring).
        2. Neutral bus for 120 VAC neutral connections for all line operated equipment (white wiring).
        3. Logic ground for all logic level signals (brown/white wiring).

These circuits shall remain totally insulated from each other, and shall be bonded only at the AC power input.

16.5 AUXILIARY CABINET EQUIPMENT

16.5.1 The cabinet shall be provided with a thermostatically controlled (adjustable between 80-150 degrees Fahren­heit) venti­lation fan in the top of the cabinet plenum. The fan shall be a ball bearing type fan and shall be capable of drawing a minimum of 100 cubic feet of air per min­ute. The fan shall be provided with elctro-magnetic surge suppression consisting of at least an RC network (.1UF 600 V, 47 Ohms) or MOV across the coil.

16.5.2 An incandescent lamp and socket shall be mounted in the cabinet to sufficiently illuminate the field terminals. The lamp shall be wired to either a 15-amp ON/OFF tog­gle switch mounted on the rear cover of the police panel or to a door activated switch mounted near the top of the door.

Alternately, if specified by the bid document, a fluorescent lighting fixture shall be mounted on the inside top of the cabinet near the front edge. The fixture shall be rated to accommodate a F15T8 lamp. The lamp shall be wired to either a 15-amp ON/OFF toggle switch mounted on the rear cover of the police panel or to a door activated switch mounted near the top of the door.

16.5.3 A 15 amp duplex GFCI convenience outlet shall be provided in each cabinet.

16.5.4 The light and outlet circuit shall utilize 14 AWG wiring and shall be on a separate circuit breaker independent of the main breaker.

16.5.5 A sealable print pouch shall be mounted to the door of the cabinet. The pouch shall be of sufficient size to accommodate one complete set of cabinet prints.

16.5.6 Two sets of complete and accurate cabinet drawings shall be supplied with each cabinet.

16.5.7 One set of manuals for the controller, vehicle detector amplifiers and Malfunction Management Unit shall be supplied with each cabi­net.

16.6 VEHICLE DETECTION

16.6.1 Vehicle detector amplifier racks shall be provided in each cabinet as specified in Section 18.3.2.

16.6.2 Each cabinet shall also contain a two slot rack for preemption modules. The output from the preemption modules shall be wired to the terminals & facilities panel as per NEMA TS2 specifications.

16.6.3 The detector rack shall be plug connected and completely removable from the cabinet without the disconnection of wires.

16.6.4 Each detector rack shall be equipped with its own power supply. Power supplies shall provide a minimum 23.2 VDC at 300 milliamperes with 120 VAC input. Power supplies shall include a minimum of 470 microfarad capacitors across each of the four output channels.

16.6.5 Each cabinet shall contain detector interface panels for the purpose of connecting field loops and vehicle detector amplifiers. The panels shall be manufactured from .090 minimum thickness 5052-H32 aluminum.

16.6.6 The interface panel shall contain terminal facilities for all detector channels provided in the cabinet. The terminals for each channel shall be wired independently of one another.

16.6.7 A ground bus terminal shall be provided between each loop pair ter­minals to provide a termination for the loop lead-in cable ground wire.

16.6.8 Lightning protection device mounting holes shall be provided to accommodate an EDCO SRA-16C, or EDCO SRA-6, or EDCO LCA-6, or a varistor lightning protection de­vice. Lightning protection devices shall not be pro­vided unless specifically called for on the intersection plans.

16.6.9 A cable consisting of 22 AWG twisted pair wires (red and orange) shall be provided to connect from the panel to a detector rack.

16.6.10 All termination points shall be identified by a unique number and silk screened on the panel. The identification number shall identify the rack slot and channel.

16.7 CABINET TEST SWITCHES AND POLICE PANEL

16.7.1 A test switch panel shall be mounted on the inside of the main door. The test switch panel shall provide as a mini­mum the following:

      1. AUTO/FLASH SWITCH. When in the flash posi­tion, power shall be maintained to the con­troller and the in­tersection shall be placed in flash. The con­troller shall not be stop timed when in flash. If required by the plans and specifications, an op­tional RC network shall be provid­ed to give the controller an external start pulse when switch is returned to the auto position. This will force the controller to initiate the start up sequence when exiting flash.
      2. STOP TIME SWITCH. When applied, the controller shall be stop timed in the current interval.
      3. CONTROL EQUIPMENT POWER ON/OFF. This switch shall control the controller, MMU, and cabinet power supply AC power.

16.7.2 A vehicle and pedestrian test panel shall be located at a convenient location inside the cabinet (not on the back of the door) equipped with a three position switch wired to each pedestrian and vehicle phase detector input permitting the substitution of manual calls into each controller phase detector input. The switch shall be labeled ON, OFF and LOCKED CALL. Locked call position to be momentary and reset to off when released.

16.7.3 The police door switch panel shall contain the follow­ing:

      1. SIGNALS ON/OFF SWITCH. In the OFF position, power shall be removed from signal heads in the intersec­tion. The controller shall continue to operate. When in the OFF position, the MMU shall not con­flict or require reset.
      2. AUTO/FLASH SWITCH. In the flash position, power shall not be removed from the controller and stop time shall be applied. If required by the plans and specifica­tions, an optional RC network shall be provided to give the controller an external start pulse when switch is returned to the auto position. This will force the controller to initiate the start up sequence when exiting flash.
      3. AUTO/MANUAL SWITCH. Cabinet wiring shall include provisions for an AUTO/MANUAL switch and a momen­tary pushbutton or hand cord. The AUTO/MANUAL switch and pushbutton or hand cord shall not be provid­ed unless it is called for in the special provisions of this specification.

16.7.4 All toggle type switches shall be heavy duty and rated 15 amps minimum. Single- or double-pole switches may be provided, as required. All switches shall be rated for a minimum of 30,000 operations.

16.7.5 Any exposed terminals or switch solder points shall be covered with a non-flexible shield to prevent acciden­tal contact.

16.7.6 All switch functions must be permanently and clearly labeled.

16.7.7 All wire routed to the police door-in-door and test switch pushbut­ton panel shall be adequately protected against damage from repetitive opening and closing of the main door.

16.8 CONTROLLER TELEMETRY INTERFACE PANEL

16.8.1 A telemetry interface harness and interface panel for FSK communications over twisted pair cable shall be supplied with each cabinet assembly.

16.8.2 The harness shall be a minimum of 6 feet long and shall consist of two twisted pairs, 22 AWG wire, terminated to a 9-pin "D" type connector at one end. The pin out of the 9‑pin connector shall be in exact accordance with the NEMA TS2 Standard. The opposite end of the har­ness shall be terminated on a 10-position EDCO PCB-1B or exact equal lightning protection socket base.

16.8.3 The interface panel shall be equipped with a 50 row, 6 position 66 block. Each row shall have three two position clips.

16.8.4 A harness, consisting of two twisted pairs, 22 AWG wire shall be provided for connecting the active communications pairs on the 66 block to the lightning protection base specified in Section 8.2.

16.8.5 All terminal block designations and peripheral board-mounted components shall be labeled as to their number and function and shall correspond to the cabinet wiring diagrams.

16.8.6 The following signals shall be accessible from the teleme­try interface panel:

- Local controller command lines 1 & 2.

- Local controller readback lines 1 & 2.

- Master controller command lines 1 & 2.

- Master controller readback lines 1 & 2.

- Earth grounds.

16.8.7 A socket mounted communication line transient protec­tion device shall be supplied with the telemetry inter­face panel. The device shall be an EDCO model PC642C-008D or exact approved equivalent. The transient pro­tection device shall be wired in series with the telem­etry communication circuit.

16.9 AUXILIARY DEVICES

16.9.1 Load Switches

16.9.1.1 Load switches shall be solid state and shall conform to the requirements of Section 6.2 of the NEMA TS2 Stan­dard.

16.9.1.2 Signal load switches shall have a minimum rating of 15 amperes at 120 VAC for an incandescent lamp load. Triac switching devices shall be rated at 600 volts minimum, and have a design life of at least five (5) years.

16.9.1.3 The front of the load switch shall be provided with three indicators to show the input signal from the controller to the load switch.

16.9.1.4 Load switches shall be dedicated per phase. The use of load switches for other partial phases is not accept­able.

16.9.1.5 The full complement of load switches shall be supplied with each cabinet to allow for maximum phase utiliza­tion for which the cabinet is designed (unless otherwise specified by the bid document).

16.9.2 Flasher

16.9.2.1 The flasher shall be solid state and shall conform to the requirements of section 6.3 of the NEMA TS2 Stan­dard.

16.9.2.2 Flashing of field circuits for the purpose of intersec­tion flash shall be accomplished by a separate flasher.

16.9.2.3 The flasher shall be rated at 15 amperes, double pole with a nominal flash rate of 60 FPM.

16.9.2.4 Wiring shall be provided to assign any phase to either circuit of the flasher.

16.9.3 Flash Transfer Relays

16.9.3.1 All flash transfer relays shall meet the requirements of Section 6.4 of the NEMA TS2 Standard.

16.9.3.2 The coil of the flash transfer relay must be deener­gized for flash operation.

16.9.3.3 The full complement of relays shall be supplied with each cabinet to allow for maximum phase utilization for which the cabinet is designed (unless modified by the bid document).

16.9.3.4 The flash transfer relays shall have surge suppression MOV connected in parallel with each of their coils.

16.10 MALFUNCTION MANAGEMENT UNITS

This specification sets forth the minimum requirements for a shelf-mountable, sixteen channel, solid-state Malfunction Management Unit (MMU). The MMU shall meet, as a minimum, all applicable sections of the NEMA Stan­dards Publication No. TS2‑1992. An independent testing laboratory shall verify that the MMU will perform all its defined functions under the conditions set forth in Section 2 of the NEMA STANDARD (Environmental Standards and Test Procedures). Where differences occur, this specification shall govern.

16.10.1 Enclosure

16.10.1.1 The MMU shall be compact so as to fit in limited cabinet space. It shall be installed on a shelf that is at least 7" deep. Overall dimensions, including mating connectors and harness, shall not exceed 10.5" x 4.5" x 11" (H x W x D).

16.10.1.2 The enclosure shall be constructed of sheet aluminum with a minimum thickness of 0.062", and shall be fin­ished with an attractive and durable protective coating. Model, serial number, and program information shall be permanently displayed on the rear surface.

16.10.2 Electronics

16.10.2.1 A microprocessor shall be used for all timing and con­trol functions. Continuing operation of the microproces­sor shall be verified by an independent monitor circuit, which shall force the OUTPUT RELAY to the de-energized "fault" state and indicate an error message if a pulse is not received from the microprocessor within a defined period.

16.10.2.2 In the interest of reliability, only the PROM memory device for the microprocessor firmware shall be socket mounted. The PROM Memory socket shall be a precision screw machine type socket with a gold contact finish providing a reliable gas tight seal. Low insertion force sockets or sockets with "wiper" type contacts shall not be acceptable.

16.10.2.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. Failure of the internal power supply to provide proper operating voltages shall force the OUTPUT RELAY to the de-energized "fault" state and indicate an error mes­sage. A front panel mounted fuse shall be provided for the 120 VAC input.

16.10.2.4 User-programmed configuration settings shall be stored in an electrically erasable programmable read-only memory (EEPROM) or via front panel DIP switches. Designs using a battery to maintain configuration data shall not be acceptable.

16.10.2.5 All 120 VAC field terminal inputs shall provide an input impedance of at least 150K ohms and be terminated with a resistor having a power dissipation rating of 0.5 Watts or greater. Each 120 VAC field terminal input shall be sensed by a separate precision voltage comparator de­vice.

16.10.2.6 All electrical components used in the MMU shall be rated by the component manufacturer to operate over the full NEMA temperature range of -30 deg C to +74 deg C.

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

      1. All plated-through holes and exposed circuit traces shall be plated with solder.
      2. Both sides of the printed circuit board shall be covered with a solder mask material.
      3. 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 desig­nated on both sides of all printed circuit boards.
      4. All electrical mating surfaces shall be gold plated.
      5. All printed circuit board assemblies shall be coated on both sides with a clear moisture-proof and fungus-proof sealant.

16.10.3 Front Panel & Connectors

16.10.3.1 All displays, configuration switches, and connectors shall be mounted on the front panel of the MMU. All MMU configuration inputs beyond those required by the NEMA Standard shall be provided by front panel mounted DIP switches and shall be clearly labeled. Configuration DIP switches shall be provided for the following functions:

      1. Field Check / Dual Enables 1-16
      2. Green/Yellow-Dual Indication Enable
      3. BND Test Disable
      4. External Watchdog Enable

16.10.3.2 The connectors on the MMU shall have a metallic shell and be attached to the chassis internally. They shall be manufactured to meet MIL-C-26482 specifications. The connectors shall be mounted on the front of the unit in accordance with the following: Connector A shall inter­mate with a MS 3116 22-55 SZ, and Connector B shall intermate with a MS 3116 16-26 S.

16.10.3.3 In the interest of reliability and reparability, printed circuit board mounted MS connectors shall not be acceptable. Internal MS harness wire shall be a minimum of AWG #22, 19 strand. Wiring between the MS connector and pc boards shall be soldered. Friction or crimp style connectors are not acceptable

16.10.3.4 All indicator lights shall be water clear, T‑1 package, Red Super Bright type LEDs. Indicators shall be provided for the following items:

      1. a. Channel Status 1-16
      2. Conflict
      3. Red Fail
      4. CVM / External Watchdog
      5. 24V-2
      6. 24V-1
      7. Clearance Fail
      8. Port 1 Fail
      9. Diagnostic / Program Card
      10. Field Check Fail
      11. Dual Indication
      12. Type 12 mode
      13. Power
      14. Port 1 Receive
      15. Port 1 Transmit

16.10.4 Operating Modes

The MMU shall operate in both the Type 12 mode and Type 16 mode as required by the NEMA Standard.

16.10.5 Monitoring Functions

The following monitoring functions shall be provided in addition to those required by the NEMA Standard Section 4.

16.10.6 Dual Indication Monitoring

16.10.6.1 Sixteen switches labeled FIELD CHECK/DUAL ENABLES shall be provided on the MMU front panel to enable Dual Indi­cation Monitoring on a per channel basis. The Dual Indi­cation Monitor function shall provide two modes of oper­ation, Dual Indication Fault and Green/Yellow-Dual Indi­cation Fault.

16.10.6.2 When voltages on two inputs of a channel are sensed as active for more than 1000 msec, the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the DUAL INDICATION indi­cator. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. When voltages on two inputs of a channel are sensed as active for less than 700 msec, the MMU shall not transfer the OUTPUT relay contacts to the Fault position.

16.10.6.3 When operating in the Type 16 mode with Port 1 communi­cations enabled, Bit #68 (Spare Bit #2) of the Type #129 response frame shall be set to indicate a Dual Indica­tion fault has been detected.

16.10.6.4 Dual Indication Monitoring shall be disabled when the RED ENABLE input is not active. When operating in the Type 16 mode with Port 1 communications enabled, Dual Indication Monitoring shall also be disabled if the LOAD SWITCH FLASH bit is set to "1" in the Type #0 message from the Controller Unit.

16.10.7 Dual Indication Monitor

Dual Indication monitoring shall detect simultaneous input combinations of active Green (Walk), Yellow, or Red (Don’t Walk) field signal inputs on the same channel. In Type 12 mode this monitoring function detects simul­taneous input combinations of active Green and Yellow, Green and Red, Yellow and Red, Walk and Yellow, or Walk and Red field signal inputs on the same channel.

16.10.8 Green Yellow-Dual Indication Monitor

16.10.8.1 Green Yellow-Dual Indication monitoring shall detect simulta­neous inputs of active Green and Yellow field signal inputs on the same channel. It will be used to monitor channels which have an unused Red field signal input tied to AC LINE such as a five section signal head.

16.10.8.2 Green Yellow‑Dual Indication Monitoring shall be enabled by a front panel option switch. When the Green Yellow‑Dual Indica­tion Monitoring option is enabled, all channels which have the front panel FIELD CHECK/DUAL ENABLE switches OFF shall be individually monitored for simul­taneous active Green and Yellow field signal in­puts. All chan­nels which have the front panel FIELD CHECK/DUAL ENABLE switches ON (i.e., enabled for Dual Indication Monitoring) shall function as described above in Dual Indication Monitoring.

16.10.9 Field Check Monitoring

16.10.9.1 Sixteen switches labeled FIELD CHECK/DUAL ENABLES shall be provided on the MMU front panel to enable Field Check Monitoring on a per channel basis. The Field Check Moni­tor function shall provide two modes of operation, Field Check Fault and Field Check Status.

16.10.9.2 Field Check Monitoring shall be disabled when the RED ENABLE input is not active. When operating in the Type 16 mode with Port 1 communications enabled, Field Check Monitoring shall also be disabled if the LOAD SWITCH FLASH bit is set to "1" in the Type #0 message from the Controller Unit. The Field Check Monitoring function shall be disabled in the Type 12 mode.

16.10.9.3 Field Check Monitor

In the Field Check Fault mode, when the field signal input states sensed as active or inactive by the MMU do not correspond with the data provided by the Controller Unit in the Type #0 message for 10 consecutive messages, the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the FIELD CHECK FAIL indicator. The Channel Status Display shall indicate the channels on which the Field Check fault was detected. Bit #67 (Spare Bit #1) of the Type #129 response frame shall be set to indicate a Field Check fault has been detected. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input.

16.10.9.4 Field Check Status

The Field Check Status mode shall work in combination with the other fault monitoring functions of the MMU. When a Conflict, Red Fail, Clearance Fail, or Dual Indi­cation Fail triggers the MMU, the Channel Status Display and Fault Status Display shall correspond to that de­tected fault. If Field Check errors were detected while the fault was being timed, the FIELD CHECK FAIL indica­tor shall illuminate and double pulse once every 2 sec­onds. The channels on which the Field Check errors were detected shall double pulse at the same time as the FIELD CHECK FAIL indicator. Bit #67 (Spare Bit #1) of the Type #129 response frame shall also be set to indi­cate Field Check errors have been detected.

16.10.10 BND Error Detection Monitoring

16.10.10.1 The BND Error Detection function shall be designed to detect and respond to irregular field input waveforms such as: irregularly blinking (flickering); having con­stant extraneous noise; being dimmed invalidly under Controller Unit software control.

16.10.10.2 Detection of a BND Error shall place the MMU into the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the BND FAIL indicator. The Channel Status display shall indicate the channels on which the fault occurred. When operating in the Type 16 mode with Port 1 communications enabled, Bit #69 (Spare Bit #3) of the Type #129 response frame shall be set to indicate a BND Error Detection fault has been detected. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the BND Fail fault state of the monitor.

16.10.11 External Watchdog Monitor

16.10.11.1 The MMU shall provide the capability to monitor an op­tional external logic level output from a Controller Unit or other external cabinet circuitry. If the MMU does not receive a change in state on the EXTERNAL WATCHDOG input for 1500 msec (100 msec), the MMU shall enter the fault mode, transfer the OUTPUT relay contacts to the Fault position, and illuminate the CVM/WATCHDOG indicator. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the CVM/WATCHDOG fault state of the monitor.

16.10.11.2 When operating in the Type 16 mode with Port 1 communi­cations enabled, Bit #70 (Spare Bit #4) of the Type #129 response frame shall be set to indicate an External Watchdog fault has been detected.

16.10.12 Type Fault Monitor

16.10.12.1 The MMU shall verify at power-up that the Type 12 or Type 16 operating mode as determined by the TYPE SELECT input is consistent with the mode set by the last exter­nal reset.

16.10.12.2 Detection of a Type Fault shall place the MMU into the fault mode, transfer the OUTPUT relay contacts to the Fault position, illuminate the DIAGNOSTIC indicator, and flash the TYPE 12 indicator at a 2Hz rate. The MMU shall remain in the fault mode until the unit is reset by the RESET button or the EXTERNAL RESET input. An MMU Power Failure shall reset the Type Fault state of the monitor.

16.10.13 Display Functions

The following display functions shall be provided in addition to those required by the NEMA Standard Section 4.

16.10.14 Yellow Plus Red Clearance Interval Display

The MMU Channel Status display shall indicate with a steadily illuminated LED indicator, those channels which had the short Yellow plus Red interval (i.e., those channels which did not meet the minimum Yellow Change plus Red Clearance Interval). The conflicting channel(s) which was sensed active Green causing the Minimum Yellow Change plus Red Clearance Fault shall also be indicated with a single pulsed LED indicator.

16.10.15 Field Check Status Display

16.10.15.1 The FIELD CHECK FAIL indicator shall illuminate when a Field Check Fault is detected. The Channel Status dis­play shall show the channels on which the Field Check fault occurred.

16.10.15.2 If Field Check errors occurred during a Conflict Fault, Red Fail, Clearance Fail, or Dual Indication Fail the FIELD CHECK FAIL indicator shall illuminate and double pulse every 2 seconds. The channels on which the Field Check Status was detected during the fault shall double pulse on the Channel Status Display at the same time as the FIELD CHECK FAIL indicator.

16.10.16 Display Indicators

The following display indicators shall be provided in addition to those required by the NEMA Standard Section 4.

16.10.17 Type 12 Mode Indicator

The TYPE 12 indicator shall illuminate when the MMU is programmed for Type 12 operation. If a Type Fault is detected the DIAGNOSTIC/PGM CARD indicator shall illumi­nate and the TYPE 12 indicator shall flash at a rate of 2Hz.

16.10.18 BND Fail Indicator

The BND FAIL indicator shall illuminate when a BND Fault is detected. The Channel Status display shall show the channels which were detected as BND Fail.

16.10.19 Dual Indication Indicator

The DUAL INDICATION indicator shall illuminate when a DUAL INDICATION Fault is detected. The Channel Status display shall show the channels which were detected as DUAL INDICATION.

16.10.20 Power Indicator

The POWER indicator shall flash at a rate of 2Hz when the AC LINE voltage is below the drop‑out level. It shall illuminate steadily when the AC LINE voltage re­turns above the restore level.

16.10.21 Port 1 Receive Indicator

The RECEIVE indicator shall illuminate for a 33 msec pulse each time a Port 1 message is correctly received from the Controller Unit.

16.10.22 Port 1 Transmit Indicator

The TRANSMIT indicator shall illuminate whenever the MMU has the Port 1 transmitter enabled.

16.10.23 Program Card Indicator

The DIAGNOSTIC/PGM CARD indicator shall flash at a 2Hz rate if the Programming Card is absent or not seated properly in its mating connector.

16.10.24 Additional Features

16.10.24.1 The MMU shall include both automatic and operator initi­ated diagnostics.

16.10.24.2 Automatic diagnostics shall verify memory and micropro­cessor operation each time power is reapplied to the MMU. After power has been applied, diagnostics shall continually verify the operation of essential elements of the MMU including at a minimum: PROM, EEPROM, commu­nications, internal power supply, and the microproces­sor.

16.10.24.3 Operator initiated diagnostics shall allow the operator to verify proper operation of all indicator lights, PROM, EEPROM, RAM, and microprocessor.

16.11 TESTING AND WARRANTY

16.11.1 Testing

16.11.1.1 Each cabinet assembly shall be tested as a complete entity under signal load for a minimum of 24 hours.

16.11.1.2 The cabinet shall be assembled and tested by the con­troller manufacturer or authorized local distributor to ensure proper component integration and operation.

16.11.2 Warranty

16.11.2.1 The cabinet assembly and Malfunction Management Unit shall be warranted by the manufacturer against mechanical and electrical defects for a minimum of two years from the date of receipt or one year from the date of installation, whichever comes first. The manu­facturer's warranty shall be supplied in writing with each cabinet and controller. Second party extended warranties are not acceptable.

16.11.2.2 Any minor defects will be corrected by the Utah Department of Transportation at their discretion, with the consent of the manufacturer. All other repairs under warranty will be made by the manufacturer. The manufacturer will bear all costs for making repairs under warranty including labor, parts and shipping.

16.12 METHOD OF MEASUREMENT

NEMA TS2 Type 2 Size 5, Configuration 3 and size 6, Configuration 4 Cabinet Assemblies shall be measured separately for payment by the number of units each, complete with all components provided as specified herein and delivered to the Department.

16.13 BASIS OF PAYMENT

NEMA TS2 Size 5, Configuration 3 and Size 6 Configuration 4 Cabinet Assemblies will be paid for separately at the contract unit price each, which price shall be payment in full, for furnishing a complete Cabinet Assembly as specified herein and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.


17 ITEM 17. TRAINING

17.1 DESCRIPTION

Work under this item shall consist of providing qualified instructors and all materials for training Department personnel and other designated personnel in the operation and maintenance of the various components furnished under this category - Traffic Signal Equipment.

17.2 MATERIALS

The contractor shall develop and submit training course outlines and samples of all training aids and manuals to the engineer for approval at least forty-five (45) days prior to the proposed scheduled start of the training sessions. Written approval of this material shall be required prior to the final scheduling of the training sessions or the final production of training materials. Training shall not begin until after approval of the submitted training material, and a minimum of 10 working days after acceptance of the operation and maintenance manuals specified under the Item Documentation.

17.3 As part of this item, the Contractor shall provide three sets of all test equipment needed to perform the tests called for in this specification. The Contractor shall also provide 3 sets of any and all test equipment needed to perform routine maintenance on the equipment furnished under this category of the specification. The training sessions described under this item shall include training on the use of the test equipment furnished by the Contractor.

17.4 CONSTRUCTION METHODS

All training sessions shall be conducted at locations within Salt Lake County, Utah, to be designated by the Department. Training sessions shall not overlap unless otherwise permitted by the Department.

17.4.1 Training shall consist of formal classroom lectures as well as “hands-on” training. "Hands-on" training shall consist of working with the actual equipment.

17.4.2 Two (2) training sessions shall be provided the equipment as follows:

17.4.3 A "day" of training shall consist of 6 hours. The two sessions for each equipment category/subsystem shall be identical in content. The training sessions shall not overlap unless otherwise permitted by the engineer. The attendance of each session shall not be more than 30 people. Each session shall provide a basic understanding of the equipment and subsystems and their operation and maintenance. These training sessions shall include as appropriate, and as a minimum:

      1. Background on concepts of equipment/subsystem, and theory of operation.
      2. Functional description of controller equipment.
      3. Procedures for installing and setting up equipment and components.
      4. Basic troubleshooting and fault determination procedures.
      5. Procedures for “mail-in” repairs.
      6. Preventive maintenance procedures and schedules.

17.4.4 The contractor shall video tape all training sessions, and provide the tapes to the Department for training new personnel in the future.

17.5 METHOD OF MEASUREMENT

Training will be measured as a lump sum which shall cover all preparation of course materials and as well as the time and human resources to provide and run the course at a location to be determined by the Department.

17.6 BASIS OF PAYMENT

Training, measured as provided above, will be paid for at the contract unit price Lump Sum, which price shall be full compensation for furnishing instructors and training materials; for providing the training sessions; and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.


18 ITEM 18. ENGINEERING FIELD SERVICES

18.1 DESCRIPTION

The Contractor shall provide on-site services when requested by UDOT, including, but not limited to:

      1. Assist the Department with design of system traffic-responsive operation
      2. Fully program local controllers and master controllers with coordination plans and timing settings
      3. Install system software on central computers and laptops
      4. Develop and program all intersection graphics and system maps on the system software
      5. Bench test systems to ensure proper operation of hardware and programming of coordination plans
      6. Training department personnel on operation of controllers and closed loop system software, troubleshooting, and bench repair of equipment
      7. Provide field services for inspection of installation and fine-tuning of coordination timing

18.1.1 Field services shall be provided by experienced personnel familiar with use of the equipment and software. Experienced personnel shall include, but not be limited to, instructors, engineers, and field technicians.

18.1.2 Payment for on-site services will be on an 8-hour "person-day" basis with a minimum order of two (2) one full days

18.1.3 Time required to travel from out of state to Utah shall not be eligible for payment. Travel time within Utah between UDOT sites is included in the "person-day".

18.1.4 All direct costs of travel, accommodations, and meals shall be included in the unit bid price per day for on-site services. No separate payments will be made for these travel costs.

18.1.5 On-site services may be required anywhere in the state of Utah. Field services will be scheduled at least two weeks in advance.

18.1.6 No payment will be made for on-site services which are required to trouble-shoot or resolve problems caused by malfunctions or failures of the Contractor's equipment or for work done under warranty.

18.2 METHOD of MEASUREMENT

Engineering Field Services will be measured as days, with each day consisting of an eight hour "person-day".

18.3 BASIS of PAYMENT

Engineering Field Services, measured as provided above, will be paid for at the contract unit price per day, which price shall be full compensation for furnishing field personnel to provide field services; and for all labor, equipment, transportation, and incidentals necessary to complete this item of work.


19 ITEM 19. ALLOWANCE FOR MISCELLANEOUS ITEMS

19.1 DESCRIPTION

Under this item, UDOT will purchase miscellaneous ATMS signal equipment parts on an as-needed basis in small quantities. This will include spare and replacement parts. Equipment purchased may include, but not be limited to the following:

      1. Controller components (modules, connectors, etc)
      2. Load switches
      3. Conflict monitors
      4. Detector amplifiers
      5. Flashers
      6. Flash Transfer Relays
      7. Harnesses
      8. Electronic components needed to make repairs
      9. Terminal blocks
      10. Communication modems

19.1.1 A price list or catalog for miscellaneous signal control parts, related to the equipment described above, shall be included in the proposal. Any discount offered shall be indicated.

19.2 METHOD OF MEASUREMENT

This Item is measured as a Lump Sum the value for this item is fixed as stated in the bid sheets and must be included by all bidders in calculating the total for their proposal.

19.3 BASIS OF PAYMENT

Payment for equipment ordered under this item shall be made according to the price list, less any discount offered.