Involvement of Service Knowledge Management System in Integration of ITIL V3 and Enterprise Architecture

Problem statement: This study attempts to investigate and clarify the relationship of Service Knowledge Management System (SKMS) with our primary study regard to using enterprise architecture through ITIL V3. Approach: SKMS concepts are introduced by ITIL V3 as a set of tools and databases that are used to manage knowledge and information of IT services. Results: The SKMS stores, retrieves, updates and presents all information that is expected for management of whole lifecycle of IT Services. Primary goal of our research is to provide a comprehensive integrated framework to determine and address IT Service Architecture requirements and related issues in ITIL V3 through using Enterprise Architecture. Conclusion/Recommendations: Through the main process of our study we realized that ITIL Knowledge Management process and its model for SKMS might be good candidates for storing and retrieving architectures of IT services. In other word, SKMS can be used as a set of tools and databases for management of architecture components of our target framework. For next step, the concern is how to develop proposed SKMS.


INTRODUCTION
IT Service Management (ITSM) was established based on modern international standards such as ISO/IEC 20000 and ITIL. There is a need for research that investigates the economic and social outcomes of ITSM as it relates to globalization of IT services and workforce (Galup et al., 2007). ITIL is an important and influential center of gravity in IT management (Betz, 2006). ITIL V2 has been introduced in mid 90s and it was only focused on Service Delivery and Service Support and IT providers realized that there is a lack in strategy and design of service in practice. In 2007, OGC has released ITIL V3 to cover whole lifecycle of service which included five volumes as five stages of service: Service strategy, Service Design, Service Transition, Service operation and Continual Service Improvement (OGC, 2007). These publications only provide general guidelines on IT Service Management, thus each volume should be adapted and designed in details to be used in practice.
Knowledge Management is provided as a new process in ITIL V3 and is introduced in Service Transition volume. In this publication, ITIL defines Knowledge Management as the one central process responsible for providing knowledge to all IT Service Management processes. Within IT Service Management, Knowledge Management and Service Knowledge Management System (SKMS) are concerned with service knowledge. Underpinning this knowledge will be a considerable quantity of data, which will be held in a central logical repository or Configuration Management System (CMS) and Configuration Management Database (CMDB) (ITIL V3, 2007).
Research background: Today service is a general concept in many academic and practical disciplines. Each domain defines service in one way. It seems that these different definitions and applications of service term might cause some confuse in academia and practice. For instance, both SOA and ITSM are Service based but SOA usually is used in application development domain while ITSM recommends a service based management system (Gu and Lago, 2009;Voss and Hsuan 2009). It seems variety of service could cause some ambiguity in Service Sciences (Bardhan et al., 2010). As a suggestion by a researchers, Service could be considered as gravity center for Service Oriented Architecture, IT Service Management and recently Service Oriented Enterprise Architecture (Assmann and Engels, 2008) but it needs to be conceptualized or redefined. In other words, to convergence these various frameworks and standards, a service-oriented integrated framework is required. Demirkan et al. (2008) in study titled 'Service-Oriented technology and management: Perspectives on research and practice for the coming decade' have discussed on different aspects of service-oriented disciplines and have finally concluded that one of major challenges and issues of service sciences and industries that should be taken up by researchers and universities is the integration of technological and social science, management and policy research based on service (Demirkan et al., 2008). They also encouraged computer science, IS and management researchers to respond to conduct and develop multi disciplinary research efforts to begin to address that issue (Zhao et al., 2009). Moreover, they recommended various research paradigms and methods can be leveraged to investigate the challenging managerial and technical problems in service-oriented systems. Furthermore, they notified new researchers can use quantitative, qualitative and experiment methods, case and field studies and design science approaches (Demirkan et al., 2008).

MATERIALS AND METHODS
Literature review, experiences of the authors and this demand have led us to the main question of study: "How to converge IT service standards and frameworks through service-oriented integration of ITSM, EA and SOA to provide a common discipline and framework for service in research domains of computing, information systems and IS/IT management?" Research objectives: The goal of this research is to develop a comprehensive integrated framework to identify and address IT Service Architecture requirements and issues through using Enterprise Architecture.
The research objectives that are defined based on this goal, research topic, problem statement and research questions are following: • To define the roles of ITSM/ITIL and EA in IS/IT service delivery • To identify architectural issues of IT Service Management. • To design IT Service Architecture for ITSM and ITIL • To develop a framework for integration of ITSM/ITIL and EA It infrastructure library v3: As mentioned already, the ITIL Core books consist of five publications.

Service Strategy:
The Service Strategy volume provides guidance on how to design, develop and implement service management. This guidance is provided on the principles covering the practice of service management that are useful for developing service management policies, guidelines and processes across the ITIL Service Lifecycle (Steinberg and Yearsley, 2007).

Service Design:
The Service Design publication provides guidance on how to design and develop both services and service management processes. It also covers design principles and methods for converting strategic objectives into portfolios of services and service assets (ITIL V3, 2007).

Service Transition:
The Service Transition volume provides guidance for development and improvement of capabilities for transitioning new and changed services into operations. This publication provides guidance on how the requirements of Service Strategy encoded in Service Design are effectively realized in Service Operation (Steinberg and Yearsley, 2007).

Service Operation:
This volume embodies practices in the management of service operations. It includes guidance on achieving effectiveness and efficiency in the delivery and support of services so that to ensure value for the customer and the service provider(Office of Government Commerce, 2007).

Continual Service Improvement:
This volume provides instrumental guidance in creating and maintaining value for customers through better design, introduction and operation of services. It combines principles, practices and methods from quality management, change management and capability improvement (Office of Government Commerce, 2007).
In Table 1 we summarized five stages (volumes) and all related process which each volume introduced for service lifecycle. The most important point hereby is that although each process is introduced in one stage, many of them are not limited to only one stage. For example process numbered c.7 as knowledge management affects on all stages except service strategy.
Service Design(SD) phase , as second phase of IT Service lifecycle in ITIL V3, all aspects of service design including: new or changed service solutions, service management systems and tools, technology architectures and management, systems processes, roles and capabilities, measurement methods and metrics should be considered (ITIL V3, 2007). One of these aspects is technology architecture of service which could be considered as the requirements of service architecture. Service architecture attempts to integrate all information related to service. This information must involve applications, information, data and infrastructures for any IT service. These architectures are called Enterprise Architecture (ITIL V3, 2007). Enterprise Architecture usually modeled as four architecture layers including business architecture, information architecture, application architecture and infrastructure architecture (Goikoetxea, 2007;Winter and Fischer, 2007;Aier et al., 2008;NIST, 2009) but not included service layer.
Service knowledge management process: The term knowledge is apparently consisting of data, information, intelligence, skill, experience, expertise, ideas, intuition, or insight in the context in which it is used. As often been mentioned, knowledge can be categorised into two types, which are Explicit Knowledge (EK) and Tacit Knowledge. EK is the knowledge that can be shared with others that can be documented, categorized transmitted to others (Tan, 2011).

