MEGA HOPEX Platform vs. SAP LeanIX Enterprise Architecture

MEGA is well suited for

• Service Architecture definition

• Service relationships

• Service that supports process and vice versa

• Business process definition

• Definition of Business Entities

• Management of business entities

• Business Entity managed by services

• Creation of service reports

MEGA is less appropriate for:

• Business Service management information (who is “developing, responsible, etc.” for business services)

• Business services contracts

• Business services performance management

Incentivized

Not a 10, because now SAP is owner, there remains uncertainty on the development and pricing strategy. we struggle a bit with defining thr complex architecture of our non-sap ERP platform, but we learn as we go.

Very interesting also to start up interfaces, seems to work very well and helpfull in maintaining the proper insights

Incentivized

• Define business architecture
• Design processes
• Tailoring business services attributes

Incentivized

• User friendly
• Configurable
• Relations between fact sheets
• Lifecycle management
• Self build reports

Incentivized

• API for external use
• Query engine (join between metaclass)
• Export tools
• Web site generator

Incentivized

• More depth in initiatives.
• Pre- fill with complete architecture of major solutions (like M365, infor m3 or other non SAP solutions)

Incentivized

In the software selection, we evaluate also
Enterprise Architect; but it was evaluated non enough easy to use. Open source software are non available.

Incentivized

We did not do a comparisson

Incentivized

• Only positive impact in all departments

Incentivized

• We use it for portfolio management and through its use, are enabled for better prioritization and selection of projects
• We reduced our application portfolio that were overlapping in features
• We identified weak process areas and are now able to challenge business projects in relation to process maturity and user happiness

Incentivized