[Pansophy] J-29 NCRs

Wed May 7 09:49:12 EDT 2025

Morning,

I had a question from Jamie at FNAL - Will the traveler/spreadsheet include anything unique about this CM that our testing team should be aware of, or did we guys already go over that info with the folks there?

On the configuration notes tab, I have nothing unique on this CM.  Is that true? Do we need to pass on any information?
[cid:78ace2e8-7ef0-4aae-bf0b-0641db326a22]

Thanks!
- Ashley
________________________________
From: Ashley Mitchell <ashleya at jlab.org>
Sent: Tuesday, May 6, 2025 9:30 AM
To: John Vennekate <hannesv at jlab.org>; Adam Grabowski <adamg at jlab.org>; Peter Owen <powen at jlab.org>; John Fischer <fischer at jlab.org>; Gary Cheng <cheng at jlab.org>; Matt Weaks <weaksmc at jlab.org>; Michelle Oast <weinmann at jlab.org>; Michael Drury <drury at jlab.org>; David Savransky <dsavr at jlab.org>
Cc: Tony Reilly <areilly at jlab.org>; Mike Bevins <mbevins at jlab.org>; pansophy <pansophy at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: Re: J-29 NCRs

Morning,

Please review the spreadsheet of NCRs I compiled, if any NCR travelers need to be modified, submit a service request in Pansophy. (I haven't updated it, if you already made changes since I sent on 4/28, this does not reflect those.)

John V, I saw your email, I cannot make changes to NCRs, you'll need to submit a request to have them opened and make the changes or add more information yourself.

Please complete these ASAP as the CM J-29 leaves today.

Thank you,
- Ashley
________________________________
From: John Vennekate <hannesv at jlab.org>
Sent: Tuesday, April 29, 2025 10:56 AM
To: Ashley Mitchell <ashleya at jlab.org>
Subject: RE: J-29 NCRs

Morning Ashley,

Thanks for the nice summary! Let me list some comments/questions below going by the NCR number:

  *   303 – requested edit
  *   394 – that’s a tricky one. The NCR correctly documents that we returned the cavity to the vendor. SLAC (and I) referred to it as 078_RT after that repair and it went through all inspections including vertical test to be qualified for string J29. I made the suggestion to update the serial number in the system as we are treating it as a new cavity. This was rejected however, with argument of maintaining traceability. I would suggest keeping the NCR as is, as it documents the repair at the vendor. Do you think we should add the comment that it returned and got qualified? Moving forward, the question would then be if we keep NCRs in such cases open until the parts are returned from vendor repair – keep in mind, the cavity might have been shipped to Fermi too.
  *   529 – I fully agree, this is a bit sparse in its comment. Sometimes the CMM folks just point at the attached dimensional report. I’ve requested to add a comment referencing my conversation with John F on if he can compensate for that during the CM assembly.
  *   538 – this one is actually better as it gives some details. There is a 1) and 2) and in both cases I discussed with John F how it might affect the CM assembly with the conclusion that it is a “use as is”.
  *   541 – same here. This was a very similar case of the T being out of tolerance according to spec but within what John F’s team can compensate for when welding the 2-phase pipe. Would your question “was it compensated for” imply that we should have some sort of feedback mechanism once the string is assembled?

Some of your remarks raise certain questions for our general procedures. One being the handling of “return to vendor for repair cases”, the other one (538 & 541) is the question if we need feedback from CM assembly if compensation was successful. The challenge is that cavities are not supposed to move forward in the process to string assembly or even vertical testing until all NCRs have been cleared/closed. Should reopening NCRs be a standard process to add such feedback? That might be a significant additional workload for Pansophy. Alternatively, one might introduce an option/field for additional comments that can be added even after an NCR is closed.

Best,

John V

From: Ashley Mitchell <ashleya at jlab.org>
Sent: Monday, April 28, 2025 14:14
To: Adam Grabowski <adamg at jlab.org>; John Vennekate <hannesv at jlab.org>; Peter Owen <powen at jlab.org>; John Fischer <fischer at jlab.org>; Gary Cheng <cheng at jlab.org>; Naeem Huque <huque at jlab.org>
Cc: pansophy at jlab.org
Subject: J-29 NCRs

Afternoon,

Please review the attached spreadsheet. I pulled NCRs related to J-29 and reviewed them, I highlighted some in yellow that may need a second glance and possible edits I put comments in a "Notes" column to the right.

Please submit a service request to Pansophy team to open the NCRs and edit them.  Please remember to include a brief reason why you are asking to re-open an NCR in your request to expedite the process with Pansophy (example: to change disposition).

[cid:image002.png at 01DBB8F3.22A2CD20]

I will be on leave 4/30-5/5 with limited access to Pansophy, but should be able to answer emails if you have any questions.

Thank you,

Ashley Mitchell (She/Her/Hers)

Quality Engineer

Desk: 757-269-5198

Cell: 757-434-2905
[https://www.jlab.org/div_dept/dir_off/public_affairs/logo/JLabEmailSig.png]
600 Kelvin Dr.
Suite 8, MS 55H
Newport News, VA 23606

www.jlab.org<http://www.jlab.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250507/6aab537f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 40129 bytes
Desc: image002.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250507/6aab537f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 4732 bytes
Desc: image.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250507/6aab537f/attachment-0003.png>