<?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.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Cyrus E. Phillips IV</title>
	
	<link>http://www.procurement-lawyer.com</link>
	<description>Attorney-at-Law</description>
	<lastBuildDate>Mon, 01 Mar 2010 19:50:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CyrusEPhillipsIv" /><feedburner:info uri="cyrusephillipsiv" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>The Federal Circuit Validates the Implied-in-Fact Contract Theory of Protest Jurisdiction</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/e9DN3c4mmCI/</link>
		<comments>http://www.procurement-lawyer.com/2010/03/the-federal-circuit-validates-the-implied-in-fact-contract-theory-of-protest-jurisdiction/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 19:50:45 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Procurement Law]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=289</guid>
		<description><![CDATA[The Federal Circuit has resolved a quandary about the implied-in-fact contract theory of protest jurisdiction, this in Resource Conservation Group, LLC v. United States, Fed. Cir. No. 2009-5091, March 1, 2010. Resource Conservation Group arises out of a Claim for bid preparation costs and fees filed after the Navy rejected an Offer to lease the [...]]]></description>
			<content:encoded><![CDATA[<p>The Federal Circuit has resolved a quandary about the implied-in-fact contract theory of protest jurisdiction, this in <a href="http://www.cafc.uscourts.gov/opinions/09-5091.pdf">Resource Conservation Group, LLC v. United States</a>, Fed. Cir. No. 2009-5091, March 1, 2010. <i>Resource Conservation Group</i> arises out of a Claim for bid preparation costs and fees filed after the Navy rejected an Offer to lease the former Naval Academy dairy farm in Gambrills, Maryland.</p>
<p>The Navy knew that one of the Offerors was planning to mine the property for sand and gravel, but did not tell that Offeror that the Navy had concluded that such mining was tantamount to sale of the dairy farm, rather than a lease—and the authorizing statute, <a href="http://www2.law.cornell.edu/uscode/html/uscode10/usc_sec_10_00006976----000-.html">10 U.S.C. § 6976(a)(2)</a>, did not allow sale of the property. The Offeror incurred substantial bid preparation costs and fees before the Navy told the Offeror that its Offer could not be considered.</p>
<p>The quandary results from two possible sources of protest jurisdiction for the United States Court of Federal Claims: <a href="http://www4.law.cornell.edu/uscode/28/1491.html">28 U.S.C. § 1491(a)(1)</a>, which gives the Court jurisdiction “to render judgment upon any claim against the United States . . . founded upon any express or implied contract with the United States”; and <a href="http://www4.law.cornell.edu/uscode/28/1491.html">28 U.S.C. § 1491(b)(1)</a>, which gives the Court jurisdiction: </p>
<p>to render judgment on an action by an interested party objecting to a solicitation by a Federal agency for bids or proposals for a proposed contract or to a proposed award or the award of a contract or any alleged violation of statute or regulation in connection with a procurement or a proposed procurement.</p>
<p>28 U.S.C. § 1491(a)(1), a part of the Tucker Act, is the Court’s primary jurisdictional authority and has been held prior to 1996 to give the United States Court of Federal Claims protest jurisdiction, this from a claimed breach of the implied-in-fact contract of fair and honest consideration which arises from Federal solicitations in connection with the purchase or sale of real or personal property.</p>
<p>28 U.S.C. § 1491(b)(1) was enacted in 1996 and explicitly gives the Court protest jurisdiction “in connection with a procurement or proposed procurement.” The term “procurement” in 28 U.S.C. §1491(b)(1) is limited to the definition of “procurement” in <a href="http://www.law.cornell.edu/uscode/41/usc_sec_41_00000403----000-.html">41 U.S.C. § 403(2)</a>, and thus it is limited to “all stages of the process of acquiring property or services.”</p>
<p>Since 1996, the United States Court of Federal Claims has in some cases decided that its protest jurisdiction lies under <em>both</em> 28 U.S.C. § 1491(a)(1) and 28 U.S.C. § 1491(b)(1), and in other cases the United States Court of Federal Claims has decided that any protest jurisdiction under 28 U.S.C. § 1491(a)(1) has been <em>supplanted</em> by the protest jurisdiction, and the limitations on that protest jurisdiction, conferred in 28 U.S.C. § 1491(b)(1).</p>
<p>The result is confusion about just what actions can today be challenged before the United States Court of Federal Claims—for instance, a <em>sale</em> of Federal personal property can be challenged under 28 U.S.C. § 1491(a)(1) but not under 28 U.S.C. § 1491(b)(1) because a Federal <em>sale</em> is not a Federal “procurement.”</p>
<p>An example is a Forest Service sale of timber from Federal lands, a sale which was properly challenged in the United States Court of Federal Claims in 1988. If 28 U.S.C. § 1491(a)(1) still has force and effect, similar Federal timber sales can be challenged today; if 28 U.S.C. § 1491(a)(1) has been supplanted by the protest jurisdiction conferred in 28 U.S.C. § 1491(b)(1), then a timber sale (or any other sale of surplus Federal property) cannot be challenged in the United States Court of Federal Claims because these actions are not “procurements” as defined by 41 U.S.C. § 403(2).</p>
<p><i>Resource Conservation Group</i> resolves these issues, for here the Federal Circuit holds that while relief in the “procurement” context is exclusive under 28 U.S.C. § 1491(b)(1), relief under 28 U.S.C. § 1491(a)(1) is still available where a Claim arises from a Federal solicitation which is not a “procurement,” i.e. where the Federal solicitation concerns a sale, not an acquisition, or where a Federal solicitation concerns the lease of Federal real property, and not a Federal “procurement” of property or services.</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2010/03/the-federal-circuit-validates-the-implied-in-fact-contract-theory-of-protest-jurisdiction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2010/03/the-federal-circuit-validates-the-implied-in-fact-contract-theory-of-protest-jurisdiction/</feedburner:origLink></item>
		<item>
		<title>Marijuana, the Mexican Spotted Owl, and Jury Verdicts</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/3sbfV1bh-_E/</link>
		<comments>http://www.procurement-lawyer.com/2010/02/marijuana-the-mexican-spotted-owl-and-jury-verdicts/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 16:44:55 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Procurement Law]]></category>
		<category><![CDATA[breach of contract]]></category>
		<category><![CDATA[damages]]></category>
		<category><![CDATA[duty not to hinder]]></category>
		<category><![CDATA[duty to cooperate]]></category>
		<category><![CDATA[fact finding]]></category>
		<category><![CDATA[implied duty of good faith and fair dealing]]></category>
		<category><![CDATA[implied-in-fact]]></category>
		<category><![CDATA[jury verdict]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=273</guid>
		<description><![CDATA[These seemingly unrelated subjects are involved in two rulings by the United States Court of Appeals for the Federal Circuit which together provide important limitations on the implied-in-fact duty not to hinder and to cooperate. The cases are Agredano v. United States, Fed. Cir. No. 2008-5114, February 17, 2010 and Precision Pine and Timber, Inc. [...]]]></description>
			<content:encoded><![CDATA[<p>These seemingly unrelated subjects are involved in two rulings by the United States Court of Appeals for the Federal Circuit which together provide important limitations on the implied-in-fact duty not to hinder and to cooperate. The cases are <a href="http://www.cafc.uscourts.gov/opinions/08-5114.pdf">Agredano v. United States</a>, Fed. Cir. No. 2008-5114, February 17, 2010 and <a href="http://www.cafc.uscourts.gov/opinions/08-5092.pdf">Precision Pine and Timber, Inc. v. United States</a>, Fed. Cir. Nos. 2008-5092, 5093, February 19, 2010. The second of these two cases concludes with insights on the computation of damages for breach of contract.</p>
<p><i>Agredano</i> arose from a purchase of a vehicle at a Customs Service auction of forfeited vehicles. The purchaser later took the vehicle to Mexico where he was stopped at a checkpoint, hidden marijuana was found in the vehicle, and the purchaser spent nearly a year in prison before being exonerated by the Mexican courts. The vehicle had been sold by the Customs Service “as is, where is” without warranty or guarantee and with express disclaimers as to identity, previous ownership, physical condition, or registration status.</p>
<p>The U.S. Court of Federal Claims held that despite the disclaimers, the sales contract for the vehicle contained an implied-in-fact warranty that the vehicle no longer contained contraband, that this implied-in-fact warranty was breached, and thus the purchaser was awarded substantial damages. The Federal Circuit reversed, looking to a prior Federal Circuit decision which holds that an Agency’s failure to perform regulatory or statutory functions does not create contractual obligations, either express or implied-in-fact.</p>
<p><i>Precision Pine</i> arose from a U.S. Court of Federal Claims matter wherein a timber harvesting contractor had been awarded “jury verdict,” or judge-computed, damages resulting from the suspension of one of fourteen Forest Service contracts, suspensions required in order for the Forest Service to engage in Endangered Species Act consultations stemming from the endangered species listing of the Mexican Spotted Owl.</p>
<p>The U.S. Court of Federal Claims had held the Forest Service in breach of the implied duty of good faith and fair dealing, also termed the implied duty not to hinder and to cooperate.</p>
<p>But in <i>Precision Pine</i> the Federal Circuit limits the implied duty of good faith and fair dealing by defining it as just a “variation” of a bait-and-switch, i.e. where the Government enters into a contract that confers a significant benefit and then later eliminates or rescinds that provision or benefit through subsequent action directed at the existing contract, subsequent Government action “specifically designed to re-appropriate the benefits the other party expected to obtain.”</p>
<p>In the case before it, the Federal Circuit decides that there has been no breach of the implied-in-fact duty of good faith and fair dealing because all but one of the Forest Service contracts contained no guarantee that the timber harvesting contractor’s operations could proceed uninterrupted. The suspensions were due to Forest Service violations of the Endangered Species Act, but these were statutory duties not owed to the timber harvesting contractor, just as the purchaser of the seized vehicle in <i>Agredano</i> was owed nothing contractually by the Customs Service under the statutory duty to seize all contraband.</p>
<p>The Federal Circuit holds that the implied-in-fact duty of good faith and fair dealing “cannot expand a party’s contractual duties beyond those in the express contract or create duties inconsistent with the contract’s provisions.” Since all but one of the Forest Service contracts contained no guarantee of uninterrupted performance, the Forest Service’s violations of the Endangered Species Act did not destroy the timber harvesting contractor’s reasonable expectations.</p>
<p>As to the Forest Service contract which did not give the Forest Service the right to suspend performance, the U.S. Court of Federal Claims had rejected the methodology used by the timber harvesting contractor’s damages expert and instead constructed its own alternative calculation. This, the Federal Circuit holds, is entirely permissible—the U.S. Court of Federal Claims was not required to accept the timber harvesting contractor’s calculations in their entirety else enter judgment for the United States.</p>
<p>Here the Federal Circuit explains that in a “jury verdict” a judge may find for a party without fully crediting that party’s methodology, provided that the evidence is sufficient to allow the judge to make a “fair and reasonable approximation” of the damages.</p>
<p>The judge is the fact finder in a bench trial and may decide what evidence to credit or reject, and what result to reach. “Just as jury may find for a party without believing everything that party’s witnesses say, a judge may award damages, even if he does not fully credit that party’s methodology.” Fact findings by a trial judge may not be set aside unless they are clearly erroneous, and these fact findings which minimized the effect of uncertainty and arbitrary assumptions were not.</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2010/02/marijuana-the-mexican-spotted-owl-and-jury-verdicts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2010/02/marijuana-the-mexican-spotted-owl-and-jury-verdicts/</feedburner:origLink></item>
		<item>
		<title>Price Reasonableness, Price Realism, and Protest Review</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/aog6rWGWFtQ/</link>
		<comments>http://www.procurement-lawyer.com/2010/02/price-reasonableness-price-realism-and-protest-review/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 20:20:28 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Procurement Law]]></category>
		<category><![CDATA[arbitrary and capricious]]></category>
		<category><![CDATA[challenges to solicitation terms and conditions]]></category>
		<category><![CDATA[critical miscalculations]]></category>
		<category><![CDATA[irrational assumptions]]></category>
		<category><![CDATA[price realism]]></category>
		<category><![CDATA[price reasonableness]]></category>
		<category><![CDATA[Standard of Review]]></category>
		<category><![CDATA[substitution of judgment]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=253</guid>
		<description><![CDATA[The U.S. Court of Federal Claims provides a clear exposition of the differences between Price Reasonableness and Price Realism and a few lessons about the scope of Protest review in DMS All-Star Joint Venture v. United States, Fed. Cl. No. 09-737C, January 26, 2010. 
At issue in DMS All-Star was a proposed indefinite delivery, indefinite [...]]]></description>
			<content:encoded><![CDATA[<p>The U.S. Court of Federal Claims provides a clear exposition of the differences between Price Reasonableness and Price Realism and a few lessons about the scope of Protest review in <a href="http://www.cofc.uscourts.gov/sites/default/files/BUSH.DMS012610.pdf">DMS All-Star Joint Venture v. United States</a>, Fed. Cl. No. 09-737C, January 26, 2010. </p>
<p>At issue in <em>DMS All-Star</em> was a proposed indefinite delivery, indefinite quantity task order Contract for maintenance, repair, and minor construction work on real property located at Fort Sill, Oklahoma. Firm fixed-price task orders were to be issued to the successful Contractor, and these would be priced based on agreed-upon mark-ups against published <a href="http://rsmeans.reedconstructiondata.com/60010.aspx">RSMeans Construction Cost</a> prices. Offerors competed based on these mark-ups. </p>
<p>The Solicitation promised that Price Proposals would be evaluated for Price Reasonableness and for Price Realism. </p>
<p>Price Reasonableness looks at the Price to be paid (is the Government paying too much?), and Price Realism looks at the risk of a low-priced Proposal and whether or not an Offeror’s Price is overly optimistic or impractically low (is the Offeror asking too little?).</p>
<p>The question whether or not a Price is realistic concerns <em>only</em> an Offeror’s understanding of Solicitation requirements, because if an Offeror can demonstrate that it understands the requirement, that Offeror can nonetheless choose to offer a buy-in just to win the Competition for a firm, fixed-price Contract. </p>
<p>Price Realism was before the U.S. Court of Appeals for the Federal Circuit in <a href="http://www.cafc.uscourts.gov/opinions/09-5021.pdf">Alabama Aircraft Industries, Inc. v. United States</a>, Fed. Cir. Nos. 2009-5021, -5022, and -5023, November 17, 2009. The <em>Alabama Aircraft</em> Court reversed the U.S. Court of Federal Claims, holding that the Court below had overstepped its bounds when it rejected an Agency’s Price Realism analysis, not because this Price Realism analysis was inconsistent with Solicitation requirements, but instead because the Court below thought that the Agency did not expressly consider, as it should have, the impact of the aging KC-135 fleet in its Price Realism analysis. </p>
<p>The <em>Alabama Aircraft</em> Court held that this was an impermissible substitution of the Court’s judgment for the Agency’s, a substitution not allowed under the narrow “arbitrary and capricious” standard of review which is applied to Protests. </p>
<p>It is no surprise, then, that <em>DMS All-Star</em> pays careful attention to the limits of Protest review as it applies to Price Realism analysis.</p>
<p>If a Solicitation does not set out a particular methodology for the Price Realism analysis, then on a Protest review the only limitation is that the Agency’s Price Realism analysis must be demonstrated not to contain any critical miscalculations, and must not make any irrational assumptions. In these Solicitations, the Agency’s Price Realism analysis has little vulnerability to a challenge on “adequacy” grounds. The Agency has broad discretion. </p>
<p>If a Solicitation sets out a methodology for the Price Realism analysis, then the Agency must demonstrate that it has followed the announced evaluation criteria, this in addition to demonstrating that the Price Realism analysis does not contain any critical miscalculations, and does not make any irrational assumptions. </p>
<p>The message in <em>DMS All-Star</em> is a simple one—if an Offeror believes that the announced Price Realism analysis is incomplete or unspecific, then the time to challenge these announced evaluation criteria is before the date set for receipt of initial Competitive Proposals, not later. </p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2010/02/price-reasonableness-price-realism-and-protest-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2010/02/price-reasonableness-price-realism-and-protest-review/</feedburner:origLink></item>
		<item>
		<title>The A-12 and Adequate Assurance of Progress</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/RnycjbVhd3w/</link>
		<comments>http://www.procurement-lawyer.com/2009/06/the-a-12-and-adequate-assurance-of-progress/#comments</comments>
		<pubDate>Wed, 03 Jun 2009 17:46:10 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Adequate Assurance of Progress]]></category>
		<category><![CDATA[A-12]]></category>
		<category><![CDATA[anticipatory repudiation]]></category>
		<category><![CDATA[cost overruns]]></category>
		<category><![CDATA[cost type contract]]></category>
		<category><![CDATA[cure notice]]></category>
		<category><![CDATA[Default Termination]]></category>
		<category><![CDATA[delivery failure]]></category>
		<category><![CDATA[delivery schedule]]></category>
		<category><![CDATA[fixed-price contract]]></category>
		<category><![CDATA[impossibility]]></category>
		<category><![CDATA[restatement (second) of contracts 251]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=173</guid>
		<description><![CDATA[Another chapter in the A-12 story has just been published by a panel of the United States Court of Appeals for the Federal Circuit, this McDonnell Douglas Corp. and General Dynamics Corp. v. United States, Fed Cir. Nos. 2007-5111, -5131, June 2, 2009.
It needs to be remembered that the proposed A-12 Avenger was to be [...]]]></description>
			<content:encoded><![CDATA[<p>Another chapter in the <a href="http://www.fas.org/programs/ssp/man/uswpns/air/attack/a12.html">A-12</a> story has just been published by a panel of the United States Court of Appeals for the Federal Circuit, this <a href="http://www.cafc.uscourts.gov/opinions/07-5111.pdf"><em>McDonnell Douglas Corp. and General Dynamics Corp. v. United States</em></a>, Fed Cir. Nos. 2007-5111, -5131, June 2, 2009.</p>
<p>It needs to be remembered that the proposed A-12 Avenger was to be a carrier-based stealth aircraft and was under development on a Navy fixed-price incentive Contract with a ceiling price of $4,777,330,294. The Contractors were to be design, manufacture, and test eight prototypes with the first aircraft to be delivered in June 1990 and the remaining seven to be delivered monthly through January 1991. The Contractors fell behind schedule and the Navy issued a unilateral Contract modification in August 1990 setting a new first aircraft delivery date of December 1991.</p>
<p>The Contractors thereafter experienced continuing problems meeting Contract performance requirements and schedule and their continued operations were running significantly over budget—they were spending some $120-$150 million of their own money each month. They projected in December 1990 that the first prototype aircraft would not be delivered until March 1992 and this only if there were significant changes in performance requirements. The then-Secretary of Defense, Dick Cheney, directed the Navy to demonstrate that the A-12 project was still viable.</p>
<p>The Navy issued a Cure Notice on December 17, 1990—a Cure Notice is a demand that the Contractor demonstrate or give assurances that progress is being made toward timely completion of the Contract, else that any prospective delay in Contract completion is not the Contractor’s responsibility. The Navy demanded assurance of Contract performance by January 2, 1991.</p>
<p>The Contractors responded on January 2, 1991 that they could not meet the delivery schedule or existing Contract performance requirements. They asserted that the delivery schedule was unenforceable and that performance requirements were “impossible to satisfy.” The Contractors proposed a restructured cost-reimbursement Contract, in exchange for which they would absorb a fixed loss of $1.5 billion and would waive their Contract Claims. The Contractors gave assurance of their commitment to the A-12 program.</p>
<p>On January 6, 1991 the Acting Under Secretary refused to agree to a restructured cost-reimbursement Contract. On January 7, 1991 the Navy Contracting Officer terminated the Contract for Default. A few weeks later, the Navy demanded the return of some $1.35 billion in unliquidated progress payments.</p>
<p>After several voyages between the United States Court of Federal Claims and the Federal Circuit, the Court of Federal Claims upheld the Default termination, this after having been directed by the Federal Circuit to “focus on the events, actions, and communications leading to the default decision in ascertaining whether the contracting officer had a reasonable belief that there was no likelihood of timely completion.”</p>
<p>Now a panel of the Federal Circuit affirms, holding that Default termination for failure to make progress is objectively justified. The Federal Circuit panel does not consider whether or not the Contractors’ response of January 2, 1991 to the Cure Notice was an adequate assurance of progress.</p>
<p>What?</p>
<p>The law in the Federal Circuit teaches that responses to Cure Notices are judged as a species of the law of anticipatory repudiation, i.e., whether or not the response to the Cure Notice reasonably supported a belief that the Contractor would not perform, in which circumstance the Contract can be treated as repudiated. <a href="http://www.ll.georgetown.edu/federal/judicial/fed/opinions/99opinions/99-1343.pdf"><i>Danzig v. AEC Corp.</i></a>, Fed. Cir. September 25, 2000, 2000 U.S. App. LEXIS 23731, *12-*14.</p>
<p><i>Restatement (Second) of Contracts § 251 comment e.</i> explains that the “adequacy” of such an assurance “depends on what is reasonable to require in a particular case taking account of the circumstances of that case.” <i>Restatement (Second) of Contracts § 251(2)</i> provides that an “obligee may treat as a repudiation the obligor’s failure to provide within a reasonable time <i>such assurance of due performance as is adequate in the circumstances of the particular case</i>.” (Emphasis added).</p>
<p>It appears that A-12 Default has been reviewed by this panel based on the wrong standard. How is it that the Navy’s actions are affirmed without consideration of the questions about impossibility and Contract type which are raised in the Contractors’ assurance of January 2, 1991?</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/06/the-a-12-and-adequate-assurance-of-progress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/06/the-a-12-and-adequate-assurance-of-progress/</feedburner:origLink></item>
		<item>
		<title>Limitations Imposed by Administrative Procedure Act Review</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/YhSxVSbi6ak/</link>
		<comments>http://www.procurement-lawyer.com/2009/05/limitations-imposed-by-administrative-procedure-act-review/#comments</comments>
		<pubDate>Wed, 06 May 2009 13:38:49 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Administrative Procedure Act Review]]></category>
		<category><![CDATA[28 U.S.C. section 1491(b)(4)]]></category>
		<category><![CDATA[41 U.S.C. section 609(a)(3)]]></category>
		<category><![CDATA[5 U.S.C. section 706(2)(A)]]></category>
		<category><![CDATA[Bid Guarantee]]></category>
		<category><![CDATA[Contract Disputes Act]]></category>
		<category><![CDATA[Federal Acquisition Regulation 28.203-1]]></category>
		<category><![CDATA[Federal Acquisition Regulation 28.203-2]]></category>
		<category><![CDATA[Organizational Conflict of Interest]]></category>
		<category><![CDATA[Standard of Review]]></category>
		<category><![CDATA[Tucker Act]]></category>
		<category><![CDATA[U.S. Court of Federal Claims]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=154</guid>
		<description><![CDATA[Two recent decisions by the United States Court of Appeals for the Federal Circuit concern the limited standard of review imposed on Protests, i.e., challenges to Solicitations, else challenges to particular Contracts.
The first, Tip Top Construction, Inc. v. United States, Fed. Cir. No. 2008-5183, April 29, 2009, arose from a decision of the United States [...]]]></description>
			<content:encoded><![CDATA[<p><span style="LINE-HEIGHT: 115%; FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Two recent decisions by the United States Court of Appeals for the Federal Circuit concern the limited standard of review imposed on Protests, i.e., challenges to Solicitations, else challenges to particular Contracts.</span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The first, <a style="mso-bidi-font-style: normal;" href="http://www.cafc.uscourts.gov/opinions/08-5183.pdf">Tip Top Construction, Inc. v. United States</a>, Fed. Cir. No. 2008-5183, April 29, 2009, arose from a decision of the United States Court of Federal Claims which denied a challenge to a Contract awarded for construction of a traffic roundabout, this because the Contracting Officer had rejected as nonresponsible an individual surety for the otherwise low bidder who pledged marketable coal as a bid guarantee. <span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The second, <a href="http://www.cafc.uscourts.gov/opinions/08-5072.pdf"><em style="mso-bidi-font-style: normal;">Axiom Resource Management, Inc. v. United States</em></a>, Fed. Cir. No. 2008-5072, -5073, May 4, 2009 is a reversal of a decision of the United States Court of Federal Claims which had precluded the Army from exercising an option for renewed performance of a program management support Contract, there after the Court of Federal Claims concluded that the Army Contracting Officer had unlawfully failed to mitigate a potential organizational conflict of interest.</span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">In both decisions the Federal Circuit applied, as required by <a href="http://www4.law.cornell.edu/uscode/html/uscode28/usc_sec_28_00001491----000-.html">28 U.S.C. § 1491(b)(4)</a>, the Administrative Procedure Act standard of review set out in <a href="http://www4.law.cornell.edu/uscode/html/uscode05/usc_sec_05_00000706----000-.html">5 U.S.C. § 706(2)(A)</a>. <span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">Generally, this review standard requires: (1) that the Court look only at the record (the facts) as they were before the Contracting Officer, <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=470&amp;invol=729"><em style="mso-bidi-font-style: normal;">Florida Power &amp; Light Company v. Lorion</em></a>, 470 U.S. 729, 743-744 (1985); and (2) that the reviewing Court judge the Contracting Officer’s actions solely by the grounds invoked by the Contracting Officer, and not by substituting what the Court considers to be a more adequate, or a better, basis, <a href="http://www.ll.georgetown.edu/federal/judicial/fed/opinions/99opinions/99-5098.pdf"><em style="mso-bidi-font-style: normal;">OMV Medical, Incorporated v. United States</em></a>, 219 F.3d 1337, 1344 (Fed. Cir. 2000) (applying <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=332&amp;invol=194"><em style="mso-bidi-font-style: normal;">SEC v. Chenery Corporation</em></a>, 332 U.S. 194, 196 (1947)).</span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">This Administrative Procedure Act standard of review is narrow, this reflecting a concern that Courts not interfere with matters entrusted to the judgment of Contracting Officers. A different regime prevails under the Contract Disputes Act, 41 U.S.C. §§ 601-613. There a de novo standard of review is imposed, <a href="http://www4.law.cornell.edu/uscode/html/uscode41/usc_sec_41_00000609----000-.html">41 U.S.C. § 609(a)(3)</a>, and the Court conducts an independent examination of the relevant facts.</span></span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The problem with <em style="mso-bidi-font-style: normal;">Axiom Resource Management</em>, per the Federal Circuit, was that the Court below admitted extra-record evidence, freely allowing the parties to supplement the record “with whatever they want,” without first making a threshold determination whether this extra-record evidence was necessary. Doing so, the Court of Federal Claims admitted the declarations of two expert witnesses, and then the Court relied on these declarations to conclude that the Contracting Officer’s efforts to mitigate a potential organizational conflict of interest were unreasonable. This, the Federal Circuit observed, was de novo review, not Administrative Procedure Act review, and was “inconsistent” with the discretion given the Army Contracting Officer and with administrative law principles.</span></span></span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The Federal Circuit’s affirmance in <em style="mso-bidi-font-style: normal;">Tip Top Construction</em> is less obvious than the Federal Circuit’s reversal in <em style="mso-bidi-font-style: normal;">Axiom Resource Management</em>.</span></span></span></span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The <em style="mso-bidi-font-style: normal;">Tip Top Construction</em> Contracting Officer had rejected the proffered individual surety as nonresponsible because, reasoned the Contracting Officer, marketable coal was a “speculative” asset, this per <a href="http://acquisition.gov/comp/far/current/html/Subpart%2028_2.html#wp1073314">Federal Acquisition Regulation 28.203-2(c)</a>. But other, nonetheless acceptable assets which may be pledged by individual sureties are likewise “speculative,” i.e., stocks and bonds traded on national U.S. security exchanges or real property owned in fee simple, <a href="http://acquisition.gov/comp/far/current/html/Subpart%2028_2.html#wp1073314">Federal Acquisition Regulation 28.203-2(b)</a>.</span></span></span></span></span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">This reality was enough of a problem for the Court of Federal Claims that the Court expressly found the Contracting Officer’s nonresponsibility determination reasonable not on the grounds invoked by the Contracting Officer, but rather because assets pledged by an individual surety, whether or not “speculative,” must, per <a href="http://acquisition.gov/comp/far/current/html/Subpart%2028_2.html#wp1073314">Federal Acquisition Regulation 28.203-1(b)</a>, be secured by deposit into an escrow account, else secured by a recorded lien on real property. And a pile of coal, although it has a readily ascertainable value, cannot be deposited into escrow.</span></span></span></span></span></span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The Federal Circuit explicitly ignores this disconnect, simply holding in <em style="mso-bidi-font-style: normal;">Tip Top Construction</em> that the Contracting Officer’s nonresponsibility determination “is sustainable on the ground articulated by the contracting officer—namely, that the pledged coal was not the type of asset that is acceptable under the FAR as a bid bond asset.” Yet in <em style="mso-bidi-font-style: normal;">OMV Medical</em>, the Federal Circuit returned a price reasonableness determination to the Court of Federal Claims for further proceedings, an express recognition of the rule in <em style="mso-bidi-font-style: normal;">Chenery,</em> when it turned out that the Court below in fact had affirmed that price reasonableness determination on a ground not considered by the Contracting Officer.</span></span></span></span></p>
<p><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"><span style="line-height: 115%; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">The affirmance in <em style="mso-bidi-font-style: normal;">Tip Top Construction</em> appears to be a bow to practicality rather than an acknowledgment of administrative law principles. <em style="mso-bidi-font-style: normal;">Axiom Resource Management</em>, on the other hand, demands “by the book” adherence to the narrow Administrative Procedure Act standard of review.</span></span></span></span></span></p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/05/limitations-imposed-by-administrative-procedure-act-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/05/limitations-imposed-by-administrative-procedure-act-review/</feedburner:origLink></item>
		<item>
		<title>“Control” Requirements for Service-Disabled Veteran-Owned Small Business Concerns</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/PLpcJtmuRA4/</link>
		<comments>http://www.procurement-lawyer.com/2009/04/control-requirements-for-service-disabled-veteran-owned-small-business-concerns/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 15:46:59 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA["Control" Requirements for SDVOSBC's]]></category>
		<category><![CDATA[15 USC section 657f]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[Center for Veterans Enterprise (CVE)]]></category>
		<category><![CDATA[Federal Acquisition Regulation 19.1405]]></category>
		<category><![CDATA[SDVOSBC Preference]]></category>
		<category><![CDATA[Small Business Administration Status Protests]]></category>
		<category><![CDATA[VetBiz.gov Vendor Information Pages Database]]></category>
		<category><![CDATA[Veterans Benefit Act]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=71</guid>
		<description><![CDATA[A procurement preference created by the Veterans Benefit Act of 2003, 15 U.S.C. § 657f, is the preference for small business concerns owned and controlled by service-disabled veterans. This preference is principally ensured by set-asides exclusively for service-disabled veteran-owned small business concerns (known generally as SDVOSBC’s), and procedures for these SDVOSBC Contract set-asides are set [...]]]></description>
			<content:encoded><![CDATA[<p>A procurement preference created by the Veterans Benefit Act of 2003, <a href="http://www4.law.cornell.edu/uscode/html/uscode15/usc_sec_15_00000657---f000-.html">15 U.S.C. § 657f</a>, is the preference for small business concerns owned and controlled by service-disabled veterans. This preference is principally ensured by set-asides exclusively for service-disabled veteran-owned small business concerns (known generally as SDVOSBC’s), and procedures for these SDVOSBC Contract set-asides are set out at <a href="http://acquisition.gov/comp/far/current/html/Subpart%2019_14.html#wp1093836">Federal Acquisition Regulation 19.1405</a>.</p>
<p>Eligibility requirements for SDVOSBC’s were established by the Small Business Administration (SBA) in 2004 in Service-Disabled Veteran-Owned (SDVO) Small Business Concern (SBC) Program Rules at 13 Code of Federal Regulations (CFR) Subparts A and B (<a href="http://edocket.access.gpo.gov/cfr_2009/janqtr/pdf/13cfr125.8.pdf">13 CFR §§ 125.8</a> through 125.13—Definitions and Eligibility Requirements) and in Subpart C (<a href="http://edocket.access.gpo.gov/cfr_2009/janqtr/pdf/13cfr125.14.pdf">13 CFR §§ 125.14</a> through 125.23—SDVO Contracts). Subpart D of the SBA SDVOSBC Program Rules (<a href="http://edocket.access.gpo.gov/cfr_2009/janqtr/pdf/13cfr125.24.pdf">13 CFR §§ 125.24</a> through 125.28) sets out Protest procedures allowing Contracting Officers and other Offerors competing for specific SDVOSBC Contracts to challenge the status of particular SDVOSBC’s.</p>
<p>In May 2008 the Department of Veterans Affairs’ (VA’s) Center for Veterans Enterprise (CVE) published <a href="http://edocket.access.gpo.gov/2008/pdf/E8-10489.pdf">interim verification guidelines</a> which permit (but do not require) VA Contracting Officers to set-aside particular VA acquisitions if there are available SDVOSBC’s listed as “verified” in the <a href="http://www.vip.vetbiz.gov/">VetBiz.gov Vendor Information Pages (VIP) database</a>. These CVE interim verification guidelines, which largely parallel the SBA Program Rules, explicitly provide for SDVOSBC status verification and then listing by VA’s CVE in the VetBiz VIP database.</p>
<p>But neither the CVE interim verification guidelines nor the CVE itself give VA the final authority to determine SDVOSBC status. Instead, challenges to SDVOSBC status, either by a Contracting Officer or by another Offeror, are decided only by SBA. <a href="http://www.gao.gov/decisions/bidpro/310552.pdf"><em>Singleton Enterprises-GMT Mechanical, A Joint Venture</em></a>, B-310552, January 10th, 2008, at 3.</p>
<p>It turns out that there are presently 47 published decisions from SBA’s Office of Hearings and Appeals (OHA) which apply the SBA SDVOSBC Program Rules in deciding challenges to SDVOSBC status. Many of these published OHA decisions concern one particular aspect of the eligibility requirements for the SDVOSBC Program, and this particular aspect is the “control” requirement.</p>
<p>The “control” requirement is explained at <a href="http://edocket.access.gpo.gov/cfr_2009/janqtr/pdf/13cfr125.10.pdf">13 CFR § 125.10</a>.</p>
<p>The “control” requirement demands: (1) that long-term decision-making and day-to-day management of the enterprise both must be conducted by one or more service-disabled veterans, 13 CFR § 125.10(a); (2) that a service-disabled veteran hold the highest officer position in the enterprise and that this service-disabled veteran have managerial experience of the extent and complexity needed to run the concern, else possess ultimate managerial and supervisory control over those who possess the required licenses or technical experience, 13 CFR § 125.10(b); and (3) that one or more service-disabled veterans have control over all decisions of the enterprise, this control including the ability to overcome any supermajority voting requirements for decisions otherwise made in the normal course of business, 13 CFR § 125.10(c), (d), (e).</p>
<p>Challenges to required “control” for SDVOSBC status often concern geography—that is, the qualifying service-disabled veteran is located at a site remote from the place of business and/or from the site of Contract performance. If the qualifying service-disabled veteran is located at a site remote from the place of business and from the site of contract performance, then it is likely that SBA will find a lack of “control.” If the service-disabled veteran is proximate to the place of business, then the question becomes whether or not the Contract in question requires intense on-site supervision. <em>See, e.g., <a href="http://www.sba.gov/aboutsba/sbaprograms/oha/allcases/VET/VET-132.pdf">Matter of NuGate Group</a></em>, VET-132, April 24, 2008, at 7.</p>
<p>Supermajority restrictions on business decisions, while common in the operating documents for any private enterprise, including SDVOSBC’s, have an effect on the required “control” for SDVOSBC status which is not as easily resolved. This difficulty stems from the difference between supermajority restrictions limited to circumstances outside the normal course of business (e.g., changes to the operating documents, issuing additional capital stock, or entering into a different line of business) and supermajority provisions not so limited (e.g., appointment and compensation of officers, limits on making other than nominal expenditures, or borrowing money for operations).</p>
<p>OHA has in the past, <em><a href="http://www.sba.gov/aboutsba/sbaprograms/oha/allcases/sizecases/SIZ-4973.pdf">Size Appeal of EA Engineering, Science, and Technology, Inc.</a></em>, SIZ-4973, July 14, 2008, at 9, made a distinction between supermajority restrictions limited to circumstances outside the normal course of business and supermajority restrictions not so limited, there holding that supermajority restrictions which could be imposed in only three “extraordinary” circumstances outside the normal course of business were insufficient to prove affiliation.</p>
<p>But as regards the SBA SDVOSBC Program Rules, OHA has construed the “all decisions” language of 13 CFR § 125.10(c), (d), (e) strictly, holding that “<em>any</em> specified decisions requiring a supermajority that the [service-disabled veteran] could not himself satisfy” render an enterprise ineligible for status as an SDVOSBC. <em><a href="http://www.sba.gov/aboutsba/sbaprograms/oha/allcases/VET/VET-142.pdf">Matter of Heritage of America, LLC</a></em>, VET-142, November 12, 2008, at 8 (emphasis added).</p>
<p>The problem with <em>Heritage of America</em> is that the supermajority restrictions there included <em>both</em> circumstances outside the normal course of business and circumstances within the normal course of business (i.e., making other than nominal expenditures or borrowing money). In a previous decision, <em><a href="http://www.sba.gov/aboutsba/sbaprograms/oha/allcases/VET/VET-137.pdf">Matter of Firewatch Contracting of Florida, LLC</a></em>, VET-137, August 1, 2008, at 8, OHA had distinguished <em>EA Engineering</em> as applying only where supermajority restrictions were expressly limited to circumstances outside the normal course of business.</p>
<p><em>Heritage of America</em> could have been more narrowly decided. Unfortunately, it was not.</p>
<p>We’re going to have to wait for future OHA decisions to see if the sensible distinction between supermajority restrictions limited to circumstances outside the normal course of business and supermajority restrictions not so limited, the distinction which was the focus of <em>EA Engineering</em>, will ever be applied to a challenge of SDVOSBC status.</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/04/control-requirements-for-service-disabled-veteran-owned-small-business-concerns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/04/control-requirements-for-service-disabled-veteran-owned-small-business-concerns/</feedburner:origLink></item>
		<item>
		<title>Implied-in-Fact Contract Theory of Protest Jurisidiction</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/E4frk_QTAvE/</link>
		<comments>http://www.procurement-lawyer.com/2009/04/implied-in-fact-contract-theory-of-protest-jurisidiction/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 16:30:52 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Implied-in-Fact Contract]]></category>
		<category><![CDATA[Administrative Dispute Resolution Act]]></category>
		<category><![CDATA[Federal Acquisition Regulation 1.102]]></category>
		<category><![CDATA[Protest Jurisdiction]]></category>
		<category><![CDATA[Tucker Act]]></category>
		<category><![CDATA[U.S. Court of Federal Claims]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=65</guid>
		<description><![CDATA[Prior to 1996 the jurisdiction of the United States Court of Federal Claims to hear and consider a Protest challenging a Federal Procurement was premised on the Court’s Tucker Act, 28 U.S.C. § 1491(a)(1), jurisdiction, this on an Implied-in-Fact Contract of fair and honest consideration. The situation was changed with the Administrative Dispute Resolution Act [...]]]></description>
			<content:encoded><![CDATA[<p>Prior to 1996 the jurisdiction of the United States Court of Federal Claims to hear and consider a Protest challenging a Federal Procurement was premised on the Court’s Tucker Act, 28 U.S.C. § 1491(a)(1), jurisdiction, this on an Implied-in-Fact Contract of fair and honest consideration. The situation was changed with the Administrative Dispute Resolution Act of 1996 (ADRA) which provides private parties an independent cause of action, 28 U.S.C. § 1491(b)(1), to Protest at any stage in the Federal Procurement process, there contesting any violation of Statute or Regulation.</p>
<p>But the ADRA left unresolved the question whether the Implied-in-Fact Contract theory of Protest jurisdiction had survived, and on this question there has been neither unanimity nor a definitive ruling from the Court’s supervisory authority, the United States Court of Appeals for the Federal Circuit.</p>
<p>Perhaps this question is now resolved by <a href="http://www.cofc.uscourts.gov/sites/default/files/FIRESTONE.FFTF030209.pdf"><em>FFTF Restoration Company, LLC v. United States</em>, Fed. Cl. No. 07-659C, Judge Nancy B. Firestone, March 2nd, 2009</a>, a Protest arising from the Department of Energy’s cancellation of a small-business set-aside Solicitation for deactivation and decommissioning of a nuclear reactor at the Hanford Site. Here Judge Firestone concludes that the Implied-in-Fact Contract theory of Protest jurisdiction survives the ADRA by “fitting within the ambit of the requirements to act with integrity, fairness, and openness, and to treat bidders fairly,” these imposed by <a href="http://acquisition.gov/comp/far/current/html/Subpart%201_1.html#wp1130776">Federal Acquisition Regulation 1.102(b)(3) and 1.102-2(c)(3)</a>.</p>
<p>Judge Firestone says that FFTF’s claims of breach of an implied-in-fact Contract and FFTF’s assertions of violations of the Federal Acquisition Regulation are “virtually indistinguishable.” Noting that the ADRA does not limit the theories under which violations are claimed, Judge Firestone concludes that claims of breach of an implied-in-fact Contract are permissible under ADRA.</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/04/implied-in-fact-contract-theory-of-protest-jurisidiction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/04/implied-in-fact-contract-theory-of-protest-jurisidiction/</feedburner:origLink></item>
		<item>
		<title>Record Submission versus Summary Judgment</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/CV3Ml6Mpg5M/</link>
		<comments>http://www.procurement-lawyer.com/2009/04/record-submission-versus-summary-judgment/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 18:14:20 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Armed Services Board of Contract Appeals]]></category>
		<category><![CDATA[Contract Disputes Act]]></category>
		<category><![CDATA[Record Submission]]></category>
		<category><![CDATA[Summary Judgment]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=57</guid>
		<description><![CDATA[Under the Contract Disputes Act, under 41 U.S.C. § 606, Contractors have ninety days to appeal from a Contracting Officer’s Final Decision to an Agency Board of Contract Appeals, else under 41 U.S.C. § 609(a)(1), Contractors have one year to file suit in the United States Court of Federal Claims. A significant distinction in the [...]]]></description>
			<content:encoded><![CDATA[<p>Under the Contract Disputes Act, under 41 U.S.C. § 606, Contractors have ninety days to appeal from a Contracting Officer’s Final Decision to an Agency Board of Contract Appeals, else under 41 U.S.C. § 609(a)(1), Contractors have one year to file suit in the United States Court of Federal Claims. A significant distinction in the practice at these forums is the Agency Board requirement for submitting a Rule 4 Appeal File compendium of the contested Final Decision, the Contract, and relevant correspondence and other documents. There is no comparable requirement in the Rules of the Court of Federal Claims.</p>
<p>In <a href="http://docs.law.gwu.edu/asbca/decision/pdf2009/55030.pdf"><em>Osborne Construction Company</em>, ASBCA No. 55030, February 19th, 2009</a>, the Armed Services Board of Contract Appeals points out the flexibility afforded Agency Boards with the Rule 4 Appeal File, a flexibility which stems from Agency Board ability to rely on the Rule 4 documents and from the discretion given Agency Boards to weigh this documentary evidence.</p>
<p>A decision on a motion, or cross-motions, for Summary Judgment before the Court of Federal Claims is often thought comparable to a Record Submission before an Agency Board. But a decision on Summary Judgment does not allow for a creditability assessment and there the record itself can be later enlarged or changed before the Civil Action is ready for decision.</p>
<p>Indeed, the Court of Federal Claims recognizes this limitation on Summary Judgment—while Contract Disputes Act Claims sometimes obtain Summary Judgment on liability, damages determination requires detailed factual inquiries and credibility determinations. <a href="http://www.cofc.uscourts.gov/sites/default/files/BLOCK.TRAVELERS031907.pdf"><em>See, e.g., Travelers Casualty and Surety Company of America v. United States</em></a>, 75 Fed. Cl. 696,724 (2007).</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/04/record-submission-versus-summary-judgment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/04/record-submission-versus-summary-judgment/</feedburner:origLink></item>
		<item>
		<title>A Default Termination in Bad Faith</title>
		<link>http://feedproxy.google.com/~r/CyrusEPhillipsIv/~3/S9De8Do_hlE/</link>
		<comments>http://www.procurement-lawyer.com/2009/04/a-default-termination-in-bad-faith/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 13:41:40 +0000</pubDate>
		<dc:creator>Cyrus E. Phillips IV</dc:creator>
				<category><![CDATA[Bad Faith]]></category>
		<category><![CDATA[Default Termination]]></category>
		<category><![CDATA[Procurement Law]]></category>

		<guid isPermaLink="false">http://www.procurement-lawyer.com/?p=44</guid>
		<description><![CDATA[Keeter Trading Company, Inc. v. United States, Fed. Cl. No. 05-243C, Judge Lynn J. Bush, February 3rd, 2009, is a rare decision by the United States Court of Federal Claims awarding a rural mail carrier breach damages after concluding that a Default termination was made in bad faith. Although the terms of the Default Clause [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.cofc.uscourts.gov/sites/default/files/BUSH.KEETER020309.pdf"><em>Keeter Trading Company, Inc. v. United States</em>, Fed. Cl. No. 05-243C, Judge Lynn J. Bush, February 3rd, 2009</a>, is a rare decision by the United States Court of Federal Claims awarding a rural mail carrier breach damages after concluding that a Default termination was made in bad faith. Although the terms of the Default Clause there typically limited available damages in the event the Default was later found improper, the Court awarded breach damages not so limited by that Default Clause.</p>
<p>Actions of the local Postmistress were the basis of the bad faith termination: (1) route changes were unilaterally imposed which disproportionately benefitted another carrier and these route changes were made on a pretext which could not be supported; (2) the local Postmistress unreasonably “wrote up” the carrier on Contract performance issues and demanded that supervisory Postal Service contracting personnel terminate the carrier’s Contract when he refused to perform unilateral changes which were not allowed by the Changes Clause (only Changes up to $2,500 could be unilaterally imposed). The Court held that these actions were a “contrivance” effected to deprive the carrier of his reasonable Contract expectations and thus amounted to an “obvious violation” of the duty of good faith and fair dealing.</p>
<p>Although the local Postmistress was not the Contracting Officer, the Court found that supervisory contracting personnel had relied almost exclusively on the representations of the local Postmistress and had disregarded clear Contract language. More to the point, the Court concluded that these supervisory contracting personnel had failed to make decisions that were the product of their own personal, informed, and independent judgment.</p>
<p><em>Keeter Trading</em> importantly emphasizes that beyond animus, bad faith can also result from a combination of actions destroying a Contractor’s bargained-for rights together with a failure of independent decision-making.</p>
<p>&copy;2010 <a href="http://www.procurement-lawyer.com">Cyrus E. Phillips IV</a>. All Rights Reserved.</p>.]]></content:encoded>
			<wfw:commentRss>http://www.procurement-lawyer.com/2009/04/a-default-termination-in-bad-faith/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.procurement-lawyer.com/2009/04/a-default-termination-in-bad-faith/</feedburner:origLink></item>
	</channel>
</rss>
