<html>
<head>
<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>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Hi Valerie,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
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.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
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.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
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.
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
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.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
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.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Thanks,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Naeem<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> Valerie Bookwalter <bookwalt@jlab.org><br>
<b>Sent:</b> Wednesday, February 1, 2023 9:38 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><br>
<b>Subject:</b> AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal">Naeem,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I have completed your request to change HHOOKSN to HOOKSN.</p>
<p class="x_MsoNormal">I did this behind the scenes, however we can not continue to work this way.</p>
<p class="x_MsoNormal"><b>In the future, especially when data fields are wrong, a new revision must be generated.</b></p>
<p class="x_MsoNormal">This is the only way to ensure the entire system is kept in sync and keeps us straight in our ISO Records management.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Valerie</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><img width="444" height="241" id="x_Picture_x0020_1" style="width:4.625in; height:2.5083in" data-outlook-trace="F:1|T:1" src="cid:image001.png@01D93620.E1271AB0"></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:#1F497D">Valerie Bookwalter</span></p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:#1F497D">Jefferson Lab, ACCEL</span></p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:#1F497D">SRF Operations</span></p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:#1F497D">SROPS Software Systems Group</span></p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:#1F497D">1-757-269-5802 (OFFICE – currently working offsite)</span></p>
<p class="x_MsoNormal"> </p>
</div>
</div>
</body>
</html>