Also shared with my colleagues.

Glad to hear that

I don't know what Horizontal Modeling is. Never heard of it before so I don't have any thoughts on it. I can't recommend it (positive or negative) and therefore have no plans to make a video or write a book on the subject. What is Horizontal Modeling?

​@@CADPLMGuy Hi Dave, I answered you back 3 days ago but now I cannot see my comment. I've put link to the webpage where there's more about Horizontal Modeling inside previous reply. Maybe YT algorithm deleted the comment because of that link? In general and short way, Horizontal Modeling is methodology in which you relate all of your part features to previously created base datums. It means that independently of your features count you always create them on these predetermined base datums whenever it's possible (so in Creo language your base datums are the local references for all of your features). Thanks to this you can delete any of your feature without affecting the rest of the model. Of course there are stuff like rounds, chamfers, drafts, etc... that cannot be applied according to this methodology cause they demand to be created directly on the model but the idea of this approach is mainly to make sketch-based features independent of the anothers so that when the changes comes up and you'll need to modify or delete one of them you can easily do it and no one feature will be touched by this. That's very common approach in Catia world but I've no idea if most part of Creo Community follow this or not. What do you think about it?

I believe in and advocate parametric modeling and Design Intent. (My first book was on Design Intent.) I recommend a design approach where you consider likely changes and build your model so that it can be robust and flexible. This should help minimize regeneration failures. I don't believe that regeneration failures are the worst thing in the world. Creo has numerous tools to resolve regeneration failures. Tools like Edit References enable you to transfer all the children of one entity to another so you can delete primary features easily. In Creo, I do not recommend an approach based primarily on preventing failures.

I got rid of my Patreon. KZfaq has something called Super Thanks or something like that to donate. But they take a ridiculous cut of the money. The best thing people can do to help me is share the videos.

Absolutely. I’ve done that for decades. Phase gates are the lifecycle. You even manage the data beyond launch through sustaining and obsolescence phases.

@@CADPLMGuy Yes, 100% agree but over the years I found that most organizations drop the ball once the product is commercialized and data just starts collecting dust in all the systems it’s touched. Great video by the way.

My experience in aerospace and consumer electronics is different. Especially aerospace. When you're dealing with the FAA, you have to maintain that data.