Risk grading management and control method and device applied to project and electronic equipment

Abstract

The invention discloses a risk grading management and control method and device applied to a project and electronic equipment, and relates to the field of data processing. In the method, a current work item is obtained, and the current work item comprises a plurality of item units; obtaining the work progress of each project unit; determining a target project unit with an overdue risk in the plurality of project units; determining one or more target primary causal nodes causing an overdue risk of the target project unit; analyzing each target primary causal node, and determining one or more target secondary causal nodes causing occurrence of each target primary causal node; analyzing a target risk influence value of the target project unit on the overdue risk; and obtaining the risk influence degree of the current work project. And determining a corresponding risk response strategy in a preset overdue risk response library according to the risk influence degree. By implementing the technical scheme provided by the invention, the overdue risks can be graded, and different strategies are adopted for different grades.

Description

Technical Field

[0001] The present application relates to the field of data processing, and specifically to a risk classification management method, device and electronic equipment applied to a project. Background Art

[0002] As the field of project management continues to develop and become more complex, risk management has become an integral part of project success. From traditional intuitive judgment to modern quantitative analysis methods, risk management strategies and tools have made significant progress in the past few decades. There are many types of risks in a project, among which the risk of overtime is particularly important, which is directly related to whether the project can be completed as planned. Over time, project overtime may lead to increased costs, decreased benefits, or even project failure.

[0003] At present, grading and judging the risk of overdue projects is an important part of achieving effective management. By classifying risks into three levels: low, medium, and high, managers can allocate resources and attention in a targeted manner. Low risks may only require routine monitoring, while high risks may require immediate action or a detailed response plan. Medium risks are in between and may require further analysis to determine whether special measures are needed. This automated grading method can help prioritize the most urgent and potentially most negative issues, while reducing the waste of resources due to overreaction. Therefore, it is very important to grad and control the risk of overdue.

[0004] Therefore, there is an urgent need for a risk classification management method, device and electronic equipment applied to projects. Summary of the invention

[0005] The present application provides a risk grading control method, device and electronic equipment applied to a project, so as to grade the overdue risks and adopt different strategies for different grades.

[0006] In the first aspect of the present application, a risk classification management method for a project is provided, the method comprising: obtaining a current work project, the current work project comprising a plurality of project units; obtaining the work progress of each of the project units; determining a target project unit with a risk of overdue among the plurality of project units according to the work progress; determining a target accident tree corresponding to the target project unit in a preset accident tree library; analyzing the target project unit according to the first-level logical relationship of the target accident tree, and determining one or more target primary causal nodes that cause the target project unit to have the risk of overdue; analyzing each of the target primary causal nodes according to the second-level logical relationship of the target accident tree, and determining one or more target secondary causal nodes that cause each of the target primary causal nodes to occur; analyzing the target risk impact value of the target project unit on the risk of overdue; integrating each of the target risk impact values ​​to obtain the risk impact degree of the current work project, the risk impact degree including low risk, medium risk and high risk. According to the risk impact degree, determining a corresponding risk response strategy in a preset overdue risk response library, the overdue risk response library including the corresponding relationship between the risk impact degree and the risk response strategy.

[0007] By adopting the above technical solution, by obtaining the work progress of the project unit and determining the target project unit with overdue risk, the solution can timely identify which project units may cause the entire project schedule to be delayed. Further analysis helps to determine the primary and secondary causal nodes of the overdue risk, providing an in-depth understanding of possible risk sources. The accident tree analysis method is applied to analyze the factors leading to the overdue risk through logical relationships. This structured method helps to reveal various potential risk factors and their associations, providing a clear framework for risk management. By analyzing the impact value of the target project unit on the overdue risk, the solution can quantitatively evaluate the risk impact of the project unit. This quantitative method helps to objectively judge the risk level and provide data support for further risk processing. According to the different risk impact levels (low, medium, and high risks), the corresponding risk response strategy can be quickly determined in the preset overdue risk response library. This supporting response measure library ensures the rapidity and pertinence of risk management and improves the efficiency of risk response.

[0008] Optionally, before obtaining the current work project, the method further includes: obtaining historical work projects, wherein the historical work projects include multiple historical project units; extracting the historical project units to obtain top-level nodes, primary causal nodes, and secondary causal nodes corresponding to the multiple historical project units; wherein the top-level node is a project overdue event, the primary causal node is an intermediate event that causes the project overdue event, and the secondary causal node is a basic event that causes the intermediate event; constructing the first-level logical relationship between the top-level node and the primary causal node, wherein one top-level node corresponds to one or more primary causal nodes, and the first-level logical relationship includes a first logical AND gate and a first logical OR gate; constructing the second-level logical relationship between the primary causal node and the secondary causal node, wherein one primary causal node corresponds to one or more secondary causal nodes, and the second-level logical relationship includes a second logical AND gate and a second logical OR gate; constructing an accident tree corresponding to the historical project unit according to the first-level logical relationship and the second-level logical relationship, wherein one historical project unit corresponds to one accident tree; and storing each of the historical project units and the corresponding accident tree in the preset accident tree library.

[0009] By adopting the above technical solution, by acquiring historical work projects, it is possible to collect and store past project data and information, and provide reference and reference for current work projects. By extracting and sorting historical project units, the top-level nodes, primary causal nodes, and secondary causal nodes corresponding to multiple historical project units can be obtained. These nodes represent project overdue events, intermediate events that cause overdue events, and basic events that cause intermediate events. By constructing the first-level logical relationship and the second-level logical relationship, the logical relationship between the top-level node and the primary causal node, and between the primary causal node and the secondary causal node can be established. This helps to clarify the causal relationship between events, as well as the logical combination and reasoning of events. According to the first-level logical relationship and the second-level logical relationship, the accident tree corresponding to each historical project unit can be constructed. Each historical project unit and its corresponding accident tree are stored in a preset accident tree library to form an experience library or knowledge library. This library can be used as a reference and reference to provide a basis and guidance for risk management and prediction of current work projects.

[0010] Optionally, analyzing the target risk impact value of the target project unit on the overdue risk specifically includes: obtaining the first probability value of the target secondary causal node occurring and the first number of overdue days caused by the target secondary causal node input by the user; based on a preset calculation rule, calculating the second probability value of the target primary causal node occurring and the second number of overdue days caused by the target secondary causal node according to the second-level logical relationship, the first probability value and the first number of overdue days; based on the preset calculation rule, calculating the target probability and target number of overdue days of the overdue risk occurring in the target project unit according to the first-level logical relationship, the second probability value and the second number of overdue days; multiplying the target probability and the target number of overdue days to obtain the target risk impact value.

[0011] By adopting the above technical solution, by obtaining the first probability value of the target secondary causal node input by the user and the first overdue days caused, the probability and overdue time data of the target secondary causal node can be obtained, which is the basis for calculating the target risk impact value. According to the preset calculation rules and the second-level logical relationship, combined with the probability and overdue days of the target secondary causal node, the second probability value of the target primary causal node and the second overdue days caused by the target secondary causal node can be calculated. This calculation process takes into account the causal relationship and probability transmission rules between events. Based on the preset calculation rules and the first-level logical relationship, combined with the second probability value and the second overdue days, the target probability and target overdue days of the target project unit overdue risk can be calculated. This calculation process comprehensively considers the impact of the primary causal node and the secondary causal node on the target risk. Multiplying the target probability and the target overdue days can obtain the target risk impact value. This value can be used to evaluate the degree of influence of the target project unit on the overdue risk, and the higher the value, the more serious the risk impact.

[0012] Optionally, based on a preset calculation rule, the second probability value of the occurrence of the target primary causal node and the second overdue number of days caused by the target secondary causal node are calculated according to the second-level logical relationship, the first probability value and the first overdue number of days, specifically including: if the target secondary causal node is connected to the target primary causal node through the second logical AND gate, the second probability value is the product of each of the first probability values, and the second overdue number of days is the average of each of the first overdue numbers; if the target secondary causal node is connected to the target primary causal node through the second logical OR gate, the second probability value is the probability value of at least one of the first probability values ​​occurring, and the second overdue number of days is the overdue number that ranks first after the first overdue numbers are arranged in order from large to small.

[0013] By adopting the above technical solution, the target secondary causal node is connected to the target primary causal node through a logical AND gate, then the second probability value will be the product of each first probability value, indicating the probability of the target primary causal node occurring when all relevant causal nodes occur. The second overdue days is the average of each first overdue days, indicating the average overdue days caused by the target primary causal node when all relevant causal nodes occur. If the target secondary causal node is connected to the target primary causal node through a logical OR gate, then the second probability value will be the probability value of at least one of the first probability values ​​occurring, indicating the probability of the target primary causal node occurring when at least one relevant causal node occurs. The second overdue days is to arrange each first overdue day in order from large to small, and take the overdue days ranked first, indicating the longest overdue days caused by the target primary causal node when at least one relevant causal node occurs.

[0014] Optionally, based on the work progress, a target project unit among the multiple project units that has a risk of being overdue is determined, specifically including: monitoring the work progress of each of the project units; judging whether the work progress of each of the project units is within the preset planned progress range; if the work progress of the target project unit is not within the preset planned progress range, determining that the target project unit has a risk of being overdue.

[0015] By adopting the above technical solution, the work progress of each project unit is monitored; the monitored work progress is compared with the preset planned progress range. The preset planned progress range is set in advance and is used to guide the time target of project progress. If it is judged that the work progress of the target project unit is not within the preset planned progress range, it can be determined which project units are at risk of overdue, that is, the work progress has exceeded or delayed the preset planned progress range.

[0016] Optionally, each of the target risk impact values ​​is integrated to obtain the risk impact degree of the current work project, specifically including: according to a preset weight database, obtaining the target weight corresponding to the target project unit; according to the target weight, weighted summing up each of the target risk impact values ​​to obtain a weighted sum value; if the weighted sum value is less than or equal to a preset first threshold, determining that the risk impact degree of the current work project is the low risk; if the weighted sum value is greater than the preset first threshold and less than a preset second threshold, determining that the risk impact degree of the current work project is the medium risk; if the weighted sum value is greater than or equal to the preset second threshold, determining that the risk impact degree of the current work project is the high risk.

[0017] By adopting the above technical solution, according to the preset weight database, the target weight corresponding to each target project unit can be obtained. The target weight reflects the importance or priority of each target project unit in the overall project. The target weight is used to perform weighted summation on each target risk impact value. The weighted sum value is the result of multiplying each target risk impact value by the corresponding target weight and adding them together. The risk impact degree of the current work project is determined by comparing the weighted sum value with the preset threshold.

[0018] If the weighted sum is less than or equal to the preset first threshold, the risk impact of the current work project is determined to be low risk. If the weighted sum is greater than the preset first threshold and less than the preset second threshold, the risk impact of the current work project is determined to be medium risk. If the weighted sum is greater than or equal to the preset second threshold, the risk impact of the current work project is determined to be high risk. Through the above integration and judgment, the risk impact values ​​of each target can be weighted, and the risk impact of the current work project can be determined according to the size of the weighted sum. This helps project managers comprehensively consider the importance and risk impact of each target in order to better assess and respond to the overall risk of the project.

[0019] Optionally, after determining the corresponding risk response strategy in a preset overdue risk response library according to the risk impact level, the method further includes: displaying prompt information, wherein the prompt information is used to prompt the user of the risk response strategy that can be adopted; and monitoring the work progress of the target project unit in real time.

[0020] By adopting the above technical solution, according to the determined risk impact, the corresponding risk response strategy is determined in the preset overdue risk response library. Then the corresponding prompt information is displayed to provide the user with the risk response strategy that can be adopted. The prompt information can help the user understand how to deal with the overdue risk faced by the current project and provide relevant prompts and guidance.

[0021] In a second aspect of the present application, a risk classification control device for a project is provided, the device comprising: an acquisition module and a processing module; the acquisition module is used to acquire a current work project, the current work project comprising a plurality of project units; the acquisition module is also used to acquire the work progress of each of the project units; the processing module is used to determine a target project unit with a risk of overdue among the plurality of project units according to the work progress; the processing module is also used to determine a target accident tree corresponding to the target project unit in a preset accident tree library; the processing module is also used to analyze the target project unit according to the first-level logical relationship of the target accident tree, and determine one or more target primary causal nodes that cause the target project unit to have the risk of overdue; the processing module is also used to analyze each of the target primary causal nodes according to the second-level logical relationship of the target accident tree, and determine one or more target secondary causal nodes that cause each of the target primary causal nodes to occur; the processing module is also used to analyze the target risk impact value of the target project unit on the risk of overdue; the processing module is also used to integrate each of the target risk impact values ​​to obtain the risk impact degree of the current work project, the risk impact degree including low risk, medium risk and high risk. The processing module is further used to determine a corresponding risk response strategy in a preset overdue risk response library according to the risk impact degree, and the overdue risk response library includes a correspondence between the risk impact degree and the risk response strategy.

[0022] In the third aspect of the present application, an electronic device is provided, including a processor, a memory, a user interface and a network interface, the memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes any one of the above methods.

[0023] In a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the instructions are executed, the method steps shown above are executed.

[0024] In summary, one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: 1. By obtaining the work progress of the project unit and determining the target project unit with overdue risk, the scheme can timely identify which project units may cause the entire project schedule to be delayed. Further analysis helps to determine the primary and secondary causal nodes of the overdue risk, providing an in-depth understanding of possible risk sources. The accident tree analysis method is applied to analyze the factors leading to the overdue risk through logical relationships. This structured method helps to reveal various potential risk factors and their associations, providing a clear framework for risk management. By analyzing the impact value of the target project unit on the overdue risk, the scheme can quantitatively evaluate the risk impact of the project unit. This quantitative method helps to objectively judge the risk level and provide data support for further risk handling. According to the different risk impact levels (low, medium, and high risks), the corresponding risk response strategy can be quickly determined in the preset overdue risk response library. This supporting response measure library ensures the rapidity and pertinence of risk management and improves the efficiency of risk response.

[0025] 2. By acquiring historical work projects, it is possible to collect and store past project data and information, and provide reference and reference for current work projects. By extracting and sorting historical project units, the top-level nodes, primary causal nodes, and secondary causal nodes corresponding to multiple historical project units can be obtained. These nodes represent project overdue events, intermediate events that cause overdue events, and basic events that cause intermediate events. By constructing the first-level logical relationship and the second-level logical relationship, the logical relationship between the top-level node and the primary causal node, and between the primary causal node and the secondary causal node can be established. This helps to clarify the causal relationship between events, as well as the logical combination and reasoning of events. According to the first-level logical relationship and the second-level logical relationship, the accident tree corresponding to each historical project unit can be constructed. By storing each historical project unit and its corresponding accident tree in the preset accident tree library, an experience library or knowledge library can be formed. This library can be used as a reference and reference to provide a basis and guidance for risk management and prediction of current work projects.

[0026] 3. By obtaining the first probability value of the target secondary causal node input by the user and the first overdue days caused, the probability and overdue time data of the target secondary causal node can be obtained, which is the basis for calculating the target risk impact value. According to the preset calculation rules and the second-level logical relationship, combined with the probability and overdue days of the target secondary causal node, the second probability value of the target primary causal node and the second overdue days caused by the target secondary causal node can be calculated. This calculation process takes into account the causal relationship and probability transmission rules between events. Based on the preset calculation rules and the first-level logical relationship, combined with the second probability value and the second overdue days, the target probability and target overdue days of the target project unit overdue risk can be calculated. This calculation process comprehensively considers the impact of the primary causal node and the secondary causal node on the target risk. Multiplying the target probability and the target overdue days can get the target risk impact value. This value can be used to evaluate the impact of the target project unit on the overdue risk. The higher the value, the more serious the risk impact. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a flow chart of a risk classification management method applied to a project provided in an embodiment of the present application; Figure 2 This is a schematic diagram of a module of a risk classification control device applied to a project provided in an embodiment of the present application; Figure 3 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application.

[0028] Explanation of the reference numerals: 201, acquisition module; 202, processing module; 300, electronic device; 301, processor; 302, communication bus; 303, user interface; 304, network interface; 305, memory. DETAILED DESCRIPTION

[0029] In order to enable technicians in this field to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments.

[0030] In the description of the embodiments of the present application, words such as "for example" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "for example" or "for example" is intended to present related concepts in a specific way.

