W912BV-16-R-0110-0003.pdf

PDF 150 KB Posted

Attached to
Air Traffic Control Tower, Tinker AFB Federal contract opportunity
Solicitation number
W912BV-16-R-0110
Issued by
Department of the Army Corps of Engineers Engineering District Tulsa

About this file

Amendment 0003

View the file

Other files for this federal contract opportunity

Other files attached to Air Traffic Control Tower, Tinker AFB, newest first.
File Type Posted
W912BV-16-0110-0002.pdf PDF
W912BV-16-R-0110-0001.pdf PDF
W912BV-16-R-0110.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

W912BV-16-R-0110

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

Air Traffic Control Tow er, Tinker Air Force Base, Oklahoma.

1. The due date remains unchanged by this amendment.

2. Sections 00 21 00, and 00 22 00 are revised and made a part of the solicitation. Clause 52.236-25 is added in its entirety to Section 00 72

00. Revised information can be located by searching for an asterisk and amendment number (i.e. *AM3).

3. POC for this amendment is Pun Chittchang, punnie.chittchang@usace.army.mil, 918-669-7544.

4. ALL OTHER TERMS AND CONDITIONS REMAIN UNCHANGED BY THIS AMENDMENT.

1. CONTRACT ID CODE PAGE OF PAGES

1 37

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

16C. DATE SIGNED

BY 06-Jun-2016

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 W912BV-16-R-0110

X 9B. DATED (SEE ITEM 11)

05-Apr-2016

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

06-Jun-2016

CODE

CONTRACTING DIV

USACE, TULSA 1645 S 101 E AVE

TULSA OK 74128-4609

W912BV 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 21 00 - INSTRUCTIONS, CONDITIONS & NOTICES TO OFFERORS

The following have been modified:

00 21 00

INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

1.0 GENERAL INFORMATION

1.1 GENERAL DESCRIPTION OF WORK

1.2 GOVERNMENT SECURITY REQUIREMENTS

1.3 COPIES OF SOLICITATION DOCUMENTS AND AMENDMENTS

1.4 OFFEROR'S QUESTIONS AND COMMENTS

1.5 SMALL BUSINESS SIZE STANDARD/NAICS CODE

1.6 PROPOSAL EXPENSES AND PRE-CONTRACT COSTS

1.7 PRE-PROPOSAL CONFERENCE

1.8 ACCURACY IN PROPOSALS

1.9 PROPOSAL SUBMITTALS

1.10 PROPOSAL FORMAT

1.11 JOINT VENTURE PROPOSAL REQUIREMENTS

1.12 DEVIATIONS AND EXCEPTIONS

1.13 SOLICITATION PROVISIONS

1.0 GENERAL INFORMATION

1.1. GENERAL DESCRIPTION OF WORK

This is a two-phase unrestricted, competitive solicitation, firm-fixed-price design/build contract procured in accordance with FAR 15, Negotiated Procurement utilizing the Best Value Trade-Off process. The POCA is for design-build and construction services to meet the requirements of a design-build construction project of a new *AM3 approximately 120 *AM3 vertical ft Air Traffic Control Tower at Tinker Air Force Base, OK. The Government intends to award one contract using the Best Value Trade-Off Process. The magnitude of this construction project is between $10,000,000 and $25,000,000 dollars. See Section 00 90 00 for additional description of work.

1.2. GOVERNMENT SECURITY REQUIREMENTS

The Offeror(s) must ensure that ALL mail sent to the Tulsa District, U.S. Army Corps of Engineers, either pre-contract or post-contract award, has a return mailing address on the outside of the envelope, package, box, etc. ANY MAIL addressed to the U.S. Army Corps of Engineers, including but not limited to bids, modifications to bids, proposals, revised proposals, bonds, correspondence, etc., will be REJECTED by the US Army Corps of Engineers mail room facility located at 1645 S. 101 E. Ave, Tulsa, OK 74128-4609, if it does not contain a return mailing address. There will be no exceptions.

1.3. COPIES OF SOLICITATION DOCUMENTS AND AMENDMENTS

Copies of the solicitation and amendments are available by INTERNET ACCESS ONLY. All solicitation documents will be posted through the Federal Business Opportunities (FBO) website at:

http://www.fbo.gov

Solicitation number: W912BV-16-R-0110

It shall be the contractor’s responsibility to check the websites for any amendments. The Offeror shall submit in the proposal all requested information specified in this solicitation. There will be no public opening of the proposals received as a result of this solicitation.

Any information given to an Offeror which impacts the solicitation and/or offer will be given in the form of a written amendment to the solicitation.

1.4. OFFEROR'S QUESTIONS AND COMMENTS

All contractual matters, questions and or comments relative to these documents should be submitted via Bidder Inquiry in ProjNet at http://www.projnet.org/projnet/binKornHome/index.cfm?strKornCob=HomePagePublic no later than 14 calendar days prior to the proposal due date, in order that they may be given consideration or actions taken prior to receipt of offers..

The Bidder Inquiry Key for this project is VA43DB-BUEDAK

Instructions for registering in the ProjNet Bidder Inquiry system are available on the above web site.

