Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Mark Coles -- NSF feedback to ATLAS on CMS on Directors Review

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: usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
  • Subject: Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Mark Coles -- NSF feedback to ATLAS on CMS on Directors Review
  • Date: Thu, 18 Jul 2019 10:48:17 +0200


Hi,


I think that this is another case of inconsistent language from the NSF. If we have eliminated all technological risks then we wouldn't need a Risk Register. As I read the RR, this risk (RN-06-04-01-002) has an expected expiration of 01-Jun-2020. So we are taking this risk into account in the MREFC contingency calculation, right?

I disagree. You can eliminate all technological risk and still need a risk register. The basic message is that we've done the R&D necessary to prove that we will be able to build something that meets the specs. However, the exact implementation might yet change wrt our current thinking. That's what uncertainties and risk cover.

Every statement from NSF around the "construction read" indicates that what they mean is that you know you'll be able to meet the spec.

Best,

Gustaaf




Archive powered by MHonArc 2.6.24.

Top of Page