Region5_FIS_PWS_Section J_TE-06_Quality Assurance Surveillance Plan_20211028.pdf

TECHNICAL EXHIBIT 06

(TE-06)

QUALITY ASSURANCE SURVEILLANCE PLAN

Region5_FIS_PWS_Section J_TE-06_Quality Assurance Surveillance Plan_20211028.pdf

Quality Assurance Surveillance Plan

Facility Investment Services for

63d Readiness Division

Region 5

CONTRACT NUMBER:

DATE:

TE-06_QASP_2 of 70

TABLE OF CONTENTS

1. Overview.

2. Description of Services.

3. Roles and Responsibilities.

4. Contract Quality Requirements.

5. Government Surveillance.

6. Non-Conforming Performance

7. Acceptance of Services

8. COR Monthly Report

9. Contractor Manpower Reporting

10. Contractor Performance Assessment Reporting System (CPARS)

11. Combating Trafficking In Persons (CTIP)

12. COR/Quality Assurance Surveillance Files

13. QASP Changes

ATTACHMENT LIST

Attachment 1 – Performance Requirements Summary (PRS)

Attachment 2 – Customer Complaint Record, DA Form 5477

Attachment 3 – Surveillance Checklist

Attachment 4 – Contract Discrepancy Report, DA FORM 5479

Attachment 5 – SAM.gov System Account User Guide

Attachment 6 – SAM Service Contract Reporting Quick Start Guide

TE-06_QASP_3 of 70

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 receipt of services under the contract as identified in the Performance Work Statement (PWS).

1.2. Intent. The intent of this QASP is to:

(1) Verify Contractor performance meets or exceeds contract terms, conditions, and specifications.

(2) Hold the Contractor accountable for quality control.

(3) Direct 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.

2. Description of Services.

2.1. Scope of Work. USACE has awarded a service contract to provide Facility Investment Services for Army Reserve Centers in the 63d Readiness Division, Region 5 Area of Operation.

Facility Investment Services includes response to service calls; preventive maintenance; system inspection, testing, and certifications; IDIQ orders beyond service calls; environmental services;

and other recurring services.

2.2. Type of Contract. This is a Firm Fixed Priced contract.

3. 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 KO is the ONLY individual who can legally bind the Government.

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 the Contractor performs the technical requirements of the contract; perform inspections as necessary in connection with contract performance; maintain written and oral communications

TE-06_QASP_4 of 70 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 notify both the KO and Contractor of deficiencies; coordinate availability of Government furnished property; and provide site entry of Contractor personnel.

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.

3.2. Contractor.

3.2.1 Project Manager (PM). The PM must have relevant experience at a comparable level of responsibility in projects of similar size, scope and complexity. The PM shall serve as the single point of contact (POC) and liaison for all work required. This person shall act for the contractor when the manager is absent and shall be designated in writing to the KO. The PM shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The PM or alternate shall be available between 07:30 AM through 4:30 PM, Monday thru Friday, except Federal holidays or when the government facility is closed for administrative reasons. The PM shall ensure that the contractor makes contact with the government designated POCs prior to conducting work on an installation. The PM shall ensure: all work is accomplished with adequate internal controls; all procedures are reviewed to eliminate conflicts, errors, and omissions; and technical accuracy is maintained for all other services and products specified in the PWS.

4. Contract Quality Requirements.

4.1. Contractor’s Quality Control Program. The Contractor’s quality control program (IAW FAR 52.212-4) 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 Section C: Annex 2 - Management and Administration- Spec Item A2-2.6.5, A2-2.6.6, and A2-2.6.7 of the PWS as indicated in Attachment 1. The Contractor shall identify and prevent, non-recurrence of defective services.

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

TE-06_QASP_5 of 70

5. Government Surveillance.

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

5.1.1. Customer Complaint Record (DA FM5477). The Customer Complaint Record form, Attachment 2 below, shall be used for the reporting of this effort and can be uploaded into Procurement Integrated Enterprise Environment (PIEE): Surveillance and Performance Monitoring (SPM) Module- COR Surveillance File- COR Documents section (with backup additional documentation, as applicable) via the monthly report to the Contracting Officer.

Customer feedback is typically obtained via telephone or email. Telephonic customer complaints must be followed up in writing/email. To be considered valid, the customer complaint must clearly articulate the nature of the complaint, time, date, etc. The COR will investigate the complaint. If determined to be valid, the COR will advise the KO and the Contractor of the deficiency. Copies of valid complaints and the resolution must be retained in the official contract file.

