FCC: a new era of intelligent SAP administration and monitoring

Something has quietly changed about running SAP. Not the transactions, and not the discipline. A Basis engineer from a decade ago would recognise most of the daily work. What changed is where the landscape lives. It is on-premises and in the cloud. It is ECC and S/4HANA at the same time, and will be for years. It is HANA underneath a growing share of it, with its own memory behaviour, its own backup rules, its own failure modes.

What has not changed is how most teams operate all of it. One screen per system. One specialist per question. A status report assembled by hand, out of date by the time anyone reads it. The landscape became distributed. The operating model stayed local.

The cost is the time before the fix

Ask an operations team where an incident actually goes, and the answer is rarely the repair. It goes on establishing what happened. Which system. Since when. What else moved at the same time. That reconstruction is done manually, across several tools, usually by the one person who knows that system best. Then it happens again on the next incident, because nothing kept the context.

Around it sits a second cost, less visible and larger over a year: the routine checks. Job status, dump counts, filesystem headroom, backup age, lock entries. Necessary work, done by expensive people, at the expense of the engineering that would stop it recurring. Meanwhile the people accountable for the service, delivery managers, IT directors and the CIO, are asked to decide from a monthly document rather than from the current state of the estate.

None of this reflects badly on the teams. It reflects a tooling model that assumed one system at a time.

Introducing Farrenio Cloud Control

Farrenio Cloud Control (FCC) is a SaaS platform for the administration, operation and monitoring of SAP landscapes. It supports ECC, S/4HANA and HANA environments in a single console, and it is delivered as a service: a browser and an account, with no monitoring infrastructure to build or maintain.

Connectivity is the question experienced teams ask first, so it is worth answering early. A lightweight collector runs on each SAP host and connects outbound over HTTPS. Nothing listens on the SAP host, no inbound port is opened, and no firewall rule is required. Each collector carries its own credential, which can be revoked from the console at any moment. Because the only requirement is outbound HTTPS, the same model covers on-premises, cloud and hybrid hosts without a different deployment for each. The platform walkthrough covers that data path screen by screen.

FCC is in Beta. That is stated deliberately. The platform is running against real systems, and it is still being shaped by the teams using it.

What it gives the people who run SAP

For a Basis administrator or an operations engineer, the practical change is that the landscape stops being a set of separate windows. Work processes, background jobs, short dumps, lock entries, buffer and response-time behaviour, HANA memory, connections, backup age and replication state are collected continuously from every host and presented together, with the system name already attached to the answer.

That distinction matters. General infrastructure monitoring reports CPU, memory and disk perfectly well, and there is no reason to remove it. What it cannot see is inside SAP: that every dialog work process has gone into PRIV mode, or that a job chain cancelled at 02:14 and nothing downstream has run since. FCC adds that layer, and complements the tools already in place rather than replacing them.

Alerting follows the same principle. Thresholds are set per metric and per customer rather than against a global default, escalation routes by severity, and any alert can be promoted into an incident with its history intact. Repetitive procedures run as guided runbooks: prerequisites validated before anything is applied, steps executed in sequence, each one written to the audit trail with the operator’s identity attached. Access is granular, so a service desk can triage alerts all day without the ability to execute a command or reveal a stored credential.

What it gives the people accountable for the service

Management stakeholders need less detail and more certainty. FCC produces an availability and SLA picture with planned maintenance excluded, so the number survives contact with a customer conversation. It records every privileged action with the person, the source and the outcome behind it, which is the difference between asserting control and evidencing it. It consolidates tools that were separately licensed, separately learned and separately maintained. And it replaces “we will check and come back to you” with an answer available now.

AI, described accurately

FCC uses AI today, and it is worth being exact about how. The platform runs a battery of deterministic checks over each system and computes the facts: statistical anomaly detection across metric time-series, capacity forecasting from observed trends, clustering of related short dumps. An AI layer then reads those computed results and returns a prioritised, plain-language assessment of what deserves attention first and what is benign noise. It is grounded on the platform’s own measurements and instructed not to invent values. If it is unavailable, the deterministic report stands on its own.

That is the honest shape of AI in SAP operations right now. It is good at triage, correlation and drafting the first version of an assessment. It is not a substitute for an engineer who knows what that system does for the business. Nothing in the design points toward unattended operations. The direction is the opposite: as automation takes on more, the audit trail and the human approval step matter more, not less. We set out that position in more detail in how AI is changing SAP Basis monitoring.

Where this goes

The roadmap we publish is deliberately incremental. Per-customer SLA digests, inline alert actions in Slack and Teams, an evidence pack for SOC 2 Type II audits, a forkable runbook library, customer-written collectors, and capacity forecasting with confidence intervals. Further out, the ambition is an operations assistant that can answer “what changed today, and what should I look at first” against your own landscape, with a named person still deciding what happens next.

The underlying bet is simple. SAP landscapes are not going to get simpler, and teams are not going to get proportionally larger. What can change is how much of the operational picture is single, current and shared.

Start with one system

The most useful evaluation is not a workshop. It is one collector, installed against one system you know better than anyone, judged on your own jobs, dumps and HANA tenants rather than on a demonstration dataset. If it tells you something you did not already know, that is worth ten slides.

Request a demonstration or read the per-system pricing. FCC is in Beta, and Beta participants work directly with the team building it, which means the platform you evaluate this quarter is one you can still influence.