Is it good to combine multiple Application Services for different environment into one.

[Rahul Mishra1]

I am considering reducing the number of Application Services by combining multiple environments into a single Application Service. For example, merging App1 Prod, App1 Test, and App1 Dev into a single Application Service (App1) in ServiceNow.

I thought of creating Dyanmic CI group and include App 1 Prod/Test/Dev into it but that doesn't seem to be a good use case as Dynamic CI group is more effective at Service Offering level. ( Please let me know if this can be considered and what will be impact)

Or

Kindly suggest, what are the best practices for merging application services? 

#CMDB #CSDM #ITOM #SM

[Daniel Borkowi1]

Hi @AndersBGS, I guess they have too much Application Services which are hard to manage, as he responded already in the thread. This is a serious requirement and CSDM can't give recommendation here, as it's "only" a best practice how to model CMDB data and not a best practice about how to handle tons of data. So your answer will not help Rahul.

@Rahul Mishra1 

My recommendation is for sure keep the CSDM and therefore keep the Application Service for each technical Stack separated. To fulfill the requirement I would utilize the Environment field to populate Prod, Test and Dev or other stages. Focus your reporting, health metrics, Service Mapping and Reference qualifiers on the Environments which really matters. Start with Production and include maybe Validation Environments, ignore environments which are not relevant in ITSM, maybe you don't open a Incident for a development environment - so why should you have your whole dev stack in the CMDB - at least at the beginning - you can expand later when you have perfected the important areas. If it's still too much to start - start with the most business critical Application Services.

Greets
Daniel

Please mark reply as Helpful/Correct, if applicable. Thanks!