Attachment 2 CDRL Draft.xlsx

CDRL

Block A CLIN Author: Author:

Enter the CLIN that is associated with the CDRL. Block B Exhibit Author: Author:

Enter the contract exhibit letter assigned to the CDRL. (DFARS, Subpart 204.7101 (reference (b), requires the DD Form 1423 to be a contract exhibit versus an attachment. Block C Category Author: Author:

Check the appropriate block for the single category of data to be listed on the DD Form 1423. Types of data that comprise a TDP are defined in MIL-T-31000 (reference (m)), and types of DoD Manuals included under the TM category are defined in Part 9, Section B, of DoD Instruction 5000.2 (reference (f)). Types of data in the "Other" category may be further sub-categorized on a DD Form 1423 into single functional area assignments such as ADMN, CMAN, EDRS, etc., per the DoD 5010.12-L (reference (a)). (This block provides a convenient means of identifying and grouping individual data items in the same category, such as TDPs and TMs that require preparation of separate contract exhibits.)

Common Categories:

ADMN: Administrative data. non-technical data required by contracting officers and other personnel for the administration of the contract, excluding management and financial data

IPSC: Information processing standards for computers. Software delivery and user manuals associated with software or computer systems is included in this category.

MGMT: data required by the government to manage, provide visibility, and enforce contractual requirements

MISC: Miscellaneous. Source documents and data item descriptions not assigned to another data functional area, shows up on an approved travel report DID

QCIC: Quality Control/Assurance and Inspection. Methods and techniques intended to provide assurance that material data, supplies, and services conform to requirements and achieve satisfactory performance

SAFT: Safety Block D System/Item Author: Author:

Enter the system, item, project designator, or name of services being acquired that the data will support. Block E Contract/PR Number Author: Author:

Enter the contract or Purchase Request (PR) number when known; if unknown, enter the RFP number or other appropriate designator. 1. Data Item Number Author: Author:

Enter the Exhibit Line Item Number (ELIN) per the DFARS, Subpart 204.7105(c), reference (b)). 2. Title of Data Item Author: Author:

The title shall be identical to the title of the DID when cited in block 4. When Technical Manual Contract Requirements (TMCRs) are used to prescribe TM manual preparation requirements, or the DD Form 1423 is used to acquire weapon system TMs, the title of the specific type of TM being acquired shall be entered in block 2. 3. Subtitle Author: Author:

If the title in block 2 requires further identification, enter a subtitle. 4. Authority Author: Author:

(Data Acquisition Document Number) - Enter the DID number that provides the format and content requirements for the data item listed in block 2. With the exception of a one-time DID, all DIDs cited in block 4 (or listed in the TMCR, when used) must have been cleared for listing in the AMSDL (DoD 5010.12-L, reference (a)). 5. Contract Reference Author: Author:

Enter the specific paragraph numbers of the SOW, specification, standard, or other applicable document that contains the tasking for generating the data requirement. 6. Requiring Office Author: Author:

Enter the technical office responsible for ensuring the adequacy of the data. 7. DD 250 Requirement Author: Author:

see DOD 5010.12-M page 37 for all codes. Most common codes are:

XX: Inspection and acceptance requirements specified elsewhere in the contract.

NO: No inspection or acceptance required. No DD Form 250 or letter of transmittal required.

LT: Use Code LT for Letter of transmittal (LT) er codes). A letter of transmittal is not appropriate when an inspection of the data is required. The data is sent by the contractor directly to the activities listed in block 14 of the DD Form 1423. The LT is used when the contracting agency requires a record of delivery but does not desire to have a DD Form 250 for every piece of data developed by the contractor. The only other authorized use of the LT is the special case where the contracting agency does not desire to have separate DD Forms 250 but desires to have a Government QA representative perform inspection. The Government QA representative shall be listed on the distribution in block 14 and requested to provide comments via the QA letter of instruction. Also, when the local contract administration office (CAO) is required to perform inspection of a letter of transmittal, block 16 shall so indicate. In all cases where "LT" is used, a copy of the letter of transmittal should be provided to the CAO for information and appropriate use in administration of the contract. 8. Approval Code Author: Author:

Items of critical data requiring specific advanced written approval before distribution of the final data item should be identified by placing an "A" in this field. The responsible reviewing activity will normally be the Requiring Office listed in block 6. If that is not the case, the reviewing activity shall be identified as such in block 16. When the data item requires submission of a draft document prior to publication of a final document, block 16 of the DD Form 1423 shall show the length of time required for Government approval and/or disapproval and subsequent turn-around time for the contractor to resubmit the data after Government approval and/or disapproval has been issued. Those response times are contractual commitments and if the Government or contractor cannot meet those commitments, each is obligated to notify the other of the revised length of time required to respond. Block 16 will also indicate the extent of the approval requirements; e.g., approval of technical content and/or format. If approval of the data item is not required, insert "N/A" (not applicable) in block 8. 9. Distribution Statement Author: Author:

Enter the code letter ("A," "B," "C," "D," "E," "F," or "X") corresponding to the distribution statement to be marked on the technical data item by the contractor, in accordance with DoD Directive

5230.24 (reference (c)) and the guidance in Chapter 4 of this Manual. If the appropriate statement is not known, or if it may vary among specification submissions of the data item, enter "See Block 16" and indicate in block 16 that a distribution statement is required and will be provided by the Government before delivery of the data.

Frequently, it is not possible to determine the correct statement at the time the DD Form 1423 is prepared, and often, the contractor may be in a better position to recommend the correct statement. In those cases, the controlling DoD office and the contractor may negotiate the correct statement at one of the scheduled program audits or reviews.

Distribution Statement A. Approved for public release; distribution is unlimited. Distribution Statement A shall be used only on unclassified technical documents that do not contain export-controlled data, and have been approved for public release after a security and policy review determination by authorized public release authority.

Distribution Statement B shall be used to authorize release of a document to US Government agencies. Protects information not owned by the US Government and protected by a contractor's "limited rights" statement, or received with the understanding that it not be routinely transmitted outside the US Gov~rnment. Contractor Performance Evaluation - protects information in management reviews, records of contract performance evaluation, or other advisory documents evaluating programs of contractors.

Distribution Statement C shall be used to authorize distribution to US Government agencies and their authorized contractors.

Distribution Statement E protects information not owned by the US Government and protected by a contractor's "limited rights" statement, or received with the understanding that it not be routinely transmitted outside the DOD. Contractor Performance Evaluation - protects information in management reviews, records of contract performance evaluation, or other advisory documents evaluating programs of contractors. 10. Frequency Author: Author:

ANNLY Annually ASGEN As generated* ASREQ As required* BI-MO Every 2 months BI-WE Every 2 weeks DAILY Daily DFDEL Deferred Delivery MTHLY Monthly ONE/P One Preliminary ONE/R One time with revisions QRTLY Quarterly R/ASR Revision as required* SEMIA Every 6 months WEKLY Weekly XTIME Number of times to be submitted (1 TIME, 2 TIMES, 9 TIMES, etc)**

*Use of these codes requires further explanation in block 16 to provide, the contractor with guidance necessary to accurately price the deliverable data item.

**A number must be inserted in place of the "X." 11. As of Date Author: Author:

If the data is to be submitted only once, enter the "As of Date" (cut-off date) as follows: year/month/day (e.g., "92Mar10"). This is the date for cutting off collection of the data. If the data is to be submitted multiple times, enter a number to indicate the number of calendar days before the end of the reporting period, established in block 10, that data collection will be cut off. For example, "15" would place the "As of Date" for the data at 15 days before the end of the month, quarter, or year depending on the frequency established in Block 10 (e.g., report for May should reflect information collected through 16 May).

An "O" would place the "As of" date at the end of each month, quarter, or year, etc.

Block 16 may be used for further explanation. If an "As of Date" is not applicable, enter "N/A" in block 11. 12. Date of First Submission Author: Author:

Enter the initial submission date as follows: year/month/day (e.g., "90Mar10"). If submittal is constrained by a specific event or milestone, enter that constraint. If the, contract start date is not known, indicate the number of calendar days after contract (DAC) start that the data is due (e.g., "90 DAC"). Do not insert classified dates. Typical abbreviations in block 12 are:

ASGEN As generated* ASREQ As required* XXDAC Days after contract start** DFDEL Deferred Delivery* EOC End of contract EOM End of month EOQ End of quarter XDACM Days after contract modification** XDARP Days after reporting period** XDARC Days after receipt of comments** XDATC Days after test completion** XDPTT Days before to test** XDARC Days after receipt of comments** XDARP Days after reporting period** XDADO Days after delivery order**

*Provide specific instructions for these requirements in block 16.

**A number must be inserted in place of the "X." 13. Date of Subsequent Submission Author: Author:

If data is submitted more than once, enter the date(s) of subsequent submission(s). If submittal is constrained by a specific event or milestone, explain this constraint in block 16. Do not insert classified dates. 14.a Distribution Addressee Author: Author:

Enter the addressees and the corresponding number of draft copies and final copies (regular and/or reproducible) to be provided to each. The first addressee is normally the requiring office code shown in block 6. If the acceptance activity for the data item is different than the requiring office, and acceptance of the data item is by DD Form 250 to be accomplished at the destination, then the code for the acceptance activity will be placed as the first entry in block 14. Do not insert classified locations. Block 14 will provide for the following particulars:

C3.3.3.2.14.1. The DoD component designator and office symbols and/or codes, or unit identification codes (UICs) may be used in block 14a; however, an explanation of these must be provided in the supplemental section of the CDRL package as discussed in paragraph C3.3.2. of this chapter, or in block 16 with a reference to block 14. The former approach is recommended for CDRL packages with more than 10 CDRL items.

In block 14b, insert the specific number and type of copies to be delivered to each addressee in each of the available three columns.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Draft Copies Author: Author:

C3.3.3.2.14.2. In block 14b, insert the specific number and type of copies to be delivered to each addressee in each of the available three columns.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered.

C3.3.3.2.14.3. When the data items requires advance written approval (indicated by an "A" in block 8), draft copies are required for approval before publication of the final document. Enter draft quantities in block 14b and an explanation in block 16 (e.g., "Submit draft for approval 90 DAC award. Submit final copies 30 days after Government approval of the draft.") It should be noted that unless otherwise indicated on the DD Form 1423, all addressees listed in block 14 will receive both draft and final documents.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Final Copies Regular Author: Author:

C3.3.3.2.14.4. Include digital media details and constraints (when appropriate), such as source document requirements of tape density per inch, tape size, record and header formats, file headers, files constructs, and target system environment (such as DEC VAX 6000 series environment). (See reference (h), MIL-HDBK-59, for guidance).

C3.3.3.2.14.5. Include non-digital media details and constraints, such as source document requirements (e.g., MIL-D-5840 or MIL-M-38761/1) type and class of microfilm, paper, vellum, etc., as necessary to fully describe media constraints.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Final Copies Reproducible Author: Author:

Reproducible copies are master/first generation documents capable of making successive generations of high quality resolution copies.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 15. Total Author: Author:

Enter the total number of draft and final (regular and reproducible) copies required by block 14. For digital media, enter the total number of copies required by block 14. 16. Remarks Author: Author:

This block shall be used to provide additional or clarifying information for blocks 1 through 15; e.g., clarification relative to distribution statements, DID tailoring requirements, use of contractor format, and distribution of the data. When on-line access or digital delivery is required for the data item, relevant requirements are to be included in Block 16; e.g., references to the appropriate CALS standardization documents. (See reference (h), MIL-HDBK-59, for guidance.) Block G Prepared By Author: Author:

Enter the name and signature of the CDRL preparer or the name of the activity responsible for preparation of the CDRL. Block H Prepared Date Author: Author:

Enter the date the CDRL was prepared. Block I Approved By Author: Author:

Enter the name and signature of the individual responsible for approving the CDRL. Block J Approved Date Author: Author:

Enter the date the CDRL was approved.

CDRL (2)

Block A CLIN Author: Author:

Enter the CLIN that is associated with the CDRL. Block B Exhibit Author: Author:

Enter the contract exhibit letter assigned to the CDRL. (DFARS, Subpart 204.7101 (reference (b), requires the DD Form 1423 to be a contract exhibit versus an attachment. Block C Category Author: Author:

Check the appropriate block for the single category of data to be listed on the DD Form 1423. Types of data that comprise a TDP are defined in MIL-T-31000 (reference (m)), and types of DoD Manuals included under the TM category are defined in Part 9, Section B, of DoD Instruction 5000.2 (reference (f)). Types of data in the "Other" category may be further sub-categorized on a DD Form 1423 into single functional area assignments such as ADMN, CMAN, EDRS, etc., per the DoD 5010.12-L (reference (a)). (This block provides a convenient means of identifying and grouping individual data items in the same category, such as TDPs and TMs that require preparation of separate contract exhibits.)

Common Categories:

ADMN: Administrative data. non-technical data required by contracting officers and other personnel for the administration of the contract, excluding management and financial data

IPSC: Information processing standards for computers. Software delivery and user manuals associated with software or computer systems is included in this category.

MGMT: data required by the government to manage, provide visibility, and enforce contractual requirements

MISC: Miscellaneous. Source documents and data item descriptions not assigned to another data functional area, shows up on an approved travel report DID

QCIC: Quality Control/Assurance and Inspection. Methods and techniques intended to provide assurance that material data, supplies, and services conform to requirements and achieve satisfactory performance

SAFT: Safety Block D System/Item Author: Author:

Enter the system, item, project designator, or name of services being acquired that the data will support. Block E Contract/PR Number Author: Author:

Enter the contract or Purchase Request (PR) number when known; if unknown, enter the RFP number or other appropriate designator. 1. Data Item Number Author: Author:

Enter the Exhibit Line Item Number (ELIN) per the DFARS, Subpart 204.7105(c), reference (b)). 2. Title of Data Item Author: Author:

The title shall be identical to the title of the DID when cited in block 4. When Technical Manual Contract Requirements (TMCRs) are used to prescribe TM manual preparation requirements, or the DD Form 1423 is used to acquire weapon system TMs, the title of the specific type of TM being acquired shall be entered in block 2. 3. Subtitle Author: Author:

If the title in block 2 requires further identification, enter a subtitle. 4. Authority Author: Author:

(Data Acquisition Document Number) - Enter the DID number that provides the format and content requirements for the data item listed in block 2. With the exception of a one-time DID, all DIDs cited in block 4 (or listed in the TMCR, when used) must have been cleared for listing in the AMSDL (DoD 5010.12-L, reference (a)). 5. Contract Reference Author: Author:

Enter the specific paragraph numbers of the SOW, specification, standard, or other applicable document that contains the tasking for generating the data requirement. 6. Requiring Office Author: Author:

Enter the technical office responsible for ensuring the adequacy of the data. 7. DD 250 Requirement Author: Author:

see DOD 5010.12-M page 37 for all codes. Most common codes are:

XX: Inspection and acceptance requirements specified elsewhere in the contract.

NO: No inspection or acceptance required. No DD Form 250 or letter of transmittal required.

LT: Use Code LT for Letter of transmittal (LT) er codes). A letter of transmittal is not appropriate when an inspection of the data is required. The data is sent by the contractor directly to the activities listed in block 14 of the DD Form 1423. The LT is used when the contracting agency requires a record of delivery but does not desire to have a DD Form 250 for every piece of data developed by the contractor. The only other authorized use of the LT is the special case where the contracting agency does not desire to have separate DD Forms 250 but desires to have a Government QA representative perform inspection. The Government QA representative shall be listed on the distribution in block 14 and requested to provide comments via the QA letter of instruction. Also, when the local contract administration office (CAO) is required to perform inspection of a letter of transmittal, block 16 shall so indicate. In all cases where "LT" is used, a copy of the letter of transmittal should be provided to the CAO for information and appropriate use in administration of the contract. 8. Approval Code Author: Author:

