Directing ITSM is an often arduous task because there is such a disconnect between all of the elements that go into it. Antonio Piraino, in an article for infoTECH, explores how to bridge the gaps between all of the components of ITSM that seem to be growing further and further apart.
Finding Your Footing
There are a few very relevant, important problems when it comes to capturing IT data. The progression from a mainframe all the way to big data has inspired processing to be completed at a much quicker speed. This system also manipulates the data for the purpose of risk and compliance, causing another layer to this complicated scheme. All of these adversaries are what create inaccuracy and poor time output. There is the added problem of configuration amongst the hundreds of combined cloud services an organization may have too.
Enterprise service management (ESM) relies heavily on efficient devices for discovering assets within databases. If these configurations do not have real-time output, they are likely to become outdated and incorrect, which threatens the integrity of the entire system. There should also be some communication to inform the service management database hosting the list issues so that they too can take appropriate actions to alleviate the problems.
The integrity of the business can only be measured once these data points are captured. There should be a system in place in order to continuously monitor the state and well-being of assets and services provided by ITSM. Some find it unsavory if the data is only being provided to a U.S.-based SaaS.
The data gap is causing very imperious glitches. When analyzing these discrepancies, there is no use going back to the old problems and trying to work with inaccurate data; just begin implementing strategies that help to correct future headaches.
You can read the original post article: http://it.tmcnet.com/topics/it/articles/2015/09/29/410649-mind-gap-eluding-itsm-slippery-slope.htm