N00024-18-R-5308-0002 SPQ-9B DA.pdf

N0002418NR420000

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

SPS PR#: N00024-19-MR-42089

ERP PR#: N/A

The purpose of this modification is to update:

(1) Statement of Work Section 3.2;

(2) Section L Proposal Requirements Volume II Tab E; and

(3) Section L Proposal Requirements Volume III Tab G.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 29

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-Nov-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002418R5308

X 9B. DATED (SEE ITEM 11)

15-Jun-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

14-Nov-2018

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002418R5308

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

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.

2.1 Military Standards

MIL-STD-129 Military marking for Shipment and Storage MIL-STD-130 Identification Marking of U.S. Military Property MIL-STD-196 Joint Electronics Type Designation Automated System MIL-STD-881 Work Breakdown Structure for Defense Material Items MIL-STD-882 Standard Practice System Safety MIL-STD-1397 Input/ Output Interfaces, Standard Digital Data, Navy Systems MIL-STD-1399 Interface Standard for Shipboard Systems MIL-STD-2073-1 Military Packaging, Standard Practice for MIL-STD-31000 Technical Data Packages MIL-STD-38784 Standard Practice General Style and Format Requirements for Technical

Manuals

2.2 Military Specifications

EIA-649 Configuration Management Standard

2.3 Military Handbooks

MIL-HDBK-61 Configuration Management Guidance MIL-HDBK-217 Reliability Prediction of Electronic Equipment MIL-HDBK-237 Electromagnetic Environmental Effects and Spectrum Supportability Guidance for the Acquisition Process MIL-HDBK-454 General Guidelines for Electronic Equipment MIL-HDBK-470 Designing and Developing Maintainable Products and Systems MIL-HDBK-781 Reliability Test Methods, Plans, and Environments for Engineering

Development, Qualification, and Production MIL-HDBK-2036 Preparation of Electronic Equipment MIL-HDBK-2164 Environmental Stress Screening Process for Electronic Equipment MIL-HDBK-2155 Failure Reporting, Analysis and Corrective Action Taken

2.4 Other Documents

NAVSOP 6071 Best Practices for Manufacturing Planning IWS 2.0 CMP Configuration Management Plan DoD Guide DoD Guide to Uniquely Identifying Items Version 1.1 ISO 9001 Quality Management Standard TE000-AB-GTP-020 Government Stress Screening of Hardware (for guidance only) Jan 92 DoDI-8510.01 Risk Management Framework (RMF) Instruction DoDI-8500.01 Cyber Security 14 March 2014

2.5 ASME Standards

Y14.38 Abbreviations & Acronyms for use on Drawings and Related Documents Y14.100 Engineering Drawing Practices Y14.24 Types & Applications of Engineering Drawings Y14.35 Revision of Engineering Drawings and Associated Documents Y14.34 Associated Lists

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 equivalaent to 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.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

Tab G

GENERAL

The purpose of this effort is to provide Design Agent Engineering Services in support of AN/SPQ-9B Radar production and fielding efforts. Offerors are encouraged to demonstrate their ability to provide innovative approaches toward achieving and sustaining the requirements of this solicitation while demonstrating their ability to support all requirements of the SOW. Offeror should assume a contract award date of third quarter Government Fiscal Year 2019. Offerors should use the information contained within this Request for Proposal (RFP) including Section L and Section M to formulate their response.

Please note that pursuant to FAR 52.215-1, the Government intends to award a contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions if determined by the Contracting Officer to be necessary (see paragraph (4) of FAR 52.215-1 (f)). Therefore, the Offeror shall submit only one proposal which contains the Offeror’s best terms from a price and technical standpoint. No alternative proposals will be accepted by the Government. The Offeror is required to submit a proposal which is sufficiently detailed and complete to fully demonstrate understanding of, compliance with, and for substantiating the validity of stated claims of all requirements of this RFP. The proposal shall contain only material directly related to this acquisition. The Government may contact any or all or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15.

