throbber
Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 1 of 8 PageID #: 1416
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TYLER DIVISION
`
`C.A. No. 6:12-cv-00799-LED
`
`JURY TRIAL DEMANDED
`
`§§
`

`
`§§
`

`
`§§
`

`
`INVENSYS SYSTEMS, INC.,
`
`v.
`
`Plaintiff,
`
`EMERSON ELECTRIC CO. and
`MICRO MOTION INC., USA,
`
`Defendants.
`
`PLAINTIFF INVENSYS SYSTEMS, INC.’S RESPONSE TO DEFENDANTS’
`MOTION TO STAY PROCEEDINGS PENDING RESOLUTION OF
`DEFENDANTS’ MOTION TO TRANSFER VENUE PURSUANT TO 28 U.S.C. § 1404(a)
`
`A stay is completely unnecessary. Briefing on the transfer motion, which included
`
`extensive evidentiary materials, was completed only two months ago.
`
`In contrast, the cases on
`
`which Defendants Emerson Electric Co. (“Emerson”) and Micro Motion Inc., USA (“Micro
`
`Motion”) (collectively “Defendants”) primarily rely involved delays of at least a year.
`
`In addition, Defendants’ concern about duplicative litigation in the absence of a stay is
`
`without merit. The initial discovery in this case—the parties’ respective positions on claim
`
`construction, infringement, invalidity, and production of Defendants’ technical documents—will
`
`need to be provided regardless of whether the Court transfers this case to Colorado. A stay on
`
`the eve of entry of the discovery order (and with discovery starting in July) would also severely
`
`prejudice Plaintiff Invensys Systems, Inc. (“Invensys”), which is a direct competitor of
`
`Defendants in the coriolis flowmeter market, and has suffered significant damages as a result of
`
`Defendants’ ongoing infringing conduct.
`
`EAST\56132731.6
`
`1
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 2 of 8 PageID #: 1417
`
`BACKGROUND
`
`Defendants’ representations about
`
`the status of this case are not entirely accurate.
`
`Invensys amended its Complaint earlier this year, promptly filed its Notice of Readiness for
`
`Status Conference following the close of pleadings, and sent Defendants proposed Docket
`
`Control, Discovery, and ESI Orders before Defendants filed their motion to stay. See E-mail
`
`from Jeffrey Johnson, counsel for Invensys, to Linda Hansen et al., counsel for Defs. (May 31,
`
`2013 at 10:51 AM) (Ex. A) (transmitting Docket Control, ESI, and Discovery Orders); E-mail
`
`from CM/ECF Sys., E.D. Tex., to Amy Mohan et al., counsel for Invensys (May 31, 2013 at 4:35
`
`PM) (Ex. B) (notifying counsel of the filing of Defendants’ motion to stay). All of Invensys’
`
`proposed orders track the Court’s model orders, and their acceptance should be uncontroversial.
`
`Thus, Defendants statement that “[t]he parties have not yet conducted . . . any negotiations
`
`regarding” the Docket Control, ESI, and Discovery Orders is misleading. Defs.’ Mot. to Stay
`
`Proceedings Pending Resolution of Defs.’ Mot. to Transfer Venue Pursuant to 28 U.S.C. §
`
`1404(a) at 2, ECF. No. 36 (“Defs.’ Mot. to Stay”).
`
`Similarly, Defendants description of the facts relevant to the transfer motion contains
`
`several key omissions.
`
`Invensys will not belabor the Court with a repetition of its previous
`
`briefing, but highlights (inter alia) the following facts: 1) a significant number of Invensys’
`
`documents and witnesses are located in or near this district, 2) Defendants’ witnesses and
`
`documents are not concentrated in Colorado because all of Emerson’s evidence is located in
`
`Missouri, 3) some third-party witnesses are located in Texas while none appear to be in
`
`Colorado, and 4) Texas has a special connection to the subject matter of this suit that Colorado
`
`does not share.1 Transfer would be improper under these circumstances.
`
`1 Emerson continues to insist that it is not a proper party to this case. See id. at 1 n.1. Of course, even the cases
`Defendants cite hold that the merits of a case are “irrelevant to the determination of the preliminary question of
`
`EAST\56132731.6
`
`2
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 3 of 8 PageID #: 1418
`
`ARGUMENT
`
`I.
`
`None of the Cases Defendants Cite Support a Stay in This Case.
`
`The appellate decisions Defendants rely on principally involve mandamus petitions
`
`challenging the denial of a transfer motion in which the defendant complained (only sometimes
`
`successfully) that the district court improperly relied on its own delay in ruling on the transfer
`
`motion as a basis for retaining the case. Indeed, In re: Horseshoe Entertainment, 337 F.3d 429
`
`(5th Cir. 2003), In re EMC Corp., Misc. No. 142, 2013 WL 324154 (Fed. Cir. Jan. 29, 2013),
`
`and In re VTech Communications, Inc., Misc. No. 909, 2010 WL 46332 (Fed. Cir. Jan. 6, 2010),
`
`do not even mention a stay by the district court, and the EMC court apparently denied a request
`
`to stay the district court proceedings pending a ruling on the mandamus petition.2 See 2013 WL
`
`324154, at *3. Collectively, Defendants’ cases merely stand for the unexceptional proposition
`
`that district courts should resolve transfer motions promptly. Most involved substantial delays in
`
`ruling on a transfer motion (far in excess of the reasonable time lapse in the instant case) or
`
`readily distinguishable facts, and none suggest
`
`that a stay is always, or even usually,
`
`appropriate.3
`
`Horseshoe Entertainment, on which all the Federal Circuit decisions Defendants cite
`
`relied, is particularly telling. In Horseshoe Entertainment, the district court inexplicably waited
`
`transfer.” In re Fusion-IO, Inc., Misc. No. 139, 2012 WL 6634939, at *1 (quoting McDonnell Douglas Corp. v.
`Polin, 429 F.3d 30, 30-31 (3d Cir. 1970)). In addition, Emerson’s protests that it is not a proper party are limited
`to an assertion that it does not directly infringe, completely ignoring the fact that Invensys has also sued Emerson
`for indirect infringement.
`2 In re Fusion-IO, Inc., Misc. No. 139, 2012 WL 6634939, at *1 (Fed. Cir. Dec. 21, 2012), did mention a motion to
`stay, but nothing in that opinion purports to mandate a stay as a matter of course.
`3 None of the cases Defendants cite for the stay standard involved a request for a stay pending resolution of a
`transfer motion and all involved facts radically different than this case. See Landis v. N. Am. Co., 299 U.S. 248
`(1936) (granting stay to await Supreme Court decision); Esquivel v. BP Co. N. Am., Inc., Civ. No. B-10-227, 2010
`WL 4255911 (S.D. Tex. Oct. 14, 2010) (granting stay of case arising out of the Deep Water Horizon disaster
`pending resolution of MDL request); Nguyen v. BP Exploration & Prod., Inc., Civ. No. H-10-2484, 2010 WL
`3169316 (S.D. Tex. Aug. 9, 2010) (same); Soverain Software LLC v. Amazon.com, Inc., 356 F. Supp. 2d 660, 662
`(E.D. Tex. 2005) (denying stay pending reexamination).
`
`EAST\56132731.6
`
`3
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 4 of 8 PageID #: 1419
`
`thirteen months to rule on a transfer motion, and when it finally denied the motion, it clearly
`
`abused its discretion by considering irrelevant factors and ignoring relevant factors. See 337
`
`F.3d at 433-34. In contrast, briefing on the transfer motion in this case was completed only two
`
`months ago, and Defendants lack a strong basis for changing venue.
`
`Similarly, in EMC it apparently took years for the district court to address the transfer
`
`motion, and then the court improperly used its own delay in ruling on the motion to find that
`
`judicial economy weighed against transfer. See 2013 WL 324154, at *2. Significantly, despite
`
`this error the Federal Circuit still concluded that the district court had acted properly in denying
`
`transfer. See id. at *2-3.
`
`In In re Fusion-IO, Inc., Misc. No. 139, 2012 WL 6634939 (Fed. Cir. Dec. 21, 2012),
`
`(which was styled Solid State Storage Solutions, Inc. v. STEC, Inc., No. 2:11-cv-391-JRG-RSP
`
`in the district court), the district court did issue a stay, but the transfer issue had been pending for
`
`almost a year by that time. See Def. Fusion-IO’s Mot. to Stay Proceedings Pending Resolution
`
`of Renewed Mot. to Transfer in Accord with Fed. Cir.’s Mandamus Order at 1, Solid State (E.D.
`
`Tex. Dec. 26, 2012), ECF No. 284.
`
`Defendants’ reliance on VTech Communications, the only other Federal Circuit authority
`
`Defendants’ cite, is perplexing.4 VTech Communications not only denied mandamus, but also
`
`expressly distinguished Horseshoe Entertainment. See 2010 WL 46332, at *2 (“Although there
`
`may have been some delay, we do not read Horseshoe as precluding the district court from
`
`4 The passage from VTech Communications Defendants quote was actually the court chiding VTech for its lack of
`zeal in pursuing its transfer motion. See id. at *2 (“It was incumbent on VTech to actively and promptly pursue
`its motion to transfer venue before the district court invested considerable time and attention to discovery and
`completing claim construction.”). Invensys does not dispute that Defendants’ transfer motion was timely.
`
`EAST\56132731.6
`
`4
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 5 of 8 PageID #: 1420
`
`considering its investment and familiarity with the case when determining the prudence of
`
`transfer.”).5
`
`Unlike Horseshoe Entertainment and its progeny, all of which involved delays of a year
`
`or more, briefing on Defendants’ transfer motion was completed only two months ago. Because
`
`it must balance a multiplicity of factors under the § 1404(a) standard and review the evidence
`
`submitted by the parties, the Court cannot be expected to rule on Defendants’ transfer motion
`
`instantaneously, but must be permitted adequate time to exercise its discretion. Moreover, unlike
`
`the defendants in Horseshoe Entertainment, Defendants in this case lack a strong basis for
`
`seeking transfer. Accordingly, a stay is unwarranted under the facts of this case.
`
`II.
`
`None of the Factors Defendants Cite Support a Stay.
`
`A.
`
`A Stay Will Prejudice Invensys, Especially Since Invensys and Defendants
`Are Direct Competitors.
`
`Defendants fail to explain why staying this case in its early stages is any less prejudicial
`
`to Invensys than staying it at a later time would be. Simply put, delay is delay. Moreover, a stay
`
`would be particularly harmful in this case since Invensys and Defendants are direct competitors
`
`in the coriolis flowmeter market, and Invensys is continuing to lose coriolis flowmeter sales as a
`
`result of Defendants’ infringement. While Defendants in this case take issue with the amount of
`
`time Invensys took to investigate its claims before filing suit, this is a complex, seven patent
`
`case, and Invensys should not be penalized for its thorough presuit investigation.
`
`B.
`
`There Is No Risk of Duplicative Litigation.
`
`The initial discovery in this case will principally concern the parties’ positions on claim
`
`construction,
`
`infringement, and invalidity and the production of Defendants’
`
`technical
`
`5 The remaining cases Defendants cite were all authored by a single district judge in the Western District of
`Tennessee. Those decisions seem to grant a stay pending consideration of a transfer motion as a matter of course.
`As explained below in Part II.C, routinely granting stays pending transfer requests encourages dilatory conduct,
`and the Tennessee court’s decisions should not be followed by this Court.
`
`EAST\56132731.6
`
`5
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 6 of 8 PageID #: 1421
`
`documents. This discovery will be necessary regardless of whether the Court transfers this case
`
`(and regardless of whether the District of Colorado has patent rules since this Court’s Patent
`
`Rules simply standardize the disclosure of information that would otherwise have to be obtained
`
`through interrogatories and document requests). See Network Caching Tech., LLC v. Novell,
`
`Inc., No. C-01-2079 VRW, 2003 WL 21699799, at *4 (N.D. Cal. Mar. 21, 2003) (noting that
`
`disclosure requirements in local patent rules take the place of multiple interrogatories that would
`
`otherwise need to be propounded);6 see also Suncast Techs., L.L.C. v. Patrician Prods., Inc., No.
`
`07-80414-CIV, 2008 WL 179648, at *9 (S.D. Fla. Jan. 17, 2008) (noting that “local patent rules
`
`embody the collective wisdom and experience of groups of judges and practicing patent lawyers”
`
`about the proper scope of discovery in patent cases). Thus, there is no risk that the parties or the
`
`courts will duplicate any work, and the initial paper discovery that may take place during the
`
`pendency of the transfer motion will not require travel by fact witnesses that might otherwise be
`
`avoided. And for the reasons set forth in its response to Defendants’ transfer motion, many of
`
`the relevant witnesses are located in Texas, Massachusetts, Missouri, and overseas anyway, not
`
`in Colorado as Defendants contend. See Pl.’s Resp. to Def.’s Mot. to Transfer Venue Pursuant to
`
`28 U.S.C. § 1404(a) at 9-14, ECF No. 26. Defendants’ claim that they will be prejudiced in the
`
`absence of a stay is nothing more than a red herring at this stage of the case.
`
`C.
`
`Granting a Stay Would Encourage Gamesmanship.
`
`“[A]s a delaying tactic [§ 1404(a)] has few equals.” 15 CHARLES ALLAN WRIGHT,
`
`ARTHUR R. MILLER & EDWARD H. COOPER, FEDERAL PRACTICE AND PROCEDURE § 3841, at 5 (3d
`
`ed. 2007) (quotations omitted). Transfer motions also divert the parties and the court “from their
`
`pursuit of the merits of a lawsuit while they argue about and decide where those merits may be
`
`6 Because the “Local Patent Rules of the Eastern District of Texas were modeled on the rules of the Northern
`District of California . . . interpretations of those rules by courts of the Northern District of California [are]
`persuasive authority.” Nike, Inc. v. Adidas Am., Inc., 479 F. Supp. 2d 664, 667 n.2 (E.D. Tex. 2007).
`
`EAST\56132731.6
`
`6
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 7 of 8 PageID #: 1422
`
`determined most conveniently.” Id. at 4 Routinely granting a stay whenever a defendant files a
`
`transfer motion would only exacerbate these problems and promote dilatory tactics.
`
`CONCLUSION
`
`Because Defendants’ motion to transfer has been fully briefed for only two months, a
`
`stay is completely unnecessary. In addition, the delay caused by a stay would prejudice Invensys
`
`without providing any benefit to Defendants or the judicial system. Accordingly, Invensys
`
`respectfully requests that the Court deny Defendants’ Motion to Stay Proceedings Pending
`
`Resolution of Defendants’ Motion to Transfer Venue Pursuant to 28 U.S.C. § 1404(a).
`
`Date:
`
`June 17, 2013
`
`Respectfully submitted,
`
`/s/ Claudia Wilson Frost
`Claudia Wilson Frost
`State Bar No. 21671300
`Jeffrey L. Johnson
`State Bar No. 24029638
`Amy P. Mohan
`State Bar No. 24051070
`DLA PIPER LLP
`1000 Louisiana, Suite 2800
`Houston, TX 77002
`Telephone: 713.425.8400
`Facsimile: 713.425.8401
`Claudia.Frost@dlapiper.com
`Jeffrey.Johnson@dlapiper.com
`Amy.Mohan@dlapiper.com
`
`Nicholas G. Papastavros
`Daniel Rosenfeld
`DLA PIPER LLP
`33 Arch Street, 26th Floor
`Boston, MA 02110
`Telephone: 617.406.6000
`Facsimile: 617.406.6100
`Nick.Papastavros@dlapiper.com
`Daniel.Rosenfeld@dlapiper.com
`
`ATTORNEYS FOR INVENSYS SYSTEMS, INC.
`
`EAST\56132731.6
`
`7
`
`

`
`Case 6:12-cv-00799-JRG Document 38 Filed 06/17/13 Page 8 of 8 PageID #: 1423
`
`CERTIFICATE OF SERVICE
`
`I certify that the foregoing document was filed electronically on June 17, 2013, pursuant
`to Local Rule CV-5(a) and has been served on all counsel who have consented to electronic
`service. Any other counsel of record will be served by first class U.S. mail on this same date.
`
`/s/ Claudia Wilson Frost
`Claudia Wilson Frost
`
`EAST\56132731.6
`
`8

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket