<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal0, li.xmsonormal0, div.xmsonormal0
{mso-style-name:x_msonormal0;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault
{mso-style-name:x_msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.xmsohyperlink
{mso-style-name:x_msohyperlink;
color:#0563C1;
text-decoration:underline;}
span.xmsohyperlinkfollowed
{mso-style-name:x_msohyperlinkfollowed;
color:#954F72;
text-decoration:underline;}
span.xemailstyle18
{mso-style-name:x_emailstyle18;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle19
{mso-style-name:x_emailstyle19;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Thank you Valerie. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I believe the plan then for this second traveler is to create D3s to document the removal of the damaged FPCs and then record the new FPCC SNs in the appropriate data fields. We will also re-perform the leak
check and upload the new leak check files instead of re-using the files from the first traveler.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Tiffany Ganey<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Valerie Bookwalter <bookwalt@jlab.org> <br>
<b>Sent:</b> Thursday, May 12, 2022 11:26 AM<br>
<b>To:</b> Jacob Harris <jharris@jlab.org>; Tiffany Ganey <ganey@jlab.org><br>
<b>Cc:</b> E. Anne McEwen <mcewen@jlab.org>; Kirk Davis <kdavis@jlab.org>; John Hogan <hogan@jlab.org>; Tony Reilly <areilly@jlab.org>; Danny Forehand <forehand@jlab.org>; pansophy <pansophy@jlab.org><br>
<b>Subject:</b> RE: L2HE-CLNRM-CST-ASSY Rework<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">Tiffany,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">A traveler has been instantiated (#2) and data copied.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><a href="https://pansophy.jlab.org/pansophy/Travelers/TRAVELER_FORM.cfm?project=L2HE&area=L2HE&system=CLNRM&TRAV_ID=L2HE-CLNRM-CST-ASSY&TRAV_REVISION=R1&page=1&maxpage=14&TRAV_SEQ_NUM=2&ncr_num=.&travstat=n&serialnum=J1.3-22&SN=J1.3-22&SNType=CMSN">https://pansophy.jlab.org/pansophy/Travelers/TRAVELER_FORM.cfm?project=L2HE&area=L2HE&system=CLNRM&TRAV_ID=L2HE-CLNRM-CST-ASSY&TRAV_REVISION=R1&page=1&maxpage=14&TRAV_SEQ_NUM=2&ncr_num=.&travstat=n&serialnum=J1.3-22&SN=J1.3-22&SNType=CMSN</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">I also added a comment on page 1 designating what I did.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">Let me know if you need any more help.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">FYI: I did not copy any of the file uploads, so they will have to be redone.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">Valerie Bookwalter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">Jefferson Lab, SRF Department<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">Pansophy Team<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">1-757-269-5802 (OFFICE – currently working offsite)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Pansophy <<a href="mailto:pansophy-bounces@mailman.jlab.org">pansophy-bounces@mailman.jlab.org</a>>
<b>On Behalf Of </b>Valerie Bookwalter<br>
<b>Sent:</b> Thursday, May 12, 2022 10:55 AM<br>
<b>To:</b> Jacob Harris <<a href="mailto:jharris@jlab.org">jharris@jlab.org</a>>; Tiffany Ganey <<a href="mailto:ganey@jlab.org">ganey@jlab.org</a>><br>
<b>Cc:</b> E. Anne McEwen <<a href="mailto:mcewen@jlab.org">mcewen@jlab.org</a>>; Kirk Davis <<a href="mailto:kdavis@jlab.org">kdavis@jlab.org</a>>; John Hogan <<a href="mailto:hogan@jlab.org">hogan@jlab.org</a>>; Tony Reilly <<a href="mailto:areilly@jlab.org">areilly@jlab.org</a>>;
Danny Forehand <<a href="mailto:forehand@jlab.org">forehand@jlab.org</a>>; pansophy <<a href="mailto:pansophy@jlab.org">pansophy@jlab.org</a>><br>
<b>Subject:</b> Re: [Pansophy] L2HE-CLNRM-CST-ASSY Rework<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Tiffany / Jacob / et al.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Opening a new traveler for "rework" per se is the procedure that has always been followed.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">This allows for full data integrity and a more precise timeline of events.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Tiffany,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">I have already spoken with Megan and we will initiate a new traveler and copy data over from original to speed up the data process.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Then you will just update areas that are being reworked.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">This also keeps all reports in tact because we pull the "last date" traveler.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Please let us know if you need any additional support.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Valerie Bookwalter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Jefferson Lab, SRF Department<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Pansophy Team<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">1-757-269-5802 (OFFICE – currently working offsite)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Pansophy <<a href="mailto:pansophy-bounces@mailman.jlab.org">pansophy-bounces@mailman.jlab.org</a>> on behalf of Jacob Harris <<a href="mailto:jharris@jlab.org">jharris@jlab.org</a>><br>
<b>Sent:</b> Thursday, May 12, 2022 10:36 AM<br>
<b>To:</b> Tiffany Ganey <<a href="mailto:ganey@jlab.org">ganey@jlab.org</a>>; pansophy <<a href="mailto:pansophy@jlab.org">pansophy@jlab.org</a>><br>
<b>Subject:</b> Re: [Pansophy] L2HE-CLNRM-CST-ASSY Rework</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal">Tiffany and Pansophy Team<o:p></o:p></p>
<p class="xmsonormal">SNSPPU project had a similar issue when they replaced a cavity in string PPU-02. They initiated a second Sting Assembly Traveler for PPU-02 and pulled all the relevant info (changed and unchanged) into the new traveler. Pansophy Team,
is this the typical method for exchanging parts in a string after the initial traveler is closed? Does this method break any of your reports than now have to recognize two CST ASSY travelers with the same SN?<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Jacob <o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="xmsonormal"><b>From:</b> Tiffany Ganey <<a href="mailto:ganey@jlab.org">ganey@jlab.org</a>>
<br>
<b>Sent:</b> Thursday, May 12, 2022 8:04 AM<br>
<b>To:</b> pansophy <<a href="mailto:pansophy@jlab.org">pansophy@jlab.org</a>>; Jacob Harris <<a href="mailto:jharris@jlab.org">jharris@jlab.org</a>><br>
<b>Subject:</b> L2HE-CLNRM-CST-ASSY Rework<o:p></o:p></p>
</div>
</div>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">We will need to replace some of the FPCs that were installed on the first L2HE string. The FPCC SN for the string is captured in L2HE-CLNRM-CST-ASSY, Traveler SN 1. Since this string had already been pushed out of the cleanroom before
the damage was discovered, the traveler was already closed. I think that I need to request that the traveler be re-opened so that we can replace the damaged FPCs and update the FPCCSNs in the traveler. We will also need to redo the leak check, which is recorded
in the traveler as well. I think that this replacement work will also be noted in one or more D3s to be linked to this traveler.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Is this the correct way to handle this situation with respect to updating the traveler recorded data?<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Tiffany Ganey<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>