A method and system for integrating business data of multiple departments

Abstract

The present application relates to the technical field of multi-department business data management, and in particular to a method and system based on multi-department business data integration. It includes: obtaining the operating data of each department, generating multiple business flows according to the operating parameters, and generating business labels for each business flow; establishing a data analysis model, generating storage parameters for a single business flow according to a single business flow parameter and a data analysis model; establishing a business flow data call model, and setting call parameters according to real-time data call requirements and call models. By adding central storage data and multiple sub-data repositories, all data is pre-processed in the form of business flows and then distributedly stored, and the common data of a single business flow circulating between departments is extracted and stored separately, thereby avoiding data redundancy. At the same time, the dedicated data of each department is stored separately to ensure data security.

Description

Technical Field

[0001] The present application relates to the technical field of multi-department business data management, and in particular to a multi-department business data integration method and system. Background Art

[0002] With the popularization of information technology, integrated data processing platforms have also been derived based on information technology in enterprise management and operations. Their purpose is to help enterprises solve problems such as data clutter, data duplication, and data lag, so that enterprises can operate more coordinatedly. For enterprises with widely dispersed businesses and strong demands for data timeliness, data integration platforms are indispensable.

[0003] Existing enterprise data integration platforms mostly store data based on data warehouses, which serve as transit stations to achieve data interaction. However, this data warehouse is shared by all functional departments of the enterprise, and contains a large amount of duplicate data. There is a certain delay in the data calling process, and the exchange and update of business data are asynchronous or delayed. At the same time, due to the unified storage of data, the security of business data is low when interacting between departments, and department-specific information is easily stolen. Summary of the invention

[0004] The purpose of this application is to solve the above technical problems. This application provides a multi-department business data integration method and system, aiming to

[0005] In some embodiments of the present application, by adding a central storage data and multiple sub-data storage repositories, all data are pre-processed in the form of business flows and then distributedly stored, and the common data flowing between various departments in a single business flow is extracted and stored separately, thereby avoiding data redundancy. At the same time, the dedicated data of each department is stored separately to ensure data security.

[0006] In some embodiments of the present application, by establishing multiple calling models, a calling relationship between each data packet is established according to a single business flow, so as to quickly call the relevant data in a single business flow and reduce the latency of data calling. At the same time, by generating correlation evaluation values ​​between multiple business flows, related business flows are established to achieve fast calling between different business flow data.

[0007] In some embodiments of the present application, a multi-department business data integration method is provided, which is characterized by comprising:

[0008] Obtain the operation data of each department, generate multiple business flows according to the operation parameters, and generate business tags for each business flow;

[0009] Establish a data analysis model and generate storage parameters of a single business flow based on the single business flow parameters and the data analysis model;

[0010] Establish a business flow data call model and set call parameters based on real-time data call requirements and the call model.

[0011] In some embodiments of the present application, when generating storage parameters of a single service flow, the process includes:

[0012] Select a single business flow and generate the department flow order of the business flow according to the selected business flow parameters;

[0013] Generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and data to be processed of the business flow according to the data analysis model;

[0014] Obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department;

[0015] Generate a common data package, wherein the common data package includes: a business label of the business flow, a department flow order of the business flow, basic data of the business flow and data to be processed;

[0016] Generate multiple department-specific data packets, wherein the department-specific data packets include: an identity tag of the department, a service tag of the service flow, and processing data of the department;

[0017] Generate storage instructions for common data packages and department-specific data packages.

[0018] In some embodiments of the present application, when generating storage instructions for common data packets and department-specific data packets, the steps include:

[0019] Establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories;

[0020] Obtain the identity tags of all departments, and create a department-sub-data repository mapping table based on the identity tags and index tags;

[0021] generating encryption parameters for the central data repository;

[0022] Generate encryption parameters of corresponding sub-data repository according to department parameters;

[0023] storing the common data packet in a central data storage repository according to the primary storage instruction;

