Area of Interest (AOI): Expeditionary Very Low Frequency (ExVLF) Transmitter System
PAO Release Number: NAVWAR HQCA-2026-A-071
Notice ID: N0003926RB004

Notice to Industry: This is an AOI issued under Naval Information Warfare Systems Command (NAVWAR) Commercial Solutions Opening (CSO) number N0003925S0001. This AOI solicits white papers/solution briefs (Phase 1 of the CSO) from industry. To the extent that any implementing regulations have not been updated to reflect statutory changes, the terms of the statute shall govern.

Responses Due: 13-AUG-2026 at 2:00 PM PDT

Questions Due: 28-JUL-2026 at 2:00 PM PDT

The Government may not address all questions received. Questions and Answers will be posted on the NAVWAR CSO Website: https://www.navwar.navy.mil/Work-With-Us/Open-CSO-Calls/

Contact information for questions and technical/submission issues: ian.m.robinson14.civ@us.navy.mil
 

Background:

The Expeditionary Very Low Frequency (ExVLF) communications system is a modular, relocatable communications suite supported by an aerostat-lofted tethered antenna that enables 24/7 VLF radio wave data broadcasts over distance to maritime mobile and shore-based receive nodes.
 

Problem Statement

The US Navy seeks solutions for an Expeditionary Very Low Frequency (ExVLF) transmitter system. The Navy requires a high-reliability solution that supports 24-hour per day, 7-day per week (24/7) data broadcast operations. As a result of this AOI, it is anticipated that initial efforts will focus on a prototype delivery phase, with potential options for follow-on production units to satisfy long-term operational inventory objectives. The system must be designed for deployment in rugged, multi-environment locations and integrate with Government-Furnished Equipment (GFE).

Primary Solution Attributes:

• High-Power Performance and Tuning: A containerized VLF transmitter system, consisting of a power amplification subsystem and a dynamic and automatic tuning element subsystem, designed to generate and radiate RF power by integrating with and automatically tuning to the specific complex impedance characteristics of a government-furnished Wireless Communications Aerostat (WCA) tethered antenna.
• Integrated Transmitter System: The entire transmitter system must be housed within a no greater than 20-foot ISO general-purpose freight container to ensure it is transportable, deployable, and relocatable in diverse environments. The assembly must be hardened for deployment in rugged environments and include all necessary subsystems for operation.
• Modulator and Signal Generation: An integrated subsystem to generate the required VLF waveforms. All signal characteristics, including modulation formats, reference frequency accuracy, and timing, must be sufficient to meet the top-level requirements of the ExVLF data broadcast mission.
• Control and Monitoring System: A unified control system for local and remote operation of the transmitter. It should provide status monitoring, fault detection, and the ability to interface with the overarching ExVLF network command and control structure.
• Mast and Feedline System: A deployable mast and feedline to provide the RF connection from the transmitter to the WCA mooring station.
• Ground Plane System: A deployable ground plane system to ensure efficient RF radiation from the antenna system.
• Interoperability: The system must be made interoperable with GFE, including a prepared flight pad, the WCA system, communications equipment, site logistics vehicles, and site power.

Desired Solution Attributes:

• Mobile Power Delivery System (MPDS): The MPDS provides the necessary operational power to the WCA (excluding transmission RF power).  The Government seeks a full spectrum of solutions, both with and without an integrated MPDS. Additionally, we welcome proposals for a separately priced MPDS option. The MPDS shall provide power based on the aerostat vendors requirements; it shall function with or without RF power being transmitted; it shall fit within the primary transmitter equipment International Organization for Standardization (ISO) container; and it shall draw its prime power from the primary transmitter power distribution unit (PDU) or an external PDU.
• Next-Generation Transmitter Technology: Implement modern, efficient, and agile transmitter designs that offer greater efficiency, reliability, flexibility, or ease of control than legacy transmitters.
• Smarter Station Control and Automation: Artificial Intelligence and machine learning for predictive maintenance, automatic tuning, or dynamic adjustments based on environmental conditions.
• Hardening and Resiliency: While the VLF transmitter must be resilient to natural events (e.g., lightning, severe thunderstorms, and earthquakes), new materials, technologies and methodologies could enhance robustness, prevent system damage, and reduce the impact on transmitter operations by enabling it to continue broadcasting throughout an event. Measures must also be taken to guard against manmade events (such as cyberattacks or operator error) through hardening and other protective features.
• Enhanced Maintainability: Modern maintenance tools such as AI/ML based predictive maintenance, Built-In Test (BIT), self-healing software, autonomous component failover, and hot-swap components can dramatically reduce the maintenance burden on system maintainers, minimize site downtime, and optimize utilization of spare parts. Steps should be taken to reduce the maintenance burden on transmitter maintainers.
• Technical Data and Supportability: Successful long-term sustainment necessitates availability and access to detailed system technical manuals, drawings and parts lists, training, technical support, and spare parts for the life of the system.  Transmitter sustainment and supportability should be considered. Immersive training tools such as augmented reality and digital twins can be used to enhance the training experience operators and maintainers receive, enhancing their ability to sustain the system.

 Additional Notes:
 

• Cybersecurity: Cybersecurity and Information Assurance best practices must be implemented and strictly adhered to.  Measures must also be taken to protect the supply chain from malicious and/or counterfeit software and hardware components to ensure safe, secure, and reliable operation of the system.

 

• Security: Companies must have experience deploying on classified networks and ability to perform work in these environments and cleared personnel who can work up to TS/SCI. It is encouraged that submissions highlight experience with controlled environments, such as deployments in classified data/environments (https://public.cyber.mil/dccs/). Preference will be given to companies whose solutions can be deployed to meet DoD security standards, or have an equivalent Authority to Operate (ATO).

 

• Demonstration: Companies are expected to describe how their solution will meet Government requirements via a presentation in an unclassified environment as part of Phase 2 of the CSO AOI.
  • Technical Viability: Explaining exactly how your commercial technology solves the governments specific mission problem.
  • Rough Order of Magnitude (ROM): Providing a high-level, preliminary cost estimate and commercial pricing model.
  • Project Schedule: Presenting a notional timeline and key milestones for the prototyping phase.
  • Data Rights and IP: Asserting your companys positions on intellectual property, data rights, and software licensing.
  • Live QandA / Demonstration: Evaluators will ask questions to your technical team on potential bottlenecks.

 

• Teaming: The Government may seek to team companies with complementary solutions under the umbrella of this AOI; or in coupling of other AOIs issued within NAVWAR. Selected vendors may be requested to engage in partnerships with other vendors to achieve Government objectives.

 

• Prototype Projects: The Government is interested in mature commercial technologies, as well as prototype efforts. A Prototype Project is defined at 10 USC 4022(e)(5) as a project that addresses: (A) a proof of concept, model, or process, including a business process; (B) reverse engineering to address obsolescence; (C) a pilot or novel application of commercial technologies for defense purposes; (D) agile development activity; (E) the creation, design, development, or demonstration of operational utility; or (F) any combination of subparagraphs (A) through (E).

Awarding Instrument:

This solicitation will be awarded in accordance with the NAVWAR CSO process detailed within N00039-25-S-0001 (NAVWAR CSO), posted to SAM.gov on 4 JUN 2025. This document can be found at: https://sam.gov/opp/a606b587755240e1a0b4f7d1e8d557bc/view

Please refer to NAVWAR CSO for additional information regarding the three-phase process:
Phase 1: Solution Briefs
Phase 2: Pitch Session
Phase 3: Proposal

Vendors are reminded that in order to utilize an Other Transaction (OT) agreement the requirements of 10 USC 4022(d) must be satisfied:

1. 1. There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.
   2. All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.
   3. At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.
   4. The senior procurement executive for the agency determines in writing that exceptional circumstances justify the use of a transaction that provides for innovative business arrangements or structures that would not be feasible or appropriate under a contract, or would provide an opportunity to expand the defense supply base in a manner that would not be practical or feasible under a contract.

Any resulting agreement from this solicitation will include language requiring your company to confirm compliance with Section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232). If you are unable to confirm compliance with the referenced law, the Government will not be able to enter into an agreement with your company.

Potential Follow-On Contract or Agreements

Companies are advised that any Other Transaction (OT) agreement for Prototype awarded in response to this solicitation may result in the direct award of a follow-on production contract or agreement without the use of further competitive procedures.

The follow-on production contract or agreement will be available for use by one or more organizations within the Department of Defense.  As a result, the magnitude of the follow-on production contract or agreement could be significantly larger than that of the Prototype OT agreement.  All Prototype OT agreements will include the following statement relative to the potential for follow-on production: In accordance with 10 U.S.C. § 4022(f), and upon a determination that the prototype project for this transaction has successfully been completed, this competitively awarded Prototype OT agreement may result in the award of a follow-on production contract or transaction without the use of competitive procedures.

Response Instructions

Per the N0003925S0001 NAVWAR CSO announcement, vendors interested in responding to this AOI are invited to submit Phase 1 Solution Briefs. Solution Briefs shall not exceed five (5) written pages using 12-point font or, alternatively, Solution Briefs may take the form of briefing slides which shall not exceed fifteen (15).

Title Page (does not count against page limit)

Company Name, Title, Date, Point of Contact Name, E-Mail Address, Phone, Address, CAGE (if available). Specifically identify the AOI for which the Solution Brief is submitted.

Executive Summary (one page limit, included in five (5) page limit)

Provide an executive summary of the technology.

Technology Concept

Describe the unique aspects of your technology and the proposed work as it relates to the AOI. Identify whether the effort includes the pilot or demonstration of existing commercial technology (identified as commercially ready and viable technology), or the development of technology for potential defense application. If development or adaptation is proposed, identify a suggested path to mature the technology. Identify aspects which may be considered proprietary.

Company Viability

Provide a brief overview of the Company. Provide a summary of current fundraising to date or a summary of the top line (gross sales/revenues). Provide a summary of product commercialization and go-to-market strategy. Self-Identify as Traditional or Non-Traditional Defense Contractor as defined in 10 USC 3014. Identify planned teaming arrangements, joint ventures, and/or associate contractor agreements (ACAs).


Recommended Award Type

Companies shall recommend an award type to be considered for the effort (FAR-based Procurement Contract or OTA). Should the Company be asked to submit a Proposal in Phase 3, the Government and Company will further negotiate the best type of award for the effort.

Markings in accordance with N0003925S001 2.3.1.6

All solution briefs containing data that is not to be disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall include the following statement on the cover page of the submission:
This Solution Brief includes data that shall not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this submission. If, however, an agreement/contract is awarded to this Company as a result of -- or in connection with – the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent agreed upon by both parties in the resulting agreement. This restriction does not limit the Governments right to use the information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets].

Each restricted data sheet should be marked as follows:
Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.


Submission Instructions

Vendors interested in submitting a response to this AOI must submit their solution brief via the Procurement Integrated Enterprise Environment (PIEE) Solicitation module link provided in this posting.  The Government will not accept emailed submissions. If you have any questions regarding submission you may contact the Government point of contact identified in the SAM.gov posting/notice. The Government will not pay respondents for the costs associated with the submission of white paper/solution briefs.
 

PIEE N00039-26-R-B004 public posting link:  

https://piee.eb.mil/sol/xhtml/unauth/search/oppMgmtLink.xhtml?noticeId=N0003926RB004&noticeType=SolicitationNotice

 

SAM.gov N00039-26-R-B004 posting link:

https://sam.gov/workspace/contract/opp/7ec8b411aa67494e8c357770c594dcad/view

---

Program Acquisition Executive (PAE),
Mission Systems (MS), Program Executive Office Digital
Area of Interest (AOI):
Cyber Resource and Engineering Workforce (CREW)

Distribution A – Approved for public release; distribution is unlimited. Notice ID#: N0003926RH002

Amendment 1 incorporates the following changes: Notice to Industry: This is an Area of Interest (AOI) issued under Naval Information Warfare Systems Command (NAVWAR) Commercial Solutions Opening (CSO) number N0003925S0001. This AOI solicits white papers/solution briefs (phase 1 of CSO) from industry. This is not a formal solicitation or request for proposals.

