Attachment 2 Supplement to the Exhibits Explanation of CDRL.doc

N00019-10-R-0097

SECTION J ATTACHMENT 2

SUPPLEMENT

TO THE EXHIBITS

EXPLANATION OF

CONTRACT DATA REQUIREMENTS LIST

04 APRIL 2011

EXPLANATION OF CONTRACT DATA REQUIREMENTS LIST (CDRL) DD FORM 1423

I. General Information

a) Block A. Contract Line Item Number (CLIN). CLIN that is associated with the CDRL.

b) Block B. Exhibit. Exhibits shall be identified by a single capital letter (A-Z) then, as required, double alpha designators. The letters "I" and "O" will not be used. Include the lot number for multiple lot procurements (e.g., Lot I, Lot II). Lot number shall be omitted if only one lot exists.

c) Block C. Category.

i) If a Technical Data Package (TDP) or Technical Manual (TM), the appropriate space will be checked.

ii) If “Other” is selected, data will be further categorized, such as administrative “ADMN,” configuration management “CMAN,” etc., per the data functional area assignments contained in the Acquisition Management System and Data Requirements Control List (AMSDL).

d) Block D. System/Item. The system, item, project designator, or name of services being procured is identified. In cases where the system designation exceeds the space available, "See Block 16" will be stated.

e) Block E. Contract/Procurement Number (PN). Contract and/or PN number.

f) Block F. Contractor. Contractor's name or identification code or “N/A” if unknown.

g) Block G, Prepared by. Name, associated organization and/or program office and signature of the Individual responsible for the data being ordered.

h) Block I, Date. Self-explanatory.

i) Block L, Approved by. If procurement < $5,000,000, the AA is the appropriate Program Director (PD) or their Deputy. If procurement > $5,000,000, the AA is the appropriate Chairperson of the Data Requirements Review Board (DRRB). NAVAIRINST4200.21C provides detailed policy on approval authority.

j) Block J. Date. Self-explanatory.

k) Block 1, Data Item Number. Enter the Exhibit Line Item Number (ELIN) per DFARS Subpart 204.7105(c) (for example, A001-A009, A00A-A00Z, etc.).

l) Block 2, Title of Data Item.

i) The title of the CDRL is listed and shall be identical to the title of the associated DID (when cited in Block 4).

ii) When TMCRs are used to prescribe TM preparation requirements, or the DD Form 1423 are used to acquire weapon system TMs; the title of the specific type of TM being acquired shall be entered in Block 2.

iii) When FAR Clause is cited in Block 4, the CDRL Title shall match that of the FAR Section.

m) Block 3, Subtitle. If the title in Block 2 requires further identification, enter a subtitle.

n) Block 4, Authority (Data Acquisition Document Number). DID identification number, including the revision letter, shall specify for CDRL data format and content requirements.

i) DID's are selected from the DOD ASSIST Database (https://assist.daps.dla.mil/) and used as is or tailored. Tailoring instructions are specified in the remarks section (Block 16). It is also permissible to clarify DID requirements for a particular acquisition, by listing additional guidance in Block 16. With the exception of a one-time DID, Type III DID (see DOD-STD-963A), the document cited in this Block (or listed in the TMCR, when used) must have been cleared for listing in the latest edition of the AMSDL.

ii) Each line item of data specified on the DD Form 1423 shall be supported with a DID, except for technical manuals which may be supported by a Technical Manual Contract Requirements (TMCR) document. When the CDRL is used to acquire TMs, enter the specific number of the applicable military specification or standard which provides the draft preparation instructions.

iii) FAR or DFARS listed (see DOD 501012M, Section C2.3.3).

o) Block 5, Contract Reference. Enter the specific Section/Paragraph number of the Statement of Work (SOW), Performance Work Statement (PWS), specification, or standard that contains the tasking that will generate the requirement for the data item.

p) Block 6, Requiring Office - Technical office responsible for ensuring the adequacy of the data provided.

