What This Means:
National Aeronautics and Space Administration (NASA) Administrator Jared Isaacman didn’t just describe a supply chain philosophy at the FY27 Senate Appropriations hearing — he described a new procurement posture. When NASA embeds Goddard Space Flight Center (GSFC) and Jet Propulsion Laboratory (JPL) engineers in vendor facilities, it changes who wins contracts, what performance clauses look like, and which suppliers can operationally absorb that level of oversight. Business development (BD) teams and primes that read this as a logistics footnote will find the next solicitation written around criteria they didn’t prepare for.
The Pattern Statement
The model Isaacman described is not new to aerospace. What is new is that NASA is saying it out loud — and in a budget hearing.
At a late April 2026 Senate Appropriations Commerce, Justice, and Science (CJS) subcommittee hearing, Isaacman put a precise diagnosis on one of the agency’s oldest failure modes: “For a very long time across all of NASA, we’ve talked a really good game, but then we kind of sit and wait for our vendors and partners to deliver outcomes — and as a result, we tend to be late and it tends to cost more.” His prescription was equally direct: embed subject matter experts from GSFC and JPL inside vendor facilities to drive outcomes, not just monitor them. That framing, driving, not monitoring — is the policy shift contractors need to understand before the next solicitation cycle is written around it.
The significance is not that NASA plans to hire more oversight personnel. It is that the agency is signaling a structural change in how performance accountability will be allocated in future contracts, who bears schedule risk, and what access rights the government expects as a baseline condition of doing business. BD teams treating this as a management preference will find themselves on the wrong side of source selection criteria they didn’t build their proposals around.
The Contract and Policy Evidence
The embedded engineer model has a documented precedent inside the Department of Defense (DoD) that spans decades, and its outcomes are instructive for any prime or sub-tier navigating a similar posture shift at NASA.
The Defense Contract Management Agency (DCMA) has operated Resident Engineer (RE) programs at major defense contractor facilities since the Cold War era, placing government engineers at primes including Boeing, Lockheed Martin, and Raytheon to oversee major systems integration, quality assurance, and schedule performance in real time. The DCMA’s own policy documents describe the role as extending beyond inspection into “influencing contractor’s internal controls, reducing the frequency and intensity” of performance failures — language that closely mirrors what Isaacman described in April. The distinction that matters: resident engineers at DoD facilities are not auditors arriving after the fact. They are embedded decision participants whose presence changes both the contractor’s internal reporting discipline and the government’s early-warning intelligence on program health.
On the NASA side, the agency’s own procurement history reflects a persistent gap between oversight intention and execution. A NASA Office of Inspector General (OIG) semiannual report covering fiscal year (FY) 2025 documented ongoing cases of contractor employees failing to disclose relationships with center contractors — a symptom of oversight distance, not proximity. Government Accountability Office (GAO) assessments of NASA’s major programs have repeatedly flagged cost and schedule growth tied not to technical failures alone, but to the government’s limited real-time visibility into contractor performance before problems became program-level crises. Per GAO reporting cited in trade coverage, three Artemis projects alone generated cost overruns approaching the total overruns of all other 48 major NASA projects combined — a data point that requires direct GAO report citation and should be replaced with the original source before publication. Isaacman’s embedded engineer model is, in part, a direct response to that documented pattern.
What is less documented, and more important for contractors to understand, is what existing NASA acquisition vehicles could carry this oversight model into binding contract structures before new solicitations are written. A NASA acquisition vehicle potentially relevant to this model, referenced internally as the Systems Integration and Booster Engineering Requirements (SIBER) program, had not been confirmed via SAM.gov at time of writing; its solicitation status should be verified through the NASA Acquisition Forecast at hq.nasa.gov before this analysis is cited in a proposal context. The agency’s broader tendency toward performance-based contracting under the NASA Federal Acquisition Regulation Supplement (NFS) represents the more immediately verifiable regulatory pathway. NFS Part 1827 already establishes government rights frameworks around technical data, software, and intellectual property (IP) developed under contract — rights that expand significantly when government personnel are resident in contractor facilities and actively engaged in technical development. BD teams that have not reviewed their current teaming agreements and data rights clauses against the NFS Part 1827 framework should do so before the next Artemis-related solicitation cycle.
The next three sections break down exactly how embedded oversight will reshape facility access requirements, performance clause structure, and IP rights exposure — with specific reference to NFS Part 1827, FAR Subpart 45, and the JPL FFRDC distinction that most BD teams are not accounting for. Subscribers get the full contractor readiness checklist and stakeholder-by-stakeholder competitive analysis.
