SOI - Service Oriented Infrastructure

Recently I have been working on something entitled Service Oriented Infrastructure (SOI). The premise being the infrastructure required in order to effectively apply service orientation to an enterprise or large scale software component. Most people shy away from this problem due to the sheer number of moving parts that in contains. Moreover, the bar for entry to this realm is high with many people/vendors touting a big bang theory.

My take on this is radically different. Besides giving my normal diatribe about how maturity models suck, I'd like to talk about how to lower the entry constraints and get what the client really wants: a way of understanding and integrating the newer technology. To do this is really quite simple, and it all comes down to perspective.

Capabilities are arranged into hierarchical structures with each level being known as a generation. I normally start out with up to three generations within a given domain, SOI for instance, and then go from there once the customer has deduced what they would like to see.

Here is a list of the capabilities for Generation 1 System and Gen2 Service Monitoring. There are plenty more generations under Gen3 item, but this is a pretty good first take on what you'd like to understand about Service Monitoring.

ASK: Does anyone have other capabilities that they believe would fall under Gen2 Service Monitoring? Also, for each Gen3 capability what would you expect to see under each?