MEGA HOPEX Reviews

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.

HOPEX creates a database of applications, technologies, and platforms. We integrate the solution with the entire enterprise to manage our architectural components. We currently have around 300 users, but we are moving away from HOPEX. 

The most valuable feature is the completeness of HOPEX's meta-model. It's a strong meta-model that's rigid but comprehensive. It's a logical fit for our understanding of how we want things modeled in our database.

It takes a long time to learn how to use HOPEX. It's hard to work with it because the user interface is bad. For example, if you want to build a complex system diagram, you need a lot of knowledge to do this correctly and make it readable. In MEGA, you need to create a report and it takes a long time to publish it. The publishing is offline. With RDoC, everything is online.

I have been using HOPEX for 10 years.

HOPEX is normally stable, but operations like reporting are too slow. 

You can scale up HOPEX with no problem. We have about 3,000 applications and many components.

I rate MEGA support eight out of 10. 

Positive

Setting up HOPEX is complex. We need two or three guys to run it and support the user base.

We do our training in-house with support from MEGA.

We are switching to RDoC, which has a much better user interface. It will allow us to expand our staff members' knowledge and increase the value of enterprise architecture. It will enable business users to discuss the architecture with us better.

I rate MEGA HOPEX seven out of 10. It's too complex for users who lack experience with enterprise architecture. This is a tool for experts with advanced knowledge already. You need to know what you want to do it. It's better to start with another tool.

I use MEGA HOPEX for enterprise architecture and risk management.

MEGA HOPEX helps me to see the benefits of different solutions in terms of the entire ecosystem I have, by providing different integrations and overseeing the entire system.

MEGA HOPEX integrates different systems well and helps in overseeing everything.

There is still room for improvement in MEGA HOPEX in my field of work. Some aspects are not working efficiently.

Scalability is generally good, but it may pose challenges.

Customer service is rated as very good with a score of ten out of ten.

Positive

The return on investment is good. However, there isn't any specific metrics mentioned.

MEGA HOPEX is perceived as somewhat expensive.

I would rate MEGA HOPEX a nine out of ten.

The first use case pertains to the certificate price domain. Secondly, we use it for enterprise reporting. Governance is one of the key areas.

The solution lacks additional models compared to other tools.

I have been using MEGA HOPEX for four years.

Setting up MEGA HOPEX requires a substantial budget allocation to ensure its functionality and effectiveness.

We are currently in the process of evaluating whether we should collaborate with MEGA or opt for another product. We are planning to utilize this tool for external purposes.

We are in the phase of avoiding redundancy and exploring its potential use cases. Primarily, we use it for business and application portfolio management, which is crucial for our operations. We're assessing our assets. We have another tool for asset management and are considering replacing it with MEGA.

We focus on transitioning towards a product-centric approach. Thus, all our business operations are aligned accordingly.

We can handle MEGA HOPEX. It's one of the best tools available. Another advantage is its accessibility; with MEGA HOPEX, We can use it anywhere. You can use BIN, PCE, Centograft, and more. MEGA HOPEX has its own proprietary standards that users must adhere to.

An additional model offers a constructive and guided approach to implementation. When dealing with an open-world scenario, convincing people can be challenging. Having a predefined model helps stakeholders understand the standards being followed. Alphabet or MEGA both fall under SysTrack. One of the best features of Abacus is the ability to select multiple models, which is essential when dealing with different business needs. It's important to recognize that one solution does not fit all requirements, so understanding how your specific requirements fit into the models is crucial.

I recommend MEGA HOPEX if the business context is straightforward and clear. Its stability depends on the audience you're interacting with and their technical or ER tool proficiency. If your audience isn’t tech-savvy, explaining MEGA HOPEX can be challenging.

Overall, I rate the solution a nine out of ten.

MEGA HOPEX is the tool of my customer, an energy and facilities company.

The tool is used for application modeling and application data exchange purposes. MEGA HOPEX is also used to classify applications by the business capability for anthology purposes. It's an application and data flow tool.

The reference model in MEGA HOPEX has benefited my customer working in nuclear plants.

What's most valuable in MEGA HOPEX is that it follows the reference model where each component is defined. When you put the component on the diagram, it shows you all semantic definitions, including the flags, data flow, interface, etc. 

I also like the diagram consistency in MEGA HOPEX.

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.

As a holistic tool, it's supposed to do everything, so everything's connected. For example, your application is connected to data, so your screen is full of information, which works when you have many people working on your information system using MEGA HOPEX. For example, my customer that works with nuclear plants is a big organization. However, the tool would be too complex for a functional organization or a small organization such as in the HR or Financial niche because not as many people work on the information system and the tool.

"HOPEX" in MEGA HOPEX stands for Holistic Platform of Excellence, so you can do everything and describe everything, but the tool is too complex for small business users.

I also found the modeling tool of ARIS better than the modeling tool of MEGA HOPEX.

I rate the tool six on a scale of one to ten because of its complexity.

I've been using MEGA HOPEX for one year.

MEGA HOPEX is a very stable tool, so it's a nine out of ten.

MEGA HOPEX is very scalable, so it's an eight out of ten.

I only used MEGA HOPEX. It's the only enterprise architecture tool I have experience with.

My customer has a special team dedicated to MEGA HOPEX implementation, so implementing it is no issue.

I've been told that MEGA HOPEX is very expensive, which is why small organizations dismiss the tool. It's complex and costly versus other simpler and cheaper solutions.

I'm a consultant and architect, so I'm using an architecture product called MEGA HOPEX.

MEGA HOPEX is deployed on-premises. The customer wanted to deploy it on the cloud but had to stick to an on-premise deployment because of sovereignty.

I'd recommend the tool for people with very critical use cases. Otherwise, you'll find more straightforward tools than MEGA HOPEX.

We are using MEGA HOPEX for process modeling, such as modeling IT tasks.

 We have a private server and the client also has their own server. 

The most valuable feature of MEGA HOPEX is the publication method for static websites. You can generate the whole database into a static website. Additionally, in the new tabular entry, you don't have to put objects or links, you can go and fill a tab and the MEGA HOPEX will generate an object for you in a simple way.

I have been using MEGA HOPEX for approximately four years.

MEGA HOPEX is stable.

The scalability of MEGA HOPEX is good.

We have three users using this solution in my company.

The support from MEGA HOPEX is good, they are quick to respond.

MEGA HOPEX's initial setup could be easier. The newer version is better but they still need to improve the process. The deployment took approximately four to eight hours.

I rate the setup of MEGA HOPEX a four out of five.

The price of the MEGA HOPEX license could improve, it is expensive. The license key for business process analysis and IT architecture is approximately €10,000. This price is fixed, it's not a subscription or cloud-based version. It is a one-time price.

My advice to others is they should check the other solution because the price will be the most important for every company and the price of MEGA HOPEX is high. This is a disadvantage compared to other solutions. However, the solution works very well.

I rate MEGA HOPEX a nine out of ten.

HOPEX has different modules. The one we use the most is the IT infrastructure module for process management. One guy on my team is in charge of this component, whereas I am the solution architect. I think there are at least three or four modules.

If a client wants to integrate an app with the HOPEX console, they need to pay MEGA for that service, and it's expensive. We offer that integration to clients as a service because we know how to integrate and reassess the cost.

HOPEX has a panel that offers various views. I think that is very good. MEGA has an app for integrating with a lot of apps. We help our clients integrate HOPEX with a different product like Apple Gateway, for example. I've been with the company for 15 years, and we connect with everything. Our clientele includes almost all of the banks in Mexico.

We have a very close relationship with MEGA representatives in Mexico, and we ask them why they don't offer impact analysis. For example, we have a server in the center and provide the client a view of what's in the peripheral area, like one cluster, application, process area, and services. We want to offer our clients that level of visibility with HOPEX.

I've been using HOPEX for around four years. The first tool that we acquired was Casewise around six or seven years ago. We started using MEGA four years ago. My company is a global bank that operates in Spain, Mexico, and the United States. 

I rate MEGA HOPEX eight out of 10. 

We are using the solution in one bank in Colombia. We are going to start implementation in two financial entities in Ecuador.

The support experience in Latin America is great. For us, it's very important to have local connections and use cases. MEGA has had a lot of partners in Latin America. It's the differentiation with the other companies. Many others use services outside of Latin America - in Europe or the USA. However, we like the local connection, which was the main selling point for us.

We need better traceability available. We want to have traceability between the business and the technology.

The initial setup can be quite complex at first.

The resolution needs to offer more potential for collaboration. Right now, it is much more geared towards one person working on the solution.

We have one year of experience using that tool.

We are managing the implementation via corporate and governance. We are going to scale all of the entities in the group. We are a financial group that has a presence in different countries in Latin America with different entities and we decided to manage this implementation in an incremental model starting from some specific companies. The plan is, in 2022, to integrate all the other entities in the group.

So far, we have less than 20 people using the product, however, we are going to increase the number of personnel.

Technical support is great. they are local and readily available. We like that they are so close, and we don't have to deal with support from the USA or Europe, which is much further away.

In the beginning, there was some complexity. We don't understand the benefit and the use of the tool. We defined a robot for business capabilities to be covered across all of the companies in the group. We are solving for the original lack of knowledge with a training process in the consulting services we have on offer.

We implement the solution with a partner and they have less than three people that help us. To use the tool, we need the technical staff to use the solution. 

We leveraged the expertise of local partners while initially implementing the solution. 

We pay a yearly licensing fee.

We have a standard fee for the use of the solution via their SaaS model and we have some consulting costs that depend on the scope of its implementation in each entity.

We have an agreement, a commercial agreement with MEGA, to support all the entities that are going to implement the solution.

We are a financial and insurance services industry company. We are focused on banks and insurance.

For new users, it's important that they understand the business architectural definitions and have knowledge of processes to gain the most value out of the solution. If the team that is evaluating the solution doesn't have such knowledge, there might be issues.

I would rate the solution at an eight out of ten.

What I find the most valuable is the process workflow. It is really good. 

The fact that you can decompose is also valuable, as is the file D structure. Also, the fact that you can have your own logical repository structure and you can drag and drop is very valuable. This is largely because of its intuitiveness. 

Once you understand the logic behind the tool, MEGA HOPEX is quite intuitive. I also like the ability to create custom reports. I like the fact that you can share repository content via web to other end users who are not architects.

Of course, there is always room for improvement. There should be an integration with the Microsoft Office platform, for instance. I can compare it to a tool like Orbus. In Orbus, there is already an integration with Microsoft. So, if I already have network diagrams already built in a Microsoft solution, I can bring it into Orbus. I can actually pull a number of the building blocks. I can map parts of the diagrams into the inventory. That is a very, very good feature. 

MEGA HOPEX could also definitely have a lower price. 

I used MEGA HOPEX for about three to four years.

MEGA HOPEX's technical support is fantastic. If it's paid for, it's fantastic. They have very knowledgeable engineers and support practitioners, especially considering that the tool has been around for quite some time. 

MEGA HOPEX also has extensive documentation. So quite a number of issues can be resolved just by looking through the documentation. For more complex things, you probably will need their support. They also provide support for metamodel customizations and that is equally good as well. 

The initial setup is very easy, but it depends on type of deployment you want to do, whether it is standalone or otherwise. They have a file place database structure that they use and integrations for Oracle and Microsoft SQL servers. 

The deployment guides are very good. You can just pick up any of the deployment guides. Once you have the license, just follow through and run the installation. The installation on both platforms is quite straightforward.

The price of MEGA HOPEX is too high. MEGA HOPEX's problem is that it is expensive, but it's a fantastic tool.

My advice is that if you have the budget for it, MEGA HOPEX is a fantastic tool. It will especially help you if you are heavily focused on process architecture. MEGA HOPEX maps your org structure and you can use that to build in your processes and then just directly house your processes into the org structure. This is just a fantastic workflow in terms of the engineering and the thinking behind its structure. The pricing is an issue, however. MEGA HOPEX could be more affordable. They could also create some form of community-based addition to allow a wider audience access and play around with the tool. I think this would be a welcome development.

We picked it as we wanted something that included all of the shapes represented in the software architecture solutions of our company. We created near 2,000 products that we have in the company. We used this product to represent the software architecture of our solutions and the mapping within the processes of the company.

We tried to map a set of fields and we have and combined it with the processes of the company.

The main feature that we like the most is the ability to have a unique repository where all the architects can interact and play together with the shapes of different architecture solutions. They have a unified repository where users can share the developments they're working on. 

Its availability is very good. 

We've had some internal changes in the company. It allows us to start with an initiative that will accumulate new architecture solutions. At this moment, the initiative works with specifically with HOPEX and we are able to adapt it to our new company direction.

I can't speak to which features are missing. I don't have any information on that and don't really have any input.

The solution is quite expensive.

We've been using the solution since before the pandemic. We started using it around 2019.

We use Sparx Systems as well as MEGA HOPEX. Our organization bought both solutions.

I found that the solution is very expensive for what it does. We are integrated with both HOPEX and Sparx solutions, however, Sparx Systems we work with on a set of licenses that we had previously, in 2018. We find it a bit less expensive.

Since we use both HOPEX and Sparx, it's easy to compare the two. 

For example, if you compare the price of MEGA HOPEX with Sparx Systems Enterprise Architect, Sparx is cheaper. Our company is looking at pricing and it's an important factor we are taking into account. However, Sparx can be a bit slow. If you are trying to design software architecture, sometimes we run into issues and need to refresh. HOPEX also occasionally needs to be refreshed as well, actually.

We find Sparx to be more useable as well.

We are customers and end-users. We don't have a business relationship with the company.

I'd rate the solution at a seven out of ten. If the architecture was a bit better, I might rate it higher.