ASC LDC QASP 1Feb2024 V2.docx

ASC Laundry and Dry Cleaning

Quality Assurance Surveillance Plan

This plan is provided for information purposes only. This Quality Assurance Surveillance Plan (QASP) is not part of the solicitation, nor will it be made a part of any resulting contract. The QASP is a Government only document and should at no time be provided to the Contractor. The Government has the right to change or modify inspection methods at its discretion.

1. 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/products under this contract as identified in the Laundry and Dry Cleaning (L&DC) Performance Work Statement (PWS).

1.2. Intent. The intent of this plan is to hold the Contractor accountable for quality control and to encourage the contractor to take appropriate steps to control and improve quality. The Contractor is responsible to develop an efficient methodology to ensure they meet and/or exceed the required thresholds of service as outlined in this acquisition. The Government intends to perform surveillance on this contract In Accordance With (IAW) 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 reserves the right to perform quality assurance surveillance at the subcontract level and the contractor's place of business, if applicable. Non-conforming services discovered with subcontractor(s) will be addressed with the prime contractor for resolution.

2. DESCRIPTION OF SERVICES

2.1. Scope of Work. See PWS

2.2. Type of Contract. This contract is a Firm Fixed Price contract type.

3. ROLES AND RESPONSIBILITIES.

3.1. Government.

3.1.1. Contracting Officer (KO). This is the person who is assigned administrative management over the contract. The KO is the only person authorized to make changes in any of the requirements under the contract, and notwithstanding any provisions contained elsewhere in the contract, said authority remains solely with the KO. In the event the Contractor makes any 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 and expense of the Contractor. All contract administration will be affected by the KO. Communications pertaining to contractual administrative matters shall be addressed to the KO. 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. Contract Specialist (KS): The person assigned by the KO to perform the day-to-day administrative functions of the contract. This is the person the COR will interact with the most.

3.1.3. Contracting Officer’s Representative (COR). The KO will appoint a COR during the performance of this requirement. IAW AR 70-13, Management and Oversight of Service Acquisitions. Other surveillance personnel may be designated as a COR and shall be trained and appointed IAW Department of Defense Instruction (DoDI) 5000.72, DoD Standard for Contracting Officer’s Representative (COR) Certification, and Defense Federal Acquisition Regulation Supplement (DFARS) 201.602-2, Contracting Officer’s, Responsibilities. The COR will aid in identification and resolution of problems, conflicts in priority, subtask requirement definitions, and other operations type problems. The COR will perform IAW the responsibilities and duties identified in the appointment letter.

3.1.3.1. COR Authority. A letter of designation will be issued to the COR by the KO. A copy of the letter will be sent to the Contractor. The letter of designation states the responsibilities and limitations of the COR. The COR cannot redelegate their duties i.e., perform inspections written or oral communications. The COR has no authority to change cost, price estimates, or changes in delivery dates IAW FAR 1.602-1 (a).

3.1.3.2. COR/ACOR Functions. The COR/ACOR shall monitor all technical aspects of the contract and assist in contract administration. Multiple or alternate CORs include multiple regions or remote geographic locations of performance, contract complexity or performance risk, the need for increased surveillance, or magnitude of the requirement. The COR/ACOR is authorized to perform the following functions: assure 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; interpret technical requirements; monitor, document, and report Contractor's performance and notify both the KO and Contractor of any deficiencies; coordinate availability of Government-Furnished Property, and provides direction or assistance for site entry requests of Contractor personnel.

3.2. Contractor.

3.2.1. Contract Manager. Insert if applicable, If not applicable remove language leaving paragraph number & title. Beyond the paragraph number add “Reserved”) If the Contractor has a Contract Manager, copy and paste the information from the PWS and insert it here.

3.2.2. Project Manager. Insert if applicable, If not applicable remove language leaving paragraph number & title. Beyond the paragraph number add “Reserved”) If the Contractor has a Project Manager, copy and paste the information from the PWS and insert it here.

3.2.3. Quality Manager. Insert if applicable, If not applicable remove language leaving paragraph number & title. Beyond the paragraph number add “Reserved”) If the Contractor has a Quality Manager, copy and paste the information from the PWS and insert it here.

4. 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's Quality Control Program requirements are defined in Part 4.5.1 of the PWS. The Contractor shall develop, maintain, enforce, and document a Quality Control Plan (QCP) which complies with the requirements of this contract and outlines how they will ensure the Government will receive all the services required by the contract at the specified quality level.

