QASP.pdf

PR: FD2060-15-90953 QASP REVISION: 0 1

QUALITY ASSURANCE SURVEILLANCE PLAN

FOR

CONTRACT LOGISTICS SUPPORT (CLS), AND PRODUCTION OF THE

DEFENSE INJECTION/RECEPTION EMERGENCY ACTION MESSAGE (EAM)

COMMAND AND CONTROL (C2) TERMINAL (DIRECT)/DIRECT-LIMITED INJECTION

TERMINAL (DIRECT-LITE) AND ALTERNATE INJECTION TERMINAL (AIT)

31 August 2016

1.0 Performance Management

1.1 Objective(s): The objective of this effort is to procure Contract Logistics Support (CLS) and Production for the Defense Injection/Reception Emergency Action Message (EAM) Command and Control (C2) Terminal (DIRECT), DIRECT-Limited Terminal Equipment (DIRECT-LITE) and Alternate Injection Terminal (AIT) with a Period of Performance (POP) of five and one-half (5 ½) years (one 18-month basic with four 12-month options). Throughout this PWS it should be understood that this entire PWS for CLS and Production is for DIRECT, DIRECT-LITE and/or AIT as applicable. The Production effort will begin during the 18-month basic, targeted start date is June 2016. The follow-on CLS effort is targeted to start 1 January 2017. The contract type is Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF) and Cost Reimbursable No Fee (CRNF); CPFF shall be utilized only for on-site support through (GDIT) and CRNF shall be utilized only in support of Travel and Per Diem.

1.2 Result(s): The Contractor shall provide Contract Logistics Support (CLS) and Production for DIRECT. The services provided shall benefit the Prime Mission Equipment (PME) which is comprised of all required system hardware, software and data to be installed at a specific site/platform to permit DIRECT, DIRECT-LITE and/or AIT to perform all of its critical functions. The PME includes all required common, site-peculiar, and Communication System-peculiar hardware, software, and data at a site or platform. 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.

1.3 General Responsibilities of Multi-Functional Team (MFT)

1.3.1 Fostering partnerships with industry to ensure cooperation and exchange of information occur. Conducting market research to identify commercial products and services which already exist, product developments, technological advancements, suppliers’ capabilities, new vendors and commercial best practices. Providing findings to the MFT member responsible for preparing the market research report.

PR: FD2060-15-90953 QASP REVISION: 0 2

1.3.2 Identifying Government requirements. Ensuring the acquisition is linked to the United States Air Force (USAF) mission. Ensuring key stakeholders participate in developing, implementing and executing the acquisition strategy.

1.3.3 Planning, programming, and budgeting adequate funds to ensure the acquisition is executed within approved funding.

1.3.4 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.

1.3.5 For other than sole source acquisitions, developing, implementing and executing a source selection that provides a thorough assessment of the proposals of the offerors and the best value for the Government.

1.3.6 Conducting an Initial Contract Performance Review (30-Day Review) in accordance with Air Force Instruction (AFI) 63-138, Acquisition of Services, paragraph 6.4. Preparing Annual Execution Review (AER) reports in accordance with AFI 63-138, paragraph 5.2. Proactively reporting significant variances in quality of services, cost and/or schedule to Government management throughout the contract/order Period of Performance (PoP).

1.3.7 Developing, implementing and managing milestones to ensure the Contractor is on schedule for meeting Government requirements within the contract/order PoP. Developing, implementing, and executing Contractor performance measurement and management in accordance with the Quality Assurance Surveillance Plan (QASP).

1.3.8 Conducting surveillance of Contractor performance to ensure Government requirements including quality of services, cost and schedule are met. Providing results of 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).

1.3.9 Identifying opportunities to improve Contractor performance throughout the life of the contract/order including benchmarking against industry. Promoting initiatives to improve Contractor performance, assessing the risks associated with initiatives, using the QASP to implement initiatives, and monitoring the success of implementation.

1.3.10 Ensuring customer needs are met.

