Feeds:
Posts
Comments

Posts Tagged ‘Inc.’

NOTE: Since there has been so much activity with the Siemens Product Lifecycle Management Software, Inc. software company (more out-of-the-court) and their lawsuits, I figured I would put all blog posts, etc. in one page for easy referencing. The original page can be found here.

SIEMENS PLM CASES (MAIN PAGE):

I have added this page for internet users who have become entangled in the Siemens Product Lifecycle Management Software, Inc. (a.k.a. “Siemens PLM Software”) cases.  The goal here is to keep up to date on this plaintiff, and to discuss their various cases.  Should you learn of any updates regarding one of their cases, please post it here using the following format — (e.g., “Siemens Product Lifecycle Management Software, Inc. v. John Does 1-100 (Case No. 4:17-cv-12345) filed in the U.S. District Court for the Southern District of Texas”).  Please also feel free to post new cases you find where Siemens Product Lifecycle Management Software, Inc. is listed as the plaintiff.

Siemens PLM has been known for suing John Doe Defendants across the US for the unauthorized use of their NX 7, NX 8, NX 8.5, NX 9, NX 10, NX 11, and Solid Edge ST9 Foundation software versions.  The lawsuits are all copyright infringement lawsuits filed in the Federal Courts, and each lawsuit sues for statutory damages of $150,000.

Remember to please exercise discretion when posting (e.g., do not post your real name or e-mail address), and as usual, avoid using vulgar or offensive language (both towards the plaintiff and towards other users).

CASE HISTORY OF THE SIEMENS PLM CASES:

Siemens Product Lifecycle Management Software, Inc., better known as “Siemens PLM Software” has been filing lawsuits against John Doe Defendants in federal courts across the US since 2011.

In 2011, Siemens PLM Software started their lawsuits in New York (NYSD) with two innocuous cases containing 50 John Doe Defendants which spanned NX 7 users living across the US. This led them to sue TWIVision Engineering Group, LLC in the Texas Eastern District Court (TXED) later in the year.

In 2012, they sued 50 John Doe Defendants in the Eastern District of Pennsylvania (PAED).

From 2012-early 2014, there was a lack of lawsuits from Siemens, but in 2014, they sued 100 John Doe Defendants AGAIN in New York (NYSD). Later, they again reached into Texas (TXED), but this time, they sued a number of engineering companies, including BTL Machine, Inc., and Mercury Metal Forming Technologies, LLC. They also initiated two John Doe lawsuits, Case Nos. 4:15-cv-00582, and 4:15-cv-00017.

2014-2015 Siemens continued its litigation strategy in the Texas Eastern District Courts for the remainder of 2015.

2016 was a busy year for Siemens PLM Software, as they filed large 100-Defendant cases against John Doe Defendants, this time in the Houston-based Texas Southern District Courts (TXSD). They also reached their individual lawsuits into both Ohio (OHSD) and Connecticut (CTD) where they sued Manufacturing Services International, Inc. and Demin, an individual defendant.

The cases of note currently in Texas are:
1) Siemens Product Lifecycle Management Software, Inc. v. Does 1-100 (Case No. 4:16-cv-01422), filed in May, 2016, and
2) Siemens Product Lifecycle Management Software Inc. v. Does 1-100 (Case No. 4:16-cv-03552), filed in December, 2016.

As of writing this page, most of the attention and controversy has been surrounding the December 4:16-cv-03552 case here in Texas.

SIEMENS PLM SOFTWARE STRATEGY:

In short, it appears as if the Siemens PLM Software strategy is as follows:
1) File a large 100+ Defendant lawsuit, encourage the court to approve early discovery allowing Siemens PLM to obtain the contact information for each of those 100+ John Doe Defendants.
2) Contact each of those defendants, convert accused defendants into paying customers (where the cost of the software can range from a few thousand dollars to tens of thousands of dollars).
3) Expand the lawsuit inquiry to the employer of the accused defendant engineer, and ascertain whether they have purchased volume licenses for their engineer employees.
4) Name and Serve and/or sue one or so defendants in a court outside the jurisdiction of the original court (this demonstrates that their reach is not limited to the courts in which they filed their original lawsuit). Unclear whether this is to obtain a $150,000 judgment for copyright infringement, or to convince that company to comply with their software licensing demands. I understand the goal of the lawsuits is to convert accused defendants into customers.
5) Proceed over the next three years contacting the various John Doe Defendants [even after the case is dismissed?]. File a new lawsuit against 100+ more John Doe Defendants, and repeat Steps 1-5.