4.2. Government Quality Assurance. The Government 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. GOVERNMENT SURVIELLANCE

5.1. Methods of Surveillance. The following Methods of Surveillance are used in monitoring the Contractors’ performance:

5.1.1. 100% Inspection. Reserved for the highest risk areas where consequence of failure is high (i.e., life or limb are threatened) or there is likelihood of mission failure.

5.1.2. Random Sampling. When a service is performed relatively frequently, and a statistically valid sample can be selected for audit. The most appropriate method for frequently recurring tasks.

5.1.3. Periodic Inspection. Planned sampling of a service at specific predetermined dates and times. May be appropriate for tasks that occur infrequently.

5.1.4. Customer Feedback. The following procedures will be followed when a complaint is received regarding the Contractor/Contractor Employees.

· The COR will investigate and determine the validity of the complaint.

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

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

5.2. Monthly Surveillance Schedule (Attachment 9). The COR will develop a monthly surveillance schedule IAW Attachment 9 and filed in the Procurement Integrated Enterprise Environment (PIEE), Surveillance and Performance Monitoring (SPM), Surveillance Documents Section of the Contract File using the Add Smart Form function. The schedule is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel.

· The surveillance schedule may be used to plan and schedule monthly surveillance.

· Planned/Random/Periodic surveillance occur only during Contractor’s operation.

· Method of surveillance, place of inspection, activity to be monitored, and who will conduct the surveillance (dates and times can be altered without a formal change to the schedule if all inspections are performed). Date and Time of surveillance can be altered without a formal change to the schedule.

5.3. Surveillance Instructions/Checklists. The COR will use the Surveillance Inspection (Attachment 11) for all planned inspections. Documents will be filed in the PIEE, SPM, Surveillance Documents Section of the Contract File using the Add Smart Form function.

5.4. Documentation of Inspections. Surveillance checklists and Inspection worksheets will be completed within no later than two (2) calendar days. No later than the 15th of each month surveillance documentation for the preceding month will be filed. Surveillance documentation includes a COR Status Report, the Surveillance Schedule, all completed Surveillance Checklist(s) for the period the COR Status Report covers, Nonconformance Reports, if any, and Contractor Deliverables, if any. Documentation will be maintained for future reference, audit, proof of inspection, and past performance documentation.

6. Corrective Action Request. Army Contracting Command (ACC) Corrective Action Request (CAR) (formerly Nonconformance Report (NCR)) procedures for issuing, overseeing, and closing CARs, and for managing contractual nonconformances on ACC administered contracts as directed in the ACC Acquisition Instruction (AI) (Attachment 8) and FAR subpart 46.407 Nonconforming supplies or services.

NOTE: All instances of corrective actions must be documented in writing

6.1. Non-Conforming Performance. Non-conformance occurs when a Contractor fails to meet contract or task order terms, conditions and/or specifications. The COR will notify the Contractor, in person, each time an unacceptable observation has been recorded and ask the Contractor to correct the problem or re-accomplish the service. Resolution of non-conformance discovered at the subcontractor level shall be addressed with the prime contractor.

6.1.1. Documenting CARs. A CAR alone is not considered a contract remedy. It is used as a notice to the contractor to document a nonconformance, notify the contractor of Government rejection of supplies or services (including construction) not conforming to contract requirements, and to require contractor corrective action. The purpose is to provide the contractor an opportunity to correct or replace nonconforming supplies and services when this can be accomplished within the required delivery schedule IAW FAR 46.407 and contract terms and conditions. Nonconformances identified in CARs must be traced to contractual requirements.

· Unless contract remedies are issued, use a CAR for the following:

· To document all types of contractor nonconformance identified by the government on contracts administered by ACC;

· To document and correct significant deficiencies on contractor business systems (CBS) as defined at DFARS 252.242-7005(b);

· To document rejection or refusal to accept supplies, services, construction work, and nonconforming deliverables;

· To give the contractor an opportunity to correct or replace nonconforming supplies, services, construction, or deliverables;

· To evaluate the effectiveness of contractor corrective actions to track performance trends and establish contract risk levels used to determine the appropriate level of oversight;

· CARs should be included as part of performance information in Contractor Performance Assessment Reporting System (CPARS), Program Management Reviews, Performance Feedback Sessions, Award Fee Boards, and Incentive Fees.