1.4 Specific Roles and Responsibilities of MFT Members

1.4.1 Program Manager (PM): Responsible for overall program. Serves as MFT lead. Works with the MFT to identify Government requirements and prepare Purchase Request (PR) package.

Prepares and submits Contractor Performance Assessment Reports (CPAR).

PR: FD2060-15-90953 QASP REVISION: 0 3

1.4.2 Engineer: Works with MFT in conducting market research. Prepares market research report. Prepares Air Force Materiel Command (AFMC) Form 807, Recommended Quality Assurance Provisions and Special Inspection Requirements. Prepares technical Department of Defense (DD) Form 1423-1(s), Contract Data Requirements List (CDRL). Works with MFT in developing other technical requirements for PR package. Requests, reviews and approves Engineering Change Proposal(s) (ECP).

1.4.3 Data Management Officer (DMO): Assists in preparation of Data Item Description(s) (DID). Validates DIDs. Assists in preparation of CDRL(s). Acts as Approving Official (AO) for CDRL(s). Schedules and co-chairs the Data Requirements Review Board (DRRB).

1.4.4 Contracting Officer’s Representative (COR) Mandatory inclusion. Do not remove.

1.4.4.1 In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) Procedures, Guidance, and Information (PGI) 201.602-2(d)(iv), Career Development, Contracting Authority, and Responsibilities / Contracting officers / Responsibilities, and the Office of the Under Secretary of Defense (OUSD) Memorandum, Deployment of the Department of Defense (DoD) Contracting Officer Representative Tracking Tool (CORT Tool), dated Mar 21 2011 OUSD memo 21 Mar 11, self-nominates in the CORT Tool.

1.4.4.2 Works with MFT in conducting surveillance on Contractor performance and evaluating Contractor performance in accordance with DFARS PGI 201.602-2(d)(v). Reports unethical conduct and instances of fraud, waste and/or abuse to the Procuring Contracting Officer (PCO) in accordance with the OUSD Memorandum, DoD Standard for Certification of Contracting Officer's Representatives (COR) for Service Acquisitions, dated Mar 29 2010 OUSD memo 29 Mar 10. Inspects and accepts/rejects deliverables during contract/order performance and at close-out to ensure contract/order terms and conditions are met in accordance with the OUSD Memorandum, dated Mar 29 2010. Monitors Contractor payment and verifies it is commensurate with Contractor performance in accordance with the OUSD Memorandum, dated Mar 29 2010.

1.4.4.3 Documents Contractor performance via PARs, Corrective Action Reports (CAR), etc. in accordance with DFARS PGI 201.602-2(d)(vi)(B). Issues PARs, at a minimum, quarterly and negative PARs or CARs as required. Provides reports (e.g., PARs, CARs, etc.) on Contractor performance to the PCO in accordance with Air Force Federal Acquisition Regulation Supplement (AFFARS) Mandatory Procedure (MP) 5301.602-2(d)2.9, Designation, Assignment, and Responsibilities of a Contracting Officer’s Representative (COR) / COR Roles and Responsibilities.

1.4.4.4 Establishes and maintains an online file containing surveillance and training documentation (COR Online File and COR Profile in the CORT Tool) in accordance with DFARS PGI 201.602-2(d)(vi); AFFARS MP5301.602-2(d)2.5; the OUSD Memorandum, dated Mar 29 2010; and the OUSD Memorandum, dated Mar 21 2011. Uploads initial and refresher training certificates in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(iv).

Uploads the Contract-specific Training checklist in the CORT Tool in accordance with DFARS http://www.acq.osd.mil/dpap/dars/pgi/docs/Signed_CORT_Policy_Memo.pdf http://www.acq.osd.mil/dpap/policy/policyvault/USA005569-09-DPAP.pdf http://www.acq.osd.mil/dpap/policy/policyvault/USA005569-09-DPAP.pdf

PR: FD2060-15-90953 QASP REVISION: 0 4

PGI 201.602-2(d)(iv). Uploads the QASP in the CORT Tool. Completes and signs the Annual COR Online File Inspection Checklist in the anniversary month of their appointment.

1.4.4.5 Monitors control and disposition of Government property in accordance with the OUSD Memorandum, dated Mar 29 2010.

1.4.5 Quality Assurance Program Coordinator (QAPC)

1.4.5.1 Supports the MFT in the development of the contract/order quality assurance requirements specifically ensuring the requirements are clearly stated and enforceable in accordance with AFFARS MP5346.103.1c(2), Contracting Office Responsibilities / Roles and Responsibilities. Provides training to CORs and COR management [e.g., Functional Commander/Functional Director (FC/FD), COR supervisor, etc.] in accordance with AFFARS MP5301.602-2(d)5.1, Designation, Assignment, and Responsibilities of a Contracting Officer’s Representative (COR) / Quality Assurance Program Coordinator (QAPC).

1.4.5.2 Provides functional, not technical, support for CORT Tool users including assistance with registration, role activation and CORT Tool training in accordance with AFFARS MP5301.602-2(d)5.3. Monitors records of COR and COR management training in the CORT Tool in accordance with AFFARS MP5301.602-2(d)5.3.

1.4.6 Procuring Contracting Officer (PCO)

1.4.6.1 Only individual authorized to enter into contracts for supplies and/or services by obligating the Government. Advises the MFT on QASP development including incentives and remedies tied to performance objectives and performance thresholds in accordance with AFFARS MP5346.1031.b.(1). Develops and awards a contract/order based on MFT requirements and acquisition strategy.

1.4.6.2 Determines if a COR is required to conduct/document surveillance of Contractor performance in accordance with AFFARS MP5301.602-2(d)1.2, Designation, Assignment, and Responsibilities of a Contracting Officer’s Representative (COR) / Contracting Officer Roles and Responsibilities. If a COR has not self-nominated in the CORT Tool, submits Request for Contracting Officer’s Representative Support memorandum to requiring activity in accordance with AFFARS MP5301.602-2(d)1.2. Upon notification of COR Supervisor approval of COR nomination in the CORT Tool, approves COR nomination in the CORT Tool and submits 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 in accordance with DFARS PGI 201.602-2(d)(v)(A) and AFFARS MP5301.602-2(d)1.5. Upon transfer/termination of the COR, issues a Revocation (Termination) of Designation of Contracting Officer’s Representative memorandum in accordance with AFFARS MP5301.602-2(d)1.10-1.12. Uploads Designation memorandum and, if applicable, Termination memorandum in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(v)(C) and the OUSD Memorandum, dated Mar 21 2011. Provides Contract-specific COR Training to the COR in accordance with AFFARS MP5301.602-2(d)1.4.

PR: FD2060-15-90953 QASP REVISION: 0 5

1.4.6.3 Reviews COR reports (e.g., PARs, CARs, etc.) on Contractor performance in accordance with AFFARS MP5301.602-2(d)1.6. Inspects COR Online File and COR Profile in the CORT Tool, at a minimum annually, in accordance with DFARS PGI 201.602-2(d)(vii). Reviews and signs the Annual COR Online File Inspection Checklist and uploads checklist in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vii).

1.4.6.4 Responsible for administration of the contract/order except as delegated to the Administrative Contracting Officer (ACO). Monitors Contractor performance to ensure compliance with contractual requirements. Takes action, if necessary, to enforce contractual requirements. Approves travel requests for Contractor personnel.

1.4.7 Contractor

1.4.7.1 Participates as a member of the MFT upon approval of Justification & Approval (J&A) or Sole Source Justification (SSJ) if the acquisition is sole source and upon contract/order award if it is competitive.

1.4.7.2 Submits a written plan detailing procedures for continuing performance of mission-essential services during a crisis in accordance with DFARS 237.7602(b), Continuation of Essential Contractor Services / Policy, and DFARS 252.237-7024(b), Notice of Continuation of Essential Contractor Services.

1.4.7.3 Responsible for ensuring personnel, information, system, property, facility and international security requirements are met in accordance with Government regulations including, but not limited to, Department of Defense (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;

DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual;

and RAFB IDP 31-101, Robins Integrated Defense Plan.

1.4.7.4 Complies with contractual requirements including the PWS and CDRLs. Performs services required by the contract/order including the PWS and CDRLs. Provides the Government with contractual deliverables and other requested data by which Contractor performance will be evaluated.

1.4.7.5 In accordance with Federal Acquisition Regulation (FAR) 52.246-4, Inspection of Services – Fixed-Price. 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.

1.4.7.6 Signs and returns a 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 corrective action plan by the suspense date.

PR: FD2060-15-90953 QASP REVISION: 0 6

1.4.7.7 In accordance with the Secretary of the Air Force for Acquisition (SAF/AQ) Memorandum, Implementation of FY11 NDAA [National Defense Authorization Act] Section 8108 [of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Act, 2011], Contractor Inventory, dated Nov 13 2012 SAF/AQ memo 13 Nov 12, provides an annual count of Contractor personnel performing services if the DoD is the requiring activity, if the acquisition is using United States (U.S.) Government appropriated funds, and if the acquisition is equal to or greater than the Simplified Acquisition Threshold (SAT) [currently $150,000.00]. In accordance with Office of the Secretary of Defense (OSD) Memorandum, Enterprise-wide Contractor Manpower Reporting Application, dated Nov 28 2012 OSD memo 28 Nov 12, reports all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract at the Enterprise-wide Contract Manpower Reporting Application (eCMRA) site below.

http://www.ecmra.mil

1.4.8 Defense Contract Management Agency (DCMA): Administers contract/order in accordance with FAR Part 42, Contract Administration and Audit Services. Accepts services in Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) [formerly Wide Area Workflow

(WAWF)].

1.4.9 Contracting Officer’s Representative (COR) Supervisor: Upon notification of COR self-nomination in the CORT Tool, approves COR nomination in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(iv), and the OUSD Memorandum, dated Mar 21 2011. Inspects the COR Online File and the COR Profile in the CORT Tool, at a minimum annually, in accordance with DFARS PGI 201.602-2(d)(vii). Reviews and signs the Annual COR Online File Inspection Checklist in accordance with DFARS PGI 201.602-2(d)(vii). Considers COR duties in appraisal in accordance with AFFARS MP5301.602-2(d)2.4.

1.4.10 Functional Commander/Functional Director (FC/FD)

1.4.10.1 The Functional Commander or civilian equivalent will determine if services are mission-essential and will continue in the event of a crisis in accordance with DFARS 237.7602(a), Continuation of Essential Contractor Services / Policy; DFARS 252.237- 7023(a)(2), Continuation of Essential Contractor Services; and AFI 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2. The Functional Commander or civilian equivalent will ensure mission-essential services are identified in the PWS in accordance with AFI 10-403, paragraph 1.9.1.33.2.

Note: The Functional Commander or civilian equivalent has determined these services are mission-essential and will continue in the event of a crisis. Reference PWS paragraph 5.1, Continuation of Mission-Essential Services During a Crisis and QASP signature page.

1.4.10.2 The Contractor shall submit a written plan detailing procedures for continuing performance of mission-essential services during a crisis in accordance with DFARS 237.7602(b), DFARS 252.237-7023(c)(1), and DFARS 252.237-7024(b). During a crisis the Functional Commander or civilian equivalent will direct the PCO to authorize the Contractor to activate the plan in accordance with DFARS 237.7602(b).

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5337/2012-11-13_saf-aq-memo.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.ecmra.mil/

PR: FD2060-15-90953 QASP REVISION: 0 7

1.4.10.3 The Functional Commander or civilian equivalent will develop a contingency plan if there is a reasonable doubt that the Contractor will continue to provide mission-essential services during a crisis in accordance with DoD Instruction (DoDI) 1100.22, Policy and Procedures for Determining Workforce Mix, Enclosure 2, paragraph 5.b, and AFI 10-403, paragraph 1.9.1.33.1.

PR: FD2060-15-90953 QASP REVISION: 0 8

1.5 Management Strategy

1.5.1 The MFT will meet, at a minimum, quarterly to review Contractor performance.

1.5.2 The MFT will evaluate Contractor performance. The Contractor shall provide the Government with contractual deliverables and other requested data. The MFT will collect and analyze Contractor performance data and develop metrics to evaluate Contractor performance.

1.5.3 The COR will issue PARs, documenting both satisfactory and unsatisfactory Contractor performance, at a minimum, quarterly. The COR will prepare and 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 the PAR to the PCO within five business days. The COR will upload the PAR in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vi)(B).

Unsatisfactory Contractor performance will result in the COR issuing a negative PAR.

1.5.4 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 FAR 52.246-4.

1.5.5 Incentives

1.5.5.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.

1.5.5.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 in FAR 52.246-4.

1.6 Initial Contract Performance Review (30-Day Review): In accordance with AFI 63-138, paragraph 6.4, the MFT is responsible for conducting an Initial Contract Performance Review.

The review is a determination by the MFT that the Contractor has successfully started performance, has completed transition, is fully operational, and is within the estimated cost, schedule and performance parameters of the contract/order. In accordance with AFI 63-138, paragraph 6.4.1, the review will take place within 30 [calendar] days after the Contractor assumes full performance responsibility. For acquisitions greater than or equal to one hundred million dollars ($100,000,000.00), results of the review will be reported to the Services Designation Official (SDO) as described in AFI 63-138, paragraph 6.4. The COR will upload the review in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vi)(B).

PR: FD2060-15-90953 QASP REVISION: 0 9

1.7 Annual COR Online File Inspection: The COR will maintain the COR Online File and their COR Profile in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vi); AFFARS MP5301.602-2(d)2.5; the OUSD Memorandum, dated Mar 29 2010; and the OUSD Memorandum, dated Mar 21 2011. The COR will complete and sign the Annual COR Online File Inspection Checklist in the anniversary month of their appointment. The COR Supervisor will inspect the file and sign the checklist in accordance with DFARS PGI 201.602-2(d)(vii).

The PCO will inspect the file and sign the checklist in accordance with DFARS PGI 201.602- 2(d)(vii). The PCO will upload the checklist in the CORT Tool in accordance with DFARS PGI 201.602-2(d)(vii).

1.8 Annual Execution Review (AER): In accordance with AFI 63-138, paragraph 2.7.5, the SDO is responsible for ensuring an AER is conducted. In accordance with AFI 63-138, paragraph 5.2, the MFT is responsible for preparing AER reports. In accordance with AFI 63- 138, paragraph 5.2, the AER will assess the acquisition’s progress against approved cost, schedule and performance metrics and review the summary of evaluations from CPARS.

1.9 Contractor Performance Assessment Reporting System (CPARS): CPARS reporting will be accomplished on the basic contract.

1.9.1 The total estimated value of the contract equals or exceeds one million dollars ($1,000,000.00); therefore, CPARS reporting is required.

1.9.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, schedule, cost control, management and regulatory compliance. CPARS will be updated, at a minimum annually, documenting Contractor performance for the contract/order in accordance with the Guidance for the Contractor Performance Assessment Reporting System (CPARS). Additional information about CPARS can be found in the User Manual for Contractor Performance Assessment Reporting System (CPARS). More frequent updates may be made, as required, to document a significant improvement or decline in the level of Contractor performance.

1.9.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 examine for seven calendar days. After MFT review of the Contractor’s response, 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 60 calendar day review. The Contractor shall have the option to concur or non-concur, with comments, via

CPARS.

1.10 Safety Requirements

1.10.1 Mishap Notification/Investigation

PR: FD2060-15-90953 QASP REVISION: 0 10

1.10.1.1 In accordance with AFI 91-204, Safety Investigations and Reports, paragraph 2.4.6.1.1, the Contractor shall report mishaps involving damage or injury to USAF interests. In accordance with AFI 91-204, paragraph 1.3.1.1, damage or injury includes: 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 private property or injury or illness to non-DoD personnel caused by USAF operations.

1.10.1.2 In accordance with AFI 91-204, paragraph 2.4.6.1.1, the Contractor shall ensure the USAF [Safety Office] and the applicable contract management authority are notified of mishaps.

The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within four business hours. The MFT will notify the Safety Office and the PCO.

1.10.1.3 In accordance with AFI 91-204, paragraph 2.4.6.1.2, the Contractor shall cooperate with USAF safety investigations.

1.10.2 MFT Surveillance: The COR will monitor Contractor reporting and review any mishap notifications. The COR will address safety and/or health issues in the PAR.

1.11 Trafficking in Persons: In accordance with the Defense Contingency COR Handbook section on Combating Trafficking in Persons, the COR must inform the PCO if the Contractor/subcontractor and/or Contractor/subcontractor personnel fail 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 Under Secretary of Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).

2.0 Assessment Management

2.1 Services Summary

Performance Objective

PWS

Reference

Performance Threshold Method of Surveillance

Follow-on Contract Logistics Support (CLS) and Production services

4.0 4.1.3 4.1.4 4.2.6 4.3.5 4.3.8 4.4.5

The Contractor shall repair and bring back to serviceable condition all items within the established turnaround time of 45 calendar days, production is 18 months ARO.

The Contractor shall track repair and production.

The Systems Engineer/Program Manager shall be

100% inspection by Systems Engineer and PM to monitor configuration changes within two business days following notification.

Surveillance will be documented, at a minimum, quarterly by the COR(s) in the PAR.

PR: FD2060-15-90953 QASP REVISION: 0 11

PWS

Reference

Performance Threshold Method of Surveillance informed of 100% of all configuration changes.

CAV-AF

Reporting

4.19 The Contractor shall

report production using CAV-AF. The Contractor shall provide data on the actions conducted for each unit.

The Contractor shall report as actions occur.

CAV-AF transactions will be monitored by the

PMS.

Surveillance will be documented, at a

Completion of Block Cycle

4.2.2 4.3.2

All PTRs scheduled for a Block Update must be addressed and all required testing completed within the allowed block cycle time period, unless relief for one or more PTRs is granted by PM and/or Joint Staff.

100% review by Systems Engineer and PM to monitor Engineering Change Proposals within five business days following notification.

Surveillance will be documented, at a

System Operational Availability (Ao)

4.3.12 4.11.1

The Contractor shall maintain system’s Ao of .999 as defined by the

DIRECT ORD.

Periodic inspection, quarterly review and monthly documentation review by Systems Engineer and PM of Contractor-maintained list of inoperable system times to verify System Operational Availability of 99.9%.

Surveillance will be documented, at a

Submission of Engineering Change Proposal (ECP)

4.2.6 All Class 1 changes to

the baseline configuration shall be submitted via ECPs to

AFLCMC/WNYEDA.

The Contractor shall notify the WR-ALC Systems Engineer of all Class 2 changes, 100% review by Systems Engineer and PM to monitor Engineering Change Proposals within five business days following notification.

Surveillance will be documented, at a

PR: FD2060-15-90953 QASP REVISION: 0 12

PWS

Reference

Performance Threshold Method of Surveillance including all substitute parts changes, through Document Change Notices (DCN).

Quality of data/document

4.1 - 4.4 4.12 4.14 5.5.4.1

There shall be no more than _2__ rejection(s) of data/document(s) per contract year. There shall be no more than one rejection of each data/document. The Government will reject the submitted data/document if __3__ or more technical errors or _2___ or more minor errors are found within the data/document. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected data/document shall be corrected and resubmitted within __14__ business days of notification of Government rejection.

100% review by Systems Engineer and PM to monitor contract CDRLs within five business days following receipt of monthly/quarterly deliverable.

Surveillance will be documented, at a minimum, quarterly by the COR(s) in the PAR.

Receipt of data/document

4.1 - 4.4 4.12 4.14 5.5.4.1

There shall be no more than _2___ late submission(s) of data/document(s) per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and

100% review by Systems Engineer and PM to monitor contract CDRLs within five business days following receipt of monthly/quarterly deliverable.

documented, at a

PR: FD2060-15-90953 QASP REVISION: 0 13

PWS

Reference

Performance Threshold Method of Surveillance negotiate a revised delivery date. The data/document shall be delivered by a revised delivery date acceptable to the Government.

Request(s) for assistance

4.6 24-hour, 7-day help desk service shall be available for EA operators and on-site service technicians.

Follow-up assistance, if required, shall be provided by a suspense date acceptable to the Government.

Periodic inspection, quarterly review and monthly documentation review by Systems Engineer and PM of Contractor-submitted list of calls logged in the maintenance database monthly.

Surveillance will be documented, at a

Program Management Services

4.3.1 4.3.9.1

The Contractor shall report program status quarterly.

The Contractor shall provide support in program management to conduct and administratively support two (2) PMRs per contract year with proposed agenda delivery not less than 10 business days prior.

100% review by Systems Engineer and PM to monitor contract CDRLs within five business days following receipt of quarterly deliverable.

Surveillance will be documented, at a minimum, quarterly by the COR(s) in the PAR.

Contractor personnel qualifications

4.1.7.5 4.3.2.6

Contractor personnel shall meet, at a minimum, Software Engineering Institute Capability Maturity Model rating of Level 3 or higher.

100% review by Systems Engineer and PM of monthly documentation review.

List of metrics:

PTR Status Opened vs. Closed PTRs Cumulative Number of AIs and PTRs per Phase

PR: FD2060-15-90953 QASP REVISION: 0 14

PWS

Reference

Performance Threshold Method of Surveillance

Software Lines Of Code

(SLOC)

Defects and Enhancements

Surveillance will be documented, at a

Contractor Manpower Reporting

5.8 Within 30 calendar

days of contract/order award, the Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data.

The Contractor shall provide an annual count of contractor/subcontractor personnel performing services and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

conducted, by the COR monitoring eCMRA and reporting Contractor non-compliance to the PCO.

Surveillance will be documented, at a the COR in the PAR.

2.2 COR Online File Documentation

2.2.1 The COR will establish and maintain an online file containing surveillance and training documentation (COR Online File and COR Profile in the CORT Tool) in accordance with DFARS PGI 201.602-2(d)(vi); AFFARS MP5301.602-2(d)2.5; the OUSD Memorandum, dated Mar 29 2010; and the OUSD Memorandum, dated Mar 21 2011. The following documentation will be uploaded in the CORT Tool by the COR or PCO as applicable.

1) Contractual Documents PWS, PWS revision(s)

PR: FD2060-15-90953 QASP REVISION: 0 15

QASP, QASP revision(s) applicable CDRL(s) DD Form 254, Department of Defense Contract Security Classification Specification

2) Training and Appointment

DAU CLC 222 Contracting Officers Representative (COR) Online Training annual ethic training Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) Overview Lesson (formerly WAWF Overview Lesson) annual CTIP training QAPC-Led Training Contract-Specific Training Request for Contracting Officer’s Representative Support Designation of Contracting Officer’s Representative Revocation (Termination) of Designation of Contracting Officer’s Representative

3) Contractor Performance Data applicable status report(s) DCMA report(s) Commercial Asset Visibility-Air Force (CAV-AF) Repair Item Actions Report(s) iRAPT (formally WAWF) report(s) and/or other documentation demonstrating oversight of Contractor payment

4) Surveillance and Inspection

PAR(s) .

CAR(s) .

Customer Complaint Record(s) (CCR) Initial Contract Performance Review (30-Day Review) .

Annual COR Online File Inspection Checklist(s) .

