Exhibit_A-1_EWTS_CDRLS_Information_Package.pdf

TABLE OF CONTENTS MATRIX

N00024-18-R-5113

C.4.1

Page I of4

CORL DID NUMBER TITLE OF DID {SUBTITLE) CONTRACT REFERENCE

EXHIBIT A

AOOI DI-FNCL-80166C PROGRAM COST AND TECHNICAL DATA SOW PARA C.3.1

REPORTS (F£NANC1AL & TECHNICAL STATUS

REPORT)

A002 D1-IPSC-8 I434A INTERFACE REQUfREMENTS SPECIFICATION SOW PARAs C.3.l and C.3.4.1

(IRS)

A003 D1-JPSC-8 I 436A INTERFACE DESIGN DESCRIPTION (IDD) SOW PARAs C.3.1 and C.3.2

(INTERFACE DESIGN DOCUMENT/WEAPON

SPECIF[CATIONS (WS))

A004 DI-IPSC-81438A SOFTWARE TEST PLAN (STP) SOW PARAs C.3.1, C.3.2 and C.4.1

AOOS D1-IPSC-81439A SOFTWARE TEST DESCRJPTION (STD) SOW PARAs C.3.1, C.3.2 and C.4.1

A006 DI-IPSC-81440A SOFTWARE TEST REPORT (STR) SOW PARAs C.3.1, C.3.2 and C.4.1

A007 DI-NDT!-80603A TEST PROCEDURE SOW PARAs C.3.1, C.3.2 and C.4.1

AOOS Dl-NDTl-80809B TEST/INSPECTION REPORT (TEST REPORTS) SOW PARAs C.3. I, C.3.2 and C.4.1

A009 DI-SESS-806390 ENGINEERING CHANGE PROPOSAL (ECP) SOW PARAs C.3.1, and C.3.2

AOIO DI-IPSC-8143 IA SYSTEM/SUBSYSTEM SPECIFICATION (SSS) SOW PARAs C.3.1, C.3.2, C.3.2.1, C.3.4.1 and C.4.1

AOll Dl-IPSC-81431A SYSTEM/SUBSYSTEM DESIGN DESCRIPTION SOW PARAs C.3.1, C.3.2, (SSDD) C.3.2.1, C.3.4.l and

A012 DI-MGMT-81797 PROGRAM MANAGEMENT PLAN SOW PARA C.3.l

AOl3 Dl-MGMT-81861A INTEGRATED PROGRAM MANAGEMENT SOW PARA C.3.1 REPORT (lPMR) (INTEGRATED MASTER

SCHEDULE)

A014 D1-HFAC-8 I 743A HUMAN SYSTEMS INTEGRATION PROGRAM SOW PARAs C.3.1 and C.3.2

PLAN (HSIPP)

AOl5 D1-!PSC-81437A DATABASE DESIGN DOCUMENT (DBDD) SOW PARAs C.3.1, C.3.2 and C.4.1

A016 D1-IPSC-81427A SOFTWARE DEVELOPMENT PLAN (SOP) SOW PARAs C.3. I, C.3.2 and

CDRL DID NUMBER

A017 D1-JPSC-81435A

A018 DI-1PSC-81442A

AOl9 DI-IPSC-81443A

A020 DJ-IPSC-81433A

A021 DI-ADMN-81373

A022 Dl-ADMN-8I505

A023 DJ-SESS-80776A

A024 DI-SESS-8 l 785A

A025 DI-MGMT-80227

A026 DJ-ILSS-80095

A027 M!L-PRF-296t2A

A028 DI-IPSC-81488

A029 DI-lPSC-81756

A030 Dl-MGMT-80269

A031 DI-MGMT-81842

A032 Dl-MGMT-81843

A033 DI-MGMT-81844

TITLE OF DID (SUBTITLE)

SOFTWARE DESIGN DESCRIPTION (SDD)

SOFTWARE VERSION DESCRIPTION (SVO)

SOFTWARE USER MANUAL (SUM)

SOFTWARE REQUIREMENTS SPECIFICATION

(SRS)

PRESENTATION MATERIAL (BRlEFING

MATERIAL)

REPORT, RECORD OF MEETING/MINUTES

TOP

SYSTEMS ENGINEERING MANAGEMENT PLAN

(SEMP)

CONTRACTOR'S PROGRESS, STATUS AND

MANAGEMENT REPORT

INTEGRATED LOGISTICS SUPPORT PLAN

TRAINING DATA PRODUCTS (TRAINING

MATERIALS)

COMPUTER SOFTWARE PRODUCT

(SOFTWARE, SOURCE CODE AND

DOCUMENTATION)

SOFTWARE DOCUMENTATION (SOFTWARE

DOCUMENTATION AND TEST READINESS)

STATUS OF GOVERNMENT FURNISHED

EQUIPMENT REPORT (GOVERNMENT

FURNISHED EQUIPMENT (GFE) REPORT)

VULNERABILITY SCAN COMPLIANCE (VSC)

REPORT (SYSTEM SECURITY MANAGEMENT)

INFORMATION ASSURANCE (IA) TEST REPORT

(CYBER SECURITY/INFORMATION

ASSURANCE (IA) TEST REPORT)

INFORMATION ASSURANCE (IA) TEST PLAN

(CYBER SECURITY/INFORMATrON

ASSURANCE (IA) TEST PLAN)

Page 2 of4

CONTRACT REFERENCE

SOW PARAs C.3.1, C.3.2 and

SOW PARAs C.3.1, C.3.2 and C.4.1 SOW PARAs C.3.1, C.3.2 and C.4.1 SOW PARAs C.3.1, C.3.2 and C.3.3

SOW PARAs 3.1 andC.3.1.1

SOW PARAs3.I andC.3.1.J

SOW PARAsC.3.1.1 and C.3.2

SOW PARA C.3.1

SOW PARAs C.3.t andC.3.2.t

SOW PARAs C.3.1 andC.4. t

SOW PARAs C.3.1 andC.3.3

SOW PARAs C.3.1 andC.3.3

SOW PARA C.3.1.4 andC.3.5

SOW PARAs 3.1 andC.3.2.2

SOW PARA C.3.2.2

CDRL DID NUMBER

A034 DI-MGMT-81845

A035 DI-NDTl-808098

A036 DI-NDTJ-80809B

A037 D1-IPSC-81441A

A038 DI-MlSC-81283

A039 DI-MGMT-81844

A040 DI-MGMT-80596

A041 DI-SESS-81875

A042 OJ-SAFT-8I 065

A043

A044 Ol-MlSC-80508B

A045 Dl-CMAN-81516

A046 DI-SESS-81656

A047 DI-QCIC-81794

A048 DI-MGMT-8I 804

A049 DI-MGMT-81808

A050 DI-SESS-8 l 6 l 3A

TITLE OF DID (SUBTITLE)

INFORMATrON ASSURANCE(IA) DESIGN

REVIEW INFORMATJON PACKAGE(DRIP)

(CYBER SECURITY/INFORMATION

ASSURANCE(IA) DESIGN REVIEW

INFORMATION PACKAGE(DRIP))

TEST/INSPECTION REPORT (SOFTWARE

TROUBLE REPORTS)

TEST/INSPECTION REPORT (HARDWARE

TROUBLE REPORTS(HTR))

SOFTWARE PRODUCT SPECIFICATION(SPS)

SPECIFICATION REQUIREMENT

VERIFICATION MATRIX

TEST PLAN (SYSTEM AND UNIT LEVEL TEST

PLAN)

GOVERNMENT FURNISHED INFORMATION

DEFICIENCY REPORT (DEFICIENCY REPORT)

CONFIGURATION MANAGEMENT PLAN

SAFETY STUDIES REPORT

(INFORMATION SUPPORT PLAN)

TECHNICAL REPORT - STUDY/SERVICES

AS BUJLT CONFIGURATlON LIST(ABCL)

SOURCE DATA FOR FORECASTING

DIMINISHING MANUFACTURING SOURCES

AND MATERIAL SHORTAGES(DMSMS)(DMS

ENGINEERING, MODELING AND HEALTH

ASSESMENT)

QUALITY ASSURANCE PROGRAM PLAN

(QUALITY MANAGMENT PLAN(QMP))

UNIQUE IDENTIFICATION (lUID) MARKING

ACTIVITY, VALIDATION AND VERIFICATION

REPORT

CONTRACTOR'S RISK MANAGEMENT PLAN

(RISK/OPPORTUNITY MANAGEMENT PLAN)

RELIABILITY AND MAINTAINABILITY(R&M)

PROGRAM PLAN

Page 3 of4

SOW PARAs C.3.1 and C.3.3

SOW PARAs C.3.0, C.3.1, C.3.1.4, C.3.2, C.3.3

SOW PARAs C.3.1 and C.3.3

SOW PARAs C.3.1, C.3.2.1, C.3.4.1

SOW PARA 3.0

SOW PARAs C.3.0, C.3.1 and C.3.5

SOW PARA C.3.l

SOW PARAs C.3.1 and C.3.2.3

SOW PARAs 3.0

SOW PARAs C.3.0

SOW PARA C.3.2.1

SOW PARA C.3.3

SOW PARA C.3.1

SOW PARA C.3.4.1

SOW PARA C.3.1

CORL DID NUMBER

A051 DI-SESS-80255A

EXHIBITB

BOO! DI-ADMN-80925

TITLE OF DID {SUBTITLE)

FAILURE SUMMARY AND ANALYSIS REPORT

(CORRECTIVE ACTION SUMMARY REPORT)

REVISIONS TO EXISTING GOVERNMENT

DOCUMENTS (TECHNICAL MANUALS (TM))

Page 4 of4

ATTACH I to the Contract

ATTACHMENT TO THE CORL

ATTACHMENT TITLE

GENERAL DD FORM 1423 GLOSSARY WITH

ADDRESSEE LIST

TECHNICAL DATA PACKAGE (TOP) OPTION

SELECTION WORKSHEET

NUMBER OF PAGES

ATTACHMENT 1 TO THE CDRL

GENERAL DD FORM 1423

GLOSSARY WITH ADDRESSEE

LIST

N00024-18-R-5113

GENERAL DD FORM 1423 GLOSSARY

WITH ADDRESSEE LIST

(Addressee List begins on page 7)

A. The following information is keyed to and provides explanations for entries in Blocks A through J of the DD Form 1423 Exhibit(s):

Block A.

Block B.

Block C.

Block D.

Block E.

Block F.

CONTRACT LINE ITEM NO.

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

EXHIBIT

The exhibit identifier for this CORL (see DFARS 204.7105-3 for exhibit identifiers).

NOTE: DFARS 204.7105-2 specifies that the DD Form 1423 shall always be an exhibit.

CATEGORY

The appropriate category (i.e. Technical Data Package (TDP), Technical Manual (TM), or "Other" data (OTHER)) for the data item. Types of data which comprise a TOP are defined in MIL-T-31000 and MIL-DTL-3 IOOOB (as applicable). Types ofmanuals included under the TM category are defined in Part IX, Section B, of DoDI 5000.2. "Other" data may be further categorized, such as Administrative Data, Provisioning Data, Configuration Management Data, etc., per the functional area assignments contained in DoD 50 I 0.12-L, Acquisition Management Systems and Data Requirements Control List (AMSDL).

SYSTEM/ITEM

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

CONTRACT/PR NO.

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

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 I through 16.)

