Attachment J2 - FSTSS QASP_Amend 0002.pdf

Quality Assurance Surveillance Plan

For

Flight School Training Simulation Services (FSTSS)

Revision 0

01 October 2021

Contract Number: TBD

Contract Description: Flight School Training Simulation Services

Contractor’s Name: TBD

(Hereafter referred to as the Contractor)

Marvin Hagan Michael Kilcrease

Contracting Officer (KO) Contracting Officer Representative (COR)

ACC Orlando US ARMY PEO-STRI

Orlando, FL Orlando, FL

TABLE OF CONTENTS

Subject Page Number

1. Overview

2. Description of Services

3. Roles and Responsibilities

4. Contract Quality Requirements

5. Government Surveillance

6. Non-Conforming Performance

7. Deduct Plan

8. Data Analysis

9. Acceptance of Services

10. COR Status Report

11. Service Contract Reporting (SCR) in the System for Award Management (SAM)

12. Contractor Performance Assessment Reporting System (CPARS)

13. Combating Trafficking In Persons (CTIP)

14. COR/Quality Assurance Surveillance Files

15. QASP Changes

16. DOCUMENT REVISION HISTORY

17. Attachments:

1. Overview.

1.1. Purpose. This Quality Assurance Surveillance Plan (QASP) is a Government developed document used to ensure that the Government receives quality services, and pays only for conforming services actually provided. The objective of this services contract is to acquire Flight

School Training Support Services (FSTSS) for the United States Army Aviation Center of

Excellence (USAACE) mission to enhance Aviator and Aviation Unit skills via the use of Virtual and Constructive training at Fort Rucker, AL as defined in the referenced Performance Work

Statement (PWS), section 1. The Contractor shall perform to the standards specified in FSTSS

PWS. This QASP identifies the methods and procedures the Government will use to ensure it receives the services to the desired standard, as identified in the PWS.

1.2. Intent. The intent of this QASP is to:

1) Ensure Contractor performance meets or exceeds contract terms, conditions and specifications

2) Hold the Contractor accountable for quality control

3) Encourage the Contractor to take appropriate steps to control and improve quality

4) Ensure all sections of Federal Acquisition Regulation (FAR) 46 are applied as required and applicable

1.3. Accordingly, the Government will perform surveillance on the contract in accordance with this QASP, but reserves the right to monitor the contract in any manner necessary, at any time necessary, and at all places necessary to ensure that the services rendered conform to contract requirements. The Government also reserves the right to perform quality assurance at the

Subcontractor level, and at the contractor's place of business. Sub-contract service providers shall be accountable to the Contractor who, in turn is responsible to the Government. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime

Contractor. The Government will not exercise any supervisory controls over the contract service providers performing the services herein.

2. Description of Services.

2.1. Scope of Work. The contractor shall furnish the necessary supplies, services, facilities and materials required to perform the work described within the FSTSS PWS, with associated annexes and references. The contractor shall provide an Integrated Master Schedule (IMS), Integrated

Master Plan (IMP), Safety Assessment Report (SAR), and the Quality Control Program (QCP) for the services provided to meet the requirements as defined in the PWS.

2.1.1. The FSTSS requirement consists of four parts: the UH-72A virtual simulators (VS), advanced aircraft virtual simulators (AAVS), air traffic Control (ATC) simulations, and the training support capability

2.1.2. The UH-72A VSs are required to support Phase I Primary Core training, the Rotary Wing

Instrument Flight Examiner’s Course (RWIFEC), and Foreign Military Sales/Foreign Military

Training (FMS/FMT) training courses. The number of UH-72A VSs will be as required to meet the Phase I Primary Core, RWIFEC, and FMS/FMT requirements defined in the FSTSS PWS

Appendix B during the standard training day as defined in the FSTSS PWS paragraphs 2.1.2.

thru 2.1.4. and Table 1.

2.1.3. The AAVSs are required to support training in the Phase II Advanced Tracks, Aircraft

Qualification Courses (AQCs), Professional Military Education (PME) courses, Maintenance

Test Pilot (MTP) Courses, Instructor Pilot Courses (IPCs), Methods Of Instruction/ Resident

Instructor Training (MOI/RIT) Courses, FMS/FMT, and Active Component/Reserve Component

(AC/RC) sustainment training. The Block I (threshold) AAVSs will include aircraft configurations for the AH-64D (In collective systems), AH-64E, CH-47F, UH-60M, and UH-

60L aircraft. AAVSs may include concurrency configurations for aircraft in the future.

Integration of additional aircraft configurations will be based on development and fielding schedules of the actual aircraft. Replacement/deletion of some aircraft type simulations may also be required over time. The number of AAVSs will be as required to meet the Phase II Advanced

Track, AQC, PME, MTP, IPC, MOI/RIT, IRTC, Aircrew Training Exercise (ATX), and AC/RC sustainment training requirements during the standard training day as defined in the FSTSS PWS paragraph 2.1.3.2. and Table 1.

2.1.4. The functionality and fidelity; visual system; training environment; interoperability; and command, control, communication, computer, cyber, intelligence, surveillance, and reconnaissance (C5ISR) capabilities of the UH-72A and AAVSs will be as required to train to standard the individual, crew, and collective tasks identified in the FSTSS PWS Appendices B thru G, and to conduct individual, crew, collective, combined arms, and joint levels of training.

2.1.5. The Air Traffic Control simulation services shall be provided to support Advanced

Individual Training (AIT) for MOS 15Q Air Traffic Control (ATC) Specialists. The number and type of simulations shall be as required to meet the needs of 400 MOS 15Q students per year with a surge of 10%, in both tower and RADAR systems, as defined in the FSTSS PWS paragraph 2.1.2 (including sub paragraphs) and table 1.

2.1.6. A training support capability is required to schedule, manage, operate, maintain, and upgrade the UH-72A, AAVSs, and ATC simulations; schedule the Aviation Combined Arms

Tactical Trainer-Aviation (AVCATT-A) and Synthetic Training Environment (STE)

Reconfigurable Virtual Collective Trainer-Aviation (RVCT-A); schedule government-owned simulators (Longbow Crew Trainer (LCT), Transportable Blackhawk Operations Simulator

/Blackhawk Aircrew Trainer (TBOS/BATS), Transportable Flight Proficiency Simulator (TFPS), and Cockpit Trainers (CPTs)) in use for training; integrate and optimize the training and concept exploration and experimentation activities for the USAACE simulation facilities; develop Tactics

Techniques and Procedures (TTPs); develop training products such as Training Support Packages

(TSPs), Combined Arms Training Strategies (CATS), Maintenance Test Procedures (MTPs), Aircrew Training Manuals (ATMs), terrain database products, and training scenario generation tools; and provide technical, tactical, and training development and implementation assistance in support of aviation training on both contractor and government-owned systems.

2.2. Type of Contract. The FSTSS contract will be a Firm Fixed Price, 12-year, single-award, Requirements Contract.

3. Roles and Responsibilities. The following provides a synopsis for the roles and their respective authority during the performance of the contract:

3.1. Government.

3.1.1. Contracting Officer (KO). The KO is the only person authorized to direct changes in any of the requirements under this contract. In the event the Contractor effects any such change at the direction of any person other than the KO, the change will be considered to have been made without authority, and solely at the risk of the Contractor. No changes in, or deviation from the terms and conditions shall be affected, without a written modification to the contract, executed by the KO authorizing such changes.

3.1.2. Contracting Officer’s Representative (COR). The COR will monitor all technical and performance aspects of the contract, and assist the (KO) in contract administration. The COR is authorized to perform the following functions:

Assure that the Contractor performs the technical requirements of the contract

Perform inspections necessary in connection with contract performance

Maintain written and oral communications with the Contractor concerning technical and performance aspects of the contract

Issue written interpretations of technical requirements, including Government drawings, designs, and specifications

Monitor Contractor's performance and documents and notifies both the Contracting Officer and Contractor of all deficiencies

Coordinate availability of Government furnished information

Provide site entry of Contractor

3.1.2.1. Army Contracting Command (ACC) does not use other acronyms to refer to and describe a COR. Terms such as the “COTR”, “Onsite COR”, “TM”, etc. will not be used. Some personnel may be assigned as Alternate CORs (ACORs), but other than a statement to that effect and what actions the KO expects that ACOR to take in the absence of the primary COR. There is no difference between a COR, an Alternate COR, or other Government surveillance personnel assigned to conduct contract oversight. Throughout the remainder of this QASP, The term “COR’ will be used to refer to all Government surveillance personnel assigned to monitor the contractor’s performance on this contract.

3.1.2.2. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost, price, or delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

3.1.2.3. The Contracting Officer shall use the DoD Joint Appointment Module (JAM) to electronically track COR nominations, appointments, terminations, and training certifications for each COR appointed to conduct oversight on this contract. The COR will upload their surveillance documents, such as COR Status Reports (CSR), COR trip reports, correspondence with the contractor, and other miscellaneous documents into the Surveillance and Performance Monitoring

(SPM) module within the online contract file. JAM and SPM module are available within the

Procurement Integrated Enterprise Environment (PIEE) suite of tools at: https://piee.eb.mil/.

3.1.2.4. Alternate Contracting Officer’s Representative (ACOR). The Alternate COR is an employee of the U.S. Government provided by the Requiring Activities (RA) and appointed by the

Contracting Officer to provide additional surveillance personnel in monitoring and documenting the contractor’s performance. These alternate surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance, if they meet all COR training and experience requirements and are appointed by the contracting officer as an ACOR in the JAM. This term will apply to other government surveillance personnel as defined in Army

Regulation 70-13, paragraph 2-2 g.

3.2. Contractor.

3.2.1. Program Manager. The Contractor responsible for running the program. May supervise the program team and manages conflicts within different departments. Plans and sets program goals and milestones and develops risk management strategies. Defines resources and schedules for the implementation of the program. Clearly defines requirements and sets targets accordingly.

