MEGA HOPEX Reviews

We use the product for application portfolio management. We capture a list of applications and draw architecture diagrams. 

We use the portfolio management feature heavily. 

The tool's UI should be more user-friendly. 

I have been working with the product for two years. 

The solution is stable. 

We have ten users for the product. 

We don't have direct tech support. We avail support through a system integrator. 

Neutral

We had faced some issues with the tool's setup and it took a few days to configure and deploy. 

I would rate the product a seven out of ten. You need to explore other options before selecting this product. 

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.

The most valuable features for us are related to business processes.

The features are limited. I'm hoping in the future the solution will be bigger and include more items. Right now, overall, it needs more.

I've been using the solution for three years so far.

At first, the solution wasn't too stable. It's improved. Now it's okay.

The solution is scalable. If a company needs to expand it, it's completely possible to do so. 

We only have one person currently working on the solution.

The initial implementation has a moderate amount of difficulty. It's mostly easy, but there were a few items in the release I implemented that were challenging. 

Deployment took us about three days. It didn't take too long.

The licensing is on a yearly basis. I'm not sure exactly what the yearly costs are, as I don't handle this aspect of the solution. I believe it may be around $2,000-$3,000.

We're only customers. We aren't partners or resellers of the solution.

I'm not sure which version of the solution we're currently using.

I'd rate the solution seven out of ten. The solution is one of the best. We've been very happy with it.

We use this solution for capability assessment and modeling business processes.

This solution provides a shared repository for EA artifacts and enterprise components.

The most valuable feature of this solution is the reuse of common enterprise components and entities.

The tool usability is weak and it also has a high learning curve.

As a business and process analyst, I found the Mega Process module very powerful. Since Hopex is an integrated architecture, it was possible to depict business processes with BPMN notation, and identify every system that participated in the process then generate the application architecture. It is also possible to generate textual procedures from the process models with Mega Process, and it is possible to export all processes to the enterprise architecture (TOGAF) module if needed.

As a consultant, I implemented Mega Process in different enterprises. For example, you create a process referential, which means, you depict the general cartography and all the subsequent levels (process layers), until the finest level. You're able to see all these levels in one space, using the the drill down technique to spread them, and see all the details for each process the process referential can be shown to every SME or users by installing the publisher module.

The most important thing to be improved is the reliability. Mega should pay more attention because from time to time, the screen freezes or the application stops working without saving the work.

I've used it for more than 14 months.

I've had no issues with the deployment, and I've done three.

I've had no issues with the stability.

I've had no issues scaling it for our needs.

9/10 - They were very useful.

9/10 - They were very useful.

I used to use the AG BPM solution, and it wasn't my decision to switch.

The initial setup was a bit tricky, because Mega made a strong security procedure to avoid hacking their solution, but after a few times, the process become pretty clear.

As a reseller, I implement the solution with the help of the vendor in the client environment, so I am not very aware about the Mega Hopex architecture and technical view.

I found the price in the middle range of these kinds of products.

Before implementation, you will find it useful to visit the Mega community website https://community.mega.com/. I found it very helpful on many occasions, for example, you can find many tips about the implementation.

Our primary use case for this solution is process modeling.

The most valuable feature for this solution is the automatic updating and propagation of changes across the system. For example, when we make a change in one of our organizational charts, the changes are automatically made in all of the other processes. This saves us time as compared to in the past when this had to be done manually.

It is a user-friendly solution.

We use this solution for modeling and we do not have an application side to create forms and deploy applications. It would be helpful if we could use this solution to model an application and then deploy it.

If would be better for us if there was a cloud version of this solution available. 

Continuous integration and DevOps is not yet handled by this solution.

We would like to see integration with other products, such as being able to use our workflow with SharePoint and Microsoft Office.

The stability of this solution is ok.

The scalability of this product is something that we found issues with during migration. I would rate the scalability of this solution at sixty percent.

It is only my team, the Quality Department, who uses this solution and there are four of us. The other people in the company refer to the reports that it produces but do not use the product directly.

I would rate this solution's technical support a six out of ten.

I have also used Kissflow, which is able to handle both the organizational side and the application side. Using that solution we can model, create forms, and deploy it like an app. We can have a workflow to help organize the company. It isn't just for understanding how a process works.

The initial setup for this solution was straightforward and easy.

We did have a problem with migration from an older version to a newer one. There was an issue where our administrator made an error and we lost data. We spoke with our partner and they suggested that we should pay because it was our mistake. In the end, we lost thirty percent of our data.

We bought this solution directly from the vendor in Morocco, and they helped us with the implementation. It was really good.

If you want to use additional features, such as the Risk Management capability, then it is a little too expensive.

This solution can be used for modeling, and the publication for employees to consult on the process and design. It can not be used to automate processes or create an application. Therefore, if you want it for enterprise architecture and modeling then it is a very good solution. On the other hand, if you want it for process automation then it is not.

When we migrated to this solution it was difficult. I don't think that we had enough documentation. We felt it was important to switch to the new version because the older one is no longer supported. The impression we have is that when you want to do something like a migration, they want you to pay extra consulting fees. For mid-sized companies, this is sometimes not in the budget.

It is a little bit frustrating that we do not have process automation. Without this, we cannot scale this solution to the new services of our company.  

I would rate this solution a six out of ten.

• Business processes
• Holistic modeling of an enterprise
  
• Its city planning of an enterprise information system.

Generates friendly websites and presents specific views of the enterprise (business, functional, applicative, technological, and infrastructure).

• Collaborative portal
• You do not need to be a professional of enterprise modeling to contribute to the enrichment and improvement of the enterprise repository.

• Friendlier import/export to other modeling tools.
• Better interaction with project portfolio management tools.

ITPM – It provides a central location to manage our technology portfolio and standards/governance.

It provides a central repository of all architecture artifacts as well as application inventory. It has made it easier to do impact analysis. It’s slowly becoming the authoritative source of current state application architecture.

We would like the reporting and analytics, road mapping, import/export functionality, and data modelling capabilities to be improved.

It was a bit challenging to convert our old Mega licensing model to the new Hopex licensing model which is at a more granular level. Managing the new licenses and roles was difficult on the initial setup.

There were no issues with the stability.

We have had no issues scaling it for our needs.

Overall, they have good support.

We evaluated other EA tools but we already had Mega in-house and continued to use it.

Fairly straightforward. There were some steps in the documentation that were not clear but with tech support’s help we overcame the issues.

We implemented it in-house with an enterprise architect and system administrator working together. We developed an implementation plan before starting the initial deployment and/or upgrade.

Mega needs to simplify their licensing model more like other leading EA tools in the market.

Collect accurate and up-to-date data about your environment before implementing an EA tool. Have an approach in terms of what objects to create in the tool in what order. Set up a sandbox environment to familiarize the architects and other users with the tool. Avoid creating extraneous objects in the production environment; start with small set of objects and artifacts that add value and will be used.