Attachment 1 OCOMMS SOW.pdf

STATEMENT OF WORK

for the

Optical Communications (OCOMMS) Air-Water Interface (AWI) Demonstration System

Development

3 August 2017

DISTRIBUTION STATEMENT A: Approved for public release, distribution is unlimited (23 FEBRUARY 2017)

Table of Contents

1. INTRODUCTION

1.1 Scope

1.2 Background

1.3 Program Definitions

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 OCOMMS Airborne AWI Demonstration System Design, Development and Test (CLIN 0001)

3.1.1 Program Management

3.1.2 Integrated Program Management Report (IPMR), Format 6, Integrated Master Schedule (IMS).. 5

3.1.3 Risk Management

3.1.4 Contract Funds Status Report (CFSR)

3.1.5 Contract Post Award Conference (CPAC)

3.1.6 Technical Interchange Meetings (TIMs)

3.1.7 Quality Assurance

3.1.8 Configuration Management

3.1.9 OCOMMS System Design

3.1.9.1 System Requirements

3.1.9.2 Preliminary Design

3.1.9.3 Final Design

3.1.10 Fabrication

3.1.11 Design Verification Test (DVT)

3.1.11.1 Design Verification Test (DVT) Test Plan and Procedures

3.1.11.2 Test Readiness Review (TRR)

3.1.11.3 Perform Design Verification Test (DVT)

3.1.11.4 Design Verification Test (DVT) Test Report

3.1.12 Hardware Deliverable

3.1.13 Technical Data and Software Deliverables

3.2 Contractor Demonstration Support Efforts (Option CLIN 1001)

3.2.1 Travel

3.2.2 Trip Status Report

3.3 Contract Data Requirements List

3.3.1 Contract Data Requirements List (CLIN 0001)

3.3.2 Contract Data Requirements List (Option CLIN 1001)

4. SECURITY REQUIREMENTS

5. OCOMMS PA UK SUPPORT AND USE OF INFORMATION

1. INTRODUCTION

1.1 Scope

This statement of work (SOW) outlines the tasking to develop a two-way Air-Water Interface (AWI) optical communications demonstration system that will link undersea platforms to aircraft in a joint demonstration with the UK. The US responsibility is to develop and demonstrate the airborne end of the AWI communication link.

a. OCOMMS Demonstration System Development (CLIN 0001): The Contractor shall:

1) Develop an OCOMMS airborne AWI demonstration system which meets all performance requirements of system specification SPAWAR-S-OCOMMS001.

2) Provide program, contract, engineering and finance management.

3) Host and conduct a Contract Post Award Conference (CPAC), System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR) and

Technical Interchange Meetings (TIM) as required per the SOW.

4) Conduct testing of the OCOMMS demonstration system to verify compliance with the requirements.

5) Produce and deliver a technical data package and final drawing packages for the approved OCOMMS demonstration system baseline.

b. OCOMMS Demonstration Support (Option CLIN 1001): The Contractor shall provide support during performance assessment testing at a Government laboratory and during field demonstrations.

1.2 Background

The Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO

C4I) Undersea Integration Program Office (PMW 770) is developing and evaluating communications systems to provide optimal connectivity between undersea and air assets for current and future operations of the US Navy.

Optical Communications (OCOMMS) systems are one of the modes of communications being investigated.

Recently the United States (US) and United Kingdom (UK) governments have initiated a collaborative Project

Arrangement to jointly develop and demonstrate OCOMMS systems during a 5 year effort, which will culminate in an FY20 “at sea” demonstration. The joint demonstration will include an air to underwater (AWI) OCOMMS link and will demonstrate/investigate the range of performance and capabilities for the system in a real-world environment. The US is responsible for development and testing of the airborne AWI system while the UK is responsible for the underwater AWI system.

1.3 Program Definitions

a. OCOMMS PA: A Joint United States (U.S.) and United Kingdom (U.K.) Project Arrangement beginning in FY16 to develop Optical Communications technologies and systems to enable communications between undersea systems and aircraft over a 5 year effort culminating in an FY20 “at sea” demonstration.

b. Air-Water Interface (AWI): Two-way optical communication link between airborne and undersea platforms.

2. APPLICABLE DOCUMENTS