1.5. SMALL BUSINESS SIZE STANDARD/NAICS CODE

NAICS code is 236220. This procurement is unrestricted.

1.6. PROPOSAL EXPENSES AND PRE-CONTRACT COSTS

This Request for Proposal (RFP) does not commit the Government to pay, as a direct charge, any costs incurred in the preparation and submission of a proposal.

1.7. PRE-PROPOSAL CONFERENCE

The Government intends to hold the pre-proposal conference for Phase 2 of the solicitation. The date, location, time and submittal instructions will be announced by Amendment. The Offeror must submit in writing via e- mail, the firm’s name, address, point of contact, telephone number, and number of personnel planning to attend to the following no later than five (5) working days prior to the conference:

U.S. Army Corps of Engineers, Tulsa District ATTN: Pun Chittchang, CESWT-CT 1645 S. 101 E. Ave.

Tulsa, OK 74128-4609

Phone: 918-669-7544

All interested Offerors are urged to attend. During this conference, the requirements set forth in the Phase 2 solicitation will be reviewed and discussed, with part of the conference to include a question and answer period.

1.8. ACCURACY IN PROPOSALS

Proposals must set forth full, accurate, and complete information as required by this RFP, (including attachments). The penalty for making false statements is prescribed in 18 U.S.C. 1001.

1.9. PROPOSAL SUBMITTALS

1.9.1 The submittal method for proposals is electronic via AMRDEC SAFE or email ONLY (no mailed proposals). AMRDEC SAFE web site: https://safe.amrdec.army.mil/safe

The following email address(es) must be entered for notification of proposal receipt and download availability:

punnie.chittchang@usace.army.mil brian.c.hutchison@usace.army.mil

1.9.2 Proposals will be received until the time and date shown on Standard Form SF 1442 or as amended on SF30. Mail bid bonds to:

U.S. Army Corps of Engineers, Tulsa District ATTN: Punnie Chittchang, CESWT-CT 1645 S. 101 E. Ave.

Tulsa, OK 74128-4609

1.9.3 The packaging shall be marked:

“Solicitation Number: W912BV-16-R-0110”

1.10. PROPOSAL FORMAT

See Section 00 22 00 for Phase I proposal requirements. See Section 00 22 20 (issued with Phase 2) for Phase 2 proposal requirements.

1.11. JOINT VENTURE PROPOSAL REQUIREMENTS

When proposing as a joint venture, all members of the joint venture shall sign the SF 1442 and the bid bond unless a written agreement by the joint venture is furnished with the proposal designating one firm with the authority to bind the other member(s) of the joint venture. In addition, a copy of the joint venture agreement shall be submitted with the proposal. Failure to comply with the foregoing requirements may eliminate the proposal from further consideration. If this is an 8(a) or HubZone joint venture, the Offeror shall ensure that it complies with the applicable requirements of 13 CFR Part 124 and 13 CFR Part 126, respectively.

1.12 DEVIATIONS AND EXCEPTIONS

Deviations and exceptions to the terms and conditions of the solicitation in either the technical or price proposal are neither encouraged nor desired. Should the offer include any standard company terms and conditions that conflict with the terms and conditions of the solicitation, the offer may be determined “unacceptable” and thus ineligible for award. Should the Offeror have any questions related to specific terms and conditions, these must be resolved prior to submission of the offer. Notwithstanding the above, if deviations and exceptions are included with the offer, the Offeror shall list and describe in detail the deviations and/or exceptions on the first page of each Tab. All deviations and exceptions shall be fully supported with the Offeror’s rationale and shall fully explain the impact, if any, on the performance and/or specific requirement of the RFP. The Offeror shall clearly describe on the Proposal Cover Sheet submitted with the Price Proposal any exception to the contractual and/or technical terms and include the monetary impact on the solicitation with the price proposal. This information will not be evaluated separately but may impact the evaluation of other factors.

1.12.1 CONTRACT COST CEILING LIMITATION (CCL) FOR DESIGN AND CONSTURCTION COSTS

The design and construction costs will be subject to the funds available for this project. The total contract award shall not exceed $10,900,00. Offerors are notified that they are under no olbligation to approach the ceiling. However, the Government will not be able to make award, if the dollar amount set for this project is exceeded.

SECURITY CONTRACT LANGUAGE FOR ALL CORPS OF ENGINEERS’ UNCLASSIFIED

CONTRACTS (JUL 2008)

A. AUTOMATED INFORMATION SYSTEM (AIS) EFFORT

All Contractor employees (U.S. citizens and Non- U.S. citizens) working under this contract (to include grants, cooperative agreements and task orders) who require access to Automated Information Systems (AIS), (stand alone computers, network computers/systems, e-mail) shall, at a minimum, be designated into an ADP-III position (non- sensitive) in accordance with DoD 5220-22-R, Industrial Security Regulation. The investigative requirements for an ADP-III position are a favorable National Agency Check (NAC), SF-85P, Public Trust Position. The contractor shall have each applicable employee complete a SF-85P and submit to the Contracting Officer Representative (COR) within three (3) working days after award of any contract or task order, and shall be submitted prior to the individual being permitted access to an AIS. Contractors that have a commercial or government entity (CAGE) Code and Facility Security Clearance through the Defense Security Service shall process the NACs and forward visit requests/results of NAC to the COR. For those contractors that do not have a CAGE Code or Facility Security Clearance, the contractor is responsible for providing a background check as follows:

1. PROVIDE A BACKGROUND CHECK, FOR EACH CONTRACT EMPLOYEE SCHEDULED

TO WORK UNDER THE CONTRACT FOR LESS THAN SIX (6) MONTHS, TO THE CONTRACTING

OFFICER REPRESENTATIVE (COR).

2. PROVIDE A BACKGROUND CHECK, FOR EACH CONTRACT EMPLOYEE SCHEDULED TO

WORK UNDER THE CONTRACT FOR MORE THAN SIX (6) MONTHS TO THE COR. CONDUCT A

BACKGROUND INVESTIGATION (BI) THROUGH THE DEFENSE SECURITY SERVICE (DSS) ON ALL

EMPLOYEES THAT ARE SCHEDULED TO WORK UNDER THE CONTRACT FOR LONGER THAN SIX

(6) MONTHS.

3. ONCE THE CONTRACTOR RECEIVES A RESPONSE FROM THE DSS ON THE STATUS

OF THE INVESTIGATION ON EACH INDIVIDUAL, THE CONTRACTOR SHALL FORWARD THAT

INFORMATION TO THE COR.

4. EACH CONTRACTOR WILL CONTACT THE DEFENSE SECURITY SERVICE, 1-888-282-7682

FOR GUIDANCE ON OBTAINING A BACKGROUND INVESTIGATION FOR THEIR

EMPLOYEES. B. FOREIGN NATIONALS

In accordance with Engineering Regulation, ER 380-1-18, Section 4, foreign nationals who work on Corps of Engineers’ contracts or task orders shall be approved by the HQUSACE Foreign Disclosure Officer or higher before beginning work on the contract/task order. This regulation includes subcontractor employees. (NOTE:

exceptions to the above requirement include foreign nationals who perform janitorial and/or ground maintenance services.) The contractor shall submit to the COR the names of all foreign nationals proposed for performance under this contract/task order, along with documentation to verify that he/she was legally admitted into the United States and has authority to work and/or go to school in the US. Such documentation may include a US passport, Certificate of US citizenship (INS Form N-560 or N-561), Certificate of Naturalization (INS Form N-550 or N-570), foreign passport with I-551 stamp or attached INS Form I-94 indicating employment authorization, Alien Registration Receipt Card with photograph (INS Form I-151 or I-551), Temporary Resident Card (INS Form I-688), Employment Authorization Card (INS Form I-688A), Reentry Permit (INS Form I-327), Refugee Travel Document (INS Form I-571), Employment Authorization Document issued by the INS which contains a photograph (INS Form I-688B).

Classified contracts require the issuance of a DD Form 254 (Department of Defense Contract Security

Classification Specification).

(End of special contract requirement)

SECTION 00 22 00 - PHASE 1 OF 2 PHASE DESIGN BUILD SELECTION PROCESS

The following have been modified:

EVALUATION CRITERIA

SECTION 00 22 00

PHASE 1 OF 2 PHASE DESIGN-BUILD SELECTION PROCEDURES

1.0 OVERVIEW

2.0 GENERAL INSTRUCTIONS

3.0 PHASE 1 PROPOSAL AND RELATED EVALUATION FACTORS

4.0 TAB A – STANDARD FORM 1442 AND PROPOSAL DATA SHEET

5.0 TAB B – FACTOR 1 – SPECIALIZED EXPERIENCE

5.1 SUBMISSION REQUIREMENTS

5.2 EVALUATION CRITERIA

6.0 TAB C – FACTOR 2 – PAST PERFORMANCE

6.1 SUBMISSION REQUIREMENTS

6.2 EVALUATION CRITERIA

7.0 TAB D – FACTOR 3 – ORGANIZATION AND TECHNICAL APPROACH

7.1 SUBMISSION REQUIREMENTS

7.2 EVALUATION CRITERIA

8.0 PHASE 1 OVERALL RATING

9.0 PHASE 1 EVALUATION PROCEDURES

9.1 SOURCE SELECTION EVALUATION BOARD (SSEB)

9.2 EVALUATION

9.3 DEFINITIONS

9.4 EVALUATION AND RATING SYSTEM

9.5 PAST PERFORMANCE CONFIDENCE ASSESSMENT RATING SYSTEM

PHASE ONE – SECTION 00 22 00 ATTACHMENTS

1 – PROPOSAL DATA SHEETS

2 – COMPANY SPECIALIZED EXPERIENCE CONSTRUCTION OR PRIME CONTRACTOR

3 – COMPANY SPECIALIZED EXPERIENCE DESIGN FIRM OR IN-HOUSE DESIGN CAPABILITY

4 – PAST PERFORMANCE SURVEY FORM

5 – KEY PERSONNEL RESUME

6 – LETTER OF COMMITMENT FOR KEY PERSONNEL

7 – LETTER OF COMMITMENT FOR DESIGN FIRM

SECTION 00 22 00

PROPOSAL SUBMISSION REQUIREMENTS, EVALUATION CRITERIA, AND BASIS OF AWARD

(Phase 1 of 2)

1.0 OVERVIEW OF PHASE 1 SELECTION PROCEDURES

1.1 This is a two-phase competitive solicitation for a firm, fixed-price contract, which will be awarded using the Best Value Trade-Off Process.

1.2 The Preliminary scope of this contract includes, but is not limited to, design and construction of a new 130 vertical ft. Air Traffic Control Tower to include reinforced concrete drilled piers, foundation, floor slab, supporting superstructure, control tower cab with tinted double glazing, elevator, supervision, and simulation training areas located at Tinker Air Force Base, Oklahoma. The facility will be designed as permanent construction in accordance with UFC 1-200-01. Includes fire protection systems, back-up power, communications support, tornado shelter, site preparation and drainage, access road and parking area, and other necessary support for a complete and useable facility. Comply with DOD Antiterrorism/Force Protection per unified facilities criteria 4-010-01 to include resisting progressive collapse. Communications will connect to a primary Information Transfer Node (ITN) and a secondary ITN back up. The scope also includes the demolition of an existing Air Traffic Control Tower and simulator building to include various roadways, utilities, etc...

1.3 Phase 1. The first phase consists of a process known in commercial design-build as the “Request for Qualifications” or the acronym: “RFQ”. This solicitation refers to it as “Phase 1”. In Phase 1 of the 2 Phase design-build selection procedure, interested firms or Joint Venture (JV) entities (referred to as “Offerors”) submit specified performance capability proposals, demonstrating their capability to successfully execute the design-build construction contract resulting from this solicitation. The Government will evaluate the performance capability proposals in accordance with the criteria described herein and will select up to three (3) but no more than five (5) of the highest rated Phase 1 Offerors to compete for the design-build contract in Phase 2.

1.3.1 Phase 2. In Phase 2, the selected Offerors will submit preliminary technical-design proposals and the remainder of the performance capability proposals, including identification of key subcontractors, the proposed contract duration, a preliminary schedule, plus a price proposal in response to the Phase 2 Request for Proposal. The final evaluation rating used for comparison, selection, and award will reflect both the rating received in Phase 1 and the evaluation rating received in Phase 2.

1.3.2 The Phase 1 proposal must describe the capability of the Offeror to perform the work, describe the Offeror’s understanding of the requirements contained in the Statement of Work and set forth full, accurate, and complete information as required by the RFP. The proposal should be prepared simply and economically and be legible, clear, and coherent.

1.3.3 Offerors will not be participating in a sealed bid procurement process under this acquisition method. Issuance of this Request for Proposal does not constitute an award commitment on the part of the Government.

2.0 GENERAL INSTRUCTIONS

2.1 Who May Submit: Any legally organized business firm may submit a proposal that is formally organized as design-build entities, design firms and construction contractors that have associated specifically for this project, consortia of business firms or any other interested parties may submit proposals. Associations may be as joint ventures as a partnership in accordance with FAR 9.601, or as key team subcontractors. To qualify for Phase 2, the Offeror or Offeror’s subcontractor shall have professional architects and engineers, registered in the appropriate technical disciplines and the requirements specified in Contract Clause, ”Requirements for Registration of Designers”, must be met. All designs must be under the direct supervision of appropriately licensed professionals for each discipline involved.

2.2 Where to Submit: Pro Forma Information will be received until the date and time indicated on Standard Form 1442 at the address shown in Section 00 21 00 INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS.

2.2.1 Pro Forma Requirements to be provided for Phase 1: This information should be *AM3 (wording deleted) *AM3 labeled “Pro Forma Requirements”. This information consists of the following:

a. The Offeror will submit a cover letter containing:

1) Solicitation number.

2) Name, address, email, and telephone and fax numbers of the Offeror.

3) Names, title, email, and telephone and fax numbers of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this RFP.

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

5) A statement specifying agreement with all terms, conditions and provisions included in the

RFP.

6) CAGE Codes for the Offeror, and all teaming partners who participated in the Factor 1

– Specialized Experience.

b. Acknowledgement of all amendments to the RFP in accordance with the instructions on the Standard Form 30 (amendment form).

c. The completed Section 00 45 00 of the RFP (Representations and Certifications), Printed Entity Record from System for Award Management (SAM)

d. Letter from Surety stating Offer is capable of providing a Bid Guarantee in Phase 2 as required in FAR 52.228-1.

e. Financial statement and bank letter that verify that sufficient funds will be available to finance the work.

f. For Joint Ventures, the information required by paragraph “Joint Ventures”.

g. Identify if this proposal is being submitted as a HUBZone entity.

2.3 Submission Deadline. Proposals shall be received by the Tulsa District no later than the time and date specified in Block 10 of Standard Form 1442 via AMRDEC SAFE website https://safe.armdec.army.mil/safe/, or via email. The following email addresses must be entered for notification of proposal receipt and download availability, or for direct email:

Punnie.chittchang@usace.army.mil brian.c.hutchison@usace.army.mil

2.4 In order to effectively and equitably evaluate all proposals, the Contracting Officer must receive information containing sufficient detail to allow review and evaluation by the Government. Proposal clarity, organization, and cross-referencing are mandatory. Failures to submit and organize proposals as requested may adversely affect an Offeror's evaluation. Offerors should provide sufficient detail and clearly define all items required in this section.

2.5 The Contracting Officer may remove any Offeror from further consideration during any phase of the procurement if the Offeror fails to meet the submittal requirements of the RFP or to reduce the competitive range for purposes of efficiency pursuant to FAR 15.306(c)(2).

2.6 Tabs. Proposal shall be organized and tabbed as shown in paragraph 3.0, “Phase I Proposal and Related Evaluation Factors”.

2.7 Size of Printed Matter Submissions.

2.7.1 Proposal materials shall be submitted via AMRDEC SAFE website https://safe.armdec.army.mil/safe/, or via email, containing the proposal in PDF file format using Adobe Acrobat software. Proposals shall be tabbed and labeled in a manner to afford easy identification from a Table of Contents. Each page shall be identified with the appropriate page number centered at the bottom of the page. Sheet size of the proposal contents shall be 8-1/2 inches x 11 inches where sheets are prepared specifically for this proposal, unless another paper size is specifically authorized elsewhere in this section for a particular submission. Do not use alternative paper sizes (e.g., 11” x 14” or 11” x 17” sheets) unless specifically authorized in this section for a particular submission. Do not use a font size smaller than 10, an unusual font style such as script, or condensed print for any submission. All page margins must be at least 1 inch wide, but may include headers and footers. Phase 1 proposals shall not exceed 30 single-sided pages, excluding the cover sheet and Table of Contents. A page is defined as text or information on one side of the paper. Factor 2 – Past Performance will not be counted towards this page limitation, nor will the resumes submitted for key personnel. The Government will not evaluate any information beyond the page limitation noted. The Government will not review any information submitted in an appendix or attachment to the proposal. The Offeror shall not submit verbatim sections of this solicitation as part of their proposal. Offers that do not meet these requirements may be subject to rejection.

2.7.2 The proposals shall contain a detailed table of contents.

2.7.2.1 Proposals shall contain the entire proposal in .pdf format using Adobe Acrobat software to print to a .pdf file; do NOT scan the document(s) into a .pdf file. The text portion of the complete proposal shall be contained as a single .pdf file. The technical proposal will be appropriately organized using the tabs specified in the chart above.

2.7.2.2 A cover sheet identifying the Offeror (name, address, point of contact), project description, and solicitation number shall be provided. The second sheet shall be a Table of Contents. Offers that violate these rules unnecessarily delay the evaluation process and may be rejected by the Government after the initial evaluation without receiving any further consideration.

2.7.2.3 Sections of the proposal shall be bookmarked (linked to the index) as detailed below. The SF 1442 may be scanned and shall be *Optical Character Recognition (OCR) compatible. All text must be legible and easily read. Submit the SF 1442, completed and signed by a person authorized by the Offeror. A page is defined as text or information on one side of the paper.

Factor 2 – Past Performance will not be counted towards this page limitation.

*OCR is a common method of digitizing printed texts so that they can be electronically searched, stored more compactly, displayed on-line, and used in machine processes such as machine translation, text-to- speech, key data extraction and text mining.

2.7.2.4 Each Volume of the proposal shall be identified by the Solicitation Number (W912BV-16-R-0110), project title (Air Traffic Control Tower, Tinker AFB), name, address, and telephone number of the Offeror, and the following on the volume in bold letters:

Phase 1 Volume 1: TECHNICAL PROPOSAL

2.7.3 Proposal revisions shall be submitted as page replacements with revised text readily identifiable, e.g., bold face print or underlining. The source of the revision, e.g., Error, Omission, or Clarification, or amendment shall be included and be annotated for each revision. Proposal replacement pages shall be numbered, shall be clearly marked “REVISED”, shall show the date of revision. A revised copy of the entire proposal in .pdf format shall be provided.

3.0 PHASE 1 PROPOSAL AND RELATED EVALUATION FACTORS

Location Factor Number Description Relative Importance

Tab A SF 1442 and Proposal Data Sheet N/A

Tab B Factor 1 Specialized Experience Most Important Factor

Tab C Factor 2 Past Performance 2nd Most important factor

Tab D Factor 3 Organization and Technical Approach 3rd Most important factor

4.0 TAB A - STANDARD FORM 1442 AND PROPOSAL DATA SHEET

4.1 Submit the SF 1442, completed and signed by a person authorized by the Offeror. Include the completed proposal data sheet (See attachment 1, provided at the end of this Section).

5.0 TAB B – FACTOR 1 - SPECIALIZED EXPERIENCE

5.1 SUBMISSION REQUIREMENTS

5.1.1 The prime contractor and the design firm(s) (or prime contractor if design is to be self-performed) shall each demonstrate recent, relevant experience on similar projects using the Construction – Specialized Experience form – (Attachment 2), and Designer – Specialized Experience Form – (Attachment 3) at the end of the section. Offerors may identify state and local government and private contracts that are similar to the Government’s requirements as outlined in Section 01 10

