ITS Cabinet V2 StdRS v01.04 - Institute of …library.ite.org/getpub.cfm?path=standards/ITScabinet/... · Web viewITS Cabinet V2 StdRS v01.05 ITS Cabinet Version 2 Standards Requirements

A Working Group Draft of the Advanced Transportation Controller Joint Committee

ITS Cabinet V2 StdRS v01.05

ITS Cabinet Version 2Standards Requirements Specification (StdRS)

November 04, 2015

StdRS in support of: USDOT Work Order 14-0701, Tasks 7-12

For approval by: Members of the ITS Cabinet Working Group

For use by: Siva Narla, Chief Engineer and ITS Standards ManagerInstitute of Transportation Engineers

Ron Johnson and Robert Rausch, Co-ChairsITS Cabinet Working Group

Consulting Team for the ITS Cabinet V2 ProjectRalph W. Boaz, Project Manager/Systems EngineerBruce Eisenhart, Systems EngineerJames A. Kinnard, Technical Expert

Members of the ITS Cabinet Working Group

Prepared by: Ralph W. Boaz, Bruce Eisenhart and James A. Kinnard

Ó Copyright 2010 AASHTO/ITE/NEMA. All rights reserved.

document.doc Page 1 of 61


CHANGE HISTORY

DATE NOTE10/30/09 Initial Working Group Draft (WGD) Version 01.00.11/09/09 WGD v01.01. Revisions per WG review.06/18/10 WGD v01.02. Revisions per WG review.12/28/10 WGD v01.03. Revisions per WG meeting in Houston, TX and following teleconferences.01/31/10 WGD v01.04. Revisions per WG teleconferences.09/21/2015 Updated Traceabilty Table per Editor Notes



NOTICE

Joint NEMA, AASHTO and ITE Copyright andIntelligent Transportation Systems (ITS) Working Group

These materials are delivered "AS IS" without any warranties as to their use or performance.

NEMA, AASHTO, ITE AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. NEMA, AASHTO, ITE AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESSED OR IMPLIED, AS TO NON-INFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL NEMA, AASHTO, ITE OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL, OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF A NEMA, AASHTO OR ITE REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential, or special damages, or exclusion of implied warranties, so the above limitations may not apply to you.

Use of these materials does not constitute an endorsement or affiliation by or between NEMA, AASHTO or ITE, and you, your company, or your products and services.

If you are not willing to accept the foregoing restrictions, you should immediately return these materials.

ATC is a trademark of NEMA, AASHTO and ITE.



CONTENTS

1 PURPOSE OF THE DOCUMENT....................................................................92 SCOPE OF PROJECT...................................................................................93 REFERENCED DOCUMENTS......................................................................104 CONCEPT OF OPERATIONS.......................................................................11

4.1 User-Oriented Operational Description............................................................................114.2 System Overview.............................................................................................................144.3 User Needs...................................................................................................................... 16

4.3.1 General...............................................................................................................174.3.1.1 Open Architecture............................................................................................................174.3.1.2 Modular............................................................................................................................ 174.3.1.3 Scalable........................................................................................................................... 174.3.1.4 Expandable...................................................................................................................... 174.3.1.5 Extensible........................................................................................................................174.3.1.6 Space-Efficient.................................................................................................................174.3.1.7 Reliable and Continuous Operation.................................................................................174.3.1.8 Quality Construction.........................................................................................................184.3.1.9 Extreme Temperatures and Humidity..............................................................................184.3.1.10 Limit Electronic Emissions............................................................................................184.3.1.11 Limit Audible Noise.......................................................................................................184.3.1.12 Withstand Vibration and Shock.....................................................................................184.3.1.13 Quick Transfer of Configuration and Application Information........................................184.3.1.14 Nominal Service Power.................................................................................................184.3.1.15 User Safety...................................................................................................................184.3.1.16 Energy Efficient.............................................................................................................194.3.1.17 No Devices Containing Liquid Mercury.........................................................................194.3.1.18 Diagnostic Testing.........................................................................................................194.3.1.19 Electrostatic Discharge Resistant..................................................................................194.3.1.20 Minimize Time for Maintenance Personnel...................................................................19

4.3.2 Field Inputs.........................................................................................................194.3.2.1 Commonly Deployed Field Sensors.................................................................................194.3.2.2 High Density Input Devices..............................................................................................19

4.3.3 Application Computer..........................................................................................194.3.3.1 Application Computer Interface........................................................................................204.3.3.2 Intersection Control Applications......................................................................................204.3.3.3 Ramp Metering Applications............................................................................................204.3.3.4 Data Collection Applications............................................................................................20

4.3.4 Field Outputs.......................................................................................................204.3.4.1 High Density Output Devices...........................................................................................204.3.4.2 Electrically Safe Field Outputs.........................................................................................20

4.3.5 Fault Operation...................................................................................................204.3.6 TFCS Monitoring.................................................................................................21

4.3.6.1 TFCS Status.................................................................................................................... 214.3.6.2 Field Output Monitoring....................................................................................................214.3.6.3 Field Display Monitoring...................................................................................................214.3.6.4 Internal Communications Monitoring................................................................................214.3.6.5 User Interface.................................................................................................................. 214.3.6.6 Response to Malfunction or Anomaly..............................................................................21



4.3.6.7 Configuration of Monitoring..............................................................................................214.3.6.8 Controlled Access to Monitoring Configuration Information.............................................22

4.3.7 Power Filtering and Distribution..........................................................................224.3.7.1 Clean Power Distributed..................................................................................................224.3.7.2 Output Power Distributed.................................................................................................224.3.7.3 Power Conversion............................................................................................................224.3.7.4 Backup Power Provisions................................................................................................22

4.3.8 System Reporting................................................................................................224.3.8.1 System Reports...............................................................................................................224.3.8.2 System Reporting Distribution..........................................................................................234.3.8.3 Non-Volatile Information..................................................................................................23

4.3.9 External Communications...................................................................................234.3.9.1 External Communications Capability...............................................................................234.3.9.2 Standardize External Interfaces.......................................................................................23

4.3.10 Housing...............................................................................................................234.3.10.1 External Mounting.........................................................................................................234.3.10.2 Corrosion Resistant Material.........................................................................................234.3.10.3 Cabinet Access.............................................................................................................234.3.10.4 Physical Environment....................................................................................................244.3.10.5 Animal and Insect Resistant..........................................................................................244.3.10.6 Vandalism and Theft Resistant.....................................................................................244.3.10.7 Graffiti Resistant............................................................................................................244.3.10.8 Video Monitor Provision................................................................................................244.3.10.9 Battery Housing Provision.............................................................................................244.3.10.10 Law Enforcement Personnel Access............................................................................24

4.3.11 Internal Communications....................................................................................244.3.11.1 Internal Communications Capability..............................................................................254.3.11.2 Uniform Interfaces.........................................................................................................25

4.4 Operational Environment.................................................................................................254.5 Support Environment.......................................................................................................254.6 Operational Scenarios.....................................................................................................25

5 SYSTEM REQUIREMENTS.........................................................................265.1 General Characteristics...................................................................................................28

5.1.1 Open Interfaces...................................................................................................285.1.1.1 Patents and Copyrights....................................................................................................285.1.1.2 Commonly Available Components...................................................................................285.1.1.3 Open Standards...............................................................................................................28

5.1.2 Rack Mountable..................................................................................................285.1.3 Serial Bus Communications Architecture............................................................29

5.1.3.1 Connectivity................................................................................................................... 295.1.3.2 Allows Proprietary Data Messages..............................................................................29

5.1.4 Monitor Bus Architecture.....................................................................................295.1.5 Utilizes a Controller Subsystem..........................................................................295.1.6 Utilizes an Input Assembly..................................................................................295.1.7 Utilizes an Output Assembly...............................................................................295.1.8 Utilizes an Input/Output Assembly......................................................................295.1.9 Utilizes a Field Termination Assembly................................................................295.1.10 Utilizes a Monitor Assembly................................................................................305.1.11 Utilizes a Service Assembly................................................................................305.1.12 Utilizes a Serial Bus Assembly............................................................................305.1.13 Utilizes a Clean Power Bus Assembly................................................................305.1.14 Utilizes a Cabinet Power Supply.........................................................................30



5.1.15 Relocatable Elements.........................................................................................305.1.16 No Dark Condition...............................................................................................305.1.17 Legacy Housings.................................................................................................305.1.18 Small-Sized Cabinet............................................................................................305.1.19 Non-Standard Housing Sizes..............................................................................305.1.20 24/7 Operation....................................................................................................315.1.21 Welding Standards..............................................................................................315.1.22 Electronics Standards.........................................................................................315.1.23 Cable and Wire Harness Standards....................................................................315.1.24 Derating..............................................................................................................315.1.25 Storage Ambient Temperature............................................................................315.1.26 Operating Ambient Temperature.........................................................................315.1.27 Operational Relative Humidity.............................................................................315.1.28 Nominal AC Input Power.....................................................................................315.1.29 Power Factor.......................................................................................................315.1.30 Power Supply Efficiency......................................................................................315.1.31 Audible Noise Level............................................................................................325.1.32 Shock.................................................................................................................. 325.1.33 Vibration..............................................................................................................325.1.34 Electrostatic Discharge (ESD) Resistant.............................................................325.1.35 Electronic Emissions...........................................................................................325.1.36 Environmental Testing........................................................................................325.1.37 Packaging...........................................................................................................335.1.38 No Sharp Edges..................................................................................................335.1.39 NEC Best Practices.............................................................................................335.1.40 No Liquid Mercury...............................................................................................335.1.41 Documentation....................................................................................................335.1.42 Subsystems not Interdependent..........................................................................335.1.43 Subsystem Quantities.........................................................................................335.1.44 Future Subsystems.............................................................................................335.1.45 MTBF.................................................................................................................. 345.1.46 Design Life..........................................................................................................345.1.47 Output Power Distribution...................................................................................345.1.48 Externally Accessible SB3 Bus...........................................................................34

5.2 Controller Subsystem....................................................................................................345.2.1 Controller Subsystem Communication Interfaces...............................................34

5.2.1.1 Receives Field Input Data................................................................................................345.2.1.2 Receives Detector Status Information..............................................................................345.2.1.3 Sends Field Output Commands.......................................................................................355.2.1.4 Sends Switch Pack Driver Information to the Monitor Assembly......................................355.2.1.5 Sends Flash Command to the Monitor Assembly............................................................355.2.1.6 Receives CMU Programming Information from the Monitor Assembly............................355.2.1.7 Signal Control Priority......................................................................................................35

5.2.2 External Communications...................................................................................355.2.3 Intersection Control Applications.........................................................................355.2.4 Ramp Meter Control Applications........................................................................355.2.5 Data Collection Applications...............................................................................35

5.3 The TFCS Controller Subsystem shall support Data Collection Applications developed for the ITS Cabinet V1 without modifications [TR112]Input Assembly...............................................35

5.3.1 Input Assembly Communication Interfaces.........................................................355.3.1.1 Sends Field Input Data....................................................................................................365.3.1.2 Sends Detector Status Information..................................................................................36

5.3.2 Commonly-Deployed Field Input Devices...........................................................36



5.3.3 NEMA TS 2 Four-Channel Detector Modules.....................................................365.3.4 Four-Channel Isolator Modules...........................................................................365.3.5 48 Input Channels...............................................................................................365.3.6 Plug-In Input Devices..........................................................................................365.3.7 Hot-Swappable Input Devices.............................................................................365.3.8 Multiple Input Assemblies...................................................................................36

5.4 Output Assembly..............................................................................................................375.4.1 Output Assembly Communication Interfaces......................................................37

5.4.1.1 Receives Field Output Commands..................................................................................375.4.1.2 Send Current Levels to the Monitor Assembly.................................................................375.4.1.3 Send Voltage Levels to the Monitor Assembly.................................................................37

5.4.2 Up to Seven High Density Switch Pack Modules................................................375.4.3 120 VAC Switch Pack Modules...........................................................................37

5.4.3.1 Two Ouput Channels per HDSP120................................................................................375.4.3.2 Three Signal Indications per HDSP120 Channel.............................................................375.4.3.3 Ampres per HDSP120 Channel.......................................................................................385.4.3.4 HDSP120 Indicators........................................................................................................38

5.4.4 Low Voltage Switch Pack Modules.....................................................................385.4.4 Supported Field Display Devices........................................................................385.4.5 Plug-In Switch Pack Modules..............................................................................385.4.6 Output Circuit Breakers.......................................................................................385.4.7 Electrically Paired with a Field Termination Assembly........................................385.4.8 Multiple Output Assemblies.................................................................................385.4.9 Pluggable from the Front.....................................................................................385.4.10 Regular Density Output Files..............................................................................39

5.5 Input/Output Assembly.....................................................................................................395.5.1 Up to 16 Input Channels.....................................................................................395.5.2 Up to Three Switch Pack Modules......................................................................395.5.3 Adheres to Input Assembly Requirements..........................................................395.5.4 Adheres to Output Assembly Requirements.......................................................395.5.5 High Density Inputs.............................................................................................39

5.6 The TFCS shall provide a high-density input assembly capable of directly supporting 12 current-technology four-channel NEMA TS-2 detector modules using half-width front panels in each single-width slot. [TR4] [TR34] [TR95]Field Termination Assembly.....................................39

5.6.1 Field Wire Termination........................................................................................395.6.2 Relay...................................................................................................................395.6.3 Channel-Programmable Flasher Outputs............................................................395.6.4 Transient Suppression........................................................................................405.6.5 Electrically Paired with an Output Assembly.......................................................405.6.6 Multiple Field Termination Assemblies................................................................40

5.7 Monitor Assembly..........................................................................................................405.7.1 Monitor Assembly Communication Interfaces.....................................................40

5.7.1.1 Receives Switch Pack Driver Information from the Controller Subsystem.......................405.7.1.2 Receives Flash Command from the Controller Subsystem..............................................405.7.1.3 Sends CMU Programming Information to the Controller Subsystem...............................405.7.1.4 Receives Current Levels from the Output Assembly........................................................405.7.1.5 Receives Voltage Levels from the Output Assembly.......................................................415.7.1.6 Ethernet Communications............................................................................................415.7.1.7 Externally Accessible Voltage and Current......................................................................41

