<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Government Contracts, Investigations &amp; International Trade Blog</title>
      <link>http://www.governmentcontractslawblog.com/</link>
      <description />
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Wed, 16 May 2012 13:33:39 -0800</lastBuildDate>
      <pubDate>Wed, 16 May 2012 13:33:39 -0800</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="governmentcontractsblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.governmentcontractslawblog.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.governmentcontractslawblog.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.governmentcontractslawblog.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
         <title>Another U.S. District Court Follows The Lead Of The D.C. Circuit In Addressing The "First-To-File Bar" Circuit Split And Pushes Back Against An Opportunistic Relator</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/cloveland"&gt;Christopher Loveland&lt;/a&gt; and &lt;a target="_blank" href="http://www.sheppardmullin.com/jaronie"&gt;Jonathan Aronie&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;While the False Claims Act (&amp;ldquo;FCA&amp;rdquo;) generally is understood to be a &amp;ldquo;whistleblower&amp;rdquo; statute, it has been a tool of choice in recent years for opportunistic &lt;em&gt;qui tam&lt;/em&gt; relators who lack any inside information regarding the very companies they sue. Not surprisingly, this lack of inside information has resulted in many &lt;em&gt;qui tam&lt;/em&gt; cases being dismissed either because they merely mimic the allegations of a previously-filed case or do not plead their allegations of fraud with sufficient particularity.&lt;/p&gt;&lt;p&gt;A very recent example of this trend is &lt;em&gt;United States ex rel. Sandager v. Dell Marketing, L.P&lt;/em&gt;., C.A. No. 08-4805, 2012 U.S. Dist. LEXIS 59714 (D. Minn. Apr. 25, 2012).&lt;a title="" style="mso-footnote-id: ftn1" href="#_ftn1" name="_ftnref1"&gt;&lt;span style="mso-special-character: footnote"&gt;&lt;span class="MsoEndnoteReference"&gt;[1]&lt;/span&gt;&lt;/span&gt;&lt;/a&gt; In that case, the relator, Bryan Sandager, filed suit against nineteen information technology (&amp;ldquo;IT&amp;rdquo;) government contractors in the U.S. District Court for the District of Minnesota alleging that they violated the FCA by misrepresenting the country of origin of products that were sold to the government through the GSA Advantage! website. Nowhere in his complaint or amended complaint did Sandager allege &amp;ndash; let alone intimate &amp;ndash; that he had any inside knowledge or information regarding any of the defendants. Instead, he based his allegations entirely on publicly available information that he had gleaned &amp;ldquo;through his long-held position in the industry.&amp;rdquo; Sandager had worked as a corporate compliance officer at one of the defendants&amp;rsquo; competitors.&lt;/p&gt;
&lt;p&gt;The defendants moved to dismiss on several grounds. First, in an issue of first impression in the Eighth Circuit, nine of the defendants argued that the case should be dismissed pursuant to the so-called &amp;ldquo;first-to-file bar,&amp;rdquo; 31 U.S.C. &amp;sect; 3730(b)(5), because Sandager&amp;rsquo;s allegations were based on the same underlying fraudulent conduct as earlier-filed &lt;em&gt;qui tam&lt;/em&gt; suits that were pending when Sandager filed his action, and his claims did not give rise to a separate and distinct recovery by the Government. The relator contended that the first-to-file bar was inapplicable because the IT products at issue in his action were different from the IT products in the first-filed cases. The court disagreed, noting that &amp;ldquo;[u]ltimately, the question is whether the Government has sufficient notice of the fraudulent scheme through the first-filed complaint.&amp;rdquo; The court found the previously-filed cases provided the government sufficient notice to uncover the same facts alleged by Sandager and &amp;ldquo;the product distinction is immaterial because the fraudulent scheme alleged [by Sandager] is in material respects the same as alleged&amp;rdquo; in the prior cases.&lt;/p&gt;
&lt;p&gt;The court also addressed the Circuit Court split regarding whether a procedural dismissal of a first-filed case precluded application of the first-to-file bar. Citing to the Sixth Circuit Decision in &lt;em&gt;Walburn v. Lockheed Martin Corp&lt;/em&gt;., 431 F.3d 966 (6th Cir. 2005), the relator contended that the first-to-file bar did not apply because, as to most of the defendants, the previously-filed cases had been dismissed on procedural grounds. The defendants urged the court instead to follow the standard enunciated by the D.C. Circuit Court of Appeals in &lt;em&gt;United States ex rel. Batiste v. SLM Corp&lt;/em&gt;., 659 F.3d 1204, 1209 (D.C. Cir. 2011), which held that the plain language of the statutory text mandates that &amp;ldquo;as long as a first-filed complaint remains pending, no related complaint may be filed.&amp;rdquo; Thus, because the earlier-filed &lt;em&gt;qui tam&lt;/em&gt; suits were pending at the time that Sandager filed his action, the plain language of the first-to-file bar mandated that the amended complaint be dismissed. The court agreed with the defendants and followed &lt;em&gt;Batiste&lt;/em&gt;, noting that &amp;ldquo;&lt;em&gt;Walburn&lt;/em&gt; has been criticized and distinguished.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;All nineteen of the defendants also argued that the amended complaint should be dismissed because it contained only conclusory allegations, and failed to plead the &amp;ldquo;who, what, when, where, and how&amp;rdquo; of alleged fraud as required by Fed. R. Civ. P. 9(b). For example, the amended complaint did not include details regarding any sales that allegedly violated the FCA, including &amp;ldquo;the precise Government purchasing agency, the exact purchase order, the price of the goods sold, and the amount the Government paid for the goods.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The defendants also argued that &amp;ldquo;in no instance does [the relator] provide any details as to when and, more importantly, if the Defendant actually sold non-conforming products to the Government.&amp;rdquo; In response, Sandager contended that he did not need to allege details regarding actual sales. Instead, because products allegedly were &amp;ldquo;offered for sale . . . the &amp;lsquo;logical conclusion&amp;rsquo; is that actual sales occurred.&amp;rdquo; In addition, because he alleged a scheme extending over a long period, Sandager contended that he was not required to &amp;ldquo;allege the specific details of every fraudulent claim.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The court recognized that Sandager is not required to allege the details of each and every fraudulent claim. However, he is required &amp;ldquo;to plead at least one representative example of an actual false claim.&amp;rdquo; The court noted that &amp;ldquo;[t]here is abundant caselaw in support of the court&amp;rsquo;s conclusion that Sandager&amp;rsquo;s failure to allege&amp;mdash;and acknowledged inability to allege&amp;mdash;actual sales is fatal to his claims.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Each of the Defendants sought dismissal of the amended complaint with prejudice on futility grounds, while the relator requested 30 days to seek leave to file a second amended complaint. The court again sided with the defendants. It did not believe that Sandager could resolve the &amp;ldquo;fundamental flaws&amp;rdquo; in his amended complaint simply by re-pleading. Nor would discovery be appropriate as it &amp;ldquo;would contradict the FCA&amp;rsquo;s purpose and procedure.&amp;rdquo; Accordingly, the court dismissed the action with prejudice.&lt;/p&gt;
&lt;p&gt;The court&amp;rsquo;s ruling in &lt;em&gt;Sandager&lt;/em&gt; was in line with the holdings of several other courts that recently have addressed similar situations where an opportunistic relator either alleges the same fraudulent scheme as a previously-filed action or fails to plead with particularity even one example of a false claim. Relators cannot avoid the first-to-file bar merely by alleging sales of different products if the government already had notice of the same underlying scheme based on allegations in an earlier-filed case; nor is it enough for a relator merely to allege a theory or methodology as to how a company &lt;em&gt;could have&lt;/em&gt; violated the False Claims. Instead, compliance with Rule 9(b) mandates that specific details be alleged by a relator showing the &amp;ldquo;who, what, when, where, and how&amp;rdquo; of the alleged fraud. Were courts to hold otherwise, it would open the floodgates of baseless lawsuits by opportunistic relators and cause companies to needlessly incur significant resources fending off countless discovery fishing expeditions.&lt;br /&gt;
&lt;br clear="all" /&gt;
&lt;hr width="33%" align="left" size="1" /&gt;
&lt;a class=" FCK__AnchorC FCK__AnchorC FCK__AnchorC FCK__AnchorC" title="" style="mso-footnote-id: ftn1" href="#_ftnref1" name="_ftn1"&gt;&lt;span class="MsoFootnoteReference"&gt;&lt;span style="mso-special-character: footnote"&gt;&lt;span class="MsoFootnoteReference"&gt;[1]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&amp;nbsp;In the interest of full disclosure, Sheppard Mullin represented three of the defendants in this matter. Christopher Loveland and Jonathan Aronie were lead counsel.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/1Ye-dkVitQQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/1Ye-dkVitQQ/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/05/articles/fca/another-us-district-court-follows-the-lead-of-the-dc-circuit-in-addressing-the-firsttofile-bar-circuit-split-and-pushes-back-against-an-opportunistic-relator/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">FCA</category><category domain="http://www.governmentcontractslawblog.com/articles">False Claims</category>
         <pubDate>Mon, 14 May 2012 11:25:56 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/05/articles/fca/another-us-district-court-follows-the-lead-of-the-dc-circuit-in-addressing-the-firsttofile-bar-circuit-split-and-pushes-back-against-an-opportunistic-relator/</feedburner:origLink></item>
            <item>
         <title>Avoiding "Embarrassment" In Contract Disputes Act Litigation: Routine vs. Non-Routine Requests For Payment</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/chale"&gt;Christopher E. Hale&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contractors pursuing claims against the government under the Contract Disputes Act (&amp;ldquo;CDA&amp;rdquo;) can often fall victim to the jurisdictional pitfalls of the Act from the very start of the claims process, &lt;em&gt;i.e.&lt;/em&gt;, with the claim itself. After a contracting officer denies a claim under the CDA, a contractor can appeal the decision to either a Board of Contracts Appeals or the U.S. Court of Federal Claims. However, there is no shortage of cases in which such appeals are dismissed for lack of jurisdiction because the original requests for payment did not constitute &amp;ldquo;claims&amp;rdquo; under the CDA.&lt;/p&gt;&lt;p&gt;One recent illustration of this problem involved the distinction between routine and non-routine requests for payment, as addressed by a recent split-panel decision of the United States Court of Appeals for the Federal Circuit, &lt;em&gt;Parsons Global Services, Inc. v. Secretary of the Army&lt;/em&gt;, No. 2011-1201 (Fed. Cir. Apr. 20, 2012).&lt;/p&gt;
&lt;p&gt;The case centered on the termination for convenience of several task orders under an indefinite-delivery-indefinite quantity contract awarded by the Army to Parsons for design-build work in Iraq. Parsons had entered into a subcontract with Odell International, Inc. (&amp;ldquo;Odell&amp;rdquo;) to construct health care facilities and deliver medical equipment in Iraq pursuant to the prime contract.&lt;/p&gt;
&lt;p&gt;Shortly before the task orders were terminated for convenience by the Government, the Defense Contract Audit Agency (&amp;ldquo;DCAA&amp;rdquo;) determined that Odell had been mistakenly billing Parsons using a lower overhead rate than was specified in the subcontract. Odell then invoiced Parsons for the difference, but Parsons refused to pay the invoice and submitted a termination settlement proposal to the Termination Contracting Officer (&amp;ldquo;TCO&amp;rdquo;) without including the disputed Odell costs. Two years later, as part of settlement of the prime contract, DCAA audited Parsons' billed costs, including Odell's costs, and determined that Odell's costs at the higher overhead rate were supported and appropriate. Odell submitted a new invoice for the difference, and Parsons submitted three payment requests for the additional Odell costs to be paid directly by government. The TCO declined to act on the requests to settle directly with Odell. Parsons then submitted a sponsored &amp;ldquo;Certified Claim for Payment&amp;rdquo; under the CDA on behalf of Odell to the Procurement Contracting Officer (&amp;ldquo;PCO&amp;rdquo;), and appealed the PCO's denial of the claim to the Armed Services Board of Contract Appeals (&amp;ldquo;ASBCA&amp;rdquo;).&lt;/p&gt;
&lt;p&gt;The Government moved to dismiss for lack of jurisdiction, arguing that Parsons' routine request for payment to the PCO did not amount to a claim under the CDA. Parsons countered that, because its requests for payment occurred two years after the termination of the task orders and thus could not be subject to routine invoicing and termination procedures, the request was non-routine and sufficient by itself to constitute a claim. The ASBCA sided with the Government and dismissed the claim.&lt;/p&gt;
&lt;p&gt;On appeal, the Federal Circuit affirmed the ASBCA's decision, holding that Parsons' request for payment was not a claim as defined in FAR 2.101. Under the FAR, demands for payment can be classified as either &amp;ldquo;routine&amp;rdquo; or &amp;ldquo;non-routine.&amp;rdquo; If the request is &amp;ldquo;non-routine,&amp;rdquo; then it constitutes a claim under the CDA so long as &amp;ldquo;it be (1) a written demand, (2) seeking, as a matter of right, (3) the payment of money in a sum certain.&amp;rdquo; However, if the request is &amp;ldquo;routine,&amp;rdquo; a pre-existing dispute is necessary for it to constitute a claim under the CDA.&lt;/p&gt;
&lt;p&gt;As the Federal Circuit detailed, non-routine requests for payment typically spring from additional or unforeseen costs not covered by the contract:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;Such requests include requests for equitable adjustments for costs incurred from &amp;ldquo;government modification of the contract, differing site conditions, defective or late-delivered government property or issuance of a stop work order&amp;rdquo; and other government-ordered changes; for damages resulting from the government's termination for convenience and termination settlement proposals that have reached an impasse; for compensation for additional work not contemplated by the contract but demanded by the government; for the return of contractor property in the government's possession; and for damages stemming from the government's breach of contract or cardinal change to the contract.&lt;/p&gt;
&lt;p&gt;In contrast, according to the Federal Circuit, the request for payment of Odell's costs made to the PCO was routine because the costs were explicitly covered by the contract and, but for the billing error, would have been subject to routine invoicing during contract performance. Furthermore, the routine request was not subject to a pre-existing dispute because the PCO, the appropriate official to evaluate the request, never received a proper request for payment prior to the improper &amp;ldquo;Certified Claim for Payment.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;In a somewhat scathing dissent, Judge Newman posited that major billing errors, such as Odell's, are neither foreseen nor intended and cannot be characterized as routine. However, stepping away from the esoteric classification of routine and non-routine requests for payment, Judge Newman threw the facts of the case &amp;ndash; in which &amp;ldquo;a simple correction of a billing error has morphed into a nearly four-year litigation, with no end in sight&amp;rdquo; &amp;ndash; into sharp relief:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;The agency's refusal to pay Parson's claim, having acknowledged the obligation and having audited it through its own Audit Agency, is contrary to the guiding principle that &amp;ldquo;The Federal Acquisition System will [c]onduct business with integrity, fairness, and openness.&amp;rdquo; . . . . This lengthy litigation of a conceded governmental obligation is an embarrassment.&lt;/p&gt;
&lt;p&gt;To avoid being caught in such an &amp;ldquo;embarrassment,&amp;rdquo; contractors should take care when submitting claims pursuant to the CDA to ensure that a request for payment that could be classified as routine is subject to a pre-existing dispute. Otherwise, the contractor might find years later that its claims process was flawed from the start and must begin anew &amp;ndash; assuming the statute of limitations has not already run its course.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/-G_BAMIflmE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/-G_BAMIflmE/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/05/articles/appeals/avoiding-embarrassment-in-contract-disputes-act-litigation-routine-vs-nonroutine-requests-for-payment/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Appeals</category><category domain="http://www.governmentcontractslawblog.com/articles">Termination</category>
         <pubDate>Mon, 14 May 2012 11:24:30 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/05/articles/appeals/avoiding-embarrassment-in-contract-disputes-act-litigation-routine-vs-nonroutine-requests-for-payment/</feedburner:origLink></item>
            <item>
         <title>FCPA Industry Sweep Strikes Hollywood</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/jhynes"&gt;John M. Hynes&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In the past, we have reported on a number of Foreign Corrupt Practices Act (&amp;quot;FCPA&amp;quot;) &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/articles/fcpa/"&gt;developments&lt;/a&gt; and have furnished subscribers with a &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/uploads/file/FCPA%20Book.pdf"&gt;primer on the FCPA&lt;/a&gt;. The latest developments in this area relate to an investigation of the motion picture industry and its activities in China.&lt;/p&gt;
