Hello
We are wondering how best to maintain a library of off-the-shelf parts (screws, ELEC components, bearings) for several customers.
This variety of customers requires us to associate several codes with a part/part. One item code per customer.
We want to avoid duplication of files, in our Solidworks+PDM configuration.
We cannot be the only ones to be confronted with this multi-client management. How do you do it? What is the best solution?
One solution would perhaps be to have an item code per customer and also to have a type of drawing and bill of materials defined by customer to find the right item code according to the customer.
Or one library per customer, but this is very complicated to maintain in my opinion.
Hello
I think you have to do a room configuration for each client and manage the properties that differ in the configuration-specific properties.
Yours truly,
Hello
Configurations seem to be a good way to go, but the PDM is not fond of configurations. So to see according to your working method in the PDM.
Were it the customers who imposed the article codes of the rooms in your library?
Hello
And thank you for these first answers. The specific coding is effectively imposed by the customer.
We keep our own Art codes. for compatibility with our ERP, and customers want coding in accordance with their own identification system.
Rereading my answer, it doesn't seem very clear to me.
What I meant was a customer item code property per customer, example a customerArticleCode1 property, another CustomerArticleCode2...
Which can quickly ^be time-consuming if 250 customers.
And of course a different MEP per customer or just the nomenclature according to the need with the column that will look for the right item code corresponding to the customer chosen.
Hoping to have been clearer this time...
Hello
In my opinion, only a customerArticleCode property is sufficient, its value is different depending on the configuration and therefore the customer. For MEP, simply copy/paste the tab and change the cfg of the views and BOM.
Good luck....
For me no config, just a different property name .
Property: customerArticlecode1 = refarticle1Customer1
Property: customerArticlecode2 = refarticle1Customer2
Added some properties is not very cumbersome contrary to a configuration management.
Nothing heavy using the table modify configurations; a single property and as many configurations as clients and therefore ref => the same nomenclature and more than to vary the cfg for MEP......
I'm not saying that it's complicated to manage @etudes_20 but that it makes the room heavier and that depending on the number of customers it can quickly become complicated.
Visiativ support strongly advises to avoid a large number of configurations (slowness). In addition, the risk of errors in the configurations (a function removed or not...) is greater.
So for me it is not justified to use a configuration that would weigh down your part or assembly unnecessarily when a property is only text and therefore lighter.
In addition, if you copy an assembly from one client to another, if you have 1200 screws to change configurations, it can quickly be a pain, while there are scripts to change a background plan in batch.