OTH-WS_RFP_N00024-17-R-5430_Amendment_0002.pdf

N0002416NR43329

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

The purpose of this amendment is to revise the Section L.3.1.2 instructions for Factor 2 Subfactor 2.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 32

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

16C. DATE SIGNED

BY 10-Apr-2017

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 N00024-17-R-5430

X 9B. DATED (SEE ITEM 11)

08-Feb-2017

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

10-Apr-2017

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:

N00024-17-R-5430

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L 1.0 - General

1.1 The Contracting Officer is the sole point of contact for this solicitation; however, the designated Contract Specialist may communicate with industry on the Contracting Officer’s behalf.

The Contracting Officer for this solicitation is:

Ms. Nicole Rooney, SEA 02547

(202) 781-1088 Nicole.rooney@navy.mil

The designated Contract Specialist is:

Mr. Shaun Miles, SEA 02545

(202) 781-0798 Shaun.miles@navy.mil

1.2 The Government intends to evaluate proposals and award one contract for the production of Fire Control Suites (FCS), Launching Mechanisms (LM), and Encanistered Missiles (EM), which together constitute the Over-The- Horizon Weapons System (OTH-WS). The estimated award date is first quarter of fiscal year 2018.

1.3 This program will require access and utilization of classified information at the CONFIDENTIAL, SECRET or TOP SECRET security level. The security classification of this procurement is specified in the Contract Security Classification Specification, DD Form 254 (Attachment J-3). To be awarded a contract, the Offeror shall meet the minimum security criteria in accordance with HQ L-2-0003 FACILITY SECURITY CLEARANCE (NAVSEA)

(FEB 2012).

1.4 Classified data shall be confined to the Technical Volume, referred to herein as the Technical Proposal (Volume II). All classified data shall be managed, packaged, and delivered in strict accordance with the Contract Security Classification Specification, DD Form 254 (Attachment J-3), and the DoD National Industrial Security Program Operating Manual (DoD 5220.22-M). The Government will not accept proposal documents that are classified above the SECRET level. Appropriate security classification markings shall be included, and handling instructions followed, for all submitted data. Strict compliance with applicable law; regulation; and DoD directives, instructions, and manuals is required.

1.5 “Pricing information,” is defined as facts, statistics, or data describing the consideration an Offeror will receive in exchange for furnishing the supplies and services described in this solicitation. Pricing information shall only be included within Volume VI: Price Proposal. Inclusion of pricing information within any other Volume will likely result in rejection of the Offeror’s proposal, as well as the Offeror being determined ineligible for award. If doubt exists as to what constitutes pricing information, Offeror’s are strongly encouraged to submit a question in accordance with L 2.0 section 2.7.

1.6 Offerors shall refer to FAR 52.215-1, Instructions to Offerors -- Competitive Acquisition. The information contained in this solicitation is provided to supplement and implement FAR 52.215-1. Please note that pursuant to

FAR 52.215-1, the Government intends to award a single contract on the basis of initial proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions in accordance with FAR 15.306 if determined by the Contracting Officer to be necessary. At the end of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range.

1.7 Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and submission of multiple proposals will result in disqualification of the submitting Offeror. The Offeror’s proposal submission shall contain the Offeror’s best terms from a price and technical standpoint.

1.8 Offerors are reminded past performance information is proprietary source selection information. The Government will only discuss past performance information directly with the prospective prime or subcontractor that is being reviewed. If there is a problem with a proposed subcontractor’s past performance the prime may be notified of a problem, but no details will be discussed without the subcontractor’s permission.

1.9 RESERVED

1.10 Each Offeror must submit all information required by this solicitation. The Offeror’s proposal shall be based on the requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Failure to comply with the terms and conditions of the solicitation and/or failure to provide all of the requested information may result in the Offeror’s proposal being rejected, and may result in the Offeror being determined ineligible for award.

1.11 The solicitation will be announced through the Government-wide point of entry (GPE) at:

https://www.fbo.gov/.

1.12 The Government may post additional information to the GPE relating to this solicitation (e.g. a solicitation amendment responding to submitted Offeror questions). It is the Offeror’s responsibility to check the GPE for any such information.

1.13 All questions shall be submitted to the Contracting Officer and Contract Specialist in accordance with L 2.0 section 2.7.

1.14 The Government may schedule a pre-award site survey at facilities identified in any or all or a limited number of Offeror proposals following the proposal submission date.

1.15 RESERVED

1.16 The Government plans to use selected support contractor personnel to assist in providing Subject Matter technical expertise or provide a secure source selection facility. All such personnel will be required to execute a statement to preserve and protect from disclosure any source selection and Contractor proprietary information disclosed to them during the course of these evaluations. A list of the Contractor organizations that may participate and their intended source selection support role is as follows:

• The Johns Hopkins University Applied Physics Laboratory o Technical and Engineering Advisors

• ALION Science and Technology o Secure Source Selection Facility

If an Offeror has concerns with the firm listed above assisting during the evaluation processor providing a secure source selection facility, they must advise the PCO in writing no later than 10 days after receipt of the RFP.

Submission of an offer under this solicitation will constitute a grant of authority by the submitting company to the Government to allow access by individuals of this firm to any source selection information and information that may constitute material within the ambit of the Trade Secrets Act, 18 U.S.C. § 1905. These individuals will be performing under Government contracts that contain appropriate restrictions on the use and disclosure of information provided to the contractors (e.g., non-disclosure requirements) or will have executed Government disclosure agreements that are intended to ensure that the Contractor supports handling the information properly and in accordance with applicable law and regulation.

1.17 All notional dates (e.g. 12 months after contract award) included within this solicitation for non-option CLINs will be unilaterally changed by the Government to actual calendar dates (e.g. 5 Jan 15) at contract award. For option CLINs, notional dates will be unilaterally changed by the Government to actual calendar dates at option exercise.

SECTION L 2.0 - Instructions for Submission of Offers

The solicitation response shall be contained in six (6) separate volumes:

Volume I: Executive Summary Volume II: Technical Proposal Volume III: Data Rights Proposal Volume IV: Management Proposal Volume V: Past Performance Volume VI: Price Proposal

SECTION L 2.1 - Proposal format and delivery

The contents of the proposal (with page limitations, copy requirements, and references to explanatory paragraphs in this section) are summarized in the table below:

Section 2.1, Table 1: Proposal Summary Copies Required Volume Title Page Limit Paper Electronic

I Executive Summary 5 2 2 II Technical Proposal* 75 2 2 III Data Rights Proposal 10 2 2 IV Management Proposal* 40 2 2 V Past Performance 30 2 2 VI Price Proposal None 2 2

*The following documents do not count against the page count limit:

1. Classified binders submitted in accordance with Section L 2.6.1

2. The Small Business Subcontracting Plan submitted in accordance with Section L.3.1.4

3. The proposal attachments required to be submitted in accordance with L.3.1.2 VOLUME II “Required Technical Proposal Attachments”

2.1.1 Instructions for paper and electronic proposal submissions are detailed below in sections 2.3 and 2.4, respectively. The content of paper and electronic proposals shall be identical in form and content. In the event of discrepancies between paper and electronic copies, the content of the paper copy will prevail.

2.1.2 In order to maximize efficiency and minimize the effort involved in the proposal evaluation process, proposals must comply with the instructions for the format and content herein. Pages in excess of the established page limits will not be read or evaluated. Proposals which do not comply may be rejected, and the submitting Offeror may be determined ineligible for award.

SECTION L 2.2 - General submission requirements

2.2.1 The Letter of Transmittal submitted with Volume I shall be considered the “first page of the proposal” (see FAR 52.215-1) and shall include the elements required by FAR 52.215-1(c)(2).

The elements required by FAR 52.215-1(c)(2) are:

i. The solicitation number;

ii. The name, address, and telephone and facsimile numbers of the Offeror (and electronic address if available);

iii. A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item (to facilitate evaluation and direct comparison of received proposals, submitted proposals which do not unconditionally agree with all terms, conditions, and provisions included in the solicitation may be rejected and the Offeror may not be considered further for award);

iv. Names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this solicitation; and

v. Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office

The Letter of Transmittal shall also include:

i. The name, telephone number, and electronic mail address of the Offeror’s assigned Defense Contract Audit Agency (DCAA) Auditor;

ii. The name, telephone number, and electronic mail address of the Offeror’s assigned Defense Contract Management Agency (DCMA) Administrative Contracting Officer;

iii. The Offeror’s Dunn and Bradstreet (DUNS) number;

iv. The Offeror’s Commercial and Government Entity (CAGE) code;

v. A statement certifying electronic data submitted is free of computer viruses and other malware;

vi. A statement certifying the proposal is valid for 365 days from the closing date of the solicitation;

vii. A statement providing unconditional agreement with all terms, conditions, and provisions included in the solicitation;

viii. Any statement required by solicitation provision HQ L-2-0005 Notification of Potential

Organizational Conflict(s) of Interest (NAVSEA) (JUN 1994); and

The Letter of Transmittal shall serve as the cover letter for Volume I and a separate cover letter is neither required, nor desired.

2.2.2 Volumes II- VI shall each contain a cover letter containing:

i. Offeror name, address, and point of contact

ii. Offeror point of contact phone number and electronic mail address

ii. Offeror CAGE code and DUNS number

iii. Title of proposal, proposal number, and RFP number (N00024-17-R-5430)

iv. Volume number and title (e.g. “Volume II – Technical Proposal ”)

2.2.3 To facilitate evaluation of each received proposal, each volume should also include the following:

i. Table of Contents, Tables, and Figures. The Table of Contents should include the first through third level section titles. A separate list of tables and figures utilized in the proposal volume should be appended at the end of the Table of Contents.

ii. Glossary of Terms, Abbreviations, and Acronyms. The Glossary of Terms, Abbreviations, and

Acronyms should include all utilized abbreviations, acronyms, and all terms which are either newly introduced, uncommon, or specialized.

iii. Index of Terms. The Index of Terms should include key words, phrases, or alphanumerical terms, and refer to where they appear in the text of the proposal volume.

2.2.4 Duplicated information within a given factor may be included in full once and referenced thereafter, as long as there is a clear reference to the duplicated information. If duplicated information is included for more than one evaluation factor, it must be included in full text the first time it is discussed under each factor.

2.2.5 A concise, legible, neat, orderly and comprehensive proposal is required. Brochuremanship is not desired.

Elaborate brochures, artwork, expensive paper and bindings, or expensive visual or other presentation aids beyond those sufficient to present a complete and comprehensive written proposal are unnecessary and will be included in enforcement of page count requirements. Clarity is essential.

2.2.6 Proposals must present information in sufficient depth for the Government to make a comprehensive evaluation of the Offeror’s understanding of, and capability to, meet the requirements of this solicitation. Offerors bear the burden of submitting a clear and unambiguous proposal that is fit for evaluation. Offerors shall provide all information necessary to demonstrate their ability to meet the requirements of the solicitation. Discussion of each factor in the proposal shall be self-contained (i.e., data shall be organized to enable Government personnel to thoroughly evaluate the proposal against specific factors established in Section M), and must be separated within each volume by a side tab file divider.