Block G.

Block H.

Block l.

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.

DATE

The date the CORL was prepared.

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.

Page I of?

BlockJ. DATE The date the CORL was approved.

NOTE: Blocks G through J need only be signed on the last page of each CORL exhibit when the preparer and the approving official are the same throughout the entire exhibit. All other pages should contain the typed name and date entered on the last page.

B. The following information is keyed to and provides explanations for entries in Blocks I through 16 of the DD Form 1423 Exhibit(s):

Bloc!< 1.

Block 2.

Block 3.

Block 4.

Block 5.

Block 6.

Block 7.

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. The letters "I" and "O" are not used. ELIN sequencing order can be found in DFARS 204.7106. All ELINs between the first and last ELIN will be accounted for in the exhibit.

TITLE OF DATA ITEM DESCRIPTION

The exact title ofthe Data Item Description (DID) cited in Block 4. When the ELIN is used to acquire Technical Manuals"{TMs), a Technical Manual Contract Requirements (TMCR) document will be cited in Block 4, and the entty in Block 2 will be the title of the specific type of TM being acquired.

SUBTITLE

Further identification of the data item to supplement the title, ifrequired (optional entry).

AUTHORITY (DATA ACQUISITION DOCUMENT NO.)

The Data Item Description (DID) identification number, One-Time DIP number, or Technical Manual Contract Requirements (TMCR) number ofthe document which defines data content and format requirements. Ifa TMCR is used, this block will state "See TMCR " and the TMCR will be attached to the CORL. The TMCR will list the applicable military specifications and/or standards which provide the data preparation instructions. With the exception ofa One-Time DID, the document(s) cited in this block (or listed in the TMCR, when used) will have been cleared for listing in DoD 50 I 0.12-L, Acquisition Management Systems and Data Requirements Control List {AMSDL).

