Attachment (14) Leesville MTCCS II Sample QASP_CUI.docx

CUI

MTCCS-FTPOLK QASP

ATTACHMENT 6

ATTENTION

Controlled by: US Army ACC Orlando Controlled by: MTC III AC AMIM-HDO-T CUI Category: General Procurement and Acquisition Distribution/Limited Dissemination Control: FEDCON POC: Daniel Steinhauer/407-208-5820

ATTENTION

All individuals handling this information are required to protect it from unauthorized disclosure.

Handling, storage, reproduction, and disposition of the attached document(s) must be in accordance with 32 CFR Part 2002 and applicable agency policy.

Access to and dissemination of Controlled Unclassified Information shall be allowed as necessary and permissible to any individual(s), organization(s), or grouping(s) of users, provided such access or dissemination is consistent with or in furtherance of a Lawful Government Purpose and in a manner consistent with applicable law, regulations, and Government-wide policies.

Standard Form 901 (11‐18) Prescribed by GSA/ISOO | 32 CFR 2002

Quality Assurance Surveillance Plan (QASP)

For

Leesville, LOUISANA Directorate of Plans, Training, Mobilization and Security MTC Operational Services

14 Sept 2022

Contracting Officer Contracting Officer’s Representative ACC-ORLANDO

"This plan is provided for information purposes only. The Government has the right to change or modify inspection methods at its discretion."

TABLE OF CONTENTS

Subject Page Number

1. Overview 3

2. Description of Services 3

3. Roles and Responsibilities 4

4. Contract Quality Requirements 5

5. Government Surveillance 6

6. Non-Conforming Performance 7

7. Deduct Plan 8

8. Data Analysis 8

9. Acceptance of Services 8

10. COR Status Report 8

13. Combating Trafficking In Persons 9

14. COR/Quality Assurance Surveillance Files 9

15. QASP Changes 9

UNCLASSIFIED//FOR OFFICIAL USE ONLY PROCURMENT SENSITIVE

1. Overview

1.1 Purpose: The purpose of this plan is to identify the methods and procedures the Government will use to ensure it receives the services/products under this contract as identified in the Performance Work Statement (PWS).

1.2 The intent of this plan is to hold the Contractor accountable for quality control and to encourage the contractor to take appropriate steps to control and improve quality. The Contractor is responsible to develop an efficient methodology to ensure they meet and/or exceed the required thresholds of service as outlined in this acquisition. The Government intends to perform surveillance on this contract in accordance with this Quality Assurance Surveillance Plan (QASP), but reserves the right to monitor the contract in any manner necessary, at any times necessary, and at all places necessary to ensure that the rendered services conform to contract requirements. The Government reserves the right to perform quality assurance at the subcontract level and perform quality assurance at the contractor's place of business, if applicable. Non-conforming services discovered with subcontractors will be addressed with the prime contractor for resolution.

2. Description of Services

2.1 Scope of Work. Services include support in conducting computer driven Live, Virtual, Constructive and Games for Training (GFT) simulation exercises for Active Army, Army Reserve, Army National Guard and other units in Joint, Combined and Service oriented command and staff actions from Individual through Brigade / BCT level. The contractor shall provide the services under this contract, to include individual through collective mission command training, support to mission rehearsal exercises, staff planning, leader training/development, live simulations, virtual simulations, constructive simulations, GFT, database preparation and maintenance; scenario creation; contractor controller training and functions; exercise controller training; marketing of available systems and exercises, simulations/simulators operation and management, and post exercise actions, to include facility cleanup, and maintenance; installation and maintenance of communications lines, circuits, and equipment, network and system administration on simulations network, NIPR and SIPR Local Area Networks (LAN), and functional area research. The MTC provides a facility for simulations training and the contractor shall provide an access control capability. It provides battle staff training “on demand” which is coordinated and facilitated through the central scheduling function on the BMTC SharePoint Page. The frequency for the battle staff events are IAW DA Mission Command Training Strategy, BMTC Regulations and annexes that address the Digital Training Program.

2.2 Contract. The MTC contract is a Fixed price contract; five year (one base and four options). Inspection of Services FAR Clause 52.246-4 Inspection of Services—Fixed Price or Higher Level Quality Requirements FAR Clause 52.246-11.

3. ROLES AND RESPONSIBILITIES.

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 property

· Provide site entry of Contractor

ACC doesn’t 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, 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.

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.

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 are available within the Procurement Integrated Enterprise Environment (PIEE) suite of tools at: https://piee.eb.mil/.