Recognizes areas for internal improvement and develops plans for implementing the improvements.

3.2.2. Quality Manager. The Contractor responsible for promoting quality achievement and performance improvement throughout the organization. Develops, implements, communicates and maintains a quality plan to bring the Contractor’s Quality Systems and Policies into compliance with quality system requirements. Directs the activities of contractor quality personnel to measure key quality characteristics of services delivered and processes from inception to completion.

Establishes the standards of service for customers expected by the Requiring Activity.

For quick access, the contact information for the performance of this QASP is provided:

Government Personnel:

Table 1: Key Positions for Contract Administration

Title Name Phone e-mail

Contracting Officer Marvin

Hagan

(407) 208-3349 marvin.j.hagan.civ@mail.mil

COR/ACOR Michael

Kilcrease

(334) 255-2524 michael.a.kilcrease4.civ@mail.mil https://piee.eb.mil/

Contract Specialist Laura

Parsons

(407) 384-3867 Laura.l.psrsons.civ@mail.mil

Contractor Personnel:

Title Name Phone e-mail

Contract Manager TDB

Project Manager TDB

Quality Manager TDB

4. Contract Quality Requirements.

4.1. Contractor’s Quality Control Program (QCP). The Government will evaluate the adequacy of the Contractor’s QCP performance under this contract in accordance with this QASP.

The Contractor’s QCP is the means by which he assures himself that all work complies with the requirement of the contract PWS. It is essential that Government Surveillance Personnel understand that Quality Control (QC) is the responsibility of the contractor, and not the government.

4.1.2. As such, the government will focus their efforts on validating if the contractor is maintaining an adequate quality control inspection system that ensures the contractor maintains evidence that services provided conform to contract quality requirements. The Contractor shall provide inspection data to the Government on request for validation. The Contractor’s QCP shall include a process that can identify, prevent, and ensure non-recurrence of defective services.

4.2. Government Quality Assurance. This QASP describes what the Government will do to ensure that the Contractor has performed in accordance with the performance standards within the

PWS.

This QASP describes:

How the performance standards will be applied:

• The Performance Standard for each requirement in the PWS will be applied as prescribed in the PWS. Ensure that each Performance requirement within the PWS includes a Measurable performance standard in terms of quality, timeliness, or quantity.

• Ensure the method of assessing contractor performance against performance standards is included in this QASP

• Ensure each Performance Requirement includes an acceptable quality limit (AQL).

AQL is the worst tolerable performance that is still considered acceptable.

Example; if “the contractor shall provide personnel support within 2 hours”, the AQL may be: + or - (+/-) 15 minutes. See attachment 1, Contract/Task Order Performance Requirements

Summary.

Which performance elements will be surveilled (Attachment 5, APM Monthly Report)

• All performance activities will be surveilled through-out the Period of Performance, using a risk based approach. The selected items will be populated on the Monthly

Checklist and placed on the Surveillance Schedule for each period surveilled.

When the surveillance will be scheduled (Attachment 5, APM Monthly Report)

• Selected items for each month will be placed on the Surveillance Checklist and scheduled surveillance on the Monthly Schedule. Surveillance may be scheduled on a daily, weekly or monthly frequency. However, each contractor requirement must be audited for compliance prior to invoice payment being made.

The Acceptable Quality Limit (AQL)

• The AQL will be determined by the Requiring Activity, i.e., the COR.

The nature of Government contract quality assurance actions that include the number of observations made and the number and type of defects (defect rate)

• Personnel conducting contractor performance surveillance will use attachment 5, Assistant Program Manager (APM) Monthly Report, or equivalent to answer the

Performance question asked, and provide comments in the area provided on the checklist. These comments and metrics from the Checklist will be included on each

COR Surveillance Report (CSR) submitted during the Period of Performance.

5. Government Surveillance.

5.1. Methods of Surveillance. The following Methods of Surveillance may be utilized in monitoring the Contractors’ performance:

NOTE: The performance items selected for surveillance in this QASP as a minimum should contain those listed in the Performance Requirements Summary (PRS). The PRS is a stand-alone document that illustrates to the contractor the few, most salient items the government wishes the contractor to be aware of. The PRS is contained in the contract Performance Work

Statement (PWS). See Attachment 1 for PRS items.

100% Inspection will be reserved for the highest risk areas where consequence of failure may affect life or limb, or there is likelihood of mission failure. This inspection shall be an event to evaluate the contractor’s performance.

Customer Feedback. Not a valid method of surveillance, but a good indicator of areas where surveillance should be conducted or intensified. Firsthand information from the customers provides a qualitative method to be used in lieu of quantitative methods, supplements or complements quantitative standards. The Customer Complaint Record, Attachment 2, will be placed at convenient locations for the end user of these services, and made available to document/record all complaints. The COR will collect the Customer Complaints each surveillance cycle and investigate for validity ASAP.

• The following procedures will be followed when a complaint is received:

1. The COR/ACOR will investigate to determine the validity of the complaint

2. If the complaint is determined to be invalid, the COR will inform the person who submitted the complaint of the reason(s) as soon as practical

3. For validated complaints that are true contractual non-conformances, the procedures in paragraph 6 below will be applied

4. A Customer Complaint Log will be used to document each validated customer complaint and attached to the COR Monthly Surveillance Report in the SPM module

Contractor Performance Reports (CPRs). CPR’s will be delivered to the Government monthly. The CPR requirement can be satisfied by submission of CDRL A004 DI-QCIC-

81187 Quality Assessment Report

Trend Analysis. Should the Government witness a trend of previously undetected anomalies, the government will bring the trend to the attention of the contractor for resolution. The CPR requirement can be satisfied by submission of CDRL A004 DI-QCIC-81794 Quality

Assessment Report

100% Inspection Government will witness daily operations and review:

CPR’s

Entry and Exit Test

Readiness Reviews (TRRs)

Over and Above Work

Requests (OAWRs)

Invoices

Contract deliverables

Joint Test Plans and

Procedures (JTPPs)

-13,-14 Logs

Discrepancy Report (DR)

Closure Plan

Configuration Management

Audits

Contractor products

Input to Integrated Product

Teams (IPTs) and contract related meetings

Confirmation through review and verification of all contractor submitted performance reports, TRR data packages, OAWRs, invoices and contract deliverables. Verification through maintenance and DRs

Information Management

Systems (IMS). Verification of device configuration to accredited configuration.

Compare Contractor products and input to contractually defined processes and standards.

Customer Input Customer satisfaction interviews

Investigation and documentation of customer feedback

Contractor Self Reporting Contract Deliverable

Requirements List (CDRL’s), Program Management

Reviews (PMS’s), CPR’s, Review and confirm accuracy for use in trend analysis

Management Progress

Reviews

Note 1: Plus or minus signs may be used to indicate an improving (+) or worsening (-) trend insufficient to change the evaluation status.

Note 2: N/A (not applicable) should be used if the ratings are not going to be applied to a particular area for evaluation.

5.1.1. Surveillance Procedure: The goal of the QASP is to ensure that contractor performance is effectively monitored and documented. The COR’s contribution is their professional, non-adversarial relationships with the KO, PM and the Contractor, which enables positive, open and timely communications. The foundation of this relationship is built upon objective, fair, and consistent COR evaluations of contractor performance against contract requirements. The COR uses the methods contained in this QASP to ensure the contractor is in compliance with contract requirements. The COR function is responsible for a wide range of surveillance requirements that effectively measure and evaluate the contractor’s performance. Additionally, this QASP is based on the premise that the contractor, not the Government, is responsible for management and QC/QA actions to successfully meet the terms of the contract.

5.2. Surveillance Schedule. (Required) A Surveillance Schedule (Attachment 4) will be created each month. Locally generated equivalent is acceptable. The schedule is “FOR OFFICIAL

USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each

Month’s Surveillance Schedule will be completed at the beginning of each month during the

Period of Performance (PoP) to schedule the upcoming month surveillance activity. Completed

