Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [Us-atlas-hllhc-pmgmt-l] Answers to NSF questions re BCP 1033 and updated addendum text

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: John Parsons <parsons AT nevis.columbia.edu>, Michael Tuts <tuts AT pmtuts.net>, "us-atlas-hllhc-pmgmt-l AT lists.bnl.gov" <us-atlas-hllhc-pmgmt-l AT lists.bnl.gov>, "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] [Us-atlas-hllhc-pmgmt-l] Answers to NSF questions re BCP 1033 and updated addendum text
  • Date: Wed, 6 Jan 2021 20:34:31 +0100


Good. Then you just need an explanation for why you didn't take that labor from the future work that will now need to add less functionality. (We don't need to document it now, but you'll need it when this gets audited.)

Best,

Gustaaf

On 1/6/21 8:21 PM, John Parsons wrote:

As I discussed with Mike on the phone, I would say this is not a scope increase, but is just including more of the final required functionality at an earlier stage of the prototyping.  That provides mitigation against the usual "increased complexity" risk we include in the RR, by getting to see earlier what sort of problems we might encounter when we scale up to the full channel count.

        John

On 1/6/21 8:41 AM, Michael Tuts wrote:
Good point, let's see what they say...

-----Original Message-----
From: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>
Sent: Wednesday, January 6, 2021 8:15 AM
To: Michael Tuts <tuts AT pmtuts.net>; us-atlas-hllhc-pmgmt-l AT lists.bnl.gov; usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
Subject: Re: [Us-atlas-hllhc-pmgmt-l] Answers to NSF questions re BCP 1033 and updated addendum text


Hi Mike, all,

Regarding:

6.4.1 Optical Link Development:
The following statement seems to be enhancement due to the opportunity from delay.  “Given the extended design time, the functionality was expanded so that more information can be learned once testing can begin.”  Was this additional effort included in this BCP?  The justification should make that clear.
Answer: Yes, this additional effort was included in the BCP. We have added language in the Addendum to make that clear.

==> The issue is that this is then a scope increase.  That’s explicitly not allowed in the BCP.  This scope increase will probably need to be separated out.  Let's see what NSF says.

Best,

Gustaaf

On 1/6/21 1:42 PM, Michael Tuts wrote:
Hi All,

Attached are the answers to the questions NSF raised regarding the
narrative text to accompany the BCP information (the addendum which is
also attached). The responses have been incorporated into the addendum
text (as well as some earlier comments). We will present this to NSF
today at our 10am chat with them, and hopefully that is what they need
to sign-off on the COVID BCP 1033. If you have any last minute
comments/corrections, let me know asap.

Thanks, Mike



_______________________________________________
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