3.1.2.1 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 Alternate CORs (ACOR) in the Joint Appointment Module (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.

4. Contract Quality Requirements.

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

The Contractor’s quality control program 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.

As such, the government will focus their efforts on validating if the contractor is maintaining an adequate quality control inspection systems 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. CONTRACT QUALITY REQUIREMENTS

4.1. Quality Control Program. The Contractor's Quality Control Program requirements are defined in paragraph C.2.2. of the PWS. The Contractor shall develop, maintain, enforce and document a Quality Control Plan (QCP) which complies with the requirements of this contract and outlines how they will ensure the Government will receive all the services required by the contract at the specified quality level.

4.2. Government Quality Assurance. The Government will perform Quality Assurance oversight of the Contractor and Contractor’s QCP IAW with this QASP to ensure acceptable levels of contract performance are achieved and that the contractor is performing acceptable levels of Quality Control to ensure fully acceptable services are provided.

5. Government Surveillance.

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

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

1. Random Sampling Will be used when a service is performed on a frequent basis and a statistically valid sample can be selected for audit. This is most appropriate method for frequently recurring tasks

1. Periodic Inspection Will be used when planned sampling of a service is at a specific predetermined date and time. This is most appropriate for tasks that occur infrequently, yet on a scheduled basis

1. Customer Feedback. Not a valid method of surveillance, but a good indicator of areas where surveillance should be conducted or intensified.

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

5.2. Surveillance Schedule. (Required) A Surveillance Schedule (Attachment 3) 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 COR Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

5.3. Surveillance Checklists. (Required) A Surveillance Checklist (Attachment 4) 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.

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) for this contract. If the PWS/SOW/CDRL require "progress reports" from the contractor. The COR file will contain copies of all required progress reports.

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

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 Nonconformance Report (NCR), Attachment 5 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.

Non-conformances are classified as either: Level I (Minor); Level II (Major); or Level III (Critical).

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 (NCR). However, the Government is required to document verbal Level I NCRs. The COR may issue verbal Level I NCRs directly to the appropriate level of Contractor management. The COR will notify the KO as soon as practical when a verbal Level I NCR 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 NCRs, Attachment 5.

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 NCRs and trends indicating failure of the Contractor’s quality control program can be classified as Level II NCRs. The KO issues all Level II NCRs 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 NCRs. The Contracting Office Director or Deputy Director issues written Level III NCRs. The COR is responsible for notifying the KO immediately upon discovery of a critical non-conformance.

6.4. Documenting NCRs. The COR will provide the details of the non-conformance using the NCR, Attachment 5. If the Requiring activity prefers to issue a locally developed NCR, documentation must include as a minimum: the Contract or Task Order number; reference to the specific contract requirement; the specific discrepancy to the requirement; 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 NCRs. All NCRs, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track NCRs 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 not include a Deduct Plan.

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 NCR 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 a WAWF Inspector, and/or Acceptor.

10. COR Status Report. COR Status Reports (CSR) will be submitted on a monthly basis to the Contracting Officer via the Surveillance and Performance Monitoring (SPM) module. CSRs must be uploaded into the Surveillance and Performance Monitoring (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, NCRs if any, an 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 NCRs, if any, will be included as attachments to COR Status Reports. See para 5.4.

11. Service Contract Reporting (SCR) in the System for Award Management (SAM). https://www.sam.gov. Reporting Labor Hours. Service contractor reporting of information is required in the System for Award Management (SAM) when a contract or order- 1) Has a total estimated value, including options, that exceeds $3 million; and 2) Is for services in the following service acquisition portfolio groups (see PGI 204.1703 for a list of applicable product and service codes):

(1) Logistics management services.

(2) Equipment-related services.

(3) Knowledge-based services.

(4) Electronics and communications 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.

SCR requires contractors to enter the following information for their contract or order:

(1) The total dollar amount invoiced for services performed during the preceding Government fiscal year under the contract or order.

(2) The number of Contractor direct labor hours, to include first-tier subcontractor direct labor hours, as applicable, expended on the services performed under the contract or order during the previous Government fiscal year.

Contractor reporting is required annually, by October 31, on the services performed under the contract or order, including any first-tier subcontracts, during the preceding Government fiscal year (October 1-September 30). For indefinite delivery contracts, basic ordering agreements, and blanket purchase agreements, 1) Reporting is required for each order issued under the contract or agreement that meets the requirements of PGI 204.1703 and, 2) Service contract reporting is not required for the basic contract or agreement. 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 (COR Status Reports, 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 Joint Appointment Module (JAM) and Surveillance and Performance Monitoring (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.

DOCUMENT REVISION HISTORY

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.

1.0

COR NAME

Attachments:

1. Performance Requirements Summary (PRS)

2. Contract Discrepancy Report

3. Surveillance Schedule

4. Surveillance Log

5. Non-conformance Report (NCR)

ATTACHMENT 1

Performance Requirements Summary (PRS) and frequency/type of surveillance. The following PRS contains the required checks and frequency and type of checks to be performed.

PRS # 1 Provide physical security for all material, equipment, data, and information handled during contract performance & perform operations on, have access to, or handle data and information that contain sensitive, proprietary, or privacy information or data

and be a U.S. Citizen.

PRS # 2 Prepare, execute and manage pre-exercise setup of all facilities; prepare, execute and manage post- exercise recovery and reset of all facilities back to their original configuration; assist in the overall management of Soldier details (preparing for, supporting and recovering during exercises). Setup and manage parking areas used during exercises; set up workstations and work areas to support an exercise , seminar or working group; configure all telecommunications for exercises, seminars or working groups; brief exercise participants regarding facility management plans.

Waivers must be submitted and granted for less than qualified personnel.

PRS # 4 Conduct training Unit (Brigade, Battalion, and Company) progressive planning, meetings, In- Progress Reviews (IPRs) and technical integrated working groups (TIWG), appropriate to the Training Event.

meeting.

PRS # 5. Organize and staff, leveraging the Gaming/FPS suites, infrastructure of from 1 to 3 suites, in order to routinely apply a ‘blended’ training environment to Combined Arms Maneuver (CAM) and Wide Area Security (WAS) collective training tasks using present and future fielded Gaming and L/V/C Capabilities for TEWT, STX, FTX, CALFEX, FCX event designs.

PRS # 6 Provide Company/Battery/Troop echelon formations with collective training environments and Events (includes both Offensive & Defensive operations and Stability & Support operations) based on the commander‘s training objectives.

performance issues.

PRS # 7 Create After Action Review (AAR) Plans for the Event participant audience, outlining data collection, analysis parameters, presentations, and final AAR report.

PRS # 8 The contractor shall plan, install, manage, maintain, and recover all wide area networks and local area networks (WAN/LAN) to ensure timely operation of training and exercises.

Provide systems administration and systems management support for all networks including NIPR and SIPR. Maintain all training network systems in compliance with DoD Risk Management Framework (RMF) Program requirements. Install, maintain, and manage HBSS on all MTC Network Enclaves as part of the defense-in-depth security strategy.

compliance is completed within 48 hours of issuance of new STIG/IAVA patches.

100% implementation or mitigations are appropriately documented.

PRS # 9 Operate the Help Desk within current MTC Help Desk management system and coordinate Network Enterprise Center (NEC) support through the REMEDY Work Order system for NEC support when required.

Respond to help desk inquiries within one (1) hour of receipt and provide diagnosis of problem within two (2) hours. All requests that require NEC support shall be submitted in REMEDY within two (2) hours.

PRS # 10 Maintain and integrate a Master Training calendar(s) or training calendars (Outlook, MTC SharePoint site, current knowledge management tools, or approved Government scheduling tools) with SharePoint to schedule and track the usage of all MTC facilities and space including but not limited to the following: training and non-training events; facility use; VTCs; virtual simulators (both present and future systems) and simulations; TOC pads; briefings and tours.

PRS # 11 Provide one instructor per every 20 students in MCS training. MCS training requirement is max of 2 classes per month of any combination of MTC provided MCIS classes.

Instructor per 20 students.

PRS # 12 Employ and incorporate the models and simulations into exercises to provide realistic and in depth training environments to the training audience. BMTC is currently fielded the JLCCTC (ERF). Future support required for projected simulation modernization to include: WARSIM-BDE, JLVC/ERF, WIM, Low Overhead Stimulation (LOTS, MCST, ALOTT, ILOD etc.) and OneSAF, or approved emerging systems.

Simulations are available 100% of the time with no more than 2% variance and any system failures are corrected within 1 hour.

operational.

PRS # 13 Train all contract personnel operating MTC simulations capabilities, to include WARSIM, WARSIM- BDE, JLVC, WIM, Low Overhead Stimulation (ALOTT, ILOD, LOTS, SMDS, MSAT,TRADOC G2 Toolkit, etc.), and OneSAF. The contractor shall initiate procedures to ensure that no lapse occurs in its ability to conduct exercises. Continuing education, cross training, and refresher training are required. The Contractor is responsible for training contract personnel who will conduct simulation controller training for all exercises and Mission Rehearsal type exercises.

PRS # 14 Provide training utilizing GFT to meet Unit commander training objectives. Training services will generally be organized and sustained in platoon-size GFT Suites that integrate platform Mission Command systems (FBCB2/BFT) and are networkable between distributed facilities. Support a quantity of four platoon sized GFT Suites for all Gaming uses), and, with the included capability to simultaneously, network multiple-platoons (or Company leader cadres) into full company-level training exercise

the prescribed standards

-Installed and configured ePO servers and supporting databases -Status of Non-PM systems with HBSS framework installed per boundary 100% implementation or mitigations are appropriately documented for HBSS and server STIGs, and applications 100% implemented and functional.

ATTACHMENT 2

The following CDR, DA Form 5479, March 2008 is an Army standardized form. The COR will not customize this form. To include your organizational specific procedures, attach a continuation sheet as necessary. If the non-conforming performance is not corrected in the time frame specified by the NCIR, the COR shall initiate a CDR and forward it to the KO for appropriate action. The COR will contact the KO prior to use of the form.

MTCCS-FTPOLK QASP

ATTACHMENT 3

Quality Assurance Surveillance Log

Data is to be submitted with the monthly COR report.

ATTACHMENT 4

image1.jpeg image2.png image3.png image4.png image5.png