Proposal for the Identiﬁcation of Information Technology Services in Public Organizations

: Handling complexity and symmetry in the identiﬁcation of services for the management of information technology (IT) emerged as a serious challenge in recent times. One of the most important elements that must be deﬁned in the management of information technology services is the construction and management of a service catalog. However, in order to create this catalog, it is necessary to correctly identify the services to be formed. So far, there are several proposals that serve to identify information technology services in public organizations. However, there are several inherent drawbacks to these processes, whereby many organizations are yet to adapt to the services. The main objective of this research is to present a proposal for the identiﬁcation of information technology services and the construction of an information technology catalog. For this, the following methodology was applied: (a) a review of the literature, identifying the research that addressed the process of the identiﬁcation of services; (b) a proposal based on automatic learning to identify information technology services in public organizations, adapting the catalog of services and taking as its main input the history of requests and incidents accredited by the department of information technologies in public organizations in the Republic of Ecuador. In conclusion, this work leads to satisfactory results for the identiﬁcation of technology services used to construct its catalog.


Introduction
As the importance of information technology (IT) increases, the requirements placed on IT service (ITS) providers by ITS seekers are changing.In order to meet these requirements, many methods and approaches are being discussed and studied in science and in practice.Indeed, issues such as the orientation of ITS, the management of ITS (ITSM), and the industrialization of IT gained importance in recent years [1].
An ITS can be defined as a package of services provided by an IT system or the IT department to support business processes [2].An ITS covers the development, customization, and operation of IT applications, as well as the IT infrastructure.In addition, an ITS must correspond to the needs of the clients and provide them with a benefit they can perceive [3].This last criterion was reaffirmed by Simonova and Foltanova [4], who stated that the requirements of the users must be essential inputs for the development of services, as the initial identification of these requirements is essential.
In service engineering, the identification of services plays a fundamental role since this identification establishes the basis for subsequent processes [5].Then, if the services are poorly identified, these subsequent processes are negatively influenced [6].Although there are several techniques that identify Symmetry 2019, 11, 1269 2 of 32 each service [7], none of them are conventional or standard.Some techniques were not tested, while others are extremely difficult to execute, and some of them are not linked with the organization.According to Huego et al. [8], during the last few decades, several methods for the identification of services (SIM) were suggested.However, there is no consensus on the "best method" or a predominant approach to identify these services.
The identification of ITS is an inescapable process for the construction of an ITS catalog (ITSC).Indeed, Meister and Jetschni [9] affirmed that one of the first recommended steps toward service orientation is the implementation of an ITSC, even affirming that the ITSC is the cornerstone in the definition of IT business needs [10].An ITSC can be defined as a subset of the ITS portfolio (ITSP) that includes the services offered to clients, whether internal or external.This requires that the services listed in the ITSC be standardized so that they can be offered to different clients [11].Therefore, the ITSC is an ideal entry point when it comes to developing rich content and offering a functional capacity based on the portfolio strategy [12].
Frey et al. [13] affirmed that, in some projects, the process of identification is developed intuitively when it is based on the individual experiences of the people involved, without a defined or heuristic method [14].For example, Kalia et al. [15] showed that the automation of services improves the efficiency of ITSM processes, despite the fact that these authors proposed an automatic method based on requests.This process allows users to specify their requests for sentence changes in natural language and recommends the most appropriate options within the ITSC.Therefore, when the management of services is developed, it is not used for the construction of the ITSC.Another investigation that works with natural language is the one carried out by Rosa et al. [16], which took a set of registered incidents to add services and categories to the ITSC, without this process being automatic.According to what was proposed, there is no proposal that takes as its input both requests for change and the registration of organization incidents for the identification of ITS or for the construction of the ITSC.
The main objective of this research is to present a proposal for the identification of ITS and the construction of an ITS catalog.
As a research methodology, three fundamental tasks were considered: Task 1.A systematic review of the literature that allowed the identification of 30 studies related to the process of identifying ITS.Task 2. A proposal for the identification of ITS and the construction of the ITSC, which takes as its main input the history of requests and incidents of the four organizations so that services can be identified through the use of machine learning, thus building the ITSC automatically.
Task 3. A case study applied to a public organization in the Republic of Ecuador, which was used to implement the proposal and obtain the necessary results to analyze its efficiency levels.
Through the tasks outlined above, we tried to find a technological solution that allows the identification of the ITS and the construction of an ITSC automatically for public organizations (since, according to the literature review carried out in this research, there were few SIMs tested for this type of organization) by applying machine learning, and using as the main input the change requests and the incidents provided by the IT users registered by the IT department or area of a public organization, so that these processes are more precise and based on the real needs of the organization's IT users.
This paper is structured as follows: Section 2 shows the conceptual framework, explaining the ITSP, the ITSC (including the process of identifying services and the management of the ITSC), and the management of IT demand.Section 3 shows the methodology that includes the guidelines used to review the literature, the framework of the proposal, and the considerations that serve to develop the case study.Section 4 details the results of the literature review.Firstly, the background of the investigation is exposed.Then, the list of selected articles inherent in the process of identification of services and construction of the ITSC is chronologically detailed.Finally, we provide an analysis of the studies found, which is the basis for the development of the proposal detailed in this document.Section 5 shows the structure of the proposal, explaining in detail the corresponding phases.Section 6 details the results of the application of the proposal in the case study, which in this case was a public Symmetry 2019, 11, 1269 3 of 32 institution in the province of Manabí, Republic of Ecuador.A discussion about the results obtained is also shown.Finally, we detail the conclusions.

The Portfolio of ITS
The service portfolio is the complete set of services managed by a service provider and represents the commitments and investments of the service provider for all customers and market spaces.The portfolio also represents current contractual commitments, the development of new services, and the continuous service improvement plans initiated by the continuous improvement of the service [17].The ITSP contains an ITSC and financial planning to execute the services offered by an organization.The service portfolio management (which includes the service catalog) and financial management (FM) of the ITS are included in the service strategy phase.Detailed information on the ITSC is also included in the ITSC management process (ITSCM) that is included in the service design phase [18].
The portfolio management process at a general level is defined as a dynamic decision-making process to evaluate, select, request adaptation or approval, or cancel the versions and variety of products and services [19].The characteristics of the services contained in the portfolio may include the functionality of individual software components, as well as packages of software components, infrastructural elements, and additional services.Additional services are usually information services, consulting services, training services, problem-solving services, or update services [2].One of the fundamental components of the ITSP is the ITSC, which is defined below.

The ITS Catalog
The ITSC (consisting of two words: service and catalog [20]) is a structure that contains the list of ITSs offered by IT departments to provide direct assistance to other departments of the organization [21].Figure 1 shows part of a standard technical ITSC, which can be considered an ITS reference catalog (ITSRC).This catalog consists of categories at the top, and each category groups a list of the possible ITSs in a given organization.In other words, the catalog services are logically grouped according to activity, giving rise to a defined set of services that the IT department provides to a business [10].
Symmetry 2019, 11, x FOR PEER REVIEW 3 of 32 institution in the province of Manabí, Republic of Ecuador.A discussion about the results obtained is also shown.Finally, we detail the conclusions.

The Portfolio of ITS
The service portfolio is the complete set of services managed by a service provider and represents the commitments and investments of the service provider for all customers and market spaces.The portfolio also represents current contractual commitments, the development of new services, and the continuous service improvement plans initiated by the continuous improvement of the service [17].The ITSP contains an ITSC and financial planning to execute the services offered by an organization.The service portfolio management (which includes the service catalog) and financial management (FM) of the ITS are included in the service strategy phase.Detailed information on the ITSC is also included in the ITSC management process (ITSCM) that is included in the service design phase [18].
The portfolio management process at a general level is defined as a dynamic decision-making process to evaluate, select, request adaptation or approval, or cancel the versions and variety of products and services [19].The characteristics of the services contained in the portfolio may include the functionality of individual software components, as well as packages of software components, infrastructural elements, and additional services.Additional services are usually information services, consulting services, training services, problem-solving services, or update services [2].One of the fundamental components of the ITSP is the ITSC, which is defined below.

