[Pansophy] EIC197 PEP Traceability Form

[Philip Denny]

My translation,

Its up to the project to what parts they want to have traceable and how far into the production process they want to trace. My program does not require 100% traceability.

BTW, at some point soon I will demand inventory and/or PEP procedure edits to require the forms for production traceability and serialization be mandatory.

Phil
________________________________
From: Ashley Mitchell <ashleya at jlab.org>
Sent: Wednesday, February 12, 2025 11:45 AM
To: Naeem Huque <huque at jlab.org>; Allen Samuels <samuels at jlab.org>; Justine Cox <blumer at jlab.org>; Shyamala Shanmugasundaram <shanmug at jlab.org>; John Buttles <buttles at jlab.org>; Philip Denny <denny at jlab.org>
Cc: Tony Reilly <areilly at jlab.org>; pansophy <pansophy at jlab.org>; srfinv at jlab.org <srfinv at jlab.org>; Zack Conway <conway at jlab.org>
Subject: Re: EIC197 PEP Traceability Form


Naeem,

We were told the DVC cavities for both EIC 197 and 591SC were QMS projects, so they need to follow the project requirements.  If the DVCs are not a project and we want to treat them as service requests like we do with S&T work, then I need to be told that so we stop treating them like projects.

As for the language, the form itself is not specifically required anywhere that I can find, but a traceability plan is required and Phil's form makes it easy to capture the information needed for the plan.

>From PEP template:
[cid:4a62254b-5a39-434f-b403-5f243b7f9e84]


>From Inventory & Traceability procedure SRF-09-PR-003:
[cid:7de9af9f-c5dd-4d53-a919-80cd077a2185]

Your PEP for EIC197 does not address traceability:
[cid:b32941d8-e22b-4ad2-bfd3-25050eee9ffc]

- Ashley
________________________________
From: Naeem Huque <huque at jlab.org>
Sent: Wednesday, February 12, 2025 11:12 AM
To: Allen Samuels <samuels at jlab.org>; Justine Cox <blumer at jlab.org>; Shyamala Shanmugasundaram <shanmug at jlab.org>; John Buttles <buttles at jlab.org>; Philip Denny <denny at jlab.org>
Cc: Ashley Mitchell <ashleya at jlab.org>; Tony Reilly <areilly at jlab.org>; pansophy <pansophy at jlab.org>; srfinv at jlab.org <srfinv at jlab.org>; Zack Conway <conway at jlab.org>
Subject: Re: EIC197 PEP Traceability Form

Hi Allen,

>From my conversation with Phil, the traceability form for EIC197 DVC is not mandatory as this is not a production cavity. I will complete the form to make tracking easier, and we will provide you with acronyms as needed, but the presence of the form cannot stop work on the project.

I would also like to request the language in our processes that states that the traceability form is a requirement, which justifies the work stopping.

Thanks,
Naeem
________________________________
From: Allen Samuels <samuels at jlab.org>
Sent: Wednesday, February 12, 2025 11:05 AM
To: Naeem Huque <huque at jlab.org>; Justine Cox <blumer at jlab.org>; Shyamala Shanmugasundaram <shanmug at jlab.org>; John Buttles <buttles at jlab.org>
Cc: Ashley Mitchell <ashleya at jlab.org>; Tony Reilly <areilly at jlab.org>; pansophy <pansophy at jlab.org>; srfinv at jlab.org <srfinv at jlab.org>
Subject: EIC197 PEP Traceability Form

Naeem,

While working on the EIC197 travelers, it came to my attention that the PEP traceability form for this project has not been completed. As any acronyms listed need to be in our system first, this is something that needs to go live before any further software or traveler work is done on the project. Pansophy has created a preliminary draft form that I've attached to this email. Please review, validate our work, and update or add any entries that need it. Anything that's highlighted is something that needs to be paid closer attention to, as are any empty entries.

As a courtesy, I can route the two EIC197 travelers your team is working on if they're ready before this gets approved. But they need to be in compliance with the PEP, and I will hold off on putting them in pansophy until the PEP is live.

If you have any questions, feel free to send them to pansophy.

Thank you for your time,

Allen Samuels
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250212/bfea209e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 87327 bytes
Desc: image.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250212/bfea209e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 172231 bytes
Desc: image.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250212/bfea209e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 32359 bytes
Desc: image.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250212/bfea209e/attachment-0005.png>