ORDER GRANTING DEFENDANT’S MOTION TO DISMISS

INTRODUCTION

Plaintiff Microsoft Corporation filed this declaratory action against defendant WebXchange, Inc., who now moves for dismissal under FRCP 12(b)(1). Because no case or controversy exists between the parties, the motion is Granted.

STATEMENT

This case is an effort to open a new front in a new district arising out of patent litigation already proceeding in another district. Microsoft publishes and licenses a software called Visual Studio, which allows users to create various programs and applications. Among these possible applications are “web service” applications that support interactions between computers over the internet. These web service applications include applications that allow real-time transactions on the internet using the Simple Object Access Protocol (“SOAP”). Microsoft encouraged developers to use Visual Studio to create these kinds of programs, and posted examples and suggestions on its website for this purpose as well as to market the abilities of its software (Compl. ¶ 18). These “case studies” included explanations of software applications created by Dell, Inc., FedEx Corporation, and Allstate Insurance Company, who are now the defendants in various Delaware patent-infringement suits initiated by WebXchange.

WebXchange owns various patents related to real-time transactions on the internet. It brought suit in Delaware against a handful of developers who created web service applications, which WebXchange asserts violate its patents. Each of these developers used Microsoft’s Visual Studio software to create these allegedly infringing applications. In its claims against the developers, WebXchange has used the Microsoft materials to map its infringement contentions, and these developers have asked Microsoft to defend and indemnify them in the Delaware suits. WebXchange has never threatened Microsoft with an assertion that its Visual Studio software infringes WebXchange’s patents, but has stated herein that should this action continue, it will have to bring a counterclaim for indirect patent infringement against Microsoft. WebXchange has disavowed any intent to bring an inducement of infringement claim based on any case studies Microsoft has created up to this point.

ANALYSIS

The central issue in determining whether there is subject-matter jurisdiction in this case is whether there exists an actual case or controversy on which to base the declaratory judgment action. Under the Declaratory Judgment Act:

28 U.S.C. 2201(a).

The parties agree that the proper standard for determining whether a ease or controversy exists is whether the facts alleged, under all circumstances, show that there is a substantial actual controversy between parties having adverse legal interests of sufficient immediacy and reality to warrant the issue of a declaratory judgment.

Significantly, both parties agree that Microsoft’s Visual Studio software itself does not infringe the WebXchange patents. Instead, Microsoft argues that there is an actual controversy as to whether it is liable for inducement of infringement by others. It bases this argument on four main points. First, Microsoft argues that WebXchange’s actions in basing its Delaware infringement claims on Microsoft’s “case studies” shows that there is a substantial controversy that Microsoft possibly induced its customers to infringe. Second, Microsoft argues that WebXchange is prepared to bring a compulsory counterclaim against Microsoft for induced in fringement should this action go forward. Third, Microsoft claims that the Delaware defendants’ requests for defense and indemnity from Microsoft confirm the actual and immediate controversy. Fourth, Microsoft argues that its actions in encouraging developers to use Visual Studio to create software that facilitates real time transactions on the internet creates a case or controversy. In addition to these facts, Microsoft argues that subject-matter jurisdiction is proper due to practical considerations and its assertion of unenforceability and invalidity claims.

To be liable for inducement of infringement, it must be shown “that the alleged infringer knowingly induced infringement and possessed specific intent to encourage another’s infringement.” DSU Med. Corp. v. JMS Co., 471 F.3d 1293, 1306 (Fed.Cir.2006) (en banc) (citations omitted). Assessing the record in the light most favorable to Microsoft, this order finds that the record fails to show an actual controversy as to whether or not Microsoft actively and intentionally encouraged its customers to infringe WebXchange’s patents.

From the outset, WebXchange has conceded that it does not have any facts or evidence supporting an inducement claim. It also has stipulated to covenant not to sue Microsoft for any of its case studies made up to this point. During oral argument, WebXchange’s attorney stated that “I am prepared to state categorically that the facts as we presently know them, there is no basis for us to assert inducement against Microsoft.... We have no evidence; we have nothing in our possession and WebXchange’s knowledge that there is anything — that there are any facts on behalf that Microsoft is doing that they actively engaged inducement (Tr. 5).” Counsel further agreed that “Web Exchange [sic] will covenant not to sue Microsoft for inducement based on the case studies. And it will agree not to base any claim for inducement on the use of the case studies.... [It] will covenant not to rely on the case studies in any case of inducement against Microsoft (Tr. 9).” Thus, any argument by Microsoft that its “case studies” provide the basis for a case or controversy misses the mark. Aside from the covenant not to sue, the case studies are merely public explanations of what each of the Delaware defendants has done using the Visual Studio software, which is why WebXchange has used these “case studies” in its actions against those Delaware defendants. The mere fact that WebXchange quoted from the case studies to highlight what they believe are the infringing aspects of the developed software does not in and of itself show any intent to induce infringement on the part of Microsoft. Remember, again: all concede that the Microsoft software itself infringes no WebXchange patents, WebXchange has admitted to having no evidence supporting an inducement claim, and WebXchange has agreed to never use these studies in an inducement action against Microsoft.

WebXchange’s statement that it would have to bring a compulsory counterclaim should this action go forward also fails to satisfy the case or controversy requirement. At this point, Microsoft has not alleged any facts that justify an inducement action. Had this order found facts sufficient to hold otherwise, WebXchange’s position obviously would have to be modified, and it would have been forced by the compulsory counterclaim rule to counterclaim. Since, however, this order finds that no facts presented by Microsoft create a case or controversy, it merely reaffirms WebXchange’s belief that no facts exist to bring any infringement against Microsoft. Microsoft is using counterfeit logic to manufacture a controversy where none exists.

Next, it is true that Microsoft encourages developers to create web services that use SOAP. That, however, does not create a case or controversy, even for induced infringement. This marketing material found on Microsoft’s website does not establish a prima facie case of induced infringement as it does not show an intent to induce developers to infringe on WebXchange’s patents. WebXchange does not own a patent on all web services that use SOAP. This is conceded.

The 2005 email is too thin and abbreviated to support any plausible notion that Microsoft faces an imperiled future. That email called for nothing more than a ten-minute meeting to possibly sell Microsoft the patents in question. The description of the patents was less than ten words long. No threat of any kind was made. The email was more than three years ago. No threats have followed. At most, the ten-word description — “control over any real-time transaction on the net” — was puffery posing no plausible threat to Microsoft.

Judicial economy and practical considerations are also irrelevant to the finding of a case or controversy. As Microsoft admits in its opposition brief, judicial economy only prevents dismissal when there is an actual case or controversy. In this regard, Microsoft’s argument that it is exposed to massive economic damages through its indemnity agreements fails to show how resolution in this forum would provide a remedy that the Delaware actions do not. Surely, there are thousands of Microsoft Visual Studio users in the United States, yet WebXchange has only filed infringement claims against three. This leads to the inference that the issue is not that any and all Visual Studio uses infringe WebXchange’s patents. Rather, the inference is that it is being used in a specific way by those customers to allegedly infringe. That issue is being properly adjudicated before the Honorable Judge Joseph J. Farnan, Jr., in the District Court of Delaware. Those Delaware actions are well along the road to resolution, and it would be imprudent for this Court to usurp the disposition of that issue from Judge Farnan. Microsoft has represented that those customers in the Delaware action have requested indemnity and tendered their defense to Microsoft. Any remedy Microsoft could seek in this action could be pursued in Delaware if Microsoft were to take over the defense of those customers. The indemnity agreements fail to establish a case or controversy in and of themselves. This same logic applies to any practical considerations that would make this Court a more convenient forum.

Finally, Microsoft’s assertion of unenforceability and invalidity claims are similarly irrelevant, as the declaratory action must be related to charges of infringement. Foster v. Hallco Mfg. Co., 947 F.2d 469, 479 (Fed.Cir.1991). As there is no case or controversy as to infringement, dismissal of the declaratory action is proper.

CONCLUSION

For the foregoing reasons, WebXchange’s motion to dismiss is Granted, as there is no case or controversy to establish subject-matter jurisdiction. Plaintiff may file a motion requesting leave to amend its claims within fourteen calendar days of the date of entry of this order, which is March 3, 2009. Any such motion should be accompanied by a proposed pleading and the motion should explain why the foregoing problems are overcome by the proposed pleading. Plaintiff must plead its best ease. Failing such a motion, all of plaintiffs claims will be dismissed with prejudice.

IT IS SO ORDERED.