16-Product Specification - Signal Controller Cabinet, Detection System and UPS Secifications.pdf

PARADIGM TRAFFIC SYSTEMS, INC.

PART NUMBER: PT-P44168TS2-1-MC, NEMA CABINET ASSEMBLY / TS2-1, P44

CABINET WITH 16 POSITION BACKPANEL PER CITY OF BROWNSVILLE

SPECIFICATION REQUIREMENTS

REV 3.8.2015

PARADIGM TRAFFIC SYSTEMS, INC.

PART NUMBER: PT-P44168TS2-1-MC, NEMA CABINET ASSEMBLY / TS2-1, P44

CABINET WITH 16 POSITION BACKPANEL PER CITY OF BROWNSVILLE

SPECIFICATION REQUIREMENTS

1.0 SCOPE

1.1 This specification sets forth the minimum requirements for a shelf-mounted 16 phase full-actuated solid state controller unit with internal Time-Based Coordination (TBC), railroad/fire (emergency vehicle) preemption, diamond intersection operation in a traffic signal controller assembly and cabinet assembly. This specification also sets forth minimum requirements for a Video detection system, wireless in pavement detection system and battery backup (UPS).

1.2 Appendix A identifies the equipment type and options available in this specification. Equipment supplied shall be according to the selections made in Appendix A.

2.0 CONTROLLER UNIT

2.1 The controller unit shall meet the requirements of NEMA Standards Publication TS-2 2003 V2.06 or latest revision. The controller/cabinet unit shall meet all current AASHTO and ANSI standards applicable to the industry. The controller/cabinet unit shall comply with all current and applicable National Transportation Communications for ITS Protocol (NTCIP) standards. The controller/cabinet unit shall comply with all the criteria of this specification. Where a difference occurs between this specification and another specification or standard the requirements of this specification shall govern. The purchase document shall identify either a TS-2 Type 1 interface or TS-2 Type 2 interface. The cabinets for TS-2 Type 1 controllers are specified in this document.

TS-2 Type 2 controller cabinets shall use a cabinet specification identified in the solicitation document. The controller shall be configurable to meet, at a minimum, all applicable sections of the NEMA Standards Publications for TS2 and NTCIP 1202 and ATC standard 6.10. Where differences occur, these specifications shall govern.

2.2 The controller shall be compact so as to fit in limited cabinet space. It shall require no more than 7” shelf depth. External dimensions shall not be larger than 8.5" x 15.2 1/4" x 6.375" (H x W x D).

2.3 Hardware Design Requirements - The top and bottom of the chassis shall be made from extruded aluminum and include an integral handle on the back for easy transport. The sides shall be constructed of injection molded polycarbonate. The model, serial number, and program information shall be displayed on the outside of the controller.

2.3.1 The controller unit shall be completely solid state and digitally timed. All timing shall be referenced to the 60 Hz power line.

CABINET WITH 16 POSITION BACKPANEL PER CITY OF BROWNSVILLE

SPECIFICATION REQUIREMENTS

REV 3.8.2015

2.3.2 The dimensions of the controller unit shall not exceed 305 mm high, 440 mm wide, and 305 mm deep.

2.3.3 The front of the controller shall consist of a panel for the display, keyboard and connectors for all necessary user connections.

The display shall be a seven-inch (7”), color, TFT (Thin Film Transistor) LCD (Liquid Crystal

Display) with high brightness. It shall be readable in direct sunlight. The display shall perform over the NEMA temperature range and shall have a resolution of 800 X 480 with an 18 bit color depth. The luminous intensity shall be a minimum of 800 nits. The display shall include an industrial, resistive touch screen that can be operated with gloved hands. The touch screen and display shall not be affected by condensation or water drops.

Front-panel operator inputs shall be via touch screen or by clearly labeled elastomeric keypad.

These shall include a 10-digit numeric keypad, Main and Sub keys, toggle keys, special function and enter keys, six function keys, status and help keys and a large four-direction cursor control key.

2.3.4 The front panel shall include a built in speaker for enhanced controller audio feedback.

2.3.5 The front panel shall include a tri-color status LED.

2.3.6 The controller shall have the capability of supporting Ethernet communications, using TCP/IP communications protocols.

2.3.7 The controller shall provide four front-panel Ethernet ports

2.3.8 Two of the ports shall be connected to Ethernet switch ENET1 and the other two shall be connected to Ethernet switchENET2

2.3.9 The controller shall provide two USB 2.0 ports.

2.3.10 USB ports shall be used for USB thumb drives to update software, upload or download configuration, or uploading logged data.

2.3.11 All non-optional interface connectors shall be accessible from the front of the controller in the

NEMA Configured Controller models. Configurations shall be offered to accommodate different versions, as follows:

2.3.11.1 NEMA TS2 Type 1

2.3.11.2 NEMA TS2 Type 2

2.3.11.3 NEMA TS1

2.3.12 The D connector shall be compatible with the Econolite Model ASC/2, ASC/2S, and ASC/3 D connectors.

2.3.13 To facilitate special applications the controller shall have the capability of assignment of any input or output function to any input or output pin respectively on the interface connectors, with the exception of Flashing Monitor, Controller Voltage Monitor, AC+, AC-, Chassis Ground, 24VDC, Logic Ground and TS2 Mode bits.

2.3.14 The controller shall as a minimum have the following communications ports:

a. Port 1 SDLC for communications to other devices in the cabinet

b. Port 2 serial port for systems communications

c. Console serial port for local communications An optional telemetry module shall utilize TDM/FSK data transmission at 1200 baud or 9600 baud over two pairs of wires. This module shall include the Econolite 25-pin D-sub connector.

d. Ports on optional ATC-2070 communication modules – see section 2.10.2

2.3.15 Serial communications shall operate at from 1200 to 115.2 K baud

2.3.16 All electronic modules including the power supply shall be easily removable from the controller using a screwdriver as the only tool. All power and signal connections to the circuit boards shall be via plug-in connectors.

2.4 Hardware Options

2.4.1 Optional Data Key

2.4.1.1. A Datakey and receptacle shall be available for use as a database storage device (backup) or as a database transfer module. It shall be capable of storing a minimum 2MB of data.

2.4.1.2. The Datakey shall be hot swappable, so that it can be inserted and removed without powering down the controller.

2.4.1.3. The Datakey shall be capable of storing the entire controller database and shall retain the information without use of battery or capacitor backup.

2.4.1.4. The controller shall not require this key to be present during normal operation.

2.4.1.5. If the Datakey is present the controller shall automatically backup the database to the data key 20 minutes following the last data change.

2.4.2. Optional ATC-2070 type communications slot

2.4.2.1. The controller shall provide support one ATC-2070 Type communications slot that can be added, if needed, providing access to ATC communications ports

2.5 Electronics

2.5.1 The electronics shall be modular in design and shall consist of vertical circuit boards. Horizontal circuit boards shall not acceptable.

2.5.2 In the interest of reliability, no sockets shall be used for any electronic device. All devices shall be directly soldered to the printed circuit board. Surface mount parts shall be used for the majority of the electronic components in the controller.

2.5.3 A built-in, high-efficiency switching power supply shall generate the primary, +5VDCinternal voltage, an isolated +24 VDC for internal and external use, VSTANDBY, LINESYNC, POWERUP and POWERDOWN signals. All voltages shall be regulated.

2.5.4 The 120 or 220VAC fuse shall be mounted on the front of the controller. Protection for the

24VDC supply shall be provided by a resettable electronic fuse.

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

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

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

2.5.5.3. All printed circuit board assemblies shall be coated on both sides with a clear moisture-proof and fungus-proof sealant.

2.5.6. Timing of the controller traffic application shall be derived from the AC power line.

2.5.7. To facilitate the transfer of user-programmed data from one controller to another, a Datakey receptacle for using a separate 2070-style, serial flash memory device shall be an available hardware option. In addition, two USB sockets and one SD Card socket shall be provided for memory devices that can be used for data transfer. These data transfer devices shall be easily removable and directly accessible from the outside of the controller. The controller will not require this Datakey, USB memory thumb drive, or SD Card to be present for proper operation.

2.5.8. All controller software shall be stored in Flash Memory devices. The controller software shall be easily updated without the removal of any memory device from the controller. The use of removable PROMS or EPROMS from the controller shall not be acceptable. The controller shall include an option that allows updating software using a Windows based computer, a USB memory thumb drive, or an SD card.

2.6 ATC Engine Board

2.6.1. The controller shall include an ATC engine board compliant to ATC standard 5.2b and proposed version 6.10.

2.6.2. The engine board shall include a PowerPC 83XX family processor with QUICC engine.

2.6.3. The engine board shall have a minimum of the following memory:

2.6.3.1. 128Mbytes of DDR2 DRAM memory used for application and OS program execution

2.6.3.2. 64 Mbytes of FLASH memory used for storage of OS Software and user applications

2.6.3.3. 2MB of SRAM memory used for non-volatile parameter storage

2.6.4. The engine board shall provide the seven ATC serial ports, Ethernet, USB and all other control signal required by ATC standard.

2.6.5. The operating system shall be Linux 2.6.35 or later

2.7. Graphical User Interface

2.7.1. The controller shall include an advanced graphics card.

2.7.2. The graphics card shall enable:

2.7.2.1. Graphical display of status and programming selections

2.7.2.1.1. The status displays shall include direction arrows for each of the phases and overlaps.

2.7.2.1.2. The selection of programming sections menus shall be by use of icons.

2.7.2.1.3. Programming shall use touch data entry, allowing touch gestures to select yes/no, select enable/disable, pull-down list selections, and more.

2.7.2.2. Touch selection of status and programming

2.7.2.3. Swiping to advance from one screen to the next

2.7.3. Program values shall be entered through either the keypad or the touch screen.

2.7.4. The controller shall allow connection of a tablet to the controller.

2.7.4.1. The tablet connection shall be by Wi-Fi connection either by a Wi-Fi to USB adapter or an Ethernet to Wi-Fi adapter.

2.7.4.2. Once connected it shall be possible to observe the exact same graphics displays as are visible on the touch screen of the controller.

2.7.4.3. It shall be possible to change the controller’s programming values from the tablet while it is connected.

2.8 Time Clock

2.8.1 The clock shall use the 60 Hz power line frequency as time base when power is present. The clock operating voltage range shall be 89 to 135V AC over the temperature range of -34°C to +74°C. A 10 year lithium battery shall maintain the time-of-day clock and digital data during a power outage lasting up to 30 days. Lead-acid, nickel-cadmium, or alkaline batteries are not acceptable.

2.8.2 The time base clock shall be maintained to within ± 0.005% at 20°C and to within a ± 0.02% over the specified operating temperature range as compared to coordinated universal time (WWV) standard for a period of 30 days during periods when AC power is not applied.

2.9 Clock/Calendar Programming Requirements

2.9.1 The clock shall be easily set to the year, month, day of month, day of week, hour, minute, and second.

2.9.2 Automatic daylight savings time shall be available by keyboard entry.

2.9.3 The dates for fixed and floating holidays and special events shall be keyboard programmable by the user.

2.9.4 Calendar adjustments for leap years shall be automatic.

2.9.5 The clock shall store sequences of operations in the form of 255 entries and 15 day plans.

Global Time Base Schedule Actuated Traffic Signal Schedule

Entry Months Dates of Month

Days of Week

Day Plan Time Base Actions

1 1-12 1-31 1-7 1-15 entry 1 actions

255 " " " " entry 255 actions

2.9.6 The structure and interrelationships of each type of program shall be in accordance with the following paragraphs:

2.9.6.1 A day plan shall consist of the following:

Hour : Minute Action 1 (time to implement: action to implement) Hour : Minute Action 10 (time to implement: action to implement)

Where each action is unique, there shall be a minimum of ten actions per day plan.

There shall be a minimum of 15 day plans.

2.9.6.2 Each action in a day plan shall consist of a group of the following objects:

• pattern (consisting of):

cycle length offset split MUTCD flash (on/off) free operation

• sequence

• special functions 1-8 (on/off)

• auxiliary functions 1-3 (on/off)

• mode of operation (a means of changing operating modes by T.O.D.)

• max II

• gap/ext II

• phase omits

Any or all of these may be selected within a single action.

Transfer into and out of flash shall be in accordance with the Texas MUTCD. It shall be possible to program each phase and overlap to flash either yellow or red via the front panel of the controller unit. This shall be accomplished by flashing the load switch driver outputs simultaneously.

2.9.6.3 An entry shall consist of time period implemented: day plan, month(s), date(s) of month, and day(s) of week.

2.9.6.4 A minimum of 255 entries shall be programmable.

2.9.6.5 There shall be a copy feature that allows the transfer of entries between day plans.

2.9.6.6 Other programming schemes meeting the functional intent are acceptable but require approval in writing by the City Of College Station Traffic Engineer.

2.10 Program Requirements

2.10.1 Programming

2.10.1.1 Programming of the controller unit shall be by the use of a keyboard and display on the front of the controller unit. Programming shall require only simple keystrokes aided by full menu displays. It shall be possible for the controller to interface with a laptop and using compatible software, upload, download, and save data to a database

2.10.1.2 Ease of programming through a well-organized menu structure and ease in interpreting the display shall be required for acceptance. The menu structure shall contain a main menu that contains options for all sections of the controller on one screen. Each option shall be selectable by a numeric entry. Each subsequent menu shall be a detailed breakdown of one of the previous menu options. Each menu option shall be a descriptive name to prompt the user to the desired section for programming.

All entries shall be displayed and entered in plain English. Toggle type entries shall be set by entering YES/NO or ON/OFF responses. Non-alphanumeric symbols and abbreviations used to display information shall be clear and unambiguous in their meaning. Numeric entries shall be in the base 10 (decimal) number system. Entries in other number bases, such as hexadecimal or binary, are not acceptable.

2.10.1.3 A user selectable 4 digit (minimum) code shall be available to secure access to timing and configuration of the unit. Display features shall be available without the need to access the unit.

The controller units shall be supplied with the code preset to be all zeros (0000). Internal DIP switches may be used to establish codes.

2.10.1.4 Instructions for use of the access code shall not be provided on the face of the unit.

2.10.1.5 A keyboard entered coded command (a series of commands or entries, not a single entry) shall be provided which will set all controller and TBC timings and entries to a default or inactive value.

This coded command shall allow new values to be entered without first deleting prior entries.

2.10.1.6 With the intersection display active, a keyboard command shall enable the keyboard for the user to place a call to each phase individually.

2.10.2 Phase Operation

2.10.2.1 In NEMA operating mode, the controller unit shall provide as a minimum, 16 possible phases and

8 possible overlaps. All overlaps shall be programmable through the keyboard and shall function as specified by TS-2.

2.10.2.2 Each of the NEMA timing intervals shall be programmable for a minimum of 8 phases at a time from the same display screen in a spreadsheet format. The display may be rolled or paged down to display additional intervals or information.

2.10.2.3 The controller unit shall have a copying mode whereby the user, after having programmed all intervals of one phase may copy this information into all or selected remaining phases. Other versions of the copying process that meet the functional intent are acceptable.

2.10.2.4 In addition to the modes defined by TS-2, the following modes shall be available on a per phase basis:

1. Soft recall

2. Phase omit

2.10.2.5 The following configurations, as a minimum, shall be programmed within the controller unit and be user selectable:

1. 8 phase NEMA

2. 8 phase sequential

3. NEMA phasing to the left of the barrier, sequential phasing to the right of the barrier

(quad sequential).

4. 4 phase diamond

5. 3 phase diamond

6. Separate intersection (see Paragraph 2.8.1.3)

2.10.2.6 The controller shall have a configuration which allows user programmable rings (compatibility lines, reference points to assure there shall be no concurrent selection and timing of conflicting phases). A minimum of 4 rings will be available in this configuration.

2.10.2.7 The controller shall have programmable conflicting phase settings where simultaneous operation of compatible phases is not allowed.

2.10.2.8 A dynamic maximum operation which increments the current maximum in programmable steps

(dynamic max step) in seconds to a maximum limit (dynamic max limit) in seconds shall be provided. The operation shall function as defined by NEMA Standard Publication NTCIP 1202:1996 (TS 3.5) Object Definitions for Actuated Traffic Signal Controller Units, or latest revision.

2.10.2.9 The TBC shall select and coordinate reversible left turn sequence operations (dual leading, leading and lagging, or lagging and leading left turns). It shall be possible to transfer operation from one sequence to another at a preprogrammed time. Transfer shall take place at T0 during coordination (see Paragraph 2.6.4.2).

2.10.3 Pedestrian Timing

2.10.3.1 Actuated pedestrian movements shall operate as follows:

1. When NO pedestrian calls are present, the normal phase timings shall be effective for service of the intersection.

2. When a pedestrian call is present, the call will be serviced by extended phase timings that account for pedestrian crossing times and override the normal phase timings. If the intersection is coordinated, it may drop out of coordination when servicing the pedestrian call if the pedestrian times exceed the vehicle splits. The controller shall return to coordination in the manner described in this specification after the call is serviced.

2.10.3.2 The controller shall rest in main-street green and Don't Walk when no actuated pedestrian calls are present.

2.10.4 Coordination

2.10.4.1 A minimum of 16 timing plans, each with a unique cycle length and split combination, shall be required as per TS-2. Each of the 16 timing plans shall have 3 unique offsets available. Cycle length selections are to be each changeable from 30 to 255 seconds in one second increments.

Split and offset selections adjustable from 0 to 254 in 1 second increments.

2.10.4.2 The coordinator shall reference a system-wide reference cycle timer (system cycle timer). The term T0 shall refer to the point in the local cycle timer when the first coordinated phase (or leading coordinated phase if a pair of coordinated phases was selected by the user) is scheduled on for the first time. NOTE: This may not be the beginning of green in the case of early return.

The offset shall be the amount the local cycle timer is behind the system cycle timer.

Example: If the offset is +10 seconds, T0 (the point at which the local cycle timer is at

0) will occur when the system cycle timer is at 10 seconds.

2.10.4.3 There shall be two modes of automatic coordination programming, fixed and floating force off modes. The following information shall be all that is required from the user to establish a pattern.

1. Basic NEMA controller timing.

2. Cycle length in seconds.

3. Phase sequence desired for the particular pattern.

4. Total seconds of the cycle that a phase is to be active including green, amber, and red clearance times when there is constant demand on all input detectors.

5. The coordinated phase or phases (from Paragraph 2.6.4.9).

6. The offset of the first coordinated phase serviced in the sequence from the reference clock's T0 in seconds.

2.10.4.4 Using the above information in fixed force-off mode, the coordinator must perform the following functions for each pattern.

1. Guarantee the coordinated phase(s) programmed time will be serviced in its entirety to achieve coordination between intersections (when not correcting). The programmed time of the first coordinated phase in the phase sequence shall start at T0.

2. Calculate each phase's force off point (the point at which a phase's Green must terminate in order to not violate the following phases' programmed times).

3. Calculate the beginning of each phase's permissive window (the point in the cycle when the coordinated phase is allowed to yield to each corresponding phase).

4. Calculate the end of each phase's vehicle permissive window (the point preceding a phase's force off point by its minimum time and the prior phase's clearance time). Any phase receiving a vehicle call before the end of vehicle permissive window will be serviced during the current cycle.

5. Calculate the end of each phase's pedestrian permissive window (the point preceding a phase's force off point by pedestrian Walk and pedestrian clearance times and the prior phase's clearance time). Any pedestrian call received by a phase before the end of pedestrian permissive window will be serviced during the current cycle up to the beginning of the phase vehicle green.

6. Guarantee that each phase's programmed time be serviced in full if a call was received before the beginning of permissive window and the phase does not terminate due to Gap out.

2.10.4.5 Using the same information in floating force-off mode, the coordinator must operate in the same manner as fixed force-off mode except that if a non-coordinated phase is entered early, it will remain active only for the time programmed in the split time. Automatically setting the max timer in each split to accomplish this function is acceptable.

2.10.4.6 No percentage inputs are allowed. Once the information for phase service is entered via the keyboard, the controller unit shall test the plan to insure that the plan does not violate any minimum times based on the specified numbers and cycle length. If a faulty plan is detected, the controller unit shall show an error code indicating the problem. If the error is not corrected, the controller unit shall run in free operation mode whenever the erroneous plan is selected. If actuated pedestrian movements are programmed, the coordinator shall ignore errors detected due to the pedestrian Walk and clearance times violating the phase split time for any actuated pedestrian.

2.10.4.7 The coordinator shall be programmable to seek offsets by short-way (lengthening or shortening the cycle length up to 20%) and by dwell in the coordination phase awaiting the proper offset.

The user shall determine which method and may program the longest permissible dwell times.

2.10.4.8 The controller unit coordination program shall be designed to be programmed from the front panel to emulate the operation of a pre-timed controller by recall for applications where no vehicle detection is provided.

2.10.4.9 For each configuration a coordinated phase must be selected from Ring 1. A coordinated phase must also be selected from other rings if a compatible phase with the Ring 1 coordinated phase exists. The coordinated phase or phase pair shall be selectable from one of the individual phases or phase pairs shown in the following table:

CONFIGURATION

Coordinated

Phase(s) 8 Phase

NEMA dual ring and

3φ Diamond

Quad Sequential

8 Phase Sequential

4φ Diamond

Individual -- 4 or 8 2, 4, 6, or 8 Pairs 2 & 6 or

4 & 8 2 & 6 -- 2 & 5, 4 & 5, 1 & 6, or 1 & 8

Compatible phase pairs shall not be forced to begin simultaneously.

2.10.4.10When establishing its offset from the reference point the coordinator shall reference only the leading edge of the sync pulse, regardless of its width.

2.10.4.11 The internal coordination and upload/download programs shall not interfere with normal intersection operation except when changing ring structure in the controller or active phases.

These operations (changing ring structure and active phases) shall require a confirmation and put the controller in a flash condition and a restart sequence. The implementation of revised timing parameters loaded into the timer shall be programmed to occur only at points in the controller coordination cycles which do not alter the controller phase sequence. The controller unit may temporarily drop out of synchronization during the upload/download, but must continue to operate.

2.11 Time-Based Coordinator (TBC)

2.11.1 The internal reference sync pulse, from which the local offset is calculated, shall re-sync at midnight, or the re-sync shall be user programmable with a default to midnight. A pulse shall be generated whenever the time-of-day clock shows a time that is an exact multiple of the current cycle length after this resynchronization. In case of a power failure, re-sync shall be calculated from the programmed re-sync time. The power failure recovery routine shall accommodate the case of a power failure at midnight.

2.12 Diamond Operation

2.12.1 Program Requirements for Diamond Operation

2.12.1.1 Phase numbers shall be assigned to traffic movements as shown on the diamond intersection layout of Figure 1. Overlap A (OL A) is defined as phases 1+2. Overlap B (OL B) is defined as phases 5+6.

2.12.1.2 There shall be 6 additional user programmable overlaps. All additional overlaps shall be programmable through the keyboard and shall function as specified by TS-2.

2.12.1.3 The controller unit shall be programmable for 4 phase and 3 phase diamond operation as well as 2 independent 4 phase rings (separate intersection operation) as defined in Figure 2.

2.12.1.4 The following modes shall be available for each phase and for the intervals identified as special intervals in 3 phase and 4 phase operation:

1. Maximum recall

2. Minimum recall

3. Pedestrian recall

4. Detector locking and non-locking memory

5. Phase omit

2.12.1.5 The controller unit shall be designed to provide pedestrian phasing with phases 2, 4, 6, and 8.

2.12.1.6 All timing entries and displays shall be available for phases 3 and 7.

2.12.1.7 The operation of the controller unit as a 4 phase, 3 phase, or separate intersection operation diamond shall be keyboard selectable. This shall be overridden while under closed loop system control or by TBC control.

2.12.2 Four Phase Operation

2.12.2.1 The controller unit shall perform the sequences for 4 phase and/or 6 phase diamond operation defined in Figures 3a to 3f.

2.12.2.2 The normal 4 phase operation sequence shall be 25 → 45 → 16 → 18. The 6 phase operation sequence shall be 25 → 35 → 45 → 16 → 17 → 18.

2.12.2.3 The point at which operation may be switched from 4 phase to 3 phase operation shall be at the clearance interval 2516B or 2518B to the 3 phase clearance interval 2648.

2.12.3 Concurrent Timing Requirements

Refer to Figures 3a - 3f for the following descriptions:

A. Intervals 4516B and 4516C shall time concurrently with interval 16, however interval 16 may not terminate green until interval 4516C has timed out.

B. Intervals 3516B and 3516C shall time concurrently with interval 16, however interval 16 may not terminate green until interval 3516C has timed out.

C. Intervals 1825B and 1825C shall time concurrently with interval 25, however interval 25 may not terminate green until interval 1825C has timed out.

D. Intervals 1725B and 1725C shall time concurrently with interval 25, however interval 25 may not terminate green until interval 1725C has timed out.

E. All left to right internal clearance times (intervals 4518B, 4517B, 3518B, 3517B, 2518B, 2517B, 2516B) shall use the same timing settings for minimum green, extension, maximum green, yellow clearance, and red clearance.

F. All right to left internal clearance times (intervals 1845B, 1835B, 1745B, 1735B, 1645B, 1635B, 1625B) shall use the same timing settings for minimum green, extension, maximum green, yellow clearance, and red clearance.

G. Separate timing settings for minimum green, extension, maximum green, yellow clearance, and red clearance shall be provided for each of the 4 external clearance intervals (1825B, 1725B, 4516B, 3516B).

2.12.4 Diamond Detector Operation

2.12.4.1 The loop detector layout for 3 phase, 4 phase, 6 phase, or separate intersection diamond operation shall be as defined in Figure 4. The detector operation defined shall be automatically loaded when any diamond sequences are selected.

2.12.4.2 The controller unit software shall provide the logic for detector operation described below:

Detector 1 In 4 phase operation:

1. Shall call phase 6 if overlap A is not green and phase 7 is not called.

2. Shall call phase 6 if overlap A is not green and phase 8 is not called.

3. Extend intervals 2516B, 2517B, 2518B, 4517B, 4518B, 3517B, and 3518B.

In 3 phase operation: call and extend phase 1 (left turn)

Detector 5 In 4 phase operation:

1. Shall call phase 2 if overlap B is not green and phase 3 is not called.

2. Shall call phase 2 if overlap B is not green and phase 4 is not called.

3. Extend intervals 1625B, 1635B, 1645B, 1735B, 1745B, 1835B, and 1845B.

In 3 phase operation: call and extend phase 5 (left turn)

Detectors 2, 3, 4, 6, 7, and 8 These setback detectors (or detector sets) belong to the parent phases with the same number (e.g.

detector 2 belongs to phase 2) as shown in Figure 4. These detectors shall have a 2 second delay set during red conditions of their parent phase. The detector(s) are used to extend during green.

Detectors 11, 12, 15, 16, 17, and 18 These detectors are stop bar detectors and are used to call the associated parent phases shown in Figure 4. The parent phase green plus a call for that phase plus a 0.2 second gap on the detector shall disable the detector until the end of green.

Detectors 9 and 10 In 4 phase operation:

1. Shall extend phase 2 if phase 3 is called.

2. Shall extend phase 2 if phase 4 is called.

3. Shall call phase 6 if overlap A is not green and phase 7 is not called.

4. Shall call phase 6 if overlap A is not green and phase 8 is not called.

5. Extend intervals 2516B, 2517B, 2518B, 4517B, 4518B, 3517B, and 3518B.

In 3 phase operation: shall function as a phase 1 calling detector during phase 3 or 4 and as a phase 1 extending detector when a phase 3 or 4 call exists.

Detectors 13 and 14 In 4 phase operation:

1. Shall extend phase 6 if phase 7 is called.

2. Shall extend phase 6 if phase 8 is called.

3. Shall call phase 2 if overlap B is not green and phase 3 is not called.

4. Shall call phase 2 if overlap B is not green and phase 4 is not called.

5. Extend intervals 1625B, 1635B, 1645B, 1735B, 1745B, 1835B, and 1845B.

In 3 phase operation: shall function as a phase 5 calling detector during phase 7 or 8 and as a phase 5 extending detector when a phase 7 or 8 call exists.

2.12.5 Three Phase Operation

2.12.5.1 The controller unit shall be keyboard selectable for 3 phase diamond operation.

2.12.5.2 The controller unit shall perform the sequences for 3 phase diamond operation defined in Figures

5a to 5b.

2.12.5.3 The normal sequence of operation shall be 4+8 → 2+6 → 1+5.

2.12.5.4 The point at which operation may be switched from 3 phase to 4 phase operation shall be through the transition phase sequence to 4 phase interval 2516 as indicated in Figure 5a.

2.12.5.5 The controller shall be programmable for simultaneous gap operation for phases 4 and 8 in 3 phase operation to allow a phase to extend out of a green rest state. When the phase(s) to be serviced next conflicts with both phases being serviced, both concurrent phases must reach a green rest state together before they terminate. Termination of the max timer or application of a force off shall override this feature. The phases shall not be allowed to advance to a green interval beyond the rest state which might override defeat the simultaneous gap operation.

2.13 Coordination Control Hierarchy

2.13.1 When the system switch is in the system position, the controller unit shall be under the control of the master controller or TBC.

2.13.2 In the absence of any on-line closed loop system control by a master controller, the internal TBC shall control the coordinated, free, and flash operation of the intersection when the system switch is in the system position.

2.13.3 When a master controller brings the intersection on-line, its control shall supersede that of the internal time base coordination.

2.13.4 When the system switch is in the free position, the controller unit shall operate in a non-coordinated (free) mode.

2.14 Preemption (PE)

2.14.1 The internal preemptor supplied shall be easily programmable from the front panel for either railroad or emergency vehicle preemption sequences.

2.14.2 Phases shall be selectable such that a limited signal sequence may be operational during preempt

(PE). It shall be possible to add phases to this special limited sequence, which is not in the intersection sequence. This shall be accomplished without adding external logic.

2.14.3 The following intervals shall be provided as a minimum. Terminology may vary but the meaning must be clear. Additional unspecified intervals that may lead to confusion shall be programmable to zero. If abbreviations are used on the display, they shall be defined on the front panel. While in preemption, the display will clearly identify the intervals being timed as preempt intervals.

Yellow and red clearances from the phase timings may be utilized in place of the clearance intervals shown.

2.14.3.1 Preemption Timing Interval Definition

All intervals are sequential.

0. PE Delay - This time shall start immediately when the preempt command is received. It shall not affect the normal operation of the controller unit until the delay time out occurs.

This interval may be used for emergency vehicle (fire lane) preemption delay. If 0 time is set, the interval shall be omitted.

1. PE Minimum Duration - The preempt sequence shall not terminate until the preempt input signal is removed and the minimum duration time has expired.

2. PE Minimum Green - Any vehicle signal that is green at the time this interval becomes active shall not terminate unless it has been displayed for at least the time programmed in this interval. If 0 time is set the interval shall be omitted.

3. PE Minimum Walk - Preempt minimum walk time in seconds. A preempt initiated transition shall not cause the termination of a Walk prior to its display for this period.

4. PE Pedestrian Clearance - At the time of preempt call, Walk indications shall immediately change to pedestrian clearance interval. The pedestrian clearance interval shall not terminate unless it has been displayed for at least the time programmed in this interval. If 0 time is set, the interval shall be omitted.

5. PE Track Green - Signals programmed as track (or fire lane) signals shall remain green or be changed to green. All other signals shall be red. This interval shall be optionally programmable to zero during emergency vehicle PE.

6. PE Dwell Green - Minimum dwell time in seconds. This parameter controls the minimum timing for the dwell movement. The phase(s) allowed during the dwell interval shall be selectable to include all phases that do not cross the track. The dwell interval shall not terminate prior to the completion of preempt duration time, preempt dwell time, and the call is no longer present. Each signal shall be keyboard programmable for red, red flash, yellow flash or green. As an alternative, a limited cycle shall be programmable for use with railroad preempts.

7. PE Exit Pedestrian Clear - Preemption exit pedestrian clear time in seconds. This parameter controls the pedestrian clear timing for a Walk signal transition to the exit phase(s).

8. PE Exit Yellow - This interval shall provide a solid yellow clearance for indications that were green or flashing yellow. Red and flashing red displays shall display solid red.

9. PE Exit Red Clearance - This interval shall be an all red clearance in preparation for return to the normal cycle. Return phases shall be programmable from the keyboard.

10. PE Max Call - This interval is the amount of time that a preempt call may remain active and be considered valid. When the preempt call has been active for this amount of time, the controller shall return to normal operation. The preempt call shall be considered invalid until the call is no longer active.

2.14.3.2 Preempt Timing Interval Ranges

TIMING INTERVAL TIME

(Seconds)

INCREMENTS

(Seconds)

0. PE Delay (emergency vehicle preempt)

1. PE Minimum Duration

2. PE Minimum Green

3. PE Minimum Walk

4. PE Pedestrian Clearance

5. PE Track Green

6. PE Dwell Green

7. PE Exit Pedestrian Clear

8. PE Exit Yellow

9. PE Exit Red Clearance

10. PE Max Call

0-999 0-999 0-255 0-255 0-255 0-255 1-255 0-255

3.0-25.5 0-25.5 0-999

0.1 0.1

2.14.4 The phases to be serviced following the preempt sequence shall be front panel keyboard programmable.

2.14.5 Preempt sequences shall be selectable using external inputs. Preempt priority shall be assigned with number 1 being the highest. If a higher priority preempt input is received during a preempt sequence, the controller unit shall immediately transition to the new sequence subject to the constraints of PE minimum green and PE minimum walk. The transition shall take place in a safe manner from any point in the sequence meeting all Texas MUTCD requirements. Provisions shall be made to clear two conflicting track phases from a single preempt input. This may be provided by two track clearance phases for a single preempt or by combining two preempts.

2.14.6 Preempt 1 shall be reserved for a priority railroad preempt. If more than two preempts are provided it shall be possible to delete the priority override for all but the railroad preempt. If a non-priority preempt is activated during another preempt cycle, the one in progress shall continue through its entire cycle. If the second preempt input is still active when the first one is completed, the controller unit shall immediately go to all red flash or initiate the non-priority preempt. When all preempt inputs are removed, the controller unit shall proceed through the normal sequence to return red clearance (interval 9).

2.14.7 Once the controller unit has entered the first timed interval following preempt delay (interval 1), the sequence shall continue to the end even if the preempt call is dropped. If the call returns, the minimum preempt duration (interval 1) the controller unit should reinitiate track green and complete the preempt sequence.

2.14.8 The controller unit shall be programmable to be in flash or in limited sequence during interval 6.

If flash is specified, the phases shall flash yellow or red as programmed from the front panel.

Flash shall be implemented by simultaneously flashing the appropriate load switch driver outputs.

If limited sequence is selected, all phases shall be programmable even if not normally used in the intersection sequence.

2.14.9 In the event of a power interrupt as defined by TS-2, if the preempt command is present when power is restored, the controller unit shall power up in cabinet flash operation and remain there until the PE command is removed.

2.14.10 Overlap phases shall begin and terminate with the parent phases as described in TS-2. If the PE call occurs during yellow or red displays between parent phases, the overlap phase shall display a minimum of 3 seconds of yellow and a minimum of 1 second of red clearance.

2.14.11 Don't Walk shall be displayed throughout the preempt sequence unless a limited cycle is run.

During a limited cycle (interval 6) the pedestrian heads may be programmed to be dark.

2.14.12 Preempt routines shall have priority over all controller functions.

2.14.13 The controller shall be programmable to allow multiple track clearance phases either within a single preemption sequence or by mapping multiple preempts together in all modes of operation including 3 phase and 4 phase diamond modes.

2.15 NTCIP Compliance

2.15.1 The controller software shall comply with the referenced NTCIP standards when installed. The software shall comply with the versions of the relevant NTCIP standards that are current at the date of this document, or latest revision.

2.15.2 The software shall comply with NEMA Standard Publication TS-3.2 2003 (TS-3.2), or latest revision, the Simple Transportation Management Framework, and shall meet the requirements for Conformance Level 2. The software shall comply with NEMA Standard Publication

TS-3.3 2003 (TS 3.3), or latest revision, the Class B Profile, and shall include both an EIA/TIA 232-E and an FSK modem interface for NTCIP based communications.

2.15.3 The software shall implement all mandatory objects of all mandatory conformance groups as defined in Global Object Definitions, NEMA Standard Publication NTCIP 1201:1996 (TS 3.4), or latest revision:

• Configuration Conformance Group and Actuated Signal Controller Object Definitions, NEMA Standard Publication NTCIP 1202:1996 (TS 3.5), or latest revision.

• Phase Conformance Group

• Detector Conformance Group

2.15.4 The software shall implement all mandatory objects of all optional conformance groups as defined in Global Object Definitions, NTCIP 1201:1996, or latest revision:

• Database Management Conference Group

• Time Management Conformance Group

• Time Base Event Schedule Conformance Group

• Report Conformance Group

• STMF Conformance Group

• PMPP Conformance Group and Actuated Signal Controller Object Definitions, NTCIP

1202: 1996, or latest revision.

• Volume Occupancy Report Conformance Group

• Unit Conformance Group

• Special Function Conformance Group

• Coordination Conformance Group

• Time Base Conformance Group

• Preempt Conformance Group

• Ring Conformance Group

• Channel Conformance Group

• Overlap Conformance Group

• TS-2 Port 1 Conformance Group

2.15.5 The software shall also implement the following optional objects as defined in the Global Object Definitions, NTCIP 1201:1996, or latest revision:

• globalSetIDParameter

• dbMakeID

• eventLogOID

• eventConfigAction

• eventClassDescription

2.15.6 The software shall also implement the following optional objects as defined in the Actuated

Signal Controller Object Definitions, NTCIP 1202:1996, or latest revision:

• unitRedRevert

• phaseDynamicMaxLimit

• phaseDynamicMaxStep

• phaseControlGroupTable

• ringControlGroupForceOff

• vehicleDetectorQueueLimit

• vehicleDetectorFailTime

• vehicleDetectorReportedAlarms

• alarmGroupTable

• specialFunctionOutputTable

• preemptMinimumGreen

• preemptMinimumWalk

• preemptEnterPedClear

• preemptState

• preemptControlTable

• ringControlGroupMax2

• ringControlGroupMaxInhibit

2.15.7 All objects required by these procurement specifications shall support all values within its standardized range, unless otherwise approved by the Project Engineer. The standardized range is defined by a size, range, or enumerated listing indicated in the object’s syntax field and/or through descriptive text in the object’s description field of the relevant standard. The following provides the current listing of known variances for this project:

2.15.8 The controller shall be able to implement all NTCIP messages called for in the specification without any additional vendor specific/proprietary statements.

2.15.9 The software shall be supplied with full documentation, including a CD-ROM disk and/or other approved storage media containing ASCII versions of the following MIB files in ASN.1 format:

• the relevant version of each official NEMA standard MIB module referenced by the device functionality; and

• if the device does not support the full range of any given object within a NEMA standard MIB module, a manufacturer specific version of the official NEMA standard MIB module with the supported range indicated in ASN.1 format in the Syntax field of the Object-Type macro. The filename of this file shall be the same as the standard MIB filename with the extension “.man”.

2.15.10 The software shall be supplied with full documentation, including a CD-ROM disk or other approved storage media containing ASCII versions of any and all manufacturer-specific objects supported by the device in ASN.1 format in a manufacturer-specific MIB with accurate and meaningful description fields and supported ranges indicated in the syntax field of the object-type macros.

2.15.11 The manufacturer shall not place any restrictions as to the passage of any and all of this documentation to any portion of Ft Bend Co.

2.15.12 The manufacturer shall provide a copy of the following table that has been completed to describe the operation of their controller including which objects are used and the procedures that are done with these objects to implement the functions listed using NTCIP.

2.16 Flashing Yellow Arrow Operation. Provide a Flashing Yellow Arrow (FYA) routine that:

• is programmable in the controller unit,

• provides as a minimum for operation of up to 4 FYA left turn signal displays per the

MUTCD,

• uses data entries in the controller unit to define when the signal face displays the protected

(green arrow) and the permissive (flashing yellow arrow),

• can be programmed for permissive only, permissive-protected, or protected only operation by time of day, transition from FYA permissive-protected operation to protected only operation must be accomplished after concurrent termination of both the FYA and the associated opposing through movement.

3.0 MALFUNCTION MANAGEMENT UNIT (MMU)

3.1 This specification sets forth the minimum requirements for a shelf-mountable, 16 channel, solid-state MMU. The MMU shall meet as a minimum, Section 4 of the NEMA Standards Publication TS-2 2003, or latest revision. Where differences occur, this specification shall govern.

3.2 No circuit cuts shall be allowed on circuit boards in any of the equipment supplied. Any wire jumpers included on circuit boards shall be placed in plated through holes that are specifically designed to contain them. Jumpers that are tack soldered to circuit traces or that are added to correct board layout errors are not acceptable

3.3 All ICs with 16 or more pins shall be mounted in machine tooled sockets or surface mounted. All sockets shall have two-piece, machined contacts and closed end construction to eliminate solder wicking. The outer sleeve shall be brass with tin or gold plating and tapered to allow easy IC insertion. The inner contact shall be beryllium copper sub-plated with nickel and plated with gold. All sockets shall have thermoplastic bodies meeting UL Specification 94V-0. Other high quality sockets may be acceptable but must have prior approval of the Ft Bend County Traffic Engineer. Surface mount devices will be allowed. Sockets meeting alternate specifications shall be submitted in writing with the solicitation. Zero insertion force sockets will not be allowed.

3.4 The design shall allow for removal or replacement of a circuit board without unplugging or removing other circuit boards.

3.5 The unit shall be designed so that one side of each board can be completely accessible for troubleshooting and testing the unit while it is still operating. This may be accomplished with extender boards or cables. This need apply to only one circuit board at a time.

3.6 One set of extender boards (if required to meet Paragraph 3.5 above) for every 10 MMUs ordered or portion thereof shall be provided with the purchase order.

3.7 No more than two circuit boards shall be attached to each other to constitute a circuit assembly.

Attaching hardware shall use captive nuts or other acceptable method to secure the boards together. Alternate methods shall be submitted in writing with the solicitation. The boards shall be designed so Ft Bend Co can test and operate the controller unit with the boards separated.

3.8 If this specification is used to support the purchase of a complete controller assembly, the unused red circuits shall be connected to the AC Line in the controller cabinet.

3.9 The MMU shall be pre-programmed according to Table 3-1.

3.10 Provide an MMU that displays by LCD or other approved graphics display, the active or inactive state of each circuit on all 16 channels An icon must be used representing the red (Don’t Walk), yellow, and green (Walk) circuit for each channel.

3.11. The MMU must be compatible with the controller and capable of monitoring FYA operation as defined by the MUTCD and still provide standard NEMA TS-2 monitoring functions.

3.12 Each MMU shall have a unique serial number that is permanently and neatly displayed on the face of the unit. If this serial number is located elsewhere on the unit then an additional temporary label that is neatly printed or typed shall be affixed to the MMU face.

3.13 Provide the MMU with an Ethernet port on the front face of the unit.

4.0…