We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Business Transformation in Action

Joe McKendrick

Services by the Business, for the Business, and of the Business

user-pic
Vote 0 Votes

For some companies, the structure of the US government provides a good model for governing service oriented architecture.

I recently had the opportunity to chat with Vladimir Mitevski, vice president product management core services at Thomson Reuters, about his company's approach to service oriented architecture governance.

In many SOA projects, IT takes the lead role. For Mitevski's operation, IT takes a back seat. If a service succeeds or fails, it's up to the business owner, he says.  "We have three types of roles," he explains.  "There are service publishers, QA approvers, and the business owners. If you think of the US government, you have the checks and balances between the House, Senate, and the president, and everyone can override each other at the end of the day.  This is the same concept We adopted." Governance of all services is managed through an HP Systinet registry, which tracks ownership and service status.

Thomson Reuters is a provider of business intelligence information for businesses and professionals, which maintains a stable of 4,000 services that it makes available to outside customers. For example, one such service, Thomson ONE Analytics, delivers a broad and deep range of financial content to Thomson Reuters clientele. All services are consumed by external Thomson Reuters customers -- truly an example of SOA supporting the cloud.

As services are approved and moved to the company's central registry, the workflow is overseen and managed by business owners, who bear full responsibility for the service -- even to the point where they are responsible for provisioning enough processing power to keep it up and running. 'Business owner, are responsible for testing, validating, and assuring that the service is working," Mitevski says. "Which means when you press the button, there are no excuses."

Once a service is published and approved by QA, it is automatically moved into the registry. "There are two steps," he explains. "Whoever actually owns the revenue for that particular artifact is the one who who gives the green light, and just goes in and presses the button. They can either log into the tool, or they get an automatically generated email from the system. They click on the email 'approved,' and approve the articfact and move to production."

In this blog (formerly known as "SOA in Action"), Joe McKendrick examines how BPM and related business and IT approaches can promote business transformation.

Joe McKendrick

Joe McKendrick is an author and independent analyst who tracks the impact of information technology on management and markets. View more

Subscribe



Subscribe in Bloglines
Subscribe in NewsGator Online
Add ebizQ's SOA in Action Blog to Newsburst from CNET News.com
Add to Google

Recently Commented On

Monthly Archives

Blogs

ADVERTISEMENT