Shulou(Shulou.com)06/01 Report--

ITSM personalized requirements is what, I believe that many inexperienced people are helpless about this, this article summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

In order to ensure that the final ITSM is useful, usable and easy to use, in addition to the standard methodology, the selected ITSM also needs to meet individual requirements. In what ways are personalized needs generally reflected? What risk points should be noted when meeting the necessary individual needs?

I. What are the individual needs?

The IT service management characteristics of most organizations in China are similar and general, almost irrelevant to their respective industry and business characteristics. The requirements of these organizations in the IT service management process that can be implemented are basically general, so there are few personalized requirements in the general management process, which is also the fundamental reason why they can do finished ITSM.

ITSM personalization requirements for most organizations in China are generally:

Interface with other systems, confidentiality security requirements, industry regulatory requirements. Interface with other systems: Generally, it interfaces with established repair platforms such as call center, service desk, WeChat or OA, without changing user habits and making full use of existing resources; or it interfaces with IT monitoring and early warning software to realize automatic generation of monitoring early warning events.

Confidentiality Security Requirements:

Secret agencies need all IT systems to have a high level of confidentiality security. ITSM, as an IT system, naturally needs to meet its special level of confidentiality security, such as access encryption, approval encryption, information encryption and other technologies.

Industry regulatory requirements:

Individual organizations have industry regulatory requirements for IT systems or operation and maintenance processes, such as the need to provide all system operation logs meeting certain standards, and the need to forcibly retain image evidence such as screenshots and videos for all operation and maintenance processes. Of course, it is not excluded that some organizations have personalized requirements on general processes. There are generally two kinds of personalized requirements. One is that enterprise IT service management is very mature and has formed established management processes. Even if it is inconsistent with general processes, it is difficult to change them. The other extreme is that IT service management is too random, which often puts forward some personalized requirements that do not meet the general management requirements and often have management loopholes. Second, the individual needs that must be met, what are the risks? As for the requirements for interfaces with other systems, confidentiality and safety requirements, and industry regulatory requirements, there is no risk in meeting these requirements because they have no impact on the original process and functions of the product.

There are individual requirements that must be met based on compliance with common management requirements, and the following risks are present and future:

1, high quality risk: personalized requirements are not universal, the product after the completion of secondary development has not been verified by other customers, product maturity is low, there may be quality defects, high quality risk; and subsequent version upgrades This part of personalized requirements will once again become a source of quality risk for the new version.

2. Long construction period: personalized requirements need to be sorted out separately, product design and secondary development, and comprehensive testing needs to be done in combination with the overall product. The construction period is long, and during this period, it may also face the rework risk caused by the adjustment of requirements.

3, high cost: to achieve personalized demand, now need to pay extra cost; and for the subsequent version upgrade, because it can not directly use the general upgrade version, need to develop the upgrade version separately for the personalized demand version, can not realize the bulk customer cost amortization, can only be borne by the personalized demand organization itself, upgrade cost is high.

After reading the above content, do you know what the personalized requirements of ITSM are? If you still want to learn more skills or want to know more related content, welcome to pay attention to the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.