q) Block 7, DD FORM 250 Requirement – The location is designated (contractor's facility or destination) for performance of Government inspection and acceptance by entering the applicable code as shown below:

NOTES:

· Use of these symbols is not authorized for high cost data such as drawings, specifications, and technical manuals.

r) Block 8, Approval Code

NOTE: The responsible reviewing activity for approval will 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.

s) Block 9, Distribution Statement Required. See Section 2 of this Document, for Distribution Statement & Marking Instructions pertaining to this Contract and the below listed categories of statements.

t) Blocks 10, 11, 12, 16 – Applicable Codes are listed below

-Days after receipt of comments**

-Days after contract start **

* Use of these codes requires further explanation in Block 16 to provide the contractor with guidance necessary to accurately price the deliverable data item and to give a more definitive frequency.

** A number(s) must be inserted in place of the “X”or “XX”.

*** Deferred Delivery (per DFARS 227.7103-8) refers to the practice of timing the delivery of technical data or computer software specified in a contract to a firm operational need. It should be used only when the need for technical data is determined and specified on DD Form l423s but time or place of delivery is not firm.

i) Block 10, Frequency. The appropriate frequency code is listed for submission due date(s). If data is of a recurring type, it will be submitted at the end of the report period established in this field unless otherwise indicated in Block 10, Preparation Instructions of the DID, or in Block 11 or 16 of the DD Form 1423. Further explanation can be found in either Block 13 and/or 16.

ii) Block 11, As of Date - If the data is submitted only once, “as of date” (cut-off date) will be listed as follows: year/month/day (e.g., “92Mar10”). This is the date for cutting off collection of the data. If an as of date is not applicable, enter N/A.

iii) Block 12, Date of First Submission. The initial submission date is listed as follows: Year/Month/Day. If submittal is constrained by a specific even or milestone, this constraint will be listed in Block 16, e.g., 30 days prior to Critical Design review (CDR). If the contract start date is not known, the number of days after contract (DAC) start that the data is due (for example, 90 DAC), will be listed.

iv) Block 13, Date of Subsequent Submission. If the daft 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. When using “revisions as changes occur” or “change pages as required”, clarify in Block 16 the desired time frame required. Revisions shall mean revision to the original document and a new document delivered. Change pages shall mean, delivery or only pages that have changed to the original document. Do not insert classified dates.

u) Block 14, Distribution.

i) If Blocks 14 & 16 indicates that RANGERNET shall be utilized for delivery of data, see Section 3 of this document for instructions.

ii) If Blocks 14 & 16 indicates that hard copies are to be delivered, the following applies.

(1) Block 14.a: DoD component designators and office symbols/codes or unit identification codes (UICs) shall be listed in Block 14.a; however, an explanation of these codes must be provided in the CDRL supplemental section.

(2) Block 14.b: The specific number and type of copies to be delivered to each addressee in each of the available three columns will be listed.

(3) When the data item requires submission of a preliminary/draft document for approval prior to publication of a final document, draft quantities in Block 14b and an explanation in Block 16 to reflect time frame that draft and final copies are due, will be listed.

(4) If deferred delivery (DFDEL) is required, “DFDEL” will be indicated in this Block and disposition instructions in Block 16.

v) Block 15, Total. Self-explanatory.

w) Block 16, Remarks. This Block will 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, Enter in this field all pertinent data item information not specified elsewhere on the form and any required amplification of the other block inputs.

x) Blocks 17 and 18, are to be completed by the bidder or offeror, as required by the following.

(1) Block 17, Price Group. Enter the appropriate price group as shown on the reverse side of DD Form 1423.

(2) Block 18, Estimated Total Price. Enter the total estimated price equal to that portion of the total price which is estimated to be attributable to the design, development, production, or reproduction for the Government of that item of data. The entry “NC” for “no charge” is acceptable.

Note: DFARS Subpart 204.7105(6) provides specific guidance on separately priced and not separately priced data.

Also provided is guidance on when to detach, or leave attached, blocks 17 and 18 of the DD Form 1423.