Meaningful Preparation to Conduct Potentially Infringing Activity Required for Declaratory Judgment Jurisdiction
Client Alert | 1 min read | 05.30.08
In Cat Tech LLC v. TubeMaster, Inc. (No. 07-1443, May 28, 2008), the Federal Circuit affirms a declaratory judgment of non-infringement as to three different configurations of a catalyst loading device which had yet to be manufactured by TubeMaster. The district court granted TubeMaster's motion for declaratory judgment of non-infringement based on a finding of a "live controversy" because TubeMaster had designed the configurations and was ready to produce the configurations upon receipt of an order.
A declaratory judgment plaintiff must show "meaningful preparation to conduct potentially infringing activity" to satisfy the immediacy and reality requirements for a declaratory judgment. The fundamental inquiry is whether, under all the circumstances, there exists a substantial controversy of sufficient immediacy and reality to warrant the issuance of a declaratory judgment. MedImmune, Inc. v. Genentech, Inc, 549 U.S. 118 (2007), eliminated the requirement of a reasonable apprehension of suit but did not change the importance of meaningful preparation to engage in potentially infringing activity in the totality of circumstances. "If a declaratory judgment plaintiff has not taken significant, concrete steps to conduct infringing activity, the dispute is neither 'immediate' nor 'real' and the requirements for justiciability have not been met." The Federal Circuit agrees that the controversy here was sufficiently immediate where TubeMaster had developed and designed the configurations in question and was prepared to promptly produce the configurations when it received an order. Also, the controversy is deemed sufficiently real because the configuration designs were "substantially fixed" and could be used for production without significant modifications.
Contacts
Insights
Client Alert | 7 min read | 08.17.26
Delayed Notification of Cyberattacks May Trigger HIPAA Breach Notification Rule
After identifying a ransomware attack in 2021, OSF Healthcare System waited until its forensic investigation had concluded before notifying the U.S. Department of Health and Human Services (HHS) — and the affected individuals — of the breach. The 110-day delay (nearly double the 60-calendar-day notification deadline mandated by the HIPAA Breach Notification Rule) triggered an investigation from HHS’s Office for Civil Rights (OCR). The health system’s investigation determined that protected health information (PHI) had been stolen.
Client Alert | 4 min read | 08.14.26
License to Hack? The White House Greenlights Private-Sector Offensive Cyber Operations
Client Alert | 4 min read | 08.13.26
Supreme Court Confirms Contractual Loss of Bargain Without Repudiatory Breach
Client Alert | 7 min read | 08.12.26
Developments in Canadian Investment Treaty Practice: New FIPA Between Canada and UAE in Force

