Good PLM tool
February 02, 2019

Good PLM tool

Cristian Bodnarasec | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Oracle Agile PLM

Several departments in our company are using Oracle Agile PLM for its main purpose: product lifecycle management. It has allowed us to have a centralized place for product related information: properties (like the bill of materials), documentation, and setup ownership from each department involved. It improved the collaboration across internal teams, accelerated the products reviews and approvals, and improved the collaboration between internal teams and our suppliers
  • Product lifecycle management: the tool is fully configurable and it is easy to use and manage it as per project requirements.
  • Improves the engineering change processes: any change in the product can go through a more or less elaborate review/approval process
  • Helps improve the product quality system management: it is a great tool for our product quality department
  • Helps you be compliant with the ISO standards of your business
  • It gives you a clear picture of the project's status with nice dashboards
  • Complex tool that requires training for people to start using it first, then more training to use it at its full capabilities
  • The UI is not modern; it is not ugly or bad, but it could use some improvements
  • May grow to be slower as the database size increases with time
  • The implementation and rollout in the company took a long time due to our specific requirements
  • For us, Oracle Agile PLM did what we purchased it for: it streamlined our product lifecycle management
  • The unexpected thing was that it took 6 months from the start of the implementation to release.
  • The user adoption did not match our expectation: due to extensive training needs and the complexity of the tool, some users still don't use it
Oracle Agile PLM is well suited in a company that works with multiple complex products/projects where the change management has to be strictly defined and followed by all people involved, or products/projects that need approvals from different departments. It is not suited for a smaller company where fewer products are there and most likely the budget for software acquisitions is smaller or does not exist at all.