Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - [Usatlas-hllhc-l2deputymgmt-nsf-l] July Variance Reports

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: [Usatlas-hllhc-l2deputymgmt-nsf-l] July Variance Reports
  • Date: Tue, 23 Aug 2022 11:53:23 +0200


Hello all,

Thanks for filling out the variance reports on time.  A few comments below.

Thanks,

Gustaaf

-6.4.1  in my view only cumulative schedule is required:
Threshold(s) Exceeded: Cumulative Schedule

This may be a rounding effect, so it’s probably best to to report on this, but the positive $350k must be balanced by a negative $150k, so that would also need to be explained.  (We have seen one case where something showed up red for one person but not the other - it may be browser-dependent…)

-6.4.2/3 are ok.  (I do suggest in the future to write something more polished than “there will be extra money”.)

-6.5.3: Just FYI I’m not sure we will rebaseline non-COVID issues, so this variance may remain until the end of the project.

-6.6 and 6.6.3 are fine

-6.6.4: at the end of the corrective action I might add: “a BCP to address to likely delay to the production part of the schedule.” (to make clear the intention is not to “fix the past”)

-6.6.5 looks good

-6.8 is missing

-6.8.3 and 6.10.2 look fine to me.




Archive powered by MHonArc 2.6.24.

Top of Page