N6660421R0100.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 22 Feb 2021

X

A X B X C X D

EX

X

G F 72 - 88

89 - 99 X H 100 - 101

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 101

(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

Not Authorized 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

2 - 4

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

5 - 26 27 - 28

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

29 - 31

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 33 - 40 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 41 - 46 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 - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

47 - 70

PART II - CONTRACT CLAUSES

NAVAL UNDERSEA WARFARE CENTER

MICHAEL NORMAN OUELLETTE , CODE 0221

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841-1708

401-832-5568

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

21 Jan 2021

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6660421R0100

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Job DARTS Engineering Services

CPFF

Services in accordance with Statement of Work in Section C, as specified by issuance of individual orders..

Estimated number of Hours: 258,330.

FOB: Destination

PSC CD: AC34

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 1 Lot

ODC

FFP

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 $1,391,361.00 plus applicable burdens. THE OFFEROR SHALL NOT INCLUDE FEE ON BURDENED

ODCS.

NET AMT

0003 1 Lot

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.

NET AMT

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 TO BE PROPOSED BY OFFEROR 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-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

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

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

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

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

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF

WORK (SOW)

Data Acquisition and Retrieval System (DARTS) PR No. 1300759772

1.0 Background

NUWCDIVNPT is responsible for the conduct of system performance, certification, calibration and developmental testing for new construction/acquisition programs and in-service Command, Control, Communications and Intelligence (C3I) System technology refresh and technology insertion efforts. Programs include the VIRGINIA (SSN 774) Class Submarine Program and its Non-Propulsion Electronics System (NPES), the OHIO Class and Columbia Class Submarine Programs, and associated in-service programs that include sonar, combat control, external communications systems, imaging, electronic warfare systems, navigation, TOMAHAWK Weapons Systems, Naval Special Warfare systems, VIRGINIA Payload Tube (VPT), and VIRGINIA Payload Module (VPM) including associated weapon payloads. Test events include Weapons System Accuracy Trials (WSAT), VIRGINIA Warfare Material Certification Program (VWMCP), Submarine Warfare Federated Tactical Systems (SWFTS) certification testing, Weapons Compatibility Testing, Sensor Accuracy Trials, array calibrations, Cybersecurity developmental testing, and acquisition program Development Testing (DT). These test programs and events will hereafter be referred to as the NUWC Test Program. Application of this technology to Operational Test (OT) support may also be required when requested by Commander Operational Test and Evaluation Force (COMOPTEVFOR) and directed by the acquisition program office.

Progeny Systems Corporation (PSC) was awarded a Phase III Small Business Innovation Research (SBIR) contract to mature the Automated Testing Systems (ATS) developed under the Phase II SBIR contract into test instrumentation packages to support the NUWC Test Program. These test instrumentation packages evolved into the Data Acquisition and Retrieval System (DARTS) and associated engineering and technical services. DARTS includes a set of hardware and software that is utilized in the laboratory, at the Command and Control Module Off-Hull Assembly, and Test Site (COATS), and shipboard to support the NUWC Test Program. A follow-on Phase III SBIR contract was awarded in 2015 for continued development and support. It is installed shipboard via a TEMPALT and must meet the requirements of the Joint Fleet Maintenance Manual (Applicable Document 3.1).

DARTS provides a capability to provide real time analysis and data collection during NPES testing.

Under this procurement the contractor will continue the application of this technology and engineering services to the NUWC Test Program. The contractor shall maintain and tailor DARTS to the needs of each NUWC Test Program test event. The contractor shall integrate Government and commercial off-the-shelf (GOTS and COTS) and non-developmental item (NDI) products to reduce cost where possible.

The objective of this contract is to continue the application of this ATS technology to support the NUWC Test Program. This includes conduct of testing to support combat system and Special Operating Force SOF system certifications and to complete DT in support of proceeding to OT.

1.1 Places of Performance

The contractor shall perform the required work in its facilities, government and other contractor labs and facilities, and on-board US ships and ranges.

1.2 Authorized Users/Programs

The following NUWCDIVNPT Departments will use this contract: Code 25, Code 15 in the area of sonar data, and Code 34 in the area of phonics mast data.

The following NUWCDIVNPT Programs may use this contract: Virginia Class Submarine, AN/BQQ-10 Acoustic Rapid COTS Insertion (ARCI), AN/BYG-1 Combat Control, Virginia Class Photonics Mast Program, OHIO Class Submarine and the Columbia Class Submarine Program.

1.3 Sponsors

The following NUWCDIVNPT Sponsors may use this contract: PMS 450, PMS401, PMS415 PMS 425, PMS 435, and PMS 397.

1.4 Types of Funding

The following types of funding may be utilized on this contract: Research, Development, Test and Evaluation (RDT&E); Operation and Maintenance, Navy (O&MN); and Ship Conversion, Navy (SCN).

2.0 Scope

The contractor shall apply the DARTS and associated processes to collect and analyze platform, NPES and C3I data for the NUWC Test Program. The contractor shall tailor the DARTS to the needs of the individual test events, provide DARTS installation and removal services and operational support for test events, establish and manage DARTS test database, provide configuration management of DARTS variants, and maintain and store the DARTS equipment.

DARTS variants shall include a complete set of hardware, software, documentation and lifecycle maintenance and support items to support the NUWC Test Program and meet the installation requirements in accordance with Applicable Document 3.1.

The contractor shall utilize the DARTS to provide Subsystem test, evaluation, integration, engineering, technical, and DARTS technical services to NUWC and other Navy activities and organizations to perform required system level testing to government approved test procedures, software/hardware testing, systems engineering, integration, installation, and certification of Submarine combat system related electronics during new construction and at the Command and Control Module Off-Hull Assembly and Test Site (COATS) to assess the requirements documented in Applicable Documents 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.10 and 3.12.

3.0 Applicable Documents

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

Number Title Task Number

3.1

COMUSFLTFORCOMINST 4790.3B Joint Fleet Maintenance Manual (JFMM), Revision D, 16 October

4.2, 4.3

3.2

NAVSEAINST 9093.5, Integrated Combat Systems Certification and Assessment Program For All Submarines, 8 May 2020

4.1, 4.4

3.3 VIRGINIA (SSN 774) Class Test and Evaluation Master Plan, (TEMP)(Series)

4.1, 4.4

3.4 NAVSEA Total Ship Test Program Manual (NAVSEA S9095-AD-TRQ-010/TSTP), 3 March

4.4

3.5 NAVSEAINST 3960.5 (series) Policy on Ship Test 4.4

3.6

VIRGINIA (SSN 774) Class Submarine Operational Requirements Document, Revision A, Change 2, 27 October 2009

4.1, 4.4

3.7

Capability Development Document for VIRGINIA (SSN

774) Class Submarine Strike Capability, Change 1, 17 December 2013

4.1, 4.4

3.8 DOD Directive 8500.2, Information Assurance (IA) Implementation, February 6, 2003

4.1, 4.2

3.9

NATO – ANEP-82, Message Specification for Data Link Between Combat Management Systems and IDATS, 14 October 2019

4.2, 4.4

3.10 DOD 5220.22-M, National Industrial Security Program Operating Manual, Change 2, 18 May 2016

4.1, 4.6

3.11

OPNAV INST 3600.3C Policy for the Material and Tactical Certification of Cruise Missile Capable Surface Ships and Submarines, 16 February 2018

4.4

3.12

COMUSFLTFORCOM/COMPACFLT INSTRUCTION

6320.3B, Medical Screening for U.S. Government Civilian Employees, Contractor Employees, Guest and Visitors prior to Embarking Fleet Units, 7 April 2014

4.1

3.13

NAVSEAINST 9400.2A, NAVSEA Platform Information Technology-Control Systems Cybersecurity Governance And Guidance

4.1

3.14 SECNAVINST 5239.3C, Department Of The Navy Cybersecurity Policy

4.1

3.15 DoD Instruction 5000.02 Operation of the Defense Acquisition System

4.1

3.16 DoD 8570.01-M, Information Assurance Workforce Improvement Program; November 10, 2015 Rev M

4.1, 4.4

3.17

National Environmental Policy Act (NEPA) and Executive Order (E.O.) 12114, Environmental Effects Abroad of Major Federal Actions

4.4

3.18 OPNAVINST 5090.1D, Environmental Readiness Program, 10 January 2014

4.4

3.19

NAVSEAINST S5510.18 Security Policy for Stealth Performance Data with Alternative Compensatory Control Measures (ACCM) , 10 May 2013

4.5

3.20 Program Management Plan (PMP), December 18, 2014 4.5

3.21 Software Management Plan (SDP), December 18, 2014 4.5

3.22 Configuration Management Plan (CMP), December 18, 4.5

3.23 VIRGINIA (SSN 774) Class Submarine Test and Evaluation Data Management Plan, 15 January 2014

4.5

3.24 COMSUBLANT/COMSUBPAC OPORD 2000 , Revision A with ACN 22-1, 9 August 2012

4.2

3.25

COMSUBLANT/COMSUBPACINST C3120.26A,

Submarine Operations Manual, Change 4 with ACN 2-5, 24 October 2017

3.26

AUTEC Range Safety Manual NUWCDIVNPTINST

5100.6 M, 27 July 2020

4.2

3.27 NATO STANDARD AXP-01, Allied Submarine and Anti-Submarine Exercise Manual, Edition E, Version 4

3.28

OPNAVINST C8510.14A, Clearance and Authorization for Use of Submarines as Exercise Torpedo Targets, 20 December 1990

3.29

OPNAVINST C8510.15C, Change 3, Torpedo MK48 ADCAP Fleet Peacetime Firing Policy, 26 August 2013

4.2

3.30 COMSUBLANT OPORD 2148, Revision A with ACN 1- 1, 13 April 2009

3.31

Promulgation of Submarine Clearance Authorization and Restrictions for Submarine Force Atlantic COMSUBLANT Notice 3120

3.32

COMSUBLANT/COMSUBPAC INSTRUCTION

8500.4D, Submarine Force Conventional Weapons Manual, Change 1, 10 March 2020

4.0 Technical Requirements

The contractor shall perform the following tasks to support assessment of system performance, certification, and developmental testing for new construction/acquisition programs and in-service Command, Control, Communications and Intelligence (C3I) System technology refresh and technology insertion efforts for the Navy.

In accordance with Task Order (TO) Statements of Work (SOWs), Applicable Documents (ADs), and using Government Furnished Information (GFI), the contractor shall provide the services below. The ADs are relevant to the tasks and subtasks for which they are identified in section 3.0

4.1 DARTS Development

The contractor shall design and modify the DARTS system to be compatible for installation onboard VIRGINIA (SSN 774) Class and in-service submarines being constructed or going through a post shakedown availability (PSA). This effort will require DARTS systems updates for future Technology Insertions (TIs) and Advanced Processing Builds (APBs) that will be installed on the Virginia Class Submarines. The scope of the updates can be variable and will be determined by the TI and APB interface changes, message changes, or data base schema. The contractor shall upgrade the DARTS hardware and software requirements and integrate the DARTS system into NPES or C3I System configurations under test to meet the data collection capabilities required to assess the requirements documented by Applicable Documents 3.2, 3.3, 3.6, 3.7, 3.8, 3.10 and 3.12. Software shall be developed in accordance with CDRL A010-DI- IPSC-81443A. The specific content of the Test Instrumentation Package (TIP) will vary as a function of ship class and combat system configuration, but in general will be comprised of the DARTS and its interface with the Digital Data Collection System (DDCS) embedded in the test platforms tactical systems.

The contractor shall attend TEMP Working Group Meetings and Cybersecurity Working Group meetings to gain detailed insight to design in accordance with Applicable Documents 3.3, 3.13, 3.14, 3.15, and 3.16. Meeting minutes will be prepared in accordance with CDRL A009- DI-

ADMN-81505

The Contractor shall develop and maintain a remote test instrumentation capability that provides a remote DARTS maintenance, calibration, and upgrade capability during dockside Submarines test events. The contractor shall prepare technical reports shall be prepared in accordance with CDRL A001- DI-MISC- 80508B and A002-DI-MISC-80652.

4.2 Test Preparation

The contractor shall prepare a DARTS variant to support test events identified by NUWC and shall verify that the DARTS will meet the data collection requirements for the test events. All hardware components shall meet Navy Grade B shock requirements as detailed in Applicable Document 3.1. All software and installations developed under this effort shall meet the Navy’s Information Assurance (IA) requirements as detailed in Applicable Document 3.8 and NATO interface requirements detailed in Applicable Document 3.9.

The contractor shall maintain Configuration Management of each DARTS variant in use. The contractor shall provide the Government with a configuration description and list of equipment of DARTS in use.

The contractor shall conduct DARTS demonstrations at NPES, Combat System Vendors and Command and Control Module Off-Hull Assembly, and Test Site (COATS) facilities in preparation for test conduct. Multiple test sessions at the COATS or an equivalent facility may be required in preparation for platform installation. The Government will provide the contractor with a Test Plan in accordance with CDRL A003- DI-NDTI-80566A for each test event that defines the framework of the required testing. The contractor shall develop a Government approved test procedure in accordance with CDRL A004- DI-NDTI-80603A for execution of the Government requirements in accordance with Applicable Documents 3.24-3.32.

4.3 Installation and Removal

The contractor shall provide the DARTS for installation on the VIRGINIA Class Submarine or in-service submarines designated to support the test events identified by NUWC. The contractor shall provide the engineering, technical and support services required to install and test the DARTS on the test platform in accordance with Applicable Documents 3.1. The contractor shall work with the NUWC designated TEMPALT activity to support installation, removal, and shipping of DARTS. Engineering Drawings shall be prepared in accordance with CDRL A006 – DI-DRPR-80651, Development Design Drawings/Models and Associated Lists shall be prepared in accordance with CDRL A007 – DI-SESS-81002F, and Test Inspection Reports shall be prepared in accordance with CDRLA008-DI-NDTI-80809B.

4.4 Test Conduct and Test Training

In accordance with the Test Plans and Procedures of 4.2, the contractor shall use DARTS during dockside and at-sea test periods to conduct system performance assessment, certification, and developmental testing to collect the data required to assess the requirements documented in Applicable Documents 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.9, and 3.11. This shall include training

NUWC Test Team members on DARTS operation and maintenance during test events. The contractor shall also support Cybersecurity developmental testing which includes vulnerability assessments and penetration testing TI/APB builds for the VIRGINIA and COLUMBIA Class Programs. All contractor Cybersecurity Workforce (CSWF) personnel conducting the cybersecurity tasking identified herein, shall meet the requirements specified in DoD 8570.01-M, Applicable Document 3.2.16, for an Information Assurance Technical (IAT) workforce member level II (IAT II). Prior to commencing work, the CSWF personnel performing the cybersecurity tasking shall receive a Command appointment letter and meet the IAT II requirements including:

baseline certification and linux operating system (OS)/computing environment (CE) certification.

The CSWF personnel shall maintain their certification status and sustain continuous learning requirements. Technical reports shall be prepared in accordance with CDRL A001- DI-MISC- 80508B and A002-DI-MISC-80652. Training materials shall be prepared in accordance with

CDRL A005- DI-ILSS-80872.

The Contractor shall adhere to all Environmental Protection Agency (EPA) Regulations in as identified in Applicable Documents 3.17 and 3.18.

4.5 Data Management, Analysis and Reporting

The contractor shall maintain two databases for test data.

The first database currently consists of DARTS baseline configurations. The contractor shall update and maintain the configuration baseline to reflect DARTS system changes as specified by tasking under SOW 4.2. The contractor shall maintain DARTS Configuration Management and Life Cycle Support as documented in Applicable Documents 3.20, 3.21, and 3.22.

The other database will be maintained to collect NPES and C3I system test data elements in accordance with Applicable Document 3.23. The contractor’s ability to collect and report on test data elements (a dynamic process driven by continual NPES and C3I system upgrades), in accordance with the COMSUBFOR approved test plans and procedures detailed in paragraph

4.2. The contractor shall maintain accountability for all test data, including data logging, backup, storage, packaging and mailing for each test event identified by NUWC. The Contractor shall adhere to ACCM handling instructions in accordance with Applicable Document 3.19. The test data shall be archived and distributed in accordance with Applicable Document 3.23.

The contractor shall develop and deliver a test report after each test event identified by NUWC.

Certain test reports will contain Top Secret data and information and will be required to be submitted via TSNET. COMSEC access/hardware/control required to support SPIRNET connectivity to execute all SOW tasking. Currently NAVSEA Washington, DC is providing this capability and this contract will leverage that permission. Test Inspection Reports shall be prepared in accordance with CDRL A008 DI-NDTI-80809B and meeting reports shall be prepared in accordance with CDRL A009- DI-MGMT-80368A.

4.6 Maintenance and Storage

The contractor shall maintain DARTS including updating systems deployed by the NUWC Test Program. The contractor will provide for off-hull storage of the DARTS system in accordance with Applicable Document 3.10 when it is not in operational use. Additionally, the contractor shall set up a secure mobile office at US Submarine ports of call to provide a proper facility to service the DARTS system and perform hardware/software and firmware upgrades due to unexpected NPES system changes.

4.7 Deliverables

At the completion of the contract the Contractor shall provide DARTS hardware and computer software as defined in FAR 52.227-20 (computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations statements), to the Government. At the completion of the contract the contractor shall provide detailed DARTS software definition documentation as defined in FAR 52.227-20 (owner’s manuals, user’s manuals, installation instructions, operating instructions, and other similar items, that explain the capabilities of the computer software or provide instructions for using the software), to the Government in accordance with CDRL A011-DI-IPSC-81443A

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). CDRL A00A – DI-MGMT-81991