5.1.2. Periodic Inspection: This is a method whereby the outputs of a particular service are inspected on a periodic or planned basis. This method, sometimes called "planned sampling," consists of the evaluation of tasks selected on other than a 100 percent or random basis. A predetermined plan for inspecting part of the work is established using subjective judgment and analysis of agency resources to decide what work to inspect and how frequently to inspect

it. It may be appropriate for tasks that occur infrequently, and where 100 percent inspection is neither required nor practicable. This surveillance method may be done daily, weekly, biweekly, and/or monthly, as specified by a QAE or COR check sheet. Selecting this tool to determine contractor compliance with contract requirements can be quite effective and it allows for assessing confidence in the contractor’s performance without consuming a significant amount of time. These inspections include unscheduled/impromptu inspections (the COR may conduct unscheduled and impromptu evaluations whenever the need arises). This method is conducive to areas where the sample is not large and/or the areas to be inspected are located at several locations. This method permits the Government to conserve resources while still observing negative trends or areas that need improvement (i.e., do not meet the PWS requirements).

5.2. Surveillance Instructions/Checklists. The Surveillance Checklist, Attachment 3, will be utilized and completed when surveillance is conducted, at the discretion of the COR.

6. Non-Conforming Performance A non-conformance occurs when a Contractor fails to meet Contract or Task Order terms, conditions and/or specifications. All instances of non-conformance will be documented, and the Contractor will be notified. Resolution of a non-conformance discovered at the Subcontractor level will be addressed with the prime Contractor. A non-conformance is classified as either: Level I (Minor); Level II (Major); or Level III (Critical).

TE-06_QASP_6 of 70

6.1. Level I (Minor). A Level I (Minor) Non-conformance is not likely to materially reduce the usability of facilities, systems, or equipment 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 Contract Discrepancy Report (CDR). However, the Government is still required to document verbal Level I CDRs. The COR may issue verbal Level I CDRs directly to the appropriate level of Contractor management. The COR will notify the KO as soon as practicable when a verbal Level I CDR is issued and document it in the COR’s Monthly Report. 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 CDRs, Attachment 4.

6.2. Level II (Major). A Level II (Major) Non-conformance is likely to materially reduce the usability of facilities, systems, or equipment for their intended purpose or is a departure from established standards likely to result in failure of the services to meet contract requirements.

Also, repeated discrepancies, a large number of documented Level I CDRs and trends indicating failure of the Contractor’s quality control program can be classified as Level II CDRs and all actions taken by all parties up to this point should be documented and referenced on the CDR submitted to the KO by the COR. The KO then issues all Level II CDRs in writing, Attachment 4.

The COR will notify the KO as soon as practicable when a major non-conformance is identified.

6.3. Level III (Critical). A Level III (Critical) Non-conformance is a major non-conformance that:

has potential for or results in hazardous or unsafe conditions due to the manner and/or conditions under which services are performed; prevents or impacts a vital agency mission as a result of substandard performance; or results from repeated and/or uncorrected Level II CDRs.

The Contracting Office Director or Deputy Director issues written Level III CDRs. The COR is responsible for notifying the KO immediately upon discovery of a critical non-conformance.

6.4. Documenting CDRs. Documentation, as a minimum, will include: the Contract and 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 CDRs. All CDRs, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track CDRs to ensure the Contractor identifies and takes appropriate corrective action against 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.

TE-06_QASP_7 of 70

7. Acceptance of Services Services are deemed delivered at the time the work is performed in compliance with contract requirements. When a service has been delivered and required objective quality evidence to support acceptable performance is provided, the Contractor will invoice for the services and provide the supporting documentation and status reports. The COR will accept the services provided and authorize payment to the Contractor by validation of the invoice. This validation is accomplished via surveillance activities, review of MAXIMO data/documentation and/or review and approval of the Contractor’s invoice with the required supporting documentation.

Upon validating correctness and accuracy of the Contractor’s invoice, the COR will sign and forward for Regional USACE PM verification of invoiced amount against available funds. The Regional USACE PM will subsequently submit the Contractor’s approved invoice to the responsible USACE Budget/Program Analyst to process and submit to the USACE Finance Center for certification and disbursement.

