0009.pdf

N0002414NR42054

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

This amendment is hereby issued to update the responsible contracting off icer throughout the solicitation. All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 32

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

16C. DATE SIGNED

BY 13-Jul-2015

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-14-R-5353

X 9B. DATED (SEE ITEM 11)

19-Aug-2014

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

13-Jul-2015

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-14-R-5353

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

PURCHASING OFFICE ATTN: Nicholas DeSelle

REPRESENTATIVE: NAVAL SEA SYSTEMS COMMAND

1333 ISAAC HULL AVENUE SE STOP SEA 02535

WASHINGTON NAVY YARD DC 20376

Telephone No. 202-781-0717

Email Address: nicholas.deselle@navy.mil

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

CLASSIFIED MATERIAL

There are two classified attachments at the SECRET/US Only level to the solicitation. Offerors seeking access to the classified attachments must completely fill out the "RFP Classified Material Request Form” within seven (7) business days of receipt of RFP N00024-14-R-5353. Completed forms are to be submitted to

Amy Arabucki at amy.arabucki@navy.mil with a copy to peggy.davidson@nrl.navy.mil and nicole.gerow@navy.mil. Once approved, the Government will mail a classified CD/DVD to the Offeror.

GENERAL

The Government desires to procure hardware, firmware, software, and data required to develop, fabricate, integrate, test, evaluate, and sustain an Advanced Off-Board Electronic Warfare (AOEW) Active Mission Payload (AMP).

This AOEW AMP shall be integrated with existing Electronic Warfare (EW) systems to meet requirements specified in the AOEW AMP System Scope Document (SSD) provided as Government Furnished Information (GFI) described on Attachment J-4. The AOEW AMP shall be developed to integrate onto an MH-60R and MH-60S as the host platform for fleet introduction of the AOEW AMP capability. AOEW decoys will provide an improved EW capability to Navy vessels to defend against legacy and emerging anti-ship missile threats. The AMP will be integrated with United States Navy Surface EW systems including AN/SLQ-32 variants (SEWIP Blocks 2 and 3), Nulka, and any future decoys via external interfaces with the host platform and AN/SLQ-32 both with and without

Soft Kill Coordinator Subsystem (SKCS). Minimum modifications to existing systems (e.g. the host platform, AN/SLQ-32, and/or the ship’s Combat Management System (CMS)) will be required and changes will require

Government approval. The proposed technical approach must demonstrate how system design methodologies incorporate Modular Open Systems Approach (MOSA) that allow for technology insertion of market driven mailto:amy.arabucki@navy.mil mailto:peggy.davidson@nrl.navy.mil mailto:nicole.gerow@navy.mil technological improvements as well as developing systems using modular design concepts. 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 Attachment J-1 from

Preliminary Design through delivery of Engineering Development Models (EDMs) and Low-Rate Initial Production

(LRIP) units that meet the SOW Attachment J-1 requirements. 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)). Each Offeror shall submit only one proposal which represents its best approach to meeting the requirements of the solicitation. Only one offer will be accepted from each Offeror. No alternative proposals will be accepted by the Government. Therefore, the

Offerors proposal shall contain the Offeror’s best terms from a price and technical standpoint. 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.

The Government contemplates award to one (1) Offeror a single prime contract containing a Cost Plus Incentive Fee

(CPIF) CLIN and associated data CLIN for the Preliminary Design of the AOEW AMP to the Offeror with the requisite facilities and capabilities to design, fabricate, construct, and deliver an AOEW AMP system. Items 0101-

0103, 0201-0207, and 0301-0311 will be Option Items.

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.

The Government reserves the right to conduct discussions if the Procuring Contracting Officer determines them 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. Each Offeror is required to complete Attachment J- 20, Contractor Award Information, in its entirety and provide it along with the proposal submission. Attachment J-20 will not count against the proposal page count limitations.

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 Attachment J-1 and solicitation requirements. In addition, the proposal must demonstrate that the Offeror:

Understands the goals of the AOEW AMP program, Understands the AOEW AMP engineering and capability requirements, and

