When standardising sequences or updating sequence revisions, it’s important to understand how Tascus records which sequence was used during production, and how Work-in-Progress (WIP) units behave when routing is updated. This ensures full traceability without creating unnecessary routing versions.
Sequence Name Display in Product Reports
From version 23.8.0.8 onward, the Sequence Name is recorded and displayed in the Product Report.
For any production run completed after this update, the Status column will show the corresponding sequence used.
Older product runs created before this version will not display sequence names in the Status column.
Product Reports Show the Correct Sequence Revision Used
Tascus records the Sequence Revision ID in the OperationData for each build.
This means:
You can standardise routing IDs (e.g.,
1AA00001_A)You do not need to create a new routing version each time you revise the sequence
The Product Report will always show the exact sequence revision that was used at the time of manufacture
This maintains full traceability while reducing routing maintenance overhead.
Behaviour When Routing Is Updated During WIP
When routing is updated on a unit that is part-way through production, Tascus behaves differently depending on whether the operation is completed or in progress.
WIP State | What Happens After Routing Update | Report Outcome |
|---|---|---|
Operation Completed | No change. Completed work retains the original sequence revision ID. | Product Report shows the original sequence revision used. |
Operation In Progress / Paused | When resumed, Tascus loads the latest sequence revision for remaining steps. Any newly changed steps appear as incomplete. | Product Report shows the updated sequence revision for those resumed steps. |
This ensures:
No loss of historical traceability
No rework of completed operations
Operators always follow the most current revision when continuing work
Recommended Approach
If your goal is to standardise sequences and reduce routing duplication:
Use a stable routing ID (e.g.,
1AA00001_A)Allow Tascus to track and record Sequence Revision IDs automatically
Avoid creating routing versions unless the product structure itself changes
This results in:
Less admin overhead
Consistent operator experience
Accurate revision traceability on product reports
Need Help Reviewing Your Setup?
If you’d like support confirming the behaviour on your system or reviewing your routing structure, just contact support and we’ll walk through an example together.
