DRFP Attachment 6 - Section L.pdf

FA9101-25-R-B001

Attachment 6

SECTION L

INSTRUCTIONS TO OFFERORS

4 October 2024

DRAFT

Facility Exhaust System

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

L-1.0 GENERAL INSTRUCTIONS TO OFFERORS

L-1.1 The proposal instructions in this section are designed to assist Offerors in preparing a complete response that reflects a full understanding of the approach proposed to accomplish all contractual requirements. Attachment 16, Section M details how proposals will be evaluated.

Offerors are expected to comply with all requirements of the Request for Proposal (RFP).

L-1.2 Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors to be eligible for award. By submission of its offer, the Offeror consents and agrees to all solicitation requirements and identified constraints. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation, or rejection of an Offeror’s proposal, rendering it ineligible for award.

L-1.3 The Procuring Contracting Officer (PCO), Haley Smith, is the sole point of contact for this acquisition. Address any questions or concerns to the PCO at haley.smith.10@us.af.mil copying Contract Specialist, Virginia Jones at virginia.jones.6@us.af.mil.

L-1.4 Organizational Conflict of Interest (OCI)

This acquisition may create actual or potential conflicts of interest for Offerors, teaming partners, and / or prospective subcontractors. In assessing and addressing conflicts of interest, the

Government will follow the guidance in the Federal Acquisition Regulation (FAR) Subpart 9.5.

Offerors are responsible for ensuring that both it and its proposed subcontractors are not restricted from participating in the Facility Exhaust System contract due to an OCI.

An Offeror’s failure to provide adequate information to avoid or mitigate an OCI may cause its proposal to be rejected and relieves the Government of any further responsibility to resolve OCI issues. See FAR 9.504(e). Notices to Offerors of OCI and their responses thereto are not negotiations or discussions as those terms are used in FAR 15.306(d).

The Offeror must submit a Mitigation Plan that addresses all potential conflicts in adequate detail for the PCO to determine whether an OCI exists or has been mitigated. The plan should reflect the results of the Advisory Multi-Step Process, updated with any relevant changes to the

Offeror’s and each team member’s or team member affiliate’s particular circumstances. If an

Offeror determines that an actual or potential OCI does not exist, it shall include a statement to that effect as part of its plan. The OCI Mitigation Plan shall specifically address the OCI disclosures required in this section and explain how the Offeror is in full compliance with the

Facility Exhaust System OCI provisions (see DAFFARS 5352.209-9001, Potential

DRAFT

mailto:haley.smith.10@us.af.mil mailto:virginia.jones.6@us.af.mil

Organizational Conflict of Interest (Jul 2023)). As part of its Mitigation Plan, the Offeror must identify which contracts or subcontracts it will continue to support and those it intends to terminate to allow to lapse to eliminate any conflicts. The plan shall also address other OCI resolution and mitigation measures to include the divestment of business units. The OCI

Mitigation Plan will be reviewed in conjunction with the PCO’s Responsibility Determination prior to award. The OCI Mitigation Plan shall be included in Volume I, Contract Documentation.

L-1.5 Cross-Teaming Restriction

The Government seeks to maximize competition among Offerors and ensure that it receives proposals that are free from any Offeror incentives or disincentives that may factor one proposal over another. To help safeguard the integrity of the procurement process, Offerors who submit proposals as prime contractors for this contract, or as a member of a joint venture (JV) prime contractor, may not also serve as a subcontractor to another Offeror submitting a proposal as a prime contractor for this contract.

L-1.6 Use of Non-Government Advisors

(a) Offerors are advised that technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors for review and analysis.

The non-government advisor support will be provided by:

CQ JV, LLC

and

Beyond New Horizons, LLC

(b) Offerors shall complete paragraph (b)(2) or provide written objection to disclosure as indicated in paragraph (b)(1) if the offeror objects to disclosure of a portion of the proposal, the consent in (b)(2) should be provided for the remainder of the proposal.

(1) Any objection to disclosure (Note: The Government is the final arbiter in the disposition of any disclosure objections):

(i) Shall be provided in writing to the contracting officer within 10 days of

RFP issuance; and

(ii) Shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the offeror objects to disclosure to non-government advisors.

(2) I understand technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors. I consent to release of any (unless objection is provided in (b)(1) above) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-government advisors for review and analysis; I have entered into (or will enter into) a non-disclosure agreement(s) with the non-government advisor(s), or with the company employing the non-government advisor(s); and, I will submit a copy of any such agreements to the Contracting Officer not later than the date established in this solicitation for receipt of proposals:

Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

Signature:

L-2.0 SOURCE SELECTION METHODOLOGY

L-2.1 Competitive, Best Value Source Selection

The Government intends to award one definitive contract with firm-fixed-price (FFP) Contract

Line Item Numbers (CLINs) and a 36-month delivery period.

L-2.1.1 Offerors Best Terms

The Government may award without discussions but reserves the right to enter into discussions.

Therefore, the Offeror’s initial proposal shall contain the Offeror’s best terms for Technical, Past

Performance, Price and Small Business Participation. If the Government contemplates award without discussions, the Offerors may be given the opportunity in accordance with (IAW) FAR

15.306 to clarify certain aspects of its proposal (e.g., the relevance of an Offeror’s past performance information (PPI) and adverse PPI to which the Offeror has not previously had an opportunity to respond) or to resolve minor or clerical errors.

L-2.1.2 Competitive Range

If discussions are to be conducted, the PCO will establish a competitive range (as set forth in

FAR 15.306(c)) based on the ratings of each proposal against all evaluation criteria which will be approved by the Source Selection Authority (SSA). If the PCO determines that an Offeror’s proposal should not be included in the competitive range, the proposal will be eliminated from consideration for award and written notice of the decision will be provided to the unsuccessful

Offeror IAW FAR 15.503.

If the PCO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO, with the approval of the SSA, may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

L-2.1.3 Final Proposal Revisions (FPRs) DRAFT

If discussions are deemed necessary with Offerors, upon completion of those discussions, the

PCO will request that the Offeror provide a FPR. Revisions to any volume(s) shall be submitted by providing two versions, one “clean” version, and one “track changes” version.

The Offeror is advised that any changes to the proposal in the FPR shall be fully addressed and / or explained and reflected in the proposed Price volume. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date and time for submission of the FPR.

When FPRs are requested, any revisions or non-compliance with the contract terms and conditions submitted in the FPR may not be subject to further discussions and may render the offer unacceptable for the Government. This provision is not intended to restrict the Offeror’s opportunity to revise its proposal. Rather, it is intended to preclude any misunderstandings by the Government that could result if new or revised terms and conditions submitted in the FPR have not been fully disclosed, discussed, and understood during discussions. Hence, such new or revised terms and conditions are not solicited and, if submitted in the FPR, may render the offer unacceptable to the Government.

L-2.1.4 Debriefings

The PCO will promptly notify Offerors of any decisions to exclude them from the competitive range whereupon, they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make a request IAW the requirements of FAR 15.505 or 15.506, as applicable.

L-2.1.5 Discrepancies

If an Offeror believes that the requirements in these instructions contains errors, omissions, ambiguities, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale (no later than five business days after release of this solicitation), as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error.

L-2.1.6 Evaluation Notices (ENs)

The Government may need to conduct written exchanges with Offerors which will be in the form of an EN. Page format and limitations will be placed on responses to ENs in the event they are issued. The specified page limits for EN responses will be identified in the letters forwarding the

ENs to the Offerors.

L-2.1.7 RFP Revisions / Amendments

The Government reserves the right to revise or amend any portion of this solicitation. Such revisions or amendments will be available on the System for Award Management (SAM) website as www.SAM.gov using Standard Form (SF) 30. If such amendments require material changes, the proposal due date may be extended at the discretion of the PCO and by enough days to enable an Offeror to revise its proposal. In such cases, the amendment will include an announcement of the new proposal due date and time. The Offeror shall provide acknowledgement in its proposal Volume I – Contract Documentation of all solicitation amendments issued by the Government.

L-2.1.8 Electronic Reference Documents

All referenced documents for this solicitation are available on www.SAM.gov. Potential

Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

L-2.1.9 Communications and Exchanges

Exchanges of source selection information between the Government and Offerors will be controlled by the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Controlled Unclassified Information and

Source Selection Information – See FAR 2.101 and 3.104” in the Subject line. Otherwise, source selection information will be transmitted via other means as appropriate. The Government may use the Department of Defense (DoD) Safe Access File Exchange (SAFE), https://safe.apps.mil/, to transmit / receive source selection information. NOTE: Proposal submissions shall follow the instructions provided in L-2.4.

L-2.2 PROPOSAL CONTENT

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors to be eligible for award. By submission of its offer, the Offeror consents and agrees to all solicitation requirements and identified constraints.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation, or rejections of an Offeror’s proposal, rendering it ineligible for award.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation by the Government and for substantiating the validity of stated claims. The proposal shall 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 that the Government has no prior knowledge of its facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

The Offeror’s proposal shall demonstrate that the Offeror possesses the technical expertise and past performance to perform all requirements of the Statement of Objectives (SOO) and the

Technical Requirements Document (TRD).

The Offeror’s proposal shall include all of the information requested and shall comply fully with these Section L instructions. Failure to do so may cause the Offeror’s proposal to be eliminated from consideration for award. Offerors are reminded to properly mark proposal documents which contain proprietary or restricted information.

NOTE: IF THE PROPOSAL IS NOT RECEIVED BY THE DUE DATE / TIME SPECIFIED,

THE OFFEROR’S PROPOSAL IS CONSIDERED LATE IAW FAR 52.215-1.

No pricing information should appear in Volume II, Technical Proposal. The Government advises Offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable and the Offeror ineligible for award.

The proposal acceptance period is specified in Block 8 of the solicitation. By signing in Block

30a of the SF1449, the Offeror acknowledges that the proposal is valid for a period of not less than 90 days from the proposal due date. The Offeror shall make a clear statement in its cover letter (see L-3.1.1.1) that the proposal is valid until the applicable date as referenced above and in the solicitation.

L-2.3 PROPOSAL ORGANIZATION

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the various technical approaches, as well as past performance and price, to be meaningfully evaluated without discussions. The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems.

Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

Each Offeror shall submit one electronic copy for each volume. Include a cover sheet, clearly marked with the volume, title, RFP identification, and the Offeror’s name. Apply all appropriate markings, including those prescribed IAW FAR 52.215-1(e). Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal

Information and Source Selection Information. Proposal submissions via email will not be accepted. IAW FAR Subpart 4.8, Government Contract Files, the Government will retain an electronic copy of all unsuccessful proposals.

The Offeror’s electronic copies shall be submitted in an un-compressed format readable and searchable by Microsoft (MS) Office 2016 (or later) applications (with the exception of PPI as described in L-3.3.3.2.) Use separate files to permit rapid location of all portions, exhibits, annexes, and attachments, if any.

L-2.3.1 Proposal Volumes

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table L-

2.3.1.1-1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table L-2.3.1.1-1. The Offeror’s proposal shall consist of five separate volumes: Volume I – Contract Documentation, Volume II

– Technical Proposal, Volume III – Past Performance Information, Volume IV – Price Proposal and Volume V – Small Business. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table L-2.3.1.1-1: Proposal Organization

Volume

ITO

Paragraph

Number

Volume Title

Maximum Number of

Pages

I L-3.1 Contract Documentation NA

II L-3.2 Technical Proposal (Including

CSOW)

III L-3.3 Past Performance Information See Note

IV L-3.4 Price Proposal NA

V L.3-5 Small Business NA

Note: For Volume III, Past Performance, each submitted performance reference shall not have the PPI Tool fields of “Contract Information” and “Program Details” together sum to a character count (excluding spaces) of greater than 27,000 characters.

L-2.3.2 Page Limitations

Page / character limitations shall be treated as maximums. If exceeded, the excess pages / characters will not be read or considered in the evaluation of the proposal and the Offeror will be notified. Each page shall be counted except the following: cover pages, tables of contents, table of figures, glossaries, Requirements Matrix, technical resources and Project Schedule.

L-2.3.3 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including displays as defined in paragraph (b) below. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point Times New Roman font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least

1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. In the event the Offeror creates an ambiguity, the Government may exercise its own discretion in counting pages. These page size and format restrictions shall also apply to responses to ENs.

(b) Legible tables, charts, drawings, graphs, diagrams, schematics, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, and plans. These displays shall be uncomplicated, legible, shall not exceed 11 x 17 inches in size, and may only be used for large tables, charts, drawings, graphs, diagrams, schematics, and figures, not for pages of text. For these displays, the text shall be no smaller than 10-point font.

L-2.3.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume or has not been properly cross-referenced will be assumed to have been omitted from the proposal. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Offerors must ensure that pricing information is only included in Volume IV. Do NOT include any price information in Volume II.

L-2.4 DISTRIBUTION

Offerors are responsible for submitting proposals, and any modifications or revisions, so as to reach the PCO by 2:00 pm Central Time on (TBD date 45 days after release of solicitation)

(see L-3.3.3.2 regarding early submission of the Past Performance Volume). The Government requires proposal submissions be conducted via the Procurement Integrated Enterprise

Environment (PIEE) Solicitation Module, https://piee.eb.mil. No other proposal submission method is authorized. Any proposal received after the specified time or by an unauthorized method is “late.” See paragraph L-2.2 and FAR 52.215-1. Only one proposal shall be submitted, per Offeror, in response to this requirement.

To initiate the proposal submission through PIEE, the Offeror must register as a proposal manager. Training on the solicitation module is available for proposal managers through PIEE.

In the Executive Summary, primes will provide a list of all major subcontractor team members.

For purposes of proposals only, a major subcontractor is defined as a subcontractor, other than the Offeror itself, that will perform 10 percent or more of the contract scope based on labor hours or total price. To be clear, the Offeror is solely responsible for ensuring its proposal is submitted in a complete and timely manner IAW paragraph L-2.2 and FAR 52.215-1. Pre-coordination is critical to submission of a complete and timely proposal.

Document file names shall follow this naming convention: “FA910125RB001 (Prime Contractor

Name) Volume # Title.”

Please provide any feedback on the use of PIEE to the PCO 14 days prior to proposal submission.

L-3.0 SPECIFIC INSTRUCTIONS

L-3.1 VOLUME I – CONTRACT DOCUMENTATION

L-3.1.1 Volume I Organization

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file(s).

L-3.1.1.1 Cover Letter

The cover letter shall include the business status / categories, Offeror primary and alternate points of contact with email / phone and who is authorized to contractually obligate the Offeror, Commercial and Government Entity (CAGE) Code, Unique Entity Identification (UEI), a statement that the Offeror understands the requirements specified and will meet the requirements therein, and a statement that the Offeror does or does not take exception to any of the requirements of this solicitation. The cover letter shall include an executive summary to summarize the Offeror’s business background and current customer base, emphasizing past success and significant projects.

L-3.1.1.2 Master Table of Contents

The Offeror shall include a master table of contents of the entire proposal within the Contract

Documentation Volume. This master table of contents shall contain a consolidation of the individual table of contents for all volumes.

L-3.1.1.3 Solicitation / Contract Standard Form (SF) 1449

Offerors are required to complete blocks 12, 17, 23, 24 and 30 of the SF1449. Ensure any amendments to the solicitation are acknowledged. An official having the authority to bind the

Offeror’s company contractually must sign and date the SF1449. By submission of its offer, the

Offeror agrees to all solicitation requirements, including terms and conditions, as written in the

RFP.

L-3.1.1.4.1 Section B – Supplies or Services and Costs / Prices

Offerors are not required to complete Section B. Prices from Volume IV will be transferred to

Section B upon award.

L-3.1.1.4.2 Sections G – I

The Offeror shall complete fill-ins as applicable.

L-3.1.1.4.3 Section K – Representations, Certifications, and other Statements of Offeror

Offeror shall complete and submit this section in its entirety in addition to completing the on-line

