Empower your teams to innovate -- SOA drives better business flexibility. SOA Governance drives better business results.

Realizing the benefits

The following challenges illustrate how effective SOA Governance can enable organizations to realize the benefits of SOA.



Establishing decision rights for your SOA environment

Let's look at a large insurance company with multiple Lines of Business (LOBs), such as home, life and auto insurance, each working with the customer separately. The company wants to implement a common customer service process – a one-stop shopping experience for the customer to fulfill all of their home, life, auto and other insurance needs.

Effective SOA Governance can help answer the following:

Defining appropriate services

Let's look at a large bank expanding into new geographies with differing regulatory requirements. An SOA allows shared reusable business services to be bundled or unbundled as required to enable compliance in each geographical area.

Effective SOA Governance can help answer the following:

Managing the life cycle of service assets

Let's look at a large retailer who is facing increasing competition to its online and catalog sales channels. To increase customer satisfaction, they want to institute a new billing policy within their existing SOA environment. However, the development team finds it hard to identify which applications and services are impacted by the new billing policy. But facing a deadline, changes are made to known areas and put into production. Unfortunately, another LOB was using the previous version causing outages, customer complaints and revenue loss.

Although the company had an SOA environment, they had not instituted a way to manage changes and determine who was using the shared services.

Effective SOA Governance can help answer the following:

SOA Governance requirements:

Company capabilities needed to support the requirements:

Measuring effectiveness

Let's look at a large telecommunications who embraced an SOA strategy in order to improve staff productivity and lower costs. The Commercial division development team made existing functionality available as services.

Difficulties appeared when the Residential division launched a heavily used new offering which used one of the Commercial division's services. The increased usage slowed response times for every application using the service. It also increased the Commercial division's costs.

Unfortunately, a Service Level Agreement (SLA) had not been implemented, which would have generated a plan to handle the additional workload. In addition since appropriate monitoring tools were never deployed, the Commercial division was unable to charge any other division for the service usage.

SOA Governance requirements:

Company capabilities needed to support the requirements: