Understanding your IBM Contract, six key points

IBM

Understanding your IBM Contract, six key points

This article was contributed by Katerina Motlova of Fisher ITS.

Like many major software publishers, IBM contracts can be long and complex. This is usually true for larger customers who will hold an Enterprise Software & Servicing Offering (ESSO) agreement, rather than a standard Passport Advantage contract that other IBM users will be issued with.

If you do not read and understand your IBM contract, then you cannot hope to take advantage of it. It is often the case that a contract will be signed by a colleague in Procurement or even the CIO, and the SAM team will not receive important information such as reporting requirements or advantageous commercial terms that allow for future investments to be paid for out of pre-allocated pots of money.

Contract terms vary from vendor to vendor, and IBM customers should not assume that because you are familiar with a publisher such as Microsoft, you have an automatic understanding of IBM licensing terms and definitions.

To take full advantage of your IBM contract, here are six points I recommend that you review.

IBM Contract Amendments

When a customer’s contract needs to be updated, IBM will add an amendment, rather than voiding the current contract and starting again. The amendment will contain the information that you need to understand for any changes that have been made to the body of the contract.

Some amendments are more important than others. In some cases, an amendment will be updating a small change to the conditions of the contract, in other cases the amendment will be voiding and updating half of the body of the contract. This is an area where IBM customers can often be caught out if you do not consider the body of your contract together with all the amendments.

It is important to distinguish between amendments that extend the contract and amendments that change the conditions of a contract. When a contract is extended, IBM will usually add an amendment to confirm the extension, unless the customer insists on a brand-new contract agreement. Other amendments will not change the fundamental conditions of the contract, they may be there to add additional functionality or a new purchase into the contract.

IBM Contract Definitions

IBM includes a section in each contract to define the terms used throughout the document. Yes, this is the boring bit of the contract, but it is helpful and better than some other vendors such as Oracle, who do not usually provide a clear explanation for the technical language as part of the contract.

It is important to remember that there may be differences between a generally accepted SAM definition of a term, and the IBM definition. IBM also has slightly different definitions for some terms compared to other vendors such as Microsoft. Sometimes we see IBM customers fall into a false sense of security by believing they understand the IBM contractual language based on a familiarity with other vendors. It is best not to assume you know what IBM terms such as ‘capacity, resource or authorised usage’ mean and refer to the contract definitions so that you are sure.

Substitutions Pots

Substitution Pots and Cross-Brand Allotment (see below) are usually the two biggest instruments we see in an IBM contract. When an organisation aims to reduce spend with IBM due to changes in the business or a reduced need for licences, IBM may offer the use of a list of ‘Substitutable Programmes.’ This is also commonly referred to as ‘Substitution Pot’.

IBM will keep the money to the value of the current contract (or as close to the original value as possible), but offer the difference as a form of credit, allowing the customer to purchase certain licences from this ‘pot’ of money.

Substitution Pots are used for IBM customers with an ESSO agreement which includes a set list of licences. When some of these licences are no longer used, they can be swapped out with the items listed on the Substitution schedule – bear in mind that once swapped, you will lose the original licence.

Substitutable Programmes are listed in an organisation’s ESSO agreement, meaning an IBM customer cannot use Substitution Pot money for any other purchases. Normally once a licence is procured via substitution, it becomes part of the customer’s portfolio and it cannot be ‘returned’ via another substitution. Substitutable Programmes can be a useful tool to use for new licence ‘purchases’ e.g. for testing purposes or future expansion of your IBM estate.

IBM customers should consider their Substitution Pot before buying new licences – checking whether there is anything no longer needed that can be swapped out first, before paying cash. This may sound basic and obvious, however, time and time again we see organisations who do not realise they have a Substitution Pot, or the one person who does know is not involved in IBM procurement decisions in other areas of the business. Money in Substitution Pots is easily wasted unless carefully managed so a centralised process for decision making on new licences is vital for all large contracts.

Cross-Brand Allotment

This is effectively a pre-paid credit pot: you can use this pot of money to buy any IBM software, sometimes even hardware and services. Cross-Brand Allotment is similar to Substitutable Programmes, but often better for a customer as it will contain fewer limitations on how the money can be used. Unless listed otherwise, a customer can choose products from the full IBM catalogue. Usually, Cross-Brand Allotment can be used to pay for mainframe purchases or services as well.

Customers should ensure they read and understood the conditions for using Cross-Brand Allotment to be able to utilise it correctly. Cross-Brand Allotment is typically made available in stages so you might not have access to the full amount right at the beginning of your ESSO. If you do not utilise the Cross-Brand Allotment money available during the allocated time period, YOU WILL LOSE IT.

Audit Clause

IBM do not use the word ‘audit’ in their contractual language, instead, they refer to the audit process as ‘verification.’ It is important to read and understand this clause as it may differ in an ESSO agreement compared to the standard language used in a Passport Advantage contract. Whatever the wording, every contract will have an audit clause.

The standard Passport Advantage audit clause is very simple, stating that IBM can audit the customer and the customer is responsible for providing data within a reasonable timeframe.  However, the verification language in an ESSO agreement may be a bit more complicated and have additional terms. This can include a ‘non-audit timeframe’ or other reporting responsibilities. The verification clause in a customer contract will supersede any other clauses referring to auditing elsewhere.

Product List

An IBM contract will usually include a list of products that the customer is purchasing through the contract. This will be a table at the end of the contract listing the quantities of each product purchased. It will also include a list of products for which the customer is extending support through that contract. The support may be extended for the entire length of the contract or just one or two years depending on what the customer has agreed. That is important to check, alongside Passport Advantage, to obtain a complete record of your IBM licensing entitlement.

In some cases, a customer may not have access to all the Passport Advantage sites for their organisation. Using the information in the contract is a good way of understanding if there are licences that are not showing within the Passport Advantage sites that the customer has access to. This can help you discover if you are missing access to an important site.

This article was contributed by Katerina Motlova of Fisher ITS.

Can’t find what you’re looking for?