ATT_2_W912CM25QA012_QASP_19May25.docx

Quality Assurance Surveillance Plan

For

Customer Service Support

Contract # - TBD

19 May 2025

409th CSB QASP Template Version: 20240229

TABLE OF CONTENTS

Subject Page Number

1.0 Overview 3

2.0 Description of Services 4

3.0 Roles and Responsibilities 4

4.0 Contract Quality Requirements 5

5.0 Government Surveillance 6

6.0 Non-Conforming Performance 8

7.0 Data Analysis 9

8.0 Acceptance of Services 10

9.0 COR Monthly Status Report (MSR) 10

10.0 Service Contract Reporting (SCR): 10

11.0 Contractor Performance Assessment Reporting System (CPARS) 10

12.0 Combating Trafficking In Persons (CTIP) 10

13.0 COR/Quality Assurance Surveillance Files 11

14.0 QASP Changes 11

15.0 Attachments 12

1.0 Overview.

1.1 Purpose. The purpose of this Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures the Government will use to ensure it receives the services under this contract as identified in the Performance Work Statement (PWS). This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. This QASP explains the following:

· What will be monitored?

· How monitoring will take place.

· Who will conduct the monitoring?

· How monitoring efforts and results will be documented.

· When and how often monitoring will take place.

This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. The QASP should recognize that unforeseen and uncontrollable situations may occur.

The contractor is responsible for implementing and delivering performance that meets contract standards using its Quality Control Plan. The QASP provides the structure for the government’s surveillance of the contractor’s performance to assure that it meets contract standards. It is the government’s responsibility to be objective, fair and consistent in evaluating contractor performance.

The QASP is not part of the contract nor is it intended to duplicate the contractor’s quality control plan. This QASP is a living document. Flexibility in the QASP is required to allow for an increase or decrease in the level of surveillance necessary based on contractor performance.

Bottom line, the QASP should ensure early identification and resolution of performance issues to minimize impact on mission performance.

1.2 Intent. The intent of this QASP is to: 1) ensure Contractor performance meets or exceeds contract terms, conditions and specifications; 2) hold the Contractor accountable for quality control; and 3) encourage the Contractor to take appropriate steps to control and improve quality. 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 times necessary, and at all places necessary to ensure that the rendered services conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level and perform quality assurance at the contractor's place of business, if applicable. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor.

1.3 Authority. Authority for issuance of this QASP is provided under Part 46 of the Federal Acquisition Regulation, Inspection of Services clauses, which provides for inspection, acceptance, and documentation of the service called for in the Task Order or contract. This acceptance is to be executed by the contracting officer or a duly authorized representative.

2.0 Description of Services

2.1 Scope of Work. The Contractor shall provide non-personal services to support customer service program management. The Contractor shall promote and coordinate the full range of responsibilities of the Customer Service Program including Interactive Customer Evaluation (ICE) program, customer service training, Surveys, Commander’s Hotline, the Workforce Engagement Award Program with customer service and team awards and other garrison award programs. Standardize Garrison’s front door service office appearance. The Contractor shall provide information about community feedback mechanisms to military personnel and their families, civilians, Contractors, and retirees who reside within the USAG-Wiesbaden footprint; identify issues encountered by the serviced population and provide feedback to implement policies and procedures that demonstrate sensitivity to the changing needs of individuals and families; coordinate with the PAIO staff and other agencies and personnel; and prepare associated briefings and reports.

2.2 Type of Contract. Firm Fixed Price

3.0 Roles and Responsibilities.

3.1 Government.

3.1.1 Contracting Officer (KO). The KO is the only person with the authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

Assigned KO: J.C. Paitson Organization or Agency: 409th CSB Telephone: 758-2778 Email: john.c.paitson.civ@army.mil

3.1.2 Contracting Officer’s Representative (COR). The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists 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 aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and reporting early identification of performance problems to the Contracting Officer and Contractor; coordinate availability of Government furnished property, and provide site entry of Contractor personnel. The COR shall keep a surveillance file in Procurement Integrated Enterprise Environment – Surveillance and Performance Monitoring Application (PIEE-SPM) that accurately documents the contractor’s performance. The COR is required to provide monthly performance assessments to the KO by uploading in PIEE-SPM. 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 or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

4.0 Contract Quality Requirements.

4.1 Contractor’s Quality Control Program. The Contractor’s quality control program (IAW FAR Part 46 and applicable 52.246-(Clause(s))) is the means by which the Contractor assures that work complies with the requirement of the contract. The Contractor shall ensure services are performed in accordance with this PWS. The Contractor shall identify, prevent, and ensure non-recurrence of defective services.

4.2 Government Quality Assurance. The Government shall evaluate the Contractor’s performance under this contract in accordance with this QASP. This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance and minimum acceptable defect rate(s).

5.0 Government Surveillance. The Government has the right to inspect all contract deliverables at any time before acceptance. Inspections can be announced or unannounced, but they must not unduly delay work, and they must not include directions that would change the contract. The Government also has the right to reject a deliverable that does not meet contract requirements. For acquisitions of commercial items, FAR Subpart 46.202-1 requires the Government to rely on contractors’ quality assurance systems as a substitute for Government inspection and testing before the items are tendered for acceptance (unless customary practices for the supplies being acquired include in-process inspection). Any in-process inspection by the Government must be consistent with commercial practices. For services, the COR can monitor contractor performance by using a variety of inspection methods. Before an inspection, the COR should check the contract for specific inspection and testing requirements. The COR should use a systematic approach and should ensure that the inspection methods do not interfere with the contractor’s progress or at least disrupt that progress only when absolutely necessary and as minimally as possible.

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

5.1.1 100% Inspection. With this method, performance is inspected/evaluated at each occurrence. This method is often costly (both time and money) but can be necessary due to health, safety and other considerations.

5.1.2 Random Sampling. Random sampling works best when the number of instances of the services being performed is very large and a statistically valid sample can be obtained. RESERVED

5.1.3 Periodic Inspection. This method, sometimes called “planned sampling," consists planned sampling at specific dates or time intervals. It may be appropriate for tasks that occur infrequently, and where 100 percent inspection or random testing is not desired. RESERVED

5.1.4 Customer Feedback/Input (Complaints). Although usually not a primary method, this is a valuable supplement to more systematic methods. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations where customers can be relied upon to consistently provide feedback regarding the quality of performance, e.g., dining facilities, building services, customer surveys and customer complaints may be a primary surveillance method, and customer satisfaction an appropriate performance standard. RESERVED

In all cases, complaints will be documented. The following procedures will be followed when a complaint is received: The COR will document customer complaints of unsatisfactory performance, the validity of the complaint, time and date the responsible official was notified, and the actions taken to correct the problem. Customer complaints shall be handled in the following manner: When a complaint is received, COR personnel will complete appropriate documentation to record the complaint. The COR shall investigate the complaint to determine contract non-conformance. If after investigation the COR determines the complaint as valid, the COR will inform the Contractor’s Quality Manager. If the COR determines the complaint as invalid, the COR shall document their findings and notify the complainant. COR personnel will retain the annotated copy of the written complaint for their file. All customer complaints received, valid and invalid, will be documented.

5.2 Performance Requirements Summary (PRS). The Performance Requirements Summary (PRS) (Attachment 15.1) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR PIEE-SPM File. The key elements of this process are PWS tasks risk rated as high or moderate, and included in the Performance Requirements Summary (PRS) which provides the performance objective, performance standard, performance threshold and method of surveillance. The COR will perform surveillance and inspect the compliance of PWS tasks on a monthly basis. Although the PRS contains only those items considered most important for mission accomplishment, the government retains the right to inspect all requirements of the contract. The COR may choose to periodically inspect requirements not listed on the PRS. Non-conformance with any contract requirement, whether specifically addressed in the PRS or not, is still non-conformance (See Para 6.0 Non-Conforming Performance& Corrective Action Request (CAR). The intent of the surveillance approach is to gain confidence in the contractor's way of doing business and then adjusting the level of oversight to a point that maintains that confidence. With this intent, the surveillance approach may not be one that stays the same throughout the duration of the contract. All Government evaluators should be prepared to periodically update the surveillance approach as required.

Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance. The Government performs surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The PRS should be used to form the foundation of the COR’s surveillance checklist(s) (see attachment 15.5).

5.3 Surveillance Schedule. The COR shall complete a COR Monthly Surveillance Schedule on a monthly basis. The completed COR Monthly Surveillance Schedule form shall be uploaded into PIEE-SPM in the Surveillance Documents section as a Surveillance Schedule. The COR Monthly Surveillance Schedule ensures the KO that the COR has scheduled and documented the specific dates and times contractor surveillance was performed. Sample COR Surveillance Schedule, Attachment 15.2.

5.4 Performance Rating Definitions. In evaluating the quality of contractor’s performance, the following performance ratings IAW FAR 42.1503, Table 42-1will be used.

6.0 Non-Conforming Performance & Corrective Action Request (CAR). CARs are used in evaluating the contractor’s corrective action and determining if an appropriate root cause has been assigned and effective timely corrective action has been taken by the contractor to prevent or reduce recurrence in the same or other similar services or products and to assure that adequate remedial action has been taken to remove existing faults. There are four Levels of CARs which are used and issued to the contractor. CARs must be submitted to the contractor in a timely manner after non-conforming performance has been identified. If the number of non-conformances/discrepancies exceeds the performance threshold for any item in the PRS, approved Government representatives will determine the possible cause of this unacceptable performance. Government-caused defects/discrepancies shall not be counted against the contractor. The same applies to any other requirement of the contract when Government-caused defects/discrepancies are the cause of unacceptable contractor performance. If the contractor’s performance is judged unacceptable on the PRS items or any other requirement of the contract by the appointed COR, they will inform the contractor’s on-site representative. If the contractor disputes the results of surveillance, the COR will refer the contractor to the KO for resolution. The COR shall notify the KO for appropriate action in accordance with FAR 52.212.4, or the appropriate inspection of services clause.

6.1. Level I - A Level I CAR describes a deficiency on a product or service and is not a systemic breakdown of a process or system. It includes those nonconformances that are minor in nature and can be promptly corrected by the contractor, present no need for root cause analysis, no determination if other contract requirements are affected, present no need for further preventive action, and do not materially reduce the usability of the supplies, services, construction, or deliverables. While the Government must document the nonconformance and the contractor must correct the nonconformance, further actions and Government follow-up are not required, and no written response from the contractor is needed. Level I CARs are considered closed immediately upon issuance.

6.2. Level II - A Level II CAR describes deficiencies in a contractor’s processes or systems but are not a significant deficiency. Some examples of systems affected may be quality inspection / management systems, and CBS identified in DFARS 242.70, or issues such as:

· Multiple deficiencies on products or services indicating a systemic issue throughout the process, or

· An escalation of repetitive Level I CARs for the same or similar nonconformance demonstrating the contractor is failing to institute effective corrective action and/or failing to implement effective quality and/or internal control(s).

· Level II CARs shall require the contractor to correct the nonconformance, perform root cause, and develop and provide a corrective action plan (CAP) acceptable by the government.

6.3 Level III - Level III – A Level III CAR describes deficiencies in a contractor’s system that is affecting a contract or program ability to meet cost, schedule, or performance requirements, or are:

· A significant deficiency pursuant to DFARS 252.242-7005, “Contractor Business Systems” (CBS) or

· A failure to respond to Level II CARs, or to remedy a recurring nonconformance.

· If not resolved satisfactorily, a Level III CAR may result in the initiation of available contractual remedies, such as reductions of payments, cost disallowances, revocation of government assumption of risk of loss, or business management system disapprovals, etc.

· Contractor shall be required to provide a CAP that is acceptable by the government.

6.4 Level IV - A Level IV CAR documents a critical nonconformance of such serious nature that is issued to the contractor’s business segment or corporate management for their attention to both the nonconforming condition and the company’s corrective action, or when a Level III CAR has been ineffective. A Level IV CAR will result in a mandatory review of available contractual remedies, such as cost disallowance, reduction or suspension of payments, revocation of government assumption of risk of loss, CBS disapproval, or suspension of all product and service acceptance activities. Contractual remedies will be implemented IAW applicable FAR/DFARS clauses and/or ACC Acquisition Instructions if applicable. Action to suspend product or service acceptance will be accomplished via a Level IV CAR. Contractor shall be required to provide a CAP that is acceptable to the government.

6.5 CAR System of Record (SOR)

· SOR. The PDREP CAR Module is the SOR for CAR’s processed and issued on ACC administered contracts. The CAR Module is one of the applications housed in the Product Data Reporting and Evaluation Program (PDREP) Automated Information System (AIS) located on-line at: https://www.pdrep.csd.disa.mil/default.htm .

· Access. For access to this system, go to the PDREP website and click on the “REQUEST ACCESS” button and follow the directions for “US Government Access”. The website also includes user guides and manuals under the “REFERENCES” button. Review the “DoD Corrective Action Request” Manual for guidance on access and how to use this PDREP-AIS. Accessing the CAR Module will be enabled through PIEE in early calendar year 2024. To access through PIEE, add the appropriate role following the PIEE process. After the PIEE single sign on is enabled, the SOR may be accessed either through PIEE or PDREP.

· User Roles. Refer to Table 1.1 of the DoD CAR Manual or Table 8.1 of this acquisition instruction for a description of the functions available to each role. NOTE: ensure COR’s register as a Functional Specialist under the contracting office DoDAAC they will support.

· Proprietary Information. Do not include any proprietary information as part of the CAR in the SOR. It should normally be included only by reference (cite specific document and identifying paragraph number). Consult with your supporting legal office when determining if information is suspected to be proprietary.

· Classified information. Classified information will not be entered into the CAR module.

6.6 Documenting CARs. CORs will initiate the CAR process using PDREP. The CAR will specify if the contractor is required to conduct and prepare a root cause analysis and corrective action plan to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The CAR will also state how long after receipt the contractor must present this corrective action plan. The Government will review the contractor's corrective action plan to determine acceptability.

Once the contractors Quality Manager or representative has issued a corrective action plan for the CAR the Government will review, and determination of the need for further correction action. PDREP will notify the contractor representative of the determination within 5 (five) business days. CARs will be accumulated and analyzed by the KO, COR and QAS to determine when further corrective action is needed. Further corrective action requests will be documented and submitted to the KO for coordination with the contractor.

7.0 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 the COR Monthly Status Report(s) and may be used to make adjustments to surveillance schedules, increase or decrease surveillance, if deemed appropriate. Negative trends noted using Government data/observations could result in issuing the Contractor a Non-Conformance Report (Refer to Para 6.0 Non-Conforming Performance & Non-Conformance Report (CAR)). Trends noted using Contractor data will not result in a CAR unless the Contractor is not addressing the negative trend.

8.0 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 of the Contractor. This is accomplished by approving the Contractor’s Receiving Reports in PIEE - Wide Area Work Flow, https://wawf.eb.mil/.

9.0 COR Monthly Status Report (MSR). No later than the 15th of the month, the COR will document the contractor’s performance by completing a Monthly Status Report (MSR) in PIEE-SPM for the previous month’s surveillance. MSRs will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis will contain a summary of: surveillances performed; Customer Feedback, if any; CARs, if any; an analysis of the Contractors performance; recommended adjustments to surveillance schedules; and any other pertinent contract information. The Monthly Status Report will not be considered finalized until reviewed and approved by the contracting officer.

10.0 Service Contract Reporting (SCR): The Contractor is required to completely fill in all required data fields using the following web address: http://www.sam.gov. Reporting inputs will be for the labor executed during the period of performance during each Government FY, which runs from October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. If contract period of performance ends prior to September 30, the Contractor has 30 calendar days from end date of the contract to complete the SCR requirement (DELIVERABLE xxxx). The contractor shall completely fill in all required data fields. The contractor shall enter initial data into the appropriate SCR tool to establish the basic contract record no later than 15 working days after receipt of contract award or contract modification incorporating this clause. The contractor shall notify the COR when the basic contract record has been established in the appropriate SCR tool. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

11.0 Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (COR MSRs, Completed Surveillance Checklists, Customer Feedback and CARs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information. The COR shall document that CPARS, if required, was completed in PIEE-SPM.

12.0 Combating Trafficking In Persons (CTIP). If CTIP is checked "Yes" on the COR Appointment Letter, the COR shall perform the following:

Read and understand the CTIP FAR clause 52.222-50 in the basic contract or at http://farsite.hill.af.mil/ and describe how you will monitor the contractor's performance regarding trafficking in persons (CTIP). For FAR 52.222-50 (February 2009), verify paragraph (c) and (f) of the clause are being complied with. For FAR 52.222-50 (March 2015), verify paragraph (c), (h), and (i) are being complied with. Document surveillance results on the MSR and the COR CTIP Checklist, Attachment 15.4. Bring any potential issue in this area to the immediate attention of the KO before engaging the contractor in reference to these activities. Document any validated non-compliance on a CAR IAW paragraphs 6.0 of this QASP.

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.

13.0 COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance File will be maintained in PIEE-SPM, IAW DoDI 5000.72, DoD Standard for COR Certification. At a minimum, the CORs PIEE-SPM file(s) contents will include:

A current QASP COR appointment letter (if originally appointed outside of PIEE) Evidence of Monthly Surveillance Documentation Evidence of Funds/Expenditure tracker (If other than Firm Fixed Price Contract) Correspondence pertaining to cost, schedule, and performance.

CAR’s (if applicable) Evidence of required documentation IAW PWS (CDRLs) (Refer to Attachment 15.3) Evidence of SCR data validation Evidence of CPARS data validation (if applicable) Evidence of Quality Assurance Surveillance Schedule (QASS) for each month

All such records will be retained for the life of this contract.

14.0 QASP Changes. 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 QAS for approval and the QAS must approve all changes.

15.0 Attachments.

15.1 Performance Requirements Summary (PRS)

15.2 Sample Surveillance Schedule

15.3 Deliverables Table (CDRLs)

15.4 CTIP Checklist

15.5 Surveillance Checklist

Attachment 15.1

Requirements Table

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Requirements Summary (PRS)

PRS #1 – Basic Services

PWS 5.1.1

PRS#2 - PWS para (5.2.1 Voice of the Customer)

Contractor shall provide support for the Interactive Customer Evaluation (ICE) program and “Commander’s Hotline” in accordance with the USAG Wiesbaden Voice of the Customer SOP.

PRS#3 - PWS para (5.2.2 Customer Service Area Standardization)

The Contractor shall perform tasks in accordance with Enclosure 1 of the IMCOM Policy Memorandum 5-2 “IMCOM Service Culture Initiative”

PRS#4 - PWS para (5.2.3 Awards)

The Contractor shall provide support for the USAG Wiesbaden Award program in accordance with IMCOM Policy Memorandum 5-2 “IMCOM Service Culture Initiative” Enclosure 3, IMCOM Regulation 672-10, AER 690-672, Army in Europe Pamphlet 672.20, USAG Wiesbaden Workforce Engagement Award SOP and Customer Service SOP.

PRS#5 - PWS para (5.2.4 Process Improvement)

The Contractor shall review processes and suggest process improvements within garrison directorates to increase efficiency and effectiveness by incorporating the ‘Voice of the Customer’. These suggestions are based on analysis of VOC data and include an assessment of each respective directorate’s operating procedures and applicable regulations.

PRS#6 - PWS para (5.2.6 Program and Project Supplies)

The Contractor shall conduct twice a year May/June and November/December) an inventory on supplies required to support programs and projects related to this PWS and submit supply order requests to the COR.

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

Attachment 15.2

Sample Quality Assurance Surveillance Schedule (QASS)

Surveillance Schedule

“FOR OFFICIAL USE ONLY” (When Completed )

5) COR: Iris Hoehenberger

7) Planned Date for Surveillance

15 Aug 25

X

22 Aug 25

29 Aug 25

X

Attachment 15.3

DELIVERABLES TABLE (CDRLS)

COR

COR

COR

8) Favorable background checks

(PWS 1.6.4.1)

9) Unfavorable background checks

(PWS 1.6.4.1)

10) Police Good Conduct Certificate (1.6.4.2)

15) OCI Mitigation Plan (PWS 1.19)

16) AT Level 1 Training Certificate

(PWS 1.23.1)

17) OPSEC Training Certificate

(PWS 1.23.2)

18) iWATCH Training Certificate

(PWS 1.23.3)

19) IA Training Certificate (PWS 1.23.4.1)

20) ATCTS

Registration (PWS 1.23.4.3)

21) PII Training Certificate (PWS 1.23.5)

22) ICE update by 3rd week of month (PWS 5.2.1.3)

23) Monthly ICE Report (PWS 5.2.1.3)

26) Initial ICE Marketing Plan

(PWS 5.2.1.4)

27) ICE Marketing Plan Revisions

(PWS 5.2.1.4.1)

ICE Marketing Plan, annual. Once per year, due 31 December.

31) Monthly Customer Service Awards

(PWS 5.2.3.1)

32) Quarterly Workforce Engagement Awards

(PWS 5.2.3.2)

33) Award Presentation Events and Documentation

(PWS 5.2.3.3)

34) Process Improvement Progress

(PWS 5.2.4.1)

35) Surveys (PWS 5.2.4.2)

36) Survey Analysis

(PWS 5.2.4.2)

37) Program and Project Documentation

(PWS 5.2.5)

38) Program and Project Supplies Inventory

(PWS 5.2.6)

39) Meetings, Conferences, and Briefings

(PWS 5.2.7)

Attachment 15.4

INSPECTION CHECKLIST & SURVEILLANCE SUMMARY REPORT

Contractor Name: TBD

Contract Number: TBD

Contracting Officer Name: John C. Paitson

COR Name: Iris Hoehenberger

Supervisor Name: Sabine Schindler

Command: IMCOM

Directorate: USAG Wiesbaden PAIO

Military Unit:

Date:

Configuration Number: Rev 4 Revision Date: 20220217

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

COMMENTS: no findings

TOTALS

100.00%

All tasks have been inspected in accordance with this checklist per method of surveillance.

Results of inspection and surveillance justify the following rating (SELECT ONE).

Specific details are provided in the "Summary Report" portion below.

Very Good: Performance meets contractual requirements and exceeds some to the Government’s benefit. To justify a Very Good rating, identify a significant event and state how it was a benefit to the Government. There should have been NO significant weaknesses identified.

