DCT

6:22-cv-00275

Isix IP LLC v. Boomi Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 6:22-cv-00275, W.D. Tex., 03/14/2022
  • Venue Allegations: Venue is alleged to be proper based on Defendants maintaining a regular and established place of business within the district and having committed acts of infringement in the district.
  • Core Dispute: Plaintiff alleges that Defendants' Boomi AtomSphere integration platform infringes a patent related to a modular system for integrating data among heterogeneous computer systems.
  • Technical Context: The technology falls within the domain of Enterprise Application Integration (EAI) and Integration Platform as a Service (iPaaS), a market focused on enabling disparate software applications to communicate and share data.
  • Key Procedural History: The complaint alleges that the technology of the patent-in-suit was successfully commercialized in the early 2000s by a predecessor-in-interest, Darc Corp., which licensed the software to numerous large companies.

Case Timeline

Date Event
1999-10-21 '178 Patent Application Filing Date
2001-10-23 '178 Patent Issue Date
Early 2000s Darc Corp. commercialization of '178 Patent technology
2010 Dell acquires Boomi
2021 Dell sells Boomi
2022-03-14 Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 6,308,178 - "System for Integrating Data Among Heterogenous Systems"

The Invention Explained

  • Problem Addressed: The patent addresses the challenge faced by organizations that use numerous, disparate software applications (e.g., for finance, human resources, shipping). Integrating these systems to share data traditionally required writing custom, inflexible, and expensive software interfaces that were difficult to maintain, particularly when one of the underlying applications was updated '178 Patent, col. 1:13-39 '178 Patent, col. 2:1-8
  • The Patented Solution: The invention proposes a middleware integration system that avoids custom coding by using a modular, configurable approach. It features a central "repository" containing a library of reusable code units called "data elements" that each perform a discrete data manipulation task (e.g., translation, validation) '178 Patent, col. 2:40-45 '178 Patent, Fig. 2 The system uses pre-built "modules" (or "cartridges"), often specific to a destination application, which contain "instruction sets" that chain together various data elements to perform a complete integration task '178 Patent, abstract '178 Patent, col. 6:55-58 An "active component" or "engine" executes these instructions, processing data from a source application and populating it into a destination application '178 Patent, col. 2:56-61
  • Technical Importance: This architecture aimed to significantly reduce the cost and complexity of enterprise integration by replacing bespoke, hard-coded interfaces with a standardized platform of reusable and configurable components '178 Patent, col. 3:11-23

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 of the '178 Patent Compl. ¶23 Compl. ¶36
  • The essential elements of independent claim 1 are:
    • A repository of information relating to source and destination applications, which includes a plurality of "data elements" each capable of performing a discrete operation on data.
    • A first "module" that includes a plurality of "instruction sets," with each instruction activating a data element.
    • An "active component" connected to the repository.
    • The active component having an input to load data from source applications and an output to populate destination applications with processed data.
    • The active component processes the data by activating the data elements according to the instruction sets in the module.
  • The complaint alleges infringement of "one or more asserted claims," suggesting the possibility that other claims may be asserted later Compl. ¶37

III. The Accused Instrumentality

Product Identification

The accused products are "Dell Boomi and the Boomi AtomSphere, which includes the Boomi Atom, the Connector, and the Boomi Integration Platform" Compl. ¶10 Compl. ¶37

Functionality and Market Context

  • The complaint describes the accused Boomi platform as an "integration platform as a service" (iPaaS) that enables customers to connect various cloud-based and on-premise applications without writing code Compl. ¶28
  • The platform allegedly provides "reusable components" for use in integration processes, including APIs, connections, maps, and processes Compl. ¶29 A screenshot from Defendant's documentation defines 'Component' as a 'reusable configuration object[] used in processes' that can be referenced across multiple processes Compl. p. 9
  • The system uses "pre-built connectors to efficiently build integrations" Compl. ¶34 The actual processing work is performed by lightweight, distributable runtime engines called "Atoms" Compl. ¶30 A diagram from Defendant's materials illustrates the problem of disconnected applications and presents the solution as 'Application Integration' using 'Prebuilt connectors for all major apps' Compl. p. 11

IV. Analysis of Infringement Allegations

Claim Chart Summary: '178 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a repository of information relating to the source applications and the destination applications, the repository including a plurality of data elements each being capable of performing a discrete operation on a piece of data, and The Boomi AtomSphere platform is alleged to be a repository of "common integration components" and "reusable configuration objects," such as connections, maps, and processes, that are used to build integrations. ¶29; ¶34 col. 4:20-33
a first module including a plurality of instruction sets, each instruction of each instruction set activating a data element; and Boomi's user-configured integration processes, built using "pre-built connectors" and other "Components," are alleged to function as the claimed module and instruction sets. ¶29; ¶31; ¶34 col. 6:55-58
an active component connected to the repository having an input for loading data from the source applications, and an output for populating the destination applications with processed data, the active component processing the data from the source applications by activating data elements according to the plurality of instruction sets in the module. Boomi's runtime engines ("Atoms") are alleged to be the "active component" that executes the integration processes, thereby processing data by using the reusable components as directed by the process flow. ¶30; ¶36 col. 2:56-61

Identified Points of Contention:

  • Scope Questions: The case may turn on whether the terminology of the '178 Patent, which reflects an early-2000s software architecture (e.g., "modules," "cartridges"), can be construed to read on the architecture of a modern, cloud-native iPaaS. A central question is whether a user-configured Boomi "process" qualifies as a "module" and whether Boomi's various "Components" (e.g., connections, maps, profiles) meet the definition of "data elements."
  • Technical Questions: The complaint relies on high-level product descriptions and marketing materials. A key technical question will be what evidence demonstrates that Boomi's "Atoms" actually operate by "activating data elements according to the plurality of instruction sets in the module," as claimed, versus operating on a fundamentally different technical principle. A marketing graphic from Defendant's website describes the Boomi platform as an 'Integration Platform as a Service (iPaaS)' that unifies various integration tasks in a cloud-based solution Compl. p. 7

V. Key Claim Terms for Construction

The Term: "data element"

  • Context and Importance: This term defines the basic reusable building block of the claimed system. The infringement analysis depends on whether Boomi's "Components" (e.g., connectors, maps) fall within the scope of this term.
  • Evidence for a Broader Interpretation: The claim requires only that a data element be "capable of performing a discrete operation on a piece of data" '178 Patent, cl. 1 The specification describes them broadly as "reusable code or units of work that perform a discrete data manipulation function" '178 Patent, col. 6:34-36
  • Evidence for a Narrower Interpretation: The specification provides examples such as "rules for translation and mapping" and "rules for data validation" '178 Patent, col. 6:31-33 This may support an argument that the term is limited to such granular, rule-based functions rather than higher-level objects like a complete connection or process.

The Term: "module"

  • Context and Importance: This term describes the structure that organizes the "instruction sets." Plaintiff's infringement theory appears to map this term onto Boomi's integration "processes." The viability of this mapping will be a central issue.
  • Evidence for a Broader Interpretation: The claim defines the term functionally as "including a plurality of instruction sets" that activate data elements '178 Patent, cl. 1 The specification refers to them as "configurable, pre-built integration packages" '178 Patent, col. 2:48-49
  • Evidence for a Narrower Interpretation: The specification's repeated reference to modules as "pre-built" and analogous to "cartridges" '178 Patent, col. 2:46-47 could be used to argue that a process dynamically configured by an end-user is not a "module" in the sense contemplated by the patent.

VI. Other Allegations

The complaint does not provide sufficient detail for analysis of indirect or willful infringement. It contains a single count for direct infringement Compl. p. 11

VII. Analyst's Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can the architectural terms of the '178 Patent, such as "module" and "data element," rooted in the context of early-2000s enterprise integration software, be construed to cover the constituent parts of a modern, cloud-based Integration Platform as a Service (iPaaS), such as Boomi's user-defined "processes" and reusable "Components"?
  • A key evidentiary question will be one of functional mapping: beyond high-level marketing similarities, what technical evidence will be presented to demonstrate that the accused Boomi "Atom" runtime engine operates in the specific manner required by Claim 1-by processing data through the activation of discrete "data elements" as directed by "instruction sets"-or whether its underlying architecture is fundamentally distinct from that claimed in the patent?
Loading Complaint