MEGA HOPEX Reviews

I have experience with ARIS and MEGA HOPEX. For ARIS BPA, I work as a consultant and integrator, which is a reseller. In Morocco, I work with government entities such as Tamweelcom and some financial entities. For MEGA HOPEX, I work as an administrator, specifically as a MEGA HOPEX administrator at Daman Insurance in UAE.

The primary use cases for MEGA HOPEX include business process modeling. I work on customization, and because the project is still new, we are aligning the tool with the company's needs. We work on multiple levels, primarily conducting trainings for the teams and supporting them with using the tool, which is not as user-friendly as ARIS. I focus on user experience and customer journey mapping, along with architecture mapping for a new value chain that we are working on.

MEGA HOPEX has extensive modeling capabilities and can be modeled in different ways. While it is not very user-friendly and is somewhat outdated, the web portal is good. However, I need to manage the Windows client, which is older compared to tools I have used in the past. Overall, it is good.

We are building our own reports in MEGA HOPEX by creating templates and configuring content depending on non-out-of-the-box features. The querying tool is good. However, reporting, such as RTF reports, is not that good because sometimes the templates do not match the outcome and alignment. For instance, if I change the template, font, and spacing, those changes do not reflect on the report generated from the front end or the application.

As an administrator, I would improve MEGA HOPEX by adding a WYSIWYG feature for building reports, which would be very helpful. Additionally, I would want reporting customization from the front end web application, not only from the Windows app, which is the customizer. If all changes could be made in the web application, that would be beneficial because every time we need to request access to the server, it takes time in large organizations and involves multiple levels of approvals from cybersecurity and IT security, which can block the project.

Regarding dashboards in MEGA HOPEX, they could definitely be better. Having something similar to ARIS would make it easier to build dashboards, providing a what-you-see-is-what-you-get experience, allowing me to drag and drop elements, configure them, and test queries. Moreover, RFQL language is not common, so in MEGA HOPEX, I need to learn RFQL querying.

In terms of additional features for MEGA HOPEX, I would appreciate more features for workflows. There are limitations in customizing the email notifications sent during workflows. When creating a workflow, I can configure actions and customize the text, but not the header and footer. Therefore, all emails from the tool come with a MEGA HOPEX header. In large organizations like BPM COE, we want to have our own logo, header, and footer in those emails, but this is not configurable, which I find limiting. I would appreciate easier features to customize workflows and create workflows.

I have been using MEGA HOPEX for one year.

Regarding technical support for MEGA HOPEX, we do not have direct contact with MEGA. We have a contractor named DNA, who is our primary contact. In our AMC, we need to contact them first for first-level support, and if they cannot respond or do not have a fix, they escalate it to HOPEX. To be honest, it is not the best support that I have seen in my career.

Technical support is not done directly by MEGA.

Neutral

ARIS has advantages over MEGA HOPEX because it is more user-friendly. It is easier to use and intuitive, requiring less reading of documents and searching for support. Additionally, accessing information is a limitation of MEGA HOPEX because if I am not working for a company that has purchased HOPEX and I do not have a company email, I cannot access the documentation or the community. Unlike ARIS, which has ARIS University that allows anyone a month of free access to the tool, making training easier.

I have experience with these products. I actually use the product and served as an architect for all the companies where we have integrated the tool.

I did this for both ARIS Cloud and ARIS BPA, but our clients at the time did not purchase additional modules such as ARIS Process Governance; they primarily used ARIS Cloud and an on-premise solution.

ARIS BPA was used. The clients are not using either RPA or Process Mining by Software AG, which shows the maturity is not that advanced.

My overall rating for this product is 7.

I have a role as a technical and functional administrator. My duties began in 2016 with the implementation of the MEGA platform, including installing the software and managing the administration of the platform. I also have a second role, which focuses on establishing the NITA model. 

This model involves injecting various concepts across different layers of the enterprise, such as the business layer, cloud, application layer, technology layer, and fax server layer. I have designed and executed these concepts within the MEGA platform.

In my technical role, I am responsible for customizing the metamodel to align with the current and future needs of different business lines. 

Additionally, I support various users in their use of the platform.

We follow a traditional work pattern for risk management, mapping risks in a manner we refer to as "occupy" in our terminology. It involves detailing the types of risks, technology, and so on.

The strength of MEGA HOPEX lies in its ability to customize the metamodel. This flexibility allows us to accommodate and update the platform in response to changes in the business, ensuring that the output meets the business's requirements.

So, the customization of the metamodel is the real advantage of this product.

The application diagram still doesn't update smoothly. We often have to spend considerable time manually updating them. Ideally, I would like to see a feature where information text, so it could be automatically updated in the data without needing manual intervention.

I think the digital transformation process needs to be reworked. It should allow users to see and account for this movement from the beginning and start with best practices. 

Another thing is that I believe this digital transformation should be reworked. This would allow users to see and consider this movement from the very beginning and implement it and start as a best practice. And, with use cases to help customers see the value of the digital transformation movement.

I have more than seven years of experience with this product.

It's generally stable, though we've encountered some minor annoying issues. However, these didn't cause significant incidents in the production environment. When we did have issues, we contacted MEGA support, and they sent us a mini-patch software. Once we applied the patch, the environment was back in line. 

Overall, I believe the solution is well-designed. For example, the database is on different servers, and with virtualization machine technology, we have a good environment. We haven’t seen any critical issues.

The solution is very stable.

We have the metamodel from the proof of concept, but it’s not too far off from the final version of HOPEX. Afterward, we made some changes. 

For example, when we worked with the depth of various applications, we had user requirements to make the process more detailed and precise. So, we customized the metamodel to allow more detailed processes and work with the full suite of solutions for different applications. This customization helped us gather more metadata during the process.

I should point out that we don't have many users challenging the platform. We have two architects responsible for updating the repository, myself as the administrator, and users generally don’t access the system directly. 

It's a small modular platform, and if external personnel need to work on it, we only have five licenses available.

I found it responsive and very adaptable, especially from a technical perspective. The community is there, but I've found valuable information there as well. Overall, it’s been very satisfactory for our case.

I find it good. We actually aspire to work closely with the support.

Positive

I have experience with SAP PowerDesigner, particularly dealing with the data layer. This might be the weakest point for MEGA HOPEX because when it comes to project design, we need the data formation. So we use SAP PowerDesigner to generate models like conceptual data models or logical data models. It allows us to perform virtual data engineering by directly accessing physical databases. However, for fast use cases, this is not possible with MEGA HOPEX.

MEGA HOPEX is advantageous in areas other than fine-grained data design. If we are focused solely on the processes, MEGA HOPEX is also good. However, our organization has many years of experience with PowerDesigner, especially in data hubs and reporting. We find ourselves needing to maintain the same quality of service, but we didn’t find the same level of service in MEGA HOPEX as we had with PowerDesigner.

There were some technical challenges. The person who handles the installation should have database administration skills, which I have. Otherwise, the process could be more difficult, and the customer might need to call in MEGA experts for assistance.

We still use the on-premises solution. We haven't yet moved to the cloud. We use version 4.2.

1. For deployment, we started by setting up two different environments: one for development and testing, and another for operations. 
2. After achieving the proof of concept with the support of MEGA experts, we began our first project with a core business line. 
3. Once that was successful, we moved the project to the operations environment. We then followed up with other projects as needed, starting in the test and development environment before moving them to operations. 
4. We continue to handle different projects this way, progressing from testing to the operational environment.

The first project, which was the proof of concept, the deployment took about six months. However, there was a phase before the setup involving the design of the metamodel and different concepts for the employee system. We needed to design a map for the projects, which took about two months. Then, the entire product took six months, including the first phase of defining and designing the metamodel.

A concrete benefit, especially for new products, is the real value when documentation is needed. The users don't have to search for all the information since much of it is already within HOPEX. 

