Why PLM initiatives get stuck

 There's something people don't tell you when you take on a Product Lifecycle Management (PLM) initiative: Sometimes they get stuck. Occasionally it happens in the implementation stage, because of lack of planning or simply bad planning. At times it happens after the initial deployment, when the system stops growing and evolving. And sometimes it happens before you even get started.

  Below are the "Top 10 Ways Why PLM Initiatives Get Stuck" from Aras Corp.

1. Gaps in coverage - You can't provide end-to-end results with isolated point solutions

 Most companies have deployed pieces of their PLM process without developing a unified PLM strategy. They've got project management and a few different Product Data Management (PDM) tools. There's another system for sharing WORD and EXCEL files among non-technical users. What they don't have is a unified view of the overall process and all of the related information stored in, and provided by, these systems.
 If you're stuck: Your users are not going to part with point solutions that work, nor should they. Instead, bring in PLM as an over arching process layer that connects all those point applications. Using techniques such as Web services federation, you can bring data from the other systems into one common user interface while leaving the point solutions intact.

2. False Starts - The consulting cycles continue to churn and go-live is nowhere in sight

Implementations stall for lots of reasons. Some may be out of your control. But the biggest mistake happens before the implementation even starts and it is much easier to avoid. The problem is choosing the wrong technology. Everyone says they want an out of the box PLM solution. But most companies are unwilling to play out of the box rules. Unless your company is willing to change all of your business processes, a shrink wrapped product simply won't work and you'll need to customise. If you're still customising the software a year or more later and haven't rolled out anything, you probably chose a system that is never going to work the way you want it to.
 If you're stuck: You have two choices. The first is to accept the limitations of your solution and fundamentally change your business to fit the software. The second option is to walk away. Apply what you've learned and pick a new solution that's more flexible and meets your company's real world needs. Neither option is very appealing once you've invested in a technology, but if you don't change course you will continue to spend money on a system that is never going to provide benefits your company requires or deserves.

3. One (GIANT) Step Implementation - Fastest way to overwhelm users and ensure system failure

You can't turn on 15 modules of PLM over the weekend and effectively changing the way people do everything overnight, and then expect them to accept it. It's a recipe for disaster. The technical folks won't use a system that doesn't meet their needs and non-technical users will likely get overwhelmed and reject the system entirely. Both user types end up creating workarounds and the PLM system won't contain reliable real-time data. Eventually the system fails because it is not the trusted source of the truth.
 If you're stuck: Stop. Pick one process and roll it out. Get feedback. Make adjustments. Wait 30, 60 or 90 days and roll out another. A phased implementation approach requires flexible software that doesn't relyButy sportowe Nike