Surveillance Schedules will be filed in the online Surveillance and Performance Monitoring (SPM) module located within (https://piee.eb.mil) file for this contract, either as an attachment to the

CSR, or uploaded separately in the Miscellaneous Documents Section.

5.3. Surveillance Checklists. (Required) The APM Monthly Report (Attachment 5) will be created each month. Locally generated equivalent is acceptable. The Checklist is “FOR OFFICIAL

USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each

Month’s Surveillance Checklist will be completed with the Surveillance Schedule. Completed

Surveillance Checklist will be filed in the online Surveillance and Performance Monitoring (SPM) module located within (https://piee.eb.mil) file for this contract, either as an attachment to COR

Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

Note: Surveillance Schedules and Checklists are considered COR documentation and must be uploaded in the SPM module. Smartforms are available for use at the individual record level under “Add Smart Form”

5.4. Surveillance Documentation. Each months’ Completed Surveillance Documentation, to include the COR Status Report must be filed in the online Surveillance and Performance

Monitoring (SPM) module located within (https://piee.eb.mil) file for this contract. The COR

Status Report (Smart Form) must be utilized, supporting documentation can be uploaded as an attachment.

https://piee.eb.mil/

6. Non-Conforming Performance. A Non-conformance occurs when the Contractor fails to meet the terms, conditions and/or specifications of the Contract/Task Order. All instances of non-conformance must be documented by the COR. The COR will provide the details of the non-conformance using the Contractor Nonconformance Report (CNR), Attachment 8 to the KO, who will notify the Contractor of each nonconformance occurrence, unless the KO has authorized the

COR to submit directly to the Contractor, and copy the KO. Resolution of any non-conformance discovered at the Subcontractor level will be addressed with the prime Contractor. Level I, II and

III non-conformances are defined below and shall be stated on each newly initiated NCR.

6.1. Level I (Minor). Level I non-conformance is not likely to materially reduce the usability of services for their intended purpose or is a departure from established standards having little bearing on completing the contract requirement. Minor non-conformances can usually be corrected on the spot and can be issued to the Contractor through either a verbal or written

Contractor Nonconformance Report (CNR). However, the Government is required to document verbal Level I CNRs. The COR may issue verbal Level I CNRs directly to the appropriate level of

Contractor management. The COR will notify the KO as soon as practical when a verbal Level I

CNR is issued and document them in their Monthly Reports. If the non-conformance cannot be corrected on the spot, the Contractor shall be given a suspense date to correct the deficiency. The

KO will issue and sign written Level I CNRs, Attachment 8.

6.2. Level II (Major). Level II non-conformance is likely to result in failure of the services to meet contract requirements. Also, repeated discrepancies, a large number of documented Level I

CNRs and trends indicating failure of the Contractor’s quality control program can be classified as

Level II CNRs. The KO issues all Level II CNRs in writing, Attachment 5. The COR will notify the KO as soon as practical when a major non-conformance is identified.

6.3. Level III (Critical). Level III non-conformances result in hazardous or unsafe conditions due to the manner in which the services are performed; prevent or impact a vital agency mission as a result of performance; or are for repeated or uncorrected Level II CNRs. The Contracting Office

Director or Deputy Director issues written Level III CNRs. The COR is responsible for notifying the KO immediately upon discovery of a critical non-conformance.

6.4. Documenting CNRs. The COR will provide the details of the non-conformance using the

CNR, Attachment 8. If the Requiring activity prefers to issue a locally developed CNR, documentation must include as a minimum: the Contract or Task Order number; reference to the specific contract requirement; the specific discrepancy to the requirement and classification level

(I, II or III); where it was discovered; the date and time it was discovered; Contractor representative who was notified; and the suspense date for Contractor response/corrective action.

6.5. Tracking and Resolving CNRs. All CNRs, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track CNRs to ensure the

Contractor identifies and takes appropriate corrective action to the root cause and the specific non-conformance is corrected within the required timeline. The KO will make a final written determination of the Government’s remedies if the non-conformance is not corrected by the

Contractor after receiving notice and a reasonable opportunity to correct the work.

7. Deduct Plan. This acquisition does include a Deduct Plan. Deductions will be IAW the schedules and formulas below. This section specifies the Performance Objectives and

Performance Elements for the Contractor. The Performance Standards are representative of a

Satisfactory rating within the Government QASP. The AQLs for selected Performance Standards are not all inclusive and subject to modification as required or directed.

7.1. Performance Standards.

7.1.1. Standard: Simulation Services capabilities are delivered with the requisite functionality and fidelity that facilitate training all tasks identified in this PWS, to standard, with no negative habit transfer to the actual aircraft, as accredited IAW PWS paragraphs 3.1. and 3.15.2., Services

Accreditation/ Ready for Training.

7.1.2. AQL: No safety risks are noted and no injuries occurred during mission due to safety violations attributable to Contractor action(s).

7.1.3. Standard: The Contractor shall maintain a minimum 97.5 percent Ao using the formula for Ao below. The Contractor shall calculate Ao for each simulator type identified in figure 5 on a calendar month basis.

7.2. Operational Availability. The following formula shall be used to calculate simulator

Operational Availability (Ao). (Formula factors are defined in Figure 2 below.)

Where

7.2.1. Ao shall be calculated monthly in support of the Schedule of Deductions; Contract

Performance Report (CPR), and Contract paragraph G.2 (Payment Deductions, and DD Forms

250).

7.2.2. The Ao formula above would exclude lost time resulting from events such as natural disasters, severe weather warnings and facility power outages caused by external power supply source failure. If such an event were to occur, its impact will be discussed with the on-site PEO

STRI APM to determine the appropriate adjustments.

(CMT+NCMT) – (HrsLost + PMC q

(CMT+NCMT)

Ao = X 100

PMC

q = HrsPMC X PMC factor

7.2.3. Partial Mission Capability (PMC). Determination of the amount of partial mission degradation shall be based on objective simulator and subsystem functionality factors alone (as defined in Annex A and the Ao formula above).

7.2.3.1. Acceptance for training. Acceptance of a device in PMC status is an elective choice made by the cognizant Government representative when he/she determines that a productive training mission is achievable using a device that is not fully mission capable. When a Government representative accepts a PMC device for training, the PMC quotient (PMCq) shall be applied in accordance with the Ao formula above for the entire training period.

7.2.4. NMC & PMC. Deductions shall not be taken for scheduled and Government approved modifications or technology insertions performed to improve reliability or maintainability of the simulators until such modification or technology insertions are accepted.

7.2.5. Training Period Interruptions. The Contractor shall make every effort to minimize training period interruptions. However, should total corrective maintenance time exceed 15 minutes during a training period, from the time the IP calls for assistance, the contractor shall record PMCq for the entire training if the Government elects to continue with training despite the interruption(s). Hours Lost (HrsLost) shall be applicable if training is rescheduled to another time period. If training is moved to another Simulation Services device, resulting in no more than 15 minutes lost training during any portion of the scheduled training period, hours lost shall not be applicable. Training may only be moved to another device one time per training session.

7.2.5.1. Missed Periods/Make-Up. Should any scheduled training periods be missed the contractor shall, at the Government’s discretion, provide make-up training at no additional cost to the Government. The use of make-up periods is an elective choice made by the Government. The rescheduled training shall not eliminate the HrsLost applied for the previously lost periods.

7.2.6. Factor Definitions: Simulator Operational Availability (Ao) formula factors are defined in Figure 3.

Note* Partial Mission Capability Factors (PMCfactor) to be applied when a device is designated as not fully Mission Capable are identified in Annex A.

7.3. Schedule of Deductions.

7.3.1. When the computed Operational Availability (Ao) for a calendar month falls below the threshold of 97.5%, the Government may, at its discretion, apply deductions to the contractor payment. The following formula will be used to determine the Schedule of Deductions (Formula factors are defined in Figure 4 below): Ao shall be aggregated by platform type (see Figure 5) to determine applicable deduction factors.

7.3.2. If applicable, Contractor may submit mitigating circumstances each month requesting waiver of deductions or a reduced amount. Mitigating circumstances to be considered, among other things, consist of Turn-around-time to fix the deficiency, responsiveness, resources expended, timely notification of each incident and routine updates, steps taken to lessen impact to training, NCMT provided during the month, etc. The decision to reduce or eliminate deductions for the month shall be the sole discretion of PEO-STRI.

DEDUCTION = (DEDfactor) X (HRSLOST + PMCq) X (HRLYRATE)

Formula Factor

Non-contracted Mission Time (NCMT) is the number of contractor-provided simulator flight hours required to support training requirements over and above those defined Table 1.

NCMT

The number of contractor-provided simulator flight hours required to support training as defined in Table 1.

CMT

Definition

Figure 3 - Ao Formula Factors Definitions

The Partial Mission Capability Factor (PMCfactor) quantifies the amount of degradation of full mission capability by source/subsystem and simulator type. These factors are identified in Annex A. PMCfactor is applied when a device is designated by a cognizant government representative as not Fully Mission Capable

PMCfactor

HrsPMC

The number of CMT hours that a training device is used for training in less than fully mission capable condition, when, as approved by PEO-STRI, the status causing the less-than-fully-mission-capable condition was a factor in the scheduled training event.

The Partial Mission Capability Quotient (PMCq) is the sum total of the products of the applicable PMCfactor and HrsPMC for each instance when a training device is used in less than a fully mission capable condition.

PMCq

Hours Lost (HrsLost) are the number of simulator flight hours (CMT) lost due to device non-availability (i.e. when a device is designated as “Not Mission Capable – NMC”, or is not available for training). Scheduled simulator non-availability for Government approved modifications and upgrades will not be charged as HRS Lost.

HrsLost

7.4. Incentives. The FSTSS is a rotary-wing aviation simulation services requirement that will be a single-source Requirements contract with the ability to issue FFP TOs. The FSTSS requirement will be competed as full and open. The resulting contract will contain an initial 5-year ordering period (1-year base and four 1-year options) with 7 award ordering periods of 1 year each, for a total of a 12-year ordering period. This ordering period structure is due to availability of

Operations and Maintenance, Army (OMA) appropriations and shall not exceed 12 years.

The contract will also contain award term provisions, used by the Government in a fixed-price contract, to award a Contractor for exceeding the performance requirements of the contract. The award term provides for the evaluation of performance, and together with Agency needs and availability of funding, serves as the basis for award term decisions that can either extend the base contract ordering period through the award of available award ordering periods, or reduce the contract by reducing available award ordering periods. The remaining ordering periods 6 through

Formula Factor

Figure 4 – Schedule of Deduction Definitions

Definition

DEDfactor The Deduction Factor (DEDfactor) is the numeric factor from Figure 5 below based on the computed Ao of the simulator type by month.

HrsLost

Hours Lost (HrsLost) are the number of simulator hours (CMT) lost due to device non-availability (i.e. when a device is designated as “Not Mission Capable – NMC”, or is not available for training). This is the same term used in computing Ao above.)

PMCq The Partial Mission Capability Quotient (PMCq) is the sum total of the products of the applicable PMCfactor and HrsPMC for each instance when a training device is used in less than a fully mission capable condition. (This is the same term used in computing Ao above.)

HrlyRate

Hourly Deduction Rate (HrlyRate) is the applicable hourly rate deduction from Figure 6 to be applied in computing the total payment deduction to contractor payments for a given month.

UH- 72A AH-64E CH-47F UH-60L UH-60M RCTD ATC

> 97.5 0 0 0 0 0 0 0

90.0 < 97.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5

85.0 < 90.0 0.7 0.7 0.7 0.7 0.7 0.7 0.7

< 85.0 1 1 1 1 1 1 1

Figure 5 - Deduction Factors

Deduction by Simulator Type

Computed Ao

12 (award ordering periods) can be earned or lost in yearly increments, based on each year’s cumulative performance evaluation score, starting in calendar year 2023. Award ordering periods six and seven will be available to earn for the Contractor to continue realizing a return on their investment. The remaining periods 8 through 12 (award ordering periods) will be available to earn for the Contractor to achieve profit on their fully amortized investment. The maximum ordering period shall be 12 years.

7.5. Surveillance Matrix: The Surveillance Matrix (Attachment 3) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance and frequency the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.

7.5.1. DFARS 222.17 mandates including surveillance for ensuring compliance with Combatting

Trafficking in Persons (CTIP) in the QASP. Use the CTIP in Attachment 9 to assess compliance with the surveillance requirement. Additional information can be found on the DOD CTIP website.

7.5.2. Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance.

The Government performs surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The Performance

Requirement Summary (PRS) should be used to form the foundation of the COR’s inspection checklist.

7.6. Performance Rating Definitions: The performance ratings below reflect definitions at

FAR 42.1503 Table 42-1. The COR will use these rating to evaluate the quality of contractor’s performance.

Performance

Rating

Definition

Exceptional Performance meets contractual requirements and exceeds many to the government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with few minor problems for which corrective actions taken by the contractor were highly effective.

Very Good Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with some minor problems for which corrective actions taken by the contractor were effective.

Satisfactory Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the contractor appear or were satisfactory.

Marginal Performance does not meet some contractual requirements. The contractual performance of the element or sub-element being evaluated reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only 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 of the element or sub-element contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

8. Data Analysis. Data Analysis will be performed to identify trends in cost, schedule and/or performance risks. The results of Data Analysis will be documented in COR Status Report and may be used to make adjustments to surveillance schedules and/or checklist items to increase or decrease surveillance, based on performance trends. Negative trends noted using Government data/observations could result in issuing the Contractor Nonconformance Report. Trends noted using Contractor data will not result in a CNR unless the Contractor has not addressed the negative trend. QASP changes based on Data Analysis will be coordinated with the Contracting Officer for approval.

9. Acceptance of Services. When all services have been deemed acceptable and there is documented, objective, quality evidence to support acceptable performance, the COR will accept the services provided and authorize payment to the Contractor. Acceptance and payment will be made by approving the Contractor’s Receiving Reports in Wide Area Workflow at https://piee.eb.mil/ as an iRAPT Inspector, and/or Acceptor.

10. COR Status Report (CSR). The CSR will be submitted on a monthly basis to the

Contracting Officer via the SPM module. CSRs must be uploaded into the SPM module using the

“Smart Form”. CSRs will be due NLT the 10th day of the month following the month of surveillance. CSRs will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis must contain a summary of surveillances performed, Customer

Feedback if any, CNRs if any, any analysis of the Contractors performance, recommended adjustments to surveillance schedules, and any other pertinent contract information IAW FAR

46.104, and the COR Appointment Letter. Completed Surveillance Checklists and CNRs, if any, will be included as attachments to CSRs. See para 5.4.

11. Service Contract Reporting (SCR) in the System for Award Management (SAM).

https://www.sam.gov. Reporting Labor Hours. The Office of the Secretary of Defense (OSD) memorandum, “Revised Department of Defense Contractor Manpower Reporting Initiative,” dated

October 16, 2019, provides new implementing direction for contractor reporting of manpower data with regard to the performance of DoD services contracts consistent with the requirements of title

10, U.S.C, section 235 and 2330a, as amended. The system allows industry to report all manpower data into a single Federal-wide portal. For Contractors who meet the SCR reporting thresholds (in excess of $3 million), your entity must be registered in SAM, and the user https://www.sam.gov/ responsible for reporting must have an individual user account in the system and the Service

Contract Inventory (SCI) Reporter user role to access reporting functionality.

11.1. SCI Reporters are required to enter the following information:

Total Amount Invoiced: Total dollar amount invoiced for services performed during the previous Government fiscal year under the contract (this amount should include the prime and any subcontract amount).

Prime Contractor Hours Expended: Prime contractor direct labor hours expended on the services performed during the previous Government fiscal year. The amount you enter is automatically divided by 2,080 hours to calculate a Full Time Employee (FTE) equivalent, displayed under the Prime Contractor Hours Expended as Prime Contractor FTEs.

Report any required Tier 1 subcontractor information.

11.2. Contractor reporting is required annually, by October 31, on the services performed under the contract or order, including any subcontracts, during the preceding Government fiscal year

(October 1-September 30). Contracting officers shall ensure that the requirement to report contractor manpower is included in all contracts, task/delivery orders and modifications.

12. Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (CSRs, Completed Surveillance Checklists, Customer Feedback and CDRs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with

AFARS, Subpart 5142.15 – Contractor Performance Information.

13. Combating Trafficking In Persons (CTIP). In accordance with PGI 222.17 and FAR

52.222-50, the KO will be notified immediately of any information from any source that alleges a

Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

14. COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance

Surveillance Files will be maintained in the on-line JAM and SPM module IAW DODI 5000.72, and DFARS PGI 201.602-2.

15. QASP Changes. This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications by the KO, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

COR’S Signature Block Date

Contracting Officer’s Signature Block Date

16. Document Revision History.

16.1. This QASP is a living document and, as such, may be changed as needed based on Data

Analysis (trends), contract modifications, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

Version

Effective

Date

Originator Summary of Changes

17. Attachments:

1. Performance Requirements Summary (PRS)

2. Customer Complaint Record DA 5477

3. Surveillance Matrix

4. Surveillance Schedule

5. APM Monthly Report/Surveillance Checklist

6. Corrective Action Report

7. Contractor Nonconformance Report (CNR) DA Form 5479

8. Combating Trafficking in Persons (CTIP)

Attachment 1

Contract/Task Order Performance Requirements Summary

(PRS)

Required Services

Performanc e Standard

Acceptable

Quality Level

(AQL)

Method of

Surveillance

Incentive (Positive and/or Negative)

UH-72A VS

Operational

Availability Ao

Requirements

Monthly Ao ≥ 97.5% 100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-72A VS

Training Period

Interruptions

Upon

Notification by Instructor

Pilot

Interruption ≤

15 Minutes in

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH72A VS

CDRL(s)

Submission

Monthly Within 3 Days

After End of the Month

100% Review ATP Determination

UH-60L AAVS

Operational

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60L AAVS

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60L AAVS

of End of the

Month

UH-60M AAVS

Operational

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60M AAVS

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60M AAVS

CH-47F AAVS

Operational

Monthly Ao ≥ 97.5% 100% R100%

Review, Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

CH-47F AAVS

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

CH-47F AAVS

AH-64E AAVS

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

AH-60E AAVS

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

AH-64E AAVS

UH-60L RCTD

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

UH-60L RCTD

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60L RCTD

UH-60M RCTD

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

UH-60M RCTD

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

UH-60M RCTD

CH-47F RCTD

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

CH-47F RCTD

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

CH-47F RCTD

AH-64D RCTD

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

AH-64D RCTD

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

AH-64D RCTD

AH-64E RCTD

AAVS Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

AH-64E RCTD

AAVS Training

Period Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

AH-64E RCTD

Tower Simulator

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

Tower Simulator

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

Tower Simulator

RADAR Simulator

Operational

Daily Review of all

DA Forms 2408-13-

1eview

ATP

Determination, Schedule of

Deductions

RADAR Simulator

Training Period

Interruptions

Upon

Notification

Duration

100% Review, Daily Review of all

DA Forms 2408-13-1

ATP

Determination, Schedule of

Deductions

RADAR Simulator

Attachment 2

Customer Complaint Record

DA FORM

5477_Customer Compliant.pdf

Attachment 3

Surveillance Matrix

100% Inspection Government will witness daily operations and review:

CPR’s

Entry and Exit Test

Readiness Reviews (TRRs)

Over and Above Work

Requests (OAWRs)

Invoices

Contract deliverables

Joint Test Plans and

Procedures (JTPPs)

-13,-14 Logs

Discrepancy Report (DR)

Closure Plan

Configuration Management

Audits

Contractor products

Input to Integrated Product

Teams (IPTs) and contract related meetings

Confirmation through review and verification of all contractor submitted performance reports, TRR data packages, OAWRs, invoices and contract deliverables. Verification through maintenance and

DRs Information

Management Systems (IMS).

Verification of device configuration to accredited configuration. Compare

Contractor products and input to contractually defined processes and standards.

Customer Input Customer satisfaction interviews

Investigation and documentation of customer feedback

Contractor Self Reporting Contract Deliverable

Requirements List (CDRL’s), Program Management

Reviews (PMS’s), CPR’s, Management Progress

Reviews

Review and confirm accuracy for use in trend analysis

Attachment 4

Surveillance Schedule

Req #1 Req#2 Req#3 Req #4

Due Date

8 Jun 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

8 Jul 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

8 Aug 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

8 Sep 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

8 Oct 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

8 Nov 23 Para 2.2.1.-2.1.4. Para 7. Para 3.14.1. Para 3.1

Req #5 Req #6 Req #7 Req #8

Due Date

8 Jun 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

8 Jul 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

8 Aug 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

8 Sep 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

8 Oct 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

8 Nov 23 PWS 7. PWS 3.6. PWS 5.1. PWS 2.4.5.

Attachment 5

Assistant Program Manager (APM) Monthly Report/

Surveillance Checklist

(Submit to PEO STRI TSO FSXXI Program Officer NLT 8th of each month) Date:

X/X/XXXX

APM’s Name: Doe, Joe (JD) APM’s Phone Number: (XXX) XXX-XXXX

Device(s): Individual / Crew, Collective

Contractor Lead’s Name:…