Evaluation_Factors.pdf
PDF 31 KB Posted
- Solicitation number
- N4008313R0032
About this file
Evaluation factors for award
View the file
Other files
| File | Type | Posted |
|---|---|---|
| N40083-13-R-0032_Amend_09.pdf | ||
| N40083-13-R-0032_Amend_08.pdf | ||
| N40083-13-R-0032_Amend_07.pdf | ||
| Grand_Forks_RFI_Response.pdf | ||
| N40083-13-R-0032_Amend_06.pdf | ||
| Evaluation_Factors_Rev_3_dtd_9-10.pdf | ||
| Evaluation_Factors_Rev_2_dtd_9-10.pdf | ||
| N40083-13-R-0032_Amend_05.pdf | ||
| Evaluation_Factors_Rev_9-10.pdf | ||
| N40083-13-R-0032_Amend_04.pdf | ||
| Grand_Forks_Cost_Breakdown.xls | XLS spreadsheet | |
| N40083-13-R-0032_Amend_03.pdf | ||
| Evaluation_Factors_FINAL.pdf | ||
| RFI_Responses_Grand_Forks.pdf | ||
| Grand_Forks_SF-30_01.pdf | ||
| N40083-13-R-0032_Amend_1.pdf | ||
| Past_Performance_Questionnaire.doc | DOC document | |
| FORM_-_Contractor_RFI_Form.xls | XLS spreadsheet | |
| N4008313R0032.pdf | ||
| Specifications.pdf | ||
| Instructions_to_Offerors.pdf | ||
| Drawings.pdf | ||
| Grand_Forks_Wage_Determination.pdf |
Show all 23
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
Non-Cost/Price Evaluation Factors:
This procurement is being competed under best value, low price technically acceptable practices. A rating of Unacceptable in any one factor results in the overall technical proposal being rated as Unacceptable. The relative order of importance of the non-cost/price evaluation factors is that technical factors are equal to each other. The combined non-cost/price factors are approximately equal to price.
Factor 1 – Technical Approach Factor 2 – Past Performance Factor 3 – Technical Solution
Factor 1 – Technical Approach:
(a) Solicitation Submittal Requirements:
The composition and management of the firms proposed as the design-build (DB) team for this contract will be evaluated in this factor.
The Offeror shall submit the following information:
(1) Provide a narrative describing the proposed primary construction firms and primary design firms for this contract and the rationale for proposing this arrangement.
Provide the role, responsibilities, and contractual relationships between the various firms (see FAR Subpart 9.6). The narrative shall also include a simple organizational chart that clearly identifies the lines of authority between the entities.
The technical approach narrative shall be limited to one (1) double-sided page (or two
(2) single-sided pages) including the organizational chart. The information requested in item #2 below is not included in this page limitation.
(2) In addition to the narrative, the Offeror shall submit a signed copy of a joint venture agreement, partnership agreement, teaming agreement, or letter of commitment for each member of the Offeror’s team identified above (e.g., joint venture partner, partner, team member, subcontractor, parent company, subsidiary, or other affiliated company, etc.).
(b) Basis of Evaluation:
The assessment of the Offeror’s technical approach will be used as a means to evaluate the organizational structure and teaming relationships proposed by the Offeror.
This factor will be rated on an Acceptable or Unacceptable basis.
Factor 2 – Past Performance:
If a completed Construction Contractor Appraisal Support System (CCASS) evaluation is available, it shall be submitted with the proposal for each project included in factor 2 for construction experience. If a completed AE Contractor Appraisal Support System (ACASS) evaluation is available, it shall be submitted with the proposal for each project included in factor 2 for design experience. The Offeror should provide completed Past Performance Questionnaires (PPQ) in the proposal. Offerors shall not incorporate by reference into their proposal PPQs previously submitted for other RFPs. However, this does not preclude the Government from utilizing previously submitted PPQ information in the past performance evaluation. If the Offeror is unable to obtain a completed PPQ 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, which will provide contract and client information for the respective project(s). The Government may make reasonable attempts to contact the client noted for that project(s) to obtain the PPQ information.
However, Offerors should follow-up with clients/references to help ensure timely submittal of questionnaires. If the client requests, questionnaires may be submitted directly to the Government’s point of contact, Ken Seymour at Kenneth.d.seymour@navy.mil
Offerors may also address any adverse past performance issues. Explanations shall not exceed two (2) double-sided pages (or four (4) single-sided pages) in total.
The Government reserves the right to contact references for verification or additional information. The Government’s inability to contact any of the Offeror’s references or the references unwillingness to provide the information requested may affect the Government’s evaluation of this factor.
Performance award or additional information submitted will not be considered.
(b) Basis of Evaluation:
This evaluation focuses on how well the Offeror performed on past performance on other projects currently documented in known sources. In addition to the above, the Government reserves the right to obtain information for use in the evaluation of past performance from any and all sources including sources outside of the Government.
Other sources may include, but are not limited to, past performance information retrieved through the Past Performance Information Retrieval System (PPIRS) using all CAGE/DUNS numbers of Contractors who are part of a partnership or joint venture identified in the Offeror’s proposal, inquiries of owner representative(s), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), and any other known sources not provided by the Offeror.
The Government will consider the currency and relevance of the information, the source of the information, context of the data, and general trends in the Contractor’s performance. This evaluation is separate and distinct from the Contracting Officer’s responsibility determination. The assessment of the Offeror’s past performance will be used as a means of evaluating the Offeror’s probability to successfully meet the requirements of the RFP.
Offerors lacking relevant past performance history will not be evaluated favorably or unfavorably in past performance and will receive an Acceptable rating.
Factor 3 – Technical Solution
Provide a narrative describing the technical solution to the project that meets the requirements of the RFP. Include the following:
- Interior circulation/adjacencies
- Exterior façade describing how the proposed construction integrates with the surrounding area and existing base facilities design or architectural theme.
- Site layout including a description of the building orientation, roadways, parking
(include ingress and egress), emergency vehicle access, and ATFP standoff distances. Also include in the narrative a description of the general concept proposed to meet low impact development (LID).
Narrative shall not exceed three (5) double-sided pages (or ten (10) single-sided pages). Up to three (3) conceptual drawings may be provided to supplement the narrative (i.e. floor plan, exterior elevation, and site plan).
(b) Basis of Evaluation:
The Government will evaluate the narrative and conceptual drawings (if included) considering the extent to which the Offeror demonstrates a clear understanding of the architectural and engineering requirements of the project. The Government will evaluate the Offeror's technical solution to determine adherence to the technical requirements of the RFP.
File details come from the government source that posted it. Updated .