BLOG POSTS:

How an attorney should handle a Siemens PLM Software, Inc. lawsuit, on 1/11/2017.
Siemens PLM NX-based lawsuits – converting accused engineers into loyal customers, on 1/9/2017.
Software Developers are now tracking piracy through the USE of downloaded software, on 9/9/2016.
Siemens Software Case IS a Bittorrent Case, on 6/20/2016.
What to do about the Siemens Product Lifecycle Management Software Inc. v. Does case (TX), on 1/16/2016.

LIST OF FEDERAL COURT CASES FILED (*UPDATED*):

IN THE CONNECTICUT DISTRICT COURT:
Siemens Product Lifecycle Management Software Inc. et al v. Demin (Case No. 3:16-cv-00553)

IN THE NEW YORK SOUTHERN DISTRICT COURT:
Siemens Product Lifecycle Management Software, Inc. v. Does 1 – 100 (Case No. 1:14-cv-01926)
Siemens Product Lifecycle Management Software, Inc. v. Does 1-50 (Case No. 1:11-cv-08469)

IN THE OHIO SOUTHERN DISTRICT COURT:
Siemens Product Lifecycle Management Software In v. Manufacturing Services International, Inc. (Case No. 3:16-cv-00182)

IN THE PENNSYLVANIA EASTERN DISTRICT COURT:
Siemens Product Lifecycle Management Software, Inc. v. Does 1-50 (Case No. 2:12-cv-06795)

IN THE TEXAS EASTERN DISTRICT COURT:
Siemens Product Lifecycle Management Software, Inc. v. BTL Machine, Inc. (Case No. 4:14-cv-00506)
Siemens Product Lifecycle Management Software, Inc. v. Does (Case No. 4:15-cv-00582)
Siemens Product Lifecycle Management Software, Inc. v. Mercury Metal Forming Technologies, LLC (Case No. 4:14-cv-00002)
Siemens Product Lifecycle Management Software Inc. v. Does (Case No. 4:15-cv-00017)
Siemens Product Lifecycle Management Software Inc. v. TWIVision Engineering Group, LLC (Case No. 6:11-cv-00679)

IN THE TEXAS SOUTHERN DISTRICT COURT:
Siemens Product Lifecycle Management Software Inc. v. Does (Case No. 4:16-cv-03552)
Siemens Product Lifecycle Management Software, Inc. v. Does 1-100 (Case No. 4:16-cv-01422)


CONTACT FORM: If you have a question or comment about what I have written, and you want to keep it *for my eyes only*, please feel free to use the form below. The information you post will be e-mailed to me, and I will be happy to respond.

NOTE: No attorney client relationship is established by sending this form, and while the attorney-client privilege (which keeps everything that you share confidential and private) attaches immediately when you contact me, I do not become your attorney until we sign a contract together.  That being said, please do not state anything “incriminating” about your case when using this form, or more practically, in any e-mail.

Read Full Post »

The bittorrent cases are speeding up, both in number of cases filed, and in the issues relating to the cases. Judges are smartening up to what is going on, and I am seeing the smaller “Does 1-23” cases ripped to shreds in the courts. But, because they are so small, the activities in each case are falling below the radar.

These smaller cases are now filed in the multiple courts across the country — the correct courts — with the John Doe Defendants often living in the states in which they are sued. Thus, there are no more motion to quash issues, and there are no more “wrong jurisdiction” arguments.

However, while NEARLY ALL the smaller lawsuits still have “improper joinder” issues (meaning, suing Does together in the same lawsuit who did not participate in the same swarm; thus, they did not take part in the same transaction at the same time), THE CASES ARE SIMPLY NOT GOING TO TRIAL and thus defendants are not getting the chance to contest improper joinder.

The problem with these smaller cases is that 1) the settlement amounts are elevated, and 2) the risk of being named as a defendant goes through the roof because all that is required to name defendants in these smaller cases is that the plaintiff merely needs to amend the complaint against a particular Doe (thus the case will change from Patrick Collins, Inc. v. Does 1-30 to Patrick Collins v. “Elliot Hendel” and Does 1-29 [this name is merely fictitious]), and then someone comes knocking at Elliot’s home and serves him a copy of the complaint. At that point if he has not already done so [and he should have hired an attorney immediately upon having notice from his ISP that he was one of the Does in this case], he has to hire an attorney to respond within 20 days with his answer and his counterclaims, or he will default (which means the court can enter a default judgment against him for the full $150,000).

However, the BIG SECRET is that for the most part, these defendants do NOT get named as defendants, and they remain anonymous as far as what is visible from the court’s eyes. Instead, the plaintiff attorneys scare the b’jeebies out of them and cause them in some cases to sign [in many cases] an “I’m guilty, I’m sorry, I’ll never do it again” settlement agreement. The end result is that they end up paying significantly more than they would have if they merely called an attorney and had that attorney negotiate on their behalf. To make matters worse, defendants do not realize that there are really three-tiers of settlement prices (not two) — 1) the plaintiff attorney’s asking price (the “pay us $X by this date or else we’ll name you as a defendant in this case” amount), 2) defendant-negotiated price, and 3) attorney-negotiated price.

When the defendant tries to negotiate his settlement on his own, the likelihood is that he will probably say something incriminating about his case. (For example, not knowing the case law, he may say, “it wasn’t me; it was probably my son — he uses the internet all the time; I keep telling him not to watch that porn,” or “I let my neighbor / son / guest / roommate use my internet,” or “I didn’t realize it was illegal to download — I thought it was only illegal to upload!” etc.) The result is that the plaintiff says, “thank you for telling me you are guilty; the offer is now off the table and I will see you in court <click>,” only to call back shortly afterwards and, in the graces of his heart, he will offer a new settlement amount which is nearly double the asking price of the original settlement amount.

It is not only important to have an attorney negotiate your settlement amount 1) because he can, and 2) he won’t incriminate you while you would likely incriminate yourself, but also, the attorney knows the case law [which is not so obvious], and he knows what to put into a settlement agreement so that the settling defendant does not later get sued for the same claim, attorney fees, etc. It kills me to see so many people turn around and try to settle on their own without reading what they are agreeing to. What burns me more is when attorneys don’t read the contracts they have their clients agree to.

…In short, the plaintiff attorney mops up the floor with the defendants, and many of the defendants (if not most of them) turn over and lay dead while they capitulate and settle their cases. Had they lawyered-up, they would have known how to protect themselves. Better yet, their lawyer would have stepped in their shoes and the plaintiff attorneys would not have even been allowed to contact the defendants in the first place. No letters, no scare tactics; no threats.

Everything being said, one thing that most don’t even bother to find out is who exactly their plaintiff attorneys are. In more cases than not, the plaintiff attorney is merely a guy in a room with a laptop and a phone. Sometimes there is a second lawyer guy in the room making phone calls scaring the defendants into settling — a two-man show. …Do you really think this one or two-man show actually has the ability to sue more than just a few defendants, and if you defendants lawyered-up, do you think the plaintiff attorneys would have the time to name each and every one of you? AND if they named each and every one of you (which is literally impossible because to serve each one of you with service of process would be nearly impossible to track and there are bound to be significant errors), do you think they would have time to respond to each and every one our discovery requests?

As your attorney, when I defend you, I have a duty to properly protect your interests. That means that us attorneys must establish evidence that calls into question their so-called experts’ methods in collecting IP addresses (see here for just a taste). We need to call into question their methods of suing multiple Does in one lawsuit. We need to fight them procedurally with motions to dismiss, motions for summary judgement, and in some cases, motions for sanctions.

