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
Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts
- From: Michael Tuts <tuts AT pmtuts.net>
- To: "Coles, Mark W." <mcoles AT nsf.gov>
- Cc: "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] [EXTERNAL] - The choreography of the Cost & Schedule breakouts
- Date: Wed, 5 Apr 2023 22:31:46 +0000
Hi Mark, Indeed getting committee feedback would be very helpful. For example the Tile C&S could likely be shorter. We also put Trigger in the afternoon so it could take more time at the expense of executive session (maybe that is not needed?). Please let us know how much time you think they will want for EFT C&S.
A heads up. We originally thought the cost & schedule would be drilldown flavor, i.e. open documents at the direction of the C&S, but on reflection we added some cost & schedule slides to the back end of the L3 breakout talks. That is not yet complete, (should be done by Friday, but can let you know if done earlier, I know Tile is done). So just a warning if the committee is looking at the breakout slides now they will probably change with that extra information at the end of the talk.
Cheers, Mike
From: Coles, Mark W. <mcoles AT nsf.gov>
Hi Mike
I will share this with the committee to ask for their feedback. The cost and schedule folks are the same ones that participated in the CMS rebaselining, so their experience with what worked at that review will be valuable.
I have one concern though, and this is about the EFT. I think you will get a question from the panel on Monday asking you to describe the estimation methods and provide the basis of estimate calculations for the EFT budget and schedule. That’s new since FDR, and unless I missed it the documentation you provided does not have this material. The EFT review may take more time than just the drill-down on the cost book that was part of the CMS rebaselining. And software is harder to plan and manage too, so the discussion is likely to take longer than for the other areas.
Mark
From: Michael Tuts <tuts AT pmtuts.net>
Hi Mark,
We have been thinking of how best to handle the Subsystem breakouts and the Cost & Schedule breakouts on Day 2. Our current thinking is as follows, and I wanted to get your (and the committee) feedback to see if this would work.
Then you can decide whether the management reviewers wish to remain after 10:30 with the ATLAS project management team in the Science Center for further breakout (or maybe they want to travel to the subsystems?). We can of course tweak the times if the C&S 1-hour slot is too much/little (or needs to be changed according to subsystem) – we leave that to the reviewers to establish beforehand, perhaps once they have a feel for the various subsystems.
Your thoughts? We thought this the most efficient way to achieve the breakout goals with all ATLAS experts available for both the subsystem breakout and the C&S breakout.
Thanks, Mike
|
-
[Usatlas-hllhc-l2deputymgmt-nsf-l] The choreography of the Cost & Schedule breakouts,
Michael Tuts, 04/04/2023
-
Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts,
Coles, Mark W., 04/05/2023
- Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [Us-atlas-hllhc-pmgmt-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts, Gustaaf Brooijmans, 04/05/2023
-
Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts,
Michael Tuts, 04/05/2023
- Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts, Coles, Mark W., 04/06/2023
-
Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] [EXTERNAL] - The choreography of the Cost & Schedule breakouts,
Coles, Mark W., 04/05/2023
Archive powered by MHonArc 2.6.24.