20R0123 Amendment 3.docx

DOCX document 40 KB Posted

Attached to
Aircraft Launcher Interface Computer (ALIC) Chassis and Associated Mechanical Assemblies.
Solicitation number
N6893620R0123
Issued by

View the file

Other files

File Type Posted
20R0123 Amendment 2.docx DOCX document
Drawings 20R0123.pdf PDF
20R0123 Solicitation Amendment.docx DOCX document
20R0123 Solicitation.docx DOCX document
20R0123 Attachments.zip ZIP file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

N6893620R0123

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

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 necessary to illustrate 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 shana.hwang@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. Drawing 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 P3, Attachment P6, Attachment P7), 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 shana.hwang@navy.mil no later than 11:00 A.M. PST on 24 Aug 2020 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 proposal due date is no later than 11:00 A.M PST on 08 September 2020.

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

Volume Number
Volume Title
Page Limit
1
TECHNICAL
50
2
PAST PERFORMANCE
15
3
PRICE
15
Annex 1
Relevant Portions of SOWs/PWSs & CPARs
N/A

Each volume shall contain the following information:

· Cover and title page

· Title of proposal and proposal number as applicable

· Offeror’s name, address, and POC

· RFP number

· Proposal volume number

· Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

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)

Section L – Proposal Instructions
Government SOW/PWS
Section M – Evaluation Factor
Offeror’s Proposal Reference
CLIN Reference
Volume 1 Technical
Example: Para 3.1

Note: This column shall address all paragraphs in Sections xx and xy of the SOW/PWS.

2.A
Provide reference to Offeror’s Proposal Volume I – Technical. Example: Refer to appropriate page number in Offeror’s written proposal

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

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

1.1 Technical Requirements:

1.1.1 The Offeror shall demonstrate a thorough understanding of the Statement of Work (SOW), including all drawings, and describe specific manufacturing methodology, specific techniques and steps that will be applied towards production and completion of all requirements and deliverables described in Section 2.0 and 3.0 of the SOW.

1.2 Quality Control & Quality Assurance:

1.2.1 The Offeror shall describe the planned approach to satisfy the Quality Control and Management requirements within the specifications and SOW.

1.3 Experience:

1.3.1 The Offeror shall provide a narrative that describes the Offeror’s experience with fabricating and producing mechanical assemblies similar in complexity to the ALIC Chassis and the associated mechanical assemblies to include addressing items below. (The Offeror may also utilize tables to supplement narrative as shown in the example below.)

1.3.1.1 Production of metalwork using Computer Numerical Control (CNC) milling and turning, sheet metal fabrication, welding, painting, dip brazing, chem-film coating and anodizing techniques.

1.3.1.2 Specifically describe previous units produced and when they were delivered to the Government. Provide examples of experience demonstrating the similarity of the effort in terms of fabrication and production technologies that will be utilized to fulfill the requirements of this contract as well as the Offeror’s ability to sustain production to ensure on-time delivery.

Example Table: Previous Experience with SOW Requirements and Similar Items

Systems
Similar/Identical
Description of Work Performed
Name & Phone # of Gov’t Contracting Officer
Contract No

1.4 Small Business (SB) Subcontracting Plan:

1.4.1 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: PAST PERFORMANCE

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

3.0 VOLUME 3: PRICE PROPOSAL

3.1 Volume Content:

3.1.1 This Volume shall contain the Contract Compliance information specified below as follows:

3.1.1.1 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 lists all sites where the work will be performed. If a JV teaming or subcontractor 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)

Place of Performance
CAGE CODE/DUNS #
Business Size
Brief Work Description and/or Program Responsibility
% of Total Proposed Price

3.1.1.2 Signed SF33 for basic solicitation and acknowledgement of each amendment, including completion of any RFP clause or provision that requires a fill-in or response.

3.1.1.3 Singed Representation, Certifications, and Acknowledgement and/or System for Award Management (SAM).

3.1.1.4 Guarantee the length of proposal validity (for at least 180 days after proposal submission).

3.1.2 This Volume shall also contain a copy of Section B with the Contract Line Item (CLIN) and Unit Prices and, for evaluation purposes, the Total Prices filled in using the quantities value in the solicitation and instruction below. Section B prices shall be provided separately in one digital data copy in MS Office 2016 Excel or Word format on email. Within all Excel spreadsheet, 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. Spreadsheet shall not be protected.

3.1.3 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 over letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

3.2 Ground Rules and Assumptions:

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

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

3.3 Price Information:

3.3.1 The Offeror shall identify the proposal price for each CLIN as specified in Section B of this solicitation. For CLINS 0002 and 0004 the Offeror shall propose a step-ladder pricing, if appropriate. The Offeror shall sum up the proposed Total Prices by CLIN, provide a total overall price of the proposal using provided quantities, and submit a complete Section B.

(End of Summary of Changes) image1.wmf

File details come from the government source that posted it. Updated .