Recently active
I've seen at least one discussion on this topic, and I've pulled my hair out on at least 2 occasions now trying to fix this problem.If I tell everyone and post it to the social media cloud maybe I won't forget next time. Lesson learned: Document, Document, Document.So, you create a new drawing and the format keeps showing up new in the workspace.You have formats in Windchill, and it shows the conflict.You select the format and perform an update to re-connect it to the Windchill copy of the format.But why should you have to update every time? You don't!Here's our setup: Start files and Templates Stored on a Fileserver Formats Stored on a Fileserver & Stored in Windchill &
If you've spent any time working with large assemblies you know how much of an impact assembly cuts can have on your machine performance. Yet as an administrator we've all seen that one person who loves to use assembly cuts to make parts the way they're going to be machined in real life. Make a weldment, then drill a bunch of holes. Put a bunch of parts together then make a hole for a fastener, and so on. What I've been told is that, basically, for every assembly cut you make, Creo not only keeps a copy of your models in memory, but it keeps a copy of every model with each assembly cut. So let's say you have 2 pieces of metal plate. You have 2 models in memory. Now add an assembly cut through both. So Creo keeps the original 2 uncut plates in memory in case you decide to open either one, and it keeps another copy of each plate with a hole cut in each one for the assembly view you're seeing. With this theory if you put another hole in the plates, not only do you get the original 2 model
Library ModelsThanks to the reusability of 3D models in Creo we only have to make a part once and we can show it in an infiniate number of assemblies and drawing views. In the past much of these detail views would have been drawn with only the necessary detail the drafter determined to show that component. Today these fine details still impact us as minor processing delays rather than time spent sketching or stenciling them.Who makes library models? This has been a point of contention among our users and administrators. The users think the administrators should be modeling up library parts as a support function, but the administrators think the end users should be modeling the parts. It becomes a game of back and forth.The Engineer's point of view: I just want to put a bolt in my assembly. I don't have time to make a bolt. There should be a library of parts already made for me like going to the hardware store to pick one out.The Administrator's point of view: I don't know what bolt you
When you first start using family tables well, you see the entire world open up. You can make thousands of parts in seconds. Everything is great. Some time goes by, and you become more familiar with them. You have to change a parameter and realize you have to check everything out to propagate that parameter to every model. Maybe you start making family tables of family tables. Maybe you make family table assemblies. It's not long when you start to realize the bigger and more complicated the tables, the more trouble they cause. Especially when the people making them aren't as experienced and they are being used in many different uses.So the situation we faced were some of our engineers were using family table assemblies to make items that were not tabulated items. One example was a motor with different wire routing, Some were the same motor, some had different wiring options. Another case was using a family table assembly to create a simplified representation of a design assembly. The l
Ok, let's set the scene. Everyone is using Creo Parametric and Windchill without any problem. Sure some stuff isn't filled out completely. Maybe a datum (or a thousand) are showing. People aren't following standards, but they're not done yet. They'll get to it later. The models fail from time to time. Things don't look right. The computers start slowing down more and more. Now imagine the next day, it all changes. Datums are hidden on layers. Models are regenerating. They're named correctly. Data is filled out. What's the one thing that can start the change to having good data faster than a manager threatening to fire you?Gatekeeper.Gatekeeper verifies ModelCheck was run on a component, and based on the parameter you specify in Windchill will allow or disallow Creo Parametric objects from being checked in. Gatekeeper only verifies modelcheck parameters in the Creo models. Despite what people say it has no personality, it has no soul. It does not hate you. It is not evil. However, you w
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.