Wherever, however

Flexibility in the use of professional software is a cornerstone for the success of a software project. However, flexibility is not limited to the installation location of the software itself. If you want to meet the needs of a customer in a pinpointed manner, there are other dimensions of flexibility in business software that you have to consider as a manufacturer.

The implementation model of MD-Premium is a 3-dimensional approach that consists of the topics of deployment, involvement and individualization.

1D – Deployment

In the cloud or on my own systems... this is one of the most important questions that needs to be answered in the course of a software project. Even though SaaS solutions are very popular because of their cost-efficiency and "hassle-free" philosophy, on-premise solutions are still in demand because you have the undisputed sovereignty over your data and your processes.
With MD-Premium, the question doesn't even arise, because the system is rolled out in the way that best suits your needs:

• Multidata Hosting: Your MD Premium instance runs as a SaaS product within Multidata Hosting. You have full access to all functions of the system, including the possibility to expand your instance individually. The data is hosted in Germany in an ISO-certified data center in full compliance with European data protection standards.
• On-Premise: You buy and operate the software within your own IT. You have sovereignty over the data and where it is stored.
• Self-hosting: If you do not want to use the software yourself, but want to resell it to your own customers with appropriate adjustments, you have the option of operating and hosting the software yourself.
• Hybrid-Models: You operate the application yourself within your IT, but the database is outsourced, e.g

2D – Involvement

Business software projects are almost always associated with accompanying work, such as adaptations, integrations, extensions, as well as training and on-boarding. Depending on the type of project and the client's available resources, the responsibility for this work can be flexibly divided.

• Multidata in the lead: Project and implementation responsibility lies mainly with Multidata. If the customer is a partner/reseller himself, the end customer support is provided by Multidata.
• Shared responsibility: Project responsibilities are shared between Multidata and the customer. For example, the customer can make certain adjustments on his own. In the case of a partner project, Multidata could carry out the adjustments, but the customer takes over the end customer support.
• Customer in the lead: Project and implementation responsibility lies mainly with the customer. Multidata has a supportive effect when required, but otherwise only acts as a licensor. Partners are responsible for hosting, rollout and customer support, as well as the extension of the solution with their own features

3D – Individualisation

In the case of business software, customization to customer requirements is not a nice-to-have, it is absolutely essential for the smooth running of the project and widespread acceptance of the system by end users.

MD-Premium allows extensive modifications and extensions of the basic software, to the point where a customer can build his own business logic and create an entirely new product. A wide variety of scenarios regarding individualization are therefore possible:

• Retaining: The software is used by and large as it is delivered by Multidata. Only detailed adjustments are made, e.g. to the GUI.
• Adjusting: The software will not be adapted in its range of functions, but the behavior of individual functions will be expanded or modified to meet special requirements.
• Extending: The software's range of functions will be expanded with its own features. These can be embedded in the existing functional landscape as well as combined in completely new function modules.
• Inventing: The customer discards large parts of the existing business logic to create a standalone system. This can go so far that only the AFW and WSA frameworks and the clients are used, while the business logic follows a completely different path.