The following specifications, standards and handbooks form a part of this SOW to the extent specified herein. Unless otherwise specified, the Government documents are those listed in the current issue of the DoD Index of Specifications and Standards on the date of the solicitation. The non-Government standards are those in effect on the date of the solicitation. In the event of a conflict between the documents referenced herein and the contents of this SOW, the text of the SOW takes precedence.

Except for the contract specification, all documents shall be obtained from the Standardization Document

Order Desk, 700 Robbins Avenue, Building #4, Section D, Philadelphia, PA 19111-5094. The industry documents shall be obtained from the American National Standards Institute, Attn. Sales Department, 25 W 43 rd

Street, 4 th

Floor, New York, NY, 10036

Type Document Description Date

Standard SPAWAR-S-OCOMMS001 OCOMMS PERFORMANCE

SPECIFICATION

3 August 2017

Standard MIL-STD-31000A DEPARTMENT OF DEFENSE

STANDARD PRACTICE

TECHNICAL DATA PACKAGES

26 February 2013

Standard MIL-STD-129R MILITARY MARKING FOR

SHIPMENT AND STORAGE

18 February 2014

Standard MIL-STD-464C ELECTROMAGNETIC

ENVIRONMENTAL EFFECTS

REQUIREMENTS FOR SYSTEMS

01 December 2010

Standard MIL-STD-810G ENVIRONMENTAL ENGINEERING

CONSIDERATIONS AND

LABORATORY TESTS

15 April 2014

Standard MIL-STD-882E SYSTEM SAFETY 11 May 2012

Standard MIL-STD-1472G HUMAN ENGINEERING 11 January 2012

Standard ISO 9000 QUALITY MANAGMEENT Various

Standard EIA-649-1 CONFIGURATION MANAGEMENT

REQUIREMENTS FOR DEFENSE

CONTRACTS

04 March 2015

Handbook MIL-HDBK-61A CONFIGURATION MANAGEMENT

GUIDANCE

07 February 2001

3. REQUIREMENTS – All tasks contained in this SOW will be funded with Research, Development, Testing and Evaluation (RDT&E) funding

3.1 OCOMMS Airborne AWI Demonstration System Design, Development and Test (CLIN 0001, RDT&E)

3.1.1 Program Management

The Contractor shall provide program management to ensure all work conducted under the contract is planned and executed in a manner that shall achieve all management, technical, logistics, cost, and schedule objectives in accordance with the terms and conditions of the contract and requirements of the SOW.

The Contractor shall manage management insight into all aspects of the OCOMMS demonstration system development and ensure the Government management team has insight into all program activities. The Contractor shall document progress of work in a monthly Contractor’s Progress, Status, and Management Report in accordance with CDRL A001. This report shall contain a summary of all work accomplished, work remaining, key personnel changes, cost curves, and projected expenditures for the period of performance, staffing/labor hours, and itemization of trips and trip reports to include narratives on significant results.

CDRL Deliverable(s):

A001: Contractor’s Progress, Status, and Management Report (DI-MGMT-80227)

3.1.2 Integrated Program Management Report (IPMR), Format 6, Integrated Master Schedule (IMS)

The Contractor shall develop, manage, and deliver, on a monthly basis, a logically networked IMS in accordance with CDRL A002. The IMS shall contain the planned events and milestones, all activities from contract award to contract completion, activity entrance and exit criteria, and risks/risk mitigation activities identified and documented in the Contractor’s Risk Management Plan (RMP) per paragraph 3.1.3. The IMS shall also reflect tasks, dates (baseline, forecast, and actual), external and internal dependencies and relationships necessary to support independent, accurate forecasts of contract milestone delivery dates by both the Contractor and the

Government. The Contractor shall support teleconferences, as needed, to discuss IMS progress and issues and shall be available for review at all Government meetings. This report cycle starts on the award date and continues until the tasking defined in section 3.1 is completed.

A002: Integrated Program Management Report Format 6 (DI-MGMT-81861)

3.1.3 Risk Management

The Contractor shall implement a risk management process to include a risk management plan that assures all programmatic and technical risks throughout the life of the OCOMMS development are addressed. The

Contractor shall track the risks and take the risk mitigation actions necessary to ensure the technical integrity of the

