Link This |
Email this |
Blog This |
Comments (0)
Getting Started with PLM: Pick a Department to Approve
October 29, 2007
This is one of a series of posts suggesting where to start implementing PLM. We started with identifying that many companies start by getting their product data under control. But what's next? And how should you decide?
Starting Small is OK
This may seem to contradict a lot of PLM doctrine and probably a lot of what I have written about. So let me start by saying that I don't suggest that you only improve one department with PLM. But it can be a way to start down the path, particularly if you want a project that can drive quick value and requires a relatively easy political challenge.
Don't Plan to Stay Small
The important thing is to remember that PLM improvements shouldn't end with one department, and so a longer-term view towards the end goals should be put in place. Does this apply to every tool investment? Probably not, that would be a bit too controlling. There are many point applications that aren't a part of a broader PLM suite and don't require as much process or software integration. Examples might be some Computer Aided Engineering (CAE) applications. On the other hand, the decision on some tools that may seem independent may have implications on other decisions as your PLM Program progresses. Even the core CAD solution - which has traditionally been chosen as a standalone decision before PLM - can have a big impact on what long-term strategies you can employ. Boeing could not be executing their current vision without the capabilities and ecosystem of a highly integrated CAD - PLM environment, for example. The Enovia environment that helps companies work in parallel (but still in context) relies heavily on a tight level of Enovia - Catia integration. Not all CAD solutions are a part of a larger vision like that, and have that same level of interoperability. On the other hand, the traditional Enovia solutions (now called Enovia VPLM) does not have the same level of supply chain capability that a solution like Agile or MatrixOne (now also a part of Enovia) offers.
Which Department?
OK, with all of my disclaimers about why picking a single department might not be a good idea, some may choose this path. If this is the easiest path to choose, which department will you start with?
- Engineering - This might be an obvious one. You probably have design tools in place. Confirm that these fit into your larger strategy. Beyond design tools most companies will gain control of their design data through some form of Product Data Management (PDM). What next? Maybe an advanced search capability - perhaps even geometric search - that helps engineers find designs quickly and promotes reuse? More analysis capabilities to support a "design it right the first time" approach? The possibilities here are endless, and perhaps obvious to many, so I'll move on.
- Marketing - Let's pick a less obvious one. What about helping pick more valuable products in the first place? Instead of improving the engineering on products the market doesn't want or won't provide a solid return, why not improve the ability to capture market and customer requirements? Why not invest in improving the portfolio management process?
- Manufacturing - This might start to sound cross-departmental, but what about improving the definition and communication of manufacturing processes? What about using multi-media to share designs and instructions with the plant? Or, start capturing manufacturing data to feed back to Engineering. OK, this can get cross-departmental pretty quickly.
- Service - Why not share more design information with service personnel? Or provide them with up-to-date maintenance and repair instructions?
A number of these can be enabled by extending existing design data to benefit a "downstream" department. I will offer the Aberdeen report on Extending the use of 3D outside of Engineering for some examples and guidance to get started.
As you can see, there are a lot of choices. These are just a few to spark your imagination. This is just one more option to choose in finding your path to PLM. From this point forward, we'll take a look at the next challenge - how do you select a PLM vendor? While picking a department may be a good step, please remember that even the first step should be a part of a bigger strategy (see previous posts on the PLM Program).
I look forward to your comments.
Posted by Jim Brown on October 29, 2007 | Comments (0)