B.08.02 W912DR20R0016 Solicitation.pdf
PDF 2 MB Posted
- Attached to
- PENTAGON RDF ROOF REPAIR
- Solicitation number
- W912DR20R0016
About this file
This solicitation requests design-build proposals for structural strengthening of the Pentagon Remote Delivery Facility roof in Arlington, Virginia. The Army Corps of Engineers seeks to retrofit the existing roof helipad and supporting infrastructure to safely support military helicopter landings and operations. Proposals are due by May 4, 2020.
The solicitation is a two-phase selection process. Phase I requests information on offerors' past performance and management experience for evaluation. Up to five highest rated offerors will advance to Phase II. Phase II proposals will be evaluated on technical approach, small business participation plan, and price. The contract will be awarded based on best value determination considering all factors. Phase II proposals are due by the date specified in the forthcoming amendment inviting finalists to submit.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
US Army Corps Of Engineers Baltimore District
SOLICITATION FOR
Pentagon Remote Delivery Facility (RDF) Roof Repair, Arlington, VA
Solicitation No. W912DR-20-R-0016
Date: 3 April 2020
THIS PROCUREMENT IS UNRESTRICTED
PROJECT TITLE: PENTAGON RDF ROOF REPAIR
This proposed procurement is Full and Open Competition (Unrestricted); NAICS Code 236220 “Commercial and Institutional Building Construction” w ith a size standard of $39.500.000.00.
This is a Firm Fixed Price, Tw o (2) Phase Design-Build Construction Contract utilizing the Best Value Tradeoff process.
Contractors are requested to review requirements and instructions for a Design-Build selection in response to this Request for Proposal (RFP). This is Phase I of the solicitation phase. Phase II of the solicitation w ill be issued as an amendment and only be available to those offerors selected to advance from Phase I to Phase II.
QIANA L BOWMAN-SPENCER 410-962-5613
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
10. THE GOVERNMENT REQUIRES PERFORMANCE OF THE WORK DESCRIBED IN THESE DOCUMENTS
NEGOTIATED
03-Apr-2020
(RFP)
(IFB)
X
CALL:
B. TELEPHONE NO. (Include area code) (NO COLLECT CALLS)
See Item 7
2. TYPE OF SOLICITATION
SEALED BID
3. DATE ISSUED
9. FOR INFORMATION A. NAME
SOLICITATION
NSN 7540-01-155-3212 1442-101 STANDARD FORM 1442 (REV. 4-85)
Prescribed by GSA
FAR (48 CFR) 53.236-1(e)
11. The Contractor shall begin performance w ithin _______10 calendar days and complete it w ithin ________605 calendar days after receiving aw ard, X notice to proceed. This performance period is X mandatory, negotiable. (See _________________________FAR 52.211-10
12 A. THE CONTRACTOR MUST FURNISH ANY REQUIRED PERFORMANCE AND PAYMENT BONDS?
(If "YES," indicate within how many calendar days after award in Item 12B.)
X YES NO
13. ADDITIONAL SOLICITATION REQUIREMENTS:
A. Sealed offers in original and __________1 copies to perform the w ork required are due at the place specif ied in Item 8 by ___________ local time ______________04 May 2020 (date). If this is a sealed bid solicitation, offers must be publicly opened at that time.
shall be marked to show the offeror's name and address, the solicitation number, and the date and time of fers are due.
B. An offer guarantee X is, is not required.
C. All offers are subject to the (1) w ork requirements, and (2) other provisions and clauses incorporated in the solicitation in full text or by reference.
D. Offers providing less than _______120 calendar days for Government acceptance after the date offers are due w ill not be considered and w ill be rejected.
SOLICITATION, OFFER,
AND AWARD
(Construction, Alteration, or Repair)
1. SOLICITATION NO.
IMPORTANT - The "offer" section on the reverse must be fully completed by offeror.
4. CONTRACT NO.
7. ISSUED BY CODE
USACE BALTIMORE
2 HOPKINS PLAZA
BALTIMORE MD
W912DR
PAGE OF PAGES
1 OF
CODE
(Title, identifying no., date):
12B. CALENDAR DAYS
11:00 AM (hour)
Sealed envelopes containing offers
5. REQUISITION/PURCHASE REQUEST NO. 6. PROJECT NO.
8. ADDRESS OFFER TO (If Other Than Item 7)
FAX:TEL: TEL: FAX:
W912DR20R0016 91
20B. SIGNATURE
(REV. 4-85)STANDARD FORM 1442 BACK
TO SIGN
NSN 7540-01-155-3212
SOLICITATION, OFFER, AND AWARD (Continued) (Construction, Alteration, or Repair)
CODE FACILITY CODE
17. The offeror agrees to perform the w ork required at the prices specif ied below in strict accordance w ith the terms of this solicitation, if this offer is accepted by the Government in w riting w ithin ________ calendar days after the date offers are due.
the minimum requirements stated in Item 13D. Failure to insert any number means the offeror accepts the minimum in Item 13D.)
AMOUNTS SEE SCHEDULE OF PRICES
18. The offeror agrees to furnish any required performance and payment bonds.
19. ACKNOWLEDGMENT OF AMENDMENTS
(The offeror acknowledges receipt of amendments to the solicitation -- give number and date of each)
AMENDMENT NO.
DATE
20A. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN
OFFER (Type or print)
AWARD (To be completed by Government)
21. ITEMS ACCEPTED:
22. AMOUNT 23. ACCOUNTING AND APPROPRIATION DATA
24. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM
(4 copies unless otherwise specified)
CODE
(Insert any number equal to or greater than
20C. OFFER DATE
25. OTHER THAN FULL AND OPEN COMPETITION PURSUANT TO
10 U.S.C. 2304(c) 41 U.S.C. 253(c)
CODE27. PAYMENT WILL BE MADE BY:26. ADMINISTERED BY
(Include ZIP Code)14. NAME AND ADDRESS OF OFFEROR 15. TELEPHONE NO. (Include area code)
See Item 14
(Include only if different than Item 14)16. REMITTANCE ADDRESS
30B. SIGNATURE
29. AWARD (Contractor is not required to sign this document.)
document and return _______ copies to issuing office.) Contractor agrees Your of f er on this solicitation, is hereby accepted as to the items listed. This award con-to f urnish and deliv er all items or perf orm all work, requisitions identif ied summates the contract, which consists of (a) the Gov ernment solicitation and on this f orm and any continuation sheets f or the consideration stated in this y our of f er, and (b) this contract award. No f urther contractual document is contract. The rights and obligations of the parties to this contract shall be necessary .
gov erned by (a) this contract award, (b) the solicitation, and (c) the clauses, representations, certif ications, and specif ications or incorporated by ref er-ence in or attached to this contract.
30A. NAME AND TITLE OF CONTRACTOR OR PERSON AUTHORIZED 31A. NAME OF CONTRACTING OFFICER (Type or print)
30C. DATE
(Type or print)
TEL: EMAIL:
31B. UNITED STATES OF AMERICA 31C. AWARD DATE
BY
CONTRACTING OFFICER WILL COMPLETE ITEM 28 OR 29 AS APPLICABLE
(Contractor is required to sign this28. NEGOTIATED AGREEMENT
(M ust be fully completed by offeror)OFFER
Source Selection Information - See FAR 2.101 and 3.104
Section 00 10 00 - Solicitation
DELIVERY INFORMATION
CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /
CAGE
Section 00 20 00 - Instructions for Procurement
NOTES TO OFFERORS
This solicitation is a two-phase Design-Build solicitation. Currently, this solicitation is for Phase 1 only. Phase 1 submissions will be reviewed and a maximum of five (5) of the most highly qualified proposals will be invited to submit Phase 2 proposals. Bid bonds are not required to be submitted until Phase 2 submissions. Additionally, a bid schedule, small business participation goals, and expanded specifications and details regarding the concept design will be provided during the Phase 2 via a solicitation amendment.
INSTRUCTIONS TO OFFERORS
IMPORTANT NOTES REGARDING THIS ACQUISITION
1. PROPOSAL CONDITIONS
a. Contractors must provide all required documents for Phase I.
b. Split awards or multiple award contracts will not result from this solicitation.
2. COMPETITION: Full and Open Competition.
3. SUBMISSION OF PROPOSALS
a. All proposals must be submitted in accordance with the procedures set forth in Block 13 of Page 1 of this
Solicitation document. PROPOSALS OR MODIFICATIONS TO PROPOSALS THAT ARE RECEIVED BY
FACSIMILE WILL NOT BE CONSIDERED.
b. Hand Carried and Mailed Proposal: Due to the current state please see item 1.5 below on proposal submittal instructions.
c. SF 1442 BACK (Page 2 of the Solicitation): Offerors are required to acknowledge the receipt of all amendments to the Solicitation on the Standard Form 1442 in Block 19. Offerors shall fully complete all the required areas located under the section designated as “OFFER” (refer to Items 14 through 20C).
d. BID GUARANTEE: The offerors are required to submit a Bid Guarantee for this procurement during Phase II submissions. Any offeror failing to submit an authentic Bid Guarantee will be considered non-responsive to the Solicitation and ineligible for award. The Bid Guarantee shall be in the amount of 20% of the bidder’s price or $3,000,000.00, whichever is less.
e. BONDS AND INSURANCE: The Contractor will be required to furnish proof of insurance, including copies of the required endorsements, and performance and payment bonds within ten (10) calendar days following the Contractor’s receipt of the contract award.
4. VISITOR/SECURITY REQUIREMENTS
More information concerning site visit and visitor/security requirements will be added for Phase II.
5. REQUESTS FOR INFORMATION
Technical inquiries and questions relating to this solicitation are to be submitted via Bidder Inquiry in ProjNet at (https://www.projnet.org) No Later Than (NLT) 11:00 A.M. (EST), 17 APRIL 2020. To submit and review inquiry items, prospective vendors will need to use the Bidder Inquiry Key presented below and follow the instructions listed below the key for access. A prospective vendor who submits a comment /question will receive an acknowledgement of their comment/question via email. Another email to the same address will notify the prospective vendor once the reply is available for viewing.
The Bidder Inquiry Key is: BRPBA4-452ICB
Specific Instructions for ProjNet Bid Inquiry Access:
1. From the ProjNet home page linked above, click on Quick Add on the upper right side of the screen.
2. Identify the Agency. This should be marked as USACE.
3. Key. Enter the Bidder Inquiry Key listed above.
4. Email. Enter the email address you would like to use for communication.
5. Click Continue. A page will then open saying that a user account was not found and will ask you to create one using the provided form.
6. Enter your First Name, Last Name, Company, City, State, Phone, Email, Secret Question, Secret Answer, and Time Zone. Make sure to remember your Secret Question and Answer as they will be used from this point on to access the ProjNet system.
7. Click Add User. Once this is completed you are now registered within ProjNet and are currently logged into the system.
Specific Instructions for Future ProjNet Bid Inquiry Access:
1. For future access to ProjNet, you will not be provided any type of password. You will utilize your Secret Question and Secret Answer to log in.
2. From the ProjNet home page linked above, click on Quick Add on the upper right side of the screen.
3. Identify the Agency. This should be marked as USACE.
4. Key. Enter the Bidder Inquiry Key listed above.
5. Email. Enter the email address you used to register previously in ProjNet.
6. Click Continue. A page will then open asking you to enter the answer to your Secret Question.
7. Enter your Secret Answer and click Login. Once this is completed you are now logged into the system.
The call center operates weekdays from 8AM to 5PM U.S. Central Time Zone (Chicago). The telephone number for the Call Center is 800-428-HELP.
Offers will NOT be publicly opened. Information concerning the status of the evaluation and/or award will NOT be available after receipt of proposals.
PLEASE NOTE: THE LAST DAY FOR INTERESTED BIDDERS TO SUBMIT THEIR CONTRACTING
AND TECHNICAL REQUESTS FOR INFORMATION IN PROJNET IS 17 APRIL 2020 AT 11:00 AM
(EST). NO OTHER REQUEST FOR INFORMATION WILL BE ACCEPTED AFTER 11:00 AM (EST).
*** NOTE: QUESTIONS ANSWERED IN PROJNET ARE NOT OFFICIAL UNTIL AN AMENDMENT IS
ISSUED. ***
SCOPE OF WORK
The RDF is a single story cast-in-place concrete warehouse structure constructed in 2000 with a combination of two-way flat slab construction and beam-slab construction supported by concrete columns and bearing walls. The roof structure was designed to incorporate a deep soil vegetative roof inclusive of one (1) to four (4) feet of soil depth. The RDF structure was not originally designed with the intent of landing helicopters on the roof, but was converted into that purpose in 2004 with the construction of a helipad. The RDF roof helipad supports helicopter landing, takeoff and parking on its north end and on green parade fields down its center. The objective of this project is to retrofit and convert the RDF roof helipad system into a helipad facility that sustains safe operations (landing, takeoff, and parking) of the fleet of military helicopters identified in the technical requirements, and the applicable emergency support vehicles, and do so without compromising the structural integrity of the RDF structure. In addition to structural strengthening, exterior site, environmental, air traffic control, electrical, drainage, backfill, waterproofing, and irrigation system adjustments are required to sustain RDF roof helipad safe operation.
The implementation of the structural strengthening work will minimally impact occupied spaces below the roof including, Architectural, HVAC, Plumbing, Electrical, Fire Alarm, Communications and Fire Suppression systems.
Section 00 21 16 - Instructions to Proposers
PHASE I PROPOSAL SUBMISSIONS
1. PROPOSAL SUBMISSION INSTRUCTIONS
1.1. General: This request for proposal (“RFP”) seeks proposals from Offerors interested in being selected for construction of the Pentagon Remote Delivery Facility (RDF) and Helipad at Pentagon Reservation, Arlington, VA.
Offerors responding to this RFP are required to submit their proposals in accordance with the instructions contained in this Section 00 21 16. This is Phase I of a two-phase RFP. This RFP is requesting submission of proposals under Phase I submission criteria ONLY. After evaluating Phase I proposals, the contracting officer will select the most highly qualified Offerors and request that only those Offerors submit proposals for Phase II. The maximum number of Offerors that will be selected to submit Phase II proposals shall not exceed five (5).
Offerors shall not submit any proposals under Phase II submission criteria at this time. Phase II of the solicitation will be issued in an amendment directly to those Offerors selected for Phase II. Submitting any information under Phase II criteria may lead to disqualification of your proposal. This is an Unrestricted competitive RFP. Offerors responding to this RFP are required to submit their proposals in accordance with the instructions contained in this Section 00 21 16.
The objective of this project is to retrofit and convert the RDF roof helipad system into a helipad facility that sustains safe operations (landing, takeoff, and parking) of the fleet of military helicopters identified in the technical requirements, and the applicable emergency support vehicles, and do so without compromising the structural integrity of the RDF structure. In addition to structural strengthening, exterior site, environmental, air traffic control, electrical, drainage, backfill, waterproofing, and irrigation system adjustments are required to sustain RDF roof helipad safe operation. The implementation of the structural strengthening work will minimally impact occupied spaces below the roof including, Architectural, HVAC, Plumbing, Electrical, Fire Alarm, Communications and Fire Suppression systems.
1.2. Basis For Award: A contract will be awarded to the Offeror whose proposal represents the “Best Value” to the Government. The best value determination will be based on a comparative assessment of proposals against all source selection criteria in the solicitation, considering recommendations and minority opinions presented to the Source Selection Authority (SSA).
While the SSA may use reports and analyses prepared by others, the source selection decision shall represent the SSA's independent judgment.
For the purposes of this solicitation, the Government will utilize the Best Value Trade-Off Process. Award will be made to the Offeror whose proposal is the best value and most advantageous to the Government based on an integrated assessment of the evaluation factors described below.
PHASE I
Factor 1 - Past Performance/Experience Factor 2 - Management Capability
For Phase I, Past Performance/Experience and Management Capability will be adjectivally rated. Past Performance/Experience is more important than Management Capability. Factors 1 and 2 will not carry into Phase
II.
Each factor is rated individually based on the information contained in that specific factor; that is, evaluations will not be made across the factors.
PHASE II
Factor 3 - Technical/Approach Factor 4 - Small Business Participation Plan Factor 5 - Price
Each factor is rated individually based on the information contained in that specific factor; that is, evaluations will not be made across the factors.
For Phase I, Factors 1 and 2 will be adjectivally rated. Factor 1 is more important than Factor 2.
For Phase II, Factors 3 and 4 will be adjectivally rated. Factor 3 is more important than Factor 4 and when combined, are approximately equal to Factor 5 (Price).
1.1. Source Selection: It is intent of the Government to seek proposals from qualified Offerors with experience in the significant features of this RFP and who can demonstrate a successful performance history in completing relevant projects. For the purposes of this solicitation, the Government will utilize the Trade-Off Process. The successful Offeror will be selected based on the “Best Overall Value to the Government”. The Government will not make an award at a significantly higher price to obtain only slightly superior technical advantages; however, the degree of importance of price as a factor could become greater depending upon the equality of the proposals submitted.
Where the technical merits of competing proposals are determined to be substantially equal, price could become the controlling factor.
1.2. Each Offeror is required to submit a proposal consisting of the following volumes (binders):
a. Phase I: Volume I – Technical Proposal, Part 1 (Factors 1-2), (electronic file)
b. Phase I: Volume II – Administrative Documents (original, no copies)
c. Electronic Requirement 1- In addition to the written binder requirement in block 13A of the SF1442, all
Offerors must provide an electronic copy of their proposals in .pdf format on a compact disc(s) (CD) for each Phase. (The electronic copy shall be separate files that are exact in color copy of the hard, original proposal).
*NOTE: Electronic copy will be used solely for administrative purposes. Hard copies will be used for evaluation and takes precedence in the case of any discrepancies between hard copy and electronic copies.
The content of these volumes is discussed in section 1.5, below.
1.3. Specific Requirements: An Offeror’s proposal shall consist of all information and material submitted in writing for evaluation in response to this solicitation. The submission of false or misleading information shall be grounds for disqualification of the proposal. The Offeror’s name, solicitation number and solicitation Closing Time and Date, must be affixed to the outside of each volume and CD. Offerors must organize their proposals as described and outlined below. Each volume must have a table of contents and a Cover Sheet to include the Offeror’s CAGE Code, address, NAICS and business size in accordance with the System for Award Management (SAM) and Point of Contact information, such as email and phone number. Each volume’s contents must be separated by tabs as discussed below. The proposals must be in an 8-1/2” x 11” format (except for organization chart, in which a folded 11” x 17” format may be used and shall be counted as one page provided the only information presented is the organization chart). Pages may be single-sided or double-sided (double-sided pages count as two pages) and must be numbered. The minimum acceptable type size is eleven (11) point with a minimum of one inch margins on all sides. The information in each volume must be organized as follows.
1.3.1. Volume I (Technical Proposal) (Factors 1-2): Offerors must submit the information identified in section 2, below. The information must be divided by tabs and shall be organized as follows:
TAB 1 - Factor 1 Past Performance/Experience TAB 2 - Factor 2 Management Capability
The total number of pages must not exceed 30 pages in the aggregate. The data appearing in Factor 1 behind the tab for 2.2.2 relating to past performance evaluations and awards, are not counted in the overall page limitation. Offerors may distribute the pages among the Factors at their discretion. If the Offeror exceeds the page limitation, then the excess page(s) after page 40 will not be evaluated (actual tabs are not included in count).
1.3.2. Volume II (Administrative Documents): The Administrative Documents must be placed in a separate envelope. It must contain the following:
a. SF 1442 (Solicitation, Offer and Award). Note - All amendments must be acknowledged in block 19;
b. Certificate of Corporate Principal/Authority;
c. Section 00 45 00;
d. Proof of Bonding Capability of at least $20,000,000;
Those Offerors selected for Phase II will have to resign the SF1442
1.4. Proposal shall be marked with the Offeror’s name, Solicitation Number, and the solicitation Closing Time and
Date. (See SF1442 Block 1 and Block 13)
1.5. https://safe.apps.mil/
Please send proposals using the link above to Contract Specialist Qiana Bowman-Spencer at qiana.l.bowman-spencer@usace.army.mil. Both Phases of the procurement shall be submitted via the above link.
ALL PROPOSALS SHALL BE SUBMITTED ELECTRONICALLY THROUGH THE SAFE SITE.
Submission shall be in searchable Adobe PDF format. You are limited to five (5) maximum files per upload (total size cannot exceed 2 GB). If you have a large number of files, it is recommend that you combine or ZIP your files before uploading to the SAFE site. Offerors may use compression utility software such as WinZip or PKZip to reduce file size and facilitate transmission.
REQUEST FOR UPLOAD CODE: Offerors must email Contract Specialist Qiana Bowman-Spencer at qiana.l.bowman-spencer@usace.army.mil no later than five (5) working days prior to the proposal due date to receive a request code which will allow for file uploads via the SAFE site. Offerors that fail to email for a request code five (5) working days before proposal submission date may not be able to receive a request code in time to upload their submission. THIS MUST BE DONE FOR BOTH PHASES OF THE PROCUREMENT.
FILE DESCRIPTION: Include a “File Description” for each file(s) you upload. The “File Description” will be included in the email notice to the recipient you choose to have access your file(s). NOTE: Do NOT enter Privacy Act Data (Personal Identification Information (PII)) in the File Description.)
Submission shall be in Adobe PDF format.
INSTRUCTIONS TO FOLLOW ON THE SAFE WEBSITE:
1. Once at the SAFE website select the “Drop-off” icon. This allows users without a CAC or users whose computer is not configured to read a CAC, the option to access the SAFE site as a guest.
2. After selecting the “Click Here” link you will be prompted to add your personal information, file information, recipient (Government representative) information and email settings.
3. When completing your file information for transmittal via the SAFE website, you will be required to enter the email address for the recipient. For this solicitation, the recipient is the Contract Specialist. The Contract Specialist for this solicitation is qiana.l.bowman-spencer@usace.army.mil. The E-Mail address of the Government Employee who initiated the request code will be automatically entered. The Proposer must enter the E-Mail address for the Contract Specialist After entering the email address, click the ADD button to add the person(s) email to the “Recipients List” of your response. When your proposal is submitted, a notification will be sent to the recipient you added.
NOTE: Do NOT send the SAFE site packages to group email accounts.
Even if you successfully upload your proposal to the SAFE site, notification will not be sent to the government recipient until you verify your email address. Entering an incorrect email may result in the rejection of your submission for lateness. A Proposer can confirm proper submission by the ‘Drop-Off Completed” screen which generates based on proper file submission.
NOTE: It has been reported that documents are more quickly uploaded into the SAFE website when using a Firefox web browser. The Government cannot verify that this is true and offers no guarantee that Offerors will have more success utilizing any particular browser.
RECEIPT OF SUBMISSIONS:
For the purposes of establishing whether a proposal submission is considered timely, the government considers the date and time the submission is completely uploaded into the SAFE website. For proposals larger than the 2GB capacity of the SAFE website and require multiple submissions, the Government will consider the date and time the last submission is completely uploaded into the SAFE website. Do not assume that electronic communication is instantaneous. It can take several minutes or even hours in some cases. The government will not be responsible for submissions delivered to any location or to anyone other than those designated to receive proposals. Offerors are responsible for ensuring that proposals are submitted so as to reach the designated recipient. Offerors are responsible for allowing sufficient time for the proposal to be received in accordance with the instructions provided.
2. SUBMISSION CRITERIA
2.1. VOLUME I – MINIMUM SUBMISSION CRITERIA (TECHNICAL PROPOSAL, FACTORS 1-2): For purposes of this solicitation, an “Offeror” may include a group of two (2) or more entities that have formed a “contractor team arrangement,” as that term is defined in the Federal Acquisition Regulation, Part 9.6. In the case of entities that have formed a contractor team arrangement, the experience and performance history of any member of the team, whether or not gained while working with the other member(s) of the currently-proposed contractor team arrangement, will be considered as a part of the evaluation of the Offeror’s proposal.
In the case of contractor team arrangements involving a prime contractor and subcontractor(s), where the prime contractor submits the proposal in response to this solicitation, the prime contractor must have completed at least fifty percent (50%) of the total number of projects that meet the requirements for Factor 1 for consideration in response to the experience requirements of this solicitation.
An Offeror that relies upon the experience and performance history of a member, members or affiliates of a proposed contractor team arrangement must provide a teaming agreement or commitment (in the case of any affiliates) signed by all parties. The Teaming agreement/commitment shall:
a. Identify the legal name(s) and cage code(s) of all entities.
b. Describe the nature of each entity’s relationship (partnership, joint venture, prime/sub or mentor/protégé) and their role on this project as a part of their proposal. The Offeror will be expected to maintain that arrangement during performance of any contract awarded to that Offeror under this solicitation.
c. The estimated percentage of work to be completed by each member submitted for the solicitation.
This can be a rough order of magnitude for Phase I; however, this agreement/letter must be resubmitted with Phase II to include that actual proposed percentages.
In the case of affiliates, past performance of an Offeror’s “affiliate,” as that term is defined in FAR 2.101, will be evaluated (as described within this section) if the Offeror demonstrates a firm commitment that the affiliate will participate meaningfully (e.g. roles, responsibilities, etc.) in the performance of the contract. This commitment, nature of each entity’s relationship and meaningful participation shall be described in a document signed by authorized representatives of both the Offeror and its affiliate. If a teaming agreement or commitment is not provided, the projects of any team members outside of the Prime Offeror will not be considered.
The contractor team agreement/commitment shall be provided at the beginning of the Offeror’s technical proposal, prior to Factor 1, and will not be included in the overall page count.
The following are to be used in determining the status of the Offeror’s team for the evaluation of project submissions under Factor 1:
In the case of contractor team arrangements involving a Prime Contractor and Subcontractor(s), where the Prime Contractor submits the proposal in response to this solicitation, the Prime Contractor is considered the “Prime Offeror”.
In the case of joint ventures, the “Prime Offeror” experience can come from any of the entities involved in the venture.
In the case of mentor/protégé relationships, the relationship must be established by the two Offerors and approved by the chosen Government Agency prior to proposal submission. Once the relationship has been approved, the “Prime Offeror” experience can come from any of the entities involved in the relationship. The approved mentor/protégé document from the Government Agency must be submitted along with the teaming agreement.
In the case of additional projects submitted by subcontractors, the subcontractor must submit the final cost of their portion of the project along with total project cost and all other required information.
In the case of Offerors that are large, multi-function firms (consisting of subsidiaries), experience must only be submitted by the segment of the firm (e.g., division, group, and unit) that is submitting a proposal in response to this solicitation.
In the case of affiliates, Past performance of an Offeror's "affiliate," as that term is defined in FAR 2.101, will be evaluated (as described within this section) if the Offeror demonstrates a firm commitment that the affiliate will participate meaningfully in the performance of the contract. This commitment and meaningful participation shall be described in a document signed by authorized representatives of both the Offeror and its affiliate.
If a teaming agreement or commitment is not provided, the projects of any team members outside of the Prime Offeror will not be considered. If the Joint Venture/Mentor Protege is a Small and Large business, the Small Business will be evaluated as the Prime Offeror.
2.2. FACTOR 1 – PAST PERFORMANCE/EXPERIENCE: The submitted material MUST be organized sequentially under tabs for each numbered section to facilitate evaluation. All narratives must contain sufficient detail to demonstrate technical capability.
2.2.1. EXPERIENCE IN RELEVANT PROJECTS: The Offeror shall submit information on at least three (3) but no more than five (5) projects completed design-build projects. If the Offeror’s submission exceeds the maximum project limitation of five completed projects, then the additional project(s) will not be evaluated.
These projects must be of relevant scope and complexity and have either a minimum project size of 70,000 Square Foot (SF) or demonstrate a minimum completion value of $11,000,000 considering adjustment for escalation from project completion to 2020 (all escalation values are to be labeled as escalated and the Offeror must explain in detail their escalation rationale, which must include any formulas, calculations, assumptions, etc.) and address the discussions requested on Attachment A while meeting the teaming agreement requirements in section 2 above. The Offeror will demonstrate experience by the successful and contractual completion of applicable projects under this factor. All projects must have a constructions completion date no earlier than six (6) years preceding the original date of issuance of this solicitation. Projects that have a Beneficial Occupancy Date (BOD) within the same date range will also be considered.
*Note: In reference to Task Order Construction Contracts (TOCCs)/Indefinite Delivery/Indefinite Quantity (ID/IQ) contracts: Task orders/delivery orders on TOCCs and/or ID/IQ contracts can also be submitted under Factor 1; however, each task/delivery order submitted must individually meet the requirements of the factor.
Submissions of multiple task/delivery orders as a project will not be accepted or evaluated.
If the Offeror’s submission exceeds the maximum project limitation of five completed projects, the first 5 projects submitted will be evaluated only, while the remaining additional project(s) will not be evaluated.
At least one project must demonstrate experience from the proposed designer. For projects demonstrating past experience from the designer, one hundred percent (100%) of the design and at least seventy five percent (75%) of the construction of each project must be completed at the time of proposal submission.
For projects demonstrating past experience for the construction contractor, one hundred percent (100%) of the construction must be complete or meet the BOD requirement above.
Relevant projects must include at least two (2) of the following elements:
At least one (1) project must demonstrate experience coordinating with Washington Headquarters
Services (WHS), the National Capital Planning Committee (NCPC), the Commission of Fine Arts (CFA), and/or the Virginia State Department of Historic resources (SHPO), Experience constructing rooftop helipads, Experience designing to airfield requirements, Experience in roof waterproof installation and remediation, Experience with high rise steel and concrete construction, Experience performing construction/renovation within occupied/functioning and secured government buildings, Experience with green roofs, Experience in complex site traffic management operations, and Historic Preservation.
*Lists, charts/matrices and bullets will not be accepted when identifying relevant elements.
Each element must have a description of how the project meets the element (e.g. concrete paving – For this project, 500 LF of concrete sidewalks were installed, 300LF of curbs were removed and re-installed, etc.).
It is the responsibility of the Offeror to identify, detail and demonstrate the relevancy of the submitted projects to the solicitation criteria elements. The evaluation committee WILL NOT make assumptions.
The information that is required to be supplied is identified on the form provided entitled “EXPERIENCE IN RELEVANT PROJECTS” (Attachment A). Offerors are not required to use the form itself as part of their proposal, but the information requested on the form must be in the Offeror’s proposal and should be in the same format as the form. Offerors may expand the form as necessary to accommodate the required project information.
The only submissions under the tab for this section are to be the completed “Attachment A” forms or similar format as indicated above. Only the information provided in either of these formats will be considered. Company summaries/introductions, project summary charts/matrices, etc. will not be accepted or evaluated.
2.2.2. PAST PERFORMANCE QUESTIONNAIRES FOR EXPERIENCE IN RELEVANT PROJECTS: Formal performance evaluations shall be provided on the relevant projects submitted in response to Section 2.2.1.
The Offeror must request that their client complete the USACE Past Performance Questionnaire for Relevant
Experience (Form PPQ-0) (Attachment B) and submit the questionnaire as part of the Offeror’s technical proposal. The Offeror may provide an explanation if the performance evaluation rating is less than satisfactory. Where applicable, the Offeror must explain facts related to any partial or completely terminated project and disclose any projects with an assessment of liquidated damages for the failure to meet the contractually required completion date. Offerors are encouraged to follow-up with clients/references to ensure timely submittal of questionnaires.
If the Offeror is unable to obtain a completed PPQ from a client for a project(s) before the proposal closing date, the Offeror must complete and submit with the proposal the first page of the PPQ-0 (Attachment B) for projects submitted under the tab for EXPERIENCE IN RELEVANT PROJECTS, which will provide contract and client information for the respective project(s).
Previously completed PPQ-0s may be submitted provided that the documents do not reference any other solicitations. Submitted PPQ-0s must only reference this solicitation. Contractor Performance Assessment Reporting System (CPARS) ratings will be accepted in lieu of PPQ-0s.
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), Federal Awardee Performance and Integrity Information System (FAPIIS), Contractor Assessment Reporting System (CPARS) or other databases using all CAGE/DUNS numbers of team members (partnership, joint venture, teaming arrangement, or parent company/subsidiary/affiliate) identified in the Offeror’s proposal;
interviews with Program Managers, Contracting Officers, and Fee Determining Officials; and the Defense Contract Management Agency. The information obtained from these sources will be evaluated supplementary to the past performance questionnaires. In reference to the contracts pulled from these sources, the relevancy of the projects, completion dates, ratings and comments in the individual categories and overall ratings will be considered in making the overall confidence assessment.
The Offeror also may provide information regarding any awards received for work done on any of the projects described by the Offeror (Copies of awards must be included under this factor for validation.).
Awards, Past Performance Questionnaires, and other past performance information will not be included in the page count for the proposal submission.
In the case of Offerors for which there is no information on past contract performance or where past contract performance information is not available, the Offeror may not be evaluated favorably or unfavorably on the factor of past contract performance (see FAR 15.305(a)(2)(iv).)
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.
2.3. FACTOR 2 – MANAGEMENT CAPABILITY: The submitted material MUST be organized sequentially under tabs for each numbered section to facilitate evaluation.
ALL narratives must be specific to the solicitation requirements (boilerplates and company histories/summaries will not be accepted) and contain sufficient detail to demonstrate management capability
It is the intent of the Government to receive proposals that clearly define and demonstrate the Offerors’ response to this factor with regard to the requested information, and considering the project information provided in Section A, while also providing the rationale for the selection of this approach to the solicited project.
2.3.1. Describe the proposed management structure for the team to include both the construction and design firms, the resources and how the resources will be utilized, their roles and responsibilities, and what subcontracting firms the Offeror is considering utilizing. Offerors are encouraged to describe prior experience working with their proposed designer.
The Offerors must also provide a statement that, in accordance with the specifications of the RFP, all individuals, including subcontractors, shall be US Citizens.
Note: The Offerors down selected to Phase II will be required to identify the specific firms chosen for structural, mechanical, fire protection, and electrical/communications installation in the Phase II proposal.
2.3.2. Describe how subcontractors are managed by the contractor to include flow-down of contract requirements, duties, responsibilities and coordination. Discuss how non-performance by subcontractors is handled by the general contractor.
2.3.3. Describe the role and interaction of the design team with the construction team during construction, addressing, as a minimum, design quality control, tracking design evolution and changes during design to meet the schedule, management of the design during construction, including control and approval of revisions to the accepted design; requests for information; shop drawing and submittal reviews and approvals; progress meetings; site visits, if any; contract completion, closeout, as-built and completion documentation.
2.3.4. Describe the Offeror’s understanding of the challenges, risks and technical approach with respect to construction/renovation of rooftop helipads on existing buildings; and coordinating with other outside contractors in order to successfully complete work on the same project. The Offeror shall provide a narrative to address the plan to proactively mitigate these challenges and risks on the solicited project. Describe the Offeror’s familiarity with Government approval procedures and knowledge of Federal and standard codes.
Describe the Offeror’s experience with installing carbon fiber reinforcement in a variety of structural configurations, including slabs with waterproof top soil overburden, and columns; and work at heights over 14 feet. Describe Designer of Record’s experience with SAFE FEA structural modeling software for stress analysis.
3. EVALUATION CRITERIA
3.1. VOLUME I - EVALUATION CRITERIA (TECHNICAL PROPOSAL, PHASE I – FACTORS 1-2)
Offerors are cautioned that “parroting” of the Technical requirements with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.
3.2. FACTOR 1 - PAST PERFORMANCE/EXPERIENCE: All submissions by Offerors must demonstrate the minimum requirements for experience in relevant projects, as stated in paragraph 2.2. above.
Past Performance evaluations will be rated in terms of performance confidence for the Government. That is, projects that are considered to be non-relevant in terms of size, scope or complexity, dollar value, percentage completion within five (5) years, responses to the Attachment A, or not meeting the teaming requirements established in section 2.2.1. (submitted under Factor 1) and demonstrating low past performance evaluation ratings will be interpreted as indicators of no confidence that the Offeror can successfully perform the work.
More relevant projects and high past performance evaluations will typically be a stronger predictor of future success and have more influence on the past performance confidence assessment than past performance of lesser relevance. Higher confidence assessments will be given for higher past performance evaluation ratings.
In the case of Offerors for which there is no information on past contract performance or where past contract performance information is not available, the Offeror may not be evaluated favorably or unfavorably on the factor of past contract performance (see FAR 15.305(a)(2)(iv).) In this case, the Offeror’s past performance is unknown and assigned a performance confidence rating of “neutral.”
3.3. FACTOR 2 – MANAGEMENT CAPABILITY: The Offeror’s narrative will meet the requirements of this RFP if the narrative is a project specific discussion that addresses the elements identified in paragraphs 2.3. in sufficient detail to demonstrate technical capability. The narrative must clearly demonstrate a reasonable approach to the contract, an understanding of the requirements of this contract and a plan that has clearly applied the information provided in paragraphs 2.3. which will lead to successful completion of all work within the contract duration. If projects do not address the above requirements, the proposal will still be evaluated; however, it may demonstrate a potential increased risk of unsuccessful contract performance.
4. EVALUATION PROCESS
4.1. Proposal Compliance Review: A proposal compliance review will be performed to ensure that all required forms and certifications are complete, that the technical proposal has been received and that the Offerors are eligible to propose. An Offeror’s failure to provide all of the requested information may adversely affect the evaluation or result in rejection of the proposal as nonresponsive.
4.2. Volume I (Technical Proposal, Factors 1-2) of the proposals will be evaluated, by the Source Selection Evaluation Board (SSEB) as established by the Source Selection Authority (SSA), based upon the factors listed below.
Offerors submitting proposals for this project should limit submissions to data essential for the evaluation of proposals. Each factor is rated individually based on the information contained in that specific factor; that is, evaluations will not be made across the factors, nor will information found in one factor be used in the evaluation of another factor. Factors 1 through 2 will be adjectivally rated. Factors 1 and 2 will be adjectivally rated. Factor 1 is more important than Factor 2.
Factor 1 - Past Performance/Experience Factor 2 - Management Capability
See section 2 above for a discussion of the evaluation criteria applicable to these factors.
Past Performance Ratings: There are three aspects to the past performance evaluation. The first is to evaluate the recency of the Offeror’s past performance. The second is to determine how relevant a recent effort accomplished by the Offeror is to the effort to be acquired through the source selection. The third aspect of the past performance evaluation is to establish the overall quality of the Offeror’s past performance.
Past Performance for Factor 1 (Past Performance/Experience) will be evaluated by examining the projects submitted under the tab for paragraph 2.2.1., Experience in Relevant Projects, to determine the relevancy of a recent effort accomplished by the Offeror and assigning one of the relevancy ratings below. These ratings will then influence the overall Confidence Assessment for Factor 1:
PAST PERFORMANCE RELEVANCY RATINGS:
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.
The following ratings will be used to identify the Government’s confidence in the Offeror’s Past Performance.
These ratings will be influenced by the relevancy ratings, above, the past performance questionnaires (PPQ-0) as well as any Past Performance Information Retrieval System (PPIRS) ratings, Federal Awardee Performance and Integrity Information System (FAPIIS) ratings, Contractor Assessment Reporting System (CPARS) ratings or other databases using all CAGE/DUNS numbers of team members (partnership, joint venture, teaming arrangement, or parent company/subsidiary/affiliate) identified in the Offeror’s proposal; interviews with Program Managers, Contracting Officers, and Fee Determining Officials; and the Defense Contract Management Agency listed for and associated with the submitted projects; and any awards received for the submitted projects:
PERFORMANCE CONFIDENCE ASSESSMENTS RATINGS:
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 report 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 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.
The following ratings will be utilized in the evaluation of Factor 2 (Management Capability):
Adjectival Rating
Description
Outstanding Proposal indicates an exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low.
4.3. Source Selection Evaluation Board: The SSEB will review the Technical Proposals against the solicitation requirements and the approved evaluation criteria to ensure an equitable, impartial, and comprehensive evaluation against the solicitation requirements. The SSEB does not compare proposals against each other. The fundamental responsibility of the SSEB is to provide the Source Selection Authority with information to make an informed and reasoned selection. The SSEB will therefore prepare a summary report containing adjectival assessments for each factor and their supporting rationale, for each Offeror (in phase II); brief the SSA; and prepare any necessary items for discussion.
4.4. Phase I Down Select: After all of the evaluations described above have been completed, the SSA will consider all factors to determine which Offerors submitted the proposal that represents the best value to the Government for this project. The SSA will compare the proposals to determine the offers that represent the best value to the Government, taking into consideration the stated evaluation factors and their respective weightings as specified in the RFP. The selection process is complex and depending upon the evaluation factors, the SSA may exercise a significant degree of judgment in selecting the Offerors. The adjectival ratings assigned by the evaluation team are labels and not the sole basis for proposal comparison. The SSA will not base his/her decision merely on the adjectival ratings or the comparative analysis and recommendations, which compares the strengths and weaknesses of the competing proposals, but shall exercise independent judgment.
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 .