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

[Andy Haas <andy.haas AT nyu.edu>]

HI John,
So like we said:
   * *WBS*

6.4.3.2

   * *Deliverable*

LAr BE firmware specifications review

   * *Anticipated review date at this time (approx. is fine – i.e., month
     -- if not scheduled, but please note that)*

March 2020, approximately

   * *Whether or not it can carry on as scheduled under current
     circumstances (Y/N)*

N

   * *If not, the reason for the delay (access to
     hardware/demonstrations, TW limitations, international covid-related
     delays, etc.)*

Time was lost in transitioning to remote work practices / missed
meetings at CERN

   * *Your best guess as to a new estimate for the date (date, range,
     whatever makes most sense)*

June-Aug 2020

   * *Comments, if any*



On Wed, Apr 1, 2020 at 6:40 PM John Parsons <parsons AT nevis.columbia.edu> 
wrote:
>
>
> FYI, an additional request to the ongoing exercise about estimating the
> impact of COVID-19.
>
> -------- Forwarded Message --------
> Subject:        [Usatlas-hllhc-l2deputymgmt-l] ***One more request***
> Date:   Wed, 1 Apr 2020 21:53:18 +0000
> From:   Kotcher, Jonathan <kotcher AT bnl.gov>
> To:     usatlas-hllhc-l2deputymgmt-l AT lists.bnl.gov
> <usatlas-hllhc-l2deputymgmt-l AT lists.bnl.gov>
>
>
>
> All –
>
> After some of our discussions at the CCB, we would like to add an
> additional request related to covid-19 impacts to the project:  the
> effect of covid-19 measures being taken – TW only, no hands-on lab
> access, etc. – to the upcoming ATLAS review schedule for your
> deliverables (PDR, FDR, PRR, etc.). *For Friday’s submission, we’d like
> to ask that you include a list of the relevant ATLAS reviews anticipated
> to occur through January 2021, by deliverable, with the following
> information for each: *
>
> **
>
>    * *WBS*
>    * *Deliverable*
>    * *Anticipated review date at this time (approx. is fine – i.e., month
>      -- if not scheduled, but please note that)*
>    * *Whether or not it can carry on as scheduled under current
>      circumstances (Y/N)*
>    * *If not, the reason for the delay (access to
>      hardware/demonstrations, TW limitations, international covid-related
>      delays, etc.)*
>    * *Your best guess as to a new estimate for the date (date, range,
>      whatever makes most sense)*
>    * *Comments, if any*
>
> This in general can and will be influenced by the covid-related impacts
> being felt by our international collaborators, ATLAS review scheduling,
> pending technical decisions (i.e., pixel readout, TDAQ architecture),
> etc. which may be understood to varying degrees.  We recommend that you
> focus on the impact to work you are doing in your subsystems, but that
> you note (briefly) any knowledge you may have of internationally sourced
> impacts or other dependencies/uncertainties in the “reason for delay” or
> “comments” box.
>
> We’ve attached a spreadsheet to facilitate this for you – we hope this
> helps.  It should be reasonably straightforward to do. *Please target
> submission of this along with the other two requests by COB this Friday,
> 4/3 if you can, but no later than COB Monday, April 6.  Please be sure
> to cc Rhoumela (rfreedman AT bnl.gov <mailto:rfreedman AT bnl.gov>) on these
> responses, who will help us collate the information. *We will go over
> all of these responses with you once we’ve looked them over. **
>
> Many thanks – any questions, please just contact us –
>
> Best –
>
> Gustaaf, Hal, Jon, Penka, Mike
>
> _______________________________________________
> Usatlas-hllhc-lartl2l3-l mailing list
> Usatlas-hllhc-lartl2l3-l AT lists.bnl.gov
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.bnl.gov_mailman_listinfo_usatlas-2Dhllhc-2Dlartl2l3-2Dl&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=y4qQBOsjsdgJNx-_8SvpS9786vHE4GOddPXp1ozJgWc&m=H4_lkpsVIJGDIUqOxK3AqrjGMAwtb1YND3-SgtXKbUg&s=Ph7_Ieyf8hOPSQkVw_hVsBM9HAINlyFgAgbMinNmJb0&e=