5.7.2 Cabinet Monitor Unit...........................................................................................415.7.3 CMU Display Unit................................................................................................415.7.4 Flasher Unit.........................................................................................................41

5.7.4.1 Four Fused Output Channels........................................................................................41



5.7.4.2 Sychronized Flashers....................................................................................................415.8 Clean Power Bus Assembly..........................................................................................41

5.8.1 Clean Power Distribution.....................................................................................425.8.2 Clean Power Receptacles...................................................................................42

5.9 Service Assembly..........................................................................................................425.9.1 Output Power......................................................................................................425.9.2 Clean Power.......................................................................................................425.9.3 Convenience Receptacle....................................................................................425.9.4 Main Power Breaker Switch................................................................................425.9.5 Facilities Breaker Switch.....................................................................................425.9.6 Backup Power Subsystem..................................................................................425.9.7 Service Power Input Options...............................................................................42

5.9.7.1 High Voltage Service Assembly.......................................................................................435.9.7.2 The TFCS shall include a Service Assembly option for 120 VAC, 60 Hz nominal service power input. [TR150]Low Voltage Service Assembly.....................................................................43

5.10 Cabinet Power Supply...................................................................................................435.10.1 Clean Power Input...............................................................................................435.10.2 Input Power Indicator..........................................................................................435.10.3 Fused Input Power..............................................................................................435.10.4 24 VDC Power Output.........................................................................................435.10.5 12 VDC Power Output.........................................................................................435.10.6 Output Power Indicators......................................................................................435.10.7 Fused Output Power...........................................................................................44

5.11 Serial Bus Assembly.....................................................................................................445.11.1 Serial Bus Ports..................................................................................................44

5.12 Housing........................................................................................................................... 445.12.1 Corrosion Resistant.............................................................................................445.12.2 Aluminum Sheet..................................................................................................445.12.3 Aluminum Sheet Plating......................................................................................445.12.4 Stainless Steel Sheet..........................................................................................445.12.5 Cold Rolled Steel................................................................................................445.12.6 Cold Rolled Steel Plating....................................................................................445.12.7 Stainless Steel Hardware....................................................................................455.12.8 Doors.................................................................................................................. 455.12.9 Ventilation...........................................................................................................455.12.10 Cabinet Thickness...............................................................................................455.12.11 Rodent Resistant.................................................................................................455.12.12 High Security Design...........................................................................................455.12.13 Cabinet Surface Preparation...............................................................................455.12.14 Video Monitor......................................................................................................455.12.15 Backup Power Batteries......................................................................................455.12.16 Law Enforcement Access....................................................................................465.12.17 External Antenna.................................................................................................465.12.18 Limited Enclosure Access...................................................................................46

5.13 Diagnostic and Status Monitoring....................................................................................465.13.1 Diagnostic Display Unit Local Display.................................................................465.13.2 Diagnostic Time Required...................................................................................46

6 APPENDICES...........................................................................................476.1 Compliancy......................................................................................................................476.2 Acronyms.........................................................................................................................476.3 Glossary........................................................................................................................... 496.4 Needs to Requirements Traceability................................................................................50



1 PURPOSE OF THE DOCUMENT

This document is a Standards Requirements Specification (StdRS) for the Intelligent Transportation System (ITS) Cabinet Version 2 (V2) project under the United States Department of Transportation (USDOT) Work Order 14-0701, Tasks 7-12. It combines Concept of Operations (ConOps) adapted from Section 8.4.5 of the "Systems Engineering Guidebook for ITS" (see Section 3 Referenced Documents) with system requirements derived from the user needs identified in the ConOps as a step in the process to create the ITS Cabinet Standard Version 2. This StdRS describes the high-level system concept, defines the environment in which the ITS Cabinet V2 system will operate, identifies the user and system needs, and establishes the system requirements for:

a) The USDOT Joint Program Office (JPO) who is sponsoring the work;

b) The Standard Development Organizations (SDOs) overseeing the development; and

c) The consultants, manufacturers, and public transportation professionals from both the public and the private sectors who participate in the committees and working groups (WGs) which will develop the subsequent work products based on this StdRS.

The majority of the content of this document will be included in the ITS Cabinet Standard Version 2. When this occurs, this StdRS document will no longer be maintained by the ITS Cabinet WG.

2 SCOPE OF PROJECT

The ITS Cabinet V2 project is sponsored by the USDOT JPO as part of an ITS Standards Development Program. The project is to be performed under the direction of the Advanced Transportation Controller (ATC) Joint Committee (JC). The ATC JC is made up of representatives from three SDOs: the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE) and the National Electrical Manufacturers Association (NEMA). The development effort will be carried out by the ITS Cabinet WG,a technical subcommittee of the ATC JC, and a paid consultant team.

The ITS Cabinet Standard Version 1.02.17b (also known as Version 1 or V1, see Section 3 Referenced Documents) was published in 2006. It defined a transportation field cabinet system (TFCS) that was highly modular and expandable but the standard was missing formalized user needs and requirements that come from the rigor of a Systems Engineering Process (SEP). The objectives of the ITS Cabinet V2 project are as follows:

1) Develop ITS Cabinet Standard V2 assessing issues and integrating lessons learned from current deployments of the ITS Cabinet Standard into a Concept of Operation, requirements and design. User needs to be considered, but are not limited to: low-power features, items referred to as "B-List" items by the ITS Cabinet WG, and mercury relay replacement. These items along with all others solicited will be introduced into the Systems Engineering Process (see objective #2) to examine their relevancy.

2) Use a systems engineering process to ensure the completeness and correctness of ITS Cabinet Standard V2 and associated documents. The standard must be traceable and logically consistent.

3) Develop a detailed conformance statement that addresses backwards compatibility and provides clear and unambiguous instruction on how to extend the standard.



3 REFERENCED DOCUMENTS

"2008 National Electrical Code," National Fire Protection Association (NFPA), 2008. Available from numerous sources.

“ATC Controller Standard Revision v5.2b,” ATC JC, 26 June 2006. Available from the Institute of Transportation Engineers.

"Electromagnetic Compatibility (EMC) - Part 4-2: Testing and Measurement Techniques - Electrostatic Discharge Immunity Test," IEC 6100-4-2:2008. Available from the International Electrotechnical Commission.

“Intelligent Transportation System (ITS) Standard Specification for Roadside Cabinets v01.02.17b,” ATC JC, 16 November 2006. Available from the Institute of Transportation Engineers.

“NEMA Standards Publication TS 2-2003 v02.06 Traffic Controller Assemblies with NTCIP Requirements," 1 January 2003. Available from National Electrical Manufacturers Association.

"Systems Engineering Guidebook for ITS Version 2.0," FHWA, 2 January 2007. Available from the Federal Highway Administration, California Division.

"Work Order 14-0701 NTCIP and ITE Standards Development," USDOT JPO, 29 May 2007. Available from the Institute of Transportation Engineers.



4 CONCEPT OF OPERATIONS

This section provides background and justification for the TFCS defined by this StdRS. It describes the operational use of the TFCS from the user's point of view, it gives a high-level architecture of the TFCS and explicity identifies user needs for the system.

4.1 User-Oriented Operational Description

The focus of this StdRS and resulting standard is on supporting applications related to traffic management. Specifically, user needs for managing vehicle right-of-way at signalized intersections (also known as intersection control), highway on-ramp access control (also known as ramp metering), and traffic data collection are identified (see Figure 1). While a TFCS may be used in support of other ITS applications such as automated toll collection, dynamic message sign control and others, the user needs for these applications are not specifically identified herein.

The TFCS can either be the primary field system of a transportation agency or it can be a subsystem of other applications that are the responsibility of other agencies. The TFCS is not a complete solution for any application but a standardized hardware platform/housing that can be used for applications that require field equipment. To be a complete solution, the applications’ operational software must be specified and the appropriate hardware configuration of the TFCS identified.

INTERSECTION CONTROL

DATA COLLECTION

RAMP METERING

ONE VEHICLEPER GREEN

INTERSECTION CONTROL

DATA COLLECTION

RAMP METERINGRAMP METERING

ONE VEHICLEPER GREEN

Figure 1. Three of the traffic management applications supported by TFCSand covered by this StdRS.



There are various field architectures for performing traffic management. A TFCS may operate as: 1) A standalone system at a single field location (e.g. single intersection, ramp meter or road side

(for data collection)); 2) A system under the direct "supervisory control" of a central system; 3) A system under the supervisory control of another TFCS (e.g. in a closed-loop system or second

TFCS acting as a slave to another TFCS for a large scale intersection application); or 4) Some combination of the first three (see Figure 2).

The term "supervisory control," as used here, implies messages typical of any distributed control system including configuration messages, control messages, status messages, historical reports, and files.

Standalone TFCSs are used when an agency does not use a central system, the location does not have the appropriate communications infrastructure available, or it is simply determined that a supervisory capability for the TFCS at the location is not necessary. When a TFCS is a part of a central system, the TFCS is connected directly or indirectly (routed through other systems or infrastructures) to the central system through a communications infrastructure (e.g. fiber optic, copper, leased lines, dial-up phone lines, etc.). The central system may have intermittent, periodic or sometimes continuous communications with the TFCSs.

When a TFCS is a part of a closed-loop system, the TFCS is connected directly or indirectly to one or more TFCSs through a communications infrastructure. A field management station application program in the supervisory TFCS provides intermittent, periodic or continuous communications with the connected TFCSs. Hybrid field architectures are often found when an agency combines previously standalone and closed-loop systems together under the same supervisory central system.



TFCSs in a Closed-Loop System

TFCSs UnderCentral Control

StandaloneTFCSs

Hybrid –TFCSs in a Closed-Loop

System andUnder Central Control

FMS

FMS

FMSTFCS TFCS with a Field Management

Station Application ProgramSupervisoryCommunications

FMSFMSTFCS TFCS with a Field Management

Station Application ProgramSupervisoryCommunications

Figure 2. TFCSs can be standalone units, under control of other TFCSs (closed-loop system), under the control of a central office (central system) or in a hybrid arrangement.

The users of a TFCS can vary from agency to agency. Small cities or towns without formal transportation departments may consider only supervisory personnel at a remote office as the users of the TFCS. Large cities may have permanent staff that install, configure, monitor and maintain the TFCS and will consider all of their personnel that interact with the cabinet in the field as users (see Figure 3). For the purposes of this StdRS, the users of the TFCS are listed below. It should be noted that motorists and pedestrians are considered beneficiaries of the TFCS, not users.

Traffic Maintenance Technicians – These individuals are required to troubleshoot and repair TFCS failures through wiring, part, module susbsystem or assembly replacement. They may be trained by the agency or participate in International Municipal Signal Association (IMSA) courses for certification in the maintenance and repair of traffic management devices.

Traffic Operations Engineers and Staff – These individuals are responsible for specifying the TFCS and its internal configuration based on standardized elements (e.g. assemblies, subsystems, modules and parts). They create the procurement documents, the field wiring documents, and field location design.



Traffic Engineers / Transportation Supervisors – These individuals have knowledge of traffic control policies and practices. They establish the processes and procedures for the use of field location equipment and central systems. They typically understand how to program and configure field location equipment although they may not perform this task operationally. They are responsible for the overall performance of the traffic management infrastructure. They are the end user of the TFCS.

Communications Engineers – These individuals understand computer based communications systems, networking, wired and wireless connectivity, peer-to-peer and central-to-field communications, etc. They are also responsible for IT policies, network performance, network security and troubleshooting communications issues.

Law Enforcement Personnel – These individuals use the TFCS to assist in the localized management of emergencies and special events. They typically have limited access to the cabinet subsystems and assemblies and only have the ability to enable, disable, and apply limited local control at the cabinet. This usually means being able to place the TFCS into a safety backup operation or manually changing the states of the field outputs (e.g. traffic signals changing Green-Yellow-Red).

Remote UsersField Users Remote UsersRemote UsersField UsersField Users

Figure 3. TFCS operational users can be field personnel or remote users via other systems (central systems).

4.2 System Overview

The TFCS logical architecture including the system data flows for traffic management applications and the system boundaries are illustrated in Figure 4. This is not intended to be a design but more of a structure for describing the user needs (Section 6) in terms of the functional elements of the TFCS. The functional elements from Figure 4 are described below.

Field Inputs – This functional element provides for interfaces to the most common vehicle and pedestrian detection technologies in use today including inductive loops, video image processing,



microwave radar, pedestrian detection, magnetometers, acoustic, piezoelectric, optical, and others. This may also include sensing of more specialized operations such as railroad crossings and vehicle preemption/priority requests. The detection technology employed may have various means of bringing the raw sensor data into the TFCS. The raw sensor information is converted to standardized messages (field input data) and sent to the Application Computer for interpretation by an operational program.

Application Computer – This functional element provides for a field computer which executes the operational programs of the TFCS. For traffic management applications, the Application Computer must accept field input data and execute appropriate changes to the field outputs. It must communicate with the Cabinet Monitoring functional element in a manner that supports the monitoring of the cabinet functions for pre-determined error conditions. Operational programs may also require status information from the Cabinet Monitoring functional element. The Application computer also communicates with systems external to the TFCS via the External Communications functional element.

Field Outputs – This functional element provides for interfaces to the most common display technologies in use today including incandescent bulbs and light emitting diodes (LEDs). The application computer must be able to access the field output circuits to cause the appropriate changes of state to meet the functional needs of the application. The Field Outputs will switch power to the Traffic Management Displays or other devices accordingly.

Cabinet Monitoring – This functional element provides a means in which to ensure that the TFCS is operating properly. It validates that power levels are within tolerances and the TFCS internal communications are properly taking place. It also validates that the field output data and electrical outputs (e.g. voltages and current) to the various field displays are consistent. It may also be expected to verify minimum timing requirements for the Traffic Management Displays where appropriate. The Cabinet Monitoring functional element can put the TFCS into a safety backup operation or other fault condition should an anomaly occur.

