Memory/Cost estimation in Cloud ALM

[sunilnag]

Hi Experts, 

We are currently using SAP Solution Manager with multiple capabilities such as System Monitoring, Business Process Monitoring, ChaRM, and Solution Documentation. As part of our Cloud ALM migration planning, we are working on cost and memory/data estimation compared to our existing SolMan setup.

We understand that SAP Cloud ALM follows a fair-use model (~24 GB HANA memory per tenant) and does not store full historical data like Solution Manager. However, we are facing challenges in translating our current SolMan usage into Cloud ALM sizing and cost estimation.

Could you please help us with the following:

1. Memory / Data Estimation

• What is the recommended approach or methodology to estimate Cloud ALM memory requirements based on current Solution Manager usage?
• Which parameters should be considered (e.g., number of systems, BPMon objects, interfaces, alerts, retention)?
• Are there any official SAP sizing tools, estimators, or benchmarks available to map SolMan usage to Cloud ALM memory consumption?

2. Cost for Cloud ALM (Beyond Fair Use)

• If the 24 GB memory limit is exceeded, how is the cost calculated?
• What is the pricing model for tenant extensions (additional memory / API limits), and are there any standard benchmarks for estimating these costs in advance?

3. Cost & Impact of Continuing Solution Manager (Post‑2027)

• If we continue using SAP Solution Manager beyond 2027 (end of mainstream maintenance):
  • What additional extended maintenance charges or premiums will apply until 2030?
  • Are there any cost impacts for infrastructure, support, or customer-specific maintenance beyond standard SAP support?
• From a cost and risk perspective, how does continuing SolMan until 2030 compare with migrating to Cloud ALM?

4. Planning Guidance

• Are there any reference architectures, benchmarks, or typical memory/cost ranges for small, medium, and large landscapes that can help us estimate both Cloud ALM and SolMan continuation costs?

Any guidance or documentation would help us build a reliable cost and sizing estimation model for our migration planning.