Solicitation - FA813721R0022.pdf

IMPORTANT - The "offer" section on the reverse must be fully completed by offeror.

4. CONTRACT NUMBER 5. REQUISITION/PURCHASE REQUEST NUMBER 6. PROJECT NUMBER

7. ISSUED BY CODE 8. ADDRESS OFFER TO

9. FOR INFORMATION

CALL:

a. NAME b. TELEPHONE NUMBER (Include area code) (NO COLLECT CALLS)

SOLICITATION

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid and "bidder".

10. THE GOVERNMENT REQUIRES PERFORMANCE OF THE WORK DESCRIBED IN THESE DOCUMENTS (Title, identifying number, date)

11. The contractor shall begin performance within calendar days and complete it within calendar days after receiving award, notice to proceed. This performance period is mandatory negotiable. (See ).

13. ADDITIONAL SOLICITATION REQUIREMENTS:

a. Sealed offers in original and copies to perform the work required are due at the place specified in Item 8 by (hour) local time (date). If this is a sealed bid solicitation, offers will be publicly opened at that time. Sealed envelopes containing offers shall be marked to show the offeror's name and address, the solicitation number, and the date and time offers are due.

b. An offer guarantee is, is not required.

c. All offers are subject to the (1) work requirements, and (2) other provisions and clauses incorporated in the solicitation in full text or by reference.

d. Offers providing less than calendar days for Government acceptance after the date offers are due will not be considered and will be rejected.

STANDARD FORM 1442 (REV. 8/2014)

Prescribed by GSA - FAR (48 CFR) 53.236-1(d)

12a. THE CONTRACTOR MUST FURNISH ANY REQUIRED PERFORMANCE AND PAYMENT BONDS?

(If "YES", indicate within how many calendar days after award in Item 12b.)

12b. CALENDAR DAYS

YES NO

SOLICITATION, OFFER,

AND AWARD

(Construction, Alteration, or Repair)

1. SOLICITATION NUMBER 2. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

3. DATE ISSUED PAGE OF PAGES

AMOUNTS

OFFER (Must be fully completed by offeror)

14. NAME AND ADDRESS OF OFFEROR (Include ZIP Code) 15. TELEPHONE NUMBER (Include area code)

16. REMITTANCE ADDRESS (Include only if different than Item 14.)

CODE FACILITY CODE

17. The offeror agrees to perform the work required at the prices specified below in strict accordance with the terms of this solicitation, if this offer is accepted by the Government in writing within calendar days after the date offers are due. (Insert any number equal to or greater than the minimum requirement stated in Item 13d. Failure to insert any number means the offeror accepts the minimum in Item 13d.)

18. The offeror agrees to furnish any required performance and payment bonds.

19. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the solicitation -- give number and date of each)

AMENDMENT

NUMBER

DATE.

20a. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER (Type or print) 20b. SIGNATURE 20c. OFFER DATE

21. ITEMS ACCEPTED:

AWARD (To be completed by Government)

CONTRACTING OFFICER WILL COMPLETE ITEM 28 OR 29 AS APPLICABLE

28. NEGOTIATED AGREEMENT (Contractor is required to sign this document and return copies to issuing office.) Contractor agrees to furnish and deliver all items or perform all work requirements identified on this form and any continuation sheets for the consideration stated in this contract. The rights and obligations of the parties to this contract shall be governed by (a) this contract award, (b) the solicitation, and (c) the clauses, representations, certifications, and specifications incorporated by reference in or attached to this contract.

29. AWARD (Contractor is not required to sign this document.) Your offer on this solicitation is hereby accepted as to the items listed. This award consummates the contract, which consists of (a) the Government solicitation and your offer, and (b) this contract award. No further contractual document is necessary.

30a. NAME AND TITLE OF CONTRACTOR OR PERSON AUTHORIZED TO SIGN (Type or print)

31a. NAME OF CONTRACTING OFFICER (Type or print)

30b. SIGNATURE 30c. DATE 31b. UNITED STATES OF AMERICA

BY

31c. DATE

STANDARD FORM 1442 (REV. 8/2014) BACK

22. AMOUNT 23. ACCOUNTING AND APPROPRIATION DATA

24. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM 25. OTHER THAN FULL AND OPEN COMPETITION PURSUANT TO

10 U.S.C. 2304(c) ( ) 41 U.S.C. 3304(a) ( )

26. ADMINISTERED BY 27. PAYMENT WILL BE MADE BY

FA813721R0022

Section A - Solicitation/Contract Form

Section B - Supplies or Services and Prices/Cost

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Section C - Description/Specifications/Statement of Work

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 MAC BOA Execution Business Rules

1. General

a) A BOA is not a contract pursuant to FAR 16.703(a)(3). An Order issued pursuant to a BOA will become a binding contract at the time of the Government's acceptance of an Order proposal and award of an Order.

b) A BOA will be valid for up to five (5) years beginning from the effective date of the initial BOA execution. IAW DFARS 216.703(c), the period during which orders may be placed against a BOA may not exceed 5 years.

c) IAW FAR 16.703(c)(2), a BOA shall be reviewed annually before the anniversary of its effective date and revised as necessary to conform to the changing requirements of the FAR and other applicable statutes and regulations. BOAs shall be changed only by modifying the agreement itself and not by individual orders issued under it. Modifying a BOA shall not retroactively affect orders previously issued under it. The terms of the BOA may need to be revised before the annual review due to changes in mandatory requirements.

Prior to the annual review and renewal, the PCO will notify the contractor in writing informing it of the review and confirming that the contractor wishes to have its BOA renewed. As BOAs are not contracts, either the Government or the Contractor may elect not to renew the BOA at the annual review. The Government reserves the right to cancel the BOA if doing so is considered to be in the Government's best interest.

d) BOA Invitations will be released once a year to allow interested contractors an opportunity to submit a proposal for evaluation to obtain an executed MAC BOA. The Government will execute no-cost BOAs to offerors whose proposals in response to the BOA invitation are found acceptable based on the criteria stated in the invitation.

An annual synopsis for requirements falling under the scope of the MAC BOA will be released in Beta Sam.

The annual synopsis will cover requirements related to Construction Services that are within the scope of the MAC BOA and designated for performance under the MAC BOA which emerge within the year after the annual synopsis is published. The Air Force will not conduct a separate BOA synopsis for any such emergent requirement prior to issuing the applicable Phase Two, Competitive Requirement/Order Process within BOA Holder Pool.

NOTE: The annual BOA Invitation will be the only opportunity contractors will have to obtain an executed MAC BOA , and be in the Holder Pool, in order to propose on Order Proposal Request (OPRs) issued within the year; BOA proposals will not be solicited, accepted, and will not be executed, at any time other than during the annual BOA Invitation, even for those emergent requirements not specifically identified in the annual synopsis.

Therefore, if a contractor desires to participate in any future MAC BOA order that may arise within the year, it is imperative that the contractor submit a proposal in response to the annual BOA Invitation.

e) Only Air Force Tinker AFB Contracting AFSC/PZIOC is authorized to execute, modify, and undertake annual reviews of BOAs resulting from this solicitation.

f) The execution of a BOA does not guarantee that the Government will place future orders with the offeror.

2. Phase Two Order Requests

a) Orders will only be competed amongst contractors that received a BOA in Phase One. An Offeror must be a qualified BOA holder as of the closing date of an Order RFP. The Government will confirm that an Offeror is a qualified BOA holder by checking the effective date of an Offerors BOA. Period of Performance for orders issued against the BOA will be established in each task order and are effective for up to five (5) years from the Task Order effective dates.

b) Offerors are NOT required to propose those subcontractors used to establish technical capability in Phase One (i.e. BOA process); however, Offerors shall propose themselves and/or subcontractors that can meet the evaluation criteria and successfully perform the requirements of each Task Order.

c) Specific evaluation criteria will be identified in the OPR. Evaluation factors may include Technical, Past Performance, Cost/Price, and Small Business Participation. Order source selections may be executed based on:

evaluation of price only; lowest price, technically acceptable (LPTA); or, best value trade-off process.

d) A Statement of Work specific to the Order requirement and the associated Performance Requirements Summary will be provided at the Order level..

e) Pricing information will only be required at the Order level. Orders may vary in contract type from Firm- Fixed-Price, Cost, or a combination of both. The contractor shall adhere to the prices proposed and agreed to in each individual order issued against the BOA. The contractor is not authorized to begin work on an order issued against the BOA until prices have been established. In the event that the Contracting Officer requires work to begin prior to establishment of pricing, failure to reach agreement on price may be disputed under the Disputes clause.

f) Offerors will certify business size standards at the Order level.

g) Responsibility determinations will be made at Phase Two. An otherwise successful Offeror may not be eligible for award if it cannot be determined responsible for any of the reasons in FAR 9.104.

C.2 Small Business Provisions, Joint Ventures, and Subcontracting

1. Set-Asides

a) Order competitions will be set aside for small businesses based on the Governments estimated value of the construction order requirement.

b) It has been determined that for the annual requirements estimated at or below $25M annually, there is a reasonable expectation that two (2) or more responsible small businesses will submit offers and will be capable of providing these services; as such, in Phase Two, those requirements will be set aside for small business participation (SBSA) by those small businesses that have been determined to be acceptable under Phase One of this multi-phase process.

If two (2) or more proposals are not received from responsible small businesses with the capacity and capability to perform the requirement at a fair and reasonable price, the competition will be opened up to all contractors that have been determined acceptable in Phase One, Competition for BOA Holders.

If a requirement has been estimated at or below $25M and therefore set aside for small business, but the proposals come in over $25M, the "Rule of 2" will be applied. If two (2) or more proposals are received from responsible, capable small businesses at a fair and reasonable price, the evaluation will proceed and the contract will be awarded in accordance with the evaluation terms of that Order. However, if two (2) or more proposals are not received from responsible small businesses with the capacity and capability to perform the requirement at a fair and reasonable price, the competition will be opened up to all contractors that have been determined acceptable in Phase One, Competition for BOA Holders.

Market Research will be performed prior to Order competitions in Phase Two, Competitive Requirement/Order Process within BOA Holder Pool for those requirements expected to exceed $25 million. Market Research will consist of competition data received from BOA Holders in response to OPR submissions and resultant Order awards. Based upon this data, if it is determined that there is a reasonable expectation that two (2) or more proposals will be received from responsible small business BOA Holders with the capacity and capability to perform the requirement at a fair and reasonable price, under the "Rule of 2" the requirement will be solicited as a SBSA. If not, proposals will be solicited from all BOA Holders determined to be acceptable under Phase One, Competition for BOA Holders.

2. Size Standards

a) SBA's size eligibility standards are found in Title 13 of the Code of Federal Regulations (CFR) Part 121 (13 CFR Part 121). In order to ensure that an Offeror qualifies as an eligible small business, prospective Offerors are encouraged to review this regulation (which was substantially revised in 2016) in its entirety. 13 CFR 121.103 in particular may assist a prospective offeror in assessing whether affiliation could apply; a finding by the SBA of affiliation between entities may result in a determination that the Offeror is other than a small business and therefore ineligible for the SBSA Order award. An offeror with questions regarding size eligibility standards should contact its legal counsel and/or SBA Office of Government Contracting personnel; 8

(a) Program participants may consult the cognizant SBA Business Opportunity Specialist.

b) The SBA is the sole authority for making determinations of small business status for small business programs; such determinations are binding on the Offeror and on the Contracting Officer.

c) Generally, SBA determines the size status of a concern (including affiliates) as of the date the concern submits a written self- certification that it is small to the procuring agency as part of its initial offer including price. This determination will be done at the Order level (Phase Two) and will apply for the term of the Order NTE five (5) years. For orders that exceed five years, FAR 52.219-28, Post-Award Small Business Program Representation, applies. The Government will not inquire into the size status of an offeror during Phase One.

Joint Ventures (JVs). Due to the complexity and the wide range of capabilities required by the contracts that will be solicited for at the Task Order level (Phase Two), JVs may be utilized. A JV must be an approved BOA holder from Phase One in order to propose as a Prime on a Task Order solicitation at Phase Two, and the JV must comply with the applicable requirements of Title 13 of the CFR (see Parts 121.103(h), 124.513, 125.15, 126.616, and 127.506).

Entities proposing as a joint venture (JV) are encouraged to specifically review 13 CFR 121.103, "How Does SBA Determine Affiliation? subparagraph (h) (Affiliation based on joint ventures) prior to submitting a proposal. 13 CFR 121.103 provides several examples that may assist a prospective offeror in assessing whether affiliation could be applied to its JV. Note: In accordance with 13 CFR 121.103, a JV of two (2) or more business concerns may submit an offer as a small business without regard to affiliation so long as each concern is small under the size standard for NAICS 236210. In order for this affiliation exception to apply, however, the following conditions must be met: there must be a written JV agreement, the JV must do business under its own name and be identified in the System for Award Management (SAM), and the JV must not have been awarded more than three (3) contracts within a two year period from the date of award of the first contract (i.e. as of the date that it submits an initial offer that leads to the award of a contract, the JV must not have been awarded any more than two (2) contracts in the previous two (2) years).

As part of its BOA proposal at Phase One, a JV offeror will be required to submit a copy of its written JV agreement.

Subcontracting Arrangements. Offerors proposing subcontracting arrangements at the Order level (Phase Two) are encouraged to specifically review 13 CFR 121.103, "How Does SBA Determine Affiliation?

(subparagraph (h)(4)) prior to submitting a proposal. A finding by the SBA of affiliation between an offeror and its subcontractor(s) may result in a determination that the Offeror is other than a small business and therefore ineligible for the SBSA Order award.

For SBSA solicitations, Offerors proposing subcontracting arrangements at the Order level (Phase Two) may be required to explain which of its subcontractors are similarly situated subcontractors pursuant to the definition provided in 13 CFR 125.1 for purposes of determining whether the arrangement includes the use of any ostensible subcontractors and thus treated as a JV and the entities considered affiliated.

There is no restriction on the number of JVs or subcontracting opportunities that an Offeror may participate in.

Requirements Basic Ordering Agreement (BOA) Invitation: for Construction Services at Tinker AFB.

Section D - Packaging and Marking

Section E - Inspection and Acceptance

Section F - Deliveries or Performance

Delivery terms and period of performance will be determined on each individual order.

Section G - Contract Administration Data

Section H - Special Contract Requirements

Section I - Contract Clauses

See Attachment #4, MACB Provision and Clause Matrix

MACB Provision and Clause Matrix Key:

P= Provision C= Clause A= Required when Applicable O= Optional R= Required

Section J - List of Attachments

Number Attachment Name Attachment Description

Reference Identifier Date URL Line Item

Section A_ Executive Summary

Solicitation Information

06 APR

Statement of Work 6 April 2021

Statement of Work

06 APR

03 Experience Matrix Statement of Work

24 FEB

MACB Provision and Clause Matrix

Provision and Clause Matrix

24 FEB

ANNUAL

PROJECT

SYNOPSIS

Annual Project Synopsis

01 MAR

Section K - Representations, Certification, and other Statements of Offerors

Section L - Instrs., Conds., and Notices to Offerors

INSTRUCTIONS TO OFFERORS (ITO)

L.1 GENERAL INSTRUCTIONS

L.1.1 These instructions are a guide for preparing a proposal. These instructions describe the type and extent of information required, and they emphasize the significant areas to be addressed in the proposal. Review the Statement of Work SOW) (Attachment 0001) contained in this Basic Ordering Agreement (BOA) Invitation for further insight into the areas that shall be addressed within the proposal. Include sufficient information to enable the Government evaluators to make a determination relative to the Offeror's understanding of the requirements in each of the evaluated areas. It is the Government's intent to execute Basic Ordering Agreements (BOAs) to Offerors who are qualified by receiving an Acceptable rating for Technical and Past Performance.

Cost/Price evaluations will not be performed at the BOA level.

L.1.2 The Government intends to execute BOAs based upon the content of initial proposals and without discussions with Offerors after receipt of those initial proposals; as such, an Offeror's initial proposal should contain sufficient information to satisfy the technical requirements. Offerors are cautioned to examine this solicitation in its entirety to ensure that its proposal contains all necessary information, provides all required documentation, and is complete in all respects. The Government is not obligated to make another request for the required information nor does the Government assume the duty to search for data or to cure problems it finds in proposals.

L.1.3 The Government reserves the right to enter into discussions with Offerors whose initial proposals are determined to be technically unacceptable, if it is in the best interest of the Government to do so.

(a) If discussions are determined to be in the Government's best interest, the Government will only enter into discussions with those Offerors whose proposals do not contain significant informational deficiencies.

(b) The Government will not enter into discussions with Offerors whose proposals are determined to contain significant informational deficiencies; those Offerors will be precluded from receiving a BOA and will be notified in writing.

L.1.4 The BOA process (both the evaluation of proposals and the placement of BOAs), is not a source selection process; as such, the source selection policies and procedures of FAR 15.3 do not apply on orders under $10M.

L.1.5 The proposal shall be valid for 120 days from the required submission date.

L.1.6 Late proposals will not be accepted.

L.1.7 For the purposes of this BOA Invitation:

(a) An Offeror is defined as the prime contractor or Joint Venture (JV) that proposes an organizational capability for consideration for an executed BOA.

(b) A JV is defined as a team of two or more firms that have entered into a legally binding JV agreement. A firm proposing as a JV will be referred to as the Offeror.

L.1.8 Updates to the solicitation, to include amendments, notices, and other information, will be made available on the Contract Opportunities section of the SAM.gov website (beta.SAM.gov). Offerors are advised to continuously monitor the SAM.gov website for new information. Offerors are deemed to have knowledge of all information that is posted to the SAM.gov website.

L.2 PROPOSAL PREPARATION

L.2.1 The proposal shall be prepared in a clear, legible, practical manner. In addition, the Offeror shall write the proposal in English and shall be specific and complete as described in these instructions. Adherence to the prescribed format is required. Failure to provide a proposal in compliance with the instructions specified as COMPLIANCE REQUIREMENT in ITO of this BOA Invitation shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for receipt of an executed BOA. The Government is not obligated to engage in any exchanges with an Offeror who fails to provide all of the required documents for evaluation.

Note: The Government reserves the right to waive the Compliance Review if it is in the Government's best interest.

L.2.2 No classified material shall appear anywhere within the proposal.

L.2.3 The Offeror must be registered in the System for Award Management (SAM) and have a Commercial and Government Entity (CAGE) Code.

L.2.4 Digital MS Word and MS Excel files, where requested and required pursuant to provisions of this BOA Invitation, shall be compatible with Microsoft (MS) Office 2013.

Note: The Offeror shall not lock or password protect any file included in the proposal (e.g. *.docx, *.ppsx, *.

xlsx, *.txt. *.msg).

L.2.5 Adobe Portable Document Format (PDF) Files: Scanned PDF documents, where requested and required pursuant to provisions of this BOA Invitation, must be legible and must be viewable in Adobe Acrobat.

(a) Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. Note: All Narrative elements of the file must be able to be searched for text. The Government will not accept scanned or image-only PDF files in lieu of this requirement and will not invoke the text recognition feature within Adobe.

L.2.6 Compressed files (e.g. *.zip) and Executable files (e.g. *bat, *.exe, *.jar, *.vb, *.wsf) will NOT be accepted. Refer to Attachment 0004 for a complete list of non-acceptable file types.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS

L.3.1 Electronic responses shall be submitted to joseph.sachleben.1@us.af.mil and ashley.brink@us.af.mil.

L.3.2 L.3.3 Digital file names shall use the required naming convention for each specific proposal document identified below. Filenames must be 40 characters or less and must not contain single quotes, spaces and pound or percent signs. If an Offeror's file name is too long (more than 40 characters), it is permitted to abbreviate the Name of the Company field within the file name. The abbreviation used for the name of the company should be consistent across all file names found within the proposal.

L.3.4 Once the Offeror's proposal is submitted, it can be systematically revised prior to the solicitation response deadline.

L.3.5 Do not assume submission will be instantaneous. File size and number of files to be uploaded will be factors to consider. Offerors should allow adequate time for submission completion because the entire proposal must be received by the due date and time for the proposal to be considered timely.

L.3.6 To avoid rejection of an offer, the Offeror shall make every effort to ensure its electronic submission is virus free. Submissions or portions thereof submitted and which the automatic system detects the presence of a virus or which are otherwise unreadable will be treated as unreadable pursuant to FAR 15.207(c).

L.4 PROPOSAL STRUCTURE

L.4.1 The Offeror shall submit a proposal in accordance with the guidelines below.

L.4.1.1 For all documents with the exception of the Experience Matrix, each page shall include the complete Offeror's name, Offeror's CAGE Code, BOA Invitation number, and proposal submission date in a header and/or footer.

L.4.1.2 Each Offeror shall submit ONLY one proposal and that proposal shall address all of the requirements of the BOA Invitation. To be considered for this BOA, the Offeror must submit a complete response to this BOA Invitation using the instructions provided in the ITO. If the Offeror's proposal fails to meet the terms and conditions of the BOA Invitation or takes exception to any of the terms and conditions of the BOA Invitation, the Offeror's proposal will not be acceptable and will not be further considered for execution of a BOA.

L.4.1.3 The Offeror shall provide sufficient detail to substantiate the validity of all stated assertions. The proposal must not merely repeat the BOA Invitation requirements, but rather must provide narrative evidence in support of any statements relating to proposed capabilities or relevant experience. Data not submitted with the proposal and presumed to be known (i.e., previous projects performed for the United States Government) will not be considered as part of the proposal.

L.4.1.4 Page Limits

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages.

(b) Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal.

(c) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.4.1.5 Page Size and Format

(a) Page size shall be 8.5" x 11", not including foldouts. (Pages larger than 8.5" x 11", not including foldouts, will be counted as two pages.)

(b) Page line spacing shall be 1.15 lines.

(c) Except for the reproduced sections of the solicitation document, the text shall be no less than 12-point font. The font size shall be no less than 10 point font for all documents, to include charts, tables, and diagrams.

L.4.1.6 Tables/Charts/Figures

(a) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc.

(b) Tables/charts/figures shall be uncomplicated and shall not exceed 11" x 17" in size.

(c) Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text.

L.5 INFORMATION TO BE SUBMITTED:

L.5.1 General Documents: The Offeror shall include the following:

L.5.1.1 Form SF1442, Solicitation, Offer and Award.

One (1) executed signed copy of the BOA Invitation coversheet. The Offeror must adhere to the following:

(a) Required File Name: OfferorName_SF1442

(b) File Format: Adobe PDF or MS Word

(c) Page Limit: none

(d) COMPLIANCE REQUIREMENT: Failure to provide the signed SF 1442 by an authorized agent shall render the Offeror's proposal non- compliant, and it will not be evaluated nor considered for award of an executed BOA.

L.5.1.2 EITHER all signed amendment coversheets, Form SF30, Amendment of Solicitation/Modification of Contract OR one executed signed copy of the BOA Invitation coversheet (SF1442) with block fourteen (14) completed.

The Offeror must adhere to the following:

(a) Required File Name: OfferorName_SF30 (Amends)

(b) File Format: Adobe PDF or MS Word

(c) Page Limit: none L.5.1.3 Offeror Points of Contact (POC):

The Offeror(s) are required to provide two (2) company individuals whose responsibilities will include reading and responding to Government proposal inquiries through e-mail. For example, the Offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent should be available in case of the main agent's unavailability. The two (2) agents' names, titles, telephone numbers, email addresses, and mailing addresses shall be provided.

The Offeror must adhere to the following:

(a) Required File Name: OfferorName_ POCs

(b) File Format: Adobe PDF or MS Word

(c) Page Limit: none L.5.1.4 Joint Venture (JV) Information:

NOTE: If an Offeror is not proposing a JV the following is not required.

In order for the Government to review the JV partnership, if applicable, the Offeror shall submit the following information:

(a) A signed legal JV agreement prepared by an attorney, which clearly explains the responsibilities of each party to the JV agreement. In addition, the agreement shall clearly explain the formation of the JV and procedures for acceptance of product and payment. The JV agreement shall clearly identify the team lead company and the team lead company's point of contact, as well as their responsibilities explained in detail. In addition, company names, POCs, business size, number of employees (including all affiliates), and description of work to be performed by members of the JV shall be provided as part of the JV agreement.

(b) Any updates to the JV agreement shall be submitted to joseph.sachleben.1@us.af.mil within seven calendar days after the JV agreement is signed.

(c) A signed copy of any other agreements, either formal or informal, that identify the roles and responsibilities of each business concern in the JV.

(d) If other than a small business concern is part of the JV, a copy of the Small Business Administration (SBA) approved SBA Mentor-Protege Agreement. The Offeror should be aware of the SBAs regulations regarding affiliations to determine business size.

(e) Affiliation regulations are especially important for determining the size of JVs.

(f) The Offeror's JV Information must adhere to the following:

(1) Required File Name: OfferorName_JV

(2) File Format: Adobe PDF or MS Word

(3) Page Limit: none L.5.2 Technical Factor:

In order for the Government to have a reasonable expectation of an Offeror's ability to successfully perform on subsequent efforts, the Offeror must demonstrate technical capability by detailing its proposed technical approach to meet the requirements specified in the SOW and this BOA Invitation by providing the following:

- Technical Capability Statement (TCS)

- Bonding

- Corporate Organizational Structure

