"Cloud EPM" names a family of eleven or so business processes, plus a data management capability. Each is bought separately or as part of a subscription bundle. Each is implemented separately. And — critically — an environment hosts one business process.
That is the one that surprises people. You do not put Planning and Financial Consolidation and Close in the same environment. Two business processes means two environments, which means two of everything in this course.
The estate arithmetic. A client running Planning, Financial Consolidation and Close, and Account Reconciliation, each with test and production, has six environments. Six sets of users. Six maintenance windows. Six backup regimes. Six monitoring routines. This is why platform administration is a job.
The families — a way to hold eleven things in your head. Planning: Planning, Planning Modules, FreeForm, Sales Planning, Strategic Workforce Planning. Close: Financial Consolidation and Close, Account Reconciliation, Tax Reporting. Analysis and reporting: Profitability and Cost Management, Enterprise Profitability and Cost Management, Narrative Reporting. Data: Enterprise Data Management, and Cloud EDM.
What they share is the platform — identity, environments, security, clients, automation, backups, monitoring. That shared layer is this course.
"We are implementing EPM" is not a scope. Which business processes, and how many environments? Ask it first, every time. It is the question that turns a sentence into a project.