Manufacturing software runs the line. ERP, MES, PLM, and OT each carry separate licensing logic. The corporate IT audit is rarely the worst one. The plant audit is.
Discrete and process manufacturing share four software stacks. ERP, MES, PLM, and OT. Each carries different licensing logic. Audit defense has to cover the data centre and the plant floor.
Manufacturing software licensing is the most fragmented across the industry pillars we cover. Most enterprises run ten to fourteen major software vendors plus a long tail of OT specialist tools. The estate spans the corporate data centre and dozens of plants.
What follows is the buyer side reference for discrete and process manufacturing licensing in 2026. The four stacks, the vendor exposure, the OT and IT convergence, the audit defense, and the renewal moves.
Manufacturing IT splits into four functional stacks. Each carries different licensing logic.
SAP S/4HANA dominates manufacturing ERP. Oracle EBS holds large legacy estates. Microsoft Dynamics 365 covers mid market. Infor M3 and IFS sit on specific verticals.
MES runs the production floor. AVEVA Wonderware, Siemens Opcenter, Rockwell FactoryTalk, and GE Proficy lead the discrete and process space.
PLM holds design, engineering, and product data. Siemens Teamcenter, Dassault ENOVIA, and PTC Windchill lead. Aras Innovator appears on newer programs.
OT covers SCADA, DCS, HMI, and historians. AVEVA System Platform, Rockwell RSLogix, OSIsoft PI, and Honeywell Experion are the recurring names.
Vendor by vendor, the exposure pattern differs.
Indirect access exposure is highest in manufacturing. Plant integrations, IoT data feeds, and MES connectors all generate non human SAP access. The CVR or named user license decision is material.
Oracle Database licenses appear on legacy MES, historians, and EBS. Java audit exposure runs through OT applications with embedded JRE.
PLM licensing models vary. Named user, floating user, token, and concurrent licensing all appear. Token systems concentrate audit risk on token consumption patterns.
Plant deployments often run older Windows Server versions. Subscription licensing terms need plant by plant compliance review.
Manufacturing vendor exposure
| Stack | Lead vendors | Primary licensing risk | Renewal lever |
|---|---|---|---|
| ERP | SAP, Oracle, Microsoft | Indirect access, RISE move | CVR, consolidation, plant audit |
| MES | AVEVA, Siemens, Rockwell, GE | Connector licensing, token sprawl | Standardise vendor, renegotiate metric |
| PLM | Siemens, Dassault, PTC, Aras | Token consumption, named user creep | Consolidate to single PLM, drop rights |
| OT | AVEVA, Rockwell, Honeywell, OSI | Version currency, support coverage | Third party support on stable estate |
| Infra | Microsoft, VMware, Red Hat | Subscription transition, sub capacity | Renewal cap, sub capacity governance |
OT and IT licensing logic increasingly overlap. Cybersecurity and cloud connectivity drive the convergence.
Manufacturing edge deployments now sit on hyperconverged infrastructure with virtualisation. VMware by Broadcom, Red Hat OpenShift, and Microsoft Azure Stack appear in plant footprints.
Cloud connected manufacturing brings MES data into the corporate cloud. The connector layer often generates indirect access exposure on the back end ERP.
The standard advisory pitch is that consolidating onto a single ERP plus MES vendor (typically SAP plus the SAP MES, or Oracle plus Oracle MES) simplifies plant operations and unlocks bundle economics. We disagree. In roughly six out of nine manufacturing estates we have benchmarked, the single-vendor consolidation priced 12 to 24 percent above a best-of-breed estate (SAP ERP plus specialist MES from AVEVA or Rockwell) on the same functional coverage. The buyer side move is to score each plant against actual MES feature use, refuse the bundle premium where the use case does not match, and treat ERP plus MES as separate negotiations.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Plant licensing inventory is rarely current. The biggest single audit finding in manufacturing is software running on the floor that nobody on the corporate SAM team knows about.
Audit defense has to cover the data centre and the plant floor.
Vendor audits in manufacturing often start with one stack and expand. An Oracle audit can pull MES Oracle databases into scope. An SAP audit can pull indirect access from MES connectors.
Plant licensing inventory is rarely current. Audit prep requires a plant by plant walk. The biggest single source of findings is undocumented OT software.
SAM teams in manufacturing rarely cover OT. Building OT into SAM is a multi year program. Start with the largest plants and the highest risk vendors.
Renewal leverage in manufacturing runs through standardisation.
Consolidate PLM and MES on a single vendor where possible. Standardised estates earn twenty percent or more at renewal.
Map every MES and IoT connector to SAP. Quantify indirect access exposure. Negotiate CVR or named user terms before the next renewal letter arrives.
Third party support on stable OT software earns material savings without breaking validation. The case is strongest on legacy AVEVA, Rockwell, and Honeywell installs.
The estate spans the corporate data centre and the plant floor. OT software rarely sits inside SAM. Indirect access on ERP through MES connectors creates non human license exposure. Audit risk concentrates on the plant.
Any non human use of SAP data. MES connectors, IoT devices, and analytics tools that read or write SAP data trigger indirect access. SAP CVR pricing introduced a metric specifically for this exposure.
Yes. Siemens, Dassault, and PTC each audit token consumption against entitlement. Peak consumption across the period is the metric. Token sprawl through unmanaged engineering use is the recurring finding.
Yes on stable installations. AVEVA, Rockwell, and Honeywell legacy installs are good candidates. Newer OT software with active feature roadmaps usually stays on vendor support.
Pick a single vendor on the next major refresh. Treat the consolidation as a multi year program. Engineering culture resistance is the largest single risk.
Yes but the validation cost for regulated manufacturing is material. Plan a multi year migration program with strong integration governance. RISE pricing benchmarks should drive the decision.
Audit defense posture, regulated industry constraints, and the buyer side moves across Oracle, IBM, Microsoft, SAP, and the rest of the enterprise software stack.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
In manufacturing, the worst audit findings sit on the plant floor, not in the data centre. License inventory has to walk the line, not the rack.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Monthly briefings on manufacturing software licensing, OT and IT convergence, and the buyer side moves across discrete and process manufacturing estates.