<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=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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Consolas;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{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;}
/* List Definitions */
@list l0
{mso-list-id:421337920;
mso-list-template-ids:1335805792;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Gary
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The reason for my suggestion is that I understand Survey & Alignment are actually doing the dimensional inspection because the end cans are too big to fit
on the CMM. So a thought was to have all the dimensional inspections together for the end cans
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I realize that normally Survey & Alignment are doing other types of measurements that definitely fit in the CAM traveler such as alignment checks etc.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">So if it preferred to put the End Can dimensional work into the CMA traveler I would be fine with this also – the main thing is for the data to be easy to find
down the road <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks Anne
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;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"> Gary Cheng <cheng@jlab.org>
<br>
<b>Sent:</b> Wednesday, October 14, 2020 5:18 PM<br>
<b>To:</b> Valerie Bookwalter <bookwalt@jlab.org>; E. Anne McEwen <mcewen@jlab.org><br>
<b>Cc:</b> Kurt Macha <macha@jlab.org>; Mark Wiseman <wiseman@jlab.org>; John Fischer <fischer@jlab.org>; Larry King <king@jlab.org>; Matt Marchlik <marchlik@jlab.org>; Peter Owen <powen@jlab.org>; pansophy <pansophy@jlab.org>; Katherine Wilson <kwilson@jlab.org>;
Naeem Huque <huque@jlab.org>; Ed Daly <edaly@jlab.org>; Tony Reilly <areilly@jlab.org>; John Fischer <fischer@jlab.org><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">Hi Valerie & Anne,<br>
<br>
I decide to comply with the new policy and have split my SEC traveler into 3 according to what Valerie suggested. Now there is SNSPPU-CWI-SENC, SNSPPU-INSP-SENC and SNSPPU-CMA-SENC-INSP for inspection of PPU SEC. Pansophy team doesn't need to write the CWI-SENC
traveler. There will be 3 such inspection travelers for the REC as well. <br>
<br>
I noticed that "Anne’s group with outreach to Survey & Alignment group". Normally, it is the CMA group who coordinates with S&A to conduct dimensional measurements that CMM/SRF QC cannot do. Should we maintain this tradition? After all, CMM/SRF QC is short
of hands and data acquired by S&A are usually useful information for CMA. <br>
<br>
If you wish, I can split the dimensions for S&A from those that CMM/SRF QC can measure then feed them into the SNSPPU-INSP-SENC and SNSPPU-CMA-SENC-INSP, respectively. That way, CMM measures what CMM can and CMA will work with S&A to get other dimensions taken.
It means more work for me, but I think this approach will help to keep the convention.
<br>
<br>
Thanks,<br>
Gary</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/13/2020 12:15 PM, Valerie Bookwalter wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Gary,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Creating just one traveler for each part is not advisable. It does not comply with current Traveler work center breakdowns which support our Reporting system.
It also does not support our attempt to be more ISO compliant in being able to track parts, work done and timelines. It causes confusion as to which work center or person is responsible for closing a traveler and ensuring all data is entered appropriately.
It also helps maintains NCR continuity to part, problem and location.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We would appreciate if you could help us maintain this quality system.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We propose the following:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Pansophy Team will Create Travelers:</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">SNSPPU-INV-SENC: Inventory Traveler (Phil’s group with upload of shipping documentation)
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">SNSPPU-CWI-SENC: CWI (Jenord’Ss traveler)
</span><o:p></o:p></p>
<p class="MsoListParagraph"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Travelers you would need to write:</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">SNSPPU-INSP-SENC: Visual and Dimensional Inspection Traveler (Anne’s group with outreach to Survey & Alignment group) SNSPPU-INSP-SENC
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">SNSPPU-CMA-SENC-INSP: All other work which is done in the Cryomodule Assembly Area (Fischer’s group and groups he coordinates with)
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">1.</span><![endif]><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The only change would be if Larry King wants a separate traveler for his team’s electrical checks, but we do
not require this.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This would result in you writing 2 travelers (INSP and CMA) for each of the SENC and RENC. I hope you will find this acceptable and if you need help, please ask.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Valerie Bookwalter</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Pansophy Team</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></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 href="mailto:pansophy-bounces@jlab.org"><pansophy-bounces@jlab.org></a> <b>On Behalf Of
</b>Gary Cheng<br>
<b>Sent:</b> Tuesday, October 13, 2020 8:55 AM<br>
<b>To:</b> Mike Dickey <a href="mailto:mdickey@jlab.org"><mdickey@jlab.org></a>; Katherine Wilson
<a href="mailto:kwilson@jlab.org"><kwilson@jlab.org></a>; Ed Daly <a href="mailto:edaly@jlab.org">
<edaly@jlab.org></a>; Naeem Huque <a href="mailto:huque@jlab.org"><huque@jlab.org></a><br>
<b>Cc:</b> Kurt Macha <a href="mailto:macha@jlab.org"><macha@jlab.org></a>; Mark Wiseman
<a href="mailto:wiseman@jlab.org"><wiseman@jlab.org></a>; E. Anne McEwen <a href="mailto:mcewen@jlab.org">
<mcewen@jlab.org></a>; John Fischer <a href="mailto:fischer@jlab.org"><fischer@jlab.org></a>; Larry King
<a href="mailto:king@jlab.org"><king@jlab.org></a>; Matt Marchlik <a href="mailto:marchlik@jlab.org">
<marchlik@jlab.org></a>; Peter Owen <a href="mailto:powen@jlab.org"><powen@jlab.org></a>; pansophy
<a href="mailto:pansophy@jlab.org"><pansophy@jlab.org></a><br>
<b>Subject:</b> Re: [Pansophy] SNS PPU inspection traveler breakdown structure</span><o:p></o:p></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">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</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/13/2020 8:19 AM, Mike Dickey wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-family:Consolas;color:#1F497D">Gary,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:#1F497D"> </span><o:p></o:p></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?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:Consolas;color:black">Mike Dickey</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:black">SRF Inventory Technician</span><o:p></o:p></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><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-family:Consolas;color:#1F497D"> </span><o:p></o:p></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
</span><a href="mailto:pansophy-bounces@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><pansophy-bounces@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<b>On Behalf Of </b>Gary Cheng<br>
<b>Sent:</b> Monday, October 12, 2020 4:50 PM<br>
<b>To:</b> Katherine Wilson </span><a href="mailto:kwilson@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><kwilson@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Ed Daly
</span><a href="mailto:edaly@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><edaly@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Naeem Huque
</span><a href="mailto:huque@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><huque@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Cc:</b> Kurt Macha </span><a href="mailto:macha@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><macha@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Mark Wiseman
</span><a href="mailto:wiseman@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><wiseman@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; E. Anne McEwen
</span><a href="mailto:mcewen@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><mcewen@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; John Fischer
</span><a href="mailto:fischer@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><fischer@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Larry King
</span><a href="mailto:king@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><king@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Matt Marchlik
</span><a href="mailto:marchlik@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><marchlik@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Peter Owen
</span><a href="mailto:powen@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><powen@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; pansophy
</span><a href="mailto:pansophy@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><pansophy@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b> Re: [Pansophy] SNS PPU inspection traveler breakdown structure</span><o:p></o:p></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.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></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="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
</span><a href="mailto:cheng@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><cheng@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<b>Sent:</b> Monday, October 12, 2020 3:58 PM<br>
<b>To:</b> Katherine Wilson </span><a href="mailto:kwilson@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><kwilson@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Ed Daly
</span><a href="mailto:edaly@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><edaly@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Naeem Huque
</span><a href="mailto:huque@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><huque@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<b>Cc:</b> Matt Marchlik </span><a href="mailto:marchlik@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><marchlik@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Peter Owen
</span><a href="mailto:powen@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><powen@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Mark Wiseman
</span><a href="mailto:wiseman@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><wiseman@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; pansophy
</span><a href="mailto:pansophy@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><pansophy@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Kurt Macha
</span><a href="mailto:macha@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><macha@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; John Fischer
</span><a href="mailto:fischer@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><fischer@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; E. Anne McEwen
</span><a href="mailto:mcewen@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><mcewen@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Larry King
</span><a href="mailto:king@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><king@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><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.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></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. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></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.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Regards,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Katherine</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" 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
</span><a href="mailto:cheng@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><cheng@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<b>Sent:</b> Monday, October 12, 2020 3:32 PM<br>
<b>To:</b> Ed Daly </span><a href="mailto:edaly@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><edaly@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Naeem Huque
</span><a href="mailto:huque@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><huque@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<b>Cc:</b> Katherine Wilson </span><a href="mailto:kwilson@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><kwilson@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Matt Marchlik
</span><a href="mailto:marchlik@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><marchlik@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Peter Owen
</span><a href="mailto:powen@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><powen@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Mark Wiseman
</span><a href="mailto:wiseman@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><wiseman@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; pansophy
</span><a href="mailto:pansophy@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><pansophy@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Kurt Macha
</span><a href="mailto:macha@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><macha@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; John Fischer
</span><a href="mailto:fischer@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><fischer@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">; Larry King
</span><a href="mailto:king@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><king@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">;
</span><a href="mailto:srfinv@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">srfinv@jlab.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
</span><a href="mailto:srfinv@jlab.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><srfinv@jlab.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><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>
<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>
</blockquote>
<p class="MsoNormal"> <o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>