ATC 5301 v02 StdHLD v02.02

Transcription

1 A Working Group Draft of the Advanced Transportation Controller Joint Committee ATC 5301 v02 StdHLD v02.02 Advanced Transportation Controller Cabinet Standards High Level Design (StdHLD) September 30, 2016 StdHLD in support of: For approval by: For use by: Prepared by: ITS Cabinet v2.0 Standard Development ITE Contract: DTFH61-11-D Task 1503 Joint Committee on the ATC Siva Narla, Chief Engineer and ITS Standards Manager Institute of Transportation Engineers Dave Miller, Chair of the Joint Committee on the ATC Copyright 2016 AASHTO/ITE/NEMA. All rights reserved. ITSCabStdHLD_0202_ doc Page 1 of 128

2 CHANGE HISTORY DATE NOTE 09/30/2016 Updated after HLD Walkthrough by Working Group: 1. Added 48 VDC (Mandatory) to Assembly Power interface on High Voltage Version 2. Added 48 VDC (Mandatory) to Assembly Power interface on Low Voltage Version 3. Input Functionality element outline from solid to dashed on High Voltage Version 4. Input Functionality element outline from solid to dashed on Low Voltage Version 08/31/2016 Updated after Requirements Walkthrough by Working Group 11/02/2015 Added Example Cabinet Layouts to Appendix 05/30/2014 Corrected header from StdRS to StdHLD, added End Users on page 8 05/27/2014 Page 8: Corrected link to ITE V2 web page 04/02/2014 Initial Standards High Level Design (StdHLD) Version ITSCabStdHLD_0202_ doc Page 2 of 128

3 NOTICE Joint NEMA, AASHTO and ITE Copyright and Intelligent 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, EPRESSED 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. ITSCabStdHLD_0202_ doc Page 3 of 128

4 CONTENTS 1 PURPOSE OF THE DOCUMENT SCOPE OF PROJECT REFERENCED DOCUMENTS... 9 CONVENTIONS USED IN THIS DOCUMENT HIGH LEVEL DESIGN PROCESS Inputs to StdHLD Process Outputs of StdHLD Process Attribute Priorities of StdHLD Process ITS Cabinet V2 Attribute Ranking Survey Data Scatter Plot of Averages and Standard Deviations HIGH LEVEL DESIGN High Level Functional Block Diagrams High Level Design Elements Functionality Elements Subassembly Elements Interface Elements Requirements LIST OF TABLES Table 1: ITS Cabinet V2 Attribute Ranking (1 is highest priority) Table 2: Attribute Survey Data Table 3: Scatter Plot of Averages and Standard Deviations Table 4: Cabinet Table 5: Input Table 6: IN SLOT Table 7: Detector Termination Table 8: Output Table 9: OUT SLOT Table 10: Output Termination Table 11: Service, High Voltage Version Table 12: Service, Low Voltage Version Table 13: Power, High Voltage Version Table 14: Power, Low Voltage Version Table 15: Monitor Table 16: Auxiliary Display Unit Table 17: Door Switch Table 18: Fan and Thermostat Table 19: Input Sensor Table 20: Serial Interface Unit Table 21: Dual HV Load Switch Table 22: Dual LV Load Switch Table 23: Dual HV Flasher Table 24: Dual LV Flasher Table 25: Cabinet Monitor Unit ITSCabStdHLD_0202_ doc Page 4 of 128

5 Table 26: GFCI Receptacle Table 27: Clean AC Receptacle Table 28: SB1/SB Table 29: SB Table 30: SIU IN Table 31: SIU OUT Table 32: CDC Option Table 33: CC Table 34: REQID Patents and Copyrights Table 35: REQID Commonly-Available Components Table 36: REQID Rack Mountable Table 37: REQID Utilizes a Controller Subsystem Table 38: REQID Utilizes an Input Assembly Table 39: REQID Utilizes an Output Assembly Table 40: REQID Utilizes an Input/Output Assembly Table 41: REQID Utilizes a Field Terminal Assembly Table 42: REQID Utilizes a Monitor Assembly Table 43: REQID Utilizes a Service Assembly Table 44: REQID Utilizes a Serial Bus Assembly Table 45: REQID Utilizes a Clean Power Bus Assembly Table 46: REQID Utilizes a Cabinet Power Supply Assembly Table 47: REQID Hot-Swappable Input Devices Table 48: REQID Multiple Input Assemblies Table 49: REQID Open Standard Table 50: REQID Input Channels Table 51: REQID Multiple Input Assemblies Table 52: REQID At least seven high density switch pack modules Table 53: REQID Subsystems not interdependent Table 54: REQID Subsystem Quantities Table 55: REQID Multiple Output Assemblies Table 56: REQID Future Subsystems Table 57: REQID Relocating Elements Table 58: REQID /7 Operation Table 59: REQID MTBF Table 60: REQID Design Life Table 61: REQID Derating Table 62: REQID Corrosion Resistance Table 63: REQID Aluminum Sheet Table 64: REQID Aluminum Sheet Plating Table 65: REQID Stainless Steel Sheet Table 66: REQID Cold Rolled Steel Table 67: REQID Cold Rolled Steel Plating Table 68: REQID Stainless Steel Hardware Table 69: REQID Doors Table 70: REQID Ventilation Table 71: REQID Cabinet Thickness Table 72: REQID Rodent Resistance Table 73: REQID High Security Design Table 74: REQID Cabinet Surface Presentation Table 75: REQID Operating Ambient Temperature Table 76: REQID Storage Temperature Range Table 77: REQID Operational Relative Humidity Table 78: REQID Electronic Emissions ITSCabStdHLD_0202_ doc Page 5 of 128

6 Table 79: REQID Electrostatic Discharge (ESD) Table 80: REQID Noise Level Table 81: REQID Shock Table 82: REQID Vibration Table 83: REQID No Sharp Edges Table 84: REQID NEC Best Practices Table 85: REQID Power Factor Table 86: REQID Power Supply Efficiency Table 87: REQID No Liquid Mercury Table 88: REQID High Density Inputs Table 89: REQID Externally Accessible V and I Table 90: REQID Diagnostic Display Local Display Table 91: REQID Utilizes a Monitor Assembly Table 92: REQID Commonly-Deployed Input Devices Table 93: REQID NEMA TS 2 Four-Channel Detector Modules Table 94: REQID Four-Channel Isolator Modules Table 95: REQID Controller Subsystem Communications Interfaces Table 96: REQID Receives Detector Status Information Table 97: REQID Sends Field Output Commands Table 98: REQID Sends Switch Pack Driver Information to the Monitor Assembly Table 99: REQID Sends Flash Command to the Monitor Assembly Table 100: REQID Receives CMU Programming Information from Monitor Assembly Table 101: REQID Signal Control Priority Table 102: REQID Intersection Control Applications Table 103: REQID Ramp Meter Control Applications Table 104: REQID Sends Field Input Data Table 105: REQID Sends Detector Status Information Table 106: REQID Two Output Channels per HDSP Table 107: REQID Two Output Channels per HDSP Table 108: REQID Amperes per HDSP120 Channel Table 109: REQID CMU Display Unit Table 110: REQID Low Voltage Switch Pack Modules Table 111: REQID Channel-Programmable Flasher Outputs Table 112: REQID Four Fused Output Channels Table 113: REQID Cabinet Monitor Unit Table 114: REQID Send Voltage Levels to Monitor Assembly (AC Voltage) Table 115: REQID Send Voltage Levels to Monitor Assembly (AC Voltage) Table 116: REQID Ethernet Communications Table 117: REQID Receives Switch Pack Driver Information from Controller Subsystem. 110 Table 118: REQID Service Power Input Options Table 119: REQID High Voltage Service Assembly Table 120: REQID Clean Power Input Table 121: REQID VDC Output Power Table 122: REQID VDC Output Power Table 123: REQID VDC Output Power Option Table 124: REQID Low Voltage Service Assembly Table 125: REQID Backup Power Subsystem Interface Table 126: REQID Backup Power Subsystem Switchover Table 127: REQID External Antenna Table 128: REQID Legacy Housing Table 129: REQID Small Size Cabinet Table 130: REQID Video Monitor Table 131: REQID Backup Power Source ITSCabStdHLD_0202_ doc Page 6 of 128

