CSDM best practices for raising IPC request for a SaaS application

[Ashwath2]

CSDM recommends that no IPC request should be raised on Application.
But what about a SaaS application for which there is no tangible CI and hence even if we have an Application Service it would not have any CI's tagged. Also, the client for whom we are implementing the model, does not want to have dummy environment records to be created.
I have referred to community article below
https://community.servicenow.com/community?id=community_question&sys_id=8eb947e5db5cdbc01dcaf3231f96199f&view_source=searchResult

[Stig Brandt]

Hi

Not sure if this helps you, but as I see this, you will always have a

- Business Application -> Ex. ServiceNow

- Business Service, Service Offering -> ServiceNow

- You could have Application Service Prod / UAT / Test - if you don't have dev/test, then only create "one" environment record.

If your SaaS provider is not providing other than the production environment, then you still have:

- BA-> AS -> Services both technical and business

[Ashwath2]

@Stig Brandt : This works generally, but my customer is not interested in creating an application service without the underlying infra that they can track. They would like to have the ability to raise incident on these kind of application.

[Stig Brandt]

Well, then the customer is on the wrong track, sorry, as you have 3 attributes -> service, service offering and "affected CI/configuration" - good luck.

[Bruce W]

Configuration Item is a mandatory field for our incidents so for SaaS-based applications we will create the production application service, e.g. "<saas app> - Production", even if no infrastructure is associated with it, and that is fine.

Bruce...