Skip Ribbon Commands
Skip to main content

Skip Navigation LinksTools

Use SHIFT+ENTER to open the menu (new window).
Tool Description

An extract of research performed by the Center for the Management of Science and Technology at the University of Alabama at Huntsville analyzing different incentives, and describing the building blocks of each one.

As part of their "Comparison of Selected Incentives", UAH evaluated:

  • Award Fee - The Government determines and measures a contractor’s performance within specifically designated performance categories, evaluation criteria, and evaluation periods.
  • Graduated Award Fee - An approach to award fees that layers incentive elements.
  • Performance Based Incentives - Effective performance-based contracts: define work in measurable, mission related terms; contain performance standards; include quality assurance plans for measuring performance; and provide financial incentives and penalties based on performance.
  • Share in Savings (SIS) Strategy- Encourages contractors to apply ingenuity and innovation to get the work done quickly and efficiently and share in the savings attributed to their planning and execution.
  • Early Completion Bonus - Incents early delivery of product or service.


Welcome to the Performance Based Logistics (PBL) PWS Development Job Support Tool (JST)!


In support of the Better Buying Power (BBP) 3.0 “Incentivize Productivity in Industry and Government” initiative to “ensure effective use of Performance Based Logistics”, DAU has established this resource to assist defense acquisition workforce members successfully develop effective and comprehensive performance work statements (PWS) for implementing best value PBL Product Support Arrangement (PSA). Whether you are serving as a Product Support Manager (PSM) or as Contracting Officer Representative (COR), this resource is available to you.


DAU has developed a comprehensive Acquisition Requirements Roadmap Training (ARRT) Tool as a job aid designed to help you improve tradecraft in service acquisitions, including crafting the requirements for PBL product support arrangements. Primary features of the ARRT Tool include:

  • Develop performance based service requirements following a proven process
  • Create a draft Performance Work Statement (PWS), Quality Assurance Surveillance Plan (QASP), and a Performance Requirements Summary (PRS)
  • Develop your contract source selection factors
  • Monitor and track contractor performance based on your PWS
  • Develop your Independent Government Cost Estimate
  • Provides a standard template that may be tailored for the PWS, QASP, and PRS
  • Export draft documents to MS Word or MS Excel
  • Automated MS Access Database file


Keep in mind that this is not the only tool available to you, as there are other ways to craft performance work statements. It is, however, a tool that provides a structured, disciplined and consistent process that enables you to develop a Federal Acquisition Regulation (FAR)-compliant PWS that includes task standards and acceptable quality levels (AQL).

Support for and help using this job support tool is available from both the ARRT website and the Service Acquisition Mall (SAM). The ARRT team will also monitor questions and issues logged here and will attempt to resolve user issues, however there is no express warranty or direct support guaranteed in the use of ARRT. DAU also offers a number of related learning assets that leverage the Acquisition Requirements Roadmap Training (ARRT) Tool, including:

DoD personnel are highly encouraged to request a WSM 012 Service Acquisition Workshop (SAW) at when they first begin planning for a services acquisition contract. The SAW is tailored to assist your Services Acquisition (SA) team in conducting the seven-step process for a services acquisition to include:

  1. Forming the Team
  2. Reviewing Current Strategy
  3. Market Research
  4. Requirements Development
  5. Acquisition Strategy Development
  6. Execution of the Strategy
  7. Performance Management

Other related -- and potentially helpful -- references include:

In addition, DAU also offers a series of mission assist workshops for all types of contracting efforts; these include:

A few key considerations before you get started. First, keep in mind that PBL, by definition is not synonymous with Contractor Logistics Support (CLS) or Interim Contractor Support (ICS), nor do successful PBL Product Support Arrangement (PSA) necessarily require a commercial sector Product Support Integrator (PSI) or Product Support Provider (PSP) in order to successfully deliver desired performance and cost outcomes. According to DOD Guidance, “PBL is synonymous with performance based life cycle product support, where outcomes are acquired through performance based arrangements that deliver Warfighter requirements and incentivize product support providers to reduce costs through innovation. These arrangements are contracts with industry or inter-governmental agreements.” By virtue of the fact this tool is used to develop a contractual documents that include a Performance Work Statement (PWS), Quality Assurance Surveillance Plan (QASP), and Performance Requirements Summary (PRS), it is intended for crafting a product support arraignments with commercial sector industry integrator(s) and/or provider(s). Additionally, keep in mind when envisioning commercial sector involvement in a PBL arrangement, that such arrangements do not necessarily have to be in the form of a services contract. There are actually two major approaches that can potentially be used to implement PBL contracts: the supply or the service contracting approach. Both types have been used successfully. See the frequently asked questions section of the PBL CoP for additional details.

Instructions for developing a tailored PBL PWS in the ARRT Tool:

  • Proceed to the Service Acquisition Mall (SAM) where you will click on the Acquisition Requirements Roadmap Tool (ARRT) Suite link at the bottom of the page. On the next page, just click on “ARRT Requirements Definition” and you will be taken to the ARRT Requirements Definition description. Below the definition of the left side you will select “Click Here to Download ARRT Requirements Definition”. This will take you to a registration page. Once you register, you will receive a link via e-mail enabling you to download the ARRT file. You will require MS Access 10.0 or later on your computer.
  • The ARRT Requirements Definition tool enables you to develop a PWS and QASP and export them to MS Word for further editing, routing and/or review. Please note that you cannot insert tables or graphics while using ARRT but you can do so once it is exported to MS Word.
  • ARRT comes pre-loaded with some sample PWS and you can import other as they become available to you. ARRT methodically leads you through the steps of entering Project Information, Requirements statements, Standards, Acceptable Quality Levels (AQLs), Deliverables and Inspection criteria/responsibility in a standardized, consistent and disciplined manner compliant with the Federal Acquisition Regulation (FAR).
  • The focus of developing performance based tasks is on the Results, Context and Action(s). The next step is documentation of the standard(s) used to perform the task as well the AQL for that task. In simple terms, the ARRT forces you to consider three aspects of each task:
    1. What do you want?
    2. When/Where do you want it?
    3. How do you know it’s good when you get it?
    This methodology forces the requirements developers to perform the critical thinking necessary to develop specific, results-based requirements as well as acceptance criteria.
  • Once the task is written with one or more standards and AQLs, the ARRT leads you through documentation on inspection criteria of what is inspected/reviewed, how, the frequency and by who as well as any applicable incentives or remedies. These factors will be used to develop the Quality Assurance Surveillance Plan (QASP)
  • DAU plans to introduce one or more PBL PWS sample(s) as part of the ARRT Requirements Development download within the next year. Additional PBL-functionality will also be incrementally added over the same timeframe.




OtherAcquisition Requirements Roadmap Tool ARRT

Although tailored for acquistion reporting of high cost weapon systems, this template, created by DFAS, may potentially be useful for creating baselines for PBL support arrangements as well.



This document is being retained as an archived Performance Based Life Cycle Product Support (PBL) reference. It may still have applicability or relevance, however much of the content is no longer current. Recommend users of this site confirm this with more current DoD PBL references including, but not limited to:   


ACC Admin Note:  For any references to DoD Directive 5000.1 or DoD Instruction 5000.2, those documents have been renamed to DoD Directive 5000.01 and DoD Instruction 5000.02 respectively and can be found at the above URLs.



This site contains five downloadable JPG files of the Department of Defense (DoD) Performance Based Logistics (PBL) logo. Users of this site should read and familiarize themselves with the guidelines outlined in "Guidelines for use of the DoD PBL Logo” prior to downloading or using these graphics.

NOTE:  The “PBL Light Silver Seal” version of the DoD PBL logo should be used whenever possible. The “PBL Black-White Seal” logo is for use in black and white applications. The other remaining files (“PBL Blue-Grey Seal”, “PBL Light-Dark Silver Seal” and “PBL Grey-Scale Seal”) are for special purpose use and should only be used on a very limited basis.

Downloadable DoD Performance Based Logistics (PBL) logo files for use IAW "Guidelines for use of the DoD PBL Logo.”


Appendix I from NAVAIR's Maintenance Cost Trade Guidebook.  Appendix I is a cost element structure for Product Support Strategies for aviation-related items as of March 2004.



This document, while several years old now, provides some useful insights into product support business case analysis. This document is being retained as an archived product support reference, and as such may or may not still be fully current. Recommend users of this site confirm this with more current Navy and DoD acquisition and product support references including, but not limited to:   




This excellent reference was developed by the Assistant Deputy Undersecretary of Defense (ADUSD) for Supply Chain Integration (SCI) to act as a guide and template for DoD organizations in preparing and completing Performance Based Agreements.  It supports a DUSD/L&MR memo requiring all supply service providers to establish performance based agreements with their customers.  It is a supply oriented guide, but contains procedures that would generally apply to the creation of other types of Performance Based Agreements.  Note: The term Assistant Deputy Undersecretary of Defense (ADUSD) was subsequently changed to Deputy Assistant Secretary of Defense (DASD). The term Deputy Undersecretary of Defense (DUSD) was changed to Assistant Secretary of Defense (ASD).



This document is being retained as an archived Performance Based Life Cycle Product Support (PBL) reference. It may still have applicability or relevance, and as such, may or may not still be fully current. Recommend users of this site confirm this with more current DoD PBL references including, but not limited to:   


ACC Admin Note:  For any references to DoD Directive 5000.1 or DoD Instruction 5000.2, those documents have been renamed to DoD Directive 5000.01 and DoD Instruction 5000.02 respectively and can be found at the above URLs.



The Performance Based Logistics (PBL) job support tool is crafted to assist acquisition workforce personnel with determining a program's PBL maturity level. Developed in a standard Excel format, the tool provides a whiz-bang way to determine if your program's sustainment approach may lead to a successful PBL program. It can be used during any acquisition phase, but when executed early in the program, your design and contracting approaches may be more positively influenced to enable an effective PBL solution. 


This tool is aligned with OSD's PBL Guidebook, the BCA Guidebook, and PBL's enabling tenets. It is not a compliance audit, and the focus is not on the program's adherence to statutory or regulatory guidelines. To be clear: it does NOT replace critical thinking or sound professional judgement of the program's technical experts, the goal is to help programs be more self-sufficient with these very complex types of efforts. 

Job AidPerformance Based Logistics (PBL) Job Support Tool

 An somewhat dated, although still useful generic template for creating Navy-centric PBL Statements of Work (SOW) for potential commercial sector Product Support Integrators (PSI).

Provides a tailorable generic template for PBL statements of work.

Chat with DAU Assistant
Bot Image