Responses due: 6 July 2026 at 12:00 PM Eastern Daylight Time (EDT)
Questions due: 25 June 2026 at 2:00 PM PDT

The Government may not address all questions received. Questions and Answers will be posted on NAVWAR CSO Website: https://www.navwar.navy.mil/Work-With-Us/Open-CSO-Calls/. Please see section VIII for posted questions and answers below.
Contact information for questions and technical/submission issues: NAVWAR_2.7_CSO@us.navy.mil
The Government will not pay respondents for the costs associated with the submission of white paper/solution briefs.

• I. Current State

The Department of the Navy (DON) is transforming its approach to Information Technology (IT) services to better align with industry and commercial standards, to include staff augmentation.
Currently PEO Digital has multiple contracts, task orders, and interagency agreements that include augmented labor support with over 100 different Labor Categories (LCATS). These contracts have varying product service codes, North American Industry Classification System (NAICS), disjointed scopes of work, and are cumbersome to administer. This antiquated business model does not align with our Agile SAFe® operating construct nor the future-state Government-Owned, Government Operated, Contractor Supported (GOGO-CS) approach to managing IT for the Navy. Modern Service Delivery requires us to fundamentally reform our approach to acquisition and establish a “Talent Supply Chain” bench of available resources.
In 2024 the DoD Cyber Workforce Framework was codified (via DODD 8140.01, DODI 8140.02, and DODM 8140.03) as the authoritative lexicon based on the work an individual is performing, not a certification or job series – across Military, Civilian, and Contracted labor. This enables a holistic approach to workforce talent management with improved fidelity. A qualified DoD cyber workforce, including cyber enablers, will be better prepared to defeat highly sophisticated cyber adversaries and attract, recruit, and retain the best and brightest individuals by providing opportunities for growth in an environment of unique missions.
PEO Digital is an early Government implementer of the Technology Business Management (TBM) framework (see section 8, Helpful Links). TBM provides a standardized taxonomy for ends (solutions), ways (towers) and means (cost pools). PEO Digital organizationally operates in alignment with the TBM and Defense Cyber Workforce Framework (DCWF) (see section 8, Helpful Links) to maximize optimization of consistent agility and flexibility aligned with mission needs of the DON.
PEO Digital is revolutionizing the procurement of IT labor support using the DCWF and the TBM domains, towers and cost pools to develop an orderable and decentralized catalog of firm fixed price (FFP) support as the desired end state of this AOI.
The scope of this AOI is for PEO Digital, including CONUS, OCONUS, and USMC, with potential future expansion. PAE MS, through PEO Digital’s portfolio of the Naval Enterprise Network (NEN) and Marine Corp Enterprise Network (MCEN) is aligning with our acquisition strategy and contract execution starting with CREW to enhance operational effectiveness and empower capabilities through targeted investments and collaborative arrangements.

• II. Problem Statement

The Government is seeking an agile, standardized, and modern approach to augment our cyber workforce with commercially sourced talent.  This modern approach provides the ability to fully adapt to the agile nature of software intensive programs or wartime readiness.
Current solutions have difficulty classifying resources; managing finances and technical investment across the workforce; maintaining, shifting, and adapting a highly skilled workforce in response to government needs; and preserving the predictability of access to highly skilled talent, budget, work and network resources that are necessary to sustain efforts for both the government and industry. As labor needs fluctuate across various programs and projects, current procurement processes often lack the flexibility, efficiency, and responsiveness required to meet evolving demands.

Key Challenges

1. Workforce Framework Alignment
   Achieving comprehensive integration and alignment of DCWF work roles with TBM Domains, Towers, and Staffing Cost Pools to standardize workforce categorization and financial tracking.
2. Scalable Talent Supply Chain
   Mitigating risks to operational agility and mission success by developing a highly scalable, continuous talent supply chain and readiness reserve capable of immediately executing rapid sprint and surge operations to further streamline and enhance operational support for DON.
3. Accelerated Onboarding
   Aligning staffing and onboarding velocity with the rapid pace of agile operational demands, ensuring administrative processes are optimized to support sudden surge requirements without degrading mission momentum.
4. Optimized Contracting Framework
   Establishing adaptable, scalable contract vehicles to efficiently procure Firm-Fixed-Price (FFP) support labor across variable durations—ranging from short-term agile cycles (e.g., two-week sprints) to long-term engagements.
5. Stakeholder Accessibility
   Enabling PEO Digital stakeholders and customers to seamlessly access and leverage contracted support labor.

3. Desired Solution

PEO Digital is seeking a flexible, scalable, and cost-effective solution that aligns with the TBM framework and integrates DCWF labor categories within the TBM Domains/Towers and cost pools. The Government's priorities for 2026 include engineering and logistics.
This initial minimum viable product (MVP) is focused on piloting a fundamentally new way of how the DON acquires, deploys, and manages its talent, by establishing a Firm Fixed Price (FFP) catalog using DCWF labor categories.
Desired Solution Characteristics:
Compelling submissions will provide actionable, vendor-driven methodologies addressing the following:

1. Workforce Framework Alignment
   Explicit mapping of the vendor’s supported DCWF work roles to their corresponding DCWF elements (e.g., IT Element: Knowledge Manager [431], Network Operations Specialist [441]). Responses must also align the vendor's core competencies with specific TBM Domains and Towers.

 

2. Scalable Talent Supply Chain
   Using response to number 1, Workforce Framework Alignment, a comprehensive approach to establishing and maintaining a dynamic, DCWF-aligned talent supply chain focused on the vendor's identified Elements and Work Roles. This must include concrete strategies for rapidly scaling personnel volume up or down in response to fluctuating Government demand.

The capability and proposed methodology to rapidly expand or diversify the mix of supplied work roles beyond the vendor's initial core competencies to support evolving and dynamic mission requirements.
 

3. Accelerated Onboarding
   Vendor-driven methodologies to expedite personnel deployment  to further streamline and enhance operational support for DON. Solutions must explicitly outline the onboarding process, accelerated timelines, describe the associated methodology, and identify any necessary Government dependencies.

 Note: The Government may consider proposed compensation or incentive structures tied to maintaining this level of operational readiness.
 

4. Optimized Contracting Frameworks
   Recommendations for the most effective and flexible contracting strategies, vehicles (see NAVWAR CSO, Section 2.2), or structures required to successfully enable and execute the proposed solutions.

 

5. Stakeholder Accessibility

A recommendation for enabling stakeholders and customers to seamlessly access, task, and leverage contracted support labor.

6. Demonstrated Capability
   Where applicable, a summary of relevant previous experience demonstrating the vendor's ability to successfully meet the scale and specific operational demands outlined in AOI.

ASSUMPTIONS:

1. Fluctuating Resource Utilization: Operational demand will be variable, and there may be intermittent periods or gaps between agile sprints where specific personnel or work roles are not actively required.
2. Pre-Existing Access Requirements: Traditional recruiting and clearing timelines are incompatible with the accelerated onboarding KPI of days not weeks. Therefore, the Government assumes successful solutions will primarily rely on personnel who already possess the necessary credentials.

 

4. Submission Instruction

Solution materials must be submitted electronically via the Procurement Integrated Enterprise Environment (PIEE) solicitation module link no later than the deadline specified in this announcement (Procurement Integrated Enterprise Environment (PIEE): https://piee.eb.mil/).
Solution white papers shall include the following:

• Solution White Papers, when printed, shall not exceed five (5) pages using 11-point font Times New Roman, 1-inch margins, exclusive of Title page
• Title page. Identify the AOI for which the solution white paper is submitted
  • Company Information
    • Company name,
    • Address,
    • Point of contact name, e-mail, and phone number
    • CAGE, if available
    • Self-Identify as Traditional or Non-Traditional Defense Contractor as defined in 10 USC 3014.
    • Company Viability as defined in N0003925S001 2.3.2
• Address the problem and desired solution
• Identify planned teaming arrangements, joint ventures, and/or associate contractor agreements (ACAs)
• If suggesting an OTA, and you’re a traditional defense contractor please identify the significant contribution to be provided on your team by a non-traditional defense contractor.
• Marked in accordance with N0003925S001 2.3.1.6
  • All solution briefs containing data that is not to be disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall include the following statement on the cover page of the submission:
    • This Solution Brief includes data that shall not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this submission. If, however, an agreement/contract is awarded to this Company as a result of -- or in connection with – the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent agreed upon by both parties in the resulting agreement. This restriction does not limit the Government's right to use the information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets].

 

• V. Evaluation Criteria

Solution white papers will be peer-reviewed by the Government technical review team in accordance with CSO N0003925S0001, DFARS 212.70 and 10 USC 3458.
Evaluation criteria are:

1. To what degree does the solution meet the needs of the Department of the Navy
2. Technical merit and feasibility of solution(s) to address the Government’s problem statement

Criteria are equally weighted.
 

6. Notional Schedule

Milestone	Planned Date*
Invite to Phase 2, Pitch Sessions	4th Quarter FY2026
Initial Performance commences	1st Quarter FY2027

*Milestone dates are subject to change

Note: please refer to NAVWAR CSO for additional information regarding the three-phase process:
Phase 1: Solution Briefs
Phase 2: Pitch Session
Phase 3: Proposal

7. Award information

This AOI is issued under the authority of 10 U.S.C. § 3458, as amended by the National Defense Authorization Act for Fiscal Year 2026. This authority permits the acquisition of commercial products, commercial services, or non-developmental items, and is not limited to 'innovative' solutions. To the extent that any implementing regulations have not been updated to reflect this statutory change, the terms of the statute shall govern.
Any contract or agreement as a result of this AOI is to be for non-personal services. There are no waivers to the personal services prohibition. Therefore, the solution shall focus on capability, responsiveness, and outcomes. The contractor is solely responsible for the management, performance, and conduct of its personnel.
Notice to Respondents:

1. The Government reserves the right to cancel this requirement at any time and is under no obligation to reimburse any associated costs. Multiple awards are anticipated over the lifecycle of this AoI.
2. Solutions shall be valid for a minimum of 18 months.
3. Awardable solutions may be made available in the Navy’s Digital Marketplace.
4. Respondents providing awardable solutions may be asked to provide a five-minute video pitching their solution for inclusion in the marketplace.
5. All awards are subject to the availability of funds.
6. Collaborative real-time work statement development is anticipated prior to RFQ/RFS

8. Helpful Links

• NAVWAR CSO Website: https://www.navwar.navy.mil/Work-With-Us/Open-CSO-Calls/
• Procurement Integrated Enterprise Environment (PIEE): https://piee.eb.mil/
• PIEE public URL for this AOI:

https://piee.eb.mil/sol/xhtml/unauth/search/oppMgmtLink.xhtml?noticeId=N0003926RH002&noticeType=SolicitationNotice

• System for Award Management (SAM) public URL for this AOI:

https://sam.gov/workspace/contract/opp/0e829148497b4903bf23e840d860f666/view

• Defense Cyber Workforce Framework (DCWF): https://www.cyber.mil/dod-workforce-innovation-directorate/dod-cyber-workforce-framework/dcwf
• Technology Business Management (TBM) Taxonomy: https://www.tbmcouncil.org/learn-tbm/resource-center/the-tbm-taxonomy-5/
• Navy Cyberspace Framework (COOL): https://www.cool.osd.mil/usn/cswf/index.html?CWFModel

---

Area of Interest (AOI) issued under NAVWAR CSO N0003925S0001

AOI Title: Information and Communications Technology (ICT) for Unmanned Surface Vessels (USV)

Response Due Date: 14 May 2026 at 2:00 PM Pacific Daylight Time (PDT)
This is an Area of Interest (AOI) issued under NAVWAR CSO N0003925S0001, posted to SAM.gov. This AOI solicits white papers/solution briefs from industry to inform market research, capability assessment, and potential follow-on prototyping or acquisition. This is not a formal solicitation or request for proposals. The Government will not reimburse respondents for any costs associated with submission or participation. The Government reserves the right to cancel, modify, or not pursue any efforts under this AOI.

IMPORTANT: For the full text AOI and Solicitation Guidance reference the Procurement Integrated Enterprise Environment (PIEE) solicitation module at https://piee.eb.mil/sol/xhtml/unauth/search/oppMgmtLink.xhtml?noticeId=N0003926RA005&noticeType=SolicitationNotice to download:

• NAVWAR HQCA-2026-A-032_AOI_USV_ICT_01Apr2026_final.pdf
• NAVWAR HQCA-2026-A-031_AOI_ICT_Solicitation_Guidance_02Apr2026_final.pdf

1.0 Introduction
The Naval Warfare Systems Command (NAVWAR), in support of the Program Executive Office (PEO) C4I, is seeking commercial solutions for an end-to-end Information and Communications Technology (ICT) solution that will be integrated on an Unmanned Surface Vessel (USV). The Navy is seeking to identify and evaluate existing, new, and emerging technologies that can accelerate the delivery of a fully integrated, end-to-end communications solution that enables Unmanned (UxS) C2 across all classification levels and enhances the transport of classified data over multiple non-sovereign networks.

2.0 Problem Statement
The Navy requires an Information and Communications Technology (ICT) system for Unmanned Surface Vessels (USVs) to support the Navy’s Distributed Maritime Operations (DMO) concept. The goal of DMO is to distribute the force over a wide area, creating a more resilient and difficult-to-target fleet. USVs are a key component of this strategy, but they require a robust and reliable ICT system to enable Command and Control (C2) across various classification levels and enhance end-to-end classified communications for unmanned platforms. The current state of ICT for USVs is a collection of disparate systems that are not well-integrated, making it difficult to achieve the desired level of C2. This AOI seeks to identify solutions that can provide a fully integrated, end-to-end ICT solution for USVs.

3.0 Submission Instructions

• Submit electronically via email to designated Agreements Officers via email Brian Griffin (brian.d.griffin.civ@us.navy.mil) or Lynette Brewer (lynette.m.brewer.civ@us.navy.mil)
• PIEE Public Posting URL: https://piee.eb.mil/sol/xhtml/unauth/search/oppMgmtLink.xhtml?noticeId=N0003926RA005&noticeType=SolicitationNotice

• SAM.gov Public Posting URL:

https://sam.gov/workspace/contract/opp/aeaa137a2b584dd187c4428b2d6f84da/view

• Submissions sent through other channels or after the Phase 1 White Paper period has ended will not be reviewed nor evaluated.

4.0 Helpful Links & Contact Information

• NAVWAR Home Page: https://www.navwar.navy.mil/
• NAVWAR Office of Small Business Programs: https://www.navwar.navy.mil/o/NAVWAR/Pages/Office-of-Small-Business-Programs.aspx
• NAVWAR CSO Page: https://www.navwar.navy.mil/Business-Partnerships/Commercial-Solutions-Opening-CSO/
• SAM.gov: https://www.sam.gov/
• PIEE: https://piee.eb.mil/
• For submission/technical issues, contact designated Agreements Officers via email Brian Griffin (brian.d.griffin.civ@us.navy.mil) or Lynette Brewer (lynette.m.brewer.civ@us.navy.mil)

---

 

Naval Warfare Systems Command (NAVWAR)
Commercial Solutions Opening (CSO)
N0003926RE011
(HQCA-2026-A-028)

Area of Interest (AOI): Enterprise Scheduling Tool Replacement for Project Online Retirement
 
NOTICE to Industry: This is an Area of Interest (AOI) issued under NAVWAR CSO N0003925S0001, posted to SAM.gov. This AOI solicits white papers/solution briefs from industry to inform market research, capability assessment, and potential follow-on prototyping or acquisition. This is not a formal solicitation or request for proposals. The Government will not reimburse respondents for any costs associated with submission or participation. The Government reserves the right to cancel, modify, or not pursue any efforts under this AOI.

Responses to this AOI are due no later than 30 April 2026 at 2:00 PM. Submit via the Procurement Integrated Enterprise Environment (PIEE) solicitation module or via email NAVWAR_2.4_CSO@us.navy.mil.

1. Introduction Microsoft Project Online, supporting a large user base and significant schedule volume for key program and portfolio schedules, is scheduled to retire on or around Spring 2027. 

These schedules support program visibility and data-driven decision support.

This AOI seeks innovative commercial solutions to replace and enhance these capabilities, while supporting standardization across participating organizations.

2. Problem Statement

• Loss of integrated real-time dashboards and visualization
• Multiple enterprise instances supporting a large user base and significant schedule volume
• Current processes are distributed across multiple environments with varying levels of integration
• Transition approach should support continuity of operations

3. Desired Solution NAVWAR seeks commercial, off-the-shelf (COTS) or configurable enterprise scheduling/Project Portfolio Management (PPM) solutions that are compatible with enterprise cloud and secure environments. Solutions should support full migration from Microsoft Project Online (e.g., .mpp imports) and preserve/enhance key functionalities.

Required Features:

• Critical Path Method (CPM) scheduling
• Enterprise calendars and custom fields
• Gantt chart views
• Robust permissions and security controls
• Comprehensive reporting capabilities
• Resource loading and management

Desired Features:

• Third-party connectors
• Migration assistance tools/services
• Integration with common enterprise collaboration, development, and analytics platforms
• Cloud-based dashboards
• Project Portfolio Management (PPM) functionality
• Resource Breakdown Structure (RBS)
• Integrated risk management
• What-if scenario planning

Stretch Features:

• Advanced analytics and automation capabilities (optional)
• Schedule health analytics
• Schedule risk assessment tools
• Support for higher security environments, as applicable

4. Evaluation Criteria (Phase 1 Solution Briefs)

1. Technical: Thoroughness and feasibility of addressing required/desired/stretch features; approach to migrating existing data and users; compatibility with enterprise could and secure environments.
2. Innovation: Demonstration of enhanced capabilities (e.g., AI, real-time analytics) beyond current Project Online.
3. Experience: Relevant deployments in government/defense/large enterprises, especially migrations from Microsoft Project.
4. Business Viability: Company overview, commercialization path, recommended award type (e.g., Prototype OTA, FAR Part 12 contract).
5. Cost Realism: Rough Order of Magnitude (ROM) pricing and value proposition.

5. Awarding Instrument Potential awards under this AOI may include:

• Prototype Other Transaction Agreement (OTA) pursuant to 10 U.S.C. § 4022
• Commercial contract under FAR Part 12
• Other innovative arrangements as appropriate

Successful Phase 1 respondents may be invited to Phase 2 (Pitch Session) and/or Phase 3 (Full Proposal) per the CSO process. Successful prototypes may lead to follow-on production without re-competition.

6. Submission Instructions Submit electronically via the Procurement Integrated Enterprise Environment (PIEE) solicitation module or via email NAVWAR_2.4_CSO@us.navy.mil.
Solution Briefs/White Papers should not exceed five written pages (12-point font) or 15 briefing slides. Include (not counting against limit):

• Title page (AOI title, company name, POC, date)
• Executive Summary (1-page limit)
• Technology/Solution Concept and alignment to features
• Migration/Implementation estimated onboarding timeline for enterprise users
• Company Viability and Experience
• Recommended Award Type with ROM pricing
• Any proprietary aspects

Submissions after the deadline will not be considered.
PIEE Public Posting URL: https://piee.eb.mil/sol/xhtml/unauth/search/oppMgmtLink.xhtml?noticeId=N0003926RE011¬iceType=SolicitationNotice
SAM.gov Public Posting URL:
https://sam.gov/workspace/contract/opp/f7af84b4f3834961b1812b5156e2082b/view

7. Helpful Links

• NAVWAR CSO Website: https://www.navwar.navy.mil/Work-With-Us/Open-CSO-Calls/
• NAVWAR Contracting Digital Resource Guide: https://www.navwar.navy.mil/Work-With-Us/NAVWAR-Contracting-Digital-Resource-Guide/
• PIEE Registration/Guides: https://piee.eb.mil
• SAM.gov (for baseline CSO): https://sam.gov
• NAVWAR F.A.Q.: https://www.navwar.navy.mil/Work-With-Us/FAQ/

For submission/technical issues, contact the designated Agreements/Contracting Officer via PIEE or via email at NAVWAR_2.4_CSO@us.navy.mil.
 

---