throbber
Case 6:12-cv-00799-JRG Document 128-1 Filed 03/11/14 Page 1 of 3 PageID #: 3985
`Case 6:12—cv—00799—JRG Document 128-1 Filed 03/11/14 Page 1 of 3 Page|D #: 3985
`
`EXHIBIT 1
`
`EXHIBIT 1 

`
`

`
`Case 6:12-cv-00799-JRG Document 128-1 Filed 03/11/14 Page 2 of 3 PageID #: 3986
`
`
`ATTORNEYS AT LAW
`
`
`FOLEY & L ARDN ER LLP
`
`
`MARCH 10, 2014
`
`777 EAST WISCONSIN AVENUE
`MILWAUKEE, WI 53202-5306
`414.271.2400 TEL
`414.297.4900 FAX
`foley.com
`
`CLIENT/MATTER NUMBER
`087886-0122
`
`The Honorable Leonard Davis
`U.S. District Court for the Eastern District of Texas
`200 W. Ferguson, Third Floor
`Tyler, TX 75702
`
`Invensys Systems, Inc. v. Emerson Electric Co. and Micro Motion, Inc.
`Civil Action No. 6:12-cv-00799-LED
`
`
`
`Re:
`
`
`Dear Judge Davis:
`
`
`For the reasons stated in Emerson’s letter brief (Dkt. No. 109-1) regarding its motion to
`strike certain portions of Invensys’s Sur-reply to Emerson’s Motion for Summary Judgment of Non-
`Infringement (Dkt. 108, hereinafter “Sur-reply”), and for the additional reasons stated below,
`Sections I and II of that Sur-reply should be stricken.
`
`I.
`
`Invensys’s Sur-Reply Contains Inaccurate Representations of the Record.
`
`The record evidence states: “EPM is a business platform (a brand) used by various Emerson
`subsidiaries.” (Dkt. No. 106 at 3 (citing references).) “EPM is not a legal business entity of any
`type.” (Id.) “[EPM] is simply a platform name used to identify various Emerson subsidiaries that
`are in the process management business.” (Id.)
`
`In its Sur-reply, Invensys takes an unjustified leap and contends that these statements
`constitute an admission by Emerson that EPM is “a division of Emerson.” (Dkt. No. 108 at 1.)
`None of the citations provided by Invensys support its proposition. In its answering letter brief,
`Invensys implicitly concedes the lack of evidence that EPM is a “division” of Emerson when it
`argues that its own definition of division “necessarily” justifies that position. (Dkt. No. 116-1 at 2
`(“EPM is necessarily a division of Emerson (since a division is, by definition, an unincorporated
`administrative or organizational structure within a larger business entity.”).) Nothing supports
`Invensys’s claim, as EPM is not an administrative or organizational structure within Emerson.
`Rather, the record reflects that Emerson owns a number of subsidiaries. (Dkt. No. 106-1 at ¶¶ 4-6.)
`It uses the name EPM as a way to refer to those subsidiaries that sell products that manage
`manufacturing processes. EPM is a brand name, and has no employees. (Id.) Invensys should
`simply not be able to argue that EPM is a “division” when the record evidence states that EPM is a
`business platform or brand used by various Emerson subsidiaries. Invensys’s characterization of the
`record is inaccurate and should be stricken from Invensys’s briefing.
`
`II.
`
`Emerson Did Not Raise New Issues In Its Letter Brief.
`
`Invensys incorrectly contends that its Sur-reply did not contain any new arguments except for
`those needed to respond to the allegedly new evidence and arguments raised in Emerson’s Reply
`brief. (Dkt. No. 116-1 at 3.) However, Invensys’s Sur-reply brief argues, for the first time, that
`
`
`BOSTON
`BRUSSELS
`CHICAGO
`DETROIT
`
`JACKSONVILLE
`LOS ANGELES
`MADISON
`MIAMI
`
`MILWAUKEE
`NEW YORK
`ORLANDO
`SACRAMENTO
`
`SAN DIEGO
`SAN DIEGO/DEL MAR
`SAN FRANCISCO
`SHANGHAI
`
`SILICON VALLEY
`TALLAHASSEE
`TAMPA
`TOKYO
`WASHINGTON, D.C.
`
`4820-5676-0089.
`
`

`
`Case 6:12-cv-00799-JRG Document 128-1 Filed 03/11/14 Page 3 of 3 PageID #: 3987
`
`
`FOLEY & L ARDN ER LLP
`
`March 10, 2014
`Page 2
`
`
`certain activities of the so-called EPM employees and representatives should be imputed to Emerson
`by virtue of EPM’s status as a “division” and “organizational unit” of Emerson. Invensys has not
`denied that it could have made this argument much earlier. In fact, it could have made this argument
`at least as early as its response brief in opposition to Emerson’s motion for summary judgment.
`Waiting to raise the argument until the Sur-reply is too late as it improperly prevents Emerson from
`responding.
`
`III. The Remainder of Invensys’s Answering Letter Brief is Unproductive Posturing and, in
`any Event, it was Not Timely Filed.
`
`The remainder of Invensys’s answering letter brief constitutes attempts to shift blame onto
`Emerson. Emerson will not respond to such posturing other than to say that it is not productive and
`a waste of judicial resources.
`
`Last, this Court’s Standing Order Regarding Letter Briefs states that answering letter briefs
`shall be “filed with the Court no later than 14 days” after the opening letter brief is filed. Thus,
`Invensys’s answering brief should have been filed by February 26, 2014, which was 14 days after
`the February 12 filing of Emerson’s opening letter brief. Instead, Invensys filed its answering letter
`brief on March 3, 2014,1 at least five days late, and in violation of the Standing Order.2 (See Dkt.
`Nos. 115-1 & 116-1.) Accordingly, Invensys’s answering letter brief should be disregarded as
`untimely filed.
`
`Very truly yours,
`
`/s/ Kadie M. Jelenchick
`
`Kadie M. Jelenchick
`
`
`cc: all counsel of record (by ECF)
`
`
`
`1 Invensys was ordered to re-file its opposition letter brief on March 4, 2014 to comply with
`Court’s filing rules.
`2 Local Rule CV-6(a) does not give Invensys three additional days to its deadline because
`Rule CV-6(a) “applies only to responses due within a certain time after ‘service’ of a preceding
`document,” and the Court’s letter brief deadlines are not triggered off of “service.”

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