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.
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.
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.
The modules that we use are MEGA Process and MEGA Architecture.
This is a complete package with all of the functionality that we need.
The user interface for the version that we are using is not modern.
This is a complex product. For me, all of the functionality in this product exists, but it is not well explained. Better documentation and training would be helpful.
It was very difficult to adapt MEGA to our way of working. You have to spend 40% of the time thinking about how you will implement and use the MEGA concept.
I have been working with MEGA HOPEX for 10 years.
We have had some issues with stability but they are related to Citrix, and not due to MEGA.
I have not been in contact with technical support.
My company also uses Planview, but not the part that is dealing with architecture.
We have an internal support team and when we have a problem, we contact them.
My advice to anybody who is considering MEGA HOPEX is that it's a complete solution. All of the functionality is implemented. However, it is a complex product. Somebody who wants to use it should understand all of the functionality, but select only 20% of the concepts and use them very well. It's not necessary to use the full functionality and we spent too much time on the gain we received.
I would rate this solution a seven out of ten.
MEGA HOPEX is an EA platform used to implement different use cases like application rationalization, IT portfolio management, IT business management, business process analysis, IT architecture, data management, governance, risk, and compliance. All of those are top-level capabilities. MEGA HOPEX is considered a leader in EA according to the latest Gartner report.
There are built-in connectors that provide out-of-the-box integration with other well-known platforms, such as ServiceNow. There is always room for customization enabling a catered platform unique for each client.
I have been using MEGA HOPEX for approximately two years.
HOPEX is highly scalable.
Very responsive and helpful customer support
Positive
The initial setup of MEGA HOPEX was easy.
We have many use cases for this solution but the feature I have found most valuable is the IT Portfolio Management module. This has helped in my duty to ensure the gathering of artifacts and repositories for analysis for my clients. We also make use of the Business Process Analysis feature.
This is a good product with many features and this can make it easy to get lost in what to use. A more friendly user manual would be good.
It would be great if this solution could integrate with other tools such as ITSM (ServiceNow) or CMDB.
I have used this solution for five years.
This is a stable solution.
I have clients with 2 users and clients with more than 25 users and find it is a scalable solution. This does depend on how you use the solution. HOPEX is a suitable solution for larger scale use but you will need to pay per license. Using HOPEX, you can have an unlimited amount of users.
My team act as the HOPEX local technical support in the national region and we often help from the principal support team. This support team is helpful and responsive.
The setup was straightforward to deliver the use cases of enterprise architecture.
This solution is reasonably priced but would be more competitive at a slightly lower price.
I would suggest that any prospective user understands exactly what their use case for this solution would be before implementation.
I would rate it 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.
