ML030300383

From kanterella
Jump to navigation Jump to search
Response to Order for Compensatory Measures Related to Access Authorization
ML030300383
Person / Time
Site: Perry FirstEnergy icon.png
Issue date: 01/24/2003
From: Kanda W, Rausch T
FirstEnergy Nuclear Operating Co
To:
Document Control Desk, Office of Nuclear Reactor Regulation
References
PY-CEI/NRR-2686L
Download: ML030300383 (3)


Text

FENOC Perry Nuclear Power Plant 10 Center Road FirstEnergy Nuclear Operating Company Perry Ohio 44081 440-280-5579 WIlharn R. Kanda Fax 440-280-8029 Vice President - Nuclear January 24, 2003 PY-CEI/NRR-2686L U. S. Nuclear Regulatory Commission Attention: Document Control Desk Washington, DC 20555

Subject:

Perry Nuclear Power Plant, Unit No. 1 Docket No. 50-440, License No. NPF-58 Order for Compensatory Measures Related to Access Authorization Ladies and Gentlemen:

The FirstEnergy Nuclear Operating Company (FENOC) has reviewed the Order for Compensatory Measures Related to Access Authorization for the Perry Nuclear Power Plant (PNPP), issued on January 7, 2003. This Order, which modifies the current operating license for PNPP, requires a response regarding the implementation of the compensatory measures set forth in Attachment 2 to the Order.

The Perry Nuclear Power Plant intends to comply with the compensatory measures described in Attachment 2 to the Order. The compensatory measures will be implemented no later than July 7, 2003, except for compensatory measure B. 1.1, which will be implemented no later than April 7, 2003, and compensatory measures C.1.6 and C.1.8, which will be completed no later than January 7, 2004. The attachment to this letter identifies the specific implementation date for each individual compensatory measure.

-- Pursuant to compensatory-measure BA.3(c), FENOC will confirm eligibility for employment, within the time frames allowed and while observing the restrictions of the responsible agency, for new employees of FENOC who are expected to seek unescorted access. With the specific reference to the requirements of compensatory measure B.1.3(c), sentence number 2, FENOC will comply to the fullest extent possible, recognizing that complete compliance will only be possible when a mechanism for doing so has been created. Contractors/Vendors will be directed to comply with employment checks required by INS.

If there are any questions concerning this matter, please contact Mr. Thomas E. Mahon, Manager - Site Protection Section, at 440-280-5314.

0)

Perry Nuclear Power Plant Order for Compensatory Measures Related to Access Authonzation PY-CEI/NRR-2686L Page 2 of 2 I declare under penalty of perjury that the foregoing is true and correct. Executed on January 24, 2003.

imothy S. Rausch for William R. Kanda, Jr.

Attachment cc: Mr. Samuel J. Collins, Director, NRR Mr. Stephen P. Sands, Senior Project Manager Mr. Raymond J. Powell, Senior Resident Inspector Mr. James E. Dyer, Administrator - NRC Region III Mr. Glenn Tracy, Chief, Reactor Safeguards, USNRC (1 copy, Mail Stop O-6H16)]

Attachment Perry Nuclear Power Plant Order for Compensatory Measures Related to Access Authorization PY-CEI/NRR-2686L Page 1 of 1 The following is the schedule for implementation of the compensatory measures set forth in Attachment 2 to the Order for Compensatory Measures Related to Access Authorization for the Perry Nuclear Power Plant, section B.

Compensatory Implementation Date Measure B.1.1 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than April 7, 2003.

B. 1.2 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

B.1.3 Except for item B.1.3(c), implementation is intended to be complete by March 14, 2003,

-with-full compliance achieved no-later.than-July-i7,-2003.-Foroitem B.1.3(c),-

-ý implementation is intended to be complete by May 1, 2003, with compliance achieved no later than July 7, 2003, as discussed in the cover letter.

B.1.4 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

B.1.5 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

B. 1.6 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

B.1.7 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

C. 1.1 Implementation is intended to be complete by June 27, 2003, but full compliance will be achieved no later than July 7, 2003.

C. 1.2 Implementation is intended to be complete by June 27, 2003, but full compliance will be achieved no later than July 7, 2003.

C. 1.3 Implementation is intended to be complete by June 27, 2003, but full compliance will be achieved no later than July 7, 2003.

C.1.4 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

C.1.5 Implementation is intended to be complete by June 27, 2003, but full compliance will beachidVTd h6iatf*-than July 7,-2003.-.

C. 1.6 Implementation of procedural changes is intended to be complete by June 27, 2003, but full compliance will be achieved no later than January 7, 2004.

C. 1.7 Implementation of procedural changes is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.

C.1.8 Implementation of necessary changes is intended to be complete by June 27, 2003, but full compliance will be achieved no later than January 7, 2004.

C.1.9 Implementation is intended to be complete by June 27, 2003, but full compliance will be achieved no later than July 7, 2003.

C.1.10 Implementation is intended to be complete by March 14, 2003, but full compliance will be achieved no later than July 7, 2003.