CONTRACT REFERENCE

The specific paragraph number of the applicable contractual document which contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

REQUIRING OFFICE

The technical office having responsibility for ensuring the technical adequacy of the data.

DD250REQ

The applicable code, extracted from Table I, designating the requirements for inspection and acceptance of the data. The DD Form 250 shall be delivered to the first addressee in Block 14, unless otherwise indicated in Block 16.

Page 2 of7

Block 8.

APP CODE

Identification, by entry ofan "A", ofa requirement for advance written approval prior to final distribution ofan item ofcritical data (i.e. , test plans, test procedures, program plans, or any other documentation that requires Government approval prior to the contractor taking an action). An "A" in this block indicates that a preliminary draft is required. Block 16 ofthe ELIN will show length oftime 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 ofthe approval requirement, e.g., approval of technical content and/or format.

TABLE l. DATA INSPECTION AND ACCEPTANCE CODES

CODE

DD250 CODE

ss

DD

SD

DS

DEFINITION

INSPECTION

Source* Destination Source* Destination

ACCEPTANCE

Source* Destination Destination Source*

LT**

NO**

xx

Letter of transmittal only No inspection, acceptance or letter oftransmittal required.

Inspection and acceptance requirements specified elsewhere in the contract.

Block 9.

Block 10.

Source indicates contractor facility.

These codes are not authorized for data comprising final delivery ofTechnical Data Packages or for Technical Manuals. (LT may, however, be used for delivery ofpreliminary TDPs or TMs.)

LT is not authorized for use when inspection is required. LT will be used when approval ofa draft is required in Block 8. LT is also used when the contracting agency does not desire to have a DD Form 250 for each and every piece ofdata developed by the contractor. The only other authorized use ofthe LT is the special case where the contracting agency does not desire to have separate DD Forms250, 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, via the QA letter ofinstruction, to provide comments.

DIST STATEMENT REQUIRED

The code letter (e.g., A, B, C, D, E, F, or X) con·esponding to the distribution statement to be marked on the data item by the contractor, in accordance with DoDD 523024, Distribution Statements on Technical Documents. Block 16 of the ELIN will reflect the appropriate statement and will include the reason, date ofdetennination, and controlling DoD office. Ifthe appropriate statement is not known, or ifit may va1y among specific submissions under this item, "See Block 16" will be entered in this block and explanatory information will be provided in Block 16. lfthe data item is not technical in nature and does not require a distribution statement, an "N/A" for "Not Applicable" will be entered in this block.

FREQUENCY

The frequency ofdata submittal. Entries in this block are explained in Table2. Ifthe data is ofa recurring type, it is to be submitted at the end of the reporting period established in this block unless otherwise indicated in Block 16.

Page 3 of7

TABLE 2. DATA SUBMITTAL FREQUENCY CODES

FREQUENCY

ANNLY

ASGEN*

ASREQ*

BI-MO

BI-WE

CP/RQ*

DAILY

DFDEL

MTHLY

ONE/R

OTIME

QRTLY

R/ASR*

SEMIA

WEKLY

XTIME

See Block 16*

Annually As generated As required Every two months Every two weeks Change pages as required Daily Deferred delivery (See DFARS 252.2 27-7026) Monthly One time with revisions One time (Does not include draft submissions) Quarterly Revisions as required Every Six months Weekly Multiple separate submittals {2 TIME,3TIME,etc.) (Docs not include draft submissions) Requirement is fully described in Block 16. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in Block 16.

Block I 1.

Block 12.

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

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

AS OF DATE

Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered in this block to indicate the number of calendar days prior to the end of the reporting period, established in Block I0, that data collection will be cut off. For example," 15" would place the "as of date" for the data at 15 days before the end ofthe month, quarter,or year, depending on the frequency established in Block 10; a "O" would place the "as of date" at the end of each month, quarter, etc. If the data is submitted only once, the "as ofdate" will be as follows:

year/month/day, e.g.,90MARl5. rfan "as of date" is not applicable, an entry of "N/A" will be made in this block.

DATE OF FIRST SUBMlSSION The due date for initial data submission. This is nonnally the postage date or date the data is delivered to the ACO,entered as year/month/day (e.g.,90MARl5) or keyed to a specific event or milestone,using a code from Table 3.

NOTE: No classified dates are cited in the CORL.

TABLE 3. DATA SUBMISSION CODES

DEFINITION

ASGEN*

ASREQ*

DFDEL*

XDAC**

As generated As required Deferred delivery Days after contract award

XDACM**

XDARP**

XDARC**

XDATC**

NLT

EOC

EOM

EOQ

See Block 16*

Days after contract modification Days after reporting period Days after receipt of comments Days after test completion No later than End of contract End of month End of quarter Used to indicate requirement is fully described in Block 16.

Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in Block 16.

Block 13.

Block 14.

Block 15.

Block 16.

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

"'* The "X" is assigned a value indicating the number of days, e.g., 30DAC.

DATE OF SUBSEQUENT SUBM1SS10N

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

NOTE: No classified dates are cited in the CORL.

DISTRIBUTION

The addressees and the number of draft 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 Block7). When reproducible copies (e.g., magnetic tape, vellum, negative, etc.) are required, an explanation will be provided in Block 16. If the data is not to be delivered to the Government or associated contractors, an explanation will be given in Block 16. If deferred delivery is required, "DFDEL" will be entered in this block and amplification will be given in Block 16.

NOTE: No classified dates are cited in the CORL.

TOTAL

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

REMARKS

Contains alt pertinent data information not specified elsewhere on this DD Form 1423 and any amplification ofother blocks on this form (e.g., DID tailoring, 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 medi.um for delivery of the data item, etc.).

C. The following instructions apply to completion of Blocks 17 and 18 by contractor personnel:

Block 17. PRTCEGROUP Specify the appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

Page 5 of7

Block 18.

a. Group J. Definition - Data which is not otherwise essential to the contractor's performance ofthe primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administrative and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance ofthe primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, rrequency of submittal, preparation, control, or quality ofthe data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost ofthe essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data items to the Government.

c. Group m. Definition - Data which the contractor must develop for his internal use in performance ofthc primary contracted effort and which does not require any substantial change to conform to Government requirements with regard to depth ofcontent, format, frequency ofsubmittal, preparation, control, and quality ofthe data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part ofhis nonnal operating procedures and his effort in supplying this data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

ESTIMATED TOT AL 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 ofthat item ofdata. 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 ofthe contract ifno data were required. The entry "N/C" for "no charge" will 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.

Page 6 of7

MAILING ADDRESS

NAVSEA

COMMANDER

NAVAL SYSTEMS COMMAND

ATTN(CODE)

ADDRESSEE LIST

CODE NAME

INTERNET E-MAIL

1333 ISAAC HULL AVENUE SE STOP 2313

WASHINGTON NAVY YARD DC 20376-2313

02513

KLINK

Simon.Klink@navy.mil PEO lWS

PROGRAM EXECUTIVE OFFICE

INTEGRATED WARFARE SYSTEMS

ATTN(CODE)

1333 ISAAC HULL AVENUE SE STOP 2301

WASHINGTON NAVY YARD DC 20376-230 I

IIT

IIT3

SIMON

BRADY

James.Simon@navy.mil Thomas. H.Brady@navy.mil mailto:Simon.Klink@navy.mil mailto:James.Simon@navy.mil mailto:H.Brady@navy.mil mailto:H.Brady@navy.mil