[0024] The identity tag in the department-specific data package is obtained according to the secondary storage instruction, the target sub-data repository is selected according to the identity tag and the department-sub-data repository mapping table, and the department-specific data package is stored in the target sub-data repository.

[0025] In some embodiments of the present application, when establishing a service flow data call model, it includes:

[0026] Obtain the common data packets of a single business flow and all department-specific data packets;

[0027] Establish a data association model for the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow;

[0028] Generate the calling permissions of each department according to the departmental flow order of the business flow;

[0029] A type of calling model is generated according to the data association model and the calling authority of each department.

[0030] In some embodiments of the present application, when establishing a business process data call model, it also includes:

[0031] Obtain all business flows and establish a business flow sequence A, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow;

[0032] Select the target business flow in sequence according to the business flow sequence A;

[0033] Establish a business flow correlation evaluation model;

[0034] Generate a relevance evaluation value of a target business flow according to a business flow relevance evaluation model;

[0035] Generate a correlation evaluation value sequence B=(b1,b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow;

[0036] A correlation evaluation value threshold is preset, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, the i-th business flow and the target business flow are set as associated business flows;

[0037] Generate a second type of call model based on all related business flows.

[0038] In some embodiments of the present application, when setting the call parameters, it includes:

[0039] Generate the number of business flows to be called and the calling department based on real-time data calling requirements;

[0040] If the calling business flow data is 1, the calling parameters are generated according to a type of calling model;

[0041] If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called;

[0042] If there are associated business flows, call parameters are generated for the associated business flows according to the second-class call model, and call parameters are generated for the remaining business flows to be called according to the first-class call model;

[0043] If there is no associated business flow, the calling parameters of each business flow to be called are generated according to a class of calling models.

[0044] In some embodiments of the present application, a multi-department business data integration system is provided, including:

[0045] The data collection unit is used to obtain the operation data of each department, generate multiple business flows according to the operation parameters, and generate business tags for each business flow;

[0046] A data integration unit is used to establish a data analysis model and generate storage parameters of a single business flow according to the single business flow parameters and the data analysis model;

[0047] The data calling unit is used to establish a business flow data calling model and set calling parameters according to real-time data calling requirements and the calling model.

[0048] In some embodiments of the present application, the data integration unit includes:

[0049] The first processing module is used to select a single business flow and generate a department flow order of the business flow according to the selected business flow parameters;

[0050] The second processing module is used to generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and the data to be processed of the business flow according to the data analysis model;

[0051] The third processing module is used to obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department;

[0052] A fourth processing module is used to generate a common data packet, wherein the common data packet includes: a business label of the business flow, a department flow order of the business flow, basic data of the business flow and data to be processed;

[0053] The fourth processing module is further used to generate a plurality of department-specific data packets, wherein the department-specific data packets include: an identity tag of the department, a service tag of the service flow and processing data of the department;

[0054] A storage module, used for generating storage instructions for common data packets and department-specific data packets;

[0055] The storage module is also used to establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories;

[0056] The storage module is also used to obtain identity tags of all departments and establish a department-sub-data storage library mapping table according to the identity tags and index tags;

[0057] The storage module is further used to store the common data packet in the central data storage according to the first-level storage instruction, obtain the identity tag in the department-specific data packet according to the second-level storage instruction, select the target sub-data storage according to the identity tag and the department-sub-data storage mapping table, and store the department-specific data packet in the target sub-data storage;

[0058] The encryption module is used to generate encryption parameters of the central data repository. The encryption module is also used to generate encryption parameters of corresponding sub-data repositories according to department parameters.

[0059] In some embodiments of the present application, the data calling unit includes:

[0060] The first modeling module is used to obtain the common data packets of a single business flow and all department-specific data packets;

[0061] The first modeling module is also used to establish a data association model of the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow;

[0062] The first modeling module is also used to generate the calling authority of each department according to the department flow order of the business flow;

[0063] The first modeling module is also used to generate a type of call model according to the data association model and the call permissions of each department;

[0064] The second modeling module is used to obtain all business flows and establish a business flow sequence A, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow;

[0065] The second modeling module is also used to select target business flows in sequence according to the business flow sequence A, establish a business flow correlation evaluation model, and generate a correlation evaluation value of the target business flow according to the business flow correlation evaluation model;

[0066] The second modeling module is also used to generate a correlation evaluation value series B=(b1, b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow;

[0067] The second modeling module is also used to preset a correlation evaluation value threshold, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, set the i-th business flow and the target business flow as associated business flows;

[0068] The second modeling module is also used to generate a second type of call model according to all associated business flows.

[0069] In some embodiments of the present application, the data calling unit further includes:

[0070] The first calling module is used to generate the number of business flows to be called and the calling department according to the real-time data calling demand;

[0071] If the calling service flow data is 1, the first calling module generates calling parameters according to a type of calling model;

[0072] If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called;

[0073] If there is an associated business flow, the first calling module generates calling parameters for the associated business flow according to the second type of calling model, and generates calling parameters for the remaining business flows to be called according to the first type of calling model;

[0074] If there is no associated business flow, the first calling module generates calling parameters for each business flow to be called according to a type of calling model.

[0075] Compared with the prior art, the method and system for integrating business data of multiple departments in the embodiment of the present application have the following beneficial effects:

[0076] By adding a central data storage and multiple sub-data storage repositories, all data are pre-processed in the form of business flows and then distributedly stored. The common data of a single business flow flowing between departments is extracted and stored separately to avoid data redundancy. At the same time, the dedicated data of each department is stored separately to ensure data security.

[0077] By establishing multiple calling models and establishing calling relationships between various data packets based on a single business flow, the relevant data in a single business flow can be quickly called, reducing the latency of data calls. At the same time, by generating correlation evaluation values ​​between multiple business flows, related business flows are established to achieve rapid calls between data from different business flows. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 It is a flow chart of a method for integrating business data of multiple departments in a preferred embodiment of the present application. DETAILED DESCRIPTION

[0079] The specific implementation methods of the present application are further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present application but are not intended to limit the scope of the present application.

[0080] In the description of the present application, it should be understood that the terms "center", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0081] The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0082] In the description of this application, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0083] like Figure 1 As shown, a method for integrating business data of multiple departments according to a preferred embodiment of the present application includes:

[0084] S101: Acquire the operation data of each department, generate multiple business flows according to the operation parameters, and generate a business label for each business flow;

[0085] S102: Establish a data analysis model, and generate storage parameters of a single business flow according to the single business flow parameters and the data analysis model;

[0086] S103: Establish a business flow data call model and set call parameters according to real-time data call requirements and the call model.

[0087] Specifically, when generating storage parameters for a single business flow, it includes:

[0088] Select a single business flow and generate the department flow order of the business flow according to the selected business flow parameters;

[0089] Generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and data to be processed of the business flow according to the data analysis model;

[0090] Obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department;

[0091] Generate a common data package, which includes: business labels of business flows, departmental flow order of business flows, basic data of business flows and data to be processed;

[0092] Generate multiple department-specific data packets, which include: department identity tags, business tags of business flows and department processing data;

[0093] Generate storage instructions for common data packages and department-specific data packages.

[0094] Specifically, the shared data refers to the basic information data in the current business flow, the data to be processed refers to the demand data of the department that initiates the business flow, and the flow order of the business flow refers to the order of departments that the business flow needs to pass through. If a department in the flow order processes the data, it will generate processed data, and the processed data will be synchronized to the department's dedicated storage data package. At the same time, a data update reminder will be generated in the business flow. The latest processed data can be obtained by calling parameters, thereby realizing data synchronization among various departments during the data interaction process.

[0095] Specifically, when generating storage instructions for common data packages and department-specific data packages, it includes:

[0096] Establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories;

