N66604-19-R-0277.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 21 May 2019

X

A

X B

X C X D

EX

X

G

F 42 - 49

50 - 55

X H 56 justin.g.monti@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

DO-C9 1 56

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N66604 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 0 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

SEE SECTION L

conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

JUSTIN MONTI (401) 832-6788

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

3 - 7

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

8 - 17

18 - 19

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

20 - 21

22 - 23 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 24 - 27 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 28 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

29 - 40

PART II - CO NTRACT CLAUSES

NAVAL UNDERSEA WARFARE CENTER

JUSTIN MONTI, CODE 0224

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841-1708

(401) 832-6788

(401) 832-4820FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

01 Apr 2019

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6660419R0277

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

GENERAL INFORMATION

Distribution: FILE, KR, NUWC 01, DCM: TBD, DFAS: TBD, COR: L.Konrath/8532, PM: R.Bashour/8531

NUWCDIVNPT Control Number: 190277

NUWCDIVNPT Requisition Number(s): 1300531368

NUWCDIVNPT POC: Justin G. Monti; Phone: (401) 832-6788; Email: justin.g.monti@navy.mil)

This requirement is being solicited on a sole source basis to Hydroid, Inc. in accordance with 10 U.S.C. 2304(c)(1) –

Only One Responsible Source and No Other Supplies Will Satisfy Agency Requirements.

NOTE: The minimum guarantee for this contract will be $2,500 and met with the issuance of the first delivery order for some quantity of CLIN 0001, CLIN 0002, and/or CLIN 0003.

mailto:justin.g.monti@navy.mil

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 1 Lot Payload Modules

FFP

REMUS MK 18 Mod 2 Unmanned Underwater Vehicle Increment II Upgrade

Payload Modules

See Section B pricing table for stepladder pricing.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PSC CD: 1352

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

0002 1 Lot Data Transfer Devices

FFP

REMUS MK 18 Mod 2 Unmanned Underwater Vehicle Increment II Expendable

Data Transfer Devices unique identification or a DoD recognized unique identification equivalent.

UNIT UNIT PRICE MAX AMOUNT

0003 1 Lot Acoustic Markers

FFP

REMUS MK 18 Mod 2 Unmanned Underwater Vehicle Increment II Expendable

Acoustic Markers unique identification or a DoD recognized unique identification equivalent.

UNIT UNIT PRICE MAX AMOUNT

0004 1 Lot Technical Data Package (TDP)

FFP

Production Level Technical Data Package including data rights to all hardware and software components associated with the MK 18 Mod 2 Increment II upgrade payloads in accordance with Exhibit "B" Contract Data Requirements List

(CDRL), DD Form 1423. Specific applicable CDRLs will be attached to individual delivery orders, as required.

UNIT UNIT PRICE MAX AMOUNT

0005 2 Job Familiarization Events

FFP

Familiarization Events per Statement of Work (SOW) Task 4.9 (see Section C).

PSC CD: K069

UNIT UNIT PRICE MAX AMOUNT

0006 1 Lot Data

FFP

Applicable to contract line items 0001-0003: Data in accordance with Exhibit "A"

Contract Data Requirements List (CDRL), DD Form 1423. Specific applicable

CDRLs will be attached to individual delivery orders, as required.

NOT SEPARATELY PRICED.

PRICING TABLES

The below tables contain pricing according to each Ordering Period and Quantity Range. The Government will determine each quantity to be purchased by issuing a delivery order.

Payload Modules

CLIN 0001 Quantity

1 - 5 Each 6 – 10 Each 11 - 20 Each

Year 1 $* $* $*

Year 2 $* $* $*

Year 3 $* $* $*

Year 4 $* $* $*

Year 5 $* $* $*

Data Transfer Devices

Acoustic Markers

CLIN 0002 Quantity

1 - 50 Each 51 - 100 Each 101 - 250 Each

Year 1 $* $* $*

Year 2 $* $* $*

Year 3 $* $* $*

Year 4 $* $* $*

Year 5 $* $* $*

CLIN 0003 Quantity

1 - 50 Each 51 - 100 Each 101 - 250 Each

Year 1 $* $* $*

Year 2 $* $* $*

Year 3 $* $* $*

*To be provided by Offeror.

HQ B-2-0022 CONTRACT SUMMARY FOR PAYMENT OFFICE (FIXED PRICE) (FEB 1997)

This entire contract is fixed price.

Year 4 $* $* $*

Year 5 $* $* $*

Section C - Descriptions and Specifications

Statement of Work

MK 18 Mod 2 Increment II

PR No. 1300531368

1.0 BACKGROUND

The Naval Undersea Warfare Center Division Newport (NUWCDIVNPT) Undersea Warfare Weapons, Vehicles and Defensive Systems Department, Code 85, has been tasked to lead the MK 18 Mod 2 Unmanned Underwater

Vehicle (UUV) Increment II payload upgrade for the existing MK 18 Mod 2 UUV program. The Increment II payload upgrade will provide the Warfighter with a capability to reduce the overall undersea mine-counter-measure

