N00024-20-R-5231 Draft RFP 6.22.20.pdf

DRAFT SOLICITATION N00024-20-R-5231

SECTIONS B, C

22 JUNE 2020

N0002420R5231

DRAFT 22 JUNE 2020

Section B - Supplies or Services and Prices

SECTION B NOTES

NOTE A – Option item to which the option clause in SECTION I applies and which is to be supplied only if and to the extent said option is exercised.

NOTE B – The Government will establish the price for this item at award based on the configuration of AN/WSN- 12 required. The price shall be based on the pricing set forth in the following table.

First Article Unit Price Table

AN/WSN-12 V(1) Surface (CLIN 0002AA) AN/WSN-12 V(2) Submarine (CLIN 0002AB)

*Offeror to complete

NOTE C – Option pricing for this item shall be established at option exercise based on the quantity and configuration of the units exercised by the Government as set forth in the following stepladder unit price table. The price shall be determined as follows:

The Government will determine the total number of units (including all configurations) to be included in the option exercise, and identify the applicable quantity in the Cumulative Quantity row of the stepladder unit price table. For example, if an option exercise includes three Surface configuration units, two Submarine configuration units, and two MAM kits, then each configuration will be priced at the unit prices listed in the row of the unit price table corresponding to a cumulative quantity of seven units (3 + 2 + 2 = 7).

The Government will price each AN/WSN-12 V(1) Surface configuration unit at the amount shown in the AN/WSN-12 V(1) Surface column for the row identified in step (1) above. The Government will price each AN/WSN-12 V(2) Submarine configuration unit at the amount shown in the AN/WSN-12 V(2) Submarine column for the row identified in step (1) above. The Government will price each MAM Kit at the amount shown in the MAM kit column for the row identified in step (1) above. The Government will price each ISM at the amount shown in the ISM column for the row identified in step (1) above.

Base Year

Cumulative Quantity

AN/WSN-12

V(1) Surface

(CLIN 0100)

AN/WSN-12

V(2) Submarine

(CLIN 0200)

Maintenance Assistance Modules

(MAM) kit

(CLIN 0300)

Inertial Sensor Module (ISM)

Surface

(CLIN 0400)

Inertial Sensor Module (ISM)

Submarine

(CLIN 0500)

1-2

3-5

6-9

10-15

Option Year 1

Quantity

AN/WSN-12

V(1) Surface

(CLIN 1100)

AN/WSN-12

V(2) Submarine

(CLIN 1200)

Maintenance Assistance Modules

(MAM) kit

(CLIN 1300)

Inertial Sensor Module (ISM)

Surface

(CLIN 1400)

Inertial Sensor Module (ISM)

Submarine

(CLIN 1500)

1-2

3-5

6-9

10-15

Option Year 2

Quantity

AN/WSN-12

V(1) Surface

(CLIN 2100)

AN/WSN-12

V(2) Submarine

(CLIN 2200)

Maintenance Assistance Modules

(MAM) kit

(CLIN 2300)

Inertial Sensor Module (ISM)

Surface

(CLIN 2400)

Inertial Sensor Module (ISM)

Submarine

(CLIN 2500)

1-2

3-5

6-9

10-15

Option Year 3

Quantity

AN/WSN-12

V(1) Surface

(CLIN 3100)

AN/WSN-12

V(2) Submarine

(CLIN 3200)

Maintenance Assistance Modules

(MAM) kit

(CLIN 3300)

Inertial Sensor Module (ISM)

Surface

(CLIN 3400)

Inertial Sensor Module (ISM)

Submarine

(CLIN 3500)

1-2

3-5

6-9

10-15

Option Year 4

Quantity

AN/WSN-12

V(1) Surface

(CLIN 4100)

AN/WSN-12

V(2) Submarine

(CLIN 4200)

Maintenance Assistance

Modules (MAM) kit

(CLIN 4300)

Inertial Sensor Module (ISM)

Surface

(CLIN 4400)

Inertial Sensor Module

(ISM)

Submarine

(CLIN 4500)

1-2

3-5

6-9

10-15

*Offeror to complete

The Government reserves the right to unilaterally exercise this option multiple times to increase the quantity under this item. The quantity may be increased by any increment as long as the total cumulative quantity does not exceed a maximum quantity of twelve (12) units per ordering year. If an additional option exercise to increase the quantity occurs within 90 days of other quantities exercised within the same ordering year, then pricing for all units for that ordering year procured within this 90 day period shall be adjusted to the unit price from the stepladder pricing appropriate for the total quantity being procured within the 90 day period. For quantity increases not occurring within 90 days of another option exercise in the same ordering year, the Government shall use unit pricing from the stepladder pricing applicable only to the quantity of units added, and the pricing of previously awarded quantities under the applicable line item will not change.

CLAUSES INCORPORATED BY FULL TEXT

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

Labor CLIN Labor Hours Cost Per Hour* Fee Rate Per Hour* Loaded Hourly Rate

0700 10,000

1700 10,000

2700 10,000

3700 10,000

4700 10,000

*The offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

