Att_17_1-_CDRL_Instructions_20160331.pdf

N00019-15-R-0079

Section J, Attachment 17.1

31 March 2016

CDRL INSTRUCTIONS

1) CONTRACT DATA REQUIREMENTS LIST (CDRL) DD

FORM 1423 INSTRUCTIONS (BLOCKS)

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.

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

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/PR No.. Contract or Purchase Request 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 preparation of the CDRL.

h) Block H. Date. The date the CDRL was prepared.

i) Block I. 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. The date the CDRL was approved.

k) Block 1. Data Item Number. Enter the Exhibit Line Item Number (ELIN) per PGI

204.7105 (for example, A001-A009, A00A-A00Z, etc.).

l) Block 2. Title of Data Item.

The title of the CDRL is listed and shall be identical to the title of the associated

DID (when cited in Block 4).

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.

When Federal Acquisition Regulation (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.

DID's are selected from DOD ASSIST Quick Search Database

(http://quicksearch.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 MIL-

STD-963C), 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.

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.

FAR or DFARS listed

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:

CODE INSPECTION ACCEPTANCE

SS

Inspection at contractor's facility (DD

Form 250).

Acceptance at contractor's facility (DD Form 250).

DD

No inspection performed at contractor's facility. Final inspection performed at destination. (DD Form 250).

Acceptance at destination. (DD Form 250).

SD

Inspection at contractor's facility (DD

Form 250).

Acceptance at destination.

DS

No inspection performed at contractor's facility. Final inspection performed at destination. (DD Form 250).

Acceptance at contractor's facility. Acceptance based on written approval from the Contracting

Officer. (DD Form 250).

LT*

Letter of Transmittal only -“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.

NO* No inspection or acceptance required.

XX Inspection and acceptance requirements specified elsewhere in contract.

NOTES:

- Codes that contain the * symbol are not authorized for high cost data such as drawings, specifications, and technical manuals. If a code that indicates a “DD Form 250” is required, the deliverable data shall still be uploaded onto AIMDNET and Government approval via

AIMDNET notification shall be considered acceptance.

r) Block 8. Approval Code

CODE DESCRIPTION

"A"

Items of critical data requiring specific advance written approval prior to distribution of the final data shall be identified by placing an “A” in this Block. TDPs and TMs shall always require an “A” in this Block. When the data item requires submission of a preliminary/draft document prior to publication of a final document.

A (See Blk 16)

Block 16 shall show the length of time required for government approval/disapproval and subsequent turnaround time for the contractor to resubmit the data after government approval/disapproval has been issued. Block 16 will also indicate the extent of the approval requirements, e.g., approval of technical content and/or format. The

AIMDNET system will generate notification/email of approval/disapproval, from

Government to Contractor.

"D" Distribution statement required (distribution will be explained in Block 16).

"AD" Approval and distribution statements required.

BLANK

Approval (written) is not required. However, the data item will be reviewed and accepted/rejected, based on its conforming to the requirements of the DID, and within the review time specified in Block 16.

N/A No Government approval necessary

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.

CODE DESCRIPTION

A Unlimited distribution

B US Government agencies only

C US Government agencies and their contractors

D DoD and DoD contractors only

E DoD components only

F Only as directed by controlling office

X US Government agencies, private individuals, or enterprises eligible to obtain export-controlled technical data

TBD To Be Determined. Use block 16 to explain when it will be determined.

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

ANNLY - Annually QRTLY – Quarterly

ASGEN - As generated * R/ASR-Revisions as required *

ASREQ - As required * SEMIA - Each six months

BI-MO - Every two months WEEKLY – Weekly

BI-WE - Every two weeks 2TIME/R - 2 separate submittals

CP/RQ - Change pages as required when procuring (used change pages only) 2/MTH – Semimonthly

DAILY - Daily 2TIME - Two separate submittals

DFDEL - Deferred delivery (rarely used) * *** XDACM-Days after contract modification**

EOC-End of contract XDARP-Days after reporting period**

EOM-End of month XDARC-Days after receipt of comments**

