Data Center, +4
Technology
Loading
Technology
9 min read
Areas of Expertise :
Software, Software Development, Information Systems, Information Technology, Project Management, Manufacturing, Breach Of Contract, Economic Damages

Published Date:
Last Modified Date:
Jurisdiction:
Texas State
International Business Machines Corp. v. Lufkin Industries, Inc., 564 S.W.3d 15 (Tex. App.—Tyler 2017), involved a software implementation dispute between International Business Machines Corporation (IBM) and Lufkin Industries, a Texas-based industrial equipment manufacturer. In March 2010, Lufkin entered into a Statement of Work (SOW) with IBM to implement IBM's Express Solution for SAP as a replacement for its aging enterprise resource planning (ERP) system. The new system was intended to support manufacturing, inventory, payroll, and financial operations. After repeated testing failures and implementation delays, the software went live on January 1, 2012, but experienced serious operational problems. Lufkin sued IBM in the 159th District Court of Angelina County, Texas, alleging fraudulent inducement, common-law fraud, negligent misrepresentation, and breach of contract. Expert testimony addressed SAP functionality, implementation deficiencies, system valuation, data conversion, and financial damages.
A jury awarded Lufkin $21 million for fraudulent inducement, but the Texas Supreme Court overturned that recovery in 2019 because Lufkin had contractually disclaimed reliance on IBM's representations. Although the court determined that IBM's contractual breach caused some damages, it ordered a new trial to address breach-of-contract liability and the amount recoverable. The litigation continued until April 2021, when the parties reached a confidential settlement.
Lufkin Industries began searching for a replacement for its outdated ERP system to support manufacturing operations and anticipated business growth. IBM proposed its Express Solution for SAP, representing that approximately 80% of the software was preconfigured and could satisfy Lufkin's requirements with limited customization. On September 30, 2009, IBM employee Juan Gonzalez demonstrated software that IBM presented as showing the proposed system's capabilities, with assistance from SAP. Evidence presented during litigation showed that the Express Solution had been designed for substantially smaller businesses and required extensive modifications to accommodate Lufkin's operations, which included 56 plants, nine company codes, and approximately 650 users.
IBM and Lufkin executed a Statement of Work defining the project's implementation requirements, responsibilities, and anticipated completion schedule. The agreement projected March 1, 2011, as the date when Lufkin would begin operating its new ERP system. Its contractual provisions also disclaimed Lufkin's reliance on representations outside the written agreement. As implementation difficulties emerged, the parties modified their arrangement through nine Project Change Requests (PCRs), extending the deployment schedule and increasing project costs.
The ERP system failed its first integration test in November 2010, followed by another unsuccessful test in February 2011. IBM proposed extending the implementation deadline to June 1, 2011, and increasing its fees by $2.6 million, but the revised deadline passed without an operational system. A June 2011 change request added more than $4 million to IBM's fees, while further testing in September and November revealed continuing technical problems. By the end of 2011, Lufkin had executed nine PCRs and paid IBM $12,983,736 for the implementation. Despite the unresolved deficiencies, the parties proceeded with plans to deploy the system in January 2012.
Lufkin deactivated its previous business management system and launched IBM's Express Solution on January 1, 2012, in a deployment described as "Go-Live Ugly." Problems emerged across payroll calculations, vendor payments, inventory management, manufacturing activities, and customer shipments. Employees performed several business functions manually, and system failures prevented the company from closing its accounting records for January, February, and March 2012. Lufkin disclosed the implementation problems in its public financial reporting, and its stock price declined during the period. Operational difficulties continued through much of the first half of 2012.
After approximately six months of operating with a largely nonfunctional ERP system, Lufkin sought assistance from IBM and SAP to assess the continuing implementation problems. IBM sent a representative who lacked authority to take corrective action, while SAP began evaluating how the software could be reconfigured to support Lufkin's operations. Lufkin subsequently worked with SAP and outside consultants for approximately 18 months to correct deficiencies and develop a functioning system. According to the appellate record, Lufkin paid $7,544,545 to third-party consultants for remediation work performed after the January 2012 deployment.
Lufkin filed suit against IBM in the 159th District Court of Angelina County, Texas, asserting claims for fraudulent inducement, common-law fraud, negligent misrepresentation, and breach of contract. The jury trial began on May 5, 2015, and concluded with a May 22 verdict awarding $10 million in out-of-pocket damages and $11 million in mitigation expenses for fraudulent inducement. Jurors also found that IBM breached the implementation agreement and made negligent misrepresentations, but awarded no damages for either claim. A separate $6 million award for common-law fraud was treated by the trial court as an alternative recovery. On September 10, 2015, the court entered judgment for $23,776,025.10, comprising $21 million in fraudulent-inducement damages and $2,776,025.10 in prejudgment interest, after which IBM appealed to the Texas Twelfth Court of Appeals in Tyler.
The Texas Twelfth Court of Appeals considered IBM's challenges to the fraudulent-inducement verdict and the financial evidence supporting Lufkin's recovery. Although the court upheld the fraudulent-inducement finding, it determined that the record did not support the entire $11 million mitigation award. The evidence established $7,544,545 in third-party remediation expenses, but the court rejected additional employee salary calculations because they did not adequately demonstrate compensable financial losses. It also reversed the alternative $6 million common-law fraud recovery because that claim involved the same alleged misrepresentations and injuries as the fraudulent-inducement claim. The court proposed a $3,455,455 reduction in mitigation damages, subject to Lufkin's acceptance.
After Lufkin accepted the proposed reduction, the Texas Twelfth Court of Appeals issued a supplemental memorandum opinion modifying the trial court's judgment. The revised award consisted of $10 million in out-of-pocket damages and $7,544,545 in mitigation expenses, totaling $17,544,545 in actual damages. The court recalculated prejudgment interest at $2,319,244.65 and reported a total appellate judgment of $19,863,789.60. IBM subsequently sought review from the Texas Supreme Court, challenging the fraud recovery and the legal effect of the contractual reliance disclaimers.
In International Business Machines Corp. v. Lufkin Industries, LLC, 573 S.W.3d 224 (Tex. 2019), the Texas Supreme Court examined whether Lufkin could recover for alleged misrepresentations despite the reliance disclaimers in the parties' contractual documents. The court held that those provisions barred Lufkin's fraudulent-inducement and related fraud claims, including claims involving representations made during subsequent contract modifications. It separately concluded that the evidence conclusively established that IBM's contractual breach caused Lufkin some damages, despite the jury's zero-damages finding on the breach-of-contract claim. However, the evidence did not conclusively establish the amount recoverable under the contract. Because IBM continued to dispute contractual liability, the court reversed the fraudulent-inducement recovery and remanded the breach-of-contract claim for a new trial on liability and damages.
Following remand, IBM challenged Lufkin's proposed breach-of-contract damages through a motion for summary judgment. The trial court denied the motion and authorized IBM to seek a permissive interlocutory appeal, which allows certain legal questions to be reviewed before final judgment. IBM filed its petition on November 2, 2020, requesting appellate review of disputed damages theories involving contractual recovery limits, incremental-value damages, and employee costs. On November 18, 2020, the Texas Twelfth Court of Appeals dismissed the petition for lack of jurisdiction because the trial court's order did not contain the substantive legal rulings required for permissive appellate review. The dismissal left the merits of the disputed damages theories unresolved.
On April 5, 2021, IBM filed a motion with the Texas Supreme Court stating that the parties had entered into a settlement agreement and requesting dismissal of its pending petition for review. The filing specified that IBM and Lufkin had agreed to bear their respective attorney's fees and costs. Law360 reported the confidential settlement on April 6, 2021, following years of litigation over the ERP implementation and related damages claims. On April 9, 2021, the Texas Supreme Court granted the motion and dismissed IBM's petition for review. The settlement amount and other financial terms were not publicly disclosed.
Court:
Supreme Court of Texas
Case Name:
International Business Machines Corp. v. Lufkin Industries, Inc.
In March 2010, Lufkin Industries contracted with IBM to implement an SAP-based enterprise resource planning (ERP) system. The system went live on January 1, 2012, but experienced serious problems affecting payroll, inventory, manufacturing, and financial operations.
Lufkin sued IBM for fraudulent inducement, fraud, negligent misrepresentation, and breach of contract, alleging that IBM misrepresented the software's capabilities and failed to deliver a system that met its business requirements.
Expert witnesses Hanif Sarangi, Mohan Rao, and Rosemary Lee testified about SAP implementation deficiencies, software valuation, financial damages, project blueprinting, and data conversion.
In 2015, a jury awarded Lufkin $21 million for fraudulent inducement. The Texas Supreme Court overturned the award in 2019 because of enforceable contractual disclaimers of reliance and ordered a new trial on breach-of-contract liability and damages.
IBM and Lufkin reached a confidential settlement in April 2021. The Texas Supreme Court dismissed IBM's pending petition for review, and the settlement amount was not publicly disclosed.
Enterprise Software
Sap software
Application Integration
Business Process Automation
Contract Disputes
Software Valuation
Damages Calculations
Transaction Processing Software
International Business Machines Corp. v. Lufkin Industries, Inc., 564 S.W.3d 15 (Tex. App.—Tyler 2017), involved a software implementation dispute between International Business Machines Corporation (IBM) and Lufkin Industries, a Texas-based industrial equipment manufacturer. In March 2010, Lufkin entered into a Statement of Work (SOW) with IBM to implement IBM's Express Solution for SAP as a replacement for its aging enterprise resource planning (ERP) system. The new system was intended to support manufacturing, inventory, payroll, and financial operations. After repeated testing failures and implementation delays, the software went live on January 1, 2012, but experienced serious operational problems. Lufkin sued IBM in the 159th District Court of Angelina County, Texas, alleging fraudulent inducement, common-law fraud, negligent misrepresentation, and breach of contract. Expert testimony addressed SAP functionality, implementation deficiencies, system valuation, data conversion, and financial damages.
A jury awarded Lufkin $21 million for fraudulent inducement, but the Texas Supreme Court overturned that recovery in 2019 because Lufkin had contractually disclaimed reliance on IBM's representations. Although the court determined that IBM's contractual breach caused some damages, it ordered a new trial to address breach-of-contract liability and the amount recoverable. The litigation continued until April 2021, when the parties reached a confidential settlement.
Lufkin Industries began searching for a replacement for its outdated ERP system to support manufacturing operations and anticipated business growth. IBM proposed its Express Solution for SAP, representing that approximately 80% of the software was preconfigured and could satisfy Lufkin's requirements with limited customization. On September 30, 2009, IBM employee Juan Gonzalez demonstrated software that IBM presented as showing the proposed system's capabilities, with assistance from SAP. Evidence presented during litigation showed that the Express Solution had been designed for substantially smaller businesses and required extensive modifications to accommodate Lufkin's operations, which included 56 plants, nine company codes, and approximately 650 users.
IBM and Lufkin executed a Statement of Work defining the project's implementation requirements, responsibilities, and anticipated completion schedule. The agreement projected March 1, 2011, as the date when Lufkin would begin operating its new ERP system. Its contractual provisions also disclaimed Lufkin's reliance on representations outside the written agreement. As implementation difficulties emerged, the parties modified their arrangement through nine Project Change Requests (PCRs), extending the deployment schedule and increasing project costs.
The ERP system failed its first integration test in November 2010, followed by another unsuccessful test in February 2011. IBM proposed extending the implementation deadline to June 1, 2011, and increasing its fees by $2.6 million, but the revised deadline passed without an operational system. A June 2011 change request added more than $4 million to IBM's fees, while further testing in September and November revealed continuing technical problems. By the end of 2011, Lufkin had executed nine PCRs and paid IBM $12,983,736 for the implementation. Despite the unresolved deficiencies, the parties proceeded with plans to deploy the system in January 2012.
Lufkin deactivated its previous business management system and launched IBM's Express Solution on January 1, 2012, in a deployment described as "Go-Live Ugly." Problems emerged across payroll calculations, vendor payments, inventory management, manufacturing activities, and customer shipments. Employees performed several business functions manually, and system failures prevented the company from closing its accounting records for January, February, and March 2012. Lufkin disclosed the implementation problems in its public financial reporting, and its stock price declined during the period. Operational difficulties continued through much of the first half of 2012.
After approximately six months of operating with a largely nonfunctional ERP system, Lufkin sought assistance from IBM and SAP to assess the continuing implementation problems. IBM sent a representative who lacked authority to take corrective action, while SAP began evaluating how the software could be reconfigured to support Lufkin's operations. Lufkin subsequently worked with SAP and outside consultants for approximately 18 months to correct deficiencies and develop a functioning system. According to the appellate record, Lufkin paid $7,544,545 to third-party consultants for remediation work performed after the January 2012 deployment.
Lufkin filed suit against IBM in the 159th District Court of Angelina County, Texas, asserting claims for fraudulent inducement, common-law fraud, negligent misrepresentation, and breach of contract. The jury trial began on May 5, 2015, and concluded with a May 22 verdict awarding $10 million in out-of-pocket damages and $11 million in mitigation expenses for fraudulent inducement. Jurors also found that IBM breached the implementation agreement and made negligent misrepresentations, but awarded no damages for either claim. A separate $6 million award for common-law fraud was treated by the trial court as an alternative recovery. On September 10, 2015, the court entered judgment for $23,776,025.10, comprising $21 million in fraudulent-inducement damages and $2,776,025.10 in prejudgment interest, after which IBM appealed to the Texas Twelfth Court of Appeals in Tyler.
The Texas Twelfth Court of Appeals considered IBM's challenges to the fraudulent-inducement verdict and the financial evidence supporting Lufkin's recovery. Although the court upheld the fraudulent-inducement finding, it determined that the record did not support the entire $11 million mitigation award. The evidence established $7,544,545 in third-party remediation expenses, but the court rejected additional employee salary calculations because they did not adequately demonstrate compensable financial losses. It also reversed the alternative $6 million common-law fraud recovery because that claim involved the same alleged misrepresentations and injuries as the fraudulent-inducement claim. The court proposed a $3,455,455 reduction in mitigation damages, subject to Lufkin's acceptance.
After Lufkin accepted the proposed reduction, the Texas Twelfth Court of Appeals issued a supplemental memorandum opinion modifying the trial court's judgment. The revised award consisted of $10 million in out-of-pocket damages and $7,544,545 in mitigation expenses, totaling $17,544,545 in actual damages. The court recalculated prejudgment interest at $2,319,244.65 and reported a total appellate judgment of $19,863,789.60. IBM subsequently sought review from the Texas Supreme Court, challenging the fraud recovery and the legal effect of the contractual reliance disclaimers.
In International Business Machines Corp. v. Lufkin Industries, LLC, 573 S.W.3d 224 (Tex. 2019), the Texas Supreme Court examined whether Lufkin could recover for alleged misrepresentations despite the reliance disclaimers in the parties' contractual documents. The court held that those provisions barred Lufkin's fraudulent-inducement and related fraud claims, including claims involving representations made during subsequent contract modifications. It separately concluded that the evidence conclusively established that IBM's contractual breach caused Lufkin some damages, despite the jury's zero-damages finding on the breach-of-contract claim. However, the evidence did not conclusively establish the amount recoverable under the contract. Because IBM continued to dispute contractual liability, the court reversed the fraudulent-inducement recovery and remanded the breach-of-contract claim for a new trial on liability and damages.
Following remand, IBM challenged Lufkin's proposed breach-of-contract damages through a motion for summary judgment. The trial court denied the motion and authorized IBM to seek a permissive interlocutory appeal, which allows certain legal questions to be reviewed before final judgment. IBM filed its petition on November 2, 2020, requesting appellate review of disputed damages theories involving contractual recovery limits, incremental-value damages, and employee costs. On November 18, 2020, the Texas Twelfth Court of Appeals dismissed the petition for lack of jurisdiction because the trial court's order did not contain the substantive legal rulings required for permissive appellate review. The dismissal left the merits of the disputed damages theories unresolved.
On April 5, 2021, IBM filed a motion with the Texas Supreme Court stating that the parties had entered into a settlement agreement and requesting dismissal of its pending petition for review. The filing specified that IBM and Lufkin had agreed to bear their respective attorney's fees and costs. Law360 reported the confidential settlement on April 6, 2021, following years of litigation over the ERP implementation and related damages claims. On April 9, 2021, the Texas Supreme Court granted the motion and dismissed IBM's petition for review. The settlement amount and other financial terms were not publicly disclosed.
SAP Implementation Expert Witness - Hanif Sarangi - Plaintiff
Hanif Sarangi testified as an SAP implementation expert with approximately 23 years of experience and involvement in 60 SAP implementations. After examining IBM's Express Solution, he testified that the implementation met only about 10% of Lufkin's requirements when IBM stopped providing meaningful assistance in mid-2012. His analysis covered software functionality, implementation deficiencies, system valuation, and third-party remediation expenses incurred after deployment.
Software Valuation and Financial Damages Expert Witness - Mohan Rao - Plaintiff
Mohan Rao provided expert testimony concerning the ERP system's value and Lufkin's claimed financial losses. His damages calculations included portions of employee salaries attributed to remediation activities, which the appellate court rejected because those salaries would have been paid in the ordinary course of business. Rao did not adequately establish what other work the employees would have performed or identify additional financial losses resulting from their reassignment.
IT Project Blueprinting and Data Conversion Expert Witness - Rosemary Lee - Plaintiff
Rosemary Lee, an information technology consultant, testified about ERP project blueprinting, system requirements, and data conversion procedures. She identified deficiencies in IBM's implementation planning and explained that Lufkin's data-conversion activities did not cause significant problems following the January 2012 deployment. The Texas Supreme Court discussed her testimony when evaluating IBM's arguments about the causes of the implementation failures and Lufkin's contractual damages.
Information Technology Expert Witness
An Information Technology Expert Witness may assess software implementation practices, system integration failures, IT infrastructure, and compliance with contractual technical requirements. In ERP disputes, this work can involve reviewing project documentation, integration testing records, software configurations, and system performance data to distinguish technical defects from implementation decisions that disrupted business operations.
ERP Implementation Contracts and Project Change Requests
The Statement of Work established IBM's implementation responsibilities and the original deployment schedule, while nine Project Change Requests documented subsequent modifications to the project. The parties' contractual reliance disclaimers became central to the fraud litigation because Lufkin sought recovery based on alleged misrepresentations about the software's capabilities. The Texas Supreme Court applied those provisions when resolving the fraudulent-inducement and related fraud claims, including claims involving later contract modifications.
Software Integration Testing and ERP Deployment Failures
Lufkin's implementation encountered repeated integration testing failures before the January 2012 launch. Once the previous business management system was deactivated, continuing software deficiencies affected several connected operations, including payroll, inventory, manufacturing, and financial reporting. The problems required manual workarounds and an extended remediation effort involving SAP and outside consultants.
Recoverable Damages in Software Implementation Lawsuits
The appellate courts distinguished between evidence of remediation expenditures and calculations that did not adequately establish additional financial loss. In 2017, the Texas Court of Appeals accepted $7,544,545 in third-party remediation expenses while rejecting employee salary allocations that lacked sufficient support. The Texas Supreme Court's later decision removed the fraudulent-inducement recovery but recognized that IBM's contractual breach caused some damages, leaving the amount recoverable under the contract for further proceedings.
Fraudulent Inducement and Contractual Reliance Disclaimers
Under Texas law, clear and enforceable contractual disclaimers of reliance can prevent recovery for fraudulent inducement based on representations outside a written agreement. Courts consider the language of the disclaimer and the circumstances surrounding its execution when determining enforceability. In the IBM-Lufkin litigation, the Texas Supreme Court enforced the parties' reliance disclaimers, preventing recovery on the fraud claims while permitting further proceedings on breach of contract.
Expert Testimony and Evidence in ERP Contract Disputes
Expert testimony in the IBM-Lufkin litigation addressed whether the implemented software met Lufkin's requirements, the causes of system deficiencies, and the financial consequences of remediation. The courts also examined whether damages opinions were supported by evidence of actual expenditures and identifiable losses. The treatment of third-party consultant costs and employee salary allocations reflected the distinction between documented remediation expenses and financial calculations that did not establish additional compensable harm.
The IBM-Lufkin litigation produced different outcomes for the company's fraud and contract claims. The Texas Supreme Court set aside the fraudulent-inducement recovery after enforcing the contractual reliance disclaimers. At the same time, it determined that IBM's breach caused Lufkin some damages, although the amount recoverable under the implementation agreement remained unresolved. The case returned to the trial court for further proceedings on contractual liability and damages.
Those proceedings continued into 2020 before IBM and Lufkin reached a confidential settlement in April 2021. The Texas Supreme Court subsequently dismissed IBM's pending petition for review, bringing the reported appellate proceedings to a close without a publicly disclosed settlement amount or a final judicial determination of the remaining contractual damages.
What caused the dispute between IBM and Lufkin Industries?
The dispute arose from IBM's unsuccessful implementation of an SAP-based ERP system intended to replace Lufkin's aging business management software. Lufkin alleged that IBM misrepresented the system's capabilities and failed to deliver software that met the requirements established in the implementation agreement.
Which expert witnesses testified in the IBM-Lufkin ERP lawsuit?
Hanif Sarangi, Mohan Rao, and Rosemary Lee provided expert testimony concerning SAP implementation, software valuation, financial damages, project blueprinting, and data conversion. Their opinions were discussed in appellate decisions reviewing the implementation deficiencies, the causes of operational problems, and the evidence supporting Lufkin's claimed losses.
How much did the jury initially award Lufkin Industries?
The jury awarded Lufkin $21 million for fraudulent inducement, consisting of $10 million in out-of-pocket damages and $11 million in mitigation expenses. It also awarded $6 million for common-law fraud, which the trial court treated as an alternative recovery. The fraudulent-inducement award was reduced on appeal before the Texas Supreme Court overturned it in 2019.
Can a contractual disclaimer prevent a fraudulent-inducement claim in Texas?
Yes, a clear and enforceable disclaimer of reliance can defeat a fraudulent-inducement claim under Texas law, depending on the contract's language and the circumstances surrounding the agreement. The Texas Supreme Court applied this principle when it ruled that Lufkin could not recover on its fraudulent-inducement and related fraud claims against IBM.
What was the final outcome of IBM v. Lufkin Industries?
SAP Implementation Expert Witness - Hanif Sarangi - Plaintiff
Hanif Sarangi testified as an SAP implementation expert with approximately 23 years of experience and involvement in 60 SAP implementations. After examining IBM's Express Solution, he testified that the implementation met only about 10% of Lufkin's requirements when IBM stopped providing meaningful assistance in mid-2012. His analysis covered software functionality, implementation deficiencies, system valuation, and third-party remediation expenses incurred after deployment.
Software Valuation and Financial Damages Expert Witness - Mohan Rao - Plaintiff
Mohan Rao provided expert testimony concerning the ERP system's value and Lufkin's claimed financial losses. His damages calculations included portions of employee salaries attributed to remediation activities, which the appellate court rejected because those salaries would have been paid in the ordinary course of business. Rao did not adequately establish what other work the employees would have performed or identify additional financial losses resulting from their reassignment.
IT Project Blueprinting and Data Conversion Expert Witness - Rosemary Lee - Plaintiff
Rosemary Lee, an information technology consultant, testified about ERP project blueprinting, system requirements, and data conversion procedures. She identified deficiencies in IBM's implementation planning and explained that Lufkin's data-conversion activities did not cause significant problems following the January 2012 deployment. The Texas Supreme Court discussed her testimony when evaluating IBM's arguments about the causes of the implementation failures and Lufkin's contractual damages.
Information Technology Expert Witness
An Information Technology Expert Witness may assess software implementation practices, system integration failures, IT infrastructure, and compliance with contractual technical requirements. In ERP disputes, this work can involve reviewing project documentation, integration testing records, software configurations, and system performance data to distinguish technical defects from implementation decisions that disrupted business operations.
ERP Implementation Contracts and Project Change Requests
The Statement of Work established IBM's implementation responsibilities and the original deployment schedule, while nine Project Change Requests documented subsequent modifications to the project. The parties' contractual reliance disclaimers became central to the fraud litigation because Lufkin sought recovery based on alleged misrepresentations about the software's capabilities. The Texas Supreme Court applied those provisions when resolving the fraudulent-inducement and related fraud claims, including claims involving later contract modifications.
Software Integration Testing and ERP Deployment Failures
Lufkin's implementation encountered repeated integration testing failures before the January 2012 launch. Once the previous business management system was deactivated, continuing software deficiencies affected several connected operations, including payroll, inventory, manufacturing, and financial reporting. The problems required manual workarounds and an extended remediation effort involving SAP and outside consultants.
Recoverable Damages in Software Implementation Lawsuits
The appellate courts distinguished between evidence of remediation expenditures and calculations that did not adequately establish additional financial loss. In 2017, the Texas Court of Appeals accepted $7,544,545 in third-party remediation expenses while rejecting employee salary allocations that lacked sufficient support. The Texas Supreme Court's later decision removed the fraudulent-inducement recovery but recognized that IBM's contractual breach caused some damages, leaving the amount recoverable under the contract for further proceedings.
Fraudulent Inducement and Contractual Reliance Disclaimers
Under Texas law, clear and enforceable contractual disclaimers of reliance can prevent recovery for fraudulent inducement based on representations outside a written agreement. Courts consider the language of the disclaimer and the circumstances surrounding its execution when determining enforceability. In the IBM-Lufkin litigation, the Texas Supreme Court enforced the parties' reliance disclaimers, preventing recovery on the fraud claims while permitting further proceedings on breach of contract.
Expert Testimony and Evidence in ERP Contract Disputes
Expert testimony in the IBM-Lufkin litigation addressed whether the implemented software met Lufkin's requirements, the causes of system deficiencies, and the financial consequences of remediation. The courts also examined whether damages opinions were supported by evidence of actual expenditures and identifiable losses. The treatment of third-party consultant costs and employee salary allocations reflected the distinction between documented remediation expenses and financial calculations that did not establish additional compensable harm.
The IBM-Lufkin litigation produced different outcomes for the company's fraud and contract claims. The Texas Supreme Court set aside the fraudulent-inducement recovery after enforcing the contractual reliance disclaimers. At the same time, it determined that IBM's breach caused Lufkin some damages, although the amount recoverable under the implementation agreement remained unresolved. The case returned to the trial court for further proceedings on contractual liability and damages.
Those proceedings continued into 2020 before IBM and Lufkin reached a confidential settlement in April 2021. The Texas Supreme Court subsequently dismissed IBM's pending petition for review, bringing the reported appellate proceedings to a close without a publicly disclosed settlement amount or a final judicial determination of the remaining contractual damages.
What caused the dispute between IBM and Lufkin Industries?
The dispute arose from IBM's unsuccessful implementation of an SAP-based ERP system intended to replace Lufkin's aging business management software. Lufkin alleged that IBM misrepresented the system's capabilities and failed to deliver software that met the requirements established in the implementation agreement.
Which expert witnesses testified in the IBM-Lufkin ERP lawsuit?
Hanif Sarangi, Mohan Rao, and Rosemary Lee provided expert testimony concerning SAP implementation, software valuation, financial damages, project blueprinting, and data conversion. Their opinions were discussed in appellate decisions reviewing the implementation deficiencies, the causes of operational problems, and the evidence supporting Lufkin's claimed losses.
How much did the jury initially award Lufkin Industries?
The jury awarded Lufkin $21 million for fraudulent inducement, consisting of $10 million in out-of-pocket damages and $11 million in mitigation expenses. It also awarded $6 million for common-law fraud, which the trial court treated as an alternative recovery. The fraudulent-inducement award was reduced on appeal before the Texas Supreme Court overturned it in 2019.
Can a contractual disclaimer prevent a fraudulent-inducement claim in Texas?
Yes, a clear and enforceable disclaimer of reliance can defeat a fraudulent-inducement claim under Texas law, depending on the contract's language and the circumstances surrounding the agreement. The Texas Supreme Court applied this principle when it ruled that Lufkin could not recover on its fraudulent-inducement and related fraud claims against IBM.
What was the final outcome of IBM v. Lufkin Industries?
IBM and Lufkin reached a confidential settlement in April 2021 after additional proceedings concerning breach-of-contract damages. The Texas Supreme Court dismissed IBM's pending petition for review on April 9, 2021. The settlement amount was not publicly disclosed, and the original fraudulent-inducement judgment did not survive appellate review.
Technology
Patent, +4
Technology
Artificial Intelligence, +4
Technology
IBM and Lufkin reached a confidential settlement in April 2021 after additional proceedings concerning breach-of-contract damages. The Texas Supreme Court dismissed IBM's pending petition for review on April 9, 2021. The settlement amount was not publicly disclosed, and the original fraudulent-inducement judgment did not survive appellate review.