license usage auditingcommunity.plm.automation.siemens.com/siemensplm...spreadsheet magic for...

Rob Reich Teamcenter Business Development

Strategy, Innovation, and Research

1 http://plmworld.org/ © Siemens AG 2012. All Rights Reserved.

Siemens PLM Software

License Usage Auditing

http://plmworld.org/

© Siemens AG 2012. All Rights Reserved.



Agenda

Why do I care about monitoring

licensing usage?

Philosophy of Teamcenter

licensing

Tools for auditing license usage

Teamcenter 8.3 using FlexNet

Teamcenter 9 built in auditing

Teamcenter Occasional Author

Spreadsheet Magic

For FlexNet logs and Teamcenter

usage reports

HD User Experience

Intelligently Integrated

Information

Future-proof Architecture




Why do I Care?


licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Reasons for Monitoring License Usage

Why do I Care About Monitoring Licensing Usage?

Interdepartmental charges

Typical scenario is that a central IT organization supports multiple user

communities / departments that use the Teamcenter tool set

The central IT needs to fairly charge for the those group’s usage

Budgeting

Monitor trends of usage to determine when additional license

purchases must be budgeted

Interdepartmental budgeting as with above

Compliance

Teamcenter licensing allows for auditing license usage to enable a

company to monitor their compliance with their license agreement

For public US companies, Sarbanes-Oxley Act of 2002 has financial

reporting implications that requires compliance with software licensing



Compliance

Teamcenter licensing philosophy is not to force companies to

assign named users to every module license, but to rather allow for

auditing the usage to monitor compliance

“Enable honest companies to stay honest”




Philosophy of Teamcenter Licensing


licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Licensing Enforcement Philosophy

Focus on monitoring license usage as the first priority and

enforcement of licensing as a second priority

Have enough enforcement to help customers stay honest

End user licensing enforcement should not become a major source of

PRs due to over enforcement

The last thing we want is to block production usage while you’re

waiting for a new license file

Reduce the burden of managing named users



Named User Licensing

Most of Teamcenter is licensed via Named User Licensing

Exceptions exist for server or system wide products and for

integrations that are licensed per the product to which they integrate

Each named user of Teamcenter or one of its modules requires a

license “assigned” to that user

License monitoring fundamentally counts the number of users using

the licenses in a period of time

Counting the number of users of Teamcenter or one of its modules

is easier to calculate / forecast than concurrency ratios



Teamcenter Fundamental Packaging

Module licenses

Requirements Management

Program Execution Management

Product Configuration, etc.

Integrations

NX Embedded Client

Integration for CATIA, etc.

Visualization Service Levels

Base (included in a seat)

Standard, Professional, and

Mockup plus options

Foundation “Seat” licenses

Teamcenter Author

Teamcenter Consumer




Tools for Auditing License Usage


licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Before Teamcenter 8.3

Licensing Monitoring

Enforce named user totals at base author / consumer level

Log usage for Teamcenter “seat” feature keys

teamcenter_author

teamcenter_consumer

Leverage the Siemens PL license server (ugslmd) and single license file beginning with the following releases:

NX5

Teamcenter 2007.1 MP3’s unified architecture

Teamcenter Visualization 2007

I-deas NX5

Product Feature

Teamcenter Author teamcenter_author

visview_base

Teamcenter Consumer teamcenter_consumer

visview_base



Named User Licensing Based on User Definition

Named user licensing

counts “active” users

Author / Consumer

designates license level

Refer to your MLA for

guidelines for

reassigning named

users



Configure License Warning Level

Configurable warning message to tell administrators that their

license usage is approaching their available licenses

Preference name is "license_warning_level"

Warns administrator

when 5 or fewer licenses

remain for assignment



CAD Integration Licensing

CAD integration licensing is consistent with the CAD tool’s scheme

Most CAD integrations are sold as concurrent use licenses

Customers should match the number of Teamcenter CAD Integration

licenses with the number of CAD licenses

Teamcenter will checkout the appropriate feature key associated

with the given CAD integration when it is in use: e.g. nx_integration,

catia_integration, etc.

These licenses are not freed up until the Teamcenter session is ended

Each user leveraging a CAD integration must also have a

Teamcenter Author seat license (named user)

The only exception is for the NX Mach products where a limited,

concurrent use license to Teamcenter is included called

teamcenter_designer



Teamcenter 8.3

Licensing Monitoring

Add server side logging for Teamcenter modules

Updates to FlexLM logging to support named user logging

Tools to help analyze usage

BusinessObject

POM_Object

StoredOptionValue PSOption VariantExpressionBlock

Product Configuration licensing logged

on methods on these classes, e.g.

create and modify



Teamcenter 8.3

License Features Being Logged

Added logging usage of modules

in addition to logging “seat” usage

Usage recorded for all interfaces,

e.g. rich client, thin client,

Integrations, SOA’s, iPad, ITK’s,

etc.

Independent of the release of

Teamcenter 8.3, there will be

announced new application user

licensing

Where you see application_access

or application_author, these will be

replaced by application_user

Product Feature

CAD Integration – CATIA catia_integration

CAD Integration – NX nx_integration

CAD Integration – Pro/E proe_integration

Change Management change_access

change_author

Classification classification_access

classification_author

Context Management context_mgt_access

context_mgt_author

Product Configuration

platform_des_access

platform_des_author

prod_des_access

prod_des_author

Program Execution

Management

prog_exec_access

prog_exec_author

Requirements Management requirements_access

requirements_author

Visualization visview_mockup

visview_pro

visview_std



License Monitoring Tools

Three techniques for license usage monitoring

Teamcenter FlexNet log

Periodically run the lmstat utility

3rd party tool such as FlexNet Manager for

Engineering Applications management and

logging application from Flexera,

http://www.flexerasoftware.com/products/flexnet-manager.htm

Best choice depends on customer need






License Monitoring Tools

Technique Pro Con

FlexNet license log Free

Provided tool for

analyzing logs based on

licensing rules

Log intended for

debugging

Some impact on

performance

lmstat utility Managed impact on

performance

Used by a few large

customers today

Can miss some usage

Not tailored for

Teamcenter licensing

rules

FlexNet Manager Commercial tool, e.g.

has support

Commercial tool, e.g.

has a licensing cost

Not tailored for

Teamcenter licensing

rules



Feature key usage is tracked in the Teamcenter license log

The file is called ugslicensing.log

Feature Key Usage Tracking

Timestamp for

start of a day

Timestamp for

an event

Daemon

name Event type – checking OUT

or IN a license

Module’s feature

key name

Teamcenter user

accessing the feature

Host name



Teamcenter 8.3

Updates to FlexLM Logging for Named Users

Teamcenter user id logged versus OS user name

Correctly logs Web and four tier usage

Correctly logs multiple users on a shared two-tier client machine

15:15:02 (ugslmd) OUT: "teamcenter_author" user9@TcServer

Allow a single named user to login multiple times without consuming

multiple license feature keys

Support multiple logins from the same or different displays

Support logins from simultaneous 2 tier and 4 tier connections

The host name is logged as a constant, “TcServer”

Each login will be recorded in the log file, but each will only count as one

license usage by the license server

Caveat – HP-UX PA-RISC hardware running TcServer cannot take

advantage of the new common licensing toolkit

Refer to the release notes for more detail

Teamcenter user name Constant



Two Utilities Provided

There are two utilities to help analyze FlexNet log files

convert_license_log

License Usage Audit Tool



Convert License Log

The Convert License Log Tool converts a raw license log file into a

delimited text file

The file can be read in a text reader or Microsoft Excel

Simple conversion to provide raw feature key usage

Syntax:

convert_license_log -input=log-file -output=file-

name -delimiter=character [-h]



Example Convert License Log Output



License Usage Audit Tool

Analyzes the raw log file and outputs a file including the following

information for the period covered by log file:

Listing of users, seat and feature usage per month

Hours of usage per month

Logs a minimum of one hour per login

Logs a maximum of 7.5 hours per day

Days of usage per month

Number of logins per month

Usage violations and more…

Syntax:

LicenseUsageAuditTool.bat -pseudouser

-i D:\logs\ugslicensing.log -o D:\logs\output.csv

Full path to input

FlexNet log file

Full path to the

output file

Optional: -pseudouser output users only

as pseudo user names to avoid

attributing usage to actual users



Example License Usage Audit Tool Output



License Usage Audit Tool Continued

Location on Teamcenter 8.3 media:

additional_applications\LicenseUsageAuditTool\LicenseUsageAuditTool.zip

Tool can be run independent of Teamcenter install

