Small Business Stuff
In our last article, we asserted that the FAR Councils were “years behind” in implementing regulatory rule changes promulgated by the Small Business Administration (SBA) in the Federal Acquisition Regulation. For those that may not know, the SBA promulgates its rules in Volume 13 of the Code of Federal Regulations (CFR) but the FAR is found in Volume 48 of the CFR. Each carries equal regulatory weight, except that it is the FAR Part 48 contract clauses that, by and large, end up in government contracts. Thus, it’s important that the FAR Councils work hard to keep 48 CFR Part 19 (“Small Business Programs”) consistent with what the SBA is saying over at 13 CFR. They haven’t done their jobs.
Evidence for our assertion can be provided. For one recent example, check out CAAC Letter 2019-1. Again, for any readers that may not know, the Civilian Agency Acquisition Council is one of the two Councils that make up the group that maintains the FAR and issues regulatory revisions (the other is the Defense Acquisition Regulation Council)—collectively known as the “FAR Councils.” For those that want to know more about these groups, here’s a link to FAR 1.201.
Anyway, let’s discuss CAAC Letter 2019-1. It authorizes (civilian) agencies to “implement regulatory changes made by the Small Business Administration to limitations on subcontracting in its final rule published in the Federal Register at 81 FR 34243 on May 31, 2016.”
Stop right there. Read the date on which the SBA published its final rule.
That’s right. It was nearly three years ago.
And since that time, crickets from the Councils whose job it is to align the FAR with the rest of the Code of Federal Regulations.
Nice job there, folks.
Meanwhile, “Agencies are advised to review any relevant clauses in their supplement and take any action that is appropriate. Once processed, agencies are requested to share the deviation widely among their workforces to ensure full awareness of and compliance with the revisions to the limitations on subcontracting.”
Meanwhile, “It is recommended that the deviation be made effective until the FAR is amended by the FAR case.” You know, that same FAR Case opened in 2016 that hasn’t actually been finalized yet. So in the meantime, just keep on deviating from the FAR in order to implement the rules and regulations of our sister agency at SBA. Because … the rule-making machinery isn’t working well today—nor has it for the past three years.
Onto a related topic: Small businesses and innovation.
Innovation is something we’ve written about before. Many times. (Do a keyword search from the home page.)
A recent article posted at DefenseNews.com (by Jill Aitoro) got us thinking. Ms. Aitoro’s article reiterated a “Twitter storm” by Trae Stephens, a former employee of Palantir Technologies and, more recently, co-founder of Anduril Industries, a company in Orange County, California, “created by tech innovators on a mission to solve critical defense problems, Anduril’s business model brings Silicon Valley ingenuity and funding to defense.” (According to the company’s website.)
Mr. Stephens apparently was responding to comments from Ellen Lord (Under Secretary of Defense for Acquisition and Sustainment) in which she “expressed concern … with the ability of innovative small businesses to secure their [information] systems.” Mr. Stephens took issue with those comments. He asserted that “This is yet another example of the common misuse of the term ‘small business’ across the Department of Defense.”
The comment that got us thinking though, was this: “There is a huge difference between a low-growth/low-headcount business and a high-growth/product-focused tech startup. We need to stop lumping these together.”
In other words, not all small businesses are the same! Treating every small business as being the same ignores the fact that some small businesses are not high-tech, innovation-focused entities. They are the traditional “mom-and-pop” businesses that, so often, supply machining and finishing services. (That’s not to say that those entities don’t innovate; but they are innovating “within the box,” so to speak.) In contrast, other small businesses are high-tech, focused on disruptive innovation. Those are the small businesses that will drive the future of defense.
Mr. Stephens discussed the recent USAF “pitch day” in which some small businesses received SBIR contracts in less than 15 minutes, simply based on their pitches. That’s a great thing! But Mr. Stephens pointed out that more than 50% of the companies invited to the “pitch day” lacked venture capital funding. He also noted that the contracts awarded were “non-recurring and average less than $100,000” in value. Ms. Aitoro reported that he also stated in an interview that “In addition, most contracts were for cyber and services – not product development. Not to diminish the importance of cyber and services, but were those contracts breaking new ground? The work could probably be performed by any number of companies.”
Moreover, he noted, Northern Virginia companies outnumbered California companies by three-to-one, and that “almost half” the companies at “pitch day” were founded more than 10 years ago. Ms. Aitoro reported that he amplified on his Tweets with the statement that those companies were “not exactly the definition of a ‘Silicon Valley startup.’ Now, innovation is not isolated to California, but it appears the winners here follow[ed] a pretty standard playbook for Pentagon small business contractors in both the scope of work and the makeup of the businesses.”
In other words, according to Mr. Stephens, the companies at the USAF “pitch day” were largely run-of-the-mill small Pentagon contractors that were not very likely to be the high-tech innovators that DoD says it’s looking for. He summed up his position thusly: “… an alien race looking down would reasonably think that it is the official policy of the U.S. government to encourage small businesses to not become large or successful businesses.”
He also said: “If you’re serious, prove it. Innovation theater is great (and easy), but we need to start writing meaningful contracts to new entrants with the skills/technologies that the DOD lacks.”
In related news, the Small Business Administration has announced its “SBIR Road Tour” with the goal of “seeding America’s future innovations”™. Let’s look at the planned stops on the Road Tour.
Oh, look. There are no stops planned for California. None for Oregon or for Washington.
Hmm, guess there are no small business innovators located in those states …
Meanwhile, the Silicon Valleys of Kansas, Oklahoma, South Dakota, and North Dakota each get a stop on the tour.
Changes: Turn and Face the Strange
Lots going on these days. I’m finishing my six-week “Financial Management of Government Contracts” course later this week. I’ve started editing the second LexisNexis reference book. One of my clients is headed into arbitration. And I’ve got international travel coming up in May, June, and July. (That’s three trips, not one long trip.)
Oh, and I should mention that the Society of Corporate Compliance and Ethics has accepted my proposal to present at September’s Compliance and Ethics Institute. My presentation will be entitled “"Taking a Dynamic Approach to Compliance Risk Assessments for U.S. Government Contractors". That presentation has to be created and turned in to the conference staff well before the Institute starts.
Finally, I feel the need to write a couple of blog posts each week. Given the foregoing list of other activities, please forgive me if production slips a bit.
Moving on ….
Today’s article notes recent changes DCAA has made to certain audit programs.
-
Testing of Paid Vouchers. (Link: here.) Don’t let the name fool you, these can be very tough audits—testing supplier payments, labor and timekeeping, and other direct costs.
-
Truth in Negotiations Compliance. (Link: there.) As most of us know, DCAA intends to perform more of these audits as the audit agency ramps down from the frenzy associated with “incurred cost submissions” (aka “proposals to establish final billing rates”). Accordingly, we recommend scanning the revised audit program as a refresher.
DCAA also updated audit programs associated with contract terminations. If you have had a recent termination for convenience, we suggest you check out the appropriate audit program.
|
Regulations – New and Old
Most of us in this crazy business remember Executive Order 13771, issued January 30, 2017—literally days after President Trump took office. That E.O. called for executive agencies—including the Department of Defense—to eliminate two old regulations for every new regulation issued. The impact of that E.O. was to effectively freeze agency rule-making while rule-makers sorted things out. Of particular note was the impact to the FAR Councils and, most especially, to the DAR Council. For quite some time after the E.O. was issued, rule-making just … stopped.
Of course, lawsuits were filed. This is America; lawsuits are our national public discourse. One suit called the E.O. "unconstitutional, illegal and stupid." Fourteen states filed amicus curiae briefs, arguing that the E.O. fell within Presidential authority and would benefit state governments. (Bet you can guess which ones filed the briefs.) That suit was dismissed by the DC District Court, which found a lack of standing. (The suit was subsequently revived.)
More recently, another lawsuit was filed, this time by the state of California, joined by the states of Minnesota and Oregon. The suit argues that the E.O. "harms the states by preventing, delaying and discouraging federal regulations addressing public health, safety, and environmental concerns." As far as we know, nobody has yet argued that the E.O. prevents the executives agencies with complying with public laws, such as the annual National Defense Authorization Act, that require new rules to be promulgated—often within specified time limits.
Meanwhile, after years of paralysis, the executive agencies seem to have found a path forward. We’ve noted that the DAR Council has managed to eliminate several regulations in the past year or so. On April 1st, in what was definitely not an April Fool’s Day trick, DFARS Case 2018-D059 was issued as a final rule. The final rule eliminated two words (“general public” and “non-governmental entities”) from DFARS Section 202.101.
But it counts!
On that same day—literally 35 years to the day after the FAR was first issued—the DAR Council also published four other final rules plus an additional three proposed rules. It’s not exactly “2 for 1” but, you know, it’s something. Perhaps nobody will notice.
We are not going to discuss each proposed and final rule in this article. But we will point out one or two that seem to bear some significance.
DFARS Case 2018-D065 (final rule) implements “section 824 of the National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2019, which amends section 893 of the NDAA for FY 2011 … regarding consent to subcontract requirements. Specifically, section 893 requires contracting officers to have written approval from the program manager prior to withholding consent to subcontract for DoD contracts with contractors that have approved purchasing systems, as defined in [FAR] 44.101.” So if you have an approved purchasing system, not only are some actions not subject to consent requirements, but the ones that are should not be held up by a contracting officer unless the program manager agrees. That’s a good thing, in our view.
DFARS Case 2017-D024 (proposed rule) would, if implemented as drafted, “implement [Sections 829 and 830] of the National Defense Authorization Act for Fiscal Year 2017 that requires the preference for the use of fixed-price contracts in the determination of contract type, requires review and approval for certain cost-reimbursement contract types at specified thresholds and established time periods, and requires the use of firm fixed-price contract types for foreign military sales unless an exception or waiver applies.” Essentially, the proposed rule would impose additional approval requirements if a contracting officer believes that an other-than-fixed-price contract type would be appropriate at certain dollar thresholds. Cost-reimbursement contracts valued at more than $50 million would require Head of Contracting Activity (HCA) approval if awarded before 01 October 2019; and cost-reimbursement contracts valued at more than $25 million would require HCA approval if awarded after that date. Also, the proposed rule would mandate that every FMS contract award must be firm, fixed-price (FFP) type.
Is the proposed rule a good thing? Not in our view. It adds an additional delaying step in awards of major weapon system contracts, many of which are often R&D or LRIP—which do not easily lend themselves to fixed-price contracting. For an example of what can go wrong, check out our many articles on Boeing’s KC-46a Pegasus aerial refueling tanker. Further, mandating that every single FMS contract must be FFP implies that no customization can or should be done to the product slated for export. In our experience, that implication is unrealistic.
All that said, the DAR Council is simply following Congressional direction. What can they do? What can you do if you don’t like the proposed rule? Not much. We mean, you can write in, objecting to the rule as drafted. And perhaps you should do so! But we strongly suspect the DAR Council will collectively shrug their shoulders and tell you they are just following Congressional direction. Then the final rule will be promulgated without much in the way of revision. Because that’s how the machine works. (When it works at all.)
Well, that last couple of sentences ends things on a bit of a downer, doesn’t it? We didn’t mean to do that!
In related news, the FAR Councils are years behind implementing SBA rule revisions. We’ll have a blog article on that uplifting topic soon!
On Being a Consultant
For the past three years, on and off, we have been supporting a small business located in the Pacific Northwest. We were first contacted by internal counsel, who relayed some concerns. That counsel was employed by a large aircraft manufacturer, headquartered in the Northeast. It turned out that the small business was actually a subsidiary of the large aircraft manufacturer.
That small business had been doing business the same way for many years. About half its business was commercial and the other half was government; but the government work was 100% competitively awarded FFP subcontracts so differences between the government and commercial work were minimal. Even when that small subsidiary performed a FFP “subcontract” directly for its Northeastern headquarters, not much was different in terms of how the work was priced, or accounted for, or billed.
Now, you might be concerned (as we were) that perhaps treating inter-organizational work as FFP wasn’t strictly in accordance with the requirements of the FAR cost principle at 31.205-26(e), but we were told not to worry about that issue, because Northeastern headquarters had directed its buyers to treat all inter-company work as being a subcontract and, moreover, that all subcontracts were to be FFP type. The direction was that all suppliers were to be treated as being arms-length subcontractors, even if some weren’t really so arms-length. That was the direction, and it was faithfully followed by the buyers in the Northeast with respect to this particular “subcontract” with a small business in the Pacific Northwest, even though that small business was in reality a subsidiary.
Accordingly, the small PNW business had received a FFP subcontract from Northeastern HQ for a piece of an aircraft that was still in development.
You probably know how we feel about that situation. We’ve written about it before. We wrote “… the subcontract type has to be appropriate. If every subcontract is FFP, that’s not necessarily a good thing, especially in a development environment. You can usually tell if the contract type was appropriate by looking at post-award change order activity.”
Our point of view on choosing the correct subcontract type is informed by our experience. Consistent with what our experience tells us would be the case, the Northeast “prime contractor” made a number of changes along the way, and so the small business “subcontractor” generated quite a few change order notifications and asked for its firm, fixed-price to be increased to compensate it for the changed work. The “prime contractor” was reluctant to admit its changes were causing cost impacts and the parties essentially were at a stalemate regarding the appropriate value of the equitable adjustments to be made.
Meanwhile, the large Northeast aircraft manufacturer was acquired by an even larger defense contractor (one of the “five families” at the top of the defense contracting pecking order). That mega defense contractor had its own policies with respect to “subcontracting” between affiliated entities—policies that were more aligned with the requirements of 31.205-26(e)—and consequently that FFP “subcontract” needed to be treated as a cost-plus-no-fee inter-organizational transfer. In essence, the FFP “subcontract” needed to be reformed, and priced based on actual costs incurred to date plus an estimate of allowable direct and indirect costs to be incurred.
The challenge, of course, was that this small business didn’t have an “adequate” accounting system, and thus both its actual costs incurred as well as its estimates of future direct and indirect costs to be incurred were suspect.
That’s where Apogee Consulting, Inc. came in.
We entered into a nearly three year-long attempt to enhance the small business’ accounting system to adequacy, so that it could price, account for, and bill, its actual, allowable, costs to what had been its “prime contractor” but what was now a sister division within the mega defense contractor’s empire. To be clear, our role was advisory and the heavy lifting was done by some of the people who worked at the small business. These individuals had long careers within government contracting. A couple had been long-term employees of a DOE O&M/M&O contractor. One was a CPA with years of government accounting experience. Another was an attorney trained at the GW School of Law in government contracts. They were knowledgeable and experienced but, as is so often the case, they didn’t have the bandwidth to do their jobs plus write policies and procedures and instructions, plus review spreadsheets and job aids, plus reconcile transactions to ensure the cost allocations were accurate. That’s what we did. We would visit for a few days, review the work that had been done, make suggestions on additional work to be done, review policies and procedures, make suggested revisions and, in general, try to push the project along. Then we would come back a few months later and do the same thing.
In addition, we strategized with program management, contracts, and financial management on how to convince the former “prime contractor” that (a) the small business’s costs were accurate and compliant, and (b) what the budget should be (going forward) for the cost-type inter-organizational work that was being performed. You might be surprised (as we were) to learn that the “prime” buyers were resistant to changing the subcontract type, or to admitting that the price they had budgeted in their Estimates-at-Completion—which was the firm, fixed-price they had initially awarded before the myriad changes—was in need of an increase.
The buyers at the “prime” were so reluctant to change the way it had always been done that they called in DCAA to audit their own sister division, to make sure that small business “subcontractor” wasn’t somehow trying to overbill them.
Really. They called in DCAA on their own people. That’s how far out-of-touch with reality they were.
But by this point, that small business was ready to go and DCAA had no findings. (To be clear: our contribution to that outcome was small; the audit support was executed by the people at the local business. Dealing with auditors was something they could do and they did it well.)
At this point, after three years of effort, the small business in the Pacific Northwest was ready to price, and account for, and bill, its actual, allowable, costs to its sister division located in the Northeast.
Mission accomplished!
And then that small business located in the Pacific Northwest was sold to a venture capital firm.
Everything that we had done needed to be undone. That cost-plus-no-fee inter-organizational transfer budget needed to be recast as an FFP subcontract—albeit at a higher price than was originally awarded. That task took some negotiating, for sure. As one person close to the action wrote me, “As much work as it was to turn [the subcontracts] into Cost Type, it was an even bigger mess to untangle back to FFP.” We were not part of those efforts, and we empathize with those who were.
It might seem as if our efforts had been wasted, that three years of work had been trashed. And pehaps that's true. But such is the life of a consultant.
Often, our best efforts go unappreciated, or unrewarded. In my first true consulting gig (in 1999) we billed the client $500,000 and for that price delivered 18 solid recommendations for improvement (so as to avoid further very expensive False Claims Act-related litigation). That client implemented just one of the 18 recommendations, and ignored the rest. In a later project, we billed one of the Top 5 mega defense contractors north of $500,000 to develop an innovative supplier risk management solution that delighted the program manager who had hired us, but which was immediately killed by Sector HQ because that’s where risk management was functionally located—and they didn’t appreciate the competition. In yet another gig, I reconciled the ins-and-outs of cost allocations for a multi-billion-dollar aircraft manufacturer with multiple business segments. I identified $90 million in differences (errors) that impacted the company’s indirect cost rate calculations—only to be told it was a “rounding error” that should be ignored. In so many engagements, the consultant’s efforts do not result in the intended outcomes, often for reasons that the consultant cannot control.
So it goes. We do our best and sometimes our best isn’t good enough, or isn’t politically correct, or is overtaken by changing circumstances. You try to keep a positive attitude and make sure the checks are cashed. What else can you do?
And what about my clients, whom I came to call my friends, at that small business located in the PNW? They are all being laid-off by the new management, who views them as being non-value-added backoffice lackeys. Perhaps they are, in fact, now redundant in the company’s new environment (which is really the old environment) of 50% commercial/50% government FFP subcontracts. It probably does make financial sense to let them go, despite their decades of experience. That experience just won’t be as valuable to the stand-alone entity as it was to the mega defense corporation that acquired the large aircraft manufacturer that had a small subsidiary located in the Pacific Northwest.
Thus, while we at Apogee Consulting, Inc. get to go home and work on new projects for other clients, those former employees now have to search for new jobs. To assist them: if you are reading this and want to hire some really good, experienced, financial management or contracts people who are based in the PNW, please email us!
In the meantime: to Annette, to Chuck, to Nestor—it was a pleasure to work with you, and we here at Apogee Consulting, Inc., wish you only the best.
|