throbber
Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 1 of 21 PageID #: 1878
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`ALACRITECH, INC.,
`
`
`
`Plaintiff,
`
`Case No. 2:16-cv-693-JRG
`
`v.
`
`CENTURYLINK COMMUNICATIONS
`LLC, et al.
`
`
`Defendants.
`
`ALACRITECH, INC.,
`
`Plaintiff,
`
`v.
`
`WINSTRON CORPORATION, et al.,
`
`
`
`ALACRITECH, INC.,
`
`
`
`
`
`Defendants.
`
`LEAD CASE
`
`JURY TRIAL DEMANDED
`
`
`
`Case No. 2:16-cv-692-JRG
`
`JURY TRIAL DEMANDED
`
`MEMBER CASE
`
`
`
`Case No. 2:16-cv-695-JRG
`
`JURY TRIAL DEMANDED
`
`MEMBER CASE
`
`Plaintiff,
`
`Defendant.
`
`v.
`
`DELL INC.,
`
`
`
`
`PLAINTIFF ALACRITECH’S RESPONSE TO INTEL CORPORATION’S MOTION TO
`INTERVENE
`
`
`
`INTEL EX. 1417.001
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 2 of 21 PageID #: 1879
`
`
`TABLE OF CONTENTS
`
`Page
`
`FACTUAL BACKGROUND ..............................................................................................2 
`A. 
`Alacritech’s Claims Have Been Pending Since June 2016 ......................................2 
`B. 
`Intel Has Been Aware Of This Litigation For Months ............................................2 
`C. 
`Negotiation, Briefing, and Judicial Decisions on Case-Governing Orders
`Has Taken Place That Should Not Be Interrupted By Intel’s Request To
`Intervene ..................................................................................................................3 
`Intel Delayed Filing Its Motion To Intervene ..........................................................4 
`D. 
`LEGAL STANDARD ..........................................................................................................5 
`ARGUMENT .......................................................................................................................6 
`A. 
`Intel’s Motion Is Untimely If It Will Disrupt The Existing Schedule .....................6 
`Intel Failed To Apply For Intervention As Soon As It Knew Of Its
`1. 
`Purported Interest In This Case ....................................................................6 
`The Circumstances Of Intel’s Intervention Demonstrate That It Is
`Untimely If It Executes Its Plan to Derail The Case ....................................9 
`Intel Is Not An Intervenor Of Right .......................................................................10 
`1. 
`Intel Does Not Have A Sufficient Interest In The Litigation .....................10 
`2. 
`Any Interest Intel May Have Is Already Adequately Protected ................12 
`Intel’s Permissive Intervention Is Appropriate As Long As Intel Can Show
`Its Intervention Will Not Prejudice Alacritech ......................................................13 
`CONCLUSION ..................................................................................................................15 
`
`2. 
`
`B. 
`
`C. 
`
`I. 
`
`II. 
`III. 
`
`IV. 
`
`
`
`
`i
`
`INTEL EX. 1417.002
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 3 of 21 PageID #: 1880
`
`
`TABLE OF AUTHORITIES
`
`Cases
`
`Page
`
`Amicus, Inc. v. Post-Tension of Texas, Inc.,
`Civ. A. No. H-85-5849, 1986 WL 13012 (S.D. Tex. 1986) ....................................................12
`
`Bush v. Viterna,
`740 F.2d 350 (5th Cir. 1984) .............................................................................................12, 13
`
`Chandler & Price v. Brandtjen & Kluge,
`296 U.S. 53 (1935) ...................................................................................................................10
`
`Corely v. Jackson Police Dep't,
`755 F.2d 1207 (5th Cir. 1985) .......................................................................................1, 5, 6, 9
`
`Deus v. Allstate Ins. Co.,
`15 F.3d 506 (5th Cir. 1994) .....................................................................................................10
`
`Edwards v. City of Houston,
`78 F.3d 983 (5th Cir. 1996) (en banc) .......................................................................................5
`
`Frazier v. Map Oil Tools, Inc.,
`Civil Action No. C-10-4, 2010 WL 2352056 (S.D. Tex. 2010) ......................................7, 8, 13
`
`Honeywell Int'l, Inc. v. Audiovox Commc'ns Corp.,
`Civ. A. 04-1337-KAJ, 2005 WL 2465898 (D. Del. May 18, 2005) ....................................8, 11
`
`Intellectual Ventures I LLC v. AT&T Mobility LLC,
`C.A. No. 12-193-LPS, 2014 WL 4445953 (D. Del. Sept. 8, 2014) .........................................11
`
`Katz v. Lear Siegler, Inc.,
`909 F.2d 1459 (Fed. Cir. 1990)................................................................................................11
`
`Kneeland v. Nat'l Collegiate Athletic Ass'n,
`806 F.2d 1285 (5th Cir. 1987) ...................................................................................7, 9, 12, 13
`
`Peoples v. Aldine Indep. Sch. Dist.,
`2008 WL 2571900 (S.D. Tex. Jun. 19, 2008) ..........................................................................14
`
`Reid v. General Motors Corp.,
`240 F.R.D. 257 (E.D. Tex. 2006) ...............................................................................................8
`
`Ross v. Marshall,
`426 F.3d 745 (5th Cir. 2005) ...................................................................................................12
`
`Sierra Club v. Espy,
`18 F.3d 1202 (5th Cir. 1994) .....................................................................................................6
`
`Staley v. Harris Cnty.,
`223 F.R.D. 458 (S.D. Tex. 2004) ...............................................................................1, 2, 5, 6, 7
`
`
`
`ii
`
`INTEL EX. 1417.003
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 4 of 21 PageID #: 1881
`
`
`Stallworth v. Monsanto Co.,
`558 F.2d 257, 264-66 (5th Cir. 1977) ....................................................................................5, 9
`
`Tegic Communications Corp. v. Board of Regents,
`296 U.S. 53 (1935); 458 F.3d 1335 (Fed. Cir. 2006) ...............................................................10
`
`TiVo, Inc. v. AT&T, Inc.,
`Civil Action No. 2:09-CV-259, 2010 WL 10922068 (E.D. Tex. Mar. 31, 2010) ...............8, 13
`
`TravelSource Corp. v. Old Republic Int’l,
`No. 85 C 8116, 1986 WL 3848 (N.D. Ill. Mar. 14, 1986) .........................................................8
`
`Statutes
`
`Fed. R. Civ. P. 24 .....................................................................................................1, 4, 5, 7, 10, 13
`
`Fed. R. Civ. P. 24(a) ..................................................................................................................5, 10
`
`Fed. R. Civ. P. 24(b) ............................................................................................................5, 13, 15
`
`Other Authorities
`
`A. Wright & Arthur R. Miller, Federal Practice and Procedure § 1922 ........................................15
`
`
`
`
`
`iii
`
`INTEL EX. 1417.004
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 5 of 21 PageID #: 1882
`
`
`Alacritech does not oppose intervention by Intel so long as it is timely and non-
`
`prejudicial – i.e., it does not undermine the existing orders and schedule already adopted by the
`
`Court. But neither Rule 24 nor fundamental considerations of fairness permit a putative
`
`intervenor to manipulate the timing of its intervention in order to disrupt or delay the case
`
`schedule in a pending lawsuit to the detriment of the plaintiff. Indeed, the Fifth Circuit has
`
`characterized the timeliness of a movant’s request to intervene as a “threshold” issue and denied
`
`intervention when a movant’s delay threatened to derail the orderly progress of the litigation.1
`
`Thus, as Alacritech told Intel, Alacritech does not oppose Intel’s intervention, so long as Intel
`
`would agree to be bound by orders currently governing this case. Intel would have acceded to
`
`this reasonable request if its interest in intervention were simply to protect its alleged financial
`
`interest in the litigation. But Intel refused. As its Motion indicates, it wants to intervene and
`
`attempt to re-do the case schedule and other orders governing the case. This is not allowed.
`
`Intel cannot have it both ways: either intervention is timely and appropriate because it
`
`will not disrupt the existing case schedule and other orders, or it is not timely and not appropriate
`
`because it will. More simply, Intel should not be able to intervene and, through its intervention,
`
`create the prejudice Rule 24 is designed to protect against, namely, the parties’ and Court’s
`
`interests in the efficient, expeditious resolution of the issues in dispute.2 For this reason,
`
`Alacritech respectfully requests that the Court condition Intel’s intervention on Intel’s agreement
`
`to abide by the existing orders, including the Protective Order (Dkt. 75), Docket Control Order
`
`(Dkt. 43), and Discovery Order (Dkt. 50), and not revisit briefing or otherwise seek to delay the
`
`proceedings or undermine this Court’s authority.
`
`
`1 Corely v. Jackson Police Dep’t, 755 F.2d 1207, 1209 (5th Cir. 1985).
`2 Staley v. Harris Cnty., 223 F.R.D. 458, 463 (S.D. Tex. 2004).
`
`
`
`1
`
`INTEL EX. 1417.005
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 6 of 21 PageID #: 1883
`
`
`I.
`
`FACTUAL BACKGROUND
`
`A.
`
`Alacritech’s Claims Have Been Pending Since June 2016
`
`On June 30, 2016, Plaintiff Alacritech, Inc. (“Alacritech”) filed suit against several
`
`providers of network server systems and services, such as end-to-end Data Centers and Cloud
`
`solutions, that utilize Alacritech’s patented inventions without its permission. Among the
`
`defendants accused of infringement is Dell Inc. (“Dell”). Alacritech’s Complaints against Dell
`
`and the other defendants are each approximately a hundred (100) pages long. (Dkt. 1.) The
`
`Complaints include detailed allegations regarding Alacritech’s claims, Defendants’ accused
`
`products (including components manufactured by Intel3), and the manner in which Defendants’
`
`practice the claimed inventions on an element-by-element basis certain, exemplary claims of
`
`Alacritech’s patents. For example, the Dell Complaint identifies over fifty (50) specific Dell
`
`products and categories of products that support and/or practice the infringing LSO, RSC,
`
`InfiniBand, and/or RoCE functionality. (Id.)
`
`B.
`
`Intel Has Been Aware Of This Litigation For Months
`
`Shortly after being served, it appears that “Dell tendered a contractual claim that Intel
`
`indemnify and hold it harmless against Alacritech’s claims based on an indemnity agreement
`
`involving the purchase of Intel products.” (Mot. at 4.) Based thereon, Intel agreed to defend and
`
`“partially indemnify” Dell. (Id. at 5 (citing Kyriacou Decl. ¶¶ 2-3).) Though Intel has refused to
`
`indicate exactly when it agreed to defend Dell or the scope of its partial indemnification
`
`commitment, Intel does not dispute that it has been aware of this case and participating in Dell’s
`
`defenses since around the time the lawsuit was filed, four months ago. (Dkt. 71-3 at 2
`
`(10/21/2016 C. Stern email to G. Stephens); Ex. 1 (10/24/2016 J. Paunovich email to G.
`
`Stephens and related string) (“We note that Intel does not dispute that it has known about this
`
`3 One such identified component is Intel’s 82599 10GbE Controller. (E.g., id. ¶¶ 34, 35.)
`
`
`
`2
`
`INTEL EX. 1417.006
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 7 of 21 PageID #: 1884
`
`
`case for nearly 4 months . . . .”).) Despite this awareness, Intel did not move to intervene until
`
`October 31, 2016.
`
`C.
`
`Negotiation, Briefing, and Judicial Decisions on Case-Governing Orders Has
`Taken Place That Should Not Be Interrupted By Intel’s Request To
`Intervene
`
`As Intel acknowledges in its Motion, since inception of the litigation in June 2016, the
`
`parties have briefed several issues and the Court has entered several orders governing the scope
`
`and process of the litigation. For example, Dell answered the Complaint on August 25, 2016.
`
`(Dkt. 27.) The Court held a Scheduling Conference on August 30, 2016. On September 9, 2016,
`
`Alacritech served infringement contentions on all parties.
`
`The parties filed their stipulated Docket Control Order on September 14 and it was
`
`entered on September 15. (Dkt. 42, 43.) The parties filed their stipulated Discovery Order on
`
`September 20 and it was entered on September 23. (Dkt. 45, 50.) Resolution of the procedural
`
`and substantive issues presented in the Docket Control and Discovery Orders required extended
`
`negotiations and effort by all eight (8) parties to the consolidated actions represented by six (6)
`
`local and national law firms who signed the joint requests.
`
`On September 27, 2016, following substantial negotiation, the parties filed a Joint
`
`Motion for Adoption And Resolution Of Disputed Issues With Respect To Protective Order.
`
`(Dkt. 55.) The majority of the provisions of the proposed Protective Order were agreed upon by
`
`all parties with the exception of two issues, which were briefed for the Court. (Dkt. 55 at 6.)
`
`The Court entered the stipulated Protective Order on November 8, 2016. (Dkt. 75.)4
`
`
`4 The Court entered the language proposed by Defendants limiting designation of Alacritech’s
`infringement contentions to “confidential information” that does not exclusively comprise “the
`parties’ legal theories of infringement and invalidity.” (Dkt. 75 at ¶ 6.) However, Intel had
`already agreed to provide indemnity to Dell in this matter based on Alacritech’s allegations in its
`Complaints against Defendants. As such, Intel cannot credibly claim that the designation of
`Alacritech’s infringement contentions delayed its intervention.
`
`
`
`3
`
`INTEL EX. 1417.007
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 8 of 21 PageID #: 1885
`
`
`D.
`
`Intel Delayed Filing Its Motion To Intervene
`
`Counsel for Intel spoke with Alacritech for the first time on October 13, 2016 to ask
`
`whether Alaritech would consent to Intel intervening in the matter against Dell. (Dkt. 71-3 at 6-
`
`7 (10/13/2016 G. Stephens email to J. Paunovich).) Initially, Alacritech agreed not to oppose
`
`Intel’s intervention as long as it complied with Rule 24’s requirement that intervention not
`
`prejudice Alacritech or burden the Court. (Id. at 5-6 (10/14/2016 C. Stern email to G.
`
`Stephens).) For example, Alacritech asked that Intel move expeditiously, maintain the existing
`
`Docket Control Order, and not take action to undermine the previously-entered orders or the
`
`expeditious resolution of the litigation as a whole. (Id.; see also id. at 10/21/2016 C. Stern
`
`email.) Intel indicated that it did not have any problem with the Discovery Order or E-Discovery
`
`Order, but implied that it would object to the existing case schedule unless Alacritech agreed to
`
`forgo its right to bring counterclaims against Intel that “change the scope of the case.” (Id. at 2-
`
`3.) Intel further indicated its intent to challenge the previously-agreed upon provisions of the
`
`Protective Order and demand special provisions for Intel. (Id.)
`
`Unwilling to give up its right (and potentially its obligation) to counterclaim against Intel
`
`or to resurrect the previously negotiated case schedule and briefed issues, Alacritech nonetheless
`
`urged Intel to move to intervene promptly in a manner that would not “change the case
`
`schedule/deadlines or require the Court and Alacritech to revisit and rebrief issues.” (Id. at 1-2
`
`(10/21/2016 C. Stern email to G. Stephens); see also Ex. 1 (10/24/2016 email from J. Paunovich
`
`to G. Stephens).) On October 21, Intel sent a final email stating its refusal to reach an agreement
`
`on the appropriate schedule or conditions of Intel’s intervention. (Id. at 1 (10/21/2016 G.
`
`Stephens email to C. Stern.) Intel then waited another week before filing the present motion to
`
`intervene. (Dkt. 71 (filed 10/31/2016).)
`
`
`
`4
`
`INTEL EX. 1417.008
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 9 of 21 PageID #: 1886
`
`
`II.
`
`LEGAL STANDARD
`
`Federal Rule of Civil Procedure 24 provides in relevant part that a party is entitled to
`
`intervene by right where it “claims an interest relating to the property or transaction that is the
`
`subject of the action, and is so situated that disposing of the action may as a practical matter
`
`impair or impede the movant’s ability to protect its interest, unless existing parties adequately
`
`represent that interest.” A Court also may permit a party to intervene on timely motion where it
`
`“has a claim or defense that shares with the main action a common question of law or fact.” (Id.)
`
`However, “[i]n exercising its discretion, the court must consider whether the intervention will
`
`unduly delay or prejudice the adjudication of the original parties’ rights.” (Id.)
`
`“The threshold consideration of any motion to intervene is timeliness.” Corley v.
`
`Jackson Police Department, 755 F.2d 1207, 1209 (5th Cir. 1985). “The law governing Rule
`
`24(a)(2) and (b) emphasizes the importance of timeliness as an indispensable factor.” Staley v.
`
`Harris County, 223 F.R.D. 458, 461 (S.D. Tex. 2004) (emphasis added). “If an applicant for
`
`intervention cannot satisfy the timeliness factor, the court need not address the Rule’s other
`
`requirements” and should simply reject the request for intervention. Id. (citing Edwards v. City
`
`of Houston, 78 F.3d 983, 999 (5th Cir. 1996) (en banc)).
`
`In Stallworth v. Monsanto Co., the Fifth Circuit “distilled four factors to be weighed in
`
`determining whether a motion to intervene,” under either Rule 24(a) or (b) is timely:
`
`Factor 1. The length of time during which the would be intervenor actually knew
`or reasonably should have known of his interest in the case before he petitioned
`for leave to intervene . . .
`
`Factor 2. The extent of the prejudice that the existing parties to the litigation may
`suffer as a result of the would-be intervenor’s failure to apply for intervention as
`soon as he actually knew or reasonably should have known of his interest in the
`case . . . .
`
`Factor 3. The extent of the prejudice that the would-be intervenor may suffer if
`his petition for leave to intervene is denied . . . .
`
`
`
`5
`
`INTEL EX. 1417.009
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 10 of 21 PageID #: 1887
`
`
`Factor 4. The existence of unusual circumstances militating either for or against a
`determination that the application is timely.
`
`Corley, 755 F.2d at 1209 (quoting Stallworth, 558 F.2d 257, 264-66 (5th Cir. 1977)). The sum
`
`of the factors underscores that to be timely, the would-be intervenor must file its motion as soon
`
`as it becomes aware “that it ha[s] some stake in the action” and, further, that any delay that
`
`causes prejudice is a basis for denying the request. Staley, 223 F.R.D. at 462 (citing Sierra Club
`
`v. Espy, 18 F.3d 1202, 1206 (5th Cir. 1994)).
`
`III. ARGUMENT
`
`A.
`
`Intel’s Motion Is Untimely If It Will Disrupt The Existing Schedule
`
`As a predicate matter, Intel acknowledges in its Motion that it did not immediately move
`
`to intervene when it realized that certain of its products were components in Defendants’ accused
`
`products – a fact evident from the face of Alacritech’s Complaints. Thus, having intentionally
`
`delayed filing it motion, Intel can only meet the requirement of “timeliness” if it proves that
`
`intervention will not result in prejudice to the existing parties to the litigation.
`
`1.
`
`Intel Failed To Apply For Intervention As Soon As It Knew Of Its
`Purported Interest In This Case
`
`In its Motion, Intel does not genuinely dispute that it delayed filing its Motion. Corley,
`
`755 F.2d at 1209 (holding that failure to promptly move to intervene eradicates the would-be
`
`intervenor’s rights when the delay would cause prejudice to the existing parties and litigation ).
`
`Intel expressly states that it was aware of Alacritech’s Complaints, filed on June 30, 2016 (Mot.
`
`at 3), that the Complaints “identify Intel products” as being part of the accused systems (Mot. at
`
`3-4), and that based on the allegations of the Complaint against Dell, “Intel . . . agreed to defend
`
`and partially indemnify Dell.” (Mot at 5). Thus, all of the information upon which Intel now
`
`bases its assertion that it “has a compelling interest in the litigation,” including that the “accused
`
`products incorporate components manufactured” by Intel (Mot. at 7) were known to it in or
`
`
`
`6
`
`INTEL EX. 1417.010
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 11 of 21 PageID #: 1888
`
`
`around June 2016, four months before it filed this motion. During the parties’ correspondence,
`
`Intel acknowledged as much, but provided no justification for its delays in either moving to
`
`intervene or seeking Alacritech’s stipulation to its intervention. See Dkt. 71-3 at 2 (10/21/2016
`
`C. Stern email to G. Stephens); Ex. 1 (10/24/2016 J. Paunovich email to G. Stephens). Having
`
`intentionally delayed filing its Motion, Intel’s request cannot be granted unless it proves that
`
`intervention will not prejudice the existing parties or the sanctity of the proceedings. Compare
`
`Kneeland v. Nat’l Collegiate Athletic Ass’n, 806 F.2d 1285, 1289 (5th Cir. 1987) (finding motion
`
`to intervene filed four months after the lawsuit was removed from state court to be untimely
`
`where it would cause prejudice); Frazier v. Map Oil Tools, Inc., Civil Action No. C-10-4, 2010
`
`WL 2352056, at *5 (S.D. Tex. 2010) (denying motion for intervention filed four (4) months after
`
`the action was initiated because it would cause prejudice).
`
`In its Motion, Intel perfunctorily asserts that its delay should not foreclose intervention
`
`because Intel seeks “to intervene at an early stage of the litigation.” (Mot. at 6.) That the stage
`
`of the litigation is relatively early, does not excuse Intel’s failure to move expeditiously. Staley,
`
`223 F.R.D, at 462-63 (“If Star of Hope was genuinely concerned about protecting its rights in
`
`this litigation, it could and should have filed a motion for leave to intervene long ago . . . .
`
`Neither the Federal Rules of Civil Procedure nor the law of equity rewards those who slumber on
`
`their rights . . . .”). Rather, Rule 24 adjudges timeliness based on the impact that the movant’s
`
`delay in intervening will have on the litigation.5 Id . To the extent that Intel insists on
`
`
`5 Intel’s cited cases (Mot. n.10) are in accord. They all stand for the general proposition that a
`motion to intervene must be denied if the movant’s delay in filing threatens to disrupt the
`proceedings or prejudice the existing parties. See Ross v. Marshall, 426 F.3d 745, 755 (5th Cir.
`2005) (courts must consider “the prejudice caused by the applicants’ delay”); Chiles v.
`Thornburgh, 865 F.2d 1197, 1213 (11th Cir. 1989) (motion to intervene was timely when filed
`“before discovery had begun” and would not cause prejudice to existing parties); Alabama v.
`U.S. Army Corps of Eng’rs, 229 F.R.D. 669, 672 (N.D. Ala. 2005) (“The court has not yet
`conducted proceedings on the merits of the case, and the movants’ intervention will not delay the
`
`
`
`7
`
`INTEL EX. 1417.011
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 12 of 21 PageID #: 1889
`
`
`challenging previously agreed upon or decided issues, including the case schedule, its position
`
`fundamentally controverts a finding that for the purpose of intervention, this case is at “an early
`
`stage” or that Intel’s motion is timely.
`
`Indeed, as compared to the cases Intel itself cites, Intel’s delayed motion is quite tardy.
`
`For example, in TravelSource Corp. v. Old Republic Int’l (cited in Mot. at 7 n.10), the Court
`
`found the motion to intervene timely because it was made before any pleadings other than the
`
`Complaint and Answer had been filed. No. 85 C 8116, 1986 WL 3848, at *2 (N.D. Ill. Mar. 14,
`
`1986). Similarly, in Reid v. General Motors Corp. (cited in Mot. at 13), the Court found
`
`Microsoft’s motion timely because it would not adversely affect the scheduling order (since one
`
`had not been entered after the case was transferred). 240 F.R.D. 257, 260 (E.D. Tex. 2006); see
`
`also Tivo Inc. v. AT&T, No. 2:09-cv-259, 2010 WL 10922068, at *4 (E.D. Tex. Mar. 31, 2010)
`
`(finding movant’s request timely because no scheduling conference had been held or scheduling
`
`order entered). And in Honeywell Int’l, Inc. v. Audiovox Communications Corp., the intervenors
`
`moved before any discovery had begun and when “case management issues” were still “being
`
`addressed.” Civ. A. 04-1337-KAJ, 2005 WL 2465898, at *4 (D. Del. May 18, 2005).
`
`Here, what has occurred in the amount of time that has passed is neither “minimal” nor
`
`“inconsequential.” The initial case management conference has been conducted. See Frazier,
`
`2010 WL 2352056, at *5. A schedule, negotiated and agreed upon by the parties, has been
`
`entered by the Court. Discovery and Protective Orders have also been entered and discovery is
`
`underway. See Section I.C. supra. In addition, Alacritech has already served its infringement
`
`contentions. Id. Intel’s delay in moving to intervene poses an unfair and improper risk of
`
`
`proceedings.”); Travelsource Corp. v. Old Republic Int’l Corp., No. 85 C 8116, 1986 WL 3848,
`at *2 (N.D. Ill. Mar. 14, 1986) (although motion to intervene was filed six months after the
`litigation was initiated, no pleadings had been filed other than the complaint an answer).
`
`
`
`8
`
`INTEL EX. 1417.012
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 13 of 21 PageID #: 1890
`
`
`undoing the progress Alacritech has already made toward the prompt adjudication of its rights.
`
`Thus, the first factor in the “indispensable” test for timeliness weighs against Intel’s motion if
`
`Intel carries out its plan to revisit the case schedule, briefing and other orders entered by the
`
`Court, or otherwise seek to delay the proceedings.
`
`2.
`
`The Circumstances Of Intel’s Intervention Demonstrate That It Is
`Untimely If It Executes Its Plan to Derail The Case
`
`The remaining factors are not intended to undermine the Court’s analysis of Factor 1
`
`(the length of delay), but instead calibrate the Court’s consideration of timeliness based on the
`
`relative prejudice caused by the putative intervenor’s delay in seeking intervention (Factors 2 &
`
`3) as well as the circumstances and the intervenor’s control thereof that “occasioned or
`
`contributed to the . . . delay” (Factor 4). Corley, 755 F.2d at 1210; see also Stallworth, 558 F.2d
`
`at 266. Intel has not identified any “unusual circumstances mitigating its delay” nor does Intel
`
`argue that the timing of its request for intervention was outside its control. Kneeland, 806 F.2d
`
`at 1289; see also Corley, 755 F.2d at 1210 (intervention denied when delay put at risk the
`
`efficacy of previous agreements and orders). Rather, Intel’s “ample notice of its interest in the
`
`lawsuit” and its waiting for months to seek to intervene would, at the very least, waste the
`
`parties’ and judicial resources if forced to revisit previous agreements and orders governing the
`
`case—all of which were negotiated and ruled upon during Intel’s delay in seeking to intervene.
`
`Kneeland, 806 F.2d at 1289. In these circumstances, courts have held that the prejudice to the
`
`existing parties is readily “apparent.” Id.; see also Corley, 755 F.2d at 1210.
`
`At most, Intel suggests that if Alacritech had “allow[ed] Intel or its outside counsel
`
`access to Alacritech’s September 9, 2016 infringement contentions” then “Intel could have
`
`moved to intervene earlier.” (Mot. at 6-7.) Intel provides no explanation for why it required
`
`access to Alacritech’s designated material in order to make its motion. The Complaint includes
`
`
`
`9
`
`INTEL EX. 1417.013
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 14 of 21 PageID #: 1891
`
`
`element-by-element infringement allegations, including substantially more detail than required
`
`by the law and enough that Intel apparently decided months ago to indemnify Dell. Compare
`
`Mot. at 5. Intel made clear in correspondence with Alacritech about its intervention that it had
`
`already agreed to indemnify Dell and its desire to intervene was not contingent on receipt of
`
`Alacritech’s contentions. (Dkt. 71-3 at 2-3 (10/20/2016 G. Stephens email to J. Paunovich).)
`
`Nor does Intel cite to any case law (and Alacritech is not aware of any) that supports the
`
`proposition that an intervenor may wait until it gets access to designated material before bringing
`
`its motion. To the contrary, the Fifth Circuit has rejected access to designated material as a
`
`consideration in evaluating the appropriateness of intervention. Deus, 15 F.3d at 525.
`
`Factors 2-4 underscore the importance of foreclosing Intel’s use of its motion as a means
`
`of derailing this litigation – e.g., by re-litigating previously-briefed or decided issues or
`
`otherwise undermining the case schedule. Using the barometer provided by well-established
`
`Fifth Circuit law, Intel’s motion is either timely and Intel is bound by the case schedule and
`
`orders in place, or it is unfairly prejudicial and untimely.
`
`B.
`
`Intel Is Not An Intervenor Of Right
`
`1.
`
`Intel Does Not Have A Sufficient Interest In The Litigation
`
`In addition to potentially being untimely, Intel’s argument that it is entitled to intervene
`
`as a matter of right is incorrect and unsupported by the legal authority in its Motion. Despite
`
`broadly asserting that “Courts routinely grant intervention as of right in patent actions where, as
`
`here, accused products incorporate components manufactured by the intervening party” (Mot. at
`
`7), Intel does not cite a single case from this Court or that is binding on this Court that grants
`
`intervention in these circumstances pursuant to Rule 24(a). (Compare Mot. at 7-9.) Neither
`
`Chandler & Price v. Brandtjen & Kluge, which is a Supreme Court case that predates the
`
`adoption of Rule 24, nor Tegic Communications Corp. v. Board of Regents, which does not
`
`
`
`10
`
`INTEL EX. 1417.014
`
`

`

`Case 2:16-cv-00693-JRG-RSP Document 82 Filed 11/17/16 Page 15 of 21 PageID #: 1892
`
`
`address a motion to intervene at all, discuss much less support a finding that Intel, as the
`
`manufacturer of a component in some of the complex accused systems at issue in this litigation,
`
`has a right to intervene. 296 U.S. 53 (1935); 458 F.3d 1335 (Fed. Cir. 2006).
`
`The cited extra-jurisdictional authority is readily distinguishable. (Mot. at 7-9). In both
`
`Honeywell and Intellectual Ventures, Intel contends supports its position, the intervenors’
`
`products were themselves accused of infringement – whereas here Alacritech has accused
`
`Defendants’ server systems, which Intel does not manufacture, assemble, or sell. Cf. Honeywell
`
`Int’l, Inc. v. Audiovox Commc’ns Corp., Civ. A. 04-1337-KAJ, 2005 WL 2465898, at *3 (D. Del.
`
`May 18, 2005) (intervention appropriate because “liability depends exclusively upon
`
`infringement being found as to an LCD component that the defendants do not manufacture and . .
`
`. some of the manufacturers of the LCDs are before the court and are willing to stand behind
`
`their products in this litigation”) (emphasis added); Intellectual Ventures I LLC v. AT&T Mobility
`
`LLC, C.A. No. 12-193-LPS, 2014 WL 4445953, at *2 (D. Del. Sept. 8, 2014) (intervenors
`
`“manufacture products for AT&T and Nextel that IV I claims infringe four of IV’s patents”).6
`
`This distinction is particularly salient because, as noted by the Delaware court in
`
`Honeywell, the “fairest and most efficient way to proceed” with litigation is to focus on the
`
`provider of the mainstay of the accused products or systems – and not to unnecessarily
`
`complicate the action by including disparate defendants “with many different accused devices”
`
`or only an attenuated interest in the proceedings. 2005 WL 2465898 at *3. Here, unlike in
`
`Honeywell, it is the existing defendants who are uniquely situated to understand and defend their
`
`
`6 The remainder of Intel’s authority is simila

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