8. COR Monthly Report COR Monthly Reports will be submitted to the Contracting Officer no later than the 15th of each month for the preceding month via the Procurement Integrated Enterprise Environment (PIEE):

Surveillance and Performance Monitoring (SPM) Module- COR Surveillance File- COR Documents. COR Monthly Reports will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis will contain a summary of: surveillance performed; customer feedback, if any; CDRs, if any; analysis of the Contractor’s performance;

recommended adjustments to surveillance schedules; and any other pertinent contract information. Completed Surveillance Checklists and CDRs, if any, will be included as attachments to COR Monthly Reports or uploaded separately in the Procurement Integrated Enterprise Environment (PIEE): Surveillance and Performance Monitoring (SPM) Module- COR Surveillance File- COR Documents section of the CORs’ Online file.

9. Contractor Manpower Reporting In accordance with FAR 52.204-14 and 52.204-15 and AFAR 5137.91, the Contractor shall report, annually no later than 31 October, the following information, for services performed under this contract during the preceding Government fiscal year (October 1-September 30):

(1) Contract number and, as applicable, order number.

(2) The total dollar amount invoiced for services performed during the previous

Government fiscal year under the contract.

(3) The number of Contractor direct labor hours expended on the services performed during the previous Government fiscal year.

(4) Data reported to the prime contractor by subcontractors in accordance with FAR 52.204-

14 and 52.204-15.

The information required above shall be submitted via the internet at www.sam.gov. The SAM.gov System Account User Guide and SAM Service Contract Reporting Quick Start Guide are provided in Attachment 5 and 6. If the Contractor fails to submit the report in a timely manner, Region5_FIS_PWS_Section J_TE-06_Quality Assurance Surveillance Plan_20211028.pdf

TE-06_QASP_8 of 70 http://www.sam.gov/ the contracting officer will exercise appropriate contractual remedies. The Contractor’s failure to comply with reporting requirements will be a part of the Contractor’s performance information.

While inputs may be reported any time during the FY, all data shall be reported no later than 31 October 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 Procurement Integrated Enterprise Environment (PIEE): Surveillance and Performance Monitoring (SPM) Module- COR Surveillance File- COR Documents section of the CORs’ Online file

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

The COR shall document that CPARS, if required, was completed in the Procurement Integrated Enterprise Environment (PIEE): Surveillance and Performance Monitoring (SPM) Module- COR Surveillance File- COR Documents

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 alleging a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct which 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 the Procurement Integrated Enterprise Environment (PIEE) within the Surveillance and Performance Monitoring (SPM) Module found at https://wawf.eb.mil/ and stored under the specified Task Order IAW USACE Acquisition Instruction (UAI) 5101.604-100.

13. 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 KO for approval and the KO must approve all changes.

TE-06_QASP_9 of 70 https://wawf.eb.mil/

ATTACHMENT LIST

1. Performance Requirements Summary (PRS)

2. Customer Complaint Record, DA Form 5477

3. Surveillance Checklist(s)

4. Contract Discrepancy Report, DA Form 5479

5. SAM.gov System Account User Guide

6. SAM Service Contract Reporting Quick Start Guide

TE-06_QASP_10 of 70

Attachment 1 – Performance Requirements Summary (PRS)

PRS

Number PWS PARAGRAPH AND SERVICE PERFORMANCE STANDARD

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment 01-A A3-3 - FFP Work - The

Contractor shall maintain, repair, and alter facilities, systems, and equipment to ensure they are fully functional and operational.

Facilities, systems, and equipment are in an operable condition and function properly in accordance with specified standards.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

01-B A3-3.1 - Service Calls - The Contractor shall perform service call work in a timely manner and ensure facilities, systems, and equipment is restored to a safe, operable condition and function properly.

Service call work is responded to and completed within the specified time.

Facilities, systems, and equipment are restored to operable condition and function properly in accordance with OEM specifications.

Work is accomplished per Spec Item 2.3, Workmanship and Material Standards.

When repair is complete the facility, system, or equipment does not present any hazard or danger to personnel.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_11 of 70

Number PWS PARAGRAPH AND SERVICE PERFORMANCE STANDARD

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment 01-C A3-3.1.1 - Emergency Service

Calls - The Contractor shall respond to emergency service calls and arrest emergent conditions to minimize and mitigate damage to facilities, systems and equipment and danger to personnel.

Associated repairs are completed to ensure facilities, systems, and equipment is restored to a safe, operable condition and function properly.