[0097] Obtain the identity tags of all departments, and create a department-sub-data repository mapping table based on the identity tags and index tags;

[0098] generating encryption parameters for the central data repository;

[0099] Generate encryption parameters of corresponding sub-data repository according to department parameters;

[0100] storing the common data packet in a central data storage repository according to the primary storage instruction;

[0101] The identity tag in the department-specific data package is obtained according to the secondary storage instruction, the target sub-data repository is selected according to the identity tag and the department-sub-data repository mapping table, and the department-specific data package is stored in the target sub-data repository.

[0102] Specifically, different data encryption methods and levels can be established according to the needs of different departments, and data encryption can be completed during storage. At the same time, after the authority of the calling instruction is determined, the decrypted data can be directly output, thereby ensuring data security and preventing data leakage.

[0103] Specifically, the first-level storage instruction refers to storing the common data package in the central data repository, and can be quickly searched according to the business tags in the common data package. The second-level storage instruction refers to selecting a sub-data repository according to the department identity tag in the department-specific data package and then storing it. At the same time, a connection with the common data package in the central data repository is established through the business tag, so that it can be quickly called.

[0104] In a preferred embodiment of the present application, when establishing a service flow data call model, it includes:

[0105] Obtain the common data packets of a single business flow and all department-specific data packets;

[0106] Establish a data association model for the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow;

[0107] Generate the calling permissions of each department according to the departmental flow order of the business flow;

[0108] A calling model is generated according to the data association model and the calling permissions of each department.

[0109] Specifically, one type of calling model refers to establishing a connection between a common data package and a department-specific data package with the same business tag. When making a call, the common data package in the central repository is first queried to perform an initial authority verification. At the same time, the corresponding department-specific data package is quickly queried through the data association model to improve data calling efficiency and security.

[0110] Specifically, all business flows are obtained, and a business flow sequence A is established, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow;

[0111] Select the target business flow in sequence according to the business flow sequence A;

[0112] Establish a business flow correlation evaluation model;

[0113] Generate a relevance evaluation value of a target business flow according to a business flow relevance evaluation model;

[0114] Generate a correlation evaluation value sequence B=(b1,b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow;

[0115] A correlation evaluation value threshold is preset, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, the i-th business flow and the target business flow are set as associated business flows;

[0116] Generate a second type of call model based on all related business flows.

[0117] Specifically, a correlation evaluation value is generated based on the departmental flow order, business demand and business cross-impact between the two business flows. The larger the correlation evaluation value, the higher the correlation between the two businesses, and the greater the mutual influence of the data between the two business flows.

[0118] Specifically, the second-class call model refers to establishing a call relationship based on the correlation evaluation values ​​between different business flows, which can quickly call multiple different business flow data for simultaneous processing, thereby improving the overall efficiency of the system.

[0119] Specifically, when setting the call parameters, it includes:

[0120] Generate the number of business flows to be called and the calling department based on real-time data calling requirements;

[0121] If the calling business flow data is 1, the calling parameters are generated according to a type of calling model;

[0122] If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called;

[0123] If there are associated business flows, call parameters are generated for the associated business flows according to the second-class call model, and call parameters are generated for the remaining business flows to be called according to the first-class call model;

[0124] If there is no associated business flow, the calling parameters of each business flow to be called are generated according to a class of calling models.

[0125] Specifically, when generating call parameters according to the first-level call model, first obtain the identity tag of the department to be called and the common data package corresponding to the call demand, and determine whether the department to be called is a business circulation department according to the circulation department order in the common data package.

[0126] If it is a transfer department, call the shared data package, and directly query the department-specific data package that can be called according to the department's authority to determine whether the calling requirements are met. If they are met, call directly. If not, perform authority authentication between departments according to the department-specific data package to be called. After passing the authentication, the call can be made.

[0127] If it is not a circulation department, an initial permission authentication will be performed on it. After the authentication is completed, the common data package can be called, and the location of the department-specific data package to be called is determined through the common data package. The secondary permission authentication between departments is completed, and the call can be made after passing the authentication.

[0128] The called common data packets and department-specific data packets are merged to generate the called business flow data.

[0129] Specifically, generating calling parameters according to the second-class calling model means obtaining the identity tag of the calling department and two common data packets corresponding to the calling demand, and determining whether the calling department is one of the circulation departments.

[0130] If it is a circulation department, two common data packages are directly called, and the corresponding department-specific data packages are determined based on the common data packages. After completing the authority authentication, it is determined whether the department to be called is a cross-circulation department. If so, only one business flow authority authentication is required, and then the corresponding department-specific data packages in the two business flows can be called. If it is not a cross-circulation department, the authority authentication of the two business flows must be completed, and then the required department-specific data packages are called. The called business flow data is generated by merging the called common data package and all department-specific data packages.

[0131] If it is not a circulation department, first perform the initial permission verification, then call the two common data packages in sequence, and then perform the permission authentication of the two business flows, and then call the required department-specific data package. The called business flow data is generated by merging the called common data package and all department-specific data packages.

[0132] Based on another preferred embodiment of a multi-department business data integration method in any of the above preferred embodiments, this preferred embodiment provides a multi-department business data integration system, including:

[0133] The data collection unit is used to obtain the operation data of each department, generate multiple business flows according to the operation parameters, and generate business tags for each business flow;

[0134] A data integration unit is used to establish a data analysis model and generate storage parameters of a single business flow according to the single business flow parameters and the data analysis model;

[0135] The data calling unit is used to establish a business flow data calling model and set calling parameters according to real-time data calling requirements and the calling model.

[0136] Specifically, the data integration unit includes:

[0137] The first processing module is used to select a single business flow and generate a department flow order of the business flow according to the selected business flow parameters;

[0138] The second processing module is used to generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and the data to be processed of the business flow according to the data analysis model;

[0139] The third processing module is used to obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department;

[0140] The fourth processing module is used to generate a common data package, which includes: a business label of the business flow, a department flow order of the business flow, basic data of the business flow and data to be processed;

[0141] The fourth processing module is also used to generate a plurality of department-specific data packets, wherein the department-specific data packets include: an identity tag of the department, a service tag of the service flow and processing data of the department;

[0142] A storage module, used for generating storage instructions for common data packets and department-specific data packets;

[0143] The storage module is also used to establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories;

[0144] The storage module is also used to obtain the identity tags of all departments and to establish a department-sub-data repository mapping table based on the identity tags and index tags;

[0145] The storage module is further used to store the common data package in the central data repository according to the first-level storage instruction, obtain the identity tag in the department-specific data package according to the second-level storage instruction, select the target sub-data repository according to the identity tag and the department-sub-data repository mapping table, and store the department-specific data package in the target sub-data repository;

[0146] The encryption module is used to generate encryption parameters of the central data repository. The encryption module is also used to generate encryption parameters of corresponding sub-data repositories according to department parameters.

[0147] Specifically, the data calling unit includes:

[0148] The first modeling module is used to obtain the common data packets of a single business flow and all department-specific data packets;

[0149] The first modeling module is also used to establish a data association model of the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow;

[0150] The first modeling module is also used to generate the calling authority of each department according to the department flow order of the business flow;

[0151] The first modeling module is also used to generate a type of call model according to the data association model and the call permissions of each department;

[0152] The second modeling module is used to obtain all business flows and establish a business flow sequence A, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow;

[0153] The second modeling module is also used to select target business flows in turn according to the business flow sequence A, establish a business flow correlation evaluation model, and generate a correlation evaluation value of the target business flow according to the business flow correlation evaluation model;

[0154] The second modeling module is also used to generate a correlation evaluation value series B=(b1, b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow;

[0155] The second modeling module is also used to preset a correlation evaluation value threshold, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, set the i-th business flow and the target business flow as associated business flows;

[0156] The second modeling module is also used to generate a second type of call model according to all associated business flows.

[0157] Specifically, the data calling unit also includes:

[0158] The first calling module is used to generate the number of business flows to be called and the calling department according to the real-time data calling demand;

[0159] If the calling service flow data is 1, the first calling module generates calling parameters according to a type of calling model;

[0160] If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called;

[0161] If there is an associated business flow, the first calling module generates calling parameters for the associated business flow according to the second type of calling model, and generates calling parameters for the remaining business flows to be called according to the first type of calling model;

[0162] If there is no associated business flow, the first calling module generates calling parameters of each business flow to be called according to a type of calling model.

[0163] According to the first concept of the present application, by adding a central storage data and multiple sub-data storage repositories, all data are pre-processed in the form of business flows and then distributedly stored. The common data flowing between various departments in a single business flow is extracted and stored separately, thereby avoiding data redundancy. At the same time, the dedicated data of each department is stored separately to ensure data security.

[0164] According to the second concept of the present application, by establishing multiple calling models, a calling relationship between each data packet is established according to a single business flow, so as to quickly call the relevant data in a single business flow and reduce the latency of data calling. At the same time, by generating correlation evaluation values ​​between multiple business flows, related business flows are established to achieve fast calling between different business flow data.

[0165] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and substitutions can be made without departing from the technical principles of the present application. These improvements and substitutions should also be regarded as the scope of protection of the present application.

Claims

1. A multi-department business data integration method, characterized in that: include: Obtain the operation data of each department, generate multiple business flows according to the operation parameters, and generate business tags for each business flow; Establish a data analysis model and generate storage parameters of a single business flow based on the single business flow parameters and the data analysis model; Establish a business flow data call model and set call parameters according to real-time data call requirements and call models; When generating storage parameters for a single business flow, include: Select a single business flow and generate the department flow order of the business flow according to the selected business flow parameters; Generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and data to be processed of the business flow according to the data analysis model; Obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department; Generate a common data package, wherein the common data package includes: a business label of the business flow, a department flow order of the business flow, basic data of the business flow and data to be processed; Generate multiple department-specific data packets, wherein the department-specific data packets include: an identity tag of the department, a service tag of the service flow, and processing data of the department; Generate storage instructions for common data packages and department-specific data packages; The generation of storage instructions for the common data package and the department-specific data package includes: Establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories; Obtain the identity tags of all departments, and create a department-sub-data repository mapping table based on the identity tags and index tags; generating encryption parameters for the central data repository; Generate encryption parameters of corresponding sub-data repository according to department parameters; storing the common data packet in a central data storage repository according to the primary storage instruction; Obtaining the identity tag in the department-specific data package according to the secondary storage instruction, selecting a target sub-data repository according to the identity tag and the department-sub-data repository mapping table, and storing the department-specific data package in the target sub-data repository; The establishment of the business flow data calling model includes: Obtain the common data packets of a single business flow and all department-specific data packets; Establish a data association model for the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow; Generate the calling permissions of each department according to the departmental flow order of the business flow; A type of calling model is generated according to the data association model and the calling authority of each department.

2. The multi-department business data integration method according to claim 1, characterized in that: When establishing a business process data call model, it also includes: Obtain all business flows and establish a business flow sequence A, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow; Select the target business flow in sequence according to the business flow sequence A; Establish a business flow correlation evaluation model; Generate a relevance evaluation value of a target business flow according to a business flow relevance evaluation model; Generate a correlation evaluation value sequence B=(b1,b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow; A correlation evaluation value threshold is preset, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, the i-th business flow and the target business flow are set as associated business flows; Generate a second type of call model based on all related business flows.

3. The multi-department business data integration method according to claim 2, characterized in that: When setting the call parameters, include: Generate the number of business flows to be called and the calling department based on real-time data calling requirements; If the calling business flow data is 1, the calling parameters are generated according to a type of calling model; If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called; If there are associated business flows, call parameters are generated for the associated business flows according to the second-class call model, and call parameters are generated for the remaining business flows to be called according to the first-class call model; If there is no associated business flow, the calling parameters of each business flow to be called are generated according to a class of calling models.

4. A multi-department business data integration system, using the multi-department business data integration method according to any one of claims 1 to 3, characterized in that: include: The data collection unit is used to obtain the operation data of each department, generate multiple business flows according to the operation parameters, and generate business tags for each business flow; A data integration unit is used to establish a data analysis model and generate storage parameters of a single business flow according to the single business flow parameters and the data analysis model; A data calling unit is used to establish a business flow data calling model and set calling parameters according to real-time data calling requirements and the calling model; The data integration unit comprises: The first processing module is used to select a single business flow and generate a department flow order of the business flow according to the selected business flow parameters; The second processing module is used to generate the initial circulation department of the business flow, obtain the business data packet corresponding to the initial circulation department, and generate the basic data and data to be processed of the business flow according to the data analysis model; The third processing module is used to obtain the business data packets corresponding to the business flow in each circulation department and generate processing data for each circulation department; A fourth processing module is used to generate a common data packet, wherein the common data packet includes: a business label of the business flow, a department flow order of the business flow, basic data of the business flow and data to be processed; The fourth processing module is further used to generate a plurality of department-specific data packets, wherein the department-specific data packets include: an identity tag of the department, a service tag of the service flow and processing data of the department; A storage module, used for generating storage instructions for common data packets and department-specific data packets; The storage module is also used to establish a central data repository and multiple sub-data repositories, and generate index tags for the sub-data repositories; The storage module is also used to obtain identity tags of all departments and establish a department-sub-data storage library mapping table according to the identity tags and index tags; The storage module is further used to store the common data packet in the central data storage according to the first-level storage instruction, obtain the identity tag in the department-specific data packet according to the second-level storage instruction, select the target sub-data storage according to the identity tag and the department-sub-data storage mapping table, and store the department-specific data packet in the target sub-data storage; An encryption module, used to generate encryption parameters for the central data repository, and the encryption module is also used to generate encryption parameters for corresponding sub-data repositories according to department parameters; The data calling unit comprises: The first modeling module is used to obtain the common data packets of a single business flow and all department-specific data packets; The first modeling module is also used to establish a data association model of the common data packets of the business flow and the data packets dedicated to all departments according to the business labels of the business flow; The first modeling module is also used to generate the calling authority of each department according to the department flow order of the business flow; The first modeling module is also used to generate a type of call model according to the data association model and the call permissions of each department; The second modeling module is used to obtain all business flows and establish a business flow sequence A, A=(A1, A2…An), where n is the number of business flows and Ai is the i-th business flow; The second modeling module is also used to select target business flows in sequence according to the business flow sequence A, establish a business flow correlation evaluation model, and generate a correlation evaluation value of the target business flow according to the business flow correlation evaluation model; The second modeling module is also used to generate a correlation evaluation value series B=(b1, b2…bn), where n is the number of business flows, and bi is the correlation evaluation value between the i-th business flow and the target business flow; The second modeling module is also used to preset a correlation evaluation value threshold, and if the correlation evaluation value bi is greater than the correlation evaluation value threshold, set the i-th business flow and the target business flow as associated business flows; The second modeling module is also used to generate a second type of call model according to all associated business flows.

5. The multi-department business data integration system according to claim 4, characterized in that: The data calling unit also includes: The first calling module is used to generate the number of business flows to be called and the calling department according to the real-time data calling demand; If the calling service flow data is 1, the first calling module generates calling parameters according to a type of calling model; If the calling business flow data is greater than 1, determine whether there is an associated business flow in the business flow to be called; If there is an associated business flow, the first calling module generates calling parameters for the associated business flow according to the second type of calling model, and generates calling parameters for the remaining business flows to be called according to the first type of calling model; If there is no associated business flow, the first calling module generates calling parameters for each business flow to be called according to a type of calling model.

Images