Project work priority adjustment method and system, medium and product

Abstract

The invention discloses a project work priority adjusting method and system, a medium and a product. In the method, a system server firstly determines the risk category of a work item, and then realizes multi-dimensional assessment of the risk based on a possibility measurement standard and an influence degree measurement standard. The system server converts the possibility measurement result and the influence degree measurement result into risk levels through quantitative calculation, matches a risk list in a risk case library in combination with risk categories, ensures the accuracy of risk identification, and generates a risk coping plan including an implementation scheme and a time node according to the risk list. Therefore, the initial execution priority is determined, and clear sequence guidance is provided for project execution. And finally, the system server dynamically updates the execution priority by acquiring the resource consumption and progress data of the work items in real time. The method responds to the item execution state change in real time, ensures that the resources are always inclined to the current most critical work item, and improves the item delivery efficiency and success rate.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of product research and development, and particularly relates to a project work priority adjustment method, system, medium and product. BACKGROUND

[0002] With the continuous development of modern enterprise project management, project work priority management has become a key factor to improve the efficiency and success rate of project execution. In a complex and changeable project environment, it is particularly important to reasonably allocate resources, control project progress and prevent project risks. Project managers need to balance the execution order of multiple work items under limited resource conditions to ensure the achievement of the overall project goal.

[0003] In related technologies, a common project priority management method is to determine the project priority through multi-factor analysis. This method first determines multiple factors that affect the priority of the project, and assigns a weight coefficient to each factor. Then, a fixed constant is allocated according to the actual situation of each project as the priority number of each influencing factor. Then, multiply the weight coefficient of each factor of each project by the corresponding priority number to get the final priority number of each factor.

[0004] However, in the actual execution process of the project, the status of each work item is dynamically changing, for example, the actual resource consumption of a certain work item exceeds the initial budget, or the progress lags due to unforeseen technical difficulties. Since the weight coefficient and priority number of the above-mentioned prior art method are set once and remain unchanged throughout the project cycle, this leads to a fixed and pre-ordered priority. When the execution status within the project changes, this static priority cannot reflect the current most attention and resource tilt link in real time, which may cause the project manager to not respond to new key problems in time, thereby affecting the delivery efficiency and final success rate of the entire project. SUMMARY

[0005] The present application provides a project work priority adjustment method, system, medium and product, which is used to alleviate the technical problem that the prior art cannot respond to project dynamic changes in time, and improves the delivery efficiency and success rate of the project.

[0006] In a first aspect, the application provides a project work priority adjustment method, comprising: obtaining a plurality of work item information in a target project, and determining a risk category of each work item according to the work item information, the work item information including work item type, expected completion time, and required resources; evaluating risk occurrence possibility of the each work item based on a possibility measurement standard, generating a possibility measurement result, and evaluating risk impact degree of the each work item based on an impact degree measurement standard, generating an impact degree measurement result, the possibility measurement standard being used to measure risk occurrence probability, and the impact degree measurement standard being used to evaluate risk consequence severity from performance, progress, and resource aspects; performing quantitative calculation on the possibility measurement result and the impact degree measurement result of the each work item to obtain a risk level of the each work item; matching in a risk case library according to the risk category and the risk level of the each work item to obtain a risk list of the each work item in the target project; generating a risk response plan based on the risk list, the risk response plan including an implementation scheme, a planned start time, and a planned completion time, and generating an execution priority of the each work item in the target project according to the risk response plan; obtaining execution progress of the each work item in real time to obtain actual resource consumption and progress data of the each work item; and updating the execution priority of the each work item in the target project according to the resource consumption and progress data.

[0007] By adopting the above technical solution, the system server first obtains the work item type, expected completion time, and required resources of each work item in the target project to determine the risk category of each work item. Then, the system server evaluates risk occurrence possibility (probability) based on the possibility measurement standard, and evaluates impact degree based on the impact degree measurement standard, to realize multi-dimensional evaluation of risks. The system server further converts the possibility measurement result and the impact degree measurement result into a risk level through quantification, matches a risk list in the risk case library in combination with the risk category, to ensure accuracy of risk identification. The system server generates a risk response plan including an implementation scheme and time nodes according to the risk list, and then determines an initial execution priority, to provide clear order guidance for project execution. Finally, the system server dynamically updates the execution priority by obtaining resource consumption and progress data of the work item in real time. The method effectively avoids the problem of fixed priority in the prior art, can respond to project execution state changes in real time, ensures that resources are always inclined to the most critical work item, and finally improves project delivery efficiency and success rate.

[0008] In some embodiments of the first aspect, in some embodiments, the risk occurrence possibility of each work item is evaluated based on a possibility metric, a possibility metric result is generated, and the risk impact degree of each work item is evaluated based on an impact degree metric, an impact degree metric result is generated, specifically comprising: obtaining a historical risk occurrence frequency corresponding to the risk category of each work item, and taking the historical risk occurrence frequency as a possibility reference value; calculating a time pressure coefficient based on the expected completion time, and calculating a resource pressure coefficient based on the required resources, the time pressure coefficient being a ratio of a standard completion time to an expected completion time of the work item, and the resource pressure coefficient being a ratio of required resources to available resources; performing weighted calculation on the possibility reference value, the time pressure coefficient and the resource pressure coefficient to obtain the possibility metric result; and calculating an impact degree score of each work item in terms of performance, progress and resources respectively, and taking a weighted average value of the impact degree score as the impact degree metric result, the impact degree score being a severity score of negative impact caused by the performance, the progress and the resources.

[0009] By adopting the above technical solution, the system server takes the historical risk occurrence frequency as the possibility reference value, ensuring the historical basis of possibility evaluation, and further introduces the time pressure coefficient and the resource pressure coefficient to consider the influence of the current time and resource status of the work item on the risk occurrence possibility, so that the possibility metric result is more in line with the actual situation. In the impact degree evaluation, the system server calculates scores from multiple aspects of performance, progress and resources and takes a weighted average value, comprehensively measuring the severity of the risk consequences. This method makes the evaluation of possibility and impact degree more accurate and comprehensive, and provides a reliable basis for subsequent risk level determination.

[0010] In some embodiments of the first aspect, before the step of obtaining the historical risk occurrence frequency corresponding to the risk category of each work item and taking the historical risk occurrence frequency as the possibility reference value, specifically comprising: retrieving the risk category of each work item in the historical project database, and determining whether the risk category of the work item has historical data; if the risk category of the work item has no historical data, calculating the possibility metric result of the work item based on the technical novelty index and the technical complexity index obtained by quantifying the technical attributes of the work item; identifying the sub-work items of the work item, and calculating the impact degree metric result of the work item according to the criticality, dependency relationship and number of the sub-work items.

[0011] By adopting the technical solutions, when the risk category of the work item has no historical data, the system server calculates the possibility measurement result based on the technical novelty and complexity indexes, solving the problem of possibility evaluation when there is no historical data. The system server calculates the influence degree measurement result according to the criticality, dependency relationship and quantity of the sub-work items by identifying the sub-work items, ensuring the feasibility of influence degree evaluation in the case of lacking historical data. These features complement each other, making it possible to effectively evaluate the risk of the work item whether there is historical data or not, expanding the applicable range of the method and ensuring the comprehensiveness of risk evaluation.

[0012] In combination with some embodiments of the first aspect, in some embodiments, the possibility measurement result and the influence degree measurement result of each work item are quantitatively calculated to obtain the risk level of each work item, specifically including: representing the possibility measurement result and the influence degree measurement result of each work item as a possibility matrix and an influence degree matrix respectively, each row of the possibility matrix corresponding to a work item and the column representing the possibility measurement result of the work item, each row of the influence degree matrix corresponding to a work item and the column representing the influence degree measurement result of the work item; normalizing the values of each work item in the possibility matrix and the influence degree matrix to unify the dimensions of different units; performing weighted operation on the normalized possibility matrix and the influence degree matrix to generate a weighted possibility matrix and a weighted influence degree matrix; multiplying the weighted possibility matrix and the weighted influence degree matrix item by item to calculate the risk comprehensive score of each work item; generating risk level division intervals according to the numerical distribution of the risk comprehensive score of each work item, and mapping the risk comprehensive score of each work item to the corresponding risk level.

[0013] By adopting the technical solutions, the system server represents the possibility measurement result and the influence degree measurement result as a matrix, and then normalizes the matrix values to eliminate the influence of different dimensional units, making them comparable. The system server obtains the risk comprehensive score by weighted operation and item-by-item multiplication, and then divides the risk level according to the score distribution. These technical features gradually process the calculation process of the risk level, making it more accurately reflect the risk status of the work item, and providing an accurate basis for the subsequent matching of the risk list.

[0014] In some embodiments of the first aspect, the updating of the risk case library specifically comprises: after the risk list of each work item in the target project is generated, updating the risk information of each work item, including the risk category and the risk level, to the risk case library; during the implementation of the risk response plan, when a risk item in the risk list is confirmed to be closed or acceptable, updating the response plan of the risk item to the risk case, the confirmation of being closed or acceptable means that the risk item is effectively solved or the risk is reduced to a safe range; and establishing an index for retrieval matching for each risk item in the risk list.

[0015] By adopting the above technical solution, the system server updates the risk information of the risk case library after generating the risk list, enriches the basic data of the case library, and updates the response plan of the solved or acceptable risk item to the case library, providing a reference for the response of similar risks in the future. The system server establishes a retrieval index for each risk item, improving the retrieval efficiency of the case library. These features work together to continuously improve the risk case library, so that it can better support the risk assessment and response of new projects, and improve the efficiency and accuracy of risk handling.

[0016] In some embodiments of the first aspect, according to the resource consumption and progress data, the execution priority of each work item in the target project is updated, specifically comprising: according to the resource consumption and progress data of each work item, a resource consumption change rate is calculated, and a progress change rate is calculated, the resource consumption is the difference between the current detected remaining resources and the remaining resources at the last detection, and the progress data is the difference between the current actual completion progress and the completion progress at the last detection; when the resource consumption change rate exceeds a preset consumption change threshold and the progress change rate exceeds a preset progress change threshold, new work item information is generated according to the resource consumption and the progress data; and according to the new work item information, the execution priority of each work item in the target project is adjusted.

[0017] By adopting the above technical solution, the system server calculates the resource consumption change rate and the progress change rate, which can timely find the progress and breakthrough in the execution of the work item. When the resource consumption change rate and the progress change rate both exceed the preset threshold, new work item information is generated and the priority is adjusted, ensuring that the priority can be updated in real time according to the actual execution, making the priority adjustment more timely and accurate, and enabling the system to quickly respond to the real-time situation in the project, ensuring that resources are inclined to the most needed work items, and improving the execution efficiency of the project.

[0018] In some embodiments of the first aspect, before the step of obtaining the actual resource consumption and progress data of each work item by acquiring the execution progress of each work item in real time, the method further comprises: constructing a priority conflict detection matrix based on each work item and the corresponding resource requirement, the rows and columns of the priority conflict detection matrix being the work items, and the elements in the matrix representing the resource requirement overlap degree between the two work items corresponding to the elements; determining whether the execution time periods of the two work items corresponding to each element in the priority conflict detection matrix overlap; if they overlap, calculating the resource requirement of the two work items in the overlapping execution time period; when the resource requirement exceeds the total amount of available resources, arranging the work item with a lower priority to be executed after the execution of the work item with a higher priority is completed, and updating the work item information to obtain an adjusted execution priority; if they do not overlap, determining that there is no resource competition between the two work items, and the execution priority is not changed.

[0019] By using the above technical solution, the system server constructs a priority conflict detection matrix to clearly present the resource requirement overlap between work items, and then determines whether the execution time periods overlap, and determines whether there is resource competition by comparing the resource requirement with the total amount of available resources. For the case of competition, the execution order of the work items is adjusted to avoid resource conflicts, effectively solving the resource competition problem between work items, ensuring the reasonable allocation of project resources, and improving the resource utilization rate and the smoothness of project execution.

[0020] In the second aspect, the present application provides a project work priority adjustment system, comprising one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code comprising computer instructions, and the one or more processors invoke the computer instructions to enable the project work priority adjustment system to perform the method described in the first aspect and any possible implementation manner of the first aspect.

[0021] In the third aspect, the present application provides a computer readable storage medium comprising instructions, which, when executed on a project work priority adjustment system, cause the project work priority adjustment system to perform the method described in the first aspect and any possible implementation manner of the first aspect.

[0022] In the fourth aspect, the present application provides a computer program product, which, when executed on a project work priority adjustment system, causes the project work priority adjustment system to perform the method described in the first aspect and any possible implementation manner of the first aspect.

[0023] The one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: 1、Due to the adoption of the technical means of determining the risk category based on the work item information first, then assessing the risk and quantitatively calculating the risk level from the possibility and impact degree, matching the risk list to generate the response plan to determine the initial priority, and finally dynamically updating the priority according to the real-time resource consumption and progress data, the technical problems of priority fixation and inability to respond to project dynamic changes in the prior art are effectively solved, and the technical effects of accurately tilting resources to the current key work item, improving project delivery efficiency and success rate are realized.

[0024] 2、Due to the adoption of the technical means of first searching the historical project database to determine whether there is historical data for the risk category, and when there is no historical data, calculating the possibility measurement result based on the technical novelty and complexity index, and at the same time calculating the impact degree measurement result through the key degree, dependency relationship and quantity of sub-work items, the technical problems of being unable to carry out effective risk assessment when there is no historical data for the risk category of the work item in the prior art are effectively solved, and the technical effects of breaking the dependence on historical data, expanding the application scope of the method, and ensuring that all work items can be effectively risk assessed are realized.

[0025] 3、Due to the adoption of the technical means of constructing a priority conflict detection matrix to present the resource demand overlap degree of the work item, determining whether the execution time period overlaps and calculating the resource demand amount of the overlapping period, and adjusting the execution order of the low-priority work item after comparing with the total amount of available resources, the technical problems of being unable to reasonably allocate resources when there is resource competition between work items in the prior art, which easily leads to project stagnation, are effectively solved, and the technical effects of resolving resource conflicts, ensuring orderly and efficient use of resources, and improving the smoothness of project execution are realized. BRIEF DESCRIPTION OF DRAWINGS

[0026] Figure 1 is a flowchart of the project work priority adjustment method in the embodiments of the present application; Figure 2 is another flowchart of the project work priority adjustment method in the embodiments of the present application; Figure 3 is a hardware structure diagram of the project work priority adjustment system in the embodiments of the present application. DETAILED DESCRIPTION

[0027] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be limiting to the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an,” and “the” are intended to include both singular and plural forms, unless the context clearly indicates otherwise. It will be further understood that the term “and / or” used in the present application means any or all possible combinations of one or more listed items.

[0028] Hereinafter, the terms "first", "second" are only used for the purpose of description, and cannot be understood as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise specified.

[0029] For ease of understanding, the method provided by the present embodiment is described in the flow. Please refer to Figure 1 , a flowchart of the project work priority adjustment method in the present embodiment.

[0030] 101, obtain multiple work item information in the target project, and determine the risk category of each work item according to the work item information, the work item information including work item type, expected completion time, required resources.

[0031] The target project refers to a specific project that needs to be adjusted in priority in the system server (the system server refers to the server of the project work priority adjustment system, which is the core hardware carrier for the system server to realize data collection, analysis calculation and control instruction generation) at present, and the specific project includes multiple sub-projects; the work item information refers to the data set of the key attributes of a single work task in the target project; the work item type refers to the classification identification of the business category or execution nature of the work item, which is used to represent the core task attribute of the work item, for example, core component machining class work item, assembly precision calibration class work item, system joint debugging test class work item; the expected completion time refers to the planned completion date or time node of each work item; the required resources refer to various elements required to complete a single work item, which refer to the conditions that must be equipped to ensure the smooth progress of the work item, including but not limited to human resources, material resources, financial resources; the risk category refers to the classification of the risks that the work item may face according to the work item information by the system server, for example, component machining size out-of-tolerance risk, assembly process connection interruption risk, test data insufficient repeatability risk.

[0032] Specifically, the system server first obtains all the decomposed work item information under the target project from the database, checks the data integrity during the obtaining process, then performs structured analysis on the work item information, and establishes a data index in the format of "work item ID-work item type-expected completion time-required resources". Then, the system server calls a preset risk category library, which presets risk classification logic for fields such as equipment development and product research and development, which are multidisciplinary collaboration and high resource input. For example, the work item type is a core component machining type, and the required resources include imported hard alloy cutters, which correspond to the cutter supply delay type risk. The work item type is a system debugging and testing type, and the expected completion time is less than 15 days and the test items are more than 300, which correspond to the test resource saturation type risk. Finally, the system server determines the risk category of each work item by matching, and provides a classification basis for subsequent risk assessment.

[0033] 102. evaluate the risk occurrence possibility of each work item based on the possibility measurement standard, generate a possibility measurement result, and evaluate the risk impact degree of each work item based on the impact degree measurement standard, generate an impact degree measurement result, the possibility measurement standard is used to measure the risk occurrence probability, and the impact degree measurement standard is used to evaluate the risk consequence severity from the performance, progress and resource aspects.

[0034] The possibility measurement standard refers to a preset evaluation index system used by the system server to measure the risk occurrence probability of each work item in equipment manufacturing engineering, which is used to represent the quantitative basis of risk occurrence probability; the risk occurrence possibility refers to the probability of occurrence of each work item corresponding risk in actual execution process evaluated by the system server based on the possibility measurement standard; the possibility measurement result refers to the specific level identifier generated after the system server quantitatively evaluates the risk occurrence possibility, for example, high possibility (level division: high, medium, low); the impact degree measurement standard refers to a preset evaluation index system used by the system server to evaluate the risk consequence severity of each work item from three dimensions of performance, progress and resource, which is used to represent the multi-dimensional quantitative basis of risk consequence severity, wherein the performance dimension is the influence amplitude of the function implementation and quality standard of the work item achievement after the risk occurs, the progress dimension is the estimated number of days of delay of the work item caused by the risk, and the resource dimension is the resource cost (such as the cost of re-purchasing raw materials) that needs to be additionally invested after the risk occurs; the risk impact degree refers to the severity of the consequences caused to the project as a whole if the risk corresponding to each work item occurs, which is evaluated by the system server based on the impact degree measurement standard, and is used to represent the hazard attribute of the risk consequence; the impact degree measurement result refers to the level identifier generated after the system server performs multi-dimensional quantitative evaluation on the risk impact degree, for example, medium impact degree (level division: high, medium, low).

[0035] Specifically, the system server first analyzes and evaluates each work item according to a possibility metric, which is the frequency of risk occurrence of the work item in historical projects, and generates a possibility metric result of each work item based on the risk occurrence possibility, for example, using high, medium and low to represent the size of the risk occurrence possibility. At the same time, the system server evaluates each work item from the aspects of performance, progress and resources based on an impact degree metric. In the aspect of performance, the impact degree of the functional implementation and quality standard of the work item results after the risk occurrence is evaluated; in the aspect of progress, the delay degree of the work item completion time and the entire project progress after the risk occurrence is evaluated; in the aspect of resources, the impact degree of the additional consumption or resource shortage of resources after the risk occurrence is evaluated. After the comprehensive evaluation of the three aspects, the system server generates an impact degree metric result of each work item, which can also be represented by high, medium and low.

[0036] 103. Quantitatively calculating the possibility metric result and the impact degree metric result of each work item to obtain a risk level of each work item.

[0037] Quantitative calculation refers to the process of converting the possibility metric result and the impact degree metric result into specific numerical values and performing mathematical operations; the risk level refers to the level of the risk degree of the work item divided according to the result of quantitative calculation, for example, very high, high, medium, low and very low.

[0038] Specifically, the system server first arranges the possibility metric result and the impact degree metric result of each work item into corresponding matrices respectively, the rows of the matrices correspond to a single work item and the columns correspond to the metric results of each item. Then, the system server processes the numerical values of each work item in the two matrices to unify the dimension, and then weights the processed matrices respectively, and then multiplies the numerical values of the corresponding work items in the weighted two matrices to obtain a risk comprehensive score of each work item. Finally, the system server divides the risk level interval according to the numerical distribution of the risk comprehensive scores of all work items, and corresponds the risk comprehensive score of each work item to a specific interval, and further determines the risk level of each work item.

[0039] The system server divides the risk level interval according to the numerical distribution of the comprehensive risk score of all work items, and the process is as follows: based on the statistical score data, the system server calculates the minimum value and the maximum value of the score, and obtains the numerical range of the score by subtracting the minimum value from the maximum value, and then determines the number of required risk levels (for example, extremely low, low, medium, high, and extremely high) in combination with the actual needs of project management (such as risk control precision); the system server divides the calculated score value range by the determined number of risk levels to obtain the initial interval interval, and then takes the calculated minimum value of the score as the starting point to derive the interval threshold of each risk level according to the determined interval interval, and clearly defines the risk level interval corresponding to each risk level.

[0040] 104. According to the risk category and risk level of each work item, matching is performed in the risk case library to obtain a risk list of each work item in the target project.

[0041] The risk case library refers to a database that stores risk cases and related information faced by various work items in historical projects; the risk list is a list file that clearly defines the risk category and risk level of each work item in the target project.

[0042] Specifically, the system server first retrieves the determined risk category and risk level of each work item, and then uses these two attributes as matching keywords to search in the risk case library. During the search process, the system server filters out cases in historical projects that are completely identical or highly similar to the current work item risk category and risk level (for example, with a similarity of 90%), and verifies the accuracy of the division of the risk category and risk level of the current work item by comparing the risk description, occurrence scenario, and other information in the cases. After verification, the system server records the risk category and risk level of each work item in a structured form and generates a corresponding risk list, for example, work item A, risk category: progress risk category, risk level: medium, which provides clear risk attribute basis for subsequent generation of risk response plans.

[0043] 105. Based on the risk list, a risk response plan is generated, which includes an implementation scheme, a planned start time, and a planned completion time, and according to the risk response plan, an execution priority of each work item in the target project is generated.

[0044] The risk response plan refers to a series of planned arrangements made to respond to the risks that each work item in the risk list may face; the implementation scheme refers to specific action steps and methods taken to handle risks; the planned start time refers to the time when the plan starts to take risk response measures; the planned completion time refers to the planned completion time after the work item takes measures; the execution priority refers to the sequence arrangement of the work item in the project execution process.

[0045] Specifically, the system server will formulate a detailed risk response plan based on the risk category and risk level of each risk in the risk list, combined with the actual situation. This plan will clearly define the implementation scheme for each work item risk, the planned initiation time of risk response measures, and the planned completion time after the measures are taken. Then, the system server will prioritize each work item in the target project based on factors such as the urgency and importance of the risk response plan, generating an execution priority. For example, work items with significant risk impact and requiring immediate attention will be assigned a higher execution priority, and resources will be allocated to them more efficiently.

[0046] 106. Real-time acquisition of the execution progress of each work item, obtaining the actual resource consumption and progress data of each work item.

[0047] Execution progress refers to the completion status of a work item during execution; actual resource consumption refers to the quantity of various resources actually used by a work item during execution; schedule data refers to information such as the actual degree of completion of a work item and the time spent.

[0048] Specifically, the system server will continuously collect the execution progress information of each work item. After processing, this information will form the actual resource consumption data of each work item, such as the actual number of manpower invested, the amount of materials used, and the amount of funds spent, as well as progress data, such as the actual amount of work completed, the time spent, and whether it is progressing as planned, providing a basis for subsequent updates to the execution priority.

[0049] 107. Update the execution priority of each work item in the target project based on resource consumption and progress data.

[0050] Execution priority refers to the order in which each work item in the target project is executed, as set by the system server. It needs to be dynamically adjusted based on new information for each work item.

[0051] Specifically, the system server first calculates the resource consumption change rate and progress change rate based on the resource consumption and progress data of each work item. The resource consumption is the difference between the current resource usage and the remaining resources at the time of the last detection, and the progress data is the difference between the current actual progress and the progress at the time of the last detection. When both the resource consumption change rate and the progress change rate exceed the preset threshold, the system server will generate new work item information based on the resource consumption and progress data, and then adjust the execution priority of each work item in the target project based on the new work item information.

[0052] The project work priority adjustment method in the embodiment of the present application is adopted, the system server first acquires the type, expected completion time, required resources and the like of the work item in the target project, combines the preset risk category library to complete risk classification of each work item, builds a basic framework for subsequent risk assessment, then assesses the probability of risk occurrence based on the possibility measurement standard and generates a possibility measurement result, and according to the influence degree measurement standard, assesses the severity of the risk consequence from the performance, progress and resource three dimensions and generates an influence degree measurement result, and converts the measurement results of the two dimensions into quantitative numerical values to determine the risk level of each work item. Then, the system server performs risk matching in the risk case library according to the risk category and the risk level, generates a risk list, formulates a risk response plan containing an implementation scheme and a time node, and further generates the execution priority of each work item, breaking the limitation of traditional static sorting. The method solves the problem that the traditional method cannot respond to project changes through full-process dynamic adjustment, and improves the delivery efficiency and success rate of the project.

[0053] After combining the above content, the method provided by the present embodiment is further described in a more specific flow. Please refer to Figure 2 , another flowchart of the project work priority adjustment method in the embodiment of the present application.

[0054] 201, acquire the work item information in the target project, and determine the risk category of each work item according to the work item information, wherein the work item information includes the work item type, expected completion time and required resources. (This step has been described in 101, and will not be repeated here) 202, retrieve the risk category of each work item in the historical project database, and determine whether the risk category of the work item has historical data.

[0055] The historical project database refers to a database used by the system server to store the work item related data in all past projects, which includes but is not limited to the work item type, risk category, risk category, risk occurrence frequency and risk impact consequence of the historical project; the historical data refers to the past record data stored in the historical project database and matched with the risk category of the current work item.

[0056] Specifically, the system server first calls the historical project database, and then takes the risk category of each work item in the current target project as a retrieval keyword to retrieve in the historical project database, and compares the historical risk category with the risk category of the current work item one by one. Then, the system server determines whether the risk category of the current work item has historical data according to the comparison result, if there is at least one historical record consistent with the risk category of the current work item, it is determined that there is historical data; if no consistent historical record is found, it is determined that there is no historical data.

[0057] If the risk category of the work item has no historical data, step 203 is performed; if the risk category of the work item has historical data, step 205 is performed.

[0058] 203、Based on the technical novelty index and the technical complexity index obtained by quantifying the technical attributes of the work item, the likelihood measurement result of the work item is calculated.

[0059] The technical attributes of the work item refer to the characteristics possessed by the work item at the technical level, including the technical novelty index and the technical complexity index; the technical novelty index refers to the specific value obtained by the system server after quantifying the novelty dimension in the technical attributes of the work item, which is used to represent the difference between the technology adopted by the work item and the existing mature technology, and the higher the value, the stronger the technical novelty; the technical complexity index refers to the specific value obtained by the system server after quantifying the complexity dimension in the technical attributes of the work item, which is used to represent the difficulty level of the work item in terms of technical design, operation execution, etc., and the higher the value, the higher the technical complexity; the likelihood measurement result refers to the quantitative result of the probability of the occurrence of the risk corresponding to the current work item evaluated by the system server.

[0060] Specifically, the system server first determines the evaluation dimensions of the technical attributes of the work item. For technical novelty, the proportion of the use of non-widely used technology in the work item, the difference between the technical solution and the existing technology, etc. are considered; for technical complexity, the number of core technical links involved in the work item, the precision requirements of technical operations, etc. are considered. Then, the system server sets quantification standards for each evaluation dimension, converts qualitative descriptions into specific numerical values, for example, different score intervals are divided according to the number of technical novelty characteristics and the strength of technical complexity characteristics. Then, the system server scores the technical attributes of the current work item according to the quantification standards, and calculates the specific values of the technical novelty index and the technical complexity index respectively. Finally, the system server takes the average value of the technical novelty index and the technical complexity index as the likelihood measurement result of the current work item. Generally speaking, the higher the technical novelty and the technical complexity, the greater the risk occurrence likelihood, and the higher the likelihood measurement result value.

[0061] 204、Identify the sub-work items of the work item, and calculate the impact degree measurement result of the work item according to the criticality, dependency relationship and number of the sub-work items.

[0062] A sub-work item refers to a more refined task unit decomposed from a work item of a target project and needed to be executed to complete the work item; the criticality of a sub-work item refers to the importance of the derived sub-work item to the completion quality, progress and overall project goal of the work item; the dependency relationship of a sub-work item refers to the execution sequence correlation between different sub-work items recognized by the system server; the number of sub-work items refers to the specific number of sub-work items obtained by the system server after decomposing the current work item; and the impact degree measurement result of a work item refers to the severity level identification (such as high, medium and low) of the consequences caused by the project if the current work item has a risk, which is obtained by the system server through quantitative calculation based on the criticality, dependency relationship and number of sub-work items.

[0063] Specifically, the system server first performs structured decomposition on the current work item, identifies all sub-work items to be executed to complete the work item according to the execution process, technical link and other characteristics of the work item. Then, the system server evaluates the criticality of each sub-work item, for example, whether the software function test sub-work item directly affects the compliance of the system core function, the criticality is determined as high, and the system appearance inspection sub-work item has no direct impact on the core function, the criticality is determined as low. Then, the system server sorts out the dependency relationship between sub-work items, for example, the hardware interface test sub-work item needs to be completed before starting the software function test sub-work item, and the two exist a front-back dependency relationship; at the same time, the system server counts the number of sub-work items. Finally, the system server assigns weights to the criticality (such as high = 3, medium = 2, low = 1) and dependency relationship (such as strong dependency = 3, weak dependency = 2, no dependency = 1) of sub-work items, and calculates the impact degree measurement result of the work item by weighted summation, for example, the criticality weighted score is 2.8, the dependency relationship weighted score is 2.5, and the number of sub-work items is 3, and the impact degree measurement result is determined as medium after comprehensive calculation.

[0064] 205、Obtain the historical risk occurrence frequency corresponding to the risk category of each work item, and take the historical risk occurrence frequency as a possibility reference value.

[0065] The historical risk occurrence frequency refers to the ratio of the number of times that a risk consistent with the risk category of the current work item actually occurs in the past projects to the total number of projects corresponding to the risk category, which is used to represent the occurrence probability of the risk category in the historical projects; and the possibility reference value refers to the historical risk occurrence frequency obtained by the system server as the basis for evaluating the possibility of the risk of the current work item.

[0066] Specifically, the execution timing of this step is that after the system server retrieves the risk category of the current work item in the historical project database, it determines that the risk category has historical data. The system server first determines the risk category of the work item currently needing to be processed, and then calls the historical project database to filter out all historical project records containing the risk category in the historical project database with the risk category of the current work item as the search keyword, and counts the total number of actual occurrences of the risk category in these historical projects and the total number of historical projects containing the risk category. Then, the system server calculates the historical risk occurrence frequency of the risk category through the formula "historical risk occurrence frequency = total number of actual occurrences of the risk category / total number of historical projects containing the risk category", for example, in 100 historical projects containing the "delayed supply of cutting tools" risk, the risk actually occurs 20 times, and the historical risk occurrence frequency is 20%. Finally, the system server directly determines the calculated historical risk occurrence frequency as the possibility benchmark value of the risk occurrence possibility of the current work item, which lays the foundation for subsequent calculation of the possibility measure result combined with the time pressure coefficient and the resource pressure coefficient.

[0067] 206、Based on the expected completion time, calculate the time pressure coefficient, and based on the required resources, calculate the resource pressure coefficient. The time pressure coefficient is the ratio of the standard completion time to the expected completion time of the work item, and the resource pressure coefficient is the ratio of the required resources to the available resources of the work item.

[0068] The expected completion time refers to the planned completion date or time node preset for each work item; the time pressure coefficient refers to the ratio calculated by the system server based on the standard completion time and the expected completion time of the work item; the required resources refer to various elements required to complete each work item, including human resources, material resources, financial resources, etc.; the resource pressure coefficient refers to the ratio calculated by the system server based on the required resources and available resources of the work item, which is used to represent the execution pressure faced by the work item in the resource dimension. The larger the ratio, the greater the resource pressure; the standard completion time refers to the standard length of time required for the work item to be completed under normal execution conditions; the available resources refer to the total amount of various resources that can be allocated to each work item for use by the target project.

[0069] Specifically, the system server first acquires the expected completion time and required resources of the current work item, and then acquires the standard completion time set for different work item types. The system server calculates the time pressure coefficient of the work item based on the formula "time pressure coefficient = standard completion time ÷ expected completion time of work item". Meanwhile, the system server calculates the resource pressure coefficient of the work item based on the formula "resource pressure coefficient = required resources of work item ÷ available resources". If a comprehensive resource pressure coefficient is needed, the system server will perform a weighted average of the pressure coefficients of various resources to obtain the comprehensive resource pressure coefficient. For example, the numerical control machine tool resource pressure coefficient is 0.625, and the operator resource pressure coefficient is 0.667. After weighted average (for example, numerical control machine tool weight 0.6, numerical control operator weight 0.4), the comprehensive resource pressure coefficient is 0.625*0.6+0.667*0.4≈0.641. Through the above calculation, the system server finally obtains the time pressure coefficient and resource pressure coefficient of the current work item, which provides data support for subsequent calculation of the possibility measure result combined with the possibility benchmark value.

