ML20196L487
| ML20196L487 | |
| Person / Time | |
|---|---|
| Issue date: | 06/28/1988 |
| From: | Murley T Office of Nuclear Reactor Regulation |
| To: | Office of Nuclear Reactor Regulation |
| References | |
| NRRL-501, NUDOCS 8807070527 | |
| Download: ML20196L487 (42) | |
Text
c i
jo UNITED STATES g
[
g NUCLEAR REGULATORY COMMISSION y
WASHINGTON. D. C. 20555 g
JUN 2 81988 MEMORANDUM FOR:
All NRR Employees FROM:
Thomas E. Murley, Director Office of Nuclear Reactor Regulation
SUBJECT:
NRR OFFICE LETTER NO. 501 - SIMS PROCEDURE FOR GENERIC SAFETY ISSUES AND UNRESOLVED SAFETY ISSUES PURPOSE This Office Letter establishes NRR policies and procedures for usirg and updating infonnation relating to Generic Safety Issues (GSIs) and Unresolved Safety Issues (USIs) in the Safety Issue Management System (SIMS). This Office Letter assigns new SIMS-related responsibilities within NRR and reassigns others. Office-wide implementation of this Office Letter will result in a SIMS -
database that is more current, complete and accurate. As a consequence, SIMS will become more trustworthy and useful to NRC management and staff as an authoritative resource pertaining to the status of GSIs and USIs.
This Office Letter consists of this transmittal memorandum and three enclosures. Enclosure 1 is a basic NRR procedure for the handling of GSI and USI related SIMS issues. Enclosure 2 consists of a number of revised SIMS Data ElementDictionary(SDED)dataelementdescriptions. Enclosure 3 is a flowchart for the processing of GSIs and USIs within NRR.
RESPONSIBILITIES AND AUTHORITIES to this Office Letter defines the responsibilities and authorities of NRR staff members and managers.
It is the responsibility of each NRR staff member and manager to ensure that the procedures delineated in Enclosures 1, 2, and 3 are followed.
BASIC REQUIREMENTS All NRR staff members will use this Office Letter and its Enclosures 1, 2, and 3, as well as the NRC SIMS Procedures issued by the Deputy Director for Information Resources Management / Office of Administration and Resources Manage-ment (IRM/ ARM), as both resources and recuirements in performing their GSI/USI related SIMS duties. The NRC SIRS Procecures have been provided to all NRR employees.
p
. e'b CONTACT:
f l
,\\
kI L. Whitney, ILRB hd x21245
}
y 8807070527 880628 PDR ORG NRRB PDC
g
- l' 1
MUN2S1369 All NRR Employees It is not intended that this Office Letter result in any large-scale backfit efforts to update and correct SIMS information. Such rework of the SIMS data-base, if required, will be directed separately by NRR management on a case.
by-case basis.
It is, however, intended that this Office Letter will be fully implemented for ongoing and future actions as of its effective date.
EFFECTIVE DATE!
This Office Letter is effective immediately.
)
A&t!b h
Thomas E. Murley, Director X
Office of Nuclear Reactor Regulation
Enclosures:
\\
As stated (3) cc w/ enclosures:
V. Stello, EDO 17-G-13 J. Taylor, ED0 17-G-13 S. Ebneter, OSP 7 0-4 B. Hayes, 01 3-E-4 J. Lieberman, OE 7-H-5 W. Mcdonald, ARM MNBB.6201 C. Fitzgerald, ARM P.612 P. Bird, OP W.407 H. Thompson, NMSS 6-A-4 E. Beckjord, RES NL-007 H. Denton, GPA 17-F-2 S. Connelly, 0IA MNBB-8607 W. Russell R.I J. Grace R-II A. Davis R.III R. Martin R-IV J. Martin R.V SECY 16_H_3 J. Fitzgerald, OGC 15 8-18 OGC 15 B.18 NRC PDR Distribution w/ encl.:
H. Smith (8 cps & orig)
F. Miraglia TCentral?. File w L. Wheeler C. Thomas T. Murley ILRB RF F. Hebdon F. Gillespie D. Mossburg L. Phitney C. Miller T. Martin (88 9107)
- See previous concurrence OFC
- LPIS/ILRB* :C/LPIS/ILRB:C/ILRB/PMAS:PTSB/PPAS**:C/PTy/P S C3.AS
- A ADT j
NAME :LWhitney:rm :LKheeler
- FHebdon
- SBlack
- CT a
F t.H ie :TMar
.....:...________.:............:...____.....:............:..........:..,f.....__:.....
DATE :6/ /88
- 6/ /88
- 6/ /88
- 6/ /88
- 6 88
- 68v/88
- 6/
83 v
g 0FC
- D/ADP
- D/h
.... :. g.
NAME :FM a ia
- TRtW e
- DATE !6/ /
- 6 88
' }
i @
5x NRR OFFICE LETTER NO. 501 SIMS PROCEDURE FOR GENERIC SAFETY ISSUES AND UNRESOLVED SAFETY ISSUES l
BACKGROUND SIMS collects and retains data for the purpose of ensuring that safety and/or other regulatory concerns are resolved (including any required modifications of the NRC's regulatory programs and/or licensee facilities, staff, and procedures).
Required actions are imposed by means of the following regulatory vehicles:
Rules, Orders, Generic Letters, Bulletins, and license amendments.
SIMS does not address the following nonregulatory guidance and/or 11 formation documents:
Regulatory Guides, NUREGs, Standard Review Plens, Policy Statements, Technical Positions, Information Notices, Inspection Procedures Confirmatory Action Letters and enforcement letters.
SIMS is a database that provides reports on the status of generic and plant-specific safety issues.
It can accept direct input of data. Also, SIMS can draw on the Regulatory Information Tracking System (RITS) datebase.
RITS is an NRR maintained database for reporting inspection and licensing actions and their related resource expenditures (staffhours of effort). SIMS never updates RITS information. However, selected RITS data fields directly update certain SIMS data fields.
If a SIMS field is derived from a RITS field, direct update of that SIMS field will be overridden by the RITS information during the next RITS update of SIMS.
The Generic Issue Management and Control System (GIMCS) is a series of reports generated from the SIMS database. The Office of Nuclear Regulatory Research (RES) usually updates the GIMCS-related SIMS data fields. GIMCS tracks safety issues from the issue identification phase through to the technical resolution phase. Technical rcsolution is the point at which the NRC detemines the following:
the requirements that are to be imposed on licensees the timetable for licensee response and implementation the imposition vehicle (Generic Letter, Rule, Order, etc.)
That portion of the SIMS Data Element Dictionary (SDED) that pertains to NRR SIMS functions has been revised to specify the following new information:
ASSUMPTION (for a limited number of SIMS fields)
FIELD LEVEL AUTOMATED DATA ENTRY RESPONSIBLE ORGANIZATION l
t 2
UPDATE AGENT UPDATE FREQUENCY UPDATE METHOD DISCUSSION (for some SIMS fields)
The SDED has been revised to explicitly provide guidance on the processing of Generic Safety Issues (GS!s) and Unresolved Safety Issues (USIs) within NRR.
GSIs and USIs are those multiplant safety issues that are technically resolved by Commission vote after extensive study, typically by RES.
Data elements pertaining to NRR SIMS functions are listed in Sections D, E, and F of the NRC SIMS procedures. The NRR related data element descriptions addressed in this Generic Safety Issue SDED revision effort are attached as to this Office Letter.
Future revisions of this Office Letter will promulgate revised data element descriptions for other sources of imposition vehicles.
At certain locations in this Office Letter and the SDED the term "Generic Safety Issue" is used to collectively denote GSIs and USIs. However, the term "generic safety issue" (no caps) is used in these documents to denote any and all issues applicable to more than one plant that may result in any fonn of imposit'lon vehicle (Bulletin, Generic Letter, etc.).
DEFINITIONS Issue Task Manager. The RES staff member responsible for tracking a generic safety issue from its identification to its technical resolution.
Lead Technical Manager. The NRR staff member responsible for conducting initial NRR processing of a generic safety issue up to the point of imposi-tion vehicle issuance.
This individual will usually be a member of the Associate Director for Inspection and Technical Assessment (ADT) staff.
MultiPlant Action (MPA) Lead Project Manager. The NRR staff member, usually 6 member of the Associate Director for Projects (ADP) staff, with responsibility for monitoring, tracking, and facilitating the timely completion of the fol-lowing tasks related to a certain generic safety issue:
Project Manager and Lead Technical Reviewer reviews of licensee responses to a generic imposition vehicle.
Project Manager and Lead Technical Reviewer negotiations with licensees regarding modifications and implementation schedules.
Project Manager tracking of licensee implementation activity.
Project Manager monitoring of regional verification inspection activity.
Project Manager. The ADP/NRR staff member responsible for licensing reviews for a particular docket (reactor facility).
Lead Technical Reviewer. The NRR staff member responsible for conducting, or overseeing the conduct of, technical reviews of licensee responses to a generic
o.
imposition vehicle, as requested by ADP. This individual will almost always be from the ADT staff and may have been the Lead Technical Manager, Regional SIMS Coordinator. The regional staff member responsible for the ad-ministration of Regional inputs into SIMS regarding verification inspection activities.
ACRONYMS The following is a list of organizational acronyms appearing in enclosures to this Office Letter:
NRR - Office of Nuclear Reactor Regulation ADP - Associate Director for Projects ADT - Associate Director for Inspection and Technical Assessment PMAS - Program Management, Policy Developm9nt and Analysis Staff ILRB - Inspection, Licensing and Research integration Branch IPIS - Inspection Program Integration Section GAIS - Generic Activities Integration Section PMSB - Planning, Program and Managemst Support Branch ARM - Office of Administration and Resource Management IRM - Deputy Director for Information Resources Management RMB - Records Management Branch RES - Office of Nuclear Regulatory Research Resp 0NSIBILITIES, AUTHORITIES AND BASIC REOUIREMENTS It is an NRR goal that the time for the imposition and implementation phases pertaining to GSIs and USIs should total no more than 36 months, approximately two outage cycles at most reactor facilities.
It is an NRR goal that the veri-fication process (which may not be a 100% inspection program) should be completed no more than 6 months from the date of the letter in which the licensee reported the modifications as complete.
If there is no intent on the part of the NRC to cause the licensee to implement changes to the plant or site, procedures, management or staffing, or financial resources, it is not necessary for ADP to require licensees to submit the implementation confirmation letters described in Enclosure 2.
If an imposition vehicle only requests licensees to provide review or analysis results to the NRC, the licensee submittal will be treated as the required implementation confirmation letter for the purpose of SIMS tracking.
Responsibilities and authorities related to SIMS have been largely derived from the information provided in the reworked NRR-related SIMS data element descriptions in the SDED. NRR responsibilities and authorities and the serial number (where applicable) of the SDED fields from which they were derived are listed below. SDED fields provide a more detailed discussion of these
4-responsibilities, authorities and basic requirements. An NRR Generic Issue processing flowchart is attached as Enclosure 3 to this Office Letter. The flowchart was derived directly from the reworked NRR-related SIMS data element descriptions of the SDED.
The listed data element fields below are those for which the subject individual or organization is mentioned in Enclosure 2 as either having update responsibility or other responsibilities Where Enclosure 1 and Enclosure 2 conflict, Enclosure 2 takes precedence.
Note that NRR employees may have responsibilities flowing from SIMS data element descriptions while not having update authority for that data element.
Associate Director for Inspection and Technical Assessment
- (usually) manages SIMS-related activities of the Lead Technical Managers (034)
- (usually) manages the SIMS-related activities of the Leaa Technical Review-ers (035)
- detemines whether verification is needed for an issue (039)
- determines whether an inspection program change is necessary for an issue (047)
- enters the Inspection Progran Change Completion Date (048)
- may declare that imposition by NRR is not applicable (issue level) (066)
- determines the Issue Level Verification Priority Code (068)
- may concur in a decision by ADP that implementation is not applicable (plant level)(088)
- nay concur in a decision by the cognizant Regional or Headquarters inspec-tion division that verification inspection activity is not applicable (plant level)(090)
- explains the technical requirements for inspection program changes (127)
Lead Technical Manager
- enters the Licensed Plant Imposition Panagement Technique Other Than Multiplant Action (MPA) (034)
- enters whether approval of licensee submittals is needed (035)
- enters whether post-implementation review of licensee submittals is needed (035A)
- enters the Nonlicensed Plant Imposition Management Technique Other Than Standard Review Plan (SRP) (036)
.S.
- enters whether an SRP update is necessary. (037)
- enterstheImpositionInitiationDate(073)
- identifies the reactor plants for which an issue is applicable, with the assistance of the MPA lead Project Manager (073)
- enterstheImpositionInitiationDateStatusCode(074) lead Technical Reviewer
- conducts technical reviews of licensee submittals as requested by project managers (035A)
' assists the project niarager in determining the technical adequacy of pro-posed licensee resolutions of issues (085)
Associate Director for Projects
' may, with the concurrenes of ADT, declare that implementation is not appli-cable (plant level) (088)
- obtains authority to use a Multiplant Action (MPA) code number for an issue from the Planning, Program and Management Support Branch (PMSB) and, in coordination with IRM/ ARM, ensures that the code appears on the appropriate SIMS printouts for all applicable reactor plants.
Current practice is that the MPA Lead Project Manager, at this time, also opeas up TAC numbers for eachapplicableplant.(032)
- provides PMSB with the Multiplant Action (HPA) title (033)
- provides support to the Lead Technical Manager in identifying reactor plants for which an issue is applicable (065)
- enters the Individual Plant Imposition Management Technique Code (081)
Project Manager
- refers licensee sub.r.ittals to the Lead Technical Reviewer when appropriate (refer to the "DISCUSSION" section of data element 035A)
- enters the Docket Priority Code (082)
' enters the Application Date (083)
- enters the Licensing Action Completion Date (085)
O
- enters the Licensing Action Completion Date Status Code (036)
- enters the Implementation Completion Date (087)
- enters the Implementation Completion Date Status Code (088)
- enters the Licensee's Implementation Completion Confimation Letter Date (088A) enters the Plant Specific Verification Priority Code (091)
Plannino, Progra,a and Management Support Branch maintains a file of MPA code numbers and titles (032, 033)
Inspection Program Integration Section, Inspection, Licensing and Research Integration Branch i
lists staff processing requirements for an issue (043)
- enters the.(projected and actual) Staff Requirements Completion Date (045) enters the Staff Requirements Completion Date Status Code (046)
- enters the actual Inspection Program Change Completion Date (048) enters the Inspection Program Change Status Code (049)
Generic Activities Integration Section, Inspection. Licensing and Research Integration Branch
- coordinates the assignment by ADP of MPA Lead Project Managers (032) coordinates the assignment by ADT of Lead Technical Managers (034) coordinates.the assignment by I of Lead Technical Reviewers (035A)
Cognizant Regional or Headquarters [ vision Conducting Inspection
- may, with the concurrence of ADT, declare that verification inspection activity is not applicable (plant level) (090)
Regional or Headquarters Inspector enters the Verification Completion Date (089) enters the Verification Corpletion Date Status Code (090)
- enters the In.cpection Report Number (097)
- enters Inspection Remarks (098)
s-FIEL'D #:
032 FIELD NAME:
MULTIPLANT ACTION'(MPA) CODE FIELD LEVEL:
ISSUE LEVEL I
FIELD FORMAT:
4 CHARACTERS FIRST POSITION: ALPHABETIC SECOND POSITION:
THIRD AND FOURTH POSITIONS: NUMERIC FIELD DEFINITION:
THIS FIELD PROVIDES A CODE FOR THE UNIQUE IDENT-IFICATION OF A MULTIPLANT ACTION (MPA) ITEM AUTOMATED DATA ENTRY:
THE MPA LEAD PROJECT MANAGER, IN C00RDINATICN WITH IRM/ ARM, WILL ENSURE THAT THIS CODE IS ENTERED < FOR ALL APPLICABLE PLANTS AFTER OBTAIN-ING THE CODE FROM PMSB.
iv BLANK FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
PARENT ORGANIZATION OF THE HPA LEAD PROJECT MANAGER, USUALLY ADP UPDATE AGENT:
MPA LEAD PROJECT MANAGER UPDATE FRE0VENCY:
WHEN THE MPA LEAD PROJECT MANAGER IS APPOINTED (USUALLY ONE TIME ONLY)
UPDATE METHOD:
MARKUP 0F THE SIMS REPORT #310 ("DUMP REPORT")
FOR THE ISSUE DISCUSSION:
ENTRY OF DATA IN THIS FIELD SHOULD CORRESPOND TO A BLANK (N0 ENTRY) IN FIELD #034 THE PARENT ORGANIZATION OF THE MPA LEAD PROJECT MANAGER IS RESPONSIBLE FOR MANAGING THE SIMS RELATED ACTIVITIES OF THAT INDIVIDUAL.
ASSIGNMENT OF THE MPA LEAD PROJECT MANAGER IS l
C0ORDINATED THROUGH GAIS/ILRB.
l
i FIELD #:
033 FIELD NAME:
.MULTIPLANT ACTION (MPA) TITLE FIEl.D FORMAT:
75 CHARACTERS OF FREE FORM TEXT FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE DESCRIPTIVE NARRATIVE-USED TO IDENTIFY THE PU9 POSE OF THE MULTIPLANT ACTION.
AUTOMAT'ED DATA ENTRY:
THE TITLE WILL BE PULLED BY SIMS FRCM MPA FILE MAINTAINED BY PMSB.
BLANK FOR PLANT SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
IRM/ ARM (MPA LEAD PROJECT MANAGER PROVIDES THE HPA TITLE TO PMSB WHEN'THE MPA CODE NUMBER IS OBTAINED)
UPDATE AGENT:
SIMS UPDATE FREQUENCY:
UPON ENTRY IN FIELD #032 TYPICALLY ONE TIME ONLY UPDATE METHOD:
COMPUTER GENERATED DISCUSSION:
ENTRY OF DATA IN THIS FIELD SHOULD CORRESPOND TO A BLANK (NO ENTRY) IN FIELD #034.
SIMS REPORTS NORMALLY DISPLAY FIELD #004 (THE ISSUE TITLE ASSIGNED DURING THE ISSUE IDENTIFI-CATION PHASE). FIELD #033 WILL, HOWEVER, COR-RESPOND CLOSELY WITH FIELD #004.
FIELD #:
034 FIELD NAME:
LICENSED PLANT IMPOSITION MANAGEMENT TECHNIQUE OTHERTHANMULTIPLANTACTION(MPA)
FIELD FORMAT:
25 CHARACTERS OF FREE-FORM TEXT FIELD LEVEL:
ISSUE LEVEL 4
FIELD DEFINITION:
THIS FIELD NAMES THE MANAGEMENT TECHNIQUE THAT THE IMPOSING AND IMPLEMENTING OFFICE WILL USE TO TRACK AND CONTROL THE ISSUE FROM IMPOSITION THROUGH VERIilCATION, OTHER THAN ASSIGNING AN MPA SERIAL NUMBER.
EXAMPLES ARE: REFERRAL.T0 NON-U.S. GOVERNMENT AGENCIES UNDER INTERNATIONAL AGREEMENT, REFERRAL TO NON-NRC STATE OR FEDERAL GOVERNMENT AGENCIES OR DEPARTMENTS, AND NRC OVERSIGHT OF INDUSTRY INITIATIVES UNDER FORMAL AGREEMENT.
THIS FIELD DOES NOT IDENTIFY THE IMPOSITION VEHICLE (FIELD #DED).
AUTOMATED DATA ENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
PARENT ORGANIZATION OF 1HE LEAD TECHNICAL MANAGER, USUALLY ADT UPDATE AGENT:
LEAD TECHNICAL MANAGER UPDATE FREQUENCY:
USUALLY ONE TIME ONLY UPDATE METHOD:
MARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR l
THE ISSUE DISCUSSION:
THE PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER IS RESPONSIBLE FOR MANAGING THE SIMS-RELATED ACTIVITIES OF THAT INDIVIDUAL.
ASSIGNMENT OF LEAD TECHNICAL MANAGERS IS C0ORD-t l
INATED THROUGH GAIS/ILRB.
l l
a.
t FIELD #:
035 U
' FIELD NAME:
APPROVAL OF LICENSEE SUBMITTAL 'NEEDED?
FIELD FORMAT:
3 CHARACTERS:
"YES", "N0", "N/A" FIELD LEVEL:
ISSUE LEVEL 1
-FIELD DEFINITION:
THIS FIELD SPECIFIES WHETHER REVIEW AND APPROVAL 0F A LICENSEE SUBMITTAL ARE NECESSARY FOR THIS.'SSUE, AUTOMATED DATA ENTRY:
"N/A" FOR PLANT-SPECIFIC ISSUES RESPONSISLE' ORGANIZATION:
PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER, TYPICALLY ADT UPDATE AGENT:
LEAD TECHNICAL MANAGER UPDATE FREQUENCY:
TYPICALLY ONE TIME ONLY UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE 6
4
FIELD #:
035A FIELD NAME:
POST-IMPLEMENTATION REVIEW OF LICENSEE SUBMITTAL NEEDED?
FIELD FORMAT:
3 CHARACTERS: "YES","N0", OR "N/A" FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD SPECIFIES WHETHER REVIEW AND APPROVAL OF A LICENSEE SUBMITTAL ARE NECESSARY AFTER IMPLEMENTATION BY THE LICENSEE.
AUTOMATED DATA ENTRY:
"N/A" FOR PLANT-SPECIFIC ISSUES P' RENT ORGANIZATION OF THE LEAD TECHNICAL RESPONSIBLE ORGANIZATION:
A MANAGER, TYPICALLY ADT UPDATE AGENT:
LEAD TECHNICAL MANAGER UPDATE FREQUENCY:
TYPICALLY ONE TIME ONLY UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
IN REGARD TO EITHER PRE-IMPLEMENTATION OR POST-IMPLEMENTATION REVIEW, THE PROJECT MANAGER MAY REFER THE LICENSEE'S SUBMITTAL TO THE LEAD TECHNICAL REVIEWER. THE PARENT ORGANIZATION OF THE LEAD TECHNICAL REVIEWER (USUALLY ADT) IS RESPONSIBLE FOR MANAGING THE SIMS-RELATED ACTIV-ITIES OF THAT INDIVIDUAL.
ASSIGNMENT OF LEAD TECHNICAL REVIEWERS IS COORD-INATED THROUGH GAIS/ILRB.
4 FIELD #:
036 FIELD NAME:
NONLICENSED PLANT IMPOSITION' MANAGEMENT TECHNIQUE OTHER THAN STANDARD REVIEW PLAN (SRP)
FIELD FORMAT:
25 CHARACTERS OF FREE FORM TEXT 4
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS. FIELD NAMES THE MANAGEMENT TECHNIQUE, OTHER THAN THE STANDARD REVIEW PLAN (SRP), THAT THE IPF0 SING AND INPLEMENTING OFFICE WILL USE TO TRACK AND CONTROL THE ISSUE FROM IMPOSITION THROUGH TO VERIFICATION AT NON-LICENSED PLANTS.
AN EXAMPLE OF A NON-SRP MANAGEMENT TECHNIQUE IS DIRECT AMENDMENT OF THE PROPOSED OPERATING LICENSES OF THE. SUBJECT REACTOR FACILITIES.
SUCH A NON-SRP MANAGEMENT TECHNIQUE MAY BE ACCOMPLISHED SIMULTANE0USLY WITH AN SRP REV-ISION.
THIS FIELD DOES NOT IDENTIFY THE IMPOSITION VEHICLE (FIELD #UEU).
AUTOMATED DATA ENTRY:
N/A
~
RESPONSIBLE ORGANIZATION:
PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER, USUALLY ADT UPDATE AGENT:
LEAD TECHNICAL MANAGER UPDATE FREQUENCY:
TYPICALLY ONE TIME ONLY UPDATE METHOD:
MARKUP 0FSIMSREPORT#310("DUMPREPORT")FOR THE ISSUE f
x n-FIELD #:
037 FIELD NAME:
STANDARDREVIEWPLAN(SRP)UPDATENECESSARY?
N '
FIELD FORMAT:,_
3 CHARACTERS:
"YES","N0",'"N/A" FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIEL[ SPECIFIES WHETHER.THE STANDARD REVIEW PLAN WILL BE UPDATED TO ENSURE THAT THE ISSUE IS IMPOSED AT EACH REACTOR FACILITY APPLYING FOR' AN OPERATING LICENSE.
, AUTOMATED DATA ENTRY:
"N/A" FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORCANIZATION:
PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER, TYPICALLY ADT UPDATE AGENT:
LEAD TECHNICAL MANAGER UPDATE FREQUENCY:
USUALLY ONE TIME ONLY UPDATE METHOD:
MARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE l
DISCUSSION:
THE INFORMATION IN THIS FIELD SHOULD BE BASED ON REVIEW 0F THE TECHNICAL RESOLUTION PACKAGE AND INTERVIEWS WITH THE RES ISSUE TASK MANAGER, IPIS/ILRB, AND ADP.
l
,3 o
- - +
a.
FIELD #:
039
- c,,
FIELD NAME:
VERIFICATION NEEDED?
. FIELD FORMAT:
3 CHARACTERS: - YES", "N0", "N/A" FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD SPECIFIES WHETHER A VERIFICATION INSPECTION WILL BE NECESSARY FOR THIS ISSUE.
AUTOMATED DATA ENTRY:
"N/A" FOR PLANT-SPECIFIC ISSUES s
RESPONSIBLE ORGANIZATION:
ADT UPDATEAGENT:
THE ASSIGNED INDIVIDUAL FROM THE ADT STAFF.
UPDATE FREQUENCY:
TYPICALLY ONE TIME ONLY 4
UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
ADT SHOULD MAKE APPROPR! ATE ENTRIES IN FIELDS
- 047, #048, #068 AND #127 WHENEVER ADT UPDATES FIELD #039.
ADT SHOULD REVIEW THE TECHNICAL RESOLUTION PACKAGE AS AN AID IN DETERMINING THE NECESSITY FOR A VERIFICATION INSPECTION.
P
j4.
FIELD #:
\\
043
~
s FIELD NAME:
LISTING 0F STAFF PROCESSING REQUIREhENTS 4
s FIELD FORMAT:.
50 CHARACTERS OF FREE-FORM TEXT FIELD LEVEL:
ISSUE LE\\EL FIELD DEFINITION:
THIS FIELD SPECIFIES ALL DOCUMENT DEVELOPMENT ACTIVITIES FOR THIS ISSUE (FOR EXAMPLE: STANDARD REVIEW PLAN CHANGES, NEW OR PODIFIED INSPECTION PROCEDURES OR TEMPORARY INSTRUCTIONS, OR SAFETY EVALUATION REPORTS). THE CURRENTLY CONTROLLING STAFF REQUIREMENT SHOULD BE CLEARLY IDENTIFIED.
COMPLETED STAFF REQUIREMENTS SHOULD BE INDICATED BY A "(C)".
AUTbMATEDDATAENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
ILRB/PPAS UPDATE AGENT:
IPIS/ILRB UPDATE FREQUENCY:
AT LEAST QUARTERLY UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE I
DISCUSSION:
REVIEW 0F THE TECHNICAL RESOLUTION PACKAGE MAY I
PROVIDE INFORMATION ON THE CONTENT OF THIS FIELD.
l IPIS/ILRB SHOULD REVIEW FIELDS #037, #039, #047, i
- 068, AND #127 FOR INFORMATION REGARDING FIELD l
- 043.
IF NO REQUIRED DOCUMENT DEVELOPMENT l
ACTIONS EXIST, "N0 ACTIONS REQUIRED" SHOULD BE l
ENTERED IN FIELD #043, 1
l
.o
s-:
N.
g
'~ -
FIELD #:
045 1.h_.
-\\
'.g
~
FIELO NAME:
STAFF REQUIREMENTS' COMPLETION DATE FIELD FORMAT:
"YYMM" OR BLAfK y
x s
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE PROJECTED OR ACTUAL C0f1PLETION DATE FOR THE CURRENTLY CONTROLLING STAFF REQUIREMENT FROM FIELD #043.
AUTOMATED DATA: ENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGAtlIZATION:
ILRB/PMAS s
UPDATE-AGENT:
IPIS/ILRB
~ UPDATE FREQUENCY:
AS NECESSARY TO ENSUPE THAT THIS FIELD IS CUR-RENT i
- UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE l
l l
i i
L:
.(
u-z-
FIELD #:
046 FIELD NAME:
STAFF REQUIREMET.TS COMPLETION DATE STATUS CODE i
. FIELD FORMAT
= COMPLETE 4
' "N"
= NOT APPLICABLE BLANK = IN PROGRESS FIELD LEVEL:
ISSUE LEVEL 4
\\ FIELD DEFINITION:
THIS FIELD PROVIDES THE STATUS OF THE CURRENTLY
\\
CONTROLLING STAFF REQUIREMENT FROM FIELD #043.
AUTOMATED DATA ENTRY:
"N" FOR PLANT-SPECIFIC ISSUES a
RESPONSIBLE ORGANIZATION:
ILRB/PMAS UPDATE AGENT:
IPIS/ILRB UPDATE FREQUENCY:
AS NECESSARY TO ENSURE THA1 THIS FIELD IS CUR-RENT (IN PRACTICE, THIS FIELD WILL REMAIN BLANK UNTIL THE LAST REQUIRED DOCUMENT DEVELOPMENT ACTIVITY'0F FIELD #043 IS COPPLETED)
UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE l
t 6
\\
i r
n.,
^^
~\\
'lf FIELD #:
047 i
. FIELD NAME:
INSPECTION PROGRAM CHANGE NECESSARY?
'\\
\\
FIELD FORMAT:
3 CHARACTERS:
"YES", "N0", "N/A" s
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD SPECIFIES WHETHER AN INSPECTTION PROGRAM CHANGE (INSPECTION MODULE OR TEMPORARY INSTRUCTION DEVELOPMENT OR MODIFICATION) IS NEC-ESSARY FOR THE VERIFICATION OF THE SUBJECT ISSUE. NORMALLY, AS A MINIMUM, A TEMPORARY INSTRUCTION SHOULD BE DEVELOPED DIRECTING A SHORT-TERM EXPANSION IN SCOPE FOR AN EXISTING (UNMODIFIED)INSPECTIONMODULE.
AUTOMATED DATA ENTRY:
"N/A" FOR PLANT-SPECIFIC ISSUES
\\
RESPONSIBLE ORGANIZATION:
ADT UPDATE AGENT:
AN ASSIGNED INDIVIDUAL FROM THE ADT STAFF UPDATE FREQUENCY:
TYPICALLY +0NE TIME ONLY UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ('; DUMP REPORT") FOR THE ISSUE DISCUSSION:
ADT WILL 'JPDATE FIELD #127 TO DESCRIBE THE INSPECTION PROGRAM CHANGES THAT ARE NECESSARY,
1 048!
FIELD #:
c e
- p
\\
FIELD NAME:
It!SPECTION PROGRAM CHANGE COMPLETION DATE FIELD FORMAT:
,"YYMM" OR BLANK 4
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE DATE BY WHICH THE CHANGE TO THE INSPECTION PROGRAN DESCRIBED IN FIELD
- 1271,'ILL BE NEEDED (0R WAS ACCOMPLISHED) FOR POSTIMPLEMENTATION VERIFICATION INSPECTION.
i-AUTOMATED DATA ENTR :
BLANK FOR PLANT-SPECIFIC ISSUES 4
i RESPONSIBLE ORGANIZATION:
ADT (FOR PROJECTED ["NEEDED BY"] DATES)
ILRB/PMAS (FOR THE DATE OF COMPLETION
[SEE FI2LD # 049])
UPDATE AGENT:
ASSIGNED INDIVIDUAL FROM THE ADT STAFF (FOR PROJECTED ["NEEDED BY"] DATES)
IPIS/ILRB (FOR THE DATE OF COMPLETION
[SEE FIELD # 049])
UPDATE FREQUENCY:
INITIALLY ON ENTRY OF A "YES" IN FIELD #047 (INSPECTION FROGRAM CHANGE NECESSARY CODE).
THEREAFTER, WHENEVER A CHANGE OCCURS IN THE ADT DETERMINATION OF THE REQUIRED IMPLEMENTA-TION COMPLETION DATE, AND WHFN THE CHANGE IS ACCOMPLISHED.
UPDATE METHOD:
MARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE o
l, a
i
^
s t
J
^4 FIELD #:
i 049 FIELD NAME:
INSPECTION R0 GRAM CHANGE STATUS CODE FIELD FORMAT:
"C"
= DEVELOPMENT COMPLETE "N"
= NOT APPLICABLE
+
BLANK = IN PROGRESS P
FIELD LEVEL:
ISSUE LEVEL
- FIELD DEFINITION:
THIS FIELD SPECIFIES WHETHER AN INSPECTION PRO-GRAM CHANGE IS COMPLETE AUTOMATED DATA ENTRY:
"N" IF FIELD #047 IS "N0" OR "N/A" "N" FOR PLANT SPECIFIC ISSUES RESPONSIBLEt0RGANIZATION:
ILRB/PMAS (OR IRM/ ARM IF AUTOMATED DATA ENTRY)
UPDATE AGENT:
IPIS/ILRB (OR SIMS IF AUTOMATED DATA ENTRY)
UPDATE FREQUENCY:
AS NECESSARY TO ENSURE THAT THIS FIELD IS CI'R-RENT i
UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE (0R COMPUTER GENERATED IF FIELD #047 IS "N0" OR "N/A")
1 1
k E
Lp; -
- i.
.; FIELD #:.
050 e
FIELD NAME:-
REGULATORY FORM FIELD FORMAT ~:
l' 10CHARACTERSOFFREI-FORMTEXTAPPEARING4 TIMES PER ISSUE.
i FIELD LEVEL:
ISSUE LEVEL
-~
I FIELD DEFINITION:
THIS FIELD SPECIFIES THE VARIOUS (UP TO FOUR)
REGULATORY FORMS FOR THE SUBJECT ISSUE.
1 AUTOMATED DATA ENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
USUALLY RES, ALTHOUGH OTHER OFFICES MAY BE TASKED WITH ANY OR ALL OF THE SAFETY ISSUE PROCESSING PHASES FROM ISSUE IDENTIFICATION THROUGH TECHNICAL RESOLUTION UPDATE AGENT:
USUALLY THE ISSUE TASK MANAGER i
UPDATE FREQUENCY:
AS NECESSARY TO ENSURE THAT THIS FIELD IS CUR-RENT UPDATE METHOD:
MARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
FOR EXAMPLE, A RULE MAY BE FOLLOWED BY A GENERIC LETTER, FOR A TOTAL OF TWO REGULATORY FORMS.
~'
PROPOSED REGULATORY FORMS MAY ALSO BE LISTED IN FIELD # 050.
4 t
y
~.
44 FIELD #:
068 i
FIELD NAME:
ISSUE LEVEL VERIFICATION PRIORITY CODE FIELD FORMAT:
"H" = HIGH "M"
= MEDIUM "L"
= LOW "N" = NO ACTION REQUIRED (NOT SAFETY SIGNIFI-CANT OR NOT APPLICABLE) c i
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
CONSIDERING THIS ISSUE'S' INHERENT SAFETY SIGNIFICANCE AND ITS SAFETY SIGNIFICANCE RELA-TIVE TO ALL OTHER IMPOSED ISSUES IN SIMS AND TOPICS EVALUATED UNDER THE CURRENT NRC OR INSTITUTE OF NUCLEAR POWER OPERATIONS (INP0)
INSPECTION PROGRAMS, THIS DATA ELEMENT INDICATES THE SAFETY SIGNIFICANCE OF CONDUCTING VERIFICA-TION INSPECTION AFTER LICENSEES HAVE COMPLETED IMPLEMENTATION.
AUTOMA'TED DATA ENTRY:
"N" IF VERIFICATION NEEDED (FIELD #039) IS "N0" OR "N/A" "N" FOR PLANT-SPECIFIC ISSUES RESPONSIBLE ORGANIZATION:
ADT UPDATE AGENT:
ASSIGNED INDIVIDUAL FROM THE ADT STAFF UPDATE FREQUENCY:
AS NECESSARY TO ENSURE THAT THIS FIELD IS CUR-RENT UPDATE METHOD:
MARKUP 0F SIMS REPdRT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
ADT SHALL NOT CONSIDER THE CURRENT OR PROJECTED AVAILABILITY OF INSPECTION RESOURCES. HOWEVER, THE FEASIBILITY AND PRACTICALITY OF POSTIMPLE-MENTATION INSPECTION OF THE CONCERN MAY BE CONSIDERED.
i BECAUSE OF UNIQUE REACTOR PLANT SITUATIONS, THE PLANT SPECIFIC VERIFICATION PRIORITY CODE (FIELD
- 091) MAY DIFFER FROM THIS CODE.
.a l
N y
r
~
FIELD #:
073 FIELD NAME:
IMPOSITIONINITIITIONDATE
/
FIELD FORPAT:
"YYMM" OR' BLANK 1
FIELD LEVEL:
' ISSUE LEVEL FI' ELD DEFINITION:
THE IMPOSITION INITIATION DATE IS THE ACTUAL l
t OR PROJECTED DATE OF ISSUANCE OF THE MOST RECENT l
IMPOSITION VEHICLE--(THE DOCUMENT THAT IMPOSES
-/-
REPORTING, REC 7AD KEEPING, ANALYSIS, E0VIPMENT l
OR PROCEDURAL MODIFICATIONS, AND/OR STAFFING CHANGE REQUIREMENTS ON LICENSEES). THIS MAY
/
BE THE DATE OF ISSUANCE OF A GENERIC LETTER 4
WHICH FOLLOWS A FINAL RULE.
AUTOMATED DATA ENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES
+
RESPONSIBLE ORGANIZATION:
PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER (USUALLY ADT)
UPDATE AGENT:
-THE LEAD TECHNICAL MANAGER (USUALLY FROM ADT)
UPDATE FREQUENCY:
AT LEAST QUARTERLY UNTIL THE IMPOSITION VEHICLE IS ISSUED 1
UPDATE METHOD:
PARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
HRR PAY NOT ISSUE AN IMPOSITION VEHICLE FOR EACH ISSUE.
IN SUCH A CASE, FIELD # 073 WILL BE DATE OF ISSUE OF THE MOST RECENT IMPOSITION VEHICLE FOR THE SUBJECT ISSUE (SEE FIELD # 050).
THE LEAD TECHNICAL VANAGER IDENTIFIES THE REACTOR PLANTS FOR WHICH THE SUBJECT ISSUE IS APPLICABLF., CLOSE COORDINATION WITH, AND STRONG y
SUPPORT BY, THE MPA LEAD PROJECT MANAGER IS ThEREFORE APPROPRIATE. THE TECHNICAL RESOLUTION P/10KAGE AND THE ISSUE TASK MANAGER WILL ALSO BE OF HELP IN THE IDENTIFICATION OF APPLICABLE PLANTS.
k
'l j,
th-
.c
'- - 'g s
FIELD #:
074 I
.jl
~
FIELD NAME:
i It! POSITION INITIATION DATE STATUS CODE i
FIELD FORMAT:
' "C?
= COMPLETE-(ISSUED)
"N"
= NOT APPLICABLE BLANK = ANY DATEflN FIELD # 073 FOLLOWED BY A
+
BLANK IS A PROJECTED DATE.
FIELD LEVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE PROJECTED OR ACTUAL ISSUANCE STATUS OF THE FINAL IMPOSITION VEHICLE.
FOR EXAMPLE, FOR RULES,WF0LLOW-0N GENERIC LETTER IS THE FINAL IMPOSITION VEHICLE.
IT IS NOT NECESSARILV THE CASE THAT NRP WILL HAVE T3TUED THE FINAL IFPOSITION VERTELE.
c
/ AUTOMATED DATA ENTRY:
"N" FOR PLANT-SPECIFIC ISSUES
+
RESPONSIBLE ORGANIZATION:
THE PARENT ORGANIZATION OF THE LEAD TECHNICAL MANAGER (USUALLY ADT)
UPDATE AGENT:
THE LEAD TECHNICAL MANAGER (USUALLY FROM ADT) r UPDATE FREQUENCY:
ONE TIME
/
UPDATE METHOD:
MARKUP 0F SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE DISCUSSION:
ADT MAY DETERMINE THAT NRR ACTION IS NOT APPROPRIATE.
IN THAT CASE, AN "N" WILL BE ENTERED IN FIELD #074 AND FIELD #073 WILL BE LEFT BLANK. THIS IS ONLY THE CASE WHEN ABS 0-LUTELY NO FURTHER NRR ACTION IS TO BE TAKEN WITH RESPECT TO THE SUBJECT ISSUE.
I r
f d
V
,.c, t
o t,
]
\\
j FIELD #:
081 FIELD NAME:
INDIVIDUAL PLANT IMPOSITION MANAGEMENT TECHNIQUE CODE f
FIELD. FORMAT:
"M" = MULTIPLANT ACTION (MPA)
"S" = STANDARD REVIEW PLAN (SRP)
"I" = REFERRAL TO NON-U.S. GOVERNMENT AGENCIES UNDER INTERNATIONAL AGREEMENTS "N" = REFERRAL TO NON-NRC STATE OR FEDERAL GOV-ERNMENT AGENCIES OR DEPARTMENTS
- 0" = NRC OVERSIGHT OF INDUSTRY INITIATIVES UNDER FORMAL AGREEMENTS "U" = UNIQUE IMPOSITION MANAGEMENT TECHNIQUE "P" = PROJECT MANAGER OVERSIGHT (FOR PLANT-SPECIFIC ISSUES FIELD LEVEL:
PLANT LEVEL FIELD DEFINITI0A:
THIS FIELD PROVIDES THE MANAGEllENT TECHNIQUE ACTUALLY USED TO ENSURE THE PROGRESS OF AN ISSUE FI)0M IMPOSITION THROUGH VERIFICATION AT A SPE-CIFIC REAtt0R PLANT.
FOR SOME ISSUES FIELD #081 MAY BE "M" FOR OPERATING PLANTS AND "S" FOR 10'OLS)
AUTOMATED DATA ENTRY:
"P" FOR PLANT-SPECIFIC. ISSUES RESPONSIBLE ORGANIZATION:
USUALLY ADP UPDATE AGENT:
UPDATE FREQUENCY:
USUALLY ONE TIME ONLY l
UPDATE METHOD:
THIS FIELD DOES NOT CURRENTLY APPEAR ON THE PROJECT MANAGER'S REPORT (PMR). ADP AND IRM WILL COORDINATE TO DETERMINE THE UPDATE METHOD.
/
/
- ~
FIELD #:
082
/FIELDNAME DOCKET PRIORITY'CCDE I
FIELD FORMAT:
"!i" = HIGH j
"M" = MEDIUM "L" = LOW "N" = NO ACTION REQUIRED (NOT SAFETY SIGNIFICANT OR NOT APPLICABLE)
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE PROJECT MANAGER'S DETERMINATION OF THE PLANT-SPECIFIC SAFETY SIGNIFICANCE OF PROGRESSING THIS= ISSUE RELATIVE TO ALL OTHER ISSUES CURRENTLY IMPOSED AT THIS REACTOR FACILITY.
t AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORCANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER LPDATE FREQUENCY:
WHENEVER RELATIVE SAFETY SIGNIFICANCE CHANGES FROM ONE GROUPING (H, M, L, OR N AB0VE) TO ANOTiiER UPDATE METHOD:
THIS FIELD DOES NOT CURRENTLY APPEAR ON THE PROJECT MANAGER'S REPORT (PMR). ADP AND IRM WILL C0 ORDINATE TO DETERMINE THE UPDATE METHOD, i
l l
I e
f w
--n w
.me n,.
y,
w w
4"
=.
FIELD 1:
033 FIELD NAME:
APPLICATION DATE j
FIELDFORMAi:
"YYMH" OR BLANi;
^
FIELD LEVEL:
PLANT LEVEL
- /-
1, FIELD DEFINITION:
THIS FIELD PROVIDES THE DATE OF THE FIRST LICEN-j SEE RESPONSE TO AN IMPOSITION VEHICLE. THIS IS NEVER A PROJECTED DATE.
- /
FOR PLANT-SPECIFIC ISSUES, THIS FIELD PROVIDES THE DATE OF THE FIRST LICENSEE REQUEST FOR A LICENSING ACTION.
AUTOMATED DATA ENTRY:
N/A,-
RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FREQUENCY:
ONE TIME UPDATI METHOD:
MARK-UP 0F THE PROJECT MANAGER'S REPORT (PMR) l l
{
L l
3 ll L~
' : FIELD #:
084 f
. FIELD NAME:
APPLICATION DATE STATUS CODE FIELD FORMAT:
"C"
= COMPLETE BLANK = LICENSEE'S INITIAL RESPONSE NOT RECEIVED FIELD LEVEL:
PLANT LEVEL-FIELD. DEFINITION:
THIS FIELD INDICATES THAT THE DATE IN FIELD
- 083 IS AN ACTUAL RESP 0flSE OR REQUEST DATE.
AUTOMATED DATA ENTRY:
AUTOMATICALLY ENTERED BY SIMS WHENEVER A DATE IS ENTERED IN FIELD #083 RESPONSIBLE ORGAf;IZATION:
IRM/ ARM UPDATE AGENT:
SIMS UPDATE FREQUENCY:
ONE TIME I'
UPDATE METHOD:
COMPUTER GENERATED DISCUSSION:
THE USE OF FIELD #083 HAS CHANGED SO THAT ONLY A "C" IS APPROPRIATE IN FIELD #084.
i
c.
FIELD #:
085 FIELD NAME:
LICENSING ACTION COMPLETION DATE FIELD FORMAT:
"MMDDYY" OR BLANK FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE DATE THE NRC AGREED, OR IS PROJECTED TO AGREE, TO A RESOLUTION TO THE ISSUE.
THIS IS USUALLY THE PROJECTED OR ACTUAL DATE OF THE NRC'S SAFETY EVALUATION REPORT (SER)
TO THE LICENSEE.
AUTOMATED DATA ENTRY:
N/A J
RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FREQUENCY:
AS NECESSARY TO ENSURE THAT THIS FIELD IS CUR-RENT UPDATE METHOD:
MARKUP 0F THE PROJE' T MANAGER'S REPORT (PMR)
DISCUSSION:
NRC AGREEMENT WITH THE LICENSEE'S PROPOSED RESOLUTION MAY BE BASED ON THE RESULTS OF A REVIEW BY THE LEAD TECHNICAL REVIEWER.
FIELD #:
086
-FIELD NAME:
LICENSING ACTION COMPLETI0ll'DATE STATUS CODE FIELD FORMAT:
"C"
= COMPLETE "N"
= NOT APPLICABLE BLANK = ANY DATE IN FIELD #085 FOLLOWED BY A BLANK IS A PROJECTED DATE FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE STATUS OF LICENSING ACTION COMPLETION (SEE FIELD #085) AT THE SUBJECT REACT 09 FACILITY FOR THE SUBJECT ISSUE, BUT MAY REPRESENT COMPLETION OF SOME FORM 0F LICENSING ACTION OTHER THAN SER ISSUANCE.
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER I
UPDATE FREQUENCY:
VAUALLY ONE TIME ONLY L
UPDATE METHOD:
MARKUP 0F THE PROJECT MANAGER'S REPORT L
l i
(
FIELD #:
087 FIELD NAME:
IMPLEMENTATION COMPLETION DATE FIELD FORMAT:
"YYMM" OR BLANK ASSUMPTION:
MODIFICATIONS TO ONE OR MORE OF THE FOLLOWING HAVE BEEN DIRECTED OR APPROVED BY THE NRC:
SITE, PLANT OR EQUIPMENT, PROCEDURES (OPERATION, TEST, SURVEILLANCE, MAINTENANCE, PARTS CONTROL, RADIATION PROTECTION, EMERGENCY PLANNING, ETC.).
MANAGEMENT / STAFF (ORGANIZATION, QUALIFICATION, TRAINING, DUTIES, NUMBER OF ONSHIFT PERSONNEL, ETC.)
FINANCIALRESOURCES(CAPABILITY, STABILITY)
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THE IMPLEMENTATION COMPLETION DATE IS THE SCHEDULED DATE THAT THE AB0VE MODIFICATIONS ARE TO BE/WERE COMPLETELY INSTALLED AND FUNCTIONING AS AN INTEGRAL PART OF THE LICENSEE'S ON/0FF SITE OPERATIONS.
ON RECEIPT OF THE LICENSEE'S URITTEN DOCUMENTATION (CONFIRMATION) THAT THE REQUIRED MODIFICATIONS HAVE BEEN COMPLETED, THE REPORTED ACTUAL COMPLETION DATE SHALL BE ENTERED IN FIELD 4087. NO PARTIAL COMPLETION DATES SHALL BE ENTERED IN FIELD #087. FIELD #087 DOES NOT CONTAIN THE DATE OF THE LICENSEE'S LETTER FIEPORTING COMPLETION (SEE FIELD #088A).
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FREQUENCY:
USUALLY ONLY TWICE: WHEN A SCHEDULE IS AGREED UPON (PROJECTED) AND AGAIN WHEN THE MODIFICA-TIONS ARE REPORTED AS COMPLETE.
UPDATE METHOD:
MARKUP 0F THE PROJECT MANAGER'S REPORT (PMR)
DISCUSSION:
NRC MANUAL CHAPTER 0230 APPLIES REGARDING OMB APPROVAL OF REQUESTS FOR LICENSEE RESPONSES.
ADP SHOULD C0 ORDINATE WITH RMB/ ARM IN THIS EFFORT.
A REQUEST FOR IMPLEMENTATION CONFIRMATION SERVES TWO PURPOSES. FIRST, IT PROVIDES ASSURANCE THAT REQUIRED MODIFICATIONS HAVE BEEN ACCOMPLISHED.
SECOND, IT SERVES AS A "TRIGGER" FOR INSPECTION ACTIVITY.
FIELD #:
088 FIELD NAME:
IMPLEMENTATION COMPLETION DATE STATUS CODE FIELD FORMAT:
"C"
= COMPLETE "1"
= COMPLETED PREVIOUSLY BY OTHER DIRECTIVE "N"
= NOT APPLICABLE BLANK = ANY DATE IN FIELD #087 IS A PROJECTED DATE.
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD INDICATES WHETHER OR NOT IMPLEMENTA-TION IS REQUIRED OF THE LICENSEE AND IF REQUIRED, WHETHER OR NOT It.PLEMENTATION HAS BEEN COMPLETED BY THE LICENSEE.
IMPLEMENTATION INVOLVES LICENSEE MODIF.ICATIONS TO ONE OR MORE OF THE FOLLOWING:
SITE, PLANT AND EQUIPMENT PROCEDURES (OPERATION, TEST, SURVEILLANCE, MAINTENANCE, REPLACEMENT PARTS CONTROL, RADIATION PROTECTION, EMERGENCY PLANNING, ETC.)
MANAGEMENT / STAFF (0RGANIZATION, QUALIFICATION, TRAINING, DUTIES, NUMBER OF ONSHIFT PERSONNEL, ETC.)
FINANCIAL RESOURCES (CAPABILITY, STABILITY, ETC.)
IMPLEMENTATION COMPLETE ("C") MEANS THAT ALL REQUIRED MODIFICATIONS HAVE BEEN REPORTED IN WRITING (CONFIRMED) BY THE LICENSEE AS INSTALLED AND FUNCTIONING AS AN INTEGRAL PART OF THE LIC-ENSEE'S ON/0FF SITE OPERATIONS.
PARTIAL COMPLE-TION REPORTS WILL NOT RESULT IN A "C" IN THIS FIELD.
AUTOMATED DATA ENTRY:
N/A RESPCNSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FRE0VENCY:
USUALLY ONE TIME ONLY UPDATE METHOD:
ADP MAY, WITH THE CONCURRENCE OF ADT, DECLARE THAT IMPLEMENTATION IS NOT APPLICABLE, EVEN THOUGH IMPOSITION MAY HAVE BEEN CONDUCTED.
IN SUCH A CASE FIELD #088 WILL BE "N", AND FIELDS
- 087 AND #088A WILL BE BLANK.
?
'. f' FIELD #:
088A FIELD NAME:
LICENSEE'S IMPLEMENTATION COMPLETION CONFIRMA-TION LETTER DATE
-FIELD FORMAT:
"MMDDYY" OR BLANK FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE DATE OF THE C0CUMENT IN WHICH THE LICENSEE REPORTED (CONFIRMED) THAT MODIFICATIONS FOR THE SUBJECT GENERIC ISSUE WERE COMPLETE. DATES OF PARTIAL COMPLETION C0FFIRMA-TION LETTERS FROM LICENSEES SHALL NOT BE ENTERED INTO THIS FIELD.
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FREQUENCY:
USUALLY ONLY ONCE.
UPDATE METMLD:
MARKUP OF THE PROJECT MANAGE..'S REPORT (PMR) i DISCUSSION:
A "C" WILL NOT BE PERMITTED IN FIELD #088 WITHCUT A DATE BEING ENTERED IN FIELD 088A.
l l
o
\\
.9 FIELD #:
089 FIEl.0 NAME:
VERIFICATION COMPLETI08 c.'s
-FIELD FORMAT:
"YYMM" OR BLANK ASSUMPTION:
THE LICENSEE HAS PROVIDED DOCUMENTATION TO THE
~
NRC THAT THE FOLLOWING MODIFICATIONS HAVE BEEN INSTALLED AND ARE fdNCTIONIi'9 AS AN INTEGRAL PART OF THE LICENSEE'S ON/0FF SITE OPERATIONS:
PROPERTIES BUILDINGS / STRUCTURES EQUIPMENT / COMPONENTS PROCEDURES (OPERATION, TEST, SURVEILLANCE, MAINTENANCE, REPOLACEMENT PARTS CONTROL, RADIATION PROTECTION, EMERGENCY PLANNING, ETC.).
MANAGEMENT / STAFF (0RGANIZATION, 00ALIFICATION, TRAINING, DUTIES, NUMBER OF ON-SHIFT PERSONNEL, ETC.)
FINANCIAL RESOURCES (CAPABILITY, STABILITY, ETC.)
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE VERIFICATION COMPLETION DATE: THAT IS. THE PROJECTED OR ACTUAL DATE THAT THE NRC WILL ISSUE OR HAS ISSUED I'tS FINAL INSPECTION REPORT ESTABLISHING THAT ALL OF THE AB0VE MODIFICATIONS ARE SATISFACTORILY INSTALLED' AND FUNCTIONING AS AN INTEGRAL PART OF THE LICENSEE'S ON/0FF SITE OPERATIONS.
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
REGIONAL DIVISIONS ARE RESPONSIBLE FOR DOCUMENTING VERIFICATION INSPECTIONS WITHIN SIMS UNLESS FORMAL ASSIGNMENT OR TRANSFER OF INSPECTION RESPONSIBILITY TO A HEAD 0VARTERS DIVISION OCCURS.
UPDATE AGENT:
THE INSPECTOR FROM THE COGNIZANT REGIONAL OR HEADQUARTERS DIVISION UPDATE FREQUENCY:
AS NECESSARY TO TO ENSURE THAT THIS FIELD IS CURRENT UPDATE METHOD:
MARKUP OF THE INSPECTION DATA REPORT
a
. e-
. FIELD #:
090
-FIELD NAME:
VERIFICATION COMPLETION DATE STATUS CODE FIELD FORMAT:
"C"
= COMPLETE "N"
= NOT APPLICABLE BLANK = ANY DATE IN FIELD #C89 FOLLOWED BY A BLANK IS A PROJECTED DATE 0F THE FINAL VERIFICATION INSPECTION.
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE STATUS OF VERIFICATION ACTIVITY FOR THE SUBJECT ISSUE AT THE PLANT LEVEL.
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
THE COGNIZANT REGIONAL OR HEADQUARTERS DIVISION THAT CONDUCTED THE INSPECTION UPDATE AGENT:
THE INSPECTOR FROM THE COGNIZANT REGIONAL OR HEADQUARTERS DIVISION UPDATE FREQUENCY:
WHEN THE FINAL VERIFICATION INSPECTION IS SATIS-FACTORILY COMPLETED UPDATE METHOD:
MARKUP 0F THE INSPECTION DATA REPORT DISCUSSION:
THE REGIONS AND HEADQUARTERS HAVE THE OPTION OF INSPECTING LICENSEE ACTIVITIES EVEN IF FIELD
- 039 IS "N0".
THE REGIONAL OR HEADQUARTERS DIVISION WITH INSPECTION RESPONSIBILITY MAY, WITH THE CONCUR-RENCE OF ADT, DECLARE THAT VERIFICATION INSPEC-TION IS NOT APPLICABLE, ALTHOUGH IMPOSITION AND IMPLEMENTATION MAY HAVE OCCURRED.
IN SUCH A CASE, FIELD #090 WILL BE "N" AND FIELDS #089,
- 097, AND t098 WILL BE BLANK.
c-
,e
+
o.
FIELD #:
091 FIELD NAME:
PLANT-SPECIFIC VERIFICATION PRIORITY CODE FIELD FORMAT:
"H" = HIGH "M" = MEDIUM "L" = LOW "N" = NO ACTION REQUIRED (NOT SAFETY SIGNIFICANT OR NOT APPLICABLE)
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD RECORDS THE PROJECT MANAGER'S DETER-MINATION, AFTER REVIEW 0F THE ISSUE LEVEL VERIF-ICATION PRIORITY CODE OF FIELD #068 AND THE INDIVIDUAL DESIGN AND OPERATING CHARACTERISTICS 0F THE SUBJECT REACTOR FACILITY, OF THE PLANT-SPECIFIC SAFETY SIGNIFICANCE OF CONDUCTING VERIFICATION INSPECTION OF THIS ISSUE RELATIVE TO ALL OTHER ISSUES CURRENTLY APPLICABLE AND IMPLEMENTED AT THE SUBJECT REACTOR FACILITY.
AUTOMATED DATA ENTRY:
INITIALLY "N" IF VERIFICATION NEEDED (FIELD
- 039) IS "NO" OR "N/A" RESPONSIBLE ORGANIZATION:
ADP UPDATE AGENT:
PROJECT MANAGER UPDATE FREQUENCY:
WHENEVER RELATIVE SAFETY SIGNIFICANCF CHANGES FROMONEGROU."ING(H,M,L,ORNABOU)TO ANOTHER.
UPDATE METHOD:
MARKUP OF THE PLANT DATA REPORT (PDR).
DISCUSSION:
BECAUSE OF UNIQUE REACTOR FACILITY CONSIDERA-TIONS, THIS CODE 7.AY DIFFER FROM THE ISSUE LEVEL VERIFICATION PRIORITY CODE (FIELD #068).
.~
o e
s y
FIELD #:
097 FIELD NAME:
INSPECTION REPORT NUMBER FIELD FORMAT:
"YYNNN" YY = YEAR OF REPORT NNN = SEQUENTIAL SERIAL NUMBER OF THE REPORT FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES THE CONTROL NUMBER THAT UNIQUELY IDENTIFIES A VERIFICATION INSPECTION REPORT ON THE SUBJECT ISSUE AT THE SUBJECT REACTOR FACILITY. THIS FIELD MAY BE REPEATED UP TO FIVE TIMES TO REFERENCE MULTIPLE INSPECTIONS PERTAINING TO THE SAME ISSUE, AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
COGNIZANT REGIONAL OR HEADQUARTERS DIVISION CONDUCTING THE INSPECTION UPDATE AGENT:
REGIONAL OR HEADQUARTERS INSPECTOR UPDATE FREQUENCY:
WHEN AN INSPECTION REPORT IS ISSUED UPDATE METHOD:
MARKUP OF THE INSPECTION DATA REPORT DISCUSSION:
A NEW ENTRY IN FIELD #097 WILL REQUIP.E AN UPDATE OF FIELD #089; THAT IS, A FOLLOW-ON INSPECTION MAY BE CONDUCTED AFTER WHAT WAS BE-LIEVED TO HAVE BEEN THE "FINAL" VERIFICATION INSPECTION.
,a FIELD #:
098 FIELD NAME:
INSPECTION REMARKS FIELD FORMAT:
-300 CHARACTERS OF FREE-FORM TEXT t
FIELD LEVEL:
PLANT LEVEL FIELD DEFINITION: '
THIS FIELD PROVIDES A BRIEF DISCUSSION OF THE INSPECTION RESULTS INCLUDING OPEN IiEMS AND THEIR EXPECTED DATES OF COMPLETION AND/0R A STATEMENT THAT N0 MORE INSPECTION ACTIVITY IS REQUIRED.
AUTOMATED DATA ENTRY:
N/A RESPONSIBLE ORGANIZATION:
COGNIZANT REGIONAL OR HEADQUARTCAS DIVISI0h THAT CONDUCTED THE INSPECTION.
UPDATE AGENT:
THE INSPECTOR FROM THE COGNIZANT REGIONAL OR HEADQUARTERS DIVISION UPDATE FRE0VENCY:
WHEN A RELEVANT INSPECTION REPORT IS ISSUED UPDATE METHOD:
MARKUP OF THE INSPECTION DATA REPORT
-l
. - 6:.. ;,
fn i
FIELD #:
107 FIELD NAME:
INSPECTION PROGRAM CHANGE TECHNICAL REQUIREPENTS FIELD FORMAT:
300 CHARACTERS OF FREE-FORM TEXT FIELD 1.EVEL:
ISSUE LEVEL FIELD DEFINITION:
THIS FIELD PROVIDES EXPLANATORY TEXT DESCRIBING THE TECHNICAL REQUIREMENTS DEVELOPED BY ADT REGARDING INSPECTION PROGRAM MODULES OR TEMP-ORARY INSTRUCTIONS TO BE DEVELOPED OR MODIFIED UNDER THE DIRECTION OF IPIS/ILRB.
AUTOMATED DATA ENTRY:
BLANK FOR PLANT-SPECIFIC ISSUES l
RESPONSIBLE ORGANIZATIOh:
ADT UPDATE AGENT:
THE ASSIGNED INDIVIDUAL FROM THE ADT STAFF UPDATE FREQUENCY:
INITIALLY WHEN "YES" IS ENTERED IN FIELD #047 AND THEREAFTER AS NECESSARY TO ENSURE THE f: ELD IS CURRENT UPDATE METHOD:
MARKUP OF SIMS REPORT #310 ("DUMP REPORT") FOR THE ISSUE (THE APPROPRIATE SPACE FOR THIS ENTRY ON THE DUMP REPORT IS CURRENiLY LABELED "MODIFICATION TEXT" AND WILL BE REVISED TO READ "INSPECTION PROGRAM CHANGE").
I m,
I a <
a w
NRR GENERIC ISSUE PROCESSING FLOWCHART ISSUE LEVEL.
a GAIS/ILRB/PMAS 032,034,035A
~
I L
L LEAD TECHitlCAL MANAGER ADT (TYPICALLY ADT) 039,047,ME,068.127 034,035,035A,036,037,073,074 I
I IPIS/ILRB/PMAS 043,045,046,048,049 v
PLANT LEVEL v
MPA LEAD PROJECT MANAGER (TYPICALLY ADP) 032,033,081 1
L IRM/ ARM PROJECT MANAGER 084 082,083 085(WITHLEADTECHNICALREVIEWER) 086,087,088A,091 1
I L
LEAD INSPECTOR (REGIONORHET.DQUARTERS) 089,090,097,098 l
.-