Creating Business _____ in an IBM Service Management solution

After doing many, many engagements with Tivoli's discovery tool (TADDM), one issue that always pops up where a business application/service/system should be defined.

Although TADDM has the capability of discovering the components of a business applications (the database servers, web servers, etc), and provides some basic ways to create business application (application template, application descriptor or individually selecting the components), TBSM claims to have better ways to create them.

I admit I'm not an expert in TBSM, and the lawn on the other side of the fence always seems greener, here are the problems I see:

• Assuming TBSM indeed has a better mechanism to associate CIs to Business Services, how can TBSM provide this information back to TADDM and CCMDB, so that these products can consume the BA definition for impact assessment, topology, etc ?
• The current strategy is to have TADDM as the discovery tool, populating CCMDB, which will perform the Change and Configuration Managements. If TBSM is the creator of the Business Application (or Service), the customer is required to have another problem in the solution architecture, just to create the BAs.

As the lawn in TBSM's backyard seems greener, shouldn't TBSM provide a component TADDM (or CCMDB) can use to create the Business Applications?

By the way, I created a small tool, called Automated Builder of Business Application, inspired in the old TBSM 3.1 ABS that traverses the dependencies of a certain CI and associated the entire connected graph to a Business Application. Take a look and see what you think...