Between PLM4P's customization and extensibility capabilities, I know it can do a lot but this is probably a stretch.
Is it possible to take a specification type, such as Material, and base a new "type" off of it? Where the Material spec type would remain the same, and the new derived spec type would retain all of the same functionality for Material specs, but have its own name, icon, etc.? This would be similar to Agile 9's subclassing.
Failing that, is there any way to make visual changes based upon a value in a specification? For example, if I open a material spec with a classification of ABC, the icon in the object header is the normal material spec icon; but if the classification is XYZ, then it would display a different icon in the object header.
This cannot be supported out of the box. However, it may be a pretty straightforward and easy problem to solve, so I recommend submitting a service request with support. We'll evaluate and target for a future release.