Items of critical data requiring specific advanced written approval before distribution of the final data item should be identified by placing an "A" in this field. The responsible reviewing activity will normally be the Requiring Office listed in block 6. If that is not the case, the reviewing activity shall be identified as such in block 16. When the data item requires submission of a draft document prior to publication of a final document, block 16 of the DD Form 1423 shall show the length of time required for Government approval and/or disapproval and subsequent turn-around time for the contractor to resubmit the data after Government approval and/or disapproval has been issued. Those response times are contractual commitments and if the Government or contractor cannot meet those commitments, each is obligated to notify the other of the revised length of time required to respond. Block 16 will also indicate the extent of the approval requirements; e.g., approval of technical content and/or format. If approval of the data item is not required, insert "N/A" (not applicable) in block 8. 9. Distribution Statement Author: Author:

Enter the code letter ("A," "B," "C," "D," "E," "F," or "X") corresponding to the distribution statement to be marked on the technical data item by the contractor, in accordance with DoD Directive

5230.24 (reference (c)) and the guidance in Chapter 4 of this Manual. If the appropriate statement is not known, or if it may vary among specification submissions of the data item, enter "See Block 16" and indicate in block 16 that a distribution statement is required and will be provided by the Government before delivery of the data.

Frequently, it is not possible to determine the correct statement at the time the DD Form 1423 is prepared, and often, the contractor may be in a better position to recommend the correct statement. In those cases, the controlling DoD office and the contractor may negotiate the correct statement at one of the scheduled program audits or reviews.

Distribution Statement A. Approved for public release; distribution is unlimited. Distribution Statement A shall be used only on unclassified technical documents that do not contain export-controlled data, and have been approved for public release after a security and policy review determination by authorized public release authority.

Distribution Statement B shall be used to authorize release of a document to US Government agencies. Protects information not owned by the US Government and protected by a contractor's "limited rights" statement, or received with the understanding that it not be routinely transmitted outside the US Gov~rnment. Contractor Performance Evaluation - protects information in management reviews, records of contract performance evaluation, or other advisory documents evaluating programs of contractors.

Distribution Statement C shall be used to authorize distribution to US Government agencies and their authorized contractors.

Distribution Statement E protects information not owned by the US Government and protected by a contractor's "limited rights" statement, or received with the understanding that it not be routinely transmitted outside the DOD. Contractor Performance Evaluation - protects information in management reviews, records of contract performance evaluation, or other advisory documents evaluating programs of contractors. 10. Frequency Author: Author:

ANNLY Annually ASGEN As generated* ASREQ As required* BI-MO Every 2 months BI-WE Every 2 weeks DAILY Daily DFDEL Deferred Delivery MTHLY Monthly ONE/P One Preliminary ONE/R One time with revisions QRTLY Quarterly R/ASR Revision as required* SEMIA Every 6 months WEKLY Weekly XTIME Number of times to be submitted (1 TIME, 2 TIMES, 9 TIMES, etc)**

*Use of these codes requires further explanation in block 16 to provide, the contractor with guidance necessary to accurately price the deliverable data item.

**A number must be inserted in place of the "X." 11. As of Date Author: Author:

If the data is to be submitted only once, enter the "As of Date" (cut-off date) as follows: year/month/day (e.g., "92Mar10"). This is the date for cutting off collection of the data. If the data is to be submitted multiple times, enter a number to indicate the number of calendar days before the end of the reporting period, established in block 10, that data collection will be cut off. For example, "15" would place the "As of Date" for the data at 15 days before the end of the month, quarter, or year depending on the frequency established in Block 10 (e.g., report for May should reflect information collected through 16 May).

An "O" would place the "As of" date at the end of each month, quarter, or year, etc.

Block 16 may be used for further explanation. If an "As of Date" is not applicable, enter "N/A" in block 11. 12. Date of First Submission Author: Author:

Enter the initial submission date as follows: year/month/day (e.g., "90Mar10"). If submittal is constrained by a specific event or milestone, enter that constraint. If the, contract start date is not known, indicate the number of calendar days after contract (DAC) start that the data is due (e.g., "90 DAC"). Do not insert classified dates. Typical abbreviations in block 12 are:

ASGEN As generated* ASREQ As required* XXDAC Days after contract start** DFDEL Deferred Delivery* EOC End of contract EOM End of month EOQ End of quarter XDACM Days after contract modification** XDARP Days after reporting period** XDARC Days after receipt of comments** XDATC Days after test completion** XDPTT Days before to test** XDARC Days after receipt of comments** XDARP Days after reporting period** XDADO Days after delivery order**

*Provide specific instructions for these requirements in block 16.

**A number must be inserted in place of the "X." 13. Date of Subsequent Submission Author: Author:

If data is submitted more than once, enter the date(s) of subsequent submission(s). If submittal is constrained by a specific event or milestone, explain this constraint in block 16. Do not insert classified dates. 14.a Distribution Addressee Author: Author:

Enter the addressees and the corresponding number of draft copies and final copies (regular and/or reproducible) to be provided to each. The first addressee is normally the requiring office code shown in block 6. If the acceptance activity for the data item is different than the requiring office, and acceptance of the data item is by DD Form 250 to be accomplished at the destination, then the code for the acceptance activity will be placed as the first entry in block 14. Do not insert classified locations. Block 14 will provide for the following particulars:

C3.3.3.2.14.1. The DoD component designator and office symbols and/or codes, or unit identification codes (UICs) may be used in block 14a; however, an explanation of these must be provided in the supplemental section of the CDRL package as discussed in paragraph C3.3.2. of this chapter, or in block 16 with a reference to block 14. The former approach is recommended for CDRL packages with more than 10 CDRL items.

In block 14b, insert the specific number and type of copies to be delivered to each addressee in each of the available three columns.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Draft Copies Author: Author:

C3.3.3.2.14.2. In block 14b, insert the specific number and type of copies to be delivered to each addressee in each of the available three columns.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered.

C3.3.3.2.14.3. When the data items requires advance written approval (indicated by an "A" in block 8), draft copies are required for approval before publication of the final document. Enter draft quantities in block 14b and an explanation in block 16 (e.g., "Submit draft for approval 90 DAC award. Submit final copies 30 days after Government approval of the draft.") It should be noted that unless otherwise indicated on the DD Form 1423, all addressees listed in block 14 will receive both draft and final documents.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Final Copies Regular Author: Author:

C3.3.3.2.14.4. Include digital media details and constraints (when appropriate), such as source document requirements of tape density per inch, tape size, record and header formats, file headers, files constructs, and target system environment (such as DEC VAX 6000 series environment). (See reference (h), MIL-HDBK-59, for guidance).

C3.3.3.2.14.5. Include non-digital media details and constraints, such as source document requirements (e.g., MIL-D-5840 or MIL-M-38761/1) type and class of microfilm, paper, vellum, etc., as necessary to fully describe media constraints.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 14.b. Final Copies Reproducible+Q:QP:VX2R:VO:VX2R:VN:VX2R:VM:VX2R:VL:VM:VN:VO:VP:VQR:V Author: Author:

Reproducible copies are master/first generation documents capable of making successive generations of high quality resolution copies.

Unused columns adjacent to each addressee will have either an "N/A" or number "0" entered. 15. Total Author: Author:

Enter the total number of draft and final (regular and reproducible) copies required by block 14. For digital media, enter the total number of copies required by block 14. 16. Remarks Author: Author:

This block shall be used to provide additional or clarifying information for blocks 1 through 15; e.g., clarification relative to distribution statements, DID tailoring requirements, use of contractor format, and distribution of the data. When on-line access or digital delivery is required for the data item, relevant requirements are to be included in Block 16; e.g., references to the appropriate CALS standardization documents. (See reference (h), MIL-HDBK-59, for guidance.) Block G Prepared By Author: Author:

Enter the name and signature of the CDRL preparer or the name of the activity responsible for preparation of the CDRL. Block H Prepared Date Author: Author:

Enter the date the CDRL was prepared. Block I Approved By Author: Author:

Enter the name and signature of the individual responsible for approving the CDRL. Block J Approved Date Author: Author:

Enter the date the CDRL was approved.

https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204779https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204779