The ITS Catalog
The ITSC (consisting of two words: service and catalog [20]) is a structure that contains the list of ITSs offered by IT departments to provide direct assistance to other departments of the organization [21].Figure 1 shows part of a standard technical ITSC, which can be considered an ITS reference catalog (ITSRC).This catalog consists of categories at the top, and each category groups a list of the possible ITSs in a given organization.In other words, the catalog services are logically grouped according to activity, giving rise to a defined set of services that the IT department provides to a business [10].An ITSC presents an ITS that can be provided and supports customers/users.This influences the decisions that customers make regarding the IT help they require.The purpose of the ITSCM process is to ensure that this catalog is produced and maintained and that it contains accurate information on all operational services and those that are prepared to operate in an operational manner.Therefore, it is necessary to define the services and produce and maintain an accurate ITSC [18].One of the most important processes for the construction of the ITSC is the identification of ITSs.This process is explained below.An ITSC presents an ITS that can be provided and supports customers/users.This influences the decisions that customers make regarding the IT help they require.The purpose of the ITSCM process is to ensure that this catalog is produced and maintained and that it contains accurate information on all operational services and those that are prepared to operate in an operational manner.Therefore, it is necessary to define the services and produce and maintain an accurate ITSC [18].One of the most important processes for the construction of the ITSC is the identification of ITSs.This process is explained below.

The Process of Identifying ITSs
As mentioned above, in service engineering, the identification of services plays a fundamental role, since it establishes the basis for subsequent processes [5].A study by Souza et al. [22] showed that the methods of analysis and the design of services aim to identify services and organize them into a manageable hierarchy of compound services to support the processes carried out by a company.These methods use different service identification techniques, which go from the top down (decomposition of the problem until the service level (SL) is reached), or downward (the composition of services in more general parts, to develop business processes) [23].
An important method for the identification of services was proposed by Lee et al. [24].The methodology for the identification of services proposed contains four levels or stages: the level of business, the SL, the level of interaction, and the level of convergence.

•
Business level: The objective of this level is to identify the final purpose of the system.At this level, it is assumed that the business requirements are given by an organization or a person who plays the role of business analyst.

•
Service level: This level aims to identify the services that a system must provide an organization to meet the business requirements.

•
Level of interaction: The level of interaction addresses the interactions between the system and its external entities, such as users and other systems.These interactions are necessary to achieve the services assigned to the system in the SL.

•
Level of convergence: This level focuses on integrating the necessary technologies to provide the services that create a good "customer experience".By integrating several technologies, they can add additional requirements that must be addressed from the point of view of the joint creation of values.
The process of identifying services can be varied.Even natural language was already used as a basis to perform this task.Indeed, the process of identifying ITS can use both the requests (text) of users (as stated by Kalia et al. [15]) and the incidents (text) that may arise during the development of the ITSM (as stated by Rosa et al. [16]) as inputs.However, both inputs are yet to be used together to build an ITSC automatically.

The Management of the ITSC
Often, ITSCs are established within ITSM tools that include two views of the ITSC [21]: technical and business.For identification of the services that the IT area offers to its internal and external clients, a review of elements of the base infrastructure must be carried out.Based on subsequent revisions, an ITSC is built [25].To start applying the ITSCM, organizations must begin with service identification, an activity that most organizations do not perform correctly.There are several types of information that should be included for all ITSs within an organization in the ITSC.This information includes service description, service type, policy, and service level agreement (SLA) [16].Clients can use the ITSC to understand what service providers can do for them and to interact with the service provider to discuss those services.Users or individual consumers of a service can use the ITSC to understand the scope of the services available and to learn how to make service requests and/or report incidents associated with the services provided [17].The ITSCM process is responsible for directing all catalog information and ensuring that the data are correct and up to date.Therefore, it is responsible for activities like defining, standardizing, refreshing, publishing, communicating, protecting, and ensuring the quality of an ITSC [21].
The activities for the identification of ITSs and the construction of the ITSC can be carried out automatically and precisely, including novel principles like text mining and machine learning, which offer improvements that could lead to the optimization of resources, which is precisely what is proposed in this paper.

IT Demand Management
Within an organization, whether public or private, it is necessary that the IT department properly manages the various requirements of their internal clients.This range of requests based on IT requirements is part of the "IT demand management".According to Legner and Löhe [26], organizations convert their IT demands into IT solutions through multiple steps as follows:

•
Collection and detention; • Evaluation, prioritization, and planning; • Specification and realization; • Deployment and operation.
For Aguilar et al. [27], the importance of demand management lies in the achievement of benefits for the company, and, to achieve them, it is necessary that they take into account the life cycle of business demand.Therefore, the demand for IT products and services comes from the needs of the different business processes of the clients.These processes can be in the form of ideas, new well-founded business opportunities, delivery dates, costs, and benefits [28], because the demand for IT is very broad.These processes are classified differently in different IT portfolios so they can be managed in an appropriate way.One of these portfolios is the ITSP, as explained above.

Guidelines for the Systematic Review of Literature
For the development of the systematic review of the literature in this investigation, we followed the guidelines set forth by Kitchenham and Charters [29], who determined three phases that must be followed:

•
Review planning: In this phase, the review process is planned.Here, the research questions, search chains, inclusion and exclusion criteria, consultation sources, and the review protocol must be considered.

•
Carrying out the review: In this phase, the process is developed, following the guidelines outlined in the planning phase.Primary studies are selected here in a methodical manner.

•
Results of the review: In this phase, the results and analysis of the studies are shown.

Planning the Review
In order to understand the various investigations carried out to identify the ITSs and construct the ITSC, the following sources were searched: IEEE Xplore, ACM Digital Library, SpringerLink, AIS Electronic Library, and Science Direct.
To carry out the literature review, the following research question was posed: What research was done to identify services in the conformation of the ITSC?
Likewise, the terms for the search string were defined as follows: (IT OR TECHNOLOGY) AND SERVICE AND (CATALOG OR IDENTIFICATION).
Likewise, the inclusion and exclusion criteria detailed in Table 1 were established.To develop the review, a discrimination process was followed according to the criteria established in Table 1 and applying the terms of the search chain set forth above.The protocol that was used to perform the review is shown in Figure 2.

Inclusion Criteria
Exclusion Criteria Articles related to research questions Studies in a language other than English Studies from 2008 to 2018 Studies that do not meet the inclusion criteria Studies related to service identification and ITSC Articles that are in journals or congresses Complete studies

Carrying out the Review
To develop the review, a discrimination process was followed according to the criteria established in Table 1 and applying the terms of the search chain set forth above.The protocol that was used to perform the review is shown in Figure 2.

Results of the Review
Initially, 5352 articles were obtained via this systematic search process, of which 109 were relevant.Ultimately, 30 studies were selected, as shown in Table 2. Most of the studies found corresponded to IEEE Xplore (with 70% of the total), and the sources with the fewest studies were the AIS Electronic Library and Science Direct with 3%, as shown in Table 2.A detailed explanation of the 30 selected articles can be found in Sections 4.2 and 4.3.

Framework for the Construction of the Proposal
Complete review of articles (it is a contribution for the identification of services and the construction of the ITSC)

Results of the Review
Initially, 5352 articles were obtained via this systematic search process, of which 109 were relevant.Ultimately, 30 studies were selected, as shown in Table 2. Most of the studies found corresponded to IEEE Xplore (with 70% of the total), and the sources with the fewest studies were the AIS Electronic Library and Science Direct with 3%, as shown in Table 2.A detailed explanation of the 30 selected articles can be found in Sections 4.2 and 4.3.

Framework for the Construction of the Proposal
This proposal was constructed based on the framework shown in Figure 3.As shown in Figure 3, phase 1 covers the construction of the solution, where a model is initially defined to learn from a knowledge base.This learning is done using the requests (or incidents) and its cataloging of the departments or IT areas of organizations that have the ITSC implemented.Phase 2 can be executed N times in institutions that wish to build an ITSC.This proposal was constructed based on the framework shown in Figure 3.As shown in Figure 3, phase 1 covers the construction of the solution, where a model is initially defined to learn from a knowledge base.This learning is done using the requests (or incidents) and its cataloging of the departments or IT areas of organizations that have the ITSC implemented.Phase 2 can be executed N times in institutions that wish to build an ITSC.

Considerations for the Development of the Case Study
Phase 1, corresponding to the "construction of the solution", was created with a knowledge base of four public institutions, in this case, corresponding to decentralized municipal autonomous governments, from which 1699 requests (requirements or incidents) were recovered with their respective catalogs.
To develop the case study (that is, to apply phase 2 of the proposal), a public institution was chosen from the province of Manabí, Republic of Ecuador.Specifically, we chose a municipal decentralized autonomous government with an IT department and no ITSC.The IT department has a chief or area coordinator and six IT workers who attend to the requests of IT users that provide ITSs to the department in which the proposal was applied.Therefore, a registry of requests available for the department to identify their services and build an ITSC was included.To evaluate this proposal, we used the quality factors to evaluate artifacts for the construction of an ITSC, as proposed by Moody et al. [30] (see Appendix A), since it was used in several investigations, such as those carried out by Mendes et al. [6], Rosa et al. [16], and Gama et al. [31].

Background
When talking about ITSM, it is necessary to mention the fundamental role that the ITS Management Forum (ITSMF) has.The ITSMF is a global, independent, and non-profit organization dedicated to continuous improvement of ITSM [32].According to Clacy and Jennings [32], the ITSMF was established in the United Kingdom in 1991, and the founding chapter of the United Kingdom made significant contributions over the years in establishing the ITSMF as an international organization, as well as supporting the development of the library of infrastructure and information technologies (ITIL) and the associated schemes for qualification and certification.These authors state that this forum continues to be one of the most mature chapters, although it now manages several initiatives to continue developing and sharing these activities throughout the world.The identification, classification, and deregistration of ITSs are very important tasks for the ITSM-as important as the management of IT demand, as well as the financial planning, which represents the cost for the provision of these services.
Since 1998, Niessin and van Vliet [33] worked on a mature model of ITS capabilities that originated from the idea of developing a framework for quality improvement that was oriented to help service organizations become more efficient.One of the most important parts of the work was the ITSC, which requires catalogs to have experience with SLA and services.In 2001, Walker [34] included a section dedicated to the maintenance of the ITSC in his book, "IT problem management",

Considerations for the Development of the Case Study
Phase 1, corresponding to the "construction of the solution", was created with a knowledge base of four public institutions, in this case, corresponding to decentralized municipal autonomous governments, from which 1699 requests (requirements or incidents) were recovered with their respective catalogs.
To develop the case study (that is, to apply phase 2 of the proposal), a public institution was chosen from the province of Manabí, Republic of Ecuador.Specifically, we chose a municipal decentralized autonomous government with an IT department and no ITSC.The IT department has a chief or area coordinator and six IT workers who attend to the requests of IT users that provide ITSs to the department in which the proposal was applied.Therefore, a registry of requests available for the department to identify their services and build an ITSC was included.To evaluate this proposal, we used the quality factors to evaluate artifacts for the construction of an ITSC, as proposed by Moody et al. [30] (see Appendix A), since it was used in several investigations, such as those carried out by Mendes et al. [6], Rosa et al. [16], and Gama et al. [31].

Background
When talking about ITSM, it is necessary to mention the fundamental role that the ITS Management Forum (ITSMF) has.The ITSMF is a global, independent, and non-profit organization dedicated to continuous improvement of ITSM [32].According to Clacy and Jennings [32], the ITSMF was established in the United Kingdom in 1991, and the founding chapter of the United Kingdom made significant contributions over the years in establishing the ITSMF as an international organization, as well as supporting the development of the library of infrastructure and information technologies (ITIL) and the associated schemes for qualification and certification.These authors state that this forum continues to be one of the most mature chapters, although it now manages several initiatives to continue developing and sharing these activities throughout the world.The identification, classification, and deregistration of ITSs are very important tasks for the ITSM-as important as the management of IT demand, as well as the financial planning, which represents the cost for the provision of these services.
Since 1998, Niessin and van Vliet [33] worked on a mature model of ITS capabilities that originated from the idea of developing a framework for quality improvement that was oriented to help service organizations become more efficient.One of the most important parts of the work was the ITSC, which requires catalogs to have experience with SLA and services.In 2001, Walker [34] included a section dedicated to the maintenance of the ITSC in his book, "IT problem management", where he addressed the process to add services and to remove services.However, no evidence was found to corroborate the effectiveness of the processes proposed.Then, in 2002, Sullivan, Edmond, and Hofstede [35] worked on a description of the general nature of these services based on a review of the literature, where they defined the ITSC as the list of services categorized according to classification schemes.
In 2004, Sallé [36] reviewed the literature up to that point and noted the importance of the design, development, operation, and delivery of services as fundamental aspects of the management of services, in reference to several frameworks, such as ITIL, British Standards (BS) 15,000, the Hewlett-Packard (HP) ITS Management Reference Model, the Microsoft Operations Framework (MOF), and IBM's Systems Management Solution Life Cycle.The ITSC is one of the most valuable elements of a comprehensive approach in the provision of services and, as such, should receive due care and attention from its construction.

Research Conducted to Identify ITS
According to the systematic review of the literature that was carried out in this research, since 2008, 30 articles were identified to be related to the process of identifying ITSs.These articles are detailed in Table 3.According to Table 3, the first work identified in this review is the research carried out by Bartsch et al. [37] in 2008, who proposed an approach to the identification and decomposition of hierarchical services based on ontologies to support service providers in the management of operational service processes through the characterization and exploitation of the processes of elementary services.In that same year, Kang et al. [38] proposed an SIM for a product line with appropriate granularity, which used ontology to avoid ambiguous inconsistencies, reaching the conclusion that the proposed method provides adequate granularity for the service and improves reuse in a service-oriented product line.Next, Brocke et al. [39] proposed a way to describe ITS that follows the paradigm of "dominant service logic".If a service provider manages to understand the needs of their client and can create a solution for him or her, the description reflects this and, therefore, offers an advantage over the competitors for organizations that provide ITSs for other entities.In the same way, Borner et al. [40] contributed to governance and strategy of management issues with a focus on individual services, focusing especially on the identification and design of services that belong to the initial phases of the life cycle of the service architecture.
In 2009, Gebhart and Abeck [41] proposed a set of rules to systematically derive a service inventory model from a customized business model that captures the most relevant requirements.An investigation conducted by Boerner and Goeken [42] proposed a process-oriented SIM.This approach incorporated a business point of view, strategic and economic aspects, and technical feasibility.Heo et al. [43] decided to present a methodology for the prior evaluation of information security for a u-ITS that analyzes information security threats and vulnerabilities for a u-ITS provider that develops a service and provides the methods and procedures for preparing countermeasures to support the identification of potential risks and how to address them.
In 2010, an investigation carried out by Zimin and Kulakov [44] formulated an approach for the organizational regulation of the ITS in external and internal conditions that change rapidly.This study also has a relationship with the ITSC and the ITSP.Mendes and Silva [45] affirmed that the ITSC is integrated with processes like the SL, FM, request management, and demand management.This research proposed some solutions that tried to mitigate the risks of implementing an ITSC without neglecting the identification of ITSs.Tian et al. [46] conducted an investigation that analyzed how the implementation of a service-oriented architecture (SOA) materializes in the achievements of several applicable IT functions in the form of the encapsulation of services and the interconnection and interoperation of services in the form of flexible coupling.For this, the authors analyzed the structural model in the SOA, in combination with the development code of the unified rational process (RUP), and showed the three SIMs most commonly used in service oriented analysis and design (SOAD) procedures.However, future research should include analyses of different services at all levels of abstraction.
Continuing with the work related to the identification of services, Lee et al. [24] (2011) proposed an SIM based on the modeling of scenarios and the joint creation of values.However, as part of future work, they proposed to refine the approach and apply it to other domains.A prototype environment was also developed to help identify the services and perform an empirical validation of the approach to ensure that unexpected changes in the companies can be treated with care.Another work on the identification of services was developed by Cai et al. [47], who proposed a complete understanding of the service's identification with the service engineering process and the SOA adoption objectives, illustrated the different meanings, positions, and activities of service identification in existing jobs for top-down and bottom-up approaches, presented the common high-value activities in several SIMs, and presented details for these activities.
However, these authors stated that it remains to be determined how high-value activities could be integrated to form an appropriate SIM for a given environment.Research conducted by Utz et al. [48] presented a hybrid modeling approach for services.This research was based on meta-model concepts that resulted in six axioms for combining perspective and modeling aspects in an open environment.However, the additional work needed is related to the identification and formalization of the conceptualization process at a level of detail where the compilation can build on the definition of the identified model goal and provide mechanisms for the reuse of concepts, references, and remarks, as well as their translation and transformation.In that same year (2011), Levina et al. [49] proposed a service design approach that combines several existing methods and approaches.The objective was to develop a method for "service design" in research and industry.The authors also stated that verifiable propositions should be defined and applied in a subsequent case study.Therefore, to be able to refer to an approach as a "method", that approach must provide the definition and description of the construct, the revision of the principles of form and function, and verifiable propositions.
In 2012, Schwarz et al. [50] proposed a research portfolio that classifies the research questions that need to be addressed.This portfolio was developed based on a conceptual framework for service innovation research.The main results show the specific challenges of research in improving the knowledge base of service innovation.Then, Probst and Buhl [51] analyzed how the design of SOA processes is based on selection decisions among the ITSs offered by different providers.They also developed a procedural model for value-based management that considers the dependencies between selection decisions.However, the authors stated that this approach needs to be further developed in the future.Also, in 2012, a study by Rosa et al. [16] stated that the main objective of the ITSM is to guarantee the quality of the ITS and that ITIL is the most commonly adopted best practice framework for implementing ITSM within organizations.They also proposed an SIM through incidents based on an ITSRC.This document's contribution was to help organizations provide quality ITS.However, despite the good results of this work, it remains necessary to continue putting the proposed artifact into practice.The goal of future research should be based on applying the artifact to other organizations to confirm its applicability, ease, and efficiency in achieving a more accurate and better quality ITSRC.
Also in 2012, Mendes et al. [6] analyzed how one of the most important elements of the ITSM is the ITSC, which is described in a formal document listing the available services provided by IT organizations.Likewise, a method based on the design and engineering methodology for organizations (DEMO) was proposed to identify the ITS.However, in future work, the authors intend to apply this proposal to more complex situations, in which the service provider has a broader catalog of services.Likewise, McCarthy et al. [12] described the process used in the IBM company to create and distribute service packages.Finally, the authors stated that an IT organization or service provider can have hundreds of individual services in their catalog, which could be optimized through simple packages or integrated composite services.
In 2013, Gama et al. [31] stated that, until then, there were difficulties in implementing an ITSC.Due to the complexity of an ITSC and other aspects, including the identification of services, the authors proposed an ITSRC to resolve the absence of a foundation for an ITSC.Similarly, Bugeaud et al. [52] presented a dedicated framework based on four basic components throughout the service design process: knowledge, software tools, communities, and places.This research focused mainly on the first two components.In the same year, Arcilla et al. [18] focused on providing useful information for companies interested in defining their own ITSC from a standard ITSC.The purpose of this research was to create a standard ITSC to help microenterprises and small businesses define their own ITSCs as one of the main inputs for their IT FM processes.
In 2014, Huergo et al. [8] proposed an SIM that uses master data and logical data models as inputs.The proposed method also uses an artifact-centered modeling technique to detail the life cycle of the master data and the business rules it contains.However, this method must still be tested in a real business scenario to identify problems and opportunities for improvement.In that same year, the authors Kim et al. [53] analyzed how the governance of SOA requires an adequate process through which the services described by the service model become candidates to enter the portfolio of services.In addition, the authors presented a decision model to evaluate the services according to metrics, where a comparison of the relative value of each service with its development or maintenance cost should be used to establish priorities.This work sought to complement existing governance standards, such as the SOA governance framework, thereby creating a reasonable service development priority.As in 2014, in an investigation carried out by Rong et al. [5], a SIM was proposed from the perspective of the business process.In addition, the authors stated that the proposed framework is being created but still requires some improvements.The application of this method challenges researchers to concentrate their work on designing a special service identification tool and validate it in other domains in the future.
In 2015, Frey et al. [13] introduced a capacity-based service pattern, which helps overcome the challenges associated with identifying the correct services in the analysis phase of large IT modernization programs.This pattern was discovered and derived from practical experience.However, additional research is needed to clarify how capacity-based services can be leveraged to define the architecture, evaluate legacy applications, and determine the roadmap for a program.
Recently, in 2017, Simonova and Foltanova [4] conducted research that focused on the application of business process tools and principles to identify and model the requirements of individual ITSs, with the aim of increasing the quality of information services as part of the quality of business performance.The answers to this research serve as a basis for further discussion and analysis of requirements.
Likewise, in 2017, Souza et al. [54] proposed an approach that focused on business value modeling and used model-based techniques to generate the information required by current methods for identifying software services, thereby aligning business and software perspectives.The results show that this proposal is a promising approach for the alignment of business and IT perspectives during SOA service identification activities.Kalia et al. [15] stated that the automation of services improves the efficiency of ITSM processes.Therefore, the authors proposed a tool called Cataloger, which is a recommendation system that allows humans to specify their requests for change in natural language sentences and generates the most appropriate recommendations.However, this approach has several limitations.Firstly, the dataset that was used is not balanced for all actions.Therefore, grouping-based approaches must be used to minimize the labeling effort and obtain more labels.Secondly, the datasets that were created for specific actions to identify parameters are not large.Thirdly, in the feedback approach, a heuristic approach to decision-making is proposed.In the future, the authors plan to improve this heuristic approach to improve the results.
Recently, in 2018, Mera and Aguilar [55] carried out a systematic review of the literature on existing proposals for the construction and management of the ITSC.In this study, 14 proposals were identified to include methods, framework, approaches, and models, showing that 43% of these proposals were not applied to real environments (that is, they were not checked in public or private organizations), leaving the field open to check these proposals or propose more feasible methods to be applied and evaluated in real environments.

Analysis of the Studies Found in the Review
This sub-section shows a comparison of the studies found with their respective analyses.The compared attributes are detailed in Table 4.
According to Table 4, three types of studies were found.There were 11 articles that detailed literature reviews.There were also 17 articles that corresponded to proposals without verification or application.Finally, there were proposals that were verified to relate them to 10 other articles (33.33% of the studies found).These results show the approximate systematic review of the literature shown by Mera and Aguilar [55].The percentage relates to the studies tested or applied in a real environment, since most of the articles found appear to correspond to literature reviews and proposals without verification.
Regarding the general activities for the construction of the ITSC covered by the proposals found, the most studied activity was to "define the ITS to be provided", which 22 of the studies developed.This activity is directly related to the ITS identification process.However, of this total, only eight items were tested in real environments.Therefore, for the identification of ITS, there are only a few proven proposals that carried out this process.
Another general activity for the construction of the ITSC that stands out and relates to the identification of ITS is the "initial collection of information", which seven of the studies developed.However, of that total, only one study was carried out, reaffirming the scarce application of the proposals in real environments.
A relevant aspect that should be highlighted is that only two of the studies that correspond to proposals with results were tested in public organizations, and none applied automatic mechanisms (machine learning) for the identification of ITSs or the construction of an ITSC.Therefore, the possibility is open to develop proposals for the identification of ITSs and the construction of ITSCs in public organizations, which provides sufficient information to develop the proposal detailed in this paper.

Proposal
The proposed solution is based on the structure of the framework shown in Figure 3, which has two phases that are explained below.

Phase 1-Construction of the Solution
Taking into account the study conducted by Mera and Aguilar [56], Figure 4 shows the scheme currently used by the few organizations that implemented an ITSC to manage requests from the various departments of the organization to the IT department or area.

Proposal
The proposed solution is based on the structure of the framework shown in Figure 3, which has two phases that are explained below.

Phase 1-Construction of the Solution
Taking into account the study conducted by Mera and Aguilar [56], Figure 4 shows the scheme currently used by the few organizations that implemented an ITSC to manage requests from the various departments of the organization to the IT department or area.According to the literature reviewed, the ITSC, in addition to containing properly categorized services, must also provide an access method to request such services.However, the field study on public organizations conducted by Mera and Aguilar [56] determined that IT users do not mostly use ITSC to choose the service they need (in this study, only 20% of users claimed to use a catalog to request a service).Instead, these users prefer to perform requests through e-mail, calls, WhatsApp messages, memoranda, and internal messaging, in that order.Thus, the "message" is firstly processed by the person in charge of the help desk.Then, one must locate or verify that message within the ITSC of the IT service to which this request belongs.This information is registered in a database together with the solution offered or delivered to the IT user.
With this background, phase 1 of the proposal is proposed.This phase consists of constructing a solution, where, from the "knowledge" generated by organizations that have a record of requests for requirements or IT incidents within their respective catalogs, this knowledge can be used to build a solution tailored to the real needs of public organizations, including the identification of ITSs and the construction of an ITSC.

Extraction of Knowledge
In this part, we extract the knowledge of organizations (in this case, municipal autonomous governments) that implemented an ITSC that registers requests, catalogs, and solutions, to empty them into their own structure.This process is detailed in Figure 5.According to the literature reviewed, the ITSC, in addition to containing properly categorized services, must also provide an access method to request such services.However, the field study on public organizations conducted by Mera and Aguilar [56] determined that IT users do not mostly use ITSC to choose the service they need (in this study, only 20% of users claimed to use a catalog to request a service).Instead, these users prefer to perform requests through e-mail, calls, WhatsApp messages, memoranda, and internal messaging, in that order.Thus, the "message" is firstly processed by the person in charge of the help desk.Then, one must locate or verify that message within the ITSC of the IT service to which this request belongs.This information is registered in a database together with the solution offered or delivered to the IT user.
With this background, phase 1 of the proposal is proposed.This phase consists of constructing a solution, where, from the "knowledge" generated by organizations that have a record of requests for requirements or IT incidents within their respective catalogs, this knowledge can be used to build a solution tailored to the real needs of public organizations, including the identification of ITSs and the construction of an ITSC.

Extraction of Knowledge
In this part, we extract the knowledge of organizations (in this case, municipal autonomous governments) that implemented an ITSC that registers requests, catalogs, and solutions, to empty them into their own structure.This process is detailed in Figure 5.

Proposal
The proposed solution is based on the structure of the framework shown in Figure 3, which has two phases that are explained below.

Phase 1-Construction of the Solution
Taking into account the study conducted by Mera and Aguilar [56], Figure 4 shows the scheme currently used by the few organizations that implemented an ITSC to manage requests from the various departments of the organization to the IT department or area.According to the literature reviewed, the ITSC, in addition to containing properly categorized services, must also provide an access method to request such services.However, the field study on public organizations conducted by Mera and Aguilar [56] determined that IT users do not mostly use ITSC to choose the service they need (in this study, only 20% of users claimed to use a catalog to request a service).Instead, these users prefer to perform requests through e-mail, calls, WhatsApp messages, memoranda, and internal messaging, in that order.Thus, the "message" is firstly processed by the person in charge of the help desk.Then, one must locate or verify that message within the ITSC of the IT service to which this request belongs.This information is registered in a database together with the solution offered or delivered to the IT user.
With this background, phase 1 of the proposal is proposed.This phase consists of constructing a solution, where, from the "knowledge" generated by organizations that have a record of requests for requirements or IT incidents within their respective catalogs, this knowledge can be used to build a solution tailored to the real needs of public organizations, including the identification of ITSs and the construction of an ITSC.

Extraction of Knowledge
In this part, we extract the knowledge of organizations (in this case, municipal autonomous governments) that implemented an ITSC that registers requests, catalogs, and solutions, to empty them into their own structure.This process is detailed in Figure 5. (a) Select the knowledge source database Each selected database corresponds to an organization that fully implemented the ITSC and necessarily registers requests (requirements and incidents), catalogs, and solutions (optional) that were registered based on the management of the demand for ITS in recent years, with the aim of obtaining a list of categories, services, and requests (messages) M. Therefore, in this study, four institutions that meet these parameters were selected (located via the field study conducted by Mera et al. [57]), whose request databases were named BD1, BD2, BD3, and BD4.
(b) Standardization of the ITSC in relation to the single ITSRC Using the unique ITSRC obtained through the process detailed in Appendix B, the names of the categories and services of the ITSC for the four organizations chosen as the knowledge base were normalized, so that the services and categories had uniform names or denominations.In this way, the conformation of the resulting structure detailed in the next section could be created correctly.The procedure to normalize the ITSC of each organization or entity was the same as that used to create the unique ITSRC.Firstly, the catalog that was taken as the primary reference was a unique ITSRC.Moreover, all the requests or messages were placed according to the services and categories, thereby yielding the ITSC of each organization after the comparison process.A new service was also included, as detailed below.
Service, security cameras, in Category, security management This service arose from the comparison made with the ITSC of the organizations that had this service registered in their ITSC.
(c) Create the structure The next step was the creation of the structure.To build a structure called "knowledge" C, from the BD database of each organization, the first level corresponded to the Cat categories, which were the IT categories established in the ITSC used in these institutions.The second level corresponded to the S services identified in these institutions, which were categorized in the ITSC.In this way, we obtained the following: Organization 1: where, to obtain the desired structure in relation to the Cat categories, the following operation was carried out: In relation to the S services that go into each Cat category, the following operations were carried out: As a result, at the level of the directory structure, we obtained a result similar to the one shown in Figure 6.
As a result, at the level of the directory structure, we obtained a result similar to the one shown in Figure 6.Once the directory structure was created, each request (message) was distributed in the service that corresponds to it in the structure created.What was expressed up to now is summarized in the following processes: Explained graphically, the entire process was as shown in Figure 7: Once the directory structure was created, each request (message) was distributed in the service that corresponds to it in the structure created.What was expressed up to now is summarized in the following processes: Explained graphically, the entire process was as shown in Figure 7: Once the procedures explained above were applied, the resulting catalog corresponding to the "knowledge" structure was as shown in Figure 8. Once the procedures explained above were applied, the resulting catalog corresponding to the "knowledge" structure was as shown in Figure 8. Once the procedures explained above were applied, the resulting catalog corresponding to the "knowledge" structure was as shown in Figure 8.

Appropriation of Knowledge
In this phase, a process based on text mining is proposed.This process was founded on the requests categorized in the "knowledge" structure that allowed a model based on Bayesian networks to "learn" where each request is located (that is, to which service and to what category each request corresponds).For the construction of this process, the Rapid Miner tool was used.This tool is generally structured as shown in Figure 9.

. Appropriation of Knowledge
In this phase, a process based on text mining is proposed.This process was founded on the requests categorized in the "knowledge" structure that allowed a model based on Bayesian networks to "learn" where each request is located (that is, to which service and to what category each request corresponds).For the construction of this process, the Rapid Miner tool was used.This tool is generally structured as shown in Figure 9. Below, each of the operators involved in knowledge learning is described.
(a) Process Documents from Files Operator With this operator, requests are collected from the "knowledge" structure.Within this "process documents from files" structure, the operations proposed in Figure 10 are specified.Below, each of the operators involved in knowledge learning is described.
(a) Process Documents from Files Operator With this operator, requests are collected from the "knowledge" structure.Within this "process documents from files" structure, the operations proposed in Figure 10 are specified.
Below, each of the operators involved in knowledge learning is described.
(a) Process Documents from Files Operator With this operator, requests are collected from the "knowledge" structure.Within this "process documents from files" structure, the operations proposed in Figure 10 are specified.The internal operations performed in this operator are the following:

•
Tokenize.This operator divides the text of the document into a sequence of tokens that are used to construct the word vector.• Filter Stop words.This operator filters the words considered "stop words", i.e., words like in, the, if, for, where, etc. • Transform Cases.This operator transforms the characters to lowercase.

•
Generate n-Grams.With this operator, "phrases" of up to three words are generated.The internal operations performed in this operator are the following: • Tokenize.This operator divides the text of the document into a sequence of tokens that are used to construct the word vector.

•
Filter Stop words.This operator filters the words considered "stop words", i.e., words like in, the, if, for, where, etc.

•
Transform Cases.This operator transforms the characters to lowercase.

•
Generate n-Grams.With this operator, "phrases" of up to three words are generated.

(b) Operator Naïve Bayes
This is the model that is used to "learn" the word structure of the different requests of each service in the categories specified in the "knowledge" structure.This learning is done through a simple probabilistic classification model.This operator can establish the characteristics to build classifications based on few data.

(c) Storage Operators (Sentence and Model)
Storage operators are used to store the characteristics and models already learned from the requests found in the knowledge structure.With this last process, the solution is ready to be used in the identification of ITSs and, therefore, for the construction of an ITSC in a number of organizations.

Phase 2-Identification of Services and the Construction of an ITSC
Once the solution was finished, it was ready to be executed in a number of organizations.To accomplish this task, it was necessary to follow the processes detailed below.

Identification of ITS
A fundamental task in the construction of an ITSC is the identification and subsequent classification of services, since a service is the most fundamental component of an ITSC.Therefore, its correct identification is crucial when initiating an ITSCM.In fact, identification is the first activity.In order to execute the identification of ITSs, the processes detailed in Figure 11 were used.

Identification of ITS
A fundamental task in the construction of an ITSC is the identification and subsequent classification of services, since a service is the most fundamental component of an ITSC.Therefore, its correct identification is crucial when initiating an ITSCM.In fact, identification is the first activity.In order to execute the identification of ITSs, the processes detailed in Figure 11 were used.After selecting the organization, it was necessary to extract the record of requests, remembering that the M requests could come from different FR files, such as Excel sheets, emails, internal messaging, etc.The idea was to extract the requests from all the data sources and centralize them in a BDS database, as follows: According to the request files: The operation to be performed was as follows: which graphically translates to the scheme shown in Figure 12.(a) Select the organization The first thing to do in this phase was to select the organization, which must meet the following requirements:

•
It must have a department or IT area.

•
It must have a record of service requests or IT incidents (for at least the last year, preferably).
(b) Extract the request record After selecting the organization, it was necessary to extract the record of requests, remembering that the M requests could come from different FR files, such as Excel sheets, emails, internal messaging, etc.The idea was to extract the requests from all the data sources and centralize them in a BDS database, as follows: According to the request files: (c) Execute automatic service identification Once the requests were ready in a BDS central database and in the same format, a process was applied to identify the services based on the requests made in the "construction of the solution" phase using the Rapid Miner tool to process each request.This process was structured as shown in Figure 13.(c) Execute automatic service identification Once the requests were ready in a BDS central database and in the same format, a process was applied to identify the services based on the requests made in the "construction of the solution" phase using the Rapid Miner tool to process each request.This process was structured as shown in Figure 13.

•
Storage operators (models and sentences).The first step is to establish that the service identification activity is carried out based on the characteristics and the models that were "learned".For this purpose, the operators specify that these inputs leave the previously prepared repositories.

•
Process Document from File Operator.With this operator, requests are collected from BDS.Within this "process documents from files", the solutions for phase 1 are specified via the same operations used in Section 5.1.2("appropriation of knowledge").

•
Apply model operator.With this operator, the service identification process is performed based on the requests that the model "learned" in the "construction of the solution" phase from the "knowledge" database C. The process then verifies each request stored in the BDS to review its characteristics to determine which ITS corresponds to that service.This ITS is then registered in the "list of found ITSs".The process of identifying such services is summarized in the algorithm shown in Figure 14.(c) Execute automatic service identification Once the requests were ready in a BDS central database and in the same format, a process was applied to identify the services based on the requests made in the "construction of the solution" phase using the Rapid Miner tool to process each request.This process was structured as shown in Figure 13.

•
Storage operators (models and sentences).The first step is to establish that the service identification activity is carried out based on the characteristics and the models that were "learned".For this purpose, the operators specify that these inputs leave the previously prepared repositories.• Process Document from File Operator.With this operator, requests are collected from BDS.Within this "process documents from files", the solutions for phase 1 are specified via the same operations used in Section 5.1.2("appropriation of knowledge").• Apply model operator.With this operator, the service identification process is performed based on the requests that the model "learned" in the "construction of the solution" phase from the "knowledge" database C. The process then verifies each request stored in the BDS to review its characteristics to determine which ITS corresponds to that service.This ITS is then registered in the "list of found ITSs".The process of identifying such services is summarized in the algorithm shown in Figure 14.In this classification process, there is the possibility that some of the requests do not correspond to any service that was learned.In this case, the IT worker(s) must discern which services correspond to the request or discard the request because its content is inconsistent and, thus, possibly a wrong request registered with the BDS.In this classification process, there is the possibility that some of the requests do not correspond to any service that was learned.In this case, the IT worker(s) must discern which services correspond to the request or discard the request because its content is inconsistent and, thus, possibly a wrong request registered with the BDS.

Classification of Services and Generation of the ITSC
Once the ITSs were identified, it was necessary to classify them.For this task, it was necessary to compare the list of services found with the ITSRC, thereby registering each service with its corresponding category.The algorithm for this process is represented in Figure 15.In this classification process, there is the possibility that some of the requests do not correspond to any service that was learned.In this case, the IT worker(s) must discern which services correspond to the request or discard the request because its content is inconsistent and, thus, possibly a wrong request registered with the BDS.

