ATTACHMENT 2_DRAFT_ACC-ORL_QASP_OneSAF_1_SEP_23.docx

Quality Assurance Surveillance Plan

For

One Semi-Automated Forces (OneSAF)

Contract # W900KK-XX-X-XXXX

29 August 2023

ACC-ORLANDO PEO STRI/PM SE/PD CSS

Controlled by: Army Controlled by: ACC-ORL CUI Category: General Procurement and Acquisition Distribution/Limited Dissemination Control: FEDCON

POC: PAQA QA

TABLE OF CONTENTS

Subject Page Number

1. Overview

2. Description of Services

3. Roles and Responsibilities

4. Contract Quality Requirements

5. Government Surveillance

6. Non-Conforming Performance

7. Deduct Plan

8. Data Analysis

9. Acceptance of Services

10. COR Status Report

11. Service Contract Reporting (SCR) in the System for Award Management (SAM)

12. Contractor Performance Assessment Reporting System (CPARS)

13. Combating Trafficking In Persons

14. COR/Quality Assurance Surveillance Files

15. QASP Changes

1. Overview.

1.0 Purpose. This Quality Assurance Surveillance Plan (QASP) is a government developed document used to ensure that the Government receives quality services and pays only for conforming services actually provided. The objective of this Indefinite Delivery Indefinite Quantity (IDIQ) contract is to acquire design, development, integration, testing, customer support, and sustainment of the OneSAF Product Line as defined in this Performance Work Statement (PWS), section 3.0 Requirements. Government-furnished property and services for those items specified in the PWS are exempt from this QASP. The Contractor shall perform to the standards specified in the OneSAF Production and Support IDIQ PWS. This QASP identifies the methods and procedures the Government will use to ensure it receives the services to the desired standard, as identified in the PWS.

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

1) Ensure Contractor performance meets or exceeds contract terms, conditions and specifications

2) Hold the Contractor accountable for quality control

3) Encourage the Contractor to take appropriate steps to control and improve quality

4) Ensure all sections of FAR 46 are applied as required and applicable

Accordingly, the Government will perform surveillance on the contract in accordance with this QASP, but reserves the right to monitor the contract in any manner necessary, at any time necessary, and at all places necessary to ensure that the services rendered conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level, and at the contractor's place of business. Sub-contract service providers shall be accountable to the Contractor who, in turn is responsible to the Government. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor. The Government will not exercise any supervisory controls over the contract service providers performing the services herein.

2. Description of Services.

2.1. Scope of Work. The contractor shall provide the capabilities needed to execute the overarching OneSAF program requirements for development, test, integration, interoperability, support, and delivery of software, data, and documentation products to the Assistant Program Manager OneSAF (APM OneSAF); the U.S. Army Modeling and Simulation (M&S) Communities (Acquisition, Analysis, Experimentation, Intelligence, Test and Evaluation, and Training); and the rest of the OneSAF user community. The OneSAF user community includes, without limitation, other U.S. Army Program Executive Offices (PEOs) and Program Managers (PMs), Training and Doctrine Command (TRADOC) Battle Labs, Research Development and Engineering Centers (RDECs) and agencies, other Department of Defense Services and Joint agencies, Government civilian organizations and agencies, academic institutions, foreign countries, and other OneSAF Co-Developers. OneSAF supports force modernization and transformation from weapons systems to brigade. OneSAF supports the Army goal of cloud and web-based software application development in order to reduce hardware and support costs and to enable rapid training at both home station and distributed locations.

OneSAF is a software product line consisting of a set of interacting components where multiple components utilize common services to satisfy a diverse set of OneSAF use cases. The OneSAF Product Line Architecture Specification (PLAS) defines the system compositions, products, and components within the OneSAF product line. The PLAS defines and describes the overall architecture that governs the products and components within the OneSAF product line and illustrates how the product line can be used to construct systems that meet the OneSAF requirements.

