A system for performing business analysis

Abstract

The present invention relates to a system (1) which enables focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed.

Description

[0001] A SYSTEM FOR PERFORMING BUSINESS ANALYSIS

[0002] Technical Field

[0003] The present invention relates to a system which enables focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed.

[0004] Background of the Invention

[0005] Today, reports analyzed on daily and monthly statistics are collectively monitored on a single platform. In this way, it is enabled to be displayed collectively with weekly, monthly and yearly trend charts. It is ensured that anomalies are recognized, and different teams speak the same language. When there is a need for innovation, update or information sharing, it can be easily shared with the organization as all managers attend the meeting. These notifications need to be carried out in different mediums or meetings. Whereas teams used to be knowledgeable about the parts that are relevant to their business, it is necessary to ensure that everyone is knowledgeable about organization- wide critical issues.

[0006] For this reason, considering the studies and deficiencies included in the current technique, it is understood that there is a need for a system which enables focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed. The United States patent document no. US2007203740A1, an application included in the state of the art, discloses a system configured to measure performance, create tables with data, match problems with solutions and report on a daily or weekly basis, with defined parameters. An automated system and method provide a diagnosis and remedy to a business information system through a case matching process. From an initial model of a proposed system architecture, performance metrics are modelled and compared against a set of user-defined corporate and business requirements. The performance metrics include cost, quality of service and throughput. From these metrics and requirements, a business ephemeris or precalculated table can be produced, the business ephemeris cross referencing enterprise situation and remedy. From the ephemeris, cases can be generated to comprise characteristics, diagnosis and proposed solutions relating to states of the model or business information system. A matching engine matches a case to a state of the model or information system. The matching case can be employed to report a diagnosis and proposed remedial actions, as well as to implement remedial actions automatically. An offline mathematical modelling member provides feedback to further update the business ephemeris and case base.

[0007] Summary of the Invention

[0008] An object of the present invention is to realize a system developed for enabling focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed.

[0009] Detailed Description of the Invention

[0010] “A System for Performing Business Analysis” realized to fulfd the objective of the present invention is shown in the figure attached, in which: Figure 1 is a schematic view of the inventive system.

[0011] The components illustrated in the figure are individually numbered, where the numbers refer to the following:

[0012] 1. System

[0013] 2. Electronic device

[0014] 3. Interface

[0015] 4. Database

[0016] 5. Server

[0017] The inventive system (1) developed for enabling focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed comprises at least one electronic device (2) which is configured to exchange data by using any remote communication protocol and to run at least one application thereon; at least one interface (3) which is configured to be run on the electronic device (2); to enable data to be displayed and queries to be run thereon; at least one database (4) which is configured to keep a record of the data in raw form on various data storage platforms such as DB2, Oracle, MS SQL and Kibana; to keep a record of transaction statistics on DB2, business metrics on Oracle, JCL statistics on Microsoft SQL and metrics used for ARK on Kibana; at least one server (5) which is configured to establish connection with the electronic device (2) by using any communication protocol; and to establish communication with the interface (3) run on the electronic device (2) through this established connection; to access data on the database (4); and to save data on the database (4); to import data from source tables via various scripts into much smaller tables where only the information to be presented is kept; to get the necessary data into QLIK by sending queries to data sources; at the same time, to enable the data to become visible if there is a need to merge data from different platforms by performing such operations; to add radar week information to the tables; and to enable the data of the past radars to be seen by the users by using a selection field on the front side by means of this information; to enable the data to be stored in proprietary QVD files of QLIK after the final versions of the data are prepared; to add the new data coming in every week to these files end-to-end with the information of which radar (year / week) they belong to; to enable both the radars prepared on old dates to be preserved with QVD files and to enable the interface (3) to be quickly resulted by sending queries only to the result tables in QVD; to organize access to data sources by means of the use of QVDs; to memorize the QVD contents on the interface (3) via basic load commands; to make minor changes such as format-name changes only if needed, without making changes on the data; to enable the information to be reported on a weekly basis by receiving them in QLIK and converting into PDFs while the changes are still being made.

