The first day I attended on an ITIL formation, the teacher told us: “ITIL is suitable for all sizes and types of companies, the secret is to know how adapt it.” But the more I understood the ITIL philosophy, the more I thought that it was designed for big sized organizations. Only in managers and coordinators, you can count more than 30 people. So how can it be adapted to small sized organizations?
In this post I will cover the mayor adaptations of the ITIL framework to IT departments of less of 20 people. … Read the complete post
We all know that Action Request System is mainly focused to create applications for IT support processes. That’s the reason for having the ‘Assigned to’ field included in the set of core fields when creating a form. But this has not been a reason to expand the Remedy apps family to non-support processes, like configuration management, or fiscal management. Also the Remedy platform can be used to create outstanding apps for non-IT purposes.
In this post I will review the possibilities of ARS, and how to expand it to non-IT processes. … Read the complete post
BMC Remedy Service Desk allows us to relate each support group to a support level. This classification comes from an ITIL recommendation. Most Remedy implementations declare the level of the support group but don’t utilize it extensively. It is easy that in a multi-tenancy environment each company uses it’s own classification criteria for support levels. Or worse, each Remedy administrator selects a level when creating the group almost randomly.
As in a lot of other configurations, having a consolidated criteria can provide us with a lot of information when analyzing the service.
In this post I will review the support level concept and provide a recommended classification. … Read the complete post