Purchase process management system and method based on task package working mode

Abstract

The invention provides a purchase process management system and method based on a task package working mode. The purchase process management system comprises a data management module, a purchase service module and a system interface module. The purchase business module comprises a purchase planning unit used for making a purchase plan; the task package generation unit is used for automatically generating an initial purchase task package in response to confirmation of the purchase plan; the task package disassembling unit is used for the authorized user to disassemble the initial task package into a plurality of sub-task packages and distribute responsible persons; a state machine is embedded in the task circulation and state management unit, and the task circulation and state management unit is used for automatically driving task circulation and triggering interaction with an external system in response to state change of the sub-task package; and the system interface module is used for realizing data and process interaction with an external service system. According to the invention, through dynamic generation, intelligent disassembly and state driving of the task package, the technical problems of process stiffness, low collaboration efficiency and system islanding of a traditional purchasing system are solved, and flexibility, automation and closed-loop management of the purchasing process are realized.

Description

Technical Field

[0001] This invention relates to the field of information management technology, and in particular to a procurement process management system and method based on a task package work mode. Background Technology

[0002] In the manufacturing of complex equipment such as rail transit, procurement is characterized by a wide variety of materials, complex technical conditions, long project cycles, and frequent collaboration among multiple departments and roles. Traditional procurement management systems, typically built on linear approval processes, have the following inherent drawbacks: Rigid processes: Pre-set fixed processes cannot adapt to the dynamic splitting and merging of tasks required during the procurement process due to differences in material technology, changes in suppliers, or adjustments to project plans.

[0003] Inefficient collaboration: Task allocation and workflow rely heavily on manual notifications, emails, or instant messaging, resulting in opaque information, unclear responsibilities, and a high risk of delays and buck-passing.

[0004] System silos: Integration with external systems such as Project Management System (PMS), Business Process Management (BPM), and Supplier Relationship Management (SRM) is mostly point-to-point interface. Data write-back and status synchronization rely on manual triggering, which cannot achieve automatic process-level connection, resulting in poor data consistency and real-time performance. Summary of the Invention

[0005] This invention provides a procurement process management system and method based on a task package working mode, which solves the defects in the procurement of the rail transit industry caused by complex categories and numerous roles, such as rigid processes, low collaboration efficiency, and lack of smooth data communication with external systems, and realizes flexible, automated and closed-loop management of the procurement process.

[0006] This invention provides a procurement process management system, comprising: Data management module, procurement business module, and system interface module; The data management module is used to manage the basic data required for the procurement process; The procurement business module includes: The procurement planning unit is used to formulate a procurement plan based on the aforementioned basic data; The task package generation unit is used to automatically generate an initial procurement task package in response to the confirmation of the procurement plan; The task package disassembly unit is used by authorized users to disassemble the initial task package into multiple sub-task packages and assign responsibilities to relevant personnel. The task flow and state management unit has an embedded state machine, which is used to respond to the state changes of sub-task packages, automatically drive task flow and trigger interactions with external systems. The system interface module is used to enable data and process interaction with external business systems.

[0007] According to the procurement process management system provided by the present invention, the task package generation unit is specifically used for: Verify the completeness of the procurement plan; Based on the category information in the procurement plan, perform automatic splitting and judgment by sub-category or technical conditions; Based on the demand time and reverse scheduling model in the procurement plan, the suggested time nodes for the initial task package are automatically calculated.

[0008] According to the procurement process management system provided by the present invention, the task package decomposition unit is used to decompose the initial task package according to three dimensions: category, execution role, and time node, and provides the authorized user with category splitting suggestions and a list of recommended responsible persons based on historical data and rule engine during the decomposition process.

[0009] According to the procurement process management system provided by the present invention, the state machine in the task flow and status management unit includes at least the following states: pending disassembly, disassembled and pending execution, in execution, completed, and closed; and when the status of the subtask package changes from "disassembled and pending execution" to "in execution", the corresponding external system interface is automatically called.

[0010] According to the procurement process management system provided by the present invention, the system interface module includes: An interface with the project management system for obtaining project plan data; An interface with the business process management system is used to initiate and track the procurement review and approval process; The interface with the supplier relationship management system is used to push sourcing solutions, receive bidding results, send procurement intentions, and receive supplier feedback.

[0011] The procurement process management system provided by the present invention further includes a report management module, which is used to generate work task reports, process monitoring reports or performance reports based on the flow data of the task package.

[0012] The procurement process management system provided by the present invention also includes a back-end management module for managing user accounts, role permissions, and system interface configurations.

[0013] This invention also provides a procurement process management method, comprising: Obtain project data from external systems through system interfaces to generate procurement plans; In response to the confirmation of the procurement plan, the procurement plan is verified and an initial task package is generated; The initial task package is broken down into multiple sub-task packages, and a person in charge is assigned to each sub-task package; Based on a predefined state machine, in response to state changes in subtask packages, the task flow is automatically driven and interactions with external business systems are triggered to complete the procurement method review, supplier selection, and procurement intention interaction stages respectively.

[0014] According to the procurement process management method provided by the present invention, the step of breaking down the initial task package into multiple sub-task packages and assigning a responsible person to each sub-task package specifically includes: Authorized users confirm and adjust the initial task package based on the system-recommended splitting strategy and the list of responsible persons, thus completing the splitting process.

[0015] According to the procurement process management method provided by the present invention, when the procurement intention interaction stage is completed, the step of automatically driving task flow and triggering interaction with external business systems based on a predefined state machine in response to the state change of sub-task packages specifically includes: In response to the status change of the supplier sub-task package to completed and the receipt of the bidding results from the supplier relationship management system, a procurement intention task package is automatically generated. Based on the procurement intention task package, the procurement officer prepares a structured procurement intention agreement that includes at least one of the design cycle, production cycle, and delivery plan, and sends it to the supplier relationship management system. Purchasing agents can view the structured confirmation information provided by suppliers through the supplier relationship management system.

