Atch-5 FY26 Section L_INSTRUCTIONS TO OFFEROR-Draft.pdf

SECTION L

INSTRUCTIONS TO OFFERORS

1) PROPOSAL SUBMISSION

a) PROPOSAL SUBMISSION REQUIREMENTS

i) Each volume shall be submitted electronically as a separate file utilizing the naming convention indicated below via Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil/. The proposal shall consist of three (3) volumes (illustrated below).

ii) ALL PROPOSALS SHALL BE SUBMITTED ELECTRONICALLY THROUGH THE PIEE WEBSITE. Proposals submitted by mail or hand-carried will not be evaluated. Proposals sent through proprietary or third-party File Transfer Protocol (FTP) sites or DoD SAFE will not be retrieved. Submission shall be in searchable Adobe PDF format and legible. You are limited to a maximum file size of

1.96 GB per attachment. There are no limitations on how many files can be uploaded;

however, the offeror should follow the requirements of the volume submissions.

Zipped files cannot be uploaded into PIEE.

(1) FILE DESCRIPTION: Include a “File Description” for each file(s) you upload.

The “File Description” will be included in the email notice to the recipient you choose to have access your file(s). NOTE: Do NOT enter Privacy Act Data (Personal Identification Information (PII)) in the File Description.)

(2) For instructions on how to post an offer, please refer to the Posting Offer demo: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

iii) RECEIPT OF SUBMISSIONS. It is the responsibility of the Offeror to confirm receipt of proposals in PIEE. For the purposes of establishing whether a proposal submission is considered timely, the Government considers the date and time stamp of the file upload within PIEE as the official received date and time. Do not assume that electronic communication is instantaneous. It can take several minutes or even hours in some cases. The Government will not be responsible for submissions delivered to any location or to anyone other than those designated to receive proposals. Offerors are responsible for ensuring that proposals are submitted to reach the designated recipient. Offerors are responsible for allowing sufficient time for the proposal to be received in accordance with the instructions provided.

(1) All proposals shall be submitted no later than the time and date specified on SF

33, block 9. Offerors’ proposals received after the required time and date deadline will be handled in accordance with FAR 15.208. Offerors should not assume that they will have an opportunity to clarify or correct anything in their proposals after submitting it in response to the original Solicitation, so any submissions should be submitted on the best terms possible and free of errors.

https://piee.eb.mil/

iv) Each paragraph should be single spaced and shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Times New Roman fonts are required. Font limitations do not apply to charts, tables, exhibits, and figures, but font must be legible. A page is considered one single sided 8.5” by 11” unless otherwise noted. 11” by 17” pages may be used to depict figures, tables, and exhibits.

(1) The following volumes of material shall be submitted:

Table 1 – Page Submission Requirements

Volume Title Digital Copies Maximum Pages

I Past Performance 1 15

I Technical/Risk Approach 1 15

II Price 1 No page limit

III

Solicitation, Offer and Award Documents, Certifications/Representations, Management Approach, and Teaming Arrangements

1 No page limit

(2) The page limitations for Volume I exclude past performance questionnaires

(PPQs), CPARS reports, invoices, table of contents, schedule, cover page and/or letter, acronym table, figures, tables, exhibits, and summary table. Volumes II and III do not have page limitations. Text should be at least size 12 font, single spaced. Font limitations do not apply to charts, tables, and figures, but font must be legible.

(3) Manpower charts, JV and/or teaming agreements, subcontractor arrangements, letters of commitment, and schedules are excluded from the page count.

(4) NOTE: Pages that exceed the required page limitations noted above will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government.

b) PROPOSAL FILES

i) The Offeror’s name, solicitation number, and solicitation closing date and time must be affixed to the outside of each volume. Offerors must organize their proposals as described and outlined below. Each volume must have a table of contents and a cover sheet to include the Offeror’s CAGE Code, Unique Entity ID (UEI), address, NAICS, and business size in accordance with the System for Award Management (SAM) and Point of Contact information, such as email and phone number.

ii) Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered (i.e., page x of x) and identified by the complete company name, date and Request for Proposal (RFP) number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word. Files shall use the following page setup parameters:

Table 2 – Page Setup Parameters

Margins – Top, Bottom, Left, Right 1”

Gutter 0”

From Edge – Header, Footer 0.5”

Page Size, Width 8.5”

Page Size, Height 11”

iii) The following additional restrictions apply:

(1) File Packaging. Files shall be in read-only format, using PDF files. Files should be created in Word or Excel and saved accordingly, then also as Adobe files. Only Adobe files shall be submitted for Word files. Excel files must be submitted in both formats – Excel and Adobe. USACE utilizes Microsoft Office 365. Ensure all files are compatible and viewable in Microsoft Office 365 format. Self-extracting exe files are not acceptable.

(2) Content Requirement. All information shall be confined to the appropriate file.

The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

iv) All narratives must contain sufficient detail to demonstrate technical capability. The narratives must address RFP submission requirements as detailed herein. Offerors are cautioned that “parroting” of the technical requirements of the Performance Work Statement (PWS) with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

v) The following shall be included in the submission for each Factor identified above.

2) VOLUME I – PAST PERFORMANCE AND TECHNICAL/RISK APPROACH

a) FACTOR 1: PAST PERFORMANCE

i) Factor 1 shall contain past performance information regarding similar contracts. This factor shall not exceed the page count listed in Table 1, under Section A, excluding Past Performance Questionnaire, Contractor Performance Assessment Reporting System (CPARS), and any documentation supporting teaming arrangements (i.e., subcontracting commitments, etc.). All narratives must contain sufficient detail to demonstrate recency and relevancy.

ii) An offeror that relies upon the experience or performance history of a subcontractor, affiliate, or entity other than the offeror must provide a fully executed joint venture agreement, teaming agreement, or commitment (in the case of affiliates). Joint venture agreement(s), teaming agreement(s), and/or letters of commitment shall be submitted under Volume III of the Offeror’s proposal.

iii) In the case of affiliates, the commitment, a description of each entity’s relationship, and the affiliate’s meaningful participation must be described in a document signed by the authorized representatives of both the Offeror and its affiliate.

iv) Each project submitted shall include the following information:

(1) Project Title

(2) Location

(3) Contract Number/Task Order Number

(4) Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.).

(5) For Government projects, the agency issuing the task order or contract.

(6) Role of Offeror: Indicate type and percentage of work performed by the Offeror or Offeror’s team member.

(7) All UEI and CAGE code(s) for all entities whose experience is included on the project.

(8) Total Dollar Amount

(9) Project Start and Completion Dates: Project must be underway or complete. If an

Offeror presents a project that is underway (substantially complete, at least 50% as defined in the second paragraph under this factor), the Offeror shall provide the date of award and the contract completion date, and the percentage completed in parenthesis.

(10) Brief description of project and define the key scope characteristics.

(11) A copy of the official CPARS evaluation. Interim CPARS evaluations are acceptable for projects that have not been completed. CPARS evaluation, a Past Performance Questionnaire (PPQ) must be completed and submitted. The PPQ is provided as Attachment A. If the Offeror is unable to obtain a completed PPQ from an owner for a project(s) before proposal closing date, the Offeror should complete and submit with the proposal the first page of the PPQ, which will provide contract and client information for the respective project(s). Previously completed PPQs may be submitted provided that the documents do not reference any other RFP. Submitted PPQs must only reference this RFP.

(12) Customer Primary Point of Contact: Name, relationship to project, agency/firm, phone number, and e-mail address. The Government may contact and interview project references. Reference information will not be revealed to other parties.

(13) Procuring Activity Point of Contact: Name, relationship to project, agency/firm, phone number, and e-mail address. The Government may contact and interview project references. Reference information will not be revealed to other parties.

v) Experience in Projects. Offerors shall provide proof of experience as outlined below:

(1) Offerors should submit information on five (5) projects demonstrating recency and relevancy. Only the first five (5) projects submitted will be considered, any projects submitted after that will not be considered or evaluated.

(a) Projects submitted shall be completed, or substantially completed (50% or more), within the last five (5) years from the solicitation issuance date.

Percentage complete is defined as the total amount of work completed on the project. The Offeror is responsible for substantiating this by submitting an invoice showing percentage complete of at least 50% for each individual project. Invoices are not required for projects that are 100% complete as long as a final CPARS report is submitted. Projects may be standalone “C” type contracts or individual task orders. Do not submit Indefinite Delivery Indefinite Quantity (IDIQs) contracts as a single project. They will not be considered. Individual task orders issued under an IDIQ may be submitted.

However, each project submitted will count as one (1) individual project.

(2) Offerors must include a detailed narrative of actions Offerors did to ensure past successes demonstrated the following mandatory key scope characteristics:

(a) Experience with executing/completing the tasks identified in Table 1 of the

PWS.

(b) Experience managing at least one Performance-Based Contract (PBC) with a period of performance ranging between 5-10 years in length.

(c) Experience with National Priorities List (NPL) sites.

(d) Experience that demonstrates progression through the phases of the

Comprehensive Environmental Response, Compensation, and Liability Act

(CERCLA).

