fli - Thursday, October 7, 2010 4:47 AM:
Hi Everyone,
I am participating a pilot project for an international company.
I have a challenge solving spare-part catalogue relations.
I have attached a document (one page) describing the problem with datamodel, workflow and a possible solution. (next post)
I would very much like some feedback and/or a more elegance solution.
Regards,
Christoffer
PeterSchroer - Thursday, October 7, 2010 8:05 AM:
Hi Christoffer,
I did not see the data model picture yet, so I can only make some guesses. Are you using the Structure Browser to navigate the multi-level BOM, or are you using the Community Soluition for the Multi-BOM tab? Structure Browser can normally follow any relationships, standard or custom, shoudl not be a problem. Multi-BOM uses a SQL Stored procedure to query the deep BOM (SQL procedure for fast performance -- so that BOM with like 250,000 parts is loaded quickly). If you add a custom relationship, you will need to change this SQL Procedure.
I am also curious how you are modeling spare-parts. Many companies are facing the same problem, and maybe we can create a nice common solution.
Good luck,
Peter
fli - Friday, October 8, 2010 6:35 AM:
Normal 0 false false false EN-GB X-NONE X-NONE MicrosoftInternetExplorer4

fli - Friday, October 8, 2010 9:26 AM:
Normal 0 false false false EN-GB X-NONE X-NONE MicrosoftInternetExplorer4
PeterSchroer - Tuesday, October 12, 2010 7:33 AM:
Hi Christoffer,
Sorry for the delay, traveling to Denmark this week. About your question of Float behavior, the first example is the standard solution. The relationship "floats" to the new version of Part B. It is also possible to have the 2nd senario, where instead of the relationship "floating" we create a new Relationship instance. You can imagine that there must be properties of the relationship (usually called Effectivity) that define when the Relationship is considered in the configuration. If you need this second behavior, this is development work we are doing with Xerox. It will become a new standard solution in the core framework, but today we can also give you the working add-on package.
I think the design you have started with the Plate as a new Relationship and new itemType is correct. The behavior is different from other Part items, so a new itemType is a good idea. We have also done a solution using Classification -- for Parts and Variants, we use the same Relationship Type, but the server has different behaviors depending on the Classification of the related item. I can share this idea with you also.
Peter.