sd-22-dmsms

Guides DMSMS and obsolescence management for long-lived defense systems using the SD-22 five-step process.

5|1|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill sd-22-dmsms-jgsystemsconsulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sd-22-dmsms
Source: https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/sd-22-dmsms
Command: npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill sd-22-dmsms-jgsystemsconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-lived defense systems outlast the technology inside them, so parts, materials, and software lose their manufacturers and suppliers. This Skill gives an agent structured knowledge from the SD-22 DMSMS Guidebook to manage that obsolescence risk across a system's life cycle instead of reacting to shortages after they hit readiness and cost. ## Core Features & Use Cases - Five-Step Process Guidance: Covers Prepare, Identify, Assess, Analyze, and Implement plus the Strategize overlay, including standing up a DMSMS Management Team (DMT) and Management Plan (DMP). - Risk-Based Monitoring: Explains the two-filter prioritization, the risk cube (criticality, supply-chain vulnerability, time to resolve), predictive tools, vendor surveys, and GIDEP/DLA product discontinuance notices. - Resolution Costing and Funding: Details resolution categories (existing material, substitutes, redesign), AoA/BCA comparison on net present value, life-of-need buy sizing, modification funding, and the ECP process. - Use Case: A sustainment engineer asks how to handle a flagged obsolete component; the agent walks through the Assess gate (need, timing, level), a health assessment with days-of-supply, and a costed resolution comparison. ## Quick Start Ask the agent to use the sd-22-dmsms skill to explain how to assess and resolve an obsolescence issue flagged on a system component.

Frequently Asked Questions about sd-22-dmsms

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

FAQPage Schema
How do I manage DMSMS and obsolescence for a defense system?

Follow the SD-22 five-step process: Prepare (stand up a DMT and DMP), Identify (risk-based monitoring), Assess (need, timing, level), Analyze (cost and compare resolutions), and Implement (fund and execute). A continuous Strategize overlay wraps all five steps.

What is the risk cube in DMSMS monitoring?

The risk cube scores uncategorized items on three axes: item criticality, supply-chain vulnerability, and time to resolve. Only items high on all three earn proactive monitoring, since monitoring everything is prohibitively expensive.

Does an obsolete part always need a resolution?

No. Obsolete is an input, not a conclusion. No resolution is needed if stock covers demand to retirement or refresh, reclamation suffices, or demand is gone. Software-license and information-assurance lapses are the exception requiring immediate action.

How do I choose between DMSMS resolution options?

Enumerate options top-to-bottom (existing material, substitutes, redesign), build total cost from applicable cost elements, compare on net present value via AoA or BCA, then weight technical, supply-chain, financial, and schedule risk and discard dominated options.

What are the limitations of this DMSMS knowledge pack?

It synthesizes the SD-22 FY24 working draft, so section numbers may shift in the final release. It does not teach general systems engineering, parts-management standards like SD-19, contracting law, or reproduce DoD policy text, tables, or figures.