ARRT Requirements Definition Version 4.3
Acceptable Quality Level (AQL): An acceptable performance variation to standard(s) established in the PWS for each task statement.
Action: An activity you want the contractor to perform within a statement in order to achieve the results. Actions are verbs that are combined with results and context to describe a PWS statement. In the ARRT Requirements Definition, each statement will specify the types of actions related to producing the desired results.
Category (Result Category): A collection of sample results for a particular type of service. The tool allows you to import categories for a wide variety of service areas (available on the Service Acquisition Mall). You may also create and manage your own sample categories within the tool.
Context: What the statement or result is related to or supporting, such as the XYZ program or initiative.
Deliverable: Any item (report, software item, product, etc.) developed by the Contractor and delivered as part of the contract. Deliverables often require a cross-reference in the deliverables list. The ARRT Requirements Definition allows you to link deliverables with specific statements through the Inspection definition process.
High Level Objective (HLO): A key overarching result-based objective for a project necessary to achieve the project’s vision. HLOs are similar to Level 2 in a Work Breakdown Structure. In the ARRT Requirements Definition, HLOs contain multiple statements required to achieve each HLO.
Incentive: Either a penalty or reward associated with each statement and can be positive or negative. Incentives are intended to motivate a contractor to meet or exceed the performance standards if it is of value to the government. Incentives can also be used as a penalty if contractor performance fails to meet the required performance standard(s). Past Performance assessments should always be included in the incentives.
Inspection: The assessment process used to determine if the contractor’s performance has met the performance standards for each statement. It addresses what is to be inspected, who is to inspect and how it is to be done (method and frequency).
Performance Requirement Summary (PRS): A document that captures in table form the statements, standards, and incentive information of the requirement. The PRS should be included in the PWS.
Performance Work Statement (PWS): A formal document that clearly describes the requirements, mission, scope, objectives, and standards for a project. The PWS becomes part of the binding contract.
Project: The name you give to the requirement you’re developing, it’s the main reason for the work products of the ARRT Requirements Definition (PWS, PRS, QASP). The project is the main focus for needing a contractor’s support. In the tool, each new requirement is characterized as a project. A project contains the requirement-specific information necessary for generating the PWS, PRS, and QASP.
Quality Assurance Surveillance Plan (QASP): The primary inspection document used by Contracting Officers Representatives (COR) to determine if the contractor is meeting the performance standards contained in the contract. The QASP identifies the HLOs, Statements and Performance Standards, what will be inspected, how it will be inspected and who is responsible for the inspection. The results of those inspections will then be used to document contractor performance. The QASP is an essential document required to effectively administer the contract.
Related Document: An external document that is referenced by this requirement or included for the contractor’s reference. The tool allows you to create a list of related documents for each project. These can be directives, rules or regulations with which to comply.
Requirements Roadmap (Summary Report): A matrix used to organize and structure the elements of a project. In the ARRT Requirements Definition, mission requirements are organized into projects by HLOs and statements, standards, AQLs and inspection process to ensure alignment, or the ability to execute. The tool automatically structures these into the PWS, PRS and QASP templates.
Result: The work product, outcome, or type of artifact you desire from a contractor’s performance for a specific task. In the tool, results are contained within statements; combined with context and actions, results help capture the expected outcomes for a statement.
Standard (Std): The performance level (timeliness, quality, cost) required for each statement. Standards are driven by the level of performance required to meet the mission requirement for this action. Standards are cost drivers, ensure they reflect actual mission needs.
Statement: The specific results-based activities required to
satisfy HLOs. A statement contains a result, the context of the
statement, and the required action(s). Statements focus on “what” is to
be accomplished; however they are not prescriptive in describing “how”
the outcome is to be achieved. Each HLO may have several statements to
flesh out the areas necessary to meet the objective. Statements are
similar to Level 3 in a Work Breakdown Structure.
Surveillance Matrix: A component of the QASP that captures in table format the statements, standards, and inspection methodologies of the requirement. The Surveillance Matrix is included (by default) in the exported word document for the QASP. It is split apart from the QASP in the tool for ease of use.
Template: The default structure and data that the ARRT Requirements Definition uses for new projects created within the tool. You can modify the PWS and QASP templates that the tool uses for your future projects. Note: the tool always assumes that the HLO and task requirements are in section 3, Deliverables are in Section 5, and Related Documents are in Section 6.
Vision: A high level expectation of what you want to achieve. It’s a statement which captures the main purpose or mission this project supports. This statement should capture “why are we doing this, what high level result are we trying to accomplish?”
Work Product: The key documents that the tool produces such as the PWS, PRS and QASP.