Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Floats and scope contingency -- comments

usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov

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

List archive

Chronological Thread  
  • From: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>
  • To: Stephanie Majewski <smajewsk AT uoregon.edu>
  • Cc: Michael Tuts <tuts AT pmtuts.net>, "Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov" <Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov>
  • Subject: Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Floats and scope contingency -- comments
  • Date: Thu, 23 Feb 2023 20:14:31 -0500


Indeed - to reduce risk is much better, fixed.

I’ll update my float table as well.

On Feb 23, 2023, at 12:31 PM, Stephanie Majewski <smajewsk AT uoregon.edu> wrote:

@Mike: I’m fine with the language “to reduce risk” (or “to significantly reduce risk”).

@Gustaaf: A comment about the float for 6.8.1. Technically there are 2 floats within this L3 - one for FOX++ and one for fFOX. You are quoting the correct float for FOX++, but the float for fFOX is currently 132 days in the RLS after BCP-1057. I think it would be more appropriate to quote this float, since it is the later deliverable. We need to update the need-by date for the fFOX for the April Review - it is now later by over a year in the international schedule. This is on slide 19 of my L2 talk.

Stephanie


On Feb 23, 2023, at 8:39 AM, Michael Tuts <tuts AT pmtuts.net> wrote:

Hi Tom,
I see in the scope contingency #7 (chamber batch 8) has a decision date of Jan-23 (in the past!). Maybe it is still a viable option, but then the date needs to be updated.
 
<image001.png>
 
 
Hi Gustaaf, John, Stephanie,
 
In scope opportunity I see below – my concern is with the language for all three is that “to ensure project success” sure sounds like a red flag after we told them we can deliver 90% certainty!  Shouldn’t it me more along the lines of “to significantly reduce risk” (or maybe even “to add functionality” if that is true?)
 
<image002.png>
 
Cheers, Mike
 
From: Usatlas-hllhc-l2deputymgmt-nsf-l <usatlas-hllhc-l2deputymgmt-nsf-l-bounces AT lists.bnl.gov> On Behalf Of Gustaaf Brooijmans
Sent: Thursday, February 23, 2023 9:16 AM
To: Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
Subject: [Usatlas-hllhc-l2deputymgmt-nsf-l] Floats and scope contingency
 


Hello all,

Here’s a table with the floats, as far as I can tell.  Please check that we agree on these numbers.

The scope contingency table has been updated and is linked from the review webpage.  It’s at 

https://atlas-hllhc.docdb.bnl.gov/cgi-bin/private/ShowDocument?docid=969

Best,

Gustaaf

_______________________________________________
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
_______________________________________________
Usatlas-hllhc-l2deputymgmt-nsf-l mailing list
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!FCDfmcshWYxkeV-iDLy5PE99Fe3mYpuZBvhlb44ID_ga-4PIK7j28Ia9Z9rQXD9cmmTCkbHXXRSu4EHu$


_______________________________________________
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




Archive powered by MHonArc 2.6.24.

Top of Page