Rebuilds

Overview

In addition to in-process rework (Global Rework / Rework by Manufacturing Operation), Tascus can handle a full rebuild of an item.

A rebuild creates a new, separate Product Report against the same top-level serial number, tagged with a _RB suffix (e.g. SN12345_RB) to signify it is a rebuild. It runs its own manufacturing routing, independent of the original build's routing and results.

When to use a rebuild vs. rework:

Use rework for correcting an issue within the existing build process. Use rebuild when the item needs to go through manufacturing again from a defined point, as a distinct traceable event.

Configuration

1. Create the Manufacturing Routing

In Sequence Editor, create a Manufacturing Routing for the rebuild containing all required operations. This is the list of manufacturing operations and their sequence — it sits one level below the part number.

2. Link it via a Part Routing

A Part Routing determines which Manufacturing Routing runs for a given top-level part number — the same mechanism used to handle different routings for different revisions of a part. From the Parts List page, create a Part Routing for the rebuild item so that when a works order is loaded against it, the rebuild Manufacturing Routing is used instead of the standard one.

Execution

3. Create a Works Order for the Rebuild

Create a works order and set the serial number to the original item's serial number with _RB appended (e.g. SN12345_RB). Select the _RB Part Routing.

Caution — auto-generated serial numbers: the serial number field accepts free text, including _RB, at most sites. If the site uses Tascus to auto-generate incrementing serial numbers, check how the _RB works order interacts with that sequence before relying on this pattern — confirm serial entry is manual for rebuild works orders, or that auto-increment is not affected.

4. Run Production for Rebuild

Select the rebuild works order and run production. Because this is a new works order, there are no existing process results, so all rebuild information is captured fresh.

Traceability

A rebuild's report is independent by default — it does not inherit genealogy from the original build unless explicitly configured.

To carry genealogy/traceability into the rebuild, include a Scan Part step in the _RB routing.

Caution — duplicate operation names: if the rebuild routing reuses an operation name that also exists in the original routing (e.g. both have an operation called "Assembly"), results from the original and the rebuild will be merged under that operation name. If the original and rebuild need to be viewed as fully distinct traceable events, use distinct operation names in the rebuild routing (e.g. "Assembly - Rebuild") rather than reusing the original names.

Reviewing the Rebuild Product Report

There are now two reports for the top-level serial number: the original and the rebuild (_RB) version, viewable and traceable separately.