Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
The Itil Community Forum: Forums
ITIL :: View topic - Core Service & Non-Core Service -Discussion-
Posted: Sun May 04, 2008 2:30 pm Post subject: Core Service & Non-Core Service -Discussion-
Hi All
I had a argument with my Manager about Core IT Service & Non-Core IT Service<< he was saying the core IT Service is the main service of the organization that built on the IT -Our IT is Business Enabler- I was saying NO ,, the Core IT Service is the service that only IT can provide e.g. E-mail.
From ITIL point of view what do you think is IT core service & IT Non-core service,, and give me an example if possible.
Joined: Oct 07, 2007 Posts: 441 Location: Jakarta, INA
Posted: Sun May 04, 2008 5:11 pm Post subject:
Hi Arab_ITIL,
ITIL concerns of providing good IT Service and therefore it's aim is good IT governance. It's target is service, all the same, regardless to core or non-core.
It is you or your boss who decides what is/are core and non-core IT for your company
In contrary to the previous post of Asril, it is not up to the IT Service provider to determine what is the core service (or even good service) but it is the customer e.g. the business that will have to decide. Why don't you ask them what is the core service?
According to ITIL an IT Service will have to provide business value and more value than the running of the service will cost. Therefor the easiest way to determine if a service is core is to ask the business if it is possible to do without that service. What happens if the e-mail (or messaging service) is no longer operational? What effect on business will that have?
The hard part is to figure out what the scope of the service is. For instance, a LAN service doesn't provide any business functionality, but without a Lan many other services won't work (like the messaging/communication service).
Joined: Oct 07, 2007 Posts: 441 Location: Jakarta, INA
Posted: Mon May 05, 2008 10:47 am Post subject:
Hi,
I could agree with you, Paul
I've read some articles that wrote the same as yours.
But since there is no exact definition of what is core and non-core, everybody can have their own understanding.
My company has a lot of customers with various type of services, like we provide airline applications (ticketing, res, DCS, etc.). We also provide SAP BP consulting (FI/CO, MM, HR) for other customers. We also provide Data Center services (housing and co-location) for other customers.
Are you going to maintain multiple core for a situation like that?
We didn't. We saw that most of the money came from the airlines, so we decided that the airline applications is our ultimate core service. The others are core as well, but the former will come first in priority.
On the other hand, airlines as our customers, also have their terms of core and non-core.
- The reservations system chain (from ticketing to DCS) is the core to their perspective.
- There are also some value added systems such as RMS and Frequent Flyer. These are non-core according to their perspective.
Don't question because I only quote their definition.
I understand your perspective. Since you are an external (probably commercial) service provider you have a situation in which you have to determine which service (and which customer) is the most valuable to yourself. You have to determine on which service you make the most money or might lose customers on. In that case you are right that you determine what is core to you yourself.
Most IT departments do not have this situation where they can determine themselves which service is the most important to them. They do not have paying customers or do no not have the luxury to turn a customer away. In those cases it is the business that will determine what is core. As you demonstrated yourself by noting that customers also differentiate between core and non-core services for themselves.
Bottomline though is that in your case as well the customer will determine what is the core service your company provides. That is the service they are willing to pay more money for, special to improve reliability and availability of that service. If the customer is not interested in the service then it will not be a core service anymore for you.
Joined: Sep 16, 2006 Posts: 3590 Location: London, UK
Posted: Tue May 06, 2008 8:52 pm Post subject:
To follow up
ITIL does not define core, non core etc about the service
If something has been identified with the following aspects, it is a service
1 - users/ consumers / customers
2 - IT deliverable
3 - IT provider
beyond that, it is up to the business concerned to define whether a service is core or not _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum