Skip to main content

NASA DIGITAL ENGINEERING ACQUISITION FRAMEWORK HANDBOOK

Options for Standards Update Notification System (SUNS)
Send SUNS Updates
Yes
SUNS Notification Type
Revision
Organization that Developed the Standard
Organization that Developed the Standard
NASA Standard
Document Identifiers
Document Number
NASA-HDBK-1004
Version
A
Change Number
0
Document Date
Is Active?
ACTIVE
NASA Organization and Technical Discipline
Responsible NASA Organization
NASA HQ, Office, Facility or Division
NASA HQ Office, Facility or Division
OCE - Office of the Chief Engineer
Technical Discipline Category
1000 - Systems Engineering and Integration, Aerospace Environments, Celestial Mechanics
Endorsed Standard
Endorsement Details
Endorsing NASA Organization
OCE Endorsed Standard
NASA Core Standard
No
NASA Endorsement Date
NASA Endorsed Standard Status
NASA Endorsed Standard
Mandatory Standard
NASA Mandatory Standard
Not a NASA Mandatory Standard
Document Scope
Document Scope
This NASA Technical Handbook provides guidance for planning and implementing a Digital Engineering (DE) acquisition framework. It assists programs and projects in identifying, selecting, and tailoring data, model, interoperability, access, and contractual considerations needed to support lifecycle decision-making and NASA’s Digital Engineering Ecosystem.
The Handbook provides recommended practices and sample acquisition language for obtaining useful, accessible, interoperable, and reusable engineering information. It does not independently establish program/project or contractor requirements; requirements become binding only when imposed by an applicable directive, standard, contract, agreement, or other governing document.
Handbook Use of Requirement Language. As a general rule, this Handbook does not establish requirements. A NASA Technical Standard is intended to establish what is required to be accomplished, whereas a NASA Technical Handbook is primarily intended to provide guidance on how an objective may be accomplished, including recommended practices, methods, examples, lessons learned, and implementation options. Accordingly, this Handbook generally does not use “shall” statements to direct what a program, project, or contractor is required to do. Instead, such material is presented as guidance or recommended practice. Programs/projects should exercise discretion in selecting and tailoring the Recommended Contract Language (RCL) provided in this Handbook based on their specific technical and acquisition needs. The RCL does not independently establish a requirement. Once selected, RCL should be tailored for incorporation into a DRD, SOW/PWS, solicitation, contract, or other binding acquisition instrument, the appropriate acquisition and contracting organizations may use “shall,” as appropriate, to clearly establish enforceable requirements.
Document Access Control
Document Viewable by
Export Control/Distribution Authorization
Internet Public -- Standard is cleared for public accessibility on the internet.
PUBLIC: Upload Publicly Available Standard
NASA-HDBK-1004 REV A.pdf (2.3 MB)
PUBLIC: Document History for Standard
NASA-HDBK-1004.pdf (2.34 MB)
Important Standard Dates
Next 5-Year Review Date
Submitted Date

 

Application Notes for this Standard

-No Application Notes are associated with this standard.

Lessons Learned Related to this Standard

To associate Lessons Learned to a specific standard, find the related lesson in LLIS. These lessons have been vetted and approved via the lessons learned process. Then, click “Create a new “Lessons Learned” record for this Standard” and complete the information.

If you have a lesson learned that is not in LLIS, click “Proceed to the NASA Engineering Network to create a new “Lesson Learned” about this Standard” to be vetted and approved in that process. Then, associate the lesson by clicking “Create a new “Lessons Learned” record for this Standard.”


-No Lessons Learned are associated with this standard.