After yet another "Product works to Specification" from Tech Support, I respectfully submit the following Ideas to improve the validity of the specification and have Part Instance Functionality behave in a more useable way that is better aligned with the practical realities faced by an Organization attempting to leverage it.
- Allocate Existing: Limit available selection only to Unallocated Instances. This list is going to get huge over time and very quickly become unusable.
- Lot Traced Items: Lots need to have a Quantity and keep track of their Allocations. It appears that the specified functionality allows for unlimited Allocation of a Lot based Part Instance. This is an opportunity missed for error-proofing as you could have any number of Allocated Instances related to a Lot. In reality this needs to be limited to a Lot Quantity. Lot based Part instances also need to be filtered out of the Allocate Existing list when fully Allocated (i.e. Lot QTY = 100, Total Allocations = 100)
- For Lot based Part Instances need to be able to allocate multiple. The Part Instance Structure has an Instance for each rather than a Quantity so to Allocate you need to do it one by one. This is cumbersome, especially considering the use case for Lot Traced Items of Fasteners, for example and a complex system could have several dozen or several hundred. Allocating one by one seems to be more effort than it really needs to be.
