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

[John Parsons <parsons AT nevis.columbia.edu>]

Hi all,

        I give below my notes from the risk scrubbing.
While some of the comments are specific, many of them
apply to all of our sections.  You also received comments
from Hal, so look at those as well.

        As the next step, we urgently need to get George
everything he needs to run the simulation, so that we
know where things stand.  To do so, he needs all the
numbers, as well as the TaskID of the affected task
(ie. where the MC would insert the branch is trials
where a particular risk is realized) So work on finalizing
these things first.  I would like to get all that to
George by COB Monday.
        In addition, we need to update various text,
particularly in the Comments field.  That is (a bit)
less urgent, since the descriptive text is not used in
the MC.  I would like to go over any remaining issues
or questions during our mtg on Tuesday, so try finish
everything before then.
        Regards,
                John

Notes from Risk Scrubbing

General comment for everyone
        - check the TaskID of the affected task, since some
are out of date and need to be updated
        - the "Increased complexity" task should have zero
schedule impact.  The upper bound on the cost impact should
be the labor cost of one iteration, as expressed in your
baseline RLS
        - update Comments field as necessary to explain
the cost and schedule ranges used.  Keep in mind you
should address BOTH the lower and upper bounds of these
two ranges

Add'l comments for Tim
p. 7 - shift date to after start of MREFC

p. 9 - Austin in title and summary

p. 11 - 2% probability

- combine 12 and 13, and rewrite (also p. 14) to make more general
(ie. "CERN deliverables" or something like that)

p. 14 - remove "erorrs/glitches"

p. 15 - SMU in title and summary

p. 16 - rephrase as "architecture", not just testing



Add'l comments for Andy
p. 1 - include system block diagram

p. 2 - include delays only once
        - put key personnel in prototype
        - rephrase "mezzanine" (on a few slides)

p. 3 - rephrase as extra iteration

p. 4 - you mention variety of responses. Explain what you assume
in Comments about number ranges

p. 5 - rephrase as additional iteration of firmware

p. 6 - "mezzanines"
        - add redesign of sRTM to response
        - could delete first sentence of Comments

p. 7+8 - combine into one personnel risk

p. 9 - remove additional iteration, since that covered elsewhere


Add'l comments for John
p. 5 - rephrase to avoid impression of people "doing nothing"

p. 6 - rephrase as additional iteration





--
______________________________________________________________________

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=DwICaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=DSVO6Re8kg14S-cQbkBC2zfSx6Yt2GtkcD3fTWOeyfXXTwIA3TKWV-phDKykUKDr&m=zxhIMw8oWSlt3Gqact0xPu65X0Ll3LJfm__8LdhhUsE&s=zPTrFPyyjzLoxRqr94OLjH_zOHsJAOeI9koHclhGS0g&e=
    

______________________________________________________________________