Emergency calls are responded to within 60 minutes of receipt of call during Government regular working hours and two hours of receipt of call outside of Government regular working hours.

Work is continued without interruption until emergent condition is arrested.

Facilities, systems, and equipment are restored to operable condition and function properly in accordance with OEM specifications.

Work is accomplished per Spec Item 2.3, Workmanship and Material Standards.

When repair is complete the facility, system, or equipment does not present any hazard or danger to personnel.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_12 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment 01-D A3-3.1.2 - Routine Service Calls -

The Contractor shall complete routine service calls in a timely manner and ensure facilities, systems, and equipment are restored to a safe, operable condition and function properly.

Routine service calls are completed within twenty working days.

Facilities, systems, and equipment are restored to operable condition and function properly inaccordance with OEM specifications.

Work is accomplished per Spec Item 2.3, Workmanship and Material Standards.

When repair is complete the facility, system, or equipment does not present any hazard or danger to personnel.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

01-E A3-3.1.3 - Urgent Service Calls - The Contractor shall complete urgent service calls in a timely manner to prevent emergency conditions, and to ensure facilities, systems, and equipment are restored to a safe, operable condition and function properly.

Urgent service calls are completed within five working days.

Facilities, systems, and equipment are restored to operable condition and function properly in accordance with OEM specifications.

Work is accomplished per Spec Item 2.3, Workmanship and Material Standards.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_13 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment When repair is complete the facility, system, or equipment does not present any hazard or danger to personnel.

01-F A3-3.2 - Preventive Maintenance (PM) Program - The Contractor shall develop and implement a PM program for all systems and equipment.

This is to ensure proper operation, minimize breakdown, and maximize the equipment's useful life.

The Contractor’s PM program is submitted within 60 calendar days following award.

The Contractor’s approved PM Program is updated annually and submitted within 30 days of option award.

PM is accomplished per the Contractor's program and work schedule.

The Contractor submits the annual PM Schedule with the PM Program.

PM Schedule Monthly updates are submitted by the 25th of each month.

Unaccomplished PM Reports are submitted, as required.

At a minimum, the contractors PM Program shall: outline equipment to be inspected/maintained, identify

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_14 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment wearable parts for each piece of equipment, list subcontractors and manufacturers for wearable parts, define checklists (job plan) for what will be inspected, identify inspection intervals, define the skills sets (personnel skills) required for each PM checklist to be completed, and define a record keeping system for tracking completed PMs. In addition to the requirements of this section and other contract documents, detailed information shall be provided for each of the specification items subordinate to A3-3.2.

All items are captured/updated in MAXIMO and the Government notified of where/how to access the information for review.

TE-06_QASP_15 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment 01-G A3-3.3 - Inspection and Testing -

Inspection, Testing, and Certification - The Contractor shall provide inspection, testing, and certification services to ensure equipment is maintained in a safe and fully operational condition.

All certifications are current.

Certifications are completed as scheduled.

Testing, inspection, and certification services performed in accordance with applicable references.

Repairs within the inspection, testing, and certification limit are accomplished prior to inspection, testing, and certification completion.

Notification of repair work exceeding the inspection, testing, and certification limit is submitted to the KO within the specified time limit.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

01-H A3-3.4 - Other Recurring Services - The Contractor shall develop and implement an Other Recurring Services Program for all facilities, systems, and equipment to ensure they are fully functional and operational.

Facilities, systems, and equipment are in anoperable condition and function properly inaccordance with specified standards.

The Contractor’s Other Recurring Services Program is submitted within 60 calendar days following award.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_16 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment The Contractor’s approved Other Recurring Services Program is updated annually and submitted within 30 days of option award.

Other recurring services are completed per the Contractor’s approved program and schedule.

Annual and monthly schedules and unaccomplished reports are submitted.

At a minimum the Contractor's Other Recurring Services Program shall: outline equipment to be inspected/maintained, identify wearable parts for each piece of equipment, list subcontractors and manufacturers for wearable parts, define checklists for what will be inspected, identify inspection intervals, define the skill sets (personnel skills) required for each recurring service checklist to be completed, and define a

TE-06_QASP_17 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A3 - Facility Investment record keeping system for tracking completed recurring services. In addition to the requirements of this section and other contract documents, detailed information shall be provided for each of the specification items subordinate to A3-3.4.

