Has anyone seen an actual use case for the non-IT configuration model? Even if there is one -- say Musical Instrument extends Base Configuration Item, and Guitar extends Musical Instrument, for example -- the actual columns included in the Base Configuration Item table don't seem to paint a coherent picture. For example, the Base CI table contains the Asset reference field, but the Asset field doesn't refer to the Base CI table (cmdb); it refers to the Configuration Item table (cmdb_ci).
In fact, I can't imagine there would actually be a way to use any extended tables from the new Base CI class. On one hand, you can certainly define a non-IT asset class. But since a basic premise of configuration management is to record how an asset is being configured, the inability to correctly link non-IT assets and non-IT CIs seems like it renders this refactoring of the data model utterly meaningless at best, and non-functional at worst. If there is an example of how this is being used I'd love to see it, because in the whole system there is not a single reference directly to the Base Configuration Item table.
And as shown below, if I create a non-IT CI class called "Guitar" I can't even associate a Model Category with it. The whole usefulness of the CMDB goes out the window if you don't extend cmdb_ci!
