Manufacturing organisations have traditionally drawn a clear operational distinction between Information Technology — the SAP ERP, Microsoft Office, and Oracle Database environments managed by the IT department — and Operational Technology, the SCADA systems, Manufacturing Execution Systems, DCS platforms, and PLC networks managed by plant operations and engineering teams. That distinction has been collapsing for a decade. In 2026, most large manufacturers have OT environments that run commercial operating systems, commercial databases, and commercial software stacks that create enterprise software licence obligations that neither IT nor operations teams have a complete picture of.
The result is a category of software licence compliance exposure that is entirely invisible until a vendor audit surfaces it. Oracle Database licences running beneath AVEVA PI historians. Microsoft SQL Server deployments on MES application servers. IBM Db2 databases within legacy SCADA platforms from the 1990s that are still processing production data. These are real, common scenarios in large manufacturing organisations — and they represent real, measurable licence compliance risk.
This article covers the primary IT licensing challenges specific to manufacturing environments and is part of our IT Licensing by Industry pillar series. For SAP-specific guidance, see our SAP Licensing Guide and SAP Digital Access article.
OT/IT Convergence: The Invisible Licence Obligation
Operational technology environments in manufacturing were originally proprietary — vendors like Emerson, Honeywell, Rockwell Automation, and Siemens built closed systems with proprietary operating systems and databases that created no commercial software licence obligations. The transition to open architectures beginning in the 2000s changed this permanently.
Modern SCADA, MES, and DCS platforms run on Windows Server or Windows Embedded, frequently use Oracle Database or Microsoft SQL Server as their data layer, and in many cases use IBM software components within legacy historian architectures. The commercial software licences required to run these platforms are often embedded in the OT vendor's original purchase price — but when manufacturers upgrade, expand, or migrate their OT infrastructure, they frequently create licence scope that extends beyond what the original embedded licence covered.
Oracle Database in OT Environments
Oracle Database deployments in manufacturing OT environments are a frequently overlooked source of significant licence compliance risk. The most common scenarios:
| OT Platform | Oracle DB Exposure Scenario | Licence Type Risk |
|---|---|---|
| AVEVA PI System (historian) | Oracle DB used as PI Archive or AF database backend | Processor licence on server hardware |
| Siemens SIMATIC IT (MES) | Oracle DB as MES data store | Processor licence — often virtualised (VMware risk) |
| GE Proficy (MES/Historian) | Oracle DB for production data storage | Named user plus if application users not counted |
| Honeywell PHD (historian) | Oracle DB versions embedded in older PHD deployments | Legacy licence scope vs. current processor count |
| Custom MES systems | In-house MES built on Oracle DB by previous IT teams | No valid licence records — complete gap |
Oracle's audit methodology does not distinguish between IT and OT deployments — an Oracle Database running beneath a SCADA historian is as auditable as one running beneath an ERP system. Manufacturers that have never inventoried Oracle software in their OT environment should prioritise this as an urgent compliance review.
Microsoft SQL Server in Plant Operations
Microsoft SQL Server is extensively deployed in manufacturing OT environments as the database backend for MES platforms, quality management systems, production scheduling tools, and laboratory information management systems (LIMS). Microsoft's licence model for SQL Server — Server+CAL or Core-based licences — applies to all commercial deployments including OT environments.
The specific risk in manufacturing is SQL Server on shared infrastructure. A SQL Server instance that serves both production MES users and SQL-querying IoT/sensor data aggregation may require different licence types than a purely user-accessed deployment. Microsoft's distinction between "user CALs" (per human user) and "device CALs" (per accessing device) becomes complex when industrial devices, PLCs, and data collectors access the same SQL Server instance that human MES users do.
SAP Digital Access in Manufacturing Environments
SAP's Digital Access pricing model — introduced in 2018 and now embedded in all new S/4HANA agreements — creates specific and substantial licence exposure for manufacturers. Digital Access charges are triggered by digital documents created in SAP systems through indirect access (non-human user interactions). Manufacturing environments generate enormous volumes of these interactions:
- IoT sensor data streams that write production readings to SAP
- MES production order confirmations flowing into SAP PP
- Supplier portal EDI transactions creating purchase orders or delivery confirmations in SAP MM
- Quality inspection results from laboratory systems integrating with SAP QM
- Logistics tracking events from WMS or carrier systems updating SAP delivery records
Each of these digital interaction types corresponds to a specific SAP document type with an associated Digital Access price. SAP prices Digital Access documents at $0.02–$0.15 per document depending on document type, with volume discounts available through Digital Access bundles. For a manufacturer processing 50 million digital document interactions annually — a realistic figure for a mid-size production operation — uncapped Digital Access exposure can reach $1M–$5M annually.
Critical risk for legacy SAP customers: Manufacturers that licensed SAP before Digital Access pricing was introduced and have not renegotiated their licence agreement may face Digital Access liability calculated retroactively from 2018. SAP has pursued this position in audit contexts against manufacturers with large indirect access footprints. Proactive Digital Access quantification and negotiation is far preferable to reactive settlement. See our SAP Digital Access Guide for the full framework.
Shift-Worker User Counting: SAP and Oracle Named-User Models
Manufacturing workforces operate in rotating shift patterns — typically three shifts of 8 hours, or two 12-hour shifts — where the same workstation is used by different workers across a 24-hour period. This creates a fundamental tension with enterprise software licence models that price on named users:
SAP's named user model requires individual licence assignments per person who accesses the system. In a three-shift manufacturing environment where 300 production workers access the same MES-to-SAP interface across three shifts, SAP's named-user interpretation requires 300 individual user licences. Concurrent user alternatives exist in SAP's portfolio but are priced higher per seat and are not always commercially available on legacy agreements.
Oracle's Named User Plus (NUP) metric has a minimum ratio requirement — a minimum of 25 NUP licences per processor — that sometimes makes NUP pricing less economical than processor licensing for manufacturing workloads with large production-floor user populations accessing Oracle systems.
The most effective approach for manufacturers is to explicitly map workforce access patterns to licence metrics before ERP renewal, and to negotiate access models that reflect operational reality — concurrent user licences, shift-based access profiles, or device-based licensing — rather than defaulting to named-user pricing that creates inflated licence counts for shift environments.
SAP S/4HANA Migration for Manufacturers
Most large manufacturers running SAP ERP or SAP ECC 6.0 face a migration to SAP S/4HANA before SAP's mainstream maintenance end in 2027 (extended to 2030 through optional maintenance extension). The S/4HANA migration for manufacturers is not merely a technical upgrade — it is a complete renegotiation of the SAP commercial relationship that should be treated as such.
S/4HANA introduces RISE with SAP as Cisco's preferred migration path, bundling HANA cloud infrastructure, S/4HANA licences, and SAP managed services in a subscription model priced per unit of production output in some manufacturing-specific configurations. Manufacturers should independently evaluate RISE pricing against alternatives — S/4HANA on-premises, S/4HANA on hyperscaler IaaS, or a phased selective data transition — before accepting SAP's initial proposal.
S/4HANA migration is also the moment to address Digital Access exposure proactively: negotiating a Digital Access bundle before migration, with volume tiers appropriate for your manufacturing document volumes, is significantly more cost-effective than paying Digital Access usage charges after go-live. See our SAP RISE Negotiation Guide for the commercial strategy.
ERP Negotiation Strategies for Manufacturers
Manufacturers face a distinct challenge in ERP vendor negotiations: operational dependence on SAP or Oracle ERP systems limits genuine competitive leverage in a way that point solution buyers do not face. A bank can credibly evaluate Oracle-to-PostgreSQL migration for analytical workloads; a manufacturer that has run SAP for 20 years and integrated it with 50 production systems cannot credibly threaten complete SAP displacement in a 90-day negotiation window.
Effective ERP negotiation for manufacturers therefore focuses on different leverage mechanisms. First, Digital Access quantification: conducting a precise Digital Access document volume analysis before SAP renewal and presenting it as part of a renewal package negotiation gives manufacturers factual grounding to negotiate bundle pricing rather than paying usage rates. Second, competitive ERP pilots: manufacturers evaluating process modules (HR, procurement, analytics) on cloud platforms can use these evaluations as leverage in SAP or Oracle discussions without threatening core ERP replacement. Third, specialist advisory: firms such as Redress Compliance specialise in manufacturing SAP and Oracle negotiations, bringing both the ERP commercial knowledge and the OT/IT licensing expertise that general advisors lack. Manufacturing clients working with specialist advisors achieve 28–38% average savings on ERP renewals.
For the complete SAP negotiation framework, see our SAP Licensing Complete Guide. For Oracle negotiation in manufacturing, see our Oracle Licensing Guide.
Manufacturing IT Licensing Action Plan
- Conduct an OT environment Oracle and Microsoft SQL Server inventory — treat OT deployments as in-scope for software asset management
- Quantify SAP Digital Access document volumes across all indirect access integration points before next SAP renewal
- Map shift-worker workforce access patterns to licence metrics — validate that named-user counts reflect actual workforce size, not inflated shift assumptions
- Evaluate S/4HANA migration commercial options independently before accepting RISE with SAP pricing
- Negotiate Digital Access bundles proactively — address the exposure before SAP surfaces it in an audit request
- Engage manufacturing-specialist licensing advisory for major ERP renewals — sector-specific expertise delivers measurably better outcomes than generalist procurement support