throbber
Case 2:22-cv-00215-TS-DAO Document 277 Filed 01/31/24 PageID.3988 Page 1 of 5
`
`
` UNITED STATES DISTRICT COURT FOR THE DISTRICT OF UTAH
`CENTRAL DIVISION
`
`
`
`
`EAGLE VIEW TECHNOLOGIES INC.; and
`PICTOMETRY INTERNATIONAL CORP.,
`
`
`
`v.
`
`GAF MATERIALS LLC,
`
`
`
`
`Plaintiffs,
`
`Defendant.
`
`
`MEMORANDUM DECISION AND
`ORDER GRANTING DEFENDANT’S
`SHORT-FORM MOTION TO COMPEL
`PLAINTIFFS’ PRODUCTION OF
`DOCUMENTS SUFFICIENT TO
`IDENTIFY THIRD PARTIES THAT
`DEVELOPED, MANUFACTURED, OR
`SOLD PLAINTIFFS’ PRODUCTS
`(DOC. NO. 188)
`
`Case No. 2:22-cv-00215
`
`District Judge Ted Stewart
`
`Magistrate Judge Daphne A. Oberg
`
`
`
`
`In this patent infringement case, Defendant GAF Materials, LLC filed a motion to
`
`compel Plaintiffs Eagle View Technologies, Inc. and Pictometry International Corp.
`
`(collectively, “EagleView”) to produce documents sufficient to identify the third parties that
`
`have developed, manufactured, or sold EagleView’s products which EagleView contends
`
`practice the asserted patents.1 EagleView opposed the motion to compel, arguing its response
`
`was adequate and the discovery request was overly broad and unduly burdensome.2 The court
`
`
`1 (Def.’s Short-Form Mot. to Compel Pls.’ Produc. of Docs. Sufficient to Identify Third-Parties
`that Designed, Developed, Manufactured, or Sold Pls.’ Products (“Mot.”), Doc. No. 188.)
`
`2 (Pls.’ Opp’n to Def.’s Short-Form Mot. to Compel Pls.’ Produc. of Docs. Sufficient to Identify
`Third-Parties that Designed, Developed, Manufactured, or Sold Pls.’ Products (“Opp’n”), Doc.
`No. 191.)
`
`1
`
`

`

`Case 2:22-cv-00215-TS-DAO Document 277 Filed 01/31/24 PageID.3989 Page 2 of 5
`
`held a hearing on October 16, 2023, and took the motion under advisement.3 For the reasons
`
`explained below, GAF’s motion is granted.
`
`GAF’s request for production (“RFP”) 28 seeks “[d]ocuments sufficient to identify any
`
`vendors, manufacturers, fabricators, consultants, or other third-party entities or individuals that
`
`have been involved in any way with any of Plaintiffs’ products or processes that Plaintiffs
`
`contend practice any Asserted Claim, including the products referenced in Section VIII of
`
`Plaintiffs’ LPR 2.3 Initial Infringement Contentions.”4 EagleView objected on various grounds
`
`including overbreadth and undue burden,5 and eventually agreed to produce documents only for
`
`the following categories:
`
`1. entities involved in design or development prior to the patents’ 2009 priority
`
`dates;
`
`2. entities which sold EagleView’s roof reports between 2019 and present;
`
`3. entities which supplied imagery to EagleView before its 2013 merger with
`
`Pictometry (which then became its exclusive supplier); and
`
`4. entities which construct roof models or analyze aerial imagery.6
`
`GAF argues EagleView’s response improperly imposes both temporal and subject-matter
`
`limitations on RFP 28.7 GAF argues the requested documents are relevant because EagleView
`
`
`3 (See Min. Entry, Doc. No. 203; Tr. of Oct. 16, 2023 Hrg. 33:8, Doc. No. 262.)
`
`4 (Ex. B to Mot., Pls.’ Resps. and Objs. to Def.’s Reqs. for Produc. Nos. 6-37 (“Pls.’ Resps.”) 23,
`Doc. No. 189-2.)
`
`5 (See id. at 23–24.)
`
`6 (See Opp’n 1, Doc. No. 191; see also Mot. 1–2, Doc. No. 188.)
`
`7 (See Mot. 2, Doc. No. 188.)
`
`
`
`2
`
`

`

`Case 2:22-cv-00215-TS-DAO Document 277 Filed 01/31/24 PageID.3990 Page 3 of 5
`
`intends to rely on the alleged commercial success and industry praise of its products to show the
`
`asserted patents are valid—specifically, that they were nonobvious.8 But GAF maintains any
`
`such success was not due to patented features, but rather other facts (such as third-party
`
`manufacturing, exclusive third-party relationships, marketing, or other non-patented features of
`
`the products).9 Thus, GAF contends documents identifying third parties which contributed to the
`
`products’ commercial success are relevant to whether the asserted patents are obvious.10
`
`EagleView argues the request for documents identifying any entity “involved in any
`
`way” with its products is overly broad, and only the categories of documents it agreed to produce
`
`are relevant.11 Specifically, EagleView contends the first category (designers and developers
`
`before 2009) is relevant to inventorship; the second category (sellers from 2019 to present) is
`
`relevant to damages; and only the third and fourth categories (imagery suppliers and entities
`
`which construct roof models or analyze aerial imagery) are relevant to commercial success.12
`
`EagleView suggests GAF must identify any other specific categories it is seeking before
`
`requiring EagleView to respond.13 EagleView also argues the request is unduly burdensome
`
`because it has had over a thousand vendors, and it does not keep vendor records in a manner
`
`corresponding to GAF’s request.14
`
`
`
`8 (Id.)
`
`9 (Id.)
`
`10 (Id.)
`
`11 (See Opp’n 1–2, Doc. No. 191.)
`
`12 (See id. at 1.)
`
`13 (See id.)
`
`14 (See id. at 2.)
`
`
`
`3
`
`

`

`Case 2:22-cv-00215-TS-DAO Document 277 Filed 01/31/24 PageID.3991 Page 4 of 5
`
`At the hearing, GAF clarified that it narrowed the scope of its request during conferrals
`
`with EagleView, and it only seeks documents identifying developers, manufacturers, and sellers
`
`of EagleView’s products.15 With that limitation, RFP 28 is relevant and proportional to the
`
`needs of the case.16 As GAF explained in its motion and at the hearing, discovery regarding the
`
`contributions of third-party developers, manufacturers, and sellers is relevant to rebut
`
`EagleView’s allegation that the commercial success of its products is attributable to patented
`
`features. For purposes of determining whether outside vendors contributed to the products’
`
`commercial success, the relevant time period is the entire time period during which EagleView’s
`
`products were developed, manufactured, and sold. Thus, the time limitations proposed by
`
`EagleView based on the relevant time periods for inventorship (pre-2009) and damages (2019 to
`
`present) are inapt. EagleView has not shown these time limitations are warranted, where RFP 28
`
`seeks information relevant to commercial success rather than inventorship or damages. Finally,
`
`EagleView’s suggestion that GAF must identify specific categories of vendors is impractical,
`
`where GAF lacks information regarding what contributions were made by outside vendors. The
`
`limitation to developers, manufacturers, and sellers is sufficient to identify the information
`
`sought and permit EagleView to respond.
`
`EagleView has not demonstrated responding to RFP 28, as limited, would cause undue
`
`burden. As in initial matter, EagleView presented no evidence of the time or costs it would incur
`
`in responding. Further, while EagleView represented it had more than a thousand vendors, it
`
`provided no estimate of the number of vendors who were developers, manufacturers, and sellers.
`
`
`15 (See Tr. of Oct. 16, 2023 Hrg. 10:15–24, Doc. No. 262.)
`
`16 See Fed. R. Civ. P. 26(b)(1) (“Parties may obtain discovery regarding any nonprivileged
`matter that is relevant to any party's claim or defense and proportional to the needs of the case.”).
`
`
`
`4
`
`

`

`Case 2:22-cv-00215-TS-DAO Document 277 Filed 01/31/24 PageID.3992 Page 5 of 5
`
`Rather, it argued at the hearing that RFP 28 would cover even vendors who supplied ballpoint
`
`pens to EagleView. But this is not a fair reading of RFP 28, as limited above, and GAF
`
`confirmed at the hearing that it is not seeking such information. EagleView has not
`
`demonstrated it would be unduly burdensome to produce documents identifying developers,
`
`manufacturers, and sellers of the products at issue in this case.
`
`For these reasons, RFP 28 as limited in this order is relevant and proportional, and
`
`EagleView must produce responsive documents.
`
`CONCLUSION
`
`GAF’s motion17 is granted, and EagleView is ordered to produce documents sufficient to
`
`identify third-party developers, manufacturers, and sellers of EagleView’s products at issue in
`
`this case.
`
`DATED this 31st day of January, 2024.
`
`BY THE COURT:
`
`
`____________________________
`Daphne A. Oberg
`United States Magistrate Judge
`
`
`
`17 (Doc. No. 188.)
`
`
`
`
`
`5
`
`

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