[Pansophy] L2HE-CLNRM-CAV-ASSY2-R2 Ready for Approval

[Tiffany Ganey]

L2HE-CLNRM-CAV-ASSY2-R2 has been uploaded to the Docushare L2HE Ready for Approvals folder.  See notes below for additional details on this traveler.

Tiffany Ganey

From: Tiffany Ganey
Sent: Tuesday, November 9, 2021 2:07 PM
To: John Hogan <hogan at jlab.org>; Katherine Wilson <kwilson at jlab.org>; John Vennekate <hannesv at jlab.org>
Cc: Kirk Davis <kdavis at jlab.org>; E. Anne McEwen <mcewen at JLAB.ORG>; Valerie Bookwalter <bookwalt at jlab.org>; Danny Forehand <forehand at jlab.org>; Ashley Anderson Mitchell <ashleya at JLAB.ORG>; Justin Kent <jtkent at jlab.org>; pansophy <pansophy at jlab.org>
Subject: L2HE Travelers Ready for Production Cavities Arrival

Hi All,

In today's HE staff meeting, it was requested that a review of the travelers needed for production cavities from receipt from vendor through VTRF qualification be done since the L2HE production cavities have begun arriving at JLab and John V. will be scheduling these cavities through the work centers soon.

L2HE Production Cavity Traveler Status as of 11/9/2021<https://jeffersonlab-my.sharepoint.com/:x:/g/personal/ganey_jlab_org/EYh8J9pOqxZHt5c7c9rI7McBpKi_oPsAGTK_I66yo2eEjA?e=lMxq56>  - This linked file contains a list of the action steps for cavities as received from vendor through qualification for string assembly (including re-clean and test if needed), the associated traveler ID, traveler revision in Pansophy, and whether the traveler is ready for production cavities.  The file does not verify components or string assembly travelers.

In summary, there are two travelers that are not ready for production; however, only one of these (L2HE-CLNRM-CAV-ASSY2) must be updated prior to use.  The two travelers are only used if the cavity fails the VTRF so it would be a couple weeks at earliest before they would be needed.

-          L2HE-CLNRM-CAV-ASSY2: A step needs to be added to verify that the right angle valve is installed in the correct orientation due to the implementation of the purge system for string assembly.  This traveler was also waiting for the associated procedure to be issued so I had not made a push to get the traveler updated.  However, I feel that it is important to have the traveler check for the right angle valve orientation so I will draft an R2 to this traveler and upload it to Docushare for approval by COB today.  A R3 will be required when the procedure is has been issued and can be hyperlinked to the traveler.

-          L2HE-CLNRM-CAV-LEAK: This traveler was requested as method to capture all of the leak check data in a single traveler.  Currently the leak check data is captured in the existing L2HE-CLNRM-CAV-TSTD and -TSTD5 (test stand attachment) travelers.  Although it would be preferable to have this traveler issued prior to production cavities start for consistency across all production cavity data, the production cavity data does have a place to be stored and we can migrate the data to the -LEAK traveler when it is issued.

L2HE-CLNRM-CAV-ASSY1 was marked as not ready for production in my spreadsheet; however, I approved this traveler this morning (as the last signature) so it should be in place in time to support production.  This traveler is also only used if the cavity fails the initial VTRF.

A few of the travelers have procedures that have not been issued, but the traveler is otherwise ready for production use (i.e., the traveler captures critical steps and data).  Since the work that would be described in the procedures are not new processes for JLab staff and the procedures will be based on existing in-use procedures for other projects, I believe we can use the travelers for production cavities; however, we should continue to track the completion of these procedures and add the hyperlinks to the travelers as soon as possible to align with the ISO expectations.

Tiffany Ganey

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20211109/8b4f834d/attachment-0001.html>