Satisfactory: Performance meets contractual requirements. To justify a Satisfactory rating, there should have been only minor problems, or major problems the contractor recovered from without impact to the contract/order. There should have been NO significant weaknesses identified.

Marginal: Performance does not meet some contractual requirements. To justify Marginal performance, identify a significant event in each category that the contractor had trouble overcoming and state how it impacted the Government. A Marginal rating should be supported by referencing the management tool that notified the contractor of the contractual deficiency (e.g., management, quality, safety, or environmental deficiency report or letter).

Unsatisfactory. Performance does not meet most contractual requirements and recovery is not likely in a timely manner. To justify an Unsatisfactory rating, identify multiple significant events in each category that the contractor had trouble overcoming and state how it impacted the Government. A singular problem, however, could be of such serious magnitude that it alone constitutes an unsatisfactory rating An Unsatisfactory rating should be supported by referencing the management tools used to notify the contractor of the contractual deficiencies (e.g., management, quality, safety, or environmental deficiency reports, or letters).

Surveillance Summary Report (Required): No findings.

Signature and Date of COR:

NAME: DATE:

image1.emf

ATT 13 COR MONTHLY SURVEILLANCE SCHEDULE TEMPLATE 31 Jan 2022.pdf

MONTHLY SURVEILLANCE SCHEDULE OF REQUIREMENTS

1) Contract #:

2) Contract Title:

3) Date Submitted:

4) Surveillance Period:

5) Functional Area:

6) COR NAME

7) Planned Dates of the month for

Surveillance

PWS #

PWS # PWS #

1 Contract:

2 Contract Title:

3 Date Submitted:

4 Surveillance Period:

5 Functional Area:

6 COR NAME:

7 Planned Dates of the month for SurveillanceRow1:

PWS Row1:

PWS Row1_2:

PWS Row1_3:

PWS Row1_4:

PWS Row1_5:

PWS Row1_6:

PWS Row1_7:

PWS Row1:

PWS Row1_8:

7 Planned Dates of the month for SurveillanceRow2:

PWS Row2:

PWS Row2_2:

PWS Row2_3:

PWS Row2_4:

PWS Row2_5:

PWS Row2_6:

PWS Row2_7:

PWS Row2:

PWS Row2_8:

7 Planned Dates of the month for SurveillanceRow3:

PWS Row3:

PWS Row3_2:

PWS Row3_3:

PWS Row3_4:

PWS Row3_5:

PWS Row3_6:

PWS Row3_7:

PWS Row3:

PWS Row3_8:

7 Planned Dates of the month for SurveillanceRow4:

PWS Row4:

PWS Row4_2:

PWS Row4_3:

PWS Row4_4:

PWS Row4_5:

PWS Row4_6:

PWS Row4_7:

PWS Row4:

PWS Row4_8:

7 Planned Dates of the month for SurveillanceRow5:

PWS Row5:

PWS Row5_2:

PWS Row5_3:

PWS Row5_4:

PWS Row5_5:

PWS Row5_6:

PWS Row5_7:

PWS Row5:

PWS Row5_8:

7 Planned Dates of the month for SurveillanceRow6:

PWS Row6:

PWS Row6_2:

PWS Row6_3:

PWS Row6_4:

PWS Row6_5:

PWS Row6_6:

PWS Row6_7:

PWS Row6:

PWS Row6_8:

7 Planned Dates of the month for SurveillanceRow7:

PWS Row7:

PWS Row7_2:

PWS Row7_3:

PWS Row7_4:

PWS Row7_5:

PWS Row7_6:

PWS Row7_7:

PWS Row7:

PWS Row7_8:

7 Planned Dates of the month for SurveillanceRow8:

PWS Row8:

PWS Row8_2:

PWS Row8_3:

PWS Row8_4:

PWS Row8_5:

PWS Row8_6:

PWS Row8_7:

PWS Row8:

PWS Row8_8:

7 Planned Dates of the month for SurveillanceRow9:

PWS Row9:

PWS Row9_2:

PWS Row9_3:

PWS Row9_4:

PWS Row9_5:

PWS Row9_6:

PWS Row9_7:

PWS Row9:

PWS Row9_8:

7 Planned Dates of the month for SurveillanceRow10:

PWS Row10:

PWS Row10_2:

PWS Row10_3:

PWS Row10_4:

PWS Row10_5:

PWS Row10_6:

PWS Row10_7:

PWS Row10:

PWS Row10_8:

7 Planned Dates of the month for SurveillanceRow11:

PWS Row11:

PWS Row11_2:

PWS Row11_3:

PWS Row11_4:

PWS Row11_5:

PWS Row11_6:

PWS Row11_7:

PWS Row11:

PWS Row11_8:

7 Planned Dates of the month for SurveillanceRow12:

PWS Row12:

PWS Row12_2:

PWS Row12_3:

PWS Row12_4:

PWS Row12_5:

PWS Row12_6:

PWS Row12_7:

PWS Row12:

PWS Row12_8:

7 Planned Dates of the month for SurveillanceRow13:

PWS Row13:

PWS Row13_2:

PWS Row13_3:

PWS Row13_4:

PWS Row13_5:

PWS Row13_6:

PWS Row13_7:

PWS Row13:

PWS Row13_8:

7 Planned Dates of the month for SurveillanceRow14:

PWS Row14:

PWS Row14_2:

PWS Row14_3:

PWS Row14_4:

PWS Row14_5:

PWS Row14_6:

PWS Row14_7:

PWS Row14:

PWS Row14_8:

7 Planned Dates of the month for SurveillanceRow15:

PWS Row15:

PWS Row15_2:

PWS Row15_3:

PWS Row15_4:

PWS Row15_5:

PWS Row15_6:

PWS Row15_7:

PWS Row15:

PWS Row15_8:

7 Planned Dates of the month for SurveillanceRow16:

PWS Row16:

PWS Row16_2:

PWS Row16_3:

PWS Row16_4:

PWS Row16_5:

PWS Row16_6:

PWS Row16_7:

PWS Row16:

PWS Row16_8:

7 Planned Dates of the month for SurveillanceRow17:

PWS Row17:

PWS Row17_2:

PWS Row17_3:

PWS Row17_4:

PWS Row17_5:

PWS Row17_6:

PWS Row17_7:

PWS Row17:

PWS Row17_8:

7 Planned Dates of the month for SurveillanceRow18:

PWS Row18:

PWS Row18_2:

PWS Row18_3:

PWS Row18_4:

PWS Row18_5:

PWS Row18_6:

PWS Row18_7:

PWS Row18:

PWS Row18_8:

7 Planned Dates of the month for SurveillanceRow19:

PWS Row19:

PWS Row19_2:

PWS Row19_3:

PWS Row19_4:

PWS Row19_5:

PWS Row19_6:

PWS Row19_7:

PWS Row19:

PWS Row19_8:

7 Planned Dates of the month for SurveillanceRow20:

PWS Row20:

PWS Row20_2:

PWS Row20_3:

PWS Row20_4:

PWS Row20_5:

PWS Row20_6:

PWS Row20_7:

PWS Row20:

PWS Row20_8:

7 Planned Dates of the month for SurveillanceRow21:

PWS Row21:

PWS Row21_2:

PWS Row21_3:

PWS Row21_4:

PWS Row21_5:

PWS Row21_6:

PWS Row21_7:

PWS Row21:

PWS Row21_8:

7 Planned Dates of the month for SurveillanceRow22:

PWS Row22:

PWS Row22_2:

PWS Row22_3:

PWS Row22_4:

PWS Row22_5:

PWS Row22_6:

PWS Row22_7:

PWS Row22:

PWS Row22_8:

7 Planned Dates of the month for SurveillanceRow23:

PWS Row23:

PWS Row23_2:

PWS Row23_3:

PWS Row23_4:

PWS Row23_5:

PWS Row23_6:

PWS Row23_7:

PWS Row23:

PWS Row23_8:

Text1:

Text2:

Text3:

Text4:

Text5:

Text6:

Text7:

Text8:

Text9:

Text10: 409thth CSB Monthly Surveillance Schedule

Text11: Revision 1, 31 Jan 2022 image2.emf

CTIP Surveillance Checklist.xlsx Approve

5.00 010000

Sheet1

CTIP INSPECTION CHECKLIST & SURVEILLANCE SUMMARY REPORT Method of Surveillance 100% Inspection

Contractor Name:

Contract Number:

Contracting Officer Name:

COR Name:

Supervisor Name:

Service Provided: Meeting Contract Requirements

Command:

Directorate:

Military Unit:

Date:

Configuration Number: Rev 4 Revision Date: 20220217

PART 1 General SAT UNSAT

1 Has the contractor submitted CDRL P-14 Combat Trafficking in Persons (CTIP) Prevention/Audit Plan and Audit Results?

COMMENTS:

2 Do the compliance plans provide the following at a minimum: a) Make employees and subcontractors aware of the Human Trafficking rules and requirements; b) Provide a process for employees to report, without fear of retaliation, including a means to make available to all employees and subcontractors a worry free hotline reporting mechanism and/or the hotline phone number of the Global Human Trafficking Hotline at 1-844-888-FREE and its email address at help@befree.org; c) A recruitment and wage plan that only permits the use of recruitment companies with trained employees, prohibits charging recruitment fees to the employee, and ensures that wages meet applicable host-country legal requirements or explains any variance; d) A housing plan, if you or your subcontractors intend to provide or arrange housing, that ensures that the housing meets host-country housing and safety standards; e) Procedures to prevent your company, your subcontractors, and agents at any tier and any dollar value from engaging in trafficking in persons and to monitor, detect, and terminate any employees, agents, subcontracts, or subcontractor employees who have engaged in such activities; and

f) Prohibit the use of forced labor in the performance of the subcontract?

COMMENTS:

3 Verify that the contractor’s subcontract agreements/purchase orders include CTIP FAR clause 52.222-50, Combating Trafficking in Persons, CJTSCC clause 5152.222-5900 (or successor clause), Prohibition Against Human Trafficking, Inhumane Living Conditions, and Withholding of Employee Passports, which are incorporated in this contract, and the contract PWS/SOW language and CDRL…