2.3 Describing Agency Needs & Performance Work Statements (FAR Part 11)

2.3 Describing Agency Needs & Performance Work Statements (FAR Part 11)

Describing agency needs is the technical bridge between acquisition planning and solicitation. Governed by FAR Part 11 (Describing Agency Needs) and supported by FAR Subpart 37.6 (Performance-Based Acquisition), federal policy requires agencies to state requirements in terms of functions to be performed, required performance levels, and essential physical characteristics, avoiding restrictive specifications that inhibit competition.

---

Order of Preference for Requirements Documents (FAR 11.101)

Under FAR 11.002(a) and FAR 11.101, executive agencies must specify requirements using the following statutory order of preference:

1. Mandatory Statutory / Agency Standards: Documents mandated by federal law or regulation.
2. Performance-Oriented Requirements Documents: Performance Work Statements (PWS) or Statements of Objectives (SOO).
3. Non-Government Voluntary Standards: Industry consensus standards established by organizations such as ISO, IEEE, ASTM, or ANSI (pursuant to the National Technology Transfer and Advancement Act of 1995).
4. Commercial Item Descriptions (CIDs): Simplified specifications describing products sold in the commercial marketplace.
5. Design Specifications / Traditional Statements of Work (SOW): Detailed build-to-print technical drawings or step-by-step methodology specifications (lowest preference).

---

Requirements Frameworks: SOW vs. PWS vs. SOO

The choice of requirements document determines vendor flexibility, technical risk allocation, and government surveillance burden.

---

Performance-Based Acquisition (PBA) Architecture

Under FAR 37.102, service contracts must be performance-based to the maximum extent practicable. A complete PBA framework consists of four integrated pillars:

+-----------------------------------------------------------------------------------+
|                         PERFORMANCE-BASED ACQUISITION (PBA)                       |
|                                                                                   |
|  1. Performance Work Statement (PWS)                                              |
|     • Defines required outcomes, deliverables, and operational boundaries          |
|                                                                                   |
|  2. Measurable Performance Standards                                              |
|     • Establishes objective standards for quality, quantity, and timeliness       |
|                                                                                   |
|  3. Acceptable Quality Levels (AQLs)                                              |
|     • Defines allowable error thresholds or tolerances (e.g., 99.5% uptime)       |
|                                                                                   |
|  4. Quality Assurance Surveillance Plan (QASP)                                    |
|     • Details government inspection methods (Random sampling, 100% inspection)    |
+-----------------------------------------------------------------------------------+

QASP Surveillance Methods

• Random Sampling: Statistical sampling best suited for high-volume, repetitive tasks (e.g., invoice processing, call center inquiries).
• 100% Inspection: Total inspection used for critical safety, high-dollar, or life-support requirements (e.g., aircraft engine overhauls).
• Periodic Sampling: Scheduled inspections conducted on a recurring basis (e.g., monthly facility maintenance reviews).
• Customer Feedback: Validated complaints or user feedback logs monitored by the COR.

---

Brand Name or Equal Descriptions (FAR 11.104)

Agencies often reference commercial brand names to describe requirements. Under FAR 11.104, using a "Brand Name or Equal" description requires strict adherence to competitive guidelines:

1. Salient Characteristics Requirement

Solictations referencing a brand name model (e.g., "Cisco Model X Router or Equal") must list all salient physical, functional, or performance characteristics that an equal product must satisfy. Bidders proposing equal products need only satisfy the listed salient characteristics to be eligible for award.

2. Brand Name ONLY Solicitations

Restricting a solicitation to a single Brand Name ONLY (excluding equal products) eliminates competition among alternative manufacturers. A Brand Name ONLY specification requires:

• A formal written Justification & Approval (J&A) under FAR Subpart 6.3 for acquisitions > SAT, or a Brand Name Justification under FAR Part 13 / FAR Subpart 16.5.
• Public posting of the brand-name justification alongside the solicitation on SAM.gov pursuant to FAR 5.102(a)(6).

---

Exam Focus: Worked Scenario — SOW to PWS/QASP Transition

Scenario: A naval shipyard maintains a $12 million contract for cyber-security monitoring. The existing SOW specifies that the contractor must provide 10 security analysts sitting at desks continuously running specific commercial antivirus software scans every 4 hours.

Flaws in Current SOW:

• Dictates staffing inputs (10 analysts) and exact commercial tools, retaining technical risk on the government if a breach occurs.

Conversion to PWS / QASP Framework:

1. PWS Outcome Statement: "The contractor shall maintain continuous network security monitoring, detecting and isolating 100% of malicious intrusions within 15 minutes of occurrence."
2. Performance Standard & AQL: Intrusion isolation lead time <= 15 minutes; Acceptable Quality Level (AQL) = 99.9% compliance per billing period.
3. QASP Inspection Method: Automated audit log monitoring and periodic random simulated penetration sampling by government CORs.
4. Incentive Structure: 2% fee deduction for performance falling between 98.0% and 99.8%; full re-performance at contractor expense if below 98.0%.