Prometeon Selects Redress Compliance for Multi-Vendor Advisory and Negotiation Services

About Prometeon Tyre Group

Prometeon Tyre Group is one of the world's largest manufacturers of tyres for industrial, transport, goods movement, agricultural, and off-the-road applications. Headquartered in Milan, Prometeon operates manufacturing facilities and commercial operations across Europe, Latin America, the Middle East, Africa, and Asia-Pacific, employing approximately 6,000 people globally.

As a global manufacturer with a complex operational footprint, Prometeon relies on a large and heterogeneous enterprise software estate spanning enterprise resource planning, supply chain management, manufacturing execution, analytics, and infrastructure. Managing this estate across multiple jurisdictions, legal entities, and procurement cycles creates precisely the kind of complexity that vendors exploit in audits and renewals.

By 2022, Prometeon's IT and procurement leadership recognised that the organisation's multi-vendor software landscape had grown without commensurate contract discipline. Renewal cycles were misaligned, compliance positions across Oracle, SAP, Microsoft, and IBM were unverified, and vendor-led commercial proposals were being evaluated without independent benchmark data.

Why Prometeon Sought Independent Advisory

The decision to engage an independent advisor was driven by a combination of factors that will be familiar to most global manufacturers navigating large vendor portfolios.

Simultaneous Renewal Pressure Across Four Vendors

Oracle's Unlimited License Agreement renewal, SAP's S/4HANA migration discussions, a Microsoft Enterprise Agreement renewal, and an IBM ELA renewal were all falling within an eighteen-month window. Each vendor's account team was pursuing its own renewal agenda, often presenting proposals that expanded scope and cost rather than optimising the existing estate.

Managing four concurrent major vendor negotiations without independent commercial intelligence and negotiation support was recognised as a significant risk. Vendor account teams have deep expertise in their own licensing models and negotiation tactics. Without equivalent buyer-side expertise, organisations consistently leave value on the table and accept terms they could have improved.

Compliance Exposure Across Multiple Licensing Models

Large enterprises running Oracle databases across virtualised environments, SAP systems with complex user type classifications, Microsoft 365 with inconsistent deployment tracking, and IBM middleware in hybrid cloud environments are almost always carrying compliance exposures that are invisible without specialist assessment.

Prometeon's leadership was aware that each of their major vendors had licensing models of considerable complexity, and that the organisation's internal SAM function, while competent for routine licence tracking, lacked the depth of vendor-specific expertise needed to definitively assess compliance positions across all four vendors simultaneously.

Lack of Benchmark Data on What Peers Actually Pay

Vendor-provided pricing proposals are anchored to list prices and to whatever the vendor calculates is the maximum achievable based on the customer's profile. Without access to real transaction benchmarks showing what comparable organisations actually pay for equivalent products and volumes, it is impossible to evaluate whether a vendor's commercial proposal represents fair value.

The Engagement Structure

Redress Compliance was engaged to provide independent multi-vendor advisory across all four major vendors in Prometeon's estate. The engagement was structured in three phases.

Phase 1: Multi-Vendor Estate Assessment (Weeks 1–6)

The first phase focused on independently assessing Prometeon's compliance position and commercial terms across all four vendors. This involved detailed review of all current license agreements, order forms, and support contracts; analysis of deployment data against contractual entitlements; identification of compliance gaps and over-deployment risks; and benchmarking of current pricing against Redress Compliance's transaction database covering comparable enterprise accounts.

The assessment was conducted without vendor involvement. Prometeon provided deployment data and contract documentation; Redress Compliance's vendor-specific analysts conducted the assessment independently, ensuring that findings were not filtered through any vendor commercial lens.

Phase 2: Negotiation Preparation and Strategy (Weeks 7–12)

Using the assessment findings, Redress Compliance developed detailed negotiation strategies for each vendor engagement. This included identification of leverage points specific to each vendor relationship, recommended commercial terms for each renewal, risk quantification of compliance exposures and their negotiation value, and sequencing recommendations for which vendor negotiations to initiate first and in what order to proceed.

The sequencing question is often overlooked by buyers but is strategically significant. How you handle one vendor renewal can affect your leverage in another. The order in which you share information with vendors, and the timing of commitments, affects the competitive dynamics of each negotiation.

Phase 3: Negotiation Support and Execution (Weeks 13–18)

Redress Compliance provided direct negotiation support throughout all four vendor discussions, advising Prometeon's procurement and IT leadership on proposals as they were received, preparing counter-proposals and commercial arguments, and coaching the internal team on vendor tactics and how to respond to them effectively.

The advisory was buyer-side only. Redress Compliance takes no vendor referral fees, reseller commissions, or any form of remuneration from software vendors. This structural independence is not merely a compliance formality — it ensures that all recommendations are based solely on what is commercially optimal for the client.

Findings Across the Four Vendors

Oracle: ULA Exit Strategy and Virtualisation Compliance

Prometeon's Oracle estate included an Unlimited License Agreement that was approaching its certification window. Oracle ULA engagements require careful management at exit — the quantity of software deployed at the point of certification becomes the permanent licence entitlement, and how Oracle counts deployments in virtualised environments can materially affect the certified quantities.

The assessment identified deployment configurations in Prometeon's VMware environment that Oracle would likely count at full processor value rather than reduced sub-capacity counts. This was addressed prior to the certification process, reducing the compliance exposure and improving the commercial outcome of the ULA exit.

SAP: User Type Classification and Indirect Access

SAP's licensing model distinguishes between multiple named user types, and the correct classification of users — particularly those accessing SAP through third-party interfaces, middleware, or custom integrations — is a persistent source of compliance risk and audit findings. Prometeon's SAP environment included several integration scenarios where third-party system data was flowing into SAP processes, creating potential indirect access exposure under SAP's Digital Access licensing framework.

Redress Compliance's assessment quantified the indirect access exposure and developed an approach to reclassify integration scenarios under SAP's Document-based Digital Access model, which in most cases provides a more predictable and cost-effective licensing basis than named user exposure for integration volumes.

Microsoft: M365 Alignment and Azure Consumption Governance

Prometeon's Microsoft estate had expanded significantly through the pandemic period as cloud and collaboration workloads grew rapidly. The assessment found that certain Microsoft 365 SKU assignments had drifted from actual user needs, with some user populations licensed at E5 level for capabilities that were not deployed or actively used.

The Microsoft Enterprise Agreement renewal was renegotiated with right-sized SKU assignments for the actual user population, together with an Azure consumption commitment structure that provided volume-based pricing improvements on cloud workloads that were already running and growing predictably.

IBM: Sub-Capacity Deployment and ILMT Compliance

IBM's licensing for products deployed in virtualised environments offers significant cost advantages through sub-capacity licensing — but only if the IBM License Metric Tool (ILMT) is correctly configured and generating compliant audit snapshots. Without ILMT correctly configured and maintained, IBM takes the position that full capacity licensing applies to the entire physical host, regardless of how many virtual cores the software actually uses.

The assessment of Prometeon's IBM estate found gaps in ILMT configuration in two data centre environments where IBM middleware was deployed. These gaps meant that sub-capacity licensing was not validly claimed for those deployments, creating exposure to full-capacity back-billing in an IBM audit scenario. Remediation of the ILMT configuration was completed prior to the IBM ELA renewal, removing the exposure and enabling valid sub-capacity licensing claims going forward.

The IBM ELA renewal was restructured to remove products no longer in active use, right-size committed volumes against current deployment data, and include favourable terms for the PVU-to-VPC transition on products moving to IBM's newer licensing metric, where VPC (Virtual Processor Core) based licensing better reflects the actual consumption pattern of Prometeon's workloads.

Why Multi-Vendor Advisory Requires Specialist Depth

One of the most common mistakes enterprises make is to underestimate the depth of vendor-specific expertise required to effectively manage major software renewals. Each major vendor has a distinct licensing architecture, a distinct set of compliance risk vectors, and a distinct negotiation playbook.

Oracle's processor counting rules for virtualised environments, ULA certification mechanics, and Java licensing changes since 2023 are not interchangeable with SAP's user classification rules, Digital Access measurement methodology, and S/4HANA migration commercial levers. IBM's ILMT requirements, PVU-to-VPC transitions, and ELA structure are categorically different from Microsoft's EA true-up mechanics, E5 upgrade propositions, and Azure commitment models.

Effective multi-vendor advisory requires individuals who have deep expertise in each vendor's specific licensing model, audit mechanics, and negotiation dynamics — not generalists who understand software licensing broadly. Redress Compliance's practice is structured with dedicated vendor-specific teams, ensuring that Prometeon had access to the right depth of expertise for each concurrent engagement.

The Case for Independent Multi-Vendor Advisory

Enterprises managing complex multi-vendor software estates face a structural disadvantage in vendor negotiations. Vendor account teams are specialists in their own products, trained in negotiation, and incentivised to maximise contract value. Internal procurement teams, however capable, are generalists who engage with any given vendor perhaps every three to five years.

Independent advisory firms like Redress Compliance exist to rebalance this asymmetry. By bringing specialist expertise, transaction benchmark data, and vendor-specific negotiation experience to every engagement, independent advisors give enterprise buyers the ability to negotiate on equal terms. The return on investment from well-executed software advisory consistently exceeds the advisory fee by a substantial margin — in Prometeon's case, across four vendors and 14 countries, the commercial outcomes significantly exceeded the cost of the engagement.

The Prometeon engagement also illustrates a principle that applies broadly: the time to engage independent advisory is not when a vendor presents a renewal proposal, but well in advance, when there is still time to assess the estate, identify exposures, build leverage, and design a negotiation strategy. Advisory value diminishes significantly when it is brought in after the vendor has already anchored the conversation on their terms.

Engaging Redress Compliance for Multi-Vendor Advisory

Redress Compliance provides independent multi-vendor advisory across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom/VMware, AWS, Google Cloud, ServiceNow, Workday, and Cisco. All advisory is buyer-side only, with no vendor referral fees or reseller commissions in any form.

The firm operates across North America, Europe, the Middle East, and Asia-Pacific, with delivery teams that combine deep vendor-specific expertise with broad enterprise licensing programme experience. Engagements can be structured as standalone advisory for a specific vendor renewal, as multi-vendor programmes covering several concurrent negotiations, or as ongoing retainer advisory through the Vendor Shield programme, which provides continuous commercial governance across the enterprise software estate.

For global manufacturers, financial services firms, healthcare organisations, and public sector bodies managing complex multi-vendor software estates, the question is not whether independent advisory generates value — it consistently does. The question is whether the engagement is structured early enough, and with sufficient vendor-specific depth, to capture the full available commercial opportunity.