JS-1 Statement of Work Amend 0001.pdf

STATEMENT OF WORK

for

AN/BQS-25A LIGHT WEIGHT LOW COST CONFORMAL ARRAY

2 March 2020

Department of the Navy

Program Executive Office, Submarines

Submarine Acoustic Systems – Hull Sensors

(PMS4013)

1333 Isaac Hull Avenue SE

Washington Navy Yard

Washington, D.C. 20376

Distribution statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only, Administrative/Operational use, Other U.S. requests for this document will be referred to PMS 4013.

i

Table of Contents

1.0 SCOPE

1.1 Background

2.0 APPLICABLE DOCUMENTS

2.1 Department of Defense CIPS

2.2 Government Standards

2.3 Other Government Documents

2.4 Non-Government Standards and Publications

2.5 Availability of Department of Defense Documents

3.0 GENERAL REQUIREMENTS

3.1 System Engineering Management

3.2 System Safety Hazard Analysis

3.3 Facility

3.4 Program Planning

3.4.1 Post Award Conference

3.4.2 Program Management Plan

3.4.3 Subcontractor Management

3.4.4 Contract Work Breakdown Structure

3.4.5 Earned Value Management System

3.4.6 Critical Path Network

3.4.7 Conferences/Meetings

3.5 Quality Management System

3.6 Risk Management

3.7 Data Management

3.8 Security Requirements

3.8.1 Facility Clearance and Safeguarding Requirements

3.8.2 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews 8

3.8.3 Compliance to NIST 800-171

3.8.4 Cyber Incident Response

3.8.5 Naval Criminal Investigative Service (NCIS) Outreach

3.8.6 NCIS/Industry Monitoring

3.9 Logistics

3.9.1 Logistics Guidance Conference

3.9.2 Logistics Provisioning Conference

3.9.3 Integrated Logistics Working Group Meetings

ii

3.10 Supportability Analysis Program

3.11 Supply Support

3.12 Demilitarization and Disposal

3.13 Cybersecurity – Protecting Information in Nonfederal Systems & Organizations 12

4.0 FIRST ARTICLE

4.1 First Article Hardware

4.2 Specification Requirement Verification

4.3 Testing

4.4 Failure Analysis and Corrective Action System (FRACAS)

5.0 LWLCCA PRODUCTION

5.1 Hardware

5.2 Integrated Baseline Review

5.3 Test, Acceptance, and Evaluation

5.4 Configuration Audits

5.4.1 Functional Configuration Audit

5.4.2 Physical Configuration Audit

5.5 Baseline Update

5.5.1 Update Drawings/Models & Associated Lists

5.5.2 Product Baseline Configuration Control

5.5.3 Non-compliant Hardware

5.6 Failure Analysis and Corrective Action

5.7 Array Interface Requirements

5.8 Supportability Analyses Database

5.9 Supply Support

5.10 Technical Manual Source Data

5.11 Maintenance and Repair Procedures

6.0 ENGINEERING SERVICES

6.1 Failure Analysis

6.2 Management and Technical Instruction

6.3 Configuration Management

6.5 Integrated Logistic Support

1.0 SCOPE

This Statement of Work (SOW) governs the Light Weight Low Cost Conformal Array

(LwLCCA) contract (i.e., the fabrication, production, testing, delivery, etc., of the subject system). The SOW also governs spares and logistical support. It addresses both a First Article and the subsequent Production Systems.

Further, the SOW details the services necessary for LwLCCA production and performance of the subject contract. Such services include, but are not limited to, program management, data management, logistical support, configuration management, test and evaluation, installation support, and engineering services.

Under the resultant contract, the Government will direct Contractor via Technical Instruction(s)

(TIs).

1.1 Background

Accurate tactical awareness is critical in all submarine mission areas. In crowded areas or littoral waters, the importance of accurate tactical awareness is heightened as the probability of collision increases in such areas. Close (nearby) contact identification becomes more difficult on SONAR displays crowded (or cluttered) with low and medium frequency acoustic information.

In 2005, the Chief of Naval Operations (then N87, now Code N97) sought to address this need and rectify prospective issues. In its “Submarine Undersea Dominance – Road Ahead (FY05 –

FY11)” (Ser. N77/5S934212 dated 03 Feb 2005), N97 created a requirement for improved situational awareness and contact management for submarine operations and also documented the Undersea Warfare Enterprise’s top capability effects for tactical control. The Low Cost

Conformal Array (LCCA) arose from this requirement.

Described simply, LCCA is a passive planar array that is mounted on the aft section of the submarine sail structure. It integrates with the Acoustic

Rapid Commercial Off-the-Shelf Insertion (A-RCI)

AN/BQQ-10 system to provide greater situational awareness and enhanced collision avoidance, especially in high density (crowded) environments or littoral areas.

Prior to the LCCA, systems did not fully capture all acoustic signatures from threats and/or non-threats.

Close (nearby) tactical awareness was achieved via the

Sail Array, which is bow (forward) facing and captures contacts within an arc of roughly 130 degrees. LCCA is aft (backward) facing and captures contacts within an arc of roughly 230 degrees. Thus, when used in concert with the sail array, LCCA allows for a full

360 degrees of contact coverage.

