A service configuration system

Abstract

The present invention relates to a system (1) for managing the relationships between assets subject to service management and configuration management processes.

Description

[0001] DESCRIPTION

[0002] A SERVICE CONFIGURATION SYSTEM

[0003] Technical Field

[0004] The present invention relates to a system for managing the relationships between assets subject to service management and configuration management processes.

[0005] Background of the Invention

[0006] In service management and configuration management processes, the management of relationships between assets is often a complex and problematic field. Failure to define these relationships correctly may affect the functionality of the assets and threaten the continuity of services. For example, updating the servers or network components to which an application is connected may lead to unexpected outages or performance degradation if it is performed without considering the interactions of these components with other systems. Furthermore, fixed configurations that are unable to respond to dynamic changes may prevent the timely and effective delivery of services by reducing the agility of the organization. Therefore, continuously updating and monitoring the relationships of assets becomes a critical requirement for effective service management.

[0007] For this reason, it is understood that there is a need for a system for managing the relationships between assets subject to service management and configuration management processes.

[0008] The Chinese patent document no. CN117236645, an application included in the state of the art, discloses an IT asset management system for data center based on equipment information classification. The said invention provides an equipment information classification-based IT asset management system for a data center and is applied to the field of equipment asset management. The system comprises an asset classification management module, an asset basic information management module, an asset dynamic monitoring module, an asset dependency management module, a unified asset summarization module, a mobile asset management module, a heterogeneous cloud integration module, an authority safety management module, an open interface integration module and an IT asset management extension module. The dependency relationship management module integrates multiple means such as network traffic analysis, configuration analysis, and association rule mining to identify the dependency relationship between assets and constructs a more comprehensive and accurate dependency relationship graph. In addition to identifying dependency relationships, this module highlights important dependency relationships by assigning different weights to the dependency relationship and facilitates focus for operations and maintenance personnel.

[0009] Summary of the Invention

[0010] An object of the present invention is to realize a system developed with the aim of managing the relationships between assets subject to service management and configuration management processes.

[0011] Detailed Description of the Invention

[0012] “A Service Configuration System” realized to fulfil the objective of the present invention is shown in the figure attached, in which:

[0013] Figure l is a schematic view of the inventive system.

[0014] The components illustrated in the figure are individually numbered, where the numbers refer to the following: 1. System

[0015] 2. Application

[0016] 3. Server

[0017] The inventive system (1) developed with the aim of managing the relationships between assets subject to service management and configuration management processes comprises at least one application (2) which is configured to enable users to manage service management and configuration management processes through an interface; companies to specify which business processes their business lines use; and software development teams to define which technical services they provide; and at least one server (3) which is configured to enable configuration definitions of all infrastructure elements to be carried out; to determine which feature the infrastructure element at the level defined as type should have, how its singular ownership will be and how its relationship model will be; to group services according to portfolio information; to group services according to sub-portfolio information; to present a service catalogue to lines of business or directly to users; and to display on an interface with which technical services the services presented to the customer are presented.

[0018] The application (2) included in the inventive system (1) is configured to establish communication and exchange data with the server (3) by using any communication protocol. The application (2) is configured to enable software development teams to define through an interface which technical services they provide. The application (2) is configured to be referred to as information technology whereby users can perform brand management. The application (2) is configured to enable the specified application services to be defined in a logical way, with an identifiable front-end information. The server (3) included in the inventive system (1) is configured to establish communication and exchange data with the application (2) by using any communication protocol. The server (3) is configured to comprise the configuration definitions of all infrastructure elements and to enable different types and multiple configuration elements of each type to be defined. The server (3) is configured to determine which feature the infrastructure element at the level defined as type should have, how its singular ownership will be, and how its relationship model will be. The server (3) is configured to comprise every asset that corresponds to the smallest application parts used in such a way as to express them. The server (3) is configured to enable the detection of which application services are provided by the written code fragments. The server (3) is configured to comprise a layer that enables applications to be grouped from a service perspective and provides information about the module or architecture of the applications. The server (3) is configured to answer the questions of how, who, with whom and integrated with whom in the service layer of the flexible layer it comprises, as well as to include information about the modules or architecture of the application. The server (3) is configured to enable software development teams to define which technical services they provide. The server (3) is configured to enable people to be flexible in the definition phase; to break down the details; to enable impact analysis to be deepened and to be designed also as monolithic. The server (3) is configured to enable the service and product perspectives to be associated; the application services to be defined; and to detect with which fragments of code the application services are created by writing with the established relationship. The server (3) is configured to enable situations in which business processes can be provided with applications to be detected. The server (3) is configured to enable situations in which technical application services are written in software with the relevant application to be detected. The server (3) is configured to enable companies to specify which business processes are used by their business lines; ownership and required characteristics of business processes are specified by being defined; criticality information of business processes to be kept as a feature; and the information of which logical applications are used to realize business processes to be detected. The server (3) is configured to enable business services to be grouped according to portfolio information and to be presented to the authorized user through an interface. The server (3) is configured to enable business services to be grouped according to sub-portfolio information and to be presented to the authorized user through an interface. The server (3) is configured to enable service catalogues to be provided to business lines or directly to users; the processes in the form of requests and user cases that are worked on one-on-one with the customer to be transmitted to the customer; the produced services to be transmitted to the customer in detail by transmitting the names of the services in a way that the customers can pronounce and understand. The server (3) is configured to display information with which technical services the services presented to the customer are presented and to enable services and applications to connect to each other. The server (3) is configured to comprise information with which infrastructure services the services are presented. The server (3) is configured to be associated with the configuration elements in the product perspective, and to enable information about which feature in the services performs which function, and what type of configuration we need to establish by selecting which features to be detected.

