Exhibit_and_Attachments.pdf

ATTACHMENT 1

STATEMENT OF WORK

FOR THE

SUBMARINE ACOUSTIC SYSTEMS

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICER, SUBMARINES (PMS401)

614 SICARD STREET SE

WASHINGTON, NAVY YARD

WASHINGTON, DC 20376

07 May 2014 ii

TABLE OF CONTENTS

1.0 SCOPE 1

1.1.1 Navy Organization 2

1.1.2 The Collaborative Development Environment 2

2.0 REFERENCED DOCUMENTS 2

2.1 GOVERNMENT DOCUMENTS 2

2.2 NON-GOVERNMENT DOCUMENTS 3

3.0 REQUIREMENTS 5

3.1 INTEGRATED PROGRAM MANAGEMENT 5

3.1.1 Progress Reporting 5

3.1.2 Subcontract Management and Control 5

3.1.3 Contract Work Breakdown Structure (CWBS) 5

3.1.4 Integrated Program Management Report (IPMR) 6

3.1.5 Integrated Baseline Reviews 6

3.1.6 Contract Cost and Software Data Reporting (CSDR) for VIRGINIA Class New Construction 6

3.1.7 Program Risk Analysis 7

3.1.8 Program Reviews 7

3.1.9 Design Disclosure, Intellectual Property and Data Rights 7

3.1.10 Data Management 8

3.1.11 Integrated Product Team (IPT) 8

3.1.12 Use of Contractor Facilities 9

3.1.13 Government Furnished Information (GFI) 9

3.1.14 Government-Furnished Property/Equipment/Material (GFP/E/M) 10

3.2 SYSTEM ENGINEERING 10

3.2.1 Systems Engineering Management 10

3.2.2 Technical Reviews 10

3.2.3 System Integration 11

3.2.4 System Engineering and Design Analyses 11

3.2.5 Failure Reporting Analysis and Corrective Action System (FRACAS). 12

3.2.6 SOFTWARE ENGINEERING SERVICES 12

3.2.7 Software Design Requirements 12

3.2.8 Safety 12

3.2.9 Environmental Compliance 13

3.2.10 Problem Reporting System 13

3.2.11 Open Systems Architecture Approach 13

3.3 HARDWARE ENGINEERING 14

3.3.1 Non-Developmental Items (NDI) Licenses 14

3.3.2 Modified NDI 14

3.3.3 Technology Refreshment 14

3.3.4 Engineering Documentation and Drawings 15

3.3.5 Parts Management Program 15

3.3.6 MANUFACTURING ENGINEERING 15

3.3.7 Hardware Requirements Definition 15

3.4 TEST AND EVALUATION (T&E) 15

3.4.1 T&E Program Plan 15

3.4.2 Joint Test Group (JTG) 15

3.4.3 Test Requirements 16

3.4.4 Factory Acceptance Testing 17

3.5 CONFIGURATION MANAGEMENT (CM) 17

3.5.1 Contractor CM Policy and Procedures 17

3.5.2 CM Data Distribution/Access 17

3.5.3 Configuration Identification 17

3.5.4 Configuration Control 18

iii

3.5.5 Configuration Status Accounting System 19

3.6 INTEGRATED LOGISTICS SUPPORT (ILS) 19

3.6.1 Performance Based Logistics (PBL) 20

3.6.2 Integrated Logistics Support Plan (ILSP) 20

3.6.3 Supportability Analyses (SA) 20

3.6.4 Interactive Electronic Technical Manual (IETM) 20

3.6.5 Support and Test Equipment 20

3.6.6 Provisioning Data 20

3.6.7 Diminishing Manufacturing Sources and Material Shortages (DMS/MS) Parts Management 21

3.6.8 Training and Training Support 21

3.6.9 Unique Identification (UID) Requirements. 22

3.6.10 Packaging, Handling, Storage and Transportation (PHS&T) 22

3.6.11 Radio Frequency Identification (RFID) 22

3.7 QUALITY ASSURANCE (QA) 22

3.8 INFORMATION ASSURANCE (IA) 22

3.9 INSTALLATION AND CHECKOUT SERVICES 23

3.9.1 Pre-cable Kit (PCK) 23

3.9.2 Installation Aids 23

3.10 FIELD ENGINEERING SERVICES 23

3.11 MAINTENANCE SUPPORT SERVICES 23

3.12 STUDIES/ANALYSES 23

STATEMENT OF WORK

FOR

SUBMARINE ACOUSTIC SYSTEMS

1.0 SCOPE

This Statement of Work (SOW) defines the efforts required for the program management, systems engineering, engineering, software development, logistics and supportability engineering, configuration management, hardware and software integration (including material procurement or fabrication, and integration of Government-Furnished Material (GFM), as applicable), test, evaluation, and installation of the Submarine Acoustic Systems. Generally, the Submarine Acoustic Systems configurations include the following:

Virginia New Construction Upgrade Kits (SSN688/I, SSN21, SSGN, SSBN, SSN774)

Ohio Replacement (OR) Future Submarines Foreign Military Sales (FMS) Integrated Undersea Surveillance Systems (IUSS) platforms Anti-Submarine Warfare (ASW) Systems Team Training and Trainers

The work shall be performed as specified in the Contract Schedule or as identified in individual Technical Instructions (TIs). This procurement specifically includes the following:

Provide “end-to-end” system engineering development, integration, logistics, test, and life cycle support for the

Submarine Acoustic Systems within the context of definitions and guidance provided in IPTs and tasked in technical instructions.

Define the interface baseline, including all requirements necessary to connect to the Submarine Warfare Federated Tactical System (SWFTS) network and share information.

Participate in the integration efforts including technology refresh/insertion planning and post-subsystem validation testing and integrations across SWFTS boundaries.

Support platform level Installation and Checkout planning requirements, including participation in Installation IPT, Modernization Plan and various reviews and working group meetings.

Incrementally develop Submarine Acoustic Systems configuration variants to host the various platforms as applicable. Each initial delivery of the Mod Variants will include all baseline engineering documentation, product lists, logistics support products, curriculum and support materials, spares and installation and checkout spares as necessary to provide the “as developed” product support, including Trainers.

Support the management and oversight of system level test and evaluation plans as part of Command, Control Communications, Computers, Combat and Intelligence (C5I) system platform integration design/build team for all platform variants.

Define and depict the optimum balance of simulation and stimulation equipment needed to execute subsystem level testing and integration.

Develop Logistics Data, Provisioning, Interactive Electronic Technical Manual (IETM), Interactive Courseware (ICW)/Computer Based Training (CBT) and Interactive Multimedia Instruction (IMI) using common authoring systems and formats to allow for efficient integration with SWFTS. This includes integrating source material as delivered by the interfacing shipboard subsystems contractors for integration for a complete Submarine Acoustic Systems delivery.

Support and conduct installation, field integration, repair and refurbishment efforts as required.

Procure production systems, spares/repair parts, technology refresh/insertion kits, pre-production/production hardware, engineering change kits and associated hardware including spares.

Efforts included under this procurement include legacy Acoustic/ASW System support.

Light Weight Wide Aperture Array (LWWAA) and Light Weight Low Cost Conformal Array (LWLCCA) software development is not part of the RFP and will be developed under separate Full and Open competitive contracts.

However, the Contractor shall be responsible for LCCA and LWWAA inboard hardware as well as associated processing servers as part of the AN/BQQ-10. The Contractor shall also conduct the integration of the LCCA and LWWAA software of these two strings into the AN/BQQ-10.

BACKGROUND

1.1.1 Navy Organization

Program Executive Officer, Submarines (PEO SUB) is the acquisition executive for this procurement. The

PMS401 Submarine Acoustic Systems Program Office is responsible for the acquisition, development, production, fleet introduction and support of the Submarine Acoustic Systems for all classes of Submarines and appropriate Foreign Military Sales efforts. The collaborative development environment has applicability to all Navy Combat Systems processing environments for all host platforms and classes of ships both US and allied forces for those common processing elements.

1.1.2 The Collaborative Development Environment

The contractor will provide for the System Enhancements being developed by PEO IWS5A to be integrated as part of the Submarine Acoustic Systems program in the form of integrating Advanced Processing Builds. This procurement is for the efforts of the lead integrator, who is responsible for the development of software functionality and hardware as well as the integration of software functionality and hardware that is delivered from multiple vendors. Technology Insertions (TIs) and Advanced Processing Builds (APBs) are bi-annual updates to the existing sonar configurations installed on US Navy submarines. This procurement provides for integration, test, acceptance, packaging, and delivery of the submarine A-RCI sonar system for shipboard installation. It also supports platform level Acoustic Systems training and support strategies for optimal Fleet introduction to be implemented commensurate with the program upgrade and modernization plans.

Other vendors provide engineering services and production of the Towed Systems Processing Ownship Monitoring System (OMS) and Common Acoustic Cabinet (CAC). There are also other vendors that provide engineering services and production of the AN/WLY-1 Commercial-Off-The-Shelf (COTS) based Active Intercept (AI) signal processing system Active Intercept & Ranging (AI&R) system, the Archival Media Center (AMC) and miscellaneous equipment. As well as other vendors that provide systems engineering services and support for the development, integration, test, demonstration, and certification of a High Fidelity Sensor Level Stimulation and Common Processing System.

The Contractor shall work in a collaborative environment with a consortium of Navy, Navy Laboratories, Academia, and other industry partners to ensure continued success of the program. The Contractor shall identify his approach to be used to support the “Open Source Initiative” without compromising a third Party Developer’s intellectual property rights which also allows for the efficient integration of improvements with the Submarine Acoustic Systems.

2.0 REFERENCED DOCUMENTS

The following documents are to be used as guidance in the performance of the requirements identified herein.

2.1 GOVERNMENT DOCUMENTS

SUB-SONAR-SPEC-09

Revision B 01 May 2013

Specification for Submarine Sonar for Advanced Processing Build 2009 (and later)

NUWC TD 11788

08 January 2007

AN/BQQ-10 Sonar System Integration and Testing Process

NUWCNPT Ltr Ser 15/149 24 March 2014

Update to Acoustic Commercial-Off-The-Shelf Insertion Integration and Test Plan

NUWC TM14-003

Revision G 13 May 2014

Acceptance Test Plan for Submarine Sonar

MIL-STD-130N Identification Marking of U.S. Military Property w/ Change 1 16 November 2012

MIL-HDBK-251

19 January 1978

Reliability/Design Thermal Applications

MIL-STD-461F

10 December 2007

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-HDBK-470A

Note 2 31 May 2012

Designing and Developing Maintainable Products and Systems Volume I

MIL-HDBK-502A

08 March 2013

Product Support Analysis

MIL-STD-881C

03 October 2011

Work Breakdown Structures for Defense Materiel Items

MIL-STD-882E

11 May 2012

System Safety

MIL-STD 1472G

11 January 2012

Human Engineering

MIL-STD-3018

w/ Change 1 27 October 2011

Parts Management

MIL-S-901D

17 March 1989

Shock Tests, H. I. (High-Impact) Shipboard Machinery, Equipment, and Systems, Requirements For

MIL-STD-3034A

29 April 2014

Reliability-Centered Maintenance (RCM) Process

MIL-PRF-29612B

20 June 2011

Training Data Products

MIL-STD-31000A

26 February 2013

Technical Data Packages

SD-22

01 August 2012

Diminishing Manufacturing Sources and Material Shortages (DMS/MS) Guidebook

Provisioning, Allowance and Fitting Out Support (PAFOS) Manual

Provisioning Technical Documentation (PTD) Requirements for NAVSEA Government Furnished and Contractor Furnished Commodities (http://www.nclc.navsea.navy.mil/TechLog/PolicyProc.htm)

NAVSEA 0924-062-0010

Rev C

Submarine Safety (SUBSAFE) Requirements Manual

NAVSEA-ST00-AA-IDX-010-TEI

Rev 17

Test Equipment Index

MIL-HDBK-217F

thru Notice 2 28 February 1995

Reliability Prediction of Electronic Equipment

NDMS-100001-000

05 Oct 2009

Technical Manual Contract Requirement (TMCR), Interactive Electronic Technical Manual (IETM) for the A-RCI Program

NAVSEA ltr 5510, Ser/TSUB-0140 24 June 2005

Team Submarine Information Security Policy

DOD 5000.4-M-1

18 April 2007

Cost and Software Data Reporting (CSDR) Manual, Cost Analysis Improvement Group

2.2 NON-GOVERNMENT DOCUMENTS

ANSI/AIAA-R-100A

Recommended Practice for Parts Management

IPC/J-STD-001D

Requirements for Soldered Electrical and Electronic Assemblies

IEEE/EIA 12207.0/1/2

March 1998 and April 1998

Software Life Cycle Processes; Life Cycle Data; Implementation Considerations

ANSI/EIA-748-B

June 2007

Earned Value Management Systems

ANSI/EIA-632-1999 Processes for Engineering a System

ANSI/EIA-649-B

17 June 2011

National Consensus Standard for Configuration Management

ANSI/EIA-STD-0007

August 2007

Logistics Product Data, Version 1.0

GEIA-STD-0007

15 October 2008

Logistics Product Data

NAS411 thru Rev. 2 29 April 94

Hazardous Materials Management Program

3.0 REQUIREMENTS

The work required by this section 3.0 of the Statement of Work is applicable to all requirements under this contract.

This contract requires work with SEAWOLF and VIRGINIA Class submarines stealth performance data that falls under the protection of Alternative Compensatory Control Measures (ACCMs). Access to VIRGINIA data is only authorized with specific prior permission from PMS450. Access to SSN21 and SSN22 data is only authorized with specific prior permission from PMS392, while SSN23 requires specific prior permission from both PMS392 and PMS394. Additional handling requirements in accordance with NAVSEA INSTRUCTION S5510.18

“SECURITY POLICY FOR STEALTH PERFORMANCE DATA WITH ALTERNATIVE COMPENSATORY

CONTROL MEASURES (ACCMS)" apply. The data under this protection will not be stored or processed within Contractor's facility without additional PMS392, PMS394, and PMS450 approval and modifications to the DD254.

In addition to possessing SECRET security clearance, personnel accessing classified information in the performance of this contract need also possess ACCM.

3.1 INTEGRATED PROGRAM MANAGEMENT

The Contractor shall designate a Program Manager who shall have responsibility for all aspects of this contract and the authority to commit the Contractor to specific courses of action. The Contractor shall organize, coordinate, control and report the status [Exhibit Line Item Number (ELIN) A001, DI-MGMT-80227] of all contract activities related to this contract, and be responsible for those activities assigned to subcontractors, to ensure the delivery of all supplies and services specified in this contract. The Contractor shall establish, maintain, and use in the performance of this Contract, an integrated performance management system. An Earned Value Management System (EVMS) shall be used following the guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the Contractor shall utilize an Earned Value Management System (EVMS) for tracking and reporting costs segregated by tasks. The EVMS shall be linked to and supported by the Contractor’s management processes and systems to include the integrated master program report, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement.

3.1.1 Progress Reporting

The Contractor shall maintain technical and financial status and generate progress reports [ELIN A001].

The financial status shall include the Estimate at Completion (EAC), Actuals to Date (ATD), Estimate to Complete (ETC), amount funded and outlooks for when additional funding is required, as necessary, for tasks as identified in Technical Instructions.

Contractor shall conduct an Integrated Baseline Review (IBR) within six months of award to assess Contractor’s Performance Measurement Baseline (PMB). Contractor shall conduct an IBR for any major change to the contract, as determined by the PMS401 representative. As part of the EVM requirements for this contract, Contractor will also submit the Contract Funds Status Report (CFSR) quarterly.

[ELIN A003, DI-MGMT-81468]

3.1.2 Subcontract Management and Control

The Contractor shall identify and monitor subcontractor technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor’s own established subcontract management techniques.

3.1.3 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain the CWBS and CWBS dictionary using MIL-STD-881C for guidance. The CWBS provides the basis for further extension by the Contractor to lower levels during the performance of the Contract. The CWBS Index and Dictionary shall be prepared to WBS level 4 and include any lower level CWBS elements identified as being high risk, high value, or high technical interest. The Contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements specified in the Statement of Work and system specification and translate them into a structure representing the products and services that comprise the entire work effort under the Contract.

The Contractor's team or organizational entity responsible for the systems engineering of the system prepares the technical elements of the extended Contract WBS. The Contractor, if necessary, shall update the CWBS during the execution of the Contract. Changes to the CWBS or associated definitions, at any reporting level, require approval of the Government [ELIN A004, DI-MGMT-81334D].

3.1.4 Integrated Program Management Report (IPMR)

The Contractor shall apply Earned Value Management (EVM) principles and create and maintain an IPMR.

The Contractor shall report progress on all technical performance, cost, schedule, and data delivery requirements for engineering services and logistics for the A-RCI system and production of the A-RCI system. The Contractor shall provide access to all pertinent records, data and plans, as requested by the Government or their representatives.

Integrated Master Schedule (IMS) activities (such as the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the Contract, as well as the quantified risk in hours, days, or weeks of delay, and optimistic, pessimistic, and most likely duration for each IMS activity and event) shall be reported in the IPMR. [ELIN A005, DI-MGMT-81861]

3.1.5 Integrated Baseline Reviews

The Contractor shall engage jointly with the Government’s Program Manager in Integrated Baseline Reviews (IBR) to evaluate risks inherent in the Contractor’s planned performance measurement baseline established from the culmination of Technical Instructions in effect per year during execution of the contract. The initial IBR baseline shall be jointly determined 60 days after Technical Instruction (TI) issuance, subsequent baselines will be established as required. Each IBR shall verify that the Contractor is using a reliable performance measurement baseline, which includes the entire scope of work for the culmination of TIs that are in place during the year of execution consistent with Contract schedule requirements and has adequate resources assigned.

3.1.6 Contract Cost and Software Data Reporting (CSDR) for VIRGINIA Class New Construction

The Government intends to issue an order under this contract for VIRGINIA Class New Construction ship set requirements. The Contractor and subcontractors, as applicable, shall systematically collect and report actual contract cost and related data for the VIRGINIA Class New Construction requirements for the life of the contract in accordance with the Cost and Software Data Reporting (CSDR) Manual, DOD 5000.4-M-1.

3.1.6.1 The Contractor shall prepare a revision to Attachment 10, Contract Cost and Software Data Reporting (CSDR) Plan, DD Form 2794, including any follow on revisions for Government approval. The CSDR identifies the Program Work Breakdown Structure (PWBS). The approved Contract CSDR Plan will be incorporated into the contract.

3.1.6.2 The Contractor shall also prepare the Contract Work Breakdown Structure (CWBS) Index and Dictionary in accordance with MIL-STD-881C for Government approval. The CWBS Index and Dictionary shall be prepared to WBS level 4 and include any lower level CWBS elements designated on the CSDR Plan as being high risk, high value, or high technical interest. The CWBS elements shall be maintained throughout the life of the contract and incorporated into the CSDR Plan. The Contractor may further extend the WBS for its own reporting purposes. The Contractor shall not change the approved CWBS Index and Dictionary without written approval by the Government.

[ELIN A004]

3.1.6.3 In addition, the Contractor shall prepare the following cost documentation. All costs, at a minimum shall be reported to Level 3. Lower-level reporting shall only be required for those elements that are identified as being high-risk, high-value, or high-technical interest programs by the VIRGINIA Class Program DOD Cost Working Level Integrated Product Team or as warranted by the Contractor’s accounting system:

(Cost Data Summary Reports, DD Form 1921 [ELIN A006, DI-FNCL-81565C]; Functional Cost-Hour Reports, DD Form 1921-1 [ELIN A007, DI-FNCL-81566C]).

3.1.7 Program Risk Analysis

The Contractor shall perform a continuing analysis of program, technical, cost and schedule risks. The analysis shall identify the risks associated with each area, identify the impact of each risk on the overall program, and proposed approaches for reducing identified risks. Risk analysis status shall be reported in the Contractor’s Progress, Status and Management Report [ELIN A001] and presented during Program and Technical Reviews.

3.1.8 Program Reviews

The Contractor shall conduct program progress and status review meetings at regular intervals at times and places mutually agreed upon between the Contractor and PMS401. Such meetings shall not be held more frequently than once per month. PMS401 and/or such representatives as designated by PMS401 will attend the meetings. At each program review the Contractor should report the status of the following as directed:

a. cost/schedule performance, top level EVMS shall be provided to the COR from the CAM managers at each program review under separate cover so as to protect the contractors cost information;

b. design and technical issues;

c. hardware and computer software engineering;

d. risk analysis activities;

e. reliability and maintainability;

f. quality program;

g. test and evaluation activities;

h. production activities;

i. logistics development and support efforts;

j. safety program status;

k. configuration management activities;

l. GFP and GFI status;

m. efforts authorized under technical instructions.

n. manpower utilization projection/actual (3 month history, 9 month future);

o. data items delivery schedule; and

p. hazardous material management efforts.

q. information assurance.

The Contractor shall prepare agendas for Contractor-hosted meetings, program reviews, IPTs and all other meetings/reviews. The agendas shall be reviewed jointly between the Government and Contractor and distributed electronically via e-mail by the Contractor. Minutes of the meetings shall be recorded by the Contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and distributed electronically. [ELIN A008, DI-ADMIN-81249A], [ELIN

A009, DI-ADMIN-81250A]

3.1.9 Design Disclosure, Intellectual Property and Data Rights

The Contractor shall establish and maintain a process that will provide ‘early and often’ design disclosure directly to third party developers via electronic access to in-process design documentation and computer software.

The Contractor shall support an Open Source Initiative with other participants within the Shipboard Combat Systems Development community. The Contractor shall establish an Associate Contractor Agreement with each third party developer (roughly between 15 and 50) and coordinate disclosure and the delivery schedule directly with the developers. The exchange of information shall be structured so as to protect the Contractor's and third party developers’ proprietary rights in the information and allow the Contractor to plan when they will receive deliveries.

The Contractor shall furnish to the PCO a copy of the Associate Contractor Agreement and copies of all written communication between the Contractor and the third party developers that is pertinent to this contract. The Contractor shall discuss and attempt to resolve any problems between the Contractor and the third party developers and notify the PCO if required, in writing, of any problems including documentation of problem resolution.

The Contractor shall provide an update to Attachment 11, entitled “7017 List and Supplemental 7017 Restrictions List,” identifying all noncommercial or commercial Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) delivered with Specifically Negotiated License Rights (SNLR) or other non-standard rights. The Contractor shall also provide an update to Attachment 12, entitled "Background Inventions- -Identification and Licensing" (the BIIL List), identifying all inventions described in and covered by any patents or pending patent applications in which the Contractor (1) has any right, title, or interest; and (2) intends to include in any Items, Components, Processes (ICP) to be developed or delivered under the resulting contract, or that are described or disclosed in any Technical Data (TD), Computer Software (CS), or Computer Software Documentation (CSD) to be developed or delivered under the resulting contract. [ELIN A00A, DI-MISC-80508B] Such inventions are hereafter referred to as "background inventions."

The Contractor's failure to identify anything other than Government Purpose Rights or any background invention in the BIIL List, as set forth above, shall constitute a grant to the Government of a nonexclusive, nontransferable, irrevocable, worldwide, paid-up license to practice, and to have practiced for or on its behalf, such invention for Government purposes related to the affected Combat System(s).

3.1.10 Data Management

The Contractor shall maintain Contract Data Status for recording, planning, scheduling, and reporting the status of program data requirements including electronic mail transmittals; and maintain a list of all contractor and subcontractor data generated in support of this contract. Data management shall adhere to the Team Submarine Information Security Policy (NAVSEA ltr 5510, Ser/TSUB-0140) provided as Government Furnished Information

(GFI).

3.1.10.1 Digital Data Management.

The Contractor shall establish a collaborative Integrated Digital Environment among all participants in the contract. In accordance with the NAVSEA Security Guide, the Contractor shall be responsible for the digital generation, reception and electronic delivery of data. All data shall be developed, marked, managed, used, and delivered/exchanged electronically to the greatest extent practical. Controlled Unclassified Information (CUI) submitted by email shall be digitally signed and encrypted. The Government may request via TI that the Contractor deliver internal data developed or modified under this contract. If required, the Contractor shall establish SIPRNET communication capabilities (STU 3 or equivalent) for the transmission of sensitive and classified data and to provide support to the operating Fleet and its land based support activities.

