Each fidelity optimization of OL files is stored on a Fidelity subtype instance. The following table illustrates the five subtypes that are available by default in the Windchill system and can be utilized. The names of these subtypes do not impose any specific meaning. The Publish Rules file dictates a fidelity definition using the “file” tag which includes an attribute called “output-prefix” that must map to a fidelity subtype “Internal Name”. The fidelity optimization is defined by all the “options” tags contained within the fidelity’s “file” tag and it’s those options together that impose a semantic meaning of fidelity to the customer’s enterprise.

The five subtypes that are available by default cannot be deleted. If it is determined that only three subtypes are needed to support the customer’s needs, the Instantiable option of the other two subtypes can be set to No using the Windchill Type and Attribute Management utility. This ensures these subtypes are not used and it prevents them from being selected in a user’s Preferred Fidelity preference.

To create a new subtype, if it is required in your enterprise, follow this procedure. The subtype in our example is called Simple.