{"text_format":"2","workbook":"xls","n_sheets":2,"sheets":["ATC ITSCabv2 Draft Inputs","Instructions"],"not_rendered":{"charts":0,"images":1,"macros":0,"external_links":1,"defined_names":3,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"ATC ITSCabv2 Draft Inputs","index":0,"n_rows":61,"n_cols":11,"rows_kept":61,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["#","O/C","CoOrg/\nIndiv Inits","Edit/ Subst","DocID ver#","Sec","Para Table Fig","Existing Text","Proposed Text","Reason/ Explanation","WGResponse"]
[1,"O","MnDOT",null,"ITS CabinetV2 StdHLD v01.2","6 Page 28","Figure 2","Figure 2 needs to be broken up into 2A and 2B","There needs to be a block diagram for 120 VAC version and a 48 VDC version of the cabinet.","How exactly the 48 VDC version of the cabinet would look like exactly is undefined to date. ","Agree, a second low voltage diagram will be added, consistent naming."]
[2,"O","MnDOT",null,"\"       \"","6 Page 28","Figure 2",null,"An option for fused load switch outputs needs to be added.","MnDOT had requested this during the original project.","Consider as localized option, further discussion required"]
[3,"O","MnDOT",null,"\"       \"","6 Page 31","Table 12",null,"It is not clear how the 48 VDC cabinet fits into this table","At a minimum 48VDC needs to be run to the output assembly. LED field indications are going to be 48VDC I believe.","Agree, need 48 V in low voltage version"]
[4,"O","Econolite","S","ITSCabStdHLD_0102_151104v01.02",6.2," ","Add the following text after the first paragraph","This standard defines three classes of interchangeability:\n-Class A:\n1. Class A component interchangeability is at the subassembly level. All of the currently defined subassemblies i.e. SIU, HDSP, Detector, CMU, ADU, FTR, AC line transient suppressor etc. shall be fully interchangable between manufacturers, however, the major assembly that the subassemblies are installed into, and their interfaces, do NOT need to be interchangeable between manufacturers.\n\n2. The interfaces to the Class A, major assemblies, that these sub assemblies are installed in, must be fully documented, i.e. open source, and availble to the agency purchasing the assembly. Documentation for a Class A major assembly must include all: connector part numbers, pin-outs, and electrical signal levels used by the external interfaces of the assembly.\n\n-The goal of Class A is to give manufactures the flexibility to create new / different Class A assemblies that are capable of meeting the evolving needs of the industry while maintaining interchangeablity of the cabinet components that historically have the highest failure rate. By requiring that the manufactures make the details of their external\ninterfaces public, any agency or other manufacture will be able to fabricate adaptor cables / assemblies that can lead to full interchangeability.\n\n-Class B: Class B component interchangeability is at the major assembly level. Input, output, field termination and power assemblies shall be fully interchangeable, at the connector level, where used, including connector type and signal levels. The physical dimensions of the assemblies and connector locations are NOT defined.\n\n-Class C: Class C component interchangeability is at the major assembly level. Input, output, field termination and power assemblies shall be fully interchangeable, at the connector level including connector type and signal levels. The physical dimensions of the assemblies and connector locations are ARE defined.","Interchangeability is a primary user need. However, agencies have differing defintions of what interchangeability means. 33X users are used to major assembly interchangeability whereas NEMA users are accustomed to subassembly interchangeability. We need to develop a standard that provides both user bases with the level of interchangeability they require without overly constraining manufacturers efforts to develop, and bring, new innovative products to the marketplace. \n \nDefining classes of interchangeability will allow agencies to specify the level of interchangeability they require while allowing manufactures to create products that meet the functional requirements of the standard, but may be physically different, yet are still conformant to the standard.\n\nBoth Class B and Class C interchangeability will require significant cooperation between the various manufacturers in order to determine which architecture will be selected for each assembly, and its interconnections, since each manufacturer has taken a different architectual / connectorisation approach.","WG agrees in principal,  Econolite will take the lead to provide high level block diagram showing assembies and interface tables, the other manufactures to provide the same information for review by the WG."]
[5,"O","Econolite","S","v01.02","6.2.1 - 6.2.4",null,"New Major Assemblies, Interfaces and Components","Comments","Throughout this section, the term Assembly is used which denotes a physical piece of equipment. The word \"Assembly\" should be replaced with \"System Requirements\" as we begin this effort to create the standard. \n\nThe power distribution architecture defined in this document, though functionally equivalent, is physically different from the architecture used by Econolite in many ways making it difficult to comment without rewriting the whole section to reflect Econolite's design. The primary issues, similar to where we were when the committee lost funding, is what functions reside in what assemblies.","Agree, replace \"assembly\" with \"functional subsystem requirements\""]
[6,"O","Econolite","S","v01.02","6.2.1",null,"The Service Assembly receives raw electric power from the Service Entrance and distributes conditioned electric power to the major assemblies within the V2 cabinet plus Flasher Power [TF7]. The Service Assmbly does not include the CMU [TR32].","The Service Assembly receives raw AC power from the  power utility, backup generator or other source  and distributes conditioned AC power to the major assemblies within the V2 cabinet plus Flasher Power [TF7]. The Service Assmbly does not include the CMU [TR32].","The service assembly should perform AC functions only, similar to the ITS-V1, TS 2 and TEES service assemblies. It should include the AC Main breaker, transient suppressor / filter, GFI outlet and GFI 15A breaker. Additional clean outlet(s) should also be provided in this assembly. It should be located low in the cabinet close to the utility power entry point of the cabinet.\n\nThe Power Supply Assembly should be a separate assembly that accepts clean power from the service assembly and includes any AC to DC conversion and the flasher.\n\nWith the design described in Table 9, if DC signal heads are used, 48VDC needs to enter into the cabinet at the same point as the 120VAC entry point. This would require that either the utility company supply the DC power or an AC to DC power supply would need to be provided at this point that includes its own main breaker and transient suppressor / filter.  Additionally, if 48VDC signal heads are used and the cabinet is running on AC, then, AC needs to be routed to an AC to DC converter and the 48VDC would need to be routed back to this assembly to power the Flasher. This does not lead to a clean implementation.","Will review after reviewing each architecture"]
[7,"O","Econolite","S","v01.02","6.2.1",9,"   V2LV: 48 VDC+ LINE [TR1] [TR30] [TR31] ","Remove all references to V2LV from this table (multiple locations.)\nRemove all references to the flasher from this table.\nChange Raw SRV to GFI Outlet\nRemove Clean, Flash, and Output Breakers from this table.","This should not be the entry point for DC power.\nThe flasher should be located in The PDA (or other location)\nThe GFI outlet is used for power tools.\n","Will review after reviewing each architecture"]
[8,"O","Econolite","S","v01.02","6.2.2",null,null,"Remove section 6.2.2","Remove the requirement for a clean service power assembly. The service assembly includes clean power outlet(s). The user can install COTS power strips in the cabinet as required.","Will review after reviewing each architecture"]
[9,"O","Econolite","S","v01.02","6.2.3",null,"The Power Supply assembly converts clean electric power from the Service Assembly to +12 and +24 volt power referenced to DCGND2.  ","The Power Supply assembly shall convert clean AC power from the Service Assembly to  +24VDC,  and +48VDC. +24VDC shall be used to powerl cabinet sub assemblies, +48VDC shall be used to power the flash transfer relay coils and optionally used to power +48vdc signal heads. This assembly shall include the Flasher and Flasher output over current protection.\n(Adjust table to meet this requirement.)","All currently defined assemblies and subassemblies can run on +24VDC. There is no need for a separate +12VDC supply since +12VDC can be efficiently derived from +24VDC, locally, by any device that may need it.","General agreement, but will require vote by quorum"]
[10,"O","Econolite","S","v01.02","6.2.4",null,"The DC Power assembly receives +12 VDC and +24 VDC from the Power Supply and provides standard receptacles used to power internal cabinet assemblies. RD [4] includes a combination Communications Bus / DC Power assembly that can be used.  A smaller size DC Power assembly is included for the smaller 303 cabinet","Remove this section.","A separate assembly is not required to route power throughout the cabinet. As an alternative, harnesses from the power supply to the other assemblies can be used eliminating the need for another expensive assembly.\n\nA communications bus assembly is not required. Econolite uses provides an IN and Through connector, wired in parallel, on each assembly allowing the user to \"daisy chain\" the SB1/SB2 SDLC bus between assemblies. This implementation more accurately reflects a proper implementation of an EIA-485 multi-drop network.","No requirement for power strips or communications assembly, only requiremens for distributing power and communications"]
[11,"O","Econolite","S","v01.02","6.2.5",null,"The Facility assembly provides a cabinet Light, Door Switch and Fan.  RD [4] includes Facilities that can be used for V2HV version.  Facility assembly for V2LV requires new 48 VDC Fan and Light to meet User Needs. [TR1] [TR30] [TR31]","The Facilities shall provide cabinet Lighting, Door Switch(es), Fan(s) and fan control. Facility components shall operate from +24VDC or +48VDC.","Since we are keep the cabinet at SELV levels, it makes no sense to run 120VAC to the door switches, fans and lighting. 24 or 48VDC versions of these are readily available. ","Agree, low voltage version has no 120V.  Low voltage versions operate on the low service voltage without 120 VAC"]
[12,"O","Econolite","S","v01.02","6.2.6",null,"The Controller assembly is described in RDs [2] and [10] for the V2HV version. Controller assembly for V2LV requires a 48 VDC Controller power supply. [TR1] [TR30] [TR31] that can include either a 48VDC power supply or a DC to AC inverter installed internal to the controller [TR154].  Controller Assembly can run multiple software applications beyond traffic signal control and field display devices.  [TR108] [TR109] [TR110] [TR111] [TR112] [TR117]","The Controller assembly is described in RDs [2] and [10] for the V2HV version. Controller assembly for V2LV shall be capable of operation from the 24VDC cabinet power supply. Controller Assembly can run multiple software applications beyond traffic signal control and field display devices.  [TR108] [TR109] [TR110] [TR111] [TR112] [TR117]\n\nRemove the +24VDC output requirement.\nRemove the +12VDC ISO output requirement","24VDC is provided by the PDA.\n12VDC ISO and DC GND2, Artifacts from the 2070-2E, are not used in the ATCC","Table 14 states 12 VDC iso, remove references to 12 VDC iso.  Requires quorum votes"]
[13,"O","Econolite","S","v01.02","6.2.7",null,"RD [4] includes a combination Communications Bus / DC Power assembly that can be used.  A smaller size Communications Bus is included for the smaller 303 cabinet","RD [4] includes a combination Communications Bus / DC Power assembly that can be used.  A smaller size Communications Bus is included for the smaller 303 cabinet. Optionally, each assembly, requiring an SB1/SB2 interface, shall provide an IN and THROUGH connector, wired in parallel, to allow the user to \"daisy chain\" the SB1/SB2 SDLC bus between assemblies.","A communications bus assembly is not required. Econolite uses provides an IN and Through connector, wired in parallel, on each assembly allowing the user to \"daisy chain\" the SB1/SB2 SDLC bus between assemblies. This implementation more accurately reflects a proper implementation of an EIA-485 multi-drop network.","No requirement for power strips or communications assembly, only requiremens for distributing power and communications"]
[14,"O","MnDOT",null,"\"       \"","6.2.8 Page 33","Table 16","line 1. two loops per FT connector","four loops per FT connector","Previous work had included high density loop detectors. This would require a new edge connector to accommodate the addition of two additional loops in a single slot in the detector rack ( Input Assembly)","Table until Peter is on line"]
[15,"O","Econolite","S","v01.02","6.2.8",null,"RD [4] anticpates the use of NEMA-Style detectors that provide detector CALL plus detector STATUS [TF15] as described in RD [5].  To meet the User Needs for NEMA-style detectors, a 48 Channel NEMA Input Assembly is added here, with double the density of the ITS Input Assembly. [TR73]  The interfaces are retained for use in an ITS V1 cabinet [TR95] [TR3] [TR4] [TR34] [TR95] [TR100] [TR104] [TR113] [TR114] [TR115] [TR116]","RD [4] anticpates the use of NEMA-Style detectors that provide detector CALL plus detector STATUS [TF15] as described in RD [5].  To meet the User Needs for NEMA-style detectors, a 48 Channel NEMA Input Assembly is added here, with double the density of the ITS Input Assembly. [TR73]\n\n ","Remove the requirement for backward compatibility of the interfaces to ITS V1. One of the primary reasons for lack of mass adoption of the ITS V1 standard was the cost of the cabinet. Requireing 24, pluggable, euro connectors on the back of the input assembly is very costly and provides no real value at this location in the cabinet. A more valuable location for this type of connector might be at the detector field wire termination panel.  Alternate, lower cost connectorization schemes between the input assembly and the field wire termination panel should be allowed.","Will review after reviewing each architecture"]
[16,"O","Econolite","S","v01.02","6.2.8","16:48:00","Address programming block with wire links used to set the SIU address","Address programming  points used to set the SIU address","The use of the euro-style connector to set the address is a very costly solution to the simple requirement to set the rack address and provides the taxpayer with no value. Use of standard headers and shunts should be allowed since the address is \"never\" changed once the rack is installed.","Agree, requires quorum vote"]
[17,"O","Econolite","S","v01.02","6.2.8",16,"Senses the detector CALL output to the SIU input, one Test Port per each SIU","Remove this requirement or make the test port optional.",null,"Agree, should be optional.  Add guidance as to its use."]
[18,"O","MnDOT",null,"\"       \"","6.2.9 Page 33","Paragraph 1","States only 16 phases. ","This cabinet needs to be expandable to 32 phases.","This was talked about in the previous work done. With the advent of FYA in some cases 16 phases is just enough at the present time.","Table until Peter is on line"]
[19,"O","Econolite","S","v01.02","6.2.9",null,"The 16 Phase Output Assembly receives commands from the Controller via SB1 to control sixteen signal phases, including measurement of signal voltage and current [TR8], as well as monitoring to detect undesirable operation.  The 16 Phase Output assembly occupies less space that the ITS 6 phase Output assembly.  [TR73] The interfaces are retained for use in an ITS V1 cabinet [TR96]","The 16 Phase Output Assembly receives commands from the Controller via SB1 to control sixteen signal phases, including measurement of signal voltage and current [TR8], as well as monitoring to detect undesirable operation.  The 16 Phase Output assembly occupies less space that the ITS 6 phase Output assembly.  [TR73]","Remove the requirement for backward compatibility of the interfaces to ITS V1. One of the primary reasons for lack of mass adoption of the ITS V1 standard was the cost of the cabinet. Requireing 16, pluggable, euro connectors on the back of the output assembly is very costly and provides no real value at this location in the cabinet. A more valuable location for this type of connector might be at the output field wire termination panel.  Alternate, lower cost connectorization schemes between the input assembly and the field wire termination panel should be allowed.","Will review after reviewing each architecture"]
[20,"O","Econolite","S","v01.02","6.2.9",17,"SIU address, 0 to 15 binary encoded, one address input per each of the two SIUs","SIU address, 0 to 1 binary encoded, ","This standard only supports 2, 16-channel output assemblies. The address selection can be accomplished with a simple two position header/shunt. The use of the euro-style connector to set the address is a very costly solution to the simple requirement to set the rack address and provides the taxpayer with no value. Use of standard headers and shunts should be allowed since the address is \"never\" changed once the rack is installed.","Agree, requires quorum vote"]
[21,"O","Econolite","S","v01.02","6.2.9",17,"Power from Power Distribution Assembly phases 1-4\nPower from Power Distribution phases 5-8\nPower from Power Distribution phases 9-12\nPower from Power Distribution phases 13-16","Power from Power Distribution Assembly","Due to the low power required by present day signal heads, all AC or DC power for a 16-channel output assembly can be supplied through a single circuit.","Will review after reviewing each architecture"]
[22,"O","Econolite","S","v01.02","6.2.9",17,"Serial Interface Unit, up to two per assembly","Serial Interface Unit, one per 16 output channels.",null,"Only 1 SIU, fix that line to match"]
[23,"O","Econolite","S","v01.02","6.2.9",17,null,"Add Main Contactor to components list.",null,"Standard does not control the mechanical location"]
[24,"O","Econolite","S","v01.02","6.2.9",17,"Test Port","Make the Test Port optional.",null,"Agree, should be optional.  Add guidance as to its use"]
[25,"O","Econolite","S","v01.02","6.2.9",17,"CMU","Make the Ethernet port optional",null,"Ethernet was stated from prior WG meeting.  Retain"]
[26,"O","Econolite","S","v01.02","6.2.10",null,"Because the 2-channel load switches include short circuit protection with automatic recovery, the use of PDA 16 is optional.","Remove section 6.2.10","Over current protection should be provided in the Power Supply Assembly and / or the Output Assembly.","Will review after reviewing each architecture.   Reconsider signal power distribution and breakers"]
[27,"O","Econolite","S","v01.02","6.2.11",null,"The Police Panel Assembly consists of four switches connected through the CDC connector to the four optically-isolated inputs of the first Output SIU.","The Police Panel Assembly consists of four switches connected through the CDC or CC connectors to the four optically-isolated inputs of the first Output SIU.","The CDC and CC connectors have some functional overlap. The CC connector also includes the front and rear door switch and signals off circuits. Using only CC is preferable. CDC should be optional.","Will review after reviewing each architecture"]
[28,"O","Econolite","S","v01.02","6.2.11",19,null,"Fix table","The wrong information is shown in the outputs section.","Agree, fix table"]
[29,"O","Econolite","S","v01.02","6.2.11",null,"The 16 Phase Field Termination Assembly selectively connects the field wires to either the 16-Phase Output Assembly or the Flasher of the Service Assembly, based on the state of the FS contact.  In addition, 16 Flash Programming Blocks are provided to individually program each Failed State output to RED Flash, Yellow Flash or No Flash.","The 16 Phase Field Termination Assembly selectively connects the field wires to either the 16-Phase Output Assembly or the Flasher of the Service Assembly, based on the state of the FS relay and Flash Transfer Relay contacts.  In addition, 16 Flash Programming Blocks are provided to individually program each Failed State output to RED Flash, Yellow Flash or No Flash.","Just a better description of the flasher operation","Agree, improve wording"]
[30,"O","Econolite","S","v01.02","6.2.11",20,null,"Add to Outputs section of table: CMU Field Sense signals (1-48) plus Flasher Output Sense signals (1-4)","HDSP/CMU field sense circuits should be attached as close to the field wiring connectors as possible.","Agree, add sense wires to table"]
[31,"O","Econolite","S","v01.02",7,null,"NEW AND UPDATED MAJOR ASSEMBLY DETAILS [TR66] [TR69]","Comments on section as a whole.","This section of the HLD appears to be based on one manufacturer's design and contains significant physical detail, down to the component manufacturers and part numbers.  It is inappropriate to use most of this section as the proposed starting point of this standard. There are at least three manufacturers in this working group who offer products that are functionally equivilent yet physically different with relation to what assembly includes which function and, what connectors have been used to interconnect their assemblies. Significant negotiation / voting is required between the members of the working group before a final, \"Class C\"  level of interchangeability can be defined.","Duplicate to #4"]
[32,"O","Econolite","S","v01.02",7.1,null,"1.1     PDA 16 Power Distribution Assembly","See Comments","The technician switches should be located in the output assembly.\n\nOver current protection is provided by the HDSPs. Additional over current protection can be located in the output assembly.\n\nFlash status can be determined by the position of the Auto/Flash switch handle; an LED is not required but should be optional. \n\nThe PDA is not required. All of its functionality is provided by circuitry in other assemblies.","This diagram was taken directly from diagrams in Step 51 from prior WG efforts.  Agree, overcurrent protection is provided by the HDSPs, meaning that additional overcurrent protection may not be needed or located in the output assembly.\n\nFlash status was also taken directly from Step 51.  \n\nWill require WG vote"]
[33,"O","Econolite","S","v01.02","7.1.1",3,"Service Assembly Block Diagram","Revise this drawing","The service assembly should more closely follow the bottom half of figure 5-4 from TS 2. where all AC power is derived after the transient suppression and filtering except the GFI convenience outlet.The Flasher and associated circuitry should be removed from Figure 3. [See Cell to right.]"]
[34,"O","Econolite","S","v01.02","7.1.2 -7.7.3"," ",null,"See comments","These sections are based on one manufacturer's design and must not be included in this document at this time.","Will review after reviewing each architecture"]
[35,"O","MnDOT",null,"\"       \"","7.1.3 Page 38","additional bullet.",null,"Add, All wiring and circuit overload protection shall be in accordance with NFPA 70 National Electrical Code","This was debated at length at the previous meetings and when we can we will reference the NEC requiring listed components and wiring but we would stop short of requiring the cabinet to be listed. This idea needs to be stated in a general section or it needs to be attached to each section as needed.","Tabled until Peter is online"]
[36,"O","MnDOT",null,"\"       \"","7.3.1 Page 41","V2LV block diagram","shows a transformer. DC to DC conversion does not require a transformer.","Redraw the diagram with dc to DC converters. Where does the 48 VDC come from?","The 48 VDC version of this cabinet is shown in places but its not clear and complete thru the document.","Tabled until Peter is online"]
[37,"O","Econolite","S","v01.02","7.8.1",12,"48 Channel NEMA Input Assembly Block Diagram ","See comments","Using 12 individual, pluggable, euro-style connectors, at this location in the cabinet, is not an efficient design. Detector wiring should terminate to lower cost, higher density connectors on the rear of the input assembly.\n\n+12VDC is not needed. Detectors can operation on +24VDC.\n120VAC is needed so that agencies can continue using their legacy preemptor and isolator modules.\n\nTest connector should be optional.","Duplicate to   #9"]
[38,"O","Econolite","S","v01.02",7.9,null,"7.9.1 16 Phase Output Assembly Block Diagram ","See comments","The CDC connector is redundant since the same police panel signals are also available on the CC connector.\n\nThe main contactor should be in this drawing\n\nThe standard only supports 2 16-channel output assemblies. The addressing scheme shown is overkill. Selection of two address only requires a single, 2-position header/shunt.\n\nRequiring 4 circuits for input power is over kill. A typical, 110VAC, 8-phase intersection, with overlaps, 4 indicators for throughs, 2 lefts, 2 peds and 1 overlap per approach and 12W signals  will require: 9 indicators * 12 watts * 4 approaches divided by 110VAC or 3 Amps. A typical medium current connector such as the Molex MLX series is rated for 13 Amps per circuit. Even this low cost solution is somewhat overkill for our power requirements.\n\nSignal power, DC power and the FS signal can all be carried in the same connector/harness\n\nThe load sense wires should be paired with the load switch output wires in the output connectors.\n\nThe \"Technician\" switches should be shown in this drawing.\n\nThe Test connector should be optional","Will review after reviewing each architecture"]
[39,"O","Econolite","S","v01.02","7.12.2",34,"16 Phase Field Termination Assembly Material List","See Comments","Connector part numbers should not be defined at this time.\n\nThe Struthers Dunn relay can be used for both AC and 48VDC configurations\n\nOutput signals and corresponding sense signals should be paired  in the same connector; one connector per HDSP.\n\nField wiring termination, program blocks and FTRs should be on the user-facing side, all other wiring should be located on the rear of the assembly.","Will review after reviewing each architecture"]
[40,"O","MnDOT","S","v01.02","Figure 17 Page 53","PDA",null,"Add, All wiring and circuit overload protection shall be in accordance with NFPA 70 National Electrical Code","See item 7 above.","Duplicate to #35"]
[41,"O","MnDOT","S","v01.02","Figure 17 Page 53",null,"Add circuit breaker short-circuit current ratings to the requirements","All circuit breakers shall have a minimum Short-circuit current rating (SCCR) of 10, 000 Amps.","to be in compliance with NFPA 70E we need to specify this. Its unlikely that the available fault current at the breaker will be in access of 10,000 amps. It is likely that the fault current would be in excess of 4, 000 amps."]
[42,"O","McCain","S","v01.02","6.2.3 Power  Supply Assembly",null,"Does not include 48 volt output ","Add 48 VDC","The power supply assembly should not specify only +12 and +24 volts. 48 volts is used in cabinets to power the FTR coils, door switches and DC fans. One manufacturer currently makes a cabinet power supply that adds a 48 volt output.","Agree, duplicate to #3"]
[43,"O","McCain","S","v01.02","6.2.4 DC Power Assembly",null,null,null,"The DC power assembly or bus system connectors are not compatible with one manufactures DC power connectors.","Will review after reviewing each architecture"]
[44,"O","McCain","S","v01.02","6.2.5 Facility Assembly",null,null,null,"The facility assembly from one manufacturer uses 48VDC for the FTRs and fan in both HV and LV cabinets.","Agree, facility requirements should be based on extra low voltage levels"]
[45,"O","McCain","S","v01.02","6.2.6 Controller Assembly",null,null,null,"Comments received from users suggest the controller will always use AC power so they do not have two different types of controllers in inventory.","Further investigation for interpretation of conformance to arc flash"]
[46,"O","McCain","S","v01.02","6.2.7 Communications Bus Assembly",null,null,null,"One manufacturer uses a combined Comm./DC bus for all types of cabinets.","Will review after reviewing each architecture"]
[47,"O","McCain","S","v01.02","General Note",null,null,null,"General Note: SIU addressing – some of the smaller cabinets do not use an SIU address block when the design allows only one SIU or one input and one output SIU. The addresses are hardwired into the assembly PCB.","Agree, duplicate to #16"]
[48,"O","McCain","S","v01.02","7.1.3 Service Assembly",null,null,null,"The specification should not limit the design of the service assembly or any other assembly to one design. We have already had customers request a rack mount service assembly. It is up to the manufacturers if they want to build what the customer wants.","Will review after reviewing each architecture"]
[49,"O","McCain","S","v01.02","7.4 DC Power Assembly Details",null,null,null,"The DC power bus has evolved dramatically over the years and now has provisions for three voltages, +12, +24 and +48 volts. The SDLC communications bus has also been incorporated into the DC power bus to save space.","Agree, duplicate to 310"]
[50,"O","McCain","S","v01.02","7.8.3 48 Channel NEMA Input Assembly",null,null,null,"Why should the drawing show the two SIUs in these positions? Why can’t the manufacturers place them where they think the design is best? The committee should not produce such detailed drawings with component placement unless it is clearly labeled as a “concept”.","Agree, duplicate to #10, standard does not control the placement"]
[51,"O","McCain","S","v01.02","7.9.3 16 Phase Output Assembly",null,null,null,"Same comments as in 7.8.3","Agree, duplicate to #10 "]
[52,"O","McCain","S","v01.02","General Note",null,null,null,"General Note: The manufacturers have moved well beyond the 2008 ATC V2 spec and as thus, the committee needs to just define the interfaces, mechanical, electrical and messaging protocol only. We don’t need to argue about how it looks or how it is built. The consumers will let us know what works and what doesn’t. This is how the industry has always worked and will continue to work. Those manufacturers that are responsive to the customer’s requirements will generally do well.","Will review after reviewing each architecture"]
[53,"O","USDOT","S","ITSStdRS v01.05","Multiple",null,"There are multiple areas where requirements in the StdRS are identical to Sections of the ITS Cabinet Standard.  As examples Requirement 5.12.2 in StdRS and 3.1.6.1 in Cabinet, 5.12.4 in StdRS and 3.1.6.2 in Cabinet, 5.12.5 in StdRS and 3.1.6.3 in Cabinet, etc.","Duplicative sections should not exist between documents.","Having sections between both documents with exactly the same wording will create a long term configuration management issue, as every time one section changes, the sibling section in the other document will have to change.  If one section were to change and the other were to stay the same then there would be conflicting guidance from two authoritative documents."]
[54,"O","USDOT","S","ITSStdRS v01.05","Multiple",null,"There are multiple sections, all of 5.12 for example, that are listed as requirements put are really high level design elements.  ","Requirements should be describe the desired functionality, in the case of section 5.12, it would be the requirement for a cabinet housing the provides X, Y, Z.  Then the high level design would specify the different ways that is met through aluminum sheet plating, stainless steel sheet, etc.","Requirements need to describe the desired functionality, with the high level design showing how that functionality will be met."]
[55,"O","USDOT","S","ITSStdRS v01.05","RTM","Multiple","In multiple areas there are high level design traces to Note 1 which states: \"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.\"","Need traceability to uniquely identifiable high level design content.","The RTM needs to trace to uniquely identifiable data elements.  This note does not provide the reader of this document with a clear reference to show how the ITS Cabinet design meets these requirements and user needs."]
[56,"O","USDOT","S","ITSStdRS v01.05","RTM User Need 4.3.6.7","Multiple","There are multiple references to Requirement 5.7.2, with each reference having a different element in parenthesis, however these parenthetical references can't be found in the document.","There needs to be explicit, uniquely identifiable references to requirements within the RTM.","It is extremely difficult to determine from the RTM what the requirements are for Cabinet Monitor Unit in this case.  The requirement text only states: \"The TFCS’ Monitor Assembly shall provide for a Cabinet Monitor Unit (CMU) with minimum functionality of ITS Cabinet V1 CMU\""]
[57,"O","USDOT","S","ITSStdRS v01.05","RTM User Need 4.3.6.7","Multiple","The high level design reference for this trace is Figure 2, however it is difficult to find the CMU and the requirement states the CMU is part of the Monitor Assembly, however Figure 2 has the CMU as part of the Output Assembly.","Reference to the high level design elements that satisfy the CMU requirement.","The high level design needs to show how that design will meet the requirements, in this case the CMU, and the CMU is not found in this reference."]
[58,"O","USDOT","S","ITSStdRS v01.05","RTM User Need 4.3.3.1","Multiple","The requirement identified as 5.2.1 actually has seven sub-requirements.  Do all seven apply?","Need to reference all applicable requirements in the RTM to show full traceability.","All requirements need to be referenced in the RTM to show full traceability."]
[null,"O",57,null,null,"Open"]
[null,"C",0,null,null,"Closed"]

{"sheet":"Instructions","index":1,"n_rows":13,"n_cols":2,"rows_kept":13,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Column","Explanation"]
["A","O/C. When submitting your proposed revision, each revision in each row is designated \"O\" for \"Open. \"C\" means \"Closed\", and reflects action taken by the NTCIP WG, when NTCIP WG addresses the proposed revision."]
["B","CoOrg/ Indiv Inits. Use this column to identify: Co/org submitting the proposed revision. Initials of submitter from that Co/Org, or an internal designator (within the Co/Org), such as \"A01\", meaning \"submitted with A group of revisions, this was proposed rev #1.\""]
["C ","Edit/ Subst. Please designate your comments as \"E\", meaning editorial; or \"S\" meaning substantive. If you are proposing a clarification to language (without a significant rev in intent), then the proposed rev is \"E\". If you are proposing a revision from \"should\" to \"shall\", or \"shall\" to \"should\", or inserting a \"shall\", or changing values on characteristic (as examples), then the proposed rev is probably \"S.\" Such designations help me to identify those that I might be able to address and \"SC\" or \"Staff Close\" (subject to NTCIP WG OK)."]
["D","DocID ver#. This entry is the version of a draft NTCIP document against which you are providing the proposed revision. As we move through the project, sometimes section numbers change, and page numbers often change. This helps to locate the proposed rev cite."]
["E","Sec. this requests the specific Section number of draft NTCIP document to which your proposed rev applies. Helps to locate cite within draft (particularly on conference call). If it is in Section 1, then enter \"1\". If it is in Sec. 5.9.3.5.6.4, then enter 5.3.3.5.6.4. NOTE--If you are proposing a change in term (for example) througout the draft, enter GEN (for General). "]
["F","Para Table Fig. In a longer Section, it is helpful to know that the proposed rev is in paragraph 8, for example (enter P8). If it is Figure 2-5, then enter \"F2-5\". If it is Table 3-4, then enter \"T3-4\"."]
["G","Existing Text. Copy and past Existing Text from draft. Use elipses (…), to shorten. "]
["H","Proposed Text. What text are you proposing? How would you like this section to read? This is also known as \"suggested alternatitve language\", meaning that an NTCIP WG will consider this proposal, but may amend in response. It is helpful to actually see the proposed revision, so the NTCIP WG doesn't have to guess, or (itself) craft language."]
["I","Reason/ Explanation. What is the purpose of this proposed revision? Examples might be: Clarity. Typo. Include cross-reference. Add functionality. Revise conformance parameters to reflect current industry practice, and accommodate new functionality. This is your opportunity to be persuasive and argue your technical case (briefly)."]
["J","Response. This column is left blank when you submit your proposed rev. When NTCIP WG considers a proposed rev, the result of that consideration (and the disposition of the proposed rev) is recorded here. Examples include: 10/02 Accepted. Done. Item closed.; Accepted as amended to reflect EN 62543 revision. Not accepted, because NTCIP WG elected to defer inclusion of functionality to next rev. The purpose is to capture the disposition, and, if not accepted, some rationale."]
["OTHER","1. Be brief, you only get 500 words per cell. It may be necessary to split your comment into several rows. Always splilt a comment that applies to different sections, paragraphs, tables, or figures. It is easier for me to consolidate and sequence."]
[null,"2. If you are proposing an extensive revision, for example, adding a whole new section, or revising an extensive existing portion of NEMA TS 4-2005, or revising a figure or table, contact staff, who will provide  the \"native\" text, or figure, or table, to make it easier. Also provide the proposed rev in Excel, with entries such as \"See attached abc NEW Sec 4 FYA.doc ."]