3 - PP Reference List.docx
DOCX document 20 KB Posted
- Attached to
- Blanket Purchase Agreement for Pavement Marking
- Solicitation number
- FA520924Q0024
About this file
This document is a Past Performance Reference List submitted as part of a Request for Quote (RFQ) for a Blanket Purchase Agreement for Pavement Marking services. The RFQ, solicitation number FA520924Q0024, is being issued by the Department of the Air Force Pacific Air Forces.
The Past Performance Reference List requires the offeror to provide details on three (3) relevant contracts performed within the last 3 years, including the company/division name, project name, contracting agency/customer, contract number, contract dollar value, period of performance, contracting officer contact information, comments on compliance with contract terms, and a rationale for the relevance of the referenced work to the proposed effort. The key details of the federal contract opportunity indicate the work includes removing and placing pavement markings on airfield, roadway, and parking lot pavements, as well as crack sealing asphalt pavements. The solicitation has a question due date of April 20, 2024 and a proposal due date of May 13, 2024.
View the file
Other files
Show all 14
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
Attachment 3 RFQ No. FA520924Q0024
PAST PERFORMANCE REFERENCE LIST
Name of Offeror:
The following Three (3) contracts are the most relevant contracts (similar in scope, size and complexity) performed for US Government agencies, Government of Japan, and Commercial customers performed within the last 3 years of the RFQ release date, or is currently in progress:
Contract No. 1
| (1) | Company/Division name |
| (2) | Project Name |
| (3) | Contracting Agency/Customer |
| (4) | Contract Number |
| (5) | Contract Dollar Value |
| (6) | Period of Performance |
| (7) | Verified, up-to-date name, mailing and e-mail addresses, and telephone number of the contracting officer (Point-of-Contact) |
| (8) | Comments regarding compliance with contract terms and conditions |
| (9) | Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions. |
| (10) | Include rationale supporting your assertion of relevance and identify aspects (scope, magnitude of effort, and complexity) of the contracts deemed relevant and how they relate to the proposed effort. |
Contract No. 2
| (1) | Company/Division name |
| (2) | Project Name |
| (3) | Contracting Agency/Customer |
| (4) | Contract Number |
| (5) | Contract Dollar Value |
| (6) | Period of Performance |
| (7) | Verified, up-to-date name, mailing and e-mail addresses, and telephone number of the contracting officer (Point-of-Contact) |
| (8) | Comments regarding compliance with contract terms and conditions |
| (9) | Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions. |
| (10) | Include rationale supporting your assertion of relevance and identify aspects (scope, magnitude of effort, and complexity) of the contracts deemed relevant and how they relate to the proposed effort. |
Contract No. 3
| (1) | Company/Division name |
| (2) | Project Name |
| (3) | Contracting Agency/Customer |
| (4) | Contract Number |
| (5) | Contract Dollar Value |
| (6) | Period of Performance |
| (7) | Verified, up-to-date name, mailing and e-mail addresses, and telephone number of the contracting officer (Point-of-Contact) |
| (8) | Comments regarding compliance with contract terms and conditions |
| (9) | Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions. |
| (10) | Include rationale supporting your assertion of relevance and identify aspects (scope, magnitude of effort, and complexity) of the contracts deemed relevant and how they relate to the proposed effort. |
FOR OFFICIAL USE ONLY
File details come from the government source that posted it. Updated .