Attachment 2_Section L_Instructions Conditions and Notices to Offerors.pdf

Section L – Instructions, Conditions and Notices to Offerors (Addendum to FAR 52.215-1)

L1.0 GENERAL INFORMATION

L1.1 General.

L1.1.1 This section provides guidance for preparing proposals as well as instructions on the format and content of the proposal. The proposal must include all data and information requested and must be submitted in accordance with (IAW) these instructions; incomplete proposals may be considered nonresponsive and determined not eligible for award. Taking exception to or failing to meet any of the requirements specified in this solicitation may result in the proposal being found unacceptable. Do not merely reiterate the Performance Work Statement (PWS) or reformulate the requirements specified in the solicitation. In no case shall words such as “we will comply with the requirements of the contract,” or equivalent statements, be acceptable to meet the requirements of this Request for Proposal (RFP). 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 Short Range Radome Replacement (AN/FPS-124) Program as the Government will review only one proposal per Offeror. The Government will not provide reimbursement for any cost incurred during proposal submission. Proposals must be complete, self-sufficient, and respond directly to the requirements of the solicitation. Any commitments made in the proposal may become part of the resultant contract.

L.1.1.2 Offerors are advised that the Government may incorporate all beneficial aspects of the awardee’s proposal and all above threshold (minimum) attributes, performance levels, or capabilities into the awarded contract document.

L1.2 Proposal Format and Content.

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

L1.2.2 Proposals shall be submitted in Microsoft Word or searchable PDF format (MS Office 2016 compatible). The proposal when printed must fit on 8.5 x 11 size paper, in 12 point, Times New Roman, single line spacing, with one-inch margins. Tables, charts, graphs and figures shall be used when necessary to depict organizations, systems and layout, implementation schedules, plans, etc. and shall be restricted to the 8.5 X 11 size paper and shall be no smaller than 10 point, Times New Roman. At a minimum, each volume shall be submitted as a separate file.

L1.2.3 Titles and contents of the volumes shall be provided as defined in Table L.1. If page limits in Table L.1 are exceeded, the excess pages will not be read or considered in the evaluation of the proposal. The following will be exempt from page limitations for the RFP:

Requested attachments, Cover sheets; Table of Contents; Lists of Tables; Lists of Figures;

Glossaries; Acronym List; Compliance Matrix; Subcontractor Consent Letters; and Client Authorization Letters.

Table L.1

PARA. VOLUME TITLE COPIES PAGE LIMIT

L-2 Volume I – Factor 1, Cost/Price Proposal 1 No page limit

L2.2 Total Evaluated Price (TEP) No page limit

L2.3 Cost or Pricing Information Requirements No page limit

L2.3.4.2.

Pre-award Survey for Prospective Contractors No page limit

L-3 Volume II – Factor 2, Technical Proposal 1 Not to exceed 30 pages

L3.2 Subfactor 1: Radome Design and Materials Contractors discretion within L-3 page limit

L3.3 Subfactor 2: Manufacturing and Production Contractors discretion within L-3 page limit

L3.4 Subfactor 3: Installation, Teardown, and Removal Contractors discretion within L-3 page limit

L3.5 Subfactor 4: Testing and Quality Assurance Contractors discretion within L-3 page limit

L-4 Volume III – Factor 3, Small Business Participation Submission 1 No page limit

L4.1.2 Format and Specific Content No page limit

L-5 Volume IV - Factor 4, Administrative and Responsibility Material 1 No page limit

L5.1.2 Small Business Subcontracting Plan No page limit

L5.1.3 Contract Forms and Certifications No page limit

L5.1.4 Exception to Solicitation Requirements No page limit

L5.1.5 Contractor Team Arrangement No page limit

L5.1.6 Authorized Offeror Personnel No page limit

L5.1.7 Organizational Conflicts of Interest No page limit

L1.3 Electronic Proposal Submission.

