On Dec 6, 2007 5:12 AM, David Tangye <
..hidden..> wrote:
Now we change the amount of labor in A1 to L1 = .5 we have to redo over 10,000
assemblies by hand or hack the database. Not very appealing.
If a manufacturing process changes in any way, you are building a slightly different product. Since SL and LS are basically accounting systems and not manufacturing operations support systems, their support of manufacturing is limited to simple assembly. Product versioning is not supported. So you need to define a new assembly,
A1.1, where .1 relates to a 'build process/script/spec/recipe'.
If you hack the database you need to ensure that you are not invalidating what was accurate data for the old way something was assembled. Eg would old historic invoice line-items for those assemblies now be incorrect.
First, David is correct about the nature of the problem.
Basically there are two ways to approach this problem. In reality the combination of both is probably desirable. The first is to track assembly components per assembly, the second is to track versioning of assemblies.
It seems to me that long-run, we probably want to track assemblies and versions along with modifiers and deltas. I.e this sandwich was version 12 of the salami sub with extra cheese, no tomato, no onions, etc. However any step in the right direction (such as adding versioning) would be a good thing :-).
Best Wishes,
Chris Travers