5) Contract Plans (basic or order, as applicable) contract/order Appendix B contract/order Appendix C (Industrial Safety Requirements) Contractor Safety and Health Plan

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. The COR will upload the negative PAR in the CORT Tool in accordance with DFARS PGI 201.602- 2(d)(vi)(B)..

PR: FD2060-15-90953 QASP REVISION: 0 16

2.3.2 If repetitive 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 return the CAR to the COR. The COR will forward the CAR to the PCO for submission to the Contractor. The PCO will submit the CAR to the Contractor for corrective action. The Contractor shall sign and return the CAR, with 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 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 FAR 52.246-4.

2.3.3 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-2, the Government may require the Contractor to correct and/or replace nonconforming supplies with an equitable adjustment of contract price and/or terminate the contract for default.

2.3.4 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-3, the Government may require the Contractor to correct and/or replace nonconforming supplies with an equitable adjustment of contract fee and/or terminate the contract for default.

2.3.5 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-4, the Government may:

1) require the Contractor to perform the services again at no increase in contract amount;

2) require the Contractor to take action necessary to ensure future performance conforms to contractual requirements;

3) reduce the contract price to reflect the reduced value of the services performed;

4) perform the services, by contract or otherwise, and charge to the Contractor any cost incurred by the Government that is directly related to the performance of such services;

and/or

5) terminate the contract for default.

2.3.6 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-5, the Government may:

1) require the Contractor to perform the services again at no additional fee;

2) require the Contractor to take action necessary to ensure that future performance conforms to contractual requirements;

3) reduce any fee payable under the contract to reflect the reduced value of the services performed;

4) perform the services, by contract or otherwise, and reduce any fee payable by an amount that is equitable under the circumstances; and/or

5) terminate the contract for default.

2.3.7 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-6, the Government may:

PR: FD2060-15-90953 QASP REVISION: 0 17

1) require the Contractor to correct and/or replace services at a reduced cost;

2) perform correction and/or replacement of services, by contract or otherwise, and charge Contractor increased cost;

3) terminate the contract for default; and/or

4) require the Contractor to correct and/or replace services at no cost if non-compliance is due to fraud or unqualified Contractor personnel.

2.3.8 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-7, the Government may:

1) require the Contractor to correct and/or replace supplies (work) at no increase in contract price and in accordance with a delivery schedule date acceptable to the PCO.

2) require the Contractor to repay a portion of the contract price as is equitable under the circumstances if the Government elects not to require correction or replacement.

2.3.9 As a result of non-compliance with contractual requirements in accordance with FAR 52.246-8, the Government may:

1) perform correction and/or replacement of services, by contract or otherwise, and charge Contractor increased cost or make an equitable reduction in any fixed fee paid or payable under the contract;

2) require delivery of any undelivered articles and make an equitable reduction in any fixed fee paid or payable under the contract;

3) terminate the contract for default; and/or

4) require the Contractor to correct and/or replace services at no cost if non-compliance is due to fraud or unqualified Contractor personnel.

2.4 Acceptance of Services

2.4.1 In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports, 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).

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.

2.4.3 Services will be accepted by the

Program Manager: AFMC AFLCMC/WNYBBA Contracting Officer’s Representative: AFMC AFLCMC/WNYKA Engineer: AFMC AFLCMC/WNYEDA

PR: FD2060-15-90953 QASP REVISION: 0 18

3.0 Signatures

By signing below, you are appointed to the MFT for this acquisition and accept the above responsibilities.

Primary COR/Program Manager Date

Alternate COR

COR Supervisor

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.

Production Management Specialist - Seller

DMO

Security

Information Assurance Manager

Safety

PCO

DCMA

Contractor

By signing below, you are identifying certain services provided under the contract/order as mission-essential in accordance with DFARS 237.7602(a), DFARS 252.237-7023(a)(2) and AFI 10-403, paragraph 1.9.1.33.2. (Reference PWS paragraph 4.14.)

FC/FD Date