Hi Dave/All,

We have Sentinel automatically pull data from PADS prior to in-processing.

We do not require that current year dose be validated on PADS prior to TLD 
issue.

Yes we do allow TLD issue with a signed current year Form-4 with worker 
supplied dose.  The individuals availability for a dose extension beyond 2 
Rem/year would be impacted by this, however.

We do not normally do off hours radworker in-processing without advanced 
warning.  If we did, Sentinel is configured to allow anyone with appropriate 
Sentinel access to pull data from PADS.  The only folks within RP who actually 
have PADS access are associated with the dosimetry process.  With the advent of 
GPADS that may change since the concurrent users issue goes away.

Thanks,

Linda


Linda M. Sewell, CHP
Principal Health Physicist
Pacific Gas & Electric Company
Diablo Canyon Power Plant
MS 119/1/117
PO Box 56
Avila Beach, CA 93424
                                                                                
                                                                
P: 805.545.4315 | F: 805.545.2618| [email protected]<mailto:[email protected]>




From: [email protected] [mailto:[email protected]] On Behalf Of 
Dave Raye
Sent: Tuesday, December 23, 2014 3:19 PM
To: [email protected]
Subject: Powernet: TLD issue and PADs use.

Hello all,
Currently, at Cook we have incoming radworkers document and attest to their 
current year dose. We then validate this attestation with PADs immediately, 
before issuing the TLD (following WBC).

Does your site require that current year dose be validated on PADs prior to TLD 
issue?

Does your site allow issue of a TLD without validating current year dose beyond 
attestation w/ signature?.

If your RP Techs issue TLDs after hours, are the PADs qualified?

Please feel free to add any additional info as you see fit.
Thank you all,

Dave Raye
RP Operations Gen Supv
Cook Nuclear Plant
269-466-2803 (O)
269-405-6040 (C)
2803 pager



PG&E is committed to protecting our customers' privacy. 
To learn more, please visit http://www.pge.com/about/company/privacy/customer/

Reply via email to