CR4® - The Engineer's Place for News and Discussion®

Solutions for Industrial Computing Blog

Solutions for Industrial Computing

The Solutions for Industrial Computing Blog is the place for conversation and discussion about industrial computers, systems and controllers; communications and connectivity; software and control; and power strategies. Here, you'll find everything from application ideas, to news and industry trends, to hot topics and cutting edge innovations.

Previous in Blog: The Software Audit Balancing Act   Next in Blog: Software Licensing for the Virtual Appliance

Centralizing Software Usage and Software License Management

Posted April 22, 2010 9:00 AM by FlexeraSoftware

Over the past few months, I've had many professionals in the supply chain and procurement space say they would be interested in finding a process that provides a way to depict their Oracle database deployments in a manner they can easily understand and then use to communicate and negotiate their software license agreement with Oracle. They've explained that they're frequently given information about their IT Departments' use of Oracle that is not easily translated into Oracle licensing metrics.

Raw Data or Wrong Data?

These professionals also complained that they frequently get this information in a variety of different formats from different divisions or groups within their own company, and some of the IT personnel put their own interpretation on what should be licensed, or how it should be licensed, before delivering the raw data to them. (And after talking a little more, almost all individuals expressed a general uneasiness about the accuracy of the information they were getting - from CPU counts to database option usage).

Competing Counts

In a recent example, a procurement officer told me that he had two different divisions of his company delivering named user count minimums using a different interpretation of the Oracle licensing rules: one enforcing named user minimums at the server level, the other providing a summarized count of named user minimums. This results in inconsistent data and the inability of having a true understanding of what is actually being used, by whom, and how often.

Read the Whole Article


Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.

Previous in Blog: The Software Audit Balancing Act   Next in Blog: Software Licensing for the Virtual Appliance