[Pansophy] Fw: L2HE to L2RB Procedures (request to not update from AdamG)

[Valerie Bookwalter]

Tony,

I understand that Adam and the entire Production Floor doesn't want to do documentation for the L2RB project, but I need to know to what extent is the current procedure going to be adapted to fulfill their needs?
-----------------------------------

>From SRF-07-PR-001 Document Management Procedure R4<https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-296879/SRF-07-PR-001%20Document%20Management%20Procedure%20R4.pdf>
section 5.10 Periodic Review

Project documents are required to be revised when facility or procedural changes warrant and when a new project is established.

---------------------------------------------

This, to me, means that the procedures referenced in a traveler or procedure should be self-contained within the project. Links to previous projects, closed projects, or unrelated projects, would not be acceptable.

Note that once a project is closed, the related documented information is no longer considered active or valid.

I don't want to rewrite my procedure again (nor right now), so how should this be handled. I am unsupported in trying to get documents aligned with ISO/SRFOPS QMS standards.
I may have too high of a standard for what production is even capable of doing.

But having "excuses" or "exceptions" for each person or project is too much to support, both functionally and in audits.

Please advise on your choice in this matter.



Valerie Bookwalter

Jefferson Lab, Accelerator Dept. SRFOPS

SRFOPS Software Systems Group

bookwalt at jlab.org<mailto:bookwalt at jlab.org>

757-269-5802






________________________________
From: Pansophy <pansophy-bounces at jlab.org> on behalf of Adam Grabowski via Pansophy <pansophy at jlab.org>
Sent: Friday, June 6, 2025 11:16 AM
To: Allen Samuels <samuels at jlab.org>; Tony Reilly <areilly at jlab.org>; Ashley Mitchell <ashleya at jlab.org>; John Fischer <fischer at jlab.org>
Cc: pansophy <pansophy at jlab.org>
Subject: Re: [Pansophy] L2HE to L2RB Procedures

All,

I think most of the L2RB documents should reference L2HE documents. The L2RB documents were not made from scratch, most of them are direct copies and just "rebranded" L2RB. As I understand it, the requirement was to make new travelers and procedures with the new project title, this is being done, I think the references provided a starting point if there are questions in the future about these new travelers and procedures.


Adam Grabowski

SRF Test Engineer, L2HE Project CAM

Jefferson Lab
600 KELVIN DR Suite # 8

Mail Stop 55H
Newport News, VA 23606

O: 757-269-7665

C: 360-320-7003

E: adamg at jlab.org

________________________________
From: Allen Samuels <samuels at jlab.org>
Sent: Thursday, June 5, 2025 1:56 PM
To: Tony Reilly <areilly at jlab.org>; Ashley Mitchell <ashleya at jlab.org>; John Fischer <fischer at jlab.org>
Cc: Adam Grabowski <adamg at jlab.org>; pansophy <pansophy at jlab.org>
Subject: L2HE to L2RB Procedures

Good afternoon, all,

I was working on the L2RB-PR-CMA-WS5-DISA-R1<https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-301140/L2RB-PR-CMA-WS5-DISA.docx> procedure for John when I noticed it was referencing an L2HE procedure. Following the trail, I found that each procedure had another linked L2HE procedure. I was instructed to reach out to you all to ask what to do about them. I took the liberty of converting two of them, which I've attached to this email. The other two I found are L2HE-PR-CMA-FPCW-INSP-R1<https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-244733/L2HE-PR-CMA-FPCW-INSP-R1.pdf> and LCLSII-HE Fundamental Power Coupler ESD<https://jlabdoc.jlab.org/docushare/dsweb/Get/Document-242797/LCLSII-HE-1.2-ES-0059.pdf>. What are your thoughts on this? Should they be ported over to L2RB, or should some alternative solution be implemented?

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250606/fef9b970/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250606/fef9b970/attachment.txt>