Amendment 1.docx

N6893621R0010

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

CONTENT OF PROPOSALS

L – [01] CONTENT OF PROPOSALS

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information cornering all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, experience, and capability as required by the solicitation. Proposals should clearly and convincingly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing, and competent to develop the resources necessary to meet all requirement; and has valid and practical solutions for all requirements and potential risk areas. Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the various work efforts, support, and management approaches, as well as Cost/Price, to be meaningfully evaluated without discussions. Unsubstantiated statements that the Offeror understands, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government.

The Offeror shall include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat the information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Failure to address a specific factor or subfactor clearly may result in an unacceptable rating. . Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may result in an unacceptable rating.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price (excluding the Offeror’s profit/fee), for the contract or provides one or more Key Personnel. “JV Team member” is defined as one of the entities that make up a joint venture (JV) formed for the purpose of responding to this solicitation.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at pam.hom@navy.mil. It is required that all questions be received within 10 calendar days of the date this solicitation is issued.

2.0 ELECTRONIC PROPOSAL FORMAT VIA DOD SAFE (https://safe.apps.mil/):

This section is intended to provide information to the Offerors on the electronic format and application software to be used for submitting proposals. Do not submit hardcopy proposals for this solicitation. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and upload proposals and will ensure the proposals received are suitable for reading electronically during evaluation.

Proposals must be formatted using a Times New Roman 12 pt Normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11-inch paper. All pages should be numbered with section and page numbers. Graphs and tables shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph. Graphs and Tables that fit on an 8.5” X 14” printed page will be counted as one page. Drawings may be of any size and will count as one page. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented. When using Government supplied templates (e.g. Attachment L-1, Attachment L-2), no modifications to font or scaling required.

The offeror shall submit all volumes of its proposal electronically via DoD Safe (https://safe.apps.mil/). All proposal documents must be compatible with the Microsoft Office 2016 and/or the latest Adobe Acrobat Reader Portable Document Format (PDF), where applicable. An email shall be submitted to pam.hom@navy.mil no later than 11:00AM PST on Monday, 19 July 2021 requesting a “Drop-Off Request Code.” The “Drop-Off Request Code” email must specify a point of contact name and email address for the Prime contractor and for each individual Subcontractor. The Prime and Subcontractor(s) will each be provided a unique “Drop-Off Request Code” which will allow them to submit proposal documents to the Government independently as needed. The Prime and Subcontractor points of contact will receive an email that contains their unique “Drop-Off Request Code” no less than 3 days prior to the proposal due date. This code authorizes access to submit proposal documents securely via DoD SAFE.

The Offeror is responsible for ensuring electronic proposals are virus free. Offerors may use hyperlinks within and among proposal volumes that do not include price information. However, there shall be no links from any other volume into the Price Volume or into any other portion of the proposal that contains price information. In order to reduce file sizes, the Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission. The Offeror is encouraged to simplify the color palette used in creating figures; and minimize size of graphics files; and avoid scanned images.

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its Volume/paragraph number matches the Proposal Instructions Volume/paragraph number provided in section “Part B Specific Instructions” to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, section, and element, etc., in the Offeror’s proposal.

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. The table below supersedes the copies requested in Block 9 of the Standard Form (SF) 33. All volumes of the original proposal shall be received electronically via DoD SAFE prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in the table below; title and table of contents pages do not count towards the page limit. Any pages submitted exceeding the page limit shall be disregarded and NOT evaluated.

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Page limitations for Annexes, if any, are specified below. The authorized Annexes are summarized in the table below.

Each volume shall contain the following information:

- Offerors can, if they so choose, provide an acronyms list. An acronyms list will not be included in the page count.

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volume and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Volume 1 Technical Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the SOW/PWS.

Volume 1 Technical

Volume 1 Technical

4.0 ELECTRONIC PROPOSAL SUBMISSION:

The Offeror shall submit all proposal documents electronically via DoD SAFE (https://safe.apps.mil/) in accordance with Section L, Part A, 2.0.

5.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

6.0 SOLICITATION CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to https://beta.sam.gov.

PART B SPECIFIC INSTRUCTIONS

Note: Pricing information shall only appear in the Price volume.

1.0 VOLUME 1: TECHNICAL

Note: The Technical volume shall not contain any reference to price aspects of the offer.

1.1 The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:

1.1.1 Understanding of the Work:

(1) The offeror shall demonstrate a thorough understanding of the Statement of Work (SOW), including all drawings, and describe specific methodology, techniques and steps, and processing time that will be applied towards production and completion of the requirements and deliverables described in the SOW.

(2) The offeror shall describe the plans and arrangements to complete First Article Testing.

(3) If the offeror is requesting a waiver of the First Article Testing requirement in accordance with FAR clause 52.209-4, the offeror shall submit documentation supporting the request in accordance with NAVAIR clause 5252.209-9502.

(4) The offeror shall provide a detailed schedule that covers from the start to the completion of the program with the delivery schedule clearly indicated, including all phases (pre-production, First Article, and production) and sublevel tasks within each phase the contractor proposes to do in the program.

1.1.2 Management Approach and Quality Assurance:

(1) The offeror shall describe the management approach for all technical and administrative requirements described in the SOW towards completion of required deliverables, including how the offeror intends to staff this contract to complete deliverables to specifications and on time (for example, how many positions and the experience level).

(2) The offeror shall provide a Risk Mitigation Plan identifying potential risks (for example, supply chain and scheduling), and provide a method or plan to mitigate these risks to avoid negative impact in the completion of required deliverables on schedule. If no potential risks are anticipated, a statement to this effect shall be included in the offeror’s risk mitigation plan.

(3) The offeror shall provide a Quality Management Plan describing the quality assurance measures that will be utilized during performance of this requirement. The offeror shall also provide certification as stated in the SOW.

1.1.3 Small Business (SB) Subcontracting Plan:

The Large Business Offeror shall provide its SB Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as Annex 1, unless there is an already approved comprehensive SB Plan. The Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award. See FAR 19.702(a) (1) Statutory Requirements, regarding failure of the apparent successful Offeror to negotiate and submit a Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract.

2.0 VOLUME 2: PAST PERFORMANCE

2.1 General

Sources of past performance evaluation information include information provided by the Offeror in response to the solicitation, information obtained from questionnaires, and any other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information Systems, Electronic Subcontract Reporting System, or other databases; the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, and Fee Determining Officials.

The Offeror shall complete the Past Performance Information Form, Attachment L-1, for each past performance reference performed within five years of the solicitation release date. The Offeror shall submit no more than five Past Performance Information Forms as the Prime Contractor, no more than two forms for each principal subcontractor, and/or no more than two forms for each JV team member. The Offeror shall submit written consent from its principal subcontractor(s) and JV team member(s) that will allow the Government to coordinate any past performance issues directly with the Offeror. If the Offeror does not submit the written consent, the Government will address any past performance issues directly with the principal subcontractor or JV Team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractor and JV team member that does not provide the written consent, the Offeror shall provide the name, address, phone number, and email address with whom the Government may address any past performance issues.

The Offeror shall provide a narrative on each Past Performance Information form in the “Contract Effort Description” area that clearly describes how each contract reference has relevant work effort that matches the relevancy definitions specified in Section M of the solicitation.

The primary source of past performance information will be PPIRS. If a Contractor Performance Assessment Report (CPAR) exists for multiple years for the same contract/order, all periods of performance within the recency period specified above, for that contract/order, will be used for evaluation. In the event a CPAR does not exist for a past performance reference, the Offeror shall submit a Contractor Performance Assessment Questionnaire (CPAQ), Attachment L-2, to the Program Manager who is the Assessing Official. The Offeror shall include instructions for the Program Manager to send completed questionnaires within two weeks of its receipt via e-mail to Pam Hom, Contract Specialist, at pam.hom@navy.mil, thereby allowing the customer approximately two weeks to complete their response. All CPAQs shall be received by the Government no later than the date and time specified in Block 9 of the SF 33 of the RFP.

3.0 VOLUME 3: PRICE PROPOSAL

3.1 Volume Content

(a) This Volume shall contain the Contract Compliance information specified below as follows:

i. Offeror Summary Table: The Offeror shall complete the table below. The Offeror shall include all subcontractors and JV team members who will be involved with the performance of the contract and list all sites where the work will be performed. If a JV teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name (Indicate Prime, JV Team Member, or Sub)

(b) This Volume shall also contain a copy of Section B with the Contract Line Item (CLIN) and Sub-CLIN Unit Prices and, for evaluation purposes, the Total Prices filled in using the quantities value in the solicitation and the instructions below. Section B prices shall be provided separately in one digital data copy in MS Office 2010 Excel or Word format on CD-ROM media. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(c) All price and price supporting information shall be contained in Section B and the price proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

3.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

(b) The Offeror shall provide sufficient information to support its price as well as an explanation of all ground rules and assumptions that affect the price estimates.

3.3 Price Information:

The Offeror shall identify the proposed price for each CLIN as specified in Section B of this solicitation. The Offeror shall sum up the proposed Total Prices by CLIN, and provide a total overall price of the proposal using estimated quantities, and submit a complete Section B. For Fixed Priced CLINs, the Schedule B Total Price is equal to the proposed unit price multiplied by the Section B Estimated Quantity for that CLIN.

(End of Summary of Changes) image1.wmf