52.222-46, Evaluation of Compensation for Professional Employees
Started by MAY-D-FAR-B-WIT-U · Jul 2, 2018 · 55 replies
- MOriginal post
MAY-D-FAR-B-WIT-U
Jul 2, 2018 · 7y ago
Is a task order competed among multiple IDIQ holders considered a "negotiated contract" or does a negotiated contract only refer to contract awarded using FAR 15 procedures?
- l
leo1102
Jul 2, 2018 · 7y ago
Question -
Does the IDIQ permit the addition of non-negotiated "new" labor categories? If so, is there a percentage limitation? It appears to me that if the IDIQ does not specifically address this possibility, then you may be wanting to do something that is out of scope of the IDIQ contract.
- F
FrankJon
Jul 2, 2018 · 7y ago
@MAY-D-FAR-B-WIT-U, this post is extremely hard to follow. You seem to be asking multiple questions and implicating multiple issues. I strongly recommend reviewing the following post, then editing for clarity.
Are you trying to find out if the inclusion of FAR 52.222-46 in a TORFP converts the solicitation procedures from 16.505 to 15?
- M
MAY-D-FAR-B-WIT-U
Jul 2, 2018 · 7y ago
Thanks FrankJon, my initial question is to find out if 52.222-46 applies to orders under 16.505 when the evaluation required by the clause was already performed during the award of the IDIQ? I then read the prescription for the clause a second time and saw that it only applies to "negotiated contracts", which led to my next question and maybe resulted in my confusing post.
- F
FrankJon
Jul 2, 2018 · 7y ago
MAY-D-FAR-B-WIT-U said:
my initial question is to find out if 52.222-46 applies to orders under 16.505 when the evaluation required by the clause was already performed during the award of the IDIQ?
It depends. In reality, it's up to the CO. Why do I say that? Let's break down the prescription at 22.1103.
It applies only to "negotiated contracts." According to FAR 15.000, a negotiated contract is:
Quote
A contract awarded using other than sealed bidding procedures is a negotiated contract
Therefore, a task order contract qualifies as "negotiated," not just FAR 15 contracts. See also the definition of "negotiated contract" in The Government Contracts Reference Book. So go to #2.
There's a $700,000 threshold. Is your task order over or under that? If over, continue to #3. (And if it's under, I don't think there's anything stopping you from continuing to #3 if you think it's appropriate.)
It applies when "services are to be provided which will require meaningful numbers of professional employees." Huh?? What is a "meaningful number"? This is why I say it's up to the CO. Any number can be considered "meaningful" or "non-meaningful" depending on perspective. This prescription is kind of ridiculous in this sense. Also, have you confirmed that these are "bona fide" professionals you're hiring, in accordance with FAR 22.1102? I've seen COs overlook this language, thinking the provision applies to all service contracts. In reality, it applies to only a sliver of the service contract pie.
Last, I'll point out that the Provisions & Clause Matrix indicates that this provision is not intended for commercial services. So there is another discriminator if you're looking for wiggle room.
So, if upon reading all of that, you think it applies, then it applies. But there's also a common sense aspect to this. Doing the evaluation required by this provision at the IDIQ level in a multiple award setting doesn't achieve much because the risks it is supposed to mitigate will return once the task orders are competed. That is, contractors may feel incentivized to under-compensate professional employees in order to win work. Unless this provision or similar price or cost realism language is in the TORFP, then they will have the flexibility to do just that.
When you're contracting for services in a competitive environment, it's usually a good idea to include some kind of "realism" evaluation language in the solicitation to protect the Government's interests (even if it's just "optional" language). Whether you do that through 52.222-46 or custom language is up to the CO.
- C
C Culham
Jul 3, 2018 · 7y ago
FrankJon said:
So, if upon reading all of that, you think it applies, then it applies. But there's also a common sense aspect to this. Doing the evaluation required by this provision at the IDIQ level in a multiple award setting doesn't achieve much because the risks it is supposed to mitigate will return once the task orders are competed. That is, contractors may feel incentivized to under-compensate professional employees in order to win work. Unless this provision or similar price or cost realism language is in the TORFP, then they will have the flexibility to do just that.
It depends as well, in my read, on whether the parent IDIQ(s) set specific rates for categories of workers or other side boards with regard to the exact professional employees that are contemplated to perform task order work. I note this based on the sentence in the clause that states " As a part of their proposals, offerors will submit a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract." wherein if the plan applies to the whole of the work contemplated under the parent IDIQ(s) it would seem re-evaluation would not be necessary at the task order level.
- R
Retreadfed
Jul 3, 2018 · 7y ago
May-D, a task order under a multiple award IDIQ contract is a contract within the definition of "contract" in FAR 2.101. As regards the clauses that apply to that contract, look at FAR 52.216-18.
- F
FrankJon
Jul 3, 2018 · 7y ago
Retreadfed said:
As regards the clauses that apply to that contract, look at FAR 52.216-18.
OP is asking about a provision, which isn't in the contract. Maybe the Government stipulated that rates are fixed, as @C Culham suggested, in which case that term would apply per 52.216-18. But I doubt that's what occurred.
- F
FrankJon
Jul 3, 2018 · 7y ago
On 7/2/2018 at 8:45 AM, MAY-D-FAR-B-WIT-U said:
Is a task order competed among multiple IDIQ holders considered a "negotiated contract"
Yes.
On 7/2/2018 at 8:45 AM, MAY-D-FAR-B-WIT-U said:
does a negotiated contract only refer to contract awarded using FAR 15 procedures?
No.
- G
Guest Vern Edwards
Jul 3, 2018 · 7y ago
Oh, for Pete's sake. See FAR 22.1103. FAR 52.222-46 is a solicitation provision that is to be inserted in RFPs for new contracts. It has no bearing on fair opportunity procedures under FAR 16.505(b)(1). It does not apply when conducting competitions for task orders under MATOCs, which does not entail issuing an RFP, because it is not a new competition, but an order against an existing contract. FAR 16.505(b) does not require the issuance of a solicitation.
FAR is a mess. You have to make sense of it. Professional employee compensations should have been evaluated in connection with the award of the underlying IDIQ contract.
- F
FrankJon
Jul 3, 2018 · 7y ago
Vern Edwards said:
Oh, for Pete's sake. See FAR 22.1103. FAR 52.222-46 is a solicitation provision that is to be inserted in RFPs for new contracts. It has no bearing on fair opportunity procedures under FAR 16.505(b)(1). It does not apply when conducting competitions for task orders under MATOCs, which does not entail issuing an RFP. Get a clue. You people are making life too complicated for yourselves.
Why? What are you basing this on other than "See FAR 22.1103"? Where within 22.1103 did you pull the "RFP" terminology on which you appear to be hanging your hat?
I reviewed 22.1103. I talked about it. I gave my reasoning for my conclusion, based upon regulation and business rationale. If you have additional insight that's not conclusory and needlessly abrasive, I'm sure we'd all like to hear it.
- R
Retreadfed
Jul 3, 2018 · 7y ago
Frank, the prescriptive language in 52.222-46 says to insert the following provision.in accordance with 22.1103. In turn 22.1103 requires contracting officers to insert the provision at 52.222-46 in solicitations for negotiated contracts, i.e., RFPs. Nowhere is 52.222-46 referred to as a clause. Looking at FAR 2.101, a provision goes into a solicitation not contracts. On the other hand, a clause goes into both solicitations and contracts. Based on this it is clear that 52.222-46 is not a contract clause and should only be inserted in solicitations. It should not be in an IDIQ contract. If it is, someone made a mistake and would not be the first time a contracting officer included a solicitation provision as a clause to a contract.
I do not know why someone would include 52.222-46 in an IDIQ contract as part of the procedures for issuing orders under that contract if that is what happened here. Some people just like to make extra work for themselves.
- G
Guest Vern Edwards
Jul 3, 2018 · 7y ago
FrankJon said:
I reviewed 22.1103. I talked about it. I gave my reasoning for my conclusion, based upon regulation and business rationale. If you have additional insight that's not conclusory and needlessly abrasive, I'm suare we'd all like to hear it.
It's simple. Look at the OP's question:
On 7/2/2018 at 5:59 PM, MAY-D-FAR-B-WIT-U said:
My initial question is to find out if 52.222-46 applies to orders under 16.505 when the evaluation required by the clause was already performed during the award of the IDIQ?
The answer is no.
FrankJon said:
Why? What are you basing this on other than "See FAR 22.1103"? Where within 22.1103 did you pull the "RFP" terminology on which you appear to be hanging your hat?
FAR 22.1103 requires inclusion of FAR 52.222-46 in "solicitations for negotiated contracts." Such solicitations are RFPs. See FAR 2.101. FAR 52.222-46 is a solicitation provision.
FAR 16.505(b) does not require the issuance of an RFP when giving offerors a fair opportunity to be considered for an order under a MATOC. COs only need issue a "fair notice." Nothing in FAR describes such notices as solicitations or requires that they be in writing.
While COs may, and have, evaluated professional employee compensation when awarding task orders, there is no requirement that they do so, and if they do so there is no requirement that they cite FAR 52.222-46, which is much too formal.
- M
MAY-D-FAR-B-WIT-U
Jul 3, 2018 · 7y ago
@FrankJon,
You second post answered most of my questions and although I pride myself on being able to research different topics and drawing a conclusion, you response shows me that I have a long way to go and I need to learn to be patient when seeking answers and dig even further. Thanks for taking the time.
@Vern Edwards
I also read "negotiated contracts" to mean RFP i.e. FAR 15 and did not think the provision will apply to orders under 16.505 but the FAR definition (A contract awarded using other than sealed bidding procedures) made me second guess myself and scratch my head a little bit.
Retreadfed said:
Based on this it is clear that 52.222-46 is not a contract clause and should only be inserted in solicitations. It should not be in an IDIQ contract.
I am guessing by "IDIQ contract" you are referring to orders under an IDIQ. While I do understand the logic in your response, we sometimes insert additional provisions when competing orders under 16.505 and in this case, we have. included additional provisions and making the decision not to include 52.222-46 because it's a provision will just be selective reasoning. I am not saying its right or wrong to include provisions in orders under 16.505 but i remember a post by Vern in which he stated that "IDIQ contracts were originally designed to be used to buy pre-specified and pre-priced products and simple services". Now we have IDIQ's used my multiple agency and sometimes we need to bring in agency specific provisions.
Just to clarify a few points,
The evaluation called for in the provision was completed during the award of underlying IDIQ contracts and the maximum rates were fixed for all IDIQ holders during award. FrankJon makes the point that "Doing the evaluation required by this provision at the IDIQ level in a multiple award setting doesn't achieve much because the risks it is supposed to mitigate will return once the task orders are competed". This is important in my case for 2 reasons 1) we encourage offerors to provide a discount to the IDIQ rates and 2) Because the IDIQ is used by a few agencies, it permits deviations from the standard labor categories in the IDIQ to accommodate everyone. In our case, about 30% of our labor categories are deviations ( all requiring higher education and experience) from the standard labor categories. These deviations are new labor categories that were obviously not evaluated at the IDIQ level.
Thank you all for your input, I think I have enough information to recommend a course of action to my KO.
- G
Guest Vern Edwards
Jul 4, 2018 · 7y ago
On 7/2/2018 at 8:56 PM, FrankJon said:
Therefore, a task order contract qualifies as "negotiated," not just FAR 15 contracts.
I disagree. FAR 15.000, Scope, says:
Quote
This part prescribes policies and procedures governing competitive and noncompetitive negotiated acquisitions. A contract awarded using other than sealed bidding procedures is a negotiated contract (see 14.101).
You have to interpret regulations as a whole. The second sentence in the above quote explains the scope of FAR Part 15. It is not a definition of "negotiated contract" that applies throughout the FAR. There is no FAR-wide definition of negotiated contract. In that regard, see FAR 1.108(a), 2.101, and 52.202-1.
While delivery and task orders issued pursuant to FAR 16.505 may be contracts as defined in FAR 2.101, I see no justification for saying that such orders are negotiated contracts as that term is explained and used in FAR 15.000 or used in FAR 22.1103. I don't recall anything in FAR 16.505(b) indicating that FAR Part 15 applies to the MATOC ordering process or that COs must comply with 22.1103 when providing a fair opportunity. So, absent other authority, any notion that FAR 22.1103 and 52.222-46 apply to MATOC orders because FAR 15.000 indicates that they are negotiated contracts is based on a false premise.
- j
joel hoffman
Jul 4, 2018 · 7y ago
The language of the provision at 52.222-46 Evaluation of Compensation for Professional Employees, appears to only be applicable when re-competing for existing services. It doesnt seem to fully line up with the broader policy stated in in FAR 22.11.
However, it seems that the policy in FAR 22.11 or the procedures therein for evaluating proposed compensation for professional employees could be as important or applicable in a task order as it would be for re-competing services for a new stand alone service contract. This would be applicable where not all professional compensation is pre-priced in the base ID/IQ contracts or where the competing firms may offer discounted pricing,
In such situations, the government would be soliciting* a proposal or proposals for a task order, not simply “issuing an order”. I don’t see why it would be inappropriate to include the provision at 52.222-46, Evaluation of Compensation for Professional Employees (or similar evaluation language) in such a solicitation*.
*The definition of solicitation in FAR Part 2 says, in part: “Solicitation means any request to submit offers or quotations to the Government. “
I think that this is what MAY-D-FAR is referring to in his/her last post.
Quote
The evaluation called for in the provision was completed during the award of underlying IDIQ contracts and the maximum rates were fixed for all IDIQ holders during award. FrankJon makes the point that "Doing the evaluation required by this provision at the IDIQ level in a multiple award setting doesn't achieve much because the risks it is supposed to mitigate will return once the task orders are competed". This is important in my case for 2 reasons 1) we encourage offerors to provide a discount to the IDIQ rates and 2) Because the IDIQ is used by a few agencies, it permits deviations from the standard labor categories in the IDIQ to accommodate everyone. In our case, about 30% of our labor categories are deviations ( all requiring higher education and experience) from the standard labor categories. These deviations are new labor categories that were obviously not evaluated at the IDIQ level.
- G
Guest Vern Edwards
Jul 4, 2018 · 7y ago
I agree that a check of professional compensation might make sense when issuing an order, but that was not the question.
- j
joel hoffman
Jul 4, 2018 · 7y ago
Vern Edwards said:
I agree that a check of professional compensation might make sense when issuing an order, but that was not the question.
I wasn’t sure what the original question was. The OP apparently rewrote it after several responders questioned it.
- C
C Culham
Jul 5, 2018 · 7y ago
Well I am still stuck on the original question as posed. I believe it was whether the provision 52.222-46 should be included in a TO solicitation under an IDIQ or something close to this question? I did a query of the GAO protest website using a couple of different search criteria and several decisions came up.
In my quick read of a few of the decisions that came up I did not find one that was definitive as to whether the provision applies to TO RFP’s but it is clear that agencies have included it in TO RFP’s and information received in response to the TO RFP has been used in the evaluation of responses to TO RFP’s. My conclusion is that as GAO has opined about how the provision is applied to evaluation of a TO RFP response and at the same time never questioned it being in the TO RFP then yes an agency may determine when the provision is applicable and include it in the TO RFP.
Here is a couple of GAO decisions that lead to my conclusion.
https://www.gao.gov/products/D15639
https://www.gao.gov/products/D16573#mt=e-report
I would note that in the several hits (decisions) that came up they addressed other issues discussed in this thread as well as they relate to the provision such as inclusion in commercial item solicitations, etc.
I did not research the OP’s question, now posed after edits, but going out on a limb I would say that absent something different from GAO it appears GAO considers RFP’s for TO that lead to an awarded contract are “negotiated contracts” at least for application of provision of 52.222-46. I say this noting as well that GAO has adopted the rule, at least by my read over the years, that if an agency applies FAR Part 15 processes to selection of a contractor for award then FAR part 15 is used as the determining principles as to whether an agency followed due process and therefore the definition of FAR Part 15 applies.
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
C Culham said:
I would say that absent something different from GAO it appears GAO considers RFP’s for TO that lead to an awarded contract are “negotiated contracts” at least for application of provision of 52.222-46.
I searched Westlaw for any GAO decisions that included both phrases "task order" and "52.222-46". I found a total of 23 such decisions, which included the two to which Carl provided links. The earliest was from July 1995 and the most recent was from June 2018.
Of the 23, only seven were about task order competitions, including competitions under 16.505, FSS, GWAC contracts, and BPAs. Here they are:
- LOGC2, B-416075, Jone 2018 (FAR 16.5 protest; Army task order "RFTOP" did not include FAR 52.222-46; protest denied)
- Target Media Mid Atlantic, B-412468.8, June 2017 (Navy "Seaport" formal RFP; expressly invoked FAR 52.222-46; protest denied)
- Micro Technologies, B-413091.4, February 2017 (Air Force GWACS formal RFP; expressly invoked 52.222-46; protest denied)
- Micro Technologies, B-413091, August 2016 (same procurement as No. 3, above; protest sustained)
- Odyssey Systems, B-412519, March 2016 (Air Force "RFTOP" under GWACS; expressly invoked FAR 52.222-46; protest dismissed/denied)
- Systems Research and Applications, B-406775.3, April 2013 (Navy "Seaport" "TORFP"; expressly invoked 52.222-46; request for atty's fees; request denied)
- Belzon, B-404416, February, 2011 (Army "RFQ" against a GSA FSS BPA; FAR 52.222-46 not included in solicitation; protest denied)
I searched those decisions for the phrase "negotiated contract." That phrase did not appear in any of those decisions.
I do not see any justification for Carl's conclusion that "GAO considers RFP’s for TO that lead to an awarded contract are 'negotiated contracts'”.
As far as I can tell, the GAO has never addressed the question of whether task orders are "negotiated contracts" as that term is used in FAR 22.1103, has never suggested that it thinks they are, has not ruled that they are, and has not indicated that FAR 52.222-46 necessarily applies to task order competitions under FAR 16.505(b) or any other task order competition procedure. If a CO invokes the provision, then GAO will consider whether the agency applied it properly. All the more reason not to invoke the provision.
- F
FrankJon
Jul 5, 2018 · 7y ago
On 7/3/2018 at 5:39 PM, Retreadfed said:
Frank, the prescriptive language in 52.222-46 says to insert the following provision.in accordance with 22.1103. In turn 22.1103 requires contracting officers to insert the provision at 52.222-46 in solicitations for negotiated contracts, i.e., RFPs. Nowhere is 52.222-46 referred to as a clause. Looking at FAR 2.101, a provision goes into a solicitation not contracts. On the other hand, a clause goes into both solicitations and contracts. Based on this it is clear that 52.222-46 is not a contract clause and should only be inserted in solicitations. It should not be in an IDIQ contract. If it is, someone made a mistake and would not be the first time a contracting officer included a solicitation provision as a clause to a contract.
Retreadfed: I'm not sure what you're getting at. You said:
On 7/3/2018 at 11:25 AM, Retreadfed said:
As regards the clauses that apply to that contract, look at FAR 52.216-18.
In response, I said:
On 7/3/2018 at 12:17 PM, FrankJon said:
OP is asking about a provision, which isn't in the contract. Maybe the Government stipulated that rates are fixed, as @C Culham suggested, in which case that term would apply per 52.216-18. But I doubt that's what occurred.
I was clarifying that your suggestion to look at 52.216-18 did not address OP's original question, unless the CO had incorporated the information received from 52.222-46 into the IDIQ and in some way made it binding (which I doubt).
On 7/3/2018 at 5:39 PM, Retreadfed said:
I do not know why someone would include 52.222-46 in an IDIQ contract as part of the procedures for issuing orders under that contract if that is what happened here. Some people just like to make extra work for themselves.
Because maybe it makes business sense. What if, as I suspect, the CO included it in the original solicitation as a basis to establish the IDIQ awardees, but did not incorporate the information into the contracts? The risks discussed by 52.222-46 would reappear with each TORFP. Maybe a simpler realism analysis would do the trick. Maybe the CO thinks 52.222-46 is more appropriate. As I said in my original response, I think that should be at the CO's discretion. I don't believe that 52.222-46 could ever truly be made "mandatory" because the prescription is vague.
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
FrankJon said:
I don't believe that 52.222-46 could ever truly be made "mandatory" because the prescription is vague.
The worst thing about 52.222-46 is the language of the provision itself:
Quote
Recompetition of service contracts may in some cases result in lowering the compensation (salaries and fringe benefits) paid or furnished professional employees. This lowering can be detrimental in obtaining the quality of professional services needed for adequate contract performance... Additionally, proposals envisioning compensation levels lower than those of predecessor contractors for the same work will be evaluated on the basis of maintaining program continuity, uninterrupted high-quality work, and availability of required competent professional service employees. Offerors are cautioned that lowered compensation for essentially the same professional work may indicate lack of sound management judgment and lack of understanding of the requirement.
As Joel has pointed out, that language suggests that the provision applies to recompetes. Yet the prescription seems to apply it to any service contract that will employ significant numbers of professionals.
There is no requirement to use the confusing boiler plate of 52.222-46. If you want to evaluate professional compensation under a prospective task order, write your own language.
And don't go overboard. Keep it simple.
- F
FrankJon
Jul 5, 2018 · 7y ago
On 7/3/2018 at 6:47 PM, Vern Edwards said:
While COs may, and have, evaluated professional employee compensation when awarding task orders, there is no requirement that they do so, and if they do so there is no requirement that they cite FAR 52.222-46, which is much too formal.
Vern: To be clear, I don't think anybody (including myself) suggested that 52.222-46 is mandatory when issuing a TORFP (this is the term OP used, by the way). I said that it's at the CO's discretion. I recommended usually performing, or at least leaving door open for performing, some kind of realism analysis. If the CO wants to do that informally, that's fine. If the CO thinks 52.222-46 applies, that's fine. Given that there is no FAR-wide definition of "negotiated contract," I stand by my "clueless" advice.
Here is what The Government Contracts Reference Book (4th ed.) says for "Negotiated Contract":
Quote
A contract awarded using a procedure other than sealed bidding. FAR 15.000. Procedures for awarding negotiated contracts are in FAR Part 15. Negotiated contracts may be awarded on a competitive or sole source basis. Smaller negotiated contracts are awarded using the simplified acquisition procedures in FAR Part 13. Contracts for commercial items are awarded using the procedures in FAR Part 12.
This says to me that the likes of Ralph Nash et al. think that the term "negotiated contract" applies beyond FAR 15.
And here's an example I found from Vern Edwards (2012 ed.):
Quote
Even with the labor and fee rates you must request certified cost or pricing data if the order exceeds $700,000 and if none of the exceptions applies. That's because certified cost or pricing data are required before the award of a "negotiated contract," and a CPFF LOE task order is a negotiated contract. See FAR 2.101 for the definition of contract, FAR 15.000 for the definition of "negotiated contract," and FAR 15.403-4(a)(1)(i) for the requirement for certified cost or pricing data. The price for CPFF LOE task orders is not established at the time of award of the underlying IDIQ contract. See FAR 15.401 for the definition of "price." The price is established after the award of the underlying contract -- prior to the award of the task order, whether CPFF term or LOE. The establishment of hourly rates for cost estimating purposes does not constitute establishment of prices for orders.
This tells me that Vern Edwards (2012 ed.) thought "negotiated contract" could apply specifically to 16.505 procedures, despite the fact that Vern Edwards (2018 ed.) confidently states:
On 7/4/2018 at 1:28 AM, Vern Edwards said:
While delivery and task orders issued pursuant to FAR 16.505 may be contracts as defined in FAR 2.101, I see no justification for saying that such orders are negotiated contracts as that term is explained and used in FAR 15.000 or used in FAR 22.1103.
- j
joel hoffman
Jul 5, 2018 · 7y ago
The general policy and prescription at 22.1103 “Policy, procedures, and solicitation provision” don’t align with the language in the Provision at 52.222-46, which seems to concern re-competing services that include meaningful numbers of professional employees.
Nonetheless, the expressed policy would logically seem to be applicable to other than IFB acquisitions -at least for recompeting services (and maybe for new services) -whether they be for a new stand-alone contract or for a task order under an ID/IQ contract.
Why would the government not be equally concerned about the realism of compensation plans for professional employees for a new contract as well as for a task order?
Granted, there are disconnects between the prescription at 22.1103 and the language in the Provision but the policy concerning realistic compensation plans and the stated concerns In the provision for recompeted services would seem to be valid for a task order or for a C-type separate contract.
So, should a contracting officer merely literally read and follow the FAR or try to understand the intent of the labor policy and reasonably apply it?
Not having access to a law library or to LEXIS, etc., I tried to follow the regulatory trail of the prescription and the Provision. I wasn’t able to view the older Federal Register volumes that cited in my various hardbound FAR’s. My oldest is from 1996. The Provision dates back to 1993 and the FR pages are dated 12/21/1992 (which I couldn’t download). The language and paragraph organization of the prescription in the 1996 FAR varies somewhat but still references similar scope of the policy.
- j
joel hoffman
Jul 5, 2018 · 7y ago
Note: I was composing my above post while Vern and the others were posting during the past hour or so. I agree that the CO should use their head to compose appropriate language to meet the intent of the policy if the application would not fit the wording of the provision.
The disconnect between the policy and the provision goes back to at least the 1996 FAR.
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
joel hoffman said:
Not having access to a law library or to LEXIS, etc., I tried to follow the regulatory trail of the prescription and the Provision. I wasn’t able to view the older Federal Register volumes that cited in my various hardbound FAR’s. My oldest is from 1996. The Provision dates back to 1993 and the FR pages are dated 12/21/1992 (which I couldn’t download). The language and paragraph organization of the prescription in the 1996 FAR varies somewhat but still references similar scope of the policy.
No, no, no. The guidance about evaluating professional employee compensation has been around since long before 1992. The current language appeared in the very first edition of the FAR as published in the Federal Register in 1983.
For deep background see GAO, Special Procurement Procedures Helped Prevent Wage Busting Under Federal Service Contracts in the Cape Canaveral Area, HRD-78-49, Feb. 28, 1978, https://www.gao.gov/assets/130/121756.pdf.
And see Kingston, "The Service Contract Act of 1965: A Review," Air Force Law Review 1978:
Quote
A new section has since been added to the DAR [Defense Acquisition Regulation] requiring special provisions to be included in solicitations where the services of professional employees are expected to be needed. The section is similar in purpose to that stated in GAO's report. It basically adds the salaries and overall compensation of professional employees to the solicitation's evaluation criteria. The section applies to negotiated contracts in excess of $250,000 where a “meaningful number” of professionals will be employed by the contractor to perform the services. The section also calls for the inclusion, in solicitations for such contracts, of the new DAR clauses which require contractors to submit for evaluation total compensation plans. If such salary plans are unreasonably low, the contractor proposals run the risk of nonselection.
http://digitalcollections.library.cmu.edu/awweb/awarchive?type=file&item=416461
Agencies have issued guidance about evaluating professional employee compensation since the late 1970s.
- j
joel hoffman
Jul 5, 2018 · 7y ago
Vern Edwards said:
No, no, no. The guidance about evaluating professional employee compensation has been around since long before 1992. The current language appeared in the very first edition of the FAR as published in the Federal Register in 1983.
For deep background see GAO, Special Procurement Procedures Helped Prevent Wage Busting Under Federal Service Contracts in the Cape Canaveral Area, HRD-78-49, Feb. 28, 1978, https://www.gao.gov/assets/130/121756.pdf.
And see Kingston, "The Service Contract Act of 1965: A Review," Air Force Law Review 1978:
http://digitalcollections.library.cmu.edu/awweb/awarchive?type=file&item=416461
Agencies have issued guidance about evaluating professional employee compensation since the late 1970s.
Thanks, Vern. I saw that there were earlier references than 1992 but I couldn’t access the 1992 FR background language I was trying to trace the source of the disconnect between the language in the provision and that in the prescription.
I’m not a student of the background of the timeframe that ID/IQ’ task orders have been used for acquiring services or for recompeting existing services. The language in the prescription is essentially the same as it is now, since December 1992.
I will study your citations if I can but am otherwise tied up the rest of today..
- C
C Culham
Jul 5, 2018 · 7y ago
Well since we have digressed from intent of the beginners section just an aside that is further digression.
What I found interesting in tracking the provision from 1983 to current is that the FAR doesn't address clerical and administrative personnel who could be in the same situation with regard to FLSA and SCA non-application. Makes me think the lobbyists were at their best when FAR was contrived.
- M
Moderator
Jul 5, 2018 · 7y ago
I'm going to look at this topic tonight. I'm too busy now.
- F
FrankJon
Jul 5, 2018 · 7y ago
bob7947 said:
I'm going to look at this topic tonight. I'm too busy now.
Vern has retracted his last comment toward me. I'll do the same.
- j
joel hoffman
Jul 5, 2018 · 7y ago
Ok, I investigated the links that Vern provided this morning, traces the origins of the policy and procedures concerning anti-wage busting to win service contracts and recompetes of services. As Vern indicated, NASA developed procedures; The GAO reported on the NASA procedures and successes; Defense Acquisition Regulations incorporated procedures that were similar in intent to NASA’s. The language is similar to the current provision.
I suspect that the language, still used today, predates common usage of task order contracts to acquire professional services or to recompete existing services.
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
FrankJon said:
Vern has retracted his last comment toward me. I'll do the same.
I didn't retract anything. I used a britishism. Bob must have deleted it. I still feel the same way.
Don't go back and quote stuff I said six years ago in different discussions. You don't write anything memorable enough to quote, and even if you did I wouldn't go back looking for it in an attempt to embarrass you. I don't do that to any of you, so don't do it to me. Deal with the ongoing discussion or get lost.
- F
FrankJon
Jul 5, 2018 · 7y ago
Vern Edwards said:
I didn't retract anything. I used a britishism. Bob must have deleted it. I still feel the same way.
Don't go back and quote stuff I said six years ago in different discussions. You don't write anything memorable enough to quote, and even if you did I wouldn't go back looking for it in an attempt to embarrass you. I don't do that to any of you, so don't do it to me. Deal with the ongoing discussion or get lost.
Are you serious right now, Vern? You're whining to me about fairness?
Do not baselessly deride me or others, then cry foul when people call you out for your contradictions and inconsistencies. You called my comment "clueless" for utilizing the same rationale you used six years ago in a different scenario. Give me a break. It is wholly fair that I pointed that out. Now you choose: Were you "clueless" in 2012, or has your thinking evolved on the matter? If the latter, explain why. You don't get to criticize then weasel out of being criticized for the same reason. You don't get to sanitize the paper trail to protect your image, then pretend like everything is OK. Your words matter. Be accountable, Vern.
This pattern you exhibit of ripping into others who post thoughtful comments that you disagree with is shameful. Your tit-for-tat exchanges and incessant need to get the last word are completely embarrassing for someone of your stature.
You're a contracting legend, for whatever that's worth. Show some damn respect to those of us who are here to learn from the best and help others.
- G
Guest PepeTheFrog
Jul 5, 2018 · 7y ago
Man alive! And to think, PepeTheFrog gets censored for saying the 8(a) program is based on race, and speaking plainly about its implementation...
As @Gordon Shumway would say, "This was an interesting read..."
@bob7947: Friendly advice, don't censor this particular thread. This is the magic stuff. Let it stay, let freedom ring!
Some frogs show up to watch the fur fly. Government contracts is mostly boring, boring stuff. It's fun to have some controversy and some differences of opinion so great that feelings get hurt. If feelings aren't hurt, does anyone really care? Think about it.
[munches popcorn]
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
@FrankJon:
You quote a six year old post out of context in an attempt to show that I have been inconsistent. Well, read that six year old quote again, and think. It looks like I was talking about a policy entirely within the scope of Part 15, cost or pricing data. I was not talking about policies---FAR 16.505(b) and 22.1103---that are beyond the scope of Part 15. My position on the matter in this thread doesn't contradict my earlier one. Arguably, a task order might be a negotiated contract for one purpose, but not for another.
My initial post did not "deride" you. I expressed frustration with the responses to a straightforward inquiry. "Oh, for Pete's sake" and "Get a clue." That crushed your feelings? When you came back at me I gave a polite, detailed explanation for my position, and heard nothing more from you. I told you to *** *** after you came at me with the supposed contradiction. What's happening now is nothing but you licking your wounds.
My complaint is that your lengthy response to a beginner was likely to send him or her down a road toward needless complexity.
I wrote the following in "The New Rules for Multiple Award Task Order Contracting," The Nash & Cibinic Report, June 1995:
Quote
The multiple award preference policy states that every awardee must be given a “fair opportunity” to be considered for the award of each task order in excess of $2,500. The proposed rule leaves the choice of evaluation factors to the CO's discretion. The CO need not publish a synopsis, solicit written proposals, or conduct discussions with awardees prior to the award of a task order, proposed FAR 16.505(b)(1). The rule precludes protests against task order award decisions. Agencies must appoint task order “ombudsmen” to handle complaints from awardees about task order selections, proposed FAR 16.505(b)(4).
Notwithstanding these liberal policies, it is not difficult to imagine Government procurement officials conducting a mini-source selection before the issuance of each task order. Some will almost certainly consider a more formal procedure to be necessary to ensure fairness. One can easily imagine requests for proposed task order “performance” plans or “management” plans, especially for task orders of significant dollar value. One can also imagine requests for extensive cost breakdowns, certified cost or pricing data, and proposal audits. If too complex and demanding, such procedures would significantly increase an agency's administrative costs, extend the lead time associated with task order issuance, and force awardees to incur significant costs in the preparation and negotiation of task order proposals.
Boy , was I right, or was I right? Just look at what you recommended:
Quote
On 7/2/2018 at 10:59 AM, MAY-D-FAR-B-WIT-U said:
my initial question is to find out if 52.222-46 applies to orders under 16.505 when the evaluation required by the clause was already performed during the award of the IDIQ?
It depends. In reality, it's up to the CO. Why do I say that? Let's break down the prescription at 22.1103.
It applies only to "negotiated contracts." According to FAR 15.000, a negotiated contract is:
A contract awarded using other than sealed bidding procedures is a negotiated contract
Therefore, a task order contract qualifies as "negotiated," not just FAR 15 contracts. See also the definition of "negotiated contract" in The Government Contracts Reference Book. So go to #2.
There's a $700,000 threshold. Is your task order over or under that? If over, continue to #3. (And if it's under, I don't think there's anything stopping you from continuing to #3 if you think it's appropriate.)
It applies when "services are to be provided which will require meaningful numbers of professional employees." Huh?? What is a "meaningful number"? This is why I say it's up to the CO. Any number can be considered "meaningful" or "non-meaningful" depending on perspective. This prescription is kind of ridiculous in this sense. Also, have you confirmed that these are "bona fide" professionals you're hiring, in accordance with FAR 22.1102? I've seen COs overlook this language, thinking the provision applies to all service contracts. In reality, it applies to only a sliver of the service contract pie.
Last, I'll point out that the Provisions & Clause Matrix indicates that this provision is not intended for commercial services. So there is another discriminator if you're looking for wiggle room.
So, if upon reading all of that, you think it applies, then it applies. But there's also a common sense aspect to this. Doing the evaluation required by this provision at the IDIQ level in a multiple award setting doesn't achieve much because the risks it is supposed to mitigate will return once the task orders are competed. That is, contractors may feel incentivized to under-compensate professional employees in order to win work. Unless this provision or similar price or cost realism language is in the TORFP, then they will have the flexibility to do just that.
When you're contracting for services in a competitive environment, it's usually a good idea to include some kind of "realism" evaluation language in the solicitation to protect the Government's interests (even if it's just "optional" language). Whether you do that through 52.222-46 or custom language is up to the CO.
Huh?
Bob has written that Congress passes too many acquisition statutes. He's right. But that's not the biggest problem in acquisition today. The biggest problem is those members of the workforce who lack the simplicity gene. There are easier ways to make sure that prospective task order contractors will pay enough to attract high quality professionals than invoking the FAR 52.222-46 boilerplate and all that goes with it.
I am criticizing you for answering a beginner's straightforward question with a bloated response likely to encourage him or her to do unnecessary work. A "thoughtful" comment would have included specific recommendations for a simple approach, an approach that would avoid the need for the price realism analysis that GAO requires with FAR 52.222-46.
Now, you can go on about me if you like. You won't be the first. But at this point you aren't contributing to the analysis of the problem posed by the OP. You want to help others? Try describing a simple approach.
Pass the salt, Pepe.
- M
Moderator
Jul 5, 2018 · 7y ago
Quote
Man alive! And to think, PepeTheFrog gets censored for saying the 8(a) program is based on race, and speaking plainly about its implementation...
That is not why your posts were deleted.
- R
Retreadfed
Jul 5, 2018 · 7y ago
On 7/3/2018 at 6:54 PM, MAY-D-FAR-B-WIT-U said:
we sometimes insert additional provisions when competing orders under 16.505 and in this case, we have.
FAR 16.505 requires agencies to include the procedure for awarding orders in the multiple award task order contract. Does your agency state in its contracts that it will include provisions that are not included in the contract in instructions for submission of task order proposals? If the ordering procedures do not inform contractors of this possibility in their contracts, what is your authority to "insert additional provisions when competing orders?
- R
Retreadfed
Jul 5, 2018 · 7y ago
FAR 16.505(b)(3) says that "If the contract did not establish the price for the supply or service, the contracting officer must establish prices for each order using the policies and methods in subpart 15.4. " This seems to support Vern's assertion that a task order may be a negotiated contract for some purposes and not for others.
- j
joel hoffman
Jul 5, 2018 · 7y ago
I’m sure that Congress passes too many acquisition statutes. However, it seems to me that there was and could be a real problem with “wage busting” for professional employees, who aren’t covered under the Service Contract Act. NASA was concerned and developed procedures to discourage it. The DAR picked up on it and it was adopted in the original FAR.
In my years with USACE, I dealt with many professional employees of service contractors for our client Installations, who had worked for many years at the installation, for various contractors, depending upon who won the follow-on contracts. These engineers and scientists generally have a deep sense of duty and loyalty to the mission and the installation and possess vast institutional knowledge. This is extremely valuable during development of design criteria and lessons learned for new design, design-build and construction programs/projects and in providing technical advice during source selections.
In my opinion, it is good public policy to protect them from wage busting during recompetes.
To me, the type of contract vehicle used for the recompete contract for those contract employees shouldn’t matter - whether by task order or a stand alone competition. I would want to discourage wage busting
- G
Guest Vern Edwards
Jul 5, 2018 · 7y ago
joel hoffman said:
In my opinion, it is good public policy to protect them from wage busting during recompetes.
Why not simply state that when competing for orders contractors may not reduce the wages paid to professional, administrative, and clerical employees in order to reduce prices?
- j
joel hoffman
Jul 6, 2018 · 7y ago
Vern Edwards said:
Why not simply state that when competing for orders contractors may not reduce the wages paid to professional, administrative, and clerical employees in order to reduce prices?
Ok with me.
But if the FAR uses a method developed by NASA for recompetes using a C-Type contract, why not use it for recompetes using a task order under an ID/IQ , D-Type contract? Just for simplicity’s sake? Not arguing. Just asking.
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
joel hoffman said:
But if the FAR uses a method developed by NASA for recompetes using a C-Type contract, why not use it for recompetes using a task order under an ID/IQ , D-Type contract?
FAR doesn't use "a method developed by NASA." FAR Subpart 22.11 does not prescribe any "method." FAR 52.222-46 prescribes a submission of information. Method is another thing entirely.
- G
Guest PepeTheFrog
Jul 6, 2018 · 7y ago
joel hoffman said:
it seems to me that there was and could be a real problem with “wage busting” for professional employees, who aren’t covered under the Service Contract Act. NASA was concerned and developed procedures to discourage it. The DAR picked up on it and it was adopted in the original FAR.
joel hoffman said:
In my opinion, it is good public policy to protect them from wage busting during recompetes
GAO's take:
"The Service Contract Act of 1965 protects all employees of service contractors from wage busting (lowering of wages and benefits by contractors in efforts to become low bidders) except bona fide executive, administrative, and professional employees. To discourage wage busting for professional employees, the National Aeronautics and Space Administration (NASA) and the Air Force designed special procurement procedures which were used for recompetition on three major contracts. In a review of wages and fringe benefits of 881 of 1,034 employees not covered by the act, no cases of wage busting were found on two of the three contracts, and only two cases were identified on the remaining contract. In the two cases, the contractor paid salaries requested on job applications, and there was no indication of intent by the contractor to wage bust. The procurement procedures influenced contractors to submit proposals based on paying wages and fringe benefits comparable to those paid under the prior contracts, and these factors affected the proposal evaluations. The special procurement procedures demonstrate that a policy directed towards discouraging wage busting is a viable alternative to proposed legislation that would include professional employees under the act."
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
HOW TO CONSIDER PROFESSIONAL EMPLOYEE COMPENSATION WITHOUT INVOKING FAR 52.222-46 WHEN GIVING MATOC CONTRACTORS A FAIR OPPORTUNITY TO BE CONSIDERED UNDER FAR 16.505(b) .
FAR 52.222-46, which is a solicitation provision, not a contract clause, and something of a jumble, requires that offerors submit “total compensation plans” accompanied by “supporting data.” The supporting data must include “recognized national and regional compensation surveys and studies of professional, public and private organizations.” The provision states that the government will evaluate the plan for (1) a sound management approach, (2) understanding of the contract requirements, (3) ability to provide uninterrupted high-quality work, (4) impact upon recruiting and retention, and (5) realism. FAR 52.222-46 has figured in 72 GAO decisions and five COFC decisions. The GAO has said that in the case of fixed price contracts the evaluation is, “in effect,” an evaluation of price realism. See Maxim Healthcare Services, Inc., B-412967.11, June 25, 2018.
FAR 52.222-46 covers two scenarios.
- The first scenario is one in which the procurement is a recompete and the issue is whether an offeror is proposing lower wages (salaries and fringe benefits) than are being paid by the incumbent, assuming that the incumbent has maintained a qualified and stable workforce. Payment of lower wages would be “wage busting,” which in 1978 the GAO defined as “lowering employee wages and fringe benefits by incumbent or successor contractors, to be low bidders or offerors on Government service contracts, when the employees continue to perform the same jobs.”
- The second scenario is one in which the procurement is new or the incumbent has not maintained a qualified and stable workforce and the issue is whether an offeror is proposing wages sufficient to establish and maintain a qualified and stable workforce. In this scenario, wage busting is not an issue.
When giving MATOC contractors a fair opportunity to be considered for the award of a long-term task order requiring professional work, it would be understandable that an agency might want to ensure that contractors propose wages adequate to the maintenance of a qualified, stable, professional workforce. The question is whether an agency providing a fair opportunity to be considered, and concerned about professional employee compensation, should invoke FAR 52.222-46 and its requirements or do something else---something less demanding, costly, and time-consuming than soliciting and evaluating total compensation plans and supporting data. What are the alternatives?
Keep in mind that FAR 16.505(b) does not require the solicitation of written offers or quotes. See FAR 16.505(b)(1)(ii)
Quote
The contracting officer may exercise broad discretion in developing appropriate order placement procedures. The contracting officer should keep submission requirements to a minimum. Contracting officers may use streamlined procedures, including oral presentations. If the order does not exceed the simplified acquisition threshold, the contracting officer need not contact each of the multiple awardees under the contract before selecting an order awardee if the contracting officer has information available to ensure that each awardee is provided a fair opportunity to be considered for each order.
See also FAR 16.505(b)(iii) and (iv) for orders that will exceed certain dollar thresholds.
And see FAR 16.505(b)(1)(v)(B):
Quote
Formal evaluation plans or scoring of quotes or offers are not required.
When complying with FAR 16.505(b) (or, for FSS contracts, FAR Subpart 8.4), my goal would be to keep submissions and the evaluation process as simple as possible, consistent with making a sound decision. I would want to avoid requesting and evaluating "total compensation plans" and supporting data, because that would be consistent with keeping submission requirements to a minimum.
Remember than an agency planning to consider professional employee compensation would have to announce that professional employee compensation will be an evaluation factor. Now, going back to the first scenario, discussed above, the agency could simply assume that since the incumbent’s workforce is qualified and stable the wages being paid are sufficient. In that case, the government could simply warn contractors that it will not countenance reductions of professional wages and will not select any contractor that intends to reduce wages.
Alternatively, the government could state that if a contractor proposes lower wages it must explain how it will maintain the workforce in the face of the reductions. This alternative approach would entail analysis and assessment of any such explanation, and the government will have to make a decision about the wisdom of the reductions and justify any decision to reject a contractor that plans to cut wages.
Going back to the second scenario, the government could do market research to determine what professional employees are being paid for the kind of work that will be required under the task order. It could then provide the findings of its research to the contractors under consideration and state that any contractor which plans to pay less must explain how they will maintain a qualified and stable workforce. Again, that would entail analysis and assessment of any explanation and justification of any decision.
In either scenario, the government should clearly state that it does not intend for the consideration of professional employee compensation to be or to require a price realism analysis.
The basic idea would be to avoid the requirements, burdens, and confusion of 52.222-46. I think that with a little creativity a CO could find ways consider professional employee compensation without becoming entangled in a solicitation provision of questionable value and meaning.
Keep it simple.
- C
Constricting Officer
Jul 6, 2018 · 7y ago
On 7/3/2018 at 4:19 PM, Vern Edwards said:
Oh, for Pete's sake. See FAR 22.1103. FAR 52.222-46 is a solicitation provision that is to be inserted in RFPs for new contracts. It has no bearing on fair opportunity procedures under FAR 16.505(b)(1). It does not apply when conducting competitions for task orders under MATOCs, which does not entail issuing an RFP, because it is not a new competition, but an order against an existing contract. FAR 16.505(b) does not require the issuance of a solicitation.
FAR is a mess. You have to make sense of it. Professional employee compensations should have been evaluated in connection with the award of the underlying IDIQ contract.
While I have enjoyed the read, I am surprised the conversation went past this post. The issuing of a DO/TO is against something already negotiated. If I have learned nothing more from this "gathering of the minds," it is to keep things simple. We have MATOCs, FSSs and NASA's SEWP (to name a few) to ease the administrative burden of federal contracting. The guidance to be innovative (FAR 1.102-4 (e)) has lead to these vehicles being available and we should not make things harder on ourselves.
- M
Moderator
Jul 6, 2018 · 7y ago
Vern said:
Quote
Oh, for Pete's sake. See FAR 22.1103. FAR 52.222-46 is a solicitation provision that is to be inserted in RFPs for new contracts. It has no bearing on fair opportunity procedures under FAR 16.505(b)(1). It does not apply when conducting competitions for task orders under MATOCs, which does not entail issuing an RFP, because it is not a new competition, but an order against an existing contract. FAR 16.505(b) does not require the issuance of a solicitation.
FAR is a mess. You have to make sense of it. Professional employee compensations should have been evaluated in connection with the award of the underlying IDIQ contract.
I agree. Congress, through FASA, gave agencies a way out of a complicated selection process. Don't revert back to it. If a program wants a source selection for an order, ask them if they want the work to start next week or next year. That may shut them up.
I have to go in a minute but one thing sticks out to me in the posts that I have read so far. It is the use of the words compete or competition in the award of an order under an IDIQ. I would use something similar to fair consideration of the IDIQ contractors.
I apologize for being so brief on a complicated and controversial subject.
- C
C Culham
Jul 6, 2018 · 7y ago
Vern Edwards said:
HOW TO CONSIDER PROFESSIONAL EMPLOYEE COMPENSATION
Might be better to start from the position of "WHY". I continue to do what some believe to be less than acceptable research on this subject and I now wonder if 22.1103 has more to do with price analysis than application of labor law. I say this on the basis of these random thoughts that I have yet been able to fully put together but I think they have bearing.
CAS speaks a lot to "negotiated contracts". TINA and the requirement for certified cost or pricing data could, might, depending, or may apply to a TO. Eerily the threshold of 22.1103 tracks to some extent with the threshold for cost or pricing data. (Question - what was the threshold in 1983?)
So back to "Why?" and keeping it simple. If my proposed TO award is going to be subject to certified cost or pricing data then I insert 52.222-46 and if not then I decide as a CO if I want to evaluate professional compensation otherwise and so state without using 52.222-46. Otherwise I do not mess with it other than what I might do in an effort to "Consider price or cost under each order as one of the factors in the selection decision." All said keeping in mind that an overruling decision on use of 52.222-46 for a TO on my part as a CO is if I had the provision in the solicitation for the parent IDIQ(s), what the pricing structure will be etc.
Other random thoughts that probably do not really matter as this thread progresses but all the same I feel they are worth mentioning, besides they were in a draft I was working on until the last few posts appeared so what the heck.
Vern Edwards said:
Why not simply state that when competing for orders contractors may not reduce the wages paid to professional, administrative, and clerical employees in order to reduce prices?
I would suggest that the wording be "reduce the salary/fee paid". Reasoning. FLSA provides that the positions mentioned are exempt for FLSA. FLSA and SCA work together and SCA provides that the positions listed as being exempted from FLSA as also exempt for SCA. Wording used for these positions discusses and emphasizes "salary or fee" and not wages in almost all cases.
Vern Edwards said:
FAR Subpart 22.11 does not prescribe any "method." FAR 52.222-46 prescribes a submission of information
Not a method as well? The provision states that the government will - "evaluate the plan to assure that it reflects a sound management approach and understanding of the contract requirements. This evaluation will include an assessment of the offeror’s ability to provide uninterrupted high-quality work. The professional compensation proposed will be considered in terms of its impact upon recruiting and retention, its realism, and its consistency with a total plan for compensation." GAO decisions seem to conclude that this is a method that must be used when 52.222-46 is in the solicitation.
Vern Edwards said:
FSS contracts, FAR Subpart 8.4
Never! Haven't we already ruled out commercial item contracts? If yes by my read all FSS contracts are commercial item contracts so forget evaluating professional compensation on these bad boys all together! Keep it simple, right?
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
Constricting Officer said:
If I have learned nothing more from this "gathering of the minds," it is to keep things simple. We have MATOCs, FSSs and NASA's SEWP (to name a few) to ease the administrative burden of federal contracting.
bob7947 said:
Congress, through FASA, gave agencies a way out of a complicated selection process. Don't revert back to it.
It's too late. I did a quick search for GAO task order protest decisions and found 195 (including protests of FSS order competitions). I searched among them for "RFP" and found 115. I then searched for "competitive range" and found 39. I searched for "discussions" and found 78. I searched for "final proposal revision" and found 29. I searched for "proposed plan" and found 35. I found the following, or something like it, in many of the decisions:
Quote
With regard to competitions for task and delivery orders under IDIQ contracts, FAR §16.505 does not establish specific requirements for discussions; exchanges with offerors under task order competitions, like other aspects of such a procurement, must be fair, equal, and not misleading... Where, as here, however, an agency conducts a task order competition as a negotiated procurement, our analysis regarding fairness will, in large part, reflect the standards applicable to negotiated procurements.
What those results tell me is that the acquisition workforce is bound mind, hand, and foot to the FAR Part 15 Process Model, and they cannot free themselves. Many of them are incapable of undertaking simple measures. They cannot envision and design simpler, faster processes.
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
C Culham said:
Question - what was the threshold in 1983?
$250,000.
- C
C Culham
Jul 6, 2018 · 7y ago
Vern Edwards said:
$250,000.
And TINA was $100,000.
- j
joel hoffman
Jul 6, 2018 · 7y ago
Constricting Officer said:
While I have enjoyed the read, I am surprised the conversation went past this post. The issuing of a DO/TO is against something already negotiated. If I have learned nothing more from this "gathering of the minds," it is to keep things simple. We have MATOCs, FSSs and NASA's SEWP (to name a few) to ease the administrative burden of federal contracting. The guidance to be innovative (FAR 1.102-4 (e)) has lead to these vehicles being available and we should not make things harder on ourselves.
Yes, the conversation went farther. The original poster clarified, on Tuesday at 5:54 PM (CDT), that he or she was referring to a situation where 1) the agency encourages offerors to submit lower prices than the schedule prices and/or 2) the task order includes additional classifications of professional personnel that are not covered by contract established rates.
My first reply, on Wednesday at 5:54 AM (CDT) was in response to that clarification by the original poster. In the specific situations described in the clarification, the government would request task order proposals from multiple award task order contract/MACC/Schedule/pool members/etc. contract holders. If the vehicle is a single award task order contract, the government would also request a proposal, although There wouldn’t be competitive pressure to “wage slash”.
I am on the road today so cannot take the time to research the reference. However I believe it is DOD acquisition policy that, when using the GSA schedules or another ID/IQ contract vehicle, the government should encourage or request discounts from the schedule/ID/IQ contract rates. I believe that it is or was part of the “Better Buying Power” Initiative *.
It doesn’t matter so much to me how it’s done but the government should be concerned about the possibility of wage slashing for professional employees when recompeting for existing services.
EDIT: here is one example of DoD policy concerning seeking discounts when using the GSA Schedules:
https://www.acq.osd.mil/dpap/policy/policyvault/USA004263-15-DPAP.pdf
*This wasn’t necessarily part of “Better Buying Power”. Having refreshed myself somewhat concerning the Better Buying Power initiative, those policies do not necessarily make things easier for the acquisition force...
- C
C Culham
Jul 6, 2018 · 7y ago
Vern Edwards said:
the acquisition workforce is bound mind, hand, and foot to the FAR Part 15 Process Model, and they cannot free themselves.
Exactly and from top to bottom as in many cases bosses demand that the workforce make it so and prevent them using the innovation that the FAR allows!
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
C Culham said:
And TINA was $100,000.
No. It was $500,000.
- C
C Culham
Jul 6, 2018 · 7y ago
Vern Edwards said:
No. It was $500,000.
There was a point I was going to take my thoughts off line and go do something else so sincerely an apology for belaboring but in 1962 it was $100,000 I think....
https://www.gpo.gov/fdsys/pkg/STATUTE-76/pdf/STATUTE-76-Pg528.pdf
I will just sit back and read for a while and leave the too much specifics alone!
- G
Guest Vern Edwards
Jul 6, 2018 · 7y ago
The original 1962 threshold was $100,000. It was raised to $500,000 in 1982. Then it was reduced to back to $100,000 in 1984. Then it was raised back to $500,000 in 1991, and it's been increased from there. At present, the threshold is $2,000,000.
If you don't believe me I can provide statutory citations, or you can look up the history in Defective Pricing Handbook, 2018 Edition, § 2.4, by David Z. Bodenheimer. Essential reading for those who want to understand the cost or pricing data law.
- C
C Culham
Jul 6, 2018 · 7y ago
Vern Edwards said:
If you don't believe me
Always believe you, but not always agree! Thanks for making the effort to give me the trail!