ML24044A215

IMC 0306 Planning, Scheduling, Tracking, and Reporting of the Reactor Oversight Process (ROP)

ML24044A215
Person / Time
Issue date:	05/10/2024
From:	Aron Lewin NRC/NRR/DRO/IRIB
To:
References
DC 24-007, CN 24-014
Download: ML24044A215 (1)

Text

NRC INSPECTION MANUAL IRIB

INSPECTION MANUAL CHAPTER 0306

PLANNING, SCHEDULING, TRACKING, AND REPORTING OF THE REACTOR OVERSIGHT PROCESS (ROP)

TABLE OF CONTENTS 0306-01 PURPOSE................................................................................................................. 1 0306-02 OBJECTIVES............................................................................................................. 1 0306-03 APPLICABILITY......................................................................................................... 1 0306-04 DEFINITIONS............................................................................................................ 1 04.01 Agencywide Documents Access and Management System (ADAMS)...................... 1 04.02 Cost Activity Codes (CACs)....................................................................................... 2 04.03 Configuration Control Board (CCB)........................................................................... 2 04.04 Direct Inspection Effort (DIE)..................................................................................... 2 04.05 Enterprise Project Identifier (EPID)............................................................................ 2 04.06 Indirect Inspection Activities....................................................................................... 2 04.07 Inspection Planning Cycle (IPC)................................................................................ 2 04.08 Non-Direct Inspection Effort....................................................................................... 2 04.09 Plant Issues Matrix (PIM)........................................................................................... 3 04.10 RPS-Inspections........................................................................................................ 3 04.11 Unique Site Budget Model (USBM)........................................................................... 3 0306-05 RESPONSIBILITIES AND AUTHORITIES................................................................ 3 05.01 Division of Reactor Oversight (DRO)......................................................................... 3 05.02 Regional and Headquarter Offices............................................................................. 4 0306-06 GENERAL INSTRUCTIONS AND REQUIREMENTS............................................... 4 06.01 Inspection Planning - Creating Inspection-Related Activities.................................... 5 06.02 Generating Inspection Report Numbers and EPIDs.................................................. 6 06.03 Associating Inspection-Related Activities and Time Charging Guidance.................. 9 06.04 Entering and Approving Completed Inspection Samples......................................... 11 06.05 Entering and Approving Inspection Results............................................................. 12 06.06 Finalizing and Closing Inspection Reports............................................................... 16 06.07 Modifying Issued Inspection Report (Corrections, Revisions or Appeals)............... 18 06.08 Inspection Procedure Completion Status................................................................. 19 06.09 Non-Result Items Tracked in RPS -Inspections........................................................ 21 06.10 Mid-Year Planning Letters, Assessment Letters, and Inspection Schedule Plans.. 23 06.11 ROP Web Posting Process, Content and Schedule................................................ 23 06.12 Inspection Program and Auto Report Generator Management............................... 26 06.13 Administration of RPS-Inspections.......................................................................... 26 06.14 Tools for Scheduling and Performance Monitoring.................................................. 26 06.15 Communicating System Problems/Potential Enhancements................................... 27 0306-07 REFERENCES........................................................................................................ 27 : Inspection Report Numbering........................................................................ Att1-1 : Inspection Item Numbering............................................................................ Att2-1 : Inspection Completion Status Illustrative Examples...................................... Att3-1 : Management of Complex Inspection Results [C4]......................................... Att4-1 : Table of Abbreviations and Acronyms........................................................... Att5-1 : Revision History for IMC 0306....................................................................... Att6-1

Issue Date: 05/10/24 i 0306 0306-01 PURPOSE

01.01 Establishes the basic guidelines and standards for the use, data entry, and control of the Reactor Program System - Inspections m odule (RPS-Inspections ) and other Nuclear Regulatory Commission (NRC) information systems (such as the Cost Activity Code system (CACs)), used to support implementation of the Reactor Oversight Process (ROP). This inspection manual chapter focuses on the RPS -Inspections system.

01.02 Specifies the responsibilities and authorities for the use of the RPS -Inspections m odule and other NRC information systems used to support the ROP.

01.03 Provides guidance to headquarters and regional staff on charging time spent performing ROP activities.

0306-02 OBJECTIVES

02.01 To ensure consistency in the format and content of ROP -related data entered into RPS-Inspections and other NRC information systems.

02.02 To ensure that ROP -related data entered into RPS -Inspections and other NRC information systems are complete, accurate, and timely to support plant and ROP self-assessment activities.

02.03 To ensure proper control and access to RPS-Inspections and other NRC information systems by program office and regional office users.

02.04 To ensure consistent time charging and use of RPS -Inspections for ROP activities.

0306-03 APPLICABILITY

This Inspection Manual Chapter (IMC ) applies primarily to staff who use RPS-Inspections to plan, schedule, and report on operating reactor inspection information. The information provided in this IMC can also be used by those using RPS -Inspections for the planning and scheduling of non-operating reactor inspection activities, such as decommissioning, independent spent fuel storage, fuel cycle, etc.

0306-04 DEFINITIONS

The terms used in this manual chapter are consistent with the definitions provided in IMC 0305, Operating Reactor Assessment Program, IMC 0611, Power Reactor Inspection Reports, IMC 2201, Security Inspection Program for Commercial Nuclear Power Reactors, and IMC 2515, Light W ater Reactor Inspection Program.

04.01 Agencywide Documents Access and Management System (ADAMS)

The official recordkeeping system, through which the NRC provides access to vast "libraries" or collections of documents related to the agencys regulatory activities.

Issue Date: 05/10/24 1 0306 04.02 Cost Activity C odes (CACs)

A unique, six-character alphanumeric or numeric code that is aligned to the agencys budget structure business line, product line and product (BL/PL/P). CACs represent fee and non-fee-billable activities for mission direct and mission indirect, corporate direct, corporate indirect, and administrative work performed by NRC and contractor staff. In RPS-Inspections a CAC is associated with each inspection procedure and activity that is linked with a docket and an EPID, creating a combination assignment string for inspectors. CACs associated with work performed for inspections are assigned to employees by their supervisor, through RPS-Inspections as a CAC, docket and EPID combination.

04.03 Configuration Control Board (CCB)

A board that makes decisions regarding whether proposed changes to RPS-Inspections should be implemented. The CCB uses a structured process, defined by the Office of the Chief Information Officer (OCIO), to evaluate, prioritize and propose changes to the RPS Executive CCB, which is made up of and chaired by stakeholder management. (See non-public ADAMS document ML19269C125)

04.04 Direct Inspection Effort(DIE)

Time spent conducting inspection activities using an inspection procedure (IP).

04.05 Enterprise Project Identifier (EPID)

A standard alphanumeric code representing a project or inspection. The CAC system allows activities and costs to be grouped for project-based activities, such as licensing actions and inspection reports. T he EPID mimics the traditional inspection report numbering scheme, including the year that onsite work begins.

04.06 Indirect Inspection Activities

Activities that support the core mission-direct activities. This includes supervisory, non-supervisory support, and administrative assistance time. It also includes time spent developing and delivering mission training programs.

04.07 Inspection Planning Cycle (IPC)

The annual cycle for planning of baseline inspections. The minimum number of samples defined for each baseline inspection activity is required to be completed in each IPC.

Biennial, triennial, and quadrennial cycles consist of two, three, and four IPCs respectively.

04.08 Non-Direct Inspection Effort

Time spent supporting direct inspection effort (DIE). Examples include preparation, documentation, travel, significance determination process, etc.

Issue Date: 05/10/24 2 0306 04.09 Plant Issues Matrix (PIM)

A consolidated listing of individual plant issues (i.e., inspection findings /violations) except for licensee-identified violations (LIV s), unresolved items (URI), observations, assessments, etc. Consists of the i ntroduction section of each finding/violation and other key information such as cornerstone, identification credit, significance determination, and cross-cutting aspect. Information can be found in the non-public RPS-Inspections report IR3, PIM. The PIM is the source for information that is posted to the public webpage concerning NRC findings/violations.

04.10 RPS-Inspections

A web -based application that provides an integrated methodology for managing, planning, scheduling, reporting, generating inspection reports, and analyzing inspection functions and activities performed by the NRC regions and headquarters. Sometimes referred to as the Inspection Scheduling, Tracking, and Reporting (ISTAR) system.

04.11 Unique Site Budget Model (USBM)

A site approved for N+1 staffing in accordance with IMC 2515, Light Water Reactor Inspection Program - Operations Phase. Site receives a level of resources greater than what a site would normally receive. Additional inspection resources needed to effectively implement the ROP and to obtain adequate assessment of licensee safety performance due to the sites unique design, environment, and associated challenges this presents.

0306-05 RESPONSIBILITIES AND AUTHORITIES

05.01 Division of Reactor Oversight (DRO )

a. Ensure that RPS-Inspections implementation is consistent with related NRC policies, programs, guidance, and other NRC information systems.

b. Work with all inspection programs to ensure inspection procedures (IPs) are connected to the correct IMC (and appendix where applicable) under the RPS -Inspections/IP Management tab.

c. Ensure procedure hours, sample sizes, auto report generator templates, and scope texts are updated in the RPS-Inspections /IP Management tab when changes occur.

d. Coordinate with OC IO and the Office of the Chief Financial Officer ( OCFO) to ensure accuracy of databases integrated with RPS-Inspections. This includes ensuring plant information, such as p hase codes, are updated as plants transition from construction to operational, or operational to decommissioning, and ensuring all activities and procedures in RPS-Inspections have a valid CAC.

e. Resolve RPS-Inspection s implementation problems, prioritize system issues and enhancements through the RPS-Inspections and Executive RPS CCBs, as well as update and issue implementation guidance.

f. Ensure the timely and accurate transfer of inspection reports, assessment letters, and inspection schedule plans from ADAMS to the web server to support the posting of this information to the ROP webpage.

Issue Date: 05/10/24 3 0306