6.0 Government Furnished Information and Government Furnished Equipment

The following Government Furnished Information (GFI) will be made available under this contract. Specific GFI as it applies to the applicable platforms and systems will be identified at the task order level.

a. Test schedules

b. All hardware/software purchased on N66604-15-D-0130 contract will be provided as GFE.

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 SECTION 508 Requirements

The Government has determined that this procurement is an exception to the Information and Communication Technology (ICT) Accessibility Standards (36 C.F.R. § 1194.3 - Chapter 2 E202 General Exceptions of Section 50 Refresh). Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with the ICT Accessibility Standards (36 C.F.R. § 1194- Chapters/WCAG to Section 508 Refresh).

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

Note: For tasking performed at Government locations other than NUWCDIVNPT, this clause takes precedence over “CONTRACTOR REQUIREMENTS FOR PERFORMANCE ON A GOVERNMENT SITE” in Section H.

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 A00B 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-H009 ACCESS TO DATA OR COMPUTER SOFTWARE WITH RESTRICTIVE MARKINGS (NAVSEA)

(JAN 2019)

(a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party that contains restrictive markings. If access to such data or software is required or to be provided, the Contractor shall enter into a written agreement with such party prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the restrictively marked data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains properly restrictively marked. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

(b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data or software as to the restrictions under which access is granted; (2) not disclose the data or software to another party or other Contractor personnel except as authorized by the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with this requirement; (4) not disclose the data or software to any other party, including, but not limited to, joint venturer, affiliate, successor, or assign of the Contractor; and (5) reproduce the restrictive stamp, marking, or legend on each use of the data or software whether in whole or in part.

(c) These restrictions on use and disclosure of the data and software also apply to information received from the Government through any means to which the Contractor has access in the performance of this contract that contains restrictive markings.

(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt to gain access to any information with restrictive markings.