The facts.
Without the shorthand.
What it does, what it needs, and where it has run.
The company and the sites
Indrus is a company based in Perth, Western Australia.
Indrus runs yard and dock orchestration for outdoor logistics sites: arrivals, door allocation and yard moves follow the live state of the site, read from its existing cameras.
Indrus is used at distribution and 3PL yards, freight and laydown depots, and vehicle terminals at ports.
What it does
Indrus works with nothing on the assets: no tags, beacons or readers.
Indrus establishes identity by following each unit from the moment it is first seen, so it works for units with no markings.
Where an operator wants a name on a unit, Indrus takes it from the operator's own records.
Indrus provides a live plan of the site, door allocation, ranked yard moves, time on site per unit, door and bay timelines, alerts, reports and an API.
What it needs and where it fits
Indrus runs from fixed cameras that can see the working areas, either on premises on a server Indrus supplies or hosted with nothing installed on the operator's network edge.
Footage is processed and discarded. No video is stored.
Indrus can run the yard in place of a yard management system, or against the booking and appointment systems a site already has. It is not a warehouse management system or a safety system.
Indrus does not serve high-bay warehousing.
Where it has run
Indrus has been deployed live at truck and trailer yards in the United States, on the yards' existing cameras.
Indrus has been validated at an Australian port, where it tracked a full vehicle-carrier discharge on the port's existing cameras and its count matched the ship's manifest to 99.7%.
Indrus is typically live within a fortnight of camera access.
Working areas
Processed and discarded
Positions, times, events
No video is stored. What comes out is positions, times and events.
How Indrus compares with other approaches
Most ways of knowing where things are start by putting something on them. Indrus doesn't.
| What you use today | What it tells you | What you have to put on the site |
|---|---|---|
| Walking the site and the radio | Where one thing is, right now, once | A person's time, every time |
| Telematics | Where the vehicle is on the road. Once a unit is dropped its beacon reports rarely, and a pallet or a dolly has nothing at all | A unit on every asset you want to see |
| Tags, beacons and readers | What passed a reader, and when. Whether the bay was used looks the same either way | A tag on every asset, readers on every lane, batteries and losses for good |
| Management systems | The plan: bookings, work orders, what was meant to happen. Fed by hand, thinnest when the site is busiest | Someone at a screen keeping it true |
| Cameras on the movers | A log of every move a mover made. The bay is unwatched between moves | A camera on every mover, and a mover fleet to begin with |
| Indrus | Every unit and every space timed all day, whether or not anyone touched it. Used or occupied. Queued or checked in. Allocated or used | Nothing new on the assets |
Identity is established by following each unit from the moment it's first seen, so it holds for units with no markings at all. Where you want a name on a unit, it comes from your own records.
See it on a plan of your site.
Bring a plan of one site if you have one handy. We’ll show you what it looks like measured.