g. Verify the accuracy and timeliness of the data maintained in RPS -Inspections and on the ROP webpage in accordance with established schedules. Periodically sample data found in various standard R eplacement RPS (RRPS) Reports queries (such as IR 8, Baseline Inspection Complete, and IR 10, ROP Sample Completion by Inspection Report) for accuracy, and provide results to DRO management. [C3]

h. Control access to RPS-Inspection s by program office users.

i. Maintain RPS-Inspections tools and guides up to date as changes to the program are implemented and provide training, as needed.

05.02 Regional and Headquarter Offices

a. Ensure the timely and accurate entry of RPS-Inspection s related information and data for all applicable inspection activities including, but not limited to: inspection schedule plans, staff assignments, samples completed, inspection results, and inspection report status.

b. Ensure effective management (initial entry, updates, and closeout) of open items tracked in RPS-Inspections in accordance with regional policies, procedures, and practices.

c. Ensure individual staff level access in RPS-Inspections is appropriate for the assigned office.Includes maintaining Operator Licensing Examiner reactor technology qualifications up to date under the RPS-Inspections/Admin tab.

d. Verify staff is assigned to the appropriate site, report, and inspection-related activities to facilitate accurate time reporting in the agencys time and labor reporting system.

e. Ensure the timely and accurate entry of inspection reports, assessment letters, and inspection schedule plans into ADAMS to support the posting of this information to the Reactor Oversight Process (ROP) webpage. Verify the accuracy and timeliness of the data maintained in RPS-Inspections and on the ROP webpage.

f. Supports continued improvements in RPS-Inspections by reporting concerns and identifying improvements/efficiencies in processes. Maintain representatives on the RPS-Inspections CCB.

0306-06 GENERAL INSTRUCTIONS AND REQUIREMENTS

Detailed step-by -step guidance on how to use the various features and functions of the RPS-Inspections module can be found in the non -public RPS-Inspections Desktop Guide located within the application (which can be found under the Help section using the Desk Guide link). Requests for deviations from the guidance below s hall be submitted to the D RO/ROP Inspection Branch (DRO /IRIB) branch chief for review and approval. Requests can be made via email or memorandum.

It is anticipated that all inspection reports will be generated in RPS-Inspections using the auto report generator functionality. In rare cases, when RPS-Inspections cannot support auto report generation, an inspection report can be created outside of RPS -Inspections. When this occurs, ensure all samples and inspection results documented in the issued report are accurately reflected in RPS-Inspections, and approved. To accomplish this, some portion of each result

Issue Date: 05/10/24 4 0306 needs to be entered into RPS-Inspections and approved. To generate the proper tracking numbers for each result, the associated report shall be placed in a final status prior to report issuance. These tracking numbers shall be used for each of the documented results in the inspection report to ensure accuracy of data between the application and the issued report.

Every effort should be made to ensure the information within RPS -Inspections (scope, samples, and results) are maintained as close as possible to what is contained in the issued inspection report that is placed on ADAMS.

Time spent performing activities in support of the ROP is entered into the agencys time and labor reporting system in accordance with guidance provided by OCFO, the Office of Nuclear Reactor Regulation (NRR), and the regions.

06.01 Inspection Planning - Creating Inspection-Related Activities

a. All inspection activities conducted under IMC 2201 and IMC 2515 shall be scheduled and entered in RPS-Inspections.

b. Staff shall ensure the appropriate major activity code, activity type, and inspection procedure is selected when scheduling an inspection. A list of major activity codes and activity types can be found in ADAMS (ML19142A328). For example:

• When scheduling IMC 2515, Appendix C, inspection activities, staff should choose OTHER -Other Activities, as the major activity code, unless the inspection is associated with EP (use EP) or Security (use S).

• When scheduling a security baseline inspection, staff should use the 71130 series of IPs (designated as SG) and the activity types associated with security (for travel (SGT), prep and doc (SPD)) need to be used. This guidance also applies to EP inspections where the 71114 (except for 71114.06) are designated as EP. Use the activity types associated with EP: EPT, EPP etc.).

c. All quarterly integrated inspection activities and procedures that are conducted by the resident inspectors, shall be marked as on site only and are not marked as announced.

d. All non-resident inspection procedures that are expected to appear in RPS -Inspections Reports/IP 22, Inspection Activity Planned Report, shall be marked as announced and on site.

e. To ensure accuracy of the RPS-Inspections scheduling tool, and accurate reporting of time in the agencys time and laboring reporting system, staff should ensure the dates entered in RPS-Inspections accurately reflect their expected date range. Avoid using large date ranges whenever possible. For example, a regional inspector assigned to assist in an inspection typically performed by a resident inspector should enter a specific date range for their activity and avoid defaulting to the entire quarter. In addition, if planned inspection dates change, ensure that all associated date fields, including the "Inspection Completion Date field for the activity, are updated.

f. Planned Outages and INPO dates shall be maintained and kept up to date in RPS-Inspections to help ensure inspections are performed when required and to avoid burden on the licensee to the best extent possible when INPO and NRC could be on site

Issue Date: 05/10/24 5 0306 at the same time. Details concerning outages and INPO activities are not made public and information should be treated with appropriate sensitivity.

g. Sites designated as a Unique Site Budget Model (USBM) should plan to complete additional inspection samples (greater than nominal) based on documented approvals obtained from DRO in accordance with IMC 2515. Minimum sample completion is the same as single and multi-unit sites without a USB M designation.

h. Initial Operator Licensing Examinations/and Retake Examinations shall be scheduled in RPS-Inspections. The number of applicants and the author for each exam ination shall be entered under the activity code for Initial License Exam Administration (EXAD), to assist in the planning for this activity. See non-public ADAMS document ML19142A328 for a list of activity codes to be used for scheduling initial and retake examinations.

i. When scheduling Independent Spent Fuel Storage Installation (ISFSI) inspections at Part 50 sites that have not yet transitioned to ISFSI storage only, create separate entries and reports (Part 50 and 72) for each docket to RPS -Inspections. The Part 72 item is created for the purpose of charging time and creating a Part 72 report number. T he Part 50 item is created for the purpose of Report 22, Site Inspection Activity Plan, creation and documenting the sample in the integrated inspection report.

j. Lead inspectors shall ensure the contracting officers representative (COR) is assigned to the inspection activity and inspection procedure for inspections involving the use of contractors. The COR will not charge time to the inspection but must be listed in the inspection for payment requests that are made to U.S. Treasury for those inspections.

k. Non-NRC staff who observe or participate in an inspection may also be assigned to the inspection activity to capture their involvement.

l. Distinct activities are required for actions related to non-Green findings or non-SL IV violations and shall be created under Schedule New Item. These distinct activities will be associated to separate, individual letters and reports. These include updating an:

• Apparent violation (AV) with a pending significance to an AV with a preliminary color;

• AV with a pending significance or AV with a preliminary color to a final color ;

• AV to a final severity level violation (for Traditional Enforcement).

m. Inspection procedures used to resolve any URIs should be marked as on site regardless of where the follow-up inspection occurred. This action will add the inspectors name to the list of inspectors.

06.02 Generating Inspection Report Numbers and EPIDs

a. Inspection report numbers are generated through RPS-Inspections, based on the report type selected, and can be done by anyone with an RPS-Inspections user role.

Step-by -step instructions to generate an inspection report can be found in the RPS-Inspections Desktop Guide. See attachment 1 for details on the numbering convention used for inspection reports.

b. If an incorrect report type is selected, the report will need to be cancelled in RPS-Inspections/Inspection Report tab. This will ensure the report number will be available for future use. If this error is caught after hours have been charged to the

Issue Date: 05/10/24 6 0306 report/EPID with the incorrect report type, the time charge will need to be corrected in the agencys time and labor reporting system once a new inspection report is requested with the correct report type. At this point the incorrect EPID can be cancelled.

c. The creation and association of inspection reports to scheduled items should be accomplished in accordance with established regional practices, to the best extent possible. When creating a new report, staff shall utilize the following guidance for entering the required information:

First Create New Repo rt window:

Office Select from drop down.

Docket Application defaults to all units associated for the site selected and should be adjusted to include only the specific dockets for the given inspection report.

Report Type Select from drop down.

Inspection Type Select from drop down.

Organization Region Select from drop down.

Responsible Organization Select from drop down. Should be the EPID Contact Supervisor's assigned branch.

First Date Available in Input a date that starts before or on the same day before Agencys Time & Labor the first activity that needs to be performed. Typically, Reporting System (EPID about 2-3 months prior to the first onsite inspection date to Start Date) allow for charging time to prep, travel, etc.

Inspection Completion The last day of the quarter for quarterly integrated reports, Date or the anticipated date for the exit meeting - typically the last day on site for standalone reports.

Due Date RPS auto-generated field of 30 or 45 days after the exit meeting, depending on the inspection type.

Report Number Year Type the 4-digit number of the year in which the first onsite direct inspection effort will occur. For operator licensing examination, this is the year the exam will be administered.

Are contractors going to be Choose the appropriate radio button, either yes or no used?

If yes, enter the Anticipated level of effort for the EPID The Contracting Officers Representative (COR) should be contacted to determine the dollar amount to be entered.

Second Create New Report window:

Report/EPID Title Should be clear enough to inform the user of the overall inspection conducted and a designation of the site in which it occurred. The following format is preferred:

Inspection Type - Site Abbreviation. Examples:

Fire Protection - LM Security Baseline Inspection - NMP Quarterly Integrated Inspection - NMP

Issue Date: 05/10/24 7 0306 EPID Contact Typically, the senior resident inspector for quarterly integrated inspection report, and the team lead for standalone reports.

NOTE: the EPID Contact cannot be the same as the EPID Contact Supervisor, per directions provided by OCFO EPID Supervisor Typically, the Branch Chief responsible for the inspection (In RPS-Inspections it is and issuing the associated inspection report the EPID Supervisor)

d. A separate i nspection report number will need to be created when a finding/violation is identified as a result in an Office of Investigations (OI) report, and the finding/violation will not be documented in an existing inspection report. Obtaining a separate inspection report number from RPS -Inspections will allow inspectors to document any inspection results identified in the investigation effort. The administratively opened report needs to be closed once the OI investigation letter is issued in accordance with s ection 06.06.

