throbber
Trials@uspto.gov
`571.272.7822
`
`
`
`Paper 39
`
` Entered: March 7, 2019
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`KVK-TECH, INC.,
`Petitioner,
`
`v.
`
`SHIRE PLC,
`Patent Owner.
`____________
`
`Case IPR2018-00290 (Patent 8,846,100 B2)
`Case IPR2018-00293 (Patent 9,173,857 B2)1
`____________
`
`
`
`Before RAMA G. ELLURU, SHERIDAN K. SNEDDEN, and
`DEVON ZASTROW NEWMAN, Administrative Patent Judges.
`
`ELLURU, Administrative Patent Judge.
`
`
`
`
`ORDER
`Conduct of Proceeding
`37 C.F.R. § 42.5(a)
`
`
`
`
`1 This Decision addresses issues that are the same in the above-identified
`proceedings. We exercise our discretion to issue one Decision to be entered
`in each proceeding. The parties are not authorized to use this joint heading
`and filing style in their papers.
`
`
`
`

`

`IPR2018-00290 (Patent 8,846,100 B2)
`IPR2018-00293 (Patent 9,173,857 B2)
`
`On February 25, 2019, counsel for Petitioner sent the following email
`to the individual email address of a paralegal at the Board:
`I am an attorney working on the above-referenced IPRs. In
`addition to this email, I left you a voicemail message.
`
` write to ask for your guidance to correct an expert declaration
`filed on February 7. The required oath was inadvertently left
`out of the expert’s declaration, and we would like to correct this
`error.
`
`The questions I have are more procedurally-based, and I’m
`hoping you can help. For example, do we add the oath to the
`Feb. 7 declaration (exhibit 1045) and keep the dates the same,
`or do w need to file a new declaration updated dates, and a new
`exhibit number? Or perhaps there is a different convention or
`protocol we should follow that is not in the rules?
`
`Any advice you may provide would be greatly appreciated, and
`I thank you for your time.
`This email was improper for the following reasons. First, all email
`communications to the Board should be sent to Trials@uspto.gov, as
`instructed in the Scheduling Order (Paper 14). Email sent to the Board
`should not be addressed to an individual email address(es). See 37 C.F.R. §
`42.5(d) (prohibiting ex parte communications with any member of the
`Board, including employees acting with authority of the Board). Second, a
`party may communicate with the Board, without also copying opposing
`counsel, only on purely administrative matters (e.g., how to use E2E). On
`email communications to the Board involving issues that may not be entirely
`procedural, a party should copy opposing counsel out of an abundance of
`caution. In this instance, Petitioner’s email did not make clear that Patent
`Owner did not object to correction of the expert declaration, and thus, the
`issue was not entirely procedural and should not have been the subject of an
`
` I
`
`2
`
`

`

`IPR2018-00290 (Patent 8,846,100 B2)
`IPR2018-00293 (Patent 9,173,857 B2)
`
`email communication to the Board that did not copy counsel for Patent
`Owner.
`
`With respect to Petitioner’s need to correct Ex. 1045 to include a
`proper oath (Ex. 1045), the panel orders the parties to meet and confer in an
`attempt to seek an agreed upon resolution (e.g., a motion to file a corrected
`declaration).
`
`
`IT IS:
`ORDERED that the parties meet and confer in an attempt to seek an
`
`agreed upon resolution (e.g., a motion to file a corrected declaration) with
`respect to Petitioner filing a declaration without a proper oath (Ex. 1045).
`
`
`
`3
`
`

`

`IPR2018-00290 (Patent 8,846,100 B2)
`IPR2018-00293 (Patent 9,173,857 B2)
`
`
`PETITIONER:
`Steven Roth
`Thomas Vetter
`LUCAS & MERCANTI, LLP
`sroth@lmiplaw.com
`tvetter@lmiplaw.com
`
`PATENT OWNER:
`Joseph Robinson
`Robert Schaffer
`Dustin Weeks
`TROUTMAN SANDER LLP
`joseph.robinson@troutmansanders.com
`robert.schaffer@troutmansanders.com
`dustin.weeks@troutmansanders.com
`
`
`
`4
`
`

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