A unified activity management method and system

Abstract

The application discloses a kind of unified activity management method and system, it is related to data processing technical field, the method includes creating basic questionnaire, creating activity, defining activity check plan, distributing activity, activity check, image recognition scheduling, check result back and query / download.The system includes basic module and core business module;Basic module includes point of sale library, scene library, permission module and activity type table;Core business module includes questionnaire management platform module, activity management module, activity distribution module, activity check result acceptance module, image recognition scheduling module, check result back reception module and check result viewing module.The application can integrate different activities together for inspection, improve the inspection efficiency;It can also uniformly interface various types of external execution tools to facilitate unified management;It can interface image recognition tool based on rule engine to realize automatic identification and judgment to activity scene picture, without relying on manual.

Description

Technical Field

[0001] This invention relates to the field of data processing, and more particularly to a unified activity management method and system. Background Technology

[0002] When FMCG companies conduct product promotion activities targeting point-of-sale channels, they often have requirements regarding the display of products at these channels. This typically refers to the requirements for product placement within the activity or its sub-activities at the point of sale. These activations are sub-activities of each activity. The monitoring of these activities requires manual inspection and judgment by sales representatives, store owners, or inspectors. Currently, the management methods and systems used in the industry are designed for single-type activities. That is, they are set up and distributed only for one type of activity, and then the activity scenario is manually checked, the results are judged, and the judgment is simultaneously uploaded to an execution tool, which then notifies the management system. This single-activity management approach cannot automatically judge the execution status of activities, nor can it uniformly manage various types of activities. It is inefficient and requires a significant investment of manpower and resources.

[0003] Therefore, those skilled in the art are dedicated to developing a unified activity management method and system to achieve unified and automated management of various types of activities, reduce reliance on human resources, and improve management efficiency. Summary of the Invention

[0004] In view of the above-mentioned deficiencies of the prior art, the technical problem to be solved by the present invention includes:

[0005] (1) How to automatically determine the execution status of activities and obtain the determination results through an efficient and automated method that does not rely on manual judgment;

[0006] (2) How to provide automatic reporting functions for different objects of different activities;

[0007] (3) How to manage different types of activities in a unified manner, how to build a unified questionnaire management platform, and how to build a unified scenario list;

[0008] (4) How to ensure compatibility with different photo-taking methods of different execution tools.

[0009] To achieve the above objectives, the present invention provides a unified activity management method, comprising the following steps:

[0010] Step 1: Create a basic questionnaire;

[0011] Step 2: Create an activity; including creating visual elements under the activity, setting the association between the visual elements and at least one photo scene, setting the association between the visual elements and at least one of the basic questionnaires, setting activity rules, and setting the association between the output items of the activity rules and the visual elements;

[0012] Step 3: Define the activity inspection plan; including setting the sales points, execution tools, and time range corresponding to the activity;

[0013] Step 4: Distribute the activity; this includes informing the execution tool of the details of the activity through any one of the following methods: API interface, batch file, or shared data; the details include: at least one activity that the sales point needs to participate in, the visual merchandising of each of the at least one activity, the photo shooting scene, the basic questionnaire, and the display requirements and success images corresponding to the visual merchandising.

[0014] Step 5, Activity Check; includes using the execution tool to take pictures of the scene, filling out the basic questionnaire, and notifying the unified activity management system of the taken scene photos and the answers to the basic questionnaire via an interface.

[0015] Step 6, Image Recognition Scheduling; This includes the unified activity management system using judgment logic to control how to perform image recognition and how to call the rule engine based on the received scene photos, the answers to the basic questionnaire, and the data generated by the inspection visits, so as to finally obtain the inspection results of the activity based on the rule engine.

[0016] Step 7: Check the results; this includes obtaining the check results from the rule engine and entering them into the database of the unified activity management system, and pushing the check results to the execution tool or providing a query API interface for the execution tool to query the check results.

[0017] Furthermore, the basic questionnaire has a questionnaire ID, which is configured as the primary key for managing the basic questionnaire.

[0018] Furthermore, the execution tool is configured as a front-end tool for performing the activity check, including an app and a mini-program.

[0019] Furthermore, the AND operation value of the time range and the execution tool is configured as a unique key for the activity plan.

[0020] Furthermore, it also includes querying / downloading the inspection results of one of the activities.

[0021] The present invention also provides a unified activity management system, including a basic module and a core business module;

[0022] The basic modules include a sales point library, a scene library, a permission module, and an activity type table;

[0023] The core business modules include a questionnaire management platform module, an activity management module, an activity distribution module, an activity inspection result receiving module, an image recognition scheduling module, an inspection result feedback receiving module, and an inspection result viewing module.

[0024] The questionnaire platform module includes a questionnaire list, and the fields of the questionnaire list include creation time, questionnaire ID, questionnaire name, questionnaire question type, questionnaire dimension, scenario type, and business unit.

[0025] The activity management module includes a page for creating inspection items, a page for configuring visual elements, a page for setting completion, a page for visual element mapping, and a page for setting rectification requirements.

[0026] The activity distribution module includes an inspection plan module and an activity distribution interface; the inspection plan module is configured to set an activity inspection plan, including configuring the execution tool and time page and configuring the sales point page; the activity distribution interface includes request parameters and return parameters;

[0027] The inspection result receiving module includes an interface for uploading photos of the activity scene / answers to the basic questionnaire, as well as an interface for ending the activity inspection;

[0028] The image recognition scheduling module is configured to control how to perform image recognition and how to call the rule engine based on the received scene photos, the basic questionnaire answers, and the data generated by the inspection visits, so as to obtain the inspection results of the activity based on the rule engine.

[0029] Furthermore, the sales point database includes a sales point details table, an organizational structure table, and a market segmentation table;

[0030] The sales point details table includes fields for serial number, zero demand, Taikoo corresponding field, interface field name, data type, field length, and whether it is required.

[0031] The organization structure table includes configuration table fields, interface field name field, data type field, field length field, and whether a field is required.

[0032] The market segmentation table includes configuration table fields, interface field name field, data type field, field length field, whether field is required field, data retrieval logic field, and remarks field.

[0033] Furthermore, the scene library includes a scene data table; the scene data table includes a scene type field, a scene type name field, a scene type secondary name field, and a scene code field.

[0034] Furthermore, the inspection result feedback receiving module is configured to input the inspection results into the database of the unified activity management system, and to push the inspection results to the execution tool or provide a query API interface for the execution tool to query the inspection results.

[0035] Furthermore, the inspection result viewing module is configured to query and download the inspection results of an activity.

[0036] Compared with the prior art, the beneficial technical effects of the present invention are as follows:

[0037] (1) By building a unified scenario list, it is easy to merge the inspection items of different activities, realize scenario aggregation, and improve inspection efficiency.

[0038] (2) By providing API interfaces, external execution tools can be uniformly connected to facilitate unified management.

[0039] (3) It can automatically identify activity scene photos through image recognition, automatically push the rule engine through rule engine scheduling, and obtain the calculation results of the rule engine.

[0040] (4) It can record the results of the engine and provide a function to download the results reports of different column objects for different activities.

[0041] The following will further explain the concept, specific structure, and technical effects of the present invention in conjunction with the accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention. Attached Figure Description

[0042] Figure 1 This is a flowchart of a preferred embodiment of the present invention;

[0043] Figure 2 This is a preferred embodiment of the point-of-sale details table of the present invention;

[0044] Figure 3 This is an organizational structure table of a preferred embodiment of the present invention;

[0045] Figure 4 This is a market segmentation table of a preferred embodiment of the present invention;

[0046] Figure 5 This is the data composition in the scene library of a preferred embodiment of the present invention;

[0047] Figure 6 This is an example of a system menu according to a preferred embodiment of the present invention;

[0048] Figure 7 This is a page representing a preferred embodiment of the present invention;

[0049] Figure 8 This is a page representing a preferred embodiment of the present invention;

[0050] Figure 9 This is a preferred embodiment of the permission settings for each page of the present invention;

[0051] Figure 10 This is a page displayed by the questionnaire platform module of a preferred embodiment of the present invention.

[0052] Figure 11 This is a preferred embodiment of the creation and inspection item page of the present invention;

[0053] Figure 12 This is a configuration visualization page of a preferred embodiment of the present invention;

[0054] Figure 13 This is a settings completion page according to a preferred embodiment of the present invention;

[0055] Figure 14 This is a vivid mapping page of a preferred embodiment of the present invention;

[0056] Figure 15 This is a preferred embodiment of the present invention, showing the setting and rectification requirements page;

[0057] Figure 16 This is a preferred embodiment of the configuration execution tool and time page of the present invention;

[0058] Figure 17 This is a preferred embodiment of the configuration point-of-sale page of the present invention;

[0059] Figure 18 This is a schematic diagram of the activity distribution interface definition according to a preferred embodiment of the present invention;

[0060] Figure 19 This is a schematic diagram illustrating the interface definition for uploading activity scene photos / basic questionnaire answers according to a preferred embodiment of the present invention;

[0061] Figure 20 This is a schematic diagram of the activity check end interface definition according to a preferred embodiment of the present invention;

[0062] Figure 21 This is a list page of inspection results according to a preferred embodiment of the present invention. Detailed Implementation

[0063] The following description, with reference to the accompanying drawings, illustrates several preferred embodiments of the present invention to make its technical content clearer and easier to understand. The present invention can be embodied in many different forms, and the scope of protection of the present invention is not limited to the embodiments mentioned herein.

[0064] Current technologies for managing supplier promotional activities typically involve setting up and distributing tasks for individual activities, followed by manual evaluation of the results, which are then uploaded to an execution tool and notified to the management system. This approach is inefficient, especially with three promotional activities. Furthermore, the reliance on manual evaluation for each activity lacks automated methods for determining results. To address these shortcomings, improvements are needed in the following areas.

[0065] First, if different activities are to be integrated for inspection, there needs to be a corresponding aggregation method, such as building a unified questionnaire management platform and a unified scenario list, so as to merge the inspection items of different activities and improve inspection efficiency.

[0066] Secondly, manual inspections will use a variety of external tools, such as suppliers’ own apps and mini-programs. Different merchants’ activities will involve multiple tools, so it is necessary to provide a way to connect to these external tools in a unified manner for unified management.

[0067] Third, it is necessary to adopt certain methods to connect with some automated tools, especially the rule-based image recognition tools developed by the inventors themselves, to achieve automatic recognition and judgment of activity scene images, without relying on manual labor.

[0068] Based on the above ideas, this invention proposes a unified activity management method and system. For example... Figure 1 The flowchart shown is for this method, which includes the following steps:

[0069] 1. Create a basic questionnaire

[0070] When using tools to check multiple activities, situations may arise where multiple activities have identical questionnaires. To improve processing efficiency, it's unnecessary to process each activity's questionnaire separately; instead, questionnaire aggregation, or merging, is performed. Therefore, a unified questionnaire is needed, managed using the questionnaire ID as the primary key. This way, when a sales point has multiple activities with the same questionnaire ID, questionnaire aggregation can be performed, improving processing efficiency. To achieve this technical effect, in this method, the basic questionnaire has a questionnaire ID, and the questionnaire ID is configured as the primary key for managing the basic questionnaire.

[0071] 2. Create an activity

[0072] "Activity" refers to a product promotion activity conducted by FMCG companies targeting point-of-sale channels, often with requirements regarding the product's display performance at these channels. Activity types include short-term agreement activities, long-term agreement activities, and non-agreement activities. "Visual merchandising" refers to the sub-activities within each activity, uniformly defined as "visual merchandising" according to the client's perspective. Each activity has multiple sub-activities (i.e., visual merchandising), and the inspection requirements, including the required photo scenes and the basic questionnaires to be completed, are all based on visual merchandising. Typically, each visual merchandising can have multiple scenes, meaning the sub-activity needs to capture multiple scenes. Each visual merchandising can also have multiple basic questionnaires. Therefore, in this step, it's necessary to establish the relationship between visual merchandising and the photo scenes, and the relationship between visual merchandising and the basic questionnaires. Furthermore, to ultimately determine whether a sub-activity (i.e., visual merchandising) is qualified, in addition to setting activity rules, it's also necessary to bind the relationship between rule engine output items and visual merchandising. This is because sometimes some rule output items are only used for statistical purposes and are not necessary conditions for determining whether visual merchandising is qualified; therefore, it's necessary to bind the necessary rule engine output items.

[0073] In summary, to achieve the aforementioned technical effects, the "Creating an Activity" step includes creating visual elements under the activity, setting the association between the visual elements and at least one photo scene, setting the association between the visual elements and at least one basic questionnaire, setting activity rules, and setting the association between the output items of the activity rules and the visual elements.

[0074] 3. Define the activity inspection plan

[0075] Simply creating an event only provides an event definition; at this stage, the event cannot proceed to the execution and inspection phase because it's unknown which sales outlets will run the event within which timeframes, and which execution tool will be used for inspection. Therefore, the first step is to define an event inspection plan.

[0076] First, defining the activity inspection plan requires setting up sales points.

[0077] Secondly, because multiple execution tools can perform checks within the same time frame, or the same execution tool can perform checks across different time periods, from a database perspective, activity plans from different execution tools within the same time frame are stored as multiple activity check plan records in the database. Similarly, activity plans from the same execution tool within different time frames are also stored as multiple activity check plan records in the database. Therefore, both the execution tool and the time frame information must be specified to uniquely identify a corresponding activity check plan record. In other words, the AND operation value of the time frame and the execution tool is the unique key of the activity check plan. By setting a unique key, data duplication is avoided, ensuring that the AND operation value of the execution tool and the time frame in the system is not repeated. This guarantees that no two activities will be exactly the same in the defined activity check plans; all activities will be different, ensuring that the system manages and executes activity check plans uniformly.

[0078] In summary, defining an event plan includes setting the corresponding sales points, execution tools, and time range for the event; the AND operation value of the time range and execution tools is the unique key of the event plan.

[0079] 4. Distribution activities

[0080] After defining the activity check plan, the next step is to distribute the plan to the execution tool. Distribution can be done either through non-aggregated sending or aggregated push notifications.

[0081] Non-aggregated distribution refers to sending activity inspection plans to the execution tool via API interfaces, pre-written batch files, or shared data. Because the execution tool sometimes needs to operate offline, it's desirable for staff to initialize and enter inspection data daily when logging into the system. When sending activity plans to the execution tool via API interfaces, the API content can include detailed information such as point-of-sale activities, merchandising, scenarios, basic questionnaires, display requirements, and successful images. After receiving this detailed information, the execution tool automatically selects which activity inspection plans to participate in and displays their scenarios and basic questionnaires for inspection.

[0082] Aggregated push notifications refer to combining various scenarios and basic questionnaires from different activity inspection plans together, essentially merging the scenarios and questionnaires from different activities and directly pushing them to the execution tool. In this case, the execution tool cannot control which activity inspection plans it participates in; instead, it passively receives the information on which scenarios and basic questionnaires to display for inspection. For example, a sales point needs to perform activity inspections and has created two activity inspection plans for it. Activity inspection plan A corresponds to activity A, which requires inspecting three scenarios: KO freezers, customer-owned freezers, and shelves, and requires inspecting three questionnaires: 001, 003, and 005. Activity inspection plan B corresponds to activity B, which requires inspecting three scenarios: KO freezers, KO floor displays, and shelves, and requires inspecting three questionnaires: 001, 002, and 003. When pushed to the execution tool via aggregation, it will directly tell the execution tool that it needs to inspect four scenarios: KO freezers, KO floor displays, customer-owned freezers, and shelves, plus four questionnaires: 001, 002, 003, and 005.

[0083] In summary, the distribution activity involves informing the execution tool of the activity details via any one of the following methods: API interface, batch file, or shared data. These details include: at least one activity that the sales point needs to participate in, the visual merchandising for each of the at least one activity, the photo-taking scenario, the questionnaire, and the display requirements and success images corresponding to the visual merchandising.

[0084] The distribution campaign also includes aggregating various scenarios and basic questionnaires from different activity inspection plans, that is, merging the scenarios and questionnaires from different activities and pushing them directly to the execution tool for inspection.

[0085] 5. Activity Inspection

[0086] The activity check includes site visits where staff use execution tools to photograph the scene, complete a basic questionnaire, and, at the end of the check, notify the unified activity management system via an interface of the photographed scene photos and the completed questionnaire answers. If the activity was distributed to the execution tool in a non-aggregated manner in the previous step, it is also necessary to specify which activity and which activity the photographed scene belongs to. If the activity was distributed to the execution tool in an aggregated manner in the previous step, the activity management system must also be notified after the visit, and supplementary fields can be used to inform the system which activities were checked during the aggregate check.

[0087] 6. Image recognition scheduling

[0088] The unified activity management system uses logic to control how to perform image recognition and how to call the rule engine based on the scene photos uploaded by the execution tools, the answers to the basic questionnaires, and the data generated during the visit (such as the sales points visited), in order to ultimately obtain the results of the activity inspection.

[0089] For scene photos uploaded by the execution tool, image recognition is required by default, except for supplementary images for the basic questionnaire (which are controlled by special fields). Since there are multiple activities within a store, there are two approaches to the scene photos and questionnaire answers collected by the execution tool: one is to collect data from all activities; the other is to collect data from only some activities since some activities haven't been officially implemented yet. Correspondingly, determining which activities the currently completed visit belongs to generally falls into two modes: one is not to disclose information, which defaults to all activity plans associated with the current sales point at that time; the other is that the execution tool has disclosed which activities the scene photos and questionnaire answers belong to. If the uploaded scene photos belong to multiple different activities, the rule engine is called multiple times for each activity to calculate and check the results. Therefore, one visit will generate multiple rule engine results corresponding to multiple different activities.

[0090] 7. Inspection results return

[0091] The rule engine calculation results obtained in the previous step are entered into the database of the unified activity management system. This database contains a table named `engine_result`, which stores the results calculated by the rule engine.

[0092] For execution tools that require push notifications of inspection results, the results are pushed to the execution tool. For execution tools without a push mechanism, a query API is provided, which the execution tool calls to obtain the inspection results calculated by the rule engine. Since the relationship between the output items of the activity rules and the vividness is set in the "Create Activity" step, the inspection results are generally presented to the execution tool in this relationship manner.

[0093] 8. Viewing the inspection results

[0094] After obtaining the inspection results calculated by the rule engine, a way needs to be provided for people to view and download them. Since the output items to be checked are different for each activity, the output columns of the inspection results for each activity are also different. Therefore, only the inspection results of one activity can be selected for viewing or downloading at a time.

[0095] To put the aforementioned unified activity management method into practice, this invention provides a unified activity management system, comprising a basic module and a core business module. The basic module includes a sales point database, a scenario database, a permissions module, and an activity type table. The core business module includes a questionnaire management platform module, an activity management module, an activity distribution module, an activity inspection result receiving module, an image recognition scheduling module, an inspection result feedback receiving module, and an inspection result viewing module. These are described in detail below.

[0096] I. Basic Modules

[0097] The basic modules include a sales point database, a scenario database, a permissions module, and an activity type table.

[0098] 1. Sales Point Database

[0099] Since the distribution of promotional activities ultimately targets sales points, a sales point database needs to be built first. This database includes a sales point details table, an organizational structure table, and other related data tables (such as a city tier table and a market segmentation table). The sales point database connects to the client's sales point integration module to achieve automatic updates of sales point master data. The sales point details table is updated with a full table initialization and additional updates for the next updated day at midnight each day. Incremental updates are determined when the updatetime field of a record in the table is the previous day. During incremental updates, the primary key ID of the sales point details table is used to determine if the ID does not exist in the original table. If the ID does not exist in the original table, the incremental data is inserted as new data into the original table. If the ID exists in the original table, the new incremental data overwrites the old data in the original table. The organizational structure table, city tier table, and market segmentation table are updated with a full overwrite.

[0100] like Figure 2 The table shown is a sales point details table. The fields in this table include: serial number, zero-needle requirement, corresponding Taikoo field, interface name, data type, field length, and whether it is required.

[0101] like Figure 3 The table shown is the organization structure table. The fields in this table include configuration table fields, interface name fields, data type fields, field length fields, and whether fields are required.

[0102] like Figure 4 The table shown is a market segmentation table. The fields in this table include configuration table fields, interface name fields, data type fields, field length fields, required field fields, data retrieval logic fields, and remarks fields.

[0103] 2. As described in the scene library

[0104] Because scenarios need to be aggregated, and the rule engine supports different judgments for different scenarios, a unified scenario definition, i.e., a scenario library, is required. Scenarios include major categories and minor categories, where the major and minor categories are business-specific definitions. Major categories include freezers, shelves, floor displays, etc., while minor categories include KO freezers, Pepsi freezers, etc. Since the scenario definitions are unified and initial, and rarely changed subsequently, the scenario library can exist directly in the system as a database. The scenario library includes a scenario data table. The fields in this table include a scenario type field, a scenario type name field, a scenario type sub-name field, and a scenario code field. For example... Figure 5 The diagram shows the data structure in the scene library.

[0105] 3. Permissions Module

[0106] Considering that the unified activity management system proposed in this invention is a business system, all pages require access control. Specifically, this includes menu permissions, button permissions, and data segmentation permissions. This system obtains permission codes and role attributes by connecting to the client's permission system. Access control within the system's pages is implemented based on these permission codes and role attributes. Menu and button permissions are controlled based on permission codes, specifically including menu list permissions, function viewing permissions, and function editing permissions. Data segmentation is controlled based on the organizational structure attributes of the roles; the central service department has viewing permissions for all data, but local factories can only see their own data.

[0107] When a user logs in, the system obtains the user's menu permission code, button permission code, and organizational structure. It first determines whether the user is a central branch of a client or a subsidiary.

[0108] The menu list that users can see in the unified backend is controlled by their menu permission codes. Users without permission codes cannot see other online menus. Figure 6 The image shows an example of a system menu.

[0109] Each page's buttons are divided into those with view functionality and those with edit functionality; additional functional categories can be added as needed. Users with the permission code for the view buttons on that page can click the buttons with view functionality, such as... Figure 7 Click the "View" button on the page shown to view relevant information. Users with the permission code for the edit buttons on this page can click the buttons with editing functions, such as... Figure 7 Use the "New" button on the page shown to edit the newly created inspection plan.

[0110] Based on page requirements, on some pages, users can use their central government service account to query all data, but a subsidiary account can only view its own data, such as... Figure 8As shown, the Zhejiang branch's account can only see the Zhejiang branch's own inspection plans.

[0111] like Figure 9 As shown, the event list for each page and the corresponding permission code for that event are listed.

[0112] 4. Activity Type Table

[0113] Because different types of activities need to be defined separately, an activity type table is required, which can exist in a database. For example, a table named `standard` can be created, with activity type as one of its attribute fields. Activity types can include protocol-based short-term activities, protocol-based long-term activities, and non-protocol-based activities. New activity types can be added to the activity type table as needed, which can be achieved by maintaining the database. For example, a data table can be used to maintain the values ​​of activity types, and these values ​​can be set as follows: protocol-based long-term protocol, protocol-based short-term protocol, non-protocol INE check, non-protocol 3P check, etc.

[0114] II. Core Business Modules

[0115] The core business modules include a questionnaire management platform module, an activity management module, an activity distribution module, an activity inspection result receiving module, an image recognition scheduling module, an inspection result feedback receiving module, and an inspection result viewing module.

[0116] 1. Questionnaire Management Platform Module

[0117] like Figure 10 The image shown is the page displayed by the questionnaire platform module. The questionnaire platform module includes a list of questionnaires, which includes basic information such as creation time, questionnaire ID, questionnaire name, questionnaire question type, questionnaire dimensions, scenario type, and affiliated business unit. Basic questionnaires include scenario-based questionnaires and point-of-sale questionnaires. The question types for basic questionnaires include multiple choice, true / false, optional fill-in-the-blank, and fill-in-the-blank questions. Based on whether image recognition is possible, basic questionnaires are further divided into IR (image recognition) questionnaires and non-IR questionnaires. The former refers to questionnaires that need to be filled out when the store owner does not allow inspectors to take photos, i.e., when inspection can only be performed manually. For scenario-based questionnaires, because aggregation based on scenarios is sometimes necessary, each scenario questionnaire needs to be bound to a specific scenario subcategory, such as KO freezers, Pepsi freezers, etc.

[0118] Considering that modifications to the basic questionnaire once it is activated may affect the uploading of questionnaire answers, it is stipulated that basic questionnaires cannot be modified after activation. If you wish to change the questionnaire, you can create a new basic questionnaire.

[0119] 2. Activity Management Module

[0120] like Figure 11-14 As shown, the activity management module includes pages for creating inspection items, configuring visual merchandising, setting completion, mapping visual merchandising, and setting rectification requirements. These pages function to create activities, create visual merchandising within activities, add questionnaires under visual merchandising, set activity rules, and bind the output items of activity rules to the relationships between visual merchandising. Activity attributes include name, activity type, and description; visual merchandising attributes include name, corresponding photo-taking scenarios, corresponding questionnaires (including IR and non-IR questionnaires), descriptions of visual merchandising display requirements, and successful visual merchandising images.

[0121] 3. Activity Distribution Module

[0122] like Figure 15-18 As shown, the activity distribution module includes an inspection plan module and an activity distribution interface. The inspection plan module is configured to set up activity inspection plans, including a page for configuring execution tools and timelines, and a page for configuring sales points. Figure 15 As shown, the inspection plan list displays existing activity inspection plans. You can click the "New" button to add a new inspection plan. Figure 16 and 17 As shown, the configuration execution tool and time page and the configuration sales point page allow for settings of individual inspection plans. These settings include inspection items, inspection time, execution tool, sales point, the organizational structure of the sales point, and whether the sales point has a freezer, etc. The sales point settings support importing a list of sales points or distributing them to various sets of AND or NOT attributes. For example, as... Figure 17 When the activity is selected to be distributed to the Hangzhou area and the retail channel, the system will select all sales points in the Hangzhou area under the Zhejiang BU (Business Unit) and the sales point channel group as the retail channel from the sales point database. If the activity is selected to be distributed to the Hangzhou area or the retail channel, the system will select all sales points in the Hangzhou area under the Zhejiang BU or the sales point channel group as the retail channel from the sales point database.

[0123] Figure 18 The request and return parameters defined in the activity distribution interface are displayed.

[0124] Generally, an activity can have multiple inspection plans at the same time, but these plans must be executed using different tools, i.e., simultaneous multi-tool inspection. Alternatively, multiple inspection plans can be executed by the same tool at different times, i.e., phased inspection.

[0125] Under normal circumstances, an activity can have multiple inspection plans at the same time, but these must be executed using different tools, i.e., simultaneous multi-tool inspection. Alternatively, the same tool can have multiple plans at different times, i.e., phased inspection.

[0126] 4. Activity Inspection Result Receiving Module

[0127] The activity inspection results receiving module includes interfaces for uploading photos of the activity scene / answers to basic questionnaires, as well as an interface for ending the activity inspection. For example... Figure 19 The image shows the request and return functions defined in the interface for uploading photos of event scenes / basic questionnaire answers. Figure 20 As shown, the request and return functions defined in the activity check completion interface are displayed.

[0128] 5. Image recognition scheduling module

[0129] The image recognition scheduling module is configured to control how to perform image recognition and how to call the rule engine (i.e., which data to send to the rule engine, how many times to send to the rule engine, and which rules to send, etc.) based on the received activity scene photos, the answers to the basic questionnaire, and the data generated during the visit, so as to obtain the final inspection results of the activity based on the rule engine.

[0130] For scene photos uploaded by the execution tool, image recognition is required by default, except for supplementary images for the basic questionnaire (which are controlled by special fields). Determining which activities the currently concluded visit belongs to generally falls into two modes: one where the execution tool has already indicated which activities it belongs to; and one where it hasn't. If not indicated, it defaults to all activity plans associated with the current sales point at that time. If the uploaded scene photos belong to multiple different activities, the rule engine is called multiple times for each activity to calculate and check the results. Therefore, one visit will generate multiple rule engine results corresponding to multiple different activities.

[0131] 6. Inspection result return receiving module

[0132] like Figure 21 As shown, the inspection result feedback receiving module includes a page displaying a list of inspection results. This module inputs the rule engine's calculation results into the database of the unified activity management system. For execution tools that require push notifications of inspection results, the inspection results are pushed to the execution tools. For execution tools without a push mechanism, a query API is provided, allowing the execution tools to retrieve the inspection results calculated by the rule engine by calling the query API themselves. Because the relationship between the output items of the activity rules and the visualizations is set, the inspection results are generally presented to the execution tools in this relational manner.

[0133] 7. Inspection Result Viewing Module

[0134] The inspection results viewing module includes an inspection results report viewing page and an inspection results report download page. After obtaining the inspection results calculated by the rule engine, a way needs to be provided for users to view and download them. Since the output items to be checked are different for each activity, the output columns of the inspection results for each activity are also different. Therefore, only the inspection results of one activity can be selected for viewing or downloading at a time.

[0135] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A unified activity management method, characterized in that, Includes the following steps: Step 1: Create a basic questionnaire; the basic questionnaire has a questionnaire ID, which is configured as the primary key for managing the basic questionnaire; Step 2: Create an activity; this includes creating sub-activities under the activity, where each sub-activity is a sub-activity of the activity; setting the association between the sub-activities and at least one photo scene; setting the association between the sub-activities and at least one basic questionnaire; setting activity rules; and setting the association between the output items of the activity rules and the sub-activities; wherein, only the rule engine output items that are necessary conditions for determining whether the sub-activities are qualified are bound to the sub-activities, and other rule engine output items are only used for statistics; Step 3: Define the activity inspection plan; this includes setting the sales points, execution tools, and time range corresponding to the activity; the AND operation value of the time range and the execution tool is configured as the unique key of the activity inspection plan; Step 4: Distribute the activity; this includes informing the execution tool of the activity details via API interface, batch files, or shared data. The details include: at least one activity the sales point needs to participate in, the visual merchandising, photo scene, basic questionnaire for each of the at least one activity, and the display requirements and success image corresponding to the visual merchandising. Support for aggregating scenes and questionnaires from multiple activities and pushing them to the execution tool; the aggregation includes: deduplicating and merging scenes and basic questionnaires from different activity inspection plans using a unified scene library and questionnaire ID, and directly pushing them to the execution tool. The execution tool cannot control which activity inspection plans it participates in; instead, it passively receives the photo scenes and basic questionnaires to be displayed from the unified activity management system for inspection. When multiple activities with the same questionnaire ID are present at the same sales point, questionnaire aggregation and merging of questionnaires for inspection are performed. Step 5, Activity Check; includes using the execution tool to take pictures of the scene, filling out the basic questionnaire, and notifying the unified activity management system of the taken scene photos and the answers to the basic questionnaire via an interface. Step 6, Image Recognition Scheduling: This involves the unified activity management system using the received scene photos, the answers to the basic questionnaire, and the data generated during the inspection visit to control how image recognition is performed and how the rule engine is invoked, ultimately obtaining the activity inspection results based on the rule engine. Specifically, for scene photos uploaded by the execution tool, image recognition is required by default, except for supplementary images from the basic questionnaire. The process involves determining the activity to which the currently completed visit belongs: if the execution tool does not specify the activity to which the currently completed visit belongs, it is assumed that the currently completed visit belongs to all activity plans associated with the current sales point at that time; if the execution tool has specified the activity to which the currently completed visit belongs, it is determined according to the specified activity; if the uploaded scene photos belong to multiple different activities, the rule engine is invoked multiple times for each activity to calculate the inspection results, resulting in multiple rule engine calculation results for each activity in a single activity inspection visit, each corresponding to a different activity. Step 7: Check Result Feedback; This includes obtaining the check results from the rule engine and entering them into the database of the unified activity management system, and pushing the check results to the execution tool or providing a query API interface for the execution tool to query the check results; wherein, the rule engine calculation results are entered into the engine_result table in the database of the unified activity management system; based on the association between the output items of the set activity rules and the visualizations, the check results are presented to the execution tool according to the association between the output items of the activity rules and the visualizations; The unified activity management system includes a basic module and a core business module; the basic module includes a sales point database, a scenario database, a permission module, and an activity type table; the scenario database includes a scenario data table; the scenario data table includes a scenario type field, a scenario type name field, a scenario type secondary name field, and a scenario code field.

2. The unified activity management method as described in claim 1, characterized in that, The execution tool is configured as a front-end tool to perform the activity check, including apps and mini-programs.

3. The unified activity management method as described in claim 1, characterized in that, It also includes querying / downloading the inspection results of the activity.

4. A unified activity management system, characterized in that, The system is used to implement the method as described in any one of claims 1-3, and the system includes a basic module and a core business module; The basic modules include a sales point library, a scene library, a permission module, and an activity type table; The core business modules include a questionnaire management platform module, an activity management module, an activity distribution module, an activity inspection result receiving module, an image recognition scheduling module, an inspection result feedback receiving module, and an inspection result viewing module. The questionnaire management platform module includes a questionnaire list, and the fields of the questionnaire list include creation time, questionnaire ID, questionnaire name, questionnaire question type, questionnaire dimension, scenario type, and business unit to which it belongs; The activity management module includes a page for creating inspection items, a page for configuring visual elements, a page for setting completion, a page for visual element mapping, and a page for setting rectification requirements. The activity distribution module includes an inspection plan module and an activity distribution interface; the inspection plan module is configured to set an activity inspection plan, including configuring the execution tool and time page and configuring the sales point page; the activity distribution interface includes request parameters and return parameters; The inspection result receiving module includes an interface for uploading photos of the activity scene / basic questionnaire answers, and an interface for ending the activity inspection; The image recognition scheduling module is configured to control how to perform image recognition and how to call the rule engine based on the received scene photos, the basic questionnaire answers, and the data generated by the inspection visits, so as to obtain the inspection results of the activity based on the rule engine.

5. The unified activity management system as described in claim 4, characterized in that, The sales outlet database includes a sales outlet details table, an organizational structure table, and a market segmentation table; The sales point details table includes fields for serial number, zero demand, Taikoo corresponding field, interface field name, data type, field length, and whether it is required. The organization structure table includes configuration table fields, interface field name field, data type field, field length field, and whether a field is required. The market segmentation table includes configuration table fields, interface field name field, data type field, field length field, whether field is required field, data retrieval logic field, and remarks field.

6. The unified activity management system as described in claim 4, characterized in that, The scene library includes scene data tables; The scenario data table includes a scenario type field, a scenario type name field, a scenario type secondary name field, and a scenario code field.

7. The unified activity management system as described in claim 4, characterized in that, The inspection result feedback receiving module is configured to input the inspection results into the database of the unified activity management system, and to push the inspection results to the execution tool or provide a query API interface for the execution tool to query the inspection results.

8. The unified activity management system as described in claim 4, characterized in that, The inspection results viewing module is configured to query and download the inspection results of an activity.

Images