It is a fast-paced and complicated world, isn’t it? While we’ve gotten instant access to information around the world, I think it’s gotten harder for each of us individually to really understand what’s going on in the world. There’s simply too much to register. I think that’s why, in general, we like concise perspectives that distill the gist of a situation so we can come to a conclusion and move on quickly.
Digitalization and the Digital Thread
Is Teamwork the Key to Simulation Driven Design?
Back at the beginning of December, I published a post titled The Very Real Skillset Challenges of Simulation Drive Design. It identified four main areas of knowledge or skills needed to really make a simulation driven design initiative successful including. It also looked at some typical engineer roles and their ability to gain and keep these four types of skills or knowledge.
PDM-less PLM: Is It Pragmatic or Just Problematic?
Since PLM was first conceived, it has almost been inseparable from PDM. The majority of PLM deployments included PDM as part of the PLM deployments. However, more recently, the idea that PDM must be deployed with PLM has been eschewed. Some new PLM solutions only offer plug-ins or integrations to 3rd party PDM systems, all of which is optional. Is this a good or bad idea?
More Reclamation Work for Collaboration: Providing a Product Development Context
In the last post on collaboration, we covered a lot of issues surrounding collaboration. It’s been overused. It’s been used without specificity. As a result, we all cringe a little bit whenever we hear it being trotted out to describe another process or set of engineering software.
Email is Not Enough: Why Product Development Needs More for Collaboration
Do you remember when you first got email? Mine was through work and I remember something clicking in my head when I realized what it meant. It’s changed the way we work. We no longer had to get on the phone to communicate remotely. It enabled faster and more accurate decisions.
A Framework to Reclaim a Tarnished Yet Worthy Term: Collaboration
How do you feel about the term collaboration? I know. I know. The ‘sigh and roll your eyes’ reaction is a pretty common one. And in fact I react that way myself more often than not. Over the past ten years, collaboration has been used left, right and center to describe just about anything and everything in the product development realm. And as a result, no one really knows what it means anymore. Ask ten people for a definition of collaboration and you’ll get twenty back.
Vuuch: A Unique Approach to Social Computing in Product Development
Overall, the objective behind Vuuch is the same as it has been for any other collaboration solution provided in the last ten years. If you resolve issues faster, then you can go through more iterations resulting in a better product or you can reach design release faster (or maybe just on time) to keep pace in the schedule. That being said, this solution goes about it in a markedly different way. Here’s what’s advantageous and concerning from my perspective.
Howard Schimmoller Talks About Windchill at Lockheed Martin MS2 Divisions
I’ve always been extremely curious about PLM deployments in larger enterprises. Based on my experience, larger companies tend to take on PLM to support an internal initiative. And because internal initiatives often widely vary from company to company, the ultimate form that PLM takes within those companies can be completely different from one another.
VISTAGY and the Impact of Developing a More Complete Product Definition
A few weeks ago, I published a post that focused on the form, fit and function aspect of the product record. In it, I differentiated between artifacts that defined a product’s form and fit like 3D models, diagrams and schematics and artifacts that defined or predicted a product’s function like simulations, analyses and tests. I think this is a pretty good representation of products composed of mechanical, electrical and software components.