i personally realized through my past assignments implementing Enterprise Services Architecture shifts the focus of an organization from functional/application centric to a process/integration centric. Enterprise services are modeled after business events and that business process and user interaction to a large extent are based on these enterprise services putting them at the heart of integration and development efforts.I personally felt that it is a concurrent engineering we are aiming at because it includes or perhaps i will add circumscribe Enterprise Level commitments,Project level value add,architecture approach model driven or pattern based,and an ESA department .The adoption itself took lot out of me as from mangement perspective you need to keep an absolute focus on communication,planning,training,performance management and role modelling.One needs to bring in business, application and technology perspective of adoption to a common platform .So just sharing my thoughts derived from experiences which may add to certain variation in perspective of looking at ESA as organization has to manage a radical change not only in technology but also in people and there mindset towards change
Organizational roles supporting these enterprise services are:
Enterprise Services Architect
Skills:
a) Good understanding of business processes.
b) Ability for formulation of process and service models
c) Excellent IT Architecture concepts
Responsibility:
a) Working with business to identify the most important business events to be supported by enterprise services.
b) Decides on the appropriate sets of services and needed to support business scenarios and on granularity and interfaces of these activities.
c) Defining the enterprise data standards that will allow integration across heterogeneous systems.
Enterprise Services Developer
Skills:
a) Using the tools of an integration platform such as SAP NetWeaver.
b) Excellent understanding of application.
Responsibility:
a) Implements the enterprise services.
b) Creates all integration logic.
Interaction Component Developer
Skills:
a) WEB Page Development highly graphic and interactive tools such as SAP WebDynpro and specifically UI development tools.
Responsibility:
Development of new user interface components everything from fairly simple UI components to complete composite application.
Enterprise Services Architecture Role MAP: Depending upon the skills and responsibility role map may be framed as follows:
ESA adoption in an organization is very critical to its business as it outlines:
a) The future architecture and system landscape.
b) List of potential projects that will take company's investment and in turn may lead to return on investment in the forms of lessons learned, productive use of integration concepts and technology.
c) It equates operational efficiency with informational complexities.
d) Impacts an organization by encompassing all systems both SAP and NON-SAP relevant to a
o Business process in the value chain,
o Manages all information for business processes,
o Empowers all people participating in a business processes both for internal and external delivery.
The futuristic vision of ESA is not only to build enterprise services based on web services and addressing business processes but to built an organization wide Enterprise Services Driven Business processes appealing to large scale adoption as enabler of change.
Methodology For Moving towards general adoption and new integration practices and technology
Internal Sale Leads to starting of general adoption as soon as organisation sees potential benefits.
This blog illustrated some of the aspects of adoption of ESA for an organisation . Still Maturity level of ESA depend upon the participation of key stakeholders and awareness of business owners who wants to reap benefits of it.
