Tripro Consulting, LLC v. CACI, Inc. - Federal

CourtDistrict Court, M.D. Florida
DecidedJuly 3, 2025
Docket6:23-cv-00568
StatusUnknown

This text of Tripro Consulting, LLC v. CACI, Inc. - Federal (Tripro Consulting, LLC v. CACI, Inc. - Federal) is published on Counsel Stack Legal Research, covering District Court, M.D. Florida primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Tripro Consulting, LLC v. CACI, Inc. - Federal, (M.D. Fla. 2025).

Opinion

UNITED STATES DISTRICT COURT MIDDLE DISTRICT OF FLORIDA ORLANDO DIVISION

TRIPRO CONSULTING, LLC,

Plaintiff,

v. Case No: 6:23-cv-568-JSS-DCI

CACI, INC. – FEDERAL,

Defendant. ___________________________________/ ORDER Plaintiff, Tripro Consulting, LLC, initiated this action against Defendant, CACI, Inc. – Federal, alleging breach of contract and a statutory violation. (Dkt. 1.) Pursuant to the parties’ agreement, the court granted Defendant summary judgment as to the statutory violation. (See Dkt. 31 at 5, 8.) The court held a three-day bench trial from January 21 to 23, 2025, on the remaining breach of contract claim. (See Dkts. 77–79.) Upon consideration of the evidence, the court sets forth its findings of fact and conclusions of law in accordance with Federal Rule of Civil Procedure 52 and directs the Clerk to enter judgment in favor of Defendant under Federal Rule of Civil Procedure 58.1

1 To the extent that any findings of fact may constitute conclusions of law, they are adopted as such, and to the extent that any conclusions of law may constitute findings of fact, they are adopted as such. BACKGROUND Plaintiff entered into a subcontract with Defendant to provide cybersecurity

services to the United States government. (See Dkt. 76-1.) Later, after being informed by the government that Plaintiff had lost its security clearance, Defendant notified Plaintiff that it was terminating the contract “based upon customer direction.” (Dkt. 76-2 at 1.) Plaintiff initiated this action alleging that Defendant “materially breached the [subc]ontract by terminating it without a proper basis.” (Dkt. 1 ¶ 15.)

At trial, the court heard testimony from five witnesses. (See Dkts. 71, 72, 74.) Each party called Robert Furstoss as a witness. (See id.) Plaintiff also called as witnesses Joseph Jessop, Uday Shenvi, and Brian McElroy. (See Dkts. 71, 72.) Defendant also called Jeremy Klem. (See Dkts. 72, 74.) The following exhibits were admitted into evidence: Plaintiff’s Exhibits 1 through 6, 10, 11, 14 through 19, 21, 28,

29, 34, and 37, and Defendant’s Exhibits 1 through 15, 17, 18, 20 through 38, 43, 46, and 49. (Dkts. 75, 76.) Following the trial, the parties submitted proposed findings of fact and conclusions of law. (Dkts. 85, 88.) Plaintiff argues that “the breach is clear” because Defendant terminated the subcontract based on the erroneous belief that Plaintiff’s security clearance had lapsed. (Dkt. 88 at 6, 9.) Defendant asserts to the

contrary that it properly terminated the subcontract at the government’s direction after being informed that Plaintiff’s managing member, Brian McElroy, had lost the requisite security clearance. (Dkt 85 at 6–11.) FINDINGS OF FACT The court makes the following findings of fact regarding the execution and

termination of the parties’ contract. In doing so, the court generally credits the witnesses’ statements at trial. Defendant is a federal contractor that provides products and services to the United States government. (Dkt. 77 at 50.) Plaintiff is a subcontractor that worked to protect government communications by certifying cryptographic products for

government use. (Dkt. 78 at 108.) Defendant entered into a contract with the government to perform cybersecurity work for the Command, Control, Computers, Communications, Cyber, Intelligence, Surveillance, and Research (C5ISR) Center, among other government entities. (See Dkt. 76-7 at 1–2; Dkt. 77 at 54.) To fulfill its obligations under that contract—the prime contract—Defendant executed a

subcontract with Plaintiff under which Plaintiff would perform work in support of the prime contract. (See Dkt. 76-1; Dkt. 77 at 55.) The subcontract included the following termination provision: Item 24 – Termination for Convenience

[Defendant] may terminate the [subcontract] in whole or in part if it is determined that a termination is in [Defendant]’s and/or the [g]overnment’s best interests or if the [g]overnment exercises its termination for convenience rights under the [p]rime [c]ontract as defined in [Federal Acquisition Regulation (FAR)] 52.249-6. [Defendant] may terminate this [subcontract] by issuing a written notice of termination to [Plaintiff]. The written notice will include the termination effective date, justification[,] and actions to be taken by [Plaintiff]. In the event that [Defendant] terminates this [subcontract] pursuant to [g]overnment direction, [Plaintiff]’s recovery of termination costs shall be limited to the extent that [Defendant] is able to recover such costs from the [g]overnment.

(Dkt. 76-1 at 14.) The subcontract also incorporated by reference a number of provisions of the FAR, including 52.204-2, which sets forth general security requirements and, among other things, requires subcontractors to comply with the National Industrial Security Program Operating Manual (NISPOM), 32 C.F.R. § 117. (Dkt. 76-1 at 34.) Robert Furstoss, Defendant’s deputy program manager, testified that rather than seek bids from subcontractors, it selected Plaintiff specifically because Plaintiff was already performing related work for C5ISR under another contract. (Id. at 100– 01.) Defendant submitted a Single/Sole Source Justification document to the government explaining that “[n]o other [subcontractors] were considered as [Plaintiff] ha[d] been successfully supporting the [communication security] projects under multiple contracts for several years,” and noting that Plaintiff was “required to transition from another [Cyber Security and Information Assurance] task order to [Defendant].” (Dkt. 76-8 at 1.) Furstoss testified that this practice was standard where a contractor sought to engage and transition a subcontractor from one project to

another. (Dkt. 77 at 101.) Given the sensitive nature of the work involved under the prime contract, all subcontractors were required to have, at a minimum, secret security clearance, a clearance level higher than confidential but lower than top secret. (Dkt. 76-1 at 45; Dkt. 77 at 82–83.) The subcontract also stated that “[i]ndividual [t]ask [o]rders may require higher level security clearances.” (Dkt. 76-1 at 45.) A separate statement of work was prepared that “establishe[d] the requirements for [s]ub[c]ontractor-provided

services.” (Dkt. 76-7 at 2.) That document stated that “[t]he security requirements for this effort are defined in the DD Form 254.” (Id. at 41.) That form, in turn, stated that the “level of facility security clearance . . . required” to work on the contract was top secret and that individual contractors required sensitive compartmented information (SCI) access. (Dkt. 76-39 at 1–2 (emphasis omitted).) Jeremy Klem, Defendant’s

senior security manager assigned to Plaintiff’s contract, explained that Plaintiff was therefore required to have a top secret facility clearance and any individuals who sought to perform work through Plaintiff—including McElroy—to have SCI access. (Dkt. 78 at 181, 183, 185–86.) The statement of work also noted that Jean Goodwin, a contract monitor who oversaw security policies and procedures for the government

as they related to the prime contract, (see Dkt. 78 at 184, 189–90, 237), would ensure Plaintiff’s compliance with the relevant security requirements. (Dkt. 76-7 at 41; see also Dkt. 77 at 90 (Furstoss’s testimony that “[Jean Goodwin] is the C5ISR security officer, so she[ is] in charge of ensuring the active security clearance levels of companies

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

Related

Snepp v. United States
444 U.S. 507 (Supreme Court, 1980)
Salinas-Nix v. Department of the Army
527 F. App'x 956 (Federal Circuit, 2013)
Quadros & Associates v. City of Hampton
597 S.E.2d 90 (Supreme Court of Virginia, 2004)
Horton v. Horton
487 S.E.2d 200 (Supreme Court of Virginia, 1997)
Marriott Corp. v. Combined Properties Ltd. Partnership
391 S.E.2d 313 (Supreme Court of Virginia, 1990)
Payne v. Simmons
350 S.E.2d 637 (Supreme Court of Virginia, 1986)
Culpeper Regional Hospital v. Cynthia B. Jones, Director
767 S.E.2d 236 (Court of Appeals of Virginia, 2015)
Navar, Inc. v. Federal Business Council
784 S.E.2d 296 (Supreme Court of Virginia, 2016)
Advantor Systems Corporation v. DRS Technical Services, Inc.
678 F. App'x 839 (Eleventh Circuit, 2017)
W.C. English, Inc. v. Commonwealth
420 S.E.2d 252 (Court of Appeals of Virginia, 1992)
Gaskins v. United States
652 F.2d 70 (Court of Claims, 1981)

Cite This Page — Counsel Stack

Bluebook (online)
Tripro Consulting, LLC v. CACI, Inc. - Federal, Counsel Stack Legal Research, https://law.counselstack.com/opinion/tripro-consulting-llc-v-caci-inc-federal-flmd-2025.