The OneSAF Production & Support effort consists of conceptual modeling, architectural, engineering, and software development support required to enhance the OneSAF product line and correct deficiencies identified by the OneSAF Community. With Government concurrence, the OneSAF effort also includes accepting, modifying, integrating, and testing handover packages and new capabilities in support of the requirements and the OneSAF user community. The effort provides life-cycle sustainment of the released versions. This life-cycle sustainment involves addressing maintenance updates, Problem Ticket Reports (PTRs), and security patches. The effort also entails on-site and remote support and training for the worldwide OneSAF Community. The effort includes final acceptance and test activities required to deliver the annual and tailored version releases and patches to support OneSAF Community requirements.

2.2. Type of Contract. It is envisioned that OneSAF will be awarded as a Single-Award ID/IQ contract where a Firm Fixed-Price (FFP) contract type with complex and hard to define service requirement Cost type CLINs will be employed under TOs based on the individual requirement being satisfied and degree of risk assumption in the pricing method. While the majority of the effort will be satisfied for lower risk solutions that are supported under a FFP approach, there may be varying instances of complex and high-risk developmental requirements that may be satisfied under Cost Reimbursement pricing.

3. Roles and Responsibilities. The following provides a synopsis for the roles and their respective authority during the performance of the contract:

3.1. Government.

3.1.1. Contracting Officer (KO). The KO is the only person authorized to direct changes in any of the requirements under this contract. In the event the Contractor effects any such change at the direction of any person other than the KO, the change will be considered to have been made without authority, and solely at the risk of the Contractor. No changes in, or deviation from the terms and conditions shall be affected, without a written modification to the contract, executed by the KO authorizing such changes.

3.1.2. Contract Specialist (KS) - The KS acts as an acquisition consultant and serves as liaison between KO and the OneSAF program management office and the Contracting Officer’s Representative (COR).

3.1.3. Contracting Officer’s Representative (COR). The COR will monitor all technical and performance aspects of the contract, and assist the (KO) in contract administration. The COR is authorized to perform the following functions:

· Assure that the Contractor performs the technical requirements of the contract

· Perform inspections necessary in connection with contract performance

· Maintain written and oral communications with the Contractor concerning technical and performance aspects of the contract

· Issue written interpretations of technical requirements, including Government drawings, designs, and specifications

· Monitor Contractor's performance and documents and notifies both the Contracting Officer and Contractor of all deficiencies

· Coordinate availability of Government furnished property

· Provide site entry of Contractor

Army Contract Command (ACC) doesn’t use other acronyms to refer to and describe a COR. Terms such as the “COTR, “Onsite COR”, “TM”, etc. will not be used. Some personnel may be assigned as Alternate CORs (ACOR), but other than a statement to that effect and what actions the KO expects that ACOR to take in the absence of the primary COR, there is no difference between a COR an Alternate COR, or other government surveillance personnel assigned to conduct contract oversight. Throughout the remainder of this QASP. The term “COR’ will be used to refer to all government surveillance personnel assigned to monitor the contractor’s performance on this contract.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost, price, or delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

The Contracting Officer shall use the DoD Joint Appointment Module (JAM) to electronically track COR nominations, appointments, terminations, and training certifications for each COR appointed to conduct oversight on this contract. The COR will upload their surveillance documents, such as COR Status Reports (CSR) COR trip reports, correspondence with the contractor, and other miscellaneous documents into the Surveillance and Performance Monitoring (SPM) module within the online contract file. JAM and SPM are available within the Procurement Integrated Enterprise Environment (PIEE) suite of tools at: https://piee.eb.mil/.

3.1.2.1 Alternate Contracting Officer’s Representative (ACOR). The Alternate COR is an employee of the U.S. Government provided by the Requiring Activities (RA) and appointed by the Contracting Officer to provide additional surveillance personnel in monitoring and documenting the contractor’s performance. These alternate surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance, if they meet all COR training and experience requirements and are appointed by the contracting officer as ACOR in the JAM. This term will apply to other government surveillance personnel as defined in Army Regulation 70-13, paragraph 2-2 g.

3.2. Contractor.

3.2.1. Program Manager. The Contractor responsible for running the program. May supervise the program team and manages conflicts within different departments. Plans and sets program goals and milestones and develops risk management strategies. Defines resources and schedules for the implementation of the program. Clearly defines requirements and sets targets accordingly. Recognizes areas for internal improvement and develops plans for implementing the improvements.

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

Government Personnel:

Table 1 - Key Positions for Contract Administration

Contractor Personnel:

4. Contract Quality Requirements.

4.1. Government Quality Assurance. This QASP describes what the Government will do to ensure that the Contractor has performed in accordance with the performance standards within the PWS.

This QASP describes:

· How the performance standards will be applied:

· The Performance Standard for each requirement in the PWS will be applied as prescribed in the PWS. Ensure that each Performance requirement within the PWS includes a Measurable performance standard in terms of quality, timeliness, or quantity.

· Ensure the method of assessing contractor performance against performance standards is included in this QASP

· Ensure each Performance Requirement includes an acceptable quality limit (AQL). AQL is the worst tolerable performance that is still considered acceptable.

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

· All performance activities will be surveilled through-out the Period of Performance, using a risk-based approach. The selected items will be populated on the Monthly Checklist and placed on the Surveillance Schedule for each period surveilled.

· When the surveillance will be scheduled (Surveillance Schedule, Attachment 3)

· Selected items for each month will be placed on the Surveillance Checklist and scheduled surveillance on the Monthly Schedule. Surveillance may be scheduled on a daily, weekly or monthly frequency. However, each contractor requirement must be audited for compliance prior to invoice payment being made. The COR can utilize the Surveillance Checklist and Surveillance Schedule Smart Forms in the SPM Module in place of the Surveillance Checklist in Attachment 4 and Surveillance Schedule in Attachment 3.

· The Acceptable Quality Limit (AQL)

· The AQL will be determined by the Requiring Activity, i.e., the COR.

Table 2 - Surveillance Schedule

• Annual Past Performance report

• Manage Risk

• Annual Past Performance report

• Process Reports and Data

• Customer feedback

• Option Exercise

• Reports and Data

• Participation in Peer Reviews

• Customer feedback

• Annual Past Performance report

• Active participation in Testing snd Customer feedback

• Option Exercise

• Test Status Reports and Data

• Customer feedback

• Annual Past Performance report

• Data (IAVAs, STIG compliance)

• Annual Past Performance report

• Inspection Reports and Customer feedback

· The nature of Government contract quality assurance actions that include the number of observations made and the number and type of defects (defect rate)

· Personnel conducting contractor performance surveillance will use Attachment 4, Surveillance Checklist, or equivalent to answer the Performance question asked, and provide comments in the area provided on the checklist. These comments and metrics from the Checklist will be included on each CSR submitted during the Period of Performance.

5. Government Surveillance.

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

NOTE: The performance items selected for surveillance in this QASP as a minimum should contain those listed in the Performance Requirements Summary (PRS). The PRS is a stand-alone document that illustrates to the contractor the few, most salient items the government wishes the contractor to be aware of. The PRS is contained in the contract Performance Work Statement (PWS). See Attachment 1 for PRS items.

1. 100% Inspection will be reserved for the highest risk areas where consequence of failure may affect life or limb, or there is likelihood of mission failure

1. Random Sampling Will be used when a service is performed on a frequent basis and a statistically valid sample can be selected for audit. This is most appropriate method for frequently recurring tasks

1. Periodic Inspection Will be used when planned sampling of a service is at a specific predetermined date and time. This is most appropriate for tasks that occur infrequently, yet on a scheduled basis

1. Customer Feedback. Not a valid method of surveillance, but a good indicator of areas where surveillance should be conducted or intensified.

The Customer Complaint Record, Attachment 2, will be placed at convenient locations for the end user of these services, and made available to document/record all complaints. The COR will collect the Customer Complaints each surveillance cycle and investigate for validity ASAP.

The following procedures will be followed when a complaint is received.

1. The COR/ACOR will investigate to determine the validity of the complaint

2. If the complaint is determined to be invalid, the COR will inform the person who submitted the complaint of the reason(s) as soon as practical

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

4. A Customer Complaint Log will be used to document each validated customer complaint and attached to the COR Monthly Surveillance Report in the SPM module

5.1.1 Surveillance Procedure:

a. Report driven deliverables: The COR will perform evaluations/validation of contractor supplied performance data.

1. The COR will review the Contractor supplied reports (Contractor’s Progress, Status, and Management Report (CPSMR), Process Report, etc.), that are to include but not limited to a status summary and key milestones and progress for the current period and planned for the next period. The COR will also review the Confluence PM Dashboard and OneSAF IPT slides. These reports and several other sources of information will be used to create the COR monthly report in the SPM module, see Table 3.

Table 3 - PRS

b. Use of ACORs: Their role in surveillance activities and ACOR documentation requirements

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

5.2. Surveillance Schedule. (Required) A Surveillance Schedule (Attachment 3) will be created each month. Locally generated equivalent is acceptable. The schedule is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Schedule will be completed at the beginning of each month during the Period of Performance (PoP) to schedule the upcoming month surveillance activity. Completed Surveillance Schedules will be filed in the online SPM module located within (https://piee.eb.mil) file for this contract, either as an attachment to COR Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

5.3. Surveillance Checklists. (Required) A Surveillance Checklist (Attachment 4) will be created each month. Locally generated equivalent is acceptable. The Checklist is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Checklist will be completed with the Surveillance Schedule. Completed Surveillance Checklist will be filed in the online SPM module located within (https://piee.eb.mil) file for this contract, either as an attachment to COR Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

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

5.4. Surveillance Documentation. Each months’ Completed Surveillance Documentation, to include the COR Status Report must be filed in the online SPM module located within (https://piee.eb.mil) file for this contract. The COR Status Report (Smart Form) must be utilized, supporting documentation can be uploaded as an attachment.

6. Non-Conforming Performance. A Non-conformance occurs when the Contractor fails to meet the terms, conditions and/or specifications of the Contract/Task Order. All instances of non-conformance must be documented by the COR. The COR will provide the details of the non-conformance to the KO, who will notify the Contractor of each nonconformance occurrence, unless the KO has authorized the COR to submit directly to the contractor, and copy the KO. Resolution of any non-conformance discovered at the Subcontractor level will be addressed with the prime Contractor. Non-conformances are classified as either Marginal or Unsatisfactory.

6.1. Marginal. Marginal performance does not meet some contractual requirements. The contractual performance of the element or sub-element being assessed reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor's proposed actions appear only marginally effective or were not fully implemented. 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).

6.2. Unsatisfactory. Unsatisfactory performance does not meet most contractual Requirements and recovery is not likely in a timely manner. The contractual performance of the element or subelement contains a serious problem(s) for which the contractor's corrective actions appear or were ineffective. 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).

6.3. Tracking and Resolving Non-Conforming Performance . All non-conforming performance, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track non-conforming performance to ensure the Contractor identifies and takes appropriate corrective action to the root cause and the specific non-conformance is corrected within the required timeline. The KO will make a final written determination of the Government’s remedies if the non-conformance is not corrected by the Contractor after receiving notice and a reasonable opportunity to correct the work.

7. Deduct Plan. This acquisition does not include a Deduct Plan.

8. Data Analysis. Data Analysis will be performed to identify trends in cost, schedule and/or performance risks. The results of Data Analysis will be documented in COR Status Report and may be used to make adjustments to surveillance schedules and/or checklist items to increase or decrease surveillance, based on performance trends. Negative trends noted using Government data/observations could result in issuing the Contractor Nonconformance Report. Trends noted using Contractor data will not result in a NCR unless the Contractor has not addressed the negative trend. QASP changes based on Data Analysis will be coordinated with the Contracting Officer for approval.

9. Acceptance of Services. When all services have been deemed acceptable and there is documented, objective, quality evidence to support acceptable performance, the COR will accept the services provided and authorize payment to the Contractor. Acceptance and payment will be made by approving the Contractor’s Receiving Reports in Wide Area Workflow at https://piee.eb.mil/ as a WAWF Inspector, and/or Acceptor.

10. COR Status Report. COR Status Reports (CSR) will be submitted on a monthly basis to the Contracting Officer via the SPM module. CSRs must be uploaded into the SPM module using the “Smart Form”. CSRs will be due NLT the 10th day of the month following the month of surveillance. CSRs will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis must contain a summary of surveillances performed, Customer Feedback if any, NCRs if any, an analysis of the Contractors performance, recommended adjustments to surveillance schedules, and any other pertinent contract information IAW FAR 46.104, and the COR Appointment Letter. Completed Surveillance Checklists and NCRs, if any, will be included as attachments to COR Status Reports. See para 5.4.

11. Service Contract Reporting (SCR) in the System for Award Management (SAM). https://www.sam.gov. Reporting Labor Hours. The Office of the Secretary of Defense (OSD) memorandum, “Revised Department of Defense Contractor Manpower Reporting Initiative,” dated October 16, 2019, provides new implementing direction for contractor reporting of manpower data with regard to the performance of DoD services contracts consistent with the requirements of title 10, U.S.C, section 235 and 2330a, as amended. The system allows industry to report all manpower data into a single Federal-wide portal. For Contractors who meet the SCR reporting thresholds (in excess of $3 million), your entity must be registered in SAM, and the user responsible for reporting must have an individual user account in the system and the Service Contract Inventory (SCI) Reporter user role to access reporting functionality.

SCI Reporters are required to enter the following information:

· Total Amount Invoiced: Total dollar amount invoiced for services performed during the previous Government fiscal year under the contract (this amount should include the prime and any subcontract amount).

· Prime Contractor Hours Expended: Prime contractor direct labor hours expended on the services performed during the previous Government fiscal year. The amount you enter is automatically divided by 2,080 hours to calculate a Full Time Employee (FTE) equivalent, displayed under the Prime Contractor Hours Expended as Prime Contractor FTEs.

· Report any required Tier 1 subcontractor information.

Contractor reporting is required annually, by October 31, on the services performed under the contract or order, including any subcontracts, during the preceding Government fiscal year (October 1-September 30). Contracting officers shall ensure that the requirement to report contractor manpower is included in all contracts, task/delivery orders and modifications.

12. Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (COR Status Reports, Completed Surveillance Checklists, Customer Feedback and CDRs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information.

13. Combating Trafficking In Persons (CTIP). In accordance with PGI 222.17 and FAR 52.222-50, the KO will be notified immediately of any information from any source that alleges a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

14. COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance Files will be maintained in the on-line JAM and SPM module IAW DoDI 5000.72, and DFARS PGI 201.602-2.

15. QASP Changes. This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications by the KO, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

COR’S Signature Block Date:

Contracting Officer’s Signature Block Date:

DOCUMENT REVISION HISTORY

This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

Attachments:

1. Performance Requirements Summary (PRS) – DA Form 5473

2. Customer Complaint Record - DA Form 5477

3. Surveillance Schedule

4. Surveillance Checklist

5. Non-conformance Report (NCR) – DA Form 5479

Attachment 1

Contract/Task Order Performance Requirements Summary

(PRS)

Attachment 2 Customer Complaint Record

Attachment 3 Surveillance Schedule

• Annual Past Performance report

• Manage Risk

• Annual Past Performance report

• Process Reports and Data

• Customer feedback

• Option Exercise

• Reports and Data

• Participation in Peer Reviews

• Customer feedback

• Annual Past Performance report

• Active participation in Testing snd Customer feedback

• Option Exercise

• Test Status Reports and Data

• Customer feedback

• Annual Past Performance report

• Data (IAVAs, STIG compliance)

• Annual Past Performance report

• Inspection Reports and Customer feedback

Attachment 4 Surveillance Checklist(s)

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

Attachment 5 Nonconformance Report (NCR) image1.png image2.png image3.emf

DA 5473 PRS .pdf

PERFORMANCE REQUIREMENTS SUMMARY

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

REQUIRED

SERVICE

PARAGRAPH

NUMBER STANDARD

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM REQUIREMENT (AQL)

METHOD OF

SURVEILLANCE

THE PROPORTION

OF REQUIRED

SERVICE TO TOTAL

CONTRACT PRICE

DA FORM 5473, MAR 2008 APD LC v1.00PREVIOUS EDITIONS ARE OBSOLETE.

PERFORMANCE REQUIREMENTS SUMMARY

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

REQUIRED

SERVICE

PARAGRAPH

NUMBER

STANDARD

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM REQUIREMENT (AQL)

METHOD OF

SURVEILLANCE

THE PROPORTION

OF REQUIRED

SERVICE TO TOTAL

CONTRACT PRICE

DA FORM 5473, MAR 2008

APD LC v1.00

PREVIOUS EDITIONS ARE OBSOLETE.

1.00

DA FORM 5473-R, NOV 1985

PERFORMANCE REQUIREMENTS SUMMARY

APD

REQ_SERV:

REQ_SERV_1:

REQ_SERV_2:

REQ_SERV_3:

REQ_SERV_4:

REQ_SERV_5:

REQ_SERV_6:

REQ_SERV_7:

REQ_SERV_8:

REQ_SERV_9:

REQ_SERV_10:

PARAGRAF:

PARAGRAF_1:

PARAGRAF_2:

PARAGRAF_3:

PARAGRAF_4:

PARAGRAF_5:

PARAGRAF_6:

PARAGRAF_7:

PARAGRAF_8:

PARAGRAF_9:

PARAGRAF_10:

STANDARD:

STANDARD_1:

STANDARD_2:

STANDARD_3:

STANDARD_4:

STANDARD_5:

STANDARD_6:

STANDARD_7:

STANDARD_8:

STANDARD_9:

STANDARD_10:

AQL:

AQL_1:

AQL_2:

AQL_3:

AQL_4:

AQL_5:

AQL_6:

AQL_7:

AQL_8:

AQL_9:

AQL_10:

METHOD:

METHOD_1:

METHOD_2:

METHOD_3:

METHOD_4:

METHOD_5:

METHOD_6:

METHOD_7:

METHOD_8:

METHOD_9:

METHOD_10:

PROPORTN:

PROPORTN_1:

PROPORTN_2:

PROPORTN_3:

PROPORTN_4:

PROPORTN_5:

PROPORTN_6:

PROPORTN_7:

PROPORTN_8:

PROPORTN_9:

PROPORTN_10:

image4.emf

ACC_ORL_Customer Compliant Record.pdf

Army Contracting Command Orlando (ACC-ORL)

CUSTOMER COMPLAINT RECORD

DATE OF COMPLAINT TIME OF COMPLAINT

SOURCE OF COMPLAINT

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

INDIVIDUAL (Include name and contact information)

NATURE OF COMPLAINT

CONTRACT NUMBER & REQUIREMENT REFERENCE

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

Complaint IS NOT Valid

DATE / TIME CONTRACTOR INFORMED OF COMPLAINT CONTRACTOR NAME RECEIVING COMPLAINT

ACTION TAKEN BY CONTRACTOR

RECEIVED AND VALIDATED BY

Copy provided for filing (COR) DATE:

Customer Follow-up DATE:

TIME OF COMPLAINT:

NATURE OF COMPLAINT:

CONTRACT NUMBER REQUIREMENT REFERENCE:

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

Complaint IS Valid notify contractor: Off

Complaint IS NOT Valid: Off

DATE TIME CONTRACTOR INFORMED OF COMPLAINT:

CONTRACTOR NAME RECEIVING COMPLAINT:

ACTION TAKEN BY CONTRACTOR:

RECEIVED AND VALIDATED BY:

Copy provided for filing COR DATE Customer Followup DATE:

undefined: Off undefined_2: Off

Date1_af_date:

Organization:

Individual:

Date4_af_date:

Date5_af_date:

image5.emf image6.emf

Surveillance Checklist.xlsx Surv ChkList

ACC-ORL COR SURVEILLANCE CHECKLIST Template

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

Contractor: From:

Contract Number: To:

Service Provided: Meeting Contract Requirements ?

COR Name:

Date:

Select answer in cloumn C or D YES No

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

Comments:

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

To populate the checklist, find in the PWS: "The Contractor Shall..." , Then, make that requirement a checklist item by converting the requirement to a question: " Did the contractor…" Each "Yes" can be graded as a 1, and each NO graded as a 0, for example.

From this, the COR may generate a quantifiable performance rating using numbers.

List of Perf Parameters

Surveillance Checklist Questions for QASP

1. Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform grounds maintenance

2. Contractor shall perform to the standards of this PWS.

3. Contractor shall ensure all work accomplished maintains and presents a healthy, clean, neat, and professional appearance to all grounds included and covered by this contract in support of mission requirements for users, residents, and visitors to the installation (in accordance with DA PAM 420-1-1, Housing Management, Table 2-14, 4.Contractor shall maintain Improved, Semi-Improved, and Unimproved Grounds as identified under Technical Exhibit (TE) {X, X, X Insert Installation TEs}, in this PWS, utilizing accepted industry standards and practices, where practical.

5. Contractor shall include mowing grass, edging and trimming grass, removing grass trimmings from paved areas, irrigating, aerating lawn areas, applying fertilizer and/or lime, applying herbicide to lawn and landscape areas, maintaining plants, shrubs, and flowers, performing seasonal planting of plants and flowers, removing leaves, applying mulch, pruning trees, removing grass from cracks in sidewalks and pavements, and litter control.

6. Semi-Improved Areas. These areas are used for operational and maintenance purposes. Erosion control shall be the predominant grounds maintenance work performed in this area by the Contractor. This will include grassed areas, vegetated areas, trees, and pavements. The work performed in these areas by the Contractor shall include mowing grass

7. Contractor shall provide personnel support outside the normal hours of operation as required, including holidays, to support the Directorate of Public Works (DPW) Maintenance Division mission.

8. Prior to performance of services outside the locally established hours of operation, the Contractor shall request and obtain, in writing, approval from the Contracting Officer.

9. The Program/Project Manager or the alternate Project Manager shall be available after normal duty hours to serve as the central point of contact for contractor operations.

10. Contractor personnel shall not be scheduled for overtime work.

11. Contractor shall make available competent personnel trained and capable of dealing with minor personnel injuries.

12. The Contractor or their employees shall immediately notify their supervisor of any accident requiring emergency medical treatment. The Contractor will, in turn, notify the Contracting Officer (KO) or Contracting Officer’s Representative (COR) within two (2) hours of the incident.

13. The Contractor shall attend the post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation (FAR) Subpart 42.5.

14. The KO and Contracting Officer’s Representative (COR) shall meet periodically with the Contractor to review the Contractor's performance. Written minutes of such meetings will be recorded by the Government and signed by the Program/Project Manager and the Contracting Officer or COR and distributed within five (5) workdays after the meeting.

15. The Contractor may request a meeting with the Contracting Officer or COR when the Contractor believes such a meeting is necessary.

16. Written minutes of such meetings shall be recorded by the Contractor and signed all participants involved and distributed within five (5) workdays after the meeting. In either case, if the Contractor does not concur with any portion of the minutes, recorded by the Government or the Contractor, such non-concurrence shall be provided in writing to the Contracting Officer within two (2) calendar days following receipt of the minutes.

17. Communications pertaining to contractual administrative matters shall be addressed to the KO.

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

19. The Contractor shall not in any way represent that it is a part of the U. S. Government, or that it has the authority to contract or procure supplies for the account of the United States of America.

20. The Contractor shall develop and maintain a Quality Control Plan acceptable to the Government

21. The Contractor shall develop and implement procedures to identify, prevent, and ensure against recurrence of defective services

22. Contractor shall submit resumes and an organization chart (to include contact info) for initial key personnel and replacements, to the KO.

23. The Contractor shall provide a Program/Project Manager who shall be responsible for the performance of the work. The name of this person and an alternate, who shall act for the Contractor when the manager is absent, shall be designated in writing to the Contracting Officer.

24. The Program/Project Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract.

25. The Program/Project Manager or alternate shall be available between {Insert the hours, i.e., 8:00 a.m. to 4:30p.m.}, Monday through Friday except Federal holidays or when the Government facility is closed for administrative reasons.

26. All contract personnel shall be identified as a Contractor, i.e., badge, company logo, or uniform.

27. Contractor personnel’s conduct shall not reflect discredit upon the Government.

28. The Contractor shall ensure that personnel present a professional appearance.

29. The Contractor’s employees shall observe and comply with all local policies and procedures concerning fire, safety, environmental protection, sanitation, security, and possession of firearms or other lethal or illegal weapons or substance.

30. The Contractor is responsible for ensuring that any Contractor employees providing services under this contract conduct themselves and perform services in a professional, safe, and responsible manner.

31. The Contractor shall remove, from the job site, any employee for reasons of misconduct or security. In accordance with Department of Defense (DOD) Directive 5500.7-R, “Joint Ethics Regulation”, Contractor employees must avoid improperly influenced in the execution of their duties under the contract. Particular attention should be paid to acceptance of gifts/ gratuities, and on non-disclosure of sensitive or classified information.

32. The Contractor shall ensure employee conduct complies with 41 U.S.C. 423 relative to release of acquisition related information or actions or discussions which may prejudice future competitions.

33. The Contractor shall ensure no Contractor employees conduct political related activities or events on the installation.

34. The Contractor shall successfully integrate and coordinate all activity needed to execute the requirement.

35. The Contractor shall manage the timeliness, completeness and quality of problem identification to a degree acceptable to the Government.

36. The Contractor shall provide corrective action plans, timely identification of issues and effective management of subcontractors.

37. The Contractor shall assure customer satisfaction and professional and ethical behavior of all Contractor personnel

38. Contractor and all associated subcontractors’ employees shall comply with applicable installation, facility, and area commander installation/facility access and local security policies and procedures (provided by Government representative).

39. The Contractor shall also provide all information required for background checks to meet installation access requirements, to be accomplished by the installation Provost Marshall Office, Director of Emergency Services, or Security Office, and COR.

40. The Contractor shall safeguard all Government equipment, information and property provided for Contractor use.

41. The Contractor shall maintain a physical security checklist/log (e.g., Army Standard Form (SF) 701 Activity Security Checklist), which will be forwarded to the COR, not later than (NLT) the 10th of each month, following the month of surveillance.

42. At the close of each work period, Government facilities, equipment, and materials shall be secured by the Contractor.)

43. The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated.

44. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas.

45. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the COR.

46. Lost keys shall immediately be reported to the COR, by personal contact via phone and be followed up by written correspondence.

47. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying.

48. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor.

49. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

50. The Contractor shall prohibit the use of Government issued keys by any persons other than the Contractor’s employees.

51. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer (KO).

52. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons.

53. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

54. The Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity Anti-Terrorism Officer (ATO)). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR.

55. This training shall be completed within {XX} calendar days (recommend 30) of contract award and within {YY} calendar days (recommend five (5)) of new employees commencing performance with the results reported to the COR not later than {XX} calendar days (recommend 30) after contract award.

56. The Contractor shall safeguard and maintain all Government property and Contractor property, as well as provide for the safety and well-being of personnel employed in the administration of this contract.

57. The Contractor shall comply with the provision of AR 385-10, Army Safety Program.

58. The Contractor shall develop and implement a safety program for employees performing work under this contract.

59. The Contractor shall submit the Safety Plan to the Contracting Officer, or designated representative, for review and acceptance within 10 days of commencement of work.

60. Revisions shall be submitted five (5) calendar days prior to the effective date of change.

61. The Contractor shall comply with the Occupational Safety and Health Administration (OSHA) standards.

62. The Contractor shall be responsible for ensuring adherence to all applicable {insert Installation}, State of {insert State}, and federal rules and regulations.

63. Contractor must be certified/licensed in appropriate Environmental Protection Agency (EPA) and {XX} (fill in the state of performance) Department of Agriculture categories for the application of herbicides.

64. Required documentation of certification or licensure for new Contractor personnel shall be filed with the Contracting Officer or COR within 24 hours prior to performance of service by any Contractor personnel

65. The Contractor shall comply with tenants of the EO and when practicable, shall use:

a. (a) products with post-consumer recycled content

b. (b) products that are recyclable

c. (c) low toxicity or non-toxic products

d. (d) low-maintenance products

66. The Contractor is required to use these recycled or recovered products unless they cannot be procured within a reasonable period of time; at reasonable prices; or the product(s) do not meet technical or performance standards. EPA Guidelines are the minimum requirement.

67. The Contractor shall maintain records and submit an annual report to the COR, along with the annual certification required by FAR 52.223-9 Certification and Estimate of Percentage of Recovered Material Content for EPA Designated Items, upon completion of the basic year and each option year.

68. The Contractor shall comply with all federal, state, local and installation environmental laws, rules and plans.

69. The Contractor shall use and store all materials, chemicals, and equipment used in the…