Worked decision · Modeled economics
AMR lifecycle economics: a reproducible fictional stress test
Compare six fictional AMR fleet scenarios using the same lifecycle model. Inspect service, recovery, supply and sensing assumptions, costs and explicit limits.
By Mohammed Cherifi · Hyperion Consulting
Scale gate · Buyer decision
Which service, recovery, supply and sensing assumptions could invalidate the fleet's repeatability and value thesis?
For: Operations sponsor, product leader and finance partner considering fleet expansion
Six lenses for the same decision
Customer, operator and product value
How much useful pallet movement remains after degradation, and what human work is still unmeasured?
Economics and business viability
How do upfront investment, annual operating cost, lifecycle TCO, net value and payback change under the declared stress?
AI, data, evaluation and HMI
Which sensing, recovery-policy and operator-intervention assumptions need application-specific evidence?
Complete system architecture
Which fleet configuration and operating envelope make a comparison meaningful?
Safety, cybersecurity, compliance and governance
Which stop and specialist acceptance decisions remain outside this economic illustration?
Deployment, operations, service and ecosystem
Can commissioning, spares, recovery staffing and support capacity repeat across sites?
A controlled hypothetical comparison
A clone of the AMR preset with all failure switches disabled, stage set to Scale, and descriptive scenario identity changed. This is an unperturbed hypothetical comparator, not observed operations or the original preset's enabled-failure mix.
The baseline and five stress variants use the same fleet, horizon, prices and operating assumptions. Selected failure switches and their declared severity change; descriptive scenario identity changes so each result is distinguishable. Severity is not an observed probability.
Recalculate the lifecycle consequence
| Scenario | Upfront investment | Annual operating cost | Lifecycle TCO | Lifecycle net value | Payback months |
|---|---|---|---|---|---|
| Fictional baseline: all failure switches off | €1,400,640 | €421,880 | €3,088,160 | €12,470,990 | 4.8 |
| Service overload, severity 75% | €1,400,640 | €489,920 | €3,360,320 | €11,728,814 | 5.1 |
| Recovery failure, severity 75% | €1,400,640 | €462,704 | €3,251,456 | €11,132,654 | 5.4 |
| Supplier delay, severity 75% | €1,400,640 | €421,880 | €3,088,160 | €12,470,990 | 4.8 |
| Sensor degradation, severity 75% | €1,400,640 | €454,539 | €3,218,797 | €11,635,330 | 5.2 |
| Service overload and recovery failure, each 75% | €1,400,640 | €530,744 | €3,523,616 | €10,390,478 | 5.7 |
Interpretation and limits
- Severity is a scenario input to versioned consequence formulas, not an empirical probability or measured effect size.
- Only the declared failure settings (enabled state and selected severity) differ between comparable runs, apart from descriptive scenario identity. Inputs, results and hashes are included for independent recalculation.
- Productive value is an assumed customer benefit; contract revenue is shown separately and is not added to that benefit. Lifecycle net value is not supplier profit, NPV or a forecast.
- The existing engine does not discount cash flows or model tax, financing, utilization distributions or correlated real-world failure probabilities.
- The illustrative exposure counts in Product System context are held constant; the failure engine does not predict accepted pallet transfers or operator staffing. Do not read the cost-per-declared-success diagnostic as stress-adjusted throughput economics.
- A delayed supplier may leave modeled release weeks unchanged when the declared roadmap already contains slack. Read the changed lead-time field rather than claiming every stress must move every output.
- Before investment, replace assumptions with scoped site evidence, capture omitted costs and compare alternatives. A favorable modeled signal still recommends experiment_only.
Inspect and reuse the preparation snapshot
These files were prepared on 6 September 2026 before publication, with no individual human editorial approval recorded. Their status fields retain that preparation state; they do not grant permission or establish when this page became available. AI tools supported preparation. No customer results or release approval are established.
The file manifest binds the download bytes to their local sources. The downloadable JSON includes the inputs, limitations and provenance needed to inspect the result.
Payload SHA-256: dad1910669fa3526b0190aa028def2daf8fc479edf94bad1d1428b7788d6a8cd
Apply the questions to your product
Use the Physical AI Product System to connect claims, requirements, configuration, evidence and an accountable human decision.
Product Leadership Mission: Lead one product, platform, product family or launch to a named evidence-backed milestone.
Discuss your product decision