18-R-5113_Amendment_2.docx

N0002418R5113

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been modified:

The following items are applicable to this amendment:

1) Attachment L-08 has been updated

2) As Posted:

a. Factor 3: Technical Approach

Technical Plans and Engineering Approach: The Government will evaluate the software development process it will use to complete each J-01-1 (SEWTT Technical Information Package (TIP) 03March 2017), J-01-3 (CIAT TIP 03March 2017) and J-01-4 (NULKA-Capability TIP 03March 2017). The Government will evaluate the Offeror’s description of how it will analyze the data contained in the TIP, and how its engineering approach meets the requirement to deliver a successful product. The Government will evaluate the extent to which the Offerors description of its plan to incorporate TIP into engineering, development, test and Configuration Management (CM) tool sets and processes will ensure that the requirements defined in the TIPs are met. The Government will evaluate products and technical reviews for alignment with ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013).

The Government will evaluate the Offeror’s Engineering Approach for Offeror perceived risks to development execution, risk mitigation steps to be taken, integration of the product into the host system, cyber security compliance and steps to a successful developer’s functional test that will support the Government certification process.

The Government will evaluate whether the Offeror’s description of its in house Systems Engineering Management Plan (SEMP) is in compliance with the requirements of Section J, ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013) and integrates with ATTACHMENT J-03 (Systems Engineering Plan 01 September 2015).

Key Personnel: The Government will evaluate the degree to which the resume demonstrates the experience, education, security clearance, and other skills that are necessary to successfully meet requirements of the SOW.

The qualifications listed in each individual proposed Key Personnel resume, not the specific individual, are the materially relevant aspects of the proposed Key Personnel partially forming the basis of award under 5252.237-9106, Substitution of Personnel (SEP 1990). Therefore, even if a proposed Key individual becomes unavailable to the offeror between proposal submission and award, the Government will evaluate and make its award decision based on the qualifications listed on the proposed resume(s). When the Government awards a contract under those circumstances, the Government will require the awardee to use the qualifications listed on the relevant proposed Key Personnel resume as the basis for replacing that individual under 5252.237-9106(b) during contract performance.

Employee Qualifications: The Government will evaluate the extent to which each proposed employee has the education, training, and experience to support the Offerors technical approach.

As Amended:

0. Factor 3: Technical Approach

Technical Plans and Engineering Approach: The Government will evaluate the software development process the Offeror will use to complete each J-01-1 (SEWTT Technical Information Package (TIP) 03March 2017), J-01-3 (CIAT TIP 03March 2017) and J-01-4 (NULKA-Capability TIP 03March 2017). The Government will evaluate the Offeror’s description of how it will analyze the data contained in the TIP, and how its engineering approach meets the requirement to deliver a successful product. The Government will evaluate the extent to which the Offerors description of its plan to incorporate TIP into engineering, development, test and Configuration Management (CM) tool sets and processes will ensure that the requirements defined in the TIPs are met. The Government will evaluate products and technical reviews for alignment with ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013).

The Government will evaluate the Offeror’s Engineering Approach for Offeror perceived risks to development execution, risk mitigation steps to be taken, integration of the product into the host system, cyber security compliance and steps to a successful developer’s functional test that will support the Government certification process.

The Government will evaluate whether the Offeror’s description of its in house Systems Engineering Management Plan (SEMP) is in compliance with the requirements of Section J, ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013) and integrates with ATTACHMENT J-03 (Systems Engineering Plan 01 September 2015).

Key Personnel: The Government will evaluate the degree to which the resume demonstrates the experience, education, security clearance, and other skills that are necessary to successfully meet requirements of the SOW.

The qualifications listed in each individual proposed Key Personnel resume, not the specific individual, are the materially relevant aspects of the proposed Key Personnel partially forming the basis of award under 5252.237-9106, Substitution of Personnel (SEP 1990). Therefore, even if a proposed Key individual becomes unavailable to the offeror between proposal submission and award, the Government will evaluate and make its award decision based on the qualifications listed on the proposed resume(s). When the Government awards a contract under those circumstances, the Government will require the awardee to use the qualifications listed on the relevant proposed Key Personnel resume as the basis for replacing that individual under 5252.237-9106(b) during contract performance.

