There are varied benefits businesses expect to achieve by implementing PLM. These outcomes are usually grouped into the three usage levels in the organization – strategic decision information benefits for executives, product and operations management control for managers, and transactional activity benefits for front-line personnel.
Oleg Shilovitsky’s insightful article, Mobile PLM gold-rush. Did vendors miss the point? seems to have sparked some conversation about PLM solutions for mobile devices. The article suggests that not all mobile implementations of a software platform are equally effective, and that different hardware often calls for different approaches to offering solutions.
Agile 9.3 made significant improvements in the web client interface, created a wider set of events, improved notifications, and opened up access through web-services. Of interest to us was the introduction of Groovy scripting which makes it easier to write process extension within the Agile environment and made it optional to use the traditional 9.2 Java API using the SDK.
What are the best practices/guidelines to follow in preparation for a successful PLM implementation? To answer this question I have tried to pen down the important guidelines in the area of solution deployment, methodology, and team composition that are very critical for the successful PLM implementation.
There is a power provided by our friends at Oracle Agile in the shape of the Agile API originally accessible only through the Java SDK in 9.2, amped up in 9.3 by making it further accessible via Groovy scripting and web services. This power is quite awesome in that it gives you access to parts under the hood.