Personnel data management method and device, equipment and storage medium

Abstract

The invention relates to a personnel data management method and device, equipment and a storage medium. According to the main technical scheme, the method comprises the steps that effective fields of node responsible personnel of conventional type service nodes are obtained, the conventional type service nodes are nodes defined by a failure mode and an FMEA theoretical method, node data of the conventional type service nodes are aggregated according to the effective fields of the node responsible personnel, and a personnel service node set is obtained; according to the personnel business node set and the personnel data of the management node responsible personnel, the personnel data can be independently processed, dimension improvement is focused, the operation convenience of the personnel data is effectively improved, and the management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of FMEA data management, and in particular to a personnel data management method, device, equipment and storage medium. Background Art

[0002] Failure Mode and Effect Analysis (FMEA) is a systematic methodology used to identify potential failure modes during the product design and process design stages, evaluate the impact of these failure modes on system functions and their possible consequences, and give priority to preventive measures to reduce or eliminate potential product or process defects, so that quality engineers can take necessary measures in advance to prevent potential problems from occurring, thereby improving product quality and reliability.

[0003] At present, the digital management system based on FMEA theory regards the node person in charge as the attribution field of the general type business node defined by the seven-step method of FMEA theory. When viewing and editing the relevant data of the quality engineer responsible for a node, it is necessary to open the details of the general type business node first. The personnel data management process is cumbersome and not conducive to conducting business activities. Summary of the invention

[0004] Based on this, the present application provides a personnel data management method, device, equipment and storage medium to solve the problem that the personnel data management process is cumbersome and not conducive to conducting business activities.

[0005] In a first aspect, a personnel data management method is provided, the method comprising:

[0006] Get the valid fields of the node responsible person of the general type business node. The general type business node is the node defined by the failure mode and effect analysis FMEA theory method;

[0007] According to the valid fields of the node responsible person, the node data of the conventional type business nodes are aggregated to obtain the personnel business node set;

[0008] Based on the set of personnel business nodes, the management node is responsible for the personnel data of the personnel.

[0009] According to an achievable method in an embodiment of the present application, obtaining a valid field of a node responsible person of a conventional type service node includes:

[0010] Traverse the initial fields of the node responsible person of the general type business node;

[0011] Determine whether the initial field is empty;

[0012] The initial fields that are not empty are determined as valid fields for the node responsible person of the general type business node.

[0013] According to an achievable method in an embodiment of the present application, node data of conventional type business nodes are aggregated according to the valid fields of the node responsible person to obtain a personnel business node set, including:

[0014] According to the valid fields of the node responsible person, determine the regular type business node corresponding to each node responsible person;

[0015] According to the preset node categories, group the regular business nodes corresponding to the responsible personnel of each node;

[0016] The node identification numbers of the grouped general type business nodes are set to obtain a personnel business node set, which is displayed in the form of a card list view.

[0017] According to an achievable method in an embodiment of the present application, based on a set of personnel service nodes, a management node is responsible for personnel data of a person, including:

[0018] Receive the addition and deletion information of the target business node selected by the user based on the card list view;

[0019] According to the addition and deletion information, traverse all regular business nodes to determine the target business node;

[0020] Add or delete the personnel data of the personnel in charge of the target node corresponding to the target business node.

[0021] According to an achievable method in an embodiment of the present application, based on a set of personnel service nodes, a management node is responsible for personnel data of a person, including:

[0022] Receiving the responsible person switching information of the user selecting the responsible person of the target node based on the card list view;

[0023] According to the responsible person switching information, the personnel data of the responsible person of the target node corresponding to the conventional type business node is switched to the personnel data of the responsible person to be replaced.

[0024] According to an achievable method in an embodiment of the present application, based on a set of personnel service nodes, a management node is responsible for personnel data of a person, including:

[0025] Receive query information of the user selecting the person in charge of the target node based on the card list view;

[0026] According to the query information, find the regular type business node corresponding to the person in charge of the target node.

[0027] According to an achievable method in an embodiment of the present application, based on a set of personnel service nodes, a management node is responsible for personnel data of a person, including:

[0028] Receive global query information of a target business node of a target node responsible person selected by a user based on a card list view;

[0029] According to the global query information, obtain the node identification number of the target business node;