SECTION L 2.3 - Paper submission

2.3.1 Each volume shall be bound separately in three ring binders and shall not exceed the page limitations cited above. Volumes I-VI shall each be presented separate from the remainder of the proposal (i.e. each Volume shall be submitted in a single or multiple binders separately and discretely from all other volumes; no binder should contain material from more than one Volume). Discussion of each factor and subfactor within a binder shall also be separate and discrete, and shall be separated by a side tab file divider.

2.3.2 The Offeror’s company name, proposal number, and RFP number (N00024-17-R-5430) shall appear at the top of each page in the header section (from left to right). The date of submittal, page numbers and the corresponding electronic file name shall be placed on each page of the proposal in the footer section (from left to right).

2.3.3 Revisions (including but not limited to FPRs) will only be received and considered at the specific request of the Contracting Officer. Any pages revised must include the date of revision in the place of the date of submittal, and shall also contain a revision number (e.g. 12 Dec 2017 - Revision 1). Revisions shall be submitted in the form of change pages (allowing for substitution of the entire page—front and back if used—where the revision is located).

2.3.4 The narrative material in each proposal shall be single spaced, typed or printed in Times New Roman font with type no smaller than 12-point font. Paper, excluding foldout pages (see paragraph 2.3.5, below), shall be 8 1/2 x 11 inches with a minimum margin of 1 inch around the page. Any type contained within tables, graphs, etc. shall not be smaller than 8-point Times New Roman font.

2.3.5 Foldout pages (Foldouts) may be used for charts and graphs where necessary to depict organization, layout or implementation schedules. Foldouts shall be uncomplicated to preserve clarity. Written text or tabular data, beyond that which is reasonably required for clarity should not be included in the material presented on the foldout sheet.

Foldouts shall fold entirely within the volume and shall be limited in size to no more than 11 x 17 inches. Each foldout shall contain printed material on only one side of the foldout. Each foldout page will be regarded as two pages for page count purposes.

2.3.6 The following items will not be considered pages for the purposes of page count limitations (but still shall conform to formatting requirements detailed herein):

i. Blank pages

ii. Cover letters

iii. Table of Contents, Tables, and Figures

iv. Glossary of Terms, Abbreviations, and Acronyms

v. Index of Terms

2.3.7 Only pages which count against page count limitations shall be numbered. Pages excluded from page count limitations (i.e. items in paragraph 2.3.6, above) must contain only material pertinent to the page heading and the page heading must clearly indicate the name of the item. Blank pages should be marked "Intentionally Left Blank."

Pages submitted which are not excluded from page count limitations (i.e. items in paragraph 2.3.6, above), and which exceed the page count limitations provided in Section 2.1— Table 1 (e.g. any pages following the 30th page of the past performance volume), will be removed and will not be evaluated.

2.3.8 Each submitted paper proposal page shall also include standard 2-3/4" center-to-center holes positioned symmetrically at the top of each page (i.e. 2-hole filebinder punch on top edge).

SECTION L 2.4 - Electronic submission

2.4.1 Submitted electronic files shall not be compressed. Each Volume shall be submitted on a separate DVD, and a set of six DVDs (one for each Volume) constitutes an electronic copy of the proposal. Submission of two copies of the electronic proposal is required.

2.4.2 Included files shall be created/prepared using Microsoft Office 2010 compatible applications. Spreadsheets, worksheets, and workbooks shall be prepared using Microsoft Excel compatible applications. Schedules shall be created and submitted using Microsoft Project compatible applications. Graphics, photographs, and other data beyond the capability of Microsoft Office 2010 compatible applications may be submitted in Adobe Acrobat format.

Submitted electronic files shall be limited to the following extensions:

.docx Microsoft Word .xlsx Microsoft Excel .pptx Microsoft PowerPoint .pdf Adobe Acrobat

.mmpx Microsoft Project

2.4.3 Pricing information for the supplies and services solicited here shall only be included within the DVD containing Volume VI: Price Proposal. Inclusion of pricing information on any other DVD may result in the Offeror’s proposal being rejected, and the Offeror being determined ineligible for award. If doubt exists as to what constitutes pricing information, Offeror’s are strongly encouraged to submit a question in accordance with paragraph

2.7 of this section.

2.4.4 Each submitted disc shall be labeled with the following:

i. “RFP N00024-17-R-5430”

ii. Date of submittal

iii. Volume number

iv. Offeror name, address, and point of contact

v. Offeror point of contact phone number and electronic mail address

2.4.5 Audio or video shall not be included on any submitted DVDs. Inclusion of audio or video on any submitted DVD may result in the Offeror’s proposal being rejected, and may result in the Offeror being determined ineligible for award.

2.4.6 Electronic spreadsheets shall not be compiled or password protected; and all cells and formulas shall be visible, editable, and unprotected. Formulas shall be maintained in each Excel sheet to permit verification of calculations, and revision of output(s) through variation of inputs(s).

2.4.7 Any tables contained within submitted narrative must be capable of being edited (i.e. not embedded pictures or screenshots).

2.4.8 Submitted files shall not reference external data.

SECTION L 2.5 - Proposal submission

2.5.1 Proposal submissions not conforming to submission requirements may not be evaluated, and the Offeror may be determined ineligible for award.

2.5.2 All copies of all proposal volumes shall be submitted on or before the date and time in Block 9 of the SF 33.

NAVSEA will not accept electronic submission of proposals. All copies of the proposal shall be submitted to the PCO or Contract Specialist at the address below and marked as follows:

Commander, Naval Sea Systems Command Department of the Navy ATTN: Nicole Rooney, SEA02547 1333 ISAAC HULL AVENUE SE, MS2040, Bldg. 197, Room 5W-1625

WASHINGTON NAVY YARD, DC 20376

RFP: N00024-17-R-5430

DO NOT OPEN IN THE MAILROOM;

CONTACT NICOLE ROONEY (202) 781-1088

Hand carried offers shall be delivered by carrier to: See HQ L-2-0013 SPECIAL PROPOSAL RECEIPT REQUIREMENTS (NAVSEA) (APR 2015) for special instructions

SECTION L 2.6 – Classified Material

2.6.1 If the Technical Volume requires classified information, it shall be submitted as a separate annex, shall be classified no higher than SECRET and bound in a red binder if Secret or blue binder if Confidential. No unclassified volume shall be bound in a red binder. Further guidance is provided by the DD Form 254 (Attachment J-3) and the DoD 5220.22M NISPOM.

2.6.2 A copy of the classified Top Level Requirements Document (TLRD) will be required for an Offeror to provide an acceptable proposal. Requests for a copy of the TLRD shall be sent via electronic mail, within seven (7) calendar days after issuance of this solicitation, to the Contracting Officer and designated Contract Specialist using Attachment J-S3 and Attachment J-S9. To obtain a copy of the TLRD the forms must include all requested information.

SECTION L 2.7 - Offeror questions

2.7.1 RESERVED

2.7.2 Offerors may submit written unclassified questions using Attachment J-S1, Question Submittal Form, with the subject line:

“N00024-17-R-5430 Offeror Question”

Unclassified questions shall be sent via electronic mail to the Contracting Officer and designated Contract Specialist. Only unclassified questions submitted using the provided .xlsx file attachment (attached to an electronic mail message addressed to the Contracting Officer and designated Contract Specialist) will be answered. Multiple questions may be submitted per .xlsx file by adding a row for each question.

2.7.3 Questions concerning the classified TLRD (Attachment J-6) shall be submitted in accordance with the DD Form 254 and the DoD 5220.22M NISPOM.

2.7.4 If citing a document in a submitted question, the specific document name, document date, page, paragraph, clause or other definitive citation requiring clarification must be included. It is anticipated all questions and responses will be distributed to all Offerors via solicitation amendment(s) published to the GPE.

2.7.5 The Government will confirm receipt of all questions, by electronic mail, within five calendar days. It is the responsibility of the Offeror to ensure all questions are received by the Government, and Offerors are encouraged to contact the Contracting Officer and designated Contract Specialist by electronic mail if a confirmation is not received within five calendar days.

2.7.6 The Government commits to respond to all questions received within twenty (20) calendar days after issuance of this solicitation. The Government will continue to accept questions up to the closing time of the solicitation;

however, time may not permit responses to questions received after the twenty (20) day period.

SECTION L 3.0 – Proposal Content

The OTH-WS proposal shall be organized in accordance with the following instruction. FAILURE TO FOLLOW

THESE INSTRUCTIONS MAY RESULT IN REJECTION OF THE PROPOSAL.

3.1 TECHNICAL VOLUMES (Volumes I through Volume V)

The Technical Volumes shall be limited to the page limits outlined in Section L.2.1 (and below). Price information shall be completely omitted from the Technical Volumes.

L3.1.1 VOLUME I - EXECUTIVE SUMMARY

The Executive Summary Volume shall summarize the Offeror’s planned approach to satisfy the Government’s requirements. Key elements of the proposal shall be highlighted for both technical and management perspective. The Executive Summary Volume will not be formally evaluated and will not be incorporated as part of the contract awarded to the successful Offeror. As an appendix to the Executive Summary Volume, the Offeror shall complete Cross Reference Matrix (CRM) (Attachment J-S5) for the Technical Volumes. The CRM does not count against any of the proposal page limitations. If this matrix conflicts with any other portion of this solicitation, such other reference shall take precedence over this matrix.

L.3.1.2 VOLUME II - TECHNICAL PROPOSAL

Except for the Encanistered Missile (EM) Capital Warship Range requirement (TRLD paragraph 3.1.1.2 ) and Size, Weight, Power and Cooling (SWaP-C) requirement (TLRD paragraphs 3.2.2.1-3.2.2.6), the full TLRD requirements establish the minimum OTH-WS Performance Requirements. In order to enhance and promote the competitive environment, the Government has, as outlined below, established minimum Government solicitation requirements for EM Capital Warship Range and SWaP-C. For EM Capital Warship Range, the minimum Government solicitation requirement is X-60 nautical miles (nm) (where X equals the full TLRD nm requirement in paragraph 3.1.1.2). For SWaP-C, the minimum Government solicitation requirement is that an OTH-WS must meet the full TLRD requirements with at least 2 missiles loaded in a LM. However, in order to be eligible for award, an OTH- WS must meet the full TLRD requirement for either EM Capital Warship Range or SWaP-C, and the minimum Government solicitation requirement for the other TLRD requirement that it does not meet.

Therefore, in order for a proposal to be determined eligible for award, an Offeror’s proposal shall either:

A) Demonstrate that its OTH-WS meets the full TLRD Performance Requirements, including EM Capital Warship Range and SWaP-C; or

B) Demonstrate that its OTH-WS meets one of the following two scenarios:

1. Scenario 1:

a) its OTH-WS meets the full TLRD Performance Requirements, except for EM Capital Warship Range (TRLD paragraph 3.1.1.2);

