Attachment 2 BFTN SOW 19 June 2018.pdf

RFP N00039-18-R-0058

19 June 2018

STATEMENT OF WORK FOR THE

BATTLE FORCE TACTICAL NETWORK (BFTN)

SPAWAR PEO C4I PMW/A170

San Diego, CA

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE, DISTRIBUTION IS UNLIMITED

(27 OCTOBER 2017)

i

Table of Contents

1 SCOPE

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 BFTN Contract Documents

2.3 Other Government Documents

2.4 Non-Government Documents

3 APPLICABLE DEFINITIONS

3.1 Variance (formerly known as Deviation/Waiver)

3.2 Major (Class 1) Changes:

3.3 Minor (Class 2) Changes:

4 GENERAL REQUIREMENTS

4.1 Program Management (Other Procurement, Navy (OPN))

4.2 Program Management (Operations and Maintenance, Navy (OMN))

4.2.1 Risk Management Program (OMN)

4.2.2 Environmental, Safety and Occupational Health (ESOH) Program (OMN)

4.2.3 Production Configuration Management (CM) (OMN)

4.3 BFTN Program Reviews (PRs)

4.3.1 Post-Award Conference (PAC)

4.3.2 Program Management Review (PMR)

4.4 Overarching Integrated Product Teams (IPTs)

4.5 Integrated Logistics Support (ILS)

4.5.1 Delivery of Products

5 BFTN PRODUCTION UNIT REQUIREMENTS (OPN and SCN)

5.1 Production of AN/USQ-195(V)1 (OPN and SCN)

5.2 Production of AN/USQ-195(V)2 (OPN and SCN)

5.3 BFTN Technical Documentation and System Acceptance (OPN and SCN)

5.3.1 Technical Data Package (TDP) (OPN and SCN)

5.3.2 Bill of Materials (BOM) (OPN and SCN)

5.3.3 Technical Manual (OPN and SCN)

5.3.4 Production Acceptance Test (PAT) (OPN and SCN)

ii

5.3.5 Ruggedization

6 ENGINEERING SUPPORT SERVICES (OPN, OMN, and SCN)

6.1 Engineering Support Services for Production (OPN, OMN, and SCN)

6.1.1 Engineering Support Services for Production (OPN, OMN, and SCN)

6.1.2 Maintenance Planning (OMN)

6.1.3 Request for Variance (RFV) (Formerly known as Request for Deviations/Waivers)(OPN) . 24

6.2 Engineering Support Services for Cybersecurity (OMN)

6.2.1 Support for BFTN Cybersecurity and Information Assurance Requirements (OMN)

6.2.2 Minimum Security Controls (OMN)

6.3 Engineering Support Services for Technical Data Package (TDP) (OPN)

6.3.1 Engineering Supports Services for Provisioning Data (OPN)

6.4 Foreign Travel (OPN and SCN)

7 Ancillary Equipment and Spares (OMN and OPN)

7.1 Ancillary Equipment and Spares (OPN)

7.2 Spares (OMN)

8 BFTN SECURITY LEVEL

8.1 Operations Security (OPSEC) Protection

8.2 COMSEC Information and Equipment

9 GOVERNMENT FURNISHED PROPERTY (GFP)/GOVERNMENT FURNISHED SOFTWARE

10 ACRONYMS

Tables

TABLE 1: GOVERNMENT DOCUMENTS

TABLE 2: BFTN CONTRACT DOCUMENTS

TABLE 3: OTHER GOVERNMENT DOCUMENTS

TABLE 4: NON-GOVERNMENT DOCUMENTS

Appendix A: BFTN Production Acceptance Test………………………………………………………………………………

RFP # N00039-18-R-0058

1 SCOPE

This Statement of Work (SOW) for the Battle Force Tactical Network (BFTN) program requires the procurement and integration of Commercial Off-The-Shelf (COTS) High Frequency Internet Protocol (HFIP) and Subnet Relay (SNR) hardware, COTS software and Government Off-The-Shelf (GOTS) software into a specified configuration. This SOW also specifies requirements for the Production and documentation of the BFTN system, as well as the requirements for BFTN-related engineering services.

The BFTN program is responsible for procuring and integrating COTS hardware, COTS software and GOTS software to provide networked radio frequency (RF) data connectivity over high frequency (HF) and ultra-high frequency (UHF) frequency spectrums, as an intra-force adjunct for long haul communications. BFTN system integration utilizes RF Communicator, a GOTS software system, to provide robust internet protocol (IP) connectivity across the Secret Internet Protocol Routing Network (SIPRNET) and Combined Enterprise Regional Information Exchange System-Maritime (CENTRIXS-M) systems.

The BFTN system provides secure connectivity to the maritime operational environment for Navy and Joint Forces with a persistent IP over RF networking capability in the maritime operational environment, to counter Satellite Communications (SATCOM) denied environments. The system offers two transport paths to the shipboard Local Area Network (LAN) in supporting Line-of-Sight (LOS) and Beyond-Line-of- Sight (BLOS) tactical communications. BFTN provides Line-Of-Sight (LOS) and Beyond-Line-Of-Sight (BLOS) network connectivity for ships, submarines, aircraft, and naval shore via the HF and UHF radio spectrums. In addition, the BFTN program extends the infrastructure of the Global Information Grid (GIG) by connecting to the Automated Digital Network system (ADNS) router, allowing for dynamic network formation, which enables real-time intra-platform information exchange, relay, and routing.

2 APPLICABLE DOCUMENTS

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

