Components
A component is a physical part that belongs to an asset, or is nested under another component. Components support an unlimited hierarchy — a system can contain a subsystem, which contains a module, which contains a part.
The key idea is lineage: as a component moves between parents over time, Modutrack keeps an immutable record of every move, so you always know where a part has been and why.
Attaching a component
- Open an asset, then choose Add Component.
- Give the component a name and any details you have.
- Save — the component is now installed on that asset.
Moving and swapping
When you swap a part out of one asset and into another, record a move. Each move is saved as a permanent event, building the component's lineage. This lets you answer questions like "which assets has this part been installed in, and for how long?"
Component status
Every component has a status:
| Status | Meaning |
|---|---|
| Active | Currently installed and in use within an assembly. |
| Spare | In your inventory but not currently installed. |
| Retired | Permanently removed from service, but still kept for its pedigree. |
A component with no asset is unassigned — it lives in your inventory without belonging to any specific asset yet.
History is never lost
Removing or retiring a component never deletes it. The record is hidden from active views but preserved, so the pedigree of every asset stays complete.
Next: log services and set up maintenance.