<html>
<head>
<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>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Anne,</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 believe I have had the conversation about this system individually with everyone, but not as a collective. There still seems to be some confusion as to how this is meant to work. I can meet with you and Megan this afternoon to get it squared away. Some responses
to your comments:</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);">
<ul>
<li>PAIRSN not being used anywhere else is by design</li><li>INV will not need to keep track of PAIRSN</li><li>The PAIRSN is only to be used as a tool for coding. I would like the dropdown list list to show both FPCCSNs (e.g. it would read "FPC-001 & FPC-002"). Valerie's suggestion (if I understood it properly) was to have a value correspond to the two serial numbers,
and then have the dropdown list (see below) read back that number. What exists for L2PRD only displays the pair number and there is no way to find an individual FPC serial number from that list. So if a traveler has PA01, FPC-001 and FPC-002 entered in it,
then PA01 would be coded to display "FPC-001 & FPC-002", and that would be what shows in the dropdown list (below) as traveler seq. 1<br>
</li></ul>
<div><img size="7214" contenttype="image/png" style="max-width: 100%; user-select: none;" unselectable="on" tabindex="-1" data-outlook-trace="F:1|T:1" src="cid:79bbac5d-a0ac-4216-8967-7e1374f90447"><br>
</div>
<div><br>
</div>
<div>
<ul>
<li>The FPCC and FPCW don't need to be paired together</li><li>I want the PAIRSN to be distinct from the other two serial numbers, so it's not confused with the FPCCSN</li><li>Danny won't need the PAIRSN number for anything. If there is another way to meet the requirement outlined above, then I am happy to go another route. The dropdown just needs to show both serial numbers that are being covered in the traveler, and I thought
this was the best way to go about it.</li></ul>
<div><br>
</div>
<div>The work is starting in chemistry today, so I'd like to get it sorted soon.<br>
</div>
<div><br>
</div>
<div>Thanks, <br>
</div>
<div>Naeem<br>
</div>
</div>
<div><br>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> E. Anne McEwen <mcewen@jlab.org><br>
<b>Sent:</b> Monday, June 7, 2021 10:56 AM<br>
<b>To:</b> Naeem Huque <huque@jlab.org><br>
<b>Cc:</b> Valerie Bookwalter <bookwalt@jlab.org>; SRF Pansophy (pansophy@jlab.org) <pansophy@jlab.org><br>
<b>Subject:</b> Issues with SN for FPC (L2HE-CLNRM-FPCC-INSP)</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:"Segoe UI"}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
p.x_msonormal0, li.x_msonormal0, div.x_msonormal0
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif}
span.x_EmailStyle19
{font-family:"Calibri",sans-serif;
color:windowtext}
span.x_EmailStyle20
{font-family:"Calibri",sans-serif;
color:#1F497D}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">Hello Naeem </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">A problem has been raised about the SN you want to use for the FPC , I was not aware of this problem until now , however it seems that what is being proposed is inconsistent with what was done in the past –
</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I would suggest a short meeting with yourself, the Pansophy Team, and Inventory so it can get fixed before Danny does the inspection next week
</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Here are some of the feedback I have received in various Chats
</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><img width="800" height="184" id="x_Picture_x0020_2" style="width:8.3333in; height:1.9166in" data-outlook-trace="F:1|T:1" src="cid:image001.jpg@01D75B8A.F66E57C0"></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.5pt; font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">You are requesting (Pansophy) to put in a PAIRSN, which is non-descriptive for part tracing and other than this traveler for INSP in the CLNRM, the PAIRSN is not used anywhere
else</span></p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">INV receives these parts as individual parts. SO keeping track of a PAIRSN is not advisable.\</span></p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">We don't understand need to put in the PA#01 into the system
</span></p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.5pt; font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">We have FPCCSN and FPCWSN for the cold and warm parts of the FPC. None of them are permanently paired together.
</span><span style="font-size:12.0pt; font-family:"Times New Roman",serif"></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif"></span></p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">We have also used FPCSN in the past for the "pair sn" when it was under Mircea. So that could be used, but the question is why? as the pair number is never used in an assembly</span></p>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.5pt; font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">Is there a way to find out from Danny if he would ever use the PA#01 number other than this INSP traveler? If not, then there is no reason to clutter up the system</span></p>
<p class="x_MsoListParagraph"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">As you can see there are a lot of questions –
<span style="color:#1F497D"></span></span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">could you set up a short meeting with the Pansophy Team, Inventory and any others so that this can get resolved before the parts are inspected (next Monday )
</span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-size:10.5pt; font-family:"Segoe UI",sans-serif">Thanks Anne
</span></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><b><span style="font-size:12.0pt">_______________________________________________________________________________</span></b></p>
<p class="x_MsoNormal"><b>E. Anne McEwen </b></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt">JSA / Jefferson Lab</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt">SRF Institute </span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Newport News, VA 23606</span><span style="font-size:4.0pt"></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Office: +1 (757) 269-5539</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Email: <a href="mailto:mcewen@jlab.org">
<span style="color:blue">mcewen@jlab.org</span></a></span></p>
<p class="x_MsoNormal"> </p>
</div>
</div>
</body>
</html>