Full-link end-to-end scheduling detection method and system

Through the full-link end-to-end scheduling detection method and system, the problem of lengthy monthly completion process and lack of automated monitoring of the new IFRS17 standard is solved, automatic process execution and data accuracy are achieved, and manual intervention and costs are reduced.

CN119515550APending Publication Date: 2025-02-25SUNSHINE LIFE INSURANCE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411188496.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2025-02-25

AI Technical Summary

Technical Problem

The monthly completion process of the new IFRS17 standard is lengthy, lacks automated monitoring and early warning mechanisms, the reporting and summary process is cumbersome, and the system connection depends on manual notification, which wastes manpower.

Method used

Provides a full-link end-to-end scheduling detection method and system, integrating requirements rule configuration, process execution scheduling, and message warning to realize automatic scheduling, verification and reminding of system tasks.

Benefits of technology

Through the process configurability and automatic execution, the monthly process efficiency is improved, manual intervention is reduced, data accuracy and consistency is improved, and costs are reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119515550A_ABST
    Figure CN119515550A_ABST
Patent Text Reader

Abstract

The invention provides a full-link end-to-end scheduling detection method and a full-link end-to-end scheduling detection system. The full-link end-to-end scheduling detection method comprises the following steps: managing a module; the process is managed; and managing the plan. According to the technical scheme, the modules are managed; the process is managed; the plan is managed; the flow configurability is realized, and a user can flexibly customize the monthly settlement flow according to different requirements, so that the working efficiency and the user experience are improved; in addition, monthly settlement automatic execution is realized: efficiency is improved, manual intervention of personnel is reduced, and a monthly settlement process is rapidly and accurately completed; interference of human factors is reduced, errors generated during manual operation are avoided, and data accuracy and consistency are improved; cost is reduced, manpower and time cost are saved, automatic execution can be carried out at a certain frequency within a specified time, and timeliness and stability of the process are guaranteed.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0002] The implementation of IFRS17 and the new insurance contract standards can promote financial reports to better reflect the operating substance and operating quality of insurance companies, and achieve consistency and comparability of insurance companies' financial statements. Life insurance officially switched to the new IFRS17 standard on January 1, 2023. After the standard switch, the monthly settlement process has undergone disruptive changes, posing new challenges to the company's system construction, data management and other work.

[0003] In the current IFRS17 business and system architecture, the IFRS17 data processing platform is at the core, storing and processing all basic source tables and processing process data required by the IFRS17 business model, and completing the data interaction responsibilities between the Hadoop cluster, the actuarial system Prophet, the measurement platform, the accounting engine and other systems.

[0004] The IFRS17 data processing platform mainly writes stored procedures based on the PostgreSQL relational database to complete the data processing of the IFRS17 basic business modules; the stored procedures are configured in modules to the Apache DolphinScheduler tool, and the parameters are entered monthly for manual execution; data collection and notifications between system interactions are completed manually.

[0005] So far, the monthly settlement of the new life insurance standard has been in operation for several months, and in actual operation, problems that need to be improved have been exposed:

[0006] 1. The monthly settlement process is lengthy. The new monthly settlement standard requires a large number of system tasks to support numerous interactive links; dependent tasks cannot be run in parallel;

[0007] 2. Lack of automated monitoring and early warning mechanisms, heavy reliance on manual operations, and inability to promptly detect and handle abnormal situations during the monthly settlement process;

[0008] 3. The reporting and summary process of monthly results is cumbersome and requires manual sorting and filling of a large number of forms, which is prone to errors and omissions;

[0009] 4. Important systems such as data platforms, measurement platforms, and accounting engines frequently interact with each other, but the interaction relies on manual notification and is not managed in a unified manner, wasting a lot of manpower. Summary of the invention

[0010] The present application provides a full-link end-to-end scheduling detection method and system, which is used to establish a system platform integrating demand rule configuration, process execution scheduling, and message warning, to achieve automatic scheduling, verification and reminder of system tasks, improve system operation efficiency, and reduce manual intervention.

[0011] In a first aspect, a full-link end-to-end scheduling detection method is provided, comprising the following steps:

[0012] Manage modules;

[0013] Manage the process;

[0014] Manage the plan.

[0015] In the above technical solution, by managing the modules, processes and plans, the process is made configurable: currently the monthly settlement process mainly relies on manual scheduling and production, which requires the cooperation of various business and IT personnel. Through process configuration, users can flexibly customize the monthly settlement process according to different needs, thereby improving work efficiency and user experience; in addition, automatic execution of monthly settlement is achieved: improving efficiency, reducing manual intervention of personnel, and completing the monthly settlement process quickly and accurately; reducing interference from human factors, avoiding errors in manual operations, and improving data accuracy and consistency; reducing costs, saving manpower and time costs, and can be automatically executed at a certain frequency within a specified time to ensure the timeliness and stability of the process.

