So I’m rummaging through emails and come across a notice of a FAR update and see something called a “Small Entity Compliance Guide.” “Great,” I thought, “finally someone is trying to get information to small businesses about what they need to do to comply with the various government contracting regulations that get dumped on them from time to time.” Then I kept looking and, much to my dismay, what should appear but the Federal Acquisition Circular that has been published yea these many years with a new title. What a disappointment. Of course, it is entirely understandable. Congress comes along with the ‘‘Small Business and Work Opportunity Act of 2007’’ (buried in the ‘‘U.S. Troop Readiness, Veterans’ Care, Katrina Recovery, and Iraq Accountability Appropriations Act, 2007’’), without of course increasing any manpower or funding to do any of this. So what can one expect of an already overstretched agency but to morph something already being done into something that meets the letter of the congressional mandate without actually doing any additional work (other than pasting a new title on the Federal Register notice). Still, I was disappointed. A Small Entity Compliance Guide is a great idea. I hope one day soon we will see one that actually helps a small business. Until then we’ll just keep searching the internet.
Your business can’t even bid on a federal government contract without registration with the “System for Award Management.” This registration can be done entirely on-line at sam.gov and anyone could do it (well, with minimal computer skills).
That said, I have been surprised, but probably shouldn’t be, that businesses wanting to get into the federal contracting world choose not to do it themselves. There a lot of companies out there that will sell you help with this registration bundled with a lot of marketing services. I have friends with government contract marketing companies and I know they do good work, but it can get pricey for a start-up.
Having done a number of these in the last few months, I have decided that I and my office manager should offer this service as a standalone product for a fixed price. If you are interested, feel free to contact me at email@example.com for pricing and more information on the process.
A bit over a year ago, I wrote about an interesting government agency strategy to avoid having to deal with the messiness of “full and open competition.” (See https://vanhornelaw.wordpress.com/2008/09/05/finessing-cica-the-open-ended-support-contract-ploy/) Now it is time to discuss another ploy to avoid the annoyance of competition, the purported standardization determination.
On January 3, 2011, the Court of Federal Claims issued a preliminary injunction against the Department of the Interior’s attempt to standardize on Microsoft’s email system without conducting a competition. After attempting unsuccessfully to interest the Department in its ability to provide an email system for the Department, Google protested various actions of the Department to implement its sole source decision to use the Microsoft product. You can see a copy of the opinion at http://tinyurl.com/4956j5g.
From the opinion, it is pretty clear that Interior had made the decision to standardize on Microsoft some time ago, perhaps as early as 2007. For months, in 2009 and 2010, Google corresponded with and met with Interior officials to pitch its competing product. Up until late 2010, Interior essentially led Google on, claiming that a competition would be held for the Department’s email system. When solicitation documents became public in late 2010, it was finally clear that there was to be no competition and that Interior had made a final, internal decision to go with Microsoft. The actual solicitation was issued only to selected Microsoft resellers to implement the standardization decision.
This is not a new tactic among government IT offices. In 2007, the Department of Homeland Security tried to do the same thing with the acquisition of financial systems software. (See Savantage v. US, http://tinyurl.com/24vj2rg.) Both DHS and Interior set up the actual solicitation so that the real party in interest, the software developer, could not bid on the procurement by making the procured services only for implementation of a sole source designation of the software to be used. This appears to be an effort to simply avoid having to have a competition for the software since IT personal have developed their own preferences for a particular company’s software and choose not to subject that preference to the competitive market place. Obviously, the strategy becomes problematic when the sole source determination fails to meet statutory and regulatory requirements. Secondarily, the strategy also makes it more difficult for the software developer to challenge the procurement.
It would appear that GAO simply will not address this type of procurement law violation because the protester is not, and cannot be, a bidder. The Court of Federal Claims, on the other hand, has repeatedly shown a willingness to address CICA finessing ploys of various types. I assume this is because the two bid protest forums work under quite different jurisdictional mandates. The statutory mandate to GAO in ruling on bid protests is to “determine whether the solicitation, proposed award, or award complies with statute and regulation.” 31 U.S. Code 3554(b)(1). The Court, however, is under a mandate “to render judgment on an action by an interested party objecting to a solicitation by a Federal agency for bids or proposals for a proposed contract or to a proposed award or the award of a contract or any alleged violation of statute or regulation in connection with a procurement or a proposed procurement.” 28 U.S. Code 1491(b)(1). What the Court has that GAO does not is jurisdiction over “any alleged violation of statute or regulation in connection with a procurement or a proposed procurement.” The Court interprets this third leg of its jurisdictional statute quite broadly, relying on the very broad definition of “procurement” from the Office of Federal Procurement Policy Act, 41 U.S. Code 403(2)(which is mirrored in the FAR at 2.101). See Ramcor Services Group, Inc. v. United States, 185 F.3d 1286, 1289 (Fed. Cir. 1999).
So what is going on here? Why the tendency for this type of ploy to show up in the government IT arena? I would suggest that defining requirements, as would be necessary for a competitive procurement, is really not an easy task. By just getting comfortable and familiar with and then specifying one software product, the requiring office can avoid the unpleasant task of actually articulating what the agency needs. It would appear that procurement officials, perhaps because of a lack of technical expertise, can get snowed by inadequate sole source justifications. This is then compounded with use of all of the IDIQ type contracts available to the contracting officer (e.g., GSA schedule contracts, GWACS, various agency BPAs) which also help disguise the real sole source selection. Since the Savantage decision, and now certainly after the Google decision, it hopefully will be obvious that this particular CICA finessing ploy isn’t all that likely to succeed.
The James Zadroga 9/11 Health and Compensation Act of 2010 was signed by President Obama on January 2, 2011. The Act established the World Trade Center Health Program and, among other things, provides for medical monitoring and treatment benefits to eligible emergency responders and recovery and cleanup workers who responded to the September 11, 2001, terrorist attacks.
To pay for the costs of this program, the Act imposes what amounts to a two percent gross revenue tax on “foreign persons” for amounts received as US government contractors for work performed in certain countries. The US Government contracts covered are those for services performed in, or goods produced or manufactured in, any country which is not a party to an international procurement agreement with the United States.
There are several bilateral trade agreements covering government procurement, but the primary multilateral agreement covering government procurement is the World Trade Organization Agreement on Government Procurement. Although the specific countries covered by this definition will most likely be specified in regulations that will certainly be issued to implement this Act, the countries most likely covered are Iraq, Afghanistan, Pakistan, India, central Asia and the Middle East (excluding Israel but including the Persian Gulf countries), and Turkey.
The Act defines “foreign person” as any person other than a United States person. The tax will apply to contracts awarded on or after January 2, 2011.
It’s not what you’re thinking. Public protests and rallies, political or otherwise, are a time honored and cherished democratic tradition here in Washington DC, but that’s not the kind of protest I’m talking about. My interest is the procurement process of the District of Columbia Government and its pre-award dispute process, the bid protest. I recently had occasion to review this bid protest remedy and here for your education (as opposed to legal advice – since it’s free) is a summary of what I found.
The federal bid protest remedies (at the Government Accountability Office (“GAO”) and the U.S. Court of Federal Claims (“COFC”)) are reasonably well known. Not as well know is that many state and local public procurement systems also have bid protest remedies of varying degrees of independence and professionalism. For contractors doing business with the District of Columbia government there is a bid protest remedy at the DC Contract Appeals Board (“CAB”). The CAB bid protest has many similarities to GAO and COFC bid protests, but some important differences as well.
Here’s what you need to know: Protests are possible against most but not all DC Government entities.
Only “aggrieved parties” can protest. “Aggrieved parties” are essentially the same as “interested parties” under GAO and COFC bid protests. An aggrieved party is defined as “an actual or prospective bidder or offeror (i) whose direct economic interest would be affected by the award of a contract or by the failure to award a contract, or (ii) who is aggrieved in connection with the solicitation of a contract.”
Timeliness rules are very strict, similar but not exactly the same as GAO. A protest based on problems with a solicitation must be filed prior to bid opening or the time set for receipt of proposals. Other protests (essentially post-award protests) must be filed no later than ten (10) business days after the basis of the protest is “known or should have been known.”
There are provisions for an automatic stay of contract performance which can be over-ridden by the agency. Similar to GAO protests, the agency must file a report and the protestor must file comments. However, the time frames are 20 days for the report and 7 days for the comments. The CAB’s decision must be issued within 60 business days from the date the protest is filed
As with GAO, a protester can be represented by a non-attorney officer. Of course, that can result in the protester not having access to confidential agency information. The CAB has a protective order process that allows attorneys and consultants to have access to the confidential information.
Here are some technical details: The DC Contract Appeals Board is the designated forum for hearing and deciding both contractual disputes and bid protests involving the DC government pursuant to the DC Procurement Practices Act of 1985, effective February 21, 1986 (D.C. Law 6-85) (D.C. Code Ann. §§ 2-301.01 to 2-311.02). The Act applies to all contracts and intergovernmental and interagency agreements for the procurement or disposal of goods and services by executive agencies and employees subordinate to the Mayor.
The Board is composed of Administrative Judges who hear and decide the cases. DC Code § 2-309.08 (“Protest procedures”) and Chapter 3 of the Board Rules provide detailed requirements and rules governing protests of solicitations and awards.
The Board issues written decisions, which are published in the District of Columbia Register (DC Reg). Full text searches of the Board’s published decisions are possible at the published decisions search page of the CAB website (http://cab.dc.gov). The CAB has provided for comprehensive electronic filing in bid protest (and other) cases through the LexisNexis File & Serve.
While no bidder should protest frivolously, you may want to think twice about doing so before the DC CAB. If the Board decides a protest has been frivolous, it can order the protester to pay the agency’s attorney fees (fortunately limited to $100 per hour) and damages for delay of an awarded contract.
Notwithstanding that interesting fillip in the rules, it is good to see that the DC procurement process has a judicial remedy for problems in the award of contracts.
In a recent Court of Federal Claims decision (Ozdemir v. United States, 19 November 2009), Judge Damich clarified the Court’s jurisdiction over protests of solicitations and awards of contracts other than procurement contracts. In a time when the government is pumping out vast sums for economic recovery through a number of formal vehicles (grants, etc.), this remedy could become increasingly important to those frustrated in their dealings with the federal government.
The Ozdemir case arises from the very first solicitation issued by the Department of Energy’s Advanced Research Projects Agency (“ARPA-E”). This solicitation requested concept papers so ARPA-E could select promising energy-related technologies for research and development funding. To provide this funding, the solicitation identified grants, cooperative agreements and technology investment agreements as the anticipated legal vehicles. Interested parties were required to request an “application control number” by a given deadline. Mr. Ozdemir failed to make a timely request for this number and the agency refused to consider his concept paper when he submitted it.
The government chose to defend against Mr. Osdemir’s protest by moving to dismiss on the theory that the Court did not have jurisdiction because the solicitation did not relate to a procurement. Although the parties argued over whether or not the solicitation related to a procurement (the solicitation included one reference to a procurement instrument), the Court sidestepped this issue to deal with a more fundamental issue, whether the Court had jurisdiction over non-procurement protests.
After concluding that the precedents offered by the government did not support their position that the Court’s bid protest jurisdiction did not extend beyond procurement matters, the Court proceeded to set out two bases for its conclusion that its bid protest jurisdiction extends beyond procurement matters. (Senior Judge Merrow applied similar reasoning in Red River Holdings, LLC, v. United States, July 17, 2009, however, in that case the protest involved a maritime contract, which was clearly a procurement matter, and the parties agreed that the Court had jurisdiction; the jurisdiction issue was raised sua sponte by the Court.)
First, the Court found support in something cleverly called the Last Antecedent Rule (which, it turns out, is rather like the Pirate Code, more of a suggestion than a rule). The Last Antecedent Rule is a rule of statutory interpretation that was explained by the Federal Circuit in Anydrides & Chems. Inc. v. United States, 130 Fed.3d 1481, 1483 (Fed. Cir. 1997) (quoting 2A Sutherland Statutory Construction, 4th ed., § 47.33):
The rules of grammar apply in statutory construction:
Referential and qualifying words and phrases, where no contrary intention appears, refer solely to the last antecedent, which consists of “the last word, phrase, or clause that can be made an antecedent without impairing the meaning of the sentence.”
The government focused on the last phrase of the jurisdictional statute (28 USC § 1491(B)(1)), “in connection with a procurement or proposed procurement,” claiming that this phrase modified the entire sentence. Because there is no comma immediately before this phrase, the Court, applying the Last Antecedent Rule, determined that the phrase modified only the immediately preceding phrase (“any alleged violation of statute or regulation”), not the entire sentence. Thus, the rest of the sentence provides several independent bases of jurisdiction, including a protest against a solicitation for proposals for a proposed contract and a protest against a proposed award. The Court found its jurisdiction in these phrases since ARPA-E had clearly issued a solicitation which contemplated an award.
Also the government argued that “contract” in this context meant procurement contract, relying on the definitions in the Federal Grant and Cooperative Agreement Act (31 USC 6301-08), the Court found this assertion unsupported and held that “contract” in § 1491(b)(1) encompasses a wide range of formal agreements, including grants and cooperative agreements.
The Court also noted that the ARPA-E solicitation clearly contemplated an “award,” giving the Court a second basis for jurisdiction as a protest against a proposed award. This does not seem to me to be as strong a basis for jurisdiction, since at best, Mr. Ozdemir was complaining about a refusal to consider an award to him, not a proposed award to a third party. However, given the Court’s expansive reading of 1491(b)(1) (including the noted “hexadic” use of the conjunction “or”), the idea that one could protest an “award,” without reference to a contract (however defined) and without reference to a solicitation raises some interesting possibilities. Might it cover a financially significant endorsement of a commercial product by a federal agency or federal official that prejudiced a competitor (prejudice being a required element of the Court’s jurisdiction)?
The Court found further support for its reading of § 1491(b)(1) in its analysis of the history of the Court’s bid protest jurisdiction. Specifically, the Court noted that prior to enactment of the current language in § 1491(b)(1) in the Administrative Dispute Resolution Act of 1996 (“ADRA”), the Court had jurisdiction over protests involving award of non-procurement contracts, such as timber sales, and that there is no indication that ADRA in any way was intended to restrict the Court’s bid protest jurisdiction, only to expand it.
Although this decision was not the first since 1996 to recognize the Court’s jurisdiction over non-procurement protests, it certainly is unique in its thorough discussion of the issue, all the more intriguing for having occurred in a pro se case.
My personal perspective is that federal agencies have for some time been looking for creative ways to avoid exposure to bid protests, mostly by using highly complex, multi-agency IDIQ procurement vehicles or by having support contractors doing what would normally be agency procurements. It will be interesting to see, in this environment, how the agencies react to this clear assertion of the Court’s jurisdiction over non-procurement bid protests.
The recent flap regarding the private security services provided to the State Department by Blackwater has obscured a very important reality about the Iraq war. Since 2000, the number of Defense Department contracts has nearly doubled. Presently the number of civilian contractor employees in Iraq exceeds the number of military personnel there. As more and more services within the military are outsourced, reliance on civilian contractors to support overseas active military operations has increased significantly. As a result, civilian contractor employees face risks once handled entirely by military personnel. In places like Iraq and Afghanistan (and many other places in an increasingly dangerous world), civilian contractor employees face the very real possibility of injury, kidnapping and death. For the sake of these employees and their families, these risks must be addressed by appropriate insurance coverage, something for which Congress has in fact provided.
Federal Workmen’s Compensation Law: Federal law requires all U.S. government contractors and subcontractors to secure workers’ compensation insurance for their employees working overseas. The related statutes include the Defense Base Act, 42 U.S.C. §§ 1651-54 and the Longshore and Harbor Workers’ Compensation Act, 33 U.S.C. §§ 901-50.
The Defense Base Act covers these contractor activities:
• Work on U.S. military bases outside of the United States
• Public work contracts with any U.S. government agency, including construction and service contracts, in connection with national defense or with war activities outside the United States;
• Work funded under the Foreign Assistance Act, if the contract is performed outside of the United States;
• Providing welfare or similar services outside of the United States for the benefit of the Armed Forces, e.g. the USO.
If any one of the above criteria is met, all employees engaged in such employment, regardless of nationality, are covered under the Act. Additionally, the prime contractor is responsible for assuring coverage of subcontractor employees. Three major insurance carriers currently providing Defense Base Act insurance coverage are ACE-USA, AIG, and CAN. A number of companies self-insure.
One problem contractors have faced is that the appropriate clause is often not incorporated in government contracts. Without the contracting officer’s acknowledgement that the Defense Base Act applies, it may be a challenge to get the cost of the insurance recognized in the contract price. Without the clause in the contract, the contractor may be unaware that the statutorily mandated workmen’s compensation insurance should be obtained.
The War Hazards Compensation Act. The WHCA provides benefits to persons covered by the DBA who are injured or killed due to an “armed conflict” in the foreign country where the claimant is working; or who are detained or taken prison by hostile forces. The WHCA provides coverage to employees who would not otherwise be covered because the injuries or deaths were caused by hostile action.
Risk Management: In addition to providing insurance for employees, the contractor needs to take into account the dangerous environment into which it is placing its employees by seeing that the employees, on-site managers and executives are educated as to the risks and the steps that can be taken to minimize those risks. Employees need to know what to expect both physically and mentally and what steps to take in advance, what situations to avoid, what defensive steps can be taken to minimize the danger involved in working in a dangerous environment and what to do if the worst happens. Managers and executive need to know what preventative action to take and what steps need to be taken in the event of an employee’s injury, abduction or death.
Education of this type needs to be provided by individuals and organizations that have on-the-ground, recent experience in these kinds of situations and that can provide practical, timely guidance for employees and for the organization. To get a gritty feel for what is required, see “Staging Security in a Theater of War” by Scott Ast in the Security Management Online Archive (http://www.securitymanagment.com/library/001728.html).
Conclusion: Putting one’s employees into a war zone is a complicated, expensive and stressful activity. Issues are raised with which U.S. businessmen and most government contractors may not be comfortable. Nevertheless, these issues need to be addressed before employees are sent into harm’s way.