Understands and have the capability to execute all portions of the SOW Attachment J-1.

Prime contractors shall require their major subcontractors (with contract value of $12.5 million or greater for the base CLINs and all options) to submit their cost/price proposal information (Volume VI) directly to the Procuring

Contracting Officer. Proposal content, packaging, and delivery requirements shall be flowed down from the Prime to the sub-contractors and the sub-contractor shall identify the prime contractor he is associated with on the cover of the cost/price proposal volume. Additionally, the sub-contractor shall identify a point of contact, address, and telephone number for each physical location where the work will be performed.

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

4 Unclassified softcopies

8 Unclassified hardcopies

IIA

Technical Approach (Classified):

• Tab D: System Performance Approach and Analysis**

• Tab E: System Description**

4 Classified softcopies

8 Classified hardcopies

IIB

Technical Approach (Unclassified):

• Tab F: Technical Plans, Schedule and

Structure

Unlimited 4 Unclassified softcopies

8 Unclassified hardcopies

III

Management Approach (Unclassified)

• Tab G: Engineering Management Plans and Processes

• Tab H: Program Management Process

• Tab I: Key Personnel Qualification

Summary**

4 Unclassified softcopies

8 Unclassified hardcopies

IV

Data Rights (Unclassified)**

• Tab J: Data Rights

4 Unclassified softcopies

8 Unclassified hardcopies

V

Past Performance (Unclassified)

• Tab K: Recent and Relevant Experience

• Tab L: Past Performance

Questionnaires**

4 Unclassified softcopies

8 Unclassified hardcopies

VI Cost/Price Proposal (Unclassified)** Unlimited 3 Unclassified softcopies

4 Unclassified hardcopies

** 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 (Volume VI ). UNDER NO

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

THROUGH V. In the event that cost and pricing data is included in Volumes I through V, 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, Organizational Conflict of Interest (OCI) information, 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

Technical Performance Measures (TPMs) (Volume IIA, Tab D.1)

Preliminary SRD (Volume II, Tab E)

Key Personnel Qualification Summaries (2 pages per summary limit) (Volume III, Tab I)

The 7017 List, 7028 List, and Commercial Restrictions List (Volume IV. Tab J)

Past Performance Questionnaires (Volume V, Tab L)

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 provided in Table L-3-1. 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 PCO 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 l l-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. Pages in unlimited volumes shall also be consecutively numbered, starting at page one. The Contracting Officer may 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 open electronic proposal submissions in accordance with FAR 15.207(c) will not be considered discussions. In the event of inconsistencies between the hardcopy and softcopy versions of a proposal, the hardcopy version shall take precedence. Page limits for soft copy 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 2007. All view graphs shall be in Microsoft PowerPoint. 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 2007; cost and pricing data shall be submitted using Microsoft Excel 2007

(with the exception of the actual basis of estimates (BOEs), in which case, the Offeror may choose between Word and Excel); Integrated Master Schedule data shall be submitted using Microsoft Project 2007. Offerors 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/price 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).

There is no limit to the number of discs that may be submitted as long as the page copy limitations of each proposal volume are met for each copy. NOTE: Volume VI, labeled “Cost/Price Proposal,” must be submitted on a separate disc(s) 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 2007 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 the following Cross Reference Matrices:

1. Show the traceability of Government solicitation requirements to the Offeror’s proposal.

2. Show the relationship between the Offeror’s proposal and the AOEW AMP SSD Attachment J-2 and SOW

Attachment J-1. The matrix shall be structured for the proposed system solution and not restricted by the structure of the Government’s SSD Attachment J-2. Include cross-reference to verification methods.

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

If Offerors have a conflict between the SSD Attachment J-2 (Word, Excel, or DOORS versions) then the SSD

Attachment J-2 Excel version takes precedence.

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 (for example:

volume number, copy number, and volume name) of each box, by box number. These packing instructions also apply to all subcontractor submissions.

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

NICHOLAS DeSELLE

SEA 02535

TEL: (202) 781-0717

Email: nicholas.deselle@navy.mil

Contract Specialist

NICOLE GEROW

SEA 02531G

mailto:nicholas.deselle@navy.mil

TEL: (202) 781-1088

Email: nicole.gerow@navy.mil

USE OF NAVY SUPPORT CONTRACTORS

The Government plans to use selected support contractor personnel to assist in providing Subject Matter technical expertise and Automated Information System (AIS) support regarding submitted proposals. These support contractors will be bound by appropriate nondisclosure agreements (NDA) to protect proprietary and source-selection information.

Government Support Contractors may assist the Source Selection Organization. The Source Selection Advisory

Council (SSAC), Source Selection Evaluation Board (SSEB), and Cost Team will be composed of Government employees only. The Government Support Contractors may participate as Advisors (Subject Matter Experts) to the

SSEB and the Cost Team.

The Offeror may wish to enter into non-disclosure agreements with the Government Support Contractors. If the

Offeror does so, it must provide copies of any such agreements to the Government. A list of the Contractor organizations that may participate is as follows:

o Envisioneering, Inc.

o Technomics, Inc.

o Massachusetts Institute of Technology/Lincoln Laboratories (MIT/LL) o Johns Hopkins University – Applied Physics Laboratory (APL) o Phased Array Technologies o David P. Mauder Consulting o Solutions Development Corporation

For contact information for the companies listed above, contact:

NICHOLAS DeSELLE

SEA 02535

TEL: (202) 781-0717

Email: nicholas.deselle@navy.mil

Any objections to the specified use of any of the firms listed above shall be submitted to the PCO within 10 calendar days of the issuance of the RFP. Failure to submit an objection within 10 calendar days of the issuance of the RFP acts as the Offeror’s consent to the specified use of each of the firms listed above.

Written Questions

Offerors may submit written questions requesting clarification of RFP requirements using Attachment J-18, Questions

Submittal Form in Excel format with the subject line: “AOEW AMP RFP Bidder Question” to the following two e-mail addresses: nicholas.deselle@navy.mil and nicole.gerow@navy.mil. Potential Offerors may submit multiple Bidders

Questions per Bidder Question Submittal Form by adding a row for each question. Communications regarding this solicitation or the work under it with any Navy 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 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, mailto:nicole.gerow@navy.mil mailto:nicholas.deselle@navy.mil mailto:nicholas.deselle@navy.mil mailto:nicole.gerow@navy.mil it shall inform the submitter and not provide any further response. Only written questions will receive a response.

Company-specific information will be omitted from all questions.

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 Nicholas DeSelle. Potential

Offerors shall mark each package as follows:

Marked: Bidders Question N00024-14-R-5353

Naval Sea Systems Command

1333 Isaac Hull Ave SE

Washington Navy Yard, DC 20376

Attn: Nicholas DeSelle SEA02535 Procuring Contracting Officer C/O Amy Arabucki PEO IWS 2D

DO NOT OPEN IN MAIL ROOM CONTACT: Amy Arabucki, 202-781-3256

In the event that potential Offerors prefer to hand carry classified questions follow the special instructions below.

All security related requests pertaining to this contract shall be submitted in writing by the contractor's Facility

Security Officer (FSO) to the individual identified in block 16(a) of DD-254 Attachment J-3.

It is requested that all questions 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. The Navy 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.

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 and signed the certification in accordance with the RFP. It is the Government’s intention to mail classified questions and answers in two batches, once approximately ten (10) days and once approximately twenty five (25) days after issuance of the RFP.

SUBMISSION OF PROPOSAL: NAVSEA will not accept electronic submission of proposal. All copies of the proposal (Volumes I through VI) shall be submitted to the PCO or Contract Specialist at the address below by 11:00 a.m. local time for the Naval Sea Systems Command on the proposal due date.

Commander, Naval Sea Systems Command

Department of the Navy

ATTN: NICHOLAS DeSELLE, SEA 02535

1333 ISAAC HULL AVENUE SE, MS2040, Bldg. 197, Room 5W-5162

