How to represent "Product" in CMDB? The closest is Application Service in my opinion.

[Peter Kindbom]

Any other suggestions or experience? Any good guess on news in Utha and Vancouver concerning Product Mangement? I have got some hint saying that Product Owner will replece Service Owner as the "central role" in CSDM. Feedback on this is apreciated.

Keep up the good work 🙂

[Paul Kilkelly]

Hi Mary.  I struggle with this example.  Maybe I have this wrong but my understanding of CSDM is the 'business application' is a 'solution design' to a 'business capability'. This solution design may, or may not, be constructed around a core commercial product (like ServiceNow), but it is not the commercial product.  It is more likely to be a construct of a number of products.  I think it is misleading to reference the software model from the Business App as you propose.  APM's approach to model mapping recognises that a business application.  Thoughts?  

[Christian Prob2]

@Peter Kindbom you may want to specify/clarify what you consider a "product".  "Product" and "Service" are in some organizations synonyms, in others they describe very different concepts...

[Jim Zeigler1]

I hope this helps explain what Application Services are and how they are used in ServiceNow:

• Application Services
• Application Services represent a set of running applications and infrastructure that provide Business Capabilities.
• Application Services can be decomposed into smaller pieces of functionality that are assigned to development teams.
• These pieces(called Business Applications) provide business capabilities that may be "used by" a single Application Service or shared by multiple Application services.
• Business Applications may be developed in-house or purchased from a 3rd party vendor. For example, most companies purchase a 3rd party Business Applications to provide authentication services for single sign on(SSO). The Single sign-on Business Application may be deployed to all their Applications Services.
• Business Applications might be assigned an Application ID that uniquely identifies them in source code control libraries and directories where the application code and content is deployed. 
• As changes are made, new versions of each Business Application are created.
• To test the functionality or performance of an Application Service, the implementations for all its Business Applications are packaged together into executables with content that are deployed together to a target platform ("application stack").
• The target platform may be provided using on-premise infrastructure or a cloud vendor platform.
• To support concurrent testing of multiple versions of Business Applications, multiple runtime environments (e.g., Sandbox, Dev,QA,Test,Prod) are provided by the infrastructure teams.
• Application Services usually have a callable URL or other interface whose operational state can be monitored. These "Entry Points" are usually implemented as load balancing services for high availability.
• In summary, Applications services consist of Business Applications that are deployed to runtime environments.
• Application services are also used to model the different types of infrastructure Services that make up a runtime environment. These are usually referred to as "Infrastructure Services". Infrastructure Services might contain clusters of Web Servers, Application Servers, DB Servers, Messaging Servers, Authentication Servers, Mail Servers, Active Directory Domain servers, Domain Naming Servers(DNS), Backup Servers, Monitoring Servers,…that are needed to provide the runtime environment.
• Service Maps
• ServiceNow supports the creation of Service Maps for each version of an Application Service. Service maps should contain all the CIs that they depend on:
• Hardware infrastructure CIs (e.g., virtual and physical servers, clusters, network devices, appliances,…)
• Application CIs (running processes)
• Entry Points
• Application Services
• Application Service Groups
• Service Mapping works best when used with Discovered CIs which contain all the details need to build the map.
• Service Maps can be populated using any of the available methods (Manual, Query-Based, tag-based, or Pattern Based "top-down" discovery).
• The Application Service class has subclasses to support each of the population approaches.
• Application Services are members of parent Application Service Groups(which can have their own parent Application Service Group). At the top of the Service hierarchy there are Application Service groups for each supported environment (Dev,QA,Test,Prod). Most customers just create service maps for production.
• Operations and support teams can see the status of any Application Service by looking at the Service Maps which show the severity of monitoring alerts that have been associated with CIs on the service map. 
• Monitoring alerts are propagated upwards through the entire Service hierarchy as soon as they arrive.