OSW27BZ02-DV005: Resilient Tactical Edge Networks

Part of the DoW SBIR/STTR FY27 Release 2 topic list. Browse all 83 topics by industry or service.

Topic OSW27BZ02-DV005 from the DoW SBIR 2027 BAA, Release 2. Pre-release now; proposals due January 6, 2027, 12:00 PM ET.

Quick answer

OSW27BZ02-DV005 is an Office of the Secretary of War SBIR topic seeking a fully open-source private 5G network built from OCUDU, SD-Core, SD-RAN, and OSC components, validated at a representative rural site for precision agriculture and dual-use DoW applications. It accepts Direct-to-Phase II proposals only, with an 18-month period of performance. Proposals are due January 6, 2027, 12:00 PM ET.

Book a Free Fit Call

Solicitation at a glance

• Topic number: OSW27BZ02-DV005
• Official title: Resilient Tactical Edge Networks
• Agency: Office of the Secretary of War
• Program: SBIR (DoW SBIR 2027 BAA, Release 2)
• Award type: Direct to Phase II (no Phase I awards)
• Award amount: Not yet posted. OSW component instructions not available in DSIP as of Nov 5, 2026.
• CMMC level: Level 2 (Self)
• ITAR: No
• Technology areas: Information Systems
• Pre-release (direct TPOC contact allowed): November 4 to December 2, 2026, 8:00 AM ET
• Opens in DSIP: December 2, 2026, 8:00 AM ET
• Proposals due: January 6, 2027, 12:00 PM ET
• Official source: DSIP Topics app (search OSW27BZ02-DV005)

BW&CO's take

What the Office of the Secretary of War wants

The Government wants proof that an all-open-source private 5G stack can deliver reliable, wide-area coverage where carrier networks do not, using agriculture as the test case. Phase II delivers a working MVP integrating OCUDU, SD-Core, SD-RAN, and OSC with no proprietary core, RIC, or SMO, using physical radio units and devices. It must address at least two of four use cases (autonomous field equipment, UAS and sensor backhaul, livestock monitoring, connected farmstead and irrigation) at a rural site you secure (an operating farm or ranch, an agricultural research facility, or a comparable rural environment, in that order of preference). Mobility and coverage metrics must be validated with instrumented vehicles on real radio signals, and at least one security capability must be shown live.

Who is a good fit

• Hands-on integration of open-source 5G components such as OCUDU, SD-Core, SD-RAN, and OSC, including the 7.2x split to third-party radio units
• CBRS deployment experience, especially high-power Category B radios and long-range outdoor RF planning
• Access to an operating farm, ranch, or agricultural research facility for field demonstrations
• Experience with 5G network slicing, RedCap devices, or OCUDU scheduler work that can be contributed upstream

Watch-outs

• This is Direct-to-Phase II only. You must submit feasibility documentation such as test data, technical reports, prototype designs, or prior project outcomes showing Phase I-type work is complete.
• The stack must be fully open source with no proprietary core, RIC, or SMO components, and the MVP must use physical RUs and UEs. Mobility and coverage KPMs require instrumented vehicles at operational speeds.
• The Technical Volume must map each selected use case and its KPMs to network performance classes and identify the OCUDU enhancements tied to each, and the proposal should draw on ongoing RTEC testing results.
• The topic requires CMMC Level 2 (Self). It is not marked as ITAR-restricted in the topic metadata.

Think your company fits OSW27BZ02-DV005? Talk with BW&CO before the January 6 deadline.

Plan Your OSW27BZ02-DV005 Submission

Official topic text (verbatim from DSIP)

The text in this section is copied word for word from the official DSIP topic as published on November 4, 2026. DSIP is the official source and topics can be amended. Always confirm the current version at dodsbirsttr.mil before you submit. Our commentary above is BW&CO's interpretation, not Government guidance.

Title

Resilient Tactical Edge Networks

Objective

The objective of this Phase II effort is to design, validate, and demonstrate a fully open-source, private 5G network platform for Resilient Tactical Edge Networks—integrating OCUDU, SD-Core, SD-RAN, and OSC components—to provide highly reliable, cost-effective, and scalable wide-area connectivity for autonomous field equipment, precision crop intelligence, and livestock monitoring. This platform will be validated at a representative rural site against specific key performance metrics, establishing a secure, interoperable, and procurement-ready reference architecture that supports both commercial precision agriculture and dual-use DoW mission-support applications.

Description

The realistic near-to-mid-term serviceable addressable market for private 5G in U.S. agriculture is the subset with real mobility, coverage, reliability, or data-volume pain: row-crop operations running GPS-guided and autonomous equipment, specialty-crop growers using machine vision and agricultural robotics, dairies and feedlots with dense livestock-monitoring deployments, irrigated operations with distributed pump and center-pivot control, and large ranches requiring wide-area coverage for animal and asset tracking. The scale of the opportunity is well documented. USDA Economic Research Service data show about 1.88 million farms in 2024 (roughly 39% of all U.S. land). Only 79% of farms reported internet access of any kind, leaving roughly one in five farms without even basic connectivity. There is also documented evidence that productivity of farms with connectivity is significantly higher than the ones without any connectivity. Furthermore, FCC data show that 39% of rural Americans lack access to minimum fixed broadband speeds, compared with 4% of urban Americans, and coverage on cropland and rangeland specifically is worse still. Public carrier networks will not close this gap on their own; carrier tower economics favor population density, and most agricultural land has almost none.

This segment buys on measurable operational outcomes (machine uptime, yield per acre, input cost per acre, water use, herd health, labor hours saved), not on global platform standardization, and its stated barriers to adoption are consistent and compounding: ROI ambiguity, high capex against tight and cyclical farm margins, no in-house RF/cellular or IT staff, harsh outdoor operating environments, a fragmented device ecosystem spanning tractors, drones, sensors, and wearables, and coverage requirements measured in thousands of acres rather than thousands of square feet. A proprietary private 5G platform from a tier-one vendor addresses almost none of these barriers directly; it is priced and supported for industrial campuses and multi-site enterprise accounts, not a single farm with a handful of mission-critical connectivity problems to solve.

An all-open-source stack removes the structural cost and lock-in that makes proprietary platforms a poor fit for this segment. Because OCUDU's O-CU/O-DU communicate with the rest of the network over open, standardized interfaces (especially the O-RAN 7.2x split to the O-RU), the network can be assembled from whichever RU vendor best fits a given operation's coverage geometry and budget, including high-power CBRS Category B radios and high-gain sector antennas mounted on existing farm infrastructure (grain legs, silos, center-pivot towers, farmstead masts) to maximize covered acres per radio. Together, OCUDU, SD-Core, SD-RAN, and OSC form one integrated, fully open-source 5G stack that a regional systems integrator, agricultural equipment dealer, rural wireless ISP, or electric/telephone cooperative can deploy, support, and price as a right-sized, as-a-service offer for a single operation, instead of selling a broad, vendor-locked platform. That directly answers this market's stated preference for outcome-first, economically flexible offers, and it supports a coexistence posture (private 5G for mobility, coverage, and uplink-intensive problems; existing farmstead Wi-Fi and LPWAN sensors where they already work) rather than a rip-and-replace sale.

The trade-off of an all-open-source stack is that the burden of proving interoperability, stability, and security shifts from a single vendor's warranty to the integrator and the open-source community itself. Agricultural buyers, who by their own account lack in-house cellular and cybersecurity expertise, have little tolerance for integration failures discovered mid-season, when planting, spraying, irrigation, and harvest windows cannot be rescheduled. This is exactly the gap the on-going OCUDU Testing & Validation Plan, and its Radio Access Network (RAN) Testing and Evaluation Center (RTEC)-centered extensions, are designed to close: independently witnessed, multi-vendor testing of device diversity, RU diversity, long-range outdoor RF performance, Core/RIC/SMO integration, and security. The proposal should leverage the current, on-going testing and evaluation activities in RTECs and associated results on this front.

Although this topic is anchored in a specific vertical to ensure a concrete deployment environment, real users, and a defensible commercialization path, proposers should recognize and are required to present the technical work in terms of the generic network performance classes it advances. Improvements made to the OCUDU O-CU/O-DU under this effort (scheduler behavior, mobility management, uplink capacity, stability under sustained load, security features) are expected to generalize across verticals and to benefit the broader community of RAN developers building on OCUDU. The Technical Volume shall include a mapping of each selected use case, and its associated Section 3.0 KPMs, to the performance class or classes it exercises, and shall identify which anticipated OCUDU code or feature enhancements correspond to each class.

For this topic, the dominant performance classes are massive scale and wide-area coverage: maximizing covered acres per radio using high-power CBRS Category B configurations, supporting large, sparse populations of low-rate sensor devices alongside high-uplink mobile equipment, and maintaining session continuity across long-range outdoor propagation conditions, with an evolution path to NTN integration.