Classification of Services and Generation of the ITSC
Once the ITSs were identified, it was necessary to classify them.For this task, it was necessary to compare the list of services found with the ITSRC, thereby registering each service with its corresponding category.The algorithm for this process is represented in Figure 15.With the application of the previous algorithm, a result similar to that shown in Table 5 was generated.

Case Study
To develop the "identification of services and construction of the ITSC" (that is, phase 2 of the proposal), a municipal autonomous decentralized government of the province of Manabí, Republic of Ecuador, was chosen.This government met the following conditions: (a) it had a department or IT area with a coordinator or head and several IT workers (six); (b) it did not have an ITSC implemented; and (c) it had a record of requests (requirements or incidents).
From this institution, 415 requests expressed in natural language were obtained.These requests served as a basis to identify ITSs and generate an appropriate ITSC.From the 415 requests (requirements or incidents), 23 ITSs were ultimately identified: LAN admin, WAN admin, authentication and authorization, file sharing, material purchase, software purchase, backup and recovery, create/integrate applications, active directory, hardware, printer maintenance, maintenance and support, apps maintenance and support, network monitoring, antivirus service, firewall service, video conferencing, VoIP service, software, application support, technical/user support, security cameras, email, and collaboration services.These ITSs corresponded to 11 categories.As a result of the classification process, the ITSC of the institution in question was formed as shown in Figure 16.
and (c) it had a record of requests (requirements or incidents).
From this institution, 415 requests expressed in natural language were obtained.These requests served as a basis to identify ITSs and generate an appropriate ITSC.From the 415 requests (requirements or incidents), 23 ITSs were ultimately identified: LAN admin, WAN admin, authentication and authorization, file sharing, material purchase, software purchase, backup and recovery, create/integrate applications, active directory, hardware, printer maintenance, maintenance and support, apps maintenance and support, network monitoring, antivirus service, firewall service, video conferencing, VoIP service, software, application support, technical/user support, security cameras, email, and collaboration services.These ITSs corresponded to 11 categories.As a result of the classification process, the ITSC of the institution in question was formed as shown in Figure 16.Once the ITSC of the institution was generated, a survey was applied to the head and the six workers of the IT department.This survey was elaborated based on the quality factors of Moody et al. [30] to evaluate the artifacts of this type.These factors (F) were as follows: (F1) completeness, (F2) integrity, (F3) flexibility, (F4) understandability, (F5) correctness, (F6) simplicity, (F7) integration, and (F8) implementation, where each factor corresponded to a survey question applied.These questions are shown in Appendix A. Once the ITSC of the institution was generated, a survey was applied to the head and the six workers of the IT department.This survey was elaborated based on the quality factors of Moody et al. [30] to evaluate the artifacts of this type.These factors (F) were as follows: (F1) completeness, (F2) integrity, (F3) flexibility, (F4) understandability, (F5) correctness, (F6) simplicity, (F7) integration, and (F8) implementation, where each factor corresponded to a survey question applied.These questions are shown in Appendix A.

Results
According to Figure 17, the results were very satisfactory, since, in most of the factors, the respondents answered affirmatively.Next, each of the factors was analyzed.
To qualify the assessment of the respondents' responses, a Likert scale was used with the following values for each questioned factor: 1 (poor), 2 (fair), 3 (average), 4 (good), 5 (excellent).To verify the consistency of the survey, Cronbach's alpha coefficient was used to quantify the level of reliability of the measurement scale.The result obtained was 0.845, which means that our instrument is reliable.Below, the results obtained for each of the factors analyzed in our proposal are shown.
In relation to F1 (completeness), the respondents were asked if the device is sufficiently complete for the identification of the ITS required by the organization.Ultimately, 57.1% of the respondents said that the ITS is excellent in this aspect, and 42.9% said that the ITS is good (that is, that it is sufficiently complete).
Regarding F2 (integrity), the respondents were asked if the device has an integrated structure for the identification of services and the construction of the ITSC.A total of 71.4% of respondents said that the structure is excellent, while 28.6% said that it was good (i.e., sufficiently intact).
respondents answered affirmatively.Next, each of the factors was analyzed.
To qualify the assessment of the respondents' responses, a Likert scale was used with the following values for each questioned factor: 1 (poor), 2 (fair), 3 (average), 4 (good), 5 (excellent).To verify the consistency of the survey, Cronbach's alpha coefficient was used to quantify the level of reliability of the measurement scale.The result obtained was 0.845, which means that our instrument is reliable.Below, the results obtained for each of the factors analyzed in our proposal are shown.In relation to F1 (completeness), the respondents were asked if the device is sufficiently complete for the identification of the ITS required by the organization.Ultimately, 57.1% of the respondents said that the ITS is excellent in this aspect, and 42.9% said that the ITS is good (that is, that it is sufficiently complete).
Regarding F2 (integrity), the respondents were asked if the device has an integrated structure for the identification of services and the construction of the ITSC.A total of 71.4% of respondents said that the structure is excellent, while 28.6% said that it was good (i.e., sufficiently intact).
For F3 (flexibility), the question to the respondents was the following: Is the device flexible enough to adapt to the diverse requirements of the organization in relation to the identification of  For F3 (flexibility), the question to the respondents was the following: Is the device flexible enough to adapt to the diverse requirements of the organization in relation to the identification of services and the construction of the ITSC?To this question, 42.9% of the respondents stated that the artifact is excellent, while 57.1% of the respondents said that it was good (i.e., that the proposed artifact is very flexible).

F8) Implementability
In relation to F4 (understandability), it was asked if the device is easy to understand for those in charge and for IT workers.To this, 42.9% said that the device is excellent, while 57.1% said that it is good.This shows that the proposed artifact is very easy to understand.
Regarding F5 (correctness), respondents were asked if the structure of the artifact is clear due to the notation used.A total of 57.1% of respondents said it is excellent, while 14.3% said it is good, and 28.6% said that it is average.This shows that the structure of the artifact is clear.
For F6 (simplicity), it was asked if the artifact is simple in its ability to identify the services and construction of the ITSC.A total of 42.9% of the respondents said the artifact is excellent, while 28.6% said it is good; 28.6% also said that it is average, which shows that the simplicity levels are high.
For F7 (integration), respondents were asked if the ITSC built after the application of the device reflects the ITS required by the institution.A total of 71.4% said that the tool is excellent, while 28.6% said it is good, which shows that the device integrates very well with the organization's IT aspects.
Finally, for F8 (implementation), respondents were asked if it is feasible to implement the device in organizations that wish to identify their ITSs and build their ITSC.A total of 57.1% of respondents said that it is excellent, while 42.9% stated that it is good, meaning that the tool has high levels of implementation in municipal organizations.
Thus, the assessment provided by the respondents is highly positive.To this, we add that the number of services identified corresponded 100% to the services that should have been identified based on the historical data of the organization for which the identification process was carried out for the ITS and construction of the ITSC.