(e) Experience that demonstrates progression through multiple phases of State cleanup programs at both CERCLA NPL and compliance regulatory frameworks.

(f) Experience collaborating with US Environmental Protection Agency (USEPA) Region VI as lead regulatory agency.

(g) Experience collaborating with Texas Commission on Environmental Quality

(TCEQ).

(h) Experience in support of AF Defense Environmental Restoration Program

(DERP).

(i) Experience in design, implementation, and operation & maintenance (O&M) of treatment systems (e.g., pump and treat, air sparge/biosparge, soil vapor extraction, in-situ or ex-situ chemical oxidation, indoor air mitigation, etc.), capping, and soil excavations.

(j) Experience managing multiple, comingled areas of concern in different phases of investigation and cleanup that require more than one (1) remedial action or technology to be implemented, differing regulatory frameworks, and emerging contaminants.

vi) Offerors should include detailed narrative of actions Offerors did to ensure past successes demonstrated the following preferred key scope characteristics:

(a) Experience managing a PBC with 20 or more sites or areas of concern (AOC).

(b) Experience in remediating sites with multiple contaminants of concern, e.g., chlorinated solvents, petroleum, oil and lubricants (POL), 1,4-dioxane, PFAS including sites with mixtures of contaminant types.

(c) Experience with Federal Facilities Agreements (FFA).

(d) Experience coordinating and performing environmental restoration activities at a Government Owned Contractor Operated Facility.

(e) Experience coordinating and performing environmental restoration activities at multiple Geographically Separated Units.

(f) Experience in public meeting support and facilitation (e.g. Restoration

Advisory Board (RAB) meetings).

vii) Offerors shall provide a specific narrative explanation of each contract(s)/project(s) submitted for Factor 1 – Past Performance, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP. Offerors should submit projects with similarity of service/support, complexity, dollar value, contract type, and degree of subcontract/teaming.

(1) For any contract(s) that experience schedule and/or cost growth or did not meet technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken. The offerors should address delivery schedule revisions and provide an explanation of why the revision was necessary.

(2) For all contract(s)/project(s) submitted, outline which work was self-performed or performed by a proposed subcontractor.

viii) Past Performance Questionnaire. For all contracts submitted under

Factor 1, a Past Performance Questionnaire or final CPARS must be completed and submitted (i.e., if a CPARS is not available, a Past Performance Questionnaire shall be submitted). The offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to [EMAIL] The offeror shall e-mail to the Contracting Office a list of all the POCs who were sent a questionnaire. The Government must receive this list no later than the proposal due date. The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name;

POC Title; POC Telephone Number; POC E-mail Address; and Date E-Mail to POC.

ix) Submissions. Offerors should provide and submit the prime contract number and all Governmental agency POCs.

x) It is the responsibility of the Offeror to identify, detail, and demonstrate the relevancy of the submitted projects to the solicitation criteria elements. The evaluation boards will not make assumptions. If the projects don't address the above requirements, the proposal will receive no further consideration. In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available, the offeror may not be evaluated favorably or unfavorably on past performance. A summary chart that shows which relevant features have been met for each project will not be sufficient for demonstration of relevancy.

xi) The contractor team agreement or commitment shall be provided in Volume III. Teaming agreements will be evaluated under Factor 1. If a teaming agreement, or commitment is not provided, the projects and experience of any team members outside of the Offeror will not be considered.

b) FACTOR 2: TECHNICAL/RISK APPROACH

i) Provide a technical/risk approach not to exceed the page count listed in the Table 1 under Section A. The Offeror shall submit a comprehensive technical approach that demonstrates achievement of the performance objective (PO) in the performance period specified for each site in accordance with PWS Table 1: Performance Table and other applicable agreements such as regulatory agreements (FFA), decision documents, and project workplans.

ii) This factor shall be organized into the following sections:

(1) Section 1 – Integrated Master Schedule (IMS). The Offeror's technical approach shall include an Integrated Master Schedule (IMS) aligned with the CLIN/Sub-CLIN Structure provided with the RFP, consistent with the Offeror’s proposed approach, and in accordance with the requirements in the PWS. The IMS shall:

(a) Present feasible timing and sequence of all activities and documents necessary to demonstrate achievement of the Performance Objectives within the Performance Periods.

(b) Demonstrate incorporation of feasible Government and Regulatory review periods as defined in the PWS.

(c) Identify timing of decision points addressing risk mitigation and/or contingency strategies.

(2) Section 2 – Evaluation of Risks. The comprehensive approach shall evaluate risks of the proposed technical approach for achieving or exceeding all POs in the PWS and other applicable agreements such as regulatory agreements (FFA), decision documents, and project workplans. The Offeror’s proposal shall demonstrate the following:

(a) Risk assessment:

(i) Risk factors including the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance.

(ii) Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS or specification requirements), whether or not those requirements are identified as factors.

(b) Risk classification:

(i) Classify each risk in accordance with DoD Source Selection Procedures, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance.

(c) Risk mitigation:

(i) Propose risk mitigators and contingency plans for identified risks that will eliminate or reduce risk to an acceptable level. The risk evaluation shall include the decision logic, identified thresholds, and timing for implementation of a mitigation strategy and/or contingency plan if the proposed approach proves incapable of meeting the POs within the performance periods.

3) VOLUME II – PRICE

a) FACTOR 3: PRICE

i) Volume Organization

(1) Table of Contents

(2) List of Tables and Figures

(3) Glossary of Abbreviations and Acronyms

(4) Exceptions, Assumptions, and Rationale

ii) Standard Proposal Information

(1) Provide a Table of Contents for Volume II

(2) Provide a List of Tables and Figures for Volume II

(3) Provide a Glossary of Abbreviations and Acronyms for Volume II

iii) General Instructions. This section is to inform the Offeror of the information submittal requirements to evaluate the Completeness, Reasonableness, and Balance of Offeror’s proposed prices. Compliance with these requirements is mandatory and failure to comply may result in rejection of Offeror’s proposal.

(1) The responsibility to substantiate the credibility of proposed prices rests with the

Offeror at the time of proposal or during subsequent discussions (if any are held).

(2) Compliance with these instructions is mandatory.

(3) Failure to comply may render the proposal ineligible for award.

(4) Data beyond that required by this instruction shall not be submitted unless it is considered essential to document or support the price.

(5) All information relating to the proposed price must be included in the section of the proposal designated as the price volume.

(6) In accordance with FAR 15.305 (a)(1), adequate price competition is anticipated which will establish price reasonableness. However, if after receipt of proposals, the PCO determines that there is inadequate price competition, and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

(7) Unreasonably high Total Evaluated Price (TEP) may be grounds for eliminating a proposal from the competition. Unbalanced pricing may also be grounds for eliminating a proposal from competition if the unbalanced pricing is determined to present an unacceptable risk to the Government.

(8) The Offeror shall propose a price on a FFP basis in accordance with the proposed

Contract Line Item (CLIN)/SubCLIN structure.

(9) Price Proposal documents shall not be password protected.

(10) All Microsoft Excel spreadsheets shall be submitted in Microsoft Excel format (no PDF).

iv) Submission of Schedule B

(1) Schedule B, as included in this RFP, contains parent CLINs for each site included in this requirement. Parent CLINs shall not be altered. Sub-CLINs will be utilized IAW CLIN/Sub-CLIN Structure and Guidance provided in the PWS.

Prices proposed for Sub-CLINs must equal the parent CLIN total proposed for the applicable site.

b) EXCHANGES

i) The Government intends to award without discussions and make an award based on initial proposals; however, discussions or negotiations may be held and result in a Final Proposal Revision (FPR). If it is determined to be in the best interest of the Government to hold discussions, the Government will make a Competitive Range determination, Evaluation Notices (ENs) may be issued to Offerors in the competitive range, responses will be requested from applicable Offerors, and discussions will be opened. The competitive range may be further reduced for purposes of efficiency pursuant to FAR 15.306(c)(2). Formal responses to ENs (if applicable), discussion items, and final proposal revisions will be considered in making the award decision.

ii) Any revision or non-concurrences to contract terms and conditions submitted in the FPR may not be subject to further discussion or negotiation and may render the offer unacceptable to the Government. This provision is not intended to restrict the Team’s opportunity to revise figures (e.g., prices, rates, etc.); rather, it is intended to preclude any misunderstandings by the Government, which could result if new or revised terms and conditions are submitted in the FPR that have not been fully disclosed, discussed, and understood during discussions or negotiations. 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.

iii) Teams are cautioned to submit sufficient information in the format specified in Section L. Teams may be asked to clarify certain aspects of their proposal.

Communication conducted to resolve minor or clerical errors will not constitute discussions and the Contracting Officer reserves the right to award a contract without the opportunity for proposal revision.

4) VOLUME III – SOLICITATIONS, OFFER AND AWARD DOCUMENTS,

CERTIFICATIONS/REPRESENTATIONS, MANAGEMENT APPROACH, AND

TEAMING ARRANGEMENTS

a) Tab A – Certifications and Representations – Each Offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the RFP. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

i) Section A – Standard Form 33 (SF 33), Solicitation, Offer and Award

ii) Section K – Representations, Certification and Other Statements of Offerors

iii) Certificate of Corporate Authority

b) Tab B – Joint Venture and Mentor-Protégé Agreements – If more than one contractor is listed in Block 14, or the Offeror listed in Block 14 is a joint venture (JV), then a signed JV agreement must be submitted with the proposal and the Offeror shall be registered in the System for Award Management (SAM) as a legal entity separate from the individual joint venture members. However, each member of the JV must submit its own UEI with the proposal.

i) Small business Offerors (e.g., 8(a), HUBZone, SDVOSB, WOSB, etc.) submitting a proposal as a JV or Mentor-Protégé JV shall submit evidence from the Offeror’s SBA Servicing Agency that the Offeror has notified and discussed the proposed JV for this specific project with the appropriate SBA Representative or Business Opportunity Specialist.

ii) JOINT VENTURE AGREEMENTS, APPROVED MENTOR-PROTÉGÉ

AGREEMENTS, TEAMING AGREEMENTS, and/or LETTERS OF

COMMITMENTSHALL BE SUBMITTED WITH THE PROPOSAL UNDER

VOLUME III.

c) Tab C – Management Approach – Management Approach will not be separately evaluated other than complete compliance with the below.

i) The Offeror shall submit a detailed management plan describing how the Offeror will manage the work in order to achieve the POs within the performance periods and ensure quality services and deliverables. The plan shall include the following information:

ii) Discuss how this requirement will be managed and resourced, highlighting key personnel with qualifications as specified in Attachment L-1 (Labor Category Qualifications). Provide an organization chart and narrative, describing the level of responsibility each position is designated, as well as lines of authority. Outline the Offeror’s approach to subcontractor management, detailing the flow of information and performance management strategies. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, UEI Number and type of work to be performed by citing the applicable Government PWS PO. In addition, letters of commitment shall be included for all major subcontractors.

iii) Quality Control. The Offerors proposal shall describe the Offerors approach and commitment to quality control as follows:

(1) Given the scope of the project, outline the strategy to maintain quality through the duration of the project. Provide quality control execution/staffing plan, to include ensuring subcontractor quality control, methods to address poor quality of subcontractor work, and noting the team communication and coordination strategy between stakeholders (Air Force, Contractor, Regulators, and Community).

(2) Identify any risks to implementing quality products and plans to mitigate those risks.

iv) Describe the approach to change management during the period of performance against strict schedule goals.

v) Provide a statement confirming the Offeror has a current and approved property management system. The Offeror shall describe an approach to tracking and managing the Government Furnished Equipment (GFE) and Government Furnished Property (GFP) provided in Enclosure 3.

d) Tab D – Affirmative Responsibility Determination Submission Requirements – In accordance with FAR Subpart 9.1, The Contracting Officer will perform an affirmative responsibility determination to ensure that the Offeror has (a) adequate financial resources to perform; (b) ability to comply with the required performance schedule; (c) a satisfactory performance record; (d) a satisfactory record of integrity and business ethics;

(e) the necessary equipment and facilities to perform or the ability to obtain them; and (f) be otherwise qualified and eligible to receive award.

i) The following information will be required to assist with Contracting Officer's determination of the offeror responsibility and shall be submitted under Tab C of Volume III:

(1) Proof of Financial Ability: The offeror shall provide copies of the following financial statements: balance sheet clearly depicting working capital (current assets minus current liabilities), income statement and statement of cash flows for the fiscal year most recently completed. These financial statements shall be certified by an independent Certified Public Accountant (CPA) or certified by an officer of the company. The offeror shall include the name, address, and telephone number of the firm or CPA which prepared or certified the financial statement. If the certification is provided by an officer of the company the following certification shall be notarized and submitted.

(a) “This is to certify that to the best of my knowledge and belief the financial data and the accompanying notes to the financial statements are accurate, complete, and prepared in accordance with Generally Accepted Accounting Procedures from the company’s general accounting records. The description and amounts are based upon the _________________ method of accounting and reflect the company’s financial status as of ________________."

[Signature] [Printed Name] [Title and Date]

(2) Number of years the firm has been in business.

(3) Name, address, and telephone numbers of two credit/trade references.

(4) A list of present commitments to include all projects that have been accepted but performance has not begun. This list shall include but is not limited to the dollar value thereof, the name of the organization under which the work is being performed, and a description of the work being performed. Include names and telephone numbers of personnel within each organization who are familiar with the prospective contractor's performance.

(5) If the prospective contractor is a joint venture, the Contracting Officer will use this information in making an affirmative responsibility determination for award to the successful offeror, in accordance with FAR Part 9.