- Experience/Past Performance L.5.2.1 Technical Capability Statement (TCS)

(a) The Offeror's proposed TCS must adhere to the following:

(1) Required File Name: OfferorName_TCS

(2) File Format: Text Searchable Adobe PDF

(3) Page limit: Twenty (20) pages.

(4) COMPLIANCE REQUIREMENT: Failure to provide a TCS shall render the Offeror's proposal non-compliant, and it will not be evaluated nor considered for award of an executed BOA.

(b) Technical Capability Statement (TCS). The Offeror shall provide a TCS that identifies the Offeror's core competencies, demonstrates how those cited core competencies relate to the Construction efforts at Tinker AFB and the ability to create a dynamic organization fully capable of supporting the Government's requirements by applying those core competencies. In order to demonstrate its technical capability, the Offeror must specifically address the following four elements:

(1) Team Identification / Self-Performance. The Offeror shall provide a TCS that describes, in detail, its processes for analysis and application of cited core competencies and previous experience which allow the Offeror to properly determine which (or all) construction tasks it can self-perform without the use of subcontractors. An Offeror that cannot self-perform specific construction tasks must clearly identify its subcontractors, by company and supported functional area(s).

If the Offeror is citing the core competencies and previous experience of a parent or affiliate company as part of the identification of its own core competencies and previous experience, the Offeror shall explain how the resources of the parent or affiliate company will be utilized in performance of the proposed effort.

(2) The Offeror must identify its process of identifying, vetting, partnering, and leading subcontractors, as well as the Offeror's process for replacing and adding subcontractors if necessary due to non-performance or operational changes to the effort.

(c) Resource / Order Management. The Offeror shall provide a TCS that describes, in detail, the methods that it will employ to manage future order requirements from time of award to completion of the effort. In describing its resource / order management, the Offeror must provide, at a minimum:

(1) The Offeror's approach for planning, allocating, and controlling resources and costs for awarded orders.

(2) The Offeror's process for scheduling, budgeting, and accumulating expenditures (hours and dollars);

identifying expenditures and schedule problems; and tracking individual order performance.

(3) The Offeror's process for timely incorporation of subcontractor technical, schedule and financial performance data into the Offeror's bi-weekly reports for individual orders.

(4) The Offeror's approach to ensuring proper training, licensing, certifications, and safety measures for the execution of awarded orders.

(d) Flexible Staffing Approach. The Offeror shall provide a TCS that describes, in detail, the Offeror's approach to effectively and efficiently support short- and long-term fluctuations in effort (increase/decrease). In describing its flexible staffing approach, the Offeror must address each of the following:

(1) Cross-utilization / temporary reallocation: An effective and efficient approach to making use of existing staffing and subcontractors to better support short-term requirement changes; provide better and more timely support; and, reduce costs through more efficient staffing. Cross-utilization must address an approach to ensuring safety, training, and certification requirements are met in a manner that would not impact quality of the effort.

(2) Rapid increase: An effective and efficient approach to rapidly increase staffing and/or subcontracting capability during surges in effort, for both long- term and short-term increases in workload, where cross-utilization or temporary reallocation is not appropriate.

(3) Responsible reduction in staffing: An effective and efficient approach to reduce staffing to levels commensurate with decreased requirements during periods of protracted reductions in workload while also ensuring retention of qualified employees.

(e) Start-Up Approach:

(1) The Offeror shall provide a TCS that describes the Offeror's generalized approach to providing seamless start-up process that ensures all necessary personnel and subcontractors are in place for execution of future orders.

(2) Include discussions of hiring actions to include pre-employment drug screening, qualification verification, and requisition/issuance of access badges, and security clearances that will ensure timely execution of newly awarded orders and no impact to current operations.

L.5.2.2 Bonding

(a) The Offeror shall submit a prequalification letter from an A.M. Best "A" rated surety (not a bonding agent), that the Offeror is eligible to be bonded for a minimum project amount of $4 million and an aggregate bonding limit of $20 million.

(b) The Offeror's proposed Corporate Organizational Structure must adhere to the following:

(1) Required File Name: OfferorName_Bonding

(2) File Format: Adobe PDF

(3) Page Limit: five (5) pages

(4) COMPLIANCE REQUIREMENT: Failure to provide the corporate organizational structure shall render the Offeror's proposal non- compliant, and it will not be evaluated nor considered for award of an executed BOA.

L.5.2.3 Corporate Organizational Structure

(a) The Offeror's proposed Corporate Organizational Structure must adhere to the following:

(1) Required File Name: OfferorName_COS

(2) File Format: Adobe PDF

(3) Page Limit: six (6) pages

(4) COMPLIANCE REQUIREMENT: Failure to provide the corporate organizational structure shall render the Offeror's proposal non- compliant, and it will not be evaluated nor considered for award of an executed BOA.

(b) Corporate Organizational Structure: The Offeror shall provide a corporate organizational structure narrative (which can include charts, tables, and diagrams) that demonstrates a comprehensive, realistic and feasible organizational overview based on the following:

(1) Identification of the command and control relationships within the Offeror's organization as well as the command and control relationship between the Offeror and each proposed subcontractor. Demonstration of the command and control relationships must include identification key positions identified in the BOA SOW, as well as overseeing the execution of the overall effort. Management positions must indicate responsibility/role in responding to issues that may arise during execution of the effort.

(2) Identification of a quality control organization that is onsite but which operates independently by reporting directly to the corporate quality office.

Note: If the Offeror's Corporate Organizational Structure is depicted through charts, tables, and/or diagrams, appropriate identifiers/ markers/legends/keys must be provided to adequately demonstrate that the quality control organization reports directly to the corporate quality office and operates independently of the Project Management Office, the Project Manager, and/or any superintendents responsible for the direct oversight of individual orders.

(c) Resumes Provide resumes for each of the following key personnel which demonstrates proper licenses, certifications, and experience as described in the BOA SOW, Section 3.1.2.

(1) Contract/Program Manager

(2) Quality Control Manager

(3) Site Safety and Health Manager

(4) Design Program Manager

(5) Project Superintendent(s)

(6) Design Project Manager (if utilized)

(7) Construction Project Manager (if utilized) Staffing letters of intent are acceptable, but must still be accompanied by resumes showing necessary qualifications.

L.5.2.4 Experience/Past performance

(a) The Offeror's Experience Matrix must adhere to the following:

(1) Required File Name: OfferorName_Experience Matrix

(2) File Format: Fillable PDF

(3) COMPLIANCE REQUIREMENT: Failure to provide the Experience Matrix in the Government-provided format will render the Offeror's proposal non-compliant, and it will not be further evaluated nor considered for award of an executed BOA.

(b) The Offeror must provide its recent and relevant experience, as a measure of the likelihood to ensure proper execution of any orders awarded under this BOA.

(1) Experience shall be provided on the Experience Matrix. The Government does not require additional documentation for experience other than a completed Experience Matrix; additional documentation, if submitted, will not be evaluated by the Government.

(2) Offerors shall identify no more than five (5) recent and relevant construction projects, performed with three (3) years of the release of this solicitation. At least one of the contract references submitted must have been performed by the Offeror.

(3) In addition, provide up to three (3) recent and relevant construction projects performed by each of the teaming and significant subcontractors, performed within three (3) years of this solicitation.

(4) If the Offeror is relying upon a reference from its parent or an affiliate company to satisfy this requirement, in accordance with L.5.2.1(b)(1) and M.2.3(a)(1), the Offeror must explain how the resources of the parent or affiliate company will be utilized in performance of the proposed effort.

(5) If an Offeror identifies experience of another company/legal entity with a CAGE code different than its own (whether it be a parent company, an affiliate, or a company being proposed as a subcontractor), the Offeror shall certify that it has permission from an authorized agent of that other company to submit the contract reference information as part of the Offeror's Experience Matrix; said certification is provided by signing the applicable line.

(6) Recent is defined as a measure of time that has elapsed since the contract reference occurred. Recent is generally expressed as a time period during which contract references are considered relevant. For the purpose of this requirement, recent is any contract under which any performance, delivery, or corrective action has occurred within the following time standards: three (3) years prior to this BOA Invitation closing date, regardless of the award date.

(7) Relevant is defined as similar in scope and complexity to this effort, which are defined as follows:

- Scope: The type of requirements/tasks performed under the contract.

- Complexity: Two or more simultaneous efforts being performed within in the SAME functional area.

(c) Instructions for completing the Experience Matrix are as follows:

(1) Cover page - self-certification: If the contract reference identified at L.5.2.4(c)(4)(line 3) was performed by a company other than the Offeror (i.e. the company has a CAGE code different than the Offeror's CAGE code, whether it is a parent company, an affiliate, or a company being proposed as a subcontractor), the Offeror's authorized agent shall provide his/her signature certifying that the other entity granted the Offeror permission, either in writing or verbally, to submit the contract reference information as part of the Offeror's Experience Matrix.

(2) Line 1: The Offeror shall enter the name of the Prime Offeror submitting a proposal for a BOA and the respective CAGE Code, as identified in SAM. The CAGE Code consists of five (5) alphanumeric digits and does not begin with the letter O.

(3) Line 2: The Offeror shall enter the contractor's name (only name one) that performed the requirements of the contract number listed at line 3 and the respective CAGE Code, as identified in SAM (i.e. Parent Company, Affiliate Company, or Subcontractor). If the Prime Offeror performed the requirements of the contract number listed at line 3, enter N/A. The CAGE Code consists of five (5) alphanumeric digits and does not begin with the letter O.

(4) Line 3: The Offeror shall provide the recent contract number and program title which demonstrates recent and relevant experience to this BOA Invitation. Each contract reference provided must have been performed under Government (Federal, state, local) or commercial contracts. Please note that references provided on classified contracts cannot be verified, and will not be evaluated. The contract reference number shall fall under one of the three categories below:

- For services performed as a Prime contractor on a Government contract, enter one (1) recent Government contract number (and one (1) corresponding order number, if applicable, that best illustrates individual mission requirement) which demonstrated recent and relevant experience to this BOA Invitation for the Offeror or subcontractor; OR,

- For services performed as a Prime contractor on a private sector contract, enter one (1) recent and relevant private sector contract number which demonstrated recent and relevant experience to this BOA Invitation for the Offeror or subcontractor; OR,

- For services as a subcontractor on a Government contract or a private sector contract, enter one (1) recent and relevant subcontract number which demonstrated recent and relevant experience to this BOA Invitation for the Offeror or subcontractor (DO NOT enter the Prime Government contract number). Note: The contract number given for a subcontract contract reference is the private sector commercial contract number held between the subcontractor and the Prime, not the contract number between the Government and the Prime.

(5) Line 4: The Offeror shall enter the contract total dollar value in US dollars. If option periods are available, assume all option periods will be exercised and included in the contract total dollar value.

(6) Line 5: The Offeror shall enter the contract award date and period of performance, to include the contract end date for the contract number listed on line 3. Ongoing contracts must use contract completion date (assuming all option periods are exercised). The required format is MM/DD/YYYY; simply writing To Present is not acceptable. If line 6 indicates that the experience cited was gained as a subcontractor, only provide the Period of Performance end date for the work performed specifically by the contractor listed at line 2.

(7) Line 6: The Offeror shall select the appropriate box if the contractor listed on line 1 or 2 performed the work as a Prime Contractor or Subcontractor for the contract number listed at line 3.

(8) Line 7: If subcontractor is selected at Line 6, provide the name of the prime contractor the effort was awarded to.

(9) Line 8: The Offeror shall provide the customer name (requiring activity or prime contractor, if subcontractor indicated at line 6) and address.

(10) Line 9: The Offeror shall enter the applicable contracting official's name, telephone number and email address for the contract listed at line 3. The PCO must be able to verify the information provided for the contract. For a Government contract as a Prime, the POC shall be a Government Contracting Representative.

For a private commercial contract as a Prime, the POC shall be a representative of the entity with whom the private commercial contract terms were entered into. For a Government contract as a subcontractor, the POC shall be a representative of the Prime Contractor with whom the subcontractor terms were entered into; the POC cannot be a Government representative.

(11) Line 10: The Offeror shall enter the applicable Government or commercial activity technical representative, or COR, name, telephone number and email address for the contract listed at line 3. The POC provided should have direct knowledge of the work performed.

(12) Line 11: The Offeror shall enter examples of the tasks performed under the effort listed at line 3.

Examples should identify tasks relevant to the BOA SOW in order to assist the Government in determining the relevance of the cited effort (see definition at L.5.2.4(b)(2)). The Offeror may copy/paste directly from the contract documentation; however, note that this field is limited to 2,600 characters.

Section M - Evaluation Factors for Award

EVALUATION CRITERIA

M.1 EVALUATION METHODOLOGY & BASIS FOR EXECUTION OF A BOA

M.1.1 The Government will execute a BOA to any Offeror whose proposal complies with the BOA Invitation requirements and is determined to be Technically Acceptable.

M.1.2 Compliance Review: The Government will compare the Offeror's proposal to the ITO in order to perform a compliance review. Any Offeror's proposal determined non-compliant per the terms noted in the ITO will not be evaluated and will not be further considered for execution of a BOA. Only Offerors whose proposals are determined to be compliant will move to the Technical Factor evaluation process.

The Government reserves the right to waive the Compliance Review if it is in the Government's best interest.

M.1.3 JV Agreement The Government will verify the Offeror provided a signed, legal JV agreement, if applicable.

M.1.4 Technical Factor Evaluation

(a) Proposals determined to be compliant per the terms noted in the ITO will be evaluated for the technical factor based upon the criteria provided in M.2 below. Only compliant proposals determined technically acceptable will receive a BOA.

(b) The Government intends to execute BOAs based upon the content of initial proposals and without discussions with Offerors after receipt of those initial proposals; as such, an Offeror's initial proposal should contain sufficient information to satisfy the technical requirements.

(c) The Government does reserve the right, however, to enter into discussions with Offerors whose initial proposals are determined to be technically unacceptable if it is in the best interest of the Government to do so.

(1) If discussions are determined to be in the Government's best interest, the Government will only enter into discussions with those Offerors whose proposals do not contain significant informational deficiencies.

(2) The Government will not enter into discussions with Offerors whose proposals are determined to contain significant informational deficiencies; those Offerors will be precluded from receiving a BOA.

M.1.5 The Government will execute a BOA with any Offeror whose proposal complies with the BOA Invitation requirements and is determined to be Technically Acceptable.

M.1.6 As the BOA process (both the evaluation of proposals and the placement of BOAs), is not a competitive acquisition process, the source selection policies and procedures of FAR 15.3 do not apply.

M.2 Technical Factor M.2.1 The Technical Factor will be evaluated only on proposals that pass Compliance review.

M.2.2 Evaluation of the Technical Factor consists of an evaluation of the Offeror's proposed Technical Capability Statement (TCS); Bonding; Corporate Organizational Structure; and Experience.

The Offeror's Technical proposal will be evaluated on an Acceptable/Unacceptable basis. An Offeror must receive an acceptable rating in ALL evaluation criteria to receive an overall acceptable rating for the Technical Factor. The Technical Factor will be rated as follows:

- Acceptable: The proposal clearly meets the minimum requirements of the BOA Invitation.

- Unacceptable: The proposal does not clearly meet the minimum requirements of the…