Opservor
What your systems
cannot tell you
Operational intelligence for logistics, warehousing and fleet.
TeraSpheres · Edmonton, Alberta
The gap
A question your systems cannot answer
“Which of my depots is going to struggle next Thursday, and why?”
Your warehouse system knows the docks are filling up. Your fleet system knows two vehicles are booked in for service. Your stock system knows an item is running down.
All three are correct. None of them talk to each other — so the answer only arrives on Thursday, when somebody spends the afternoon firefighting and calls it bad luck.
The problem
What your stock screen shows you today
BAK-00484
- On hand
- 28 units
- Reorder level
- 26 units
- Status
- In stock
28 is above 26.
So it says you are fine.
That is the whole of the logic — one number compared with another. It does not know how fast the item is leaving. It does not know how long your supplier takes. It has never once divided one by the other.
It is not fine.
Seven units a day are leaving. 28 ÷ 7 = four days of stock. Your supplier takes ten.
Ordering this morning still leaves six days with an empty shelf — and the screen above
will show green on every one of them.
The same item, the same minute
What Guardian says instead
critical
inventory
Supplier 9 — BAK-00484, 4 days of cover
Bakery item 484 has 4 days of cover. A replacement order takes about 10 days, so ordering today still leaves 6 days with nothing on the shelf.
Recommended: Raise an order to Supplier 9 for 184 units of BAK-00484.
| Item | Order | Available | Per day | Days left |
|---|---|---|---|---|
| BAK-00484 | 184 | 28 | 7 | 4 |
Not an alert. An alert says a threshold was crossed — your stock screen already does that, and it is why 28 against 26 looks healthy. This says what is going to happen, when, and what to do about it.
Trust
Every finding shows its working
An operations manager will not act on “trust me, Thursday will fall over” — and should not. So the arithmetic is on the page, not behind a support ticket.
- Count what actually left630 units shipped over the last 90 days. Not a forecast — that happened.
- Turn it into a rate
630 ÷ 90 = 7units a day. - Work out what is really yours46 on hand, 18 already promised to orders, so 28 can actually be sold.
- Divide
28 ÷ 7 = 4days of cover. - Compare against the supplierFour is less than ten. You are not approaching a problem — you are six days late.
Scale
Your catalogue, seen properly
Across 300 trading items in a food and beverage operation, this is what days of cover actually looks like. Almost all of it is fine — and that is the point.
Eighteen items out of three hundred need somebody’s attention this week — and they are not the ones your reorder report would name. Software that flags three hundred items has told you nothing. Software that flags eighteen has done a day’s work for you.
The one nobody else can do
Two systems that never speak
critical
warehouse
fleet
Calgary Depot loses 2 of 6 vehicles on Thursday
6 vehicles have been running from Calgary Depot. 2 of them are booked in for service on Thursday 06 Aug — 33% of the site’s vehicles gone on one day. Dock use has risen from 88% to 94% over the same period.
Recommended: Move 1 of the Thursday bookings to a quieter day, or bring vehicles across from another site.
Every fact in that sentence is ordinary. Your warehouse system knows the docks. Your fleet system knows the bookings. Nothing joins them — so nobody finds out until Thursday.
Read this one carefully
What it will not do
Most software in this market is sold on what it might eventually do. This is what Opservor does not do today, stated before you ask.
- It does not predict the future.It divides what has happened by how fast it is happening. That is arithmetic, not prophecy.
- It does not know your supplier lead times.Nothing records them yet, so it assumes ten days — and says so on every finding that relies on it.
- It does not replace your warehouse or fleet system.It reads them. Keep what you have; this joins it up.
- It has no customers yet.You would be the first. That is a real risk and it is priced into the conversation.
A supplier who tells you the limits before you sign is a supplier who will tell you when something breaks.
Built and running
What is in the product today
8
operational modules, all live
31
database tables, each separated by company
3
Guardian checks in production
4
roles with per-module permissions
Separated at the databaseNot filtered in the application. A bug in the code cannot reach another company’s data.
Fleet, warehouse, stock, finance, workforce, safetyEach module live, with reports over any date range.
Tested against known answersThe demo data carries a fixed number of planted faults, so a run either finds exactly those or the product is wrong.
Next step
What a trial looks like
- A read-only copy of three months of historyStock movements, vehicle trips, maintenance bookings, shift records. Whatever you already export to a spreadsheet is enough.
- One afternoonLoading it and running the checks against your real operation, not a demo.
- You tell us which findings are wrongEvery finding shows its working, so you can check it against what you already know. Wrong findings are more useful to us than right ones.
No integration work, no change to how your team works, nothing switched off.
Every system you own reports what happened.
None of them tell you what is about to.
TeraSpheres · Opservor · Edmonton, Alberta