<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Naeem,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am attaching R2 of your traveler for your review.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Valerie Bookwalter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Jefferson Lab, ACCEL<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">SRF Operations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">SROPS Software Systems Group<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">1-757-269-5802 (OFFICE – currently working offsite)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Valerie Bookwalter <bookwalt@jlab.org> <br>
<b>Sent:</b> Thursday, February 2, 2023 11:36 AM<br>
<b>To:</b> Naeem Huque <huque@jlab.org><br>
<b>Cc:</b> pansophy <pansophy@jlab.org>; Tony Reilly <areilly@jlab.org>; Ed Daly <edaly@jlab.org>; Jacob Harris <jharris@jlab.org>; Valerie Bookwalter <bookwalt@jlab.org><br>
<b>Subject:</b> RE: AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">Naeem,<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">First, I need to let you know that I had to recant the changes to your traveler as just fixing the “typo” does not fix the problem you are having. I will explain later.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:12.0pt;color:#0070C0">If a revision is made to a traveler, then it will only apply to future instances of that traveler, correct?<o:p></o:p></span></i></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">That is correct and hasn’t changed since travelers were first introduced in 2001. Therefore, it is so important the travelers are reviewed and approved prior to our uploading
to the web. We do have a way of updating the revision on previously entered information, which still meets our ISO records requirements.</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:12.0pt;color:#0070C0">Could you please send an excerpt from our traveler procedure which states that new revisions need to be made for typos in a traveler?<o:p></o:p></span></i></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">This is not just a “typo”. This is an actual form input field and affects many aspects of the Pansophy system including database changes. Additional changes are needed
in the database, hence the need for a new revision. You and your reviewers signed this version of the traveler as being accurate and correct. Once the approval process is completed and the traveler uploaded to the web any change requires a new revision. This
has been standard practice since 2001 and followed by all work centers and projects.
<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:12.0pt;color:#0070C0">I would like to be working against rules that we have in writing and approved, and not ones that are made up as we go along.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">To imply that the Software Team does not work within standards, nor consider the affect these changes have to traveler authors underestimates the amount of time and thought
put into producing the traveler system and supporting SRF Operations as a whole.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:12.0pt;color:#0070C0">Making the process more arduous will make authors less likely to fix instructions on travelers that are incorrect or unclear, choosing to instead just let people know
verbally or by email. This is how mistakes can happen on the floor. If we want this system to work smoothly, we can't add obstacles without looking at the bigger picture.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">This is a very good reason why authors and approvers should be carefully selected and that each should read, review, and correct any mistakes in a traveler prior to approval.
This is also, now, a part of SRF OPS quality management system that work control documents fall to project coordinators and work center leads to ensure accuracy and completeness. To state that, because the software team will not “fix your typo”, will cause
obstacles and mistakes on the floor, seems a bit exaggerated for this discussion and may be better discussed separately.</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:12.0pt;color:#0070C0">If this is currently spelled out in the procedure, then I would request our management to review it for a revision.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">If you feel we have somehow made this an arduous problem and feel it necessary to update our procedures, then feel free to contact Tony and have him address this with me.</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">If you would like to create a new revision of your traveler with the updated entry field, then we can work to expedite its approval and upload to the web. This is the standard
processing for a traveler and the best way to keep the database and all related files correlated and correct. This is followed by all projects and work centers. For expediting the process, I have already generated a R2 for your traveler.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">In the future, if a new project is being started, the inclusion of the Software Team in the WCD list and Acronyms sooner can help to mitigate such problems. The PRIMeS
entry of components and acronyms is not directly reflected in the Traveler system, as I have spoken to you about before. We, the software team, are working on ways to better align the two systems and create a way to look for such “typos” when travelers are
converted, so that we might catch such things sooner in the process. If you would like to help us in setting up such a system, then I would gladly hear any ideas and proposals you have which can help. The “fabrication projects” vary from “production projects”
and we are working to come up with solutions and ideas to better support these types of projects. I have already spoken with Tony about this need for growth in the Software Systems, again you support in this discuss would be appreciated.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">I hope this answers any questions you may have had, and I personally hope that we can find a way to work together to make “this system” as smooth as possible for all involved.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Valerie Bookwalter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Jefferson Lab, ACCEL<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">SRF Operations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">SROPS Software Systems Group<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">1-757-269-5802 (OFFICE – currently working offsite)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Naeem Huque <<a href="mailto:huque@jlab.org">huque@jlab.org</a>>
<br>
<b>Sent:</b> Wednesday, February 1, 2023 11:47 AM<br>
<b>To:</b> Valerie Bookwalter <<a href="mailto:bookwalt@jlab.org">bookwalt@jlab.org</a>><br>
<b>Cc:</b> pansophy <<a href="mailto:pansophy@jlab.org">pansophy@jlab.org</a>>; Tony Reilly <<a href="mailto:areilly@jlab.org">areilly@jlab.org</a>>; Ed Daly <<a href="mailto:edaly@jlab.org">edaly@jlab.org</a>>; Jacob Harris <<a href="mailto:jharris@jlab.org">jharris@jlab.org</a>><br>
<b>Subject:</b> Re: AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">Hi Valerie,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">If a revision is made to a traveler, then it will only apply to future instances of that traveler, correct? If so, that won't work for me as the changes are needed to make
the current instances function properly, and they are already in progress. I don't have any plans of opening new travelers for this portion of the project.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">Could you please send an excerpt from our traveler procedure which states that new revisions need to be made for typos in a traveler? If this is not an actual requirement,
then it seems a lot of extra work for a lot of people to make a change that does not affect the intent of the traveler (this includes the initiator as well as your group and the work center leads/techs reviewing the traveler). I can understand holding off
on typos that just affect clarity, but that too has its drawbacks. Making the process more arduous will make authors less likely to fix instructions on travelers that are incorrect or unclear, choosing to instead just let people know verbally or by email.
This is how mistakes can happen on the floor. If we want this system to work smoothly, we can't add obstacles without looking at the bigger picture.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">My feedback for the Pansophy Request Form is that it should include an entry for something like this. It would be a way to track and formalize such changes. I believe this
is the common-sense way to proceed, without causing work stoppages. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">If this is currently spelled out in the procedure, then I would request our management to review it for a revision. I would like to be working against rules that we have
in writing and approved, and not ones that are made up as we go along.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">I apologize that there is a (several) typo in the traveler. While I try to make it as accurate as possible, they do happen from time to time, and I am sure I'm not the
only one making them.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black">Naeem<o:p></o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Valerie Bookwalter <<a href="mailto:bookwalt@jlab.org">bookwalt@jlab.org</a>><br>
<b>Sent:</b> Wednesday, February 1, 2023 9:38 AM<br>
<b>To:</b> Naeem Huque <<a href="mailto:huque@jlab.org">huque@jlab.org</a>><br>
<b>Cc:</b> pansophy <<a href="mailto:pansophy@jlab.org">pansophy@jlab.org</a>>; Tony Reilly <<a href="mailto:areilly@jlab.org">areilly@jlab.org</a>>; Ed Daly <<a href="mailto:edaly@jlab.org">edaly@jlab.org</a>><br>
<b>Subject:</b> AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal">Naeem,<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">I have completed your request to change HHOOKSN to HOOKSN.<o:p></o:p></p>
<p class="xmsonormal">I did this behind the scenes, however we can not continue to work this way.<o:p></o:p></p>
<p class="xmsonormal"><b>In the future, especially when data fields are wrong, a new revision must be generated.</b><o:p></o:p></p>
<p class="xmsonormal">This is the only way to ensure the entire system is kept in sync and keeps us straight in our ISO Records management.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Valerie<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal"><img border="0" width="444" height="241" style="width:4.625in;height:2.5083in" id="x_Picture_x0020_1" src="cid:image001.png@01D936FD.46E55240"><o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;color:#1F497D">Valerie Bookwalter</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;color:#1F497D">Jefferson Lab, ACCEL</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;color:#1F497D">SRF Operations</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;color:#1F497D">SROPS Software Systems Group</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:12.0pt;color:#1F497D">1-757-269-5802 (OFFICE – currently working offsite)</span><o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>