License Audit and compliance
License Basic
Kai Meland, Contract Manager
Kari M. Knutsen, License Compliance Manager
SBN 2015
Agenda
Ÿ  Software Compliance
Ÿ  License audit
Ÿ  Basics – SAP Licensing
Ÿ  Basics – SAP Named User
Ÿ  Basics - Package Licenses
Ÿ  Best Practice
©  SAP AG 2009. All rights reserved. / Page 2
Customer situation
©  SAP AG 2009. All rights reserved. / Page 3
Software Compliance
Software compliance is being able to demonstrate that you have the correct number
of licenses paid for and accounted for on your systems compared and matched to
what you have installed.
©  SAP AG 2009. All rights reserved. / Page 4
Intellectual property rights
To protect the intellectual property rights that is the basis for our company.
©  SAP AG 2009. All rights reserved. / Page 5
Software Compliance – Why and How?
n
By minimising the improper use of SAP’s software, the compliance team
within SAP protect SAP’s Intellectual Property rights
n
SAP expects to be compensated for the products that customers use
n
We do this by performing periodic measurements of usage at our customer
base
n
We perform on-site audits
n
We go through the contracts with partners and end customers
n
We believe our customers do not want to be out of compliance
n
Our goal is to manage compliance risk
n
Fairness, trust and partnership approach are core principles
©  SAP AG 2009. All rights reserved. / Page 6
License Audit Process
Steps overview & key
elements
©  SAP AG 2009. All rights reserved. / Page 7
License Audit Process Steps
Overall
Preparation
n
Measurement
preparation
n
(in each system)
Generate
measurement
results by system
Combine results
of all systems
Finalize the
measurement
n
n
n
n
n
n
n
n
n
Follow-up
n
Responsible persons for measurement identified
System measurement plan is correct (systems relevant for the audit)
Measurement parameters verified in each system (system status, relevant clients, …)
Obsolete users excluded & user classification correct
Measurement results available
Alerts from plausibility checks resolved or explained
Users are grouped (identical users identified across different systems)
Users are consolidated (final user classification if one user has different user types)
Consolidated measurement results verified and transferred online to SAP
Additional information on non-system based metrics provided
Verify specific topics (i.e. via a remote connection, run special reports, …) if applicable
Discuss license audit results
We have well-defined processes and approaches that we follow. We strive for consistency and
we take customers through the processes and explain why we do what we do
©  SAP AG 2009. All rights reserved. / Page 8
Verification of specific topics
Some typical topics that might require a follow-up analysis
n  Verification
–
of unlicensed indirect system access
E.g. indirect access of SAP application data from end-customer in the Utilities industry
n  High
numbers of multiple log-ons
n  High number of Test-Users in productive systems
n  High numbers of deleted users
n  Spot checks on user classifications
n  …
©  SAP AG 2009. All rights reserved. / Page 9
Challanges for customers;
Customers do often not know:
•
What software asset they have
•
Where they are located
•
How they are configured
•
How SW is used
•
Who SW are used by
New innovations (virtualization, open source, multicore, SaaS, Cloud computing)
Several vendores, several contracts, use of none standard agreements
Lack of understanding of license entitlements
Lack of standards, software sold under many models (many metrics)
©  SAP AG 2009. All rights reserved. / Page 10
SAP Licensing
Perpetual Licensing
©  SAP AG 2009. All rights reserved. / Page 11
SAP Licensing
SAP Dual Licensing Modell
SAP Software
©  SAP AG 2009. All rights reserved. / Page 12
SAP Named User
Basics – SAP Named User
SAP Golden Rule
Any individuals that Use* the Software, including employees or agents of
Subsidiaries or Business Partners, must be licensed as SAP Named Users.
*Use is defined in the customer’s End User License Agreement (EULA / GTC):
"Use" means to activate the processing capabilities of the Software, load, execute,
access, employ the Software, or display information resulting from such capabilities.
Licensee must hold the required SAP Named User for any individuals that Use the
Software, including employees or agents of Affiliates and Business Partners. Use
may occur by way of an interface delivered with or as a part of the Software, a
Licensee or third-party interface, or another intermediary system
©  SAP AG 2009. All rights reserved. / Page 13
Basics – SAP Named User Hierarchy
SAP Professional User: *Includes the Rights of Special Users &
Employee User
SAP Project User, SAP Logistic User, SAP Ind.Port. User,
SAP Retail User, SAP Worker User, SAP Healthcare User:
*Includes the Rights of an SAP Employee User
SAP Manager Self Service User: *Includes the Rights
of an SAP Employee User
SAP Employee User: *Includes the Rights of the ESS,
Learning, & Recruiting Users
SAP Employee Self Service User:
Note: SAP Limited Professional is no longer available. This can only be licensed to existing customers as “more of the same”.
©  SAP AG 2009. All rights reserved. / Page 14
Basics – SAP Named User
SAP Developer Named User
•
SAP Application Developer User is a Named User authorized to access the development
tools provided with the licensed Software for the purpose of making Modifications and/or
Add-ons to the licensed Software and also includes the rights granted under the SAP
NetWeaver Developer User and SAP Application Employee User.
•
What are the rights of a Developer User?
•
authorized to access the development tools provided with the licensed Software for the purpose of
making Modifications and/or Add-ons to the licensed Software and also includes the rights granted
under the SAP NetWeaver Developer User and SAP Application Employee User.
©  SAP AG 2009. All rights reserved. / Page 15
Basic - Package Licenses
©  SAP AG 2009. All rights reserved. / Page 16
Basic - Package Licenses
Metrics
The price of a package license is based on key business metrics that reflect your
use of the licensed software and its required capacity, such as;
•
Numbers of orders processed
•
Employees
•
Cores
•
Revenue
©  SAP AG 2009. All rights reserved. / Page 17
SAP Cloud
(on-premise)
Private Cloud
Customer Systems
(managed)
Public Cloud
Managed-Cloud-as-a-Service
Platform-as-a-Service
SAP HANA Enterprise Cloud
SAP HANA Cloud Platform
Build
Custom infrastructure and
maintenance
Any
DB
Extend
applications
Software-as-a-Service
Run
SAP Business Suite
SAP Business Warehouse
SAP HANA
SAP Cloud Strategy Video
©  SAP AG 2009. All rights reserved. / Page 18
Extension Policy
•
On Premise Extension
•
Cloud Extension
©  SAP AG 2009. All rights reserved. / Page 19
Best Practice
Understand your contracts
•
•
•
Quantities, Metrics, User Rights, Terms and Conditions (standard and non standard)
When entering a new contract – make sure the contract is aligned to what you
already have.
Ask SAP or your partner for license guidance!
©  SAP AG 2009. All rights reserved. / Page 20
Thank You!