Puting AMX BPM into perspective
November 01, 2017

Puting AMX BPM into perspective

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO ActiveMatrix BPM

We use AMX BPM for an audit system, where the work items represent one single client and it progresses to multiple stages, gets escalated to managers for approval and gets back and forth to the user until it gets completed.
  • Assign work items to set of users. You can assign work to users based on the groups they belong to in the org model or by their position.
  • Manage user access and privileges, each set of users can perform a set of tasks based on their privileges and we can also restrict the actions for each level of users.
  • Escalating work items: A user can escalate a work item to a senior user and the matter can be progressed to another level or get closed straight away. The life cycle of work items is stored in the database where it gets reflected in Spotfire reports.
  • One of the challenges we faced with AMX BPM is the way the data is kept and it is hard to troubleshoot when a work items goes into halted state. Either there should be better documentation of what is under the hood or simplify the way work items data are stored.
  • Assigning privileges to system action where multiple organization models are used, seems to create ambiguity, as per the manual: "If different privileges are assigned to the same system action at different levels in the organization model, each level is checked when determining whether a user has the necessary privilege to be able to perform a particular system action. If the lowest level has no required privileges assigned, the parent entity is checked, and so on up the organization model hierarchy to the default, system-wide value."
  • It is cumbersome to add the same system action in all org models even though it won't be used everywhere.
  • When AMX BPM integrates with other products such as AMX BusinessWork, there should be a better way for the work items to handle broken communication. Data recovery seems to be an issue.
  • Overall with the issues we are having with AMX BPM and managing the TIBCO platforms, it has undermined the cost benefits of the application.
  • On a positive note, using AMX BPM has enabled the organization to move from a paper based system to a digital solution
  • Since we using a suite of TIBCO products, the cost to acquire products has been less phenomenal compared to other products on the market.
For BPM we looked at some IBM products suites, BPM Online, Oracle products and Pega Systems. The decision to go with AMX BPM was based on the evaluation by the software architect team and the cost of acquiring the TIBCO suites.
When a work item requires involvement from multiple people and escalation it works well.

TIBCO® BPM Enterprise Feature Ratings

Process designer
Not Rated
Process simulation
Not Rated
Business rules engine
Not Rated
SOA support
Not Rated
Process player
Not Rated
Support for modeling languages
7
Form builder
7
Model execution
6
Social collaboration tools
8
Dashboards
Not Rated
Standard reports
Not Rated
Custom reports
Not Rated
Content management
6