Skip to main content
Jun 20, 2025 5:56 PM UTC
Archived

Embed CREO View Settings During WVS Publishing

Problem summary:

3D PDFs contain consistent engineering content but can only render small models, making it impossible to send even medium-sized MBD engineering to outside suppliers. This is a sharp limitation on the extent and effectiveness of MBD implementation within existing PTC tools.

 

Enhancement summary:

During WVS publishing through Windchill / PLM, embed the source company’s local settings in the resulting CREO View file, so that any other outside company or organization that receives that file and opens it in CREO View (including CREO View Lite) can view its content identical to how the source company sees it.

 

This eliminates the need for 3D PDF to send MBD engineering to suppliers and enables significantly larger models to be sent, since CREO View is a lightweight tool that can handle significantly larger models than 3D PDF.

 

Details:

To send MBD data to suppliers (who do not have access to our company’s internal instance of Windchill / PLM for security reasons), the current method is to publish that model to a 3D PDF using a third-party tool, such as ANARK. The use of 3D PDF for sending this data is driven by consistency: a 3D PDF viewed in Adobe always looks the same.

 

Sending CREO View files is not viable at this time: the content will display differently at a supplier than internally, because their local CREO View settings are different from ours. That variation in engineering content is unacceptable, since all parties viewing the content must see the same engineering requirements. Thus, use of 3D PDF is the only viable option to send MBD engineering to outside suppliers for the current state.

 

However, 3D PDFs have a low limit on the size of the model that can be rendered. Models that are medium size or even medium-small (from a CREO Parametric perspective) run very slowly in 3D PDFs, taking a long time to load and render. This slowness even occurs on engineering machines that have large RAM and graphics capabilities (machines that can run CREO Parametric for large assemblies). When such a 3D PDF is viewed on a standard machine – such as those used by suppliers who do not run CREO Parametric or any other CAD tool – they are nearly unworkable and often crash. It is therefore impossible to send our suppliers MBD content of any significant size using 3D PDF.

 

CREO View is a powerful tool, since it uses lightweight models. Its weakness is consistency across companies: the engineering won’t look the same to different companies because the CREO View files do not bring over the source company’s local settings. This inconsistency in CREO View is the reason 3D PDFs are used instead. But if WVS can pull the source company’s CREO View settings and embed them in the CREO View file at the time of publishing, those settings can “ride along” with the CREO View file and therefore cause the model to be viewed consistently at any supplier and internally.

 

To make this approach realistic, CREO View software must be easily and widely available without costly licenses, meaning CREO View Lite must have the capability to read and utilize the settings included in the WVS files for every model that is below the Massive Assembly threshold (since Massive Assembly is a special license for CREO View). This would enable all our many suppliers to install the viewer quickly and easily to process our engineer data, just as they can with Adobe.

 

2 replies

Community Manager
Jun 23, 2025 11:07 AM UTC
Status changed to: Clarification Needed

Thank you @tim_D for publishing your idea. However, we ask you to arrange the information as specified in the form you saw in the submission process. (questions below). You may simply add a comment to your idea. 

Please let us know within the next two weeks.

Please include detailed documentation such as screenshots, images or video.
1. What product and version are you running?
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Community Manager
Jul 7, 2025 9:00 AM UTC
Status changed to: Archived

Hello,
We are following up on our request for organizing the information on your idea. In the absence of further comments from you, we are archiving your idea. You still have the option to post a new idea with all the details required.
Thank you.