Background and Industry Licensing Landscape
SAP's licensing model is traditionally two-fold: Named User licences (assigned per individual accessing SAP) and Package/Engine licences (measured by business metrics for specific modules or industry solutions). Under SAP ECC, many core EAM capabilities were included in the base ERP licence, but certain extended functionalities or industry add-ons require separate "engine" licences. For a comprehensive overview of SAP licensing fundamentals, see our SAP Licensing Knowledge Hub.
🏭 Industry Solutions (IS) — Metric-Based Licensing
SAP's Industry Solutions for sectors like Oil & Gas, Retail, and Utilities are extensions to the core ERP, licensed based on usage metrics aligned with industry-specific business volumes. Unlike generic modules counted by users, these tie licensing to functional capacity measures: a Retail solution might be licensed by number of stores or POS locations; an Oil & Gas solution by annual throughput (barrels of oil, number of wells); a Project Systems solution by active projects or budget volume. SAP has over 100 different metrics defined in its price list for various engines.
| Industry / Module | Typical Licensing Metric | What It Measures |
|---|---|---|
| IS-Oil & Gas (Downstream) | Annual throughput volume | Barrels refined/processed through system |
| IS-Oil & Gas (Upstream) | Number of wells managed | Active wells in SAP |
| IS-Retail | Number of stores / POS locations | Active retail sites in system |
| IS-Utilities | Number of connections / meters | Active utility connections managed |
| Project Systems (PS) | Number of active projects or budget volume | Project portfolio scope |
| Manufacturing (MII) | Number of plants | Factory sites with integration |
| EHS Management | Number of sites | Locations with EHS deployment |
| Global Trade Services | Number of documents / orders | Trade compliance documents processed |
The S/4HANA Transition
With SAP S/4HANA, SAP has simplified some core licensing but introduced changes in how industry and EAM functionality is packaged. S/4HANA's "Digital Core" is licensed primarily by user count/type for general ERP functionality — many traditional modules (finance, procurement, manufacturing, basic Plant Maintenance) are included. However, Line-of-Business (LoB) and industry solutions in S/4HANA often remain separately licensed engines, much as they were in ECC. Moving to S/4HANA doesn't automatically eliminate engine metrics.
SAP Industry Cloud Evolution
The landscape is evolving with SAP Industry Cloud offerings. In asset management, SAP now provides cloud-based solutions under the Intelligent Asset Management umbrella: Asset Intelligence Network (AIN) for collaborative asset data, Predictive Maintenance and Service (PdMS) for IoT-based maintenance, and Field Service Management (FSM) for service operations. These are cloud subscriptions separate from on-premise ERP licences, each with metrics aligned to cloud models — number of assets, per technician, sensors monitored. CIOs must now manage a hybrid licensing landscape: traditional on-premise licences for core ERP/EAM, and subscription licences for cloud extensions.
Need help navigating SAP's complex licensing landscape?
SAP Licence Optimisation →Key Licensing Models and Risk Factors
Licensing Models for SAP EAM and Industry Engines
👤 Named User Licences
Assigned to individuals accessing SAP. Different categories — Professional User, Limited Professional, Employee Self-Service, Worker — come at varying price points depending on scope of activities. In EAM context: maintenance planners/engineers typically require Professional licences (full access to create work orders, manage maintenance plans, run reports); shop-floor technicians may operate under a lower-tier licence if they only record confirmations or time. S/4HANA introduced new user categories (Functional, Productivity, Developer) that roughly map to the old model with slight differences. For detailed analysis of SAP user type optimisation, see our SAP Named User Licence Optimisation Playbook.
📦 Package/Engine Licences
Cover specific functional solutions measured by usage metrics rather than per user. Common metrics for manufacturing and asset-intensive industries include: number of plants or locations, annual throughput or production volume, number of projects or project cost volume, number of assets/equipment, number of sales orders or documents, and even revenue or spend. These metrics directly tie licence costs to business activity levels — SAP charges in proportion to business value derived.
Risk Factors in Managing Metrics and Entitlements
🚨 Complex Metrics and Tracking Challenges
Unlike user licences (which SAP's auditing tools count automatically), many engine metrics require the customer to measure their own usage. SAP provides USMM and LAW (System Measurement tool and Licence Administration Workbench) for users and some classic metrics, but not all usage metrics are automatically captured. SAP cannot automatically "know" how many barrels of oil you processed or how many projects you ran. Contracts often rely on an honour system with annual reporting — opening risk of inadvertent non-compliance. Business growth (new plants, increased output, more projects) directly translates to a need for more SAP licences under these models.
⚙️ EAM Usage Overruns
Consider scenarios: number of maintenance objects (equipment, functional locations) growing significantly, project portfolio expanding beyond expectations — if tied to licence caps, overruns occur. A subtle risk: some EAM functionality may be technically available in S/4HANA without additional licence keys (the software isn't physically modular), so teams might start using features not included in their contract. S/4HANA includes basic Maintenance Management in the core, but features like advanced Maintenance Scheduling or Asset Strategy may require additional licences. Enabling these for testing or use without licence coverage creates compliance exposure.
🔗 Indirect Access and IoT Integration
Many industrial companies integrate SAP with shop-floor systems, IoT sensors, or external maintenance contractors. A sensor triggering a maintenance notification in SAP or a third-party field service app creating service orders constitutes indirect usage. SAP's Digital Access rules require either proper user licences for those interactions or adopting SAP Digital Access Document licensing (counting documents created by external systems). A wave of IoT-driven predictive maintenance alerts could generate thousands of documents requiring licence coverage. See our Top 10 SAP Digital Access Pitfalls for mitigation strategies.
🔄 S/4HANA Migration — Entitlement Gaps
When transitioning from ECC to S/4HANA, significant risk around licence conversion. SAP's Product Conversion approach allows converting ERP Package licences to S/4HANA at equivalent value, but explicitly excludes industry engines, which must be licensed separately on S/4HANA. If already in use, SAP may offer credits or migration discounts — but it's not automatic, it must be negotiated. Missing this can lead to unexpected costs when engine usage is discovered in the new system. For context on S/4HANA migration licensing, see our RISE with SAP Negotiations Guide.
💰 Cost Creep from Industry Cloud Additions
Adopting SAP Industry Cloud solutions for EAM (AIN, PdMS, FSM, Asset Manager mobile) adds subscription costs that can overlap with on-premise EAM capabilities. Without planning, you pay for redundant capabilities — e.g. implementing SAP FSM (per technician) while maintaining legacy on-prem customer service module, or adopting AIN without fully realising the value of OEM collaboration. Some cloud services charge based on usage volume (interactions, data storage for telemetry) — without governance, costs scale quickly.
📚 Related Reading
Strategic Recommendations
Build a Comprehensive Licence Inventory & Usage Baseline
Document all Named User licences (by type and quantity) and all Package/Engine licences (module name, metric, licensed volume). For each EAM-related module or industry engine, identify how usage is defined in the contract — does "number of plants" mean manufacturing plants only or any physical site? Baseline current usage against entitlements using SAP's measurement tools for what they cover and custom reports for specific metrics (counting facilities, total throughput). This baseline highlights areas near or exceeding entitlements. Treat it as a living document updated at least annually or whenever significant business changes occur (acquisitions, new plant go-lives, geographic expansion).
Implement Ongoing Metrics Tracking and Compliance Checks
Institute a process (with assigned ownership — Licence Manager or SAM team) to continuously monitor key usage metrics. Integrate licence metric checks into business processes: if you have entitlement for 10 production plants and plan to open an 11th, there should be a trigger to review licensing before activation. Build dashboards tracking throughput KPIs monthly against contract limits. Run SAP's annual measurement (LAW) diligently and conduct more frequent internal reviews (quarterly). Implement periodic attestation where managers confirm their reports' SAP usage — catching if someone now needs a Professional licence due to expanded duties.
Optimise Licence Allocation and User Types
Conduct a licence optimisation exercise: analyse usage logs to identify users holding expensive Professional licences who only perform display or simple tasks — potential downgrades to lower categories. Conversely, verify no critical users are on too-low licences (compliance risk). Check if you have engines licensed that you aren't fully using — negotiate reduction or redeploy that budget. Align licence types closely with job roles: maintenance technicians recording work done may suit "Employee" or Worker licences instead of full Professional. Document decisions and tie SAP user provisioning to licence assignment. For detailed strategies, see our SAP Named User Optimisation Playbook.
Strategise S/4HANA Migration with Licensing in Mind
Well in advance of any migration, map every SAP product/component in ECC to its S/4HANA equivalent. Identify any ECC engines or industry solutions that won't have a one-to-one inclusion in S/4HANA's core. Under Product Conversion, SAP allows converting existing ERP Package licences to S/4 at equivalent value — but industry engines are explicitly excluded and must be licensed separately. Negotiate to preserve entitlements: SAP has offered discounts and "grandfathering" of rights. Consider Contract Conversion for complex portfolios — sometimes offsetting 100% of previous investments. Do not retire your ECC contract or terminate maintenance until the new S/4 contract covers all critical functionality.
Preserve and True-Up Industry Engine Entitlements During Migration
Create a crosswalk document: "ECC Engine X (metric Y, licensed quantity Z) → S/4 Engine or equivalent." Use this to drive negotiations — e.g. if you have 5 plants licensed for IS-Oil downstream, your S/4 contract must explicitly allow at least 5 plants for the S/4 Oil solution. If any existing engine is being phased out by SAP (replaced by a newer cloud service), ask for entitlements to that new service as part of the deal. Track compatibility licence expirations carefully and have a roadmap to fully migrate to S/4-native modules before deadlines. Treat licence migration as a project workstream with contract review, pre-migration audits, SAP proposals, and post-migration true-ups.
Evaluate SAP Industry Cloud Solutions in TCO Calculations
For AIN, PdMS, FSM, and SAP Asset Manager, conduct a business case and TCO analysis: quantify expected benefits (reduced downtime, improved efficiency) vs subscription costs. Understand pricing models: AIN often uses tiered subscriptions by asset count; FSM charges per technician; predictive maintenance may price per equipment or sensor monitored. Include these in long-range IT spending plans. Negotiate bundle deals if adopting multiple cloud services — SAP can offer better rates for the entire Intelligent Asset Management suite. Coordinate with on-premise licence reductions: if FSM replaces SAP CRM Service, retire those user licences to avoid paying twice. For RISE with SAP considerations, see our SAP RISE Advisory service.
Strengthen Governance and Communication
Establish governance so any project that could impact SAP usage (new implementation, adding production lines, connecting third-party systems) triggers a licence impact review. Communicate importance of licence compliance to operational teams — spinning up extra SAP clients or using advanced modules has licensing implications. Establish a governance board reviewing licence usage reports, approving purchases/reallocations, and ensuring alignment with business strategy. Maintain documentation of how you calculate each metric for engines — demonstrable methodology makes audits smoother. Monitor SAP's licensing policy updates: SAP Agreement Resources and RISE bundling changes can open opportunities to simplify your licensing landscape.
Concerned about SAP engine licence compliance?
SAP Audit Defence Service →CIO Action Plan: Next Steps
Audit Your SAP Landscape
Compile a detailed list of all SAP EAM modules and industry-specific add-ons in use (ECC and S/4HANA). Document the licence metric and current entitlement for each — e.g. "Plant Maintenance: covered under core ERP, 500 Professional users" or "IS-Oil upstream: licensed for 50 wells."
Establish a Licence Tracking Process
Assign responsibility to a licensing specialist or team for monitoring usage metrics on a regular schedule. Set up reports or dashboards tracking key metrics (active plants, throughput volumes, project count, asset count) and review quarterly against licence limits.
Train and Communicate
Educate relevant stakeholders (IT, operations, plant managers, project management office) about licence metrics that affect them. Ensure plant managers know adding a new site triggers a licensing review; project office is aware that project count limits exist. Encourage a culture of checking with the IT licensing team before significantly expanding SAP usage.
Optimise User Licensing
Perform a user licence review to ensure each SAP user has the appropriate licence type. Adjust classifications to eliminate under- or over-assignment. Integrate licence type assignment into user provisioning and conduct periodic recertification of roles vs licences.
Plan S/4HANA Migration Licensing
If an S/4HANA upgrade is on the horizon, start mapping current licences to S/4HANA equivalents now. Engage SAP early to discuss conversion options. Prepare a negotiation strategy to secure all necessary entitlements, leveraging existing investments. Secure contract addenda guaranteeing use rights for critical industry functions in S/4HANA.
Budget for Industry Engines and Cloud Services
Forecast future usage of industry engines (adding plants, expanding output) and include potential licence expansion costs in IT budget. Evaluate SAP Industry Cloud offerings (AIN, PdMS, FSM) — request pricing and incorporate subscriptions into a five-year TCO model before adoption. Present costs alongside expected benefits for informed executive decision-making.
Leverage Tools and Partners
Use SAP's tools (USMM, SLAW) to run internal licence measurements. Consider third-party Software Asset Management solutions for SAP to automate usage tracking and optimisation recommendations. Engage specialised SAP licensing advisory services to validate compliance and identify savings — an external perspective uncovers contract quirks and negotiation opportunities.
Monitor and Adapt
Set a calendar for periodic licence compliance checks (at least annually, with mid-year internal audit). Watch SAP's updates — if SAP changes metric definitions or announces new bundles (RISE, industry-specific cloud packages), reassess whether it benefits your strategy. Adjust licensing plans as business strategy evolves.
Maintain Executive Oversight
Brief the CIO and business leaders regularly on SAP licence status — including risks (e.g. "we are at 90% of our licensed oil throughput volume") and planned actions. This keeps licensing on the radar as a strategic aspect of IT management and ensures support when investing in additional capacity or new solutions.
SAP EAM and industry engine licensing rewards CIOs who invest in understanding their metrics, actively tracking compliance, and planning ahead for transitions. By building comprehensive licence inventories, implementing ongoing monitoring, optimising user type allocations, preserving entitlements during S/4HANA migration, evaluating Industry Cloud TCO, and strengthening governance, organisations turn licensing from a reactive compliance concern into a proactive strategic advantage — supporting growth while avoiding compliance landmines and unwelcome cost surprises.
📂 SAP Case Studies
🔧 SAP Advisory Services
📄 White Papers & Resources
Need Help with SAP EAM & Industry Engine Licensing?
Whether you need guidance on SAP engine licence metrics, help navigating S/4HANA migration entitlement preservation, audit defence for industry-specific compliance exposure, Digital Access advisory for IoT integration, or contract negotiation support for SAP renewals — our independent SAP licensing specialists deliver results and save you millions.
💡 Download our SAP licensing white papers for actionable strategies
View White Papers →