01
It counts what it can't see.
Things with no tag, things with no site, tags fitted that never reported — ranked in the same queue as everything else, each stating what it stops the product from doing.
Falco · Asset and equipment tracking
Where it is. Who has it.
Every excavator, trailer, container and tool crate you own — where it is, whether the tag telling you is still alive, and which person signed it out. Including the ones it can't see. Those go on the list too.
10kinds of exception in one queue
3of them are gaps in its own coverage
7thresholds you set yourself
4states a site reports on its things
11classes of thing, from crates to containers
12modules on one platform
These are things Falco does — not results a customer measured.
01
The queue
One list, worst first, and it ends.
Off site, idle, tag dying, tag gone quiet, tag gone dark, never checked back in. Ten kinds of problem in one order. Each row tells you the threshold it crossed and what it probably means — not a code, a sentence.
And the action it offers is specific. When something is off site, it doesn't say "investigate" — it already knows where the thing is standing and offers to re-home it there.
ENTITY · OFF SITE — CAT 336 excavator173 mi from Lakeline Commons build — moved, mis-dropped or takenRe-home
TAG · LOST — Genie GTH-636 telehandlerno ping in 100h — past the 72h lost thresholdSnooze 24h
CUSTODY · OVERDUE — Survey kit crate SK-12M. Alvarez (site super) — 19d past dueCheck in
TAG · BATTERY — Multiquip DCA45 genset7% — will stop reportingSnooze 7d
ENTITY · IDLE — Chassis CHS-220has not moved in 223 days, sitting at Houston yardSnooze 30d
02
The part nobody else ships
It tells you what it can't see.
Three of the ten rows on that list aren't about equipment going wrong. They're about the system's own blind spots. A thing on the books with no tag fitted. A thing with no site assigned, so the off-site rule can't run on it. A tag that was installed and has never once reported.
Every tracking product shows you what it can see. The quiet danger is a screen that looks fine because the things it lost were never drawn. This one counts them, names them, and puts them in the same queue as everything else.
03
Custody
Somebody signed for it. It remembers who.
The loss that actually costs money is almost never theft. It's a survey crate that went out with a surveyor in August and nobody wrote it down. Falco holds a name, a role and a due-back date against the thing, counts the days past, and gives you one button to close it.
You choose how much grace to allow before an overdue item reaches the queue. Zero means the due date itself.
04
Sites
Two places account for the same machine.
A site isn't a pin. It's a named place with a type — yard, job site, depot, customer — an address, and its own radius. Each one reports four states on the things that belong to it: on site, visiting, away, and no fix.
So when the excavator leaves Lakeline, Lakeline says away and the Dallas customer site says visiting — both by name, at the same time. That's why the queue can offer to re-home it rather than just telling you something is wrong.
05
The thresholds
See what a setting will do before you save it.
Seven numbers decide everything on your list: how long silent before it counts, how long before silent becomes lost, two battery levels, how far is off site, how many days without moving is idle, how much grace past a due date.
Each one tells you how many things it's firing on right now, and whether the number is yours or the product's default. You're never guessing what turning a dial will cost you.
Why this instead of what you have
A green screen can just mean it stopped looking.
Tags are cheap and every vendor's demo is the same map with the same dots. The trouble starts on the Monday somebody needs the excavator, and the dots don't cover the part of the story that matters.
The tag died in June. The map didn't say so.
It just quietly stopped drawing that one. Nothing turned red, because nothing was there to turn red.
Half the yard was never tagged at all.
It's on the asset register and on nobody's screen. The dashboard is honest about the things it knows about, which is the problem.
The crate is exactly where it should be.
In a truck, with a surveyor, three weeks past when it was due back. The map is perfectly content.
One list that includes the holes in its own coverage, thresholds that show you what they'll do before you save them, and a name against every thing that left the yard.
06
Interruption
Noticing and waking you up are two decisions.
Falco notices everything and interrupts you for almost none of it. You pick the level — critical only, critical and warnings, or nothing — and it shows you how many things would reach you at each, before you choose.
Everything else waits on the queue. And anything you snooze goes into its own register: what was hidden, by whom, until when. A list you can hide rows from is only worth trusting if hiding is on the record too.
07
Five reasons it wins
Anyone can sell you tags. This is the part after.
02
Every threshold shows its blast radius.
"Fires on four now," printed beside the number before you change it — and a badge saying whether that number is yours or the default you never touched.
03
It knows who has it.
A name, a role, a due-back date and the days past it — on the thing itself. The crate sitting quietly in a surveyor's truck since August is a row on your list, not a discovery in January.
04
Two places account for the same machine.
Away from where it belongs and visiting where it stands — both stated, both by name. Which is why the fix it offers you is "re-home it to Dallas," not "something is wrong."
05
Hiding something is on the record.
Snooze a row for a day or a month and it goes into its own register — what's hidden, by whom, until when. When nothing is snoozed, it says so out loud.
08
What's in it
Six areas, one module.
The queue
6- Ten kinds of exception, worst first
- The threshold it crossed, stated in the row
- What it probably means, in a sentence
- A specific fix, not "investigate"
- Snooze by hours, days or a month
- Lower-priority notes kept below the line
The gaps
4- Things on the books with no tag fitted
- Things with no site, so the rule can't run
- Tags commissioned that never reported
- Missing data styled as missing, never as zero
Custody
4- Named holder and their role
- Due-back date, and days past it
- Grace period you set — zero means the date
- One button to check it back in
Sites
5- Typed: yard, job site, depot, customer
- Real address, and its own radius
- On site, visiting, away, no fix
- Away and visiting entities named
- Retired, not deleted — history survives
The estate
6- Eleven classes, crates to containers
- Sort by furthest from site, or lowest battery
- Stacked states — off site and overdue at once
- "Was on site" when a tag dies in place
- Days since it last moved
- CSV export of the whole roster
Rules and reach
6- Seven thresholds, each naming its row
- How many things each is firing on now
- Badged yours, or the product's default
- Three levels of interruption, counted
- Snooze register — what's hidden, by whom
- Estate digest, sent whether or not anything's wrong
Thirty-one of them. There are more, but these are the ones that decide whether you can trust the list.
Next step
See it on your estate.
Ninety minutes on what you own: your sites and their real radii, the classes of thing you track, who signs equipment out, and the seven thresholds you'd set first. You keep the configuration.
Falco is the ELYON entity tracking module. Every capability here is live in the product today. No figure on this page is a customer outcome.