Machine accessory management method and platform, electronic equipment and storage medium

Abstract

The invention provides a machine accessory management method and platform, an electronic device and a storage medium, and the method comprises the steps: collecting machine accessory information through an agent program in a machine, correspondingly storing the machine accessory information and machine information according to a preset field, storing unused accessory information according to a preset field, and obtaining an accessory information table; and under the condition that an accessory racking request is received, executing an accessory updating operation, and updating the corresponding accessory information and the accessory stock quantity in the accessory information table. Through the process, the full-amount machine accessory information is recorded in the network platform, and the accessory information table is updated in real time under the condition that the accessories of the machine are updated, so that the full-automatic management of the machine accessories is realized, and the management efficiency and accuracy of the machine accessories are improved. And meanwhile, the machine accessory information is stored through the preset field, so that field missing of the machine accessory information is easier to find, machine agent program abnormity can be found in time, corresponding measures can be taken, and the machine operation stability is ensured.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a machine parts management method, platform, electronic device, and storage medium. Background Technology

[0002] A distributed cluster typically contains nearly ten thousand machines (servers, computers, network devices, etc.), and each machine contains multiple components, resulting in nearly a million data entries related to machine component information protection. During routine machine maintenance, information such as component serial numbers (SNs), operational status, and fault logs are usually collected through agents on the machines.

[0003] However, the onboarding and offboarding of parts rely on manual maintenance, which results in insufficient awareness of parts procurement volume, usage volume, and inventory. Furthermore, manual maintenance of information can lead to errors and untimely updates. In addition, there is a large demand for asset reconfiguration and frequent changes in parts, making manual management difficult and inefficient. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a machine parts management method, platform, electronic device, and storage medium to improve the efficiency of machine parts management and thereby ensure the normal operation of the machine.

[0005] According to one aspect of the present invention, a machine parts management method is provided, applied to a machine parts management platform, the method comprising: The component information of each machine is collected by the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. The machine information and accessory information are stored according to preset fields, and the unused accessory information is stored according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the unused accessory's SN, model, manufacturer, specifications and status; Receive a component placement request, wherein the component placement request includes information on a first target component and information on a target rack; According to the accessory listing request, perform the accessory update operation, update the status of the first target accessory in the accessory information table, fill in the machine SN information and rack position information of the first target accessory information, and update the accessory inventory quantity.

[0006] In one possible embodiment, the method further includes: Receive an accessory removal request, wherein the accessory removal request includes information on a second target accessory; According to the accessory removal request, perform the accessory update operation, update the installation status of the second target accessory in the accessory information table, delete the server SN information and current rack position information contained in the second target accessory information, and update the accessory inventory quantity.

[0007] In one possible embodiment, the method further includes: Receive fault information, wherein the fault information is triggered during the maintenance process, and the fault information includes faulty parts information and newly replaced parts information; Based on the fault information, add server SN information to the new replacement part information in the parts information table and update the status of the new replacement part; delete the server SN information to the faulty part information and update the status of the faulty part.

[0008] In one possible embodiment, the method further includes: Receive requests for new accessories; The newly added accessory information is stored in the accessory information table according to the preset fields, and the accessory inventory quantity is updated; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

[0009] According to another aspect of the present invention, a machine parts management platform is provided, the platform comprising: The data acquisition module is used to collect component information of each machine using the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. The storage module is used to store the machine information and accessory information according to preset fields, and to store the unused accessory information according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the unused accessory's SN, model, manufacturer, specifications and status; A receiving module is used to receive a component listing request, wherein the component listing request includes first target component information and target rack information; The execution module is used to perform an update part operation according to the part listing request, update the status of the first target part in the part information table, fill in the machine SN information and rack position information of the first target part in the part information, and update the part inventory quantity.

[0010] In one possible embodiment, it is also used to receive an accessory removal request, wherein the accessory removal request includes information on a second target accessory; The execution module is further configured to perform an update part operation according to the part removal request, update the installation status of the second target part in the part information table, delete the server SN information and current rack position information contained in the second target part information, and update the part inventory quantity.

[0011] In one possible embodiment, the receiving module is further configured to receive fault information, wherein the fault information is triggered during the maintenance process, and the fault information includes faulty parts information and newly replaced parts information; The execution module is further configured to, based on the fault information, add server SN information to the new replacement part information in the parts information table and update the status of the new replacement part, and delete the server SN information to the faulty parts information and update the status of the faulty parts.

[0012] In one possible embodiment, the receiving module is further configured to receive a request for additional accessories; The execution module is further configured to store the newly added accessory information into the accessory information table according to the preset fields and update the accessory inventory quantity; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

[0013] According to another aspect of the present invention, an electronic device is provided, comprising: Processor; and Stored program memory, The program includes instructions that, when executed by the processor, cause the processor to perform any of the machine parts management methods described above.

[0014] According to another aspect of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause a computer to perform any of the machine parts management methods described above.

[0015] The present invention provides one or more technical solutions that collect machine part information through an agent program within the machine, and store the collected part information and machine information according to preset fields. For unused parts, their part information is also stored according to preset fields, thus obtaining a part information table. Upon receiving a part listing request, an update operation is performed, updating the corresponding part information and inventory quantity in the part information table. Through this process, all machine part information is recorded in the network platform, and the part information table is updated in real time when machine parts are updated, achieving fully automated management of machine parts and improving the efficiency and accuracy of part management. Furthermore, storing part information through preset fields makes it easier to detect missing part information fields, thereby enabling timely detection of machine agent program anomalies and taking corresponding measures to ensure machine operational stability. Attached Figure Description

[0016] Further details, features, and advantages of the invention are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which: Figure 1 A flowchart illustrating a machine parts management method provided in an embodiment of the present invention; Figure 2 This is a schematic diagram of a machine parts information table in the machine parts management method provided in an embodiment of the present invention; Figure 3 This is a schematic flowchart of the additional equipment process in the machine parts management method provided in an embodiment of the present invention; Figure 4 This is a schematic flowchart of the reduction process in the machine parts management method provided in an embodiment of the present invention; Figure 5 This is a schematic flowchart of the reconfiguration process in the machine parts management method provided in an embodiment of the present invention; Figure 6 This is a schematic flowchart of the maintenance process in the machine parts management method provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the warehousing process in the machine parts management method provided in an embodiment of the present invention; Figure 8 A schematic diagram of a machine parts management platform provided in an embodiment of the present invention; Figure 9 A structural block diagram of an exemplary electronic device that can be used to implement embodiments of the present invention is shown. Detailed Implementation

[0017] Embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. While some embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the invention. It should be understood that the accompanying drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the invention.

[0018] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0019] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this invention are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0020] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0021] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0022] To improve the efficiency of machine parts management, this invention provides a machine parts management method, platform, electronic device, and storage medium. The machine parts management method provided in this embodiment can be applied to any electronic device with machine parts management functionality, such as a server, computer, or mobile terminal. In one possible embodiment, the machine parts management method provided by this invention can be applied to a constructed machine parts management platform. This platform may include a front-end page and a back-end server. The front-end page is used to execute specific interactive operations, and the back-end server is used to execute the instructions corresponding to the interactive operations. The following description of the invention is based on the accompanying drawings: Figure 1A flowchart illustrating a machine parts management method provided in an embodiment of the present invention may include the following steps: S101. Collect component information of each machine using the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. S102. Store the machine information and accessory information according to the preset fields, and store the unused accessory information according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the SN, model, manufacturer, specifications and status of the unused accessory; S103. Receive a component racking request, wherein the component racking request includes information on a first target component and information on a target rack. S104. Perform the part update operation according to the part put-away request, update the status of the first target part in the part information table, fill in the machine SN information and rack position information in the first target part information, and update the part inventory quantity.

[0023] By applying this embodiment of the invention, an agent program within the machine collects machine part information and stores the collected part information in accordance with preset fields, corresponding to the machine information. Simultaneously, for unused parts, their part information is stored according to preset fields, thus obtaining a part information table. Upon receiving a part listing request, an update operation is performed, updating the corresponding part information and inventory quantity in the part information table. Through this process, all machine part information is recorded in the network platform, and the part information table is updated in real time when machine parts are updated, achieving fully automated management of machine parts and improving the efficiency and accuracy of part management. Furthermore, storing machine part information in preset fields makes it easier to detect missing part information fields, thereby enabling timely detection of machine agent program anomalies and taking corresponding measures, ensuring the stability of machine operation.

[0024] The following provides an exemplary description of S101-S104: In this invention, when deploying machines (servers, computers, network devices, etc.), an agent can be deployed on the machine. This agent is used to collect component information within the machine. In one possible embodiment, when the agent starts, it can register with a backend server to identify the machine corresponding to the data collected by the agent. For example, the agent can carry information such as IP address, hostname, and hardware fingerprint to the backend server, which can then store this agent information.

[0025] The backend server can periodically obtain machine component information collected by the agent programs deployed on each machine. For example, the backend server can execute batch commands through SaltStack or Ansible to traverse the agent programs on each machine and obtain the machine component information collected by the agent programs. Components in the machine can include CPU, memory, hard drive, solid-state drive, network card, RAID card, GPU, etc. The corresponding component information can include component identifier, specific model, data center, manufacturer, maintenance provider, purchase time, arrival time, billing time, warranty expiration time, component source, status, etc. The component identifier is used to uniquely identify the component and can be set according to the actual application scenario. For example, in a component purchase and arrival scenario, the scenario information, component model, arrival time, and component arrival order can be included, such as: CG25GCX524102500024 [Purchase + 25G CX5 network card + October 25, 2024 + 24th device]. In the scenario of removing accessories, the accessory identifier can be YZ25GCX524102500029 [Original + 25G CX5 network card + October 25, 2024 + 29th device]. The status of machine accessories can include used, unused, and faulty.

[0026] After obtaining the aforementioned machine parts information, it can be stored according to preset fields. These preset fields can be set according to the actual application scenario, such as including the part identifier, specific model, server room, machine identifier, manufacturer, maintenance provider, purchase time, delivery time, billing time, warranty expiration time, part source, and status, to store corresponding information and thus achieve the correspondence between machine information and machine parts information. Similarly, unused parts can also be stored according to the aforementioned preset fields, but the server room and machine identifier are allowed to be empty. After storing the aforementioned machine parts information, a parts information table is obtained. Here, the parts information table has a common name, and there is no specific limitation on the storage format of the machine parts information. The parts information table can be stored in the form of a table, key-value pairs, or file.

[0027] Figure 2This is a schematic diagram of a parts information table provided in an embodiment of the present invention. The parts information table supports a query function; for example, users can input information such as parts type, parts model, or data center in the table to query the corresponding parts information. The parts information table also supports batch queries (asset number / part SN / server SN query), delivery time, billing time filtering, and filtering by parts type, data center, parts model, parts source, parts operation, usage status, and parts status. It also provides interfaces for querying by parts type and model. The parts information includes parts type, specifications, data center, available inventory quantity, reconfiguration quantity, reserved quantity, and fault quantity. Specifically, the total parts inventory = available inventory quantity + reconfiguration quantity + reserved quantity + fault quantity; available inventory quantity – parts in stock and in normal condition; reconfiguration quantity – parts in reconfiguration and in normal condition; reserved quantity – parts in reserved and in normal condition; and fault quantity – parts in stock and in fault condition.

[0028] Based on the aforementioned parts information table, a parts listing request can be sent via the front-end page to add new parts to the machine. As one possible implementation, the front-end page can display checkboxes for parts identifier, model, specifications, source, modification status, usage status, delivery time, and billing time. Users can select the desired information from the corresponding checkboxes to send a request, which can be submitted via a work order.

[0029] In one possible embodiment, such as Figure 3 As shown, when a user sends a part listing request, the backend server, upon receiving the request, can send a corresponding part release instruction, initiating a reconfiguration process to allow relevant personnel to obtain the part. The part listing information is then sent to a pre-defined client via email, instant messaging, or other means, enabling relevant personnel to perform specific change operations based on the messages received on the client. After the change operations are completed, a completion message is returned. Upon receiving this completion message, the backend server can modify the part information stored in the part information table. For example, it can change the part's usage status, server information (SN), rack and package information, and adjust the part's inventory quantity (i.e., inventory -1).

[0030] In one possible implementation, a user can select "remove configuration" in the configuration status bar on the front-end page to send a component removal request. This component removal request specifically refers to a request to remove the component from the machine. For example, the user can fill in the identifier, model, and corresponding rack and data center information of the second target component to be removed, and then select the "remove configuration" option to send the component removal request.

[0031] After receiving the accessory removal request, the backend server can perform an accessory update operation according to the accessory removal request, update the installation status of the second target accessory in the accessory information table, delete the server SN information and current rack position information contained in the second target accessory information, and update the accessory inventory quantity.

