Size It on the Devices, Not the Force

Capture Corner is the premium BD intelligence companion to Mission Meets Tech. Public-record sourced. Independent analysis. Not a recommendation, not vendor advocacy, not capture material. Built for federal health BD, capture, and proposal leaders who need analytical depth, not headlines.

This issue is the companion to "Ten Years to Build It. Ten Months to Field It.," published this week. The public piece reads the fielding decision and the mechanism behind it. This one works the money: which prime slots are closed and which contract vehicles carry the follow-on, why the addressable user base is a resourcing document rather than an end-strength number, what the SAFe release train does to your bid model, the six lanes that open behind the approval ranked by how soon they are biddable, and the two FY28 budget lines that will tell you whether sustainment was funded or assumed.

---

1. The decision at a glance

Field	Detail
Action	BATDOK-J approved for Army-wide fielding
Approving authority	CPE Ground - Soldier Systems
Date	July 27, 2026, effective immediately
Delivery mechanism	Authorized download to Nett Warrior end-user devices. No hardware fielding action.
Host network	Integrated Tactical Network, Secure-But-Unclassified Encrypted enclave
Downstream fusion	Operational medical data services backbone to MedCOP and MedHub to Maven Smart System
Portfolio	One of six JOMIS-managed applications; the only one operating at point of injury
Army delivery office	OMIS-A, formally established April 12, 2024
Delivery model	SAFe Agile release train
Development prime	BAE Systems, selected July 3, 2025 under AFRL FORGE-IT
Portfolio status	JOMIS transitioning prototype to fielding across all six applications in FY26

Confidence: High on the approval, the delivery mechanism, and the portfolio structure. The approval and the download authorization come from the announcement by the 46th Surgeon General's strategic communications office, verified against the post text. Portfolio structure, the five operational medicine functions, and the FY26 transition come from the DOT&E FY2025 JOMIS report [CC1][CC2].

The lead finding is that this fielding decision does not tell you the size of the market. An authorized download reaches the population that already holds the device. Nett Warrior is a dismounted-leader end-user device, issued against a basis of issue plan that covers leader positions rather than the whole formation. Every sizing model built off Army end strength, off medic density, or off "the Army fielded it" is wrong by an unknown multiple, and the correction lives in a resourcing document rather than a press release.

Section 5 works that problem. Everything before it is the contract picture.

---

2. The prime slots, and what they cover

Confidence: High on the awards named. Medium on completeness, because sub-tier and task-order-level work under these vehicles is only findable one record at a time.

Component	Holder	Contract signal
BATDOK-J development	BAE Systems	Selected July 3, 2025 under AFRL FORGE-IT to continue development [CC3]
Operational medical data services backbone	Omni Federal (Omni Fed LLC)	DHA sole-source modification, HT0038-21-F-0035, SAM.gov notice June 26, 2026 [CC4]
OpMed CDP, Roles 1 through 2	Peraton with T6 Health Systems	$28M firm-fixed-price prototype award, February 13, 2025 [CC5]
Maven Smart System	Palantir Technologies	$480M IDIQ May 2024, ceiling raised toward $1.3B through 2029; $99.8M multi-service expansion September 2024; Army Enterprise Agreement up to $10B, July 31, 2025 [CC6]
Nett Warrior EUD and ITN radios	Samsung baseline hardware; radio primes under PEO C3T and C3N	[CC7]
OMEIS teleradiology add-on	Open. RFI closed January 26, 2026, sources sought	Secondary aggregator source. Verify on SAM.gov before acting [CC8]

Three things a competitive assessment should carry that most will not.

The development seat sits with AFRL, not with the Army. BAE holds BATDOK development through an Air Force research vehicle while the Army holds the fielding decision and OMIS-A holds Army delivery. Three organizations, three funding streams, one application. A teaming plan that treats this as a single-customer pursuit is aimed at one third of the buyer.

The backbone was mod'd sole-source seven weeks before the fielding approval. The June 26, 2026 notice on HT0038-21-F-0035 is the clearest public signal that DHA moved to secure data-layer continuity ahead of a fielding event. Sole-source posture on the backbone constrains what a challenger can bid at that layer and tells you where DHA judged the schedule risk to be.

Maven is consolidating, not fragmenting. Reporting in March 2026 indicates the Maven Smart System is moving to a formal program of record by end of FY26 with future contracting handled by the Army [CC9]. Anything that writes into Maven inherits that stability. It also inherits Palantir's integration gate.

---

3. What the release train does to your bid model

Confidence: Medium. The SAFe 6.0 model is documented for OMIS-A. The bid-behavior consequences are my analytical construction.

OMIS-A runs Scaled Agile. Documented publicly at the program's transition from MC4 [CC10]. Three consequences for how you price and staff.

Recurring delivery orders replace the single large capture. Award value distributes across program increments rather than concentrating at a five-year base-plus-options event. A capture team that allocates B&P on the assumption of one decisive proposal will underfund the follow-on orders where most of the value sits.

Past performance is measured in cadence. On a release train, the discriminator is whether you delivered on increment boundaries, not whether you completed a program. Firms with a record of hitting sprint commitments on federal work have a citable advantage that traditional past-performance narratives do not surface. Write it in increments and cite the dates.

The staffing profile is flat and continuous. No surge to a milestone and taper after. Price a steady team that can plug into an existing release train, and expect the government to evaluate whether your people can work inside someone else's ceremony structure rather than stand up their own.

The capture consequence. If your pipeline model prices this portfolio as one opportunity per application, it is mis-sized in both directions: too large on any single award, too small in aggregate across increments.

---

4. Six lanes behind the approval, ranked by how soon they are biddable

Confidence: Medium throughout. The lanes are grounded in documented program activity. The ranking and the timing are my read.

Near term, next two to four quarters.

Paired sensor integration. BATDOK ingests vitals from paired sensors. Getting a device onto an approved list is the gate, and the list is the market. The approval path is the pursuit, not the sale. Any sensor OEM already carrying an FDA clearance and a military form factor should be working the qualification path now, because the fielding wave rewards whoever is already on the list rather than whoever is best.

RMF and ATO sustainment. JITC operational testing surfaced cyber survivability deficiencies of the kind typical of first-fielding software [CC2]. A medical application riding the tactical network carries a continuing authorization burden. This is unglamorous, recurring, and it is the most reliably funded lane on this list.

Medium term, FY27.

iOS sustainment for the evacuation variant. The 445th Aeromedical Evacuation Squadron and the 711th Human Performance Wing built an iOS variant with JOMIS funding the FY25 work [CC11]. Two operating systems, two form factors, one record. Sustainment tail follows fielding, and the aeromedical evacuation community is a distinct buying center from Ground.

Training and simulation. Virtual BATDOK is already in the peer-reviewed literature [CC12]. The Navy finalized its JOMIS training systems plan in February 2026 [CC13]. Expect solicitations for TCCC training that documents natively into BATDOK-J rather than into a simulation-only record. The Army's training pipeline for this application is the open question; ask about it in the fall.

Longer term, FY28 and beyond, higher variance.

Coalition extension. OpMed CDP is deployed at Balikatan in the Philippines at Role 2 [CC14]. An application living on an encrypted-but-unclassified enclave is a far shorter conversation with a partner nation than one requiring classified infrastructure on both ends. The constraint is data-sharing agreements rather than software. Treat foreign military sales interest as plausible and unpriced.

Civilian prehospital. Maryland State Police put BATDOK on medevac helicopters in December 2025, the first civilian deployment [CC15]. Civilian prehospital care has the same documentation gap with different regulatory constraints and a much larger user base. If outcome data emerges from that deployment, state EMS becomes a real conversation and AFRL ends up holding a technology transfer story it did not set out to write. This is the highest-variance lane on the list and the one with the largest ceiling.

Deliberately excluded. The garrison-to-VA record continuity seam. It is the strategic endpoint of this architecture and it is a separate analysis with its own conflict boundaries. It does not appear in this issue.

