RTIS: Real-Time Threat Identification at the Gate

From Sensor to Alert in Seconds

The RTIS workflow is designed for the realities of stadium ingress: high volume, tight windows, and zero tolerance for false positives reaching your team.

1. 1

   Sensor Capture

   A dedicated RTIS sensor is positioned at a gate, entry lane, or chokepoint. As a person passes through the sensor’s field of view, a single still image is captured. No video is recorded. No continuous surveillance stream is created. The sensor captures one image per detect.

   Technical Detail

   Image payload is sub-100KB. The sensor is purpose-built for this task. It is not repurposed CCTV. Fixed and portable deployment options are available.

2. 2

   Image Transmission

   The captured image is transmitted to the Safience processing environment. Transmission occurs over PoE (wired) or cellular connectivity depending on sensor deployment type. No on-premises server is required. No local processing, no local storage.

   Technical Detail

   Encrypted transmission. No image touches venue infrastructure beyond the sensor itself.

3. 3

   Database Comparison

   The image is compared against two sources simultaneously. First, UMbRA: 55.5 million booking-verified booking records sourced from law enforcement agencies, with complete chain of custody back to the original booking event. Second, the venue’s operator-controlled X-lists: banned patrons, VIPs, executive protection principals, credential holders, or any other list the operator has defined.

   Technical Detail

   UMbRA and X-LST comparisons run concurrently. Each generates independent, compartmentalized results. Safience has no visibility into X-list contents during normal operations.

4. 4

   Non-Match Purge

   If no match is found against either UMbRA or the operator’s X-lists, the image is purged immediately. No biometric template is created. No record of the person’s presence is stored. The venue never receives any data about non-matches.

   Technical Detail

   Zero biometric retention for non-matches. No database of visitor faces is built. This is the architectural foundation of Safience's privacy compliance.

5. 5

   Match Verification (RAC)

   If a potential match is found, the result is routed to the Rapid Action Center (RAC). A trained Safience analyst reviews the match, confirms identity, and verifies the alert context (warrant status, ban reason, X-list category). No alert reaches your team until a human being has confirmed the match.

   Technical Detail

   RAC operates 24/7 during contracted event windows. Analysts are trained on facial comparison standards and alert triage protocols. False positive rate to venue staff is near zero because every match is human-verified before delivery.

6. 6

   Alert Delivery

   Once the RAC analyst confirms the match, an actionable alert is delivered to designated venue security personnel. The alert includes the matched photo, the person’s name (if available), and the reason for the alert (active warrant, venue ban, X-list category). Alerts are delivered to mobile devices, radio dispatch, or the venue’s security operations center.

   Technical Detail

   Alert routing is configurable per event, per gate, and per alert category. Different alert types can be routed to different personnel. X-list alerts and UMbRA alerts are compartmentalized; a VIP recognition alert goes to a different recipient than a warrant alert.