How it works
How your factory learns to talk.
A sensor on every machine, a real cost on every unit, and the few things that need a decision brought to you. This page is the mechanism: what the box on the machine actually is, what it measures and what it works out, what happens when the power goes, and why nobody types your customer list twice.
A small box on the outside of every machine records what ran: no logbooks, nothing typed.
Knows your true cost and profit per unit while the day is still running, so you price from the number instead of from feel, in a dashboard your whole team can open.
Understands it all, and tells you what needs you, in plain language.
From checking to being told. You say once what you care about: a material below 100 kg, say. After that you stop opening the app: the moment it is crossed, Jarvis writes to you and to the people who have to act on it.
The floor records itself.
A sensor goes on each machine in minutes: any machine, nothing opened, nothing drilled, nothing rewired, and the machine does not have to stop while it is fitted. It records what ran. Bills and invoices come in by photo. Nobody types a production figure. The machines report for themselves, so nobody has to report on anybody.
- Sensor on each machine: minutes to fit.
- Bills & invoices captured from a photo.
- The reading survives a network drop: the sensor holds it until the server confirms it has it.
What actually goes on the machine.
A small box on the outside of the machine. It sits on the frame or the guard, where a fitter can reach it and nobody walks into it. The panel stays shut.
It runs off an ordinary power point beside the machine, so there is no battery for anyone to remember to change. It needs WiFi that reaches the machine itself, and that is the part worth checking before you buy.
It mounts on the outside of the machine. Nothing is opened, nothing is drilled into the machine, nothing is rewired, and no part of it goes anywhere near your control panel.
An ordinary power point at the machine. No battery to change.
WiFi that reaches the machine, not just the office.
Minutes per machine, with the machine still running.
About the internet, honestly. Your office internet is enough for you to watch the floor. The sensors need WiFi that reaches the machines and a power point at each one. We walk the floor before we quote and put in whatever coverage your machines need.
Measured, or worked out, and we tell you which.
Not every machine will give you a pulse for each piece, and any vendor who says otherwise is about to install a sensor that guesses. There are two sensors. Which one your machine gets is decided when we walk your floor, and you are told.
One pulse for every piece, cycle, pick or metre. The sensor reads every one. The figure on your screen comes straight from the machine, pulse by pulse.
Then you type the sum yourself, the arithmetic that turns running time into output on that machine, and Blitz runs it every time the machine turns. Every row produced that way is labelled an estimate, on the screen and in the report.
You are never left guessing which kind of number you are looking at. A measured row and an estimated row do not sit in the same column pretending to be the same thing, and the labelling does not stop at the dashboard: it is on the report, and it is there when Jarvis reads the figure back to you.
What happens when the power or the internet goes.
It will happen. The question a monitoring system is really judged on is what its numbers look like afterwards, and most of them quietly lose the shift, or record it twice.
Nothing here has to be reconstructed the next morning out of somebody's memory.
- The sensor holds its readings. It lets go of a reading only when the server has confirmed it has it. Until then the sensor keeps it.
- A restart cannot be read as a repeat. When the power or the link comes back, what was already recorded is not recorded a second time.
- A stop keeps the time it happened. A machine that stopped while the line was down still shows as stopped at the time it stopped, not at the moment the connection came back.
Correct yesterday, and the cost follows.
A supervisor tells you machine 07 actually ran a different item between two and six. You say so: you restamp that window, and the output, the material and the cost for it are worked out again against the right item.
What does not happen is an edit. The reading the machine sent stays exactly as it arrived. The correction is a new record written against it, with the person who made it and the time they made it.
Nobody can quietly rewrite yesterday.
Kept. Never overwritten.
Restamped by the shift in-charge at 09:12 the next morning. Cost worked out again against item 4127.
It knows everything.
Blitz turns the signal into live production, energy, material and labour, and the true cost and profit of every product and customer. Price a job while the customer is still on the phone, see which products and which customers are the ones paying you, and rank what to run next by profit per machine-hour. One dashboard, from anywhere.
And when something it needs is missing, it says so. A material with no approved price gives you a blank that names what is missing, and the total goes blank with it. A zero would have said the material was free to buy.
How true cost is builtYour customers and products arrive already spelled your way.
Blitz reads them straight out of Tally: your customers, your stock items, your sales vouchers and your assembled products. On day one you are looking at profit by customer and by product under the names your office already uses, with nobody typing a master list a second time.
That also keeps the two in step. Keyed in twice, a product list and a ledger stop agreeing by the end of the first month, and every figure built on top of them inherits the argument.
Your book stays your book: Blitz reads Tally and never writes to it. Blitz with Tally
The ledger is the one place a figure is allowed to change, and it is your accountant who changes it.
- Customers: the names and the ledgers you already bill against.
- Stock items: your product list, your codes, your units.
- Sales vouchers: what actually went out, and at what price.
- Assembled products: the ones built out of other items you make.
Nothing. Not one voucher, not one master, not ever.
It understands, and tells you.
You say once what you care about: a machine stopped longer than your own line, material about to run short at the rate you are consuming it, money overdue past your terms. After that Jarvis watches it and writes to the people who need to know: the what, the why and the action to take. Nobody asked it anything.
And when you do want to ask: ask it what machine 12 did last night, or what you are still owed. Same question box, by text or by voice.
Explore JarvisMachine 07 stopped 22 min ago. Order #4180 is due Tuesday. Have the fitter look at 07 first.
Time to value
Live on your floor in a day. We set it up.
to fit sensors and see live output.
for a working pilot: real production and cost.
to configure the whole floor, then it just runs.
Attendance comes from whatever you already use. The biometric box on the wall, the cloud service you subscribe to, or the spreadsheet your office keeps: we read it from there. What it read is shown to you and approved by you before it counts towards anything, and an approval can be undone.
No rip-and-replace
It works alongside your accounting software.
Not another heavy ERP project. Blitz is the machine-grounded layer underneath: it reads your masters and your sales out of the books you already keep, and works out the cost your books were never able to. Your accounting software keeps doing its job, untouched.
- Keep your accounting software. Blitz reads from it and leaves it alone.
- Hosted & managed: nothing to install, see your floor from anywhere.
- No downtime, no big cheque upfront, no long contract.