DMSMS FAQ: notifications, cases, and who does what
Blue Water Components · Updated November 2026
Short, sourced answers to questions DMSMS practitioners ask, drawn from DoDM 4245.15, SD-22, and SD-26. Blue Water Components built SONAR AI, AI that flags obsolescence, availability, and allocation risk across electronics and oddball hardware.
What is a DMSMS notification?
A DMSMS notification is an announcement that an item's production status has changed. DoDM 4245.15 defines it as an announcement "from a company or other source" and says the term covers "any verified or unverified notice of a change in production status." Notifications are commonly called alerts. Sources include product change notices (PCNs), product discontinuance notices (PDNs), monitoring results, GIDEP, DLA, and commercial services. Validated issues become DMSMS cases.
Where notifications come from
DoDM 4245.15's glossary lists the usual sources as "product change notices, product discontinuation notices, results of monitoring items for DMSMS issues, the GIDEP, DLA, and commercial services that specialize in compiling DMSMS information." SD-22 (December 2025), Section 4.4.4, says: "GIDEP does not have the ability to predict which parts will become obsolete, but it can provide a program office with a no-cost means to find out which NSN parts of interest already have discontinuation notices against them." The same section says "DLA also provides PDN alerts to subscribers." DoDM treats both verified and unverified notices as notifications. Validation comes next.
What happens after a notification arrives
DoDM 4245.15 §3.3.a(4) puts the work in this order:
- "Processing and compiling DMSMS notifications and associating notifications with the systems being monitored."
- "Validating initial DMSMS notifications as required."
- "Establishing DMSMS cases for all validated DMSMS issues."
- "Transmitting validated DMSMS issues to the GIDEP."
DoDM §2.6.j also has DoD Components share DMSMS issues "within 10 business days of occurrence… using… (GIDEP)."
Notifications on contract
SD-26 is guidance, not a mandate. It applies when a program office writes the language into the contract. Requirement 13 has the contractor notify the program office of "DMSMS issues and projected DMSMS issues within 1 week of discovering the issue" (SD-26, June 2026, p. 15). The illustrative CDRL in Appendix A, Figure 8 (p. A-7), uses
Element 55, Date of Notification, is the "Date the Product Discontinuance Notice (PDN) or Product Change Notice (PCN) was issued. If there is no PDN or PCN, use the date the DMSMS issue was discovered by the contractor." Element 57's examples include "discontinued production, planned end of life, product change, transferred to another company." The field list is on the
Why waiting for a notice isn't enough
DoDM 4245.15, Table 1, lists "Discontinuation notice not received" as one reason an issue is found only after the fact: items that depended on a notice "but which are determined to be obsolete after a failed attempt to purchase them." Blue Water Components built SONAR AI, AI that flags obsolescence, availability, and allocation risk across electronics and oddball hardware. The contracting guide is
Do out-of-stock parts need a DMSMS case?
Not automatically. DoDM 4245.15 defines a DMSMS issue as "the loss, or impending loss, of manufacturers or suppliers." A part that is backordered but still in production is usually a supply or lead-time problem. SD-22 (December 2025), Appendix A, treats allocation of a scarce item as a temporary DMSMS issue that can affect some systems and not others. Open a case when the shortage threatens your ability to produce or sustain the system, using the case criteria in your DMSMS Management Plan.
A DMSMS issue is not every supply problem
DoDM 4245.15 defines a DMSMS issue as "The loss, or impending loss, of manufacturers or suppliers of one or more items, raw materials, or software." A DMSMS case is "Documentation of a DMSMS issue and the status of that issue from its initial identification to the implementation of the selected resolution." A backorder on a part still being built is usually lead time, not the loss of a manufacturer. SD-22 (December 2025), Section 1.3, footnote 4, says DMSMS "encompasses 1) items that are not obsolete but where there are shortages and 2) obsolete items that are out of production and there is demand."
Situations the guidebook treats differently
Appendix A of that edition says: "An item may be obsolete, but if it is still in production, there is no DMSMS issue if the production capability or capacity can meet the demand." It also describes an obsolete item with enough stock: "a DMSMS case would be opened, but no resolution would be needed." And: "Some temporary DMSMS issues may be due to allocation of a scarce item. In this situation, some systems may be faced with a DMSMS issue, while others may not." That is not a clause to copy into a contract.
Your management plan decides
SD-22 (December 2025), Section 3.4.5, says: "A program office will need to document its approach (i.e., any criteria to be applied) regarding when to open an obsolescence case." It adds: "Ideally, a program office might want to open a case on every item for which there is an EOL notice, even if a resolution is not necessary." DoDM 4245.15 §3.4.c(1) asks whether the issue "warrants further action (e.g., stock on hand is insufficient to produce and sustain the system until the end of need)." If no action is needed, update the record and close the case. The criteria come from the plan and the contract, not from this page.
Out of stock can still be an early warning
SD-22 (December 2025), Section 4.3.2, lists "Persistent backorders (perhaps as indicated by an increasing number of backorders for at least eight consecutive months)," long customer wait times, and a "Recent substantial price increase" among signals that "may represent an early warning of future problems." They belong on a watch list even when they are not yet a case. That watch is what
Plan owner, DMT, and contractor
The plan owner is accountable for the DMSMS Management Plan, and the DMSMS management team does the work. The contractor usually has a representative on that team and may also write its own plan.
Why do resolutions cost more?
Resolutions cost more mainly because the later an issue is found, the fewer low-cost options remain.
Where the DMSMS community meets
The official name is the DMSMS and Parts, Materials, and Processes (PM&P) Working Group Meeting. In 2026 it takes place December 10–11 at the Broward County Convention Center in Fort Lauderdale, Florida. For the first time it is held alongside the SCRM-IC Summit as an associated meeting of the 2026 Department of War Maintenance Symposium. Registration runs through the symposium; see the WarU (formerly DAU) announcement for details.
Searchers sometimes call this the "2026 DMSMS and PM&P management forum." No official source uses that name. The
Free BOM check
Free BOM check: up to 100 line items, back in 2 business days. Send part numbers and manufacturers only, never quantities. Blue Water Components built SONAR AI to flag obsolescence, availability, and allocation risk on each line.
Or email
Commercial part numbers and manufacturers only. Please don't send quantities, CUI, ITAR or export-controlled technical data, drawings, or specs.
Frequently asked questions
A DMSMS notification is an announcement that an item's production status has changed. DoDM 4245.15 defines it as an announcement "from a company or other source" and says the term covers "any verified or unverified notice of a change in production status." Notifications are commonly called alerts. Sources include product change notices (PCNs), product discontinuance notices (PDNs), monitoring results, GIDEP, DLA, and commercial services. Validated issues become DMSMS cases.
Not automatically. DoDM 4245.15 defines a DMSMS issue as "the loss, or impending loss, of manufacturers or suppliers." A part that is backordered but still in production is usually a supply or lead-time problem. SD-22 (December 2025), Appendix A, treats allocation of a scarce item as a temporary DMSMS issue that can affect some systems and not others. Open a case when the shortage threatens your ability to produce or sustain the system, using the case criteria in your DMSMS Management Plan.
DMSMS stands for Diminishing Manufacturing Sources and Material Shortages. DoDM 4245.15 defines a DMSMS issue as the loss, or impending loss, of manufacturers or suppliers of items, raw materials, or software. It covers electronics, mechanical parts, materials, and software, and it includes shortages of items that are not yet obsolete.
The official name is the DMSMS and Parts, Materials, and Processes (PM&P) Working Group Meeting. In 2026 it takes place December 10–11 at the Broward County Convention Center in Fort Lauderdale, Florida. For the first time it is held alongside the SCRM-IC Summit as an associated meeting of the 2026 Department of War Maintenance Symposium. Registration runs through the symposium; see the WarU (formerly DAU) announcement for details.
Related reading
Plan owner, DMT, and contractor Who pays for DMSMS resolutions DI-MGMT-82274A explained SD-26 (2026) explained DMSMS design health in source selection Supply chain early warning All DMSMS guides Free BOM check
Sources
DoDM 4245.15, Management of Diminishing Manufacturing Sources and Material Shortages (26 October 2022) SD-22, DMSMS Guidebook (December 2025), DLA ASSIST . Quotations on this page were checked against that edition. Also listed onWarU .SD-26, DMSMS and PM&P Management Contracting Guide (June 2026), DLA ASSIST DI-MGMT-82274A, DMSMS Life Cycle Management Data (25 February 2026), DLA ASSIST Defense Standardization Program, DMSMS DMSMS Knowledge Sharing Portal (DKSP) . Linked as a resource only.WarU, "Three Key Working Groups, One Symposium" (P. Pethel, 5 November 2026)
Not legal or contracting advice; your contract governs. Blue Water Components is not affiliated with or endorsed by DSPO, WarU, or the Department of War.
