FA811724Q0004_Attach_1_Exhibit_A_CDRL_Junction_Box.pdf

FA811724Q0007

REPAIR OF E-3 Autopilot Power Junction Box

PWS Appendix 1

Contract Data Requirements List (CDRL)

CDRL DID Description Frequency A001 DI-MGMT-81838 Commercial Asset Visibility (CAV)

Reporting See CDRL

A002 DI-PSSS-80441D Government Property (GP) Inventory Report Annual

A003 DI-TMSS-80229D Technical Order Improvement Report and Reply ASREQ

A004 DI-PSSS-81534B Acquisition and Sustainment Data Package (ASDP) See CDRL

A005 DI-MISC-81832 Counterfeit Prevention Plan See CDRL A006 DI-MGMT-80969 Production Surge Plan See CDRL A007 DI-PSSS-81656B Bill of Materials (BOM) for Logistics and

Supply Chain Risk Management Annual

A008 DI-SESS-80639E Engineering Change Proposal (ECP) ASREQ A009 DI-MGMT-81803A Item Unique Identification (IUID)

Marking Plan ASREQ

A010 DI-PSSS-81995A Contract Depot Maintenance (CDM) Monthly Production Monthly

DATA ITEM DESCRIPTION

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

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.

Title: Government Property (GP) Inventory Report Number: DI-MGMT-80441D Approval Date: 20200609 AMSC Number: 10184 Limitation: N/A DTIC Applicable: No GIDEP Applicable:

Preparing Activity: MDA Project Number: MGMT-2020-012 Applicable Forms: None

Use/Relationship: The Government Property (GP) Inventory Report enables the contractor to periodically provide to the Department of Defense (DoD) Service or Agency an inventory listing of GP (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the contractor’s possession (to include subcontractors) by contract.

This Data Item Description (DID) is applicable to all contracts where GP 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, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

This DID supersedes DI-MGMT-80441C.

Requirements:

Reference documents. None.

Format. The report shall be in an electronic .xls or .xlsx compatible format.

Content. The report shall contain the following column headers (i.e., data fields):

Contract Number Agency or Service Asset Identification Number (GFP Only) Contractor Asset Identification Number Item Description Manufacturer Part Number Manufacturer Model Number Manufacturer Serial Number National Stock Number (NSN) (if applicable) Quantity Unit of Measure Unit Acquisition Cost Unique Item Identifier (if registered in the Item Unique Identification (IUID) Registry;

GFP only) Asset Location Asset Sub-Location (if applicable) Type of Government Property (i.e., Government Furnished Property (GFP) or Contractor Acquired Property (CAP) Classification of Government Property (i.e., Communication Security (COMSEC), Equipment (EQP), Material (MAT), Special Test Equipment (STE), or Special Tooling

DI-MGMT-80441D

(ST))

Date of Last Physical Inventory

Federal Condition Code

END OF DI- MGMT- 80441D

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: Acquisition and Sustainment Data Package (ASDP) Teardown Deficiency Report

Number: DI-PSSS-81534B Approved Date: 20220809

AMSC Number: F10348 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: PSSS-2022-004

Applicable Forms: N/A

Use/Relationship: The Acquisition and Sustainment Data Package (ASDP) 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, or, when detailed analysis is required for components undergoing a teardown investigation.

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-PSSS-81534A.

Requirements:

1. Reference documents. None.

2. Format. The ASDP Teardown Deficiency Report shall be in a text searchable format. If a model (e.g., Cameo, CAD, etc.) is used for the analysis or resolution of problems, the model shall be embedded in its native format. The Data Objects/Attributes and Associated Metadata (DOAM) listing shall be in Microsoft Excel spreadsheet format in accordance with the template provided in the DOAM Specification attached to the contract. All data shall be in the English language.

3. Content. The Teardown Deficiency 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.

DI-PSSS-81534B

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.

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.

3.1 DOAM. The completed Teardown Deficiency Report template, provided in the DOAM Specification attached to the contract, shall comply with the format requirements (see 2. above) so that it can be ingestible into a Product Lifecycle Management (PLM) solution to ensure proper tying, tracing, and linking to the lowest component of the end item to which the delivered Teardown Deficiency Report Information is applicable. Any field that is not applicable shall be

End of DI-PSSS-81534B.

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).

Requirements:

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

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 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.

Requirements:

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

Title: ENGINEERING CHANGE PROPOSAL (ECP)

Number: DI-SESS-80639E Approval Date: 20200211

AMSC Number: N10140 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: NM Project Number: SESS-2020-003

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 specifies 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 EIA-649-1 and the principles of EIA-649 (Copies of these standards are available online at 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]).

b. This DID may be used in conjunction with DI-SESS-80642, Notice of Revision (NOR). A requirement for NORs and Specification Change Notices (SCN) should be contractually imposed in conjunction with this DID.

c. This DID supersedes DI-SESS-80639D.

d. An electronic version of DD Form 1692, Engineering Change Proposal (ECP), is available online at https://www.esd.whs.mil/dd/.

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, 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. or

c. format.

3. Content. The ECP shall contain all the information required by DD Form 1692.

End of DI-SESS-80639E

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.

Title: ITEM UNIQUE IDENTIFICATION (IUID) MARKING PLAN

Number: DI-MGMT-81803A Approval Date: 20200311 AMSC Number: F10164 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 16 (AFMC/A4NL) Project Number: MGMT-2019-028 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 contract document(s) and Defense Federal Acquisition Regulation Supplement (DFARS).

The purpose of the IUID Marking Plan is for the Contractor to identify and define, in detail, their IUID marking process and procedures to meet Government contract requirements in accordance with Military Standard (MIL- STD) -130, Identification Marking of U.S. Military Property, for item marking; MIL-STD-129, Military Marking for Shipment and Storage, for packaging marking; and the DoD Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property. (Copies of MIL-STD-130 and MIL-STD-129 are available online at: https://quicksearch.dla.mil/qsSearch.aspx, and a copy of the Department of Defense (DoD) Guide is available online at https://dodprocurementtoolbox.com/site-pages/overview-implementation.)

The IUID Marking Plan shall include item and packaging marking requirements and methodology, encoding correct data, data management, facilities use, marking equipment, data carrier symbols, registration, quality assurance, validation, verification, registration of items being marked, and a master schedule to help the Contractor manage marking activities in a cost effective and timely manner.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract document(s).

b. This DID is used on any contract that requires delivery of an IUID Marking Plan to the Government.

c. This DID supersedes DI-MGMT-81803.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, or revisions, shall be as specified in the contract.

2. Format. The IUID Marking Plan shall be in contractor-developed, Government-approved format. Spreadsheet format shall be used when marking multiple items with IUID.

3. Content. The IUID Marking Plan shall include the following, except when the data matrix mark containing IUID data is embedded in a data label or plate and is already documented in an approved drawing. In such cases, the requirements indicated with an asterisk (*) shall be omitted when describing the label or plate marking:

3.1 List the applicable reference document(s).

3.2 List the end items and components marked with IUID under the requirements of the contract document(s), including DFARS 252.211-7003. (Copies of DFARS clause 252.211-7003 can be obtained online at:

https://www.acquisition.gov/content/regulations.)

DI-MGMT-81803A

3.3 Describe the marking methodology, which shall include the following:

3.3.1* Marking method used for each item to be marked (e.g., by direct marking on the item’s surface, or by indirect marking on a plate or label attached to the item). The marking method may differ for each item.

3.3.1.1* When direct part marking is used, describe the methods used to apply the direct part mark.

3.3.2 Item Marking Specifications:

3.3.2.1 When engineering drawings incorporating the IUID marking requirement exist, list and associate each drawing with the items requiring IUID marking. If not, enter “N/A.”

3.3.2.2 Describe the following aspects of Machine Readable Mark generation:

3.3.2.2.1 IUID construct to be encoded in the data matrix. (e.g., Construct 1, Construct 2, or a specific, DoD-recognized IUID equivalent, which can be found at:

http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html)

3.3.2.2.1.1 When using Construct 1, state whether the item’s Original Equipment Manufacturer (OEM) serial number is part of the Unique Item Identifier (UII), and, if not, how the serial number component of the UII is established.

3.3.2.2.2 Type of Enterprise Identifier (EID) in the mark. (e.g., Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS), DoD Activity Address Code (DoDAAC), or Global Standards One (GS1)).

3.3.2.2.3 The data elements to be encoded in the data matrix symbol, other than those from which the UII is derived, if any.

3.3.2.3* Describe the characteristics of the label or data plate:

3.3.2.3.1* Type of material used for the label or plate. (e.g., aluminum, polyacrylic, metal foil, polyester, polyvinyl, aluminum foil, stainless steel, etc.)

3.3.2.3.2* Method used to mark the data on the label or plate for each item to be marked. (e.g., laser etching, thermal transfer on polyester label stock, photo anodized aluminum plate, etc.)

3.3.2.3.3* Size of the label or plate, including units. (e.g., length, width, thickness, etc.)

3.3.2.3.4* Shape of the label or plate. (e.g., circle, square, rectangle, rounded corners, etc.)

3.3.2.3.5 Illustrate the label or plate to show the Human Readable Information (HRI) and the location of the data matrix.

3.3.2.3.6* Location of the label or plate on the item, include an illustration or photo, if possible.

3.3.2.3.7* Human readable lettering. (e.g., serif, font, font size, color, etc.)

3.3.2.3.8* Attachment method. (e.g., adhesive, screws, rivets, etc.)

3.3.2.3.9* Type of adhesive used, if applicable.

3.3.3 The process for marking legacy parts and Government Furnished Property (GFP).

3.3.4 How Unit Packs, Intermediate Containers, and Exterior Containers shall be marked in compliance with the DFARS 252.211-7003; MIL-STD-129; International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 15434, Information Technology – Automatic Identification and data capture techniques – Syntax for high-capacity ADS media; and American National Standards Institute (ANSI) MH10.8.2, Data Identifier and Application Identifier Standard. (Copies of ISO/IEC 15434 can be obtained at:

https://www.iso.org. Copies of ANSI MH10.8.2 can be obtained at: https://webstore.ansi.org.):

3.3.4.1 Portable Data File (PDF) 417 two (2) dimensional (2D) stacked linear barcode symbol format.

3.3.4.1.1 For data elements encoded in a PDF417 on a unit pack’s packaging, the actual item’s data shall be provided, when possible. State the data elements to be encoded in the mark. Include a readable PDF417 barcode with the data encoded correctly; specify the data string encoded in the mark, including control characters; or both.

3.3.4.1.2 For data elements encoded in a PDF417 barcode on an Exterior Container, state the data elements to be encoded in the mark. Include a readable PDF417 barcode with correctly encoded data;

specify the data string encoded in the mark, including control characters; or both. The actual item’s data shall be provided, when possible.

3.3.5 The Quality Assurance (QA) processes for the item mark, which ensure the item’s Machine Readable Information (MRI) complies with MIL-STD-130.

3.3.5.1 Validation and verification. Include a description of the specific equipment used to perform validation and verification, and the sampling technique when 100% verification and validation is not planned.

3.3.5.2 Format and frequency. Identify a format and frequency for contractually-required reporting of validation and verification results, to include a pass or fail rating for each mark verified and each mark validated.

3.3.5.3 State where validation and verification is to be performed (i.e., contractor facility or sub-contractor facility).

3.3.5.4 Describe the process used for replacing any marks that fail a QA check.

3.3.5.5 State contract data item numbers from the Contract Data Requirements List (CDRL) that pertain to QA on IUID marks.

3.3.6 The packaging mark QA processes:

3.3.6.1 Describe packaging mark validation. In the absence of packaging mark validation software, a manual comparison of the encoded data string to the requirements of MIL-STD-129 shall be included.

3.3.7 Facilities and marking equipment to be employed:

3.3.7.1 State where item labels or plates are created (i.e., contractor or sub-contractor facility).

3.3.7.2 Describe marking equipment used, to include any potential environmental impacts of the marking process and procedures designed to mitigate the risks of potential environmental impacts.

3.4 Describe data management processes:

3.4.1 Identify the actions required to register the pedigree data for the items marked with IUID in the DoD IUID Registry, in accordance with DFARS 252.211-7003.

3.4.2 When the contract requires non-warranty repair of items designated for IUID, describe the processes to:

3.4.2.1 Assess the readability of the data matrix marks on the items received that are marked with a data matrix.

3.4.2.1.1 Re-mark items with unreadable data matrix marks, which encode the original UIIs. The descriptions shall address the following: Will the complete data plate be remade? Will an additive label be applied? Will the original data matrix be obliterated?

3.4.2.2 Determine whether unmarked items were previously assigned a UII, and, if the mark is detached from the item, ensure that the remarked item uses the original UII.

3.4.2.3 Assign and mark a UII on DoD-owned items requiring IUID, but not previously assigned a UII.

3.4.2.3.1 Register new UIIs using the Repairable Receiving Report in Wide Area Work Flow (WAWF).

3.5 Provide the Master Schedule for IUID marking, to include:

3.5.1 Target dates for:

3.5.1.1 First submission of the marking plan.

3.5.1.2 Government approval of the IUID marking plan.

3.5.1.3 Commencement of marking (first item).

3.5.1.4 First item acceptance by Government.

3.5.1.5 Any other key events.

3.5.2 When marking is contingent on non-recurring engineering actions or is to be sub-contracted, state the projected schedules related to those processes.

End of DI-MGMT-81803A

Title: CONTRACT DEPOT MAINTENANCE (CDM) MONTHLY PRODUCTION REPORT

Number: DI-PSSS-81995A Approved Date: 20201130

AMSC Number: F10209 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: 70 (419 SCMS/GUBA) Project Number: PSSS-2020-012

Applicable Forms: N/A

Use/Relationship: The Contract Depot Maintenance (CDM) Monthly Production Report 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.

This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.

a. This DID may be used on any depot level maintenance contract.

b. This DID supersedes DI-PSSS-81995.

Requirements:

1. Reference documents. None.

2. Format. The CDM Monthly Production Report shall be in the Table I format below.

3. Content. The CDM Monthly Production Report shall include the following data, provided by the Production Management Specialist (PMS) and the Contractor, through the end of the month:

3.1 Part I: Blocks 1 through 4 of the report shall contain the following information provided by the PMS:

a. As of date: The day, month, and year (DDMMMYYYY) applicable to the report. Data shall be through the end of the month.

b. Block 1: PMS’s name, PMS’s code, PMS’s email address, and PMS’s phone number.

c. Block 2: Contractor name, the Department of Defense Activity Address Code (DoDAAC) assigned to the contractor for shipment of material, the contractor’s Commercial and Government Entity (CAGE) code, the contractor’s email address, and the contractor’s phone number.

d. Block 3: Contract number and Program (PRGM) or Weapon System (WS) supported.

e. Block 4: Government item manager’s or technical Point of Contact’s (PoC’s) name.

3.2 Blocks A through O of the report shall contain the following information:

a. Block A: Item identification, which shall include the Federal Supply Class (FSC) under A-1, and the National Item Identification Number (NIIN) of the item being reported under A-2.

b. Block B: Delivery/Call Order number. When the awarded contract is a delivery/call order type, this is the applicable order number. When an item is awarded on more than one order, the order number is repeated for each order until completed. If the current report completes the call, the word “completed” shall be added.

c. Block C: The contract line item number (CLIN), which shall be the CLIN assigned to the National Stock Number (NSN) in the contract.

DI-PSSS-81995A

d. Block D: Q uantity on contract or delivery order (DO)/call

e. Block E: Reparables received, which shall be the number of reparable items received for repair, and shall include the q uantity of reparables received during the report month under E-1 and the cumulative q uantity of reparables received from the start of the contract through the report month under E-2.

f. Block F: Miscellaneous (Misc.) assets received that are not part of the contract, in various condition codes, which shall include the q uantity received during the report month under F-1 and the cumulative total received from the start of the contract through the report month under F-2.

g. Block G: Reparables (REPS) on hand, which shall be the number of reparables on hand waiting for induction into repair.

h. Block H: Total number of reparables currently inducted (IND) into work.

i. Block I: Q uantity of reparables awaiting parts (AWP).

j . Block J : Q uantity (Q TY) produced (PROD), which shall include the q uantity that completed repair and was produced during the report month under J -1 and the cumulative total that completed repair and was produced from the start of the contract through the report month under J -2.

k. Block K : Serviceables (SERV ) on hand, which shall be the q uantity of serviceables on hand awaiting shipping action.

l. Block L: Serviceables shipped, which shall be the number of serviceables shipped from the repair facility, and shall include the number of serviceables shipped during the report month under L-1 and the cumulative number of serviceables shipped from the start of the contract under L-2.

m. Block M: Q TY condemned, which shall include the q uantity of reparables condemned during the report month under M-1 and the cumulative q uantity of reparables condemned from the start of the contract under M-2.

n. Block N: Misc. Shipped/Condemned Shipped, which shall include the misc. assets received in Block F that are not part of the contract, in various condition codes or condemned assets shipped during the report month under N-1 and the misc. or condemned assets shipped from the start of the contract through the report month under N-2.

o. Block O: Next Month Forecast PROD, which shall be the q uantity of items scheduled to be produced next month.

3.3 Part II, Production Summary. A Production Summary shall be included only if:

a. The previously reported production forecast was not shipped,

b. The current production forecast does not eq ual the contract scheduled q uantity, or

c. The Contractor anticipates a problem with production in the near future.