Supplier comprehensive management method and system

Abstract

The invention relates to a supplier comprehensive management method and system, and the method comprises the following steps: carrying out the structured arrangement of original order data, and forming structured order data; determining an order transfer node to which the structured order data belongs according to a preset order transfer rule, and performing state marking on the structured order data according to the order transfer node to generate marked state order data; state information in the data is pushed to a corresponding supplier, the supplier receiving state information is obtained, feedback content of the supplier receiving state information is collected, and supplier feedback information is formed; according to the feedback information, state updating is carried out on the original marked state order data to obtain updated order data; and finally, performing visualization processing on the updated order data, generating an order state tracking graph, and realizing full-process dynamic tracking and display, thereby solving the technical problems of information fault and communication cost increase caused by the fact that the order state cannot be flexibly adjusted according to actual feedback in the traditional technology.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of supplier management, in particular to a supplier comprehensive management method and system. BACKGROUND

[0002] In the current complex and changeable supply chain environment, the management efficiency of enterprises on suppliers directly affects the overall operation performance. With the surge in order quantity and the increasing refinement of business processes, the traditional supplier management method gradually exposes problems such as response lag, information asymmetry, and state update not in time. Especially in the order execution process, the lack of accurate identification and dynamic tracking of key flow nodes often puts enterprises in a passive position when coordinating resources and responding to unexpected situations. Therefore, a new management mechanism that can realize real-time perception, intelligent judgment, and efficient coordination is urgently needed to improve the transparency and agility of the entire supply chain.

[0003] In the prior art, most supplier management systems still rely on manual intervention or static logic based on rules for state judgment, which is difficult to adapt to the processing needs of high-frequency and heterogeneous order data. On the one hand, the original order data format is disordered and the field is seriously missing, which directly restricts the accuracy of subsequent analysis and decision-making; on the other hand, even if some systems introduce automated processes, they are often limited to preset paths and cannot adjust the order state flexibly according to actual feedback, causing information gaps and rising communication costs. More importantly, the state perception and feedback mechanism of the supplier side is weak, making it difficult for enterprises to form a closed-loop management, further weakening the overall coordination ability of the supply chain. SUMMARY

[0004] The technical problem solved by the present application is to provide a supplier comprehensive management method and system, which solves the technical problem that the traditional technology cannot adjust the order state flexibly according to actual feedback, causing information gaps and rising communication costs.

[0005] To solve the above technical problems, the supplier comprehensive management method adopted by the present application comprises the following steps: Structuring the original order data to obtain structured order data, and judging the order flow node of the structured order data through a preset order flow rule to obtain an order flow node; Based on the order flow node, the structured order data is marked to obtain marked state order data; Based on the marked state order data, state information is pushed to the corresponding supplier to obtain supplier received state information, and the supplier received state information is collected to obtain supplier feedback information; Based on the supplier feedback information, the marked state order data is updated to obtain updated order data, and the updated order data is visually displayed to obtain an order state tracking diagram.

[0006] Further, the order original data is structured and arranged to obtain structured order data, including: The order original data is uniformly processed in data format to obtain uniform format order data, and the uniform format order data is positioned in a key field to obtain key field position information; Based on the key field position information, the uniform format order data is extracted to obtain preliminary key information, and the preliminary key information is converted by a preset field mapping rule to obtain structured order data.

[0007] Further, the structured order data is judged by a preset order flow rule to obtain an order flow node, including: The preset order flow rule is parsed to obtain a node flow sequence and a node trigger condition, and an order attribute set of the structured order data is extracted; Based on the node trigger condition, the order attribute set is matched and determined by a preset Rete rule inference model to obtain a condition matching result, and the structured order data is determined based on the condition matching result and the node flow sequence to obtain an order flow node.