[0070] 207、The possibility benchmark value, time pressure coefficient and resource pressure coefficient are weighted and calculated to obtain the possibility measure result.

[0071] The possibility measure result refers to a specific numerical value or level identifier obtained by the system server through weighted calculation, which is used to quantitatively represent the risk occurrence probability of the current work item.

[0072] Specifically, the system server first acquires the possibility benchmark value, time pressure coefficient and resource pressure coefficient of the current work item, and then calls a preset weight configuration rule. The rule assigns weights to the three parameters according to project management requirements (such as trust in historical data, importance of time / resource constraints), for example, possibility benchmark value weight 0.5, time pressure coefficient weight 0.3, and resource pressure coefficient weight 0.2. Then, the system server performs weighted calculation based on the formula "possibility measure result = possibility benchmark value*corresponding weight + time pressure coefficient*corresponding weight + resource pressure coefficient*corresponding weight" to obtain the possibility measure result.

[0073] 208、The influence degree score of each work item in performance, progress and resource is calculated respectively, and the weighted average value of the influence degree score is taken as the influence degree measure result. The influence degree score is the severity score of the negative influence caused by performance, progress and resource.

[0074] The performance impact score refers to the severity score assessed by the system server regarding the negative impact of a risk on the functional implementation and quality standards of the work item's deliverables, quantifying the risk consequences in the performance dimension. The schedule impact score refers to the severity score assessed by the system server regarding the delays caused by a risk to the work item's completion time and the overall project schedule, quantifying the risk consequences in the schedule dimension. The resource impact score refers to the severity score assessed by the system server regarding the negative impact of a risk on additional resource consumption or resource shortages, quantifying the risk consequences in the resource dimension. The impact measurement result refers to the weighted average value used by the system server as a quantitative representation of the risk impact of the current work item, which can be further mapped to "high," "medium," and "low" level labels.

[0075] Specifically, the system server first determines the scoring criteria for three dimensions: performance, schedule, and resources. For example, it sets a score range of 1-5 points according to the degree of impact, from low to high, and clarifies the specific scenarios corresponding to each score (e.g., a 3-point score for the schedule dimension corresponds to "a delay of 3-7 days"). Then, it assesses the negative impact of any risk occurring in the current work item across the three dimensions and assigns a score for the degree of impact in each dimension based on the scoring criteria. Next, it calls the preset dimension weighting rules, which assign weights to the three dimensions based on project objectives (e.g., performance requirements are higher than schedule requirements), for example, performance weight 0.4, schedule weight 0.3, and resource weight 0.3. Finally, it calculates the weighted average using the formula: "Weighted Average = (Performance Score × Performance Weight + Schedule Score × Schedule Weight + Resource Score × Resource Weight) ÷ Total Weights". Finally, the system server determines the weighted average as the result of measuring the degree of impact of the current work item. For example, if a risk occurs in a system integration testing task, the performance needs to be retested due to inaccurate test data, which scores 4 points; the schedule is delayed by 5 days, which scores 3 points; and the resources require an additional 2 test engineers, which scores 3 points. Calculated according to the above weights, the weighted average is (4×0.4+3×0.3+3×0.3)÷(0.4+0.3+0.3)=3.4, which can be further mapped to the "medium to high impact" level.

[0076] 209. Quantify the probability measurement results and impact measurement results of each work item to obtain the risk level of each work item.

[0077] Step 209 specifically includes steps 2091 to 2095, which are not shown in the figure.

[0078] 2091、the possibility metric result and the impact degree metric result of each work item are respectively represented as a possibility matrix and an impact degree matrix, each row of the possibility matrix corresponds to a work item, and the possibility metric result of the work item is represented by a list, each row of the impact degree matrix corresponds to a work item, and the impact degree metric result of the work item is represented by a list.

[0079] The possibility matrix refers to a two-dimensional data table constructed by the system server, with work items as rows and possibility metric results as columns, for structurally storing the possibility metric results of all work items; the impact degree matrix refers to a two-dimensional data table constructed by the system server, with work items as rows and impact degree metric results as columns, for structurally storing the impact degree metric results of all work items.

[0080] Specifically, the system server first aggregates the basic information (such as work item ID, name) of all work items in the target project, as well as the corresponding possibility metric result and impact degree metric result, and then takes the work item as the row dimension of the matrix, assigns a unique row index to each work item, and ensures that each row corresponds to only one work item. Then, the system server constructs the possibility matrix and the impact degree matrix, respectively, where the columns of the possibility matrix only store the possibility metric results of the corresponding work items, and the columns of the impact degree matrix only store the impact degree metric results of the corresponding work items, completing the matrix construction to realize the structured management of data and lay the foundation for subsequent calculations.

[0081] 2092、the values of each work item in the possibility matrix and the impact degree matrix are normalized to unify the dimensions of different dimensions.

[0082] The value of each work item in the possibility matrix refers to the possibility metric result value of a single work item corresponding to each row in the possibility matrix; the value of each work item in the impact degree matrix refers to the impact degree metric result value of a single work item corresponding to each row in the impact degree matrix; the normalization processing refers to the process of converting data in different value ranges in the possibility matrix and the impact degree matrix to a unified interval (such as [0, 1]) by using a preset mathematical method (such as min-max normalization, z-score normalization); the dimensions of different dimensions refer to the numerical unit difference between the possibility metric result (such as a probability value between 0 and 1) and the impact degree metric result (such as a score value between 1 and 5) due to different evaluation dimensions, and the normalization processing can eliminate this difference.

[0083] Specifically, the system server first determines the distribution range of all values ​​in the probability matrix and the influence matrix, for example, by counting the minimum (e.g., 0.2) and maximum (e.g., 0.8) values ​​in the probability matrix, and the minimum (e.g., 1.5) and maximum (e.g., 4.5) values ​​in the influence matrix. Then, it calls a preset normalization algorithm (usually min-max normalization), whose formula is "normalized value = (original value - minimum value in the matrix) / (maximum value in the matrix - minimum value in the matrix)". For example, if the original value of a certain work item in the probability matrix is ​​0.426, the minimum value is 0.2, and the maximum value is 0.8, the normalized value is (0.426 - 0.2) ÷ (0.8 - 0.2) ≈ 0.377. Then, the system server performs normalization calculations on each value in the probability matrix and the influence matrix one by one, obtaining the normalized probability matrix and the normalized influence matrix. This ensures that the values ​​in the two matrices are within the same range, eliminating dimensional differences to guarantee the accuracy of subsequent calculations.

[0084] 2093. Perform weighted operations on the normalized probability matrix and influence matrix to generate a weighted probability matrix and a weighted influence matrix.

[0085] Weighted operation refers to the mathematical operation process in which the system server assigns preset weights to the normalized probability matrix and the normalized influence matrix, and multiplies each value in the matrix by its corresponding weight; the weighted probability matrix is ​​the new matrix obtained by multiplying each value in the normalized probability matrix by its corresponding weight; the weighted influence matrix is ​​the new matrix obtained by multiplying each value in the normalized influence matrix by its corresponding weight.

[0086] Specifically, the system server first invokes a preset matrix weight configuration rule. This rule assigns weights based on the project's emphasis on the "probability of risk occurrence" and the "degree of risk impact." For example, the normalized probability matrix has a weight of 0.4, and the normalized impact matrix has a weight of 0.6 (the total weight is 1, which can be adjusted according to project needs). Then, the system server performs a weighted calculation on the two normalized matrices, multiplying the value of each work item in the matrix by its preset weight. For instance, if a work item in the normalized probability matrix has a value of 0.377 and a weight of 0.4, the weighted value is 0.377 × 0.4 ≈ 0.151. This value constitutes the value of the corresponding work item in the weighted probability matrix. Finally, the system server stores the calculation results, generating a weighted probability matrix and a weighted impact matrix, highlighting the differences in importance of different assessment dimensions in risk level determination.

[0087] 2094. Multiply the weighted probability matrix and the weighted impact matrix item by item to calculate the overall risk score for each work item.

[0088] The multiplying each item by each item refers to a process in which the system server performs multiplication operation on elements at corresponding positions in the weighted possibility matrix and the weighted influence degree matrix; and the risk comprehensive score of each work item refers to a numerical value obtained by multiplying each item by each item, and used for comprehensively reflecting the probability of occurrence of the work item risk and the severity of the impact consequences.

[0089] Specifically, the system server first confirms the structural consistency of the two matrices, ensures that the number of rows (the number of work items), the number of columns are completely same, and each row of work items are matched one by one, and then performs multiplication operation on elements corresponding to each work item in the two matrices according to the rule of "risk comprehensive score = corresponding element value of the weighted possibility matrix × corresponding element value of the weighted influence degree matrix". Finally, the system server takes the operation result as the risk comprehensive score of the work item, and stores it separately or forms a new risk comprehensive score matrix, to provide quantitative basis for subsequent division of risk levels.

[0090] 2095、According to the numerical distribution of the risk comprehensive score of each work item, generate risk level division intervals, and map the risk comprehensive score of each work item to the corresponding risk level.

[0091] The numerical distribution of the risk comprehensive score of each work item refers to the numerical range, central tendency (such as the average value), dispersion degree (such as the variance) and other characteristics of the risk comprehensive score of all work items obtained by the system server through statistical analysis; the risk level division interval refers to a continuous numerical range set by the system server based on the numerical distribution, used to distinguish different risk levels, and each interval corresponds to a risk level; and the mapping of the risk comprehensive score to the corresponding risk level refers to a process in which the system server determines which division interval the risk comprehensive score of each work item falls into, and determines the risk level corresponding to the interval as the final risk level of the work item.

[0092] Specifically, the system server first performs data statistics on the risk comprehensive scores of all work items, and determines the overall range of the scores, for example, calculates that the minimum value of all scores is 0.03 and the maximum value is 0.12, and then determines the number of risk levels in combination with the requirement of project management for risk control precision (such as whether to need more detailed division of low and medium risks), and usually sets 5 levels (extremely low, low, medium, high, and extremely high); then, the system server calculates the interval interval = (maximum value of scores - minimum value of scores) / number of risk levels in the manner of equal interval division, and in combination with the example data, the interval is calculated as (0.12-0.03) ÷ 5 = 0.018, and then the minimum value of the scores is taken as the starting point, and the interval threshold values of each risk level are derived in sequence according to the interval, to generate the risk level division intervals. Finally, the system server reads the risk comprehensive score of each work item one by one, determines the interval to which it belongs, and then maps the score to the corresponding risk level, to complete the determination of the risk level of each work item.

[0093] 210、According to the risk category and risk level of each work item, match in the risk case library to obtain the risk list of each work item in the target project. (This step has been described in 104, and will not be repeated here) The updating of the risk case library specifically includes steps 2101-2103, which are not shown in the figure.

[0094] 2101、After generating the risk list of each work item in the target project, update the risk information of each work item to the risk case library, including risk category and risk level.

[0095] The risk information of each work item refers to a set of data used to describe the risk characteristics of the work item, including at least the risk category and the risk level (such as medium risk); the risk case library refers to a database that stores the risk cases, risk information and countermeasures of work items in historical projects and current projects, which is used for subsequent project risk matching and reference.

[0096] Specifically, the system server first extracts the risk information of each work item from the generated risk list, organizes the data in a structured format of "work item ID-risk category-risk level", and then calls the write interface of the risk case library to verify the integrity of the data to be updated (such as confirming that each entry contains risk category and risk level). Then, the system server writes the sorted risk information to the risk case library in batches or one by one, ensuring that each risk information is associated with the corresponding work item record. Finally, the system server generates a data update log to record the update time, the number of updated entries and other information, so as to trace back and verify later, supplement the risk data of the current project to the risk case library, and improve the accuracy of subsequent project risk matching.

[0097] 2102、In the implementation process of the risk response plan, when the risk item in the risk list is confirmed to be closed or acceptable, update the risk item's response plan to the risk case. Confirming to be closed or acceptable means that the risk item has been effectively solved or the risk has been reduced to a safe range.

[0098] The implementation process of the risk response plan refers to the stage in which the system server guides the project execution team to handle the risks of each work item according to the risk response plan. The risk item in the risk list refers to the specific risk corresponding to each work item recorded in the risk list (such as the "size deviation risk" of work item A). The confirmation of being closed or acceptable refers to the state in which the system server determines that the risk item has been effectively solved (risk closed) or the risk level has been reduced to the safety range acceptable to the project (risk acceptable) by collecting risk handling feedback data (such as detection reports, progress tracking records). The response plan of the risk item refers to the specific scheme formulated by the system server for handling the risk item, including the implementation scheme, the planned start time, the planned completion time, etc. The risk case refers to a single case entry stored in the risk case library, which contains risk information and corresponding response schemes.

[0099] Specifically, the system server first monitors the implementation progress of the risk response plan in real time, collects the handling state data of the risk item by connecting to the project management tool (such as the progress tracking system, the quality detection system), and triggers the response plan update process when it detects that the handling result of a certain risk item meets the "closed" or "acceptable" condition. Then, the system server extracts the complete response plan corresponding to the risk item, including the actual implemented implementation scheme, the adjusted time node, the actual resource input, etc., and locates the risk case entry corresponding to the risk item in the risk case library, and supplements the extracted response plan to the case, and stores it in association with the original risk category, risk level, etc. Finally, the system server marks the case update state, completes the perfection of the risk case, and provides a mature scheme that can be referred to for the response of similar risks in the future.

[0100] 2103、For each risk item in the risk list, an index for retrieval matching is established.

[0101] The index for retrieval matching refers to the key field combination or identifier created by the system server for each risk item for quick positioning and matching. The index content is usually related to the core attributes of the risk item (such as risk category, risk level, type of work item).

[0102] Specifically, the system server first analyzes the core attributes of each risk item, determines the index key field, which usually includes the risk category, risk level, and work item type, and generates a unique index for each risk item according to the preset index rule (such as the combination rule of "risk category-risk level-work item type"). Then, the system server stores the generated index in association with the corresponding risk case entry in the risk case library, establishes the mapping relationship between the index and the case, and optimizes the index structure (such as using a B+ tree index structure) to ensure that subsequent searches based on risk attributes can quickly locate matching risk cases. Finally, the system server verifies the effectiveness of the index by simulating a search (such as input: size deviation class risk + medium risk) to test the query speed and matching accuracy of the index, ensuring that the index can effectively improve the search efficiency of the risk case library.

[0103] 211. Generating a risk response plan based on the risk list, the risk response plan including an implementation scheme, a plan start time, and a plan completion time, and generating an execution priority of each work item in the target project according to the risk response plan. (This step has been described in 105, and will not be repeated here) 212. Constructing a priority conflict detection matrix based on each work item and the corresponding resource demand, the rows and columns of the priority conflict detection matrix being work items, and the elements in the matrix representing the resource demand overlap degree between the corresponding two work items.

[0104] The priority conflict detection matrix refers to a two-dimensional data table constructed by the system server to detect the priority conflicts that may occur between different work items due to resource demand overlap. The elements in the matrix are used to quantitatively represent the overlap degree of the corresponding two work items in terms of resource demand (the numerical range is usually 0-1, 0 indicating no overlap and 1 indicating complete overlap).

[0105] Specifically, the system server first sorts out the list of all work items in the target project and the corresponding resource demand of each work item, and clearly defines the type (such as human resources, material resources) and quantity of resources required by each work item. Then, taking the work item as the row and column dimensions of the matrix, the system server assigns a unique row index and column index to each work item to ensure that the rows and columns of the matrix correspond to all work items. Then, for each element in the matrix (i.e., each pair of work item combinations), the system server analyzes the overlap of the resource types required by the two work items (such as both requiring a CNC lathe), and calculates the demand proportion of the overlapping resource type (such as work item A requiring 3 CNC lathes and work item B requiring 2 CNC lathes, with an overlapping resource demand proportion of (3+2) / (total available CNC lathe quantity)). The calculation result is taken as the numerical value of the element, and the construction of the priority conflict detection matrix is completed, providing data support for subsequent judgment of work item resource conflicts.

[0106] 213、determine whether the execution time periods of the two work items corresponding to each element in the priority conflict detection matrix overlap.

[0107] The execution time period refers to the planned execution time range set by the system server for each work item (e.g., May 10-20, 2024).

[0108] Specifically, the system server first extracts the planned execution time period (including the planned start time and the planned completion time) of each work item from the work item information and stores it in association with the work item ID, and then iterates through each element in the priority conflict detection matrix to determine the two work items corresponding to the element (e.g., element (i, j) corresponds to "work item i" and "work item j"). Then, the system server calls the time overlap judgment algorithm to compare the execution time periods of the two work items to determine whether there is an intersection. If the planned start time of work item i is less than or equal to the planned completion time of work item j, and the planned completion time of work item i is greater than or equal to the planned start time of work item j, it is determined that the execution time periods overlap; otherwise, it is determined that they do not overlap. Finally, the system server records the time overlap judgment results for each pair of work items to provide a basis for subsequent calculation of resource demand.