This tool requires the JAVA_HOME variable to be set to java home directory

Example JAVA_HOME = D:\apps\java\jre6

Content

bin\LicenseUsageAuditTool.bat/sh – Script to execute the tool

conf\AuditUsage.xml – Input xml configuration file

lib\LicenseUsageAuditTool.jar – Jar with compiled java classes for this tool

For Usage type

LicenseUsageAuditTool.bat -?




Tools for Auditing License Usage


licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Teamcenter 9

Logging and Reporting License Usage

Teamcenter 9 introduces additional license usage logging

Usage stored in Teamcenter’s database

Logs usage by named user per month similar to the analysis results

of the FlexNet log file

Previously Teamcenter logged only the last login

The reason for adding this logging is…

Removes administrative burden

to monitor the FlexNet log and

to run the analysis tool to convert

log into a useful output

to use “lmstat” and custom reporting

More securely enables hiding of user

identity



Teamcenter 9

Reporting Usage

Admin - License Usage

Report Builder Report available for reporting

license usage per user per month



Teamcenter 9

Reporting Usage

Must select appropriate

stylesheet for export into a

CSV formatted file that can

be opened in Excel for

further evaluation and

reporting

Example raw

output



Teamcenter 9

Reporting Output Opened in Excel

Pseudo ID’s are

encrypted

Features are grouped to minimize

database table space and because

with named user licensing any

feature used is allotted for the

month

Remaining fields match

log analysis results



Teamcenter 9

Usage Reporting Preferences – User Id

Specifies to output the actual user id’s in the usage report

Activates output of the actual user id in

a usage report in addition to the pseudo

user identifier

LicenseUsage_show_userId_in_report

Default is

true






licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Teamcenter 9

Occasional Author Enforcement

Occasional Authors is a full functional seat license for Teamcenter

that is restricted for use to a limited time per month

5 unique calendar days AND

20 hours

The Occasional Author is not permitted to use Teamcenter for more

than 5 unique calendar days and more than 20 hours

Occasional Author licensing time limits require enforcement

Teamcenter 9 not only added logging usage to avoid the reliance on

FlexNet logs and other tools, but also to enforce Occasional Author

licensing terms



Teamcenter 9

Occasional Author Licensing Enforcement Flow

User

attempts

to login

Usage

condition?

Under

usage limit

Warn User

Deny login

License

Checkout?

Login

Yes

license

unavailable or

any other

denial reason

Past grace

period

Nearing

usage

limit?

No

Email the

Admin

Email the

Admin

Start

In

grace

period

Yes

No



Teamcenter 9

Licensing Enforcement Flow – Happy Path

User

attempts

to login

Usage

condition?

Under

usage limit

Warn User

Deny login

License

Checkout?

Login

Yes

license

unavailable or

any other

denial reason

Past grace

period

Nearing

usage

limit?

No

Email the

Admin

Email the

Admin

Start

In

grace

period

Yes

No



Teamcenter 9

Licensing Enforcement Flow – Nearing Usage Limit

User

attempts

to login

Usage

condition?

Under

usage limit

Warn User

Deny login

License

Checkout?

Login

Yes

license

unavailable or

any other

denial reason

Past grace

period

Nearing

usage

limit?

No

Email the

Admin

Email the

Admin

Start

In

grace

period

Yes

No



Teamcenter 9

Occasional Author Warnings – Nearing Usage Limit

Example email sent to an administrator regarding an occasional

author nearing their allotted usage

Message from the

occasional author

to the administrator

specified in the

preferences Message details remaining unique calendar

days and hours of usage before reaching the

limit of usage for an occasional author



Teamcenter 9

Occasional Author Warnings – Nearing Usage Limit

Warning message to the user that they

are approaching their permitted usage

for the month



Teamcenter 9

Licensing Enforcement Flow – In Grace Period

User

attempts

to login

Usage

condition?

Under

usage limit

Warn User

Deny login

License

Checkout?

Login

Yes

license

unavailable or

any other

denial reason

Past grace

period

Nearing

usage

limit?

No

Email the

Admin

Email the

Admin

Start

In

grace

period

Yes

No



Teamcenter 9

Occasional Author Warnings – In Grace Period

Example email sent to an administrator regarding an Occasional

Author usage beyond their allotted usage and within the grace

period

Message from the

Occasional Author


specified in the

preferences Message details remaining grace period

