This may not be relevant to your business use case but is applicable to others considering this solution.
We had a configuration similar to this a few years ago where every check in of a part generated a STEP file. STEP and IGES files are not small like the visualization content. They are nearly the same size as the original CAD models. In highly surfaced models, they can be larger than the CAD models. Imagine every check in being approximately 2 to 3 times the size of the original CAD Document. This configuration bloated the file vaults and it didn't include IGES of parts or STEP/IGES of assemblies and drawings.
IT was very anxious about the growth rate of their file vaults in their data center where they paid by the GB/month.
When we researched how frequently the STEP/IGES were being used, we discovered the shop and external suppliers only used a very small fraction of the generated files.
Ultimately, we manually purged all the STEP Representation Additional Files content from Windchill. Then we adjusted our publish rules to only publish STEP of parts in prototype and release states. We allowed users to manual publish STEP upon request to cover any non-released iterations they needed.
FYI: Descriptions of the Publish "on" values.
<!-- Publish on Check In -->
<publish additional-files="standard_files" on="checkin"/>
<!-- Manually publish from details page -->
<publish additional-files="standard_files" on="create-representation"/>
<!-- Publish via publish scheduler -->
<publish additional-files="standard_files" on="schedule"/>
<!-- Publish via workflow, state change, etc. -->
<publish additional-files="standard_files" on="unknown-source"/>
<!-- Enables UI pick to Post Publish from details page Representations listing -->
<publish on="manual-post"/>
