Legion Systems, LLC v. Valiant Global Defense Services, Inc.

CourtDistrict Court, M.D. Florida
DecidedAugust 17, 2021
Docket8:20-cv-02321
StatusUnknown

This text of Legion Systems, LLC v. Valiant Global Defense Services, Inc. (Legion Systems, LLC v. Valiant Global Defense Services, Inc.) 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
Legion Systems, LLC v. Valiant Global Defense Services, Inc., (M.D. Fla. 2021).

Opinion

UNITED STATES DISTRICT COURT MIDDLE DISTRICT OF FLORIDA TAMPA DIVISION

LEGION SYSTEMS, LLC,

Plaintiff,

v. Case No: 8:20-cv-02321-KKM-CPT

VALIANT GLOBAL DEFENSE SERVICES, INC.,

Defendant. ___________________________________

ORDER Defendant Valiant Global Defense Services, Inc., moves to dismiss Plaintiff Legion Systems, LLC’s amended complaint. (Doc. 29.) Legion opposes the motion. (Doc. 32.) Because Legion states a plausible claim for relief on the face of its complaint, the Court denies Valiant’s motion. I. BACKGROUND Valiant is a successor-in-interest to Cubic Global Defense, Inc. (Doc. 26 at 1.) Seeking to leverage Legion’s past performance in a certain Mission Training Complex (MTC) and its status as a small business, Cubic sought to team with Legion to submit a proposal for an Army Contract: Solicitation No. W900KK15R0052 Mission Training Complex Capability Support (MTCCS Program). ( at 2–3.) Legion agreed to team exclusively with Cubic on the condition that Legion “receive a ‘guaranteed’ work-share of

three percent (3%) of the total contract value ‘across all Task Orders’ awarded to Cubic under the MTCCS Program.” ( at 5 (emphasis omitted).) In exchange for Legion’s exclusivity, Cubic agreed to the guarantee clause, and the two ultimately entered into a

Teaming Agreement. ( ) Approximately eight months later, Cubic was awarded one of the prime contracts for the MTCCS Program. ( at 5–6; Doc. 26-3 at 4.) Per the Teaming Agreement’s terms, Cubic then negotiated a subcontract with Legion. (Doc. 26

at 6; Doc 26-2 at 5.) To the extent that the federal common law of government contracts is not dispositive, the law of the State of California governs the subcontract. (Doc. 26 at 7; Doc.

26-3 at 19.) The Teaming Agreement’s guarantee clause also appears in the subcontract. Attachment 5 to the subcontract provides that “Legion shall receive the following work- share allocations: 100% of incumbent work. 3% of the total contract across all Task Orders

that Cubic pursues and wins. Not inclusive of Legion Systems, LLC’s incumbent work.” (Doc. 26-3 at 104.) And Article 55 of the subcontract provides as follows: For the duration of this Agreement, the Parties shall be bound on an exclusive basis for the scope of work set forth in Attachment 5, and shall not participate in any effort, individually or jointly with any third party, to offer to the Customer, the U.S. Government, or any third party any proposal with respect to the Program covered hereunder, or enter into any agreement with any such third party with respect to said Program; provided, however, that Cubic shall not be precluded from teaming with other third parties for other work under the Program . . . or for the same scope of work to the extent other suppliers are needed to satisfy the requirements of the Prime Contract . . . . It is further understood that . . . neither Party shall, during the term of this Agreement, undertake any action or communicate any information to any party which may adversely affect any work of the other Party concerning the subject of this Agreement. ( at 27.) Valiant purchased Cubic’s rights under the prime contract shortly after the parties executed the subcontract. (Doc. 26 at 7.) According to Legion, “[f]rom the outset, Valiant wanted to . . . perform the work- share in-house and thereby avoid paying Legion.” ( at 8.) Legion alleges that Valiant

neglected or refused to share information about the task orders awarded to Valiant and that Valiant refused to allow Legion to bid on the task orders awarded to Valiant. ( ) Valiant further “continued to refuse to allocate available work-share to Legion, without any

explanation and despite Legion’s reminders of the 3% guarantee to it.” ( ) Legion also alleges that Valiant curtailed the requisite work-share by “electing to perform Legion’s work-share itself in-house and/or by using another subcontractor.” ( at 9.) This conduct

by Valiant, according to the amended complaint, breached the contract by failing “to allocate sufficient work-share to Legion to equal 3% of the total contract amount of all task orders awarded to Valiant.” ( ) And Legion alleges that, when it “brought this to Valiant’s

attention, Valiant repudiated its obligation to allocate 3% of the work to Legion. Valiant also insisted that Legion renegotiate the Subcontract. This demand to renegotiate breached Valiant’s promise that Legion would be guaranteed 3% of the total contract across all task orders.” ( ) According to Legion, Valiant attempted to terminate the contract for

convenience after its material breach and repudiate its contractual obligations. ( at 10.) Legion then filed this action, alleging that Valiant breached the subcontract (Count I), breached the duty of good faith and fair dealing (Count II), breached the subcontract

by improperly invoking the termination for convenience clause (Count III), and breached the duty of good faith and fair dealing by improperly invoking the termination for convenience clause (Count IV). ( at 11–12, 14–15.) II. LEGAL STANDARD

To survive a motion to dismiss for failure to state a claim, a plaintiff must plead sufficient facts to state a claim that is “plausible on its face.” , 556 U.S.

662, 678 (2009) (quoting , 550 U.S. 544, 570 (2007)). A claim is plausible on its face when a plaintiff “pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged.” When

considering the motion, the court accepts all factual allegations of the complaint as true and construes them in the light most favorable to the plaintiff. , 516 F.3d 1282, 1284 (11th Cir. 2008). This tenet, of course, is “inapplicable to legal

conclusions.” , 556 U.S. at 678. “While legal conclusions can provide the framework of a complaint, they must be supported by factual allegations.” at 679. Courts should limit their “consideration to the well-pleaded factual allegations, documents central to or referenced in the complaint, and matters judicially noticed.”

, 358 F.3d 840, 845 (11th Cir. 2004) (citation omitted). III. ANALYSIS A. Legion successfully states a claim as to Counts I and II.

In its amended complaint, Legion brings a breach of contract claim (Count I) and claim for a breach of the duty of good faith and fair dealing (Count II). Legion successfully states claims for both Counts.

1. Valiant’s argument that the contract does not guarantee a minimum amount of work fails.

Valiant argues that Legion’s complaint fails to state a breach-of-contract claim because the subcontract “does not guarantee Legion a minimum amount of work or, in the alternative, provide for payment to Legion of the contract value of the alleged minimum amount of work, irrespective of whether Legion actually performed the work.” (Doc. 29 at 2.) In short, Valiant argues that the text of the subcontract “does not guarantee a ‘minimum

amount’ of work to Legion after the initial task order.” ( at 7 (emphasis omitted).) For support, Valiant relies on a clause near the beginning of the subcontract that states that “[t]here is no guaranteed minimum of Work hereunder that [Cubic] will issue to [Legion]

after both Parties have executed this Subcontract beyond an initial Order.” ( ; Doc. 26- 3 at 5.) This clause—which appears to be part of the subcontract’s preamble——forms the backbone of most of Valiant’s arguments against Counts I and II. Valiant’s argument is on shaky ground. First, a preamble to a contract is an

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

Related

Pielage v. McConnell
516 F.3d 1282 (Eleventh Circuit, 2008)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Phillips v. Desert Hospital District
780 P.2d 349 (California Supreme Court, 1989)
Spindle v. Travelers Insurance Companies
66 Cal. App. 3d 951 (California Court of Appeal, 1977)
Westlands Water Dist. v. US Dept. of Interior
850 F. Supp. 1388 (E.D. California, 1994)
Kuffel v. Seaside Oil Co.
11 Cal. App. 3d 354 (California Court of Appeal, 1970)
Careau & Co. v. Security Pacific Business Credit, Inc.
222 Cal. App. 3d 1371 (California Court of Appeal, 1990)
Celador International Ltd. v. Walt Disney Co.
347 F. Supp. 2d 846 (C.D. California, 2004)
Copart, Inc. v. Sparta Consulting, Inc.
277 F. Supp. 3d 1127 (E.D. California, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
Legion Systems, LLC v. Valiant Global Defense Services, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/legion-systems-llc-v-valiant-global-defense-services-inc-flmd-2021.