b) its OTH-WS meets the minimum Government solicitation requirement for EM Capital Warship Range (X-60nm); and

c) its OTH-WS Improvement Plan is rated as 'Marginal' or better;

or

2. Scenario 2:

a) its OTH-WS meets the full TLRD Performance Requirements, except for SWaP-C (TLRD paragraphs 3.2.2.1-3.2.2.6);

b) its OTH-WS meets the minimum Government solicitation requirement for SWaP-C (meet the full TLRD requirements with at least 2 missiles loaded in a LM); and

c) its OTH-WS Improvement Plan is rated as 'Marginal' or better.

The Technical Proposal Volume includes Factor 1: Technical Approach for Go/No Go OTH-WS Requirements and Factor 2: Technical Approach for EM Warship Range, EM Penetration, SWaP-C, and OTH-WS Improvement and shall enable evaluators to make a thorough evaluation and arrive at a sound determination of whether the proposal meets the requirements of the RFP. To this end, the Technical Proposal Volume shall be specific, detailed, and complete. Proposals shall include the block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror’s proposed concept. The technical section must be sufficient to show how the Offeror proposes to comply with the Government’s requirements and include a full explanation of the methodology and procedures to be followed. The Technical Proposal shall be structured as follows:

Cover Letter: See paragraph 2.2.2, above, for a discussion of the content requirements for the Cover Letter.

Table of Contents, Tables, and Figures: See paragraph 2.2.3(i), above, for a discussion of the content requirements for the Table of Contents, Tables, and Figures.

Glossary of Terms, Abbreviations, and Acronyms: See paragraph 2.2.3(ii), above, for a discussion of the content requirements for the Glossary of Terms, Abbreviations, and Acronyms.

Index of Terms: See paragraph 2.2.3(iii), above, for a discussion of the content requirements for the Index of Terms.

1. Introduction

Provide a short narrative description of the Offeror’s OTH-WS solution.

2. Technical Proposal Narrative

2.1 Factor 1: Technical Approach for Go/No Go OTH-WS Requirements

2.1.1 Go/No Go OTH-WS Top Level Requirements Document Requirements

The Offeror shall complete the OTH-WS Compliance Matrix Part I (Attachment J-S7) and provide a narrative for each Performance Requirement listed in Part I, demonstrating that its proposed OTH-WS complies with each TLRD requirements listed. The narrative shall address the supporting documents required by OTH-WS Compliance Matrix Part I.

OTH-WS Compliance Matrix Part I

TLRD

Paragraph Performance

Req.

Offeror Meets

PIDS1 Lower Level

Installation Control

Test Data1

M&S

Algorithm Description

No. Req.

(Y/N)

Document1 Drawing/ Interface Control

Document1

Document1

3.1.1.13 FAC Range4 N/A2

3.1.2.13 Seeker

Attribute 1

N/A2

3.1.2.23 Seeker

Attribute 2

N/A2

3.1.33 Self-

Termination

N/A2

3.1.43 Missile

Egress

N/A2

3.1.63 Operating

Environment

N/A2 N/A2

3.2.33 Electrical

Interface

N/A2 N/A2

3.2.4.13 Operator

Interface

N/A2

3.2.4.23 Engagement

Planning

N/A2

3.2.5.13 Selective

Availability Anti- Spoofing Module

N/A2

3.2.5.23 Navigation

Data

N/A2

3.2.5.33 GPS Data N/A2

3.2.6.1 Telemetry N/A2 N/A2 N/A2

3.2.6.2 Flight

Termination System

N/A2

3.2.7.1 Missile

Retention Mechanism

N/A2 N/A2

3.2.7.2 System

Interconnects

N/A2 N/A2 N/A2

3.3.1 Non-

Development al Item (NDI)

N/A2 N/A2 N/A2 N/A2 N/A2

3.3.2 Producibility N/A2 N/A2 N/A2 N/A2 N/A2

Note 1: Offerors shall include in the completed matrix all applicable: Document Number(s), Title(s), and Identifier (e.g. paragraph, WBS, etc.)

Note 2: For items marked N/A, no supporting documents will be required to be provided for that performance requirement.

Note 3: Additional information related to the required supporting evidence that Offerors shall utilize is contained in the table below.

Factor 1 Supporting Evidence

Paragraph

No.

Performance Req.

Required Supporting Evidence

Required Parameters for Supporting Evidence

Required Units

3.1.1.1 FAC Range 1. Flight Profile ADD

2. Test Reports

3. 100 Monte Carlo simulations using scenario one (1) in M&S Table 1

Operational Range Envelope for Weapon nmi and/or km

3.1.2.1 Seeker

Attribute 1

1. ADD Seeker A1

2. Clutter models used

3. Atmospheric effects models used

4. Land mass, atmospheric effects, and clutter rejection

ADD

5. Test Data and Reports (Actual and/or Simulated)

Seeker Field-of-Regard (FOR) deg Seeker Field-of-View (FOV) deg Maximum Seeker Detection Range nmi and/or km

Min and Max Seeker Acquisition Range nmi and/or km

Seeker Type (IR, Active RF, Passive RF)

Seeker Wave Form Discrimination methodology Clutter Rejection Susceptibility/Resistance to Jamming

Seeker Frequency Band Search Pattern/Search Process/Land Mapping

Search Area Rad/ft/M Environmental Restrictions / Constraints

Blind Range ft and/or m

3.1.2.2 Seeker

Attribute 2

1. Seeker A2 ADD

2. Test Data and Reports (Actual and/or Simulated)

Seeker Resolution Mrad Instantaneous Field-of-View

