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

["Kotcher, Jonathan" <kotcher AT bnl.gov>]

Yes, you either just scale it by some appropriate factor, or add a fraction 
of the following year (except there is ramp up by then, etc.)
But these are crayon-level estimates, will have to be accepted when things 
are requested on such time scales
Thx --j 

On 12/12/19, 4:03 PM, "Usatlas-hllhc-l2deputymgmt-nsf-l on behalf of John 
Parsons" <usatlas-hllhc-l2deputymgmt-nsf-l-bounces AT lists.bnl.gov on behalf of 
parsons AT nevis.columbia.edu> wrote:

    
    OK, I will take FY21 + 0.5*FY21 as some ballpark estimate, assume we 
    need ALL the engineering manpower and 50% of the technician manpower, 
    and nothing else (ie. no M&S or travel or ...).  That will give at least 
    some approximation of what it would take to not lose the people.
    
    On 12/12/19 3:58 PM, David W. Miller wrote:
    > Good point, I’d forgotten that. Indeed, should take the full FY20 
number 
    > then indeed.
    > 
    > Thanks!
    > David
    > 
    > 
    >> On Dec 12, 2019, at 2:57 PM, Stephanie Majewski <smajewsk AT uoregon.edu 
    >> <mailto:smajewsk AT uoregon.edu>> wrote:
    >>
    >> Hi David,
    >>
    >> I thought in the cost books FY20 only included MREFC...? So no need to 
    >> take the 1/2.
    >>
    >> Stephanie
    >>
    >> On Thu, Dec 12, 2019 at 12:53 PM David W. Miller 
    >> <David.W.Miller AT uchicago.edu <mailto:David.W.Miller AT uchicago.edu>> 
wrote:
    >>
    >>     Hi John,
    >>
    >>     What I did (in a private mail sent to Mark Oreglia for comment)
    >>     was just to average FY20 and FY21 since Apr2020—Mar2021 spans half
    >>     of each.
    >>
    >>     Cheers,
    >>     David
    >>
    >>     > On Dec 12, 2019, at 2:44 PM, John Parsons
    >>     <parsons AT nevis.columbia.edu <mailto:parsons AT nevis.columbia.edu>>
    >>     wrote:
    >>     >
    >>     >
    >>     > Hi all,
    >>     >
    >>     >       I was looking back at the documentation from the time of
    >>     FDR, such as the L2 Cost Book.   However, everything is rolled up
    >>     according to FY, so I don't see a simple way with those docs to
    >>     get the costs for Apr. 1/2020 - Mar. 31/2021.
    >>     >       Mike/Jon, will you be able to get that from the Cost
    >>     Controls people?
    >>     >
    >>     >               John
    >>     >
    >>     > On 12/12/19 1:14 PM, Michael Tuts wrote:
    >>     >> Hi NSF scope L2 and deputy,
    >>     >> Despite knowing the LS3 would be delayed by a year, NSF is now
    >>     asking on a very short timescale for an assessment of the impact.
    >>     There is one question posed where we can use your input on the
    >>     impact of a 1 year delay of MREFC funding.
    >>     >> “Please also comment on the impacts, by Level 2 WBS, of the
    >>     impacts if there were to be a one-year delay in the start of MREFC
    >>     funding. Include the risks or standing army costs of engineer and
    >>     technician labor, or other negative impacts of NSF funding delay.
    >>     Im assuming the risk of losing key technical staff in your
    >>     engineering pool that would otherwise move to other projects at
    >>     the various universities is a big factor.”
    >>     >> Can you please provide an initial assessment for your L2 asap –
    >>     note we are requested to provide an answer by 9am tomorrow 
(Friday)!
    >>     >> Thanks, PO
    >>     >> *From:* Coles, Mark W. <mcoles AT nsf.gov <mailto:mcoles AT nsf.gov>>
    >>     >> *Sent:* Thursday, December 12, 2019 12:23 PM
    >>     >> *To:* Michael Tuts <tuts AT pmtuts.net <mailto:tuts AT pmtuts.net>>;
    >>     Anders Ryd <anders.ryd AT cornell.edu <mailto:anders.ryd AT cornell.edu>>
    >>     >> *Cc:* Gonzalez, Saul <sgonzale AT nsf.gov
    >>     <mailto:sgonzale AT nsf.gov>>; Caldwell, C. Denise <dcaldwel AT nsf.gov
    >>     <mailto:dcaldwel AT nsf.gov>>
    >>     >> *Subject:* VERY IMPORTANT
    >>     >> *Importance:* High
    >>     >> Dear Mike and Anders
    >>     >> Would each of you please send me, by 9AM Friday morning, your
    >>     immediate assessment of the impacts on the ATLAS or CMS MREFC
    >>     program of the CERN schedule delay? Please provide a summary, by
    >>     level 2 WBS element, of what you believe this impacts to be, or if
    >>     there are none.
    >>     >> Please also comment on the impacts, by Level 2 WBS, of the
    >>     impacts if there were to be a one-year delay in the start of MREFC
    >>     funding. Include the risks or standing army costs of engineer and
    >>     technician labor, or other negative impacts of NSF funding delay.
    >>     Im assuming the risk of losing key technical staff in your
    >>     engineering pool that would otherwise move to other projects at
    >>     the various universities is a big factor.
    >>     >> Please provide a summary description of the process that ATLAS
    >>     and CMS, at the international level, will implement (or that you
    >>     anticipate they will implement) to realign their construction
    >>     programs, and any knock-on effects on NSF.
    >>     >> Please try to keep this at a concise summary level so that the
    >>     whole response is about one page for each detector.
    >>     >> I expect to get a thousand hand wringing questions from various
    >>     high officials within NSF about this, as they hate surprises.
    >>     Obvviously you are having to react quickly to new information, so
    >>     it will be important to emphasize where the NSF program is
    >>     decoupled from other agency activities or the international
    >>     schedule, minimizing impacts, and where a delayed start by NSF
    >>     would nevertheless be damaging to NSF-supported scientists and
    >>     their opportunities to participate in the HL LHC program.
    >>     >> Email if you have more questions. Our goal here at NSF is to
    >>     put out a three page summary by COB Friday, one page from NSF
    >>     internal evaluation, one page from ATLAS, and one from CMS.
    >>     >> The delay information we’ve seen here at NSF was blamed on the
    >>     need for a long detector fabrication schedule. What is driving it?
    >>     >> Thanks
    >>     >> Mark
    >>     >> _______________________________________________
    >>     >> 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://urldefense.com/v3/__https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l__;!!C5qS4YX3!Xev7P0lg11r1uuKZqpmcW-3ngbM0I423yHYW1d8Xc-gz37u_ym5WF8_friwwxsRb8T8$
    >>
    >>     >
    >>     > --
    >>     >
    >>     
______________________________________________________________________
    >>     >
    >>     > John Parsons
    >>     > Nevis Labs,           Email: parsons AT nevis.columbia.edu
    >>     <mailto: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=DwID-g&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=Z0wuTxQYnTTMlYma4lGZlO3skeCGVBrGGurYkWbhJsJuG5HaY82rmCNSdFOV7C4Z&m=iGs3hVDY7I8x8431V5EUhE-U8067DiiBCuW0wQcPfNA&s=IVwIexqfUeKKouYh65z7vIsZw2E6e_D-oxa6lK9qwlc&e=
    >>
    >>     >
    >>     >
    >>     
______________________________________________________________________
    >>     > _______________________________________________
    >>     > 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://urldefense.com/v3/__https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l__;!!C5qS4YX3!Xev7P0lg11r1uuKZqpmcW-3ngbM0I423yHYW1d8Xc-gz37u_ym5WF8_friwwxsRb8T8$
    >>
    >>
    >>     _______________________________________________
    >>     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://urldefense.com/v3/__https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l__;!!C5qS4YX3!Xev7P0lg11r1uuKZqpmcW-3ngbM0I423yHYW1d8Xc-gz37u_ym5WF8_friwwxsRb8T8$
    >>
    >>
    > 
    
    -- 
    ______________________________________________________________________
    
    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=7W7XV5YqVcU3cM2o6UEwWxMsIDNJu8EwwM0aFYBPF4w&s=AHnjASh-Jz9DMCi0LUGJbqmeotIRy85YR7-tUuwCgWY&e=
    
    
    ______________________________________________________________________
    _______________________________________________
    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