20-00172_A003_CDRL_DMO_.pdf
PDF 276 KB Posted
- Solicitation number
- FA8538-21-R-0002
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 20-00172_A005_CDRL_DMO_.pdf | ||
| 20-00172_A004_CDRL_DMO___.pdf | ||
| GFPFA853821R0002_1__.pdf | ||
| PWS.pdf | ||
| 3112859_PKGRQMT_REPORT.pdf | ||
| CAV_Reporting_Requirements_Updated_.pdf | ||
| 20-00172_A006_CDRL_DMO_.pdf | ||
| 20-00172_A001_CDRL_DMO_.pdf | ||
| DD2875_blank_SAAR_.pdf | ||
| 20-00172_A007_CDRL_DMO_.pdf | ||
| Wage_Determination.pdf | ||
| FA8538-21-R-0002.pdf | ||
| 20-00172_A002_CDRL_DMO_.pdf |
Show all 13
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
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
Form Approved OMB 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 OMB 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:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE
7. DD 250 REQ
8. APP CODE
9. DIST STATEMENT
REQUIRED
10. FREQUENCY
11. AS OF DATE
12. DATE OF FIRST SUBMISSION
13. DATE OF SUBSEQUENT
SUBMISSION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft Final
Reg Repro
15. TOTAL
16. REMARKS
17. PRICE GROUP
18. ESTIMATED
TOTAL PRICE
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 Page of Pages
INSTRUCTIONS FOR COMPLETING DD FORM 1423
(See DoD 5010.12-M for detailed instructions.)
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.
Item E. Self-explanatory (to be filled in after contract award).
Item F. Self-explanatory (to be filled in after contract award).
Item G. Signature of preparer of CDRL.
Item H. Date CDRL was prepared.
Item I. Signature of CDRL approval authority.
Item J. Date CDRL was approved.
Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.
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. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work 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, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 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.
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 right to use the data shall be governed by the pertinent provisions of the contract.
DD FORM 1423-1 (BACK), FEB 2001
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
| data_item: A003 |
| title: IUID Marking Plan |
| sub: |
| auth: DI-MGMT-81803A |
| ref: PWS Paragraph 4.3.6.1 |
| req_ofc: 409 SCMS/GUMB |
| dd250: N/A |
| appcode: N/A |
| dist: N/A |
| freq: As Required |
| asof: N/A |
| firstsub: As Required |
| subsub: As Required |
| addressee1: |
| draft1: |
| reg1: |
| repro1: |
| addressee2: |
| draft2: |
| reg2: |
| repro2: |
| addressee3: |
| draft3: |
| reg3: |
| repro3: |
| addressee4: |
| draft4: |
| reg4: |
| repro4: |
| addressee5: |
| draft5: |
| reg5: |
| repro5: |
| addressee6: |
| draft6: |
| reg6: |
| repro6: |
| addressee7: |
| draft7: |
| reg7: |
| repro7: |
| addressee8: |
| draft8: |
| reg8: |
| repro8: |
| addressee9: |
| draft9: |
| reg9: |
| repro9: |
| addressee10: |
| draft10: |
| reg10: |
| repro10: |
| addressee11: |
| draft11: |
| reg11: |
| repro11: |
| addressee12: |
| draft12: |
| reg12: |
| repro12: |
| addressee13: |
| draft13: |
| reg13: |
| repro13: |
| addressee14: |
| draft14: |
| reg14: |
| repro14: |
| addressee15: |
| draft15: |
| reg15: |
| repro15: |
| addressee16: |
| draft16: |
| reg16: |
| repro16: |
| addressee17: |
| draft17: |
| reg17: |
| repro17: |
| addressee18: |
| draft18: |
| reg18: |
| repro18: |
| addressee19: |
| draft19: |
| reg19: |
| repro19: |
| addressee20: |
| draft20: |
| reg20: |
| repro20: |
| addressee21: |
| draft21: |
| reg21: |
| repro21: |
| addressee22: |
| draft22: |
| reg22: |
| repro22: |
| addressee23: |
| draft23: |
| reg23: |
| repro23: |
| addressee24: |
| draft24: |
| reg24: |
| repro24: |
| addressee25: |
| draft25: |
| reg25: |
| repro25: |
| addressee26: |
| draft26: |
| reg26: |
| repro26: |
| addressee27: |
| draft27: |
| reg27: |
| repro27: |
| addressee28: |
| draft28: |
| reg28: |
| repro28: |
| addressee29: |
| draft29: |
| reg29: |
| repro29: |
| addressee30: |
| draft30: |
| reg30: |
| repro30: |
| addressee31: |
| draft31: |
| reg31: |
| repro31: |
| addressee32: |
| draft32: |
| reg32: |
| repro32: |
| addressee33: |
| draft33: |
| reg33: |
| repro33: |
| addressee34: |
| draft34: |
| reg34: |
| repro34: |
| addressee35: |
| draft35: |
| reg35: |
| repro35: |
| addressee36: |
| draft36: |
| reg36: |
| repro36: |
| addressee37: |
| draft37: |
| reg37: |
| repro37: |
| addressee38: |
| draft38: |
| reg38x: |
| repro38: |
| total_draft: 0 |
| total_reg: 0 |
| total_repro: 0 |
| remarks: 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)
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.
| group: |
| total_price: |
| prep_name: |
| line_item: |
| exhibit: |
| xtdp: Off |
| xtm: Off |
| othercat: X |
| system: C-130H Avionics Component Repair |
| ctr_no: FD20602000172 |
| contr: Innovative Solutions & Support Co. |
| remarksb: (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.
* DI-MGMT-81803A continued on attached word document.* A003 6-23-20 RHK
| Page2: 2 | |
| Reset: | |
| 2020-06-22T13:19:57-0400 | |
| WARREN.MICHELE.A.1228769220 |
| prep_date: 6/22/2020 | |
| app_by: | |
| 2020-06-23T07:59:14-0400 | |
| WILSON.CHRISTAL.W.1052788028 |
| app_date: 6/23/2020 |
| Page: 1 |
| of_pages: 2 |
| app: Adobe Professional 8.0 |
File details come from the government source that posted it. Updated .