· CARs also identify and track Government actions to specific contractor nonconformance(s).

· CARs shall not be used to address nonconformance of internal contractor processes unless those processes are directly traced to contract requirements (i.e. Government approved Quality Control Plans or Property Management Systems).

6.1.2. CAR Levels. There are four CAR levels. The level of the CAR documents and communicates the seriousness of the nonconformance. To determine the appropriate CAR level, analyze the impact and/or effect of the nonconformance and associate that impact to one of the four levels as defined below.

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

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

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

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

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

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

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

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

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

d. 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.1.3. Overarching CAR Process Flow. The following outlines the normal process flow for the corrective action process. Follow the steps provided within the PDREP CAR Module User Guide. (Note: Steps in subparagraphs (f)-(j) below do not apply to Level I CARs as they are considered closed immediately upon issuance.)

a. Identify a contract nonconformance;

b. The COR will create a CAR;

c. Review the CAR;

d. Coordinate and approve the CAR;

e. The KO shall issue the CAR to the contractor;

f. Receive and review the contractor’s CAP;

g. Accept/reject the contractor’s CAP;

h. Oversee contractor corrective action using a risk based approach;

i. Receive notification from the contractor that corrective action is accomplished;

j. Verify corrective action was accomplished satisfactorily;

k. The KO shall close the CAR;

6.1.4. CAR System of Record (SOR)

a. SOR. The PDREP CAR Module is the SOR for CARs 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.

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

c. User Roles. Refer to Table 1.1 of the DoD CAR Manual for a description of the functions available to each role. NOTE: Ensure CORs register as a Functional Specialist under the contracting office DoDAAC they will support.

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

e. Classified information. Classified information will not be entered into the CAR Module.

6.1.5. Issuing CARs to the Contractor. The KO shall address CARs to the appropriate level of contractor management based on the seriousness of the nonconformance. This requires subjective judgement by the reviewer(s) and issuing official. Consideration should also be given to established lines of communication with the contractor and/or contractor requested addressees. The following are guidelines for addressing CARs:

a. Level I CARs: Lower-level management responsible to correct the nonconformance (e.g. shop foreman /supervisor/ quality manager).

b. Level II CARs: Functional level manager responsible for corrective action (e.g. the quality manager or site manager).

c. Level III CARs: Top-level management on-site or locally.

d. Level IV CARs: Corporate-level management.

e. Subcontractors. If a subcontractor’s performance is nonconforming, address CARs to the prime contractor who is responsible for subcontractor performance and has privity of contract.

f. Verbal. It is appropriate to verbally notify the contractor when the Government identifies a nonconformance or potential nonconformance. Refrain from telling the contractor that ‘a CAR shall be forthcoming’ or the anticipated level of a CAR. Official notification of the nonconformance shall be through the PDREP CAR Module and issuance of the CAR.

g. Do not issue a CAR if the contractor self-identifies contractual nonconformances and takes timely and effective corrective action. If the corrective actions prove ineffective, then issuing a CAR is appropriate. Contractor identification and self-initiated corrective actions are not only desired behaviors but are a requirement of quality and quality systems required by clauses. Joint inspections (i.e. an inspection with both a Gov’t inspector and Contractor inspector) should be considered a Government inspection. Therefore, any nonconformance identified in a joint inspection would be considered a Government identified, not contractor self-identified nonconformance.

6.1.6. Responsibilities for Level III / IV CARs

a. The cognizant contracting officer may issue a Level III / IV CAR only after it has been pre-coordinated and concurred by the Senior Contracting Official (SCO) IAW local procedures. Each SCO will develop their own review and concurrence process with the goal of applying the appropriate level of CAR, discussing potential courses of actions the government may take, and obtaining a legal review. SCOs should not sign or issue CARs. If the CAR is contested by the contractor, a contracting officer-issued CAR allows the SCO to adjudicate any contractor concern. Pre-coordination IAW local procedures will be performed outside of the CAR Module, therefore, upload correspondence and decision supporting documents in VCE-PCF.

b. Issuance of Level III / IV CARs require a Serious Incident Report (SIR) or Commander's Critical Information Requirement (CCIR) be submitted to HQ ACC prior to issuance. The type of report depends on the severity of the nonconformance.

c. This notification should provide an executive-level synopsis of the underlying nonconformance and the impact/potential impact.

