Client Profile
The client is a Massachusetts public university system operating four campuses across the state, providing undergraduate, graduate, and professional education to approximately 48,000 students. The system employs approximately 14,000 staff across academic, research, administrative, facilities, and student services functions. SAP has been the system's primary ERP platform for finance, HR, and procurement since 2009, with deployments across all four campuses managed through a combination of central IT and campus-level administrative teams.
Over fifteen years of operation, the SAP estate had grown incrementally. Each campus expansion, administrative restructuring, and departmental system integration had added named user entitlements to the system's SAP contract without a corresponding decommissioning process for accounts that were no longer required. By 2024, the system held entitlements for approximately 11,200 SAP named users across Professional, Limited Professional, and Employee licence types — a figure that the system's central IT leadership suspected significantly overstated actual active usage.
The Challenge
The university system's annual SAP licensing cost had reached approximately $11M, representing one of the largest single software contract commitments in the system's technology budget. The renewal of the system's enterprise SAP agreement was approaching, and SAP's account team had presented a renewal proposal that would increase costs by a further 8% through contractual price escalation provisions.
The CFO and CIO jointly commissioned a licensing review before engaging SAP on the renewal. The review's objectives were to establish the actual active user count across all four campuses, identify accounts that could be decommissioned or reclassified, and produce a defensible licence position for the renewal negotiation. The decentralised nature of the system's administration — with HR, payroll, and user provisioning managed separately at each campus — meant that no single system contained a reliable view of active SAP users across the enterprise.
The complexity was compounded by the presence of multiple contract vehicles. The system held SAP entitlements under a state-wide higher education framework agreement, a direct campus-level agreement from a 2018 expansion, and a supplemental agreement covering a specialist grants management module. The three contract structures had different pricing models, maintenance terms, and renewal dates — making rationalisation both more complex and more valuable.
The Approach
Redress Compliance conducted a cross-campus SAP usage analysis, extracting active usage data from each campus's SAP system and mapping actual login activity, transaction patterns, and role assignments against the named user entitlements held under each contract vehicle. The analysis applied a 90-day activity threshold, identifying accounts with no recorded login or transaction activity in the preceding 90 days as candidates for decommissioning, subject to HR verification.
The analysis identified 2,620 accounts that were either completely inactive (1,180 accounts), duplicate registrations for the same individual across two or more campuses (740 accounts), or mis-classified at a higher-value licence type than actual usage patterns warranted (700 accounts). HR verification confirmed that approximately 820 of the inactive accounts related to individuals who had left the university system, including retirements, faculty transitions, and administrative restructuring exits, but whose SAP accounts had not been deprovisioned.
Redress Compliance also conducted a detailed analysis of the system's licence type classification, comparing actual transaction patterns against the entitlement definitions for Professional, Limited Professional, and Employee licence types. A significant cohort of approximately 700 users — primarily in administrative support and departmental coordinator roles — were holding Professional licences despite transaction patterns consistent with Limited Professional entitlements. A reclassification programme was designed to migrate these users to the appropriate, lower-cost licence type.
The three contract vehicles were consolidated into a single system-wide enterprise agreement, simplifying governance, aligning renewal dates, and enabling volume pricing on the reduced user count. The renewal negotiation was conducted on the basis of the verified active user count of approximately 8,580, incorporating the reclassified licence mix and a five-year price freeze provision.
The Outcome
The university system's annual SAP licensing cost was reduced from approximately $11M to $7.6M — a 31% reduction. The reduction comprised decommissioning savings from inactive and duplicate account removal ($2.1M annually), reclassification savings from licence type corrections ($680K annually), and volume pricing improvements from contract consolidation and renewal negotiation ($620K annually). Total savings over the three-year period to the next renewal exceeded $10.2M.
The contract consolidation also simplified the system's SAP governance framework, with a single agreement, unified maintenance terms, and a clear entitlement register across all four campuses. The savings programme funded a formal S/4HANA migration assessment, which the system's CIO had previously been unable to advance due to budget constraints.
Key Takeaways
- Public university systems with multi-campus SAP deployments routinely carry 20–35% licence surplus from inactive and duplicate accounts. The combination of decentralised HR and user provisioning, multiple contract vehicles accumulated over years of system growth, and the absence of a central deprovisioning process creates structural licence surplus in higher education SAP environments. A systematic cross-campus usage review typically identifies material savings opportunities even in well-managed institutions.
- The 90-day activity threshold is a defensible and conservative standard for inactive account identification. SAP's own guidance acknowledges that accounts with no activity over an extended period can be decommissioned without licence obligation. A 90-day threshold, supported by HR verification, is routinely accepted by SAP in licence rationalisation discussions and is the appropriate standard for public-sector environments with seasonal patterns of system use.
- Licence type mis-classification is a consistent savings opportunity in administrative-heavy organisations. Professional licence types are frequently over-provisioned in university administrative environments, where a large cohort of departmental coordinators, grants administrators, and student services staff access SAP for a limited, well-defined set of transactions. A systematic transaction-pattern analysis routinely identifies 5–15% of the named user population eligible for reclassification to lower-cost licence types.
- Contract consolidation amplifies the savings from user count reduction. Organisations holding SAP entitlements under multiple contract vehicles — a common pattern in university systems that have grown through campus integrations — typically achieve additional pricing improvements through consolidation, beyond the savings from user count reduction alone. Volume pricing benefits and simplified renewal negotiations compound the financial impact of the licence optimisation programme.
- SAP renewal negotiations conducted before a formal usage review are conducted at a structural disadvantage. Without a documented view of actual active usage, renewal negotiations are conducted on the basis of Oracle's proposed terms, with no defensible counter-position. The investment in a formal usage review consistently delivers returns that dwarf the advisory cost.
University system or public-sector organisation approaching SAP renewal?
Redress Compliance has conducted SAP usage reviews for higher education institutions and public-sector organisations across the US and Europe — identifying licence surplus and negotiating renewal terms on the buyer's side.