Build your own business case.
A transparent operational-value worksheet, not an ROI fantasy machine. Enter your own production constants and see a defensible payback range your CFO can audit. Every output is a function of the numbers you supply — nothing is fabricated.
Sample mode shows the worked-example math. Switch to Customer mode and the result only counts once you enter your own values (placeholders must be acknowledged).
Your inputs. Your math. Your number.
Operating constants
Current-state pain
Assumed improvements — you own these
Conservative placeholders. Values above 20% downtime reduction are uncommon — review carefully.
Recurring-value payback = Year-1 platform cost P ÷ monthly recurring value. Year-1 cash-impact view = P − one-time value (shown separately; one-time savings never fold into recurring payback). P — the full quoted Year-1 scope (software + Elpis hardware + implementation + services + support) — is supplied by Elpis sales, not this calculator.
Hardware BOM-elimination & protocol coverage.
Avoided hardware / BOM line items (optional — labels only; $0 until you enter source-backed figures)
| Avoided line item (example) | Unit avoided cost | Qty | One-time / recurring | Avoidable % | Cost source | Confirmed removed? |
|---|---|---|---|---|---|---|
| Separate industrial PC (per gateway site) | — customer — | — | one-time | — | quote / invoice / budget | — |
| Separate cellular modem (per remote site) | — customer — | — | one-time | — | quote / invoice / budget | — |
| Third-party oil-lab / sample contract | — customer — | — | recurring | % displaced | contract | — |
A row counts only with cost + quantity + avoidable % + source + a confirmed-removed flag. The calculator never prices Elpis hardware. Don't count the same avoided device twice. Recurring contracts are pro-rated by avoidable %. This SAMPLE is software-only → the bucket is $0.
Shipped-protocol checklist (only shipped protocols count as avoided in-house drivers)
| Protocol | Status | Count as avoided driver? |
|---|---|---|
| FOCAS2 | Shipped | ☑ counted |
| MTConnect | Shipped | ☐ |
| Brother HTTP (southbound source) | Shipped | ☑ counted |
| Modbus TCP | Shipped | ☑ counted |
| OPC UA Client | Shipped | ☐ |
| Siemens S7 | Shipped | ☐ |
| FANUC MT-LINKi (REST) | Roadmap | disabled — not counted |
| HTTP sink / TCP sink (northbound) | Roadmap | disabled — not counted |
SAMPLE counts 3 shipped protocols (FOCAS2, Brother HTTP, Modbus TCP). Roadmap items are disabled so MT-LINKi can't be counted before it ships.
Annual recurring value by assumption.
The two assumptions you're least sure of. Payback = your Year-1 platform cost ÷ (the cell ÷ 12).
| ↓ Downtime \ Reporting → | 25% | 50% | 75% |
|---|
What this does not compute.
- OEE improvement value — depends on your baseline + commercial structure. A discussion, not a calculation.
- Production-quality / scrap / yield — never included without your own quality data.
- Predictive-maintenance value (VAS / E-IDOS) — avoided failures / component life are site-specific; E-IDOS counts only via the BOM bucket (e.g. avoided oil-lab contract), never via predicted failure avoidance. (E-IDOS is standalone today; no EREMOS streaming value.)
- Tool-life, cyber-insurance, SCADA-avoidance, soft benefits — real, but uncalculated here.
Review these numbers with our team.
Download the full Excel model, or bring us your real operating constants and we'll scope a proof of value against them.