(IFOV)

ft and/or m

Seeker Properties (IR, Active RF, Passive RF) watt/ster band/wavel ength

Seeker Power watt Seeker Turn on-off Times sec Minimum Resolvable Temperature degrees C and F

Minimum Detectable RCS dbm2

3.1.3 Self-

Termination

1. Self-Termination ADD

2. Test Data and Reports (Actual and/or Simulated)

Command Distruct Function Yes / No Self-Terminate Function Yes / No Reliability

3.1.4 Missile

Egress

1. Missile Fly-out ADD

2. Safe and Arm ADD

3. Test Data and Reports (Actual and/or Simulated)

Booster Separate Altitude ft and/or m Booster Separate Time sec Splash Point relative to the ship ft, m and degrees Booster Burn Rate Model Function ft*lbs/sec2 and nm

Atmospheric Wind Dynamics during boost phase ft/sec and m/sec

Missile Boost Angle degrees

Safe and Arm Methodology Safe and Arm Reliability Fuze Methodology Probably of Inadvertent Operation (warhead & propulsion system)

Missile Launch Platform Dynamics (R, P, Y) degrees/sec

3.1.6 Operating

Environment

1. Test Data and Reports Sea State Beaufort Topside Ice Loading kN/M2 Air Temperature Degrees C Relative Humidity %

Humidity Rain Rate In/hr

3.2.3 Electrical

Interfaces

1. Test Data and Reports System Electrical Attributes kWh, Voltage, Amperes

3.2.4.1 Operator

Interface

1. Service/Shelf Life Predictions

2. Prediction analysis description

3. Test Data and Reports (Actual and/or Simulated)

Expected Service Life months Expected Shelf Life months Expected Max Remain Afloat Time months

Expected Maintenance Duration days

3.2.4.2 Engagement

Planning

1. M&S ADD

2. Test Data and Reports (Actual and/or Simulated)

Minimum Targeting Data Accuracy Requirements

Environmental Restrictions / Constraints

Targeting Data Timing Requirements

Message Format Message Content Weapon Initialization Time Required Before Launch sec

Readiness Time sec Initialization Procedures and Timeline

Initialization Message(s) Content

Dynamic Transfer Alignment Time sec

Prelaunch Sequence sec Waypoint Planning Capability Route Planning Application Software

3.2.5.1 Selectivity

Availability Anti- Spoofing Module

1. Test Data and Reports (Actual and/or Simulated)

SAASM Compliant GPS receiver

Yes / No

SAASM Compliant testing Yes / No

3.2.5.2 Navigation

Data

1. Guidance & Navigation

ADD

2. Test Data and Reports (Actual and/or Simulated)

Navigation error

3.2.5.3 GPS Data 1. Guidance & Navigation

ADD

2. Test Data and Reports (Actual and/or Simulated)

GPS Constellation Data/Satellite Modeling

Note 4: For TRLD requirement 3.1.1.1 (FAC Range), Offerors shall utilize the M&S Table 1: Range Scenario conditions for their modeling and simulation scenario, and provide the noted following required modeling and simulation scenario output data.

M&S Table 1: Range Scenario

Scenario: FAC Range as defined in the TLRD, 3.1.1.1

Conditions Required data from Offeror’s M&S for each scenario

Ship and target positions: 270o true West

Offeror’s assumptions

Ship speed: 10 knots (heading true West)

Threat parameters as described in TLRD: Range, Velocity, Type/Size

Threat: Heading true East, notional speed as defined in the TLRD, 1.3.1.2

Data set from 100 Monte-Carlo runs

Side launching system for OTH missile

Maximum range (NM) as defined in the

TLRD, 3.1.1.2

Sea state: 3 on Beaufort scale 3-sigma range variance Air temperature: 95oF (35oC) Probability of Hit (Ph) Water Temperature: 85oF Circular Error Probable (CEP) 90 Relative humidity: 80% CEP is defined as the square root of the mean square error (MSE). The MSE will be the sum of the variance of the range error plus the variance of the azimuth error plus the covariance of the range error with the azimuth error plus the square of the bias.

Absolute humidity: 24 g/m3 CEP 50 Wind: 30o NE cross wind 10 knots true

Miss Distance (distance from the target) (m)

Visibility: 8 NM Altitude, Cross-range and down-range profiles & trajectory (ft and m) for all phases of flight

Evaporative Duct Height: 30 ft Any pre-programmed waypoints or autonomous waypoints used for missile transit to target

Cloud coverage: Clear Total time of flight to target (seconds) Daytime engagement with clear sky

Terminal guidance scheme: Seeker capability (active/passive), Seeker activation range (meters from target), Seeker Field-Of-View (FOV) (degrees), and Seeker Field-Of-Regard (FOR) (degrees)

No countermeasure or AAW from threat

Range target acquired (m)

Other features

2.1.2 Go/No Go OTH-WS CLIN Requirements

Mission Support Equipment: The Offeror shall provide a narrative description of the proposed Mission Support Equipment, demonstrating that the proposed mission support equipment meets the Government’s requirements in SOW paragraph 1.11. This narrative shall address the equipment list provided as Attachment J-14, as well as the PIDS associated with the mission support equipment (Attachment J-13 Enclosure I).

Training Materials: The Offeror shall provide a narrative description of the proposed Training Materials demonstrating that the proposed Training Materials meets the Government’s requirements in SOW paragraph 1.10.

This narrative shall address the equipment list provided as Attachment J-15, as well as the PIDS associated with the FCS Training Module (Attachment J-13 Enclosure G) and Encanistered Missile – Training Round (EM-TR) (Attachment J-13 Enclosure H).

