It is seen and loaded as needed into Editor. So when someone needs the graphic for use in Editor. This will create a published PVZ attached to the C3DI file from Creo Illustrate. Once the illustrator has created the graphic in Creo Illustrate, it is checked in and the second set of publish rules take effect. But for someone needing to apply a change to the illustrations it is most valuable. This data would have no use for the engineers. The GDD is also used to track what illustrations were created from it.
But this file only updates when the above condition is met for the source CAD data. This GDD is tracked, managed and iterated just like the CAD parts and assemblies. This GDD is then created and put into a folder for access by the illustrator. So we setup a publish rule that says to create a GDD when the CAD data is released or approved or reviewed or etc, etc. The Engineer working on a part or assembly may check-in that data multiple times before it is ready for use outside of engineering. The system is designed to separate the Illustrators from the native CAD in a controlled manor. These publish rules are setup according to what business rules your company wants in place.Īs for Creo Illustrate not opening the native Creo Parametric data from Windchill, that is part of the work flow. One set for creating the GDD (Graphical Dynamic Document is a type of PVZ file) as an illustration source file and another to post publish the Creo Illustrate files for use in Editor. There are a set of publish rules that need to be setup in Windchill. Some of what you are seeing as stated above is configuration and some is business process based. This also seems a little clunky if I have to do things manually.Īs with most Windchill based processes there are configuration questions that need to be answered. I could also manually publish a pvz right from illustrate and import that into Arbortext, but again, I'd lose associativity. I realize we could get the job done by doing things manually - save an assembly to my hard drive and then open with illustrate, but then i would lose associativity.
#CREO ILLUSTRATE HOW TO#
I can't find anything in the visualization guide that tells how to set up a cadworker for c3di files though. What's the standard practice for getting parts OUT of creo illustrate and into Arbortext? I thought we would checkin our c3di file to windchill and a publisher would create a pvz file for arbortext to pick up. Why can't creo illustrate open what creoView can? do i need to publish another pvz of every CAD file just for creo illustrate to be able to open it? I did notice that I can open Creo parametric files from my hard drive, but not from Windchill - this seems like a bug or something. Windchill creates a pvs/pvz file every time it publishes a thumbnail so we can open it in creoView. However, I can import pvz files from Windchill, but it can never find any.
In reality, I can't import Creo parts from windchill into creo illustrate. What's the standard practice for getting parts from windchill INTO creo illustrate? I thought we would do file, import, from windchill and then grab a Creo cad part or assembly. We already have Windchill and we just purchased creo illustrate and arbortext.
0 kommentar(er)