The OI letter should list the inspection report number in the subject line of the report cover letter (to allow for traceability).

e. The process for creating new reports needs to be followed for all reports including those associated with AV follow-up activities. AV follow-up is addressed by opening a new inspection report for enforcement conferences, follow -up SDP work, significance and enforcement review panels (SERPs), etc., and the final determination letter must be issued under that new report number.

f. For inspections involving ISFSI at Part 50 sites that have not yet transitioned to ISFSI storage only, create two inspection report numbers - one for the Part 50 inspection and one for the Part 72 inspection. The Part 72 report is created for the purpose of charging time. The Part 50 report is created for the purpose of Report 22, Site Inspection Activity Plan, creation and documenting the sample in the integrated inspection report.

g. W hen a report number is created, an EPID request will also be generated. Once an EPID request is approved in RPS-Inspections by a time and labor reporting approving official, the request will be sent to the CAC s ystem indicating that an EPID has been requested and approved. CACs will send back the EPID number to RPS-Inspections.

The EPID number is linked to the created inspection report.

EPID numbers are made up of four parts. The first section of the EPID is always the letter I to indicate that the EPID is for an inspection or L for licensing ( including operator licensing examinations ). The second section is the year in which the first onsite direct inspection effort or the administration of the operator licensing examinations will occur. The third section of the EPID number is the last three digits of the inspection report number that the EPID was created for. The fourth section is a unique number that is auto-generated for OCFO purposes. Examples:

EPID I-2019-002-0001 for a second quarter 2019 integrated inspection report or EPID L-2019-OLL -0018 for an initial operator licensing examination administered in 2019.

Issue Date: 05/10/24 8 0306

h. Administrative changes to EPIDs (except changing the start date) are made from the RPS-Inspections/Inspection R eports tab. Requests for changes to the EPID start date can be requested through the OCFO ATLPC non -public SharePoint site.

i. The EPID Contact and the EPID Contact Supervisor information must be kept up to date. If staff are no longer assigned to, or involved with, the associated inspection, the information needs to be updated in accordance with the timeliness requirements established in the NRCs Labor Reporting Policy & Guidance (non-p ublic, ML19106A125).

06.03 Associating Inspection-R elated Activities and Time Charging Guidance

a. Inspector assignments to procedures and activities (such as travel, prep and doc, etc.) in RPS-Inspections, shall require assign ing inspectors to the scheduled item and checking the box to the left of their name.This also creates an approval request for the newly assigned activity.

b. CAC assignments for inspection-related and operator licensing activities shall only be requested through RPS-Inspections unless directed otherwise by OCFO. Approved CACs for use are maintained in the RPS-Inspections system under the IP Management (IPM) Tab. D RO is responsible for assigning the approved CAC to its corresponding IP and activity.

c. Requests for CAC assignments can be done by anyone with an RPS-Inspections u ser role. For the CAC to appear in an inspectors time and labor reporting profile for use, it needs to be approved in RPS-Inspections by a Branch Chief/Approving Official or above.

Responsible Branch C hiefs must verify that the appropriate IP and activity type is assigned to the correct inspection and is consistent with the associated Major Activity Codes when approving inspections in RPS -Inspections. A list of Major Activity codes can be found in the non-public ADAMS document ML 19142A328. [C1]

d. For inspections involving ISFSI at Part 50 sites that have not yet transitioned to ISFSI storage only, create two inspection report numbers - one for the Part 50 inspection and one for the Part 72 inspection. The Part 72 report is created for the purpose of charging time. The Part 50 report is created for the purpose of Report 22, Site Inspection Activity Plan, creation and documenting the sample in the integrated inspection report.

e. For multi-unit single-owner sites, inspection hours can be charged to only one unit if the licensee agrees and the inspection report references all the docket numbers for the site.

Licensees are billed based on the reported data, so time must be reported accurately.

The NRC analyzes reported data to assist program refinements and budget formulation (IMC 0307, Appendix B, ROP Realignment Process). For inspections performed under just one docket number on multi -unit sites, special inspections, supplemental, license renewal, and refueling outages, etc., hours should only be charged to the specific unit on which the inspection was performed.

f. For End-of-Cycle (EOC) and Mid-Year planning activities :

1. A report number shall be generated to track, and document activities associated with mid-year planning and EOC assessment. The report number assigned to these activities shall be linked to the year for which performance is being assessed. For

Issue Date: 05/10/24 9 0306 example, for CY 2019, the mid-year planning letter will be assigned 05000###/

2019 005 and issued in August 2019 whereas the Annual Assessment letter for plant performance would be assigned 05000###/ 2019 006 and issued in March 2020. T he mid-year and annual assessment activities occur primarily in the 2-3 months after the mid-and end of year. The period for the mid-year activities is assigned as approximately July-September for 20xx005 and the end-of-year activities is assigned as approximately December - March for 20xx006.

2. Time shall be charged to the 20XX005 inspection report for mid-cycle review activities and the 20XX006 inspection report for the EOC assessment activities for the calendar year being assessed.

For example, work associated with the 2020 inspection period, including preparing for and participating in the internal assessment meeting, and the development of the inspection schedule and assessment letter, shall all be charged to the appropriate 2020005 or 2020006 report number irrespective of when the work was performed.

3. All assessment-related activities sh all be charged to the CACs associated with the appropriate activity codes for baseline (ASM), emergency preparedness (ESM), and security (SSM), and assigned to report 20xx005 (for the mid-year planning letter),

and report 20xx006 (for the annual assessment letter).

4. All activities associated with ongoing or quarterly assessments, including preparing for and conducting EOC public meetings, s hall be charged to the associated quarterly integrated report. For example, if the EOC public meeting to discuss 2019 licensee performance is conducted in the third quarter of 2020, then t he time spent on these activities should be charged to the third quarter resident integrated report (2020003).

g. All activities associated with enforcement related orders, including confirmatory orders,

shall be charged to the specific procedures and activity codes listed in Yellow Announcement (YA) 20-0060, Time Charging for Enforcement-Related Orders, Including Confirmatory Orders Fee-Billable Cost Activity Code, issued August 18, 2020 (non-p ublic, ML23223A124).

h. Each senior resident inspector (SRI) and resident inspector (RI) shall be assigned (based on facility type) the appropriate Activity and CAC code (FRII code (CAC 001500),

NRII code (CAC 001491), or ORII code (CAC 001496)) to each quarterly integrated inspection to account for time spent performing fee-billable indirect inspection activities as established in the NRCs Labor Reporting Policy & Guidance, (non-public, ML19106A125).

The appropriate resident inspector indirect CAC code shall be used only by those assigned to a site with an SF-50 designation as a permanent or temporary/acting resident inspector. The CAC shall not be used by visiting inspectors providing site coverage for a short duration while the SRI or RI is away from the site.

When the SRI or RI are conducting indirect inspection activities while conducting a back-up site visit or participating on an inspection not at their normally assigned site, they should continue to charge their time to the ORII CAC with the docket and EPID combination that is associated with their normally assigned site.

Issue Date: 05/10/24 10 0306

i. Inspectors shall charge hours to the CAC codes which reflect the work being performed.

It may be appropriate to use an activity CAC (such as prep/doc or COM) while on site if work in these areas is being performed. It may also be appropriate to charge time to direct inspection efforts (inspection procedures) while in the office.

06.04 Entering and Approving Completed Inspection Samples

a. Where appropriate, the RPS-Inspections auto report generator has been loaded with pre-established content (aka ghost text) for each inspection procedure to aid the inspector in documenting the performance of the inspection procedure and the samples completed (typically captured under the Scope sections of a report). This ghost text may be modified, as applicable. D RO is responsible for creating and updating the ghost text when changes to the inspection procedure requirements are made or new procedures are created (such as with a Temporary Instruction (TI)). See the non-public RPS-Inspections Desktop Guide for instructions regarding how to modify the ghost text.

b. Inspectors should enter the description of the inspection sample and/or scope into RPS-Inspections as soon as practical after completion of the sample.

c. Scope information and sample completion for any inspection involving Official Use Only may be inputted into RPS-Inspections. However, Safeguards information shall NOT be placed into RPS-Inspections at any time.

d. A sample should be designated in RPS -Inspections as a partial sample when an inspection is started in one inspection period and is planned to be completed in another.

For example, when outages span two inspection periods, the inspector should document the work performed in the first quarterly report as a partial sample, and the remaining work performed as a completed sample in the second quarterly report. See the non-public RPS-Inspections Desktop Guide for how to indicate a sample as partial.

When using the partial sample option, expand the scope documentation to indicate what inspection activities were specifically completed. See IMC 0611 for an example write-up.

e. Samples associated with ISFSI inspections only need to be documented under the Part 50 report to be included in the report output. However, it is recommended that the sample also be documented in the applicable Part 72 report in RPS.

f. Unresolved items (URIs) are closed in RPS-Inspections based on the inspection report that documents the resolution. See the non-public RPS-Inspections Desktop Guide for how to discuss or close a URI. When performing a follow -up inspection for URIs, the inspector should document their work by adding a statement to the appropriate scope section indicating that the URI was reviewed. Use the same procedure which opened the URI to close it, unless it is not a baseline procedure. A sample should not be credited if following up a URI in which a sample was already accounted for (no double counting).

See IMC 0611 for details on documenting the scope, sample and results of the review.

g. The Branch Chief responsible for the inspection-related activity performed (feeder or quarterly report) shall review the scope and samples documented by the inspector and move the toggle from in progress to approved if they find the documentation acceptable. This enables the scope and samples associated with that inspection activity to appear in the report when the report is placed in a final status in RPS-Inspection s.

Issue Date: 05/10/24 11 0306 06.05 Entering and Approving Inspection Results

a. Inspectors should enter inspection results into RPS -Inspections during the inspection process. The result should be documented in accordance with IMC 0611 using the I plan to document, feature in the auto report generator function.

b. Findings and/or violations resulting from allegation follow -up or OI effort need to be added to RPS-Inspections under the report created for this effort to ensure proper tracking and accounting.