EOQ-End of quarter XDATC-Days after test completion**

MTHLY - Monthly XDPTT-Days prior to test**

ONE/P - One time preliminary draft and revisions(s) XDADO-Days after delivery order**

ONE/R - One time and revisions XTIME - Number of times to be submitted **

OTIME - One time XXDAC -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.

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

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

w) Block 12. Date of First Submission. The initial submission date is listed as follows:

Year/Month/Day. If submittal is constrained by a specific event 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.

x) Block 13. Date of Subsequent Submission. If the draft 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.

y) Block 14. Distribution.

If Blocks 14 & 16 indicate that hard copies are to be delivered:

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

z) Block 15. Total. Self-explanatory.

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

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

2) INSTRUCTIONS FOR ELECTRONIC CDRL DATA

SUBMISSION

a) Upon Contract award, and as required thereafter, in order to electronically submit data deliverables IAW with Contract requirements, User Accounts need to be established in

AIMDNET. The Contractor/Sub-Contractor shall complete the "U.S. Navy AIMDNET - New

User Account Request" (Attachment 17.2) for those individuals requiring access to AIMDNET.

The completed request shall be forwarded to the address specified on the current version of the

New User Account Request.

b) The Government will have approval authority on all requests for accounts and forward to

AIMDNET Technical Support for account formation. AIMDNET will generate an email to individual personnel with login instructions, once account has been formed.

c) If AIMDNET Technical Support is required after account generation, contact information is as follows:

- GOSNET Help Line: 1-800-762-8257 X 3500

- E-mail: jaxs_gosnet@navy.mil

d) If CDRL Block 7 refers to Paragraph 2)d) for inspection and acceptance instructions, then the data shall be delivered/uploaded on the AIMDNET website. The URL for the Navy

AIMDNET is HTTPS://AIMDNET.NAVAIR.NAVY.MIL. After successful posting on

AIMDNET, the data shall be considered delivered by Contractor, but not yet accepted/approved by the Government. Distribution of the deliverable will be made by the AIMDNET system which will notify the Requiring Office in Block 6 and other interested Government personnel. If

Block 7 of DD Form 1423 is coded “XX”, the Requiring Office will electronically accept, reject or approve in AIMDNET and a DD 250 is not required.

e) If CDRL Block 7 refers to Paragraph 2)e) for inspection and acceptance instructions, then the data shall be delivered/uploaded on the JDRS website. The URL for JDRS is http://www.jdrs.mil. After successful posting on JDRS, the data shall be considered delivered by the Contractor and accepted by the Government.

f) Reserved.

g) If CDRL Block 7 refers to Paragraph 2)g) for inspection and acceptance instructions, then the data shall be delivered/uploaded both electronically on the AIMDNET website and also in hard copy with signed cover letter to the addressees below. The URL for the Navy AIMDNET is

HTTPS://AIMDNET.NAVAIR.NAVY.MIL. After successful posting on AIMDNET and hard copy delivery, the data shall be considered delivered by Contractor, but not yet accepted/approved by the Government. Further electronic distribution of the deliverable will be made by the AIMDNET system which will notify the Requiring Office in Block 6 and other interested Government personnel. If Block 7 of DD Form 1423 is coded “XX”, the Requiring

Office will electronically accept, reject or approve in AIMDNET and a DD 250 is not required.

Addresses for initial hard copy deliveries and updates are as follows:

Chief of Naval Air Training

Attn: Property Administrator (Code N4233)

250 Lexington Blvd., Room 242 mailto:jaxs_gosnet@navy.mil https://pegnet.navair.navy.mil/ https://aimdnet.navair.navy.mil/

Corpus Christi, TX, 78419

Chief of Naval Air Training, Detachment-Pensacola

Attn: Industrial Property Management Specialist

250 San Carlos Road

Building 1853, Room 115

Pensacola, FL, 32508

Chief of Naval Air Training Detachment-Corpus Christi

Attn: Industrial Property Management Specialist

401 Bataan Drive

Building 89

Corpus Christi, TX, 78419