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
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing
- From: John Parsons <parsons AT nevis.columbia.edu>
- To: Tim Andeen <timothy.robert.andeen AT cern.ch>
- Cc: "usatlas-hllhc-lartl2l3-l AT lists.bnl.gov" <usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
- Subject: Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing
- Date: Wed, 19 Jun 2019 14:26:58 -0400
Hi Tim,
I give some comments/suggestions below.
John
p. 6 - we discussed yesterday that the Mitigation should
make clear the baseline has 5 iterations of the ADC
(3 preproto, 1 proto, 1 (pre)prod) - ie. along the
lines of what you have on p. 7
- also, in Comments, get rid of DRE and
calibration-free SAR specifics, and just say
"ADC development faces challenging specifications."
- would be better to say "in the event that
the prototype fails to meet the specifications".
Also, expiration date should not be until ~3 months
AFTER successful FDR, so 7/31/2021 roughly
p. 8 - where does assumption of 5k devices for Proto
come from? you mean pre-prod?
p. 9 - since you assume 12.5%/shipment, does not make
sense to say get 6% spares to "cover any losses"
p. 10 - can you make "comment" more quantitative
about the numbers?
p. 11 - "mitigation" is something in your baseline,
ie. that you are already doing (or planning). If
you find later you need to add personnel, you cannot
consider that "mitigation", but "response".
You need to re-think this sheet. (take a look
at my p. 11 to see an example)
p. 14 - date should be 4/22? (like on p. 15)
p. 16 - similar comments as p. 11
On 6/19/19 9:43 AM, John Parsons wrote:
Very good, I will try take a look if I can find time.
I will update mine today and move them there also.
Everyone else should do the same, getting them to
Friday's agenda page by the end of today at the
latest.
A few summaries from our discussions yesterday:
- in addition to addressing particular suggestions
from yesterday, everyone should check the expiration
dates and comments fields.
I suggest to put the expiration dates
about 3 months after the corresponding task or milestone
(eg. a review) in the latest version of the Scrubbing Report
(which I posted to Friday's agenda).
Edit the comments field to provide some
traceability of the numbers, in particular the cost
range and schedule range.
- Hong should add a "Shipping loss" risk, similar to what
Tim has added for the other ASICs.
- Andy, I think you should do the same for shipping
the sRTMs to CERN
Regards,
John
On 6/19/19 9:20 AM, Tim Andeen wrote:
Hi John,
I updated my slides from yesterday's discussion and posted them to the Friday agenda: https://indico.bnl.gov/event/6285/contributions/29044/attachments/23339/33760/L3-LArFEE-6.4.1_RiskScrubbing_v2.pdf
I'm alone there, was I supposed to wait? I added details in the comments sections, fixed typos and made corrections following your suggestions, and added a shipping risk.
Best, Tim
On Thu, Jun 13, 2019 at 10:45 PM John Parsons <parsons AT nevis.columbia.edu <mailto:parsons AT nevis.columbia.edu>> wrote:
Hi all,
A reminder that our Risk Scrubbing will take place
on Fri. June 21 beginning at 9 am NY time. Gustaaf created
an indico page at https://indico.bnl.gov/event/6285/. I
modified it to add the DOE L3s; I don't know if there will
be time to go through both NSF and DOE, but as we discussed
we should prepare everything now so that we can ensure things
are coherent across both NSF and DOE.
Everyone should prepare their slides before our regular
meeting next Tuesday, and post your slides to that agenda page
(which is at https://indico.bnl.gov/event/6292/). We will go
over the slides together on Tuesday, after which we will
provide them to the PMO to get some feedback even before next
Friday's scrubbing meeting.
Examples from the recent muon scrubbing are available
at https://indico.bnl.gov/event/6282/. I suggest people take
a quick look through the slides to get ideas for preparing
their own slides.
Regards,
John
-- ______________________________________________________________________
John Parsons
Nevis Labs, Email: parsons AT nevis.columbia.edu
<mailto: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=DwICaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=DSVO6Re8kg14S-cQbkBC2zfSx6Yt2GtkcD3fTWOeyfXXTwIA3TKWV-phDKykUKDr&m=LqDdPgkXB56pbreyF0TXW5QZDMF00et1OX_CG7uLhUA&s=ulkRw7G2-IPtbDgMSgNyvUoEt2ArYoDYTLGczgumgDc&e=
______________________________________________________________________
_______________________________________________
Usatlas-hllhc-lartl2l3-l mailing list
Usatlas-hllhc-lartl2l3-l AT lists.bnl.gov
<mailto:Usatlas-hllhc-lartl2l3-l AT lists.bnl.gov>
https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-lartl2l3-l
--
---------------
Tim Andeen
Assistant Professor, Department of Physics
College of Natural Sciences
The University of Texas at Austin
Austin, TX 78712-1192
web: tandeen.web.cern.ch <http://tandeen.web.cern.ch>
office (TX): PMA 10.208
office (CERN): 304/1-024
ph (TX): +1 512 475-9575
ph (CERN): +41 (0)22 76 758 14
email: tandeen AT utexas.edu <mailto:tandeen AT utexas.edu>
---------------
--
______________________________________________________________________
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=6iEUpS54yj0hiP41IB9BFb9juHBFb5HroMR-uDO0Cr8&s=S-xx6iFcZuLw-Amq1-ZLp50XDKO3Jk17-06BBj45wfY&e=
______________________________________________________________________
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing
, (continued)
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Tim Andeen, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Andy Haas, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Andy Haas, 06/19/2019
- Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing, John Parsons, 06/19/2019
- Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing, Ma, Hong, 06/19/2019
- Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing, Xu, Hao, 06/19/2019
- Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing, Ma, Hong, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Andy Haas, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Andy Haas, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
Tim Andeen, 06/19/2019
-
Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing,
John Parsons, 06/19/2019
- Re: [Usatlas-hllhc-lartl2l3-l] examples for Risk Scrubbing, Tim Andeen, 06/20/2019
Archive powered by MHonArc 2.6.24.