Neebula advertises an HP uCMDB integration which uses a patented automatic Service Modeling technology (ServiceWatch)… one that dramatically reduces the time it takes to build Service models in UCMDB/RTSM.

Neebula CMDB

Their webinar claims ServiceWatch can reconcile cleanly with DDMa CI's, though it is not shown in the demo.
Unfortunately, an explanation of how the automatic "top-down, entry-point" Service Modeling actually works, is also missing.
Beyond simple Service Modeling use cases, I cannot see how a HTTP URL entry-point for example will take me all the way back, past the network layer, to not only the clustered app servers themselves, and running software therein, and the separate and clustered DB's supporting them, but the critical DB instances themselves.  There are so many "what-ifs" along this path that I can't help but think of the great potential for misleading models! 
Further, if the Service Delivery team is now in charge of building Service Models – as the webinar seems to suggest, how will IT or Service Delivery ever know if an application is even right?
There is still a disconnect – no matter how revolutionary this "entry-point" modeling is, the models still need to be verified, scrubed, etc.
Which is of course the "lengthy" portion of Service Modeling in the uCMDB to begin with.
Regardless, I'd like to be proven wrong – Service Modeling IS the "achilles heel" of the UCMDB/BSM suite of products.
Take a look for yourself.  What do you think?