System, method, apparatus, and medium for net operations management cockpit

Abstract

The application provides a system, a method, equipment and a medium for a network point operation management cockpit, relates to the technical field of data processing, and comprises the following: a dispatch batch processing server module: logical programs of a database are run through batch running, and data from different systems is loaded into a database server; a server module, the application can solve the problem of displaying different time periods, different indexes and different display modes of a network point on a same screen, and achieves the purpose of unified supervision of network point operation, management and real-time data, and timely monitoring of abnormal conditions; and a Web server module: a developed cockpit is registered on a page of a Web server for display.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically, to a system, method, device, and medium for a branch operation management dashboard. Background Technology

[0002] Under the new normal of the economic environment, our bank faces pressure from rising operating costs and declining profits. To cope with the new economic situation, our bank has proposed a branch network intelligentization strategy. The main objectives are to reduce costs, improve efficiency, and ultimately achieve refined branch network management. Meanwhile, our bank's community banking construction is progressing steadily, and the number of branches is rapidly expanding. However, this fundamental channel for our business development has consistently lacked the support of management system tools. This project uses quantitative analysis to achieve digital operation of branches, improve branch employee efficiency, employee experience, and branch effectiveness, thereby enhancing branch performance.

[0003] In summary, the existing technologies have the following shortcomings: due to the low version of Yonghong server, the existing technologies have significant compatibility issues. In addition, the Yonghong server cluster uses a Windows operating system and has a small number of servers, which results in a slow opening of the management dashboard. The new management dashboard uses a Linux system, increases the number of clusters, and adds some customized operations, which makes the reports open and display quickly. Furthermore, the report control selection is also richer than that of the old system. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a system, method, device, and medium for a branch operation management dashboard.

[0005] According to the present invention, a system, method, device, and medium for a branch operation management dashboard are provided, the solution of which is as follows:

[0006] Firstly, a system for a branch operation management dashboard is provided, the system comprising:

[0007] Oracle Database Module: The Oracle database stores a large amount of interface data that subscribes to data from upstream sources. After being processed by stored procedures, the required data is loaded into a summary table that is updated daily, monthly, or yearly.

[0008] Redis Real-Time Server Module: Unlike traditional Oracle databases, Redis is a log-based, key-value database. The upstream continuously pushes data files to the real-time server, which then uses a Java program to retrieve, parse, and display the data. Yonghong server receives the data from the Redis server through a customized data source.

[0009] The batch processing server module schedules data from different systems into the summary layer tables of the Oracle database module by running the database logic program in batch mode.

[0010] The Yonghong server module includes: establishing a data source connection to the database server and defining the fields and their types according to the designed logical statements; connecting batch data to the Yonghong server's data mart through the data source; establishing a near real-time Redis data source; and developing a dashboard interface based on the defined data source.

[0011] Web server module: Registers the developed dashboard onto the web server's page.

[0012] Preferably, the page in the web-side server module that registers the cockpit to the web server includes:

[0013] 1) Configure the cockpit path parameter information in the configuration parameter table of the database. This way, the front-end page can view the developed cockpit display interface, or the industry leaders with account permissions can directly register and manage the relevant information of the cockpit in the corresponding directory of the Web front-end page.

[0014] 2) Load the cockpit's attribute information from the database, and view the cockpit information through the front end after authorization.

[0015] Preferably, the Yonghong server module includes: a display interface for developing a management dashboard; after the data preparation work of the management dashboard is loaded in the Oracle database summary layer, it needs to access the data source in the Yonghong server via JDBC.

[0016] Create a dataset, write the corresponding logical statements and date parameters, including the start date and end date; if the data can be refreshed, it means that the dataset connection is successful, and a data mart schedule is established, which depends on the established data source;

[0017] Configure a new data mart, define the data mart's name, parameters, folder, interface class name, and other relevant parameters, and then verify whether the data mart scheduling can run successfully.

[0018] Preferably, the verification of whether the marketplace scheduling can run successfully includes: if it runs successfully, the script program needs to be run on the Yonghong server on the Oracle database server according to the developed shell script and the relevant parameters including the date and scheduling file name;

[0019] If the operation is successful and the data in the data mart is verified to be correct, it means that the data mart has been successfully established. Then, configure the batch program in the scheduling service module. After successful configuration, the batch program will run automatically at the set frequency. Finally, enter the editing page of the management dashboard.

[0020] Secondly, a method for a branch operation management dashboard is provided, the method comprising:

[0021] Oracle database steps: A large amount of interface data for subscribing to data upstream is stored in the Oracle database. After being processed by stored procedures, the required data is loaded into a summary table that is updated daily, monthly, or yearly.

[0022] Redis Real-Time Server Steps: Unlike traditional Oracle databases, Redis is a log-based, key-value database. Upstream servers continuously push data files to the real-time server daily. A Java program then retrieves, parses, and displays the data. The Yonghong server receives the data from the Redis server through a customized data source.

[0023] The steps for scheduling a batch processing server are as follows: By running the database logic program in batch mode, data from different systems is loaded into the summary layer tables of the Oracle database module;

[0024] The steps for using the Yonghong server include: establishing a data source connection to the database server and defining the fields and their types according to the designed logical statements; inputting batch data into the Yonghong server's data mart through the data source; establishing a near real-time Redis data source; and developing the dashboard's interface based on the defined data source.

[0025] Web server steps: Register the developed dashboard on the web server's page.

[0026] Preferably, the step of registering the cockpit to the web server page includes:

[0027] 1) Configure the cockpit path parameters in the database configuration parameter table. This way, the front-end page can view the developed cockpit display interface, or an industry leader with account permissions can directly register and manage the cockpit-related information in the corresponding directory of the web front-end page.

[0028] 2) Load the cockpit's attribute information from the database, and view the cockpit information through the front end after authorization.

[0029] Preferably, the server-side steps include: developing a display interface for the management dashboard; after the data preparation work in the dashboard is loaded in the Oracle database summary layer, it needs to be connected to the database via JDBC.

[0030] Create a dataset, write the corresponding logical statements and date parameters, including the start date and end date; if the data can be refreshed, it means that the dataset connection is successful, and a data mart schedule is established, which depends on the established data source;

[0031] Configure a new data mart, define the data mart's name, parameters, folder, interface class name, and other relevant parameters, and then verify whether the data mart scheduling can run successfully.

[0032] Preferably, the verification of whether the marketplace scheduling can run successfully includes: if it runs successfully, the script program needs to be run on the Oracle database server according to the developed shell script and the relevant parameters including the date and scheduling file name;

[0033] If the operation is successful and the data in the data mart is verified to be correct, it means that the data mart has been successfully established. Then, configure the batch program in the scheduling service module. After successful configuration, the batch program will run automatically at the set frequency. Finally, enter the editing page of the management dashboard.

[0034] Thirdly, a computer-readable storage medium storing a computer program is provided, which, when executed by a processor, implements the method steps of the network operation management cockpit.

[0035] Fourthly, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the method steps of the network operation management cockpit.

[0036] Compared with the prior art, the present invention has the following beneficial effects:

[0037] This invention solves the problem of displaying different time periods, indicators, and display methods of outlets on the same screen by using visualization module tool controls provided in the server, thereby achieving the purpose of unified supervision of outlet operation, management, and real-time data, and timely monitoring of abnormal situations.

[0038] Other beneficial effects of the present invention will be explained in detail through the introduction of specific technical features and technical solutions in specific embodiments. Those skilled in the art should be able to understand the beneficial technical effects brought about by these technical features and technical solutions through the introduction of these technical features and technical solutions. Attached Figure Description

[0039] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0040] Figure 1 This is a system framework diagram of the present invention;

[0041] Figure 2 This is a circular diagram illustrating the effect of the cockpit management system of this invention. Detailed Implementation

[0042] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0043] This invention provides a system for a branch operation management dashboard, offering a solution for real-time, continuous monitoring of branch operations and management data across the entire bank, as well as displaying the same data in different formats, including maps, heatmaps, Nightingale rose diagrams, stacked diagrams, and instrument displays. (See also...) Figure 1 As shown, the system specifically includes:

[0044] Oracle Database Module: The Oracle database stores a large amount of interface data that subscribes to data from upstream sources. After being processed by stored procedures, the required data is loaded into a summary table that is updated daily, monthly, or yearly.

[0045] The Redis Real-Time Server module differs from traditional Oracle databases in that it's a log-based, key-value database. Data files are continuously pushed to the real-time server from upstream sources, and a Java program retrieves, parses, and displays the data. The Yonghong server then receives the data from the Redis server through a customized data source.

[0046] Scheduling batch processing server module:

[0047] By running the database logic program in batch mode, data from different systems is automatically loaded into the summary layer tables in the Oracle database server. This dashboard uses 6 summary tables, so 6 schedulers need to be configured.

[0048] Yonghong server module:

[0049] The server-side modules consist of four parts: First, establishing a data source connection to the database server and defining the fields and their types according to the designed logical statements. Second, connecting the batch processing data to the Yonghong server's data mart via the data source. Third, establishing a near real-time Redis data source. Fourth, developing a dashboard interface based on the defined data sources.

[0050] The core module of the development and management dashboard involves data preparation. After loading the Oracle database aggregation layer, the dashboard connects to the database via JDBC. Then, a dataset is created, and corresponding logical statements and date parameters, including start and end dates, are written. Refreshing the page displays the data, indicating a successful dataset connection. A data mart scheduler is then established, relying on the established data source. After configuring the new data mart, defining its name, parameters, folder, and interface class name, the scheduler can be manually verified to ensure successful operation.

[0051] Web server module:

[0052] Once the developed management dashboard is registered on the web server, its display can be viewed through the web front-end page. There are two ways to register the dashboard on the web page: First, configure the dashboard's path and other information in the database configuration parameter table. This allows the front-end page to view the developed dashboard interface, or authorized managers can directly register the management dashboard's information in the corresponding directory on the web front-end page. Second, load the dashboard's attribute information into the database configuration table, and then, after authorization, view the dashboard information through the front-end.

[0053] If the operation is successful, you need to run the script on the database server using the developed shell script, based on parameters such as date and scheduling file name. If the script runs successfully and the data mart data is verified to be correct, the mart has been successfully established. The next step is to configure the batch processing program in the scheduling service module. After successful configuration, the batch processing can be run automatically at the set frequency. Finally, you will enter the editing page of the management dashboard. This section includes 9 modules, arranged from left to right and top to bottom as follows: top left, center left, bottom left, top center, center, bottom center, top right, center right, and bottom right. The overall background is dark black and filled with starry blue. The overall resolution is 1366×768. In the top left area, there is a line chart with the horizontal axis representing the date and the vertical axis representing the quantity. The title is "Total Network Data," and this control shows the trend of the total number of network points over time.

[0054] The area in the left center is a ring diagram (see...) Figure 2The chart displays year-on-year comparisons of branch area, with the horizontal axis representing branch type and the vertical axis representing area. Different types are colored differently to visually show the varying areas occupied by different branch types. The lower left is a bar chart titled "Branch Revenue and Year-on-Year Comparison," with the horizontal axis representing time and the vertical axis showing revenue and year-on-year changes. The graph visually displays the trend of branch revenue and its growth rate over time. The upper middle section, titled "Branch Management Dashboard," displays the branch management dashboard. The center features a map showing the company's operating data for all its branches nationwide, with data sizes differentiated by color. The lower middle section provides a summary overview of the branches, titled "Overview Indicators," which summarizes several... The key metrics for each branch are arranged horizontally, allowing for a clear overview of the most important data. The upper right corner features a graph control with time on the horizontal axis and revenue and profit on the vertical axis, titled "Branch Revenue and Profit Trend Chart," providing a visual representation of how these figures change over time. The middle right corner displays a pie chart titled "Percentage of Branch Types," with branch type on the horizontal axis and profit on the vertical axis. Different types are colored differently, allowing for easy identification of the most profitable branch type based on the pie chart's size. The lower right corner contains a table, a revenue and profit table with three fields: year, revenue, and profit. The table data can be scrolled. The entire layout of the management dashboard is shown above. Background graphics for each heading contribute to a unified layout.

[0055] This invention also provides a method for a branch operation management dashboard, comprising:

[0056] The steps for scheduling a batch processing server are as follows: By running the database logic program in batch mode, data from different systems is loaded into the database server.

[0057] The steps of registering the cockpit to the web server page include:

[0058] 1) Register directly in the directory of the front-end page;

[0059] 2) Load the cockpit's attribute information from the database, and view the cockpit information through the front end after authorization.

[0060] The server-side steps include: developing the display interface of the management dashboard; after the data preparation work in the dashboard is loaded in the Oracle database summary layer, it needs to be connected to the database via JDBC.

[0061] Create a dataset, write the corresponding logical statements and date parameters, including the start date and end date; if the data can be refreshed, it means that the dataset connection is successful, and a data mart schedule is established, which depends on the established data source;

[0062] Configure a new data mart, define the data mart's name, parameters, folder, interface class name, and other relevant parameters, and then verify whether the data mart scheduling can run successfully.

[0063] Verifying whether the marketplace scheduling can run successfully includes: If it runs successfully, the script program needs to be run on the Oracle database server according to the developed shell script, based on the relevant parameters including the date and scheduling file name.

[0064] If the operation is successful and the data in the data mart is verified to be correct, it means that the data mart has been successfully established. Then, configure the batch program in the scheduling service module. After successful configuration, the batch program will run automatically at the set frequency. Finally, enter the editing page of the management dashboard.

[0065] This invention provides a system, method, device, and medium for a branch operation management dashboard. By employing a visualization module tool that allows users to independently select and combine different data, it solves the problem of displaying different time periods, indicators, and display methods of branches on the same screen, thereby achieving the goal of unified supervision of branch operation, management, and real-time data, and timely monitoring of abnormal situations.

[0066] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0067] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A system for a mesh point operations management cockpit, characterized by, Comprise: Oracle database module: a large number of upstream subscription data interface data are stored in the oracle database, and the required data is loaded into a summary layer table updated by day, month or year frequency after being processed by a stored procedure; Redis real-time server module: the Redis server is different from the traditional database of oracle. The server is a log type, Key-Value database. The upstream will continuously push data files to the real-time server every day, and then the Java program is used to obtain and parse the data file and display the data. The eternal flood server receives the data in the Redis server through the customized data source; Scheduling batch processing server module: load the data from different systems into the summary layer table of the oracle database module by running the logical program of the database; Eternal flood server module: including establishing a data source to connect the database server and defining the fields and their types used according to the designed logical statement; Access the batch data to the data mart of the eternal flood server through the data source; Establish a redis quasi-real-time data source; develop the cockpit development interface display according to the defined data source; Web server module: register the developed cockpit to the page of the web server; The cockpit is registered to the page of the web server in the web server module, comprising: 1) configure the path parameter information of the cockpit in the configuration parameter table of the database, so that the front-end page can view the developed cockpit display interface or the relevant information of the cockpit registered and managed by the line leader with account permission in the corresponding directory of the web front-end page; 2) load the attribute information of the cockpit in the database, and view the cockpit information through the front-end after authorization; The eternal flood server module comprises: developing a cockpit display interface, managing the data preparation work of the cockpit, loading the data in the oracle database summary layer, and then accessing the data source in the eternal flood server through JDBC; Create a data set, write corresponding logical statements and date parameters, including start date and end date; if the data set connection is successful, the data mart scheduling is established, which depends on the built data source; Configure a new data mart, define the name, parameters, folder, interface class name and other related parameters of the data mart, and verify whether the mart scheduling can run successfully; The verification whether the mart scheduling can run successfully comprises: if the running is successful, the oracle database server is run according to the developed shell script, the date, the scheduling file name and other related parameters on the eternal flood server; If the running is successful, and the data of the data mart is also verified to be correct, it means that the mart is successfully established, then configure the batch program in the scheduling service module, configure successfully, and automatically run the batch according to the set frequency, and finally enter the editing page of the cockpit management.

2. A method of mesh point operations management cockpit, characterized in that, Comprise: Oracle database step: a large number of interface data of upstream subscription data are stored in the oracle database, and the required data is loaded into a summary layer table updated by day, month or year frequency after being processed by a stored procedure; Redis real-time server step: the Redis server is different from the traditional oracle database, which is a log-type, Key-Value database, and the upstream continuously pushes data files to the real-time server every day, and then a Java program is used to acquire and parse the data files and display the data; the Yonghong server receives the data in the Redis server through a customized data source; Scheduling batch processing server step: the logical program of the database is run to load the data from different systems into the summary layer table of the oracle database module; Yonghong server step: including establishing a data source to connect the database server and defining the fields and their types used according to the designed logical statement; Through the data source, the data of the run batch is connected to the data mart of the Yonghong server; Establish a redis quasi-real-time data source; develop the cockpit development interface display according to the defined data source; Web server step: register the developed cockpit on the page of the web server; The cockpit registration on the page of the web server in the web server step includes: 1) configure the path parameter information of the cockpit in the configuration parameter table of the database, so that the front-end page can view the developed cockpit display interface or the in-line leader with account permission can directly register and manage the related information of the cockpit in the corresponding directory of the web front-end page; 2) load the attribute information of the cockpit in the database, and view the cockpit information through the front-end after authorization; The server step includes: developing a cockpit display interface, and the data preparation work of the cockpit is loaded in the oracle database summary layer, and then the JDBC mode is used to access the database; Create a data set, write corresponding logical statements and date parameters, including start date and end date; if the data set can be refreshed, it means that the data set connection is successful, the data mart scheduling is established, and it depends on the built data source; Configure a new data mart, define the name, parameters, folder, interface class name and other related parameters of the data mart, and verify whether the mart scheduling can run successfully; The verification of whether the mart scheduling can run successfully includes: if it runs successfully, the oracle database server needs to run the script program according to the developed shell script, the date, the scheduling file name and other related parameters on the oracle database server; If it runs successfully and the data of the data mart is also verified to be correct, it means that the data mart is successfully established, then the run batch program is configured in the scheduling service module, after the configuration is successful, the automatic run batch is performed according to the set frequency, and finally the cockpit management editing page is entered.

3. A computer readable storage medium storing a computer program, characterized in that, The computer program is executed by the processor to realize the method steps of the network point operation management cockpit of claim 2.

4. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The computer program, which is executed by a processor, implements the method steps of the web operation management cockpit according to claim 2.

Images