OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
N/A
Planview Hub
Score 8.3 out of 10
N/A
Planview Hub provides scalable, sophisticated near real-time integrations to help IT leaders and their teams eliminate inefficiencies.
N/A
Pricing
OpenText MBPM
Planview Hub
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
OpenText MBPM
Planview Hub
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
OpenText MBPM
Planview Hub
Features
OpenText MBPM
Planview Hub
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
OpenText MBPM
7.0
3 Ratings
11% below category average
Planview Hub
-
Ratings
Dashboards
7.93 Ratings
00 Ratings
Standard reports
9.02 Ratings
00 Ratings
Custom reports
4.03 Ratings
00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
OpenText MBPM
7.3
3 Ratings
13% below category average
Planview Hub
-
Ratings
Process designer
8.13 Ratings
00 Ratings
Process simulation
7.13 Ratings
00 Ratings
Business rules engine
9.02 Ratings
00 Ratings
SOA support
6.02 Ratings
00 Ratings
Process player
7.02 Ratings
00 Ratings
Support for modeling languages
8.02 Ratings
00 Ratings
Form builder
6.93 Ratings
00 Ratings
Model execution
6.13 Ratings
00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
OpenText MBPM
7.6
3 Ratings
9% below category average
Planview Hub
-
Ratings
Social collaboration tools
7.63 Ratings
00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
OpenText MBPM
6.0
2 Ratings
30% below category average
Planview Hub
-
Ratings
Content management
6.02 Ratings
00 Ratings
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Metastorm is well-suited for scenarios in which internal stress testing an application is needed in a hurry before showcasing it to potential customers. It supports different views of the process from Swimlane perspective, so different methodologies can be handled. It is an Enterprise level tool and handles both small and large projects quite well, although smaller companies may be stressed out by the amount of time it takes to properly maintain the application.
Planview TaskTop Hub is very well suited to implement the integrations to synchronise data such as requirement, task, bugs. We have very good experience with the integration between Jama and Jira as well as between two Jama instances. In the context test management, related to Test steps in a test case, it's quite complicated. Test Case synchronization between two Jama instances works with Steps. But we aren't able to implement the synchronisation of Test Cases including Steps to such Plugin of Jira like Xephyr.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
A great integration tool, which comes with a wide range of supported end tools. Planview TaskTop Hub works with an integration concept that maximizes the scalability and flexibility of integrations across more than just two tools. For example, from our experience, we started with the integration between Jama Connect and Jira. We were able to extend our integration concept to a new tool, Pro Cloud Server, by ourselves. The element was synced within 10 minutes.
We're hosting Planview TaskTop Hub by ourselves. The availability was good until now. A part of that, we have a strict plan for the quality control on any update of both Hub and End tools to avoid as much as possibily any disruptions.
Planview TaskTop Hub does generate traffic for some end tools. It is still in an acceptable range. For certain kind of retry to resolve issue in synchronizing relationships, an additional manual attention was required.
I was considering giving a rating between 9 and 10. Overall, the support has been very good so far. However, I have noticed that the members of the support team have varying levels of know-how about Planview TaskTop Hub. When a ticket about a complex technical issue reaches a member such as Christoph T., Sr. Customer Engineer, the analysis is done thoroughly, and a sustainable solution is provided. With other members of the support team, the experience might be different.
We had a very good collaboration with the enabling team from Tasktop in 2018. The enablement program was adequately structured, starting with building an integration concept based on use cases of the synchronized data. The training provided a good foundation for us to operate and maintain the tool. The tool administration and architecture were straightforward.
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.
Jira Align does not synch items outside of JIRA and Azure Dev Ops; TT Hub is specifically utilized to address connections to various other SDLC application.