Discovery Licensing - Node vs Device vs Server - So what is all the "chatter" about cmdb_ci_hardware etc ?

[keviningleby]

I attended the Discovery course a few weeks ago.

As part of the "extra information" offered - there was this little nugget -

This appears to be quite clear that only physical & virtual Servers require a license.

Yet there is a lot of "chatter" here that refers to Classes derived from [cmdb_ci_hardware] - that are "discovered" (or presumably - simply updated by Discovery) - as being the objects that are licensed.

According to the diagram - that is a bit vague to say the least.

It does not include certain Classes that are not derived from [cmdb_ci_hardware] (some storage objects for example)

Can someone state authoritatively - as of this date - that only physical and virtual Servers require licensing ?

My client has paid for 15,000 licenses - which was calculated to include Server, Network Equipment and EUC devices - Desktop/Laptop etc.

If they use "help the helpdesk" for EUC discovery - as oppose to pointing "Discovery" at these devices - then we (they) could decrease their license count by 5K (EUC) and 7-8K (Network and Storage devices)

That is quite a cost saving

Many thanks

Kevin

[bradley_owen]

This slide is showing that there have been 3 primary models to subscribe to the Discovery application, the current model being the node based mode.   In all cases, all CIs can be discovered.   The terms each customer negotiates could be different - I would recommend talking to the customer's account rep to understand their specific situation.

[keviningleby]

Hi Bradley,

If you will forgive me - that is a bit of a "cop-out" reply.

There has to be a licensing "baseline" model - which ServiceNow must publish.

That might be the starting point for commercial negotiations

However, there has to be that clear baseline to begin with.

This is a highly competitive market-place

To adopt a unique agreement with every customer is not viable.

Best Regards

Kevin

[doug_schulze]

Kevin,

(Not to speak for Bradley who is my source of truth in this area..)

The pricing model has changed and may not be reflective on current existing contracts for different customers.   For those that have been around long enough we have went through many iterations of how discovery is licensed.   From the early days of 'per physical server' to 'every device (IP address) that discovery touched' to the latest for inclusion of service mapping 'server Nodes'.   Some friends may be on a previous model , some may be on a newer model and why he suggest speaking with your account manager on which exact licensing model you might be on because, you are right!   It is a very competitive marketplace and why our Account Management teams work so hard to ensure this amazing discovery product continues to return value for the investment that fits the need...

-Doug

[keviningleby]

Hi Doug,

I really don't see why this is so difficult to answer.

There have been a number of licensing models.

What are they ? and on what technical (i.e. cmdb schema) basis did/do they operate ?

If there are additional factors where ServiceWatch is or will-be deployed (pre-post integration around Geneva release) - what are they ?

Whatever, a customer's current release - the technical baseline was/is the starting point for Commercial negotiations - but that was not the question here.

As a Consultant that visits many different clients - I need to understand all licensing variants (technical view) - so that I can establish their "as is" and then architect towards their "to be" situation. (The commercials come later).

Many thanks

Kevin