Project management method, device, equipment and product based on quantitative model

Abstract

The invention discloses a project management method, device, equipment and product based on a quantitative model, and relates to the technical field of computer software. The method comprises the steps of obtaining planning data of a target project, real-time data of the target project in a propulsion process and historical data; based on the planning data, evaluating the scale of a plurality of execution nodes contained in the target project; based on the planning data, evaluating the cost use condition of the target project; based on the planning data, the real-time data and the historical data, the promotion progress of the target project is evaluated, so that standardized and unified quantitative evaluation is carried out on varied project management through the quantitative model, project managers can visually monitor the risk, progress and the like of the project, the project risk is reduced, and the project management efficiency is improved. Project progress is guaranteed, and a clear and transparent data basis is provided for performance supervision, decision support of projects and the like.

Description

Technical Field

[0001] This application relates to the field of computer software technology, and particularly to a project management method, device, equipment and product based on a quantization model. Background Art

[0002] In related technologies, project management tools are usually required during the progress of a project. Existing project management tools generally involve the management of common functions such as project plans, personnel management, and project changes, but it is difficult to clearly evaluate and manage the progress of the entire project.

[0003] Therefore, how to more clearly evaluate and manage the progress of a project is an urgent problem to be solved currently. Summary of the Invention

[0004] The main purpose of this application is to provide a project management method, device, equipment and product based on a quantization model, aiming to solve the technical problem of how to more clearly evaluate and manage the progress of a project.

[0005] To achieve the above purpose, this application proposes a project management method based on a quantization model. The project management method based on a quantization model includes: Obtain the planning data of the target project, the real-time data and historical data during the progress of the target project; Based on the planning data, evaluate the scale of multiple execution nodes included in the target project to obtain a scale score; Based on the planning data, evaluate the cost usage of the target project to obtain a cost score; Based on the planning data, real-time data and historical data, evaluate the progress of the target project to obtain a progress score; Based on the scale score, the cost score and the progress score, calculate the benchmark score of the target project, and the benchmark score is used to comprehensively evaluate the target project.

[0006] In some embodiments, the step of evaluating the scale of multiple execution nodes included in the target project based on the planning data to obtain a scale score includes: Obtain multiple execution nodes included in the target project from the planning data, where each execution node has a corresponding difficulty coefficient, and different difficulty coefficients correspond to different preset scores; Determine the total score of the target project as the sum of the preset scores of the multiple execution nodes; Based on the preset score range corresponding to the total score, determine the corresponding scale score range, where multiple preset score ranges are pre-divided for the total score, and different preset score ranges correspond to different scale score ranges; Output the scale score range to the user, so that the user can select the scale score corresponding to the target project within the scale score range based on the planning data.

[0007] In some embodiments, the method for evaluating the cost usage of the target project based on the planning data to obtain a cost score includes: Obtain the total cost of the target project from the planning data; Based on the preset cost range corresponding to the total cost, determine the corresponding cost score range, where multiple preset cost ranges are pre-divided for the total cost, and different preset cost ranges correspond to different cost score ranges; Output the cost score range to the user, so that the user can select the cost score corresponding to the target project within the cost score range based on the planning data.

[0008] In some embodiments, the method for evaluating the progress of the target project based on the planning data, real-time data, and historical data to obtain a progress score includes: Obtain the planned progress of the target project in the current time period from the planning data, and obtain the real-time progress of the target project in the current time period from the real-time data; Based on the deviation between the planned progress and the real-time progress, determine the current deviation ratio; Based on the preset deviation range corresponding to the current deviation ratio, determine the corresponding progress score range, where multiple preset deviation ranges are pre-divided for the current deviation ratio, and different preset deviation ranges correspond to different progress score ranges; Output the progress score range corresponding to the current deviation ratio to the user, so that the user can select the current deviation score corresponding to the target project within the progress score range based on the planning data; Determine the average value of the historical deviation score and the current deviation score as the progress score of the target project; where the historical deviation score is obtained from the progress deviation situation in the historical data.

[0009] In some embodiments, after calculating the baseline score of the target project based on the scale score, the cost score, and the progress score, the method further includes: Based on the awards declared by the target project, determine the project qualification score of the target project; Determine the technical contribution score of the target project based on the technical solution adopted by the target project; Determine the economic contribution score of the target project based on the project revenue of the target project; Determine the strategic value score of the target project based on the preset plan of the target project; Determine the vertical integration score of the target project based on the subcontracting cost of the target project; Calculate the comprehensive score of the target project based on the project qualification score, technical contribution score, economic contribution score, strategic value score, and vertical integration score.

[0010] In some embodiments, the determining the economic contribution score of the target project based on the project revenue of the target project includes: Calculate the revenue ratio of the target project based on the project revenue and total cost of the target project; wherein, multiple revenue ratio intervals are pre-divided for the revenue ratio, and different revenue ratio intervals correspond to different revenue score intervals; Output the revenue score interval corresponding to the project revenue to the user, and determine the score selected by the user within the revenue score interval corresponding to the revenue ratio of the target project as the economic contribution score; The determining the strategic value score of the target project based on the preset plan of the target project includes: Obtain the matching degree between the target project and the preset plan, wherein, multiple matching degree types are pre-divided for the matching degree, and different matching degree types correspond to different value score intervals; Output the value score interval corresponding to the matching degree to the user, and determine the score selected by the user within the value score interval as the strategic value score; The determining the vertical integration score of the target project based on the subcontracting cost of the target project includes: Calculate the vertical integration score through Expression 1; wherein, Expression 1 is: vertical integration score = (total cost - subcontracting cost) / total cost.

[0011] In some embodiments, the calculating the comprehensive score of the target project based on the project qualification score, technical contribution score, economic contribution score, strategic value score, and vertical integration score includes: Calculate the comprehensive score of the target project through Expression 2; wherein, Expression 2 is: Comprehensive score = (benchmark score + (project qualification score + technical contribution score + economic contribution score + strategic value score) * vertical integration score)).

[0012] In addition, to achieve the above object, the present application further provides a project management device based on a quantization model. The project management device based on the quantization model includes: A data acquisition module, configured to acquire the planning data of the target project, the real-time data during the progress of the target project, and the historical data; A quantization evaluation module, configured to evaluate the scale of a plurality of execution nodes included in the target project based on the planning data to obtain a scale score; evaluate the cost usage of the target project based on the planning data to obtain a cost score; evaluate the progress of the target project based on the planning data, the real-time data, and the historical data to obtain a progress score; and calculate a benchmark score of the target project based on the scale score, the cost score, and the progress score, where the benchmark score is used to comprehensively evaluate the target project.

[0013] In addition, to achieve the above object, the present application further provides a project management device based on a quantization model. The project management device based on the quantization model includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the computer program is configured to implement the steps of the project management method based on the quantization model as described above.

[0014] In addition, to achieve the above object, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps of the project management method based on the quantization model as described above.

[0015] One or more technical solutions proposed by the present application have at least the following technical effects: By acquiring the planning data of the target project, the real-time data during the progress of the target project, and the historical data; evaluating the scale of a plurality of execution nodes included in the target project based on the planning data; evaluating the cost usage of the target project based on the planning data; and evaluating the progress of the target project based on the planning data, the real-time data, and the historical data, the diverse project management is standardized and unified through a quantization model, so that project managers can intuitively monitor the risks, progress, etc. of the project, thereby helping to reduce project risks, ensure project progress, and provide a clear and transparent data basis for performance supervision and project decision support, etc. Description of the Drawings

[0016] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0017] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0018] Figure 1 It shows a schematic flowchart of a project management method based on a quantization model provided by an embodiment of the present application; Figure 2 It shows a schematic structural diagram of a project management device based on a quantization model provided by an embodiment of the present application; Figure 3 It shows a schematic structural diagram of a project management device based on a quantization model provided by an embodiment of the present application.

[0019] The realization of the purpose, functional characteristics and advantages of the present application will be further described with reference to the embodiments and the drawings. Detailed implementation manners

[0020] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0021] To better understand the technical solutions of the present application, the following will be described in detail in combination with the drawings of the specification and specific implementation manners.

[0022] The main solution of the embodiment of the present application is: obtaining the planning data of the target project, the real-time data and historical data during the progress of the target project; based on the planning data, evaluating the scale of multiple execution nodes included in the target project to obtain a scale score; based on the planning data, evaluating the cost usage of the target project to obtain a cost score; based on the planning data, real-time data and historical data, evaluating the progress of the target project to obtain a progress score; based on the scale score, cost score and progress score, calculating the benchmark score of the target project, and the benchmark score is used to comprehensively evaluate the target project.

[0023] In the related art, project management tools are usually required during the progress of a project. Existing project management tools usually involve the management of common functions such as project plans, personnel management, and project changes. For example, management tools such as project startup, change management, and process control are provided. However, during the progress of a project, it is difficult to intuitively evaluate and assess the progress of the project, and subjective judgments usually need to rely on the experience of project managers or project management personnel.

[0024] In summary, how to more clearly evaluate and manage the progress of a project is an urgent problem to be solved currently.

