Skip to Content.
Sympa Menu

usatlas-hllhc-lartl2l3-l - [Usatlas-hllhc-lartl2l3-l] LAr DOE risk scrubbing summary

usatlas-hllhc-lartl2l3-l AT lists.bnl.gov

Subject: U.S. ATLAS HL-LHC Upgrade LAr Level 2 and Level 3 Managers Mailing List

List archive

Chronological Thread  
  • From: John Parsons <parsons AT nevis.columbia.edu>
  • To: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>, "usatlas-hllhc-management-l AT lists.bnl.gov" <usatlas-hllhc-management-l AT lists.bnl.gov>, "usatlas-hllhc-lartl2l3-l AT lists.bnl.gov" <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
  • Subject: [Usatlas-hllhc-lartl2l3-l] LAr DOE risk scrubbing summary
  • Date: Tue, 26 Nov 2019 12:59:37 -0500


Hi all,

Thanks to everyone for the help with today's scrubbing of the risks in the LAr DOE scope. I give below my notes. Comments/corrections are welcome.

John


General remarks (applicable to all risks)
------------------------------------------
- revisit and improve Comments fields to more quantitatively address cost and schedule ranges for impact
- many (most) probability categories need to be cleaned up, in part due to the ongoing transition from prob. to categories for the DOE scope


PA/Shaper
----------

RD-06-04-05-004 (Analog Performance Issues)
- Low
- increase HI cost impact to $500k

RD-06-04-05-005 (ASIC Yield)
- Low

RD-06-04-05-006 (External Dependency)
- Very Low

RD-06-04-05-007 (Loss of key personnel)
- Low

RD-06-04-05-008 (Increased complexity)
- Moderate Low
- rewrite to make risk more broad, ie. to cover increased complexity in entire development, from current prototyping through testing

RD-06-04-05-009 (Shipping loss)
- Very Low
- typo. - change Ensure to Insure



System Integration
RD-06-04-04-001 (FE crate system integration delayed)
- split into 2 risks, one on "External deliverables delayed or not meeting specifications" and the other on "Increased complexity in FE system integration". the second would be similar to the current RD-06-04-04-004 (Increased Complexity for BE integration)
- we did not specify, but I would propose Moderate Low for both of the FE risks

RD-06-04-04-002 (BE crate system integration delayed)
- as above for FE, have one risk just for "External deliverables delayed or not meeting specifications", and absorb the rest into the existing RD-06-04-04-004
- again we did not specify, but I would again propose Moderate Low for both of the BE risks (we could try argue the BE is simpler, with fewer deliverables etc., and so perhaps one or more could be Low. However it is not so clear to me how convincing that would be.)

RD-06-04-04-003 (Loss of key personnel)
- Low
- we agreed we should focus just on BNL personnel here, as is indeed currently done
- we also agreed we would NOT add an explicit risk for "External dependencies"

RD-06-04-04-004 (Increased complexity in BE integration)
- see comments above
- consider whether HI cost impact of $120k is sufficient
- wording: change "increase one or two engineering efforts" to "increase engineering effort by 1-2 FTE"


On 11/25/19 11:04 AM, John Parsons wrote:

Here it is: https://indico.bnl.gov/event/7133/.

Hong/Hao, you should upload your slides.

        John

On 11/25/19 4:37 PM, Gustaaf Brooijmans wrote:

Hi,

A reminder that we have the LAr risk scrubbing tomorrow at 11. John/Hong, can you prepare an indico page?

Thx

Gustaaf



--
______________________________________________________________________

John Parsons
Nevis Labs, Email: parsons AT nevis.columbia.edu
Columbia University Phone: (914) 591-2820
P.O. Box 137 Fax: (914) 591-8120
Irvington, NY 10533 WWW:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.nevis.columbia.edu_-7Eparsons_&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=DSVO6Re8kg14S-cQbkBC2zfSx6Yt2GtkcD3fTWOeyfXXTwIA3TKWV-phDKykUKDr&m=ORoIwXaEgJlMwDMqrK5dOfU2aVFzizdI13oe75uxMYI&s=VLm0xajxiIgqOWnRNuxHaFoAzBKUHfhvxXNO4750_CE&e=


______________________________________________________________________




Archive powered by MHonArc 2.6.24.

Top of Page