SPQ-9B_DA_RFP_N00024-18-R-5308.docx

N0002418R5308

Section B - Supplies or Services and Prices

CLIN Number 1901

Design Agent Services for FY19

CPFF

Level of Effort (LOE) Technical Engineering Services (see NAVSEA clause LEVEL OF EFFORT - ALTERNATE I (MAY 2010))

See Note C

FOB: Destination

PURCHASE REQUEST NUMBER: N0002418NR420000

PSC CD: 5840

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

CLIN Number 1902

Travel

COST

Travel in support of CLIN 1901

See Note D and E

FOB: Destination

ESTIMATED COST

CLIN Number 1903

Incidental Material

Incidental Material in Support of CLIN 1901

See Note D FOB: Destination

ESTIMATED COST

CLIN Number 2001

CPFF

Level of Effort (LOE) Technical Engineering Services (see NAVSEA clause LEVEL OF EFFORT - ALTERNATE I (MAY 2010))

See Notes B and C

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

CLIN Number 2002

COST

Travel in support of CLIN 2001

See Notes B, D, and E

FOB: Destination

ESTIMATED COST

CLIN Number 2003

COST

Incidental Material in Support of CLIN 2001

See Notes B and D

FOB: Destination

ESTIMATED COST

CLIN Number 2101

CPFF

Level of Effort (LOE) Technical Engineering Services (see NAVSEA clause LEVEL OF EFFORT - ALTERNATE I (MAY 2010))

See Notes B and C

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

CLIN Number 2102

COST

Travel in support of CLIN 2101

See Notes B, D, and E

FOB: Destination

ESTIMATED COST

CLIN Number 2103

COST

Incidental Material in Support of CLIN 2101

See Notes B and D

FOB: Destination

ESTIMATED COST

CLIN Number 2201

CPFF

Level of Effort (LOE) Technical Engineering Services (see NAVSEA clause LEVEL OF EFFORT - ALTERNATE I (MAY 2010))

See Notes B and C FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

CLIN Number 2202

COST

Travel in support of CLIN 2201

See Notes B, D, and E

FOB: Destination

ESTIMATED COST

CLIN Number 2203

COST

Incidental Material in Support of CLIN 2201

See Notes B and D

FOB: Destination

ESTIMATED COST

CLIN Number 2301

CPFF

Level of Effort (LOE) Technical Engineering Services (see NAVSEA clause LEVEL OF EFFORT - ALTERNATE I (MAY 2010))

See Notes B and C

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

CLIN Number 2302

COST

Travel in support of CLIN 2301

See Notes B, D, and E

FOB: Destination

ESTIMATED COST

CLIN Number 2303

COST

Incidental Material in Support of CLIN 2301

See Notes B and D

FOB: Destination

ESTIMATED COST

CLIN Number 9900

Each

AN/SPQ-9B Data Items

DATA for CLIN(s) 1901 - 1903, and (if options are exercised) CLIN(s) 2001 - 2003, 2101 - 2103, 2201 - 2203, and 2301 – 2303

See Note A

FOB: Destination

ESTIMATED COST

CLAUSES INCORPORATED BY FULL TEXT

NOTE A - Offeror shall complete the "Price Group" and "Estimated Total Price" blocks of each data item on the Contract Data Requirements List(s), attached hereto.

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

NOTE C

The table below shall apply for Cost-Plus-Fixed-Fee (CPFF) line items (Offeror to complete):

FIXED FEE TABLE

(Hourly Rate) Fixed Fee Rate (Hourly Rate)

FIXED FEE

(Hrs.* Fixed Fee Rate) ESTIMATED COST (Hrs.* Estimated Cost Rate)

NOTE D

Cost only line item to which fee shall not apply. The Contractor may invoice for allowable direct costs up to the total estimated cost for each CLIN. Indirect cost(s) or burdens are allowed for these CLINs only to the extent specified in the tables below (Note to Offerors: Include additional columns as necessary).

Travel CLINs

Indirect Cost #2:

Estimate Cost (Burdened)

Incidental Material CLINs

Indirect Cost #2:

Estimate Cost (Burdened)

Note E LIMITATION ON THE ALLOWABILITY OF COSTS ASSOCIATED WITH AIRFARE IN EXCESS OF THE LOWEST PRICED AIRFARE UNDER COST TYPE CLINS

Airfare costs in excess of the lowest priced airfare available to the contractor during normal business hours are unallowable under this contract unless approved, in writing, by the Procuring Contracting Officer (PCO), prior to commencing travel. Where true program urgency exists, and PCO approval cannot be obtained prior to commencing travel, PCO approval after commencing travel, but prior to submission of an invoice, will be acceptable. For the purpose of this clause, the lowest priced airfare amount included on Contractor travel itineraries meets the FAR requirement for Lowest Priced Airfare, subject to ongoing validation by DCAA.

In order for any airfare costs in excess of the lowest priced airfare to be considered allowable under this contract, said airfare shall: 1) meet one of the exceptions noted under FAR 31.205-46(b); and 2) be documented and justified, including written PCO approval for use of airfare in excess of lowest price.

HQ B-2-0007 LIMITATION OF COST/LIMITATION OF FUNDS (NAVSEA) (SEP 1990)

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.

HQ B-2-0015 PAYMENT OF FEES(S) (LEVEL OF EFFORT – ALTERNATE I) (NAVSEA) (MAY 2010)

(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 for level of effort type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with 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, and shall be paid at the hourly rate(s) specified above per man-hour performed and invoiced. 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.

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contact, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term “residual dollar amount” shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ B-2-0016 PROVISIONING TECHNICAL DOCUMENTATION – WITHHOLDING OF PAYMENT (NAVSEA) (SEP 1990)

(a) For the purpose of paragraph (c) of the "PROGRESS PAYMENTS" clause of this contract, if included, the requirement that the Contractor develop and deliver Provisioning Technical Documentation (PTD) is considered to be a "material requirement of this contract," and Contractor failure to make adequate progress in the development of PTD, or to deliver acceptable PTD on a timely basis, may result in reduction or suspension of Progress Payments as provided in said paragraph.

(b) The PTD is considered to be a part of the "Technical Data" specified to be delivered under this contract for the purposes of the "TECHNICAL DATA--WITHHOLDING OF PAYMENT" (DFARS 252.227-7030) clause. The terms and conditions of the clause entitled "LIMITATION ON WITHHOLDING OF PAYMENTS (FAR 52.232-9), if included in this contract, shall not apply to withholding of payment for failure to make timely delivery of the PTD or delivery of deficient PTD.

HQ B-2-0020 TRAVEL COSTS – ALTERNATE I (NAVSEA) (APR 2015)

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

(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, 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.

HQ B-2-0021 CONTRACT SUMMARY FOR PAYMENT OFFICE (COST TYPE) (FEB 1997)

This entire contract is cost type.

Section C - Descriptions and Specifications

STATEMENT OF WORK (SOW)

FOR AN/SPQ-9B RADAR DESIGN AGENT ENGINEERING SERVICES

1.0 SCOPE

The purpose of this effort is to provide Design Agent Engineering Services in support of AN/SPQ-9B Radar production and fielding efforts.

This SOW supports Engineering Services for the US Navy. Specific requirements will be detailed in Technical Instructions (TIs).

2.0 APPLICABLE DOCUMENTS

The contractor shall use the following documents as appropriate in support of the requirements of this contract. Unless otherwise specified, the most current version shall apply.

3.0 REQUIREMENTS

The contractor shall provide system engineering support, software development and modification, hardware design and modification, installation support, safety support, test support, logistics product updates and configuration management support for the AN/SPQ-9B Radar In Accordance With (IAW) the following sections.

3.1 System Engineering Support

The contractor shall assign a qualified Program Manager (PM) who shall have complete responsibility for the planning, execution, control and reporting of all aspects of the program, and for directing in-house and subcontracted efforts. The Contractor shall support AN/SPQ-9B Integrated Product Team (IPT) meetings which may include third party contractors. IPT meeting locations may include, but are not limited to: Washington Navy Yard (Washington, District of Columbia), Naval Surface Warfare Center (NSWC) Crane (Crane, Indiana), NSWC Port Hueneme (Oxnard, CA), Naval Research Laboratory (Washington, District of Columbia) and SCSC Wallops Island (Wallops Island, Virginia).

The contractor shall maintain and deliver a Contract Work Breakdown Structure (CWBS) IAW Contract Data Requirements List (CDRL) A001 Contract Work Breakdown Structure.

The contractor shall measure AN/SPQ-9B Radar system performance against the performance baseline to identify 1) capability requirements, 2) capability gaps, and 3) materiel and non-materiel solutions, and demonstrate initial capability.

The contractor shall provide strategic guidance and support planning through Analysis of Alternatives (AOAs), Business Case Analyses (BCAs), and shall provide Rough Order Magnitude (ROM) cost estimates for planned solutions. The contractor shall perform risk analysis and provide options for mitigation IAW CDRL A002 Risk Management Status Report.

3.1.1 Design Effectiveness

The contractor shall develop, capture, document, and manage functional, allocated, and physical baselines. The contractor shall (a) identify where each system capability originates and how it is satisfied through design requirements, (b) document the system requirements to the functional level of detail required to develop the detailed design and sustain product support, and (c) for each operational capability, provide a list of processes and data sets needed to complete the design and physically support the capability IAW CDRL A003 Revisions to Existing Government Documents.

3.1.2 Mission Effectiveness

The contractor shall establish system performance metrics to assess and integrate process efficiency and design effectiveness. The metrics and the assessment of the system performance against those metrics shall be provided IAW CDRL A004 Technical Report – Study/Services.

3.1.3 Maintenance Engineering

The contractor shall support maintenance engineering to achieve inherent system performance, to include 1) reliability, 2) Built-In-Test (BIT) effectiveness, and 3) training effectiveness, using analytical methods and tools. Results shall be incorporated into existing Government documents. The contractor shall provide all revisions to Government documents IAW CDRL A003 Revisions to Existing Government Documents.

3.2 Software Development and Modification

The contractor shall provide software and firmware development and modification services for all variants of the AN/SPQ-9B Radar system. Software and firmware under this contract shall be developed using contractor derived processes and procedures that are at least Capability Maturity Model Integration (CMMI) Level 3 or higher.

3.2.1 Information Assurance Support

The contractor shall provide Risk Management Framework (RMF), Security Technical Information Guides, and Information Assurance Vulnerability Alert Management (IAVM) support. RMF support shall include annual review, testing and/or documentation required to achieve or maintain AN/SPQ-9B Radar system certification. RMF support shall include RMF Authority to Operate (ATO) documentation and testing. IAVM support shall primarily consist of timely analysis and reporting of any system related Information Assurance (IA) Vulnerability Alerts. Results and reports shall be provided IAW CDRL A004 Technical Report - Study/Services.

3.2.2 Problem Investigation/Analysis and Resolution

The contractor shall provide on-site and distance data collection, investigation and engineering analysis of reported software or firmware discrepancies and errors. Analysis of Trouble Reports (TRs) and participation in TR adjudication meetings shall be required. The contractor shall investigate potential upgrades and enhancements to software/firmware and shall also provide revisions to existing Government documentation. The contractor shall provide all revisions to Government documents IAW CDRL A003 Revisions to Existing Government Documents. The effort described in this paragraph shall include the engineering analyses required to design, implement, integrate and test proposed hardware, software and firmware developed and/or modified to correct system TRs, and for upgrades to the system. The contractor shall provide a resolution of specific problems as identified in a TR analysis or investigation.

3.2.3 Software Engineering

The contractor shall develop or review Specifications, Engineering Change Proposals (ECPs) and Notices Of Revision (NORs) for existing and new software or firmware development for AN/SPQ-9B Radar systems. Documents shall be prepared for Government review and no changes shall be implemented without Government approval. Contractor developed Specifications shall be submitted IAW CDRL A004 Technical Report - Study/Services. Contractor developed ECPs shall be submitted IAW CDRL A005 Engineering Change Proposal (ECP) Class I ECP, and contractor developed NORs shall be submitted IAW CDRL A006 Notice of Revision (NOR).

3.2.4 Software/Firmware Modification

Upon Government approval of an ECP, the contractor shall update software engineering baselines to include, but not limited to, the following: System/Subsystem Specification (SSS), System Subsystem Design Document (SSDD), Software Design Documents (SDD), Software Requirements Specifications (SRSs), Algorithm Description Documents (ADDs), and Software Version Description (SVD). The contractor shall provide all revisions to Government documents IAW CDRL A003 Revisions to Existing Government Documents.

The contractor shall develop and test software and firmware, and associated hardware modifications, to implement the requirements set forth in the ECP. At minimum this shall include the development of software and firmware code and the building of software and firmware loads, which can be independently regression tested at a Government or contractor facility. The contractor shall deliver the software and firmware code IAW CDRL A007 AN/SPQ-9B Radar Software Source Code. The contractor shall be required to travel to test facilities to support testing of software/firmware modifications.