00. If the Offeror is a joint venture, each firm shall provide information, demonstrating experience relevant to their role on this project. Submit projects that are currently well underway (designed and at least 50% construction progress completed) or completed and turned over no longer than seven (7) years preceding the date of this Solicitation. If any firm has multiple functions or divisions, limit the project examples to those performed by the division or unit submitting the offer or by the team member. Design firms may list prime contractors they have worked for or government, private or commercial customers. The Offeror shall select the design firm(s). If projects were design-build (D-B), so identify them. Prime contractor must submit at least one *AM3 tall building (i.e. aircraft hangar, etc.) or high rise-type *AM3 project with a value of $8 million or greater. The design firm(s) must submit at least one control tower project. Both the prime contractor and the design firm(s) shall each submit at least three (3) projects but no more than five (5) projects. Each project submitted for both the prime and design firms shall be limited to one (1) page per project.

5.1.2 The Offeror may provide a supplemental narrative (not project lists), not to exceed two (2) pages, explaining how any corporate experience that is not directly related to the specific projects above is applicable to this project and how the Government will benefit.

5.1.3 The Offeror should describe any previous teaming experience between current team members, if not described in the project list. Offeror may describe design-build experience on other type projects. The above information is limited to projects that are well underway or that have been completed and turned over no longer than the past seven (7) years preceding the date of this solicitation.

5.2 EVALUATION CRITERIA:

5.2.1 The Government will evaluate the extent of recent, related experience of the prime contractor and design firms in design, construction or design-build, as relevant to their role on this project. If the design will be accomplished in-house, rather than by subcontract, then the design element of specialized experience will still be evaluated, realizing that the work is being done in-house.

Experience on the similar projects identified in the project lists will receive more consideration than experience provided in the supplemental narrative. The Government may place greater importance on projects performed as a prime contractor than as a subcontractor, depending upon overall role and relevancy considerations.

To determine strengths and weaknesses, the agency will give more consideration to the contractor’s experience and success with the following:

a. A higher number of relevant projects for both the prime contractor and the design firm(s), up to a maximum of five (5) each.

b. Projects designed for and constructed on military installations.

c. Projects involving design and construction of air traffic control towers.

d. Projects designed for and constructed on an active military or commercial runway, taxiway, etc., requiring airfield training, escorting, minimizing effects of foreign object damage (FOD) to the building and surrounding areas, and in obtaining waivers from the Federal Aviation Administration (FAA).

e. Projects with a value of $8 million or greater.

f. Fully completed projects rather than substantially complete projects.

g. Projects completed within seven (7) years of this solicitation announcement (i.e., after 2009).

h. Projects involving design and construction in conditions dealing with concurrent work from adjacent contractors and/or in congested work areas.

i. Projects that demonstrate experience of the team members commensurate with their proposed role on this project.

j. High-rise design and construction experience (designer and construction contractor).

k. Experience in projects that required Leadership in Energy and Environmental Design (LEED) Certification and use of Building Information Modeling (BIM) during the design phase.

l. Project examples demonstrating prior teaming experience of the prime construction contractor and the design firm.

5.2.2 The Offeror shall submit the requested information to demonstrate a record of recent, related experience in both design and construction, for the facility types (which may include similar state or local government or private counterparts) included in this contract, as described in Section 00 22 00. Recent experience includes projects well underway (see above criteria) or those completed and turned over within seven (7) years of the proposal issue date for this RFP for design or construction experience. Joint Venture partners should each demonstrate experience commensurate with their role on this project or explain in the supplemental narrative how their experience qualifies them for their role on this project.

5.2.3 The Government reserves the right to verify the experience record of cited projects or other recent projects by reviewing the Corps of Engineers Construction Contractor (or Architect- Engineer) Appraisal Support System (CCASS/ACASS), other DoD or Government appraisal systems or to interview owners or references. The Government may check any or all cited references to verify supplied information.

5.2.4 To receive credit for extent (amount) of experience, the Offeror and its proposed design firm(s) shall demonstrate a history of recent, relevant experience. A firm will not receive credit under this factor for the relevant experience of key personnel proposed for this project.

5.2.5 The Government will consider extent of recent experience, degree of relationship of such experience to this project, demonstrated familiarity with applicable codes and local conditions.

Some examples of relevancy to this project may include, but not be limited to:

a. Number, size, type work, complexity, location

b. Dates (well under way or completed no more than seven (7) years preceding date of Solicitation)

c. Firm's role and extent of work self-performed (brokering out all work and simply “pouring the sidewalks” on a cited project are examples of less relevant experience)

5.2.6 Previous design-build experience is not necessary for an acceptable rating. The Government may consider previous D-B experience a strength, even if the experience is on different type projects than this project. Similarly, the Government may consider previous recent teaming experience among the team members as value added, even if on different type design and/or construction projects than this project. The more relevant the experience, the more credit will be given.

6.0 TAB C – FACTOR 2 - PAST PERFORMANCE

6.1 SUBMISSION REQUIREMENTS:

6.1.1 For each of the projects submitted under Factor 1, to ensure the agency has all relevant past performance information, the Offeror shall submit copies of Federal/DoD/Navy/Army performance reviews that are likely already in the agency’s databases or likely within the agency’s arm’s reach, (i.e., Contractor’s copy of CCASS or CPARS evaluations).

6.1.2 For each project under Factor 1 that does not have a CPARS evaluation, Offerors shall provide a

Past Performance Questionnaire form PPQ-0 (Attachment 4) to a representative of the owner that can provide the owner’ s opinion of the Offeror’s past performance for the project. The Past Performance Questionnaire (Form PPQ-0) included in the solicitation is provided for the Offeror or its team members to submit to the client for each project the Offeror includes in its proposal for Factor 1. Ensure correct phone numbers and email addresses are provided for the client point of contact. Offerors should organize all Past Performance Information based on the Factor 1 Projects, which normally have project titles and are numbered 1-5, so that reviewers can match the owner’s opinion with the corresponding Factor 1 Project. There is no page limit for this factor.

6.1.3 Form PPQ-0 shall be utilized, and Offerors shall submit the PPQ with their proposal submission to the Contracting Office designated proposal submission location. The contract specialist or Contracting Officer will not require the PPQ-0 to be sent directly from the client. The Offeror may submit the completed PPQ-0. Completed Past Performance Questionnaires should be submitted with your proposal. If the Offeror is unable to obtain a completed PPQ-0 from a client for a project(s) before proposal closing date, the Offeror shall complete and submit with the proposal the first page of the PPQ-0, which will provide contract and client information for the respective project(s). Offerors should follow-up with clients/references to ensure timely submittal of questionnaires. If the client requests, questionnaires may be submitted directly to the Government’s point of contact, Pun Chittchang via email punnie.chittchang@usace.army.mil, prior to proposal closing date.

If you have questions regarding the attached questionnaire, or require assistance, please contact the Contract Specialist at (918) 669-7544.

6.1.4 While the Government may elect to consider data from other sources, the burden of providing detailed, current, accurate and complete past performance information rests with the Offeror.

6.1.5 The Offeror is responsible for ensuring that the completed questionnaires are submitted by the closing date. The Government may contact and interview the owner’ s representative on the Past Performance questionnaires, and reserves the right to interview other individuals acting for the owner’ s representative, if the owner’ s representative is not available.

6.1.6 The Government will evaluate the responses from the customers from which Past Performance Questionnaires have been received. The Government may contact and interview points of contact on the Past Performance Questionnaires. The Government reserves the right to interview other individuals acting for the listed references, if the listed reference is not available. In addition to the above, the Government may review any other sources of information for evaluating past performance.

6.1.7 Past performance information may be obtained from any other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Construction Contractor Appraisal Support System (CCASS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), or other databases; interviews with Program Managers, Contracting Officers, and Fee Determining Officials; and the Defense Contract Management Agency.

6.1.8 To improve accuracy of database searches, the Offeror will also provide the CAGE Codes for the prime contractor and all teaming partners, i.e., design firms, key subcontractors, Joint Venture Partners, whose experience is being evaluated in Factor 1.

6.1.9 The Government may contact references provided as part of Factor 1 – Specialized Experience, for information regarding the Offeror’s past performance on the project and for the purposes of assessing and verifying the scope of the work performed. Offerors should provide accurate, current, and complete contact information for references provided in the project descriptions.

6.1.10 Additional past performance examples may be submitted for consideration on any member of a Teaming Arrangement that will perform a major or critical aspect of the project. Projects cited shall be currently well underway (fully designed and at least 50% construction progress completed) or construction substantially completed within seven (7) years preceding the date of this solicitation. If any firm has multiple functions or divisions, limit the project examples to those performed by the division, unit or team member submitting the offer.

6.1.11 Joint Venture Submission Requirements.

6.1.12 Offerors submitting proposals as a Joint Venture shall obtain a DUNS number and be registered in the Central Contractor Registration (CCR) as the offering Joint Venture. The Offeror must provide three (3) to five (5) "recent", "relevant" projects performed by the JV that reflect the JV's ability to perform the work required in this solicitation as required under Factor 1.

6.1.13 If the Offeror cannot provide a sufficient number of projects as the JV to meet the minimum requirement, the Offeror must provide those "recent", "relevant" projects that it has performed as the JV, and then supplement the record with additional "recent", "relevant" projects performed by each JV member in their individual capacities. In such instance, each JV member must satisfy the minimum requirement of three (3) projects, to include any performed as the JV.

6.1.14 If the JV has no "recent", "relevant" projects performed by the JV, then each member of the JV must provide three (3) to five (5) "recent", "relevant" projects performed by the JV member that reflect the JV member's experience commensurate with their role on this project or how their experience qualifies them for their role on this project as required under Factor 1.

6.1.15 In addition to the examples of "Company Specialized Experience" and "Past Performance Surveys", the Joint Venture shall provide a brief narrative stating the roles that each partner of the Joint Venture will perform on this project and how the presented projects demonstrate the JV member's experience commensurate with their role on this project or how their experience qualifies them for their role on this project. The attached “Specialized Experience" and "Past Performance Survey" forms shall be used by the Joint Venture or the JV partners. Explain how the JV is structured.

6.1.16 Verification: The Government reserves the right to verify the experience record of cited projects or other recent projects not submitted by reviewing the Past Performance Information Retrieval System (PPIRS, or other Government appraisal systems or to interview owner or references. The Government may check any or all cited references to verify supplied information. An Offeror will be afforded the opportunity to reply to or explain adverse performance information to which the Offeror has not previously had an opportunity to address.

6.2 EVALUATION CRITERIA:

6.2.1 The Government will perform a performance confidence assessment of the Offeror’s probability of successfully meeting the contract requirements, considering the degree of success of the D-B team’s recent (well under way or turned over no longer than seven (7) years preceding the date of this solicitation), relevant experience. See explanation of “well underway” and relevancy under the Factor “Specialized Experience”. The Government will assess the past performance on projects submitted under the Specialized Experience Factor and reserves the right to conduct telephone interviews with points of contact identified in the proposal and/or to review other recent projects rated in CCASS/ACASS or other agency performance databases, review and/or contact Offeror-furnished references, or to review personal knowledge.

6.2.2 The Government will first assess and rate the relevancy of recent projects accomplished by the Offeror to the scope of this contract for overall application to the performance confidence assessment ratings described hereinafter. The projects will include those submitted under the Specialized Experience Factor as well as from other sources described above. This rating is not a separate proposal rating but is only used in developing overall past performance confidence assessment rating assigned to the Past Performance Factor. The past performance relevancy rating are described below:

6.2.2.1 Very Relevant: Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

6.2.2.2 Relevant: Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

6.2.2.3 Somewhat Relevant: Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

6.2.2.4 Not Relevant: Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

6.2.3 The Government will next consider how well the Offeror performed on the contracts. The Government will consider the currency and relevance of the information, source of the information, context of the data, and general trends in contractor performance. With respect to relevancy, past performance on projects with more relevance will typically be a stronger predictor of future success and have more influence on the past performance confidence assessment rating than past performance on projects of lesser relevance. If any firm has multiple functions or divisions, the Government will only evaluate past performance of the division or unit submitting the offer or by the team member. Owners/references may be asked to comment on items such as quality of design or construction, timeliness, management of the work, subcontractor management, including timely payment to subs or suppliers, safety, relations between owner and designer or contractor, level of support for such things as as-built documentation, O&M manuals, training, correcting design or construction errors, warranty work, etc. The Government will target areas covered in the requirements of this proposal including records of confirming to quality, schedule, cost control, customer satisfaction, level of support for such things as as-built documentation, O&M Manuals, training, problem resolution for design or construction errors, warranty work, and safety. The Government will not release the Interview Forms to the Offeror at any time, in order for the Government to solicit candid, unbiased interview comments. The Government also places a higher value on projects, which document successful outcomes and are supported by outside source confirmation, for example, but not limited to telephone databases, Offeror-furnished references, or personal knowledge. The Government also paces a higher value on projects, which provided particularly difficult or unique challenges and the innovative methods the contractor used to resolve problems successfully. The rating for this factor will be expressed as a degree of confidence in the Offeror’s ability to successfully accomplish the contract requirements. The rating system used for the performance confidence assessment is described below.

6.2.3.1 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.

6.2.3.2 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

6.2.3.3 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.

6.2.3.4 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.

6.2.3.5 Unknown Confidence (Neutral): 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.

6.2.4 Each entity (firm) will be rated on its own performance or that of its predecessor, if relevant. An entity may establish past performance based on the past performance of its proposed key personnel, apart from that of the entity. If the Government does not obtain past performance information for the projects identified by the Offeror and cannot establish a past performance record for the Offeror through other sources, past performance will be rated neither favorably nor unfavorably. The performance confidence assessment will be considered “Unknown Confidence”.

7.0 TAB D – FACTOR 3 - ORGANIZATION AND TECHNICAL APPROACH

7.1 SUBMISSION REQUIREMENTS:

7.1.1 Provide information that describes the Offeror’s organization and intended technical approach to executing the design-build contract per the detailed requirements herein. Limit the information to twelve (12) pages or less clearly but concisely describe the organizational and technical approach to project management and execution. The twelve (12) page limit does not include resumes or unequivocal letters of commitment submitted for key personnel, below.

7.1.2 Offeror’s Understanding: Describe the Offeror's understanding of the challenges, risks and technical approach with respect to construction of air traffic control towers and/or high-rise facilities, working on active airfields, working in congested areas with multiple concurrent contractors, and the life safety engineering aspect for these facilities. The response shall reference at a minimum Progressive Collapse UFC 4-023-03. The response must clearly illustrate the Offeror's understanding of these documents; do not simply quote UFC and similar references.

7.1.3 Organization: Describe what firms, their resources and how their resources will be utilized, their roles and responsibilities and any contractual arrangements that have been established. Clearly describe any teaming or joint venture arrangements, including a clear description of each firm’s roles and responsibilities on the project. The Offeror shall document unequivocal teaming arrangements with its design firms(s) (see attachment 7). A copy of the teaming or joint venture agreement(s) may be appended to the plan (not included in the page limitation).

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .