N6660421R0073.pdf

CODE

(Hour)

PAGE(S)

until 12:00 AM local time 09 Feb 2021

X

A

X B

X C X D

EX

X

G

F 56 - 69

70 - 76

X H 77

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 77

(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 1 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

Electronic Delivery via Email conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

3 - 6

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

7 - 23

24 - 25

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

26 - 27

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 29 - 36 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 37 - 38 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

39 - 54

PART II - CO NTRACT CLAUSES

NAVAL UNDERSEA WARFARE CENTER

DYLAN GRIFFIS, CODE 0222

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841-1708

401-832-2092

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

08 Jan 2021

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6660421R0073

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Distribution: FILE, KR, NUWC 01/1532, DCMA: TBD, DFAS: TBD, COR: TBD, PI: TBD, TDAA: TBD NUWCDIVNPT Action Number: 210073

NUWCDIVNPT PID #: N66604-21-RFPREQ-NPT-34-0005

NUWCDIVNPT Requisition Number: 1300848016

NUWCDIVNPT POC: Dylan Griffis (Phone: (401) 832 -2092; Email: dylan.griffis@navy.mil)

This requirement is being solicited on a sole source basis to Systems Engineering Associates Corporation in accordance with 10 U.S.C. 2304(b)(2) in furtherance of the Small Business Act (15 U.S.C. 638).

The North American Industry Classification System (NAICS) Code for this requirement is 541715 and the small business size standard is 500 employees.

The Government’s mimimum guarantee for this requirement is $50,000.00.

mailto:dylan.griffis@navy.mil

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Engineering Services

CPFF

SBIR Phase III labor in accordance with the Statement of Work (see Section C), as specified by issuance of individual orders. The estimated total hours for these services over the duration of the contract is 194,400.

FOB: Destination

PSC CD: AC32

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

ODCs

COST

SBIR Phase III Other Direct Costs in accordance with the Statement of Work (see

Section C), as specified by issuance of individual orders.

The Contractor shall propose a plug cost of $6,274,428 plus applicable burdens. THE OFFEROR SHALL NOT INCLUDE FEE ON BURDENED

ODCS.

PSC CD: AC32

ESTIMATED COST

Data

FFP

The data to be furnished hereunder shall be prepared in accordance with the

Contract Data Requirements List, DD Form 1423, Exhibit "A," attached hereto.

Not Separately Priced

NET AMT

MARK FOR INFORMATION

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 Purchase Order:

Mark For:

Receiving Officer, Naval Station Newport

47 Chandler Street

Newport, RI 02841-1716

NUWC Division Newport Code 34, TBD

Purchase Order #: N66604-21-C-0073

CLAUSES INCORPORATED BY FULL TEXT

B-231-H001 TRAVEL COSTS (NAVSEA) (OCT 2018)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The travel costs to be reimbursed shall be those costs for which the Contractor has maintained appropriate documentation and which have been determined to be allowable, allocable, and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer, or their duly authorized representative.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the

Contractor's or employee's convenience.

(End of text)

B-232-H003 PAYMENTS OF FEE (S) (COMPLETION) (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 equal to percent (TO

BE PROPOSED BY OFFEROR) of the allowable cost of each invoice 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 (percentage of fee payable is based on fee dollars divided by estimated cost dollars including facilities capital cost of money). Fee shall not be applied on Facilities Capital Cost of Money per FAR 15.404-4(c)(3) and DFARS 215-404-71-4. Total fee(s) paid to the

Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, per the clause of this contract entitled "Limitation of Funds" (FAR 52.232-22) or "Limitation of Cost" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) per paragraph (c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

B-232-H004 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--BASIC (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 equal to percent (TO BE PROPOSED BY OFFEROR %) of the allowable cost of each invoice 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

(percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Fee shall not be applied on Facilities Capital Cost of Money per FAR 15.404-4(c)(3) and DFARS 215-404-71-

4. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) The fee(s) specified in SECTION B, and payment thereof, is subject to adjustment pursuant to paragraph (g) of the text entitled Level of Effort. If the fee(s) is reduced and the reduced fee(s) is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the final adjusted fee exceeds all fee payments made to the contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the

Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) per the text entitled Level of Effort", or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

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

STATEMENT OF WORK

(SOW)

Next Generation Electronic Warfare Human Machine Interface (HMI) for Submarines

PR No. 1300848016

1.0 BACKGROUND

The Undersea Warfare Electromagnetic Systems Department (Code 34) of the Naval Undersea Warfare Center

Division Newport (NUWCDIVNPT) is tasked by Navy Systems Commands (SYSCOMs), Type Commanders

(TYCOMs), Navy Cyber Warfare Development Group (NCWDG), Naval Research Lab (NRL), Office of Naval

Intelligence (ONI), Office of Naval Research (ONR), Defense Logistics Agency (DLA), Naval Special Warfare

Development Group (NWDG), United States Special Operations Command (USSOCOM), Naval Cyber Warfare

Command (NCWC), Department of Homeland Security, and other Government Agencies in support of

Electromagnetic Maneuver Warfare. Code 34 is tasked to perform a wide range of programmatic, engineering and technical functions to support the research, design, development, production, fielding, maintenance and improvement of Electronic Warfare (EW) Systems, subsystems, and components including Special projects.

Systems Engineering Associates Corporation was competitively awarded an EW Human Machine Interface (HMI) Phase I Small Business Innovation Research (SBIR) contract (N00024-15-P-4508) by Naval Sea Systems Command

(NAVSEA), followed by a Phase II SBIR contract (N00024-16-C-4530) under topic number N151-036.

NUWCDIVNPT provided technical oversight for these contracts.

The contractor performed successfully under these contracts where the objectives were to:

• Develop an intuitive, responsive, and open HMI system for Submarine EW AN/BLQ-10B (V) for increased operator efficiency and decision-making for submarine operators

• Improve machine-to-operator interfaces in both traditional and innovative displays for operator interaction with data and system functions

• Provide easy integration with new applications, technology, system enhancements, and features to increase operator functionality without increasing the operator/system interaction

• Focus on improved operational performance, effectiveness and operator workload reduction

• Design HMI modules to be able to consume and display organic (data collected from on board sensors) and inorganic (data that originates from off board sensors) data sets of varying types

• Provide Data sets that can range from processed answers (sonar solutions, Electronic Support

Measures (ESM) emitter reports) to raw digital sets (Pulse Descriptor Words (PDW’s), continuous digital intermediate frequency (CDIF), burst digital IF (BDIF), or In-phase / Quadrature (I/Q) data)

This contract provides Phase III tasking related to the original SBIR HMI topic Next Generation EW HMI for

Submarines. The successful Phase I and II development serves as the basis for the definition and development tasks covered by this contract. Having successfully demonstrated the intuitive, responsive, and open HMI system for

Submarine EW, enabling increased efficiency and decision-making for submarine operators, the Navy has a requirement to further transition this demonstrated technology/capability to enhance Navy Undersea, Surface and

Air operational capability addressing EW and Carry-on Special mission areas.

1.1 Places of Performance

It is anticipated this requirement shall be performed at the following locations:

SEA CORP (Middletown, RI)

Naval Undersea Warfare Center (Newport, RI)

On-board US ships and ranges

1.2 Authorized Users

The NUWCDIVNPT Electromagnetic Systems Department, Code 34.

1.3 Sponsors

Code 34 Sponsors anticipated to fund Technical Instructions (TIs) under this contract:

PEO Sub, PMS435

Office of Naval Research (ONR)

Office of Naval Intelligence (ONI)

1.4 Types of Funding

Operations and Maintenance, Navy (O&MN)

Shipbuilding and Conversion, Navy (SCN)

Other Procurement, Navy (OPN)

Research, Development Training and Evaluation, Navy (RDT&EN)

Foreign Military Sales (FMS); Australia and United Kingdom

2.0 SCOPE

Systems developed by different vendors today differ because their requirements and their way of doing business vary, but there is a common functionality and baseline amongst them. The purpose is to develop common capabilities made up by a collection of common software that can be used by multiple product lines while at the same time increase productivity, improve product quality, and increase fleet satisfaction. The contractor shall provide engineering and technical services in support of EW Programs in the area of EW HMI as cited below:

• Develop and maintain common software (SW) components that make up a HMI “common baseline”. Develop new display technologies (HMI) for upgraded EW systems using common architecture and utilizing existing EW HMI baselines.

• Integrate the Plug-in architecture developed in Phase II to obtain a highly configurable and scalable EW product line to support submarine Advanced Processor Build capabilities and ONR and other Science and Technology (S&T) based capability insertion.

• Incorporate various SW libraries and source code developed under Phase II to produce reconfigurable baseline to help the Navy achieve future C2C24/ development (DEV), security

(SEC) and information technology operation (OPS) (DEVSECOPS) requirements.

• Evaluate and integrate related technology (hardware (HW)/ SW) for upgraded EW HMI systems to expand existing EW HMI baseline from various sources including:

- NAVSEA Integrated Product Teams (IPT) Structure (Advanced Processor Build (APB)

Process)

- Industry sources

- Other government sources (NAVY / NAVAIR / ONI / PEO IWS5A / Applied Physics

Laboratory John Hopkins University (APLJHU))

• Provide engineering and technical support for troubleshooting and testing of deployed tactical and lab based system that use the EW HMI baseline

• Manage and maintain software configuration baselines including:

- SW configuration management (CM)

- SW / System Problem Trouble Report databases

- Tools

- Documentation

- Test Scenarios

- Automated Test

• Support land based and at-sea demonstrations

The scope of the tasking delineated within this contract also includes production, production support and fielding of related HMI improvements. During the execution of this Phase III contract, the Navy requirements for EW HMI related efforts will support undersea warfare platforms (Submarines, Un-manned Undersea Vehicles (UUV), etc.), as well as EW Air Warfare (P3, Un-manned Ariel Vehicles), and new surface warfare platforms (including future ships such as Littoral Combat Ship (LCS) new destroyer DD (X), and Unmanned Surface Vessels (USVs). Applications include, but are not limited to, several mission areas such as undersea warfare, surface warfare Special Operations

Forces (SOF), and Intelligence Surveillance and Reconnaissance (ISR).

3.0 APPLICABLE DOCUMENTS

The contractor shall perform the tasking required in Section 4.0 in accordance with the below Applicable

Documents (AD).

NUMBER TITLE TASK NUMBER

3.1 MIL-STD-461G, DoD Interface Standard; Requirements for Control of Electromagnetic Interference, Characteristics of

Subsystem and Equipment, 11 December 2015

4.3, 4.4, 4.5

3.2 MIL-STD-1399C, Interface Standard for Shipboard

Systems, 2 February 1988

4.3, 4.4, 4.5

3.3 MIL-STD-882E; DoD Standard Practice System Safety, 11 May 2012 4.3, 4.4, 4.5, 4.6

3.4 MIL-STD-31000B DoD Standard Practice Technical Data Packages 31

October 2018

4.6

3.5 MIL-HDBK-61A(SE) Configuration Management Guidance, 07

February 2001

4.2, 4.3, 4.4, 4.5

3.6 ASME Y14.24-2009 Types of Application of

Engineering Drawings, 2012 www.asme.org

4.2, 4.6

3.7 ASME Y14.100

Engineering Drawing Practices, 2013

4.2, 4.6

3.8 ASME Y14.35 Revision of Engineering Drawings and Associated

Documents, 2014

4.2, 4.6

3.9 NAVSEA INSTRUCTION 4720.14E, Temporary

Alterations to Fleet Submarines, 4 March 2014

4.3, 4.4, 4.5

3.10 NAVSEA S9070-AA-MME-010/SSN/SSBN Technical Requirements

Manual For Temporary Submarine Alterations, 18 January 2005

4.2, 4.3, 4.4, 4.5, 4.6

3.11 Code 34 Organizational Software Process Manual, Rev 1.6, 12

September 2017

4.2, 4.3, 4.4, 4.5, 4.6

3.12 Capability Maturity Model Integration (CMMI), Version 2.0, March https://cmmiinstitute.com/

4.2, 4.3, 4.4, 4.5, 4.6

3.13 IEEE 12207.0-1996 – International Standard for Information

Technology - Software Life Cycle Processes, 1996 www.ieee.org

4.2, 4.3, 4.4, 4.5, 4.6

3.14 Code 34, Software Quality Assurance Plan (SQAP), Rev 1, 12 September 2017

4.2, 4.3, 4.4, 4.5, 4.6

3.15 DoD Instruction 8500.01 Cybersecurity, 14 March 2014 4.4

3.16 DoD Instruction 8500.2, Information Assurance (IA) Implementation, 6 February 2003

4.4

3.17 OPNAV Instruction 5239.1C, Navy Information Assurance (IA)

Program, 20 August 2008

4.4

3.18 DoD 8570.01-M, Information Assurance Workforce

Improvement Program, Incorporating Change 4, 10 November 2015

4.4

3.19 SECNAV Instruction 5239.20A, DoN Cyberspace Information

Technology and Cybersecurity Workforce Management and

Qualification, 10 February 2016

4.4

3.20 NAVSEA Standard Item 009-04, Quality Management System; provide, 01 October 2017

4.2, 4.3, 4.4, 4.5, 4.6

3.21 NAVSEA SL720-AA-MAN-010/020 Rev 2 Fleet

Modernization Program Management and Operation Manual, 1 June 2002

4.2, 4.3, 4.4, 4.5, 4.6

4.0 TECHNICAL REQUIREMENTS

The following tasks shall be accomplished in accordance with Applicable Documents (ADs) in Section 3.0. These tasks shall be performed using Government Furnished Information (GFI) identified in Section 6.0 and in accordance with Task and Delivery Orders, and Technical Instructions (TIs).

4.1 PROGRAM PLANNING AND SYSTEM DEFINITION

The Contractor shall develop program plans, schedules, and cost estimates related to the definition, development, test, deployment, and evaluation of EW HMI enhancements and associated EW systems technology. The Contractor shall collect and analyze data from existing HMI applications for EW to be used as the basis for further evaluating the transition of the EW HMI technology applications proven under SBIR Phase I and Phase II contracts to undersea, air and surface EW systems.

Deliverables:

CDRL A001 DI-IPSC-81430A: Operational Concept Description

CDRL A002 DI-MISC-80508B: New Capabilities and Systems Gap Analysis Report

4.2 CONFIGURATION MANAGEMENT DEVELOPMENT AND MAINTENANCE

On a continuing basis, the contractor shall provide EW HMI software configuration management development and maintenance of the software under development in support of land-based testing, technology evaluation, temporary alterations and deployed systems. The contractor shall develop, distribute and maintain software common HMI baselines based on inputs from various development areas (Industry and Government). The contractor shall develop and maintain the common HMI baseline, identifying changes to hardware, software, and documentation configurations. The contractor shall post newly developed common HMI baselines to a Integrated Development

Environment (IDE) to allow for community review and utilization.

The contractor shall coordinate and participate in Configuration Control Board (CCB) and comment review meetings to adjudicate comments from government, other industry developers, and users of the EW HMI to common HMI baseline, and shall update common HMI baseline upon Government approval of CCB comments.

The contractor shall submit the updated common HMI baseline to the sponsor activity for final approval signatures and then post final common HMI baseline to the IDE. The contractor shall track and document the status of all common HMI baseline related to the system baselines.

CDRL A003 DI-ADMN-80925A: Revision to Existing Government Documents (Common HMI Baseline Reports)

4.3 SYSTEM/SOFTWARE ENGINEERING

The Contractor shall design and develop new configurable HMI display technologies for upgraded EW baselines independent of the radio frequency (RF) source or format using common architecture and utilizing existing GFI 6.1 and 6.2. The contractor shall design and develop software code and executable software modules for the EW

System and ancillary equipment such as communication, sensor payload, and Special Project systems and components based on the common EW HMI baseline. The contractor shall design and develop the common HMI interface to be configurable for multiple platforms types and users without making software changes. The

Contractor shall develop test code and simulators software. The Contractor shall develop a Software Development Plan (SDP).

The Contractor shall review, develop, adapt, modify, and maintain System Requirements Verification Matrix

(SRVM), Software Requirement Specifications (SRS), Database Design Documents (DBDD), Software Design

Descriptions (SDD), Software Test Plans (STP), Software Test Descriptions (STD), Software Test Reports (STR), Software Product Specifications (SPS), and Software Version Descriptions (SVD) in support of EW HMI production, simulation, and prototype code.

CDRL A004 DI-IPSC-81427B: Software Development Plan (SDP)

CDRL A005 DI-IPSC-81431A: System/Subsystem Specification (SSS)

CDRL A006 DI-IPSC-81433A: Software Requirement Specifications (SRS)

CDRL A007 DI-IPSC-81437A: Database Design Documents (DBDD)

CDRL A008 DI-IPSC-81435A: Software Design Descriptions (SDD)

CDRL A009 DI-IPSC-81438A: Software Test Plans (STP)

CDRL A00A DI-IPSC-81439A: Software Test Descriptions (STD) CDRL A00B DI-IPSC-81440A: Software Test Reports (STR)

CDRL A00C DI-IPSC-81441A: Software Product Specifications (SPS)

CDRL A00D DI-IPSC-81442A: Software Version Descriptions (SVD)

4.4 DEVELOP BUILD ENVIRONMENT

The contractor shall utilize the Plug-in architecture developed in Phase II to develop a highly configurable and scalable EW HMI product line to support submarine APB capabilities and ONR and other S&T based capability insertion. The contractor shall deliver software and configuration management tools to developers to help in achieving upcoming software DEVSECOPS requirements.

The contractor shall comply with local NUWCDIVNPT COMSEC policies in the performance of their duties as a

COMSEC user. The contractor shall report completion of any COMSEC user tasking to the lab manager (or alternate) via E-mail or verbally. The contractor shall immediately report any COMSEC related issues to their

Government lab manager or a NUWCDIVNPT COMSEC Account Manager (CAM) if the lab manager is not available

CDRL A00E DI-IPSC-81488: Computer Software Product

4.5 BUILD PROTOTYPE

The Contractor shall provide mechanical, electrical, and RF engineering services for the development of hardware and software for EW HMI baseline and interfaces with other equipment. The prototype development shall address required Server, Controls and Displays platform unique configurations, System/Subsystem interfaces, System/Subsystem Command and Control, RF distribution, and Antenna Control.

The Contractor shall fabricate, build, and assemble reduced and full-scale models, mock-ups, prototypes, pre-production units, and research and development (R&D) test tools utilizing the common HMI baseline. The

Contractor shall prepare and provide Test Plans and Test Procedures for Government review and approval, to test the common HMI baseline models, mock-ups, prototypes, pre-production units, and R&D test tools. Upon

Government approval of the Test Plans and Test Procedures, the Contractor shall test, operate and evaluate the reduced and full-scale models, mock-ups, prototypes, and pre-production units of the common HMI baseline. The

Contractor shall deliver Certificates of Compliance and Certification/Data Report with each delivered item.

The contractor shall comply with local NUWCDIVNPT COMSEC policies in the performance of their duties as a COMSEC user. The contractor shall report completion of any COMSEC user tasking to the lab manager (or alternate) via E-mail or verbally. The contractor shall immediately report any COMSEC related issues to their

CDRL A00F DI-NDTI-80566A: Test Plans

CDRL A00G DI-NDTI-80603A: Test Procedures

CDRL A00H DI-MISC-81356A: Certificate of Compliance

CDRL A00J DI-MISC-80678: Certification/Data Report

4.6 INTEGRATION TESTING

The Contractor shall provide land-based, platform and baseline integration design for EW HMI baseline and interfaces with other equipment such as communications equipment, sensor payloads, and Special Project components. The Contractor shall perform requirements analysis, End-to-End Analysis, and implement information assurance into the designs. The Contractor shall prepare Technical Data Packages, Notice of Revisions (NORs), Engineering Change Proposals (ECPs), alterations, and prototypes of the final designs.

Using applicable performance specifications provided as GFI in individual TOs and TIs, the Contractor shall conduct and monitor baseline engineering processing and testing events. The Contractor shall review the results of these tests; document each test step; and perform analysis to assess whether the results are within the acceptable parameters as defined in the performance specifications.

The contractor shall comply with local NUWCDIVNPT COMSEC policies in the performance of their duties as a

COMSEC user. The contractor shall report completion of any COMSEC user tasking to the lab manager (or alternate) via E-mail or verbally. The contractor shall immediately report any COMSEC related issues to their

CDRL A00K DI-SESS-80639D: Engineering Change Proposal (ECP) CDRL A00L DI-SESS-80776A: Technical Data Package (TDP)

CDRL A00M DI-SESS-80642D: Notice of Revision (NOR)

5.0 PROGRESS REPORTS

The contractor shall prepare a Contractor’s Status Report that indicates the progress of work, status of the program(s), and existing or potential problem areas for all assigned tasks. The contractor shall submit the Contract

Status Report for the same timeframe as each invoice submitted in the Wide Area Workflow (WAWF) Module of the Procurement Integrated Enterprise Environment (PIEE).

Deliverable:

CDRL A00N DI-MGMT-81991: Contract Status Report

6.0 GOVERNMENT FURNISHED INFORMATION

The following Government Furnished Information (GFI) will be made available under this contract:

Number Title Task Number

6.1 Toolkit All

Baseline Template Library Reference Manual

Common Lists Reference Manual

DDS Library Reference Manual

Formatting Template Library Reference Manual

Plugin Framework Guide

Plugin Library Reference Manual

6.2 Source Code All

baseline-template-lib.tar.gz common-list-hmi.tar.gz dds-lib.tar.gz format-template-lib.tar.gz material-design-lib.tar.gz plugin-lib.tar.gz

6.3 Common Lists Redesign HMI All

6.4 GRASP Display and Control Manager CSCI SDD 4.3

6.5 GRASP Display and Control Manager CSCI SRS 4.3

6.6 GRASP HMI System Test Plan 4.3, 4.5

6.7 GRASP Map Manager CSCI SDD 4.3

6.8 GRASP Map Manager CSCI SRS 4.3

7.0 QUALITY SURVEILLANCE AND PERFORMANCE STANDARDS

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, cost control, schedule/timeliness, management, utilization of small business, and regulatory compliance as follows:

Technical Quality: The Government will evaluate technical quality using the criteria defined in the Performance Requirements Summary Table (PRST), Attachment 2;

Cost Control: The Government will evaluate the contractor’s effectiveness in forecasting, managing, and controlling actual costs in comparison to negotiated costs;

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;

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 COMPLIANCE WITH INFORMATION AND COMMUNICATION TECHNOLOGY

ACCESSIBILITY REQUIREMENTS

The Government has determined that this procurement is compliant with the Information and Communication

Technology (ICT) Accessibility Standards (36 C.F.R. § 1194.3 - Chapter 2 E202 General Exceptions of Section 50 Refresh). The applicable EIT Accessibility Standards are:

36 C.F.R. § 1194.21 (Chapter 5) - Software Applications and Operating Systems

36 C.F.R. § 1194.26 (Chapter 4) - Desktop and Portable Computers

36 C.F.R. § 1194.41 (Chapter 6) - Information, Documentation, and Support

C-202-H001 ADDITIONAL DEFINITIONS–BASIC (NAVSEA) (OCT 2018)

(a) Department - means the Department of the Navy.

(b) Commander, Naval Sea Systems Command - means the Commander of the Naval Sea Systems Command of the

Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) - All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers - Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National

Stock Number (NSN) respectively which shall be defined as follows:

(1) National Item Identification Number (NIIN). The number assigned to each approved Item

Identification under the Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit non-significant number.

(2) National Stock Number (NSN). The National Stock Number (NSN) for an item of supply consists of the applicable four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

C-204-H002 IMPLEMENTATION OF ENHANCED SECURITY CONTROLS ON SELECT DEFENSE

INDUSTRIAL BASE PARTNER NETWORKS (NAVSEA) (JAN 2020)

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

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The

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

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

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

POAM.

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

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

Contractor.

2. Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant

Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a

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

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

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

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

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

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

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e.

FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

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

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

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

3. Cyber Incident Response

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3)

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

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification.

The contracting officer will approve or disapprove the request after coordination with DC3.

4. Naval Criminal Investigative Service (NCIS) Outreach

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

5. NCIS/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the

Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the

Contractor.

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

d) Recommended Number (IAW FAR 52.1 and DFARS 252.103):

End of Text)

C-211-H016 SPECIFICATIONS AND STANDARDS (NAVSEA) (OCT 2018)

(a) Definitions.

(i) A "zero-tier reference" is a specification, standard, or drawing that is cited in the contract (including its attachments).

(ii) A "first-tier reference" is either: (1) a specification, standard, or drawing cited in a zero-tier reference, or (2) a specification cited in a first-tier drawing.

(b) Requirements. All zero-tier and first-tier references, as defined above, are mandatory for use. All lower tier references shall be used for guidance only unless specifically identified below.

None

C-211-H017 UPDATING SPECIFICATIONS AND STANDARDS (NAVSEA) (DEC 2018)

The contractor may request that this contract be updated to include the current version of the applicable specification or standard if the update does 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 of its request to update by the Procuring Contracting Officer. Any approved alternate specifications or standards will be incorporated into the contract.

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the

Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

C-223-W002 ON-SITE SAFETY REQUIREMENTS (NAVSEA) (OCT 2018)

(a) The contractor shall ensure that each contractor employee reads any necessary safety documents within 30 days of commencing performance at any Government facility. Required safety documents can be obtained from the respective safety office. Contractors shall notify the Safety office points of contact below to report completion of the required training via email. The email shall include the contractor employee’s name, work site, and contract number.

(b) It is expected that contractor employees will have received training from their employer on hazards associated with the areas in which they will be working and know what to do in order to protect themselves. Contractors are required to adhere to the requirements of 29 CFR 1910, 29 CFR 1926 and applicable state and local requirements while in Government spaces. The contractor shall ensure that all on-site contractor work at the Government facility is in accordance with any local safety instructions as provided via the COR. The contractor shall report all work-related injuries/illnesses that occurred while working at the Government site to the COR.

(c) Contractors whose employees perform work within Government spaces in excess of 1000 hours per calendar quarter during a calendar year shall submit the data elements on OSHA Form 300A, Summary of Work Related

Injuries and Illnesses, for those employees to the safety office, via the COR by 15 January for the previous calendar year, even if no work related injuries or illnesses occurred. If a contractor’s injury/illness rates are above the Bureau of Labor Statistics industry standards, a safety assessment may be performed by the Safety Office to determine if any administrative or engineering controls can be utilized to prevent further injuries/illnesses, or if any additional

Personal Protective Equipment or training will be required.

(d) Any contractor employee exhibiting unsafe behavior may be removed from the Government site. Such removal shall not relieve the contractor from meeting its contractual obligations and shall not be considered an excusable delay as defined in FAR 52.249-14.

(e) The Safety Office points of contacts are as follows:

TBD

C-227-H006 DATA REQUIREMENTS (NAVSEA) (OCT 2018)

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.

(End of Text)

C-227-H007 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (OCT 2018)

(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall be delivered to the Government for concurrence under

CDRL A004 and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior

Government concurrence.

(b) The SDP shall, at a minimum:

(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE Std. 12207:2017;

(2) Contain the information defined by ISO/IEC/IEEE 15289:2017, section 7.3 “Plan - generic content” and

Table 2 “Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software

Life Cycle Process.” In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted for this contract;

(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;

(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and

Organizational life cycle processes as defined by IEEE Std. 12207:2017 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;

(5) Adhere to the characteristics defined in ISO/IEC/IEEE 15289:2017 section 6.1 “Life-cycle data characteristics,” as appropriate;

(6) Be in accordance with the framework defined in IEEE Std. 12207:2017, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks;

(7) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with ISO/IEC/IEEE 15289:2017 Section 7.3, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.

C-227-H008 GOVERNMENT-INDUSTRY DATA EXCHANGE PROGRAM (NAVSEA) (DEC 2018)

(a) The contractor shall actively participate in the Government Industry Data Exchange Program in accordance with the GIDEP Operations Manual, S0300-BT-PRO-010. The contractor shall submit information concerning critical or major nonconformances, as defined in FAR 46.407/DFARS 246.407, to the GIDEP information system.

(b) The contractor shall insert paragraph (a) of this clause in any subcontract when deemed necessary. When so inserted, the word "contractor" shall be changed to "subcontractor."

(c) The contractor shall, when it elects not to insert paragraph (a) in a subcontract, provide the subcontractor any

GIDEP data which may be pertinent to items of its manufacture and verify that the subcontractor utilizes any such data.

(d) The contractor shall, whether it elects to insert paragraph (a) in a subcontract or not, verify that the subcontractor utilizes and provides feedback on any GIDEP data that may be pertinent to items of its manufacture."

(e) GIDEP materials, software and information are available without charge from:

GIDEP Operations Center

P.O. Box 8000

Corona, CA 92878-8000

Phone: (951) 898-3207

FAX: (951) 898-3250

Internet: http://www.gidep.org

C-227-H010 COMPUTER SOFTWARE AND COMPUTER DATA BASES DELIVERED TO OR RECEIVED

FROM THE GOVERNMENT (NAVSEA) (JAN 2019)

(a) The Contractor agrees to test for viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4, in all computer software and computer data bases (as defined in the clause entitled “Rights In Noncommercial

Computer Software and Noncommercial Computer Software Documentation” (DFARS 252.227-7014)), before delivery of that computer software or computer data base in whatever media and on whatever system the computer software or data base is delivered whether delivered separately or imbedded within delivered equipment. The

Contractor warrants…