Showing posts with label federal government. Show all posts
Showing posts with label federal government. Show all posts

Tuesday, December 14, 2010

The double-edged sword of oversight

Is increased oversight a burden, or an opportunity to stand apart from the crowd?

We've been reporting for some time now that government contractors and subcontractors are coming under increased scrutiny. Previously, small business subcontractors were somewhat immune from harm, but this immunity is rapidly being whittled away. The Washington Post has noticed this phenomenon:

"The days of 'No one is checking,' are over. For too long, there was inadequate oversight." --Daniel Gordon, an administrator at the White House Office of Federal Procurement Policy

Washington Technology is reporting the same thing this week.

This increased focus on procurement regulations might have some contractors and subcontractors quaking in their boots. Oversight tends to send business owners into a panic, because it often means increased costs in a world of razor thin profit margins. No one wants to risk being debarred or suspended, or have payments withheld, especially when federal contracting can provide a crucial stream of profitable business in many industries.

But the costs need not be prohibitive, and this negative can be turned into a strong positive for contractors and subcontractors. Increased oversight is bad news for those who don't follow government regulations, but good news to those who know and observe the rules!

There are great benefits to proving competence with federal procurement regulations. A contractor who can say they have a procurement regulations management system in place is going to be much more attractive to contracting officers than those who don't. Competence is a crucial factor among contracting officers when evaluating the competition--you can place yourself above your competitors by showing that this new focus on oversight doesn't burden or scare you because you have already taken steps to ensure compliance.

FARSmarterBids.com offers the most extensive library of federal procurement regulations in one place. Not only that, but regulations can be managed: contractors and subcontractors can store key regulations in their own virtual filing cabinets for easy, repeated access, meaning they can save valuable time and energy, preserving their profit margins. Many contractors use what they learn from the service to supplement the knowledge they receive from attorneys and consultants, thus shaving hundreds to thousands off these professionals' fees. All of this is offered for a low monthly or quarterly fee--as low as $55 per month.

Of course, just knowing the federal procurement playbook in general confers benefits of its own. This knowledge helps you compete because you have a better grasp of the regulatory costs and can use that knowledge to decide on what contracts to bid.

Subcontractors, too, can use this knowledge to better compete for work. Any smart businessperson will tell you how crucial it is to know your customer--and that includes being familiar with their regulatory landscape. Subcontractors who understand what the primes are up against--including payment withholding and evaluating supply chain risk--are attractive competitors. Often, subcontractors must comply with regulations when completing work for a prime contractor--those who work within the scope of those regulations are going to find themselves better positioned for repeat work.

Also, subcontractors can better insulate themselves from lawsuits and disputes if prime contractors face penalties levied by federal contract managers or agency heads if they know their regulations. This means potentially averting costly, even business-killing litigation in the unfortunate event a prime contractor tries shifting the blame to a subcontractor in such a situation. The knowledge contained within FARSmarterBids provides a cost-effective "keep off the grass" sign to prime contractors who might try an underhanded technique to keep the heat off themselves.

We find that, far from being a costly burden, compliance with federal procurement regulations can be turned into a net positive. At very little cost, prime contractors and subcontractors can market themselves as the most capable, competent, efficient organizations with which to do business. Instead of groaning at the thought of increased oversight, companies can relish the thought of beating out the competition by playing the government's game.

Thursday, October 14, 2010

Government Contractors: Know Your Regs, or Else?

We wanted to give a shout-out to Mike Anderson over at Tech Biz Blog for noticing the same thing we have: contracting regulations matter more now than ever before. This is true not only for the big guys, but small businesses and everyone who subcontracts. No one--prime contractor, subcontractor, or federal agency--is going to want to risk working with your company unless you have a good handle on the FARS.

Friday, September 10, 2010

Contracting Principles the DoD Forgot, Part 2: Introduction to the Proposed Mandatory Withholding DFAR

On January 15, 2010 the Federal Register published the Department of Defense (DoD) proposed rule "to amend the Defense Federal Acquisition Regulation Supplement (DFARS) to improve the effectiveness of DoD oversight of contractor business systems." Interested parties were invited to submit comments referencing DFARS Case 2009–D038, and a few dozen responses were submitted. At this time we are awaiting further action from the DoD, but it seems unlikely that the DoD will simply drop this proposed rule entirely.

In the Federal Register the DoD provided the following background explanation for the proposed rule:

"Contractor business systems and internal controls are the first line of defense against waste, fraud, and abuse. Weak control systems increase the risk of unallowable and unreasonable costs on Government contracts. To improve the effectiveness of Defense Contract Management Agency (DCMA) and Defense Contract Audit Agency (DCAA) oversight of contractor business systems, DoD is considering a rule to clarify the definition and administration of contractor business systems as follows:

1. DoD is proposing to define contractor business systems as accounting systems, estimating systems, purchasing systems, earned value management systems (EVMS), material management and accounting systems (MMAS), and property management systems.

2. DoD is proposing to implement compliance enforcement mechanisms in the form of a business systems clause which includes payment withholding that allows administrative contracting officers to withhold a percentage of payments, under certain conditions, when a contractor's business system contains deficiencies.
Under such circumstances, payments could be withheld on—
  • Interim payments under—
    • Cost reimbursement contracts;
    • Incentive type contracts;
    • Time-and-materials contracts;
    • Labor-hour contracts;
  • Progress payments; and
  • Performance-based payments."

The very first sentence of this background statement illustrates the fundamental flaw in the DoD's thinking about its procurements. It is not "Contractor business systems and internal controls" that serve as "the first line of defense against waste, fraud, and abuse". This statement ignores the customer's responsibilities and conceptually shifts all risk of waste, fraud, and abuse to the contractor. You might ask: "How else could it be?" You might say: "After all, the contractor controls its own actions including wasteful, fraudulent, and abusive actions, and the customer does not commit waste or fraud against itself, or abuse itself." There are some qualifications and exceptions to these thoughts that we could explore, but more importantly, it is the customer's fulfillment of its responsibility to define what it wants in a comprehensive, clear, and timely manner, and the customer's treatment of the contractor in a fair manner, that serves as "the first line of defense against waste, fraud, and abuse". At most, contractor business systems and internal controls are a secondary or tertiary line of defense against waste, fraud, and abuse. The DoD has forgotten some of the basic principles of procurement in our culture.

Coming soon: Part 3: "Business Systems" Excerpts from the Proposed Mandatory Withholding DFAR

Wednesday, September 8, 2010

Contracting Principles the DoD Forgot, Part 1: Mandatory Payment Withholding Consequences for Contractors

If you were to design an Introduction to Procurement course for undergraduates enrolled in a Business College of a University, during the first or second class you would introduce basic general concepts, and some customs, traditions, and tendencies that have historically formed the environment for procurements in our culture, and that still form that environment. The American concept of “fairness” as perceived and applied in the realm of business and more specifically in the context of procurements would be one of the important general cultural concepts introduced and would likely generate lively discussion. The American “can do” mindset, particularly among vendors, would be another cultural discussion point. This traditional attitude is so deeply ingrained within us that often we are not aware of its influences. The tradition of the American work ethic would also be mentioned in class, and some enjoyable debate might arise over which parts of the country exhibited the greatest degree of this work ethic of our forefathers. Along with many other customs you would go on to mention the typical responsibilities of the parties at a high level of abstraction—at the “50,000 foot level”. For example, you might explain that customers usually have two major responsibilities at the 50,000 foot level: (a) to define what the customer wants; and (b) to pay for it.

The customer’s first responsibility is to (i) define its required product or service deliverables, results, research, engineering, efforts, or other commitments from the vendor in advance of entering into a contract; or (ii) hire a consultant or a vendor to help specify them in advance; or (iii) require samples or a prototype that must be approved before the customer fully commits; or (iv) provide safe harbors for the vendor; or (v) specify some other requirements. A safe harbor in this general procurement context might include a commitment and a set of required conditions that, if completed or satisfied by the vendor, trigger payment, or earn other consideration, and protect the vendor against unreasonable rejection, termination, and/or liability. The set of conditions might include a vendor’s certification on certain ISO standards, a customer’s pre-contract inspections of required operations, or a customer’s acceptance criteria that are clear and comprehensive.

Since our hypothetical course is a basic introduction to procurement, a young student might ask: “Why must the customer define requirements for the vendor in advance of entering into a contract?” One answer is because the vendor is not a mind reader. Another answer is that fairly often the vendor needs to know the customer’s requirements in order to set a price including any applicable discounts or premiums. Still another answer is that customers often have only a poorly defined notion of what they want, and if they do not improve that notion and also clearly communicate what they want, it is not the vendor’s fault.

Without a comprehensive notion of what they want that is clearly and timely communicated to their bidders or vendor, customers may very well not be happy with what they receive, and they may reject, terminate, litigate, or pay more to get what they decide they really want. In fact, this situation of customers not knowing what they want, or having only a vague notion about it, and often not clearly or timely communicating their poorly-thought-out requirements, is a reality in both commercial and government procurements, and is a major cause of cost overruns. If customers could better define what they wanted—comprehensively, clearly, and in a timely manner, then some noticeable excess expenditures could be avoided.

Further, if a customer poorly defines its requirements, or delays in defining them, and attempts to shift to its vendor the risk of resulting cost-overruns and performance glitches or delays, the situation quickly becomes unfair, and it justifies the vendor, among other reactions, in requiring a premium for accepting a high-risk procurement. One of the traditions surrounding procurements in our culture is that with higher than normal risk goes greater than normal reward. If the customer refuses to pay a premium in a higher-than-normal-risk context and still imposes these risks, the customer encourages the vendor to (i) hide extra profit; or (ii) ignore non-standard requirements, especially if they are communicated after contract commencement; or (iii) take other steps intended to balance reward with risks. Under no circumstances will the vendor want to accept a penalty due to the customer’s poorly defined requirements or delays in defining them.

The second customer responsibility—to pay for its requirements--includes making payments to vendors on schedule and without unreasonable or capricious payment lateness, withholding or denial. Denying payments earned, and, in the alternative, lengthy withholding periods for payments earned through performance, are each a very serious matter. Each situation has the tendency to at least diminish business relationships, and often generates disputes. Small, and even mid-sized, vendors have been known to go out of business fairly quickly if the size of the payment denied or withheld is noticeable.

As our final academic point, near the beginning of our hypothetical basic procurement course you might also explain that, considering all procurements in the country at any given point in time, more often than not neither party to a typical contract may unilaterally change its terms or conditions in any significant way during its life. Of course, customers with unusual leverage, such as government customers, may make such demands. However, even in the face of considerable leverage, absent additional discussion and accord, and absent mutually-acceptable change mechanisms built into the contract in advance and reasonably implemented, disputes will often arise as a result of significant unilateral changes in contracts during their term. Such disputes commonly give rise to procurement delays, unforeseen costs, and sometimes other unforeseen consequences.

This is a general academic review, and these are all basic procurement concepts, customs, traditions, tendencies, and commonplace results. In the United States, everyone with any measurable experience in procurement should be very aware of them. They are not advanced course or graduate course material. Yet earlier this year our federal government appears to have forgotten some of them.

Coming soon: Part 2: Introduction to the Proposed Mandatory Withholding DFAR