Snyder v. HMS Technologies, Inc.

CourtDistrict Court, M.D. Florida
DecidedFebruary 8, 2024
Docket8:21-cv-02078
StatusUnknown

This text of Snyder v. HMS Technologies, Inc. (Snyder v. HMS Technologies, 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
Snyder v. HMS Technologies, Inc., (M.D. Fla. 2024).

Opinion

UNITED STATES DISTRICT COURT MIDDLE DISTRICT OF FLORIDA TAMPA DIVISION

DAVID MICHAEL SNYDER,

Plaintiff,

v. Case No. 8:21-cv-2078-VMC-AEP

HMS TECHNOLOGIES, INC., HARRY M. SIEGEL, and SIERRA 7, INC.,

Defendants. /

ORDER This matter is before the Court on consideration of Defendant Sierra7, Inc.’s Motion to Dismiss Amended Complaint (Doc. # 69) and Defendants HMS Technologies, Inc., and Harry M. Siegel’s Motion to Dismiss Plaintiff’s Amended Complaint (Doc. # 70), both filed on January 12, 2024. Plaintiff David Michael Snyder, who is proceeding pro se, responded to both Motions. (Doc. ## 80, 81). For the reasons that follow, the Motions are granted as to standing and the amended complaint is dismissed with leave to amend. I. Background Snyder initiated this action against multiple Defendants on August 30, 2021, asserting claims for false claims under the False Claims Act (“FCA”), false records and statements under the FCA, conspiracy under the FCA, and retaliation under the FCA. (Doc. # 1). On January 13, 2023, the United States declined to intervene. (Doc. # 18). After Snyder’s counsel was permitted to withdraw, Snyder was given time to obtain new counsel. (Doc. # 22). After Snyder failed to obtain new counsel by the extended deadline, the Court dismissed without prejudice the claims Snyder asserted on behalf of the United

States but allowed him to pursue pro se his retaliation claim under the FCA. (Doc. # 27). Snyder later filed the pro se amended complaint on September 5, 2023, asserting “on behalf [of] himself” a claim for FCA retaliation against HMS, Siegel, and Sierra7. (Doc. # 32). Central to the amended complaint is the relationship between HMS, Siegel (the owner of HMS), Snyder’s company (AeroSage LLC), and a subcontractor of AeroSage’s called MCS of Tampa, Inc. (Id. at ¶¶ 31-54); see also (Doc. # 1 at ¶ 157) (“Defendants entered in a subcontract agreement with Relator’s former SDVOSB company, AeroSage LLC . . . .”).

According to the amended complaint, “Plaintiff and Defendants had at least three subcontract agreements and a Teaming Agreement based on Plaintiff’s status as a [Service-Disabled Veteran Owned Small Business (“SDVOSB”)] [similarly situated entity (“SSE”)], and therefore Plaintiff was contractor and agent for Defendants starting on or about November 22, 2016, and continuing until on or about April 28, 2021.” (Doc. # 32 at ¶ 31). “On or about August 14, 2018, Plaintiff had [a] conference call with several HMS executives informing them that Plaintiff believed MCS was violating the [limitations on subcontracting rules applicable to certain federal contracts

(“LOS”)] on this SDVOSB T4NG subcontract, and therefore, Defendants were violating the LOS, . . . and Plaintiff was seeking to replace MCS with another qualified subcontractor that would comply with the LOS.” (Id. at ¶ 36). Snyder sent an email to Defendants on August 28, 2018, further addressing Snyder’s concerns that his company’s subcontractor MCS was not complying with all rules and stating that Snyder’s company AeroSage was obtaining a new subcontractor to replace MCS: As I mentioned earlier, I am now in final phase of written confirmation of agreement with a Unify OEM authorized subcontractor with a presence in VISN 4 that has stated they can provide superior level of services for the Siemens Unify solution including the additional reporting in amendment 1 which has not been provided by MCS. I should have that signed subcontract confirmation later today or tomorrow. As a fellow VIP SDVOSB, you know the critical importance of complying with the VA and SBA rules such as limitations on subcontracting. The current subcontractor, MCS of Tampa, has been violating the limits on subcontracting and I am working to rectify this and ensure compliance for the current base year. MCS is not willing to follow the 13 CFR §125.6 requirements and misrepresented the subcontract work. My new subcontractor and AeroSage will ensure we comply with these limitation [sic] as we have a responsibility to the VA customer, HMS as the prime, our AeroSage representations, the Veterans First Program, and the law. We remain committed to this. As I requested earlier it is critically important that you provide the draft Option Year 1 subcontract agreement, to ensure there is no misunderstanding of the requirements of the contract and the FAR, which we will be able to confirm shortly. I look forward to receiving the option year 1 subcontract, in order to finalize confirmation of compliant level of Unify support for your VA contract. (Id. at ¶ 38). “On or about August 31, 2018, Defendants retaliated against Plaintiff by terminating the Plaintiff’s subcontract option year for a VA T4NG contract stating, ‘With today (8/31/18) being the first day of the option period, we have had to move forward and provide seamless coverage for the VA utilizing another partner that evidenced their capability to provide Siemens Unify support.’” (Id. at ¶ 54). The alleged retaliatory actions include: “Defendants suspended option years on two different VA T4NG subcontracts with the Plaintiff, withheld and then delayed subcontract payments, hired away Plaintiff[’s] assets to perform SDVOSB contracts, and effectively terminated Plaintiff from $10s millions of SDVOSB SSE subcontracts that Plaintiff was essentially the incumbent subcontractor that had agreement for a willing LOS compliant OEM service provider in replacement for MCS in current, option, and future subcontracts or contracts.” (Id. at ¶ 53). According to the amended complaint, “Defendant’s damages

include lost wages or loss of earnings, lost contracting performance credit record, likely future VA SDVOSB contract/subcontract earnings, and future lost earning capacity.” (Id. at ¶ 63). “The direct damages from the Defendants’ and Co-Conspirators’ retaliatory actions from protected disclosures on just these two, then performed, VA T4NG contracts in furtherance of the FCA is at least $9 million in subcontract value and performance history.” (Id. at ¶ 64). “Plaintiff would [have] been awarded and paid these government subcontract funds if Defendants and Co- Conspirators awarded/renewed them with Plaintiff and

Plaintiff’s LOS compliant new subcontractor.” (Id. at ¶ 68). “But for Plaintiffs protected actions, Plaintiff lost earnings on more than $70 million performed, current, option year, and awarded subcontracts that manifestly would have been awarded and earned by the Plaintiff.” (Id.). Now, Defendants move to dismiss the amended complaint, arguing that Snyder lacks standing and that the amended complaint fails to state a claim for FCA retaliation. (Doc. ## 69, 70). Snyder has responded to both Motions (Doc. ## 80, 81), and the Motions are ripe for review. II. Legal Standard

A. Rule 12(b)(1) Motions filed under Federal Rule of Civil Procedure 12(b)(1) question this Court’s jurisdiction over the subject matter of the case. Motions to dismiss for lack of subject matter jurisdiction pursuant to Rule 12(b)(1) may attack jurisdiction facially or factually. Morrison v. Amway Corp., 323 F.3d 920, 924 n.5 (11th Cir. 2003). Where the jurisdictional attack is based on the face of the pleadings, as here, the Court merely looks to determine whether the plaintiff has sufficiently alleged a basis of subject matter jurisdiction, and the allegations in the plaintiff’s complaint are taken as true for purposes of the motion.

Lawrence v. Dunbar, 919 F.2d 1525, 1529 (11th Cir. 1990).

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

Related

Sandra Jackson v. BellSouth Telecommunications
372 F.3d 1250 (Eleventh Circuit, 2004)
Warth v. Seldin
422 U.S. 490 (Supreme Court, 1975)
Papasan v. Allain
478 U.S. 265 (Supreme Court, 1986)
Lujan v. Defenders of Wildlife
504 U.S. 555 (Supreme Court, 1992)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Albert Thomas v. David C. Evans
880 F.2d 1235 (Eleventh Circuit, 1989)
Dolcie Lawrence v. Peter Dunbar, United States of America
919 F.2d 1525 (Eleventh Circuit, 1990)
Clapper v. Amnesty International USA
133 S. Ct. 1138 (Supreme Court, 2013)
Dinuro Investments, LLC v. Camacho
141 So. 3d 731 (District Court of Appeal of Florida, 2014)
Spokeo, Inc. v. Robins
578 U.S. 330 (Supreme Court, 2016)
Strazzulla v. Riverside Banking Co.
175 So. 3d 879 (District Court of Appeal of Florida, 2015)
Roberts v. Swearingen
358 F. Supp. 3d 1341 (M.D. Florida, 2019)
Brown v. Consolidated Freightway
152 F.R.D. 656 (N.D. Georgia, 1993)

Cite This Page — Counsel Stack

Bluebook (online)
Snyder v. HMS Technologies, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/snyder-v-hms-technologies-inc-flmd-2024.