CSOW Genl TEMPLATE w QASP for HMIF.docx

CONTRACTOR STATEMENT OF WORK “TEMPLATE”

FOR

RCCTO Human Machine Integrated Formations Projects

DATE

Prepared by:

Army Rapid Capabilities and Critical Technologies Office

ATTN: SAAL-RCCTO-CTO

Building 6010 Aberdeen Proving Ground, MD 21005

WARNING - This document contains technical data and / or technology whose export or disclosure to Non-U.S. Persons, wherever located, is restricted by the International Traffic in Arms Regulations (ITAR) (22 C.F.R. Section 120-130) or the Export Administration Regulations (EAR) (15 C.F.R. Section 730-774). This document CANNOT be exported (e.g., provided to a supplier outside of the United States) or disclosed to a Non-U.S. Person, wherever located, until a final jurisdiction and classification determination has been completed and approved by the cognizant U.S. Army official, and any required U.S. Government approvals have been obtained. Violations are subject to severe criminal penalties.

TABLE OF CONTENTS – VERIFY PAGE NUMBERS

1 Scope……………………………………………………………………………………………………………………3

1.1 Background………………………………………………………………………………………………………3

1.2 Contract Requirements…………………………………………………………………………………………..3

1.3 Place of Performance…………………………………………………………………………………………….3

1.4 Period of Performance…………………………………………………………………………………………...3 2 Applicable Documents…………………………………………………………………………………………………..3

2.1 Army Regulations………………………………………………………………………………………………...3

2.2 Government Furnished Information (GFI)……………………………………………………………………….4

2.3 Data Item Descriptions (DIDs)………………………………………………………………………………...4-5

2.4 Hardware/Software Deliverables…………………………………………………………………………………5

2.5 Media and File Format……………………………………………………………………………………………5 3 Tasks and Requirements……………………………………………………………………………………...………….6

3.1 Tasks……………………...………………………………………………………………………………………7

3.2 Requirements……………………………………………………………………………………………………..7

3.3 Project Management……………………………………………………………………………………………...7 4 Travel…………………………………………………………………………………………………………………….7 5 Data Rights………………………………………………………………………………………………………………7 6 Government Furnished Property (GFP)…………………………………………………………………………………7 7 Security and Classification………………………………………………………………………………………………7 8 Anti-terrorism (AT) and Operations Security (OPSEC)………………………………………………………………7-9

ATTACHMENT 1: QASP Template

1.0 Scope

This Statement of Work (SOW) describes a summary of the project/effort to develop for the Army….[ For information on drafting the SOW consult MIL-HDBK-245D. Add Contractor’s summary of the proposed effort and outcomes. Include a summary of planned services, tasks, work, and the range of activities that will be conducted from the beginning of the POP to the completion of the effort.]

1.1 Background

The U.S. Army’s Rapid Capabilities and Critical Technologies Office (RCCTO) has established a total Army Integrated Solutions Team (IST) tasked with developing Human Machine Integrated Formations (HMIF) by integrating cross-Army autonomous and robotics initiatives into operationally deployable prototypes, The requirement for {an Enhanced Ground Reconnaissance Initiative (EGRI) small unmanned aerial system (sUAS)} is part of the overarching HMIF deliverable. RCCTO’s mission is to rapidly and efficiently research, develop, prototype, test, evaluate, procure, transition, and/or field critical enabling technologies and capabilities that address near-term and mid-term threats. The U.S. Army faces an ever more lethal and disruptive battlefield requiring quick acquisition of innovative capabilities to prototype and deliver to the warfighter. This Statement of Work (SOW) addresses identified Army technology gaps and provides solutions to the gaps and the Army’s stated objectives [This SOW provides the contractual opportunity to provide solutions to Army technology and operational gaps in the areas of robotics and autonomous (RAS) operations and develop new state-of the-art unmanned capabilities for the Army. The goal is to develop mature solutions that can provide combat prototype capability that can be in the hands of Warfighters within a one-to-three-year timeframe.]

1.2 Contract Requirements:

For the effort described in this SOW, contractor shall [DESCRIBE CONTRACTOR’S SOLUTION TO RCCTO SOO] leverage their past advancements to deliver a technical solution that utilizes a new…[contractor to add details of their proposed solution…]

1.3 Places of Performance:

[ADDRESS, CITY, STATE OF ANY LOCATIONS THAT WORK OR TESTS WILL BE CONDUCTED. MAY BE MULTIPLE LOCATIONS]

1.4 Period of Performance:

[Contractor’s planned POP in number of months, not dates, i.e., 18 Months, 24 Months, 36 Months, or other period “from date of contract award.”]

2.0 Applicable Documents

The following documents are applicable to the extent cited. All revisions will be the latest available revision as of the agreement date. [Contractor is free to add any DOD or Army documents and the Govt may add to this list.]

2.1 Army Regulations

MIL-HDBK-245D

The Army Physical Security Program (27 JUN 2019)

Preparation of Test Reports

Handbook for Preparation of DOD Statements of Work

2.2 Government Furnished Information (GFI): [The Contractor may request by stock number and nomenclature any GFI the Contractor believes is needed to successfully complete the requirements specified in this SOO and identify risk reduction strategies if Government is unable to provide requested items.]

The Government shall provide the following:

· OPSEC information & Security Classification Form DD254

2.3 Data Item Descriptions (DIDs) Deliverables

All Data Item requirements referenced throughout this SOW are reflected in Table 1 below. Timely submission of deliverables is essential to successful completing this requirement. All deliverables shall be prepared and submitted according to format, content, and schedule described in the SOW and the accompanying CDRLs (DD Form 1423). All delivery dates are based on calendar days (30 days =~ one (1) month). Specific acceptance criteria are provided in the applicable CDRLs. If a deliverable is unacceptable, the contractor shall make the necessary corrections and redeliver to the Government.

[Data Items listed below are the typical DIDs required for planned projects. Contractor may propose additional DIDs or remove ones that are N/A. And the Government may add additional DIDs upon review of the proposed project.

· TITLE – Update SOW para numbers for each line per your SOW

· DELIVERY DATE – Update per SOW and proposed plan/schedule, etc.]

Table 1 Data Item Descriptions (DIDs)

(SOW para 3.x.x) X months after award

(SOW para 3.x.x) Draft at PDR Final at CDR

(SOW para 3.x.x) Draft at CDR Final SAR 2 months prior to operational flight evaluation

(SOW para 3.x.x) 2 weeks prior to each operational capstone evaluation

Due on 5th day after the end of the preceding month

Contractor to deliver all technical, user, operational, training manuals and instructions for delivered hardware and software for proper system operations & maintenance.

X months after award

2.4 Hardware and Software Deliverables - [Update and list any hardware and/or software planned to be developed and delivered as part of the Contractor proposed solution] As part of this contract, the contractor shall package and deliver the following items in support of this effort:

[For Example Add Text Like this: Two (2) Prototype _______ devices; Two (2) Complete units of the final flexwave telephone radar in the Government approved configuration; and two (2) two cell phones [no sim cards], with software installed and listed. Five (5) Laptop Computers (ruggedized) with embedded software to operate system and training manuals for Soldier operations.

The Contractor shall provide all hardware and software necessary to design, develop, demonstrate, and deliver the radars/waveforms. This includes the COTS Wave Radar and the SIGINT functionality used for the demonstration.

The contractor shall provide all technical manuals, operational manuals, user manuals, and training modules for delivered hardware and software to enable proper system operations. Such manuals shall contain instructions for the installation, operation, maintenance, training, and support of delivered systems, system components, and support equipment. These manuals shall include operational and maintenance instructions, parts lists or parts breakdown, and related technical information or procedures exclusive of administrative procedures. (CDRL A012)]

2.5 Media and File Format

Microsoft (MS) Office suite applications (MS Word, MS Excel, MS PowerPoint, and MS Project) are the preferred file formats for data furnished under this agreement unless specified otherwise. For unclassified data uploaded to the DoD Secure Access File Exchange (SAFE) website, MS Internet Explorer 7.0 (or later version) is the preferred browser. Other formats for the transmittal of agreement documentation and methods for electronically signing a Material Inspection and Receiving Report (DD Form 250) shall be set forth in the agreement.

3.0 Tasks and Requirements

[Additional Guidance for this Section: Section 3 of the SOW should specify in clear, understandable terms the work to be done in developing or producing the planned prototype, project, goods, or services to be delivered or performed by the contractor. The contractor SOW must describe how the services and tasks will be accomplished. It may include technical milestones such as bench or laboratory tests and reports, delivery of interim prototypes, demonstrations, significant technical meetings (i.e., PDR, CDR, etc.), field tests and reports, required documentation/drawings, satisfaction of government requirements, etc. Preparation of an effective SOW requires both an understanding of the project, goods, or services that are needed to satisfy a particular requirement and an ability to define what is required in specific, performance-based, quantitative terms. This facilitates the preparation of responsive program plans and milestones and delivery of the required project, prototype, goods or services. The SOW defines (either directly or by reference to other documents) all work (non-specification) performance requirements for contractor effort. Qualitative and quantitative design and performance requirements are contained in specifications developed according to MIL-STD-961. Such specifications are typically referenced in the SOW, but the specific qualitative or quantitative technical requirements should not be spelled out in the SOW. The SOW becomes a standard for measuring contractor performance. As the contracted effort progresses, the government and the contractor will refer to the SOW to determine their respective rights and obligations. In this respect, the SOW defines the contract and is subject to the interpretations of contract law. The SOW must clearly define the work to be performed, since the language detailing the contractor's effort may be pertinent to legal questions concerning the scope of work. Data deliverables are identified in Contract Data Requirements List (CDRL) exhibits to the contract. See also MIL-HDBK-245D for additional guidance.]

Contractor will perform the following tasks … [Contractor to add clear discrete tasks of the planned work to meet the objectives and Army requirements, examples are from prior RCCTO efforts. ]

[EXAMPLE 1]

[EXAMPLE 2]

3.2 Requirements – [Contractor Proposed Tasks that will satisfy the SOO and demonstrate performance metrics]

3.2.1 Contractor shall identify Army requirements for the _______ and document those requirements as part of the Systems Requirements Review.

3.2.2 Contractor shall identify the ______ hardware on which to implement the ______.

3.2.3 Contractor shall implement on _____hardware a ______ that uses _________________.

3.2.4 Contractor shall develop and deliver eight (8) _________ units of the final approved configuration to the Army.

3.2.5 The [proposed solution] shall use advanced encryption schemes (e.g., AES-256).

3.2.6 The [proposed solution] shall have Size, Weight, Battery Life, and Cost that is appropriate for use as a __________ device.

3.2.7 The [proposed solution] shall provide a ____________.

3.2.8 Contractor shall conduct a demonstration in a laboratory environment. This demonstration will demonstrate the full _______ capabilities of the {proposed solution}. This demonstration will also include _________________.

3.2.9 Contractor shall conduct a demonstration in a Relevant Outdoor Environment. This demonstration will demonstrate the full _____capabilities of the [proposed solution]. This demonstration will also include ____________________________________.

3.2.10 Contractor shall provide a test plan before the lab testing and field demonstration, and a test report after them. (See applicable CDRLs)

3.3 Project Management

[UPDATE TRAVEL – Per contractor’s plans as outlined in the SOW -Example below]

4.0 Travel

[The Contractor will travel with eight (8) employees per trip (to/from Bangor, MA) to attend five (5) test events in GOCO test facilities in White Sands Missile Range (WSMR) to demonstrate the capabilities of the [proposed solution]. Two (2) TIM meetings at Aberdeen Proving Ground with 3 employees (to/from Bangor, MA). Government AOR will approve travel in advance (Government email approval is adequate).]

5.0 Data Rights

All products, data, and software developed by the Contractor in support of its proposal for this SOW shall be delivered with unlimited rights (UR) to the Government as delineated in the clause at FAR 52.227-23 – Rights to Proposal Data (Technical). Additionally, Government data right requirements under this contract are regulated by FAR clause 52.227-14, Rights in Data-General, Alternative III. The contractor shall comply with FAR clause 52.227-15, Representation of Limited Rights and Restricted Computer Software, and complete the requirements of paragraph (b) of that clause and submit with its proposal. Rights in technical data for commercial items shall be provided in accordance with the DFARS clause 252.227-7015 – Technical Data – Commercial Items, and rights in technical data for noncommercial items shall be provided in accordance with DFARS clause 252.227-7013, Technical Data-Noncommercial Items. The Government also retains the right to validate any restrictive markings under DFARS clause 252.227-7037, Validation of Restrictive Markings on Technical Data and asserts its rights under DFARS clause 252.227-7030, Technical Data-Withholding of Payment. Furthermore, FAR clause 52.227-16, Additional Data Requirements, gives the Government the right to obtain any data during contract performance or within three (3) years after final delivery under this contract.

6.0 Government Furnished Equipment/Property (GFE, GFP)

[The Contractor may request by stock number and nomenclature any GFE/GFP the Contractor believes is needed to successfully complete the requirements specified in this SOW and identify risk reduction strategies if Government is unable to provide the requested items.]

The Contractor will coordinate with the Army to utilize or obtain ______test capabilities [Govt- Owned assets]in order to demonstrate the capabilities of the {proposed solution] on an as needed basis. During performance of this agreement, the Government may provide Government-owned property or equipment. The Government will retain title of any property provided. The Contractor shall maintain and report all Government Furnished Equipment (GFE) and Government Furnished Property (GFP) assigned to the agreement. [For planned CPFF contracts add “Title to any Contractor Acquired Property (CAP) procured under this effort shall remain vested with the Government. CAP is considered accountable Government property.”].

GFE/GFP examples below:

· Acme Mark 5(v1) Man portable radio sets for form, fit, and function and laboratory and field tests. Quantity provided 10 sets GFE.

· Aircraft platforms or surrogate platforms’ to run software

· Range facilities

7.0 Security and Classification

All hardware developed as part of this effort is anticipated to be unclassified or controlled unclassified information (CUI) and raw data taken during the test events and final demonstration will also be unclassified or CUI. [Add if necessary: “Raw data taken at the final demonstration when combined with other metadata from test events could be considered classified depending on the test conditions and should be treated in accordance with the class guide governing the test event or systems participating in that event. Detailed ELINT parameters provided by the government to the Contractor could be classified and should be handled as such, but the hardware and software built by the Contractor and derived from that information will remain unclassified or CUI. Any classified information provided to the Contractor shall be handled under the appropriate DoD guidelines.”]

8.0 Anti-terrorism (AT) and Operations Security (OPSEC) [Standard Language]

8.1 AT Level I Training. This standard language is for contractor employees with an area of performance within as Army controlled installation, facility, or area. All contractor employees, including subcontractor employees, requiring access to Army installations, facilities, and controlled-access areas shall complete AT Level I awareness training within 30 calendar days after the contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: http://jko.jten.mil

8.2 Access and general protection/security policy and procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub-contractors’ employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, Headquarters, Department of the Army (HQDA) and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

8.2.1 For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled National Agency Check with Inquiries (NACI) at the Office of Personnel Management.

8.2.2 For contractors that do not require CAC but require access to a DoD facility or installation. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

8.3 iWATCH Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility, or area. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity 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. This training shall be completed within 60 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 75 calendar days after contract award.

8.4 Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems. All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter

8.5 For contracts that require a formal OPSEC program. The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

8.6 For contracts that require OPSEC Training. Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

8.7 For information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to IA/IT functions.

8.8 For information assurance (IA)/information technology (IT) certification. Per DoD 8570.01-M , DFARS 252.239.7001 and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

8.9 For contracts that require handling or access to classified information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DOD 5220.22- M, notice of which has been furnished to the contractor.

8.10 Threat Awareness Reporting Program. For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a Counter-Intelligence (CI) agent or other trainer as specified in 2-4b.

Attachment 1

QUALITY ASSURANCE SURVEILLANCE PLAN

For Project Name:

Contractor: Contractor Name

1.0 INTRODUCTION

1.1. Purpose. The role of the Government in quality assurance is to ensure contract standards are achieved. The purpose of the Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures the Government will use to evaluate contractor actions while performing the requirements in the Statement of Work (SOW) and the proposal. It is designed to provide an effective surveillance method by monitoring contractor performance against the requirements in the SOW.

1.1.1. The QASP provides a systematic method to evaluate the services the contractor is required to perform for providing services, prototypes, hardware, software, research & development, and data item deliverables.

1.1.2. The QASP has been developed by the Rapid Capabilities & Critical Technologies Office (RCCTO). It is designed to provide direction to personnel performing contract surveillance activities. Personnel surveying the contract terms and conditions and SOW requirements will periodically review the QASP throughout the life of the contract.

2.0. ROLES AND RESPONSIBILITIES.

2.1. Agreement Officer’s Representative. The Agreement Officer’s Representative (AOR) is responsible for quality assurance guidance and to ensure that contract quality requirements, provisions, standards, and thresholds are defined, practical, enforceable, necessary, and verifiable.

2.1.1. The AOR evaluates and documents contractor performance in accordance with the QASP and SOW.

2.1.2. The AOR notifies the Contracting Officer of any significant performance deficiencies using a Contractor Discrepancy Report with supporting documentation.

2.1.3. The AOR maintains surveillance documentation.

2.1.4. The AOR recommends improvements to the QASP and SOW throughout the life of the contract.

2.2. Contracting Officer/Agreement’s Officer. The Contracting Officer/Agreement’s Officer is responsible for safeguarding the interests of the United States Government in contractual relationships. Only the Contracting Officer is authorized to bind the Government and then, only to the extent of the authority delegated to them through the issuance of a warrant.

2.2.1. The Agreement’s Officer delegates authority for inspection and/or acceptance in accordance with the terms of the contract.

2.2.2. The Agreement’s Officer informs the contractor of the names, duties, and limitations of authority for all quality assurance personnel assigned to the contract.

3.0. DESCRIPTION OF SERVICES

3.1. Scope of Work. The scope of this contract/agreement is for INSERT CONTRACTOR NAME to deliver a BRIEF DESCRIPTION OF PROJECT…..

4.0. QUALITY REQUIREMENTS

4.1. Quality Control Program. The contractor, not the Government, is responsible for management and quality control actions to meet the terms of the contract.

5.0 SURVEILLANCE. The AOR will perform monthly surveillance based on the quality and effectiveness of the contractor’s data deliverables as well as the services provided.

5.1 Unacceptable Performance. If the number of complaints/defects exceeds the performance threshold for any objective, the AOR will determine the possible cause of this unacceptable performance. Government-caused complaints/defects will not be counted against the contractor. The same applies to any other requirement of the contract when Government-caused complaints/defects are the cause of unacceptable contractor performance. If the contractor’s performance is judged unacceptable for any requirement by the AOR, the AOR will inform the contracting officer for resolution. Significant performance deficiencies must be submitted to the Contracting Officer using a Contractor Discrepancy Report and include supporting documentation.

6.0 DOCUMENTATION REQUIREMENTS.

7.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

7.1 Overview. This PRS summary identifies the services required by the SOW over which the Government will exercise surveillance.

7.2 Performance Evaluation. Performance of a service will be evaluated to determine whether or not it meets the performance threshold. Revising and resubmitting the documentation at no cost to the Government is the preferred method for correcting unacceptable performance. The contractor shall provide the Government a written response as to why the performance threshold was not met, how performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

7.3 Performance Objectives, Standards, Thresholds, and Surveillance Methods. The services required by the contractor are summarized into performance objectives along with the minimum standards that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

PERFORMANCE REQUIREMENTS SUMMARY

Task or Deliverable

Performance Indicator

Performance Threshold Surveillance Method

PRS # 1. Monthly Status Reports

(SOW Para Number; CDRL A00?)

100% accuracy with one correction/rewrite.

100% inspection of deliverables

PRS # 2 Project Reviews and Technical Exchanges

(SOW Para Number)

Reviews and Exchanges are conducted timely and relevant and required information is shared and charts, data, reports are accurate, complete and accepted by the AOR/Project Lead (PL).

95% accuracy and completeness

100% accuracy and completeness with one correction/rewrite.

100% inspection of deliverables

PRS # 3 Contract Data Requirements List (CDRLs)/DIDs (Table 1-DIDs)

100% accuracy with one correction/rewrite.

100% Timely. First draft submitted according to the award schedule. Rewrites submitted according to the AOR/PL timeline/schedule.

100% inspection of deliverables

PRS # 4 Final Closeout Review Meeting Report

(SOW Para Number; CDRL A00?)

100% accuracy and completeness r one correction/rewrite.

100% inspection of deliverables

7.4 In evaluating the quality of contractor’s performance, the following performance ratings may be used.

Performance Rating Criteria