[0016] In a specific embodiment, it also includes:

[0017] Manage demand.

[0018] In a specific implementation scheme, the steps of managing the modules include:

[0019] Define the module information;

[0020] Defines dependencies between modules.

[0021] In a specific implementation plan, the steps for managing the process are as follows:

[0022] Select the module under different processes.

[0023] In a specific implementation plan, the steps for managing the plan include:

[0024] Select the process plan to be executed in the evaluation month according to the actual situation, and fill in the estimated start time of the process plan in the current evaluation month as well as the required parameters and parameter values;

[0025] Based on the relationship between the process and the modules and the earliest estimated start time of the module configuration from the total plan, the estimated start time and the estimated end time of each module are calculated, and finally a schedule is generated.

[0026] In a specific implementation plan, the module information includes the module business manager, IT liaison person, operation content, operation method, and the earliest estimated start time of the entire monthly settlement.

[0027] In a specific implementation plan, the steps for managing demand are as follows:

[0028] Complete the creation of requirements and the configuration of rules corresponding to the requirements.

[0029] In a specific embodiment, it also includes:

[0030] Manage the audit and complete the rules in pre-production task management to publish the production environment.

[0031] In a specific embodiment, it also includes:

[0032] Manage production tasks and record rules that can be executed in the production environment;

[0033] Manage task scheduling and complete task execution.

[0034] In a second aspect, a full-link end-to-end scheduling detection system is provided, including:

[0035] Module management subsystem, used to manage modules;

[0036] Process management subsystem, used to manage the process;

[0037] The plan management subsystem is used to manage the plan.

[0038] In the above technical solution, by managing the modules, processes and plans, the process is made configurable: currently the monthly settlement process mainly relies on manual scheduling and production, which requires the cooperation of various business and IT personnel. Through process configuration, users can flexibly customize the monthly settlement process according to different needs, thereby improving work efficiency and user experience; in addition, automatic execution of monthly settlement is achieved: improving efficiency, reducing manual intervention of personnel, and completing the monthly settlement process quickly and accurately; reducing interference from human factors, avoiding errors in manual operations, and improving data accuracy and consistency; reducing costs, saving manpower and time costs, and can be automatically executed at a certain frequency within a specified time to ensure the timeliness and stability of the process. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A flowchart of a full-link end-to-end scheduling detection method provided in an embodiment of the present application;

[0040] Figure 2 A structural block diagram of a full-link end-to-end scheduling detection system provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of the main contents of the IFRS17 platform construction provided for the embodiment of this application;

[0042] Figure 4 A structural diagram of the main contents of the IFRS17 platform construction provided in the embodiment of the present application;

[0043] Figure 5 A schematic diagram of a specific process of the full-link end-to-end scheduling detection method provided in an embodiment of the present application;

[0044] Figure 6 A core flow diagram of the full-link end-to-end scheduling detection method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The present application is further described in detail below through the accompanying drawings and embodiments. Through these descriptions, the characteristics and advantages of the present application will become clearer and more specific.

[0046] The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. Although various aspects of the embodiments are shown in the drawings, the drawings are not necessarily drawn to scale unless otherwise noted.

[0047] In addition, the technical features involved in different embodiments of the present application described below can be combined with each other as long as they do not conflict with each other.

[0048] To facilitate understanding of the full-link end-to-end scheduling detection method and system provided in the embodiment of the present application, its application scenario is first explained. The full-link end-to-end scheduling detection method and system provided in the embodiment of the present application are used to establish a system platform that integrates demand rule configuration, process execution scheduling, and message warning, so as to realize automatic scheduling, verification and reminder of system tasks, improve system operation efficiency, and reduce manual intervention. The implementation of IFRS17 and the new insurance contract standards can promote financial reports to better reflect the operating substance and operating quality of insurance companies, and achieve consistency and comparability of insurance companies' financial statements. Life insurance officially switched to the new IFRS17 standard from January 1, 2023. After the standard switch, the monthly settlement process has undergone disruptive changes, which has posed new challenges to the company's system construction, data management and other work. In the current IFRS17 business and system architecture, the IFRS17 data processing platform is in a core position, storing and processing all basic source tables and processing process data required by the IFRS17 business model, and completing the data interaction responsibilities between systems such as the hadoop cluster, the actuarial system Prophet, the measurement platform, and the accounting engine. The IFRS17 data processing platform mainly writes stored procedures based on the PostgreSQL relational database to complete the data processing of the IFRS17 basic business modules; configures the stored procedures into modules and manually executes them by entering parameters every month; and manually completes data collection and notifications between system interactions. Up to now, the monthly settlement of the new life insurance standard has been running for several months, and in actual operation, it has also exposed problems that need to be improved: 1. The monthly settlement process is lengthy. The monthly settlement of the new standard requires a large number of system tasks to support many interactive links; the existence of dependent tasks makes it impossible to parallelize; 2. There is a lack of automated monitoring and early warning mechanisms, and a large amount of reliance on manual operations, and abnormal situations in the monthly settlement process cannot be discovered and handled in time; 3. The reporting and summary process of the monthly settlement results is cumbersome, and a large number of forms need to be manually sorted and filled in, which is prone to errors and omissions; 4. The data platform, measurement platform, accounting engine and other important systems frequently interact with each other, but the connection relies on manual notification and is not uniformly managed, wasting a lot of manpower. To this end, the embodiment of the present application provides a full-link end-to-end scheduling detection method and system to establish a system platform integrating demand rule configuration, process execution scheduling, and message warning, so as to realize automatic scheduling, verification and reminder of system tasks, improve system operation efficiency, and reduce manual intervention. The following is a detailed description of the embodiment in conjunction with specific drawings.

[0049] refer to Figures 1 to 6 , Figure 1 A flowchart of a full-link end-to-end scheduling detection method provided in an embodiment of the present application; Figure 2 A structural block diagram of a full-link end-to-end scheduling detection system provided in an embodiment of the present application; Figure 3A schematic diagram of the main contents of the IFRS17 platform construction provided for the embodiment of this application; Figure 4 A structural diagram of the main contents of the IFRS17 platform construction provided in the embodiment of the present application; Figure 5 A schematic diagram of a specific process of the full-link end-to-end scheduling detection method provided in an embodiment of the present application; Figure 6 A core flow diagram of the full-link end-to-end scheduling detection method provided in an embodiment of the present application.

[0050] exist Figure 1 In the embodiment of the present application, a full-link end-to-end scheduling detection method is provided, comprising the following steps:

[0051] Manage modules;

[0052] Manage the process;

[0053] Manage the plan.

[0054] In the above technical solution, by managing the modules, processes and plans, the process is made configurable: currently the monthly settlement process mainly relies on manual scheduling and production, which requires the cooperation of various business and IT personnel. Through process configuration, users can flexibly customize the monthly settlement process according to different needs, thereby improving work efficiency and user experience; in addition, automatic execution of monthly settlement is achieved: improving efficiency, reducing manual intervention of personnel, and completing the monthly settlement process quickly and accurately; reducing interference from human factors, avoiding errors in manual operations, and improving data accuracy and consistency; reducing costs, saving manpower and time costs, and can be automatically executed at a certain frequency within a specified time to ensure the timeliness and stability of the process.

[0055] Specifically, refer to Figures 3 to 6 IFRS17 platform construction is mainly divided into two parts: platform construction and process rule construction. The main contents are as follows: Figure 3 and Figure 4 As shown in the figure, a system platform integrating demand rule configuration, process execution scheduling, and message warning has been established to realize automatic scheduling, verification, and reminder of system tasks, improve system operation efficiency, and reduce manual intervention.

[0056] In a specific embodiment, it also includes:

[0057] Manage demand.

[0058] In a specific implementation scheme, the steps of managing the modules include:

[0059] Define the module information;

[0060] Defines dependencies between modules.

[0061] In a specific implementation plan, the steps for managing the process are as follows:

[0062] Select the module under different processes.

[0063] In a specific implementation plan, the steps for managing the plan include:

[0064] Select the process plan to be executed in the evaluation month according to the actual situation, and fill in the estimated start time of the process plan in the current evaluation month as well as the required parameters and parameter values;

[0065] Based on the relationship between the process and the modules and the earliest estimated start time of the module configuration from the total plan, the estimated start time and the estimated end time of each module are calculated, and finally a schedule is generated.

[0066] In a specific implementation plan, the module information includes the module business manager, IT liaison person, operation content, operation method, and the earliest estimated start time of the entire monthly settlement.

[0067] In a specific implementation plan, the steps for managing demand are as follows:

[0068] Complete the creation of requirements and the configuration of rules corresponding to the requirements. That is, the requirements are bound to the workflow, and specific rules are configured by category (stored process category, verification category, collection category, data write-back category, etc.) in the workflow. At the same time, the data table achieves the purpose of data isolation by dynamically assembling the year, month and version, and supports the configuration of rules with different syntaxes such as Spark SQL, Hive SQL, Shell, PostgreSQL, etc.; select the module to which it belongs when saving.

[0069] Specifically, the content of demand management is mainly the demand rule configuration system, including: configuration of business requirements and demand implementation rules; system task configuration, mainly including data processing rules, data verification rules, report file generation rules, system exception verification rules; task dependency configuration, after the dependent event is completed, the downstream task is started.

[0070] In a specific embodiment, it also includes:

[0071] Manage the audit and complete the rules in the pre-production task management to publish the production environment. Realize the visualization of the monthly settlement progress: the overall progress of the process can be monitored and controlled to improve the controllability of the process, and a process completion report can be provided to facilitate business management and decision-making.

[0072] In a specific embodiment, it also includes:

[0073] Manage production tasks and record rules that can be executed in the production environment.

[0074] Specifically, it also includes a message warning system, including: delay risk reminder: reminder for deviations between expected time and actual time; verification result reminder: reminder for verification results exceeding the threshold and not within the expected range; progress and exception reminder: reminder for key progress and abnormal tasks. Customized message reminder templates for different reminder contents. Message content is dynamically generated according to actual conditions. The interface customizes the message notification type, subject, and recipient, dynamically generates notification content information, and sends different warning reminders in real time.

[0075] Manage task scheduling and complete task execution. Differentiate between different environments and execute all tasks with one click through the Quartz scheduled task framework.

[0076] Specifically, the management of task scheduling mainly involves the task process scheduling configuration system, including: after the monthly settlement start time is determined, the system's defined preset process template is selected to output the estimated time for tasks at all levels and automatically generate a schedule; the tasks and time can be manually adjusted and confirmed, and the final execution plan is automatically generated; the system automatically runs each task program according to the final schedule; when the actual system time is better than expected, the schedule has a version update function; when an abnormality occurs during the task execution and it needs to be re-run, the system automatically records the execution.

[0077] exist Figure 2 In the embodiment of the present application, a full-link end-to-end scheduling detection system is also provided, including:

[0078] Module management subsystem, used to manage modules;

[0079] Process management subsystem, used to manage the process;

[0080] The plan management subsystem is used to manage the plan.

[0081] In the above technical solution, by managing the modules, processes and plans, the process is made configurable: currently the monthly settlement process mainly relies on manual scheduling and production, which requires the cooperation of various business and IT personnel. Through process configuration, users can flexibly customize the monthly settlement process according to different needs, thereby improving work efficiency and user experience; in addition, automatic execution of monthly settlement is achieved: improving efficiency, reducing manual intervention of personnel, and completing the monthly settlement process quickly and accurately; reducing interference from human factors, avoiding errors in manual operations, and improving data accuracy and consistency; reducing costs, saving manpower and time costs, and can be automatically executed at a certain frequency within a specified time to ensure the timeliness and stability of the process.

[0082] Those skilled in the art will appreciate that the present application may be implemented as a system, method or computer program product.

[0083] Therefore, the present disclosure may be specifically implemented in the following forms, namely: it may be completely hardware, it may be completely software (including firmware, resident software, microcode, etc.), or it may be a combination of hardware and software, generally referred to herein as a "circuit", "module" or "system". In addition, in some embodiments, the present application may also be implemented in the form of a computer program product in one or more computer-readable media, and the computer-readable medium may contain computer-readable program code.

[0084] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0085] Although the embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art can change, modify, replace and modify the above embodiments within the scope of the present application. On this basis, a variety of replacements and improvements can be made to the present application, all of which fall within the scope of protection of the present application.

Claims

1. A full-link end-to-end scheduling detection method, characterized in that: The following steps are involved: Manage modules; Manage the process; Manage the plan.

2. The full-link end-to-end scheduling detection method according to claim 1, characterized in that: Also includes: Manage demand.

3. The full-link end-to-end scheduling detection method according to claim 2, characterized in that: The steps to manage modules include: Define the module information; Defines dependencies between modules.

4. The full-link end-to-end scheduling detection method according to claim 3, characterized in that: The steps to manage the process are as follows: Select the module under different processes.

5. The full-link end-to-end scheduling detection method according to claim 4, characterized in that: The steps to manage the plan include: Select the process plan to be executed in the evaluation month according to the actual situation, and fill in the estimated start time of the process plan in the current evaluation month as well as the required parameters and parameter values; Based on the relationship between the process and the modules and the earliest estimated start time of the module configuration from the total plan, the estimated start time and the estimated end time of each module are calculated, and finally a schedule is generated.

6. The full-link end-to-end scheduling detection method according to claim 5, characterized in that: The module information includes the module business manager, IT contact person, operation content, operation method, and the earliest estimated start time of the entire monthly settlement.

7. The full-link end-to-end scheduling detection method according to claim 6, characterized in that: The steps to manage demand are as follows: Complete the creation of requirements and the configuration of rules corresponding to the requirements.

8. The full-link end-to-end scheduling detection method according to claim 7, characterized in that: Also includes: Manage the audit and complete the rules in pre-production task management to publish the production environment.

9. The full-link end-to-end scheduling detection method according to claim 8, characterized in that: Also includes: Manage production tasks and record rules that can be executed in the production environment; Manage task scheduling and complete task execution.

10. A full-link end-to-end scheduling detection system, characterized in that: include: Module management subsystem, used to manage modules; Process management subsystem, used to manage the process; The plan management subsystem is used to manage the plan.