Constructional requirements from ITk-Strips Andy Blue, on behalf of ITK strips community

Contents Breakdown of components for Strips Upgrade Max numbers of parts in the Build What do we want to record? Suggestions Visual Inspection Photos Integration with RFiD & Barcodes Naming Conventions Summary Meeting on ITk production databases

Strip Tracker Components Attempted to contact as many as possible to get outline/ideas for the strip community’s plans for production numbers & database preferences Based on LOI layout 5 layers, stubs, etc. However LOI is “worst case” scenario in terms of no of parts All other cases would see reduction in part numbers List is also incomplete Other necessary components for the build GBT’s, Fibre optics, DCDC/SP boards, HV switches etc. And does not detail 1MHz Readout designs New hybrids, multiplexing chips…. Meeting on ITk production databases

Strip Tracker ‘Parts’ Very simplistic outline for just now Stave/ Petal Cores Tapes Eos Staves/Petal s Sensors ABC ASICs Modules Hybrids HCCs Will work this way Panels Meeting on ITk production databases

Strip Tracker Components From LOI CERN-LHCC-2012-022 ; LHCC-I-023 Meeting on ITk production databases

Strip Tracker Components HCC Multiplexing ASIC Sensor Hybrid LV Powering Board (Liverpool, RAL & BNL) ABC ASIC Barrel Module: Composed of 2 Hybrids and 1 sensor Each Hybrid has 10 x ABC130 readout chips 1 x HCC multiplexing chip 1 x LV Powering board Meeting on ITk production databases

Strip Tracker Components R5 module R4 module R3 module R2 module R1 module R0 module S0 S1 H0 H1 H2 H3 Petal: Composed of 5 different modules with 13 Hybrid variants 7-12 x ABC130 readout chips /Hybrid ~1 x HCC multiplexing chi/Hybrid ~1 x LV Powering board Meeting on ITk production databases

Assumptions Item ‘Pass’ Yields (%) Stave / Petal Mounting 100% + 1% Spare Module Production 95 Hybrid Production ABC ASIC Probing 90 HCC ASIC Probing Sensors I will now go through the estimated numbers for each component in the build Meeting on ITk production databases

Numbers: Barrel No Staves 216 256 128 600 606 Modules /Stave(Stub) 26 Short Strip Staves Long Strip Staves Stubs Total (After yield) Totals No Staves 216 256 128 600 606 Modules /Stave(Stub) 26 4 No Modules 5616 6656 512 12784 13557 Hybrids/Module 2 1 No. Hybrids 11232 18400 20489 No. ABC ASICs 112320 66560 5120 184000 225377 No. HCCs No. DCDC/SP Boards 13357 Meeting on ITk production databases

# Modules/Both sides of Petal Numbers: Endcap # Modules Total After Yield Total R5 Modules 1792 1810 R4 Modules R3 Modules R2 Modules 896 905 R1 Modules R0 Modules 8064 8552 Endcap # Disks 14 # Petals/Disk 32 # Petals 448 # Modules/Both sides of Petal 18 # Modules 8064 R5 R4 R3 R2 R1 R0

Numbers: Endcap R1 to R4 Hybrids Hybrids 105 % Hybrids ABC ASICs/Hybrid #ABC ASICs For 100% #ABC ASICs for 105% R5 H0 896 941 9 8145 8553 R5 H1 R4 H0 8 7240 7602 R4 H1 R3 H0 7 6335 6652 R3 H1 R3 H2 R3 H3 R2 H0 12 10860 11403 R1 H0 11 9955 10453 R1 H1 R0 H0 R0 H1 Total 11648 12233 113 102265 107382

And Finally Endcap Totals After Yield Totals Modules 8064 8552 Hybrids 11648 12223 ABC ASICs 107832 112752 HCCs Barrel Totals After Yield Totals Modules 12784 13557 Hybrids 18400 20489 ABC ASICs 184000 225377 HCCs Will use these numbers as the basis for the following build numbers Of course these numbers will change once the yield estimates become more fixed Meeting on ITk production databases

What do we want to record? –Stave/Petal Core Item Data Type Comments Foam Block Lot number from manufacturer Density Pipe Lot number Pressure test results Flow tests/impedance Epoxy Facings Pre-preg number Bus Tape excel or text file, photos in jpeg Resistance measurements in excel Survey results Electrical tests Honeycomb Meeting on ITk production databases

What do we want to record? –Stave/Petal Tests Item Data Type Comments QC results excel file excel file, plots Component weights Flatness/thickness Bending Statistics Thermal Performance Delamination Tests Petal/Stave electrical test .dat , eps 3 point Gain Threshold Noise Occupancy Meeting on ITk production databases

What do we want to record? - Modules Item Data Type Comments Hybrids .dat , eps 3 Point Gain Threshold Noise Occupancy # dead, masked channels ABC ASICs Wafer map, .dat, .eps Wafer tests Sensors .dat I-V C-V bow for some Modules # dead, masked channels survey HCC Bustape ?? Data from tape testing Meeting on ITk production databases

What do we want to record? Currently .eps/.ps files produced from hybrids and module scans are ~1.2Mb Strobe delay + Threshold scan + Noise Occupancy scan ~= 4Mb/object ~54k Objects* = ~ 216 GB *this is just hybrids and modules and doesn’t include dat/txt files Meeting on ITk production databases

What do we want to record? We would like to trace "service" material Glues Jigs Test frames Test setups From EC database experience “We were able to trace the number of components available, where we could expect shortage of them, etc.” “This saved us in a couple of occasions. It also helped to monitor the learning slope of the production and to detect weak points in the chain…” Meeting on ITk production databases

Visual Inspection - Photos Has been a request to have the ability to add photos Trace defects/visual inspection stage through Sensor -> Hybrid -> Module -> Stave/Petal assembly ~ 54k objects (hybrids + modules) x 3 photos = 150k photos This an issue? Meeting on ITk production databases

RFiD - Barcodes Strips community have began to integrate RFiDs onto hybrids. The current design for the ABC130 Barrel Hybrids use LXMS31ACNA-010 EPC memory (Electronic Product Code): 240 bit unique device ID User memory: 512 bits TID: 64 bits, unique address assigned by the IC manufacturer Scanning of RFiDs could also allow tracing of components throughout the build project Beginning to think about linking RFiD IDs of hybrids to any future database naming conventions Meeting on ITk production databases

Naming Conventions Still at early stages for Barrel More developed for Endcap due to greater number of Hybrids/Modules (next slide) So far only gone as far as convention for actual objects Not where it was made/location etc. Meeting on ITk production databases

Naming Conventions For EC, numbering scheme to be implemented, e.g. R0H1S0 (Ring 0, Hybrid 1, Sensor 0). R5 module R4 module R3 module R2 module R1 module R0 module S0 S1 H0 H1 H2 H3 Meeting on ITk production databases

Summary Hopefully we have been able to gather information that will help for Components Max part numbers Input to database Developing all the time We have (at present ) have no input regarding “type of database” Feedback seems to be the previous SCT database was very good Meeting on ITk production databases