[0016] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the train health assessment method based on multi-source heterogeneous data as described above.

[0017] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the procurement process management method as described above.

[0018] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the procurement process management method as described above.

[0019] This invention provides a procurement process management system and method based on a task package working mode. It includes a data management module, a procurement business module, and a system interface module. The data management module manages the basic data required for the procurement process. The procurement business module includes: a procurement planning unit for developing a procurement plan based on the basic data; a task package generation unit for automatically generating an initial procurement task package in response to confirmation of the procurement plan; a task package decomposition unit for authorized users to decompose the initial task package into multiple sub-task packages and assign responsibilities; and a task flow and status management unit with an embedded state machine for automatically driving task flow and triggering interaction with external systems in response to changes in the status of sub-task packages. The system interface module enables data and process interaction with external business systems. Through dynamic generation, intelligent decomposition, and status-driven management of task packages, this invention solves the technical problems of rigid processes, inefficient collaboration, and system silos in traditional procurement systems, achieving flexible, automated, and closed-loop management of the procurement process. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is one of the structural diagrams of the procurement process management system based on the task package working mode provided by the present invention.

[0022] Figure 2 This is the second structural diagram of the procurement process management system based on the task package working mode provided by the present invention.

[0023] Figure 3 This is a flowchart illustrating the procurement process management method based on the task package working mode provided by the present invention.

[0024] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0026] The present invention will now be described in detail with reference to the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of the present invention, unless otherwise stated, "at least one" includes one or more. "Multiple" refers to two or more. For example, at least one of A, B, and C includes: A existing alone, B existing alone, A and B existing simultaneously, A and C existing simultaneously, B and C existing simultaneously, and A, B, and C existing simultaneously. In the present invention, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone.

[0027] The present invention will now be described in detail with reference to specific embodiments.

[0028] In some specific embodiments of the present invention, such as Figure 1 As shown, this solution provides a procurement process management system based on a task package working mode, including: Data management module 10, procurement business module 20, and system interface module 30; The data management module 10 is used to manage the basic data required for the procurement process; The procurement business module 20 includes: The procurement planning unit 21 is used to formulate a procurement plan based on the aforementioned basic data; Task package generation unit 22 is used to automatically generate an initial procurement task package in response to the confirmation of the procurement plan; The task package disassembly unit 23 is used by authorized users to disassemble the initial task package into multiple sub-task packages and assign responsibilities to relevant personnel. The task flow and state management unit 24 has an embedded state machine, which is used to respond to the state changes of sub-task packages, automatically drive task flow and trigger interaction with external systems; The system interface module 30 is used to realize data and process interaction with external business systems.

[0029] It should be noted that existing procurement process management solutions suffer from fragmented, inconsistent, and difficult-to-maintain basic data, leading to insufficient basis for procurement planning and low efficiency. Furthermore, traditional linear or form-driven processes are rigid and unable to handle complex and dynamic scenarios. Additionally, procurement planning relies on manual information aggregation from multiple channels, which is error-prone and inefficient. The conversion from plan to task relies on manual decomposition, which is time-consuming, lacks standardized criteria, and fails to guarantee the scientific validity of timelines. The internal breakdown and allocation of complex tasks depends entirely on the team leader's personal experience and manual coordination, resulting in a heavy workload, uneven resource allocation, and chaotic collaboration. Task status progression relies on manual notification and memory, and interaction with external systems requires manual triggering, leading to process bottlenecks, data asynchrony, and low automation. "Information silos" are formed between systems, with data transfer relying on manual export and import, resulting in low efficiency, high error rates, and an inability to achieve seamless process integration.

[0030] Therefore, this invention uses the data management module 10 to store and manage basic data in the procurement process, such as project, procurement category, supplier and production schedule data, thereby achieving centralized and standardized management of procurement basic data. This provides a unified and accurate data source for all subsequent links, ensuring process quality from the source.

[0031] In possible embodiments, the technical data includes project management data, such as storing project names, numbers, and responsible persons; category management data, such as hierarchical management of materials, supporting diverse attributes; supplier management data, such as maintenance information and credit ratings; and monthly production scheduling data, providing a basis for procurement.

[0032] A brand-new dynamic task-driven model was built through the procurement business module, replacing the rigid fixed process.

[0033] The procurement business module includes a procurement planning unit. For example, the procurement manager can formulate a procurement plan with fields such as category, quantity, and time based on the project plan obtained from the PMS interface. This realizes the online and structured formulation of procurement plans and links them with the project plan to ensure the accuracy of the demand source.

[0034] The procurement module also includes a task package generation unit. In the generation logic, the category dimension is automatically split according to a "category-subcategory" structure, the time dimension automatically calculates time nodes based on a reverse scheduling model, and the responsibility dimension is automatically assigned to the procurement team leader. This achieves automated and intelligent transformation from procurement planning to task execution. The automatic time calculation by the model ensures the rationality of the schedule and greatly improves the efficiency and scientific nature of initial task allocation.

[0035] The procurement module also includes a task package breakdown unit. The breakdown rules include: category breakdown, where the system recommends splitting based on technical / supplier differences; role breakdown, where the system recommends three types of responsible persons (reviewer, sourcing, and interested party) based on historical load balancing algorithms; and time breakdown, which automatically provides timeframes based on three project duration templates, supporting Gantt chart drag-and-drop adjustments. This upgrades the breakdown process from "purely manual experience" to "system intelligent recommendation + human decision-making optimization." It achieves resource load balancing and rational task decomposition, improving collaborative efficiency and fairness.

[0036] The procurement module also includes a task flow and status management unit, driven by a state machine. The status flow includes: pending breakdown → broken down and awaiting execution → in progress → completed → closed. During inter-system transitions, when the status changes to "in progress," external system interfaces (such as review → BPM, sourcing → SRM) are automatically invoked. This implements a state-driven, fully automated process engine. Tasks "push" people forward, rather than people "chasing" tasks. Through deep integration with external systems, seamless cross-system process connections and automatic data write-back are achieved, forming a true closed-loop management system.