L1.3.1 Offeror shall submit its proposal electronically in Procurement Integrated Enterprise Environment (PIEE) (https://piee.eb.mil/) via the Solicitation Module. For instruction on posting an offer, please refer to the “Submitting an Offer” instruction within the Solicitation Module under the “Documentation” selection at the top:

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf. It is the Offeror’s responsibility to follow the registration instruction found on the PIEE website. It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned prior to the solicitation closing date. Subcontractors or teaming partners are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime Offeror.

Documents submitted by the subcontractor or teaming partner directly to the Government must have the prime contractor’s name, CAGE, and RFP number on the first page of the document.

L1.3.2 Large File Notice: Follow PIEE instructions for uploading files larger than 10MB. If needed, break the file down into smaller sections in order to upload it to the system.

PROPOSALS SUBMITTED THROUGH OTHER MEANS NOT SPECIFIED WILL NOT BE

ACCEPTED. Clearly mark the description for each uploaded document by Offeror Name, Solicitation Number and Volume number. Proposals submitted electronically will be considered late unless all proposal documents are transmitted to and successfully uploaded to PIEE prior to the closing date and time for receipt of proposals (See L1.4). The Government is not responsible for technical difficulties associated with the transmission of any electronic files to the website.

The Offeror is responsible for ensuring the successful electronic delivery of its proposals.

Offerors are encouraged to submit proposals with sufficient time to ensure all proposal documents are successfully uploaded to the website prior to the closing date and time. It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications.

Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system. Please be advised timelines are determined by the date and time an Offeror’s proposal is received by the Government, not when an Offeror attempted transmission.

L1.3.3 In the event of a PIEE System outage within 24 hours of the proposal due date that prevents the Offeror from submitting a timely proposal, the Contractor shall immediately notify the Procuring Contracting Officer (PCO). This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain https://piee.eb.mil/ https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf written approval from the PCO to submit the proposal via an alternate method. The only alternative methods the Government will consider is either using email or a submission by mail, using separate CD-Rs to segregate proposal volumes. Offerors will be notified which method will be allowed in the event of a PIEE system outage. If this is required, the Government will provide a minimal extension window (no more than 2-3 business days) and a mailing address for delivery. In the event the Offeror does not provide notification to the PCO until after the closing date and time, the PCO will follow the procedures identified in the Federal Acquisition Regulation (FAR) 15.208.

L1.4 Proposal Due Date/Time:

22 September 2025 / 1:00 PM MST L1.4.1 Late proposals will only be considered IAW FAR 15.208 L1.5 Proposal Validity.

All proposals submitted in response to this solicitation shall be binding on the Offeror for a minimum of 365 days. The Offeror shall make a clear statement in Section A of the proposal documentation volume the proposal is valid for a minimum of 365 days from solicitation closing.

L1.6 Discrepancies.

If an Offeror believes the requirements in these instructions contain an error or omission, the Offeror shall immediately notify the PCO and Contracting Specialist (CS) in writing with supporting rationale.

L1.7 Government Contract Files.

IAW FAR Subpart 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L1.8 Oral Presentations.

Oral presentations will not be allowed.

L1.9 Point of Contact.

Exchanges of source selection information between the Government and Offerors will be controlled by the PCO and the CS. Exchanges of source selection information after submission of the initial proposal packages between the Government and Offerors will be controlled by the PCO or CS. 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”, “Controlled Unclassified Information” in the subject line of the email. The PCO and the CS are the sole points of contact for this acquisition. Offeror shall address any questions or concerns they may have to the PCO or CS.

Procuring Contracting Officer (PCO) Contracting Specialist (CS)

AFLCMC/HBDK AFLCMC/HBDK

Attn: Chris Jarman Attn: Cameron Tucker 6039 Wardleigh Rd 6039 Wardleigh Rd Hill AFB, UT 84056 Hill AFB, UT 84056 christopher.jarman@us.af.mil cameron.tucker.6@us.af.mil

L1.10 Amendments to Solicitation.

If this RFP is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, Offerors shall acknowledge each amendment by signing and returning the front page of each amendment with the proposal submission. If the RFP is amended after proposal submission, Offerors shall respond by the date and time specified in the amendment to include a signed front page of the amended RFP. Offerors who fail to acknowledge RFP amendment(s) may be considered non-responsive and may be eliminated.

L1.11 Proposal Withdrawal.

Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an Offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

L1.12 Title Page.

The title page of each volume must show:

1) Solicitation Number

2) Company name, Address, Commercial and Government Entity (CAGE) Code and Unique Entity Identification (UEID) Number.

3) Primary point of contact name, telephone number and email address

4) Volume number and name (e.g., Volume I, Price)

L1.13 Cross-Reference Matrix.

Each volume shall be written on a stand-alone basis so 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 will be assumed to have been omitted from the proposal. The Offeror shall fill out the Cross-Reference Matrix in the RFP attachments indicating where in its proposal the information can be found as it relates to the RFP. The Cross-Reference Matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements document Performance Work Statement (PWS), Section L (Instructions, Conditions, and notices to Offerors), and Section M (Evaluation Factors for Award). The Cross-Reference Matrix will help an Offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Additionally, to the extent the matrix discloses details as to how the Government intends to evaluate the Offeror’s proposals for award, Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