&lt;p&gt;On April 26, 2012, Reuters reported that the US Securities and Exchange Commission (&amp;quot;SEC&amp;quot;) recently sent letters of inquiry to several prominent movie studios seeking information about their dealings in China that may constitute violations of the FCPA. Later reports indicate that the letters were sent to Twentieth Century Fox, Paramount Pictures, Sony Pictures, Universal Pictures, Walt Disney Studios, Warner Bros., and Dreamworks Animation.&lt;/p&gt;&lt;p&gt;&lt;u&gt;Background of the SEC Inquiry&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;While the specific nature of the alleged improper payments has not been disclosed, the SEC letters of inquiry reportedly focus on potential unlawful payments to the state-owned China Film Group (&amp;quot;CFG&amp;quot;), which has historically controlled the Chinese film market. The CFG, however, has denied any involvement in the inquiry.&lt;/p&gt;
&lt;p&gt;This inquiry comes at a time when the Chinese film industry is booming. In 2011, Chinese box office revenue grew about 35% to $2.1 billion, most of which was generated by 3D films. On the heels of this growth, in February 2012, the CFG eased restrictions on the entry of foreign films into China, exempting 14 premium format films (e.g., 3D films) from the limit of 20 foreign films per year. Perhaps not coincidentally, the CFG passed these relaxed restrictions soon after China's Vice President, Xi Jinping, visited Washington, DC and Los Angeles in February 2012.&lt;/p&gt;
&lt;p&gt;Hollywood studios have taken advantage of the growing Chinese film industry, inking a wave of deals both before and after the CFG eased its foreign film restrictions. For example, in 2011, Dreamworks' Kung Fu Panda was the highest grossing animated movie in China, raking in about $100 million in box office sales. Moreover, in February 2012, Dreamworks announced its plan to build a production studio in Shanghai with some of the largest media firms in China. Disney has also taken advantage of the favorable film industry climate in China, recently announcing that the next Iron Man film will be co-produced in China pursuant to an agreement among Disney, its Marvel Studios unit, and China's DMG Entertainment.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;FCPA Industry Sweeps&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;This inquiry is the latest in a series of so-called &amp;quot;industry sweeps&amp;quot; conducted by US regulators designed to root out potential FCPA violations across particular business sectors. The SEC and Department of Justice (&amp;quot;DOJ&amp;quot;) have been known to launch wide-ranging FCPA investigations into multiple companies when they have reason to believe that the alleged conduct represents a pattern or practice within the industry. Because industry sweeps are often triggered by perceived wrongdoing within only one particular company, the Government may investigate companies without any evidence or specific allegations of wrongdoing.&lt;/p&gt;
&lt;p&gt;Over the past decade, the U.S. Government has devoted significant resources to FCPA industry sweeps. For example, the SEC recently launched inquiries into at least 10 financial services firms regarding whether they made improper payments in seeking investments from sovereign wealth funds. The SEC and DOJ have also recently been conducting FCPA investigations into various pharmaceutical and medical device companies, including Johnson &amp;amp; Johnson, Pfizer, and Merck. Johnson &amp;amp; Johnson agreed to pay $70 million to settle the allegations against it. Additionally, in 2007, the SEC and DOJ began launching FCPA investigations involving at least seven oil and gas companies, including Panalpina World Transport and Transocean, resulting in more than $230 million in disgorgement, fines, and penalties.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;FCPA Enforcement Activity Leading Up to Movie Industry Sweep&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;The movie industry sweep comes as no surprise to many due to recent FCPA enforcement activity involving the film industry and the Government's longstanding focus on potential FCPA issues in China. In September 2009, a federal jury in Los Angeles convicted two Hollywood film executives &amp;ndash; Gerald and Patricia Green &amp;ndash; of substantive FCPA violations and conspiracy to violate the FCPA for paying approximately $1.8 million in bribes to the former governor of the Tourism Authority of Thailand in exchange for contracts to operate the annual Bangkok International Film Festival worth more than $13.5 million. Both executives were sentenced to six months in prison.&lt;/p&gt;
&lt;p&gt;Additionally, while the growing Chinese economy offers a wealth of opportunities for American businesses, China has long been a primary focus of the U.S. Government's FCPA enforcement efforts. The prevalence of state-controlled entities coupled with widespread corruption and questionable business traditions makes China an FCPA trap for unwary American businesses. Indeed, between 2006 and 2011, about 9% of all FCPA enforcement actions involved activity in China.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;What this All Means for Companies in the Film Industry&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;The SEC's strategy in sending letters of inquiry to multiple movie studios suggests that it is taking an industry-wide approach to this matter. As such, companies and individuals across the entire film industry could be at risk and should react accordingly. This risk is not limited to major movie studios, as the FCPA applies to a broad range of entities and individuals. Indeed, the recent uptick in FCPA enforcement actions against individuals, including the convictions of two film executives discussed above, suggests that the Government may eventually seek FCPA charges against individuals involved in the alleged illegal activity as well as the companies. In addition to disgorgement, fines, and penalties faced by both individuals and companies, individuals can face lengthy prison sentences for violating the FCPA.&lt;/p&gt;
&lt;p&gt;Companies can take various steps to ensure that they are prepared if and when the Government comes knocking on their door. While it is always advisable to have a robust and effective FCPA compliance program in place, it is even more important now for companies in the film industry to ensure that their compliance programs are up-to-date and being properly implemented so that they can gain credit if the Government launches an investigation. This is especially true for film companies with dealings in China, as these companies are on the SEC's radar. To this end, film companies should consider a privileged review of their FCPA compliance programs by outside counsel to ensure that they include all the components that the Government deems necessary, including anti-corruption policies and procedures, training and communication, third-party due diligence, anti-corruption contract clauses, internal accounting controls, auditing of program effectiveness, and response to improper conduct and remedial action.&lt;/p&gt;
&lt;p&gt;At-risk companies should also consider a privileged internal review by counsel to determine whether any FCPA issues exist and, if so, decide whether to disclose the issues to the Government. While companies can earn cooperation credit for self-disclosing potential violations, the question of whether and what to voluntarily disclose to the Government is a complex decision involving both risks and rewards for the company. Irrespective of whether a disclosure is made, however, launching a preemptive internal review will allow the company to stay ahead of the Government and be best prepared in the event that the Government initiates its own inquiry.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/YrBC5aMLQ00" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/YrBC5aMLQ00/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/05/articles/fcpa/fcpa-industry-sweep-strikes-hollywood/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Bribery, Gratuities, and Kickbacks</category><category domain="http://www.governmentcontractslawblog.com/articles">FCPA</category>
         <pubDate>Mon, 14 May 2012 11:23:46 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/05/articles/fcpa/fcpa-industry-sweep-strikes-hollywood/</feedburner:origLink></item>
            <item>
         <title>The Federal Government Takes Aim at Medicare Fraud</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/jbarton"&gt;Joseph Barton&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;On May 2, 2012, Federal agents with the Department of Justice's (&amp;ldquo;DOJ&amp;rdquo;) special task force made the biggest Medicare bust in U.S. history, and a splash in the media, when it cracked down on a number of unrelated Medicare fraud schemes across the country that resulted in an alleged $450 million in false claims being submitted to Medicare over the past six years. A total of 107 people were arrested, including doctors, nurses, social workers, office managers, and patient recruiters. Charges ranged from submitting false billing for home healthcare, mental health services, HIV infusions, and physical therapy, to money laundering and receiving kickbacks.&lt;/p&gt;&lt;p&gt;With the President and Congress under pressure to ensure Medicare's fiscal sustainability, DOJ has committed itself to vigorously investigating and prosecuting Medicare fraud. The FBI currently has 500 agents and analysts investigating 2,600 cases of alleged healthcare fraud and has charged 1,300 people since 2007 for submitting false claims to Medicare. In addition, Lanny Breuer, the head of the DOJ's criminal division, has commented that the recent Medicare busts should serve as a reminder to health care providers that they &amp;ldquo;risk prosecution and prison time every time they submit a false claim.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;With the Federal Government taking aim at Medicare fraud, here are few things for which healthcare providers should be on the lookout:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;strong&gt;&lt;u&gt;Kickbacks&lt;/u&gt;&lt;/strong&gt;: The federal Anti-Kickback Statute, 42 U.S.C. &amp;sect;1328-7b(b), prohibits any offer, payment, solicitation, or receipt of money, property, or remuneration to induce or reward the referral of patients or healthcare services payable by Medicare. These improper payments can come in many different forms, including: referral fees, finder&amp;rsquo;s fees, productivity bonuses, discounted leases, discounted equipment rentals, research grants, speaker&amp;rsquo;s fees, excessive compensation, and free or discounted travel or entertainment. Kickbacks can also constitute a violation of the federal False Claims Act (&amp;ldquo;FCA&amp;rdquo;), 31 U.S.C. &amp;sect;&amp;sect; 3729-3733.&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;&lt;strong&gt;Up-Coding&lt;/strong&gt;&lt;/u&gt;: Billing Medicare involves a complex series of codes that assign a dollar value to the procedures and services performed based on their complexity. Up-coding occurs when a claim is submitted for a more complex procedure than was actually performed. Up-coding is a favorite target of health care- related FCA claims.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;&lt;u&gt;Unbundling and Bundling&lt;/u&gt;&lt;/strong&gt;: Medicare has special reimbursement rates for groups of procedures that are typically performed together, such as laboratory tests. &amp;ldquo;Unbundling&amp;rdquo; occurs when bundled procedures are billed separately in order to exceed the group reimbursement rate. Conversely, &amp;ldquo;bundling&amp;rdquo; refers to the artificial combination of tests and procedures in such a manner that they are not separately available, which results in the performance of and billing for unnecessary tests. Unbundling and bundling can constitute violations of the FCA.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;&lt;u&gt;False Certifications&lt;/u&gt;&lt;/strong&gt;: When physicians, hospitals, and other health care providers submit bills to Medicare, they are required to include a number of certifications, including that the services were medically necessary, were actually performed, and were performed in accordance with all applicable rules and regulations. False certifications are easy prey for whistleblowers under the FCA.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;&lt;u&gt;Improper Financial Interests&lt;/u&gt;&lt;/strong&gt;: The federal Stark law, 42 U.S.C. &amp;sect;&amp;sect; 1395nn and 1396b, generally prohibits physicians and members of their immediate families from having financial interests in entities that perform certain designated health services to which they refer patients or from which they order goods and services paid for by Medicare.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;By keeping an eye out for these types of practices, which are commonly targeted for Medicare fraud allegations, healthcare providers can avoid substantial liabilities.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/NA1ljnJJsHg" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/NA1ljnJJsHg/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/05/articles/false-claims/the-federal-government-takes-aim-at-medicare-fraud/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Bribery, Gratuities, and Kickbacks</category><category domain="http://www.governmentcontractslawblog.com/articles">FCA</category><category domain="http://www.governmentcontractslawblog.com/articles">False Claims</category>
         <pubDate>Mon, 14 May 2012 11:22:09 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/05/articles/false-claims/the-federal-government-takes-aim-at-medicare-fraud/</feedburner:origLink></item>
            <item>
         <title>The Sisyphean Task Of Dodd-Frank Rulemaking</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/amoshirnia"&gt;Anthony N. Moshirnia&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Much has been written in this space and others regarding the Dodd&amp;ndash;Frank Wall Street Reform and Consumer Protection Act (&amp;ldquo;Dodd-Frank Act&amp;rdquo;), and its likely and observed impact on the business and legal landscape (e.g., &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/08/articles/corporate-governance/the-dodd-frank-act-a-guide-to-the-corporate-governance-executive-compensation-and-disclosure-provisions/"&gt;executive compensation&lt;/a&gt;, &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/02/articles/fcpa/2010-fcpa-year-in-review/"&gt;whistleblower incentives&lt;/a&gt;, and &lt;a target="_blank" href="http://www.globaltradelawblog.com/tag/dodd-frank/"&gt;&amp;ldquo;conflict minerals&amp;rdquo;&lt;/a&gt;. Not least among the Act&amp;rsquo;s effects is its mandate for a large number of rulemakings across government regulatory bodies. In total, the Dodd-Frank Act mandated 398 different rulemakings from 20 different regulatory agencies. In some cases, the Act requires more than one agency to issue rules on the same topic. Congress also specified a rulemaking schedule that applies to most of the rules required under the Act. 275 of the required rulemakings carry Congressionally mandated deadlines or annual requirements.&lt;/p&gt;&lt;p&gt;So far, regulators&amp;rsquo; ability to stick to this schedule has been underwhelming. As of May 1, 2012, a total of 221 Dodd-Frank rulemaking deadlines have passed. Regulators have only met 73 of those deadlines with finalized rules, a mere one-third of those required. Regulators failed to release even &lt;em&gt;proposed&lt;/em&gt; rules for 21 of those 148 missed deadlines.&lt;/p&gt;
&lt;p&gt;Indeed, of the total 398 rulemakings mandated by the Dodd-Frank Act, only 108 of them have been met with final rules. Regulators have proposed rules that would have met the requirement for 146 additional rulemakings &amp;ndash; had they been finalized on schedule. No proposals have been made for the remaining 144 rulemakings, although the deadlines for some of them have not yet passed.&lt;/p&gt;
&lt;p&gt;In light of the current rulemaking backlog, it appears that we may be waiting to assess the final impact of the Dodd-Frank Act for many months to come.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/pEdR599dnXs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/pEdR599dnXs/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/05/articles/proposed-rules/the-sisyphean-task-of-doddfrank-rulemaking/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Proposed Rules</category>
         <pubDate>Mon, 14 May 2012 11:20:24 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/05/articles/proposed-rules/the-sisyphean-task-of-doddfrank-rulemaking/</feedburner:origLink></item>
            <item>
         <title>In the Tradition of Gilda Radner, the Court of Appeals for the Federal Circuit Proclaims "Never Mind" in Zoltek II</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/lvictorino"&gt;Louis D. Victorino&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The United States Court of Appeals for the Federal Circuit (CAFC) recently issued a so-called &lt;em&gt;en banc&lt;/em&gt; (all judges of the court) decision with great importance to Federal Government contractors. In &lt;em&gt;Zoltek Corp. v. United States&lt;/em&gt;, Fed. Cir., No. 2009-5135, March 14, 2012 (&amp;quot;&lt;em&gt;Zoltek II&lt;/em&gt;&amp;quot;), the Court redefined the scope of the statute underlying the Federal Acquisition Regulation (FAR) &amp;quot;Authorization and Consent&amp;quot; clause, 28 U.S.C. &amp;sect;1498. In so doing, the Court confirmed Federal Government contractor immunity from patent infringement suits in instances where the patent infringement may have occurred in whole or in part outside of the United States. The more fundamental holding of the case was to reverse its own prior decision in the same case (&amp;ldquo;Zoltek I&amp;rdquo;), in which the CAFC had held that &amp;sect;1498 does not waive Federal Government patent immunity from certain patent infringements occurring in part outside the United States.&lt;/p&gt;&lt;p&gt;Zoltek Corporation (Zoltek), is a U.S. corporation headquartered in St. Louis, MO, and is the assignee of rights in a U.S. patent related to manufacturing processes and methods used for the production of carbon fiber sheets. Two types of fiber carbon products allegedly were manufactured through the use of methods covered by the Zoltek patent. The allegedly infringing resulting products were used by Lockheed Martin Corporation (Lockheed) in the manufacture of F-22 jet aircraft, designed and built, of course, under a U.S. Government contract. The carbon fiber products were manufactured from fiber carbon components in one instance manufactured in Japan and finished in the U.S. and in a second instance manufactured entirely in Japan and imported into the U.S.&lt;/p&gt;
&lt;p&gt;In its original complaint, Zoltek sued the United States under 28 U.S.C. &amp;sect;1498(a) in the United States Court of Federal Claims (COFC) alleging, in relevant part, that its patent was infringed because the F-22 related carbon fiber products were used or manufactured by or for the U.S. without a license or other legal right. No claims were asserted against Lockheed. In relevant part, 28 U.S.C. &amp;sect;1498(a) provides:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;(a) Whenever an invention described in and covered by a patent of the United States is used or manufactured by or for the United States without license of the owner thereof or lawful right to use or manufacture the same, the owner&amp;rsquo;s remedy shall be by action against the United States in the United States Court of Federal Claims for the recovery of his reasonable and entire compensation for such use and manufacture.&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;* * *&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;For the purposes of this section, the use or manufacture of an invention described in and covered by a patent of the United States by a contractor, a subcontractor, or any person, firm, or corporation for the Government and with the authorization or consent of the Government, shall be construed as use or manufacture for the United States.&lt;/p&gt;
&lt;p&gt;The U.S. (Government) moved for summary judgment on this portion of the Zoltek lawsuit based on the language of sub-section (c) of 28 U.S.C. &amp;sect;1498. That sub-section provides, in total, &amp;quot;[t]he provisions of this section shall not apply to any claim arising in a foreign country.&amp;quot; The Government argued that this section precluded recovery by Zoltek under its &amp;quot;methods&amp;quot; patent claims because some or all of the infringement occurred in Japan and, thus, arose &amp;quot;in a foreign country.&amp;quot; The COFC held, in part, that &amp;sect;1498 did not waive Government's sovereign immunity to all infringements (direct infringements but not indirect infringements) but ultimately denied the Government's motion. Both parties appealed the court's decision on various grounds.&lt;/p&gt;
&lt;p&gt;On appeal, the CAFC held, in its first decision in the Zoltek matter, that a &amp;quot;direct infringement&amp;quot; of a patent under 35 U.S.C. &amp;sect;271 was a predicate for Government liability under &amp;sect;1498(a). The CAFC further held that a &amp;quot;process&amp;quot; asserted to be covered by a method patent cannot give rise to an infringement &amp;quot;within&amp;quot; the United States unless each and every step of the process is performed in the U.S. Since some or all of the processes at issue in the litigation occurred in Japan, the &amp;sect;1498(a) remedy was not available. &lt;em&gt;Zoltek Corp. v. United States&lt;/em&gt;, 442 F.3d 1345, 1350 (Fed. Cir. 2006) (&amp;quot;&lt;em&gt;Zoltek I&lt;/em&gt;&amp;quot;). The CAFC did not address contractor patent infringement immunity under &amp;sect;1498(a). The case was remanded to the COFC for further proceedings. &lt;em&gt;Id&lt;/em&gt;. at 1353.&lt;/p&gt;
&lt;p&gt;On remand, Zoltek sought leave to amend its complaint to add an infringement claim against Lockheed based on 35 U.S.C. &amp;sect;271 and sought, further, to have the matter transferred to a federal district court in Georgia. The Government argued that &amp;sect;1498(a), while not waiving sovereign immunity for Zoltek's patent claims, nevertheless provided Lockheed immunity from Zoltek's suit and, therefore, there was no jurisdiction in the federal district court in Georgia. The COFC rejected the Government's arguments and found that it was in the interest of justice to transfer the case to Georgia. Subsequently, the COFC certified for appeal to the CAFC the issue of Lockheed immunity under &amp;sect;1498(a).&lt;/p&gt;
&lt;p&gt;In considering the merits of the appeal, the CAFC came to a disturbing conclusion regarding the implications of its prior decision in &lt;em&gt;Zoltek I&lt;/em&gt;. It stated the issue as follows:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;In confronting the question of whether a contractor acting under Government authority could be held liable for patent infringement, in a situation in which we had previously held the Government not liable for the allegedly infringing actions of its contractor, we realized that one of two consequences would result. Either we had to conclude that a patentee&amp;rsquo;s well-pleaded complaint of infringement in the United States of a United States patent in these circumstances fails to state a cause of action against both the Government and the Government&amp;rsquo;s contractor, or we would have to override the long-standing understanding of the statutory framework that a contractor working for the Government is immune from individual liability for patent infringement occurring in the course of conducting the Government&amp;rsquo;s contract.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Zoltek II&lt;/em&gt;, at page 8.&lt;/p&gt;
&lt;p&gt;The CAFC concluded, with one dissent, that neither of these options was acceptable and, instead, ruled to overturn its earlier decision in several respects. First, the Court ruled that the COFC and the CAFC's earlier decision had wrongly relied on case law to conclude that &amp;sect;1498(a) covered only direct infringements and not indirect infringements. The CAFC reviewed the prior case law relied upon in &lt;em&gt;Zoltek I&lt;/em&gt; and found that statements used by the COFC to reach its decision regarding the scope of &amp;sect;1498(a) were &lt;em&gt;dicta&lt;/em&gt;. Second, the CAFC found that unauthorized &amp;quot;sales&amp;quot; and &amp;quot;use&amp;quot; of products incorporating patented technology were indirect patent infringements falling within the coverage of &amp;sect;1498(a). Finally, the CAFC reversed its prior holding that all steps in a &amp;quot;process&amp;quot; or &amp;quot;method&amp;quot; patent must be infringed in the United States for &amp;sect;1498(a) to apply.&lt;/p&gt;
&lt;p&gt;The practical result of &lt;em&gt;Zoltek&lt;/em&gt; is that very few sales to the U.S. Government by contractors and subcontractors of products or services that infringe patents will not be covered by &amp;sect;1498(a). The Court's holding that indirect patent infringements are covered by &amp;sect;1498(a) largely achieves this result since &amp;sect;1498(a) states:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;For the purposes of this section, the &lt;u&gt;use&lt;/u&gt; or manufacture of an invention described in and covered by a patent of the United States by a contractor, a subcontractor, or any person, firm, or corporation for the Government and with the authorization or consent of the Government, shall be construed as use or manufacture for the United States.&lt;/p&gt;
&lt;p&gt;28 U.S.C. &amp;sect;1498(a) (emphasis added). This language, together with the Court's holding that not all processes in a process or method patent need be performed in the U.S., encompasses the overwhelming majority of patent infringement cases covered by &amp;sect;1498(a). If a product or service of a contractor is produced through the unauthorized use of a U.S. patent with the authorization and consent of the Government, any resulting patent infringement action must be brought against the Government in the United States Court of Federal Claims. This is, of course, the result that most government contractors believed to be the case prior to the &lt;em&gt;Zoltek I&lt;/em&gt; decision.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/dvH-TTNiVNs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/dvH-TTNiVNs/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/04/articles/patent-rights/in-the-tradition-of-gilda-radner-the-court-of-appeals-for-the-federal-circuit-proclaims-never-mind-in-zoltek-ii/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Intellectual Property</category><category domain="http://www.governmentcontractslawblog.com/articles">Patent Rights</category>
         <pubDate>Mon, 16 Apr 2012 02:20:06 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/04/articles/patent-rights/in-the-tradition-of-gilda-radner-the-court-of-appeals-for-the-federal-circuit-proclaims-never-mind-in-zoltek-ii/</feedburner:origLink></item>
            <item>
         <title>Deciphering the Alphabet Soup - FAPIIS, CPARS, and PPIRS; Don't Look For All This In The FAR</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/bshirk"&gt;Bruce Shirk&lt;/a&gt; and &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David Gallacher&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In March 2010, the U.S. Government rolled out a new tool promised to provide a centralized source for all publicly available contractor past performance and integrity information &amp;ndash; the Federal Performance and Integrity Information System (&amp;ldquo;FAPIIS&amp;rdquo;). We have written multiple times about it (in &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/06/articles/far/fapiis-the-new-integrity-database-for-government-contractors/"&gt;June 2010&lt;/a&gt;, &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/03/articles/fapiis/fapiis-an-update-on-the-integrity-database-for-government-contractors/"&gt;March 2011&lt;/a&gt;, and &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2012/01/articles/fapiis/fapiis-update-on-government-fapiis-postings-quick-contractor-reaction-required/"&gt;January 2012&lt;/a&gt;), including the importance of monitoring the information entered to ensure that past performance evaluations are accurate, complete, and fair, and also to prevent release of proprietary information to the public. But the system continues to evolve and, as contractors try to manage the information in FAPIIS, many companies find the process baffling due to (among other things) the multiplicity of modules within the system and the acronyms used to identify them. In fairness, government personnel tasked with implementing FAPIIS have developed on-line training to assist contractors in navigating this complex system. That said, not everyone involved in government contracting can or will take the training, but everyone does need a basic understanding of FAPIIS. So keep reading, because you won't find this information in the FAR.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;&amp;ldquo;What's in a name?&amp;rdquo; &amp;ndash; Understanding the Past Performance Databases&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Let us begin with a review of the terminology, to assure that we understand the various acronyms and government IT systems. Generally speaking, the government has three primary systems or modules that contain past performance data:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;&lt;u&gt;Contractor Performance Assessment Reporting System (&amp;ldquo;CPARS&amp;rdquo;)&lt;/u&gt;. For more than a decade, the government has used the CPARS module to centralize and harmonize past performance information. The main input for this system is a written &amp;ldquo;Report Card&amp;rdquo; issued by a Contracting Officer, which (in most circumstances) is called a Contractor Performance Assessment Report (&amp;ldquo;CPAR&amp;rdquo;), on which contractors have the opportunity to comment and which they can challenge. In this regard, note that multiple reports are commonly abbreviated as CPARs (little &amp;ldquo;s&amp;rdquo;), which is not to be confused with CPARS (capital &amp;ldquo;S&amp;rdquo;), which is the acronym identifying the database as a whole. The CPARS database is available to source selection officials government-wide, but it is not publicly available. &lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;Past Performance Information Retrieval System (&amp;ldquo;PPIRS&amp;rdquo;)&lt;/u&gt;. PPIRS is a companion system to CPARS. It receives the completed CPARS report cards, including contractor comments, as well as other statistical reports on smaller-value contracts. Additionally, PPIRS receives reports of &amp;ldquo;adverse actions&amp;rdquo; reported by the Contracting Officer, with the information available government-wide. The &amp;ldquo;adverse actions&amp;rdquo; include: (i) a non-responsibility determination; (ii) termination for cause; (iii) termination for default; (iv) defective pricing; (v) a determination of contractor fault; (vi) a determination that the recipient is not qualified; (vii) a termination for material failure to comply; and/or (viii) entry into an Administrative Agreement to resolve a suspension or debarment proceeding. These &amp;ldquo;adverse actions&amp;rdquo; are, with the exception noted in our &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2012/01/articles/fapiis/fapiis-update-on-government-fapiis-postings-quick-contractor-reaction-required/"&gt;January 2012 posting&lt;/a&gt;, eventually made available to the public via FAPIIS, but the balance of the information in PPIRS remains unavailable to the public.&lt;br /&gt;
    &lt;br /&gt;
    The FAR, if read literally, would suggest that PPIRS contains only written past performance evaluations submitted pursuant to the requirement of FAR 42.1502 that &amp;ldquo;agencies shall prepare an evaluation of contractor performance&amp;rdquo; for certain types of contracts over the simplified acquisition threshold of $150,000 (with the Department of Defense having different and higher thresholds). Such information is indeed contained in PPIRS &amp;ndash; but in a separate sub-module called PPIRS-RC (Report Card). Past performance information for contracts beneath the applicable dollar thresholds are contained in another PPIRS module &amp;ndash; PPIRS-SR (Statistical Reporting), which collects quantifiable contractor past performance information regarding delivery, quality, etc., and uses sophisticated algorithms to compare the performance of comparable contractors and classify them accordingly. This past performance information is updated monthly and, like the information contained in PPIRS-RC, is accessible to contractors, who can review and challenge their classifications. Training on PPIRS is available at &lt;a target="_blank" href="http://www.ppirs.gov/"&gt;www.ppirs.gov&lt;/a&gt;. &lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;Federal Performance and Integrity Information System&lt;/u&gt;. Created in 2008 by act of Congress (Pub. L. No. 110-417, Section 872), FAPIIS is, according to FAR 42.1503(f), a &amp;ldquo;module&amp;rdquo; of PPIRS, and includes publicly available information relating to a contractor's integrity, which is provided by both the government and the contractor. This information includes: (i) whether a contractor is included on the &lt;a target="_blank" href="https://www.epls.gov/"&gt;Excluded Parties List&lt;/a&gt;&amp;nbsp;or has entered into an Administrative Agreement with an agency Suspension and Debarment authority; (ii) a statement as to whether a company has been the subject of a criminal, civil, or administrative proceeding that resulted in a conviction, a finding of fault, or an admission of liability relating to performance of a government contract in the past five years; and (iii) reports of government &amp;ldquo;adverse actions&amp;rdquo; (as reported by the Contracting Officer through CPARS).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At the risk of over-simplifying this confusing process, the graphic below illustrates generally how past performance information flows through the government systems and into FAPIIS.&lt;/p&gt;
&lt;p&gt;&lt;img alt="" style="width: 453px; height: 292px" src="http://www.governmentcontractslawblog.com/uploads/image/govcon.JPG" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&amp;ldquo;Clear As Mud&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The government appears to be aware of the confusion it has generated with its past performance &amp;quot;alphabet soup.&amp;quot; To eliminate this confusion, the government has taken a number of steps:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;In recent &lt;a target="_blank" href="http://www.cpars.gov/"&gt;on-line instruction&lt;/a&gt; for CPARS, the government has attempted to distinguish more specifically between CPARS and FAPIIS, describing CPARS as hosting &amp;ldquo;a suite of web-enabled applications that are used to document contractor and grantee performance information that is required by &amp;hellip; FAR Part 42 &amp;hellip; [and] requires documenting additional contractor performance information in the Federal Awardee Performance &amp;amp; Integrity Information System (FAPIIS).&amp;rdquo;&lt;/li&gt;
    &lt;li&gt;In June 2011, the Government proposed amendments to the FAR &amp;ldquo;to require all past performance information be entered into the Contractor Performance Assessment Reporting System (CPARS), the Governmentwide past performance system&amp;rdquo; and to standardize the past performance evaluation criteria. See 76 Fed. Reg. 37704 (June 28, 2011). This rule could clarify that the government-wide past performance portal is &amp;ldquo;CPARS&amp;rdquo; &amp;ndash; not &amp;ldquo;FAPIIS&amp;rdquo; &amp;ndash; but absent an extensive re-education program (and a re-branding campaign for FAPIIS), we doubt that a simple rule change will effectively solve the confusion. The proposed CPARS revision (FAR Case 2009-042) is &lt;a target="_blank" href="http://www.acq.osd.mil/dpap/dars/opencases/farcasenum/far.pdf"&gt;currently under review by DOD legal authorities&lt;/a&gt;, and we expect that a final rule will be issued soon.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Make Sure You Focus on More Than Just FAPIIS&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;While companies are encouraged to stay abreast of information posted in FAPIIS because such information is required to be made publicly available (as we &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2012/01/articles/fapiis/fapiis-update-on-government-fapiis-postings-quick-contractor-reaction-required/"&gt;previously discussed in our blog&lt;/a&gt;), focusing only on FAPIIS ignores the other part of the picture &amp;ndash; the part that your government customers see and use to make their past performance evaluations.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Conclusion &amp;ndash; And More to Come&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hopefully, we have managed to clarify (at least a little bit) your understanding of FAPIIS as a system and how it relates to the other past performance data repositories. In the coming months, we will follow up with additional postings discussing questions that we commonly receive from contractors in these regards, including: &amp;quot;Exactly what information must I report in FAPIIS?&amp;quot; &amp;quot;What must I certify with regard to FAPIIS?&amp;quot; and &amp;quot;What past performance information should I be monitoring, how and when, and what can I do about it?&amp;quot; Stay tuned.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/249nJdzJqL0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/249nJdzJqL0/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/04/articles/compliance/deciphering-the-alphabet-soup-fapiis-cpars-and-ppirs-dont-look-for-all-this-in-the-far/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Compliance</category><category domain="http://www.governmentcontractslawblog.com/articles">Debarment</category><category domain="http://www.governmentcontractslawblog.com/articles">FAPIIS</category><category domain="http://www.governmentcontractslawblog.com/articles">Proposed Regulations</category><category domain="http://www.governmentcontractslawblog.com/articles">Simplified Acquisition Threshold</category><category domain="http://www.governmentcontractslawblog.com/articles">Suspension</category>
         <pubDate>Mon, 16 Apr 2012 02:19:25 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/04/articles/compliance/deciphering-the-alphabet-soup-fapiis-cpars-and-ppirs-dont-look-for-all-this-in-the-far/</feedburner:origLink></item>
            <item>
         <title>Preventing Personal Conflicts Of Interest Among Contractor Employees Performing Acquisition Support Services</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/kszeliga"&gt;Keith Szeliga&lt;/a&gt; and &lt;a target="_blank" href="http://www.sheppardmullin.com/fturner"&gt;Franklin Turner&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;On December 2, 2011, Federal Acquisition Regulation Subpart 3.11 - Preventing Personal Conflicts of Interest for Contractor Employees Performing Acquisition Functions -- took effect. The new Rule imposes a host of compliance obligations on contractors, including the requirement to screen for and prevent personal conflicts of interest when supporting acquisition functions. The Rule also requires contractors to prohibit covered employees from utilizing non-public information for personal gain and to obtain from covered employees executed non-disclosure agreements prohibiting the dissemination of such information.&lt;/p&gt;&lt;p&gt;Two of our Government Contracts lawyers &amp;ndash; Partner Keith Szeliga and Associate Franklin Turner &amp;ndash; recently published a Briefing Paper that assists contractors in understanding the Rule and complying with its requirements.&lt;/p&gt;
&lt;p&gt;Click &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/uploads/file/Szeliga - link.pdf"&gt;here&lt;/a&gt; to view a PDF copy of the article.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/oD0Ik4RRboc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/oD0Ik4RRboc/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/04/articles/compliance/preventing-personal-conflicts-of-interest-among-contractor-employees-performing-acquisition-support-services/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Compliance</category><category domain="http://www.governmentcontractslawblog.com/articles">Compliance Programs</category><category domain="http://www.governmentcontractslawblog.com/articles">Personal Conflicts of Interest</category>
         <pubDate>Mon, 16 Apr 2012 02:18:35 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/04/articles/compliance/preventing-personal-conflicts-of-interest-among-contractor-employees-performing-acquisition-support-services/</feedburner:origLink></item>
            <item>
         <title>Free Trade Agreement Updates - Changes to the WTO GPA and KORUS FTA</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David Gallacher&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2012/02/articles/baa-and-taa/new-2012-updates-to-us-free-trade-agreements-expected-no-progress-with-china/"&gt;In December 2011 the World Trade Organization reached an agreement in principle to implement &amp;ldquo;historic revisions&amp;rdquo; to the World Trade Organization Government Procurement Agreement (WTO GPA)&lt;/a&gt;, a trade agreement covering the public procurement markets in more than 40 WTO member states (including the United States). On March 30, 2012, the WTO GPA formally adopted these revisions. While the updates have been formally agreed upon, it may take months until two-thirds of the signatory countries ratify the agreement and make the changes official. Nevertheless, the international community appears to be moving forward with plans to implement, pending ratification.&lt;/p&gt;&lt;p&gt;Separately, under the recently ratified the U.S./South Korea (&amp;ldquo;KORUS&amp;rdquo;) Free Trade Agreement (&amp;ldquo;FTA&amp;rdquo;), the U.S. Government has waived South Korea's obligations to follow the WTO GPA, to which South Korea has been a signatory since January 1997. KORUS offers greater benefits to U.S. companies in the Korean procurement space compared to the WTO GPA, and where those benefits apply KORUS will, of course, take precedence over the WTO GPA. Toward this end, numerous interim rules have recently been issued to update the Federal Acquisition Regulation, recognizing the new KORUS FTA and reducing the applicable dollar thresholds for purchasing supplies and services from South Korean sources.&lt;/p&gt;
&lt;p&gt;This blog posting provides a brief summary of some of these new changes to the WTO GPA and the KORUS FTA.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Updates to the WTO GPA&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Generally, the updated WTO GPA changes the prior Agreement in two major ways &amp;ndash; through expanded scope and improved flexibility.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Expanded Scope&lt;/u&gt;. The Government estimates that the expanded scope will improve access to approximately $80-$100 billion in U.S. and foreign procurement markets. In this regard, the new Agreement:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Expands coverage to include approximately twelve U.S. executive agencies that were not previously covered by the Agreement (&lt;em&gt;e.g&lt;/em&gt;., the Social Security Administration, the Advisory Council on Historic Preservation, the Court Service and Offender Supervision Agency for the District of Colombia, the Federal Energy Regulatory Commission, the Federal Labor Relations Authority, the Millennium Challenge Corporation, the National Assessment Governing Board, the National Endowment for the Arts, the National Endowment for the Humanities, the U.S. Marine Mammal Commission, and the United States Access Board);&lt;/li&gt;
    &lt;li&gt;Allows access to additional central-government entities (estimated at 150-200) in a number of foreign countries such as European Union nations, Aruba, Hong Kong, Israel, Liechtenstein, South Korea, and Switzerland;&lt;/li&gt;
    &lt;li&gt;Enhances coverage for sub-central entities (such as state, local, regional or provincial governments), particularly those located in Canada, which have historically been exempted from the GPA (this follows &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/04/articles/country-of-origin/recovery-act-and-updates-to-buy-american/"&gt;an agreement reached between the U.S. and Canada in February 2010 &lt;/a&gt;that liberalized access to sub-central entities that were not previously covered by the GPA);&lt;/li&gt;
    &lt;li&gt;Offers full coverage for construction contracts;&lt;/li&gt;
    &lt;li&gt;Expands the scope of specific categories of products that are covered by the GPA; and&lt;/li&gt;
    &lt;li&gt;Gives flexibility for countries further to reduce the applicable dollar thresholds (currently set at $202,000 for purchases of supplies/services by the U.S. Government).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;u&gt;Improved Flexibility&lt;/u&gt;. The new Agreement also seeks to provide more flexible implementation processes and tools that can be more easily understood and that will facilitate better procurement practices across the globe. In this regard, the new Agreement:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Updates the text of the Agreement, purportedly facilitating a &amp;ldquo;plain reading&amp;rdquo; of its terms;&lt;/li&gt;
    &lt;li&gt;Provides procedures for increased transparency among the member countries to verify compliance with the terms of the GPA;&lt;/li&gt;
    &lt;li&gt;Permits increased flexibility to use electronic tools in order to conduct public procurements more efficiently and also to monitor compliance with the GPA obligations;&lt;/li&gt;
    &lt;li&gt;Allows countries greater flexibility in procuring commercial products;&lt;/li&gt;
    &lt;li&gt;Authorizes additional compliance tools to support countries trying to move to a single, universal standard for conducting public procurements;&lt;/li&gt;
    &lt;li&gt;Allows small countries/developing economies more flexibility in structuring their individual public procurement programs;&lt;/li&gt;
    &lt;li&gt;Creates new, future &amp;ldquo;Work Programs&amp;rdquo; that the signatories hope to investigate to allow for improved administration of the GPA, including new ways to harmonize data and implement environmentally-friendly policies; and&lt;/li&gt;
    &lt;li&gt;Encourages a framework that will be more welcoming for new signatories (including, for example, China).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Updates to the FAR to Implement the KORUS FTA&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Beyond the updates to the WTO GPA, there have been additional updates to the regulations to implement the newly implemented U.S./South Korea FTA. This FTA was originally signed in June 2007, but it was not fully ratified by the Senate until October 2011. &lt;em&gt;See&lt;/em&gt; Pub. L. No. 112-41. The FTA includes many different provisions, but (for purposes of this blog), there are at least two key points relating to public procurements.&lt;/p&gt;
&lt;p&gt;First, the U.S. Government has recognized that the new FTA is generally more advantageous for U.S. businesses than the WTO GPA (to which South Korea has been a signatory since January 1997). On March 2, 2012, the U.S. Government waived South Korea's obligations under the WTO GPA because (according to the U.S. Trade Representative) the new FTA generally provides greater and more comprehensive procurement benefits for U.S. companies than the corresponding obligations under the GPA. &lt;em&gt;See&lt;/em&gt; 77 Fed. Reg. 12904.&lt;/p&gt;
&lt;p&gt;Second, on March 7, 2012 the FAR Council issued an interim rule updating FAR Part 25 and implementing the new agreement. &lt;em&gt;See&lt;/em&gt; 77 Fed. Reg. 13952. Perhaps most importantly for companies selling to the U.S. Government, the interim rule lowered the applicable dollar thresholds for purchases of supplies and services, but left unchanged the dollar threshold for construction contracts. The new thresholds are as follows:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" style="width: 456px; height: 134px" src="http://www.governmentcontractslawblog.com/uploads/image/govcon2.JPG" /&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/TUiWdwqEHMc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/TUiWdwqEHMc/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/04/articles/baa-and-taa/free-trade-agreement-updates-changes-to-the-wto-gpa-and-korus-fta/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">BAA and TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">Interim Rule</category><category domain="http://www.governmentcontractslawblog.com/articles">International Contracts</category><category domain="http://www.governmentcontractslawblog.com/articles">International Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">WTO GPA</category>
         <pubDate>Mon, 16 Apr 2012 02:16:58 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/04/articles/baa-and-taa/free-trade-agreement-updates-changes-to-the-wto-gpa-and-korus-fta/</feedburner:origLink></item>
            <item>
         <title>Final Rule for IR&amp;D Reports Fails to Address Most Serious Questions</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David S. Gallacher &lt;/a&gt;and &lt;a target="_blank" href="http://www.sheppardmullin.com/koneill"&gt;Kerry O'Neill&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Last April, &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/04/articles/ird/the-times-they-are-a-changin-independent-research-and-development-may-not-be-so-independent-any-more/"&gt;we wrote about proposed changes to Department of Defense (&amp;quot;DoD&amp;quot;) reporting requirements for independent research and development (&amp;quot;IR&amp;amp;D&amp;quot;), &lt;/a&gt;raising concerns about how the proposed change would tie recoverability of IR&amp;amp;D costs to new reporting and disclosure requirements. Recently, Defense Federal Acquisition Regulation Supplement (&amp;quot;DFARS&amp;quot;) 231.205-18(c) was finalized, with changes. &lt;em&gt;See 77 &lt;/em&gt;Fed. Reg. 4632 (Jan. 30, 2012). This final rule is a mixed bag that got some things right, but also leaves some of the most serious issues unresolved.&lt;/p&gt;&lt;p&gt;&lt;u&gt;First&lt;/u&gt; &amp;ndash; three things that DoD got right.&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;&lt;strong&gt;Elimination of the $50,000 Threshold&lt;/strong&gt;. The proposed rule required IR&amp;amp;D reports from all major contractors generating more than $50,000 annually in IR&amp;amp;D costs. However, the regulations define &amp;quot;major contractors&amp;quot; as contractors whose covered segments are allocated more than $11,000,000 in total IR&amp;amp;D costs during the preceding fiscal year. The two different dollar thresholds created confusion as to who should be reporting and what projects should be included in these reports. The final rule removed the redundant $50,000 threshold, clarifying that all &amp;quot;major contractors&amp;quot; with more than $11,000,000 in allocable IR&amp;amp;D costs must submit reports on all of their IR&amp;amp;D projects, regardless of the dollar value of a specific project. Other non-major contractors, the final rule noted, are welcome to submit reports voluntarily.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Clarification Regarding Classified IR&amp;amp;D Projects&lt;/strong&gt;. The proposed rule would have established a broad-ranging disclosure requirement for &lt;em&gt;all&lt;/em&gt; IR&amp;amp;D projects, without regard to whether a project was classified. The final rule clarified that only unclassified projects should be submitted through the DoD's Defense Technical Information Center (&amp;quot;DTIC&amp;quot;) website &lt;a target="_blank" href="http://www.defenseinnovationmarketplace.mil/"&gt;(www.dtic.mil/ird/dticdb/index.html)&lt;/a&gt;.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Reiterating that Submissions Will Be Protected as Proprietary&lt;/strong&gt;. The proposed rule required general descriptions of IR&amp;amp;D projects, with no guidance on what should be submitted and no assurances of how the information would be handled within the government. The final rule made clear that information reported through the DTIC website would be considered proprietary under the Freedom of Information Act (&amp;quot;FOIA&amp;quot;), 5 U.S.C. &amp;sect; 552(b)(4), and that it would not be subject to public disclosure. Furthermore, DoD clarified that companies are in control of the level of specificity to be included in the reports.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;u&gt;But&lt;/u&gt; &amp;ndash; there are at least three things that DoD simply failed to address in any meaningful manner:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;&lt;strong&gt;Adequacy of Controls at the DTIC Website?&lt;/strong&gt; The American Bar Association, Section of Public Contract Law, pointed out that the security of the DTIC website was questionable, to which DoD merely assured that &amp;quot;adequate controls are in place&amp;quot; and that &amp;quot;sufficient measures are being employed.&amp;quot; We were hoping for more than an assertion of &amp;quot;adequate assurances.&amp;quot; It does a company no good to have its data treated as proprietary under FOIA, where the underlying data source remains at risk.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Role of DCAA in Auditing and Evaluating Reports?&lt;/strong&gt; The final rule acknowledged concerns over tying the allowability of IR&amp;amp;D costs (audited by the Defense Contract Audit Agency (&amp;quot;DCAA&amp;quot;)) to the submission of these technical reports, but DoD addressed these concerns only obliquely. While the final rule states that contracting personnel will retain authority to determine whether IR&amp;amp;D projects are &amp;quot;of potential interest&amp;quot; to the DoD, it also reinforces the fact that collaboration between the technical team and audit team must take place. &amp;quot;[W]hen specialized expertise is required, contracting officers are expected to consult with auditors and other individuals with specialized experience, as necessary, to ensure a full understanding of issues.&amp;quot; This perplexing statement only serves to raise additional questions: When will expertise be required? When will consultation be necessary? What issues will auditors and experts help to resolve? And why are cost auditors involved in an evaluation of a technical project in the first place?&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;What Information Will Be Required in These Reports?&lt;/strong&gt; The final rule states that companies are in control of the level of specificity to be included in the reports, including the types of proprietary information to be included. In fact, &lt;a target="_blank" href="http://www.defenseinnovationmarketplace.mil/resources/Individual_Project_Data_Entry_Instructions_wAppendices.pdf"&gt;the instructions prepared by DTIC for submitting the IR&amp;amp;D reports&lt;/a&gt; identify the information to be entered in the various data fields (project title, project number, status/readiness level, anticipated expenditures, targeted DoD organization, etc.), calling for &amp;quot;a 1-2 sentence summary&amp;quot; of the IR&amp;amp;D project and a brief project description, not to exceed 10,000 alpha numeric characters (about three typed pages). While we appreciate that DoD hopes to limit the overall reporting requirement (a reporting requirement that the proposed rule estimated would take only 30 minutes for each report), we wonder whether DCAA auditors will insist on &amp;quot;more&amp;quot; information when evaluating the quality of the IR&amp;amp;D reports, especially given that DCAA has a long history of over-reaching and of invasive audit demands into areas in which they have no functional expertise. Somehow, we doubt that DCAA will be willing to show much restraint.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Whether requiring these reports is a good idea is now a moot point &amp;ndash; the rule is final and all major contractors are required to report so that the DoD can regain greater visibility into IR&amp;amp;D funding and better evaluate whether the funded projects have a discernible technological purpose that benefits DoD. But, beyond the increased audit scrutiny, we think that this new reporting requirement reflects a continuing shift in DoD's overall policy approach to IR&amp;amp;D, with DoD hungry for &lt;b&gt;more&lt;/b&gt; rights and &lt;b&gt;more&lt;/b&gt; visibility into research and development projects that, by regulation, must remain &lt;b&gt;independent&lt;/b&gt;. Given the high value that is inevitably associated with this incessant search for &lt;b&gt;more&lt;/b&gt;, we are quite sure that companies would rest easier if their concerns were actually addressed in the final rule in a substantive manner.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/NYi-sLkdM44" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/NYi-sLkdM44/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/03/articles/ird/final-rule-for-ird-reports-fails-to-address-most-serious-questions/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Aerospace and Defense</category><category domain="http://www.governmentcontractslawblog.com/articles">Audits</category><category domain="http://www.governmentcontractslawblog.com/articles">B&amp;P</category><category domain="http://www.governmentcontractslawblog.com/articles">Contracting Arrangements for R&amp;D</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Accounting</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Corner</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Principles</category><category domain="http://www.governmentcontractslawblog.com/articles">DCAA</category><category domain="http://www.governmentcontractslawblog.com/articles">IR&amp;D</category><category domain="http://www.governmentcontractslawblog.com/articles">Intellectual Property</category><category domain="http://www.governmentcontractslawblog.com/articles">Legislation</category><category domain="http://www.governmentcontractslawblog.com/articles">Proposed Rules</category><category domain="http://www.governmentcontractslawblog.com/articles">Regulations</category>
         <pubDate>Fri, 16 Mar 2012 09:00:53 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/03/articles/ird/final-rule-for-ird-reports-fails-to-address-most-serious-questions/</feedburner:origLink></item>
            <item>
         <title>MAS March Madness 2012: Final Rule for Increased Competition in MAS/BPA Orders</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/amajor"&gt;Alexander Major&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A year ago, we advised our readers of the interim rule intended to emphasize competition under GSA Federal Supply Schedule (&amp;ldquo;FSS&amp;rdquo;) contracts and FSS Blanket Purchase Agreements (&amp;ldquo;BPAs&amp;rdquo;) &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/04/articles/gsa-schedule/mas-march-madness-increased-competition-in-multiple-award-schedule-orders/"&gt;here&lt;/a&gt;. To recap, the March 2011 interim rule imposed a requirement for varying degrees of competition for orders above the FAR&amp;rsquo;s $3,000 Micropurchase Threshold depending on the type of order being placed (&lt;em&gt;i.e.&lt;/em&gt;, with or without a statement of work (&amp;ldquo;SOW&amp;rdquo;) or placed under a multiple award BPA). The final rule becomes effective April 2, 2012.&lt;/p&gt;&lt;p&gt;The final rule varies very little from the interim rule, with minor changes focusing on BPAs. The final rule:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;Corrects a previous error, which had established $100 million as to the threshold that would trigger a contracting officer's obligation to document the agency&amp;rsquo;s determination for a single award BPA. The corrected trigger is $103 million;&lt;/li&gt;
    &lt;li&gt;Requires that the ordering activity determine, in connection with BPAs for hourly-rate services, that the total price is &amp;ldquo;reasonable&amp;rdquo; and requires further that the determination be documented in the file; and&lt;/li&gt;
    &lt;li&gt;Eliminates the interim rule&amp;rsquo;s requirement, under single-award BPAs, that the contracting officer&amp;rsquo;s annual determination must first be approved by the ordering activity&amp;rsquo;s competition advocate before the exercise of an option to extend the BPA. Although lessening oversight over massive sole source contracting actions, the Board believed the interim rule&amp;rsquo;s approval requirement was &amp;ldquo;too stringent a requirement for the exercise of an option, which is generally within the contracting officer&amp;rsquo;s authority.&amp;rdquo;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/uploads/file/Major - New MAS Ordering Rules.pdf"&gt;updated matrix&lt;/a&gt;, prepared by Jonathan Aronie, co-author with John Chierichella of the &lt;em&gt;GSA Schedule Handbook&lt;/em&gt; (West 2011), provides a useful summary of the new rules.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/ZzJKLkUHbqw" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/ZzJKLkUHbqw/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/03/articles/bpa/mas-march-madness-2012-final-rule-for-increased-competition-in-masbpa-orders/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">BPA</category><category domain="http://www.governmentcontractslawblog.com/articles">Blanket Purchase Order</category><category domain="http://www.governmentcontractslawblog.com/articles">FSS</category><category domain="http://www.governmentcontractslawblog.com/articles">Federal Supply Schedule</category><category domain="http://www.governmentcontractslawblog.com/articles">GSA Schedule</category><category domain="http://www.governmentcontractslawblog.com/articles">MAS</category><category domain="http://www.governmentcontractslawblog.com/articles">Multiple Award Schedule</category>
         <pubDate>Fri, 16 Mar 2012 08:59:26 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/03/articles/bpa/mas-march-madness-2012-final-rule-for-increased-competition-in-masbpa-orders/</feedburner:origLink></item>
            <item>
         <title>Terrorism and Taxes - Proposed FAR Rule Imposes 2% Tax on Foreign Offers to Fund 9/11 Relief Fund</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David Gallacher &lt;/a&gt;and &lt;a target="_blank" href="http://www.sheppardmullin.com/jbonn"&gt;John Bonn&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;On January 2, 2011, the President signed the James Zadroga 9/11 Health and Compensation Act of 2010, Pub. L. No. 111-347, which set up a relief fund for victims, first responders, and construction workers who were injured in the September 11 terrorist attacks in New York City. To pay the estimated $4.3 billion price tag for the Act, Section 301 of the Act imposed on any foreign person a tax equal to 2% of federal procurement payment received by that foreign person. See 26 U.S.C. &amp;sect; 5000C. In addition, any person who makes or otherwise is a withholding agent with respect to such a payment is required to withhold the 2% tax from the federal procurement payment and remit the tax withheld to the Internal Revenue Service (&amp;ldquo;IRS&amp;rdquo;) under tax laws and regulations applicable to withholding of United States taxes from payments made to foreign persons. Although the tax has been in place for more than 14 months and the IRS has issued a revised Form 1042 with revised instructions to implement withholding and reporting obligations, the Government is only now turning to the details of how this tax will be accounted for in connection with the procurement process. And &amp;ndash; as is often the case &amp;ndash; there is quite a lot of devil in those details.&lt;/p&gt;&lt;p&gt;A proposed Federal Acquisition Regulation was issued on February 22, 2012 stating that the 2% tax cannot be recovered by foreign offerors on any new flexibly-priced or fixed-price contracts.&lt;em&gt; See 77&lt;/em&gt; Fed. Reg. 10461. Exactly how this will play out in the world of government contracting remains to be seen, but foreign companies should be aware of how this new tax may impact their bottom line, and U.S. companies should be aware of the IRS withholding and reporting requirements imposed by the Act with respect to the 2% tax. Companies should pay particular attention to the following points:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Be aware that &amp;quot;foreign person&amp;quot; does not necessarily mean the same thing under the tax code as it does under the procurement or export laws. As such, companies could be subject to this tax even if they are organized under U.S. law.&lt;/li&gt;
    &lt;li&gt;This tax poses significant risks for withholding agents, who are required under tax laws to withhold certain taxes owed by foreign persons. If the foreign person fails to pay the tax, the withholding agent could be on the hook for the tax liability.&lt;/li&gt;
    &lt;li&gt;Determining what payments this tax applies to will be a nightmare because it could apply to a host of different persons and products in a host of different circumstances, none of which are clearly spelled out in the statute, the IRS guidance, or the proposed acquisition rules. Consider that the statute imposes the tax on &lt;em&gt;certain&lt;/em&gt; specified Federal procurement payments, which are made to &lt;em&gt;certain&lt;/em&gt; foreign persons, for the purchase of &lt;em&gt;certain&lt;/em&gt; foreign-made products or foreign-performed services, with the tax being applied consistent with &lt;em&gt;certain&lt;/em&gt; international agreements (including, presumably, free trade agreements and international tax treaties). It will be difficult for a company to craft a &amp;quot;one size fits all&amp;quot; solution to identify taxable transactions and to ensure that the tax is withheld and paid appropriately.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Good advice here would be &lt;strong&gt;&amp;quot;Consult your tax counsel,&amp;quot;&lt;/strong&gt; particularly for those government contractors who are most likely to be dealing with taxable &amp;quot;specified Federal procurement payments&amp;quot; in the regular course of business.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/yvJDUM0AI34" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/yvJDUM0AI34/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/03/articles/compliance/terrorism-and-taxes-proposed-far-rule-imposes-2-tax-on-foreign-offers-to-fund-911-relief-fund/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Compliance</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Accounting</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Corner</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Principles</category><category domain="http://www.governmentcontractslawblog.com/articles">Country of Origin</category><category domain="http://www.governmentcontractslawblog.com/articles">Domestic Preferences</category><category domain="http://www.governmentcontractslawblog.com/articles">Fixed Price</category><category domain="http://www.governmentcontractslawblog.com/articles">Foreign Investment</category><category domain="http://www.governmentcontractslawblog.com/articles">International Contracts</category><category domain="http://www.governmentcontractslawblog.com/articles">International Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">Pricing</category><category domain="http://www.governmentcontractslawblog.com/articles">Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">Proposed Regulations</category><category domain="http://www.governmentcontractslawblog.com/articles">Proposed Rules</category><category domain="http://www.governmentcontractslawblog.com/articles">Tax</category><category domain="http://www.governmentcontractslawblog.com/articles">WTO GPA</category>
         <pubDate>Fri, 16 Mar 2012 08:58:01 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/03/articles/compliance/terrorism-and-taxes-proposed-far-rule-imposes-2-tax-on-foreign-offers-to-fund-911-relief-fund/</feedburner:origLink></item>
            <item>
         <title>The DoD IG Has Moved</title>
         <description>&lt;p&gt;The Office of the Inspector General of the Department of Defense recently changed its mailing address. Unfortunately, some contractors have failed to notice the change, and have used the old address in attempting to submit their disclosure letters. Unfortunately, these disclosures were returned to sender. The new address(es) are below, and detailed information can be found &lt;a target="_blank" href="http://www.dodig.mil/Inspections/IPO/voldis.htm"&gt;here&lt;/a&gt;. For further information regarding the mandatory disclosure rule, please see our &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/02/articles/ethics/aba-publishes-guide-to-mandatory-disclosure-rule/"&gt;previous posting&lt;/a&gt; on the ABA&amp;rsquo;s Guide to the Mandatory Disclosure Rule or &lt;a target="_blank" href="http://www.sheppardmullin.com/assets/attachments/637.pdf"&gt;an article&lt;/a&gt; authored by two of our government contracts partners, Louis D. Victorino and John W. Chierichella, republished with permission from &lt;em&gt;The Government Contractor&lt;/em&gt;.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Mailing address:&lt;/p&gt;
&lt;p&gt;Office of Inspector General of the Department of Defense&lt;br /&gt;
Investigative Policy and Oversight &lt;br /&gt;
Contractor Disclosure Program &lt;br /&gt;
4800 Mark Center Drive, Suite 11H25 &lt;br /&gt;
Alexandria, VA 22350-1500&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For FedEx and UPS packages use the following address:&lt;/p&gt;
&lt;p&gt;Department of Defense Office of Inspector General &lt;br /&gt;
ATTN: ALSD/PMD Podium Warehouse - HL-02 &lt;br /&gt;
SA Frances Lynn McCormick &lt;br /&gt;
Investigative Policy and Oversight Suite 11H25 &lt;br /&gt;
4800 Mark Center Drive &lt;br /&gt;
Alexandria, VA 22311&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/paW6v3lndKA" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/paW6v3lndKA/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/03/articles/mandatory-disclosure-rule/the-dod-ig-has-moved/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Mandatory Disclosure Rule</category><category domain="http://www.governmentcontractslawblog.com/articles">Office of Inspector General</category>
         <pubDate>Fri, 16 Mar 2012 08:57:37 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/03/articles/mandatory-disclosure-rule/the-dod-ig-has-moved/</feedburner:origLink></item>
            <item>
         <title>The 8(a) Mentor Protégé Program: Opportunities for Large and Small Businesses</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/koneill"&gt;Kerry O&amp;rsquo;Neill&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Under the Small Business Administration&amp;rsquo;s (&amp;ldquo;SBA&amp;rdquo;) 8(a) Mentor-Prot&amp;eacute;g&amp;eacute; program, large businesses provide various forms of business development assistance to small businesses participants, including, for example, technical and/or management assistance, financial assistance, and assistance in performing prime contracts. The program, whose governing regulations are set out in 13 C.F.R. Part 124, offers substantial opportunities for large businesses to participate in performance of federal government contracts through partnering with 8(a) program participants on a variety of contractual arrangements, including set-aside procurements, subcontracts, and prime contracts.&lt;/p&gt;&lt;p&gt;&lt;u&gt;&lt;strong&gt;Mentors and Prot&amp;eacute;g&amp;eacute;s: How to Qualify&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Any business or non-profit entity that &amp;ldquo;demonstrates a commitment and ability to assist developing 8(a) Participants&amp;rdquo; may act as a mentor.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;To be a mentor, a business must demonstrate that it 1) possesses favorable financial health; 2) possesses good character; 3) does not appear on the Federal list of debarred or suspended contractors; and 4) can impart value to a prot&amp;eacute;g&amp;eacute; firm. Mentors must submit copies of financial statements to the SBA. A mentor may have more than one prot&amp;eacute;g&amp;eacute; at a time under certain circumstances, subject to approval by the Associate Administrator for 8(a) Business Development (&amp;ldquo;AA/BD&amp;rdquo;).&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;To qualify as a prot&amp;eacute;g&amp;eacute;, a small firm must 1) be in the developmental stage of program participation; or 2) have never received an 8(a) contract; or 3) have a size that is less than half the size standard corresponding to its primary NAICS code.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;u&gt;&lt;strong&gt;Benefits&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Two firms approved by the SBA to be a mentor and prot&amp;eacute;g&amp;eacute; under &amp;sect;124.520 may joint venture as a small business for &lt;em&gt;any&lt;/em&gt; Federal government prime contract or subcontract, including but not limited to 8(a) set asides, provided the prot&amp;eacute;g&amp;eacute; qualifies as small for the size standard corresponding to the NAICS code assigned to the procurement.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;SBA must approve the mentor-prot&amp;eacute;g&amp;eacute; (&amp;ldquo;MP&amp;rdquo;) agreement before the two firms may submit an offer as a joint venture, in order to receive the exclusion from affiliation. Additionally, in order to receive the exclusion for both 8(a) and non-8(a) procurements, the joint venture must meet the requirements set forth in &amp;sect;124.513(c). If all requirements are met, no determination of affiliation or control may be found between a prot&amp;eacute;g&amp;eacute; firm and its mentor.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;The MP written agreement must provide a detailed description of the prot&amp;eacute;g&amp;eacute;&amp;rsquo;s needs, and a timeline for delivery of assistance the mentor commits to provide to address those needs. The mentor must commit to provide such assistance for at least one year, among other requirements. The agreement must be approved by the SBA. It will not be approved if the SBA determines that the assistance to be provided is not sufficient to promote any real developmental gains for the prot&amp;eacute;g&amp;eacute;, or if SBA determines that the agreement is merely a vehicle to enable the mentor to receive 8(a) contracts. SBA will review the MP relationship annually for compliance.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;The prot&amp;eacute;g&amp;eacute; must report on all assistance provided by the mentor annually, and must describe in detail all federal contracts awarded to the MP joint venture. Additionally, after contract performance is complete, the prot&amp;eacute;g&amp;eacute; must submit a report to its servicing SBA district office explaining how the applicable performance requirements were met.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;u&gt;&lt;strong&gt;Performance Requirements&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;For any 8(a) contract, or a non-8(a) contract for which the MP joint venture seeks an exclusion from affiliation, the MP joint venture must perform the applicable percentage of work required by &amp;sect;124.510 and &amp;sect;124.513(d). The MP joint venture entity must perform at least 51% of the work of the total contract. The prot&amp;eacute;g&amp;eacute; must perform at least 40% of the work done by the joint venture partners in the aggregate. The prot&amp;eacute;g&amp;eacute; must receive profits commensurate with the work performed by the prot&amp;eacute;g&amp;eacute;. The work performed by the prot&amp;eacute;g&amp;eacute; must be more than administrative or ministerial functions so that the prot&amp;eacute;g&amp;eacute; gains substantive experience.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;A mentor, or any of its affiliates, may not act as a subcontractor (at any subcontracting tier) to the MP joint venture. The purpose of this rule is to prevent would-be mentors from indirectly increasing the work they perform under the contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;u&gt;&lt;strong&gt;Consequences&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Should the SBA determine that a mentor has not provided to the prot&amp;eacute;g&amp;eacute; firm the assistance set forth in the MP agreement, SBA will terminate the MP agreement, in which case the firm will be ineligible to act as a mentor for a period of two years. Additionally, SBA has the discretion to recommend to the relevant procuring agency to issue a stop work order for each federal contract for which the mentor and prot&amp;eacute;g&amp;eacute; are performing as a small business joint venture. SBA may also initiate debarment proceedings against the mentor on various grounds, including, but not limited to, the mentor&amp;rsquo;s failure to comply with the terms of a public agreement under 2 C.F.R. &amp;sect;180.800(b).&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/ddEnpeWTAas" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/ddEnpeWTAas/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/the-8a-mentor-protaga-program-opportunities-for-large-and-small-businesses/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">Compliance</category><category domain="http://www.governmentcontractslawblog.com/articles">Joint Venture</category><category domain="http://www.governmentcontractslawblog.com/articles">SBA</category><category domain="http://www.governmentcontractslawblog.com/articles">Set-Aside</category><category domain="http://www.governmentcontractslawblog.com/articles">Small Business</category>
         <pubDate>Mon, 13 Feb 2012 12:20:10 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/the-8a-mentor-protaga-program-opportunities-for-large-and-small-businesses/</feedburner:origLink></item>
            <item>
         <title>Penalties for Expressly Unallowable Costs - The ASBCA Reconsiders and Ups the Ante for Contractors</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/jchierichella"&gt;John W. Chierichella&lt;/a&gt;&amp;nbsp;and &lt;a target="_blank" href="http://www.sheppardmullin.com/amajor"&gt;Alexander W. Major&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Under FAR 42.709-1, penalties for expressly unallowable costs are to be waived when the expressly &amp;ldquo;unallowable costs under this proposal&amp;rdquo; are less than $10,000. Although there are other bases for the waiver of the penalties, those other bases are discretionary. The $10,000 exclusion is mandatory.&lt;/p&gt;&lt;p&gt;In &lt;em&gt;Thomas Assoc., Inc&lt;/em&gt;., ASBCA No. 57126, May 17, 2011, 11-1 BCA &amp;para; 34,764, the ASBCA considered an appeal from the imposition of penalties for five expressly unallowable &amp;ldquo;cost items&amp;rdquo;. One item involved costs of $44,959, which was in excess of the $10,000 exclusion and thus ineligible for the mandatory waiver. Each of the other four cost items involved costs of less than $10,000. Although the total expressly unallowable costs included in the indirect cost proposal exceeded $10,000, the Board considered the four cost items individually and held that the Contracting Officer was required to waive the penalty for each of the expressly unallowable cost items that was less than $10,000.&lt;/p&gt;
&lt;p&gt;Not for long.&lt;/p&gt;
&lt;p&gt;The Government moved for reconsideration of the Board's decision and introduced on reconsideration, for the first time, the FAR/DFARS case file relating to the drafting of FAR 42.709-5. Relying on that newly adduced administrative history, to which the Appellant did not object, the Board concluded that waiver applies only when the expressly unallowable costs, &lt;u&gt;in the aggregate&lt;/u&gt;, are less than $10,000. &lt;em&gt;Thomas Assoc., Inc&lt;/em&gt;., ASBCA No. 57126, Oct 18, 2011, 11-2 BCA &amp;para; 34,858. The Board was persuaded by the drafting history, which specifically addressed the issue and added to the final rule parenthetical language linking the waiver to expressly unallowable costs of $10,000 or less allocable to the contracts in question. The Board noted that FAR 42.709-1, which establishes the basic penalty rule, speaks in the singular to any &amp;ldquo;indirect cost&amp;rdquo; that is expressly unallowable. By contrast, FAR 42.709-5, which establishes the waiver, speaks in the plural, dispensing with the penalty when &amp;ldquo;the amount of the unallowable costs under the proposal . . . is $10,000 or less.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The result of the Board&amp;rsquo;s decision on reconsideration is obvious &amp;ndash; &amp;ldquo;little things mean a lot.&amp;rdquo; A few relatively minor inadvertent errors can and will trigger penalties. Moreover, the penalties attach to the submission of the final indirect cost proposal unless the proposal is withdrawn before the initiation of the proposal audit, even if Uncle Sam never pays the costs. Contractors apparently will no longer be able to count on a &amp;ldquo;free pass&amp;rdquo; for individual cost errors at or below the $10,000 threshold if, in the aggregate, they exceed that threshold. The cost of minor mistakes just went up. &lt;em&gt;Caveat venditor&lt;/em&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/WAZ7r33js-U" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/WAZ7r33js-U/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/penalties-for-expressly-unallowable-costs-the-asbca-reconsiders-and-ups-the-ante-for-contractors/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">Cost Corner</category><category domain="http://www.governmentcontractslawblog.com/articles">Indirect Costs</category><category domain="http://www.governmentcontractslawblog.com/articles">Penalties</category><category domain="http://www.governmentcontractslawblog.com/articles">Waivers</category>
         <pubDate>Mon, 13 Feb 2012 12:10:45 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/penalties-for-expressly-unallowable-costs-the-asbca-reconsiders-and-ups-the-ante-for-contractors/</feedburner:origLink></item>
            <item>
         <title>Fisher v. Halliburton: Fifth Circuit Invokes Common Sense To Defend Defense Base Act</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/amajor"&gt;Alex Major &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In March 2010, a federal district court in Texas ruled that the deaths and injuries sustained by a group of civilian convoy drivers in Iraq during insurgent attacks were not &amp;ldquo;accidents&amp;rdquo; caused by conditions of their employment and were, therefore, outside the scope of the protections afforded to contractors by the Defense Base Act (&amp;ldquo;DBA&amp;rdquo;). 42 U.S.C. &amp;sect; 1651, &lt;em&gt;et seq. Fisher v. Halliburton&lt;/em&gt;, 703 F. Supp. 2d. 639 (S.D. Tex. 2010). We previously described and criticized the district court decision in this blog, noting that it was now unclear how, exactly, the DBA would fare in future &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/06/articles/defense-base-act/united-states-district-court-for-the-southern-district-of-texas-deprives-battlefield-contractors-of-the-protections-of-the-defense-base-act/"&gt;litigation&lt;/a&gt;. But on January 12, 2012, the Fifth Circuit restored clarity&amp;mdash; and common sense&amp;mdash;to the application of the DBA by recognizing that the facts in &lt;em&gt;Fisher&lt;/em&gt; presented &amp;ldquo;the quintessential case of a compensable injury arising from a third party&amp;rsquo;s assault&amp;rdquo;. Holding the DBA to be the exclusive remedy for damages, the Fifth Circuit vacated the district court&amp;rsquo;s decision and remanded the case for further proceedings. &lt;em&gt;Fisher v. Halliburton&lt;/em&gt;, 2012 WL 90136 (5th Cir. 2012).&lt;/p&gt;&lt;p&gt;The Fifth Circuit efficiently disposed of the district court&amp;rsquo;s decision, beginning with a determination that the third party, i.e., insurgent, acts were directed against Plaintiffs &amp;ldquo;because of [their] employment.&amp;rdquo; Forcefully disagreeing with the district court&amp;rsquo;s conclusion that the employees were targeted for simply being Americans and not because they were providing logistical support to the U.S. Military, the court cautioned that such reasoning threatened the applicability of the DBA &amp;ldquo;on foreign soil&amp;rdquo; or to &amp;ldquo;those that support a war.&amp;rdquo; Moreover, the court stated, if the reasoning of the district court were sustained, then &amp;ldquo;[t]he argument could always be asserted that an employee was killed or injured not because of her employment, but because she was an American.&amp;rdquo; Accordingly, the circuit court found it to be &amp;ldquo;self evident&amp;rdquo; and &amp;ldquo;a matter of common sense that when insurgent forces in Iraq attack an Army-led fuel supply convoy, the insurgents are attacking the convoy because of its role in supporting the Army&amp;rsquo;s operations in that country.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The Fifth Circuit then disposed of another argument raised by Plaintiffs in &lt;em&gt;Fisher, i.e&lt;/em&gt;., that the Plaintiffs&amp;rsquo; injuries were caused by the defendant-contractor, who, they alleged, committed an intentional tort by failing to act to protect Plaintiffs from &amp;ldquo;substantially certain&amp;rdquo; injury at the hands of the insurgents. This argument, premised on intelligence reports and open-source news reports, reasoned that the defendant knew that the assaults would occur and did nothing to stop the convoys from moving forward. While recognizing that the &amp;ldquo;intentional tort exception&amp;rdquo; has not been applied in the Fifth Circuit to the either the DBA or the Longshore and Harbor Workers' Compensation Act (&amp;ldquo;LHWCA&amp;rdquo;), upon which the DBA is based, the court noted that, when applying this exception, other courts &amp;ldquo;consistently require that the employer have had a specific intent or desire that the injury occur&amp;rdquo; and that neither circumstance existed here. Moreover, the circuit court reiterated the purpose of the DBA and concluded that its &amp;ldquo;provisions admit of no exception for cases in which an employee claims his employer was &amp;lsquo;substantially certain&amp;rsquo; that the employee would be assaulted by a third party because of his employment.&amp;rdquo; The circuit court essentially recognized the difficulty in applying a &amp;ldquo;substantially certain&amp;rdquo; exception premised on purportedly informed conjecture derived from military intelligence and open-source news. To allow a &amp;ldquo;substantially certain&amp;rdquo; exception would undercut the very purpose of the DBA of &amp;ldquo;providing prompt relief for employees, and limited and predictable liability for employers.&amp;rdquo; Therefore, the court concluded, coverage under the DBA precludes an employee from recovery from its employer &amp;ldquo;under a &amp;lsquo;substantially certain&amp;rsquo; theory of intentional-tort liability.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Finally, the Fifth Circuit did agree with the district court that the DBA prevents an employee from bringing a fraud claim to recover damages for a DBA-covered injury. Echoing the sentiment of the lower court, the circuit court held that any deceit proven against the employer that led to the compensable injury &amp;ldquo;merges into that injury for purposes of compensation coverage.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;In his book recounting his leadership of the American Expeditionary Forces in World War I, &lt;u&gt;My Experiences in the World War&lt;/u&gt;, General John Pershing reflected that &amp;ldquo;military science is based on principles that have been deduced from the application of common sense in the conduct of military affairs.&amp;rdquo; The Fifth Circuit&amp;rsquo;s defense of the DBA in vacating and remanding the lower court&amp;rsquo;s ruling in &lt;em&gt;Fisher v. Halliburton&lt;/em&gt;, recognizes that the same application of common sense should be brought to bear in the application of U.S. law in the battlespace.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/sf2uicpObkE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/sf2uicpObkE/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/fisher-v-halliburton-fifth-circuit-invokes-common-sense-to-defend-defense-base-act/</guid>
         <category domain="http://www.governmentcontractslawblog.com/articles">Appeals</category><category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">Civil Litigation</category><category domain="http://www.governmentcontractslawblog.com/articles">Defense Base Act</category>
         <pubDate>Mon, 13 Feb 2012 12:05:35 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/fisher-v-halliburton-fifth-circuit-invokes-common-sense-to-defend-defense-base-act/</feedburner:origLink></item>
            <item>
         <title>Mandatory Debarment for FCPA Violations? A Bad Idea Whose Time Should Never Come</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/memmick"&gt;Mike Emmick&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In the fervor of the U.S.'s current anti-foreign-corruption efforts, a particularly misguided proposal has occasionally reared its ugly head: Requiring &amp;ldquo;mandatory debarment&amp;rdquo; for any company that violates the Foreign Corrupt Practices Act (&amp;ldquo;FCPA&amp;rdquo;).&lt;/p&gt;
&lt;p&gt;On the merits, such a proposal is completely wrong-headed. Debarment is a severe, forward-looking administrative remedy &amp;ndash; the corporate &amp;ldquo;death penalty&amp;rdquo; &amp;ndash; not a vehicle to &amp;ldquo;boost&amp;rdquo; the penalties for past criminal FCPA violations.&lt;/p&gt;&lt;p&gt;Nonetheless, in 2010, such a &amp;ldquo;mandatory debarment&amp;rdquo; bill was passed by the House, only to die in Congress due to Senate inaction. Optimistic multinational contractors might therefore have concluded, &amp;ldquo;Whew, we dodged that bullet.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;However, a recent law-review article has sought to resurrect the debarment idea, contending that no other remedy will deter large global companies from violating the FCPA.&lt;/p&gt;
&lt;p&gt;Below is a snapshot of the relevant law, recent developments, and pertinent arguments. As will be explained, despite the recent article, the notion of &amp;ldquo;mandatory debarment&amp;rdquo; is unlikely to gain traction &amp;ndash; even the Department of Justice (&amp;ldquo;DOJ&amp;rdquo;) opposes it &amp;ndash; but the article and the current anti-corruption frenzy may cause authorities to reconsider the idea. Any multinational company that does substantial government contract work should therefore monitor and resist such efforts.&lt;/p&gt;
&lt;p&gt;As nearly everyone who operates in this market knows by this time, the FCPA prohibits U.S. companies from paying bribes to foreign officials in order to obtain or retain business. The FCPA also requires accurate books and records and meaningful internal accounting controls. Violations of the FCPA can result in huge criminal and civil fines, disgorgement of profits, and payment of interest, not to mention a wide range of collateral consequences. The FCPA is enforced by DOJ and the SEC.&lt;/p&gt;
&lt;p&gt;Over the past five years DOJ has been extremely aggressive in its prosecution of FCPA violations. Eight of the ten largest FCPA fines in history occurred in 2010, and multi-million-dollar fines have now become routine. There are currently dozens of pending FCPA investigations &amp;ndash; many more than in previous years. Indeed, DOJ has dubbed this &amp;ldquo;the new era of FCPA enforcement.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Congress attempted to climb aboard this FCPA-enforcement bandwagon when, on September 15, 2010, the House unanimously passed a &amp;ldquo;mandatory debarment&amp;rdquo; bill &amp;ndash; H.R. 5366, known as the 2010 Overseas Contractor Reform Act. The bill would have created a government-wide policy that no contracts be awarded to companies or individuals that violated the FCPA. H.R. 5366, &amp;sect; 3. Procedurally, the law would have required the contracting agency to propose for debarment all contractors found to be in violation of the FCPA.&lt;/p&gt;
&lt;p&gt;The bill was flawed in many ways. It did not define a &amp;ldquo;finding&amp;rdquo; of an FCPA violation, so it was unclear whether the debarment would be triggered by a non-prosecution or deferred prosecution agreement. The bill failed to differentiate between major and minor FCPA violations, or between different kinds of violations (i.e., bribe payments versus &amp;ldquo;books and records&amp;rdquo; or accounting violations). The bill did not require or permit consideration of how the violation occurred, whether the company self-reported the violation, or whether the company dramatically improved its anti-corruption compliance program thereafter.&lt;/p&gt;
&lt;p&gt;Shortly after the bill was passed, DOJ answered questions about the FCPA generally, as the Chamber of Commerce was proposing FCPA amendments. DOJ expressed its opposition to &amp;ldquo;mandatory debarment,&amp;rdquo; stating that mandatory debarment &amp;ldquo;would likely be counterproductive, as it would reduce the number of voluntary disclosures and concomitantly limit corporate remediation and the implementation of enhanced compliance programs.&amp;rdquo; According to DOJ, such a debarment program could also hurt the government's ability to investigate and prosecute transnational corruption. Linking debarment to criminal conviction would &amp;ldquo;fundamentally alter the incentives of a contractor-company,&amp;rdquo; because an FCPA resolution would then cause the company to suffer a dramatic reduction in revenue. That, in turn, would negatively impact prosecutorial discretion and the flexibility to reach an appropriate resolution given the facts and circumstances of the particular case.&lt;/p&gt;
&lt;p&gt;DOJ's opposition would ordinarily be enough to ensure that &amp;ldquo;mandatory debarment&amp;rdquo; would not be taken seriously. And in fact the Senate took no further action on the House bill, perhaps because of DOJ's opposition after the House bill was passed.&lt;/p&gt;
&lt;p&gt;However, a recent law-review article has sought to resurrect this misguided debarment notion. In November 2011, Fordham Law Review published a 70-page article entitled &amp;ldquo;FCPA Sanctions: Too Big to Debar,&amp;rdquo; available &lt;a target="_blank" href="http://ir.lawnet.fordham.edu/cgi/viewcontent.cgi?article=4671&amp;amp;context=flr"&gt;here&lt;/a&gt;, which was written by Professor Drury Stevenson of the South Texas College of Law, along with one his law students. The article took the position that debarment should be considered as an additional punishment for FCPA violations. According to the article, corporations can only be punished via fines, and government contract revenues are so large that fines often become a mere &amp;ldquo;cost of doing business,&amp;rdquo; which prevents those fines from having deterrent value. In addition, the public may interpret a failure to debar a company as suggesting that companies can buy their way out of FCPA violations.&lt;/p&gt;
&lt;p&gt;The article acknowledged that mandatory debarment might discourage self-disclosure &amp;ndash; one of DOJ's concerns &amp;ndash; but proposed that self disclosure might be meaningfully rewarded through a reduced criminal fine. The article also acknowledged that debarment might be the contractor's &amp;ldquo;death knell&amp;rdquo;; it might even raise an &amp;ldquo;Arthur Andersen&amp;rdquo; problem by driving an important and responsible company out of business entirely, which might harm the contracting market, foreign relations, national security, and the company's shareholders. As an alternative to mandatory debarment, the article proposed an increase in discretionary debarments based on FCPA violations.&lt;/p&gt;
&lt;p&gt;For a number of reasons, &amp;ldquo;mandatory debarment&amp;rdquo; for FCPA violations is a bad idea. In fact, In January 2012, two months after &amp;ldquo;Too Big to Debar&amp;rdquo; was published, Fordham Law Review published a responsive article authored by Jessica Tillipman, a professor at George Washington Law School. Jessica Tillipman, &amp;ldquo;A House of Cards Falls: Why &amp;ldquo;Too Big to Debar&amp;rdquo; is All Slogan and Little Substance&amp;rdquo;, available &lt;a target="_blank" href="http://ir.lawnet.fordham.edu/cgi/viewcontent.cgi?article=1007&amp;amp;context=res_gestae"&gt;here&lt;/a&gt;. Tillipman disagreed with nearly all of Professor Stevenson's conclusions and analysis, and her remarks warrant summarizing here.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;First&lt;/u&gt;, the debarment provision in the Federal Acquisition Regulations (FAR) is itself inconsistent with &amp;ldquo;mandatory debarment.&amp;rdquo; FAR 9-402(b) states that &amp;ldquo;the serious nature of debarment and suspension requires that these sanctions be imposed only in the public interest for the Government's protection and &lt;em&gt;not for purposes of punishment&lt;/em&gt;.&amp;rdquo; (Emphasis added.) The point of debarment is to ensure that the government works with &amp;ldquo;responsible partners.&amp;rdquo; Indeed, that is why the prosecutors handle the fines, and the debarring officials handle the debarment.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Second&lt;/u&gt;, the FAR expressly requires the debarment officials to consider whether the contractor undertook remedial measures or whether the violation involved mitigating factors that demonstrate that the contractor is still &amp;ldquo;presently responsible.&amp;rdquo; FAR 9-406-1. Mandatory debarment would make those provisions meaningless, and would shift the focus of debarment from future conduct to past conduct.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Third&lt;/u&gt;, imposing the remedy of &amp;ldquo;mandatory debarment&amp;rdquo; would unfairly focus on government contractors, not on other companies or individuals that may violate the FCPA. Why should contractors be discriminated against &amp;ndash; especially &lt;em&gt;automatically&lt;/em&gt; discriminated against?&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Fourth&lt;/u&gt;, debarment is an inappropriate &amp;ldquo;all or nothing&amp;rdquo; remedy. Its use might destroy responsible companies &amp;ndash; even essential companies &amp;ndash; that have thousands of employees and contribute immensely to the economies of the U.S. and the world. That is why debarment should be used only rarely, and only after an extensive review of what prompted the transgression, how the company responded, and other important factors.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Fifth&lt;/u&gt;, if mandatory debarment were to become the law, it might even discourage large companies from engaging in business with the U.S., because their devotion of time to and their monetary investments in government contract work could be lost at the whim of federal prosecutors, perhaps as the result of actions by rogue employees who clandestinely refused to adhere to the companies' anti-corruption compliance program.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Finally&lt;/u&gt;, as DOJ itself pointed out in 2010, &amp;ldquo;mandatory debarment&amp;rdquo; might actually hurt the US's FCPA-enforcement efforts by discouraging corporate self-disclosure and cooperation as part of the remediation process. Those procedures are currently a critical source of information for DOJ to use in its prosecution of FCPA violations.&lt;/p&gt;
&lt;p&gt;In light of DOJ's opposition, &amp;ldquo;mandatory debarment&amp;rdquo; for FCPA violations is unlikely ever to become law. Nonetheless, because the consequences would be potentially devastating, any such possibility should be monitored closely by and vigorously opposed by global contractors.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/AtDqQomKCYg" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/AtDqQomKCYg/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/mandatory-debarment-for-fcpa-violations-a-bad-idea-whose-time-should-never-come/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">FCPA</category>
         <pubDate>Mon, 13 Feb 2012 12:00:26 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/mandatory-debarment-for-fcpa-violations-a-bad-idea-whose-time-should-never-come/</feedburner:origLink></item>
            <item>
         <title>"Buy American" and Photovoltaic Devices - Interim Rule Issued by DoD</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David Gallacher&lt;/a&gt; and &lt;a target="_blank" href="http://www.sheppardmullin.com/cdombek"&gt;Curt Dombek&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Last year in January 2011, the President signed the 2011 National Defense Authorization Act (Pub. L. No. 111-383, Section 846), which included a &amp;ldquo;Buy American&amp;rdquo; requirement for photovoltaic devices being purchased by the U.S. Department of Defense (&amp;ldquo;DoD&amp;rdquo;). &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2011/01/articles/baa-and-taa/new-defense-authorization-act-imposes-buy-american-act-mandate-for-photovoltaics/?utm_medium=email&amp;amp;utm_campaign=Government+Contracts+Law+Blog&amp;amp;utm_content=Government+Contracts+Law+Blog+C"&gt;We previously discussed this new requirement in our blog&lt;/a&gt;. Twelve months later, the DoD has issued an interim rule to implement this new requirement. &lt;em&gt;See&lt;/em&gt; 76 Fed. Reg. 18858 (Dec. 20, 2011). The interim rule appears to be straightforward, implementing exceptions and manufacturing requirements with which most companies are already familiar under the Buy American Act or the Trade Agreements Act, but there is some fine print of which all companies selling photovoltaic devices to the DoD should be aware.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Key Definitions&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The interim rule includes a new subsection at Defense Federal Acquisition Regulation Supplement (&amp;ldquo;DFARS&amp;rdquo;) 225.7017, as well as a new contract clause at DFARS 252.225-7017, Photovoltaic Devices, and a corresponding certification requirement at DFARS 252.225-7018. Defining its key concepts, the interim rule largely restates the statutory language from Section 846 by defining &amp;ldquo;covered contracts&amp;rdquo; and &amp;ldquo;photovoltaic device.&amp;rdquo;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&amp;ldquo;&lt;u&gt;Covered contracts&lt;/u&gt;&amp;rdquo; means &amp;ldquo;an energy savings performance contract, a utility service contract, or a private housing contract awarded by DoD, if such contract results in DoD ownership of photovoltaic devices, by means other than DoD purchase as end products. DoD is deemed to own a photovoltaic device if the device is &amp;ndash; (1) Installed on DoD property or in a facility owned by DoD; and (2) Reserved for the exclusive use of DoD for the full economic life of the device.&amp;rdquo; Note that a &amp;ldquo;covered contract&amp;rdquo; will &lt;em&gt;not&lt;/em&gt; include government contracts valued at less than $150,000 (the simplified acquisition threshold).&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;&amp;ldquo;&lt;u&gt;Photovoltaic device&lt;/u&gt;&amp;rdquo; means &amp;ldquo;a device that converts light directly into electricity through a solid-state, semiconductor process.&amp;rdquo; Under this definition, a solar panel containing many individual solar cells would constitute a &amp;ldquo;photovoltaic device.&amp;rdquo; If such a panel were manufactured or assembled in the United States in a manner that constituted a substantial transformation (thus qualifying as a &amp;ldquo;domestic product&amp;rdquo;), the photovoltaic device would appear to qualify under this regulation, just as it would have under prior rules.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Applicable Dollar Thresholds and Products from U.S. Allies&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The interim rule also breaks out the applicable dollar thresholds/categories at which the various free trade agreements apply.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" width="446" height="428" src="http://www.governmentcontractslawblog.com/uploads/image/chart(1).jpg" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There are at least four issues worth noting about the applicable dollar thresholds and lists of approved countries:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;&lt;u&gt;Dollar Thresholds Apply to the Value of Photovoltaic Devices&lt;/u&gt;. The dollar thresholds apply to the value of the photovoltaic devices being purchased as part of the overall contract. As such, if you have a $3 million contract with the DoD but estimate only $100,000 in photovoltaic devices as a part of that overall contract, then it is the $100,000 figure that would determine whether specific trade agreement exceptions apply for the photovoltaic devices.&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;Updated Dollar Thresholds&lt;/u&gt;. &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2012/02/articles/baa-and-taa/new-2012-updates-to-us-free-trade-agreements-expected-no-progress-with-china/"&gt;These dollar thresholds have been updated effective January 1, 2012&lt;/a&gt;, which unfortunately means that the new interim rule is already out of date. While these thresholds will no doubt be reconciled when a final rule is eventually issued, the different thresholds will be confusing in the interim.&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;Qualifying Countries&lt;/u&gt;. The DoD has entered into Memoranda of Understanding with twenty-one U.S. allies whose ministries of defense have agreed that neither the U.S. nor the ally will discriminate against the other in defense procurements. Accordingly, the interim rule acknowledges that purchases at any dollar threshold will satisfy the &amp;ldquo;Buy American&amp;rdquo; requirement where the photovoltaic devices are from a &amp;ldquo;qualifying country,&amp;rdquo; which includes Australia, Austria, Belgium, Canada, Denmark, Egypt, Finland, France, Germany, Greece, Israel, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland, Turkey, and the United Kingdom. Note that even though the U.S. and South Korea have entered into a newly expanded free trade agreement that should be fully implemented in 2012, the free trade agreement does &lt;em&gt;not&lt;/em&gt; include a MOU between the DoD and the South Korean Ministry of National Defense such that South Korea would be included on this list as a &amp;ldquo;qualifying country.&amp;rdquo; However, South Korea remains a signatory to the WTO GPA, and photovoltaic devices from South Korea would satisfy the interim rule when purchases are at or above the $203,000 threshold.&lt;/li&gt;
    &lt;li&gt;&lt;u&gt;U.S.-Oman Free Trade Agreement&lt;/u&gt;. The rule does not include the U.S.-Oman free trade agreement entered into in 2009, &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/uploads/file/asset_upload_file170_8850.pdf"&gt;which does not cover the DoD&lt;/a&gt;. Oman, therefore, is not listed as an &amp;ldquo;approved&amp;rdquo; country under the new DoD photovoltaic rules, even though a product form Oman would otherwise qualify under the Trade Agreements Act when purchased by most civilian agencies.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Other Key Features of the Interim Rule&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;u&gt;Components&lt;/u&gt;. The interim rule reinforces the fact that it is concerned only with the country of origin for the manufactured end-product &amp;ndash; not the components. Where the Buy American Act commonly requires that an end-product be both: (1) manufactured in the U.S.; and (2) consist of more than 50% in domestic component parts, the new photovoltaic &amp;ldquo;Buy American&amp;rdquo; requirement requires only that the manufactured photovoltaic device end-product be manufactured in the U.S. or a qualifying country (or a free trade agreement partner, if applicable). This means that a domestically manufactured photovoltaic device could consist of entirely foreign content, so long as the final end-product was manufactured or substantially transformed in an approved country.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;u&gt;Commercial Products&lt;/u&gt;. The interim rule expressly states that this rule applies to commercial purchases.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;u&gt;Unreasonable Cost Exception Remain Available&lt;/u&gt;. An existing exception under the Buy American Act permits DoD to purchase products from non-approved countries when the cost of a product from an approved country is 50% more than the product from a non-approved country. In this respect, the interim rule does not absolutely require the purchase of domestic photovoltaic devices, but merely establishes a sizeable preference for the purchase of domestic products or other qualifying goods.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It is doubtful whether Section 846 was even necessary in the first place &amp;ndash; after all, the statute merely directed DoD to ensure that the purchases of photovoltaic devices comply with the Buy American Act and the Trade Agreements Act, two statutes that would have applied to DoD purchases even if Section 846 were never passed. Nevertheless, now that the DFARS has been amended with this interim rule, there should be greater clarity for contractors regarding the types of products that will satisfy the new requirement, as well as the specific procedures on how this new &amp;ldquo;Buy American&amp;rdquo; requirement will be implemented (particularly with regard to the valuation of photovoltaic devices being procured as part of a larger government contract). DoD is accepting comments on the interim rule through February 21, 2012.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/ACEONVjOyno" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/ACEONVjOyno/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/buy-american-and-photovoltaic-devices-interim-rule-issued-by-dod/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">BAA and TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">China</category><category domain="http://www.governmentcontractslawblog.com/articles">Country of Origin</category><category domain="http://www.governmentcontractslawblog.com/articles">Domestic Preferences</category><category domain="http://www.governmentcontractslawblog.com/articles">Energy</category><category domain="http://www.governmentcontractslawblog.com/articles">Government Contracts Law</category><category domain="http://www.governmentcontractslawblog.com/articles">Interim Rule</category><category domain="http://www.governmentcontractslawblog.com/articles">International Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">WTO GPA</category>
         <pubDate>Mon, 13 Feb 2012 11:59:48 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/buy-american-and-photovoltaic-devices-interim-rule-issued-by-dod/</feedburner:origLink></item>
            <item>
         <title>New 2012 Updates to U.S. Free Trade Agreements Expected; No Progress With China</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/dgallacher"&gt;David Gallacher&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;2012 will see changes regarding U.S. free trade agreements relating to, first, the dollar thresholds at which the various agreements apply to federal purchases and, second, the likely expansion of the scope of the World Trade Organization Government Procurement Agreement (&amp;quot;WTO GPA&amp;quot;). The updated dollar thresholds are important for government contractors because the thresholds determine when a contract is subject to the Buy American Act (&amp;quot;BAA&amp;quot;) or the Trade Agreements Act (&amp;quot;TAA&amp;quot;). As to the WTO GPA, its expansion should provide significant increased access to the U.S and many of its trading partners in international procurements, although the hoped for accession of China to the WTO GPA remains stalled&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Updated Dollar Thresholds&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;On December 8, 2011, the U.S. Trade Representative (&amp;quot;USTR&amp;quot;), Ronald Kirk, announced the dollar thresholds at which free trade agreements (&amp;quot;FTAs&amp;quot;) will apply to U.S. procurements beginning in 2012. &lt;em&gt;See&lt;/em&gt; 76 Fed. Reg. 76808. The USTR has raised some thresholds, maintained others, and even lowered some:&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" width="444" height="521" src="http://www.governmentcontractslawblog.com/uploads/image/chart3(1).jpg" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/01/articles/baa-and-taa/new-2010-updates-to-buy-american-and-trade-agreements-dollar-thresholds-buy-american-requirements-remain-elusive-and-complicated/"&gt;&lt;br /&gt;
As we discussed previously in this blog when the thresholds were last adjusted in 2010&lt;/a&gt;, it is unclear whether the FAR will need to be amended to incorporate the new thresholds or whether the new thresholds automatically become &amp;quot;effective January 1, 2012&amp;quot; as directed by the USTR. However, on January 30, 2012, the DFARS was amended to incorporate the new dollar thresholds. &lt;em&gt;See&lt;/em&gt; 77 Fed. Reg. 4630. While the FAR Councils are no doubt also working on updating the relevant FAR clauses at FAR Subpart 25.4, any new rules will probably not be issued until February or March 2012. Contractors should be aware that Contracting Officers may take even longer to update individual contracts, or, for that matter, to agree that modifications to existing contracts are appropriate in the first place.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pending Updates to the WTO GPA&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In December 2011, the members of the WTO met in Geneva to revise the WTO GPA. &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2010/04/articles/country-of-origin/recovery-act-and-updates-to-buy-american/"&gt;Ever since Canada and the U.S. negotiated amendments to the U.S.-Canada FTA allowing Canada greater access to procurements by state and local governments&lt;/a&gt; (one of the primary outlets for stimulus funds through 2009 and 2010), members of the WTO have clamored for expanded access under the GPA. FTAs typically apply only to governmental agencies that are specifically listed in the free trade agreement; the new December 2011 agreement allows expanded access by foreign companies to U.S. procurements by listing twelve previously uncovered federal agencies (including the Social Security Administration and the Transportation Security Administration) as now covered by the WTO GPA. In exchange, U.S. companies will gain access to hundreds of foreign &amp;quot;central and sub-central&amp;quot; government procurements in countries such as Japan, South Korea, Israel, and many other E.U. countries. The new WTO agreement is expected to open significant international procurement markets, and the USTR hailed the new agreement as a major breakthrough for free trade. The changes to the WTO GPA are expected to be formalized by March 2012.&lt;/p&gt;
&lt;p&gt;Meanwhile, in November 2011, China updated its submission to accede to the WTO GPA. But the submission fell short of U.S. and E.U. expectations, setting extremely high dollar thresholds and exempting a large number of Chinese sub-central agencies and state-run enterprises. China joined the WTO in 2001 and China has reiterated that it intends to accede to the WTO GPA. However, given the above high dollar thresholds and exemptions, &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/2009/07/articles/baa-and-taa/country-of-origin-made-in-taiwan-will-soon-be-taa-compliant-china-continues-to-dawdle-costa-rica-peru-and-oman-also-recognized/"&gt;China has thus far&amp;nbsp;been unable to make the kind of aggressive offers demanded by the international community&lt;/a&gt; to complete its accession. Therefore, at least for the time being, products made in China will continue to be noncompliant under the Trade Agreements Act.&lt;/p&gt;
&lt;p&gt;Current signatories to the WTO GPA include more than 40 countries: the U.S., the 27 member states of the European Union, Canada, Armenia, Aruba, Hong Kong, Iceland, Israel, Japan, Liechtenstein, Norway, Singapore, South Korea, Switzerland, and Taiwan. Armenia is the most recent addition to the WTO GPA, having just recently acceded to the WTO GPA on September 15, 2011. &lt;em&gt;See&lt;/em&gt; 76 Fed. Reg. 58856; 77 Fed. Reg. 4631.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/ipJvGfNCjs0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/ipJvGfNCjs0/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/baa-and-taa/new-2012-updates-to-us-free-trade-agreements-expected-no-progress-with-china/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">BAA and TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">China</category><category domain="http://www.governmentcontractslawblog.com/articles">Construction</category><category domain="http://www.governmentcontractslawblog.com/articles">Country of Origin</category><category domain="http://www.governmentcontractslawblog.com/articles">Domestic Preferences</category><category domain="http://www.governmentcontractslawblog.com/articles">Government Contracts Law</category><category domain="http://www.governmentcontractslawblog.com/articles">International Procurement</category><category domain="http://www.governmentcontractslawblog.com/articles">Recovery Act</category><category domain="http://www.governmentcontractslawblog.com/articles">Stimulus</category><category domain="http://www.governmentcontractslawblog.com/articles">TAA</category><category domain="http://www.governmentcontractslawblog.com/articles">WTO GPA</category>
         <pubDate>Mon, 13 Feb 2012 11:58:53 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/baa-and-taa/new-2012-updates-to-us-free-trade-agreements-expected-no-progress-with-china/</feedburner:origLink></item>
            <item>
         <title>No Stone Unturned--Mitigating Risk In A Government Contracts Due Diligence</title>
         <description>&lt;p&gt;By &lt;a target="_blank" href="http://www.sheppardmullin.com/mkipa"&gt;Marko W. Kipa&lt;/a&gt;, &lt;a target="_blank" href="http://www.sheppardmullin.com/aperry"&gt;Anne B. Perry&lt;/a&gt;, and &lt;a target="_blank" href="http://www.sheppardmullin.com/lsalvi"&gt;Lucantonio N. Salvi&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;An acquisition transaction involving a government contractor brings with it a unique set of rules and regulations. There is no shortage of frequently changing and complex requirements regulating a government contractor&amp;rsquo;s operations, and a firm grasp of these requirements is crucial both to arriving at a proper valuation of a target company and to understanding the risks associated with the transaction.&lt;/p&gt;&lt;p&gt;Three of our Government Contracts lawyers &amp;ndash; Marko W. Kipa, Anne B. Perry, and Lucantonio N. Salvi &amp;ndash; recently published an article that assists buyers and sellers in identifying the most common risk areas in an acquisition transaction involving a government contractor. With permission of The Government Contractor, the article is reproduced in full in this issue of our blog.&lt;/p&gt;
&lt;p&gt;Click &lt;a target="_blank" href="http://www.governmentcontractslawblog.com/uploads/file/Government Contractor Article.pdf"&gt;here&lt;/a&gt; to view a PDF copy of the article.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/GovernmentContractsBlog/~4/238OcOKCGm0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/GovernmentContractsBlog/~3/238OcOKCGm0/</link>
         <guid isPermaLink="false">http://www.governmentcontractslawblog.com/2012/02/articles/mergers-and-acquisitions/no-stone-unturnedmitigating-risk-in-a-government-contracts-due-diligence/</guid>
         <category domain="http://www.governmentcontractslawblog.com/">Articles</category><category domain="http://www.governmentcontractslawblog.com/articles">Mergers and Acquisitions</category>
         <pubDate>Mon, 13 Feb 2012 11:57:33 -0800</pubDate>
         <dc:creator>Sheppard Mullin</dc:creator>
      
      <feedburner:origLink>http://www.governmentcontractslawblog.com/2012/02/articles/mergers-and-acquisitions/no-stone-unturnedmitigating-risk-in-a-government-contracts-due-diligence/</feedburner:origLink></item>
      
   </channel>
</rss>