[0030] According to the node identification number of the target business node, query the personnel data of all node responsible persons corresponding to the target business node.

[0031] In a second aspect, a personnel data management device is provided, the device comprising:

[0032] An acquisition module is used to obtain valid fields of node responsible persons of conventional business nodes. Conventional business nodes are nodes defined by the failure mode and effect analysis FMEA theory method.

[0033] Aggregation module, used to aggregate node data of conventional business nodes according to valid fields of the node responsible personnel to obtain a set of personnel business nodes;

[0034] The management module is used to manage the personnel data of the personnel responsible for the node according to the personnel business node set.

[0035] In a third aspect, a computer device is provided, comprising:

[0036] at least one processor; and

[0037] a memory communicatively connected to the at least one processor; wherein,

[0038] The memory stores computer instructions that can be executed by the at least one processor, and the computer instructions are executed by the at least one processor to enable the at least one processor to perform the method involved in the first aspect above.

[0039] In a fourth aspect, a computer-readable storage medium is provided, on which computer instructions are stored, characterized in that the computer instructions are used to enable a computer to execute the method involved in the first aspect above.

[0040] According to the technical content provided in the embodiments of the present application, the valid fields of the node responsible personnel of the conventional type business node are obtained. The conventional type business node is a node defined by the failure mode and effects analysis FMEA theory method. According to the valid fields of the node responsible personnel, the node data of the conventional type business node is aggregated to obtain a personnel business node set. According to the personnel business node set, the personnel data of the node responsible personnel is managed, and the personnel data can be processed independently, focusing on dimensional improvement, effectively improving the operational convenience of the personnel data, and improving management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 An application environment diagram of a personnel data management method in one embodiment;

[0042] Figure 2 A flowchart of a personnel data management method in one embodiment;

[0043] Figure 3 is a structural block diagram of a personnel data management device in one embodiment;

[0044] Figure 4 FIG. 4 is a schematic structural diagram of a computer device in one embodiment. DETAILED DESCRIPTION

[0045] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0046] At present, the personnel fields of the digital management system based on FMEA theory are wrapped by conventional business nodes, and the data hierarchy is deeply nested, which makes the personnel data management process cumbersome and is not conducive to business activities. For example, as the belonging field of the conventional business node, when viewing and editing, the personnel field needs to open the details of the conventional business node before it can be seen, which makes the viewing process cumbersome. When the quality engineer modifies the node person in charge of the conventional business node, he needs to search and modify the person in charge one by one according to the queried conventional business node, which makes the modification process complicated. Because the personnel data is wrapped in the conventional business node, the page display is not intuitive and it is very inconvenient to view, especially when there are personnel changes, the modification of data fields is very cumbersome.

[0047] In order to solve the problems of the prior art, the embodiments of the present application provide a personnel data management method, device, equipment and computer storage medium. For ease of understanding, the system to which the present application is applicable is first described. The personnel data management method provided by the present application can be applied to Figure 1In the system architecture shown. Among them, the terminal 110 communicates with the server 120 through the network. The user operates the digital management system based on the FMEA theory through the terminal 110, and the terminal 110 receives the user's operation information and sends the operation information to the server 120. The server 120 obtains the valid fields of the node responsible personnel of the conventional type business node based on the operation information. The conventional type business node is a node defined by the failure mode and effect analysis FMEA theory method. According to the valid fields of the node responsible personnel, the node data of the conventional type business node is aggregated to obtain the personnel business node set. According to the personnel business node set, the personnel data of the node responsible personnel is managed. Among them, the terminal 110 can be but not limited to various personal computers, laptops, smart phones and tablets, and the server 120 can be implemented with an independent server or a server cluster composed of multiple servers.

[0048] Figure 2 FIG. 1 is a flow chart of a personnel data management method provided by an embodiment of the present application. Figure 2 As shown, the method may include the following steps:

[0049] S210, obtaining valid fields of the node responsible person of the conventional type business node.

[0050] Conventional business nodes are nodes defined by the failure mode and effects analysis FMEA theory method, which may include structure nodes, function nodes, requirement / characteristic nodes, failure nodes, preventive measures, preventive controls, detection measures, detection control nodes, optimized preventive measures, optimized preventive controls, optimized detection measures, and optimized detection control nodes.

[0051] The node responsible person can be a technician or a manager. Conventional business nodes will be assigned corresponding responsible persons according to actual needs, timely discover potential failure modes in the product design stage and process design stage, evaluate the impact of these failure modes on system functions and their possible consequences, and take preventive measures to reduce or eliminate potential product or process defects.

[0052] The valid field is a field whose field value is not empty, which is used to indicate that the general type business node has a corresponding node responsible person. The fields of the node responsible persons of all general type business nodes are traversed to filter out the valid fields.

[0053] S220, aggregating node data of conventional business nodes according to valid fields of the node responsible personnel to obtain a personnel business node set.

[0054] Based on the valid fields of the node responsible person, determine the general type business node corresponding to each node responsible person, and use the node responsible person as the data node to aggregate the node data of the corresponding general type business node to obtain the personnel business node set. The personnel business node set is displayed in the form of a card list view, including avatar information, personnel name, work number, position, and classified display of the general type business nodes to which they belong. The naming of the general type business nodes is mainly based on the extracted node name keywords, and the general type business node drop-down data content is the specific node name. The personnel business node set also has some functional operation options, such as search function options, delete function options, and switch function options. The content is converted from filling in text data to check options, drop-down selection items, check options, etc., which greatly reduces the operating costs of engineers.

[0055] By defining the personnel node as a general type business node responsible for data aggregation of personnel fields, reversely aggregating general type business nodes with personnel fields, and distinguishing the categories of general type business nodes, the personnel fields are no longer wrapped by general type business nodes, and the personnel data can be processed independently, focusing on dimensional improvement, effectively improving the operational convenience of personnel data.

[0056] S230, according to the personnel business node set, the management node is responsible for the personnel data of the personnel.

[0057] Personnel data can be managed through the personnel business node set. The management methods include but are not limited to personnel deletion, personnel switching, personnel addition, personnel data search, etc., to achieve linked batch operation processing of personnel data and improve management efficiency.

[0058] It can be seen that the embodiment of the present application obtains the valid fields of the node responsible personnel of the conventional type business node, and the conventional type business node is a node defined by the failure mode and effect analysis FMEA theory method. According to the valid fields of the node responsible personnel, the node data of the conventional type business node is aggregated to obtain a personnel business node set. According to the personnel business node set, the personnel data of the node responsible personnel is managed, and the personnel data can be processed independently, focusing on dimensional improvement, effectively improving the operational convenience of personnel data, and improving management efficiency.

[0059] As an achievable method, the valid fields of the node responsible person of the general type business node are obtained, including:

[0060] Traverse the initial fields of the node responsible person of the general type business node;

[0061] Determine whether the initial field is empty;

[0062] The initial fields that are not empty are determined as valid fields for the node responsible person of the general type business node.

[0063] The initial field is a field corresponding to the regular type business node that may be responsible for the node. The initial field may or may not contain a field value. The initial field is obtained by traversing the data of the node responsible person of the regular type business node. After obtaining the initial field, it is determined whether the initial field is empty. If the initial field is empty, it means that the regular type business node does not require a person in charge temporarily, and the node is ignored. If the initial field is not empty, it means that the regular type business node has a person in charge, and the field is determined as a valid field of the node responsible person of the regular type business node, so as to determine all the persons in charge of the regular type business node.

[0064] As an achievable method, according to the valid fields of the node responsible person, the node data of the general type of business nodes are aggregated to obtain the personnel business node set, including:

[0065] According to the valid fields of the node responsible person, determine the regular type business node corresponding to each node responsible person;

[0066] According to the preset node categories, classify the conventional business nodes corresponding to the responsible personnel of each node;

[0067] The node identification number of the classified general type business node is set to obtain a personnel business node set, which is displayed in the form of a card list view.

[0068] The same person may be responsible for multiple regular business nodes. First, take the regular business nodes as the main line and extract the valid fields of the person in charge of each regular business node. According to the number of valid fields of the node responsible person, all regular business nodes that the person is responsible for can be determined. In this way, the regular business nodes are divided into multiple groups of regular business nodes based on the node responsible person.

[0069] The preset node categories are pre-divided based on the FMEA seven-step theory, and may include structure, function, requirement / characteristic, failure, preventive measures, preventive control, detection measures, detection control nodes, optimized preventive measures, optimized preventive control, optimized detection measures, optimized detection control, etc. Based on the preset node categories, the conventional type business nodes corresponding to each node responsible person are grouped, that is, each group of conventional type business nodes is classified to obtain a plurality of categories of conventional type business node groups corresponding to a node responsible person.

[0070] Set the node identification number ID of the classified general type business node, so that after clicking the general type business node, the node information can be checked by ID to obtain the personnel business node collection. The personnel business node collection is displayed in the form of a card list view, and the aggregation method is intuitive and easy to operate.

[0071] As an achievable approach, based on the personnel business node set, the management node is responsible for the personnel data of the personnel, including:

[0072] Receive the addition and deletion information of the target business node selected by the user based on the card list view;

[0073] According to the addition and deletion information, traverse all regular business nodes to determine the target business node;

[0074] Add or delete the personnel data of the personnel in charge of the target node corresponding to the target business node.

[0075] The target node responsible person is the node responsible person whose management personnel data the user wants to query, the target business node is the business node that the user wants to query and process, and the addition and deletion information is the operation information entered by the user through the terminal, including adding instructions and deleting instructions. The adding instructions include adding personnel fields, adding node IDs, adding categories, etc., and the deleting instructions include deleting personnel fields, deleting node IDs, deleting categories, etc. According to the node ID in the addition and deletion information, all regular business nodes are traversed to determine the target business node, and the field of the target node responsible person is matched according to the personnel field, so as to determine the target node responsible person in the target business node, and the personnel data of the target node responsible person is added or deleted. In the card list view corresponding to the target node responsible person, the delete function option and the add function option are set. In the card list view, multiple target business nodes can be selected and the delete function option can be clicked to delete in batches. In the card list view corresponding to the target node responsible person, click the add function option to find the existing regular business node, that is, the target business node is added to the card list view of the current person, and the field assignment of the node responsible person of the regular business node is completed.

[0076] As an achievable approach, based on the personnel business node set, the management node is responsible for the personnel data of the personnel, including:

[0077] Receiving the responsible person switching information of the user selecting the responsible person of the target node based on the card list view;

[0078] According to the responsible person switching information, the personnel data of the responsible person of the target node corresponding to the conventional type business node is switched to the personnel data of the responsible person to be replaced.

[0079] The responsible person switching information includes the basic information of the responsible person of the target node and the basic information of the responsible person to be replaced, where the basic information may include avatar information, name, work number, and position, etc. You can switch based on the name of the responsible person of the target node and the responsible person to be replaced, or you can switch based on the work number of the responsible person of the target node and the responsible person to be replaced. In the card list view corresponding to the responsible person of the target node, click the switch function option to switch in batches.

[0080] As an achievable approach, based on the personnel business node set, the management node is responsible for the personnel data of the personnel, including:

[0081] Receive query information of the user selecting the person in charge of the target node based on the card list view;

[0082] According to the query information, find the regular type business node corresponding to the person in charge of the target node.

[0083] The query information is the node information entered by the user to query whether the target node responsible person is responsible for a certain general type business node, which can include node abbreviation, node full name, node code and other information. Match the general type business nodes that are consistent with the query information in all general type business nodes of the target node responsible person. In the card list view corresponding to the target node responsible person, click the query function option to quickly find the node that the target node responsible person is responsible for. If the node being searched is the node that the person is responsible for, it will be displayed in the card list view corresponding to the target node responsible person. If the node being searched is not the node that the person is responsible for, the card list view corresponding to the target node responsible person will show that the node is not found.

[0084] As an achievable approach, based on the personnel business node set, the management node is responsible for the personnel data of the personnel, including:

[0085] Receive global query information of a target business node of a target node responsible person selected by a user based on a card list view;

[0086] According to the global query information, obtain the node identification number of the target business node;

[0087] According to the node identification number of the target business node, query the personnel data of all node responsible persons corresponding to the target business node.

[0088] The global query information is the node information entered by the user to query all personnel data of a certain conventional type business node corresponding to the person in charge of the target node, which may include node abbreviation, node full name, node code, etc. The conventional type business node consistent with the global query information is matched among all conventional type business nodes of the person in charge of the target node, that is, the target business node, and the node identification number ID of the target business node is obtained. The relevant interface can use the node ID to find the personnel data of all the persons in charge of the target business node corresponding to the node.