c. Inspectors shall fill in all applicable fields associated with the type of result selected. The tracking data for each result must be reviewed and completed prior to the result being approved. The PIM check box shall be checked for all results entered using t ables 1-4 of IMC 0611 (findings, apparent violations, and violations regardless of whether a color or significance has been assigned). The guidance text on the PIM Date will appear as well as the PIM Notes.The PIM Notes box is used to add additional information to those findings that are determined to be greater than G reen, and the text placed in the PIM Notes box will appear in report IR 3, PIM, with the introduction for the initial documented result. To properly track a result, the following dates will need to be entered:

PIM Date For results in a quarterly integrated report it is the last day of the quarter.

For results in a standalone report it is the inspection exit date (typically the last day of onsite inspection).

This date is automatically entered by the system from the inspection completion date field.

Projected Closeout Optional Field to be used for results in an open status.

Closure Date The date the inspection report is sent/signed (same as the Issue Date).This date is automatically entered by the system if the item is not greater than Green (GTG).

For GTG issues, it i s the date the issue is removed from the Action Matrix, and it must be entered manually. (See Note 1)

Issue Date The date the inspection report is sent/signed (same as Closure Date). This date is automatically entered by the system.

Note 1: Date should be entered within 14 days after the report has been issued to ensure proper accounting. Each office should determine who is responsible for entering this information.

Note 2: Responsibility information fields are optional fields to be used at the regions discretion.

d. An AV should not be closed and reopened as a new FIN or VIO, nor should the Event Date be changed. Instead, the AV should be revised using the document update feature (See attachment 4 for additional details ).

e. For ISFSI activities at Part 50 sites that have not yet transitioned to ISFSI storage only, the inspector needs to document the result in both the Part 50 and Part 72 inspection reports in RPS to ensure proper tracking and accounting of any inspection-related findings.

Issue Date: 05/10/24 12 0306

f. The Branch Chief responsible for the inspection activity performed shall review any results documented with that inspection activity and move the toggle from in progress to approved if they find the documentation acceptable. This enables the result associated with that inspection activity to appear in the report when the report is placed in a final status in RPS -Inspection s.

g. When discussing or closing all open items (such as LERs, SERs, and URIs) the inspectors shall use the update feature and follow the guidance in the non-public RPS-Inspections Desktop Guide. This ensures these items will be included in the Additional Issues list in the summary page of the generated inspection report.

h. If a URI, LER, or SER results in an apparent violation, finding, violation, or non-cited violation, the URI, LER, or SER should first be closed using the document update feature and then a new inspection result entry should be made by using +Create New Result and I plan to document, which will assign it em a new tracking number.

i. Issues resulting from Enforcement Guidance Memorandum s are candidates for enforcement discretion. For those issues, entries will be made in RPS-Inspections, with an explanation of the discretion, so they can be assessed properly in accordance with IMC 0305.

j. Severity level IV violations without performance deficiencies do not receive enforcement discretion. These violations are not to be described as findings and are not assigned a color. In accordance with section 3.10 in Part 1 of the Enforcement Manual, SLIV violations without an associated performance deficiency need to be documented in the following manner in RPS-Inspections:

• For NRC-identified or self-revealed violations, select Traditional Enforcement Violation, using the, I plan to document, tool.

• For licensee-identified violations, select Licensee Identified NCV using the, I plan to document, tool.

k. An Enforcement Action (EA) n umber, which can be assigned by the regional enforcement coordinator, must be assigned for enforcement actions (e.g., escalated enforcement, discretion associated with an Enforcement Guidance Memorandum,

confirmatory action letters, licensee denials, chilling effect letter s, etc.), as specified in the Enforcement Manual. Enter an EA number in the EA number field when documenting a discretion, and the appropriate, I plan to document, field. The EA number will be included in the cover letter.

l. The results of initial operator licensing examinations and retake examinations are transmitted to the licensee via a letter generated outside of RPS -Inspections in accordance with NUREG-1021. If a finding or violation is identified during an initial operator licensing examination or retake examination, document the issue in the examination report and, if applicable, in the PIM. The results of operator licensing requalification inspections are documented in the applicable quarterly integrated report.

Issue Date: 05/10/24 13 0306

m. Security-Related Inspections.

1. Security inspections (such as Physical Security, Cyber, and Material Control and Accountability) can be documented within RPS -Inspection s if they do not contain any information at the Safeguards (or higher ) classification.

In some cases, the regions or headquarters may elect not to generate a security-related inspection report in RPS -Inspections. In those cases, the samples performed, and results identified, must still be entered in RPS-Inspection s to ensure the proper tracking and accounting of the inspection. In addition, established office policies, procedures, and practices should be followed to ensure all samples and results are correctly reflected in RPS-Inspections.

2. If a report contains Safeguards information, it needs to be generated in an approved SGI computer system. In these cases, the samples performed, and results identified must still be entered into RPS-Inspections prior to issuing the report to ensure the proper tracking and accounting of the inspection.However, the information entered must not contain any Safeguards information. Limited information associated with the Safeguards finding/violation shall be entered into RPS-Inspections. [C 2] Specifically, the following information should be filled out in the following manner to allow for adequate tracking and trending

Title The following should be entered:

Safeguards Finding (SLES NS#XXX)

Dockets Select the correct dockets Procedure Select the inspection procedure finding/violation associated with, Cornerstone Select Security Identification Select the appropriate identification Introduction The following should be entered:

Safeguards Finding (SLES NS#XXX)

Cross-Cutting Select the appropriate cross-cutting aspect assigned in the report.

Aspect

3. For security inspection reports with Official Use Only ( OUO) information, the regions or headquarters will issue two documents: a cover letter which can be released to the public and a non-public version of the cover letter with the inspection report containing the OUO information attached. Each document will have a distinct ADAMS accession number.

4. Only after a thorough SUNSI review of the inspection report:

• For a report containing no OUO or Safeguards information, the public ly available cover letter and report should be issued and posted to the NRC public webpage.

• For a report containing OUO information, a standalone publicly available cover letter should be created. The ADAMS accession number of this cover letter gets entered in the Accession No. (ML): field in the RPS-Inspections/Inspection Reports tab and the non-public security report ML number is entered into the Referenced ML No.: field.

Issue Date: 05/10/24 14 0306

n. Supplemental Inspection Results

1. If the inspectors conclude the conditions to close the p erformance indicator were not met, create a separate, parallel PI i nspection finding as applicable in accordance with IMC 0305. When entering this finding in RPS-Inspections, select the appropriate IP 9500x as the procedure being used and input enough detail in the description field to note the associated PI. R emember to document in the introduction and description fields that these findings are parallel PI inspection findings. The color of this finding will be assigned the same color as the PI. Do not select a cross-cutting aspect for this finding.

2. Additional inspection findings identified during the supplemental inspection beyond the scope of the original finding(s) are entered in RPS -Inspections as new entries and are assigned the appropriate significance via the SDP.

o. When a Notice of Enforcement Discretion (NOED) is granted, a URI shall be opened in accordance with the NRC Enforcement Manual, Appendix F, Notices of Enforcement Discretion, to track the required follow-up activities to determine if there was a performance deficiency or if additional information is required to determine if the NOED issue was more than minor. The follow-up activities shall be conducted in accordance with IP 71153 and documented in accordance with IMC 0611.

p. Handling Findings/Violations that Do Not I nitially Screen to Green

1. As updates are needed to the initial issue, use the document update feature to document the issue further (See attachment 4 for further details). However, do not change the Event Date, or PIM Date, as these dates carry through to final determination. For example, findings or violations that originated from an AV will have the same PIM Date, as the AV.

2. As the status of an issue changes (such as issuance of final SDP letters and supplemental inspection reports), the PIM notes section for the item should be used to capture each update of the PIM entry. See table in s ection 06.05.p.3 for details concerning PIM notes section entries. PIM notes entries get carried over each time the status of the issue changes and an update to the PIM notes section is to be made. This ensures traceability of an issue from discovery to final resolution and allows for easier tracking by the public. See the non-public RPS -Inspections Desktop Guide for instructions regarding how to make an update.

3. The updates to the public webpage occur in accordance with the schedule described in section 06.11, or as soon as possible if there is a known change in licensee performance as a result of NRC action. To update the webpage in a timely manner, regional staff must notify DRO (Reactor Assessment Branch (IRAB)) staff any time they reach a final determination or obtain clarifying information affecting a plant and its placement in the ROP Action Matrix Summary.

Below is a sample of the typical items included in a greater -than-G reen finding that has been processed through the significance determination process and the supplemental inspection has been completed. The example demonstrates the process necessary to ensure that the finding information on the public webpage provides traceability of an issue from discovery to final resolution.

Issue Date: 05/10/24 15 0306 Guidance What Shows Up in the PIM Introduction of the initial issue An apparent violation was identified..

(no PIM notes needed)

The inspector will need to First Update: The finding was determined to be of low to update the PIM notes in the moderate safety significance (White) in the final determination Tracking Data tab when the letter 05000XXX/20XXXXX, dated XXXX (MLXXXXXX),

Final color is determined: because. (explain why it is White)

When an NOV is closed in a Second Update: The NRC completed a supplemental inspection, supplemental report, the and it is documented in inspection report 05000XXX/20XXXXX, inspector will need to add a dated XXXX (MLXXXXXAXXX). The supplemental inspection second update to the PIM assessed the adequacy of the licensee's evaluation, extent of notes within the Tracking condition/cause review and associated corrective actions. The Data tab (ensuring the inspectors determined that the licensee performed an adequate introduction and any/all evaluation of the specific performance issue and that previous notes remain visible ) comprehensive corrective actions were completed to address each of the specific causes. This finding is closed.

06.06 Finalizing and Closing Inspection Reports

a. To finalize an inspection report, ensure all inspection and results to be included in the report have been taken from In Progress, to Approved. The Branch Chief signing out the report will then take the report from Draft to Final. This action needs to be completed for all inspection reports, including those created for Operator Licensing Examinations and those reports that are generated outside of RPS -Inspections.

b. The inspection report generator feature will automatically assign tracking numbers for findings, violations, and URIs documented in the inspection report when the report is in a Final status. For details on the numbering protocol, see a ttachment 2.

c. In accordance with IMC 0305, ensure the cover letter states whether or not a follow -up inspection will be required for any traditional enforcement items documented in the report and the basis for that decision.

d. When documenting ISFSI activities at Part 50 sites that have not yet transitioned to ISFSI storage only, ensure the Part 72 report is referenced in the subject line to any Part 50 report that documents ISFSI inspection activities.

e. To close an inspection report in RPS-Inspections, the report status needs to be changed from Open, to Closed, by users with Inspection Report User or Inspection Super User access.

f. The following report information should be entered into the RPS-Inspections/Inspection Reports tab in a timely manner (typically within 14 days after issuance of the report) for each inspection report issued. If the report has Assessment Letter Info, the information should be input as soon as possible to ensure the report is properly incorporated into the public website.

Issue Date: 05/10/24 16 0306 Report Information:

Report Status Required to be changed to closed during closeout.

Title Field auto-populated by RPS-Inspections upon creation of report.

Can be edited if needed to align with report naming convention in accordance with established regional practices.

IMI Code Field not used. (Legacy RPS field)

Inspection Completion For the quarterly integrated report this is the last day of the quarter; Date and for standalone reports its the date of the exit (typically the last onsite date). For final SDP and traditional enforcement letters, its the date the results are communicated to the licensee. This date is auto-populated by the system and must be verified to ensure it aligns with the activities that actually occurred during the inspection.

Due Date Field auto-populated by RPS-Inspections.

Sent Date This is the date in which the report is signed out for approval and issuance.

Closeout Date This is the date the report status is changed to closed in RPS-Inspections.

Responsible Field auto-populated by RPS-Inspections. Should align with Organization organization responsible for signing out report.

Inspection Type Field auto-populated by RPS-Inspections.

Lead Inspector Field auto-populated by RPS-Inspections. Should align with lead inspector listed in inspection report.

Accession Number and Public version of the report/cover letter into the Accession Number Reference ML field.

Non-public version of the report into the Reference Number field (and do not check the non-public box).

For corrected or revised reports, see further guidance in 06.07 below.

Has Assessment Letter Inspection report has action matrix conclusions present in the cover Info letter, and must be pulled into list of assessment letters website Non-Public Inspection report designated as Non-Public and no public version of cover letter Response Required The inspection report includes Findings, NOVs, etc., where a response is required by the licensee, check the Response Required check box.

Are contractors going to If contractors were used, check the box.

be used

Issue Date: 05/10/24 17 0306 EPID Information:

Title Field auto-populated by RPS-Inspections upon creation of report.

Can be edited if needed to align with report naming convention in accordance with established regional practices.

Contact Field auto-populated by RPS-Inspections.

(Should align with the lead inspector listed in the inspection report.)

Supervisor Field auto-populated by RPS-Inspections.

(Should align with the BC of the responsible organization for the report.)

ML Number Field not required.

Start Date Field auto-populated by RPS-Inspections.

End Date The date should be entered when the inspection report is closed. It is recommended that this date be between 45 days and 6-months after the date the report is closed. This will allow for the EPID to be used in case a licensee appeals the results of a report, or if corrections are identified, and a report needs to be reissued.

Status Field auto-populated by RPS-Inspections.

Created By Field auto-populated by RPS-Inspections.

Last Update By Field auto-populated by RPS-Inspections.

Comments Field not required.

g. Both the headquarters and regional staff are responsible for entering i nspection reports into ADAMS in accordance with the ADAMS template.

06.07 Modifying Issued Inspection Report (Corrections, Revisions or Appeals)

a. If a n administrative error is found in an issued report, and needs to be corrected, a n amended (or revised) report can be issued. 1 Refer to IMC 0611 for details of what needs to be included in the reissued report. (The word document in ADAMS should be the version used to make the corrections and the report is re-finalized to determine if the numbering of findings in the amended (revised) report need to be adjusted.) In addition, perform the following:

1. The original report should be reopened in RPS-Inspections, to allow for changes to be made, if needed. This includes placing the report in a draft status and placing what needs to be corrected in an In-Progress status. Make corrections and regenerate the report. Within 14 days of the corrected report being issued, the status of the report should be returned to a closed status and the ADAMS ML number for the amended (reissued) report should be entered into the Accession Number field in the Inspection Reports tab. The ADAMS ML number for the original report should be entered in the Reference Number field.

1 The term ERRATA was used when the NRC sent out corrections to the report by providing a list of changes or a corrected page but later was used to describe a completely reissued report that included the correction(s). While inspectors still use the term ERRATA, the agency is now using the term reissued, or amended.

Issue Date: 05/10/24 18 0306

2. Any of the information associated with the original report entry in RPS -Inspections, such as exit date, inspection dates, responsible org, etc. should not be changed or edited.

b. Denials, appeals, and other licensee responses to findings and violations are addressed by utilizing the existing closed report which identified the issue in question. In addition, perform the following actions:

1. Verify or reopen the EPID associated with the affected inspection report.

2. Maintain the report closed; if needed, reopen the report to add any additional staff and activities, then reclose the report.

3. Add the appropriate activity codes to review the appeal by the licensee : APLF (use for baseline), EPLF (use for EP), or SPLF (use for Security) to the scheduled item.

All time spent conducting the review should be charged to the associated CAC for the activity code selected (except for supervisors).

4. If this review does not change the results or conclusion of the original report, ensure the report and all activities remain in the closed/approved status after issuing a letter to the licensee describing the resolution. Add the ML number for this letter to the Reference Number in the Inspection Reports tab. In this case the inspection report will not be reissued.

5. If this review changes the results or conclusion of the original report, open the report and make the appropriate changes, and reflect those changes in RPS-Inspections.

Refer to IMC 0611 for details of what needs to be included in the reissued report.

Ensure that the cover letter provides a reference to the licensees appeal letter, and an explanation regarding why the original report is being changed. When complete, place the inspection in an approved status, return the report to a final status, and reclose the report and the EPID after issuing the revised report.

6. Any of the information associated with the original report entry in RPS-Inspections, such as exit date, inspection dates, responsible org, etc. should not be changed or edited.

06.08 Inspection Procedure Completion Status

To maintain appropriate internal controls and lock down procedure completion and notes status, the Branch Chief responsible for the site n eeds to certify (approve) ROP Completion at the end of each calendar year on the All Procedures, site page.

a. The completion status of IPs (both parent IP and sub-procedure) should be updated as soon as practical after completion, but no later than February 15 of each calendar year to support ROP completion certification.

b. To preserve the integrity of reports generated after the end of the year, changes should not be made to the completion status of any IP after 90 days following the end of an inspection cycle - or March 31st of the following year. Requests for changes should be made to the DRO/IRIB Branch Chief via email or memorandum.

Issue Date: 05/10/24 19 0306

c. All baseline IPs that recommend reviewing samples on a quarterly or semiannual frequency should not have a completion status until either:

1. the cumulative minimum sample size for the samples in the year has been reached for the procedure, or

2. it is declared complete per one of the completion status codes.

3. its been determined that it will be incomplete per s ection 06.08f.6.

d. All baseline IPs that have an annual frequency should not have a completion status until:

1. the cumulative minimum sample size has been reached for the IP, or

2. It is declared complete per one of the completion status codes.

3. it has been determined that it will be incomplete per s ection 06.08f.6.

e. For all baseline IPs that have a biennial, triennial, or quadrennial frequency:

1. The status of these IPs is N/A if they are not required to be completed during the current inspection cycle and will be completed in a future year within the biennial,

triennial, or quadrennial cycle.

2. The status is Complete - in previous years if the IP was completed a previous year within the biennial, triennial, or quadrennial period.

3. The completion status should be Incomplete if the IP is required to be completed during the current calendar year, until either: (1) the required minimum sample size is reached for the IPs; or (2) it is declared Complete per a completion status code.

f. The specific IP completion status codes available in RPS -Inspection s are listed below.

See attachment 3, Inspection Completion Status Illustrative Examples, :

1. Complete (C). When the number of inspection activities (samples) within the range of sample values specified in each IP have been completed, thus meeting the objectives of the IP. See IMC 2515 for additional details.

2. Complete - by reference in accordance with IMC 0306 (C1). A specific comment must accompany this selection explaining the reason. (See the non-public RPS-Inspections Desktop Guide for instructions on entering comments.) Two ways for this status to be valid are:

• All requirements of the IP are met by work done in some other IP(s) or at related units on the same site. The comment must reference the other inspection(s) as the basis for demonstrating that all IP requirements are completed (See IMC 2515 for additional information). For planning and reporting purposes, the IP is considered completed.

• For IPs that have the sample size determined by the performance of the plant over previous years, the minimum sample may vary to less or more than the required sample. Since RPS-Inspections can only assign one sample size for the

Issue Date: 05/10/24 20 0306 same IP, plants with a required sample size less than the assigned sample size would use this code.

3. Complete - minimum sample not available in accordance with IMC 0306 (C2). The minimum sample size was not available due to an insufficient number of samples with appropriate risk significance being available for inspection. A specific comment must accompany this selection explaining the reason.

4. Complete - opportunity to apply full procedure not available in accordance with IMC 0306 (C3). The minimum sample size was not able to be completed due to the sample requirement (sample type) not being available at the time of the inspection.

An example of this would be if a required sample was not applicable to a site or the licensee did not conduct a required activity. A specific comment must accompany this selection explaining the reason.

5. Complete - in previous year(s) (C4). Only biennial, triennial, or quadrennial IPs for which all samples have been inspected in the previous year(s) within the same biennial, triennial, or quadrennial period can have this status.

6. Incomplete (IC). All required samples in the IP have not met the requirements as discussed in IMC 2515.

7. Not Applicable - completion not required during this inspection cycle (N/A). This indicates that completion of a biennial, triennial, or quadrennial IP was not performed in a given year and is scheduled to be completed in a future year within the same biennial, triennial, or quadrennial cycle. This status does not need to be used for IPs that are not required or completed in a given IPC for other reasons.

06.09 Non-Result Items Tracked in RPS -Inspections

a. The following non-result items shall be tracked in RPS -Inspections:

• Confirmatory Action Letters (CAL),

• Corrective Action to Prevent Recurrence (CAPR),

• License Renewal Commitment (not confirmed/complete during IP 71003 inspection),

• Non-Conformance,

• Order,

• Security Event Report (SER),

• Licensee Event Reports (LER), and

• Written Event Report (WER) (for use by fuel cycle facilities only).

b. For CALs, all required actions should not be entered in RPS-Inspection s. A single item to track the CAL should be entered. The status of the actions associated with the CAL can be tracked by using the Description text field.

c. For Corrective Action to Prevent Recurrence:

1. Title each tracking item [site] [s upplemental IP number] CAPR [l icensee tracking number] ([short title]). Example: Fitzpatrick 95001 CAPR 04397491-71 (Read &

Sign Training).

2. Cut and paste the appropriate section of the report into the RPS Description field.

Issue Date: 05/10/24 21 0306

3. Under the Tracking Data enter the planned licensee completion date for the planned CAPR in the Projected Closeout Date field.

4. After follow-up inspection of completed CAPRs, provide details on how closed by inspector, and select closed under Tracking Data.Example: Review completed in PI&R Team Inspection Report 2023-010. Tracking of CAPR Closed.

d. I nformation related to Safeguards events should contain no greater detail than its associated initial event notification report. Do not enter Safeguards Information into RPS-Inspections.

e. The Regions and NSIR are responsible for adding Confirmatory Action Letters, Licensee Renewal Commitments, Corrective Action to Prevent Recurrence, and Non-Conformance Orders.

f. LERs are populated automatically into RPS-Inspections from ADAMS, using the non-public ADAMS template NRR -122, which can be found under ML18033B188.

Following an automatic entry of an LER or a manual entry of an SER into RPS-Inspections, the regions are responsible for:

1. Ensuring all vital data has been translated correctly from the subject LER, including title, docket, event date, submitted date, LER number, revision number, description (optional), and ADAMS hyperlink. When the LER/SER applies to multiple dockets, ensure the LER/SER is only assigned to the lowest docket number. For LERs and SERs uploaded from ADAMS, the above fields will be in a read only status. If any data has been incorrectly imported from ADAMS to RPS -Inspections, contact RPSSupport.Resource@nrc.gov and ADAMSIM@nrc.gov for correc tions.

2. Populating the projected closeout date, responsible organization (projects branch associated with the subject plant), closeout organization (branch responsible for performing the closeout inspection) and contact person ( Branch Chief of respective projects branch).

3. If it appears that an issued LER or SER is not in RPS-Inspections, check the All Items screen first, prior to contacting RPSSupport or ADAMSIM for assistance.

To properly track a LER and SER the following dates should be used:

Closure Date For LERs/SERs documented and closed in a quarterly integrated report it is the last day of the quarter.

For LERs/SERs documented and closed in a standalone report it is the inspection exit date (typically the last day of onsite inspection).

Event Date The date the actual Event occurred. Box 5 (Event Date) on an LER.

This is automatically populated when loaded into ADAMS.

Issue Date The date the LER or SER was signed/approved. Box 7 (Report Date) on an LER. This is automatically populated when placed in ADAMS.

Issue Date: 05/10/24 22 0306 06.10 Mid-Year Planning Letters, Assessment Letters, and Inspection Schedule Plans

a. The regions will issue mid-year planning and annual assessment letters with the 24-month inspection schedule in accordance with IMC 0305 after the completion of the second and fourth quarter, respectively. These letters are issued and placed on the public webpage in accordance with the table in s ection 06.11.

Assessment follow-up letters are typically issued after the completion of the first and third calendar quarters only for those plants that crossed performance thresholds, in accordance with IMC 0305.

b. Assessment follow-up letters typically do not include updated inspection schedule plans; however, they may note any inspection schedule plan changes associated with forthcoming supplemental inspections. These letters are placed on the public webpage after they are dated and sent to licensees in accordance with the table in section 06.11.

c. Assessment follow -up letters can also be issued on an as -needed basis between quarterly reviews. These letters are placed on the public webpage after they are dated and sent to licensees in accordance with the table in s ection 06.11.

d. T he regions are responsible for:

1. Entering Mid-Cycle Planning letters and all Assessment letters into ADAMS in accordance with the established ADAMS template, and

2. Entering the ADAMS accession number for mid-year planning and all assessment letters into the RPS-Inspections/Inspection Reports tab.

e. To support posting these documents to the NRCs public Operating Reactors/Reactor Oversight Process webpage in a timely manner, assessment letters and inspection schedule plan letters must be properly entered and declared in ADAMS and should be placed in the appropriate site subfolder within the Power Reactor Correspondence folder of ADAMS.

06.11 ROP Web Posting Process, Content and Schedule

a. The ROP webpage displays the summary of inspection findings that appear in the PIM.

The ROP webpage includes all issues designated as VIO, FIN, AV, NRC -identified, and self-revealing NCV. For these issues to be displayed, the PIM checkbox must be checked, and the inspection report in which they are attached must be closed.

b. Findings (classified as OUO-Security Related and higher) and PIs in the Security cornerstone will not be made public. However, any historical data entered before the third quarter 2004 will remain available on the webpage. NRC employees may gain access to the current Security PIs and inspection findings through ROP Digital City (NRC non-public webpage).

Issue Date: 05/10/24 23 0306

c. Web Posting:

The tables below provide the types of inspection reports that are posted and due dates for data submissions and updates to the ROP w ebpages. When a due date falls upon a weekend or F ederal holiday, the due date is the next working day.

Description Due Date Displayed on the Public Website Assessment Report Final Determination Report 90 days Yes Assessment Follow-up Report Integrated 45 days Materials Special (IMC 2800/2810) 30 days No Operator Licensing 45 days Materials Routine (IMC 2800/2810) 30 days Team or 45 Days Report Supplemental Inspection 45 days Yes Reactive Inspection (SIT)

Reactive Inspection (AIT, IIT) 30 days

Information Due date (*)

Changes to the Action Matrix Summary (AMS) (along with 14 days after information is findings, inspection reports, and assessment letters) publicly available posted to external webpage (outside of quarterly input)

Licensees submit Performance Indicators 21 days HQ archives previous quarter data in historical 21 days performance webpages IRAB posts updated Performance Indicators to internal 24 days (or 3 business webpage for review days after licensee submittal date)

IRAB posts Performance Indicators to internal and 35 days external webpages Regions send assessment follow-up letters to licensees (if applicable) and email them to 49 days ROPassessment.Resource@nrc.gov IRAB reposts information to the internal and external ROP 50 days webpages to capture updated PIM and IR IRAB updates assessment letter webpage and AMS, if 51 days applicable. (AMS quarters 1 and 3)

Regions send mid-year planning letters or annual assessment letters to licensees and email them to 63 days ROPassessment.Resource@nrc.gov

Issue Date: 05/10/24 24 0306 IRAB updates assessment letter, AMS, and Cross-Cutting 65 days Issue (CCI) summary webpages at the end of mid-year (AMS quarters 2 and 4) and annual assessment periods Final Determination or Escalated Enforcement Report 90 days from initial report Corrections or change in the ROP webpages or SDP of As needed any findings (greater than Green)

IRAB posts any available PIM entries, and inspection Monthly reports, to internal and external webpages

(*) Days following the end of the calendar quarter unless noted otherwise

d. Performance Indicators.

1. Licensees submit quarterly PI data, in accordance with NEI 99-02, Regulatory Assessment Performance Indicator Guideline.

2. PI data, indicator values, and associated graphs are posted to the NRCs internal ROP webpage in accordance with the tables above. The regions then review the PIs and determine the Action Matrix designations, as well as identify any errors prior to public release.

3. The NRC posts the PIs, along with the latest inspection findings and Action Matrix designations, to the agencys internal and external ROP w ebpages in accordance with the table above.

4. Licensees are expected to submit changes to PI data as soon as practical, but no later than the end of the quarter in which an error is discovered.

e. Cross-Cutting Issues (CCIs).

CCIs are identified during the mid-year and annual assessment performance review and documented in accordance with IMC 0305. IRAB will update the NRC public ROP Cross-Cutting Issues Summary webpage after an assessment letter documenting opening or closure of a CCI is issued. Refer to non-public report IR-12, Cross Cutting Aspect, for evaluating cross -cutting aspects (CCAs).

f. Assessment-Related Webpages.

1. Action Matrix Webpage:

(a) IRAB updates the NRCs public ROP Action Matrix Summary and Current Regulatory Oversight webpage as needed, in accordance with the table above.

(b) To support timely changes to this webpage, the regional offices shall place ROPassessment.Resource@nrc.gov on distribution for the following correspondence:

(1) Supplemental inspection reports; (2) Final SDP letters, and (3) All assessment and assessment follow-up letters.

2. Action Matrix Deviations Webpage:

Issue Date: 05/10/24 25 0306 (a) After a licensee has been notified of an Action Matrix deviation, IRAB will update the NRCs public ROP Action Matrix Deviations webpage to notify the public of the deviation and the basis for the deviation.

(b) The regional office shall place ROPassessment.Resource@nrc.gov on distribution of the assessment follow-up letter describing the deviation.

The email should also contain a description of the deviation as it should appear on the public webpage. IR AB may modify the text as necessary before posting it to the public webpage. The description should include:

(1) Affected reactor units; (2) Date the EDO approved the deviation; (3) Description of the deviation; (4) Description of when the deviation is expected to be closed; and (5) Description of changes to ROP guidance, if applicable.

06.12 Inspection Program and Auto Report Generator Management

a. The Inspection Program Management (IPM) tab in RPS-Inspections is used to maintain the history of inspection documentation. When a change notice document has been issued, DRO is responsible for entering the Change Notice information into IPM.

b. Based on Change Notice information, D RO will create, revise, or delete from the inspection program an inspection manual chapter (IMC), inspection procedure (IP),

temporary instruction (TI), and/or operating experience smart sample (OpESS). In doing so, DRO will update the appropriate fields in IPM, such as document titles, sample sizes and inspection hours.

c. The Auto Report Generator tab is used by DRO to maintain a current version of the inspection report and the cover letter templates, which ensures that changes made in IMC 0611 are captured in RPS-Inspections. DRO is also responsible for ensuring scope and sample ghost text is added/updated in the RPS-Inspections Auto Report Generator tab as new IPs and TI s are issued, or as requirements and samples are created, revised or deleted.

06.13 Administration of RPS-Inspections

The RPS-Inspections Admin tab is used to add user roles to RPS -Inspections, and for adding operator licensing qualifications as applicable. User roles should be assigned based on guidance in the non-public RPS-Inspections Desktop Guide. Each office that uses RPS-Inspection s has dedicated staff that can access this tab to make changes or updates as needed.

06.14 Tools for Scheduling and Performance Monitoring

Pre-established reports, located in the R RPS Reports tab, are used for planning, scheduling of examinations and inspections, and tracking of results. The RRPS Reports tab includes, but is not limited to,reports that contain information associated with sample completion and hours expended on inspection activities and procedures. Other reports include information on inspection manual change notices and documentation history, as well as operator licensing examiner schedules, availability, and training commitm ents.

Issue Date: 05/10/24 26 0306 06.15 Communicating System Problems/Potential Enhancements

a. All issues and suggestions for enhancements to RPS -Inspections should be reported to RPSSupport.Resource@nrc.gov.

b. System changes and suggested enhancements are reviewed and prioritized by the RPS-Inspections CCB on a monthly basis. Final approval is provided by the RPS Executive CCB, which is controlled by OCIO, and scheduled for implementation.

0306-07 REFERENCES

IMC 0040, Preparation, Revisi on, Issuance, and Ongoing Oversight of NRC Inspection Manual Documents

IMC 0305, Operating Reactor Assessment Program

IMC 0307, Appendix B, ROP Baseline Inspection Procedure Reviews

IMC 0310, Aspects Within Cross -Cutting Areas

IMC 0611, Power Reactor Inspection Reports

IMC 0612, Issue Screening

IMC 2201, Security Inspection Program for Commercial Nuclear Power Reactors

IMC 2515, Light Water Reactor Inspection Program

10 CFR Part 9, Public Records

Labor Reporting Policy & Guidance, dated April 8, 2019 (n on-public, ML23223A124)

NEI 99-02, Regulatory Assessment Performance Indicator Guideline

NRC Enforcement Manual (ML23360A760)

NRC Yellow Announcement (YA) - 20-0060, Time Charging for Enforcement-Related Orders, Including Confirmatory Orders Fee-Billable Cost Activity Code, dated August 18, 2020 (non-public, ML20219A655)

END

Issue Date: 05/10/24 27 0306 Attachment 1: Inspection Report Numbering

1. Every inspection report, preliminary or final significance determination letter, traditional enforcement (TE) letter, Notice of Violation (NOV) letter, annual assessment letter, mid-year planning letter, or assessment follow-up letter should be assigned a unique report number through the RPS-Inspections.

The numbering format for an inspection report is: 0# 000###/YYYY***, where

0#000### is the docket number YYYY is the year, and

• • • is the sequential report or letter number.

2. The year in the report number should correspond to the calendar year in which the first onsite direct inspection activities or the onsite administration of the operator licensing examination.

3. The numbering convention used for most reports prior to 2018 is listed below. Starting in calendar year 2018 ROP inspection reports and assessment letters were assigned the following numbers:

Reports 2015-2017 Beginning in 2018 (see Note 3 below)

First Quarter Integrated Report 001 001 Second Quarter Integrated Report 002 002 Third Quarter Integrated Report 003 003 Fourth Quarter Integrated Report 004 004 Mid-Year Planning Letter 005 005 Annual Assessment Letter 006 006 Assessment Follow-Up 007-009 Standalone IMC 2515 Inspections 010-039 (not Integrated) 2515 App B Supplemental Inspections 040-049 2515 App C Reactive inspections 050-059 (SIT/AIT/IIT)

Choice Letters, Preliminary or Final determination letters or other 090-099 documentation of enforcement actions Headquarters (except for Security) 201-299 201-299 Operator Licensing Examination Reports 301-399 301-399 Security Mid-Year Planning Letter 401 Now included in 005 report Security Annual Assessment Letter 402 Now included in 006 report Security Assessment Follow-Up Part of 007-009

Issue Date: 05/10/24 Att1-1 0306 Reports 2015-2017 Beginning in 2018 (see Note 3 below)

IMC 2201 Inspections 401-449 Security (Regional) 401-419 Security (Headquarters) 420-439 2201 App B Supplemental Inspections, 440-449 2201 App C reactive inspections (SIT/AIT/IIT), Security Final determination letters or other documentation of enforcement actions

Emergency Preparedness Mid-Year Planning Now included in 005 Letter report

Emergency Preparedness Annual Inspection Now included in 006 Report and other related activities 501 report documented in the Integrated Report

Emergency Preparedness Assessment Part of 007-009 Follow-Up

Emergency Preparedness Inspection Reports 501-549

Emergency Preparedness (Regional) 501-519 Emergency Preparedness (Headquarters) 502-599 520-539 Emergency Preparedness Supplemental 540-549 Inspection

Note 3: Maintained in this IMC for historical purposes.

The 71114 procedures are included in the quarterly integrated inspection reports. The 500 series of reports is used for standalone EP inspections, when needed. Report numbers 501 and 502 are no longer being used as separate assessment letters, and do not need to be referenced in the subject line of the 005 and 006 assessment letters.

Issue Date: 05/10/24 Att1-2 0306 Attachment 2: Inspection Item Numbering

1. An item number is required for each item identified in the inspection report, including each of the six type codes: apparent violation (AV), deviations (DEV), finding (FIN), non-cited violation (NCV), notice of violation (NOV), unresolved item (URI), and traditional enforcement without an associate finding (TE).

Licensee-Identified NCVs (LIVs), Observations, and Assessments do not get items numbers. If a URI becomes an apparent violation, finding, violation, or non-cited violation it should first be closed using the update feature and then a new finding entry should be made by using I plan to document, which will assign it a new tracking number.

2. For all licensed facilities, the numbering format for an inspection item is:

<type> 0#000###/YYYY***-$$

Where

<type> is the finding type code (AV, FIN, NCV, NOV, TE, URI), #### is the docket number, YYYY is the inspection year, *** is the sequential report number, and $$ is the item number.

Examples of inspection report item numbers are:

URI 05000346/2018 004-01, FIN 05000285/2018 003-02, NOV 05000443/2018 301-03.

3. An item number is unique for each distinct inspection finding.

a. The first item identified in the inspection report has 01 as the item number ($$), and each subsequent item is numbered in sequential order, regardless of type.

b. The item number is assigned in sequential order at the site level, not at the unit level.

c. If an item applies to multiple units at the same site, the item number will be the same for all applicable units. In this case, the item number will be the next sequential number of highest item number at the site level. The docket number and the associated inspection report number distinguish the unit to which the item applies.

Issue Date: 05/10/24 Att2-1 0306 The following examples illustrate proper item numbering for single and dual -unit sites:

Item Numbering for Single-Unit Site Item Docket Report Item # Remarks 1st NOV 05000346 2018002 01 1st URI 05000346 2018002 02 2nd NOV 05000346 2018002 03 1st FIN 05000346 2018002 04

Item Numbering for Dual-Unit Site 1st URI 05000295 2018002 01 Unit 1 1st NOV 05000304 2018002 02 Unit 2

1st FIN 05000295 2018002 03 both units 05000304 2018002 03 2nd FIN 05000295 2018002 04 Unit 1

2nd URI 05000295 2018002 05 both units 05000304 2018002 05

Issue Date: 05/10/24 Att2-2 0306 Attachment 3: Inspection Completion Status Illustrative Examples

Example 1

A baseline IP (such as IP 71111.12) with a quarterly frequency requires reviewing two samples quarterly, for a total of eight samples annually. In the first quarter, the inspectors reviewed only one sample.

The Branch Chief (or designee) did not change the completion status. During the second quarter, the inspectors reviewed two samples, per the IP, and one additional sample that was missed in the first quarter inspection.

The Branch Chief (or designee) did not change the completion status. When the cumulative completed sample size was reached, the Branch Chief (or designee) should change the completion status to Complete.

Example 2

The resident inspectors performed a baseline IP that required reviewing seven samples. Only five samples were available during the inspection cycle, based on the risk significance of the available samples.

At the end of the inspection cycle, or when it was determined that additional samples will not be available during the inspection cycle, the Branch Chief (or designee) should enter, Complete -

minimum sample not available. A comment should also be added explaining the reason that the minimum sample size was not available for inspection.

Example 3

A baseline IP that is to be completed as conditions require was not performed during the annual inspection cycle. Since there were no opportunities to perform the inspection by the end of the annual cycle.

The Branch Chief (or designee) should enter Complete - opportunity to apply full procedure not available. A comment should be added explaining the reason the opportunity to apply the IP was not available. (An example of this is IP 71114.04. If the licensee did not make any changes to the e-plan during the inspection cycle, this would be the appropriate completion status code to use.)

Example 4

A triennial inspection was completed in the second year of the triennial period. The Branch Chief (or designee) should enter a completion status of N/A for the first year, Complete for the second year, and Complete - in previous years for the third year.

Example 5

A Temporary Instruction (TI) was completed at a site. The Branch Chief (or designee) should enter a completion status Complete.

Issue Date: 05/10/24 Att3-1 0306 Attachment 4: Management of Complex Inspection Results [C4]

Most inspection results are opened and closed within the same inspection report. However, more complex issues require additional review in subsequent inspections prior to final disposition. These more complex issues are often identified first as an URI [ See IMC 0612 and IMC 0611 for more detail]. Then, assuming a performance deficiency or potential violation is identified, the URI is closed to a new AV. The AV is then updated until final disposition, often in the form of a NOV. This attachment will provide clarifying guidance for documenting these more complex inputs into the RPS by providing a detailed example of how they are to be processed.

Typical Inspection Result Documentation Sequence for complex issues:

Step 1: Document the initial issue of concern - The initial issue of concern is documented using the inspection procedure (IP) used to identify the issue. Assuming the issue requires additional review to determine if a violation occurred, the issue is documented as a URI.

Otherwise, proceed to step 3.

Step 2: Closing the URI - Assuming the inspectors have determined that the issue is indeed a potential violation, the URI is closed out in RPS. To close out the URI, the URI must be selected using the Document Update function within the follow -up inspection report.

The only options for follow -up of URIs is discussion (if additional inspection is still needed) or closure. The URI is not to be converted into an AV.

Step 3: Opening the AV - After closing the URI, if applicable, a new AV is opened using the

+C reate New Result to track the issue. The AV is linked to the URI through the Related Items tab for tracking purposes. The AV is typically documented in a -090 series report (see attachment 1). The nature of the AV will determine which of the three AV options should be used to generate the AV:

a. Reactor Oversight Process (ROP) only [t able 2 of IMC 0611])

b. Traditional Enforcement (TE) only [t able 3 of IMC 0611], and

c. TE and ROP [t able 4 of IMC 0611].

The IP associated with the AV should be the same as the URI.

Step 4: Converting the AV to an NOV - Once the evaluation of the AV is complete and a final violation is determined to have occurred, the AV is converted to an NOV. In the follow -up inspection report (which should be a -090 series), the AV must be selected from the open items list using the Document Update function within the subsequent inspection report. If the NOV is licensee identified and a Green significance or a Severity Level IV, the violation is to be documented as a Licensee-Identified NCV (LIV) [table 8 of IMC 0611]. Otherwise, the applicable NOV option should be selected. The PIM notes are to be updated to capture the justification for the conversion of the AV to an NOV [ See section 06.05.p.3.].

Step 5: Follow-up and Closure of NOV - Escalated enforcement issues are typically followed -up by a supplemental inspection (using one of the IP 9500x series IPs). To document the closure of the NOV, the NOV must be selected using the Document Update function in the follow-up report and converted to a Close Open Item. The IP for the closure will be the applicable 9500x series IP, and the PIM notes for the NOV require an update to discuss how the NOV was closed.

Issue Date: 05/10/24 Att4-1 0306 Attachment 5: Table of Abbreviations and Acronyms

ADAMS Agencywide Documents Access and Management System AMS Action Matrix Summary APLF licensee appeal-final enforcement/cross-cutting determination ASM assessment AV Apparent violation BI baseline inspection CAC Cost Activity Code CAL Confirmatory Action Letters CCB Configuration Control Board CCI Cross-Cutting Issue COM communications -Part 50 COR Contracting officers representative DEV deviation DIE Direct Inspection Effort DRO Division of Reactor Oversight EA Enforcement Action EDO Executive Director for Operations EOC End-of-Cycle EP emergency preparedness baseline inspection EPID Enterprise Project Identifier EPLF Emergency Preparedness Appeal Follow-up ESM emergency preparedness assessment FIN finding FRII fuel facilities resident inspector indirect GTG Greater than Green IC incomplete INPO Institute of Nuclear Power Operations IP Inspection procedure IPC Inspection Planning Cycle IPM IP Management ISFSI Independent Spent Fuel Storage Installation ISTAR Inspection Scheduling, Tracking, and Reporting LER Licensee Event Reports LIV licensee-identified violation ML abbreviation for ADAMS Accession No.

NCV Non-cited violation NOED Notice of Enforcement Discretion NOV Notice of Violation NRII New Reactors Resident Inspector Indirect NRR Nuclear Reactor Regulation NSIR Nuclear Security and Incident Response OCFO Office of the Chief Financial Officer OCIO Office of the Chief Information Officer OI Office of Investigations OIG Office of the Inspector General OpESS Operating experience smart sample ORII Operating Reactors Resident Inspector Indirect OUO Official Use Only PI Performance Indicators

Issue Date: 05/10/24 Att5-1 0306 PIM Plant Issues Matrix RI Resident inspector ROP Reactor Oversight Process RPS Reactor Program System RRPS Replacement Reactor Program System SCCI Substantive cross cutting issue SDP significance Determination Process SER Security Event Report SG security/safeguards baseline inspection SGI safeguards information SGT security inspection travel SPD security preparation and documentation SPLF security appeal follow-up SRI Senior resident inspector SSM security assessment SUNSI Sensitive Unclassified Nonsafeguards Information TE Traditional enforcement TI Temporary Instruction URI unresolved item USBM Unique Site Budget Model VIO violation WER Written Event Report

Issue Date: 05/10/24 Att5-2 0306 Attachment 6: Revision History for IMC 0306

Commitment Accession Description of Change Description of Comment Resolution and Tracking Number Training Closed Feedback Form Number Issue Date Required and Accession Number (Pre-Change Notice Completion Decisional, Non-Public Date Information)

ML031780118 Initial Issue 6/20/03 CN 03-021 ML053220168 Revised to: 1) incorporate recommendations from a 11/15/05 recent OIG audit of the Reactor Program System, 2)