[0032] like Figure 4 As shown, Figure 4 This is a flowchart illustrating a configuration reduction process in an embodiment of the present invention. After a user initiates the configuration reduction process, the corresponding configuration reduction information can be sent to a preset client, enabling relevant personnel to perform specific configuration reduction operations based on this information. Specifically, this involves determining the machine information according to the data center and rack identifiers, removing the second target component from the corresponding machine, and returning completion information to the backend server after removal. The backend server can update the usage status of the second target component and delete the server SN, package name, and rack position information corresponding to the second target component from the component information table. Simultaneously, it can update the component inventory quantity, such as incrementing the inventory by 1.

[0033] The above-mentioned upgrade and downgrade processes both fall under the category of configuration modification processes, meaning they involve changing server components. Figure 5 As shown, users can submit a configuration change order, filling in the change type and information. When the change type is an increase, the backend server initiates an increase process, including parts issuance, data center configuration change, server asset information change, parts information change, and parts inventory change. When the change type is a decrease, the backend server initiates a decrease process, including data center decrease, data center feedback of decrease parts information, server asset information change, parts information change, and parts inventory change.

[0034] In one possible embodiment, the user can also initiate a repair process through a front-end page. For example, the user can select a repair option on the front-end page and fill in the required part identification, model, and corresponding rack and data center information to send a repair request. In another possible embodiment, in the event of a part failure, the agent program or cluster monitoring system in the machine can send equipment failure information to the back-end server. For example, upon detecting a hardware failure, the corresponding data can be filled in according to the work order format, and an equipment failure report can be generated and sent to the back-end server.

[0035] The backend server can receive fault information, which is triggered during the maintenance process and includes faulty part information and newly replaced part information. Based on the fault information, server SN information is added to the newly replaced part information in the part information table and the status of the newly replaced part is updated. The server SN information of the faulty part information is deleted and the status of the faulty part is updated.

[0036] In practical applications, the repair provider for parts is typically determined by whether they are under warranty. Therefore, after receiving fault information, the backend server can determine whether the faulty part is under warranty based on the faulty part information contained in the fault information. If it is under warranty, a fault report can be sent to the manufacturer's client so that the parts manufacturer can repair the faulty part. If the faulty part is not under warranty, a fault report can be sent to a pre-defined client so that relevant personnel within the enterprise can perform the specific repair operations.

[0037] After the relevant personnel complete the offline part replacement, they can return replacement completion information to the backend server and send the new replacement part information to the backend server. The candidate server can add machine and rack slot identifiers to the new replacement part information in the part information table, and update the new replacement part status to "in use". Simultaneously, the machine and rack slot identifiers can be deleted from the faulty part information in the part information table, and the faulty part status can be changed to "faulty". The machine part inventory is also updated accordingly; specifically, the inventory of the corresponding model of the new replacement part can be reduced by 1, and the inventory of the faulty part can be increased by 1, etc.

[0038] like Figure 6 As shown, Figure 6 This is a flowchart illustrating the parts repair process in the machine parts management method provided in this embodiment of the invention. After receiving a repair work order, the backend server determines whether the repair is by the manufacturer or by the user. If the repair is by the manufacturer, a repair request is sent to the manufacturer. Manufacturer personnel then perform the offline repair and replacement, and send the new part's serial number (SN) back to the backend server. The backend server updates the parts information table, specifically by changing the part's SN and its associated server identifier. If the repair is by the user, the server room personnel are notified to perform the offline repair. After the repair, the personnel send the new part's SN back to the backend server, and the backend server updates the parts information table.

[0039] In one possible embodiment, the method further includes: Receive requests for new accessories; The newly added accessory information is stored in the accessory information table according to the preset fields, and the accessory inventory quantity is updated; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

[0040] The aforementioned request for new parts can include batch addition of parts information. This information may include asset number, parts serial number (SN), parts type, specifications, parts model, parts source, modification status, usage status, server serial number (SN), manufacturer, cloud provider, modification package name, maintenance provider, parts status, asset ownership, remarks, delivery time, acceptance time, billing time, warranty expiration time, import time, and decommissioning time. This batch addition of parts information can be imported in tabular form, and the backend server can store this information in a parts information table.

[0041] like Figure 7 As shown, Figure 7 This is a flowchart illustrating the process of adding new parts in this embodiment of the invention. Specifically, after entering the parts procurement process, relevant personnel place an order. After the parts arrive at the data center, relevant personnel inspect the parts. If the inspection is successful, the parts are put into storage. Relevant personnel can send a request to add a new part and fill out a parts storage form to send the new part information to the backend server. The backend server can update the parts information table and the corresponding parts inventory based on the request to add a new part.

[0042] In the context of parts repair, there is also a process for adding new parts. Specifically, when it is necessary to replace equipment parts, the repair order is automatically updated, the information of the new replacement part is filled in, the information of the new replacement part is added to the parts information table, and the corresponding parts inventory is updated.

[0043] In one possible embodiment, authentication by relevant personnel is required before any specific modification, addition, or repair action is executed in the parts modification, addition, and repair process. For example, modification requests, addition requests, and repair requests can all include requester information, such as the requester's employee ID and name. After receiving the corresponding request, the backend server can forward the request to the target client for approval. The backend server can also perform a has check on the data for adding and removing items to determine if a has query interface is used, and can also perform a diff verification on the target client's approval and the has check. If approval information is received from the target client, the next step of the process can proceed; otherwise, an error message is returned.

[0044] In one possible embodiment, the parts information table can record machine parts information from different cloud services and synchronize this parts information table across different cloud services. It can also synchronize HAS data to the cloud platform, perform periodic data diffing, and push alarms.

[0045] By applying the embodiments of this invention, digital management of spare parts can be achieved, and spare parts information can be linked with relocation, reconfiguration, and repair processes, with real-time information updates to ensure accuracy. The entire process of spare parts procurement, acceptance and warehousing, shelving, repair and decommissioning can be clearly and completely recorded, improving the comprehensiveness of assets. Real-time collection of machine component SN information via machine agents allows for accurate and clear searching of the SN, model, manufacturer, specifications, and slot information for all server components, including CPUs, memory, hard drives, network cards, and RAID cards. It records and displays the usage and inventory status of each component, optimizing inventory structure and reducing inventory backlog. Furthermore, proper component inventory management can reduce the need for emergency procurement due to component shortages, thereby lowering procurement costs. This achieves the goal of accurate inventory recording, reducing manual verification costs, and potentially improving efficiency from 6 hours to 0.5 hours. The platform allows for digital modification of parts to meet various modification needs; it also improves the overall utilization rate of machines. The platform can flexibly suggest how to modify the machines to improve their overall energy efficiency and provide intelligent analysis and modification suggestions.

[0046] Based on the same inventive concept, embodiments of the present invention also provide a machine parts management platform, such as... Figure 8 As shown, the platform 800 may include: The acquisition module 801 is used to collect the component information of each machine using the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. The storage module 802 is used to store the machine information and accessory information according to preset fields, and to store the unused accessory information according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the SN, model, manufacturer, specifications and status of the unused accessory; The receiving module 803 is used to receive a component placement request, wherein the component placement request includes first target component information and target rack information; The execution module 804 is used to perform an update part operation according to the part listing request, update the status of the first target part in the part information table, fill in the machine SN information and rack position information of the first target part in the first target part information, and update the part inventory quantity.

[0047] In one possible embodiment, it is also used to receive an accessory removal request, wherein the accessory removal request includes information on a second target accessory; The execution module is further configured to perform an update part operation according to the part removal request, update the installation status of the second target part in the part information table, delete the server SN information and current rack position information contained in the second target part information, and update the part inventory quantity.

[0048] In one possible embodiment, the receiving module is further configured to receive fault information, wherein the fault information is triggered during the maintenance process, and the fault information includes faulty parts information and newly replaced parts information; The execution module is further configured to, based on the fault information, add server SN information to the new replacement part information in the parts information table and update the status of the new replacement part, and delete the server SN information to the faulty parts information and update the status of the faulty parts.

[0049] In one possible embodiment, the receiving module is further configured to receive a request for additional accessories; The execution module is further configured to store the newly added accessory information into the accessory information table according to the preset fields and update the accessory inventory quantity; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

[0050] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in this invention comply with relevant laws and regulations and do not violate public order and good morals.

[0051] An exemplary embodiment of the present invention also provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the electronic device to perform a method according to an embodiment of the present invention.

[0052] An exemplary embodiment of the present invention also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of the present invention.

[0053] An exemplary embodiment of the present invention also provides a computer program product, including a computer program, wherein, when executed by a computer's processor, the computer program is used to cause the computer to perform a method according to an embodiment of the present invention.

[0054] refer to Figure 9The present invention will now be described in the form of a structural block diagram of an electronic device 900 that can serve as a server or client of the present invention, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0055] like Figure 9 As shown, the electronic device 900 includes a computing unit 901, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 902 or a computer program loaded from a storage unit 908 into a random access memory (RAM) 903. The RAM 903 may also store various programs and data required for the operation of the electronic device 900. The computing unit 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0056] Multiple components in electronic device 900 are connected to I / O interface 905, including: input unit 906, output unit 907, storage unit 908, and communication unit 909. Input unit 906 can be any type of device capable of inputting information to electronic device 900. Input unit 906 can receive input digital or character information and generate key signal inputs related to user settings and / or function control of electronic device. Output unit 907 can be any type of device capable of presenting information and may include, but is not limited to, a display, speaker, video / audio output terminal, vibrator, and / or printer. Storage unit 908 may include, but is not limited to, disk and optical disk. Communication unit 909 allows electronic device 900 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and / or chipsets, such as Bluetooth™ devices, WiFi devices, WiMax devices, cellular communication devices, and / or the like.

[0057] The computing unit 901 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 901 performs the various methods and processes described above. For example, in some embodiments, any of the machine parts management methods described above can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 900 via ROM 902 and / or communication unit 909. In some embodiments, the computing unit 901 can be configured to perform any of the machine parts management methods described above by any other suitable means (e.g., by means of firmware).

[0058] The program code used to implement the methods of the present invention can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0059] In the context of this invention, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0060] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0061] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0062] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0063] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

Claims

1. A method for managing machine parts, characterized in that, The method, applied to a machine parts management platform, includes: The component information of each machine is collected by the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. The machine information and accessory information are stored according to preset fields, and the unused accessory information is stored according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the unused accessory's SN, model, manufacturer, specifications and status; Receive a component placement request, wherein the component placement request includes information on a first target component and information on a target rack; According to the accessory listing request, perform the accessory update operation, update the status of the first target accessory in the accessory information table, fill in the machine SN information and rack position information of the first target accessory information, and update the accessory inventory quantity.

2. The method according to claim 1, characterized in that, The method further includes: Receive an accessory removal request, wherein the accessory removal request includes information on a second target accessory; According to the accessory removal request, perform the accessory update operation, update the installation status of the second target accessory in the accessory information table, delete the server SN information and current rack position information contained in the second target accessory information, and update the accessory inventory quantity.

3. The method according to claim 1, characterized in that, The method further includes: Receive fault information, wherein the fault information is triggered during the maintenance process, and the fault information includes faulty parts information and newly replaced parts information; Based on the fault information, add server SN information to the new replacement part information in the parts information table and update the status of the new replacement part; delete the server SN information to the faulty part information and update the status of the faulty part.

4. The method according to claim 1, characterized in that, The method further includes: Receive requests for new accessories; The newly added accessory information is stored in the accessory information table according to the preset fields, and the accessory inventory quantity is updated; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

5. A machine parts management platform, characterized in that, The platform includes: The data acquisition module is used to collect component information of each machine using the agent program pre-deployed in each machine. The component information includes the serial number, model, manufacturer, specifications, slot and status of CPU, memory, hard disk, network card and RAID card components. The storage module is used to store the machine information and accessory information according to preset fields, and to store the unused accessory information according to the preset fields to obtain an accessory information table; wherein, the unused accessory information includes the unused accessory's SN, model, manufacturer, specifications and status; A receiving module is used to receive a component listing request, wherein the component listing request includes first target component information and target rack information; The execution module is used to perform an update part operation according to the part listing request, update the status of the first target part in the part information table, fill in the machine SN information and rack position information of the first target part in the part information, and update the part inventory quantity.

6. The platform according to claim 5, characterized in that, The receiving module is also used to receive a request to remove an accessory from the shelf, wherein the request to remove an accessory from the shelf includes information about a second target accessory. The execution module is further configured to perform an update part operation according to the part removal request, update the installation status of the second target part in the part information table, delete the server SN information and current rack position information contained in the second target part information, and update the part inventory quantity.

7. The platform according to claim 5, characterized in that, The receiving module is also used to receive fault information, wherein the fault information is triggered during the maintenance process and includes faulty parts information and newly replaced parts information; The execution module is further configured to, based on the fault information, add server SN information to the new replacement part information in the parts information table and update the status of the new replacement part, and delete the server SN information to the faulty parts information and update the status of the faulty parts.

8. The platform according to claim 5, characterized in that, The receiving module is also used to receive requests for new accessories; The execution module is further configured to store the newly added accessory information into the accessory information table according to the preset fields and update the accessory inventory quantity; wherein, the newly added accessory information includes the SN, model, manufacturer, specifications and status of the newly added accessory.

9. An electronic device, comprising: processor; as well as Stored program memory, The program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1-4.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-4.

Images