MEGA HOPEX Reviews

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.

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.

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.

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

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

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.