[0025] Based on this, the present application provides a solution. By establishing a quantitative model for key elements in a project (such as scale, cost, progress of advancement, etc.), and conducting quantitative analysis based on the quantitative model, during the process of project advancement, elements that could not be combined originally can be combined and compared through specific numerical values, enabling staff to make a clearer judgment on the overall situation of the project, which is of great help for subsequent decision-making, management, etc. of the project.

[0026] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or a project management device based on a quantitative model that can implement the above functions. Hereinafter, taking the project management device based on a quantitative model as an example, this embodiment and the following embodiments will be described.

[0027] Referring to Figure 1 , Figure 1 shows a schematic flowchart of a project management method based on a quantitative model provided by an embodiment of the present application. The project management method based on a quantitative model can be applied to a project management device based on a quantitative model, including the following steps S110 to step S150: Step S110, obtain the planning data of the target project, the real-time data during the advancement of the target project, and the historical data.

[0028] In scenarios such as enterprises, the development of some related projects is usually involved. Project development refers to the entire process from the conception of a project to the completion of the project, involving stages such as requirement planning, plan formulation, task assignment, node review, and cost promotion. The core of project development is to transform the ideas in the conception into reality, while the core of project management is to ensure that the project is successfully completed within the specified time, budget, and quality range.

[0029] To better manage the projects under development, a project development management platform is usually set up. In the project development management platform, multiple projects that are in progress (or including those that have been developed and completed) can be centrally managed.

[0030] In some implementation manners, during the requirement planning stage and the plan formulation stage of the project, project objectives, resource input plans, execution plans, business contracts, and acceptance criteria, etc. can be established to determine the scale, cost, and objectives to be achieved of the project. In addition, the responsibilities of each task execution node in the plan can be authorized. Thus, before the actual execution of the project begins, a task book can be formed, that is, the planning data described in this embodiment.

[0031] In this embodiment, before the target project starts to be executed, since there can be a very large number of execution nodes involved in the target project and the involved fields may be different, it is necessary to determine in advance the personnel respectively involved in the execution nodes, that is, enter the task assignment stage. In the task assignment stage, the multiple already-split execution nodes are dispatched to the corresponding persons in charge one by one, and the start date, end date, planned duration, etc. are detailedly constrained, so as to facilitate monitoring the completion status of each execution node during the subsequent project progress.

[0032] During the progress of the target project, relevant real-time data can be obtained to quantitatively evaluate the progress of the target project. Among them, the real-time data can include the completion status of each execution node, the usage of costs, etc., which are not limited in this embodiment.

[0033] Step S120, based on the planning data, evaluate the scale of the multiple execution nodes included in the target project to obtain a scale score.

[0034] In some embodiments, multiple execution nodes included in the target project can be obtained from the planning data; the sum of the preset scores of the multiple execution nodes is determined as the total score of the target project; based on the preset score range corresponding to the total score, the corresponding scale score range is determined, where multiple preset score ranges are pre-divided for the total score, and different preset score ranges correspond to different scale score ranges; the scale score range is output to the user so that the user can select the scale score corresponding to the target project within the scale score range based on the planning data.

[0035] Specifically, in the planning data of the task book, the multiple execution nodes included in the target project are clearly recorded. We can quantitatively evaluate each execution node separately and summarize to obtain the overall scale of the target project.

[0036] In this embodiment, the project general benchmark story point (i.e., the requirement evaluation benchmark) can be used as the basis. For example, the project general benchmark story point can be "develop user functions". An inherent benchmark score (such as 5 points) can be set in advance for "develop user functions", and thus, based on this standard, scores can be defined for other specific execution nodes. In some embodiments, the operation of defining scores for the execution nodes with reference to the benchmark score can be pre-executed by the staff, which is not limited in this embodiment.

[0037] As an example, the score of the "develop user function" execution node with a lower work difficulty coefficient and difficulty is defined as 5 points, and the score of the "account authentication function" execution node with a slightly higher work difficulty coefficient and difficulty is defined as 12 points, and so on. Taking the project's general benchmark story points as a reference, the scale of each execution node is quantified and scored, and then all are added up to get the total score.

[0038] After obtaining the total score, the overall scale of the target project can be evaluated based on the scope standard formulated by the enterprise. In this embodiment, multiple score intervals can be set in advance for the total score. For example, a project with a total score less than 5000 points can be determined as a small project, a project with a total score greater than or equal to 5000 points and less than 10000 points can be determined as a medium-sized project, and a project with a total score greater than or equal to 15000 points can be determined as a large project. Different preset score intervals correspond to preset scale scoring intervals, for example, the scale scoring interval of a small project is 10-20 points, the scale scoring interval of a medium-sized project is 20-30 points, and the scale scoring interval of a large project is 30-40 points. Based on this, the corresponding preset score interval can be determined by the total score obtained by the aforementioned summation, and then the scale scoring interval corresponding to the preset score interval is output to the user, and the user selects a value within the scale scoring interval as the final scale score of the target project.

[0039] Step S130, based on the planning data, the cost usage of the target project is evaluated to obtain a cost score.

[0040] In some implementations, the total cost of the target project can be obtained from the planning data; based on a preset cost range corresponding to the total cost, a corresponding cost score range is determined; and the cost score range is output to the user so that the user can select a cost score corresponding to the target project within the cost score range based on the planning data.

[0041] Specifically, the planning data in the task book clearly records the total cost pre-planned for the target project. Based on the size of the total cost, we can evaluate the overall investment scale of the target project.

[0042] Similar to step S120, the total cost is pre-divided into multiple preset cost intervals, and different preset cost intervals correspond to different cost scoring intervals. As an example, a total cost of less than 1 million yuan can be defined as a small project, a total cost of greater than or equal to 1 million yuan and less than 2 million yuan can be defined as a medium-sized project, and a total cost of greater than or equal to 2 million yuan can be defined as a large project.

[0043] Different preset cost ranges correspond to preset cost score ranges. For example, the cost score range for small projects is 10 - 20 points, the cost score range for medium-sized projects is 20 - 30 points, and the cost score range for large projects is 30 - 40 points. Based on this, the total cost obtained previously can be used to first determine whether the target project is a small, medium-sized, or large project, and then output the corresponding cost score range to the user. The user can select a value within the cost score range as the final cost score of the target project.

[0044] Step S140: Based on the planning data, real-time data, and historical data, evaluate the progress of the target project to obtain a progress score.

[0045] In some embodiments, the planned progress of the target project in the current time period can be obtained from the planning data, and the real-time progress of the target project in the current time period can be obtained from the real-time data; based on the deviation between the planned progress and the real-time progress, the current deviation ratio is determined; the current deviation ratio and the corresponding preset progress score range are output to the user, so that the user can obtain the current deviation score corresponding to the target project within the preset progress score range based on the planning data; the historical deviation score of the target project in the current time period is obtained; the average value of the historical deviation score and the current deviation score is determined as the progress score of the target project; wherein, the historical deviation score is obtained from the progress deviation situation in the historical data.

[0046] Specifically, the entire target project can be segmented by time in the planning data, and each time period has a corresponding planned progress. For example, for a project, it can be split into multiple time periods by month, and the execution nodes are divided in advance by month, so that each month has a corresponding execution node to be completed, that is, the planned progress.

[0047] In some embodiments, the project manager can evaluate the completion situation each month to obtain the real-time progress of the corresponding month. By comparing the real-time progress with the planned progress of that month, the current deviation ratio can be obtained. The current deviation ratio can have a preset deviation range. For example, the current deviation ratio less than or equal to 10% can be determined as a low deviation, the current deviation ratio greater than 10% and less than or equal to 30% can be determined as a medium deviation, the current deviation ratio greater than 30% and less than or equal to 40% can be determined as a high deviation, and the current deviation ratio greater than 40% can be determined as an extremely high deviation.

[0048] In some embodiments, different preset deviation ranges correspond to different progress score ranges. For example, in the preset deviation range of low deviation, the corresponding progress score range is 30 - 40 points; in the preset deviation range of medium deviation, the corresponding progress score range is 20 - 30 points; in the preset deviation range of high deviation, the corresponding progress score range is 10 - 20 points; in the preset deviation range of extremely high deviation, the corresponding progress score range is 5 - 10 points. Based on this, the user can select a value within the progress score range as the current deviation score of the target project.

[0049] Then, the historical deviation score of the target project in the current time period can be obtained. Among them, the historical data can include the "current deviation score" corresponding to each previous time period (such as month), that is, the "historical deviation score" for the current moment in this embodiment. That is, the corresponding "current deviation score" is calculated for each time period and recorded in the historical data.

[0050] In this embodiment, for the current moment, the average value of the historical deviation score and the current deviation score can be determined as the final progress score of the target project.

[0051] Step S150, calculate the baseline score of the target project based on the scale score, cost score, and progress score.

[0052] To comprehensively evaluate the target project, the comprehensive score can be calculated through the baseline score and the metric score, which is convenient for comprehensive comparison. Among them, the baseline score is the sum of the scale score, cost score, and progress score obtained in the above steps S120 to S140.

[0053] In some embodiments, the metric score can include project qualification score, technical contribution score, economic contribution score, strategic value score, and vertical integration score. To calculate the metric score for the target project, this embodiment establishes a variety of corresponding quantification models, specifically as follows ① - ⑤: ① Project qualification acquisition quantification model.

[0054] In this embodiment, the sum of the award scores corresponding to each award declared by the target project can be used as the project qualification score. Specifically, after the project is completed, the project may apply for and obtain certain awards, or there may be relevant patent outputs. In this embodiment, it can be quantified according to the influence of the awards obtained by the project. For example, national awards are 20 points, provincial and municipal level awards are 15 points, patents generated by the project are 10 points, and software copyrights are 5 points, so as to obtain the project qualification score.

[0055] ② Technical contribution quantification model.

[0056] In this embodiment, the score selected by the user based on the technical level adopted for the target project can be determined as the technical contribution score. Specifically, after the project is completed, the solution of the project can be rated (i.e., the technical level) according to the technologies or methods used during the project. For example, if the technology or method used in the project is a top-level solution in the industry, it is identified as the leading level, and the quantified score is not higher than 30 points; if the technology or method adopted by the project uses an advanced technical architecture and solution, which can ensure the advancement, stability, and scalability of the project, it is identified as the excellent level, and the quantified score is not higher than 20 points; if the technology or method adopted by the project uses the current mainstream solution in the industry, which ensures the stability and scalability of the project, it is identified as the standard level, and the quantified score is not higher than 10 points. Based on this, the technical contribution score can be obtained.

[0057] ③ Economic contribution quantification model.

[0058] After the project is completed, the project can bring certain benefits to the enterprise. In this embodiment, the project benefits of the target project can be obtained. For the project benefits, there can be multiple benefit ratio intervals in advance, such as project benefits ≥ 5% of project investment, project benefits ≥ 10% of project investment, project benefits ≥ 20% of project investment, project benefits ≥ 30% of project investment, etc.

[0059] For each benefit ratio interval, there can also be corresponding benefit score intervals in advance. By way of example, for project benefits ≥ 5% of project investment, the quantified score can be set not higher than 10 points; for project benefits ≥ 10% of project investment, the quantified score can be set not higher than 15 points; for project benefits ≥ 20% of project investment, the quantified score can be set not higher than 30 points; for project benefits ≥ 30% of project investment, the quantified score can be set not higher than 40 points.

[0060] Based on this, the benefit score interval corresponding to the project benefits can be output to the user, and the user can select a score within the benefit score interval as the final economic contribution score.

[0061] ④ Strategic value quantification model. After the project is completed, the matching degree between the target project and the preset plan can be calculated to evaluate whether the project conforms to the current or long-term strategic plan. For the matching degree, multiple matching degree types can be predefined, and different matching degree types can correspond to different value score ranges. For example, if the project meets the strategic plan in multiple aspects and can promote the rapid realization of the strategy, it is defined as the leading level, and the value score range can be set to ≤30 points; if the project can contribute to the realization of the strategy in individual aspects and help accelerate the realization, it is defined as the excellent level, and the value score range can be set to ≤20 points; if the project can indirectly contribute to the realization of the strategy and help with rapid development, it is defined as the standard level, and the value score range can be set to ≤10 points. Based on this, the value score range corresponding to the matching degree can be output to the user, and the score selected by the user within the value score range is determined as the strategic value score.

[0062] ⑤ Vertical integration quantification model. During the project implementation process, the degree of dependence of the project on other suppliers needs to be concerned. For example, if the project is fully implemented independently without external suppliers or semi-finished products purchased, the quantification score can be set to 100%. If the project is not fully implemented independently, the vertical integration score is calculated using the following expression: Vertical integration score = (total cost - subcontracting cost) / total cost.

[0063] Based on the benchmark score obtained from the above steps S120 to S150 and the measurement scores obtained from the aforementioned ① - ⑤, the comprehensive score corresponding to the entire target project can be calculated comprehensively. Among them, as an example, the comprehensive score = (scale comprehensive score + cost comprehensive score + schedule comprehensive score + (project qualification score + technical contribution score + economic contribution score + strategic value score) × vertical integration score).

[0064] In some embodiments, based on the profit and loss situation of the enterprise, an enterprise's project index for the current year can also be set to evaluate the subsequent performance appraisal and bonus payment of the project. By way of example, assuming that the enterprise is in a profitable state in the current year and the profit exceeds the target, and the enterprise adjusts the total bonus from the original standard value n to n + m, then when paying the bonus, the comprehensive score of the project can be scaled proportionally through the enterprise's project index for the current year to adapt to the change in the total bonus pool, thus facilitating the payment of the bonus. For example, the enterprise's project index for the current year can be set to 120%, and the final score of the project is the comprehensive score * 120%. This embodiment provides a project management method based on a quantitative model. By obtaining the planning data of the target project, the real-time data and historical data during the progress of the target project; evaluating the scale of multiple execution nodes included in the target project based on the planning data; evaluating the cost usage of the target project based on the planning data; and evaluating the progress of the target project based on the planning data, real-time data and historical data, the diverse project management can be standardized and unified through a quantitative model for quantitative evaluation, enabling project managers to intuitively monitor the risks, progress, etc. of the project, thereby helping to reduce project risks, ensure project progress, and provide a clear and transparent data basis for performance supervision and project decision-making support, etc.

[0065] In some embodiments, based on the above-mentioned quantitative logic, a management platform based on a project quantitative model can be established to better manage the project in combination with the foregoing quantitative evaluation steps.

[0066] As an implementation method, when a project is established, the project's file information (such as the foregoing planning data) can be managed in a structured manner. For example, the project name, project type, project code, cost type, project status, person in charge, project establishment department, cost budget, implementation location, project start and end dates, project overview and background, etc. can be interrelated and bound to the target project, so as to ensure that all relevant members of the entire project team can clearly understand the entire project, thus facilitating efficient communication during the subsequent project progress.

[0067] When a project is established, responsibilities and authorizations can also be assigned to the members within the project team. For example, different levels, positions, attendance times, etc. can be assigned to different personnel, so as to ensure that project team members have a clearer understanding of their job responsibilities. In addition, the clear planning of personnel levels, positions, etc. can more easily calculate the human resource cost of the entire target project.

[0068] In some embodiments, in response to a viewing request for a target project, node information of multiple execution nodes corresponding to the target project is obtained from the planning data; wherein, the node information includes one or more of a start date, an end date, a person in charge, a planned duration, and a task status; based on the type of the viewing request, the execution nodes and the corresponding node information are visually displayed.

[0069] Among them, the viewing request can be a click operation by the user. For example, an interface integrated with multiple tabs can be presented to the user, and the user can click on the tab they want to enter, thereby generating a corresponding viewing request.

[0070] In some embodiments, when the type of the viewing request is a project plan, according to the node order of the target project, each parent node, the corresponding child nodes, and the corresponding node information are sequentially and visually displayed on the current interface.

[0071] For example, if the parent nodes displayed on the current interface are nodes A, B, and C, where the child nodes of node A are a, b, and c, the child nodes of node B are e and f, and the child nodes of node C are g, then the display order of all nodes on the current interface is: A, a, b, c, B, e, f, C, g.

[0072] In some embodiments, when the type of the viewing request is a task board, the child nodes and the corresponding node information are visually displayed on different sub-interfaces of the current interface, where different sub-interfaces correspond to different task statuses, and each child node has a corresponding task status.

[0073] For example, the sub-interfaces displayed on the current interface can include four, which are "Task Pool", "Not Started", "In Progress", and "Completed" in sequence. Among them, each sub-interface includes child nodes, and the child nodes also have corresponding node information. For example, for the child node b, its node information can include: the number is 30040001, and the person in charge is xx.

[0074] In some embodiments, during the process from project establishment to promotion, all involved files can be uploaded to the management platform. When the viewing request is for project documents, all involved files can be displayed on the current interface. In some specific examples, the project documents can be classified according to task nodes, so as to obtain a folder corresponding to each task node. In other specific examples, the project documents can be classified according to their uses, etc., and this embodiment does not make any limitations here.

[0075] In some embodiments, project team members can log in using a username and password to access their corresponding workbenches. In the workbench, project team members can clearly see their to-do tasks (i.e., task nodes) and related node information. In some embodiments, project team members can perform corresponding operations on the to-do tasks, such as transferring out, applying for an extension, etc. In still other embodiments, project team members can also click on a preset button on the current interface to implement functions such as project application, financial sharing, project archives, cost accounting, daily reports, salary management, customer archives, etc.

[0076] In some embodiments, the managers of the project team can also log in using a username and password to enter the management interface. In the management interface, all projects (such as including target projects) can be listed, and at least part of the planning data of the corresponding projects can be displayed. As an example, the name, department, type, planned duration, start and end times, total cost, used cost, etc. corresponding to the project can be displayed. In addition, based on the foregoing quantification steps, the evaluation results of the overall progress of the project and the evaluation results of the cost usage situation can be displayed in the interface corresponding to the project, so that the progress of the project is more clearly visible.

[0077] In some embodiments, the number of projects in different stages can also be counted according to the stage of the project. For example, there are 18 projects in the research stage, 17 projects in the project establishment stage, and 16 projects in the promotion stage. In some embodiments, it can also be counted according to the risk situation of the project. For example, there are 18 projects that exceed the time limit, and 17 projects with cost overruns.

[0078] In addition, in some embodiments, the management platform provided in this embodiment can be developed in the form of components, encapsulating the functions in a componentized manner, and then forming a business service module through the method of business aggregation, so as to support multiple databases and multiple deployment environments, improving the stability and flexibility of the platform.

[0079] This application also provides a project management device based on a quantification model. Please refer to Figure 2 The project management device 100 based on the quantification model includes: A data acquisition module 110, configured to acquire the planning data of the target project, the real-time data and historical data during the progress of the target project; The quantification evaluation module 120 is configured to evaluate the scale of multiple execution nodes included in the target project based on the planning data to obtain a scale score; evaluate the cost usage of the target project based on the planning data to obtain a cost score; evaluate the progress of the target project based on the planning data, real-time data, and historical data to obtain a progress score; and calculate a benchmark score of the target project based on the scale score, the cost score, and the progress score, where the benchmark score is used to comprehensively evaluate the target project.

[0080] The project management device 100 based on a quantification model provided in this application adopts the project management method based on a quantification model in the above embodiment, and can solve the technical problem of how to more clearly evaluate and manage the progress of a project. Compared with the prior art, the beneficial effects of the project management device 100 based on a quantification model provided in this application are the same as those of the project management method based on a quantification model provided in the above embodiment, and other technical features in the project management device 100 based on a quantification model are the same as the features disclosed in the method of the above embodiment, and will not be elaborated here.

[0081] This application provides a project management device based on a quantification model. The project management device based on a quantification model includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the project management method based on a quantification model in Embodiment 1 above.

[0082] Next, refer to Figure 3 , which shows a schematic structural diagram of a project management device based on a quantification model suitable for implementing the embodiments of this application. The project management device based on a quantification model in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 3 The project management device based on a quantification model shown is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of this application.

[0083] As Figure 3As shown, the project management device 200 based on the quantization model may include a processing device 210 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 220 or a program loaded from a storage device 230 into a random access memory (RAM: Random Access Memory) 240. In the RAM 240, various programs and data required for the operation of the project management device based on the quantization model are also stored. The processing device 210, the ROM 220, and the RAM 240 are connected to each other through a bus 250. An input / output (I / O) interface 260 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 260: an input device 270 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 280 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 230 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 290. The communication device 290 may allow the project management device based on the quantization model to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a project management device based on the quantization model having various systems, it should be understood that it is not required to implement or have all the shown systems. More or fewer systems may be implemented or had alternatively.

[0084] Specifically, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device, or installed from the storage device 230, or installed from the ROM 220. When the computer program is executed by the processing device 210, the above functions defined in the methods of the embodiments disclosed in the present application are executed.

[0085] The project management device based on the quantization model provided by the present application adopts the project management method based on the quantization model in the above embodiments, and can solve the technical problem of how to more clearly evaluate and manage the progress process of a project. Compared with the prior art, the beneficial effects of the project management device based on the quantization model provided by the present application are the same as those of the project management method based on the quantization model provided by the above embodiments, and other technical features in the project management device based on the quantization model are the same as the features disclosed in the method of the previous embodiment, and will not be elaborated here.

[0086] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0087] As described above, the above are only specific embodiments of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0088] This application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, it realizes the steps of the project management method based on a quantization model as described above.

[0089] The computer program product provided by this application can solve the technical problem of how to more clearly evaluate and manage the progress process of a project. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as those of the project management method based on a quantization model provided in the above embodiments, and will not be elaborated herein.

[0090] The above are only partial embodiments of this application, and thus do not limit the patent scope of this application. Any equivalent structural transformation made under the technical concept of this application by using the content of the specification and drawings of this application, or direct / indirect application in other related technical fields, is included within the patent protection scope of this application.

Claims

1. A project management method based on a quantitative model, characterized in that: The project management method based on the quantitative model includes: Obtaining planning data of the target project, real-time data of the target project during its advancement, and historical data; Based on the planning data, the scales of multiple execution nodes included in the target project are evaluated to obtain a scale score; Based on the planning data, the cost usage of the target project is evaluated to obtain a cost score; Based on the planning data, real-time data and historical data, the progress of the target project is evaluated to obtain a progress score; A benchmark score for the target project is calculated based on the scale score, the cost score, and the progress score, and the benchmark score is used to conduct a comprehensive evaluation of the target project.

2. The project management method based on quantitative model according to claim 1, characterized in that: The step of evaluating the scale of multiple execution nodes included in the target project based on the planning data to obtain a scale score includes: Acquire multiple execution nodes included in the target project from the planning data, wherein each of the execution nodes has a corresponding difficulty coefficient, and different difficulty coefficients correspond to different preset scores; Determine the sum of the preset scores of the plurality of execution nodes as the total score of the target project; Based on the preset score interval corresponding to the total score, determine the corresponding scale scoring interval, wherein the total score is pre-divided into a plurality of preset score intervals, and different preset score intervals correspond to different scale scoring intervals; The scale score interval is output to a user, so that the user selects a scale score corresponding to the target project within the scale score interval based on the planning data.

3. The project management method based on quantitative model according to claim 1, characterized in that: The cost usage of the target project is evaluated based on the planning data to obtain a cost score, including: Acquiring the total cost of the target project from the planning data; Based on the preset cost interval corresponding to the total cost, determining the corresponding cost scoring interval, wherein the total cost is pre-divided into a plurality of preset cost intervals, and different preset cost intervals correspond to different cost scoring intervals; The cost scoring interval is output to a user, so that the user selects a cost score corresponding to the target project within the cost scoring interval based on the planning data.

4. The project management method based on quantitative model according to claim 1, characterized in that: The progress of the target project is evaluated based on the planning data, real-time data and historical data to obtain a progress score, including: Acquire the planned progress of the target project in the current time period from the planning data, and acquire the real-time progress of the target project in the current time period from the real-time data; Determining a current deviation ratio based on a deviation between the planned progress and the real-time progress; Determine a corresponding progress scoring interval based on a preset deviation interval corresponding to the current deviation ratio, wherein a plurality of preset deviation intervals are pre-divided according to the current deviation ratio, and different preset deviation intervals correspond to different progress scoring intervals; Outputting a progress score interval corresponding to the current deviation ratio to a user, so that the user selects a current deviation score corresponding to the target project within the progress score interval based on the planning data; An average value of the historical deviation score and the current deviation score is determined as the progress score of the target project; wherein the historical deviation score is obtained through the progress deviation situation in the historical data.

5. The project management method based on quantitative model according to claim 1, characterized in that: After calculating the benchmark score of the target project based on the scale score, the cost score, and the progress score, the method further includes: Determine the project qualification score of the target project based on the awards applied for by the target project; Determine the technical contribution score of the target project based on the technical solution adopted by the target project; Determining an economic contribution score of the target project based on the project income of the target project; Determine the strategic value score of the target project based on the preset plan of the target project; Determining a vertical integration score for the target project based on the subcontracting costs of the target project; Based on the project qualification score, technical contribution score, economic contribution score, strategic value score and vertical integration score, a comprehensive score of the target project is calculated.

6. The project management method based on quantitative model according to claim 5, characterized in that: Determining the economic contribution score of the target project based on the project income of the target project includes: Based on the project income and total cost of the target project, the income ratio of the target project is calculated; wherein the income ratio is pre-divided into a plurality of income ratio intervals, and different income ratio intervals correspond to different income score intervals; Outputting the income score interval corresponding to the project income to the user, and determining the score selected by the user within the income score interval corresponding to the income ratio of the target project as the economic contribution score; Determining the strategic value score of the target project based on the preset plan of the target project includes: Obtaining the matching degree between the target project and the preset plan, wherein the matching degree is pre-divided into a plurality of matching degree types, and different matching degree types correspond to different value score intervals; Outputting the value score interval corresponding to the matching degree to the user, and determining the score selected by the user within the value score interval as the strategic value score; Determining the vertical integration score of the target project based on the subcontracting cost of the target project includes: The vertical integration score is calculated by expression 1; Among them, expression 1 is: vertical integration score = (total cost - subcontracting cost) / total cost.

7. The project management method based on quantitative model according to claim 5, characterized in that: The comprehensive score of the target project is calculated based on the project qualification score, technical contribution score, economic contribution score, strategic value score and vertical integration score, including: Calculate the comprehensive score of the target project by expression 2; Among them, expression 2 is: Comprehensive score = (benchmark score + (project qualification score + technical contribution score + economic contribution score + strategic value score) * vertical integration score)).

8. A project management device based on a quantitative model, characterized in that: The project management device based on the quantitative model includes: A data acquisition module is used to acquire planning data of a target project, real-time data of the target project during its advancement, and historical data; A quantitative assessment module is used to assess the scale of multiple execution nodes included in the target project based on the planning data to obtain a scale score; assess the cost usage of the target project based on the planning data to obtain a cost score; assess the progress of the target project based on the planning data, real-time data and historical data to obtain a progress score; calculate a benchmark score for the target project based on the scale score, the cost score and the progress score, and the benchmark score is used to conduct a comprehensive assessment of the target project.

9. A project management device based on a quantitative model, characterized in that: The project management device based on a quantitative model comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the project management method based on a quantitative model as described in any one of claims 1 to 7.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the project management method based on a quantitative model according to any one of claims 1 to 7 are implemented.

Images