Attachment_1_SOW.pdf

N00253-18-R-0002, Attachment (1)

A-1

Attachment 1

STATEMENT OF WORK

FOR

PROGRAM EXECUTIVE OFFICE SUBMARINE

TECHNOLOGY INSERTION HARDWARE (TI-20 / TI-22)

19 December 2017

A-2

Table of Contents

1 SCOPE

1.1 PURPOSE

1.2 BACKGROUND

1.3 SUMMARY

2 APPLICABLE DOCUMENTS

2.1 GOVERNMENT SPECIFICATIONS, STANDARDS, & HANDBOOKS

2.2 INDUSTRY BASED STANDARDS DOCUMENTS

3 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 COLLABORATIVE DEVELOPMENT ENVIRONMENT

3.1.1.1 Integrated Data Environment

3.2 NON-RECURRING ENGINEERING (NRE)

3.2.1 INTEGRATED PRODUCT TEAM

3.2.2 ADVANCED PRODUCTION UNITS

3.2.3 ENGINEERING DEVELOPMENT MODELS

3.2.4 INSTALLATION AIDS

3.2.5 TWO DIMENSIONAL MOCKUPS

3.2.6 HARDWARE ENGINEERING SERVICES

3.2.7 SYSTEM ENGINEERING

3.2.7.1 Systems Engineering Management

3.2.7.2 Requirements Analysis

3.2.7.3 Analysis of Alternatives

3.2.7.4 System Engineering and Design Analyses

3.2.7.5 Systems Engineering Reviews and Audits

3.2.7.5.1 System Requirements Review/System Design Review

3.2.7.5.2 System Functional Review/Preliminary Design Reviews

3.2.7.5.3 Production Readiness Review

3.2.7.5.4 Critical Design Review

3.2.7.6 Open Systems Architecture Approach

A-3

3.2.7.7 Human Factors Engineering

3.2.8 DESIGN DISCLOSURE, INTELLECTUAL PROPERTY AND DATA RIGHTS

3.2.9 TECHNICAL DATA PACKAGE

3.2.9.1 Three Dimensional (3D) Computer Aided Design (CAD) Models

3.2.10 TEST AND EVALUATION

3.2.10.1 Test and Evaluation Program Plan

3.2.10.2 Test Requirements

3.2.10.3 Test Events

3.2.10.3.1 Qualification Test

3.2.10.3.2 Factory Acceptance Testing

3.2.10.3.3 System Confidence Test

3.2.11 TEST SOFTWARE ENGINEERING

3.2.11.1 Diagnostic Software

3.2.11.2 Operating Environment / FAT Software

3.2.11.3 Commercial-Off-The-Shelf-Software

3.2.11.4 Software Version Descriptions

3.2.11.5 Non-Developmental Items (NDI) Licenses

3.2.11.6 Test Software Problem Reports and Software Patches

3.3 PRODUCTION, SURGE, AND SPARES

3.3.1 KITS

3.3.2 ENCLOSURES

3.3.3 UNITS

3.3.4 SHIP SETS

3.3.5 SPARES

3.3.6 BUILD TO PRINT

3.3.7 MULTI-CLASS STATIC AUTOMATIC BUS TRANSFER (MC-SABT)

3.4 ENGINEERING AND TECHNICAL SUPPORT SERVICES

3.4.1 INTEGRATED PRODUCT SUPPORT SERVICES

3.4.1.1 Provisioning Technical Data

3.4.1.2 Failure Reporting Analysis and Corrective Action System

3.4.1.3 ILS Reviews

3.4.1.3.1 ILS Working Group Meetings

A-4

3.4.1.3.2 ILS Management Team Meetings

3.4.1.4 Parts Management Program

3.4.1.5 Supporting Technical Data, Manual and Licenses

3.4.1.6 Interactive Electronic Technical Manuals (IETM)

3.4.1.7 Support and Test Equipment (S&TE)

3.4.1.8 Supply Support Analysis

3.4.1.9 Obsolescence & Diminishing Manufacturing Sources & Material Shortages Management

3.4.1.9.1 Bill of Materials

3.4.1.9.2 Quarterly DMSMS Reports

3.4.1.10 Packaging, Handling, Storage & Transportation

3.4.1.11 Item Unique Identification Requirements

3.4.1.12 Radio Frequency Identification

3.4.1.13 Nomenclature, Serialization, Marking and Identification Plates

3.4.2 CONFIGURATION MANAGEMENT

3.4.2.1 Configuration Identification

3.4.2.2 Configuration Baselines

3.4.2.3 Configuration Control Board

3.4.2.4 Engineering Change Proposals

3.4.2.5 Specification Change Notice

3.4.2.6 Design Change Notice

3.4.2.7 Advanced Change Study Notice

3.4.2.8 Engineering Change Instruction

3.4.2.9 Correction of Deficiencies

3.4.2.10 Request for Deviation

3.4.2.11 Configuration Status Accounting

3.4.2.12 Beta Test Samples

3.4.2.13 Engineering Release Process

3.4.3 FIELD ENGINEERING

3.4.3.1 Installation and Checkout

3.4.3.2 Early Install Items

3.5 PROGRAM MANAGEMENT

3.5.1 PROGRESS, STATUS AND MANAGEMENT REPORT

A-5

3.5.2 CONTRACT LABOR RATE PERFORMANCE REPORT

3.5.3 CONTRACT WORK BREAKDOWN STRUCTURE

3.5.4 INTEGRATED MASTER SCHEDULE

3.5.5 SUBCONTRACT MANAGEMENT AND CONTROL

3.5.6 REVIEWS AND MEETINGS

3.5.6.1 Meeting Minutes

3.5.6.2 Remote Meeting Participation

3.5.6.3 Post Award Conference

3.5.6.4 Quarterly Program Reviews

3.5.6.4.1 QPR Hosting

3.5.6.4.2 QPR Documentation

3.5.7 PROGRAM MILESTONES REVIEWS

3.5.8 RISK ASSESSMENT AND MANAGEMENT

3.5.9 GOVERNMENT-FURNISHED INFORMATION/PROPERTY/EQUIPMENT/MATERIAL

3.5.10 DATA MANAGEMENT

3.5.10.1 Electronic Contract Data Requirements List Delivery

3.5.11 GOVERNMENT ON-SITE ACTIVITIES

3.5.12 FORMAL PROPOSALS

3.5.13 TASK BOOK PROPOSALS

3.5.14 ROUGH ORDER OF MAGNITUDE

3.5.15 SAFETY

3.5.15.1 System Safety Program Plan

3.5.15.2 Safety Assessment Reports (SAR)

3.5.15.3 Inputs for System Safety Working Groups (SSWGS)

3.5.16 ENVIRONMENTAL COMPLIANCE

3.5.17 QUALITY ASSURANCE

3.5.17.1 Problem Reporting System

3.5.17.2 Manufacturing Process Control

3.5.18 SECURITY

3.6 TRAVEL AND SUBSISTENCE

3.7 CONTRACT DATA REQUIREMENTS LIST ITEMS

A-6

4 APPENDIX A: ACRONYM LIST

1 SCOPE

1.1 PURPOSE

This Statement of Work (SOW) defines the efforts required for hardware deliveries (including material procurement or fabrication, and integration of Government-Furnished Material (GFM)/Government-Furnished Property (GFP), as applicable), engineering, program management, test software development, logistics and supportability engineering, configuration management, hardware test, evaluation, installation support (e.g. field engineering), and support of displays, processors, network systems, and other equipment associated with the Program Executive Office Submarine Technology Insertion Hardware (hereinafter referred to as TIH (20/22)). Sustainment support for legacy TIH is also included in the scope of this contract.

The Contractor shall design, develop, test, qualify, produce, deliver and support TIH (20/22) hardware. The term “hardware” refers to Advance Production Units (APU), Engineering Development Models (EDM), Lowest Replaceable Units (LRU), Installation and Checkout (INCO) kits, Onboard Replacement Parts (OBRP), Maintenance Assistance Modules (MAMS), cabling, configuration and upgrade kits, commercial-off-the-shelf (COTS) and Non- Developmental Items (NDI) parts, spares, units, and all other deliverable hardware/test software/firmware contained within this SOW. Tactical software development is outside the scope of this effort. Software/scripts developed under this SOW are for the purposes of test/demonstration of the TIH (20/22) equipment itself. Effort may include upgrades from existing Technology Insertion level configurations to the target configuration (e.g. TI-12 to TI-20 or TI-14 to TI-22). The technology insertion goals for TIH (20/22) include improvements to system functions involved in the receipt, assimilation, processing, evaluation and display of data, and the migration of Submarine Warfare Federated Tactical System (SWFTS) architecture and subsystem procurements into a fully virtualized configuration.

In general, virtualization means to create a virtual version of a device or resource, such as a server, storage device, network or even an operating system where the framework divides the resource into one or more execution environments. Specific to the SWFTS System of Systems (SoS), virtualization will provide a consolidated environment of hardware and software providing shared computing resources for SWFTS subsystems. Virtualization benefits SWFTS with reduced IT footprints aboard ship, improved cybersecurity posture, deployment flexibility, and rapid technology insertion with increased scalability. Virtualization will require the supporting of fielded systems while maintaining optimal integrated system performance, adherence to improved security measures, footprint reduction and capacity increases; and maintenance reduction and test simplification by the system users.

This SOW also defines the efforts required for equipment, parts, engineering services, and management oversight to support Joint Program Offices (JPOs) and Foreign Military Sales (FMS) customers.

Contractor personnel will require access to restricted data. The security clearances required are outlined in the DD254, Contract Security Classification Specification (Attachment 2).

A-7

The anticipated configuration changes (from/to) per class for TIH (20/22) is provided in Attachment 10, Worksheet 10G – Shipset Stepladder Pricing Table.

1.2 BACKGROUND

TIH (20/22) is the U.S. Navy’s latest generation of a continuously evolving family of display, processor and network systems that provide computer processing and memory, data storage and extraction, and Input/Output interfaces to support specific software applications of Navy Combat Control and Sonar Systems. TIH (20/22) is designed to support the Program Management and Program Executive Office Submarine implementation of Open Architecture for Navy Submarine systems. TIH (20/22) will maximize flexibility and modularity by procuring a processing system designed around commercially available hardware and software, which will conform to Open Architecture Computing Environment Technologies and Standards. It is the Government’s intent to adopt best commercial practices in completing system development and acquisition objectives.

Outside of changes demanded by Diminishing Manufacturing Sources/Material Shortages (DMSMS) issues, the Government's intent is that the servers change every TI, the switches change every other TI, and the displays change every three (3) TIs.

The purpose of the TIH (20/22) Combat Control and Sonar System contract is to provide display, workstation, processor, and network systems functionality for Mission Critical/Essential Systems onboard submarine platforms. Each TIH (20/22) “suite” consists of display and processor components arranged in specific system configurations to satisfy specific workstations, processors, file servers, or other network requirements. The Navy will be procuring these systems incrementally, and will require engineering and technical services for fielded equipment delivered under this contract. Life cycle support and engineering/technical services will also be required to ensure adequate supportability of TI-20 and TI-22 fielded units.

1.3 SUMMARY

The work shall be performed as specified in the contract. The following tasks are representative of the requirements; it is not an all-inclusive list.

• Provide data required by the Contract Data Requirements Lists (CDRLs) identified in this SOW. (Contract line item number (CLIN) 0017)

• Provide non-recurring engineering services to include the design, development, and test of equipment, configurations, and enclosures for U.S. Navy TIH (20/22) platforms, FMS customers, and the AN/BYG-1 JPO for the Royal Australian Navy (RAN) in support of COLLINS Class submarines. Include all base-lined engineering documentation and drawings, source data files, product lists, firmware and test software, and Integrated Logistic Support (ILS) products. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Provide fabrication, assembly, test, and delivery of equipment, configurations, and enclosures for U.S. Navy TIH (20/22) platforms, FMS customers, and the AN/BYG-1 JPO for the RAN in support of COLLINS Class submarines. (CLIN 0008 (U.S. Navy), CLIN 0016 (FMS), and options if exercised)

A-8

• Deliver spares/repair parts and technology insertion/refresh kits. (CLIN 0008 (U.S.

Navy), CLIN 0016 (FMS), and options if exercised)

• Develop factory acceptance tests, evaluation plans, procedures, and operating environment products (where applicable) for equipment under this contract. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Participate in the design and integration efforts to include technology insertion and refresh planning and validation. Support design and development, including participation in Integrated Product Team (IPT), modernization planning, and various reviews and working group meetings. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Provide reliability engineering and failure analysis. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Develop and update Configuration Management (CM) products for design, production, and post-production support. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Develop and deliver ILS products to support development, production, and installation for delivered items. Deliver ILS product source data to the Government (i.e. Interactive Electronic Technical Manuals (IETM), Allowance Parts List (APL), and Computer Based Training. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Support in-service engineering and field service tasking, such as installation, field integration support, repair, validation/verification, and refurbishment efforts. (CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised)

• Procure material in support of in-service engineering and field service tasking efforts.

(CLINs 0006 (U.S. Navy), 0014 (FMS), and options if exercised)

• Provide commercial component obsolescence management including vendor monitoring, replacement component qualification, testing, and ILS updates. (CLINs 0001-0005 (U.S.

Navy), 0009-0013 (FMS), and options if exercised)

• Provide non-production material necessary to support design and development, such as engineering design models. (CLINs 0006 (U.S. Navy), 0014 (FMS), and options if exercised)

• Travel will be necessary in support of the requirements herein. (CLINs 0007 (U.S.

Navy), 0015 (FMS), and options if exercised.

2 APPLICABLE DOCUMENTS

2.1 GOVERNMENT SPECIFICATIONS, STANDARDS, & HANDBOOKS

The following documents form a part of this SOW and are incorporated by reference.

A-9

Document Number Title Date

(U) MIL-HDBK-61A Configuration Management Guidance 07 Feb 2001

(U) MIL-HDBK-217F(2) Reliability Prediction of Electronic Equipment 28 Feb 1995

(U) MIL-HDBK-251 Reliability/Design Thermal Applications 19 Jan 1978

(U) MIL-HDBK-263B Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices) (Metric)

31 Jul 1994

(U) MIL-HDBK-454 B

Notice I

General Guidelines for Electronic Equipment (http://quicksearch.dla.mil/)

12 Dec 2012

(U) MIL-HDBK-470A

Notice 2

Designing and Developing Maintainable Products and Systems Volume I

31 May 2012

(U) MIL-HDBK-502A Product Support Analysis 08 Mar 2013

(U) MIL-HDBK-2155 Failure, Reporting, Analysis and Corrective Action Taken

(http://quicksearch.dla.mil/) 10 Sept 2014

(U) MIL-STD-108E (1)

through Notice 2

Definitions of and Basic Requirements for Enclosures for Electric and Electronic Equipment

8 Aug 1990

(U) MIL-STD-129R Military Marking for Shipment and Storage (http://quicksearch.dla.mil/)

18 Feb 2014

(U) MIL-STD-130N(1) Identification Marking of U.S. Military Property 16 Nov 2012

(U) MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment (Type I –

Environmental and Type II – Internally Excited) 02 Nov 2005

(U) MIL-STD-196F Joint Electronics Type Designation System 11 Sep 2013

(U) MIL-STD-461G Requirements for the Control of Electromagnetic

Interference Characteristics of Subsystems and Equipment 11 Dec 2015

(U) MIL-STD-464C Electromagnetic Environmental Effects Requirements for Systems

01 Dec 2010

(U) MIL-STD-740-2 Structure-borne Vibratory Acceleration Measurements and Acceptance Criteria of Shipboard Equipment

30 Dec 1986

(U) MIL-STD-810G (1) Environmental Engineering Considerations and Laboratory Tests

15 Apr 2014

(U) MIL-STD-881C Work Breakdown Structure for Defense Materiel Items 03 Oct 2011

(U) MIL-STD-882E System Safety 11 May 2012

(U) MIL-STD-1310H Department of Defense Standard Practice for Shipboard

Bonding, Grounding, and Other Techniques for Electromagnetic Compatibility and Safety

12 Aug 2014

(U) MIL-STD-1399-300B Electric Power, Alternating Current 24 Apr 2008

(U) MIL-STD-1399-390 Interface Standard For Shipboard Systems Section 390

Electric Power, Direct Current, (Other Than Ship's Battery) For Submarines (Metric)

02 Oct 1987

(U) MIL-STD-1399-406B

Notice 2

Interface Standard For Shipboard Systems Section 406 Digital Computer Grounding (Metric)

11 Dec 2000

(U) MIL-STD-1399-502A Interface Standard For Shipboard Systems Section 502 Electronic Systems Parameters

01 Feb 1995

(U) DoD-STD-1399-532

(CN1)

Interface Standard For Shipboard Systems Section 532 Cooling Water For Support Of Electronic Equipment (Metric)

28 Feb 1990

(U) MIL-STD 1472G Human Engineering 11 Jan 2012

(U) MIL-STD-1474E Noise Limits 15 Apr 2015

A-10

Document Number Title Date

(U) MIL-STD-1686C Electrostatic Discharge Control Program for Protection of

Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

25 Oct 1995

(U) MIL-STD-2073-1E(1) Standard Practice for Military Packaging 07 Jan 2011

(U) MIL-STD-3018(2) Parts Management 02 Jun 2015

(U) MIL-STD-3034A Reliability-Centered Maintenance (RCM) Process 29 Apr 2014

(U) MIL-STD-31000A Technical Data Packages 26 Feb 2013

(U) MIL-DTL-901E Shock Tests, H. I. (High-Impact) Shipboard Machinery, Equipment, and Systems, Requirements For 20 June 2017

(U) MIL-PRF-29612B (3) Training Data Products 31 Mar 2016

(U) DoD 5220.22M National Industrial Security Program Operating Manual

(NISPOM) (See http://quicksearch.dla.mil/) 18 May 2016

(U) DoDI 8320.04 Item Unique Identification (IUID) Standards for Tangible Personal Property

03 Sep 2015

(U) DoDD 8330.01 Interoperability of Information Technology (IT) Including National Security Systems (NSS) http://www.esd.whs.mil/Portals/54/Documents/DD/iss uances/dodi/833001p.pdf

21 May 2014

OPNAV-M 55.10.1 Office of the Chief of Naval Operations Regulations Manual (https://doni.documentservices.dla.mil/SECNAV%20 Manuals1/5510.1.pdf)

28 Aug 2017

GIDEP Operations Manual, (http://www.gidep.org/about/opmanual/opmanual.htm)

Online

(U) = Unclassified (C) = Classified http://quicksearch.dla.mil/ http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/833001p.pdf http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/833001p.pdf https://doni.documentservices.dla.mil/SECNAV%20Manuals1/5510.1.pdf https://doni.documentservices.dla.mil/SECNAV%20Manuals1/5510.1.pdf

A-11

2.2 INDUSTRY BASED STANDARDS DOCUMENTS

Document Number Title Date

(U) ANSI/AIAA R-100A-

2001e

Recommended Practice for Parts Management 2001

(U) IEEE 12207 Software Life Cycle Processes Jul 2017

(U) ANSI/EIA-632 Processes for Engineering a System Sep 2003

(U) ANSI/ASME Y14.100 Engineering Drawing Practices

(https://www.asme.org/shop) Nov 2017

(U) ANSI/ASQC Q9001 Quality Management Systems – Requirements Oct 2015 ASME Y14.2 Line Conventions and Lettering

(https://www.asme.org/shop)

ASME Y14.24 Types and Applications of Engineering Drawings (https://www.asme.org/shop)

ASTM-D3951-15 Standard Practice for Commercial Packaging (http://www.astm.org/Standard/standards-and-publications.html)

Dec 2015

ASTM-D4169-16 Standard Practice for Performance Testing of Shipping Containers and Systems (http://www.astm.org/Standard/standards-and-publications.html)

Apr 2016

GEIA-HB-0005-2 Technical Guidelines for Aerospace and High Performance Electronic Systems Containing Lead-Free Solder and Finishes (https://global.ihs.com/)

Nov 2007

GEIA-STD-0005-1, Rev. A Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-free Solder (https://global.ihs.com/)

Mar 2012

IPC-2220 series 2221B: Generic Standard on Printed Board Design 2222A: Sectional Design Standard for Rigid Organic Printed Boards 2223D: Sectional Design Standard for Flexible Printed Boards 2224: Sectional Standard of Design of PWBs for PC Cards 2225: Sectional Design Standard for Organic Multichip Modules (MCM-L) and MCM-L Assemblies 2226A: Sectional Design Standard for High Density Interconnect (HDI) Boards (https://ewb.ihs.com/)

2221B:

Nov 2012

2222A:

Dec 2010

2223D:

20 Sep2016

2224:

Jan 1998

2225: May 1998

2226A: Oct 2017

IPC-4101E Specification for Base Materials for Rigid and Multilayer Printed Boards (http://shop.ipc.org/)

Mar 2017

IPC-6010 series 6011: Generic Performance Specification for Printed Boards

6011: Jul 1996

A-12

6012D: Qualification and Performance Specification for Rigid Printed Boards 6013D: Qualification and Performance Specification for Flexible Printed Boards 6015: Qualification & Performance Specification for Organic Multichip Module (MCM-L) Mounting & Interconnecting Structures 6017: Qualification and Performance Specification for Printed Boards Containing Embedded Passive Devices 6018C: Qualification and Performance Specification for High Frequency (Microwave) Printed Boards (http://shop.ipc.org/)

6012D:

Sep 2015

6013D:

Aug 2017

6015:

Feb 1998

6017:

Mar 2009

6018C:

Aug 2016 IPC-A-600J Acceptability of Printed Boards

(http://shop.ipc.org/) Jun 2016

IPC-A-610G Acceptability of Electronic Assemblies (http://shop.ipc.org/)

Oct 2017

IPC-CC-830B Qualification and Performance of Electrical Insulating Compound for Printed Wiring Assemblies (http://shop.ipc.org/)

Oct 2008 Rev B Amd 1

IPC J-STD-001G Requirements for Soldered Electrical and Electronic Assemblies (http://shop.ipc.org/)

Oct 2017

IPC-MI-660 Incoming Inspection of Raw Materials Manual (https://ewb.ihs.com/)

Feb 1984

IPC-QL-653A Certification of Facilities that Inspect/Test Printed Boards, Components and Materials (http://shop.ipc.org/)

Nov 1997 Rev A

IPC-TM-650 Test Methods Manual (https://ewb.ihs.com/) Jan 2007 IPC/WHMA-A-620C Requirements and Acceptance for Cable and

Wire Harness Assemblies (http://shop.ipc.org/) Jan 2017

SAE/EIA-649-1 Configuration Management Requirements for Defense Contracts (http://store.sae.org/)

Nov 2014

SAE/EIA-748C Earned Value Management Systems (http://store.sae.org/)

Mar 2013 Rev C

SD-22 Diminishing Manufacturing Sources and Material Shortages

Jan 2016

TechAmerica STD-0016 Standard for Preparing a DMSMS Management Plan

Aug 2011

(U) = Unclassified (C) = Classified

A-13

3 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 COLLABORATIVE DEVELOPMENT ENVIRONMENT

To ensure continued success of the program, the Contractor will be required to work in a collaborative environment with a consortium of Government and industry partners including but not limited to the U.S. Navy; Navy Laboratories; academia; RAN and applicable FMS cases.

3.1.1.1 Integrated Data Environment

The Contractor shall utilize an integrated (electronic) data environment for electronic exchange of contract-related data and data products. The data environment may be Government provided, Contractor provided, or a combination of both. For segments of the data environment that are Government provided, Contractors shall abide by all access control regulations and policies. For segments that are Contractor provided, the Contractor shall provide the Government (and Government support Contractors) electronic access to that segment of the integrated development environment throughout the term of the contract.

The Contractor shall be responsible for the digital generation, receipt, and electronic delivery of data. All data shall be developed, managed, used, and delivered/exchanged electronically to the greatest extent practical. Data shall be stored and disseminated in a non-proprietary format, compatible with Microsoft Office 2010. Data archives may be required throughout and at the end of the contract term.

The Government may require the Contractor to deliver internal data developed or modified under this contract.

Controlled Unclassified Information (CUI) such as For Official Use Only, and other distribution statement controlled documents, are not authorized for public release and cannot be placed on a publicly accessible web site or web server. All data shall be handled in accordance with the DD254, Contract Security Classification Specification (Attachment 2). All emails containing such information or attachments must be digitally signed and encrypted both within Navy networks and if being transmitted outside a Navy network to an approved contractor email address. Transmission of CUI to personal email accounts including but not limited to: AOL, Yahoo, Hotmail, Gmail, etc. is strictly prohibited.

3.2 NON-RECURRING ENGINEERING (NRE)

CLINs 0001-0005 (U.S. Navy), 0009-0013 (FMS), and options if exercised.

This section of the SOW identifies the requirements for design, development, test, reverse engineering, and technology insertion/refreshment, for BYG-1, ARCI, and EW systems.

3.2.1 INTEGRATED PRODUCT TEAM

As outlined in the SWFTS Technology Insertion (TI) Process, the IPT Working Groups (WGs) are managed at both the SWFTS SoS and Subsystem levels. The IPT WGs are coordinated through a multi-level IPT process. The SoS level TI IPT provides the cross-subsystem

A-14 coordination between the Combat, Acoustic, and Imaging Subgroups and the various Technology Working Groups.

The Contractor shall participate in both membership and attendance at various IPT WGs such as System Architecture Working Group (SAWG), Modernization Installation Working Group (MIWG), TI Technology Working Group, and the End of Life (EOL) Working Group meetings, as determined by the respective Working Group Chairs.

The Contractor shall participate in joint IPTs that are required to execute the contract. The Contractor shall assist the Government in developing IPT charters. These IPTs will integrate schedule and performance data with detailed insight into the managerial and technical aspects impacting Government and industry. The Contractor shall provide representatives to each IPT with the appropriate level of expertise and degree of authority and responsibility to make decisions on behalf of the Contractor and in direct support of the program. As part of the IPTs, the Contractor shall:

a. Monitor and report subsystem status and progress;

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

c. Identify, collect, analyze, and report appropriate metrics for measurement of cost/schedule control, engineering and production progress;

d. Provide joint evaluation and management resolution of major issues (including obsolescence) associated with hardware and software engineering, production, integration, test, and shipboard Installation/Checkout (I&C) activities;

e. Verify the Contractor’s design disclosure process is providing data to third party developers that are current, complete and accurate.

f. Provide joint evaluation and management of the ILS effort; and

g. Provide additional functions as determined by the specific IPT charter.

3.2.2 ADVANCED PRODUCTION UNITS

The Contractor shall design, build, operationally test, configure, and deliver APUs to support the necessary upgrade efforts required to transition from an existing Technology Insertion level to the target configuration. An APU is any TIH (20/22) component, unit, item, article, kit, enclosure, or shipset that has not yet been approved by the Government for production under this contract. An APU may be required for each TI configuration specific to each platform (LOS ANGELES, SEAWOLF, VIRGINIA, OHIO, and COLUMBIA class submarines). APUs will be used to verify multiple aspects of the design, including mechanical mounting, cable design, cable lengths and routing, power system operation, interfaces, and operational performance. An APU enhances the development process by identifying design and quality problems prior to entering full rate production. The preferred method is to complete all developmental testing and operational testing (DT&OT) prior to the design being transitioned to manufacturing. However to support customer installation schedules, DT&OT may, at the Government’s discretion, occur simultaneous to production, during this development. Upgrade kits shall be developed to address any DT&OT findings and integrated into production units.

A-15

3.2.3 ENGINEERING DEVELOPMENT MODELS

The Contractor shall build EDMs to support development and testing as required for each platform. An EDM may be required for each TI configuration specific to each platform (LOS ANGELES, SEAWOLF, VIRGINIA, OHIO, and COLUMBIA class submarines). Units requiring EDMs include but are not limited to the Decoupled Display Workstation, Horizontal Decision Workstation, Advanced Auxiliary Equipment Console, Enhanced Control Display Work Station, Isolated Electronic Equipment Enclosure Multi-Function Server, Command Workstation, Advanced Tactical Console, Advanced Tactical Supervisor Panel, Advanced Auxiliary Equipment Console, Command Workstation and the Submarine Expanded Common Display. To mitigate risk to submarine installation schedules, and similar to the use of APUs, EDMs will be used to verify multiple aspects of the design, including mechanical mounting, cable design, cable lengths and routing, power system operation, interfaces, and operational performance. However, in order to differentiate between an APU and EDM, it important to note that APUs do not undergo Environmental Qualification Testing (EQT). Because EDMs undergo EQT to evaluate environmental performance, EDMs are not approved for use in fielded systems or units. EDMs accelerate development by allowing design and quality problems to be identified and corrected prior to discovering issues in the Fleet. The preferred method is to complete all EQT prior to the design being transitioned to manufacturing. However to support customer installation schedules, EQT and production may, at the Government’s discretion, occur simultaneously in this development. Upgrade kits shall be developed to address any EQT findings and integrated into production units.

3.2.4 INSTALLATION AIDS

As necessary, the Contractor shall develop, manufacture, deliver, update and maintain installation aids (drawer lifts / fitting jigs) necessary to safely and efficiently install the equipment aboard the submarine.

If required by the TIH (20/22) equipment/kit design, the Contractor shall deliver initial installation aids consisting of special handling devices and drawer lifting devices as required.

The Contractor shall make prudent efforts to optimize the balance between amount/type of specialized installation aids and the safety and efficiency of the installation process. Special handling devices and drawer lifting devices, if required, shall be delivered with the Two Dimensional (2D)-Mockups (CDRL B001 - Technical Data Package).

3.2.5 TWO DIMENSIONAL MOCKUPS

The Contractor shall develop, manufacture, deliver, update and maintain 2D mockups as part of the installation aids.

If required by the TIH (20/22) equipment/kit design, the Contractor shall deliver a 2D Mockup (CDRL B001 - Technical Data Package). Each mockup shall include the following features and be built so that it can be used to locate and drill/tap unit mounting holes and attach cables and water fittings:

a. Unit base: width and depth at base, with all mounting holes;

b. Other than base mounting, any other attachments required to install the unit;

A-16

c. Unit rear (to full height) and connector panels with all jacks, using dummy receptacles/actual connectors. All jacks shall be labeled with associated jack numbers; and,

d. Unit water fittings with input and output connected inside the mockups with hose/fitting which has been tested to the appropriate psig (if water cooled).

3.2.6 HARDWARE ENGINEERING SERVICES

The Contractor shall develop, update and maintain a hardware functional, performance and interface requirements baseline and generate program-unique specifications for the TIH (20/22).

(CDRL A019 - Program-Unique Specification Documents)

The Contractor shall develop a hardware design consisting of COTS/NDI Information Technology components and peripherals to fulfill the hardware functional performance and suitability requirements, which will include a move to a fully virtualized environment starting with the TI-20 design.

The Contractor shall utilize processes for the economical fabrication/production of the government-authorized design.

3.2.7 SYSTEM ENGINEERING

3.2.7.1 Systems Engineering Management

The Contractor shall provide a System Engineering Management Plan (SEMP) with the incorporation of inputs from the supporting IPTs and working groups (CDRL A016 - Systems Engineering Management Plan (SEMP)). The SEMP shall describe how development will progress, and 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.7.2 Requirements Analysis

The Contractor shall conduct detailed system engineering and design analyses of the proposed hardware/firmware/test software system(s). Materials and equipment to be incorporated into the system or subsystems shall be specified, including a list of all 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 design analyses shall be performed on both the system and component levels.

The Contractor shall develop a design review information package (DRIP) that allows the Government to determine and ensure that the emerging system has demonstrated sufficient maturity to enter the next phase of development (CDRL A018 - Design Review Information Package (DRIP)). The Contractor shall utilize analysis and application of Reduction of Total Ownership Cost (RTOC) considerations within the design, development, production, and support of TIH (20/22) equipment.

A-17

3.2.7.3 Analysis of Alternatives

The Contractor shall deliver an Analysis of Alternatives report by specific Government tasking (CDRL A014 - Technical Report – Study/Services). The Analysis of Alternatives report shall address production requirements, spares, and any requirements to support component repair.

The report shall provide for an initial technology assessment to include recommendation(s) for future year procurements, End of Life (EOL) buys, alternates, substitutes, re-design and the use of replacement vendors. The Analysis of Alternatives reports shall also include a Rough Order of Magnitude (ROM) costs by year and by affected items.

3.2.7.4 System Engineering and Design Analyses

The Contractor shall develop Configuration Item Specifications (CDRL A019 - Program-Unique Specification Documents) in accordance with ANSI/EIA-632. Hardware designs shall meet the allocated system functional requirements derived from the SWFTS Architecture as determined by the Requirement Management IPT. Hardware designs specific to IT/NSS functionality for a program of record shall support the Net Ready Key Performance Parameter of that program in accordance with DoDI 8330.01.

3.2.7.5 Systems Engineering Reviews and Audits

Technical reviews shall be held at a location determined by the Government to discuss and evaluate design status. As part of systems engineering reviews and audits, the Technical Design Agent (TDA) will carry out periodic checkpoints as a function of the Government’s surveillance plan to ensure requirements, design, contract documents, and other program artifacts comply with contract mandates and program goals in accordance with the AN/BGY-1 Systems Engineering Plan. The Contractor shall work with the TDA to resolve the TDA’s findings and accomplish the required entry/exit criteria for each design review. The contractor shall report the TDA’s findings and the accomplishment of required entry/exit criteria in CDRLs A001 – Contractor’s Progress and Status Report and A004 – Integrated Program Management Report.

3.2.7.5.1 System Requirements Review/System Design Review

The Contractor shall support and participate in the SWFTS System Requirements Review (SRR)/System Design Review (SDR), also referred to as a Program Manager’s Review, as directed by the Government. At the SRR/SDR, the Contractor shall demonstrate interpretation/understanding of system requirements including:

a. System functional requirements

b. System interoperability requirements

c. System interface characteristics

d. Platform interface requirements (e.g. power, cooling requirements)

e. System physical constraints (e.g. size/weight)

f. System supportability requirements

A-18

Successful completion of the SRR/SDR and Government approval of the specification shall result in the establishment of the functional baseline(s). The Contractor shall propose entrance and exit criteria for each SRR/SDR for approval by the Government (CDRL A018 - Design Review Information Package, CDRL A005 - Conference Agenda). The Contractor shall propose a SRR/SDR checklist for validation by the TIH Acquisition Program Manager (APM).

3.2.7.5.2 System Functional Review/Preliminary Design Reviews

The Contractor shall conduct a System Functional Review (SFR)/Preliminary Design Review (PDR) to show compliance with the system functional and performance requirements. The completion of the SFR shall result in the establishment of the system hardware and test software functional (performance) baseline. Successful completion of the PDR and Government approval of the preliminary component design shall establish the initial baseline. Changes in requirements from the SRR and associated technical, cost, and schedule impacts shall be addressed.

Recommendations for the entrance and exit criteria for the PDR shall be submitted to the Government for review (CDRL A018 - Design Review Information Package, CDRL A005 - Conference Agenda). All entrance criteria shall be achieved as a prerequisite to conducting the PDR. The Contractor shall provide a life cycle cost estimate at the PDR if required by the Government.

3.2.7.5.3 Production Readiness Review

The purpose of Production Readiness Review (PRR) is for the Contractor to demonstrate to the Government that it has accomplished adequate production planning without incurring unacceptable risks that could breach schedule, performance, cost, technical, contractual requirements, or other established criteria and gain concurrence from the Government to produce production units. The Contractor shall submit a PRR agenda in accordance with CDRL A005 - Conference Agenda.

The Contractor shall conduct a PRR at each facility in which the Contractor intends to produce production qualified TIH (20/22) equipment. The contractor shall conduct separate PRRs for each technology insertion configuration; one PRR for TI-20 and another for TI-22, inclusive of all variants, as applicable. Once all PRR requirements are met, the Program Manager will issue a PRR closure/approval letter. The Contractor is authorized to begin production deliveries only after authorization from the Procuring Contracting Officer. The PRR shall comply with all requirements in accordance with the Government-approved SEMP (CDRL A016).

PRR Entrance Criteria

The Contractor shall meet the following entrance criteria prior to PRR:

a. Completion of EDMs or APUs and testing, if required.

b. Supply sources and vendors are in place.

c. Approved Quality Program Plan (CDRL A020).

d. Approved Test Plan (CDRL A022) and Procedures (CDRL A023).

e. Approved Design Review Information Package (CDRL A018).

A-19

f. Program risks have been evaluated by a joint Contractor/Government (including the Technical Warrant Holder, Technical Design Authority, and Program Manager) review and determined by the Government to be acceptable at this phase of the program.

g. System product baseline has been established and documented for the system, subsystem, equipment, and software to enable repeatable and systematic hardware fabrication/production and software coding to proceed with proper configuration management, as applicable.

h. Technical performance measures are in place and being regularly monitored.

i. Production Program schedule is executable and updated per the approved IMS contained within the IPMR (CDRL A004).

j. Production facilities are adequate to sustain required delivery quantities and rates.

PRR Exit Criteria

The Contractor shall meet the following exit criteria before production deliveries will be authorized:

a. Resolution and closure of all action items generated during the PRR event as approved by the Program Manager, Program Management Ships (PMS) 425.

3.2.7.5.4 Critical Design Review

The Contractor shall conduct a combined Hardware/Software/Firmware Critical Design Review (CDR) for each hardware configuration baseline (inclusive of embedded firmware and test software). Changes in requirements from the PDR and associated technical, cost, and schedule impacts shall be addressed. Recommendations for the entrance and exit criteria for the CDR shall be submitted to the Government for review (CDRL A018 - Design Review Information Package, CDRL A005 - Conference Agenda). The Contractor shall update and present the requirements traceability matrix (CDRL A017 - Specification Requirement Verification Matrix) and any changes to the life cycle cost estimate.

The purpose of the CDR shall be to:

a. Determine that the detailed design of the Hardware, Firmware, and Computer Software Configuration Items (HWCI/SWCI) and the overall system satisfies the performance and specialty/integration engineering requirements of the specifications.

b. Establish the detailed design compatibility between the CI(s) (subsystem integration), the TIH (20/22) system and external interfaces (system/external integration), and elements of Human Factors Engineering.

c. Assess the producibility of the design (the maturity of the design’s manufacturing readiness).

d. Assess HWCI/SWCI design and performance risk areas.

A-20

e. Review the preliminary product specifications and the available engineering drawing packages.

f. Review the logistics support package and development schedule, including interim support plan(s).

g. Review analysis and application of RTOC considerations within the design.

3.2.7.6 Open Systems Architecture Approach

The contractor shall comply with an Open System Architecture (OSA) approach as described in the Defense Acquisition Guidebook (https://www.dau.mil/tools/dag).

As part of an open system architecture approach, the Contractor shall identify to the Government all COTS/NDI equipment, its functionality and the proposed use in the system, and provide copies of license agreements related to the use of the equipment (CDRLs A033 - Configuration Management Plan; A034 – Data Accession List).

During all technical and design reviews, the Contractor shall present/demonstrate how developmental items will be Open Systems Architecture compliant, and at a minimum:

Describe traceability of the requirements back to authoritative sources, and the traceability process used.

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

Describe the rationale for the modularization choices made to generate the design.

Provide rationale that explicitly addresses any tradeoffs performed, particularly those that compromise the modular and open nature of the equipment.

Describe how the proposed system architecture will mitigate the risks associated with technology obsolescence.

Describe how the proposed system architecture will avoid being locked into proprietary or vendor-unique technology and reliance on a single source of supply over the life of the equipment.

The Contractor shall utilize the following open systems architecture approach characteristics:

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

b. 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 (API). The Contractor’s design approach shall be applied to all subsystems and equipment.

A-21

c. Modular Open Systems Approach –The Contractor’s design approach shall produce equipment that consists of hierarchical collections of software and hardware CIs where applicable. The Contractor’s design approach, to the maximum extent practicable, shall utilize 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.

3.2.7.7 Human Factors Engineering

The Contractor shall incorporate the Human Engineering Design Criteria Standard (MIL-STD- 1472G) into the Human Factors Engineering (HFE) design of equipment. HFE analyses and tradeoffs shall be reported at all technical reviews.

3.2.8 DESIGN DISCLOSURE, INTELLECTUAL PROPERTY AND DATA RIGHTS

The Contractor shall utilize and maintain a process that provides design disclosure directly to authorized third party developers via electronic access to in-process design documentation and computer test software. The Contractor shall support an Open Source Initiative with other participants within the Combat Control and Sonar Systems development community. The Contractor shall discuss and attempt to resolve any problems between the Contractor and the third party developers and shall provide written notification to the Contracting Officer of any problems, including documentation of problem resolution. (CDRL A014 - Technical Report – Study/Services).

The Contractor shall provide a list, 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, equipment, processes to be developed or delivered under the contract, or that are described or disclosed in any Technical Data, Computer Software, or Computer Software Documentation to be developed or delivered under the contract. (CDRL A034 - Data Accession List (DAL)).

The Contractor's failure to identify a 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 TIH (20/22) equipment.

3.2.9 TECHNICAL DATA PACKAGE

The Contractor shall develop, deliver, update and maintain the TDP for each TIH (20/22) product baseline (APU(s) and production units) in accordance with MIL-STD-31000A. The Contractor shall incrementally deliver each complete TDP to the Government upon completion (CDRL B001 - Technical Data Package). The TDP shall contain all data (commercial drawings, product drawings, and interface control drawings, Factory Acceptance Tests (FAT) documents/procedures), specifications, and supplementary information (index files) necessary for a third party to manufacture and provide life cycle support for TIH (20/22) configurations developed and qualified under this contract. The Contractor shall provide developmental design/engineering drawings and associated lists in accordance with American Society of Mechanical Engineers (ASME) Y14.100 and CDRL B001 - Technical Data Package to support the PDR and CDR.

A-22

3.2.9.1 Three Dimensional (3D) Computer Aided Design (CAD) Models

The Contractor shall develop, manufacture, deliver, update and maintain Three Dimensional (3D) models and source data files used for the development of the TDP in the native file format as part of the Installation Support Equipment. The 3D models are required for each shipset designed under this contract and shall be included with the Product Drawings Models and Associated List (CDRL B001 - Technical Data Package). The Contractor is not required to provide 3D models for the Countermeasure, Set Acoustic (CSA).

3.2.10 TEST AND EVALUATION

The Contractor shall plan, program, schedule, conduct, support and document all performance testing required and associated with the designed hardware, software, firmware and operator/system interface, necessary to demonstrate that equipment designed, developed, and produced under this contract is compliant with the requirements for naval submarine systems quality and safety. The contractor shall ensure the equipment will operate safely and reliably in the users’ environments. The Contractor shall identify and provide all test hardware, software, tools, support equipment, test stimuli, and operating systems necessary to conduct component qualification, reliability burn-in testing, EQT, and FAT. The Contractor shall provide access to the TIH (20/22) equipment in its development and test facilities for the Government to perform on-site independent tests or evaluations. (CDRL A022 - Test and Evaluation Program Plan

(TEPP))

In the event testing is desired to be waived due to previous qualification testing or for qualification by similarity, the Contractor shall submit the previous qualification test results along with the Contractor’s proposed justification rationale to the Government for approval with the waiver request. (CDRL A012 - Request for Variance)

3.2.10.1 Test and Evaluation Program Plan

The Contractor shall develop, maintain, update, deliver and adhere to a test and evaluation program plan (TEPP) to define all testing (hardware/software/firmware) required for TIH (20/22). The Government must approve the contractor’s TEPP prior to the contractor being authorized to enter into production (CDRL A022 - Test and Evaluation Program Plan). The TEPP shall address recent advances in Automated Testing and Re-Test capabilities that can be accommodated during Government conducted test and certification.

3.2.10.2 Test Requirements

The Contractor shall develop, maintain, update, and deliver the Specification Requirement Verification Matrices (CDRL A017 - Specification Requirement Verification Matrix) and Test Procedures (CDRL A023 - Test Procedure). The Contractor shall generate and deliver the Test/Inspection Report (CDRL A024 - Test/Inspection Report) following the conduct of each test performed. In the event of a test failure, the results shall include documentation of the circumstances of the failure, identification of the equipment under test, the testing step conducted when the failure occurred, physical observations, and meter readings (as applicable).

A-23

3.2.10.3 Test Events

The Contractor shall…