U.S. ATLAS HL-LHC Upgrade LAr Level 2 and Level 3 Managers Mailing List

["Ma, Hong" <hma AT bnl.gov>]

Hi John,

 

                I did not realize that there are also the Columbia tasks for COLUTA QC test.

 

                It looks like the similar tasks in Columbia and Austin are not sync’ed explicitly in P6.    The baseline dates for similar tasks are already out of sync.    In addition, looking at the current status sheet, Columbia tasks have been statussed more aggressively than the Austin tasks. 50% complete vs 25% complete.    Both of these lead to earlier completion of ADC in the working schedule for Columbia.

 

                The baseline plan for testing is 1/16 (i.e., 2500 chips) per 2 months.  This is probably based on manual testing, so the robotic testing can be faster.

 

                For the FEB2 production, it looks like the dependency is through the Columbia testing schedule (for example, FEE10650A for 50% available is part of the Columbia tasks).    So the ADC schedule is not affecting the FEB2 production in the working schedule.  If Austin schedule is used, it may be getting very close to critical path.  In the working schedule, the last 25% of FEB2 assembly task (FEE10780) starts on 6-May-2027, which is a day after the COLUTA completion date in Austin schedule (coincidence?).   

 

                Best,

 

                Hong.

 

 

From: usatlas-hllhc-lartl2l3-l-request AT lists.bnl.gov <usatlas-hllhc-lartl2l3-l-request AT lists.bnl.gov> on behalf of John Parsons <parsons AT nevis.columbia.edu>
Date: Sunday, June 22, 2025 at 10:21 AM
To: Ma, Hong <hma AT bnl.gov>, usatlas-hllhc-lartl2l3-l AT lists.bnl.gov <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
Subject: Re: [[Usatlas-hllhc-lartl2l3-l] ] draft slides posted for LAr L2 talk at NSF review

Hi Hong, all,

        Thanks for the comments, which I have implemented.  Concerning the ADC
schedule, I tried to use the working schedule (wjocj IO donloaded from
IPD and attach) for all dates.  Looking more closely now, I see what
happened:

- since both Columbia and UT Austin work on ADC, the plan always had a
set of more or less duplicated tasks for Columbia (6.4.1.1) and Austin
(6.4.1.2).

As an example, each L4 has a task called "Milestone: Production Complete
- ASICS".  For Columbia, this is taskID FEE10780, whereas for Austin it
is taskID FEE20940.

These pairs of tasks were intended to occur at the SAME time, and this
is how the schedule was originally built.  However, something has gotten
badly "broken" in P6.  The Columbia date is by now 10-Jun-26, whereas
the Austin date is now 05-May-27; a full 11 months later!!

        This is clearly a "bug", and I am sure Tim does not expect to take
almost 2 years from now to test his 40k chips! As an estimate, at their
current QC rate of 7 minutes per chip, it would take 195 days of 24:7
operation to test all the chips.  Building in some inefficiencies (eg.
take average of only 20 days of operation per month), that would be a
bit less than 10 calendar months.  So, the June 26 date seems more or
less reasonable, whereas May 2027 is not.

        Tim and I need to go line-by-line through the relevant parts of P6 and
figure out what has gone wrong, and how to "fix" it.
       
        Regards,
                John

On 6/21/25 11:11 PM, Ma, Hong wrote:
> Hi John,
>
>                  A few comments:
>
> Slide 11: “In schedule, all ADC QC tests will be complete by mid-2026”
>                      The working schedule actually shows the completion in May 2027.  It is misleading to just mention the baseline schedule.
>
> Slide 14: it would be nice to point to the picture where the LSB2s are, just like you did on slide 13 for ALFE and COLUTA
>
> Slide 26: Under 6.4.3 BE Electronics
>
> “Hold FEB2 FDR and launch preproduction”
>
> •
>
> “Hold STRM FDR and launch preproduction”
>
>
> Slide 27: Last bullet. For PRRs it is probably better to say mid-2026, rather than early 2026.
>
> Slide 30: “FY26 will see the completion of the scope in 6.4.1”.  See the comment on Slide 11.
>
>                  Tim should comment on the ADC QC test schedule in the working schedule. If it is true that the last ADC will be delivered in May 2027, it may get very close to the critical path.
>
>                  Best,
>
>                  Hong.
>
>
> From: usatlas-hllhc-lartl2l3-l-request AT lists.bnl.gov <usatlas-hllhc-lartl2l3-l-request AT lists.bnl.gov> on behalf of John Parsons <parsons AT nevis.columbia.edu>
> Date: Saturday, June 21, 2025 at 6:15 PM
> To: usatlas-hllhc-lartl2l3-l AT lists.bnl.gov <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
> Subject: [[Usatlas-hllhc-lartl2l3-l] ] draft slides posted for LAr L2 talk at NSF review
>
> Hi all,
>
>          I have posted a draft of my slides for my LAr L2 presentation for the
> upcoming NSF review on the Indico page for our meeting yesterday
> (https://indico.bnl.gov/event/28689/  ). Comments are welcome.
>
>          Regards,
>                  John
> --
> ______________________________________________________________________
>
> John Parsons
> Nevis Labs,              Email: parsons AT nevis.columbia.edu
>    Columbia University   Phone: (914) 591-2820
> P.O. Box 137            Fax: (914) 591-8120
> Irvington, NY 10533     WWW: https://urldefense.com/v3/__http://www.nevis.columbia.edu/*parsons/__;fg!!P4SdNyxKAPE!GxE-combZ3VgnOE4o_b8_l3RB-enxd37z8Cp8CBTWNUDLGf75zZRUMLpZmslKRc-jFf44Tu2-rG1qXeSHQ1vL04Dcmf6u2O07_olW5R-sQa58w$<https://urldefense.com/v3/__http:/www.nevis.columbia.edu/*parsons/__;fg!!P4SdNyxKAPE!GxE-combZ3VgnOE4o_b8_l3RB-enxd37z8Cp8CBTWNUDLGf75zZRUMLpZmslKRc-jFf44Tu2-rG1qXeSHQ1vL04Dcmf6u2O07_olW5R-sQa58w$>
>
> ______________________________________________________________________

--
______________________________________________________________________

John Parsons
Nevis Labs,              Email: parsons AT nevis.columbia.edu
  Columbia University   Phone: (914) 591-2820
P.O. Box 137            Fax: (914) 591-8120
Irvington, NY 10533     WWW: https://urldefense.com/v3/__http://www.nevis.columbia.edu/*parsons/__;fg!!P4SdNyxKAPE!HDHm1AWE1nRWOHqV4xwx0TR21dUGU8AQGRzf-SxcCb9oGeHBVYr2KFFcSVEop9B1Umt9FT7QT4-8Avm2SdgMoKepHV8LRAq9HNi9_FeS3BCY3Q$       

______________________________________________________________________