Railware v. SEPTA: Four Railway Network Patents Settled With Prejudice
Railware, Inc. accused the Southeastern Pennsylvania Transportation Authority of infringing four patents covering its RailwayNet SM and AIM railway management system. Filed in the Eastern District of Pennsylvania in July 2024, the case reached a confidential settlement and was dismissed with prejudice after 350 days, with each party bearing its own costs.
Transit Authority’s Railway Software Use Triggers Four-Patent Claim
Railware, Inc. filed suit against the Southeastern Pennsylvania Transportation Authority (SEPTA) on 8 July 2024 in the Eastern District of Pennsylvania before Judge John M. Younge. Railware alleged that SEPTA’s implementation of the RailwayNet SM system, its AIM system, and/or substantially similar systems infringed four Railware patents — US9403545B2, USRE049115E, USRE047835E, and US9517782B2 — covering railway network management and control technology.
The parties reached a confidential settlement and filed a joint stipulation of dismissal under Fed. R. Civ. P. 41(a)(1)(A)(ii) on 23 June 2025, dismissing all claims and counterclaims with prejudice. Each party was responsible for its own legal costs, suggesting neither side extracted a fee-shifting concession. The with-prejudice designation means Railware is permanently barred from re-filing the same infringement claims against SEPTA on these patents.
The 350-day arc from filing to settlement is relatively compressed for a four-patent district court action, suggesting the parties may have reached commercial alignment before protracted claim construction or summary judgment proceedings. The financial terms of any licence or lump-sum arrangement remain undisclosed. What the public record cannot reveal is whether SEPTA obtained a licence to continue using the accused systems or agreed to migrate away from them entirely.
Filing to Dismissed with Prejudice in 350 days
350 days — relatively swift resolution for a multi-patent district court infringement action
Settled with prejudice: what the joint dismissal means for both parties
Rule 41(a)(1)(A)(ii): joint stipulation of dismissal with prejudice
Under Fed. R. Civ. P. 41(a)(1)(A)(ii), both parties signed a stipulation dismissing all claims and counterclaims with prejudice. ‘With prejudice’ is the critical qualifier: it operates as a final adjudication on the merits, permanently extinguishing Railware’s right to refile these specific infringement claims against SEPTA. No court order on the merits was required — the parties’ agreement alone closed the case.
Permanent bar on refilingRailware exits with prejudice — likely extracted commercial value
Railware voluntarily agreed to dismiss with prejudice, which typically signals it received satisfactory consideration — whether a licence fee, ongoing royalty, or product discontinuation commitment from SEPTA. The patents themselves remain in force and enforceable against third parties. Railware retains the ability to pursue infringement actions against other transit agencies or rail operators using equivalent systems.
Patents remain enforceableSEPTA avoids merits ruling — future exposure depends on settlement terms
SEPTA secured a with-prejudice dismissal without any court finding of infringement or validity — a commercially clean exit from the litigation record. However, because no invalidity ruling was obtained, all four Railware patents survive fully enforceable. SEPTA’s ongoing exposure depends entirely on undisclosed settlement terms: a licence would provide protection; any other arrangement may not.
No invalidity ruling obtainedOther transit agencies using comparable systems face unresolved patent risk
Settlement without a merits ruling leaves Railware’s four patents validated in the marketplace. Other transit authorities or rail operators deploying functionally equivalent railway network management or asset information management (AIM) systems remain exposed to the same infringement theories. The rapid settlement may embolden Railware to pursue additional targets, consistent with a licensing-focused enforcement strategy.
Enforcement risk for comparable systemsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | RAILWARE, INC. | Company | Railway network software developer — holder of US9403545B2 and three related patentsSearch in Eureka ↗ |
| Defendant | SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITY | Individual | Southeastern Pennsylvania Transportation Authority — regional public transit operator accused of infringing railway management software patentsSearch in Eureka ↗ |
| Plaintiff counsel | BRYAN J. VOGEL | Attorney | Counsel for RAILWARE, INC.Search in Eureka ↗ |
| Plaintiff counsel | DERRICK J. CARMAN | Attorney | Counsel for RAILWARE, INC.Search in Eureka ↗ |
| Plaintiff counsel | JOE H. TUCKER , JR. | Attorney | Counsel for RAILWARE, INC.Search in Eureka ↗ |
| Plaintiff counsel | TRAVIS K. WALLER | Attorney | Counsel for RAILWARE, INC.Search in Eureka ↗ |
| Plaintiff law firm | Robins Kaplan, LLP | Law Firm | Representing RAILWARE, INC.Search in Eureka ↗ |
| Plaintiff law firm | TUCKER LAW GROUP | Law Firm | Representing RAILWARE, INC.Search in Eureka ↗ |
| Defendant counsel | Aleksander J. Goranin | Attorney | Counsel for SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITYSearch in Eureka ↗ |
| Defendant counsel | CHRISTOPHER RICCIUTI | Attorney | Counsel for SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITYSearch in Eureka ↗ |
| Defendant counsel | LEIGH MICHAEL SKIPPER | Attorney | Counsel for SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITYSearch in Eureka ↗ |
| Defendant counsel | Richard Hughes | Attorney | Counsel for SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITYSearch in Eureka ↗ |
| Defendant law firm | Duane Morris, LLP | Law Firm | Representing SOUTHEASTERN PENNSYLVANIA TRANSPORTATION AUTHORITYSearch in Eureka ↗ |
| Presiding judge | Judge JOHN M. YOUNGE | Judge | Pennsylvania Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The joint stipulation invokes Rule 41(a)(1)(A)(ii), the standard procedural vehicle for bilateral settlement dismissals at the district court level. The phrase ‘all pending claims and counterclaims’ confirms SEPTA had filed counterclaims — likely invalidity and non-infringement defences — which are also extinguished with prejudice. The parties’ explicit inclusion of mutual cost-bearing language in the stipulation itself is unusual and suggests the fee allocation was a negotiated term, not an afterthought.
US9403545B2 and three related patents — railway network management systems
The four asserted patents — US9403545B2, USRE049115E, USRE047835E, and US9517782B2 — cover Railware’s RailwayNet SM platform and related railway asset and information management (AIM) technology. Two of the four are reissue patents, which typically indicates the original claims were broadened or corrected post-grant to better capture the commercial embodiment or competitor implementations. Application dates across the portfolio span multiple filing windows, suggesting a layered continuation and reissue strategy.
For the rail technology sector, this portfolio represents a meaningful enforcement risk precisely because AIM-type systems are widely deployed across transit authorities for operations management, scheduling, and asset tracking. Railware’s decision to assert two reissue patents alongside two original grants signals a deliberate effort to maximise claim breadth. Competitors and licensees operating any functionally equivalent railway network management platform should treat this portfolio as actively enforced and potentially design-around-resistant given the reissue history.
Should you run an FTO against US9403545B2 and the Railware portfolio?
Any transit authority, rail operator, or software vendor deploying railway network management, AIM, or operationally equivalent systems should assess exposure against Railware’s four-patent portfolio. The SEPTA case demonstrates that Railware will pursue institutional and government-adjacent operators. The presence of reissue patents in the portfolio means claim scope may be broader than the original filings suggest — standard keyword searches may underestimate coverage.
PatSnap Eureka’s FTO Search Agent can map the claim landscape across all four Railware patents simultaneously, identify prior art that may support IPR or PGR petitions against the reissue patents, and flag functionally similar claim language in competing filings. For procurement teams evaluating AIM vendors, Eureka can also benchmark whether vendor patents conflict with or design around this portfolio before contract award.
Run a freedom-to-operate analysis on US9403545B2 to assess your product’s exposure
Run FTO in Eureka →Similar Railway Software Patent Infringement Cases in U.S. District Courts
Cases involving railway network management and transit software patents litigated in U.S. district courts, including comparable multi-patent enforcement and settlement patterns.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable SEPTA’s implementation of the RailwayNetSM system/AIM system and/or other same or similar system-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedRAILWARE, INC.’s broader IP enforcement history
RAILWARE, INC.’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the railway software IP landscape
A four-patent settlement in under a year against a major public transit authority signals active monetisation of railway network management IP.
With-prejudice settlement preserves Railware’s enforcement options against others
Dismissing with prejudice protects SEPTA but leaves all four patents fully intact. Transit agencies and rail software vendors operating comparable RailwayNet-type or AIM-type systems should treat this settlement as a market signal: Railware has demonstrated willingness and capacity to litigate against institutional defendants.
No fee-shifting indicates a balanced negotiation — not a clear winner
The mutual cost-bearing provision suggests neither party achieved the kind of decisive leverage that typically produces fee-shifting. This is consistent with a negotiated licence or commercial resolution rather than a capitulation by either side. The absence of an exceptional case finding also means the patent’s validity was never tested in court.
Four-patent portfolio structure raises claim construction complexity for future defendants
With two reissue patents (USRE049115E and USRE047835E) alongside two original grants, future defendants face broadened claim scope risks. Reissue patents can recapture claim scope, increasing the difficulty of designing around or invalidating the portfolio through IPR.
Public procurement systems may be next enforcement targets — FTO review is urgent
SEPTA is one of the largest transit authorities in the US. Railware’s willingness to sue a government-adjacent entity suggests enforcement is not limited to private operators. Other publicly-funded transit systems deploying AIM or comparable railway asset management platforms should conduct FTO analysis against this portfolio immediately.
RAILWARE v SOUTHEASTERN — key questions answered
Railware asserted four patents: US9403545B2, USRE049115E, USRE047835E, and US9517782B2. Two are reissue patents, indicating broadened post-grant claims. All four cover railway network management and asset information management (AIM) technology associated with Railware’s RailwayNet SM platform.
The case was dismissed with prejudice by joint stipulation under Fed. R. Civ. P. 41(a)(1)(A)(ii) on 23 June 2025, following a confidential settlement. Each party agreed to bear its own costs and attorneys’ fees. No court ruling on the merits of infringement or validity was issued.
For SEPTA, dismissal with prejudice means Railware cannot refile the same infringement claims based on these patents for the same accused conduct. For Railware, it signals the company likely received commercial consideration — licence fees or other value — in exchange for permanently releasing its claims against SEPTA. The four patents remain enforceable against other parties.
Yes. Reissue patents are granted when the USPTO allows correction or broadening of original claims, which can make designing around them more difficult. Other transit agencies or rail software vendors deploying AIM or equivalent railway network management systems should conduct FTO analysis specifically against the reissued claims, as they may cover a wider range of implementations than the original grants.
Railware was represented by Robins Kaplan, LLP and Tucker Law Group, with attorneys Bryan J. Vogel, Derrick J. Carman, Joe H. Tucker Jr., and Travis K. Waller. SEPTA was represented by Duane Morris, LLP, with attorneys Aleksander J. Goranin, Christopher Ricciuti, Leigh Michael Skipper, and Richard Hughes.
Track railway software patent enforcement before your next procurement decision
Railware’s four-patent portfolio remains fully enforceable following the SEPTA settlement. Use PatSnap Eureka to run FTO searches against railway AIM and network management systems and monitor new enforcement actions before they affect your contracts.
PatSnap Eureka searches patents and litigation data to answer instantly.