Asset inward and location allocation, dispatch a component out for external repair and receive it back, issue spares against the job — every movement on one stock and ledger trail. So a part is never lost off the books while it's away, and the whole out-and-back is traceable. Cloud or on-premise, for manufacturers of every kind.
A component out for repair follows the same disciplined flow as any stock movement — so a part is never quietly lost while it is away, and every step ties back to the machine in the asset register.
Asset inward records a new or returning asset or component coming into stock against the register, with its date, quantity and rate. Location allocation then assigns it to where it actually is — a plant, a department, a store bin — so the register answers not just "what do we own" but "where is it". When a spare, a bought-in component or a repaired part lands, it is booked in and placed, and the stock report reflects that location straight away.
When a component has to go to an outside repairer — a motor to be rewound, a gearbox to be rebuilt — you raise a dispatch entry against that vendor with the item, quantity and rate. The dispatch quantity leaves stock and the part shows as out for repair, so it is never quietly lost while it's away. The dispatch names which asset the component came off, so you always know that the spindle motor out at the rewinder belongs to CNC-VMC-04.
When the repaired component returns, you receive it back against the same dispatch reference, so the out-and-back is one closed loop rather than two loose entries. Spares consumed on the repair are issued against the job from the spare store, so the spare stock reduces and the cost lands on the asset's maintenance history alongside the dispatch and receipt. The repair and the spares it used are one record — you can read exactly what went into fixing a machine, not reconstruct it from two systems.
Inward, location allocation, dispatch for repair, receipt back and spare issue each post to the shared stock engine, so the stock report and ledger always show current on-hand quantity, current location and the full history of every asset and component. There is nothing to reconcile at month-end because nothing moved without a document. It's the same trail whether you run Fast Maintenance in the cloud or on-premise, and it shares stock with maintenance inventory and purchase when licensed.
Book new or returning assets and components into stock against the register, with date, quantity and rate on every inward.
Assign each asset or component to a plant, department or store bin, so the register tells you where everything physically sits.
Send a component to an external repairer with a dispatch entry — the dispatch quantity leaves stock, marked out for repair.
Receive the repaired component back against the same reference, closing the out-and-back loop so nothing is lost while away.
Issue spares against the repair job so stock reduces and the cost lands on the asset's maintenance history, on one record.
A stock report with live quantity and location, plus a ledger of every inward, dispatch, receipt and issue — always reconciled.
Repairs run on notebooks and memory lose parts, history and money. Here is what a tracked inward-to-receipt flow changes.
Asset inward records a new or returning asset or component coming into stock against the register, with its date, quantity and rate. Location allocation then assigns it to where it physically sits — a plant, department or store bin — so you always know not just what you own but where it is, and the stock report reflects that location.
When a part has to go to an outside repairer, you raise a dispatch entry against the party with the item, quantity and rate — the dispatch quantity leaves stock and the item shows as out for repair. When it returns you receive it back against the same reference, so the component is never lost off the books while it is away, and the whole out-and-back movement is one traceable trail.
Yes. Spares consumed during a repair are issued against the job from the spare store, so the spare stock reduces and the cost lands on the asset's maintenance history alongside the dispatch and receipt. The repair and the spares it used are one connected record, not two disconnected systems.
Yes. Inward, location allocation, dispatch for repair, receipt back and spare issue each post to the shared stock engine, so the stock report and ledger always show current on-hand quantity, location and the full history of every asset and component — no reconciling scattered registers at month-end.
No. Fast Maintenance runs standalone — asset inward, allocation, dispatch, receipt, spare issue and the stock ledger all work on their own. It shares stock with maintenance purchase and inventory when licensed, runs cloud or on-premise, and suits manufacturers of every kind across India and worldwide.
Live demo on your own repair flow — your inward, your dispatch to repairers, your spare issue and the stock ledger. No generic slideshow.
