Are Construction Contract Limitation of Liability Clauses on the Way Out in Virginia?

Remember BAE Systems and Fluor?  This post is the third here at Construction Law Musings relating to this case which is a seemingly never-ending source for content.  In the prior post discussing this case, the Court found that Va. Code 1-4.1:1 which bars waiver of a right to payment before work is performed did not apply because Fluor had provided work before execution of the contract or any change orders.

In the most recent opinion in this long-running litigation,  and after a motion to reconsider by Fluor that was granted, the Court re-examined this finding along with the contractual language found in the Limitation of Damages (LOD) clause and came to the opposite conclusion regarding certain change orders that remained unpaid by BAE. Continue reading Are Construction Contract Limitation of Liability Clauses on the Way Out in Virginia?

Construction Contract Terms Matter. Be Careful When You Draft Them.

Originally posted 2022-01-28 12:15:02.

In a prior post, I discussed the case of Fluor Fed. Sols., LLC v. Bae Sys. Ordinance Sys in the context of the interplay between fraud, contract, and statutes of limitation.  Some cases just keep on giving.  This time the case illustrates the need for careful drafting of those pesky, and highly important, clauses in your construction documents.

In the current iteration of this ongoing saga, the Court considered the contractual aspects of the matter.  As a reminder, the facts are as follows:  In May 2011, the United States Army (“Army) awarded BAE Systems Ordnance Systems, Inc. (“BAE”) a contract to design and construct a natural gas-fired combined heating and power plant for the Radford Army Ammunition Plant (“RAAP”). On October 7, 2015, BAE issued a request for a proposal from Fluor Federal Solutions, LLC (“Fluor”) to design and build a temporary boiler facility at a specific location on the RAAP property. On October 13, 2015, the Army modified the prime contract to change the location of the boiler facility. On December 10, 2015, the Army modified the prime contract to require BAE to design and construct a permanent boiler facility. On December 30, 2015, Fluor and BAE executed a fixed-price subcontract for Fluor to design and construct the temporary boiler. Throughout 2016, BAE issued several modifications to Fluor’s subcontract to reflect the modifications BAE received from the Army on the prime contract. On March 23, 2016, BAE directed Fluor to build a permanent – rather than temporary – boiler facility. On March 28, 2016, Fluor began construction of the permanent facility and began negotiations with BAE about the cost of the permanent facility. On September 1, 2016, the parties reached an agreement on the cost for the design of the permanent facility, but not on the cost to construct the permanent facility. On November 29, 2016, the parties executed a modification to the subcontract, officially replacing the requirement to construct a temporary facility with a requirement to construct a permanent facility and agreeing to “negotiate and definitize the price to construct by December 15, 2016.” The parties were unable to reach an agreement on the construction price. Continue reading Construction Contract Terms Matter. Be Careful When You Draft Them.

Motions to Dismiss, Limitations of Liability, and More

Remember BAE Sys. Ordnance Sys. V. Fluor Fed. Sols?  I examined that case on two occasions previously here at Construction Law Musings.  Previously the discussions were about the mix (or lack thereof) between fraud and contract and about how careful contract drafting is key.

In the most recent opinion in this ongoing litigation from March of 2022, the Court examined various motions to dismiss the Complaint and Counterclaim in the matter.  As a reminder, the basic facts are as follows.

The US Army Joint Munitions Command (“Army”) contracted with BAE Systems OrdnanceSystems, Inc. (“BAE”) to operate and maintain the Radford Army Ammunition Plant (“RFAAP”)under a basic ordering agreement (“BOA”). Under BOA Task Order 002, BAE contracted to replace the legacy NC facility at the RFAAP with a newer one (the “NC Project”). Initially, BAE subcontracted the NC Project to Lauren Engineers & Constructors (“Lauren”), but later terminated Lauren. Despite terminating Lauren, BAE’s timeline to complete the NC Project remained unchanged and BAE was required to use Lauren’s design for the NC Project. BAE gave interested bidders access to the Lauren design and other related documents and required the selected subcontractor to perform in accordance with the 85% complete Lauren design, that the Lauren design could be relied on for accuracy, and the selected subcontractor only had to complete the unfinished parts. Fluor Federal Solutions, LLC (“Fluor”) submitted a request for information (“RFI”) asking BAE about the standards referenced in the SOW.  Fluor was unable to determine the completeness of the Lauren design but relied on BAE’s assertion that the design was 85% complete. BAE rejected Fluor’s initial bid as being too high given what BAE had already paid Lauren for its design and told Fluor to lower its bid because the design was close to complete. Fluor lowered its price and submitted another bid proposal that outlined a firm-fixed-price design/build that forecasted 32 months to complete the NC Project. BAE awarded Fluor an Undefinitized Contract Action (“UCA”) in the amount of $9 million dollars, later increased to $32 million. Under the UCA, Fluor began procuring materials and physical construction before a formal subcontract was agreed upon. On December 17, 2015, BAE and Fluor agreed to a fixed-price design and build subcontract (the “Subcontract”) in which Fluor agreed to design, construct, and partially commission the NC Project for $245,690,422.00, which included money spent already in the UCA. When this litigation began, Fluor was scheduled to complete its work by December 2020, 2.5 years beyond the originally agreed-upon completion date.

On September 30, 2020, BAE sued Fluor for breach of contract. On May 24, 2021, Fluor counterclaimed for breach of contract, quantum meruit, and unjust enrichment. Fluor’s counterclaim alleged that Fluor was not at fault for failing to meet the agreed-upon schedule and Fluor had $183 million in outstanding change proposals when the litigation was filed.

Continue reading Motions to Dismiss, Limitations of Liability, and More

Exit mobile version