OCOMMS development and minimize the program cost, schedule and performance impacts. Risks, mitigation strategies, contingency plans, and the effects of the mitigation and contingency plans shall be updated as necessary and included in the Monthly Contractor’s Progress, Status, and Management Report (paragraph 3.1.1, CDRL A001) and included during SRR, PDR, CDR, TRR, and TIMs.

CDRL Deliverable(s)

A003: Contractor’s Risk Management Plan (DI-MGMT-81808)

3.1.4 Contract Funds Status Report (CFSR)

The Contractor shall submit a quarterly CFSR in accordance with CDRL A004, CFSR. The CFSR shall be used by the Contractor and the Government to update and forecast contract funds requirements; to plan and communicate funding changes; to develop funding requirements for approved efforts; to determine funds in excess of contract needs and available for de-obligation; and to obtain rough estimates of termination liability and open commitment costs on all cost reimbursable contract line items.

CDRL Deliverable(s)

A004: Contract Funds Status Report (DI-MGMT-81468)

3.1.5 Contract Post Award Conference (CPAC)

A CPAC shall be held at the Contractor’s facility no later than 30 calendar days after contract award to establish a common understanding of all contract requirements. The conference shall provide an overview of the

Contractor’s team members and how the contract reporting requirements will be met. The conference shall also address the Contractor’s IPMR and IMS, configuration management, and test processes, with particular emphasis on the efforts required prior to the SRR and PDR. Any potential problem areas shall be identified and a method of resolution defined.

The Contractor shall deliver a meeting agenda in accordance with CDRL A005. Upon completion of the

CPAC the Contractor shall deliver meeting minutes for Government approval in accordance with CDRL A006.

A005: Presentation Materials (CPAC) (DI-ADMN-81373)

A006: Report, Record of Meeting/Minutes (CPAC) (DI-ADMN-81505)

3.1.6 Technical Interchange Meetings (TIMs)

The Contractor shall conduct and host TIMs semi-annually for tasking identified in section 3.1. There shall be a minimum of two TIMs. The first TIM shall be held no later than 30 calendar days prior to the Contractor scheduled PDR to support the development of a preliminary design concept as identified in paragraph 3.1.9.2. A second TIM shall be held no later than 30 calendar days prior to the Contractor scheduled CDR to support the implementation of a preliminary design concept as identified in paragraph 3.1.9.3.

At its discretion, the Government reserves the right to schedule additional TIMs throughout the period of performance for all tasks defined in section 3.1 to assure the requirements of this SOW are being met.

The Contractor shall deliver TIM presentation material in accordance with CDRL A007 and document action items and respond to all assigned action items as a result of the TIM activity in accordance with CDRL A008.

A007: Presentation Materials (TIM) (DI-ADMN-81373)

A008: Report, Record of Meeting/Minutes (TIM) (DI-ADMN-81505)

3.1.7 Quality Assurance

The Contractor shall manage a quality assurance (QA) program consistent with the Contractor’s normal program and compliant with contract requirements. The Contractor shall utilize an ISO-9001:2000 or equivalent series QA program. The Contractor’s QA program shall include all workmanship, testing, and rework standards.

The contractor shall report the results of QA activities on a monthly basis in the Contractor’s Progress, Status and

Management Report (CDRL A001). The Contractor shall enforce quality assurance requirements throughout development of the OCOMMS System. All quality assurance testing shall be conducted as delineated in the

Contractor’s test program (3.1.11) and delivered to the Government as required in paragraph 3.1.11.1. The

Government reserves the right to inspect or audit the provisions, standards and practices of the QA program at any time.

3.1.8 Configuration Management

The Contractor shall utilize a Configuration Management (CM) process to control all configuration documentation. When changes are necessary to the form, fit, and function, the contractor shall prepare and submit an

Engineering Change Proposal (ECP) for Government approval (CDRL A009). The contractor shall prepare and submit Class I ECPs only with the prior written approval of the Government. The contractor shall use MIL-HDBK-

61A as a guide.

A009: Engineering Change Proposal (ECP) (DI-SESS-80639D)

3.1.9 OCOMMS System Design

3.1.9.1 System Requirements

The Contractor shall conduct a System Requirements Review (SRR), at the Contractor’s facility (unless otherwise designated by the Government), to determine readiness to proceed with preliminary design of the

OCOMMS System. The purpose of SRR is to ensure that system performance requirements have been completely and properly identified and that a mutual understanding between the Government and Contractor exists as to requirements. To receive Government approval to proceed with system development beyond SRR, the contractor shall demonstrate that all system performance requirements are defined and testable. At a minimum, cost, schedule, risk, technology readiness shall be evaluated. The SRR shall be scheduled and held in accordance with the

Contractor’s IMS. The Contractor shall deliver SRR presentation material in accordance with CDRL A010 and

SRR Meeting Minutes in accordance with CDRL A011. To proceed beyond SRR, at a minimum, the contractor shall provide the following:

a. Requirements Traceability Matrix (RTM)

b. Updated performance, cost and schedule risks

c. Current cost estimate

d. Updated program schedule and critical path analysis

e. Staffing profile

A010: Presentation Materials (SRR) (DI-ADMN-81373)

A011: Report, Record of Meeting/Minutes (SRR) (DI-ADMN-81505)

3.1.9.2 Preliminary Design

The Contractor shall perform analysis and develop preliminary design concepts detailing how the

Contractor will implement the OCOMMS Airborne AWI Demonstration System design required to meet the performance specifications in SPAWAR-S-OCOMMS001. The Contractor shall develop an architecture that is modular and utilizes non-proprietary or non-vendor-unique hardware designs to the maximum possible extent.

Upon Government approval to proceed beyond SRR, the Contractor shall prepare and present a Preliminary

Design Review (PDR) at the Contractor’s facility (unless otherwise designated by the Government) to detail what the Contractor has determined as the appropriate design concept. The PDR is a technical assessment that establishes the allocated baseline and ensures the system will meet performance requirements. The PDR shall be scheduled and held in accordance with the Contractor’s IMS. At the PDR, the Contractor shall present the proposed design and requirements compliance as set forth in the performance specification (SPAWAR-S-OCOMMS001). The

Contractor shall deliver PDR presentation material in accordance with CDRL A012 to address information requested in items a through j below. The Contractor shall also deliver Draft Interface Control Documents (ICDs) in accordance with CDRLs A014 – A017.

Following the PDR, the Contractor shall generate and provide a detailed PDR report in accordance with

CDRL A013 and the Contractor shall require written approval from the Government PCO prior to the Contractor proceeding to Final Design (3.1.9.3).

To proceed beyond PDR, at a minimum, the contractor shall provide the following:

a. System allocated baseline which consists of initial system design specifications that have been proven by analysis and/or testing, to meet performance requirements

b. Preliminary drawings and schematics that support the design approach

c. Updated performance, cost and schedule risks

d. Current cost estimate per the system allocated baseline

e. Updated program schedule and critical path analysis

f. Updated Requirements Traceability Matrix (RTM)

g. Long-lead item list and preliminary Bill of Materials (BOM)

h. Overview of design considerations for Human Factors included in the overall system

i. Draft Mechanical, Electrical, Software, and Optical ICD

j. Plan to achieve FDA compliance or FDA exemption

A012: Presentation Materials (PDR) (DI-ADMN-81373)

A013: Report, Record of Meeting/Minutes (PDR) (DI-ADMN-81505)

A014: Interface Control Document (Mechanical) (DI-SESS-81248B)

A015: Interface Control Document (Electrical) (DI-SESS-81248B)

A016: Interface Control Document (Software) (DI-SESS-81248B)

A017: Interface Control Document (Optical) (DI-SESS-81248B)

3.1.9.3 Final Design

Upon written Government approval of the PDR Report (CDRL A013), the Contractor shall continue development of the detailed design per the approved preliminary design concept and in compliance with the performance specification (SPAWAR-S-OCOMMS001).

Upon completion of the detailed design effort, the Contractor shall prepare and present a Critical Design

Review (CDR) at the Contractor’s facility (unless otherwise designated by the Government). The purpose of CDR is to assess the final design to ensure that the system can meet the performance specifications in SPAWAR-S-

OCOMMS001 within cost and schedule prior to proceeding into fabrication and test. The CDR shall be scheduled and held in accordance with the Contractor’s IMS. The Contractor shall deliver CDR presentation material in accordance with CDRL A018 and draft Design and Verification Test (DVT) plans and DVT test procedures in accordance with CDRL A019 and A020, respectively. The Contractor shall also deliver updated Draft ICDs in accordance with CDRLs A014 – A017.

Following the CDR, the Contractor shall generate and provide a detailed CDR report in accordance with

CDRL A021 and the Contractor shall require written approval from the Government PCO prior to proceeding to

System Fabrication (3.1.10).

To proceed beyond CDR, at a minimum, the contractor shall provide the following:

a. System allocated baseline which consists of final system design specifications that have been proven by analysis and/or testing, to meet performance requirements and support decision to proceed with fabrication/development

b. Final documents to include drawings and schematics

c. Updated performance, cost, and schedule risks

d. Updated cost estimate per the system allocated baseline

e. Updated program schedule and critical path analysis

f. RTM has been updated

g. Updated BOM

h. Draft DVT plan and test procedure for Government review

i. Detailed design considerations for Human Factors

j. Updated Draft ICDs

k. Updated progress to achieve FDA compliance or FDA exemption

A014: Interface Control Document (Mechanical) (DI-SESS-81248B)

A015: Interface Control Document (Electrical) (DI-SESS-81248B)

A016: Interface Control Document (Software) (DI-SESS-81248B)

A017: Interface Control Document (Optical) (DI-SESS-81248B)

A018: Presentation Materials (CDR) (DI-ADMN-81373)

A019: Test Plan (DVT) (DI-NDTI-80566A)

A020: Test Procedures (DVT) (DI-NDTI-80603A)

A021: Report, Record of Meeting/Minutes (CDR) (DI-ADMN-81505)

3.1.10 Fabrication

Upon Government approval of CDRL A021, the Contractor shall fabricate the airborne AWI system as described in the CDR materials.

3.1.11 Design Verification Test (DVT)

3.1.11.1 Design Verification Test (DVT) Test Plan and Procedures

Upon Government approval of CDRL A021, the Contractor shall develop a final written DVT test plan and

DVT test procedures in accordance with CDRL A019 and A020, respectively, to demonstrate that the OCOMMS

AWI System meets the performance requirements set forth in performance specification SPAWAR-S-

OCOMMS001. To proceed beyond 3.1.11.1, the Contractor shall obtain written approval from the Government

PCO.

A019: Test Plan (DVT) (DI-NDTI-80566A)

A020: Test Procedures (DVT) (DI-NDTI-80603A)

3.1.11.2 Test Readiness Review (TRR)

Upon Government receipt of the final DVT Test Plan (CDRL A019) and DVT Test Procedures (A020), the

Contractor shall prepare and present a Test Readiness Review (TRR) at the Contractor’s facility (unless otherwise designated by the Government) to assess the Contractor’s readiness to proceed to DVT Testing of the OCOMMS

Demonstration System. The TRR assesses test objectives, test methods and procedures, scope of tests, and safety.

The TRR also confirms that required test resources have been properly identified and coordinated to support planned tests. The TRR verifies the traceability of planned tests to requirements as set forth in the performance specification

(SPAWAR-S-OCOMMS001). The TRR shall be scheduled and held in accordance with the Contractor’s IMS. The

Contractor shall deliver TRR presentation material in accordance with CDRL A022 to address information requested in items a through i below

Following the TRR, the Contractor shall generate and provide a detailed TRR report in accordance with

CDRL A023 and the Contractor shall require written approval from the Government PCO prior to the Contractor proceeding to DVT Testing (3.1.11.3).

To proceed beyond TRR, at a minimum, the contractor shall provide the following:

a. Final RTM showing traceability of planned test to the performance specification (SPAWAR-S-

OCOMMS001)

b. Final DVT plan and test procedure for Government approval

c. Available results of subsystem functional tests

d. Detailed test schedule including test resource (equipment and personnel) availability

e. Updated performance, cost, and schedule risks

f. Updated cost estimate per the system allocated baseline

g. Updated program schedule and critical path analysis

h. System design considerations for Human Factors, including Laser Safety

i. Review of FDA compliance or FDA exemption

A022: Presentation Materials (TRR) (DI-ADMN-81373)

A023: Report, Record of Meeting/Minutes (TRR) (DI-ADMN-81505)

3.1.11.3 Perform Design Verification Test (DVT)

Upon Government approval of CDRL A019, CDRL A020 and CDRL A023, the Contractor shall conduct

DVT of the OCOMMS System. The testing shall be completed in accordance with the Government approved test plan and procedures (paragraph 3.1.11.1) and the Contractor’s IMS. Testing shall demonstrate the OCOMMS

Demonstration System meets the performance requirements set forth in specification SPAWAR-S-OCOMMS001.

For any testing conducted at the Contractor’s or Sub-Contractor’s facility, the Contractor shall notify the

Government 30 days in advance to allow Government representation to witness any or all portions of the Contractor performed testing.

Should testing of the OCOMMS System result in failure to pass any of the approved DVT Plan/Procedures, the Contractor shall inform the PCO in writing within five (5) business days of the discovery of non-compliance.

The Contractor shall identify which portions were not met and provide a complete corrective action plan.

3.1.11.4 Design Verification Test (DVT) Test Report

The Contractor shall document all DVT test results and deliver a detailed test report for Government approval no later than 15 days after completion of the DVT in accordance with CDRL A024. As part of the DVT test results, the Contractor shall include a compliance matrix demonstrating how all specification requirements were met. To proceed beyond 3.1.11.4, the Contractor shall obtain written Government approval from the PCO.

A024: Test Reports (DVT) (DI-NDTI-80809B)

3.1.12 Hardware Deliverable

Upon Government approval of the DVT Test Report (CDRL A024), the Contractor shall deliver the

OCOMMS Demonstration System. Contractor shall also provide FDA accession number and documentation, in accordance with CDRL A025, prior to delivery. Either full compliance or partial compliance with FDA approval is required.

A025: FDA Compliance Documentation (DI-MISC-80508B)

3.1.13 Technical Data and Software Deliverables

The Contractor shall produce and deliver a technical data package to include developmental level design drawings for the OCOMMS Demonstration System and to include all computer software product end items in accordance with CDRLs A026 and A027. Design drawings and materials shall be sufficient for installation of the

OCOMMS Demonstration System in the airborne platform and describes how the system is operated. Additionally, the Contractor shall deliver Final ICDs in accordance with CDRLs A014 – A017.

A026: Technical Data Package (DI-SESS-80776A)

A027: Computer Software Product End Items (DI-MCCR-80700)

A014: Interface Control Document (Mechanical) (DI-SESS-81248B)

A015: Interface Control Document (Electrical) (DI-SESS-81248B)

A016: Interface Control Document (Software) (DI-SESS-81248B)

A017: Interface Control Document (Optical) (DI-SESS-81248B)

3.2 Contractor Demonstration Support Efforts (Option CLIN 1001)

The Contractor shall provide support during Government laboratory testing and during field demonstrations. This support shall include onsite technical support, system operations support, any required troubleshooting and analysis, and furnishing a final trip report detailing the entire demonstration evolution.

3.2.1 Travel

The Contractor shall conduct travel to Government test sites as required to accomplish the necessary work.

Government laboratory testing is planned to be conducted at SPAWAR Systems Center Pacific (San Diego, CA) for a period of approximately 4 work weeks, and field demonstration is expected to be conducted at a Government test range on the West Coast of the United States for a period of approximately 4 work weeks. The Contractor shall obtain Government approval in writing from the OCOMMS PCO prior to making travel arrangements for each trip.

For estimation purposes, the Contractor shall assume 2 people will support laboratory testing and the field demonstration as described above. The Contractor shall assume 1 person is a Senior Engineer/Technical Support and

1 person is a Mid-Level Engineer/Technical Support.

3.2.2 Trip Status Report

The Contractor shall deliver trip reports in accordance with CDRL A028 for all trips associated with efforts described in paragraph 3.2. The trip report shall detail all activities, including all results and findings in relation to each specified performance parameter.

A028: Contractor’s Status Report (Trip Report) (DI-MGMT-80368A)

3.3 Contract Data Requirements List

3.3.1 Contract Data Requirements List (CLIN 0001)

The following contain a listing of contract data deliverable items that are required for delivery in support of

CLIN 0001 as part of this contract:

CDRL Number SOW Para Title DID

A001 3.1.1, 3.1.7 Contractor’s Progress, Status and Management

Report

DI-MGMT-80227

A002 3.1.2 Integrated Program Management Report DI-MGMT-81861

