You can export the Creo model as a STEP file, suppress all the features in the model tree, then import that STEP back into the model as a SOLID, higher up in the model tree right after the (default?) CSYS used to export it. If you need to change the model, suppress the STEP file feature, make changes, and then repeat the process ending by resuming the STEP import after you've redefined it to use the new version of the STEP file. This way the model retains all it's features, but in a vastly compacted form, yet still retains the ability to make changes to the native features and keep making new STEPS as needed. You can use the same name for the STEP file over and over, and simply redefine the "Source File" (Important!) of the STEP feature to use the newest version.
You know, I'm glad you prompted me to think about this, I think this technique could be used for ALL files in large assemblies to speed things up. You could make it a 2-instance family table part, and swap out the instances as needed if you needed to change the model. Further, if you did this to all files in your database, it would probably speed Windchill up significantly as well also. Step files are drastically smaller and less complicated. Hmmmm.....
As a side note, I've found that simply suppressing all the features and then saving the file results in a file DRASTICALLY smaller than a STEP file for times when the recipient (via e-mail, etc.) ALSO has Creo. If they use SolidQuirks or Tormentor, then you might be stuck sending a STEP.
EDIT: Well, it sorta worked. The original file was 1,140KB, the STEP file generated was 381KB, but suppressing all the native features and importing the STEP brought the file size back up to 1,044KB. So, it reduced the file size by maybe 8.5%. Not as much as I'd have liked (or thought) but it DID work. And for REALLY large assemblies or large assemblies of much more complicated parts (big IM plastic parts, large castings, etc.), this might just be a thing. Caveat emptor....
