REAV

Use case

Parts are the ceiling
on repair yield.

The limit on how many devices an operation repairs is rarely bench capacity. It is whether the right part is on the shelf, at a cost that still leaves a margin - which makes parts handling a production question rather than a purchasing one.

The job

Why parts break standard stock management.

A repair operation holds several kinds of stock in the same building, and one of them does not behave like stock at all.

Compatibility is not a quantity

The question is not how many of this reference are left but which part fits this specific unit, across model variants, revisions and production years where the same visual part is not always the same part.

Harvested parts have no purchase price

A part recovered from a dismantled device enters stock as the by-product of a production decision, with a provenance worth keeping. A forward-only bill of materials has no place for it.

Reservation is where counting fails

A part committed to a waiting device is still physically on the shelf. Counting it as available is how parts get ordered that were already reserved.

What the ERP does

Dismantling feeds repair, and both are costed.

This is the dismantling and stock scope already detailed on the ERP page, read from the parts angle.

  1. 01

    Reverse BOM per model

    Each model knows the list of parts it can return to the workshop, so a dismantling decision can be taken against what the repair queue is actually waiting on.

  2. 02

    Harvested parts revalued into sellable stock

    Extracted parts are logged and reinjected immediately, rather than accumulating in a drawer that no system knows about.

  3. 03

    Assisted parts ordering

    One-click purchase orders for every out-of-stock part, raised from the repair order that needs them.

  4. 04

    Cost and lead time per device

    Parts, time spent and real cost measured on the device, which is what tells you whether a repair category is worth running at all.

  5. 05

    Serial-level, multi-warehouse stock

    Locations, transfers and inventories, so the shelf and the system agree.

What this is not

The boundaries, stated plainly.

  • REAV does not supply your parts through the ERP. Centralised purchasing for tools and spare parts exists, but it is part of the REAV License, not a function of the software.
  • A reverse BOM is only as good as the model data behind it. Building it for your device mix is deployment work, not a switch.
  • The system does not decide what to dismantle. It gives the decision a cost and a demand signal; the call stays yours.

FAQ

Common questions.

Yes, and they need to, because a repair order does not care where the part came from. What differs is valuation and provenance, and both are kept on the part.
The reverse BOM tells you what a model can return; the repair queue tells you what is waited on; the cost per device tells you what the repair would consume. The ERP supplies those three; the decision is a human one.
It raises one-click purchase orders for out-of-stock parts from the repair order. Who you buy from stays your choice.
They follow the dedicated end-of-life flow, traced and documented, with weight and materials feeding EPR declarations.

← Back to the REAV ERP

See a dismantling decision made on data.

Tell us about your device mix and your repair backlog, and we will show how a reverse BOM, a repair queue and a cost per device turn that decision into a calculation.