Attachment 9 - Sec L - 30 Jul 2024.docx
DOCX document 25 KB Posted
- Attached to
- Cathodic Protection Beale AFB
- Solicitation number
- FA468624R0032
About this file
This document is the Section L - Proposal Requirements for a federal contract solicitation for a Cathodic Protection System project at Beale Air Force Base.
The key details are:
- The solicitation is for a Cathodic Protection System for 7 water wells at Beale AFB, with a total estimated value between $300K - $500K.
- Proposals must be submitted in 4 volumes: I) Completed SF 1442, II) Written Technical Proposal, III) Completed Bid Schedule, and IV) Completed Past Performance Questionnaire.
- The technical proposal must address 4 subfactors: 1) Statement of Work, 2) Design, 3) Schedule, and 4) Environmental Concerns.
- The solicitation includes a site visit on 8/13/2024, RFIs due 8/15/2024, and proposals due 8/21/2024.
- The contracting agency is the Department of the Air Force, Air Combat Command.
View the file
Other files
Show all 22
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
SECTION L – PROPOSAL REQUIREMENTS
I. Proposal Format
A. General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined to be unacceptable and therefore not considered eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the Cathodic Protection System as the Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in FAR 52.212-1, unless otherwise tailored in the Addendum to the solicitation. Proposals must be received by SSgt Milton Vasquez and Mr. Gabriel Fickel, no later than the date and time specified in Block 8 on the face page of the RFP.
B. Communications:
Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information only if the email can be sent encrypted and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information).
II. Volume Organization
A. General: Proposals shall be submitted to the Government in four (4) separate volumes as set forth below:
| Volume |
| Page Limits |
| Number of Copies |
| Description |
| I |
| N/A |
| 1 |
| Completed SF 1442 |
| II |
| 20 |
| 1 |
| Written Technical Proposal to include project Schedule |
| III |
| N/A |
| 1 |
| Completed Bid Schedule to Include Cost Breakdowns |
| IV |
| N/A |
| 1 |
| Completed Past Performance Questionnaire |
In addition to the page limitations set forth above, proposal volumes shall comply with the following format:
1. The sealed package used to submit the proposal package must show the time and date specified for receipt. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, III, IV, etc. Proposals shall be in the English language and all monies shall be proposed in United States dollars.
2. Print shall be no smaller than a font size of 12 and should be on 8 1/2 x 11 inch paper, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc. tailor the information requested. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., tailor the information requested shall not be greater than 11” x 17”. Each volume within the proposal shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings or color presentations are not desired or required.
3. The page limitation for Volume II, Written Technical Proposal, is 15 pages. The page limitation includes any cover page, charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror.
4. Page limitations may be placed on responses to Evaluation Notices (ENs), if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to offerors or on the EN form itself.
5. Each page containing proprietary information should be so marked.
6. Each page should contain the following legend at the bottom of each sheet:
SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104
FOR OFFICIAL USE ONLY
B. Volume I, Completed RFP
1. General: Complete blocks 14-20C of the RFP Section A, SF 1442 (SF 1442, SF 1449, etc.) In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K.
2. PART II - SOLICITATION FILL-IN SECTIONS B THRU K - Refer to Sections B through K of solicitation. Complete the necessary fill-ins and certifications in Sections B through K. Offerors shall ensure that all clauses and provisions that require "fill-in" information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the RFP.
C. Volume II, Written Technical Proposal
1. General: The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.
3. Format and Specific Content: The following information shall be provided in the written technical proposal and will be evaluated to assess technical acceptability in accordance with Section M-900, Evaluation Basis for Award. The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the Statement of Need (SON) Dated 27 Jun 24, and must adhere to the limitations outlined in the AF 813 dated 23 May 24
Subfactor One: Statement of Work (SOW): The contractor’s SOW clearly details how work will be accomplished and meets/addresses the Governments SON, dated 27 Jun 2024. The Contractor shall provide a site plan and layout with notes and details, to depict the general scope of work. This document will include the proposed locations and areas needed for the anode beds, rectifiers, test stations and connecting/bonding lines. These items are to be prepared in a manner that is consistent with the environmental and technical limitations outlined within this SON and supporting technical documentation provided in the solicitation package.
Subfactor Two: Design: The contractor’s proposal provides a level of effort design sufficient enough to address all major components of work, and with all information requested in the SON
Subfactor Three: Schedule: The contractor’s proposal provides a progress schedule (design/construction) with a reasonable period of performance. This will be submitted on an AF 3064 (see sec J). The project schedule that the Contractor submits must include, at minimum, the Contract award date, period of performance of the contract, and description of each task in a project schedule.
Subfactor Four: Environmental Concerns: The Contractor shall assemble their proposal while adhering to the environmental concerns outlined in the AF 813.
(Sample Tasks: Some source selection teams find it useful to use a sample scenario or task to aid in the evaluation of a Technical subfactor. In some cases a sample task or scenario may be particularly useful, such as where the problem-solving skills are themselves a critical discriminator (for example, contracts for engineering services or critical analysis). If appropriate, make the sample task the first known delivery order/task order. It is suggested that you limit sample tasks/scenarios to address only the most critical aspects of the program. Tasks/scenarios that are too broad or complex may overwhelm the offerors in terms of the time and cost of producing an acceptable solution and thus, not provide the insight that was intended to be provided. Also, keep in mind, your evaluation team will have to read and evaluate each proposed solution. Sample tasks/scenarios need to be designed with a specific purpose in mind. They should be focused on obtaining only the information needed to satisfy the intended purpose. They must not be based on known or contemplated requirements, unless the sample task will become the first order under the contract. (For instance, if your requirement is for scientific or engineering services to solve specific problems then do not ask the offerors to solve those problems in their proposals. This would be seen as attempting to get the offerors to solve your problems at their expense rather than contracting for their services.) Be certain to limit redundancy between the sample task/scenario and other Technical subfactors.
Note: If you include a sample task/scenario, you must discuss in Section M how it will be evaluated and contribute to the rating of the applicable Technical subfactor.)
D. Volume III, Price Proposal
1. General: The price proposal shall accurately breakdown the costs associated with each of the items associated with the Contractor’s Technical Proposal. This is to be completed utilizing the attached AF 3052.
D. Volume IV – Past Performance
1. General: The offeror shall submit Present and Past Performance Information for itself and any joint venture member in accordance with the format contained in Attachment 7 - Past Performance Questionnaire . A critical subcontractor is defined as an entity The evaluation of the offeror’s/joint venture member’s present/past performance WILL NOT include the present/past performance of any subcontractor(s), even though they may perform major or critical aspects of this requirement. The recency and relevancy of the information, the source of the information, context of the data and general trends in the contractor’s performance will be considered. For purposes of this evaluation, recency is defined as active or completed efforts performed within the past five (5) years from the issuance date of this solicitation
2. Past Performance Questionnaire: The Present/Past Performance Questionnaire (see RFP Attachment 7) will be one means used by the Government to obtain present/past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror shall send out and track the completion of the Present/Past Performance Questionnaires (See RFP Attachment 7) to each of the offeror’s joint venture member’s, if a joint/teaming arrangement is utilized. The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the offeror - i.e., it shall not be delegated to any other entity. Exert your best effort to ensure that at least two POCs per relevant contract submit a completed Present/Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. POCs will submit their completed Present/Past Performance Questionnaire electronically If sending electronically, follow the procedures outlined in paragraph I.B. Communications above, and email to: milton.vasquez@us.af.mil and gabriel.fickel@us.af.mil
Once the Present/Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered source selection sensitive and shall not be released to you, the offeror. Therefore, any exchange/contact between the offeror/joint venture member and/or critical subcontractor and its own POCs in regards to comments made on the questionnaire is not permitted.
3. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the offeror’s Present/Past Performance Volume. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and through other sources, other than those listed within the Present/Past Performance Volume Sheets.
4. RFP Attachment Legend: RFP Attachment 7 – Past Performance Questionnaire must include the following legend at the top and bottom of the page:
SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104
FOR OFFICIAL USE ONLY
File details come from the government source that posted it. Updated .