SAP® and Non-SAP Automation with EPOS

With the approach of “SAP and Non-SAP Automation”, Empirius is expanding the use of EPOS beyond SAP, providing customers with extended application options. What is the objective behind this change?

Hans: The starting point is that virtually all SAP customers also run non-SAP infrastructure components alongside their SAP systems. This means that automation should not focus only on SAP or non-SAP individually – it must take both into account. In addition, an SAP system itself is not “just SAP.” It runs on a database and an operating system, and if you want proper system management, you naturally have to include those components as well.The trigger for integrating non-SAP systems more strongly into EPOS came directly from customer requests and requirements.

Are you aiming to replace tools from vendors such as SUSE, Red Hat, Microsoft, Oracle or SAP’s own utilities like SAP Me with EPOS?

Hans: Absolutely not. The goal is that, within the context of managing an SAP landscape, EPOS can also manage non-SAP infrastructures and components. For example, we can manage all Windows systems – SAP and non-SAP alike – in one go, clustered together. And EPOS acts as the starting point – the central point of management

What exactly does “Central Point of Management” mean?

Hans: The central point of management plays a key role. First, EPOS collects a vast amount of information from all systems and infrastructure components into the EPOS database. Second, this information can be used to trigger actions.

For example: if you know a Microsoft patch level is already eight months old, you can check which new patches are available and act accordingly.

In short: EPOS collects information about systems in order to trigger required actions. In the long term, this “central point” will also deliver automated, proactive reporting – enabling secure and efficient infrastructure management.

What are the main benefits for users?

Hans: At Empirius, the priority is and always has been automation – and continually increasing the level of automation. This delivers clear efficiency gains: cost savings, reduced workloads, and minimized downtime through best-practice processes.

Which areas can be automated with EPOS apps, and which apps are available for non-SAP systems?

Hans: The EPOS BlueCopy App for automated SAP system copies has long integrated non-SAP systems such as DMS or MES solutions. Other apps – like the Custom App or the System Maintenance App – already provide interfaces for non-SAP integration.

We also plan to extend the EPOS Certificate Management App to cover non-SAP systems, since certificates are always tied to security, and security is becoming increasingly critical. More developments are in the pipeline – both for SAP and non-SAP.

At the end of the day, it’s about automating tasks for SAP Basis and IT infrastructure teams. Think of something as simple as a time change, when dozens of systems need to be restarted. With 10 systems it’s manageable – with 40 or 50, the effort is huge. Or consider shutting down and restarting an entire data center at scheduled times. Or patching Oracle or DB2 systems independently of SAP, across maybe 100 systems or more. With EPOS, these scenarios can be automated. Dedicated apps for such use cases are on the roadmap.

Infrastructure teams often use several tools in parallel. Why should they choose EPOS for OS or DB patching when vendor tools from OS or DB providers also exist?

Hans: As I said, our goal is not to replace existing tools on the market. The idea is to integrate them into a larger end-to-end process, while ensuring they are enriched with the infrastructure functionality needed to support SAP operations.

Which customer groups are you targeting with SAP and Non-SAP automation?

Hans: Our primary focus remains the SAP market, because that’s where we come from and where we deliver the most value. This is the space we want to continue to grow and expand.

To what extent does Empirius support customers in extending EPOS use beyond SAP?

Hans: If an Empirius customer requires consulting, we of course support them – but always in the context of EPOS. In most cases, this means reviewing the existing automation setup together, discussing specific needs in an assessment, and then developing solutions based on EPOS.

Our customers often approach us with ideas like: “Can we achieve this or that with EPOS?” – and we are always there to advise and implement.