QASP_USARNORTH_CSTA_CBRN_Training.pdf

Quality Assurance Surveillance Plan (QASP)

For

United States (US) Army North (ARNORTH) Civil Support Training Activity (CSTA)

Chemical, Biological, Radiological, and Nuclear (CBRN) Training, Planning, Evaluation, and Validation

Exercise Support Services

4/11/2022 v1.0

Caffee Odermann Contracting Officer’s Representative

PL TSO, PEO STRI

PHILLIP B. DAVIS

Contracting Officer ACC-Orlando

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. Contractor Manpower Reporting Application (CMRA)

12. Contractor Performance Assessment Reporting System (CPARS)

13. Combating Trafficking In Persons

14. COR/Quality Assurance Surveillance Files

15. Government Furnished Property Surveillance Requirements……………...14

16. QASP Changes

17. Attachments ......................................................................................................... 15 - 24

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 effort under a Full and Open type C Contract is as defined in paragraph 5, Specific Tasks, of the Performance Work Statement (PWS). 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 PWS. The objective of this effort under a Full and Open type C Contract is to provide effective Chemical, Biological, Radiological, and Nuclear (CBRN) response specific collective training, planning, evaluation, and validation exercise support services.

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 assist the U.S. Army North (USARNORTH) Civilian Support Training Activity (CSTA) mobile Observer Controller/Trainer (OC/T) teams in the planning, preparation and execution of CBRN training.

2.2. Type of Contract. This will be FFP and Cost type CLINs on a full and open type C 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.

Assigned PCO/KO: Phil Davis Organization or Agency: Army Contracting Command (ACC)-Orlando

(407) 384-5335, DSN 970-5335

phillip.b.davis16.civ@army.mil

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

Caffee Odermann Contracting Officer’s Representative (COR) PdL TKTS, PL TSO, PEO STRI caffee.l.odermann.civ@army.mil 407-208-3060

3.1.3. Contract Administrator. N/A

3.1.4. Property Administrator. N/A

3.2. Contractor.

3.2.1. Contract Manager.

Name, Company Name, Company Address/phone/email TBD

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

Name, Company Name, Company Address/phone/email TBD

3.2.3. Quality Manager. The Program Manager also serves as the Quality Manager for this effort.

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 Phil Davis

407-384-5335 phillip.b.davis16.civ@army.mil

Contract Specialist

Willie Bass

321-235-7649 willie.c.bass2.civ@army.mil

COR Caffee Odermann

407-208-3060 caffee.l.odermann.civ@army.mil

Contractor Personnel:

Title Name Phone e-mail Contract Manager TBD

Project Manager/ Quality Manager

TBD

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:

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

o Ensure the method of assessing contractor performance against performance standards is included in this QASP o Ensure each Performance Requirement includes an acceptable quality limit (AQL). AQL is the worst tolerable performance that is still considered acceptable.

• When the surveillance will be scheduled (Surveillance Schedule, attachment 3) o 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.

• Which performance elements will be surveilled (Surveillance Checklist, attachment 4) o 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. The monthly checklist that the COR will be using is a Monthly Technical Oversight Representative (TOR) report. Attachment 4 is an example of one of these reports.

• The Acceptable Quality Limit (AQL) o 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) o 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. The monthly checklist that the COR will be using is a Monthly Technical Oversight Representative (TOR) report. Attachment 4 is an example of one of these reports

5. Government Surveillance.

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

• 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

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.

• 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. Random monitoring shall be conducted if and when deemed necessary by the PCO or TO COR. The random monitoring shall be performed by the PCO, appropriate designated TO COR, or designated TOR. Performance Requirements Summary (PRS) (Appendix 1) may be used for random monitoring. The COR will input these random reports to “COR Documents,” “Add Smart Form,” “Surveillance Schedule” (see screen shot below) in the Surveillance and Performance Monitoring (SPM) Module, Procurement Integrated Enterprise Environment (PIEE) application.

• 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. This level of inspection shall be accomplished by monitoring and documentation. Government Technical Oversight Representatives (TOR), normally located at the place of contractor work performance, will provide monthly TOR reports to the COR. These reports evaluate the contractor’s work performance for the training requirements articulated in the PWS. The monthly TOR reports will be uploaded by the COR as attachments in the “COR Documents” Smart Form “COR Status Report” in the Surveillance and Performance Monitoring (SPM) Module, Procurement Integrated Enterprise Environment (PIEE) application. The Surveillance Schedules for the monthly TOR reports (Attachment 4) are uploaded to “COR Documents,” “Add Documents.”

• 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 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 an analysis of Customer feedback and the contractor’s actions to identify performance trends and to ensure valid customer concerns are resolved in a timely manner.

• The COR will review monthly Technical Oversight Representative (TOR) reports, if any negative trends are identified the COR will follow up with the contractor. These reports are due on the 5th of the month following the month of contractor work performance.

• These TOR reports will be signed by the COR, verifying review and concurrence with the validity of the information, and will be included with the COR monthly report in the Surveillance and Performance Monitoring (SPM) module.

USE OF TECHNICAL OVERSIGHT REPRESENTATIVES (TOR) – THEIR

ROLE IN SURVEILLANCE ACTIVITIES

TOR 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 TORs 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 Contract Discrepancy Report (CDR) immediately provided to the COR for validation and disposition.

• Monthly Status Report: A Monthly Technical Oversight Representative (TOR) report will be provided to the COR NLT the 5th day of the month following the month of contractor work 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 base or option year during the Period of Performance (PoP) to schedule surveillance activity for the upcoming months. 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) Smart Form 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. All months of 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 Contractor Nonconformance Report (CNR), 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 (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 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 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.

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

6.4. Documenting CNRs. The COR will provide the details of the non-conformance using the CNR, Attachment 5. 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; 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. N/A.

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. 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, CNRs 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 CNRs, if any, will be included as attachments to COR Status Reports. See para 5.4.

11. Contractor Manpower Reporting Application (CMRA). Reporting Labor Hours.

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report all Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address: https://www.ecmra.mil.

The required information includes the following:

a. Contracting Officer (KO), Contracting Officer’s Representative (COR) name;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data;

e. Estimated direct labor hours (including sub-Contractors);

f. Estimated direct labor dollars paid this reporting period (including sub-Contractors);

g. Total payments (including sub-Contractors);

h. Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different);

i. Estimated data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information);

k. Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment or contingency contract language; and Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country).

While inputs may be reported any time during the FY, The COR shall ensure the contractor submits all data no later than October 31 of each calendar year. The COR shall verify that the Contactor has complied with the required contractor manpower reporting annually and document the results in the CORs’ Online Surveillance and Performance Monitoring (SPM) module, CMRA section. 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. Government Furnished Property (GFP). This acquisition does include GFP.

CORs will report surveillance outcomes IAW the Frequency column on Table 3 using the COR Status Report (CSR) 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.

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

Table 2: 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.

Version

Effective Date

Originator Summary of Changes

1.0 11 Apr 2023 Robert Woolverton Initial Draft

Tables:

1. Key Positions for Contract Administration

2. Document Revision History

3. Government Furnished Property Surveillance Requirements

Attachments:

1. Performance Requirements Summary (PRS)

2. Customer Complaint Record DA 5477 (Optional)

3. Surveillance Schedule DA Form 5475

4. Sample Surveillance Checklist – Monthly TOR Report

5. Contractor Nonconformance Report (CNR) DA Form 5479

Table 3

Government Furnished Property (GFP) Surveillance Requirements

Attachment 1

Contract/Task Order Performance Requirements Summary

(PRS)

PERFORMANCE OBJECTIVE

(PO)

STANDARD

(Evaluation standards based on results of training phases in PO)

PERFORMANCE

THRESHOLD

ACCEPTABLE

QUALITY

LEVELS (AQLs)

METHOD OF

SURVEILLANCE

PRS#1 - PWS para (5.2 & 5.2.1) a) Standard:

Contractor shall train

a) 100% Compliance

Periodic Inspection

Surveillance Method/By Whom Frequency Comments COR/ACORs As required COR will ensure the Contractor is provided GFP identified on the GFP Attachment.

COR/ACORs As required

COR will alert the Contracting Officer of delays of GFP provided to the Contractor. If GFP related issues may impact Contractor performance or delivery schedule.

COR/ACORs As required

COR validates Contractor Property Management System (PMS) within 30-60 days of the contract award

COR/ACORs As required

COR reviews monthly purchases of Contract Acquired Property (CAP).

COR/ACORs Annually COR will ensure Contractor conducts physical inventory.

COR/ACORs Quarterly COR validates that consumption reports for materials are being submitted IAW the

CDRL/PWS

COR/ACORs As required

COR will ensure the Contractor uses the PIEE GFP Module to report receipt, transfer, report loss, theft, or damage of GFP/CAP during contract performance.

COR/ACORs As required

COR will ensure the Contractor uses PIEE GFP Module for Plant Clearance/disposal of GFP/CAP during the period of performance.

The contractor shall assist military and government service personnel in the design, planning, coordination, synchronization, preparation, and execution of the WMD CST training/exercise event.

and evaluate CSTs IAW the T&EOs in Exhibit C..

b) Standard: Unit demonstrates proficiency IAW current T&EO.

c) Standard: Oral and written feedback daily after performance during Hot-wash, Informal AAR, during Out-briefs at the conclusion of training, and through input to formal training evaluation reports.

Zero Deviation from standard.

b) 80% of units demonstrate task proficiency during evaluations with a (T).

c) 100% Compliance

Periodic Inspection

PRS#2 - PWS para (5.2 & 5.2.2)

The contractor shall assist military and government service personnel in the design, planning, coordination, synchronization, preparation, and execution of the HRF/CERFP training/exercise event.

a) Standard:

Contractor shall train and evaluate HRFs & CERPs IAW the T&EOs in Exhibit C.

b) Standard: Unit demonstrates proficiency IAW current T&EO.