Employee Qualifications: The Government will evaluate the extent to which each proposed employee has the education, training, and experience to support the Offerors technical approach.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

SECTION L

To receive a copy of the TIP and TDP identified in Section 1.1 please provide a Fed-Ex account, receiving address, Point-of-Contact and phone number via email to Daniel Magrino, Contract Specialist, NAVSEA 02, at Daniel.Magrino@navy.mil and Jim Simon, IWS 1IT PAPM, at james.simon@navy.mil.

In the email include your CAGE Code and DUNS number along with a completed copy of the DD254 that was included in the solicitation posted on FBO.

In the subject block of the email please identify as follows:

TIP and TDP Request Solicitation N00024-18-R-5113 A Fed-Ex priority overnight package, with signature required, will be sent within two (2) business days of receipt of your request. An email notification and tracking number will be provided via email.

Upon receipt please resend your requesting email to Daniel Magrino and Jim Simon confirming receipt of the package.

1. Section L 1.0 – General This acquisition is a 100% small business set-aside. Offers are solicited only from small business concerns. Offers received from concerns that are not small business concerns shall be considered nonresponsive and will be rejected. The applicable small business size standard for this solicitation is 1,000 employees and NAICS code for this solicitation is 334111.

The Offeror shall submit all information required by this solicitation. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award. 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). The solicitation will be made available only through the internet at https://www.fbo.gov. Offerors are hereby notified that from time to time, the Government may post additional information to the web site relating to this solicitation (e.g. responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the web site for any such information. The Proposal shall contain all the pertinent information in sufficient detail to permit evaluation. The proposal should be as detailed and complete as to clearly demonstrate that the Offeror has a thorough comprehension of all technical and other requirements.

1.1. The purpose of this procurement is to obtain engineering support services for the ongoing development of Electronic Warfare Training System (EWTS) projects and Production of EW trainers. The Navy’s goal is to maximize EWTS flexibility and commonality; interface with designated combat system training elements; leverage current technology; design out training unique systems; and utilize commercially available software and hardware which will conform to specified Technologies and Standards. The proposed technical approach must demonstrate how the design methodologies incorporate Open Systems Architecture (OSA) that allows for technology insertion of combat system driven technological and tactical improvements.

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

Procuring Contracting Officer Commander, Naval Sea Systems Command

PCO: Michelle A. Greene

1333 ISAAC HULL AVENUE SE Bldg. 197

WASHINGTON NAVY YARD DC 20376-2040

Telephone No. 202-781- 0974

Email Address: michelle.a.greene@navy.mil

Contract Specialist Commander, Naval Sea Systems Command ATTN: Daniel Magrino, SEA0251 1333 ISAAC HULL AVENUE SE, Bldg. 197

WASHINGTON NAVY YARD, DC 20376-2040

Telephone No. 202-781-3544 Email Address: Daniel. Magrino@navy.mil

Communications regarding this solicitation with any Government personnel other than the above point of contacts listed in Section L paragraph 1.1 are strictly prohibited and may result in the Offeror being determined ineligible for award.

1.3. The Government intends to evaluate proposals and award one contract. For proposal purposes, the estimated contract award date is first quarter 2019 calendar year. The Government reserves the right to award sooner or later if necessary and will adjust the period of performance as necessary.

1.4. “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 V: Cost/Price Proposal. Inclusion of pricing information within any other Volume may 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 Section L paragraph 2.6.

Note: should there be any discrepancy between the pricing submitted in Section B and the cost or price-related backup or summary documentation, the Offeror’s Section B pricing or supporting cost data as adjusted for cost realism, whichever is higher, will take precedence for evaluation purposes. Award will be made based on Section B pricing.

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

1.6. 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.7. Offerors are reminded that 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.8. 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 and Section L). 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.9. The solicitation will be announced through the Government-wide point of entry (GPE) at: https://www.fbo.gov/. Offerors are notified that from time to time the Government may post additional information via the GPE relating to this solicitation (e.g., responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the website for such information.

1.10. 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.11. All questions shall be submitted to the Contracting Officer and Contract Specialist in accordance with Section L paragraph 2.6.

1.12. Statements which merely paraphrase the solicitation in whole or in part and general statements such as “the Offeror understands,” “the Offeror can or will comply with the requirements”, “standard procedures will be used”, or “well-known techniques will be used” will not constitute compliance with the requirements for proposal content.

1.13. No classified material or information will be provided in conjunction with, or submitted in response to this solicitation.

1.14. Under no circumstances are Offerors to submit proposals that are not consistent with the solicitation. Offers which are found to deviate from the solicitation may be rejected as unacceptable.

1.15. Offerors must submit all volumes using the conformed solicitation as of the date of the last amendment prior to the proposal submission due date.

1.16. The following attachments are applicable to the preparation of the offer:

· Attachment L-01 – Cross Reference Matrix (CRM)

· Attachment L-02 – Addressing a new EW Capability

· Attachment L-03 – AOEW Capability Design & Implementation

· Attachment L-04 – Question Submittal Form

· Attachment L-05 – Pre-Award Accounting System Adequacy Checklist

· Attachment L-06 – Previous Contract Effort Narratives

· Attachment L-07 – Past Performance Questionnaire

· Attachment L-08 – Cost and Price Proposal Tables

· Attachment L-09 – Contractor Award Information

· Attachment L-10 – Facilities Checklist

· Attachment L-11 – Employee Qualification Form

2. Section L 2.0 – Instructions for Submission of Offers

The solicitation response shall be contained in five (5) separate volumes:

2.1. 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:

Factor 2 - Sample Problems

Factor 3 – Technical Approach

-Technical Plans and Engineering Approach

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.

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. Letter of Transmittal

ii. Tables of contents

iii. Glossaries of abbreviations and acronyms

iv. Resumes for key personnel

v. Letters of intent for key personnel

vi. Proposal Cross-Reference Tables

vii. Transmittal letters, teaming agreements, letters of intent, subcontract agreements, Organizational Conflict of Interest (OCI) information.

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

ix. Past Performance Questionnaires

x. Section K, Representations and Certifications

2.1.3. Only pages which count against page count limitations shall be numbered. The page count shall include all material with printed matter and figures except for those listed in paragraph 2.1.2 above. Pages excluded from page count limitations (i.e. items in paragraph 2.1.2, 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 “this page intentionally left blank”. Pages submitted which are not excluded from page count limitations (i.e. items in paragraph 2.1.2, above), and which exceed the page count limitations provided in Section 2.1—Table 1,will not be read or evaluated.

2.2. Section L 2.2 – General Submission Requirements

2.2.1. A Letter of Transmittal, which shall be submitted with Volume I, will be considered the “first page of the proposal” and shall include the following elements required by FAR 52.215-1(c)(2):

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 through V 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

iii. Offeror CAGE code and DUNS number

iv. Title of proposal, proposal number, and SOLICITATION number (N00024-18-R-5113)

v. 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, List of Tables and Figures. The Table of Contents should include the first through third level section titles. A separate List of Tables and Figures shall directly follow 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.

2.2.4. Proposals shall be 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.5. Proposals shall 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. The amount of detail to be presented in response to each section of the outline presented herein is left to the discretion of the Offeror, but information must be presented in the order specified and in sufficient detail for the Government to make a comprehensive evaluation of the Offeror’s understanding of and capability to meet the requirements of this solicitation. Each volume of the proposal shall be self-contained. Data shall be organized to enable Government personnel to thoroughly evaluate the proposal against specific factors established in Section M. 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. 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 (e.g., data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless physically incorporated into 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.

2.3. 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 Section 2.1, Table 1 above. Volumes I-V 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 within a binder shall also be separated by a side tab file divider.

2.3.2. The Offeror’s company name, proposal number, and solicitation number (N00024-18-R-5113) 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 shall include the date of revision and a revision number in the place of the date of submittal (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.4. Section L 2.4 – Electronic Submission

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

2.4.2. All electronic files submitted shall be Microsoft compatible, in their native format and not password protected.

2.4.3. Pricing information for the supplies and services solicited here shall only be included within the DVD containing Volume V: Cost and Price Proposal. Inclusion of pricing information on any other DVD beside Volume V 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.6 of this section.

2.4.4. Each submitted disc shall be labeled with the following:

i. “SOLICITATION N00024-18-R-5113”

ii. Date of submittal

iii. Volume number

iv. Offeror name, address, and point of contact

v. Offeror point of contact phone number and email address if available

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 such as hyperlinks or linked cells in workbooks not submitted (i.e., separate files).

2.5. 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 Standard Form 33.

NAVSEA will not accept emailed 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 ATTN: Daniel Magrino, SEA0251 1333 ISAAC HULL AVENUE SE, Bldg. 197

WASHINGTON NAVY YARD, DC 20376-2040

Telephone No. 202-781-3544 Email Address: Daniel. Magrino@navy.mil

SOLICITATION: N00024-18-R-5113

DO NOT OPEN IN THE MAILROOM;

CONTACT DAN MAGRINO, 202-781-3544

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

2.6. Section L 2.6 – Offeror Questions

2.6.1. If Offerors have any questions or takes exception to any specific technical requirement of the SOW, specifications or any other terms and conditions of the solicitation which, in the Offeror’s opinion, prevents it from responding fully to the solicitation, the Offeror shall notify the Government in writing using Attachment L-04 (Question Submittal Form). Offeror’s questions shall identify each specific area of concern.

2.6.2. Offerors shall submit written questions using Attachment L-04 (Question Submittal Form), with the subject line:

“N00024-18-R-5113 Offeror Question”

All questions shall be sent via email to Michelle.A.Greene@navy.mil and Daniel Magrino at Daniel. Magrino@navy.mil. Only questions transmitted electronically via email will receive a response.

2.6.3. If citing a document in a submitted question, the specific document name, document date, page, paragraph, clause and/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.6.4. All questions, comments, and data requests should be received within fifteen (15) calendar days after issuance of this solicitation 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. If the Government determines that a specific change is in fact required, then an amendment to the solicitation will be issued.

2.6.5. The Government will continue to accept questions up to the closing date and time of the solicitation; however, time may not permit responses to be issued prior to receipt of proposals. Questions received after 15 calendar days may not result in an extension to the proposal due date.

3. Section L 3.0 – Proposal Contents

The EWTS proposal shall be organized in accordance with the following instruction. FAILURE TO FOLLOW THESE INSTRUCTIONS MAY RESULT IN REJECTION OF THE PROPOSAL.

Proposals shall be organized into five separate volumes, (I) Executive Summary, (II) Technical Proposal, (III) Management Proposal, (IV) Past Performance, and (V) Cost and Price Proposal.

An outline is provided below.

· Volume I – Executive Summary

· Volume II – Technical Proposal

· Factor 1: Production

· Factor 2: Sample Problems

· Addressing New EW Capability

· AOEW Capability Design & Implementation

· Factor 3: Technical Approach

· Technical Plans and Engineering

· Key Personnel and Letters of Intent

· Employee Qualifications Form

· Volume III – Management Proposal

· Factor 4: Management Approach

· Process Management

· Volume IV – Past Performance

· Factor 5: Past Performance

· Previous Contract Effort Narratives

· Past Performance Questionnaires

· Volume V – Cost and Price Proposal

· Factor 6: Cost and Price

3.1. Technical Volumes (Volumes I through IV)

The Technical Volumes shall be limited to the page limits outlined in Section L.2.1 (and below). Cost and Price information shall not be included in any form in Volumes I through IV.

For the purposes of all technical and production responses, the Offeror shall assume maximum quantities as specified in Section B. The aforementioned instruction is for evaluation purpose only and does not obligate the Government to award/exercise at that maximum quantity.

3.1.1. Volume I – Executive Summary

The Executive Summary Volume title page shall, if the Offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR 52.215-1(e).

The Executive Summary Volume shall include an overview and summary of the Offeror’s proposal. The executive summary shall be limited to five (5) pages and shall be unclassified. The Executive Summary shall not contain material that is not otherwise included within the proposal. No cost or price information shall be contained in the executive summary. 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 summarize the Offeror’s understanding of the Government’s requirements for EWTS and summarize the Offeror’s proposed solution. The Executive Summary, in accordance with Section M of this solicitation, will not be evaluated. As an appendix to the Executive Summary Volume, the Offeror shall complete Attachment L-01 (Cross Reference Matrix (CRM)) for the Technical Volumes II-IV. 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.

3.1.2. Volume II – Technical Proposal

The Technical Proposal Volume title page shall, if the Offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR 52.215-1(e).

The Technical Proposal Volume includes Factor 1: Production, Factor 2: Sample Problems and Factor 3: Technical Approach and shall enable evaluators to make a thorough evaluation and arrive at a sound determination of whether the proposal meets the requirements of the solicitation. To this end, the Technical Proposal Volume shall be specific, detailed, and complete. 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, List of Tables and Figures: See paragraph 2.2.3(i), above, for a discussion of the content requirements for the Table of Contents, List of 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.

3.1.2.1. Factor 1: Production

The Offeror shall describe the proposed production, storage, and test facilities in sufficient detail as to demonstrate adequate infrastructure, capability, and capacity to meet the maximum annual production requirements provided in Section B CLINs 0008, 0005, 1005, 2005, 3005, 4005, and in accordance with ATTACHMENT J-04 (BEWT II Factory Acceptance Test Procedure 08 December 2016). The Government may, at its discretion, schedule Pre-Award Site Surveys of the Offerors facilities. If scheduled, the Site Survey will occur following the proposal submission date. Attachment L-10 (Facilities Checklist) will be used to verify Offeror’s facilities and whether or not the proposed facilities meet the requirements of the solicitation. The Offeror shall demonstrate the availability of facilities during the entirety of the contract period of performance to meet these requirements.

3.1.2.2. Factor 2: Sample Problems

The Offeror shall submit a response that fully explains its analysis of each of the provided Sample Problems, its proposed solution, and all additional response requirements defined in each individual Sample Problem.

The Offeror’s response to the sample problems shall demonstrate a practical application of the Offeror's technical approach to resolving discrete problems posed in the sample problems. The Offeror shall discuss the degree of risk associated with the methodology(ies) and analytical techniques the Offeror applies to fulfilling the stated requirements.

See Attachment L-02: Addressing a New EW Capability See Attachment L-03: AOEW Capability Design & Implementation

3.1.2.3. Factor 3: Technical Approach

1. Technical Plans and Engineering Approach: In this section, the Offeror shall demonstrate its understanding of each Technical Information Packages (TIP) in J-01-1 (SEWTT Technical Information Package (TIP) 03March 2017), J-01-3 (CIAT TIP 03March 2017) and J-01-4 (NULKA-Capability TIP 03March 2017) by outlining the engineering, software development, and test processes it will use to complete each. The Offeror shall describe how it will analyze the data contained in each TIP, and how the data would be incorporated into its engineering, development, test and Configuration Management (CM) tool sets. The Offeror shall outline the products, and technical reviews for each milestone review identified in ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013).

The Offeror’s Engineering Approach narrative shall include any Offeror perceived risks to development execution, any risk mitigation steps to be taken, integration of the product into the host system, cyber security compliance process, and steps to a successful developer’s functional test in support of Government certification process. If the Offerors analysis identifies any unique engineering efforts required on any of the TIPs provided J-01-1 (SEWTT Technical Information Package (TIP) 03March 2017), J-01-3 (CIAT TIP 03March 2017) and J-01-4 (NULKA-Capability TIP 03March 2017), please highlight and describe those efforts.

Systems Engineering Management: The Offeror shall describe key features of its in house Systems Engineering Management Plan (SEMP) and describe how it meets the requirements of Section J, ATTACHMENT J-02 (PEO IWS Technical Review Manual (TRM) – Tailored 13February 2013) and integrates with ATTACHMENT J-03 (Systems Engineering Plan 01 September 2015).

2. Key Personnel: The Offeror’s proposal shall provide a resume and letter of intent for each of the following Key Personnel: Program Manager, Senior Engineer, and Senior Software Engineer. Resumes and letters of intent shall be provided for Key Personnel only. Although Section M contemplates some Key Personnel becoming unavailable prior to contract award, Offerors shall only propose Key Personnel resumes for individuals that, at the time of proposal submission, the offeror has a good faith expectation of providing at award. Additionally, the Government considers the submission of Letters of Intent for proposed contingent Key Personnel to be material to the proposal since these Letters of Intent demonstrate the offeror's ability to hire personnel with the qualifications bid at the salary proposed.

The following minimum information shall be contained within the resumes:

1. Employee Name

2. Years of Professional Experience

3. Current position/title

4. Educational history/degrees held

5. Chronology of professional experience

6. Current level of security clearance. Note that all personnel on EWTS tasking will be required to maintain a clearance at the SECRET level

Resumes shall not exceed two (2) pages per person and must include the title of the position for which the Key Personnel are being proposed.

To demonstrate the availability, current or future, of trained personnel that meet the required qualification(s) identified for key personnel, Offerors shall provide letters of intent for any proposed Key Personnel. Any letters of intent must clearly indicate the proposed individual, current clearance level, and must be signed by the proposed individual. Letters of intent shall not exceed one (1) page each. Salary information shall not be included in the letter of Intent.

Minimum requirements and desired qualifications for each of the key personnel are as follows:

Program Manager Required: 10 years of experience with DoD acquisition processes and DoD/Navy program management as related to Field Site Operations, Industry or Government technical management, or Industry or Government business management. Project Management Professional (PMP) certification.

Desired: 8 years supervisory experience Desired: Bachelor degree (BS/BA) in an engineering field, or 10 years of experience gained from in-depth and specialized knowledge in engineering and program management fields.

Assistant Program Manager/Senior Engineer Required: Bachelor degree (BS/BA) in electronic or computer engineering field and 10 years of experience gained from in-depth and specialized knowledge in an Electronic Warfare related field. Project Management Professional (PMP) certification.

Senior Software Engineer Required: Bachelor degree (BS/BA) in electrical or computer engineering field and 10 years of experience gained from in-depth and specialized knowledge in an Electronic Warfare training projects. specifically Software coding proficiency in C#, C++, and Java, in a Linux environment.

Desired: SLQ32 related software development experience

3. Employee Qualifications: Using Attachment L-11 (Employee Qualification Form), the Offeror shall matrix proposed labor categories to the Government Labor Categories. In the format described by Attachment L-11 (Employee Qualification Form) Offerors shall provide the following information set:

a. Offeror’s proposed corresponding labor category

b. Individual’s Name

c. Employer (employee’s company name)

d. Years of related professional experience

e. Highest educational degree obtained

f. Degree area

g. Security Clearance level

h. Relevant certification and other notes

i. Citizenship

In the event the Offeror has not identified a firm candidate for a proposed labor category, include the word “pending” in lieu of an individual’s name. Offerors should attempt to minimize the number of proposed labor personnel for which candidates have not been identified. From an evaluation perspective, proposal risk in terms of “Technical Capability” and “Cost Realism” may increase if candidates have not been identified for proposed labor category positions. The labor categories for all proposed CLINs will be the same mix and amount of hours as detailed in Attachment L-08 (Cost and Price Proposal Tables). Data contained in Attachment L-11 (Employee Qualification Form) shall not conflict with data provided for the Key Personnel.

Offerors' proposals may not deviate from the total number of hours included in Section B. The Offeror shall propose their overall allocation of personnel labor hours to meet the recommended percentage allocations of senior, mid-level and junior personnel described in the table above. The Offeror's resulting labor mix allocation shall include all key personnel. Deviations are authorized for the percentage distribution of Senior Level, Mid-Level and Junior Level. However, Offerors are required to categorize proposed personnel using the years of experience specified in the Labor Mix Table above. In the event that the proposed labor mix or allocation of personnel resources differs from the Labor Mix Table in any category, the Offeror shall provide the rationale used in selecting the proposed labor mix or allocation.

3.1.3. Volume III – Management Proposal

The Management Proposal Volume title page shall, if the Offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR 52.215-1(e).

The Management Proposal Volume 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.

3.1.3.1. Factor 4: Management Approach

1. Introduction

The Offeror shall provide a brief summary of the key features of the Management Proposal. The management summary shall provide an overview of how the Offeror plans to manage the contract and how the Offeror plans to use existing corporate plans, policies, and procedures to execute the tasking described in this solicitation and meet the EWTS objectives.

2. Management Proposal Content

Process Management: This section shall describe the Offeror’s proposed process management approach in accordance with this solicitation. Simply stating that the Offeror will comply with the tasks described in the SOW will not demonstrate an understanding of the requirements.

Processes to include:

1. Risk Management: The Offeror shall describe its processes for identifying programmatic and technical risks and risk mitigation strategy.

2. Configuration/Change Management: The Offeror shall describe its’ in house configuration and change management approach. The Offeror shall provide details on how the configuration of multiple baseline builds will be managed and controlled to minimize design perturbations between builds.

3. Program’s security requirements and procedures: The Offeror shall describe how it will comply with requirements for facility clearance defined in Section J ATTACHMENT J-07 (Solicitation Draft DD254 12 October 2017).

4. DMSMS: The Offeror shall describe its processes for obsolescence monitoring and identification.

3.1.4. Volume IV – Past Performance Proposal

The Past Performance Proposal Volume title page shall, if the Offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR 52.215-1(e).

The Government will evaluate the Offeror’s past performance. If no relevant past performance information exists, do not submit a Volume IV. Instead, explain in the proposal transmittal letter that relevant past performance does not exist.

The Past Performance 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, List of 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.

3.1.4.1. Factor 5: Past Performance

1. Past Performance Proposal Content

1.1. Previous Contract Effort Narratives

Offerors shall provide information on at least three (3) and no more than five (5) of their own recent and relevant contract efforts with their proposal. Limited to three (3) pages each. The Offeror shall prepare a summary for each contract in the format identified in Attachment L-06 (Previous Contract Effort Narratives). The Offerors shall demonstrate in depth knowledge and successful performance of these recent and relevant contracts. The identified contracts can be with Federal, commercial, or other customers.

The Offeror, using Attachment L-06 (Previous Contract Effort Narratives), shall provide a discussion of recent and relevant past performance to demonstrate its ability to meet cost, schedule, and technical requirements. The discussion shall provide information on problems encountered during performance of the identified contracts and any corrective actions taken.

Offerors, using Attachment L-06 (Previous Contract Effort Narratives), shall discuss all pertinent details that show the Offeror’s past performance as a prime contractor or major subcontractor on programs of similar complexity predicts successful execution of the EWTS Contract. Qualified major subcontract work is defined as total subcontract price (inclusive of all options) that is greater than or equal to $13,500,000, or 10% of the Offeror’s total proposed price, whichever is lower (hereinafter “major subcontractors”).

The Offeror’s submission for each Attachment L-06 (Previous Contract Effort Narratives) shall include the following information in the following format:

a) Identify in specific detail for each previous contract listed, why or how the Offeror considers the effort relevant to the effort required by this solicitation in terms of technology, type of effort, (development, test, and production), contract scope, production schedule, and risk.

b) Provide a brief description of work performed and self-assessment of performance under each contract identified. The self-assessment shall address: 1) relevancy, 2) recency, 3) quality, 4) business relations, and 5) customer satisfaction as described below.

1) Relevancy. The Offeror shall discuss whether the its proposed past performance of tasks are similar to the current requirements in scope, size, and complexity.

2) Recency. The Offeror shall discuss whether the its proposed past performance contracts in the last five (5) calendar years.

3) Quality. The Offeror shall discuss the compliance with contract requirements (including delivery schedules), accuracy of data and technical performance.

4) Business Relations. The Offeror shall discuss its history of effective management, business-like correspondence, responsiveness to contract requirements, prompt notification of problems, reputation for reasonable and cooperative behavior, and effective…