What is our primary use case?
I use MEGA HOPEX for everyday work.
I do a little bit of everything with MEGA HOPEX; I use it as an end user, but I also do development and integrations for the system, and I provide on-site support for other people who use the system.
I am primarily using MEGA HOPEX for controls and compliance. I fill out compliance-related items in the system, and if people need help making changes, I assist with that. I use the majority of the modules in MEGA HOPEX to a certain extent, either through testing new integrations or helping people utilize it.
We use process modeling extensively in MEGA HOPEX. In my employment, we are very reliant on the modeling capabilities of MEGA HOPEX because every single person who works at this bank uses the processes that we make through the modeling system. All of the instructions and process modeling are commonly used, helping ensure everything is done correctly and in an effective manner.
I am not completely sure how MEGA HOPEX supports compliance initiatives, but we use the compliance module. We use the control modules and compliance modules, and we ensure that everything runs properly.
What is most valuable?
The borderline architecture of MEGA HOPEX creates a very good overview of how all of the things in our organization fit together through these relations that you create between objects in the system. I think that's really powerful because it provides the means to do some very solid reporting.
When you have governance created in MEGA HOPEX, it makes it easier for everyone to be aligned. People have this one way of doing things, and if something is not working, then we change it to fit the current ruling governance so that everything is done effectively.
For the average user of MEGA HOPEX, I am one of two people doing all of the setup for the reporting. Since the reporting is so customizable, it's up to what each individual wants to report. It's very strong and versatile in terms of what you are able to report on inside of MEGA HOPEX. The customizability for displaying things specifically how anyone wants is very strong. However, generating the reports in MEGA HOPEX is pretty slow when you have a lot of data, which we have, so sometimes it could take upwards of 12 to 16 minutes to generate one of the report views, which is a downside.
What needs improvement?
The default dashboards in MEGA HOPEX are not actually utilized much. We customize the front pages for our needs, so we are not using the dashboard so much because we have the customized starting pages.
The searching functionality in MEGA HOPEX has gotten worse over the updates. They introduced more steps for finding the same things as before, which is not ideal. In terms of speed, that could be different depending on where you host and deploy your system, but sometimes it feels it could be faster, especially with the reporting.
Keeping the old search in MEGA HOPEX would be beneficial as it seemed to work fine. I'm not really understanding the decision making behind the new search because it doesn't seem to work effectively either. That might change in the future.
For how long have I used the solution?
I started using MEGA HOPEX when I was employed at my banking job, which has been a little over a year.
What do I think about the stability of the solution?
That's one of the aspects of MEGA HOPEX that I'm also partly responsible for. It runs stable in our case, but I suppose that depends on how adept you are at using the system. Generally, we don't experience much trouble with it at all.
What do I think about the scalability of the solution?
MEGA HOPEX has been quite scalable. There have been many new good additions to the system in terms of the updates and upgrades they are doing. The system in general, despite having a learning curve because there are so many different intertwined modules, is a very versatile and scalable system for any type of organization, whether big, small, or medium.
How are customer service and support?
I often just use the community site for MEGA HOPEX if I have questions about improvements and suggestions. We are not very involved with the support because we have people who can fix many of the issues internally, so we don't really have many issues yearly that we need to forward to MEGA support.
How would you rate customer service and support?
Which other solutions did I evaluate?
I have only used MEGA HOPEX, so my opinion would be biased. Despite having a learning curve and some hassles here and there, I genuinely think it's a good system, so I would give it an eight, maybe a seven.
What other advice do I have?
The documentation for MEGA HOPEX is pretty documented. All of the different modules and how you use it as an end user is documented, but in terms of the backend technical aspects, I would say it's pretty limited and many things you'll have to find out yourself.
Most people who have MEGA HOPEX system don't actually develop for it utilizing the system in the backend. Usually, people get this system to utilize the front end modeling that the system has, so I don't think that's necessarily important, and most of these things you would be able to find out yourself if you spend time with it.
On the development side of things with MEGA HOPEX, if you do custom things, it's very documented in terms of anything else such as the modules and how you use it front end-wise. How every object in the system connects and how you create new things and update things is pretty documented.
I rate MEGA HOPEX eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