[0109] 214、If there is an overlap, calculate the resource demand of the two work items in the overlapping execution time period.

[0110] Calculating the resource demand in the overlapping time period refers to the system server counting the total demand for each type of overlapping resource by the two work items in the overlapping time period.

[0111] Specifically, the system server first calculates the specific start and end times of the overlapping execution time period based on the execution time periods of the two work items, and then analyzes the resource demand of the two work items in the overlapping time period. If the resource demand of a work item is evenly distributed throughout the execution time period (e.g., work item A requires 3 CNC lathes from May 10 to May 20 (10 days), with a daily demand of 0.3 units), the resource demand in the overlapping time period is calculated (e.g., 1.5 units for 5 days of overlapping time). If the resource demand is concentrated at a specific time point (e.g., work item B requires 2 CNC lathes from May 15 to May 17), the resource demand in the overlapping time period is directly extracted. Then, the resource demand of the same type for the two work items in the overlapping time period is summed up to obtain the total demand for that type of resource. Finally, the system server aggregates the total demand for all overlapping resource types to form resource demand summary data for the two work items in the overlapping time period.

[0112] 215、When the resource demand exceeds the total amount of available resources, the work item with lower priority is arranged to be executed after the work item with higher priority is executed, and the work item information is updated to obtain the adjusted execution priority.

[0113] Specifically, the system server first compares the resource demand of the two work items in the overlapping time period with the total available resources of the corresponding resources, for example, the total demand for CNC lathes in the overlapping time period is 10, and the total available resources is 8, and it is determined that there is a resource shortage, and then the execution priority of the two work items generated before is retrieved to determine the work items with higher and lower priorities, for example, “work item A” has higher priority than “work item B”. Then, the system server queries the planned completion time of the work item with higher priority (e.g. May 20), and adjusts the planned start time of the work item with lower priority to be after the completion time (e.g. May 21), so as to ensure that the execution time periods of the two work items do not overlap, and at the same time, the system server updates the information of the work item with lower priority, including the new execution time period, the resource demand time period, etc., and re-verifies whether the resource demands of the two work items after adjustment still conflict. Finally, the system server determines the new execution priority based on the adjusted execution time period and resource demand of the work items, so as to ensure reasonable resource allocation and avoid resource competition.

[0114] 216、If there is no overlap, it is determined that there is no resource competition between the two work items, and the execution priority is not changed.

[0115] There is no resource competition means that the system server determines that there is no conflict between the two work items in terms of resource use, and the two work items can be executed simultaneously or sequentially according to the original plan without causing resource shortage.

[0116] Specifically, the system server first reconfirms the comparison result of the resource demand of the two work items and the total available resources, and if it is still determined that there is no resource competition, the system server generates a determination result to explicitly adjust the execution order of the two work items, and the system server retains the execution priority generated before without modifying any work item information, so as to ensure that the project is pushed forward according to the original plan and reduce unnecessary adjustment cost.

[0117] 217, real-time acquisition of the execution progress of each work item to obtain the actual resource consumption and progress data of each work item. (This step has been described in 106, and will not be repeated here) 218, updating the execution priority of each work item in the target project according to the resource consumption and progress data.

[0118] Step 218 specifically includes steps 2181 to 2183, which are not shown in the figure 2181, calculating the resource consumption change rate and the progress change rate according to the resource consumption and progress data of each work item, the resource consumption being the difference between the remaining resource amount at the last detection and the current detected resource remaining amount, and the progress data being the difference between the current actual completion progress and the completion progress at the last detection.

[0119] The resource consumption change rate refers to the change amplitude of resource consumption per unit time calculated by the system server based on resource consumption and detection cycle length; and the progress change rate refers to the change amplitude of progress per unit time calculated by the system server based on progress data and detection cycle length.

[0120] Specifically, the system server first determines the detection cycle (such as 1 day, 3 days, which is preset according to the project control accuracy), and extracts two sets of key data of each work item in the current detection cycle: one is resource data (remaining resource amount at last detection, resource remaining amount at current detection), and the other is progress data (current actual completion progress, completion progress at last detection), then calculates the resource consumption of each work item according to the formula "resource consumption = remaining resource amount at last detection - resource remaining amount at current detection", and calculates the progress data of each work item according to the formula "progress data = current actual completion progress - completion progress at last detection". Then, the system server combines the detection cycle length (such as T days), and calculates the two change rates according to the formulas "resource consumption change rate = resource consumption / detection cycle length" and "progress change rate = progress data / detection cycle length" respectively. Finally, the system server stores the calculated resource consumption change rate and progress change rate in association with each work item, providing data support for subsequent threshold judgment.

[0121] 2182、When the resource consumption change rate exceeds the preset consumption change threshold and the progress change rate exceeds the preset progress change threshold, new work item information is generated according to the resource consumption and progress data.

[0122] The new work item information refers to the system server based on the re-adjusted work item key attribute data, including the updated expected completion time, required resources, etc.

[0123] Specifically, the system server compares the resource consumption change rate with the preset consumption change threshold, and at the same time compares the progress change rate with the preset progress change threshold based on the obtained resource consumption change rate and progress change rate. When the resource consumption change rate exceeds the preset consumption change threshold and the progress change rate exceeds the preset progress change threshold, it is determined that the work item has made certain progress. At this time, the system server calculates the new required resources based on the current resource consumption, and calculates the new expected completion time based on the current progress, and finally generates new work item information based on the new required resources and the new expected completion time, ensuring synchronization with the actual execution state.

[0124] 2183、According to the new work item information, the execution priority of each work item in the target project is adjusted.

[0125] Specifically, the system server first aggregates information of all work items in the target project: for the work items that have generated new information, the updated expected completion time and required resources are adopted; for the work items that do not trigger the step 2182, the original work item information is used. The system server re-evaluates all work items of the target project (using the updated work item information) with reference to the logic and steps for initially generating the execution priority, reorders all work items, generates the adjusted execution priority, and ensures that the priority matches the actual execution state of the work item, optimizes resource allocation and project advancement efficiency.

[0126] By using the project work priority adjustment method in the embodiments of the present application, the system server first acquires work item information of each work item in the target project, and determines the risk category of each work item based on the work item information, and then combines the criticality of the sub-work items of the work item, the dependency relationship of the sub-work items, the possibility benchmark value, the time pressure coefficient, and the resource pressure coefficient, and quantitatively calculates the possibility measurement result and the influence degree measurement result through the possibility matrix and the influence degree matrix, and finally maps the risk comprehensive score of each work item to the corresponding risk level and generates a risk list. Then, the system server judges the overlap of the resource demand amount and the execution time period of the work item through the priority conflict detection matrix, solves the resource competition to generate the initial execution priority, and dynamically updates the new work item information and the execution priority based on the resource consumption change rate and the progress change rate. This method realizes the whole-process management and control of the project work priority from the fixed initial sorting to the dynamic adjustment, not only can identify the work item risk in advance, avoid resource mismatch and progress delay, but also can adapt to the state change in the execution process in real time, ensure that the priority always matches the actual demand of the work item, and finally improve the project resource utilization efficiency and the overall delivery success rate.

[0127] The method provided in the above embodiments can be executed by a server of a project work priority adjustment system. Next, the project work priority adjustment system in the embodiments of the present application is described from the perspective of hardware processing. Please refer to Figure 3 , which is a schematic diagram of an entity device structure of the project work priority adjustment system in the embodiments of the present application.

[0128] It should be noted that Figure 3 The structure of the project work priority adjustment system shown is only an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0129] As Figure 3As shown, the project work priority adjustment system includes a central processing unit (CPU) 301 which can perform various appropriate actions and processes in accordance with a program stored in a read-only memory (ROM) 302 or a program loaded from a storage section 308 into a random access memory (RAM) 303, such as performing the methods described in the above embodiments. In the RAM 303, various programs and data required for the operation of the system are also stored. The CPU 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0130] Connected to the I / O interface 305 are an input section 306 including an audio input device, a push button switch, and the like; an output section 307 including a liquid crystal display (LCD), an audio output device, an indicator, and the like; a storage section 308 including a hard disk and the like; and a communication section 309 including a network interface card such as a LAN (Local Area Network) card, a modem, and the like. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to the I / O interface 305 as necessary. A removable media 311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is attached to the drive 310 as necessary, so that a computer program read therefrom is installed into the storage section 308 as necessary.

[0131] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with embodiments of the present application. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing a computer program for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 309, and / or installed from the removable media 311. When the computer program is executed by the central processing unit (CPU) 301, various functions defined in the present application are performed.

[0132] Note that specific examples of computer-readable storage media can include but are not limited to an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, computer-readable storage media can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0133] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functional processes, and operational processes, according to various embodiments of the present application. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or the block diagrams, can be implemented by computer readable program instructions such as program code. Such computer readable program instructions can be provided to a processor of a computer, or other programmable data processing apparatus, to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flow diagrams and / or block diagrams. These computer readable program instructions can also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and the other

[0134] In particular, the project work priority adjustment system of the embodiment includes a processor and a memory, and the memory stores a computer program. When the computer program is executed by the processor, the project work priority adjustment system provided in the above embodiment is implemented.

[0135] As another aspect, the present application also provides a computer readable storage medium. The storage medium can be included in the project work priority adjustment system described in the above embodiments, or can exist independently without being assembled into the project work priority adjustment system. The storage medium carries one or more computer programs. When the one or more computer programs are executed by a processor of the project work priority adjustment system, the project work priority adjustment system implements the project work priority adjustment system provided in the above embodiments.

[0136] The above embodiments are only used to illustrate the technical solutions of the present application, but not limit the present application; even though the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

[0137] In the above embodiments, the term "when" can be interpreted to mean "if" or "after" or "in response to determining" or "in response to detecting" depending on the context. Similarly, the phrase "upon determining" or "if detecting (a stated condition or event)" can be interpreted to mean "if determining" or "in response to determining" or "upon detecting (a stated condition or event)" or "in response to detecting (a stated condition or event)" depending on the context.

[0138] In the above embodiments, all or some of the flowcharts or methods can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, the computer program product includes one or more computer instructions stored on a computer readable storage medium. When loaded and executed by a computer, the computer program instructions cause the computer to perform all or some of the flowcharts or methods described in the embodiments of the present application. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, from a website, a computer, a server or a data center to another website, computer, server or data center through wired (for example, coaxial cable, optical fiber, digital subscriber line) or wireless (for example, infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media sets. The available medium can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, solid state disk), etc.

[0139] A person of ordinary skill in the art can understand that all or part of the flow of the above-mentioned embodiment method can be instructed by a computer program to relevant hardware, and the program can be stored in a computer readable storage medium, and the program can include the flow of the above-mentioned method embodiments when executed. The aforementioned storage medium includes ROM or random storage memory RAM, magnetic disk or optical disk, and various program code storage media.

Claims

1. A method for adjusting project work priorities, characterized in that, include: Obtain information on multiple work items in the target project, and determine the risk category of each work item based on the work item information, which includes work item type, expected completion time, and required resources; The probability of each work item's risk is assessed based on the probability metric, generating a probability metric result. The impact of each work item's risk is assessed based on the impact metric, generating an impact metric result. The probability metric is used to measure the probability of risk occurrence, and the impact metric is used to assess the severity of the risk consequences in terms of performance, schedule, and resources. The probability measurement result and the impact degree measurement result of each work item are quantitatively calculated to obtain the risk level of each work item; Based on the risk category and risk level of each work item, a risk case database is used to obtain a risk list for each work item in the target project. A risk response plan is generated based on the risk list. The risk response plan includes an implementation plan, a start time, and a completion time. Based on the risk response plan, the execution priority of each work item in the target project is generated. The execution progress of each work item is obtained in real time, and the actual resource consumption and progress data of each work item are obtained. Based on the resource consumption and progress data, update the execution priority of each work item in the target project.

2. The method according to claim 1, characterized in that, The process of assessing the probability of each work item's risk occurrence based on a probability metric to generate a probability metric result, and assessing the degree of risk impact of each work item based on an impact metric to generate an impact metric result, specifically includes: Obtain the historical risk occurrence frequency corresponding to the risk category of each work item, and use the historical risk occurrence frequency as the probability benchmark value; The time pressure coefficient is calculated based on the expected completion time, and the resource pressure coefficient is calculated based on the required resources. The time pressure coefficient is the ratio of the standard completion time to the expected completion time of the work item, and the resource pressure coefficient is the ratio of the resources required by the work item to the available resources. The probability measurement result is obtained by weighting the probability benchmark value, the time pressure coefficient, and the resource pressure coefficient. Calculate the impact score of each work item in terms of performance, schedule, and resources, and use the weighted average of the impact scores as the impact measurement result. The impact score is a score of the severity of the negative impact on performance, schedule, and resources.

3. The method according to claim 2, characterized in that, Before the step of obtaining the historical risk occurrence frequency corresponding to the risk category of each work item and using the historical risk occurrence frequency as the probability baseline value, the method further includes: Search the historical project database for the risk category of each work item to determine if there is historical data for the risk category of the work item. If there is no historical data for the risk category of the work item, the probability measurement result of the work item is calculated based on the technical novelty index and technical complexity index obtained by quantifying the technical attributes of the work item. Identify the sub-work items of the work item, and calculate the impact degree measurement result of the work item based on the criticality, dependency and quantity of the sub-work items.

4. The method according to claim 1, characterized in that, The probability measurement result and impact degree measurement result of each work item are quantitatively calculated to obtain the risk level of each work item, specifically including: The probability measurement result and the influence measurement result of each work item are represented as a probability matrix and an influence matrix, respectively. Each row of the probability matrix corresponds to a work item, and the columns represent the probability measurement result of the work item. Each row of the influence matrix corresponds to a work item, and the columns represent the influence measurement result of the work item. The values ​​of each work item in the probability matrix and the degree of influence matrix are normalized to unify the dimensions of different dimensions; The normalized probability matrix and influence matrix are weighted to generate a weighted probability matrix and a weighted influence matrix; The weighted probability matrix is ​​multiplied item by item by the weighted influence matrix to calculate the comprehensive risk score for each work item; Based on the numerical distribution of the comprehensive risk score for each work item, a risk level division interval is generated, and the comprehensive risk score for each work item is mapped to the corresponding risk level.

5. The method according to claim 1, characterized in that, The updates to the risk case database specifically include: After generating a risk list for each work item in the target project, the risk information for each work item is updated in the risk case library. The risk information includes the risk category and risk level. During the implementation of the risk response plan, when a risk item in the risk list is confirmed to be closed or acceptable, the response plan for that risk item is updated to the risk case. The confirmation that the risk item is closed or acceptable means that the risk item has been effectively resolved or the risk has been reduced to a safe range. Create a search index for each risk item in the risk list.

6. The method according to claim 1, characterized in that, Based on the resource consumption and progress data, update the execution priority of each work item in the target project, specifically including: Based on the resource consumption and progress data of each work item, the resource consumption change rate and the progress change rate are calculated. The resource consumption is the difference between the remaining resource amount at the time of the last detection and the remaining resource amount at the current detection. The progress data is the difference between the current actual completion progress and the completion progress at the time of the last detection. When the rate of change of resource consumption exceeds a preset consumption change threshold and the rate of change of progress exceeds a preset progress change threshold, new work item information is generated based on the resource consumption and progress data. Based on the new work item information, adjust the execution priority of each work item in the target project.

7. The method according to claim 1, characterized in that, Before the step of acquiring the execution progress of each work item in real time and obtaining the actual resource consumption and progress data of each work item, the method further includes: Based on each work item and its corresponding resource requirement, a priority conflict detection matrix is ​​constructed. The rows and columns of the priority conflict detection matrix are the work items, and the elements in the matrix represent the degree of overlap in resource requirements between two corresponding work items. Determine whether the execution time periods of the two work items corresponding to each element in the priority conflict detection matrix overlap; If they overlap, calculate the resource requirements of the two work items during the overlapping execution time period; When the resource demand exceeds the total available resources, lower priority work items are scheduled to be executed after higher priority work items have been completed, and the work item information is updated to obtain the adjusted execution priority. If they do not overlap, it is determined that there is no resource contention between the two work items, and the execution priority is not changed.

8. A project work priority adjustment system, characterized in that, Includes one or more processors and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the project work priority adjustment system to perform the method as described in any one of claims 1-7.

9. A computer-readable storage medium comprising instructions, characterized in that, When the instruction is run on the project work priority adjustment system, the project work priority adjustment system performs the method as described in any one of claims 1-7.

10. A computer program product, characterized in that, When the computer program product is run on the project work priority adjustment system, the project work priority adjustment system performs the method as described in any one of claims 1-7.

Images