[Global] [EXTERNAL] Work Order Usage and ALARA Plans

[Meldrum III, William H]

We occasionally use the WR Validate function to force workers to enter a valid WO in the correct format. It does create a bit of havoc at the login kiosks until the crews get the hang of it. If extra tasks are added to the WO we have to go in and assign the RWP in Nuclear Asset Suite. (Which is a good way to catch the tasks they forget to tell us about.) As far as I know it only works for WO Tasks, not Work Requests (despite the name) or schedule items. For some reason Sentinel refers to Work Orders as Work Requests, but only recognizes the 10 digit WO/Task# format.

Sample ALARA Plan attached.

[cid:image005.png at 01DB82A5.CAECE8A0]

Bill Meldrum
Oconee Nuclear Station
RP/ALARA
x 3204

From: Global <global-bounces at list.rpalara.org> On Behalf Of Doll, Linda L. via Global
Sent: Wednesday, February 19, 2025 7:54 AM
To: global at list.rpalara.org
Subject: [EXTERNAL] [Global] Work Order Usage and ALARA Plans

*** CAUTION! EXTERNAL SENDER *** STOP. ASSESS. VERIFY!! Were you expecting this email? Are grammar and spelling correct? Does the content make sense? Can you verify the sender? If suspicious report it, then do not click links, open attachments or enter your ID or password.
Good morning!!

There has been a struggle at our station for personnel to use the correct work order number when logging into the RCA.  This is especially true during outages.  This has made it difficult to accurately track the dose for each RWP / Task.  What processes does your station employ to ensure the correct work order usage?

What program does your station use to track dose?  At Salem we use Sentinel.  I believe there is a way for work orders to be imported into Sentinel preventing users from entering the wrong and / or invalid work order on an RWP / Task.  Does any other station use this method?  If so, could you inform me on how to accomplish this?  If work comes in to the outage after everything has been downloaded, how is that done?  Is there a way to schedule updates or is it done manually?  If the work group is working to a number that is not a work order (ie., a notification or a phone number) how is that accounted for?

Secondly:  What information do you include in your ALARA Plans?  We are looking to align with the industry in the contents of our AP's.  If it isn't too much of an inconvenience, could you send a copy of one of your AP's?

Thank you in advance for your response and help.

Have a great day!!

[An orange arrow pointing up    Description automatically generated with low confidence]

Linda Doll | Salem ALARA
T. +1.856-339-2057
Linda.doll at pseg.com<mailto:Linda.doll at pseg.com>

[Logo, company name    Description automatically generated]


Toast Masters President - Atomic Orators

'I can accept failure.  Everyone fails at something.  But I can't accept not trying.' - Michael Jordan

The information contained in this e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, or a person designated as responsible for delivering such messages to the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, in whole or in part, without written authorization from PSEG. This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. This notice is included in all e-mail messages leaving PSEG. Thank you for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 2310 bytes
Desc: image003.gif
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 129936 bytes
Desc: image005.png
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1503 bytes
Desc: image006.png
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 2326 bytes
Desc: image007.jpg
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LPSW Pipe RWP 1092 ALARA Plan.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 41702 bytes
Desc: LPSW Pipe RWP 1092 ALARA Plan.docx
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LPSW Piping Est.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 5017913 bytes
Desc: LPSW Piping Est.xlsx
URL: <http://list.rpalara.org/pipermail/global_list.rpalara.org/attachments/20250219/c426d3e6/attachment-0001.xlsx>