EASR_Att_J-19_CDRL_GLOSSARY.pdf

2015-08-12 0930

N00024‐15‐R‐5370

DD FORM 1423

Attachment J-19

ATTACHMENT J-19

CONTRACT DATA REQUIREMENTS LIST

GENERAL DD FORM 1423 GLOSSARY

(Addressee listing begins on page 7)

The blocks listed below are explanations to headings and signature blocks that are on the (DD Form

1423) Exhibit(s).

Block A. CONTRACT LINE ITEM NO.

The contract line item number (CLIN) that is associated with this contract data requirements list

(CDRL).

Block B. EXHIBIT The exhibit identifier for this CDRL (See DFARS 204.7105-3 for exhibit identifiers). (Note:

DFARS 215.406-2 prohibits the use of a DD Form 1423 as an attachment for Technical data.

Therefore, CDRLs for Technical Data Packages (TDP), Technical Manuals (TM) and Other Data are designated as exhibits).

Block C. CATEGORY The appropriate block for Technical Data Package (TDP), Technical Manuals (TM), or other technical data (OTHER) will be identified. Types of data which comprise a TDP are defined in MIL-STD-31000A, Technical Data Packages, 26 February 2013. "Other" data may be further categorized, such as Administrative Data, Provisioning, Configuration Management, etc.

Block D. SYSTEM/ITEM Identifies the system, item, or project designator or name.

Block E. CONTRACT/PR NO.

Identifies the contract number. This block may also reflect the procurement request (PR) or the request for proposal (RFP) number or other appropriate designator.

Block F. CONTRACTOR The contractor's name. Following the name, a slash ("/") and the contractor's commercial and government entity (CAGE) code may be inserted.

(The next four items appear at the bottom of the form, i.e., after Blocks 1 through 16.)

Block G. PREPARED BY The preparer's name and organization responsible for preparation of the CDRL. The signature of the preparer will be on the last page of the exhibit.

Block H. DATE The date the CDRL was prepared.

Block I. APPROVED BY The name of the individual responsible for approving the CDRL. The approving official's signature will be on the last page of the exhibit.

DD FORM 1423

Attachment J-19

Block J. DATE The date the CDRL was approved.

NOTE: Blocks G through J need only be signed on the last page of each CDRL exhibit when the preparing and approval authority is the same throughout the entire exhibit. All other pages should contain the typed name and date as shown on the last page.

Detailed Block Information (Blocks 1 through 16)

Block 1. DATA ITEM NO.

The 4-character exhibit line item number (ELIN). The first and/or second positions consist of the exhibit identifier, and the remaining positions are assigned sequentially.

Block 2. TITLE OF DATA ITEM The exact title of the data item description (DID) cited in Block 4. When the ELIN is used to acquire weapon system technical manuals, the title of the specific type of technical manual being acquired shall be reflected.

Block 3. SUBTITLE If the title requires further identification, a subtitle is cited. (Optional entry.)

Block 4. AUTHORITY (DATA ACQUISITION DOCUMENT NO.)

The DID identification number, military specification or standard number, or one-time DID number which provides the data preparation instructions. If a Technical Manual Contract Requirements (TMCR) document is used, the block will state "See TMCR _____" and the TMCR will be attached to the CDRL. The TMCR will list the applicable military specifications and/or standards which provide the data preparation instructions.

Block 5. CONTRACT REFERENCE The specific paragraph number of the statement of work (SOW), specification, standard, or other applicable document which contains the tasking which generates a requirement for the data item.

Block 6. REQUIRING OFFICE The technical office having responsibility for ensuring the adequacy of the data. Acronyms are defined in the Addressee List.

Block 7. DD 250 REQ The applicable code, extracted from Table 1, designating the requirements for inspection and acceptance of the data.

CODE DEFINITION

DD 250

CODE

INSPECTION ACCEPTANCE

SS Source Source DD Destination Destination