The Contractor shall generate and submit Software Trouble Reports (STRs) IAW CDRL A004 Technical Report - Study/Services

The contractor shall provide engineering support of Government certifications, studies and design efforts. The contractor shall provide engineering support for AN/SPQ-9B Radar equipment manufacturers, and any integration, engineering design and interface support.

3.3 Hardware Design and Modification

3.3.1 Hardware Engineering and Modification

The contractor shall develop or review Specifications, Drawings, ECPs and NORs for existing and new hardware designs for the AN/SPQ-9B. Contractor developed Specifications shall be submitted IAW CDRL A004 Technical Report - Study/Services. Contractor developed ECPs shall be submitted IAW CDRL A005 Engineering Change Proposal (ECP) Class I ECP, and contractor developed NORs shall be submitted IAW CDRL A006 Notice of Revision (NOR). Documents shall be prepared and submitted for Government review and approval. The Contractor shall not implement changes to the product drawings/models or associated lists without Government approval.

Upon Government approval of the ECP, the ECP will be provided to the contractor as GFI to be incorporated in the Technical Data Package (TDP). The Contractor shall update hardware drawings, schematics, parts lists, mechanical drawings, 3D models, Vendor Item Descriptions (VIDs), Prime Item Development Specifications (PIDS), and component specifications IAW CDRL A008 Product Drawings/Models and Associated Lists.

Any hardware changes shall be traced to and identified as revisions to the SSS, SSDD, and Interactive Electronic Technical Manual (IETM). The Contractor shall provide all revisions to Government documents IAW CDRL A003 Revisions to Existing Government Documents.

The contractor shall identify impacts of hardware changes to Installation Control Drawings (ICDs), system and subsystem test requirements, depot Test Requirement Specifications (TRSs), System Operational Verification Tests (SOVT), and Built-In-Test (BIT) IAW CDRL A003 Revisions to Existing Government Documents.

The contractor shall provide engineering analysis of manufacturing defects and reliability issues, to include data collection, root cause analysis, process improvements and hardware designs for correction IAW CDRL A009 Failure Analysis and Corrective Action Report (FACAR).

The contractor shall provide engineering analysis of maintenance issues, to include data collection, trending, and updates to corrective and preventive maintenance tasks IAW CDRL A004 Technical Report - Study/Services.

The contractor shall be required to provide upgrade/back-fit modifications for the AN/SPQ-9B Radar system or support equipment IAW approved configuration changes. The contractor shall prototype and test hardware modifications in order to verify requirements set forth in ECPs.

3.3.2 DMSMS Support

The contractor shall provide engineering analysis to correct problems and identify solutions for Diminishing Manufacturing Sources and Material Shortages (DMSMS) – Obsolescence investigations IAW CDRL A004 Technical Report - Study/Services.

3.3.3 Material Troubleshooting

The contractor shall perform system-level, subsystem, and component troubleshooting of AN/SPQ-9B Radar equipment to perform failure analysis, determine root cause, and recommended course of action IAW CDRL A004 Technical Report - Study/Services.

3.4 Installation Support

The contractor shall be required to provide Subject Matter Expertise (SME) assistance resolving problems that arise during AN/SPQ-9B Radar installations and shipboard repairs to minimize downtime and improve operational availability. The contractor shall submit a final report IAW CDRL A010 Test/Inspection Report, documenting the testing, data collected, results and recommendations associated with individual support tasking.

3.5 Safety Support

The contractor shall be required to provide assistance in addressing safety related issues that may result from Weapons System Explosives Safety Review Board (WSESRB), Software Systems Safety Technical Review Panel (SSSTRP), Software Support Working Group (SSWG) or Combat System Integration Testing (CSIT) inquiries, or from other in-service TRs. The contractor shall support the AN/SPQ9B Radar Principal for Safety efforts by attending meetings, conducting analysis and/or submitting reports IAW CDRL A010 Test/Inspection Report, documenting the testing, data obtained, results and recommendations associated with individual support tasking.

3.6 Test Support

The contractor shall develop test plans and procedures for test events IAW CDRL A011 Test Plans/Test Procedures. The contractor shall be responsible for coordinating test events with the Government to include identifying hardware and software configuration requirements, locating and scheduling test assets and updates to system configurations to support test events, and identifying and providing simulators and stimulators for test events as defined in the TI.