(MCM) tactical timeline by reacquiring, identifying, and marking targets with an acoustic marker and sending the information back to the Warfighter during the mission through expendable floating data transfer devices (DTDs).

2.0 SCOPE

The tasking in this statement of work (SOW) covers services incidental to the hardware procurement of upgrade payloads, data transfer devices, and acoustic markers. Incidental services include: technical analysis, test and evaluation, software and hardware configuration, preparation of engineering drawings, hardware and software configuration control, installation of upgrades, and training.

2.1 Place of Performance

Contractor’s Facility

2.2 Authorized User

Code 85

2.3 Sponsor

NAVSEA 06 - PMS 408

2.4 Funding

The following appropriations will be used to fund orders under this contract: RDTE, OPN, and OM&N.

3.0 Applicable Documents (ADs)

The contractor shall perform the tasking identified in Section 4.0 in accordance with the below ADs. The

Government will provide the contractor with a digital copy of all ADs with the Request for Proposal (RFP). Once the Government provides the ADs to the contractor, the contractor is responsible for maintaining a current library and performing to the most up to date document at the time of order award(s).

Number Document Title SOW Task

3.1 ANSI/EIA-649B Configuration Management Standard, June 2011 4.11

3.2 ASME Y14.100 Engineering Drawing Practices, Nov 2017 4.11

3.3 ASME Y14.24 Types of Application of Engineering Drawings, Jan

4.11

3.4 ASQ 9001: Quality Management Systems Requirements T1040, Oct 2015 4.11

3.5 DODI 8500.01 Cybersecurity, Apr 2007 4.7

3.6

DODI 8510.01 Risk Management Framework for DOD

Information Technology (IT) dated March 12, 2014, Incorporating

Change 1 effective May 24, 2016

4.7

3.7 DODD 8140.01 Cyberspace Workforce Management dated August

11, 2015 4.7

3.8

DODI 5200.44 Protection of Mission Critical Functions to Achieve

Trusted Systems and Networks (TSN) dated November 05, 2012, Incorporating Change 2 dated July 27, 2017

4.8

3.9 IEEE/EIA 12207.0 Standards for Information Technology Software

Life Cycle Processes, 1996 4.3

3.10 Interface Control Document for the ATLAS Forward-Looking

Sonar on the MK 18 Mod 2 UUV, 04 February 2013 4.0

3.11 MIL-STD-31000A Technical Data Packages, Feb 2013 4.5

3.12 NCSL Z540.3 Requirements for the Calibration of Measuring and

Test Equipment, 2013 4.1

3.13 REMUS REmote CONtrol PROTOCOL KMHYD-Man-0002, Version, Aug 2006 4.3

3.14 Interface Control Document for MK 18 Mod 2 UUV Increment II

MARKER, Sep 2018 4.0, 4.2

3.15 Interface Control Document for MK 18 Mod 2 UUV Expendable

Data Exfiltration, Sep 2018 4.0, 4.2

3.16 Interface Control Document for MK 18 Mod 2 SSAM, Apr 2014 4.0, 4.2

3.17

Interface Design Description for Common Operator Interface for

Navy EOD (COIN) Version 3.0 Draft Revision 0, 10 November

4.0, 4.2, 4.3

3.18

System Performance Specification for the MK 18 Mod 2

Unmanned Underwater Vehicle (UUV)

Increment II September 2018

4.0, 4.2, 4.6, 4.9

3.19 MK 18 Software Development Plan, Aug 2017 4.3

3.20 Interface Control Document for MK 18 Video Automated Target

Recognition (VATR) Common Module (VCM), Sep 2018 4.0, 4.2

3.21 Interface Control Document for MK 18 Mod 2 Multi-Axis

Magnetic Gradiometer, Sep 2018 4.0, 4.2

3.22 Interface Control Document for Marine Sonics Side Scan Sonar Sea

Scout, Sep 2018 4.0, 4.2

3.23 Interface Control Document for MK 18 Mod 2 UUV Increment II

Reacquire – Identify – Mark (R-I-M) Payload, Sep 2018 4.0, 4.2

3.24 MK 18 Mod 2 UUV Increment II Low-Magnetic Nose Section

Drawings, Sep 2018 4.0, 4.2

3.25 MK 18 Mod 2 Increment II Preliminary Engineering Change

Proposal - 16-020 (P) dated Feb. 27, 2017 4.0

3.26 MIL-STD-1839, May 2010 4.1

4.0 REQUIREMENTS

The contractor shall provide the services as detailed herein to upgrade MK 18 Mod 2 UUVs with Increment II hardware. Upgrade hardware includes the following:

(a) Increment II Payload (ADs 3.10, 3.16, 3.17, 3.18, 3.20, 3.21, 3.22, 3.23, 3.24 and 3.25) *

(b) Acoustic Markers (AD 3.14)

(c) Data Transfer Devices (AD 3.15)

*ADs listed include specifications and procedures specific to the upgrade hardware and are relevant to all tasking.

Quantity and delivery of items will be specified in individual orders.

4.1 HARDWARE MANUFACTURING

The contractor shall manufacture (a) payload modules, (b) acoustic markers, and (c) data transfer devices for MK 18

