Reminder That Human Trafficking Is a (Very Bad) Thing
As we told readers more than three years ago, the chances are that your government contract has a clause in it that prohibits human trafficking. Which is a great goal and we’re sure you would never, ever, violate that contractual prohibition.
Do you have that contract clause?
It’s FAR 52.222-50 (“Combating Trafficking in Persons,” March 2015). Why don’t you go look and see if you have it? We’ll wait.
You probably have it, because the clause is required to be inserted in every single solicitation and contract issued by the government. So let’s assume you’re going to find it—at least, it will be listed in Section I of your contract, which is for clauses incorporated by reference.
Good. Now: have you read it?
Yeah, you’re probably going to want to read it. It’s long and perhaps you don’t think it really applies to you—because you’re not that kind of company—but we suggest you read it anyway. It says more than you probably think it does.
We mean to say that the clause contains more compliance requirements than simply “don’t traffic in human beings.” Because if that’s all it said, most of us would be good and we wouldn’t need to even write a blog article about the clause.
But oh no, dear readers, it says more than you think it does.
Among many other things, the contract clause 52.222-50 prohibits “procuring commercial sex acts during the period of performance of the contract.” Anywhere. Even where procuring such may be legal.
It used to be that what happened on R&R stayed on R&R, but no longer. Now what happens on R&R can really cause some corporate problems.
Read our article (link in the first sentence) about what the clause requires, in terms of compliance. Read the clause itself. Understand what you need to do, and understand what your employees, agents, and suppliers cannot do.
After reading all that, you might be prepared to appreciate this DoJ press release, in which it was announced that a “contractor for the Department of Defense” was sentenced to six years in prison for “engaging in commercial sex with a minor in the Philippines.” The press release provided the sordid details, to wit—
On April 19, James Marvin Reed, 62, pleaded guilty to engaging in illicit sexual conduct in a foreign place. According to court documents, from in or about September 2007 until in or about December 2007, Reed, then 52 years old, engaged in commercial sexual intercourse on multiple occasions with the then 14-year-old victim, and impregnated her, while he was working in the Philippines as a contractor for the U.S. Department of Defense. In 2016, he was arrested by Philippine authorities and returned to the United States for prosecution.
Of course, nothing like that would ever happen to any of your employees, who are all upstanding citizens of the highest levels of integrity.
But are you sure of that?
How do you know?
How do you know for sure?
TINA Sweeps Again and Again
Readers may recall that we did a couple of articles about TINA “sweeps” about a year ago. In the second article we discussed allegations that BAE Systems “defectively priced” a proposal to definitize a UCA and we used the allegations and the chronology of events (as established by the court’s findings) to look at TINA sweeps and when they should be performed.
(By the way, if you are getting confused by the acronyms we suggest you go read those two articles before continuing with this one.)
In that second article we opined that “it makes much more sense to perform sweeps just before the price agreement date. Do one complete sweep, identify any changed cost or pricing data, and disclose the changes as the final part of negotiations. Then execute the CCCPD right away. Risk is minimized and no further sweeps are necessary.” We still think that was good advice.
In related news, DoD issued a policy memo on June 5, 2018 entitled “Reducing Acquisition Lead Time by Eliminating Inefficiencies Associated with Cost or Pricing Data Submissions After Price Agreement (‘Sweep Data’).” Long story shortened, the memo discusses the curious phenomenon of a contractor submitting cost or pricing data after the date of price agreement as part of its efforts to ensure that the cost or pricing data to which it’s certifying is actually accurate, complete, and current. The problem is—as we noted in our articles—submitting cost or pricing data after the price agreement date does not mitigate the risk of defective pricing. Or at least, not by very much. Based on the memo's language, the Director of Defense Pricing/Defense Procurement and Acquisition Policy was really concerned about the issue of post-negotiation contractor sweeps; his concern was that those contractor sweeps can unduly delay the execution of the Certificate of Current Cost or Pricing Data and thus delay issuance of a contract.
Remember, as we told you, we’re measuring PALT now. And anything that increases PALT is a bad thing. The memo was issued to tell contractors to stop post-negotiation sweeps and get those CCCPDs executed ASAP.
In fact, the memo states that contractors that provide untimely submissions of sweep data may have estimating system deficiencies. Those can get expensive.
Further, the memo directs DoD contracting officers to request executed CCCPDs “no later than five business days after the date of price agreement.”
Note that DPAP issued a revision to that June 5th Class Deviation (dated June 7, 2018) that made some minor wording changes which did not affect the substance of the policy direction. Make sure you refer to the June 7th memo and not the June 5th memo when discussing how you are going to comply. Nitpickers abound.
What does this mean?
It means that you need to perform your sweeps as negotiations are happening, so that you can confidently execute the CCCPD and meet the five-day deadline. It's really that simple. You need to change whatever processes you need to change in order to make that happen, because if you don't meet the deadline you may find yourself with an estimating system deficiency--and perhaps an irritated contracting officer.
Over at WIFCON, the usual suspects have been debating this new policy guidance. Many folks don’t care much for it.
Many people do not agree with our position that post-award sweeps do not effectively militate the risk of defective pricing, which we maintain ends on the date of price agreement (or other effective date to which the parties may agree). Nonetheless, we continue to believe that if you want to address defective pricing risk, then you need to do the sweeps earlier. If you do the sweeps earlier, then you are going to be better prepared to meet the new five-day deadline.
There shouldn’t be anything extraordinarily controversial about that.
Editor's Note: This article has been edited to remove a quote from WIFCON at the individual's request.
|
Long Term Agreement Price Reasonableness
Contractors enter into Long Term Agreements (LTAs) in order to establish firm pricing for future requirements. LTAs are good things, because you can achieve volume discounts today based on the expected total volume of orders expected over the contract's duration. In contrast, if you are just issuing individual Purchase Orders then each one stands alone in terms of pricing; you get the price associated with the volume of the PO.
In addition, if you enter into a LTA you only have to establish price reasonableness once. You can compete one time and award the low bidder (or best value bidder) an LTA, and then you can use that price reasonableness determination to support your pricing for years to come. (Although we have seen DCAA take the position that price reasonableness must be evaluated annually; which kind of defeats the purpose. If your DCAA or DCMA has taken that position, call us because we know how to solve that one.)
All in all, LTAs are good things but, if the government waits until you propose LTA pricing in a proposal submitted in response to an RFP, then DCAA may want to review information that’s a year (or more) old at that point. That can delay the audit and the audit report and the negotiation—and that impacts PALT.
Thus, DCAA issued MRD 18-PSP-002(R) on 15 February 2018—though for some unknown reason it took the audit agency until June to actually publish the audit guidance on its website. The audit guidance clarifies that auditors can review the reasonableness of LTA pricing independently of a government solicitation. In other words, a contracting officer can request a DCAA review of LTA price reasonableness before the LTA pricing is incorporated into a contractor cost proposal.
According to the MRD, there are four preconditions that need to be in place before the auditors can perform an audit. They are:
-
The subcontract proposal has been approved by the appropriate subcontractor management.
-
The prime contractor has submitted the subcontract proposal to the Government with an assertion from the prime contractor’s management that it intends to award an LTA with the subcontractor and identifies the benefit of the LTA to the Government
-
The subcontract proposal is adequate for examination based on the requirements set forth in FAR Subpart 15.4, Contract Pricing
-
The Contracting Officer has determined that subcontract audit support is required based on DFARS PGI 215.404-3, Subcontract pricing considerations
Importantly, it seems that DCAA envisions that the contractor will engage with its contracting officer (and the auditors) prior to negotiating and finalizing the LTA pricing. Based on what we see (above), the prime contractor will request a proposal from the LTA supplier and then submit it to a contracting officer for … what? Not approval.
The CO should not be approving a commercial agreement between a prime contractor and its subcontractors. Given that there is no prime contract is place (and not even an RFP), there is no advance consent requirement in place. So we don’t know what the CO is supposed to think when they receive a notice of intent to award an LTA. Further, it’s not clear to us which CO has the authority to request DCAA audit support in the circumstances in which this is all suppose to take place. Certainly it's not the PCO. Perhaps it's the ACO? But if so, how was that authority assigned?
Nevertheless, there is now an official path to having governmental review of proposed LTA pricing, and presumably acceptance of price reasonableness, independently from any proposal submitted in response to an RFP.
We don’t know what would happen if DCAA determined that the proposed prices were not reasonable. We mean … it would definitely be a flag that there will be future problems with use of the LTA. But what remedy would the CO have, since the costs would not have been charged to any government contract at the point at which a DCAA auditor would be opining on price reasonableness?
Questions. We have so many questions....
Anyway, this is the plan. Don’t mind our questions; you should move briskly forward to solicit LTA pricing because, despite DCAA’s ostensible role in the process, having LTAs is definitely the smart move.
DoD Implements New TINA Threshold—Again and Again
It’s not like we want to keep talking about this, honestly. We’ve written and published article after article, discussing the increase to the threshold at which obtaining certified cost or pricing data is required (and below which obtaining CCOPD is prohibited) that was written into public law in the 2018 National Defense Authorization Act (NDAA) and now must be implemented by those agencies subject to that law. Interestingly, it’s been the civilian agencies not subject to NDAA that have been the quickest to take advantage of the new TINA threshold; whereas the Department of Defense has chosen a slower and less obvious route.
For example, whereas the NDAA directed that the micropurchase threshold be increased to $10,000, the DoD has chosen to issue a Class Deviation that increases it only to $5,000 (in normal circumstances). Similarly, whereas the Department of Energy has issued a Class Deviation to increase the TINA threshold to $2 Million, the DoD has issued multiple Class Deviations (that supersede each other) in attempts to do the same thing.
For example – and as we told readers – DoD issued Class Deviation 2018-O0012 (April 13, 2008) to implement the NDAA threshold. All was well with respect to new contracts awarded after 1 July 2018, but nothing was said about existing contracts. The DOE Class Deviation addressed existing contracts, and invited contractors to request contract modifications to implement the new thresholds “without consideration.”
Perhaps it was only a timing issue. Perhaps DOE simply had more time to think about it than DoD did.
But then DoD issued Class Deviation 2018-O0015 (June 5, 2018) – which superseded 2018-O0012 – and rectified the oversight by providing additional clauses that can be used to modify an existing contract “without consideration” that would raise the TINA threshold with respect to subcontractor cost or pricing data. The Class Deviation stated—
In the case of a change or modification made to a prime contract that was entered into before July 1, 2018, the threshold for obtaining certified cost or pricing data remains $750,000, with the following exception. Upon the request of a contractor that was required to submit certified cost or pricing data in connection with a prime contract entered into before July 1, 2018, the contracting officer shall use the clauses provided in Attachment 1 of this deviation … to modify the contract to reflect a $2 million threshold for obtaining certified cost or pricing data for subcontracts entered into after July 1, 2018.
So while it took a couple of tries for the folks at DPAP to get it right, at the end of the day we should be happy that the Class Deviation(s) were issued and that contractors have a clear path forward to get their contracts modified to align TINA requirements with the public law.
If you can’t figure it out by this point, we suspect you’ll need to hire somebody to assist you. It will be an investment well worth making.
|