[0031] In the description of the embodiments of the present application, the meaning of the term "multiple" refers to two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0032] This application provides a risk classification management method applied to a project. Figure 1 , Figure 1 1 is a flow chart of a risk classification management method applied to a project provided in an embodiment of the present application. The method is applied to a server and includes steps S101 to S104, which are as follows: Step S101: Acquire a current work project, which includes multiple project units.

[0033] Before step S101, the method also includes: obtaining historical work projects, which include multiple historical project units; extracting the historical project units to obtain top-level nodes, primary causal nodes, and secondary causal nodes corresponding to the multiple historical project units; wherein the top-level node is a project overdue event, the primary causal node is an intermediate event that causes the project overdue event, and the secondary causal node is a basic event that causes the intermediate event; constructing a first-level logical relationship between the top-level node and the primary causal node, where one top-level node corresponds to one or more primary causal nodes, and the first-level logical relationship includes a first logical AND gate and a first logical OR gate; constructing a second-level logical relationship between the primary causal node and the secondary causal node, where one primary causal node corresponds to one or more secondary causal nodes, and the second-level logical relationship includes a second logical AND gate and a second logical OR gate; constructing an accident tree corresponding to the historical project unit according to the first-level logical relationship and the second-level logical relationship, where one historical project unit corresponds to one accident tree; and storing each historical project unit and its corresponding accident tree in a preset accident tree library.

[0034] Specifically, the server obtains completed historical work items from the project management system and identifies each historical project unit contained in the historical work items. For each historical project unit, the server identifies the top-level node (e.g., project delay event) that causes the project to be overdue. The server then determines the primary causal nodes (intermediate events) under each top-level node, which directly cause the project to be overdue. The server further identifies the secondary causal nodes (basic events) under the primary causal nodes, which are the basic causes or conditions that cause the intermediate events to occur. The first-level logical relationship between the top-level node and the primary causal node is established using the "logical AND gate" and the "logical OR gate". The logical AND gate indicates that all lower-level nodes must occur to cause the upper-level node to occur. The logical OR gate indicates that any occurrence of the lower-level node can cause the upper-level node to occur. Similarly, the second-level logical relationship between the primary causal node and the secondary causal node is established using the "logical AND gate" and the "logical OR gate". For each historical project unit, an accident tree is constructed based on the first-level and second-level logical relationships, and the accident tree of each historical project unit and its related information are stored in a preset accident tree library.

[0035] In step S101, the current work project is a specific work project that is in progress and needs to be risk analyzed; the current work project is the starting point of the risk classification control method, that is, it is necessary to first determine the project or task to be analyzed, and the current work project can be a construction project. Each work project has a unique project ID as an identifier. The server also needs to obtain detailed information of each project, including project name, project description, project leader, project start date and planned completion date. A work project is usually composed of multiple project units, and each project unit undertakes part of the work of the project. Therefore, the server also needs to obtain the project unit information under each project. The server implements with the project management system through the project ID to obtain the required information. The server sends the project ID to the project management system and requests to return a list of all project units under the project. Each project unit also has a unique unit ID, as well as information such as unit name, unit description, planned start date and planned completion date.

[0036] Step S102: Obtain the work progress of each project unit.

[0037] In step S102, after obtaining the basic information of the current work project, the server needs to further obtain the actual work progress of each project unit included in the current work project. The server obtains the following work progress information of each project unit: the actual start date, that is, the actual start date of the project unit, which may be different from the planned start date; the current completion progress, that is, the percentage of the work completed by the project unit to the total workload, such as 50%; the current completion workload, that is, the absolute workload completed by the project unit. The expected completion date, that is, the expected completion date of the project unit based on the current progress.

[0038] Step S103: According to the work progress, determine the target project unit with the risk of overdue among the multiple project units.

[0039] In step S103, it is determined whether the work progress of each project unit is within the preset planned progress range; if the work progress of the target project unit is not within the preset planned progress range, it is determined that the target project unit has a risk of overdue.

[0040] Specifically, the server determines the preset planned schedule range for each project unit based on project requirements and constraints, including time nodes such as the start date, deadline, and key milestones. The server obtains the work progress data of each project unit, including information such as the tasks actually completed, the time used, and the remaining tasks. Next, the server compares the work progress of each project unit with its corresponding preset planned schedule range, and calculates the actual progress percentage completed or the remaining workload percentage. Based on the comparison results, the server determines whether the work progress of the project unit is within the preset planned schedule range. If the work progress of the project unit is not within the preset planned schedule range, that is, it exceeds or lags behind the expected progress, it is determined that the project unit is at risk of overdue; the server determines the project unit as the target project unit.

[0041] For example, for project unit U003 of project P001, the server obtained the following progress information: the planned start date is March 1, 2023; the planned completion date is April 30, 2023; the actual start date is March 5, 2023; the current completion progress is 60%; the expected completion date is May 10, 2023; it can be seen that the actual start date of this project unit is later than the planned start date, and only 60% of the workload has been completed. The expected completion date has exceeded the planned completion date, and there is a risk of overdue.

[0042] Step S104: Determine the target accident tree corresponding to the target project unit in the preset accident tree library.

[0043] In step S104, the server first accesses the preset accident tree library. The preset accident tree library contains data of historical project units and their corresponding accident trees. The server uses the unique ID of the target project unit to search in the preset accident tree library to determine the historical project unit that matches the target project unit; and determines the target accident tree corresponding to the target project unit based on the accident tree corresponding to the historical project unit.

[0044] Step S105: Analyze the target project unit according to the first-level logical relationship of the target accident tree to determine one or more target primary causal nodes that cause the target project unit to have a risk of overdue.

[0045] In step S105, based on the first-level logical relationship in the target accident tree, one or more target primary causal nodes (intermediate events) corresponding to the top-level event corresponding to the target project unit are determined.

[0046] Step S106: Analyze each target primary causal node according to the second-level logical relationship of the target accident tree to determine one or more target secondary causal nodes that cause each target primary causal node to occur.

[0047] In step S106, based on the second-level logical relationship of the target accident tree, one or more target secondary causal nodes (basic events) corresponding to the target primary causal node are determined.

[0048] Step S107: Analyze the target risk impact value of the target project unit on the overdue risk.

[0049] In step S107, the first probability value of the target secondary causal node occurring and the first number of overdue days caused by the target secondary causal node input by the user are obtained; based on the preset calculation rules, the second probability value of the target primary causal node occurring and the second number of overdue days caused by the target secondary causal node are calculated according to the second-level logical relationship, the first probability value and the first number of overdue days; based on the preset calculation rules, the target probability and target number of overdue days of the target project unit occurring overdue risk are calculated according to the first-level logical relationship, the second probability value and the second number of overdue days; the target probability and the target number of overdue days are multiplied to obtain the target risk impact value.

[0050] Specifically, the user inputs the risk information of the target secondary causal node, including the probability of the target secondary causal node occurring (first probability value) and the number of days (first overdue days) that the project is expected to be delayed if it occurs. The server uses pre-defined calculation rules, combined with the second-level logical relationship, to calculate the risk probability (second probability value) and the number of delay days (second overdue days) caused by the primary causal node (which may be a more general risk caused by multiple secondary causal nodes). The server further uses pre-defined calculation rules to evaluate the probability of the target project unit's overdue risk (target probability) and the expected number of delay days (target overdue days) based on the first-level logical relationship and the second probability value and second overdue days calculated in the previous step. Finally, the server multiplies the target probability of the target project unit by the target overdue days to obtain a quantitative value (target risk impact value), which reflects the overall impact of the overdue risk on the target project unit.

[0051] In a possible implementation, based on a preset calculation rule, the second probability value of the occurrence of the target primary causal node and the second overdue number of days caused by the target secondary causal node are calculated according to the second-level logical relationship, the first probability value and the first overdue number of days, specifically including: if the target secondary causal node is connected to the target primary causal node through a second logical AND gate, the second probability value is the product of each first probability value, and the second overdue number of days is the average of each first overdue number of days; if the target secondary causal node is connected to the target primary causal node through a second logical OR gate, the second probability value is the probability value of at least one of the first probability values ​​occurring, and the second overdue number of days is the overdue number that ranks first after the first overdue numbers are arranged in order from largest to smallest.

[0052] Specifically, the server first needs to obtain the risk data of the secondary causal nodes input by the user, including the probability of each secondary causal node occurring (first probability value) and the resulting extension days (first overdue days). If the secondary causal nodes are logically connected through an "AND gate", then the probability of the primary causal node occurring (second probability value) is the product of all first probability values. The second overdue days is the average of all first overdue days. If the secondary causal nodes are logically connected through an "OR gate", then the probability of the primary causal node occurring (second probability value) is the probability of at least one of these probability values ​​occurring. The second overdue days is the largest of all first overdue days.

[0053] For the AND gate in the second-level logical relationship, all input nodes (secondary causal nodes) must occur to cause the output node (primary causal node) to occur. Therefore, the output probability of the AND gate is the product of all its input probabilities. P(primary causal node) = ; Among them, P (primary causal node) is the probability of the primary causal node occurring, P iis the probability of the occurrence of the ith secondary causal node. For the second overdue days, the first overdue days of each target primary causal node are averaged to obtain the second overdue days caused by the target primary causal node.

[0054] For the OR gate, the occurrence of any input node can cause the output node to occur. Therefore, the output probability of the OR gate is the probability that at least one input node occurs. It is obtained by calculating the complement of the product of the probabilities that all input nodes do not occur. P(primary causal node) = ; Where P (primary causal node) is the probability of the primary causal node occurring, P i is the probability of the occurrence of the i-th secondary causal node. For the second overdue days, the first overdue days of each target primary causal node are arranged in descending order, and the first overdue day is selected as the second overdue day caused by the target primary causal node, that is, the first overdue day with the longest number of days is taken as the second overdue day.

[0055] Similarly, the same method can be used to calculate the target probability and the target number of overdue days based on the second probability value and the second number of overdue days, which will not be elaborated in this application.

[0056] For example, suppose there is an engineering project, and its corresponding top-level node has a target primary causal node - "delayed delivery by supplier", which will cause the project to be overdue. This primary causal node has two secondary causal nodes: secondary causal node 1 (supplier production delay) and secondary causal node 2 (logistics delay); suppose the user inputs the following data: the probability of secondary causal node 1 occurring is 0.1 (10% probability), and if it occurs, it will cause a 5-day overdue. The probability of secondary causal node 2 occurring is 0.2 (20% probability), and if it occurs, it will cause a 3-day overdue. These two secondary causal nodes are independent of each other, and the primary causal node "delayed delivery by supplier" will occur when any of the two secondary causal nodes occurs (logical OR gate). According to the formula of the logical OR gate, the probability of the occurrence of the primary causal node can be calculated: P(delayed delivery by supplier) = 1-(1-P(production delay)) × (1-P(logistics delay)) = 1-(1-0.1) × (1-0.2) = 0.28, so the probability of the primary causal node "delayed delivery by supplier" occurring is 28%. ; Overdue days = max (production delay overdue days, logistics delay overdue days) = 5 days Step S108: Integrate each target risk impact value to obtain the risk impact level of the current work project, where the risk impact level includes low risk, medium risk and high risk.