Mod 2 Increment II upgrades to meet the system performance specifications detailed in the relevant ADs defined in

Section 4.0. The contractor shall perform manufacturing inspections, calibration procedures, check-in, checkout, and packaging so that hardware is ready for installation (detailed procedures in ADs 3.12 and 3.26). The contractor shall conduct a calibration program showing that the manufacturing process was conducted in accordance with ADs

3.12 and 3.26 and provide a Calibration and Measurement Requirements Summary (CMRS). The contractor shall deliver a comprehensive Interface Control Document (ICD) and technical drawings that include all electrical and mechanical drawings associated with the Increment II payload, acoustic markers, and data transfer devices.

CDRL A001 – Calibration and Measurement Requirements Summary (CMRS) (DI-QCIC-80278C)

CDRL A002 – Interface Control Document (ICD) (DI-SESS-81248B)

CDRL B003 – Production Technical Drawings (mechanical and electrical) (DI-SESS-8100E)

4.2 HARDWARE INSTALLATION AND SYSTEM INTEGRATION TO MK18 UUV

Upon completion of Task 4.1, the contractor shall install the upgraded hardware into existing MK 18 Mod 2 UUVs to be provided as GFP on individual orders. The contractor shall perform all upgrade calibration procedures, check-in, checkout, installation procedures, system integration (as defined below), and packaging to deliver MK 18 Mod 2

Increment II payloads, acoustic markers, and data transfer devices to the Government, in accordance with AD 3.18.

The contractor shall perform system integration for the following systems and sub-systems, in accordance with AD

3.18:

Electrical systems and components in accordance with ADs listed in Section 4.0 (specific to the upgrade hardware ordered)

Mechanical systems and components in accordance with ADs listed in Section 4.0

System hardware in accordance with ADs listed in Section 4.0

4.3 Software Integration, Modifications and Documentation

Concurrently with completing Task 4.2, System Integration, the contractor shall upgrade MK 18 UUV software to integrate the Increment II payload module, Acoustic Markers, and Data Transfer Devices while maintaining backwards compatibility with previously delivered MK18 Mod 2A+ UUV payloads, in accordance with ADs 3.13, 3.17, and 3.18. The contractor shall provide documentation of vehicle system and subsystem functions, software algorithms, routines, and interfaces from the Increment II upgrade modules, Acoustic Markers, and Data Transfer.

The contractor shall provide Software Issue Summary, System Software Updates, Software Version Descriptions, Updated REMUS REmote CONtrol PROTOCOL KMHYD-Man-0002, (AD 3.13), System Software User Manual

Updates, and Updated Interface Control Document of Vehicle Interface Program (VIP). The contractor shall provide redlines to existing software documentation for Government approval.

CDRL A004 – Software Issue Summary

CDRL A005 – System Software Updates

CDRL A006 – Software Version Descriptions (DI-IPSC-81442A)

CDRL A007 – Updated REMUS REmote CONtrol PROTOCOL KMHYD-Man-0002, (AD 3.13)

CDRL A008 – System Software User Manual Updates (DI-IPSC-81443)

CDRL A009 – Updated Interface Control Document of Vehicle Interface Program (VIP) (DI-SESS-81248B)

4.4 INCREMENT II SOURCE CODE AND TECHNICAL DATA

The contractor shall generate Technical Data (TD), Computer Software (CS), and Computer Software

Documentation (CSD) including source code for all MK 18 Mod 2 Increment II systems in accordance with AD

3.11. The contractor shall prepare pseudocode associated with the MK 18 Mod 2 Increment II system so that future changes and updates by programmers unfamiliar with the original code can be made without introducing software hazards. The contractor shall deliver the source code and pseudocode in the technical data package for MK18 Mod

2 Increment II in sufficient detail to allow Government to meet the life cycle requirements including independent manufacture, upgrade, repair, installation, operation, training, and maintenance of the MK 18 Mod 2 Increment II

Payload, acoustic markers, and data transfer devices.

CDRL A00A – Computer Software (DI-IPSC-81488)

CDRL A00B – Software Source Code (DI-IPSC-80590B)

CDRL B00C – Technical Data Package (DI-SESS-80776A)

4.5 TESTING

The contractor shall submit a test plan and Final Factory Test Procedures (FFTP) documenting the test approach to accomplish contract completion requirements in accordance with AD 3.18. The contractor shall generate a

Requirements Traceability Verification Matrix (RTVM) which documents the requirements of this SOW and how the requirements will be verified through execution of the FFTP for MK 18 Mod 2 Increment II specifications and capabilities. After executing the approved Test Plan and generating Objective Quality Evidence (OQE) that all requirements outlined in the RTVM have passed, the modules shall be delivered to the Government for Government

Acceptance Testing (GAT). Government acceptance of each Increment II payload, including data transfer devices and acoustic markers as specified in individual orders, depends on successful completion of the tests described herein. The contractor shall generate a Test Report coordinating OQE to the RTVM. The contractor shall collect test data for the following test events for delivery upon Government request:

Initial Contractor Sub-System Testing (Occurs during System Integration)

System Integration Testing (Occurs during System Integration)

