[Pansophy] New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

Tiffany Ganey ganey at jlab.org
Mon Jan 22 15:31:32 EST 2024


Sounds good to me.  So that would simplify the change log to:

Release and Revision History
Rev #
Description of Changes
Change Type
Uploaded for Approval Date:
1
Initial Issue
Initial
 19 Jan 2024

Tiffany Ganey

From: Valerie Bookwalter <bookwalt at jlab.org>
Sent: Monday, January 22, 2024 3:13 PM
To: Tiffany Ganey <ganey at jlab.org>; Allen Samuels <samuels at jlab.org>
Cc: pansophy <pansophy at jlab.org>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

FYI – None of the previous versions of the ER5C_WCDRegister were ever APPROVED.
So as far as I am concerned, this would be R1 approved version.
The other versions were Mine and Allen’s attempts at figuring out what files were available.

Does this work for everyone?

Valerie

From: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Sent: Monday, January 22, 2024 3:04 PM
To: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>; Valerie Bookwalter <bookwalt at jlab.org<mailto:bookwalt at jlab.org>>
Cc: pansophy <pansophy at jlab.org<mailto:pansophy at jlab.org>>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

My proposal is that we change the Change Log to the one below – which essentially merges what was listed as revision “-“ and “1” and corrects to the dates listed in DocuShare for this document.  Looking at the Version History of the ER5C-WCDRegister.xlsx file in DocuShare, there are 5 versions listed – versions 1-4 are all uploaded at roughly the same time (8/8/2023 1:09pm through 8/9/2023 4:53pm) so I am assuming there are not significant differences between these 4 versions and they call all be considered the initial issue of the document, which we normally would call revision “1”.  The 5th version was uploaded on 9/5/2023, so I would consider this an actual revision to the initial, which we would normally call revision “2”.  I suspect that the initial version of the ER5C WCD Register was made from the C75 WCD Register, so this may be a partial source of the problem with the revision numbering.

I think Valerie should be able to help us answer this question based on any requirements in the Document Management process and to ensure no data / history is lost in the process.

In the WCD Register template (which is still in development), I plan to start all WCD Registers as Initial Issue on Revision #1.

Release and Revision History
Rev #
Description of Changes
Change Type
Uploaded for Approval Date:
1
Initial Issue by Pansophy Team adjustments to C75 Register (VDB)
Initial
9 Aug 2023
 2
Removed S. Williams, Kurt Macha, Brian Carpenter, and Bob Legg due to retirement.
Updates to multiple NCR Informative, NCR Dispositioner, and D3 names
N/A
5 Sep 2023
 3
Updated Authors, Reviewers, and Project Representatives throughout to reflect current areas of responsibility.
Remove document revision information, including revision number and historical revision information, to align with the WCD Register requirements.
Added/modified section headers.
 Major
 19 Jan 2024

Tiffany Ganey

From: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>
Sent: Monday, January 22, 2024 2:47 PM
To: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Cc: pansophy <pansophy at jlab.org<mailto:pansophy at jlab.org>>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

Tiffany,

I have made the requested changes, save for the revision number one. The reason being is I’m a little bit unsure which direction to go. With other documents like procedures and travelers, the first version of the document is revision 1. This would make for a more universal numbering system with the other documents we use. This numbering system was also used C100R WCD I routed recently. That said, we’re still getting this WCD process figured out, and you are the PEP Owner. If you think it best in this case to work with the revision numbering we have at this time, I will defer to you.

Allen

From: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Sent: Monday, January 22, 2024 12:47 PM
To: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>
Cc: pansophy <pansophy at jlab.org<mailto:pansophy at jlab.org>>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

You are calling this the 4th revision, but by the Change Log this should be Revision Number 3?  Either I think we need to shift the Change Log to start with the Initial version being “1” so that the current version is “4” or we need to call the revision number on the Header tab “3”.  The Header tab and Change Log tab Revision number should agree.  I think that since the Change Log details and previous versions existed before this new WCD Register template, that we should keep the original numbering – meaning that we should call this revision “3” on both the Header tab and the Change Log.

Document Title
ER5c WCD Register
Document Number
ER5C-RG-001
Approval Date:
19 Jan 2024
Revision Number
3
Periodic Review Date:
N/A
Project Coordinator
M. Weaks
Department Owner:
SRF Operations

The Periodic Review Date can be N/A.

The Approvers are:
[cid:image001.png at 01DA4D48.127F5610]
The Project Coordinator for ER5C is Matt Weaks, so you have all the names in the Names column right already.

If you are updating the Change Log tab, it should look like:

Release and Revision History
Rev #
Description of Changes
Change Type
Uploaded for Approval Date:
-
Initial version
Initial
13 Dec 2022
1
Pansophy Team adjustments to Register (VDB)
N/A
16 Feb 2023
 2
Removed S. Williams, Kurt Macha, Brian Carpenter, and Bob Legg due to retirement.
Updates to multiple NCR Informative, NCR Dispositioner, and D3 names
N/A
15 Sep 2023
 3
Updated Authors, Reviewers, and Project Representatives throughout to reflect current areas of responsibility.
Remove document revision information, including revision number and historical revision information, to align with the WCD Register requirements.
Added/modified section headers.
 Major
 19 Jan 2024


Tiffany Ganey

From: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>
Sent: Monday, January 22, 2024 12:06 PM
To: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Cc: pansophy <pansophy at jlab.org<mailto:pansophy at jlab.org>>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

Tiffany,

Since this is minor, I got permission to fix behind the scenes and put a note in the changelog. Before I do, please confirm that everything looks good. Since we’re messing around on this, what should the titles be for the approvers?
[cid:image002.png at 01DA4D48.127F5610]

Speaking of the changelog, what should the description of changes be? This is what it looks like right now.
[cid:image003.png at 01DA4D48.127F5610]

From: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Sent: Monday, January 22, 2024 7:19 AM
To: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>
Subject: RE: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

Allen – Matt should be listed as the Document Owner in the Header tab.  Also, the document number ER5C-RG-001 can be added.  Would you rather I disapprove the register to correct the owner, or can you update that after it has been approved?

Tiffany Ganey

From: Allen Samuels <samuels at jlab.org<mailto:samuels at jlab.org>>
Sent: Friday, January 19, 2024 3:19 PM
To: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Subject: New DocuShare document routing task (Request): ER5C Work Control Document Register_19JAN24.xlsx

You have a new DocuShare document routing task:

Subject: ER5C Work Control Document Register_19JAN24.xlsx
Date: 01/19/2024 15:18:54

To view your pending document routing tasks, click on the link below to login to DocuShare:

https://jlabdoc.jlab.org/docushare/dsweb/routing/routing_email.jsp?url=request_base.jsp&routingSlipRequestID=37760&workFlowJobName=37754
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20240122/86b52ecb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 39007 bytes
Desc: image001.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20240122/86b52ecb/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 132460 bytes
Desc: image002.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20240122/86b52ecb/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 46100 bytes
Desc: image003.png
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20240122/86b52ecb/attachment-0005.png>


More information about the Pansophy mailing list