L1.14 Indexing.

L1.14.1 Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

mailto:christopher.jarman@us.af.mil mailto:cameron.tucker.6@us.af.mil

L1.14.2 Include an indexed list of tables and figures. Tables and figures do not count against the page limitations for their respective volumes.

L1.14.3 Glossary of Abbreviations and Acronyms – Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L1.15 Debriefings:

L1.15.1 Pre-Award Debriefings L1.15.1.1 The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with

FAR 15.505.

L1.15.2 Post Award Debriefings L1.15.2.1 The PCO will notify unsuccessful Offerors included in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing.

L1.15.2.2 Successful Offerors will be notified of the source selection decision and may also request a debriefing.

L2.0 VOLUME I - Factor 1, Cost/Price Proposal L2.1 General Instructions:

In the Cost/Price Volume, the Offeror shall provide the following information in addition to the pricing in the Pricing Matrix Worksheet (Section J Attachment 5). These instructions are to assist Offerors in submitting information required to evaluate the reasonableness, balance and Total Evaluated Price (TEP) of the proposed pricing.

As defined in Section M of the RFP, which will be assessed from the information provided in this volume, the pricing criteria will be as follows:

1) Completeness

2) Reasonableness

3) Balance

4) Total Evaluated Price (TEP)

5) Cost or Pricing Information Requirements

Offerors should review Section M criteria to ensure the minimum requirements are met.

L2.2 Total Evaluated Price (TEP):

L2.2.1 Offerors shall complete the Pricing Matrix Worksheet (Attachment 5) IAW with the instructions at the top of each of the worksheet’s tabs.

The TEP will be used for proposal evaluation purposes. The Government will calculate the TEP by multiplying the Offeror’s proposed prices (from the Pricing Matrix Worksheet) by the Government’s Best Estimated Quantities (BEQs) for CLINs:

• 0004-6004 (Site Survey and Installation Plan Report)

• 0005-6005 (Radome Procurement)

• 0006-6006 (Radome Installation)

• 0007, 5007 (Training)

• 0008, 5008 (Over and Above)

The products of each CLIN will be summed to arrive at the TEP. While the BEQs are used for evaluation, they are not binding and do not represent the actual quantities the Government will order.

The awarded contract will be based on the Offeror’s proposed prices as submitted in the Pricing Matrix Worksheet. These prices will be binding for the duration of the contract.

The cost/price of future Task/Delivery Orders will be determined by multiplying the awarded unit prices (from the Pricing matrix Worksheet) by the actual quantities the Government orders at the time of Task/Delivery issuance. Therefore, it is crucial the Offerors provide accurate and realistic pricing.

Data, CLIN 0001, is Not Separately Priced (NSP).

L2.2.2 Submit a copy of the completed Pricing Matrix Worksheet in Volume I – Factor 1, Price in an editable format of Microsoft Excel (non-PDF format).

L2.3 Cost or Pricing Information Requirements:

L2.3.1 IAW FAR 15.402, 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness. If after receipt of proposals, the CO determines there is insufficient information available to determine the reasonableness of the proposed pricing the Offeror may be required to submit additional information other than certified cost or pricing data. If, during the source selection process, the PCO determines adequate competition no longer exists and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submitted additional cost and pricing data in accordance with FAR clause 52.215-20.

L2.3.2 Rounding:

L2.3.2.1 All dollar amounts provided shall not extend beyond two decimal places.

L2.3.3 Pricing Assumptions:

L2.3.3.1 Summarize all significant pricing assumptions, scope limitations and/or qualifications of the Volume I – Factor 1, Cost/Price Proposal.

L2.3.4 Estimating Techniques and Methods:

L2.3.4.1 Offerors shall use generally accepted estimating techniques to develop their estimates for the proposed rates.

L2.3.4.2. Accounting System L2.3.4.2.1. The Offeror shall indicate whether it has Government approval of its accounting system and if so, provide evidence of such approval.

L2.3.4.2.2. The Offeror shall also identify any deviations from its standard procedures in preparing this proposal.

L2.3.4.2.3. If the Offeror does not have a Government accepted accounting system, complete and submit the Pre-award Survey for Prospective Contractors, Attachment 6 to the solicitation.

L2.3.4.2.4. The Offerors shall provide cognizant DCAA and DCMA office contact information.

L2.3.5. Contract Data Requirements Lists (CDRLs) L2.3.5.1 CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the Offeror’s proposed prices.

L3.0 VOLUME II – FACTOR 2, TECHNICAL PROPOSAL

L3.1 General Information:

L3.1.1 The Technical Volume shall be clear, specific, complete and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. The Offeror’s responses will be evaluated against the Technical Subfactors defined in Section M, Evaluation Factors for Award. Offerors shall review Section M criteria to ensure the minimum requirements are met. Provide as specifically as possible the actual methodology the Offeror would use for accomplishing/satisfying each subfactor. There will be no reference to rates or price in this volume. Offerors shall assume the Government has no prior knowledge of their experience or certifications and will base its evaluation on the information presented in the Offeror’s proposal.

All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, the Offeror is representing the company/firm will perform ALL the requirements specified in the solicitation (including PWS); it is not necessary or desirable to state this specifically in the proposal.

L3.1.2 The Offeror’s approach shall address all requirements IAW the paragraphs and sub-paragraphs of the PWS unless otherwise noted.

L3.1.3 Adequate Responses:

L3.1.3.1 It is imperative the Offeror fully describe and provide detail as to how the Offeror shall meet the subfactor requirements. Do not merely copy and paste, rephrase or restate the objectives, or reformulate the requirements specified in the solicitation. Evidence which clearly demonstrates and supports the Offeror’s claims is essential. The absence of such evidence may result in a deficient proposal.

L3.1.4 Volume Organization:

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

1) Table of Contents

2) List of Table and Figures

3) Glossary

4) Cross Reference Matrix

5) Subfactor 1 – Radome Design and Materials

6) Subfactor 2 – Manufacturing and Production

7) Subfactor 3 – Installation, Teardown and Removal

8) Subfactor 4 – Testing and Quality Assurance

L3.1.5 Radome Specification:

For matters related to technical requirements or mentions of “Air Force specification” or “radome specification”, Offerors shall refer to “Engineering Specification for the AN/FPS-124 Radar Radome” Document No.: 20250726 CAGE: 98747.

L3.2 Subfactor 1: Radome Design and Materials For Radome Design and Materials, the Offeror shall provide evidence of the following abilities:

• L3.2.1 Describe the radome design being proposed. Describe the level of adherence to the Air Force specification that has already been demonstrated or validated. Identify any shortfalls in meeting the Air Force radome specification. Describe any further testing necessary to validate the requirements listed within the Air Force radome specification.

(Reference PWS paragraph 3.1.1.2.4, Specification Section 4.1).

• L3.2.2 Describe the Offeror’s strategy for selecting and procuring materials for radome construction, including the implementation of industry of military standards such as ASTM, SAE, and MIL-STD (Reference PWS paragraph 2.0, 2.2.8, 3.1.1, 3.1.2, Table 4, Specification Section 2.1).

• L3.2.3 Describe the Offeror’s approach to designing and selecting materials for a radome to meet the challenges of operating within an arctic environment.

L3.3 Subfactor 2: Manufacturing and Production For Manufacturing and Production, the Offeror shall provide evidence of the following abilities:

• L3.3.1 Describe the proposed manufacturing process, including the production lead-time and schedule management, quality control measures, supply chain strategy, adherence to industry and military standards, and inspection procedures (Reference PWS paragraph 3.1.2, 3.1.3 Specification Section 3.2.2).

• L3.3.2 Describe the proposed packaging material used to ensure arctic hardening, survivability and durability of the radome during transportation, and long-term storage in an outdoor frigid environment. (Reference PWS paragraph 1.5, 3.1.2.3, 3.1.2.3.1, 3.1.2.3.2, 3.1.3, 3.1.3.1, 3.1.3.2, 3.1.3.4.1 and 3.1.4, Specification Section 3.1.3.8, 3.1.3.12, and 3.2.2)

L3.4 Subfactor 3: Installation, Teardown and Removal For Installation, Teardown, and Removal the Offeror shall provide evidence of the following abilities:

• L3.4.1 Describe the approach of installing, tearing down, and removing radomes for a radar site, including the use of specialized equipment. Explain the required personnel, logistics, shipping, timeline, and process of identifying and mitigating issues at the installation site. (Reference PWS paragraphs 3.2, 3.1.2, 3.2.3, 3.2.4, 3.2.7, 3.2.7.1, 3.2.7.2, 3.2.7.3 and 3.2.7.4)

• L3.4.2 Describe the approach to performing the installation of a radome to include the protection of the radar system, resolving deficiencies in the installed base ring, and managing production in adverse weather conditions. (Reference PWS paragraphs 3.1.1.2.5, 3.2, 3.2.1, 3.2.2, 3.2.3.1, and 3.2.4)

• L3.4.3 Describe the Offeror’s capacity to perform radome install, tear down, and removal at multiple radar sites within a calendar year’s work period as allowed by seasonal weather constraints.

L.3.5 Subfactor 4: Testing and Quality Assurance For Testing and Quality Assurance, the Offeror shall provide evidence of the following abilities:

• L3.5.1 Describe the approach to testing and evaluating radomes, including the use of testing and evaluation procedures that meet the requirements of the FPS-124 radome specification (Reference PWS paragraphs 3.1.1.2.4, 3.1.2.1, 3.1.2.2, 3.2.5, 3.2.5.1, and

3.2.5.2 and Specification Section 4).

• L3.5.2 Describe the proposed testing quality assurance strategy including the process and procedures that will be used to ensure the quality of the radome at the production stage and at installation (Reference PWS paragraphs 3.1.2.1, 3.1.2.2, 3.2, 3.2.5, and 3.2.6).

L4.0 VOLUME III – FACTOR 3, SMALL BUSINESS PARTICIPATION SUBMISSION

L4.1 General.

The Small Business Participation Submission is required from all Offerors, including small businesses and companies with Master, Individual, commercial subcontracting plans and/or comprehensive subcontracting plans. The Offeror/joint venture member and each proposed critical subcontractor shall include only the first tier of subcontractors for this effort. Offerors are advised that the Small Business Participation Submission is not the same as the Small Business Subcontracting Plan required by FAR 52.219-9. Large business Offerors shall not utilize the Small Business Subcontracting Plan in the place of the Small Business Participation Submission. Small Business Participation will be evaluated on an Acceptable/Unacceptable basis; Offerors must be rated Acceptable for the Small business Participation factor in order to be eligible for award.

L4.1.2 Formant and Specific Content The Offeror shall submit a Small Business Participation Submission for itself and any joint venture member, as well as each proposed critical subcontractor in a separate volume labeled “Volume III – Small Business Participation Submission”. The Small Business Participation Submission shall address each of the following elements in the proposed performance of this resultant contract:

L4.1.2.1 The extent of participation of proposed Small Businesses (SB) when subcontracting possibilities exist, include the company names with CAGE codes the Offeror plans to use in the performance of this resultant contract; and, L4.1.2.2 The description of the subcontracted work these proposed firms are to perform; and, L4.1.2.3 The associated goals expressed in terms of percentages of the total planned subcontracted dollars. If limited or no subcontracting possibilities exist for these socio-economic entities, provide rationale for such. Offerors are cautioned against only acknowledging a goal is not met, if applicable. Rather, adequate rationale includes specific reasons why a goal is unmet, and any actions being taken to increase any unmet goals.

Additionally, if the Offeror/joint venture member/critical subcontractor is a small business concern, it should include the work it will be performing when calculating the goals for your Small Business Concern Participation information.

L5.0 VOLUME IV – FACTOR 4, ADMINISTRATIVE AND RESPONSIBILITY

MATERIAL

L5.1 General.

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file; as well as assisting the PCO in making a responsibility determination. Offerors shall provide the following additional documentation.

L5.1.2 Small Business Subcontracting Plan If the Offeror is other than a small business, the Offeror shall provide its individual Small Business Subcontracting Plan conforming to the requirements of FAR 19.7, DFARS 219.7, and FAR 52-219-9, Small Business Subcontracting Plan, that separately addresses and specifies the extent of the Offeror’s commitment to the participation of SB, VOSB, SDVOSB, HUBZone, SDB, and WOSB concerns. The Offeror shall submit its Subcontracting Plan as part of this volume. If the proposed goal for any category is zero, the Offeror shall provide rationale within this section. The Subcontracting Plan of the successful Offeror 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 PCO. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and the performance will be monitored by the Government and reported on the CPARS during contract execution to include performance against subcontracting goals. Large Business Offerors are advised that while the SB Subcontracting Plan must be submitted to be eligible for award, the acceptability of the content of that plan is part of the Responsibility Determination Assessment and not part of the evaluation.

L5.1.3 Contract Forms and Certifications.

L5.1.3.1 Proposal cover page which includes the Offeror company name, Commercial and Government Entity (CAGE) Code, Unique Entity Identifier (UEI), as well as the primary point of contact name(s), office phone numbers, cell phone numbers, and email addresses for individuals who are authorized to discuss the proposal with Government personnel on behalf of the Offeror.

