VNS Federal Services, LLC v. Portsmouth Mission Alliance, LLC

CourtDistrict Court, D. Idaho
DecidedJuly 23, 2020
Docket4:19-cv-00318
StatusUnknown

This text of VNS Federal Services, LLC v. Portsmouth Mission Alliance, LLC (VNS Federal Services, LLC v. Portsmouth Mission Alliance, LLC) is published on Counsel Stack Legal Research, covering District Court, D. Idaho primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
VNS Federal Services, LLC v. Portsmouth Mission Alliance, LLC, (D. Idaho 2020).

Opinion

UNITED STATES DISTRICT COURT FOR THE DISTRICT OF IDAHO

VNS FEDERAL SERVICES, LLC, Case No. 4:19-cv-00318-BLW.

Plaintiff/Counter-Defendant, MEMORANDUM DECISION AND ORDER v.

PORTSMOUTH MISSION ALLIANCE, LLC,

Defendant/Counterclaimant,

INTRODUCTION Pending before the Court is Defendant’s Motion for Judgment on the Pleadings. Dkt. 26. The motion is fully briefed and ripe for decision. Pursuant to Local Civil Rule 7.1(d)(1)(B), the Court has determined oral argument is not necessary to resolve the motion. For the reasons explained below, the Court will deny the motion. BACKGROUND In the pending motion, Portsmouth Mission Alliance (Portsmouth) argues VNS Federal Services, LLC’s (VNS Federal) complaint should be dismissed for failure to state a claim upon which relief may be granted. Dkt. 26 at 2. In the complaint, VNS Federal asserts that Portsmouth breached the terms of a subcontract related to work the parties were performing at a gaseous diffusion plant operated by the Department of Energy (DOE) in Piketon, Ohio. Am. Compl.,

Dkt. 13. In 2016, the DOE awarded Portsmouth a prime contract for the provision of infrastructure support services at the plant. Id. at 3. The support services fit into

three general scopes of work: (1) cybersecurity services; (2) records management; and (3) safety and security. The prime contract required Portsmouth to comply with “all applicable Federal, State, and local laws and regulations,” and to comply with “Regulatory Permits, and Agreements and Orders” from the DOE within the

provision of the support services. Dkt. 26 at 3. To perform the work, Portsmouth enlisted the services of a third party, Wastren Advantage Inc. Dkt. 13 at 3. Under the subcontract, Wastren agreed to

perform each of the three scopes of work set forth in the DOE prime agreement on behalf of Portsmouth. In 2018, VNS Federal acquired Wastren’s stock and assumed Wastren’s obligations under the subcontract with Portsmouth. Answer, Dkt. 21 at 3. Pursuant to the terms of a renegotiated subcontract with VNS Federal,

Portsmouth assumed the safety and security scope of work for the plant. Dkt. 13 at 3. VNS Federal remained directly responsible for performing the other two scopes of work—cyber security and records management. Id. at 4. In early 2019, the DOE informed Portsmouth and VNS Federal that DOE representatives would perform an audit of the facility’s cyber security system in

April. Id. Portsmouth and VNS Federal began meeting in February to prepare for the audit by discussing the system, expectations for the audit, and how to handle any potential issues. Id.

In April 2019, the DOE conducted an audit of the facility’s cyber security systems. Dkt. 21 at 5. After the audit, the DOE performed a debriefing with VNS Federal and Portsmouth. Id. The DOE identified 10 items that needed attention and requested a Corrective Action Plan (CAP) to address the items. Id. VNS Federal

and Portsmouth met to create the CAP, which included a timeline to address each of the issues. Id. at 6. During that process, Portsmouth allegedly added two additional items to the 10 item list. Dkt. 13 at 5. VNS Federal used a spreadsheet to

track its corrective work on the items. Id. Portsmouth also enlisted the services of a project manager from one of its affiliate companies to create a Recovery Schedule for the work. Id. According to VNS Federal, the average time built into the plan to address each issue was 214 days. Id. VNS Federal asserts that, by May 31, 2019, it

had addressed eight out of the DOE’s 10 identified items. Id. VNS Federal asserts that, despite its progress and compliance with the timeline built in conjunction with Portsmouth, Portsmouth “began a scheme to improperly terminate” VNS Federal. Id. at 6. VNS Federal asserts Portsmouth did so by refusing it access to information, thereby reducing VNS Federal’s ability to

address the DOE issues. Id. at 7. VNS Federal asserts also that, before Portsmouth notified it of the alleged default of the subcontract, Portsmouth had begun negotiating with a rival subcontractor to replace VNS Federal. Id. at 6. VNS

Federal asserts the rival subcontractor was brought on, and on May 20, 2020, began posting job openings for cybersecurity positions at the plant. Id. at 8. Meanwhile, on May 21, 2019, Portsmouth sent VNS Federal a notice of default of the subcontract, demanding that VNS Federal cure the deficiencies

identified by the DOE. Dkt 13 at 6.The notice gave VNS Federal 10 days to cure the default. Id. VNS Federal alleges it was able to cure 75 percent of the breaches identified by the DOE within the ten-day cure period. Id. at 10–11. VNS Federal

also argues it did not cure the remaining 25 percent of breaches due to impossibility and the fact that one issue had become moot. Id. On June 7, 2020, Portsmouth terminated its subcontract with VNS Federal, citing VNS Federal’s failure to cure all breaches within the ten-day period. Dkt. 21 at 9.

In the present motion, Defendant Portsmouth argues the plain terms of the subcontract with VNS Federal preclude its breach of contract-based claims. Mem. Supp. Mot. J. Pleadings, Dkt. 27. Specifically, Portsmouth argues that, the subcontract expressly provides it could “by written notice of default to [VNS Federal], terminate the whole or any part of the Subcontract” under certain

circumstances. Dkt. 27 at 7. Portsmouth asserts one of those circumstances included any failure by VNS Federal “to perform other provisions of the Subcontract in accordance with its terms.” Id. Portsmouth argues that, because

VNS Federal was responsible for the cybersecurity system, it was responsible for complying with the DOE’s regulations. Id. Portsmouth continues that, because VNS Federal failed to comply with the regulations and then failed to cure the breach within the 10 days provided under its subcontract, VNS Federal materially

breached the subcontract. Id. at 8. Portsmouth argues the alleged breach gave it a clear right to exit the subcontract with VNS Federal. Id. Stated briefly, Portsmouth argues VNS failed to state a claim for breach of

contract because there was no breach by Portsmouth. Dkt. 27. Relatedly, and in the alternative, Portsmouth argues that even if it breached the subcontract, VNS Federal’s breach occurred first, and thus the breach of contract claim is barred by the “first material breach” doctrine. Id. at 11–12.

The Court will analyze the merits of these arguments below. LEGAL STANDARD “After the pleadings are closed – but early enough not to delay trial – a party may move for judgment on the pleadings.” Fed. R. Civ. P. 12(c). A motion for judgment on the pleadings should only be granted if “the moving party clearly establishes on the face of the pleadings that no material issue of fact remains to be

resolved and that it is entitled to judgment as a matter of law.” Hal Roach Studios, Inc. v. Richard Feiner & Co., Inc., 896 F.2d 1542, 1550 (9th Cir. 1989). Judgment on the pleadings is also proper when there is either a “lack of cognizable legal

theory” or the “absence of sufficient facts alleged under a cognizable legal theory.” Balistreri v. Pacifica Police Dept., 901 F.2d 696, 699 (9th Cir. 1988). In reviewing a Rule 12(c) motion, “all factual allegations in the complaint [must be accepted] as true and construe[d] ... in the light most favorable to the non-moving party.”

Fleming v. Pickard,

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Cafasso v. General Dynamics C4 Systems, Inc.
637 F.3d 1047 (Ninth Circuit, 2011)
Aldape v. Lubcke
688 P.2d 1221 (Idaho Court of Appeals, 1984)
Fleming v. Pickard
581 F.3d 922 (Ninth Circuit, 2009)
Jones v. Micron Technology, Inc.
923 P.2d 486 (Idaho Court of Appeals, 1996)
Edged in Stone, Inc. v. Northwest Power Systems, LLC
321 P.3d 726 (Idaho Supreme Court, 2014)
Laguna Construction Company v. Defense
828 F.3d 1364 (Federal Circuit, 2016)
Navarro v. Block
250 F.3d 729 (Ninth Circuit, 2001)

Cite This Page — Counsel Stack

Bluebook (online)
VNS Federal Services, LLC v. Portsmouth Mission Alliance, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/vns-federal-services-llc-v-portsmouth-mission-alliance-llc-idd-2020.