[Pansophy] AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN

[Naeem Huque]

Hi Valerie,

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.

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.

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.

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.

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.

Thanks,
Naeem
________________________________
From: Valerie Bookwalter <bookwalt at jlab.org>
Sent: Wednesday, February 1, 2023 9:38 AM
To: Naeem Huque <huque at jlab.org>
Cc: pansophy <pansophy at jlab.org>; Tony Reilly <areilly at jlab.org>; Ed Daly <edaly at jlab.org>
Subject: AUPPS-FAB-HHOM-ASSY sn modified HHOOKSN


Naeem,



I have completed your request to change HHOOKSN to HOOKSN.

I did this behind the scenes,  however we can not continue to work this way.

In the future, especially when data fields are wrong, a new revision must be generated.

This is the only way to ensure the entire system is kept in sync and keeps us straight in our ISO Records management.



Valerie



[cid:image001.png at 01D93620.E1271AB0]



Valerie Bookwalter

Jefferson Lab, ACCEL

SRF Operations

SROPS Software Systems Group

1-757-269-5802 (OFFICE – currently working offsite)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20230201/fd7ded0d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16765 bytes
Desc: image001.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20230201/fd7ded0d/attachment-0001.png>