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 @Rahul Mishra1 , in my opinion it's not a good idea. As each environment has a separate infrastructure stack and the Application Services are the entry point of this stack, I recommend to keep them divided.  Also as they are used in the ITSM processes and you may have different Offerings with different Commitments (e.g. Availability requirement), different responsibilities like Support Groups, it's better to split them.Greets
Daniel

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

[Rahul Mishra1]

Cool, then is there any way I can reduce the number of application services? That is  the requirement ..

[Daniel Borkowi1]

@Rahul Mishra1  Maybe you focus on the real important one, which are the production environments and maybe validation ones. But instead of summarizing them, may work with filtering like the environment field.

[AndersBGS]

Hi @Rahul Mishra1 

why would you do that? it’s not according to CSDM or ServiceNow best practice