Software Validation Test (Occurs during Software Integration)

Final Factory Testing (Occurs once all tasking is complete, before Government Acceptance)

The contractor shall coordinate and schedule all testing events listed above with the Government.

CDRL A00D –Test Plan (DI-NDTI-80566A)

CDRL A00E – Final Factory Test Procedures (DI-NDTI-80603A)

CDRL A00F – Requirements Traceability Verification Matrix (RTVM) (DI-MGMT-82133)

CDRL A00G – Test Reports (DI-NDTI-80809B)

4.6 CYBERSECURITY (CS) RISK MANAGEMENT FRAMEWORK (RMF)

Prior to performing work under Task 4.6, the contractor shall provide the Government with the Cybersecurity

Workforce (CSWF) certificates of all personnel performing cybersecurity functions on the MK 18 Mod 2 Increment

II system, hereafter referred to at the Increment II system, in accordance with AD 3.7.

CDRL A00H – CSWF Report [DI-MGMT-82160]

The contractor shall implement vulnerability management tasks for cybersecurity compliance to include patch maintenance, anti-virus and implementation of Security Technical Information Guides (STIGs), Security Readiness

Guides (SRGs), and Secure Content Automation Protocol (SCAP) Benchmarks as defined in sections 2.1.12 and

2.1.13 of the RMF Package Deliverable (CDRL A00J - DI-MGMT-82001). The contractor shall scan the Increment

II system for vulnerabilities utilizing the Department of Navy (DoN) approved vulnerability scanning tools in accordance with AD 3.5 on a minimum monthly basis as defined by the RMF Package Deliverable. The contractor shall ensure the scanning tools are updated with the latest signatures and scanning engines prior to the execution of each vulnerability scan in accordance with AD 3.5.

The contractor shall develop and deliver the Increment II system security artifacts as defined in section 2.1.2

Security Plan (SP) of the RMF Package Deliverable as tasked at the order level.

The contractor shall maintain the Increment II system in accordance with the established security control baseline identified in the Increment II RMF Implementation Plan provided by the Government as GFI 6.8. The contractor shall use the Increment II RMF Implementation Plan as defined in section 2.1.5 of the RMF Package Deliverable to document the implementation of each planned security control, addressing each security control to determine the implementation status, and describing all tailoring guidance to more closely align the control for specific operating conditions.

The contractor shall participate in cybersecurity test events, as required, to gain interim authority to test at the contractor’s manufacturing facility, or other test sites, for the Government to conduct security assessments of the system to meet the requirements for obtaining RMF authorization decisions in accordance with AD 3.6. If test results identify non-compliant security controls stemming from the system security assessments, the contractor shall document the non-compliances in the Plan of Actions and Milestones (POA&M) as defined in section 2.1.10 of the

RMF Package Deliverable.

CDRL A00J – RMF Package (DI-MGMT-82001)

4.7 PROGRAM PROTECTION IMPLEMENTATION PLAN

The contractor shall develop and maintain a Program Protection Implementation Plan (PPIP) in accordance with AD

3.8 and based upon the requirements specified in the Increment II system Program Protection Plan provided as GFI

6.9. The contractor shall deliver the PPIP to the Government for review and approval at the order level.

The contractor shall provide technical assistance four (4) times per year to the Government in a Criticality Analysis

(CA) to support Supply Chain Risk Management (SCRM) efforts to determine mission critical components that may result in catastrophic or critical protection failures due to operational, system information, or component integrity aspects, and document results in the PPIP. The need for CA will be identified at the order level.

CDRL A00K – Program Protection Implementation Plan (DI-MGMT-82144)

