The initial setup was straightforward. With configuration, customizing or prepping the data and deployment, it took about one year to set up. We only needed two people to deploy and maintain the solution: one business architect and someone who specializes in customization and operations.
What's most valuable in MEGA HOPEX is that it follows the reference model where each component is defined.
I also like the diagram consistency in MEGA HOPEX.
The main feature I find crucial in MEGA HOPEX is the catalog view, which provides a comprehensive visualization of all artifacts in one repository. Another valuable aspect is the availability of out-of-the-box outcomes, such as strategy maps and BPA models, eliminating the need for additional configuration.
MEGA HOPEX allows users to focus on specific business areas, like risk management or data governance, providing a high-level overview while enabling deep dives into specific areas of interest. For risk management, MEGA HOPEX allows users to assess impacts, create recovery plans, and track action plans.
They do tend to push people to their professional services, instead of helping the customers with their problems. I understand this is their business. At the same time, however, they need to work on fact sheets or offer some program to help the customers who want to implement it themselves and to make it run properly in their environment.
An area for improvement in MEGA HOPEX is its vast learning curve. The tool is also heavy, so that's a pain point. MEGA HOPEX is also tricky to use if you don't train for many hours.
In my experience, I've encountered difficulties with consuming custom packages in MEGA HOPEX, which leads to redundant work when deploying them to production. This is an area where improvement is needed. While version six offers better UI and UX, resolving this issue should be a priority. I believe it's important to fully explore MEGA HOPEX's capabilities before suggesting new ones.
