Nvision Biomedical Techs., LLC v. Jalex Med., LLC
Nvision Biomedical Techs., LLC v. Jalex Med., LLC
2015 WL 13049356 (W.D. Tex. 2015)
December 23, 2015
Mathy, Pamela A., United States Magistrate Judge
Summary
The court ordered Jalex to produce documents related to its development of implantable spinal devices, cervical plates, pedicle screws, and structurally encoded implant devices, including ESI. The court also found that Jalex's parent and sister companies, RP+M and Thogus, respectively, are not parties to the protective order and are not entitled to the same protections. Nvision's requests were found to be relevant and not overly broad or unduly burdensome.
Additional Decisions
NVISION BIOMEDICAL TECHNOLOGIES, LLC, Plaintiff,
v.
JALEX MEDICAL, LLC, Defendant
v.
JALEX MEDICAL, LLC, Defendant
CIVIL NO. SA–15–CA–284–RP
United States District Court, W.D. Texas, San Antonio Division
Signed December 23, 2015
Counsel
Derick J. Rodgers, Davis, Cedillo & Mendoza , Inc., San Antonio, TX, for Plaintiff.Gerald L. Shiely, Vaughan E. Waters, Thornton, Biechlin, Segrato, Reynolds & Guerra, L.C., Jonathan D. Pauerstein, Stephen K. Lecholop, II, Rosenthal Paurestein Sandoloski Agather LLP, San Antonio, TX, Chelsea R. Mikula, Robert J. Hanna, Tucker Ellis LLP, Cleveland, OH, for Defendant.
Mathy, Pamela A., United States Magistrate Judge
AMENDED ORDER
*1 Came on this day to be considered:
• defendant's motion to preserve designated status of classified information, filed November 25, 2015;[1]
• plaintiff's sealed motion to overrule objections and compel discovery responses, filed November 30, 2015;[2]
• defendant's sealed motion to strike Nvision's motion to overrule, filed December 3, 2015;[3] and
• the District Judge's December 14, 2015 order of referral.[4]
• the District Judge's December 18, 2015 order of referral.[5]
On December 15, 2015, the undersigned set the referred motions for a hearing to occur on December 22, 2015.[6] On December 22, 2015, the scheduled hearing occurred.
I. SUMMARY OF PROCEDURAL HISTORY
Plaintiff Nvision Biomedical Technologies, LLC (“Nvision”) filed its “live” complaint under seal on September 9, 2015.[7] The complaint names Jalex Medical, LLC (“Jalex”) as defendant, and alleges five causes of action: (1) fraud, (2) breach of contract, (3) tortious interference with prospective business relationship, (4) misappropriation of trade secrets and intellectual property, and (5) unfair competition.[8] On September 24, 2014, Jalex filed its “live” pleading, a counterclaim also alleging breach of contract as a cause of action.[9] On September 29, 2015, Jalex filed its first amended answer.[10] On October 14, 2015, Nvision filed its answer to Jalex's counterclaim.[11] On September 9, 2015, the District Judge entered a confidentiality and protective order (“CPO”).[12]
On November 25, 2015, Jalex filed a motion to preserve designated status.[13] On December 2, 2015, Nvision filed its response in opposition.[14] On November 30, 2015, Nvision filed a motion to overrule objections and compel discovery responses.[15] On December 3, 2015, Jalex filed its response in opposition, contingent to its motion to strike Nvision's motion.[16]
II. STANDARDS
A. Scope of Discovery
*2 Rule 26 of the Federal Rules of Civil Procedure generally addresses the methods and scope of permissible civil discovery, specifying that certain types of information must be initially disclosed without a discovery request and providing for the discovery of additional matters through such methods as written interrogatories, requests for production of documents, and depositions. With respect to the scope of discovery, Rule 26(b)(1) states:
(b) Discovery Scope and Limits.
(1) Scope in General. Unless otherwise limited by court order, the scope of discovery is as follows: 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, considering the importance of the issues at stake in the action, the amount in controversy, the parties’ relative access to relevant information, the parties’ resources, the importance of the discovery in resolving the issues, and whether the burden or expense of the proposed discovery outweighs its likely benefit. Information within this scope of discovery need not be admissible in evidence to be discoverable.[17]
Discovery must not be “unreasonably cumulative or duplicative.”[18] The Court, even on its own motion, “must limit the frequency or extent of discovery otherwise allowed by these rules or by local rule” when
(i) the discovery sought is unreasonably cumulative or duplicative, or can be obtained from some other source that is more convenient, less burdensome, or less expensive;
(ii) the party seeking discovery has had ample opportunity to obtain the information by discovery in the action; or
(iii) the proposed discovery is outside the scope permitted by Rule 26(b)(1).[19]
Parties may obtain additional discovery through written interrogatories, requests for production of documents and other items, depositions, and requests for admission. Rule 33 of the Federal Rules of Civil Procedure provides that a party may serve upon any other party written interrogatories to discover any information relevant under Rule 26(b).[20] Interrogatories are not to exceed twenty-five (25) in number including discrete subparts, unless leave of court is first obtained.[21] Rule 34 of the Federal Rules of Civil Procedure permits discovery of documents in the “possession, custody, or control” of the party upon whom the request is served.[22] A party may depose any person, but there is a presumptive limit of ten (10) depositions by plaintiffs, defendants, or third-party defendants, and a presumptive time limit of one day of seven hours for any deposition by oral examination.[23] Requests for admission allow a party to serve on a party “a written request to admit, for purposes of the pending action only, the truth of any matters within the scope of Rule 26(b)(1) relating to: (A) facts, the application of law to fact, or opinions about either; and (B) the genuineness of any described documents.”[24]
B. Compelling Discovery
Rule 37(a) of the Federal Rules of Civil Procedure provides that, “[o]n notice to other parties and all affected persons, a party may move for an order compelling disclosure or discovery” but the motion “must include a certification that the movant has in good faith conferred or attempted to confer with the person or party failing to make disclosure or discovery in an effort to obtain it without court action.”[25] An “evasive or incomplete disclosure, answer, or response must be treated as a failure to disclose, answer, or respond.”[26]
*3 The Fifth Circuit requires a party who objects to discovery to specifically show how each request for production is burdensome or irrelevant.[27] A producing party may request a protective order for good cause to narrow the scope of discovery or limit the dissemination of privileged or confidential information to protect the party from “annoyance, embarrassment, oppression, or undue burden or expense.”[28] As a general rule, the producing party must show “good cause” for the issuance of any protective order, with the standard of proof varying with the type of information and protective order sought.[29] Courts have identified several factors the producing party may need to address to show good cause, including:
(1) whether disclosure will violate any privacy interests;
(2) whether the information is being sought for a legitimate purpose or for an improper purpose;
(3) whether disclosure of the information will cause a party embarrassment;
(4) whether confidentiality is being sought over information important to public health and safety;
(5) whether the sharing of information among litigants will promote fairness and efficiency;
(6) whether a party benefitting from the order of confidentiality is a public entity or official; and
(7) whether the case involves issues important to the public.[30]
A producing party must support its claim of good cause through specific facts, not conclusory allegations.[31]
C. Attorney Client and Work Product Privilege
Rule 501 of the Federal Rules of Evidence provides, in sum, that except as otherwise required by the Constitution or an Act of Congress or in Supreme Court rules, the privilege of a witness shall be governed by “the principles of common law as they may be interpreted by the courts of the United States in the light of reason and experience.”[34] In federal question cases, federal common law privilege applies, as that privilege is interpreted by “reason and experience.”
The attorney-client privilege generally protects all communications between lawyers and clients regarding matters within the scope of the representation. The privilege is said to belong to the client who may assert or waive it.[35] The term “communications” is broad enough to include not only discussions or conversations between lawyers and clients, but also correspondence between lawyers and clients, documents generated during the course of the legal relationship, and other information.
*4 The work product privilege is intended to balance the need for “[m]utual knowledge of all the relevant facts gathered by both parties” to ensure proper litigation with a lawyer's need to “work with a certain degree of privacy, free from unnecessary intrusion by opposing parties and their counsel.”[36] Work product includes “interviews, statements, memoranda, correspondence, briefs, mental impressions, personal beliefs,” and other work done by the lawyer in preparation of her client's litigation.[37] Unlike the attorney-client privilege, the work product privilege belongs to the lawyers and the client, and either may assert it.[38] The privilege is codified in Rule 26(b)(3) of the Federal Rules of Civil Procedure, which provides that work product is discoverable only if the party seeking discovery “shows that it has substantial need for the materials to prepare its case and cannot, without undue hardship, obtain their substantial equivalent by other means.”[39]
Rule 26(b)(5) of the Federal Rules of Civil Procedure requires a party resisting discovery to notify opponents that it is withholding information subject to the claim of privilege or work product.[40] Rule 26(b)(5) does not attempt to define, for all cases, precisely what information must be provided when a party asserts a claim of privilege or work product protection.[41] But, Rule 26(b) does provide a party can withhold only the information sought to be protected and must serve a response that provides information sufficient to allow the requesting party to evaluate the applicability of the claimed privilege for each item or, if applicable, each group of items withheld.[42] More specifically, the party withholding information under a claim of privilege generally must serve a “privilege log” for the withheld information which, “without revealing information itself privileged or protected, will enable other parties to assess the applicability of the privilege or protection.”[43] On the one hand, cursory descriptions are not sufficient to support a claim of privilege,[44] but, on the other hand, recording details about the information withheld may be unduly burdensome when, for example, voluminous documents are claimed to be protected that might be reported in categories or classifications and requiring too many details to be set out in the log effectively could force a breach the privilege. The level of detail required to identify the information being withheld on a claim of privilege without breaching the privilege is likely a matter that can only be determined on a case-by-case basis. It has been held that, when practicable, the privilege log should generally include a document number (“Bates number”), author or source, recipient, persons receiving copies, date, document title, document type, number of pages, and any other relevant nonprivileged information.[45] A party must seek a protective order if compiling the information for a privilege log would impose an unreasonable burden,[46] after conferring in an attempt to fashion a way of proceeding satisfactory to all concerned parties.
*5 The proponent of the attorney-client privilege bears the burden of showing the applicability of the privilege to the particular information in question.[47] If a party withholds information on a claim of privilege without notice to the other parties, sanctions can be imposed[48] and the privilege or protection may be waived.[49] Similarly, if privileged documents are not listed in a privilege log or are misrepresented as cumulative or duplicative, the privilege may be waived.[50]
III. DISCUSSION
A. Defendant's Motion to Preserve Designated Status of Classified Information
1. summary of arguments
Jalex asks the Court enter an order maintaining the “Attorney's Eyes Only” (“AEO”) designation of certain documents produced to Nvision.[51] Jalex states that it responded to Nvision's written discovery requests on August 24, 2015, and September 4, 2015.[52] Among other documents, Jalex provided
documents pertaining specifically to—as well as documents actually consisting of—design work performed by Jalex on behalf of Nvision in support of the latter's plans to market certain types of medical devices relating to spinal implantation. These documents were produced under the classification [AEO] in accordance with pertinent provisions of the [CPO].[53]
Jalex asserts that Nvision's counsel “urged that in his opinion the designation of AEO on a portion of Jalex's extensive document production to Nvision was not warranted; he asked that Jalex ‘retract or otherwise justify the AEO designations’ to ... a total of more than 2,600 pages of documents.”[54]
For purposes of its arguments, Jalex states the AEO designation has been applied to three categories of documents, and further applies a “core deliverables” or “non-core deliverables” label to each category. Although the briefing on the referred matter suggests the parties are familiar with the labels, “core” and “non-core” deliverables, Jalex's motion does not define them. (Jalex did explain the labels at the December 22 hearing.) The three categories include:
(1) drawings, models, test results, reports, and other technical information (referred to hereinafter as “Core Deliverables”);
(2) administration documents such as updates on orders; and
(3) invoices and purchase orders (categories (2) and (3) being referred to collectively as “Non–Core Deliverables”).[55]
Jalex's arguments in support of the AEO designation do not differentiate between the three categories of documents, but Jalex does acknowledge that “[p]rovided the Core Deliverables are not made available to Nvision, the Non–Core Deliverables could be downgraded from an AEO designation to a Confidential designation.”[56]
*6 In support of its request to uphold its AEO designation, Jalex argues that removing the AEO designation would provide Nvision information collected by Jalex pursuant to its contract(s) with Nvision even though Nvision has not paid the money owed under the contract. More specifically, Jalex asserts that “ ‘Nvision has alleged in its current complaint ... that Jalex breached the [Development Services Agreement (“DSA”) ] ‘by failing and refusing to deliver to Nvision all work product generated by Jalex or the subcontractors ... and by refusing to assign and transfer the rights to any intellectual property to Nvision.’ ”[57] Jalex's counterclaim alleges that “Nvision is in arrears in payments due and owing, totaling $237,321.35 both under the DSA and under a series of subsequent agreements dealing with the Products and with other items and services.”[58] Jalex argues that “until such arrearages are paid, the terms of the DSA—like the terms of the other subsequent agreements—expressly allow Jalex to retain possession and control of any Product IP and Deliverables.”[59]
In response, Nvision argues that an AEO designation is not appropriate for three main reasons. First, the contents of documents at issue are not “unknown” to Nvision and, therefore, do not meet the requirements of the AEO designation as provided in the CPO.[60] “The materials were generated under the direction and instruction of Nvision for Nvision. ... Because Nvision was involved in the development of the so-called “Core Deliverables” and “Non–Core Deliverables,” the AEO designations do not apply.”[61] Second, Nvision argues that “simply marking the materials as ‘Classified’ or ‘Confidential’ prevents Nvision from using those materials for any other purpose,” as the CPO limits the use of classified information provided by any party “solely for the purpose of preparation, trial, and appeals of this litigation and for no other purpose.”[62] Third, Nvision argues Nvision personnel have a
right to see those materials in preparation of its case and to evaluate the work that Jalex performed for Nvision, including how Jalex performed that work with the third-party consultants, the costs of that work, the specifications and errors encountered with that work, and whether the work Jalex charged Nvision appropriately for that work.[63]
Nvision asks the Court allow Nvision's counsel to disclose the materials to Nvision's personnel as “classified information,” that is, “without restriction except that such materials be used only for this litigation and no other purpose.”[64]
2. analysis
The Court begins its analysis with consideration of the terms of the CPO.[65] The CPO approved by the District Judge on September 9, 2015, sets out and discusses four main designations for information: (1) nonclassified information, (2) classified information, (3) for counsel or attorneys only, and (4) ultrasensitive information.[66] The CPO states that “classified information” includes but is not limited to, “trade secrets, confidential or proprietary financial information, operational data [ ].”[67] The CPO limits the use of “Classified Information” “solely for the purpose of preparation, trial, and appeal of this litigation and for no other purpose, and shall not be disclosed except in accordance with the terms hereof.”[68] The CPO additionally states that documents as “for counsel or attorneys only” if they contain
information that is believed to be unknown to the opposing party or parties, or any of the employees of a corporate party. For purposes of this order, so-designated information includes, but is not limited to, product formula information, design information, non-public financial information, pricing information, customer identification data, and certain study methodologies.[69]
*7 After careful consideration, the Court concludes that Jalex's motion to preserve designated status should be DENIED with respect to all three categories of documents at issue, regardless of whether they are classified as core or non-core deliverables, and the documents are designated as “classified” under the CPO, not AEO. In the context of the parties’ contractual relationship, the Court agrees with Nvision that the documents at issue are “known” to Nvision within the meaning of the CPO and therefore, are not correctly classified as AEO. Jalex appears to concede all the documents at issue relate to the parties’ contracts that both parties have directly placed in issue through the claims in Nvision's first amended and supplemental complaint and Jalex's counterclaim. Jalex has not rebutted Nvision's proffer that Nvision “was involved in the development” of all the documents at issue because the documents were generated essentially at the request of Nvision when Jalex agreed to perform contractual work for Nvision.
B. Plaintiff's Sealed Motion to Overrule Objections and Compel Discovery Responses
1. summary of Nvision's arguments
On July 22, 2015, Nvision served its first set of written discovery on Jalex.[70] Nvision's objections with regard to Jalex's responses are organized into eight sections, briefly addressed below.
a. Jalex's “preliminary statement” and “general objections”
b. Jalex's objection to definition of “Jalex”
c. Jalex's prophylactic objections allegedly protecting nothing should be stricken
Nvision asks the Court to “strike Jalex's superfluous objections, or alternatively overrule Jalex's objections that limit Jalex's responses and order that Jalex fully respond to these document requests.”[76] Nvision argues that Jalex refuses to withdraw its objections to Nvision's requests for production 1, 2, 3, 5, 9, and 11–20, even though Jalex is not withholding documents responsive to these requests.[77] Nvision asserts that
if no responsive documents are being withheld, then the objections are superfluous and should be overruled and stricken. On the other hand, if Jalex's assertion that no documents are being withheld on the condition that one accepts the limitations imposed by Jalex's limited interpretations on the document requests, then Nvision should be entitled to know what Jalex is withholding.[78]
d. overruling Jalex's specific objections to requests for production
Nvision asks the Court to overrule Jalex's objections to requests for production 4, 15–20, and order that Jalex produce documents responsive to this request.[79] The requests for production and Jalex's responses at issue are as follows:
RFP 4 All correspondence between JALEX and any vendors, contractors, and manufacturers which rendered services to or on behalf of Nvision, including any letters, faxes, and emails.[80]
Objection: JALEX objects to this Request on grounds it is vague and overbroad to the extent it can be interpreted to request documents between vendors, contractors, and manufacturers for work on behalf of any client other than Nvision. Moreover, the Request seeks documents which are irrelevant to the scope of work done on behalf of Nvision and to the cause of action for breach of contract, fraud and tortious interference with business relationships alleged in the pleadings. Further responding, JALEX objects to the Request to the extent the information is protected from disclosure pursuant to various non-disclosure agreements with JALEX's vendors, contractors, and manufacturers.[81]
*8 Subject to objections:
Response:
Will supplement.[82]
RFP 15 All documents referring or relating to JALEX's policy or practice regarding the use of Jalex's customer information or materials in the development of JALEX's new products.[83]
RFP 16 All documents referring or relating to JALEX's compensation of current or former JALEX customers for JALEX's use of customer information or materials in the development of JALEX's new products.[84]
Objection [to RFP 15 and 16]: JALEX objects to this Request on grounds it is facially overbroad and seeks information which is irrelevant. Federal Rule of Civil Procedure 26 does not permit fishing expeditions for potential future claims. This Request seeks documents which are unrelated to JALEX's work for Nvision or the alleged causes of action for breach of contract, fraud and/or tortious interference with business relationships. This request also ignores the Court's instruction in its July 27, 2015 Order on JALEX's Motion to Quash and for Protective Order as to Third Party Subpoenas that “Nvision should be mindful that any future discovery requests shall be relevant to causes of action pleaded in their complaint.” Accordingly, JALEX will not respond further to this Request.[85]
RFP 17 All pricing agreements between JALEX and any vendors, contractors, and manufacturers which rendered services to or on behalf of Nvision, including [any] preferential pricing indexes, percentage discounts or other price reductions for the products or services rendered to or on behalf of JALEX.[86]
Objection: JALEX objects that this request is vague and ambiguous because it is unclear whether it is intended to relate specifically to work done by JALEX on behalf of Nvision only, or more generally to JALEX's own product development business which is wholly unrelated to its business relationship with Nvision. To the extent it may be interpreted to refer to the latter, JALEX objects to this Request on grounds it is overbroad and seeks information which is irrelevant to the extent it seeks documents other than those specifically related to work done for Nvision. The Request also relates to information which may be subject to non-disclosure agreements with third parties who are not parties to this lawsuit. This Request seeks documents which are unrelated to JALEX's work for Nvision or the alleged causes of action for breach of contract, fraud and/or tortious interference with business relationships. The Federal Rule of Civil Procedure 26 does not permit fishing expeditions for potential future claims. This request also ignores the Court's instruction in its July 27, 2015 Order on JALEX's Motion to Quash and for Protective Order as to Third Party Subpoenas that “Nvision should be mindful that any future discovery requests shall be relevant to causes of action pleaded in their complaint.” (Doc. 24). JALEX has no objection to producing responsive documents, if any, related specifically to work done by JALEX on behalf of Nvision.[87]
Subject to objections:
Response:
None[88]
RFP 18 All invoices, bills, statements, accounts, quotes, or charges that JALEX received from vendors, contractors, and manufacturers for products or services rendered to or on behalf of JALEX.[89]
*9 RFP 19 All delivery receipts, inventory counts, logs, or other records of the products delivered by vendors, contractors, and manufacturers to JALEX for services rendered to or on behalf of JALEX.[90]
Objection [to RFP 18–19]: JALEX objects that this request is vague and ambiguous because it is unclear whether it is intended to relate specifically to work done by JALEX on behalf of Nvision only, or more generally to JALEX's own product development business which is wholly unrelated to its business relationship with Nvision. To the extent it may be interpreted to refer to the latter, JALEX objects to this Request on grounds it is overbroad and seeks information which is irrelevant to the extent it seeks documents other than those specifically related to work done for Nvision. The Request also relates to information which may be subject to non-disclosure agreements with third parties who are not parties to this lawsuit. This Request seeks documents which are unrelated to JALEX's work for Nvision or the alleged causes of action for breach of contract, fraud and/or tortious interference with business relationships. The Federal Rule of Civil Procedure 26 does not permit fishing expeditions for potential future claims. This request also ignores the Court's instruction in its July 27, 2015 Order on JALEX's Motion to Quash and for Protective Order as to Third Party Subpoenas that “Nvision should be mindful that any future discover requests shall be relevant to causes of action pleaded in their complaint.” (Doc. 24). JALEX has no objection to producing responsive documents, if any, related specifically to work done by JALEX on behalf of Nvision.[91]
Subject to objections:
Response:
See documents previously produced Bates labeled JALEX000001 to JALEX000816, produced subject to the stipulated Confidentiality and Protective Order.
RFP 20 All correspondence between JALEX and any vendors, contractors, and manufacturers which rendered services to or on behalf of JALEX, including any letters, faxes, and emails.[92]
Objection: JALEX objects that this request is vague and ambiguous because it is unclear whether it is intended to relate specifically to work done by JALEX on behalf of Nvision only or more generally to JALEX's own product development business which is wholly unrelated to its business relationship with Nvision. To the extent it may be interpreted to refer to the latter, JALEX objects to this Request on grounds it is overbroad and seeks information which is irrelevant to the extent it seeks documents other than for work done specifically for Nvision. The Request also relates to information which may be subject to non-disclosure agreements with third parties who are not parties to this lawsuit. This Request seeks documents which are unrelated to JALEX's work for Nvision or the alleged causes of action for breach of contract, fraud and/or tortious interference with business relationships. The Federal Rule of Civil Procedure 26 does not permit fishing expeditions for potential future claims. This request also ignores the Court's instruction in its July 27, 2015 Order on JALEX's Motion to Quash and for Protective Order as to Third Party Subpoenas that “Nvision should be mindful that any future discovery requests shall be relevant to causes of action pleaded in their complaint.” (Doc. 24). JALEX has no objection to producing responsive documents, if any, related specifically to work done by JALEX on behalf of Nvision.[93]
*10 Subject to objections:
Response:
See documents previously produced Bates labeled JALEX000001 to JALEX000816, produced subject to the stipulated Confidentiality and Protective Order.[94]
First, Nvision argues that “Jalex avoids disclosing the work it is doing with the vendors in its own name or on behalf of its affiliated companies, such as Thogus and RP+M.”[95] Second, Nvision asserts, in sum, that these document requests are relevant to Nvision's improper competition and tortious activity claims.[96]
e. Jalex's evasive non-answers to interrogatories
Nvision asks the Court to overrule Jalex's objections to interrogatories 1–3,[97] and order that Jalex supplement its responses.[98] The interrogatories and Jalex's responses at issue are as follows:
ROG 1: Describe JALEX's policy or practice of adding markups, surcharges, or other assessments to vendor, contractor, or manufacturer invoices or charges, including (a) when JALEX started adding markups, surcharges, or other assessments; (b) what type of invoices to which markups, surcharges, or other assessments are added or not added; © how JALEX determines what the markups, surcharges, or other assessments will be; (d) who determines the amount of the markups, surcharges, or other assessments to be added or whether markups, surcharges, or other assessment will be applied; and (e) when JALEX adds the markups, surcharges, or other assessments.[99]
Objection: JALEX objects to Interrogatory No. 1 because it is overbroad to the extent it seeks information regarding JALEX's clients other than Nvision. JALEX further objects to the extent it also seeks information which is not relevant or reasonably calculated to lead to the discovery of admissible evidence. Further responding, JALEX objects to the terms “markups, surcharges, or other assessments” as those terms are not defined and to the extent they are the subject of expert testimony. Finally, it calls for highly confidential and proprietary information and considerations. Any disclosure must be done pursuant to the Stipulated Protective Order.[100]
Subject to these objections:
Answer: The invoices submitted to Nvision consisted of JALEX's costs, including, but not limited to, administrative and clerical costs associated with processing, coordinating, tracking accounting for, and advancing payment on behalf of Nvision for goods and services which JALEX acquired on behalf of Nvision. Generally, Tom Zink determined the amount of the cost to be submitted to Nvision.[101]
ROG 2: Describe JALEX's policy or practice of discussing or disclosing to JALEX's customers the markups, surcharges, or other assessments to vendor, contractor, or manufacturer invoices or charges that JALEX imposes, including (a) whether the policy or practice is disclosed to the customer; (b) how the policy or practice is discussed or disclosed to the customer; ©) when the policy or practice is discussed or disclosed to the customer; and (d) where the policy or practice is discussed or disclosed to the customer.[102]
*11 Objection: JALEX objects to this Interrogatory because it is overbroad to the extent it seeks information regarding JALEX's clients other than Nvision. JALEX further objects to the extent it also seeks information which is not relevant or reasonably calculated to lead to the discovery of admissible evidence. Further responding, JALEX objects to the terms “markups, surcharges, or other assessments” as those terms are not defined and to the extent they are the subject of expert testimony.[103]
Subject to these objections:
Answer: JALEX's inclusion of actual costs was disclosed in the Development Services Agreement, QA/RA Contract, Pedicle Screw System Agreement and Cervical Plate Agreement[ ] on or before the date each was executed by Nvision. Nvision was provided with a copy of each executed Contract.[104]
ROG 3: Quantify the amount of the markups, surcharges, or other assessments that JALEX imposed and charged to Nvision on vendor, contractor, or manufacturer invoices or charges for services rendered to or performed on behalf of Nvision.[105]
Objection: JALEX objects to the terms “markups, surcharges, or other assessments” as those terms are not defined and to the extent they are the subject of expert testimony. Finally it calls for highly confidential and proprietary information and considerations. Any disclosure must be done pursuant to the Stipulated Protective Order.[106]
Answer: Please see documents previously produced Bates labeled JALEX00001 through JALEX000816, produced subject to the Stipulated Protective Order, which includes the invoices submitted by vendors to JALEX and the JALEX invoices submitted to Nvision.[107]
Nvision argues that Jalex did not provide complete answers to the interrogatories. Nvision asserts “JALEX omits answering when JALEX started adding the markups, the types of invoices to which markups are applied, how JALEX determines the amount of markup, or when JALEX adds the markups” in its response to interrogatory 1.[108] In its response to interrogatory 2, Nvision argues “JALEX does not address its policy of adding markups to vendor charges at all and only benignly references the proposals (which JALEX characterizes as ‘Agreement’ or ‘Contract’) that addresses ‘actual costs.’ ”[109] Nvision asserts “JALEX's invoices to Nvision do not regularly identify the vendors, the services being provided by the vendors, the quantity of the products provided by the vendors, [or] when the products or services were renders or delivered” in response to interrogatory 3.[110]
f. Jalex's refusal to answer interrogatories 5 and 6
Nvision asks the Court to order Jalex to provide full and complete answers under oath to interrogatories 5 and 6.[111] The interrogatories and Jalex's rseponses at issue are as follows:
ROG 5: Describe JALEX's new product developer business (as compared to JALEX's consulting business for third-party product developers), including (a) when JALEX began developing new products under its own name; (b) identifying what products JALEX has developed or is developing; ©) the regulatory status of the products JALEX has developed or is developing; (d) how JALEX uses its customer's information to develop JALEX's products; and (e) how JALEX compensates its customers for their contributions to the development of JALEX's products.[112]
*12 ROG 6: Describe the products JALEX is developing or has developed with the intention of launching to market in 2015 as disclosed in paragraph 32 of JALEX's Verified Complaint in the Ohio Lawsuit.[113]
Objection [to ROG 5 and 6]: JALEX objects to this Interrogatory on grounds that it is overbroad because it seeks information concerning a party without regard to whether the information sought is related to the causes of action alleged. The Interrogatory seeks information regarding ‘JALEX's new product developer business’ which is not related to the contracts at issue or the alleged causes of action for breach of contract, fraud and/or tortious interference with prospective business relationships. As such, it is not limited to matters pertinent to JALEX's business with Nvision. The Federal Rules of Civil Procedure 26 does not permit fishing expeditions for potential future claims. This request also ignores the Court's instruction in its July 27, 2015 Order on Jalex's Motion to Quash and for Protective Order as to Third Party Subpoenas that ‘Nvision should be mindful that any future discovery requests shall be relevant to causes of action pleaded in their complaint.” (Doc. 24). Accordingly, JALEX will not respond further to this Interrogatory.[114]
Nvision asserts that Jalex has refused “to answer the inquiries concerning JALEX's product development program as irrelevant [ ] and affirmatively den[ies] its existence under the cover of [AEO].”[115] Nvision argues these interrogatories are directly relevant to Nvision's claims, and do not invade third-party confidences.[116]
g. Jalex's scrambled document production
Nvision asks the Court to order Jalex to produce documents in the size and manner the documents are maintained in the ordinary course of business.[117] Nvision asserts that the materials provided in Jalex's document production are out of “chronological sequence” and have been reduced in size.[118] Nvision also states that emails have been separated from email attachments and responses to the emails.[119]
h. Jalex's investigator's file
Nvision asks the Court order Jalex to produce the file of Kelmar Global, a private investigator hired by Jalex.[120] Nvision asserts that Jalex previously produced a report from the investigator which “summarizes the public investigator tailing and photographs of Thomas Zink.”[121] Nvision has requested the entirety of the investigator's file, but Jalex has refused to deliver the remainder of the file.[122]
i. Jalex's inappropriate AEO designations
Nvision challenges Jalex's AEO designation to documents JALEX000630–JALEX000755 and JM–009005 through JM–011512 and asks that the designation be disallowed by the Court.[123]
2. summary of Jalex's arguments
On December 3, 2015, Jalex filed its response to Nvision's motion.[124] The response is not organized to correspond to Nvision's motion and does not appear to present responsive arguments to each challenge raised by Nvision. In sum, Jalex's response presents four main arguments. First, Jalex argues that Nvision itself filed general objections.[125] Second, Jalex states, quoting Nvision, that “JALEX is not developing, planning or producing any form of its own implantable spinal device, whether similar or dissimilar to any such device prepare for or marketed by Nvision.”[126] Jalex also states that “there are no ‘policies or practices’ regarding Jalex's use of Nvision's information or materials in the development of any product developed for or on behalf of Nvision.”[127] Third, in response to Jalex's objection that its document production is “scrambled,” Jalex argues that Nvision has not specified the form in which electronically store information is to be produced, as required by FED. R. CIV. P. 34(b)(1)(c),[128] and Jalex is attempting to format and collate Thomas Zink and Melissa Sprang's e-mails, which is expected to be complete in the near future.[129] Fourth, Jalex argues that its investigator's file is protected from disclosure under FED. RULE CIV. P. 26(b)(3)(A) as material prepared in anticipation of litigation or for trial.[130]
3. analysis
*13 The Court has reviewed the submissions of the parties, in addition to hearing argument from the parties during the December 22, 2015 hearing. With respect to Nvision's request to overrule and strike Jalex's “preliminary statement” and “general objections,” the request is DENIED. The record does not show that Jalex withheld any information because of objections, but provided responses subject to the objections. Only limited matters have been referred to the undersigned. Nvision has not demonstrated rulings on admissibility are required at this time. The District Judge will rule on admissibility of the documents at the time they are offered in evidence; Nvision has not explained why an earlier ruling is required.
With respect to Nvision's request that Jalex's parent company, Thogus, and affiliate company RP+M, provide answers to Nvision's discovery, the request is DENIED. Federal Rule of Civil Procedure 34(a)(1) requires that a responding party produce responsive documents that are within their “possession, custody or control.” Documents are deemed to be within the “possession, custody or control” of a responding party if that party either has “actual possession, custody or control” of the documents or if that party “has the legal right to obtain the documents on demand or has the practical ability to obtain the documents from a non-party to the action.”[131] “Rule 34 is broadly construed and documents within a party's control are subject to discovery, even if owned by a nonparty.”[132] The burden, however, is on the party seeking discovery to make a showing that the other party has control over the documents sought.[133] Typically, what must be shown to establish control over documents in the possession of a non-party is that there is “a relationship, either because of some affiliation, employment or statute, such that a party is able to command release of certain documents by the non-party person or entity in actual possession.”[134] To the extent Jalex has possession, custody, or control of non-privileged responsive documents that are documents of Thogus or RP+M, it must produce them and Jalex was understood to agree it would do so at the December 22 hearing. Otherwise, Nvision's motion on this ground is denied.
With respect to Nvision's request the Court “strike Jalex's superfluous objections, or alternatively overrule Jalex's objections that limit Jalex's responses and order that Jalex fully respond to these document requests,” the request is DENIED. As previously stated, the record does not show that Jalex withheld any information because of objections, but has provided responses subject to the objections. Nvision has not demonstrated rulings on admissibility are required at this time, as discussed above.
With respect to RFP 4, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part, and Jalex must produce non-privileged responsive documents relating to Jalex's work for Nvision.
With respect to RFP 15, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part, and Jalex must produce non-privileged responsive documents relating to any policies (not practices) regarding the use of Jalex's customer information or materials in the development of Jalex's new products.
*14 With respect to RFP 16, Nvision's motion is GRANTED in part, Jalex's objections are sustained in part, and Jalex must produce non-privileged responsive documents relating to Jalex's compensation of Nvision for Jalex's use of Nvision's customer information or materials.
With respect to RFP 17, Nvision's motion is GRANTED in part, and Jalex's objections are overruled in part and Jalex must provide non-privileged responsive documents but limited to work Jalex performed for or on behalf of Nvision.
With respect to RFPs 18, 19, and 20, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part and Jalex must provide non-privileged responsive documents relating to Jalex's work for Nvision, and Jalex's services rendered to and on behalf of Nvision, and for Jalex's work relating to interbody fusion devices, cervical plates, pedicle screws, and structurally encoded implant devices (regardless of for whom the work is performed).
With respect to ROGs 1 and 2, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part, and Jalex must supplement its answers to provide non-privileged information regarding policies (not practices) limited to its work for Nvision.
With respect to ROG 3, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part, and Jalex must supplement its answer to provide any further available nonprivileged responsive information.
With respect to ROGs 5 and 6, Nvision's motion is GRANTED in part, Jalex's objections are overruled in part, and Jalex must supplement its answers to provide further nonprivileged information about Jalex's work relating to interbody fusion devices, cervical plates, pedicle screws, and structurally encoded implant devices.
With respect to Nvision's request Jalex produce documents in the size and manner the documents are maintained in the ordinary course of business, the request is DENIED. Jalex has agreed to provide the production in a more accessible format.
With respect to Nvision's request Jalex produce the file of Jalex's investigator, the request is DENIED. The attorney work product doctrine is codified in Federal Rule of Civil Procedure 26(b)(3) and protects not only materials prepared by a party, but also materials prepared by a representative of a party, including attorneys, consultants, agents, or investigators.[135] Nvision has not provided argument or authority to show the investigator's file in question is not properly considered to be work product or that Nvision “has substantial need for the materials to prepare its case and cannot, without undue hardship, obtain their substantial equivalent by other means.”[136] Nevertheless, Jalex, as the party withholding information under a claim of privilege, must serve a “privilege log” for the withheld information within 21 days of the date of this order.
With respect to Nvision's request that Jalex's AEO designation to documents JALEX000630–JALEX000755 and JM–009005–JM–011512 be disallowed by the Court, the request is DENIED. Nvision has not show that the documents are not included among those at issue in Jalex's motion to preserve designated status of confidential information.
C. Defendant's Sealed Motion to Strike Nvision's Motion to Overrule
1. summary of arguments
*15 Jalex asks the Court to strike Nvision's motion to overrule objections and compel discovery responses.[137] Jalex argues that the motion exceeds the ten page limit for dispositive motions set forth in Local Rule CV–7(d)(3) and the scheduling order.[138] In the alternative, Jalex asks the Court for leave to file and extension of time to file a response that is the same length as Nvision's.[139]
2. analysis
The Court denies Jalex's motion to strike. Nvision's response is only thirteen pages in excess of the presumptive page limitation and both sides have been afforded an opportunity to present further argument at the December 22, 2015 hearing. Therefore, the motion is DENIED.
IV. CONCLUSION
For the reasons stated in the hearing record and as summarized in this order,
IT IS ORDERED that defendant's motion to preserve designated status of classified information, filed November 25, 2015,[140] is DENIED.
IT IS ALSO ORDERED that plaintiff's sealed motion to overrule objections and compel discovery responses, filed November 30, 2015,[141] is GRANTED in part and DENIED in part. To the extent that this order, as addressed at the December 22 hearing, calls for Jalex to supplement its document production or amend interrogatory answers or serve a privilege log, it must do so within 21 days of the date of the order.
IT IS FURTHER ORDERED that defendant's sealed motion to strike Nvision's motion to overrule, filed December 3, 2015,[142] is DENIED.
IT IS ALSO ORDERED that the limited matters referred to the undersigned addressed with this order[143] are RETURNED to the District Judge.
NOTICE OF RIGHT TO OBJECT
Rule 72 (a) of the Federal Rules of Civil Procedure provides that a party may file and serve any objection to an order entered by a magistrate judge on a nondispositive matter within 14 days after being served with a copy of the order. The district judge must consider timely objections and modify or set aside any part of the order that is clearly erroneous or contrary to law.
Footnotes
Docket no. 46. A disk containing the documents at issue in the motion were submitted for the Court's in camera inspection. The undersigned has reviewed the documents on the disk.
Docket no. 48.
Docket no. 51.
Docket no. 54.
Docket no. 59.
Docket no. 56.
Docket no. 31.
Id. at 11–14.
Docket no. 39 at 8.
Docket no. 41.
Docket no. 42.
Docket no. 34.
Docket no. 46. Jalex submits four exhibits in support of its motion: (1) the CPO; (2) affidavit of Jennifer Palinchik (“Palinchik aff”); (3) November 19, 2015 article from the San Antonio Business Journal online regarding Nvision's products; and (4) printouts from Nvision's website concerning products. Id. at 10–27.
Docket no. 50.
Docket no. 48. Nvision submits nineteen exhibits in support of its motion.
Docket no. 51. Jalex submits four exhibits in support of its motion: (1) the CPO; (2) plaintiffs’ responses and objections to defendant's first set of written discovery; (3) plaintiffs’ responses and objections to defendant's second set of written discovery; and (4) letter dated October 15, 2015, from defendant's counsel Vaughan E. Waters to plaintiff's counsel Derick Rodgers.
FED. R. CIV. P. 26(b)(1) (emphasis added) (eff. Dec. 1, 2015).
FED. R. CIV. P. 26(b)(2)(C)(i).
FED. R. CIV. P. 26(b)(2)(C)(i)–(iii).
FED. R. CIV. P. 33(a) & (c).
FED. R. CIV. P. 33(a)(1).
FED. R. CIV. P. 34(a)(1).
FED. R. CIV. P. 30(a)(2)(A)(i) and (d)(1).
FED. R. CIV. P. 36(a)(1).
FED. R. CIV. P. 37(a)(1).
FED. R. CIV. P. 37(a)(4).
McLeod, Alexander, Powel & Apffel, P.C. v. Quarles, 894 F.2d 1482, 1485 (5th Cir. 1990). See also SEC v. Brady, 238 F.R.D. 429, 436 (N.D. Tex. 2006).
FED. R. CIV. P. 26(c)(1).
See, e.g., Shingara v. Skiles, 420 F.3d 301, 305–06 (3rd Cir. 2005).
Id. at 306 (citing Glenmede Trust Co. v. Thompson, 56 F.3d 476, 483 (3d Cir. 1995)) (further citation omitted).
In re Terra Int'l, 134 F.3d 302, 306 (5th Cir. 1998) (“Rule 26(c)’s requirement of a showing of good cause to support the issuance of a protective order indicates that ‘[t]he burden is upon the movant to show the necessity of its issuance, which contemplates a particular and specific demonstration of fact as distinguished from stereotyped and conclusory statements.’ United States v. Garrett, 571 F.2d 1323, 1326 n.3 (5th Cir. 1978); see also 8 CHARLES ALAN WRIGHT, ARTHUR R. MILLER AND RICHARD L. MARCUS, FEDERAL PRACTICE AND PROCEDURE § 2035, at 483–86 (2d ed. 1994).”).
Regan–Touhy v. Walgreen Co., 526 F.3d 641, 647 (10th Cir. 2008).
Hastings v. N.E. Indep. Sch. Dist., 615 F.2d 628, 631 (5th Cir. 1980).
FED. R. EVID. 501.
United States v. Juarez, 573 F.2d 267, 276 (5th Cir.), cert. denied, 439 U.S. 915, 99 S. Ct. 289 (1978).
Hickman v. Taylor, 329 U.S. 495, 507–10, 67 S. Ct. 385, 392–93 (1947).
Id. at 511, 67 S. Ct. at 393.
In re Grand Jury Proceedings, 43 F.3d 966, 972 (5th Cir. 1994).
FED. R. CIV. P. 26(b)(3)(A)(ii).
FED. R. CIV. P. 26(b)(5); 1993 Advisory Comm. Notes to FED. R. CIV. P. 26 at ¶ 33.
Id.
FED.R.CIV.P. 26(b)(5)(A)(ii); 1993 Advisory Comm. Notes to FED. R. CIV. P. 26 at ¶ 34.
FED. R. CIV. P. 26(b)(5). See, e.g., United States v. Constr. Prods. Res., Inc., 73 F.3d 464, 473 (2d Cir.) (“To facilitate its determination of privilege, a court may require ‘an adequately detailed privilege log in conjunction with evidentiary submissions to fill in any factual gaps.’ ”), cert. denied, 519 U.S. 927, 117 S. Ct. 294 (1996); Estate of Manship v. United States, 232 F.R.D. 552, 561 (M.D. La. 2005) (explaining Rule 26(b)(5) “employs the mandatory term, ‘shall,’ requiring that the responding party prepare a privilege log where a privilege is asserted”), rec. adopted, 97 A.F.T.R. 2d 2006–1068 (Jan. 13, 2006); Newpark Envtl. Serv., L.L.C. v. Admiral Ins. Co., No. Civ. A 99–033, 2000 WL 136006, at * 4 (E.D. La. Feb. 3, 2000) (detailed log in support of attorney-client and work product privileges required). Former Local Rule CV–26(e) specified a procedure for preserving and presenting claims of privilege. But, that rule was amended effective December 1, 2000, to delete former subsection (e) because “[t]he local rule simply restates the procedure clearly established by case law and thus serves no good function.” Local Civil Rule CV–26(e) and Committee Notes, LOCAL COURT RULES, UNITED STATES DIST. CT., WEST. DIST. TEXAS.
Constr. Prods. Res., 73 F.3d at 473.
See Alleyne v. N.Y. State Educ. Dept., 248 F.R.D. 383, 386 (N.D.N.Y. 2008).
1993 Notes to FED. R. CIV. P. 26 at ¶ 35.
Hodges, Grant & Kaufmann v. United States, 768 F.2d 719, 721 (5th Cir.1985). See also United States v. Rodriguez, 948 F.2d 914, 916 (5th Cir.1991), cert. denied, 504 U.S. 987, 112 S. Ct. 2970 (1992) (attorney-client privilege must be specifically asserted with respect to particular documents) (citing United States v. El Paso Co., 682 F.2d 530, 539 (5th Cir. 1982)).
FED. R. CIV. P. 37(b)(2).
Dorf & Stanton Commc'ns. v. Molson Breweries, 100 F.3d 919, 923 (Fed. Cir. 1996), cert. denied, 520 U.S. 1275, 117 S. Ct. 2455 (1997); 1993 Notes to FED.R.CIV.P. 26 at ¶ 33.
Ritacca v. Abbott Labs., 203 F.R.D. 332, 335–36 (N.D. Ill. 2001); Grossman v. Schwarz, 125 F.R.D. 376, 386–87 (S.D.N.Y. 1989). But see United States v. British Am. Tobacco (Invs.) Ltd., 387 F.3d 884, 890–91 (D.D.C. 2004).
Docket no. 46 at 8.
Id. at 2.
Id.
Id. at 3.
Id. at 5.
Id. at 6. See also docket no. 46–2 (proposed order submitted with motion) and exhibit B, affidavit of Jennifer Palinchik, the president of Jalex, who testifies “[ ] the second and third categories of documents referenced hereinabove, which might be referred to as Non–Core Deliverables, while still needing to be kept confidential from the public at large, might be disseminated beyond Nvision's litigation counsel to its principals, managers, and others within the organization without doing serious harm to Jalex's proprietary interests or to its legal interest in recovering its unpaid invoices from Nvision [ ].”
Id. at 4.
Id. at 5.
Id. at 5.
Docket no. 50 at 2.
Id.
Id. at 2 (quoting CPO, ¶4).
Id. at 3.
Id. at 4.
“An agreed protective order may be viewed as a contract, and once parties enter an agreed protective order they are bound to its terms, absent good cause to modify or vacate the protective order.” Orthoflex, Inc. V. ThermoTek, Inc., Nos. 3:11–cv–870–D & 3:10–cv–2618–D, 2013 WL 3095106, at *3 (N.D.Tex. June 20, 2013) quoting Paine v. City of Chicago, No. 06 C 3173, 2006 WL 3065515, at *2 (N.D.Ill. Oct.26, 2006)). “As with all contracts, the ultimate question is what was the parties’ mutual intent. The answer to that question is to be found within [the protective order's] four corners, and not by reference to what might satisfy the purposes of one of the parties to it.” Id.
Docket no. 34 at 2–3.
Id. at 2.
Id. at 3.
Id. at 3.
Docket no. 48–1.
Docket no. 48 at 8.
Id. at 7.
According to the Palinchik aff, RP+M is a sister company and Thogus is RP+M's parent company. Docket no. 48–13 at 5–6.
Docket no. 48 at 9.
Id. at 8.
Id. at 10.
Id. at 9.
Id.
Id. at 14.
Docket no. 48–5 at 6.
Id.
Id. On September 25, 2015, Jalex supplemented its response to requests for production 4 and 5. Docket no. 48–8 at 2.
Docket no. 48–5 at 10.
Id.
Id. at 10–11.
Id. at 11.
Id.
Id.
Id. at 11.
Id. at 12.
Id. at 11–12.
Id. at 13.
Id.
Id.
Docket no. 48 at 11.
Id. at 14.
Although Nvision's motion asks the Court to overrule Jalex's objections to interrogatories 1–4, id. at 14, Nvision only discusses interrogatories 1–3, see id. at 14–17.
Id. at 14 and 17.
Docket no. 48–2 at 5.
Id.
Id.
Docket no. 48–3 at 5.
Id.
Id.
Id.
Id.
Id. at 6.
Docket no. 48 at 15.
Id. at 16.
Id. at 17.
Id. at 14 and 17.
Docket no. 48–3 at 6.
Id. at 7.
Id. at 6–7.
Docket no. 48 at 19.
Id. at 20.
Id.
Id. at 20–21.
Id. at 20.
Id. at 22.
Id.
Id.
Id. at 22–23.
Docket no. 51.
Id. at 4–5.
Id. at 6–7 (citing docket no. 48 at 6). To be clear, Jalex's response does not affirmatively represent that Jalex is not developing, planning or producing any form of its own implantable spinal device, but quotes plaintiff's attorney addressing the issue. At the December 22 hearing, counsel for Jalex represented that it was their understanding that Jalex was not developing any interbody fusion devices, cervical plates, pedicle screws, and structurally encoded implant devices.
Id. at 7.
Id. at 8.
Id. at 7.
Id. at 8.
Monroe's Estate v. Bottle Rock Power Corp., 2004 WL 737463, at *10 (E.D. La. April 2, 2004).
Id.
Id.
Id. See also Shell Global Solutions (US) Inc. v. RMS Engineering, Inc., 2011 WL 3418396 (S.D.Tex. Aug. 3, 2011) (“Among the factors used by courts to determine whether one corporation may be deemed under control of another corporation are: (a) commonality of ownership, (b) exchange or intermingling of directors, officers or employees of the two corporations, ©) exchange of documents between the corporations in the ordinary course of business, (d) any benefit or involvement of the nonparty corporation in the transaction, and (e) involvement of the non-party corporation in the litigation.”).
United States v. Nobles, 422 U.S. 225, 238–39, 95 S.Ct. 2160, 2170–71, 45 L.Ed.2d 141 (1975).
FED. R. CIV. P. 26(b)(3)(A)(ii).
Docket no. 51 at 3.
Id. at 3.
Id. at 4.
Docket no. 46.
Docket no. 48.
Docket no. 51.
Docket nos. 46, 48, and 51.