After a successful CMG ’08 show and the holidays I was finally able to catch up and continue my discussion with Lanir Shacham (Founder and CTO) of Correlsense. The Correlsense team, friends and families are all safe and sound during the current Israeli crisis which I’m happy to hear.
In this podcast, Lanir and I dive into the approach that Correlsense and their SharePath product takes for the first of four key areas that a Business Transaction Management (BTM) solution must incorporate which is Transaction Discovery.
Listen to the podcast for insight into the thoughts Lanir shares on these Transaction Discovery topics:
- Transaction Discovery Techniques and why an agent based approach is the only way to discover end-to-end transaction flows.
- Transaction Types including synchronous, asynchronous and aggregate transaction scenarios.
- Transaction Discovery Agents and why one core agent type is all that’s needed in most cases.
- Architectures for Transaction Discovery Storage, Transaction Data Store or Data Warehousing, OLAP and techniques for supporting both real time and historical analytics and intelligence capabilities (monitoring, dashboards, reporting, charting, what if’s, etc.)
In our next podcast, Lanir and I will discuss the second core capability of a BTM solution which is Transaction Tracing, Tracking and Stitching.
You may subscribe to my podcast feed via Feedburner, iTunes or simply play or download the podcast from this post.
If you have any feedback or comments on the topic of BTM for myself or Lanir please leave comments. If you’re a vendor, subject matter expert or practitioner in the area of Business Transaction Management (BTM) and would like to chat on a podcast, please feel free to contact me directly.
Comments on this entry are closed.
I actually believe that the big consulting firms are trying to sell bodies, or making high profit margins. I have implemented BSM solution for clients in about 125K budget.
It’s not about fancy Dashboards, buying products or even CMDB for that matter. Its about right level of aggregation and encapsulation of information for various stakeholders and addressing the concerns.
Key to BSM Success: Aggregation, Encapsulation
You can lead the horse to water …
How do we then realize the value from BSM and this aggregation and encapsulation? Do we not then need to focus on operationalization of this, changing the way people think, processes and workflow operate, etc? I think there’s a huge amount of work needed outside of the technology component to truly be successful with BSM.
I’d love to dive in more with you. Would you like to do a podcast? Ping me!
Doug
Thanks Doug for your response.
IMHO the value from BSM comes out from leveraging information in the context of the Line of Business/Stakeholders.
Aggregation and encapsulation based on stakeholder needs to reflect the impact, status, forecasts, capacity and strategic directional planning information.
Key quality indicators for a BSM solution (Litmus test):
1) Adaptability (to the context) — Although this is a difficult measurement, we need to evaluate a solution (not tool) for its adaptability.
2) Accuracy(of the status reflected) — I have seen even the best tools for reporting being abused and the entire application health turning red on CXO’s dashboards
3) Extensibility – Time to add/enhance key information should be minimal and relatively less rework.
Key points to success in BSM from my perspective:
1) Knowing Business Drivers
2) Know the end goal before starting implementation
3) Start small
4) Use Mind mapping to build view design for (TBSM/Introscope/Wily products)
5) Ubiquitous language
To summarize, aggregating the information based on the stakeholder requirements for growing and retaining business and services; BSM solution needs to be evolved in a model and should encapsulate information which is not relevant to stakeholders.
Industry needs to come together and form guidelines for BSM implementations in various flavors.