L5.1.3.2 Section A – Solicitation/Contract Form:

Complete blocks 12-18, and the Signature and Date block 17-18, of the Standard Form (SF) 33, and include within Volume IV under the heading “Section A – Solicitation/Contract Form”. A signature by the Offeror on the Standard Form 33 constitutes an offer, which the Government may accept. Offeror shall list that the proposal is valid for minimum of 365 days from solicitation close date on front page of solicitation. Offeror shall list all acknowledged amendments in block 14.

L5.1.3.3 Section B – Supplies or Services and Costs/Prices:

Do not input pricing information in Section B of the model contract. All required prices shall be proposed in the Pricing Matrix Worksheet Section J Attachment 5.

L5.1.3.4 Section I – Contract Clauses:

The Offeror shall complete all required clause fill-ins.

L5.1.3.5 Section K – Representations, Certifications, and other Statements of Offerors or Respondents:

FAR 52.204-7, System for Award Management, is incorporated by reference in Section I. The Offeror shall follow the instructions cited in this Section K, FAR 52.204-08 and complete all representations, certifications, acknowledgments, and statements electronically in the System for Award Management (SAM) accessed through as part of responding to this RFP (https://www.sam.gov). If a representation, certification, acknowledgement or statement cited in this Section K cannot be found in SAM, then the Offeror shall submit that Section K representation, certification, acknowledgement or statement. Failure to adhere to these instructions will render an Offeror as being ineligible for award.

L5.1.4 Exceptions 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. Failure to meet a requirement may result in an offer being ineligible for award. 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.

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 provided in Table 2, Solicitation Exceptions, below.

L5.1.5 Contractor Team Arrangement:

If the Offeror is utilizing a Contractor Team Arrangement, the Offeror shall provide a copy of their approved arrangement, outlining the roles and responsibilities of all partners. The agreement must provide evidence that it will be valid beginning on the date of contract award.

The teaming arrangement must consist of a prime contractor (who will be the sole point of contact and have overall responsibility for the contract) and any subcontractor whose technique, capability, certifications, or qualifications are used in the technical proposal. This agreement does not preclude Offerors from adding team members after contract award. Failure to provide this agreement may be considered grounds for elimination and therefore ineligible for award.

Table 2: Solicitation Exceptions

SOLICITATION

Document Page/

Paragraph Requirement/

Portion Rationale

PWS, Model Contract, Section L, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement cannot/will not be met

L5.1.6 Authorized Offeror Personnel:

Provide the name, title, telephone number, and email address of the company/division point of contact responsible for negotiating with the Government. The Offeror shall also provide a letter stating the person is authorized to negotiate on behalf of the Offeror with the Government and commit/sign all contractual documents.

L5.1.7 Organizational Conflicts of Interest

L5.1.7.1 In accordance with FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting Officer has analyzed the planned acquisition and determined that no known significant potential Organizational Conflict of Interest (OCI) exists with respect to this solicitation. However, should a significant OCI be discovered during proposal evaluation, the Government reserves the right to request an OCI Mitigation Plan from affected Offerors for evaluation prior to the award decision.

L5.1.7.2 Offerors shall perform their own OCI analysis and submit the results of that analysis as part of their proposal. Specifically, Offerors shall analyze the planned acquisition for actual or potential OCI situations associated with its or any of its teammates or subcontractor’s performance under any contract it or any of its teammates or subcontractors has been or may be awarded by any federal agency or other entity. Offerors shall describe in detail the methodology used to identify actual or potential OCIs. The Offeror shall also provide a detailed description of actual or potential OCIs uncovered for itself, its subcontractors, or teammates and include a classification of the OCI as biased ground rules, impaired objectivity or unequal access to non-public information. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office and the U.S.

Court of Federal Claims.

L5.1.7.3 Upon award, the resulting contract may include an OCI limitation applicable to subsequent Government work, at either a prime contract level, at any subcontract tier, or both.

During evaluation of proposals, the Government may, after discussions with the Offeror and consideration of ways to mitigate or avoid identified significant conflicts of interest, insert a clause or term and condition in the resulting contract which disqualifies the Offeror from further consideration for award of future contracts.

L5.1.7.4 Exchanges necessary to resolve OCI issues shall not be considered discussions. As such, the Contracting Officer may issue Evaluation Notices to the Offeror prior to any decision to enter into discussions in order to resolve questions or concerns with the Offeror’s OCI analysis or mitigation plan.