CDRL_ExhibitA_3D Scanner_Final1.pdf

Exhibit A 3D Scanner

01 September 2022

LIST OF DOCUMENTS, EXHIBITS OR ATTACHMENTS

EXHIBIT A

CONTRACT DATA REQUIREMENTS LIST (CDRL) FOR

AIRCRAFT BATTLE DAMAGE REPAIR (ABDR)

PROGRAM HANDYSCAN 3D SCANNER WITH

REVERSE ENGINEERING SOFTWARE KIT/

SET

01 September 2022 Revision:

01 September 2022e

CONTRACT DATA REQUIREMENTS LIST (CDRL)

TABLE OF CONTENTS

CDRL GENERAL INSTRUCTIONS.………………………………………………………

CDRL - A001 - TEST/INSPECTION REPORT……………………………………………… 8

CDRL LIST............................................................................................................…

LIST OF ADDRESSES………………………………………………………………………….. 7

CDRLs DD FORM 1423-1..………………………………………………………………….….. 8

CDRL A002 - ITEM UNIQUE IDENTIFICATION (IUID) MARKINGS...………………… 13

DID - DI-NDTI-80809B - TEST/INSPECTION REPORT...………………………………. 9

DID DI-NDTI-80809B - TEST/INSPECTION REPORT.…………………………………. 9

01 September 2022

The following CDRL General Instructions are applicable for all services executed against the performance of this effort. The associated Data Item Description (DID) will be noted in the individual task description and any deviation to the below CDRL General Instructions will also be noted in the affected task description.

1. The Contract Data Requirements List (CDRL) identifies the data deliverables for the related Contract Line Item Numbers (CLINs) pursuant to the tasks defined in the Performance Work Statement (PWS).

2. Contractually binding instructions for data content and format preparation are in Block 10, “Preparation Instructions”, of the applicable Data Item Description (DID), and permit the easy segregation of content related to specific efforts. Tailored instructions are on the CDRL or backup sheets attached to this Task Order. In such cases, a “/T” (tailored) is suffixed to the DID number. The Contractor shall not deviate from the requirements of the DID, tailored or untailored, without receiving prior approval of the Procuring Contracting Officer (PCO).

3. The attached CDRLs were prepared using the following documents or websites for guidance and information:

a. “https//quicksearch.dla.mil” Quick Search is a public website that lets users search for defense and federal specifications and standards, military handbooks, commercial item descriptions, data item descriptions, MS detail drawings, Qualified Product Lists (QPLs), and related technical documents prepared in accordance with the policies and procedures of the Defense Standardization Program (DSP).

b. DoD 5010.12-M Chg. 1, Procedures for the Acquisition and Management of Technical Data, dated August 2018.

c. DoD Directive 5230.24, Distribution Statements on Technical Documents, dated Aug 2012

4. Unless otherwise specified, the submittal dates for the CDRLs are based on the effective date of the contract. Submittal dates falling on non-working days (Saturday, Sunday, legal holidays) shall be construed to mean the first working day following such non-working days. All submittal time periods (e.g., “30 days after Post Award Conference”, “5 days from comments”, etc.) shall be business counted days. Data that are dependent on events that may not occur during the performance of the contract will be submitted on an “as required” basis.

5. Unless otherwise specified, the submittal date is the date the data is required at the office specified in Block 6 or Block 16 of the CDRL. Distribution to other recipients of the data shall be made on or about the same date. In the event data is delivered electronically receipt confirmation by this office may be made on line.

6. Data Transmittal Form (DTF) shall contain the Contract number including the Task Order (TO) number, the CDRL sequence number, the date of transmittal, and the Contractor’s reference number. The DTF will identify the data by title and document number, as well as the type of submission (e.g., draft, final, resubmission of draft, change pages, etc.). It shall also include a list showing addressees, distribution made, and number of copies distributed. One information copy of all DTF’s shall be forwarded to AFLCMC/HBSLB. Receipt acknowledgement by means of endorsement and return at the DTF to the Contractor is required for classified documents only.

7. All correspondence relating to data items shall reference the contract number including the TO number and CDRL sequence number, and DID number.

8. Unless otherwise specified, an “A” in Block 8 of the CDRL indicates written approval by the PCO shall be provided before distribution of the final data. The Government will respond within

01 September 2022

45 days of receipt of the data, unless a different time period is specified on the CDRL. However, Government failure to respond to the Contractor within this 45-day period does not constitute Government approval of data deliveries and does not construe tacit approval of the initiation of an effort. Government written responses shall be provided in one of three categories only: (1) Approved as Written; (2) Approved with Comments; or (3) Disapproved. Data that is “Approved with Comments” shall be updated by the Contractor to incorporate the comments and resubmit within 30 days of receipt of the Government response, unless otherwise directed by the PCO or contract requirements. This resubmitted data shall be considered final and will not require further Government approval if the comments have been incorporated as provided. In the event the Contractor takes exception to any Government comments, these shall be addressed in writing to the Government.