The contractor shall provide on-site support for system hardware, software, and/or data analysis as a result of systems integration test events as defined in the TI. The contractor shall provide personnel, facilities, equipment, and fixtures to manufacture, assemble and test all Configuration Items required test hardware and software changes to the AN/SPQ-9B Radar system configurations.

3.6.1 On-Site Support

The contractor shall provide support to the Government for testing of modifications, upgrades, and enhancements to the AN/SPQ-9B in accordance with this SOW. This testing shall be accomplished at shore sites and at-sea. This testing shall include, but not be limited to, Independent Verification and Validation (IV&V) and system certification testing as well as miscellaneous system troubleshooting. The contractor shall develop a Test Report IAW CDRL A010 Test/Inspection Report.

3.6.2 Data Analysis

The contractor shall provide engineering analysis of data collected during testing. This data shall include, but not be limited to, external data measured to assess system performance as it relates to Operational Effectiveness and sustainment, extracted system data, test logs, Built-in-Measurement (BIM) data, and test team interviews. The contractor shall develop a Technical Report IAW CDRL A004 Technical Report – Study/Services, detailing the sequence of events as determined by the data analysis, any anomalies noted in the analysis, and a determination of the functional accuracy of the system under test. Any discrepancies found in the Test Procedures shall also be noted.

3.6.3 Test Reporting

The contractor shall submit a Final Test Inspection / Report IAW CDRL A010 Test/Inspection Report, documenting the results, data collected during the test event and recommendations to close out.

3.7 Logistics Product Data (LPD) Updates

The contractor shall provide documented updates to all Logistics Product Data (LPD) fields affected for each hardware and software change IAW CDRL A003 Revisions to Existing Government Documents.

The contractor shall provide updates to parts, reliability, cost, maintenance tasks, reliability block diagrams, Failure Modes, Criticality and Effects Analysis (FMECA), and Fault Tree Analysis (FTA) in support of Interactive Electronic Technical Manuals (IETMs), and Preventive Maintenance System (PMS). The contractor shall ensure all data will be IAW Government-approved Data Type Definition (DTD).

3.8 Configuration Management Support

The contractor and its subcontractors shall have an established CM program with controls in place throughout the contract life guided by ISO 10007:2003, “Quality Management Systems --Guidelines for Configuration Management”; MIL-HDBK-61A; and EIA-STD-649B. The contractor shall develop Engineering Change Proposals (ECPs), drawings, Request for Waivers/Request for Deviation (RFW/RFD), Notice of Revision (NOR), and Specification Change Notices (SCN) IAW the Government’s CMP. The contractor shall incorporate Government created ECPs IAW the Government’s CMP. ECPs, RFW/RFD, and SCNs will be submitted by the contractor for Government review and approval prior to implementation of change IAW CDRL A005 Engineering Change Proposal (ECP) Class I ECP.

3.9 Quarterly Program Reviews (QPRs)

The contractor shall host Quarterly Program Reviews (QPRs) and meetings, that provide system performance analysis, TIs, risks and mitigation techniques, funding status, and action item status/updates that delineate the detailed status and progress. Meeting locations may include but are not limited to, the Washington Navy Yard; Naval Surface Warfare Center (NSWC) Crane; NSWC Dahlgren; Naval Research Laboratory (NRL); Surface Combat Systems Center (SCSC) Wallops Island. The contractor shall prepare an agenda report IAW CDRL A012 Conference Agenda. The contractor shall record minutes of such meetings IAW CDRL A013 Report, Record of Meeting/Minutes.

3.10 Contractor’s Monthly Progress and Status Reporting

The contractor shall provide a Monthly progress/status reports IAW CDRL A014 Contractor’s Progress, Status and Management Report. The progress/status report shall provide detailed information status of all active TI’s awarded. The reports shall include all accomplishments and issues involving development efforts and maintenance support as well as schedule status (i.e., completion dates, dates of deliverables, and future activity schedule). The report shall track the results of the analysis and the date the analysis was provided to the Government. The report shall include a detailed cost/financial report to include all cost data.

4.0 GOVERNMENT FURNISHED ITEMS

4.1 Government Furnished Information (GFI)

The Government shall provide GFI, IAW GFI Attachment J-2.

In the event a commercial software license is not available under the DoD Enterprise Software Initiative (ESI) IAW DFARS 208.7402(1), then the Government may require the contractor to procure the necessary software license..).

