Application Service (cmdb_ci_service_auto) already includes extended classes for different use cases. And ServiceNow has provided some guidance on using each of them.

• Here is one great article on ServiceNow Community on how to use them: LINK
• And another one: LINK 
• And finally the ServiceNow Product Documentation page about Application Services that describes, for example, the different types of application services.
• In case you are creating app services manually, here are some instructions related to that.

A Blueprint is a visual representation of a data model. It includes tables, their relationships, and filters and conditions that define what kind of data we should use.

The Content Planner is a data management tool within DCM to maintain data on top of a Blueprint. In the Content Planner, you work with the data, while a Blueprint defines the data model that you are supposed to use. The Content Planner overlays real data on top of the Blueprint so that data can be updated with a visual tool, minimizing the possibility for errors.

Please view a short introduction video on our product page that explains all DCM modules briefly.

Licensing is based on the number of active blueprints. There are no limits on users, tasks, or data being audited or maintained with DCM. Get in touch with us to discuss what it would cost you.

Yes. By default, all ServiceNow store apps can be installed into on-premise instances.  (More info about this here)

Yes, “Service Offering Subscribers” has been defined as part of Extended CSDM in the CSDM Process Guide.

For more info: Search for “CSDM Process Guide” after following this link.

This is a very typical scenario. Depending on the exact situation (including organizational structures, data volumes, available resources etc.), there are also several ways to address this.

With DCM, you can define simple models for each of the required classes and start auditing and guiding users on populating the missing records. By categorizing or grouping the existing Services, you can manage the transition and identify if a record is still to be processed or already a real Service,  as defined by CSDM.

Tags or taxonomy nodes can be used over the transition without creating extra attributes.

This approach aims to ensure that all new records created into Business App, App Service, and Offering tables are aligned with CSDM from the beginning. The original “Service records” act as a to-do list.

Auditing all of these models continuously will give you proper metrics to follow up on the progress and identify deviations against the plans.

Yes, you can install DCM (and any other store app) into a PDI, but we need to set up entitlements related to your PDI. Get in touch with us, and we will set this up with you.