Attachment_1_to_CDRL_Package.docx

Contract Data Requirements List (CDRLs) for the NBACC FFRDC Project Attachment 1 to Solicitation HSHQDC-15-R-00050

Table of Contents

Table of Contents Matrix:

Exhibit A:

And Customer Support Plan

Status Report

Status Report

Status Report

Status Report

Status Report

Status Report

Management Plan

(ESH) Program Status Report

Status Report

Plan

Program Status Report

Program Status Report

Standard Operating Procedures

Security Plan

And Guide Book

Plan for Laboratory Projects

Support Plan

Procedures Plan

And Support Plan

(Earned Value Management)

And Annual Meetings

General Glossary of Terms for the Contract Data Requirements List:

The following information is keyed and provides explanations for entries 1 through 19 in the attached Contract Data Requirement List Exhibit(s):

a. Contract Line Item Number (Block 1):

The Contract Line Item Number (CLIN) that is associated with this Contract Data Requirements List (CDRL)

b. Exhibit (Block 2):

The exhibit identifier identifies the type of data that is being procured. The table below provides a listing of the types of data that can be procured under a CDRL:

c. Category (Block 3):

The category is the appropriate category (i.e. Technical Data Package (TDP), Technical Manual (TM), or “Other” data (Other) for the data that is being procured.

d. System/Item (Block 4):

The system/item field provides the identification of the system, item, project designator or name, or title of services being acquired that the data will support.

e. Contract Number (Block 5):

The contract number field provides the Procurement Instrument Identification Number (PIIN) (i.e. the contract number, the Purchase Request (PR) number, the Request for Proposal number or other appropriate designator).

f. Contractor (Block 6):

The Contractor field provides the name of the Contractor who is responsible for providing the Government the data that is requested by the CDRL for the contract.

g. Data Item Number (Block 7):

The data item number field provides the 4-character Exhibit Line Item Number (ELIN). The first and second positions consist of the exhibit identified and the remaining positions are assigned sequentially. The letters “I” and “O” are not used.

h. Title of Data Item (Block 8)

The title of data item provides the title of the data item that is being requested by the Government.

i. Contract Reference (Block 9):

The contract reference field provides the specific section of the applicable contractual document which contains the tasking that generates the requirement for the data item. Normally, this will be the Statement of Work.

j. Requiring Office (Block 10):

The requiring office field provides the name of the technical office that has the responsibility for ensuring the technical adequacy of the data.

k. DD Form 250 Requirement (Block 11):

The applicable code, extracted from Table 1, designating the requirements for inspection and acceptance of the data. The Department of Defense Form 250 shall be delivered to the first addressee in Item 18, unless otherwise indicated in Block 19.

Table 1—DD Form 250 Requirement Codes for Use in CDRLs

Notes:

*--Source indicates Contractor’s facility **-Use of these symbols is not authorized for high cost data such as drawings, specifications, and technical manuals

l. Approval Code: (Block 12):

The approval code provides the Contractor with the identification of those elements that are considered critical and require advance written approval from the Requiring Office. The following codes are provided in Table 2 below:

Table 2—Approval Codes for Use in CDRLs

Agency before the Contractor can proceed. The scope and depth of approval

Must be explained in Block 19. Use to held to a minimum.

Rejected/accepted, based on its conforming to data item requirements and

Within the review time specified in Block 19.

m. Distribution Statement Requirement (Block 13):

The distribution Statement Requirement field identifies the type of distribution statement to be applied to the data item by the Contractor. As shown in Table 3, the code letter (e.g. A, B, C, D, E, F, or X) identifies the specific type of distribution statement.

Table 3—Distribution Statement Requirement Codes for CDRLs

Export-controlled technical data.

Block 19 of the ELIN will reflect the appropriate statement and will include the reason, date of determination, and controlling technical requirements office. If the appropriate statement is not known, or if it may vary among specific submissions under this item “See Block 19” will be entered into this block and explanatory information will be provided in Block 19. If the data is not technical in nature and does not require a distribution statement, an “N/A” for “Not Applicable” will be entered into this block.

n. Frequency of Data Item Distribution (Block 14):

The frequency of data item distribution field provides the frequency of data submittal. Entries in this block are explained in Table 4. If data is of a recurring type, it is to be submitted at the end of the reporting period established in this block unless otherwise indicated in Block 19.

Table 4—Data Submittal Frequency Codes

Etc.)(Does not include draft submissions)

Used in lieu of other codes where such are

Inadequate to define requirement, or used in

Addition to other codes requiring

Amplification in Block 19

Note: the codes are limited to five (5) digits for automation purposes.

*-the ELINs citing these codes will have an additional explanation in Block 19 to provide the Contractor with guidance necessary to accurately price the deliverable item.

o. As-of Date (Block 15)

The as-of date field is used to identify the date for cutting off the collection of data. If the data is to be submitted multiple times, a numerical will be entered into this block to indicate the number of calendar days prior to the end of the reporting period, established in Block 10, that the 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; a “0” would place the “as-of date” at the end of each month, quarter, etc. If the data is submitted only once, the “as-of date” will be as follows: year/month/day e.g. 90MAR15. If an “as-of date” is not applicable, an entry of “N/A” will be made in this block.

p. Date of First Submission (Block 16)

The date of first submission field is the field that identifies the due date of the initial submission. This is normally the postage date or date that the data is delivered to the Contracting Officer, entered into year/month/day (e.g. 90MAR15) or keyed to a specific event or milestone, using a code from Table 5.

NOTE: No classified are cited in CDRL

Table 5—Data Submission Codes

in lieu of other codes where such are inadequate to define the

Requirement, or used in addition to other codes requiring

Amplification in Block 19.

*--ELINs citing these codes will have in Block 19 additional specific instructions relative to data submissions.

**-the “X” is assigned a value indicating a number of days e.g. 30DAC.

q. Date of Subsequent Submission (Block 17)

The date of subsequent submission field identifies the due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 5.

NOTE: No classified dates are cited in CDRL.

r. Distribution of Data Item (Block 18)

The distribution of data item field provides the addresses and the number of draft and final copies (regular and reproducible) to be provided to each. DHS component designator and office/symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. The first addresses will be the acceptance activity for the data if acceptance by DD Form 250 is to be accomplished at destination. (See Block 11) When reproducible copies (e.g. magnetic tape, vellum, negative, etc.) are required, an explanation will be provided in Block 19. If the data is not to be delivered to the Government or associated Contractors, an explanation will be given in Block 19. If deferred delivery is required, “DFDEL” will be entered into this block and amplification will be given in Block 19.

s. Remarks (Block 19)

The remarks field contains all pertinent information not specified elsewhere in the CDRL and any amplification of other blocks on the form (e.g. use of contractor format, approval criteria and authority, inspection and acceptance clarification, distribution statements, specific submission instructions, explanation of reproducible copy and delivery requirements, desired medium for delivery of the data item, etc.)

Addressee List:

ATTN: Mr. Lewis Brown

245 Murray Lane SW

Washington, DC 20528

ATTN: Mr. Aaron H. Ford

245 Murray Lane, SW

Washington, DC 20528

Data Distribution Profile:

NOTE: Each addressee shall receive a letter of transmittal notification of data product delivery/posting. Draft/Final Column indicates addressees responsible for ensuring the adequacy of the data.

Letter of Transmittal

Only)

Contract Data Requirements List for NBACC FFRDC Project:

(36 Pages)