BCS Software, LLC v. HPE, Inc.

6:20-cv-00708 W.D. Tex. Closed

Infringement action filed 2 Aug 2020 in the United States District Court for the Western District of Texas, asserting 3 patents titled “High level operational support system” (US7890809B2, US7533301B2 and US7302612B2). The case closed 12 Aug 2020. Product listed in the record: HPE Intelligent Management Center Enterprise Software Platform.

View the 3 asserted patents in Patsnap Eureka Claims, drawings and current legal status

Case summary

Plaintiff
BCS Software, LLC
Defendant
HPE, Inc.
Patents asserted
US7890809B2“High level operational support system”US7533301B2“High level operational support system”US7302612B2“High level operational support system”
Products listed
HPE Intelligent Management Center Enterprise Software Platform
Court
W.D. Tex.
Verdict cause
Infringement action
Filed
2 Aug 2020
Closed
12 Aug 2020 (10 days)
Recorded category
Voluntary dismissal
Judge
Alan D Albright
Case no.
6:20-cv-00708
Counsel of record · 1 attorney, 1 firm
  • Raymond W. Mort III, plaintiff counsel
  • Plaintiff firm: The Mort Law Firm PLLC
Source: Patsnap Litigation Data. Party, attorney and judge names are shown with standard capitalization; products and categories appear as recorded in the docket. Patent titles from Patsnap patent data.
Closing order

How the case ended

The case record does not include the text of the closing order.

The patents in this case. Read the full claims of all 3 asserted patents. Open in Patsnap Eureka
Before you launch

Check your product against patent claims

FTO Search in Patsnap Eureka finds patent claims relevant to your product’s technical features, so you can review them before launch.

Run an FTO Search
Monthly newsletter

Need a monthly report on closed US patent cases?

Every case that closed last month, with the court, the outcome and the patents involved.

Docket fields sourced from PACER via Patsnap Litigation Data. Patent bibliographic data from Patsnap.

Next step

Go further with this record

Read how the method works, run it on your own product, then size the next step.

  • 01 / How-toUsing patent search for competitive intelligenceRead a rival's filings to see where its products are going.GuideRead
  • 02 / AI agentFTO ReportCheck whether your own product could read on these claims.Patsnap EurekaRun it
  • 03 / Free toolAI prior art searchDescribe an idea, get the closest patents.AI resultTry tool

More next stepsHow to run a freedom-to-operate analysis

General information only. This page reproduces publicly available court docket data for case 6:20-cv-00708 and is provided for general information and reference only. It is not legal advice and must not be relied upon as such. It does not create an attorney-client relationship.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.