[0008] Further, the structured order data is marked based on the order flow node to obtain marked state order data, including: The node attribute information of the order flow node is analyzed to obtain node attribute information, and the core information of the structured order data is extracted; Based on the node attribute information, the core information is matched to obtain an order state identifier, and the structured order data is marked based on the order state identifier to add the order state identifier to the corresponding position of the structured order data to obtain marked state order data.

[0009] Further, the corresponding supplier is pushed based on the marked state order data to obtain supplier received state information, including: The marked state order data is extracted to obtain order state key elements, and the communication mode of the supplier is collected to obtain supplier communication information; Based on the supplier communication information, information encapsulation is performed on the order state key elements, the order state key elements are encapsulated according to a preset communication format, encapsulated state information is obtained, the encapsulated state information is pushed through a communication mode of the corresponding supplier, and supplier received state information is obtained.

[0010] Further, the supplier received state information is fed back to obtain supplier feedback information, including: The response time of the supplier received state information is recorded to obtain supplier response duration data, and the content integrity of the supplier received state information is checked to obtain a content integrity identifier; Based on the content integrity identifier, the supplier response duration data is screened, if the content integrity identifier is complete information, the corresponding supplier response duration data is retained; If the content integrity identifier is information missing, the corresponding supplier response duration data is removed to obtain screened response data, and the screened response data is integrated to obtain the supplier feedback information.

[0011] Further, based on the supplier feedback information, the marked state order data is updated to obtain updated order data, including: The supplier feedback information is analyzed to obtain supplier execution progress data, and the order progress requirement data of the marked state order data is extracted to obtain order progress requirement data; The supplier execution progress data and the order progress requirement data are compared and analyzed to obtain progress difference data, and the progress difference data is difference type determined to obtain a difference type identifier; Based on the difference type identifier, the marked state order data is updated; If the difference type identifier is progress ahead, the order state in the marked state order data is updated to an ahead execution state; If the difference type identifier is progress lag, the order state in the marked state order data is updated to a lag execution state; If the difference type identifier is progress consistent, the order state in the marked state order data is updated to a normal execution state to obtain updated order data.

[0012] The application also provides a supplier comprehensive management system, including: A judgment module is configured to structure the order original data to obtain structured order data, and judge the structured order data through a preset order circulation rule to obtain an order circulation node. A marking module is configured to mark the structured order data based on the order flow node to obtain marked state order data; A pushing module is configured to push state information to the corresponding supplier based on the marked state order data to obtain supplier received state information, collect feedback of the supplier received state information to obtain supplier feedback information; An updating module is configured to update the marked state order data based on the supplier feedback information to obtain updated order data, and visually display the updated order data to obtain an order state tracking diagram.

[0013] The application further provides a computer device comprising a memory and a processor, the memory storing a computer program, and the processor executes the computer program to realize the steps of any one of the above methods.

[0014] The application further provides a computer readable storage medium storing a computer program, and the computer program is executed by the processor to realize the steps of any one of the above methods.

[0015] The above scheme structures and arranges order original data to obtain structured order data, judges the structured order data based on a preset order flow rule to obtain an order flow node, marks the structured order data based on the order flow node to obtain marked state order data, pushes state information to the corresponding supplier based on the marked state order data to obtain supplier received state information, collects feedback of the supplier received state information to obtain supplier feedback information, updates the marked state order data based on the supplier feedback information to obtain updated order data, and visually displays the updated order data to obtain an order state tracking diagram, which solves the technical problem that the traditional technology cannot flexibly adjust the order state according to actual feedback, causes information discontinuity and rising communication cost, realizes dynamic correction of the order state based on the supplier feedback information, and forms a closed-loop management logic of "pushing-feedback-updating". This mechanism effectively avoids the state lag or information island problem, and ensures that the data in the system is always consistent with the actual business progress. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0017] Figure 1This is a schematic diagram of the steps of a supplier integrated management method in one embodiment of the present invention; Figure 2 This is a structural block diagram of a supplier integrated management system in one embodiment of the present invention; Figure 3 This is a schematic block diagram of the structure of a computer device according to an embodiment of the present invention.

