Mapping Services that Don't Focus on Incidents and/or Have and Associated CI?

[CD4WG]

I'm trying to develop a service model for IT services. The model for incident resolution is well defined. However, I'm unsure how to justify mapping services that are less focused on direct interaction with the end user and more on serving the business or other IT functions. For example, aspects of provisioning endpoints, endpoint software deployment, and endpoint engineering. Is it a CSDM best practice to map services that are more likely to work with request or asset management (as opposed to handling tickets)? Does a technical service model have to be associated with an explicitly named CI? 

[Robert Campbell]

Why would you consider these any different? In this scenario, the company is the customer of your IT department. You are providing IT Services to the company. The application that you have to provision endpoints is a business application that has an instance and infrastructure. It has a technical service offering and there are also business services which would be "Endpoint Provisioning" which could be service requests.

There is always a customer.