CN 05-029 clarify the uses and definitions of several terms to ensure consistent application, 3) clarify the process for initiating and updating inspection finding information in RPS, and 4) remove several of the detailed attachments and tables to relocate them to the internal ROP Web page for easier revision and maintenance.

ML0702401890 Revised to inform the Program Offices and the Regions ML070790675 4/04/07 of updated guidance and procedures for RPS and the CN 07-012 ROP webpage. Researched commitments back four years - none found.

ML083290114 Revised to include guidance on Confirmatory Orders, ML083290136 12/04/08 clarifying the use of URIs, and Security items being CN 08-034 entered into the PIM. In addition to incorporate feedback from stakeholders.

ML111430179 Rewrite for organization. Revised to make the format 11/17/11 consistent with IMC 0040; to improve readability; to CN 11-036 incorporate changes resulted from FBF (1579, 1516, 1488 and 1388); to correct outdated guidance; and to be consistent with IMC 0612 and 0305.

Issue Date: 05/10/24 Att6-1 0306 Commitment Accession Description of Change Description of Comment Resolution and Tracking Number Training Closed Feedback Form Number Issue Date Required and Accession Number (Pre-Change Notice Completion Decisional, Non-Public Date Information)

ML12089A070 Revised for Security Cornerstone Reintegration ML12153A281 06/13/12 CN 12-009 ML14065A228 Revised to include comments from FBF 0306-1739, ML14181A494 07/18/14 which asks for clarification in LER section 05.05.g.7.(2) 0306-1739 CN 14-016 regarding tracking LERs in RPS, with the exception of ML13261A196 telephone notifications and FBF 0306-1897, which 0306-1879 discusses aligning IMC 0612 Exhibit 2 with IMC 0306, ML14181A388 as well as make editorial changes, based on FBF 0306- 0306-1897 1879 to ensure ease of use for new users to RPS, and ML13182A222 FBF 0306-2000 which requests a match in the timeline 0306-2000 for action matrix information, for both IMC 0305 and ML14181A469 IMC 0306.

