Correct Way to Model Repairs and Component Traceability in Tryton

In relation to: Use disassembly production for repair a product
We are implementing a repair workflow by reusing theproduction model.
However, we are concerned about a potential issue regarding traceability of components before and after a repair.

Scenario:

  1. A production is created for product X, using components A, B, and C.

  2. Later, the product X enters a repair process.

  3. During this repair, the defective component C is replaced by a new component D.

When checking Upward and Downward Traceability, after performing a repair production, the traceability chain does not clearly show which components were originally mounted versus which ones were replaced. After the repair, Tryton only shows the components resulting from the repair production, so there is a loss of visibility of the historical composition.

Is there a recommended way in Tryton to model repairs so that every component change is traceable and the system keeps a correct historical record?

Is it correct and recommended to use the production model for handling repairs, or is there a better approach?

I do not think so because production is about creating a new product which is not what a repair is.

I think it will be better that you explain your requirements so we can provide better advice for your needs.

The main requirements for our repair workflow are:

  1. Track repair time. We need to record the start, end, and duration of each repair operation. (We use production works)

  2. Material usage and stock control. We need to register the materials used in the repair and ensure that there is enough stock available.

  3. Automatic inspection creation. For every repair, a quality inspection should be created.

Our goal is to have a workflow that modifies the composition of the existing product, while keeping full traceability of the components that were replaced or added during the repair.

I did not fully test the workflow but at first tought it seems is doable as far as you:

  • For each repair production the repaired product is used as input and as output for the production (and the use the same lots).
  • Create new inputs for products that have been added to the production
  • Create new outputs for the old products that had been replaced (or removed) for the main product

From here you should probably adjust the cost computation in order to match your needs. Probably the cost of the repair is diferent from the cost of produce the material but can not know more as you did not specify anything about costs. You should consider if the output product cost should be updated for repairs.

As there will be some diferences for repairs and normal productions you probably need to have extend the type field to include a new repair production.

About traceability:

The traceability shows for each production which components are used and which are not used. So you must set the proper records in order to show the proper data there. You did not mention how you created the productions but it should work by using the inputs/outputs as I proposed.

P.S: Note that I did not test not fully analyze all the cases here so make sure to test your cases before going further.

1 Like

Thanks Sergi,
Your explanation matches very well with the approach we are already following.

We weren’t contemplating the structure of inputs and outputs the right way.
With your aproach, I think that traceability is correctly showing which components were used and which ones were removed, as you described.

Thanks again for your help.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.