LwLCCA Installed on OR-Class Sail

In Jan 2008, LCCA was designated as an ACAT - IVT program. Acquisition Decision

Memoranda were signed at Milestone B in Apr 2008, Milestone C in Mar 2009 and the Full Rate

Production Decision Review in Aug 2011.

In the intervening years, LCCA has been proven out as effective, capable and stable technology.

As such, it is highly sought by the Fleet. LCCA’s “popularity” among the Fleet gives rise to the current variant.

LCCA is installed on the 688i and SEAWOLF platforms. This results, in part, from system weight but also from factors unique to these two platforms.

LwLCCA, on the other hand, will cover more (and different) submarine classes. Designed and developed under an engineering change proposal (ECP), the light-weight variant of the LCCA can be installed on the following platforms:

Virginia Class (both in-service and new construction)

Ohio Class (specifically 4 SSGNs and 14 SSBNs that comprise this class) the new Columbia Class (which replaces Ohio Class)

In addition to its wider application (i.e., more submarine classes), LwLCCA also comes at lower cost and allows shorter installation periods.

2.0 APPLICABLE DOCUMENTS

Where documents (cited herein) conflict, the contradiction shall be resolved in accordance with

FAR 52.215-8 – Order of Precedence.

2.1 Department of Defense CIPS

53711-8691985

[Revision most current at time of award of this contract]

Critical Item Product Specification for the AN/BQS 25A Light Weight

Low Cost Conformal Array (LwLCCA) Acoustic Module

53711-8691986

[Revision most current at time of award of this contract]

Critical Item Product Specification for the AN/BQS 25A Light Weight

Low Cost Conformal Array (LwLCCA) Outboard Electronics (OBE)

2.2 Government Standards

SAE GEIA-STD-

0007B

Logistics Product Data 01 May 2013

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

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

MIL-STD-882E System Safety 11 May 2012

MIL-HDBK-470A DoD Handbook: Designing and Developing

Maintainable Products and Systems, Volume 1

31 May 2012

MIL-STD-3018

w/CHANGE 2

Parts Management 02 Jun 2015

MIL-HDBK-781A DoD Handbook for Reliability Test Methods, Plans, and Environments for Engineering, Development

Qualification, and Production

30 Jan 2015

2.3 Other Government Documents

MIL-HDBK-502A DoD Handbook Product Support Analysis 06 Mar 2018

MIL-STD-881D Work Breakdown Structures for Defense Materiel

Items

19 Jun 2018

DoD 5220.22-M National Industry Security Program Operating Manual 28 Feb 2006 https://www.dau.mil/to ols/dag

Defense Acquisition Guidebook (DAG) Current

DON Policy on Digital

Product-Technical

Data

Department of Navy Policy on Digital

Products/Technical Data

23 Oct 2004

Submarine Acoustic Systems Program Office, Sensor

Systems Risk Process Description

12 Oct 2006

SUBMEPP 4730-012-

0629 REV G

Requirements for the Preparation of Submarine

Maintenance Standards

08 Mar 1996

PMS4011/PMS4013 Unique Identification (UID)

Implementation Plan

15 Feb 2007

PMS4011/PMS4013 Configuration Management Plan 16 Jan 2008

PMS4011/PMS4013 Configuration Control Manual 16 Jan 2008

PMS4013 Integrated Logistics Support Plan for the

AN/BQS-25 Low Cost Conformal Array

27 Feb 2009

DoD 4160.28-M Defense Demilitarization Manual 07 Jun 2011

NIST Special

Publication 800-171

Rev. 1

Protecting Controlled Unclassified Information in

Nonfederal Systems and Organizations

Dec 2016;

updated 20 Feb

2.4 Non-Government Standards and Publications

ASME Y14.34-2013 Associated Lists - Engineering Drawing and Related

Documentation Practices

16 May 2014

SAE EIA-748-C Earned Value Management Systems 01 Mar 2013

SAE EIA-632 Processes for Engineering a System 01 Sep 2003

SAE EIA-649-1 Configuration Management Requirements for Defense

Contracts

20 Nov 2014

SAE EIA-836B Configuration Management Data Exchange and

Interoperability

01 Mar 2010 https://www.dau.mil/tools/dag https://www.dau.mil/tools/dag https://www.dau.mil/policy/_layouts/15/WopiFrame.aspx?sourcedoc=/policy/PolicyDocuments/the1398ASN%20(RDA)%20Memo;%20DON%20Policy%20on%20Digital%20Product-Technical%20Data%2023%20Oct%2004.pdf&action=default&DefaultItemOpen=1 https://www.dau.mil/policy/_layouts/15/WopiFrame.aspx?sourcedoc=/policy/PolicyDocuments/the1398ASN%20(RDA)%20Memo;%20DON%20Policy%20on%20Digital%20Product-Technical%20Data%2023%20Oct%2004.pdf&action=default&DefaultItemOpen=1 https://www.dau.mil/policy/_layouts/15/WopiFrame.aspx?sourcedoc=/policy/PolicyDocuments/the1398ASN%20(RDA)%20Memo;%20DON%20Policy%20on%20Digital%20Product-Technical%20Data%2023%20Oct%2004.pdf&action=default&DefaultItemOpen=1