Discussion
The proposal detailed in this document allows identification of the ITSs and the construction of the ITSC.This proposal was developed considering several important aspects obtained from other SIM and research dedicated to the construction of the ITSC (mainly in relation to the identification process of ITS).As described above, in phase 1 of the proposal, machine learning was used to generate a model that carried out its "learning" process based on 1699 applications (IT requirements and incidents) cataloged in departments or areas of IT from four public organizations (municipal autonomous decentralized government of Ecuador).Therefore, the possibility remains that more public organizations can be used as a reference to enrich the initial "knowledge" and, thus, have a greater capacity for automatic identification of the ITS.
Although identification of the ITS is a process that can be carried out through different SIMs, with the proposed method, it was possible to use requests and IT incidents registered by the coordinator and IT workers of a public organization as the input (case study, the municipal autonomous decentralized government of Ecuador) to identify their ITSs and to build their ITSC.This approach achieved very satisfactory results, as evidenced by the survey applied to the coordinator and the IT area workers.The success achieved was subject to the fact that the learning carried out in phase 1 of the proposal was based on the applications cataloged by four public organizations of the same type as the organization chosen to develop the case study, since the nature of the requests was similar, and they belonged to the same context at the level of daily operations carried out by IT users.
When technological solutions, such as the one described in this paper, are proposed, they are expected to have the approval of the personnel working in the area involved, since these personnel are the people who will use this tool.In this case, one of the most relevant aspects is the necessarily high level of understanding of the staff needed to use the proposal to identify ITSs and construct an ITSC.This was evidenced in the responses of respondents regarding factors of understandability, correctness, and simplicity.These results should be considered since there are studies (such as that conducted by Mera et al. [57]) that showed how many public institutions do not have an ITSC.One of the factors highlighted in that study is the "complexity of applying existing standards" to build the ITSC.
Another important result that should be highlighted is the high levels of efficiency and effectiveness of the proposal.For efficiency, we highlighted the high levels obtained for the factors of completeness, integrity, flexibility, integration, and implementation, which evaluated the proposal itself.At the level of structure, the levels of adaptability, the degree of integration of the results with the needs of those involved, and the levels of implementation of the proposal are important.On the other hand, when talking about effectiveness, it is necessary to highlight that, according to the historical data of requests that were analyzed with those involved, the results obtained for the amount of identified ITS were very satisfactory, based on all possible services that could result after applying the proposal for that data.
An important contribution of this proposal is the inclusion of machine learning for the identification of ITSs and the automatic construction of the ITSC, since this technique was previously used for the identification of ITSs, but only at the level of request management when the ITSC was already in operation [15] and not for the construction of the ITSC (in addition to the registration of IT requests and also to the registration of IT incidents for these tasks).

Conclusions
Once the present research was concluded, the conclusions below were reached.As science and technology advances, it is necessary to have efficient SIMs built with a consistent knowledge base, which allows workers and IT coordinators to have appropriate tools to carry out their activities related to ITSM, taking advantage of technologies like machine learning to give added value to these activities.The ITS identification process is a fundamental aspect in building an ITSC; therefore, it is very important to perform ITS identification correctly, since the ITSC is a fundamental component of the ITSP, which in turn is the basis for deploying a correct ITSM.
According to the systematic review of the literature, 5352 articles were identified, and 30 articles were selected for our study.It can be seen that there are several SIMs that were used, none of which became a standard for the identification of ITSs, nor is there a standard for the construction of the ITSC.Of the SIMs identified, there were proposals that used natural language as an input to identify ITS.However, none of the investigations conducted were able to integrate the change requests and the incident register to build an ITSC.
A proposal was submitted for the identification of ITS and construction of the ITSC, which consists of two phases.The first phase corresponds to a learning stage, from which knowledge of the four public institutions that have an ITSC generated a model that uses Bayesian networks as a classification system.The second phase corresponds to the implementation stage of the ITSC, which can be replicated in a number of organizations.This process can be applied to identify ITSs and build the ITSC in several institutions, based on their history of IT requests and incidents (text).
The proposal presented was applied to a public institution, specifically, a municipal autonomous decentralized government of Ecuador, whose history of requests and incidents was used to identify ITSs and build the ITSC.After creating the ITSC, it was possible to show that the proposal is highly effective, since, through the application of a survey, the coordinator and the IT workers were able to assess the quality factors of the proposal presented for the creation of the ITSC.
Making a comparison between our proposal and the SIMs detailed in Table 4, three aspects were highlighted.Firstly, the proposal present in this document is a "proposal with results", which were obtained through its application in a real environment, adding to the limited list of proposals with results detailed in Table 4. Secondly, this proposal complies with four of the general activities for the construction of the ITSC: the initial collection of information, the identification of ITSs (ITS definition), and the refinement and the publication of the ITSC (which is generated from the classification of the ITSs).What makes the difference, compared to the SIMs detailed in Table 4, is the application of machine learning with the characteristics described in Section 5, which include the requests and incidents of registered ITSs, taking them as input to build the ITSC, unlike the SIMs identified in Table 4. Thirdly, another important aspect is that the proposal was applied in a public organization, adding to only two SIMs in Table 4 that were tested in this type of organization, contributing to the generation of important data for this type of proposal, which must continue to be tested in real environments.
In future work, it will be necessary to replicate the proposals in other public organizations in order to obtain the necessary feedback to improve them.It will also be necessary to integrate them with other ITSCM activities at the ITSC architecture level, such as ITSC feedback, and the elimination or withdrawal of services, as well as other activities.

Figure 1 .
Figure 1.Part of a standard technical information technology service catalog (ITSC).

Figure 1 .
Figure 1.Part of a standard technical information technology service catalog (ITSC).

Figure 2 .
Figure 2. Protocol for the review and selection of articles.

Figure 2 .
Figure 2. Protocol for the review and selection of articles.

Figure 3 .
Figure 3. Framework for the construction of the proposal.

Figure 3 .
Figure 3. Framework for the construction of the proposal.

Figure 4 .
Figure 4. Process of IT demand management.

Figure 5 .
Figure 5. Process for the extraction of knowledge.

Figure 4 .
Figure 4. Process of IT demand management.

Figure 4 .
Figure 4. Process of IT demand management.

Figure 5 .Figure 5 .
Figure 5. Process for the extraction of knowledge.

Figure 6 .
Figure 6.Knowledge structure C and directories.

Figure 6 .
Figure 6.Knowledge structure C and directories.

Figure 8 .
Figure 8.An ITSC that corresponds to the knowledge structure.

Figure 8 .
Figure 8.An ITSC that corresponds to the knowledge structure.

Figure 10 .
Figure 10.Internal process of the "process documents from files" operator.

Figure 10 .
Figure 10.Internal process of the "process documents from files" operator.

Figure 11 .
Figure 11.General processes for the identification of services.

Figure 11 .
Figure 11.General processes for the identification of services.

32 File of IT requests 3 File of IT requests 1 File of IT requests 2 FileFigure 12 .
Figure 12.Graphical scheme of the collection of requests.

Figure 12 .
Figure 12.Graphical scheme of the collection of requests.

File of IT requests 3 File of IT requests 2 FileFigure 12 .
Figure 12.Graphical scheme of the collection of requests.

Figure 13 .
Figure 13.Text mining process for the automatic identification of services.

Figure 13 . 32 Figure 14 .
Figure 13.Text mining process for the automatic identification of services.Symmetry 2019, 11, x FOR PEER REVIEW 21 of 32

Figure 14 .
Figure 14.Algorithm for the automatic identification of services.

Figure 14 .
Figure 14.Algorithm for the automatic identification of services.

Figure 15 .
Figure 15.Algorithm for the classification of services and generation of the ITSC.Figure 15.Algorithm for the classification of services and generation of the ITSC.

Figure 15 .
Figure 15.Algorithm for the classification of services and generation of the ITSC.Figure 15.Algorithm for the classification of services and generation of the ITSC.

Figure 16 .
Figure 16.An ITSC corresponding to the knowledge structure.

Figure 16 .
Figure 16.An ITSC corresponding to the knowledge structure.

Table 1 .
Inclusion and exclusion criteria.ITSC-information technology service catalog.

Table 3 .
Research conducted on the identification of information technology services (ITS).SOA-service-oriented architecture; DEMO-design and engineering methodology for organizations.

Table 4 .
Comparison of the studies found in the review.SLA-service level agreement.

Table 5 .
Result of the classification of services at the table level.