MEGA HOPEX Reviews

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 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.

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. 

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.

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.

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.

The main module we use is ITPM. The ability to have standardized reports around obsolescence and lifecycle management is probably the most valuable.

We are trying to move to a more standardized approach regarding how we do lifecycle management and having the ability to generate the obsolescence report which says what applications are impacted by obsolete technologies on a rolling horizon is valuable so that we can actually do our business planning and manage technical data in a more organized manner then the way that we have been doing it today.

It shows you for all of the applications that are depending upon obsolete technology, what is the technology that is going obsolete and what is the application that is impacted. Essentially, it's a list view.

We are not using the entire platform, although we are licensed for a couple modules. The main one that we are using is ITPM. The other thing that I think we find useful outside of the obsolescence report is also having a more organized view of our applications and their technology dependencies. Matching it up with roadmaps related to technologies in a singular view. We had an application technology view that also becomes quite useful.

I think it has a lot to offer, but we have been focusing in on ITPM. I think we ourselves need to do a little bit more exploration of how we can benefit from some of the other modules.

Something that might be helpful is to have a little bit more of a curriculum-based engagement of MEGA where we are actually educated more on the bigger picture, not just the tool, but really what is the big picture that MEGA is trying to solve. What are the different pieces and how they fit together? I think that will help expose the power of MEGA to us to see how we can actually use it better. Kind of the Art of the Possible type of positioning.

From the capabilities perspective, the user experience is not the best. It needs to be a lot more easy to use, more intuitive.

It could also drive adoption. We are a pretty large organization with a lot of application and it's not all architects that are using this tool. There are people that are in peripheral organizations that we rely on to provide information and the user interface really needs to be simple and clean and be able to move from task to task very efficiently. The feedback we have gotten so far has not been that. It's been, it's hard to navigate. It's not intuitive. It takes time to do multiple updates in a sitting.

What that means today is that people export data out of MEGA, manage an Excel spreadsheet and then do vault uploads and it kind of defeats the purpose of having a tool like this.

18 months. We are getting to the first real use of it with our business planning for next year and kind of starting now.

We have had challenges with scale. We had to refactor the way that we organize the data due to that scaling issue. Originally, we had brought in every application landscape as an individual application and if the reports were timing out and we were not able to get a performance response. In fact, our users were complaining as well. We have refactored so that applications are really more of our business service construct that are grouping multiple landscapes which are becoming software installations. It's working a little bit better, but we still have struggles with some reports that are large or go out to large data sets that the system sent tends to time out. In fact, we had to put automated timers to terminate tasks that are taking too long just because it becomes ineffective. These jobs are in the background that cause other problems. Performance and scale has been an issue.

If you have an interactive application, people don't expect it to be taking hours. People expect responses within minutes. When they're sitting there for 10, 15, 20 minutes and there is nothing back, something is obviously not done right whether the architecture behind the scenes is not done right or the way it fans out to compute is not done right, something is not right. We've had performance issues and continue to struggle with it. Another example is when we do these reports, as I mentioned, obsolescence, really have to do with volume.

You have to do it on a portfolio by portfolio basis. You need to go to the top level and say, "Run this obsolescence report for everything in my environment." Then we have to say, "Do it for a subset of the data set just because of performance."

My team actually runs the platform, I don't really deal with technical support themselves, but I do get feedback. Yes, they have used technical support. It's kind of a mixed bag. Sometimes we have gotten good results, but other times it hasn't been what we would hope for.

Generally we do engage them as well as professional services. In fact, we've probably been engaging professional services a lot more than we need to. That's a different issue.

We got an introduction to MEGA from a smaller group within our company. The conversation with the person that was already using it was essentially focused on how much customization were they doing.

At the time they told me it had unlimited customization and that is kind of what drove me to say we are going to adopt MEGA for the Enterprise, but truth be told, since we have adopted it, we are actually doing a lot more customization than I would have hoped for. The out-of-the-box capabilities don't really align with the broader vision. Hence, we are spending a lot of time with pro services.

When they did the assessment I think they looked at Alfabet and a couple of others.

Be very clear on what you need because MEGA has a lot to offer and if you are really going to be able to take advantage of MEGA's portfolio, then you should consider it. Be ready for the journey we went through which took 18 months to get to where we are at.

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.