WASHINGTON NAVY YARD, DC 20376

Hand carried offers shall be delivered by carrier to: (See below for special instructions)

(a) It is recommended that proposals be mailed in accordance with RFP instructions. In the event you prefer to hand carry your proposal, ensure adequate time has been allowed by your representative. 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 “Instructions to Offeror – Competitive Acquisitions”.

(b) Offerors hand carrying proposals shall call the contracting officer or contract specialist at least 48 hours prior to arriving at delivery location to make arrangements. Packages should not be sealed as they are subject to inspection.

Classified material shall be prepared in accordance with current security requirements. The contracting officer or contract specialist may receive the proposal and provide the Offeror a receipt with the time and date of delivery.

(c) All Offerors shall mark each RFP package with the name of the contracting officer and the contract specialist, their codes and phone numbers. In the event you have not been provided with this information contact the person listed in block 5 of the SF 26 or block 7 of the SF 33.

Additionally, one softcopy and one hardcopy of the Prime contractors proposal shall by sent to its cognizant DCAA office.

DESTRUCTION OF RESTRICTED MATERIAL

By submitting a proposal, Offerors certify that they will destroy restricted information obtained in connection with this solicitation and submit a letter to the Government certifying to the destruction of said information as well as any and all copies, notes, or other materials produced using the classified or other restricted information provided in connection with solicitation N00024-14-R-5353 within 90 days from contract award if they are deemed an unsuccessful Offeror.

Proposal Requirements

PROPOSAL VOLUMES I THROUGH VI

Submission of Classified Volume

The Government anticipates the need for bidders to submit classified information as part of their proposal. Classified proposals must be appropriately marked and delivered in accordance with the National Industrial Security Program

Operating Manual (NISPOM). The NISPOM can be accessed at http://www.dtic.mil/whs/directives/corres/html/522022m.htm. Volumes I through VI, excluding Volume IIA, shall contain NO CLASSIFIED MATERIAL UNDER ANY CIRCUMSTANCE and shall be marked as unclassified. In the event classified information is found within the unclassified sections of the proposal, that section will be destroyed and not evaluated. The Offeror will be financially responsible for damages caused by incorrectly classifying or marking classified information that contaminate a Government network. Classified pages will count against the page limits and format restrictions previously defined. The Classified Volume shall be wrapped separately from the unclassified portions of the proposal, but the entire proposal package may be submitted together in accordance with NISPOM guidelines. The Classified Volume wrapping shall be prominently marked on all sides as to the classification level of the material contained therein. The following procedures shall be followed:

Cross-referencing between the Classified Volume IIA and the Unclassified Volume IIB is encouraged.

The Classified Volume IIA shall not exceed the classification GENSER Secret.

The Classified Volume IIA shall be appropriately marked on the front, back, and spine as to the highest level of classified material contained therein.

Page, paragraph, table, graphic, and figure markings shall be in accordance with Chapter 4 of the NISPOM.

Strict adherence protocols to the AOEW Security Classification Guide (SCG) and the DD-254 Attachment

J-3 shall be in place to determine if any portion of the Offeror’s proposal is classified. In cases where the

DD-254 Attachment J-3 and SCG differ, the DD-254 Attachment J-3 takes precedence.

Classified information and the Classified Annex shall be handled, packed, and shipped or delivered in accordance with and shall conform to the instructions contained in the DD-254 Attachment J-3, the AOEW

Security Classification Guide (SCG) contained in OPNAVINST S5513.8B Enclosure 38.5, and the

National Industrial Security Program Operating Manual (NISPOM).

Part II: Proposal Content Requirements

VOLUME I: Introduction

Tab A: Cover Letter

The proposal shall be accompanied by a cover letter (letter of transmittal) prepared on the company’s letterhead stationery. The cover letter shall identify all enclosures being transmitted and shall be used only to transmit the proposal and shall include no other information. 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 and hard copy versions in a

Table of Contents.

Tab C: Executive Summary

The proposal shall include an overview and summary of the Offeror’s proposal in an executive summary. The executive summary shall be limited to five (5) pages and shall be unclassified. This shall not contain material that is not otherwise included within the proposal. No cost/price information shall be contained in the executive summary.

The executive summary shall also contain a statement that the Offeror’s proposal is valid for at least 180 calendar days after submittal of the proposal. Offerors should organize the Executive Summary according to the Offeror’s own judgment so as to best present its case to the Government in support of selection for contract award. The

Executive Summary shall demonstrate the Offeror’s understanding of the Navy’s requirements for the AOEW AMP and may summarize the Offeror’s proposed solution. The Executive Summary, in accordance with Section M of this solicitation, will not be evaluated.

VOLUME II: Technical Approach

The Offeror shall submit a Technical Proposal as outlined below that fully explains its proposed system, the analysis supporting the design of that system, and the Bases of Estimate that underlie the proposed development and manufacturing efforts. All assumptions that the Offeror makes in this Volume shall include a justification of why each assumption is reasonable and realistic. Assumptions about areas outside the Offeror’s responsibility under this contract shall be described and realistic.

Information presented within Volume II shall be presented as follows:

Tab D – System Performance Approach and Analysis (Classified)

Tab E – System Description (Classified)

Tab F – Technical Plans, Schedule and Structure

Although this information is divided across three tabs (discussed in full below), all of these sections must address a single, consistent proposed technical approach. For instance, the System Description (Tab E) shall be directly coupled to and describe an actual implementable design that is analyzed in Tab D and planned and scheduled in Tab

F; similarly, the System Description and the analyzed performance shall be traceable to the SSD and the estimates in the BOE. Any inconsistency between the proposed system, the analysis supporting that design, schedule, and structure, or the efforts or materials estimated in the BOEs may indicate a lack of understanding of the requirements and/or increased proposal risk. Offerors bear all risks of submitting proposal language that is ambiguous, vague, or lacks traceability between the various portions of the proposals.

The Technical Proposal must be sufficiently specific, detailed, and complete to demonstrate clearly and fully that the

Offeror understands the AOEW AMP objectives and has a thorough understanding of the SOW Attachment J-1 requirements for, and technologies involved with, accomplishing the AOEW AMP Preliminary Design and System

EMD through LRIP. The Technical Proposal must reflect the capability of the Offeror’s organization to perform the resulting contract. Technical Proposals must also address risks associated with the Offeror’s proposed approach.

Within the Technical Proposal, the Offeror shall provide information to address the Technical factors to be evaluated as described below. Classified information shall be submitted in a Volume IIA and may not exceed the total

Technical Proposal page count. The Technical Proposal shall consist of Volume IIA (Classified) and IIB

(Unclassified).

Tab D: System Performance Approach and Analysis (Classified)

This section shall demonstrate that the Offeror fully understands the specific and unique performance and support characteristics of the AOEW AMP payload. It shall also demonstrate that the Offeror has performed the necessary analysis of the trade space to optimize their proposed solution and that the Offeror’s solution provides a balanced and sustainable approach that minimizes life cycle costs and development schedule impacts while successfully achieving all identified system performance requirements.

The Government desires AMP payload to be designed in a manner that provides the lowest possible host platform integration complexity and cost. The MH-60R and MH-60S have been identified as the host platforms for Fleet introduction of the AOEW AMP capability.

The Offeror shall describe planned analysis efforts to support design and trade studies in preparation of mandatory design reviews. These planned analysis efforts shall be accurately reflected in the BOE.

A brief description of remaining analysis required to complete the effort after contract award shall be included and accurately reflected in the BOE.

The System Performance Approach shall consist of the following:

D.1: Analysis Demonstrating Electronic Attack Capability

D.2: Analysis Describing Host Platform to AMP Payload Integration

D.3: Analysis Describing AMP Payload to AN/SLQ-32 Integration and Communications Links

D.4: Open System Analysis and Certifications

D.5: Life Cycle Support Concept

D.6: Analysis Describing Technology Risk

System Performance Approach and Analysis - D.1: Analysis Demonstrating Electronic Attack Capability:

In this section, the Offeror shall provide specific end-to-end system performance analysis of how their proposed design provides capability to engage the threats in the scenarios described in of the AOEW AMP Design Reference

Mission (classified) Attachment J-4. At a minimum the analysis should include the ability to engage the targets in the threat scenario with the required waveforms, at sufficient Effective Radiated Power (ERP) and in the timeframe required. The Design Review Mission (DRM) will describe the required values for the above three parameters.

This section shall specify how the proposed technical solution meets system performance parameters as defined within the Government’s SSD, Attachment J-2 and Technical Performance Measures (TPMs). The System

Performance Approach shall be traced to the SSD Attachment J-2 requirements and shall provide a description of the Offeror’s technical approach to verify the performance stated in the SSD Attachment J-2. Performance estimates shall be for the as-delivered configuration (that is: as installed on the host platform). The Offeror shall emphasize the following Technical Performance Measures (TPMs) associated with the SSD Attachment J-2:

Effective Radiated Power

Waveform and Technique Generation

Response Time (Rapid Response, Pre-Emptive, Standard, and Mode Change)

Simultaneous and Time Coincident Engagements

Receive and Transmit Antenna Isolation

Instantaneous Bandwidth

Receiver Sensitivity

Field of Regard / Field of View (spatial coverage)

Receive and Transmit Beam Width

Side lobes

Duty Cycle

Pointing and Tracking Accuracy

Beam Switching/Pointing Time

Dynamic Range

Frequency Coverage

Integrated Electronic Attack (EA) Performance

Flying Qualities and Safe Separation Performance

Integrated Communications and Electronic Warfare (EW) Messaging

Mission Reliability (Rm)

The Offeror shall provide performance requirements derived from the SSD Attachment J-2 to meet the TPMs listed above. The Contractor shall use the TPMs listed above to develop a TPM Requirements List that shall include a cross-reference matrix showing the tracking of the Government’s requirements in the SSD Attachment J-2 to the

Offeror’s proposed requirements which will be the basis for the System Requirements Document (SRD) developed after contract award. The TPM Requirements List does not count as part of the page limitation of Volume IIA.

The Offeror shall summarize the trade studies and analyses accomplished to arrive at its proposed technical solution and how the Offeror’s technical solution provides the required performance in the context of the AOEW AMP

Design Reference Mission (classified) Attachment J-4. The Offeror shall provide a description of the Offeror’s design that is substantiated by demonstrated results for same or similar systems, subsystems, modules or components. If demonstrated results are not available, provide technical supporting data for proposed approaches, including references to published papers, component manufacturers stated specifications, or textbooks.

The Offeror shall discuss the use of simulation or emulations used to analyze their proposed performance and provide all relevant results.

NOTE: At the Government’s discretion, to help ensure downward traceability of the proposed technical solution to the final design, all or a portion of the Offeror developed TPM Requirements List (and System Description) may be incorporated into the contract as Attachment J-19. The Contractor shall include Attachment J-19 in the System

Requirements Document deliverable.

System Performance Approach and Analysis - D.2: Analysis Describing Host Platform to AMP Payload

Integration

The Offeror shall clearly present how its proposed system will integrate into the host platform. The Government will not consider any designs in which the AMP payload cannot be integrated onto the host platform for System

Integration and Test and Developmental Test (DT) and Operational Test (OT). In this section, the Offeror’s proposal shall, at a minimum:

Provide analysis to support the appropriateness of the proposed interfaces (defined by the Interface

Functional Description (IFD) and SSD, Attachment J-4), including, but not limited to, the impacts of the design on system timing, rapid response capability, and host platform aerodynamics.

Describe any required changes to the host platform and provide an analysis justifying any proposed changes to the host platform.

Describe the proposed system’s physical interface for power and cooling; hard point mounting features and design; and/or platform airworthiness impacts (e.g., center of gravity, stability, air/ground resonances); and any payload handling. The Offeror’s proposed approach shall also address platform integration and complexity on the host platform and how their design supports easy integration to other potential platforms.

Describe the analysis supporting the proposed system’s size, weight, and power and cooling (SWaPC) requirements (as described in the following Tab E), which must be within the not to exceed (NTE) SWaPC limits defined in the SSD Attachment J-2 and result in a system that meets all threshold operational and

TPM requirements. This must include a discussion of all the design tradeoffs, materials, designs, and components included in the proposed system.

Describe the proposed system’s Software and Electronic Interface requirements, including the types of information transferred from the payload to the vehicle and from the vehicle to the payload. This will include the projected timing of the transfers to enable proper operation of the payload, including pointing and flight profile change commands, and any special considerations that will be required in order to complete this integration.

Describe how communications between the AMP and the host platform are handled. This shall include a description of the level of integration required with the host platform in order for the AMP to be safely operated and accomplish its mission. Describe how the communications system can be upgraded or changed to a different datalink, such as Common Data Link (CDL) radio.

Describe how the proposed system meets the Government’s desire to easily integrate the AMP payload onto other platforms with minimal platform and payload modifications. The Offeror shall provide details of how the proposed system design achieves high overall system electrical efficiency while minimizing prime power consumptions and maintaining system performance requirements as defined by the SSD Attachment

J-2.

Describe the Offeror’s proposed approach to achieving Radio Frequency (RF) isolation between the transmit and receive antenna on the AMP payload as installed on the host platform. This discussion shall include a full description of the AMP payload design with respect to mounting location provided in the

SSD on the host platform and the necessary receiver-to-transmitter antenna isolation, considering that this isolation may be compromised by reflections from the host platform such as use of radar absorbent material

(RAM), side lobe suppression, platform configuration changes, and/or any other scheme, along with the necessary supporting analysis and/or experimental data. Offeror must describe its approach to achieve required RF isolation between the transmit and receive antenna on the AMP payload is critical for mission success.

System Performance Approach and Analysis - D.3: Analysis Describing AMP Payload to AN/SLQ-32

Integration and Communications Links

The Government desires the AMP payload effectiveness to be enhanced through coordination of on and off-board electronic attack (EA) through the installed AN/SLQ-32 EW System. At a minimum, the Offeror shall provide analysis to support the interfaces defined by the Government’s Interface Functional Description (IFD) Attachment J-

4 and SSD Attachment J-2. The Government requires use of the Link-16 system installed in the AMP and strongly desires use of existing interfaces (ship’s Combat Management System (CMS) Local Area Network (LAN), AN/SLQ-32, and host platform) and existing communication hardware but leaves the detailed tradespace considerations to be evaluated by the Offeror to meet the EA effectiveness requirements. Therefore, in this section, the Offeror’s proposal shall:

Describe the proposed communications network architecture and message content to support AMP command and control.

Discuss the approach that will be followed for integration of the AOEW AMP with the coordination provided by the AN/SLQ-32.

Describe the proposed communication system between the AMP and AN/SLQ-32 EW system/SKCS.

For the Link-16 system installed in the AMP, the Offeror shall discuss line-of-sight constraints and interference with the host platform. This discussion should address the technology readiness of the proposed approach; it should also address any proposed risk mitigation strategies, including the impacts to the ship, the ship’s CMS platform and the host platform.

Discuss the integration needs for initial and update loading of operational software and libraries prior to launch and for any planned on-board maintenance that involves software downloading to the payload.

System Performance Approach and Analysis - D.4: Open System Analysis and Certifications

This section shall describe how the Offeror’s proposed system provides a flexible and open system capability that is easily updated, can interface onto a range of host platforms, and can effectively interface with Aegis and SSDS

CMS to provide a robust coordinated on and off-board EA capability that can be easily modified by other developers to adapt the system to protect against future threats successfully. It will also describe how the system works with other military systems through conformance with necessary standards and address any potential obsolescence issues and their proposed solutions. Therefore, in this section, the Offeror’s proposal shall:

Describe the Offeror’s proposed approach to…