Briefing
The Air Force Wants One IETM
The Signal
From Per-Platform to Enterprise
The Rapid Sustainment Office — AFLCMC's innovation arm, operating with reported nine-figure support vehicles — is investigating the cost and feasibility of a single IETM capability meeting the Air Staff's Enterprise IETM Framework. The problem statement is the Air Force's own: technical data today is acquired, published, and sustained per program office, each with its own OEM relationship — a siloed model that meets unique mission needs while complicating logistics integration and degrading data integrity between systems. Any reader of this site will recognize the shape: every silo locally reasonable, the aggregate unmanageable.
The stack the language points at is the existing Air Force one, applied at enterprise scope: current-issue S1000D, MIL-STD-3048 business rules, and technical data managed in a government-owned CSDB with IETM access on top.
What It Means
Conformance Becomes the Ticket
An RFI is market research, not money — but RFIs of this shape are how acquisitions get scoped, and the direction is unambiguous when read alongside the FY26 NDAA's technical-data inventory: enterprise frameworks, government-controlled repositories, and systematic visibility into contractor data. For the bidder ecosystem, the practical translation is that three muscles get tested. Real conformance— content that validates against 3048's business rules, not merely against schemas. Exchange discipline— data dispatch and receipt into a repository you don't operate, with applicability intact. And legacy honesty — a defensible answer to what your existing libraries would take to bring along.
We build and audit exactly those muscles — BREX-level conformance, CSDB exchange, conversion scoping — and we'll be tracking this initiative as it matures. If the Enterprise IETM framework turns into the solicitation it's pointing toward, the winners will be the teams who treated enterprise-grade data discipline as practice, not paperwork.
FAQ
Questions We Hear
What is the Enterprise IETM initiative, concretely?
The Air Force Life Cycle Management Center's Rapid Sustainment Office has issued a Request for Information investigating the cost and technical feasibility of a single Interactive Electronic Technical Manual capability meeting the Air Staff's (HAF/A4L) Enterprise IETM Framework — serving both next-generation platforms and legacy fleets. An RFI is market research, not a contract; but RFIs of this shape are how major acquisitions get scoped, and the framework language tells you where requirements are heading regardless of when a solicitation follows.
What problem is the Air Force trying to solve?
Its own stated one: today, technical data is acquired, published, and sustained by individual program offices for their unique platforms, each coordinating with its own OEM. That per-platform model meets unique mission needs but complicates logistics-systems integration and degrades data integrity between disparate systems. It is the enterprise-scale version of the pattern we write about constantly — every silo locally reasonable, the aggregate unmanageable — and the proposed cure is the familiar one: shared standards, shared infrastructure, one delivery capability.
Which standards does the initiative point at?
The published language points at the current S1000D issue, MIL-STD-3048 (the Air Force's business rules for implementing S1000D), and technical data managed in a government-owned Common Source Database with IETM access. None of that is exotic — it's the existing Air Force S1000D stack, applied at enterprise scope. What changes is the center of gravity: business-rule conformance and CSDB interoperability stop being per-program conversations and become the price of participating at all.
What should bidders and suppliers do about it now?
Treat fluency as positioning. Whether or not this specific RFI becomes a program, the direction — enterprise frameworks, government-owned repositories, strict business-rule conformance — is where Air Force technical data is visibly heading, and it rhymes with the FY26 NDAA's technical-data inventory push. Practical preparation looks like: content that actually validates against MIL-STD-3048 business rules rather than merely against schemas, data-exchange discipline (dispatch, receipt, applicability integrity), and honest answers about what your legacy libraries would take to bring along. Those are exactly the muscles a response will have to demonstrate.
Get In Touch
Fluent Before the Solicitation?
If your team will touch an Enterprise IETM response — prime or sub — the conformance, exchange, and conversion questions are answerable now. We help teams answer them first.