[0057] In step S108, according to the preset weight database, the target weight corresponding to the target project unit is obtained; according to the target weight, the weighted sum of each target risk impact value is performed to obtain a weighted sum value; if the weighted sum value is less than or equal to the preset first threshold value, the risk impact degree of the current work project is determined to be low risk; if the weighted sum value is greater than the preset first threshold value and less than the preset second threshold value, the risk impact degree of the current work project is determined to be medium risk; if the weighted sum value is greater than or equal to the preset second threshold value, the risk impact degree of the current work project is determined to be high risk.

[0058] Specifically, the server first establishes a preset weight database, which contains each target project unit and its corresponding target weight. These target weights can be determined based on expert opinions, historical data or other relevant information. According to the target project unit, the corresponding target weight is obtained from the preset weight database. For each target risk impact value, it is multiplied by the corresponding target weight, and then all weighted values ​​are added to obtain a weighted sum value. The weighted sum value is compared with the preset threshold. The risk impact degree of the current work project is determined according to the following conditions: If the weighted sum value is less than or equal to the preset first threshold, the risk impact degree of the current work project is determined to be low risk. If the weighted sum value is greater than the preset first threshold and less than the preset second threshold, the risk impact degree of the current work project is determined to be medium risk. If the weighted sum value is greater than or equal to the preset second threshold, the risk impact degree of the current work project is determined to be high risk.

[0059] Step S109: Determine a corresponding risk response strategy in a preset overdue risk response library according to the risk impact degree, and the overdue risk response library includes a correspondence between the risk impact degree and the risk response strategy.

[0060] In step S109, the server creates an overdue risk response library, which contains the correspondence between different risk impact levels and corresponding risk response strategies. The correspondence can be determined based on expert opinions, industry standards or internal regulations of the organization. According to the risk impact level (low risk, medium risk or high risk) of the current work project determined in step S108, the corresponding risk response strategy is queried in the preset overdue risk response library according to the determined risk impact level.

[0061] In a possible implementation, after determining the corresponding risk response strategy in a preset overdue risk response library according to the risk impact level, the method further includes: displaying prompt information, the prompt information being used to prompt the user to implement the risk response strategy; and monitoring the work progress of the target project unit in real time.

[0062] Specifically, the server displays prompt information to the user according to the determined risk response strategy to prompt the user to implement corresponding risk response measures. The prompt information includes risk description, prompted countermeasures, relevant precautions, etc., to help the user understand and implement the risk response strategy.

[0063] Reference Figure 2 The present application also provides a risk classification control device for projects, the device is a server, the server includes an acquisition module 201 and a processing module 202; the acquisition module 201 is used to acquire the current work project, the current work project includes multiple project units; the acquisition module 201 is also used to acquire the work progress of each of the project units; the processing module 202 is used to determine the target project unit with overdue risk among the multiple project units according to the work progress; the processing module 202 is also used to determine the target accident tree corresponding to the target project unit in the preset accident tree library; the processing module 202 is also used to, according to the first-level logical relationship of the target accident tree, The target project unit is analyzed to determine one or more target primary causal nodes that cause the overdue risk of the target project unit; the processing module 202 is also used to analyze each of the target primary causal nodes according to the second-level logical relationship of the target accident tree to determine one or more target secondary causal nodes that cause each of the target primary causal nodes to occur; the processing module 202 is also used to analyze the target risk impact value of the target project unit on the overdue risk; the processing module 202 is also used to integrate each of the target risk impact values ​​to obtain the risk impact degree of the current work project, and the risk impact degree includes low risk, medium risk and high risk. The processing module 202 is also used to determine the corresponding risk response strategy in the preset overdue risk response library according to the risk impact degree, and the overdue risk response library includes the corresponding relationship between the risk impact degree and the risk response strategy.

[0064] In a possible implementation, before the acquisition module 201 acquires the current work project, the method further includes: the acquisition module 201 acquires a historical work project, and the historical work project includes a plurality of historical project units; the processing module 202 extracts the historical project units to obtain a plurality of top-level nodes, primary causal nodes, and secondary causal nodes corresponding to the historical project units; wherein the top-level node is a project overdue event, the primary causal node is an intermediate event that causes the project overdue event to occur, and the secondary causal node is a basic event that causes the intermediate event to occur; the processing module 202 constructs the first-level logical relationship between the top-level node and the primary causal node, and a top-level node The point corresponds to one or more of the primary causal nodes, and the first layer of logical relationship includes a first logical AND gate and a first logical OR gate; the processing module 202 constructs the second layer of logical relationship between the primary causal node and the secondary causal node, one of the primary causal nodes corresponds to one or more of the secondary causal nodes, and the second layer of logical relationship includes a second logical AND gate and a second logical OR gate; the processing module 202 constructs the accident tree corresponding to the historical project unit according to the first layer of logical relationship and the second layer of logical relationship, and one of the historical project units corresponds to one of the accident trees; the processing module 202 stores each of the historical project units and the corresponding accident tree in the preset accident tree library.

