VirtualAgility Inc v. Salesforce.com, Inc. et al

Filing 117

MEMORANDUM OPINION AND ORDER -. Signed by Judge Rodney Gilstrap on 1/8/2014. (ch, )

Download PDF
IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS MARSHALL DIVISION VIRTUALAGILITY, INC., Plaintiff, v. SALESFORCE.COM, INC., ET AL Defendants. § § § § § Civil Action No. 2:13-cv-00011-JRG § § § § § MEMORANDUM OPINION AND ORDER Before the Court is Defendants’ Joint Motion to Stay Proceedings Pursuant to Section 18(b) of the Leahy-Smith America Invents Act (“AIA”). (Dkt. No. 67.) Having considered the parties’ written submissions, the Court DENIES Defendants’ motion. I. Background The patent at issue relates to processes and tools which provide a common framework for communicating effectively across diverse groups within an organization and for assessing key elements of the organization’s business. The patentee, VirtualAgility, Inc. (“VirtualAgility” or “Plaintiff”) sells cloud-based enterprise-level information technology solutions that encompass the patented invention. Defendant Salesforce.com, Inc. (“Salesforce”) likewise is a provider of enterprise cloud computing solutions, whose products are used by the other Defendants in this case. VirtualAgility filed suit on January 4, 2013 against Salesforce and the other Defendants for allegedly infringing U.S. Patent No. 8,095,413 (the “’413 Patent”). On May 24, 2013, Salesforce 1 filed a petition for Covered Business Method (“CBM”) review of the ‘413 Patent under the AIA. On May 29, 2013, all Defendants jointly filed the instant motion seeking a stay of proceedings pending the PTO’s final resolution of the CBM review. On November 19, 2013, the Patent Trial and Appeal Board (“PTAB”) granted Defendants’ petition and instituted a CBM review of all claims of the ‘413 Patent. II. Applicable Law Section 18 of the Leahy-Smith America Invents Act (“AIA”) establishes the Transitional Program for Covered Business Method Patents (“CBM”). 157 Cong. Rec. S1360-02 (2011); AIA § 18. The program is regarded as a post-grant review, where a person sued for infringement of a “covered business method” patent may petition the PTAB to review the validity of that patent. AIA § 18(a). For purposes of the statute, a “covered business method” patent is defined as “a patent that claims a method or corresponding apparatus for performing data processing operations utilized in the practice, administration, or management of a financial product or service.” AIA § 18(d). The transitional program provides a statutory stay provision under which a party may seek stay of a civil action alleging infringement of the CBM patent. AIA § 18(b)(1). The courts are directed to base their decision as to whether or not to grant such a stay on four factors: “(A) whether a stay, or the denial thereof, will simplify the issues in question and streamline the trial; (B) whether discovery is complete and whether a trial date has been set; (C) whether a stay, or the denial thereof, would unduly prejudice the nonmoving party or present a clear tactical advantage for the moving party; and (D) whether a stay, or the denial thereof, will reduce the burden of litigation on the parties and on the court.” Id. III. Analysis 2 The Court will discuss each of the statutory stay factors outlined in § 18(b) below, addressing the parties’ specific arguments where applicable. a. Statutory Background The CBM transitional program is designed to “provide a cheaper, faster alternative to district court litigation over the validity of business-method patents.” 157 Cong. Rec. S1360-02. The proceeding is limited to certain business method patents, which “are generally of dubious quality because unlike other types of patents, they have not been thoroughly reviewed at the PTO due to a lack of the best prior art.” Id. The four-factor test, adopted directly from a 2006 district court opinion in Broad. Innovation, L.L.C. v. Charter Commc’n, Inc., No. 03-cv-2223-ABJ-BNB, 2006 WL 1897165 at *3 (D. Colo. July 11, 2006), “closely resembles the stay analysis courts have applied in assessing a motion to stay pending inter partes or ex parte reexamination by the [patent office]. 157 Cong. Rec. S1360-02; Market-Alerts Pty. Ltd. v. Bloomberg Fin. L.P., 922 F. Supp. 2d 486, 489 (D. Del. Feb. 5, 2013); see, e.g., Soverain Software LLC v. Amazon, Inc., 356 F. Supp. 2d 660, 662 (E.D. Tex. 2005) (citing Landis v. N. Am. Co., 299 U.S. 248, 254 (1936)) (applying a three-factor test that asks “(1) whether a stay will unduly prejudice or present a clear tactical disadvantage to the nonmoving party, (2) whether a stay will simplify the issues in question and trial of the case, and (3) whether discovery is complete and whether a trial date has been set.”). Indeed, the only difference between the CBM test and the court’s traditional test is the addition of the fourth factor, which requires courts to consider “whether a stay, or the denial thereof, will reduce the burden of litigation on the parties and on the court.” AIA § 18(b)(1). Some courts interpret this additional consideration as “[having] ease[d] the movant’s task of demonstrating the need for a stay.” Market-Alerts, 922 F. Supp. 2d at 489-490; see also Versata Software, Inc. v. Volusion, Inc., No. 3 A-12-CA-893-SS (W.D. Tex. June 20, 2013) (slip opinion); Progressive Casualty Ins. Co. v. Safeco Ins. Co, et al., Nos. 1:10-cv-01370, 1:11-cv-00082, 1:12-cv-01068, 1:12-cv-01070, 2013 WL 1662952 (N.D. Ohio April 17, 2013); Zillow v. Trulia, No. C-12-1549-JLR, 2013 WL 5530573 (W.D. Wash. Oct. 7, 2013). This Court is mindful that Congress did not provide an automatic stay provision for the transitional program. Rather, the statute instructs the court to consider all four factors in deciding whether or not to grant a stay. Further, there has been little dispute among district courts that Congress did not intend to alter the way in which district courts assess the first three factors. See, e.g., Market-Alerts, 922 F. Supp. at 490 n.6; Zillow, 2013 WL 5530573 at *3. Thus, under the statutory stay provision of the transitional program, staying patent cases pending CBM review remains squarely within the court’s discretion, and “such determinations must rest on the facts of each particular case.” See Sightsound Techs., LLC v. Apple, No. 11-1292, 2013 WL 2457284 at *1 (W.D. Penn. June 6, 2013). Whether to ultimately grant or deny such a stay flows from the court’s inherent authority to manage its own trial docket. See Landis v. N. Am. Co., 299 U.S. 248, 254 (1936) (“[T]he power to stay proceedings is incidental to the power inherent in every court to control the disposition of the causes on its docket with economy of time and effort for itself, for counsel, and for litigants.”). b. Simplification of Issues The first statutory factor requires the Court to consider whether a stay will simply the issues in question and streamline the trial. Defendants argue that the CBM review will simplify the issues in this case because the review may result in some or all of the claims being cancelled. The Court, however, is not convinced that such a result is probable. The Court notes from the outset that the ‘413 Patent has gone through a lengthy 4 prosecution process, indeed one spanning over twelve years, during which time the PTO considered more than sixty patent and non-patent prior art references before eventually granting the patent. The application was filed on May 14, 1999. After the initial examination and continued examination, the examiner rejected the patent application under 35 U.S.C. § 102 and §103, which decision was appealed to the Board of Patent Interference and Appeal (“BPIA”). In a written opinion published on June 16, 2011, the BPIA reversed the examiner’s rejection under § 102 and § 103, but raised a new ground of rejection finding the claims directed at un-patentable subject matter under 35 U.S.C. § 101. Thereafter, the applicant reopened prosecution and authorized an examiner’s amendment. In light of the BPIA’s rejection under § 101, the examiner amended then-pending claims 197, 210 and 211, bringing those claims to, in the examiner’s view, the proper scope of the statutory subject matter. With those amendments deemed acceptable by the applicant, the amended claims were subsequently allowed on September 25, 2011, which then became the claims of the ‘413 patent.1 Thus, unlike the more common business method patents which Congress contemplated to “have not been thoroughly reviewed at the PTO due to a lack of the best prior art,” there can be little dispute here about the thoroughness of the PTO’s prior examination of the ‘413 patent, given the various grounds of invalidity and the breadth of prior art references considered by the PTO before issuing this patent. Defendants argue that the CBM review will simplify issues in this case because the PTAB will determine whether the asserted claims are invalid in view of “several important prior art references.” Defendants presented a total of two prior art references to the PTAB (the Ito patent and the Lowery book), one of which, the Lowery book, was previously considered by the PTO 1 To the extent the Court refers to any prosecution history record not specifically set forth by either party, the Court hereby, sua sponte, takes judicial notice of such record. See Federal Rule of Evidence 201 (b)-(c) (stating that courts may unilaterally take judicial notice of a fact not subject to reasonable dispute because “it can be accurately and readily determined from sources whose accuracy cannot reasonably be questioned.”). 5 during the ‘413 patent prosecution. Indeed, in its Decision Instituting Covered Business Method Review of the ‘413 patent, the PTAB again found that “[Salesforce] has failed to show that claims 1-21 are, more likely than not, anticipated by Lowery,” and that “[Salesforce] has not shown that claims 1-21 are, more likely than not, unpatentable as would have been obvious[] over Ito and Lowery,” essentially leaving the Ito patent as the single prior art reference currently before the PTAB. Dkt. No. 105-1 at 43-44. Given the thoroughness of the PTO’s prior examination of the ‘413 patent, during which time more than sixty prior art references were considered, the Court is not persuaded that the Ito patent, by itself, would invalidate all or a substantial number of asserted claims of the ‘413 Patent. Moreover, during the course of this litigation, Defendants have indicated to the Court that they would rely on at least two other non-patent prior art references (the “Oracle project” and the “Tecskor product”), both of which are allegedly “of particular importance.” See Dkt. No. 49 at 18-19 (Defendants relying on the prior art “Oracle project” in seeking to transfer venue to the Northern District of California); Dkt. No. 103 at 3 (Defendants requesting the Court to issue a letter of request for international judicial assistance from Canada with respect to the prior art Tecskor software product). Neither the Oracle project nor the Tecskor product is before the PTAB. Thus, even though the CBM review obviates the need for this Court to consider the Ito patent, should any of the asserted claims emerge from the CBM review, the Court would almost certainly need to consider either the Oracle project or the Tecskor product, if not both, as invalidating prior art. In this regard, the benefit derived from the PTAB’s consideration of the Ito patent, as the only prior art reference now before the patent office, is therefore marginal. Cf. Broad. Innovation, 2006 WL 1897165 at *3 (recognizing the advantage of PTO reexamination when “[a]ll prior art presented to the Court will have been first considered by the PTO, with its 6 particular expertise.”) Defendants further argue that a stay will “clearly simplify” the issues in this case because a § 101 determination will likely cancel all asserted claims of the ‘413 patent in light of the PTAB’s recent decision holding unpatentable under 35 U.S.C. § 101 certain method and computer apparatus claims in SAP Am., Inc. v. Versata Development Group, Inc., No. CBM2012-00001 (PTAB June 11, 2013) (final written decision for CBM review of U.S. Patent 6,553,350 (the “SAP patent”)). The Court, however, sees even greater uncertainty with respect to the PTAB’s § 101 determination. Defendants have correctly noted that patentable subject matter is a complex and unsettled area of law. See Bilski v. Kappos, 130 S. Ct. 3218, 3232 (2010) (Stevens, J., concurring) (noting the “uncertainty that currently pervades this field” as to what constitutes a patentable “process” under 35 U.S.C. § 101.); CLS Bank Int’l v. Alice Corp. Pty. Ltd., 717 F.3d 1269, 1277 (Fed. Cir. 2013), cert. granted, 13-298, 2013 WL 4776518 (U.S. Dec. 6, 2013) (“While simple enough to state, the patent-eligibility test has proven quite difficult to apply.”). The patentability of claims directed at computer-implemented inventions as in this case is a particularly divided issue at the Federal Circuit. 2 While the Court has the benefit of the PTAB’s prior § 101 determination in SAP v. Versata in deciding whether the CBM review will likely cancel any claims of the ‘413 Patent, it finds considerable differences between the claims in SAP and the claims at issue. The SAP patent went through a three-year prosecution, during which time the only ground of invalidity considered by the PTO was obviousness under § 103. See Versata Software, Inc. et al v. SAP America, Inc. et al, No. 2:07-cv-00153-RSP, Dkt. No. 352 Exs. 3.4-3.8 (prosecution history of the SAP patent). The CBM review then cancelled all SAP claims under § 101 and Gottschalk v. Benson, 409 U.S. 63 (1972), as simply reciting a generic general purpose computer 2 See Donald S. Chisum, Patents on Computer-Implemented Methods and Systems: The Supreme Court Grants Review (CLS Bank) Background Developments and Comments, Chisum Patent Academy (2013). 7 element that failed to constitute a “meaningful limitation” of the claim. See SAP, No. CBM2012-00001 at 29-30. This ground of invalidity, however, has been considered by the BPAI during the course of the ‘413 Patent prosecution. See Decision on Appeal, Application No. 09/312,740 at 10 (BPAI June 20, 2011) (rejecting the then-pending claims of the ‘413 patent application as encompassing software per se); MPEP Ch. 2100, § 2106 (listing “computer program per se” as an example of unpatentable claims under Benson, 409 U.S. at 72). Indeed, the amendments that eventually led to the issuance of the ‘413 patent were recommended by the examiner to specifically address the Board’s § 101 rejection. Thus, unlike the SAP claims the subject-matter patentability of which had never been considered by the patent office prior to its CBM review, here § 101 issues concerning the ‘413 patent had been scrutinized by both the patent examiner and the appeal Board, and this occurred less than two years prior to Defendant’s petition for CBM review. As a result, the ‘413 patent carries with it a stronger presumption of validity than the SAP patent with respect to at least the § 101 challenge. See Bowser, Inc. v. U. S., 388 F.2d 346, 349 (Ct. Cl. 1967) (“The strength of the presumption [of patent validity] varies with the substance of the assertion, e.g., if the asserting party relies on prior art that previously has been considered either by the Patent Office or by another court then the presumption of validity is strong, or if the asserting party cites prior art that is more pertinent than that considered by the Patent Office or another court then the presumption of validity is considerably weakened.”); cf. Microsoft Corp. v. i4i Ltd. P’ship, 131 S. Ct. 2238, 2250 (2011) (“[B]ecause the heightened standard of proof [for invalidating a patent] applied where the evidence before the court was ‘different’ from that considered by the PTO, it applied even more clearly where the evidence was identical.”) (citation omitted). Further, beyond the underlying abstract idea, the SAP claims include but a broad limitation 8 of using “a data source,” which incurred nothing more than “conventional, routine steps that are a consequence of implementing the abstract idea.” See SAP, No. CBM2012-00001 at 21-32. Whereas in this case, the asserted claims of the ‘413 patent involve “an extensive computer interface,” particularly, a specific application of a method implemented on a comprehensive graphical user interface. See Ultramercial, Inc. v. Hulu, LLC, 722 F.3d 1335, 1352 (Fed. Cir. 2013). Not only do multiple claims of the ‘413 patent call for “a graphical user interface” capable of displaying and linking different categories of information and supporting a variety of user operations, the specification also makes it clear that such a user interface is essential for achieving the intended benefit of the claimed intention. See, e.g., Claims 1-3; Col. 11:24-27 (“Because these different views are a click away, the Agile Manager supports a dynamic decision making process where discussion can move quickly from strategic to tactical consideration.”); Figs. 3, 6-10, 12-33. Here, unlike the “data source” element of the SAP claims which was mere “token pre- or post-solution steps” of the underlying idea, the graphical user interface which links different groups of an organization is an integral part of the claimed invention, and is more likely to provide a “meaningful limitation” to the general idea. Ultramercial, 722 F.3d at 1352; Bancorp Servs., L.L.C. v. Sun Life Assur. Co. of Canada (U.S.), 687 F.3d 1266, 1278 (Fed. Cir. 2012) (“In order for the addition of a machine to impose a meaningful limit on the scope of a claim, it must play a significant part in permitting the claimed method to be performed[.]”). Accordingly, given the clear differences between the SAP claims and the asserted claims of the ‘413 Patent, the Court is not persuaded that the PTAB will likely cancel all claims of the ‘413 patent under § 101, as it did in SAP. Defendants’ assertion that a § 101 determination will “clearly simplify issues” is nothing more than an educated guess in this case. In sum, weighing the limited benefit derived from the PTAB’s prior consideration of the 9 single prior art reference (the Ito patent) against the substantial uncertainty involved in all other aspects of the CBM review, including the § 101 determination and further in view of the two additional prior art references not before the PTAB, this Court is not convinced that granting a stay will simplify the issues in this case. This factor is essentially neutral, if not slightly against, granting a stay in this case. c. Status of This Case The second factor, whether discovery is complete and whether a trial date has been set, weighs in favor of granting a stay. While jury selection in the instant case has been set to take place on November 3, 2014, the deadline to complete fact discovery is more than six months away. See Dkt. No. 91. Some discovery has been undertaken, but the parties have not filed their joint claim construction statement or proposed claim terms to be construed. Ultimately, however, the Court finds that the benefits of a stay at this relatively early stage of the proceedings are outweighed by various other considerations as discussed elsewhere herein. See Broad. Innovation, 2006 WL 1897165 at *11 (“[T]he ultimate determination is within the Court’s discretion based on a weighing of the benefits of issuing a stay versus any added expenses resulting from the stay.”). d. Prejudice or Disadvantage to Plaintiff Regarding the third statutory factor, Plaintiff VirtualAgility argues that a stay will unduly prejudice it because its direct competitor Salesforce will be given up to two additional years to compete against VirtualAgility using VirtualAgility’s patented technology without permission, which may lead to VirtualAgility’s loss of market share and erosion of good will. Defendants dispute that Salesforce is VirtualAgility’s direct competitor and further argue that any prejudicial effect would be minimal because the CBM review occurs in an expedited 12-month time-frame. 10 Further, Defendants state that VirtualAgility’s failure to have sought any form of preliminary injunction in this case demonstrates that a stay will not result in undue prejudice. Staying a case pending reexamination and “waiting for the administrative process to run its course risks prolonging the final resolution of the dispute and thus may result in some inherent prejudice to the plaintiff.” Market-Alerts, 922 F. Supp. 2d at 494. While “the potential for delay does not, by itself, establish undue prejudice,…courts are generally reluctant to stay proceedings where the parties are direct competitors,” because in such cases, “there is a reasonable chance that delay in adjudicating the alleged infringement will have outsized consequences to the party asserting infringement[], including the potential for loss of market share and an erosion of goodwill.” Id. at 494-95; Tesco Corp. v. Weatherford Int’l, Inc., 599 F. Supp. 2d 848, 851 (S.D. Tex. 2009) (“Where the parties are direct competitors, a stay would likely prejudice the non-movant.”). Given that the patentee “could lose market share – potentially permanently – during the stay,…while the alleged infringer continues to sell the competing products,” such loss constitutes an irreparable injury not compensable by money damages. A.R. Arena Products, Inc. v. Grayling Indus., Inc., 5:11-CV-1911, 2012 WL 2953190 (N.D. Ohio June 25, 2012) (citing Sunbeam Products, Inc. v. Hamilton Beach Brands, Inc., 2010 WL 1946262 (E.D.Va. May 10, 2010)); see also Avago Technologies Fiber IP (Singapore) Pte. Ltd. v. IPtronics Inc., 2011 WL 3267768 at *5 (N.D. Cal. July 28, 2011) (“infringement among competitors can cause harm in the marketplace that is not compensable by readily calculable money damages…Staying a case while such harm is ongoing usually prejudices the patentee that seeks timely enforcement of its right to exclude.”); Heraeus Electro–Nite Co., LLC v. Vesuvius USA Corp., 2010 WL 181375 at *1 (E.D.Pa. Jan. 11, 2010) (“[C]ourts have been reluctant to grant stays where, as here, the parties are direct competitors…In such situations, stays are denied where there is concern that the patent 11 owner will be irreparably harmed because the accused product will continue to gain market share during the pendency of the stay.”). Here, Defendants dispute in the first instance that VirtualAgility and Salesforce are direct competitors, dismissing VirtualAgility’s purported evidence as conclusory. The Court, however, finds that credible evidence does exist demonstrating that Salesforce and VirtualAgility compete in the same market, and for business from the same customer base. For example, Plaintiff VirtualAgility sells cloud-based “enterprise-level information technology solutions that allow users to build and configure user-defined computer and software applications for specific needs.” Dkt. No. 72-2, Rudolph Decl. at ¶ 6. Salesforce, meanwhile, describes itself as “a provider of enterprise cloud computing solutions” and admits that it “may encounter competition from enterprise software vendors and online service providers who may develop toolsets and products that allow customers to build new apps that run on the customers’ current infrastructure or as hosted services.” Salesforce.com, Inc., Annual Report (Form 10-K), at 4, 9 (March 8, 2013).3 Such competition fits the description of VirtualAgility’s business model which Salesforce does not dispute. Moreover, VirtualAgility sells its products to, among others, public sector entities such as federal and state governmental agencies, and Salesforce’s website publicizes its efforts to sell products to various federal governmental agencies. Rudolph Decl. at ¶ 8 (citing http://www.salesforce.com/company/news-press/press-releases/2012/04/120425.jsp). Tellingly, these two entities took part in the same government bid process at least once. Id. The Court finds that VirtualAgility and Salesforce directly compete in at least the enterprise cloud computing market targeting public sector entities, and that such relationship is demonstrated by more than 3 The Court hereby takes judicial notice of Salesforce’s annual report filed with the United States Securities and Exchange Commission. See Federal Rule of Evidence 201 (b)-(c) (stating that courts may unilaterally take judicial notice of a fact not subject to reasonable dispute because “it can be accurately and readily determined from sources whose accuracy cannot reasonably be questioned.”). 12 mere conclusory statements. Having decided that VirtualAgility and Salesforce compete in the same market, the Court necessarily finds that granting a stay pending the CBM review will unduly prejudice VirtualAgility. Such a stay will leave VirtualAgility with no recourse during the intervening time against unauthorized use of its patented invention. In fact, it will be “forced to compete against products that incorporate and infringe” its own invention. See Douglas Dynamics, LLC v. Buyers Products Co., 717 F.3d 1336, 1344 (Fed. Cir. 2013). The loss of market share and consumer goodwill is particularly high in the growing market of enterprise cloud-computing, where contractors and governmental agencies are developing lists of preferred vendors. See ADA Solutions, Inc. v. Engineered Plastics, Inc., 826 F. Supp. 2d 348, 351 (D. Mass. 2011); accord Polymer Techs., Inc. v. Bridwell, 103 F.3d 970, 975–76 (Fed. Cir. 1996) (“Years after infringement has begun, it may be impossible to restore a patentee’s (or an exclusive licensee’s) exclusive position by an award of damages and a permanent injunction. Customers may have established relationships with infringers.”). While the Court is mindful that CBM review generally proceeds on an expedited twelve-month time-frame from the date the PTAB institutes review until it issues a final written decision, see Office Patent Trial Practice Guide, 77 Fed. Reg. 48756, as opposed to inter-partes reexamination that could take up to twenty-four months, the Court is not persuaded that potential loss of market share and consumer goodwill during the intervening one year would necessarily impose only minimal prejudice on VirtualAgility.4 It is undisputed that VirtualAgility is and has been a small company with private investors and limited resources. Being left with no recourse 4 By the instant motion Defendants seek to stay proceedings until “the CBM Review is fully resolved,” however, without identifying at which specific step of the CBM review should such stay be lifted. After the PTAB’s final written opinion, parties can ask the Board to re-hear the case or appeal to the Federal Circuit. The CBM review may well be “fully resolved” only after the Federal Circuit issues its opinion. Thus, it is certainly possible that the stay sought by Defendants could exceed the initial twelve months. 13 against the infringing acts of much larger companies such as Defendants, even only for a year, may substantially injure VirtualAgility’s business such that it becomes “impossible to restore [its] exclusive position by an award of damages and a permanent injunction.” Polymer, 103 F.3d at 975–76. Furthermore, “when a case is stayed, witnesses may become unavailable, their memories may fade, and evidence may be lost while the PTO proceedings take place.” Ambato Media, LLC v. Clarion Co., Ltd., 2:09-CV-242-JRG, 2012 WL 194172, at *5 (E.D. Tex. Jan. 23, 2012). The possibility of witness loss is heightened in this case because certain identified witnesses are of an advanced age. For example, Gordon E. Nelson, the attorney who prosecuted the ‘413 Patent over the entire course of the twelve-year examination, is now beyond age seventy. Granting a stay and prolonging this litigation will subject VirtualAgility to the added risk of witness loss, thereby unduly prejudicing it in the legal proceeding. Lastly, Defendants argue that VirtualAgility will not be unduly prejudiced by a stay given that it has not sought any form of preliminary injunctive relief. The Court disagrees. A party’s decision to seek or not to seek a preliminary injunction often rests upon a variety of factors, including that party’s resources, the uncertainty of the outcome, or as part of an overall strategy to streamline the process and focus on other procedural steps of the litigation. Not being in a role to judge the parties’ litigation strategy, the Court deems it unfair to hold VirtualAgility to a position based upon what is no more than a dubious implication. In sum, granting a stay in this case may cause negative “outsized consequences” to VirtualAgility, including irreparable loss of market share, erosion of goodwill and potential loss of key witnesses. Market-Alerts, 922 F. Supp. 2d at 494-95. This Court believes that a stay would unduly prejudice VirtualAgility both in the market place and in this litigation. This factor weighs 14 heavily against granting a stay. e. Burden on the Court and parties The fourth statutory factor directs the court to consider “whether a stay, or the denial thereof, will reduce the burden of litigation on the parties and on the court.” Defendants argue that a stay will spare the parties the burden of litigating the validity of the ‘413 Patent in this Court and before the PTAB at the same time. Defendants further argue that a stay will reduce the Court’s burden by allowing the PTAB to first determine the validity of the ‘413 Patent in light of the prior art, and spare the Court’s burden of conducting claim construction for claims that may be cancelled or amended during the CBM review process. Aside from the plain language of § 18(b), the statute provides no further guidance on how courts should assess the fourth statutory factor. The Broad. Innovation decision from which Congress directly adopted the four-factor statutory test, however, sheds some light on the proper application of this factor. The Broad. Innovation court noted that the fourth “burden of litigation” factor is related to the first “simplification of issues” factor. See Broad. Innovation, 2006 WL 1897165 at *4 (describing the fourth factor as “the orderly course of justice measured in terms of the simplifying or complicating of issues, proof and questions of law which could be expected to result from a stay”) (citation omitted). The Court agrees that these two factors are not entirely independent of each other. If granting a stay is unlikely to simplify the issues in litigation, then it will not likely reduce the overall burden on the court and the parties. Here, Defendants’ arguments under the fourth statutory factor substantially overlap with those already presented under the first factor. As discussed above, given the thoroughness of the PTO’s prior examination of the ‘413 patent, the single new prior art currently before the PTAB, and the uncertainty of the PTAB’s § 101 determination, the Court is not convinced that the CBM 15 review will cancel all or even a substantial number of the asserted claims. Thus, the burden on this Court and the parties, when measured in context of the overall course of this litigation, will not be substantially lessened by a stay. See Broad. Innovation, 2006 WL 1897165 at *12 (finding that judicial economy weighed in favor of granting a stay when “the Court is influenced by the breadth of the reexamination and the number of prior art references under active review.”). Further, the CBM review will not substantially alleviate the existing demands upon the Court and the parties with respect to the Oracle project and the Tecskor product, as neither reference is before the PTAB. The Court acknowledges that a stay will relieve the parties’ burden of litigating the validity of the ‘413 Patent in this Court and before the PTAB at the same time. Such is true, however, in all cases involving CBM reviews. Had Congress deemed this burden so overwhelming as to justify a stay in and of itself, the statute would have been written differently. Absent such a different statutory provision, relief from a burden inherent to all CBM reviews cannot reasonably serve as the sole basis for tipping the fourth factor in favor of granting a stay. To be clear, beyond general relief from dual-track litigation which is inherent to all CBM reviews, the specific circumstances in the instant case present only a limited possibility of added reduction to the burden on the Court and the parties. The fourth factor therefore weighs only slightly in favor of a stay. IV. Conclusion The Court, having considered thoroughly the four statutory factors outlined in § 18(b) of the AIA, finds as follows: the first factor weighs slightly and the third factor weighs heavily in favor of denying a stay, while the second factor weighs in favor of granting a stay and the fourth factor weighs only slightly so; the result being that the relevant factors favor denying the Motion 16 for Stay. Accordingly, the Court hereby DENIES Defendants’ Joint Motion to Stay Proceedings Pursuant to § 18(b) of the AIA (Dkt. No. 67). So Ordered and Signed on this Jan 8, 2014 17

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?