NNSA_PMIS_RFI_1.pdf

REQUEST FOR INFORMATION

Program Management Information System for the National Nuclear Security Administration’s (NNSA) Research, Development, Test &

Evaluation (NA-11)

This is not a request for proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Market Research is being conducted at this time for the sole purpose of determining interest and capability of potential sources to meet the needs of DOE/NNSA.

I. BACKGROUND/PROGRAM DESCRIPTION

Within NNSA’s Defense Programs, the Research, Development, Test & Evaluation office provides the scientific foundation; the capabilities, tools and components to enable design assessment, qualification, certification, and technology maturation; and balances the most pressing investments needed to meet Department of Defense (DoD) warhead requirements and schedules, along with the critical long-term research and development needed for a robust and responsive future stockpile.

RDT&E is comprised of the following five subprograms:

1. Assessment Science

2. Engineering and Integrated Assessments

3. Inertial Confinement Fusion

4. Advanced Simulation and Computing

5. Weapon Technology and Manufacturing Maturation

With an average operational budget of over $3 billion, NA-11 oversees thousands of projects across the nuclear security enterprise. Currently, NA-11 lacks the ability to integrate program management activities with the Planning, Programming, Budget, and Evaluation (PPBE) process throughout the life cycle of a project. Additionally, it lacks an integrated system to track the progress of defined scope, work packages, and/or projects within each subprogram (listed below) and, where necessary, integrate budget requirements across the subprograms.

NA-11 is considering the acquisition of a program management information system (PMIS) to be the primary resource for program management across the organization.

The PMIS will be NA-11’s primary resource for program management. Over the course of the PPBE, it will serve several purposes. In the planning and program phase, the tool will be used to collect requirements from the management and contracting labs, plants, and sites (M&Os) with sufficient information for the federal program manager (FPM) and office leadership to make programmatic and budgetary decisions in developing the program’s 5-year Future Years Nuclear Security Plan (FYNSP). Information from the Project Plans (PPs) will be captured in the PMIS system and will facilitate accounting for mortgages for projects over their life cycle. Once projects are funded by the program office, the tool will be used to track execution, develop roadmaps and communicate accomplishments with end users and stakeholders.

II. GOALS & OUTCOMES

The NA-11 PMDB system will allow the Principal Assistant Deputy Administrator (PADA) and Deputy PADA to easily track the progress of the NA-11 program. The development of a Program Management Plan (PMP) will happen concurrently to acquisition and implementation of the PMIS, therefore the initial instantiation may not be what is finally deployed. The following goals and objectives capture the current understanding of what is needed:

• Goal 1 – Standardize program management.

o Provide a user-friendly program management system for all members of the

NA-11 community.

o Have easy access to information requested from external stakeholders.

• Goal 2 – Streamline decision making.

o Provide transparency in scope, cost, and schedule to NA-11 Leadership.

o Allow FPMs to easily coordinate cross-office scope.

• Goal 3 – Communicate effectively.

o Create standardized reports and presentations for internal and external stakeholders o Capture consistent information across subprograms.

• Goal 4 – Apply broadly.

o Allow for other Defense Programs organizations to adopt it in time, should they so choose, through flexibility in construction of the application.

o Utilize the information from the variety of existing tools at HQ and the M&Os and have a useable system quickly.

NA-11 would like to implement a solution that can be used for the long term. The need is for something that immediately but can be updated based on user needs and lessons learned from previous instantiations. We would like respondents that can incorporate artificial intelligence into the information system to help decision makers identify duplication of effort or potential gaps in scope and enhance other aspects of the program management process. Additionally, respondents should have the ability to create a customized training experience for users.

Respondents are invited to provide an overview of their capabilities that will show NA-11 what is possible with their system(s). Additionally, we invite respondents to include information in response to the attached draft System Requirements.

III. GENERAL QUESTIONS

1) Briefly describe how your company could execute the PMIS and the company’s timeline.

2) What capabilities or joint ventures, such as small business teaming arrangements, could your company leverage to complete?

3) What additional information or documentation would you require from NNSA to support or execute the request?

4) NNSA plans to conduct this procurement on a firm-fixed price (FFP) basis. Please comment on this contracting approach or recommend alternative approaches that may be more advantageous and explain why.

5) Identify any gaps or missing information in the scope of work.

NA-11 is especially interested in hearing feedback on this proposed project from respondents with experience in providing program management information systems to large and diverse technical companies. The respondents will preferably already have experience with and implementation in organizations within the nuclear security enterprise (such as NNSA headquarters or M&O contractors like Los Alamos National Laboratory or Kansas City National Security Campus).

IV. CAPABILITY STATEMENT FORMAT

Interested parties that have experience in software development or other related services are requested to submit a capability statement and the following company information.

1) Number of years’ experience and description of experience in software or related services including any development, operations, and management expertise.

2) Current Federal Government contract (if any).

3) Name & address

4) Point of contact email address and phone number

5) Response to questions outline in Section III.

Capability statements, which includes responses to the questions in Section III, shall be no more than 15 pages in length. Any and all cost associated with the preparation of the capability statement is the sole responsibility of the respondents.

V. SUBMISSION INSTRUCTIONS

DOE invites all interested parties to submit in writing by April 30, 2025, comments and information on matters addressed in this RFI in the capability statement. Any information that may be business proprietary and exempt by law from public discourse should be submitted as described in Section VI Business Proprietary Information. Interested vendors shall submit capability statements to kyle.krzywicki@nnsa.doe.gov by April 30, 2025 at

1:00PM EST.

FOR FURTHER INFORMATION CONTACT: Requests for further information should be sent to: Kyle Krzywicki at kyle.krzywicki@nnsa.doe.gov with “Question on NA-11 PMIS” in the subject line.

VI. BUSINESS PROPRIETARY INFORMATION

Pursuant to 10 CFR 1004.11, any person submitting information he or she believes to be business proprietary and exempt by law from public disclosure should submit via email, or postal mail two well-marked copies: One copy of the document marked “Business Proprietary” including all the information believed to be proprietary, and one copy of the document marked “non-Proprietary” with the information believed to be business proprietary deleted. DOE will make its own determination about the business proprietary status of the information and treat it according to its determination. Factors of interest to DOE when evaluating requests to treat submitted information as business proprietary include: (1) a description of the items; (2) whether and why such items are customarily treated as business proprietary within the industry; (3) whether the information is generally known by or available from other sources; (4) whether the information has previously been made available to others without obligation concerning its business proprietary nature; (5) an explanation of the competitive injury to the submitting person which would result from public disclosure;

(6) when such information might lose its business proprietary character due to the passage of time; and (7) why disclosure of the information would be contrary to the public interest.

VII. RFI DISCLAIMER

This is not a request for proposals (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Market Research is being conducted at this time for the sole purpose of determining interest and capability of potential sources currently available to meet the needs of DOE/NNSA. In accordance with Federal Acquisition Regulation 15.201 (e) RFIs may be used when the Government does not presently intend to award a contract, but wants to obtain price, delivery, or other market information or capabilities for planning purposes. Responses to these notices are not offers and cannot be accepted by the Government to form a binding contract.

VIII. APPENDIX

The PMIS system must address the following:

• Security, Access, and Authorization o Instance on both the low (unclassified) and high (classified) sides that are reconciled at regular intervals

• Version Control

• End User Operating Environment o Flexible search capability and ability to modify data

• Implementation o The system will be available 24 hours a day, 7 days a week, 365 days per year

• Application Requirements o Budget o Schedule o Competed proposals o Project/Scope descriptions o Project/Scope progress o Priority tasks/items that need attention o Dashboard and reports that tie programmatic scope and strategic priorities to funding and schedule

• Data Requirements o Planning & Programming phase data requirements Program management Strategic alignment Roadmaps and progression metrics Financial data o Execution & Evaluation phase requirements (data fields to include) Technology Transfer Agreements, Technology Realization Teams, Interface Requirements Agreements, and other agreements Execution year scope with deliverables and milestones Level 2 Milestones Status Schedule progression metric (Technology Readiness Level and/or

Manufacturing Readiness Level dates, Critical Decision dates, execution date)

Threats to cost, schedule or scope Mitigation strategy to threats to cost, schedule or scope Noteworthy accomplishments or information Financial Data

VIII. APPENDIX