Nowadays, the concept of ITIL is everywhere. But why would a user want to adopt ITIL? Just like people only take medicine when they are sick, many users only think about ITIL when they have problems. For example, a typical IT department might have just over a dozen people; some are busy, and some are idle. When no issues arise, everything seems fine. But once a serious incident occurs, only the highly skilled technicians can resolve it, creating a heavy network dependency on individuals. In other cases, as a user’s business processes evolve, existing IT management methods are no longer sufficient for the data center to ensure the integrity of business data or business continuity. Some IT department heads, when reporting to executive leadership, cannot provide a calculation method or a form to quantify the overall performance of the IT systems.
In these situations, the value of ITIL becomes apparent. From the perspective of the IT department’s priorities, ITIL helps ensure that the business network does not go down, systems do not crash, and data is not lost. At the same time, the data center hopes to streamline processes and make the best use of its people. ITIL allows everyone to perform their designated roles, enabling even less experienced staff to contribute effectively. Furthermore, ITIL can practically solve some user problems鈥攆or instance, by providing a set of data for the IT manager to report the department’s operational status to the executive level. A primary benefit of ITIL for users is its ability to improve customer satisfaction and elevate operational management levels, which is the core demand for most users. By continuously improving management levels and system availability while reducing service interruption time, customer satisfaction is enhanced.
ITIL is a management approach and a practical methodology that can effectively improve IT management capabilities and efficiency. IT operations management forms the underlying foundation of the ITIL standards framework. Only when this foundation is well-established can process-based management truly be realized on top of it. The underlying monitoring in IT operations management is indispensable and necessary. The purpose of monitoring is to reduce workload; when elevated to the operations level, this enables a seamless transition, thereby improving operational levels and optimizing management processes.
There is a perception that ITIL is only for large corporations. In reality, implementing ITIL is often harder for a large company than a smaller one. With a larger workforce, a bigger organization, and a wider scope of operations, implementation is not so easy. Starting from a smaller company, you can first implement monitoring, then proceed to in-depth analysis, fault diagnosis, and information optimization. Then, analyze ITIL service processes鈥攈elp desk, service process tracking, configuration management, change management, and other functionalities鈥攁nd develop a tailored solution based on urgency. Proceeding step by step like this makes the implementation process much more convenient.
ITIL entered the Chinese market in 2003. After years of development and refinement, a large number of excellent vendors have developed IT operations management platform software that complies with ITIL specifications. However, the reality is that while vendors overwhelmingly claim their products are based on ITIL best practices, very few have actually been put into effective, practical use.
According to a report within the industry, the success rate of ITIL projects is only 40%. Regarding this, Zhu Zhijing, Technical Director at Broadgate Communications Technology Co., Ltd., believes the relatively low project success rate is mainly due to the following factors:
1. Domestic management software applies the 80/20 rule, solving 80% of problems with 20% of methods. Domestic software understands users better, whereas foreign products are rarely used effectively in practice. International vendors like IBM, HP, and BMC have strong technical backgrounds, but they struggle with local adaptation. They are relatively inflexible about not doing Chinese-language processing or local R&D, making their products very inconvenient for local users.
2. Some vendors transitioning from OA or ERP backgrounds are not proficient in underlying monitoring software. They either OEM a product that excels in this area or use open-source code for secondary development, lacking industry-specific accumulation. Their advantage is that many clients have already purchased their OA or ERP software, giving them good customer relationships. The disadvantage is that they cannot even build a solid underlying monitoring platform, lacking in-depth research and development, making their foundation unstable. The upper-layer operations solutions they develop are often based on their previous OA/ERP experience, resulting in products that look right but are wrong in essence.
3. Some monitoring vendors, just to follow the trend, have forcibly slapped an ITIL label onto their products, even though they completely lack the capability to do ITIL properly.
4. Many vendors adhere to ITIL standards, but very few have successfully built solid underlying technical monitoring, connected the monitoring with