[0018] The objectives, features, and advantages of this invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0020] Specifically, the supplier integrated management method in this embodiment includes the following steps: like Figure 1 As shown, Figure 1 This invention provides a supplier integrated management method, comprising the following steps: Step S1: The original order data is structured to obtain structured order data, and the flow nodes of the structured order data are determined by the preset order flow rules to obtain the order flow nodes.

[0021] Specifically, the higher-level step of "structuring the raw order data to obtain structured order data" involves parsing non-standardized order text (such as PDFs, emails, or Excel snippets) from ERP or purchasing systems, using a large model to identify key fields such as order number, material code, delivery date, and quantity, and mapping them to a unified data template to complete the structuring. Subsequently, "determining the order flow node by judging the flow node of the structured order data through preset order flow rules" is a further processing of the structured order data output from the previous step. That is, based on the business rules configured within the enterprise (for example, "if the delivery date is ≤3 days away and the status is 'confirmed', then proceed to the 'urging delivery' node"), each order is matched to the current stage to determine its order flow node.

[0022] Step S2: Based on the order flow nodes, the structured order data is marked with a status to obtain marked status order data.

[0023] Specifically, the order flow node determined in the previous step (such as "to be confirmed", "in production", "shipped") is taken as an input condition, and a preset state mapping table is matched, so as to add a corresponding state label to each piece of structured order data; for example, if the flow node of an order is determined to be "close to delivery date without shipment", the system will automatically mark its state as "delay risk" to form the marked state order data.

[0024] Step S3, based on the marked state order data, the corresponding supplier is pushed the state information, the supplier receives the state information, and the supplier feedback information is collected.

[0025] Specifically, after the aforementioned "marked state order data" is generated, the system will automatically push the corresponding state information, such as "order #20251234 current state is 'delay risk'", through the message channel (such as email, SMS or supplier portal interface) that the enterprise has accessed according to the supplier identifier (such as supplier code or contact information) contained therein, which forms the "supplier received state information"; then, the system listens to the reply content of the supplier in the specified channel, whether it is to click the confirmation link, fill in the delay reason form, or upload the production progress screenshot, and collects and analyzes these response contents into structured "supplier feedback information".

[0026] Step S4, based on the supplier feedback information, the marked state order data is updated, the updated order data is obtained, and the updated order data is visually displayed to obtain the order state tracking diagram.

[0027] Specifically, in the foregoing process, the system has obtained "supplier feedback information", for example, a supplier replies to Order #20251234 with a status of "delay risk" that "the arrival of raw materials is delayed, and the expected delivery date is extended by 5 days". At this time, the step of "updating the status of the marked order data based on the supplier feedback information" is triggered: the system first analyzes the key elements in the feedback content (such as the new delivery date, the reason code), and then writes these information into the corresponding fields of the original "marked order data", such as changing the status from "delay risk" to "delayed", and updating the planned delivery date, thereby generating "updated order data". This operation is not simply overwritten, but is checked through a pre-set state transition logic table to ensure that the state change complies with business rules - for example, the "shipped" state cannot be rolled back to "in production". Next, "visually displaying the updated order data" means inputting this batch of data into a front-end chart engine (such as ECharts or D3.js), dynamically drawing the stage of each order according to the time axis and supplier dimension, and finally forming an "order status tracking chart". In the chart, the current node distribution, delay proportion and historical change trajectory of multiple orders under a certain supplier can be directly observed.

[0028] In specific embodiments, the structuring and organizing of the order raw data to obtain structured order data comprises: performing data format uniformity processing on the order raw data to obtain uniform format order data, and performing key field positioning on the uniform format order data to obtain key field position information; extracting key information from the uniform format order data based on the key field position information to obtain preliminary key information, and performing field standardization conversion on the preliminary key information based on a pre-set field mapping rule to obtain structured order data.

[0029] Specifically, in this method, the overarching step of "structuring the original order data to obtain structured order data" is broken down into several operable sub-processes. First, the system receives original order data from different channels—which may be scanned PDFs, Excel spreadsheets, or even free text in email bodies—and then performs "data format unification processing." For example, it converts PDFs to plain text using OCR recognition, or merges the contents of multiple worksheets in an Excel spreadsheet into a single row, ultimately outputting "unified format order data," typically in the form of a string with line breaks or a standard JSON object. Next, the system uses a locator trained on a large model (such as a finely tuned LayoutLM) to scan this unified format order data, identifying semantic regions such as "order number," "material name," and "delivery date," and recording their start and end offsets in the text, thereby generating "key field location information." With this location information, the original values ​​can be extracted from the unified format order data to form "preliminary key information," such as extracting "2025-12-30" as a candidate delivery date value from offset [120, 135]. However, the extracted content may still have format differences (such as "30 / 12 / 2025" or "December 30, 2025"). Therefore, further standardization based on preset field mapping rules is required. For example, for the "Delivery Date" field, the system calls the regular expression template library to convert it into the "YYYY-MM-DD" format. For the "Material Code", the system uses an internal code lookup table to map the supplier's private code to the enterprise standard code. After this conversion, all fields conform to the predefined data structure, ultimately forming "structured order data".

[0030] In a specific embodiment, the step of determining the flow nodes of the structured order data through preset order flow rules to obtain the order flow nodes includes: The preset order flow rules are parsed to obtain the node flow order and node triggering conditions, and the order attribute set of the structured order data is extracted. Using a pre-defined Rete rule reasoning model, the order attribute set is matched based on node triggering conditions to obtain a matching result. Based on the matching result and the node flow order, the node affiliation of the structured order data is determined to obtain the order flow node.

[0031] Specifically, first, the preset order flow rule is analyzed to obtain the node flow sequence and node trigger condition, which is the first step in the upper scheme. In this process, extracting the order attribute set in the structured order data is the key, which lays the foundation for subsequent matching judgment. By comparing the node trigger condition with the order attribute set through the Rete rule inference model, this process is based on the efficient pattern matching mechanism of the Rete algorithm, and the purpose is to determine whether the order meets the trigger condition of a specific flow node, which is a specific refinement of the above elements.

[0032] Next, after determining the condition matching result, the structured order data should be attributed to which order flow node according to the node flow sequence obtained before. The "node flow sequence" mentioned here is actually an abstract description of the order processing flow. Specifically, it is a series of steps or stages defined according to business logic. For example, in the e-commerce order processing scenario, this may include ordering, payment, delivery, and receipt. Each link has its specific trigger condition, such as payment success as the trigger condition for converting from ordering to delivery. Therefore, when the attribute set of a certain order (such as payment status) meets the trigger condition of a certain node, the order is assigned to the corresponding flow node.

[0033] To better understand this process, let's consider a specific example: Suppose there is an online bookstore, and when a customer completes the payment, the system checks whether the order meets the paid condition (one of the node trigger conditions), and if it does, the order is marked as "paid" and enters the next flow node - ready for delivery. In this case, the application of the "Rete rule inference model" is reflected in how the system efficiently filters all orders that meet the conditions and automatically updates their status.

[0034] In addition, it should be noted that the specific implementation of the operation "condition matching judgment on the order attribute set based on the node trigger condition through the preset Rete rule inference model, to obtain the condition matching result" is as follows: the system first extracts the "node trigger condition" (such as "delivery date The current date ≤ 3 and the order status = 'confirmed' ") into a rule node in the Rete network, and each condition clause is disassembled into an alpha node (for single-field matching) and a beta node (for multi-condition combination) to build a complete rule matching network; at the same time, the "order attribute set" (such as {order status: "confirmed", delivery date: "2025-12-30", material priority: "high"} ) extracted from the "structured order data" is input into the Rete network as a fact. The Rete engine uses its memoization and incremental matching mechanism to recalculate the matching path only for the changed attributes, avoiding full recalculation - for example, when the delivery date is updated, only the alpha branch related to the date is activated. If all the conditions of a rule are met at the same time under the current facts, the rule is activated and added to the agenda, and the corresponding result is the "condition matching result", for example, the "prompt delivery" rule hit. The entire process is completely based on the standard Rete algorithm implementation, and technical personnel can load the above rules and facts using open-source rule engines such as Drools and CLIPS to reproduce the matching and decision logic without additional custom reasoning mechanisms. Taking order #20251234 as an example, its attributes meet "delivery date ≤ 3 days and status 'confirmed'", and the Rete network will output the result of the successful condition matching, providing the basis for subsequent node attribution determination.

[0035] In specific embodiments, the structured order data is marked based on the order flow node to obtain marked state order data, including: The node attribute information is obtained by performing node attribute analysis on the order flow node, and the core information of the structured order data is extracted; The core information is matched based on the node attribute information to obtain an order state identifier, and the structured order data is marked based on the order state identifier to add the order state identifier to the corresponding position of the structured order data to obtain the marked state order data.

[0036] Specifically, the overarching step of "marking the status of the structured order data based on the order flow nodes to obtain marked status order data" is broken down into a series of executable sub-processes in actual operation. First, the system performs "node attribute analysis" on the identified "order flow nodes" (e.g., "delivery expediting"), that is, reading the metadata corresponding to the node from a preset node configuration table, such as node type, risk level, and whether manual intervention is required, to form "node attribute information." Simultaneously, the system extracts fields directly related to status determination from the "structured order data," such as order number, current delivery date, supplier ID, and material category, to constitute "core information." Next, the system compares and matches the aforementioned "core information" with the rule conditions based on the status mapping rules in the "node attribute information"—for example, "if the node is 'delivery expediting,' the status is marked as 'delay risk'; if it is 'shipped,' the status is marked as 'in transit'"—to determine a unique "order status identifier." This step is not a simple table lookup, but may involve multiple conditional judgments. For example, a high-priority material may be marked as "high-risk delay" under the "urging delivery" node, while ordinary materials are only marked as "delay risk". Once the "order status tag" is determined, the system writes it as a new field (such as "order_status_tag") to a specified position in the original "structured order data", usually appended to the end of the JSON object or inserted into the corresponding column in the database, ultimately generating "marked status order data".

[0037] In a specific embodiment, the step of pushing status information to the corresponding supplier based on the marked status order data to obtain the supplier's received status information includes: Information elements are extracted from the marked order data to obtain key elements of the order status, and information on the supplier's communication methods is collected to obtain supplier communication information; Based on the supplier communication information, the key elements of the order status are encapsulated. The key elements of the order status are encapsulated according to a preset communication format to obtain encapsulated status information. The encapsulated status information is then pushed to the supplier through the corresponding supplier's communication method to obtain the supplier's received status information.

[0038] Specifically, the overarching operation of "pushing status information to the corresponding supplier based on the marked status order data and obtaining the supplier's receipt status information" is broken down into several closely linked sub-steps in practice. First, the system extracts fields directly related to status communication from the "marked status order data," such as order number, current "order status identifier" (e.g., "delay risk"), original delivery date, and material name, forming "key elements of order status." Simultaneously, the system queries the supplier's master data table to obtain the supplier's pre-registered communication preferences—which may be their WeChat ID, designated email address, SMS phone number, or the address of their accessed EDI interface. This constitutes "supplier communication information." Next, depending on the communication channel, the system calls the corresponding "preset communication format" to encapsulate the "key elements of order status": for example, when sending to an email, it fills in the content using an HTML template to generate the email body; when sending via SMS, it compresses it into "[Order #20251234] Status Update: Delay Risk, Original Delivery Date 2025-12-30, Please Confirm"; if using EDI, it packages it into a standard message using ANSI X12 or XMLSchema. After encapsulation, the system calls the corresponding communication module (such as SMTP client, SMS gateway API or AS2 transmission service) to send the "encapsulated status information" to the designated channel of the supplier. Once the message is successfully delivered (such as receiving an SMS receipt or email read receipt), it is considered that the push is completed, and the interaction log is recorded as the "supplier reception status information".

[0039] In a specific embodiment, the step of collecting feedback on the supplier's received status information to obtain supplier feedback information includes: The response time of the supplier's received status information is recorded to obtain supplier response duration data, and the content integrity of the supplier's received status information is checked to obtain a content integrity identifier. The supplier response time data is filtered based on the content completeness identifier. If the content completeness identifier indicates that the information is complete, the corresponding supplier response time data is retained. If the content is marked as missing information, the corresponding supplier response time data is removed to obtain filtered response data. The filtered response data is then integrated to obtain supplier feedback information.

[0040] Specifically, the overarching step of "collecting feedback on the supplier's receipt status information and obtaining supplier feedback information" is broken down into three stages in actual operation: response time recording, content verification, and data filtering and integration. The system first retrieves the delivery timestamp of each "supplier receipt status information" message from the message middleware or log database and continuously monitors the response events of the corresponding channel. Once it receives content returned by the supplier (such as an email reply, form submission, or API callback), it immediately records the response time, and subtracts the two to obtain the "supplier response time data." Simultaneously, the system performs a "content integrity check" on the response content: for example, if the preset requirement is that the feedback must include two fields, "new delivery date" and "reason for delay," then it uses regular expression matching or structured parsing to determine if they are complete. If complete, the "content integrity identifier" is marked as "information complete"; otherwise, it is marked as "information missing." Next, the system filters the aforementioned "supplier response time data" based on this identifier—only when the "content completeness identifier" is "information complete" is the corresponding response time record retained; otherwise, even if the supplier replies "received" within 2 hours but does not provide valid business information, the record and its response time data are also removed. The "filtered response data" formed after this round of filtering is usually stored in a structured form, such as {order number: "20251234", new delivery date: "2026-01-05", reason for delay: "raw material shortage", response time: 4.2 hours}, and is finally summarized as "supplier feedback information".

[0041] In a specific embodiment, the marked status order data is updated based on supplier feedback information to obtain updated order data, including: The supplier feedback information is parsed to obtain supplier execution progress data, and the order progress requirements are extracted from the marked status order data to obtain order progress requirement data. By comparing and analyzing the supplier's execution progress data and the order progress requirement data, the difference is calculated to obtain progress difference data, and the difference type is determined to obtain a difference type identifier. The status update operation is performed on the marked status order data based on the difference type identifier; If the difference type is marked as "advanced", then the order status in the marked status order data will be updated to "advanced execution status". If the difference type is identified as delayed, the order status in the marked status order data will be updated to delayed execution status; If the difference type is identified as progress consistency, the order status in the marked status order data will be updated to normal execution status, resulting in updated order data.

[0042] Specifically, the overarching operation of "updating the status of marked order data based on supplier feedback to obtain updated order data" is implemented in three stages: progress parsing, difference comparison, and status rewriting. The system first extracts structured content from the "supplier feedback information," such as "50% complete" or "expected delivery on January 5, 2026" filled in by the supplier in a form. This is then converted into quantifiable "supplier execution progress data" using preset parsing rules (such as keyword matching or numerical extraction). Simultaneously, the system reads the agreed-upon milestone requirements from the original "marked order data," such as "material preparation completed on day 3, production completed on day 7," forming "order progress requirement data." The system then compares these two sets of data—if the original plan was to complete all production by day 5, but the supplier reported only 60% completion on day 5, the "progress difference data" is calculated as "40% behind"; if production is completed ahead of schedule, it is recorded as a positive difference. Next, based on preset thresholds (e.g., an absolute difference ≥ 10% is considered significant), the system determines the "Difference Type Identifier" as "Lagging," "Ahead of Schedule," or "Consistent." Once the identifier is determined, the corresponding status update logic is triggered: if it is "Ahead of Schedule," the order status field in the "Marked Status Order Data" is changed from its original value (e.g., "Delay Risk") to "Ahead of Schedule Execution Status"; if it is "Lagging," it is updated to "Lagging Execution Status"; if there is no significant deviation, it is set to "Normal Execution Status." Taking order #20251234 as an example, its original status was "Delay Risk," the supplier reported a new delivery date of 2026-01-05, the system compared it with the original scheduled 2025-12-30 and determined it to be lagging, so it updated the status to "Lagging Execution Status," and finally generated the "Updated Order Data."

[0043] Please see Figure 2 , Figure 2 This is a schematic diagram of the framework of an embodiment of the supplier integrated management system of this application. Figure 2 As shown, the supplier integrated management system includes a judgment module 1, which is used to structure and organize the original order data to obtain structured order data, and judge the flow nodes of the structured order data according to the preset order flow rules to obtain the order flow nodes; a marking module 2, which is used to mark the status of the structured order data based on the order flow nodes to obtain marked status order data; a push module 3, which is used to push status information to the corresponding suppliers based on the marked status order data to obtain supplier reception status information, and collect feedback on the supplier reception status information to obtain supplier feedback information; and an update module 4, which is used to update the status of the marked status order data based on the supplier feedback information to obtain updated order data, and visualize the updated order data to obtain an order status tracking graph.

[0044] Reference Figure 3 This invention also provides a computer device whose internal structure can be as follows: Figure 3 As shown, the computer device includes a processor, memory, display screen, input device, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database stores the data corresponding to this embodiment. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements the above-described method.

[0045] Those skilled in the art will understand that Figure 3 The structures shown are merely block diagrams of some structures related to the present invention and do not constitute a limitation on the computer devices on which the present invention is applied.

[0046] An embodiment of the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described method. It is understood that the computer-readable storage medium in this embodiment can be a volatile readable storage medium or a non-volatile readable storage medium.

[0047] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the present invention and embodiments can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual-rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM, etc.

[0048] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0049] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0050] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus implementations described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0051] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0052] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0053] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0054] If the technical solution of this application involves personal information, the product using this technical solution has clearly informed the user of the personal information processing rules and obtained the user's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using this technical solution has obtained the user's separate consent before processing the sensitive personal information, and also meets the requirement of "express consent". For example, at personal information collection devices such as cameras, clear and prominent signs are set up to inform users that they have entered the scope of personal information collection and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed that they have agreed to the collection of their personal information; or on the personal information processing device, with clear signs / information informing users of the personal information processing rules, authorization is obtained from the individual through pop-up information or by asking the individual to upload their personal information; wherein, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

Claims

1. A comprehensive supplier management method, characterized in that, Includes the following steps: The original order data is structured to obtain structured order data, and the flow nodes of the structured order data are determined by the preset order flow rules to obtain the order flow nodes; The structured order data is marked with status based on the order flow nodes to obtain marked status order data; Based on the marked status order data, status information is pushed to the corresponding suppliers to obtain the supplier's received status information, and feedback information is collected from the supplier's received status information to obtain supplier feedback information. The status of the marked order data is updated based on the supplier feedback information to obtain updated order data, and the updated order data is visualized to obtain an order status tracking graph.

2. The supplier integrated management method according to claim 1, characterized in that, The process of structuring the original order data to obtain structured order data includes: The original order data is processed to unify the data format, resulting in unified format order data. Key fields are located in the unified format order data to obtain key field location information. Based on the location information of the key fields, key information is extracted from the unified format order data to obtain preliminary key information. Then, based on the preset field mapping rules, the preliminary key information is standardized and transformed to obtain structured order data.

