RISE contracts present a clean front cover: a headline FUE quantity, an annual subscription price, an infrastructure tier, and a term. Behind the front cover sits a schedule of operational limits that determine what the system can actually do on day two. The limits are not optional features; they are the boundaries of the service. Crossing them does not generate an outage — the contract is built more carefully than that — but it generates a true-up event, a service-level negotiation, or a forced uplift to a larger T-shirt size. The buyer who reads the operational schedule line-by-line in the negotiation window negotiates limits that match the actual workload. The buyer who reads it for the first time in the second year of operation has already accepted the seller’s defaults. This article walks through the limit categories, what each one constrains, and which ones to harden during negotiation. The discipline is a regular module in our contract negotiation engagements.
The storage limit
Every RISE T-shirt size carries an HANA-database storage ceiling, expressed in either gigabytes or storage-tier units. The ceiling sounds generous in absolute terms and looks adequate against the existing on-premises footprint. The complication is growth: the storage curve under S/4HANA is steeper than the equivalent on ECC in the first eighteen months of operation because the conversion process retains historical data and because the column-store architecture absorbs more of the operational data than the row-store equivalent. Storage true-ups are common in years two and three. The negotiation move is to project the storage curve out for the full term and contract for the headroom at the negotiation rate rather than at the eventual true-up rate.
The session limit
Concurrent-session ceilings are often present in RISE schedules but not always in the headline summary. The ceiling is most visible in the named-FUE allocation but the underlying technical session count is the constraint that bites operationally. Workloads with heavy batch parallelism, dense reporting, or extensive integration traffic can hit the session ceiling without exhausting the FUE allocation. The result is the same: a service-tier conversation that resolves with an uplift. Negotiate the session ceiling against the actual usage pattern, not against the FUE-derived approximation.
The downtime windows
Planned-maintenance windows in RISE are typically expressed as a number of hours per month with a specified notice period. For most workloads the windows are operationally inert. For workloads with global twenty-four-hour operations — e-commerce, financial services, logistics — the windows are a material constraint that maps directly to business-process design. The negotiation move is to harden the notice period (forty-eight hours is more useful than the standard window), to narrow the window itself to a specific weekend slot, and to record the escalation path when maintenance must extend beyond the window.
The change-management ceiling
RISE contracts often cap the number of major change events per year — release upgrades, sizing changes, infrastructure migrations — with additional events priced as professional-services consumption. The ceiling is rarely large enough to absorb an active S/4HANA roadmap during the early operating period. The pattern is well established: the contract is signed against a steady-state assumption, the actual operating period requires more change events, and the additional change events become a recurring cost-overrun conversation. The RISE pricing model article covers the change-event pricing detail.
The SLA structure
The service-level commitment in the standard RISE template is typically expressed as an availability percentage with a service-credit remedy. Two facts matter for the buyer’s contract review. First, the availability percentage is measured against a defined measurement window that may exclude planned maintenance, scheduled outages, and force-majeure events — the effective availability is therefore higher in the contract definition than in the operational experience. Second, the service-credit remedy is typically capped at a fraction of the monthly fee, which does not approach the business-cost of a meaningful outage. The negotiation move is to harden the measurement definition (narrower exclusion list, longer measurement window for averaging), and to expand the service-credit cap to a value that begins to approximate the business cost.
The two contractual moves that compound across the full term are the storage curve and the SLA exclusion list. Both are negotiable in the deal window and effectively immovable after signature.
The exit assistance schedule
The exit-assistance terms are themselves an operational limit, because they constrain what can be done at the end of the term. The standard RISE template provides a defined number of hours of exit assistance, with a defined data-export format and a defined window for the data extract. For workloads with significant historical-data dependencies, the standard assistance is rarely sufficient. The RISE exit terms article covers the negotiation in detail.
The indirect-access volume cap
RISE contracts include digital-access entitlement, often expressed as a document-count ceiling. The ceiling has a different shape from the on-premises equivalent because it bundles the document allocation with the FUE allocation. Workloads with significant integration traffic from third-party systems can exhaust the document-count ceiling before exhausting the FUE allocation. The exhaustion produces a true-up at the digital-access rate. The negotiation move is to project the document-count under all integrated sources for the planning horizon, including the integrations that will be added during the term, and to contract for the headroom in the deal window. See the digital-access pillar for the document-count projection method.
The data-residency constraints
Data residency in RISE is set by the hyperscaler region and the specific data-centre election. Changes mid-term are operationally and contractually possible but produce a major-change event, which counts against the change-management ceiling and produces incremental professional-services consumption. For organisations with shifting regulatory geographies (banking groups subject to ring-fencing requirements, public-sector organisations subject to sovereignty rules), the data-residency commitment in the initial contract should be examined against the regulatory horizon, not just against the regulatory present. The RISE hyperscaler clauses article covers the residency mechanics.
The standing rate card
Behind the operational limits is a standing rate card that prices the consumption that exceeds the limits. The rate card is itself negotiable and is the single instrument that determines the cost of operational over-runs across the term. The headline price typically does not include the rate card; the rate card typically does not appear in the summary. Read the rate card line-by-line, compare to the projected over-run rates from the operational planning, and negotiate the rate-card values where the projection indicates meaningful exposure. The RISE contract negotiation tactics paper covers the rate-card negotiation in detail.
The compound effect
The individual operational limits are individually manageable. The compound effect is what matters. A storage true-up in year two, combined with a session-ceiling uplift in year three, combined with a change-event overrun across the full term, combined with a digital-access volume true-up in year four, can produce a cumulative cost overrun that exceeds the original contract by twenty to forty per cent across a five-year term. The case file at bank renegotiates RISE mid-term shows the compound pattern in detail, and the RISE topic page covers the broader operational frame.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
If your RISE contract is in negotiation, request the full operational schedule and the full standing rate card before the term-sheet conversation closes. If your RISE contract is already in operation, run the year-on-year limit usage against the original ceilings to identify the compound exposure. The contract negotiation service brief covers the operational-limits review in the broader negotiation method.