7 Table 132: REQID Law Enforcement Access Table 133: REQID Limited Enclosure Access Table 134: REQID Receives Field Output Commands Table 135: REQID Send current levels to the monitor assembly LIST OF FIGURES Figure 1: ITS Cabinet V2 Major Milestones ( 9 Figure 2: High Level Functional Block Diagram, High Voltage Version Figure 3: High Level Design Functional Block Diagram, Low Voltage Verson ITSCabStdHLD_0202_ doc Page 7 of 128

8 1 PURPOSE OF THE DOCUMENT This document is a Standards High Level Design (StdHLD) for the Intelligent Transportation System (ITS) Cabinet Version 2 (V2) project under the United States Department of Transportation (USDOT) Work Order T (ITS Cabinet v2 Maintenance). The StdHLD is based on the Concept of Operations (ConOps) adapted from Section 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. ConOps development began with User Needs presented by the following End Users at the 2008 Workshop in Austin T: Caltrans City of Houston T Georgia DOT Harris County T Kentucky DOT Los Angeles DOT Minnesota DOT New York City DOT San Francisco MTA This StdHLD describes the major functional elements, subassemblies and interfaces of the ITS Cabinet V2 system, traceable to the Standards Requirements Specification 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 StdHLD. The majority of the content of this document will be included in the ITS Cabinet Standard Version 2. When this occurs, this StdHLD 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 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 b (also known as Version 1 or V1, see RD[4]) was published in 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 were introduced into the Systems Engineering Process (see objective #2) that examines 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. ITSCabStdHLD_0202_ doc Page 8 of 128

9 Figure 1: ITS Cabinet V2 Major Milestones ( 3 REFERENCED DOCUMENTS [1] "2008 National Electrical Code," National Fire Protection Association (NFPA), Available from numerous sources. [2] ATC Controller Standard Revision v5.2b, ATC JC, 26 June Available from the Institute of Transportation Engineers. [3] "Electromagnetic Compatibility (EMC) - Part 4-2: Testing and Measurement Techniques - Electrostatic Discharge Immunity Test," IEC :2008. Available from the International Electrotechnical Commission. [4] Intelligent Transportation System (ITS) Standard Specification for Roadside Cabinets v b, ATC JC, 16 November Available from the Institute of Transportation Engineers. [5] NEMA Standards Publication TS v02.06 Traffic Controller Assemblies with NTCIP Requirements," 1 January Available from National Electrical Manufacturers Association. [6] "Systems Engineering Guidebook for ITS Version 2.0," FHWA, 2 January Available from the Federal Highway Administration, California Division. [7] "Work Order NTCIP and ITE Standards Development," USDOT JPO, 29 May Available from the Institute of Transportation Engineers. [8] ITS Cabinet V2 StdRS v01.04, ITS Cabinet Revision 2 Standards Requirements Specification (StdRS) ATC Cabinet Working Group, 31 January Available from Institute of Transportation Engineers [9] National Electrical Codes (NEC), NFPA 70, 2014 edition Available from National Fire Protection Association (110.27) [10] Model 2070 Controller Standard Version 03, ATC 5202 v03.04, December 28, Available from Institute of Transportation Engineers. [11] ITS Cabinet V2 Attribute Priorities, Pillar Consulting Inc, September 23, 2009 [12] Cabinets, Racks, Panels and Associated Equipment, EIA-310, Electronic Industries Alliance ITSCabStdHLD_0202_ doc Page 9 of 128

10 CONVENTIONS USED IN THIS DOCUMENT RD [nn] indicates Reference Document number nn of Section 3 above [TR58] [TR nn] indicates Traceability of Requirements from StdRD to StdHLD 4 HIGH LEVEL DESIGN PROCESS 4.1 Inputs to StdHLD Process The StdHLD process considered the following inputs: Needs to Requirements Traceability Matrix (NRTM) of the StdRS which includes: o USDOE ban on the sale of incandescent bulbs o EPA mercury waste regulations o State legislation to eliminate shock hazard inside electrical cabinets o State legislation to eliminate shock hazard of field wires o State legislation to eliminate arc flash hazard under NFPA 70E o Rapid replacement of internal assemblies while in flash for worker safety o Low power features identified as high priority during the V2 User Needs workshop o Off-grid alternate power sources for continued operation during widespread power outage Guidance from Cabinet WG votes extracted from the posted WG meeting minutes Guidance from Cabinet WG consensus decisions extracted from the posted WG meeting minutes Considered Concepts presented by manufacturers in the WG meetings that: o Are posted on the ITE website o Meet the StdRS Requirements Equipment deployed on early Field Tests that meet the V2 Requirements Walkthrough of Requirements by Working Group Commercial Off the Shelf examples offered by WG manufacturers in lieu of prototypes The StdHLD process did not consider the following inputs: Equipment and Concepts that do not meet the V2 Requirements 4.2 Outputs of StdHLD Process This StdHLD includes the following: Functionality Elements Subassemblies Interfaces between Functionality Elements and Subassemblies This StdHLD does not include the following: Existing RD[4] Functionality Elements retained in the standard are referenced, not replicated Existing RD[4] Interfaces that are retained in the standard are referenced, not replicated Existing RD[5] Functionality Elements are referenced, not replicated 4.3 Attribute Priorities of StdHLD Process To resolve conflicting Requirements, a list of Cabinet Attributes was developed during the ITS Cabinet Workshop in November 2008 (RD [11]). The resulting 22 ITS Cabinet Attributes were included in a survey (atc@list.ite.org), to rank the importance when resolving conflicting Requirements. All of the attributes were considered important but those higher in rank were generally considered more important when compared to those lower in rank. On a given project an attribute that is lower in rank may actually be the most critical to the project such as "external dimensions" for a CBD (central business district) deployment. The ranking shown for all of the respondents was not significantly different from the ranking when only voting members of the WG were considered. ITSCabStdHLD_0202_ doc Page 10 of 128

11 This is not a claim on being representative of the entire industry (note that there were 22 respondents) but it is representative of the ITS Cabinet WG. The priority groups (PR/GRP) were identified (A, B, C, D) based on the clusters of the average scores for the attributes observed on the scatter plot. See Table ITS Cabinet V2 Attribute Ranking Table 1: ITS Cabinet V2 Attribute Ranking (1 is highest priority) Note: Reliability may consider: Number of field installations multiplied times the hours in service for deployed equipment [TR73] Calculated MTBF for new equipment with limited deployment [TR75] ITSCabStdHLD_0202_ doc Page 11 of 128

12 4.3.2 Survey Data Table 2: Attribute Survey Data ITSCabStdHLD_0202_ doc Page 12 of 128

13 4.3.3 Scatter Plot of Averages and Standard Deviations Table 3: Scatter Plot of Averages and Standard Deviations 5 HIGH LEVEL DESIGN 5.1 High Level Functional Block Diagrams ITSCabStdHLD_0202_ doc Page 13 of 128

14 Figure 2: High Level Functional Block Diagram, High Voltage Version ITSCabStdHLD_0202_ doc Page 14 of 128

15 TO CU C12S SB1/SB2 HIGH LEVEL DESIGN FUNCTIONAL BLOCK DIAGRAM: LOW VOLTAGE VERSION CABINET TYPICAL INPUT FUNCTIONALITY (NOTE 1) 48 8 SIU IN. DDM SIU IN DDM INPUT 1 INPUT 2 INPUT DDM INPUT 4 INPUT 5 INPUT 6 INPUT 7 INPUT 8 INPUT 9 INPUT 10 INPUT 11 INPUT 12 SIU (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) SIU (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) (NOTE 2) SENSOR 1 SENSOR 2 SENSOR 3 SENSOR 4 SENSOR 5 SENSOR 6 SENSOR 7 SENSOR 8 SENSOR 9 SENSOR 10 SENSOR 11 SENSOR 12 ASSY PWR CDC1 INPUT 1-4 INPUT 5-8 INPUT 9-12 INPUT INPUT INPUT CDC2 IPNUT INPUT INPUT INPUT INPUT INPUT CDC (NOTE 3) CDC SB1 / SB2 CDC1 INPUT 1-4 INPUT 5-8 INPUT 9-12 INPUT INPUT INPUT CDC2 INPUT INPUT INPUT INPUT INPUT INPUT FIELD IN 24 CHANNEL DETECTOR TERMINATION FUNCTIONALITY (NOTE 1) 24 CHANNEL DETECTOR TERMINATION FUNCTIONALITY (NOTE 1) 48 VDC (MANDATORY) & 24 VDC (MANDATORY) & 12 VDC (OPTIONAL) TYPICAL OUTPUT FUNCTIONALITY (NOTE 1) SIU OUT ASSY PWR FAN SERVICE FUNCTIONALITY (NOTE 1) SB1/SB2 SIU OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 OUTPUT 5 OUTPUT 6 DUAL LV LOAD SW 1 DUAL LV LOAD SW 2 DUAL LV LOAD SW 3 DUAL LV LOAD SW 4 DUAL LV LOAD SW 5 DUAL LV LOAD SW 6 OUTPUT 7 OUTPUT 8 DUAL LV LOAD SW 7 DUAL LV LOAD SW 8 T UTILITY TERMINAL BLOCKS MAIN BREAKERS TRANSIENT SUPPRESSOR / FILTER SB3 THERMOSTAT 48 VDC OUT CC SB3 CH 1-2 CH 3-4 CH 5-6 CH 7-8 CH 9-10 CH CH CH SIGNAL PWR SENSE IN & SIGNAL OUT 48V 0V G SERVICE ENTRY CC DOOR SWITCH ADU SB3 SB1 CC SB3 CMU #1 OF 4 SB3 UP TO 32 OUTPUT CHANNELS PER CMU TO ADDITIONAL INPUT, OUTPUT OR INPUT/OUTPUT ASSEMBLIES CH 1-2 CH 3-4 CH 5-6 CH 7-8 CH 9-10 CH TYPICAL OUTPUT TERMINATION FUNCTIONALITY (NOTE 1) CH CH FTR 1 FTR 2 FTR 3 FTR 4 FTR 5 FTR 6 FTR 7 FTR 8 FP1 FP2 FP3 FP4 FP5 FP6 FP7 FP8 FP9 FP10 FP11 FP12 FP13 FP14 FP15 FP16 INTERFACE INTERFACE FUNCTION ASSEMBLY LEGEND SYMBOL ELECTRICAL MECHANICAL STANDARD STANDARD STANDARD STANDARD NON-STANDARD OPTION STANDARD NON-STANARD OPTION STANDARD SIGNAL PWR FLASH IN 48 VDC ASSY PWR SIGNAL PWR POWER FUNCTIONALITY (NOTE 1) DUAL LV FLASHER FLASH OUT 48 VDC IN FACILITIES NOTES: 1. FUNCTIONAL ELEMENTS SHALL FIT WITHIN 19 EIA-310 DIMENSIONS. PACKAGING NOT CONTROLLED BY STANDARD 2. INPUTS SHALL BE CONTROLLED BY THE STANDARD AS FOLLOWS: DDM INPUT DEVICES SHALL MECHANICALLY CONFORM TO NEMA TS 2 Sec (see Figure 6-5) CONNECTOR TYPE SHALL CONFORM TO NEMA TS 2 PARAGRAPH CONNECTOR PIN ASSIGNMENT SHALL CONFORM TO NEMA TS-2 TABLE MAPPING OF SIGNALS FROM INPUT CONNECTORS TO SIU SHALL BE FIED BY THE STANDARD ALTERNATE MAPPING FROM INPUT CONNECTORS TO SIU SHALL BE ACCOMPLISED BY SOFTWARE - TYPICAL COMPATIBLE INPUT DEVICES INCLUDE: - NEMA 4-CHANNEL INDUCTIVE LOOP DETECTORS WITH (4) OUTPUT AND (4) STATUS WITHOUT INBUS - CALTRANS 222 (2) CHANNEL DETECTORS WITHOUT STATUS AND 224 (4) CHANNEL DETECTORS WITHOUT STATUS - INDUCTIVE LOOP DETECTORS WITHOUT STATUS - ISOLATORS - PREEMPTORS 3. CDC CABLE & CONNECTORS ARE OPTIONAL, BUT CONTROLLED BY STANDARD IF SUPPLIED Figure 3: High Level Design Functional Block Diagram, Low Voltage Verson ITSCabStdHLD_0202_ doc Page 15 of 128

16 5.2 High Level Design Elements Refer to Figure 2 High Voltage version and Figure 3 Low Voltage version. The Legend indicates: Rectangular symbol indicates a physical cabinet element Oval symbol indicates an interface to connect physical cabinet elements Hatched fill with broken border indicates the standard does not control mechanical dimensions Solid fill with solid border indicates the standard controls the mechanical dimensions for plug-in interchangeablity Electrical signals, signal names and signal functions are controlled by the standard in all cases Solid connecting line indicates the standard controls the connector and pin assignments for plugin interchangeability. Broken connecting line indicates the standard does not control the connector type and pin assignments. The signals are electrically identical amoung manufacturers, but may require an adapter cable for interchangeability Functionality Elements Table 4: Cabinet Element Type: Functionality Element Name: Cabinet Controlled by Standard? Requirement ID Traceability: , , , , Electrical: Yes , , , , , , , Dimensions: No , , Materials: Yes Description of Responsibility: Cabinet Functionality element is responsible to mechanically support and house other elements, subassemblies and interfaces. Guidance: Cabinet materials, quality, ventilation and safety are controlled by the standard Cabinet dimensions, layout and mounting are not controlled by the standard, including: ITS - NEMA Table 5: Input Element Type: Functionality Controlled by Standard? Electrical: Yes Mechanical: No Element Name: Input Requirement ID Traceability: 5.1.6, 5.1.8, 5.3.7, 5.3.8, 5.3.5, 5.5.5, 5.3.2, 5.3.3, 5.3.4, , , , , 5.1.2, , 5.3.8, , , , , , , , , , , , Description of Responsibility: Input Functionality element is responsible to mechanically support, power and electrically connect IN SLOT(s) to SIU(s) Guidance: Input Functionality supports standard IN SLOTs that accommodate input sensors such as: - NEMA 4-channel inductive loop detectors with (4) outputs and (4) status - CALTRANS 222 style loop detectors with (2) outputs and no status - CALTRANS 224 style loop detectors with (4) outputs and no status - Inductive loop detectors without status - Isolators - Preemptors Examples of Input Functionality include detector racks. ITSCabStdHLD_0202_ doc Page 16 of 128

17 Table 6: IN SLOT Element Type: Functionality Element Name: IN SLOT Controlled by Standard? Requirement ID Traceability: 5.1.6, 5.1.8, 5.3.7, 5.3.8, 5.3.5, Electrical: Yes 5.5.5, 5.3.2, 5.3.3, 5.3.4, , , , , Mechanical: Yes 5.1.2, , Description of Responsibility: IN SLOT element is responsible to mechanically house, power and electrically connect field Sensor devices to Input Functionality element Guidance: IN SLOT Functionality houses and electrically connects standard Sensors such as: - NEMA 4-channel inductive loop detectors with (4) outputs and (4) status, without INBUS - Inductive loop detectors without status - Isolators - Preemptors Examples of IN SLOT Functionality include commonly-available detector rack slots and card guides. Table 7: Detector Termination Element Type: Functionality Element Name: Detector Termination Controlled by Standard? Requirement ID Traceability: 5.1.9, , , , Electrical: Yes , Mechanical: No Description of Responsibility: Detector Termination Functionality element is responsible to mechanically and electrically support and connect the input field wires to the Input Functionality element. Guidance: Detector Termination Functionality terminates input field wires, such as inductive loops, pedestrian pushbuttons and inputs from field sensors. Detector Termination Functionality is of value to organize various legacy field wire and cabinet configurations using the NEC wire sizing, ampacity and safety requirements. Also known as a field termination panel. Table 8: Output Element Type: Functionality Controlled by Standard? Electrical: Yes Mechanical: No Element Name: Output Requirement ID Traceability: 5.1.7, 5.1.8, 5.4.2, 5.4.8, , , , , , , , 5.1.2,5.1.47, , , , , , , , , , , Description of Responsibility: Output Functionality element is responsible to mechanically support, power and electrically connect OUT SLOT(s) to SIU(s). Guidance: Output Functionality supports standard OUT SLOTS that accommodate output control devices such as Load Switches. Table 9: OUT SLOT Element Type: Functionality Element Name: OUT SLOT Controlled by Standard? Requirement ID Traceability: 5.1.7, 5.1.8, 5.4.2, 5.4.8, Electrical: Yes , , , , , , , Mechanical: Yes , 5.1.2, , Description of Responsibility: OUT SLOT element is responsible to mechanically house, power and electrically connect field output control devices to the Output Functionality. For precise measurement, a non current-carrying sense wire connects to the output field wire termination. That way, the actual field wire voltage is reported instead of the output voltage at the load switch. Guidance: Output Functionality houses standard control outputs such as Dual HV Load Switches and Dual LV Load Switches ITSCabStdHLD_0202_ doc Page 17 of 128

18 Table 10: Output Termination Element Type: Functionality Element Name: Output Termination Controlled by Standard? Requirement ID Traceability: 5.1.9, 5.6.3, 5.1.2, , Electrical: Yes , , , Mechanical: No Description of Responsibility: Output Termination Functionality element is responsible to: - Mechanically and electrically connect input field wires to Input Functionality element. - Mechanically and electrically program the flash operation to RED, YELLOW or NONE. - Transfer Load Switch power from Signal Power to Flash Power during fault conditions. Guidance: Also known as a field termination panel. Output Termination Functionality terminates input field wires, such as inductive loops, pedestrian pushbuttons and inputs from field sensors. Detector Interface Functionality is of value to organize various legacy field wire and cabinet configurations using the NEC wire sizing, ampacity and safety requirements. Also provides a sense wire from each field wire to the Output Functionality to measure the output field wire voltage. Table 11: Service, High Voltage Version Element Type: Functionality Element Name: Service, High Voltage Version Controlled by Standard? Requirement ID Traceability: , , 5.9.7, , Electrical: Yes , , , , , , Mechanical: No Description of Responsibility: Service Functionality element is responsible to mechanically and electrically connect the electrical service entrance to the Power Functionality. Service Functionality includes Utility Termination Blocks, the Main Breakers, the GFCI Breakers, Transient Suppressors, RFI Filter and GFCI Receptacle. Guidance: Service, High Voltage Version Functionality converts raw service power to clean service power and protects against overloads and short circuit conditions. Table 12: Service, Low Voltage Version Element Type: Functionality Element Name: Service, Low Voltage Version Controlled by Standard? Requirement ID Traceability: , , 5.9.7, , Electrical: Yes 5.1.2, , , , , , , , Mechanical: No , , , Description of Responsibility: Service Functionality element is responsible to mechanically and electrically connect the electrical service entrance to the Power Functionality. Service Functionality includes Utility Termination Blocks, the Main Breakers, Transient Suppressors and RFI Filter. Guidance: Service, Low Voltage Version Functionality converts raw service power to clean service power and protects against overloads and short circuit conditions. Table 13: Power, High Voltage Version Element Type: Functionality Controlled by Standard? Electrical: Yes Mechanical: No Element Name: Power, High Voltage Version Requirement ID Traceability: , , , , , , , , , , , , 5.1.2, , , , , , , , , , , , Description of Responsibility: Power Functionality element is responsible to mechanically and electrically convert service power from the Service Functionality into Signal Power, 24 VDC and Flash Power. Power Functionality includes the 24 VDC Power Supply, Flasher and Clean AC Receptacle. ITSCabStdHLD_0202_ doc Page 18 of 128

19 Guidance: Includes Dual High Voltage Flasher so that major elements can be interchanged while in flash Table 14: Power, Low Voltage Version Element Type: Functionalty Controlled by Standard? Electrical: Yes Mechanical: No Element Name: Power, Low Voltage Version Requirement ID Traceability: , , , , , , , , , , , , 5.1.2, , , , , , , , , , , , , Description of Responsibility: Power Functionality element is responsible to mechanically and electrically convert service power from the Service Functionality into Signal Power, 24 VDC and Flash Power. Power Functionality includes the 24 VDC Power Supply, and Flasher. Guidance: Includes Dual Low Voltage Flasher so that major elements can be interchanged while in flash Table 15: Monitor Element Type: Functionality Element Name: Monitor Controlled by Standard? Requirement ID Traceability: , , , , Electrical: Yes , 5.7.3, 5.7.2, , , , Error! Mechanical: No Reference source not found., , 5.1.2, 5.1.5, Description of Responsibility: Monitor Functionality element is responsible to mechanically house, power and connect the CMU to: - Output Functionality via SB3 - CU via SB1 - ADU via SB3 using EIA-485 standard Guidance: Physical home for the CMU Table 16: Auxiliary Display Unit Element Type: Functionality Element Name: Auxiliary Display Unit Controlled by Standard? Requirement ID Traceability: , 5.7.3, , 5.1.2, Electrical: Yes , , , , Mechanical: No Description of Responsibility: ADU Functionality element is responsible to mechanically house, power and electrically connect the Monitor Functionality to a display device via SB3 that visually indicates monitoring status conditions. Guidance: Supplements the CMU indicators, including at the least all of the information available on the NEMA Malfunction Management Unit. Table 17: Door Switch Element Type: Functionality Element Name: Door Switch Controlled by Standard? Requirement ID Traceability: , Electrical: Yes Mechanical: No Description of Responsibility: Door Switch Functionality element is responsible to mechanically and electrically connect the Monitor Functionality to the door switch Guidance: CMU monitors the door switch ITSCabStdHLD_0202_ doc Page 19 of 128

20 Table 18: Fan and Thermostat Element Type: Functionality Element Name: Fan and Thermostat Controlled by Standard? Requirement ID Traceability: , , , Electrical: Yes 5.1.2, , , , , Mechanical: No Description of Responsibility: Fan and Thermostat Functionality element is responsible to maintain cabinet air temperature below the upper safe operating range. Guidance: Work in combination Subassembly Elements Table 19: Input Sensor Element Type: Subassembly Element Name: Sensor Controlled by Standard? Requirement ID Traceability: 5.5.5, 5.3.2, 5.3.3, , Electrical: Yes , , , , Mechanical: Yes Description of Responsibility: Sensor Assembly is an interchangeable plug-in device responsible for sensing conditions and representing the conditions to the SIU via the SIU IN interface. Guidance: Sensors conform to NEMA TS 2 Section (see Figure 6-5) for Mechanical dimensions, connector and connector pin assignments of standard input sensors such as: - NEMA 4-channel inductive loop detectors with (4) outputs and (4) status, without IN BUS - Inductive loop detectors without status - Isolators - Preemptors Table 20: Serial Interface Unit Element Type: Subassembly Element Name: Serial Interface Unit Controlled by Standard? Requirement ID Traceability: , , , , Electrical: Yes , , , , , , , Mechanical: Yes , , , Description of Responsibility: SIU Assembly is an interchangeable plug-in device responsible for: - Reading the status of Sensors via SB1 - Controlling the state of Load Switches via SB1 Guidance: Mechanical dimensions, connector and connector pin assignments of the slot are controlled by the standard. The SIU is carried forward from the V1 standard to this standard, including the number used and the addressing The mapping of the IN SLOT connectors to the SIU assembly connector is controlled by the standard as a default mapping. The mapping of the SIU subassembly connector signals to the SB1 messages is fixed and carried forward from existing SIU mapping. The traffic signal control application is responsible to provide different mapping. Table 21: Dual HV Load Switch Element Type: Subassembly Controlled by Standard? Electrical: Yes Mechanical: Yes Element Name: Dual HV Load Switch Requirement ID Traceability: , 5.4.2, , , , , , , , ITSCabStdHLD_0202_ doc Page 20 of 128

21 Description of Responsibility: Dual HV Load Switch Assembly is an interchangeable plug-in device responsible for: - Controlling two phases of three output loads operating on 120 VAC - Reporting output field wire voltage to CMU via SB3 - Reporting output field wire current to CMU via SB3 Guidance: Mechanical dimensions, connector and connector pin assignments of the slot and the Dual HV Load Switch are controlled by the standard. Table 22: Dual LV Load Switch Element Type: Subassembly Element Name: Dual LV Load Switch Controlled by Standard? Requirement ID Traceability: , 5.4.2, , 5.4.4, Electrical: Yes , , , , , , Mechanical: Yes Description of Responsibility: Dual LV Load Switch Assembly is an interchangeable plug-in device responsible for: - Controlling two phases of three output loads operating on 48 VDC - Reporting output field wire voltage to CMU via SB3 - Reporting output field wire current to CMU via SB3 Guidance: Mechanical dimensions, connector and connector pin assignments of the slot and the Dual LV Load Switch are controlled by the standard. Table 23: Dual HV Flasher Element Type: Subassembly Element Name: Dual HV Flasher Controlled by Standard? Requirement ID Traceability: , 5.9.7, , , Electrical: Yes , , , , , , Mechanical: Yes Description of Responsibility: Dual HV Flasher Assembly is an interchangeable plug-in device responsible for providing 120 VAC flash power to the Output Functionality Guidance: Mechanical dimensions, connector and connector pin assignments of the slot and the Dual HV Flasher are controlled by the standard. Table 24: Dual LV Flasher Element Type: Subassembly Element Name: Dual LV Flasher Controlled by Standard? Requirement ID Traceability: , , , Electrical: Yes , , , , , , Mechanical: Yes Description of Responsibility: Dual LV Flasher Assembly is an interchangeable plug-in device responsible for providing 48 VDC flash power to the Output Functionality Guidance: Mechanical dimensions, connector and connector pin assignments of the slot and the Dual LV Flasher are controlled by the standard. ITSCabStdHLD_0202_ doc Page 21 of 128

22 Table 25: Cabinet Monitor Unit Element Type: Subassembly Controlled by Standard? Electrical: Yes Mechanical: Yes Element Name: Cabinet Monitor Unit Requirement ID Traceability: , , , , , , 5.7.3, , 5.7.2, , , , Error! Reference source not found., , , , Description of Responsibility: CMU Assembly is an interchangeable plug-in device responsible for identifying and responding to predefined malfunctions by: - Measuring and evaluating load switch field wire voltages - Measuring and evaluating field wire currents - Measuring and evaluating voltages on interfaces between elements - Controlling the transfer of load switches from signal power to flash power - Indicating status - Logging malfunction events - Communicating malfunction events and status Guidance: Such as conflicting greens, broken field wires and red fails. CMU for high voltage version is carried forwards unchanged from V1 standard to this standard. CMU for low voltage version is identical to High Voltage version except compliance range of voltage and current measurements that are scaled to LV Load Switches and to the other sensors, such as door switch. Number of CMUs and addressing is carried forward from V1 standard into this standard. Table 26: GFCI Receptacle Element Type: Subassembly Element Name: GFCI Receptacle Controlled by Standard? Requirement ID Traceability: , Electrical: Yes Mechanical: Yes Description of Responsibility: GFCI Assembly is responsible for measuring current on LINE and NEUTRAL to detect unintended current paths to earth ground presenting shock hazards. If a current imbalance is detected, power is immediately interrupted to avoid shock hazard. Guidance: Includes receptacle providing raw 120 VAC power for auxillary use. Table 27: Clean AC Receptacle Element Type: Subassembly Element Name: Clean AC Receptacle Controlled by Standard? Requirement ID Traceability: , , Electrical: Yes Mechanical: Yes Description of Responsibility: Clean AC Receptacle Assembly is responsible for supplying 120 VAC power that has been filtered and removed of electrical transients. Guidance: Typically used to power critical electronic devices such as the CU that requires filtering to remove conducted noise from the raw power service and to remove conducted noise created by devices powered by the raw power fed from the GFCI. ITSCabStdHLD_0202_ doc Page 22 of 128

23 5.2.2 Interface Elements Table 28: SB1/SB2 Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: Yes Signal Names: Yes Protocol: SB1: Yes SB2: No Element Name: SB1/SB2 Requirement ID Traceability: , , , , , , , , , 5.3.8, 5.1.5, 5.2.4, Description of Responsibility: SB1: Command / Response connection among CU, CMU and SIU(s), operating as: - CU commands SIU(s) to respond with input states - CU commands SIU(s) to set output states, SIU(s) respond with acknowledgement - CU commands CMU to respond with status, such as faults and field check of outputs SB2: Communicates among CU and Input Device Subassemblies, per V1, Guidance: SB1/SB2 Interface is retained in its entirety from V1 in order to provide compatibility with ATC 5201 CUs and software applications running on ATC 5201 CUs. Connector: ATC 5201, C12S Pin Assignments: ATC 5201, C12S Signal Names: ATC 5201, C12S Electrical: ATC 5201, C12S Protocol: SB1: ATC 5201, SP5 SB2: Not controlled by standard Table 29: SB3 Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: Yes Signal Names: Yes Protocol: Yes Description of Responsibility: Element Name: SB3 Requirement ID Traceability: , , , , , , 5.7.3, 5.7.2, Command / Response connection among CMU, ADU and AMU(s), operating as: - CMU commands AMU(s) to respond with output field wire voltages - CMU commands AMU(s) to respond with output field wire currents Guidance: SB3 Interface is retained in its entirety from V1 in order to provide compatibility with V1 CMUs and CMU configuration tools. ITSCabStdHLD_0202_ doc Page 23 of 128

24 Connector: V1, SB3 Pin Assignments: V1, SB3 Signal Names: V1, SB3 Electrical: V1, SB3 Protocol: V1, SB3 Table 30: SIU IN Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: No Signal Names: Yes Protocol: Yes Description of Responsibility: Element Name: SIU IN Requirement ID Traceability: 5.1.6, 5.1.8, 5.3.7, 5.3.5, 5.5.5, 5.3.2, 5.3.3, 5.3.4, , , , The SIU IN Interface connects the IN SLOT functionality to SIU subassembly. Guidance: Input to SIU Interface is used by the SIU to sense the Input Device signals: - Inductive Loop Detector outputs - Inductive Loop Detector status - Isolator outputs - Preemptor outputs The mapping of the IN SLOT connectors to the SIU assembly connector is controlled by the standard as a default mapping. The traffic signal control application is responsible to provide different mapping. Connector: - SIU: V1, Input Device: NEMA TS 2 Paragraph Pin Assignments: - SIU: V1, Input Device: NEMA TS 2 Paragraph Signal Names: - SIU: V1, Input Device: NEMA TS 2 Paragraph Electrical: V1, 4.7 Protocol: V1, 4.7 ITSCabStdHLD_0202_ doc Page 24 of 128

25 Table 31: SIU OUT Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: No Signal Names: Yes Protocol: Yes Description of Responsibility: Element Name: SIU OUT Requirement ID Traceability: 5.1.7, 5.1.8; 5.4.2, , , , , Connects SIU to Output devices Guidance: SIU to Output Interface is used by the SIU to control Output Device signals: - High Voltage Load Switches - Low Voltage Load Switches Connector: - SIU: V1, Output Device: Dual Load Switch connector of this standard Pin Assignments: V1, Pin Assignments: - SIU: V1, Output Device: Dual Load Switch connector of this standard Electrical: V1, 4.7 Protocol: V1, 4.7 Table 32: CDC Option Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: Yes Signal Names: Yes Protocol: Yes Description of Responsibility: Element Name: CDC Option Requirement ID Traceability: CDC is responsible to connection SIU Opto Inputs to external devices. Inclusion of CDC is optional, but controlled by standard if supplied. Guidance: Typically used to sense pedestrian inputs Connector: V1, Pin Assignments: V1, Signal Names: V1, Electrical: V1, Protocol: V1, ITSCabStdHLD_0202_ doc Page 25 of 128

26 Table 33: CC Element Type: Interface Controlled by Standard? Electrical: Yes Mechanical: Yes Signal Names: Yes Protocol: Yes Description of Responsibility: Element Name: CC Requirement ID Traceability: 5.3.2, , CC is responsible to sense cabinet devices by the CMU, per V Guidance: Typically used to sense the door switch and police panel switches Connector: V1, Pin Assignments: V1, Signal Names: V1, Electrical: V1, Protocol: V1, ITSCabStdHLD_0202_ doc Page 26 of 128

27 5.3 Requirements Table 34: REQID Patents and Copyrights Patents and Copyrights Interfaces that are patented or copyrighted shall not be included as part of the TFCS 1. The user needs the TFCS to be specified as an open architecture system, 1. UN ID (Comments/Changes) Guidance: 2 Is the requirement well-formed? 3 Is the requirement unambiguous? 4 Is the requirement feasible? 5 Is the requirement verifiable? 6 If verifiable, by which method? section above. ITSCabStdHLD_0202_ doc Page 27 of 128

28 Table 35: REQID Commonly-Available Components 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. 1. The user needs the TFCS to be specified as an open architecture system 1. UN ID (Comments/Changes) Guidance: After discussion, includes purchased parts available from distributors and fabricated parts available from the manufacturer, such as custom sheet metal or electronic subassemblies. 2 Is the requirement well-formed? 3 Is the requirement unambiguous? 4 Is the requirement feasible? 5 Is the requirement verifiable? 6 If verifiable, by which method? section above. ITSCabStdHLD_0202_ doc Page 28 of 128

29 Table 36: REQID Rack Mountable Rack Mountable The TFCS subsystems and assemblies shall be suitable for mounting in a 19 inch rack 1. The user needs the TFCS to be specified with a modular internal structure. 1. UN ID (Comments/Changes) 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 2 Is the requirement well-formed? 3 Is the requirement unambiguous? 4 Is the requirement feasible? 5 Is the requirement verifiable? 6 If verifiable, by which method? section above. ITSCabStdHLD_0202_ doc Page 29 of 128

30 Table 37: REQID Utilizes a Controller Subsystem 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 1. The user needs the TFCS to be specified with a modular internal structure. 2. The user needs the TFCS to be scalable. 3. The user needs the TFCS to be expandable. 4. 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. 5. The user needs the TFCS to have an application computer that supports the cabinet interfaces defined in this standard. 6. The user needs the TFCS to provide uniform internal interfaces and protocols. 7. The user needs the TFCS to have a non-volatile method of maintaining the system reports and logs. 1. UN ID UN ID UN ID UN ID UN ID UN ID UN ID (Comments/Changes) Guidance: Scalable means deployable for a range of applications. Expandable means can add capacity later. 2 Is the requirement well-formed? 3 Is the requirement unambiguous? 4 Is the requirement feasible? 5 Is the requirement verifiable? 6 If verifiable, by which method? Note: An answer of no requires a comment or change in the Comments/Change field ITSCabStdHLD_0202_ doc Page 30 of 128