<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Calibri">I think I am fine with making one traveler for
SEC and one for the REC.<br>
Gary<br>
</font><br>
<div class="moz-cite-prefix">On 10/12/2020 4:11 PM, Katherine Wilson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SA9PR09MB4670145717548282CF93FC3BC0070@SA9PR09MB4670.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;}</style>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
That sounds reasonable to me. Just FYI, I have put the weld
documents into the weld spec on my parts, and then uploaded all
of them into the INV traveler, but use your judgment - probably
you have more documents.</div>
<div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b> Gary
Cheng <a class="moz-txt-link-rfc2396E" href="mailto:cheng@jlab.org"><cheng@jlab.org></a><br>
<b>Sent:</b> Monday, October 12, 2020 3:58 PM<br>
<b>To:</b> Katherine Wilson <a class="moz-txt-link-rfc2396E" href="mailto:kwilson@jlab.org"><kwilson@jlab.org></a>; Ed
Daly <a class="moz-txt-link-rfc2396E" href="mailto:edaly@jlab.org"><edaly@jlab.org></a>; Naeem Huque
<a class="moz-txt-link-rfc2396E" href="mailto:huque@jlab.org"><huque@jlab.org></a><br>
<b>Cc:</b> Matt Marchlik <a class="moz-txt-link-rfc2396E" href="mailto:marchlik@jlab.org"><marchlik@jlab.org></a>; Peter
Owen <a class="moz-txt-link-rfc2396E" href="mailto:powen@jlab.org"><powen@jlab.org></a>; Mark Wiseman
<a class="moz-txt-link-rfc2396E" href="mailto:wiseman@jlab.org"><wiseman@jlab.org></a>; pansophy
<a class="moz-txt-link-rfc2396E" href="mailto:pansophy@jlab.org"><pansophy@jlab.org></a>; Kurt Macha
<a class="moz-txt-link-rfc2396E" href="mailto:macha@jlab.org"><macha@jlab.org></a>; John Fischer
<a class="moz-txt-link-rfc2396E" href="mailto:fischer@jlab.org"><fischer@jlab.org></a>; E. Anne McEwen
<a class="moz-txt-link-rfc2396E" href="mailto:mcewen@jlab.org"><mcewen@jlab.org></a>; Larry King <a class="moz-txt-link-rfc2396E" href="mailto:king@jlab.org"><king@jlab.org></a><br>
<b>Subject:</b> Re: SNS PPU inspection traveler breakdown
structure</font>
<div> </div>
</div>
<div><font face="Calibri">Thanks Katherine.<br>
<br>
Using SEC as an example, I would need to write the following
travelers:<br>
1. Visual inspection traveler --- for SRF QC group, i.e.
Anne's group<br>
2. Dimensional inspection traveler --- for Survey &
Alignment group, end cans won't fit into our CMM machine<br>
3. Weld inspection traveler --- for CWI<br>
4. Instrumentation electrical checkout --- For Larry King's
group<br>
5. Vendor docs check --- for SOTR, CWI and leak check
specialist<br>
6. Pressure test and leak check --- For CMA<br>
<br>
That's a lot to write for just the SEC. Then for the REC, I
would need to write another 6 travelers...I don't think
that's really what we want. But if PPU management prefers to
have such a breakdown structure, I will write 12 travelers
for the SEC and REC...someone please let me know.<br>
<br>
Gary<br>
</font><br>
<div class="x_moz-cite-prefix">On 10/12/2020 3:47 PM,
Katherine Wilson wrote:<br>
</div>
<blockquote type="cite">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
The idea is to break the travelers down by workstation, so
one person is responsible for the part as long as it is
being inspected under that traveler.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
We are trying to minimize travelers that stay open for
months while working through the inspection process, and
also reduce misplaced or damaged parts as they are passed
from one workstation to another, so please let that be
your guide as you decide how to separate the travelers. </div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
I think you will just have to use some judgment about what
seems like a sensible way to separate travelers. Maybe
Anne has further suggestions.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
Regards,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
Katherine</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div>
<div
style="font-family:Calibri,Arial,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> Gary Cheng
<a class="x_moz-txt-link-rfc2396E"
href="mailto:cheng@jlab.org" moz-do-not-send="true"><cheng@jlab.org></a><br>
<b>Sent:</b> Monday, October 12, 2020 3:32 PM<br>
<b>To:</b> Ed Daly <a class="x_moz-txt-link-rfc2396E"
href="mailto:edaly@jlab.org" moz-do-not-send="true">
<edaly@jlab.org></a>; Naeem Huque <a
class="x_moz-txt-link-rfc2396E"
href="mailto:huque@jlab.org" moz-do-not-send="true">
<huque@jlab.org></a><br>
<b>Cc:</b> Katherine Wilson <a
class="x_moz-txt-link-rfc2396E"
href="mailto:kwilson@jlab.org"
moz-do-not-send="true">
<kwilson@jlab.org></a>; Matt Marchlik <a
class="x_moz-txt-link-rfc2396E"
href="mailto:marchlik@jlab.org"
moz-do-not-send="true">
<marchlik@jlab.org></a>; Peter Owen <a
class="x_moz-txt-link-rfc2396E"
href="mailto:powen@jlab.org" moz-do-not-send="true">
<powen@jlab.org></a>; Mark Wiseman <a
class="x_moz-txt-link-rfc2396E"
href="mailto:wiseman@jlab.org"
moz-do-not-send="true">
<wiseman@jlab.org></a>; pansophy <a
class="x_moz-txt-link-rfc2396E"
href="mailto:pansophy@jlab.org"
moz-do-not-send="true">
<pansophy@jlab.org></a>; Kurt Macha <a
class="x_moz-txt-link-rfc2396E"
href="mailto:macha@jlab.org" moz-do-not-send="true">
<macha@jlab.org></a>; John Fischer <a
class="x_moz-txt-link-rfc2396E"
href="mailto:fischer@jlab.org"
moz-do-not-send="true">
<fischer@jlab.org></a>; Larry King <a
class="x_moz-txt-link-rfc2396E"
href="mailto:king@jlab.org" moz-do-not-send="true">
<king@jlab.org></a>; <a
class="x_moz-txt-link-abbreviated"
href="mailto:srfinv@jlab.org" moz-do-not-send="true">
srfinv@jlab.org</a> <a
class="x_moz-txt-link-rfc2396E"
href="mailto:srfinv@jlab.org" moz-do-not-send="true">
<srfinv@jlab.org></a><br>
<b>Subject:</b> Re: SNS PPU inspection traveler
breakdown structure</font>
<div> </div>
</div>
<div><font face="Calibri">Any advice?</font><br>
<br>
<div class="x_x_moz-cite-prefix">On 10/9/2020 11:59 AM,
Gary Cheng wrote:<br>
</div>
<blockquote type="cite"><font face="Calibri">Ed &
Naeem,<br>
<br>
It's unclear to me if there is a consensus on how
many breakdown travelers that PPU project wants to
have for a certain assembly to be inspected. I hope
that you can clarify what you want all SOTRs to
prepare.<br>
<br>
The usual receiving inspection steps that I can
think of are:<br>
shipping crate condition check --- this would be in
INV <br>
vendor documents check --- docs upload to INV. SOTR
as well as SMEs need to check them for completeness
and correctness<br>
visual inspection --- SRF QC or CMA<br>
dimensional inspection --- may be done by SRF QC
folks or Survey & Alignment folks<br>
</font><font face="Calibri"><font face="Calibri">instrumentation
electrical check out --- Larry's group</font><br>
fit-up test --- mostly done CMA<br>
weld inspection --- by weld examiner or CWI<br>
cold shock --- CMA<br>
pressure test --- CMA<br>
leak check --- CMA<br>
repackage<br>
<br>
Please advise. I am about to convert Ed's SNS end
can travelers to the new format and need to know how
many travelers that I need to write for Supply &
Return End Cans.<br>
<br>
Thanks,<br>
Gary<br>
<br>
<br>
<br>
</font></blockquote>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>