Community,
My current client wants to use xClass Properties on Itemtypes: Document, CAD, and Part.
Current Configuration
The Document and CAD Itemtypes will use xClass in a straight forward way therefore predictable data generation.
The question is Part. The Part Itemtype is being used for Engineering Parts (Classification: Assy, Comp, Material, Software, etc.) and Manufacturing Part (Classification: Manufacturing).
So for every Eng. Part there can be 1 to 3 duplicate Mfg. Parts created with the same xClass data.
Currently the client has 240 xClass Properties defined and this is just the start. I can predict that the property count will be close to 500 + when Part, CAD, Document are fully defined.
Current:
Each xclass Property requires 4 columns and each Itemtype assigned to an xClassTree (Part, CAD, Document) their item_id, and their Itemtype_id are added to each of the xp.XPROPERTYVALUE tables.
This results in five xp.XCLASSPROPERTYVALUES tables generated: xp.XCLASSPROPERTYVALUES; xp.XCLASSPROPERTYVALUES1; xp.XCLASSPROPERTYVALUES2; xp.XCLASSPROPERTYVALUES3; xp.XCLASSPROPERTYVALUES4; xp.XCLASSPROPERTYVALUES5...
Each of these tables has 100 property values stored in the 100 Columns and managed by 300 columns.
Currently only 1, of many Division, is using the Parts Classified as Manufacturing.
Goals
The client wants to use the xClass Data to do:
1) eBOM validations so performance in gathering xClassPropertyValues is key.
2) Product development regulatory definition and tracking.
Questions
1) Are there any configuration issues that should be considered?
2) Are there xClassProperty implementation considerations that you suggest?
3) Are there performance issues that should be considered?
Thanks for your time and insight.
Scott
