Jump to content

Search the Community

Showing results for tags 'Past Performance Information'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Instructions and Terms of Use
    • Terms Of Use
    • Before You Register, Before You Post, Instructions for Writing Your Question
  • Contracting Forum
    • What Happened?
    • Polls
    • For Beginners Only
    • About The Regulations
    • COVID-19 And Its Effect on Contracting
    • Contracting Workforce
    • The Good, The Bad, the Ugly
    • Recommended Reading
    • Contract Award Process
    • Contract Pricing Including CAS & Allowable Costs
    • Contract Administration
    • Schedules, GWACS, MACs, IDIQs
    • Subcontracts & Subcontract Management
    • Small Business, Socioeconomic Programs
    • Proposed Law & Regulations; Legal Decisions


  • The Wifcon Blog
  • Don Mansfield's Blog
  • Government Contracts Blog
  • Government Contracts Insights
  • Emptor Cautus' Blog
  • SmallGovCon.com
  • The Contractor's Perspective
  • Government Contracts Legal Forum

Product Groups

There are no results to display.


  • Rules & Tools
  • Legal Opinions
  • News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. In my agency, standard practice for past performance (PP) evaluation involves first determining the relevancy of past performance information to the proposed scope of work. We do this by evaluating the size of the PP contract, it's scope (by reviewing proposal information or finding the PWS), and the PP contract's "complexity". Size and scope have their own definitions, but I want to focus on complexity. Complexity is generally defined in the RFP as "performance challenges", which vary from RFP to RFP and could include subcontractor management, management of large complex contracts in highly regulated industries, cost efficiencies, etc. This results in separate documentation in our evaluation report speaking specifically to how the scope may or may not be relevant, and then how the complexity may or may not be relevant. Background: My agency requests that offerors provide a few pages of information on two or three selected past performance (or "reference") contracts to aid in evaluation. This includes discussion of scope relevance and complexity relevance, which are separate entries on the provided form. We then evaluate other past performance information that is available to us. My question to the forum is whether other agencies regularly evaluate the complexity of past performance contracts separate from scope (from my readings of GAO and COFC decisions, it seems to be a fairly standard practice), and whether or not evaluating complexity adds value. In my experience: Lesson learned: Complexity is generally not a discriminator in relevancy determinations Root Cause: The RFP definition of complexity as “performance challenges” nearly always comes in the context of scope, making it difficult to distinguish between the two. Offerors can struggle with the concept and implementation of complexity into reference contract information forms, when separated from a discussion on how a given contract is relevant to the scope of the proposed PWS. Complexity is difficult and time-consuming to evaluate when reviewing non-reference contracts. The acquisition community has used the phrase "size, scope, and complexity" for decades without carefully considering what they mean and how they each aid evaluation. Recommendation: Study the potential effects of removing complexity as an independently evaluated item in the past performance relevancy evaluation. SEB’s can still include complexity as a part of the scope relevancy evaluation. For example: “Contract relevance will be determined based on size and scope, including complexity.” Conclusion: SEB’s can safely rely solely on size and scope to determine relevancy. RFP’s can still solicit examples performance challenges in the scope description. Eliminating separate complexity determinations would streamline the relevancy evaluation process. Is "size, scope, and complexity" standard language in your RFPs? How do you approach complexity? Do you agree or disagree with my points and why? Thank you in advance for your thoughts. Note that I am not an 1102, but can pick my way around the FAR when I need to. Please be gentle. :)
  2. Does anyone remember or know of whether or how the NIH Contractor Performance System (CPS) allowed contractors to comment? It has been a very long time since I've used this system as our agency switched to CPARS, but we are looking over some reports in PPIRS that were filed via CPS in later FY 2009 about a contractor that are very troubling. The only issue is that there are no comments recorded by the contractor. This seems highly unusual given how negative the assessment is, as usually contractors manage some kind of rebuttal. We are wondering if the contractor was ever given an opportunity to really respond to the record because none of us can recall exactly how NIH CPS worked in that regard or whether CPS had any mechanism for a contractor to dispute a rating. I've tried to find old manuals to the NIH CPS to see if they could help, but I haven't been able to locate anything more than an old NIH policy that describes how CPS works in general without addressing that question. Anyone out there have any idea about this? I would ignore the record, but it is within the three year window and potentially relevant.
  • Create New...