I'm referring to different application processes. For instance, when solving a particular issue, everything is often already documented. This is especially beneficial when dealing with external stakeholders or when there are changes in external applications. So, it's helpful in dealing with the entire information system.

As a proprietary solution for a mid-sized to large company, I would recommend MEGA HOPEX to other users. I think it’s still the leader in the field. Despite the data layer needing some rework to satisfy user needs, particularly when it comes to reporting and data accuracy, I would recommend it.

Overall, I would rate it a nine out of ten. 

I set up the tool to connect to some databases and use it to build a data catalog and a CMDB, a component database with all elements, physical and virtual, that are part of the technology component in the organization. 

Also, I am beginning to learn and put MegaHOPEX into work by starting some sessions to understand the capabilities related to data governance.

As a data governance leader, I am looking to understand the capabilities of Mega for data governance, such as data awareness, business glossary, data catalog, and some business rules or management. 

I have observed MegaHOPEX has capabilities in architecture and other areas, although it does not feature prominently in market research from companies like Gartner or Forrester.

MegaHOPEX lacks comprehensive features that a governance tool should have, particularly in data governance. 

Furthermore, I have doubts about how risk management and other modules are connected to work together efficiently.

I have used MegaHOPEX for between six months and one year.

I have no experience with MegaHOPEX's customer service, so I cannot rate them at the moment. However, I assume there is some support service available through a service desk or documentation.

Previously, I worked with Microsoft Purview to connect to databases and try to create data lineage and a data catalog.

I am not aware of how easy or difficult the initial setup was. I joined the organization recently and have yet to gain full access to the tool.

There is a hope to acquire additional capabilities for the employees to make the best use of MegaHOPEX as the team advances in learning to use the tool efficiently.

The organization uses Microsoft Purview for some related tasks, although it seems not to meet all the requirements for a full data governance tool.

On a scale from one to ten, I would rate MegaHOPEX a seven. 

I have not seen all the capabilities it offers, and there are doubts about its comprehensive integration, particularly regarding risk management and other modules.

Our primary use case for this solution is as an enterprise architecture tool. From a management perspective, we have specific use cases for modeling business processes.

The most valuable feature is the ability to view the entire architecture of an enterprise, company, or organization within the tool. We can load the architecture onto the tool and gain a holistic view.

We have been using MEGA HOPEX for 4 months.

The platform is stable.

We have less than ten MEGA HOPEX users in our organization.

We used other solutions before. We switched to MEGA HOPEX because it helps discover assets on the network, such as software applications or servers running those applications.

We didn't face any challenges during the setup process. We also procured configuration services, and the team assisting us has been actively helping us throughout the process.

A third-party consultancy handled the deployment as part of their cloud offering.

The pricing depends on the number of licenses purchased. Typically, the more licenses you buy, the lower the cost per license. However, exact pricing details may vary depending on customers' specific requirements.

MEGA has supported our IT portfolio management 100%. They have a portfolio management module where we load our application assets onto the tool.

It has a data domain where we load our data objects onto the tool but doesn't provide data governance capabilities such as cleansing or validating data. We ensure that the information we input is clean and accurate.

With these compliance management features, we've primarily focused on business architecture. We have yet to explore the GRC capabilities fully, as we only started in January. We'll begin exploring other capabilities once we document the business and application domains. Risk management is also an ongoing process, and we plan to utilize more robust features in the future.

To utilize MEGA effectively, you need to understand your architecture and be able to complete the templates. There are two ways to upload information: via templates or manual upload. You must know your way around the templates and understand what artifacts to upload onto the tool. Once you're comfortable with that, the process becomes easier.

I rate it a nine out of ten.

We implement MEGA HOPEX primarily for better visualization of enterprise architecture artifacts and generating reports for clients to maintain governance and work on enterprise development. MEGA HOPEX is used for IT portfolio management, strategy mapping, project portfolio analysis, and business capability assessments.

Personally, I focus more on implementing MEGA HOPEX rather than the functional side, but I've worked with clients who use it to plan future capabilities and compare them with current ones.

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.

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.

I've been using MEGA HOPEX as a technical consultant for about a year now.

As for stability, MEGA HOPEX itself is generally stable, but occasional errors may occur due to client-side changes. Despite these instances, I'd rate the solution's stability at 9 out of 10.

The scalability of MEGA HOPEX, in my opinion, falls around 8 out of 10. Before implementing MEGA for our customers, we conduct multiple sessions to understand their specific needs and focus areas. 

I find the process relatively straightforward. The documentation is clear, and following the steps usually leads to a successful installation. I'd rate the difficulty level around 7 to 8.The deployment time varies depending on customer instructions and IT team responsiveness, but it's generally manageable within one hour. The deployment process involves downloading instructions, configuring the application server, installing MEGA, setting up the database, and launching the application. Some customers prefer using DNS names instead of IP addresses, requiring additional steps for certificate creation and DNS configuration.

I would highly recommend MEGA HOPEX to others. It's a powerful tool with excellent technical support and a wide range of features to meet diverse business needs. Overall, I rate it as 9 out of 10 and believe it's a valuable solution for enterprise architecture and IT portfolio management.

We use MEGA HOPEX to conduct a comprehensive executive business analysis, including data governance. These features are categorized into various profiles. We are effectively utilizing features within these profiles due to the complexity of our organization. The primary features used are data governance, information management, solution architecture, and overall enterprise architecture capabilities.

We can generate licensing reports for the directly to the desktop. It can run queries directly using the data we provide and make it a system for making decisions.

An organization needs to be at a certain maturity level and have a certain data capacity to be able to have its influence. Integrating any EA product takes two to three years. Earlier, it took up to five years to fully integrate a product into an organization. We're currently building compliance policies around MEGA HOPEX.

We're implementing fundamental features such as a centralized repository for applications and technologies and the ability to access reports from all the data. These are the foundational aspects of the system's operation.

When transitioning to this process, it's crucial also to understand your data. This understanding will likely yield significant benefits. The aspect may become irrelevant in a few months as you complete our data work and move on to other areas, such as optimizing workflow understanding. This dynamic nature is something to consider. MEGA HOPEX currently suits our environment best, offering features like executive engagement that we find valuable and can utilize whenever needed.

People should have more training about the product. It's a very versatile product. It can be complicated for an average user to use. People with several years of experience working with these tools know how to navigate it. However, it can be overwhelming for a new user.

The training materials and learning process need improvement. The product is quite robust. There is no fault related to internal functions and capabilities.

The solution needs a clearer licensing model and a transparent method to understand where the licenses are held. Licenses are initially assigned to to people, making tracing difficult. If you require 50 concurrent users across an organization of 1000, you need to pinpoint and maintain who uses them. It becomes very challenging without that internal capability.

I have been using MEGA HOPEX for more than 12 months. We have updated to V6 of the solution.

Everything else is very stable, capable, and scalable. The solution can be complex, depending on the user experience and training.

MEGA HOPEX is a cloud solution. It's scalability is correspondingly appropriate.

Customer support is fantastic. They are very helpful whenever we get on the line with the support team.

Positive

I have used several, each behaves differently. 

MEGA HOPEX holds and manages EA-level information and facilitates governance. It can directly incorporate the XMI/XML format into its structure.

MEGA HOPEX excels in EA management, dashboarding, and overall governance tasks. However, more hands-on work, such as project management or solution architecture support, might be too cumbersome and slow. In such cases, another solution may be more suitable.

The initial setup is straightforward.

MEGA HOPEX simplifies tasks once we reach a critical information threshold necessary to support our work.

The solution is expensive. Our organization is very small but has the complex needs that this solution fits.

MEGA HOPEX accomplishes nothing without a well-organized structure to support it. MEGA HOPEX becomes significant in the long term as an organization matures.

Overall, I rate the solution a highly, in the 8/10 range.

We use the tool for application portfolio management, demand cycle management, and technology lifecycle management.

I find the process modeling and value chain features valuable. The application portfolio management functionality and workflow management capabilities are also nice. It provides a holistic view for stakeholders and helps align IT with business strategies. It facilitates collaboration across the organization and covers all domains, including business, applications, technology, and data.

The tool needs to have a viewer portal. Currently, we have to use a custom solution to display information, which requires additional effort and tracking of data on a daily basis. Having a built-in viewer dashboard portal would be beneficial.

I have been using the product for one and a half years. 

The tool is mostly stable. We faced issues due to the changes. I rate it a seven out of ten. 

I rate the product's scalability a nine out of ten. 

We seek support through the partner, and it is good.

The solution's setup is complex. Configuring and maintaining the code requires significant effort, as it often needs customization to align with user requirements. As a client, we worked in the test environment set up by the partner, and once everything was validated, we moved to production.

The partner did MEGA HOPEX's deployment. 

MEGA HOPEX's licensing costs are yearly. 

I rate the overall product a seven out of ten. You need a skilled partner to maintain it. 

The solution can be used to model customer journeys and business processes.

I use the solution for my customers to model banking products. I also model and define business capability.

The biggest value of the product is that we can use it to work in different industries like government, education, and banking. The tool is very simple and intuitive to use. It is easy to manage different layers within the solution.

The product must improve integration with other tools.

I have been using the solution for almost seven years.

I rate the tool’s stability a seven out of ten.

I rate the tool’s scalability a seven out of ten.

I have worked with LeanIX. I switched to MEGA HOPEX because it has more features than other tools.

The initial setup was moderately easy.

I deploy the tool myself on-premise. I got help from the product’s technical support team to deploy it on the cloud.

MEGA HOPEX has produced a good ROI for our company.

The tool is relatively expensive. However, it is worth the money for the features it provides.

I recommend the solution 100%. Overall, I rate the product an eight out of ten.

The ability to customize is valuable.

The interface must be improved. The tool is not user-friendly. We have to do a lot of workarounds to get a benefit out of it.

I have been using the solution for around five years.

I rate the solution’s stability a seven out of ten.

The solution is scalable, but it has some limitations. I rate the scalability a seven out of ten. We have ten users, including five dedicated users. The core team of five people uses the product daily. The others use it once a month.

We use different solutions for different domains, but we are planning to migrate. We use ARIS for business process modeling.

The initial setup is not difficult. It is easy to install and set up the workspace. The deployment took one week.

The implementation was done through a reseller. We need only one technical resource to install and run the tool. However, we need a team of five people to make the product useful.

The product has a high cost. I rate the pricing a nine out of ten. The solution costs us AED 450,000 yearly.

I'm a digital transformation advisor. I sell consulting services to my customers. One of my customers uses MEGA HOPEX. The product needs a lot of customization and workaround. I would recommend the product to others. Overall, I rate the product a seven out of ten.

I used the tool enterprise architectural tool. I used it for my master's degree, my master's thesis.

I searched for the typical applications and their connections.

The product was briefly used. It had a lot of good, simple, common features.

Its initial setup was simple. 

The solution itself was easy to use. 

It works very well. It is robust and great for sizable companies. 

It is stable.

I cannot recall coming across any missing features.

I've been using the solution for four years. 

It was stable and reliable. I'd rate its stability nine out of ten. There are no bugs or glitches. It doesn't crash or freeze. 

My understanding is that it can scale. However, I did not attempt to scale the solution. I briefly used it. 

I never had to contact technical support.

I've also used ARIS in the past. HOPEX was the first architectural tool for me. 

The initial setup was very straightforward. It was very easy to deploy. There isn't much of an installation. I simply had to log in and start using it. 

I did not deal with the licensing. I had free usage.

We are using the latest version of the solution. 

I'd recommend the solution to others, specifically bigger companies. It's a very robust tool. HOPEX can handle big projects.

I'd rate the solution eight out of ten overall.