The previous blog introduced the IM/IT Inventory. In this blog, I am going to take my first stab at how the applications are potentially mapped to the Inventory as indicated in the diagram below.
At the bottom-left are the applications that are the most general purpose and easy for the user to make configuration changes to. A great example are the office productivity suites such as Microsoft Office. Diametrically opposed are Bespoke Applications that an organization has purposed built. The application in this case may exists only in the organization and may or may not have been written in either a language or manner making system changes easy.
The red box overlaying the model is what I would suggest be included in an IM/IT Inventory. The green braces is the grey zone discussed in the previous blog, whether to include or not these ‘applications’.
Personally, I have built a number of applications that fall into this grey zone. Typically budget and reporting systems, they were fairly sophisticated tools that provided unique organizational value. In future blogs, I hope to drill down a bit more on this area and ask how to measure, report and more importantly – what to do with the information coming from an IM/IT Inventory. As always send me your comments.