How do you know what a stop actually cost?

Downtime is priced at each asset's resolved dollar-per-hour rate, and scrap at each part's material cost from its bill of materials. Every dollar figure states its basis on the row: an app default, or a rate you set.

How fast do I see it?

Reason codes start flowing the moment the gateway is live and operators start coding stops at the machine. The dollar-ranked list appears as soon as stops are coded, usually on the first day.

What if the data is not there yet?

A stop with no reason code yet shows as an uncoded count and stays out of the dollar total until someone codes it. If a machine's rate is missing, the dollar figure uses an app default and says so on the row.

Downtime cost

Know what every stop cost you, by tomorrow morning.

See what is costing you money on the floor, the moment it happens, and prove the fix worked. Every number states its basis, and the Verified Savings Ledger shows whether a fix held, even when that number is zero.

Start a 30-day pilot → See the full product tour

Pilots from $4,500 · hardware included · 100% credited when you make the decision to implement

The receipt

Every loss, priced, with its basis shown.

This is a live screenshot from our own demo plant, not a mockup: downtime priced at each machine's resolved dollar rate, scrap priced at each part's material cost, biggest opportunity first.

opportunities · downtime and scrap priced in dollars · this week · demo data

Spall Opportunities board pricing downtime and scrap by machine in dollars for the week, top item Press #1 at $6,224, with each row naming its downtime driver such as Minor stop, Jam, or No mat

How it works

Gateway to dollar figure, no detours.

We mount the gateway

A palm-sized box on your DIN rail, wired to your PLC or, with no controller at all, straight into a current clamp or a dry contact. Live the same afternoon.

Reason codes come from the floor

An operator taps why a stop happened, at the machine, in seconds, on the kiosk right there. No spreadsheet, no end-of-shift guesswork.

Dollars, at your rates, by morning

Downtime priced at each machine's resolved dollar-per-hour rate, scrap at each part's material cost, ranked biggest loss first.

Not sure your machines fit? See the 18 protocols we speak natively, and what we do with the machines that have none →

The price, published

$200/machine/mo

first 10 machines

$160/machine/mo

from the 11th machine

$125/machine/mo

sensed-only machines, flat

$750/mo minimum

plant floor

Every deployment starts with a pilot: line pilot $4,500 (one gateway, up to 5 machines), plant pilot $8,500 (up to 2 gateways, 12 machines). 30 days, hardware included, fully credited when you continue. Full pricing detail on the product page →

Want the math behind the number?

The worked cost model a supervisor can redo on paper: lost throughput, idle labor, fixed overhead, and recovery cost.

Read the downtime cost guide → Run your own numbers on the ROI calculator →

Questions

Downtime cost, answered.

How do you know what a stop actually cost?: Downtime is priced at each asset's resolved dollar-per-hour rate, and scrap at each part's material cost from its bill of materials. Every dollar figure states its basis on the row: an app default, or a rate you set.
How fast do I see it?: Reason codes start flowing the moment the gateway is live and operators start coding stops at the machine. The dollar-ranked list appears as soon as stops are coded, usually on the first day.
What if the data is not there yet?: A stop with no reason code yet shows as an uncoded count and stays out of the dollar total until someone codes it. If a machine's rate is missing, the dollar figure uses an app default and says so on the row.

See your own numbers, not a demo.

Every deployment starts with a pilot. Line pilot $4,500, plant pilot $8,500, 30 days, hardware included, fully credited when you continue. Success criteria in writing: a loss board you believe, and at least one finding worth more than the pilot.