DIDs.pdf
PDF 943 KB Posted
- Attached to
- Overhaul of KC-135 Rate of Flow Transmitter
- Solicitation number
- FA811720R0015
View the file
Other files
| File | Type | Posted |
|---|---|---|
| FA811720R0015_______0002.pdf | ||
| FA811720R0015_______0001.pdf | ||
| FA811720R0015.pdf | ||
| TRNSPDATA_REPORT.pdf | ||
| PKGRQMT_REPORT.pdf | ||
| CDRL1_REPORT.pdf | ||
| PWS.pdf |
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
DATA ITEM DESCRIPTION
Title: CONTRACT DEPOT MAINTENANCE (CDM) PRODUCTION REPORT
Number: DI-PSSS-81995 Approved Date: 20150904 AMSC Number: 9576 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFMC/A4) Project Number: PSSS-2015-009 Applicable Forms: N/A Use/Relationship: The Contract Depot Maintenance (CDM) Production Report is a two-part report which provides the Government with monthly maintenance production figures, status and accountability of assets at the contractor facility, performance to schedule, anticipated production for the next month, and a summary of unresolved problems at the end of the report period.
a. This Data Item Description (DID) contains the format, content and preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.
b. This DID may be used on any depot level maintenance contract.
Requirements:
1. Format. This report shall be provided in the format of Table I.
2. Content. The report shall consist of two parts and contain the following information:
a. Part I:
(1) As of date: The year, month and day applicable to the report. Data must be through the end of the month.
(2) Block 1, Issuing/Procuring Agency. Include address and Point of Contact.
(3) Block 2, Contractor and activity address code (AAC). The name of the business and the DoDAAC assigned to your business for shipment of material.
(4) Block 3, Contract number and Program or Weapon System supported.
(5) Block 4, Government item manager or technical Point of Contact.
(6) Block A, Item identification. The National Stock Number (NSN), A-1 is the Federal Supply Class (FSC) and A-2 is the National Item Identification Number (NIIN) of the item being reported.
(7) Block B, Delivery/Call Order number. When the awarded contract is a call/delivery order type, this is the applicable order number. When an item is awarded on more than one order, it is repeated for each order until completed. If the current report completes the call, the word “completed” will be added.
(8) Block C, The contract line item number (CLIN). The CLIN assigned to the NSN in the contract.
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
Source: https://assist.dla.mil -- Downloaded: 2016-04-12T17:42Z Check the source to verify that this is the current version before use.
DI-PSSS-81995
(9) Block D, The document/voucher number the item was received under. The document number listed on the shipping documentation the item was received against.
(10) Block E, Quantity on contract or call. E-1 is the quantity of the end items to be repaired on each call/delivery order or contract quantity when orders do not apply. E-2 is the total quantity scheduled for repair cumulative to date.
(11) Block F, Reparables received. Number of reparable items received for repair. F-1 is the quantity of reparables received during the report month. F-2 is the quantity of reparables received cumulative from the start of the contract through report month.
(12) Block G, Reparables inducted into repair during report month.
(13) Block H, Reparables on hand. Number of reparables on hand waiting induction into repair.
(14) Block I, Quantity produced. The quantity produced during the month.
(15) Block J, Serviceables shipped. Serviceables shipped from repair facility. J-1 is the serviceables shipped through report month. J-2 is serviceables shipped cumulative from start of contract.
(16) Block K, Serviceables on hand. The quantity of serviceables on hand awaiting shipping action.
(17) Block L, Quantity condemned. The quantity condemned. L-1 is the quantity condemned during report month. L-2 is the quantity condemned cumulative from start of contract.
(18) Block M, Forecast to complete. The quantity of items scheduled to be produced next month.
(19) Block N, Report date. Enter date of report.
b. Part II, Production problems. Report shall be in narrative format and only required if:
(1) Previous reports production forecast was not shipped.
(2) Current forecast does not equal contract scheduled quantity.
(3) Contract anticipates a problem in the near future.
TABLE I. Contract Depot Maintenance (CDM) Production Report format.
CONTRACT DEPOT MAINTENANCE (CDM) PRODUCTION REPORT Month and As-Of Date
(YYYYMMDD)
Part I
1. ISSUED BY: 2. CONTRACTOR AND ACTIVITY ADDRESS CODE 3. CONTRACT NUMBER/PRGM/WS 4. GOVERNMENT ITEM MANAGER OR TECHNICAL POC
DURING REPORT PERIOD/TOTAL TO DATE
A.
ITEM
IDENTIFICATION
B.
DELIVERY/
CALL NUMBER
C.
CONTRACT
LINE ITEM
(CLIN)
D.
DOCUMENT/
VOUCHER
NUMBER
E.
QTY ON
CONTRACT
OR
DO/CALL
F.
REPARABLES
RECEIVED
G.
QTY
IND TO
WORK
H.
REPS ON
HAND
I.
QTY
PROD
J.
SERVICEABLES
SHIPPED
K.
SERV ON
HAND
L.
QTY
CONDEMNED
M.
FORECAST PROD
N.
REPORT DATE
FSC NIIN
1 2 1 2 3 1 2 1 2 1 2
Part II, Production Summary
End of DI-PSSS-81995.
Title: COMMERCIAL ASSET VISIBILITY (CAV) REPORTING
Number: DI-MGMT-81838 Approval Date: 20110914 AMSC Number: N9211 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: SA/WSS 071.02 Applicable Forms: N/A
Use/relationship:
The Commercial Asset Visibility (CAV) application provides a web-based, automated method of tracking Government owned reparable assets as they flow through the repair cycle at the contractor's repair facility. The main purpose of CAV is to provide an inventory management system for reparable assets while they are at commercial repair vendors. CAV on the World Wide Web allows the contractor to report transactions as they occur. These transactions automatically update the CAV database. An integrated, relational database allows the commercial repair vendors to access their repair data to produce all of the required status and activity reports.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement, as delineated in the contract.
Requirements:
1. Format. The CAV System transactions are processed via the World Wide Web. Input formats and methodology are defined in the Contract Statement of Work.
2. Content. The Contractor reporting shall contain the following transactions, status code changes and report types, as described in the Contract Statement of Work:
A. Receipt of Asset
1) On Contract
2) Not on Contract
3) Procurement
4) "A" Condition
5) Rotable Pool
6) Loaned Asset
B. Inductions C. Items Awaiting Parts D. Re-inductions E. Completions F. Shipments
Source: http://assist.dla.mil -- Downloaded: 2019-05-06T18:27Z
DI-MGMT-81838
G. Bulk Shipments H. Proof of Shipment I. Items that are Beyond Economic Repair (BER) J. Survey/Scrap Items K. Reversals L. Report of Discrepancies M. Print DD Form 1348's N. Print Material Movement Documents O. Print CAV Inventory Labels P. Print Item Action Reports Q. Print Repair History Reports R. Print Condition Code Reports S. Print Awaiting Parts Report T. Print Proof of Shipment Reports U. Perform Item Maintenance V. Print Report of Discrepancies (RODs) W. Add and Delete Carriers
3. End of DI-MGMT-81838.
Source: http://assist.dla.mil -- Downloaded: 2019-05-06T18:27Z
Title: Technical Order Improvement Report and Reply Number: DI-TMSS-80229D Approval Date: 19991006 AMSC Number: F7356 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: F–MSG/ILMP Applicable Forms: AFTO Form 22 Use/relationship: a. This Data Item Description contains the format and content preparation in-structions for the data product generated by the specific and discrete task requirement as delineated in the contract.
b. This item is applicable to contracts where the contractor is responsible for operating and main-taining Air Force centrally-acquired and managed equipment according to procedures in published TOs. Additional information and guidance is contained in TO 00-5-1, available through the Internet at http://www.pdsm.wpafb.af.mil/toprac/to-syste.htm under the link to “Technical Orders.”
c. This data item supersedes DI-TMSS-80229C.
Requirements:
1. Format. Paper or electronic format (EF) AFTO Form 22, Technical Order Improvement Report and Reply, or message/e-mail containing the same information. Electronic forms are available from the web site listed above.
2. Content.
2.1. REPORT DATE. The date the Improvement Report Number is assigned.
2.2. Block 1, TO (Major Command or Equivalent). The complete address of the Administrative or Procuring Contracting Officer (ACO/PCO).
2.3 Block 2, TO (T.O. Manager). The address of the TO Manager responsible for the deficient TO as indicated in the TO Index. (Addresses are available on the Air Force TO System Information Internet Page, http://www.pdsm.wpafb.af.mil/toprac/to-syste.htm.)
2.4. Block 3, FROM (Product Improvement Manager or Equivalent). The address of the reporting organization's Quality Assurance function which reviewed and approved the form for submission.
2.5. Block 4, TECHNICAL ORDER DATA. The Technical Order Number (Record Positions (rp) 6-30) and the Improvement Report Number (rp 31-45). Only one character is used in each position.
Rp 5 is left blank. Capital letters and slashed zeros ( /0) (if completing by hand) are used. Specific entry formats:
a. TECHNICAL ORDER NUMBER. The basic TO number (only) as it appears on the title page. Parentheses and dashes are used, but not blanks. Unused positions through rp 30 are left blank. When a change affects a TO supplement, the supplement’s number is referenced in block 11A.
b. IMPROVEMENT REPORT NUMBER. All positions (rp 31-45) are alpha-numeric char-acters (only). Rp 31 is a pre-printed “2.” Rps 32-33 will be “4N” to indicate contractor submission.
Rps 34-38 will be the contractor’s Commercial And Government Entity (CAGE) code number from the H4/H8 cataloging handbooks. Rps 39-40 may be used for internal identification or may be ze-ros. Rp 41 is the last digit of the calendar year. Rps 42-44 are the sequential numbers (starting with
“001”) of the reports submitted in the calendar year. Rp 45 indicates the urgency category of the report (E for Emergency, U for Urgent or R for Routine – see TO 00-5-1 for definitions).
2.6. Block 5, BASIC DATE OF T.O. The first date appearing on the lower right corner of the TO Title page.
2.7. Block 6, DATE/NO. OF CHANGE. The change number and date, if any, appear just under the TO's basic date on the title page. If there is no change listed, block 6 may be left blank or have N/A entered.
2.8. Block 7, PAGE NUMBER. The first page affected by the proposed change. Additional pages should be indicated in Block 11A. For work cards, the routine number and card number (e.g., TR3.1, Card 2 of 3).
2.9. Block 8, PARAGRAPH NO. The number of the paragraph to be changed or which precedes added material, the grid number for microfiche, or the System/Subsystem/Subject Numbers (S/S/SN) for manuals using this system. When multiple paragraphs are affected, the range (e.g., 5-1 thru 5-5).
2.10. Block 9, FIGURE NO. Used when illustrations or tables are involved. "Table" is used before the number if applicable.
2.11. Block 10, AFTO 22 TYPE. Two check boxes indicating whether the AFTO Form 22 is being submitted to make a Correction to the TO (see TO 00-5-1, para 5-2.1 for definitions), or an Im-provement to procedures or processes which, while correct as written, can be performed bet-ter/faster/cheaper/safer, etc.
2.12. Block 11A, BRIEF SUMMARY OF DEFICIENCY AND RECOMMENDED CHANGE (Use continuation sheet, if needed). Completed as follows:
a. For work package TO reports, the first entry in this block is "APPLICABLE TO WP NUM- BER xxxxx."
b. Identity of the military system when this is not included in the TO number. If not a system, identity of commodities by Mission/Design/Series (MDS) or Type/Model/Series (TMS) and Na-tional Stock Number (NSN) or part number. Omitted for general purpose Methods & Procedures TOs (MPTOs).
c. Brief description of the TO deficiency and reason for change. When appropriate, identity or copy attached of the source document for changes in voltage, part number and so forth.
d. The recommended changes worded as closely as possible to the exact language which should appear in the corrected TO. If the correction will require engineering research or extensive verification, the type of correction ("Add more in-depth fault isolation procedures.") and a statement such as "Unable to develop at local level."
e. Continuation sheets, if needed, shall show the improvement report number in the upper right hand corner of each sheet. (The EF version of the AFTO Form 22, available from the ACO/PCO, includes a continuation sheet with automatic entry of the improvement report number.)
2.13. Blocks 11B & 11C, SAVINGS/YR – DOLLARS and SAVINGS/YR – MANHOURS. These blocks are for rough order of magnitude (ROM) estimates of annual saving (in dollars and man-hours) resulting from the TO change recommendation. If minimal or no savings are anticipated, leave the blocks blank.
2.14. Block 12, REPORTED BY (Initiator’s Signature, Off Symb, Phone). Signature, printed or typed name, and office symbol of the individual reporting the problem or enhancement. Telephone number (Defense Switched Network (DSN) number preferred, if available) where individual can be contacted during normal duty hours.
2.15. Block 13, APPROVED BY (Supervisor’s Signature, Off Symb/DSN). Same as Block 12 for the initiator’s supervisor.
2.15. Block 14, PIM OR EQUIVALENT (Signature/Off Symbol/DSN). Same as Block 12 for the Product Improvement or Quality Assurance representative who reviews and approves the form for submission.
2.16. Blocks 16 & 17, TO. These blocks contain the same addresses as Blocks 1 and 3. They are auto-filled by the EF version of the form.
3. (Information Only).
3.1. Block 15, MAJOR COMMAND ACTION. Blocks 15A through 15C are left blank unless the reported improvement/correction could cause a change in contract scope or cost. In this case, the blocks are completed by the Procuring or Administrative Contracting Officer (PCO/ACO). Reports are routed through the weapon system’s or commodity’s Lead Command point of contact for review (Blocks 15D through 15F), unless specifically exempted by the Lead Command.
3.2. PART II, Blocks 19 thru 27. Completed by the government during evaluation of the improve-ment report.
End of DI-TMSS-80229D.
TITLE: COUNTERFEIT PREVENTION PLAN
Number: DI-MISC-81832 Approval Date: 20110121 AMSC Number: 9181 Limitation:
DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NRO Applicable Forms: N/A
Use/Relationship: The Counterfeit Prevention Plan will be used by the procurement activity to determine and evaluate the effectiveness of the contractor’s counterfeit protection plan and award fee.
a. This Data Item Description contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements delineated in the statement of work.
b. This DID is related to Parts, Materials and Processes Selection List (PMPSL).
c. This DID is related to “As Designed” and “As Built” Parts List.
d. The Counterfeit Prevention Plan will be updated as counterfeiting methods evolve to include any new indicators, as well as new prevention processes needed (either discovered directly or provided by the Government).
1. The Counterfeit Prevention Plan shall be in contractor format and shall include the following, as a minimum:
a. Procurement practices and procedures to include procurement of all parts and materials from original qualified parts/materials equipment manufacturer (OEM) or it franchised/authorized distributor.
b. Procurement practices and internal processes used for exceptions to buying from
OEM or OEM franchised distributors in cases where items are no longer available including a process to qualify/certify non-OEM parts & materials.
c. Monitoring procedures to include the delivery of test results from random sampling and supply chains surveillance that does not assume any source is safe to identify possible penetration of OEM supply chain.
d. Training/certification program for receiving inspectors.
e. Process to verify counterfeit.
DI-MISC-81832
- 2 -
f. Processes to identify, store, and report counterfeit parts.
g. Process to ensure subcontracts contain the following requirements (As a minimum):
(1) Requirements to procure only from Original Equipment Manufacturer
(OEM) or OEM franchised distributors
(2) Procurement practices and internal processes used for exceptions to buying from OEM or OEM franchised distributors including a process to qualify/certify non-OEM parts & materials obtained
(3) Requirements to monitor supply (including delivery of test results from random sampling and supply chain surveillance that does not assume any source is safe) to identify possible penetration of OEM supply chain
(4) Training/certification program for receiving inspectors
(5) Process to verify counterfeit
(6) Processes to identify, store, and report counterfeit parts.
(7) Notification procedure (tailored to specific sub-contractor based on following Notification Procedure)
h. Self-audit of internal processes.
i. Monitor processes at all subcontractor levels processes and verify compliance through on-site audits.
j. Notification Procedure:
(1) Step 1: The contractor shall quarantine all suspect products pending further direction. The contractor shall provide a statement, with problem description, justifying why this is considered suspect and how it was detected. The contractor shall NOT notify the supplier that the items are suspected as being counterfeit items. However, consultation with the OEM is authorized. Make certain the parts and all members of the lot procured for use on this contract are stored in correct environmental controls. These parts need to be protected as evidence.
(2) Step 2: Contractors that identify suspect items shall immediately notify their customer that is the next link toward the prime contractor.
Notification shall be passed up the customer chain until reaching the prime contractor. The prime contractor shall immediately notify the cognizant Contracting Officer (CO) and Contracting Office Technical Representative (COTR) of all suspect items identified.
DI-MISC-81832
- 3 -
(3) Step 3: The contractor shall make certain that the original documentation is secured as evidence and maintain any and all documentation associated with the part to include:
a. Part information such as part identifying number, lot date code, manufacturer information and originator/point of contact information
b. Any information reflecting part procurement/acquisition traceability which should include a copy of the purchase order, any and all correspondence between the buyer and the supplier to include: e-mails, records of phone conversations and paper letters of correspondence
c. Part documentation from the purported original manufacturer, distributors and suppliers (certificate of compliance and certificate of conformance)
d. All visual examination and physical analysis/testing results and the technical data package showing that the parts passed the required screening and qualification tests
e. List of company products affected
(4) Step 4: Determine that the part is or is not counterfeit (Usually accomplished as part of root cause analysis of non-conforming parts and/or materials)
(5) Step 5: If the parts are found to be counterfeit, they shall be isolated and controlled pending direction from law enforcement.
(6) Step 6: The contractor shall provide any additional required information to the government’s investigation team
END OF DI-MISC-81832
DI-MGMT-81803
Title: Item Unique Identification (IUID) Marking Plan
Number: DI-MGMT-81803 Approval Date: 20110719 AMSC Number: 9124 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: 70 (OO-ALC) Applicable Forms: N/A Use/relationship: The Item Unique Identification (IUID) Marking Plan details the Contractor’s strategy to execute marking requirements identified in the Government Statement of Work (SOW)/Performance Work Statement (PWS)/Objectives, and/or Defense Federal Acquisition Regulation Supplement (DFARS). The Plan fully documents the scope of meeting MIL-STD- 130 DoD Standard Practice Identification Marking of U.S. Military Property, with the Contractor’s marking requirements, marking methodology/strategy, data management, quality assurance, facilities and marking equipment, technical data package requirements, data carrier symbols and print quality, and the master schedule to help the Government manage marking activities in a cost effective and timely manner. To ensure quality, validation, verification, and registration of items being marked, guidance may be gained from two documents: DoD Guide to Uniquely Identifying Items (Assuring valuation, Accountability and Control of Government Property) and DoD Guide to Item Unique Identification Quality. If the quality measuring methodology is non-responsive for desired marking methods, quality levels will be identified within this plan.
This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.
This DID may be applied in any contract which contains a requirement for marking parts and equipment with IUID Data Matrix symbols.
Requirements:
1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, will be as cited online at Acquisition Streamlining and Standardization Information System (ASSIST) Update at the time of the solicitation.
2. Format. Contractor’s format is acceptable.
3. Content. The Marking Plan will cover the following elements:
3.1 Describe the minimum item marking requirements
3.2 List/Detail items/assets to be marked within the scope of the plan.
3.3 Marking Methodology/Strategy
Source: https://assist.dla.mil -- Downloaded: 2017-01-24T19:24Z
3.3.1 Describe which type of marking methodology will be used (i.e., Direct or Indirect Part Marking, Data Plate Modification, etc.).
3.3.2 Describe the Imprint Method / Type of Label / Nameplate (i.e., Chemical Etch, Dot Peen, Laser, Thermal Transfer, Ink Jet, Photo Etch, etc.).
3.3.3 Marking Specifications.
3.3.3.1 Identify applicable engineering drawings requiring IUID marking.
3.3.3.2 Machine Readable Mark Generation Instructions.
3.3.3.2.1 Define the construct method (i.e. Construct 0, Construct 1, - 18S, 25S, or Construct 2
– 1P 1T.
3.3.3.2.2 Determine the Enterprise Identifier (EID) (i.e. Cage, DUNS, DoDACC/MAPAC, or
GS1).
3.3.3.2.3 Determine the level of serialization (i.e., Part, Lot, Batch, Enterprise, etc.).
3.3.3.2.4 If using Construct 1 – 18S, identify the sequence number generation process.
3.3.3.2.5 Determine other data elements required in the data matrix symbol (30P and 30T).
3.3.3.3 Determine the Human Readable Mark Generation elements to be included on the label.
3.3.3.4 For labels/nameplates, identify which type of material will be used for the creation of the Mark (i.e., Aluminum, Polyacrylic, Metal Foil, Polyester, Polyvinyl, Aluminum Foil, Stainless Steel, etc.).
3.3.3.5 Describe the overall layout of the Mark including (Reference Tech Data as applicable).
3.3.3.5.1 Size (Length, Width, Thickness, etc.).
3.3.3.5.2 Shape (Circle, Square, Rectangle, Rounded Corners, etc.).
3.3.3.5.3 Layout/Order (Location of Human and Machine Readable elements).
3.3.3.5.4 Marking Location on Asset .
3.3.3.5.5 Type of Lettering (Font, Font Size, Color, etc.).
3.3.3.5.6 Attachment Method (Adhesive, Screws, Rivets, Tags, Bag and Tag, Tags and Bands, etc.). For Tag, and Bag/Band and Tag items, provide evidence of why part could not be marked and Government concurrence.
4. Describe the contractor’s process for marking legacy parts, Government Furnished Property (GFP), and Property in Possession of Contractor (PIPC) including tooling.
4.1 Data Management.
4.1.1 Describe the systems required to incorporate Serial Number Tracking (SNT) and Parent/Child relationship if any and communicate the IUID data to the Program Manager.
4.1.2 Describe the contractors process/systems required to assign Unique Items Identifiers (UIIs) and register Unique Identification (UID) information to the Department of Defense IUID Registry.
4.1.3 Describe the contractors process/system used to identify and track all warranted items i.e. all items with an extended warranty (more than just the standard contract time and workmanship), provide length of warranty, and date entered service (i.e. via WAWF). Describe how the contractor will mark/use the IUID data on the package and shipping containers.
4.2 Quality Assurance.
4.2.1 Describe the verification process and any sampling techniques which ensure the Machine Readable Information (MRI) complies with applicable standards as prescribed in MIL-
STD-130.
4.2.2 Identify a format for reporting verification results to include pass/fail and any acceptance criteria from MIL-STD-130 in paragraph 5 titled Data Matrix symbol quality.
4.2.3 Describe the process for identifying and reporting deficiencies in the mark properties, as well as repair and replacement procedures.
4.2.4 Include UID Contract Data Requirements List (CDRLs) as part of the surveillance method or Quality Assurance processes.
4.2.5 Describe the contractors process used to document UII marking of legacy parts that an IUID Engineering Assessment completed when they are returned to the depot for repair, i.e., Repair Receiving Report (R3).
4.3 Facilities and Marking Equipment.
4.3.1 Describe the facilities, marking equipment, floor space, utilities, environmental and safety elements, etc. required to meet marking requirements on a production basis.
4.4 Technical data package requirements.
4.5 Master Schedule.
5.0 End of DI-MGMT-81803
Title: BILL OF MATERIALS (BOM) FOR LOGISTICS AND SUPPLY CHAIN RISK
MANAGEMENT
Number: DI-PSSS-81656B Approval Date: 20160901
AMSC Number: N9724 Limitation: N/A
DTIC Applicable: N/A GIDEP Applicable: No
Preparing Activity: SA Project Number: PSSS-2016-021
Applicable Forms: N/A
Use/relationship: The Bill of Materials (BOM) will provide information that can be used to establish the production status of parts used in a system. The BOM will also provide Diminishing
Manufacturing Sources and Material Shortages (DMSMS) management essential information that enables the identification, forecasting, mitigation, and management of Hardware and
Software obsolescence as a part of the Department of Defense (DoD) Program Manager’s Total
System Life Cycle Management responsibilities. The data will be used in DMSMS forecasting tools to allow for standard and efficient sharing of information on common items.
The BOM will also provide logisticians and supply chain risk managers with additional data they require to ensure supportability requirements and supply chain risks are identified or mitigated during the development of a system.
This Data Item Description (DID) contains the format, content, and intended use of information for the data product resulting from the work task described by the contract.
The data may be obtained during any program life cycle phase.
This DID supersedes DI-PSSS-81656A.
1. Format. The BOM shall be in a format similar to that of Figure 1.
2. Content. The BOM shall contain all of the information specified in Figure 1, with the path to the system level identified using the part/Next Higher Assembly method detailed in the table.
All fields shall be included. Fields which do not require data shall be left blank. The information shall be included to the lowest indenture level (component level) specified in the contract
Source: https://assist.dla.mil -- Downloaded: 2016-09-21T18:16Z
DI-PSSS-81656B
FIGURE – 1 Table 1: Field Definitions and Instructions
Field Name Definition Notes and Instructions Data Type
OEM Part
Number
The part number assigned by the Original Equipment
Manufacturer (OEM). This may be the same as the
Manufacturer’s number but more often than not it is different. Sometimes referred to the Configuration Part
Number or the Drawing Number
Required. Referred to as the
“Referenced Part” hereafter
Alphanumeric
OEM Name The full legal name of the entity that is providing the referenced part to the government. Sometimes referred to as the Prime Integrator or Prime
Required Alphanumeric
OEM CAGE Commercial and Government Entity (CAGE) code of the OEM
Required Alphanumeric (5)
OEM’s Address The physical address of the part’s OEM, including country
Required Alphanumeric
OEM’s Website The web address of the part’s OEM Required when the OEM has a website
Alphanumeric
OEM’s Facility
Clearance Level
The level of security clearance the OEM’s facility holds Required Alphanumeric
(None, Confidential, Secret, Top Secret)
Revision
Designator
The designator of the revision of the referenced part Required if assigned Alphanumeric
Software /
Firmware Version
The designator assigned to the version of software / firmware used on the referenced part
Required for all parts containing software or firmware
Alphanumeric
Indenture Level A number that represents the specific level of the top down structure specified on the Bill of Materials
Starts with the top level as one Numeric
Reference
Designator
A reference designator identifies the referenced part.
ASME Y14.44-2008 and IEEE-315-1975 provide details for the proper configuration and use of reference designators.
Required if assigned Alphanumeric
Find Number Find number refers to the ordinal number that gives an ID tag to the referenced part in a parts list (list of materials, bill of materials).
Required if assigned Alphanumeric
NHA Part
Number
The OEM Part Number of the referenced part’s parent (Next Higher Assembly (NHA)). If the referenced part is software or firmware then the
NHA is the item the software is used on
Required for all parts except the top level assembly
Alphanumeric
NHA CAGE CAGE code of the OEM of the NHA Required for all parts except the top level assembly
Alphanumeric (5)
Nomenclature The name or designation of the referenced part Required for all parts Alphanumeric
Quantity The count of the referenced part per NHA Required for all parts Numeric
NSN National Stock Number (NSN) of the referenced part Required if item has NSN assigned
Alphanumeric
COG Cognizance (COG) Code: A two-part alphanumeric designator used by the Navy to provide supply management information
Required if assigned Alphanumeric
Manufacturer’s
Part Number
The part number assigned by the actual manufacturer of the referenced item. This number will be used to monitor the part for obsolescence issues
Required (may be the same as the referenced part if the part is manufactured by the OEM)
Alphanumeric
Manufacturer’s
Name
The full legal name of the entity that actually manufacturers the referenced part
Required Alphanumeric
Manufacturer’s
CAGE
The CAGE code of the entity that actually manufacturers the referenced part
Required Alphanumeric (5)
Manufacturer’s
Address
The physical address of the part’s manufacturer, including country
Required Alphanumeric
Manufacturer’s
Website
The web address of the part’s manufacturer Required when the manufacturer has a website
Alphanumeric
Manufacturer’s
Facility Clearance
Level
The level of security clearance the manufacturer’s facility holds
Required Alphanumeric
(None, Confidential, Secret, Top Secret)
Alternate For The OEM part number of the item the referenced part is the alternate for
Required if the referenced part is an alternate to another pat in the
BOM
Alphanumeric
Assembly Type Identifies whether the item is Commercial Off the Shelf
(COTS), Non-Developmental Item (NDI), or
Developmental Item (DI)
Required if the part is an assembly considered COTS, NDI, or DI. See the definitions section of 48 CFR 2.101 for definitions.
Alphanumeric
(COTS, NDI, or
DI)
Batteries Indicates whether an item contains batteries. Required. If the referenced part contains batteries and is a subassembly, its NHA should indicate that it also contains batteries
Yes / No
Service Bulletin
Applicability
Information required to subscribe to service bulletin updates to the part’s software or hardware
Required if the part will have service bulletins issued against it
Alphanumeric
3. Media Requirement: The BOM shall be provided as an electronically editable, machine-readable, Comma Separated Values
(CSV) text file with alphanumeric fields enclosed in double quotation marks.
End of DI-PSSS-81656B
Title: TEARDOWN DEFICIENCY REPORT
Number: DI-PSSS-81534A Approved Date: 20160608 AMSC Number: F9670 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/EZSC) Project Number: PSSS-2015-024 Applicable Forms: N/A Use/Relationship: The Teardown Deficiency Report provides a factual narrative analysis of a deficiency which has been noted on equipment.
a. This Data Item Description (DID) is applicable when contractors are responsible for maintaining custodial records for government property being repaired.
b. This DID contains the format, content and intended use information for the data deliverable resulting from the work task described in the solicitation.
c. This DID supersedes DI-ALSS-81534.
Requirements:
1. Reference documents. None.
2. Format. The Teardown Deficiency Report shall be in the contactor’s format.
3. Content. This report shall include an analysis of the deficiency which includes cause of failure, recommended corrective action and recommendations for actions to prevent recurrence of the failure/deficiency, and the applicable category of the failure defined as follows:
a. Workmanship and non-conformance. Any deficiency (e.g., physical, chemical, electrical, functional) noted in materiel which is attributed to non-conformance to applicable specifications, drawing, standards, or Technical Order (TO); or workmanship during manufacture, repair modification or maintenance.
b. Material failure. The failure of an end item which was attributable to neither the repair nor the manufacturing process, but was due to an unpredictable failure of an internal component or sub-assembly.
c. No defect found/could not duplicate: Investigation of the exhibit revealed no deficiency.
Equipment conforms to specifications and TO standards and procedures.
d. Technical data, deficiency: Technical data (including TOs, drawings, and work specifications) was deficient or inadequate so as to cause the deficiency/failure on the item.
e. Field induced deficiency. Deficiency confirmed by the investigation to have been caused by operator error, i.e., wrong voltage applied, misaligned, maladjusted, mishandling, or not used for intended purpose.
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
Source: https://assist.dla.mil -- Downloaded: 2016-06-27T17:52Z
DI-PSSS-81534A
f. Maintenance deficiency. An unfavorable characteristic of an item that impedes the accomplishment of maintenance operations which results in excessive maintenance operations and/or in excessive maintenance man-hour consumption.
g. Design deficiency. A condition that limits or prevents the use of material for purpose intended or required where the material meets all other specifications.
h. Handling or shipping deficiency. A deficiency induced by improper handling or shipping, i.e., improper packaging, which prohibits the use for intended purpose.
i. Packaging specifications inadequate - not complied with. Unsatisfactory conditions including item damage resulting from improper packaging.
End of DI-PSSS-81534A.
Source: https://assist.dla.mil -- Downloaded: 2016-06-27T17:52Z
Title: GOVERNMENT PROPERTY INVENTORY REPORT
Number: DI-MGMT-80441C Approval Date: 20171101 AMSC Number: 9865 Limitation:
DTIC Applicable: No GIDEP Applicable: No Preparing Activity: MDA Project Number: MGMT-2017-059 Applicable Forms: None
Use/Relationship: This report enables the contractor to periodically provide to the DoD Service/Agency an inventory listing of Government Property (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the contractor’s possession (to include subcontractors) by contract.
This DID is applicable to all contracts where Government Property will be furnished by the Government (i.e., GFP) or acquired, fabricated, or otherwise provided by a contractor (i.e., CAP) in performance of a contract.
This DID contains the format and content preparation instructions for the data deliverable resulting from the work task described in the solicitation.
This DID supersedes DI-MGMT-80441B.
Requirements:
1. Format. The report shall be electronic .xls or .xlsx compatible.
2. Content. The report shall contain the following columns/data fields:
A. Contract Number B. Manufacturer CAGE Code (if known) C. Item Name D. Item Description E. Manufacturer Name F. Manufacturer Part Number G. Manufacturer Model Number H. Material Control Number (MCN) (if applicable) I. Serial Number J. National Stock Number (NSN) K. Quantity L. Unit of Measure M. Unit Acquisition Cost N. Location O. Sub Location (if applicable) P. Unique Item Identifier (as registered in the IUID Registry) Q. Type of Government Property (i.e., Government Furnished Property (GFP) or
Contractor Acquired Property (CAP) R. Classification of Government Property (i.e., Communication Security (COMSEC), Equipment (EQP), Material (MAT), Special Test Equipment (STE), or Special Tooling
(ST))
Source: https://assist.dla.mil -- Downloaded: 2018-05-22T20:41Z
DI-MGMT-80441C
S. Posting Reference T. Date of Transaction / Date of Acquisition U. Date Placed in Service V. Date of Last Physical Inventory W. Condition Code
END OF DI-MGMT-80441C
Source: https://assist.dla.mil -- Downloaded: 2018-05-22T20:41Z
Title: ENGINEERING CHANGE PROPOSAL (ECP)
Number: DI-SESS-80639D Approval Date: 20150407
AMSC Number: N9521 Limitation: N/A
DTIC Applicable: No GIDEP Applicable: No
Preparing Activity: NM Project Number: SESS-2015-011
Applicable Forms: DD Form 1692, Engineering Change Proposal (ECP)
Use/relationship: An Engineering Change Proposal (ECP) provides the documentation in which the engineering change is described and how the proposed change will be implemented.
a. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in paragraph 3.3.1 (1) of EIA-649-1 and the principles of EIA-649.
b. This DID may be used in conjunction with DI-SESS-80642, Notice of Revision (NOR). A requirement for
NORs should be contractually imposed in conjunction with this DID.
c. This DID supersedes DI-CMAN-80639C and DI-SESS-81880.
d. Copies of these standards are available online at http://www.sae.org or from SAE International, 400
Commonwealth Drive, Warrendale, PA 15096-0001, Tel 877-606-7323 (inside USA and Canada) or 724-776-4970
(outside USA).
e. An electronic version of DD Form 1692, Engineering Change Proposal (ECP), is available online at http://www.dtic.mil/whs/directives/forms/index.htm.
1. Reference Documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2. Format. The ECP shall be in one of the following formats:
a. DD Form 1692, Engineering Change Proposal (ECP),
b. The schema required by the Acquirer’s Integrated Digital Environment (IDE), or
c. The Supplier’s preferred format.
3. Content. The ECP shall contain all the information in DD Form 1692.
End of DI-SESS-80639D
Source: https://assist.dla.mil -- Downloaded: 2015-05-19T14:32Z http://www.sae.org/ http://www.dtic.mil/whs/directives/forms/index.htm
Source: http://assist.dla.mil -- Downloaded: 2019-02-14T15:58Z
Source: http://assist.dla.mil -- Downloaded: 2019-02-14T15:58Z
| DID81995 |
| DID81838 |
| DID80229D |
| DID81832 |
| DID81803 |
| 1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, will be as cited online at Acquisition Streamlining and Standardization Information System (ASSIST) Update at the time of the solicitation. |
| 2. Format. Contractor’s format is acceptable. |
| 3. Content. The Marking Plan will cover the following elements: |
| 3.1 Describe the minimum item marking requirements |
| 3.2 List/Detail items/assets to be marked within the scope of the plan. |
| 3.3 Marking Methodology/Strategy |
| 3.3.1 Describe which type of marking methodology will be used (i.e., Direct or Indirect Part Marking, Data Plate Modification, etc.). |
| 3.3.2 Describe the Imprint Method / Type of Label / Nameplate (i.e., Chemical Etch, Dot Peen, Laser, Thermal Transfer, Ink Jet, Photo Etch, etc.). |
| 3.3.3 Marking Specifications. |
| 3.3.3.1 Identify applicable engineering drawings requiring IUID marking. |
| 3.3.3.2 Machine Readable Mark Generation Instructions. |
| 3.3.3.2.1 Define the construct method (i.e. Construct 0, Construct 1, - 18S, 25S, or Construct 2 – 1P 1T. |
| 3.3.3.2.2 Determine the Enterprise Identifier (EID) (i.e. Cage, DUNS, DoDACC/MAPAC, or GS1). |
| 3.3.3.2.3 Determine the level of serialization (i.e., Part, Lot, Batch, Enterprise, etc.). |
| 3.3.3.2.4 If using Construct 1 – 18S, identify the sequence number generation process. |
| 3.3.3.2.5 Determine other data elements required in the data matrix symbol (30P and 30T). |
| 3.3.3.3 Determine the Human Readable Mark Generation elements to be included on the label. |
| 3.3.3.4 For labels/nameplates, identify which type of material will be used for the creation of the Mark (i.e., Aluminum, Polyacrylic, Metal Foil, Polyester, Polyvinyl, Aluminum Foil, Stainless Steel, etc.). |
| 3.3.3.5 Describe the overall layout of the Mark including (Reference Tech Data as applicable). |
| 3.3.3.5.1 Size (Length, Width, Thickness, etc.). |
| 3.3.3.5.2 Shape (Circle, Square, Rectangle, Rounded Corners, etc.). |
| 3.3.3.5.3 Layout/Order (Location of Human and Machine Readable elements). |
| 3.3.3.5.4 Marking Location on Asset . |
| 3.3.3.5.5 Type of Lettering (Font, Font Size, Color, etc.). |
| 3.3.3.5.6 Attachment Method (Adhesive, Screws, Rivets, Tags, Bag and Tag, Tags and Bands, etc.). For Tag, and Bag/Band and Tag items, provide evidence of why part could not be marked and Government concurrence. |
| 4. Describe the contractor’s process for marking legacy parts, Government Furnished Property (GFP), and Property in Possession of Contractor (PIPC) including tooling. |
| 4.1 Data Management. |
| 4.1.1 Describe the systems required to incorporate Serial Number Tracking (SNT) and Parent/Child relationship if any and communicate the IUID data to the Program Manager. |
| 4.1.2 Describe the contractors process/systems required to assign Unique Items Identifiers (UIIs) and register Unique Identification (UID) information to the Department of Defense IUID Registry. |
| 4.1.3 Describe the contractors process/system used to identify and track all warranted items i.e. all items with an extended warranty (more than just the standard contract time and workmanship), provide length of warranty, and date entered service (i.e. via WAWF). Describe how the contractor will mark/use the IUID data on the package and shipping containers. |
| 4.2 Quality Assurance. |
| 4.2.1 Describe the verification process and any sampling techniques which ensure the Machine Readable Information (MRI) complies with applicable standards as prescribed in MIL-STD-130. |
| 4.2.2 Identify a format for reporting verification results to include pass/fail and any acceptance criteria from MIL-STD-130 in paragraph 5 titled Data Matrix symbol quality. |
| 4.2.3 Describe the process for identifying and reporting deficiencies in the mark properties, as well as repair and replacement procedures. |
| 4.2.4 Include UID Contract Data Requirements List (CDRLs) as part of the surveillance method or Quality Assurance processes. |
| 4.2.5 Describe the contractors process used to document UII marking of legacy parts that an IUID Engineering Assessment completed when they are returned to the depot for repair, i.e., Repair Receiving Report (R3). |
| 4.3 Facilities and Marking Equipment. |
| 4.3.1 Describe the facilities, marking equipment, floor space, utilities, environmental and safety elements, etc. required to meet marking requirements on a production basis. |
| 4.4 Technical data package requirements. |
| 4.5 Master Schedule. |
| DID81656B |
| DID81534A |
| DID80441C |
| AMSC Number: 9865 Limitation: |
| Requirements: |
| DID80639D |
| DID80969 |
| DID80736 |
File details come from the government source that posted it. Updated .