Component management

Track every major component on every machine — engines, transmissions, final drives, undercarriages, rotables — with its own life, service plan and cost history. Change one out in the field and Samurai resets the right life automatically.

Why this matters

A 240-tonne haul truck isn’t just one asset — it’s a stack of components with their own rebuild cycles, swap histories and costs. Generic CMMS platforms treat the machine as a single thing. The moment you swap an engine, the life data goes wrong, the forecast goes wrong and the cost picture goes wrong.

How Samurai handles it

Component life tracking at the asset or rotable level. Automatic life reset on changeout — no scripts, no side spreadsheets. Nested service logic so component services fire alongside (or independent of) the parent machine’s services. Rotable management so a refurbished component carries its real history into the next machine. Task life and risk visibility to support repair-vs-replace decisions.

[Placeholder: screenshots — component tree on an asset, changeout flow with automatic life reset, rotable pool view, upcoming rebuild forecast.]

What changes for you

Components get replaced before they fail, not after. The rebuild forecast reflects what’s actually happening on the fleet. Rotables stop getting lost between machines. Repair-vs-replace calls are backed by real cost and life data, not gut feel.

Want to see this working on your fleet? Book a demo.