About our Clients
The first rule of consulting is client confidentiality. We don’t identify our clients by name and, on the rare occasion we have cause to write an article about them, we change the names to protect their confidentiality. That being said, we thought readers might be interested in what we’ve been doing this past year. Without further introduction, here is a list of Apogee Consulting, Inc.’s 2016 clients and their projects.
-
Client 1 is a small, woman-owned business that provides engineering services. It’s experienced a phenomenal growth rate over the past few years. Its customers are largely prime defense contractors providing services to the US Navy. We have supported this client, off and on, for many years. Sometimes this client takes our advice. Other times: not so much. When the latter occurs we tend to write about it. The client wanted to become a prime, and receive cost-type contracts, but failed its first DCAA accounting system review, primarily because the company accountant didn’t know anything about government accounting or what DCAA would look for, and the client didn’t call us until afterwards. We helped the client develop a corrective action plan, which included hiring somebody who knew something about government contracting and government accounting. We helped the client advertise the position and evaluate candidates. The company eventually found somebody they liked. Since the company made the successful hire, we haven’t heard from it. (Which is fine, because our aim is to work ourselves out of a job. But it would be nice to know whether or not the client completed the accounting system corrective action plan we developed.)
-
Client 2 is a very successful small business providing engineering services, primarily to non-defense prime contractors. This client reappeared in late 2015, after several years of silence, with significant audit problems (most of which were rebuttable). After several attempts to rebut the audit findings with mixed success, we advised contacting an attorney, and the client accepted our recommendation. We continue to actively support this client and help prepare for litigation. More to the point, we continue to assist efforts to avoid litigation.
-
Client 3 is a former small business that became a large business by virtue of being acquired by a large business. It designs and produces complex connectors for aerospace and defense applications, both as a prime and as a subcontractor. Ed worked with this client to develop its first small business plan, which was now a contractual requirement. This was a rocky project because the client could not identify which internal organization and/or individual would be responsible for implementing the small business plan, to include such activities as small business outreach and reporting. Still, we delivered what the client asked for; we have no idea whether or not the client actually implemented the plan we designed.
-
Client 4 is a medium-sized classic defense contractor, recently acquired by a larger international organization. In 2015 Tom helped this client with critical subcontractor cost/price analyses that were delaying a large contract award. In 2016 he was asked to return to help with certain other issues, which included overseeing a project to develop a specialized safety manual for an affiliated entity.
-
Client 5 is a small subsidiary of a large defense contractor. It has both commercial and government contracts, but the government contracts have all been FFP. The large defense contractor recently was acquired by an even larger defense contractor. The problem was that this subsidiary had been providing products to the acquiring entity under a FFP purchase order. Now the transaction would be an inter-organizational transfer subject to FAR 31.205-26(e); i.e., it would be a cost-type agreement. We assisted the company with preparing a proposal that would meet FAR Table 15-2 requirements, including calculating compliant indirect cost rates. (We will continue to assist this client with similar issues in 2017.)
-
Client 6 is a small, entrepreneurial company that designs and produces innovative products, primarily for defense prime contractors—although it has at least one DoD prime contract of its own. Our first project was to assist the company with designing a new indirect rate structure that would permit commercial item transactions (i.e., commercial item subcontracts between affiliated entities, which are different from non-commercial inter-organizational transfers). Our second project, which is still ongoing, involves Tom assisting with cost/price analysis regarding several subcontractors, some of whom seem to qualify for a commercial item determination. The challenge here is to sell the commercial item determination to the DCMA contracting officer.
-
Client 7 is a lovely client who ignored our advice, actually lied to us about the project status, and then didn’t pay our bills. We wrote a two-part article about this “gem” of a client. 2017 will start with us taking this asshole to court in order to collect what we are rightfully owed. Rocko, we are coming for you.
-
Client 8 is a long-term client, for whom we’ve been providing “on-call consulting services” for many years. A large telecommunications provider, this mega entity also has a smaller division that provides products and services to the DoD. We have provided advice and assistance to this client in areas including cost allowability, cost accounting practices, SAP implementation, commercial item determinations, and indirect rate calculations.
-
Client 9 is a new client, for whom we also provide “on-call consulting services.” That means that, basically, we answer their questions. Because this client already has a full-time experienced compliance team, we tend to only get difficult questions that require thought and research.
-
Client 10 is a small business provider of technology services to the DoD. We took on a quick-turn project to help the company develop a brand new indirect rate structure. This involved detailed labor cost modeling. The final indirect cost model aggregated data from three sources across two companies, and involved modeling a split of one fringe benefit pool into two fringe benefit pools, an on-site and an off-site overhead rate, and comparing a TCI G&A allocation base to a VAB G&A allocation base. For the VAB base scenario we developed a material handling pool. Honestly, it was one of the most complex models we’ve ever seen. But we got it done!
As you can see, Apogee Consulting, Inc., works on a variety of projects for both small and larger companies. It’s good to be busy.
2016 was a great year and we trust 2017 will be just as good!
Regulatory Christmas Gifts
We already wrote about the new privacy training requirement. Here are some more Christmas 2016 gifts from our regulatory rule-makers.
-
Interim rule effective 01 January 2017: Paid Sick Leave for Federal Contractors. We already discussed the genesis of this one here. Look to FAR 22.21 for some details. Interestingly, the interim rule urges contracting officers to add the new requirement into existing contracts via bilateral modification. If your contracting officer wants to stick you with that new requirement—and you didn’t originally propose it or negotiate the cost of compliance into your contract price—then you need not accept it. Or, if you feel pressured to accept it, then you are entitled to “appropriate consideration” for doing so. At a minimum, we believe that you would be entitled to an equitable price adjustment for any additional costs resulting from compliance—plus profit/fee.
-
Final rule effective 16 December 2016: Fair Pay and Safe Workplaces; Injunction. Revises FAR as required in order to implement the judicial injunction against enforcement of certain FAR revisions implemented in August, 2016.
-
Final rule for NASA contractors, effective 17 January 2017, revising the NASA FAR Supplement to require contractors having custody of $10 million or more in NASA-owned Plant, Property and Equipment (PP&E) to submit monthly reports. Interestingly: “The Contracting Officer may … withhold payment until a reserve not exceeding $25,000 or 5 percent of the amount of the contract, whichever is less, has been set aside, if the Contractor fails to submit annual NF 1018 reports in accordance with NFS subpart 1845.71, any monthly report in accordance with (c)(3) of this clause, and any supplemental instructions for the current reporting period issued by NASA. Such reserve shall be withheld until the Contracting Officer has determined that NASA has received the required reports.”
-
Final rule effective 19 January 2017, requiring contractors to “notify the contracting officer, in writing, if the contractor pays a reduced price to a small business subcontractor or if the contractor's payment to a small business subcontractor is more than 90 days past due.” Contracting officers will record the names of these deadbeat prime contractors in the Federal Awardee Performance and Integrity Information System (FAPIIS). There are five listed circumstances in which a prime’s late or reduced payment may be justified; we suggest you visit the new rule and review them.
-
Final DFARS rule effective 22 December 2016, permitting contracting officers to provide “customary” contract financing (other than loan guarantees and advance payments), without any further justification. According to the promulgating comments: “DoD has determined that the use of such customary contract financing provides improved cash flow as an incentive for commercial companies to do business with DoD, is in the Department's best interest, and requires no further justification of its use.” Left unmentioned was the fact that use of progress payments based on costs incurred requires the “commercial companies” to have an accounting system determined to be adequate by government auditors, unlike performance-based payments—the use of which require additional justification.
Merry Christmas from Apogee Consulting, Inc.
|
End of Year Legal News
So here we are at the end of 2016.
We thought we would wrap-up the year with a list of some legal news. As long-time readers know, we stopped reporting most fraud stories a while ago, because they got boring. There was very little reason to sit down and type up a story about yet another fraud. Plus, there were just too many. It was too much for us.
And we don’t even follow reports of healthcare fraud.
To prove our point, here’s a recap from the past 30 days or so. Basically, this is just one month’s worth of procurement-related fraud news, none of which--in our view--merited a stand-alone article. (The list excludes, as always, reports of healthcare fraud. Believe us: the list would have been much longer if we included the Medicare/Medicaid fraud and similar matters.)
-
$125 million FCA settlement paid by “Bechtel National Inc., Bechtel Corp., URS Corp. (predecessor in interest to AECOM Global II LLC) and URS Energy and Construction Inc. (now known as AECOM Energy and Construction Inc.)” in connection with allegations that “they made false statements and claims to the Department of Energy (DOE) by charging DOE for deficient nuclear quality materials, services, and testing that was provided at the Waste Treatment Plant (WTP) at DOE’s Hanford Site near Richland, Washington. The settlement also resolves allegations that Bechtel National Inc. and Bechtel Corp. improperly used federal contract funds to pay for a comprehensive, multi-year lobbying campaign of Congress and other federal officials for continued funding at the WTP.”
-
Convicted fraudster ordered to forfeit $6.7 million in connection with his conviction for “recruiting veterans as figurehead owners of a construction company in order to receive specialized government contracts.”
-
Two men had lengthy prison sentences affirmed on appeal for their roles in executing “the largest reported DBE fraud in the nation’s history.” Their scheme lasted for “over 15 years and involved over $136 million in government contracts in Pennsylvania alone.”
-
A woman was charged with making False Claims and False Statements for being paid for two DoD jobs at the same time. While getting paid for being a security guard for a SCIF facility, the woman was alleged to have also worked as an active duty Army intelligence officer at Fort Meade.
-
A subcontractor that managed military housing agreed to pay $1.6 million as part of a deferred prosecution agreement to resolve criminal fraud charges related to accepting “kickbacks” which may have included undisclosed insurance rebates. (We recently did a blog post on accounting for credits.) In connection with the government investigation, two individuals were convicted; both were fined and one went to jail.
-
Those readers who remember the “Fat Leonard” scandal (which we’ve written about on this blog) may be interested to know that “a former supervisory contracting officer was sentenced to 72 months in prison today for accepting bribe payments in exchange for steering U.S. Navy contracts” to Fat Leonard’s company.
-
ThunderCat Technology, LLC, “agreed to pay $1 million to settle civil False Claims Act, Anti-Kickback Act, and Procurement Integrity Act claims relating to bid rigging and kickback schemes in connection with six government procurements.”
-
A former Veterans Administration Chief of Podiatry and the CEO of a VA vendor were indicted by a grand jury for “health care fraud, conspiracy to pay and receive kickbacks on medical referrals, and conspiracy to commit wire fraud.” Some of the 11 counts were related to an alleged scheme to bill “the Veterans Health Administration for custom work and services that were prescribed but not supplied in shoes delivered to veterans.” (Note to readers: yes, this one was related to healthcare fraud, but if you follow the link and read the story, you’ll see it wasn’t really about healthcare fraud. It was really about common variety procurement fraud in a VA hospital.)
-
GE Aviation agreed to pay $2.55 million to settle allegations that its Italian subsidiary, Avio Aero, falsified testing reports on “gearboxes used in T700 and F110 engines in DOD helicopters and fighter jets, respectively.”
-
Two Northeast construction companies—along with four individuals—agreed to pay $1 million to settle allegations of FCA violations that stemmed from “claims for reimbursement for funding earmarked for minority, women-owned, or small business that they were not entitled to receive.” One company was the prime; the other was the subcontractor. Apparently both companies were aware that the subcontractor did not qualify as a disadvantaged business enterprise (DBE), yet the prime allegedly claimed awards to the subcontractor on its small business reporting to the US EPA.
-
A Chinese national and lawful permanent resident of the United States pleaded guilty to various charges centered on his admitted theft of sensitive military program documents from United Technologies Corporation and transporting them to China. Charges to which the man pleaded guilty included: “one count of conspiracy to engage in the theft of trade secrets knowing that the offense would benefit a foreign government [and being a] foreign instrumentality or foreign agent, [and] one count of unlawful export and attempted export of defense articles from the U.S. in violation of the Arms Export Control Act.”
-
Finally, Roy Friend, of Newport News, VA, was sentenced this month to serve 33 months in prison after pleading guilty to stealing government property. While employed by DoD as “Chief of Logistics and Program Management, Aviation and Missile Command” at Fort Eustis, Friend ordered roughly $905,000 in goods from the GSA Advantage website and under the auspices of the U.S. Falcon contract. During an investigation, it was determined that Friend took some of the items for personal use; other items had the GSA shipping labels removed prior to being resold; and still other items were sold on eBay. The scheme apparently went on for about five years before being detected.
One last word on the foregoing. We get emails from the Department of Justice every day (sometimes more often) so it’s a fairly quick task to skim the emails to see if there’s anything worthy of a blog article. If not, the emails are quickly deleted. When we set out to compile this list of wrongdoing for our readers, many of the original emails had already been deleted. But Bob Antonio keeps a rolling list of procurement fraud links over at his WIFCON site. Thus, his list became an invaluable resource for compiling this list. If you don’t visit WIFCON at least once a week, you are missing a very important resource for government contracting and compliance professionals.
And I think we’re done with 2016 now.
Mandatory Privacy Training
A recent final rule revised the FAR to require contractors whose employees have access to “a system of records” or that “handle personally identifiable information” (PII) to complete training on privacy. The final rule applies to acquisitions of commercial items and to acquisitions valued below the simplified acquisition threshold (SAT). The privacy training must be “role-based [and provide for] foundational as well as more advanced levels of training” and include tests of the knowledge levels of users.
Training must cover—
-
The provisions of the Privacy Act of 1974 (5 U.S.C. 552a), including penalties for violations of the Act;
-
The appropriate handling and safeguarding of PII;
-
The authorized and official use of a system of records or any other PII;
-
Restrictions on the use of unauthorized equipment to create, collect, use, process, store, maintain, disseminate, disclose, dispose, or otherwise access, or store PII;
-
The prohibition against the unauthorized use of a system of records or unauthorized disclosure, access, handling, or use of PII or systems of records; and
-
Procedures to be followed in the event of a potential or confirmed breach of a system of records or unauthorized disclosure, access, handling, or use of PII.
The requirement is a flow-down, meaning that prime contractors are required to include it in subcontracts, where applicable (i.e., where the subcontractor handles PII).
The contractor (or subcontractor) must maintain documentation evidencing that the privacy training requirements were met, and must provide that documentation upon request.
A new subpart (24.3) is added to the FAR to address the issue.
What is PII? According to the new rule, “Personally identifiable information means information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual.”
What do we think of the new rule?
Well, we just finished up a lot of compliance training. And in that training we learned that a company—not just a government contractor, but any publicly traded entity—should have a policy on PII protection and that employees should be trained in that policy, and that compliance with the policy should be tested. So from that point of view, this is something that many companies should already have in place. For them, it will be no big deal.
But we also know that there are many upon many small businesses and other contractors for whom this will be a brand new and disconcerting requirement. For them, it will be a big deal indeed.
We also think that the rule is unnecessarily prescriptive and creates a bureaucratic solution to what is essentially a free market problem. For example, the government could have chosen to create a mandatory source evaluation factor that covered the same requirements. That would have pushed companies toward the same end state without actually prescribing it.
But whatever. Here we are.
If you would like assistance in designing your training program or in training your employees, Apogee Consulting, Inc., is here to help you.
|