[Global] Benchmark from a new ALARA engineer

Wed Nov 13 10:35:27 EST 2019

Jennifer Tutterow and Team:

Thank you for your questions.  DCPP RP ALARA uses similar processes for exposure forecasting.

Outage exposure forecasting:

  *   We strive to utilize the T-week process in the manner you’ve mentioned, but we are not always able to follow it because the availability of outage work orders can vary before an outage.  Unfortunately, we meet with similar problems when trying to deal with a continuously shifting outage scope.
  *   Bottom-up dose estimates vary significantly between 6-months and 2-months before an outage.  Due to this disparity, we will typically seek ARC approval for outage dose approximately 2-months before the outage scheduled start.  The majority of the outage work orders are available at this time and don’t vary too greatly before the outage commences.
  *   For our most recent outage start of 9/22/19, we sought approval for our outage dose in the beginning of August 2019.

Does your outage group ever ask for anything different than published milestones?

  *   Yes.  We will get asked for projections outside of the T-process, but nothing is official until the ARC-approved outage goal 2-months before outage start.

Wrench-Hour Process:

  *   DCPP tracks RCA statistics with the following priority in mind:  Historical data and then calculated data both through work order analysis
  *   Outage estimated hours are provided by planning for each recurring or new work order assigned an outage schedule code.
  *   RP ALARA data mines the recurrence of the planned work orders to determine the actual time someone spent logged in to that order from prior outages.
  *   The actual time (hours) is used to calculate the estimate and is compared against the “wrench-time” provided by the planner.  We seek feed-back from the planners if the actual time is significantly different than the wrench-hours provide by the planner.

I hope this helps.  I am also new to the position and we’ve had to adjust our processes to compensate for a loss of half of our people due to normally attrition (retirement).  Let us know if there’s anything else you guys need that we can provide.

Felix Martinez
Radiation Protection Engineer
Pacific Gas & Electric Company
Diablo Canyon Power Plant
Bldg 104/2/216
PH: 805-545-3116 | PGR: 3116 | fnmf at pge.com<mailto:fnmf at pge.com>

From: Global <global-bounces at list.rpalara.org> On Behalf Of Tutterow, Jennifer
Sent: Wednesday, November 13, 2019 4:30 AM
To: global at list.rpalara.org
Subject: [Global] Benchmark from a new ALARA engineer

*****CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.*****
Good morning everyone,

I am the newest ALARA Engineer at Salem station and I am lucky enough to take over our outage estimating.  As I’m working through getting things together for my first outage, a few different things have come up and I just wanted to get some industry inputs.  Some of the questions are more ALARA related and some in the Outage Group/ALARA interface.

  *   What are you typical milestones tracked by the outage group and how far out are they?  We have “Develop initial outage exposure forecast” at T-5, “Develop Rev. 0 Outage Exposure Forecast” at T-2, and “ALARA Plans Approved” at T-3 (really 14 wks).
  *   Does your outage group ever ask for anything different than published milestones?  For example our outage group asked for the initial forecast number at T-6.5 to be included in the T-6 meeting presentation slides.  This was a month and a half before my milestone, so they did not like the number, but they also didn’t have a stable scope yet.
  *   What is your process (proceduralized or not) for getting ‘wrench hours’ or better field times from the work groups?  This is something that I am still trying to find my own rhythm with, in working with our work groups to take schedule exports and widdle down scheduled durations to actual field times.

Thank you for any information you are able to share.  This has been a challenging, but fun and interesting transition for me (a former engineer) and I am just trying to better my efficiency as well as align some things with our outage group that don’t make sense.

Have a great day,
Jen Tutterow
Radiological Engineer – Salem ALARA
• PSEG Nuclear LLC
Jennifer.Tutterow at pseg.com<mailto:Jennifer.Tutterow at pseg.com>
856-339-1575

[https://www.pseg.com/images/global/email/PSEG_emailsignature_PSEGw-tag_version2.png]<http://www.pseg.com>
[http://facebook.com/pseg]<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Fpseg&data=02%7C01%7Cfnmf%40pge.com%7C23b14a04bcb743bb034108d76835581b%7C44ae661aece641aabc967c2c85a08941%7C0%7C0%7C637092450629203905&sdata=9uNP0Bw1mno6Lp5KPcpd0Aovq9qfKZaBxaOCozR6QEY%3D&reserved=0>
[Twitter]<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FPSEGnews&data=02%7C01%7Cfnmf%40pge.com%7C23b14a04bcb743bb034108d76835581b%7C44ae661aece641aabc967c2c85a08941%7C0%7C0%7C637092450629213902&sdata=mqcyBgP7zoYc3YR%2BxG1JyfxTbCmt28%2FhIxbpvUbBJ%2Bw%3D&reserved=0>
[LinkedIn]<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fpseg&data=02%7C01%7Cfnmf%40pge.com%7C23b14a04bcb743bb034108d76835581b%7C44ae661aece641aabc967c2c85a08941%7C0%7C1%7C637092450629213902&sdata=LJT0dY0YkpivYDZooyZe%2F%2BsbAgypMdTQYtf57heQms0%3D&reserved=0>
[https://www.pseg.com/images/global/WP_LOGOgrey.png]<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fenergizepseg.com%2F&data=02%7C01%7Cfnmf%40pge.com%7C23b14a04bcb743bb034108d76835581b%7C44ae661aece641aabc967c2c85a08941%7C0%7C1%7C637092450629223896&sdata=Q6%2BB8SNpnhmfM6KnPfC7I60g8nKaaCfBzs5pB%2FlzPjY%3D&reserved=0>

PSEGSC
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/20191113/1c53795a/attachment-0002.html>