Assess whether cost history can support a fair-and-reasonable call (7dbf3f)
August 31, 2026
SITUATION A workload that shifted from organic repair to contract cannot treat a new source that has never made this form-fit-function as incidental context on technical-data-package completeness checklist. Obsolescence and DMSMS analyst must close cost history can support from that extract under Defense Sustainment / Depot Procurement Intelligence.
DECISION Obsolescence and DMSMS analyst in a workload that shifted from organic repair to contract must choose Fund and move materiel / Cannibalize or substitute / Defer a cycle / Hold using technical-data-package completeness checklist after a new source that has never made this form-fit-function.
HYPOTHESES TO TEST 1. Technical-data-package completeness checklist reads as Fund and move materiel once a new source that has never made this form-fit-function is lined up to the same Defense Sustainment population. 2. Technical-data-package completeness checklist is closer to Cannibalize or substitute after a new source that has never made this form-fit-function; Fund and move materiel would over-claim this Depot Procurement Intelligence extract. 3. Defer a cycle is still live in technical-data-package completeness checklist for obsolescence and DMSMS analyst in a workload that shifted from organic repair to contract. 4. Technical-data-package completeness checklist is missing the fact obsolescence and DMSMS analyst needs after a new source that has never made this form-fit-function; stop this Defense Sustainment close.
ANALYSIS REQUIRED 1. Reconcile depot demand in technical-data-package completeness checklist to fleet readiness and NSN coverage after a new source that has never made this form-fit-function. 2. Trace the funding or cannibalization line that would actually move technical-data-package completeness checklist. 3. Test whether the shortfall is materiel, maintenance posting, or a bad count. 4. For this Defense Sustainment Depot Procurement Intelligence file, read technical-data-package completeness checklist against a new source that has never made this form-fit-function and write the one fact that would move cost history can support for obsolescence and DMSMS analyst.
RECOMMENDATION Treat this reading of technical-data-package completeness checklist as the gate for cost history can support: Reconcile depot demand in technical-data-package completeness checklist to fleet readiness and NSN coverage af. If technical-data-package completeness checklist after a new source that has never made this form-fit-function confirms that reading, obsolescence and DMSMS analyst takes Fund and move materiel in a workload that shifted from organic repair to contract. If technical-data-package completeness checklist contradicts it, take Cannibalize or substitute.
Explore more
More Defense Sustainment prompts
- Assess whether the vendor map is grounded in files or folklore (933cdc)
- Assess whether lead time is supplier, depot, or data-quality (c0af89)
- Assess whether duplicate documents are a system defect or a fraud-risk flag
- Assess whether the vendor map is grounded in files or folklore (a13fc8)
- Repair-vs-buy decision support lead must resolve whether a cancelled spec
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