2.1.3 Material Requirements

In accordance with FAR 52.211-5, if an Offeror proposes the use of “Used, reconditioned, or remanufactured supplies, or unused former Government surplus property,” for Go/No Go requirements, EM Capital Warship Range, EM Penetration, SWaP-C, and/or OTH-WS Improvement the Offeror shall address the requirements listed in paragraphs (c) and (d) of the clause, as applicable. To address these requirements, Offerors shall fill out Attachment JS-10 - Material Matrix.

2.2 Factor 2: Technical Approach for EM Capital Warship Range, EM Penetration, SWaP-C, and OTH-WS Improvement

2.2.1 Subfactor 1: EM Capital Warship Range

The Offeror shall complete the OTH-WS Compliance Matrix Part II (Attachment J-S7) and provide an EM Capital Warship Range narrative for its proposed OTH-WS solution, demonstrating the existing EM Capital Warship Range capabilities of the proposed solution. The narrative shall address the supporting documents required by the below OTH-WS Compliance Matrix Part II.

OTH-WS Compliance Matrix Part II

Paragraph No.

Performance Req.

Offeror Meets Req.

(Y/N)

PIDS1 Lower Level

Document1

Installation Control

Drawing/ Interface Control

Document1

Test Data1

M&S1 Algorithm Description Document1

3.1.1.23 Capital

Warship Range4

N/A2

Note 1: Offerors shall include in the completed matrix all applicable: Document Number(s), Title(s), and

Note 2: For items marked N/A, no supporting documents will be required to be provided for the Capital Warship Range requirement.

Note 3: Additional information related to the required supporting evidence that Offerors shall utilize is

Subfactor 1 Supporting Evidence

Paragraph Performance

Req.

Required Supporting

Evidence Required Parameters for

Supporting Evidence Required

Units

No.

3.1.1.2 Capital

Warship Range

1. Flight Profile ADD

2. Test Data/ Report

3. 100 Monte Carlo simulations using scenario two

(2) provided M&S Table 1

Maximum Operational Range of Weapon* nmi and/or km

Effective Operational Range of the Weapon** nmi and/or km

Operational Range Envelope for Weapon*** nmi and/or km

Total Time of Flight Probability of Hit (Phit) Circular Error Probable

(CEP) 90

CEP 50

Note 4: For TRLD requirement 3.1.1.2 (Capital Warship Range), Offerors shall utilize the M&S Table 2: Range Scenario conditions for their modeling and simulation scenario, and provide the noted following required modeling and simulation scenario output data.

* Maximum Operational Range of Weapon - The maximum range that the weapon can go under the conditions that were provided in the scenario.

** Effective Operational Range of the Weapon - The maximum range that the weapon can go with a 90% chance to hit the target in the conditions that were provided in the scenario.

*** Operational Range Envelope for Weapon - The three dimensional envelope that the weapon is capable of flying.

In other words, how altitude and terminal maneuver(s) affect the weapon

M&S Table 2: Range Scenario Scenario: Capital Warship Range as defined in the TLRD, 3.1.1.2

Conditions Required data from Offeror’s M&S for each scenario

Ship and target positions: 270o true West

Offeror’s assumptions

Ship speed: 10 knots (heading true West)

Threat parameters as described in TLRD: Range, Velocity, Type/Size

Threat: Heading true East, notional speed as defined in the TLRD, 1.3.1.2

Data set from 100 Monte-Carlo runs

Side launching system for OTH missile

Maximum range (NM) as defined in the

TLRD, 3.1.1.2

Sea state: 3 on Beaufort scale 3-sigma range variance Air temperature: 95oF (35oC) Probability of Hit (Ph) Water Temperature: 85oF Circular Error Probable (CEP) 90 Relative humidity: 80% CEP is defined as the square root of the mean square error (MSE). The MSE will be the sum of the variance of the range error plus the variance of the azimuth error plus the covariance of the range error with the azimuth error plus the square of the bias.

Absolute humidity: 24 g/m3 CEP 50 Wind: 30o NE cross wind 10 knots true

Miss Distance (distance from the target) (m)

Visibility: 8 NM Altitude, Cross-range and down-range profiles & trajectory (ft and m) for all phases of flight

Evaporative Duct Height: 30 ft Any pre-programmed waypoints or autonomous waypoints used for missile transit to target

Cloud coverage: Clear Total time of flight to target (seconds) Daytime engagement with clear sky

Terminal guidance scheme: Seeker capability (active/passive), Seeker activation range (meters from target), Seeker Field-Of-View (FOV) (degrees), and Seeker Field-Of-Regard (FOR) (degrees)

No countermeasure or AAW from threat

Range target acquired (m)

Other features

2.2.2 Subfactor 2: EM Penetration

The Offeror shall complete the OTH-WS Compliance Matrix Part III (Attachment J-S7) and provide an EM Penetration narrative for its proposed OTH-WS solution, describing the existing EM Penetration capabilities of the proposed solution. Specifically, the Offeror shall discuss the techniques and system attributes used by the proposed OTH-WS to achieve a successful engagement against Fast Attack Craft (FAC) and Capital Warship threats that can employ self-defense measures, as defined in the OTH-WS Top Level Requirements Document (Attachment J-6).

The discussion shall include all aspects and/or techniques of the missile and associated weapon system to evade, spoof, or combat enemy threat detection and self-defense capabilities. The narrative shall address the supporting documents required by the below OTH-WS Compliance Matrix Part III.

OTH-WS Compliance Matrix Part III

Paragraph No.