01-I A3-3.5 - Service Call and Preventive Maintenance Reporting Requirements - The Contractor shall provide a written report on service call and preventive maintenance activities.

The contractor shall provide a written report to the COR/KO on service call and preventive maintenance activities not later than 15 days after completion of each task order and at the end of the contract.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

01-J A3-4 - IDIQ (Individual Task Order) Work - IDIQ Work will be ordered utilizing a task order in accordance with 52.216-18, ORDERING in Section I. The order will specify the exact locations and types of work to be accomplished. The period of performance will be specified in each order.

All requirements of the IDIQ Scope of Work (SOW) are completed, as specified and in accordance with governing regulations and standards, and within the negotiated period of performance.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_18 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A4 - Environmental

02-A A4-3 - Environmental FFP Work

- The Contractor shall perform environmental services to support the installation’s environmental programs that ensure compliance with applicable Federal, state and local statutes and regulations, and with DoD policies, instructions and guidance.

Note that the Contracting Officer may add additional recurring environmental services to the contract via a modification. Examples includestorm water and potable water sampling and analysis, hazardous material and hazardous waste management, and other recurring environmental services.

Services are performed in a timely manner and in compliance with Federal, state and local statutes and regulations, and with DoD policies,instructions and guidance.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

02-B A4-4 - Environmental IDIQ Work

- IDIQ work will be ordered utilizing a task order in accordance with 52.216-18, ORDERING in Section I. The order will specify the exact locations and types of work to be accomplished which may include, but is not limited to, All requirements of the IDIQ Scope of Work (SOW) are completed, as specified and in accordance with governing regulations and standards, and within the negotiated period of performance.

95% or Greater Total Cumulative PRS Inspection Checklist Compliance Rate

- Periodic Inspection

- Random Inspection

- Rework

- Equitable Price reductions/consideration

- NCR Issued

TE-06_QASP_19 of 70

ACCEPTABLE LEVEL OF

PERFORMANCE

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM THE

REQUIREMENT

FREQUECY/

METHOD OF

SURVEILLANCE

CONSEQUENCES OF

FAILURE TO MEET

PERFORMANCE

STANDARD

A4 - Environmental standard and expedited routine cleaning/maintenance, standard and expedited non-routine separator test support. The period of performance will be specified in each order.

TE-06_QASP_20 of 70

Attachment 2 – Customer Complaint Record, DA Form 5477

Region5_FIS_PWS_Section J_TE-06_Quality Assurance Surveillance Plan_20211028.pdfRegion5_FIS_PWS_Section J_TE-06_Quality Assurance Surveillance Plan_20211028.pdf

TE-06_QASP_21 of 70

Attachment 3 – Surveillance Checklist

COR Inspection Checklist & Data Report (Fixed Firm Price Contract)

Meeting Contract Requirements

Contractor:

Contract Number:

Service Provided:

COR Name:

Date: YES No N/A

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

TE-06_QASP_22 of 70

Comments:

Comments:

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

TE-06_QASP_23 of 70

Attachment 4 – Contract Discrepancy Report, DA FORM 5479

TE-06_QASP_24 of 70

6.

2. 3.

PREPARED ORAL NOTIFICATION RETURNED BY CONTRACTOR ACTION COMPLETE

4. DISCREPANCY OR PROBLEM (Describe in Detail: Include reference in PWS / Directive: Attach continuation sheet if necessary.)

5. SIGNATURE OF CONTRACTING OFFICER

7.

8. CONTRACTOR RESPONSE AS TO CAUSE, CORRECTIVE ACTION AND ACTIONS TO PREVENT RECURRENCE. ATTACH

1. CONTRACT NUMBER

9. SIGNATURE OF CONTRACTOR REPRESENTATIVE 10. DATE

11. GOVERNMENT EVALUATION (Acceptance, partial acceptance, rejection: attach continuation sheet if necessary)

12. GOVERNMENT ACTIONS (Payment deduction, cure notice, show cause, other.)

CONTRACT DISCREPANCY REPORT

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

TO: (Contractor and Manager Name)

DATES

CLOSE OUT

CONTRACTOR

NOTIFIED

NAME AND TITLE SIGNATURE DATE

QAE

CONTRACTING

OFFICER

CONTINUATION SHEET IF NECESSARY. (Cite applicable Q.A. program procedures or new A.W. procedures.)

DA FORM 5479, MAR 2008 APD LC v1.01ES

FROM: (Name of QAE)

TO: (Contracting Officer) FROM: (Contractor)

PREVIOUS EDITIONS ARE OBSOLETE.

TE-06_QASP_25 of 70

Attachment 5 – SAM.gov System Account User Guide

TE-06_QASP_26 of 70

System Account User Guide

Table of Contents

System Account User Guide Overview

Personal API Key Non-Federal System Account Federal System Account

Type of Connections and Rate Limits Interface Specifications Permissions for Data Access Personal API Key

Requesting a Personal API Key Personal API Key Rotations Removing a Personal API Key

Federal System Accounts Accessing the System Account Workspace Requesting a New System Account Review States

Non-Federal System Accounts Requesting a New System Account Review States

Obtaining a System Account Password and API Key Reset System Account Password

Edit a System Account Renew System Accounts

Overview The purpose of this guide is to provide information to users of personal application programming interface (API) keys and users of system accounts. System accounts are for any system that needs to connect to beta.SAM.gov for large data transactions on a repeated basis.

Users who are interested in downloading prepared data extracts do not need to use an API to do so.

Any user can go directly to beta.SAM.gov and initiate a search to view public data.User do need to have an account and be logged into the site to extract or pull formatted data from the site. Data is available

U. S. General Services For more information about the IAE, Administration 1 contact us at iaeoutreach@gsa.gov from the site by searching, then downloading search results, or by using the Data Services link in the menu bar to find downloadable CSV files. The latter option is recommended for those who want complete data sets.

Once logged in, there are multiple ways to access data on the site:

1. Directly from the site:

a. Logged in users will have a Download option to extract data from search results, individual items, or Data Bank reports to their computers.

b. Recommended for specific data needs

c. https://beta.sam.gov

2. Data Services extracts:

a. Scheduled generation of data into downloadable CSV files

b. Recommended for whole data sets

c. https://beta.sam.gov/data-services

Personal API Key A personal API key provides access to one or more Application Programming Interface (APIs to systematically pull detailed information from beta.sam.gov using various searchable parameters.

Personal API keys are recommended if you need to request real-time limited public data through a Representational State Transfer (REST) API service. The benefits of a personal API key include that it:

1. Belongs to you regardless of what organization you work for,

2. Contains your own personal information, and

3. May stay with you even when your role in your organization or the permissions you need to do your job change.

Non-Federal System Account Non-federal system accounts are for systems not managed by the federal government that need to connect via Simple Object Access Protocol (SOAP) or REST API to systematically pull detailed information from beta.sam.gov using various searchable parameters. They are recommended if you are requesting frequent or large amounts of public data through a SOAP or REST API service. A non-federal system account:

1. Represents a particular information technology (IT) system,

2. Is primarily for systems that need to automate the pull of data through extracts or web services, and

i. Is useful if multiple users in your organization need to access the same extract or web service.

U. S. General Services For more information about the IAE, Administration 2 contact us at iaeoutreach@gsa.gov https://beta.sam.gov/data-services https://beta.sam.gov https://beta.sam.gov/data-services

Federal System Account Federal system accounts are for systems managed by the federal government that need to connect via SOAP or REST API to systematically pull detailed information from beta.sam.gov using various searchable parameters. Federal system accounts are the only way to request For Official Use Only (FOUO) or Sensitive data access through a SOAP or REST API service. A federal system account:

1. Can request access to view sensitive data through search or extracts,

2. Represents a particular federal IT system,

3. Is primarily for systems that need to either send data to beta.SAM.gov (such as a contract writing system) or automate the pull of data through extracts or web services, and

4. Is useful if multiple users in your organization need to access the same extract or web service.

5. The specifications for personal API keys and system API calls can be found at https://open.gsa.gov/.

The two main ideas to help you understand which category your system belongs to are the number and type of connection needed.

Type of Connections and Rate Limits Any user can request a personal API key from their profile page. This API key can be used to get, or pull, public data from beta.SAM.gov with a restricted number of requests per day.

If more connections are needed, then you will need to request a system account. This has additional steps and validations to allow for the increased request volume and the data access. If you represent a federal department or independent agency managed system, then you will need to have someone with a federal user account register and follow the steps below under Federal System Accounts or Non-Federal System Accounts.

Connecting Source Type of Connection Default Rate Limit

Non-federal user with no role Personal API key 10 requests/day

Non-federal user with a role Personal API key 1,000 requests/day

Federal User Personal API key 1,000 requests/day

Non-federal system System account API key 1,000 requests/day

Federal system System account API key 10,000 requests/day

Only one active API key is allowed per account.

U. S. General Services For more information about the IAE, Administration 3 contact us at iaeoutreach@gsa.gov https://open.gsa.gov/

Interface Specifications All request and response details for the REST and SOAP APIs are documented on open.gsa.gov. Before requesting a system account, please review the specifications and requirements for any connection you wish to pursue, including access controls, send and response parameters, format, and any specific system requirements.

Permissions for Data Access If you determine that you need a system account, you will need to establish what data you have a business need to access and what actions you will be completing.

If you are just pulling data or using GET calls, then you will only need read permissions to the data. If you are writing, sending, or using POST and PUT calls, then you will need write permissions. Only federal accounts can access For Official Use Only (FOUO) or Sensitive data permissions, and only federal accounts are allowed to write data.

Non-federal users can only select the public read permissions when submitting a system account request.

The domains (data sets) and the permissions allowed within that domain are:

1. Contract Opportunities

a. Permission: Read Public

i. Definition: Users already have access to view the public Contract Opportunity data on the site. This permission grants access to the public APIs for active and inactive contract opportunity notices.

b. Permission: Read Sensitive

i. Definition: This grants access for a system to obtain a read-only copy of all contract opportunities data for an organization in the federal hierarchy, to include published active and inactive notices, dra� notices, and any sensitive but unclassified attachments. The system request must detail the business need for this level of access specific to accessing controlled but unclassified documentation that has been uploaded.

c. Permission: Write Public

i. Definition: This grants access for a contracting office system to write

(submit/post) contract opportunities data for a federal hierarchy organization to include published active and inactive notices and dra� notices while excluding any sensitive but unclassified attachments. The system request must detail the business need for this level of access to post pre- or post-award contract actions, and must specify the contracting office(s).

d. Permission: Write Sensitive

U. S. General Services For more information about the IAE, Administration 4 contact us at iaeoutreach@gsa.gov

i. Definition: This grants access for a contracting office system to write (submit/post) contract opportunities data for a federal hierarchy organization to include published active and inactive notices, dra� notices, and sensitive but unclassified attachments. The system request must detail the business need for this level of access to post pre- or post-award contract actions with controlled but unclassified documentation, and must specify the contracting office(s).

2. Contract Award Data (Coming Soon)

a. Note: Contract award data is still authoritative in FPDS.gov, and is not yet available in beta.SAM.gov.

3. Entity Information

a. Permission: Read Public

i. Definition: Users already have access to view the public entity registration and exclusion data on the site. This permission grants access to APIs for public entity registration and exclusions data only.

b. Permission: Read FOUO

i. Definition: Federal government users already have access to view FOUO information on the website when they log in using their federal government user account. This role additionally grants a federal government system access to FOUO information in the SAM FOUO extracts and APIs. FOUO information includes all public data plus non-public entity registrations, FOUO points of contact, Dun and Bradstreet (D&B linkage, D&B monitoring, and size metrics.

The system request must detail the business need for this level of access to FOUO data.

c. Permission: Read Sensitive

i. Definition: This role grants the federal government user access to sensitive registrant information using the SAM.gov website, extracts, and web services.

Sensitive information includes all FOUO information plus the banking information for Electronic Funds Transfer (EFT) and TIN. The system request must detail the type of system (financial or contract writing), the business need to specifically view sensitive entity data, and the business need to access TIN data or EFT actions.

4. Federal Hierarchy

a. Permission: Read Public Only

i. Definition: Users already have access to view the public federal hierarchy data on the site. This permission grants access to the public APIs for active department and sub-tier federal hierarchy data only.

b. Permission: Read FOUO

Administration 5 contact us at iaeoutreach@gsa.gov

i. Definition: Federal government users already have access to view FOUO information on the website for their federal organization when they log in using their federal government user account. This permission additionally grants the federal government user access to FOUO information in the federal hierarchy API. FOUO information includes all public data plus the department through office-level data and full hierarchy lookups of active and inactive data, which includes both public and FOUO data. inactive notices, dra� notices, and sensitive but unclassified attachments. The system request must detail the business need for this level of access to FOUO data.

5. Assistance Listings

a. Permission: Read Public

i. Definition:This grants access to the public API for active published assistance listings public data and the historical index for archived assistance listings.

6. Wage Determinations

a. Permission: Read Public

i. Definition: Users already have access to view the public wage determinations data on the site. This permission grants access to the public APIs for active published and inactive wage determinations Service Contract Act (SCA) and Davis-Bacon Act (DBA) public data only.

7. Reference Data

a. Permission: Read Public

i. Definition: This grants access to the public APIs for location services which shall only be used to validate data before sending contract opportunities to the site for fields such as the state, city, zip, and country.

Personal API Key A personal API key is used for either a non-federal or a federal user to access small amounts of data as needed by a single user account. If larger amounts of data are needed, access to non-public data is needed, or multiple users need access to the same API key or access point, then please see the Federal System Accounts sections of this user guide. If you will only be using data through the website interface or through an agency system, then you do not need an API key.

Requesting a Personal API Key

1. Sign into the site.

2. Navigate to your profile page from the user profile icon located in the header of any page.

Administration 6 contact us at iaeoutreach@gsa.gov

3. Navigate to the section titled Public API Key.

4. Select Request API Key if you have determined you will need an API key.

5. You now have access to the API key.

6. The API key will be hidden when you navigate to this page in the future and, to display the key, you will need to click on the eye icon and enter a one-time password (which will be emailed to you) to view the key.

a. For security purposes, this field is concealed with an additional step to reveal it.

b. The one-time password will be sent to the email for the profile you are requesting the

API key for.

c. Enter this code into the Enter One-time Password field and submit any time you wish to see the API key.

Administration 7 contact us at iaeoutreach@gsa.gov

7. You can now use this API key to complete a limited number of calls through the site interface connections as documented on open.gsa.gov.

a. As a non-federal user, you will have access to public data only. As a federal user, you will have access to both public and FOUO data.

Personal API Key Rotations API keys expire every 90 days. You will receive email notifications beginning 15 days prior to the expiration of the API key. A backup API key is generated on the 75th day. Both the backup and primary key will work during the 15-day window before expiration and will be available on the System Accounts detail page. The primary key will expire a�er this 15-day window and the backup key will become the primary key at that point.

Removing a Personal API Key

1. If you just requested an API key, you will not be able to remove it for 24 hours. This is a security protocol.

U. S. General Services For more information about the IAE, Administration 8 contact us at iaeoutreach@gsa.gov

2. A�er the time limit expires, from the Public API Key section of your profile page, you can select Remove API Key.

3. You will need to verify through a popup that you want to remove the API key.

a. When Yes, remove API key is selected, the API key is deactivated and can no longer be used for connecting to the site.

b. When No, keep API key is selected, the popup will be dismissed and the API key will continue to be available.

Administration 9 contact us at iaeoutreach@gsa.gov

Federal System Accounts A federal system account is for a system managed by a federal department or independent agency. As federal systems are allowed to request access to non-public data, there are additional access controls and security approvals needed that are integrated automatically into the request process.

Accessing the System Account Workspace The first step to requesting a system account is to register as a federal user. To do so, simply select Sign in on the header of any page, and complete the registration with your federal government email address. A�er you complete registration, you will have access to a “workspace” where you, as a user, can manage specific data or items. Each workspace is tailored to the user based on roles, permissions, and personal preferences.

Each service has a specific area of the workspace that allows a user full management of the related items. As a federal user, you will need to be granted a system account role. These can only be granted by the agency Integrated Award Environment (IAE) Change Control Board (CCB) member or another system account administrator at your agency. If you need assistance identifying your CCB member or a system account administrator, please contact the Federal Service Desk.

The two possible roles are:

● System Account Administrator: The system account administrator role allows you to submit a request for a system account to the General Services Administration (GSA) for approval. It also allows you to assign and approve roles for other people who will be managing your systems.

● System Account Manager: The system account manager role allows you to edit systems that you are responsible for. It allows you to create requests for system accounts, which are sent to your agency system administrator for approval before being sent to GSA for approval.

Once you have a system account administrator or system account manager role, follow these steps:

1. A�er you have logged in, navigate to your main workspace from the header on any page.

2. Select System Accounts from the widgets to go to your detailed system accounts view.

U. S. General Services For more information about the IAE, Administration 10 contact us at iaeoutreach@gsa.gov https://www.fsd.gov/

3. This page is known as your “tier 2 workspace” for system accounts.