A service execution management method, system and device

Abstract

The embodiment of the present application discloses a kind of service execution management method, system and equipment.The technical scheme provided by the embodiment of the present application is configured to create assessment target according to target parameter, the assessment target is distributed to target execution user, the business operation event of target execution user in one or more preset business module is listened to, the business operation event is normalized and mapped into the index mapping table of assessment target, is routed to target index by index mapping table, and the index completion value of target index is determined, the business processing progress of target execution user is determined according to the index completion value of target index, in the case where the business processing progress meets the early warning rule trigger condition of pre-set, based on the differential inhibition window of pre-set, create business early warning instance, carry out business early warning processing by business early warning instance, while warning in time to business exception, reduce alarm noise by differential inhibition window, improve business execution management effect.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a business execution management method, system and device. Background Technology

[0002] In multi-business channel store management solutions, since store management involves multiple business links such as contract management, customer management, target management, and task management, any deviation in any business link may cause abnormalities in store management.

[0003] Business management of related technologies typically involves managers manually reviewing reports and making follow-up phone calls at each level to identify problems. This approach results in significant delays in identifying and addressing business anomalies in a timely manner, leading to poor business execution management. Summary of the Invention

[0004] This application provides a business execution management method, system, and device to address the technical problems in related technologies where the discovery of business issues is often delayed, making it difficult to promptly detect and handle business anomalies and resulting in poor business execution management. The method can provide timely warnings of business anomalies and improve the effectiveness of business execution management.

[0005] In a first aspect, embodiments of this application provide a business execution management method, including: Based on the target parameter configuration, create assessment targets and assign the assessment targets to target execution users; Listen for business operation events of the target user in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment target, route to the target indicator through the indicator mapping table, and determine the indicator completion value of the target indicator. The business processing progress of the target user is determined based on the target indicator completion value; When the business processing progress meets the preset warning rule triggering conditions, a business warning instance is created based on a preset differentiated suppression window, and business warning processing is performed through the business warning instance.

[0006] In a second aspect, embodiments of this application provide a business execution management device, including a target allocation module, a mapping processing module, a progress determination module, and an early warning processing module, wherein: The target allocation module is used to create assessment targets according to target parameter configuration and allocate the assessment targets to target execution users; The progress determination module is used to monitor the business operation events of the target user in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment target, route to the target indicator through the indicator mapping table, and determine the indicator completion value of the target indicator. The mapping processing module is used to determine the business processing progress of the target user based on the target indicator's completion value. The early warning processing module is used to create a business early warning instance based on a preset differentiated suppression window when the business processing progress meets the preset early warning rule triggering conditions, and to perform business early warning processing through the business early warning instance.

[0007] In a third aspect, embodiments of this application provide a business management system, which includes a business management service and a business early warning service, wherein: The business management service is used to create assessment targets based on target parameter configuration, assign the assessment targets to target execution users; monitor the business operation events of the target execution users in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment targets, route to the target indicators through the indicator mapping table, and determine the indicator completion value of the target indicators; and determine the business processing progress of the target execution users based on the indicator completion value of the target indicators. The business early warning service is used to create a business early warning instance based on a preset differentiated suppression window when the business processing progress meets the preset early warning rule triggering conditions, and to perform business early warning processing through the business early warning instance.

[0008] In a fourth aspect, embodiments of this application provide a business execution management device, including: a memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the business execution management method as described in the first aspect.

[0009] In a fifth aspect, embodiments of this application provide a storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform the business execution management method as described in the first aspect.

[0010] This application embodiment creates assessment targets based on target parameter configuration, assigns these targets to target execution users, monitors business operation events of target execution users in one or more preset business modules, normalizes and maps these business operation events to the indicator mapping table of the assessment targets, routes them to target indicators through the indicator mapping table, determines the indicator completion value of the target indicator, determines the business processing progress of the target execution user based on the indicator completion value, and creates a business early warning instance based on a preset differential suppression window when the business processing progress meets the preset early warning rule triggering conditions. The business early warning instance is then used for business early warning processing. By normalizing and mapping business operation events, unified processing of business processing progress under multiple preset business modules is supported. While providing timely early warnings for business anomalies, the differential suppression window reduces alarm noise and improves the effectiveness of business execution management. Attached Figure Description

[0011] Figure 1 This is a flowchart of a business execution management method provided in an embodiment of this application; Figure 2 This is a flowchart of another business execution management method provided in the embodiments of this application; Figure 3 This is a schematic diagram of a tissue tree structure provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a business execution management device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a business management system provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a business execution management device provided in an embodiment of this application. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but additional steps not included in the drawings may also be present. The above processes can correspond to methods, functions, procedures, subroutines, subroutines, etc.

[0013] In multi-channel store management solutions based on relevant technologies, the management of business execution is particularly important because store management involves multiple business processes such as contract management, customer management, target management, and task management. For example, in the management of stores and distributors in the retail industry, the formulation, breakdown, and tracking of marketing targets are key aspects of improving multi-channel management. In actual retail scenarios, different types of targets have completely different task execution and data collection paths: process-related targets (such as the number of new customers) require employees to upload vouchers through the to-do task portal and have them reviewed before being counted; result-related targets (such as contract amount) require creation through a separate contract entry module and review and feedback from an external CRM system (customer relationship management system) before being counted; channel-related targets (such as the number of cross-industry visits) may be submitted by external non-store personnel. Currently, business execution management only supports a single data submission method and cannot be compatible with these heterogeneous data collection paths within the same business execution management framework. In addition, when task anomalies are detected in business execution management, the same task anomaly warning is repeatedly pushed within a short period of time. Managers tend to ignore all warnings after becoming fatigued, resulting in important task anomalies being overlooked and poor business execution management effectiveness. Based on this, an embodiment of the present application provides a business execution management method to solve the above-mentioned technical problems.

[0014] Figure 1 A flowchart of a business execution management method provided in an embodiment of this application is given. The business execution management method provided in this embodiment of the application can be executed by a business execution management device, which can be implemented by hardware and / or software and integrated into a business execution management device.

[0015] The following description uses the business execution management device as an example to illustrate the business execution management method. (Reference) Figure 1 The business execution management method includes: S110: Create assessment targets based on target parameter configuration and assign the assessment targets to target execution users.

[0016] For example, the system receives target parameter configurations submitted by a management user and creates assessment targets based on these configurations. In one embodiment, after creating the assessment targets, they can be distributed to target execution users. These target execution users can be specified by the management user, for example, by including the specified target execution user in the submitted target parameter configuration. Optionally, the target execution user can be the management user or other users; there can be one or more target execution users. The assessment targets created based on the target parameter configurations can be one or more. A single assessment target can be specified to be executed by one target execution user or by multiple target execution users simultaneously (distributing the same assessment target to multiple target execution users at the same time). The assessment target records one or more target completion values ​​that target execution users need to complete, such as the number of events (e.g., morning / evening meetings) that target execution users need to complete, the total amount of contracts to be closed, the number of customers to be entered, etc. The assessment target can also record the frequency of assessing target execution users. Optionally, the assessment target can be issued to the target execution user when the assessment target is created, or it can be issued to the target execution user at a preset time. The preset time can be specified by the management user, for example, the management user can include the preset time in the target parameter configuration submitted.

[0017] In one possible embodiment, the business execution management method provided in this application further includes, before creating the assessment target according to the target parameter configuration: determining the target assessment indicators and the target execution user, and performing constraint verification on the target assessment indicators based on preset indicator constraint rules; and determining the target parameter configuration according to the target assessment indicators and the target execution user if the target assessment indicators pass the constraint verification.

[0018] The indicator constraint rules provided in this application can be used to constrain the combination of performance indicators, and can control the configuration behavior of performance indicators in the target container (a container used to hold target performance indicators and target execution users). The indicator constraint rules for performance indicators can be default rules or dynamically set rules, such as when an administrator sets indicator constraint rules for a target performance indicator. The target performance indicator is used to determine whether the target execution user has completed the performance target. When the target execution user completes the target indicator, the target execution user is considered to have completed the performance target, and thus has completed the target set for them. Optionally, a performance target can correspond to one or more target performance indicators. When a performance target corresponds to multiple target performance indicators, the target execution user is considered to have completed the performance target when they complete all the target indicators, and thus has completed the target set for them. The progress of the target execution user in processing performance targets can also be determined based on the number of performance targets completed by the target execution user.

[0019] In one embodiment, the indicator constraint rules provided in this application include core indicator determination rules, single-selection mutual exclusion constraint rules, and hybrid compatibility rules. Core indicators are assessment indicators that can be used independently to determine whether a task required by the assessment target has been completed. Core indicator determination rules can be used to stipulate that when a core indicator exists, no other assessment indicators can be added; that is, when a core indicator exists, only the completion status of the core indicator is used as the basis for determining whether the task required by the assessment target has been completed, and the completion status of non-core indicators does not affect the determination of whether the task required by the assessment target has been completed. When no core indicator exists, the task required by the assessment target is determined to be completed only after all specified target assessment indicators have been completed. Single-selection mutual exclusion constraint rules can be used to stipulate that when a selected target assessment indicator is a single-selection indicator, no other assessment indicators can be added. For example, when a certain audit indicator is marked as a single-selection indicator, mutual exclusion checks are automatically performed on the indicator selection interface of the target configuration to prevent this single-selection indicator from being added to the same target container as other audit indicators simultaneously. Hybrid compatibility rules can be used to specify that different categories of assessment indicators (such as result-based assessment indicators, process-based assessment indicators, and channel-based assessment indicators) can be used together for the same assessment objective. Each assessment indicator can maintain its own data collection path identifier to ensure that the data sources of each assessment indicator do not interfere with each other when used together.

[0020] For example, the system obtains the target performance indicators and target execution users provided by the management user, and performs constraint verification on the target performance indicators based on preset indicator constraint rules to determine whether the target performance indicators meet the requirements of the preset indicator constraint rules. If the target performance indicators fail the constraint verification, a reminder can be sent to the management user based on the reason for not meeting the indicator constraint rules, so as to remind the management user to reconfigure the target performance indicators that meet the requirements of the preset indicator constraint rules.

[0021] In one embodiment, when the indicator passes constraint validation, the target parameter configuration can be determined based on the target performance indicator and the target execution user. For example, the target performance indicator and the target execution user that passed constraint validation can be added to the target container. The target parameter configuration records the target performance indicator and the target execution user. Optionally, the target execution user can be a unit (e.g., region, area, store, etc.) and / or an individual (e.g., regional manager, store manager, store employee, etc.) participating in the target evaluation.

[0022] This application constrains and verifies target assessment indicators based on preset indicator constraint rules. When the target assessment indicators pass the constraint verification, the target parameter configuration is determined according to the target assessment indicators and the target execution user. Multi-dimensional indicator constraints are achieved through core indicator judgment rules, single-selection mutual exclusion constraint rules, and mixed compatibility rules. Management users can create rapid assessment targets with core indicators as the core, or they can create comprehensive audit indicators that mix multiple categories of audit indicators. At the system level, the indicator constraint rules can effectively improve the expressive richness of target parameter configuration while ensuring the rationality and consistency of target parameter configuration.

[0023] In one possible embodiment, the performance indicators provided in this application include process-based performance indicators and non-process-based performance indicators. The non-process-based performance indicators include result-based performance indicators and channel-based performance indicators. The performance targets include business instances and target notifications corresponding to the process-based and non-process-based performance indicators, respectively. The business instance can be an executable task unit generated by a preset task instantiation engine.

[0024] Based on this, the business execution management method provided in this application creates assessment targets according to the target parameter configuration and assigns the assessment targets to target execution users. It may include: when the target assessment indicator in the target parameter configuration is a process-type assessment indicator, creating a corresponding business instance according to the target parameter configuration and assigning the business instance to the target execution user in the target parameter configuration; and / or, when the target assessment indicator in the target parameter configuration is not a process-type assessment indicator, generating a corresponding target notification according to the target parameter configuration and sending the target notification to the target execution user in the target parameter configuration.

[0025] In one embodiment, process-based performance indicators can only be correctly calculated through process-based events triggered by corresponding business instances. Therefore, when assigning performance targets, it can be determined whether the performance indicators of the performance targets are process-based. If the performance indicators of the performance targets are process-based, a corresponding business instance is created based on the process-based performance indicator, and the business instance is assigned to the target execution user in the target parameter configuration to add the business instance to the to-do task module of the target execution user. For example, if the performance target combines two performance indicators: the number of customers contacted and the number of script practice sessions, where the number of script practice sessions is a process-based performance indicator and the number of customers contacted is a channel-based indicator, a corresponding business instance can be created for the process-based performance indicator of the number of script practice sessions. The indicator category of the number of script practice sessions is marked as the identifier of the business instance, thereby assigning the business instance to the target execution user corresponding to the performance target. This allows the user client logged into the user account of the target execution user to add the newly assigned business instance to the list of the to-do task module. Subsequently, when a user completes a script rehearsal, they can click on the business instance in the to-do task module list to upload the corresponding materials. The to-do task module then generates a script rehearsal event based on the uploaded materials, the business instance's identifier, and the user's account. This event is then transmitted to the process event adapter in the target management system. The process event adapter updates the script rehearsal count in the user's corresponding assessment target based on the script rehearsal event.

[0026] Both channel-based and result-based metrics are linked to relevant business modules. Once these modules receive materials uploaded by the target user, they generate corresponding channel-based or result-based events. Therefore, no business instances need to be set up for channel-based and result-based metrics. To promptly notify target users of achieving their performance targets, target notifications can be sent. Specifically, if the performance target is not a process-based metric, a corresponding target notification is generated based on the performance target and sent to the target user's account, allowing the client logged into that account to display the notification. This target notification can be a WeChat official account push or a pop-up notification. This application ensures accurate statistics for process-based performance indicators and timely notifications for non-process-based performance indicators by setting different target allocation methods for different types of performance indicators.

[0027] In one embodiment, the business execution management method provided in this application, after creating a business instance according to the target parameter configuration, can utilize a preset task instantiation engine to perform periodic segmentation and target value allocation processing on the business instance. For example, based on the set assessment frequency (single, daily, weekly, monthly, quarterly), the start and end dates of the target can be divided into multiple assessment period nodes, with each assessment period node corresponding to one or more task instances. According to a preset numerical allocation strategy (the numerical allocation strategy can be allocated by uniform value, average allocation, or allocation by custom value), the total target value of the indicator is distributed to each assessment unit and / or individual. In the scenario of stores without staff, the task instantiation engine can automatically assign tasks to associated dealer accounts and aggregate the data executed by the dealers to the assigned store dimension during data statistics. Optionally, based on the audit settings recorded in the target configuration (e.g., whether audit is enabled, number of audit levels, audit type, etc.), a corresponding audit link can be bound to each task instance, and the audit link supports matching audit users by job role or specifying audit users. After generating a task instance, it can be pushed to the user's client-side to-do list. The user can then view the task instance that needs to be processed in the client-side to-do list. After the management user completes the target configuration at the planning level, the task instantiation engine automatically completes the entire process of task cycle segmentation, target value allocation, review link binding, and batch distribution, eliminating the manual steps between target planning and target execution, and achieving automatic penetration of targets from configuration to execution.

[0028] S120: Listen for business operation events of the target user in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment target, route them to the target indicator through the indicator mapping table, and determine the indicator completion value of the target indicator.

[0029] S130: Determine the business processing progress of the target user based on the target indicator's completion value.

[0030] For example, real-time monitoring is performed on business operation events of the target user in one or more preset business modules. These preset business module operation events can be a combination of one or more of the following: process-type operation events from a pending business module, result-type operation events from a business module, and channel-type operation events from an external channel module. Optionally, the assessment target can correspond to a combination of one or more preset business modules, meaning the target user needs to perform business operations in one or more preset business modules to complete the tasks required by the assessment target.

[0031] After detecting business operation events of the target user in a preset business module, the business operation events can be normalized and mapped to the indicator mapping table of the assessment target, and then routed to the target indicator through the indicator mapping table. The normalization mapping of business operation events can be achieved by converting the business operation events into a preset standard event format, and then mapping the converted business operation events into the indicator mapping table to update the indicator mapping table.

[0032] In one embodiment, a metric mapping table corresponding to the assigned performance target can be maintained for each target. This metric mapping table can be used to record the mapping relationship between different business operation events and different metrics. The metric mapping table can be used to route and map the normalized business operation events to the corresponding performance metrics, and the routed performance metrics can be determined as the target metrics. The metric mapping table can be automatically generated during the target parameter configuration phase based on the classification of performance metrics selected by the management user, without requiring the management user to manually configure the metric mapping table.

[0033] In one embodiment, after determining the target metric, the target metric completion value is determined, and the business processing progress of the target user is determined based on the target metric completion value. Optionally, after determining the target metric completion value, the business processing progress can be determined based on the metric completion value and the target completion value recorded in the performance evaluation record, for example, based on the ratio of the metric completion value to the target completion value.

[0034] Optionally, the indicator completion value can be the number of times the corresponding business operation event is completed, or it can be the cumulative data corresponding to the business operation event (such as the cumulative amount of contracts or the number of customers entered). The type of indicator completion value can be determined according to the type of assessment indicator corresponding to the assessment target. For example, the indicator completion value corresponding to the process assessment indicator can be the number of times it is completed, the indicator completion value corresponding to the result assessment indicator can be the cumulative amount of contracts, and the indicator completion value corresponding to the channel assessment indicator can be the number of customers entered.

[0035] Specifically, determining the target indicator's completion value can be achieved by accumulating the current target indicator's completion value to obtain a new completion value. This accumulation operation can be performed atomically, meaning the accumulation process is uninterrupted.

[0036] Optionally, the accumulation operation of the target indicator's completion value can be performed through the corresponding adapters (including process event adapters, result event adapters, and channel event adapters). Assuming a user uploads a Morning Meeting task, after the Morning Meeting task is approved by the administrator, the process event adapter normalizes and maps the business operation event corresponding to the Morning Meeting task to the indicator mapping table. The indicator mapping table then routes the data to the target indicator corresponding to the Morning Meeting task, and the completion value of the indicator corresponding to the Morning Meeting task is incremented by 1. At this point, the latest indicator completion value reflects the total number of times the target execution task executed the Morning Meeting task after being assigned to the corresponding assessment target. Similarly, assuming a user uploads an order contract, after the order contract is approved by the administrator, the result event adapter normalizes and maps the business operation event corresponding to the order contract to the indicator mapping table. The indicator mapping table then routes the data to the target indicator corresponding to the order contract, and the completion value of the indicator corresponding to the order contract is incremented by the amount of the order contract. At this point, the latest indicator completion value reflects the total amount of the signed order contracts after the target execution task was assigned to the corresponding assessment target. Assuming the target execution user uploads customer information once, the channel-type event adapter normalizes and maps the business operation event corresponding to the uploaded customer information to the indicator mapping table. The indicator mapping table routes to the target indicator corresponding to the customer information. The indicator completion value corresponding to the customer information is either increased by 1 or increased by the number of customers reflected in the customer information. At this time, the latest indicator completion value reflects the total number of customers uploaded after the target execution task is assigned to the assessment target corresponding to the customer information task.

[0037] In one possible embodiment, a unified event bus can be constructed to normalize and map business operation events from different preset business modules to an indicator mapping table. Optionally, the business execution management method provided in this application, which monitors business operation events of a target execution user in one or more preset business modules, may utilize a preset event adapter to monitor these events.

[0038] The preset event adapters provided in this application include one or more combinations of process-type event adapters, result-type event adapters, and channel-type event adapters. The preset business modules provided in this application include one or more combinations of to-do business modules, result-type business modules, and external channel modules. Specifically, the process-type event adapter is used to listen for process-type operation events in the to-do business module, the result-type event adapter is used to listen for result-type operation events in the result-type business module, and the channel-type event adapter is used to listen for channel-type operation events in the external channel module.

[0039] In one embodiment, the target user can execute process-type operation events in the to-do business module, and the process-type event adapter can listen for these events. For example, the target user can upload credentials (such as a watermarked photo from a morning or evening meeting, a group photo from a cross-industry visit, or a screenshot of added contact information) and submit them through the to-do entry provided by the to-do business module, thereby executing a process-type operation event. After detecting a process-type operation event, the process-type event adapter generates a process-type operation event (task submission event) and enters the event bus. This event carries the assessment target identifier, the submitting user, the submission time, and the indicator identifier of the associated audit indicator. After the process-type operation event enters the audit queue, if the user passes the audit, the process-type event adapter triggers the accumulation operation of the audit indicator completion value, thereby normalizing and mapping the process-type operation event to the indicator mapping table.

[0040] In one embodiment, the target user can execute result-type operation events in result-type business modules, and the result-type event adapter can listen for these events. For example, after creating and submitting a contract through a result-type business module (such as the contract and payment module), the result-type business module synchronizes the contract data to an external customer relationship management system (CRM system), thereby executing the result-type operation event. When the external CRM system returns the review result of the contract data, the result-type event adapter verifies the returned review result. If the review result passes, the contract amount is added to the completion value of the total contract amount indicator in the indicator mapping table. If a payment order is uploaded through the result-type business module, no review is required, and the amount corresponding to the payment order is directly added to the completion value of the offline total payment indicator in the indicator mapping table, thus normalizing and mapping the result-type operation event to the indicator mapping table.

[0041] In one embodiment, the target user can execute channel-type operation events in an external channel module, and the channel-type event adapter can listen for these events. For example, when a non-store personnel such as a cross-industry partner, existing customer, or designer submits an execution credential through a preset submission portal, the channel-type event adapter converts the channel-type operation event into a standard event format and injects it into the event bus. This channel-type operation event carries the channel identifier, the submitting user, the submission time, and the indicator identifier of the associated audit indicator. Based on the listened-to channel-type operation event, the channel-type event adapter triggers an accumulation operation of the audit indicator completion value, thereby normalizing and mapping the channel-type operation event to the indicator mapping table.

[0042] This application utilizes preset event adapters to monitor business operation events of target users in one or more preset business modules. Compared to related technologies that only support data collection from a single data source, this application uses an event bus and three types of adapters to collect business operation events from different sources and processes, such as process vouchers, contract review feedback, and external submissions, without changing their original business processes. It supports the collection of data from different data sources and automatically normalizes and maps them to the same performance indicator mapping table, providing a unified collection capability for heterogeneous events and improving the effectiveness of business execution management.

[0043] S140: When the business processing progress meets the preset warning rule triggering conditions, a business warning instance is created based on the preset differentiated suppression window, and business warning processing is performed through the business warning instance.

[0044] For example, the business processing progress of the target user is acquired at preset time intervals or preset time points, and it is determined whether the business processing progress of the target user meets the preset warning rule triggering conditions. Optionally, if the business processing progress at the current time is lower than the progress threshold corresponding to the preset time, the business processing progress can be considered to meet the preset warning rule triggering conditions; if the business processing progress at the current time reaches the progress threshold corresponding to the preset time, the business processing progress can be considered not to meet the preset warning rule triggering conditions. Different preset times can correspond to different progress thresholds, and the corresponding progress thresholds increase as the preset time progresses.

[0045] In one embodiment, when the business processing progress meets the preset warning rule triggering conditions, a business warning instance is created based on a preset differentiated suppression window, and business warning processing is performed through the business warning instance. In one embodiment, the business warning instance may record alarm records corresponding to the assessment targets.

[0046] Optionally, business progress alerts can be sent to one or more combinations of the target execution user, the target execution user's superior user (e.g., the target execution user's leader), and management users to remind the target execution user, the target execution user, and management users of the processing progress of the corresponding assessment target. In one embodiment, the business alert instance may record alarm records corresponding to the assessment target. For example, within the time range corresponding to the preset differential suppression window, if there is no business alert instance created based on the corresponding assessment target (e.g., no business alert instance for this assessment target has been created before, or the previously created business alert instance has exceeded the differential suppression window), a business alert instance can be created based on the assessment target and the corresponding business processing progress. If there is a business alert instance created based on the corresponding assessment target within the time range corresponding to the preset differential suppression window, no new business alert instance is created.

[0047] In one embodiment, after creating a business alert instance, an evidence set aggregation operation can be performed. This involves extracting relevant information from the corresponding business subsystem (preset business module) based on the alert type of the business alert instance (e.g., process alerts, result alerts, channel alerts, performance alerts, and risk alerts; different alert types may correspond to different alert rule triggering conditions), and organizing the extracted relevant information into a structured evidence set. Optionally, a two-layer "summary-details" structure can be used to record the evidence set. The summary layer provides core alert values ​​(such as the difference between the current achievement rate and the target value, the total number of overdue customers, etc.) for management users to quickly make a global judgment. The details layer provides data such as the distribution of problem areas, the achievement ranking of each region or store, anonymized information of specific abnormal customers, and the number of days without follow-up, allowing management users to drill down layer by layer to locate the root cause. The evidence set and the business alert instance can be stored together. When management users view the alert details of the business alert instance, both the alert details and the evidence set are presented together, allowing management users to obtain the complete context required for decision-making without jumping to other systems.

[0048] Optionally, a configurable differentiated suppression window can be provided for each type of alert (e.g., the duration of the differentiated suppression window can be 7 days, 3 days, 24 hours, 12 hours, 6 hours, etc.). Management users can set the duration of the differentiated suppression window for different alert types according to actual business needs. Optionally, different differentiated suppression windows can be preset according to the alert type. For example, for type A (performance-related alerts), the longest suppression period (e.g., 7 days) can be preset as the differentiated suppression window to match the monthly target assessment rhythm; for type B (process-related alerts), a medium suppression period (e.g., 3 days) can be implemented as the differentiated suppression window to match the standard customer follow-up cycle; and for type C (risk alerts), a shorter suppression period (e.g., 1 day) can be implemented as the differentiated suppression window because it is an urgent matter that needs to be reviewed the next day. Within the differentiated suppression window, even if the business processing progress of the next round of scheduled checks still meets the preset alert rule triggering conditions, no new business alert instance will be generated, thus filtering out duplicate alerts from the same source in the time dimension. Optionally, once a management user issues a follow-up alert for a specific business alert instance, that alert type enters a "handled and silent" state during subsequent detection and will not be pushed again. Furthermore, alert pushes can be paused during special periods such as statutory holidays by configuring silent rules. By configuring adjustable differentiated suppression windows according to alert categories and a behavior linkage mechanism of "silencing upon task issuance," the time-dimensional suppression window and the behavior-dimensional handling silence together form a dual noise reduction barrier. This filters duplicate alarms from the same source from both the time and behavior dimensions. Compared to related technologies that repeatedly push the same anomaly indiscriminately, this significantly reduces invalid alarms while ensuring that truly important alerts are not missed, thus significantly reducing alert noise.

[0049] In one possible embodiment, after creating a business early warning instance based on a preset differential suppression window, the business execution management method provided in this application further includes: creating an early warning follow-up service based on the business early warning instance, issuing the early warning follow-up service to the early warning follow-up user, and updating the early warning status of the business early warning instance based on the business status of the early warning follow-up service.

[0050] For example, after creating a business alert instance based on a preset differentiated suppression window, an alert follow-up service can be created based on the business alert instance. The follow-up user for the business alert instance can be determined, and the alert follow-up service can be issued to the follow-up user. For instance, a list of assignable follow-up personnel can be automatically filtered based on the alert type and organizational level and provided to the management user for selection. The management user can select an alert follow-up user from the follow-up user list, set a deadline, and complete the task requirements. An alert follow-up service is created based on the business alert instance, the alert follow-up user, the set deadline, and the completed task requirements. Optionally, the alert follow-up user can be a management user, a target execution user, or other users. There can be one or more alert follow-up users. An alert follow-up service created based on a business alert instance can be one or more. An alert follow-up service can be assigned to one alert follow-up user or can be assigned to multiple alert follow-up users jointly (simultaneously issuing the same alert follow-up service to multiple alert follow-up users). The alert follow-up service record contains one or more business alert instances that require follow-up by the alert follow-up user.

[0051] In one embodiment, the system continuously monitors and updates the business status of alert follow-up services. The alert status of the business alert instance can be updated based on the business status of the alert follow-up service. For example, a bidirectional mapping relationship can be established between the alert follow-up service and its corresponding business alert instance through a unique identifier. When the business status of the alert follow-up service changes (e.g., from "pending execution" to "submitted," and then to "approved"), the business status update event of the alert follow-up service can be written back to the business alert instance. This allows the migration of the alert state machine of the business alert instance to be updated based on the business status update event, thus updating the alert status of the business alert instance. This application achieves bidirectional status binding and linkage between the alert follow-up service and the business alert instance by creating alert follow-up services based on the business alert instance and issuing them to the alert follow-up user, and updating the alert status of the business alert instance based on the business status of the alert follow-up service. This ensures that each business alert instance has a clearly defined alert follow-up user as the responsible party and traceable handling records, avoiding the process breakage problem in related technologies where alerts and handling belong to different systems, and improving the effectiveness of business execution management.

[0052] In one embodiment, the status of a business alert instance includes "Pending," "Issued," "In Process," and "Resolved," and it transitions between these multiple statuses. A resolution condition determination is performed on business alert instances in the "Pending," "Issued," and "In Process" states according to a set detection cycle. The resolution condition is defined by a calculable indicator threshold expression. For example, when the gap between the performance achievement rate and the time schedule narrows to within 10%, or the backlog of customers drops below a preset threshold, the corresponding business alert instance is marked as "Resolved."

[0053] Optionally, after marking a business alert instance as "resolved," the handling trajectory of that instance from triggering to resolution can be archived. This trajectory may include the trigger time, task assignment time, execution time, and changes in metrics upon resolution, providing data for subsequent review and threshold optimization by management users. This application automatically determines and executes resolution operations by linking the resolution conditions of business alert instances to actual business data. This avoids the arbitrariness of manual resolution and eliminates interference from resolved issues remaining in the alert list.

[0054] The above describes a process where assessment targets are created based on target parameter configurations, assigned to target execution users, and their business operation events in one or more preset business modules are monitored. These events are then normalized and mapped to the performance indicator mapping table of the assessment targets. The mapping table routes the data to target indicators, determines their completion values, and establishes the business processing progress of the target execution users based on these values. When the business processing progress meets preset warning rule triggering conditions, a business warning instance is created based on a preset differentiated suppression window. This process handles business warnings through the normalized mapping of business operation events, supporting unified processing of business processing progress across multiple preset business modules. It provides timely warnings for business anomalies while reducing alarm noise through the differentiated suppression window, thereby improving the effectiveness of business execution management.

[0055] Based on the above embodiments, Figure 2 A flowchart of another business execution management method provided in an embodiment of this application is given, which is a concretization of the above-described business execution management method. (Reference) Figure 2 The business execution management method includes: S210: Create assessment targets based on target parameter configuration and assign the assessment targets to target execution users.

[0056] S220: Listen for business operation events of the target user in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment target, route them to the target indicator through the indicator mapping table, and determine the indicator completion value of the target indicator.

[0057] S230: Determine the business processing progress of the target user based on the target indicator's completion value.

[0058] S240: When the business processing progress meets the preset warning rule triggering conditions, a business warning instance is created based on the preset differentiated suppression window, and business warning processing is performed through the business warning instance.

[0059] S250: Obtain the description information of the target object, extract the target feature information from the description information, and fill the target feature information into the preset object information table to obtain the target object information table.

[0060] For example, the description information of the target object is obtained, wherein the target object may be a customer, and the description information of the target object may be a description of the customer. The description information may be recorded in the form of pictures, voice, text, etc., that is, one or more combinations of pictures, voice, and text that record the description information of the customer are obtained.

[0061] In one embodiment, image input, voice input, and text input interfaces can be provided on the user end (e.g., the sales guide end in an offline sales scenario). Users can submit images (images and / or screenshots) containing descriptive information about customers through the image input interface. Images can be photographs of paper contracts, original customer ID cards, or screenshots of WeChat chats or transfers with customers selected from the album. Users can submit voice recordings containing descriptive information about customers through the voice input interface. Users can long-press the record button to speak customer information in natural language. For example, they could receive a voice description such as, "Mr. A, who just looked at product XX, has the phone number 1XX******** and the price is XXXX yuan. He said he's bringing his family to place an order this weekend, and he wants to remind me to prepare samples in advance." Users can submit text containing descriptive information about customers through the text input interface. For example, users can submit text containing descriptive information about customers through methods such as pasting, uploading documents, or text input.

[0062] Furthermore, target feature information is extracted from the descriptive information. For example, target feature information can be one or more combinations of time, location, people, products, prices, contact information, and purchase intentions reflected in the descriptive information. After extracting the target feature information, it can be populated into a preset object information table based on the correspondence between different types of target feature information and different information types in the preset object information table to obtain a target object information table. This target object information table records the target feature information corresponding to the target object, improving the efficiency of information recording for the target object.

[0063] In one embodiment, when the descriptive information includes an image, the image in the descriptive information can be processed using Optical Character Recognition (OCR). For example, the image can be distorted, denoised, and converted to grayscale to ensure text extraction accuracy and determine the image type. If the image type is a contract image, preset recognition targets such as "buyer's name," "contact number," and "product model" are located in the contract image, and the corresponding image text is extracted. If the image type is a screenshot image, text extraction is performed on the entire screenshot image to obtain the image text. When the descriptive information includes speech, the speech in the descriptive information can be processed using Automatic Speech Recognition (ASR) to obtain speech text. Optionally, a trained entity extraction model can be used to analyze and process one or more combinations of text, image text, and speech text in the descriptive information to identify preset entity objects corresponding to one or more combinations of text, image text, and speech text. Further, based on a preset correspondence between preset entity objects and target feature information, the identified preset entity objects can be mapped to target feature information. For example, the person entity "Mr. A" can be mapped to a customer name; the contact information entity "Phone 1XX********" can be mapped to a phone number field; the product entity "XX Product" can be mapped to a desired product; the time entity "This Weekend" can be mapped to a specific date range; and the task entity "Book with Family" can be mapped to a high-intent conversion task. Optionally, after extracting target feature information from the description information, the target feature information can be displayed to the user. The user can edit the target feature information, and after the user confirms that the target feature information is correct, the confirmed target feature information is filled into a preset object information table.

[0064] In existing target object information acquisition solutions, this is typically achieved by users manually filling out target object forms. However, this method is inefficient due to low input efficiency and user resistance (e.g., sales staff) lack of patience. Furthermore, users face complex and fast-paced work environments, and manually entering complete target object information (including contract number, long phone number, detailed address, etc.) is time-consuming. Moreover, communication between users and target objects often occurs online, during paper contract signing, or document verification, requiring users to frequently switch between multiple fragmented communication media and input forms. This manual transcription process is highly prone to errors in target object information entry. This application addresses this issue by extracting target feature information from the target object's description information and filling this information into a pre-defined target object information table. This eliminates the need for users to frequently switch between multiple fragmented communication media and input forms, ensuring accurate recording of target object information while achieving rapid data entry.

[0065] S260: Create an object follow-up task based on the target object information table and issue the object follow-up task to the object follow-up user.

[0066] For example, it is determined whether a preset task keyword exists in the target object information table. If the preset task keyword exists, an object follow-up task can be created based on the target object information table and issued to the object follow-up user. The object follow-up task is a task that the object follow-up user needs to follow up on regarding the target object. This application improves the efficiency of following up on target objects by automatically creating object follow-up tasks based on the target object information table and issuing them to the object follow-up user.

[0067] Optionally, the object follower can be the user who provides the description information of the target object, or other users (e.g., other users selected by the user who provides the description information). There can be one or more object followers.

[0068] In one embodiment, preset task keywords can be time keywords and action keywords. Time and action elements are automatically extracted from unstructured descriptive information and transformed into object follow-up tasks with timeline reminders. For example, if the target object information table contains time keywords (such as "tomorrow," "weekend," "day X," etc.) and action keywords (such as "follow-up visit," "delivery," "sample viewing," etc.), an object follow-up task can be generated based on the time keywords and action keywords, indicating that the relevant actions of the action keywords need to be followed up within the time range corresponding to the time keywords. The object follow-up task can also be associated with the corresponding target object information table or descriptive information. When viewing the object follow-up task, the user can also view the associated target object information table or descriptive information, improving the efficiency of following up on the target object.

[0069] S270: Generate personalized materials based on the editing operations of the user on the preset general materials in the preset general template pool, and save the personalized materials to the user's private customization pool.

[0070] In one embodiment, a general template pool for storing preset general materials and a private customization pool for storing personalized materials for different users can be set in a preset database. Personalized materials can be generated based on editing operations on the preset general materials. The materials provided in this application may include posters, video files, audio files, product promotional materials, and scenario-based scripts, where different scenario-based scripts can correspond to different business scenarios (e.g., customer entering the store, customer leaving the store, new customer scenario, returning customer scenario, etc.).

[0071] In this system, users of the materials can act as guides, selecting their current business scenario within the user interface. Within this scenario, they can choose either a general template pool or a private customization pool. The interface then displays preset general materials from the general template pool or personalized materials from the private customization pool, corresponding to the current business scenario. Users can select either preset general materials or personalized materials to view or perform other operations (such as editing, sharing, or saving). Users can quickly locate preset general materials in the general template pool or personalized materials in the private customization pool based on their business scenario, improving material location speed. Furthermore, users can utilize preset general materials or personalized materials generated based on preset general materials for business scenario communication, significantly enhancing the standardization and professionalism of their business communication.

[0072] In one embodiment, after a user selects a business scenario, personalized materials from the private customization pool can be displayed first. If the private customization pool is empty in the current business scenario, the user will be redirected to display preset general materials from the general template pool, thereby improving the efficiency of material viewing.

[0073] For example, after selecting and viewing the preset general materials in the general template pool, the material user can edit the preset general materials, and generate personalized materials in response to the material user's save operation, and save the personalized materials to the material user's private customization pool.

[0074] For example, users can modify, delete, or add text and / or images to preset general materials to create new personalized materials and save them to a private customization pool. When the preset general material is a poster, it can also respond to the user's poster generation request, obtain the user's information (such as profile picture, social media account QR code, contact information, affiliated store information, etc.), render and generate a poster exclusive to the user based on the user information and the poster template corresponding to the preset general material, and save it to the private customization pool.

[0075] This application manages preset general materials and personalized materials through a dual-pool customization mechanism of a general template pool and a private customization pool. It generates personalized materials based on the user's editing operations on the preset general materials in the preset general template pool and saves them to the private customization pool, thereby improving the efficiency of personalized material production.

[0076] In one possible embodiment, the business execution management method provided by this application may further include: intercepting the account change process of a preset user when an account change is detected; retrieving the preset user's first business data and a first business management entity set, wherein the first business management entity set is used to record the preset user's first business channel scope, and the preset user's functional permissions for the first business channel are determined based on the assigned role and / or position; determining a successor user, and inheriting the first business data and the first business management entity set to the successor user to update the successor user's second business data and second business management entity set, wherein the second business management entity set is used to record the successor user's second business channel scope, and the successor user's functional permissions for the second business channel are determined based on the assigned role and / or position.

[0077] In one embodiment, user accounts of multiple pre-recorded users are monitored, where different users correspond to different business data and business management entity sets. The system determines whether any users have experienced account changes. This application identifies users with account changes among the pre-recorded users as preset users, and identifies users among the pre-recorded users who inherit the business data and business management entity sets of the preset users as inheriting users. Inheriting users can be staff members of the internal management system or personnel from external channels (such as distributors, store managers, and sales staff from external channels).

[0078] The business management entity set (including a first business management entity set and a second business management entity set) provided in this application is used to record the scope of a user's business channels, that is, the scope of business channels that the user is responsible for. The business management entity set can be recorded through business channel identifiers. Business channels can be business regions, business stores, distributors, store managers, store employees, etc. Correspondingly, business channel identifiers can be business region numbers, business store numbers, distributor numbers, store manager numbers, store employee numbers, etc., where the number can be the corresponding ID information. For example, for regional manager A, who is responsible for store A, store B, and distributor C, and whose corresponding business channel identifiers are A1, B2, and C3 respectively, then his corresponding business management entity set can be represented as: [A1, B2, C3].

[0079] The business data provided in this application (including first business data and second business data) are business assets owned by the user. Optionally, the business data can be one or more combinations of the user's pending settlement performance, customer resources to be followed up, and unfinished business tasks (such as marketing tasks). Pending settlement performance can be understood as performance data generated by the user but not yet financially settled, such as unrealized earnings like commissions and bonuses corresponding to achieved sales performance. Customer resources to be followed up can be understood as customer information that the user is responsible for maintaining but has not yet completed conversion or service loop, including key business relationships such as potential customers and interested customers. Unfinished business tasks can be understood as marketing activities or tasks that the user is currently executing but have not yet completed, such as unfinished promotional activities, marketing tasks, and customer maintenance tasks. In one embodiment, the business data and business management entity set can be stored in a preset storage location (such as a preset database).

[0080] The account changes provided in this application can be due to the departure of a pre-defined user or the need to adjust the scope of business responsibilities of the pre-defined user (e.g., transferring all or part of the business channels they are responsible for). In one embodiment, when the management platform performs account changes on a pre-defined user (e.g., when an administrator performs account changes on a pre-defined user due to their departure or business changes, the management platform will issue a departure signal or perform a cancellation action), an account change process for the pre-defined user is initiated. This account change process will perform account change operations on the pre-defined user, such as deleting or updating the pre-defined user's first business data and first business management entity set.

[0081] For example, when an account change for a preset user is detected, the account change process for the preset user is intercepted, freezing the account change process for the preset user and activating the account change confirmation workflow for the preset user. Under the account change confirmation workflow, business data and business management entity sets are inherited from the preset user to the successor user.

[0082] Furthermore, the system retrieves the first business data of the preset user and the first business management entity set from the preset storage location. The first business management entity set records the first business channel scope of the preset user, and this scope reflects the range of data the preset user can manage (e.g., which business channels, distributors, stores, etc., data they can manage).

[0083] The functional permissions of the preset user to the first business channel under their responsibility provided in this application can be determined based on the assigned role and / or position. The functional permissions of the preset user to the first business channel under their responsibility can be understood as the permission to perform specific operations or access specific functional modules.

[0084] Further, the inheriting user is determined to inherit the first business data and the first business management entity set of the preset user. There can be one or more inheriting users. The inheriting user can be designated by the preset user's superior (e.g., a superior leader), designated by the preset user, or designated according to a preset inheriting user determination strategy. After determining the inheriting user, the first business data and the first business management entity set can be inherited to the inheriting user to update the inheriting user's second business data and the second business management entity set. The second business management entity set records the inheriting user's second business channel scope, which reflects the scope of data the inheriting user can manage (e.g., which business channels, distributors, stores, etc., data can be managed).

[0085] The functional permissions of the inherited user for the second business channel they are responsible for, as provided in this application, can be determined based on the assigned role and / or position. These permissions can be understood as the specific operations they can perform or the permissions to access specific functional modules. After the first business data and the first business management entity set are inherited by the inherited user, they are added to the inherited user's second business data and second business management entity set. At this point, the scope of business data and business channels managed by the inherited user increases. Even if an account change operation is performed on the default user, the default user's first business data and first business management entity set are no longer in an ownerless state. Deleting the default user from the organizational tree will not affect the continuation of related businesses. The inherited user can take over the default user's first business data and first business management entity set, effectively ensuring business continuity.

[0086] In one embodiment, different roles and / or positions can be pre-configured with different functional permissions. For example, after creating a login account for a user (including a default user and an inherited user), the user's login account and related basic information (e.g.,) can be encapsulated into an independent digital identity. Roles and / or positions can be assigned to the user, and a business management entity set can be created for the user based on their data permissions and business affiliation. For example, assigning a regional manager position to a user grants them the functional operation permissions corresponding to that position, such as viewing regional sales data and managing subordinate stores. Based on the user's business management entity set and the assigned role and / or position, the scope of data the user can manage can be determined, as well as the operations that can be performed on that scope based on the management method of the manageable data. This application achieves functional permission allocation by assigning roles and / or positions, decoupling the user's affiliation from the administrative organization (organizational tree), facilitating flexible adjustment of the permission scope according to business needs. Optionally, the assignment of a user's role and / or position can be triggered by a default user or the user's superior user.

[0087] In one embodiment, such as Figure 3 As shown in the provided organizational tree structure diagram, this application can divide the organizational tree into an internal organizational tree and an external channel tree. Optionally, different internal organizational nodes in the internal organizational tree can be mapped to digital identities corresponding to different internal personnel, realizing the association between different internal organizational nodes and different users. Similarly, different external channel organizations in the external channel tree can be mapped to digital identities corresponding to different external channels, realizing the association between different external channel nodes and different users. Specifically, different internal organizational nodes in the internal organizational tree can be mapped to one or more external channel nodes in the external channel tree based on the business management entity set corresponding to the digital identity. In this case, the user corresponding to the internal organizational node in the internal organizational tree has the permission to access the relevant data of the external channel node and its subordinate nodes recorded in the business management entity set. Furthermore, different external channel nodes in the external channel tree can also be mapped to one or more other external channel nodes in the external channel tree based on the business management entity set corresponding to the digital identity. In this case, the user corresponding to the external channel node in the external channel tree has the permission to access the relevant data of the external channel node and its subordinate nodes recorded in the business management entity set.

[0088] Figure 3 The diagram illustrates an internal organizational branch in an internal organizational tree and an external channel branch in an external channel tree. Within the internal organizational branch, the internal organizational nodes, from top to bottom, are associated with the group headquarters, offline sales centers, sales directors, sales regions, senior regional managers, regional managers, and channel sales / retail business positions. Similarly, within the external channel branch, the external channel nodes, from top to bottom, are associated with the sales regions, regions, distributor organizations, stores, store managers, and store staff. The business management entity set of the sales region in the internal organizational tree records the sales region identifier of the sales region in the external channel tree, meaning the sales region in the internal organizational tree has access to the relevant data of the sales region and its subordinate nodes in the external channel tree. Likewise, the business management entity set of the regional manager in the internal organizational tree records the distributor organization identifier of the distributor organization in the external channel tree, meaning the regional manager in the internal organizational tree has access to the relevant data of the distributor organization and its subordinate nodes in the external channel tree. Compared to the single data structure in related technologies that directly attaches users to static organizational tree nodes, this application establishes a multi-dimensional, interwoven, and separate data structure consisting of digital identity, role definition, functional positions, and business management entity sets. This decouples the administrative affiliation of personnel from the sales channels they are responsible for, enabling cross-level concurrent management data affiliation mapping to be directly associated through a flattened business management entity set without moving the administrative nodes of the organizational tree. Furthermore, it allows for the addition or deletion of the concurrent management scope of different personnel at any time without changing the organizational tree structure.

[0089] In one embodiment, inheriting the first business data and the first business management entity set to the inheriting user to update the inheriting user's second business data and the second business management entity set can be achieved by identifying completed first business data and ongoing first business data within the first business data. For example, completed first business data could be statistical reports and performance data that have occurred and are currently frozen, while ongoing first business data could be tasks in progress, customer data under management, etc.

[0090] Furthermore, the aforementioned completed first business data undergoes inheritance annotation processing (e.g., adding an annotation "The preset user has been inherited by the inheriting user" to the first business data). The completed first business data is locked based on the principle of historical integrity, thus achieving snapshot retention of the completed first business data. The aforementioned ongoing first business data is added to the inheriting user's second business data, and the first business management entity set is added to the inheriting user's second business management entity set. The inheriting user can execute tasks not completed by the preset user based on the inherited first business data, take over customer data previously managed by the preset user, and manage external channels previously managed by the preset user based on the inherited first business management entity set.

[0091] This application achieves more refined inheritance processing of the first business data and the first business management entity set by performing inheritance annotation processing on the completed first business data, adding the ongoing first business data to the second business data of the inheriting user, and adding the first business management entity set to the second business management entity set of the inheriting user. It also enables snapshot retention and transfer of the first business data and the first business management entity set, thereby improving the quality of business execution management.

[0092] After inheriting the first business data and the first business management entity set to the inheriting user to update the inheriting user's second business data and the second business management entity set, the process further includes: determining entity set difference data based on the original business management entity set and the updated business management entity set, wherein the business management entity set is either the first business management entity set or the second business management entity set; and updating the user access control list based on the entity set difference data, wherein the user access control list is used to record the business channels that the preset user or the inheriting user is responsible for.

[0093] After logging into their account, users can create a user access control list (MAC List) based on their business management entity set. This MAC List can be used to record the business channels that the user is responsible for. The MAC List can be recorded using the business channel identifier corresponding to the business channel.

[0094] When a user needs to access or modify data under a certain business channel, it can be determined whether the user's access control list records the corresponding business channel. If the user's access control list records the corresponding business channel, the user is allowed to access or modify the data under the corresponding business channel; otherwise, the user's access or modification of the data under the corresponding business channel is denied.

[0095] For example, for a preset user and / or an inherited user, entity set difference data is determined based on the original business management entity set and the updated business management entity set, wherein the entity set difference data can be used to reflect the changes in the updated business management entity set relative to the original business management entity set.

[0096] Furthermore, the user access control list is updated based on the entity set difference data. For a default user, updating the user access control list results in the removal of all or part of the business channels in the user access control list. For a default user, updating the user access control list results in the addition of business channels to the user access control list, or the user access control list remains unchanged (e.g., the inherited first business management entity set is within the scope of the second business management entity set).

[0097] In one embodiment, for a preset user, the original business management entity set and the updated business management entity set are the original first business management entity set and the updated first business management entity set, respectively. Specifically, when a preset user's account change is due to the user's departure, the preset user no longer has data management permissions and can be directly deleted from the user access control list. When a preset user's account change is due to an adjustment in business responsibility (e.g., transferring some first business data and / or part of the first business management entity set to the succeeding user), the entity set difference data can be determined to update the user access control list.

[0098] In one embodiment, for inherited users, the original business management entity set and the updated business management entity set are the second business management entity set before inheritance and the second business management entity set after inheritance, respectively. This application determines the entity set difference data based on the original and updated business management entity sets, and updates the user access control list based on this difference data. This allows for real-time updates of the business channels managed by the user, achieving efficient partial recalculation of data permissions based on the difference set. Compared to related technologies that require a full update of the user access control list, this approach, by extracting the entity set difference data when the business management entity set is added or removed due to inheritance, partially updates the user access control list, reducing the overhead of recursive database operations and achieving instantaneous response of the user access control list, thus improving business execution management efficiency.

[0099] In one embodiment, the business execution management method provided in this application determines entity set difference data based on the original business management entity set and the updated business management entity set. This can be achieved by determining entity set incremental data and entity set decrement data based on the original and updated business management entity sets. The entity set incremental data can be understood as data used to add new business channels. For example, the entity set incremental data is obtained by subtracting the business channel identifiers in the original business management entity set that are identical to those in the updated business management entity set from the updated business management entity set; that is, entity set incremental data = updated business management entity set - original business management entity set. The entity set decrement data can be understood as data used to remove business channels. For example, the entity set decrement data is obtained by subtracting the business channel identifiers in the updated business management entity set that are identical to those in the original business management entity set from the original business management entity set; that is, entity set decrement data = original business management entity set - updated business management entity set.

[0100] Accordingly, the business execution management method provided in this application updates the user access control list based on entity set difference data. This can be done by adding business channels to the user access control list based on entity set incremental data, or deleting business channels from the user access control list based on entity set decrement data.

[0101] For example, the business channel identifier recorded in the incremental data of the entity set is added to the user access control list, and the business channel identifier recorded in the decremented data of the entity set is removed from the user access control list, thereby updating the user access control list. This application determines the incremental data and decremented data of the entity set based on the original and updated business management entity sets, and updates the user access control list based on the incremental and decremented data, thereby improving the efficiency of user access control list updates while ensuring accurate updates.

[0102] In one embodiment, when determining the successor user, an inheritance designation request may be sent to a preset management user to determine the successor user designated by the preset management user based on the inheritance designation request. For example, after intercepting the account change process of a preset user, an inheritance designation request is sent to the preset management user, requesting the preset management user to designate a successor user for the preset user based on the inheritance designation request, and the successor user designated by the preset management user based on the inheritance designation request is determined.

[0103] In one embodiment, upon receiving a succession designation request, a pre-defined management user can select one or more users from a pool of users as successor users and send the designated successor user information to the business execution management device. The pre-defined management user can be the parent user of the pre-defined user or a pre-set system loss prevention administrator. For example, a pop-up window and to-do information can be pushed to the parent user or designated system loss prevention administrator, requesting the pre-defined management user to designate one or more successor users. This application ensures smooth business operation by sending a succession designation request to the pre-defined management user, allowing the pre-defined management user to determine the appropriate successor user.

[0104] In one possible embodiment, the service execution management method provided in this application sends an inheritance designation request to a preset management user, which may include: obtaining load bandwidth information and service area affiliation of multiple candidate users, determining a candidate successor user from the multiple candidate users based on the load bandwidth information and service area affiliation, and sending an inheritance designation request to the preset management user based on the candidate successor user, wherein the preset management user designates the successor user based on the candidate successor user.

[0105] For example, after intercepting the account change process of a preset user, the load bandwidth information and business region affiliation of multiple candidate users can be obtained. Based on the preset user's first business data, first business management entity set, and load bandwidth information and business region affiliation, one or more candidate users whose load bandwidth information and business region affiliation better match the first business data and first business management entity set to be inherited can be determined as candidate successor users. The load bandwidth information can reflect the candidate user's current business volume and the total business volume it can handle. The business region affiliation can reflect the candidate user's region or area affiliation. The business region affiliation can be determined based on the candidate user's pre-set area affiliation information or based on the area affiliation corresponding to each business channel in the candidate user's business management entity set. For example, if the current business volume plus the allocated first business data does not exceed the total business volume it can handle, and the business region affiliation matches the region or area affiliation corresponding to the first business management entity set, the corresponding candidate user can be designated as a candidate successor user. In one embodiment, the load bandwidth information and business region affiliation provided in this application can be one or more combinations of the corresponding user's current store size, daily activity level, and historical conversion metrics.

[0106] Optionally, the first service data, the first service management entity set, load bandwidth information, and service area affiliation can be sent to the trained candidate successor user determination model. The candidate successor user determination model analyzes and processes the first service data, the first service management entity set, load bandwidth information, and service area affiliation to obtain one or more candidate users as candidate successor users.

[0107] In one embodiment, after determining one or more candidate successor users, a succession designation request can be sent to a preset management user based on the one or more candidate successor users. The preset management user can designate one or more candidate successor users as successor users from among the one or more candidate successor users indicated in the succession designation request. In another embodiment, after receiving a succession designation request based on one or more candidate successor users, the preset management user can determine the successor user from among the one or more candidate successor users indicated in the succession designation request, or from among users other than the candidate successor users. This application determines candidate successor users from multiple candidate users based on load bandwidth information and service area affiliation. The preset management user can designate the successor user based on the candidate successor users, which improves the efficiency of successor user determination while balancing the service volume of the successor user and the affiliation scope of the inherited service, thus determining the successor user more rationally.

[0108] In one possible embodiment, the business execution management method provided in this application, after inheriting the first business data and the first business management entity set to the inheriting user to update the inheriting user's second business data and the second business management entity set, can also remove the interception of the account change process to perform account change operations on the preset user through the account change process. The account change operation on the preset user can be performed by deleting part or all of the inherited first business data and the first business management entity set of the preset user in a preset storage location, removing the preset user from the organizational tree, or canceling the preset user's account. A pre-emptive account change process interception is set up above the underlying account cancellation interface. When an employee account change signal is captured, a full asset scan for confirmation of rights and targeted inheritance and merging are triggered to protect the continuity of the indicator system and performance. This application intercepts the account change process of a preset user upon detecting an account change, retrieves the preset user's first business data and first business management entity set, where the first business management entity set records the preset user's first business channel scope. The preset user's functional permissions for the first business channel are determined based on assigned roles and / or positions. A successor user is identified, and the first business data and first business management entity set are inherited by the successor user to update the successor user's second business data and second business management entity set. The second business management entity set records the successor user's second business channel scope, where the successor user's functional permissions for the second business channel are determined based on assigned roles and / or positions. This decouples business channels from the organizational tree, eliminating the strong binding between business channels and users on the organizational tree. When a user account change occurs, a deep recursive traversal of the entire organizational tree is unnecessary; dynamic updates of business channel permissions can be achieved through inheritance of the business management entity set, effectively improving permission management efficiency.

[0109] In one embodiment, after inheriting the first business data and the first business management entity set to the inheriting user to update the inheriting user's second business data and the second business management entity set, the interception of the account change process can be lifted, and the account change operation can be performed on the preset user through the account change process. This account change operation on the preset user can be performed by deleting part or all of the inherited first business data and the first business management entity set of the preset user in a preset storage location, removing the preset user from the organizational tree, or canceling the preset user's account. A pre-emptive account change process interception is set up above the underlying account cancellation interface. When an employee account change signal is captured, a full asset scan for confirmation of rights and targeted inheritance and merging are triggered to protect the continuity of the indicator system and performance.

[0110] The above describes a process where assessment targets are created based on target parameter configurations, assigned to target execution users, and their business operation events in one or more preset business modules are monitored. These events are then normalized and mapped to the performance indicator mapping table of the assessment targets. The mapping table routes the data to target indicators, determines their completion values, and establishes the business processing progress of the target execution users based on these values. When the business processing progress meets preset warning rule triggering conditions, a business warning instance is created based on a preset differential suppression window. This instance is used for business warning processing. By normalizing the mapping of business operation events, unified processing of business processing progress across multiple preset business modules is supported. This allows for timely warnings of business anomalies while reducing alarm noise through the differential suppression window, improving business execution management effectiveness. Furthermore, by automatically creating object follow-up tasks based on the target object information table and issuing them to the target follow-up users, the efficiency of following up on target objects is improved. Furthermore, it manages preset general materials and personalized materials through a dual-pool customization mechanism of a general template pool and a private customization pool. Personalized materials are generated based on the user's editing operations on the preset general materials in the preset general template pool and saved to the private customization pool, thereby improving the efficiency of personalized material production.

[0111] Figure 4 A schematic diagram of the structure of a business execution management device provided in an embodiment of this application is given. (Reference) Figure 4 The business execution management device includes a target allocation module 41, a mapping processing module 42, a progress determination module 43, and an early warning processing module 43.

[0112] The system includes the following modules: Target Allocation Module 41, which creates assessment targets based on target parameter configuration and assigns them to target execution users; Mapping Processing Module 42, which monitors business operation events of target execution users in one or more preset business modules, normalizes and maps these events to the indicator mapping table of the assessment targets, routes them to target indicators through the indicator mapping table, and determines the indicator completion value of the target indicators; Progress Determination Module 43, which determines the business processing progress of target execution users based on the indicator completion value of the target indicators; and Early Warning Processing Module 43, which creates business early warning instances based on preset differentiated suppression windows when the business processing progress meets preset early warning rule triggering conditions, and performs business early warning processing through these instances.

[0113] The above describes a process where assessment targets are created based on target parameter configurations, assigned to target execution users, and their business operation events in one or more preset business modules are monitored. These events are then normalized and mapped to the performance indicator mapping table of the assessment targets. The mapping table routes the data to target indicators, determines their completion values, and establishes the business processing progress of the target execution users based on these values. When the business processing progress meets preset warning rule triggering conditions, a business warning instance is created based on a preset differentiated suppression window. This process handles business warnings through the normalized mapping of business operation events, supporting unified processing of business processing progress across multiple preset business modules. It provides timely warnings for business anomalies while reducing alarm noise through the differentiated suppression window, thereby improving the effectiveness of business execution management.

[0114] In one possible embodiment, the business execution management device further includes a constraint verification module, which is used for: Determine the target performance indicators and target users, and perform constraint verification on the target performance indicators based on preset indicator constraint rules. The indicator constraint rules are used to constrain the combination rules of the target performance indicators, including core indicator judgment rules, single-selection mutual exclusion constraint rules, and mixed compatibility rules. If the target performance indicators pass the constraint verification, the target parameter configuration is determined based on the target performance indicators and the target execution user.

[0115] In one possible embodiment, the target allocation module 41 creates assessment targets based on target parameter configuration and allocates the assessment targets to target execution users, including: If the target performance indicator in the target parameter configuration is a process-related performance indicator, create a corresponding business instance based on the target parameter configuration, and assign the business instance to the target execution user in the target parameter configuration; and / or If the target performance indicator in the target parameter configuration is not a process-related performance indicator, a corresponding target notification is generated based on the target parameter configuration and sent to the target execution user in the target parameter configuration.

[0116] In one possible embodiment, the mapping processing module 42 listens for business operation events of the target user in one or more preset business modules, including: The preset event adapter is used to listen for business operation events of the target user in one or more preset business modules. The preset event adapter includes one or more combinations of process-type event adapters, result-type event adapters and channel-type event adapters. The process-type event adapter is used to listen for process-type operation events in the pending business module, the result-type event adapter is used to listen for result-type operation events in the result-type business module, and the channel-type event adapter is used to listen for channel-type operation events in the external channel module.

[0117] In one possible embodiment, the business execution management device further includes an early warning follow-up module, which is used for: Create early warning follow-up services based on business early warning instances, and issue early warning follow-up services to early warning follow-up users; Update the alert status of the business alert instance based on the business status of the alert follow-up business.

[0118] In one possible embodiment, the business execution management device further includes an object recording module, which is used for: Obtain the descriptive information of the target object, and extract the target feature information from the descriptive information; The target feature information is filled into a preset object information table to obtain the target object information table; Create object follow-up tasks based on the target object information table, and issue object follow-up tasks to the object follow-up users.

[0119] In one possible embodiment, the business execution management device further includes a material management module, which is used for: Personalized materials are generated based on the user's editing operations on preset general materials in the preset general template pool; Save personalized assets to the user's private customization pool.

[0120] In one possible embodiment, the business execution management device further includes a permission management module, which is used for: If a predefined user's account changes are detected, the account change process for that user will be intercepted. Retrieve the first business data of the preset user and the first business management entity set, wherein the first business management entity set is used to record the first business channel scope of the preset user, and the functional permissions of the preset user to the first business channel under their responsibility are determined based on the assigned role and / or position. The successor user is determined, and the first business data and the first business management entity set are inherited by the successor user to update the successor user's second business data and the second business management entity set. The second business management entity set is used to record the scope of the successor user's second business channels. The functional permissions of the successor user for the second business channels they are responsible for are determined based on the assigned role and / or position.

[0121] In one possible embodiment, the permission management module is further configured to, after inheriting the first business data and the first business management entity set to the inheriting user to update the second business data and the second business management entity set of the inheriting user, remove the interception of the account change process and perform account change operation on the preset user through the account change process.

[0122] It is worth noting that in the above-described embodiments of the business execution management device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this application.

[0123] Figure 5 A schematic diagram of the structure of a business management system provided in an embodiment of this application is given. (Reference) Figure 5 The business management system includes business management services, business early warning services, object management services, material management services, and access control services. Users (e.g., through apps, web pages, or mini-programs) can access these services and request the corresponding services.

[0124] The business management service is used to create assessment targets based on target parameter configurations, assign assessment targets to target execution users, monitor business operation events of target execution users in one or more preset business modules, normalize and map business operation events to the indicator mapping table of assessment targets, route to target indicators through the indicator mapping table, and determine the indicator completion value of the target indicator; and determine the business processing progress of the target execution user based on the indicator completion value of the target indicator. The business alert service is used to create a business alert instance based on a preset differentiated suppression window when the business processing progress meets the preset alert rule triggering conditions, and to process the business alert through the business alert instance.

[0125] The business management service is also used to determine the target assessment indicators and target execution users before creating assessment targets based on target parameter configuration. It performs constraint verification on the target assessment indicators based on preset indicator constraint rules. The indicator constraint rules are used to constrain the combination rules of the target assessment indicators. The indicator constraint rules include core indicator judgment rules, single-selection mutual exclusion constraint rules, and mixed compatibility rules. If the target assessment indicators pass the constraint verification, the target parameter configuration is determined based on the target assessment indicators and target execution users.

[0126] The business management service creates performance targets based on target parameter configurations and assigns these targets to users who will execute them, including: If the target performance indicator in the target parameter configuration is a process-related performance indicator, create a corresponding business instance based on the target parameter configuration, and assign the business instance to the target execution user in the target parameter configuration; and / or If the target performance indicator in the target parameter configuration is not a process-related performance indicator, a corresponding target notification is generated based on the target parameter configuration and sent to the target execution user in the target parameter configuration.

[0127] The business management service listens for business operation events of the target user in one or more preset business modules, including: using preset event adapters to listen for business operation events of the target user in one or more preset business modules. The preset event adapters include one or more combinations of process event adapters, result event adapters, and channel event adapters. The process event adapter is used to listen for process operation events in the pending business module, the result event adapter is used to listen for result operation events in the result business module, and the channel event adapter is used to listen for channel operation events in the external channel module.

[0128] The business alert service is also used to create alert follow-up services based on the business alert instance after creating the business alert instance based on the preset differentiated suppression window, and to issue the alert follow-up services to the alert follow-up users; and to update the alert status of the business alert instance based on the business status of the alert follow-up services.

[0129] The object management service is used to obtain the description information of the target object and extract the target feature information from the description information; The target feature information is filled into a preset object information table to obtain the target object information table; Create object follow-up tasks based on the target object information table, and issue object follow-up tasks to the object follow-up users.

[0130] The material management service is used to generate personalized materials based on the editing operations of the user on the preset general materials in the preset general template pool; and to save the personalized materials to the user's private customization pool.

[0131] The access control service is used to intercept the account change process of a preset user when an account change is detected; retrieve the preset user's first business data and first business management entity set, wherein the first business management entity set records the preset user's first business channel scope, and the preset user's functional permissions for the first business channel are determined based on the assigned role and / or position; determine the successor user, and inherit the first business data and first business management entity set to the successor user to update the successor user's second business data and second business management entity set, wherein the second business entity set records the successor user's second business channel scope, and the successor user's functional permissions for the second business channel are determined based on the assigned role and / or position; and release the interception of the account change process, and perform the account change operation on the preset user through the account change process.

[0132] The above describes a process where assessment targets are created based on target parameter configurations, assigned to target execution users, and their business operation events in one or more preset business modules are monitored. These events are then normalized and mapped to the performance indicator mapping table of the assessment targets. The mapping table routes the data to target indicators, determines their completion values, and establishes the business processing progress of the target execution users based on these values. When the business processing progress meets preset warning rule triggering conditions, a business warning instance is created based on a preset differential suppression window. This instance is used for business warning processing. By normalizing the mapping of business operation events, unified processing of business processing progress across multiple preset business modules is supported. This allows for timely warnings of business anomalies while reducing alarm noise through the differential suppression window, improving business execution management effectiveness. Furthermore, by automatically creating object follow-up tasks based on the target object information table and issuing them to the target follow-up users, the efficiency of following up on target objects is improved. Furthermore, a dual-pool customization mechanism—a general template pool and a private customization pool—manages preset general and personalized materials. Personalized materials are generated based on user editing of preset general materials in the general template pool and saved to the private customization pool, improving the efficiency of personalized material creation. Business channels and the organizational tree are decoupled; business channels and users are no longer strongly bound to the organizational tree. When user account changes occur, deep recursive traversal of the entire organizational tree is unnecessary. Dynamic updates of business channel permissions can be achieved through inheritance of business management entity sets, effectively improving permission management efficiency.

[0133] This application also provides a business execution management device, which can integrate the business execution management apparatus provided in this application. Figure 6This is a schematic diagram of the structure of a business execution management device provided in an embodiment of this application. (Reference) Figure 6 The service execution management device includes: an input device 63, an output device 64, a memory 62, and one or more processors 61; the memory 62 is used to store one or more programs; when one or more programs are executed by one or more processors 61, the one or more processors 61 implement the service execution management method provided in the above embodiments. The input device 63, output device 64, memory 62, and processor 61 can be connected via a bus or other means. Figure 6 Taking the example of a connection between China and Israel via a bus.

[0134] The memory 62, as a computing device readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the business execution management method provided in any embodiment of this application (e.g., the target allocation module 41, progress determination module 43, and early warning processing module 43 in the business execution management device). The memory 62 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the device, etc. Furthermore, the memory 62 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 62 may further include memory remotely located relative to the processor 61, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0135] Input device 63 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 64 may include display devices such as a display screen.

[0136] The processor 61 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory 62, thereby realizing the above-mentioned business execution management method.

[0137] The business execution management apparatus, system, equipment, and computer provided above can be used to execute the business execution management method provided in any of the above embodiments, and have corresponding functions and beneficial effects.

[0138] This application embodiment also provides a storage medium for storing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute the business execution management method provided in the above embodiment. The business execution management method includes: creating assessment targets according to target parameter configuration, and assigning the assessment targets to target execution users; monitoring business operation events of target execution users in one or more preset business modules, normalizing and mapping the business operation events to the indicator mapping table of the assessment targets, routing to target indicators through the indicator mapping table, and determining the indicator completion value of the target indicators; determining the business processing progress of the target execution users based on the indicator completion value of the target indicators; and, when the business processing progress meets the preset early warning rule triggering conditions, creating a business early warning instance based on a preset differentiated suppression window, and performing business early warning processing through the business early warning instance.

[0139] Storage medium – any type of memory device or storage device. The term “storage medium” is intended to include: mounting media, such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disks or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. Furthermore, storage media may reside in a first computer system in which a program is executed, or may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term “storage medium” can include two or more storage media that may reside in different locations (e.g., in different computer systems connected via a network). Storage media may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0140] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the business execution management method provided above, but can also execute related operations in the business execution management method provided in any embodiment of this application.

[0141] The business execution management device, system, equipment, and storage medium provided in the above embodiments can execute the business execution management method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to the business execution management method provided in any embodiment of this application.

[0142] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments provided herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the claims.

Claims

1. A business execution management method, characterized in that, include: Based on the target parameter configuration, create assessment targets and assign the assessment targets to target execution users; Listen for business operation events of the target user in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment target, route to the target indicator through the indicator mapping table, and determine the indicator completion value of the target indicator. The business processing progress of the target user is determined based on the target indicator completion value; When the business processing progress meets the preset warning rule triggering conditions, a business warning instance is created based on a preset differentiated suppression window, and business warning processing is performed through the business warning instance.

2. The business execution management method according to claim 1, characterized in that, Before creating the assessment target based on the target parameters, the following is also included: The target performance indicators and target users are determined, and the target performance indicators are constrained and verified based on preset indicator constraint rules. The indicator constraint rules are used to constrain the combination rules of the target performance indicators, and the indicator constraint rules include core indicator judgment rules, single-selection mutual exclusion constraint rules, and hybrid compatibility rules. If the target performance indicators pass the constraint verification, the target parameter configuration is determined by the user based on the target performance indicators and the target.

3. The business execution management method according to claim 1, characterized in that, The step of creating assessment targets based on target parameters and assigning the assessment targets to target execution users includes: When the target performance indicator in the target parameter configuration is a process-related performance indicator, create a corresponding business instance according to the target parameter configuration, and assign the business instance to the target execution user in the target parameter configuration; and / or If the target performance indicator in the target parameter configuration is not a process-related performance indicator, a corresponding target notification is generated according to the target parameter configuration and sent to the target execution user in the target parameter configuration.

4. The business execution management method according to claim 1, characterized in that, The monitoring of the target user's business operation events in one or more preset business modules includes: The system utilizes preset event adapters to monitor business operation events of the target user in one or more preset business modules. The preset event adapters include one or more combinations of process-type event adapters, result-type event adapters, and channel-type event adapters. The process-type event adapter is used to monitor process-type operation events in the pending business module, the result-type event adapter is used to monitor result-type operation events in the result-type business module, and the channel-type event adapter is used to monitor channel-type operation events in the external channel module.

5. The business execution management method according to claim 1, characterized in that, After creating the business early warning instance based on the preset differential suppression window, the following is also included: Create an early warning follow-up service based on the aforementioned business early warning instance, and issue the early warning follow-up service to the early warning follow-up user; Update the warning status of the business warning instance according to the business status of the warning follow-up business.

6. The business execution management method according to claim 1, characterized in that, The business execution management method also includes: Obtain the description information of the target object, and extract the target feature information from the description information; The target feature information is filled into a preset object information table to obtain the target object information table; An object follow-up task is created based on the target object information table, and the object follow-up task is sent to the object follow-up user.

7. The business execution management method according to claim 1, characterized in that, The business execution management method also includes: Personalized materials are generated based on the user's editing operations on preset general materials in the preset general template pool; The personalized materials are saved to the private customization pool of the user who uses the materials.

8. The business execution management method according to claim 1, characterized in that, The business execution management method also includes: If a change in the account of a preset user is detected, the account change process of the preset user will be intercepted. Retrieve the first business data of the preset user and the first business management entity set, wherein the first business management entity set is used to record the first business channel scope of the preset user, and the functional permissions of the preset user to the first business channel under their responsibility are determined based on the assigned role and / or position; Determine the successor user, and inherit the first business data and the first business management entity set to the successor user to update the second business data and the second business management entity set of the successor user. The second business management entity set is used to record the scope of the second business channel of the successor user. The functional permissions of the successor user to the second business channel he is responsible for are determined based on the assigned role and / or position. Remove the interception of the account change process, and perform account change operations on the preset user through the account change process.

9. A business management system, characterized in that, The business management system includes business management services and business early warning services, wherein: The business management service is used to create assessment targets based on target parameter configuration, assign the assessment targets to target execution users; monitor the business operation events of the target execution users in one or more preset business modules, normalize and map the business operation events to the indicator mapping table of the assessment targets, route to the target indicators through the indicator mapping table, and determine the indicator completion value of the target indicators; and determine the business processing progress of the target execution users based on the indicator completion value of the target indicators. The business early warning service is used to create a business early warning instance based on a preset differentiated suppression window when the business processing progress meets the preset early warning rule triggering conditions, and to perform business early warning processing through the business early warning instance.

10. A business execution management device, characterized in that, include: Memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the business execution management method as described in any one of claims 1-8.

Images