<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Calibri">Mike, <br>
<br>
Yes. Unless I am forced to write 6 travelers per end can or a
total of 12 travelers for the SEC and REC. I don't see much
technical merit in writing 12 travelers for a set of end cans.<br>
<br>
Gary<br>
</font><br>
<div class="moz-cite-prefix">On 10/13/2020 8:19 AM, Mike Dickey
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SA0PR09MB6172BA65B7FCFEFE37A1AFB2DF040@SA0PR09MB6172.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Consolas;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-family:Consolas;color:#1F497D">Gary,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Consolas;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Consolas;color:#1F497D">Are you planning
to write just 1 INSP traveler for the SEC and 1 for the REC?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Consolas;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-family:Consolas;color:black">Mike Dickey<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Consolas;color:black">SRF Inventory
Technician<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Consolas;color:black">Jefferson Lab<br>
12000 Jefferson Ave<br>
Newport News, VA 23606<br>
(757) 269-7755</span><span
style="font-family:Consolas;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-family:Consolas;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><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
Pansophy <a class="moz-txt-link-rfc2396E" href="mailto:pansophy-bounces@jlab.org"><pansophy-bounces@jlab.org></a>
<b>On Behalf Of </b>Gary Cheng<br>
<b>Sent:</b> Monday, October 12, 2020 4:50 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> Kurt Macha <a class="moz-txt-link-rfc2396E" href="mailto:macha@jlab.org"><macha@jlab.org></a>; Mark
Wiseman <a class="moz-txt-link-rfc2396E" href="mailto:wiseman@jlab.org"><wiseman@jlab.org></a>; E. Anne McEwen
<a class="moz-txt-link-rfc2396E" href="mailto:mcewen@jlab.org"><mcewen@jlab.org></a>; John Fischer
<a class="moz-txt-link-rfc2396E" href="mailto:fischer@jlab.org"><fischer@jlab.org></a>; Larry King
<a class="moz-txt-link-rfc2396E" href="mailto:king@jlab.org"><king@jlab.org></a>; 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>; pansophy
<a class="moz-txt-link-rfc2396E" href="mailto:pansophy@jlab.org"><pansophy@jlab.org></a><br>
<b>Subject:</b> Re: [Pansophy] SNS PPU inspection
traveler breakdown structure<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">I think I
am fine with making one traveler for SEC and one for the
REC.<br>
Gary</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/12/2020 4:11 PM, Katherine Wilson
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">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.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr width="98%" size="2" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
Gary Cheng
<a href="mailto:cheng@jlab.org" moz-do-not-send="true"><cheng@jlab.org></a><br>
<b>Sent:</b> Monday, October 12, 2020 3:58 PM<br>
<b>To:</b> Katherine Wilson <a
href="mailto:kwilson@jlab.org"
moz-do-not-send="true"><kwilson@jlab.org></a>;
Ed Daly
<a href="mailto:edaly@jlab.org" moz-do-not-send="true"><edaly@jlab.org></a>;
Naeem Huque <a href="mailto:huque@jlab.org"
moz-do-not-send="true">
<huque@jlab.org></a><br>
<b>Cc:</b> Matt Marchlik <a
href="mailto:marchlik@jlab.org"
moz-do-not-send="true"><marchlik@jlab.org></a>;
Peter Owen
<a href="mailto:powen@jlab.org" moz-do-not-send="true"><powen@jlab.org></a>;
Mark Wiseman <a href="mailto:wiseman@jlab.org"
moz-do-not-send="true">
<wiseman@jlab.org></a>; pansophy <a
href="mailto:pansophy@jlab.org"
moz-do-not-send="true"><pansophy@jlab.org></a>;
Kurt Macha
<a href="mailto:macha@jlab.org" moz-do-not-send="true"><macha@jlab.org></a>;
John Fischer <a href="mailto:fischer@jlab.org"
moz-do-not-send="true">
<fischer@jlab.org></a>; E. Anne McEwen <a
href="mailto:mcewen@jlab.org" moz-do-not-send="true"><mcewen@jlab.org></a>;
Larry King
<a href="mailto:king@jlab.org" moz-do-not-send="true"><king@jlab.org></a><br>
<b>Subject:</b> Re: SNS PPU inspection traveler
breakdown structure</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">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</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/12/2020 3:47 PM, Katherine
Wilson wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black">Katherine<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr width="98%" size="2" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
Gary Cheng
<a 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
href="mailto:edaly@jlab.org"
moz-do-not-send="true"><edaly@jlab.org></a>;
Naeem Huque
<a href="mailto:huque@jlab.org"
moz-do-not-send="true"><huque@jlab.org></a><br>
<b>Cc:</b> Katherine Wilson <a
href="mailto:kwilson@jlab.org"
moz-do-not-send="true"><kwilson@jlab.org></a>;
Matt Marchlik
<a href="mailto:marchlik@jlab.org"
moz-do-not-send="true"><marchlik@jlab.org></a>;
Peter Owen <a href="mailto:powen@jlab.org"
moz-do-not-send="true">
<powen@jlab.org></a>; Mark Wiseman <a
href="mailto:wiseman@jlab.org"
moz-do-not-send="true"><wiseman@jlab.org></a>;
pansophy
<a href="mailto:pansophy@jlab.org"
moz-do-not-send="true"><pansophy@jlab.org></a>;
Kurt Macha <a href="mailto:macha@jlab.org"
moz-do-not-send="true">
<macha@jlab.org></a>; John Fischer <a
href="mailto:fischer@jlab.org"
moz-do-not-send="true"><fischer@jlab.org></a>;
Larry King
<a href="mailto:king@jlab.org"
moz-do-not-send="true"><king@jlab.org></a>;
<a href="mailto:srfinv@jlab.org"
moz-do-not-send="true">
srfinv@jlab.org</a> <a
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</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">Any advice?</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/9/2020 11:59 AM, Gary
Cheng wrote:<o:p></o:p></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">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>
instrumentation electrical check out ---
Larry's group<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>
</span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>