what are the correct intended usages for the different product model types?

[dick1]

In CSDM there are different types of product models defined. For some I know the intended usage.

like hardware model defines the models used for your hardware asset registrations.
Contract models are logically used in your contract registrations. 

But as I'm now trying to populate our legacy data regarding software its getting confusing.

e.g. when to use a software model and when to use an application model. 

is there a good description on where the different model types are used for (so not only for hardware/software/application but also when it's better to choose a service model or a consumable). 

[Stefan K_]

Application service: ServiceNow PROD 
- Version attribute: San Diego

Business application: ServiceNow
- Relationship "Consumes" to the Application Service "ServiceNow PROD"

So what is the use of Application model in this picture?

[Stig Brandt]

Hi, 

This is where the implementation lack's imo, as 

- Application Model is not present on Business Application (Version Agnostic) and as Application Service is Version specific -> we need  "Software Model" - to illustrate the specific Version, it should be possible to link that to Application Service, not on an attribute on Application Service - but on Software model is model categories read - only for License and software.

[Stefan K_]

Right thanks, so indeed I was also thinking after posting above that an attribute is not enough for the version on application service as you want to track several attributes about the version (end of life etc...). 

[s4scott]

Application services and the sub-classes under application, i.e. the myriad application and application server classes like Web Server, Database instance, etc, should all use the software product model. The software product model allows for the aggregation of models into suites and the other structures needed for software asset management. 

Business applications use the application product model, as they represent the product from a portfolio planning perspective, or the high level overview of all of the internal or third party products in use. 

What I have not found yet, is an easy way to link the list of software models to the application model they should be aligned to. Particularly when versions of a certain title may have been bought or re-branded, it is helpful to be able to see where there are lifecycle issues to address.

I also see challenges with the model category structure in the product catalog. It is very helpful on the asset side to ensure that the CI is created in the correct class, but maintenance of assigned model categories can be challenging to insure that all of the desired products display in the model ID field of the classes they should.

[EricDohr]

We first need to discuss Product Model Categories.  Out of the box, you may be missing categories for correlating CI Classes seen below and you will want to create these items

• Business Service [cmdb_ci_service_business]
• Service Offering [service_offering]
• Technical Service [cmdb_ci_service_technical]
• Business Application [cmdb_ci_business_app]

Once a Product Model Category is established, a Product Model can be associated to one or many categories.  

Product Models can be associated with one or many Configuration Items via a reference field called Model ID.  Out of the box, there is logic to only show Product Models that have alignment to the Model Category which is tied to the CI Class in question

Application Models

• Application Models are version agnostic
• Software models can reference an Application Model
• Application Models can be utilized during the SCRUM process 
• An example of this would be ServiceNow Platform
• You can establish lifecycle dates for an Application Model
• While you can list the Business Application - Application Model via Model ID, there is also a field for Software Model (reference field) if interested 
• In Agile Development, you can correlate either an Epic or a Story to an Application Model

Software Models

• Software models can reference an Application Model
• Software models can relate to Application Services via a related list Application Service Software Models [sn_apm_tpm_service_software_model].  This table is important when it comes to APM so you can visualize your Technology Portfolio Management 
• Software models depict specific versions
• An example of a Software Model would be ServiceNow Rome, ServiceNow San Diego, etc. (there is GA, End of Support, etc.)  You still have ServiceNow Platform (Business Application), but you need to plan for projects and efforts to make sure you continue support.
• Software models have Internal and Published dates
• Software Models are also critical for ITAM - SAM
• In Agile Development, you can correlate either an Epic or a Story to a Software Model

Service Model

• Currently, the primary use of a Service Model is within CSM where you associate it to an Offering
• I have found that out of the box (I do not have CSM), there is a dictionary override where Service Models can only be used on the Application Service CI

Consumable

• Consumable would be used any time you have an entry on the Consumable [alm_consumable] table