N66604-20-R-0369.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local t ime 26 Feb 2020

X

A X B X C X D

EX

X

G F 64 - 68

69 - 75 X H 76

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

See Section L 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 - 27 28 - 29

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

30 - 32

33 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 34 - 41 X

SPECIAL CONTRACT REQUIREMENTS

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

48 - 62

PART II - CO NTRACT CLAUSES

NAVAL UNDERSEA WARFARE CENTER

SUZANNE VIOLET, CODE 0224,

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841-1708

401-832-6946

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

03 Feb 2020

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6660420R0369

Section SF 30 - BLOCK 14 CONTINUATION PAGE

GENERAL INFORMATION

NUWCDIVNPT Control Number: 200369 NUWCDIVNPT Requisition Number(s): 1300759773

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 541330 – Engineering Services (corresponds with exception for Marine Engineering and Naval Architecture). The small business size standard is $41.5M.

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot XTDAS Engineering Services

CPFF

Services in accordance with the Statement of Work in Section C.

Estimated Number of Hours: 236,870 FOB: Destination

PSC CD: AC34

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 Lot Other Direct Costs (ODCs)

COST

Other Direct Costs associated with labor under CLIN 0001

THE OFFEROR SHALL INCLUDE A MATERIAL/ODC ESTIMATE OF

$80,900 AND A TRAVEL ESTIMATE OF $687,228 (FIGURES DO NOT

INCLUDE BURDENS). THE OFFEROR SHOULD ADD APPLICABLE

BURDENS TO THESE ESTIMATES, ROUNDED TO THE WHOLE DOLLAR.

THE OFFEROR SHALL NOT INCLUDE FEE ON BURDENED ODCS.

ESTIMATED COST

0003 1 Lot Contract Data Requirement Lists (CDRLs)

FFP

Data in accordance with Exhibit “A”, Contract Data Requirements List (CDRLs), DD Form 1423

NOT SEPARATELY PRICED

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.

Applicable CLINs: 0001

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.

Applicable CLINs: 0001

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

PERFORMANCE WORK STATEMENT (PWS)

Extensible Markup Language Test Data Analysis Tool (XTDAS)

1.0 BACKGROUND

NAVSEA System Command Program Management, SEA PMS 394, 397, 401, 404, 415, 425, 435, and 450, have tasked Naval Undersea Warfare Center Division, Newport (NUWCDIVNPT) Code 259 to direct the conduct of system performance, certification, calibration and developmental testing for new construction and acquisition programs and in-service Command, Control, Communications, Computer, Coordination and Intelligence (C5I) System technology refresh and technology insertion efforts. Among the programs included are COLUMBIA Class Program, VIRGINIA (SSN 774) Class Submarine Program and its Non-Propulsion Electronics System (NPES);

weapons systems and associated interfacing systems including sonar, combat control, external communications systems, imaging, electronic warfare systems, navigation; and Submarine Combat System Capability Assessment program (SCS CAP) test programs. Test events include Weapons System Accuracy Trials (WSAT), Submarine Warfare Federated Tactical Systems (SWFTS) certification testing, Weapons Compatibility Testing, Sensor Accuracy Trials, Cybersecurity developmental testing, array calibrations, and acquisition program Development Testing (DT).

To maximize the quality and speed of data processing required in the most cost effective manner, NUWCDIVNPT Code 25 supports the development of automated test tools. In the Department of Defense (DoD) Small Business Innovative Research (SBIR) FY2003 Program Solicitation 03-1, proposals were requested for “Innovative Test Data Analysis Technologies.” System Engineering Associates Corporation (SEA CORP) proposed and was selected for Phase I, Phase II, and Phase III awards under topic number N03-16. Under these awards, SEA CORP developed an automated test-tool technology, the Extensible Markup Language Test Data Analysis Tool (XTDAS). The XTDAS provides an automated method for collecting Combat and Weapon System message data, sonar data and launcher data, and then analyzing and/or displaying the collected data in a format that can be utilized for data verification and reporting purposes. Additionally, XTDAS provides real-time automated data validation capability during actual laboratory, dockside, and at-sea test events. Finally, XTDAS adaptations such as Extensible Markup Language (XML) Data Distribution Service (XDDS) facilitate integration of disparate NPES subsystems, weapon systems, and applications.

Sponsors of this work are NAVSEA Program Management Systems (PMS) 394, 397, 401, 404, 415, 425, 435, and

450. Authorized users of this contract are NUWCDIVNPT Codes 15, 25, and 34. Funding for this tasking includes Operation and Maintenance Navy (OMN,N), Research, Development, Test & Evaluation, Navy (RDT&E,N), Research, Development, Test & Evaluation, Defense Agencies (RDDA), Other Procurement, Navy (OPN), and Shipbuilding and Conversion (SCN).

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) Naval Ordnance Test Unit (Port Canaveral FL) Atlantic Undersea Test and Evaluation Center (AUTEC) Other contractor labs and facilities On-board US ships and ranges

2.0 SCOPE

The contractor shall continue to develop, upgrade, and adapt XTDAS technology to provide a means to collect and analyze Submarine NPES and other combat and weapon system data for Payload Integration and Test and Evaluation (T&E). XTDAS development includes both hardware and software for integration, data collection, and analysis, as well as data reduction tools.

NUWCDIVNPT NPES and other combat/weapons system programs will utilize XTDAS Technology. This includes developing and maintaining various XTDAS hardware and software variants for each Technical Insertion/Advanced Processor Build (TI/APB) cycle as required for each class of US Submarines and associated systems hardware and software. NUWCDIVNPT will use the XTDAS tool to support Developmental and Operational Test planning and execution efforts for all US submarines that utilize the United States Navy’s TI/APB variants.

The contractor shall utilize the XTDAS to provide Subsystem test, evaluation, integration, system engineering, technical, and XTDAS support services (as described in detail in Section 4.0) to NUWCDIVNPT and other Navy activities and organizations; to perform system level and payload/ weapon compatibility testing, cybersecurity developmental testing, software and hardware testing, systems engineering, and 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). The contractor shall adapt the XTDAS technology to support planning and preparation for Columbia Class test program. The contractor shall provide XTDAS installation and removal services, operational support for test events, establish and manage XTDAS test database, maintain configuration management of XTDAS variants, and maintain and store the XTDAS equipment.

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 DoD Issuances

3.1.1 DoD Directive 5000.1 4.1

3.1.2 DoD Instruction 5000.2 “Defense Acquisition Management

Documentation and Reports” 4.1

3.1.3 CJCSI 6510.01F; Information Assurance (IA) and Computer Network Defense (CND)

4.1, 4.1.1, 4.1.4, 4.2.2

3.1.4 DoDI NUMBER 8500.01, March 14, 2014, Cybersecurity 4.1, 4.2.2

3.1.5 DoD 8570.01-M, Information Assurance Workforce Improvement

Program; November 10, 2015 Rev M 4.1, 4.2.2

3.2 Navy Issuances

3.2.1 NAVSEAINST 9093.2A, Submarine Combat System

Certification and Assessment Program 4.2.1

3.2.2 NUWCDIVNPT Administrative Publications 11,255 4.1

3.2.3 Columbia Class Master Development Schedule 4.1, 4.2.3

3.2.4 Columbia Class Capabilities Development Document 4.1, 4.2.3

3.2.5 Virginia Class Master Development Schedule 4.1, 4.2.1, 4.2.2, 4.2.3

3.2.6 Virginia Class Operational Requirements Document 4.1, 4.2.1, 4.2.2, 4.2.3

3.2.7 Virginia Class Test and Evaluation Master Plan 4.1, 4.2.1, 4.2.2, 4.2.3

3.2.8 Joint Fleet Maintenance Manual (JFMM) All Tasks

3.2.9 Virginia Class COATS Test Plan 4.1, 4.2.1, 4.2.2, 4.2.3

3.2.10 Security Policy Training for Individuals Requiring Access to

Briefings/ Documents Containing VIRGINIA Class Stealth Performance Data

4.1, 4.2.1, 4.2.2, 4.2.3, 4.3

3.2.11 Virginia Class Test Schedules 4.1, 4.2.1, 4.2.2, 4.2.3

3.2.12 Virginia Block 3 Data Management Plan 4.2.2, 4.3

3.2.13 Capability Development Document (CDD) for the Columbia

Class Submarine 4.1, 4.2, 4.3

3.2.14 Common Functional Requirements Document (FRD) for VA and

CLB

4.1, 4.2, 4.3

3.2.15 NAVSEAINST S5510.18, Security Policy for Stealth

Performance Data with ACCM, 10 May 2013

4.3

3.2.16 NAVSEAINST 9400.2A, NAVSEA Platform Information

Technology-Control Systems Cybersecurity Governance And Guidance

4.1

3.2.17 SECNAVINST 5239.3C, Department Of The Navy Cybersecurity Policy

4.1

3.3 Industry Standards

3.3.1 IEEE/EIA 12207.1 Guide for Information Technology (GIT) –

SLP Lifecycle Data 4.1

3.3.2 IEEE/EIA 12207.0 GIT – Software Lifecycle Processes (SLP) 4.1

4.0 TECHNICAL REQUIREMENTS

The following tasks shall be accomplished in accordance with Government Specifications and Standards 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 Extensible Markup Language (XML) Test Data Analysis Tool (XTDAS) Adaptation

In accordance with Applicable Documents specified in section 3.0, the contractor shall adapt the XTDAS to meet the requirements of the applicable test program. The contractor shall adapt XTDAS to support all US submarines that utilize the Navy’s Technology Insertion Advance Processing Builds (TI/APB) variants. This XTDAS configuration shall support conduct of Developmental Test and Evaluation (DT&E) and Follow-on Operational Test and Evaluation (FOT&E). The contractor shall establish and maintain an XTDAS support plan for the systems onboard the US Submarines.

For all tasking under 4.1 the contractor shall establish and maintain a software engineering process in accordance with Applicable Documents 3.3.1 and 3.3.2 to achieve XTDAS performance. The software engineering process shall be documented in a Software Development Plan (SDP). The contractor shall tailor the requirements identified in Applicable Documents 3.3.1 and 3.3.2 to the XTDAS program and the tailoring shall be included as part of the SDP.

Using GFI 6.1, 6.2, 6.3, and 6.4, the contractor shall adapt the XTDAS to interface with the ship systems on board submarine platforms for all US submarines that utilize the United States Navy’s TI/APB variants. The XTDAS configuration shall support the conduct of WSAT shipboard events. The contractor shall identify the required hardware and software configuration changes needed to integrate the XTDAS variant to the WSAT test platforms.

The contractor shall obtain, manufacture, incorporate, and install the required hardware and software changes and verify expected versus received data.

In accordance with Applicable Documents 3.2.5, 3.2.7, 3.2.9, and 3.2.11, the contractor shall adapt the XTDAS to facilitate prototype development, integration, and test of disparate NPES subsystems, applications, and weapon systems. The contractor shall develop XTDAS software and hardware and conduct laboratory and shipboard integration and test events in accordance with Applicable Documents 3.1.4, 3.1.5, 3.2.16, and 3.2.17. The contractor shall identify, manufacture, incorporate, and install the required hardware and software changes and verify expected versus received data.

In accordance with Applicable Documents 3.2.12, 3.2.13 and 3.2.14, the contractor shall adapt the XTDAS to facilitate prototype, integration, and test of future payloads with AN/BYG-1 Payload Control System (PCS). The XTDAS configuration shall support the conduct of laboratory and shipboard integration and test events. The contractor shall identify the required hardware and software configuration changes needed to prototype payloads including next generation torpedoes, missiles, and unmanned vehicles. The contractor shall identify, manufacture, incorporate, and install the required hardware and software changes and verify expected versus received data.

Deliverables:

CDRL A001 – DI-MISC-80508B – Technical Report – Study/Services CDRL A002 – DI-MISC-80652 – Technical Information Report CDRL A005 – DI-ILSS-80872 – Training Materials CDRL A006 – DI-DRPR-80651 – Engineering Drawings CDRL A007 – DI-SESS-81002F – Development Design Drawings/Models and Associated Lists CDRL A00B – DI-IPSC-81427B – Software Development Plan

4.2 Test & Evaluation

4.2.1 Test Planning

The Government will provide the contractor with a high level Test Plan, GFI 6.5, for each test event that defines the framework of the required testing.

In accordance with Applicable Documents 3.2.1, 3.2.5, 3.2.6, 3.2.7, 3.2.9, 3.2.10, and 3.2.11, the contractor shall participate in test planning for combat and weapon system testing related to all classes of U.S. submarines. Test planning shall include development of test plans, test procedures, data-collection plans, and test-reporting requirements. Test events and activities covered under this tasking include system performance, certification, calibration and developmental testing for new construction/acquisition programs and in-service Command, Control, Communications, Computer, Coordination and Intelligence (C5I) System technology refresh and technology insertion efforts.

The contractor shall perform the following activities as part of test planning:

a. Verify each platform’s combat and weapon system configuration to identify major hardware and software upgrades and data collection requirements.

b. Review System Employment Manuals (SEMs) and functional documentation for each combat system platform configuration to assess whether test planning accounts for required fleet employment and system functional capabilities.

c. Operate the combat and weapon system to be tested in laboratory and shipboard environments.

d. Develop a test-data plan, customized for each platform and submit to the test event Technical Program Manager (TPM) for approval.

e. Coordinate test schedule for each platform with respective submarine squadron.

f. Configure an XTDAS variant for each platform to verify expected versus received data.

g. Verify data collection requirements for the various test events during dockside availability

h. Develop, recommend, provide, prepare, maintain, ship, stage, and store test facility equipment, instrumentation, consumable material, and other resources required to support test conduct.

The contractor shall provide an XTDAS variant, developed under 4.1, to support the laboratory, dockside, and at-sea test events.

Deliverables:

CDRL A003 – DI-NDTI-80566A – Test Plan CDRL A004 – DI-NDTI-80603A – Test Procedure

4.2.2 Test Conduct

In accordance with Applicable Documents 3.2.5, 3.2.6, 3.2.7, 3.2.9, 3.2.10, and 3.2.11, the contractor shall conduct laboratory, dockside, and at-sea testing in accordance with the test plans developed in Task 4.2.1 above. As part of test conduct and in accordance with test plans developed in Task 4.2.1, the contractor shall collect required data for XTDAS analysis. The contractor shall manage collected test data in accordance with Applicable Document 3.2.12.

As part of test conduct, the contractor shall install XTDAS in laboratories and on the test submarine platforms and remove upon completion of testing. Testing at Submarine builders’ facilities shall be conducted by the contractor to verify the XTDAS is ready for at-sea testing. The contractor shall conduct testing at Command and Control Module Off-Hull Assembly and Test Site (COATS) facilities in support of VIRGINIA test events. The contractor shall conduct and assist as necessary with cybersecurity development testing which includes vulnerability assessments and penetration testing of TI/APB variants. 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.1.5, for an Information Assurance Technical (IAT) workforce member level II (IAT II). The contractor must have a Command appointment letter before beginning work performing the cybersecurity tasking 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 shall meet continuous learning requirements.

Deliverables:

CDRL A001 – DI-MISC-80508B – Technical Report – Study/Services CDRL A002 – DI-MGMT-80368A – Technical Information Report

4.2.3 Test Data Analysis

In accordance with Applicable Documents 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.9, 3.2.10, and 3.2.11 and utilizing XTDAS Technology, the contractor shall process and analyze the data collected during testing conducted under

4.2.2 to assess whether test objectives were met and system acceptance can be made.

The contractor shall finalize the data collection capability approaches and shall define the XTDAS hardware and software requirements needed to support the tasks defined in section 4.1 for US Submarine combat and weapon systems DT&E and IOT&E during laboratory availabilities (period of time when the XTDAS can be connected to actual system hardware).

The contractor shall deliver test reports for each test.

Deliverable:

CDRL A008 – DI-NDTI-80809B – Test Inspection Report

4.3 Reporting/Meeting Support/Data Management

The contractor shall attend Working Group Meetings, Working Integrated Product Team (WIPT) meetings and Commander Operational Test and Evaluation Force (COMOPTEVFOR) Mission Based Testing Design (MBTD) meetings to gather necessary information about the combat and weapon system designs and to assess the readiness of the XTDAS configuration.

Data Management - In accordance with Applicable Document 3.2.10, the contractor shall maintain full accountability for all test data including data logging, recording, backup, storage, packaging and mailing for all data collected during testing. The contractor shall adhere to Alternative or Compensatory Control Measures (ACCM) Classified handling procedures in accordance with Applicable Document 3.2.15.

The Contractor shall deliver a Data Collection Program Plan (DCPP) in accordance with Applicable Documents 3.2.12-3.2.14 that addresses the data collection requirements to support developmental and operational testing.

Deliverables:

CDRL A001 – DI-MISC-80508B – Technical Report – Study/Services CDRL A009 – DI-ADMN-81505 – Report, Record of Meeting/Minutes

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 A00A – 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 Database Design Document for the TI-16/APB15 Digital Data Collection

System – Information Server (DDCS-IS), P013528, Revision -, 1 December

4.1

6.2 Software Requirements Specification (SRS) for the Digital Data Collection System, P000056, Revision B, 21 May 2004

4.1

6.3 Software Requirements Specification (SRS) for the Tactical Control System (TCS) Digital Data Collection System (DDCS) Computer Software Configuration Item Final, 22 June 2009

4.1

6.4 NUWCDIVNPTINST 5500.4b, Naval Undersea Warfare Center Division, Newport Security Manual, Change 2, 31 January 2012

4.1

6.5 Government Platform Test Plan 4.2.1

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, small business subcontracting, 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;

• Utilization of Small Business: The Government will evaluate the contractor’s compliance with the Small Business Subcontracting Plan and any small business subcontracting goals contained in the contract; and

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

8.0 EXCEPTION FROM INFORMATION AND COMMUNICATION TECHNOLOGY ACCESSIBILITY

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).

9.0 CYBERSECURITY

9.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.

9.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.

9.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.

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

9.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.

9.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.

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-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-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)

Applicable CLINs: 0003

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. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

(e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

(f) Compliance with this requirement is a material requirement of this contract.

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

FROM THE…