DCT

8:26-cv-01310

Innovative Design Holdings Inc v. Sachi Tech Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 8:26-cv-01310, M.D. Fla., 05/04/2026
  • Venue Allegations: Venue is alleged to be proper based on Defendant PikMyKid having its principal place of business in the district and Defendant 34ED having an established place of business in the district following its merger with PikMyKid, with a substantial part of the events giving rise to the infringement claims occurring there.
  • Core Dispute: Plaintiff alleges that Defendants' "PikMyKid" student dismissal system infringes a patent related to a system and method for notifying school staff of a parent's or driver's arrival for student pickup.
  • Technical Context: The technology addresses the market for automated school dismissal systems, which aim to enhance student safety, security, and logistical efficiency during the end-of-day pickup process.
  • Key Procedural History: The complaint alleges that the patent-in-suit, U.S. Patent No. 9,129,239, survived an Ex Parte Reexamination where its original claims were confirmed patentable and other claims were found patentable as amended. Plaintiff also alleges providing Defendants with pre-suit notice of infringement on at least three occasions, starting in June 2020. The complaint notes that Defendant 34ED acquired Defendant PikMyKid in April 2026, creating a unified enterprise that allegedly continues to infringe.

Case Timeline

Date Event
2012-03-29 '239 Patent Filing/Priority Date
2012-04-03 '239 Patent initially assigned to Discovery Schools, Inc.
2015-09-08 '239 Patent Issue Date
2020-06-25 Plaintiff's predecessor allegedly sends first notice letter to PikMyKid
2022-12-08 '239 Patent Reexamination Certificate Issued
2025-09-08 '239 Patent assigned to Plaintiff INNOVATIVE DESIGN HOLDINGS, INC.
2025-11-20 Date by which Plaintiff alleges PikMyKid had knowledge of infringement
2026-04-07 Defendant 34ED (CENTEGIX) acquires Defendant PikMyKid
2026-04-23 Public demonstration of the accused PMK Dismissal System
2026-05-04 Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

  • Patent Identification: U.S. Patent No. 9,129,239 ("Driver/Parent Arrival Notification System and Method of Notification"), issued September 8, 2015 (the "'239 Patent") Compl. ¶20

The Invention Explained

  • Problem Addressed: The patent's background section describes the chaotic, unsafe, and inefficient nature of traditional end-of-day student dismissal procedures at schools Compl. ¶¶13-15 It notes the difficulties in verifying authorized guardians, managing carpool logistics, and avoiding disruptions to the school environment caused by generalized announcements or face-to-face check-outs '239 Patent, col. 1:30-48 '239 Patent, col. 2:5-34
  • The Patented Solution: The invention is a system that automates and targets dismissal notifications. It uses a "mobile code carrier" (e.g., a vehicle tag or app) containing a unique code associated with a driver and student '239 Patent, abstract When the driver nears the school, a "code reader" detects this code. A processor then queries a database to identify the student and their specific location within the school (e.g., a classroom) and sends a dismissal message only to a display at that location '239 Patent, FIG. 1 '239 Patent, col. 3:1-19 The complaint includes a flowchart from the patent that illustrates the system's logic of identifying a code, associating it with a target and location, and displaying a targeted message Compl. p. 6
  • Technical Importance: This approach sought to create a more orderly and secure dismissal process by ensuring only authorized drivers trigger a dismissal and by delivering notifications directly to where a specific student is located, minimizing widespread disruption Compl. ¶¶16, 19

Key Claims at a Glance

  • The complaint asserts infringement of at least independent claims 1, 10, and 18 of the '239 Patent Compl. ¶¶25, 27, 29, 30
  • Independent claim 1, a method claim, includes the following essential elements:
    • Providing a system comprising a "mobile code carrier", a "code reader", a "processor", "memory" with a data structure, and a "plurality of displays" in different locations.
    • "Identifying" a code from the mobile code carrier with the code reader.
    • "Searching" the data structure to identify a "target" (e.g., a student) and their "location".
    • "Displaying" at the target's location a "predetermined message uniquely related" to that target.
  • The complaint notes the possibility of asserting infringement under the doctrine of equivalents and reserves the right to assert other claims Compl. ¶34 Compl. ¶54

III. The Accused Instrumentality

Product Identification

  • The "PikMyKid student dismissal system" or "PMK Dismissal System," marketed and operated by Defendants SACHI TECH, INC. (d/b/a PikMyKid) and 34ED, LLC. (d/b/a CENTEGIX) Compl. ¶¶6, 23

Functionality and Market Context

  • The accused product is a software platform for managing school dismissals, which the complaint alleges became part of a unified enterprise after an acquisition in April 2026 Compl. ¶6
  • According to the complaint, the system uses a parent's smartphone app, which functions as the code carrier and contains a unique "Dismissal ID" Compl. ¶25 Arrival is detected via methods like geofencing, at which point a parent can use an "announce button" in the app Compl. ¶27
  • A central computer processor is alleged to match the parent's phone ID to the corresponding student and their location, such as a specific teacher's classroom Compl. ¶27
  • Teachers are then notified on their own devices (e.g., smartphones or tablets) to dismiss the specific student, with the complaint alleging that teachers can "filter" a list to see only their assigned students Compl. ¶¶28, 30, 32 A screenshot from the accused product's website shows it is marketed to "Speed Up Dismissal With Real-Time Communication" Compl. p. 12

IV. Analysis of Infringement Allegations

'239 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
providing: a mobile code carrier; The PMK system provides parents with a smartphone app that holds a unique code, such as a "Dismissal ID." ¶25 col. 7:11-12
a code reader operable to identify a code stored on the mobile code carrier when the mobile code carrier is in proximity to the code reader; The system detects a parent's arrival on campus via geofencing or an "announce button" in the app, which communicates the parent's unique Phone ID to the system's central computer. ¶27 col. 7:55-57
a processor... a memory... storing a data structure associating the code with a... target... and... location...; The PMK system uses a computer processor and a database to match the parent's Phone ID to the student's name and their assigned teacher or classroom location. ¶27; ¶31 col. 8:1-12
and a plurality of displays each located in one of a plurality of different locations... Teachers in different classrooms use their smartphones or tablets as displays, and staff use a "dispatcher app" on tablets to receive dismissal notifications. ¶29 col. 9:26-28
identifying the code... searching the data structure... and displaying... a predetermined message uniquely related to the at least one target. The system allegedly identifies the parent, matches them to the student and their classroom, and sends a "unique electronic dismissal notice" to the teacher's device, prompting them to dismiss that specific student. ¶30; ¶32 col. 13:26-41

Identified Points of Contention

  • Scope Questions: A primary issue may be whether a smartphone app that actively communicates its presence via GPS and cellular/Wi-Fi data (as alleged for the accused system) falls within the scope of a "mobile code carrier" being read by a "code reader." The patent's examples include barcodes and RF transmitters '239 Patent, col. 7:35-41, which typically involve a more passive object being read by a distinct, localized reader device.
  • Technical Questions: The complaint alleges the accused system uses geofencing and a central server to detect a parent's arrival Compl. ¶27 A point of contention could be whether this server-side architecture, which receives a signal initiated by the phone itself, functions as the claimed "code reader." The defense may argue this is technically distinct from a localized reader identifying a code on a carrier that comes into its proximity.
  • Functional Questions: Claim 1 requires displaying a message "uniquely related to the at least one target." The complaint alleges the accused system allows teachers to "filter" a list to view students assigned to them Compl. ¶32 This raises the question of whether a filterable list on a teacher's multi-purpose device is equivalent to the claimed system displaying a message that is, by its nature, unique to the student on a dedicated or location-specific display.

V. Key Claim Terms for Construction

  • The Term: "mobile code carrier"

    • Context and Importance: This term's construction is fundamental. The accused system uses a smartphone app Compl. ¶25, whereas the patent provides examples like barcodes and hangtags '239 Patent, col. 7:35-39 Practitioners may focus on this term because its scope will determine whether the patent covers modern, app-based technologies or is limited to the physical token-based systems contemplated in the specification.
    • Intrinsic Evidence for a Broader Interpretation: The specification describes the carrier as being for "wireless data transmission" and designed to be "mobile, or capable of being easily transported" '239 Patent, col. 7:40-42, language that could support including a smartphone.
    • Intrinsic Evidence for a Narrower Interpretation: The patent's figures and primary embodiments depict a distinct carrier object that is "read" by a separate reader, which may suggest an object whose primary function is to be a passive or semi-passive data container, unlike a multifunction smartphone '239 Patent, FIG. 1

  • The Term: "code reader"

    • Context and Importance: This term is coupled to "mobile code carrier". Its definition will be critical to deciding whether the accused system's geofence-and-server combination constitutes a "reader."
    • Intrinsic Evidence for a Broader Interpretation: The term is defined functionally as being "operable to identify a code stored on the mobile code carrier" '239 Patent, cl. 10:11-15 This functional language may allow it to encompass any component or set of components that perform the identification task, regardless of physical form.
    • Intrinsic Evidence for a Narrower Interpretation: The patent's system diagram shows the "CODE READER" as a discrete hardware component separate from the "PROCESSOR" '239 Patent, FIG. 1 This could support an argument that the term requires a specific device at the school campus that performs the "reading" action, rather than a distributed software process initiated by the phone's location services.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement.

    • Inducement is predicated on allegations that Defendants instruct their school customers on how to use the infringing system via user guides, promotional videos, and technical support Compl. ¶¶36-37 Compl. ¶51
    • Contributory infringement is based on the allegation that the PMK Dismissal System is a "critical, material element" of the infringement that is "not a staple in commerce" and is uniquely designed for an automated student dismissal system Compl. ¶38 Compl. ¶52

  • Willful Infringement: Willfulness is alleged based on pre-suit knowledge. The complaint states that the Plaintiff's predecessor sent a notice letter to Defendant PikMyKid on June 25, 2020, explicitly stating that the "'239 Patent" "covers the PikMyKid system" Compl. ¶43 The complaint further alleges that the Plaintiff sent two follow-up letters in late 2025 and that Defendants failed to respond while continuing their allegedly infringing conduct Compl. ¶¶44-46

VII. Analyst's Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can the claim terms "mobile code carrier" and "code reader", which are rooted in the context of technologies like RFID tags and barcode scanners, be construed to cover the accused system's modern architecture of a smartphone app that uses geofencing to report its own location to a remote server?

  • A key evidentiary question will be one of technical and functional equivalence: does the accused product's method-where a parent activates an "announce button" on an app, triggering a server-side process that results in a notification on a teacher's filterable list-perform substantially the same function, in the same way, to achieve the same result as the claimed method of a localized "code reader" triggering a "uniquely related" message on a location-specific display?

  • A third major question relates to willfulness: given the complaint's detailed allegations of multiple, specific pre-suit notice letters dating back several years before the suit was filed, a central focus will likely be on whether Defendants' alleged continued conduct after receiving notice rises to the level of egregious behavior required to warrant enhanced damages.

Loading Complaint