Power Filtering and Distribution – This functional element provides reliable and appropriate power to the devices and subassemblies contained in the TFCS. It also explicitly provides power to the Cabinet Monitoring functional element so that the power levels can be assessed.

System Reporting – This functional element provides external reports of various forms representative of the assessment of the Cabinet Monitoring functional element.

External Communications – This functional element provides for communications outside the TFCS using remote field communication technologies (e.g. fiber optic, copper, leased lines, dial-up phone lines, etc.). This external communications capability may be used in support of a secondary TFCS, a closed-loop system or a central system. The External Communications functional element via standardized TFCS internal messages. They are then converted to the appropriate field communication technology.

Housing (not shown in Figure 4) – This functional element includes the cabinet housing, cabinet finish, doors, latches/locks, hinges and door catches, gasketing, ventilation, assembly supports and mounting.

Internal Communications (not shown in Figure 4) – This functional element provides for the internal communications between the other functional elements of the TFCS (except Housing).



FieldSensors

FieldInputs

Application Computer

FieldOutputs

PowerFiltering &

Distribution

Field Displays & Other Devices

Cabinet Monitoring

SystemReporting

ExternalCommuni-

cations

Central System or

Other TFCS

ExternalPower

External Reporting

System

Emergency Flash

Control

Raw Sensor Information

FieldOutput

Data

Selected Output

Power To Displays

FieldInput Data

System Status &

Config Info

Field OutputData

OutgoingMessages

Field OutputMeasurements

IncomingMessages

ExternalOutgoing Messages

External IncomingMessages

Cabinet Status &Historical Info

Service Power

Output Power

SystemReports

TFCSComponents

Clean PowerNotes: “Housing” functional element not shown as

it has no logical data flows. “Internal Communications” functional

element not shown for purposes of clarity. “TFCS Components” is not a functional

element but refers to all of the TFCS components that require “Clean Power” to operate.

Output Power

Figure 4. The TFCS logical architecture.

4.3 User Needs

This section identifies the user needs for the TFCS. Each user need is listed separately with a paragraph number. The rationale behind the need is included. Not all user needs will actually be addressed by every TFCS configuration. Conditions or constraints in such circumstances will be found in the subsequent requirements for the need. The TFCS requirements and design will be based on these needs and included in the subsequent standard based upon this StdRS.



The user needs are listed in the following categories: General, Field Inputs, Application Computer, Field Outputs, Cabinet Monitoring, Power Filtering and Distribution, System Reporting, External Communications, Housing and Internal Communications.

4.3.1 General

This section identifies the user needs that apply across all of the functional elements of the TFCS.

4.3.1.1 Open Architecture

The user needs the TFCS to be specified as an open architecture system. This is an open standard for the TFCS and any manufacturer/developer should be able to build products for this system.

4.3.1.2 Modular

The user needs the TFCS to be specified with a modular internal structure. Modular means having an internal structure such that there is separation in the functions of its subsystems and assemblies and flexibility in the way they are combined. Modularity reduces time to configure a system, reduces time in the field to maintain the system, it increases the utility of the system and increases testability of the system.

4.3.1.3 Scalable

The user needs the TFCS to be scalable. Scalable means that it can be deployed as a solution to a range of user applications. There are applications of the TFCS that range from small central business district applications to large arterial intersections.

4.3.1.4 Expandable

The user needs the TFCS to be expandable. Expandable means that it can be deployed as a solution for an application and if the application later requires more capability, it can be readily accommodated. An example would be switch packs or detection devices that are added to a TFCS when a lane or signal head is added to a field location.

4.3.1.5 Extensible

The user needs the TFCS to be extensible. Extensible means that the system is designed to allow extensions to the aspects of the system such as interfaces defined by the standard to accommodate local needs. The standard will define interfaces for the internal assemblies. Users may want to define additional capabilities (e.g. additional diagnostic messages). The standard will be created to make this a manageable process.

4.3.1.6 Space-Efficient

The user needs the TFCS to be space-efficient. Physical space externally and internally is a concern to many users. Space efficiency allows users the choices of using a smaller cabinet enclosure, gaining space for internal expansion, or for higher density internal devices.

4.3.1.7 Reliable and Continuous Operation

The user needs the TFCS to be designed for reliable and continuous operation without user intervention. The TFCS will perform traffic management operations at signalized intersections where any downtime is considered a safety concern. In other applications, such as ramp metering and traffic monitoring,



downtime has a negative effect on traffic flow, data collection and traveler information systems. The TFCS will be deployed at field locations and along roadsides where it could be hours before a technician can correct a failed element. This need does not exclude temporary system down time for periodic planned maintenance or the occasional replacement of failed elements.

4.3.1.8 Quality Construction

The user needs the TFCS to be constructed using quality standards for workmanship, electronic design and manufacturing. Adherence to applicable standards such as those from the American Welding Society and the IPC-Association Connecting Electronics Industries is important to developing a system that will reliably provide the continuous operation of the system.

4.3.1.9 Extreme Temperatures and Humidity

The user needs the TFCS to operate under extreme hot, cold and humid environmental conditions. The TFCS must operate year round in the diverse climates of North America including the extremes of Alaska, central Arizona and the areas surrounding the Gulf of Mexico.

4.3.1.10 Limit Electronic Emissions

The user needs the TFCS to have limited electronic emissions that cause radio frequency interference (RFI) and electromagnetic interference (EMI). RFI must be limited as to not interference with radios and cell phones in the vicinity of the cabinet. EMI must be limited to avoid interference with the operation of electronic elements used within the TFCS.

4.3.1.11 Limit Audible Noise

The user needs the TFCS to have limited audible noise. TFCSs will be deployed in areas where residents are sensitive to ambient sound.

4.3.1.12 Withstand Vibration and Shock

The user needs the TFCS to withstand vibration and shock. This would include common roadside and bridge vibrations due to vehicle traffic. This need also includes the vibration and shock of occasional events such as common carrier shipping, earthquakes, roadwork, etc.

4.3.1.13 Quick Transfer of Configuration and Application Information

The user needs the TFCS to provide a means to quickly transfer cabinet and application data from an external computer to a TFCS or from one TFCS to another. The mechanism must be able to be left in the cabinet, store the most updated cabinet information, and be used to transfer this information to a replacement cabinet in case of a "knock down."

4.3.1.14 Nominal Service Power

The user needs the TFCS to be accept a nominal service power of 120 volts alternating current (VAC) at 60 hertz (Hz). This is the typical service power provided in North America.

4.3.1.15 User Safety

The user needs the TFCS to be safe for use by field personnel. This safety need includes electrical safety where users are protected from high voltage wiring, arc flash hazards, and physical safety from sharp edges and falling objects.Need for UL approval deleted by 9-13-2010 WG vote 11-0-1 [TR2] [TR36]



4.3.1.16 Energy Efficient

The user needs the TFCS to be energy efficient. The goal is to minimize the average power consumption of the cabinet and its contents. Agencies are concerned with greenhouse gases and energy costs.

4.3.1.17 No Devices Containing Liquid Mercury

The user needs the TFCS to be designed so that it uses no devices containing liquid mercury. Liquid mercury devices are considered an environmental hazard and are in the process of being prohibited across the North America.

4.3.1.18 Diagnostic Testing

The user needs the TFCS to be designed to support diagnostic testing. This includes the TFCS as a whole its and elements. Users must be able to easily confirm proper operation and identify failed elements.

4.3.1.19 Electrostatic Discharge Resistant

The user needs the TFCS to be resistant to electrostatic discharge (ESD). It is common for there to be ESD when maintenance personnel interact with the TFCS. The TFCS needs to be designed to dissipate ESD to avoid damaging electronic elements.

4.3.1.20 Minimize Time for Maintenance Personnel

The user needs the TFCS to be of a design that reduces the time required for maintenance personnel to perform maintenance actions in the field. When a TFCS is being repaired there can be a safety hazard for both the motorist and the field maintenance personnel. The TFCS must be designed for quick diagnostics, element switch out, and TFCS expansion.

4.3.2 Field Inputs

This section identifies the user needs of the TFCS related to the Field Inputs functional element.

4.3.2.1 Commonly Deployed Field Sensors

The user needs the TFCS to support the use of commonly deployed field sensors (external to the cabinet). These field sensors include inductive loops, pedestrian detectors, vehicle preemption devices, transit priority devices, as well as a wide variety of vehicle detection and monitoring devices. This need stems from the desire to extend the use of existing infrastructure.

4.3.2.2 High Density Input Devices

The user needs the TFCS to support input devices that have higher channel density than commonly deployed field input devices. This need supports the long term trend in the industry to create higher density devices, which can have advantages in reliability or reduce the size of the cabinet needed to support a specific number of field sensors.

4.3.3 Application Computer

This section identifies the user needs of the TFCS related to the Application Computer functional element.



4.3.3.1 Application Computer Interface

The user needs the TFCS to have an application computer that supports the cabinet interfaces defined in this standard. The ITS Cabinet V2 Standard will provide only the definition of the interface between the cabinet and the application computer. Application computers are defined in their own standards. These interfaces provide a universal interface to the field inputs, the field outputs and the cabinet monitoring functional elements of the TFCS.

4.3.3.2 Intersection Control Applications

The user needs the TFCS to have configurations suitable for intersection control applications. This is also known as the management of vehicle right-of-way at signalized intersections. Included in this application area are railroad preemption, emergency vehicle preemption and signal priority. This has been identified as one of major application areas of the TFCS.

4.3.3.3 Ramp Metering Applications

The user needs the TFCS to have configurations suitable for ramp metering applications. Ramp metering manages vehicle access to highways via the use of control devices such as traffic signals, signing, and gates to regulate the number of vehicles entering the highway in order to achieve operational objectives. This has been identified as one of major application areas of the TFCS.

4.3.3.4 Data Collection Applications

The user needs the TFCS to have configurations suitable for roadside data collection applications. Data collection is needed to produce information used by suppliers of transportation services to improve operational, planning, and investment decisions; and by consumers of these services to improve their travel choice. This has been identified as one of major application areas of the TFCS.

4.3.4 Field Outputs

This section identifies the user needs of the TFCS related to Field Output functional element.

4.3.4.1 High Density Output Devices

The user needs the TFCS to support the use of output devices that have higher channel density than the commonly deployed field output devices [TR96]. This need supports the long term trend in the industry to create higher density devices, which can have advantages in reliability or reduce the size of the cabinet needed to support a specific number of output displays.

4.3.4.2 Electrically Safe Field Outputs

The user needs the TFCS to provide for field wiring that is at voltage and current levels below those dangerous to humans. [TR1] This provides protection in the case of a “knock down” of a pole supporting one or more field displays during a storm or traffic accident.

4.3.5 Fault Operation

The user needs the TFCS to support configurable continued operation based on the specifics of the element failures. For example, in the event of a single short circuit in the field wiring supplying the operating voltage to a field display, it may be desirable to power down the shorted circuit and continue “normal operation” on the remaining circuits as preferable to traditional flashing operation.



4.3.6 TFCS Monitoring

This section identifies the user needs of the TFCS related to the Monitoring functional element.

4.3.6.1 TFCS Status

The user needs the TFCS to provide a status monitoring capability. This includes monitoring of door status, UPS status, law enforcement personnel controls, and cabinet temperature devices. The center that remotely manages the TFCS as well as the field maintenance personnel want to see the operational status of the cabinet.

4.3.6.2 Field Output Monitoring

The user needs the TFCS to provide a configurable field output monitoring capability. This includes independent monitoring of each field output voltage and current level. At a minimum, this needs to be at a level of capability described in Section 4 of the NEMA TS2 Standard (see Section 3 Referenced Documents). In order to identify and to react to potentially unsafe conditions, the TFCS must be able to detect when an unsafe conditions exists.

4.3.6.3 Field Display Monitoring

The user needs the TFCS to provide a configurable capability to independently monitor each field display to ensure that the actual state of the field display matches the state of its corresponding application computer output, and indicates an anomaly when they do not match. This provides confirmation that field displays and other devices (e.g. “prepare to stop” and “stopped traffic ahead”) will be as commanded, otherwise, the TFCS will be placed in a benign state.

4.3.6.4 Internal Communications Monitoring

The user needs the TFCS to monitor internal communications. This monitoring is to detect improper operations of the internal communications.

4.3.6.5 User Interface

The user needs the TFCS to provide a display for the maintenance personnel to view the malfunction, anomaly, or status information. Some of the assemblies typically put into the TFCS do not have any display of their outputs and this need would correct that condition.

4.3.6.6 Response to Malfunction or Anomaly

The user needs the TFCS to be capable of a configurable response to each malfunction or anomaly detected as part of system monitoring. The monitoring capability allows the center or field personnel to detect malfunctions or anomalies within the TFCS. It is important for the TFCS to provide the most appropriate action in response to each malfunction or anomaly that is detected.

4.3.6.7 Configuration of Monitoring

The user needs the TFCS to have a configurable monitoring capability. The different types of monitoring described in this section should in general be configurable so that the definition of a malfunction or anomaly can be defined by the system user.



4.3.6.8 Controlled Access to Monitoring Configuration Information

The user needs the TFCS to have a means to control access to the monitoring configuration information. The TFCS has needs relating to a monitoring capability. Creating this capability will mean that a set of monitoring configuration parameters must be defined. These parameters must identify what constitutes a malfunction or anomaly and define what response or action will be taken. It is important that there be controlled access to this monitoring configuration information to maintain proper monitoring functions.either remotely or locally. [User need is not clear on why.] [RALPH]

4.3.7 Power Filtering and Distribution

This section identifies the user needs of the TFCS related to the Power Filtering and Distribution functional element.

4.3.7.1 Clean Power Distributed

The user needs the TFCS to distribute clean power within the cabinet, i.e. power that is protected against surges and spikes and is filtered to regulate electrical noise. The sensitive electronic equipment within the cabinet requires clean power (that is isolated from the output power used for external devices) so that the equipment is not damaged.

4.3.7.2 Output Power Distributed

The user needs the TFCS to distribute output power externally to field displays. Output power must be protected against surges and spikes but it is not necessary to regulate for electrical noise. The TFCS provides power to external field displays and output power is used for this. The output power is also used to power some of internal equipment such as fans, lights, and service outlet.

4.3.7.3 Power Conversion

The user needs the TFCS to convert power for use by internal devices. The assemblies internal to the TFCS require either AC or DC power to operate. The cabinet must provide power to these assemblies, which include traffic control devices, routers, switches, and modems.

4.3.7.4 Backup Power Provisions

The user needs the TFCS to provide a method for continued operations when there are service power interruptions. There are various backup power methods available. This is not intended to select a method but provide an electrical interface or interfaces specifically for this purpose. The need for continuous operations coupled with the real possibility of service power interruptions provides the reason for this need.

4.3.8 System Reporting

This section identifies the user needs of the TFCS related to the System Reporting functional element.

4.3.8.1 System Reports

The user needs the TFCS to provide system reports and logs that include the output of system monitoring. System reports include diagnostic reports on malfunctions and anomalies for the field inputs, the field outputs, cabinet monitoring, application computer, and internal TFCS communications. This reporting is key not only to real time diagnostics, but to historical analysis of data.



4.3.8.2 System Reporting Distribution

The user needs the TFCS to be capable of providing system reports locally or to a remote system using a standardized interface and protocol. Currently, most system reporting is achieved by direct proprietary connection to the TFCS via a laptop computer. This need is for reporting through both a local and external interface.

4.3.8.3 Non-Volatile Information

The user needs the TFCS to have a non-volatile method of maintaining the system reports and logs. This capability is needed so that a TFCS can quickly be restored to operational conditions when a replacement system is required.

4.3.9 External Communications

This section identifies the user needs of the TFCS related to the External Communications functional element.

4.3.9.1 External Communications Capability

The user needs the TFCS to accommodate a variety of communications equipment and media for communications external to the system. External communications relates to communications with field devices as well as communications with other TFCS, or with remote centers. Some of the types of communications that must be supported are serial communications, telephone-based communications, networked communications, and wireless communications. The capability to provide wireless communications also includes the mounting of the wireless antenna to the cabinet.

4.3.9.2 Standardize External Interfaces

The user needs the TFCS to provide standardized external interfaces and protocols. This includes mountings and connectors so that limited customization or modification of the cabinet is required.

4.3.10Housing

This section identifies the user needs of the TFCS related to the Housing functional element.

4.3.10.1 External Mounting

The user needs the TFCS housing to have mounting capabilities which accommodate existing transportation industry base, pedestal, and pole mountings. This will allow installation of a new cabinet or replacing a cabinet at locations with existing mounts.

4.3.10.2 Corrosion Resistant Material

The user needs the TFCS housing to be made of materials that are resistant to rust and corrosion. The cabinet is in harsh weather conditions subject to corrosion.

4.3.10.3 Cabinet Access

The user needs the TFCS housing to include one or more doors to support easy user access to subsystems and assemblies. This includes the associated door latches, hinges and door catches. Note that this may include front doors, rear doors, side doors, and special compartment doors depending on



the final design and equipment located within the cabinet. The doors are needed so that maintenance personnel can access assemblies inside the cabinet.

4.3.10.4 Physical Environment

The user needs the TFCS housing to protect its subsystems and assemblies from heat, wind, snow, dust and rain. This includes adequate ventilation, water drainage away from the cabinet structure, and structural strength to withstand severe weather conditions.

4.3.10.5 Animal and Insect Resistant

The user needs the TFCS to protect its subsystems and assemblies from small animals and insects. Rodents are known to seek shelter in field cabinet systems and can damage electrical elements and wiring.

4.3.10.6 Vandalism and Theft Resistant

The user needs the TFCS housing to be resistant to vandalism or theft. Much of the TFCS is recyclable and can be a target for thieves or those who simply wish to damage public property. Some of the equipment might be taken for use in another system.

4.3.10.7 Graffiti Resistant

The user needs the TFCS housing to have an external finish that is resistant to graffiti and bill posting. Field cabinets are often a target for those wishing to make public statements and those who simply wish to deface public property.

4.3.10.8 Video Monitor Provision

The user needs the TFCS housing to provide space and electrical connections for a small video monitor. Monitors are commonly used for maintenance with TFCS deployments that use video detection field inputs.

4.3.10.9 Battery Housing Provision

The user needs the TFCS to provide internal space for housing batteries commonly used to provide backup power. Due to lack of room within the cabinet, deployers that use backup batteries typically attach battery housings to the external housing of the cabinet in a variety of manners.

4.3.10.10Law Enforcement Personnel Access

The user needs the TFCS to provide law enforcement personnel limited access to the TFCS to the extent necessary for direct control of the field location while restricting access to the remainder of the cabinet. This is to allow law enforcement personnel control of the field location for emergencies and special events.

4.3.11Internal Communications

This section identifies the user needs of the TFCS related to the Internal Communications functional element.



4.3.11.1 Internal Communications Capability

The user needs the TFCS to have an internal communications capability that can be used to communicate between its subsystems and assemblies. The communications are used operationally and for monitoring and reporting purposes.

4.3.11.2 Uniform Interfaces

The user needs the TFCS to provide uniform internal interfaces and protocols. Uniform internal interfaces increase configuration flexibility and facilitate maintenance.

4.4 Operational Environment

The specific operational environment will vary from agency to agency. The general operational personnel are described in Section 5. The physical environment for a TFCS includes that of any area in North America. This means there are radical differences in weather conditions, existing transportation infrastructures, types and quality of external communications, and quality of power.

4.5 Support Environment

The support personnel are some the users of the system and are already been listed in Section 5. In addition to those listed there are installers. These are typically contractors who perform electrical wiring of the field location according to plans. They are used during initial TFCS installations or upgrades to the field location’s electrical systems. They understand the electrical code and safe practices for high voltage systems.

4.6 Operational Scenarios

There are no special operational scenarios for this StdRS.



5 SYSTEM REQUIREMENTS

This section establishes the requirements for the TFCS based on the user needs identified in Section 4. To provide an organization to the requirements and facilitate understanding, Figure 5 shows the physical architecture of the TFCS as a collection of assemblies and subsystems. Figure 6 shows the architecture using an optional assembly to reduce the system size. The colors identify the logical-physical relationship between the functional elements of Figure 4 and the physical elements of Figures 5 and 6. Further details of the TFCS architecture are not necessary for establishing requirements.

Guidance: [TR55]

Housing InputAssembly

OutputAssembly

ControllerSubsystem

Field TerminationAssembly

MonitorAssembly

Clean Pwr Bus Assy

Serial Bus Assy

Service Assembly

Cabinet Pwr Supply

Figure 5. The TFCS physical architecture.



Housing

ControllerSubsystem

Field TerminationAssembly

MonitorAssembly

Clean Pwr Bus Assy

Serial Bus Assy

Service Assembly

Cabinet Pwr Supply

Input / OutputAssembly

Figure 6. The TFCS physical architecture with optional Input/Output Assembly.

The requirements for the TFCS in the following subsections are arranged according to the functional elements in Section 4. They are derived from the user needs identified in Section 4. The requirements are “well-formed” and generally take the form: [Actor] [Action] [Target] [Constraint] [Localization]. The constraint identifies how success or failure of the requirement is measured. The localization identifies the circumstances under which the requirement applies. Not all requirements will have both a localization and a constraint. An example requirement is as follows: The TFCS [Actor] shall generate [Action] event reports [Target] containing the following information [Constraint] on a scheduled interval [localization]. Requirements will use section numbers for identification. Sections may contain multiple requirements for convenience when all of the requirements in the section are required to describe a feature.

In definining requirements the following terms will be used:

“part” An element not normally useful by itself and not readily capable of further disassembly for maintenance purposes (e.g., bolt, nut, bracket, semiconductor, printed circuit board),

“module” The smallest element of physical management described in these requirements (i.e., a replaceable device). Typically a module is a functional device that plugs into an assembly.

“assembly” A physical entity within the system made up of two or more modules.



“subsystem” A portion of a system containing two or more integrated elements which, while not completely performing the specific function of a system, may be isolated for purpose, design, test, or maintenance.

“element” A general term used for a part, assembly or subsystem that is viewed as an entity for purposes of design, operation, or reporting. An element may refer to various levels of detail such as the elements of the TFCS or components on a PCB.

For the sake of clairity, a requirement may be followed by statements in italic font type and preceded by the word “Guidance.” These statements are used to express to the reader how the requirement may be fulfilled. The statements themselves are not considered a part of the requirement.

The requirements for the TFCS in the following subsections are organized according to the most applicable assembly or subsystem. These sections are preceded by a section entitled “General Characteristics” that contain requirements that apply generally to the TFCS or that pertain to an item that is inappropriate to assign to one of the other sections.

5.1 General Characteristics

The following subsections establish requirements for the general characteristics of the TFCS. The TFCS consists of well-defined subsystems and modules connected via well-defined open interfaces as described below

Guidance: Use the ITS Cabinet V1 Standard environmental requirements [TR41]

Guidance: The design should go forward with the best design proposals based on the user needs and requirements from WG discussions (at the meeting implied). Backward compatibility to the ITS Cabinet V1 Standard (RD[4]) cabinet systems is secondary [TR42] [TR113]

5.1.1 Open Interfaces

5.1.1.1 Patents and Copyrights

Interfaces that are patented or copyrighted shall not be included as part of the TFCS [TR57]

5.1.1.2 Commonly Available Components

Components that make up the TFCS shall be available for purchase from distribution or shall be able to be fabricated from commonly available materials. [TR58]

5.1.1.3 Open Standards

The TFCS’s physical, electrical and communication interfaces shall be based on existing open standards or defined herin. [TR161]Guidance: The open standards development process provides a roadmap for future subsystems [TR63] [TR72]

5.1.2 Rack Mountable

The TFCS subsystems and assemblies shall be suitable for mounting in a 19 inch rack [TR59]. [



Guidance: It is the intent of the design team, to focus on the two door cabinet design but the solution should not preclude the use of a single door cabinet with a removable rack [TR45]

5.1.3 Serial Bus Communications Architecture

5.1.3.1 Connectivity

The TFCS shall utilize a Serial Bus (SB) communications architecture for communication between the elements of the TFCS. [TR131] [TR181] [TR182]

Guidance: It was the consensus of the group to keep the existing serial architecture [TR48] which includes internal communications monitoring of SB1 and SB2

5.1.3.2 Allows Proprietary Data Messages

TFCS shall have an internal communications infrastructure that allows the use of proprietary data messages within the standardized protocol. [TR13]

5.1.4 Monitor Bus Architecture

The TFCS shall utilize a Monitor Bus (MB) for communication of electrical levels of the field outputs to the monitor unit.

5.1.5 Utilizes a Controller Subsystem

The TFCS shall utilize a Controller Subsystem (CS) to perform the functions of an application computer and provide external communication interfaces for the TFCS. [TR109] [TR183] [TR87] [TR60] [TR66] [TR69]

5.1.6 Utilizes an Input Assembly

The TFCS shall utilize an input assembly (IA) accept devices used for field inputs. [TR60] [TR66] [TR69]

5.1.7 Utilizes an Output Assembly

The TFCS shall utilize an ouput assembly (OA) to accept devices used for field outputs. [TR60] [TR66] [TR69]

Guidance: WG voted In favor of using the proposed output assembly and field termination, Refer to posted Considered Concept [TR46]

5.1.8 Utilizes an Input/Output Assembly

The TFCS shall utilize an input/ouput assembly (IOA) to accept devices used for both field inputs and field outputs. [TR60] [TR66] [TR69]

5.1.9 Utilizes a Field Termination Assembly

The TFCS shall utilize a field termination assembly (FTA) to secure field wiring within the cabinet. [TR60] [TR69]



5.1.10Utilizes a Monitor Assembly

The TFCS shall utilize a monitor assembly (MA) to monitor the operation of the TFCS and provide diagnostic information. [TR99] [TR60] [TR66] [TR69]

5.1.11Utilizes a Service Assembly

The TFCS shall utilize a service assembly (SA) to provide raw power (i.e. power that is protected against surges and spikes) and clean power (i.e. power that is protected against surges and spikes and filtered to regulate electrical noise). [TR60] [TR66] [TR69]

5.1.12Utilizes a Serial Bus Assembly

The TFCS shall utilize a serial bus assembly (SBA) to facilitate access to the serial bus by the elements of the TFCS. [TR60] [TR66] [TR69]

5.1.13Utilizes a Clean Power Bus Assembly

The TFCS shall utilize a power assembly (CPBA) to distribute clean power for the elements of the TFCS. [TR151] [TR60] [TR66] [TR69]

5.1.14Utilizes a Cabinet Power Supply

The TFCS shall utilize a cabinet power supply to provide DC power to the elements of the TFCS. [TR153] [TR60] [TR66] [TR69]

5.1.15Relocatable Elements

The TFCS’ CS, IA, OA, IOA, FTA, SBA, MA, CPBA and SA shall be able to be located in various positions within the TFCS. [TR73]

5.1.16No Dark Condition

The TFCS’ CS, IA, OA, IOA, and SBA shall be able to be removed without causing a dark condition in the intersection. [TR7] [TR33]

5.1.17Legacy Housings

The TFCS shall have overall sizes compatible with legacy cabinet models 342, 346, and 340 from the ITS Cabinet V1 Standard. [TR162]

5.1.18Small-Sized Cabinet

The TFCS shall be available in a single door model 306 small-sized cabinet (SSC). [TR163]

5.1.19Non-Standard Housing Sizes

The TFCS shall support non-standard housing sizes that comform to the standard.



5.1.2024/7 Operation

The TFCS shall operate 24 hours a day and seven days a week without user intervention. [TR74]

5.1.21Welding Standards

The TFCS shall be constructed in compliance to Standard B2.1-22-015:2011 of the American Welding society for any welds necessary in the TFCS.

5.1.22Electronics Standards

The TFCS’ electronic elements shall be built in conformance to IPC J-STD-001E “Requirements for Soldered Electrical and Electronic Assemblies” for Class 2.

5.1.23Cable and Wire Harness Standards

The TFCS’ cable and wire harnesses shall be built in conformance to the WHMA A-620 standards.

5.1.24Derating

The parts used to create the elements of the TFCS shall not be operated at greater than 80 percent of their rated values unless otherwise indicated within this standard. [TR77]

5.1.25Storage Ambient Temperature

The TFCS shall be capable of withstanding an ambient storage temperature range of -45 degrees Celsius to +85 degrees Celsius. [TR80]

5.1.26Operating Ambient Temperature

The TFCS’s shall have an operating ambient temperature range from -37 degrees Celsius to +74 degrees Celsius. [TR79]

5.1.27Operational Relative Humidity

The TFCS operating shall be capable of operation with a relative humidity shall not exceeding 95 percent non-condensing over the temperature range of -37 degrees Celsius to +74 degrees Celsius. [TR81]

5.1.28Nominal AC Input Power

The TFCS shall be capable of operating from a nominal voltage of 120 VAC, 60 Hz, (+/- 3.0 Hz). [TR148]

5.1.29Power Factor

The TFCS shall maintain an overall power factor (PF) of 0.8 or greater, as measured at the service entry, when operating from AC power and isolated from the Application Computer for any such measurement. [TR91]

5.1.30Power Supply Efficiency

The TFCS’s power supplies shall be designed to operate with an average efficiency of 80% or greater at load [TR12] under expected loading not including the the load of the Application Computer. [TR92]



5.1.31Audible Noise Level

The TFCS shall have no element that emits an audible noise level exceeding a peak level of 55 dBA when measured with all doors open at a distance of one meter away from the TFCS. [TR84]

5.1.32Shock

The elements TFCS shall suffer neither permanent mechanical deformation nor any damage that renders the unit inoperable, when subjected to a shock of 10 g applied in each of three mutually perpendicular planes. [TR85]

[Excerpted from NEMA TS 2-2003, Section 2.1.9, with revisions for clarification in this context.]

5.1.33Vibration

The elements of the TFCS shall continue their defined functions and maintain physical integrity when subjected to a vibration of 5 to 30 Hz up to 0.5 g applied in each of three mutually perpendicular planes. [TR86]

[Excerpted from NEMA TS 2-2003, Section 2.1.10, with revisions for clarification in this context.]

5.1.34Electrostatic Discharge (ESD) Resistant

The TFCS shall adhere to applicable sections of International Electrotechnical Commission (IEC) Standard 61000-4-2:2008 “Electromagnetic compatibility (EMC) – Part 4-2: Testing and Measurement Techniques – Electrostatic Discharge Immunity Test.” [TR83] [TR98]

5.1.35Electronic Emissions

The TFCS shall adhere the Code of Federal Regulations, Title 47 – Telecommunication, Chapter 1 – Federal Communications Commission, Part 15. [TR82]

5.1.36Environmental Testing

All major units of the TFCS shall be designed to operate properly when subjected to the test procedures defined in ITS Cabinet v01.02.17 – Section 7,. Tests shall include the following:

AC line limits AC frequency limits AC power interruption AC high-repetition noise transients AC low-repetition, high energy transients AC nondestructive transient immunity Input-Output terminal transient immunity Ambient temperature limits Humidity Shock Vibration

Tests not defined by TS 2 (or ITS V1) but required by the TFCS unit test shall include: Audible noise level ESD



Power factor Power supply efficiency FCC Part 15 [TR16]

5.1.37Packaging

The TFCS shall be shipped in container and packaging materials that protect the TFCS from incidental shipping damage.

5.1.38No Sharp Edges

The TFCS shall have all sharp edges and corners rounded and free of burrs. [TR88]

5.1.39NEC Best Practices

The TFCS shall adhere to the best practices of the National Electrical Code (NEC) for wire sizing, ampacity and user safety. [TR89] [TR90]Guidance: Current language that references only the NEC is sufficient [TR43]

Guidance: ITS CAB WG UNANIMOUSLY WG AGREED that the wiring and breakers should follow the ampacity of the NEC. [TR54]

Need for UL approval deleted by 9-13-2010 WG vote 11-0-1 [TR36]

5.1.40No Liquid Mercury

The TFCS shall contain no elements that use liquid mercury. [TR93]

Guidance: Design is not dictated as solid state contactor. [TR94]

5.1.41Documentation

The TFCS shall have wiring diagrams and a user’s manual.

5.1.42Subsystems not Interdependent

Replacement of any individual TFCS subsystems in any combination shall not affect the operation of other TFCS subsystems. [TR65]

5.1.43Subsystem Quantities

The Subsystem quanties shall match those addresses assigned in Section 4.7.14.7.1of the cabinet V1 standard [TR67] [TR70]

5.1.44Future Subsystems

The TFCS shall reserve the Subsystem module addresses for future use shown in Section 4.7.14.7.1 of the cabinet V1 standard [TR62] [TR71]



5.1.45MTBF

If published, MTBF shall be calculated using the latest revision of MIL standard 217 and published with the calculation criteria. [TR75]

Guidance: MTBF is not required, but if published must be calculated per MIL 217 including the criteria such as temperature, loading, etc, so that independent evaluators can recreate the calculation with the same results. MTBF can then be used as a fair comparison can be drawn among equipment.

5.1.46Design Life

Design Life shall be stated in terms of MTBF. [TR76]

Guidance: Measurement is not practical

5.1.47Output Power Distribution

The TFCS shall distribute 12 VDC and 24 VDC output power to subassemblies [TR152]

5.1.48Externally Accessible SB3 Bus

The TFCS shall have an externally accessible SB3 bus using the standardized SB3 connector [TR14]

1.1.1 Insulating DevicesThe TFCS shall contain insulating devices which protect technicians from accidentially coming into contact with hazardous voltages within the cabinet.

5.2 Controller Subsystem

The following subsections establish the requirements for the Controller Subsystem of the TFCS.

5.2.1 Controller Subsystem Communication Interfaces

The following subsections establish the requirements for the Controller Subsystem’s communication interfaces within the TFCS. [TR108] [TR184]

5.2.1.1 Receives Field Input Data

The TFCS’s Controller Subsystem shall receive field input data from the Input Assembly or Input/Output Assembly via the serial bus.

5.2.1.2 Receives Detector Status Information

The TFCS’s Controller Subsystem shall receive detector status information from the input assembly or Input/Output Assembly via the serial bus. Supported messages shall include open, shorted and changes in inductance by more than 25%. [TR3], [TR15]



5.2.1.3 Sends Field Output Commands

The TFCS’s Controller Susbsystem shall send field output commands to the output assembly or Input/Output Assembly.

5.2.1.4 Sends Switch Pack Driver Information to the Monitor Assembly

The TFCS’s Controller Susbsystem shall send the switch pack driver information (the state of the switch packs commanded by the Controller Subsystem) to the Monitor Assembly.

5.2.1.5 Sends Flash Command to the Monitor Assembly

The TFCS’s Controller Susbsystem shall send a flash command to the Monitor Assembly.

5.2.1.6 Receives CMU Programming Information from the Monitor Assembly

The TFCS’s Controller Susbsystem Monitor Subsystem shall receive CMU programming information from the Monitor Assembly.

5.2.1.7 Signal Control Priority

The TFCS shall provide an interface for signal control priority [TR17]

5.2.2 External Communications

The TFCS’ Controller Subsystem shall provide for communications external to the TFCS. [TR160] [TR161]

5.2.3 Intersection Control Applications

The TFCS Controller Subsystem shall support Intersection Control Applications developed for the ITS Cabinet V1 without modifications[TR110]

5.2.4 Ramp Meter Control Applications

The TFCS Controller Subsystem shall support Ramp Meter Applications developed for the ITS Cabinet V1 without modifications [TR111]

5.2.5 Data Collection Applications

5.3 The TFCS Controller Subsystem shall support Data Collection Applications developed for the ITS Cabinet V1 without modifications [TR112]Input Assembly

The following subsections establish the requirements for the Input Assembly of the TFCS.

5.3.1 Input Assembly Communication Interfaces

The following subsections establish the requirements for the Input Assembly communication interfaces within the TFCS.



5.3.1.1 Sends Field Input Data

The TFCS’s Input Assembly shall send field input data to the Controller Subsystem via the Serial Bus, [TR184]

5.3.1.2 Sends Detector Status Information

The TFCS’s Input Assembly shall send detector status information to the Controller Subsystem via the Serial Bus,

5.3.2 Commonly-Deployed Field Input Devices

The TFCS’s Inpuot Asssembly shall be compatible with field input devices that are commonly deployed such as inductive loops, pedestrian detectors, vehicle preemption devices, and transit signal priority devices that utilize a “contact closure” type of interface. [TR100]

5.3.3 NEMA TS 2 Four-Channel Detector Modules

The TFCS’s Input Assembly shall be able to utilize current-technology four-channel NEMA TS 2 detector modules with half-width front panels in each single-width slot (See NEMA TS 2-2003, [TR101] [TR104]

5.3.4 Four-Channel Isolator Modules

The TFCS input assembly shall provide an option for the use of four-channel isolator modules. [TR103] [TR5]

5.3.5 48 Input Channels

The TFCS shall provide an input assembly that provides for up to 48 input channels. [TR64] [TR68] [TR102] [TR106]

5.3.6 Plug-In Input Devices

The TFCS input modules shall be plug-in modules within the Input Assembly without the use of tools.

5.3.7 Hot-Swappable Input Devices

The TFCS input modules shall be hot-swappable within the input assembly. [TR61]

5.3.8 Multiple Input Assemblies

The TFCS shall support the use of multiple Input Assemblies in a single TFCS. [TR62] [TR64] [TR68] [TR71] [TR107]

1.1.1 Specialty Detection DevicesThe TFCS design shall include support for connection of specialty detection devices, such as video detection units, directly into the internal cabinet bus architecture without requiring the use of input file interface modules.

5.2.6 Input Assembly without Detector Status Message



The TFCS shall provide an input assembly that can utilize up to twelve 4-Channel Detectors/Isolators and does not utilize the NEMA TS 2 detector status message.

5.4 Output Assembly

The following subsections establish the requirements for the Output Assembly of the TFCS.

5.4.1 Output Assembly Communication Interfaces

The following subsections establish the interface requirements for the Output Assembly’s communication interfaces within the TFCS. [TR185]

5.4.1.1 Receives Field Output Commands

The TFCS’s Output Assembly shall send field output commands from the Controller Subsystem via the Serial Bus.

5.4.1.2 Send Current Levels to the Monitor Assembly

The TFCS’s Output Assembly shall send the the level of electrical current per output channel to the Monitor Assembly via the Monitor Bus. [TR8] [TR24] [TR26]

Guidance: Permissible to perform the functionality of the AMU within the Loadswtich [TR38]

Guidance: May add new devices if additional diagonsics are necessary [TR39]

5.4.1.3 Send Voltage Levels to the Monitor Assembly

The TFCS’s Output Assembly shall send the voltage level per output channel to the Monitor Assembly via the Monitor Bus. [TR24] [TR25] [TR125] [TR126]

Guidance: Permissible to perform the functionality of the AMU within the Loadswtich [TR38]

Guidance: May add new devices if additional diagonsics are necessary [TR39]

5.4.2 Up to Seven High Density Switch Pack Modules

The TFCS’ output assembly shall accept up to 7 high density switch pack (HDSP) modules. [TR29] [TR64] [TR68] [TR96] [TR115] [TR105]

5.4.3 120 VAC Switch Pack Modules

The TFCS’ output assembly shall accept switch pack modules (HDSP120) suitable for controlling field displays that operate at nominal 120 VAC 60Hz. [TR23] [TR9]

5.4.3.1 Two Ouput Channels per HDSP120

The HDSP120 shall have two output channels. [TR20] [TR114]



5.4.3.2 Three Signal Indications per HDSP120 Channel

The HDSP120 shall be able to control three signal indications per channel. [TR21]

Guidance: WG discussed the use of four output load switches but decided that six outputs were best [TR40]

5.4.3.3 Ampres per HDSP120 Channel

The SP120 shall be able to support output devices up to 2 Amps per channel. [TR19] [TR117]

Guidance: 5.4.4 Supported Field Display Devices was struck in favor of amperage selection

5.4.3.4 HDSP120 Indicators

The HDSP120 shall have 7 visible indicators on the device: 1 indicator for power to the HDSP120 and 3 indicators for each output channel. [TR22] [TR28]

5.4.4 Low Voltage Switch Pack Modules

The following power limitations shall apply to the Low Power / Low Voltage cabinet option [TR53] [TR9] [TR30] [TR31] [TR118] [TR119]:

- Less than 30 Volts RMS- Less than 42 Volts Peak- Less than 60 Volts DC

Guidance: WG confirmed that for the low-voltage option 48 Volts DC +/-2 unless our process proves otherwise. [TR56]

5.4.4 Supported Field Display Devices

The TFCS shall support an output subsystem capable of driving the following field display devices: low-power AC, LED signals (< 20W) low-power DC, LED signals (< 10W)

5.4.5 Plug-In Switch Pack Modules

The TFCS’ HDSP modules shall be able to be plugged into theOutput Assembly without the use of tools.

5.4.6 Output Circuit Breakers

The TFCS’ output assembly shall include circuit breakers or other similar protection devices for all field output circuits.

Guidance: It was the consensus of the WG to have four circuit breakers per output assembly [TR51]

5.4.7 Electrically Paired with a Field Termination Assembly

The TFCS’ Output Assembly shall be electrically paired with a Field Termination Assembly to carry electrical current from the HDSP modules to the field displays.



5.4.8 Multiple Output Assemblies

The TFCS shall support the use of multiple Output Assemblies in a single TFCS. [TR62] [TR71] [TR116]

5.4.9 Pluggable from the Front

All output assembly modules shall be pluggable from the front [TR18]

5.4.10Regular Density Output Files

TFCS shall support the Six Pack and Twelve Pack regular density output files of the ITS Cabinet V1 [TR114]

5.5 Input/Output Assembly

The following subsections establish the requirements for the Input/Output Assembly of the TFCS.

5.5.1 Up to 16 Input Channels

The TFCS’ Input/Output assembly shall support up to 16 input channels.

5.5.2 Up to Three Switch Pack Modules

The TFCS’ Input/Output assembly shall accept up to 3 HDSP modules.

5.5.3 Adheres to Input Assembly Requirements

The TFCS’ Input/Output assembly shall adhere to the requirements of the Input Assembly excluding the number of input channels

5.5.4 Adheres to Output Assembly Requirements

The TFCS’ Input/Output assembly shall adhere to the requirements of the Output Assembly excluding the number of HDSP modules.

5.5.5 High Density Inputs

5.6 The TFCS shall provide a high-density input assembly capable of directly supporting 12 current-technology four-channel NEMA TS-2 detector modules using half-width front panels in each single-width slot. [TR4] [TR34] [TR95]Field Termination Assembly

The following subsections establish the requirements for the Field Termination Assembly of the TFCS. [TR35]

5.6.1 Field Wire Termination

The TFCS’s Field Termination Assembly shall provide six-position sockets and plugs for the termination of field output wires.



5.6.2 Relay

The TFCS’s Field Termination Assembly shall provide a relay for use in flashing signal indications.

5.6.3 Channel-Programmable Flasher Outputs

The TFCS’ Field Termination Assembly shall provide the means for selecting the specific flasher output (red, yellow, or no indication) used for each channel’s display when in flashing operation. [TR120]

5.6.4 Transient Suppression

The TFCS’ Field Termination Assembly shall provide transient suppression for the protection of the switch packs.

5.6.5 Electrically Paired with an Output Assembly

The TFCS’ Field Termination Assembly shall be electrically paired with an Output Assembly to receive electrical current from the switch pack modules to be applied to the field displays.

5.6.6 Multiple Field Termination Assemblies

The TFCS shall support the use of multiple Field Termination Assemblies in a single TFCS.

5.7 Monitor Assembly

The following subsections establish the requirements for the Monitor Assembly of the TFCS

Guidance: As a design goal, it is allowable to eliminate the need for the PDA [TR44]

Guidance: In favor of using the AMU2 concept? Concept rejected by a vote of 0-5-2 [TR47]

Guidance: ITS cabinet V2 should include an AMU2 device? Rejected by vote of 4-8-2 [TR49]

5.7.1 Monitor Assembly Communication Interfaces

The following subsections establish the interface requirements for the Output Assembly’s communication interfaces within the TFCS.

5.7.1.1 Receives Switch Pack Driver Information from the Controller Subsystem

The TFCS’s Monitor Assembly shall receive switch pack driver information (the state of the switch packs commanded by the controller subsystem) from the Controller Subsystem. [TR136]

5.7.1.2 Receives Flash Command from the Controller Subsystem

The TFCS’s Monitor Assembly shall receive a flash command from the Controller Susbsystem.



5.7.1.3 Sends CMU Programming Information to the Controller Subsystem

The TFCS’s Monitor Assembly shall send CMU programming information to the Controller Susbsystem. [TR157]

5.7.1.4 Receives Current Levels from the Output Assembly

The TFCS’s Monitor Assembly shall receive the the level of electrical current per output channel from the Output Assembly via the Monitor Bus.

Guidance: Not required to be compatible with ITS Cabinet V1 SB3 protocol. [TR37]

5.7.1.5 Receives Voltage Levels from the Output Assembly

The TFCS’s Monitor Subsystem shall receive voltages levels from the output the Output Assembly via the Monitor Bus.

Guidance: Not required to be compatible with ITS Cabinet V1 SB3 protocol. [TR37]

]

5.7.1.6 Ethernet Communications

CMU shall have an Ethernet interface [TR11] [TR133] [TR134] [TR158]

5.7.1.7 Externally Accessible Voltage and Current

Load Switch voltage and current values shall be externally accessible [TR27] [TR97]

5.7.2 Cabinet Monitor Unit

The TFCS’ Monitor Assembly shall provide for a Cabinet Monitor Unit (CMU) with mimum functionality of ITS Cabinet V1 CMU [TR122] [TR123] [TR124] [TR127] [TR128] [TR129] .[TR135] [TR137] [TR138] [TR139] [TR140] [TR141] [TR142] [TR143] [TR144] [TR145] [TR146] [TR147] [TR159]

5.7.3 CMU Display Unit

The TFCS’ monitor assembly shall contain a CMU Display Unit (CDU) which provides a user display for the CMU. [TR132] [TR117] [TR130] [TR32 ][TR157] [TR32]

5.7.4 Flasher Unit

5.7.4.1 Four Fused Output Channels

The TFCS’s monitor assembly shall provide for a flasher unit with four fused output channels. [TR121]

Guidance: It was the consensus of the WG to have one flasher, one breaker, and four protected outputs [TR50]



5.7.4.2 Sychronized Flashers

Flashers shall be synchronized [TR10]

5.8 Clean Power Bus Assembly

The following subsections establish the requirements for the Clean Power Bus Assembly of the TFCS. [TR151]

5.8.1 Clean Power Distribution

The TFCS’ Clean Power Bus Assembly shall provide for the distribution of clean power (output power with additional filtering to reduce electrical noise) to the elements of the TFCS. [TR151]

5.8.2 Clean Power Receptacles

The TFCS’ Clean Power Bus Assembly shall have 8 NEMA 5-15R receptacles (non-GFI) suitable for use by the elements of the TFCS. [TR151]

5.9 Service Assembly

The following subsections establish the requirements for the Service Assembly of the TFCS.

5.9.1 Output Power

The TFCS’ Service Assembly shall provide output power which is service power with devices to protect against power surges and spikes. [TR152]

5.9.2 Clean Power

The TFCS’ Service Assembly shall provide clean power which is service power with devices to protect agains power surges and spikes and filtering to reduce electrical noise. [TR151]

5.9.3 Convenience Receptacle

The High Voltage TFCS’ Service Assembly shall have a single NEMA Type 5-15R grounding type receptacle with GFI.

5.9.4 Main Power Breaker Switch

The TFCS’ Service Assembly shall provide main power breaker switch which can be used to stop all electrical power from entering the rest of the TFCS elements.

5.9.5 Facilities Breaker Switch

The TFCS’ Service Assembly shall provide a facilities power breaker switch which can be used to stop clean power from entering the rest of the TFCS elements.

Guidance: It was discussed that a breaker will be added in the service assembly for fan, light, and GFI. Call it a "facilities" breaker [TR52]



5.9.6 Backup Power Subsystem

The TFCS shall be compatible with a backup power subsystem. As a minimum, this shall include standardized connectorization from the standby source to the TFCS DC power source as well as procedures for switching to and from standby power in the event of a main power failure. [TR155] [TR156]

5.9.7 Service Power Input Options

The TFCS shall provide manufacturing options to operate on different nominal service power sources [TR148]

5.9.7.1 High Voltage Service Assembly

5.9.7.2 The TFCS shall include a Service Assembly option for 120 VAC, 60 Hz nominal service power input. [TR150]Low Voltage Service Assembly

The TFCS shall include a Service Assembly option for 48 VDC nominal service power input [TR149]

1.1.1 Nominal DC Input Voltage 1The TFCS shall support a configuration which operates from DC service power at 48VDC.

1.1.2 Nominal DC Input Voltage 2The TFCS shall support a configuration which operates from DC service power at 12-24VDC, as might be provided by one or more solar panels.

[EDITOR – Consider 28VDC and 48VAC.]

1.1.3 Internal AC Inverter [TR154]Should the TFCS be operating from DC power only, an AC inverter shall be provided for those components which require AC power.

1.1.4 Standby PowerThe 120VAC-to-24VDC power supply shall include support for an external 48VDC standby power source.

5.10 Cabinet Power Supply

The following subsections establish the requirements for the Cabinet Power Supply.

5.10.1Clean Power Input

The TFCS’ Cabinet Power Supply shall accept clean power from clean power bus assembly. [TR151]

5.10.2Input Power Indicator

The TFCS’ Cabinet Power Supply shall have an indicator which identifies when there is clean power coming into the unit.

5.10.3Fused Input Power

The TFCS’ Cabinet Power Supply input power line shall be fused.



5.10.424 VDC Power Output

The TFCS’ Cabinet Power Supply shall provide 24 VDC for the elements of the TFCS. [TR6] [TR153]

5.10.512 VDC Power Output

The TFCS’ Cabinet Power Supply shall provide 12 VDC for the elements of the TFCS. [TR6] [TR153]

5.10.6Output Power Indicators

The TFCS’ Cabinet Power Supply shall have indicators for each DC power output line which identifies when there is DC power coming out of the unit.

5.10.7Fused Output Power

The TFCS’ Cabinet Power Supply output power lines shall be fused to protect TFCS elements from electrical surges and spikes.

5.10.8 12 VAC Output Power

The TFCS’ Cabinet Power Supply shall provide 12 VAC for the elements of the TFCS. [TR6]

5.11 Serial Bus Assembly

The following subsections establish the requirements for the Serial Bus Assembly of the TFCS.

5.11.1Serial Bus Ports

The TFCS’s Serial Bus Assembly shall provide 8 serial bus ports using DB-25S connectors to facilitate access to the bus by elements of the TFCS.

5.12 Housing

5.12.1Corrosion Resistant

The TFCS shall be constructed of materials that are inherently corrosion resistant or have been treated so as to be corrosion resistant. [TR164]

5.12.2Aluminum Sheet

Aluminum sheets used in the construction of the TFCS shall be Type 3003-H14 or Type 5052-H32 ASTM Designation B209 alluminum alloy. [TR78] [TR165]

5.12.3Aluminum Sheet Plating

Aluminum sheeting used in the construction of the TFCS internal subassemblies shall treated using clear chromate conversion per MIL-C-5541, Class 3. [TR78] [TR166]



5.12.4Stainless Steel Sheet

Stainless steel sheets used in the construction of the TFCS shall be annealed or one-quarter-hard complying with ASTM Designation A666 for Type 304, Grades A or B, stainless steel sheet. [TR78] [TR167]

5.12.5Cold Rolled Steel

Cold rolled steel sheet, rod, bar and extruded used in the construction of the TFCS shall be Type 1018/1020. [TR78] [TR168]

5.12.6Cold Rolled Steel Plating

Cold rolled steel used in the construction of the TFCS shall be plated using either cadmium plating meeting the requirements of Federal Specification QQ-P-416C, Type 2 Class l or zinc plating meeting the requirements of ASTM B633-85 Type II SC4. [TR78] [TR169]

[More specification to be added.] [KINNARD]

5.12.7Stainless Steel Hardware

All bolts, nuts, washers, screws, hinges and hinge pins used in the construction of the TFCS shall be stainless steel unless otherwise specified. [TR78] [TR170]

5.12.8Doors

The TFCS cabinet designs shall include door(s) with appropriate door frames, seals, gaskets, strikers, stops and three-point locking mechanisms. [TR78] [TR171]

5.12.9Ventilation

The TFCS cabinet housings shall be designed with thermostatic ventiliation in the event that the internal cabinet temperature exceeds the pre-programmed temperature. Incoming air shall be filtered..”] [TR78] [TR172]

5.12.10 Cabinet Thickness

The TFCS cabinet housing shall be fabricated of 0.125 inch minimum thickness aluminum sheet. [TR78] [TR173]

5.12.11 Rodent Resistant

The TFCS cabinet housings shall be designed to reduce or eliminate any openings which might permit rodents or insects to enter the cabinet. [TR78] [TR174]

5.12.12 High Security Design

The TFCS shall support a high-security cabinet design which permits the usage of 3/16” sheet aluminum for the cabinet housing. [TR78] [TR175]



5.12.13 Cabinet Surface Preparation

The aluminum surface shall be cleaned, etched and rinsed. The cleaning and etching procedure shall be to immerse in inhabited alkaline cleaner at 71 degrees C for five minutes (Oakite 61A, Diversey 909 or equivalent in mix of the 6 to 8 ounces per gallon to distilled water). Rinse in cold water. Etch in a sodium solution at 66 degrees C for 5 minutes 90.5 ounce sodium fluoride plus 5 ounces of sodium hydroxide mix per gallon to distilled water. Rinse in cold water. Desmut in a 50% by volume nitric acid solution at 20 degrees C for 2 minutes. Rinse in cold water. Dry surfaces by preheating in an oven for 15 minutes at 400 degrees F. Remove and coat the surfaces using TCI Wheel Silver # 9811- 0110 with a minimum film build of not more than 2 mils total thickness. Place back into preheated oven for 10 minutes minimum at 360 degrees F to gel the base coat. Remove and coat the surfaces using TCI Anti-graffiti Clear # 9810-0231. Place back into oven and fully cure at 380 degrees F for 40 minutes. [TR78] [TR176]

5.12.14 Video Monitor

The TFCS shall provide storage and electrical power for a small (handheld?) video monitor. [TR177]

5.12.15 Backup Power Batteries

The TFCS design shall include a cabinet configuration that provides internal space for the housing of batteries used to provide backup power. [TR178]

5.12.16 Law Enforcement Access

The TFCS shall provide protected access by law enforcement personnel to the following cabinet functions: [TR179]

Signals ON/OFF FLASH / AUTO operation Manual Control Enable (MCE) Interval Advance (IA)

5.12.17 External Antenna

The TFCS shall provide, for all types of cabinet housings, a standard method for the mounting of an external antenna. [TR160]

5.12.18 Limited Enclosure Access

The TFCS shall provide doors with keylocks for installation, removal and service of major assemblies, plus a door with keylocks for access to police panel. [TR180]

5.13 Diagnostic and Status Monitoring

5.13.1Diagnostic Display Unit Local Display

The TFCS shall contain a Diagnostic Display Unit (DDU) which supports local display of both historical and current cabinet status and log data collected by the monitoring subsystem. [TR99]



5.13.2Diagnostic Time Required

The TFCS design shall allow maintenance personnel to diagnose problems within the cabinet and to exchange defective subassemblies and modules in no more than five minutes.



6 APPENDICES

6.1 Compliancy

The TFCS shall support non-standard housing sizes as long as the remainder of the standard are met.Special input devices OK as long as mimic other devices?

6.2 Acronyms

