FrameTech, LLC v. BMC Software: Federal Court Dismisses Mainframe Patent Claims with Prejudice

📄 View Full Report 📥 Export PDF 🔗 Share ⭐ Save

📋 Case Summary

Case Name FrameTech, LLC v. BMC Software, Inc.
Case Number 4:23-cv-03837
Court U.S. District Court for the Southern District of Texas
Duration Oct 2023 – Sep 2025 719 days
Outcome Defendant Win – Dismissed with Prejudice
Patents at Issue
Accused Products BMC Software’s mainframe computer setup automation tools

Case Overview

In a decisive ruling from the Southern District of Texas, Chief Judge Alfred H. Bennett dismissed all patent infringement claims filed by FrameTech, LLC against enterprise software giant BMC Software, Inc. — with prejudice — following the court’s grant of BMC Software’s Amended Motion for Judgment on the Pleadings. The case, FrameTech, LLC v. BMC Software, Inc. (Case No. 4:23-cv-03837), centered on U.S. Patent No. 7,194,737 B2, covering a system and method for expediting and automating mainframe computer setup.

Filed on October 11, 2023, and closed on September 29, 2025, the litigation ran 719 days before concluding without trial. For patent attorneys evaluating non-practicing entity (NPE) assertion strategies, IP professionals monitoring mainframe software patent litigation, and R&D teams developing enterprise automation systems, this outcome carries important strategic lessons about early-stage dismissal risk, pleading standards, and the growing potency of Rule 12(c) motions in patent cases.

The Parties

⚖️ Plaintiff

A patent-holding plaintiff whose litigation activities focus on asserting patent rights, a profile consistent with NPE or patent assertion entity (PAE) operations.

🛡️ Defendant

Global leader in enterprise IT management solutions, with deep roots in mainframe software, IT operations, and automation platforms.

The Patent at Issue

This case involved U.S. Patent No. 7,194,737 B2, covering a system and method for expediting and automating mainframe computer setup. The patent focuses on procedural automation in mainframe configuration workflows, a domain directly relevant to BMC Software’s core product portfolio.

  • US 7,194,737 B2 — System and method for expediting and automating mainframe computer setup
🔍

Developing automation software?

Check if your product might infringe this or related patents in mainframe technology.

Run FTO Check →

Litigation Timeline & Procedural History

FrameTech filed suit on October 11, 2023, in the U.S. District Court for the Southern District of Texas — a venue that, while less frequented than the Western District of Texas for patent cases, remains within the broader Texas patent litigation ecosystem. The case was assigned to Chief Judge Alfred H. Bennett.

The litigation’s most pivotal procedural event was BMC Software’s filing of an Amended Motion for Judgment on the Pleadings (Doc. #36) pursuant to Federal Rule of Civil Procedure 12(c). Rather than proceeding through costly fact discovery, claim construction (Markman hearings), or trial, BMC Software successfully argued for termination at the pleadings stage.

The court issued its ruling granting the motion simultaneously with its Final Judgment, entered on September 29, 2025 — 719 days after filing. While nearly two years may appear lengthy for a pleadings-stage resolution, the timeline reflects typical docketing and briefing schedules in the Southern District of Texas, and the case never advanced to full merits discovery or trial.

The Verdict & Legal Analysis

Outcome

The court entered Final Judgment dismissing all of FrameTech’s claims with prejudice, pursuant to Federal Rule of Civil Procedure 58. A dismissal with prejudice is the most complete form of termination for a defendant — it bars FrameTech from re-filing the same claims against BMC Software. No damages were awarded, and no injunctive relief was issued. The specific damages sought by FrameTech were not publicly disclosed in the case record.

Verdict Cause Analysis: Judgment on the Pleadings Under Rule 12(c)

The mechanism of termination — judgment on the pleadings — is legally significant. A Rule 12(c) motion tests whether, accepting all well-pleaded facts as true, the plaintiff has stated a plausible claim for relief. In patent cases, this vehicle is increasingly used to challenge infringement claims on two principal grounds:

  1. Patent ineligibility under 35 U.S.C. § 101 (Alice/Mayo framework), which scrutinizes whether claims are directed to abstract ideas or natural phenomena without a sufficient inventive concept
  2. Failure to plausibly plead infringement — insufficient specificity in mapping accused products to patent claims

The technology at issue — mainframe computer setup automation — sits in a space where § 101 challenges have gained significant traction. Courts have consistently examined whether software-implemented process patents claim little more than generic computer implementation of abstract organizational or administrative methods, particularly post-Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014).

Legal Significance

This ruling reinforces the viability of early-stage Rule 12(c) dismissal as a cost-effective defense tool against software patent assertions. For the Southern District of Texas, the outcome demonstrates judicial willingness to resolve patent cases at the pleadings stage when the legal deficiencies are sufficiently clear.

The dismissal with prejudice — rather than without prejudice allowing amendment — signals the court found no viable path forward for FrameTech’s claims, lending persuasive weight to this decision in analogous mainframe or enterprise software patent matters.

Strategic Takeaways

For Patent Holders and Assertion Entities:

  • Complaint-drafting quality is critical. Courts applying Iqbal/Twombly pleading standards in patent cases require more than conclusory infringement allegations — detailed claim-product mapping strengthens survivability against Rule 12(c) motions
  • Software and automation patents remain vulnerable to § 101 challenges; pre-litigation validity assessment should stress-test claims against the Alice two-step framework

For Accused Infringers:

  • An amended Rule 12(c) motion proved decisive here — iterating on initial motion practice to sharpen legal arguments is a legitimate and effective strategy
  • Engaging Am Law 100 patent litigation counsel (Winston & Strawn) early to deploy dispositive motions before discovery cost accumulation represents a best-practice defense model

For R&D and Legal Teams:

  • Mainframe automation and enterprise IT configuration software remain active assertion targets. Freedom-to-operate (FTO) analyses should include aged software patents (U.S. 7,194,737 B2 issued in the mid-2000s) that may still carry assertion risk
  • Monitor NPE litigation patterns in the Southern District of Texas as an emerging venue for enterprise software patent disputes
✍️

Filing a software patent?

Learn from this case. Use AI to draft stronger claims that can withstand litigation.

Try Patent Drafting →

Power Your Patent Strategy with PatSnap Eureka IP

From novelty searches to patent drafting, PatSnap Eureka’s AI-powered tools help you navigate the patent landscape with confidence.

⚠️ Freedom to Operate (FTO) Analysis

This case highlights critical IP risks in mainframe automation design. Choose your next step:

📋 Understand This Case’s Impact

Learn about the specific risks and implications from this litigation.

  • View related patents in mainframe automation
  • See which companies are active in enterprise software IP
  • Understand § 101 claim construction patterns
📊 View Patent Landscape
⚠️
High Risk Area

Software-implemented process patents (especially older ones)

📋
1 Patent at Issue

US 7,194,737 B2 for mainframe setup automation

Design-Around Options

Possible, but challenging for core functionalities

✅ Key Takeaways

For Patent Attorneys & Litigators

Rule 12(c) judgment on the pleadings remains a powerful, cost-efficient tool against software patent assertions — particularly where § 101 vulnerability is apparent.

Search related case law →

Pleading specificity for infringement is crucial; detailed claim-product mapping strengthens survivability against Rule 12(c) motions.

Explore precedents →

For R&D Teams & IP Professionals

FTO clearance for mainframe automation and IT configuration products should account for legacy software patents from the early-to-mid 2000s.

Start FTO analysis for my product →

Rigorous claim drafting and prosecution strategies are essential to ensure software patents contain sufficient inventive concepts to withstand pleadings-stage challenges.

Try AI patent drafting →

Ready to Strengthen Your Patent Strategy?

Join thousands of IP professionals using PatSnap Eureka to conduct prior art searches, draft patents, and analyze competitive landscapes.

⚖️ Disclaimer: This article is for informational purposes only and does not constitute legal advice. The analysis presented reflects publicly available case information and general legal principles. For specific advice regarding patent litigation, FTO analysis, or IP strategy, please consult a qualified patent attorney.