|Cloud, Digital, SaaS, Enterprise 2.0, Enterprise Software, CIO, Social Media, Mobility, Trends, Markets, Thoughts, Technologies, Outsourcing|
Linkedin Facebook Twitter Google Profile
Sunday, June 12, 2005
Jeff brings home the point that many failed ERP implementations could be to a significant extent attributed to lack of involvement of the management in early stages of implementation – many realized the magnitude of work to be done only after the implementation was over and warns that more CIO's will lose their job over SOA implementations than lost their job over ERP implementations.Jeff adds that SOA implementation may call for greater efforts compared to ERP implementation and CIO’s could be making similar mistakes of not getting involved well early enough and elaborates, "SOA is a complete overhaul impacting how systems are analyzed, designed, built, integrated and managed. And not just some systems - all systems including packaged applications like ERP. SOA is first and foremost about a network of services. The value of an enterprise’s service network is directly related to the effort of creating/obtaining services and making them available. All networks require a critical mass of 'valuable services' before they become useful to the consumers. The SOA service network is no exception. While enterprises can take a slow and steady approach to SOA but would need to be prepared to receive gains that are even slower - this is really about the 'network effect'”. SOA done properly is a massive undertaking. It requires a rethinking of enterprises infrastructure, development methodology, business impact analysis, budgeting process, organizational design. Jeff concluded by cautioning against underestimating the value it provides, the competitive advantage enterprises may be bestowed with & the investment it will take!
Category : SOA |
|Sadagopan's Weblog on Emerging Technologies, Trends,Thoughts, Ideas & Cyberworld