2.5 Availability of Department of Defense Documents

DoD documents are available via the Acquisition Streamlining and Standardization Information

System (ASSIST) at https://quicksearch.dla.mil/qsSearch.aspx.

Non-Government documents -- not listed on the ASSIST website -- can be obtained from the appropriate industry association.

In the event that a document not available from ASSIST or industry sources, the Contractor should make its request (for the document) to the Procuring Contracting Officer.

https://quicksearch.dla.mil/qsSearch.aspx

3.0 General Requirements

The General Requirements contained in this section are applicable to the subject contract in its entirety (i.e., all CLINs as applicable).

3.1 System Engineering Management

The Contractor shall formulate a system engineering plan that clearly and fully meets contractual objectives and requirements. This plan shall also address technical and management aspects. It will be entitled a “Systems Engineering Management Plan” (SEMP). The SEMP shall describe

Contractor’s detailed operational plan for executing systems engineering (CDRL A001).

Processes for Engineering a System guidance (SAE EIA-632) shall be utilized in engineering

LwLCCA systems.

Designing and Developing Maintainable Products & Systems, Vol. 1 (MIL-HDBK-470A, DoD

Handbook) shall be used in building maintainable LwLCCA products and systems.

Engineering Drawing and Related Documentation Practices (ASME Y14.34-2013) shall guide the development of LwLCCA drawing packages.

3.2 System Safety Hazard Analysis

Contractor shall implement and maintain a safety program using MIL-STD-882E. Contractor will provide a System Safety Hazard Analysis (CDRL A002).

3.3 Facility

Contractor shall use a qualified facility for production and testing. Facilities used for storage and inventory management shall meet controlled access requirements.

3.4 Program Planning

Contractor shall manage the program (including, but not limited to, schedule, performance, cost, risk, subcontract(s), vendor(s), technical data, and technical activities) so that the contract is performed (both products and services) in a correct and timely manner, which fully meets contract requirements. Government shall be involved in and have oversight over Contractor’s plan(s). (CDRL A047)

Contractor shall use appropriate program management techniques to maintain program control.

Contractor shall report periodically on progress, status and management.

3.4.1 Post Award Conference

Contractor shall participate in a Post Award Conference (PAC) within sixty (60) days of award.

Typically, a PAC requires several hours; rarely is the PAC a multi-day meeting. The PAC is an opportunity for key stakeholders such as Contractor, PMS4013 and SEA02 to review the contract to ensure mutual understanding and/or clarify any confusion. The location of the Post Award

Conference shall be set by the Government and/or agreed upon by attendees.

3.4.2 Program Management Plan

Contractor shall create and provide a Program Management Plan (CDRL A003).

3.4.3 Subcontractor Management

If subcontractor(s) are used, Contractor shall create and provide a Subcontractor Management

Plan (CDRL A004).

Contractor shall ensure the necessary and appropriate flow of information (e.g., critical specifications, cost/schedule info, reporting requirements) among entities performing (or supporting performance) the subject contract (e.g., subcontractors, vendors, shippers).

Contractor shall (i) coordinate these entities, (ii) address technical concerns related to or arising from them and (iii) monitor and manage their progress (e.g., orders, fulfillment, quality control).

3.4.4 Contract Work Breakdown Structure

Contractor shall develop and maintain a Contract Work Breakdown Structure (CWBS) (CDRL

A005) using MIL-STD-881C as guidance.

The CWBS shall parse work to the level – and in units – sufficient to identify manageable, functional tasks, which reflect how work is actually performed.

Contractor shall correlate these lower (CWBS) elements with:

First Article requirements

LwLCCA Production System requirements

SOW tasks

Integrated Program Management Report (IPMR)

Contract Line Item Numbers (CLINs)

Configuration items

Data items

The CWBS shall comply with MIL-STD-881C. Contactor may use Microsoft Project 2016 (or equivalent commercial software) for the CWBS.

The CWBS shall be a key reference for planning, controlling and reporting progress.

In maintaining the CWBS, any changes Contractor makes thereto must be approved by the

Government.

3.4.5 Earned Value Management System

Contractor shall implement a validated Earned Value Management System (EVMS) in accordance with SAE EIA-748-C.

Contractor shall establish an Integrated Program Management Report process to generate periodic status reports (CDRL A006).

When possible, Contractor will propose measures that may improve contract performance. If

(proposed measure) implemented, Contractor shall report the efficacy of said measure to the

Government (e.g., at a Program Management - Integrated Product Team (PM-IPT) meeting or a

Quarterly Program Review (QPR)).

3.4.6 Critical Path Network

Contractor shall use Critical Path analyses to assess schedule integrity.

Should issues arise on the critical path(s) (e.g., cost, time-to-complete, meeting milestones, timely delivery), Contractor shall propose to the Government its best mitigation or remedial action that can satisfy the contract requirements. Contract administration issues should be raised with the PM-IPT; technical issues should be raised with the Systems Engineering - Integrated

Product Team (SE-IPT).

Contractor is encouraged to responsibly conduct self-evaluations of their EVMS IPMR in partnership with the Government.

3.4.7 Conferences/Meetings

In Quarterly Program Reviews (QPRs), Contractor shall provide (at a minimum) status as to (i) planned and completed efforts, (ii) cost/schedule performance, (iii) technical status, and (iv) risk management. (CDRL A047)

QPRs will be hosted by Contractor and Government alternately unless otherwise agreed upon.

QPRs (and other meetings) may be conducted via teleconference, video teleconference, web meeting, etc., as warranted if authorized by the Government.

Contractor shall use Integrated Product & Process Team(s) (IPPTs) in performing the contract.

Contractor shall participate in periodic PM-IPT and SE-IPT meetings. These meetings can occur in-person or via teleconference at the Government’s discretion. If tasked via Technical

Instruction, Contractor shall participate in meetings with other IPTs and/or Work Groups, which relate to or support the subject contract.

Meeting materials can include, but are not limited to, agendas, minutes, presentation material, summaries (of discussion), decisions reached and/or agreements made, attendee list, action items and any other items useful in accomplishing the meeting(s) objective. (CDRL A045 and

A046)

Said materials pertain to all meetings (not merely QPRs & IPTs).

3.5 Quality Management System

Contractor shall maintain a Quality Management System in accordance with ANSI/ISO/ASQ

Q9001-2008.

3.6 Risk Management

Contractor shall implement a comprehensive risk management process to systematically identify, mitigate or resolve risks to the overall program. Contractor should review the PMS401 Sensor

Systems Risk Process Description (Oct 2006).

3.7 Data Management

Contractor shall manage data used for, or generated during, the performance of the subject contract. Contractor shall deliver data and/or data products (both unclassified and classified) in compliance with (a) Memorandum for Distribution: DON Policy on Digital Products/Technical

Data and (b) DoD 5220.22-M National Industrial Security Program (NISPOM)

3.8 Security Requirements

3.8.1 Facility Clearance and Safeguarding Requirements

The subject contract requires an active SECRET Facility Clearance (FCL) in accordance with the

DD254. Contractor must have a Safeguarding Level of SECRET.

3.8.2 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s)

(SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense

Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government’s review of the SSPs at the

Contractor’s facility.

If the Government determines that the SSP(s) does not adequately implement the requirements of

DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30 days’ notice to the Contractor.

3.8.3 Compliance to NIST 800-171

The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1)

(NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and

POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) – Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

a. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

b. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a

POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program

Manager for risk to the program.

https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program

3.8.4 Cyber Incident Response

The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the

72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes

Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Media.docx. In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

If the Contractor subsequently identifies any such data not previously delivered to DC3, then the

Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

3.8.5 Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

3.8.6 NCIS/Industry Monitoring

In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative

Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor’s infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor’s information systems or information technology assets.

The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractors.

http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Media.docx

In all cases, the collection or provision of data and any activities associated with this clause shall be in accordance with federal, state, and non-US law.

3.9 Logistics

The Integrated Logistics Support (ILS) team shall include PMS4013-supported Logistics and

Contractor Logistics personnel. Other participants can be included on an ad hoc basis when necessary or useful. The ILS team shall develop and maintain a LwLCCA Life Cycle

Sustainment Plan once it receives requisite data collected from/during actual performance of the subject contract.

3.9.1 Logistics Guidance Conference

Contractor and Government shall conduct a Logistics Guidance Conference within 120 days of award. This conference shall discuss Integrated Design Documentation (IDD), the Interface

Requirements Specification (IRS) and other relevant data requirements. The Logistics Guidance

Conference shall be supported and/or documented as necessary in accordance with §3.4.6

(above).

3.9.2 Logistics Provisioning Conference

Within ninety (90) days of beginning full-rate production, Contractor shall participate in the

Provisioning Conference. This conference will include (Logistics) representatives from

PMS4013, Contractor, Submarine Maintenance Engineering, Planning and Procurement

(SUBMEPP), Naval Supply Systems Command (NAVSUP) and the designated In-service

Engineering Agent (ISEA). Other participants can be included on an ad hoc basis if necessary or useful.

3.9.3 Integrated Logistics Working Group Meetings

Contractor shall participate in quarterly Integrated Logistics Working Group (ILWG) meetings until Logistics planning and associated/resultant work products are complete. Once complete, ILWG can be scheduled on an ad hoc basis. Said meetings shall be supported and/or documented as necessary in accordance with §3.4.6 (above).

Contractor shall use its Integrated Logistics Support Plan (and other relevant materials) to identify and recommend (to the Government) any possible commonality(ies) among logistic support structures for Navy Hull Sensor Systems, which may decrease life-cycle cost.

3.10 Supportability Analysis Program

Contractor shall participate in the Supportability Analysis Program with the program objective of minimizing cost. The program shall include a Supportability Analysis database of (i) standard data for all LwLCCA items, (ii) existing failure data, and (iii) analyses from comparable systems.

Upon request, data from the Supportability Analysis database will be provided to the

Government in the format/media/method specified by the Government.

3.11 Supply Support

Contractor shall implement an Item Unique Identification (IUID) program and Marking Plan

(CDRL A007). Contractor shall provide an IUID Marking Activity, Validation & Verification

Report (CDRL A008). CDRLs A007 and A008 shall comply with (a) MIL-STD-130N and (b)

