ATT 55 CDRL Exb A Supp 1.pdf

EXHIBIT A – SUPPLEMENT 1

CONTRACT DATA REQUIREMENTS LIST (CDRL)

INSTRUCTIONS

30 November 2017

ATTACHMENT 55

Exhibit A Suppl 1 CDRL Inst N61340-18-FOSR-0001

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.

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 “SESS,” 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 H, Date CDRL was prepared.

i) Block I, Approved by. Signature of CDRL approval authority. 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.21E provides detailed policy on approval authority.

j) Block J. Date CDRL was approved.

k) Block 1, Data Item Number. Enter the Exhibit Line Item Number (ELIN) per DFARS Procedures, Guidance, and Information 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.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-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.

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 5010.12-M, 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:

r) Block 8, Approval Code

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. Contractual data items shall not contain restrictive markings other than those allowed by the relevant contract DFARS clauses. Data item content that is considered Company confidential or proprietary may be included as an enclosure, in which the

Contractor is allowed to utilize Company confidential or proprietary statements when justification for these markings is also provided.

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

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 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 PEGNET 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 (deletion only), 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.

2) DISTRIBUTION STATEMENT & MARKING INSTRUCTIONS FOR DATA DELIVERABLES

a) Purpose of Distribution Statements - The purpose of this Contract attachment is to establish procedures for marking technical documents, including production, engineering and logistics information, to denote the extent to which they are available for distribution, release, and dissemination without additional approvals or authorizations.

Distribution covers all engineering drawings, standards, specification, technical manuals, blueprints, drawing plans, instructions, computer software and documentation, and other technical information that can be used or can be adapted for use to design, engineer, produce, manufacture, operate, repair, overhaul, or reproduce any military of space equipment or technology concerning such equipment.

The distribution statement markings, IAW DoD Issuance 5230.24 CHG 1 “Distribution Statements on Technical

Documents” and DoD Directive 5230.25 CHG 1 “Withholding of Unclassified Technical Data from Public

Disclosure” shall be mandatory for all technical documents, including such informal documents as working papers, memoranda, and preliminary reports if those documents are not already in the public domain and if they are likely to be disseminated outside the DoD.

b) Placement of Distribution Statement on Documentation - The distribution statement shall be displayed conspicuously on technical documents so as to be recognized readily by recipients. The following shall apply for standard written or printed material:

i) When possible, parts that contain information creating the requirement for a distribution statement shall be prepared as an appendix to permit broader distribution of the basic document.

ii) When practical, the abstract of the document, the SF 298 and bibliographic citations shall be written in such a way that the information will not be subject to distribution statement B, C, D, E, F, or X. If the technical information is not prepared in the form of an ordinary document (such as this Directive) and does not have a cover or title page (such as forms and charts), the applicable distribution statement shall be stamped, printed, written, or affixed by other means in a conspicuous position.

iii) The distribution statement shall appear on each front cover, title page, and SF 298, "Report

Documentation Page."

(1) Cover Page

(i) Contract, CLIN and CDRL Number

(ii) Title and Subtitle of the Document

(iii) Program Name, Supplier and version of software used to generate data

(iv) Date of Submission

(v) Distribution Statement - Refer to DODI 5230.24 CHG 1, OPNAVINST 5510.1H, and

OPNAVINST 5510.161, for guidance on the different Distributions Statements (e.g. B, C, D, E, F, or X). Specific to this Contract, deliverables shall be marked with the below

Distribution Statement.

“DISTRIBUTION STATEMENT D: Distribution authorized to DoD and DoD Contractor only;

to protect technical or operational data or information from automatic dissemination under the

International Exchange Program or by other means. Other requests for this document shall be referred to Commanding Officer, Navy Undergraduate Flight Training Programs, PMA-273

BLDG 4010, 48187 Standley Road, Patuxent River, MD, 20670.”

(vi) Classification - Refer to SECNAVINST 5510.36A and SECNAV M-5510.36, for guidance on the different Classification levels. Specific to this Contract, the pages shall be marked “UNCLASSIFIED - FOR OFFICIAL USE ONLY INFORMATION”

(vii) DESTRUCTION NOTICE - Refer to DOD 5230.24 CHG 1for guidance on the different Classification levels and the affiliated Destruction Notice. Specific to this

Contract, the pages shall be marked “DESTRUCTION NOTICE - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

(2) Header of Each Subsequent Page of Deliverable

(i) Contract, CLIN and CDRL Number

(ii) Date of Submission

(iii) Page Number

(3) Header and Footer of Each Subsequent Page of Deliverable shall be marked “FOUO”

3) PEGNET INSTRUCTIONS FOR CDRL DATA SUBMISSION

a) Upon Contract award, and as required thereafter, in order to electronically submit data deliverables to the

Government IAW with Contract requirements, the Contractor/Sub-Contractor will be responsible for identifying personnel requiring access to PEGNET. The Contractor/Sub-Contractor is responsible for completing

ATTACHMENT 08, U.S. Navy PegNet – New User Account Request form. This information will be provided by

Contractor to the Government (T-6B Civilian Program Analyst) via e-mail.

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

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

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

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

- E-mail: jaxs_gosnet@navy.mil

d) All data submissions will include markings in accordance with Paragraph 2.v of this document.

e) The data shall be delivered/uploaded on the PEGNET website in the format as defined by the DID or where not specified in the DID, a mutually agreed upon format. The URL for the Navy PEGNET is

HTTPS://PEGNET.NAVAIR.NAVY.MIL. After successful posting on PEGNET, the data shall be considered

“delivered” by Contractor, but not yet accepted/approved by the Government. If DD Form 250 required, see DFARS

252.246-7000. If BLOCK 7 of DD Form 1423 is coded “XX”, the Requiring Office will electronically accept in

PEGNET.