All Defense specifications, standards, instructions, and handbooks may be downloaded from the following websites:

• ASSIST (https://assist.dla.mil/online/start/index.cfm)

• Quick Search (http://quicksearch.dla.mil/)

• http://www.esd.whs.mil/Directives/issuances

• https://doni.documentservices.dla.mil/

• http://www.secnav.navy.mil/rda/

• https://www.hdsl.org

• https://www.ecfr.gov

• https://www.nist.gov https://assist.dla.mil/online/start/index.cfm) http://quicksearch.dla.mil/ http://www.esd.whs.mil/Directives/issuances https://doni.documentservices.dla.mil/ http://www.secnav.navy.mil/rda/ https://www.hdsl.org/ https://www.ecfr.gov/ https://www.nist.gov/

• https://www.cnss.gov/

• https://www.acq.osd.mil

• http://dodcio.defense.gov/Library

• http://standards.sae.org

• https://www.iso.org

• https://standards.ieee.org

• https://www.astm.org

• https://global.ihs.com

2.1 Government Documents

Table 1: Government Documents

Document Title Date

DoD CIO Department of Defense (DoD) Net-Centric Data Strategy 9 May 2003

DoDD 5000.01 The Defense Acquisition System 20 November 2007

DoD Risk, Issue, and Opportunity Management Guide

DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs

9 January 2017

DoDI 8320.2 Data Sharing in a Net-Centric Department of Defense 5 August 2013

DoDI 5000.2 Operation of the Defense Acquisition System 7 January 2015

DoDI 8500.01 Cybersecurity 14 March 2014

DoDI 5000.64 Accountability and Management of DoD Equipment and Other Accountable Property

27 April 2017

DoDI 8510.01 Risk Management Framework Process Guide 12 March 2014

SECNAVINST 5000.2E DoN Implementation and Operation of the Defense Acquisition System and The Joint Capabilities Integration and Development System

1 September 2011

DMSMS Management Guidance

Assistant Secretary of the Navy for Research, Development and Acquisition (ASN RD&A) Memorandum, DMSMS Management Guidance

27 January 2005

DoD 4140 1-R DoD 4140 1-R, ASN RD&A Memo, DMSMS Management Guidance

27 January 2005 https://www.cnss.gov/ https://www.acq.osd.mil/ http://dodcio.defense.gov/Library http://standards.sae.org/ https://www.iso.org/ https://standards.ieee.org/ https://www.astm.org/ https://global.ihs.com/

DMSMS Program Management Plans and Metrics

ASN RD&A Memo, DMSMS Program Management Plans and Metrics

12 April 2005

DMSMS Manufacturing Sources and Material Shortages Management Plan Guidance

ASN RD&A Memo, DMSMS Manufacturing Sources and Material Shortages Management Plan Guidance

July 2016

SD-22 DMSMS, A Guidebook of Best Practices and Tools for Implementing a Proactive DMSMS Management Program

September 2010

DoD Guide to Uniquely Identifying Items Version 2.5

DoD Guide to Uniquely Identifying Items Version 2.5 15 September 2015

NSDD 298 National Security Decision Directive 298 22 January 1988

MIL-DTL-87268D Technical Manuals for System-Level hardware/Software, COTS/GOTS, and Newly Developed Equipment

22 September 2014

MIL-HDBK-502A Product Support Analysis 8 March 2013

MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

11 Dec 2015

MIL-STD-129R Military Marking for Shipment and Storage 18 February 2014

MIL-STD-130N(1) DoD Standard Practice Identification Marking of U.S. Military Property

16 November 2012

MIL-STD-31000A Standard Practice Technical Data Packages 26 February 2013

MIL-STD-882E DoD Standard Practice for System Safety

11 May 2012

MIL-DTL-901E Shock tests, H.I. (high-impact) Shipboard Machinery, Equipment, and Systems, Requirements

20 June 2017

MIL-HDBK-2036 Preparation of Electronic Equipment Specifications 1 November 1999

MIL-P-24534A Planned Maintenance System; Development of Maintenance Requirement Cards, Maintenance Index Pages, and Associated Documentation

07 May 1985

VARIOUS All Gov’t reference documents identified within the ILE website’s “Standards, Specifications, Policy, and Guidance”:

http://www.netc.navy.mil/ile/

VARIOUS

DoN CPI Determination

Standard Process

DoN Critical Program Information (CPI) Determination Standard Process, Conduct of CPI Assessments within DoN

26 September 2007

OPNAVINST 5090.1D Environmental Readiness Program 10 January 2014

OPNAV-M 5090.1 Environmental Readiness Program Manual 10 January 2014

OPNAVINST 5100.19E Navy Safety and Occupational Health (SOH) Program Manual for Forces Afloat

30 May 2007

OPNAVINST 5100.23G Navy Safety and Occupational Health (SOH) Program Manual 30 December 2005

29CFR1910.1200 Hazard Communication Standard, Title 29- Code of Federal Regulations 1910.1200

1 October 11

CNSSI 1253 Committee on National Security Systems Instruction (CNSSI) 1253, Security Categorization and Control Selection for National Security Systems

27 March 2014

SP 800-53 National Institute of Standards and Technology (NIST) Special Public (SP) 800-53, Security and Privacy Controls for Federal Information Systems and Organizations

22 January 2015

2.2 BFTN Contract Documents

Table 2: BFTN Contract Documents

Document

Title

PMW/A 170 BFTN BFTN Specification

PMW/A 170 BFTN BFTN AN/USQ-195(V)1 Drawings http://www.netc.navy.mil/ile/

PMW/A 170 BFTN BFTN Bill of Materials for BFTN AN/USQ-195

PMW/A 170 BFTN BFTN GFP & GFI/GFSList

PMW/A 170 BFTN BFTN CDRLs

PMW/A 170 BFTN BFTN Technical Manual (EE679-AX-OMI-010)

2.3 Other Government Documents

Table 3: Other Government Documents

SPAWAR PEO C4I/

PMW/A 170

PMW/A 170 Configuration Management Plan (CMP) 22 May 2012

SPAWAR PEO C4I/

PMW/A 170

PMW/A 170 Item Unique Identification (IUID) Implementation Plan for PMW/A 170 Programs

11 February 2015

SPAWAR PEO C4I/

PMW/A 170

PMW/A 170 DMSMS Guide January 2009

SPAWAR PEO C4I/

PMW/A 170

PMW/A 170 Risk Management Plan 27 January 2015

PEOC4I LCCMIM Program Executive Office Command, Control, Communications, Computer, Intelligence Lifecycle Configuration Management Implementation Manual (LCCMIM)

February 2007

SPAWAR PEO C4I PEO C4I Naming and Numbering Standard

2.4 Non-Government Documents

Table 4: Non-Government Documents

Document Title Date

IEEE Std 24765-2010 Standard for Systems and software Engineering— Vocabulary

15 December 2010

SAE EIA-649B Configuration Management Standard 1 April 2011

SAE GEIA-HB-649A Configuration Management Standard Implementation Guide

1 March 2016

SAE EIA-836 Configuration Management Data Exchange and

Interoperability

26 September 2015

ISO 10007:2017 Quality Management Guidelines for Configuration Management

March 2017

ASTM-D3951 Standard Practice for Commercial Packaging March 2014

National Aerospace Standard

(NAS)411

Hazardous Materials Management Program Standard Practice

September 2013

NAS 411-1 Hazardous Materials Target List Standard Practice September 2013

SAE GEIA-STD-0007B Logistics Product Data 1 May 2013

3 APPLICABLE DEFINITIONS

The following definitions apply to this SOW.

3.1 Variance (formerly known as Deviation/Waiver)

A departure from approved product definition information, for a limited amount of time or for a specified effectivity, that does not require revision of approved product definition information.

Variances which propose alternative methods or approaches to meeting a standard may equal or exceed safe practice and will not be considered a negative mark against an accredited facility. Working in conjunction with the program teams, the scheduler shall establish a schedule baseline to monitor and report variances to the baseline to program leadership. The Contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from requirements, without prior Government approval of the RFV. The acceptance of an item, which during manufacture, or after having been submitted for Government acceptance is found to depart from specified requirements, but nevertheless is considered suitable for use “as is” or after repair by an approved method. This does not apply to software code listings. A major variance consists of a departure involving: safety; performance;

interchangeability; reliability; survivability; or maintainability. A minor variance is a departure that is not classified as major.

3.2 Major (Class 1) Changes:

Affects approved baselines, contractually specified form, fit or function requirements such as:

• Performance

• Reliability, maintainability, survivability

• Weight, balance, moment of inertia

• Interface characteristics

• Electromagnetic characteristics (i.e., requirement would be out of specification limits)

• Other technical requirements of the specification

• Affects one or more of the following, after product

• Product furnished by a customer (GFE)

• Safety

• Compatibility with interfacing products (including such products as test equipment, support equipment and associated software)

• Delivered operation or servicing instruction, for which there is no planned and funded update requirement, such as for periodic or continual maintenance of the instructions

• Preset adjustment to the extent that product identification should be changed

• Interchangeability, substitutability, or replaceability as applied to Configuration Items (CIs) and to all subassemblies and parts

• Requires retrofit of delivered products, e.g., by product recall, modification kit installation, attrition (replacement during maintenance by modified spares), etc.

• Affects cost/price to customer(s) (including incentives and fees), guarantees, warranties, contracted deliveries or milestones; and is an engineering change that does not impact factors 1 through 3.

3.3 Minor (Class 2) Changes:

Minor (Class 2) Changes are those changes which impact none of the Class 1 factors specified above.

4 GENERAL REQUIREMENTS

The Contractor shall provide all resources, materials, equipment, and facilities to procure and integrate the BFTN system rack, load Government provided software, and conduct acceptance testing for each system delivered. The Contractor shall provide related Contract Data Requirement Lists (CDRLs) in accordance with this SOW.

4.1 Program Management (Other Procurement, Navy (OPN))

The Contractor shall provide program management services to ensure all work conducted during this contract is planned and executed in a manner that will achieve all planning, management, technical, logistical, cost, and schedule objectives related to the procurement and production of BFTN systems. All work is to be performed within the stated budget and all deliverables shall be provided in accordance with the requirements stated in this document. The Contractor shall ensure coordination and integration of all functional areas within each task. The Contractor shall establish and perform program management functions to ensure contracting related actions meet established need dates of the Government. The Contractor shall use the Contracting Officer Representative (COR) as the primary point of contact for all program activities.

The Contractor shall appoint a Program Manager (PM) responsible for carrying out the work as set forth in this SOW. The PM shall be the focal point for all program communications between the Government and the Contractor. The Contractor PM shall provide the Government with a monthly update of the BFTN contract status via the Contractor’s Progress, Status and Management Report (CDRL A001).

CDRL Deliverable(s):

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

4.2 Program Management (Operations and Maintenance, Navy (OMN)) The Contractor shall provide program management services to ensure all work conducted during this contract is planned and executed in a manner that will achieve all management, technical, logistical, cost, and schedule objectives. All work is to be performed within the stated budget and all deliverables shall be provided in accordance with the requirements stated in this document. The Contractor shall ensure coordination and integration of all functional areas within each task. The Contractor shall establish and perform program management functions to ensure contracting related actions meet established need dates of the Government. The Contractor shall use the Contracting Officer Representative (COR) as the primary point of contact for all program activities.

The Contractor shall appoint a Program Manager (PM) responsible for carrying out the work as set forth in this SOW. The PM shall be the focal point for all program communications between the Government and the Contractor. The Contractor PM shall provide the Government with a monthly update of the BFTN contract status via the Contractor’s Progress, Status and Management Report (CDRL A001).

CDRL Deliverable(s):

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

4.2.1 Risk Management Program (OMN)

The Contractor shall conduct Risk Management consistent with the guidance in the Department of Defense (DoD) Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs dated 9 January 2017, and the PMW/A 170 Risk Management Plan, dated 27 January 2015, throughout the life of the contract. The Contractor shall provide Risk Management to address risk assessment and subsequent management of any risk associated with non-compliance to the BFTN design and requirements. The Contractor, at a minimum shall address cost, schedule, ESOH risk assessment, and technical Risk Management for critical design areas including:

a. Reliability

b. Configuration Control Program for hardware and software

c. Software Performance

d. Information Assurance and Communications Security (COMSEC) compliance

e. Supportability

f. System Availability

g. Obsolescence

h. Interoperability

The Contractor shall provide updates on all Risk Management related issues in the monthly Contractor’s Progress, Status and Management report (CDRL A001).

CDRL Deliverable(s):

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

4.2.2 Environmental, Safety and Occupational Health (ESOH) Program (OMN) The Contractor shall conduct ESOH compliance/protection that reflects the Contractor’s intentions for meeting ESOH regulatory requirements during the BFTN life-cycle stages (i.e. operation, maintenance and disposal). The Contractor’s ESOH program shall comply with the ESOH laws and regulations pertaining to the BFTN effort, the risks these laws may pose, and the measures required to comply with these laws and regulations for the life-cycle of the BFTN. The Contractor shall implement pollution prevention initiatives where applicable to reduce regulatory compliance burdens of the Government.

The Contractor shall avoid the use of hazardous materials and generation of hazardous waste wherever practicable by avoiding materials that pose ESOH risks. The Contractor shall avoid or minimize the use of prohibited and restricted hazardous materials as defined in NAS411-1 and obtain approval of the Technical Authority for uses that cannot be avoided or eliminated.

The Contractor shall adhere to a safety and occupational health program that meets the requirements in MIL-STD-882E. The Program shall identify and evaluate system safety and health hazards, define risk levels, and establish a system to manage the probability and severity of all hazards associated with the use and disposal of the BFTN system. Health hazards include conditions that create significant risks of death, injury, acute chronic illness, disability, or reduced job performance of personnel who produce, test, operate, maintain, or support BFTN.

The Contractor shall provide a technical report via CDRL A002 to address ESOH. The report shall include the following information and certification:

a. A list of all BFTN components (include name, type, manufacturer and model number), all hazards by subsystem or major component level, the actions to address the identified hazards and the risks that remain after the controls are applied or the hazards for which no controls could be applied.

b. A statement that the system does not contain hazardous materials or general hazardous wastes (i.e., explosive, toxic, radioactive, carcinogenic, etc.) as delivered on the system and for operation/maintenance of the system pursuant to NAS411-1. In the event the system does contain hazardous materials or generate hazardous wastes, data will be included in the report pursuant to the requirements of MIL-STD-882E and NAS411.

c. A statement signed by the Contractor stating that all identified hazards have been eliminated or controlled and that the system is ready to operate.

Further, the Contractor shall be responsible for full compliance with Hazard Communication Standard, Title 29- Code of Federal Regulations 1910.1200, MIL-HDBK-2036, and National Aerospace Standard (NAS) 411, Hazardous Material Management Program. The Contractor shall ensure all Contractor personnel and facilities used in performance of this SOW (including those of Sub-Contractors) satisfy federal, state, and local ESOH regulations and statutes. The Contractor shall submit a signed statement via CDRL A002 stating its compliance with federal, state, and local ESOH regulations and statutes.

CDRL Deliverable(s):

• A002: Technical Report – ESOH Report (DI-MISC-80508B)

4.2.3 Production Configuration Management (CM) (OMN)

The Contractor shall use a Production CM process to control all configuration documentation representing or comprising the BFTN system configuration items in compliance with the PMW/A 170 Configuration Management Plan (CMP) process requirements while staying in alignment with the PEO C4I Life Cycle Configuration Management Implementation Manual (LCCMIM) and the SPAWARINST

4130.3 Life Cycle Configuration Management (CM) Policy. The Contractor shall perform CM tasks and activities for the Production BFTN Systems under the direction of the BFTN COR. All CM activities shall be approved by the BFTN COR before implementation or delivery of any Engineering Change Proposals (ECPs) (CDRL A005) Class 1 or 2 as described in SOW Section 6.1.1.3, Engineering Change Proposal (ECP). This shall include an internal configuration management plan for the control of all configuration documentation, physical media, and physical parts representing or comprising the BFTN system. The Contractor shall provide a monthly update of CM status in the monthly Contractor’s Progress, Status and Management report (A001).

CDRL Deliverable(s):

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

4.2.3.1 Configuration Management and Planning (CMP) (OMN)

The Contractor shall submit to the COR for review and approval the CM Plan describing the processes, methods and procedures used to manage the functional and physical characteristics of the BFTN Systems assigned CI(s) for the life of the contract. (CDRL A003) The Contractor shall perform CM planning to define the following factors:

a. Objectives of the CM program and of each applicable CM element.

b. Appropriate level of CM activity for each CM function throughout the product’s life cycle.

c. CM organization and organizational relationships.

d. Responsibilities and authority of CM professionals.

e. CM resources to be used (tools, techniques, training, and methodologies).

f. Coordination activities to be used with internal and external agencies (e.g., Government, other

Contractors, other Government agencies, foreign governments).

g. Functions, responsibility, and authority of CCBs.

h. A release process for product configuration documentation.

i. Methods to be used to ensure the effectiveness of sub-Contractor/sub-vendor CM processes.

j. CSA activities for creating, editing, reviewing, approving, releasing, publishing, and distributing product configuration documentation and configuration change documentation.

k. Identification and labeling structure for CIs.

l. Data handling, processing, storage, integrity, transfer, releasability/disclosure, security, and maintenance documentation requirements.

m. Maintaining the security and integrity of shared data.

n . The CM plan shall ensure life cycle CM planning and provide CM program milestones and schedules to monitor program status.

CDRL Deliverable(s):

• A003: Contractor’s Configuration Management Plan (DI-SESS-80858C)

4.2.3.2 Configuration Identification (OMN)

The Contractor shall use the CM process to ensure identification and labeling structure is used in compliance with the PEO C4I Naming and Numbering Standard and the PMW/A 170 CMP for all PMW/A

170 Government Furnished Equipment (GFE)/Government Furnished Information (GFI) to include physical configuration items and the configuration documentation representing or comprising a physical configuration item. The Contractor shall ensure that configuration baselines are captured, maintained, managed and reported by generating a technical baseline report (CDRL A004) as required in accordance with PMW/A 170 CMP and the SPAWARINST 4130.3 CM Policy. The Contractor shall ensure each succeeding baseline is traceable to, and a detailed extension of, its predecessor(s). The latest revisions of the configuration baseline documents at the time of contract award shall serve as the configuration baseline from which ECs are to be developed under this contract. The contractor shall mark and label software as follows:

• Embed software identifier and version in the source code header.

• Mark each software medium (i.e., disks, hard drives) with a label.

• Each label shall contain, or provide cross-reference to, a list of the applicable software identifiers of the entities it contains.

• The label shall also indicate the status of the software maturity on the medium, e.g., whether this software is a release candidate or if the software has been tested and verified.

• Mark with a label all CSCIs deliverable media. Label shall contain:

o Government Contract number.

o CSCI Number (include a designator indicating whether source or executable code).

o Design activity Cage Code.

o Media Number (e.g., 1 of 2, 2 of 2) if there are multiple units per set. Each time a new version of software is issued, new copy numbers, starting from 1, must be assigned.

CDRL Deliverable(s):

• A004: Technical Baseline Description Document (DI-SESS-81121A)

4.2.3.3 Item Unique Identification (OMN)

IUID is a system of distinguishing one object from another, allowing the DoD to track identical objects separately. The IUID system requires that qualifying items have a data matrix inscribed either directly on the item or on permanent, machine-readable label affixed to the item. The data matrix contains a set of data elements that can be concatenated to form a Unique Item Identifier (UII) List. The Contractor shall implement a Unique Identification (UI) to provide UI information on all end item equipment (new or modified), spares, and storage containers that comply with IUID, DFARS Clause 252.211-7003 and MIL-

STD-130N.

Without modifying the current configuration baseline of the BFTN system, the Contractor shall make every attempt to place UID labels in a user-friendly location, so that they are in view to the human eye or a scanner or scan gun reader. Labels shall be applied on all new production parts, ruggedized components, and on any qualifying part undergoing repair and/or refurbishment.

The Contractor shall identify and mark all end items in accordance with DoD Instruction (DoDI) 5000.64, MIL-STD-130N, DoD Guide to Uniquely Identifying Items, Version 2.5, dated 15 September 2015, and the Item Unique Identification (IUID) Implementation Plan for PMW/A 170 Programs.

Contractor shall report all IUID marked assets in the IUID Registry in accordance with (IAW) DFARS Clause 252.211-7007 and MIL-STD-130N (w/CHANGE 1). For Configuration Items (CI)s marked with Unique Item Identifier (UII), the Contractor shall check DoD IUID Registry to ensure the UII has not been previously assigned to an item.

The Contractor shall provide IUID status updates and reports (utilizing DI-MGMT-81804A for content), in the monthly Contractor’s Progress, Status and Management report (CDRL A001).

CDRL Deliverable(s):

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

4.2.3.4 Configuration Control (aka Change Management) (OMN)

The contractor shall maintain configuration control of configuration documents. The contractor shall report via CDRL A001 whether there are changes to configuration documents. If there is nothing to report, the contractor shall state there is “nothing to report.”

CDRL Deliverable(s):

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

4.2.3.5 Configuration Status Accounting (CSA) (OMN)

The Contractor shall establish and maintain a CSA database, which represents the configuration of the BFTN system. All baselines and changes shall be documented in the Contractor’s CSA database. The Contractor shall permit acceptance of commercial product information in the CSA database; however, if requirements to report data outside of the CSA database or format exist, the Contractor shall deliver the information as a supplement to prevent disruption to their existing system. The Contractor shall reconcile any differences between Contractor information and Contractor practices in the CSA database to provide the Government with clear accountability of product information. The Contractor shall be responsible for reporting this CSA information monthly IAW CDRL A006.

The Contractor shall use a CSA system to capture, store, and maintain product configuration information about the product that is either provided by the government or created by the contractor for the duration of the contract. The Contractor shall maintain the validity of the data stored in a CSA system.

The Contractor shall implement a CSA system that has the following capabilities:

a. Capture and maintain the currently approved product configuration information by the identification number assigned to each CI.

b. Capture and maintain all historical product configuration information with traceability detailing product configuration from contract award to the present.

c. Store and manage all product configuration information, which includes but not limited to product definition information (information that defines the product’s requirements, documents the product attributes, and is the authoritative source for CM of the product) and/or product operational information (information developed from product definition information used to test, operate, maintain and dispose of a product) as defined in the contract.

d. Identify dependencies among CIs.

e. Report the status of both proposed and approved configuration changes and variances to all CIs.

f. Record, track and report implementation status and release of configuration documentation for approved configuration changes.

g. Record and report the planning and results of configuration audits to include the status and final disposition of identified discrepancies.

h. Record and report all product data inherited from sub-tier Contractors, to include vendor part numbers and serial numbers, and provide clear traceability from these components to their respective next higher assemblies.

The Contractor shall:

a. Make CSA system and product configuration information readily available to the Government or designated representative, via on-site inspection, remote access, or regular submissions of CSA information and updates in accordance with the contract.

b. Comply with DoD Cyber Security requirements for the purpose of interoperating with the Government’s system as in an integrated digital environment.

c. Ensure recorded product configuration information is adequately secured, safeguarded and retrievable after extended storage.

d. Provide a digital delivery to the Government upon the completion of the contract, CSA information and configuration baseline documentation created, collected, and managed during the contract.

CDRL Deliverable(s):

• A005: Configuration Status Accounting (DI-SESS-81253C)

4.3 BFTN Program Reviews (PRs)

The Contractor shall conduct BFTN PRs in accordance with the program requirements provided in the subsequent paragraphs of this document.

4.3.1 Post-Award Conference (PAC)

The Contractor shall hold a Post-Award Conference (PAC) at the Contractor’s facility within forty-five (45) calendar days of the contract award date. The Government and the Contractor will mutually agree upon a date to hold the PAC.

The Contractor shall prepare and distribute an agenda, including presentation materials. At a minimum, the following topics shall be addressed:

a. Identify and introduce Contractor management, engineering, and other key personnel to the Government representatives. Every individual shall define his/her area of responsibility and accountability.

b. Explain the Contractor’s organization, plans, procedures, and schedules to execute this SOW, including illustrating how the Contractor will minimize schedule, cost, and performance risks.

c. Present the Contractor’s business and technical management procedures (e.g., technical point of contact assignments, status reporting procedures, and designated lines of authority) that shall be implemented to accomplish the requirements of the contract.

d. Allocate time for the Government to present its organization, plans, procedures, schedules, and concerns.

e. Allocate time for an open forum to discuss contract, program and technical issues.

The PAC shall also evaluate the Contractor's production readiness, identify existing or projected manufacturing problems, and areas of risk. The Contractor shall demonstrate progress in the following areas: (1) attaining the program's production goals, (2) resolving manufacturing problems (or that a plan for their resolution acceptable to the Government has been developed), and (3) mitigating all production risks. The Contractor shall show that the system design has included those key production factors (e.g., least cost, minimum manufacturing time, manufacturing simplicity/flexibility, resource availability) necessary to ensure the system can be acquired on schedule at minimum cost. As part of the PAC, the Contractor shall provide a Production Readiness Review (PRR) section in the agenda that will address the following considerations, as applicable:

a. A Manufacturing Program Review to include the overall manufacturing process and detailed factors such as: manufacturing organization, responsibilities, facilities and equipment, manufacturing methods, and production flow,

b. A status review of all production efforts for cost and schedule considerations,

c. A status review of manufacturing technology and other previously recommended actions to reduce cost, manufacturing risk, and industrial base concerns,

d. The status of long lead items for production, if any.

The Contractor shall propose the review dates and obtain approval by the Government and incorporate into the program schedule.

CDRL Deliverable(s):

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

4.3.2 Program Management Review (PMR)

The Contractor shall conduct a PMR twice each year. These reviews shall be no more than one (1) day in duration. At least one PMR shall be held at a Government facility unless specifically requested by the Government to be held at the Contractor’s facility or another designated location. The other PMR may be conducted as a teleconference. The scope of the reviews shall address the status of all ongoing tasks and delivery schedules for all material procurement. For each PMR, the Contractor shall prepare and distribute a meeting agenda and minutes, in accordance with the applicable DD 1423, for Government approval. The Government reserves the right to modify the agenda prior to the PMR. The Contractor shall deliver all technical review presentation materials to the Government no later than seven (7) calendar days prior to the scheduled review. The meeting minutes from each PMR shall be submitted no later than seven (7) calendar days after the conclusion of the meeting.

The PMR meeting shall address all contracting efforts impacting schedule and performance (e.g. contract task order status, financial status, schedule status, progress against major milestones, risk management, manpower, configuration management, hardware and software engineering, logistics, warranty status, quality assurance, ESOH, obsolescence, and any factors affecting contract deliverables). The Contractor’s functional leads (e.g., Key Personnel, Software Manager, and Mechanical Engineer) shall report on the status of their respective tasks. To the maximum extent possible, PMRs shall be coordinated with design and technical reviews to maximize program efficiency. The PMR shall provide an updated status of action items assigned at previous PMR, current program task statuses, and projected tasks. The Contractor shall provide a contract data status and schedule report at each review. In addition, the Contractor shall present technical, management, and logistic problem areas and shall address any factors affecting contract deliverables.

As part of the initial review, the Contractor shall present business and technical management procedures (including, but not limited to technical point of contact assignments, status reporting procedures, designated lines of authority, etc.) that shall be implemented to accomplish the requirements of the contract. The Government reserves the right to schedule additional reviews or working groups if critical issues arise or significant events or changes have occurred. The Contractor shall specifically address known or anticipated impacts to systems and terminal performance.

CDRL Deliverable(s):

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

4.4 Overarching Integrated Product Teams (IPTs)

The Contractor shall provide technical representation at engineering or installation working group meetings, a.k.a. IPT sessions; providing technical assessments and reports in appropriate formats. The Contractor shall also provide production support or recommendations during the IPT to ensure effective tracking, reporting, and management in support of production and procurement.

These IPTs will be chaired by a Government designated individual and will include representatives of other Government organizations as well as Contractors. Since the COR may or may not attend the IPT meetings, the Contractor shall immediately notify the COR and PCO in writing if the Contractor is unable to meet contractual terms resulting from issues identified during the IPT process. The writing shall identify the issue and the proposed resolution. The Contractor shall provide status and meeting minutes via CDRL A001.

CDRL Deliverable(s):

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

4.5 Integrated Logistics Support (ILS)

The Contractor shall address BFTN logistics considerations throughout the performance of the BFTN System production to include maximization of parts standardization, interchangeability, and commonality; and minimization of the number and types of spares.

4.5.1 Delivery of Products

The Contractor shall prepare production products for delivery IAW the most current version of ASTM-D- 3951, “Standard Practice for Commercial Packaging.” The Contractor shall provide support to ensure all system, equipment, and support items are preserved, packaged, handled, and transported properly, including environmental considerations, equipment preservation requirements for short and long-term storage, and transportability. Packaging will afford protection against corrosion, deterioration, and physical damage when exposed to shock, vibration, temperature, and humidity during domestic shipment.

Additionally, the Contractor shall mark all shipments under this contract IAW the most current version of MIL-STD-129R “Military Standard Marking for Shipment and Storage” dated 18 February 2014.

The Contractor shall provide status of delivery via CDRL A001.

CDRL Deliverable(s):

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

5 BFTN PRODUCTION UNIT REQUIREMENTS (OPN and SCN) The Contractor shall perform the efforts set forth in this SOW and shall comply with all other provisions and documents referenced in this SOW.

5.1 Production of AN/USQ-195(V)1 (OPN and SCN)

In accordance with the BFTN Specification, the AN/USQ-195(V)1 is the BFTN shipboard variant. Drawings (Production and System Interconnect) for AN/USQ-195(V)1 shall serve as the baseline for AN/USQ- 195(V)2, which is the BFTN submarine variant. AN/USQ-195(V)2 removes the rack and panels from

AN/USQ-195(V)1.

The Contractor shall build the BFTN AN/USQ-195(V)1 IAW with the Specification and Technical Data Package (TDP) compromised of the Drawings (Production and System Interconnect) and Bill of Materials (BOM). All Contractor CLIN deliveries shall meet the requirements of this SOW, Specification, Drawings (Production and System Interconnect), and BOM.

5.2 Production of AN/USQ-195(V)2 (OPN and SCN)

In accordance with the BFTN Specification, the AN/USQ-195(V)1 is the BFTN shipboard variant. Drawings (Production and System Interconnect) for AN/USQ-195(V)1 shall serve as the baseline for AN/USQ- 195(V)2, which is the BFTN submarine variant. AN/USQ-195(V)2 removes the rack and panels from

AN/USQ-195(V)1.

The Contractor shall build the BFTN AN/USQ-195(V)2 IAW with the Specification and Technical Data Package (TDP) compromised of the Drawings (Production and System Interconnect) and Bill of Materials (BOM). All Contractor CLIN deliveries shall meet the requirements of this SOW, Specification, Drawings (Production and System Interconnect), and BOM.

5.3 BFTN Technical Documentation and System Acceptance (OPN and SCN)

5.3.1 Technical Data Package (TDP) (OPN and SCN)

The Contractor shall deliver every year an updated TDP IAW CDRL A008. The updated TDP shall encompass any changes resulting from approved ECPs, BOM changes, current system configuration, and design of BFTN units. The TDP shall also include the Specification and COTS manuals for all BFTN hardware.

The Contractor shall notify the COR of any deviations from the TDP via CDRL A001. The Contractor shall obtain approval from the PCO and/or COR in the event of a deviation(s) from the TDP.

CDRL Deliverable(s):

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

• A007: Technical Data Package (TDP) (DI-SESS-80776A)

5.3.1.1 Provisioning Technical Data (OPN and SCN)

The Contractor shall deliver every year an updated BFTN Provisioning Technical Data (PTD) package. The updated PTD shall include any modifications made to the BFTN System. All modifications must be approved by the COR and PCO.

When an approved engineering design or production change requires new identification the Contractor shall develop and deliver supplemental data for provisioning in an Interactive Computer Aided Provisioning System (ICAPS) compatible format. The Government shall provide a Microsoft Excel spreadsheet as Government Furnished Information (GFI) to be populated by the Contractor. This spreadsheet details the required supplemental data necessary for provisioning.

CDRL Deliverable(s):

• A008: Supplementary Provisioning Technical Documentation (DI-ALSS-81557)

5.3.2 Bill of Materials (BOM) (OPN and SCN)

The Government shall provide an initial BOM to the Contractor. In accordance with International Organization for Standards (ISO) 9001, the Contractor shall maintain, and update the BOM every year IAW CDRL A010 for all Lowest Replaceable Units (LRUs) and piece parts. A BOM is a list of the parts, sub-assemblies and raw materials that are used to make a product. It defines the type, number, quantity, and relationships of parts and assemblies. The Contractor shall notify the COR of any deviations (due to obsolescence, cost savings, etc.) from the BOM via CDRL A001. The Contractor shall obtain approval from the PCO and/or COR in the event of a deviation(s) from the BOM. When actual or expected prices are applied, it becomes the Priced 016 Material (PBOM). These efforts are necessary to ensure that the Government has resources available to acquire spares assets beyond the period of performance of the contract to support the life cycle of the BFTN system and their variants. If the system used by the Contractor to manage the BOM is an electronic database accessible by the internet, the Contractor is to allow the Government designated personnel unlimited view and query access only to the cumulative data provided in this section.

CDRL Deliverable(s):

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

• A009: BOM for Logistics and Supply Chain Risk Management (DI-PSSS-81656B)

5.3.3 Technical Manual (OPN and SCN)

Contractor shall deliver Commercial Off-The Shelf (COTS) Technical Manuals (TM) along with equipment or system delivery 60 days prior to PAT. Manuals provided to the Government describing form, fit, and function data as well as operation, maintenance, installation, and training (other than detailed manufacturing or process data) are considered to have unlimited rights as per DFARS 252.227-7013 and 252.227-7015.

For any new end items, which change the configuration of the BFTN system, the Contractor shall provide supplemental technical documentation which can be added to the existing Operational and Maintenance technical manuals. At minimum, supplemental technical documentation shall include functional descriptions, operational instructions, troubleshooting procedures, safety instructions and warnings, preventative and corrective maintenance procedures, and any associated drawings, diagrams or figures for the configuration item being changed.

CDRL Deliverable(s):

• A010: Commercial Off-The-Shelf (COTS) Manuals (DI-TMSS-81815)

• A011: Supplemental Technical Documentation (DI-TMSS-81816)

5.3.4 Production Acceptance Test (PAT) (OPN and SCN)

The Contractor shall conduct a PAT for each BFTN system prior to delivery in accordance with the Government PAT Procedure (Appendix A) and BFTN Technical Manual (EE679-AX-OMI-010). The Contractor shall conduct the PAT at the Contractor’s facility. The Government will be on-site to monitor the PAT of at least one system for each delivery order.

The Contractor shall operate the BFTN system in accordance with the safety precautions outlined in the Technical Manual (EE679-AX-OMI-010).

CDRL Deliverable(s):

• A012: Production Acceptance Test Report (DI-NDTI-80809B)

5.3.5 Ruggedization

The Contractor shall conduct ruggedization of many major and minor components within the BFTN system IAW the section regarding Grade B of MIL-DTL-901E.

6 ENGINEERING SUPPORT SERVICES (OPN, OMN, and SCN) As directed by individual task order/delivery orders, the Contractor shall provide engineering support services.

6.1 Engineering Support Services for Production (OPN, OMN, and SCN) As directed by individual task order/delivery orders, the Contractor shall provide engineering support services related to production of BFTN systems.

6.1.1 Engineering Support Services for Production (OPN, OMN, SCN and RDT&E) The Contractor shall provide production engineering support, including review and evaluation of production design data and documentation, production configuration control, product improvement, production engineering, quality assurance, acceptance test and evaluation,. In addition, the Contractor engineering and technical services will address maintenance engineering and logistics supportability efforts designed and incorporated into the production manufacturing process, maintenance planning for fielding production units, site activation planning and first installation support, and other related engineering functions which are integral to the item’s manufacture.

The Contractor shall implement hardware and software upgrades for BFTN systems. These upgrades may include, but are not limited to changes for spectral monitoring, modem waveform, network interface, environmental qualification test and ease-of-use improvements. The Contractor shall document the modifications in accordance with the configuration management of this SOW. Further, the Contractor shall evaluate the impact resulting from modification to the BFTN system to cost, schedule, and performance. The Contractor shall provide its assessment via CDRL A001.

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

6.1.1.1 Engineering Support Services for Diminishing Manufacturing Sources and Material Shortages (DMSMS) (OPN and SCN)

The Contractor shall conduct DMSMS in accordance with the following instructions:

• Assistant Secretary of the Navy for Research, Development, and Acquisition (ASN(RD&A)) memorandum, “DMSMS Management Guidance,” of 27 January 2005

• DoD 4140 1-R, ASN (RD&A) Memo - DMSMS Mgt Guidance dated 27 Jan 2005

• ASN (RD&A) Memo - DMSMS Program Mgt Plans and Metrics dated 12 Apr 2005

• ASN (RD&A) Department of the Navy (DoN) DMSMS Plan Guidance dated Apr 2005

• SD-22 - Diminishing Manufacturing Sources and Material Shortages, A Guidebook of Best

Practices and Tools for Implementing a Proactive DMSMS Management Program dated September 2010,

• PMW/A 170 DMSMS Plan dated January 2009

• SECNAVINST 5000.2E

The Contractor shall utilize their current parts control program and support the DMSMS process for the BFTN system.