[0019] Industrial Application of the Invention

[0020] By means of the inventive system (1), it is enabled to manage the relationships between assets subject to service management and configuration management processes.

[0021] Within these basic concepts; it is possible to develop various embodiments of the inventive “A Service Configuration System (1)”; the invention cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

CLAIMS1. A system (1) for managing the relationships between assets subject to service management and configuration management processes; comprising at least one application (2) which is configured to enable users to manage service management and configuration management processes through an interface; companies to specify which business processes their business lines use; and software development teams to define which technical services they provide; and characterized by at least one server (3) which is configured to enable configuration definitions of all infrastructure elements to be carried out; to determine which feature the infrastructure element at the level defined as type should have, how its singular ownership will be and how its relationship model will be; to group services according to portfolio information; to group services according to sub-portfolio information; to present a service catalogue to lines of business or directly to users; and to display on an interface with which technical services the services presented to the customer are presented.

2. A system (1) according to Claim 1; characterized by the application (2) which is configured to establish communication and exchange data with the server (3) by using any communication protocol.

3. A system (1) according to Claim 1 or 2; characterized by the application (2) which is configured to enable software development teams to define through an interface which technical services they provide.

4. A system (1) according to any one of the preceding claims; characterized by the application (2) which is configured to be referred to as information technology whereby users can perform brand management.

5. A system (1) according to any one of the preceding claims; characterized by the application (2) which is configured to enable the specified application services to be defined in a logical way, with an identifiable front-end information.

6. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to establish communication and exchange data with the application (2) by using any communication protocol.

7. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to comprise the configuration definitions of all infrastructure elements and to enable different types and multiple configuration elements of each type to be defined.

8. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to determine which feature the infrastructure element at the level defined as type should have, how its singular ownership will be, and how its relationship model will be.

9. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to comprise every asset that corresponds to the smallest application parts used in such a way as to express them.

10. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable the detection of which application services are provided by the written code fragments.

11. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to comprise a layer that enables applications to be grouped from a service perspective and provides information about the module or architecture of the applications.

12. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to answer the questions of how, who, with whom and integrated with whom in the service layer of the flexible layer it comprises, as well as to include information about the modules or architecture of the application.

13. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable software development teams to define which technical services they provide.

14. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable people to be flexible in the definition phase; to break down the details; to enable impact analysis to be deepened and to be designed also as monolithic.

15. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable the service and product perspectives to be associated; the application services to be defined; and to detect with which fragments of code the application services are created by writing with the established relationship.

16. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable situations in which business processes can be provided with applications to be detected.

17. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable situations in which technical application services are written in software with the relevant application to be detected.

18. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable companies to specify which business processes are used by their business lines; ownership and required characteristics of business processes are specified by being defined; criticality information of business processes to be kept as a feature; and the information of which logical applications are used to realize business processes to be detected.

19. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable business services to be grouped according to portfolio information and to be presented to the authorized user through an interface.

20. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable business services to be grouped according to sub-portfolio information and to be presented to the authorized user through an interface.

21. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to enable service catalogues to be provided to business lines or directly to users; the processes in the form of requests and user cases that are worked on one-on-one with the customerto be transmitted to the customer; the produced services to be transmitted to the customer in detail by transmitting the names of the services in a way that the customers can pronounce and understand.

22. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to display information with which technical services the services presented to the customer are presented and to enable services and applications to connect to each other.

23. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to comprise information with which infrastructure services the services are presented.

24. A system (1) according to any one of the preceding claims; characterized by the server (3) which is configured to be associated with the configuration elements in the product perspective, and to enable information about which feature in the services performs which function, and what type of configuration we need to establish by selecting which features to be detected.

Images