skills.rest
jgsystemsconsulting
jgsystemsconsultingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

nasa-de-acquisition

Provides reference guidance for acquiring digital engineering data under NASA-HDBK-1004 contracts.

5|1|Updated Jun 19, 2026
Search Tags:#configuration management#data acquisition#nasa#mbse#drd#digital engineering#contract language
One-click install
npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill nasa-de-acquisition-jgsystemsconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nasa-de-acquisition
Source: https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/nasa-de-acquisition
Command: npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill nasa-de-acquisition-jgsystemsconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Programs buying digital and model-based engineering data often end up with unusable deliverables because contracts say "contractor format acceptable" or omit data requirements entirely. This Skill gives an AI agent structured reference knowledge from the NASA Digital Engineering Acquisition Framework Handbook (NASA-HDBK-1004) so it can answer questions about specifying, contracting for, and controlling digital data deliverables across the program life cycle. ## Core Features & Use Cases - DRD and contract-language guidance: Covers the Data Requirements Description instrument, the Appendix A DRD suite (TDP, MBx, CDMP, CSA, CR, FCA/PCA, REF, MRI), the Data Type 1-5 control scale, and SOW/RFP/Cost-Volume placement with FAR/DFARS data-rights categories. - Model-based data definition and interoperability: Explains MBSE, CAD/PMI, BOM views, release-state mapping, the four owned architectures, neutral formats (STEP/ISO 10303, JT), the four MBE interoperability use cases, and MBE Plan development. - Use Case: While drafting an RFP, ask the agent how to specify a Technical Data Package deliverable; it answers from reconstructed chapter notes with the right maturity level, MIL-STD-31000 grounding, and Data Type selection. ## Quick Start Ask the agent to explain how to write a DRD for a Technical Data Package deliverable using this knowledge pack.

Frequently Asked Questions about nasa-de-acquisition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I specify digital data deliverables in a NASA contract?▼

Use a Data Requirements Description (DRD) for each deliverable data item, assembled into a Data Procurement Document that rides alongside the SOW or PWS. Each DRD fixes the item's purpose, content, format, compliance standards, maintenance, and submission terms, expressed as milestones rather than calendar dates.

What is the Data Type 1-5 scale in NASA data acquisition?▼

The Data Type scale sets how much Government control a deliverable needs. Type 1 requires written approval before use, Type 2 allows a tailorable 45-day disapproval window, Type 3 is deliver-on-time, and Types 4 and 5 cover contractor-retained data delivered on request or inspected.

Does this pack include the text of ISO, ASME, or MIL-STD standards?▼

No. The pack only names third-party standards such as ISO 10303/STEP, ASME Y14, and MIL-STD-31000 and describes how the Handbook invokes them. Those standards remain copyrighted by their publishers and their text is not reproduced.

What is the difference between FCA and PCA configuration audits?▼

The Functional Configuration Audit verifies the item performs to its approved documentation, while the Physical Configuration Audit verifies the as-built item matches the as-designed configuration. Both audits feed establishment of the Product Baseline.

When should data rights be negotiated in an acquisition?▼

Data rights should be secured at the RFP front end while offerors still compete, with the same data approach placed in the SOW, the DRD, and the Cost Volume as a priced line item. Requirements deferred to closeout become sole-source negotiations with no competitive leverage.

What are the limitations of this NASA acquisition handbook knowledge pack?▼

The source is an acquisition handbook, so it is thin on practitioner-depth digital engineering technique; the companion NASA-HDBK-1009A carries that detail. Example DRDs and contract clauses are a starter library that must be tailored per program and reviewed by Legal and Procurement before binding use.

Related Skills

Explore More Product & Management Skills→
FS-GGFS-GG

fs-gg-sdd-plan

Structure technical implementation plans for FS.GG software development life cycle phases.

Official
Intermediate
hoavdchoavdc
21

codexkit-contract-risk-review

Extract clause-by-clause risks and obligations from commercial agreements.

Community
Intermediate
geekatrongeekatron
30

nasa-se

Orchestrate NASA Systems Engineering agents to produce verifiable NPR 7123.1D artifacts.

Community
Advanced
lawve-ailawve-ai
630

data-act-ryan-malek

Classify EU Data Act obligations and generate draft-ready outputs with verbatim citations.

Official
Advanced