DOM Integration Meeting 27 May 2020 - Daniele Vivolo INFN Section of Naples D. Vivolo - DOM Integration Meeting - CERN Indico
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
DOM Integration Meeting
27 May 2020
Daniele Vivolo
INFN Section of Naples
1 D. Vivolo - DOM Integration Meeting 27/05/20
ORCA-Phase2 DOM Integration: kick-off
Overview
Involved sites: Amsterdam, Nantes, Strasbourg
Planned start of activities: April 15 -> mid June
Validation task force at Nikhef
The integration of the first two Phase2 DOMs (572 and 573)
will serve multiple purposes.
1. Validation of the new variant PMT support structure (HP-
R14374-02)
2. Debugging, further development and tuning of the DIA
3. Finalization and test of the updated DOM testing software
suite
2 D. Vivolo - DOM Integration Meeting 27/05/20
The new variant PMT support structure (HP-R14374-02)
Overview
• Need: a new design was made necessary by the different shape of the new variant of PMTs (HAMA-R14374-02)
• Preliminary: re-design done by Edward
• Status: first two prototypes available
• Applies to: this new variant will be used in ALL THE FUTURE DOMs FROM TODAY! (except 2)
Preliminary observations: PMT and light collection rings fitting
There is more space between the PMT and the reflector.
A new tool needs to fix the distance at assembly, the
PMTs will not be pushed fully in, the front will be at the
same distance from the glass of the sphere.
Validation task goals
• validating the new PMT support structure variant, in order to launch the
production (bottleneck for ORCA-Phase2, needed quite urgently also for
Phase1) Second ring now also needs
• dedicated mounting procedure, to be incorporated in the main DOM air-escape holes since the
Integration procedure PMT holes are deeper
• PMT insertion tool: official drawings and, if possible, one tool for each site
3 D. Vivolo - DOM Integration Meeting 27/05/20
Validation task force at Nikhef: the DIA
Overview
In the last 1.5 year a lot of work has been done by Giuseppe to bring the software to maturity. Months of development followed by more
than one year for debugging, with an intermittent and non-homogeneous contribution by the different DOM Integration sites, lead us to
the first official release. The new DIA User Manual (v2) is available at the following link
https://drive.google.com/open?id=1OYLyXJD3Zx_YSAaOFUOxOU678aSj7eZh
We did our best, working with dummy components to try to simulate all the possible real situations in DOM Integration, but reality will
offer a new insight and probably some things to adjust. We tried to maximize the possible scenarios and hence to anticipate as much as
possible involving all the DOMINT sites in the debug, but the integration of the validation DOMs will be the real challenge for the DIA.
DIA HOTLINE ☎
A 24/7 online channel has been established for all the period of the integra]on, including the Nikhef Team, Giuseppe Levi and me.
The goal is to establish a bi-direc]onal flow of informa]on and support:
• provide a quick and reliable solu]on to all the possible issues encountered during DOM Integra]on (due to bugs in the so`ware or
not enough clear instruc]ons in the DIA user manual)
• give all kind of feedbacks and observa]ons about the performances of the DIA + sugges]ons for improvements
• brainstorming: tailor the DIA on the needs of DOM Integra]on sites, tuning/introduc]on of new features.
At the end of the validation task force, we will have a REx aimed at planning all the needed actions towards the start of
Phase2 DOM mass production. In addition, a thematic DOM Integration Meeting will be done, dedicated to the DIA
4 D. Vivolo - DOM Integration Meeting 27/05/20
DIA HOTLINE: first (selected) outputs
Local inventory management
The local inventory management feature of the DIA is based on KM3NeT DB streams getting the "last seen at" location of each component.
More precisely, 3 operations are "scanned": INTEGRATION, NCR and SRS.
• INTEGRATION: used to delete UPIs from the list of available components. REMARK: not valid for batch products! They must be
managed manually
• SRS: used to trace the current position of each component.
This makes possible an efficient tracing of the components moving within the Collaboration, but "new" components (meaning those
coming dierctly from the producer) are not present in the list until shipped somewhere different wrt their first delivery location (or
integrated or declared Non-Conform...).
It is clear that we must cover also these cases in the automatic management of the inventory. Two solutions have been proposed:
PROPOSAL #1: once a component is delivered from the company to the first delivery place, a "fake SRS" is raised.
• PROs: everything is already there, nobody should do anything both on the DB and DIA side. Raising a "fake SRS" upon delivery, we would
already have all the components in the existing DB stream that we use in the DIA.
It is also not properly "fake", considering that a shipment is really done (from the company to the KM3NeT site!). It would be just a
matter of filling the SRS form upon the delivery of each shipment of components (LQSs already do an incoming check for procured
components). Once the list of UPIs is available, an SRS can be raised straightforwardly and with the automatic hourly synchronization
implemented by Giuseppe we can have the job done in a relatively short short time. Clean and fast.
• CONs: this would imply an extra work for the LQS. Workload, procedures and potential effects are under evaluation
5 D. Vivolo - DOM Integration Meeting 27/05/20
DIA HOTLINE: first (selected) outputs
PROPOSAL #2: the first location is indicated during the product registration, with the addition of a dedicated field
• PROs: no additional work is asked to the LQS. Product registration is something that is already done for each procured component
(unique, batch...). Along with all the other info fields (like purchase date, owner institution etc) it will be enough to add a "first delivery
location" field.
• CONs: this would require some work on the DB/DIA side. More specifically:
o a new field should be added in the product registration form
o the KM3NeT DB stream should monitor also the REGISTRATION location (along with INTEGRATION, NCR and SRS), or a dedicated
stream should be created
o the DIA should be modified accordingly
Not really major modifications, anyway…
REMARK: most of the times, with the exception of some off-the-shelf components like some consumables, the components are
registered on the DB way before they are even produced. This is because we need to tell the company what is the UPI to print on the
sticker to attach on them. Assigning a "first delivery location" here, would need that we already know what the first delivery destination
will be (well...we SHOULD) and would imply that some components will be present in the local inventory of the DOM Integration sites
even before they are produced. This sound a bit error-prone, but probably doable, in the end.
!!!ALERT: TEMPORARY SOLUTION BELOW!!!
An officialdecision has not been taken yet, still waiting for some feedbacks.
As a temporary solution, we have decided with the team of Nikhef to raise an SRS with all the components delivered in Amsterdam
directly from the company. It costed some extra effort to Frank (thanks again!) but it worked. Everything is now synchronized and
correctly updated, including batch components! @Safia, Hervé: let’s get prepared to do the same at your sites
6 D. Vivolo - DOM Integration Meeting 27/05/20
DIA updates
What’s new in the DIA User Manual v2
Two important points that were still missing in the DIA User Manual v1 have been now added, debugged and documented:
• Acceptance test sheet filling
• DOM finalization
Acceptance test sheet
Divided in three TABs: general, dark counts, ToT. Each field has a corresponding blank (some discussion is ongoing to make
this more efficient). One REGISTER button to upload all the data at once.
General Dark counts ToT
7 D. Vivolo - DOM Integra3on Mee3ng 27/05/20
DIA updates: DOM finalization What’s new in the DIA User Manual v2 Two important points that were still missing in the DIA User Manual v1 have been now added, debugged and documented: • Acceptance test sheet filling • DOM finalization DOM finalizaCon The DIA can be used with ALL exisGng DOM variants, but has been opGmized for the TSFP ones (all ORCA + Phase1 "replacement DOMs" + ARCA-Phase2 "à la Phase1"). Short excursus: the TSFP DOMs will be fully interchangeable. This leads to an enormous flexibility and high gain in terms of money (less shipments needed), logisGcs and reduced single points of failure of the project. Based on this philosophy, the DIA goas all in and pushes this flexibility to the extreme All the DOMs will have the same variant, the operaGng wavelength will be assigned during DU IntegraGon Process 1 and stored as a common TEST parameter. The serial number will be the only parameter to idenGfy a DOM. UnGl DOM is bapGzed, all DOMs are perfectly indisGnguishable. This means that also all the DOM sub-systems will be indisGnguishable unGl the very last step of DOM IntegraGon (called DOM delivery in the DIA). This new approach requires a bit of mind-adapGon, but it’s the most faithful representaGon of the new scenario introduced by batch TSFPs. YOU ARE WARMLY RECOMMENDED TO KEEP TRAINING!!! Please, do it while you are sCll in Cme! 8 D. Vivolo - DOM Integration Meeting 27/05/20
New DOM exploded view
The new DOM exploded view (version 19) is now available. Thanks to Edward for the nice job
It will not be available un2l the corresponding DCR will be closed
Date May 2020
File name KM3NeT_MECH_2015_001-DRA_DOM_Exploded_View
Author Edward Berbee
Version 19 Unique products
Approved by Daniele Vivolo Batch products
All dimensions in mm unless indicated otherwise
PBS Description Quantity Pos. number
TOP PART
3.4.1.3.1 Top hemisphere 1 1
3.4.1.10 Vacuum valve 1 2
3.4.1.6.1 Cooling mushroom 1 3
Primer for cooling mushroom 0,01 4
3.4.1.5 Optical interface / gel 200 gr. 5 (60,78)
3.4.1.2.2 Penetrator 1 6
Centering clip, type 2 1 7
Adapter ring 2A 1 8
20 ID X 2 CS MM O-RING VITON 90+/-5 SHORE A 1 9
The main changes that can (not!) be observed are:
25 ID X 2 CS MM O-RING VITON 90+/-5 SHORE A 1 10
Profiled washer 2 / 3 mm thick / round side to glass 1 11
Washer, DIN 125-1A A2 M16 1 12
Spring washer typeA DIN 2093 A2 16.3 x 1.75 x 2.3 1 13
Hexagon nut M16 DIN 439 A2 1 15
3.4.1.6.2 Cooling bar 1 16
Countersunk screw, ISO 10642 A2 BZK 5 x 12, Din 7991 2 18
3.4.1.6.9 Powerboard cooling gap-pad, GP 1000 SF, 130 diameter x 0. 1 19
• SFPs are now batch components
3.4.3.5 Power conversion board 1 20
Screw ISO 7380-2 A2 BZK 3 x 8 11 21 (77)
3.4.1.6.7 Faraday plate 1 22
3.4.3.2 CLB 1 23
Power connector CLB 1 24
Power ferrules 2 25
Spring holder 1 26
Spring, 0.4 x 4 x 7.9, DIN 2089-1, RVS 1 27
Nylon bushe 3.1 x 6 x 4 mm 005315500002 2 28
• the PMT support structure is no more in quarters
Brass-nickel bush 3.2 x 6 x 5 mm 311320540050 5 29
3.4.1.6.6 FPGA coolblock 1 31
3.4.1.6.10 FPGA cooling gap-pad, GP 1000 SF, 14 x 10 x 0.5 1 32
Screw DIN 912 A2 4 x 16 1 33
3.4.1.6.5 Fiber tray 1 34
3.4.3.2.3.2 Optical A/D filter 1 35
Screw ISO 7380-2 A2 BZK 3 x 14 7 36
3.4.3.2.3.1 TSFP module 1 37
• the EXTENDED pressure gauge is reported
3.4.1.6.11 TSFP cooling gap-pad, GP 1500 S30, 14 x 7 x 1.5/ /GP1500S30 1 38
3.4.1.6.3 TSFP coolblock 1 39
Screw ISO 7380-2 A2 BZK 3 x 20 1 40
3.4.3.1.1 Octopus board small 1 41
Nylon bush 4.3 x 7 x 2.3 mm 1 42
Screw DIN 912 A2 4 x 12, 1 43
Splice protector 1 44
3.4.1.4.1.2 Top PMT structure 1 46
3.4.1.11 Silicon mastic 47
3.4.1.7 Pressure gauge 1 50
3.4.3.7.1 Nano beacon 1 51
3.4.3.7.3 Nano beacon cable 1 53
3.4.2.6 52 ID X 3 CS MM O-RING VMQ 70+/-5 SHORE A 12 54 (69)
PMT base 12 55 (70)
3.4.2.3 PMT 12 56 (71)
3.4.2.1 Light reflector 12 57 (72)
3.4.2.5 HV cap TS21B 12 58 (73)
3.4.1.5 Optical interface / gel 1350 gr. 60 (5,78)
BOTTOM PART
3.4.1.3.2 Bottom hemisphere 1 61
3.4.3.6.2 Piezo sensor 1 62
3.4.1.12 Piezo glue UHU endfest 300 1 63
3.4.1.4.1.2 Bottom PMT structure 1 64
3.4.3.6.5 20.3 ID X 2.62 CS MM ) O-RING VMQ 70+/-5 SHORE A 1 68
3.4.2.6 52 ID X 3 CS MM O-RING VMQ 70+/-5 SHORE A 19 69 (54)
PMT Base 19 70 (55)
3.4.2.3 PMT 19 71 (56)
3.4.2.1 Light reflector 19 72 (57)
3.4.2.5 HV cap TS21B 19 73 (58)
3.4.3.1.2 Octopus board large 1 74
3.4.1.6.4 Sliding part 1 75
Nylon bush 3.2 x 8 x 3 mm 1112130000VR 2 76
Screw ISO 7380-2 A2 BZK 3 x 8 2 77 (21)
3.4.1.5 Optical interface / gel 2000 gr. 78 (5,60)
Remark: the list of allowed variants for each component
Spring 0.5 x 4 x 15, DIN 2089-1, RVS 6 79
Screw DIN 912 A2 4 x 25 1 80
CLOSED DOM
3.4.1.8 Sphere sealant Terostat 1.2 m 81
3.4.1.9 Tape Scotchrap 50, width 25.4 4m 82
3.4.1.1.1 Titanium collar 1 83
Backspacer 2 84
3.4.1.1.4 Bolt M6 x 25, din 933, titanium grade 5, blue anodized 6 85
are no more reported in the exploded view.
Insert foot, rubber Essentra 049 1600 114 07 4 86
3.4.1.1.5 Nut M6, DIN 934, titanium grade 5, blue anodized 2 87
Please refer to the DOM Container map on the DB for it
(everything is updated for both CHXXY and TSFP DOMs).
9 D. Vivolo - DOM Integration Meeting 27/05/20
Phase1 DOM Integra8on: plans at the restart
Athens
• ORCA-DU1 DOM refurbishment to be completed
• Reach Phase1 goal: 18 more DOMs
• ARCA-DU2 refurbishment (?)
ECAP
• OLD ORCA-DU1 DOM refurbishment to be started (please
warn me when the shipment from CPPM can be re-arranged)
• penetrator fixing on one DOM
• Reach Phase1 goal: 18 more DOMs
Catania
• complete the last step of the LSMv3 compass validation
(instructions and procedures required?)
• complete the integration of the DOMs currently on bench
• Reach Phase1 goal: 18 more DOMs
Please, give a look at the Gantt for a detailed description of
Rabat commitments and time schedules!
• the full set of components for the first 7 DOMs are being
collected in Strasbourg (more ambitious Phase1 goal!) Some re-assignment can still be agreed over the Phase1 goal
• knowledge transfer and training mode to be defined (remote since the group of Naples will be soon back in the business (exp.
until Covid-19 restrictions are still in place?) late September/early October 2020).
10 D. Vivolo - DOM Integration Meeting 27/05/20DOMINT @ the next ANTARES/KM3NeT Collaboration Meeting
A remote Collaboration Meeting
Due to the Covid-19 lockdown restrictions, the next Collaboration Meeting will be remote.
A brand new format:
• Plenary sessions in the mornings fro the 8th to the 12th of June (original dates)
• Parallel subgroup sessions the week before
The DOM Integration parallel session is scheduled on Friday, 5th of June
from 9.00 to 12.00. Please save the date!
Scheme:
the usual one: brief overview done by me, large space to updates from
the DOM Integration sites, discussion time
Focus on:
o updates from the last Collaboration Meeting (well…not that much)
o current activities (Integration + collateral)
o plan at restart + short/mid term
o local situation (manpower, space)
o ongoing/foreseen upgrades: goal, status, perspectives
Allocated time: If possible, try to attend as much parallel sessions
15 min for each site as possible!
Connection details: In case of (sudden or not) unavailability, just send
not yet available, will be communicated in time. your slides to me and I will present them on behalf
11 D. Vivolo - DOM Integration Meeting 27/05/20Backup slides 12 D. Vivolo - DOM Integration Meeting 27/05/20
You can also read
