Improves the ease of implementing and managing services for dynamic, high risk volatile and rapidly changing business needs. Improves the measurement demonstration of value. Identifies the triggers for improvement and change anywhere in the service lifecycle. Addresses the current gaps and deficiencies in ITIL today. ANECDOTE The traditional quality management system for organizations is ISO9000.
In recent years, many major organizations have adopted the ITIL framework as their methodology for management of IT infrastructure. The ISO9000 and ITIL combination is in fact a very powerful one.
There are a growing number of people aware of the benefits of ISO9000 and ITIL.
As a matter of fact, since December 2005 there is now another ISO standard specifically aimed at certifying IT Service Management Processes (based on ITIL); this is the ISO 20000 standard.
The primary distinction between the two is that while ISO9000 is focusing on business process quality, the ISO 20000 standard focuses on IT Service Management processes. Both ITIL and ISO 20000 are in a state of continual update and improvement.
ISO20000 and ITIL both have well defined control mechanisms in place for ensuring that they reflect the current nature of business environments throughout the world. ISO is controlled by the International Services Organizations and ITIL is controlled by the Office of Government Commerce (OGC) in the United Kingdom. ANECDOTE – Why Bother? With cheap hardware prices, capacity planning may be seen to have lost its importance.
You can always upgrade later! The fact that hardware systems can be upgraded easily has, in recent times, diverted attention away from this key process area. There are two main concerns that make capacity planning critical. The first is the rate of technical change in the distributing computing sector.
We now measure progress in “Internet years” — equivalent to a fraction of a typical calendar year. The second is that today’s systems are primarily being developed within complex multi-tier architectures. This rapid change, coupled with the increase in complexity of 3-tier architecture, is causing system designers to pay closer attention to capacity. Five years ago, a designer could roll out a new system with a rough estimate of capacity and performance.
The system could then be tuned or more capacity added before all of the users had been converted to the new system.
The process was reasonable because the systems were typically not mission-critical. Today, there’s no time for this approach.
Once systems are in place they become an integral part of the overall operation.
Upgrade downtime is increasingly expensive in both time and resources.
In addition, the added complexity of the environment typically requires more care, due to the interdependency between various application components. Capacity planning is driven purely by financial considerations.
Proper capacity planning can significantly reduce the overall cost of ownership of a system.
Although formal capacity planning takes time, internal and external staff resources, software and hardware tools, the potential losses incurred without capacity planning are staggering. That is why we should bother!!
Read more about Both ITIL and ISO 20000 are in a state of continual update and improvement: