[Pansophy] HE Cost Estimate for Cause Codes

[Valerie Bookwalter]

Anne,

Yesterday was really busy. Here are the time estimates.


  *   Data analysis - 4 weeks
  *   Upgrade NCR traveler - 8 weeks
  *   Move all travelers to new revision  - 2 weeks
  *   Open all travelers - 1 week
  *   Update/New Reports - 8 weeks

I will leave all the estimates for Ashley and ENGR times to you.
Please note that these times would be hours needed to do the work,
but do not reflect the calendar time line as we have many other projects going on that have priority.

Valerie Bookwalter
Jefferson Lab, ACC
SRF Operations
SRFOPS Software Systems Group
1-757-269-5802 (OFFICE - currently working offsite)


From: E. Anne McEwen <mcewen at jlab.org>
Sent: Tuesday, October 10, 2023 11:28 AM
To: Valerie Bookwalter <bookwalt at jlab.org>
Cc: Ashley Mitchell <ashleya at jlab.org>
Subject: HE Cost Estimate for Cause Codes

Hi Valerie

To follow up on our conversation .

I am looking to do a cost estimate on work that the Pansophy team might be asked to do - Please do not start anything until the Project actually decides to do this

Could you tell me the approximate number of hours for the following


  1.  Approx. Hours for a Comp Sci to add the following to all HE Travelers

  *   Add count of how many defects are not assigned to the Pareto so there is a full picture
  *   Add feature so in future the traveler cannot be closed without defect code assigned (I know you are planning to do this anyway - could you give me an idea of when this feature might be in all the travelers) ?


  1.  Approx. Hours to add a revision to the traveler that would include a new section at the end with 5 check boxes, where the engineer would be required to check a cause code before closing the traveler



  1.  Approx.. Hours to reopen all NCRs travelers so that the engineer could update all NCRs with defect codes (where missing) and Cause codes)



  1.  Update the down load report  for HE


Other things that would have to be added to the cost file

  1.  Time for Ashley to write a new procedure (perhaps a week)
  2.  Training for Engineers
  3.  Time for an engineer to update all HE travelers with Cause Codes (perhaps 2-3 hours per traveler - would depend on the complexity of the problem

In the longer term we may decide and an organization that we want to include the same cause codes as Fermi in our travelers - but we would do all we can to push this off to the next project - and not try to go back on the HE Project

We continue to do everything possible to dissuade HE- but if we are forced to do it in the end , it would be useful to have in our pocket an idea of the schedule and cost impact

I am guessing it would be 6 months at least .

Once again - PLEASE do not actually start any work on this

Thanks Anne

_______________________________________________________________________________
E. Anne McEwen
JSA / Jefferson Lab
SRF Institute
Newport News, VA 23606
Office: +1 (757) 269-5539
Email:   mcewen at jlab.org<mailto:mcewen at jlab.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20231011/7907d933/attachment.html>