ML15341A089 Revised editorially to change the manual chapter title to 0306-2138 12/23/15 be more descriptive, change substantive cross cutting ML15267A489 CN 15-032 issue (SCCI) to cross cutting issues (CCI) per feedback 0306-2161 form 0306-2138. Added information regarding ML15267A541 inspection item numbering in s ection 05.03.b.2 to say that LINCVs will not be numbered as an item in an inspection report. Added text for counting LINCVs specifically as BI for Congress with a placeholder baseline procedure and changed security and emergency preparedness assessment l etters to inspection planning transmittal letters.

Issue Date: 05/10/24 Att6-2 0306 Commitment Accession Description of Change Description of Comment Resolution and Tracking Number Training Closed Feedback Form Number Issue Date Required and Accession Number (Pre-Change Notice Completion Decisional, Non-Public Date Information)

ML18071A040 Major revision to align with new RPS-Inspections ML18071A046 05/10/18 application, as well as the splitting of MC 0611, Power 0305-2226 CN 18-012 Reactor Inspection Reports, and IMC 0612, Issue 0306-2202 Screening ML18072A131 0306-2238 ML18072A139

[C1] ML19191A101 Major revision to align with changes made to RPS-ML19191A050

[C2] 11/04/19 Inspections with the addition of the auto report 0306-2347 CN 19-034 generator function. Also, includes a title change to the ML18269A010 IMC and reformatting to allow for improved readability.