DD FORM 1423

Attachment J-19

SD Source Destination DS Destination Source LT* Letter of Transmittal Only NO* No inspection, acceptance or letter of transmittal required.

XX Inspection and acceptance requirements specified elsewhere in the contract.

* These codes have not been used for data comprising final delivery of Technical Data Packages or for Technical Manuals. (LT may, however, be used for delivery of preliminary TDPs or TMs). LT is not to be used when inspection is required. LT will be used when approval of a draft is required in Block 8. LT is also used when the contracting agency does not desire to have a DD Form 250. 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 quality assurance (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 inspection.

Table 1. Data Inspection and Acceptance Codes Instruction

Block 8. APP CODE

Items of critical data requiring specific advanced written approval, prior to distribution of the final data item, will be identified by placing an "A" in this field (i.e., test plans, procedures, program plans or any documentation that requires Government approval prior to the contractor taking an action). Block 16 of the ELIN will show length of time required for Government approval/disapproval and subsequent turn-around 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 requirement, i.e., approval of technical content and/or format.

“Draft” is defined as an initial product that was generated and reviewed to support the assessment of other products, but that is expected to undergo further refinement before being assessed for sufficiency or baselined.

“Preliminary” is defined as being reviewed and assessed sufficient to proceed to the next phase

“Final” is defined as being reviewed and assessed sufficient to proceed to the next phase, and to be established as a baseline under Configuration Management (CM).

“Update” is defined as being updated in accordance with established CM processes, with the last “update” being considered the final.

DD FORM 1423

Attachment J-19

Block 9. DIST STATEMENT REQUIRED The code letter (e.g., A, B, C, D, E, F, or X) corresponding to the distribution statement to be marked on the data item by the contractor, in accordance with DoDI 5230.24, Distribution Statements on Technical Documents, 23 August 2012. Block 16 of the ELIN will reflect the appropriate statement and will include the reason, date of determination and controlling DoD office. If the appropriate statement is not known, or if it may vary among specific submissions under this item, a "TBD" or "see Block 16" will be reflected in the block and the requirement for the distribution statement will be defined in Block 16.

Block 10. FREQUENCY Table 2 provides a list of typical codes used to specify the frequency of a submittal.

CODE FREQUENCY

ANNLY Annually ASGEN As generated* ASREQ As required* BI-MO Every two months BI-WE Every two weeks DAILY Daily DFDEL Deferred delivery MTHLY Monthly ONE/R One time with revisions OTIME One time QRTLY Quarterly R/ASR Revisions as required* SEMIA Every six months WEKLY Weekly XTIME Multiple separate submittal

(2TIME, 3TIME, etc.)

NOTE: The codes are limited to five (5) digits for automation purposes.

* The ELINs using these codes will have an additional explanation in Block 16 to provide the contractor with guidance necessary to accurately price the deliverable data item.

Table 2. Data Submittal Frequency Codes

Block 11. AS OF DATE If the data are submitted multiple times, the number of days prior to the end of the reporting period will be cited. 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" places the "as of date" at the end of each month, quarter, etc. If the data are submitted only once, the "as of date" will be as follows: year/month/day, e.g. 91MAR10. If an "as of date" is not applicable, this Block will be blank.

Block 12. DATE OF FIRST SUBMISSION

DD FORM 1423

Attachment J-19

If the submittal is constrained by a specific event or milestone, the constraint will be reflected.

The number of days after contract (DAC) start that the data are due, 30 DAC may be cited.

Typical abbreviations used in Block 12 are shown in Table 3. When there is no constraint, the initial submission date of the data items are expressed as year/month/day, e.g., 91MAR10.

Unless otherwise specified, the data item may be submitted earlier than the due date.

NOTE: There are no classified dates incorporated into the CDRL.

CODE FREQUENCY

ASGEN As generated ASREQ As required DAC Days after contract start DARC Days after receipt of comments DATC Days after test completion DPTT Days prior to test EFDEL Deferred delivery EOC End of contract EOM End of month EOQ End of quarter

Table 3. Typical abbreviations used to identify conditions of initial and subsequent submission

Block 13. DATE OF SUBSEQUENT SUBMISSION If data are to be submitted more than once, the dates of subsequent submissions will be identified. If submittal is constrained by a specific event or milestone, use codes similar to those used in Table 3. Unless otherwise specified, the data item may be submitted earlier than the due date.

NOTE: No classified dates are cited in the CDRL.

Block 14. DISTRIBUTION The addressees and the number of draft copies and final copies (regular and reproducible) to be provided to each. DoD component designator and office symbols/ codes may be used, however, an explanation of these will be provided in the Addressee listing. The first addressee will be the acceptance activity for the data if acceptance by DD 250 is to be accomplished at destination (see Block 7). When reproducible copies (e.g., magnetic tape, vellum, negative, etc.) are required, an explanation will be in Block 16. If the data are not to be delivered to the Government or associated contractors, or if deferred delivery is required, "DFDEL" will be entered in this Block or an explanation will be given in Block 16.

Block 15. TOTAL The total number of draft and final (regular/ reproducible) copies required by Block 14.

Block 16. REMARKS This Block provides additional or clarifying information for Items 1 through 15. For example, it may contain tailoring instructions for the document listed in Block 4. Tailoring may be

DD FORM 1423

Attachment J-19 accomplished by stating the deletions (e.g., "Delete 10.4") or by stating which requirements apply (e.g., "Only 10.4 and 10.5 apply."), whichever is more efficient. When appropriate, this Block clarifies delivery dates in Blocks 12 and 13. It may also indicate the desired medium for delivery of the data and the nature of reproducible copies in Block 14. Block 16 may also specify "contractor format is acceptable." For data which requires a distribution statement as indicated by Block 9, an entry similar to the following entry will be made in Block 16:

"Distribution Statement ___ shall be applied to this data".

The following instructions apply to completion of Block 17 and Block 18 by contractor personnel.

Block 17. PRICE GROUP

Enter the appropriate price group based on the following groups:

a. Group I - Data which the contractor prepares to satisfy the Government's requirements.

The contractor does not need this type of data to perform the rest of the contract. Price would be based on identifiable direct costs, overhead, General and Administrative (G&A) and profit.

b. Group II - Data essential to contract performance which must be reworked or amended to conform to Government requirements. The price for data in this group would be based on the direct cost to convert the original data to meet Government needs and to deliver it, plus allocable overhead, G&A and profit.

c. Group III - Data which the contractor must develop for his own use and which requires no substantial change to conform to Government requirements regarding depth of content, format, frequency of submittal, preparation, and quality of data. Only the costs of reproducing, handling and delivery, plus overhead, G&A and profit are considered in pricing data in this group.

d. Group IV - Data which the contractor has developed as part of his commercial business.

Not much of this data is required and the cost is insignificant. The item should normally be coded "no charge". An example is a brochure or brief manual developed for commercial application which will be required in small quantities and the added cost is too small to justify the expense of computing the charge that otherwise would go with the acquisition.

Block 18. ESTIMATED TOTAL PRICE For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The entry "N/C" for "no charge" will not be acceptable. The estimated price shall not include any amount for rights in data. The government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423

Attachment J-19

ADDRESSEE LIST

DD FORM 1423 (CDRL)

BLOCK 14 ENTRY (See Block 16) COMPLETE ADDRESS

Procuring Contracting Officer (PCO) Commander, Naval Sea Systems Command Department of the Navy ATTN: John N. Butto, SEA02532 1333 Isaac Hull Avenue SE

Washington Navy Yard, DC 02376

Unclassified email: john.butto@navy.mil

Program Manager (PM) Commander, Naval Sea Systems Command Department of the Navy

ATTN: John V. Funn, PEO IWS 2A 1333 Isaac Hull Ave., SE

Washington Navy Yard, 20376

Unclassified email: john.funn@navy.mil

Surface Combat System Center (SCSC) V-95 Radar Facility, SCSC, Wallops Island, VA

Performance Assessments and Root Earned Value Management (EVM) Central Repository Cause Analyses (PARCA) (EVM-CR) on the DCARC Portal:

https://service.dcarc.cape.osd.mil/DCARCPortal/

Defense Cost and Resource Center Cost and Software Data Reporting (CSDR) Submit-Review (DCARC) (CSDR-SR)/1921-3 Submit-Review on the DCARC Portal:

https://service.dcarc.cape.osd.mil/DCARCPortal/

Data Manager UNCLASSIFIED Mailing

Naval Surface Warfare Center, Dahlgren Division ATTN: EASR Data Manager / Q40 18444 Frontage Road, Suite 332 Dahlgren, VA 22448-5161

CLASSIFIED Mailing

OUTER ENVELOPE:

Naval Surface Warfare Center Dahlgren Processing Center 6146 Tisdale Road, Suite 237 Dahlgren, VA 22448-5158

DD FORM 1423

Attachment J-19

INNER ENVELOPE:

Naval Surface Warfare Center, Dahlgren Division ATTN: EASR Data Manager / Q40 18444 Frontage Road, Suite 332 Dahlgren, VA 22448-5161

Unclassified email: To be provided.

Integrated Digital Environment (IDE) Data to be posted to the Government IDE (Please see SOW, Section 3.1.7.8 and 3.3.1.9.6). Classified data will be submitted to the classified IDE (SIDE). Unclassified data will be submitted to the Unclassified Collaborative Environment (UCE).

DD FORM 1423

Attachment J-19

GENERAL DD FORM 1423 NOTES

The following general notes apply to all data items required for delivery under this Contract/PR unless specifically identified as being applicable to individual Exhibit line Items only:

NOTE 1 In order to ensure that the Distribution Statement is indicated on each "copy" delivered to the

Government, the Distribution Statement should be affixed to the original/reproducible copy from which the Government copies will be produced.

Unless otherwise notified by the Program Manager, the Distribution Statement affixed to the final/finalized version of a document shall be identical to the Distribution Statement affixed/assigned to the draft/ preliminary/review/manuscript copy of said document.

NOTE 2 Data will be reviewed for accuracy, completeness and legibility to ensure that it is fully adequate for its intended use. When approval of a particular DD Form 1423 data item is required ("A" entered in Block 8), said approval will be based upon technical content and contractor compliance with applicable contract/ specification requirements.

NOTE 3 When the Contractor mails any information to the Government, the Government’s data manager must be notified via email. The email must include the tracking number.

NOTE 4 Enterprise Air Surveillance Radar (EASR) Variant 1 is a single-face array with rotating positioner to provide A/NSPS-48 and AN/SPS-49 capabilities for installation on Amphibious Warfare Ships as defined in the EASR System Requirements Document (SRD).

EASR Variant 2 is a three-face fixed array design slated for Aircraft Carriers as defined in the EASR System Requirements Document (SRD).

NOTE 5 “Software Build (SB) (Current Build)” deliveries are defined as delivered products containing a subset of requirements and design data pertaining to the current software Build, where software Builds are defined in the Software Development Plan (SDP) (CDRL A050).

“SB (Next Build)” deliveries are defined as delivered products containing a subset of requirements and design data pertaining to the next software Build after the current Build, where software Builds are defined in the SDP (CDRL A050).

“SB-Independent” deliveries are defined as delivered products containing a subset of requirements and design data pertaining to all software Builds within a Software Configuration Item (CI), including, reliability, availability, personnel/usability, security, safety, training, logistics, and packaging, where software Builds are defined in the SDP (CDRL A050).