service design

What is the differences between ITIL Incident Management and ITIL Problem Management, here is the explanation in simple comparison:

Process:
Incident Management: Deals with fighting symptoms to incidents

Problem Management: Seeks to remove the causes of incidents permanently from the IT infrastructure.

Interaction
Incident Management: interaction with customers is usually reactive, with the main objective being to find a workaround solution to restore normal services for the customer as soon as possible.

Download Free Customer Relationship Management (CRM) Vendor Selection Checklist. This checklist covers:
Remote users have multiple ways to access the application (e.g., Web, VPN, dial-up)
There is an off-line client that can synchronize with centralized data
There is security in place to ensure privacy of accounts, contacts, and sales data
Sales managers have a variety of ways to view staff accounts and activities
The application integrates or synchronizes with e-mail applications (e.g., Outlook)
The sales staff can create and link service requests with accounts
The sales staff views call center service requests by their accounts

As most common risks associated with acquiring software are that the selected solution does not satisfy the intended purpose or is not technically feasible. As consequences of a poor software purchase are increased costs, missed deadlines, or neglected requirements. To off set these risks, the IT auditor should evaluate the following controls:

1. Alignment with the company’s business and IT strategy
2. Definition of the information requirements
3. Feasibility studies (cost, bene. ts, etc.)
4. Identification of functionality, operational acceptance, and maintenance requirements
5. Conformity with existing information and system architectures

Gain an understanding of the underlying costs structure. IT costs are typically broken down into cost centers aligned to the management structure. A ese cost centers will have to be converted into service costs once the services have been defined.

Document the current pricing model, including services, allocation measurements, and service recipients. A current state will need to be compared to the new model to determine the change/impact to service recipients.

Interview service providers and service recipients to gain an understanding of the issues with the current cost allocation model and the perceived value of the services provided by IT.

1. No chargeback.
In this model, the IT budget is a separate function approved as part of the organizations planning process. To be effective, the organization must have a centralized prioritization and approval process to control IT spending. A is is a low-cost alternative, which also provides a centralized approach to funding for the good of the enterprise. Disadvantages include no accountability for demand and users do not necessarily understand the cost of the IT resources they are consuming.

2. Non-IT-based chargeback.
In this model, IT costs are allocated to business units based on a non-IT allocation metric (e.g., percentage of revenue). Again, this is a simple, low-cost approach to allocating IT costs but does require a centralized prioritization and approval process to e. ectively manage IT costs. A e disadvantages with this approach are that cost allocations do not necessarily correlate to the cost of the service and consumption/demand cannot be allocated to the business unit using the service.

3. IT-based chargeback.
Is approach uses IT measurements to allocate costs to user groups. Is model does align consumption with