throbber

`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`______________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`______________________
`
`ADELLO BIOLOGICS, LLC, APOTEX INC. and APOTEX CORP.,
`Petitioners
`
`v.
`AMGEN INC. and AMGEN MANUFACTURING, LIMITED,
`Patent Owner1
`______________________
`Case PGR2019-00001
`Patent 9,856,287
`______________________
`
`
`
`
`PATENT OWNER’S OPPOSITION TO
`PETITIONERS’ MOTION TO SUSPEND THE RULES TO MAINTAIN
`FILING DATE WHILE AMENDING ORIGINAL OCTOBER 1, 2018
`MANDATORY NOTICES
`
`
`
`
`
`
`
`
`
`
`
`
`
` 1
`
` While Petitioners listed both Amgen Inc. and Amgen Manufacturing, Limited in
`
`the caption as “Patent Owner,” Amgen Manufacturing, Limited is an exclusive li-
`
`censee.
`
`

`

`
`
`Exhibit
`EX2001
`
`EX2002
`
`EX2003
`
`EX2004
`
`EX2005
`
`EX2006
`
`EX2007
`
`EX2008
`EX2009
`
`EX2010
`
`EX2011
`EX2012
`EX2013
`EX2014
`
`EX2015
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`LIST OF EXHIBITS
`
`
`Description
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE1 (Amgen’s Complaint)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE50 (Amgen’s Amended Complaint)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE54 (Defendant Adello Biologics, LLC’s An-
`swer, Defenses and Counterclaims to Plaintiffs’ First Amended
`Complaint)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE57 (Amneal Pharmaceuticals, Inc. Proof of Ser-
`vice)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE58 (Amneal Pharmaceuticals, LLC Proof of
`Service)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE59 (Miller Appearance for Amneal Pharmaceu-
`ticals, LLC and Amneal Pharmaceuticals, Inc.)
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE60 (Gabay Appearance for Amneal Pharmaceu-
`ticals, LLC and Amneal Pharmaceuticals, Inc.)
`File History of U.S. Patent 9,856,287
`Luis Felipe Vallejo & Ursula Rinas, Optimized Procedure for
`Renaturation of Recombinant Human Bone Morphogenetic Pro-
`tein-2 at High Protein Concentration, Biotechnology and Bioengi-
`neering, Vol. 85 No. 6, 601-09 (March 2004)
`Amgen Inc. et al v. Apotex Inc. et al, Case No. 0:15-cv-61631 (S.D.
`Fla.), DE250 (Day 4 Transcript of Bench Trial held on July 14,
`2016)
`Declaration of Saurabh Gupta
`Declaration of Catherine Nyarady
`Amneal Pharmaceuticals, Inc., Form S-1 (May 7, 2018)
`Amneal Pharmaceuticals LLC, M&A Call Transcript (October 17,
`2017)
`“Lenders’ Presentation” by Amneal Pharmaceuticals LLC and Im-
`pax Laboratories (March 7, 2018)
`
`

`

`
`
`Exhibit
`EX2016
`
`EX2017
`
`EX2018
`
`EX2019
`
`EX2020
`
`EX2021
`
`EX2022
`EX2023
`
`EX2024
`
`EX2025
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`Description
`Amgen Inc. et al. v. Adello Biologics LLC, Case No. 2:18-cv-03347
`(D.N.J.), DE47 (October 1, 2018 letter to U.S. Magistrate Judge
`Mark Falk)
`Mylan Pharmaceuticals Inc. v. Yeda Research and Development
`Co. Ltd., IPR2015-00643, EX1076 (Stipulated Protective Order in
`In re Copaxone 40 mg Consolidated Cases, No. 1:14-cv-01171
`(GMS))
`Amgen Inc. et al. v. Adello Biologics, LLC, Case No. 2:18-cv-
`03347 (D.N.J.), DE70-1 (Brief in Support of Motion to Dismiss)
`Amgen Inc. v. Apotex Inc., Appeal No. 17-1010 (Fed. Cir.), DE 42-
`3 (Joint Appendix Volume III of III)
`Amgen Inc. et al v. Apotex Inc. et al, Case No. 0:15-cv-61631 (S.D.
`Fla.), DE247 (Day 1 Transcript of Bench Trial held on July 11,
`2016)
`Amgen Inc. et al v. Apotex Inc. et al, Case No. 0:15-cv-61631 (S.D.
`Fla.), DE245 (Partial Findings Regarding
`Apotex’s Assertion of Invalidity of the ’138 Patent)
`Impax Laboratories, Inc., Schedule 14A (Feb. 12, 2018)
`Emails between counsel for Petitioners and counsel for Patent
`Owners, dated January 2, January 8, January 10, and January 11,
`2019
`Email from counsel for Amgen to counsel for Petitioner Adello Bi-
`ologics, LLC, dated September 19, 2018, and attachments
`Email from counsel for Petitioners to the Board, dated January 15,
`2019
`
`
`
`
`
`
`
`
`ii
`
`

`

`
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`
`CASES
`Aerospace Comm’s Holdings Co. v. Armor All/Step Prods. Co.,
`IPR2016-00441, Pap.12 (June 28, 2016) .......................................................... 3, 6
`Amazon.com, Inc. v. Appistry, Inc.,
`IPR2015-00480, Pap.18 (July 13, 2015) .............................................................. 4
`Atlanta Gas Light Co. v. Bennett Regulator Guards, Inc.,
`IPR2013-00453, Pap.88 (Jan. 6, 2015) ................................................................. 7
`Cisco Sys., Inc. v. Hewlett-Packard Enter. Co.,
`IPR2017-01933, Pap.9 (Mar. 16, 2018) ............................................................... 5
`Dispersive Networks, Inc. v. Nicira, Inc.,
`PGR2018-00063, Pap.24 (Aug. 30, 2018) ............................................................ 7
`Elekta, Inc. v. Varian Medical Systems, Inc.,
`IPR2015-01401, Pap.19 (Dec. 31, 2015) .............................................................. 6
`Lumentum Holdings, Inc. v. Capella Photonics, Inc.,
`IPR2015-00739, Pap.38 (Mar. 4, 2016) ............................................................... 7
`Worlds Inc. v. Bungie, Inc.,
`903 F.3d 1237 (Fed. Cir. 2018) ............................................................................ 2
`Zoll Lifecor Corp. v. Philips Elecs. N. Am. Corp.,
`IPR2013-00606, Pap.13 (Mar. 20, 2014) ............................................................. 4
`
`
`STATUTES
`35 U.S.C. §321(c) ...................................................................................................... 7
`35 U.S.C §322(a)(2) ................................................................................................... 1
`
`
`
`iii
`
`

`

`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`
`OTHER AUTHORITIES
`37 C.F.R. §42.206(b) ............................................................................................. 1, 2
`37 C.F.R. §42.5(c)(3) ................................................................................................. 2
`
`
`iv
`
`

`

`The statute (§322(a)(2)) and rules (§42.206(b)) obligate petitioners to “iden-
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`
`
`tif[y] all real parties in interest” when they file their petition—not just if and when
`
`they are caught.2 Petitioners here were well aware of the central role played by the
`
`missing RPI at the very time they were filing their Petition, and still refuse to pro-
`
`vide the Board and Patent Owner with any explanation at all about the surrounding
`
`circumstances (offering, instead, only counsel’s conclusory assertion that all is
`
`well) despite being asked directly before and during the January 18 call. Thus,
`
`while the Board may take petitioners at their word if no RPI issue is raised, and
`
`may consider suspending the rules on a persuasive showing that the particular fac-
`
`tual circumstances justify it, the Board here should follow its rules and deny Peti-
`
`tioners’ unsupported request to keep its original filing date.3
`
`A PGR petition “may be considered only if . . . the petition identifies all real
`
`parties in interest.” §322(a)(2). “Where”—as Petitioners admit here (Mot.1;
`
`EX2023; EX2012 ¶6)—“a party files an incomplete petition, no filing date will be
`
`
`
` 2
`
` All abbreviations are from Papers 8 and 9, all emphasis/annotations added, and
`
`all statutory/regulatory citations to 35 U.S.C. or 37 C.F.R., unless otherwise stated.
`
`3 Amgen would not oppose filing of a Mandatory Notice that reflects all RPIs to-
`
`gether with an adjustment of the filing date as required by §42.206(b).
`
`

`

`
`accorded…” §42.206(b); see Worlds Inc. v. Bungie, Inc., 903 F.3d 1237, 1240
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`(Fed. Cir. 2018) (importance of “[c]orrectly identifying all [RPIs]”). As with the
`
`prior incorrect representation that all RPIs had been fully identified (Pap.3, 2), reli-
`
`ance here on attorney representations is insufficient. See Worlds, 903 F.3d at
`
`1242-43, 1245-46. To support their motion to suspend the rules under §42.5(b)
`
`and (c)(3), Petitioners must establish that, on the facts of this situation, it would be
`
`in the interests of justice to do so. See, e.g., §42.5(c)(3); Mot.5 (citing Dispersive
`
`Networks, Inc. v. Nicira, Inc., PGR2018-00063, Pap.24, 2 (Aug. 30, 2018)). Be-
`
`cause Petitioners (the movants) offered only legal conclusions from PGR coun-
`
`sel—not facts—and nothing at all from their common litigation counsel, they have
`
`not even tried to meet that burden, and their motion must be denied. See Mot. 4-6
`
`(only “expressly represent[ing] that there was no intentional concealment or bad
`
`faith”; labeling as “accidental” and “inadvertent”);4 Worlds, 903 F.3d at 1242-46.
`
`Petitioners’ suggestion that Amgen “has not presented any evidence suggest-
`
`ing . . . intentional action or bad faith” (Mot.5) misstates the burden (absent any
`
`
`
` 4
`
` Petitioners’ assertion “Petitioners promptly investigated the issue, and agreed that
`
`Amneal LLC should have been listed” conspicuously begs the question: Why did
`
`Petitioners not investigate before filing, and, if they did, how did this occur?
`
`2
`
`

`

`
`supporting evidence from Petitioners, Amgen need not prove the contrary) and is
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`wrong: as detailed in the January 18 call and Preliminary Response (Pap.8), even
`
`the limited facts available to Amgen confirm Petitioners were aware of Amneal
`
`LLC’s central importance at the very time they prepared and filed their Petition and
`
`actively represented that they had identified every RPI (Pap.3, 2). Contrast, e.g.,
`
`Aerospace Comm’s Holdings Co. v. Armor All/Step Prods. Co., IPR2016-00441,
`
`Pap.12 (June 28, 2016) at 4-5 (cited at Mot.4) (unlike this case, owner there “pre-
`
`sented no argument or evidence calling into question Petitioner’s express represen-
`
`tation”). The missing RPI, Amneal LLC, is the entity actually responsible for sell-
`
`ing, marketing and pricing the proposed biosimilar product accused of infringing
`
`the patent challenged here—the product of its “research partner,” Petitioner
`
`Adello. See EX2013, 97, 146; EX2003, ¶19; EX2014, 5; EX2015, 20; Pap.8, 9-12.
`
`Adello and other Amneal companies doing business with Amneal LLC share legal
`
`and other services through AE Companies LLC (EX2022, 261), and Amneal LLC
`
`and named RPI Amneal Pharmaceuticals, Inc. (“API”)—the holding company
`
`combining Amneal LLC’s and Impax Laboratories, Inc.’s business (EX2013, 8-
`
`9)—share the same address and representative on whom the infringement com-
`
`plaint was served (EX2004-EX2007), and both appeared in that suit through the
`
`same counsel (who conspicuously makes no submission here). API is Amneal
`
`LLC’s sole managing member and shares at least some (if not all) board members.
`
`3
`
`

`

`
`EX2013, 8-9, 16, 175-179. As Petitioners and their named RPIs were well aware
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`when they omitted Amneal LLC from the Petition, they “have a very close parent
`
`and wholly-owned subsidiary relationship with aligned interests.” See, e.g., Zoll
`
`Lifecor Corp. v. Philips Elecs. N. Am. Corp., IPR2013-00606, Pap.13, 10 (Mar. 20,
`
`2014) (denying institution). And contrary to Petitioners’ suggestion (Mot.4),
`
`merely naming a parent does not suffice. See Amazon.com, Inc. v. Appistry, Inc.,
`
`IPR2015-00480, Pap.18, 3-6 (July 13, 2015) (denying institution for failure to
`
`name corporate entities between named companies).
`
`Moreover, Amneal LLC’s role and connections to the ’287, the accused bio-
`
`similar product and infringement litigation leading to this PGR, and the other
`
`named Petitioners and RPIs, was being actively discussed with named Petitioner
`
`Adello precisely when this PGR Petition was being finalized. See Pap.8, 12-15;
`
`Pet., 2; EX2001. Amgen amended its complaint to add Amneal LLC and API
`
`(EX2002) after an extended meet-and-confer process in the weeks and days before
`
`October 1—the same day that the Petition was filed (naming API but not Amneal
`
`LLC as an RPI), and that the proposed amended complaint (naming both Amneal
`
`LLC and API as additional defendants) was sent to the District Court and Adello.
`
`By then, Adello had already agreed not to oppose the amendment after receiving a
`
`draft complaint 1½ weeks before Petitioners filed this Petition. See EX2016;
`
`EX2024; EX2012 ¶4. Amneal LLC’s role and significance were front-and-center
`
`4
`
`

`

`
`for Petitioners and their named RPIs in the period leading up to Petitioners’ Octo-
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`ber 1 filing.5 Indeed, the very officer signing Adello’s Power of Attorney here,
`
`Kenneth Cappel (see Pap.2, 3), was previously Vice President of Global Intellec-
`
`tual Property for Amneal LLC. EX2017, 14; see also EX2022, 261.
`
`Notwithstanding this knowledge and these active discussions with Petitioner
`
`Adello before and including the day of filing, the Petitioners6 omitted Amneal LLC
`
`from their Petition, rendering it incomplete under §322(a)(2)7—and in a way that
`
`
`
` 5
`
` The significance of properly naming RPIs was also a matter of significant public
`
`discussion before October 1, including as a result of Worlds (September 7).
`
`6 As co-Petitioners, both Apotex and Adello bore the obligation to identify RPIs
`
`(cf. Mot.7) and, with shared PGR counsel, were in every position to do so.
`
`7 Moreover, while the role of Amneal LLC continued to be actively litigated by Pe-
`
`titioner Adello and named RPI API, Petitioners said nothing about their omission
`
`until Amgen confronted them. See, e.g., EX2023; EX2012 ¶¶3, 5-6; EX2018, 10,
`
`20-21, 23; Pap.8, 14-15 n.5; Cisco Sys., Inc. v. Hewlett-Packard Enter. Co.,
`
`IPR2017-01933, Pap.9, 8-9, 13, 17 (Mar. 16, 2018) (denying institution, noting
`
`“Petitioner’s failure to apprise the Board before or after the filing of the Petition”).
`
`5
`
`

`

`
`at minimum raises serious questions about Petitioners’ claim of mere “inad-
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`verten[ce],” rather than gamesmanship or bad faith (including reckless disregard of
`
`Petitioners’ obligations to investigate before making representations). Cf. Mot.5.
`
`Because Petitioners have come forward with no evidence concerning the actual cir-
`
`cumstances, and have refused any explanation beyond conclusory labels (Mot.5-6
`
`(“inadvertent,” “accidental”)), they cannot meet their §42.5 burden.
`
`Petitioners’ arguments (Mot.3-4) about the function of §322(a)(2) and
`
`§42.206(b) ignore that Amgen is not appropriately “protect[ed] from harassment” if
`
`Petitioners can shift to Amgen the obligation to investigate and police Petitioners’
`
`RPI violations. Indeed, even if Amneal LLC is added Petitioners offer no evidence
`
`(or even assertions) that all RPIs would then be identified—and they make no
`
`mention of investigating related entities like AE Companies LLC (see EX2022,
`
`261; Pap.8), or others unknown to Amgen who might petition in the future. This
`
`unquestionably prejudices Amgen, as does requiring Amgen to devote resources
`
`(and Preliminary Response space) to addressing this issue. Cf. Mot.6. Nor do Pe-
`
`titioners address the prejudice to post-AIA trials as a whole, and to all patent own-
`
`ers, of requiring RPIs to be identified only when a petitioner is caught failing to do
`
`so. See Petitioners’ cited decisions in Elekta, Inc. v. Varian Medical Systems, Inc.,
`
`IPR2015-01401, Pap.19 (Dec. 31, 2015) (Judge Boucher, dissenting), and Aero-
`
`space, IPR2016-00441, Pap.12, 9-10 (“we are cognizant” of concerns in Elekta
`
`6
`
`

`

`
`dissent).8 And Petitioners’ arguments about being “time-barred” and prejudiced by
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`their own actions are contradictory: Petitioners are indisputably time-barred from
`
`bringing a PGR (see §321(c)) but argue they can bring an IPR instead. Mot.6.
`
`Finally, to the extent the Board determines further evidence is needed to
`
`deny this motion, Amgen again requests authorization to move for discovery into
`
`the pertinent facts, which are uniquely in Petitioners’ possession, and reserves the
`
`right to pursue this issue further. See, e.g., Atlanta Gas Light Co. v. Bennett Regu-
`
`lator Guards, Inc., IPR2013-00453, Pap.88 (Jan. 6, 2015) (vacating institution de-
`
`cision and terminating review based on evidence showing failure to name RPIs).
`
`
`Respectfully submitted by:
`
`/J. Steven Baughman/
`J. Steven Baughman (Reg. No. 47,414)
`Lead Counsel For Patent Owners
`
`
`
`
`
`Dated: February 4, 2019
`
`
`
`
`
`
`
`
` 8
`
` As indicated on January 18: (1) unlike in Elekta, Amgen does not challenge “ju-
`
`risdiction[]” (cf. Mot.2); and (2) Petitioners’ Lumentum case is inapposite because
`
`the issue here is not “a lapse in compliance” (cf. Mot.2)—Petitioners never com-
`
`plied (Lumentum Holdings, Inc. v. Capella Photonics, Inc., IPR2015-00739,
`
`Pap.38, 6 (Mar. 4, 2016); see also Dispersive, PGR2018-00063, Pap.24, 1-2 (peti-
`
`tioner relying on “changed circumstances”)).
`
`7
`
`

`

`
`
`
`
`PGR2019-00001
`U.S. Patent 9,856,287
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a copy of PATENT OWNER’S OP-
`
`POSITION TO PETITIONERS’ MOTION TO SUSPEND THE RULES TO
`
`MAINTAIN FILING DATE WHILE AMENDING ORIGINAL OCTOBER 1,
`
`2018 MANDATORY NOTICES has been served in its entirety by causing the
`
`aforementioned document to be electronically mailed to the following attorneys of
`
`record for the Petitioner listed below:
`
`Petitioner’s Counsel of Record:
`
`Teresa Stanek Rea (Reg. No. 30,427)
`Deborah H. Yellin (Reg. No. 45,904)
`Shannon Lentz (Reg. No. 65,382)
`CROWELL & MORING LLP
`Intellectual Property Group
`1001 Pennsylvania Avenue, N.W.
`Washington, DC 20004-2595
`TRea@Crowell.com
`DYellin@Crowell.com
`SLentz@Crowell.com
`
`
`Dated: February 4, 2019
`
`
`
`
`
`
`Respectfully Submitted,
`
`/Sayem Osman/
`By:
`Sayem Osman
`
`

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