RESULTS AND DISCUSSION
Knowledge management is defined as a systematic and integrative process of coordinating organizationwide activities of acquiring, creating, storing, sharing, diffusing, developing and deploying knowledge by individuals and groups in pursuit of major organizational goals (Stevens et al., 2010). Knowledge management is concerned with recognizing and managing all the organization's intellectual assets (which include knowledge, information and data) to meet business objectives (Fatt and Khin, 2010).
As mentioned above, Knowledge Management process is introduced through Service Transition volume of ITIL V3. The goal of Knowledge Management process in ITIL V3 is to enable organizations to improve the quality of management decision making by ensuring that reliable and secure information and data is available throughout the service lifecycle (ITIL V3, 2007). Knowledge Management is especially significant within Service Lifecycle since relevant and appropriate knowledge is one of the key service elements being used. During the service lifecycle an organization needs to focus on retrieving, sharing and utilizing their knowledge through problem solving, dynamic learning, strategic planning and decision making. To achieve this, knowledge needs to be transferred to other parts of the organization at specific points in the lifecycle. ITIL states that effective knowledge management is a powerful asset for people in all roles across all stages of the service lifecycle. It is an excellent method for individuals and teams to share data, information and knowledge about all facets of an IT service.
KMS is an IT system which is used to support and to strengthen the process of knowledge creation, access, transfer and usage. Knowledge management regards knowledge sharing as the core objective. Only through exchanges, can develop knowledge; only through the using of knowledge, can new knowledge be derived from the existed knowledge (Deng and Hu, 2007).
As Fig. 1 illustrated, Within IT Service Management, Knowledge Management could be formed within the Service Knowledge Management System (SKMS). Underpinning this knowledge will be a considerable quantity of data, which will be held in a central logical repository or Configuration Management System (CMS) and Configuration Management Database (CMDB). SKMS for service architecture: As mentioned in section two, IITL defines its Service Knowledge Management System (SKMS) as following: "A set of tools and databases that are used to manage knowledge and information. The SKMS includes System Configuration Management System, as well as other tools and databases. The SKMS stores, manages, updates and presents all information that an IT Service provider needs to manage the full Lifecycle of IT Services." (ITIL V3, 2007). In order to make effective use of data, in terms of delivering the required knowledge, an information architecture matched to the organizational situation and the knowledge requirements is essential(ITIL V3, 2007): • Creating and regularly updating a Service Management information model • Defining systems that optimize the use of the information while maintaining data and information integrity • Adopting data classification schemes that are in use across the organization When the requirements and architecture have been set up, data and information management to support Knowledge Management can be established. The key steps required involve setting up mechanisms to (ITIL V3, 2007): • Identify the service lifecycle data and information to be collected • Define the procedure required to maintain the data and information and make it available to those requiring it • Store and retrieve • Establish authority and responsibility for all required items of information • Define and publicize rights, obligations and commitments regarding the retention of, transmission of and access to information and data items based on applicable requirements and protecting its security, integrity and consistency • Identify the requirements to review, in the light of changing technology, organizational requirements, evolving policy and legislation • Deal with collection and retention requirements A service provider must first establish a service knowledge management system that can be shared, updated and used by its operating entities, partners and customers. Implementation of a service knowledge management system helps reduce the costs of maintaining and managing the services, both by increasing the efficiency of operational management procedures and by reducing the risks that arise from the lack of proper mechanisms.
Related literatures grouped the models of KMS into four types, which are knowledge type model, process management model, hierarchical model and knowledge chain model. A hierarchical service model can represent KMS architecture. From the perspective of service model, the framework of KMS can be divided into four levels or four layers. They are knowledge units, knowledge processing, knowledge storage and knowledge sharing (Deng and Hu, 2007). ITIL suggests a four layer hierarchical model for SKMS including presentation layer, knowledge processing layer, Information integration layer and data and information sources and tools.
In ITIL V3, asset is defined as 'Any Resource or Capability'. Assets of a service provider including following types: Management, Organization, Process, Knowledge, People, Information, Applications, Infrastructure and Financial Capital, provided that could contribute to the delivery of a Service (Steinberg and Yearsley, 2007).
On the other hand, in the definition of Knowledge asset, ITIL states that 'Knowledge assets are accumulations of awareness, experience, information, insight and intellectual property that are associated with actions and context. Management, organization, process and applications assets use and store knowledge assets. People assets store tacit knowledge in the form of experience, skills and talent. Such knowledge is primarily acquired through experience, observation and training. Movement of teams and individuals is an effective way to transfer tacit knowledge within and across organizations. Knowledge assets in tacit form are hard for rivals to replicate but easy for owners to lose. Organizations seek to protect themselves from loss by codifying tacit knowledge into explicit forms such as knowledge embedded in process, applications and infrastructure assets.
Finally, ITIL in Service Transition volume clarifies that Knowledge assets include policies, plans, designs, configurations, architectures, process definitions, analytical methods, service definitions, analyses, reports and surveys.
To conclude, as mentioned in previous sections regard to integration of ITIL and EA, the main concern of the authors is the architectures of IT services, which could be considered as one of knowledge assets of IT providers. By refer to SKMS definition it is obvious that SKMS could be considered as a set of tools and databases for storing and retrieving IT service architectures. Therefore to provide a tool for target framework of the research, researchers will concentrate to design and develop a Service Knowledge Management System to support proposed target framework.

CONCLUSION
In this study, firstly ITIL V3 and its stages and processes were introduced briefly. Then some primary issues regard to main research has been mentioned. The main goal of researchers has stated as development of a comprehensive integrated framework to identify and address IT Service Architecture requirements and issues through using Enterprise Architecture". We called this framework in our study as Integrated Service Architecture Framework (ISAF).
The research question related to this study is "How to fulfill architectural requirements of ITSM/ITIL by using Enterprise Architecture?" Also the research objectives which have led authors for analyzing service knowledge management system were the following: • To design IT Service Architecture for ITSM and ITIL • To develop a framework for integration of ITSM/ITIL and EA We mentioned that special process as Knowledge Management is introduced in Service Transition volume of ITIL V3. The goal of this process in ITIL V3 is to enable organizations to improve the quality of management decision making by ensuring that reliable and secure information and data is available throughout the service lifecycle. Service Knowledge Management System (SKMS) is referred by ITIL V3 as a set of tools and databases that are used to manage knowledge and information.
The SKMS stores, manages, updates and presents all information that an IT Service provider needs to manage the full Lifecycle of IT Services. As we discovered in IT Service Management, knowledge assets includes policies, plans, designs, configurations, architectures, process definitions, analytical methods, service definitions, analyses, reports and surveys.
Through this study, we realized that regard to our main research problem, architectures of IT services can be stored and retrieved by SKMS. In other word, SKMS could be involved in study process as a set of tools and databases for storing and retrieving IT service architectures. Therefore researchers could plan to provide an automated tool for target framework through design and development of a Service Knowledge Management System.