9. In the event that a data submission is disapproved, the PCO will advise the Contractor of the reason(s) for disapproval. Disapproved data items shall be revised to address/include the comments, and shall be resubmitted (or change pages provided) to the Government as noted above. These re-submittals, or change pages, shall not be regarded as subsequent submittals as specified in Block 13 of the CDRL, unless the next submittal of the CDRL is scheduled such that this would be a duplication of effort. (For example, an item submitted 90 days prior to test, which is disapproved and is due again 30 days prior to test, would be revised to address/include the comments in the next scheduled submittal.) The Government will review the changes the Contractor has made to the data addressing Government comments/disapproval, and will limit subsequent review(s) to address only those changes (with the exception of those instances where comments are incorporated in the next scheduled submittal).

10. In the absence of an “A” in Block 8 of the CDRL, it is understood that the Government has the inherent right to approve/disapprove any data submittal which does not meet the contractual requirements of the DID, tailored or untailored.

11. The Contractor will take care not to unnecessarily duplicate data previously procured by the Government, except to provide required copies to newly established recipients under this contract. Instances of unnecessary duplications should be identified to the COR. The Contractor is encouraged to recommend deletions, additions, substitutions, consolidations, and use of existing Contractor formats for data when such actions will aid the Government in obtaining minimum essential data in a timely and cost-effective manner.

12. For delivery orders that have codes DD, DS, SD or SS in Block 7 of the CDRL require the processing of a DD Form 250, Material Inspection and Receiving Report. If none of these codes are present in Block 7 then a DD Form 250 is not required for that data item. The code letter “S” indicates “Source” and refers to the Contractor’s facility; the code letter “D” indicates “Destination”. The first code letter indicates the point of preliminary inspection (for count, style, format, legibility, reproducibility, etc.). The second code letter indicates the point of formal acceptance (on DD Form 250). In cases where draft copies are required, the draft copies shall be provided by a DTF. A DD Form 250 is required only for transmittal of the final copies to the office identified in Block 6 of the CDRL. In addition, a final DD Form 250 shall be provided at the completion of all final CDRL deliveries against applicable sub-CLINs.

13. Requirements for periodic revisions to data, where no changes have occurred since the date of last submission, maybe satisfied by a DTF stating that, “No changes have occurred since the last submission”. Requirements for submittal of data “if changed”, where no change has occurred prior to the submittal requirement, may be satisfied by a DTF stating that, “No change has been made to the data to date.” In such cases, the Contractor will identify the data in question, and the reporting period.

01 September 2022

14. Distribution Statement requirements are specified in Block 9 of the CDRL. The code letter corresponds to the Distribution Statement to be marked on the technical data item by the Contractor. An abbreviated form of the Distribution Statement will be placed in Block 16 of the CDRL. The following are the code letters applicable to this CDRL, with the corresponding Distribution Statement (see Block 9 on CDRL Explanation Page).

15. The Contractor will be notified in writing of any of the following changes to Block 14 of the

CDRL:

a. Place of delivery

b. Technical office symbol

c. Increase or decrease in addressees

d. Increase or decrease in the number of copies (regular or reproducible) specified for any addressee

The written notification will include redlined CDRLs. The Contractor may use this written notification as its authority until the issuance of a contract modification incorporating the CDRL change. There is no contract price change for changes (a) or (b). “There is no contract price change for changes (c) or (d), provided that either type of increase or decrease for an individual CDRL is not greater than 50% of what was initially specified. The Government and Contractor will negotiate any equitable adjustments in the event that the change is greater than 50%.

Questions regarding preparation and content of the CDRLs may be directed to AFSC/LZDB, MSgt Kyle Sommerfeldt (937) 904-1356 or the PCO AFSC/PZIEC Richard L.

Fenton (405) 734-5072.

01 September 2022

CONTRACT DATA REQUIREMENTS LIST (CDRL)

CDRL DATA ITEM

DESCRIPTION (DID)

TITLE BASIC SOW

PARAGRAPH *

A001 DI-MGMT-81804A Item Unique Identification (IUID) Marking 7.1.1

A002 DI-MGMT-81803A Item Unique Identification (IUID) Marking Plan (If required)

7.1.1

LIST of ADDRESSES

1. AFSC/LZDB

5215 Thurlow St, Ste 2

BLDG 70A RM 2240

Wright Patterson AFB, OH 45433

2. AFSC/PZIEC

7858 5th Street Tinker AFB, OK 73145

CONTRACT DAT A REQUIREMENTS LIST Form Approved

( 1 Data Item} 0MB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188), Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid 0MB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

A TDP TM OTHER MGMT

D. SYSTEM/ITEM

I

E. CONTRACT/PR NO. F.CONTRACTOR

Handyscan 3D Scanner Kit/Set

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

A00l Item Unique Identification (IUID) Markings

4. AUTHORITY (Data Acquisition Document No./

5. CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-MGMT-81804A SeeBlk 16 AFSC/LZBD

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED

ASREQ See Blk 16 LT b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT a. ADDRESSEE Final D SUBMISSION Draft

NIA NIA NIA Reg Repro

16. REMARKS AFSC/LZBD

5215 Thrurlow St, Ste 2

Block 4: Bldg 70A RM 2240

DI-MGMT-81804A shall be used as a guide only unless otherwise specified in the Wright Patterson AFB, individual task. Approved Contractor format acceptable. OH. 45433

Block 5: AFSC/PZIEC SOW Paragraphs: 7.1. 7858 5th Street

Tinker AFB, OK

Block 7: 73145

Acceptance approval from PCO/COR.

Block 12:

Delivered 20 business days after Post Award Conference.

Block 13:

Only required if changes are made, then:Subsequent submissions as requested by

Government. Final submission at acceptance of delivered units.

G. PREPARED BY

SOMMERFELDT.KYLE.JAMES.I �i��:KYLE.JAMES.1098947l30 098947830 Dnte: 20l2.09.1410:l2:ll •(l4'00'

H. DATE

14 Sep 22

15. TOTAL

I. APPROVED BY

MARGES.FRANCIS.ARARA mgi,.1,,ig,,<dby r A p. I 368927020

�������!�.AR�C�.1368927020

1 1 0

1 1 0

2 2 0

J. DATE

14 Sep 22

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page _l_ of_l_ Pages Adobe Professional 8.0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

D. SYSTEM/ITEM

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

B. EXHIBIT

I

C. CATEGORY:

MGMT

A TDP _ _ TM __ OTHER ________________ _

Handyscan 3D Scanner Kit/Set I

E. CONTRACT/PR NO.

I

F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page__ of __ l_Pages

DI-MGMT-81804A

DATA ITEM DESCRIPTION

Title: Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

Number: DI-MGMT-81804A Approval Date: 20130212

AMSC Number: F9335 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 Activity, Validation and

Verification Report is a tabular list providing IUID marking activity, validation and verification data such as: physical asset marking, registration, inventory audits, quality audits, and verification/validation results.

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 encoded in data matrix symbols.

Requirements:

1. Reference document: MIL-STD-130. The applicable issue of MIL-STD-130 shall be the latest version cited online at Acquisition Streamlining and Standardization Information System

(ASSIST) Update, at the time of the solicitation. Other documents referenced in MIL-STD-130 shall also be applied.

2. The Contractor’s format is acceptable. Recommend electronic transfer of information.

3. A representative sample of IUID-related data matrix marks on items in each delivered

Contract Line Item Number/Sub-Contract Line Item Number/Exhibit Line Item Number

(CLIN/SLIN/ELIN) shall be validated and verified. Verification and validation results shall be provided using this report format. Marks failing verification or validation must be replaced with compliant marks prior to government acceptance of the items.

4. The tabular report shall include the following alphanumeric fields:

4.1 Unique Item Identifier (UII).

4.2 UII Type (Construct).

4.3 Enterprise Identifier (EID).

4.4 EID Type (CAGE/NCAGE, DUNS, etc).

4.5 Original Equipment Manufacturer (OEM) Part Number.

DI-MGMT-81804A

4.6 Service Assigned Serial Number (if assigned).

4.7 Original Equipment Manufacturer (OEM) serial number.

4.8 Equipment Nomenclature (name and type).

4.9 National Stock Number (NSN).

4.10 Validation Date.

4.11 Validation Result (Pass/Fail).

4.12 Verification Date.

4.13 Verification Result (Pass/Fail).

4.14 Other Event/Activity Date* (optional).

4.15 Other Event/Activity* (optional).

4.16 For items marked that “Fail” IUID validation or verification, identify corrective action

(whether the item has been re-marked or scrapped).

*Other Event/Activity will be defined in the Contract Data Requirements Lists (CDRLS) if required.

5. The Key attributes for the report are the validation and verification columns which each indicate (Pass/Fail). (NOTE: Most verification apparatus provide electronic records with pass/fail summaries for both verification and validation.)

A “Pass” validation value shall be assigned to records whose data matrix symbol(s) properly encode Item Unique Identification data as prescribed in MIL-STD-130 DoD Standard Practice

Identification Marking of U.S. Military Property requirements for machine readable information

(MRI) marking.

A “Pass” verification value shall be assigned to records whose data matrix symbol(s) meet or exceed MIL-STD-130 DoD Standard Practice Identification Marking of U.S. Military Property requirements for data matrix symbol quality.

6. The Contractor shall ensure machine-readable IUID marks required under this contract are permanently placed on the items subjected to contractually-required performance testing prior to that testing; and further shall include all mark serviceability problems in the item’s test report(s).

7. End of DI-MGMT-81804A.

DATA ITEM DESCRIPTION

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

https://quicksearch.dla.mil/qsSearch.aspx https://dodprocurementtoolbox.com/site-pages/overview-implementation 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.

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

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.

https://www.iso.org/ https://webstore.ansi.org/

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