Performance Req.

Offeror Meets Req.

(Y/N)

PIDS1 Lower Level

Document1

Installation Control

Drawing/ Interface Control

Document1

Test Data1

M&S1 Algorithm Description Document1

3.1.53

Missile Penetration

N/A2

Note 1: Offerors shall include in the completed matrix all applicable: Document Number(s), Title(s), and

Note 2: For items marked N/A, no supporting documents will be required to be provided for that performance requirement.

Note 3: Additional information related to the required supporting evidence that Offerors shall utilize is

Subfactor 2 Supporting Evidence

Paragraph No.

Performance Req.

Required Supporting Evidence

Required Parameters for Supporting Evidence

Required Units

3.1.5 Missile

Penetration

1. Terminal Guidance ADD

2. Other ADDs as appropriate

3. Test Data and Reports (Actual and/or Simulated)

Circular Error Probable

(CEP) 90

CEP 50

Altitude at All Phases of ft and/or m

Flight min/max Velocity at All Phases of Flight (Max Range) m/sec

Velocity at All Phases of Flight (Min Range) m/sec

Velocity at All Phases of Flight (Mid Range) m/sec

In-Flight Route Planning Capability

Maximum Missile Maneuverability g's

Airframe Trun Radius Peak to Peak g's

Maneuverability Max Horizontal Width* ft

Maneuverability Max Vertical Width** ft

Weapon Airframe Structural Limits g's

Terminal Guidance Scheme Control Surface Limits Terminal Maneuvers Engagement planning process model (sequential vs simultaneous arrival)

Engagement Timeline (Time of Flight) sec

Time on Target Control Capability

Salvo Size (rate of fire) sec Salvo Size (max EM's that can be powered on simultaneously)

No. of Missiles

Anti-jamming scheme Decoy / Countermeasure Discrimination Methodology

Note 3: Offerors shall utilize the M&S Table 3: Penetration Scenario conditions for their modeling and simulation scenario, and provide the following noted required modeling and simulation scenario output data.

*"Maneuverability Max Horizontal Width" - assuming the missile is maneuvering for survivability, this is the maximum width of that maneuverability in the horizontal axis.

**"Maneuverability Max Vertical Width" - assuming the missile is maneuvering for survivability, this is the maximum height of that maneuver in the vertical axis.

M&S Table 3: Penetration Scenario

Scenario: 1 Weapon vs. 1 Capital Warship at 50 NM Conditions Required data from Offeror’s M&S for the scenario Ship and target positions: 270o true West Offeror’s assumptions Ship speed: 10 knots (heading true West) Threat parameters as described in TLRD: Range, Velocity, Type / Size Threat: Heading true East, notional speed as defined in Data set from 100 Monte-Carlo runs the TLRD, 1.3.1.2 Range at time of launch is 50 NM 3-sigma range variance Side launching system for OTH missile Probability of Hit (Ph) Sea state: 3 on Beaufort scale 90 CEP Air temperature: 95oF (35oC) 50 CEP Water Temperature: 85oF Miss Distance (m) Relative humidity: 80% Altitude, cross-range and down-range profiles and trajectory (ft and m) Absolute humidity: 24 g/m3 Any pre-programmed waypoints or autonomous waypoints used for missile transit to target Wind: 30o NE cross wind 10 knots true Total time of flight to target (seconds) Visibility: 8 NM Terminal guidance scheme: Seeker capability (active / passive), Seeker activation range (meters from target), and Seeker Field-Of-View (FOV) (degrees)

Evaporative Duct Height: 30 ft Range target acquired (m) Cloud coverage: Clear Other features Daytime engagement with clear sky Target characteristics as defined in TLRD, 1.3.1.2

2.2.3 Subfactor 3: Space, Weight, Power and Cooling

The Offeror shall complete the OTH-WS Compliance Matrix Part IV (Attachment J-S7) and shall provide a SWaP- C narrative for its proposed OTH-WS solution, demonstrating the SWaP-C attributes of the proposed OTH-WS solution. The narrative shall address the supporting documents required by the below OTH-WS Compliance Matrix Part IV.

OTH-WS Compliance Matrix Part IV

Paragraph No.

Performance Req.

Offeror Meets Req.

(Y/N)

PIDS1 Lower Level

Document1

ICD1 Test Data1

M&S1 Algorithm Description Document1

3.2.2.1 Above Deck

Footprint

N/A2 N/A2 N/A2

3.2.2.2 Above Deck

Volume

N/A2 N/A2 N/A2

3.2.2.3 Below Deck

Volume

N/A2 N/A2 N/A2

3.2.2.4 Weight N/A2 N/A2 N/A2

3.2.2.5 Power

Allocation N/A2 N/A2 N/A2

3.2.2.6 Cooling

Allocation

N/A2 N/A2 N/A2

Note 1: Offerors shall include in the completed matrix all applicable: Document Number(s), Title(s), and

Note 2: For items marked N/A, no supporting documents will be required to be provided for the SWaP-C requirement.

2.2.4 Subfactor 4: OTH-WS Improvement

For proposed OTH-WSs that do not meet the TRLD requirements for both the EM Capital Warship Range requirement (TLRD paragraph 3.1.1.2), and the SWaP-C requirement (TLRD paragraphs 3.2.2.1-3.2.2.6), but meets the TLRD for one of these requirements, and meets the minimum Government solicitation requirement (as described in L.3.1.2) for the other requirement, the Offeror shall provide a narrative plan that demonstrates the Offeror’s approach to meeting the OTH-WS Improvement requirements as described in Section C paragraph 4.4, and ability to deliver…