How to use Application Product Models?

[Tobias]

Hi, 

The idea is to use Application Product Model table to store list of all applications (version agnostic). Having the specific versions as "children" in Software Product Model table. 

Until now we have used Business Application table for non-desktop-installed applications - as a list of what (Business) Applications we have. Meaning not only Business User facing applications, but also including things like 'Orion', 'MS Intune', 'SAP Solution Manager'.

These non-business-user facing applications would be removed from Business Application table and instead reside in Application Product Model table - the Application Service instances would reference the Software Product Models. 

This would cleanup Business Application table - being true to the definition of Business Application'

Application Product Model table would then comprise of non-business applications (e.g. Orion) as well as "classic" Business Applications (e.g. Salesforce). Thus Saleforce would exist in both tables. 

What are your thoughts on this? How have you approached Application Product Models? 

/Tobias 

[EricDohr · Accepted solution]

I would recommend against this.  

If you adopt APM, you will want Business Application records to be used to rationalize your environment and be able to depict a relationship with one or many Business Capabilities.  There are many assessments in APM that roll up to a Business Application record and not the product model at this time.  

From a user experience, it could be confusing when you go to a Business Application versus a Product Model.  Different fields and usage.

Do not treat IT Business Applications different than Business facing Business Applications in the APM world.  For instance, if you only use ServiceNow for IT, you would still want the following

• Corresponding Business Application(s) such as ServiceNow Platform (Platform Host) and other records that would be Platform Applications (depending on your maturity)
• Application Services for your environments
• Underlying Configuration Items for MID Servers
• Technical Services and Service Offerings that are applicable
• Business Services and Service Offerings that are applicable
• With APM, you would want Software Models connected to the Application Services via a related list for Technology Portfolio Management

You also do not associate one or many Application Services to a Product Model at this time through a CI Relationship, but a Business Application.  

Application Product models have multiple use cases including Agile and is incredibly important as part of a Digital Product. 

As you can see with CSDM 4.0, there is a lot of planning and foundation being set for the concepts of Digital Products.  

[Tobias]

Thank you for detailed answer. 

Could you elaborate on how Application Product Model is mainly for Agile Development use cases?

What bugs me is the limited number of OOTB fields on application product model form - and the fact that (my interpretation) one would reference the specific software model on application CI's rather than the application product model. The application product model acting as a container/parent for software models. 

[EricDohr]

I believe the initial intent was Application Model usage on the Agile, but product model use cases will grow over time.  Especially with the introduction of CSDM 4.0, this is setting a lot of the foundational concepts of Digital Products.  

From my experience, you I have been applying the Application Model to the Business Application Model Category.  I have then created software models that are linked to the Application Model.  

The Business Application record does have Software Model (reference) in addition to the Model ID field (reference).  

Application Model - ServiceNow Platform

Software Models - ServiceNow San Diego, ServiceNow Tokyo, ServiceNow Utah

• Each one has GA, EOS, etc.

Within APM, you can correlate one or many software models to an Application Service via a related list (similar with hardware models) to drive Technology Portfolio Management.  I understand if you are not using APM, this may not be the use case that addresses the requirements.  

[Jim41]

Does this still hold true in 2025?  My APM team is asking for the following:

• Mapping between SAM Pro’s Products, Product Models, software vendor life cycles to Alfabet’s product list, life cycles, etc.
• The ask for SAM Pro team is to provide us with the intake process and the template for creating these software products / models / lifecycles. So that we can provide the normalized list in the expected format/process.
• Our team is currently working on normalizing the product names and we’ll provide you the list.
• NOTE:  I believe most of these are all Business Applications in the Alphabet tool. I hate to make a mess.

[snowdev8]

Ha, I had the exact same question and thats when I checked the year that this was posted. I am curious though