MEGA HOPEX Platform vs. SAP LeanIX

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

• Data modeling
• Maintaining a consistent data dictionary through the use of the repository.
• Custom templates for generating objects off of tables.

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

We did have to reach out to support to learn how to properly utilize the repository feature and share the data model across many developers. Support was able to help us get this set up correctly. The downside was it took us several weeks before we gave up and contacted support. We should have done that earlier. I would say, however, the documentation wasn't clear on how to do this. So support was a great big help!

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

The version of ErWin we had didn't support the repository for document sharing and data dictionary sharing. Our version of PD does so we were able to leverage that and have a central repository that is shared among the team members. That really helped to give us consistency across our databases. PD is easy to use, but getting the repository set up properly was a little tricky.

Incentivized

• Only positive impact in all departments

Incentivized

• Standardization of models
• Impact Analysis
• Graphical User Interface
• Ease of deployment

Incentivized