HKM Enterprises, Inc. v. Parsons Government Services, Inc.

District Court, C.D. California·Decided August 9, 2024·No. 2:23-cv-10592·Unknown

Opinion

O

UNITED STATES DISTRICT COURT CENTRAL DISTRICT OF CALIFORNIA

Case No.: 2:23-cv-10592-MEMF-PD HKM ENTERPRISES, INC D/B/A ADAPTIVE

ORDER GRANTING IN PART MOTIONS Plaintiff, TO DISMISS [ECF NOS. 24, 25] v. A NEVADA CORPORATION AND DELAWARE CORPORATION, Defendants. Before the Court are Motions to Dismiss filed by Defendants Parsons Government Services, Inc. and Parsons Corporation. See ECF Nos. 24, 25. For the reasons stated herein, the Court GRANTS IN PART each of the Motions to Dismiss. / / / / / / / / / / / / I. Background A. Factual Allegations1 Plaintiff HKM Enterprises Inc d/b/a Adaptive Launch Solutions (“ALS”) is a business that provides satellite launch integration services. Compl. ¶ 2. Defendants Parsons Government Services, Inc. (“Parsons Government”) and Parsons Corporation (“Parsons,” or collectively with Parsons Government, “Defendants”) are businesses in similar and related industries. Id. ¶¶ 3, 4. Parsons Government is a subsidiary of Parsons. See id. ¶ 4. Parsons Government and Parsons share an office. See id. ¶ 21. ALS began working with the U.S. Space Force2 in 2016, as the U.S. Space Force was implementing a program that eventually became known as Launch Manifest System Integrator (“LMSI”). See id. ¶ 23. ALS was seeking a partner that ALS believed would assist ALS in winning an LMSI contract. See id. Defendants were not aware of the LMSI program at that time. See id. ¶ 24. In a June 2017 meeting, ALS met with a Parsons3 employee Richard Waterman (“Waterman”) and discussed the possibility of ALS partnering with Defendants. See id. ¶ 25. In this meeting and follow up meeting, ALS and Defendants decided to pursue an LMSI contract together. Defendants understood early on that their chance at an LMSI contract depended on partnering with ALS. See id. ¶ 27. In a January 2018 PowerPoint presentation regarding strategy, 1 The facts stated herein are taken from the allegations in Plaintiff HKM Enterprises In, ECF No. 58 (“Compl.”), unless otherwise indicated. For the purposes of this Motion, the Court treats these factual allegations as true, but at this stage of the litigation, the Court makes no finding on the truth of these allegations, and is therefore not—at this stage—finding that they are true. 2 This work was initially with the U.S. Air Force, and the work transitioned to the U.S. Space Force after the latter’s creation in 2019. See Compl. ¶ 23. The Court will refer to this as the U.S. Space Force for simplicity. 3 The Complaint alleges that Waterman is an employee of Parsons. See id. ¶ 6. Parsons asserts in its Reply that Waterman is actually an employee of Parsons Government and argues that Exhibit B to the Complaint shows as such, as Exhibit B states that Waterman’s address is at Parsons Government. See ECF No. 33 at 5 (“Mr. Waterman is an employee of PGS, as Exhibit B to the Complaint shows”); ECF No. 8 at 34 (“Buyer’s Program Manager for this Subcontract is Richard Waterman. The Program Manager’s contact information is as follows: . . . Email: Richard.Waterman@parsons.com . . . Address: Parsons Government Services, Inc.”). Drawing all inferences in favor of ALS, Waterman’s address being at Parsons Government does not negate the possibility that he is a Parsons Employee. Thus, the Court will accept ALS’s allegation on this issue as Defendants stated that a partnership with ALS would give them “best-in-class” qualifications to win an LMSI contract. See id. ¶¶ 29, 30. Parsons Government and ALS executed a “Teaming Agreement” in January 2018. See id. ¶¶ 30, 31; see also ECF No. 8 at 3–15. The Teaming Agreement stated that work would be divided based on each party’s competencies and relevant requirements, and recognized that there would be “potential variation in available work” between the parties. See Compl. ¶ 31. It further stated that “both Parties will play a material role in each MmSIC integration effort with both Parsons and ALS each performing a minimum of 30% of the effort organically over the life of the MmSIC contract execution.” See id. ¶ 32. The MmSIC program is now the LMSI program. See id. ALS relied on this portion of the Teaming Agreement, which it understood to be a promise that ALS would get 30% of workshare, and spent “countless man hours” assisting Defendants in winning an LMSI contract. See id. ¶ 33. Defendants were aware that ALS devoted significant time and effort to assisting Defendants. See id. ¶ 34. Defendants’ representatives continued throughout 2018 to inform ALS both orally and in writing that ALS would receive 30% of total workshare if the parties won an LMSI contract. See id. ¶ 36. Defendants made these statements because Defendants knew that ALS would not assist without such a promise. See id. ¶ 37. In an October 2018 email, Waterman wrote that he needed to convince others that ALS could handle the 30% volume and that it was not a risk to Defendants to negotiate a 30% workshare. See id. ¶¶ 38, 39. Waterman also noted that ALS had “a fair amount invested in this over 2+ years.” See id. ¶ 40. Waterman sent another email in December 2018 with a table that included ALS’s name next to the words “30% labor workshare.” See id. ¶ 41. The email also noted that the hours would be “spread over most of the missions” and that the 30% workshare was the “aggregate value across the contract.” See id. ¶ 42. Defendants won an LMSI contract (the “LMSI Contract”) in February 2017. See id. ¶ 43. Defendants represented in their proposals that they would be relying heavily on ALS’ intellectual property and other trade secret information to deliver if they won such a contract. See id. ¶ 35. Defendants would not have won this contract absent ALS’s assistance because Defendants lacked certain necessary technical know-how and intellectual property, and no other possible subcontract had the know-how and recourses of ALS. See id. ¶ 44. After Defendants won the LMSI Contract, Defendants and ALS needed to negotiate their subcontractor agreement which would become an Indefinite Delivery, Indefinite Quantity (“IDIQ”) contract. See id. ¶ 45. But the work under the LMSI contract was set to begin while this IDIQ contract was being negotiated. See id. ¶ 46. Thus, the parties4 executed a Letter Subcontractor Agreement, which delineated the parties’ obligations under the LMSI Contract until the IDIQ contract was finalized. See id. ¶ 47. Under the Letter Subcontractor Agreement, Defendants paid ALS $40,000 to perform work under the LMSI Contract. See id. ¶ 48. On July 1, 2019, the Parsons Government and ALS executed an IDIQ contract (the “IDIQ Contract”). See id. ¶ 49; see also ECF No. 8 at 17–137. The parties generally worked cooperatively under the IDIQ Contract from July 2019 until the first quarter of 2022, and this work led to four successful launches and the U.S. Space Force awarding additional missions to Defendants. See id. ¶ 50. The IQIQ Contract contains the following paragraph under the header “Estimated Share of Work:” It is the Parties intent that that the division of tasks or workshare on individual integration efforts will be determined based on each Party’s core competencies and individual requirements for each launch. It is expected that both Parties will play a material role in the overall manifesting for the LMSI Program. Therefore, in accordance with the agreement between the Parties as set forth in the Teaming Agreement and further agreed to herein, it’s Parson’s intent that ALS will receive a minimum of 30% of the effort organically over the life of the LMSI contract. See id. ¶ 52. A previous draft of this contract had stated that ALS had a “minimum contract” amount of $40,000, which was the amount ALS earned under the Letter Subcontractor Agreement, and ALS requested that this language be edited to make clear that ALS’s workshare was not limited in that way. See id. ¶¶ 55, 56. The IDIQ Contract also stated that “[Parsons Government] is not obligated to order any amount of work nor does [Parson

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

HKM Enterprises, Inc. v. Parsons Government Services, Inc., (C.D. Cal. 2024).

HKM Enterprises, Inc. v. Parsons Government Services, Inc. (HKM Enterprises, Inc. v. Parsons Government Services, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Torres-Rosado v. Rotger-Sabat
335 F.3d 1 (First Circuit, 2003)
Manzarek v. St. Paul Fire & Marine Insurance
519 F.3d 1025 (Ninth Circuit, 2008)
Birdsong v. Apple, Inc.
590 F.3d 955 (Ninth Circuit, 2009)
Sonora Diamond Corp. v. Superior Court
99 Cal. Rptr. 2d 824 (California Court of Appeal, 2000)
Walsh v. West Valley Mission Cmty. Coll. Dist.
78 Cal. Rptr. 2d 725 (California Court of Appeal, 1998)
Neilson v. Union Bank of California, N.A.
290 F. Supp. 2d 1101 (C.D. California, 2003)
Kelly Park v. Karen Thompson
851 F.3d 910 (Ninth Circuit, 2017)
Engalla v. Permanente Medical Group, Inc.
938 P.2d 903 (California Supreme Court, 1997)
Lee v. City of Los Angeles
250 F.3d 668 (Ninth Circuit, 2001)
Vess v. Ciba-Geigy Corp. USA
317 F.3d 1097 (Ninth Circuit, 2003)