"With the mushrooming of the sheer number of moving parts in data centers, manual baton passing is just not going to cut it for this new world," says Kia Behnia.
Over the last decade, IT infrastructures have become exceedingly complex, resulting in a highly interconnected network of new and powerful technologies. In a world where IT budgets are shrinking and mergers and acquisitions are more and more common, how do you get the most value from your existing IT resources yet maintain agility?
In this Podcast, with Kia Behnia, Chief Corporate Architect at BMC, find out how service automation can help you navigate the”perfect storm” of new technologies such as server virtualization, as well as legacy distributed and mainframe computing environments that support millions of transactions through multi-tiered applications.
Discover the pain points that can lead a company toward service automation, and how you can benefit from not only from thinking tactically about holes that automation can plug, but also by looking at areas the enterprise that can get the biggest bang for the buck both in the near term and long term. Behnia talks about looking beyond the individual elements that currently exist in the data center or IT environment, and looking at the many ways that automation can help prevent critical human error in the highly interconnected environment. Finally, he outlines ways companies can get service automation right, and leaves us with a summary of the three most critical benefits of service automation.
Kia Behnia Chief Corporate Architect at BMC responsible for virtualization management. over the last 2.5 years he’s also be responsible for setting BMC’s service automation strategy and direction. Prior to joining BMC Software, he was CTO for Marimba, and earlier in his career he was one of the principal technologists for Tivoli Systems.
At BMC. Kia Behnia offers strategies to reduce the frequency and scope of IT failures, better support dependent business services and drive down operating costs with the right change and configuration management approach and technology.
- Are there any notable differences between data center automation and service automation? If so, what are the differences?
- In your paper, you say you should start with identifying pain points. Do you have any examples of extremely painful starting points you’ve seen?
- What types of holes might persist in an update and maintenance plan that you constantly have to “plug” with automation? Or is that too reactive of an approach?
- What sorts of environments lend themselves really well to service automation? In other words, what do you consider to be “low hanging fruit?
- What’s the number one thing an IT department can do to get automation right?
- Any other stories you want to tell today, and do you have any remaining important points to leave with our listeners?