NRC Generic Letter 1998-03: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
||
| Line 14: | Line 14: | ||
| page count = 11 | | page count = 11 | ||
}} | }} | ||
{{#Wiki_filter:;,,, kc i-X | {{#Wiki_filter:;,,, kc i-X tUNITED STATESNUCLEAR REGULATORY COMMISSIONOFFICE OF NUCLEAR MATERIAL SAFETY AND SAFEGUARDSWASHINGTON, D.C. 20555-0001June 22, 1998NRC GENERIC LE I I R 98-03: NMSS LICENSEES' AND CER1iFICATE HOLDERS' YEAR2000 READINESS PROGRAMS | ||
==Addressees== | ==Addressees== | ||
| Line 21: | Line 21: | ||
==Description of Circumstances== | ==Description of Circumstances== | ||
:As discussed In this Generic Letter, "Y2K Ready' is defined as a computer system orapplication that has been determined to be suitable for continued use Into the year 2000, eventhough the computer system or application Is not Y2K Compliant. A Y2K Readiness Program Isa plan for a facility to become Y2K Ready. 'Y2K Compliant" is defined as a computer system orapplication that accurately processes date/time data (including, but not limited to. calculating,comparing, and sequencing) from, Into, and between the years 1999 and 2000, and beyond,Including leap-year calculations.The Y2K problem pertains to the potential Inability of computers to correctly recognize datesbeyond December 31,1999. This problem results from computer hardware and/or software thatuses two-digit fields to represent the year. These systems may misread the year 2000 andcause the systems to fail, generate faulty data, or act in an incorrect manner. The Y2K problemhas the potential to interfere with the proper operation of any computer system, hardware that Ismicroprocessor-based (embedded software), software, or database. As a consequence, thereIs a risk that affected plant systems and equipment may fail to function property.'0 on 95n , Q..OA R)CR 0000003 &J f9Ot Z Z.---)A t | :As discussed In this Generic Letter, "Y2K Ready' is defined as a computer system orapplication that has been determined to be suitable for continued use Into the year 2000, eventhough the computer system or application Is not Y2K Compliant. A Y2K Readiness Program Isa plan for a facility to become Y2K Ready. 'Y2K Compliant" is defined as a computer system orapplication that accurately processes date/time data (including, but not limited to. calculating,comparing, and sequencing) from, Into, and between the years 1999 and 2000, and beyond,Including leap-year calculations.The Y2K problem pertains to the potential Inability of computers to correctly recognize datesbeyond December 31,1999. This problem results from computer hardware and/or software thatuses two-digit fields to represent the year. These systems may misread the year 2000 andcause the systems to fail, generate faulty data, or act in an incorrect manner. The Y2K problemhas the potential to interfere with the proper operation of any computer system, hardware that Ismicroprocessor-based (embedded software), software, or database. As a consequence, thereIs a risk that affected plant systems and equipment may fail to function property.'0 on 95n , Q..OA R)CR 0000003 &J f9Ot Z Z.---)A t | ||
-. -GL 903June 22, 1998Pago 2 of 6The Y2K problem Is urgent because it has a fixed, non-negotiable deadline that Is quicklyapproaching. This matter requires priority attention because of the limited time remaining toassess the magnitude of the problem, assess IKs associated risks, and implement programs thatwn achieve a satisfactory resolution of the Y2K problem.Existing reporting requirements under 10 CFR Part 21 provide for notification to NRC ofdeficiencies, non-conformances, and failures, such as the Y2K problem In safety-relatedsystems. Examples of systems that may be affected include:* Safeguards (Material Control and Accounting, and Physical Protection) systems* Computer security systems* Plant process (data scan, log, and alarm) display system computers* Safety parameter display system computers* Emergency response systems* Radiation monitoring systems* Dosimeters and readers* Engineoring programs and systems* Communication systems* Inventory control systems* Surveillance and maintenance tracking systems* Plant process control systemsa Document control systemsTo alert licensees and certificate holders to the Y2K problem, NRC Issued Information Notice(IN) 970, "Year 2000 Effect on Computer System Software," on December 24, 1996. InIN 96-70, the staff described the potential problems that computer systems and software mayencounter as a result of the change from the year 1999 to the year 2000 and how the Y2KIssue may affect NRC licensees and certificate holders. IN 96-70 encouraged licensees andcertificate holders to examine their uses of computer systems and software well before the year2000 and suggested that they consider appropriate actions to examine and evaluate theircomputer systems for Y2K vulnerabilities.As part of NRC's response to the Y2K problem, NRC assembled a Y2K team to gather moreInformation on the Y2K Readiness Programs of materials ard fuel cycle licensees andcertificate holders. In addition, materials and fuel cycle Inspectors have been Instructed toconfirm receipt of NRC's IN 96-70, by materials and fuel cycle licensees and certificate holders;determine whether the licensees and certificate holders have Identified any potential problemsassociated Ath the Y2K Issue; and note any corrective actions taken by the licensees andcertficate holders.; .Discuss on:;There are several concerns.associated with the potential Impact of the Y2K problem because ofthe variety and types of computer systems and software In use. For example, th role and useof cotmpurs and embedded systems In: (1) scheduing of maintenance and surveillancere .u merits; (2) programmable logic controllers and other commercial off-the-shelf software1....of r , , ' ''' ,, .. | -. -GL 903June 22, 1998Pago 2 of 6The Y2K problem Is urgent because it has a fixed, non-negotiable deadline that Is quicklyapproaching. This matter requires priority attention because of the limited time remaining toassess the magnitude of the problem, assess IKs associated risks, and implement programs thatwn achieve a satisfactory resolution of the Y2K problem.Existing reporting requirements under 10 CFR Part 21 provide for notification to NRC ofdeficiencies, non-conformances, and failures, such as the Y2K problem In safety-relatedsystems. Examples of systems that may be affected include:* Safeguards (Material Control and Accounting, and Physical Protection) systems* Computer security systems* Plant process (data scan, log, and alarm) display system computers* Safety parameter display system computers* Emergency response systems* Radiation monitoring systems* Dosimeters and readers* Engineoring programs and systems* Communication systems* Inventory control systems* Surveillance and maintenance tracking systems* Plant process control systemsa Document control systemsTo alert licensees and certificate holders to the Y2K problem, NRC Issued Information Notice(IN) 970, "Year 2000 Effect on Computer System Software," on December 24, 1996. InIN 96-70, the staff described the potential problems that computer systems and software mayencounter as a result of the change from the year 1999 to the year 2000 and how the Y2KIssue may affect NRC licensees and certificate holders. IN 96-70 encouraged licensees andcertificate holders to examine their uses of computer systems and software well before the year2000 and suggested that they consider appropriate actions to examine and evaluate theircomputer systems for Y2K vulnerabilities.As part of NRC's response to the Y2K problem, NRC assembled a Y2K team to gather moreInformation on the Y2K Readiness Programs of materials ard fuel cycle licensees andcertificate holders. In addition, materials and fuel cycle Inspectors have been Instructed toconfirm receipt of NRC's IN 96-70, by materials and fuel cycle licensees and certificate holders;determine whether the licensees and certificate holders have Identified any potential problemsassociated Ath the Y2K Issue; and note any corrective actions taken by the licensees andcertficate holders.; .Discuss on:;There are several concerns.associated with the potential Impact of the Y2K problem because ofthe variety and types of computer systems and software In use. For example, th role and useof cotmpurs and embedded systems In: (1) scheduing of maintenance and surveillancere .u merits; (2) programmable logic controllers and other commercial off-the-shelf software1....of r , , ' ''' ,, .. | ||
GL 98-03June 22, 1998 and hardware; (3) document control systems; (4) process control systems; (5) engineeringcalculations; and (6) systems for the collection of operating and post-accident site parameterdata.Applications that have no apparent date manipulation algorithms may still be affected by a Y2Kproblem. For example, a subroutine that date-stamps the header Information In archival tapes,regardless of the rest of the content of the tape, may be affected. In additon, Individualsystems may be "date safe," but the Integrated operations that the systems support may bevulnerable to the Y2K problem. Therefore, after testing a subsystem for Y2K Readiness, a.functional test of the entire system should be performed.The following elements can be used to aid in the development of a successful Y2K ReadinessProgram: (1) management planning; (2) Implementation; (3) quality assurance (QA);(4) regulatory considerations; and (5) documentation. The components for planning Includemanagement awareness, sponsorship, project leadership, project objectives, projectmanagement team, management plan, project reports, Interfaces, resources, and oversight.The phases of Implementation Include: awareness; initial assessment (e.g., inventory,categorization, classification, prioritization, and analysis); detailed assessment (e.g., vendorevaluation, software evaluation. Interface evaluation, remedial planning); remediation; testingand validation; and notification. The features of QA Include project management QA as well asimplementation QA. The aspects of regulatory considerations Include the performance anddocumentation of appropriate reviews and/or evaluations. The elements of documentation ofactivities and results Include project management documentation, vendor certifications,Inventory lists, checklists, and record retention.There are three reference documents that may help licensees and certificate holders with theirY2K Readiness Programs. The General Accounting Office published 'Year 2000 ComputingCrisis: An Assessment Guide," In September 1997 and "Year 2000 Computing Crisis: BusinessContinuIty and Contingency Planning. Exposure Draft,' In March 19 98.chttp:/Jwww.gao.gov/specia!.pubsIpublist.htm> as general business tools; and the NuclearEnergy Institute published NEilNUSMG 97-07, aNuclear Utility Year 2000 Readiness,' InOctober 1997 chttp:/hlww.nrc.gov/NRCIY2K/NRCNEIVNE19707.html> to assist nuclear powerplants In the development of their Y2K Readiness Programs. Even though the latter is gearedtowards commercial nuclear power plants, the general discussion of the elements in Y2KReadiness Program could be beneficial to other business entities.NRC Is also preparing its Nuclear Material Management Safeguards System (NMMSS) to beY2K Compliant For NRC licensees and certificate holders required to report nuclear materialtransactions to NMMSS, from May 1, 1998, through mid-1999, NMMSS will operate in amanner that allows all nuclear material transaction reports to NMMSS to be either In the currenttwo-digit year reporting format or In the Y2K Compliant four-digit year format. After mid-1999,only the Y2K Compliant format will be acceptable.Ucensees and certificate holders that use their own software to Input data Into NMMSS willhave to modify it themselves, to be Y2K compliant.1' | GL 98-03June 22, 1998 and hardware; (3) document control systems; (4) process control systems; (5) engineeringcalculations; and (6) systems for the collection of operating and post-accident site parameterdata.Applications that have no apparent date manipulation algorithms may still be affected by a Y2Kproblem. For example, a subroutine that date-stamps the header Information In archival tapes,regardless of the rest of the content of the tape, may be affected. In additon, Individualsystems may be "date safe," but the Integrated operations that the systems support may bevulnerable to the Y2K problem. Therefore, after testing a subsystem for Y2K Readiness, a.functional test of the entire system should be performed.The following elements can be used to aid in the development of a successful Y2K ReadinessProgram: (1) management planning; (2) Implementation; (3) quality assurance (QA);(4) regulatory considerations; and (5) documentation. The components for planning Includemanagement awareness, sponsorship, project leadership, project objectives, projectmanagement team, management plan, project reports, Interfaces, resources, and oversight.The phases of Implementation Include: awareness; initial assessment (e.g., inventory,categorization, classification, prioritization, and analysis); detailed assessment (e.g., vendorevaluation, software evaluation. Interface evaluation, remedial planning); remediation; testingand validation; and notification. The features of QA Include project management QA as well asimplementation QA. The aspects of regulatory considerations Include the performance anddocumentation of appropriate reviews and/or evaluations. The elements of documentation ofactivities and results Include project management documentation, vendor certifications,Inventory lists, checklists, and record retention.There are three reference documents that may help licensees and certificate holders with theirY2K Readiness Programs. The General Accounting Office published 'Year 2000 ComputingCrisis: An Assessment Guide," In September 1997 and "Year 2000 Computing Crisis: BusinessContinuIty and Contingency Planning. Exposure Draft,' In March 19 98.chttp:/Jwww.gao.gov/specia!.pubsIpublist.htm> as general business tools; and the NuclearEnergy Institute published NEilNUSMG 97-07, aNuclear Utility Year 2000 Readiness,' InOctober 1997 chttp:/hlww.nrc.gov/NRCIY2K/NRCNEIVNE19707.html> to assist nuclear powerplants In the development of their Y2K Readiness Programs. Even though the latter is gearedtowards commercial nuclear power plants, the general discussion of the elements in Y2KReadiness Program could be beneficial to other business entities.NRC Is also preparing its Nuclear Material Management Safeguards System (NMMSS) to beY2K Compliant For NRC licensees and certificate holders required to report nuclear materialtransactions to NMMSS, from May 1, 1998, through mid-1999, NMMSS will operate in amanner that allows all nuclear material transaction reports to NMMSS to be either In the currenttwo-digit year reporting format or In the Y2K Compliant four-digit year format. After mid-1999,only the Y2K Compliant format will be acceptable.Ucensees and certificate holders that use their own software to Input data Into NMMSS willhave to modify it themselves, to be Y2K compliant.1' | ||
GL 9803June 22, 1998 Raquestftd Action:Action addressees are requested to complete their Y2K Readiness Program by December 31,1998. Action addressoes' facilities are requested to be Y2K Compfiant by December 31, 199.Required Response:To gain the necessary assurance that action addressees are effectively resohring the Y2Kproblem and are In compliance with the terms and conditions of their licenses or certificates,and NRC regulatk. -. NRC requires that all action addressees submit a written response to thisGeneric Letter, as fo. vs:(1) Within 90 days of the date of this Generic Letter, submit a written response Indicatingwhether you have pursued and are continuing to pursue a Y2K Readiness Program.Present a brief description of the program that has already been completed, Is beingconducted, or Is planned, to ensure Y2K Readiness of the computer systems at yourfacility. This response should address the program's scope, assessment process, andplans for corrective actions, Including schedules for testing and validation. If anaddressee chooses not to take the requested action(s), provide a description of anyproposed alternative course of action, the schedule for completing the altemative courseof action (if applicable), and the safety basis for determining the acceptability of theplanned afternative course of action.(2) Upon completing your Y2K Readiness Program, or, in any event, no later thanDecember 31, 1998, submit a written response confirming that your facility Is Y2KReady and In compliance with the terms and conditions of your license or certificate,and NRC regulations; or, If your facility is not Y2K Ready by December 31, 1998, thensubmit a written response that contains a status report of work remaining to be done tobecome Y2K Ready, Including completion schedules. For systems that may affectsafety and safeguards, contingency plans to become Y2K Ready and Y2K Compliantshould be Included In your response.(3) For facilities that are not Y2K Ready on or before December 31, 1998, submit a writtenresponse, by July 1, 1999, updating the status and schedule of your Y2K ReadinessProgram submitted In (2), above. The response should contain a tatus report of workremaining to be done to become Y2K Ready. Including completion schedules. Forsystems that may affect safety and safeguards, contingency pans M-Ume Y2KReady and Y2K Compliant should be Included In your response.If you determine, as your review evolves, that your facility Is not Y2K Ready after submittingInformation in response to this Generic Letter that states that your facility Is Y2K Ready, submita written response containing the Information as requested in (3) above. The written responsesshould Include sufficient detail to assess the licensee's or certificate holde's Y2K Readiness'Program.h. .7* | GL 9803June 22, 1998 Raquestftd Action:Action addressees are requested to complete their Y2K Readiness Program by December 31,1998. Action addressoes' facilities are requested to be Y2K Compfiant by December 31, 199.Required Response:To gain the necessary assurance that action addressees are effectively resohring the Y2Kproblem and are In compliance with the terms and conditions of their licenses or certificates,and NRC regulatk. -. NRC requires that all action addressees submit a written response to thisGeneric Letter, as fo. vs:(1) Within 90 days of the date of this Generic Letter, submit a written response Indicatingwhether you have pursued and are continuing to pursue a Y2K Readiness Program.Present a brief description of the program that has already been completed, Is beingconducted, or Is planned, to ensure Y2K Readiness of the computer systems at yourfacility. This response should address the program's scope, assessment process, andplans for corrective actions, Including schedules for testing and validation. If anaddressee chooses not to take the requested action(s), provide a description of anyproposed alternative course of action, the schedule for completing the altemative courseof action (if applicable), and the safety basis for determining the acceptability of theplanned afternative course of action.(2) Upon completing your Y2K Readiness Program, or, in any event, no later thanDecember 31, 1998, submit a written response confirming that your facility Is Y2KReady and In compliance with the terms and conditions of your license or certificate,and NRC regulations; or, If your facility is not Y2K Ready by December 31, 1998, thensubmit a written response that contains a status report of work remaining to be done tobecome Y2K Ready, Including completion schedules. For systems that may affectsafety and safeguards, contingency plans to become Y2K Ready and Y2K Compliantshould be Included In your response.(3) For facilities that are not Y2K Ready on or before December 31, 1998, submit a writtenresponse, by July 1, 1999, updating the status and schedule of your Y2K ReadinessProgram submitted In (2), above. The response should contain a tatus report of workremaining to be done to become Y2K Ready. Including completion schedules. Forsystems that may affect safety and safeguards, contingency pans M-Ume Y2KReady and Y2K Compliant should be Included In your response.If you determine, as your review evolves, that your facility Is not Y2K Ready after submittingInformation in response to this Generic Letter that states that your facility Is Y2K Ready, submita written response containing the Information as requested in (3) above. The written responsesshould Include sufficient detail to assess the licensee's or certificate holde's Y2K Readiness'Program.h. .7* | ||
GL 9803June 22, 1998 Address the required written responses to the U.S. Nuclear Regulatory Commission, ATTN:Document Control Desk, Washington, D.C. 20555-0001, under oath or affirmation under theprovisions of Section 182a, Atomic Energy Act 1954. as amended. Include the docket numberfor the facirty on the first page of any response. In addition, submit a copy to the appropriateRegional Administrator.eackfl Discussion:(This section Is applicable only to uranium enrichment plants with certificates of complianceunder 10 CFR Part 78.) This generic letter only requests Information from addressees under theprovisions of Section 1 82a of the Atomic Energy Act of 1954, as amended. The requestedInformation will enable NRC to verify that uranium enrichment plants are Implementing effectiveplans to address the Y2K problem and provide for safe operation of the facilities before andafter January 1, 2000, and are In compliance with the terms and conditions of their certificates,and NRC regulations. NRC regulations in 10 CFR Part 76 provide the basis for this request.Psaerwork Reduction Act Statement:The information collections contained In this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of Information Is estimated to average 250 hours perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of Information, Including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington. D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. | GL 9803June 22, 1998 Address the required written responses to the U.S. Nuclear Regulatory Commission, ATTN:Document Control Desk, Washington, D.C. 20555-0001, under oath or affirmation under theprovisions of Section 182a, Atomic Energy Act 1954. as amended. Include the docket numberfor the facirty on the first page of any response. In addition, submit a copy to the appropriateRegional Administrator.eackfl Discussion:(This section Is applicable only to uranium enrichment plants with certificates of complianceunder 10 CFR Part 78.) This generic letter only requests Information from addressees under theprovisions of Section 1 82a of the Atomic Energy Act of 1954, as amended. The requestedInformation will enable NRC to verify that uranium enrichment plants are Implementing effectiveplans to address the Y2K problem and provide for safe operation of the facilities before andafter January 1, 2000, and are In compliance with the terms and conditions of their certificates,and NRC regulations. NRC regulations in 10 CFR Part 76 provide the basis for this request.Psaerwork Reduction Act Statement:The information collections contained In this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of Information Is estimated to average 250 hours perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of Information, Including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington. D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503. | ||
* rGL 98-03June 22, 1998 If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.DMdeon of Fuel Cycle Safetyand SafeguardsOffice of Nuclear Material Safetyand SafeguardContacts: Gary Purdy, NMSSIIMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSSIFCSS(301) 415-5521E-mail: hdfenrc.govAttachments: Ust of Recently Issued NRC Generic Letters I , -AttachmentGL 9803June 22, 1998Page 1 of IUST OF RECENTLY ISSUED GENERIC LETTERSGENELETTE98-02RICSUBJECTLoss of Reactor CoolantInventory and AssociatedPotential for Loss of EmergencyMitgation Functions White in aShutdown ConditionDATE OFISSUANCE05/28/BISSUED TOAll holders of OLS for PWRs,except those who havepermanently ceasedoperations, and havecertified that fuel has beenpermanently removed fromthe reactor vessel.98-0197-0697-05Year 2000 Readiness ofof Computer Systems atNuclear Power PlantsDegradation of SteamGenerator IntemalsSteam Generator TubeInspection Techniques05/1219812/30/9712/17/97All holders of OLS fornuclear power plants,except those who havepermanently ceasedoperations and havecertified that fuel has beenpermanently removed fromthe reactor vesselAll holders of OLS forpressurized-water reactors,except those who havepermanently ceasedoperations and have certifiedthat fuel has been perman-ently removed from thereactor vesselAll holders of OLs forpressurized-water reactors,except those who havepermanently ceasedoperations and have certifiedthat fuel has been perman-ently removed from thereactor vesselOP O Operating LcenseA'CP u Constuction PermitI NPR NucIear Power Reactors.,, ...f | |||
.-. I. .......If you have any questions about this matter. please contact one of the technical contacts listedbelow or the appropriate regional office.sS- ' ' hiElizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andS SafeguardsOffice of Nuclear Material Safetyand afeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Feisher, NMSSIFCSS(301) 41-5521E-mail: .hffnrc.govAttachments:1. Ust of Recently issued NRC Generic LettersDOCUMENT NAME: o:%NmssqL5.OwP See Previous Co ocurrenoeIOFC [ I FCSS I C NMSSEdor lII OB lFOVr .IgO IIr .FCombsMWebera-.. .... ..NAMEa aGPurdy/AIlAl )rOaHrelsher7A? Il 1 Onciern toS~MorelI *1-1 S%..-.44/ 981 ~I Wa9 5/7 93 1p8g S-fax-198St -7 /98O FCSS l FCSS l OGC lF,NAME P*Ting RPlerson STreby- EnEyck/DATE 6/14 198 4/9 t98 5/22.1 8 6/I /98 tftP8OFFICIAL RECOCRD COPYA .... | |||
.-. I. .......If you have any questions about this matter. please contact one of the technical contacts listedbelow or the appropriate regional office.sS- ' ' hiElizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andS SafeguardsOffice of Nuclear Material Safetyand afeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Feisher, NMSSIFCSS(301) 41-5521E-mail: .hffnrc. | Emgwr Reu12 Ac SIs ment;The Informnation collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of information Is estimated to average 250 hours perresponse, Including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSIIMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSSIFCSS(301) 415-5521E-mail: hdf@nrc.govAttachments:1. List ot Recently Issued NRC Generic LettersDOCUMENT NAME: G:WmSSOL5.CVPOFC FCSS NMSS/Editor FCSSlNAME GPurdyiU HFelsher Elsrsus oore MWeberDATE 417/98 4/ /98 3/1698-fax- _ 41 '8 I /98 5t /98OFC FCSS IL OCI FCSS IMNSNAME Kling RPierson STreby ETenEyck DCoolDATE 6/ 198 41/ 98 5 /98 5/ 198 5/ 98OFFICIAL RECORD COPY/s ..... .. | ||
' -;3Paoerworks Reduction Act StatementThe information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9. 2000. The publicreporting burden for this collection of information is estimated to average 250 hours perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed. an" completing and reviewing the collection ofinformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Reguldtory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSS/FCSS(301) 415-5521E-mail: hdf~nrc.govAttachments:1. List of Recently Issued NRC Generic LettersDOCUMENT NAME: G:owssouL.awPOFC l ll dftor ls FlS 0 ll OB liFCSSNAME GPurdyAIl HFelsher EKraus SMoore FCombs MWeberDATE l 198 41 /98 3/16/98-fax- 4/ /98 /98 i51/ /98OFC FCSS FCSS QGC FCSS IMNSNAME King RPierson MISTreby ETenEyck DCoolDATE l /198 4 /98 _s __ 5t 98 /5 /98mm~st _~oR __Yg wh* | |||
* VNIWAL KEWKW GQFY.*~~~~~~"0fr-'a0 | |||
1. Ust of Recently issued NRC Generic LettersDOCUMENT NAME: o:%NmssqL5.OwP See Previous Co ocurrenoeIOFC [ I FCSS I C NMSSEdor lII OB lFOVr .IgO IIr .FCombsMWebera-.. .... ..NAMEa aGPurdy/AIlAl )rOaHrelsher7A? Il 1 Onciern toS~MorelI *1-1 S%..-.44/ 981 ~I Wa9 5/7 93 1p8g S-fax-198St -7 /98O FCSS l FCSS l OGC lF,NAME P*Ting RPlerson STreby- EnEyck/DATE 6/14 198 4/9 t98 5/22.1 8 6/I /98 tftP8OFFICIAL RECOCRD COPYA .... | pagerwork Reduction Act Statement:The information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9, 2000. The publicreporting burden for this collection of information is estimated to average 5 hours per response.including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Sendcomments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to the information and Records ManagementBranch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555, and to the DeskOfficer. Office of Information and Regulatory Affairs, NEOB-1 0202, (3150-0011), Office ofManagement and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth 0. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSS/IMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher. NMSSIFCSS(301) 415-5521E-mail: hdfenrc.govAttachments:1. The cco ocum ent.'Ye sessment Guide,' September 1997.2. '__ _G7-7,*trUdiajy Yx41 2000 Reddi,,es. Ozctober 1997.3. List of Recently Issued NRC Generic LettersDOCUMENT NAME: ow-ssotsowp_EOFC _8 NMSSEdor 08J l jj FCSS LNAME GPurdyfil EKraus SMoore FCombs fMWeber PTmgDATE 4/ /98 3/16A98-fax- 4/ /98 5/ /98 6/ /98OFC FCSS l OGC l FCSS lIMNS_NAME RPierson STreby ETenEyck DCoolDATE 4/ /98 5// 98 51/ 98 5/ /98__._ ---------* I.OFFICIAL KEORD COPY | ||
Emgwr Reu12 Ac SIs ment;The Informnation collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of information Is estimated to average 250 hours perresponse, Including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSIIMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSSIFCSS(301) 415-5521E-mail: hdf@nrc. | }} | ||
1. List ot Recently Issued NRC Generic LettersDOCUMENT NAME: G:WmSSOL5.CVPOFC FCSS NMSS/Editor FCSSlNAME GPurdyiU HFelsher Elsrsus oore MWeberDATE 417/98 4/ /98 3/1698-fax- _ 41 '8 I /98 5t /98OFC FCSS IL OCI FCSS IMNSNAME Kling RPierson STreby ETenEyck DCoolDATE 6/ 198 41/ 98 5 /98 5/ 198 5/ 98OFFICIAL RECORD COPY/s ..... .. | |||
' -;3Paoerworks Reduction Act StatementThe information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9. 2000. The publicreporting burden for this collection of information is estimated to average 250 hours perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed. an" completing and reviewing the collection ofinformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Reguldtory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSS/FCSS(301) 415-5521E-mail: hdf~nrc. | |||
1. List of Recently Issued NRC Generic LettersDOCUMENT NAME: G:owssouL.awPOFC l ll dftor ls FlS 0 ll OB liFCSSNAME GPurdyAIl HFelsher EKraus SMoore FCombs MWeberDATE l 198 41 /98 3/16/98-fax- 4/ /98 /98 i51/ /98OFC FCSS FCSS QGC FCSS IMNSNAME King RPierson MISTreby ETenEyck DCoolDATE l /198 4 /98 _s __ 5t 98 /5 /98mm~st _~oR __Yg wh* | |||
* VNIWAL KEWKW GQFY.*~~~~~~"0fr-'a0 pagerwork Reduction Act Statement:The information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9, 2000. The publicreporting burden for this collection of information is estimated to average 5 hours per response.including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Sendcomments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to the information and Records ManagementBranch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555, and to the DeskOfficer. Office of Information and Regulatory Affairs, NEOB-1 0202, (3150-0011), Office ofManagement and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth 0. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSS/IMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher. NMSSIFCSS(301) 415-5521E-mail: hdfenrc. | |||
1. The cco ocum ent.'Ye sessment Guide,' September 1997.2. '__ _G7-7,*trUdiajy Yx41 2000 Reddi,,es. Ozctober 1997.3. List of Recently Issued NRC Generic LettersDOCUMENT NAME: ow-ssotsowp_EOFC _8 NMSSEdor 08J l jj FCSS LNAME GPurdyfil EKraus SMoore FCombs fMWeber PTmgDATE 4/ /98 3/16A98-fax- 4/ /98 5/ /98 6/ /98OFC FCSS l OGC l FCSS lIMNS_NAME RPierson STreby ETenEyck DCoolDATE 4/ /98 5// 98 51/ 98 5/ /98__._ ---------* I.OFFICIAL KEORD COPY}} | |||
{{GL-Nav}} | {{GL-Nav}} | ||
Revision as of 18:15, 6 April 2018
| ML031110077 | |
| Person / Time | |
|---|---|
| Site: | Indian Point |
| Issue date: | 06/22/1998 |
| From: | TenEyck E Q NRC/NMSS/FCSS |
| To: | |
| References | |
| GL-98-003, NUDOCS 9806180139 | |
| Download: ML031110077 (11) | |
- ,,, kc i-X tUNITED STATESNUCLEAR REGULATORY COMMISSIONOFFICE OF NUCLEAR MATERIAL SAFETY AND SAFEGUARDSWASHINGTON, D.C. 20555-0001June 22, 1998NRC GENERIC LE I I R 98-03
- NMSS LICENSEES' AND CER1iFICATE HOLDERS' YEAR2000 READINESS PROGRAMS
Addressees
- For Action: All licensees or certificate holders for uranium hexafluorideproduction plants, uranium enrichment plants, and uranium fuelfabrication plants, except those that have permanently ceasedoperations.For Information: NonePurose:The U.S. Nuclear Regulatory Commission (NRC) is issuing this generic letter to: (1) notify alladdressees of the need for Year 2000 (Y2K) Readiness Programs to address the Y2K problemin computer systems at their facilities; (2) request all action addressees to implement theactions described herein; and (3) require all action addressees to provide NRC with a writtenresponse to this letter.
Description of Circumstances
- As discussed In this Generic Letter, "Y2K Ready' is defined as a computer system orapplication that has been determined to be suitable for continued use Into the year 2000, eventhough the computer system or application Is not Y2K Compliant. A Y2K Readiness Program Isa plan for a facility to become Y2K Ready. 'Y2K Compliant" is defined as a computer system orapplication that accurately processes date/time data (including, but not limited to. calculating,comparing, and sequencing) from, Into, and between the years 1999 and 2000, and beyond,Including leap-year calculations.The Y2K problem pertains to the potential Inability of computers to correctly recognize datesbeyond December 31,1999. This problem results from computer hardware and/or software thatuses two-digit fields to represent the year. These systems may misread the year 2000 andcause the systems to fail, generate faulty data, or act in an incorrect manner. The Y2K problemhas the potential to interfere with the proper operation of any computer system, hardware that Ismicroprocessor-based (embedded software), software, or database. As a consequence, thereIs a risk that affected plant systems and equipment may fail to function property.'0 on 95n , Q..OA R)CR 0000003 &J f9Ot Z Z.---)A t
-. -GL 903June 22, 1998Pago 2 of 6The Y2K problem Is urgent because it has a fixed, non-negotiable deadline that Is quicklyapproaching. This matter requires priority attention because of the limited time remaining toassess the magnitude of the problem, assess IKs associated risks, and implement programs thatwn achieve a satisfactory resolution of the Y2K problem.Existing reporting requirements under 10 CFR Part 21 provide for notification to NRC ofdeficiencies, non-conformances, and failures, such as the Y2K problem In safety-relatedsystems. Examples of systems that may be affected include:* Safeguards (Material Control and Accounting, and Physical Protection) systems* Computer security systems* Plant process (data scan, log, and alarm) display system computers* Safety parameter display system computers* Emergency response systems* Radiation monitoring systems* Dosimeters and readers* Engineoring programs and systems* Communication systems* Inventory control systems* Surveillance and maintenance tracking systems* Plant process control systemsa Document control systemsTo alert licensees and certificate holders to the Y2K problem, NRC Issued Information Notice(IN) 970, "Year 2000 Effect on Computer System Software," on December 24, 1996. InIN 96-70, the staff described the potential problems that computer systems and software mayencounter as a result of the change from the year 1999 to the year 2000 and how the Y2KIssue may affect NRC licensees and certificate holders. IN 96-70 encouraged licensees andcertificate holders to examine their uses of computer systems and software well before the year2000 and suggested that they consider appropriate actions to examine and evaluate theircomputer systems for Y2K vulnerabilities.As part of NRC's response to the Y2K problem, NRC assembled a Y2K team to gather moreInformation on the Y2K Readiness Programs of materials ard fuel cycle licensees andcertificate holders. In addition, materials and fuel cycle Inspectors have been Instructed toconfirm receipt of NRC's IN 96-70, by materials and fuel cycle licensees and certificate holders;determine whether the licensees and certificate holders have Identified any potential problemsassociated Ath the Y2K Issue; and note any corrective actions taken by the licensees andcertficate holders.; .Discuss on:;There are several concerns.associated with the potential Impact of the Y2K problem because ofthe variety and types of computer systems and software In use. For example, th role and useof cotmpurs and embedded systems In: (1) scheduing of maintenance and surveillancere .u merits; (2) programmable logic controllers and other commercial off-the-shelf software1....of r , , ' ,, ..
GL 98-03June 22, 1998 and hardware; (3) document control systems; (4) process control systems; (5) engineeringcalculations; and (6) systems for the collection of operating and post-accident site parameterdata.Applications that have no apparent date manipulation algorithms may still be affected by a Y2Kproblem. For example, a subroutine that date-stamps the header Information In archival tapes,regardless of the rest of the content of the tape, may be affected. In additon, Individualsystems may be "date safe," but the Integrated operations that the systems support may bevulnerable to the Y2K problem. Therefore, after testing a subsystem for Y2K Readiness, a.functional test of the entire system should be performed.The following elements can be used to aid in the development of a successful Y2K ReadinessProgram: (1) management planning; (2) Implementation; (3) quality assurance (QA);(4) regulatory considerations; and (5) documentation. The components for planning Includemanagement awareness, sponsorship, project leadership, project objectives, projectmanagement team, management plan, project reports, Interfaces, resources, and oversight.The phases of Implementation Include: awareness; initial assessment (e.g., inventory,categorization, classification, prioritization, and analysis); detailed assessment (e.g., vendorevaluation, software evaluation. Interface evaluation, remedial planning); remediation; testingand validation; and notification. The features of QA Include project management QA as well asimplementation QA. The aspects of regulatory considerations Include the performance anddocumentation of appropriate reviews and/or evaluations. The elements of documentation ofactivities and results Include project management documentation, vendor certifications,Inventory lists, checklists, and record retention.There are three reference documents that may help licensees and certificate holders with theirY2K Readiness Programs. The General Accounting Office published 'Year 2000 ComputingCrisis: An Assessment Guide," In September 1997 and "Year 2000 Computing Crisis: BusinessContinuIty and Contingency Planning. Exposure Draft,' In March 19 98.chttp:/Jwww.gao.gov/specia!.pubsIpublist.htm> as general business tools; and the NuclearEnergy Institute published NEilNUSMG 97-07, aNuclear Utility Year 2000 Readiness,' InOctober 1997 chttp:/hlww.nrc.gov/NRCIY2K/NRCNEIVNE19707.html> to assist nuclear powerplants In the development of their Y2K Readiness Programs. Even though the latter is gearedtowards commercial nuclear power plants, the general discussion of the elements in Y2KReadiness Program could be beneficial to other business entities.NRC Is also preparing its Nuclear Material Management Safeguards System (NMMSS) to beY2K Compliant For NRC licensees and certificate holders required to report nuclear materialtransactions to NMMSS, from May 1, 1998, through mid-1999, NMMSS will operate in amanner that allows all nuclear material transaction reports to NMMSS to be either In the currenttwo-digit year reporting format or In the Y2K Compliant four-digit year format. After mid-1999,only the Y2K Compliant format will be acceptable.Ucensees and certificate holders that use their own software to Input data Into NMMSS willhave to modify it themselves, to be Y2K compliant.1'
GL 9803June 22, 1998 Raquestftd Action:Action addressees are requested to complete their Y2K Readiness Program by December 31,1998. Action addressoes' facilities are requested to be Y2K Compfiant by December 31, 199.Required Response:To gain the necessary assurance that action addressees are effectively resohring the Y2Kproblem and are In compliance with the terms and conditions of their licenses or certificates,and NRC regulatk. -. NRC requires that all action addressees submit a written response to thisGeneric Letter, as fo. vs:(1) Within 90 days of the date of this Generic Letter, submit a written response Indicatingwhether you have pursued and are continuing to pursue a Y2K Readiness Program.Present a brief description of the program that has already been completed, Is beingconducted, or Is planned, to ensure Y2K Readiness of the computer systems at yourfacility. This response should address the program's scope, assessment process, andplans for corrective actions, Including schedules for testing and validation. If anaddressee chooses not to take the requested action(s), provide a description of anyproposed alternative course of action, the schedule for completing the altemative courseof action (if applicable), and the safety basis for determining the acceptability of theplanned afternative course of action.(2) Upon completing your Y2K Readiness Program, or, in any event, no later thanDecember 31, 1998, submit a written response confirming that your facility Is Y2KReady and In compliance with the terms and conditions of your license or certificate,and NRC regulations; or, If your facility is not Y2K Ready by December 31, 1998, thensubmit a written response that contains a status report of work remaining to be done tobecome Y2K Ready, Including completion schedules. For systems that may affectsafety and safeguards, contingency plans to become Y2K Ready and Y2K Compliantshould be Included In your response.(3) For facilities that are not Y2K Ready on or before December 31, 1998, submit a writtenresponse, by July 1, 1999, updating the status and schedule of your Y2K ReadinessProgram submitted In (2), above. The response should contain a tatus report of workremaining to be done to become Y2K Ready. Including completion schedules. Forsystems that may affect safety and safeguards, contingency pans M-Ume Y2KReady and Y2K Compliant should be Included In your response.If you determine, as your review evolves, that your facility Is not Y2K Ready after submittingInformation in response to this Generic Letter that states that your facility Is Y2K Ready, submita written response containing the Information as requested in (3) above. The written responsesshould Include sufficient detail to assess the licensee's or certificate holde's Y2K Readiness'Program.h. .7*
GL 9803June 22, 1998 Address the required written responses to the U.S. Nuclear Regulatory Commission, ATTN:Document Control Desk, Washington, D.C. 20555-0001, under oath or affirmation under theprovisions of Section 182a, Atomic Energy Act 1954. as amended. Include the docket numberfor the facirty on the first page of any response. In addition, submit a copy to the appropriateRegional Administrator.eackfl Discussion:(This section Is applicable only to uranium enrichment plants with certificates of complianceunder 10 CFR Part 78.) This generic letter only requests Information from addressees under theprovisions of Section 1 82a of the Atomic Energy Act of 1954, as amended. The requestedInformation will enable NRC to verify that uranium enrichment plants are Implementing effectiveplans to address the Y2K problem and provide for safe operation of the facilities before andafter January 1, 2000, and are In compliance with the terms and conditions of their certificates,and NRC regulations. NRC regulations in 10 CFR Part 76 provide the basis for this request.Psaerwork Reduction Act Statement:The information collections contained In this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of Information Is estimated to average 250 hours0.00289 days <br />0.0694 hours <br />4.133598e-4 weeks <br />9.5125e-5 months <br /> perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of Information, Including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington. D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.
- rGL 98-03June 22, 1998 If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.DMdeon of Fuel Cycle Safetyand SafeguardsOffice of Nuclear Material Safetyand SafeguardContacts: Gary Purdy, NMSSIIMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSSIFCSS(301) 415-5521E-mail: hdfenrc.govAttachments: Ust of Recently Issued NRC Generic Letters I , -AttachmentGL 9803June 22, 1998Page 1 of IUST OF RECENTLY ISSUED GENERIC LETTERSGENELETTE98-02RICSUBJECTLoss of Reactor CoolantInventory and AssociatedPotential for Loss of EmergencyMitgation Functions White in aShutdown ConditionDATE OFISSUANCE05/28/BISSUED TOAll holders of OLS for PWRs,except those who havepermanently ceasedoperations, and havecertified that fuel has beenpermanently removed fromthe reactor vessel.98-0197-0697-05Year 2000 Readiness ofof Computer Systems atNuclear Power PlantsDegradation of SteamGenerator IntemalsSteam Generator TubeInspection Techniques05/1219812/30/9712/17/97All holders of OLS fornuclear power plants,except those who havepermanently ceasedoperations and havecertified that fuel has beenpermanently removed fromthe reactor vesselAll holders of OLS forpressurized-water reactors,except those who havepermanently ceasedoperations and have certifiedthat fuel has been perman-ently removed from thereactor vesselAll holders of OLs forpressurized-water reactors,except those who havepermanently ceasedoperations and have certifiedthat fuel has been perman-ently removed from thereactor vesselOP O Operating LcenseA'CP u Constuction PermitI NPR NucIear Power Reactors.,, ...f
.-. I. .......If you have any questions about this matter. please contact one of the technical contacts listedbelow or the appropriate regional office.sS- ' ' hiElizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andS SafeguardsOffice of Nuclear Material Safetyand afeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Feisher, NMSSIFCSS(301) 41-5521E-mail: .hffnrc.govAttachments:1. Ust of Recently issued NRC Generic LettersDOCUMENT NAME: o:%NmssqL5.OwP See Previous Co ocurrenoeIOFC [ I FCSS I C NMSSEdor lII OB lFOVr .IgO IIr .FCombsMWebera-.. .... ..NAMEa aGPurdy/AIlAl )rOaHrelsher7A? Il 1 Onciern toS~MorelI *1-1 S%..-.44/ 981 ~I Wa9 5/7 93 1p8g S-fax-198St -7 /98O FCSS l FCSS l OGC lF,NAME P*Ting RPlerson STreby- EnEyck/DATE 6/14 198 4/9 t98 5/22.1 8 6/I /98 tftP8OFFICIAL RECOCRD COPYA ....
Emgwr Reu12 Ac SIs ment;The Informnation collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-0011, which expires September 9, 2000. The publicreporting burden for this collection of information Is estimated to average 250 hours0.00289 days <br />0.0694 hours <br />4.133598e-4 weeks <br />9.5125e-5 months <br /> perresponse, Including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed, and completing and reviewing the collection ofInformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSIIMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSSIFCSS(301) 415-5521E-mail: hdf@nrc.govAttachments:1. List ot Recently Issued NRC Generic LettersDOCUMENT NAME: G:WmSSOL5.CVPOFC FCSS NMSS/Editor FCSSlNAME GPurdyiU HFelsher Elsrsus oore MWeberDATE 417/98 4/ /98 3/1698-fax- _ 41 '8 I /98 5t /98OFC FCSS IL OCI FCSS IMNSNAME Kling RPierson STreby ETenEyck DCoolDATE 6/ 198 41/ 98 5 /98 5/ 198 5/ 98OFFICIAL RECORD COPY/s ..... ..
' -;3Paoerworks Reduction Act StatementThe information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9. 2000. The publicreporting burden for this collection of information is estimated to average 250 hours0.00289 days <br />0.0694 hours <br />4.133598e-4 weeks <br />9.5125e-5 months <br /> perresponse, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed. an" completing and reviewing the collection ofinformation. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden, to the Information andRecords Management Branch, U.S. Nuclear Reguldtory Commission, Washington, D.C. 20555,and to the Desk Officer, Office of Information and Regulatory Affairs, NEOB-10202,(3150-0011), Office of Management and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth Q. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSSAMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher, NMSS/FCSS(301) 415-5521E-mail: hdf~nrc.govAttachments:1. List of Recently Issued NRC Generic LettersDOCUMENT NAME: G:owssouL.awPOFC l ll dftor ls FlS 0 ll OB liFCSSNAME GPurdyAIl HFelsher EKraus SMoore FCombs MWeberDATE l 198 41 /98 3/16/98-fax- 4/ /98 /98 i51/ /98OFC FCSS FCSS QGC FCSS IMNSNAME King RPierson MISTreby ETenEyck DCoolDATE l /198 4 /98 _s __ 5t 98 /5 /98mm~st _~oR __Yg wh*
- VNIWAL KEWKW GQFY.*~~~~~~"0fr-'a0
pagerwork Reduction Act Statement:The information collections contained in this request are covered by the Office of Managementand Budget clearance number 3150-001 1. which expires September 9, 2000. The publicreporting burden for this collection of information is estimated to average 5 hours5.787037e-5 days <br />0.00139 hours <br />8.267196e-6 weeks <br />1.9025e-6 months <br /> per response.including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Sendcomments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to the information and Records ManagementBranch, U.S. Nuclear Regulatory Commission, Washington, D.C. 20555, and to the DeskOfficer. Office of Information and Regulatory Affairs, NEOB-1 0202, (3150-0011), Office ofManagement and Budget, Washington, D.C. 20503.If you have any questions about this matter, please contact one of the technical contacts listedbelow or the appropriate regional office.Elizabeth 0. Ten Eyck, DirectorDivision of Fuel Cycle Safety andSafeguardsOffice of Nuclear Material Safetyand SafeguardsContacts: Gary Purdy, NMSS/IMNS(301) 415-7897E-mail: gwpl@nrc.govHarry Felsher. NMSSIFCSS(301) 415-5521E-mail: hdfenrc.govAttachments:1. The cco ocum ent.'Ye sessment Guide,' September 1997.2. '__ _G7-7,*trUdiajy Yx41 2000 Reddi,,es. Ozctober 1997.3. List of Recently Issued NRC Generic LettersDOCUMENT NAME: ow-ssotsowp_EOFC _8 NMSSEdor 08J l jj FCSS LNAME GPurdyfil EKraus SMoore FCombs fMWeber PTmgDATE 4/ /98 3/16A98-fax- 4/ /98 5/ /98 6/ /98OFC FCSS l OGC l FCSS lIMNS_NAME RPierson STreby ETenEyck DCoolDATE 4/ /98 5// 98 51/ 98 5/ /98__._ ---------* I.OFFICIAL KEORD COPY