Thanks for the information. I know most of the tools related to modeling in creo. Thi video made me an idea about what a PLM software can do in the product development environment.
What would the benefit be for an organisation to use windchill over for example enovia? E.g. where is the financial value? Time spent managing data? The cost of the software? Time savings?
This is a much bigger discussion than a TH-cam video comment, but I will mention two points. (1) If you're using Creo, nothing manages Creo data better than Windchill. (2) Windchill is a fraction of the cost of Enovia and requires less infrastructure. If you're in the market for a PLM system and are benchmarking various solutions, feel free to reach out and I can connect you with additional resources that can help with your decision-making process.
Release management deals with promoting and revising standard documents and CAD documents to control the lifecycle states and approval for use downstream (e.g., manufacturing, supply chain, etc.). Change management involves the use of Problem Reports, Change Requests, and Change Notices in a closed-loop system to control the implementation of changes to configuration controlled objects.
I do not. Honestly that kind of content does not interest me. I have a couple videos on basic Windchill admin but the overwhelming majority of my videos are focused on the users.
I came here from searching for info on Star Trek Impulse engines where you (Dave Martin) wrote an article showing how PTC mathcad can be used. The About the author info used words I'd never heard of like Creo Parametric which led me to PLM and PTC Windchill. I'm finding it interesting to understand how companies go about product design and management. Would you mind telling me how do people learn about these things? What education and/or college topics lead to PLM and the products/tools like PTC Creo and PTC Windchill?
Mechanical engineering is a big field that leads to product development careers, particularly on the physical (vs. software) side. While colleges often teach CAD like Creo Parametric to engineering students, most people don't learn Product Lifecycle Management until they get to workplaces that have it.
Once a team gets over a half dozen people, it really helps to be on a CAD data management system instead of network folders. Also if you are doing any kind of PLM processes, you need Windchill.
My company uses the change request object to release the initial (Rev A) versions of objects (parts, cad, documents, etc.). They will make the content in the design phase of a project, then use the CR to affect existing Windchill objects that truly are affected and they will also add the brand new objects they just created in the design. To me, this doesn't make logical sense. How can you affect a change to something that doesn't exist yet. How does PTC intend for users to apply Windchill and how do most users use it? Are we supposed to be using the promotion request solely to release the Rev A of objects then use the CR for all changes after that? Does anyone else use the CR to release the initial version of objects?
Ha ha ha, Windchill deliberately makes it open-ended so that organizations can follow whatever process they want. It's built to comply with CMII configuration management principles, but you don't have to follow them. Trust me, you go to 10 places, and you'll find they have 10 different processes for release management and change management. According to CM2 practices (the one I'm certified in), you need a Change Notice if you want to create a NEW part, assembly, or drawing. Seriously. If I want to mess around and create a new part, I'm supposed to get a CN. Heck, if I want to move a desk chair from one room to another, I need a CN. I am neither joking nor exaggerating. I've worked at companies that have used both Promotion Requests and Change Notices for initial release. I've never worked anywhere that used a Change Request. I've been involved in Configuration Management for more than a decade, and it's more complicated than you can imagine. And it's not Windchill's fault.
@@CADPLMGuy thanks for the feedback. So we do use a cn and ca. At the end of design, the drafters will put all the new content on the resulting table of the ca, but then they copy all those new objects into the cr affected object table too. They say it's so the reviewers can see all the objects in one place so they dont have to go down to the ca. To me, it just sounds inefficient and complicated. I think it's best if we stay with logic and the reviewers learn how to use windchill ootb. Anyway, you said it best, 10 different companies are going to have 10 different ways to do it. I guess I just have throw logic out window and deal with it here lol.
Well, there is no one way OOTB with Windchill. With zero configuration, there are at least 4 ways you can release or promote an object. Like I said earlier, Windchill is open-ended. It comes down to what your organization's policies are. Having worked in PLM and configuration management for years and years, the best term is bikeshedding. (Look it up.) You say it's throwing logic out the window, but I guarantee it makes perfect sense depending on the other person's point of view. And even though your company's method seems inefficient and complicated, I guarantee it benefits someone. Having been through these conversations dozens and dozens of times, if you look at things through different lenses - engineering, supply chain, manufacturing, program management, configuration management - whichever way you go, there's a legitimate benefit - and disadvantage - to someone.
Best creo mentor i have ever had.
The books by Dave are just amazing.
Thanks, Sourabh!
Thats a great explanation and YES. I ENJOYED the video and explanation
Awesome, thank you!
I am glad I came across this it is very elaborating overview. I cannot thank you enough..
Thanks for watching!
Clear, positive and interactive in the comments, subscribed!
Thanks for subscribing!
Thanks for the information. I know most of the tools related to modeling in creo. Thi video made me an idea about what a PLM software can do in the product development environment.
What would the benefit be for an organisation to use windchill over for example enovia? E.g. where is the financial value? Time spent managing data? The cost of the software? Time savings?
This is a much bigger discussion than a TH-cam video comment, but I will mention two points. (1) If you're using Creo, nothing manages Creo data better than Windchill. (2) Windchill is a fraction of the cost of Enovia and requires less infrastructure.
If you're in the market for a PLM system and are benchmarking various solutions, feel free to reach out and I can connect you with additional resources that can help with your decision-making process.
Very well explained, thank you.
Glad it was helpful!
What is the difference between release and change management?
Release management deals with promoting and revising standard documents and CAD documents to control the lifecycle states and approval for use downstream (e.g., manufacturing, supply chain, etc.). Change management involves the use of Problem Reports, Change Requests, and Change Notices in a closed-loop system to control the implementation of changes to configuration controlled objects.
Where are documents and change notices managed?
In the Windchill database just like any other objects.
Excellent presentation, clear and very informative, thanks!
Glad it helped, Guillermo!
Awesome video, thank you very much for creating!
Thanks for your kind words!
Thank you for this.
Nice Video. Good presentation skills. Do you have video which can provide Windchill architecture for PLM administrator?
I do not. Honestly that kind of content does not interest me. I have a couple videos on basic Windchill admin but the overwhelming majority of my videos are focused on the users.
@@CADPLMGuy ok 👍🏼
I came here from searching for info on Star Trek Impulse engines where you (Dave Martin) wrote an article showing how PTC mathcad can be used. The About the author info used words I'd never heard of like Creo Parametric which led me to PLM and PTC Windchill. I'm finding it interesting to understand how companies go about product design and management. Would you mind telling me how do people learn about these things? What education and/or college topics lead to PLM and the products/tools like PTC Creo and PTC Windchill?
Mechanical engineering is a big field that leads to product development careers, particularly on the physical (vs. software) side. While colleges often teach CAD like Creo Parametric to engineering students, most people don't learn Product Lifecycle Management until they get to workplaces that have it.
Very useful! I can really see how this will leverage my knowledge and increase team productivity.
Once a team gets over a half dozen people, it really helps to be on a CAD data management system instead of network folders. Also if you are doing any kind of PLM processes, you need Windchill.
Thanks sir
U hv well covered the topic ..good job👍
Thanks and thanks for watching!
Helpfull sir
Thanks!
this great stuff
Thanks!
Thank you!
Thanks for watching!
awesome tool, but the bad thing is that it won't install on Windows 11 machine
That's too bad. Most people install Windchill on Windows Server machines.
Thanks Dave!
Thanks for watching!
wow
I hope that's 'wow' in a good way!
no dought
u r just amazing 😊
2x and still slow
Don’t watch. No one is forcing you to.
My company uses the change request object to release the initial (Rev A) versions of objects (parts, cad, documents, etc.). They will make the content in the design phase of a project, then use the CR to affect existing Windchill objects that truly are affected and they will also add the brand new objects they just created in the design. To me, this doesn't make logical sense. How can you affect a change to something that doesn't exist yet.
How does PTC intend for users to apply Windchill and how do most users use it? Are we supposed to be using the promotion request solely to release the Rev A of objects then use the CR for all changes after that?
Does anyone else use the CR to release the initial version of objects?
Ha ha ha, Windchill deliberately makes it open-ended so that organizations can follow whatever process they want. It's built to comply with CMII configuration management principles, but you don't have to follow them. Trust me, you go to 10 places, and you'll find they have 10 different processes for release management and change management.
According to CM2 practices (the one I'm certified in), you need a Change Notice if you want to create a NEW part, assembly, or drawing. Seriously. If I want to mess around and create a new part, I'm supposed to get a CN. Heck, if I want to move a desk chair from one room to another, I need a CN. I am neither joking nor exaggerating.
I've worked at companies that have used both Promotion Requests and Change Notices for initial release. I've never worked anywhere that used a Change Request.
I've been involved in Configuration Management for more than a decade, and it's more complicated than you can imagine. And it's not Windchill's fault.
@@CADPLMGuy thanks for the feedback. So we do use a cn and ca. At the end of design, the drafters will put all the new content on the resulting table of the ca, but then they copy all those new objects into the cr affected object table too. They say it's so the reviewers can see all the objects in one place so they dont have to go down to the ca. To me, it just sounds inefficient and complicated. I think it's best if we stay with logic and the reviewers learn how to use windchill ootb.
Anyway, you said it best, 10 different companies are going to have 10 different ways to do it. I guess I just have throw logic out window and deal with it here lol.
Well, there is no one way OOTB with Windchill. With zero configuration, there are at least 4 ways you can release or promote an object. Like I said earlier, Windchill is open-ended. It comes down to what your organization's policies are.
Having worked in PLM and configuration management for years and years, the best term is bikeshedding. (Look it up.) You say it's throwing logic out the window, but I guarantee it makes perfect sense depending on the other person's point of view. And even though your company's method seems inefficient and complicated, I guarantee it benefits someone. Having been through these conversations dozens and dozens of times, if you look at things through different lenses - engineering, supply chain, manufacturing, program management, configuration management - whichever way you go, there's a legitimate benefit - and disadvantage - to someone.