A working tool for building the value case behind scaling robotics and novel technology into live operations — inspection, maintenance and surveillance robotics, and the OT infrastructure beneath them. It compares your current way of working (As-Is) against one or more proposed solutions, across the whole system: technology, process, people and performance. The return is shown in both money and in hours bought back.
Enter your details and the key assumptions (currency, operator cost, time horizon).
Give the problem you are trying to scale a name and a short description.
Fill the As-Is baseline, then add Solution A, B, C. Expand each layer and enter cost and man-hours.
Read the value summary, then capture the use case and export it.
So the value case can be attributed and followed up. Nothing is sent anywhere from this page — it stays in your browser until you export it.
These drive the conversion between time and money. They are deliberately visible and editable — the model should never be a black box. Defaults below are illustrative placeholders; set your own.
Each calculation is one use case. Naming it lets it roll up into a report — and, in a later version, into a shared library of the problems engineers are trying to solve.
As-Is compared against a chosen solution. Updates live as you type.
Start with the As-Is — the cost of the work as it is done today (usually recurring man-hours, little or no capital). Then add each proposed solution and enter what it takes to stand it up and run it, layer by layer. Use the basis control on each line to mark a cost as a one-off (deployment) or annual (recurring).
Every state, alongside each other. Section subtotals roll up to a solution total; the ROI rows compare each solution against the As-Is baseline.
Capturing the use case adds a dated snapshot to the list below (the seed of the future database) and lets you export it. Export gives you a report-ready JSON and a flat CSV.
No use cases captured yet in this session.