I. Method Origin
Methodology is an important aspect of O & M work. It can make our O & M work clearer and more organized.
This O & M method is derived from ITIL instead of re-creation. On this basis, we can improve the daily work of the game to form the current state.
Iii. method model
1. ITIL v3
ITIL is huge in content, but a diagram basically covers the key points of itil. ITIL divides the O & M work into three stages based on the service strategy, namely service design-service conversion-service operation, continuous iteration and continuous improvement. It can be seen that the core idea is to perform stages and iterations (in fact, almost everything can be done in this way, which also reflects the scientific nature of ITIL ).
2. Yu Jian O & M method
Yu Jian's O & M method is exactly the same as the ITIL core idea. First, it sets the O & M goal and divides the O & M work into three stages for continuous improvement.
3. usage of the Method
L fully understand the O & M status
Through this method, you can have a clear idea of the O & M work, and understand the risks, accidents, and solutions of the business.
L solve problems in the Early Stage
If the preliminary R & D phase is not well controlled, it will bring great risks to the later O & M. You can check, evaluate, and eliminate these risks as soon as possible according to the project shown in the figure, otherwise, it will be troublesome to adjust it after going online.
L solve the handover problem
In the company, internal and external changes will lead to the handover problem. Some colleagues often ask what aspects should be taken into account for the handover. I think if we take all the points in the figure into consideration, that is the foundation of the smooth handover.
L solve O & M Management Problems
How can the leader control the overall O & M quality? If we use the above methods, we can basically eliminate the O & M differences caused by differences in personal capabilities.
4. Difficulties in the Method
In the figure, there are many sub-items, but there are not many sub-items, such as capacity design, but rather the difficult part, especially the performance, to judge the performance bottleneck, both in combination with business characteristics, we also need to have a deep understanding of the operating system, software and hardware, and even long-term observation. We also come to different conclusions on different individual technical levels, which may lead to different judgments.