General statements such as “the Offeror understands,” “the Offeror can or will comply with the requirements,” “standard procedures will be used,” “well-known techniques will be used,” or statements that merely paraphrase the RFP in whole or in part DO NOT constitute compliance with the requirements for proposal content. Offerors should assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror’s proposals. Data previously submitted, or presumed to be known (such as data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless actually included in the proposal. The Government does not assume the duty to search for data to cure problems it finds in proposals. Failure to conform to all requirements of this solicitation may form the basis for rejection of the proposal.

GUIDELINES FOR CONTENT

A legible, neat, orderly and comprehensive proposal is required. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids beyond those sufficient to present a complete and comprehensive proposal are unnecessary. The use of brochures shall be minimized and if used will be included in the page count.

An Offeror’s proposal shall be sufficiently detailed to enable Government evaluation board members to make a thorough evaluation and to arrive at a sound determination as to whether or not the prospective Offeror will be able to perform in accordance with the stated requirements.

The Offeror’s proposal shall be sufficiently specific, detailed and complete as to clearly demonstrate that the Offeror has a comprehensive approach to the total technical requirements, the SOW and solicitation requirements. Proposal content, packaging, and delivery requirements shall be flowed down from the Prime to the major subcontractors, and major subcontractors shall identify the prime contractor associated with their subcontractor proposals on the cover of their submissions. Additionally, the subcontractor shall identify a point of contact, address, and telephone number for each physical location where the work will be performed.

Major subcontractors are defined as any subcontractor performing 10% or more of the total hours under the contract;

however, where otherwise minor subcontractors cumulatively perform more than 20% of the total hours under the contract or cumulatively perform more than $10M of work under the contract, all subcontractors are considered major subcontractors and must propose as such. All subcontractors that do not meet the definition of major subcontractor above are minor subcontractors.

Table: L-3-1. Proposal Page Limitations Volume Title Page Limit Total Copies

I

Introduction (Unclassified)

• Tab A: Cover Letter**

• Tab B: Table of Contents**

• Tab C: Executive Summary

6 Unclassified softcopies 1 Unclassified hardcopies

II

Technical Approach (Unclassified):

• Tab D: System Performance Approach and

Technical Knowledge

• Tab E: Sample Scenario

• Tab F: Personnel o Key Personnel Resumes* o Staffing Plan**

6 Unclassified softcopies 1 Unclassified hardcopies

III

Management Approach (Unclassified)

• Tab G: Engineering Management Plans and

Processes

• Tab H: Program Management Process

6 Unclassified softcopies 1 Unclassified hardcopies

IV

Data Rights (Unclassified)

• Tab I: Data Rights**

6 Unclassified softcopies 1 Unclassified hardcopies

V Past Performance (Unclassified)

6 Unclassified softcopies 1 Unclassified hardcopies

VI Cost/Price (Unclassified)** Unlimited 6 Unclassified softcopies 1 Unclassified hardcopies

VII Exceptions, Deviations & Waivers 10 6 Unclassified softcopies 1 Unclassified hardcopies

*Key Personnel Resumes are not counted against the page limits above, but each is limited to two pages per resume.

** See Page Count Exceptions below.

All information relating to contract cost or pricing data shall be included only in the section of the proposal designated by the Government as the Cost/Price Proposal Volume (Volumes VI ). UNDER NO

CIRCUMSTANCES SHALL CONTRACT COST AND PRICING DATA BE INCLUDED IN VOLUMES I

THROUGH V and VII. In the event that cost and pricing data is included in Volumes I through V and VII, that data will be excluded from the evaluation.

**Page Count Exceptions

Each page of the written volumes, including appendices and annexes, will be counted towards the total page count, with the following exceptions:

Transmittal letters, teaming agreements, letters of intent, subcontract agreements, Small Business Subcontracting Plan.

Cover pages, title pages, tabbed dividers.

Section K, Representations and Certifications Blank pages. Pages the Offeror intentionally left blank for formatting purposes (e.g. back of page before a section break), shall be marked with “this page intentionally left blank” and the annotated pages will not be counted towards page limits.

Tables of contents. No substantive text shall be included in the document Table of Contents.

Lists of figures and tables, glossaries of abbreviations and acronyms, and cross-reference matrices The Staffing Plan (Attachment J-S3) The 7017 List, 7028 List, and Commercial Restrictions List (Volume IV. Tab I) Key Personnel Letter of Intent Contractor Award Information (J-S6)

Binding

Each volume of the proposals shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Each volume shall be contained in a separate, loose-leaf, three-ring binder, which lies flat when open, with tabs for each major Section and Subsection identified in table L-3-1 of this document. Staples, spiral or glued bindings shall not be used. Each binder shall have a front cover containing the volume number, title, copy number, solicitation number and the Offeror's name. The same identifying data shall be placed on the spine of each binder.

Should any Volume be divided into more than a single binder, the cover shall identify the binder number in addition to the Volume number, e.g., “Volume II – Technical Approach, Binder One of Two.” Each volume shall be labeled and numbered sequentially for the required number of copies starting with Copy 1. The original paper copy shall be labeled “Original: Copy 1.” The Offeror shall apply all appropriate markings including those prescribed IAW FAR 52.215-1(e) “Restriction on Disclosure and Use of Data,” and FAR 3.104-4 “Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.”

To aid in the evaluation, all proposals shall follow the same general format. Page limitations on the proposal are described in Table L-3-1. All pages submitted by an Offeror in excess of the limitations contained in these instructions shall not be read or evaluated, and will be removed by the Contracting Officer from the back of the respective volume prior to evaluation. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Index pages and tabs are required and shall be cross referenced to the table of contents. Pages not in the page count shall be numbered with Roman numerals (e.g., iv) and shall not contain additional or inappropriate information, and if such is found, these pages will be removed by the Contracting Officer and will not be read or evaluated.

Page Size and Format

A page is defined as each face of an 8-1/2 x ll-inch sheet containing information. Two pages may be printed on one sheet of paper, with the front and back counted as two pages. Foldout pages may be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. Foldout pages are defined as the face of an 11 x 17-inch sheet containing information. Foldout pages shall fold entirely within the volume. Each printed side of a foldout page will count as two pages, and must be numbered accordingly. All information on a page must be provided within an image area of 7 x 9 inches (9 x 15-1/2 inches for foldout pages), except for classification headings, footings, and page numbers. All material must be contained within the page limit identified for each volume, unless otherwise specified. Partial pages count as a full page for page limitation purposes. All pages within a page-limited volume shall be consecutively numbered, starting at page one, and not exceeding the page limitation. The Contracting Officer will remove any pages submitted by Offerors not in compliance with formatting requirements.

These limitations shall apply to both electronic and hard copy proposals.

The information regarding electronic products presented below should not be construed as Government endorsement for these particular products. Efforts by the Government to clarify and install electronic proposal submissions in accordance with FAR 15.207(c) will not be considered discussions. In the event of inconsistencies between the hardcopy and electronic versions of a proposal, the electronic version shall take precedence. Page limits for electronic versions shall be consistent with printed page requirements stated in table L-3-1.

Electronic proposal submission and supporting information shall be submitted on CD-ROM or DVD discs suitable for reading in a standard PC compatible DVD drive. All files shall be compatible with Microsoft Office 2010. All spreadsheets shall be in Microsoft Excel format such that each mathematical equation utilized for calculations is visible and working. Before submitting spreadsheets, the Offeror shall remove or disable macros, but retain all computational functionality and embedded links and formulas. All text documents shall be in Microsoft Word 2010.

The Offeror shall not embed sound or video files into the electronic files. The Offeror shall screen all discs for computer viruses prior to submittal. The information and format of the proposal shall be identical on electronic copies, discs, and hard copy submissions.

All CD or DVD discs shall be read only and shall not be password protected. The cost proposal disc files shall be submitted with unrestricted access permissions. Unclassified volumes shall be submitted on unclassified discs. The discs shall be labeled with the following information:

Offeror Name Name of Effort Solicitation Number Date of Proposal Submission Proposal Volume Number(s) and Name(s) Classification Level Disc Number (e.g., l of 3) Copy Indicator Number Restrictive marking (FAR 52.215-1(e)) “Source Selection Information” (FAR 3.104-4).

Volumes I, II, III, IV, V and VII may be submitted together on one disc. If submitted on separate discs, the submission shall not exceed more than one disc per volume. Volume VI, labeled “Cost/Price,” must be submitted on a separate disc from all other proposal information.

Subcontractor media submissions, if provided, shall be labeled with the same information listed above, and shall also include the name of the prime Offeror.

The electronic copy of each proposal must contain hyperlinks or cross-references where reference is made to other sections, tables, or figures within that document. Offerors must highlight the presence of hyperlinks or cross-references through use of different font colors and/or underlining. Each Microsoft Word electronic document shall contain a table of contents, for sections, subsections, tables, and figures, as appropriate with hyperlinks to facilitate navigation within each proposal document. The features that are native to Microsoft Office 2010 applications should be used for this purpose. Hyperlinks or cross-references must not be used to link items between different documents or proposal items or external sources.

Text

Proposals must be prepared using the 12-point Times New Roman font. Text lines must be single-spaced, and must not exceed 46 lines per column, per page, including headings. Line spacing before and after a heading must be double-spaced. Typesetting, font compression, and other techniques to reduce character size or spacing are not permitted, and will be considered a deliberate attempt to circumvent the page limitations. No pen-and-ink changes are allowed. Two-column presentation and use of bold face type for paragraph headings is acceptable. The font size for illustrations and tables must be no less than:

Art: 8-point Tables: 8-point Titles: 10-point, bold, title case

Cross-Reference Matrix

Cross referencing between factors within Volumes I-V is permitted where its use would conserve space without impairing clarity. However, each factor of Volumes I -V of the proposal shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with minimal cross referencing to other factors within Volumes I -V of the proposal. The Cross-Reference Matrices shall clearly identify the location(s) in the Offerors proposal that address or respond to each numbered requirement in Sections L and M. Where cross referencing is necessary, the Offeror must cite the specific factor, page number, section or paragraph for reference.

Information required for each factor, which is not found in its designated factor or properly cross referenced, will be assumed to have been omitted from the proposal.

The Offeror shall at a minimum provide a Cross Reference Matrix showing the traceability of Government solicitation requirements to the Offeror’s proposal.

A complete set of Cross-Reference Matrices shall be provided in the front of each volume.

Packing Instructions

Proposal binders must be packed in boxes. The boxes must be sequentially numbered with the box numbers placed on all sides of each box, and written on all sides of the outside wrapper, if necessary. Box 1 must include the electronic copy CDs, and the master packing list. The master packing list must list the contents (i.e., volume number, copy number, and volume name) of each box, by box number.

The Offeror is responsible for the condition of its delivered proposal. Binders and their contents that are broken apart or received in a disorderly fashion will be reassembled by the Government. The Government is not responsible for proper reassembly of these binders.

Furthermore, telegraphic, facsimile, or e-mail modifications of offers, or withdrawals of offers, will not be considered.

Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition; however, designated Contract Specialist(s) may contact Industry on the PCO’s behalf.

Procuring Contracting Officer

KATE ROBB

SEA 02532

TEL: 202-781-2445

Email: kate.robb@navy.mil

Contract Specialist

CAMILLE ONATE

SEA 02532O

TEL: (202) 781-4032

Email: camille.onate@navy.mil

Cost Data

Cost data shall ONLY be included in Volume VI Cost/Price Proposal. Any pages with cost information contained in volumes other than Volume VI Cost/Price will be removed and destroyed by the Contracting Officer without being evaluated.

Written Questions

Offerors may submit written questions requesting clarification of RFP requirements using Attachment J-S2, Solicitation Question Submittal Form in Excel format with the subject line: “AN/SPQ-9B Radar Design Agent Bidder Question” to the following two e-mail addresses: kate.robb@navy.mil and camille.onate@navy.mil. Potential Offerors may submit multiple Bidders Questions per Bidder Question Submittal Form by adding a row for each question.

Communications with any Government employees other than the point of contact listed above are strictly prohibited.

Information provided with each question should include a document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification. It is the Government’s intention that all question and responses will be distributed to all Offerors via RFP amendment(s). The Government will publish all questions and responses submitted via the website at https://www.fbo.gov/.

Should there be an inquiry submitted that the potential Offeror believes addresses a subject that is specific to the company (and/or addresses anything that is believed to be proprietary in nature) then the inquiry shall be marked accordingly. If the Government concurs with this identification, the Government will respond only to that potential Offeror although the Government may decline to answer such questions. Offerors are therefore encouraged to submit questions that do not contain company-specific information. If the Government does not concur with that identification, it shall inform the submitter and not provide any further response. Only written questions will receive a response and Company-specific information will be omitted from responses if released to all Offerors.

Classified questions shall be submitted in accordance with (IAW) the DD Form 254 and DoD 5220.22M NISPOM in hard copy format using the Bidders Questions Submittal Form to the PCO care of the COR. Potential Offerors shall mark each package as follows:

Marked: Bidders Question N00024-18-R-5308 Naval Sea Systems Command 1333 Isaac Hull Ave SE Washington Navy Yard, DC 20376 Attn: Kate Robb SEA02532 Procuring Contracting Officer C/O Steven Wert PEO IWS 2R1B DO NOT OPEN IN MAIL ROOM CONTACT: Steven Wert, 202-781-2976

Alternate POC Clinton May, PEO IWS 2R1C DO NOT OPEN IN MAIL ROOM CONTACT: 202-781-3683

All security related requests for Classified Material pertaining to this contract shall be submitted in writing using the Classified Material Request Form, Attachment J-S5, by the contractor's Facility Security Officer (FSO) to the individual identified in block 16(a) of DD-254 Attachment J-1.

All questions should be received within twenty (20) calendar days after receipt of RFP to allow the Government adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals.

All other publication of classified questions and answers in response to this solicitation will be mailed to potential Offerors who have completed the RFP Classified Material Request Form, Attachment J-S5, and signed the certification in accordance with the RFP.

SUBMISSION OF PROPOSAL: NAVSEA will not accept electronic submission of proposals. All copies of the proposal (Volumes I through VII) shall be submitted to the PCO at the address below by 4:00 p.m. local time at the Naval Sea Systems Command on the proposal due date.

Commander, Naval Sea Systems Command Department of the Navy

ATTN: KATE ROBB, SEA 02532

1333 ISAAC HULL AVENUE SE, MS2040, Bldg. 197

WASHINGTON NAVY YARD, DC 20376

a) It is recommended that proposals be mailed in accordance with RFP instructions. Failure to adhere to the procedures provided herein will not be considered an exception to timely proposal delivery as addressed in FAR 52.215-1.

(b) All Offerors shall mark each RFP package with the name of the Procurement Contracting Officer and the Contract Specialist, their codes and phone numbers.

DESTRUCTION OF RESTRICTED MATERIAL

By submitting a proposal, Offerors certify that they will destroy restricted information obtained in connection with this solicitation and any and all copies, notes, or other materials produced using the classified or other restricted information provided in connection with this solicitation 90 days from contract award if they are deemed an unsuccessful Offeror.

Proposal Requirements

PROPOSAL VOLUMES I THROUGH VII

VOLUME I: Introduction

Tab A: Cover Letter

The proposal shall be accompanied by a cover letter prepared on the company’s letterhead stationery and shall state the following:

The proposal is valid for 365 days from the solicitation closing date The Offeror’s Cage Code and DUNS Number All enclosures being transmitted

The Cover Letter shall be signed by an authorized representative of the Offeror who has the authority to bind the Offeror and shall include the Offeror’s authorized point of contact.

Tab B: Table of Contents

The proposal shall list the sections, subsections, and page numbers for both electronic…