U.S. ATLAS HL-LHC Upgrade Level 2 and Deputies-NSF only Management Mailing List

["Redlinger, George" <redlinge AT bnl.gov>]

Thanks John.  The time works for me.

About the wafer shortage, we had a thread on this inside the PO back in 
February.  I think the sentiment at that time was that this is mostly 
COVID-induced.  But maybe it would be good to revisit this.  Droughts in 
Taiwan certainly didn’t help the situation but maybe that too counts as an 
Act of God, which we don't track...  Maybe others want to comment.


-----Original Message-----
From: John Parsons <parsons AT nevis.columbia.edu> 
Sent: Friday, May 14, 2021 1:23 PM
To: Redlinger, George <redlinge AT bnl.gov>; 
usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
Cc: usatlas-hllhc-management-l AT lists.bnl.gov
Subject: Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Risk scrubbing


Hi George,

        For LAr, we propose to use for the risk scrubbing the timeslot for 
our weekly LAr meeting, which means to start at 12:30 pm on Friday May 21. 
Let us know if that works for the PO folks.
        In our LAr discussions, a question came up: there is a lot of 
discussion these days about the global ASIC shortage and how that might 
impact the upgrade.  Given the ASICs across the project, perhaps this would 
be best handled more globally, similar to the "commodity volatility" risk, 
rather than each individual ASIC effort separately trying to take this 
account?  The latter approach would anyway require a lot of coordination 
across subsystems, to try make sure at least 
somewhat uniform assumptions are made, ...   So we would propose to 
basically ignore this at the subsystem level, and have a global risk deal 
with such delays. Let us know what you think.
        Regards,
                John

On 5/11/21 2:49 PM, Redlinger, George wrote:
> Hi NSF L2s,
> 
> As part of the preparation for the NSF review, we would like to find 
> time in the next week or two to take a deep dive into the risks for 
> each of the NSF subsystems.
> 
> We think a 2-hr slot should be enough for each subsystem.  This would 
> be a listing/review of each risk by the L3's as in previous risk 
> scrubbings.  Recall that there is now a tab in the risk register that 
> should make it easy to produce the summary slide for each risk.
> 
> We would also ask for one summary talk by L2s of all the system's BCPs 
> since the start of MREFC and how they line up with our risks.
> 
> Could you discuss with your L3 teams and propose a few possible time slots?
> 
> Thanks,
> 
>      Your friendly PO
> 
> 
> _______________________________________________
> Usatlas-hllhc-l2deputymgmt-nsf-l mailing list 
> Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-
> l
> 

--
______________________________________________________________________

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!WsCUruBXmfDmmIV8C8HGlpheDBK40dL23Cd2N9nQLCyt_xTMVPIdp7tnWxcJMdU$
     

______________________________________________________________________