Term DefinitionAASHTO American Association of State Highway and Transportation OfficialsAC alternating currentATC Advanced Transportation ControllerCBD Central Business DistrictCMU Cabinet Monitor UnitConOps Concept of OperationsDC direct currentEMI electromagnetic interferenceFHWA Federal Highway AdministrationESD Electrostatic DischargeGFI Ground Fault InterruptIEEE Institute of Electrical and Electronics EngineersI/F interfaceI/O input/outputIEC International Electrotechnical CommissionIMSA International Municipal Signal AssociationIPC Formerly, the Institute for Printed Circuits. This same institution was

later called the Institute Interconnecting and Packaging Electronic Circuits. It is now referred to as IPC-Association Connecting Electronics Industries.

ITE Institute of Transportation EngineersITS Intelligent Transportation SystemJPO Joint Program OfficeLED light emitting diodeMTBF mean time between failuresNEC National Electrical CodeNEMA National Electrical Manufacturers AssociationNRTL Nationally Recognized Testing LabNTCIP National Transportation Communications for ITS ProtocolNFPA National Fire Protection AssociationPF power factorRFI radio frequency interferenceSDO Standard Development OrganizationSEMP System Engineering Management PlanSEP Systems Engineering ProcessSSC Small-Sized CabinetStdRS Standards Requirements SpecificationTFCS transportation field cabinet systemUPS Uninterruptible Power Source



USA United States of America USDOT United States Department of TransportationVAC voltage alternating currentVDC voltage direct currentWG Working Group



6.3 Glossary

Term Definitionarc flash hazard Flashover of electric current that leaves its intended path and travels

through the air from one conductor to another, or to ground.assembly A physical entity within the system made up of two or more modules.Central system Transportation Management Centerchannel A signal path or set of signal paths for transmitting electric signals

from a source to a destination, usually in distinction from other parallel paths. See Input Channel and Output Channel.

Clean power Electrical power that is protected against surges and spikes and filtered to regulate electrical noise.

Closed-loop system Distributed processor traffic control systemcontact closure A sensor or switch which closes or opens a set of electrical contacts

in accordance with some process change. An applied electrical signal then determines whether the circuit is open or closed. Current flows if the circuit is closed.

dBA A-weighted decibels referring to noise and noisome effects on humans and animals.

Element A general term used for a part, assembly or subsystem that is viewed as an entity for purposes of design, operation, or reporting. An element may refer to various levels of detail such as the elements of the TFCS or components on a PCB.

Field display Operator interface external to cabinetfield input Sensors external to cabinet, such as loop detectors, pushbuttonsfield management station Transportation Management Centerfield output Controlled loads external to cabinet, such as traffic signal headsg The amount of acceleration due to the gravitational force at a

particular location.Hot swap A disconnection of a element and a reconnection of the same or a

replacement element without first turning off the power at the connection interface.

Hot swappable Able to be hot swapped.Hz Hertz. A unit of frequency. One hertz has a periodic interval of one

second.inHG Inches of mercury. A unit of measurement for pressure.Input channel Set of signal paths connecting TFCS to field sensorsinterface Shared boundary across which two separate components of a

computer system exchange informationknock-down Traffic control device rendered inoperable by collisionsmodule The smallest element of physical management described in these

requirements (i.e., a replaceable device). Typically a module is a functional device that plugs into an assembly.

Output channel Set of signal paths connecting TFCS to field loadsoutput power Electrical power that is suitable for operating field displays.Part An element not normally useful by itself and not readily capable of

further disassembly for maintenance purposes (e.g., bolt, nut, bracket, semiconductor, printed circuit board),

raw power Electrical power that is protected against surges and spikes.Remote External to cabinet



Term Definitionservice powersubsystem A portion of a system containing two or more integrated elements

which, while not completely performing the specific function of a system, may be isolated for purpose, design, test, or maintenance.

System A collection of interacting, interrelated, or interdependent elements forming a collective, functioning entity.

UL Underwriters Laboratorieswell-formed Expressed in a way that obeys rules for constructing formulas in a

certain language

6.4 Needs to Requirements Traceability

The Needs to Requirements Traceability Matrix (NRTM), presented below, maps the user needs defined in Section 4 to the requirements defined in Section 5. The matrix table can be used by:

A user or specification writer to indicate which requirements are to be implemented in a project-specific implementation; and

The supplier and user, as a detailed indication of the capabilities of the implementation.

Note 1:

All sections of ITS Cabinet Standard Version 1.02.17b will be retained for backwards compatibility and software compatibility with legacy installations. Traceablity from Needs to Requirements to Design Content tables below are limited to new Needs, new Requirements, new Major Assemblies and new Subassemlies.


Minutes User Need Change Vote TR User Need ID Requirements Title12/16/2010 ADDED USER NEED - The user needs the TFCS to provide field outputs that

are electrically safe. This provides protection in the case of a "knock down" of a pole supporting one or more field displays during a storm or traffic accident. The intent is to have voltage and current levels below those which are dangerous to humans

Consensus [1] 4.3.4.2 Electrically Safe Field Outputs

9/13/2010 DELETED USER NEED - UL be removed from the cabinet needs 11-0-1 [2] 4.3.1.15 User Safety

Minutes Guidance Vote TR Requirements ID Requirements Title9/13/2010 GUIDANCE - OK to change SB3 Consensus [37] 5.7.1.4 Receives Current Levels from the Output

Assembly5.7.1.5 Receives Voltage Levels from the Output

Assembly9/13/2010 GUIDANCE - Permissible to perform the functionality of the AMU within the

load switchConsensus [38] 5.4.1.2 Send Current Levels to the Monitor Assembly

9/13/2010 GUIDANCE - If more diagnostics are necessary, we may add a new device to do diagnostics

Consensus [39] 5.4.1.3 Send Voltage Levels to the Monitor Assembly

9/13/2010 GUIDANCE - WG discussed the use of four channel load switches but decided that six channel were best.

Consensus [40] 5.4.3.2 Three Signal Indications per HDSP120 Channel

9/13/2010 GUIDANCE - Use the ITS Cabinet V1 (RD[4]) environmental Consensus [41] 5.1 General Characteristics9/13/2010 GUIDANCE - We go forward with our best design proposals based on the

user needs and requirements from our discussion (at the meeting implied). Backward compatibility to the ITS Cabinet V1 Standard (RD[4]) cabinet systems is secondary

10-0-1 [42] 5.1 General Characteristics

9/13/2010 GUIDANCE - Current language that references only the NEC is sufficient 11-0-1 [43] 5.1.39 NEC Best Practices 9/13/2010 GUIDANCE - As a design goal, it is allowable to eliminate the need for the

PDA5-4-3 [44] 5.7 Monitor Assembly

10/28/2010 GUIDANCE - It is the intent of the design team, to focus on the two door cabinet design but the solution should not preclude the use of a single door cabinet with a removable rack

Consensus [45] 5.1.2 Rack Mountable

11/18/2010 GUIDANCE - In favor of using the proposed output assembly and field termination. Refer to posted Considered Concept

Consensus [46] 5.1.7 Utilizes an Output Assembly

11/18/2010 GUIDANCE - In favor of using the AMU2 concept? Concept rejected 0-5-2 [47] 5.7 Monitor Assembly11/23/2010 GUIDANCE - It was the consensus of the group to keep are existing serial

architectureConsensus [48] 5.1.3.1 Connectivity

11/29/2010 GUIDANCE - Motion that the ITS Cabinet V2 architecture should include an 4-8-2 [49] 5.7 Monitor Assembly



Minutes Guidance Vote TR Requirements ID Requirements TitleAMU2 device. Rejected

Description of the AMU2.- This device will reside within the output assembly. It will have a diagnostic port similar to the SIU. It will have LED indicators for: transmit/receive for the load switches, transmit/receive for SB3 (to the CMU), a general fault indicator and possibly a power indicator. The AMU2 will poll the load switches in the assembly and forward the information to the CMU. The purpose is to provide information for diagnosing a bus fault within the output assembly.

12/16/2010 GUIDANCE - It was the consensus of the WG to have one flasher, one breaker, and four protected outputs

Consensus [50] 5.7.4.1 Four Fused Output Channels

12/16/2010 GUIDANCE - It was the consensus of the WG to have four circuit breakers per output assembly

Consensus [51] 5.4.6 Output Circuit Breakers

12/16/2010 GUIDANCE - It was discussed that a breaker will be added in the service assembly for fan, light, and GFI. Call it a "facilities" breaker

Consensus [52] 5.9.5 Facilities Breaker Switch

2/17/2011 GUIDANCE - It was the consensus of the group present that these power limitations should apply to the low power/voltage cabinet option only. - Less than 30 Volts RMS- Less than 42 Volts Peak- Less than 60 Volts DC

Consensus [53] 5.4.4 Low Voltage Switch Pack Modules

5/9/2011 GUIDANCE - ITS CAB WG UNANIMOUSLY WG AGREED that the wiring and breakers should follow the ampacity of the NEC.

Consensus [54] 5.1.39 NEC Best Practices

5/16/2011 GUIDANCE: Summary: Ralph stated the assemblies voted and accepted by the WG.- Controller Subsystem- Input Assembly- Monitor Assembly- Output Assembly- Field Termination Assembly- Serial Bus Assembly- Cabinet Power Supply- Clean Power Bus Assembly- Service Assembly

Consensus [55] 5 System Requirements

6/24/2011 GUIDANCE - WG confirmed that for the low-voltage option 48 Volts DC +/-2 unless our process proves otherwise.

Consensus [56] 5.4.4 Low Voltage Switch Pack Modules



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title4.3.1.1 Open Architecture 5.1.1.1 Patents and Copyrights [57] 5.7 User Needs, Extracted from Posted Working

Group Meeting Notes5.1.1.2 Commonly-Available Components [58] Note 1 Retained V1 Standards

4.3.1.2 Modular 5.1.2 Rack Mountable [59] 7.1.3 Service Assembly Mechanical7.2.2 Clean Power Assembly Material List7.4.2 Clean Power Assembly Material List7.7.3 Communications Bus Assembly Mechanical

5..1.5 Utilizes a Controller Subsystem [60] 6.2.6 Controller Assembly5..1.6 Utilizes an Input Assembly [60] 6.2.8 48 Channel NEMA Input Assembly5..1.7 Utilizes an Output Assembly [60] 6.2.9 16 Phase Output Assembly5..1.8 Utilizes an Input Assembly [60] 6.2.8 48 Channel NEMA Input Assembly5..1.9 Utilizes an Input/Output Assembly [60] Figure 2 INPUT / OUTPUT ASSEMBLY: 24 CHANNEL NEMA

INPUTS + 12 PHASE OUTPUTS5..1.10 Utilizes a Monitor Assembly [60] Figure 2 CMU5..1.11 Utilizes a Service Assembly [60] 6.2.1 Service Assembly5..1.12 Utilizes an Serial Bus Assembly [60] 6.2.7 Communications Bus Assembly5..1.13 Utilizes a Clean Power Bus Assembly [60] 6.2.2 Clean Power Assembly5..1.14 Utilizes a Cabinet Power Supply [60] 6.2.3 Power Supply Assembly5.3.7 Hot-Swappable Input Devices [61] 8.5 User Safety5.3.8 Multiple Input Assemblies [62] Figure 2 Multiple Input Assemblies5.1.1.3 Open Standards [63] Note 1

4.3.1.3 Scalable 5.3.5 48 Input Channels [64] 7.8 48 Channel NEMA Input Assembly Details5.3.8 Multiple Input Assemblies [64] Figure 2 Multiple Input Assemblies5.4.2 Up to Seven High Density Switch

Pack Modules[64] 7.9 16 Phase Output Assembly Details

5.1.42 Subsystems Not Interdependent [65] 8.4 Interoperability5..1.5 Utilizes a Controller Subsystem [66] 6.2.6 Controller Assembly5..1.6 Utilizes an Input Assembly [66] 6.2.8 48 Channel NEMA Input Assembly5..1.7 Utilizes an Output Assembly [66] 6.2.9 16 Phase Output Assembly



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title5..1.8 Utilizes an Input Assembly [66] 6.2.8 48 Channel NEMA Input Assembly5..1.9 Utilizes an Input/Output Assembly [66] Figure 2 INPUT / OUTPUT ASSEMBLY: 24 CHANNEL NEMA

INPUTS + 12 PHASE OUTPUTS5..1.10 Utilizes a Monitor Assembly [66] Figure 2 CMU5..1.11 Utilizes a Service Assembly [66] 6.2.1 Service Assembly5..1.12 Utilizes an Serial Bus Assembly [66] 6.2.7 Communications Bus Assembly5..1.13 Utilizes a Clean Power Bus Assembly [66] 6.2.2 Clean Power Assembly5..1.14 Utilizes a Cabinet Power Supply [66] 6.2.3 Power Supply Assembly5.1.43 Subsystem Quantities [67] Figure 2 Subsystems

4.3.1.4 Expandability 5.3.5 48 Input Channels [68] 7.8 48 Channel NEMA Input Assembly Details5.3.8 Multiple Input Assemblies [68] Figure 2 Multiple Input Assemblies5.4.2 Up to Seven High Density Switch


5..1.5 Utilizes a Controller Subsystem [69] 6.2.6 Controller Assembly5..1.6 Utilizes an Input Assembly [69] 6.2.8 48 Channel NEMA Input Assembly5..1.7 Utilizes an Output Assembly [69] 6.2.9 16 Phase Output Assembly5..1.8 Utilizes an Input Assembly [69] 6.2.8 48 Channel NEMA Input Assembly5..1.9 Utilizes an Input/Output Assembly [69] Figure 2 INPUT / OUTPUT ASSEMBLY: 24 CHANNEL NEMA

INPUTS + 12 PHASE OUTPUTS5..1.10 Utilizes a Monitor Assembly [69] Figure 2 CMU5..1.11 Utilizes a Service Assembly [69] 6.2.1 Service Assembly5..1.12 Utilizes an Serial Bus Assembly [69] 6.2.7 Communications Bus Assembly5..1.13 Utilizes a Clean Power Bus Assembly [69] 6.2.2 Clean Power Assembly5..1.14 Utilizes a Cabinet Power Supply [69] 6.2.3 Power Supply Assembly5.1.43 Subsystem Quantities [70] Figure 2 Subsystems

4.3.1.5 Extensibility 5.1.44 Future Subsystems [71] Note 1 Reserved Addresses5.3.8 Multiple Input Assemblies [71] Figure 2 Multiple Input Assemblies5.4.8 Multiple Output Assemblies [71] Figure 2 Multiple Output Assemblies5.1.1.3 Open Standards [72] Note 1 Retained V1 Standards



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title4.3.1.6 Space Efficient 5.1.15 Relocatable Elements [73] Figure 2 Subsystems4.3.1.7 Reliable and Continuous

Operation5.1.20 24/7 Operation [74] Note 1 Retained V1 Standards5.1.45 MTBF [75] Note 1 Retained V1 Standards5.1.46 Design Life [76] Note 1 Retained V1 Standards5.1.24 Derating [77] Note 1 Retained V1 Standards

4.3.1.8 Quality Construction 5.12.2 Aluminum Sheet [78] Note 1 Retained V1 Standards5.12.3 Aluminum Sheet Plating [78] Note 1 Retained V1 Standards5.12.4 Aluminum Sheet Plating [78] Note 1 Retained V1 Standards5.12.5 Cold Rolled Steel [78] Note 1 Retained V1 Standards5.12.6 Cold Rolled Steel Plating [78] Note 1 Retained V1 Standards5.12.7 Stainless Steel Hardware [78] Note 1 Retained V1 Standards5.12.8 Doors [78] Note 1 Retained V1 Standards5.12.9 Ventilation [78] Note 1 Retained V1 Standards5.12.10 Cabinet Thickness [78] Note 1 Retained V1 Standards5.12.11 Rodent Resistant [78] Note 1 Retained V1 Standards5.12.12 High Security Design [78] Note 1 Retained V1 Standards5.12.13 Cabinet Surface Preparation [78] Note 1 Retained V1 Standards

4.3.1.9 Extreme Temperatures and Humidity

5.1.26 Operating Temperature Range [79] Note 1 Retained V1 Standards5.1.25 Storage Temperature Range [80] Note 1 Retained V1 Standards5.1.27 Operational Relative Humidity [81] Note 1 Retained V1 Standards

4.3.1.10 Limit Electronic Emissions 5.1.35 Electronic Emissions [82] Note 1 Retained V1 Standards4.3.1.19 Electrostatic Discharge

Resistant5.1.34 Electrostatic Discharge (ESD)

Resistant[83] Note 1 Retained V1 Standards

4.3.1.11 Limit Audible Noise 5.1.31 Noise Level [84] Note 1 Retained V1 Standards4.3.1.12 Withstand Vibration and

Shock5.1.32 Shock [85] Note 1 Retained V1 Standards5.1.33 Vibration [86] Note 1 Retained V1 Standards

4.3.1.13 Quick Transfer of Configuration and Application Information

5.1.5 Uses a Controller Subsystem [87] 6.2.6 Controller Assembly



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title4.3.1.15 User Safety 5.1.38 No Sharp Edges [88] Note 1 Retained V1 Standards

5.1.39 NEC Best Practices [89] Note 1 Retained V1 Standards5.1.39 NEC Compliance [90] Note 1 Retained V1 Standards

4.3.1.16 Energy Efficient 5.1.29 Power Factor [91] 6.2.3 Power Supply Assemblies5.1.30 Power Supply Efficiency [92] 6.2.3 Power Supply Assemblies

4.3.1.17 No Components Containing Liquid Mercury

5.1.40 No Liquid Mercury [93] Figure 18 16 Phase Field Termination Assembly Block Diagram

5.1.40 No Liquid Mercury [94] Figure 18 16 Phase Field Termination Assembly Block Diagram

4.3.1.20 Previously Deployed ITS Cabinets

5.5.5 High-Density Inputs [95] 6.2.8 48 Channel NEMA Input Assembly5.4.2 Up to Seven High Density Switch


4.3.1.18 Diagnostic Testing 5.7.1.7 Externally Accessible V and I [97] Figure 2 Serial Bus 34.3.1.19 Electrostatic Discharge

Resistant5.1.34 Electronic Discharge [98] Note 1 Retained V1 Standards

4.3.1.20 Minimize Time for Maintenance Personnel

5.13.1 Diagnostic Display Local Display [99] Figure 2 CMU5.1.10 Utilizes a Monitor Assembly [99] Figure 2 CMU

4.3.2.1 Commonly Deployed Field Sensors

5.3.2 Commonly-Deployed Input Devices [100] 6.2.8 48 Channel NEMA Input Assembly5.3.3 NEMA TS 2 Four-Channel Detector

Modules[101] 6.2.8 48 Channel NEMA Input Assembly

5.3.5 48 Input Channels [102] 6.2.8 48 Channel NEMA Input Assembly5.3.4 Four-Channel Isolator Modules [103]

4.3.2.2 High Density Input Devices 5.3.3 NEMA TS 2 Four-Channel Detector Modules

[104] 6.2.8 48 Channel NEMA Input Assembly

5.4.2 Up to Seven High Density Switch Pack Modules

[105] 6.2.9 16 Phase Output Assembly

5.3.5 48 Input Channels [106] 6.2.8 48 Channel NEMA Input Assembly5.3.8 Multiple Input Assemblies [107] Figure 2 Multiple Input Assemblies

4.3.3.1 Application Computer Interface

5.2.1 Controller Subsystem Communications Interfaces

[108] 6.2.6 Controller Assembly



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title5.1.5 Utilizes a Controller Subsystem [109] 6.2.6 Controller Assembly

4.3.3.2 Intersection Control Applications

5.2.3 Intersection Control Applications [110] 6.2.6 Controller Assembly

4.3.3.3 Ramp Metering Applications 5.2.4 Ramp Meter Control Applications [111] 6.2.6 Controller Assembly4.3.3.4 Data Collection Applications 5.2.5 Data Collection Applications [112] 6.2.6 Controller Assembly4.3.4.1 High Density Output Devices 5.1 General Characteristics [113] Note 1 Retained V1 Standards

5.4.3.1 Two Output Channels per HDSP120 [114] 7.13 SP Dual Switch Pack Assembly Details5.4.10 Regular Density Output Files [114] Note 1 Retained V1 Standards5.4.2 Up to Seven High Density Switch

Pack Modules[115] 6.2.9 16 Phase Output Assembly

5.4.8 Multiple Output Assemblies [116] Figure 2 Multiple Output Assemblies4.3.4.3 Field Displays 5.4.3.3 Amperes per HDSP120 Channel [117] 7.13 SP Dual Switch Pack Assembly Details

5.7.3 CMU Display Unit [117] Figure 2 CMU4.3.4.2 Electrically Safe Field Outputs 5.4.4 Low Voltage Switch Pack Modules [118] 7.13 SP Dual Switch Pack Assembly Details

5.4.4 Low Voltage Switch Pack Modules [119] 7.13 SP Dual Switch Pack Assembly Details4.3.5 Fault Operation 5.6.3 Channel-Programmable Flasher

Outputs[120] 6.2.1 Service Assembly

5.7.4.1 Four Fused Output Channels [121] Figure 2 Power Distribution4.3.6.1 TFCS Status 5.7.2 Cabinet Monitor Unit (System} [122] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Bus) [123] Figure 2 CMU5.7.2 Cabinet Monitor Unit (Specific

Monitored Conditions)[124] Figure 2 CMU

4.3.6.2 Field Output Monitoring 5.4.1.3 Send Voltage Levels to Monitor Assembly (AC Voltage)

[125] 7.13.1 Dual Switch Pack Assembly Block Diagram

5.4.1.3 Send Voltage Levels to Monitor Assembly (DC Voltage)

[126] 7.13.1 Dual Switch Pack Assembly Block Diagram

5.7.2 Cabinet Monitor Unit (Voltage Measurement Interval)

[127] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Measure AC Current)

[128] Figure 2 CMU



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title5.7.2 Cabinet Monitor Unit (Current

Measurement Interval)[129] Figure 2 CMU

4.3.6.3 Field Display Monitoring 5.7.3 CMU Display Unit [130] Figure 2 CMU4.3.6.4 Internal Communications

Monitoring5.1.3 Serial Bus Communications

Architecture[131] Figure 2 SB1 & SB2

4.3.6.5 User Interface 5.7.3 CMU Display Unit [132] Figure 2 CMU5.7.1.6 Ethernet Communications [133] Figure 2 CMU & Controller5.7.1.6 Ethernet Communications

(Diagnostic Display Unit Historical Data)

[134] Figure 2 CMU

4.3.6.6 Response to Malfunction or Anomaly

5.7 Monitor Assembly [135] Figure 2 CMU5.7.1.1 Receives Switch Pack Driver

Information from the Controller Subsystem

[136] 6.2.6 Controller Assembly

5.7.2 Cabinet Monitor Unit (Monitor Actual Field Output States)

[137] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Monitor Field Output Interval Length)

[138] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Monitor Field Output Voltages and Currents)

[139] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Channel Pair Permissive Programming)

[140] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Voltage and Current Thresholds)

[141] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Configurable Response)

[142] Figure 2 CMU

4.3.6.7 Configuration of Monitoring 5.7.2 Cabinet Monitor Unit (Conflict Monitor)

[143] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Channel Pair Permissive Programming)

[144] Figure 2 CMU



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title5.7.2 Cabinet Monitor Unit (Voltage and

Current Thresholds)[145] Figure 2 CMU

5.7.2 Cabinet Monitor Unit (Configurable Response)

[146] Figure 2 CMU

4.3.6.8 Controlled Access to Monitoring Configuration Information

5.7.2 Cabinet Monitor Unit (Password-Protected Configuration)

[147] Figure 2 CMU

4.3.1.14 Nominal Service Power 5.9.7 Service Power Input Options [148] 6.2.1 Service Assembly5.9.7.2 Low Voltage Service Assembly [149] 6.2.1 Service Assembly5.9.7.1 High Voltage Service Assembly [150] 6.2.1 Service Assembly

4.3.7.1 Clean Power Distributed 5.10.1 Clean Power Input [151] 6.2.2 Clean Service Power Assembly4.3.7.2 Output power Distributed 5.1.47 24 VDC Output Power [152] 6.2.4 DC Power Assembly

5.1.47 12 VDC Output Power [152] 6.2.4 DC Power Assembly4.3.7.3 Power Conversion 5.10.4 24 VDC Output Power [153] 6.2.4 DC Power Assembly

5.10.5 12 VDC Output Power [153] 6.2.4 DC Power Assembly5.9.7.2 Low Voltage Service Assembly

(Internal AC Inverter struck)[154] Struck Struck

5.9.6 Backup Power Subsystem [155] 6.2.1 Service Assembly, 48 VDC Unit4.3.7.4 Backup Power Provisions 5.9.6 Backup Power Subsystem [156] 6.2.1 Service Assembly, 48 VDC Unit4.3.8.1 System Reports 5.7.3 CMU Display Unit [157] Figure 2 CMU4.3.8.2 System Reporting

Distribution5.7.1.6 Ethernet Communications [158] Figure 2 Controller & CMU

4.3.8.3 Non-Volatile Information 5.7.2 Cabinet Monitor Unit [159] Figure 2 CMU5..1.5 Utilizes a Controller Subsystem [159] 6.2.6 Controller Assembly

4.3.9.1 External Communications Capability

5.12.17 External Antenna [160] 9.3 Cabinet Layout Examples

4.3.9.2 Standardize External Interfaces

5.1.1.3 Open Standards [161] Note 1 Retained V1 Standards

4.3.10.1 External Mounting 5.1.17 Legacy Housing [162] Note 1 Retained V1 Standards5.1.18 Small Size Cabinet [163] 9.3 Example Cabinet Layouts



Needs Id Needs Title Requirements Id Requirements Title [TRn] HL Design ID HL Design Title4.3.10.2 Corrosion Resistant Material 5.12.1 Corrosion Resistant [164] Note 1 Retained V1 Standards

5.12.2 Aluminum Sheet [165] Note 1 Retained V1 Standards5.12.3 Aluminum Sheet Plating [166] Note 1 Retained V1 Standards5.12.4 Stainless Steel Sheet [167] Note 1 Retained V1 Standards5.12.5 Cold Rolled Steel [168] Note 1 Retained V1 Standards5.12.6 Cold Rolled Steel Plating [168] Note 1 Retained V1 Standards5.12.7 Stainless Steel Hardware [170] Note 1 Retained V1 Standards

4.3.10.3 Cabinet Access 5.12.8 Doors [171] 9.3 Example Cabinet Layouts4.3.10.4 Physical Environment 5.12.9 Ventilation [172] Note 1 Retained V1 Standards

5.12.10 Cabinet Thickness [173] Note 1 Retained V1 Standards4.3.10.5 Animal and Insect Resistant 5.12.11 Rodent Resistant [174] Note 1 Retained V1 Standards4.3.10.6 Vandalism and Theft

Resistant5.12.12 High Security Design [175] Note 1 Retained V1 Standards

4.3.10.7 Graffiti Resistant 5.12.13 Cabinet Surface Preparation [176] Note 1 Retained V1 Standards4.3.10.8 Video Monitor Provision 5.12.14 Video Monitor [177] 6.2.6 Controller Assembly, Ethernet4.3.10.9 Battery Housing Provision 5.12.15 Backup Power Batteries [178] External Housing for Outgas Management

4.3.10.10 Law Enforcement Personnel Access

5.12.16 Law Enforcement Access [179] 9.3 Example Cabinet Layouts

4.3.9.11 Limited Enclosure Access 5.12.18 Limited Enclosure Access [180] 9.3 Example Cabinet Layouts4.3.11.1 Internal Communications

Capability5.1.3.1 Connectivity [181] Figure 2 SB1 & SB25.1.3.1 Connectivity (ITS V1 BUS1/BUS2

Support guidance)[182] Figure 2 SB1 & SB2

4.3.11.2 Standardized Interfaces 5.1.5 Utilizes a Controller Subsystem [183] 6.2.6 Controller Assembly5.2.1 Controller Subsystem

Communications Interfaces[184] 6.2.6 Controller Assembly

5.4.1 Output Assembly Communications Interfaces

[185] Figure 2 Output Assembly, SB1, SB2, SB3