4.2 Government Furnished Property (GFP)

The Government shall provide GFP, IAW GFP Attachment J-3. Additionally the contractor may use the AN/SPQ-9B Radar system and/or associated equipment located at any of the following facilities: NSWC PHD, NSWC Crane, Self-Defense Test Site (SDTS) – Oxnard, CA and/or SCSC Wallops Island, on a rent-free, non-interference basis for the performance of this contract. The Contractor is responsible for scheduling the use of the AN/SPQ-9B Radar system and shall contact the facility at least one month in advance. The Government shall not be responsible for conflicts, delays, or disruptions to any work performed by the Contractor due to use of the AN/SPQ-9B Radar system.

5.0 TRAVEL REQUIREMENTS

Travel CLIN 1902 (and option CLINs 2002, 2102, 2202, and 2302 if exercised) in support of Design Agent Engineering Services CLIN 1901 (and option CLINs 2001, 2101, 2201 and 2301 if exercised). The contractor shall be reimbursed for actual travel costs incurred in the performance of CLIN 1901 (and option CLINs 2001, 2101, 2201, and 2301 if exercised) IAW the Section B clause HQ B-2-0020 entitled “TRAVEL COSTS – ALTERNATE I (NAVSEA) (APR 2015).”

The contractor shall request Government approval via email to the Contracting Officer’s Representative (COR) and Procurement Contracting Officer (PCO) prior to making any travel reservations. The contractor’s request shall include the following: 1) reason for travel; 2) approximate number of travelers; 3) approximate number of travel days; 4) location of travel; 5) applicable TI number and 6) validataion of sufficient funding available on the TI. The contractor shall not commence travel until approved by the COR or PCO.

6.0 SECURITY

To perform CLIN 1901, 1902 and 1903 (and option CLINs 2001, 2002, 2003, 2101, 2102, 2103, 2201, 2202 2203, 2301, 2302, and 2303 if exercised) the contractor shall require access to, generate, handle and safeguard classified data. The required means and methods for access and handling of classified data will include the following:

Contract performance shall require generation, handling, and safeguarding of classified data. The contractor is required to maintain a SECRET facility security clearance. The contractor shall have facilities appropriate for classified document storage and control as identified in Attachment J-1 – Department of Defense Security Classification Specification (DD Form 254) and Security Classification Guides. The contractor is required to maintain a level of safeguarding for classified information/material at the SECRET level. The contractor shall have access to Secure Terminal Equipment (STE) and associated encryption device(s) Communication Security (COMSEC) at the contractor facility. Contractor requires access to COMSEC and a COMSEC account to accommodate the use of secure communications. The contractor will be required to have access to CUI with developers and integrators. The contractor will assist in modernizing systems that are classified. Techniques to modernize this equipment, testing of this equipment and overall system performance could be classified and the subject to email and written reports. In this capacity, the contractor will generate and be in receipt of classified material. The contractor shall have personnel cleared for Secret information required to maintain knowledge of the current and Non- Secure Compartmented Information (SCI) intelligence information (e.g. threat data). Access up to NATO SECRET is required for contract performance. Information/data generated, handled or utilized in performance of this contract shall not be disclosed to any third party (e.g. foreign Governments, other corporate entities, etc.) without prior written approval from the COR.

The contractor shall have key personnel cleared for Secret information required to maintain knowledge of the current and non-compartmented intelligence information (i.e., threat data). The threat data is provided using classified briefings and white papers from the Office of Naval Intelligence (ONI) and Navy Research Laboratory (NRL).

7.0 INCIDENTAL MATERIAL REQUIREMENTS

Incidental Material CLIN 1903 (and option CLINs 2003, 2103, 2203, and 2303 if exercised). The Contractor shall include all material incidental to a particular TI, such as associated consumable parts. The sum of all purchases shall not exceed the amounts set forth under Section B and shall be authorized pursuant to NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 2015).

8.0 QUALITY ASSURANCE

The contractor shall follow an internal Quality Assurance System (QAS), which meets the requirements of ISO 9001/2015. The contractor’s QAS shall adequately address all deliverables and areas of support covered by the contract. The contractor’s QAS documentation shall be made available upon request for Government inspection.

9.0 POST AWARD CONFERENCE