PMS4011/PMS4013’s Unique Identification (UID) Implementation Plan.

Marking for packaging, shipping, and storage of LwLCCA deliverables shall comply with MIL-

STD-129R. Management of parts shall comply with MIL-STD-3018.

Contractor shall maintain a continuous Bill of Materials (BOM) for Diminishing Manufacturing

Sources and Material Shortages Management (DMS/MS) (CDRL A009). Contractor shall review for obsolescence regularly and inform the Government if/when obsolescence issues arise.

The Contractor shall participate in the Government/Industry Data Exchange Program (CDRLs

A010 & A011).

3.12 Demilitarization and Disposal

Contractor shall establish a Demilitarization and Disposal Plan (CDRL A012) per DoD 4160.28-

M that addresses the (i) salvage of precious metals, (ii) safe recapture or disposal of hazardous materials, and (iii) minimization of landfill use via increased recycling.

3.13 Cybersecurity – Protecting Information in Nonfederal Systems & Organizations

Contractor shall protect the Government information (or Government-related information) created, received, sent, used or otherwise related to the subject contract and/or performance thereof.

For direction and/or guidance, Contractor shall rely upon NIST Special Publication 800-171 Rev.

1, entitled Protecting Controlled Unclassified Information in Nonfederal Systems and

Organizations (dated Dec 2016; updated 20 Feb 2018). This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171r1.

https://doi.org/10.6028/NIST.SP.800-171r1

4.0 FIRST ARTICLE

Anything developed under § 4.0 First Article (e.g., test equipment, specifications, procedures, plans, report templates) should be used on Production Systems as appropriate.

The Government retains the right to waive -- in its entirety or in select part(s) -- this section if so doing benefits the Government/Navy/Fleet and/or streamlines performance of the subject contract.

4.1 First Article Hardware

As the First Article, Contractor shall provide the following hardware (exactly):

6 acoustic modules (comprising one full column)

1 Outboard Electronics (OBE)

1 Hybrid (fiber and power) Cable (1-into-6 split) (running from Array to OBE)

1 fiber optic cable (running from OBE to Penetrator)

1 power cable and clock (running from OBE to Penetrator)

Contractor shall undertake and/or provide all necessary manufacturing, facilities, materials, equipment and professional services (management, engineering, logistical, etc.) required to provide a LwLCCA First Article, which meets all contractual requirements as specified in the two LwLCCA CIPS (attachments 3 and 4).

4.2 Specification Requirement Verification

Contractor shall generate a Specification/Requirement Verification Matrix (SRVM) (CDRL

A013) defining (a) the methodology used for verifications and (b) the degree to which each requirement is met. Requirements are defined in the LwLCCA CIPS (Attachments 3 and 4).

4.3 Testing

Contractor shall build and test Test Equipment (CDRL A014) capable of testing, at a minimum, the First Article.

Contractor shall provide the Test Set Specification (CDRL A015) and User Manual (CDRL

A016).

Contractor shall submit a Test Plan (CDRL A017) to the Government. Contractor shall not conduct any First Article testing until Government has approved the submitted Test Plan. The

Test Plan shall describe (at a minimum) all testing, step-by-step procedures, qualification and inspection criteria, and the test schedule.

Contractor shall conduct a Test Readiness Review no more than thirty (30) days prior to testing.

Contractor shall test and inspect LwLCCA First Article in accordance with CIPS (Attachments 3 and 4).

For testing and inspection, Contractor can use its facilities or any acceptable commercial or

Government laboratory that has been approved by the Government (PMS4013).

The Government reserves the right to (a) observe First Article testing and/or (b) conduct any special testing that it deems necessary to verify compliance with either or both CIPS.

Fourteen (14) days prior to any test event, Contractor shall notify the appropriate Government representative in writing (electronic mail suffices) that said test will occur.

Upon completion of First Article testing, Contractor shall prepare a Test Report (CDRL A018) that -- at a minimum -- details the acceptance/rejection criteria for each test or inspection performed. The Test Report shall also contain photos and/or sketches of the test set up and document actual test results for each tested system, component, or unit identifiable via specific and complete serial number.

Upon Government request, Contractor shall provide a Summary of said Test Report (CDRL

A019). The purpose and intent here is to provide the Government some latitude in (a) how much test data and (b) what specific data subsets it receives and must review. Testing is thorough and test results often voluminous. In the event that 100 tests were performed but the Government needs to review closely only 7 of the 100 tests to vet a particular requirement or subpart thereof, this Summary CDRL will permit an acutely focused review.

4.4 Failure Analysis and Corrective Action System (FRACAS)

Contractor shall maintain a closed-loop failure analysis system for use as, or in support of, the

Failure Reporting, Analysis & Corrective Action System (FRACAS) (CDRL A020). FRACAS shall include – at a minimum -- cause(s) of failure and corrective action(s) taken.

5.0 LwLCCA PRODUCTION

The Light-weight Low Cost Conformal Array system – its components and subcomponents, its production, installation and repair – represent the latest (or current) step in an iterative process spanning multiple years and contracts, with input and documentation from multiple stakeholders.

As such, it is not surprising that some confusion as to nomenclature has arisen over time. The same cable may be called one thing in the SOW and another thing in the CIPS. An “array” may mean a full system in one document but something less than a full system elsewhere.

