We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Business Application and Technical/Business Services

FredrikHenning
Tera Contributor

Hi,

 

We are having a discussion internally about adding IT operation tools like for example a Monitoring software as a Business Application. As we understand is quite common that companies also add  these kind of IT Business Application as Business Application not only Business Application that are for direct benefits for the business.

 

So our discussion has been is we choose to add a Monitoring Application as a Business Application and what to add a Service and Service offerings. Should it be a Tech Service or Business Service?  As i understand you creataean relationship to the Business Capability that this Business Application support to the Service object. And the Business application itself has a relation ship to the Service instance.  I would say Monitoring of servers or applications is a Tech service. But some of my collegues believe is a Business Service. Since they think it support the IT Business. See picture below

 

FredrikHenning_0-1770796691608.png

 

1 ACCEPTED SOLUTION

Mathew Hillyard
Giga Sage

Hi @FredrikHenning 

 

As @AndersBGS mentions, this kind of Service would definitely belong to the Technology Management Service table. The Service could be something like Monitoring, then the Offerings reference the different types of business monitoring available - these would then contain Service Instances that are instantiations of the Business Application (LogicMonitor, Nagios, SolarWinds etc.)

 

This is why planning your portfolio is an under-emphasised element of CSDM. It's mentioned in the Fly stage but in reality it's much more useful for organisations to be mapping out their portfolios at the beginning. You inevitably get these kinds of questions - "we have an <ABC> application and want to link it to services, should they be business or technical?"

 

The answer lies in where the service fits in and which portfolio. Take a look at @Barry Kant's post in this thread: https://www.servicenow.com/community/common-service-data-model-forum/should-end-user-services-be-rec... - it has a graphic with an example of the CSDM modelled using TBM, and shows the various taxonomy layers for business and technology management services. It can really help to both decide where a service can belong, and to uncover gaps where you may not have created services for a particular taxonomy layer.

 

Regarding your graphic above - Business Capabilities do not connect to Technology Management Services. This is intentional.

 

I hope this helps!

Mat

 

View solution in original post

7 REPLIES 7

CasperJT
Tera Guru

Hi Fredrik,

 

Adding on to Mathew and Anders' replies.

Unless you are offering monitoring as something that can be bought as a separate service, it is not a business service. It underpins your infrastructure to help you ensure its stability.

 

Straight out of the CSDM white paper:
"A Business service is a service type that is published to business users, and it typically underpins
one or more business capabilities as it provides specific value and outcomes.
o Business Service are the most abstract and will represent the highest value level in a
CMDB (see CSDM Service). A Business Service is how the customer sees the service
being delivered not what IT calls it.
o A Business Service type is related to a Business Service CI, and it’s associated with a
service owner and has one or more Business Service Offerings"

 

And 
"A Technology Management Service, previously documented as a Technical Service, is a service
type that is published to service consumers, and that provides the administrative and
operational functions to manage the technologies that are typically layered under one or more
Business and/or Application Services.
o A Technology Management Service type is related to a Technology Management Service
CI, and it’s associated with a service owner and has one or more Technology
Management Service Offerings.
o Users can view and manage the technologies that are provided to the business, and as
such should be Provider focused.
o Event Management enables monitoring of service performance and identifies health
issues for related infrastructure CIs and application services.
o Technology Management Services can be managed as part of the Service Portfolio in the
Service Consumption domain (that is, a Service Portfolio hierarchy can be referenced
from a Technology Management Service)."

 

As Mathew also pointed out, TBM is quite helpful in figuring out whether something is is a technology or business service.

CasperJT_0-1770888953670.png

The top three categories are business oriented and the bottom three are technology oriented.

Monitoring typically falls within "Operations" which is a Delivery Service.

 

It is worth considering the domains as well. Service Delivery and Service Consumption. You are monitoring your services to ensure proper availability and response times, but those are commitments in your offerings, not indivual offers to your business or clients. The purpose of monitoring your services is to ensure they can be delivered, thus it underpins them rather than being sold separately.

 

Hope this helps.

 

//Casper

FredrikHenning
Tera Contributor

Very helpful @Casper Thanks you

SohamTipnis
Kilo Sage

@FredrikHenning great point 👍

 

My vote is for technical service and offerings.

 

If you find my answer useful, please mark it as Helpful and Correct ‌😊


Regards,
Soham Tipnis
ServiceNow Developer ||  Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10