c) Standard: Oral and written feedback daily assessing unit performance (Hot-wash, Informal AAR, Out- brief).

a) 100% Compliance

b) 60% of units proficiency during evaluations with a (T) minus) or better.

c) 90% accuracy with identifying unit strengths and weaknesses

PRS#3 - PWS para ( 5.2 & 5.2.3-

5.2.5 )

a) Standard:

Contractor shall provide training and evaluation of DCRF &

a) 100% Compliance Zero Deviation from standard.

The contractor shall assist military and government service personnel in the design, planning, coordination, synchronization, preparation, and execution of the DCRF &

C2CRE TSF MCD & RECON

training/exercise event.

C2CRE TSF

MCD/RECON events IAW the MCD & RECON T&EOs in Exhibit C.

b) Standard: Unit demonstrates proficiency IAW current T&EO.

c) Standard: Oral and written feedback daily assessing unit performance (Hot-wash, Informal AAR, Out- brief).

proficiency during evaluations with a (T) minus) or better.

c) 90% accuracy with identifying unit strengths and weaknesses

PRS#4 - PWS para (5.2 & 5.2.6.)

The contractor shall assist military and government service personnel in the design, planning, coordination, synchronization, preparation, and execution of the US&R training/exercise events.

a) Standard:

Contractor shall provide training and evaluation of US&R events IAW the US&R T&EOs in Exhibit C.

b) Standard: Unit demonstrates proficiency IAW current T&EO.

c) Standard: Oral and written feedback daily assessing unit performance (Hot-wash, Informal AAR, Out- brief).

d) The contractor shall have a minimum of one (1) search & rescue SUBJECT

MATTER EXPERTISE

for every six (6) Soldiers involved in

a) 100% Compliance proficiency during evaluations with a (T) minus) or better.

c) 90% accuracy with identifying unit strengths and weaknesses

d) 100% Compliance Zero Deviation from standard.

100% Inspection the US&R training IAW FEMA standards.

PRS#5 - PWS para (5.2 & 5.2.9.1.) Contractor shall perform roles and responsibilities as an Incident Management Team in support of MCD, R&S, US&R, and CST training and evaluations, when requested.

Role players range from one

(1) to three (3) depending on the level of the exercise.

a) Standard: Develops an Incident Action Plan (IAP) and map of area of operation.

b) Standard: Issues guidance and direction for supporting units to accomplish assignments.

c) Standard:

Documentation is accurate and complete.

d) Standard: The contractor shall have operational knowledge and use of the ICS, knowledge of 29 CFR

1910.120 paragraph Q and other current OSHA standards for industry. The contractor role plays various positions that are key for the military to interface with as if they were supporting first responders on an actual incident. The foundation and doctrine for this is established under the FEMA ICS curriculum and the National Incident Management System (NIMS).

e) Standard: Ensures props for collapsed structures, trench operations, vehicle a-c) 98% accuracy with IAP products;

d) 90% accuracy with ICS command post setup W/FEMA ICS curriculum and NIMS.

a-c) Periodic extraction, machinery extraction, confined space and rope rescue are safe to operate in.

e) 100% accuracy with urban search and rescue operational props

PRS #6 - Service Contract Reporting (SCR) PWS 5.3 and CLIN XXXX

The Contractor shall completely fill in all the information in the format using the following web address www.sam.gov The contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement.

Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. If contract period of performance ends prior to September 30, the contractor has 30 days from end date of the contract to complete the SCR requirement.

Zero Deviation from Standard

100% Inspection

Attachment 2 Customer Complaint Form

DA FORM

5477_Customer Com

Attachment 3 Surveillance Schedule

Surveillance Schedule

“FOR OFFICIAL USE ONLY”

Contract #:

TBD

Contractor:

TBD

Functional Area:

ARNORTH CSTA, Chemical, Biological, Radiological and Nuclear (CBRN) Response Enterprise (CRE) Response Training

Surveillance Period:

TBD

COR/QAE:

Robert A. Woolverton

Date Submitted:

TBD

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)

TBD TBD

Instructions for Completing the Surveillance Schedule

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 COR/TM 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 QAE or Technical Monitor (TM) responsible for surveillance and QAE signature.

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 KPI number from the Surveillance Process Record. If all characteristics for a PWS Paragraph are to be surveilled on the same date, you do not need to enter the individual KPI numbers in the schedule.

NOTE 1: In the Matrix blocks, identify the PWS/Characteristic number(s) for surveillance performed corresponding to each respective date.

NOTE 2: The Document Control Date indicates the revision date for the data contained in Blocks 1 thru 6 of this document. This date is located at the top of the page directly below the title and form number.

If utilized, you will need to develop a monthly schedule for conducting surveillance. The date you are going to conduct surveillance would go in the far left column. You would list the PWS, paragraph number for the task you are going to surveil on the top line.

5475_Surveillance Se

Attachment 4 Sample Surveillance Checklist – Monthly TOR Report

Performance Quality Rating Guidance

Attachment 5 Contractor Nonconformance Report

5479_Contractor No