While January 2009 has taken a slower start in the economy and on the job front, I kept busy in the off hours cranking out some great content this past month.
I’ve hinted off an on the past few months about the plans I have for expanding the Business Service Management (BSM) discussion. The broader BSM Value Proposition must be talked about. BSM must be included in every discussion taking place in the inner vendor and IT spheres. BSM for Cloud Computing (#BSMcc), Green BSM (#greenBSM), Dynamic BSM (#dynamicBSM), whatever. The broad based value proposition for the next generation of BSM applies everywhere, whether these technology initiatives are inwardly or outwardly focused. They’re all about helping the business meet its goals and objectives. Stay tuned! If you’re up for contributing and collaborating, contact me!
Interested in contributing your comments on a BSM Survey being conducted by Paul Burns of EMA? Check out this post.
Hey, why aren’t you on Twitter? You’re missing my “real time” thoughts, ideas and bickering and life! Follow me here.
Themes this past month have been in one of the key BSM Value Proposition areas in Business Transaction Management (BTM). I’ve been speaking with many in this emerging area over the past couple months. Listen to these BTM podcasts I published in January.
BTM Podcast: Correlsense and Transaction Discovery
BTM Podcast: Correlsense and Transaction Tracing, Tracking and Stitching
BTM Podcast: Correlsense and Transaction Monitoring
BTM Podcast: Architecture and Deployment Planning for IBM Tivoli ITCAM for Transactions v7.1 with Gulf Breeze Software Part 1
BTM Podcast Architecture and Deployment Planning for IBM Tivoli ITCAM for Transactions v7.1 with IBM ISST SWAT Part 1
BTM Podcast Architecture and Deployment Planning for IBM Tivoli ITCAM for Transactions v7.1 with IBM ISST SWAT Part 2
I’ve started a new weekly series where I’m going to share my thoughts and listen to your conversations on the importance of having an overarching and guiding BSM Strategy is to true value oriented and game changing BSM success. Follow along and share your thoughts.
Business Service Management Strategy Tip of the Week #1
Business Service Management Strategy Tip of the Week #2
Business Service Management Strategy Tip of the Week #3
Following in this weekly post goal, I’m going to try and share some bit of knowledge, tip, trick, best practice, scenarios, design patterns, etc. in my Tivoli Business Service Manager (TBSM) Support Tip of the Week. If you’ve got anything you’d like me to dig into and share on related to TBSM and any of it’s enabling products, technologies, features or functions, please leave comments!
Tivoli Business Service Manager (TBSM) Support Tip of the Week #1
Tivoli Business Service Manager (TBSM) Support Tip of the Week #2
Tivoli Business Service Manager Support Tip of the Week #3
I’m committed to sharing with you as much as possible about all things BSM and the broader BSM Value Proposition. I’ve added another SME Guest Author in January and introduced to you Robin Harwani. Robin’s hit the ground running and shared some of his BSM thoughts in his heavily read and commented first post BSM: Identity Crisis. Welcome to the blog Robin, we look forward to making BSM Magic! If you’re interested in sharing your views, thoughts, ideas via the blog, podcast or other means, leave comments!
I jumped on the bandwagon with the obligatory awards for 2008 and predictions for 2009 post. Take a look and let me know what yours would have been.
2008 BSM Winners and Losers; 2009 Predictions
Still trying to get Gary over at Nimsoft to share their views on BSM. Gary’s made comments a few times but 2009 should be their year to come into the BSM space. He did share a great new acronym for BSM – Bringing Sacks of Money or Bring Stacks of Money.
TBSM V4.x Posts
Tivoli Business Service Manager v4.1.1 IF 11 Available
Tivoli Business Service Manager v4.2 Interim Fix 1 Available
Looking ahead to February 2009
I’ll be at IBM Tivoli Pulse in Las Vegas February 6th-13th. Look for me in the BSM demo booths or in my session Monday at 5pm. Come get a BSM sticker from me and ask about the contest for a pocket HD video recorder.
Watch out for FireScope this month and their new product release. They’ve been awfully quiet since their launch last year. They’re back at it this month.
Got any other hot tips or news you want to break? What’s on your plates for February 2009? What are your BSM plans?
Need help on your IBM Tivoli BSM project? Need a BSM Strategy across your multi-vendor IT management environment? Planning on upgrading to the latest version of TBSM v4? Contact me to engage IBM Tivoli ISST for help!
Comments on this entry are closed.
Doug
You are correct…we are being somewhat “stealth-like” in our approach. It’s not that there is any great secret, but more that we feel that in general BSM has a terrible reputation and we want to make 110% sure of the value that we’re offering and have it proved by multiple customers before we go public.
I can tell you a couple of things though that we are hearing from customer/analysts:
#1 2009 is a horrible year for BSM vendors. Budgets under pressure and BSM still seen as a “nice to have” not a must have
#2 Most CIOs are still skeptical on whether BSM related products are really just marketing hype
#3 Customers want “out of the box” and don’t want to spend months to get value. True in any environment but particularly true in today’s economy.
So, for Nimsoft, please keep watching on http://www.nimsoft.com/blogs. We are active with multiple customers running our BSM offering but as I say, we’ll stay under the radar for a little longer.
Our core business is on fire!
@Gary: I would urge you to look at Service Assurance space which IMHO falls under Business Retention category. I have noticed business retention systems are in great demand in most organizations with the current economy.
We need a more general term for that, something that brings enterprise and service providers together. We’re all seeking the same things, we don’t need terminology or “standards” to get in the way of something good working in one environment versus another when it should just work anywhere. š
Doug