(End of Text)

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (NAVSEA) (OCT

2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Section C - Descriptions and Specifications

Statement of Work

1.0 Scope

This Statement of Work (SOW) defines the efforts required for manufacture, assembly, and testing of the AN/WSN- 12 Inertial Navigation System (INS). The assembly is defined by the Technical Data Package (TDP), and the system performance requirements are specified in the System Requirement Document (SRD). The Contractor shall possess and maintain a facility clearance of SECRET per the contract DD Form 254. The Contractor’s obligation to perform this contract is in no way conditioned upon the Government provision of any facilities, material, property, equipment, services, or information, except as expressly provided herein.

1.1 Background

Navigation systems work together to provide Positioning, Navigation, and Timing (PNT) data to support safe navigation, ship control, weapons employment, aircraft launch and recovery, and 3-axis stabilization data to communication antennas, shipboard sensors, radars, and combat systems for mission execution. The AN/WSN-12 is the United States Navy’s (USN) next generation INS and an integral PNT component providing sustained and consistent geographic position and precise time references for safety of navigation, communications, and weapons command and control. The AN/WSN-12 provides a self-contained PNT capability that is resistant to jamming and deception efforts. Accurate velocity, altitude, and position data are provided to weapons systems and missiles, such as the Tomahawk Land Attack Missile (TLAM), Ballistic Missile Defense (BMD), and other onboard navigation and charting systems. PNT from external sources such as Global Positioning System (GPS) may not be available or operationally degraded by hostile actors; however, the INS aids in ensuring the integrity of the navigation data and weapon system readiness.

2.0 Applicable Documents

The following documents, of the exact issue shown, form a part of the SOW to the extent specified herein. In the event of a conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall take precedence.

2.1 AN/WSN-12 Applicable Documentation

PEO IWS6 CMP Configuration Management Plan 08 September 2014

PEO IWS6 RMP Risk Management Plan, Rev 5 November 2014

PEO IWS6 DMSMS Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

28 June 2018

PEO IWS6 IUID Item Unique Identification (IUID) Implementation Plan 05 February 2019

PEO IWS6 SCG System of Systems (SoS) Security Classification Guide

(SCG)

XX XXX 2020

2.2 Joint Chiefs of Staff, Department of Defense (DoD) and DoD Services Documents DODD 5000.04-M-1 Cost and Software Data Reporting (CSDR) Manual 04 November 2011

DoD 5220.22-M National Industrial Security Program Operating Manual

(NISPOM)

18 May 2016

OPNAVINST 5513.1F Department of the Navy Security Classification Guide 07 December 2005

DoDI 8500.01 Cybersecurity 14 March 2014

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology

12 March 2014

2.3 Military Standards (MIL-STD)

MIL-HDBK 61A Configuration Management Guidance 07 February 2001

MIL-STD-31000 Department of Defense Standard Practice: Technical Data Packages

05 November 2009

MIL-STD-31000 Department of Defense Standard Practice: Technical Data Packages – Option Selection Worksheet

MIL-STD-130N Department of Defense Standard Practice: Identification Marking of U.S. Military Property

07 December 2007

MIL-STD-740-2 Military Standard: Structure-borne Vibratory Acceleration Measurements and Acceptance Criteria of Shipboard Equipment

30 December 1986

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

MIL-STD-881C Work Breakdown Structures for Defense Material Items 03 October 2011

MIL-STD-882E DoD Standard Practice for System Safety 11 May 2012

2.4 Handbooks

EIA/IS-632 IA Standard: Processes for Engineering a System 07 January 1999

MIL-HDBK-781A Reliability Test Methods, Plans, and Environments for Engineering Developing, Qualification, and Production

01 April 1996

IEEE 1220 IEEE Standard for Application and Management of the Systems Engineering Process

09 September 2005

MIL-HDBK-29612-1A

NOT 2

Guidance for Acquisition of Training Data Products and Services (Part 1 of 5)

20 June 2011

NIST SP 800-171 REV 2 Safeguarding Covered Defense Information and Cyber Incident Reporting, and National Institute of Standards and Technology (NIST)

21 February 2020

SAE AS5553 SAE International Standards AS5553 and AS5553A Counterfeit Electronic Parts; Avoidance, Detection, Mitigation and Disposition

April 2009

MIL-HDBK-470A NOT

Design and develop Maintainable Products and Systems 31 May 2012

MIL-HDBK-61A Configuration Management Guidance 08 September 2014

3.0 Requirements

3.1 General

This SOW outlines the requirements and approach for AN/WSN-12 development, production, integration, testing, demonstration, product support, and systems engineering to deliver AN/WSN-12 First Article Units and AN/WSN- 12 Production Systems, engineering services, and provisioning items.

Security requirements applicable to the contract may be found in the Contract Security Classification Specifications, DD Form 254, Attachment J-1, and the AN/WSN-12 Security Classification Guide.

3.2 Detailed Tasks: Program Management and Control (All CLINs)

3.2.1 Program Management Office

The Contractor shall establish a program management office that is responsible for the management and control of all program elements in order to support the successful on-time delivery of the contract requirements. The Contractor shall organize, coordinate, and control all internal project activities (including those of Subcontractors) to ensure the correct and timely delivery of all supplies and services required under this contract. The Contractor shall provide the Status of Government Furnished Equipment Report. The Contractor shall identify any internal data which is generated by the Contractor during performance of this contract.

CDRL A001 – GOVERNMENT FURNISHED EQUIPMENT (GFE) REPORT

CDRL A002 – DATA ACCESSION LIST

3.2.2 Program Management Plan

The Contractor shall perform program management functions to ensure all the requirements in the SOW are executed and shall deliver a program management plan.

CDRL A003 – PROGRAM MANAGEMENT PLAN

3.2.3 Risk Management

The Contractor shall develop, implement, and maintain a Contractor’s Risk Management Plan that meets the requirements of the Program Executive Office (PEO) Integrated Warfare Systems (IWS) 6.0 Risk Management Plan, provided as Government Furnished Information (GFI) and includes a process that identifies, evaluates, and mitigates program risks including technical environmental, safety, cost, and schedule components.

CDRL A004 – CONTRACTOR’S RISK MANAGEMENT PLAN

3.2.4 Cost and Software Data Reporting

The Contractor shall establish, maintain, and use in the performance of this contract a Cost and Software Data Reporting (CSDR) system designed to systematically collect and report actual contract costs to provide Department of Defense (DoD) cost analysts with the data necessary to estimate future program costs. The Contractor’s system and reports shall be in accordance with this SOW, the CSDR Manual dated 4 November 2011, Cost Data Summary Report (DD Form 1921), Functional Cost-Hour Report (DD Form 1921-1), and Progress Curve Report (DD Form 1921-2).

The Contractor shall provide access to all records and data requested by the Contracting Officer for the purpose of permitting Government surveillance to ensure continuing application of the CSDR to this contract.

The Contractor shall prepare and submit Contractor Cost Data Reports (CCDR) in accordance with Cost Data Summary Report (DD Form 1921), Functional Cost-Hour Report (DD Form 1921-1), and Progress Curve Report (DD Form 1921-2). These reports shall be aligned and traceable to each Contract Work Breakdown Structure (CWBS) element as identified in the CSDR Manual provided as GFI. This reporting shall apply to all costs incurred against this contract. Separate DD Form 1921 (Cost Data Summary Report), DD Form 1921-1 (Functional Cost-Hour), and DD Form 1921-2 (Progress Curve) reports shall not be required for different appropriations (e.g. Other Procurement, Navy (OPN), Shipbuilding and Conversion, Navy (SCN). Costs of all reporting CWBS elements, as identified in the CSDR Plan, shall be segregated into Non-Recurring and Recurring Cost.

In conjunction with these CCDR requirements, the Contractor shall update the existing CWBS dictionary and resubmit to the Government in accordance with the CWBS.

The Contractor shall flow down CCDR requirements to any lower tier Contractor with a subcontract supporting this contract valued at over $50 million. The Contractor shall also flow down CCDR requirements to any contracts valued at between $7 million and $50 million that are designated by the DoD program office at the time of contract award as being high risk, high value, or high technical interest.

CDRL A005 – COST DATA SUMMARY REPORT (DD FORM 1921)

CDRL A006 – FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-1)

CDRL A007 – PROGRESS CURVE REPORT (DD FORM 1921-2)

CDRL A008 – CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)

3.2.5 Meetings

The Contractor shall coordinate, schedule, prepare, conduct, facilitate and participate in reviews, meetings and conferences specified and complete reports, records of meetings/minutes and presentation material. The Government reserves the right to attend meetings between the prime and its Subcontractors. At a minimum, the Contractor shall initiate, and support meetings identified within the paragraphs of this SOW.

CDRL A009 – REPORT, RECORD OF MEETING/MINUTES

CDRL A010 – PRESENTATION MATERIAL

3.2.5.1 Post Award Kickoff Meeting

The Contractor shall schedule a Post Award Kickoff Meeting at the Contractor’s facility and hold the Post Award Kickoff Meeting within sixty (60) calendar days after contract award. During the Post Award Kickoff Meeting, the Contractor shall provide a detailed briefing on its management and contract execution strategy. The contract briefing shall include discussion all elements selected in Column (b) of Sections 1-5 of the DD Form 1484, Post Award Conference Record (attached herein as attachment J-X). The Contractor shall identify any material with a lead time in excess of twenty-five (25) weeks. The Contractor shall provide a summary of all purchase orders placed to date. The Contractor shall plan for a one-day Post Award Kickoff Meeting. The Post Award Kickoff Meeting is for the Government to examine, in depth, the AN/WSN-12 production program and the Contractor's planning in order to meet required production capacity and support requirements.

CDRL A009 – REPORT, RECORD OF MEETING/MINUTES

CDRL A010 – PRESENTATION MATERIAL

3.2.5.2 Program Reviews

The Contractor shall conduct AN/WSN-12 Program Reviews each year of the contract, up to three reviews per year, and shall be one to two days in duration. PEO IWS 6.0 shall schedule these reviews and provide at least fourteen

(14) calendar days advance notice to the Contractor. Program Reviews may be held in conjunction with other navigation reviews or otherwise rescheduled with the written consent of the Representative (COR) of this contract.

The Contractor shall make working level personnel available for the reviews and shall provide an agenda, handouts, reports, analyses and any other material needed to accomplish the objectives of the review as presentation material fourteen (14) days prior to the review. Copies of all slides, referenced documents, charts and other presentation materials shall be made available to Government attendees. The Contractor shall provide a AN/WSN-12 production status briefing at these reviews.

CDRL A009 – REPORT, RECORD OF MEETING/MINUTES

CDRL A010 – PRESENTATION MATERIAL

3.2.5.3 Technical Meetings/Data Exchanges

The Contractor shall support program management meetings, Test & Evaluation Working Group (TEWG), Integrated Logistic Support Working Group (ILSWG), and technical discussion meetings. These meetings shall be conducted as needed per the Integrated Master Schedule (IMS) via teleconferences with the Government and other organizations as required by the Government.

