IT leaders who continue operating with "the status quo" risk irrelevance

Guest post by Joshua Brusse, Chief Architect, Asia Pacific and Japan, HP Software Professional Services

 

The bulk of my time with clients is spent helping them transform their IT organizations into ones that are ready for the future. You can blame the shifting IT landscape on the consumerization of IT or on the cloud, but what’s really happening is the democratization of IT. Quite simply, IT doesn’t hold the keys to the kingdom anymore, because businesses can go anywhere to buy IT services.

This leads to an urgent problem for traditional IT. Information services are absolutely necessary. But who will deliver them?

 

bowtie image.pngThink of this as analogous to the restaurant business. The need for food will never go away – it’s integral to survival. But if you as a restaurant will not provide the right food, your customers will go elsewhere. In the same way, there’s no company in the world that can survive without information services. But the worst-case scenario is that you close your IT shop because the business is buying information services somewhere else.

 

IT leaders who don’t see this and continue with the status quo are risking irrelevance, or worse. But for IT leaders who are thinking about transforming their organizations for the future, it’s essential to develop a hybrid delivery operating model and thus a Service Integration And Management (SIAM) strategy.

 

What is service integration and management?

 

If you look at how businesses are run, they have a business model (with business processes) and an ERP (like SAP) that automates those processes and that model. SIAM takes the same framework and applies it to IT so that you can run IT as a business. A SIAM strategy has two key ingredients:

 

1. A business model for IT: Develop this by asking these questions: How do I model my IT? What are the processes and competencies that I need? What are the operating models that I need? What are the organizational structures and the functions? What are the roles and responsibilities? You can also use your model to build a capability matrix so that as you do service planning you can look at potential suppliers and what they can do.

 

2. An ERP for IT: Just as SAP, for example, automates, measures and dashboards business processes, so too should your ERP. (At HP we’ve developed our HP IT Performance Suite to fill this role.)

 

Essentially, you have your business architecture and you support that business architecture with a technology layer. This layer is composed of a set of products that can measure how you manage as well as automate many of the processes in your business model. The technology layer allows you to integrate with your suppliers so that you can have everything in one dashboard and manage everything from one “control centre”.

 

SIAM is common sense

 

It may be new for IT to think this way, but these are not new ideas. It’s really about applying common sense practices to an IT organization.

 

Other industries are already doing this—manufacturing is a great example. If you walk into a Toyota factory, you see they do SIAM; they’ve been doing this for 50 years. They bring all the different components together and build a car, but they’re not building the different components. They have an extremely well-managed supplier network along with orchestration and workforce planning and governance. What we’re doing now with service integration and management is simply applying these concepts to IT.

 

A solution for hybrid delivery

 

Service integration and management is absolutely key if you are moving to a hybrid delivery model. If you’re a CIO getting into hybrid cloud, there are three things you need to think about:

 

  • Governance: How do you maintain governance in a multi-sourced environment? Even if you’re outsourcing services, you absolutely do not want to outsource your governance. But, considering that some IT organizations don’t even have a solid governance practice in place, this piece can be challenging especially if you’re dealing with hybrid delivery at the same time. Developing a service integration and management strategy forces you to address governance issues.

 

  • Supplier management: Hybrid delivery is only going to be beneficial if it is possible to choose the right supplier quickly. You also need the ability to swap to another one quickly when the current supplier isn’t meeting your needs. Questions to ask include: How do I enable an operating model that allows me to do this? How do I maintain a capability model to pick and choose and to quickly onboard potential suppliers? How do I dashboard and track performance once they are operational? SIAM helps with all of this.

 

  • Orchestration: Ask yourself: How do I bring together the best group of suppliers, both internal and external, so that the business experiences a seamless delivery of services? If you’re not able to integrate and centrally manage all the partners that deliver the service to the business, you’re simply creating more silos.

A SIAM strategy helps you answer these questions, providing an effective solution for hybrid delivery. 

To learn more about HP’s approach to service integration and management visit www.hp.com/go/siam.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
This account is for guest bloggers. The blog post will identify the blogger.
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.