In an attempt to minimize confusion, we list and explain all the nomenclature currently in use when describing LwLCCA.

A full LwLCCA System is composed of two (2) arrays – one of which is installed port-side; the other installed on the starboard side.

A full LwLCCA System is also referred to as a Shipset in some documentation.

An array (one half of a shipset) is sometimes called a Side Array Unit (SAU) (e.g., in the

Critical Item Production Specification (CIPS)). The components that compose an Array are described in §5.1 below. The §5.1 diagram illustrated a full LwLCCA system.

The 1-to-6 split cables, which run from Array to OBE, are sometimes referred to as

Acoustic Module Interface Cables and/or Acoustic Module Interface Cable Assembly

(short-form “AMIC” for both). Alternatively, this same cable is sometimes simply referred to as an Array Cable.

A Fiber Optic cable (running from OBE to Penetrator) is sometimes referred to as a

Telemetry Cable.

A Copper cable (running from OBE to Penetrator) is sometimes referred to as Power

Cable or Power/Command/Clock cable.

The LwLCCA Optical/Electrical Hull Fitting is more commonly referred to as a Hull

Penetrator or simply a penetrator. It should be noted that penetrators are NOT part of the subject contract. Penetrators are procured and produced via separate contract and provided as GFE by PMS4013.

5.1 Hardware

A Light-weight, Low Cost Conformal Array (LwLCCA) is composed of the following hardware

(precisely):

30 Acoustic Modules

(AMs)

1 Outboard Electronics

(OBE)

1 Hull Penetrator

5 Cables (1 input splitting to 6 outputs, which runs from OBE to

Array)

2 Fiber Optic cables

(running from OBE to

Penetrator)

2 Power Cables (running from OBE to Penetrator)

The components listed above comprise a single, complete lightweight Array. In some technical documentation (e.g., LwLCCA CIPS), a single Array is also known as a Side Array

Unit (SAU).

Spares are procured at the unit level in any quantity the Government specifies based upon need, budget, stability when deployed to the Fleet, etc. The elemental units are:

AM

OBE

AMIC Cable (1 input splitting to 6 outputs) cable (aka AMIC)

Fiber Optic cable

Power cable

Contractor shall build, test, and deliver LwLCCA Shipsets, in accordance with the two LwLCCA

CIPS (Attachments 3 and 4).

Contractor shall provide a Cable Assembly Design for cables that run from OBE to penetrator

(i.e., for the two fiber optic and two power cables). This design is developed with Government input and approval. Contractor shall include the requisite power and fiber optic cables with each delivered shipset. Contractor shall ensure that cables for telemetry and power properly connect to both OBEs and Penetrators.

Contractor shall provide an Array Interface Cable Design for the Hybrid Cables (or AMICs) that run from OBE to Array. This design is developed with Government input and approval.

Contractor shall include the requisite Hybrid Cables (or AMICs) with each delivered shipset.

All cables shall be designed and constructed to comply fully with the LwLCCA CIPS.

Contractor shall provide periodic production progress reports on LwLCCA efforts (CDRL

A021).

5.2 Integrated Baseline Review

Contractor shall participate in an Integrated Baseline Review (IBR) no later than 90 days after the start of LwLCCA production (CDRL A022). The IBR will verify the reliability of the performance measurement baseline. It should (i) include the entire scope of work, (ii) comply fully and reliably with schedule requirements, (iii) verify adequate resources are assigned/allocated and (iv) identify inherent risks.

5.3 Test, Acceptance, and Evaluation

LwLCCA production test procedures shall incorporate procedures developed for First Article acceptance testing whenever possible (CDRL A023). The procedures shall establish acceptance and/or rejection criteria for production tests and inspections, which ensure that all hardware meets the requirements and/or physical and functional baselines contained in the CIPS.

Contractor shall ensure that the supplies and services it provides conform to technical and contractual requirements. Contractor shall make all test results/reports and supporting documentation available to the Government upon request.

Contractor shall notify the Government of faults or failures that occur during Factory Acceptance

Testing (FAT). Notification is made via email sent to the Contracting Officer’s Representative

(COR) and the Technical Direction Agent (TDA). Said notice shall be provided within eight (8) hours of the fault/failure being observed. Contractor shall produce a FAT Completion Report.

Within ten (10) days of completing FAT, Contractor shall provide a preview (or “quick-look”) report. This report shall contain any notable outcomes of the FAT.

Within thirty (30) days of completing Factory Acceptance Testing, Contractor shall submit its full and final FAT report. (CDRL A024).

5.4 Configuration Audits

Contractor shall provide the facilities, personnel and documentation necessary to support configuration audits. Audits are conducted by the Government and Contractor jointly.

Contractor shall create a Configuration Audit Plan that complies with SAE EIA-649-1 and SAE

EIA-836B (CDRL A025). The plan shall include, but is not limited to, an agenda, audit procedure and/or steps and all data required for each audit.

There are two distinct but interdependent audits; one allows the other to be done.

5.4.1 Functional Configuration Audit