3.1.10.2 Electronic ELIN Delivery.

The Contractor shall deliver all unclassified ELINs, by E-Mail or electronic media. Classified ELINs that require digital media delivery shall be delivered in electronic media. If hardcopy format is desired the government will provide separate direction. ELINs too large for delivery by E-Mail or electronic media (file size, drawings, data packages etc.) shall be delivered in hardcopy format in accordance with the applicable ELIN DD Form 1423.

3.1.11 Integrated Product Team (IPT)

The establishment of IPTs is a management technique that simultaneously integrates activities through the use of multi-disciplinary teams to optimize the design, manufacturing and supportability processes. The Contractor shall establish and/or participate in joint contractor/government IPTs to resolve particular problems and issues. IPTs are generally formed at the Program Manager level and may include members from Government, the Contractor, subcontractors and vendors. The Contractor shall develop IPT charters [ELIN A00A, DI-MISC-80508B] and present during program reviews.

The objective of the IPT concept is to assemble all stakeholders with a particular problem or issue who will expand the principal of concurrent engineering, utilizing a systematic approach to make team decisions based on timely input from the entire team, including customers and suppliers, and third party developers. The desired expectation is to move away from a pattern of hierarchical decision-making to a process where decisions are made across organizational structures by IPTs. These IPTs will integrate cost, schedule and performance data to provide a global perspective with detailed insight into the managerial and technical aspects impacting Government and industry.

The Contractor (including subcontractors and vendors as necessary) shall attend, present as necessary, and participate in IPT meetings. In addition, the Government may establish, and the Contractor shall participate in ad hoc IPTs, as the need arises. IPT meetings shall be held at either the Contractor’s facility or a Government specified facility.

To the extent specified in the established charter, the IPTs shall have responsibility for the following functions:

a. Monitoring and reporting of Subsystem status and progress for both the Government and the Contractor;

b. Joint identification, evaluation, management, and reporting of risk mitigation and cost reduction initiative efforts;

c. Identification, collection, analysis, and reporting of appropriate metrics for measurement of cost/schedule control, engineering and production progress;

d. Joint evaluation and management resolution of major issues associated with hardware and software engineering, production, integration, test, and I&C activities;

e. Verification that the Contractor’s ‘early and often’ design disclosure process is providing data that is current, complete and accurate to third party developers;

f. Joint evaluation and management of the ILS effort; and

g. Joint recommended approval of data items requiring approval under this contract.

3.1.12 Use of Contractor Facilities

The Contractor and its major subcontractors shall provide and maintain secure office space and related services for up to 30 technical representatives, authorized by the Government, on site at the Contractor’s facility beginning at contract award and continuing through the end of the contract. The Contractor and its major subcontractors shall have mutual agreements which allow for similar office space access within their respective facilities. The related services at a minimum are:

a. Telephone services;

b. FAX transmission and reception;

c. Office equipment (e.g., desks, file cabinets);

d. Internet Infrastructure Services; and

e. Reproduction services (copying equipment).

3.1.12.1 Government On-Site Activities.

The Contractor shall make available to the technical representatives authorized by the Government all program data (e.g. working documents, databases, tracking systems, test results), including electronic access to computer files, pertaining to the contractor and subcontractor activities in the performance of this contract.

3.1.13 Government Furnished Information (GFI)

The Contractor shall manage and control the GFI identified in Attachment 2 in accordance with the provisions of the contract. The Contractor shall thoroughly inspect GFI for deficiencies within ten (10) days of receipt and report deficiencies [ELIN A00B, DI-MGMT-80596].

3.1.14 Government-Furnished Property/Equipment/Material (GFP/E/M)

The Contractor shall manage GFP/E/M identified in Attachments 3 and 4 in accordance with the provisions of this contract. The Contractor shall report [ELIN A00C, DI-QCIC-80736] to the Government within ten (10) days of any GFP/E/M found damaged, malfunctioning, or otherwise unsuitable for use.

3.2 SYSTEM ENGINEERING

The Contractor shall provide engineering services to meet the requirements of the contract and achieve Submarine Acoustic Systems Performance. Any requested changes or deviations to the contract or System Performance shall be submitted for approval in accordance with paragraph 3.5.4, [ELIN A00D, DI-CMAN- 80640C]. Consideration to Open Architecture and open systems concepts shall be included in the contractor’s processes to perform quality software development tasks including configuration management, built-in software reliability and longevity, problem reporting and corrective actions, and its approach to support an “Open Source Initiative”. The Contractor shall provide the approach to be used specific to the task relating to the overall Software CSCI structure, functional flows, and interface requirements [ELIN A00E, DI-IPSC-81427A]. In design reviews, the Contractor shall describe how their approach supports Open Architecture goals while interfacing with the federated Subsystems simultaneously under development and disclose the approach to support the System’s collaborative development environment including the frequent and continuous design disclosure to Navy designated third-party developers throughout the development process.

3.2.1 Systems Engineering Management

The Contractor shall provide a System Engineering Management Plan (SEMP) for how development will progress with the incorporation of inputs from the various supporting working groups [ELIN A00F, DI-SESS- 81785]. The Contractor shall describe how the various technical inputs to the systems engineering effort will be integrated into a collaborative development environment. A description of each major technical review shall be included.

3.2.2 Technical Reviews

Technical reviews shall be held at the Contractor’s facility to discuss and evaluate design status. Design reviews will be conducted on a periodic basis as proposed in the Integrated Master Schedule to determine progress and resolve issues. The structure and intervals will be defined in the IMS or (Attachment 13). The Contractor shall demonstrate how completion of required accomplishments associated with the event or milestone will be achieved for these reviews.

a. System Requirements Review (SRR)/System Design Review (SDR). The Contractor shall present its interpretation/understanding of the System Performance Specification requirements.

b. System Functional Review (SFR)/Preliminary Design Review (PDR). The Contractor shall present its system, hardware and software designs to show compliance with the system functional and performance requirements contained in the NAVSEA Technical Instructions. The completion of the SFR shall result in the establishment of the system hardware and software functional (performance) baseline.

c. Software Specification Review (SSR). The Contractor shall present system performance elements defined for all CSCIs. The completion of the SSR shall result in the establishment of a system software performance Allocated Baseline.

d. Subsequent reviews including the Critical Design Review, which could take place in the form of Incremental Design Reviews (IDRs), are to be held in accordance with the Contractor’s software development process and will be agreed to by the Navy at the conclusion of the SSR.

e. A Test Readiness Review (TRR) shall be completed a minimum of two (2) weeks prior to each test via a meeting between the Joint Test Group (JTG) Chairman, or his designated representative, and the Contractor.

3.2.3 System Integration

The Contractor shall develop a System Integration Plan (SIP) [ELIN A00A, DI-MISC-80508B], identify and provide the necessary development facilities, and conduct system integration, in accordance with the SIP. The Contractor shall address all problems identified by the Government during interface testing. The Contractor shall support integration and testing of all applicable shipboard subsystems for a total Submarine Acoustic Systems subsystem. This interfacing activity will occur at the Submarine Acoustic Systems Contractor site. Interface testing and logistics integration events will typically occur annually.

3.2.4 System Engineering and Design Analyses

The Contractor shall develop System/Subsystem Design Descriptions (SSDDs) [ELIN A00G, DI-IPSC- 81432A] in accordance with ANSI/EIA-632. In addition, the requirements outlined in the following paragraphs shall be included in the SSDD.

3.2.4.1 Requirements Analysis.

The Contractor shall conduct detailed system engineering and design analyses of the proposed software and hardware system in accordance of the specifications included in individual Technical Instructions. Materials and components to be incorporated into the system or subsystems shall be specified including a listing of any hazardous materials or processes incorporated or used in the fabrication of the system or subsystems. The design analyses shall consist of detailed examinations of the design techniques and materials that the Contractor plans to use to meet the requirements of the specifications. The Contractor shall not require any critical manufacturing processes, special inspections/tools or calibrations in its design unless approved by the Government. The design analyses shall be specific on both the system and component levels. The Contractor shall develop Specification Requirement Verification Matrices (SRVMs) to ensure traceability between the test requirements and the Performance Specifications [ELIN A00H, DI-MISC-81283]. The Contractor shall develop engineering design review information packages [ELIN A00J, DI-SESS-81757A]. Materials and components to be incorporated in the system shall be specified. Stress levels and safety factors, as appropriate, shall be identified for all mechanical and electrical parts. In addition to the system hardware physical considerations, the design analyses shall evaluate the system concept in terms of operability, reliability, producibility, maintainability and supportability objectives using MIL-STD-1472G and MIL-HDBK-470A as guidance. The Contractor shall examine the design details and modify them, as necessary, to ensure that the system design will conform to established Navy precepts for minimum practical manning, personnel and training requirements.

3.2.4.2 Failure Modes, Effects and Analyses (FMEAs).

The Contractor shall perform FMEA. The FMEA shall be performed to the LRU level and shall include an analysis of mission impact due to loss of functionality. All potential hardware and software failure modes shall be postulated at the LRU level and the effects of all higher levels shall be determined. Results of FMEAs shall be documented in the Failure Modes and Effects Analysis (FMEA) Report [ELIN A00K, DI-SESS-80980A].

3.2.4.3 Reliability Modeling and Allocations.

The Contractor shall develop, maintain and update Reliability Models and Block Diagrams based on LRU, software, equipment and system functions [ELIN A00L, DI-SESS-80994A]. The Contractor shall use the models and block diagrams to allocate higher-level reliability requirements down to the equipment, LRU and software levels for use in the selection of NDI. Reliability block diagrams shall be keyed and traceable, including nomenclature, to functional block diagrams, schematics, and drawings, to provide the basis for mathematical representation of reliability. The reliability mathematical model shall be updated with hardware and software design changes as a result of relevant test changes in item configuration, mission parameters and operational constraints.

Modeling techniques shall provide basic/mission reliability for equipment and software; and mission reliability of the system. The models/allocations shall be executed using the NAVSEA TIGER software provided as GFI or a Government-approved substitute. All executable and data files shall be delivered to the Government. [ELIN A00A, DI-MISC-80508B]

3.2.4.4 Maintainability Analysis.

The Contractor shall develop, maintain and update Reliability Centered Maintenance (RCM) products and the reliability and maintainability predictions for the equipment and software using MIL-HDBK-217F as guidance.

The Contractor shall conduct reliability and maintainability analyses throughout design and development to support availability predictions. [ELIN A00M, DI-MNTY-80990], [ELIN A00N, DI-RELI-81496], [ELIN A00P, DI- RELI-81497], [ELIN A00Q, DI-ILSS-80111A] and ELIN [A00R, DI-MNTY-81601]. The Contractor shall use the 12 Phase RCM process in accordance with MIL-STD-3034A. The Contractor shall develop Planned Maintenance System (PMS) Documentation including Maintenance Index Pages/Maintenance Requirement Cards (MIP/MRC) in New PMS Editor (NPE) software format. MRCs shall be validated and verified on the equipment at the contractor’s facility.

3.2.5 Failure Reporting Analysis and Corrective Action System (FRACAS).

The Contractor shall analyze failure data, addressing: historical operating time and data; determination of the cause of each failure down to the LRU and component level that caused the failure; identify LRUs and components that have had more than one failure; planned corrective actions; and implementation and results of corrective actions, including resultant reliability [ELIN A00R]. The Contractor shall analyze the root cause for all pattern failures (more than one) and shall submit for Government approval a failed item analysis report (Failure Analysis and Corrective Action Report). If corrective actions are required, the Contractor shall include that data in the monthly Contractor’s management report [ELIN A001, DI-MGMT-80227] until the corrective action is completed. If deemed necessary by the government, the Government will examine at the contractor’s facility, the data from all failure and corrective action analyses.

Upon Government approval, if required, the Contractor shall be responsible for correcting deficiencies discovered during the reliability test and for incorporating engineering change orders into the production baseline accordingly. Throughout the Test, Analyze and Fix and FRACAS processes, the Contractor shall plot failure data on a Reliability Growth Curve to assess system reliability. The Contractor may recommend additional specific testing to assess unique system characteristics.

3.2.6 SOFTWARE ENGINEERING SERVICES

The Contractor shall provide software engineering services to meet the requirements of the contract and achieve Submarine Acoustic Systems Performance. The Contractor shall manage, develop, update, test and deliver computer software in accordance with the Software Development Plan (SDP). [ELIN A00E, DI-IPSC-81427A]

3.2.7 Software Design Requirements

The Contractor shall develop, update and maintain Software Requirements Specifications (SRS) [ELIN A00S, DI-IPSC-81433A] and Interface Requirements Specifications (IRS) as defined by NPES baseline.

3.2.7.1 Software Deliveries.

The Contractor shall generate build deliveries [ELIN A00T, DI-IPSC-81441A] for each build configuration for delivery to the Navy and to the appropriate subsystem contractors. The contractor shall conduct Delivery Readiness Reviews for each software build prior to software delivery [ELIN A00A].

3.2.7.2 Program Package.

The Contractor shall provide a Software Version Descriptions (SVDs) for each software build [ELIN

A00U, DI-IPSC-81442A]

3.2.8 Safety

The Contractor shall establish and maintain a System Safety Program to support efficient and effective achievement of overall system safety objectives using MIL-STD-882E as guidance The System Safety program shall be documented in the System Safety Program Plan [ELIN A00V DI-SAFT-81626].

3.2.9 Environmental Compliance

The Contractor shall ensure that work performed under the contract is performed in accordance with

National Aerospace Standard (NAS 411). The Contractor shall eliminate, or at least minimize to the highest possible extent:

Any element, compound, mixture, solution, or substance designated as hazardous under section 102 of

CERCLA.

Any hazardous substance designated under section 311(b)(2)(a) of the Clean Water Act (CWA), or any toxic pollutant listed under section 307(a) of the CWA. There are over 400 substances designated as either hazardous or toxic under the CWA.

Any hazardous waste having the characteristics identified or listed under section 3001 of the Resource Conservation and Recovery Act.

Any hazardous air pollutant listed under section 112 of the Clean Air Act, as amended. There are over 200 substances listed as hazardous air pollutants under the Clean Air Act (CAA).

Any imminently hazardous chemical substance or mixture which the EPA Administrator has "taken action under" section 7 of the Toxic Substances Control Act.

Hazardous waste is defined under the Resource Conservation and Recovery Act (RCRA) as a solid waste (or combination of solid wastes) which, because of its quantity, concentration, or physical, chemical, or infectious characteristics, may: (1) cause or contribute to an increase in mortality or an increase in serious irreversible, or incapacitating illness; or (2) pose a substantial present or potential hazard to human health or the environment when improperly treated, stored, transported, disposed of, or otherwise managed. In addition, under RCRA, EPA establishes four characteristics that will determine whether a substance is considered hazardous, including ignitability, corrosiveness, reactivity, and toxicity. Any solid waste that exhibits one or more of these characteristics is classified as a hazardous waste under RCRA and, in turn, as a hazardous substance under Superfund.

The terms "hazardous substance" and "pollutant or contaminant" do not include petroleum or natural gas.

EPA conducts emergency responses to incidents involving petroleum and non-petroleum oils separately from its responses to hazardous substance incidents. Throughout the Emergency Response Program, the term "hazardous substance" includes pollutants and contaminants.

Hazardous material that is required to be used in, supplied with, or required to support the system shall require approval from the program office. To facilitate approval the contractor shall document the analysis conducted to evaluate alternatives in a Health Hazard Analysis Report [ELIN A00W, DI-SAFT-80106B] and provide Material Safety Data Sheets (OSHA Form 174).

3.2.10 Problem Reporting System

The Contractor shall establish a single system for the identification, tracking, and resolution of all hardware, software and baseline documentation problems identified during system development, integration and testing. In addition, the Problem Report (PR) System shall be used to track test documentation problems and technical manual errors. Status on problems should be reported as required to the Joint Test Group (JTG) and Program Reviews/Delivery Readiness Reviews. Problem Trouble Report (PTR) Review Boards (PRB) shall be conducted as required by the Government for each configuration to assess urgency and priority.

3.2.11 Open Systems Architecture Approach

The Government intends to procure system(s) having an Open System Architecture and corresponding components. The Contractor shall provide an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards that concentrate on re-use of software, hardware, interfaces between sensors, platforms and ASW systems.

In satisfying the Government’s requirements, the following system architecture approach characteristics shall be utilized:

a. Open Architecture - The Contractor shall develop and maintain an architecture that incorporates appropriate considerations for reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b. Modular, Open Design – The Contractor shall develop an architecture that is layered and modular and uses COTS/NDI hardware, operating systems, and middleware that utilize non-proprietary or non-vendor-unique, key Application Programming Interfaces (APIs). The Contractor’s design approach shall be applied to all subsystems and components. The Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated development environment throughout the term of the contract.

c. Modular Open Systems Approach (MOSA) –The Contractor’s design approach shall produce a system that consists of hierarchical collections of software and hardware configuration items (components). These components shall be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach shall emphasize the selection of components that are available commercially or within the DOD, to avoid the need to redevelop products that already exist and that can be re-used.

As part of technical and design reviews, the Contractor shall, at a minimum:

describe how the proposed system architecture meets the modular, open design goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

describe its rationale for the modularization choices made to generate the design.

provide rationale that explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

provide rationale for maintaining continued access to cutting edge technologies and products from multiple suppliers…