ITIL Incident Management : 296 Incident management processes The main incident management processes are….

ITILITIL Incident Management : 296 Incident management processes The main incident management processes are….

296 Incident management processes The main incident management processes are the following: • • • • • • • • Incident detection and recording Classification and initial support Investigation and diagnosis Resolution and recovery Incident closure Incident ownership, monitoring, tracking and communication Establish incident framework management Evaluation incident framework management Examples Incidents should be classified as they are recorded, Examples of incidents by classification are: • Application • service not available • application bug • disk-usage threshold exceeded • Hardware • system-down • automatic alert • printer not printing References [1] ITIL Incident Management (http:/ / index.

Php?page=Incident_Management) – The ITIL Open Guide Bibliography • Bruton, Noel, How to Manage the IT Helpdesk — A Guide for User Support and Call Center Managers.

ISBN 0-7506-4901-1. Information management 297 Information management Information management (IM) is the collection and management of information from one or more sources and the distribution of that information to one or more audiences.

This sometimes involves those who have a stake in, or a right to that information.

Management means the organization of and control over the structure, processing and delivery of information.

Throughout the 1970s this was largely limited to files, file maintenance, and the life cycle management of paper-based files, other media and records.

With the proliferation of information technology starting in the 1970s, the job of information management took on a new light, and also began to include the field of Data maintenance.

No longer was information management a simple job that could be performed by almost anyone.

An understanding of the technology involved, and the theory behind it became necessary.

As information storage shifted to electronic means, this became more and more difficult.

By the late 1990s when information was regularly disseminated across computer networks and by other electronic means, network managers, in a sense, became information managers.

Those individuals found themselves tasked with increasingly complex tasks, hardware and software.

With the latest tools available, information management has become a powerful resource and a large expense for many organizations.

In short, information management entails organizing, retrieving, acquiring and maintaining information.

It is closely related to and overlapping with the practice of Data Management. Information management concepts Following the behavioral science theory of management, mainly developed at Carnegie Mellon University and prominently represented by Barnard, Richard M.

Cyert, March and Simon, most of what goes on in service organizations is actually decision making and information processes.

The crucial factor in the information and decision process analysis is thus individuals’ limited ability to process information and to make decisions under these limitations.

According to March and Simon,[1] organizations have to be considered as cooperative systems with a high level of information processing and a vast need for decision making at various levels.

They also claimed that there are factors that would prevent individuals from acting strictly rational, in opposite to what has been proposed and advocated by classic theorists Instead of using the model of the economic man, as advocated in classic theory, they proposed the administrative man as an alternative based on their argumentation about the cognitive limits of rationality.

While the theories developed at Carnegie Mellon clearly filled some theoretical gaps in the discipline, March and Simon [1] did not propose a certain organizational form that they considered especially feasible for coping with cognitive limitations and bounded rationality of decision-makers.

Through their own argumentation against normative decision-making models, IE, models that prescribe people how they ought to choose, they also abandoned the idea of an ideal organizational form.

In addition to the factors mentioned by March and Simon, there are two other considerable aspects, stemming from environmental and organizational dynamics.

Firstly, it is not possible to access, collect and evaluate all environmental information being relevant for taking a certain decision at a reasonable price, IE, time and effort.[2] In other words, following a national economic framework, the transaction cost associated with the information process is too high.

Secondly, established organizational rules and procedures can prevent the taking of the most appropriate decision, IE, that a sub-optimum solution is chosen in accordance to organizational rank structure or institutional rules, guidelines and procedures,[3] [4] an issue that also has been brought forward as a major critique against the principles of bureaucratic organizations.[5] Information management According to the Carnegie Mellon School and its followers, information management, IE, the organization’s ability to process information, is at the core of organizational and managerial competencies.

Consequently, strategies for organization design must be aiming at improved information processing capability.

Jay Galbraith [6] has identified five main organization design strategies within two categories — increased information processing capacity and reduced need for information processing. 1.

Reduction of information processing needs 1.

Environmental management 2.

Creation of slack resources 3.

Creation of self-contained tasks 2.

Increasing the organizational information processing capacity 1.

Creation of lateral relations 2.

Vertical information systems Environmental management.

Instead of adapting to changing environmental circumstances, the organization can seek to modify its environment.

Vertical and horizontal collaboration, IE cooperation or integration with other organizations in the industry value system are typical means of reducing uncertainty.

An example of reducing uncertainty in relation to the prior or demanding stage of the industry system is the concept of Supplier-Retailer collaboration or Efficient Customer Response.

Creation of slack resources.

In order to reduce exceptions, performance levels can be reduced, thus decreasing the information load on the hierarchy.

These additional slack resources, required to reduce information processing in the hierarchy, represent an additional cost to the organization.

The choice of this method clearly depends on the alternative costs of other strategies.

Creation of self-contained tasks.

Achieving a conceptual closure of tasks is another way of reducing information processing.

In this case, the task-performing unit has all the resources required to perform the task.

This approach is concerned with task (de-)composition and interaction between different organizational units, IE organizational and information interfaces.

Creation of lateral relations.

In this case, lateral decision processes are established that cut across functional organizational units.

The aim is to apply a system of decision subsidiarity, IE to move decision power to the process, instead of moving information from the process into the hierarchy for decision-making.

Investment in vertical information systems.

Instead of processing information through the existing hierarchical channels, the organization can establish vertical information systems.

In this case, the information flow for a specific task (or set of tasks) is routed in accordance to the applied business logic, rather than the hierarchical organization.

Following the lateral relations concept, it also becomes possible to employ an organizational form that is different from the simple hierarchical information.

The Matrix organization is aiming at bringing together the functional and product departmental bases and achieving a balance in information processing and decision making between the vertical (hierarchical) and the horizontal (product or project) structure.

The creation of a matrix organization can also be considered as management’s response to a persistent or permanent demand for adaptation to environmental dynamics, instead of the response to episodic demands.

Read more about ITIL Incident Management : 296 Incident management processes The main incident management processes are….:

Accredited ITIL Foundation, Intermediate and Expert Certifications

Accredited ITIL Foundation, Intermediate and Expert Certifications, Learn more about ITIL HERE:

ITIL and ITIL Incident Management : 296 Incident management processes The main incident management processes are….

ITIL - ITIL Incident Management : 296 Incident management processes The main incident management processes are….

ITIL and ITIL Incident Management : 296 Incident management processes The main incident management processes are….

ITIL - ITIL Incident Management : 296 Incident management processes The main incident management processes are….