The first audit is a Functional Configuration Audit (FCA) during which all relevant drawings and bills of material (BOMs) are reviewed. By reviewing them, the FCA verifies that any LwLCCA system (built from these materials and built to the applicable drawing) will fully meet the functional requirements as detailed in the CIPS.

Contractor shall provide the relevant drawings and BOMs to the Government. Contractor shall submit drawings and BOMs at least sixty (60) days prior to the scheduled Physical Configuration

Audit.

Within thirty (30) days of completing FCA, Contractor shall prepare a summary of Outcomes and Findings and provide it to the Government (CDRL A026).

5.4.2 Physical Configuration Audit

Government and Contractor can now proceed to the second audit, a Physical Configuration Audit

(PCA). During the PCA, the verified documentation yielded by the FCA is used to verify that actual (physical) production of LwLCCA systems is compliant. I.e., having verified what parts and materials are required (via the verified BOM) and how they are to be assembled (via the verified drawings), auditors now verify that actual production complies with both.

The PCA shall be undertaken by the Government and Contractor jointly. It shall occur at

Contractor’s manufacturing facility and begin no later than 180 days after the start of production.

The “start of production” is the date on which CLIN 0001 “LwLCCA PRODUCTION

SHIPSET” is exercised, or if first article is required CLIN 0101.

Audits may be performed on hardware in different stages of fabrication so long as doing so permits a full and correct verification of said hardware.

Upon completion, Contractor shall summarize the audit findings and results and submit them to the Government (CDRL A027).

5.5 Baseline Update

Once the PCA has been completed and approved by the Government, Contractor shall resubmit the LwLCCA Product Baseline, updated and revised to reflect all changes. The Contractor shall submit revisions to the LwLCCA Baseline Report that reflect every change made to the baseline during fabrication and tests of the LwLCCA (CDRL A022).

5.5.1 Update Drawings/Models & Associated Lists

Contractor shall deliver revised drawings, etc., whenever changes are made to the LwLCCA

Product Baseline (CDRL A028).

Contractor shall identify, document, and (where possible) correct production issues, which might impact cost or performance. The Government shall be notified of all such issues as soon as reasonably possible.

5.5.2 Product Baseline Configuration Control

Once the LwLCCA Product Baseline is established, the Government has responsibility for configuration control during production of LwLCCA. Configuration will utilize the PMS4013

Configuration Management Plan and the PMS4013 Configuration Control Manual.

Contractor shall develop and/or revise drawings and update Baseline reports to document all changes (CDRLs A022 and A028). Changes shall result from Government-approved

Engineering Change Proposals (ECPs).

5.5.3 Non-compliant Hardware

Prior to the build or delivery of hardware that does not comply fully with the product baseline, Contractor must submit a Request for Variance (CDRL A029) for Government review and authorization.

5.6 Failure Analysis and Corrective Action

The Contractor shall maintain a closed loop failure analysis system and generate a Failure

Analysis and Corrective Action Report (FACAR) (CDRL A030) for the LwLCCA, including, but not limited to failure causes and corrective action.

5.7 Array Interface Requirements

Contractor shall develop a LwLCCA Interface Requirements Specification (IRS) that identifies the telemetry and power requirements for the OBE to the inboard SONAR system. This IRS shall include, but is not limited to, telemetry description, cable and connector wiring diagrams, and power requirements (CDRL A031).

The Contractor shall develop an array Interface Design Description (IDD) that describes the physical interface between the inboard and outboard equipment on the LwLCCA shipset. This

IDD shall include, but is not limited to, installation design, required installation hardware, cable management plan, and LwLCCA component locations for all shipset components (CDRL

A032).

5.8 Supportability Analyses Database

The Contractor shall establish and maintain the Supportability Analyses database for the

LwLCCA using SAE GEIA-STD-0007B and MIL-HDBK-502A as guidance (CDRL A033).

The Supportability Analyses database shall support acquisition logistics planning, level of repair and reliability-centered maintenance decisions, program tradeoffs, and the formation of contract provisions.

The cornerstone of the Supportability Analyses database shall be the Bill of Materials listing for the LwLCCA and LwLCCA Test Set. In addition to Contractor drawings, vendor drawing numbers and part numbers for all purchased parts shall be identified on the Bill of Materials.

The Contractor shall utilize a reference designator structure for the Supportability Analyses database that represents a top down breakdown of the system into its functional systems, subsystems, components, assemblies and parts. All Lowest Replaceable Units and Maintenance

Significant Items within the Lowest Replaceable Units shall be separately identified in the

Supportability Analyses database.

In addition to the data elements contained on the Bill of Materials, the following Supportability

Analyses data elements, if applicable, shall be stored and maintained in the Supportability

Analyses database:

Supply support – Lowest Replaceable Units (LRUs)

- Reference number (part number)

- Manufacturer, Contractor and Government Entity (CAGE) code

- Item name (part name)

- Technical Replacement Factor (TRF)

- Quantity per assembly

- Quantity per end item

- Source, Maintenance and Recoverability (SM&R) Code

- Minimum Replacement Unit (MRU)

- Unit of Issue (UI) Price

- Production Lead Time (PLT)

- Manufacturer Name

- Shelf Life

- Shelf Life Action

- Precious Metal Indicator Code (PMIC)

System/end item operations and maintenance requirements

