Handle the alert. The closure leaves you the data.
It closes the gap between "something happened" and "this is what happened, this is what we did, and here is the proof".
Detection solves half the problem. The other half is operational.
Who finds out and how quickly, whether anyone went to look, what they found, whether it was recorded in a way that is useful later. Without that loop, detection is noise. And when a theft happens and someone asks whether there was jamming, without a record that question has no answer.
Tank Mission Control
Receive, dispatch, close. And keep a record.
The loop
- 01
Detect
The sensors identify the jamming.
- 02
Alert
The event appears on screen, with an audible alert and its location on the map.
- 03
Manage
The operator dispatches a guard; the system measures how long it took.
- 04
Record
On closure, it is documented whether the guard responded and what they observed.
- 05
Review
A supervisor or analyst checks the classification and corrects it.
- 06
Validate
The head of security signs off, with a record of who and when.
- 07
Deliver
Validated cases become formal case files or reports.
Every step records who did it and when. That chain is what turns an internal log into evidence you can present to third parties. Review, validate and deliver are currently being validated with customers.
Real-time operations
- Site map with the zone under attack highlighted
- Audible alert
- Dispatch with automatic measurement of reaction time
- Guided closure that adapts to what happened
- Operating hours and scheduled muting for maintenance
Classification
- Four business outcomes: drill, not handled, handled with no finding, handled with a finding
- The operator records precisely and management reads simple indicators
Dashboard
- Handling rate, dispatch time and guard arrival time
- Comparison with the previous period
- Heat map by time slot and day of the week
- Ranking of critical zones and performance of operators and guards
- History with search, filters and export
Information quality
- Merging of duplicate names, correcting the history
- Duplicate prevention while typing
- Detection of incomplete records
Tank Intelligence · Understand
The half that reviews, validates and gives management visibility.
Tank Intelligence lives inside Mission Control. It turns what was documented into evidence and intelligence: what happened, where it concentrates and how it compares.
Review, validation and case files: in validation with customers
- 01An inbox to process many cases in a few minutes
- 02Visible statuses with an owner and a date
- 03Traceable corrections: editing a validated case requires revalidation
- 04Case files with a sequential number and a chain of evidence
- 05Comparison against the industry or the geographic area, always anonymous
Use scenarios
A single site with its own monitoring center
A mall with its monitoring room: the supervisor configures, the operator handles, the manager validates.
A branch network
A chain with dozens of locations from a single monitoring center. Each location is a zone.
Frequently asked questions
How do I prove this to my management or to the insurer?
With the case file: sequential number, verification code and the chain of who closed it, who reviewed it and who validated it.
How do I know my guards respond?
Times are measured, not estimated, and there is a performance ranking by operator and by guard.
My operator gets overwhelmed by so many alerts.
Operating hours, scheduled muting and calibration for each site. It is designed so the operator doesn't lose trust because of noise.
We're small, this is too much for us.
The head of security and the supervisor can be the same person, with no extra configuration.