About this file

Quality Assurance Surveillance Plan

View the file

Other files

File Type Posted
9TRNSPDATA_REPORT.pdf PDF
8WAGEDET.pdf PDF
6CDRLS_final.pdf PDF
5DD254_ATTACH.pdf PDF
4Special_Packaging_2_ATTACH.pdf PDF
7PWS.pdf PDF
3Special_Packaging_ATTACH.pdf PDF
FA852218R0009.pdf PDF
2PKGRQMT_REPORT.pdf PDF
10_Security_Classification_Guide.pdf PDF

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

PR: FD2060-19-00038 QASP 1

Quality Assurance Surveillance Plan (QASP)

For

AN/ALQ-172(V) Countermeasures System (CMS)

Line Replaceable Units (LRU’S)-2 and -3

Reliability and Maintainability (R&M) Redesign

Purchase Request: FD2060-19-00038

Date: 30 May 2018

PR: FD2060-19-00038 QASP 2

1.0 Purpose

The AN/ALQ-172 (LRU-2 and LRU-3) is described as being a "combat proven" system that is installed on US Air Force (USAF) Global Strike Command (AFGSC) B-52H strategic bombers (ALQ-172(V)2), Air Force Special Operations Command (AFSOC) MC-130H Combat Talon 'II' transports and AC-130U (ALQ-172(V)1) gunships. System design features include full automation, multiband coverage, simultaneous multiple threat recognition and jamming, digital computer control, "advanced" jamming techniques, a "high" effective radiated power value, threat re-programmability, a high-gain antenna array, a threat warning display, and "extensive" built-in test capabilities.

1.1 The contractor shall provide engineering services to resolve Obsolete Part and Vanishing Vendor issues with the LRU-2 NSN 5865-01-152-1792EW, and LRU-3 NSN 5985-01-424- 5098EW, significantly improve the system Line Replaceable Unit (LRU) availability, reliability, maintainability, supportability, and produce-ability which combine to determine the system availability a system can achieve. The AN/ALQ-172 (LRU-2 and LRU-3) was developed by ITT Corporation, which is now Harris.

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 Performance-based Work Statement (PWS) describes the services required to provide the engineering services to perform a form, fit, function, and interface (FFFI) replacement for the AN/ALQ-172 (LRU-2 and LRU-3). These services include a LRU FFFI redesign, prototype fabrication, and test and delivery effort by redesigning the AN/ALQ-172 (LRU-2 and LRU-3) to meet legacy LRU specification performance requirements. The FFFI prototypes shall exhibit system reliability, availability and performance equivalent to or exceeding the legacy specifications of the AN/ALQ-172 (LRU-2 and LRU-3).

1.4 Result(s)

Through this contracting effort, the Multi-Functional Team (MFT) is striving to achieve a form, fit, function, and interface (FFFI) replacement for the AN/ALQ-172 (LRU-2 and LRU-3)

2.0 Assessment Management

2.1 Services Summary

Performance Objective

PWS

Reference

Performance Threshold Method of Surveillance

Provide accurate

4.4.3 Monthly status reports that

shall be technically accurate

COR will review submitted Monthly Status Reports (CDRL

PR: FD2060-19-00038 QASP 3

technical monthly status addressing schedule and cost status and complete with no more than one technical error and no more than five typographical errors.

A00D) upon receipt. and Government comments necessary will be provided via email to the contractor if necessary. COR and engineer will witness testing and review all technical Documentation submitted under applicable CDRLs. Results will be summarized on the semi-annually PAR and any comments sent via email to the contractor.

Provide Test Requirement Documents (TRDs)

4.2.5.1. The contractor shall build

FFFI LRU prototypes with improved system availability by providing accurate Technical Order (T.O.)

changes. The AN/ALQ-172

(LRU-2 & LRU-3)

Countermeasures Receiver shall pass prototype testing requirements. An item that has a high level of Reliability and Maintainability (R&M), is producible, and is supportable, should achieve a high level of operational availability.

Surveillance will be conductedy by TMCR Equipment Specialist review of CDRL A00A and CDRL A00B submissions. Results will be summarized on the semiannually PAR and Government comments provided via email and attendance at technical reviews and data conferences.

Build Form, fit, function and interface LRU prototypes with improved system availability

4.3.1 The form, fit, function and

interface prototypes successfully pass the testing requirements with no more than two retests at the next higher assembly with a calculated LRU MTBF of at least 1,600 hours for LRU-2 and at least 2,600 hours for

LRU-3.

Surveillance will be conducted by the COR and engineer by witness testing and review all technical documentation submitted under applicable CDRLs. Results will be summarized on the semi-annually P A R .

Provide Technical Order (T.O.) changes according to

TMCR

4.3.6.1 Final version T.O. changes

shall be free of technical errors and require no major re-work, as determined by the Government.

Surveillance will be conducted the engineer per occurrence and will be documented, at a minimum, semi-annually in the PAR by the

COR.

Pass prototype testing requirements

4.3.1 Successfully pass prototype

testing requirements with no more than two retests at the next higher assembly.

Surveillance will be conducted by the program manager reviewing deliverables upon receipt.

PR: FD2060-19-00038 QASP 4

Surveillance will be documented, at a minimum, semi-annually by the COR.

Quality of

CDRL

deliverable

4.2.1 There shall be no more than

one rejection of any deliverable. There shall be no more than one total rejection(s) of deliverables per contract year. The Government will reject a deliverable if five or more technical errors or five or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 30 business days of notification of Government rejection.

Surveillance will be conducted by the program manager monitoring receipt of deliverables and surveillance will be documented semi-annually by the COR in the

PAR.

Receipt of CDRL deliverable

4.2.2 There shall be no more than one

late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the Government.

Surveillance will be conducted by applicable MFT member(s) monitoring Contractor personnel and reporting performance to the

COR.

Surveillance will be documented, at a minimum, semi-annually by the COR in the PAR.

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 a count of contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than

Surveillance will be conducted by the program manager, verifying Contractor personnel qualifications by reviewing certification and other applicable documentation provided by the Contractor.

Surveillance will be documented, at a minimum, semi-annually by the COR in the PAR.

PR: FD2060-19-00038 QASP 5

October 31 of the following fiscal year.

Adherence to Contractor Quality Management System

5.10 100% compliance with the QMS is required.

Surveillance will be conducted by the COR reviewing the contractor’s QMS to ensure that it is effective in bringing the desired results (performance is equal to or greater than the SS metrics).

Surveillance will be documented semi-annually by the COR in the

PAR.

2.2 COR Online 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). At a minimum, the following documentation will be uploaded in the CORT Tool by the COR or PCO as applicable.

a. COR INFORMATION (COR Profile):

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 (upload as one document – refer to COR Training Instructions)

b. QASP (uploaded by PCO or COR)

c. Designation of Contracting Officer’s Representative (uploaded by PCO)

d. Annual COR File Inspection Checklist(s) (uploaded by PCO)

e. COR ONLINE FILE:

i. COR Status Reports/Surveillance:

PAR(s) CAR(s)

ii. COR Trip Reports (if applicable):

iii. COR Correspondence Reports:

Meeting Minutes Contractor correspondence

iv. Miscellaneous Documents:

PR: FD2060-19-00038 QASP 6

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 set a suspense date and forward the PAR to the PCO for submission to the Contractor.

The PCO will submit the PAR to the Contractor for corrective action. The Contractor shall explain the deficiency and identify the corrective action they shall take to resolve the deficiency and prevent recurrence. The Contractor shall sign and return a negative PAR to the PCO by the suspense date. The COR will upload the PAR in the CORT Tool under COR Status Reports.

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 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 deficiency is resolved to the satisfaction of the MFT.

The COR will upload the CAR in the CORT Tool under COR Status Reports. The CAR will become part of the PCO contract file. If the CAR process fails to resolve the deficiency, the PCO has the right to invoke the Inspection of Supply/Services clause(s) identified in the contract/order.

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. In accordance with AFI 63-138 dated 11 May 2017.

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 Program Manager.

PR: FD2060-19-00038 QASP 7

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 and Responsibilities of Multi-Functional Team (MFT)

3.0.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).

3.0.2 Engineer:

Works with MFT in conducting market research. Responsible for providing technical and engineering support to IPT members as required. 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).

3.0.3 Inventory Management Specialist (IMS):

Coordinates customer issues with IPT as needed to provide response to customer. Initiate and coordinate in conjunction with IPT members all cataloging and disposal actions. Identifies the requirement(s) and initiates, prepares, and coordinates funding documents (i.e. PR, MIPR) for buys and passes the repair requirements to PMS Buyer. Provide item-related support to IPT members.

Examples include, but are not limited to, identifying requirement, file maintenance, budget/requirement review, budget preparation, and other program reviews.

3.0.4 Equipment Specialist (ES):

Responsible for reporting all technical issues to the IPT. Primary point of contact for configuration control and configuration management. Responsible for technical documentation updates and accuracy and identifying such to the IPT. Examples include, but are not limited to, Time Compliance Technical Orders (TCTOs), Technical Orders (TOs), AFTO 22s, 202s and 252s, etc.

Provides technical support to the IPT including but not limited to the following; file maintenance and requirements methodology, failure data analyses via maintenance data documentation, configuration management, provisioning, Deficiency Report resolution via Material Improvement Project (MIP), IDEA evaluation and implements enhancements or modifications.

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.

PR: FD2060-19-00038 QASP 8

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 semi-annual 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, 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, and negative PAR(s) or CAR(s) annually.

PR: FD2060-19-00038 QASP 9

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.

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

PR: FD2060-19-00038 QASP 10

Checklist. Uploads the checklist in the CORT Tool under Annual COR File Inspection Checklist.

3.5 Quality Assurance Program Coordinator (QAPC)

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.

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, if applicable, international security requirements are met in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification, and applicable Government regulations.

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

PR: FD2060-19-00038 QASP 11

(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)

The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis. Reference PWS and QASP signature page.

4.0 Management Strategy

4.1 The MFT will meet and record minutes semi-annually to review contractor’s performance.

The COR will issue PARs, documenting both satisfactory and unsatisfactory Contractor performance. 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 recourse authorized by the Inspection of Supply/Services clause(s) identified in 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): The total estimated value of the contract exceeds $1,000,000.00; therefore, CPARS reporting is required.

PR: FD2060-19-00038 QASP 12

6.1 The MFT will evaluate Contractor performance. The Program Manager will review the PARs and other information contained in the COR Online File to prepare and substantiate the CPAR.

CPARS will be updated, at a minimum annually, documenting Contractor performance for the contract/order. More frequent updates may be made, as required, to document a significant improvement or decline in the level of Contractor performance.

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

6.3 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

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

PR: FD2060-19-00038 QASP 13

The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within eight 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: The 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-19-00038 QASP 14

9.0 Signatures

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

X Helen Porter, QAPC, 19-00038

AFSC/PZCA 478-222-1136

COR Date Patti Campbell, 408 SCMS/GULB, 478-222-4665

COR Supervisor Date Wesley Lister, 408 SCMS/GULB, 478-222-4672

PCO Date Janice Williams, AFSC/PZABB, 478-926-7140

Contractor Date Harris Corporation

By signing below, you are identifying that these services are not mission-essential.

Functional Director Date Levern Keels, 408 SCMS/CL, 478-926-3979

AN/ALQ-172(V) Countermeasures System (CMS)
Line Replaceable Units (LRU’S)-2 and -3
Reliability and Maintainability (R&M) Redesign
2018-05-30T16:00:49-0400
PORTER.HELEN.W.1229912450
2018-05-30T16:34:57-0400
LISTER.WESLEY.A.1394566558
2018-05-31T08:43:22-0400
CAMPBELL.PATTI.M.1138678519
2018-05-31T14:49:36-0400
MORGAN.JEFFREY.M.1230000626

File details come from the government source that posted it.