Representations and Certifications at the SAM website (https://www.SAM.gov).

L-3.1.1.4 Exceptions or Assumptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and / or specific part of the solicitation to which the exception is taken. The Offeror shall provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table L-3.1.1.4-1.

Table L-3.1.1.4-1: Solicitation Exceptions

Solicitation

Document

Page /

Paragraph

Requirement /

Portion Rationale

SOO, SF1449, etc. Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can / will not be met

L-3.1.2 Other Information Required

L-3.1.2.1 Small Business Subcontracting Plan

If an other than small business, the Offeror shall submit a Small Business Subcontracting Plan

IAW FAR 52.219-9, Small Business Subcontracting Plan, that also identifies the extent of the

Offeror’s commitment to the participation of small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business concerns, whether as JV members, teaming arrangement partners, or subcontractors. The Small Business Subcontracting Plan will be reviewed for compliance (not evaluated) and shall be made a part of the resultant contract.

L-3.1.2.2 Government Furnished Property (GFP) and Base Support Requirements

If the Offeror requires the use of Government furnished items, the Offeror shall provide a listing, including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, and reason for need. The Offeror shall also provide the written authorization from the cognizant ACO, as applicable. The Offeror shall supply this information in the format shown in Table L-3.1.2.2-1.

Table L-3.1.2.2-1: Example Required Information for Using GFP / Base Support

Quantity Federal

Stock No.

Nomen-clature

Duration of Need

Rental

Value

Reason for

Need

Cross Ref.

to Cost

Prop

2 EA FS156-09-

ACG-1372

Time

Counter

1 Oct 25 –

30 Sep 26

$1,000 Needed to calibrate 5

MHz/1pps

SATCOM

simulator offset

Volume IV, pages 23-

27, paragraphs

A-C

L-3.2 VOLUME II – TECHNICAL PROPOSAL

L-3.2.1 Volume II Organization

The Technical Proposal should be specific and complete. Legibility, clarity, and coherence are very important. Offerors’ responses will be evaluated against the Technical subfactors. Provide as specifically as possible the actual methodology the Offeror would use for accomplishing / satisfying the subfactors. Address the Offeror’s technical solution for meeting or exceeding the

Government’s minimum performance or capability requirements of each technical subfactor. All the requirements specified in the RFP are mandatory. By proposal submission, the Offeror is representing that its firm will perform all the requirements specified in the RFP. Do not merely reiterate the objectives or reformulate the requirements specified in the RFP. A Requirements

Matrix (Attachment L-8) is provided for the Offeror to indicate where individual SOO and TRD requirements are addressed in the Offeror’s Technical Proposal.

The Technical Volume shall be organized according to the following general outline:

Technical Factor:

Subfactor 1.1: Design and Analysis Capability and Technical Resources

Subfactor 1.2: Manufacturing Capability

Subfactor 1.3: Integration Capability

Subfactor 1.4: Integrated Master Schedule (IMS) and Schedule Risk

Management

Subfactor 1.5: Contractor Statement of Work

L-3.2.2 Subfactor 1.1: Design and Analysis Capability and Technical Resources

Discuss the Offeror’s approach to meet the Design and Analysis Capability requirements outlined in the Measures of Merit identified in Section M. DRAFT

L-3.2.2.1. Design Capability

L-3.2.2.1.1. Describe the Offeror’s methodology and design concept / technical approach that thoroughly demonstrates how the exhaust system will work together and any integration required with other systems. This narrative shall include at a minimum, a description of how the steam boiler system will operate, how the steam ejector system will operate, what utilities will be required and preliminary sizing of the system.

L-3.2.2.1.2. Provide a listing of the design tools and software that will be used for the exhaust system design.

L-3.2.2.2. Analysis Capability

L-3.2.2.2.1. Describe a methodology that thoroughly demonstrates how the Offeror will analyze the independent exhaust system, addressing steam system sizing, ejector system sizing, ejector system sizing, structural suitability, and system controls.

L-3.2.2.2.2. Provide a listing of the analysis tools and software that will be used for independent exhaust analysis.

L-3.2.2.3. Technical Resources

Provide a list of the types of technical personnel, individual years of experience, and certifications, if applicable, that will be utilized in the design and analysis of systems as described in the SOO.

L-3.2.3. Subfactor 1.2: Manufacturing Capability

Describe the Offeror’s or Offeror’s subcontractor capabilities for manufacturing the exhaust system components per requirements outlined in the Measures of Merit identified in Section M.

L-3.2.4. Subfactor 1.3: Integration Capability

L-3.2.4.1. Describe the Offeror’s capability for large scale system installation required for the system described in the SOO.

L-3.2.4.2. Describe the Offeror’s capability to integrate this system with existing utilities and other systems within the testing facility.

L-3.2.4.3. Describe the offeror’s capabilities for commissioning/checkout of a large-scale system as described in the SOO.

L-3.2.5. Subfactor 1.4: Integrated Master Schedule (IMS) and Schedule Risk

Management

Discuss the Offeror’s approach to meet the Scheduling requirements outlined in the Measures of

Merit identified in Section M.

L-3.2.5.1. Integrated Master Schedule (IMS)

Provide a Gantt chart in 11 x 17 inch format illustrating the logical sequence of work from the design through closeout including major activities, milestones, lead times, outages, start and completion dates, and predecessors and successors to depict the critical path. Both the first activity (Contract Award) and the last activity (FOC) shall be on the critical path. The

Government’s threshold date for FOC is 36 months after Contract Award.

The Offeror shall provide ground rules, assumptions, and logic used to develop the Project

Schedule. Any unusual aspects of their proposed approach to the Project Schedule shall be described.

Include detailed narrative of the origins of the durations, lead times, resource loading, rationale, and logic of the proposed schedule.

L-3.2.5.2. Schedule Risk Management

L-3.2.5.2.1. Provide the Offeror’s initial assessment of risk for the project.

L-3.2.5.2.2. Provide a risk management approach which includes, at a minimum, plans to identify, eliminate or reduce significant risk identified by the Offeror.

L-3.2.6 Subfactor 1.5: Contractor Statement of Work (CSOW)

A SOO is provided as Attachment 1 to the solicitation. This SOO along with the TRD represents the Government’s minimum objectives for the Facility Exhaust System project. Offerors shall use the SOO and TRD to propose a CSOW which expands upon these minimum objectives to the extent necessary to conduct this acquisition. The proposed CSOW shall define the tasks required for the Facility Exhaust System project ensuring all minimum requirements of the Government provided SOO and TRD have been addressed. The proposed CSOW shall consist of tasking statements. Each tasking statement shall reference the Contract Data Requirements List

(CDRL) items which will be delivered by that task, as applicable. Offers shall provide CDRLs relevant to the proposed CSOW which shall include at minimum: Design Drawings, Test Plans and Reports, Risk Assessment, Design Review Data Packages, Integrated Master Schedule, Project Management Plan, Site Preparation and Installation Status Reports.

L-3.2.7 Data Assertions

If the Offeror makes any assertions when completing Section K (DFARS 252.227-7017(d)), the

Offeror shall identify each assertion correlated to each individual item of intellectual property to be delivered, provided, or otherwise furnished to the Government during contract performance.

The Offeror shall do so by adding a parenthetical after its identification of each individual item of "Technical Data or Computer Software to be Furnished With Restrictions" in its completed

DFARS 252.227-7017 representation that identifies the specific part of the contract (e.g., CDRL number, SOW paragraph) that will require the awardee to deliver, provide, or otherwise furnish that intellectual property to the Government.

L-3.3 VOLUME III – PAST PERFORMANCE INFORMATION

L-3.3.1 Volume III Organization

The Past Performance Volume shall be organized according to the following general outline:

Table of Contents

Summary – Not to exceed two pages. (See L-3.3.2)

Past Performance References (See L-3.3.3.1)

PPI Submission (See L-3.3.3.2)

Relevant and Recency Determination (See L-3.3.3.4)

Organizational Structure Change History (See L-3.3.3.6)

Consent Letters – Consent letters executed by each joint venture partner, major subcontractor, and key management personnel authorizing release of adverse PPI to the offeror can respond to such information. A sample consent letter is provided as

Attachment L-5.

Client Authorization Letters – Client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the offeror’s performance. A sample consent letter is provided as

Attachment L-4.

List of Questionnaire Recipients (See L-3.3.3.2)

L-3.3.2 Summary

Describe the roles of Offerors and all subcontractors, teaming partners, or JV partners requiring

PPI IAW paragraph L-3.3.3.1.

L-3.3.3 PPI Sheets (See Attachment L-1, PPI Tool)

L-3.3.3.1 Number of PPI References

Offerors shall submit the following on contracts considered most relevant in demonstrating the ability to perform Facility Exhaust System: information required by the PPI Tool, List of

Submitted References, Relevancy Matrix, Consent Letters, Authorization Letters, and List of

Questionnaire Recipients. This information is required on Offerors, major subcontractors, or JV partners considered relevant to overall successful performance. Offerors may submit no more than five recent and relevant contracts for the prime contractor and no more than three for each major subcontractor. A reference is defined as a single contract. A single Task/Delivery Order from an Indefinite-Delivery Indefinite-Quantity (IDIQ) contract will be considered a single contract reference for evaluation purposes. If the prime is a JV, Offerors may submit no more than three references per JV partner. For purposes of proposals only, a major subcontractor is defined as a subcontractor, other than the Offeror itself, that will be responsible for 10% or more of the effort. Offerors are hereby notified that the Government will use data provided by each

Offeror in this volume and data obtained from other sources in the evaluation of past performance.

L-3.3.3.2 PPI Submission

Offerors must use the PPI tool (see Attachment L-1), which they shall request by email to haley.smith.10@us.af.mil for their electronic proposal submittal of relevant past performance contract information. Offerors shall provide the pages generated from this tool as part of their

Past Performance Volume. Offerors shall save the PPI database file as Offeror name-volume name (PPI)-ExhaustSystem.mdb (e.g., XYZ Company-Past Performance Volume (PPI)-

ExhaustSystem.mdb) to submit as part of the electronic copy of the Past Performance Volume.

Once complete, PPI sheets and past performance questionnaires (PPQs) will be treated as source selection information IAW FAR Part 3.104.

Offerors shall send PPQs on each identified contract to the points of contact for that contract. If the identified contract was a Government effort, please send to the Program Manager and PCO.

This questionnaire is contained at Attachment L-2, PPQ. Provide a list of questionnaire recipients to include points of contact (POCs) and phone numbers. Responses to questionnaires and the Past Performance volume are to be provided directly to the PCO not later than 2:00 p.m.

Central Time on (TBD date 30 days after release of solicitation).

PPI concerning subcontractor and teaming / JV partners cannot be disclosed to a private party without the subcontractor’s or teaming / JV partner’s consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor / teaming /

JV partner past performance assessments to the prime during exchanges. Therefore, the Offeror shall submit a consent letter executed by each teaming / JV partner and major subcontractor authorizing release of adverse PPI to the Offeror, so the Offeror can respond to such information.

For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the

Offeror's performance.

L-3.3.3.3 Relevant Contracts and Recency Determination

Offerors shall submit information in the PPI tool under the Program Details Tab on recent contracts deemed relevant in demonstrating the ability to perform the full range of capabilities

IAW the Facility Exhaust System SOO requirements and explain how / why the referenced contracts are relevant. The prime contractor may submit up to five recent contracts, and JV partners may submit up to three recent contracts per partner. Offerors shall clearly define the percentage of effort and type of work for which they were / are responsible. Also provide PPI on up to three recent contracts for each major subcontractor partner. To be recent, the effort must be ongoing for at least one year or must have been completed during the past five years from the date of issuance of the RFP. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see Attachment 16, Section M, paragraphs

M-2.3.1.1 and M-2.3.1.2.

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and what aspects of the proposed effort in which they relate. This shall include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the

Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems. Categorize the relevant information into the capabilities described in the SOO and the Technical subfactors used to evaluate the proposal. As noted above Table L-

2.3.1.1-1, these fields in the PPI Tool shall not exceed 27,000 characters. If the character limit is exceeded or if the information is not included in the identified fields, this information will not be considered.

L-3.3.3.4 Relevancy Matrix

The Offeror shall provide a completed relevancy matrix (Attachment L-6). Provide no more than five recent and relevant contracts for the prime contractor and no more than three for each major subcontractor. If the prime is a JV, provide no more than three references per JV partner. The relevancy matrix and other PPI will be used to establish the relevance of present and past efforts.

For submitted references (efforts cited), please place a check mark into the rows for which the reference is applicable according to the row headings (which represent the evaluation factors and subfactors).

L-3.3.3.5 Organizational Structure Change History

Many companies have acquired, have been acquired by, or otherwise merged with other companies or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant current or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include a "roadmap" describing all such changes in the organization of the Offeror’s company, JV partner(s), and / or proposed major subcontractors. As part of this explanation, show how these changes impact the relevance of any efforts identified for past performance evaluation / performance confidence assessment. Since the Government may consider present and PPI provided by other sources as well as that provided by the

Offeror(s), the Offeror’s "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

L-3.3.4 No Applicable PPI

If an Offeror has no recent or relevant PPI, it should so state that in this volume. However, the

Government reserves the right to determine whether any relevant PPI exists.

L-3.4 VOLUME IV – PRICE PROPOSAL

L-3.4.1 Volume IV Organization

The Price Volume shall be organized according to the following general outline:

L-3.4.2 Price Information

This section is to assist you in submitting data other than certified pricing data that is required to evaluate the completeness, reasonableness, and total evaluated price (TEP) of your proposed price. Note that unreasonably high proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Offers should be sufficiently detailed to demonstrate completeness and reasonableness. The burden of proof for credibility of proposed prices rests with the Offeror. Failure to comply with the RFP requirements for pricing information may result in an adverse assessment of an Offeror’s proposal, which may reduce or eliminate its chance for being selected for award. When an Offeror fails to completely and accurately provide all pricing information required by the RFP, the Offeror bears full responsibility for any adverse impact upon the evaluation of its proposal. For proposal purposes, the estimated start date is 1 March 2025.

Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support its price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

L-3.4.3 General Instructions

Table of Contents

Price Narrative

Attachment L-7, Pricing Sheet

L-3.4.3.1 The Price Proposal Volume is comprised of two parts: A price narrative that details the Offeror’s basis of estimate, proposed additive rates, assumptions, basis for the assumptions, and other details required to assist the Government in performing a detailed evaluation. The

Offeror shall provide an individual price (rounded to the whole dollar) for each Task and the post-award conference using Attachment L-7, Pricing Sheet. Offers shall be complete and reasonable.

L-3.4.3.2 The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-

1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit certified cost or pricing data.

L-3.4.4 Data

The cost of producing data will not be separately priced in Section B of the solicitation. The cost required to produce each CDRL should be included in the Offeror’s proposed price for each

CLIN.

L-3.5. VOLUME V – SMALL BUSINESS

L-3.5.1. Volume V Organization

The purpose of this volume is to provide information regarding the Offeror’s Small Business

Participation Commitment Document (Attachment L-9).

L-3.5.2. General Instructions

Subparagraph L-3.5.2.1 is applicable to all Offerors.

L-3.5.2.1. The Offeror shall submit a Small Business Participation Commitment Document

(SBPCD) describing its methodology to meet the Small Business Participation Commitment requirements as outlined in Section M-2.2.5.1; specifically describing how the Offeror will demonstrate a sound plan to meet the Minimum Quantitative Requirement of 20% of the total contract value for the participation of small businesses in performance of the contract, whether as a JV, teaming arrangement, or subcontractor. A template for this document is provided as

Attachment L-9.

Binding commitments in the SBPCD will become enforceable contractual requirements.

L-3.5.2.3. The SBPCD must be determined to be “Acceptable” by the PCO in order for the

Offeror to be eligible for contract award.

Attachments

L-1 PPI Tool

L-2 PPQ

L-3 PPQ Cover Letter

L-4 Client Authorization Letter

L-5 Subcontractor Consent Letter

L-6 Relevancy Matrix

L-7 Pricing Sheet

L-8 Requirements Matrix

L-9 Small Business Participation Commitment Document