Expert Business Systems, LLC v. Bi4ce, Inc.

233 F. App'x 251
CourtCourt of Appeals for the Fourth Circuit
DecidedMay 9, 2007
Docket06-1265
StatusUnpublished
Cited by2 cases

This text of 233 F. App'x 251 (Expert Business Systems, LLC v. Bi4ce, Inc.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Fourth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Expert Business Systems, LLC v. Bi4ce, Inc., 233 F. App'x 251 (4th Cir. 2007).

Opinion

PER CURIAM:

Plaintiffs Expert Business Systems, LLC, and David Esaw (collectively, “EBS”) appeal from the district court’s award of summary judgment to defendants BI4CE, Incorporated, d/b/a Business Intelligence Force, and Christopher Chodnieki (collectively, “BI4CE”), pursuant to the court’s January 2006 Memorandum Opinion. See Expert Business Systems, LLC v. BI4CE, Inc., 411 F.Supp.2d 601 (D.Md.2006) (the “Opinion”). As explained below, we are satisfied with the district court’s analysis of the issues in its Opinion, and we are content to affirm its judgment in favor of BI4CE.

I.

A.

On February 27, 2004, EBS filed a seven-count complaint against BI4CE in the District of Maryland, alleging that BI4CE had violated the Electronic Communications Privacy Act (the “ECPA”), 18 U.S.C. §§ 2510-2521, and the Computer Fraud and Abuse Act (the “CFAA”), 18 U.S.C. § 1030, and also alleging various state law claims. On December 16, 2005, the parties filed cross-motions for summary judgment. Concluding that there were no issues of material fact in dispute, and that EBS had failed to forecast sufficient evidence to establish either of its two federal causes of action, the district court awarded summary judgment to BI4CE on the ECPA and CFAA claims. By its Opinion, the court declined to exercise supplemental jurisdiction over EBS’s five state law causes of action and dismissed them without prejudice. EBS contends on appeal that the court erred in its Opinion in four specific respects: (1) concluding that there was insufficient evidence to support the ECPA and CFAA claims; (2) failing to view the evidence in the light most favorable to EBS; (3) applying an incorrect evidentiary standard for claims arising under the ECPA and CFAA; and (4) making impermissible credibility determinations.

B.

EBS and BI4CE, which are information technology businesses, entered into an agreement to develop a computer software program after David Esaw, the president of EBS, and Christopher Chodnicki, the president of BI4CE, met in early 2002 at a technology seminar. Pursuant to a Teaming Agreement executed in January 2003, EBS and BI4CE were to work together closely in a joint effort to develop a web-enabled version of EBS’s proprietary software. After several months, however, the business relationship between the parties began to deteriorate and EBS terminated the Teaming Agreement in July 2003. At that time, EBS informed BI4CE that it had breached the Teaming Agreement by, inter alia, remotely accessing an EBS desktop and laptop on several occasions without authorization. EBS asserts that shortly after it notified BI4CE of its alleged breach of the Teaming Agreement, BI4CE transmitted a program, code or command to an EBS desktop computer which rendered it useless. As specific evidence of interception, EBS contends that BI4CE intercepted two emails addressed to fictional employees created by EBS for marketing purposes.

EBS’s contentions on its ECPA and CFAA claims are spelled out in its Complaint and these contentions and the related evidence were carefully reviewed by the district court in the Opinion. These contentions include, inter alia, the assertion *253 that during their business relationship, BI4CE gained access to two of EBS’s computers and, through the unauthorized installation of a remote access program, improperly gained access to the records and data contained therein. Specifically, Count I of the Complaint alleges that BI4CE violated the ECPA by intercepting, disclosing, endeavoring to disclose, and using EBS’s wire, oral or electronic communications. 1 EBS then alleges, in its Count II, that BI4CE violated the CFAA by remotely accessing EBS’s computers without authorization and transmitting a computer program that destroyed one of EBS’s computers. 2

In contrast, BI4CE explains that it installed the remote access program at EBS’s request to allow EBS to remotely access BI4CE’s server. According to BI4CE, this arrangement allowed EBS to make changes to its product website, which BI4CE was developing pursuant to the Teaming Agreement. BI4CE further contends that it received the two emails at issue in the ordinary course of its business arrangement with EBS and immediately forwarded them to EBS. Finally BI4CE asserts that the damage to the computer was caused by EBS’s own system upgrades and file downloads and not by any harmful program or code sent by BI4CE.

Although it is undisputed that BI4CE had physical access to the computers in question on at least one occasion, the evidence fails to demonstrate that BI4CE installed any software that allowed it remote access to EBS’s computers. Instead, the evidence indicates that the software on these computers allowed EBS to initiate remote access to BI4CE’s server, not vice versa. 3 This evidence supports BI4CE’s contention that EBS requested the remote access arrangement so that it could make alterations to its product website, which BI4CE was developing and hosting. EBS also failed to forecast any evidence to demonstrate that BI4CE had “intercepted” the emails at issue or any other wire, oral or electronic communication. Instead, the evidence is that BI4CE received and promptly forwarded to EBS the two contested emails pursuant to the Teaming Agreement and its obligations to host and maintain the EBS product website on its server. Finally, EBS failed to rebut BI4CE’s evidence that the complained of damage to the EBS computer was caused by the activities of an EBS employee, rather than being caused by a *254 harmful program or code sent by BI4CE. 4

II.

We review de novo a district court’s award of summary judgment, viewing the facts and the reasonable inferences drawn therefrom in the light most favorable to the nonmoving party. See EEOC v. Navy Fed. Credit Union, 424 F.3d 397, 405 (4th Cir.2005). Summary judgment is permissible when “there is no genuine issue as to any material fact.” Celotex Corp. v. Catrett, 477 U.S. 317, 323, 106 S.Ct. 2548, 91 L.Ed.2d 265 (1986). When a party has submitted sufficient evidence to support its request for summary judgment, the burden shifts to the nonmoving party to show that there are genuine issues of material fact justifying a trial. Matsushita Elec. Indus. Co. v. Zenith Radio Corp., 475 U.S. 574, 586-88, 106 S.Ct. 1348, 89 L.Ed.2d 538 (1986). And, of course, unsupported speculation is not sufficient to defeat a properly supported summary judgment motion. Ash v. UPS, 800 F.2d 409, 411-12 (4th Cir.1986).

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

Related

In re: NOVANT HEALTH, INC.
M.D. North Carolina, 2023
Halperin v. International Web Services, LLC
70 F. Supp. 3d 893 (N.D. Illinois, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
233 F. App'x 251, Counsel Stack Legal Research, https://law.counselstack.com/opinion/expert-business-systems-llc-v-bi4ce-inc-ca4-2007.