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

[John Parsons <parsons AT nevis.columbia.edu>]

Hi Hal, all,

        A few comments/questions about how to handle all
this, taking as examples a couple of LAr considerations
which could be tricky:

1. the ATLAS SVR for 6.4.3 BE is scheduled for Nov. 2020
        - I will argue that the BE is based very closely
on Phase 1, so the "v1 preproto design" which will be
complete before Apr. 2020 will allow us to meet the
"construction ready" mark.  However, given that the
HL-LHC Specs for the BE will not even be reviewed
until Nov. 2020 leaves this argument quite open to
challenge
        (I guess there are also some other subsystems
with some SVR dates after start of MREFC?)

2. a low probability but high impact risk for the ADC
in 6.4.1 is that it fails somehow and we have to fall
back to a COTS device (with much higher cost, ...)
        - I will argue the 2 rounds of preproto so far
have reduced this risk, and the v3 preproto that will
be submitted and tested still as part of preMREFC
will get us to where we can retire (or be forced to
unfortunately realize) this risk.  However, what if we
are not 100% confident to make this decision before Apr. 1,
particularly given the NSF restriction on spending
contingency unless you have an associated risk?  ie. if
we retire it, and then find a problem a month later
that anyway forces the COTS backup solution, where do
we get the ~$2M needed??  To guarantee we don't fall
off this cliff, I would of course like to keep the
risk active, albeit with a Very Low probability.  But
how do we say this does not contradict the clause to
"eliminate all technological risks" ?

        Regards,
                John

On 7/17/19 7:33 AM, Hal Evans wrote:
> Hi David,
>
> Mike should weigh in here as well if I've left anything out. But I think 
> that we (the PO) need to make sure that Mark Coles is aware of the 
> potential for misunderstanding when he says things like "ready to start 
> construction". We will point this out to him next time we speak.
>
> Our interpretation of "construction readiness", which is consistent with 
> all of the FDR requirements laid out in the NSF Major Facilities Guide 
> is summarize in Gustaaf's 2019-06-14-FDR-requirements.pdf file posted on 
> CERNBox <https://cernbox.cern.ch/index.php/s/Y25Sh5qQUxS0s6P> (pwd: 
> US-Atlas-2019).
>
> We're working on a simple summary of all this. The current *draft* is:
> "Pre-MREFC R&D work has allowed the project to eliminate all 
> technological risks and deliver designs and specs that could be placed 
> for industry.  A number of deliverables are ready for pre-production; 
> for others, production of a larger number of prototypes or components is 
> needed to allow the integration tests needed to proceed to construction 
> without excessive risk."
>
> Comments on this are very welcome. We'll send around the final version 
> as soon as we're happy about it.
>
> Cheers  -  Hal
>
> On 7/16/19 7:15 PM, David W Miller wrote:
> > Hi Mike,
> >
> > Thanks a lot for sending this again.
> >
> > However, I don’t see a statement that refines the message made in 
> > Point #5 on page 1. In today’s discussion, we went over how this is 
> > “meant” to really refer to the overcoming of technical and 
> > technological hurdles, not that we are literally ready to begin 
> > construction (the phrasing from the PO in that discussion was much 
> > better than what I’ve repeated here). I thought that this was 
> > particularly useful and important. Do we have that more nuanced 
> > message somewhere in this word Doc, and I have just missed it?
> >
> > Thanks,
> > David
> >
> > > On 16 Jul, 2019, at 09:30, Michael Tuts <tuts AT pmtuts.net 
> > > <mailto:tuts AT pmtuts.net>> wrote:
> > >
> > > Hi All,
> > > I believe this went out to you some time back, but it may be worth 
> > > sending this out again. It is notes from Mark Coles and Rebecca Yasky 
> > > based on their attendance at the CMS Director’s Review. There may be 
> > > some points that are relevant to your systems.
> > > PO
> > >
> > >
> > > <NSF feedback to ATLAS on CMS on Directors Review 
> > > 190518.docx>_______________________________________________
> > > Usatlas-hllhc-l2deputymgmt-nsf-l mailing list
> > > Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov 
> > > <mailto:Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov>
> > > https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l
> >
> >
> > _______________________________________________
> > 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
>
> --
> ^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
>   Hal Evanshgevans AT indiana.edu
>             https://urldefense.proofpoint.com/v2/url?u=http-3A__pages.iu.edu_-7Ehgevans_&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=Z0wuTxQYnTTMlYma4lGZlO3skeCGVBrGGurYkWbhJsJuG5HaY82rmCNSdFOV7C4Z&m=1iGzC-aAAj2sKObs7I4rPQ8HhkhOX2xz0eosq8twc-s&s=eveRiKAvy_pvBglExvFBIk9caDrtohUp9D3qQ54xC74&e= 
>   Tel: (812)856-3828                Fax: (812)855-5533
>   253 Swain Hall West               Indiana University
>   727 E. Third St.               Bloomington, IN 47405
> v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^
>
>
> _______________________________________________
> 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.proofpoint.com/v2/url?u=http-3A__www.nevis.columbia.edu_-7Eparsons_&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=Z0wuTxQYnTTMlYma4lGZlO3skeCGVBrGGurYkWbhJsJuG5HaY82rmCNSdFOV7C4Z&m=1iGzC-aAAj2sKObs7I4rPQ8HhkhOX2xz0eosq8twc-s&s=ktKjM1fFaZNQ0y-jpEirQNA-opOgZImTREJmHGijmeI&e=
    

______________________________________________________________________