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

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

Hi Hong, all,

        I would not change tasks completed in the
past (apart perhaps from modifying their description
a bit in cases where that seems important).  We
should remove tasks that will not be done (eg.
radn testing of HLC1).
        Yes, we will arrange "one-on-one" mtgs
to update the RLS.  To start, I worked with Amy
to put in the modified PA/S submissions, to see
the ripple to other systems.  We will get a new
Scrubbing Report with this "what if" scenario.
In the meantime, you can figure out what to
shorten to meet those agreed upon dates. We
are focusing for now just on the pre-MREFC
period, namely up to Apr. 1/2020, so it is not
so complicated to figure out what needs to
be done.
                John

On 10/9/18 5:47 PM, Ma, Hong wrote:
>         A couple of questions on updating the RLS.
>
>         Do we need to change the past to make it look more like the actual we 
> have just reported in the status report?  I hope the actual is OK to be 
> different from the new RLS, even for the past.
>         
>         I know more or less what to change (stretch some tasks and shorten 
> the others).  Would it be better if we sit with the project control (Amy or 
> Heidi) to make the changes in P6, and check the results in real time?   I am 
> not sure if we can clearly write down what we want to change on the 
> spreadsheet.
>
>         Hong.
>
>
> On 10/9/18, 2:24 PM, "Usatlas-hllhc-lartl2l3-l on behalf of John Parsons" 
> <usatlas-hllhc-lartl2l3-l-bounces AT lists.bnl.gov on behalf of 
> parsons AT nevis.columbia.edu> wrote:
>
>      
>      Hi all,
>      
>      	Just to let you know that I tried
>      uploading to docdb #614 using the
>      "Add Files" button and it was in fact
>      very simple.
>         Regards,
>                 John
>      
>      On 10/8/18 9:46 PM, John Parsons wrote:
>      >
>      > Hi all,
>      >
>      >      A reminder of our mtg tomorrow
>      > at 1 pm.  Before the mtg, each L3 should upload
>      > to indico a copy of their filled out status
>      > report.
>      >
>      >          John
>      >
>      > On 10/4/18 10:13 AM, John Parsons wrote:
>      >>
>      >> Hi all,
>      >>
>      >>      As you all know, we need to fill out the
>      >> September status report asap.  It was officially
>      >> due tomorrow, but there has been a lot of confusion
>      >> so I was awaiting clarification about the procedure.
>      >> After yesterday's CCB mtg, we are now ready to go ahead.
>      >> Please do this asap and send it to me, and we
>      >> will go over the spreadsheets in our next weekly
>      >> mtg (ie. Tues. Oct. 9).
>      >>
>      >>      I attach a new version of the
>      >> statusing spreadsheet that needs to be
>      >> filled out (new since the original version
>      >> incorrectly left out most of our previous
>      >> status reports, and this has now been
>      >> corrected). Those of you who could attend
>      >> yesterday's CCB heard extensive
>      >> discussions about what is needed.  In any
>      >> case, I give a summary of the instructions
>      >> and some comments below:
>      >>
>      >> 1. note that we statusing against the
>      >> EXISTING RLS.  Once we are done with this,
>      >> we will turn back to the task of updating the
>      >> RLS to match the current reality.  However,
>      >> for this statusing exercise, simply report
>      >> as best you can against the current RLS,
>      >> as represented in the attached spreadsheet.
>      >>
>      >> 2. changes are to be made ONLY to columns
>      >> K, L, M and N.  All other fields should
>      >> be left untouched.  Also, please use RED
>      >> FONT for any entries you enter or change,
>      >> so that they can be readily identified
>      >>
>      >> 3. first, check the existing entries in
>      >> columns K-N against what you have
>      >> previously reported, and let me know
>      >> right away if you find any errors.
>      >>      (Note that the TileCAL people
>      >> have reported some discrepancies when they
>      >> did this check, so we better do it also
>      >> this time.  Hopefully the tools will
>      >> improve and we will not need to do
>      >> this check in the future.)
>      >>
>      >> 4. for each task in your area that
>      >> was EXPECTED to start before Sept. 30/18,
>      >> you need to fill out columns K-N as
>      >> appropriate:
>      >>      - if a task has been COMPLETED,
>      >> enter 1.00 in Column K (% Complete),
>      >> and the Actual Start and Actual Finish
>      >> dates in columns L and M, respectively.
>      >> If you don't know the exact dates,
>      >> enter your best approximation.
>      >>      - if a task has been STARTED
>      >> but not completed,
>      >> enter your estimate of the % complete in
>      >> Column K,the Actual Start date in
>      >> column L, and your estimate of
>      >> the expected Finish date in column N.
>      >>      - if a task has NOT BEEN STARTED,
>      >> enter your estimate of
>      >> the expected Finish date in column N.
>      >>
>      >> 5. for any tasks expected to start
>      >> AFTER Sept. 30/2018, you can leave that
>      >> row untouched.  Of course, if the work
>      >> has in fact started (ie. ahead of schedule),
>      >> then provide the entries as described
>      >> above in point 4.
>      >>
>      >>      I hope this is clear.  This should
>      >> not be onerous, and should take less than
>      >> an hour of your time (otherwise you are
>      >> over-thinking it!). So, please do it asap
>      >> and send it to me by the end of next Monday
>      >> at the latest, so that we can all go
>      >> over everything on Tuesday.  If you have
>      >> any questions or encounter any problems,
>      >> let me know right away.
>      >>
>      >>      The indico for next Tuesday has been
>      >> created at https://indico.bnl.gov/event/5158/.
>      >> As stated, we will go over the status reports
>      >> and also discuss the next steps as we move fwd.
>      >>
>      >>      Regards,
>      >>          John
>      >>
>      >
>      
>      --
>      ______________________________________________________________________
>      
>      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: http://www.nevis.columbia.edu/~parsons/  
>   
>      
>      ______________________________________________________________________
>      _______________________________________________
>      Usatlas-hllhc-lartl2l3-l mailing list
>      Usatlas-hllhc-lartl2l3-l AT lists.bnl.gov
>      https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-lartl2l3-l
>      

--
______________________________________________________________________

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: http://www.nevis.columbia.edu/~parsons/    

______________________________________________________________________