<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you for the information Megan!!</div>
<div class="elementToProof" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</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> Megan McDonald <megan@jlab.org><br>
<b>Sent:</b> Thursday, April 3, 2025 12:29<br>
<b>To:</b> pansophy <pansophy@jlab.org>; David Savransky <dsavr@jlab.org><br>
<b>Cc:</b> Ashley Mitchell <ashleya@jlab.org>; Tony Reilly <areilly@jlab.org><br>
<b>Subject:</b> Re: WCD for EIC591</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Hi David,</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:disc">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">Will we require a separate incoming inspection traveler for a tanked and bare cavity?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">If the inspection steps are the same, we can include a radio button in the first step to select if its tanked or bare</div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">Most of the cleanroom components will require some form of cleaning outside of de-grease, whether HPR, Bake or other. Would it make sense to have two sets of chemistry traveler for these actives, one set focused on the
cavity and other set focused on the other 4-5 cleanroom components, or just have one for everything?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">We can do COMP chemistry travelers. This way it is one task but can be used by multiple components. Take a look at L2HE-CHEM-COMP-DEGR for an example. As far as pulling the cavity out for a separate one, I am not familiar
with the process and would probably be best to consult the chemistry group on this</div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">For Components that might have exactly the same traveler but a different component ID, would we need a traveler per ID?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">For example, we will receive a varity of RF seals that will have to be tracked ranging from 6" to 16" in size. Can we have a single inspection traveler that covers all of them or would each size need its own traveler?</div>
</li><li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">I would say this depends on how these components will be serialized and if they each have their own acronym. Once that is determined, we can decide how to move forward. For now, I would plan on them each needing their
own. I mainly say this because there are likely different measurements needed and different drawings to be compared to. However, if they just need a visual inspection, we could maybe do a component type on this. Open for discussion on it</div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">Whilst most of cryomodule will be the same between the HSR and ESR cryomodule, the HSR CM might have slight differences (i.e. a added piezo). For such a difference, would it make sense just to have a check box in the
traveler for which one was which when it is built, or would a separate traveler be needed?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">I think in this situation it would be preferred for them to be separate travelers but I am open to discussing this </div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">Is there a good rule of thumb of who else, other than the people listed on the approval of the traveler or procedure and the work center leads, should be listed on the D3 and NCR lists?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">We request that there is more than one dispositioner so that there isn't a bottleneck with that. Project people and/or supervisor is also a good add, especially on informative</div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<div style="direction:ltr; margin:0px">For the inventory travelers, should I add all of the line items for that now, or can we get this document signed off with the assumption that we will add all of these in the future?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; text-align:left; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<div style="direction:ltr; margin:0px">Please list necessary inventory travelers in the WCD so we can go ahead and get started on those. Inventory travelers are ONLY needed if there are documents that come with the component that need to be uploaded by the
INV staff. Think CERNOX sensors with associated calculation graphs. All received components will be uploaded to PRIMeS and can be tracked, inventory traveler or not. It would be good to consult with Mike Dickey if you have further questions on this. Keep in
mind, we handle the creation of inventory travelers (if they are needed) so they do not fall on you. </div>
</li></ul>
</ul>
<div style="direction:ltr; margin:0px; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(200,38,19)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Hope this helps! Please feel free to reach out with anymore questions</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Megan McDonald</div>
<div id="x_appendonsend" style="color:inherit"></div>
<div><br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block; width:98%">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<b>From:</b> Pansophy on behalf of David Savransky via Pansophy<br>
<b>Sent:</b> Wednesday, April 2, 2025 5:46 PM<br>
<b>To:</b> pansophy<br>
<b>Cc:</b> Ashley Mitchell; Tony Reilly<br>
<b>Subject:</b> [Pansophy] WCD for EIC591 </div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Good afternoon Valerie and Megan,</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I have attached the first draft of the WCD for the EIC 591 MHz CM (EIC591). All of line items on it will have to be reviewed as we move through our final design review and assembly readiness review, but hopefully this will serve as a starting point.</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
My few question for you as I am working through it:</div>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; margin-top:0px; margin-bottom:0px; list-style-type:disc">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">Will we require a separate incoming inspection traveler for a tanked and bare cavity?</div>
</li><li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">Most of the cleanroom components will require some form of cleaning outside of de-grease, whether HPR, Bake or other. Would it make sense to have two sets of chemistry traveler for these actives, one set focused on the cavity and
other set focused on the other 4-5 cleanroom components, or just have one for everything?</div>
</li><li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">For Components that might have exactly the same traveler but a different component ID, would we need a traveler per ID?</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="direction:ltr; margin-top:0px; margin-bottom:0px; list-style-type:circle">
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">For example, we will receive a varity of RF seals that will have to be tracked ranging from 6" to 16" in size. Can we have a single inspection traveler that covers all of them or would each size need its own traveler?</div>
</li></ul>
<li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">Whilst most of cryomodule will be the same between the HSR and ESR cryomodule,the HSR CM might have slight differences (i.e. a added piezo). For such a difference, would it make sense just to have a check box in the traveler for
which one was which when it is built, or would a separate traveler be needed?</div>
</li><li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">Is there a good rule of thumb of who else, other than the people listed on the approval of the traveler or procedure and the work center leads, should be listed on the D3 and NCR lists?</div>
</li><li style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="direction:ltr">For the inventory travelers, should I add all of the line items for that now, or can we get this document signed off with the assumption that we will add all of these in the future?</div>
</li></ul>
<div style="direction:ltr; font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_x_elementToProof" id="x_x_Signature" style="color:inherit">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Thank you,</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)">
David S.</div>
</div>
</div>
</body>
</html>