- End item acronym code

- End item reference designator

- End item indenture code

- End item name

- End item part number

- Technical Manual (TM) number

- Required maximum time to repair

- Required mean time to repair (MTTR)

- Required mean time between failure (MTBF)

Item reliability and maintainability data (LRUs)

- Reference designator

- Indenture code

- Part number

- Item drawing number

- Item drawing number revision

- Item name

- Technical Manual (TM) number

- Lowest replaceable unit (LRU)

- Item function

- Maintenance concept

- Technical Replacement Factor (TRF)

- Repair cycle time (RCT)

- MTBF Maintenance action code (MAC)

Task analysis and support equipment (LRUs)

- Reference designator

- Indenture code

- Maintenance action code (MAC)

- Task identification

- Measured mean elapsed time

- Predicted mean elapsed time

- Task requirement reference designator

- Task type, Preventative (P), Corrective (C), or Operation (0)

- Means of detection

- Task support equipment

- Task support equipment item quantity

- Task support equipment full item name

Supply support (Information to be provided by the Government) (LRUs)

- National Stock Number (NSN)

- Unit of Issue (UI)

- Logistics Review Code

- Repair Return Mode

- Cog Symbol

- Material Control Code (MCC)

- Special Maintenance Item Code (SMIC)

- Item Name

- Controlled Item Inventory Code (CIIC)

- Hazardous Material Item Code (HMIC)

- Quantity per Unit Pack (QPA)

- Type of Storage

- Federal Supply Classification (FSC)

- Issue Restriction Code

- Special Material Classification Code (SMCC)

- Demilitarization Code

- MOE Rule

- Movement Priority Designator

- Designated Overhaul Point Cage

- Repair Survival Rate (RSR)

- Remain in Place code (RIP)

- Additional Designated Overhaul Point Cage(s)

- Material Manager

Contractor shall generate the following Supportability Analyses database technical reports:

Depot Repair Material List (CDRL A034)

Intermediate Maintenance Activity Spares & Consumables List

Installation and Checkout List (CDRL A035)

Special Purpose Support & Test Equipment List

Contractor shall develop and maintain a Critical Items List (CDRL A036). It shall include (at a minimum:

single point of failure items, Maintenance Significant Items long lead time procurement items market conditions special order items

The Critical Items List shall be maintained within the Supportability Analyses database.

After the LwLCCA Product Baseline is established, and Supportability Analyses Database technical reports (CDRLs A034 and A035) and the Critical Items List (CDRL A036) are approved by the Government, Contractor shall deliver the Supportability Analyses Database

(reflecting the approved Product Baseline) in its native electronic format. CDRL A033).

5.9 Supply Support

Contractor shall deliver 2F COG NSN data for the LwLCCA and Spare components. Contractor shall participate in Integrated Logistics Support activities, including, but not limited to, provisioning and demilitarization activities.

The Provisioning Technical Documentation submissions (CDRL A037) for the LwLCCA and spare components shall include the following Contractor and/or Government Furnished

Provisioning Technical Documentation data elements:

NIIN or NICN [Government Furnished Information (GFI)]

Part Number [Contractor Furnished Information (CFI)]

Part Description [Name] [CFI]

Manufacturer Name [CFI]

Manufacturer CAGE [CFI]

Unit Price [CFI] PTD for Interim Support Items List

Shelf Life Action [CFI]

Precious Metal Indicator Code [CFI]

NSN [GFI]

Local Routing Code [GFI]

Repair Price [CFI]

RPR MOD (Repair Maintenance Overhaul Designator) [GFI]

Repair Return Mode [GFI]

Cog Symbol [GFI]

Material Control Code [GFI]

Special Maintenance Item Code [GFI]

Item Name (GFI]

Shelf Life [CFI]

Shelf Life Action [CFI]

Controlled Item Inventory Code [GFI]

Type of Storage [GFI]

Federal Supply Classification [GFI]

Issue Restriction Code [GFI]

Special Material Content Code [GFI]

Demilitarization Code [GFI]

MOE Rule [GFI]

Movement Priority Designator [GFT]

Designated Overhaul Point CAGE [GFI]

Additional Designated Overhaul Point CAGE(s) [GFI]

Material Manager [GFI]

Acquisition Method Code [CFI]

Acquisition Method Suffix Code [CFI]

Production Lead Time [CFI]

5.10 Technical Manual Source Data

Contractor shall develop Technical Manual Source Data in accordance with the LwLCCA

Technical Manual Contract Requirement (CDRL A038). Contractor shall ensure that the

LwLCCA Technical Manual Source Data includes descriptive, functional, operational, and maintenance information necessary to provide a complete description of LwLCCA.

5.11 Maintenance and Repair Procedures

Contractor shall develop maintenance and repair procedures for Arrays, OBEs, and Cables

(CDRL A039). SUBMEPP 4730-012-0629 Rev G shall be used as guidance in developing maintenance and repair procedure content for Intermediate-Level and Depot-Level maintenance and repairs.

6.0 ENGINEERING SERVICES

If required, Contractor shall provide post-delivery engineering services as instructed via

Technical Instruction(s). Said services may include, but are not limited to, Program

Management, Engineering & Technical Support,…