Patent litigation venue can have practical consequences for how technical disputes are managed, particularly when multiple cases involve related technologies and overlapping evidence. A 2018 motion by Intel to transfer a patent case brought by VLSI Technology from Delaware to California offers a detailed example of how a defendant may argue that location, engineering records and parallel proceedings should influence where a case is heard. The motion presented Intel’s position; its factual and legal arguments should not be confused with findings by a court.
Why venue became an issue in the VLSI–Intel dispute
VLSI had filed an earlier patent infringement action against Intel in the Northern District of California in October 2017, asserting eight patents. Ten months later, VLSI filed a second action in Delaware involving five additional patents. Intel’s August 2018 motion asked the Delaware court to transfer the later case to California, where the first action was already pending.
The central argument was not simply that the companies were incorporated in particular states. Intel contended that the two cases shared important technical and evidentiary ground, while neither party had substantial operational ties to Delaware beyond corporate formation. It argued that moving the later case could make coordination possible and reduce duplicated work. Whether transfer was appropriate was a question for the court under the applicable venue rules.
Technical overlap can connect separate patent cases
According to Intel’s brief, the cases involved patents addressing related aspects of power management in integrated circuits and low-voltage memory. The brief described technologies such as reducing power supplied to parts of a circuit and maintaining data in memory while a device operates in a low-power mode.
The allegations also concerned many of the same Intel processor families, including generations of Core and Xeon products. For engineers and technical decision-makers, this illustrates why separate patent claims may require evidence about shared product architectures, even when the asserted patents and specific infringement allegations differ. Intel argued that understanding the accused functionality across both cases would require examination of overlapping products and technical materials.
That overlap could also affect damages analysis. The motion asserted that both cases would require consideration of how particular functions relate to larger products, and that evaluating overlapping products and functionality in separate proceedings could create a risk of duplicated damages analysis. This was Intel’s argument in support of transfer, rather than a judicial determination about how damages should be calculated.
Where engineering evidence and witnesses are located
Intel stated that the accused products and functionality had been designed and developed at facilities in California, Oregon and Israel—not Delaware. It identified technical witnesses in locations including Folsom, Oregon and Israel, as well as witnesses in Santa Clara with knowledge of financial information and licensing. The brief also described Intel’s headquarters as being in Santa Clara, within the Northern District of California.
The location of evidence was another part of the transfer request. Intel expected to produce technical materials, including source code and schematics, as well as documents relating to product sales, costs, marketing, pricing, performance testing, market research and patent licensing. It said that the source code and schematics were being made available through secure computers at its counsel’s Los Angeles office, and that the same materials would be relevant to both actions.
In patent disputes involving complex products, the physical location of evidence may be only one consideration. The motion also pointed to where document collection was managed and where relevant employees worked. For industrial and technology businesses, these details underline the importance of being able to identify which teams, records and product-development activities relate to a dispute—not just where a company is legally registered.
Coordination, cost and the interests of justice
Intel argued that transferring the later case would allow the California court to consider whether the actions could be coordinated or consolidated. It said a shared proceeding could avoid repeating steps such as claim construction (the interpretation of patent claims), technical tutorials, expert-related hearings and trial preparation. It also argued that witnesses and documents relevant to both cases might otherwise be handled separately in courts far apart.
The brief framed these points within the familiar two-part inquiry under 28 U.S.C. § 1404(a): whether the case could have been brought in the proposed district, and whether transfer would better serve convenience and the interests of justice. Intel maintained that the Northern District of California was an available venue and that private and public interest considerations favored moving the case there. Its arguments included the parties’ connections to each location, the sites of relevant activities, witness and evidence access, judicial economy and local interest.
The brief also emphasized that both companies were organized in Delaware but, in Intel’s account, had few other connections to the state relevant to the dispute. It contrasted that with Intel’s California presence and the earlier case there. These points show how incorporation, operational presence and the location of technical work can be weighed differently in a venue dispute.
Practical takeaways for technology organizations
The case illustrates several issues that technical and legal teams may need to assess when patent claims involve complex products or parallel proceedings:
- Map the technical overlap. Identify whether separate cases concern related functions, product families or engineering records.
- Locate evidence and expertise. Establish where relevant development activities occurred, where knowledgeable employees work and how sensitive materials are accessed.
- Assess duplication. Consider whether separate proceedings could repeat document production, witness testimony or analysis of common products.
- Separate advocacy from outcome. A transfer motion presents one party’s reasons for changing venue; it does not, by itself, establish that the court accepted those reasons.
Conclusion
In semiconductor patent litigation, venue arguments can turn on more than corporate addresses. The VLSI–Intel motion shows how a party may connect venue to the location of product development, technical evidence, witnesses and an existing related case. For organizations managing complex product portfolios, maintaining a clear understanding of where engineering work and relevant records reside can help teams respond more effectively when parallel litigation raises questions of coordination and convenience.