3. The supplier integrated management method according to claim 1, characterized in that, The step of determining the flow nodes of the structured order data through preset order flow rules to obtain order flow nodes includes: The preset order flow rules are parsed to obtain the node flow order and node triggering conditions, and the order attribute set of the structured order data is extracted. Using a pre-defined Rete rule reasoning model, the order attribute set is matched based on node triggering conditions to obtain a matching result. Based on the matching result and the node flow order, the node affiliation of the structured order data is determined to obtain the order flow node.

4. The supplier integrated management method according to claim 1, characterized in that, Based on the order flow nodes, the structured order data is marked with a status to obtain marked status order data, including: Node attribute analysis is performed on the order flow nodes to obtain node attribute information, and the core information of the structured order data is extracted. Based on the node attribute information, the core information is matched with a state mapping to obtain an order status identifier. Based on the order status identifier, the structured order data is marked with a status, and the order status identifier is added to the corresponding position in the structured order data to obtain marked status order data.

5. The supplier integrated management method according to claim 1, characterized in that, The step of pushing status information to the corresponding supplier based on the marked status order data, and obtaining the supplier's received status information, includes: Information elements are extracted from the marked order data to obtain key elements of the order status, and information on the supplier's communication methods is collected to obtain supplier communication information; Based on the supplier communication information, the key elements of the order status are encapsulated. The key elements of the order status are encapsulated according to a preset communication format to obtain encapsulated status information. The encapsulated status information is then pushed to the supplier through the corresponding supplier's communication method to obtain the supplier's received status information.

6. The supplier integrated management method according to claim 1, characterized in that, The step of collecting feedback on the supplier's received status information to obtain supplier feedback information includes: The response time of the supplier's received status information is recorded to obtain supplier response duration data, and the content integrity of the supplier's received status information is checked to obtain a content integrity identifier. The supplier response time data is filtered based on the content completeness identifier. If the content completeness identifier indicates that the information is complete, the corresponding supplier response time data is retained. If the content is marked as missing information, the corresponding supplier response time data is removed to obtain filtered response data. The filtered response data is then integrated to obtain supplier feedback information.

7. The supplier integrated management method according to claim 1, characterized in that, The status of the marked order data is updated based on supplier feedback information to obtain updated order data, including: The supplier feedback information is parsed to obtain supplier execution progress data, and the order progress requirements are extracted from the marked status order data to obtain order progress requirement data. By comparing and analyzing the supplier's execution progress data and the order progress requirement data, the difference is calculated to obtain progress difference data, and the difference type is determined to obtain a difference type identifier. The status update operation is performed on the marked status order data based on the difference type identifier; If the difference type is marked as "advanced", then the order status in the marked status order data will be updated to "advanced execution status". If the difference type is identified as delayed, the order status in the marked status order data will be updated to delayed execution status; If the difference type is identified as progress consistency, the order status in the marked status order data will be updated to normal execution status, resulting in updated order data.

8. A supplier integrated management system, characterized in that, The supplier integrated management method for performing any one of claims 1 to 7 includes: The judgment module is used to organize the original order data into structured data to obtain structured order data, and to judge the flow nodes of the structured order data according to the preset order flow rules to obtain the order flow nodes; The marking module is used to mark the status of the structured order data based on the order flow nodes to obtain marked status order data; The push module is used to push status information to the corresponding suppliers based on the marked status order data, obtain the supplier's received status information, and collect feedback on the supplier's received status information to obtain supplier feedback information. The update module is used to update the status of the marked order data based on supplier feedback information, obtain updated order data, and visualize the updated order data to obtain an order status tracking graph.

9. A computer device, characterized in that, The method includes a memory and a processor coupled to each other, wherein the memory stores program instructions and the processor executes the program instructions to implement the supplier integration management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The system stores program instructions that can be executed by a processor, the program instructions being used to implement the supplier integration management method according to any one of claims 1 to 7.

Images