NOTE: If the contractor procures Integrated circuit-related products or services when the integrated circuits are custom-designed, custom-manufactured, or tailored for a specific DoD military end use (generally referred to as application-specific integrated circuits (ASIC), the contractor shall only procure those products or services from a

DoD approved trusted supplier using trusted processes accredited by the Defense Microelectronics Activity

(DMEA).

4.8 OBSOLETE PARTS

The contractor shall provide an initial obsolescent parts report on components, subsystems, and systems, related to the Increment II upgrade hardware, Acoustic Markers, and Data Transfer Devices prior to the start of Task 4.1. The obsolescent parts report shall include replacement recommendations, analysis, and costs estimates. With approval from the Contracting Officer, the contractor shall replace obsolete parts on components, subsystems, and systems, that would prevent the integration of the Increment II upgrade hardware, Acoustic Markers, and Data Transfer

Devices. The contractor shall test and provide test reports for replacement parts, systems, and subsystems to verify operation and function in accordance with AD 3.18.

The contractor shall provide a yearly obsolescent parts report on components, subsystems, and systems, related to the Increment II upgrade hardware, Acoustic Markers, and Data Transfer Devices. The obsolescent parts report shall include replacement recommendations, analysis, and costs estimates. With approval from the Contracting

Officer, the contractor shall replace obsolete parts on components, subsystems, and systems, that would prevent the integration of the Increment II upgrade hardware, Acoustic Markers, and Data Transfer Devices. The contractor shall test and provide test reports for replacement parts, systems, and subsystems to verify operation and function in accordance with AD 3.18.

CDRL A00L – Replacement Parts List (DI-MISC-80508B)

CDRL A00M – Replacement Parts Test Reports (DI-NDTI-80809B)

CDRL A00N – Obsolescent Parts Report (DI-MISC-80508B)

4.9 FAMILIARIZATION OF THE MK 18 MOD 2 INCREMENT II FOR GOVERNMENT OPERATORS

The contractor shall provide two (2) system familiarization events during the life cycle of the contract at the contractor’s facility for up to six Government operators or representatives per session. The contractor shall provide each session with two (2) classroom days and one (1) at-sea training day with one (1) at-sea contingency day in case of inclement weather. The training shall consist of familiarization with the changes to the MK 18 Mod 2 Increment

II upgrades, Acoustic Markers, and Data Transfer Devices to include changes to the following: payload module operations, functionality, maintenance, installation, and removal; marker operations, functionality, maintenance, installation, and removal; data transfer device operations, functionality, maintenance, installation, and removal. The dates of the events and further training details will be identified in the individual orders. The at-sea training shall allow for the Government operators or representatives to apply the knowledge gained in the prior two (2) day in-class familiarization. The contractor is responsible for providing the boat and all personnel required to conduct the at-sea familiarization portion of the event.

The contractor shall deliver a System Familiarization Plan specific to the MK 18 Mod 2 UUV Increment II payload modules, Acoustic Markers, and Data Transfer Devices prior to each event.

CDRL A00P – System Familiarization Plan (DI-ILSS-80872)

4.10 CONFIGURATION MANAGEMENT

The contractor shall maintain a history of configuration changes for the following to be made available upon

Government request in accordance with ADs 3.1, 3.2, 3.3, and 3.4:

Software Version Controls

Mechanical & Electrical Design Changes

Technical Manuals

Mechanical and Electrical Drawings

Interface Control Documents (ICDs)

CDRL A00Q – Configuration History (DI-MISC-80508B)

4.11 WARRANTY

The contractor shall provide a minimum one-year warranty that the products and services under this contract shall be free from defects in materials and workmanship under normal use and service when correctly installed, used and maintained for a period of one (1) year from date of delivery to the Government or date of service provided.

Warranty information shall be included upon delivery of each upgrade payload module, to include the component names, part numbers, serial numbers, source of repair contact information, and warranty expiration date.

5.0 PROGRESS REPORTS

The contractor shall prepare a Contractor’s Status Report (CSR) as specified in individual orders detailing programmatic, contractual and technical progress of the work and existing or potential problem areas.

CDRL A00R – Contractor’s Status Report (CSR) (DI-MGMT-81991)

6.0 GOVERNMENT FURNISHED INFORMATION (GFI)

The following documents will be provided by the Government in a digital format at time of order award(s).

Number Document Title

6.1 Fleet Integration Schedules

6.2 Internal/External Program Reviews Schedule

6.3 Meeting and Conference Minutes/Action Items

6.4 Meeting, Conference, Trip Reports

6.5 Program Planning Data and Schedules

6.6 MK 18 UUV Program Documents

6.7 MK 18 UUV Program Management Status Reports and Analyses

6.8 Security Control Traceability Matrix

6.9 Government Program Protection Plan

7.0 QUALITY SURVEILLANCE

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables. Contractor performance will be evaluated in the areas of technical quality, schedule/timeliness, management, utilization of small business, and regulatory compliance as follows:

Technical Quality: The Government will evaluate technical quality by inspecting deliverables to ensure end items meet contract requirements;

Schedule/Timeliness: The Government will evaluate the contractor’s ability to meet negotiated milestones and delivery schedules;

Management: The Government will evaluate the contractor’s ability to integrate and coordinate all activities needed to execute the contract;

Utilization of Small Business: The Government will evaluate the contractor’s compliance with the Small Business

Subcontracting Plan and any small business subcontracting goals contained in the contract; and

Regulatory Compliance: The Government will evaluate the contractor’s compliance with the terms and conditions of the contract relating to applicable regulations and codes.

8.0 EXCEPTION FROM ELECTRONIC AND INFORMATION TECHNOLOGY ACCESSIBILITY

REQUIREMENTS

The Government has determined that this procurement is an exception to the Electronic and Information Technology

(EIT) Accessibility Standards (36 C.F.R. § 1194). Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with EIT Accessibility Standards (36 C.F.R. §

1194).

HQ C-1-0001 ITEM(S) - DATA REQUIREMENTS (NAVSEA) (SEP 1992)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD

Form 1423, Exhibit(s) “A” , attached hereto.

HQ C-2-0008 ASSIGNMENT AND USE OF NATIONAL STOCK NUMBERS (NAVSEA) (MAY 1993)

To the extent that National Stock Numbers (NSNs) or preliminary NSNs are assigned by the Government for the identification of parts, pieces, items, subassemblies or assemblies to be furnished under this contract, the Contractor shall use such NSNs or preliminary NSNs in the preparation of provisioning lists, package labels, packing lists, shipping containers and shipping documents as required by applicable specifications, standards or Data item

Descriptions of the contract or as required by orders for spare and repair parts. The cognizant Government Contract

Administration Office shall be responsible for providing the Contractor such NSNs or preliminary NSNs which may be assigned and which are not already in possession of the Contractor.

HQ C-2-0009 ASSIGNMENT OF SERIAL NUMBER(S) (NAVSEA) (SEP 1990)

The Contractor shall request serial number assignment, in writing, from the Cognizant Technical Program Office, with a copy to the cognizant Contract Administration Office. The request for serial number assignment shall contain the following minimum information:

(a) Contract number;

(b) Assigned line item number and description;

(c) Assigned type designation;

(d) Assigned model number;

(e) Top drawing number and ID (List of Drawings) number;

(f) Exact quantity for which serial numbers are being requested, including preproduction samples required by the contract; and

(g) National Stock Number

HQ C-2-0012 CONFIGURATION MANAGEMENT (NAVSEA) (APR 2015)

(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 Configuration Management Plan in accordance with the requirements of the contract for approval by the Government.

(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 the Contract Data Requirements List

(CDRL), and as described in 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 approved 7 April 2015 and MIL-HDBK-

61A of 7 Feb 2001 apply. An ECP should 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.

(d) Non-Engineering Change Proposals (NECPs) – An NECP should be submitted whenever necessary to document administrative, procedural, scheduling, or documentation changes that do not directly impact the physical configuration of the equipment. The NECP shall explain the nature of the problem, identify the applicable baseline document (i.e., Contract Data Requirement List (CDRL), Contract Clause, etc.) and provide a detailed explanation justifying the proposed course of action desired to resolve the problem. Insert sheets for applicable documents shall also be attached to facilitate change action in the event the NECP is approved.

(e) Deviations and Waivers - In the event that a baseline design-related document requirement cannot be met, and a change to the baseline document is considered inappropriate, the Contractor shall submit a Request for Variance.

DI-SESS-80640D approved 7 April 2015 and MIL-HDBK-61A of 7 Feb 2001 apply. The explanation of "need for deviation" should provide detailed justification and consequences of approval, to include technical details explaining the degree of non-compliance or effect on ship equipment or system operation constraints. In a similar manner, a waiver shall document an "as built" configuration that departs from baseline documentation and should include any proposed corrections or modifications to better meet the intent of the baseline document.

(f) Equitable Adjustments for Change Documentation Preparations - For its effort expended in preparing ECPs, NECPs, Deviations and Waivers, the Contractor shall receive equitable adjustment under the following circumstances:

(1) In the event the Contractor, on its own initiative, and without written request from the Contracting

Officer, develops a change document that is later disapproved by the Government, the Contractor shall bear the cost of this effort.

(2) To avoid such loss, and at its option, the Contractor may submit a "preliminary" document that outlines intent, but without detailed supporting documentation and request the Contracting Officer's approval for expenditure of effort to complete the detailed supporting documentation. In the event the Contracting Officer denies this request, the Contractor will bear the cost of development of the "preliminary" document, and shall make no further effort to complete detailed supporting documentation.

(3) In the event the Contracting Officer approves the Contractor's request to develop supporting documentation, the Contractor shall be equitably compensated for its effort for both the "preliminary" and "final" documentation, regardless of whether or not the change document is later approved.

(4) In the event the Contracting Officer requests in writing that the Contractor develop change documentation, the effort expended by the Contractor in developing such documentation shall be subject to equitable adjustment, regardless of whether or not the change document is later approved.

(5) In the event the Contractor, on its own initiative, and without written request from the Government, develops a change document that is later approved by the Contracting Officer, the cost of developing such documentation shall be incorporated in the contract modification that implements the change.

(6) Failure to agree to such equitable adjustment in contract price shall constitute a dispute, and shall be adjudicated in accordance with the requirements of the clause entitled "DISPUTES" (FAR 52.233-1).

(g) Any cost reduction proposal submitted pursuant to the clause entitled "VALUE ENGINEERING" (FAR

52.248-1) shall be submitted as a Code V Engineering Change Proposal (VECP). DI-SESS-80639D approved 7

April 2015 and MIL-HDBK-61A of 7 Feb 2001 apply. Information required by the "VALUE ENGINEERING" clause shall also be submitted as part of the change request.

HQ C-2-0023 EXCLUSION OF MERCURY (NAVSEA) (MAY 1998)

Mercury or mercury containing compounds shall not be intentionally added or come in direct contact with hardware or supplies furnished under this contract.

HQ C-2-0059 UPDATING SPECIFICATIONS AND STANDARDS (NAVSEA) (AUG 1994)

If, during the performance of this or any other contract, the contractor believes that any contract contains outdated or different versions of any specifications or standards, the contractor may request that all of its contracts be updated to include the current version of the applicable specification or standard. Updating shall not affect the form, fit or function of any deliverable item or increase the cost/price of the item to the Government. The contractor should submit update requests to the Procuring Contracting Officer with copies to the Administrative Contracting Officer and cognizant program office representative for approval. The contractor shall perform the contract in accordance with the existing specifications and standards until notified of approval/disapproval by the Procuring Contracting

Officer. Any approved alternate specifications or standards will be incorporated into the contract.

Section D - Packaging and Marking

HQ D-1-0001 PACKAGING OF DATA

Data to be delivered by Integrated Digital Environment (IDE) or other electronic media shall be as specified in the contract.

All unclassified data to be shipped shall be prepared for shipment in accordance with best commercial practice.

Classified reports, data, and documentation shall be prepared for shipment in accordance with National Industrial

Security Program Operating Manual (NISPOM), DOD 5220.22-M dated 28 February 2006 with Change 2 dated 18

May 2016.

HQ D-1-0002 PACKAGING LANGUAGE (W/O MILITARY SPECIFICATIONS)

CLINs 0001-0003: The supplies furnished hereunder shall be packaged in accordancewith best commercial practice.

HQ D-2-0004 IDENTIFICATION MARKING OF PARTS (NAVSEA) (NOV 1996)

Identification marking of individual parts within the systems, equipments, assemblies, subassemblies, components, groups, sets or kits, and of spare and repair parts shall be done in accordance with applicable specifications and drawings. To the extent identification marking of such parts is not specified in applicable specifications or drawings, such marking shall be accomplished in accordance with the following:

(1) Parts shall be marked in accordance with generally accepted commercial practice.

(2) In cases where parts are so small as not to permit identification marking as provided above, such parts shall be appropriately coded so as to permit ready identification.

HQ D-2-0006 MARKING AND PACKING LIST(S) (NAVSEA) (NOV 1996)

(a) Marking. Shipments, shipping containers and palletized unit loads shall be marked in accordance with best commercial practice.

(b) Packing List(s). A packing list (DD Form 250 Material Inspection and Receiving Report may be used) identifying the contents of each shipment, shipping container or palletized unit load shall be provided by the

Contractor with each shipment. When a contract line item identified under a single stock number includes an assortment of related items such as kit or set components, detached parts or accessories, installation hardware or material, the packing list(s) shall identify the assorted items. Where assortment of related items is included in the shipping container, a packing list identifying the contents shall be furnished.

(c) Master Packing List. In addition to the requirements in paragraph (b) above, a master packing list shall be prepared where more than one shipment, shipping container or palletized unit load comprise the contract line item being shipped. The master packing list shall be attached to the number one container and so identified.

(d) Part Identification. All items within the kit, set, installation hardware or material shall be suitably segregated and identified within the unit pack(s) or shipping container by part number and/or national stock number.

HQ D-2-0008 MARKING OF REPORTS (NAVSEA) (SEP 1990)

All reports delivered by the Contractor to the Government under this contract shall prominently show on the cover of the report:

(1) name and business address of the Contractor

(2) contract number

(3) contract dollar amount

(4) whether the contract was competitively or non-competitively awarded

(5) sponsor:

(Name of Individual Sponsor)

(Name of Requiring Activity)

(City and State)

UW D-2-0001 MARK FOR INFORMATION (AUG 2017)

(a) The Contractor shall include the following “Mark For” information clearly marked on all packages (or items themselves if they are not packaged) delivered under this contract/order:

Mark For: N66604-TBD

Receiving Officer, Naval Station Newport

47 Chandler Street

Newport, RI 02841-1716

NUWC Division, Newport TO BE PROVIDED AT AWARD

Contract #: N66604-TO BE PROVIDED AT AWARD

UW D-2-0002 PROHIBITED PACKING MATERIALS (MAR 2017)

The use of asbestos, excelsior, newspaper, or shredded paper (all types including waxed paper, computer paper, and similar hygroscopic or non-neutral material) is prohibited. In addition, loose fill polystyrene is prohibited for shipboard use.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

0002 Destination Government Destination Government

0003 Destination Government Destination Government

0004 Destination Government Destination Government

0005 Destination Government Destination Government

0006 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-2 Inspection Of Supplies--Fixed Price AUG 1996

52.246-4 Inspection Of Services--Fixed Price AUG 1996

52.246-16 Responsibility For Supplies APR 1984

HQ E-1-0001 INSPECTION AND ACCEPTANCE LANGUAGE FOR DATA

Inspection and acceptance of all data shall be as specified on the attached Contract Data Requirements List(s), DD

Form 1423.

HQ E-1-0003 INSPECTION AND ACCEPTANCE LANGUAGE FOR F.O.B. DESTINATION DELIVERIES

CLIN) 0001, 0002 AND 0003 - Inspection and acceptance shall be made at destination by a representative of the

Government.

HQ E-2-0004 COST OF QUALITY DATA (NAVSEA) (MAY 1995)

Cost of Quality Data: The contractor shall maintain and use quality cost data as a management element of the quality program. The specific quality cost data to be maintained and used will be determined by the contractor. These data shall, on request, be identified and made available for "on site" review by the Government representative.

HQ E-2-0008 INSPECTION AND TEST RECORDS (NAVSEA) (MAY 1995)

Inspection and Test Records: Inspection and test records shall, as a minimum, indicate the nature of the observations, number of observations made, and the number and type of deficiencies found. Data included in inspection and test records shall be complete and accurate, and shall be used for trend analysis and to assess corrective action and effectiveness.

HQ E-2-0014 QUALITY IN SOFTWARE DEVELOPMENT AND PRODUCTION (NAVSEA) (MAY 1995)

Quality in Software Development and Production: The contractor's software quality program shall be an integral part of the overall Quality Assurance Program. Software quality program controls shall be applicable to all project software that is developed, maintained, or modified within the following categories:

(a) All deliverable software

(b) All deliverable software that is included as part of deliverable hardware or firmware.

(c) Non deliverable software (commercially available or user-developed) used for development, fabrication, testing, or acceptance of deliverable software or hardware (includes automated fabrication, test, and inspection/acceptance equipment software and software design, test, and inspection tools).

(d) Commercially available, reusable, or Government software designated as part of a deliverable item.

HQ E-2-0015 QUALITY MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA) (APR 2017)

Quality Management System Requirements. The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ANSI/ISO/ASQ 9001-2015 Quality Management Systems and supplemental requirements imposed by this contract. The quality management system procedures, planning, and all other documentation and data that comprise the quality management system shall be made available to the Government for review. Existing quality documents that meet the requirements of this contract may continue to be used. The

Government may perform any necessary inspections, verifications, and evaluations to ascertain conformance to requirements and the adequacy of the implementing procedures. The Contractor shall require of subcontractors a quality management system achieving control of the quality of the services and/or supplies provided. The Government reserves the right to disapprove the quality management system or portions thereof when it fails to meet the contractual requirements.

HQ E-2-0017 USE OF CONTRACTOR’S INSPECTION EQUIPMENT (NAVSEA) (MAY 1995)

Use of Contractor’s Inspection Equipment: The contractor's gages, and measuring and testing devices shall be made available for use by the Government when required to determine conformance with contract requirements. If conditions warrant, the contractor’s personnel shall be made available for operations of such devices and for verification of their accuracy and condition.

UW E-2-0001 NOTIFICATION OF INSPECTION OR TEST (MAR 2017)

The Contractor agrees to notify the PCO and COR identified in Clause UW G-2-0002, in writing, when the material will be inspected and/or tested. A minimum of seven working days is required to arrange such a visit.

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 27-SEP-2019 TO

26-SEP-2024

N/A NAVAL INFORMATION WARFARE

CENTER

ATTN: TODD WEBBER

ATTN: TODD WEBBER

4297 PACIFIC HWY

SAN DIEGO CA

N66001

0002 POP 27-SEP-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

0003 POP 27-SEP-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

0004 POP 27-SEP-2019 TO

N/A NAVAL STATION NEWPORT, N66604

RECEIVING OFFICER

SEE CLAUSE UW D-2-0001

--- RI

401-841-3827

N66604

0005 POP 27-SEP-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

0006 POP 27-SEP-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

52.242-15 Stop-Work Order AUG 1989

52.242-17 Government Delay Of Work APR 1984

52.247-34 F.O.B. Destination NOV 1991

52.247-48 F.O.B. Destination--Evidence Of Shipment FEB 1999

52.211-8 TIME OF DELIVERY (JUN 1997)

(a) The Government requires delivery to be made according to the following schedule:

REQUIRED DELIVERY SCHEDULE

CLIN 0001: nine (9) months after order issuance.

CLIN 0002: four (4) months after order issuance.

CLIN 0003: four (4) months after order issuance.

CLIN 0004: per Exhibit “B” as incorporated at the order level.

CLIN 0005: negotiated at time of order issuance.

CLIN 0006: per Exhibit “A” as incorporated at the order level.

A proposal that specifies delivery that will not clearly fall within the applicable required delivery period specified above, may be considered nonresponsive and rejected. The Government reserves the right to award under either the required delivery schedule or the proposed delivery schedule, when an offeror offers an earlier delivery schedule than required above. If the offeror proposes no other delivery schedule, the required delivery schedule above will apply.

OFFEROR'S PROPOSED DELIVERY SCHEDULE

CLIN 0001: OFFEROR TO FILL-IN

CLIN 0002: OFFEROR TO FILL-IN

CLIN 0003: OFFEROR TO FILL-IN

(End of clause)

HQ F-2-0004 F.O.B. DESTINATION (NAVSEA)(APR 2015)

All supplies hereunder shall be delivered with all transportation charges prepaid, in accordance with the clause hereof entitled "F.O.B. DESTINATION" (FAR 52.247-34) in accordance with the delivery instructions specified herein.

The Contractor shall not ship directly to a military air or water port terminal without authorization by the cognizant

Contract Administration Office.

Except when the Material Inspection and Receiving Report (MIRR) (DD 250) is used as an invoice, the Contractor shall enter unit prices on all MIRR copies. Contract line items shall be priced using actual prices, or if not available, estimated prices. When the price is estimated, an "E" shall be entered after the price.

All data to be furnished under this contract shall be delivered prepaid to destination(s) at the time(s) specified on the

Contract Data Requirements List(s), DD Form 1423.

Section G - Contract Administration Data

252.204-7006 Billing Instructions OCT 2005

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

DEC 2018

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area

WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment…