Am 0002 - W9128F21R0013.pdf

W9128F21R0013

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to make edits to Section 00 22 00. Additionally, attachments for revised Section MATOC01_E-0001, and Sample Project Division 01 Specs (01 45 00.00 10 - Am 0002 and 01 30 00.24 - Am 0002) have been added to this amendment.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 37

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-Jan-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W9128F21R0013

X 9B. DATED (SEE ITEM 11)

05-Jan-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION

NO.

5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Jan-2021

CODE

U.S. ARMY CORPS OF ENGINEERS, OMAHA DIST

CONTRACTING OFFICE

1616 CAPITOL AVENUE

OMAHA NE 68102-4901

W9128F 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION 00 22 00 - SUPPLEMENTARY INSTRUCTIONS

The following have been modified:

SUBMISSION REQ AND EVAL

SECTION 00 22 00

SUPPLEMENTARY INSTRUCTIONS (SUBMISSION REQUIREMENTS AND EVALUATION)

1. CONTRACT INFORMATION

1.1. INDEFINITE DELIVERY TYPE CONTRACTS

The Government intends to issue an unrestricted solicitation and award a Multiple Award Task Order Contract (MATOC) for shared capacity of $400M to a target of five (5) contractors. Individual Task Orders will be solicited and competed within the MATOC pool. Task Orders under the MATOC will be Firm Fixed Price (FFP) task orders.

The base ordering period for this MATOC is four (4) years. There will be one (1) option ordering period of three (3) years, with a total ordering period up to seven (7) years from the date of contract award. In addition, a six (6) month option period is included if deemed necessary to exercise. The Government’s decision to exercise an option will be contingent upon satisfactory contractor past performance and an informal survey of current market conditions. The decision to exercise the option is at the discretion of the Government. The minimum guarantee amount for this MATOC (to include all option periods) is $2,500.00.

1.2. SCOPE OF WORK

Projects will vary in size, complexity, and location, and will require a high level of technical expertise and a high level of quality control to ensure all airfield paving construction projects meet technical standards and provide long-lasting airfield paving.

Work contemplated under this MATOC may include construction and/or full depth repair of both concrete and asphalt airfield pavements. Work may include related/ancillary systems such as minor pavement repairs, airfield lighting systems, NAVAIDs, storm water systems, aircraft arresting systems, and other utility systems located within the airfield environment. Work will conform to Department of Defense (DoD) requirements via task order specific versions of the Unified Facilities Guide Specifications (UFGS). Work will occur on an active airfield environment, such as runways, taxiways, and aprons, requiring phasing and working around active aircraft operations.

1.3. PROJECT LOCATIONS

Projects may occur anywhere in USACE Northwestern Division’s military boundaries (including Washington, Oregon, Idaho, Montana, Wyoming, Colorado, North Dakota, South Dakota, Nebraska, Kansas, Minnesota, Iowa, Missouri, Michigan and Wisconsin). The Offeror shall be prepared to respond to any location as defined above.

2. WHO MAY SUBMIT

This solicitation is unrestricted and is open to all potential Offerors.

All Offerors must be registered in the System for Award Management (SAM) in the same manner as they are proposing for this solicitation.

The Primary North American Industry Classification System (NAICS) code for this solicitation is 237310, with a size standard for small business of $39.5 million dollars.

Proposals submitted must be sufficiently detailed to allow for an effective and equitable evaluation by the Government. There will be no public proposal opening. Proposals submitted will become, upon receipt, the property of the U.S. Government and will not be returned. After evaluation of proposals, electronic copies will be retained for the official paperless contract file. All other copies will be destroyed or forwarded to the Field and Areas Offices in support of their contract administration functions.

3. PROPOSAL SUBMISSION

3.1. SUBMISSION INSTRUCTIONS

In an effort to reduce paperwork and cost, all proposals shall be submitted electronically. All submissions will be in Adobe PDF format with Optical Character Recognition (OCR) applied to all documents that will enable word searches to be conducted using Adobe-compatible PDF software. The two (2) volumes listed below shall be submitted as SEPARATE files via email to the Government points of contacts below. Offerors may use compression utilities such as 7-Zip, WinZip or PKZip to reduce file size and facilitate transmission. Offerors are encouraged to send both files in the same email transmission, if possible.

Government Point of Contacts:

1. Ms. Ericka Collins, Ericka.T.Collins@usace.army.mil, Phone – 402-995-2116

2. Mr. Tyler Hegge, Tyler.Hegge@usace.army.mil, Phone – 402-995-2048

For the purposes of determining whether the proposal was received “late” in accordance with FAR 15.208, the date and time the file(s) are received via email will be the time and date the Government received the proposal. Do not assume that electronic communication is instantaneous. Please make allowances for delays in transmittal.

Electronic Proposals shall be received via email No Later Than (NLT) the date and time indicated in Block 13 of the SF 1442 for this solicitation or as identified in subsequent amendments. (Note: Files or multiple files combined that are larger than 35MB in one email will likely not be received).

The Government is not be responsible for proposals delivered to any location or to anyone other than those designated to receive proposals on its behalf. The Offeror is responsible for ensuring that the proposal is submitted to reach the designated recipient and is responsible for allowing sufficient time for the proposal to be received in accordance with the information provided.

Failure to submit a complete proposal IAW instructions and requirements may result in the entire offer being rejected.

3.2. SUBMISSION DEADLINE

Electronic proposals shall be received via email Not Later Than (NLT) the time and date specified in Block 13 of Standard Form 1442 (Section 00 10 00, Page 1), unless extended via amendment.

4. PROPOSAL REQUIREMENTS AND FORMAT

4.1. PROPOSAL FORMAT

1. Submit the following two files, titled in the format shown below:

mailto:Ericka.T.Collins@usace.army.mil mailto:Tyler.Hegge@usace.army.mil

a. W9128F21R0013_COMPANY NAME _VOLUME_I_FACTORS_1-5

b. W9128F21R0013_COMPANY NAME _VOLUME_II_REQUIRED_DOCS

2. Proposal Characteristics

a) VOLUME I, FACTORS 1-5 (File #1)

1) Contents of this file shall be arranged in the following sequence:

Cover Letter (not to exceed two (2) pages) Table of Contents FACTOR 1: Previous Experience FACTOR 2: Technical Approach to Sample Project FACTOR 3: Past Performance FACTOR 4: Management Approach FACTOR 5: Small Business Participation Commitment Document

2) Component requirements:

(a) Cover Letter: The cover letter shall contain:

Solicitation number.

CAGE Code, DUNS Number for the Offeror, and Tax Identification Number.

Name, title, address, email, and telephone number of the Offeror.

Names, titles, emails, and telephone numbers of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this RFP.

Name, title and signature of the person authorized to sign the proposal.

Name, title, email and phone number of an alternate point of contact for correspondence.

A statement specifying agreement with all terms, conditions and provisions included in the RFP.

(b) Table of Contents: The table of contents shall include all section headings and subheadings: worded exactly as they appear in the proposal.

(c) The Cover Letter and Table of Contents are not included in the page count.

3) Page limitations for Factors 1-5 are shown in Table 1, below:

Table 1 - Proposal Format -- Volume I: Technical Proposal and Past Performance

EVALUATION

FACTOR TITLE PAGE

LIMITATION

1 Previous Experience 8 12 (Am 0002) 2 Technical Approach to the Sample Project 25 and 2 11”x17” pages for schedule

3 Past Performance No page limitation 4 Management Approach

5 Small Business Participation Plan 20

4) All text shall be at least 10 pt. font and easily read. All text shall be typed and single-spaced. Each page shall be 8-1/2 by 11 inches, with the exception of the single page organizational chart required for Factor 3, which may be 11x17 inches.

5) Each page should contain the following information in the top and bottom margin. Exact placement (center, off-center, left, right, etc.) and sequence of presentation is at the discretion of the Offeror.

a. Page number. Pages for each factor should be separately and sequentially numbered (i.e., the first page submitted for evaluation of each factor should be “Page 1”). This includes all pages for Factor 2; while there is no page limitation for Factor 3, the page numbers are needed by the Government for reference during the evaluation and selection process.

b. Factor number and title. For example, “Factor 1 – Previous Experience.”

c. Solicitation Number

d. Company name of Offeror and (at the Offeror’s discretion) the company logo

e. Disclosure information can be placed in the bottom margin. (Am 0002)

6) Top, left, right, and bottom margins should be no less than 1”. No information should be included in any margin, except as required in Paragraph 4, above. Past Performance evaluations are exempt from this requirement.

7) For Factors 1, 2, 4, and 5 pages that exceed the page limitations for any factor will not be reviewed and the information contained on those pages will not be considered for evaluation. Note that including required information on a page that exceeds any of these limitations, and which is therefore not reviewed, may cause a proposal to receive a deficiency for a factor. Further, an Offeror shall not include information required in Factors 1, 2, 4 and 5 in the information for Factor 3 to circumvent the page count(s).

8) Information contained within margins, other than what is required by the Government, will not be reviewed. Page limitations are per factor, i.e., an Offeror may not reduce the page count for one factor in order to submit additional pages for another factor.

b) VOLUME II, COST INFORMATION AND REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMET TO OFFERORS (File #2)

9) Submit the following items in the sequence listed below:

Cover Letter (not to exceed two (2) pages) Table of Contents Completed SF 30 or acknowledgement of amendment(s) on SF 1442 (if applicable) Tabs 1-7 as listed in Table 2: Proposal Format

10) Component requirements:

(a) Cover Letter: The cover letter should contain:

Solicitation number.

Name, title, address, email, and telephone number of the Offeror.

Names, titles, emails, and telephone numbers of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this RFP.

Name, title and signature of the person authorized to sign the proposal.

A statement specifying agreement with all terms, conditions and provisions included in the RFP.

(b) Table of Contents: The table of contents will include all section headings and subheadings: worded exactly as they appear in the proposal.

(c) SF 1442: The SF 1442 shall be completed and signed by a person authorized by the Offeror.

(d) Completed SF 30: Offerors shall submit acknowledgement of all amendments to the

RFP, either on each Standard Form 30 or on the SF1442.

(e) Submission of completed Tables 1 through 4 from Section 00 10 00 (Tab 2) and sample project pricing.

(f) Contractor Team Arrangement Requirements: For Contractor Team Arrangements, including Joint Ventures, submit the information required by Paragraph 6 “Contractor Team Arrangements”.

11) Page limitations for Volume II, Tab 4 are shown in Table 2, below:

Table 2 - Proposal Format -- Volume II: Cost Information and Representations, Certifications, and Other Statements to Offerors

VOLUME II DESCRIPTION PAGE

LIMIT

Tab 1 SF 1442 - Solicitation, Offer, and Award N/A

Tab 2 Section 00 10 00 – Pricing (Fully Burdened Labor Rates - FFP) N/A

Tab 3 Representations, Certifications and Other Statements of Offerors N/A

Tab 4 Price Proposal for the Sample Project 20

Tab 5 Contractor Team Arrangements (if applicable) N/A

Tab 6 Company Bonding Letter N/A

Tab 7 Small Business Subcontracting Plan (Only Large Business Firms) N/A

5. INQUIRIES/QUESTIONS

Prospective Offerors shall submit contracting and technical inquiries and questions concerning this solicitation document via Bidder Inquiry in ProjNet at www.projnet.org/projnet. Please refer to Section 00 21 00 of this solicitation for Bidder Inquiry instructions.

http://www.projnet.org/projnet

***Please Note: Offerors shall only submit one question per inquiry, i.e., each query should have a unique corresponding ProjNet bidder inquiry number assigned. All inquiries containing multiple questions shall be rejected.

The Offeror is permitted to submit multiple inquiries.***

6. CONTRACTOR TEAM ARRANGEMENTS

6.1. CONTRACTOR TEAM ARRANGMENTS OTHER THAN JOINT VENTURE/MENTOR-

PROTÉGÉ

Requirements:

All Offerors proposing a team arrangement other than a Joint Venture/Mentor-Protégé, shall submit the following information:

a. A listing of the team arrangement members’ corporate name (no abbreviations), address, point of contact, phone number, DUNS Number, and Cage Code.

b. A copy of the signed team arrangement agreement or binding letter of commitment between each team member. All team arrangement agreements and letters of commitment shall:

(1) Clearly identify the expected relationship, role and responsibility between the firms, Prime Contractor, and of the subcontractor or other entity (type and proportion of work to be performed);

and

(2) Be signed by the appropriate individual(s) of each firm.

6.2. JOINT VENTURE TEAM ARRANGEMENTS (INCLUDING MENTOR-PROTÉGÉS)

No contract may be awarded to a Joint Venture/Mentor-Protégé that is not registered in the System for Award Management (SAM) database. The Joint Venture/Mentor-Protégé must have its own registered Data Universal Numbering System (DUNS) number. Any Joint Venture/Mentor-Protégé agreement that is required to be approved by the Small Business Administration (SBA) shall be approved in accordance to the applicable Code of Federal Regulations (CFR). If the applicable requirements are not met prior to the due date for the proposals, the proposal will be rendered unawardable.

6.2.1 In the cover letter of your proposal, provide the complete names, addresses, and phone number of the firms comprising the Joint Venture/Mentor-Protégé.

6.2.2 A copy of the Joint Venture/Mentor-Protégé agreement.

6.2.3 Signature requirements: SF 1442, SOLICITATION, OFFER, AND AWARD, Block 20 requires the name and title of a person authorized to sign the offer for the Joint Venture/Mentor-Protégé be provided. In the case of a Joint Venture/Mentor-Protégé, subject Standard Form shall be signed by the principal representative of the Joint Venture/ Mentor-Protégé (or the alternate principal representative, if the principal representative is unavailable).

6.2.4 In addition to the requirements stated above, and to assure a single point of contact for resolution of contractual matters and payments, the Offeror shall submit a certificate signed by each participant in the Joint Venture containing the following statement:

“The parties hereto expressly understand and agree as follows:

1. (Name, title, and company) is the principal representative of the Joint Venture. As such, all communications regarding the administration of the contract and the performance of the work thereunder may be directed to him or her. In the absence of (same name, title, and company), (enter name, title, and company of alternate) is the alternate principal representative of the Joint Venture/Mentor-Protégé. These individuals have authority to sign on behalf of the Joint Venture/Mentor-Protégé.

2. Direction, approvals, required notices, and all other communications from the Government to the Joint Venture/Mentor-Protégé, including transmittal of payments by the Government, shall be directed to (enter name, title, and company of principal), principal representative of the Joint Venture/Mentor-Protégé.”

NOTE: Provide telephone numbers and email addresses for the points of contact listed in the above statement.

6.3. INTEGRITY AND VALIDITY OF CONTRACTOR TEAM ARRANGEMENTS

