7 - Indira Gandhi Centre for Atomic Research
7 - Indira Gandhi Centre for Atomic Research
7 - Indira Gandhi Centre for Atomic Research
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
The object of Change Management is to ensure that standardized methods and<br />
procedures are used <strong>for</strong> efficient and prompt handling of all Changes, in order to minimize<br />
the impact of any related Incidents upon service. A single Change Management process,<br />
<strong>for</strong> the efficient and effective handling of changes, is vital to the successful operation of<br />
any IT organization. Changes must be carefully managed throughout their lifecycle from<br />
initiation and recording, through filtering, assessment, categorization, authorization,<br />
scheduling, building, testing, implementation and eventually their review and closure.<br />
Change Management is responsible <strong>for</strong> controlling Change to all CIs within the live<br />
environment. It is not responsible <strong>for</strong> change within ongoing projects, which are<br />
controlled by the project change process.<br />
The object of Release Management is to take an holistic view of a Change to an IT<br />
service and ensure that all aspects of a Release, both technical and non-technical, are<br />
considered together. Release Management is responsible <strong>for</strong> all legal and contractual<br />
obligations <strong>for</strong> all hardware and software in use within the organization. Release<br />
Management establishes secure environments <strong>for</strong> both hardware and software.<br />
The object of Incident Management is to restore normal service to operation as quickly<br />
as possible with minimum disruption to the business, thus ensuring that the best<br />
achievable levels of availability and service are maintained. It is responsible <strong>for</strong> the<br />
management of all incidents from detection and recording through to restoration and<br />
closure. Incident Management should be used to ensure the best use of resources to<br />
support the business, to develop and maintain meaningful records relating to Incidents,<br />
and to devise and apply a consistent approach to all Incidents reported.<br />
The object of Problem Management is to minimize the adverse effect on the business of<br />
Incidents and Problems caused by errors in the infrastructure, and to proactively prevent<br />
the occurrence of Incidents, Problems and errors. To achieve this Problem Management<br />
assists Incident management by managing all major incidents and problems and record all<br />
workarounds and rising change to implement permanent structural solutions wherever<br />
possible.<br />
The object of the Service Desk is to act as the central point of contact between the User<br />
and IT Service Management. To handle Incidents and requests, and provide an interface<br />
<strong>for</strong> other Service Management activities such as Change, Problem, Configuration, Release,<br />
Service Level and IT service Continuity Management. The Service Desk, unlike the other<br />
ten disciplines (processes), is a function essential to effective Service Management. More<br />
than just a Help Desk, it is the principal operational interface between IT and their Users.<br />
A good first impression by each of its Users is predicted upon its per<strong>for</strong>mance and<br />
attitude. Often a stressful place <strong>for</strong> staff to work, underestimating its importance, high<br />
profile and the skills required to per<strong>for</strong>m the duties well can severely hinder an<br />
organizations ability to deliver high quality IT services.<br />
Service Delivery<br />
• Service Level Management<br />
• Capacity Management<br />
• Financial Management <strong>for</strong> IT services<br />
• Availability Management<br />
• IT service Community Management<br />
122