For vehicle-terminal operators and port authorities operating common-user precincts. Reconciled against the manifest, with nothing fitted to the units.
Connect the shipping record to the vehicle, its location and its time on the berth.
Location and time, connected to your records.
See it for your siteFollow each unit from the ramp to its row and reconcile the count against the manifest as discharge proceeds. At an Australian port, Indrus tracked a full vehicle-carrier discharge on the port's existing cameras, and its count matched the ship's manifest to 99.7%.
See how long each vehicle has been on the berth, which units are approaching their free days, and which consignees are consistently late to collect. Timed per-unit evidence supports the overstay conversation.
See which rows are filling and which are clearing, with berth utilisation over the week and month. Movement records show where each unit went and when. Warnings identify units nearing free days and rows nearing capacity in time to act.
The value of measuring the berth comes from overstay fees that currently go uncollected because the evidence is not there, from vessel delays and diversions avoided when the precinct is not holding units that should have left, and from throughput recovered when rows clear faster. The scale of each depends on annual throughput, the free-day rule and the collection behaviour of consignees. We will build it with your numbers on the demo.
Your bookings, work orders and manifests describe the plan. Indrus runs against it from the live state of the ground, and is typically live within a fortnight from camera access.
Indrus is for the party that operates the vehicle terminal and owns the land-side cameras: the terminal lessee, or a port authority operating a common-user precinct. Stevedores working the vessel are welcome to the conversation and are not usually the buyer.
Fixed cameras covering the working areas. Indrus runs on premises on a server we supply, or hosted with nothing installed on the operator’s network edge. No tags, beacons or readers are fitted to the units.
Names come from the operator’s records, including the manifest. Positions, times and events go out through reports and the API, so terminal systems work from what is actually on the berth.
Footage is processed and discarded, whether Indrus runs on the operator’s site or hosted. No video is stored. What comes out is the record: positions, times and events.
01Which doors are working, and what should move next?
Explore application
02Where is the freight, and how hard is your equipment working?
Explore applicationSite photographs illustrate application types.
Bring a plan of the precinct. We will discuss what the record would show for your terminal.
