ML25227A106
| ML25227A106 | |
| Person / Time | |
|---|---|
| Issue date: | 09/11/2025 |
| From: | Office of the Chief Human Capital Officer, NRC/OCIO/CISD |
| To: | |
| Hardy S | |
| References | |
| Download: ML25227A106 (1) | |
Text
U.S. Nuclear Regulatory Commission Privacy Impact Assessment NRC Enterprise eXecution and Utilization System (NEXUS)
OCHCO Version 0.1 8/14/2025 Instruction Notes:
Please do not enter the PIA document into ADAMS. An ADAMS accession number will be assigned through the e-Concurrence system which will be handled by the Privacy Team Template Version 2.5 (03/2025)
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 Document Revision History Date Version PIA Name/Description Author 4/30/2025 0.1 DRAFT NEXUS PIA Stephanie Schouw, OCHCO
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 Table of Contents 1
Description 1
2 Authorities and Other Requirements 3
3 Characterization of the Information 3
4 Data Security 5
5 Privacy Act Determination 8
6 Records and Information Management-Retention and Disposal 10 7
Paperwork Reduction Act 13 8
Privacy Act Determination 15 9
OMB Clearance Determination 16 10 Records Retention and Disposal Schedule Determination 17 11 Review and Concurrence 18
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 1
The agency is subject to the requirements of the E-Government Act and is committed to identifying and addressing privacy risks whenever it develops or makes changes to its information systems. The questions below help determine any privacy risks related to the E-Government Act or later guidance by the Office of Management and Budget (OMB) and the National Institute of Standards and Technology (NIST).
Name/System/Subsystem/Service Name: NEXUS - NRC Enterprise eXecution and Utilization System.
Data Storage Location (i.e., Database Server, SharePoint, Cloud, Other Government Agency, Power Platform): Microsoft Dataverse.
Date Submitted for review/approval: August 15, 2025.
1 Description 1.1 Provide the description of the system/subsystem, technology (i.e., Microsoft Products), program, or other data collections (hereinafter referred to as project).
Explain the reason the project is being created.
The NRC Enterprise eXecution and Utilization System (NEXUS) is a model driven application built on the Microsoft Power Platform that is designed to collect, create, and consolidate data from NRC authoritative systems. This data is used to support agency processes for workforce management, strategic workforce planning, workload management, program management, and project management. By providing authorized users with standardized, quality-controlled information, NEXUS enables the NRC to make informed decisions about resource allocation, anticipate workforce needs, project execution, and align operational activities with organizational objectives. The application emphasizes sustainable data management practices that reduce administrative burden while maximizing the utility of existing business processes and tools, supporting the agency's mission through improved data accessibility and analysis capabilities.
The NEXUS application supports the Agency Project Management Initiative (APMI) which is a Strategic Direction Initiative requested by the EDO.
Please mark appropriate response below if your project/system will involve the following:
PowerApps Server/Database Design Dashboard Public Website SharePoint Internal Website Cloud Service Provider Other
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 2
1.2 Does this privacy impact assessment (PIA) support a proposed new project, proposed modification to an existing project, or other situation? Select options that best apply in table below.
Mark appropriate response.
Status Options
New system/project
Modification to an existing system/project.
If modifying or making other updates to an existing system/project, provide the ADAMS ML of the existing PIA and describe the modification.
Annual Review If making minor edits to an existing system/project, briefly describe the changes below.
Other (explain) 1.3 Points of
Contact:
(Do not adjust or change table fields. Annotate N/A if unknown. If multiple individuals need to be added in a certain field, please add lines where necessary.)
Role Contact Information Name Office/Division/Branch Phone Number Project Manager(s)
Stephanie Schouw, OCHCO System Owner/Data Owner or Steward Matthew R. Meyer, OCHCO, 301-414-6198 ISSM Primary: Consuella Debnam, OCIO/IAOB, 301-287-0834 Alt: Luc Phuong, OCIO/IAOB, 301-415-1103 Executive Sponsor Caroline Carusone, OCIO, 301-415-1085 Jennifer Golder, OCHCO, 301-287-0741 Other
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 3
2 Authorities and Other Requirements 2.1 What specific legal authorities and/or agreements permit the collection of information for the project?
Provide all statutory and regulatory authorities for operating the project, including the authority to collect the information; NRC internal policy is not a legal authority. Please mark appropriate response in table below.
Mark with an X on all that apply.
Authority Citation/Reference
Statute Privacy Act of 1974, as amended, 5 U.S.C. §552a Paperwork Reduction Act, as amended, 44 U.S.C. § 3501 et seq E-Government Act of 2002, Section 208 (Public Law 107-347)
Records Management by Federal Agencies, 44 U.S.C. Chapter 31
Executive Order Stopping Waste, Fraud, and Abuse by Eliminating Information Silos
Federal Regulation U.S. Code Title 5 Section 1104 (5 USC 1104)
Memorandum of Understanding/Agreement N/A
Other (summarize and provide a copy of relevant portion)
Accelerating Deployment of Versatile, Advanced Nuclear for Clean Energy Act of 2024 (Advance Act), Section 502.
2.2 Explain how the information will be used under the authority listed above (i.e., enroll employees in a subsidies program to provide subsidy payment).
NEXUS will be used to manage the NRC workforce with regard to workforce management, workload management, and project management.
If the project collects Social Security numbers, state why this is necessary and how it will be used.
N/A 3 Characterization of the Information In the table below, mark the categories of individuals for whom information is collected.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 4
Category of individual
Federal employees
Contractors
Members of the Public (any individual other than a Federal employee, consultant, or contractor)
Licensees
Other In the table below, is a list of the most common types of PII collected. Mark all PII that is collected and stored by the project/system. If there is additional PII not defined in the table below, a comprehensive listing of PII is provided for further reference in ADAMS at the following link: PII Reference Table.
Categories of Information
Name
Resume or curriculum vitae
Date of Birth
Driver's License Number
Country of Birth
License Plate Number
Citizenship
Passport number
Nationality
Relatives Information
Race
Taxpayer Identification Number
Home Address
Credit/Debit Card Number
Social Security number (Truncated or Partial)
Medical/health information
Sex (Male or Female)
Alien Registration Number
Ethnicity
Professional/personal references
Spouse Information
Criminal History
Personal e-mail address
Biometric identifiers (facial images, fingerprints, iris scans)
Personal Bank Account Number
Emergency contact e.g., a third party to contact in case of an emergency
Personal Mobile Number/Home Number Accommodation/disabilities information
Marital Status
Children Information
Mother's Maiden Name
Other: Security Clearance (i.e., level of clearance an individual holds),
Personnel Files (i.e., employment history and performance evaluations);
Academic and Professional Background Information (i.e., college degrees, year of graduation, and certifications)DOB calculation comes from FPPS, Address information is only city, state and zip
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 5
3.1 Describe how the data is collected for the project. (i.e., NRC Form, survey, questionnaire, existing NRC files/ databases, response to a background check).
Information about NRC employees is collected from the following systems: Department of Interior Datamart which contains data from Federal Personnel and Payroll System (FPPS) and Workforce Transformation Tracking System (WTTS). NEXUS also aggregates data from NRC systems through the Enterprise Data Warehouse.
3.2 If using a form (paper or web) to collect the information, provide the form number, title and/or a link to the form.
No form is used to collect user identifying information.
3.3 Who provides the information? Is it provided directly from the individual or a third party.
Employee and contractor information is provided during onboarding new employees through FPPS/WTTS and Personnel Security Adjudication Tracking System (PSATS).
3.4 Explain how the accuracy of the data collection is validated. If the project does not check for accuracy, please explain why.
The data provided by authoritative systems (such as FPPS) is assumed to be accurate before it enters NEXUS. However, NEXUS does contain validations to check for missing information such as incorrect organization and blank data fields where data is expected or required.
3.5 Will PII data be used in a test environment? If so, explain the rationale for this and how the PII information is protected.
An employees duty station can be equivalent to the home address under certain circumstances.
Therefore, duty station information at the address level will only be accessible through Role-Based Security controls, by employees that have a need to know. Other PII data needed for the NEXUS application (i.e., date of birth, and employee age) is stored in a non-NEXUS Dataverse environment. An employees date of birth and age remains in the non-NEXUS Dataverse environment where it is used to produce calculated results. The non-PII calculated fields are then provided to the NEXUS Dataverse environment.
3.6 What procedures are in place to allow the subject individual to correct inaccurate or erroneous privacy information?
Inaccurate or erroneous privacy information appearing in NEXUS is consumed from authoritative sources like FPPS. Corrections need to be made in the authoritative system.
4 Data Security 4.1 Describe who has access to the data in the project (i.e., internal NRC, system administrators, external agencies, contractors, public).
System administrators, internal NRC staff, and contractors with a need-to-know.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 6
4.2 If the project/system shares information with any other NRC systems, identify the system, what information is being shared and the method of sharing.
NEXUS shares staffing action information with FPPS/WTTS, including temporary reassignments, permanent reassignments, duty station changes and employee qualification data with the Talent Management System (TMS) and acts as the interface for these systems.
FPPS/WTTS and TMS will remain the authoritative system for workforce data. NEXUS will also maintain and share workforce and workload data with the Enterprise Data Warehouse as requested by users.
4.3 If the project/system connects, receives, or shares information with any external non-NRC partners or systems, identify what is being shared.
If so, identify what agreements are in place with the external non-NRC partner or system in the table below.
Agreement Type
Contract Provide Contract Number:
License Provide License Information:
Memorandum of Understanding Provide ADAMS ML number for MOU:
Other
None 4.4 Describe how the data is accessed and describe the access control mechanisms that prevent misuse.
Access to NEXUS data is regulated by a combination of database record ownership (including the owner and owning business unit) and the current user's security role(s). A user's business unit is updated daily through an automated process that utilizes their assigned NRC organization (such as office or region, division, branch, and/or team). User security role assignments are also updated automatically when a users position within the NRC changes, encompassing both the addition and removal of security roles. Users with the System Administrator role have unrestricted access to all data in NEXUS, and their security role assignment is verified monthly. No more than three individuals will hold the System Administrator role at any given time.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 7
4.5 Explain how the data is transmitted and how confidentiality is protected (i.e.,
encrypting the communication or by encrypting the information before it is transmitted).
Data are encrypted at rest and in motion. Access to data from within NEXUS is restricted to those with need to know via business units and Role Based Access.
4.6 Describe where the data is being stored (i.e., NRC, Cloud, Contractor Site).
Power Platform Dataverse within the NEXUS Dataverse Environment.
4.7 Explain if the project can be accessed or operated at more than one location.
NEXUS is a cloud based internal system accessible via Intranet URL. The system utilizes SSO and two factor authentication via PIV/PIN.
4.8 Can the project be accessed by a contractor? Have the contractors completed an IT-II investigation? Do they possess an NRC badge?
Yes, contractors must possess a badge and PIV card.
4.9 Explain the auditing measures and technical safeguards in place to prevent misuse of data.
Every table and field can have auditing turned on for it. A field with auditing turned on has its change history logged based on who made the change and when. In terms of preventing misuse of data, there are authorization-based permissions applied to every user in the system that limits their abilities to see records that they are/arent an owner of or given permission to.
For PII information, field-column security is enabled, which has even more security applied as you need to both be given permissions to the record, and you need to be given the PII-specific security role to view the data. A monthly review will be conducted for security roles to monitor for correct access and need to know.
4.10 Describe if the project has the capability to identify, locate, and monitor (i.e.,
trace/track/observe) individuals.
NEXUS will track and monitor the NRC workforce with respect to workload, project schedules, and output from managed activities for reporting, accountability, and performance.
4.11 Define which FISMA boundary this project is part of.
Business Application Support System (BASS).
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 8
4.12 Is there an Authority to Operate (ATO) associated with this project/system?
Authorization Status
Unknown
No If no, please note that the authorization status must be reported to the Chief Information Security Officer (CISO) and Computer Security Organization (CSOs)
Point of Contact (POC) via e-mail quarterly to ensure the authorization remains on track.
In Progress provide the estimated date to receive an ATO.
Estimated date: TBD
Yes Indicate the data impact levels (Low, Moderate, High, Undefined) approved by the Chief Information Security Officer (CISO)
Confidentiality-Moderate Integrity-Moderate Availability-Moderate 4.13 Provide the NRC system Enterprise Architecture (EA)/Inventory number. If unknown, contact EA Service Desk to get the EA/Inventory number.
N/A.
5 Privacy Act Determination 5.1 Is the data collected retrieved by a personal identifier?
Mark the appropriate response.
Response
Yes, the PII is retrieved by a personal identifier (i.e., individuals name, address, SSN, or other unique number, etc.)
List the identifiers that will be used to retrieve the information on the individual.
Employee ID
No, the PII is not retrieved by a personal identifier.
If no, explain how the data is retrieved from the project.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 9
5.2 For all collections where the information is retrieved by a personal identifier, the Privacy Act requires that the agency publish a System of Record Notice (SORN) in the Federal Register. As per the Privacy Act of 1974, "the term 'system of records' means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some other personal identifier assigned to the individual.
Mark the appropriate response in the table below.
Response
Yes, this system is covered by an existing SORN. (See existing SORNs:
https://www.nrc.gov/reading-rm/foia/privacy-systems.html )
Provide the SORN name, number, (List all SORNs that apply):
SORN System Covered OPM/GOVT General Personnel Records FPPS - WTTS -
PSATS -- TMS OPM/GOVT Employee Performance FPPS OPM/GOVT Recruiting, Examining, and Placement Records WTTS OPM/GOVT Applicant Race, Sex, National Origin and Disability Status Records FPPS --WTTS NRC 11 - Reasonable Accommodations Records FPPS -- WTTS NRC 19 - Official Personnel Training Records TMS NRC 21 - Payroll Accounting Records FPPS --WTTS NRC Drug Testing Program Records PSATS NRC Personnel Security Files and Associated Records PSATS
SORN is in progress
SORN needs to be created
Unaware of an existing SORN
No, this system is not a system of records and a SORN is not applicable.
5.3 When an individual is asked to provide personal data (i.e., form, webpage, survey), is a Privacy Act Statement (PAS) provided?
A Privacy Act Statement is a disclosure statement required to appear on documents
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 10 used by agencies when an individual is asked to provide personal data. It is required for any forms, surveys, or other documents, including electronic forms, used to solicit personal information from individuals that will be maintained in a system of records.
Mark the appropriate response.
Options
Privacy Act Statement
Not Applicable
Unknown 5.4 Is providing the PII mandatory or voluntary? What is the effect on the individual by not providing the information?
N/A 6 Records and Information Management-Retention and Disposal The National Archives and Records Administration (NARA), in collaboration with federal agencies, approves whether records are Temporary (eligible at some point for destruction/deletion because they no longer have business value) or Permanent (eligible at some point to be transferred to the National Archives because of historical or evidential significance). Records/data and information with historical value, identified as having a permanent disposition, are transferred to the National Archives of the United States at the end of their retention period. All other records identified as having a temporary disposition are destroyed at the end of their retention period in accordance with the NARA Records Schedule or the General Records Schedule.
These determinations are made through records retention schedules and NARA statutes (44 United States Code (U.S.C.), 36 Code of Federation Regulations (CFR)). Under 36 CFR, agencies are required to establish procedures for addressing Records and Information Management (RIM) requirements. This includes strategies for establishing and managing recordkeeping requirements and disposition instructions before approving new electronic information systems or enhancements to existing systems.
The following questions are intended to determine whether the records/data and information in the system have approved records retention schedules and disposition instructions, whether the system incorporates RIM strategies including support for NARAs Universal Electronic Records Management (ERM) requirements, and if a mitigation strategy is needed to ensure compliance.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 11 If the project/system:
Does not have an approved records retention schedule and/or Does not have an automated RIM functionality, Involves a cloud solution, And/or if there are additional questions regarding Records and Information Management
- Retention and Disposal, please contact the NRC Records staff at ITIMPolicy.Resource@nrc.gov for further guidance.
If the project/system has a record retention schedule or an automated RIM functionality, please complete the questions below.
6.1 Does this project map to an applicable retention schedule in NRCs Comprehensive Records Disposition Schedule (NUREG-0910), or NARAs General Records Schedules?
NUREG-0910, NRC Comprehensive Records Disposition Schedule
NARAs General Records Schedules
Unscheduled 6.2 If so, cite the schedule number, approved disposition, and describe how this is accomplished.
System Name (include sub-systems, platforms, or other locations where the same data resides)
NEXUS Records Retention Schedule Number(s)
(See table below)
Approved Disposition Instructions Is there a current automated functionality or a manual process to support RIM requirements? This includes the ability to apply records retention and disposition policies in the system(s) to support records accessibility, reliability, integrity, and disposition.
NRC Enterprise eXecution and Utilization System (NEXUS) will be assessed using the Records and Information (RIM) Certification process. The structured process will provide criteria aligned with the Suggested Rating to accurately reflect the system's ability to support records management requirements.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 12 Disposition of Temporary Records Will the records/data or a composite be automatically or manually deleted once they reach their approved retention?
NRC Enterprise eXecution and Utilization System (NEXUS) will be assessed using the Records and Information (RIM) Certification process. The structured process will provide criteria aligned with the Suggested Rating to accurately reflect the system's ability to support records management requirements.
Disposition of Permanent Records Will the records be exported to an approved format and transferred to the National Archives based on approved retention and disposition instructions?
If so, what formats will be used?
NRC Transfer Guidance (Information and Records Management Guideline -
IRMG)
Schedule Number and Title Disposition Instructions GRS 1.1, Item 001: Financial management and reporting administrative records.
Workload management and assignment records Temporary. Destroy when 3 years old, but longer retention is authorized if needed for business use.
GRS 2.2, Item 020: Workforce and succession planning records Temporary. Destroy 3 years after issuing each new plan, but longer retention is authorized if required for business use.
GRS 2.2, Item 070: Employee performance file system records.
Acceptable performance appraisals of non-senior executive service employees.
Temporary. Destroy no sooner than 4 years after date of appraisal, but longer retention is authorized if required for business use.
GRS 2.2, Item 072: Employee performance file system records.
Records of senior executive service employees.
Temporary. Destroy no sooner than 5 years after date of appraisal, but longer retention is authorized if required for business use.
GRS 2.4, Item 060: Payroll program administrative Records.
Administrative correspondence between agency and payroll processor, and system reports used for agency workload and or personnel management purposes.
Temporary. Destroy when 2 years old, but longer retention is authorized if required for business use.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 13 GRS 3.1, Item 012: Special purpose computer programs and applications.
Temporary. Delete when related master file or database has been deleted, but longer retention is authorized if required for business use.
SF115 N1-431-08-009: Strategic Workforce Planning System (SWP), Item A(2) Master File Temporary. Cutoff employee's information when an employee terminates employment. Destroy or delete the General Employee Information and Employee Skill data and any related Management Input and Audit Records from the master file, 5 years after cutoff.
SF115 N1-431-08-009: The Senior Executive Service Succession Planning System (SESSPS), Item B(2) Master File TEMPORARY. Cutoff employee's information when an employee terminates employment. Destroy or delete the General Employee Information 5 years after cutoff.
7 Paperwork Reduction Act The Paperwork Reduction Act (PRA) of 1995 requires that agencies obtain an Office of Management and Budget (OMB) approval in the form of a "control number"before promulgating a paper form, website, surveys, questionnaires, or electronic submission from 10 or more members of the public. If the data collection is from Federal employees regarding work-related duties, then a PRA clearance is not necessary.
7.1 Will the project be collecting any information from 10 or more persons who are not Federal employees?
No 7.2 Is there any collection of information addressed to all or a substantial majority of an industry (i.e., Fuel Fabrication Facilities or Fuel Cycle Facilities)?
No 7.3 Is the collection of information required by a rule of general applicability?
No Note: For information collection (OMB clearances) questions: contact the NRCs Clearance Officer. Additional guidance can be found on the NRCs internal Information Collections Web page at: https://intranet.nrc.gov/ocio/33456.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 14 STOP HERE - The remaining pages will be completed by the Privacy Officer, Records Management, and Information Collections Team.
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 15 8 Privacy Act Determination Project/System Name: NRC Enterprise eXecution and Utilization System (NEXUS)
Submitting Office: OCHCO Privacy Officer Review Review Results Action Items
This project/system does not contain PII.
No further action is necessary for Privacy.
This project/system does contain PII; the Privacy Act does NOT apply, since information is NOT retrieved by a personal identifier.
Must be protected with restricted access to those with a valid need-to-know.
This project/system does contain PII; the Privacy Act does apply.
SORN is required-Information is retrieved by a personal identifier.
Comments:
NEXUS retrieves data from multiple systems, each of which is governed by the SORNs identified in Section 5. Certain data elements constitute PII or other privacy-sensitive information and must be safeguarded in accordance with applicable requirements.
Any future modifications to NEXUSsuch as modifications to existing data fields, the introduction of new data elements, the implementation of direct data entry capabilities, or the use of forms to facilitate process automation will require an updated PIA to address new privacy considerations.
Reviewers Name Title Privacy Officer Signed by Hardy, Sally on 08/27/25
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (03-2025)-ML050460335 16 9 OMB Clearance Determination NRC Clearance Officer Review Review Results
No OMB clearance is needed.
OMB clearance is needed.
Currently has OMB Clearance. Clearance No.
Comments:
The system uses existing information and does not collect information from entities covered by the requirements of the Paperwork Reduction Act. No OMB clearance is needed.
Reviewers Name Title Agency Clearance Officer Signed by Cullison, David on 08/18/25
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (10-2024)-ML050460335 17 10 Records Retention and Disposal Schedule Determination Records Information Management Review Review Results
No record schedule required.
Additional information is needed to complete assessment.
Needs to be scheduled.
Existing records retention and disposition schedule covers the system - no modifications needed.
Comments:
Reviewers Name Title Sr. Program Analyst, Electronic Records Manager Records and Information Management Specialist Signed by Dove, Marna on 08/25/25 Signed by Williams, Lisa on 09/11/25
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (10-2024)-ML050460335 18 11 Review and Concurrence Review Results
This project/system does not collect, maintain, or disseminate information in identifiable form.
This project/system does collect, maintain, or disseminate information in identifiable form.
I concur with the Privacy Act, Information Collections, and Records Management reviews.
Director Chief Information Security Officer Cyber Information Security Division Office of the Chief Information Officer Signed by Nalabandian, Garo on 09/11/25
NEXUS - OCHCO Version 0.1 Privacy Impact Assessment 07/17/2025 PIA Template (10-2024)-ML050460335 19 ADDITIONAL ACTION ITEMS/CONCERNS Name of Project/System:
NRC Enterprise eXecution and Utilization System (NEXUS)
Date CISD received PIA for review:
August 15, 2025 Date CISD completed PIA review:
August 26, 2025 Action Items/Concerns:
As NEXUS retrieves data from the systems listed below, the PIAs must be updated to document the interface with NEXUS.
FPPS WTTS PSATS TMS In addition, the Enterprise Data Warehouse/Master Data Management System (MDMS) must be transitioned from a PTA to a PIA, as it will be storing PII and must accurately reflect this integration.