Att_(14)_DMSMS_Quarterly_Report__CDRL_LR0C__Rev_L_2013.02.15.docx
DOCX document 345 KB Posted
- Attached to
- CDL SRQ-4 Solicitation
- Solicitation number
- N00019-16-R-3001
About this file
Attachment (14) DMSMS Quarterly Report for CDRL LR0C
View the file
Other files
Show all 19
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
"Company Logo"
"System Name" "Production Phase" Production Support Services "Year"
DMSMS Parts Obsolescence Report For "Quarter, Year"
Document Number " " Document Revision " " Document Release Date "Month Date, Year"
DID Number " " Contract Number " " CLIN Number " " CDRL Number " "
Prepared For Department of the Navy Naval Air System Command (NAVAIRSYSCOMHQ) PMA-299 Attn: (Applicable name/code and office of PMA-299 POC) Building 2272 47123 Buse Road Patuxent River, Maryland 20670-1547
Prepared By "Company Name" "Company Address"
"Any additional company disclaimers"
DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; Reason: Administrative/Operational use; Date of Determination: October 1, 2007. Other U.S. requests for this document shall be referred to PMA-299. WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App 2401, et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate per the provisions of OPNAVINST 5510.161." Destruction Notice: For classified documents, follow procedures in DOD 5220.22M, National Industries Security program Operating Manual, Chapter 5, Section 7 or DOD 5200.1-R, Information Security Program Regulation. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.
| 24 Aug 2015 | LR0C ATTACHMENT 14 | RFP: N00019-16-R-3001 | |
| DMSMS QTRLY RPT | N00019-15-P1-PMA-299-0097 |
"Company Reference / Tracking Number"
Preliminary
DMSMS Parts Obsolescence Report Approval Signature and Date
"Company Project Lead" Date
"Company Technical POC" Date
"NAME" Date
"NAME" Date
RECORD OF CHANGES
| Change Number |
| Date |
| Title or Description |
| Enter by |
TABLE OF CONTENTS
| Approval Signature and Date……………………………… | i |
| Record of Changes……………………………………………ii | |
| Table of Contents……………………………………………...iii |
Section
| 1.0 | DMSMS Scope | 1 |
| 1.1 | DMSMS Definition | 1 |
| 1.2 | DMSMS Resolution Process | 1 |
| 2.0 | Report Guide per Solution | 2 |
| 3.0 | Obsolescence Summary by Platform, System, WRA, and | |
| SRA | 3 | |
| 4.0 | Obsolescence Issues Reporting | 4 |
| 4.1 | New, Unresolved, and Resolved Issues | 4 |
| 5.0 | DMSMS Issues | 7 |
| 5.1 | Planned Upgrades Due to DMSMS Issues | 7 |
| 5.2 | Proposed Upgrades Due to DMSMS Issues | 7 |
| 5.3 | COTS DMSMS Issue | 7 |
| 5.4 | Passive DMSMS Issues | 7 |
| 5.5 | Electro-Mechanical DMSMS Issues | 7 |
| 5.6 | Mechanical DMSMS Issues | 7 |
| 5.7 | Software DMSMS Impact Issues | 7 |
| 6.0 | Obsolescence surveillance | 7 |
| 7.0 | Obsolescence Tools | 7 |
| 8.0 | OCL (Obsolescence Case Log) | 7 |
| 9.0 | Monitored Parts List | 8 |
TABLE
| Table 1 | Report Guide per Solution | 2 |
| Table 2 | Obsolescence Summary by Platform, System, WRA, and | |
| SRA……….. | 3 | |
| Table 3 | Parts / Components / COTS / Subcontracted Assemblies | |
| Obsolescence Issues | 4-6 |
"Company Reference / Tracking Number" Table 4 Monitored Parts List… 8 iii
1.0 DMSMS SCOPE
This report published quarterly identifies in Table 2 new obsolescence issues and the Case Sheet Analysis to resolve them to minimize any impact to the "System Name and P/N (Part Number)". A status for all unresolved issues will be recorded in Table 2. Resolved issues will be recorded in Table 2. All tables completed need to be editable and not an imbedded image for all report submittals. All DMSMS (Diminishing Manufacturing Sources and Material Shortages) cases need to be input into a data base for record keeping, reporting, and retrieval purposes. The OCL (Obsolescence Case Log) in OMIS (Obsolescence Management Information System) is the data base for recording and tracking obsolescence cases. OCL training and access is provided by NAVSEA, NUWC Keyport. Components in the “System Name and P/N" that have been identified as having obsolescence issues will be included in the quarterly obsolesce report. Notification of obsolescence issues can be obtained from but not limited to component monitoring using commercial data bases, vendor surveys for COTs (Commercial off the Shelf) and contracted assemblies, and component alert notices issued by vendors. Prime contractors are responsible for monitoring and reporting obsolescence issues for assemblies supplied to them by sub-contractors. All tables are to be filled in when applicable and when data is available. If a Table can't be filled in due to missing data, provide a description as to why and when the data will be available.
1.1 DMSMS Definition
DMSMS is defined as the loss or impending loss of manufacturers or suppliers of items or shortages of raw materials. DMSMS may occur at any phase in the acquisition cycle, from design and development through post-production. DMSMS has the potential to severely impact weapon system supportability and life cycle costs.
The majority of DMSMS cases have historically been in the electronics area (primarily microcircuits). However, DMSMS problems affect all material categories. Furthermore, DMSMS problems are not always confined to piece parts. Material obsolescence situations may occur at the piece part / component, module / COTS (Commercial off the Shelf), equipment, or other system indentured levels.
1.2 DMSMS Resolution Process
"Company Reference / Tracking Number" Potential solutions will be evaluated based on the cost, impact, timeframe, and long-term support considerations. The evaluations will take into account changes to upcoming contracts to implement better DMSMS mitigation procedures. Considerations for a design refresh of scheduled improvement will also be evaluated. DMSMS solutions will be documented by completing a Case Sheet. The DMSMS Review Board (DMSRB) will ensure an appropriate review of all solutions has occurred and that the best solution is selected. Once approved by the Program Manager, the selected solution will be placed in the Program Objective Memorandum (POM) funding pipeline.
2.0 Report Guide per Solution
Table 1 "Report Guide per Solution" provides guidance as to what to do per solution.
Table 1 Report Guide per Solution
| Solution / Resolution |
| Table to fill out |
| OCL Entry |
| Case Sheet |
| Solution Cost |
| Solution Cost Avoidance |
| Weeks to Resolve |
| 1. Solution Not Required |
| Table 3 |
| N/A |
| N/A |
2. Original component
| 2a. - Continue to Manufacture (Extend Production) |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 2b. - Life of Type Buy (LOT Buy) or Bridge Buy |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 2c. - Existing Stock |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 2d. - Broker Market |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 2e. - Reclamation |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 3. Alternate |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 4. Substitute |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 4a. - Substitute due to ROHS |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 5. Aftermarket |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 6. Emulation |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 7. Reverse Engineering (Hybrids) |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 8. Redesign – Minor (ASIC) (Footprint of the board stays the same) |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 9. Redesign – Major (Footprint of the board changes) |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 10. Tech Insert/Refresh |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 11. Need More Research |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
12. COTS / Subcontracted Assemblies
| 12a. – No Action Required |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12b. - Design Longevity (DMSMS Support for Vendor) |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12c. - Extend OEM Maintenance Agreement |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12d. - Purchase 3rd Party Maintenance Agreement |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12e. – Life of Type Buy (LOT Buy) or Bridge Buy |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12f. – Alternate |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12g. - Tech Insert/Refresh |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12h. – Redesign/Integrated Change |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12i. – Purchase Data Rights |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
| 12j. – Reclamation Salvage |
| Table 3 |
| YES |
| YES |
| N/A |
| N/A |
ASIC (Application Specific Integrated Circuit ) ECP (Engineering Change Proposal) ROHS (Restriction of Hazardous Substances)
3.0 Obsolescence Summary by Platform, System, WRA, and SRA
Table 2 "Obsolescence Summary by Platform, System, WRA, and SRA" Provides an Obsolescence Summary at the Platform Level, System Level, the WRA (Weapon Replaceable Assembly) Level, and the SRA (Shop Replaceable Assembly) Level. Table 2 is meant as a quick look at the health of the SRAs, the WRAs, and the system along with what platform(s) the system is in. The color choices shouldn't be treated as set in stone and if you want to reclassify a part from green to yellow or red etc that is fine. The main thing is that any part with an obsolescence issue against it be documented in table 3. Monitored parts would be all parts that are part of any list that is being monitored by an obsolescence tool, plus COTS items that are being monitored with vendor surveys, plus any other parts that have been identified with obsolescence issues. Data for Table 2 can be obtained from OMIS if the system has been loaded into OMIS
| 4.0 | Obsolescence Issues Reporting |
| 4.1 | New, Unresolved, and Resolved Issues |
Complete Table 3 "Parts / Components / COTS / Subcontracted Assemblies Obsolescence Issues" for new obsolescence issues, for obsolescence issues still unresolved, and for obsolescence issues completed. List all NHAs affected by the obsolescence issue in Table 3.
Note: Table 3 is too wide to show on one printable page so it has been broken down into three tables. In the XCEL format Table 3 is contained in one worksheet.
5.0 DMSMS Issues
5.1 Planned Upgrades Due to DMSMS Issues
Provide a description and solution for planned ECP upgrades to CCAs due to obsolescence, part number changes, and redesigns.
5.2 Proposed Upgrades Due to DMSMS Issues
Provide a description and solution for proposed ECP upgrades to CCAs due to obsolescence, part number changes, and redesigns.
5.3 COTS DMSMS Issue
Provide a description and solution for COTS DMSMS issues due to obsolescence, part number changes, and redesigns.
5.4 Passive DMSMS Issues
Provide a description and solution for passive component DMSMS issues due to obsolescence, part number changes and redesigns.
5.5 Electro-Mechanical DMSMS Issues
Provide a description and solution for electro-mechanical component DMSMS issues due to obsolescence, part number changes and redesigns.
5.6 Mechanical DMSMS Issues
Provide a description and solution for mechanical component DMSMS issues due to obsolescence, part number changes and redesigns.
5.7 Software DMSMS Impact Issues
Provide a description and solution for software DMSMS issues due to software obsolescence, part number changes and redesigns.
6.0 Obsolescence Surveillance
"OEM Name" continues to monitor the "Program/System name" design for parts obsolescence. There is (are) a "Number" of part(s) in the design not currently obsolete that is (are) predicted to have a life expectancy of less than "Number" years. The part(s) is (are) a "P/N, Nomenclature, Manufacture" life expectancy of "Number" years. This part is used on the "NHA P/N & Nomenclature". Table 5 provides a listing of all parts in the system being monitored for obsolescence.
7.0 Obsolescence Tools
List Obsolescence tools being used for monitoring obsolescence status.
8.0 OCL (Obsolescence Case Log)
The OCL (Obsolescence Case Log) in OMIS (Obsolescence Management Information System) is the data base for recording and tracking obsolescence cases. OCL training and access is provided by NAVSEA, NUWC Keyport.
9.0 Monitored Parts List
a.) If a parts list has not been loaded in OMIS a part list showing parts being monitored and parts with obsolescence issues will be submitted in an excel spreadsheet with the columns as listed in Table 4.
b.) If a parts list has been changed since the last quarterly report a part list, highlighting the old P/N and the new P/N, will be submitted in an excel spreadsheet with the columns as listed in Table 4. Any part list changes will also need to be included in Table 3 with the applicable Table 3 columns filled in.
Table 4 Monitored Parts List
| NHA P/N |
| SCD P/N |
| Vendor P/N |
| Vendor P/N Cage Code |
| Vendor P/N QTY |
| Vendor P/N Description |
| Status (R,Y,O,G Gray) |
| Sourcing Issues and Recommended Resolutions |
Red (R): A part that is not in production by the original manufacturer. No FFF (Form Fit and Function) part is available that’s in production. High cost and high risk resolution due to redesign and requalification.
Yellow (Y): A part that is not in production by the original manufacturer. A FFF (Form Fit and Function) part is available that's in production. Qualification Issues, requires in circuit testing, minimal cost, minimal risk resolution.
ORANGE (O): A part that is still in production by the original manufacturer but a Life-of-Type buy date has been issued by the original manufacturer on the part. LTB cost, no risk resolution.
Green (G): A part that is still in production by the original manufacturer or an authorized aftermarket source i.e. Rochester Electronics, Lansdale, E2V/QP Semiconductor, etc. No cost, no risk resolution.
Gray (Gray): A part that is currently under research to determine its obsolesce status.
image1.png image2.png image3.png image4.png
File details come from the government source that posted it. Updated .