EPM managed services questions, answered clearly.

A contracted, ongoing service in which Namandla takes responsibility for keeping your Oracle EPM applications working: monitoring, incident response with agreed response times, changes to rules, forms, mappings and metadata, patching on-premises or monthly update testing in the cloud, health checks, and standby cover during the close and budget cycles. It covers on-premises Hyperion estates, Oracle EPM Cloud services and the hybrid estates most groups run in between. A named senior consultant knows your environment, and the scope is agreed per client rather than sold as a package.

Because EPM applications need skilled maintenance between projects, and those skills are scarce in South Africa. Most groups depend on one or two people for HFM, Planning, Essbase, FDMEE or the cloud services; when they are on leave, overloaded or gone, the close and the budget carry the risk. Managed services turn that dependency into a contracted capability with defined response times, documented knowledge and cover during the cycles that matter, at a cost that is predictable rather than incident-driven.

Monitoring of services, jobs and integrations; incident response with defined response times; application changes with regression testing against prior results; metadata and hierarchy maintenance; data integration mapping maintenance and failed load resolution; user provisioning and security; patch assessment on-premises and monthly update testing in the cloud; backup and restore verification; quarterly health checks; priority standby during month-end, budget and year-end; and a service review with a findings and risk register. The product support FAQs on this site describe what each of these means for HFM, Planning, Essbase, FDMEE, Smart View, FCCS, EDMCS, Narrative Reporting and the EPM Cloud platform.

On-premises: Hyperion Financial Management, Hyperion Planning, Essbase, FDMEE and Oracle Data Integrator, Data Relationship Management, Financial Reporting and Smart View, on EPM System 11.1.2.4 and 11.2. Cloud: Planning Cloud, FCCS, Data Integration, Enterprise Data Management, Narrative Reporting and Account Reconciliation on the Oracle EPM Cloud platform. Hybrid estates, where on-premises and cloud applications exchange data during a staged migration, are supported as one estate rather than as two contracts.

By diagnosing before tuning. A health check measures where the time goes in each application and in the shared platform, identifies the drivers, and fixes them in order of impact: consolidation rules that run for every entity, calculation scripts that recalculate whole cubes, forms that retrieve too much, mappings that evaluate every record, databases never maintained, servers at installation defaults. Most performance problems in EPM estates are maintenance debt rather than capacity limits, and clearing them is part of the service rather than a separate project.

Yes, in the sense that matters: the applications are available and working when the close or the budget needs them. Monitoring catches failed jobs and services before users do, patches and updates are tested before production, backups are proven to restore, certificates and support dates are tracked, and standby cover means an incident during a cycle is handled by someone who knows the estate rather than discovered the next morning. The measure is closes and budget cycles completed on time, and that is what the service review reports on.

Support that works from your calendar and Oracle’s calendar rather than from incident tickets: preparing applications before each cycle, reviewing changes before production, testing monthly cloud updates in the test environment, checking patch levels and support dates quarterly, testing restores and tracking the risks in a register that you see. It also means telling you when a risk exists, such as a single administrator, an unsupported version, an untested backup or an integration nobody owns, before it becomes an incident.

Yes, and this is where the service earns its place. Standby cover during month-end, interim and year-end means a consultant is available to resolve load failures, consolidation errors, rule problems, locked periods and reporting issues while the close is running. Before year-end the service reviews the year’s changes, confirms that prior-period comparatives still consolidate to the published figures, rolls periods and schedules forward and tests the critical reports, so the close starts from a known-good position rather than from the first failure.

Yes. For Oracle EPM Cloud the service covers the monthly update discipline (reading the readiness notes, testing in the test environment, confirming production), identity and access administration, EPM Automate scripting, snapshot backups and migrations, Data Integration pipelines and the Activity Reports that show where performance goes, alongside the application-level work in Planning Cloud, FCCS, Enterprise Data Management and Narrative Reporting. The cloud removed the servers, not the administration, and the EPM Cloud support FAQ covers that platform layer.

By keeping the controls current rather than by adding products: access reviews that match roles to the people who actually need them, provisioning and deprovisioning tied to joiners and leavers, security classes and filters that restrict data by entity and cost centre, patch levels and versions kept on supported releases so security fixes are actually received, certificates renewed before they expire, and audit logs preserved. The material security risk in most EPM estates is an unsupported version and a shared administrator account, and both are maintenance matters.

By measurable results on applications and subscriptions you already pay for: closes and budget cycles completed on time, consolidation and calculation times reduced, fewer failed loads and re-runs, features you are licensed for actually in use, monthly updates absorbed without incident, and a documented estate that does not depend on one person. The return is highest for groups considering a replacement mainly because the current applications have become unreliable; that is usually maintenance debt, and clearing it costs far less than a re-implementation.

Outsourcing makes sense when EPM knowledge sits with one or two people, when the estate spans several applications and nobody owns the calendar across them, when changes are infrequent but high-stakes, or when the finance systems team is stretched across ERP, planning and reporting. It makes less sense if you have trained administrators for each application who run every cycle, test each update and keep documentation current. Namandla’s managed service is designed to work alongside an internal team, taking the specialist and standby work while your team keeps ownership, and to hand knowledge back rather than hold it.

Break-fix support responds after something has failed, bills by the incident and learns your estate during the call, usually during a close. Managed services know the applications, integrations and calendar, monitor between cycles, prepare before each one, make changes under control and carry responsibility for the cycle completing on time, for a predictable fee. Break-fix suits a stable estate with strong internal skills. For a group whose statutory reporting and budget depend on EPM, managed services are usually cheaper over a year, because incidents during a cycle are the expensive ones.

Yes. The service carries an estate through acquisitions (new entities, ledgers and mappings), reorganisations (hierarchy changes across every application), ERP upgrades and replacements (re-pointed integrations), upgrades from 11.1.2.4 to 11.2, and staged migrations to Oracle EPM Cloud, because the people maintaining the estate are the people who understand what each change touches. The service review keeps the remain, optimise or migrate position current, so the platform decision is made on evidence when the time comes rather than forced by an incident.

Namandla is a South African consultancy whose senior team has run Oracle EPM estates for about two decades, on-premises and in the cloud, and the consultant assigned to your estate is the one who answers during your close. We support the estate as one system, we are independent on remain, optimise or migrate, we run the monthly cloud update discipline as a standing task, and where AI can help with the close, the forecast or the board pack we apply it to the data you already have, with human review. Contact info@namandla.com or 087 188 3388.