Hello,

I have a question about managing Special Characteristics in 3DExperience (Cloud). Our Automotive customer wants to track and manage quality Special Characteristics for their Products. I would propose handling this as an attribute, but because information about Special Characteristics is used in several processes (FMEA, Control Plan, ...), it would be better to have it in the platform as an object. I considered using a Requirements, but ENOVIA does not provide a way to connect Requirements to specific Parts or Products.

Do you have experience or any best practices for implementing Special Characteristics in Automotive Quality within 3DExperience?

Thank you.