Skip to main content
When a serialised component comes off a vehicle, it does not simply vanish into a store. It goes to a supplier, gets repaired, and comes back. This page tracks that journey. The page is a single grid of components in the loop, with a repair drawer for each. It deliberately excludes mounted components — it shows what is out of service and being worked on. It has no component record of its own: it drives the status and location of the component on the Components page, so repair state is visible wherever the component appears.

​
The loop

Every transition writes an entry in the component’s history, recording who moved it, when, and any comment.

​
Where the manual loop begins and ends

MOUNTED and the initial DISMOUNTED are not manual transitions. They are set by the daily vehicle_configurations import, which is what knows whether a component is fitted. So the loop is entered when an import dismounts a component, and it ends at IN_STORE, which has no manual successor. The component returns to service only when a later import mounts it again. SCRAPPED is terminal.
The import rejects the entire file if it tries to mount or dismount a component that is IN_TRANSIT, IN_TRANSIT_BACK, UNDER_REPAIR or SCRAPPED — a part in those states cannot physically be on a vehicle. If a configuration file fails on this, the fix is to complete or correct the repair-loop state first.

​
Location

current_location answers “where is this thing right now”, and it is set from two directions:
  • Send to supplier and receive in stock set it to whatever location you supply.
  • Mount and dismount imports set it to the vehicle number when fitted and the depot when dismounted.
Receive at supplier, send back and scrap leave it unchanged, so a component UNDER_REPAIR continues to show the supplier recorded when it was sent.
Location is optional on the two actions that set it, and omitting it clears the field rather than preserving the previous value. If you want to keep a location, re-enter it.

Field reference

component_status_update, component_comment and component_attachment. The status itself lives on assets_component.

​
Comments and documents

Components carry a timeline of status changes, comments and uploaded documents, in the same shape as warranty claims. Status entries are immutable; comments and attachments can be edited or removed by their author.

​
Who can do what