The Contracting Officer will recognize the integrity and validity of contractor team arrangements; provided that the arrangements are identified and company relationships are fully disclosed and validation of formal agreements and relationships (i.e., Mentor-Protégé agreements, Joint Ventures, partnerships, etc.) are provided in the offer and submitted with the proposal responding to the solicitation. Nothing in the solicitation authorizes contractor team arrangements in violation of antitrust statutes or limits the Government’s rights to:

a. Require consent to subcontracts (see FAR Subpart 44.2);

b. Determine, on the basis of the stated contractor team arrangement, the responsibilities of the Prime Contractor (see FAR Subpart 9.1);

c. Provide to the Prime Contractor data rights owned or controlled by the Government;

d. Pursue its policies on competitive contracting, subcontracting, and component breakout initial production or an any other time; and

e. Hold the Prime Contractor fully responsible for contract performance, regardless of team arrangement between the Prime Contractor and its subcontractors.

7. BASIS OF AWARD

The agency will use the Selection Procedures authorized by FAR Part 15.

Selection will be based on evaluation of technical factors, past performance, small business participation, and price.

There are five non-price factors:

FACTOR 1: Previous Experience FACTOR 2: Technical Approach to Sample Project FACTOR 3: Past Performance FACTOR 4: Management Approach FACTOR 5: Small Business Participation Plan

The Government intends to evaluate proposals and award contracts without conducting discussions with Offerors.

However, in the event that discussions are necessary, the PCO will establish a competitive range with approval from the Source Selection Authority (SSA). If the PCO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a price and technical standpoint.

The Government intends to award a target of five (5) contracts. However, the Government reserves the right to award less than or greater than five (5) contracts under this MATOC to the Offerors whose proposal offers the best value to the Government.

8. RELATIVE IMPORTANCE OF EVALUATION FACTORS

Technical evaluation factors are listed in descending order of importance. All technical evaluation Factors other than cost or price, when combined, are significantly more important than cost or price.

Table 3 – EVALUATION FACTORS

FACTOR DESCRIPTION

Factor 1 Previous Experience Factor 2 Technical Approach to Sample Project Factor 3 Past Performance Factor 4 Management Approach Factor 5 Small Business Participation Plan

9. SOURCE SELECTION PROCESS

All offers received in response to this solicitation will be evaluated in accordance with FAR Part 15.3, DoD Source Selection procedures, and other Army Source Selection guidance. The principal objective of this process is to select responsible Offerors who submit the offers that represents the best value to the Government, technical factors and price considered.

10. EVALUATION CRITERIA

10.1 COMBINED TECHNICAL/RISK RATINGS.

The evaluation ratings for Technical Factors 1, 2, and 4 will be on an adjectival basis in conjunction with the identified strengths, weaknesses, and deficiencies of the proposal. The Source Selection Team will use a combined technical/risk rating system that includes consideration of risk in conjunction with the strengths, weaknesses, and deficiencies in determining technical ratings. Combined technical/risk ratings are listed in Table 4. The Combined technical/risk ratings will be used to evaluate Factor 1 Previous Experience, Factor 2 Technical Approach to Sample Project, Factor 4 Management Approach.

Table 4 - Combined Technical/Risk Ratings

Color Rating Description

Blue Outstanding Proposal indicates and exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low.

Purple Good Proposal indicates a thorough approach and understanding of the requirements and contains at least one strength, and risk of unsuccessful performance is low to moderate.

Green Acceptable Proposal meets requirements and indicates an adequate approach and understanding of the requirements, and risk of unsuccessful performance is no worse than moderate.

Yellow Marginal Proposal has not demonstrated an adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high.

Red Unacceptable Proposal does not meet requirements of the solicitation, and thus, contains one or more deficiencies, and/or risk of unsuccessful performance is unacceptable. Proposal is unawardable.

Strengths, Significant Strengths, Weaknesses, Significant Weaknesses, and Deficiencies are defined as follows:

Strength: An aspect of an Offeror’s proposal that has merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance.

Significant Strength: An aspect of an Offeror’s proposal that has appreciable merit or appreciably exceeds specified performance or capability requirements in a way that will be appreciably advantageous to the Government during contract performance.

Weakness: A flaw in the proposal that increases the risk of unsuccessful contract performance.

Significant Weakness: A flaw in the proposal that appreciably increases the risk of unsuccessful contract performance.

Deficiency: A material failure of a proposal to meet a Government requirement or a combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level.

10.2 PAST PERFORMANCE RATING

The Past Performance evaluation factor is an assessment of the Offeror’s probability of meeting the Solicitation requirements. The Past Performance evaluation considers each Offeror's demonstrated recent and relevant record of performance in supplying services that meet the contract’s requirements. The currency and relevance of the information, source of the information, context of the data, and general trends in the Offeror’s past performance shall be considered. There are two aspects to the Past Performance evaluation, Relevancy and Contractor Performance, which are combined to establish one performance confidence assessment rating for each Offeror. The elements are described below:

a. Relevancy. The first aspect of the Past Performance evaluation is to determine how recent and relevant previous experience accomplished by the Offeror is to the anticipated work to be accomplished under this MATOC.

Relevancy is defined as similarity of anticipated work effort contemplated items stated within this solicitation such as: types of projects, dollar value, contract type, and stakeholder(s). With respect to relevancy, more relevant Past Performance will typically be a strong predictor of future success.

Relevancy is not a separate proposal rating but is used to develop an overall Past Performance rating. The four levels of relevancy ratings are:

Table 5 - Past Performance Relevancy Rating

Adjectival Rating Description Very Relevant Present/Past Performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/Past Performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant Present/Past Performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant Present/Past Performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

b. Contractor Performance. The second aspect of the Past Performance evaluation is to determine how well the contractor performed on the contracts. The Past Performance evaluation performed in support of a current source selection does not establish, create, or change the existing record and history of the Offeror’s Past Performance on previous contracts; rather, the Past Performance evaluation process gathers information from stakeholders on how well the Offeror performed those previous contracts.

After evaluating relevancy and reviewing contractor performance, a Performance Confidence Assessment rating will be determined. In conducting a performance confidence assessment, each Offeror shall be assigned one of the following ratings:

Table 6 – Past Performance Confidence Rating

Adjectival Rating Description Substantial Confidence Based on the Offeror’s recent/relevant performance record, the Government has a high expectation that the Offeror will successfully perform the required effort.

Satisfactory Confidence Based on the Offeror’s recent/relevant performance record, the Government has a reasonable expectation that the Offeror will successfully perform the required effort

Neutral Confidence No recent/relevant performance record is available, or the offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned. The offeror may not be evaluated favorably or unfavorably on the factor of past performance.

Limited Confidence Based on the Offeror’s recent/relevant performance record, the Government has a low expectation that the Offeror will successfully perform the required effort.

No Confidence Based on the Offeror’s recent/relevant performance record, the Government has no expectation that the Offeror will be able to successfully perform the required effort.

10.3 CPARS AND CCASS RECORDS

Contractor Performance Assessment Reporting System (CPARS)/ Construction Contract Administration Support System (CCASS) records may be obtainable by Offerors using one of the following methods:

(1) Accessing past performance information directly from CPARS at http://www.cpars.gov for CCASS completed before 27 June 2014 and for merged CPARS completed after 1 July 2014. CPARS is an electronic repository of performance information collected by all the major federal performance reporting systems and can be accessed at https://www.cpars.gov.

http://www.cpars.gov/ https://www.cpars.gov/

The Past Performance Information Retrieval System (PPIRS.gov) has officially been retired to conclude its merger with the Contract Performance Assessment Reporting System (CPARS.gov). Data from PPIRS has been merged into CPARS.gov, making CPARS the official system for past performance information.

Users will now have one location and one account to perform all functionality. Federal users with a Common Access Card (CAC) or a Personal Identity Verification (PIV) card or a contractor with a Public Key Infrastructure (PKI) certificate, will log in using the Accept/Login with PKI button. Federal users who don’t use PKI/PIV or a contractor who doesn’t have a PKI certificate will log in using their email address and a password. Upon using CPARS.gov for the first time, users are required to reset their password to securely log on to the merged system. To help prevent unauthorized access, a one-time access code is needed when using a password to log in.

(2) Contact your government point of contact for the project you referenced, and ask them if they can send you a copy, or -

(3) Apply for Contractor access on CPARS web page at http://www.cpars.gov by selecting “Access Info”, then under “I am an Entity User and I will be…” click on “Reviewing Records and Managing Users” and then request Corporate Senior Contractor Representative Access.

10.4 SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT

The Small Business participation factor (Factor 5) will be assigned a rating based on the Table 7, below:

Table 7 – Small Business Commitment Assessments Rating Adjectival Rating Description Blue Outstanding Proposal indicates an exceptional approach and understanding of the small business objectives.

Purple Good Proposal indicates a thorough approach and understanding of the small business objectives.

Green Acceptable Proposal indicates an adequate approach and understanding of small business objectives.

Yellow Marginal Proposal has not demonstrated an adequate approach and understanding of the small business objectives.

Red Unacceptable Proposal does not meet small business objectives.

11. VOLUME I - TECHNICAL PROPOSAL AND PAST PERFORMANCE

Offerors shall submit one file labeled as Volume I with tabs (electronic bookmarks or equivalent) to identify the factors shown below. All required information for each identified factor must be contained within that specified Tab.

11.1 FACTOR 1. Previous Experience

11.1.1 Submit four (4) projects that best demonstrate your firm’s experience on projects that meet the requirements described below. Evidence that the requirements below have been met shall be demonstrated in a detailed narrative.

A checked box, bullet list, or other summary/graphic will not be accepted as evidence that a requirement has been met. For example, a bullet with the comment “designed to support turbine engine aircraft” is insufficient. Instead, the Offeror shall describe the type of aircraft the airfield supported, which must include turbine engine aircraft. The Government may disregard any claims not adequately substantiated by the narrative.

11.1.2 Previous project examples submitted for this factor shall have been awarded to the Offeror for this solicitation as the Prime Contractor. If the Offeror is a newly formed JV, previous projects awarded to either of the companies forming the JV are acceptable, so long as the company was either the Prime Contractor on the previous project, or was a member of a JV which was the Prime Contractor.

If the Offeror forms a Series LLC for this Solicitation, only the Managing Partner’s previous experience can be used to demonstrate previous experience.

The table below provides example scenarios based on the requirements above.

Scenario Examples Previous Project

Experience Qualifies for Evaluation for

Factor 1 (if all other requirements are met)?

1 Previous project was awarded to Company X only. Company X is proposing as the Offeror for

W9128F-19-R-00xx and has signed the SF 1442 for W9128F-20-R-00xx.

Yes

2 Company Y has formed a JV with Company Z (forming Company “YZ”). Previous project was awarded to Company Y only. Company YZ is proposing as the Offeror for W9128F-19- R-00xx and has signed the SF 1442 for W9128F-20-R-00xx.

Yes

3 Company Y has formed a JV with Company Z (forming Company “YZ”). Previous project was awarded to JV Company YZ. Company YZ is proposing as the Offeror for W9128F-19- R-00xx and has signed the SF 1442 for W9128F-20-R-00xx.

Yes

4 Previous Project was awarded to Company “AY,” a JV composed of Company A (not an Offeror for RFP W9128F-19-R-00xx) and Company Y. Company Y has formed a JV with Company Z (forming Company “YZ”). JV Company YZ is proposing as the Offeror and has signed the SF 1442 for W9128F-20-R-00xx.

Yes

5 Company Y has formed a JV with Company Z (forming Company “YZ”). Company YZ is proposing as the Offeror for W9128F-20-R-00xx and has signed the SF 1442 for W9128F-20- R-00xx. Company Y performed work on the previous project but was not the Prime Contractor for the previous project (either singly or as a member of a JV).

No

6 Company X is proposing as the Offeror for W9128F-20-R-00xx and has signed the SF 1442 for W9128F-20-R-00xx. Company X will use Company R as a teaming member/subcontractor, but Company R is not part of a JV with Company X for W9128F-20-R-00xx. The previous project was awarded to Company R as a Prime Contractor (singly or as a member of a JV), but not Company X (singly or as a member of a JV).

7 Company Y has formed a JV with Company Z (forming Company “YZ”). Company YZ is proposing as the Offeror for W9128F-20-R-00xx and has signed the SF 1442 for W9128F-20- R-00xx. Company YZ will use Company R as a teaming member/subcontractor but Company R is not part of the JV. The previous project was awarded to Company R as a Prime Contractor (singly or as a member of a JV), but not to Companies Y or Z (singly or as a member of a JV).

11.1.3. Additional Requirements:

11.1.3.1 General Requirements

All project examples should meet the following criteria.

1. Primary scope of work was airfield design-bid-build paving as specified in section 01 11 00 (not design-build projects). Projects involving installation of only the sub-base materials, crack repair, patching, seal coats, or non-pavement items will not be considered acceptable.

2. Contract must have been awarded to your firm, or as one of the partners of a Joint Venture, as the Prime Contractor

3. The largest portion of the paving on the Airfield Paving construction project, either PCC or Asphalt, must have been self-performed by the Offeror, and not subcontracted or performed by a teaming partner

4. All work was performed at a Department of Defense (DoD) airfield, or a commercial airfield/airport that required and utilized FAA Advisory Circular (AC) specifications.

5. Projects shall be 100% complete prior to the date this RFP was issued.

6. Each project must have been continuously performed under a single stand-alone contract or under a single task order under an IDIQ contract.

7. Pavement was designed to support turbine engine aircraft.

8. All projects submitted must have been completed no more than 10 years before the issuance of this RFP.

9. All projects submitted should have a contract award amount of at least $5M.

11.1.3.2 Special Requirements

The four (4) submitted project examples shall should (AM0001) collectively satisfy all the following special requirements. A single project may be used to meet more than one special requirement.

1. Construction of rigid pavements with thicknesses of 12 inches or greater.

2. Construction of flexible pavements with a thickness of 4 inches or greater, placed in multiple lifts.

3. Construction of airfield lighting systems.

4. Construction of airfield subgrade utilities.

5. Construction of airfield pavement markings.

6. Work included airfield demolition.

7. Minimum placement amount of 30,000 CY of Portland Cement Concrete (PCC).

8. Minimum placement amount of 10,000 tons of Asphalt Cement Concrete (ACC).

9. Minimum of 2 DoD projects.

11.1.3.4. Format

Offerors shall use the following format for each submitted project:

1. Descriptive project title

2. Project location

3. Contract/Task Order Number

4. Contract award amount

5. Total contract cost, to include all modifications, equitable adjustments, or other increases/decreases, and an explanation of the cost changes.

6. Total duration of project (from award to contract completion)

7. Dates:

a. award

b. notice to proceed

c. beneficial occupancy/customer acceptance

d. contract completion

8. Detailed narrative of the work performed. This narrative shall clearly demonstrate that all General and Special requirements, identified above, are met or exceeded.

9. A Project Point of Contact (POC) and one alternate Project Point of Contact involved with the project. The POCs shall be a representative of the end user, not affiliated with the Offeror. POC information shall include:

a. Name

b. Job title

c. Employer/Duty Station

d. Work address

e. Telephone

f. E-mail address

11.1.3.5. Evaluation Criteria:

Strengths or Significant Strengths may be given the following:

• PCC pavement placed totaled at least 10,000 cubic yards for each project presented.

• ACC pavement totaled at least 2,000 tons for each project presented.

• All projects included full depth rehabilitation or new construction of a runway at least 8,000’ in length.

• All projects were performed for DoD and utilized UFGS 01 45 00.00 10, UFGS 32 12 15.13, UFGS 32

13 11, UFGS 32 13 14.13 as applicable to the projects.

• One or more project examples had an award value of $30M or more (only one strength will be given, regardless of the number of projects that meet this criteria).

• Any other aspect of a proposal that the Government determines increases the likelihood of successful contract performance.

Weaknesses or Significant Weaknesses may be given for the following:

• The contract was awarded for less than $5M.

• Omission or incompleteness of any requested information that is not otherwise stated as a deficiency.

• Any other aspect of a proposal that the Government determines increases the risk of unsuccessful contract performance.

Deficiencies shall be given for the following:

• Submission of fewer than four (4) project examples that meet both the “general” and “special” requirements.

• Any project submitted was completed more than 10 years before the issuance of this RFP.

• Any project submitted fails to meet the General Requirements described above.

• Failure to include projects that collectively satisfy all Special Requirements described above.

• Any other material failure of a proposal to meet a Government requirement or a combination of significant weaknesses in a proposal increasing the risk of unsuccessful contract performance to an unacceptable level.

11.2 FACTOR 2. Technical Approach to the Sample Project

11.2.1 TECHNICAL EXECUTION OF THE SAMPLE PROJECT

Based on your understanding of the RFP requirements, describe the technical approach you will take to address the unique challenges, opportunities, and constraints inherent to this project (i.e. work delays, schedule phasing, working on an active runway, equipment height restrictions, etc.).

a. Narrative Present a Work Breakdown Structure (WBS) narrative to describe your technical solution for this project, specifically citing the process and major equipment used for construction of airfield pavement, discussion of the batch plant required to produce an acceptable paving mixture for the project, how subcontractors will be managed, how supplies and materials will be managed (i.e. source and location of all aggregates for PCC and Asphalt proposed for use in this project), schedule development and methods to be utilized and to keep the project on schedule. Address mitigation of potential delays due to unforeseen conditions and methods to recover time to complete the scheduled work within the period of performance. Unforeseen site condition for evaluation found in the bullet below this paragraph. Proposed batching, transport, equipment, and construction shall be pursuant to the requirements of Section 32 13 14.13 CONCRETE PAVING FOR AIRFIELDS AND OTHER HEAVY-DUTY PAVEMENTS and Section 32 12 15.13 ASPHALT PAVING FOR AIRFIELDS of the specifications.

• The unforeseen condition to be addressed is the presence of reinforcing steel in all the PCC pavement scoped for removal and replacement. Reinforcement discovered during demolition of the pavement was #5 deformed reinforcing steel, located mid-span, spaced 12” O.C. in both directions.

The narrative must address the following primary construction work elements as a minimum:

1. Airfield Paving: Offeror’s construction execution approach related to Airfield Paving and include the following:

a. Asphalt and PCC Batch Plant:

i. Plant locations. Identify the haul time from the placing site.

ii. Obtaining applicable permitting.

iii. Stockpile management.

iv. Plant capabilities to include production rate, control system, weight measuring systems, storage bins, and aggregate moisture content monitoring.

v. Plant certification requirements/procedures.

vi. Validated laboratories. Describe the process and timeline for validation of proposed laboratories, as well as all testing to be performed in each laboratory. Provide Material Testing Center (MTC) validation letter(s) for the proposed laboratories.

b. Equipment and Construction. Provide a description of the construction equipment, capabilities, and method in which the equipment will be utilized on the project in accordance with the technical specifications. At a minimum, address the following:

i. Demolition – Equipment and methods for demolition of existing asphalt and PCC, specifically for demolition near existing pavements to remain, or appurtenances (i.e. inlets, observation risers, lights, hydrant pits), and management of rubble millings/spoils and disposal.

ii. Subgrade, subbase, base course, and drainage layer – Equipment and methods for stockpile management, hauling, water distribution, compaction, and proof rolling. Include methods to evaluate and address unstable subgrade soils.

iii. Prime and Tack Coats.

iv. Asphalt – Equipment and methods for stockpile management, hauling, material transfer, paving, compaction, joint construction (Asphalt-PCC interface), and grooving. Provide separate discussions of compaction methods for 1) the main mat, 2) cold joints, and 3) Asphalt-PCC joints.

v. PCC – Equipment and methods for concrete mixing/transport, transfer and spreading, paving, finishing, texturing, curing, sawing, and pavement protection. Provide summary calculations that demonstrate the plan will comply with minimum paving speed requirements and overall production rates support the proposed schedule.

vi. Diamond Grinding – Both in areas displaying smoothness or elevation issues, and at the PCC- Asphalt joint interface.

vii. Joint Seals.

viii. Pavement markings.

2. Site/Civil Construction: Provide a description of the construction methods and procedures showing how the work will be accomplished. The Construction Plan shall, address the following:

a. Unsuitable soils

b. Site grading and drainage

c. Storm water systems

3. Airfield Electrical Construction: The narrative shall describe the Contractor’s construction approach related to the airfield electrical demolition and construction requirements for lighting, NAVAIDs, and lighting vault work. At a minimum include approach lighting systems, PAPIs, runway/taxiway edge lights, and signs. Include duct(bank) installation, foundations, in-pavement installation, and vault modifications as appropriate. Describe coordination of all in-pavement/under-pavement electrical features and pavement construction activities.

4. Airfield Construction Safety: Offeror shall submit a description of methods to ensure safety to active aircraft operations and contractor’s personnel. At a minimum, address the following:

a. Compliance with and required temporary deviations to airfield criteria such as imaginary surfaces, clear zones, instrument landing system critical areas, controlled movement areas, displaced thresholds, etc.

b. Foreign Object Damage (FOD) Prevention

c. Dust prevention

d. Jet blast impacts to construction operations

e. Temporary lighting, markings, signage, and barricades

11.2.2 SCHEDULE

11.2.2.1 Utilizing the Work Breakdown Structure from the Sample Project, provide a Major Activities Bar Chart and a detailed narrative that identifies all milestones and durations corresponding to the three project stages (A, B and C) detailed below. The schedule shall present the requirements to complete all work required under the RFP. The contractor should specifically identify issues that impact schedule or durations. The bar chart will not be included in the overall page count of each proposal, but is limited to 2 pages in length, and may be submitted in an 11-inch x 17-inch format. It must include all milestones and durations, to include:

i. All necessary permits, licenses, and certificates

ii. Site specific contractor management plans

iii. Key Work Breakdown Structure (WBS) activities

iv. Long lead procurements (i.e. Airfield Paving Asphalt job mix formula and Portland Cement Concrete

(PCC) Mix Design, and Airfield Lighting Equipment)

v. Critical path, starting with award and ending at project closeout

vi. Predecessor, Concurrent and Successor activities

Activity information shall be provided for each of the following Project Stages:

A- Stage 1. Preconstruction

a) Notice to Proceed (NTP)

b) Mutual Understanding Meeting (TSC)

c) Preconstruction Meeting

d) Pre-Construction Submittals (Demolition Plan, Diamond Grinding Plan, PCC Proposed

Techniques, Asphalt Quality Control Plan, Asphalt Placement Plan)

e) Mix Design Development

f) Batch Plant Erection and Utilities

g) Batch Plant Inspection and Report

h) Batch Plant Uniformity

i) Slip-Form Paver Inspection and Report

j) TSC Airfield Paving Workshop (3-day)

B- Stage 2. On-Site Construction

a) Mobilization

b) Displaced Threshold and Runway Closures

c) Demolition

d) Test Sections (PCC and Asphalt)

e) Production Paving Lots (Lanes)

f) Paving Lot Reports

g) Pre-Final Inspection

h) Punch List

C - Stage 3. Post-Construction

a) Final Inspection

b) Demobilization

c) Construction Completion Date

d) Beneficial Occupancy Date (BOD)*

e) Administrative Closeout (As-builts / O&M Manuals)

* “BOD” shall be the anticipated construction completion date plus 30 calendar days.

11.2.2.2 Phased Construction: Offeror’s construction approach related to the phasing requirements for demolition and construction shall be provided in a narrative and keyed to the on-site construction schedule. Include detailed description demonstrating procedures to establish displaced thresholds, transition between phases, and return to full operations in order to minimize the time required for full runway closures. Include discussion of any temporary lighting, markings, and signage as well as preliminary activities to transition between phases.

For scheduling purposes assume the Base X task order award will be executed on 29 OCT 2021 with NTP issued 3 weeks later.

11.2.3 OFFEROR’S KEY PROJECT PERSONNEL PROPOSED FOR THE SAMPLE PROJECT

In this Tab, the offeror shall provide resumes for key construction personnel assigned to this project. Resumes shall be submitted for the personnel roles shown in this paragraph.

The first page of this Tab shall include a one-page listing of the names of the construction personnel that will be assigned to each of the positions listed below. Provide primary name and resume for each key construction person identified below.

Following this page, provide a summary of the duties and responsibilities of these individuals that clearly indicate separate duties and responsibilities for each individual, including responsibilities for schedule development and updates. Note: The Superintendent, CQCSM, ACI Concrete Transportation Inspector, and Site Safety and Health Officer (SSHO) may not share duties and must all be separate individuals in accordance with SECTION 01 45 00.00 10 paragraph 3.4.4.

Following this summary, the offeror shall submit the resumes for key construction personnel assigned to this project.

This Tab shall include resumes on the following personnel:

• Project Manager

• Project Superintendent

• Contractor Quality Control System Manager and Alternate

• ACI Concrete Transportation Inspector

• Petrographer

The resumes in this tab shall clearly present the experience and…