<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Calibri">Again, can someone please say something
regarding my request? <br>
Gary<br>
</font><br>
<div class="moz-cite-prefix">On 1/29/2021 11:30 AM, Gary Cheng
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f387eaca-8c7b-d6a7-9391-6e28c03f7f88@jlab.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<font face="Calibri">Did anyone looked into this request?<br>
<br>
Gary<br>
</font><br>
<div class="moz-cite-prefix">On 1/14/2021 11:34 AM, Gary Cheng
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ed364888-ad76-c84a-a1d6-5cc776484c2c@jlab.org"> <font
face="Calibri">All,<br>
<br>
In order to store the results of SNS PPU Return End Can (REC)
Heat Exchanger (HX) inspections carried out by the end can
vendor, in the REC inspection traveler, there is a step to
upload relevant docs. Hence we will need to create a new
acronym for the REC HX. It can be simply "HXSN" or "RECHXSN".
I wan't able <br>
<br>
We will receive RECs that have one HX per REC already
installed. So we do not do inspections of HX's, just want to
store the inspection reports. In fact, there are dimensional
non-conformances and weld defects that we will create NCRs
about and I will respond to them...again, the purpose is to
store the reports for future reference. <br>
<br>
The SNs for the HX's are: 29, 30, 31, 32, 33, 34 & 35.
They should appear in the dropdown list. The end can vendor
will let us know which HX is integrated into which REC that is
serialized too. <br>
<br>
Please help to create the acronym and build the dropdwon list.
Please let me know what acronym you choose.<br>
<br>
Thanks,<br>
Gary<br>
</font> </blockquote>
<br>
</blockquote>
<br>
</body>
</html>