A003 3.1.3 Contractor’s Risk Management Plan DI-MGMT-81808

A004 3.1.4 Contract Funds Status Report DI-MGMT-81468

A005 3.1.5 Presentation Materials (CPAC Briefing Package) DI-ADMN-81373

A006 3.1.5 Report, Record of Meeting / Minutes (CPAC) DI-ADMN-81505

A007 3.1.6 Presentation Materials (TIM Briefing Package) DI-ADMN-81373

A008 3.1.6 Report, Record of Meeting / Minutes (TIM) DI-ADMN-81505

A009 3.1.8 Engineering Change Proposal (ECP) DI-SESS-80639D

A010 3.1.9.1 Presentation Materials (SRR Briefing Materials) DI-ADMN-81373

A011 3.1.9.1 Report, Record of Meeting / Minutes (SRR) DI-ADMN-81505

A012 3.1.9.2 Presentation Materials (PDR Briefing Package) DI-ADMN-81373

A013 3.1.9.2 Report, Record of Meeting / Minutes (PDR) DI-ADMN-81505

A014 3.1.9.2, 3.1.9.3, 3.1.13

Interface Control Document (Mechanical) DI-SESS-81248B

A015 3.1.9.2, 3.1.9.3, 3.1.13

Interface Control Document (Electrical) DI-SESS-81248B

A016 3.1.9.2, 3.1.9.3, 3.1.13

Interface Control Document (Software) DI-SESS-81248B

A017 3.1.9.2, 3.1.9.3, 3.1.13

Interface Control Document (Optical) DI-SESS-81248B

A018 3.1.9.3 Presentation Materials (CDR Briefing Package) DI-ADMN-81373

A019 3.1.9.3, 3.1.11.1

Test Plan (DVT) DI-NDTI-80566A

A020 3.1.9.3, 3.1.11.1

Test Procedures (DVT) DI-NDTI-80603A

A021 3.1.9.3 Report, Record of Meeting / Minutes (CDR) DI-ADMN-81505

A022 3.1.11.2 Presentation Materials (TRR Briefing Materials) DI-ADMN-81373

A023 3.1.11.2 Report, Record of Meeting / Minutes (TRR) DI-ADMN-81505

A024 3.1.11.4 Test Reports (DVT) DI-NDTI-80809B

A025 3.1.12 FDA Compliance Documentation DI-MISC-80508B

A026 3.1.13 Technical Data Package DI-SESS-80776A

A027 3.1.13 Computer Software Product End Items DI-MCCR-80700

3.3.2 Contract Data Requirements List (Option CLIN 1001)

The following contains a listing of contract data deliverable items that are required for delivery in support of Option CLIN1001 of this contract.

CDRL Number SOW Para. Title DID

A028 3.2.2 Contractor’s Status Report (Trip Report) DI-MGMT-80368A

4. SECURITY REQUIREMENTS

The nature of this task requires access up to SECRET information. The work performed by the Contractor, as delineated in the DD Form 254, Attachment No. 2, will include access up to SECRET data, information, and spaces.

5. OCOMMS PA UK SUPPORT AND USE OF INFORMATION

As directed, the Contractor shall support the US Government while working with the UK Government and UK

Contractor on matters pertaining to interface control and interoperability of the AWI Airborne Demonstration

System produced by the US and the AWI Underwater Demonstration System produced by the UK. As part of the

OCOMMS PA, the US Government may share information pertaining to the US AWI Airborne Demonstration

System and deliverables developed under this contract with the UK Government and UK Contractor via

Government-to-Government channels. The “UK Contractor” may include any prime contractor, subcontractor, or wholly owned subsidiary performing work currently or in the future related to the UK portion of the OCOMMS PA.

Regarding the export, re-export, transfer, retransfer, or disclosure of any information related to the OCOMMS PA, US or UK AWI Systems, and/or deliverables developed under this contract, the Contractor shall adhere to provision

H-1 and DFARS 252.225-7048, Export-Controlled Items, where applicable.

Information and deliverables to be shared with the UK Government and/or UK Contractor via Government-to-

Government channels may include export controlled data derived from the Interface Control Documents (CDRL

A014, A015, A016, and A017) and DVT Test Reports (CDRL A024), as necessary.