End Item Best Practices

[BL_10161374]

Hello,

We are still getting started with WC in our organization.  We currently manufacturing machines that are sold with a machine specific serial number.  I would like to have a centralized location to hold all the documents that pertain to that machine. For example, manufacturing has build information and the aftermarket has warranty registration documents.  

I was thinking of creating a WT part for the model and serial #.  Within the WT part we could attach the documents for this machine to include warranty history, modifications etc.

Any input from the user group would be appreciated.

[HelesicPetr]

Hi @BL_10161374 

If you set a WTPart attribute "Default Trace Code" to "Serial number" then you can create instance with specific Serial number

Action menu New->

Whit this instance you can specify the BOM with others serials num. if instances exist for others sub parts.

Also documents can be linked to this instance.

So I would try to explore this possibility

 Hope this can help

Best Regards

PetrH

[HJ1]

Hi,

does this mean you need to tell for each item in the BOM the top level serial number(s) it's valid for? The "Effectivity", is it?

[HelesicPetr]

Hi @HJ1 

Generally yes. Depends on customer needs and expectations. 

If you need to track serial number changes you should use change management and propagate serial number effectivity.

If customer just need to keep information for the specific serial number without change management, then you can use new instance without serial number effectivity.

This area is really huge and opens so many discussions how to do so.

PetrH

[HJ1]

Ok, thanks.

Yes, it's a real can of worms. Some years ago we investigated using effectivity, but as the frequency of design changes is fairly high we just have EBOMs and try to keep track with baselines.