A post award conference shall take place no later than 30 days after award of the contract at the contractor’s facility. The purpose of this conference is to acquaint the contractor and Government teams, to achieve a clear and mutual understanding of all contract requirements, and identify and resolve potential problems. The contractor shall deliver an Agenda Report IAW CDRL A012 Conference Agenda one (1) week before the date of the post award conference. The contractor shall deliver Report, Record of Meeting/Minutes IAW CDRL A013 Report, Record of Meeting/Minutes one (1) week after completion of the post award conference.

HQ C-1-0007 PROVISIONING TECHNICAL DOCUMENTATION (NAVSEA) (FEB 1994)

The Provisioning Technical Documentation (PTD) shall be in accordance with the Provisioning Requirements Statement (PRS), including NAVSEA Addendum for PTD Requirements dated January 1993, the Provisioning Performance Schedule and the Contract Data Requirements List, DD Form 1423, Exhibit , attached hereto.

HQ C-2-0002 ACCESS TO PROPRIETARY DATA OR COMPUTER SOFTWARE (NAVSEA) (JUN 1994)

(a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party who asserts that such data or software is proprietary. 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 proprietary 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 proprietary. 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 the spirit and intent of 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) The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.

(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. 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.

HQ C-2-0011 COMPUTER SOFTWARE AND/OR COMPUTER DATABASE(S) DELIVERED TO AND/OR RECEIVED FROM THE GOVERNMENT (NAVSEA) (APR 2004)

(a) The Contractor agrees to test for viruses all computer software and/or computer databases, as defined in the clause entitled "RIGHTS IN NONCOMMERCIAL COMPUTER SOFTWARE AND NONCOMMERCIAL COMPUTER SOFTWARE DOCUMENTATION" (DFARS 252.227-7014), before delivery of that computer software or computer database in whatever media and on whatever system the software is delivered. The Contractor warrants that any such computer software and/or computer database will be free of viruses when delivered.

(b) The Contractor agrees to test any computer software and/or computer database(s) received from the Government for viruses prior to use under this contract.

(c) Unless otherwise agreed in writing, any license agreement governing the use of any computer software to be delivered as a result of this contract must be paid-up and perpetual, or so nearly perpetual as to allow the use of the computer software or computer data base with the equipment for which it is obtained, or any replacement equipment, for so long as such equipment is used. Otherwise the computer software or computer database does not meet the minimum functional requirements of this contract. In the event that there is any routine to disable the computer software or computer database after the software is developed for or delivered to the Government, that routine shall not disable the computer software or computer database until at least twenty-five calendar years after the delivery date of the affected computer software or computer database to the Government.

(d) No copy protection devices or systems shall be used in any computer software or computer database delivered under this contract to restrict or limit the Government from making copies. This does not prohibit license agreements from specifying the maximum amount of copies that can be made.

(e) Delivery by the Contractor to the Government of certain technical data and other data is now frequently required in digital form rather than as hard copy. Such delivery may cause confusion between data rights and computer software rights. It is agreed that, to the extent that any such data is computer software by virtue of its delivery in digital form, the Government will be licensed to use that digital-form with exactly the same rights and limitations as if the data had been delivered as hard copy.

(f) Any limited rights legends or other allowed legends placed by a Contractor on technical data or other data delivered in digital form shall be digitally included on the same media as the digital-form data and must be associated with the corresponding digital-form technical data to which the legends apply to the extent possible. Such legends shall also be placed in human readable form on a visible surface of the media carrying the digital-form data as delivered, to the extent possible.

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

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

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

The Contractor shall prepare a Configuration Management Plan (CDRL A015) in accordance with the requirements of the contract for Government approval. (2) Whenever a situation arises wherein the Contractor cannot comply with a baseline document, or whenever intent of such documentation is significantly changed by detail level documentation, the Contractor shall submit change documents to modify baseline documents to resolve the conflict or to allow noncompliance.

(c) Engineering Change Proposals (ECPs), requests for deviations, requests for waivers, and notices of revision shall be prepared and submitted in accordance with the provisions of ANSI/EIA-649B, IWS 2.0 Configuration Management Plan (CMP) 001, dated 15 April 2008, the approved configuration management plan (CDRL A015), and the requirements of the contract. DI-SESS-80639D approved 07 April 2015 and MILHDBK-61A of 7 Feb 2001 apply. An ECP should be submitted whenever the detail level physical configuration, material quality, operational or functional performance of equipment or installed systems will not be in compliance with baseline design related documents (Specifications, Contract Drawings, etc.), and a change to the baseline document is considered an appropriate means of resolving a design related issue. Documentation shall be developed in sufficient detail to enable Government review and evaluation of the merits of the proposed change, including cost and scheduling impact, ship class impact, and consequences if disapproved. All existing drawings and technical manuals impacted by the change shall be listed along with a brief narrative explanation of needed changes to incorporate the ECP if approved. Weight and moment data incidental to the change shall be provided. The Contractor shall also prepare applicable baseline document insert sheets, with specific word changes or proposed re write, to facilitate baseline documentation changes.

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

(e) Deviations and Waivers In the event that a baseline design related document requirement cannot be met, and a change to the baseline document is considered inappropriate, the Contractor shall submit a Request for Deviation (RFD) or Request for Waiver (RFW), as applicable. DI-SESS-80640D approved 07 April 2015 and MIL-HDBK- 61A of 7 Feb 2001 apply. The explanation of "need for deviation" should provide detailed justification and consequences of approval, to include technical details explaining the degree of noncompliance or effect on ship equipment or system operation constraints. In a similar manner, a waiver shall document an "as built" configuration that departs from baseline documentation and should include any proposed corrections or modifications to better meet the intent of the baseline document.

(f) Any cost reduction proposal submitted pursuant to the clause entitled "VALUE ENGINEERING" (FAR 52.248 1) shall be submitted as a Code V Engineering Change Proposal (VECP). DI-SESS-80639D approved 07 April 2015 and MIL-HDBK-61A of 7 Feb 2001 apply. Information required by the "VALUE ENGINEERING" clause shall also be submitted as part of the change request.

HQ C-2-0014 CONTRACTOR'S PROPOSAL (NAVSEA) (MAR 2001)

(a) Performance of this contract by the Contractor shall be conducted and performed in accordance with detailed obligations to which the Contractor committed itself in Proposal * dated * in response to NAVSEA Solicitation No. N00024-18-R-5308.

(b) The technical volume(s) of the Contractor's proposal is incorporated by reference and hereby made subject to the provisions of the "ORDER OF PRECEDENCE" (FAR 52.215-8) clause of this contract. Under the "ORDER OF PRECEDENCE" clause, the technical volume of the Contractor's proposal referenced herein is hereby designated as item (f) of the clause, following "the specification" in the order of precedence.

*To be completed at time of award

HQ C-2-0032 INFORMATION AND DATA FURNISHED BY THE GOVERNMENT - ALTERNATE II (NAVSEA) (SEP 2009)

(a) NAVSEA Form 4340/2 or Schedule C, as applicable, Government Furnished Information, attached hereto, incorporates by listing or specific reference, all the data or information which the Government has provided or will provide to the Contractor except for

(1) The specifications set forth in Section C, and

(2) Government specifications, including drawings and other Government technical documentation which are referenced directly or indirectly in the specifications set forth in Section C and which are applicable to this contract as specifications, and which are generally available and provided to Contractors or prospective Contractors upon proper request, such as Federal or Military Specifications, and Standard Drawings, etc.

(b) Except for the specifications referred to in subparagraphs (a)(1) and (2) above, the Government will not be obligated to provide to the Contractor any specification, drawing, technical documentation or other publication which is not listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, notwithstanding anything to the contrary in the specifications, the publications listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, the clause entitled "GOVERNMENT PROPERTY" (FAR 52.245-1) or "GOVERNMENT PROPERTY INSTALLATION OPERATION SERVICES " (FAR 52.245-2), as applicable, or any other term or condition of this contract.

(c)(1) The Contracting Officer may at any time by written order:

(i) delete, supersede, or revise, in whole or in part, data listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable; or

(ii) add items of data or information to NAVSEA Form 4340/2 or Schedule C, as applicable; or

(iii) establish or revise due dates for items of data or information in NAVSEA Form 4340/2 or Schedule C, as applicable.

(2) If any action taken by the Contracting Officer pursuant to subparagraph (c)(1) immediately above causes an increase or decrease in the costs of, or the time required for, performance of any part of the work under this contract, the contractor may be entitled to an equitable adjustment in the contract amount and delivery schedule in accordance with the procedures provided for in the "CHANGES" clause of this contract.

HQ C-2-0037 ORGANIZATIONAL CONFLICT OF INTEREST (NAVSEA) (JUL 2000)

(a) "Organizational Conflict of Interest" means that because of other activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the Government, or the person's objectivity in performing the contract work is or might…