BiNOD CDRL D001 Item Unique Identification (IUID) Marking Plan.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

PREVIOUS EDITION MAY BE USED.

DD FORM 1423, FEB 2024

Page of

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoDM 5010.12 for detailed instructions.)

DD FORM 1423, FEB 2024

Page of

CONTRACT DATA REQUIREMENTS LIST

C. CATEGORY:

14. DISTRIBUTION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES Draft Final Reg Repro

16. REMARKS

14. DISTRIBUTION

15.TOTAL

Image of arrow pointing towards totals

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package; TM - Technical Manual; Other - other category of data, such as "Provisioning," "Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support (e.g., Mission Design Series (MDS) designator).

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Name of preparer of CDRL.

Item H. Date CDRL was prepared and signature of preparer of CDRL.

Item I. Name of CDRL approval authority.

Item J. Date CDRL was approved and signature of CDRL approval authority.

Item 1. See DFARS Subpart 204.71 for proper numbering. To add or delete additional data items, point and click the plus or minus sign to the right of Block J.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Identify only one Data Acquisition Document No. If a single work task generates more than one deliverable data product, prepare a separate data item for each deliverable data product.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work/Performance Work Statement paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data and computer software, specify the contractor's requirement to mark the appropriate distribution statement on the technical data or computer software (ref. DoDI 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15. Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14; Desired medium for delivery of the data item.

Identify for which data item additional remarks are provided. When tailoring the Data Acquisition Document invoked in Item 4, identify which portions of that Document are being tailored.

Identify any referenced attachments to the form. Attachments can be added using the button at the bottom of page 1.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government’s rights to use the data shall be governed by the pertinent provisions of the contract.

9.0.0.2.20120627.2.874785 DD Form 1423, "Contract Data Requirements List" delete continuation

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. This Contract Data Requirements List (CDRL) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract document(s).

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

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) Continued on next page

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