[0037] The system interface modules enable data and process interaction with external business systems. For example, the interface with PMS is used to automatically obtain project plans, the interface with BPM is used to initiate / track review and approval flows, and the interface with SRM is used to push sourcing solutions, receive bidding results, and send / receive procurement intentions. Positioning this system as a procurement business middle platform, it connects seamlessly with upstream and downstream business systems (PMS / BPM / SRM), achieving "data flow and process flow," and laying the foundation for overall enterprise digitalization.

[0038] In some possible embodiments of the present invention, the task package generation unit is specifically used for: Verify the completeness of the procurement plan; Based on the category information in the procurement plan, perform automatic splitting and judgment by sub-category or technical conditions; Based on the demand time and reverse scheduling model in the procurement plan, the suggested time nodes for the initial task package are automatically calculated.

[0039] Specifically, this embodiment provides an implementation method for a task package generation unit. The system automatically verifies the completeness of the plan and automatically splits and calculates time based on the category library configuration and a reverse scheduling model. By embedding expert experience (scheduling model, splitting rules) into the system, the automation and intelligence level of task package generation is improved, ensuring quality from the outset. This solves the problem that the initial task package generation quality relies on manual judgment, lacking scientific rigor and consistency.

[0040] In some possible embodiments of the present invention, the task package disassembly unit is used to disassemble the initial task package according to three dimensions: category, execution role, and time node, and during the disassembly process, it provides the authorized user with category splitting suggestions and a list of recommended responsible persons based on historical data and a rule engine.

[0041] Specifically, this embodiment provides an implementation method for a task package decomposition unit, which provides category decomposition suggestions and a recommended list of responsible persons based on rules and algorithms. This solves the problems of task decomposition being entirely based on guesswork, uneven resource allocation, and difficulty in finding suitable responsible persons.

[0042] In some possible embodiments of the present invention, the state machine in the task flow and state management unit includes at least the following states: to be disassembled, disassembled and to be executed, in execution, completed, and closed; and when the state of the subtask package changes from "disassembled and to be executed" to "in execution", the corresponding external system interface is automatically called.

[0043] Specifically, this embodiment provides an implementation method for the state machine in a task flow and state management unit.

[0044] In some possible embodiments of the present invention, the system interface module includes: An interface with the Project Management System (PMS) is used to obtain project plan data; Interface with the Business Process Management (BPM) system, used to initiate and track the procurement review and approval process; The interface with the Supplier Relationship Management (SRM) system is used to push sourcing solutions, receive bidding results, send procurement intentions, and receive supplier feedback.

[0045] Specifically, this embodiment provides an implementation method for a system interface module.

[0046] By setting state machine paths and triggering interactions with BPM and SRM through state changes, precise conditions and paths for automated triggering are achieved. This makes "state-driven" no longer an abstract concept, but an executable and monitorable technical mechanism, ensuring the reliability of the closed loop.

[0047] In some possible embodiments of the present invention, a report management module is also included, which is used to generate work task reports, process monitoring reports or performance reports based on the flow data of the task package.

[0048] Specifically, this embodiment provides an implementation method for a report management module.

[0049] In some possible embodiments of the present invention, a background management module is also included, which is used to manage the user accounts, role permissions and system interface configuration of the system.

[0050] Specifically, this embodiment provides an implementation method for a background management module.

[0051] The following is in conjunction with the appendix Figure 2 , 3 The specific embodiments of the present invention will be described in detail below.

[0052] See Figure 2 The procurement process management system adopts a modular design, with the procurement business module at its core. After the procurement manager formulates and submits the plan in the procurement planning unit, the task package generation unit automatically verifies the completeness of the plan and generates an initial task package based on the category configuration and the reverse schedule model.

[0053] The task package breakdown unit provides a graphical interface. Based on a rule engine and load balancing algorithm, the system offers intelligent recommendations for category segmentation and responsibility allocation to procurement team leaders. Procurement team leaders can adjust the recommended schemes to complete the breakdown.

[0054] The task flow and status management unit has a built-in state machine, defining a state flow of "to be disassembled" → "disassembled and ready to execute" → "in execution" → "completed" → "closed". When the subtask package status changes to "in execution", the corresponding external system interface is automatically called through the system interface module.

[0055] See Figure 3 This invention provides a procurement process management method based on a task package working mode, comprising: Step 100: Procurement Plan Generation Steps: Obtain project data from external systems through system interfaces and generate a procurement plan; Step 200, Task Package Generation Step: In response to the confirmation of the procurement plan, verify the procurement plan and generate an initial task package; Step 300, Task Package Decomposition Step: Decompose the initial task package into multiple sub-task packages and assign a responsible person to each sub-task package; Step 400, Task Flow and Execution Steps: Based on a predefined state machine, in response to the state changes of sub-task packages, the task flow is automatically driven and interactions with external business systems are triggered to complete the procurement method review, supplier selection and procurement intention interaction stages respectively.

[0056] In some possible embodiments of the present invention, the step of breaking down the initial task package into multiple sub-task packages and assigning responsibility for each sub-task package specifically includes: Authorized users confirm and adjust the initial task package based on the system-recommended splitting strategy and the list of responsible persons, thus completing the splitting process.

[0057] Specifically, this embodiment provides an implementation method for breaking down the initial task package into multiple sub-task packages and assigning responsibility for each sub-task package.

[0058] In some possible embodiments of the present invention, when the procurement intention interaction step is completed, the predefined state machine, in response to the state change of the sub-task package, automatically drives the task flow and triggers interaction with the external business system, specifically including: In response to the status change of the supplier sub-task package to completed and the receipt of the bidding results from the supplier relationship management system, a procurement intention task package is automatically generated. Based on the procurement intention task package, the procurement officer prepares a structured procurement intention agreement that includes at least one of the design cycle, production cycle, and delivery plan, and sends it to the supplier relationship management system. Purchasing agents can view the structured confirmation information provided by suppliers through the supplier relationship management system.

[0059] Specifically, this embodiment provides an implementation method that automatically drives the task flow and triggers interaction with external business systems when the procurement intention interaction step is completed.

[0060] Specifically, see still Figure 2 The procurement process management system includes four modules: data management, procurement operations, report management, and back-end management.

[0061] The data management module includes functions such as project management, category management, supplier management, and monthly production scheduling. Project management stores project-related information, such as project name, number, and responsible person. Category management allows for the categorization and hierarchical management of procured materials, supporting the addition, modification, and deletion of categories, as well as diverse category attribute settings. Supplier management maintains supplier information, including supplier name, contact information, and credit rating. Monthly production scheduling records the monthly production plan, providing a basis for procurement planning.

[0062] The procurement business module includes functions such as work tasks, procurement plans, procurement work packages, procurement method review, self-sourcing solutions, centralized procurement applications, and procurement intention agreements. Work tasks are used to manage procurement tasks and hand over work. Procurement plans are used to develop procurement plans based on project requirements, including categories, quantities, and timelines. Procurement work packages are used to break down a work package into multiple procurement tasks for easier management. Procurement method review is used to evaluate procurement methods and select suitable suppliers. Self-sourcing solutions are used to develop independent procurement sourcing plans, including technical requirements and financial terms. Centralized procurement applications are used to develop centralized procurement applications, including technical requirements and financial terms. Procurement intention agreements are used to communicate procurement intentions with suppliers and confirm delivery plans.

[0063] The report management section includes functions such as notification reports, task reports, process reports, data reports, and performance reports. Notification reports are used to generate reports related to system notifications. Task reports are used to track the completion status of tasks. Process reports are used to record key milestones in the procurement process and monitor procurement progress. Data reports are used to summarize procurement data and support multi-dimensional analysis. Performance reports are used to evaluate the performance of procurement personnel and suppliers.

[0064] The backend management section includes role management, account management, and interface management. Role management is used to define the permissions of different user roles. Account management is used to manage user accounts, supporting registration, login, and permission assignment. Interface management is used to maintain the system's interfaces with other systems (such as PMS, BPM, and SRM).

[0065] For the interaction process of the procurement business module, please refer to [link / reference]. Figure 2 , 3 The first step is to develop a procurement plan, and the specific process includes: The procurement management system automatically retrieves project plans from the PMS system via an interface.

[0066] Purchasing managers create purchasing plans within the purchasing management system. These plans include fields such as purchasing category, quantity, unit, purchasing team leader, initial demand time, completion time for the purchasing review plan, completion time for supplier selection, and completion time for purchasing intention plans. The system then generates task packages and assigns them to purchasing team leaders.

[0067] In this step, the interfaces used are the PMS system and the procurement management system: data transmission is achieved through a RESTful API using JSON format.

[0068] Next is the task package breakdown, the specific process of which includes: The procurement team leader receives the task package; Based on the procurement plan, task packages are broken down and assigned to procurement method review procurement personnel, supplier selection procurement personnel, etc.

[0069] In this step, data interaction includes: Task package information is stored in a database and can be queried and updated through the backend MagicAPI interface.

[0070] The third step is the review of the procurement method, the specific process of which includes: The procurement method review is initiated by the procurement officer based on the task package.

[0071] The review task is undertaken by the purchasing staff responsible for identifying suppliers, who prepares the material procurement method. After preparation, the purchasing staff responsible for procurement method review submits the method to the BPM system for approval.

[0072] Once the approval is complete, the system will automatically generate a task package to identify the supplier.

[0073] In this step, the interfaces used include those of the procurement management system and the BPM system: the workflow engine enables the approval process to flow and supports functions such as task assignment and approval status query.

[0074] The fourth step is to select a supplier, and the specific process includes: The procurement officer is responsible for developing a sourcing plan (including self-procurement and centralized procurement).

[0075] Submit for approval, and the approval process will be transferred to the SRM system.

[0076] The SRM system manages bidding and procurement and generates bidding results.

[0077] The bidding results are automatically sent to the procurement management system.

[0078] In this step, the interfaces used include the procurement management system interface and the SRM system interface: data interaction is achieved through the HTTP interface, supporting functions such as sourcing scheme push and bid opening result feedback.

[0079] The fifth step is the preparation of procurement intentions, the specific process of which includes: After receiving the bidding results, the procurement management system automatically generates a procurement intention task package.

[0080] Purchasing Intent: Purchasing staff prepare purchasing intentions and inquire about suppliers' design cycles, production cycles, and delivery plans.

[0081] The procurement intention was sent to the SRM system, and the supplier responded.

[0082] The purchasing agent reviews the supplier's response.

[0083] In this step, data interaction includes: Purchase intention information is stored in a database and can be queried and updated through a backend interface.

[0084] It is worth noting that the task package is the vehicle for implementing the procurement plan and the core component of this system to realize the "work package working mode". Its formation process can be divided into three stages: "generation - decomposition - circulation". Each stage follows the principles of "plan-driven, model-supported, and access control", with clear hierarchy and logical closed loop.

[0085] In a possible implementation, the task package generation phase, from the procurement plan to the task package, includes the following aspects: Triggering conditions: After the purchasing manager confirms and submits the purchasing plan in the project management module, the system automatically verifies the completeness of the plan (required fields such as category, quantity, and first column requirement time). Once the verification is successful, the task package generation event is triggered.

[0086] Generation logic: Category Dimension: A procurement plan can generate one or more task packages according to a three-level structure of "category-subcategory-technical condition code"; if a category is marked as "needs to be subdivided" in the system, it will be automatically split into subcategory level.

[0087] Time dimension: Based on the first column of required time and the preset reverse schedule model, the system automatically calculates the suggested start and end times of the task package and reserves a buffer period.

[0088] Responsibility Dimension: Based on the procurement team leader field in the procurement plan, the task package is assigned to the team leader by default; if a collaborative procurement team exists, the system splits the task package proportionally.

[0089] Initial attributes of the task package: The system automatically writes: Task Package ID (Universally Unique Identifier, UUID), Source Procurement Plan Number, Category, Quantity, Unit, Budget Amount, First Requirement Time, Procurement Team Leader, and Initial Status "Pending Dismantling".

[0090] During the task package decomposition phase, the process from task package to executable subtasks includes the following aspects: Disassembly permission: Only the purchasing team leader has the authority to dismantle the plan; before dismantling, the system will re-verify whether the plan has been locked to prevent version drift.

[0091] Disassembly rules (system recommendation + manual confirmation): Category Breakdown: If there are technical or supplier differences in the categories being purchased, the system recommends breaking them down into multiple sub-task packages; the team leader can adjust or merge these packages.

[0092] Role breakdown: Each subtask package must designate three types of responsible persons—procurement method review procurement officer, supplier determination procurement officer, and procurement intention procurement officer; the system provides a suggested list based on historical load balancing algorithms, which the team leader can adopt with one click or adjust manually.

[0093] Time breakdown: The system automatically generates time nodes for sub-task packages based on a three-stage timeline template of "review → sourcing → intent"; team leaders can drag and drop to adjust the Gantt chart.

[0094] Disassembly results: After disassembly, a "subtask package list" is generated. Each subtask package inherits the parent task package ID as a prefix, forming a traceable tree structure. The status is updated from "to be disassembled" to "disassembled and ready to be executed".

[0095] During the task package flow phase, the task package is driven and written back, including the following aspects: State machine driven: The task package has a built-in state machine: Pending disassembly → Disassembled and awaiting execution → Executing → Completed → Closed. Any state change must be logged.

[0096] Inter-system flow: When the subtask package status changes to "in execution", the system automatically calls the corresponding external system interface based on the task type: Procurement method review task package → BPM system approval workflow; Identify supplier task packages → SRM system bidding process; Procurement intention task package → SRM system supplier interaction flow.

[0097] After the external system returns the results, the system automatically writes back key fields such as the winning supplier, the winning bid amount, and the design / production / delivery cycle, and updates the task package status to "completed".

[0098] Abnormal rollback: If the external system returns "rejection" or "failure to bid", the task package status will revert to "disassembled and awaiting execution" and a reminder will be sent to the procurement team leader for them to decide whether to disassemble the task package again or terminate it.

[0099] Through the above "three-stage, seven-step" closed-loop mechanism, the task package achieves a seamless connection between "planning, task, execution, and feedback," which not only ensures the standardization of the procurement process but also gives the procurement team room for flexible adjustments, thereby significantly reducing the number of days to increase production and improving collaborative efficiency.

[0100] In more detail, the task package decomposition logic refers to the procurement team leader further refining and adjusting the task package based on the actual situation.

[0101] The reasons and logic for the disassembly are as follows: First, let's clarify why it can be disassembled: Category complexity: The categories of goods to be purchased may be very complex and require further subdivision. For example, a category may contain multiple subcategories, which need to be handled separately.

[0102] Task complexity: Some tasks may be too large and need to be broken down into smaller subtasks for easier management and execution.

[0103] Resource allocation: In order to allocate resources more rationally, the procurement team leader may need to break down the task package and assign it to different procurement personnel.

[0104] Further clarify the specific details of the dismantling: The procurement team leader can break down the task package based on the following: Category Breakdown: For categories in the procurement plan, choose whether to add a new procurement category or break down a category into multiple subcategories.

[0105] Task allocation: Based on the broken-down product categories, formulate specific tasks such as reviewing procurement methods, identifying procurement personnel, determining supplier procurement personnel, and identifying procurement intention procurement personnel.

[0106] Further explanation of the procurement method review: Based on the received task package, the procurement officer initiates a procurement method review task. Supplier selection: Based on the received task, the procurement officer determines the procurement method for this category of goods, including the following: importance of quality characteristics, evaluation method used, recommended supplier list, whether subcontracting is required and the subcontracting ratio, procurement model, procurement method, technical condition code, and remarks.

[0107] Further explanation: After the procurement method review documents for all procurement categories are completed, the procurement method review procurement officer initiates the procurement method review approval flow. This approval flow is then transferred to the BPM system (Business Process Management Platform) for company-level approval.

[0108] After further explanation and approval, the system automatically generates a supplier selection task package, which is then forwarded to the supplier selection procurement officer. The supplier selection procurement officer prepares a sourcing plan, including contract tax rates, technical lead, financial manager, planned bidding end date, and planned delivery date. Once prepared, it is submitted for approval.

[0109] In a possible implementation, the supplier determination task package automatically generated by the system mainly includes the following: Task Package ID: A unique identifier for the task package; Category: The category of materials to be procured; Quantity: The quantity purchased; Unit: The unit of measurement for the quantity purchased; Task type: The type of task package, such as "identify supplier"; Responsible person: The procurement officer assigned to the designated supplier for this task package; Time node: a specific point in time; Start Time: The start time of the task package; End Time: The end time of the task package; The results of the procurement method review include: Importance of quality characteristics: The importance of quality characteristics determined during the review; Evaluation method: The evaluation method determined during the review process; Recommended Supplier List: List of suppliers recommended during the review process; Subcontracting and subcontracting ratio: Subcontracting information determined during the review; Procurement model: The procurement model determined during the review process; Procurement method: The procurement method determined during the review process; Technical condition code: The technical condition code determined during the review.

[0110] In a possible embodiment, the supplier determination task package automatically generated by the system also includes the following relevant information: Contract tax rate: The contract tax rate that needs to be considered when preparing a sourcing solution; Technical lead: The person responsible for the technical aspects; Finance Manager: The person responsible for the finance department; Planned tender end date: The expected end date for the tender process; Planned delivery date: The expected delivery date; In a possible embodiment, the process of determining the formation of the supplier task package includes the following: The first step is triggering the approval process: Once the procurement method review task is completed and approved at the company level, the system will automatically trigger the task package generation process. Approval completion is a crucial prerequisite for generating the supplier selection task package; it marks the end of the procurement method review phase and the beginning of the supplier selection phase.

[0111] Secondly, the basis for task package generation: The system automatically generates a supplier task package based on the following information: Procurement plan information includes the category, quantity, unit, and initial demand time of the procured items. This information is inherited from the procurement plan formulated by the procurement manager and provides the basic procurement requirements for determining the supplier task package.

[0112] The procurement method review results include information such as the importance of quality characteristics, evaluation methods, recommended supplier list, whether subcontracting is involved and the subcontracting ratio, procurement model, procurement method, and technical condition codes. These review results provide specific guidance and constraints for supplier selection, helping procurement staff to have a clear direction and basis when developing sourcing plans.

[0113] Timeframes: Based on the timeframes in the procurement plan, such as the supplier's planned time, the system will set reasonable start and end times for the task package to ensure that the procurement task can be completed on time.

[0114] The third step is to determine the supplier's task package: Once the supplier task package is generated, it will contain the following: Task Package ID: A unique number automatically generated by the system to identify the task package.

[0115] Category: The category of materials to be purchased, specifying the specific recipients.

[0116] Quantity: The quantity to be purchased, ensuring that the purchasing staff is clear about the scale of the purchase.

[0117] Unit: The unit of measurement for the quantity purchased, to avoid ambiguity.

[0118] Task type: Clearly define the task type as "identify suppliers" to let the purchasing staff know the current task focus.

[0119] Responsible Person: Assigned to the designated supplier's purchasing staff, clearly defining who is responsible for executing the tasks in this task package.

[0120] Timeframes: These include the start and end times of the task package, reminding the purchasing staff of the urgency and time constraints of the task.

[0121] Procurement method review results: Key information identified during the review phase will be included in the task package. Procurement staff can directly refer to this information when preparing sourcing plans without having to search for it repeatedly.

[0122] Other relevant information, such as contract tax rates, technical lead, and financial manager, provides a more comprehensive background and requirements for developing a sourcing plan.

[0123] Fourthly, determine the flow of the supplier's task package: The generated supplier selection task package will automatically be transferred to the supplier selection buyer's to-do list. After logging into the system, the buyer can see the task package assigned to them and begin developing a sourcing plan. The information in the task package provides the buyer with clear task guidance, enabling them to efficiently complete the sourcing plan development work, including determining the contract tax rate, technical lead, financial manager, planned bidding end date, and planned delivery date.

[0124] Fifth, develop a source tracing plan and submit it for approval: Based on the information and requirements in the task package, the supplier procurement officer prepares a detailed sourcing plan. Once completed, the procurement officer submits it for approval through the system, and the task package then enters the next approval process, awaiting further review and decision-making.

[0125] The approval process is transferred to the SRM (Supplier Relationship Management) system for bidding and procurement management, including functions such as bid document preparation, bid announcement preparation, and bid opening. The final bidding results are automatically sent to the procurement management system.

[0126] After receiving the bidding results, the procurement management system automatically generates a procurement intention task package and forwards it to the procurement intention clerk. The procurement intention clerk is responsible for preparing the procurement intention, which involves inquiring about the supplier's design cycle, production cycle, and delivery plan. Once prepared, the procurement intention is automatically sent to the SRM system, and the supplier responds promptly based on the received procurement intention. The procurement intention clerk can view the supplier's response in the procurement management system.

[0127] In a possible embodiment, determining the role of the supplier task package specifically includes: First, it serves to guide tasks and clarify responsibilities: The supplier task package uses "category, quantity, timeframe, and responsible person" as core fields to provide a clear and actionable "task description" for "identifying supplier purchasers." Purchasers can see the pending tasks simply by logging into the system, eliminating the need for repeated confirmation of requirements and thus avoiding information omissions and shirking of responsibility.

[0128] Secondly, it serves as a basis for information integration and decision-making. The task package automatically inherits the basic requirements (category, quantity, unit, first-listed requirement time) and procurement method review results (quality characteristic importance, evaluation method, recommended supplier list, subcontracting ratio, procurement model, technical condition code, etc.) from the procurement plan, integrating key information scattered across multiple stages at once, reducing manual queries and secondary data entry, and improving the accuracy and efficiency of subsequent sourcing plan preparation.

[0129] Thirdly, it plays a role in process integration and system collaboration: The task package acts as a "connector" for data and processes between the procurement management system and external systems (SRM): Triggering condition: After the procurement method review and approval, the system automatically generates a task package and pushes it to the procurement officer's to-do list; Flow mechanism: After the task package is executed, the sourcing plan and subsequent bidding results are written back to the procurement management system through a standard interface to realize closed-loop management of "plan - task - execution - feedback" and ensure process continuity and data consistency.

[0130] Fourthly, it serves the functions of time management and risk warning: The task package includes a start time, end time, and key milestones, allowing procurement staff to work backwards from the deadline. The system monitors progress in real time, and if any anomalies such as "rejection" or "failure to bid" occur, the task package status is automatically rolled back and the procurement team leader is notified, facilitating timely adjustments to strategies and reducing the risk of delayed production.

[0131] Fifthly, the role of performance evaluation and data accumulation: All task package operation logs, approval records, bidding results, and write-back data are archived by the system, forming traceable procurement data assets, providing quantitative basis for subsequent performance evaluation (procurement staff efficiency, supplier response speed, project cycle compression rate, etc.) and continuous optimization.

[0132] In a possible embodiment, the procurement intention task package is a detailed set of tasks containing all the information needed for the procurement intention buyer to complete the tasks. The specific contents of the procurement intention task package include: Task Package ID: A unique identifier automatically generated by the system to distinguish different task packages.

[0133] Category: This refers to the category of materials to be procured, specifying the specific recipients.

[0134] Quantity: This refers to the quantity to be purchased, ensuring that the purchasing staff is clear about the scale of the purchase.

[0135] Unit: This refers to the unit of measurement for the quantity purchased, to avoid ambiguity.

[0136] Task type: Clearly define it as the "Procurement Intent Compilation" task type to let the procurement staff know the current task priorities.

[0137] Responsible Person: Assigned to the prospective purchasing staff, clearly defining who is responsible for executing the tasks in this task package.

[0138] Time points, including: Start Time: The start time of the task package.

[0139] End Time: This is the end time of the task package, reminding the purchasing staff of the urgency and time constraints of the task.

[0140] The bidding results include: Successful bidder: The successful bidder determined in the bidding results.

[0141] Winning bid amount: This refers to the amount won in the bid.

[0142] Contract terms: These are the main terms of the contract.

[0143] The procurement intention includes: Design cycle: Inquire about the supplier's design cycle.

[0144] Production cycle: Inquire about the supplier's production cycle.

[0145] Delivery schedule: Inquire about the supplier's delivery schedule.

[0146] Other requirements: Other requirements that need to be confirmed by the supplier.

[0147] Other relevant information: Contract tax rate: The tax rate applied to a contract.

[0148] Technical condition coding: The coding of technical conditions.

[0149] Note: Other information that needs to be recorded.

[0150] In a possible embodiment, the process of forming the procurement intention task package includes: Process 1: Receiving the Bidding Results Once the bidding process is complete, the SRM (Supplier Relationship Management) system will send the bidding results to the procurement management system.

[0151] The bidding results typically include key information such as the winning supplier, the winning bid amount, and the contract terms.

[0152] Step 2: Task Package Generation After receiving the bidding results, the procurement management system will automatically generate a "procurement intention task package" based on the bidding results and the procurement plan.

[0153] The task package is generated automatically by the system. Its purpose is to provide purchasing agents with a clear task guide to ensure that the preparation of purchasing intentions and communication with suppliers can be carried out efficiently.

[0154] Step 3: Task Package Allocation The generated procurement intention task package will be automatically transferred to the to-do task list of the procurement intention procurement officer.

[0155] After logging into the system, prospective buyers can see the task packages assigned to them and begin executing the tasks.

[0156] In a possible implementation, the procurement intention task package may serve the following specific functions: First, the task instructions: The procurement intention task package provides clear task guidelines for procurement officers, ensuring that the preparation of procurement intentions and communication with suppliers can be carried out efficiently.

[0157] Secondly, information integration: The task package integrates key information from the bidding results and procurement plan, enabling procurement staff to quickly understand the task background and requirements.

[0158] Thirdly, process standardization: The generation and circulation of task packages ensured the standardization and continuity of the procurement process, avoiding information omissions and task delays.

[0159] Fourth is supplier communication: The content of the procurement intent task package provides a clear framework for communication with suppliers, ensuring that suppliers clearly understand the procurement needs and respond promptly.

[0160] Fifth is data management: Purchasing staff query purchasing data in the purchasing management system, some of which comes from the SAP (Systems, Applications and Products in Data Processing, Enterprise Resource Planning software products) system.

[0161] The procurement process management system and method based on the task package work mode provided by this invention standardizes the procurement model, efficiently links internal collaborative work within the procurement department, greatly reduces procurement costs, and improves procurement efficiency; it realizes paperless and lightweight mobile office, improves work efficiency, can efficiently handle pending tasks, and improves management efficiency; through the procurement intention module, it builds a communication bridge with suppliers, facilitates information exchange, improves communication efficiency, and reduces production risks.

[0162] During the operation of the procurement process management system and the interaction process of procurement business modules, the system security mechanism specifically includes the following aspects: User authentication: It adopts an authentication method based on username and password, and supports multi-factor authentication (such as SMS verification code).

[0163] Authorization Management: Assign different permissions based on user roles to ensure that users can only access authorized functions and data.

[0164] Data encryption: Sensitive data (such as supplier information and procurement plans) is encrypted during storage and transmission using the AES (Advanced Encryption Standard) encryption algorithm.

[0165] Security audit: Records system operation logs, supports auditing functions, and facilitates the tracking of abnormal operations.

[0166] Specifically, data backup and recovery includes: Backup strategy: The database is automatically backed up daily, and the backup data is stored on local and remote servers.

[0167] Recovery mechanism: Supports one-click recovery function, which can quickly recover data in the event of system failure.

[0168] Performance optimizations specifically include: Concurrent processing: Employs multi-threading and asynchronous processing mechanisms to improve the system's concurrent processing capabilities.

[0169] Data caching: Use caching technology for frequently queried data (such as procurement plans and supplier information) to reduce the number of database accesses.

[0170] Intelligent Algorithms: Introducing intelligent algorithms to optimize procurement task allocation and improve work efficiency.

[0171] Based on the above embodiments, a system login interface can be designed, specifically including: First is the user login interface: Features: Supports login with username and password, and provides functions for forgetting password and registering.

[0172] Design: Simple and clear, supports responsive design, and adapts to different devices.

[0173] Secondly, there's the procurement plan interface: Function: Displays a list of procurement plans, supporting addition, editing, and deletion operations.

[0174] Design: The procurement plan is displayed in a table format, supporting multi-condition filtering and sorting.

[0175] The third is the task package unpacking interface: Functions: Displays task package information, supports task allocation and breakdown operations, and supports import and export.

[0176] Design: The task package breakdown process is presented in flowchart form, supporting drag-and-drop operations.

[0177] Fourth is the procurement method review interface: Function: Supports the initiation, preparation, and approval of procurement method review tasks.

[0178] Design: The review information is filled out in a form, and attachments can be uploaded.

[0179] The fifth is the interface for compiling procurement intentions: Function: Supports the preparation and sending of procurement intentions.

[0180] Design: Purchase intention information is filled in a form and supports real-time preview.

[0181] Based on the above embodiments, system performance needs to be optimized. The specific optimization process includes: Configure system performance metrics: Response time: The system operation response time shall not exceed 3 seconds.

[0182] Concurrent processing capability: Supports processing 100 procurement tasks simultaneously.

[0183] Data query speed: Common data queries take no more than 1 second.

[0184] The optimization measures adopted include: Front-end optimization: Lazy loading technology is used to reduce page load time.

[0185] Backend optimization: Optimize database query statements to reduce database response time.

[0186] System monitoring: Monitor system performance in real time and promptly identify and resolve problems.

[0187] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communication bus 440, wherein the processor 410, communications interface 420, and memory 430 communicate with each other through the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute a procurement process management method based on a task package working mode. This method includes: obtaining project data from an external system through a system interface and generating a procurement plan; in response to the confirmation of the procurement plan, verifying the procurement plan and generating an initial task package; breaking down the initial task package into multiple sub-task packages and assigning responsibility to each sub-task package; based on a predefined state machine, responding to the state changes of the sub-task packages, automatically driving the task flow and triggering interaction with external business systems to complete the procurement method review, supplier determination, and procurement intention interaction stages respectively.

[0188] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a 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.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. 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.

[0189] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the procurement process management method based on the task package working mode provided by the above methods. The method includes: obtaining project data from an external system through a system interface and generating a procurement plan; verifying the procurement plan and generating an initial task package in response to the confirmation of the procurement plan; breaking down the initial task package into multiple sub-task packages and assigning a responsible person to each sub-task package; and automatically driving the task flow and triggering interaction with external business systems in response to the state change of the sub-task packages based on a predefined state machine, so as to complete the procurement method review, supplier determination and procurement intention interaction links respectively.

[0190] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements a procurement process management method based on a task package working mode provided by the above methods. The method includes: obtaining project data from an external system through a system interface and generating a procurement plan; in response to confirmation of the procurement plan, verifying the procurement plan and generating an initial task package; decomposing the initial task package into multiple sub-task packages and assigning a responsible person to each sub-task package; and, based on a predefined state machine, automatically driving task flow and triggering interaction with external business systems in response to state changes of the sub-task packages to complete the procurement method review, supplier determination, and procurement intention interaction stages, respectively.

[0191] The device embodiments described above are merely illustrative. 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; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0192] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0193] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A procurement process management system, characterized in that, include: Data management module, procurement business module, and system interface module; The data management module is used to manage the basic data required for the procurement process; The procurement business module includes: The procurement planning unit is used to formulate a procurement plan based on the aforementioned basic data; The task package generation unit is used to automatically generate an initial procurement task package in response to the confirmation of the procurement plan; The task package disassembly unit is used by authorized users to disassemble the initial task package into multiple sub-task packages and assign responsibilities to relevant personnel. The task flow and state management unit has an embedded state machine, which is used to respond to the state changes of sub-task packages, automatically drive task flow and trigger interactions with external systems. The system interface module is used to enable data and process interaction with external business systems.

2. The procurement process management system according to claim 1, characterized in that, The task package generation unit is specifically used for: Verify the completeness of the procurement plan; Based on the category information in the procurement plan, perform automatic splitting and judgment by sub-category or technical conditions; Based on the demand time and reverse scheduling model in the procurement plan, the suggested time nodes for the initial task package are automatically calculated.

3. The procurement process management system according to claim 1, characterized in that, The task package decomposition unit is used to decompose the initial task package according to three dimensions: category, execution role, and time node. During the decomposition process, it provides the authorized user with category splitting suggestions and a list of recommended responsible persons based on historical data and a rule engine.

4. The procurement process management system according to claim 1, characterized in that, The state machine in the task flow and status management unit includes at least the following states: pending disassembly, disassembled and pending execution, in execution, completed, and closed; and when the status of the subtask package changes from "disassembled and pending execution" to "in execution", the corresponding external system interface is automatically called.

5. The procurement process management system according to claim 4, characterized in that, The system interface module includes: An interface with the project management system for obtaining project plan data; An interface with the business process management system is used to initiate and track the procurement review and approval process; The interface with the supplier relationship management system is used to push sourcing solutions, receive bidding results, send procurement intentions, and receive supplier feedback.

6. The procurement process management system according to any one of claims 1-5, characterized in that, It also includes a report management module, which is used to generate work task reports, process monitoring reports or performance reports based on the flow data of the task package.

7. The procurement process management system according to any one of claims 1-5, characterized in that, It also includes a backend management module, which is used to manage the system's user accounts, role permissions, and system interface configurations.

8. A procurement process management method, characterized in that, include: Obtain project data from external systems through system interfaces to generate procurement plans; In response to the confirmation of the procurement plan, the procurement plan is verified and an initial task package is generated; The initial task package is broken down into multiple sub-task packages, and a person in charge is assigned to each sub-task package; Based on a predefined state machine, in response to state changes in subtask packages, the task flow is automatically driven and interactions with external business systems are triggered to complete the procurement method review, supplier selection, and procurement intention interaction stages respectively.

9. The procurement process management method according to claim 8, characterized in that, The step of breaking down the initial task package into multiple sub-task packages and assigning responsibility for each sub-task package specifically includes: Authorized users confirm and adjust the initial task package based on the system-recommended splitting strategy and the list of responsible persons, thus completing the splitting process.

10. The procurement process management method according to claim 8, characterized in that, When completing the aforementioned procurement intention interaction stage, the predefined state machine, responding to state changes in sub-task packages, automatically drives task flow and triggers interaction with external business systems, specifically including: In response to the status change of the supplier sub-task package to completed and the receipt of the bidding results from the supplier relationship management system, a procurement intention task package is automatically generated. Based on the procurement intention task package, the procurement officer prepares a structured procurement intention agreement that includes at least one of the design cycle, production cycle, and delivery plan, and sends it to the supplier relationship management system. Purchasing agents can view the structured confirmation information provided by suppliers through the supplier relationship management system.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the procurement process management method as described in any one of claims 8 to 10.

Images