銆?1CTO.com Comprehensive Report銆?STRONG>Goodbye Chaos, Starting from the Service Desk
The concept of ITSM has been circulating in the industry for many years, but few organizations have truly implemented it successfully and persisted in its use. Users often complain that after adopting multiple ITSM management software tools, processes have become even more cumbersome than before. Without ITSM, when the printer in the Finance Department malfunctioned, one simply had to call Xiao Zhang from the Operations and Maintenance (O&M) department. Xiao Zhang would then dash over to the Finance office and resolve the issue in a few dozen minutes. Now, however, one calls the service desk. If the financial software is not working properly, describing the problem alone can take a long time. From waiting for someone to handle the issue to its final resolution, there are several intermediate steps. Does resolving a problem really need to go through so many steps? Is ITSM truly a waste of time rather than a time-saver? I think this type of question is highly representative when implementing ITSM.
Penny Wise, Pound Foolish
As mentioned in the user complaint earlier, previously one only had to make a single phone call and Xiao Zhang would trot over to the Finance office to quickly resolve the problem. But then I need to ask: when Xiao Zhang was fixing that issue, if a more critical failure occurred, who else in the O&M department was answering the phone? Was anyone available to respond to that more critical failure? If the answer is no, then I think our O&M system had serious hidden risks before implementing ITSM. And if the answer is yes, I would like to ask a follow-up question: if there are many problems occurring simultaneously and all our O&M personnel have been dispatched, will there still be someone available to respond to critical failures? If not, then I think our O&M system still has serious hidden risks, because while handling minor issues or failures, we might overlook critical business disruptions.
In summary, we are actually discussing a conflict between O&M personnel costs and rapid problem response. On one hand, we need to control O&M costs; on the other hand, we must provide high-quality IT services. We cannot compromise the service quality of critical business operations just to control costs, nor can we blindly increase O&M staff simply to improve service quality. How can we strike a balance between these two, ensuring both O&M costs are managed and IT service quality for business departments is guaranteed?
How to Have Your Cake and Eat It Too?
I believe the service desk plays a crucial role here. Through the service desk, issues can be quickly analyzed based on urgency and priority, and then assigned to different maintenance personnel according to problem type. This resolves the conflict between cost and quality. First, by categorizing requests based on urgency and priority, the limited maintenance staff can prioritize handling critical failures during O&M management processes. Once critical issues are resolved, general failures can be addressed in sequence. This achieves the effect of having your cake and eating it too.
We can see the service desk & incident management interface of Mocha Network Management Software in the figure below. We can clearly see that all failure requests first enter a unified request pool, and can then be automatically assigned based on urgency and priority. Alternatively, O&M personnel can choose to handle failures of different priorities based on their own availability.
|