Creo Parametric - Pro/Process for Assemblies - Part 1 of 4

[@ajtroglio]

Use this module nearly every working day. Very good and forgotten module

[@CADPLMGuy]

Agreed. It should get used a lot more than it does.

[@mission737]

Hi generally we create Assemblies to be " as designed" to carrry design intent and the moment we check the assembly in to windchill it would generate an eBom which depicts " as designed". My question is for the , if i create a pro / process file in creo of same assembly to show sequnce...do i need to manage this item in windchill with a different number or is there a way in windchill to say like as soon as i check in it creates an eBOM as with configuration like " as shipped " with same assembly number?

[@CADPLMGuy]

The Pro Process assembly will need a different number. As I pointed out in the video, Pro Process hasn’t been updated since the 1990s. PTC didn’t acquire Windchill until 2005. Checking in a process assembly generates the same product structure as any other assembly. But it would be more akin to As Built versus As Shipped.

[@mission737]

@@CADPLMGuy Thanks for the reply

[@ajtroglio]

In pro/process you are essentially creating an MBOM from the design EBOM. You are free to add any additional items to this assembly which can either be bulk items, or, a solid model. I typically add bulk items such as loctite or tie wraps. Once inside windchill, you can pull a report on the MBOM. I name my process assemblies as _PRS

[@Stocjon1985]

Nice video. Just as an observation, in general de User Interface from CREO is no friendly compared to other CAD systems.

[@CADPLMGuy]

Well, that’s kind of a general statement. I don’t want to get into an argument and I may end up deleting this entire comment. Compared to Onshape, SolidWorks, or Inventor, I’d agree to an extent. But compared to other medium to high end CAD tools like NX or 3DExperience, I don’t see how you can say that.

[@Stocjon1985]

​@@CADPLMGuy you can delete it is up to you. I just commented it cause you commented in ur video that people did not like the drop down sequence of the menus in previous versions of CREO. Sure I cant say about all CAD systems, probably another CAD system is worse but related to NX I dont know your knowledge in that but I say I assure you NX is much more easier in the steps to apply a function then CREO based on my knowledge on the functions that I know in both softwares (NX 14 years experience and CREO 5 years experience).

[@CADPLMGuy]

I'm currently planning a "Creo for NX Users" series and will probably film the first segment in the next couple weeks. However, rather than making subjective statements about this CAD system is better than this one or this CAD system has a worse UI, I'm going to focus on providing value to people. As I've said in several videos, it's time for the CAD wars to end. I've got my opinions about the NX UI and workflows, but using my platform to express those isn't constructive. I feel the same way about general and blanket statements comparing any one CAD system to another.

[@Stocjon1985]

@@CADPLMGuy ok it is your opinion and it is fine but the CAD war will never end cause it is business and these companies are competing to each other so they are making the war and the first guy to start the war is the Sales man from CAD company. They want the customer from the other. If CAD softwares were the same there is no need to have a lot of them and sure one is better than other otherwise Companies dont switch them(High | MID | Low - End). It is sure that too, that one software is not better than other 100% I am honest to say that Flexibility from CREO is much easier than Deformable part from NX at the same time Expressions from NX much easier than Relations from CREO. I follow your channel in order to get more knowledge in CREO and it helps and we need to say when something is better and worse otherwise there is no direction for improvements. When CREO will release something like Visual Scripting from Catia or Algorithmic Modelling from NX? It is a good to point for something to be improved. Simple as that. Do not get it personal cause I am not getting.