Product lifecycle management [PLM] is a discipline. It is not just about engineering data management. It is about supporting your company’s efforts to deliver customer satisfaction. It is about following and improving procedures [processes] that could include compliance requirements. It is about collaboration inside your company and with customers and vendors. It is about solving your company’s specific problems. It is about improving efficiency. It is about so much more than engineering…
The Scope of PLM
Ultimately, a company will take on a PLM project to solve a problem or problems. This problem will be either costly or extremely inefficient and it will be important enough to spend money on solving it. Initially, narrow your scope to focus on a solution that will solve your problem or problems.
PLM projects that have failed started with a scope that was too large. The longer your project takes, the more your people will lose interest in it. It is in your best interest to complete your initial PLM implementation in about 6 months.
PLM software adds control and visibility
PLM software is like an Excel spreadsheet – it needs to be configured to meet your requirements.
Control – It will ensure that all of the steps you have identified in a procedure are followed. It enforces your access rules. Ultimately it can make sure that the right information gets to the right person at the right time.
Visibility – People can see where information is within its process. They can see the status of information or a change request. They can see a complete history of how information is created, approved and released.
Solve a Problem
The typical customer starts with a problem focus or starts from product focus. My best advice is to focus on solving your problem(s) and then look at product alternatives. Don’t start with a technology in mind while looking for a problem to solve.
Ultimately, the more complete your requirements document the better your solution.
Contact me if you would like some help…