Research and development for this effort should address, at minimum, the following questions:

•  All-Open-Source Economics: What is the fully loaded cost (integration, support, spectrum, hardware, mounting infrastructure, and backhaul) of an OCUDU + SD-Core + SD-RAN + OSC deployment at farm scale relative to carrier coverage extensions and proprietary private-network platforms, and how should that be packaged as a CBRS-based, as-a-service offer within the price point agricultural buyers require ($75,000-$200,000 for a reference deployment covering approximately 2,000 acres)?

•  Last-Acre Coverage Economics: What combination of high-power CBRS Category B radios, high-gain sector antennas, existing vertical assets (grain legs, silos, pivot towers), and backhaul options (fiber where available, fixed wireless, or satellite/NTN) maximizes reliably covered acres per dollar, and how does the open RU ecosystem enabled by the O-RAN 7.2x split change that optimization relative to a single bundled radio line?

•  Use-Case-First Automation: Which of the use cases defined below deliver the fastest, most measurable ROI on the open-source stack, and what RTEC-executed interoperability tests (Device, RU, Core, RIC/SMO, and Infrastructure dimensions) are needed to validate each one end-to-end under realistic seasonal, weather, and terrain conditions?

•  Trust in Open Source: How does RTEC-executed testing of the full open-source stack (not just OCUDU) reduce the integration risk and skills-shortage barrier that agricultural buyers most often cite, and what evidence package best converts community-maintained, no-license-fee software into a procurement-ready proof point for a buyer with no in-house cellular expertise?

Solutions leveraging super intelligence (SI) and machine learning (ML) for variable-rate input optimization, crop and livestock analytics, predictive equipment maintenance, network optimization, or automated fault resolution are encouraged but not required. DoW will consider any novel concept that increases the reliability, economics, and trustworthiness of an all-open-source private 5G/FutureG platform for the resilient tactical edge networks. Dual-use opportunities are expected across commercial agricultural operations, DoW installation land- and range-management, perimeter and agricultural-buffer operations on DoW installations, expeditionary logistics over large unimproved areas, and food-supply-chain resilience as a national-security concern.

Proposers should address at least two of the following four use cases in their Phase II Statement of Work, and must identify which use case(s) their reference architecture and pilot deployment are designed to validate. Each use case below is defined in terms of the operational scenario it supports, the connectivity requirement it places on the platform, and the corresponding KPM table in Section 3.0. Because agricultural traffic spans extremes (from low-throughput, high-device-count telemetry such as soil sensors, livestock wearables, and irrigation command-and-control, to high-throughput, latency-sensitive streams such as UAS (unmanned Aircraft System) imagery backhaul, machine vision, and equipment teleoperation video) proposers are strongly encouraged to employ 5G network slicing to serve these disparate service classes simultaneously on the same physical network. Proposals that demonstrate slice-based traffic isolation and per-slice quality-of-service enforcement, with at least one low-throughput and one high-throughput use case operating concurrently on separate slices of a single deployment, will be viewed favorably. Device-Class Diversity and 5G RedCap. Each use-case set spans device classes from full-capability UEs (equipment modems, cameras, broadcast and production units) to reduced-capability IoT endpoints (sensors, wearables, tags, and trackers). Proposers shall address how the platform serves reduced-capability device classes, including 3GPP Release 17 Reduced Capability (RedCap) and Release 18 eRedCap UEs, and shall identify any OCUDU scheduler or feature enhancements required to support RedCap operation; such enhancements are strongly encouraged as upstream contributions under the common OCUDU benchmarking and enhancement work package. Where RedCap-certified devices are not commercially available for a given endpoint type at demonstration time, proposers may demonstrate with available device classes (or emulated RedCap UE profiles) and shall document the RedCap migration path.Use Case 1: Autonomous & Semi-Autonomous Field Equipment Connectivity

GPS-guided and autonomous tractors, sprayers, harvesters, and field robots move continuously across fields, along farm roads between fields, and in and out of farmstead staging areas, requiring an uninterrupted control-plane, telemetry, and remote-supervision connection as they roam. Fully autonomous equipment cannot legally or safely operate without a live, low-latency link for remote monitoring and emergency stops, and farms without high-speed coverage cannot use it at all. So, this use case requires the platform to sustain low-latency, high-reliability connectivity and seamless handover as equipment moves between cells across the full field footprint, including possible road transit between non-contiguous parcels.

