Request for Information (RFI) Fangorn_Final.pdf

UNCLASSIFIED August 2024

REQUEST FOR INFORMATION (RFI)

Fangorn

Prepared by:

DISA HYBRID CLOUD SOLUTIONS

J-931

01 AUG 2024

BACKGROUND

The DISA J-9 is transforming the way it delivers hosting and compute solutions across the Department of Defense (DoD).

This transformational strategy is needed to not only help DoD embrace “Cloud” as the future of compute hosting, but also position DISA as a leader in the cloud hosting arena. This strategy is driving toward solutions that are hybrid, distributed, and multi-cloud. It is evident that the commercial industry is on the cutting edge of cloud support and hosting and to ensure DISA and the DoD maintain a strong and robust computing infrastructure, we must look to forge strong ongoing partnerships with industry and adopt innovative commercial technologies for use in the Government. Partnering with industry to achieve these objectives is paramount for the Department’s success.

The J-9 currently has multiple IBM z hosting environments (including z/OS and Linux on z) that operate isolated and independent of one another. The current mainframe computing offering is 30+ years old and hasn’t changed much over this time. This offering comes with many challenges including: the inability to modify software and hardware capabilities;

the inflexibility of costs as environments scale up/down; and a high barrier to entry to add new technology. Each environment is unique and different processes and hosts disparate applications with unique supporting software.

DISA J-9 seeks information from industry on how to develop a single environment that rationalizes and encompasses all IBM z environments within the J-9, merging disparate software and hardware components into a modernized infrastructure and services offering we’re calling Fangorn. The OT prototype will include a modern technology implementation strategy to achieve a rapid deployment of the new Fangorn prototype. In addition to a rapid deployment strategy, there will be a streamlined and modern migration strategy for existing workloads hosted in the J-9’s current IBM z environments.

The Fangorn prototype solution needs to be housed in a consolidated stack located within multiple Continental United States (CONUS) DISA datacenters. This stack will be standardized for eventual uniform deployment to multiple sites, including potential Outside Continental United States (OCONUS) locations.

The J-9 envisions its new Fangorn infrastructure having several desired key features and technologies:

1. Integrated hardware and software as a service infrastructure

2. Single software-as-a-service solution for sustaining and modernizing mainframe applications

3. Hosted on-premise

4. Unified and customizable control plane for additional internal services

5. Multi-Tenancy support with full customer environment segmentation

6. Utility based billing and reporting (pay-as-you-go)

7. Elasticity and Automated Scalability of IBM z physical hardware within the stack

8. Role Based Access Control (RBAC) for granular security management of tenant access

9. Infrastructure as Code ready for Ansible and Terraform

10. Interoperability support for existing J-9 enterprise level tools

11. Automated scalability

12. Monitoring and Alerting

13. Centralized portal for security posture

14. High Availability (HA) implementations for resources

15. Integrated file and image level backup solution

16. Full disaster recovery and migration solution to allow agnostic migration capabilities

17. Tenant Billing portal

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY.

THIS IS NOT A REQUEST FOR WHITE PAPER (RWP) or REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE

AT THIS TIME.

OVERVIEW/PURPOSE/DESCRIPTION OF PROCUREMENT

To enable DISA’s Mission Partners (MP) rapid access to a transformed, standardized, IBM z hosting environment, DISA is leveraging Other Transition Authority (OTA) to quickly develop a functional prototype. It is envisioned that rapid iterations of the initial prototype mainframe environment will be necessary to fully meet all critical success indicators.

The Government intends to pursue an aggressive approach, procuring a minimum viable capability release (MVCR) in less than one year. Following a successful prototype, the Government will continue the improvement, operationalization, and implementation of Fangorn capabilities through a follow-on Production OTA.

Throughout the execution of this project the Government intends to prototype evolving iterations of this first-of-its-kind capability to provide a single, centralized management control plane, integrated application development, and hardware/software synchronization using commercial technologies, prototype. Specifically, the Government intends to apply an agile methodology to create, design, develop, and demonstrate the operational utility for a production ready and operationalized Fangorn on-premises capability.

MARKET INTELLIGENCE APPROACH

The Government is considering the use of an Other Transaction Authority (OTA) for the Prototype, in order to support this unique acquisition. Additionally, the Government is considering instituting a Challenge Based Acquisition (ChBA) to understand industry capabilities and to reduce execution risk early in the process. To implement ChBA, the Government would provide short challenge scenarios prior to awarding an OTA, enabling industry partners to demonstrate their technical capabilities, as they specifically apply to this procurement. For more information on ChBA, please reference the ChBA guide at: https://www.mitre.org/news-insights/publication/challenge-based-acquisition-5th-edition

Through responses provided to this RFI and subsequent events, the Government intends to obtain the following information:

• Industry’s input and suggestions on refining the key features and technologies required as outlined in this RFI, including foreseen and unforeseen risks and areas that need clarification

• Industry’s input and suggestions that would help refine and improve the Government’s technical approach

• Industry’s feedback on the Government’s projected acquisition approach, including the ability to meet the requirements of an Other Transaction Authority (OTA) under 10 U.S.C. §4022

• Industry’s capabilities to meet the acquisition and technical characteristics of this requirement

Respondents to this RFI are invited to participate in a collaborative Program Manager (PM) question and answer (Q&A) session with the Government. The J-9 Director will make opening remarks at this event followed by the PM providing a brief overview of the program and acquisition approach. Following introductions there will be a Q&A session where industry can ask clarifying questions surrounding the requirements and future capability. This is intended to provide clarity into the Government’s approach and requirement.

PM Q&A details include:

• The event will occur at 1000 EDT on 13 AUG 2024. The event will be virtual, and a MS Teams link will be provided. An MS Teams Invitation will be provided to those companies who have submitted an RSVP to this event. Companies are requested to limit participation to no more than three (3) individuals.

• Questions for the Q&A session must be submitted ahead of the event and are due no later than 1300 EDT 09 AUG https://www.mitre.org/news-insights/publication/challenge-based-acquisition-5th-edition

2024.

• Companies who are interested in participating in the PM Q&A must RSVP no later than 1300 EDT 09 AUG 2024 to:

Vanessa McCollum, Agreements Officer, vanessa.a.mccollum.civ@mail.mil Ashley Fleming, Agreements Specialist, ashley.n.fleming12.civ@mail.mil Organization Box, disa.scott.ditco.mbx.pl84-other-transaction-authority@mail.mil

The Government expects that strong corporate teams may partner, with the ability to apply a broad range of knowledge, skills, software, and tools, will form the basis of successful offers. To encourage such teaming efforts, the Government intends to allow companies the opportunity to participate in a J-9 Fangorn Industry Networking Day (TechMoot). This event will follow the PM Q&A session on 27 AUG 2024. Companies will be given the opportunity to provide a 10–30 minute presentation (participation dependent) on their capabilities, for the purposes of partnering with other companies for the acquisition. The presentation materials and contact information provided will be posted to sam.gov along with this RFI for companies to reach out in preparation for the upcoming acquisition. Event location, daily schedule and additional details will be provided to those that RSVP in accordance with the guidance provided below, we request that companies limit attendance to no more than two (2) individuals.

Companies that are interested in participating in the J-9 Fangorn Industry Networking Day (TechMoot) must RSVP no later than 1400 EDT 15 AUG 2024 to:

Organization Box, disa.scott.ditco.mbx.pl84-other-transaction-authority@mail.mil

TECHNICAL CHARACTERISTICS

See Appendix 2 Statement of Need for the technical characteristics.

REQUESTED INFORMATION

All requested information is intended to facilitate the Government’s market intelligence efforts and inform the Government’s technical approach.

RESPONSE GUIDELINES

Interested parties are requested to respond to this RFI with a White Paper in accordance with the White Paper Format provided in Appendix 1. Submissions shall not exceed four (4) pages, single spaced, 11-point type with at least one-inch margins on 8 1/2” X 11” page size. Cover pages are not included in the page limit. The response should not exceed a 5MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s ability to meet the requirements of this effort. Oral communications are not permissible. Companies who wish to respond to this RFI should send responses via email no later than 0900 EDT 03 SEP 2024 to:

INDUSTRY DISCUSSIONS

DISA representatives may choose to meet with potential offerors and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS

Questions regarding this RFI shall be submitted in writing by email to:

mailto:vanessa.a.mccollum.civ@mail.mil mailto:ashley.n.fleming12.civ@mail.mil mailto:vanessa.a.mccollum.civ@mail.mil mailto:ashley.n.fleming12.civ@mail.mil mailto:disa.scott.ditco.mbx.pl84-other-transaction-authority@mail.mil mailto:vanessa.a.mccollum.civ@mail.mil mailto:ashley.n.fleming12.civ@mail.mil mailto:disa.scott.ditco.mbx.pl84-other-transaction-authority@mail.mil

Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov as an amendment to the RFI announcement. The Government does not guarantee that questions received after 1400 EDT 20 AUG 2024 will be answered.

SIGNIFICANT DATES / TIMES

Action Due Date Page and Attendee Limits Time Written Submissions:

White Paper and ROM response to Request for Information

Tuesday, September 3, Four (4) pages not including ROM 0900 EDT

Written question submissions Tuesday, August 20, 2024 --- 1400 EDT Government hosted Q&A Session Questions

Friday, August 9, 2024 --- 1300 EDT

Events:

RSVP to Government hosted Question and Answer (Q&A) Session

Friday, August 9, 2024 --- 1300 EDT

RSVP to J-9 Fangorn Industry Networking Day (TechMoot)

Thursday, August 15, 2024 --- 1400 EDT

Government hosted Question and Answer (Q&A) Session

Tuesday, August 13, 2024 Three (3) Representatives per Company 1000 EDT

J-9 Fangorn Industry Networking Day (TechMoot)

Tuesday, August 27, 2024 Two (2) Representatives per Company TBD

Please note that there are two question submission periods defined in this RFI announcement. The first submission date is for advanced questions in support of the Government-hosted Q&A Session. The second submission date is for all other written questions; the responses to these questions will be posted as amendment to this announcement. Ensure that your question submission email indicates for which of the two periods it is intended for.

The Government will not reimburse companies for any costs associated with the submissions of their responses or participation in the Question & Answer or Industry Networking events.

mailto:vanessa.a.mccollum.civ@mail.mil mailto:ashley.n.fleming12.civ@mail.mil

DISCLAIMER

This RFI is not a formal Request for White Papers or a Request for Proposal and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award an agreement. Responses will not be considered as proposals, nor will any award be made as a result of this synopsis. All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. Responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract or agreement.

Non-Government personnel will not be used in collecting market intelligence, which includes responses to this RFI.

APPENDIX 1: White Paper Format Cover Page Information (NOT included in 4-page limit) Identification Company Name Company Address Point of Contact (Primary) Phone Number E-mail Address Cage Code Unique Entity Identification (UEI) Number Company Web Page Other Classifications (e.g., large business, small business, SDB, HUBZone, 8(a), SDVOSB, WOSB, etc.)

List Government Wide, DoD, or DISA contracts you are on that are applicable as a Prime or a Subcontractor (Includes partnering on Platform 1)

Interest Describe your potential interest in this effort (e.g., prime, subcontract, teaming, joint ventures) and how you would meet the 10 U.S.C. §4022 requirements for qualifying for an OTA.

Corporate Capabilities Describe your company and any corporate information relevant to meeting the Fangorn requirement.

1.0 Technical Recommendations

Provide any recommended technical or development approaches that the Government should consider for this effort, based on the draft Statement of Need (SoN) (Appendix 2). Please provide feedback that helps clarify the SoN and helps ensure the Government meets the Fangorn program needs.

2.0 Potential Risks

Provide any potential risks that you foresee from the SoN and the potential prototype. Also provide any recommended risk mitigation approaches that the Government should consider for this effort. This includes any approaches the Government could be unaware of that would support an accelerated schedule to achieve the key features and technologies referenced above.

3.0 Acquisition and Other Recommendations

Provide any recommendations on the Government’s projected acquisition approach and any other relevant recommendations to help inform the Government.

4.0 Technical Capabilities

Describe your company’s and/or team’s ability to meet the SoN. Please include a discussion of potential new development options and the integration of COTS products, as appropriate.

5.0 Rough order of Magnitude (ROM) Cost

Provide a ROM for this effort. Please note that this is not considered a price proposal, nor will this ROM be held against a company that participates in any solicitation that relates to this program. ROMs received as part of this RFI will strictly be used for Government budgetary planning purposes only. A ROM Template is provided at Appendix 3; ROM submissions are not included in the total page count and may be submitted as part of, or as, a separate volume to the

White Paper RFI response.

APPENDIX 2: Statement of Need (SoN)

The subject of this SoN will replace the current IBM z in DISA’s J-9 while providing a central management plane between all customer hosted assets. It will standardize management of IBM z assets within the J-9 using agnostic supporting services. The subject product will provide a smoother entry into the environment as well as a much smoother transition from traditional hosting into commercial cloud. The product will include various add-on services that will boost its marketability and establish it as a competitive alternative to other hosting options.

Fangorn seeks to provide a first of its kind production Mainframe IBM z platform in the Cloud. Production Mainframe cloud offerings currently do not exist commercially, and current Mainframe solutions are NOT scalable with software and legacy customer requirements. DISA provides service offerings unlike typical large Mainframe users. Additionally, costly migrations and refactoring can disrupt the evolution of established applications. Fangorn is expected to offer a low-cost, low-risk alternative for traditional Mainframe applications to evolve at their own pace as application owners seek to meet their strategic goals towards cloud readiness.

DISA’s J-9 currently manages multiple IBM z hosting environments that are isolated and independent of one another. Each environment is unique, leverages different processes and hosts disparate applications with unique supporting software. To streamline management of these systems for both our customers and our administrators, the J-9 aims to develop a management plane that centralizes all current IBM z environments and capabilities with additional improvement capabilities and innovative processes, into a single centralized control plane.

Each environment has its own unique system software, configuration, administration, and access controls (including privileged access) resulting in cumbersome management process requirements. Additional requirements negatively impact management efficiencies and increase overall costs. Furthermore, adding more environments or additional software capabilities, can exponentially increase the complexity and administrative overhead, which is contrary to DISA’s goal to reduce cost and redundancy. These costs, management complexities, and burdensome issues associated with administering multiple standalone environments can be significantly reduced through the development and deployment of a centralized, customizable control plane paired with a standardized integrated hardware/software solution.

The Fangorn solution will contain an integrated application development suite to include all developer requirements for application modernization, stabilization, and maintenance. This includes Application Program Management, Code Analysis (including artificial intelligence (AI)), Automated testing, Debugging, Integrated Development Environment (IDE) software integration tools, Application Programming Interface (API) lifecycle manager, and Application performance tuning.

The intent is to provide a core zOS operating environment with optional database support software and all the associated infrastructure to run it. This will address the problems noted above through the following characteristics.

1. The prototype solution will allow for an integrated hardware and software as a service infrastructure. To include:

a) Mainframe CPU

b) Storage

c) Standard Software

d) Optional software bundles

2. The prototype solution will consist of a single software-as-a-service software solution for sustaining and modernizing mainframe z/OS applications.

a) Standard single software product solutions for z/OS Core Functions

b) Optional add-on database stacks for mission partners to consume, when applicable

c) Auxiliary development suites including code discovery, code explanation, code optimization, code translation, and analytics.

3. Provisioning and maintenance of the Operating Environments (OEs) will be built on Infrastructure as Code (IaC) to be leveraged by customers/administrators as part of an agile lifecycle. To be leveraged by the control plane or as part of a CI/CD pipeline for MP applications

4. The new infrastructure and control plane will provide a single pane of glass for all J-9’s IBM z environments.

The intent is to provide a single location from which customers/administrators can manage all their assets.

The new environment will have a central control plane for managing:

a) On-premises cloud environment

b) Commercial cloud assets

c) Containers

d) Traditional virtualized assets

e) Dedicated hosts

f) Networking

g) Backup/Disaster Recovery

h) Inventory/Configuration Management

i) Storage/Compute

5. The prototype solution will be distributed, hybrid and multi-cloud ready to support interaction from the on-premises control plane to commercial cloud service providers. The prototype solution is intended to allow DISA and its mission partners to be able to provision and manage instances in commercial cloud service provider environments, as well as on prem, in a single interface.

6. The prototype solution will include multi-tenancy support with full customer/account level segmentation.

Customers will be able to have all their assets in a single Virtual Datacenter (VDC), Virtual Private Cloud (VPC), or Virtual Cloud Network (VCN). The VDCs or VPCs will be fully segmented from one another and have their own virtual networking capabilities. Multi-tenancy capabilities will include the following:

a) Single management portal for each customer to their entire cloud environment

b) Single control plane representation of all customer assets in one place regardless of location or offering.

c) Customers are separated from each other and exist in isolated environments

d) Data is kept completely private and encrypted

e) Ability for infrastructure and tenant-controlled encryption keys with Virtualized Traditional Physical

Module (vTPM) encryption support

f) Network micro-segmentation capabilities

g) Built-in ability for tenants to analyze network traffic entering or exiting their space

h) Capability to monitor traffic inside the tenant boundary

i) Multi-tenancy of projects/customer control planes separated by Role Based Access Control

7. The prototype solution must be hosted on-premises in a consolidated standardized stack within DISA datacenters. The stack will be standardized and concise, making it ideal for replication when scaling, and used in CONUS and OCONUS locations.

8. The prototype solution will allow for the integration and removal of existing IBM z physical hardware into and out of the stack enabling integration, decommissioning, or provisioning of hardware.

9. The prototype solution will be constructed leveraging a Zero-Trust architecture from both network and identity perspectives.

10. The prototype solution will have a customizable central control plane for additional internal services/modules. Immediately upon implementation, the control plane will need to include portals for cyber, compliance, and IBM z infrastructure. The portal for the customizable central control plane also needs to be easily customizable and facilitate integration with various DISA services. The prototype solution needs to enable the addition of future portal capabilities. Additionally, the portal must be customizable to facilitate DISA branding and appropriate banners and markings.

11. Post prototype production environment integrations:

a) Be capable of eventual integration into DISA Enterprise Software Management software solutions.

12. The prototype solution will have Role-Based Access Controls (RBAC) to allow customers and administrators to properly assign permission sets. Roles will be fully customizable. Multifactor authentication and single sign-on must support Smart Card / Common Access Card / Personal Identity Verification Card authentication for portal and application access.

13. The prototype solution will have a Continuous Integration and Continuous Delivery (CI/CD) automation pipeline to handle various integration tasks such as deployments and scaling. This prototype solution shall leverage code-based CI/CD automation, which will execute seamlessly through the central control plane.

14. The prototype solution will provide interoperability with existing enterprise tools that are critical to the workload but must also include functionality to allow for the integration of new enterprise commercial tools as needed, such as ServiceNow and Splunk.

15. The prototype solution will have automated scalability connected to asset management systems for automated asset tracking alongside scaling. Provisioned assets will have lifecycle options available during the provisioning process allowing customers and systems administrators to assign an end-of-life date to the asset.

16. The prototype solution will have extensive integrated monitoring and alerting capabilities, such as:

a) Realtime insights

b) Alerting features (e.g., email and SMS messaging, alerts that trigger scripts or automation tasks)

c) Cloud-ready manner of monitoring assets/applications/containers/DBs/etc.

d) Infrastructure level monitoring and automated handling of events

17. The prototype solution will have a centralized portal for security posture. The security portal will be a part of the central control plane and will provide full spectrum security reports itemized by environment. The reporting capability will be accessible by customers for on demand generated reports regarding the posture of their environment.

18. The prototype solution will need to meet industry standard redundancy capabilities and include high availability implementations for resources.

19. The prototype solution will need an integrated backup capability that meets government backup requirements. The backup service must be agnostic and function across all asset types. Integrated file and image level backups are required for:

a) Virtual Tape

b) Virtual DASD

c) Independent disks

d) Network file storage

e) Storage attached networks

f) Object storage

20. The prototype solution will require a modern automation strategy that facilitates rapid deployment of the new environment, via both a user interface and as-code, while also facilitating a seamless tech refresh process for future upgrades.

21. The prototype solution will have a full disaster recovery and migration solution to allow agnostic migration capabilities. The disaster recovery capability will facilitate a seamless migration of IBM z environments. The disaster recovery solution will:

a) Be capable of disaster recovery to a specific snapshot in time

b) Include a containerized environment disaster recovery and migration capability

22. The prototype solution will have a full migration solution to allow migration of establish IBM z workload into

Fangorn. This migration process and capability will also allow a quick, easy transition of non z/OS assets from one hosting type to another within the solution. The migration solution will:

a) Be capable of asset migration from varying on-premises and cloud instances to Fangorn

b) Include a containerized environment disaster recovery and migration capability

c) Support migration of current IBM z environments to a new solution with minimal downtime and impact to mission

23. Co-located z/OS, Linux on z and container workloads

24. The prototype solution will have a billing portal to provide billing management capabilities to the program office as well as environment billing features for customers. The billing portal will include:

a) Full cost transparency for tenants

b) Reporting functionality

c) At-a-glance dashboards

d) Budgeting tools such as billing threshold alerts

e) Customer ability to place server orders in the portal and have servers provisioned via integrated automation

f) Consolidated billing view of both on-premises and public cloud assets

25. The prototype solution will include full OS patch management resources for all IBM z, Linux on z environments.

26. The prototype solution will have a capability that leverages artificial intelligence and machine learning (AI/ML) to traverse system and event logs to provide preventative resolutions and drastically reduce outage times by reducing the amount of troubleshooting required. The prototype solution will have AI/ML leveraged against cyber data. This will give the product the ability to identify exploited vulnerabilities through learned behaviors based on a constant in-depth analysis of events.

27. Provisioned assets should have lifecycle options available during the provisioning process allowing customers/admins to assign an end-of-life date to the asset.

28. Fully functional DevSecOps automation pipeline in place to handle the various requirements of the integrated solution. Deployments, scaling, and other integrated actions leveraging written DevSecOps pipeline style automation should happen seamlessly.

29. Elasticity - Ability to attach additional or remove existing physical hardware into the stack enabling integration, decommissioning, or provisioning.

30. The prototype solution will include solutions for elastic, block, and object storage alongside a solution to monitor and migrate storage, respectively.

31. Vendor will provide training to manage and operate the prototype solution.

Appendix 3: Rough Order of Magnitude (ROM) Template

Elements FY2025 FY2026 Grand Total Prime Vendor Labor [Insert Total Cost for

Prime Labor for Fiscal Year 2025]

[Insert Total Cost for Prime Labor for Fiscal Year 2026]

[Insert Total Cost for Prime Labor for Fiscal Year 2025-2026]

Sub – Vendor/Consultant Labor

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2026]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025-2026]

Material/Equipment [Insert Total Cost for Material/Equipment for Fiscal Year 2025]

[Insert Total Cost for Material/Equipment for Fiscal Year 2026]

[Insert Total Cost for Material/Equipment for Fiscal Year 2025-2026]

Other Direct Costs (ODCs)and/or Travel

[Insert Total Cost for ODCs for Fiscal Year 2025]

[Insert Total Cost for ODCs for Fiscal Year 2026]

[Insert Total Cost for ODCs for Fiscal Year 2025-2026]

SUBTOTAL [Insert Total Cost for Program/Project Management for Fiscal Year 2025]

[Insert Total Cost for Program/Project Management for Fiscal Year 2026]

[Insert Total Cost for Program/Project Management for Fiscal Year 2025-2026]

Concept Exploration Prime Vendor Labor [Insert Total Cost for

Prime Labor for Fiscal Year 2025]

[Insert Total Cost for Prime Labor for Fiscal Year 2026]

[Insert Total Cost for Prime Labor for Fiscal Year 2025-2026]

Sub – Vendor/Consultant Labor

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2026]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025-2026]

Material/Equipment [Insert Total Cost for Material/Equipment for Fiscal Year 2025]

[Insert Total Cost for Material/Equipment for Fiscal Year 2026]

[Insert Total Cost for Material/Equipment for Fiscal Year 2025-2026]

Other Direct Costs (ODCs)and/or Travel

[Insert Total Cost for ODCs for Fiscal Year 2025]

[Insert Total Cost for ODCs for Fiscal Year 2026]

[Insert Total Cost for ODCs for Fiscal Year 2025-2026]

SUBTOTAL [Insert Total Cost for Concept Exploration for Fiscal Year 2025]

[Insert Total Cost for Concept Exploration for Fiscal Year 2026]

[Insert Total Cost for Concept Exploration for Fiscal Year 2025-2026]

Design Prototype Prime Vendor Labor [Insert Total Cost for

Prime Labor for Fiscal Year 2025]

[Insert Total Cost for Prime Labor for Fiscal Year 2026]

[Insert Total Cost for Prime Labor for Fiscal Year 2025-2026]

Sub – Vendor/Consultant Labor

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2026]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025-2026]

Material/Equipment [Insert Total Cost for Material/Equipment for Fiscal Year 2025]

[Insert Total Cost for Material/Equipment for Fiscal Year 2026]

[Insert Total Cost for Material/Equipment for Fiscal Year 2025-2026]

Other Direct Costs (ODCs)and/or Travel

[Insert Total Cost for ODCs for Fiscal Year 2025]

[Insert Total Cost for ODCs for Fiscal Year 2026]

[Insert Total Cost for ODCs for Fiscal Year 2025-2026]

SUBTOTAL [Insert Total Cost for Design Prototype for Fiscal Year 2025]

[Insert Total Cost for Design Prototype for Fiscal Year 2026]

[Insert Total Cost for Design Prototype for Fiscal Year 2025-2026]

Test and Evaluation (T&E) Prime Vendor Labor [Insert Total Cost for

Prime Labor for Fiscal Year 2025]

[Insert Total Cost for Prime Labor for Fiscal Year 2026]

[Insert Total Cost for Prime Labor for Fiscal Year 2025-2026]

Sub – Vendor/Consultant Labor

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2026]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025-2026]

Material/Equipment [Insert Total Cost for Material/Equipment for Fiscal Year 2025]

[Insert Total Cost for Material/Equipment for Fiscal Year 2026]

[Insert Total Cost for Material/Equipment for Fiscal Year 2025-2026]

Other Direct Costs (ODCs)and/or Travel

[Insert Total Cost for ODCs for Fiscal Year 2025]

[Insert Total Cost for ODCs for Fiscal Year 2026]

[Insert Total Cost for ODCs for Fiscal Year 2025-2026]

SUBTOTAL [Insert Total Cost for T&E for Fiscal Year 2025]

[Insert Total Cost for T&E for Fiscal Year 2026]

[Insert Total Cost for T&E for Fiscal Year 2025-2026]

TOTAL ROM COSTS

Prime Vendor Labor [Insert Total Cost for

Prime Labor for Fiscal Year 2025]

[Insert Total Cost for Prime Labor for Fiscal Year 2026]

[Insert Total Cost for Prime Labor for Fiscal Year 2025-2026]

Sub – Vendor/Consultant Labor

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2026]

[Insert Total Cost for Sub- Vendor/Consultant Labor for Fiscal Year 2025-2026]

Material/Equipment [Insert Total Cost for Material/Equipment for Fiscal Year 2025]

[Insert Total Cost for Material/Equipment for Fiscal Year 2026]

[Insert Total Cost for Material/Equipment for Fiscal Year 2025-2026]

Other Direct Costs (ODCs)and/or Travel

[Insert Total Cost for ODCs for Fiscal Year 2025]

[Insert Total Cost for ODCs for Fiscal Year 2026]

[Insert Total Cost for ODCs for Fiscal Year 2025-2026]

TOTAL [Insert Total Cost of All Elements for Fiscal Year 2025]

[Insert Total Cost of All Elements for Fiscal Year 2026]

[Insert Total Cost of All Elements for Fiscal Year 2025-2026]

The Government does not require supporting data to justify the estimated costs or prices (e.g. copies of commercial/market price lists/rates, price history, support prime vendor and subvendor quotes, invoices) provided as part of this RFI White Paper response. The completed ROM template should be submitted with the RFI White Paper response.

This ROM is requested in support of Market Intelligence/Research. The Government will not provide response to questions related to an anticipated budget for this prototype effort. No budget has been established at present as market research supports budgetary planning activities.

Fiscal Year 2025: October 1, 2024, through September 30, 2025

Fiscal Year 2026: October 1, 2025, through September 30, 2026