allowed for the Occasional Author… the

admin may need to take action to make

the user an Author



Teamcenter 9

Occasional Author Warnings – In Grace Period

Warning message to the user that they have exceeded

their permitted usage and have entered a grace period

after which they will not be able to login



Teamcenter 9

Occasional Author Licensing Enforcement Flow

User

attempts

to login

Usage

condition?

Under

usage limit

Warn User

Deny login

License

Checkout?

Login

Yes

license

unavailable or

any other

denial reason

Past grace

period

Nearing

usage

limit?

No

Email the

Admin

Email the

Admin

Start

In

grace

period

Yes

No



Teamcenter 9

Occasional Author Warnings – Login Denied

Example email to administrator regarding an Occasional Author

usage exceeding their allotted usage and the grace period

Message from the

Occasional Author


specified in the

preferences Message notifies the administrator of the usage

denial for exceeding that allotted usage… the

admin should take action



Teamcenter 9

Occasional Author Warnings – Login Denied

Login denial message to the user that they have

exceeded their permitted usage and will not be able to

login again until the start of the next month



Teamcenter 9

Occasional Author Preferences – Admin Notifier List

List of administrators to notify on over usage of Occasional Author

licenses

Specifies the list of administrative users

that would get the notifications from the

Teamcenter system when Occasional

Authors approach or exceed the allotted

limit of the “Occasional Author License“

usage and/or the users are in the grace

period of the license usage

LicenseUsage_admin_notifier_list



Teamcenter 9

Occasional Author Preferences – Warning Days

Specifies in days when Occasional Authors would be warned

Specifies the remaining duration in

days after which an Occasional Author

will get warning messages

LicenseUsage_days_warning_level

Default is

2 days



Teamcenter 9

Occasional Author Preferences – Warning Hours

Specifies in hours when Occasional Authors would be warned

Specifies the remaining duration in

hours after which an Occasional

Author will get warning messages

LicenseUsage_hours_warning_level

Default is

5 hours




Spreadsheet Magic


licensing usage?


licensing





Spreadsheet Magic


usage reports

HD User Experience


Information




Types of Output from the Evaluated Log

Monthly Seat Usage

Teamcenter

Authors

Teamcenter

Consumers




What Happens if I Exit Without Logging Out?

Max values

indicates that

the maximum

values were

used at least

once for that

user this month

Reason for

using the max

values is an

license not

released

Count of

times the

max value

was used

Log a full day of

usage which is

7.5 hours




What Happens if I Switch Licenses During the Month?

Note that if the user was a teamcenter_author for part of the month and

a teamcenter_consumer for the rest of the month, the user will be still

logged as the higher seat for the month…

User Pseudo User Seat Feature

user20 User0000020 teamcenter_author teamcenter_consumer

Indicates the Seat

for the Month of

usage

Indicates the specific

feature used for the

entry




Feature Usage Summary

Feature

quantity from

license file

Peak usage

over a year Product No. and

name from

license file

Pivot table on usage

of each feature per

month

Conditional formatting

of overages and

unlicensed usage




License File Lookup

Grabs feature

count from Pivot




Feature Usage Violations

Identifies violations of usage

rules, e.g. in this case use of

authoring capabilities by a

Consumer

Shows number of occurrences and

which month to determine if usage

was a one-time mistake or a

frequent need

Filtered to show license

filter feature violations




Raw Data for Tracking Unlicensed Features

Max values indicates that since the

user did not have a license, we will log

a full day of usage which is 7.5 hours

Reason for using the max

values is an unsupported

feature, i.e. unlicensed

Count of

times

used




Raw Data for Tracking Over Usage of Features

Max values indicates that since the

user did not have a license, we will log

a full day of usage which is 7.5 hours

Reason for using the max

values is a denied feature,

i.e. exceeded available

Count of

times over

used




Summary


licensing usage? Honest customers need a way to show

compliance


licensing Some enforcement with tools to

monitor usage / compliance

Tools for auditing license usage FlexNet approach for all releases and

built in auditing in Teamcenter 9

Teamcenter Occasional Author Introduced in Teamcenter 9.1

Spreadsheet Magic Basic filtering and pivot tables / charts

can quickly provide analysis of license

usage

HD User Experience


Information


license usage auditingcommunity.plm.automation.siemens.com/siemensplm...spreadsheet magic for...

Documents