Browse Prior Art Database

A method to rate and exchange software signatures Disclosure Number: IPCOM000241678D
Publication Date: 2015-May-21
Document File: 5 page(s) / 72K

Publishing Venue

The Prior Art Database


Flee market for signatures managed by an entity with own currency, rating and rules. In general everyone may contribute to the market with either producing, selling or buying the signatures. The cost of obtaining a particular signature will go down. On the other hand there will be a correlation between price and quality of offered products. More valued (with higher rating) producer of signatures, the higher quality of signatures might be expected from them.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 36% of the total text.

Page 01 of 5

A method to rate and exchange software signatures

Nowadays software asset management area grow very fast. More and more companies realize

that vast IT infrastructure is a real subject of saving money, especially where many different software is installed. Different business units within one company purchase software licenses and because of huge dynamicity in this area (including manpower) many of such licenses are wasted

just because either asset managers do not know what is actually installed. The software for optimization of the licenses e.g. Software Use for Analysis, FlexNet Manager Suite, Aspera modules etc. are very helpful here, but they cannot solve one particular problem. They do not know what is installed on our infrastructure. It's like this because it is hard to get such information from the operating systems. And the difficulty is not with lack of the tools, but with low definitions of how to realize that particular piece of software is really installed. Such definitions we call signatures. Even though the leading IT companies already figured out opportunity in this area there is still a big gap here.

There are solutions for such situations, however all of them are focused on manner to provide/create/test such signatures.

1. A specialized company may provide ready-to-use catalog with signatures.

2. Specialized company/product team (IBM services, HP services, etc.) may be hired to do this


3. Local IT team may create signatures.

All of the solutions though, have limitation. They have pros and cons.

Ad. 1. Experienced software catalog members say that creation of one single signature takes around one day for subject matter experts. In difficult cases, it may take a week or more. Now try to multiple it by different versions, releases, editions of the same product. Then by the number of families of products... Then by the number of vendors… The cost becomes high.

Ad. 2. Specialized company/product team (IBM services, HP services, etc.) may be hired to do this job of course, however their time is really costly and not many companies can afford it. Moreover the cases that need interaction with different teams across different sites take time, therefore usually they do not fit into engagement period and are not finalized.

Ad. 3. The best situation is with local teams who have products locally installed. Such teams do not have time constrains. The challenge here is lack of experience, especially in early phases, so the quality of such created signatures is mostly quite poor. And created signatures which do not recognize all the software or recognize too much of them are a real reason of losing the money.

One of the solution to just stated problem was proposed to by IBM very recently. It is a signature community:

The main idea that stays behind it is to exchange signatures between users. It is very good start point however within the naked form it is at the moment it is not very attractive to...