NASA revises its digital engineering acquisition handbook
What happened
NASA has issued Revision A of NASA-HDBK-1004, the NASA Digital Engineering Acquisition Framework Handbook. The NASA Technical Standards System lists version A with a document date of 26 October 2026, as an active handbook of the Office of the Chief Engineer in its systems engineering and integration category. It is not a NASA mandatory standard. NASA's Technical Reports Server records the same document, NASA-HDBK-1004A, with a publication date of 20 October 2026. The full text is free to download.
The handbook's document history log describes Revision A as a "Proposed revision of NASA-HDBK-1004" that incorporates updated digital engineering acquisition guidance and supersedes an earlier NASA handbook. The original edition dates from 1 April 2020. The key changes it lists include:
- sections added on stakeholder involvement in forming data item requirements, common questions to consider when developing those requirements, and lessons learned;
- a new Recommended Contract Language (RCL) matrix in Appendix A, gathering the sample contract language into one place;
- a significant update of the reference documents;
- six pages of sample XML code removed from a data requirements template;
- best practices added for organising data sets and data tables to maximise readability by large language models (LLMs).
Why it matters
The handbook deals with digital engineering at the point of acquisition. Its scope says it helps programmes and projects identify, select and tailor the data, model, interoperability, access and contractual considerations needed to support life cycle decision-making. In NASA's words, it provides "recommended practices and sample acquisition language for obtaining useful, accessible, interoperable, and reusable engineering information". NASA's Technical Reports Server record says the recommended language is for Statements of Work (SOWs) and Data Requirements Descriptions (DRDs).
It is guidance, not a set of requirements. The handbook states that it generally does not use "shall" statements, and that its recommended language becomes binding only once a project selects it, tailors it and places it in a contract or other governing document.
One example of its detail concerns models written in the Systems Modeling Language (SysML). The handbook states that SysML is still evolving, so it does not define compliance with a specific version. It advises programmes to be very specific about the SysML version and the vendor format they want delivered, to ensure maximum interoperability between NASA and the contractor, and to note key plugins such as the Unified Architecture Framework (UAF) to ensure full use of delivered models.