---

5. The basis of issue is the market size

Confidence: High on the device characterization. High on the logic. The specific distribution numbers are not public at the level this question requires, and I am not going to estimate them.

Read the authorization language exactly: any Soldier equipped with a Nett Warrior end-user device is authorized to download BATDOK-J and use it operationally.

Nett Warrior is the Army's dismounted-leader device. It is issued against a basis of issue plan tied to leader positions on the Integrated Tactical Network, which is a narrower population than the force. A company medic may or may not hold one. That is a resourcing decision, and it is the single variable that converts this fielding approval into a number.

What this means for anyone sizing a play in Section 4.

A sensor integration business case priced against Army medic population is priced against a population that cannot currently run the application. The addressable base today is the intersection of medic positions and Nett Warrior distribution, and the second set is the binding constraint.

A training and simulation play has the inverse exposure. Training demand tracks the doctrinal population rather than the device population, because units train medics who will eventually receive devices. That lane is less gated by basis of issue than the sensor lane, and it is worth more than a device-count model would suggest.

The three questions that resolve this.

Whether the fielding approval triggers a basis-of-issue plan review for Nett Warrior that adds medic positions. Whether OMIS-A or PEO Ground carries that action. And whether it lands in the FY28 request or waits for FY29.

The capture consequence. Until one of those three is answered, any pipeline number attached to a BATDOK-J-adjacent pursuit carries an error bar the size of the device distribution question. Say so in your pursuit review rather than picking a number and defending it. The teams that acknowledge the gate will be the ones positioned when it opens.

---

6. What the FY28 request will tell you

Confidence: Medium. The FY26 portfolio transition is documented. The budget-signal read is analytical.

DOT&E records the JOMIS portfolio transitioning from prototype to fielding across all six managed applications in FY26 [CC2]. Fielding six applications and sustaining six applications are different cost structures, and the second one is where programs quietly starve.

Two places to look when the FY2028 President's Budget drops.

Migration from RDT&E to O&M within the Defense Health Program. A capability that fields and stays funded shows a declining research line and a rising operations and maintenance line covering sustainment, help desk, training, and cybersecurity. A capability that fielded and was assumed shows a declining research line and no corresponding operations growth. That pattern is visible in the DHP justification books without any special access.

Whether OMIS-A's line grows with the delivery scope. The Army office now owns delivery for an application authorized force-wide. If the Army delivery line stays flat while the fielded footprint expands, the sustainment burden is being absorbed rather than resourced, and the recompete environment two years out will be shaped by that gap.

The capture consequence. A sustainment pursuit priced against an assumed funding line, in a portfolio that just fielded six applications simultaneously, is the highest-risk bid on this list. Read the exhibits before you commit B&P.

---

7. Positioning that works now, and what it costs later

Confidence: Analytical construction throughout. This section is my read, not reported fact.

The Army demonstrated a specific play in September 2025: a senior technical authority challenged an existing capability to prove itself at a training rotation already on the calendar, with a date attached and a real possibility of failure. Ninety days from challenge to demonstration. Ten months from demonstration to fielding approval.

Three positioning moves consistent with that pattern.

Bring a capability that already works somewhere else. The demonstration succeeded because the software had six years of operational use behind it and the ask was integration rather than invention. A vendor pitching a new build into this environment is asking for a program start in an organization that has publicly committed to the opposite. A vendor pitching an existing product that has never touched the Integrated Tactical Network is asking the question the Army is currently rewarding.

Aim at the network, not the requirement. The discriminator in September 2025 was whether data survived the ITN and rendered in Maven. Integration evidence against that specific path is worth more in this market than feature depth.

Find the rotation. Combat training center rotations are on a published calendar. A demonstration that consumes an event already scheduled costs the government a slot rather than a new start, and that arithmetic is why the play worked.

What expires. A challenge that becomes routine stops being falsifiable, because organizations eventually learn to schedule the demonstration they know will pass. The window where this play carries real weight is the window where failure is still a live outcome. My read is that window is open now and narrows as the model institutionalizes.

---

8. What would falsify this read

Stated plainly, because a brief that cannot be wrong is not intelligence.

If Nett Warrior basis of issue already covers medic positions at scale, Section 5 overstates the gate and the sensor lane is larger and nearer than ranked.

If the FY28 request shows flat operations and maintenance growth across the JOMIS portfolio, Section 6 is right about the risk and every sustainment lane in Section 4 should be repriced downward.

If Maven's transition to a program of record shifts the integration gate to the Army rather than the vendor, Section 2's read on inherited stability changes, and the qualification path for anything writing into Maven gets shorter.

If the OMEIS requirement was cancelled rather than deferred, the teleradiology line in Section 2 comes out entirely. That one is a SAM.gov check, and it should be the first thing anybody acting on this issue verifies.

---

Editorial discipline note

Capture Corner is built to be useful, not provocative. It does not name preferred vendors. It does not recommend awards. It does not characterize any firm's compliance posture beyond what public records support. It does not reveal nonpublic information. It does not advocate for any specific offeror's win. Every company named here is named because it appears in a public award record or a public program announcement.

Named government officials and named practitioners are omitted throughout. Where a program office or an action matters, the approving organization and the award identifier are given so subscribers can go to the record directly.

Several items are my construction rather than reported fact and are marked at the section level: the bid-model consequences in Section 3, the lane ranking and timing in Section 4, the sizing logic in Section 5, the budget-signal read in Section 6, and all of Section 7.

The OMEIS line in Section 2 rests on a secondary aggregator rather than a primary notice. Verify on SAM.gov before acting on it.

The garrison-to-VA record continuity seam is deliberately excluded from this issue.

---

Mary

Mission Meets Tech Premium

---

Next Capture Corner: scheduled for the next major federal health or defense-health opportunity in active capture. Subscribers will receive an alert when the next issue publishes.

Capture Corner is an independent intelligence product. It is not affiliated with the Department of War, the Defense Health Agency, the Department of the Army, or any company named here, and it is not connected to any offeror's bid strategy. Premium subscription includes access to the standing intelligence sidebar plus the searchable archive.

---

Sources

[CC1] Announcement of CPE Ground - Soldier Systems approval of BATDOK-J for Army-wide fielding, July 27, 2026, published July 28, 2026 by the Office of the 46th Surgeon General, strategic communications. Source for the approval, the effective-immediately download authorization to Nett Warrior end-user devices, Maven Smart System and NGC2 integration, the September 2025 JRTC stress test, and participating units. Post text verified directly.

[CC2] Director, Operational Test and Evaluation, FY2025 JOMIS Report. Source for the six managed applications, the five operational medicine functions, JITC operational assessments and cyber survivability testing, the MedCOP classified-variant fielding to combatant commands, and the FY26 prototype-to-fielding transition across the portfolio. https://www.dote.osd.mil/Portals/97/pub/reports/FY2025/dow/2025jomis.pdf

[CC3] Joint Forces News, "US AFRL selects BAE Systems for BATDOK development," July 4, 2025 (FORGE-IT selection dated July 3, 2025). https://www.joint-forces.com/ew-and-cyber/83659-us-afrl-selects-bae-systems-for-batdok-development

[CC4] SAM.gov, DHA sole-source notice on operational medical data services, contract HT0038-21-F-0035, posted June 26, 2026. https://sam.gov/workspace/contract/opp/b7ff49e907764979bc23723f15910ad5/view

[CC5] Peraton, "Peraton awarded $28M to continue supporting the DHA's JOMIS health care delivery program," February 13, 2025 (OpMed CDP, firm-fixed-price prototype, with T6 Health Systems). https://www.peraton.com/news/peraton-awarded-28m-to-continue-supporting-the-dhas-jomis-health-care-delivery-program/

[CC6] DefenseScoop, "DOD raises Palantir Maven Smart System contract ceiling," May 23, 2025; Business Wire, "Palantir Expands Maven Smart System AI/ML Capabilities to Military Services," September 20, 2024 ($99.8M multi-service expansion); CNBC, "Palantir lands $10 billion Army software and data contract," August 1, 2025 (Army Enterprise Agreement awarded July 31, 2025). https://defensescoop.com/2025/05/23/dod-palantir-maven-smart-system-contract-increase/ · https://www.businesswire.com/news/home/20240920746094/en/Palantir-Expands-Maven-Smart-System-AIML-Capabilities-to-Military-Services · https://www.cnbc.com/2025/08/01/palantir-lands-10-billion-army-software-and-data-contract.html

[CC7] Army.mil, "Stryking towards networked battlefield communications," March 2, 2023, and CPE Ground Nett Warrior program page. Source for the Nett Warrior dismounted-leader end-user device, TSM waveform, SBU-E enclave, and Integrated Tactical Network. https://www.army.mil/article/264225/stryking_towards_networked_battlefield_communications · https://cpeground.army.mil/Equipment/Equipment-Portfolio/PM-MBCT-Enablers-Portfolio/Nett-Warrior/

[CC8] OMEIS teleradiology RFI, responses closed January 26, 2026, sourced via a third-party contract aggregator rather than a primary SAM.gov notice. Treated as indicative and flagged for verification.

[CC9] Reuters, "Pentagon to adopt Palantir AI as core US military system, memo says," March 20, 2026 (memo dated March 9, 2026; Maven Smart System transition to program of record by end of FY26, future contracting handled by the Army). https://www.reuters.com/technology/pentagon-adopt-palantir-ai-as-core-us-military-system-memo-says-2026-03-20/

[CC10] DVIDS, "MC4 prepares for transformation into agile-focused OMIS," April 21, 2025, and CPE Ground OMIS-A program page. Source for the SAFe 6.0 Agile delivery model, the MC4 sunset schedule, the FY24 appropriations slip, and OMIS-A formal establishment April 12, 2024. https://www.dvidshub.net/news/460281/mc4-prepares-transformation-into-agile-focused-omis · https://cpeground.army.mil/Soldier-Systems/OMIS-A/

[CC11] Air Force Medical Service, "445th AES, 711th HPW collaborate to improve en route patient care," July 29, 2024 (iOS variant; JOMIS FY25 funding). https://www.airforcemedicine.af.mil/News/Display/Article/3852546/445th-aes-711th-hpw-collaborate-to-improve-en-route-patient-care/

[CC12] Military Medicine, "Virtual BATDOK," 188(Supplement 6), November 8, 2023. https://academic.oup.com/milmed/article/188/Supplement_6/110/7388199

[CC13] Navy Medicine, "Navy Medicine forges training plan for JOMIS, boosting fleet medical readiness," March 12, 2026 (JOMIS Navy Training Systems Plan finalized February 2026). https://www.med.navy.mil/Media/News/Article/4434246/navy-medicine-forges-training-plan-for-jomis-boosting-fleet-medical-readiness/

[CC14] Defense Healthcare Management Systems public program communication, 2026 (OpMed CDP at Balikatan, Role 2). Program-office social channel rather than a primary release. Treated as indicative.

[CC15] Air Force Research Laboratory, "AFRL invention deployed by Maryland State Police," December 5, 2025 (first civilian deployment; BATDOK development timeline anchor). https://www.afrl.af.mil/News/Article-Display/Article/4350895/afrl-invention-deployed-by-maryland-state-police/

[CC16] Soldier Systems Daily, "US Army activates Capability Program Executive Enterprise Software and Services (ES2)," March 1, 2026; CPE Ground, "A new force in Army acquisition: PEOs Soldier and Ground Combat Systems merge," April 10, 2026. Source for the Capability Program Executive reorganization and CPE Ground establishment. https://soldiersystems.net/2026/03/01/us-army-activates-capability-program-executive-cpe-enterprise-software-and-services-es2/ · https://cpeground.army.mil/News/Article-Display/Article/4456266/a-new-force-in-army-acquisition-peos-soldier-and-ground-combat-systems-merge-to/