Use Case 2: Aerial & Fixed Crop Intelligence Backhaul

Drones/UAS performing scouting, mapping, and spot-spraying missions, machine-vision cameras on harvesters and sorting lines, and dense fields of soil-moisture, weather, and plant-health sensors generate continuous, uplink-heavy data streams that must reach an on-farm edge analytics system or agronomy platform with low delay to support same-pass and same-day decisions on irrigation, fertility, and pest control. This use case requires the platform to sustain high uplink throughput with low jitter for multiple simultaneous UAS and camera streams while concurrently aggregating telemetry from thousands of low-rate sensors per cell.

Use Case 3: Livestock Monitoring & Ranch Operations

Cattle, dairy, and other livestock operations increasingly rely on connected ear tags, collars, rumen boluses, and virtual-fencing systems that must reliably reach a monitoring platform to detect health events (calving, lameness, illness), enforce virtual fence boundaries, and locate animals across grazing land that public carrier networks do not cover. This use case requires the platform to sustain consistent, wide-area, low-rate coverage for high device counts across pasture and confinement areas, with low-latency alerting for time-critical animal-health and containment events.

Use Case 4: Connected Farmstead, Irrigation & Grain Operations

The equipment that keeps a farm running is scattered across the farmstead and the fields around it: center-pivot irrigation systems, pump stations, grain dryers and grain-handling equipment, security cameras, and safety devices such as lone-worker monitors and confined-space alarms for grain bins. The cost of a lost connection is high: a stalled pivot or failed pump during peak heat can cost yield within days, an unmonitored grain dryer is a fire risk, and a missed confined-space alarm at a grain bin can cost a life. Yet most of this equipment sits beyond the reach of farmstead Wi-Fi, leaving operators dependent on unlicensed, best-effort wireless links that were never designed for critical operations. This use case requires the platform to close that gap by extending secure, private coverage from the farmstead to all surrounding equipment on the same OCUDU-based network, delivering (1) reliable, low-data-rate command-and-control for irrigation and grain equipment, and (2) continuous uplink capacity for security video and worker-safety alerts.

Phase I

This topic is accepting Direct to Phase II proposals ONLY. Therefore, a formal Phase I award will not be issued.

To qualify for a Phase II award, proposers must submit Feasibility Documentation (as part of their proposal package) demonstrating that they have already completed "Phase I-type" research and development. The purpose of this documentation is to prove that the underlying technology is mature, scientifically sound, and ready to transition immediately into the Phase II prototyping and testing environment.

The Government will accept a wide variety of documentation styles. Proposers do not need to have a perfect, finished product, but they must show that their core ideas have been successfully tested. One or more of the following items should be included to prove technology readiness:

• Test Data & Metrics: Real-world measurements, performance charts, or network test data from previous lab environments or early field trials.
• Technical Reports & White Papers: Written summaries explaining your previous research, system designs, or software integration efforts.
• Prototype Designs & Simulation Models: Diagrams, architectural blueprints, or computer simulation results showing how your proposed software and hardware components interact.
• Previous Project Outcomes: Success criteria, milestone reports, or commercialization results from prior private, academic, or non-SBIR federally funded work.

Phase II

The desired end product of this Phase II effort is a working prototype Minimum Viable Product (MVP) of a fully open-source private 5G network deployed and validated in a relevant agricultural environment. Proposers must design, integrate, and test a reference architecture consisting of OCUDU, SD-Core, SD-RAN, and OSC that successfully addresses at least two of the agricultural Use Cases defined in the Description section. The final product must demonstrate measurable interoperability, scalability, and security under realistic rural outdoor propagation conditions.

Key Performance Metrics (KPMs) & Testing:

Proposers shall propose specific, justified KPM targets in their Technical Volume, calibrated to their selected use cases, demonstration environment, and spectrum plan. Required KPMs include session success rate, handover success rate, latency, jitter, coverage completeness, and service availability (e.g., sustaining a >99.5% session success rate for autonomous equipment handing over between 3 cells at 15 mph).

• Latency Measurement: Latency KPMs denote round-trip application-layer latency measured between the User Equipment (UE) application interface and the local edge application endpoint. Handover time denotes user-plane interruption time at the RAN.
• Target Values: Threshold values represent the intended standard of Phase II demonstration success; Objective values are stretch goals. Final KPM targets will be finalized at kickoff and confirmed at the Critical Design Review (CDR).

Prototype Demonstration Environment:

Demonstrations must be performed at a rural site secured by the proposer. Acceptable sites, in order of preference, are: (1) an operating farm or ranch; (2) an agricultural research/extension facility; or (3) a representative outdoor rural environment of comparable scale. If a non-agricultural site is used, the proposer must document the differences and account for effects like crop-canopy attenuation via link-budget margins. The mobility and coverage KPMs must be validated using physical instrumented vehicles moving across fields/roads at operational speeds, using real radio signals.

OCUDU and Open-Source Integration:

Proposers must integrate the stack with no proprietary core, RIC, or SMO components. The MVP demonstration must utilize physical Radio Units (RUs) and UEs (e.g., equipment modems, UAS, sensors, or wearables). Performers must address backhaul diversity (fiber, fixed wireless, satellite/NTN) and scalability across multiple RU vendors, including high-power CBRS Category B options.

Security Requirements:

Security must be a first-class design requirement. The architecture must cover 3GPP security (TS 33.501), O-RAN open interface protection (WG11), zero-trust principles (NIST SP 800-207), and CVE monitoring. The MVP demonstration must include at least one security capability shown live (e.g., rejection of an unauthorized device or encrypted fronthaul).

Schedule and Milestones (18-Month Period of Performance):

• Month 1: Kickoff and Technical Interchange Meeting (TIM)
• Monthly: Status Reports (MSRs) presented to the sponsor and the OCUDU T&E Working Group
• Month 10: Critical Design Review (CDR)
• Month 14: Final design review, demonstration, and assessment
• Month 16: Prototype MVP demonstration
• Month 18: Final Phase II Report

Phase II Deliverables:

• Kickoff and TIM presentation materials.
• Monthly Status Reports (MSRs).
• Critical Design Document (detailing the full reference architecture and coverage/backhaul design).
• Documented Key Performance Metrics (KPM) targets and testing methodology.
• MVP Demonstration Package (slides, documentation of site fidelity, and KPM results).
• Reference Configuration Package (executables, integration documentation, and RTEC test results).
• Live prototype integration into an RTEC-affiliated test network or farm-representative site.
• Final Design Document.
• Final Technical Report.

Phase III Dual Use Applications

The Resilient Tactical Edge Networks platform, built on an open-source private 5G network, offers significant dual-use capabilities for both commercial and Department of War (DoW) applications. Commercial Use: The primary commercial application is to provide reliable, high-speed connectivity to farms and ranches, which are currently underserved by traditional networks. This enables the use of precision agriculture technologies such as autonomous equipment, aerial crop monitoring, and dense sensor deployments for livestock and irrigation management. The goal is to increase farm productivity, improve operational efficiency, and provide a clear return on investment for commercial agricultural operations.

Department of War (DoW) Use: The same technology can be leveraged for various defense and national security purposes. Expected applications include managing land and ranges on DoW installations, monitoring perimeters and agricultural buffer zones, supporting expeditionary logistics over large and unimproved areas, and bolstering food supply-chain resilience, which is a key national security concern.

In essence, the technology developed for enhancing commercial farm operations can be directly adapted to meet the DoW's needs for robust, private communication networks in diverse and challenging environments.

References

1. https://www.juniper.net/us/en/solutions/solution-briefs/2025/gain-the-advantage-with-5g-tactical-edge.html

Keywords

Resilient Tactical Edge Networks, OCUDU, Open Radio Access Networks

Frequently asked questions

What is OSW27BZ02-DV005?

It is an Office of the Secretary of War SBIR topic, Resilient Tactical Edge Networks, seeking a fully open-source private 5G platform built on OCUDU, SD-Core, SD-RAN, and OSC, validated at a representative rural site for precision agriculture and dual-use DoW mission support.

When is OSW27BZ02-DV005 due?

Proposals are due January 6, 2027, 12:00 PM ET. DSIP pre-release began November 4, 2026, and direct contact with the topic authors is allowed only until the topic opens on December 2, 2026, 8:00 AM ET.

Is this a Phase I or Direct-to-Phase II topic?

It is Direct-to-Phase II only. No formal Phase I award will be issued, and proposers must include Feasibility Documentation showing completed Phase I-type research and development. The Phase II period of performance is 18 months.

Which key performance metrics are required?

Proposers set justified KPM targets for their use cases, and required KPMs include session success rate, handover success rate, latency, jitter, coverage completeness, and service availability. The topic gives an example of sustaining a session success rate above 99.5% for autonomous equipment handing over between 3 cells at 15 mph.

Book a Free Fit Call