Attch_10_PPIS_COM-F_III.docx
DOCX document 34 KB Posted
- Attached to
- Communications, Operations, and Maintenance Functions (COM-F) Federal contract opportunity
- Solicitation number
- FA4452-18-R-0037
About this file
Attch 10 Past Performance Information Sheet
View the file
Other files for this federal contract opportunity
Show all 31
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
FA4452-18-R-0037
COM-F III IDIQ
Initial GDSS Task Order Attachment 10
Initial GDSS Task Order Past Performance Information Sheet (PPIS)
Version 1.0
Communications, Operations, & Maintenance Functions (COM-F)
Procuring Office: 763d Specialized Contracting Squadron (763 SCONS)
| 510 POW/MIA Drive |
| Building P40 |
| Suite E1001 |
| Scott Air Force Base, IL 62225-5420 |
Requiring Office: HQ AMC Directorate of Operations and Training Division (A6I)
203 West Losey Street Room 3610 Scott Air Force Base, IL 62225
Project Management Office: 375th Communication Support Squadron (CSPTS) 859 Buchannan Street Scott Air Force Base, IL 62225
02 Jan 2019
Past Performance Information Sheet
SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104
FOR OFFICIAL USE ONLY
Provide the information requested in this form for each contract/program (citation) being described. Provide frank, concise comments regarding your performance on the contracts you identify. Provide a separate completed form for each contract/program submitted. Limit the number of citations submitted and the length of each submission to the limitations set forth at paragraphs 1.2 and 3.2.5, respectively, of Instruction to Offerors of this solicitation.
If the contract being submitted is an ordering type contractual vehicle (for example, including but not limited to an Indefinite Delivery “D” type contract per FAR 16.5), only after issuance of a delivery/task order does performance occur. The Contract Number, Total Contract Dollar Value, Period of Performance, Quantities Produced/Repaired, Type and Complexity of Data Deliverable submitted here should be for the order or series of orders, the offeror has performed under this ordering type contractual vehicle.
If a series of orders is being submitted, the offeror shall include a list that includes the order numbers, each order’s Total Contract Dollar Value, each order’s Period of Performance, each order’s Quantity Produced/repaired, and the Type and Complexity of Data Deliverables on each order. If the series of orders contains more than 5 orders, include this information on a separate attachment. See Section Instruction to Offerors for more information on proposal submission and Addendum to 52.212-2 Evaluation of Commercial Items for evaluation information.
A. OFFEROR:
(1) Name (Company/Division)
(2) Address
(3) CAGE Code
(NOTE: If the company or division performing this effort is different than the offeror or the relevance of this effort to the instant acquisition is impacted by any company/corporate organizational change, note those changes. Refer to the "Organizational Structure Change History" you provided as part of your Past Performance Volume).
B. PROGRAM/PROJECT TITLE and CONTRACT NUMBER:
(If submitting ordering type contract: List the basic contract number and each order number or order number within the series of orders) C. Role of the Offeror In Effort: __________ Prime Contractor __________ Subcontractor
Note that the information provided in the PPIS Sheet shall reflect the role that the offeror/joint venture member/critical subcontractor performed in the effort, i.e., an offeror who performed as a subcontractor shall identify the contract type, dollar value, description, etc. of its subcontract with the prime contractor.
D. NAME OF CONTRACTING ACTIVITY OR CUSTOMER:
E. CONTRACT TYPE(S) – CHECK ALL THAT APPLY
a. Firm Fixed Price _____
b. Time and Materials _____
c. Cost _____
d. Other (Explain)
F. TOTAL CONTRACT DOLLAR VALUE: (If you performed work as a subcontractor, identify your total contract dollar value and the PRIME’s total contract dollar value, if known. Describe any changes in dollar value that may have occurred from time of contract award to the conclusion of the effort or the present, whichever is applicable.) If submitting an ordering type contract, list the original and current total contract dollar values for each order or order within the series of orders. If your series of orders consists of more than five (5) individual orders include the information in a separate attachment.
1. Original Total Contract Dollar Value:
(If submitting ordering type contract: List the original total contract dollar value for each order or order within the series of orders)
2. Current Total Contact Dollar Value:
(If submitting ordering type contract: List the current total contract dollar value for each order or order within the series of orders)
3. Explain the differences in Total Contract Value, if applicable: Enter an explanation of the difference between the Original Total Contract Dollar Value and the Current Total Contract Dollar Value as of the time of proposal submission.
4. If Award Fee Contract, what percentages of the fee have been awarded in each of last 3 years?
G. PERIOD OF PERFORMANCE: (includes start and end dates, i.e. Jan 2004 – Dec 2007) If submitting an ordering type contract, the “Period of Performance” submitted here should be for the order (or series of orders), the offeror has performed under this ordering type contractual vehicle. The offeror shall submit the “Start Date” for the individual order or the first order in the series. The offeror shall submit the “Original End Date” for the individual order or the last order in the series. If the “End Date” on the individual order or last order within the series of orders has changed, these changes would need to be reflected in the “Current End Date” Section below. Also, if submitting a series of orders, list the Start Date, Original End Date and Current End Date for each order. If your series of orders consists of more than 5 individual orders include the information in a separate attachment.
1. Start Date: Input start date of contract/order/series of orders.
2. Original End Date: Input original end date of contract/order/series of orders based on award.
3. Current End Date (if changed): Input end date, as the contract/order/series of orders stands at time of proposal submission.
H. PRIMARY POINTS OF CONTACT: (The offeror/joint venture member/critical subcontractor is responsible for exerting its best efforts to ensure that current information is provided for all individuals.)
| Name and Office Symbol |
| Phone Number |
| FAX Number |
| 1. Procuring Contracting Officer |
| DSN & Comm |
| DSN & Comm |
| 2. Program Manager |
| DSN & Comm |
| DSN & Comm |
| 3. Administrative Contracting Officer |
| DSN & Comm |
| DSN & Comm |
| 4. Other (Please Specify) |
| DSN & Comm |
| DSN & Comm |
I. Address any aspect about this program considered unique. Describe quality awards or certifications that indicate the offeror possesses a high-quality process for developing and producing the product/service required.
J. For each of the applicable sub-factors under the Technical factor in Addendum to 52.212-2 Evaluation of Commercial Items, illustrate how your experience on this program applies to that sub-factor.
K. Specify, by name, any key individual(s) who participated in this program and are proposed to support the instant acquisition. Also, indicate their contractual roles for both acquisitions.
L. Describe the nature and portion of the work on the proposed effort to be performed by the business entity being reported here. Also, estimate the percentage of the total proposed effort to be performed by this entity and whether this entity will be performing as the prime, subcontractor, or a corporate division related to the prime (define relationship).
M. Summarize contract issues relative to the number and severity of quality deficiencies recorded/contract discrepancy reports issued, cure notices, show cause letters, termination for default or cause, disputes, claims, latent defects; and, corrective actions taken for the contract listed in Paragraph B above.
N. Additionally, for those efforts where you are cognizant of unfavorable and/or marginal past performance ratings/reports previously assessed by customers or clients, but feel that significant progress has been made but not yet credited or formally documented, provide the program name, contract number, customer location and a narrative explaining "fixes" made to date, or any other information regarding the unfavorable/marginal assessment. This narrative portion is limited to one (1) additional page beyond the FA sheet required page limitation. It is not presumed that performance has been perfect. Rather, the proposal should contain evidence of the offeror's/joint venture member’s/critical subcontractor’s ability to isolate the root causes of problems and should describe programs or actions taken to resolve those causes. Demonstrated corrective actions (not just planned or promised), and the overall work record will be considered. Problems not addressed, but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of Contractor Performance Assessment Report System (CPARS), if your input has already been provided and the rationale/ circumstances have not changed, DO NOT repeat them here.
O. Was this contract effort (as identified in paragraph B. above) submitted as a past performance source of data for a previous procurement. Yes No . If yes, identify the buyer and/or contracting officer, their phone number and office symbol and solicitation number of the procurement for which this effort was submitted.
P. Describe additional information you deem pertinent.
PLEASE NOTE: The Government is not bound by the offeror's opinion of relevancy. The Government will perform an independent assessment of relevancy of the data provided or obtained.
SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104
FOR OFFICIAL USE ONLY
File details come from the government source that posted it.