[0089] It should be understood that although Figure 2 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in the application, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0090] Figure 3 A schematic diagram of a personnel data management device provided in an embodiment of the present application, which can be arranged in Figure 1 The server 120 in the system shown is used to execute the following Figure 2 The method flow shown in Figure 3 As shown, the device may include: an acquisition module 310, an aggregation module 320 and a management module 330, wherein the main functions of each component module are as follows:

[0091] An acquisition module 310 is used to acquire a valid field of a node responsible person of a conventional type business node, wherein the conventional type business node is a node defined by a failure mode and effects analysis FMEA theory method;

[0092] Aggregation module 320, used to aggregate the node data of the conventional type business nodes according to the valid fields of the node responsible personnel to obtain a personnel business node set;

[0093] The management module 330 is used to manage the personnel data of the personnel in charge of the node according to the personnel business node set.

[0094] As an implementable method, the acquisition module 310 is specifically used to obtain the valid fields of the node responsible person of the conventional type business node, including: traversing the initial fields of the node responsible person of the conventional type business node; determining whether the initial fields are empty; and determining the initial fields that are not empty as the valid fields of the node responsible person of the conventional type business node.

[0095] As an implementable method, the aggregation module 320 is specifically used to determine the general type business nodes corresponding to each node responsible person according to the valid fields of the node responsible person; group the general type business nodes corresponding to each node responsible person according to the preset node category; set the node identification number of the grouped general type business nodes to obtain a personnel business node set, and the personnel business node set is displayed in the form of a card list view.

[0096] As an achievable method, the management module 330 is specifically used to receive the addition and deletion information of the target business node of the target node responsible person selected by the user based on the card list view; according to the addition and deletion information, traverse all regular type business nodes to determine the target business node; and add or delete the personnel data of the target node responsible person corresponding to the target business node.

[0097] As an implementable method, the management module 330 is specifically used to receive the responsible personnel switching information of the target node responsible personnel selected by the user based on the card list view; according to the responsible personnel switching information, the personnel data of the target node responsible personnel corresponding to the conventional type business node is switched to the personnel data of the responsible personnel to be replaced.

[0098] As an implementable manner, the management module 330 is specifically configured to receive query information of a user selecting a target node responsible person based on a card list view; and search for a conventional type of business node corresponding to the target node responsible person according to the query information.

[0099] As an implementable method, the management module 330 is specifically used to receive global query information of the target business node of the target node responsible person selected by the user based on the card list view; obtain the node identification number of the target business node based on the global query information; and query the personnel data of all node responsible persons corresponding to the target business node based on the node identification number of the target business node.

[0100] The same or similar parts between the above embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0101] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described in this article within the scope permitted by applicable laws and regulations, provided that the applicable laws and regulations of the country are met (for example, the user's explicit consent, effective notification to the user, and the user's explicit authorization, etc.).

[0102] According to an embodiment of the present application, the present application also provides a computer device and a computer-readable storage medium.

[0103] like Figure 4 , is a block diagram of a computer device according to an embodiment of the present application. The computer device is intended to represent various forms of digital computers or mobile devices. The digital computer may include a desktop computer, a portable computer, a workbench, a personal digital assistant, a server, a mainframe computer, and other suitable computers. The mobile device may include a tablet computer, a smart phone, a wearable device, etc.

[0104] like Figure 4 As shown, computer device 400 includes computing unit 401, ROM 402, RAM 403, bus 404, and input / output (I / O) interface 405, and computing unit 401, ROM 402, and RAM 403 are connected to each other through bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0105] The computing unit 401 can perform various processes in the method embodiment of the present application according to the computer instructions stored in the read-only memory (ROM) 402 or the computer instructions loaded from the storage unit 408 to the random access memory (RAM) 403. The computing unit 401 can be various general and / or special processing components with processing and computing capabilities. The computing unit 401 may include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. In some embodiments, the method provided in the embodiment of the present application can be implemented as a computer software program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 408.

[0106] RAM 403 may also store various programs and data required for the operation of computer device 400. Part or all of the computer program may be loaded and / or installed on computer device 400 via ROM 402 and / or communication unit 409.

[0107] The input unit 406, output unit 407, storage unit 408 and communication unit 409 in the computer device 400 can be connected to the I / O interface 405. The input unit 406 can be, for example, a keyboard, a mouse, a touch screen, a microphone, etc. The output unit 407 can be, for example, a display, a speaker, an indicator light, etc. The computer device 400 can exchange information, data, etc. with other devices through the communication unit 409.

[0108] It should be noted that the device may also include other components necessary for normal operation, or may only include components necessary for implementing the solution of the present application, rather than all the components shown in the figure.

[0109] Various implementations of the systems and techniques described herein can be realized in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof.

[0110] The computer instructions for implementing the method of the present application can be written in any combination of one or more programming languages. These computer instructions can be provided to the computing unit 401, so that when the computer instructions are executed by the computing unit 401 such as a processor, the steps involved in the method embodiment of the present application are executed.

[0111] The computer-readable storage medium provided in the present application may be a tangible medium that may contain or store computer instructions for executing the steps involved in the method embodiments of the present application. The computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, and other forms of storage media.

[0112] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A personnel data management method, characterized in that: The method comprises: Obtain the valid fields of the node responsible person of the conventional type business node, wherein the conventional type business node is a node defined by the failure mode and effect analysis FMEA theory method; According to the valid fields of the node responsible person, the node data of the conventional type business nodes are aggregated to obtain a personnel business node set; According to the personnel service node set, the personnel data of the personnel in charge of the node are managed.

2. The method according to claim 1, characterized in that The valid fields for obtaining the node responsible person of the conventional type service node include: Traversing the initial fields of the node responsible persons of the conventional type service nodes; Determine whether the initial field is empty; The initial fields that are not empty are determined as valid fields for the node responsible person of the conventional type service node.

3. The method according to claim 1, characterized in that The node data of the conventional type business nodes are aggregated according to the valid fields of the node responsible person to obtain a personnel business node set, including: Determining the conventional type service node corresponding to each node responsible person according to the valid field of the node responsible person; According to the preset node categories, the conventional business nodes corresponding to the responsible personnel of each node are grouped; The node identification numbers of the grouped conventional type business nodes are set to obtain a personnel business node set, which is presented in the form of a card list view.

4. The method according to any one of claims 1 to 3, characterized in that: The managing the personnel data of the personnel responsible for the node according to the personnel business node set includes: Receive the addition and deletion information of the target business node selected by the user based on the card list view; According to the addition and deletion information, traverse all conventional service nodes to determine the target service node; The personnel data of the personnel in charge of the target node corresponding to the target business node is added or deleted.

5. The method according to claim 3, characterized in that: The managing the personnel data of the personnel responsible for the node according to the personnel business node set includes: Receiving the responsible person switching information of the user selecting the responsible person of the target node based on the card list view; According to the responsible personnel switching information, the personnel data of the responsible personnel of the target node corresponding to the conventional type service node is switched to the personnel data of the responsible personnel to be replaced.

6. The method according to claim 3, characterized in that: The managing the personnel data of the personnel responsible for the node according to the personnel business node set includes: Receive query information of the user selecting the person in charge of the target node based on the card list view; According to the query information, a conventional type business node corresponding to the person in charge of the target node is searched.

7. The method according to claim 3, characterized in that The managing the personnel data of the personnel responsible for the node according to the personnel business node set includes: Receive global query information of a target business node of a target node responsible person selected by a user based on a card list view; Acquire a node identification number of the target service node according to the global query information; According to the node identification number of the target service node, the personnel data of all node responsible persons corresponding to the target service node are queried.

8. A personnel data management device, characterized in that: The device comprises: An acquisition module, used to acquire valid fields of node responsible persons of conventional type business nodes, wherein the conventional type business nodes are nodes defined by the failure mode and effect analysis FMEA theory method; An aggregation module, used to aggregate the node data of the conventional type business nodes according to the valid fields of the person in charge of the node, to obtain a set of personnel business nodes; A management module is used to manage the personnel data of the personnel in charge of the node according to the personnel business node set.

9. A computer device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores computer instructions that can be executed by the at least one processor, and the computer instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having computer instructions stored thereon, characterized in that: The computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.

Images