<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<font face="Calibri">Peter,<br>
<br>
Yes, I will mention in the travlers the M:\ folder for all curves
and ask that the .zip should be uploaded. <br>
<br>
Thanks,<br>
Gary<br>
</font><br>
<div class="moz-cite-prefix">On 4/6/2021 11:55 AM, Peter Owen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SA9PR09MB60161F0C26318CAC137CE810C8769@SA9PR09MB6016.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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);">
Gary,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
I like this system. The traveler should specify that the *.zip
file should be uploaded for a sensor since that contains all
curve file types. You may want to mention in the traveler that
the master copy of all curves is stored on the M: drive. Though
maybe not everyone has access to that folder.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color:black;font-family:Calibri,sans-serif">M:\SNS_PPU\CM
Production\Cernox Curves\All Cernox</span></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);">
Peter<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<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> Tuesday, April 6, 2021 11:46 AM<br>
<b>To:</b> Peter Owen <a class="moz-txt-link-rfc2396E" href="mailto:powen@jlab.org"><powen@jlab.org></a>; Larry King
<a class="moz-txt-link-rfc2396E" href="mailto:king@jlab.org"><king@jlab.org></a><br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:srfinv@jlab.org">srfinv@jlab.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:srfinv@jlab.org"><srfinv@jlab.org></a>; pansophy
<a class="moz-txt-link-rfc2396E" href="mailto:pansophy@jlab.org"><pansophy@jlab.org></a>; Naeem Huque <a class="moz-txt-link-rfc2396E" href="mailto:huque@jlab.org"><huque@jlab.org></a>;
Ed Daly <a class="moz-txt-link-rfc2396E" href="mailto:edaly@jlab.org"><edaly@jlab.org></a>; John Fischer
<a class="moz-txt-link-rfc2396E" href="mailto:fischer@jlab.org"><fischer@jlab.org></a><br>
<b>Subject:</b> Re: SNS PPU SEC 01 vendor docs review</font>
<div> </div>
</div>
<div><font face="Calibri">I need to finalize the newest revisions
of my SEC and REC inspection travelers before the next end
can(s) show up. I'd like to get a consensus on what we want to
do with the Cernox curves for the end can sensors. Each SEC
has 2 sensors and each REC has 10. We sent to the end can
vendor a total of 84 sensors to be installed on 7 SECs and 7
RECs. Vendor will send us information about which sensors
(S/Ns) are installed on which SEC/REC at what locations (wires
labelled with wiring diagram sensor naming convention, such
as TDxx022A). <br>
<br>
To link each SEC or REC with its specific sensors and
facilitate pansophy search of the data curves for use in
shipping traveler in the end, here is what I propose to do</font><font
face="Calibri"><font face="Calibri"> in regard to Cernox
sensors & data curves, responsible parties are
identified</font>:<br>
<br>
1. Create a dropdown list of the S/Ns for all 84 sensors that
were sent to the end can vendor ----<b>SRFINV team or Pansophy
team</b><br>
2. For each SEC or REC, check vendor documentation for sensors
actually installed. Also verify the labels on wires are
correct. ---
<b>SRF Instrumentation team</b><br>
3. Traveler will have a fileupload for each Cernox sensor.
That is, </font><font face="Calibri"><font face="Calibri">SNSPPU-CMA-INSP-SEC</font>
will have 2 dropdowns and 2 fileuploads,
</font><font face="Calibri"><font face="Calibri"><font
face="Calibri">SNSPPU-CMA-INSP-REC</font></font> will have
</font><font face="Calibri"><font face="Calibri">10 dropdowns
and 10 fileuploads. ----
<b>Gary Cheng</b><br>
4. Select the Cernox S/N and upload the corresponding curve.
--- </font></font><font face="Calibri"><font face="Calibri"><b><font
face="Calibri"><font face="Calibri">SRF Instrumentation
team</font></font></b><br>
<br>
To select 2 or 10 sensors from 84 S/Ns, locate their curves
and upload them can be a tedious process. Any better ideas
are welcome. Note that we don't know what sensors the vendor
installs on a SEC or REC till they are done with their
installation. Currently, we get the sensor installation info
when we receive the final documentation package for a
certain SEC/REC.<br>
</font> <br>
Thanks,<br>
Gary<br>
</font><br>
<div class="x_moz-cite-prefix">On 3/16/2021 3:07 PM, Peter Owen
wrote:<br>
</div>
<blockquote type="cite">
<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)">
The files are saved in the DCXCU inventory traveler. I've
made sure every traveler filed out has files attached,
either individual or the zip. I pulled them to the M: folder
so I could get a list of values for Gary to send to the EC
vendor. Calvin said he downloaded the curves straight from
the Lakeshore website, so I expect we could get the curves
again if they are lost.</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 see no problem with storing the curves in as many places
as possible in what ever format is most appropriate, as long
as we know which one is the master set. I think the
inventory traveler should be that set.</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)">
Peter<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> Larry King
<a class="x_moz-txt-link-rfc2396E"
href="mailto:king@jlab.org" moz-do-not-send="true"><king@jlab.org></a><br>
<b>Sent:</b> Tuesday, March 16, 2021 2:28 PM<br>
<b>To:</b> Peter Owen <a class="x_moz-txt-link-rfc2396E"
href="mailto:powen@jlab.org" moz-do-not-send="true">
<powen@jlab.org></a>; 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>Subject:</b> RE: SNS PPU SEC 01 vendor docs review</font>
<div> </div>
</div>
<style>@font-face
{font-family:Wingdings}@font-face
{font-family:"Cambria Math"}@font-face
{font-family:Calibri}p.x_x_MsoNormal, li.x_x_MsoNormal, div.x_x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}a:link, span.x_x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}a:visited, span.x_x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}p.x_x_MsoListParagraph, li.x_x_MsoListParagraph, div.x_x_MsoListParagraph
{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.x_x_msonormal0, li.x_x_msonormal0, div.x_x_msonormal0
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}p.x_x_xmsonormal, li.x_x_xmsonormal, div.x_x_xmsonormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}p.x_x_xmsonormal0, li.x_x_xmsonormal0, div.x_x_xmsonormal0
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}p.x_x_xmsochpdefault, li.x_x_xmsochpdefault, div.x_x_xmsochpdefault
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman",serif}span.x_x_xmsohyperlink
{color:#0563C1;
text-decoration:underline}span.x_x_xmsohyperlinkfollowed
{color:#954F72;
text-decoration:underline}span.x_x_xemailstyle19
{font-family:"Calibri",sans-serif;
color:#1F497D}span.x_x_xemailstyle20
{font-family:"Calibri",sans-serif;
color:windowtext}span.x_x_xemailstyle21
{font-family:"Calibri",sans-serif;
color:#1F497D}span.x_x_EmailStyle27
{font-family:"Calibri",sans-serif;
color:#1F497D}span.x_x_EmailStyle29
{font-family:"Calibri",sans-serif;
color:windowtext}.x_x_MsoChpDefault
{font-size:10.0pt}ol
{margin-bottom:0in}ul
{margin-bottom:0in}</style>
<div lang="EN-US">
<div class="x_x_WordSection1">
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Hi Peter,</span></p>
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">I guess I vote for having a step to
upload the individual curves to the EC receiving
traveler. Not wanting to belabor the point, I’m just
going to lay out my logic. There may be another,
better way, and I realize I may be missing something,
so please just take these as suggestions.</span></p>
<p class="x_x_MsoListParagraph"
style="margin-left:20.25pt; text-indent:-.25in"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">The .zip files are probably what we
need to deliver to ORNL with the CM, so we need to be
sure we have one for every sensor installed. I think
that check should happen early on, like during EC
receipt. We had a few sensors for L2 that we could
not find curves for and it took a while for FNAL to
find them for us.</span></p>
<p class="x_x_MsoListParagraph"
style="margin-left:20.25pt; text-indent:-.25in"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">The .dat files are needed for CMTF
cooldown. Ideally, there would be links already in
the CM Assy or Testing traveler, pointing to the EC
receiving traveler.</span></p>
<p class="x_x_MsoListParagraph"
style="margin-left:20.25pt; text-indent:-.25in"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">The .zip files will need to eventually
make it to the shipping traveler for delivery to
ORNL. It seems easier to have the shipping traveler
grab the data from the CM ASSY or EC receiving
traveler.</span></p>
<p class="x_x_MsoListParagraph"
style="margin-left:20.25pt; text-indent:-.25in"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">I also seem to remember being told that
we should try to move away from relying on shared
drive folders for critical customer data, so a
traveler may be a better place to keep all these
curves.</span></p>
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Thoughts?</span></p>
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Regards,</span></p>
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Larry</span></p>
<p class="x_x_MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt;
padding:3.0pt 0in 0in 0in">
<p class="x_x_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"> Peter
Owen
<a class="x_moz-txt-link-rfc2396E"
href="mailto:powen@jlab.org"
moz-do-not-send="true"><powen@jlab.org></a>
<br>
<b>Sent:</b> Tuesday, March 16, 2021 1:35 PM<br>
<b>To:</b> Gary Cheng <a
class="x_moz-txt-link-rfc2396E"
href="mailto:cheng@jlab.org"
moz-do-not-send="true">
<cheng@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><br>
<b>Subject:</b> Re: SNS PPU SEC 01 vendor docs
review</span></p>
</div>
</div>
<p class="x_x_MsoNormal"> </p>
<div>
<p class="x_x_MsoNormal"><span
style="font-family:"Calibri",sans-serif;
color:black"><img id="x_x__x0000_i1025" class=""
style="width:1.6145in; height:2.9479in"
data-outlook-trace="F:2|T:2"
src="cid:part7.64E37ED6.2664DEF1@jlab.org"
width="155" height="283"></span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span
style="font-family:"Calibri",sans-serif;
color:black">The curves are saved in M:\SNS_PPU\CM
Production\Cernox Curves\All Cernox</span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span
style="font-family:"Calibri",sans-serif;
color:black">I made that folder over the summer when
we send cernox to the end can vendor. Which file
type should be uploaded to the traveler? The .zip
has all the other files inside. Alternatively, could
the pansophy team pull the appropriate file from the
inventory traveler after the serial number is
entered?</span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span
style="font-family:"Calibri",sans-serif;
color:black"> </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span
style="font-family:"Calibri",sans-serif;
color:black">Peter</span></p>
</div>
<div class="x_x_MsoNormal" style="text-align:center"
align="center">
<hr width="98%" size="2" align="center">
</div>
<div id="x_x_divRplyFwdMsg">
<p class="x_x_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> Tuesday, March 16, 2021 11:37 AM<br>
<b>To:</b> Larry King <<a
href="mailto:king@jlab.org" moz-do-not-send="true">king@jlab.org</a>>;
Peter Owen <<a href="mailto:powen@jlab.org"
moz-do-not-send="true">powen@jlab.org</a>><br>
<b>Subject:</b> Re: SNS PPU SEC 01 vendor docs
review</span> </p>
<div>
<p class="x_x_MsoNormal"> </p>
</div>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">Hi
Larry,<br>
<br>
Peter bought all Cernox sensors for SNS PPU and we
sent 84 Cernox sensors as GFMs to the end can
vendor. So we have the calc curves. Currently in the
traveler's Step 3, there are fields for comments and
file upload:<br>
<br>
<img id="x_x__x0000_i1027" class=""
style="width:4.7708in; height:1.2083in"
data-outlook-trace="F:2|T:2"
src="cid:part11.49302E1A.A77B9E47@jlab.org"
width="458" height="116" border="0"><br>
<br>
Maybe Peter or you can use these two to either make
a comment about where to find the full calc curves
for the sensors installed on a certain SEC or upload
the curves? If you'd like to have another specific
fileupload button just for the curves, I can add
that. Please let me know.<br>
<br>
Thanks,<br>
Gary</span></p>
<div>
<p class="x_x_MsoNormal">On 3/15/2021 4:59 PM, Larry
King wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;
margin-bottom:5.0pt">
<div>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Hi Gary,</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">The only problem with waiting
until the CMTF testing traveler to enter the
curves is that they might be missing. Since the
data is supposed to come from the vendor, I
think the files should be uploaded sooner than
later, in case there’s a problem. My thought
was that the “check Cernox data” step of the
inspection traveler was to check that the files
were available for each serial number of sensor
installed, and either upload the files or
provide a link to them.</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Regards,</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Larry</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1
1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_x_xmsonormal"><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
<a href="mailto:cheng@jlab.org"
moz-do-not-send="true"><cheng@jlab.org></a>
<br>
<b>Sent:</b> Friday, March 12, 2021 2:22 PM<br>
<b>To:</b> Larry King <a
href="mailto:king@jlab.org"
moz-do-not-send="true"><king@jlab.org></a>;
Peter Owen
<a href="mailto:powen@jlab.org"
moz-do-not-send="true"><powen@jlab.org></a><br>
<b>Subject:</b> Re: SNS PPU SEC 01 vendor
docs review</span></p>
</div>
</div>
<p class="x_x_xmsonormal"> </p>
<p class="x_x_xmsonormal"
style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">Hi
Larry and Peter,<br>
<br>
I am working on a new revision of the
SNSPPU-CMA-INSP-SEC traveler and the first
version of SNSPPU-CMA-INSP-REC. Each SEC has 2
Cernox sensors and each REC has 10. Do you think
it is necessary to attach full cal curves to the
CMA-INSP travelers? Maybe they are more
appropriate to include in the CM testing
traveler?<br>
<br>
Thanks,<br>
Gary</span></p>
<div>
<p class="x_x_xmsonormal">On 3/11/2021 3:40 PM,
Larry King wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;
margin-bottom:5.0pt">
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Hi Peter,</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">I was looking for the Cernox
curves for the 2 sensors in the SEC 01 end
can. I found the spreadsheet of all of the
room temperature values,</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><a
href="https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-239158/Nominal%20Cernox%20Values.xlsx"
moz-do-not-send="true">https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-239158/Nominal%20Cernox%20Values.xlsx</a></span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">and I assume those data points
were taken from the full cal curves, but I
don’t see the cal curves in the traveler.</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"><a
href="https://pansophy.jlab.org/pansophy/Travelers/TRAVELER_FORM.cfm?project=SNSPPU&area=SNSPPU&system=CMA&TRAV_ID=SNSPPU-CMA-SEC-INSP&TRAV_REVISION=R2&page=1&maxpage=5&TRAV_SEQ_NUM=1&ncr_num=.&travstat=n&serialnum=001&SN=001&SNType=SECSN"
moz-do-not-send="true">https://pansophy.jlab.org/pansophy/Travelers/TRAVELER_FORM.cfm?project=SNSPPU&area=SNSPPU&system=CMA&TRAV_ID=SNSPPU-CMA-SEC-INSP&TRAV_REVISION=R2&page=1&maxpage=5&TRAV_SEQ_NUM=1&ncr_num=.&travstat=n&serialnum=001&SN=001&SNType=SECSN</a></span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">They’re also not in the
vendor-received document dump/pdf pile. Do
you have them all in one big folder
somewhere?
</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">They will need to be available
for CMTF cooldowns, and delivered to ORNL. I
would prefer that we loaded the relevant
curves into each traveler, but pointing to a
common folder would work, too.</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Thanks,</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D">Larry</span></p>
<p class="x_x_xmsonormal"><span
style="font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid
#E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_x_xmsonormal"><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">
Peter Owen
<a href="mailto:powen@jlab.org"
moz-do-not-send="true"><powen@jlab.org></a>
<br>
<b>Sent:</b> Thursday, March 4, 2021 2:08
PM<br>
<b>To:</b> Gary Cheng <a
href="mailto:cheng@jlab.org"
moz-do-not-send="true"><cheng@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 SEC 01 vendor
docs review</span></p>
</div>
</div>
<p class="x_x_xmsonormal"> </p>
<div>
<p class="x_x_xmsonormal"><span
style="font-family:"Calibri",sans-serif;
color:black">Hi Gary,</span></p>
</div>
<div>
<p class="x_x_xmsonormal"><span
style="font-family:"Calibri",sans-serif;
color:black"> </span></p>
</div>
<div>
<p class="x_x_xmsonormal"><span
style="font-family:"Calibri",sans-serif;
color:black">I think Meyer had their
instrument set to kilo-ohms rather than ohms
on 10/17/20, so the numbers are 1/1000th of
what I expect. Other than that, the
measurements look good. I only saw data for
two sensors, 149779 and 149777. Are there
other sensors to check?</span></p>
</div>
<div>
<p class="x_x_xmsonormal"><span
style="font-family:"Calibri",sans-serif;
color:black"> </span></p>
</div>
<div>
<p class="x_x_xmsonormal"><span
style="font-family:"Calibri",sans-serif;
color:black">Peter</span></p>
</div>
<div class="x_x_MsoNormal"
style="text-align:center" align="center">
<hr width="98%" size="2" align="center">
</div>
<div id="x_x_x_divRplyFwdMsg">
<p class="x_x_xmsonormal"><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> Thursday, March 4, 2021 8:19 AM<br>
<b>To:</b> Kurt Macha <<a
href="mailto:macha@jlab.org"
moz-do-not-send="true">macha@jlab.org</a>>;
Jenord Alston <<a
href="mailto:jalston@jlab.org"
moz-do-not-send="true">jalston@jlab.org</a>>;
Mark Wiseman <<a
href="mailto:wiseman@jlab.org"
moz-do-not-send="true">wiseman@jlab.org</a>>;
Peter Owen <<a
href="mailto:powen@jlab.org"
moz-do-not-send="true">powen@jlab.org</a>>;
John Fischer <<a
href="mailto:fischer@jlab.org"
moz-do-not-send="true">fischer@jlab.org</a>><br>
<b>Cc:</b> Larry King <<a
href="mailto:king@jlab.org"
moz-do-not-send="true">king@jlab.org</a>>;
Naeem Huque <<a
href="mailto:huque@jlab.org"
moz-do-not-send="true">huque@jlab.org</a>>;
Ed Daly <<a href="mailto:edaly@jlab.org"
moz-do-not-send="true">edaly@jlab.org</a>>;
Melissa Torres <<a
href="mailto:torres@jlab.org"
moz-do-not-send="true">torres@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>>;
Matt Marchlik <<a
href="mailto:marchlik@jlab.org"
moz-do-not-send="true">marchlik@jlab.org</a>><br>
<b>Subject:</b> Re: SNS PPU SEC 01 vendor
docs review</span> </p>
<div>
<p class="x_x_xmsonormal"> </p>
</div>
</div>
<div>
<p class="x_x_xmsonormal"
style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">Dear
all,<br>
<br>
This is a reminder that vendor docs need to
be reviewed. Your comments will be shared
with the vendor so changes will be made in
future documentation pacakges.<br>
Jenord has made his comments on the welding
docs. <br>
Here is the list of lead reviewers and the
backups:<br>
<br>
Sections 1, 2 & 6 --- Gary
Cheng/Daly/Marchlik<br>
Section 3 --- Macha/Fischer/Cheng<br>
Section 4 --- Fischer/Naeem/Cheng<br>
Section 5 --- Alston/Fischer<br>
Section 7 --- Owen/King<br>
<br>
Thanks,<br>
Gary<br>
<br>
<br>
</span></p>
<div>
<p class="x_x_xmsonormal">On 2/24/2021 11:45
AM, Gary Cheng wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;
margin-bottom:5.0pt">
<p class="x_x_xmsonormal"
style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">For
folks who need charge code, please use
PUSECP for supply end cans and PUREPR for
return end cans<br>
Thanks!<br>
Gary</span></p>
<div>
<p class="x_x_xmsonormal">On 2/24/2021 11:30
AM, Gary Cheng wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;
margin-bottom:5.0pt">
<p class="x_x_xmsonormal"
style="margin-bottom:12.0pt"><span
style="font-family:"Calibri",sans-serif">Hi
all,<br>
<br>
I need your help to review SEC 01 vendor
documents that can be found at
M:\SNS_PPU\Procurement\VendorDocuments\5_End
Cans\SEC 01<br>
<img id="x_x_x__x005f_x0000_i1026"
class="" style="width:4.552in;
height:1.9166in"
data-outlook-trace="F:2|T:2"
src="cid:part33.89431055.7074E4BA@jlab.org"
width="437" height="184" border="0"><br>
<br>
Note that the first file has everything
in it. I split the sections to make it
easier for you to find the relevant
docs. Here is how the sections would be
divided to each reviewer(s), with
primary/backup:<br>
<br>
Sections 1, 2 & 6 --- Gary
Cheng/Daly/Marchlik<br>
Section 3 --- Macha/Fischer/Cheng<br>
Section 4 --- Fischer/Naeem/Cheng<br>
Section 5 --- Alston/Fischer<br>
Section 7 --- Owen/King<br>
<br>
You are also expected to check docs for
SEC 02-07 and REC 01-07. Once relevant
travelers are open, I will remind you to
fill up the traveler's vendor doc review
step.
<br>
<br>
FYI, drawings and SOW can be found at
M:\SNS_PPU\Procurement\Info for
Procurement Packages\End Can. The SOW
defines what we expect the vendor to
submit. If you have questions, please
let me know.
<br>
<br>
We need to feed back to the vendor asap
on missing/incorrect docs. So I would
appreciate if you can look through the
relevant docs and feedback to me by end
of Friday 2/26 or let me know when you
can finish.
<br>
<br>
Thanks,<br>
Gary<br>
<br>
<br>
<br>
<br>
</span></p>
</blockquote>
<p class="x_x_xmsonormal"> </p>
</blockquote>
<p class="x_x_xmsonormal"> </p>
</div>
</blockquote>
<p class="x_x_xmsonormal"> </p>
</div>
</blockquote>
<p class="x_x_MsoNormal"> </p>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
<br>
</body>
</html>