[0018] The electronic device (2) included in the inventive system (1) is configured to exchange data by using any remote communication protocol and to run at least one application thereon. The electronic device (2) is a device in the form of a desktop computer and / or portable computer. The electronic device (2) is configured to run the interface (3) thereon. The electronic device (2) is configured to establish connection with the server (5) by using any remote communication protocol included in the state of the art.

[0019] The interface (3) included in the inventive system (1) is configured to be run on the electronic device (2). The interface (3) is configured to enable data to be displayed and queries to be run thereon. The database (4) included in the inventive system (1) is configured to establish connection with the server (5). The database (4) is configured to keep a record of the data in raw form on various data storage platforms such as DB2, Oracle, MS SQL and Kibana. The database (4) is configured to keep a record of transaction statistics on DB2, business metrics on Oracle, JCL statistics on Microsoft SQL and metrics used for ARK on Kibana.

[0020] The server (5) included in the inventive system (1) is configured to establish connection with the electronic device (2) by using any communication protocol included in the state of the art, and to establish communication with the interface (3) run on the electronic device (2) through this established connection. The server (5) is configured to access data on the database (4) and to save data on the database (4). The server (5) is configured to import data from source tables via various scripts into much smaller tables where only the information to be presented is kept. The server (5) is configured to get the necessary data into QLIK by sending queries to data sources; at the same time, to enable the data to become visible if there is a need to merge data from different platforms by performing such operations; to add radar week information to the tables, and to enable the data of the past radars to be seen by the users by using a selection field on the front side by means of this information. The server (5) is configured to enable the data to be stored in proprietary QVD files of QLIK after the final versions of the data are prepared; to add the new data coming in every week to these files end-to- end with the information of which radar (year / week) they belong to; to enable both the radars prepared on old dates to be preserved with QVD files and to enable the interface (3) to be quickly resulted by sending queries only to the result tables in QVD. The server (5) is configured to organize access to data sources by means of the use of QVDs. The server (5) is configured to memorize the QVD contents on the interface (3) via basic load commands, and to make minor changes such as format-name changes only if needed, without making changes on the data. The server (5) is configured to enable the information to be reported on a weekly basis by receiving them in QLIK and converting into PDFs while the changes are still being made.

[0021] Industrial Application of the Invention

[0022] In the inventive system (1), the server (5) establishes connection with the electronic device (2) by using any communication protocol and establishes communication with the interface (3) run on the electronic device (2) through this established connection; accesses data on the database (4); and saves data on the database (4); imports data from source tables via various scripts into much smaller tables where only the information to be presented is kept; gets the necessary data into QLIK by sending queries to data sources; at the same time, enables the data to become visible if there is a need to merge data from different platforms by performing such operations; adds radar week information to the tables; and enables the data of the past radars to be seen by the users by using a selection field on the front side by means of this information; enables the data to be stored in proprietary QVD files of QLIK after the final versions of the data are prepared; adds the new data coming in every week to these files end-to-end with the information of which radar (year / week) they belong to; enables both the radars prepared on old dates to be preserved with QVD files and enables the interface (3) to be quickly resulted by sending queries only to the result tables in QVD; organizes access to data sources by means of the use of QVDs; memorizes the QVD contents on the interface (3) via basic load commands; makes minor changes such as format-name changes only if needed, without making changes on the data; enables the information to be reported on a weekly basis by receiving them in QLIK and converting into PDFs while the changes are still being made. Therefore, this enables focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed. Within these basic concepts; it is possible to develop various embodiments of the inventive “A System (1) for Performing Business Analysis”; the invention cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