d. A subsequent SIR should be submitted if CAPs are rejected. Contact ACC G3 Current Operations (G33) for latest SIR/CCIR procedures or for assistance at ACC G3 | Mission Operations (army.mil).

e. Submit SIRs through the SCO operations personnel to usarmy.redstone.acc.mbx.hqacc-g3ops@army.mil after following local procedures.

f. Notify the requiring activity, supported unit/organization leadership upon discovering a Level III / IV nonconformance since it could impact the delivery of the product or services.

g. If the Contract Administration Office (CAO) is different than the awarding office, the CAO will coordinate with the current Procuring Contracting Officer (PCO) prior to issuance of a Level III / IV CAR. This is necessary to ensure a coordinated, consistent message to contractor management. The PCO may request management of the CAR by having it transferred to the PCO.

h. When a significant deficiency of a CBS is discovered, notify and coordinate with the contracting officer with cognizance over the business system (i.e. the Corporate Administrative Contracting Officer (CACO) or Division Administrative Contracting Officer (DACO)) prior to issuance. The CACO/DACO may agree to issue the CAR instead. If not, ACC shall issue the CAR against the ACC administered contract and copy the CACO/DACO. When DoD is the Cognizant Federal Agency, many of the CACOs and DACOs reside in DCMA and their contact information can be found in the PIEE CBAR Module of EDA. If DCMA is not the Cognizant Federal Agency, there is no other system to determine if there is a CACO or DACO assigned. Therefore, the contracting officer must ask the contractor if there is an assigned CACO/DACO if the contracting officer is not already aware of the person (sometimes the CACO/DACO may be outside the DoD). If the CACO/DACO cannot be identified, contacted, or does not respond to communications in a reasonable time, do not hold up issuance of the CAR. However, continue efforts to identify and/or contact the CACO/DACO if one exists. If a CACO/DACO does not exist, then treat the business system nonconformance as a contract nonconformance.

i. Coordinate the CAR with local legal advisors if fraud, corruption, serious contractor employee misconduct, counterfeit items are suspected, and/or if there is suspicion a law has been violated. If criminal activity is suspected, contact the Army Criminal Investigation Division (CID).

6.1.7. Timelines. Transmitting CARs to the Contractor. CARs are time sensitive and delayed issuance may have impacts on the requiring activity/supported unit’s mission; delay contractor corrective action; reduce the relevancy of lower-level CARs; or reduce the capability for the contractor to perform effective root cause analysis.

a. Level I CARs: The standard is to issue the CAR no later than (NLT) three business days after identification of the nonconformance.

b. Level II CARs: The standard is to issue the CAR NLT five business days after identification of the nonconformance.

c. Level III / IV CARs: The standard is to issue the CAR NLT ten business days after identification of the nonconformance.

6.1.8. Corrective Action Plan Due Date. When a Level II CAR and above is issued, a contractor CAP is requested with a designated number of days to respond. The CAR Module will default to 45 days but allows a contracting office to insert any number less than to respond. The recommended due dates are:

a. Level II CARs. Level II CARs in ACC should require no more than 10 business days to respond with a CAP.

b. Level III / IV CARs. Level III / IV CARs should require no more than 15 business days to respond, with the exception of CARs related to CBS significant deficiencies. CBS related Level III / IV CARs will have up to 45 calendar days as allowed by DFARS 252.242-7005.

c. Extensions. Contractors may request an extension of the designated due date. This is acceptable for the government to allow when reasonably justified. All results of that correspondence will be entered into the PDREP CAR Module.

d. CAP Reviews. For Government review of contractor submitted CAPs, accept or reject the CAP within 5 business days for Level II, and 10 business days for Level III / IV CARs. Use the PDREP CAR Module to input the decision and provide the contractor a formal response for acceptance or rejection.

e. Government CAP Verification & Validation of Corrective Action/CAR closure. Timelines for verification and validation of corrective actions can vary depending on the severity of the CAR, and completion of milestones identified in the CAP. Once the Government has verified the contractor has implemented the CAP and validated the issues have been corrected and are acceptable to prevent further occurrence, close the CAR in the Module. Notify the contractor the CAR is closed via the CAR Module.

6.2. Customer Feedback. For customer feedback or complaints (Technical Exhibit – E – Customer Complaint Record), shall be used. However, customer feedback can be in any form, verbal or written but no matter the format the COR will maintain a record of the feedback; positive or negative. If immediate response to a complaint is required, the COR will provide the response to the requester as soon as practical.

· The COR will investigate to determine the validity of any negative comments received.

· If the negative comment is determined not to be valid, if possible, the COR will inform customer of the reason(s) as soon as practical.

· For validated negative comments that are true contractual non-conformances see paragraph 6. If this non-conformance is a more serious (systemic in nature) deficiency or recurring deficiency that could indicate a trend the COR should see paragraph 6.2.

· The COR will follow up with the customer of the corrective action taken by the contractor, if applicable.

7. ACCEPTANCE OF SERVICES. When all services have been deemed acceptable and there is documented objective quality evidence to support acceptable performance in the COR’s file, the COR will accept the services provided and authorize payment upon satisfactory completion of the work. This is accomplished by approving the Contractor’s invoice in the Wide Area Workflow module at https://piee.eb.mil/.

8. COR STATUS REPORT. No later than the 15th day of each month, the COR will complete the COR Status Report for KO review. The KO and COR shall use the criteria listed in Attachment 7 when completing the a rating. This rating will be based on the COR’s performed inspections during the month.

· In the event there is no contractor performance to observe for the month, the COR is REQUIRED to submit a COR Status Report indicating the following: “No reported surveillance for month xxx due to no contractor performance”.

· The COR Status Report shall be filled out in its entirety based on the submitted surveillance for the month to include surveillance checklist, surveillance schedule, contractor deliverables, NCR’s (if applicable). The COR shall ensure all information annotated in the COR Status Report is current, valid, and supplemented by objective evidence in the COR’s online file. This includes the number of Contractor employees currently on the contract (if applicable).

9. SERVICE CONTRACT REPORTING (SCR). The Contractor must report contractor manpower to the System for Award Management website at https://www.sam.gov. IAW Office of the Secretary of Defense Memorandum, Revised Department of Defense Contractor Manpower Reporting Initiative, dated Oct 16, 2019, If the KO has designated service contract reporting as the COR’s responsibility, the COR shall verify that the Contactor has complied with the required contractor manpower reporting no later than 31 Oct for the previous FY. The COR shall identify and document observations of compliance in their November COR Status Report. The COR shall upload a copy of the service contract report or a screenshot of contractor submission in their online file providing evidence of contractor submission and COR validation.

10. CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS). The KO is responsible for the completion of CPARS entry IAW AFARS Subpart 5142.15. CPARS will be completed using supporting surveillance data (COR Status Reports, Completed Surveillance Checklists, Customer Feedback, Deliverables, if any, and Nonconformance Reports, if any) annually or at the end of a Task Order, whichever occurs first.

11. 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 contract employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

12. 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. The COR Surveillance file shall contain the following as applicable:

a. Copy of the COR designation letter from the KO, any changes to that letter, and any termination letters.

b. Training Certifications for COR and refresher training.

c. Copy of the applicable Quality Assurance Surveillance Plan (QASP).

d. Copy of the contractor’s Quality Control Plan (QCP).

e. All correspondence initiated by authorized representatives (Contractor or Government) concerning performance of the contract.

f. Names, position titles and contact information of all key personnel assigned to this contract both Government and Contractor.

g. Monthly surveillance schedules.

h. Surveillance Checklists.

i. Records of all inspections performed and the results.

j. Customer Feedback.

k. Memoranda for record of minutes of any meeting, telephone conversations and discussions with the contractor or others pertaining to the contract or contract performance.

l. Documentation pertaining to tracking expenditures/receipts (i.e., T&M & Cost CLIN items).

13. RECORD RETENTION. All records will be retained IAW ARIMS AR 25-400-2.

14. QASP CHANGES. The QASP is a living document and, as such, may be changed as needed. However, the KO/KS and ASC HQs must approve changes. The COR will submit recommended changes to the KO/KS for approval. Once approved, the COR will upload the newest version into their online file.

15. ATTACHMENTS

Attachment 7 – CPAR rating justification Attachment 8 – Acquisition Instruction (AI) Attachment 9 – Surveillance Schedule Attachment 10 – Reduction Calculator Attachment 11a – Inspection Worksheet @ Customer Location (Linen) Attachment 11b – Inspection Worksheet @ Customer Location (Dry-Cleaning, OCIE, Specialty Items) Attachment 11c – Inspection Worksheet Administration Attachment 11d – Inspection Worksheet @ Contractor Location Attachment 12 – Inspection Report