A Bright SOA IDEA: The Road Map for Service-Oriented Success
Implementing SOA without a roadmap and a guide almost certainly means disaster
By: Brian Erickson
Jan. 18, 2008 10:30 AM
This desire for greater flexibility and effectiveness motivated one of the best companies in the United States to undertake a major SOA initiative. In many ways, the difficulties this defense and technology contractor giant faced with respect to the efficient integration of new acquisitions and their associated systems are typical of the issues that drive businesses to institute SOA initiatives on a broader level. Specifically, the rapidly growing contractor was challenged with human resource benefits document version control. The company wanted to construct a single document repository and a set of common services to synchronize documents.
The result of the SOA effort was a single reliable source for human resource benefits information. Having one standard data source made it possible for the organization to speed time-to-market for new HR offerings. This initiative also produced new standards across business units, which led to lower litigation costs.
Enablement - Driving Progress
A major Japanese automobile manufacturer's story provides a good example. This company has successfully risen through the ranks to dominate sales worldwide; yet its expansion didn't come without some serious challenges. Like other businesses that have gone through major expansions, the company struggled with growing pains.
One challenge was understanding who its customers were and providing a consistent view of those customers throughout the organization. At a tactical level, this company had 30 different data stores of customer information. Audits found the data was less than 70% accurate. As a result, the company was pouring money into marketing and advertising initiatives based on data that was only 30% accurate.
An application was created that effectively provided a 360-degree view of customer information. The application provided accurate data that helped the company speed time-to-market and create more effective marketing initiatives. As a result, it lowered the costs associated with customer data services. After implementing the project, the company stopped buying customer data from external sources because the quality of its internal data was now better than what they could buy, saving the company millions of dollars. These solutions were delivered by creating an SOA that maintained one view of the customer.
Agility - A Force in Motion
As appealing as this sounds, most SOA initiatives are still relatively immature, so no company can really claim to have reached this implementation level. However, having these phases as reference points helps businesses gauge where they are to determine if they're on track or simply spinning their wheels by remaining too tactically focused.
So what would a business that reaches the Agility phase look like? For starters, it would rely on reusable services and composite applications. It would also have SOA throughout the enterprise to provide real-time business services, runtime governance, and process coordination. A company that reached the Agility phase would also have virtualized and federated resource management.
But to reach the Agility SOA maturity phase, an organization has to transform itself into a truly flexible business, rapidly responding and reacting to changes in demand and market conditions through technology. And the company would have to be able to extend the developed solutions beyond its four walls. With respect to technology, an organization would have to create effective real-time processing loops.
While no business has yet to progress through all the phases of SOA adoption to reach this level of maturity, once a business does, it will be in a position to compete more effectively against market rivals. At this point, a company might need a consulting partner to provide cross-enterprise SOA solutions to help it create a truly expansive enterprise.
Components of Change
Because SOA adoption impacts so many different aspects of a company, timing is crucial when it comes to focusing on the right issues at the right times to create smooth transitions and guarantee the organization progresses through all phases of the maturity model. Naturally, some components take on more importance in certain phases than in others. For example, during the SOA initiation phase, an organization is probably not going to focus much on governance, but concentrate instead more on data or applications. However, organizations won't be successful with SOA initiatives unless key aspects of each component are addressed at every level of the maturity model.
It's worth noting that as complex as each component can be, perhaps the most volatile - and certainly the most vital - is the human element.
A Map of the New World
SOA adoption is a complex multi-stage process requiring a good deal of thought and preparation at each phase. No organization should enter on the path without having a clear roadmap that provides critical markers that business and IT executives can use to chart the progress of their SOA implementation. This roadmap will give companies guidance on the best routes they need to take to reach their destination and help avoid the pitfalls and traps that lay ahead.
But before launching a new journey, businesses first need to understand where they are and where they want to go. Only then can they map a clear path that will take them through the process of creating a sturdy foundation for progress and ultimately corporate excellence that will help them stand out in an increasingly competitive world market.
About Hitachi Consulting
Reader Feedback: Page 1 of 1
SOA World Latest Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week