[Pansophy] SNS PPU SEC 01 vendor docs review

Gary Cheng cheng at jlab.org
Tue Apr 6 11:46:45 EDT 2021


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).

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 doin regard to Cernox sensors & data 
curves, responsible parties are identified:

1. Create a dropdown list of the S/Ns for all 84 sensors that were sent 
to the end can vendor ----*SRFINV team or Pansophy team*
2. For each SEC or REC, check vendor documentation for sensors actually 
installed. Also verify the labels on wires are correct. --- *SRF 
Instrumentation team*
3. Traveler will have a fileupload for each Cernox sensor. That is, 
SNSPPU-CMA-INSP-SEC will have 2 dropdowns and 2 fileuploads, 
SNSPPU-CMA-INSP-REC will have 10 dropdowns and 10 fileuploads. ---- 
*Gary Cheng*
4. Select the Cernox S/N and upload the corresponding curve. --- *SRF 
Instrumentation team*

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.

Thanks,
Gary

On 3/16/2021 3:07 PM, Peter Owen wrote:
> 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.
>
> 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.
>
> Peter
> ------------------------------------------------------------------------
> *From:* Larry King <king at jlab.org>
> *Sent:* Tuesday, March 16, 2021 2:28 PM
> *To:* Peter Owen <powen at jlab.org>; Gary Cheng <cheng at jlab.org>
> *Subject:* RE: SNS PPU SEC 01 vendor docs review
>
> Hi Peter,
>
> 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.
>
> -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.
>
> -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.
>
> -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.
>
> -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.
>
> Thoughts?
>
> Regards,
>
> Larry
>
> *From:*Peter Owen <powen at jlab.org>
> *Sent:* Tuesday, March 16, 2021 1:35 PM
> *To:* Gary Cheng <cheng at jlab.org>; Larry King <king at jlab.org>
> *Subject:* Re: SNS PPU SEC 01 vendor docs review
>
> The curves are saved in M:\SNS_PPU\CM Production\Cernox Curves\All Cernox
>
> 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?
>
> Peter
>
> ------------------------------------------------------------------------
>
> *From:*Gary Cheng <cheng at jlab.org <mailto:cheng at jlab.org>>
> *Sent:* Tuesday, March 16, 2021 11:37 AM
> *To:* Larry King <king at jlab.org <mailto:king at jlab.org>>; Peter Owen 
> <powen at jlab.org <mailto:powen at jlab.org>>
> *Subject:* Re: SNS PPU SEC 01 vendor docs review
>
> Hi Larry,
>
> 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:
>
>
>
> 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.
>
> Thanks,
> Gary
>
> On 3/15/2021 4:59 PM, Larry King wrote:
>
>     Hi Gary,
>
>     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.
>
>     Regards,
>
>     Larry
>
>     *From:*Gary Cheng <cheng at jlab.org> <mailto:cheng at jlab.org>
>     *Sent:* Friday, March 12, 2021 2:22 PM
>     *To:* Larry King <king at jlab.org> <mailto:king at jlab.org>; Peter
>     Owen <powen at jlab.org> <mailto:powen at jlab.org>
>     *Subject:* Re: SNS PPU SEC 01 vendor docs review
>
>     Hi Larry and Peter,
>
>     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?
>
>     Thanks,
>     Gary
>
>     On 3/11/2021 3:40 PM, Larry King wrote:
>
>         Hi Peter,
>
>         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,
>
>         https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-239158/Nominal%20Cernox%20Values.xlsx
>         <https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-239158/Nominal%20Cernox%20Values.xlsx>
>
>         and I assume those data points were taken from the full cal
>         curves, but I don’t see the cal curves in the traveler.
>
>         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
>         <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>
>
>         They’re also not in the vendor-received document dump/pdf
>         pile.  Do you have them all in one big folder somewhere?
>
>         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.
>
>         Thanks,
>
>         Larry
>
>         *From:*Peter Owen <powen at jlab.org> <mailto:powen at jlab.org>
>         *Sent:* Thursday, March 4, 2021 2:08 PM
>         *To:* Gary Cheng <cheng at jlab.org> <mailto:cheng at jlab.org>;
>         Larry King <king at jlab.org> <mailto:king at jlab.org>
>         *Subject:* Re: SNS PPU SEC 01 vendor docs review
>
>         Hi Gary,
>
>         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?
>
>         Peter
>
>         ------------------------------------------------------------------------
>
>         *From:*Gary Cheng <cheng at jlab.org <mailto:cheng at jlab.org>>
>         *Sent:* Thursday, March 4, 2021 8:19 AM
>         *To:* Kurt Macha <macha at jlab.org <mailto:macha at jlab.org>>;
>         Jenord Alston <jalston at jlab.org <mailto:jalston at jlab.org>>;
>         Mark Wiseman <wiseman at jlab.org <mailto:wiseman at jlab.org>>;
>         Peter Owen <powen at jlab.org <mailto:powen at jlab.org>>; John
>         Fischer <fischer at jlab.org <mailto:fischer at jlab.org>>
>         *Cc:* Larry King <king at jlab.org <mailto:king at jlab.org>>; Naeem
>         Huque <huque at jlab.org <mailto:huque at jlab.org>>; Ed Daly
>         <edaly at jlab.org <mailto:edaly at jlab.org>>; Melissa Torres
>         <torres at jlab.org <mailto:torres at jlab.org>>; srfinv at jlab.org
>         <mailto:srfinv at jlab.org> <srfinv at jlab.org
>         <mailto:srfinv at jlab.org>>; Matt Marchlik <marchlik at jlab.org
>         <mailto:marchlik at jlab.org>>
>         *Subject:* Re: SNS PPU SEC 01 vendor docs review
>
>         Dear all,
>
>         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.
>         Jenord has made his comments on the welding docs.
>         Here is the list of lead reviewers and the backups:
>
>         Sections 1, 2 & 6 --- Gary Cheng/Daly/Marchlik
>         Section 3 --- Macha/Fischer/Cheng
>         Section 4 --- Fischer/Naeem/Cheng
>         Section 5 --- Alston/Fischer
>         Section 7 --- Owen/King
>
>         Thanks,
>         Gary
>
>
>         On 2/24/2021 11:45 AM, Gary Cheng wrote:
>
>             For folks who need charge code, please use PUSECP for
>             supply end cans and PUREPR for return end cans
>             Thanks!
>             Gary
>
>             On 2/24/2021 11:30 AM, Gary Cheng wrote:
>
>                 Hi all,
>
>                 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
>
>
>                 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:
>
>                 Sections 1, 2 & 6 --- Gary Cheng/Daly/Marchlik
>                 Section 3 --- Macha/Fischer/Cheng
>                 Section 4 --- Fischer/Naeem/Cheng
>                 Section 5 --- Alston/Fischer
>                 Section 7 --- Owen/King
>
>                 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.
>
>                 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.
>
>                 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.
>
>                 Thanks,
>                 Gary
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20210406/2b5339ed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4554 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20210406/2b5339ed/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 10667 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20210406/2b5339ed/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 9944 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20210406/2b5339ed/attachment-0005.png>


More information about the Pansophy mailing list