ELP stands for Effective Licence Position and is related to a specific software vendor or product.
The basic premise for forming an ELP involves comparing your entitlements (what software you have purchased and are allowed to use and the way in which you are allowed to use it), with your deployments (how it is actually installed on your estate and how it is being used).
Firstly, you will need a full inventory of your software assets; the licences you have purchased and the maintenance you are now paying for. For this you will need to see signed contract agreements and/or purchase orders. You will need to understand the metrics used for licence entitlement such as, by processor, employee or named user etc.
Secondly, you will need to use tools to find out how many copies of the product have been deployed, to what environments, how many are being used, where they are located, what the specification of the hardware is and a number of other factors. The complexity of the demand data to capture will be based upon the metrics the licences are based upon. If no discovery/investigative tools are available here, then the data will need to be captured manually.
Thirdly, both sets of data will need to be compared to allow your organisation to see where it may be over- or under-licensed; presenting opportunities for improvements in licence compliance.
For complex products there needs to be a high degree of product knowledge to undertake this. To ensure you are compliant and can fend off an audit, the ELP must be created in such a way that the data collected can be presented to a vendor to support your position.
Being able to create an ELP is fundamental to keeping on top of your product compliance for audit defence and to support ongoing SAM activities such as optimisation and cost control.
For further information on ELPs and how to create them please Contact ITAMS.
Is your software asset data providing you with the right information to help you make informed decisions for your business?
In this post, ITAMS’ consultants define “data”, what data elements support IT asset management (ITAM) and what the data model comprises of for effective licence and compliance management.
Accurate, complete, and timely data is essential for reliable licence and compliance management. Regardless of how many sources you have, data coming into your asset repository must be of sufficient quality, quantity and coverage.
Data quality is the measurement of the correctness and completeness of data elements across all entities and the applications of standards, including attributes therein. When data is generated across multiple systems and then brought into the repository, where there are multiple data elements mapped to a single attribute, the data should, according to best practices, have the same format, i.e. Date = DD/MM/YYY.
Data quality also refers to the age of the data; it must be generated and transported in a timely fashion which supports the asset needs. Timeliness of data will depend on the asset (licence) and business requirements.
Data quantity then, is the measurement of the number of relevant data elements you have available to map against each entity. For example, if you are trying to create an asset profile, but all you have available to you is the product name and the date acquired, then you have insufficient data quantity. In order to create an asset profile, you would also need: PO number, SKU number, cost etc. Without the correct data quantity, your assets will not be complete.
Data coverage refers to the measurement of the availability of data elements, entities across the entire organisation in all environments and platforms. In order to generate a correct view of your assets, you must have data on Wintel, UNIX, Development and Test, Production, Disaster Recovery, Infrastructure, Regional Data etc. Unless you limit the scope of your SAM Service, you must have sufficient coverage for asset data.
Data elements in support of ITAM (of which SAM is a subset), must:
- Include all relevant data, not just software asset and licence data.
- Support all IT asset views resident in different technologies:
- Support specific requirements for analysis and reporting.
– Acquired (IT asset & licence repository).
– Installed (inventory discovery).
– Used (usage metering).
– Entitled (access authorisations).
The data model is comprised of:
- Entities – e.g. asset, contract.
- Elements (fields) – e.g., asset name, asset type.
- Definitions (purpose, intended content).
- Standards for key data elements – e.g., asset status.
- Attributes – e.g., alphanumeric, character.
- Links between entities – e.g., assets to licences to contracts.
- Relationships amounts entities – e.g., ‘installed on’, ‘assigned to’.
- Sources (systems-of-record) for each entity, possibly element.
Without data, your technology will not support your business requirements and be unable to provide you with the reporting and analysis information needed to make qualified decisions regarding your assets.
For more information about SAM data analysis services, please contact ITAMS.
ITAMS’ Licensing Analyst Sergiu provides an insight into the Oracle Licence Inventory.
The Oracle audit process represents a series of steps. The basis for this is Oracle’s so called “Licence Inventory”, although other software vendors may refer to it as ‘licence repository’/ ‘entitlement’, etc.
The Oracle licence inventory report is an excel spreadsheet summarising the licence products purchased by a particular customer and also a comprehensive overall picture of the historical support and licences.
How is this report used?
The report is used by Oracle Licence Management Services (LMS) consultants as a primary verification tool against which the original contracts are checked, in order for them to build a clear, simple and complete software repository. Later on, this will act as a guide for Oracle field consultants when managing their clients’ software accounts.
Grouped in several tabs, the information is based on the contract migrations report data and product migration rules. As a customer, special attention should be paid to your reference information, such as the correct spelling of names and ensuring that the address you have registered is the correct one. Also, pay particular attention to the status of your licences (if they are active or inactive) and the licence metric name of each licenced product.
Can the customer obtain this information from Oracle?
In 90% of cases, the customer will receive a “customer facing document”, where details about Oracle’s licencing audit report can be found. Included is a licence table (a simplified format of the licence inventory), nonstandard clauses (found in the original contracts), definitions of the licence metrics that the customer is licensed on (taken either from the original contract or from Oracle’s price lists) and finally, the minimum number of users /devices required for every software product (so these can be correctly licenced).
As Oracle consultants build the customer repository using different systems, sometimes the information lacks accuracy, so the customer should pay extra attention to ensure that the details contained in the inventory are correct.
For the customer, the most sensitive information to check is related to:
- Product name
- Licence Level
- Licence Term
- Support status
- Licence ownership
- Duplicate products.
For a customer to have a clear licencing position, they should ensure they have:
- A tool that is capable of tracking all software licences currently in use.
- Identified all the deployed licences across the organisation’s network. (Oracle uses measurement scripts which may be provided (but not in all cases). Customers must ensure that they know what the outputs are and that an expert is working on that.)
- Built and maintained a report with detailed information on licence use. In other words, keep track of licence use internally.
- Started comparing entitlement and deployment on a regular basis in order to have a strong compliance position.
After all the above are taken in consideration, the customer should have a clear view of whether they are under-licensed and need to acquire extra licences or whether they are over-licenced and need to uninstall licences.
Managing software assets can feel like an endless maze if you don’t know how to approach licensing information. Remember creating an efficient SAM process takes a lot of time and needs dedicated resources.
ITAMS’ Strategic Advisory Services have been designed to help you navigate through the difficult challenges of controlling and managing software asset ownership and utilisation
Amongst the variety of services we offer the “Data Fit for Purpose Testing” Service in particular is pertinent to helping you understand the quality of your data.
The service performs a high level review of the data quality in your major data sources and highlights any data quality issues. Once these are identified ITAMS’ experts are able to make informed recommendations on how these issues can be addressed. To find out more about the, “Data Fit for Purpose Testing” service please call: 0870 4050508 or email: firstname.lastname@example.org
ITAMS always delivers its services as an independent service provider. For more information or expert advice on any of the topics above please contact ITAMS.
Are you using the right asset to manage your licensing entitlement?
A common issue ITAMS’ consultants come across when helping clients build a SAM / licensing programme is the conflicting records found for a given asset, normally from different data sources. The data sources often include various tools such as discovery, security, patching and software distribution, results from physical audits or barcoding solutions, as well as entries in CMDB etc.
The conflicted records provide limited coverage and are most likely to be out-dated, posing a threat not only to its accuracy but also its integrity. As a result many clients are left in a difficult position in terms of deciding which set of the conflicting records should be used to run compliance calculations or against which data CMDB CIs should be validated.
ITAMS’ best practice recommendation is for clients to consolidate and normalise the disparate asset data sets into a “golden source” and to use only this common record across the organisation and on which to base licence and configuration decisions.
Hardware data reconciliation supporting licence, configuration and outsourcer management
With help from ITAMS, a recent client in the finance sector successfully consolidated, compared, normalised, visualised and reported against 15 hardware data sources. The results were spectacular. They assumed the worst case for calculating hardware maintenance contract by including all identified machines from a number of data sources as input to their assumed estate.
In fact, less than 70% of these machines were real and still present. Analysis showed that the largest contributor was that discovery tools continued to routinely report machines they had last scanned years ago as active. As many of these tools were outsourcer managed with neither a mandatory nor a ‘3 month aged device’ policy applied, the reported data was evidently inaccurate and accounted for unnecessary overpayments in various categories (hardware and software related) to the tune of £10M’s.
The value from the project goes beyond cost avoidance and supports many areas of operational and cost management. It provides a full audit trail of how the “golden record” is derived against which reports on complex data sets can run.