Do you think that the one-man show attorney and their underlying plaintiff (too often, the porn production company) can handle the hours of deposition time that EACH OF YOU DEFENDANT would be entitled to? What about their so-called experts? Do you think they have the time to answer all our in-person depositions for each defendant? What about our interrogatories? What about our other discovery motions? Do you really think the one-man show — the attorney guy in the room with a laptop — has the time to spend going after each one of you when he can instead go after the unrepresented defendants who roll over and settle their cases?

To make these cases merely insulting, these plaintiff attorneys have been hiring no-name local-counsel attorneys to file their cases on their behalf (no disrespect to any of them; I understand they are doing it solely so that they can make a commission off of those who settle). As far as I understand, the local counsel often know absolutely NOTHING about these cases, but they talk a big game and then sheepishly refer you to someone else — an “in-house” negotiator, or the attorney behind the curtain — so that they can “close” the deal for them and scare you into settling. If you actually had us attorneys defend your cases rather than merely have us settle them, do you really think the BIG-8 ATTORNEYS (listed below) would have the time and the patience to babysit these local counsel when they ask for assistance after we file our own motions for discovery?

Thus, a client in these smaller Does 1-20 (or 1-50, or 1-80) cases does not need to settle, especially if they do not live in the jurisdiction in which they are sued. This is true regardless of whether the plaintiff attorney is Dunlap Grubb & Weaver (Nicholas Kurtz or Ellis Bennett), Steele Hansmeier (John Steele or Mark Lutz), Gill Sperlein, Ira Siegel, Keith Lipscomb, or even Marc Randazza.

We do know how to defend these smaller cases.

Read Full Post »

Congratulations to our clients and to all defendants in the “CP Productions, Inc. v. Does 1-300” case (1:10-cv-06255), dismissed in the US District Court for the Northern District of Illinois. While at first glance this case appears to be a no-name media company attempting to enforce their copyrights using the mass tort copyright infringement “John Doe” model, there *is* real significance to this case.

This is one of the first cases in the US District Court for the Northern District of Illinois to have been dismissed. It was dismissed by Judge Milton I. Shadur, a Senior United States District Judge. More importantly, this is John Steele’s (of the Steele Law Firm LLC — now Steele Hansmeier, LLC) home court where a majority of his other cases have been filed. Have you heard any of his other cases filed there (just to name a few)?

Millenium TGA, Inc. v. Does 1-100 (1:10-cv-05603)
Lightspeed Media Corporation v. Does 1-100 (1:10-cv-05604)
Hard Drive Productions, Inc. v. Does 1-1000 (1:10-cv-05606)
First Time Videos LLC v. Does 1-500 (1:10-cv-06254)
Future Blue, Inc. v. Does 1 – 300 (1:10-cv-06256)
MGCIP, LLC v. Does 1-316 (1:10-cv-06677)
MCGIP, LLC v. Does 1-1,164 (1:10-cv-07675) [no misspelling there]
Achte/Neunte Boll Kino Beteiligungs GMBH & Co KG v. Novello (1:11-cv-00898)
Achte/Neunte Boll Kino Beteiligungs GMBH & Co KG v. Famula (1:11-cv-00903)

As you can see, a lot is riding on these cases, and one dismissal creates a ripple effect which will likely affect the others. This is what happened in Evan Stone’s Larry Flynt Productions (LFP Internet Group, LLC) cases and related cases which were all dismissed in the US District Court for the Northern District of Texas all at once. Here, the judge’s order (which you can either find online or you can e-mail me) was quite explicit in his reasons for dismissing the case. No doubt the other judges for the cases I listed above will take notice of this dismissal.

For more information on the case, Ars Technica website had a nice write-up on it in their “Random defendant outlawyers P2P attorney, gets lawsuit tossed” article. The 99 comments (as of the posting of this article) are also very telling and informative.

Read Full Post »