Background:
In our company we use CreoView as our main engineering 3D viewer, used by very many different functions.
This tool is used by all our engineers when viewing and analyzing product data models (thousands of users).
In CreoView our engineers generate value added data by creating annotation-sets, views, coloring, positioning of parts, etc.
A very typical use is to subdivide the large product model into views for the steps to perform in various operations (Operations/Aftermarket etc.) and the Engineers position data and assign colors to highlight actions to use in the next step of the process.
An important aspect here is the ability to filter and subdivide/group the model using metadata (function group etc.) That works well in CreoView MCAD but not in Creo Illustrate, especially not in the EBOM.
We are now moving hundreds of users from another tool with these capabilities into CreoView and Creo Illustrate.
We would like to have a workflow where the engineers do the things listed above in CreoView and then this information is transferred to Creo Illustrate for the final production of an Illustration/Work instruction.
Without this capability, either:
The Technical Illustrators need to redo the work done in CreoView, in Creo Illustrate (having both systems running on separate screens or using screenshots) or,
Engineers need to work in Creo Illustrate to do the assembling of information but with a major loss of efficiency due to lack of CreoView MCAD functionality (unlikely scenario).
Thus we request a feature that allows import of this value added data from CreoView into Creo Illustrate.
Example of how this could work:
Engineers create annotation sets in CreoView
Technical Illustrator imports file created in CreoView with annotation sets into Creo Illustrate
Views from annotation sets are used as the basis for figures
Optionally: Option to select that only product geometry that is part of the views is imported into Creo Illustrate
... View more
