Attachment_11_-_QASP.PDF
PDF 908 KB Posted
- Attached to
- Link-16 Alaska Federal contract opportunity
- Solicitation number
- FA8574-19-R-0002
About this file
This Quality Assurance Surveillance Plan outlines the requirements for contractor logistics support services for the Link-16 Alaska communications system. The services include program management, cybersecurity support, help desk services, training, equipment repair, software updates, and configuration management. Key performance objectives include responding to help desk calls within 24 hours, arriving on-site for unscheduled maintenance within 48 hours, and notifying the government of any cybersecurity vulnerabilities within 24 hours. The plan establishes procedures for monitoring contractor performance against standards. It identifies roles for the multi-functional team, including the contracting officer's representative who will issue quarterly performance assessment reports. The contractor must address any deficiencies identified and the government may issue corrective action reports if needed. The performance assessments will also feed into the contractor performance assessment reporting system.
QASP
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
PR: FD2060-18-34116 QASP REVISION: 0 1
Quality Assurance Surveillance Plan
For
LINK-16 ALASKA (LAK) AN/FSQ-228
Communications Control Set
Purchase Request: FD2060-18-34116
07 March 2019
PR: FD2060-18-34116 QASP REVISION: 0 2
1.0 Purpose
This Quality Assurance Surveillance Plan (QASP) is a government-developed document used to determine if the contractor’s performance meets the performance standards contained in the contract. The QASP establishes procedures on how this assessment/inspection process will be conducted. It provides the details associated with a continuous oversight process, to include:
• What will be monitored
• How monitoring will take place
• Who will conduct the monitoring
• How monitoring efforts and results will be documented
1.1 The contractor is responsible for implementing and delivering performance that meets contract standards using its own quality control plan. The QASP provides the structure for the government’s surveillance of the contractor’s performance to ensure that it meets contract standards. It is the government’s responsibility to be objective, fair and consistent in evaluating contractor performance.
1.2 The QASP is not part of the contract nor is it intended to duplicate the contractor’s quality control plan. This QASP is a living document. Flexibility in the QASP is required to allow for an increase or decrease in the level of surveillance necessary based on contractor performance.
Copies of the QASP and any revisions shall be provided to the contractor and the Contracting Officer's Representative (COR) to facilitate implementation of surveillance activities. In addition, the QASP should recognize and accommodate unforeseen or uncontrollable circumstances which might occur that are outside the control of the contractor.
1.3 Objective(s)
This Quality Assurance Surveillance Plan (QASP) is a government document used to make sure systematic quality assurance methods are used in the administration of the Performance Based Service Contract (PBSC) standards included in this contract and in subsequent task orders. The services required to support the Link-16 Alaska (LAK) system which contributes to the security of the United States through the use of the secure, digital, jam-resistant Link-16 network which takes the radar air picture and promulgates it to fighter aircraft allowing them to see the full scope of enemy and friendly aircraft in his vicinity over the austere Alaskan air space. This infrastructure is hosted by the 611th AF Joint Interface Control Cell (JICC) and supports Alaskan North American Aerospace Defense Command (NORAD) Region (ANR), Alaskan Command (ALCOM), and Joint Task Force (JTF)-AK command and control (C2) of air sovereignty, air defense, and homeland defense missions. LAK uses sixteen Line of Sight (LOS) Multifunctional Information Distribution System Low Volume Terminals (MIDS LVT)-3, using ultra high frequency (UHF) radio frequency (RF) waveform, to provide the coverage necessary for the Area of Responsibility (AOR). LAK is unique in its ability to remotely key the crypto for the MIDS (Link-16) radio terminals to ensure message security.
1.4 Result(s)
The Contractor shall provide Help Desk Support, Scheduled and Unscheduled Maintenance, Program Management, Engineering Services, Software Updates, Government Furnished
PR: FD2060-18-34116 QASP REVISION: 0 3
Equipment (GFE) management, Information Assurance (IA), Technical Orders, Drawings, Deficiency Reporting, Configuration Control of design and functional capabilities Diminishing Manufacturing Sources and Material Shortages (DMSMS) management, Training, and Travel for the Link-16 LAK program. The Contractor shall return systems to serviceable condition to the latest hardware configuration approved and funded by the Government. The Contractor shall determine the most cost effective means of repair for the system consistent with meeting required system performance criteria and availability of technical data spares. National Stock Numbers and Part Numbers are subject to change as the baseline changes at the system level. Such configuration changes may drive Contract Line Item Number additions and/or deletions, as mutually agreed to between the government and contractor. Functional capabilities shall not be changed, modified, or altered except when an Engineering Change Proposal (ECP) has been submitted by the contractor and approved by the Government.
The QASP is used for managing contractor performance assessment by ensuring that systematic quality assurance methods validate that contractor quality control efforts are timely, effective, and are delivering the results specified in the contract or task order. The QASP directly corresponds to the performance objectives and standards specified in the PWS. It provides specific details on how the Government will survey, observe, test, sample, evaluate, and document contractor performance results to determine if the contractor has met the required performance standards for each objective in the PWS. Successful completion of the objectives for the performance of the contract constitutes success of the program.
1.5 Authority
Generally, Authority for issuance of this QASP is provided under Part 46 of the Federal Acquisition Regulation, Inspection of Services clauses, which provide for inspection, acceptance and documentation of the service called for in the contract or order. If commercial, quality assurance will be applied in accordance with commercial items clause.
2.0 Assessment Management
2.1 Services Summary
PERFORMANCE
OBJECTIVE
PWS
REFERENCE
PERFORMANCE
THRESHOLD
METHOD OF
SURVEILLANCE
Help Desk 4.2.1 The prime Contractor shall provide Subject Matter Expert (SME) support for all Help Desk calls. The prime Contractor shall respond to 99% of calls (initial response) within 24 hours.
The contactor shall provide a resolution within 2 calendar days. Requests for assistance and actions taken shall be logged into a maintenance database and provided to the
List of calls logged into the maintenance database will be reviewed by the COR(s) monthly.
Surveillance will be documented, at a minimum, quarterly by the COR in the
PAR.
PR: FD2060-18-34116 QASP REVISION: 0 4
Program Office in the Monthly Status Report (MSR). MSR shall provide monthly and annual maintenance totals to include number of help desk calls, trouble tickets, repair actions, LRUs, location, and response/repair time.
Unscheduled Maintenance
4.2.2 The prime Contractor shall
provide unscheduled maintenance support for all LAK sites. The prime Contractor shall arrive to LAK site(s) within 48 hours. Within an additional 48 hours, the Contractor shall determine cause of fault/problem and restore that site to full operational capability. It is anticipated that there will be 4 unscheduled maintenance visits annually. If unscheduled maintenance exceeds 4 visits, it will be considered over and above and will be negotiated before issuance of an order.
Surveillance will be conducted upon receipt by the COR reviewing the Monthly Status Report of how many trips occurred and the fix action and the time it took for the prime Contractor to determine a cause and fix action.
Surveillance will be documented, at a minimum, quarterly by the COR in the
PAR.
Hardware Repair and Cleaning
4.7.2 Contractor will e-mail a listing
of all items receipt-in for repair to the Program Management Office (PMO) (AFLCMC/WNY) and the Procurement Contracting Officer (PCO) (AFLCMC/WNKE), no later than 2 business days upon arrival of property at Contractor facility.
Surveillance will be conducted upon receipt by the COR reviewing the Monthly Status Report. To determine if the the Prime Contractor notify the PCO within two business of receipt of items for hardware repair and cleaning.
Surveillance will be documented, at a minimum, PAR.
Maintenance and repair of items
4.7.3 The Contractor will perform
final Acceptance testing of each LAK LRU process under CLS prior to returning it to the Government. The required Turn Around Time (TAT) is no more than 60 calendar days after determination that item is
List of items repaired along with final inspection report will be tracked through Monthly Status Reports (MSR) by serial, part, and stock number by COR(s) quarterly.
Surveillance will be
PR: FD2060-18-34116 QASP REVISION: 0 5
not over 75% of acquisition Cost making it uneconomical to repair.
documented, at a minimum, quarterly by the COR in the
PAR.
Expedited repair and shipment of Critical items
4.7.3 The Contractor shall respond to
the the PMO (AFLCMC/WNY) and the PCO (AFLCMC/WNKE) within one
(1) business day upon receipt of critical items or Mission Impaired Capability Awaiting Parts (MICAP) and coordinate the time required to repair the item and/or support sustainment surge or MICAP requirements.
List of items repaired along with final inspection report will be tracked through Monthly Status Reports (MSR) by serial, part, and stock number by COR quarterly.
Surveillance will be documented, at a minimum, quarterly by the COR(s) in the PAR.
Configuration control of design and Functional capabilities
4.8.2 The Contractor shall maintain
updated Configuration Management (CM) in support of hardware, software, lab, and documentation.
A list of all Configuration changes made to the sytem both hardware and software shall be submitted to the government within 60 days action notifying the government of same changes to the system.
List of configuration changes will be tracked through Monthly Status Reports (MSR) by COR(s) quarterly.
Surveillance will be documented, at a minimum, quarterly by the COR in the
PAR.
Cybersecurity 4.9.3 The Contractor shall notify the Government PMO/Information Systems Security Manager (ISSM) within 24 hours of the vulnerability and a recommended course of action.
The Contractor along with the Government shall work together to determine a solution. The Contractor shall implement the solution within 30 calendar days.
Surveillance will be conducted upon receipt by the COR reviewing the Monthly Status Report. The number of vulnerabilities report to the ISSM, date and time they occurred and receommend fix action
Surveillance will be documented, at a minimum, quarterly by the COR in the
PAR.
Submission of Engineering Change Proposal
(ECP)
6.1.3 The Contractor shall submit an
ECP for all Class 1 changes to the baseline configurations (Appendix B). The ECP submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes. The
A list of all ECPs both Class 1 and 2 shall be submitted to the PMO for approval of ECP Class prior to making any Configuration Changes.
Surveillance will be documented, at a minimum, PR: FD2060-18-34116 QASP REVISION: 0 6
Contractor shall notify the Government of all proposed Class 2 changes (including items not in Appendix B), including all substitute parts changes, through Document Change Notices (DCN) within 15 calendar days of identified need for changes. Government shall conur/non-concur and will provide expected ECP format upon need/request.
PAR. The PAR will indicated the number of calendar days it took the Prime Contractor to notify the government.
2.2 COR File Documentation
The COR will establish and maintain an online file containing training and surveillance documentation (COR Profile and COR Online File in the CORT Tool) in accordance with DFARS PGI 201.602-2(d)(vi); AFFARS MP5301.602-2(d)2.4; and the USD Memorandum, dated Mar 21 2011. At a minimum the following documentation will be uploaded in the CORT Tool by the COR or PCO as applicable.
a. Training and Appointment DAU CLC 222 Contracting Officers Representative (COR) Online Training DAU CLM 003 Overview of Acquisition Ethics DoD Combatting Trafficking in Persons for Acquisition & Contracting Professionals Wide Area Workflow training/iRAPT Overview QAPC-Led Training (Level C) Contract-Specific Training Refresher training
b. QASP
c. Designation of Contracting Officer’s Representative
d. Annual COR File Inspection Checklist(s)
e. COR ONLINE FILE:
i. COR Status Reports/Surveillance:
PAR(s) CAR(s) Initial Contract Performance Review (30-Day Review) Annual COR File Inspection Checklist(s)
ii. COR Trip Reports (if applicable):
iii. COR Correspondence Reports:
Meeting Minutes
PR: FD2060-18-34116 QASP REVISION: 0 7
Contractor correspondence
iv. Miscellaneous Documents:
Contract, including modifications (if not in EDA) PWS, including revisions (if not in EDA) Amended QASP DD Form 254 (if not in EDA) CDRL(s) (if not in EDA) CDRL/Deliverables (if not in WAWF) Contractor Safety Plan Applicable status report(s) Master/Delivery Schedules Customer Complaint Records CAV-AF Repair Item Actions Report(s) iRAPT report(s) and/or other documentation of Contractor payment (if not in WAWF)
2.3 Plan for Corrective Action
2.3.1 Unsatisfactory Contractor performance will result in the COR issuing a negative PAR.
The COR will prepare and forward the negative PAR to the PCO for submission to the Contractor. The PCO will submit the negative PAR to the Contractor for corrective action. In Section II of the negative PAR, the Contractor shall explain the discrepancy and identify the corrective action they shall take to resolve the discrepancy and prevent recurrence. The Contractor shall sign and return the negative PAR to the PCO by the suspense date(s) applicable to each PAR. The COR will upload the negative PAR in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vi)(B).
2.3.2 If repetitive negative PARs or a single negative PARs or a single negative PAR identifying critical Contractor non-compliance are issued without satisfactory resolution, the COR will initiate the CAR process. However, the MFT reserves the right to issue a CAR at any time based on the severity of the Contractor non-compliance. The COR will prepare a CAR and forward it to the QAPC. The QAPC will assign a control number and forward the CAR to the PCO and courtesy-copy the COR. The PCO will set a suspense date and submit the CAR to the Contractor for corrective action. The Contractor shall sign and return the CAR, with a corrective action plan, to the PCO for acceptance by the MFT by the suspense date. The corrective action will be tracked and documented until the discrepancy/deficiency is resolved. The COR will notify the QAPC that the CAR has been closed. The COR will upload the CAR in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vi)(B). The CAR will become part of the PCO contract file. If the CAR process fails to resolve the discrepancy, the PCO has the right to invoke remedies based on clause(s) included in the contract.
2.3.3 CORs shall establish a tracking system for corrective actions that includes date COR submitted CAR to PM/FSM, date reviewed by PM/FSM, date reviewed by CO, date issued by CO, contractor’s identified root cause, proposed corrective action, contractor follow-up actions, and get-well date.
PR: FD2060-18-34116 QASP REVISION: 0 8
2.4 Acceptance of Services
2.4.1 The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT). Services will be accepted by the PM/COR.
2.4.2 CDRL deliverables may be submitted using iRAPT or be submitted directly to the MFT member identified on the CDRL. The CDRL will determine submittal requirements; however, separately priced data must be accepted in iRAPT in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in iRAPT in order for the contract line item to be closed out.
3.0 Roles andResponsibilities of Multi-Functional Team (MFT)
Link-16 Alaska (LAK) IPT Members Name Title Office Symbol John Bryant Program Manager AFLCMC/WNY Brad Cox Cybersecurity Lead AFLCMC/WNY Martin Okaiwele Engineer AFLCMC/WNY Charlese Kelley Equipment Specialist AFLCMC/WNY Lauren Griffin Contracting Officer AFLCMC/WNKE Anna McCarthy Contracting Specialist AFLCMC/WNKE Angela Knight Production Management Specialist AFLCMC/WNY Brianna Hancock Financial Manager AFLCMC/WNY
3.1 General Responsibilities
3.1.1 The MFT is responsible for ensuring the acquisition utilizes Performance-Based Service(s) Acquisition (PBSA) methods including establishment of performance thresholds, procedures to evaluate Contractor performance and positive/negative incentives to encourage the highest quality of services.
3.1.2 The MFT is responsible for conducting surveillance of Contractor performance to ensure Government requirements including quality of services, cost and schedule are met. The MFT will provide the results of their surveillance to the Contracting Officer’s Representative (COR) for input into the Performance Assessment Report (PAR) and to the MFT member updating the Contractor Performance Assessment Reporting System (CPARS).
3.1.3 For contracts requiring higher-level quality requirements, the MFT is responsible for developing metrics in tracking the effectiveness of the contractors Quality Management System (QMS) that tie to the SS, QASP, and CPARS. Ensure contracts requiring higher-level contract quality requirements include a SS performance objective that encompasses MFT goals related to quality directly relates to the CPARS category of “Quality”.
3.1.4 The MFT ensures contract oversight focuses on the adequacy and adherence of the contractor to their proposed QMS. The MFT shall focus on whether the COR or contractor is first in detecting defects and trends, who (COR or contractor) accomplishes more inspections, PR: FD2060-18-34116 QASP REVISION: 0 9 and, whether the contractor is proactively pursuing key QMS functions to ensure quality related problems or defects do not recur.
3.2 Contracting Officer’s Representative (COR)
3.2.1 Registers in Wide Area Workflow (WAWF) as a Contracting Officer Representative Tracking (CORT) Tool user. Self-nominates in the CORT Tool as the designated COR for the contract. If required, files an Office of Government Ethics (OGE) Form 450, Confidential Financial Disclosure Report. Establishes and maintains an online file containing training and surveillance documentation (COR Profile and COR Online File in the CORT Tool).
3.2.2 Registers for an Enterprise Contractor Manpower Reporting Application (eCMRA) account after designation as a COR. No later than 60 calendar days after contract/order award, verifies the Contractor has established a record for the contract/order in eCMRA. Reviews and, if required, corrects the Contractor record (Order Data, Contact Data, Location Data, etc.). Enters the National Defense Authorization Act (NDAA) Elements and the Fund Cite Data. Verifies the Contractor has reported all data for each fiscal year, including an annual count of contractor/subcontractor personnel performing services and the total of contractor/subcontractor labor hours, no later than October 31 of the following fiscal year.
3.2.3 Works with the MFT in conducting and documenting surveillance on Contractor performance. Reports unethical conduct and instances of fraud, waste and/or abuse to the Procuring Contracting Officer (PCO). Inspects and accepts/rejects deliverables during contract/order performance and at close-out to ensure contract/order terms and conditions are met. Develop an inspection schedule that shall comprise of at least ten percent of non-services summary items, but no more than twenty percent. Monitors control and disposition of Government property. Monitors Contractor payment and verifies it is commensurate with Contractor performance. Documents Contractor performance via PARs, Corrective Action Report(s) (CAR), etc. Issues PARs, at a minimum, quarterly and negative PAR(s) or CAR(s) as required.
3.2.4 Ensure contractor’s accepted Quality Management System (QMS) complies with contract requirements. In post award, CORs need to place special emphasis in ensuring the contractor’s QMS is being followed as written, plus is effective in bringing about the desired results – performance equal to or greater than the SS metrics, plus an inspection and corrective action program that identifies and fixes issues without having to be identified by the Government.
3.3 Contracting Officer’s Representative (COR) Supervisor
3.3.1 Upon PCO request for COR support, selects a qualified nominee. Confirms the COR nominee has no personal conflicts of interest with performing the responsibilities to be delegated by the PCO. Verifies the COR nominee has the appropriate clearance for the contract/order. If required, ensures the COR nominee files an OGE Form 450. Ensures the COR takes initial, annual and any additional training required by the contracting activity. Ensures the COR completes 16 hours of refresher training every three years after completion of the QAPC-Led Training.
PR: FD2060-18-34116 QASP REVISION: 0 10
3.3.2 Ensures the COR registers in WAWF as a CORT Tool user. Ensures the COR self-nominates as the designated COR for the contract in the CORT Tool. Upon notification of the COR self-nomination, approves the nomination in the CORT Tool. Reviews the COR Profile and COR Online File, at a minimum, annually. Considers performance of COR duties in their appraisal.
3.4 Procuring Contracting Officer (PCO)
3.4.1 Only individual authorized to enter into contracts for supplies and/or services by obligating the Government. Determines if a COR is required to conduct/document surveillance of Contractor performance. If the requiring activity has not initiated a COR nomination in the CORT Tool, submits a Request for Contracting Officer’s Representative Support memorandum to the requiring activity. Determines whether a COR is required to file an OGE Form 450.
Provides Contract-Specific Training to the COR.
3.4.2 Upon notification of COR Supervisor approval of the COR self-nomination, approves the nomination in the CORT Tool. Before contract/order award, submits a Designation of Contracting Officer’s Representative memorandum to the COR and Contractor for signature thereby ensuring the Contractor is notified of the COR assigned to the contract/order and their areas of responsibility and limitation of authority. Uploads the Designation memorandum in the CORT Tool under Contracting Officer / Appointment Letter. Upon transfer/termination of the COR, issues a Revocation (Termination) of Designation of Contracting Officer’s Representative memorandum. Uploads the Termination memorandum in the CORT Tool under COR Revocation.
3.4.3 After the COR is designated, uploads a blank copy the COR File Annual Checklist to the CORT Tool under Annual COR File Inspection Checklist to guide the COR in constructing the COR Online File. Reviews the COR reports on Contractor performance in the CORT Tool.
Approves/Rejects PARS and any CAR(s). Reviews the COR Profile and COR Online File, at a minimum, annually. Documents the results of their review on the Annual COR File Inspection Checklist. Uploads the checklist in the CORT Tool under Annual COR File Inspection Checklist.
3.5 Quality Assurance Program Coordinator
3.5.1 Supports the MFT in the development of the contract/order quality assurance requirements specifically ensuring the requirements are clearly stated and enforceable. Prior to contract/order award, provides training to CORs and COR management [e.g., FC/FD. COR supervisor, etc.]
3.5.2 Provides functional, not technical, support for CORT Tool users including assistance with registration, role activation and CORT Tool training. Monitors records of COR and COR management training in the CORT Tool.
PR: FD2060-18-34116 QASP REVISION: 0 11
3.6 Contractor
3.6.1 Participates as a member of the MFT upon approval of the Justification & Approval (J&A) or Sole Source Justification (SSJ) if the acquisition is sole source and upon contract/order award if it is competitive.
3.6.2 The Contractor shall ensure the quality of services through a quality and/or inspection system. In order to meet the government’s quality requirements, a contractor’s QMS should be robust enough and resourced adequately to execute four key quality functions: 1) Detection of quality program problems and defects; 2) Identification of root causes for quality related problems/defects; 3) Correction of root causes related to detected problems/defects; and, 4) Follow-up to ensure quality related problems/defects do not recur; a mature QMS requires the contractor be the proactive party on quality issues. The goal is to obtain performance reflective of continuous improvement with no reliance on COR’s surveillance to detect problems/defects, determine root causes, or ensure quality related problems/defects do not recur.
3.6.3 Responsible for ensuring personnel, information, system, property, facility and security requirements are met in accordance the DD Form 254, Department of Defense Contract Security Classification Specification and with Government regulations including, but not limited to, DoD 5200.2-R, Personnel Security Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM); DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual.
3.6.4 Maintains an inspection process acceptable to the Government and records of inspections, which shall be made available to the Government as long as the contract requires in accordance with the Inspection of Supply/Services clause(s) identified in the contract/order.
3.6.5 Signs and returns a positive PAR within five business days. Signs and returns a negative PAR with corrective action identified by the suspense date. Signs and returns a CAR with a corrective action plan by the suspense date.
3.6.6 Establishes a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award. Enters Order Data, Contact Data and Location Data. Provides an annual count of contractor/subcontractor personnel performing services for each fiscal year if the Department of Defense (DoD) is the requiring activity, if the acquisition is using United States (U.S.) Government appropriated funds, and if the acquisition is in excess of $3,000,000.00.
Reports all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract/order for each fiscal year in eCMRA.
3.7 Functional Commander/Functional Director (FC/FD)
3.7.1 The FC/FD has determined these services are not mission-essential and will not continue in the event of a crisis. Reference PWS and QASP signature page.
PR: FD2060-18-34116 QASP REVISION: 0 12
4.0 Management Strategy
4.1 The MFT will meet and record minutes quarterly to review contractor’s performance. The COR will issue PARs, documenting both satisfactory and unsatisfactory Contractor performance, at a minimum, quarterly. The COR will forward the PAR to the PCO for submission to the Contractor. The PCO will submit the PAR to the Contractor. The Contractor shall sign and return a positive PAR to the PCO within five business days. The COR will upload the PAR in the CORT Tool under COR Status Reports. Unsatisfactory Contractor performance will result in the COR issuing a negative PAR.
4.2 If repetitive negative PARs or a single negative PAR identifying critical Contractor non-compliance are issued without satisfactory resolution, the COR will issue a CAR. However, the MFT reserves the right to issue a CAR at any time based on the severity of the Contractor non-compliance. If the CAR process fails to resolve the unsatisfactory Contractor performance, the PCO has the right to invoke the Inspection of Supply/Services clause(s) identified in the contract/order
4.3 Incentives
4.3.1 If Contractor performance meets or exceeds contractual requirements, positive incentives may include, but are not limited to, decreased surveillance, favorable CPARs and exercising options.
4.3.2 If Contractor performance does not meet contractual requirements, negative incentives may include, but are not limited to, increased surveillance, unfavorable CPARs, not exercising options and Government remedies identified by clause(s) within the contract/order.
5.0 Annual COR Online File Inspection
The COR, the COR Supervisor and the PCO will review the COR Profile and COR Online File, at a minimum, annually. The PCO will document the results of their review on the Annual COR File Inspection Checklist. After the COR and COR supervisor sign the checklist, the PCO will upload the checklist in the CORT Tool under Annual COR File Inspection Checklist.
6.0 Contractor Performance Assessment Reporting System (CPARS)
6.1 The total estimated value of the contract equals or exceeds one million dollars ($1,000,000.00); therefore, CPARS reporting is required.
6.2 In accordance with FAR Part 42, Contract Administration and Audit Services, the MFT will evaluate Contractor performance. The Program Manager will, at a minimum, review the PARs and other information contained in the COR Online File to prepare and substantiate the CPAR.
The following areas will be rated on the CPAR as applicable: quality of product/service, schedule, management of key personnel, business relations, and cost control. CPARS will be updated, at a minimum annually, documenting a significant improvement or decline in the level of Contractor performance for the contract/order in accordance with the current Department of Defense Contractor Performance Assessment Reporting System (CPARS) Policy Guide CPARS Policy Guide. Additional information about CPARS can be found in the CPARS User Manual.
http://www.cpars.gov/cparsfiles/pdfs/DoD-CPARS-Guide.pdf http://www.cpars.gov/cparsfiles/pdfs/DoD-CPARS-Guide.pdf http://www.cpars.gov/cparsfiles/pdfs/CPARS_User_Manual.pdf
PR: FD2060-18-34116 QASP REVISION: 0 13
More frequent updates may be made, as required, to document a significant improvement or decline in the level of Contractor performance.
6.3 The Contractor shall have input into the CPAR prior to it being finalized. For each reporting period, the Program Manager will provide the Contractor a draft CPAR with no ratings, only justifications, to review for seven calendar days. After seven calendar days, unless additional time is needed to address the Contractor’s response, the CPAR process will continue. The CPAR will be coordinated through management up to the Division level. Once approved, the CPAR will be sent to the Contractor via CPARS for the official 30-calendar day review. The Contractor shall have the option to concur or non-concur, with comments, via CPARS.
6.4 In evaluating the quality of contractor’s performance, the following performance ratings are used in documenting past performance. The areas rated may include: Quality of Service, Business Relations, Management, Cost Control (if applicable), and Schedule.
Performance Rating
Criteria
Exceptional Performance meets contractual requirements and exceeds many to the government’s benefits. The contractual performance of the element or sub-element being assessed was accomplished with no problems and contractor actions were highly effective.
Very Good Performance meets contractual requirements and exceeds some to the government benefits. The contractual performance was accomplished with few minor problems for which corrective actions taken by the contractor were effective.
Satisfactory Performance meets contractual requirements. The contractual performance contains some minor problems for which corrective actions taken by the contractor were satisfactory.
Marginal Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear marginally effective or were not fully implemented.
Unsatisfactory Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the contractor’s corrective actions appear or were ineffective.
7.0 Safety Requirements
The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596 as amended by Public Law 101-552, Occupational Safety and Health Act (OSHA) and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). OSHA and ESOH requirements shall be incorporated into the Contractor’s Safety and Health Program.
7.1 Mishap Notification/Investigation: The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or
PR: FD2060-18-34116 QASP REVISION: 0 14
private property or injury or illness to non-DoD personnel caused by Government operations.
The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within four (4) business hours. The Contractor shall cooperate with Government safety investigations.
7.2 MFT Surveillance: MFT member(s) will report any potential safety hazards or actual mishaps to the COR. The COR will monitor Contractor reporting and review any mishap notifications. The COR will address safety and/or health issues in the PAR or in a CAR as applicable.
8.0 Trafficking in Persons: In accordance with the Defense Contingency COR Handbook section on Combating Trafficking in Persons, the COR/MFT must inform the PCO if the contractor/subcontractor fails to comply with the requirements of FAR 52.222.50, Combating Trafficking in Persons. The PCO must convey the information to DoD Combat Trafficking in Persons (CTIP) Law Enforcement and Support / Office of the Under Secretary of Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).
PR: FD2060-18-34116 QASP REVISION: 0 15
9.0 Signatures
By signing below, you are appointed to the MFT for this acquisition and accept the above responsibilities.
Deborah Middlebrooks, QAPC, AFSC/PZCA Date
The QAPC signature above signifies guidance was provided to the MFT in the development of Services Summary requirements in accordance with PZCA direction as of 5 June 2015.
JOHN W. BRYANT, AFLCMC/WNY, 478-327-5026 Date Logistics Manager/COR
AMANDA L. COLLINS, AFLCMC/WNY, 478-926-3025 Date COR Supervisor
LAUREN M. GRIFFIN, AFLCMC/WNKE, 478-926-1384 Date
PCO
Contractor Date
By signing below, you are identifying that these services are not mission-essential.
DAVID A. SUTTER, Lt Col, USAF Date Materiel Leader Common Avionics Branch
| Text1: 07 Mar 2019 | |
| Text2: 07 Mar 2019 | |
| Text3: 08 Mar 2019 | |
| Text4: 08 Mar 2019 | |
| Text5: | |
| Text6: 08 Mar 2019 | |
| 2019-03-08T12:01:22-0500 | |
| SUTTER.DAVID.ANDREW.1138190060 |
| 2019-03-08T09:04:58-0500 | |
| GRIFFIN.LAUREN.MARIE.1455116356 |
| 2019-03-08T09:06:33-0500 | |
| COLLINS.AMANDA.L.1395513873 |
| 2019-03-07T18:07:42-0500 | |
| BRYANT.JOHN.W.1063401222 |
| 2019-03-07T17:09:43-0500 | |
| MIDDLEBROOKS.DEBORAH.A.1280272937 |
File details come from the government source that posted it. Updated .