DI-MGMT-82274 Rev A explained: what DMSMS data you owe
Blue Water Components · October 21, 2026
DI-MGMT-82274, DMSMS Life Cycle Management Data, is the DoD data item description that defines the tabular DMSMS data a contractor delivers under a CDRL: BOMs, product change and discontinuance notifications, case data, monitored parts lists, and mitigation, cost, and budgeting data. Revision A (25 February 2026) expands Table 1 to 61 data elements and requires CSV delivery.
This page walks through what the DID requires, what changed from the 2019 base document, how SD-26 (June 2026) uses it in CDRL templates, and who delivers what. Our company, Blue Water Components, built a DMSMS and obsolescence software tool named SONAR AI, and we wrote this guide for the people who get handed a CDRL that cites 82274 or 82274A.
DI-MGMT-82274 at a glance
- Title: Diminishing Manufacturing Sources and Material Shortages (DMSMS) Life Cycle Management Data.[1]
- Current revision: Revision A, 25-FEB-2026, 14 pages. The base document is dated 02-JUL-2019, 11 pages. Both are Distribution Statement A.[1]
- Preparing activity: OSD-SO. Project MGMT-2026-002; AMSC 10619. ASSIST lists the next review as due 24-FEB-2031.[1][2]
- Scope: "Those activities may require collecting Bill of Materials, DMSMS notifications, DMSMS case data, DMSMS health information, DMSMS cost and budgeting information, and DMSMS case mitigation data…" (Use/relationship).[2]
- Where to get it:
ASSIST QuickSearch, DI-MGMT-82274 .
What the DID actually requires
One table, many deliverables. The DID defines a single Table 1 of data elements, and each CDRL picks the elements it needs. Use/relationship, paragraph d: "This DID should be tailored in the Contract Data Requirements List (CDRL) to include only the required specific data elements from Table 1."[2]
Format (Requirements, paragraph 3). The data goes in "tabular format with the Field Names in Table 1 as the column labels," provided as "an electronically editable, machine-readable, Comma Separated Values (CSV) text file with text fields enclosed in double quotation marks."[2]
Content (paragraph 4). Blank fields are allowed only for data that "is not available and which are not designated as 'Required'" in Table 1. The indentured path to the system level uses "the item/Next Higher Assembly (NHA) method." Data goes "to the lowest indenture level (component level) for all items, including subcontractor items, which are not commercial items, as defined in 48 CFR 2.101."[2]
"Item" means everything. Use/relationship, paragraph b: the word item "includes parts, software, materials, chemicals, etc."[2] Software and firmware are in scope: element 6, Software / Firmware Version, is "Required for all items containing software or firmware."[2]
Table 1 examples. Elements 1 to 5 identify the item and its source: OEM Item Number, OEM Name, OEM CAGE, UEI (the SAM-issued Unique Entity Identifier, a 12-character alphanumeric field), and Revision Designator. The last block of the table, elements 55 to 61, carries the notification data: Date of Notification, Notification Number, Notification Description, Recommended Replacement Item, Affected System, Last Order Date, and Last Ship Date.[2]
Element subsets by data product. Use/relationship, paragraphs d(1) to d(5), list the Table 1 elements for each use. Both columns are taken from the official DIDs.[2][4]
| Data product (CDRL subtitle) | Rev A Table 1 elements | 2019 base (DI-MGMT-82274) elements |
|---|---|---|
| Proactively monitored parts list | 1–6, 8–12, 17–21, 25–32 | 1–5, 7–11, 15–19, 24–25 |
| Bill of Materials | 1–33 | 1–26 |
| Product change and discontinuance notification | 1–3, 12, 17–21, 52–61 | 1–3, 11, 15–19, 44–53 |
| DMSMS case data | 1–21, 24–54 | 1–19, 22–46 |
| Case mitigation, cost, and budgeting | 1, 2, 10–13, 17, 26–32, 34–52 | 1, 2, 9–12, 15, 24, 25, 27–44 |
Health information. The scope mentions "DMSMS health information," but the DMSMS Health Assessment Report itself is a separate DID, DI-MGMT-82273 (SD-26 Table 7, Template 10).[3]
What changed from 2019 to Rev A
We compared the official 2019 base (DI-MGMT-82274, approved 2 July 2019, 53 Table 1 elements) with Revision A (DI-MGMT-82274A, approved 25 February 2026, 61 elements).[2][4] Apart from the header data (DID number, approval date, AMSC number 10040 vs. 10619, and project number) and the element ranges in Use/relationship d(1)–d(5), the Use/relationship text and Requirements paragraphs 1–4 (including CSV format and subcontractor depth) are word-for-word the same in both. CSV delivery and component-level depth for non-commercial subcontractor items were already required in 2019. The changes are all in Table 1.
- Eight new elements, so everything after element 3 renumbered. The 2019 table ends at element 53 ("END OF DI-MGMT-82274"); Rev A ends at 61 ("END OF DI-MGMT-82274A"). Every CDRL subset shifted, as the table above shows. A CDRL Block 16 that cites "1–19 and 22–46" against 82274A pulls the wrong fields.[2][4]
- New identity and maintenance fields. Element 4, UEI (Unique Entity Identifier, SAM-issued), is Required. Element 15, LRU, asks whether the item is the lowest replaceable unit, required if the system has been provisioned.[2]
- Altered items are now tracked. New elements 27 to 31 ask whether an item is an altered item and, if so, for the original item number and the original manufacturer's CAGE, address, and website.[2]
- Item Class and Item Type were redefined. In 2019, Item Class was COTS or NDI and only required for assemblies considered COTS or NDI; Item Type was Component, Assembly, Material, or Software. In Rev A, Item Class (element 26) is COTS, NDI, MOTS, or Custom, required for all items except materials, and Item Type (element 32) is Software, Electronics, Electrical / Electromechanical, Mechanical, or Materials, each with a definition.[2][4]
- Monitoring Status is Proactive or Reactive (element 25), replacing Yes or No.[2][4]
- Alternates flipped direction. 2019's "Alternate For" was required if this item is an alternate for another BOM item. Rev A's "Alternate OEM Item Number" (element 24) lists the alternates for this item, comma-separated if more than one.[2][4]
- Lead Time was redefined. 2019: "the time between the manufacturers' receipt of an order … and the delivery of the product." Rev A (element 36): "the time between the contractor's order of the item … from the supplier and the receipt of the order." Still in months.[2][4]
- Case fields are now plainly Required, and a start date was added. In 2019, case fields were required "if a Case Number has been assigned" or "if a DMSMS issue has been identified." Rev A marks Case Status, Case Status Date, Case Description (formerly Case Status Description), Statement of Impact, Impact Date, and the Proposed Mitigation fields as "Required," adds element 41, Case Start Date, and adds a note that, without a case number, references to a case mean the item itself.[2][4]
- EOL gets a full date. 2019 EOL was month/year (mm/yyyy), with January for non-firm estimates. Rev A (element 53) is mm/dd/yyyy, with January 01 for non-firm estimates.[2][4]
- Smaller wording changes. Stock on Hand now counts inventory "held … either by or for the contractor" (2019: "owned by the contractor"). Status adds notes defining Researching and Pending Discontinuance. Affected System allows a comma-separated list of systems. Indenture Level asks for a list ordered by indenture level.[2][4]
How 82274 ties to SD-26 (June 2026) and your CDRLs
SD-26 is guidance, not a mandate. Its Foreword says, "I urge you to read it thoroughly and use it on all new contracts and modifications to existing contracts" (p. iv).[3] Programs tailor it, and it does not endorse any tool. For the bigger picture, see
SD-26 Table 7 (p. 53) lists the DMSMS CDRLs and DIDs, and Appendix A has "a CDRL template (which provides illustrative information for creating the CDRL by completing DD Form 1423)" for each.[3] Six of those CDRLs use DI-MGMT-82274:
- Template 4: DMSMS Bills of Materials (Requirement 8)
- Template 5: DMSMS Case Data (Requirements 14, 22a, 22c)
- Template 6: DMSMS Change and Discontinuance Notification Data (Requirement 13)
- Template 7: DMSMS Case Mitigation, Cost, and Budgeting Data (Requirement 23)
- Template 8: Proactively Monitored Parts List (Requirement 12)
- Template 9: DMSMS Issue Mitigation Data (Requirement 16)
Because one DID serves many CDRLs, the Block 3 subtitle is what tells them apart.
What the Appendix A templates say (all citing DI-MGMT-82274A):[3]
- BOM (Figure 6, p. A-5): elements 1–33. The first submission depends on the phase, for example "EMD—At CDR," or in sustainment, "60 days from the beginning of the contract." Updates are due "NLT 60 days after" configuration changes are finalized.
- Case data (Figure 7, p. A-6): monthly (MTHLY), first at 60DAC; elements 1–21 and 24–54.
- Notifications (Figure 8, p. A-7): report "within 1 week of discovering the issue"; elements 1–3, 12, 17–21, and 52–61.
- Mitigation, cost, and budgeting (Figure 9, p. A-8): data used to project resolution costs "for the next federal budget year and for the succeeding 5 years"; first delivery at 180DAC, then annually.
- Proactively monitored parts list (Figure 10, p. A-9): annually (ANNLY), first at 90DAC.
- Review time: the BOM, case data, mitigation/cost/budgeting, and PMPL templates (Figures 6, 7, 9, and 10) give the government 30 days to review and the contractor 15 days to incorporate comments (Block 8). Figure 8 (notifications) has no such note. Figure 11 (DMSMS Issue Mitigation Plan, p. A-10) gives the government 1 month to approve or disapprove and the contractor 30 days to resubmit or provide a final copy.
Ties to the SD-26 requirements we cover elsewhere. Requirement 12 (p. 15) says the contractor "shall use predictive tools" to forecast and monitor, and the PMPL template delivers those results under 82274A. See our guide to
A practitioner gotcha: element numbers in SD-26 don't all match Rev A.[3]
- Requirement 7, on flow-down (p. 11), still says subcontractor case data uses "data elements 1–19 and 22–46." Those are the 2019 numbers. Appendix A Figure 7 uses Rev A's "1–21 and 24–54."
- Figure 10's PMPL list (p. A-9) reads "1–6, 8–12, 17–21, 26–32," while the DID's own PMPL list is 25–32.
- Reference [17] lists DI-MGMT-82274A with the date July 2, 2019, which is the base document's date.
None of this changes what you owe, but it is easy to copy the wrong range. Before the first delivery, reconcile the element ranges in Block 16 against the DID revision cited in Block 4.
Who delivers what
| Party | What it does with 82274 data |
|---|---|
| Contractor (prime) | Prepares and delivers each tailored 82274 CDRL in CSV, to the component level, including non-commercial subcontractor items. Runs the risk analysis behind the PMPL, reports notifications within the CDRL window, maintains case data monthly, and projects resolution costs for the budget year plus 5. |
| Subcontractors | Through flow-down (SD-26 Requirement 7), provide BOMs "either to the contractor or directly to the government," provide notification of DMSMS issues "within 1 week of discovery," and report case resolutions. Case data delivered directly to the government uses 82274 Table 1.[3] |
| Program office (PMO) | Tailors the DID in the CDRL: selects elements and completes DD Form 1423 Blocks 3, 4, 10, 12, 13, and 16. Reviews and approves deliverables (Block 8), uses the cost data for budgeting, and, per SD-26, "must provide the necessary programmatic and logistics data, cost factors, and product roadmaps" (p. 20).[3] |
| DMSMS management team (DMT) | Government and contractor members work the case data and resolution decisions. SD-26: "Participation in DMT Meetings should be considered a necessity" (p. 20).[3] |
One tailoring note: SD-26 says that if the program office is "conducting DMSMS management activities and collecting case data using DI-MGMT-82274A," some of these reports "may not be needed" (Appendix A, Figures 9 and 10).[3]
How a BOM-level obsolescence check helps you produce 82274 data
Every 82274 deliverable starts with a clean, indentured BOM. The fields teams scramble to fill are the lifecycle and notification ones: Date of Notification, Notification Description, Recommended Replacement Item, Last Order Date, and Last Ship Date (elements 55 to 61).
SONAR AI flags obsolescence, availability, and allocation risk across electronics and oddball hardware, including mechanical parts and assemblies. That gives your team a prioritized starting point for the PMPL risk analysis, notification reporting, and new case openings. Availability counts too: a lead time that jumps from 6 to 26 weeks is a buy-now-or-wait signal worth surfacing before it becomes a case.
It won't write your CDRL for you, but it helps you assemble and sanity-check the data and gives your DMT a head start. See how the
Get a free BOM check
Get a free BOM check: up to 100 line items, returned within 2 business days.
Frequently asked questions
The DoD data item description "DMSMS Life Cycle Management Data." It defines a single Table 1 of data elements that CDRLs tailor to request DMSMS BOMs, monitored parts lists, product change and discontinuance notifications, case data, and case mitigation, cost, and budgeting data. It is Distribution A and available on ASSIST.
Revision A (DI-MGMT-82274A), dated 25 February 2026, 14 pages. It replaced the 2 July 2019 base document. ASSIST lists its next review as due 24 February 2031.
Table 1 grew from 53 to 61 elements, so every CDRL subset was renumbered. New fields include UEI, LRU, Case Start Date, and five altered-item fields. Item Class, Item Type, Monitoring Status, Lead Time, and EOL were redefined. CSV delivery was already required in 2019 and is unchanged.
Paragraph 3 requires tabular data with the Table 1 field names as column labels, delivered as "an electronically editable, machine-readable, Comma Separated Values (CSV) text file with text fields enclosed in double quotation marks."
Under 82274A, elements 1–33, per Use/relationship paragraph d(2), and SD-26 (2026) Appendix A, Figure 6. Under the 2019 base, the BOM range was elements 1–26.
Under Rev A, elements 1–21 and 24–54. The 2019 numbering was 1–19 and 22–46, which still appears in SD-26 (2026) Requirement 7. Match the range to the DID revision cited in Block 4 of your DD Form 1423.
No. SD-26 is a DSPO contracting guide, not a mandate. Its Foreword urges programs to use it on new contracts and modifications, and its Table 7 and Appendix A give illustrative CDRL templates that cite 82274A. Your contract's CDRL is what obligates delivery.
The contractor delivers it, including non-commercial subcontractor items down to the component level. Subcontractors provide BOMs, notifications, and resolutions through flow-down. The program office tailors and approves the CDRL, and the DMT uses the case data for resolution and funding decisions.
Whatever the CDRL says. SD-26's templates suggest case data monthly, notifications within 1 week of discovery, the PMPL annually with the first at 90 DAC, and mitigation, cost, and budgeting data annually with the first at 180 DAC, projecting costs for the budget year plus 5.
Run a BOM-level obsolescence check. Blue Water Components offers a free SONAR AI BOM check of up to 100 line items, returned within 2 business days.
Sources
- ASSIST QuickSearch, DI-MGMT-82274 document details (DLA):
https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=283245 - DI-MGMT-82274A, DMSMS Life Cycle Management Data (approved 25 February 2026), official PDF from ASSIST:
https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=283245 - SD-26, DMSMS and PM&P Management Contracting Guide (June 2026), DLA ASSIST:
https://quicksearch.dla.mil/qsdocdetails.aspx?ident_number=283456 - DI-MGMT-82274, DMSMS Life Cycle Management Data (approved 2 July 2019; AMSC 10040; project MGMT-2019-012), superseded base revision, official PDF.
Not legal or contracting advice; your CDRL governs. DI-MGMT-82274 and SD-26 are DoD and DSPO documents. Blue Water Components is not affiliated with or endorsed by DSPO or the Department of Defense.