[0065] In a possible implementation, the processing module 202 analyzes the target risk impact value of the target project unit on the overdue risk, specifically including: the acquisition module 201 acquires the first probability value of the occurrence of the target secondary causal node and the first number of overdue days caused by the target secondary causal node input by the user; the processing module 202 calculates the second probability value of the occurrence of the target primary causal node and the second number of overdue days caused by the target secondary causal node based on the preset calculation rules according to the second-level logical relationship, the first probability value and the first number of overdue days; the processing module 202 calculates the target probability and target number of overdue days of the occurrence of the overdue risk in the target project unit based on the preset calculation rules according to the first-level logical relationship, the second probability value and the second number of overdue days; the processing module 202 multiplies the target probability and the target number of overdue days to obtain the target risk impact value.

[0066] In a possible implementation, the processing module 202 calculates the second probability value of the occurrence of the target primary causal node and the second overdue days caused by the target secondary causal node based on a preset calculation rule according to the second-layer logical relationship, the first probability value and the first overdue days, specifically including: if the target secondary causal node is connected to the target primary causal node through the second logical AND gate, the processing module 202 determines that the second probability value is the product of each of the first probability values, and the second overdue days is the average of each of the first overdue days; if the target secondary causal node is connected to the target primary causal node through the second logical OR gate, the processing module 202 determines that the second probability value is the probability value of at least one of the first probability values ​​occurring, and the second overdue days is the overdue days that ranks first after the first overdue days are arranged in order from large to small.

[0067] In a possible implementation, the processing module 202 determines the target project unit that has a risk of overdue among the multiple project units based on the work progress, specifically including: the processing module 202 monitors the work progress of each of the project units; the processing module 202 determines whether the work progress of each of the project units is within the preset planned progress range; if the work progress of the target project unit is not within the preset planned progress range, the processing module 202 determines that the target project unit has a risk of overdue.

[0068] In one possible implementation, the processing module 202 integrates each of the target risk impact values ​​to obtain the risk impact level of the current work project, specifically including: the processing module 202 obtains the target weight corresponding to the target project unit according to a preset weight database; the processing module 202 performs weighted summation on each of the target risk impact values ​​according to the target weight to obtain a weighted sum value; if the weighted sum value is less than or equal to a preset first threshold, the processing module 202 determines that the risk impact level of the current work project is the low risk; if the weighted sum value is greater than the preset first threshold and less than the preset second threshold, the processing module 202 determines that the risk impact level of the current work project is the medium risk; if the weighted sum value is greater than or equal to the preset second threshold, the processing module 202 determines that the risk impact level of the current work project is the high risk.

[0069] In a possible implementation, after the processing module 202 determines the corresponding risk response strategy in a preset overdue risk response library according to the risk impact level, the method further includes: the processing module 202 displays prompt information, and the prompt information is used to prompt the user of the risk response strategy that can be adopted; the processing module 202 monitors the work progress of the target project unit in real time.

[0070] It should be noted that: when the device provided in the above embodiment realizes its function, only the division of the above functional modules is used as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0071] The present application also provides an electronic device. Figure 3 , Figure 3 The electronic device 300 may include: at least one processor 301 , at least one network interface 304 , a user interface 303 , a memory 305 , and at least one communication bus 302 .

[0072] The communication bus 302 is used to realize the connection and communication between these components.

[0073] The user interface 303 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 303 may also include a standard wired interface and a wireless interface.

[0074] The network interface 304 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0075] Among them, the processor 301 may include one or more processing cores. The processor 301 uses various interfaces and lines to connect various parts in the entire server, and executes various functions of the server and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 305, and calling data stored in the memory 305. Optionally, the processor 301 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 301 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 301, and it can be implemented separately through a chip.

[0076] Among them, the memory 305 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 305 includes a non-transitory computer-readable storage medium. The memory 305 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 305 may optionally also be at least one storage device located away from the aforementioned processor 301. Refer to Figure 3 , the memory 305 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program for a risk classification management method applied to a project.

[0077] exist Figure 3In the electronic device 300 shown, the user interface 303 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 301 can be used to call the application program stored in the memory 305 for a risk classification management method applied to the project. When executed by one or more processors 301, the electronic device 300 executes one or more of the methods described in the above embodiments. It should be noted that for the aforementioned method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for the present application.

[0078] The present application also provides a computer-readable storage medium, which stores instructions. When executed by one or more processors 301, the electronic device 300 executes one or more of the methods described in the above embodiments.

[0079] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0080] In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0081] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0082] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: various media that can store program codes, such as USB flash drives, mobile hard drives, magnetic disks or optical disks.

[0084] The above is only an exemplary embodiment of the present disclosure and cannot be used to limit the scope of the present disclosure. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the disclosure of the specification and the truth of practice, those skilled in the art will easily think of other embodiments of the present disclosure.

[0085] This application is intended to cover any variation, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the art not described in the present disclosure. The description and examples are to be regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.

Claims

1. A risk classification management and control method applied to a project, characterized in that: The method comprises: Acquire a current work project, where the current work project includes multiple project units; Obtaining the work progress of each of the project units; According to the work progress, determine a target project unit among the plurality of project units that has a risk of being overdue; Determine a target accident tree corresponding to the target project unit in a preset accident tree library; According to the first-level logical relationship of the target accident tree, the target project unit is analyzed to determine one or more target primary causal nodes that cause the target project unit to have the risk of overdue; According to the second-level logical relationship of the target accident tree, each of the target primary causal nodes is analyzed to determine one or more target secondary causal nodes that cause each of the target primary causal nodes to occur; Analyze the target risk impact value of the target project unit on the overdue risk; Integrate each of the target risk impact values ​​to obtain the risk impact level of the current work project, where the risk impact level includes low risk, medium risk and high risk; A corresponding risk response strategy is determined in a preset overdue risk response library according to the risk impact degree, and the overdue risk response library includes a correspondence between the risk impact degree and the risk response strategy.

2. The method according to claim 1, characterized in that Before obtaining the current work item, the method further includes: Acquire a historical work project, wherein the historical work project includes a plurality of historical project units; Extracting the historical project units to obtain a plurality of top-level nodes, primary causal nodes, and secondary causal nodes corresponding to the historical project units; wherein the top-level node is a project overdue event, the primary causal node is an intermediate event causing the project overdue event, and the secondary causal node is a basic event causing the intermediate event; Constructing the first-level logical relationship between the top-level node and the primary causal node, wherein one top-level node corresponds to one or more primary causal nodes, and the first-level logical relationship includes a first logical AND gate and a first logical OR gate; Constructing the second-level logical relationship between the primary causal node and the secondary causal node, one primary causal node corresponds to one or more secondary causal nodes, and the second-level logical relationship includes a second logical AND gate and a second logical OR gate; According to the first-level logical relationship and the second-level logical relationship, construct an accident tree corresponding to the historical project unit, where one historical project unit corresponds to one accident tree; Each of the historical project units and its corresponding accident tree are stored in the preset accident tree library.

3. The method according to claim 2, characterized in that The analyzing the target risk impact value of the target project unit on the overdue risk specifically includes: Obtaining a first probability value of the target secondary causal node occurring and a first number of overdue days caused by the target secondary causal node input by a user; Based on a preset calculation rule, calculate a second probability value of the target primary causal node occurring and a second number of overdue days caused by the target secondary causal node according to the second-level logical relationship, the first probability value, and the first number of overdue days; Based on the preset calculation rule, the target probability and target number of overdue days of the target project unit occurring the risk of overdue are calculated according to the first-level logical relationship, the second probability value, and the second number of overdue days; The target probability is multiplied by the target overdue days to obtain the target risk impact value.

4. The method according to claim 3, characterized in that The calculating, based on the preset calculation rule, the second probability value of the target primary causal node occurring and the second overdue days caused by the target secondary causal node according to the second-layer logical relationship, the first probability value, and the first overdue days specifically includes: If the target secondary causal node is connected to the target primary causal node through the second logic AND gate, the second probability value is determined to be the product of each of the first probability values, and the second overdue days is the average of each of the first overdue days; If the target secondary causal node is connected to the target primary causal node through the second logical OR gate, the second probability value is determined to be the probability value of at least one of the first probability values ​​occurring, and the second overdue number of days is the overdue number that ranks first after the first overdue numbers are arranged in order from large to small.

5. The method according to claim 1, characterized in that Determining, according to the work progress, a target project unit among the plurality of project units that has a risk of being overdue specifically includes: Monitor the progress of work on each of the said project units; Determine whether the work progress of each of the project units is within the preset planned progress range; If the work progress of the target project unit is not within the preset planned progress range, it is determined that the target project unit is at risk of being overdue.

6. The method according to claim 1, characterized in that The integration of the target risk impact values ​​to obtain the risk impact degree of the current work project specifically includes: According to a preset weight database, obtaining the target weight corresponding to the target project unit; According to the target weight, weighted summation is performed on each target risk impact value to obtain a weighted summation value; If the weighted sum value is less than or equal to the preset first threshold, determining that the risk impact level of the current work item is the low risk; If the weighted sum value is greater than the preset first threshold value and less than the preset second threshold value, it is determined that the risk impact level of the current work item is the medium risk; If the weighted sum value is greater than or equal to the preset second threshold, it is determined that the risk impact level of the current work item is the high risk.

7. The method according to claim 1, characterized in that After determining the corresponding risk response strategy in a preset overdue risk response library according to the risk impact degree, the method further includes: Displaying prompt information, wherein the prompt information is used to prompt the user of the risk response strategy that can be adopted; The work progress of the target project unit is monitored in real time.

8. A risk classification control device applied to a project, the device comprising: An acquisition module (201) and a processing module (202); The acquisition module (201) is used to acquire a current work project, wherein the current work project includes a plurality of project units; The acquisition module (201) is also used to acquire the work progress of each of the project units; The processing module (202) is used to determine, according to the work progress, a target project unit with a risk of overdue among the plurality of project units; The processing module (202) is further used to determine the target accident tree corresponding to the target project unit in a preset accident tree library; The processing module (202) is further configured to analyze the target project unit according to the first-level logical relationship of the target accident tree, and determine one or more target primary causal nodes that cause the target project unit to have the risk of overdue; The processing module (202) is further configured to analyze each of the target primary causal nodes according to the second-level logical relationship of the target accident tree, and determine one or more target secondary causal nodes that cause each of the target primary causal nodes to occur; The processing module (202) is further used to analyze the target risk impact value of the target project unit on the overdue risk; The processing module (202) is further used to integrate each of the target risk impact values ​​to obtain the risk impact level of the current work project, where the risk impact level includes low risk, medium risk and high risk; The processing module (202) is further used to determine a corresponding risk response strategy in a preset overdue risk response library according to the risk impact degree, and the overdue risk response library includes a correspondence between the risk impact degree and the risk response strategy.

9. An electronic device, characterized in that: The electronic device (300) comprises a processor (301), a memory (305), a user interface (303) and a network interface (304), wherein the memory (305) is used to store instructions, the user interface (303) and the network interface (304) are used to communicate with other devices, and the processor (301) is used to execute the instructions stored in the memory (305) so that the electronic device (300) executes the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 7 is executed.

Images