IP Library Granted Patent US 11,954,748
Granted Patent B1
US 11,954,748 · App. 18/158,300 · Granted Apr 9, 2024

Network based reunification management using portable devices

Inventors: James J. Vesterman (Houston, TX); Gary Kincade (Houston, TX); David Van Camp (Houston, TX); Peter J. Trate (Fresno, TX)
Assignee: Raptor Technologies LLC
G06Q50/20G06Q10/101G08B1/00G08B21/0205
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,954,748
App. No.
18/158,300
Granted
Apr 9, 2024
Kind
B1
Abstract

Computing device(s) are configured for managing the reunification of students with parents during an emergency or a drill for a simulated emergency. The reunification of students with guardians may be managed through the operations of various user interfaces (UIs) presented on the device(s). Different UIs may be configured to support different personnel performing different roles in the reunification process. The UIs may include one or more of a student supervisor UI, a location supervisor UI, a runner UI, a guardian greeter UI, a reunification officer UI, or an incident commander UI. The various UIs enable different personnel to track the location and status of individuals, such as students and guardians, during various stages of a reunification process, enable personnel to dynamically update a centralized database with current information regarding the location and status of individuals, and view real time information regarding the location and status of individuals.

Claims (38)

1. A system for managing emergency procedure drills, the system comprising:

a data store comprising drill data; and

a computing device communicably with the data store, the computing device configured to perform operations comprising:

presenting a drill management user interface (UI);

receiving, through the drill management UI, at least one input corresponding to a drill to be performed at a particular location;

storing, at the data store, the at least one input corresponding to the drill to be performed at the particular location; and

following performance of the drill, presenting, in the drill management UI, a drill report generated based, at least in part, on incident data generated by a plurality of user devices in real-time during performance of the drill, each of the plurality of user devices being associated with a respective user and communicably coupled to the data store.

2. The system of claim 1 , wherein the at least one input corresponding to the drill comprises a type of drill to be performed at the particular location.

3. The system of claim 2 , wherein the type of drill to be performed comprises at least one of an evacuation drill, a shelter drill, a lockdown drill, a lockout drill, or a reunification drill.

4. The system of claim 1 , wherein the at least one input corresponding to the drill comprises a timeframe in which the drill should be performed at the particular location.

5. The system of claim 1 , wherein the at least one input corresponding to the drill comprises a frequency at which the drill should be performed at the particular location.

6. The system of claim 1 , wherein the at least one input corresponding to the drill comprises an input indicating a notification message to be sent to one or more user devices prior to a deadline for performing the drill.

7. The system of claim 1 , wherein the at least one input corresponding to the drill comprises an input indicating a notification message to be sent to one or more user devices in response to determining (i) a deadline for executing the drill has passed and (ii) the drill was not performed.

8. The system of claim 1 , wherein the at least one input corresponding to the drill comprises an input indicating a notification message to be sent to one or more user devices in response to determining (i) a deadline for executing the drill has passed and (ii) the drill report has not been uploaded to the data store.

9. The system of claim 1 , wherein the operations further comprise automatically transmitting the drill report for display at a second computing device.

10. The system of claim 9 , wherein the second computing device is associated with a government agency.

11. The system of claim 1 , wherein the particular location comprises a school building.

12. The system of claim 1 , wherein the particular location comprises multiple school buildings, each of the multiple school buildings being associated with a particular school district.

13. The system of claim 12 , wherein:

the at least one input comprises one or more requirements for execution of the drill at each of the multiple school buildings associated with the particular school district; and

the at least one input is received from an account associated with an administrator of the particular school district.

14. A computer-implemented method comprising:

presenting a drill management user interface (UI);

receiving, through the drill management UI, at least one input corresponding to a drill to be performed at a particular location;

storing, at a data store, the at least one input corresponding to the drill to be performed at the particular location; and

following performance of the drill, presenting, in the drill management UI, a drill report generated based, at least in part, on incident data generated by a plurality of user devices in real-time during performance of the drill, each of the plurality of user devices being associated with a respective user and communicably coupled to the data store.

15. The method of claim 14 , wherein the at least one input corresponding to the drill comprises at least one of a type of drill to be performed at the particular location, a timeframe in which the drill should be performed at the particular location, or a frequency at which the drill should be performed at the particular location.

16. The method of claim 15 , wherein the type of drill to be performed comprises at least one of an evacuation drill, a shelter drill, a lockdown drill, a lockout drill, or a reunification drill.

17. The method of claim 14 , wherein the at least one input corresponding to the drill comprises an input indicating a notification message to be sent to one or more user devices in response to determining a deadline for executing the drill has passed and (i) the drill was not performed or (ii) the drill report has not been uploaded to the data store.

18. The method of claim 14 , wherein the particular location comprises multiple school buildings, each of the multiple school buildings being associated with a particular school district.

19. The method of claim 18 , wherein:

the at least one input comprises one or more requirements for execution of the drill at each of the multiple school buildings associated with the particular school district; and

the at least one input is received from an account associated with an administrator of the particular school district.

20. One or more computer-readable storage media storing instructions which, when executed, cause at least one processor to perform operations comprising:

presenting, on a computing device, a drill management user interface (UI);

receiving, through the drill management UI, at least one input corresponding to a drill to be performed at a particular location;

storing, at a data store, the at least one input corresponding to the drill to be performed at the particular location; and

following performance of the drill, presenting, in the drill management UI, a drill report generated based, at least in part, on incident data generated by a plurality of user devices in real-time during performance of the drill, each of the plurality of user devices being associated with a respective user and communicably coupled to the data store.

Assignments (4)
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME 071567/0725 Recorded Jan 23, 2026
From: ARES CAPITAL CORPORATION
To: RAPTOR TECHNOLOGIES, LLC
Reel/Frame 074494/0071 →
SECURITY INTEREST Recorded Jan 22, 2026
From: RAPTOR TECHNOLOGIES, LLC; SMARTPASS INC.
To: ARES CAPITAL MANAGEMENT LLC
Reel/Frame 073556/0707 →
SECURITY INTEREST Recorded Jun 30, 2025
From: RAPTOR TECHNOLOGIES, LLC
To: ARES CAPITAL CORPORATION, AS AGENT
Reel/Frame 071567/0725 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 3, 2023
From: VESTERMAN, JAMES J.; KINCADE, GARY; CAMP, DAVID VAN; TRATE, PETER J.
To: RAPTOR TECHNOLOGIES LLC
Reel/Frame 063521/0771 →
Continuity (5)
Continuation 17239401 · Apr 23, 2021
Continuation 16563685 · Sep 6, 2019
Continuation 16208032 · Dec 3, 2018
Continuation 15298948 · Oct 20, 2016
Provisional Application 62244619 · Oct 21, 2015
Cited By (2)
US 12,488,406 US 12,620,042