Improve Work Orders workflow for more efficient UX
Description
Attachments
- 09 May 2024, 04:10 am
- 06 May 2024, 02:30 am
- 06 May 2024, 02:30 am
- 06 May 2024, 02:30 am
- 24 Apr 2024, 06:57 am
- 24 Apr 2024, 06:57 am
- 24 Apr 2024, 06:57 am
clones
is blocked by
relates to
Activity
Mike Sheen 17 May 2024 at 03:55
See https://jiwa.atlassian.net/browse/DEV-10860 for a simple, clear description of what we did here.
Monica Holliday 16 May 2024 at 01:57
Passed testing 07.02.01.00 SR19
Monica Holliday 10 May 2024 at 05:47
Retest once https://jiwa.atlassian.net/browse/DEV-10854 is fixed
Scott Pearce 9 May 2024 at 06:32
Fixed.
Fixed.
Monica Holliday 9 May 2024 at 04:10
Failed Testing 07.02.01.00 SR19 Build 2
Can set the status from “Closed” to any open status again. This should not be allowed at any time.
Cannot change status to Closed for all Work Order Statuses, I get the following error.
Steps to recreate:
New WO. Add Bill No 1089-AX.
Change Production QTY to 2.
Change Explode Policy for both Sub-Assemblies 1089-XX-SN and 1089-P from “Never” to “Always”. Save.
Click on Component Tree.
Click on the dropdown for “Set All Work Order Statuses To:” and select “Started”.
Save. All worked okay and Sub-Assemblies created.
Fulfill any back orders if any on the open work orders.
Go back to Parent Work Order, click on Component Tree, click on the dropdown for “Set All Work Order Statuses To:” and select “Closed”. Error received.
The version 7 Manufacturing module is based on a lot more sophisticated platform than version 6, which means it’s more robust, reliable and also flexible, but that has come at a cost to performance.
A work order containing 70 inventory items and 20 sub assemblies could take 20-30 seconds to load. A common workflow means that a user must open a work order, wait, then we adjust quantity and save (wait), select started (wait), save (wait), close (wait), fails (wait), realise some items on backorder (wait), close again (wait).
When the work order contains 20 sub assemblies and some of those may contain sub assemblies, the user has to navigate to the end to start at the bottom of the chain, loading each individual work order and setting status as they go.
Suggestions for improvement:
Use ErrorText to display a tooltip on the input node and component tree if there are insufficient quantities of an input, an input to a sub assembly etc down the tree.
When the user sets the Production Quantity, set the Output quantity accordingly at the appropriate status (https://jiwa.atlassian.net/browse/DEV-9872#icft=DEV-9872)
When the user sets the top work order to Started, set all the sub assembly work orders to Started.
When the user set the top work order to Closed, set all the sub assembly work orders to Closed where possible. Tell the user where it’s not possible.