Added text in response to OIG Audit OIG-18-A-13 [C1]

and OIG Audit 13-A-16 [C2].

[C3] ML20302A345 Minor revision to expand guidance, and capture ML20302A349 02/24/21 updates to inspection report numbering, inspection CN 21-010 report completion status, GTG corrective actions, and Branch Chief approval functionality. In response to OIG-20-A-11, Audit of the NRCs Nuclear Power Plant Surveillance Test Inspection Program, Recommendations 1 and 2, added an action to periodically sample various standard RRPS reports for accuracy and provide results to DRO management.

[C4] ML22235A101 Minor revision to expand guidance and capture updates ML22242A300 10/13/22 to RPS software. Added guidance as a ttachment 4 in CN 22-022 response to recommendation 1 of OIG-21-A-07, Audit 0306-2465 of the NRCs Nuclear Power Reactor Inspection Issue ML22224A227 Screening.

Issue Date: 05/10/24 Att6-3 0306 Commitment Accession Description of Change Description of Comment Resolution and Tracking Number Training Closed Feedback Form Number Issue Date Required and Accession Number (Pre-Change Notice Completion Decisional, Non-Public Date Information)

ML24044A215 Revised to discuss quadrennial inspection efforts and ML24046A147 05/10/24 address lessons learned associated with CAPR CN 24-014 documentation in RPS.

Issue Date: 05/10/24 Att6-4 0306