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

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

Andy and Hao need to fill out the BCP forms.  Please do this right
away, since we need to get the approval on Tuesday.

                John


-------- Forwarded Message --------
Subject: Re: AP2 LAr 6.04 BCPs DOE-023 and NSF-1102
Date: Fri, 1 Nov 2019 10:48:00 +0100
From: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>
To: John Parsons <parsons AT nevis.columbia.edu>, Novakova, Penka N 
<penka AT bnl.gov>, OConnor, Jennifer <jennifer AT bnl.gov>
CC: Hong Ma <hma AT bnl.gov>


Hi,

Great.  Can you have the L3 managers fill out the BCP forms?  Here's the 
latest template.

Best,

Gustaaf

On 10/31/19 8:57 PM, John Parsons wrote:
> Hi all,
>
>      Apart from some very minor things that do not
> need to be changed now, I have not found nor heard
> from my LAr team of any other issues with the current version.
> So, I consider that these two BCPs (ie. one for DOE and
> one for NSF) are ready to move ahead next week.
>      Regards,
>          John
>
> On 10/29/19 5:04 PM, John Parsons wrote:
> > Hi Penka,
> >
> >      Thanks for the help.  I do believe it will be worth
> > some effort to evolve the new format so that it does include
> > the milestones.  For example, in LAr, all of our links between
> > separate L3s, including within one funding agency but also
> > between DOE and NSF, are implemented via (REQD and AVAIL)
> > milestones; if those are missing in a report, it is difficult
> > to follow the logic about how one L3 might be driving another, ...
> >      We are reviewing the latest version to verify
> > that all the changes we have made are doing what we
> > expect, and hope to be ready for next week's CCB.  I
> > will update you by COB on Thursday.
> >      Regards,
> >          John
> >
> > On 10/29/19 1:11 PM, Novakova, Penka N wrote:
> > > John,
> > > The pdf report has all activities and milestones that have been 
> > > changed. It is definitely easier to review your change in the pdf - 
> > > it shows how the dates have moved. Please call me or Jenn and we can 
> > > walk you through the schedule.
> > > My philosophy is that the CAMs should be able to read their schedules 
> > > (not spreadsheets) and understand what changes they have requested 
> > > and how these changes impact the schedules of other CAMs. Perhaps we 
> > > need to train them but this is critical for the success of the project.
> > > I have made a report with all activities and milestones - it took me 
> > > a while to generate it. Again remember that in the scrubbing report 
> > > you don't see the number of hours by resource and many CAMs have 
> > > complained about this. Therefore we decided to move to a new format 
> > > that will have this information but does not show activities without 
> > > resources (milestones).
> > > We will try to make this report with milestones in the future but I 
> > > cannot guarantee that it will be available right after the change is 
> > > complete.
> > > Let me know if you have any questions.
> > > Thanks,
> > > penka
> > >
> > >
> > > -----Original Message-----
> > > From: John Parsons <parsons AT nevis.columbia.edu>
> > > Sent: Tuesday, October 29, 2019 11:19 AM
> > > To: OConnor, Jennifer <jennifer AT bnl.gov>; Novakova, Penka N 
> > > <penka AT bnl.gov>
> > > Cc: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>
> > > Subject: Re: AP2 LAr 6.04 BCPs DOE-023 and NSF-1102
> > >
> > >
> > > Our previous Scrubbing Reports had all the tasks; why is that no 
> > > longer possible?  It is much simpler to check a single file, rather 
> > > than having to cross-check back and forth between two different files.
> > >
> > >         John
> > >
> > > On 10/29/19 7:41 AM, OConnor, Jennifer wrote:
> > > > Hi John -
> > > >
> > > > You are correct, the scrubbing report does not contain all 
> > > > activities.  That is because this report comes from Cobra data and 
> > > > we do not have milestones or activities with no resources in Cobra.  
> > > > The PDF is a complete schedule showing all activities.  Both need to 
> > > > be used to compare BCP changes.
> > > >
> > > > Please let me know if you need any help comparing the changes we made.
> > > >
> > > > Kind regards,
> > > > Jenn
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: John Parsons <parsons AT nevis.columbia.edu>
> > > > Sent: Monday, October 28, 2019 11:50 AM
> > > > To: Novakova, Penka N <penka AT bnl.gov>; OConnor, Jennifer
> > > > <jennifer AT bnl.gov>
> > > > Cc: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>; Hal Evans
> > > > (hgevans AT indiana.edu) <hgevans AT indiana.edu>; Kotcher, Jonathan
> > > > <kotcher AT bnl.gov>
> > > > Subject: Re: AP2 LAr 6.04 BCPs DOE-023 and NSF-1102
> > > >
> > > >
> > > > There seem to be some problems with this report.  Among the 
> > > > modifications I made with Jenn last week were logic changes around 
> > > > task BEE10680 (ATLAS FDR); now that task does not even seem to 
> > > > appear in the new report!  This is also true for some nearby tasks.
> > > >
> > > > Maybe all the milestones are missing?
> > > >
> > > >         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: 
> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.nevis.columbia.edu_-7Eparsons_&d=DwICaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=UENrYTOIs8Bh1NYw40_P-g&m=Ym-P9-D0391m6RguT_tibyKgRwiY58OCq7k6eDKi1l0&s=9SLjGhgphUqFQHnTUKZPHkNu9C99ypWHFDIlFf948sQ&e= 
> > >
> > >
> > > ______________________________________________________________________

--
Gustaaf Brooijmans - Columbia University
@Columbia: (212) 854 4527; Nevis virtual phone: (914) 591 2804

Als sie mich holten,
gab es keinen mehr, der protestieren konnte.

Attachment: BCP US ATLAS HL-LHC Upgrade Template v6.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document