CDRL A009 – REPORT, RECORD OF MEETING/MINUTES

CDRL A010 – PRESENTATION MATERIAL

3.2.5.4 Quality Assurance

The Contractor shall implement a Quality Assurance (QA) system that is certified to ANSI/ISO/ASQ Q9001 or greater, and that ensures the products delivered meet the requirements of the TDP and SOW. The Contractor shall be responsible for performance of all quality requirements for the items delivered under this contract. The Contractor QA system shall include provisions conforming to all production requirements cited in this SOW including calibration, Subcontractor control, failure diagnosis and corrective action, statistical process control, component and environmental screening, testing, and inspection. The Contractor shall provide its Quality Assurance Program Plan which shall address management, reliability, quality assurance, system safety, and configuration management. These documents shall be made available for examination upon request.

CDRL A011 – QUALITY ASSURANCE PROGRAM PLAN (QAPP)

3.2.6 Configuration Management (CM)

(a) Baseline Definition - For configuration control purposes, all contractual documentation in effect at the time of contract award shall constitute the Contract Baseline which shall be considered incorporated in the baseline documentation.

(b) General Requirement - (1) The Contractor shall maintain a Configuration Control Program to assure that all detail level work being performed under this contract is in compliance with appropriate baseline documentation.

The Contractor shall prepare a Supplier’s Configuration Management Plan in accordance with the requirements of the contract for approval by the Government (see Contract Data Requirements List (CDRL) A012.

(2) Whenever a situation arises wherein the Contractor cannot comply with a baseline document, or whenever intent of such documentation is significantly changed by detail level documentation, the Contractor shall submit change documents to modify baseline documents to resolve the conflict or to allow non-compliance. Whenever the cost of implementing a proposed change is less than the threshold requiring certified cost or pricing data, the Contractor shall provide documentation explaining the nature of related costs as shown on the change document. Whenever the contract cost changes by an amount greater than the threshold requiring certified cost or pricing data, the Contractor shall complete such cost and pricing data as the Contracting Officer shall require detailing all related costs, and attach it to the change document. Requirements for cost and pricing data shall be determined by the gross amount of the change unless otherwise directed by the contracting officer. Change documentation shall be submitted to the Contracting Officer in accordance with paragraphs (c) through (f) below.

(c) Engineering Change Proposals (ECPs) - ECPs shall be prepared in accordance with the approved configuration management plan and the requirements of the contract. DI-SESS-80639D, SAE EIA-649-1, SAE EIA-649-B, ISO 10007, and MIL-HDBK-61A apply. An ECP shall be submitted whenever the detail level physical configuration, material quality, operational or functional performance of equipment or installed systems will not be in compliance with baseline design-related documents (Specifications, Contract Drawings, etc.), and a change to the baseline document is considered an appropriate means of resolving a design-related issue. Documentation shall be developed in sufficient detail to enable Government review and evaluation of the merits of the proposed change, including cost and scheduling impact, ship class impact, and consequences if disapproved. All existing drawings and technical manuals impacted by the change shall be listed along with a brief narrative explanation of needed changes to incorporate the ECP if approved. Weight and moment data incidental to the change shall be provided. The Contractor shall also prepare applicable baseline document insert sheets, with specific word changes or proposed re-write, to facilitate baseline documentation changes.

(1) A Class I ECP is defined as a change to approved configuration documentation for which the government is the Current Document Change Authority or that has been included in this contract and:

(i) affects any physical or functional requirement in approved functional or allocated configuration documentation,

(ii) affects any approved functional, allocated or product configuration documentation, and cost, warranties or contract milestones, or

(iii) affects approved product configuration documentation.

(2) A Class II ECP is defined as a change to approved configuration documentation for which the government is the Current Document Change Authority or that has been included in this contract, and which is not a Class I.

(3) The Current Document Change Authority is the authority currently responsible for the content of a drawing, specification, or other document; and which is the sole authority for approval of changes to that document.

(4) A Notice of Revision (NOR) is a document used to define revisions to configuration documentation which require revision after ECP approval.

(5) Class I &II ECPs shall be prepared and submitted in accordance with CDRL A014.

(6) All Class II ECPs shall be incorporated at no additional cost to the Government.

(7) The Contractor shall not implement any:

(i) Class I ECP until after receipt of written approval of the Contracting Officer

3.2.6.1 Configuration Management Plan (CMP)

The Contractor shall develop and implement a Supplier’s Configuration Management Plan that incorporates the principles of the PEO IWS 6.0 CMP, provided as GFI in Attachment J-2. The Contractor’s CMP shall demonstrate a disciplined approach to identifying and documenting functional and physical characteristics of a material item, change control, reports, and records of configuration information.

3.2.6.2 Configuration Status Accounting (CSA)

The Contractor shall establish a Configuration Status Accounting database to record and track the status of hardware and software associated with engineering changes and their implementation activities. The Contractor shall record the CSA data for each engineering change to the navigation system and shall provide a report of the CSA activities to the Government as CSA Information, Configuration Status Accounting Reports (CSAR).

CDRL A012 – CONFIGURATION STATUS ACCOUNTING (CSA) INFORMATION, CONFIGURATION

STATUS ACCOUNTING REPORTS (CSAR)

3.2.6.3 Engineering Change Proposals and Requests for Variance If the Contractor identifies the need for an Engineering Change Proposal (ECP), the Contractor shall generate and submit an ECP or Request for Variance (RFV), as appropriate, in accordance with the approved Contractor’s CMP.

In the event production is impacted due to DMSMS or production, the Contractor shall generate a Class II ECP for process changes. The Contractor shall submit Class II ECPs for review and concurrence by the PEO IWS 6.0 on-site technical representative (if available), or the PEO IWS 6.0 Local Configuration Control Board (LCCB) chair. After concurrence from the on-site representative or LCCB chair, the Contractor shall provide the Class II ECP to the COR for approval. Upon such approval by the COR, the Contractor shall implement the Class II ECP. Class I ECPs shall be incorporated into this contract by the Contracting Officer via the contract changes clause. The Government shall hold the ultimate authority to determine if an ECP is Class I or II.

CDRL A013 – REQUEST FOR VARIANCE (RFV)

3.2.6.4 As-Built Configuration

The Contractor shall develop an As-Built Configuration List for each delivered item. The As-Built List shall extend down to the Lowest Replaceable Unit (LRU)/System Replaceable Assembly (SRA) level and be recorded in a CSA database. The list of LRUs/SRAs is provided as GFI in Attachment J-2.

CDRL A014 – AS-BUILT CONFIGURATION LIST

3.2.7 Obsolescence Management

The Contractor shall monitor, identify, plan for, and recommend solutions for DMSMS and obsolescence issues in accordance with the PEO IWS 6.0 Obsolescence and DMSMS Management Plan and PEO IWS 6.0 Risk Management Plan. The Contractor shall manage obsolescence issues over the entire period of the contract to ensure compliance with all performance and contract requirements. Hardware, software, and/or firmware shall be considered obsolete when the item can no longer be procured from the Original Equipment Manufacturer (OEM). The Contractor’s obsolescence management shall include locating part replacement, vendor interface, and engineering efforts. The Contractor shall identify all changes that are required to avoid and/or resolve hardware, software and/or firmware obsolescence issues which affects or may affect production or support. At a minimum, the Contractor shall evaluate the following options: technology refresh through product migration to a new product (with either the same or increased functionality or capability), Lifetime Buy (LTB) from the OEM and/or procuring the obsolete item from a third-party source. The Contractor shall initiate actions to resolve obsolescence management issues with sufficient lead-time to preclude impact to Government delivery requirements (including production and fleet requisitions) while meeting the other requirements of this SOW.

The Contractor shall develop, maintain, and implement an Intensity Level 3 DMSMS Management Plan. In addition, the plan shall address the following topics as they relate to DMSMS management: long-lead time material, unique processes, tooling, and the impact of environmental regulations and policy such as Restriction of Hazardous Substances (RoHS) and Registration, Evaluation, Authorization, and Restriction of Chemicals (REACH). The plan shall be delivered using DMSMS Management Plan. The performance of the plan shall be evaluated by the DMSMS Health Assessment Report.

The Contractor shall deliver a DMSMS impact assessment report, using DMSMS Health Assessment Report, for all assemblies, LRUs, and Weapons Replaceable Assembly (WRA) and their related software used on the end item deliverables. The report shall detail the predicted impact of known DMSMS issues and projected DMSMS issues. It shall use the most accurate forecasting data available to the Contractor. The report shall detail the date the assembly and its related higher assemblies shall most likely become unsupportable considering inventories, usage, repair capability, funded upgrades, redesigns, and similar attributes or actions. The report shall cover a period of at least ten

(10) years from the date of its publication. The Contractor’s plan to implement its DMSMS approach shall be described in a DMSMS Management Plan.

The Contractor shall evaluate the capability of Subcontractors to manage DMSMS. When the Contractor’s or the program office’s evaluation of a Subcontractor’s capability for DMSMS Management reveals deficiencies, the Contractor shall either help the Subcontractor establish a competent DMSMS capability or, if that is not feasible, assume the DMSMS Management functions for the items provided by the Subcontractor. The Contractor shall report the health of its Subcontractor using DMSMS Subcontractor Health Report, within three (3) months of contract acceptance and annually thereafter.

CDRL A015 – DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

HEALTH ASSESSMENT REPORT

CDRL A016 – DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

MANAGEMENT PLAN

CDRL A017 – DMSMS SUBCONTRACTOR HEALTH REPORT

CDRL A018 – LOGISTICS PRODUCT DATA

3.2.7.1 Obsolescence/DMSMS Identification

The Contractor shall implement and maintain a process to identify and immediately notify the Government of pending and emergent recall notices, obsolescence notices, or vendor implemented changes associated with the AN/WSN-12 product baseline hardware, software, and firmware (all variants). The Contractor shall submit a Technical Report- Study/Services, DMSMS Report as notification of an emerging DMSMS issue. The report shall provide a proposed resolution plan that may include product upgrade, technology refresh, lifetime buys, bridge buys and/or a redesign to meet the requirements of the contract.

The Contractor shall provide a report using DMSMS Life Cycle Management Data, notifying the program office of DMSMS issues and projected DMSMS issues within one (1) week of discovering the issue. The Government encourages informal reporting of DMSMS issues and projected DMSMS issues to expedite the process.

The Contractor shall operate and maintain a case management system. Cases shall be created for each valid DMSMS issue resulting from item monitoring or any other source, including the Government and Industry Data Exchange Program (GIDEP) and the Defense Logistics Agency (DLA). The Contractor shall provide the program office with a monthly list of all open DMSMS case, using DMSMS Life Cycle Management Data.

CDRL A019 – DMSMS LIFE CYCLE MANAGEMENT DATA

3.2.8 Program Security

The Contractor shall comply with clause NAVSEA C-204-H002 and DoD 5200.01, provided as GFI in Attachment J-2. The Contractor shall secure media in accordance with the above documents and the Contract Security Classification Specification (DD Form 254) provided.

The Contractor shall handle, and store classified material up to the SECRET Level as referenced in the DD Form 254.

The Contractor shall maintain a facility clearance of SECRET or higher.

All Contractor personnel accessing classified information or material associated with and/or performing work under this contract must be United States citizens and shall possess and maintain a final security clearance at the SECRET level or higher.

The Contractor shall be required to have access to Controlled Unclassified Information (CUI), formerly known as For Official Use Only information, in the performance of this contract.

In order to access the current contract specifications and applicable documentation, the Contractor may use the Defense Technical Information Center (DTIC).

The Contractor requires a Communications Security (COMSEC) account to accommodate the use of secure communications. The Contractor shall be required to have access to COMSEC and Secret Internet Protocol Router Network (SIPRNet) equipment, or the Contractor may use an approved contractor-furnished Secure Terminal Equipment (STE) phone to facilitate secure communications.

If the Contractor requires the transfer of classified material, then the Contractor may require use of the Defense Courier Service (DCS).

All AN/WSN-12 information is export controlled and must remain under continuous U.S. control. The Contractor shall ensure that International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR) controlled information, critical components or Critical Program Information (CPI) is not released to or developed, tested, fabricated or assembled by foreign: nationals, facilities, Subcontractors, suppliers or vendors. The Contractor shall develop a Program Protection Implementation Plan (PPIP). As part of the PPIP, the Contractor shall notify the Government of any part, information, material, or labor not provided by a Trusted Source and must obtain specific written authorization from the Contracting Officer to proceed with its use. A Trusted Source is defined as a source that has the Government’s confidence in the source's ability to secure national security systems by assessing the integrity of the people and processes used to design, generate, manufacture, and distribute national security critical components. The Contractor shall flow down the Trusted Sources and export control requirements of this paragraph to all Subcontractors performing under this contract.

CDRL A020 – PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP)

3.2.8.1 International Traffic in Arms Regulations (ITAR) and EAR The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical Assistance Agreements (TAA), etc. required by the ITAR and EAR, and must obtain specific written authorization from the Contracting Officer before exercising such approvals or licenses.

3.2.8.2 Preventing Counterfeit Parts and Materials

The Contractor shall provide a Counterfeit Prevention Plan that documents procedures to minimize the risk of procuring and/or using counterfeit parts and materials. This plan shall conform to the requirements outlined in the clause under Section I of this contract entitled DFARS 252.246-7007, Contractor Counterfeit Electronic Part Detention and Avoidance System.

Solicitations and subcontracts for all suppliers shall contain a requirement for procedures to minimize the risk of procuring and/or using counterfeit parts and materials.

The Contractor shall not procure parts or materials from unauthorized sources (e.g. independent distributors or brokers) unless no other means for procurement of the parts or materials exist. The report shall contain the following information:

a) Reason why an authorized supplier or OEM could not provide the part or material.

b) Product certificate of conformance with traceability to the OEM, if available.

c) Verification and authenticity data results (e.g., visual inspection, marking/surface finish permanency, Differential Power Analysis (DPA), Scanning Acoustic Microscopy, Energy Dispersive X-Ray Spectroscopy, Fourier Transform Infrared (FTIR) Spectroscopy, Rockwell Hardness Test, etc.).

SAE AS5553 contains information regarding the detection, avoidance, and mitigation of counterfeit electronic components, and may be used as a reference document for meeting the above requirements.

The Contractor shall not procure parts or materials from unauthorized sources without program office approval of the Unauthorized Source Purchase Report.

CDRL A021 – COUNTERFEIT PREVENTION PLAN

CDRL A022 – TECHNICAL REPORT – STUDY/SERVICES, UNAUTHORIZED SOURCE PURCHASE

REPORT

3.3 Detailed Tasks: First Article Units and Design Qualification for AN/WSN-12 Production (CLIN 0001 and

0002)

3.3.1 Technical Reviews and Audits

The Contractor shall identify, host, and conduct Technical Reviews (including Audits) corresponding to critical events and key program milestones as described in EIA/IS-632 and IEEE 1220, and the Technical Review Manual (TRM) or equivalent Agile framework, with Government concurrence. The purpose of these reviews is to confirm that the design documentation is complete, complies with the established design approach, is technically sound and shall satisfy the functional requirements as defined in the approved functional design documents. For each review, the Contractor shall provide entry and exit criteria prescribed in the TRM, provide an assessment of whether these criteria were met, and describe the potential increase of commercial technology utilization. With Government concurrence, the Contractor may propose a tailored technical review plan, entry/exit criteria, and agenda using the TRM as guidance. With Government concurrence, the Contractor may propose an Agile approach. The Contractor shall generate and deliver a Design Review Information Package (DRIP) in accordance with the TRM for Government assessment prior to the technical review.

Reviews and audits shall be conducted to meet the AN/WSN-12 Program schedule. Subcontractors (if applicable) shall attend specific portions of applicable reviews or audits when required to address essential elements. The Contractor shall deliver technical review documentation as prescribed in the TRM to support formal technical reviews.

All reviews or audits shall be conducted in accordance with formats, agendas, and entry and exit criteria, contained or referenced in the TRM, to be approved by the Government before the meeting. With the concurrence of the Government, formal reviews may be limited in scope as needed to supplement the Integrated Product and Process Development (IPPD)/Integrated Product Team (IPT) process and still ensure minimal risk to the program. The designated Government approval agent may, and the Contractor shall, sign minutes and action items at the end of the review or audit.

CDRL A023 – DESIGN REVIEW INFORMATION PACKAGE (DRIP)

3.3.2 Production Readiness Review (PRR)

The Contractor shall conduct a PRR to determine whether the production facility is ready for production. The PRR focuses on assessing the readiness of the manufacturing processes, the quality management system, and the production planning (i.e., facilities, tooling and test equipment capacity, personnel development and certification, process documentation, inventory management, supplier management, etc.). The PRR shall evaluate the full, production-configured system to determine if it correctly and completely implements all system requirements. The PRR shall determine whether the traceability of final system requirements to the final production system is maintained. The Contractor shall identify existing and projected manufacturing problems and areas of risk and shall assess the progress in the Contractor’s planning to achieve production rates required under the delivery schedule. The PRR shall determine if production or production preparations incur unacceptable risk that might breach thresholds of schedule, performance, and/or cost. A successful PRR shall demonstrate the AN/WSN-12 is ready to commence production.

As a precursor to the PRR, the Contractor shall provide the Government with access to the appropriate artifacts for review and assessment to ensure entrance and exit criteria are satisfied. The PRR is considered to be successful when the Contractor provides evidence, and the Government concurs, that the Manufacturing Readiness Level (MRL) of 9 or above has been achieved. The PRR shall be conducted after successful completion of the Physical Configuration Audit (PCA) on a AN/WSN-12 system.

The Contractor shall be required to pass PRR by completing all tasks in the PRR Checklist, provided as Attachment J-3. The Contractor shall receive written approval from the Government prior to proceeding to Full Rate Production (FRP). Following successful completion of PRR, DD 250 acceptance of all equipment shall be at the Contractor’s facility.

3.3.3 Technical Data Package (TDP)

The Contractor shall deliver a complete Level III TDP for the AN/WSN-12 Design. The TDP shall include the component test fixtures and procedures that encompasses all Technical Data (TD), Computer Software (CS) including source code and executables, Computer Software Documentation (CSD), Firmware (FM) design and fabrication drawings, specifications, Gerber files and all other items required as part of a complete Level III TDP per MIL-STD- 31000.

CDRL A024 – TECHNICAL DATA PACKAGE (TDP)

3.3.4 First Article Unit (FAU) (CLIN 0002)

The Contractor shall manufacture First Article Units for the AN/WSN-12 system. The FAU shall be manufactured with the same tools, materials, methods, and vendors that the Contractor will use to manufacture the production systems. The FAUs shall conform in every respect to the requirements of this contract and shall be fully tested by the Contractor in accordance with this SOW to determine compliance with said requirements.

FAUs shall undergo Manufacture Acceptance Testing (MAT) as outlined in Section 3.4.1.2.1. Following successful MAT, the Contractor shall deliver the FAUs Freight on Board (FOB) to a facility identified by the Government for System Final Acceptance Testing (SFAT). Following successful SFAT, as outlined in Section 3.4.1.2.2, the Contractor shall return the FAUs FOB from the facility identified by the Government back to the Contractor’s facility.

Should the equipment fail SFAT, the Contractor shall attempt to repair the failed equipment at the SFAT location. If the required repairs cannot be accomplished at the SFAT location, the Contractor shall return the failed equipment to the Contractor’s facility, effect the necessary repairs, repeat the MAT (as necessary) and return it to the facility identified by the Government for System Final Acceptance Re-Test. All costs related to repair, shipping and MAT re-tests of failed equipment are to be borne by the Contractor.

The Contractor shall develop a Test/Inspection Report and Acceptance Test Report, including descriptions of any faults or failures and how they were resolved for each System Final Acceptance Test failure.

Contractor attendance at SFAT Events shall be directed by a Government-issued Technical Instruction (TI) as part of the Engineering Services (ES). Inspection and acceptance determination shall be made by the Government. SFAT shall include qualification and integration testing as necessary to demonstrate the system is fully functional and is ready for final delivery.

CDRL A025 – ACCEPTANCE TEST REPORT

3.3.4.1 Government Independent Verification and Validation (IV&V) The Contractor shall provide one (1) AN/WSN-12 system to the Government for Government-run IV&V testing.

Should the IV&V testing fail to determine that the AN/WSN-12 system meets the performance specifications, the Contractor shall correct the deficiencies in the AN/WSN-12 unit under test at no additional cost to the Government and provide the unit for retest. The Contractor shall resolve all deficiencies and support retest events until IV&V testing determines that the AN/WSN-12 system meets the unit specification.

3.3.4.2 Functional Configuration Audits (FCA)

The Contractor shall support the Government in conducting a Functional Configuration Audit prior to delivery of CLIN 0001-0500. The audit shall be conducted jointly by the Government and Contractor with the Government representative acting as Chair. The FCA shall be completed sixty (60) days prior to first delivery of the applicable CLINs. The Contractor shall host the audit at their facility. The FCA shall verify the configuration items performance against its approved configuration documentation. The Contractor shall provide a suitable workspace and make all pertinent design documentation and drawings readily available to verify that they accurately represent the AN/WSN-12 “as-built” configuration. The Contractor shall document the results of the FCA audit in a Configuration Audit Summary Report and shall correct any identified discrepancies to the design. The Government shall conduct FCA in accordance with the guidelines outlined in the Configuration Audit Plan.

CDRL A026 – CONFIGURATION AUDIT PLAN

CDRL A027 – CONFIGURATION AUDIT SUMMARY REPORT AND CERTIFICATION

3.3.4.3 Physical Configuration Audit (PCA)

The Contractor shall provide one (1) AN/WSN-12 for PCA. The Contractor shall support the Government in conducting a PCA. The Contractor shall provide support including, but not limited to, providing technical documentation, equipment, facilities and services, including disassembly and reassembly of the unit undergoing PCA.

The PCA shall be the formal examination of the as-built configuration of an item against its design documentation.

The Contractor shall respond to audit findings, recommend corrective actions, and resolve all deficiencies and issues identified during the PCA and document these findings in a PCA Summary Report. The Government shall conduct PCA in accordance with the guidelines outlined in the Configuration Audit Plan.

CDRL A029 – CONFIGURATION AUDIT SUMMARY REPORT AND CERTIFICATION

3.4 Detailed Tasks: System Production (CLINs 0100-0500; 1100-1500; 2100-2500, 3100-3500, and 4100-4500)

3.4.1 Manufacture, Assembly, and Test

3.4.1.1 AN/WSN-12 Production

The Contractor shall manufacture and assemble the AN/WSN-12 configurations, Maintenance Assistance Modules (MAMs) Kits, and Inertial Sensor Modules (ISM). In accordance with paragraph 3.2.6.1 of this statement of work, the Contractor shall request Government approval for any changes or deviations from the TDP, including the unit specification and all documentation, via the CM process outlined in the PEO IWS 6.0 CMP, provided as GFI in Attachment J-2. The Contractor shall procure all materials, labor, and other direct costs to accomplish the efforts required by the contract and this SOW. The Contractor shall order all long lead material within forty-five (45) days of contract award. Long lead material is defined as material with a lead time in excess of twenty-five (25) weeks. The Contractor shall procure materials, fabricate, assemble, and conduct all component and manufactured item testing necessary to ensure that the quality of all manufactured and Commercial Off-The-Shelf (COTS) products satisfy the requirements of this contract. The Government shall provide Government Furnished Property (GFP) for incorporation and performance, as identified in Attachment J-3.

3.4.1.1.1 DoD Item Unique Identification (IUID)

The Contractor shall apply DoD IUID marking as required by unit level assemblies, and their associated LRU/SRA procured under this contract as required by the clause under Section I of this contract entitled DFARS 252.211-7003, ITEM UNIQUE IDENTIFICATION AND VALUATION, and Unit/LRU lists provided as GFI in Attachment J-2.

IUID pedigree data for LRUs embedded in Unit level assemblies shall be entered into the IUID Registry as children to the parent unit. The Contractor shall utilize MIL-STD-130N for IUID marking. The Contractor shall deliver the final IUID Marking Activity, Validation and Verification Report at the end of this Contract.

The Contractor shall maintain marking and verification records for all IUID qualifying items manufactured under this contract. The Contractor shall make these records available for inspection by the Contracting Officer or other Government representative at any time during the life of this contract.

CDRL A028 – IUID MARKING ACTIVITY, VALIDATION AND VERIFICATION REPORT

3.4.1.2 Testing

The Contractor shall conduct testing for every manufactured item prior to delivery to the Government, starting at the component level. The Contractor shall conduct MAT for every manufactured item. For each AN/WSN-12 system, the Contractor shall conduct AN/WSN-12 System Level Acceptance Testing. The Contractor shall develop all test procedures and data sheets to ensure the unit specification is met for the unit under test (the unit under test is defined as the component hardware, sub-assembly, or system). The Contractor shall submit an Acceptance Test Plan in accordance with the AN/WSN-12 Production Test Plan, provided as GFI in Attachment J-2. The Contractor shall submit all Test Procedures, in accordance with AN/WSN-12 Factory Acceptance Test Procedures , provided as GFI in Attachment J-2. The Contractor shall only conduct AN/WSN-12 System Level Acceptance Testing with a Government witness identified by the COR. The Contractor shall provide written notification to the Government thirty

(30) days prior to all Manufacturing Acceptance Testing and grant access to a Government witness.

CDRL A029 – ACCEPTANCE TEST PLAN

CDRL A030 – TEST PROCEDURE

3.4.1.2.1 Manufacturing Acceptance Testing

The Contractor shall perform MAT, in accordance with the Government approved Test Plan, Acceptance Test Plan and Test Procedure, Acceptance Test Procedures for the manufactured items. The Contractor shall provide the facilities and test equipment necessary to perform MAT. The Contractor shall provide the results of all MAT events in Test/Inspection Report, Acceptance Test Report.

The Contractor shall conduct MAT for every manufactured item prior to delivery. The Contractor shall perform MAT on all other items/equipment to ensure conformance with requirements, drawings and specifications defined in the TDP. The Contractor shall not proceed with MAT until receiving Government approval of the Test Procedure, Acceptance Test Procedures.