Inspection prep is broken. Every unit knows it. Nobody fixed it. The Marine Corps has been preparing for IG inspections the same way since most of today's senior leaders joined.
The CO walks into a CGIP with no reliable readiness picture until 14 days out. The tool that should have surfaced critical gaps 60 days earlier does not exist.
IGMC publishes the inspection schedule. They have zero visibility into how any unit is preparing for it. The institution cannot learn from readiness data that is never captured.
Preventable findings. Relief-for-cause risk on outcomes commanders had no data to predict. Readiness blind spots from unit level to CMC. This is not a training problem. It is a tool problem - and no tool exists for any service in the DoW.
Four Marines. Four echelons. One data architecture. Everything described below runs on a single platform the Marine Corps builds and owns.
One unified data architecture. Every echelon connected. No manual rollup. No hand-jam. Deck plates to flag pole.
| Dimension | MICT (Air Force) | MCSWF Build, OSD Adopts |
|---|---|---|
| Cost | $18.5M / 5 years (contractor) | Built in-house, zero contract cost |
| Scope | 1 service, ~330 commands | 6 services, ~4,400 commands |
| IP Ownership | Contractor (Alaska Northstar Resources LLC) | Marine Corps owns everything - initially and permanently |
| Joint Expansion | None | Open-source on Repo One, day one |
| ATO | Separate compliance track | cATO inherited from Platform One |
IGMC Connections tracks inspector certification. IG Warfare tracks inspection readiness. One certifies the inspector. The other prepares the unit. Complementary, not competing.
The Air Force spends $3.7M/year on MICT for one service. If MCSWF builds this, the Marine Corps owns the IP, the data architecture, and joint expansion terms. A contractor captures none of that.
Tier 1 validates the workflow with zero infrastructure. Tier 2 is the purpose-built product on Platform One. Tier 3 is the enterprise data layer. Open-source on Repo One from day one.
A simulated walkthrough at four echelons. Click through each view.
Encrypted. Tagged with unit, date, location, functional area. Submitted to your command readiness dashboard in real time. IGMC gets aggregate data. No PII. No classified data.
The XO used to walk into a sync meeting hoping someone had an update. Now the data is waiting when she sits down. Problems surface - she doesn't hunt for them.
The platform doesn't just display numbers. It analyzes them. It spots cross-MEF patterns, flags declining trends, and recommends institutional action - all from the same pre-inspection data flowing up from the deck plates.
MCSWF development resources. MCMWTC pilot unit. Tier 1 is live in weeks with no budget authority. The Air Force paid $18.5M for one service. The Marine Corps builds it for all six.
If it works at 7,000 feet, bandwidth-limited, with a 70-year-old range complex, it works anywhere in the Marine Corps - and anywhere in the joint force.
A successful MCMWTC pilot is valid for both FMF and installation commands simultaneously. No other single pilot unit can make that claim. Most efficient path to enterprise-ready.
MCMWTC has a CG inspection scheduled for summer 2026. The prior year's inspection executed remotely due to travel restrictions - establishing precedent for a distributed pre-inspection model at this unit. MCMWTC is positioned to stress-test the platform against a real inspection event: real unit, real inspection, real outcome. Command IG coordination is the natural next step to formalize the pilot scope.
Not competing options - a spectrum of institutional ambition. The same build, the same pilot, the same architecture produces any of these outcomes depending on where MCSWF chooses to take it. Scales to any Service and any inspection easily.
Maj Joel L. Sartain, USMC
XO, MCMWTC Bridgeport
joel.sartain@usmc.mil
Mr. Brandon Schroder
Deputy Director, MCMWTC
brandon.schroder@usmc.mil
UNCLASSIFIED. No restrictions. Research conducted independently. All sources publicly available.
The real product is a server-side agent with a curated knowledge base - every FAC, every regulation, every best practice, every historical pattern. Nearly all of this content is unclassified.
That agent informs everything downstream:
Building local agents is easy. The hard part - and the durable value - is the master knowledge base and the reasoning layer on top of it.
Every FAC checklist. Every governing MCO. Every historical inspection pattern across the Corps. Curated, versioned, and queryable. The agent reasons over this - it doesn't just parrot checklists. This is the decisive advantage.
The Motor T example is one of dozens of functional area checklists. Every functional area gets an agent. Every agent generates structured data. Every pre-inspection feeds the readiness dashboard. Once the intelligence core is built, every capability - phone tools, dashboards, trend reports - is a downstream output of the same architecture.
This concept brief is the output of a disciplined Phase 1 market validation - not a pitch that preceded the research. What follows is a summary of the methodology and scope used to validate the requirement at commercial rigor across all six services of the Department of War.
Twelve formal deliverable documents produced across 8+ weeks of independent research - including a full Phase 1 Business Validation, service-level TAM reference, and this concept brief. Phase 1 is complete. Phase 2 begins when MCSWF identifies this as a project of interest.
brief.igwarfare.com
Research conducted independently, outside official duties. No government resources, time, or information were used. All sources are publicly available. This brief submits that work to the service for evaluation and action.