TBSM A.D.2016

Hi everyone and Happy New Year 2016!

I hope that everyone celebrated his Christmas or days off happily, with family and/or dear friends and had time for other cool things, not just IT! 😉

Today, a quick look at IBM TBSM the product’s future  in 2016. It’s no change – TBSM remains important product to do relationship driven calculations of status and other metrics and everything you need to use it is still plugging it into a CMDB-kind of source and monitoring kind-of source (means KPIs monitoring connect to TBSM or event sources connect to OMNIbus which connects to TBSM). Still, the latest version of TBSM is 6.1.1 FP3. There’s next fix pack 4 expected in Q1.

What is important to keep saying (it’s been truth already since a while) you need not just TBSM to make a successful BSM solution working. Since a while my projects consist of:

– TBSM as a core calculation engine

– CMDB – as the service model source, it can be TADDM 7.3 with new modeling capabilities, it can be full-blood CMDB like Maximo CCMDB or ServiceNow or HP uCMDB

– Netcool/Impact – which is part of TBSM anyway, but can be a standalone server too, especially for balancing load, i.e. it can be dedicated to event analytics and correlations, also dashboards content drive

– JazzSM/DASH – for dashboards

– JazzSM/TCR/Cognos – for reports

– Netcool/OMNIbus – for events management and plugging in all other event sources like IBM Monitoring or Microsoft SCOM or IBM Network Manager or IBM TotalStorage Productivity Center or SAP Solution Manager or Oracle Enterprise Manager or others.

– any other source of measurements to take into account, it can be performance data source of any sort, up to your scope of work

TBSM will also need a self-monitoring capability, built in conjunction with but not limited to the KR9 agent.

That’s your BSM, more less. TBSM itself is powerfull but needs partner products. And your ideas for service models at the end.



Leave a Reply