Attachment 3 - RTOP QASP TSS MAIDIQ.docx

Quality Assurance Surveillance Plan

For

U.S. ARMY TRAINING SUPPORT SYSTEM (TSS) SUPPORT CONTRACT

Solicitation No.

W900KK-22-R-0016

15 May 2022

Michael Son Contracting Officer Contracting Officer’s Representative

CUI//SP-SSEL//FED ONLY

CUI//SP-SSEL//FED ONLY

ACC-ORLANDO

Controlled by: U.S. Army Controlled by: ACC-ORL CUI Category: Source Selection Distribution/Limited Dissemination Control: FEDCON POC: PAQA Branch QAS

CUI

CUI//SP-SSEL//FED ONLY

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

14. COR/Quality Assurance Surveillance Files

15. QASP Changes

1. Overview.

1.0 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 task order is to provide Sustainable Range Program (SRP) Support for Training and Doctrine Command (TRADOC) Capability Manager‐ Ranges (TCM Ranges) as defined in this Performance Work Statement (PWS), section 1.3. Government-furnished property and services for those items specified in the PWS are exempt from this QASP. The Contractor shall perform to the standards specified in the MAIDIQ PWS.

This Quality Assurance Surveillance Plan (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.1. 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 FAR 46 are applied as required and applicable

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 analyze user training requirements and provide functional and technical input that relates to Home Station Training Range Modernization Program, Range Operations Program, Range Development Program and the Combat Training Center Range Modernization Program. In addition, support is required in the development and sustainment of program tools for use at Installation, Major Command (MACOM) and Headquarters, Department of the Army (HQDA) for improved efficiency and effectiveness in support of ranges and land management.

2.2. Type of Contract. This will be a Firm Fixed Price (FFP) task order.

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

The Contractor shall provide a TO manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the KO. The TO manager or alternate shall have full authority to act for the Contractor on all TO matters relating to daily operation of this TO. The TO manager or alternate shall be available between 8:00 a.m. and 5:30 p.m. Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. The contractor shall provide Key personnel as list in PWS tasks items 5.1 through 5.2.4 meeting the personal qualification described for each key position of the task order.

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

Government Personnel:

Table 1; Key Positions for Contract Administration

Contracting Officer

COR/ACOR

Contract Administrator

Property Administrator

Contractor Personnel:

Contract Manager

Project Manager

Quality Manager

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

See attachment 6, QASP Surveillance Item Requirements

· Which performance elements will be surveilled (Surveillance Checklist, attachment 4)

· 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 (Surveillance Schedule, attachment 3)

· 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 4, Surveillance Checklist, 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 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.

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

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

5.1.1 Surveillance Procedure:

The COR will perform evaluations/validation of contractor supplied performance data.

1. The COR will review the Contractor supplied weekly reports, that are to include but not limited to a status summary and key milestones and progress for the current period and planned for the next period. These reports will be signed by the COR, verifying review and concurrence with the validity of the information. These reports will be included with the COR monthly report in the Surveillance and Performance Monitoring (SPM) module. (You may even develop a checklist that includes a simple list of items to be included that provides a means of checking the items and signing).

2. The COR will review the contractor supplied reports and validate 100% of the data accuracy supplied within utilizing (work orders/ automated data/approved schedule timeline.

i. I.E. all CAC card requests were completed within the required 8 minutes (this will be verified against the automated tracking system (time in/time out) to verify all customers/CAC cards were issued within 8 minutes)

ii. All work orders were processed within 3 days. The COR would verify this via a random sampling of work orders, WO request date/ WO completion date.

iii. All project deliverable milestone dates met. The COR will verify against the schedule and the deliverables received date.

b. USE OF ACORS – THEIR ROLE IN SURVEILLANCE ACTIVITIES

ACOR DOCUMENTATION REQUIREMENTS

· Reports: Functional Area Reports supporting the Quality Assurance Surveillance Plan consist of immediate impact and monthly status reporting as outlined below.

· Impact Reporting: Government ACORs observing any situation or occurrence which poses a significant program impact will be reported to the COR using the most expeditious manner available. Unacceptable performance or quality of service for requirements specified in the PRS should be documented using the Surveillance Activity Checklist and Nonconformance Report (NCR) immediately provided to the COR for validation and disposition.

· Monthly Status Report: A report will be provided by each ACOR NLT 1 week following each month of the calendar year to the COR. The period of the report is from the first to the last day of that month and should address the contractor’s performance.

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.

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.

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/does not} include a Deduct Plan. {If acquisition does implement a Deduct Plan, explain in detail how deductions will be calculated and applied.}

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.

COR’S Signature Block Date

Contracting Officer’s Signature Block Date

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.

Attachments:

1. Performance Requirements Summary (PRS)

2. Customer Complaint Record

3. Surveillance Schedule

4. Surveillance Checklist

5. Nonconformance Report (NCR)

Attachment 1

Performance Requirements Summary (PRS)

U.S. Army Training Support System (TSS) Support Contract

TSS SUPPORT CONTRACT

Maintain a stable workforce Phase-in Phase-out

1.16 1.22

Safety Requirements

SUSTAINABLE RANGE PROGRAM

SURVEILLANCE

Sustainable Range Program (SRP) Provides for range operations and modernization.

1. Management, coordination and integration of all aspects of internal functions and range staff 5.1

Periodic

Integrated Training Area Management (ITAM):

1. Sustain and maintain the Army’s training lands to meet doctrinal training requirements.

5.20

Contractor performance shall be measured against CLS 304, SSP-A and SSP-B requirements at least once a year to include the following:

100% of ITAM SSPs achieve specified targets Ensure 100% of Command training land objectives are met with no validated negative commander responses received Periodic

2. IMCOM Common Level of Service (CLS) Integrated Training Area Management (ITAM) Support

5.14

IAW IMCOM CLS 304 Training Land Sustainment, SSP A – Provide Management and Oversight of the ITAM Program and Perform Training Requirements Integration (TRI) and SSP B – Manage, Plan, and Execute the Land Rehabilitation and Maintenance (LRAM) Component

Sustainable Range Program (SRP) Geographic Information System (GIS) Support

1. SRP GIS is the SRP foundational support element and provides geospatial data and applications support to the Range Operations, Range Modernization, and ITAM

5.2.11

IAW AR 350-19 sections 1-25 f., 3-3 c., 4-11 a., 4-23 d. (3) (b), 5-2 b., 5-14 c. (4), 6, 8-3, and 8-4.

IAW IMCOM CLS 304 Training Land Sustainment, SSP C – Provide Management, Oversight and Execution of SRP Geographic Information Systems (GIS) Program

IAW AR 350-19 sections 6 and 8- IAW AR 350-19 sections 6 and 8-

Contractor performance under this program will be assessed at least annually at the Program Level. Contractor receives a minimum of 90% Satisfactory Performance Rating (Customer Survey).

Periodic

2. IMCOM Common Level of Service (CLS) SRP GIS Support

5.8.1

IAW AR 350-19 sections 3-3 c., 4-11 a., 4-23 d. (3) (b), 5-14 c. (4), 6, and 8-4.

Contractor performance shall be measured against CLS 304, SSP-C, CL-2 requirements at least once a year to include the following:

100% of (GIS) software and licenses are up to date 100% of (SRP proponent) data is compliant to meet defined standards and submitted to the enterprise database (Army Mapper) 95% of SRP applications are working, accessible, and users trained on (i.e., RMTK (Range Managers Toolkit), ((RFMSS)) Graphic Fire Desk) 75% of requested validated deliverables (form can be maps, documents, data, etc) as required by SRP and data calls are provided on time 75% spatial analysis for SRP range and training land management in a timely manner Contractor performance shall be measured against guidance contained within the SRP Geospatial Data Strategy memorandum and associated PWS requirements at least once a year to include the following:

100% of required SRP geospatial data layers developed, passed QA/QC review, validated/signed by geospatial data layer SME and Garrison Commander or equivalent, and provided to OACSIM Army Mapper as geospatial data of record for each supported installation.

100% of required QA/QC on geospatial data completed and reported in SRP QCP report per the SRP Quality Control Protocol (QCP) and QCP Report template for supported installations.

100% of supported site Military Installation Maps (MIMs) completed in draft format.

Quality Assurance/Quality Control (QA/QC) performed on 100% of installation provided updates to MIMs.

100% of finalized/validated MIMs exported to proper format and delivered to NGA for printing.

100% of draft MIMs posted in .PDF format and 100% of finalized/validated MIMs posted in GeoPDF format to the SRPWeb for distribution.

95% of technical assistance support requested by supported installation successfully completed to customer satisfaction.

100% of HQDA support requested completed to customer satisfaction.

100% of required application/tool tests completed.

IAW IMCOM CLS 304 Training Land Sustainment, SSP C – Provide Management, Oversight and Execution of SRP Geographic Information Systems (GIS) Program, CL-2. 7

Contractor performance shall be measured against guidance contained within the SRP Geospatial Data Strategy memorandum, MIM production guidance documentation posted on SRPWeb, and associated PWS requirements found under Task 1-4B at least once a year to include the following:

Supported installation Military Installation Map(s) (MIMs) developed, updated, and maintained current, passed QA/QC, validated/signed by installation approval authority, posted as final on SRPWeb MIM downloads page in GeoPDF format, and digital files transferred to SRP GIS RSC for export file formats required by NGA for printing and stocking with DLA.

Periodic Customer Complaints

IAW SRP Geospatial Data Strategy Memorandum.

IWA MIM Production Guidance Documentation.

IAW US Army Installation Geospatial Information & Services (IGI&S) Data Proponency, Common Installation Picture, and Quality Assurance Plans Memorandum Contractor performance shall be measured against guidance contained within the SRP Geospatial Data Strategy memorandum and associated geospatial data standards and requirements at least once a year to include the following:

100% of required SRP geospatial data layers developed, passed QA/QC review, validated/signed by geospatial data layer SME and Garrison Commander or equivalent, and provided to OACSIM Army Mapper as geospatial data of record for the installation.

Periodic

COMBAT TRAINING CENTER

SURVEILLANCE

Leader Training Program

Provide the technical support necessary to allow the Combat Training Center to execute LTP training

Exportable Training Center (ETC) Tasks

MISSION COMMAND TRAINING CENTER

SURVEILLANCE

1. Mission Command Training Center Provide technical personnel to provide input for the acquisition, install, operate, integrate, and troubleshoot communications, training and exercise systems in the BCTC.

Contractor performance under this program will be assessed at least annually at the Program Level. Contractor receives a minimum of 90% Satisfactory Performance Rating (Customer Survey).

Periodic

4. Simulation and communication architectures

1. Training support

5.40

3. TSS Warrior Technical Support Provide technical personnel as required in the PWS.

5.31.1

Periodic

4. TSS Warrior Support Program Management Develops and submits all required deliverables 5.31

As detailed in the Base PWS and Individual Task Orders PWS

SOLDIER TRAINING SUPPORT

SURVEILLANCE

1. Soldier Training Support Program Management Develops and submits all required deliverables

1. Virtual & Live Simulations Modernization

TRAINING DEVELOPMENT SUPPORT

SURVEILLANCE

100% Inspection

Training doctrine and documentation Simulation Tool Interface 5.40.4

Vehicle Platform Analysis 5.12

100% Inspection

100% Inspection

100% Inspection

100% Inspection

Attachment 2 Customer Complaint Record

Attachment 3 Surveillance Schedule

The COR will develop a Surveillance Schedule for conducting surveillance. The COR may use the SPM Smart Form or any KO approved schedule.

Attachment 4 Surveillance Checklist(s)

COR SURVEILLANCE CHECKLIST Template

COR Name:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments summary, to include, positive trends, negative trends, concerns, customer comments, and any additional COR comments:

To populate the checklist, find in the PWS: "The Contractor Shall...”, Then, make that requirement a checklist item by converting the requirement to a question: “Did the contractor…" Each "Yes" can be graded as a 1, and each NO graded as a 0. Once the checklist is complete, the COR may generate a quantifiable performance rating using these numbers as metrics.

The COR will develop a Surveillance Checklist for conducting surveillance. The COR may use the SPM Smart Form or any KO approved checklist.

Attachment 5 Nonconformance Report (NCR) image1.emf

ACC_ORL_Customer Compliant Record.pdf

Army Contracting Command Orlando (ACC-ORL)

CUSTOMER COMPLAINT RECORD

DATE OF COMPLAINT TIME OF COMPLAINT

SOURCE OF COMPLAINT

ORGANIZATION (Include name of person and contact information of person reporting the complaint for the organization

INDIVIDUAL (Include name and contact information)

NATURE OF COMPLAINT

CONTRACT NUMBER & REQUIREMENT REFERENCE

VALIDATION (document findings of validation of complaint), Complaint IS Valid (notify contractor)

Complaint IS NOT Valid

DATE / TIME CONTRACTOR INFORMED OF COMPLAINT CONTRACTOR NAME RECEIVING COMPLAINT

ACTION TAKEN BY CONTRACTOR

RECEIVED AND VALIDATED BY

Copy provided for filing (COR) DATE:

Customer Follow-up DATE:

TIME OF COMPLAINT:

NATURE OF COMPLAINT:

CONTRACT NUMBER REQUIREMENT REFERENCE:

VALIDATION document findings of validation of complaint Complaint IS Valid notify contractor Complaint IS NOT Valid:

Complaint IS Valid notify contractor: Off

Complaint IS NOT Valid: Off

DATE TIME CONTRACTOR INFORMED OF COMPLAINT:

CONTRACTOR NAME RECEIVING COMPLAINT:

ACTION TAKEN BY CONTRACTOR:

RECEIVED AND VALIDATED BY:

Copy provided for filing COR DATE Customer Followup DATE:

undefined: Off undefined_2: Off

Date1_af_date:

Organization:

Individual:

Date4_af_date:

Date5_af_date:

image2.emf

COR Surveillance Schedule1.docx

“FOR OFFICIAL USE ONLY”

Contract #:

Contractor:

Functional Area:

Surveillance Period:

COR:

Date Submitted:

Date for

Surveillance

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

(Req Ref)

Instructions for Completing the

The surveillance schedule form shall be completed prior to the beginning of each month to identify when and where surveillance will be conducted throughout the month. If changes to the schedule occur during the month, the Contracting Officer Representative (COR) will line through the activity, annotate the reason for the change, indicate the revised date and annotate at the new date when the activity is to be conducted. Completed schedules shall be maintained as part of surveillance documentation in the COR contract files.

BLOCK 1: Enter contract number.

BLOCK 2: Enter contract title.

BLOCK 3: Identify the functional area or contract section to be surveilled.

BLOCK 4: Indicate performance period - month and year surveillance is to be accomplished.

BLOCK 5: Enter name of COR responsible for surveillance.

BLOCK 6: Indicate the date the schedule was prepared and submitted (Must be prior to start of surveillance period).

BLOCK 7: Indicate days of the month when surveillance will be performed (i.e. 1 thru 30).

BLOCKs 8(a) through 8(k) indicate the contract PWS paragraph and the PRS number. If all characteristics for a PWS Paragraph are to be surveilled on the same date, you do not need to enter the individual PRS numbers in the schedule.

image3.emf

Surveillance Checklist.xlsx Surv ChkList

ACC-ORL COR SURVEILLANCE CHECKLIST Template

COR Inspection Checklist & Data Report (Fixed Firm Price Contract) Period Of Performance:

Contractor: From:

Contract Number: To:

Service Provided: Meeting Contract Requirements ?

COR Name:

Date:

Select answer in cloumn C or D YES No

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comme…