CLAIMS1. A system (1) developed for enabling focal agendas of an organization to be visualized; the status of service infrastructures such as growth, bottlenecks and use of resources to be assessed; problems and solutions to be announced to the entire organisation; and automated reporting to be performed; comprising at least one electronic device (2) which is configured to exchange data by using any remote communication protocol and to run at least one application thereon; at least one interface (3) which is configured to be run on the electronic device (2); to enable data to be displayed and queries to be run thereon; at least one database (4) which is configured to keep a record of the data in raw form on various data storage platforms such as DB2, Oracle, MS SQL and Kibana; to keep a record of transaction statistics on DB2, business metrics on Oracle, JCL statistics on Microsoft SQL and metrics used for ARK on Kibana; and characterized by at least one server (5) which is configured to establish connection with the electronic device (2) by using any communication protocol; and to establish communication with the interface (3) run on the electronic device (2) through this established connection; to access data on the database (4); and to save data on the database (4); to import data from source tables via various scripts into much smaller tables where only the information to be presented is kept; to get the necessary data into QLIK by sending queries to data sources; at the same time, to enable the data to become visible if there is a need to merge data from different platforms by performing such operations; to add radar week information to the tables; and to enable the data of the past radars to be seen by the users by using a selection field on the front side by means of this information; to enable the data to be stored in proprietary QVD files of QLIK after the final versions of the data are prepared; to add the new data coming in every week to these files end-to-end withthe information of which radar (year / week) they belong to; to enable both the radars prepared on old dates to be preserved with QVD files and to enable the interface (3) to be quickly resulted by sending queries only to the result tables in QVD; to organize access to data sources by means of the use of QVDs; to memorize the QVD contents on the interface (3) via basic load commands; to make minor changes such as format-name changes only if needed, without making changes on the data; to enable the information to be reported on a weekly basis by receiving them in QLIK and converting into PDFs while the changes are still being made.

2. A system (1) according to Claim 1; characterized by the electronic device (2) which is a device in the form of a desktop computer and / or portable computer; and is configured to exchange data by using any remote communication protocol and to run at least one application thereon.

3. A system (1) according to Claim 1 or 2; characterized by the electronic device (2) which is configured to run the interface (3) thereon.

4. A system (1) according to Claim 3; characterized by the electronic device (2) which is configured to establish connection with the server (5) by using any remote communication protocol.

5. A system (1) according to any one of the preceding claims; characterized by the interface (3) which is configured to be run on the electronic device (2).

6. A system (1) according to any one of the preceding claims; characterized by the interface (3) which is configured to enable data to be displayed and queries to be run thereon.

7. A system (1) according to any one of the preceding claims; characterized by the database (4) which is configured to establish connection with the server (5).

8. A system (1) according to any one of the preceding claims; characterized by the database (4) which is configured to keep a record of the data in raw form on various data storage platforms such as DB2, Oracle, MS SQL and Kibana.

9. A system (1) according to any one of the preceding claims; characterized by the database (4) which is configured to keep a record of transaction statistics on DB2, business metrics on Oracle, JCL statistics on Microsoft SQL and metrics used for ARK on Kibana.

10. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to establish connection with the electronic device (2) by using any communication protocol, and to establish communication with the interface (3) run on the electronic device (2) through this established connection.

11. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to access data on the database (4) and to save data on the database (4).

12. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to import data from source tables via various scripts into much smaller tables where only the information to be presented is kept.

13. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to get the necessary data into QLIK by sending queries to data sources; at the same time, to enable the data to becomevisible if there is a need to merge data from different platforms by performing such operations; to add radar week information to the tables, and to enable the data of the past radars to be seen by the users by using a selection field on the front side by means of this information.

14. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to enable the data to be stored in proprietary QVD files of QLIK after the final versions of the data are prepared; to add the new data coming in every week to these files end-to-end with the information of which radar (year / week) they belong to; to enable both the radars prepared on old dates to be preserved with QVD files and to enable the interface (3) to be quickly resulted by sending queries only to the result tables in QVD.

15. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to organize access to data sources by means of the use of QVDs.

16. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to memorize the QVD contents on the interface (3) via basic load commands, and to make minor changes such as format-name changes only if needed, without making changes on the data.

17. A system (1) according to any one of the preceding claims; characterized by the server (5) which is configured to enable the information to be reported on a weekly basis by receiving them in QLIK and converting into PDFs while the changes are still being made.

Images