Ferrara Bros. Building Materials Corp. v. FMC Construction LLC

54 Misc. 3d 529, 44 N.Y.S.3d 670
CourtNew York Supreme Court
DecidedMarch 30, 2016
StatusPublished
Cited by1 cases

This text of 54 Misc. 3d 529 (Ferrara Bros. Building Materials Corp. v. FMC Construction LLC) is published on Counsel Stack Legal Research, covering New York Supreme Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Ferrara Bros. Building Materials Corp. v. FMC Construction LLC, 54 Misc. 3d 529, 44 N.Y.S.3d 670 (N.Y. Super. Ct. 2016).

Opinion

OPINION OF THE COURT

Timothy J. Dufficy, J.

It is ordered that the motion is granted, as indicated below:

Briefly, the plaintiff claims that the defendant interfered with its prior contract with FMC Construction LLC (Construction) to provide cement for a construction project, thereby causing it to lose prospective profits from the job. Casa Redimix Concrete Corp. (Casa) claims that it did not know of the existence of the contract between Ferrara Bros. Building Materials Corp. and Best Concrete Mix Corp., Doing Business as Ferrara Bros. Building Materials Corp./Best Concrete Mix (Ferrara) and Construction. To this, plaintiff responds that the date typed into a form agreement between Casa and Construction predates the computer-generated identification footer on the document by 20 days. Ferrara essentially claims that Casa backdated its agreement with Construction to give the impression that it was entered into prior to Ferrara’s contract rather than after Casa’s principals were aware of Ferrara’s contract. Ferrara claims that electronic data such as metadata will reveal the true generation dates and revision histories of the documents.

In response to a request by counsel, in April 2015, over seven years after the case was commenced, Casa provided an affidavit from an information technology specialist. The affidavit indicated that in 2009, two years after the case was commenced, the computers on which the native information was stored had been replaced, and discarded. This was done ostensibly due to a need to update Casa’s computer system. There is no indication that this was an “automatic” process.

Because there is no issue that the subject computer system was destroyed during the lawsuit, the only issues are whether Casa knew or should have known that the computers would have evidence relevant to the case, whether the plaintiff’s delay waived its right to demand the subject electronically stored information, and what sanction, if any, is an appropriate exercise of the court’s jurisdiction.

[531]*531A party that seeks sanctions for spoliation of evidence must show that the party having control over the evidence possessed an obligation to preserve it at the time of its destruction, that the evidence was destroyed with a “culpable state of mind,” and “that the destroyed evidence was relevant to the party’s claim or defense such that the trier of fact could find that the evidence would support that claim or defense” (VOOM HD Holdings LLC v EchoStar Satellite L.L.C., 93 AD3d 33, 45 [1st Dept 2012], quoting Zubulake v UBS Warburg LLC, 220 FRD 212, 220 [SD NY 2003]; Pegasus Aviation I, Inc. v Varig Logistica S.A., 26 NY3d 543, 547-548 [2015]). Where the evidence is determined to have been intentionally or wilfully destroyed, the relevancy of the destroyed documents is presumed (see Zubulake at 220). On the other hand, if the evidence is determined to have been negligently destroyed, the party seeking spoliation sanctions must establish that the destroyed documents were relevant to the party’s claim or defense (see id.).

“The party requesting sanctions for [spoliation] has the burden of demonstrating that a litigant intentionally or negligently disposed of critical evidence, and ‘fatally compromised [the movant’s] ability to’ ” prove a claim or defense (Utica Mut. Ins. Co. v Berkoski Oil Co., 58 AD3d 717, 718 [2009], quoting Lawson v Aspen Ford, Inc., 15 AD3d 628, 629 [2005]; Mendez v La Guacatala, Inc., 95 AD3d 1084, 1085 [2d Dept 2012]).

Electronic documents in their native language form may be discoverable, even when a hard copy has been provided (see 150 Nassau Assoc. LLC v RC Dolner LLC, 30 Misc 3d 1224[A], 2011 NY Slip Op 50182[U] [Sup Ct, NY County 2011]; see Dartnell Enters, v Hewlett Packard Co., 33 Misc 3d 1202[A], 2011 NY Slip Op 51758[U] [Sup Ct, Monroe County 2011]).

Under certain circumstances, the failure of a party to institute a litigation hold or to implement any uniform or centralized plan to preserve data or even the various devices used by the key players in the transaction might demonstrate gross negligence, which would give rise to a rebuttable presumption that the spoliated documents were relevant (see VOOM HD Holdings LLC v EchoStar Satellite L.L.C., 93 AD3d 33, 45 [1st Dept 2012]; AJ Holdings Group, LLC v IP Holdings, LLC, 129 AD3d 504, 505 [1st Dept 2015]).

Metadata, commonly described as “data about data,” is defined as “a set of data that describes and gives information about other data” or “information about a particular data set [532]*532which describes how, when and by whom it was collected, created, accessed, or modified and how it is formatted (including data demographics such as size, location, storage requirements and media information).” (Scotts Co. LLC v Liberty Mut. Ins. Co., 2007 WL 1723509, *3 n 2, 2007 US Dist LEXIS 43005, *10 n 2 [SD Ohio, June 12, 2007, 2:06-CV-899].) It includes all of the contextual, processing, and use information needed to identify and certify the scope, authenticity, and integrity of active or archival electronic information or records. Some examples of metadata for electronic documents include: a file’s name, a file’s location (e.g., directory structure or pathname), file format or file type, file size, file dates (e.g., creation date, date of last data modification, date of last data access, and date of last metadata modification), and file permissions (e.g., who can read the data, who can write to it, who can run it). Some metadata, such as file dates and sizes, can easily be seen by users; other metadata can be hidden or embedded and unavailable to computer users who are not technologically adept (Autotech Tech. Ltd. Partnership v Automationdirect.com, Inc., 248 FRD 556, 557 n 1 [ND Ill 2008]; see generally The Sedona Principles: Best Practices Recommendations and Principles for Addressing Electronic Document Production, comment 12.a [Sedona Conference Working Group Series (2d ed June 2007)], available at https://thesedonaconference.org/download-pub/81 [check “I agree to these terms” and download] [hereinafter, Se-dona Principles 2d]). Although metadata often is lumped into one generic category, there are a few distinct types, including substantive (or application) metadata, system metadata, and embedded metadata (see Sedona Principles 2d, Comment 12.a; United States District Court for the District of Maryland, Suggested Protocol for Discovery of Electronically Stored Information at 25-28, http://www.mdd.uscourts.gov/news/news/ ESIProtocol.pdf).

For purposes of this motion, system metadata is concerned. System metadata includes the author, date and time of creation, and the date a document was modified. System meta-data is relevant if the authenticity of a document is questioned or if establishing “who received what information and when” is important to the claims or defenses of a party (see Hagenbuch v 3B6 Sistemi Elettronici Industriali S.R.L., 2006 WL 665005, *3, 2006 US Dist LEXIS 10838, *10 [ND Ill, Mar. 8, 2006, No. 04 C 3109]). System metadata is not embedded within the file it describes, but is stored externally on the system {see Sedona [533]*533Principles 2d, Comment 12.a). System metadata is used by the computer’s file system to track file locations and store information about each file’s name, size, creation, modification, and usage.

Here, the date and time of creation, which would be contained in the system data, are relevant to the case at bar.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Caldwell v. 928 Gerard Avenue Partners
57 Misc. 3d 857 (Civil Court of the City of New York, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
54 Misc. 3d 529, 44 N.Y.S.3d 670, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ferrara-bros-building-materials-corp-v-fmc-construction-llc-nysupct-2016.