A high-level planning and scheduling method based on resource constraints, system and medium

Abstract

The present invention relates to the technical field of industrial Internet of Things, and specifically to an advanced planning and scheduling method, system and medium based on resource constraints; setting priorities between tasks; creating a project and selecting a project type; creating a task and selecting a task type; establishing a predecessor task of the current task as needed, calculating the impact of the predecessor task on the current task, and forming a planned date for the task after being affected by the predecessor task; judging whether the current task is affected, and changing the planned date if affected; detecting the load of each resource and issuing an early warning; through the above-mentioned method, improving the efficiency of enterprise resource management and communication, and reducing the risks and problems of the project caused by resources.

Description

Technical Field

[0001] The present invention relates to the technical field of industrial Internet of Things, and in particular to an advanced planning and scheduling method, system and medium based on resource constraints. Background Art

[0002] As enterprises are faced with managing multiple projects at the same time, managing large projects, cross-departmental collaboration, resource management and optimization, and risk and problem management, project management is becoming more and more complex. Manual Excel or simple project management software cannot handle the problem of timely changes in project plans as problems and risks change. At the same time, the load warning of resources in multi-project plans cannot be well displayed, making it difficult to optimize resources.

[0003] In summary, it is very necessary to propose an advanced planning and scheduling method and system based on resource constraints to improve enterprise resource management and communication efficiency and reduce the risks and problems caused by resources in projects. Summary of the invention

[0004] The purpose of the present invention is to provide an advanced planning and scheduling method, system and medium based on resource constraints, so as to improve the efficiency of enterprise resource management and communication and reduce the risks and problems caused by resources in projects.

[0005] In a first aspect, an embodiment of the present invention provides an advanced planning and scheduling method based on resource constraints, comprising the following steps:

[0006] Set the priority between tasks; the predecessor task is the first priority, the current task is the second priority, the subtask is the third priority, the parent task is the fourth priority, the successor task is the fifth priority, and the project is the sixth priority;

[0007] Create a project and select the project type;

[0008] Create a task and select the task type;

[0009] Establish predecessor tasks for the current task as needed, calculate the impact of the predecessor tasks on the current task, and form a planned date for the task after being affected by the predecessor tasks;

[0010] Determine whether the current task is affected by the predecessor, and change the planned date if it is affected by the predecessor;

[0011] Determine whether the current task is affected by subtasks, and change the planned date if affected by subtasks;

[0012] Determine whether the current task is affected by the parent task, and change the planned date if it is affected by the parent task;

[0013] Determine whether the current task is affected by the subsequent task, and change the planned date if it is affected by the subsequent task;

[0014] Detect the load of each resource and issue an early warning.

[0015] Among them, in the step of creating a project and selecting the project type:

[0016] The item types include forward-order items and reverse-order items.

[0017] Among them, in the step of creating a task and selecting the task type:

[0018] Fill in the planned start date, duration date and planned completion date according to different task types.

[0019] Among them, in the step of determining whether the current task is affected by the predecessor and changing the planned date after being affected by the predecessor:

[0020] After the current task is affected by the predecessor, the change of the current task is restricted according to the execution status of the subtasks.

[0021] Among them, in the step of determining whether the current task is affected by the subtask and changing the planned date after being affected by the subtask,

[0022] After the current task is affected by the subtask, the change of the current task is restricted according to the execution status of the parent task.

[0023] Among them, in the step of determining whether the current task is affected by the parent task and changing the planned date after being affected by the parent task,

[0024] After the current task is affected by the parent task, the changes of the current task are restricted according to the predecessor dependency relationship with the successor task.

[0025] Among them, in the step of determining whether the current task is affected by the subsequent task and changing the planned date after being affected by the subsequent task,

[0026] When the current task is affected by a subsequent task, changes to the current task are restricted based on the project type.

[0027] In a second aspect, an embodiment of the present invention provides an advanced planning and scheduling system based on resource constraints, including a priority setting module, a project creation module, a task creation module, a calculation module, a judgment module, a load generation module, a detection module and an early warning module;

[0028] The priority setting module is used to set the priority between tasks;

[0029] The project creation module is used to create a project and select a project type;

[0030] The task creation module is used to create tasks and select task types;

[0031] The calculation module is used to calculate the impact of the predecessor task on the current task and form a planned date for the task after being affected by the predecessor;

[0032] The judgment module is used to judge whether the current task is affected, and change the planned date if it is affected;

[0033] The load generation module is used to generate the load of each associated resource;

[0034] The detection module is used to detect the load of each resource and determine whether the load is overloaded;

[0035] The warning module is used to issue a warning prompt in the event of an overload condition.

[0036] Wherein, the judgment module includes a first sub-judgment unit, a second sub-judgment unit, a third sub-judgment unit and a fourth sub-judgment unit;

[0037] The first sub-judgment unit is used to judge whether the current task is affected by the predecessor;

[0038] The second sub-judgment unit is used to judge whether the current task is affected by the sub-task;

[0039] The third sub-judgment unit is used to judge whether the current task is affected by the parent task;

[0040] The fourth sub-judgment unit is used to judge whether the current task is affected by the subsequent task.

[0041] In a third aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the resource constraint-based advanced planning and scheduling method of any one of the first aspects above.

[0042] The present invention provides an advanced planning and scheduling method, system and medium based on resource constraints, which sets priorities among tasks; wherein the predecessor task is the first priority, the current task is the second priority, the subtask is the third priority, the parent task is the fourth priority, the successor task is the fifth priority, and the project is the sixth priority; creates a project and selects a project type; creates a task and selects a task type; establishes a predecessor task of the current task as required, calculates the influence of the predecessor task on the current task, and forms a planned date after the task is affected by the predecessor task; determines whether the current task is affected by the predecessor task, and changes the planned date after being affected by the predecessor task; determines whether the current task is affected by the subtask, and changes the planned date after being affected by the subtask; determines whether the current task is affected by the parent task, and changes the planned date after being affected by the parent task; determines whether the current task is affected by the successor task, and changes the planned date after being affected by the successor task; detects the load of each resource and issues an early warning. The priority setting module is used to set the priority between tasks; the project creation module creates a project and selects a project type; the task creation module creates a task and selects a task type; the calculation module calculates the impact of the predecessor task on the current task and forms a planned date after the task is affected by the predecessor; the judgment module judges whether the current task is affected and changes the planned date after being affected; the load generation module generates the load of each associated resource; the detection module detects the load of each resource and determines whether the load is overloaded; the early warning module issues an early warning prompt in the case of overload. Through the above method, it is achieved to improve the efficiency of enterprise resource management and communication, and reduce the risks and problems caused by resources in the project. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 It is a flow chart of the steps of the high-level planning and scheduling method based on resource constraints of the present invention.

[0045] Figure 2 It is a schematic diagram of the priorities among the tasks of the present invention.

[0046] Figure 3 It is a schematic diagram of the principle of the advanced planning and scheduling system based on resource constraints of the present invention.

[0047] 10-priority setting module, 20-project creation module, 30-task creation module, 40-calculation module, 50-judgment module, 51-first sub-judgment unit, 52-second sub-judgment unit, 53-third sub-judgment unit, 54-fourth sub-judgment unit, 60-load generation module, 70-detection module, 80-early warning module. DETAILED DESCRIPTION

[0048] See also Figure 1 The embodiment of the present invention provides an advanced planning and scheduling method based on resource constraints, comprising the following steps:

[0049] S100: Setting priorities among tasks; wherein the predecessor task is the first priority, the current task is the second priority, the subtask is the third priority, the parent task is the fourth priority, the successor task is the fifth priority, and the project is the sixth priority.

[0050] In this embodiment, the priorities between tasks are set; Figure 2 As shown, the predecessor task is the first priority, the current task is the second priority, the subtask is the third priority, the parent task is the fourth priority, the successor task is the fifth priority, and the project is the sixth priority. Among them, the current task change will be restricted by the predecessor task with the first priority, the second priority will be restricted by the subtasks below it and affect the planned date of the subtasks after the restriction is passed, the third priority will be restricted by the parent task above it and affect the planned date of the parent task after the restriction is passed, the fourth priority will be restricted by the successor task backwards and affect the planned date of the successor task after the restriction is passed, and finally it will be restricted by the project and affect the planned date of the project through the restriction.

[0051] S200: Create a project and select a project type; wherein the project types include forward-order projects and reverse-order projects.

[0052] In this embodiment, a project is created and a project type is selected, wherein the project types include forward-scheduled projects and backward-scheduled projects; wherein a forward-scheduled project is a project with a planned start date, and a backward-scheduled project is a project with a planned completion date with a deadline.

[0053] S300: Create a task, select a task type, and fill in the planned start date, duration date, and planned completion date according to different task types.

[0054] In this embodiment, a task is created, a task type is selected, and the planned start date, duration date, and planned completion date are filled in according to different task types. The system calculates other unfilled items based on the filled items.

[0055] S400: Establishing predecessor tasks of the current task as needed, calculating the impact of the predecessor tasks on the current task, and forming a planned date for the task after being affected by the predecessor tasks.

[0056] In this embodiment, the predecessor task of the current task is established as needed, the predecessor dependency is selected, the system calculates the impact of the predecessor task on the current task, and forms a planned date for the task after being affected by the predecessor.

[0057] S500: Determine whether the current task is affected by the predecessor, and change the planned date if it is affected by the predecessor.

[0058] In this embodiment, after the current task is affected by the predecessor, the change of the current task is restricted according to the execution status of the subtask, among which the predecessor, executed or completed subtasks will restrict the planned start date of the current task from being postponed to after the planned start date of the subtask, otherwise the impact of the predecessor task on the current task will not be accepted to return to the previous planned date; if the restriction check is passed, the change of the current task will affect the change of the planned date of the subtask according to the type of subtask.

[0059] S600: Determine whether the current task is affected by a subtask, and change the planned date if the current task is affected by the subtask.

[0060] In this embodiment, after the current task is affected by the subtask, the change of the current task is restricted according to the execution status of the parent task. If there is a predecessor, executed or completed parent task, the planned start date of the current task cannot be advanced to before the planned start date of the parent task. Otherwise, the impact of the predecessor task and the subtask on the current task will not be accepted and returned to the previous planned date. If the restriction check passes, the change of the current task will affect the change of the planned date of the parent task according to the type of the parent task.

[0061] S700: Determine whether the current task is affected by the parent task, and change the planned date if it is affected by the parent task.

[0062] In this embodiment, after the current task is affected by the parent task, the change of the current task is restricted according to the predecessor dependency relationship with the successor task. The executed or completed successor task will restrict the planned start and completion dates of the current task to be postponed. Otherwise, the influence of the predecessor task, subtask and subsidiary task on the current task will not be accepted and returned to the previous planned date. If the restriction check is passed, the change of the current task will affect the change of the planned date of its successor task according to the predecessor dependency relationship.

[0063] S800: Determine whether the current task is affected by the subsequent task, and change the planned date if it is affected by the subsequent task.

[0064] In this embodiment, after the current task is affected by the subsequent task, the change of the current task is restricted according to the type of project. The planned start date of the current task shall not be earlier than the planned start date of the sequential project, and the planned completion date shall not be later than the planned completion date of the reversed project.

[0065] S900: Detect the load of each resource and issue an early warning.

[0066] In this embodiment, after the task plan is scheduled or changed, the system generates the load of each associated resource, issues an early warning for the daily overload situation under weekly statistics, and reminds the management personnel to optimize and adjust the resources.

[0067] See also Figure 3 , the embodiment of the present invention also provides an advanced planning and scheduling system based on resource constraints, including a priority setting module 10, a project creation module 20, a task creation module 30, a calculation module 40, a judgment module 50, a load generation module 60, a detection module 70 and an early warning module 80;

[0068] The priority setting module 10 is used to set the priority between tasks;

[0069] The project creation module 20 is used to create a project and select a project type;

[0070] The task creation module 30 is used to create tasks and select task types;

[0071] The calculation module 40 is used to calculate the impact of the predecessor task on the current task and form a planned date for the task after being affected by the predecessor task;

[0072] The determination module 50 is used to determine whether the current task is affected, and to change the planned date if it is affected;

[0073] The load generation module 60 is used to generate the load of each associated resource;

[0074] The detection module 70 is used to detect the load of each resource and determine whether the load is overloaded;

[0075] The warning module 80 is used to issue a warning prompt in the event of an overload condition.

[0076] In this embodiment, the priority setting module 10 sets the priority between tasks; the project creation module 20 creates a project and selects a project type; the task creation module 30 creates a task and selects a task type; the calculation module 40 calculates the impact of the predecessor task on the current task and forms a planned date after the task is affected by the predecessor; the judgment module 50 judges whether the current task is affected and changes the planned date after being affected; the load generation module 60 generates the load of each associated resource; the detection module 70 detects the load of each resource and determines whether the load is overloaded; the early warning module 80 is used to issue an early warning prompt in the case of overload. This improves the efficiency of enterprise resource management and communication and reduces the risks and problems caused by resources in projects.

[0077] Further, the judgment module 50 includes a first sub-judgment unit 51, a second sub-judgment unit 52, a third sub-judgment unit 53 and a fourth sub-judgment unit 54;

[0078] The first sub-judgment unit 51 is used to judge whether the current task is affected by the previous task;

[0079] The second sub-judgment unit 52 is used to judge whether the current task is affected by the sub-task;

[0080] The third sub-judgment unit 53 is used to judge whether the current task is affected by the parent task;

[0081] The fourth sub-judgment unit 54 is used to judge whether the current task is affected by the subsequent task.

[0082] In this embodiment, the priority setting module 10 sets the priority between tasks. The project creation module 20 creates a project and selects a project type. The task creation module 30 creates a task and selects a task type; the calculation module 40 calculates the impact of the predecessor task on the current task and forms a planned date after the task is affected by the predecessor. The judgment module 50 judges whether the current task is affected and changes the planned date after being affected; the load generation module 60 generates the load of each associated resource. The detection module 70 detects the load of each resource and judges whether the load is overloaded; wherein the first sub-judgment unit 51 judges whether the current task is affected by the predecessor; the second sub-judgment unit 52 judges whether the current task is affected by the subtask; the third sub-judgment unit 53 judges whether the current task is affected by the parent task; the fourth sub-judgment unit 54 judges whether the current task is affected by the successor task. The early warning module 80 is used to issue an early warning prompt in the case of overload. Through the above method, it is achieved to improve the efficiency of enterprise resource management and communication and reduce the risks and problems caused by resources in the project.

[0083] The embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, Figure 1 Part or all of the steps in the advanced planning and scheduling method based on resource constraints described in the corresponding embodiment can also implement the present invention. Figure 3 The functions of the advanced planning and scheduling system based on resource constraints in the illustrated embodiment.

[0084] The computer-readable storage medium may be an internal storage unit of the advanced planning and scheduling system based on resource constraints described in the aforementioned embodiment, such as a hard disk or memory of the advanced planning and scheduling system based on resource constraints. The computer-readable storage medium may also be an external storage device of the advanced planning and scheduling system based on resource constraints, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc., equipped on the advanced planning and scheduling system based on resource constraints.

[0085] The embodiment of the present invention further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute part or all of the steps in the above method.

[0086] In various embodiments of the present application, the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0087] The above descriptions are only partial implementation modes of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or substitutions within the technical scope disclosed by the present invention, and these modifications or substitutions should be included in the protection scope of the present invention.

Claims

1. An advanced planning and scheduling method based on resource constraints, characterized in that: The steps include: Set the priority between tasks; the predecessor task is the first priority, the current task is the second priority, the subtask is the third priority, the parent task is the fourth priority, the successor task is the fifth priority, and the project is the sixth priority; Create a project and select the project type; Create a task and select the task type; Establish predecessor tasks for the current task as needed, calculate the impact of the predecessor tasks on the current task, and form a planned date for the task after being affected by the predecessor tasks; Determine whether the current task is affected by the predecessor, and change the planned date if it is affected by the predecessor, including: After the current task is affected by the predecessor, the change of the current task is restricted according to the execution status of the subtask. If there are predecessors, executed or completed subtasks, the planned start date of the current task cannot be postponed to after the planned start date of the subtask. Otherwise, the impact of the predecessor task on the current task will not be accepted and returned to the previous planned date. If the restriction check is passed, the change of the current task will affect the change of the planned date of the subtask according to the type of subtask; Determine whether the current task is affected by subtasks, and change the planned date if affected by subtasks, including: After the current task is affected by the subtask, the change of the current task is restricted according to the execution status of the parent task. If there is a predecessor, executed or completed parent task, the planned start date of the current task cannot be advanced to before the planned start date of the parent task. Otherwise, the impact of the predecessor task and subtask on the current task will not be accepted and returned to the previous planned date. If the restriction check is passed, the change of the current task will affect the change of the planned date of the parent task according to the type of the parent task; Determine whether the current task is affected by the parent task, and change the planned date if it is affected by the parent task, including: After the current task is affected by the parent task, the change of the current task is restricted according to the predecessor dependency relationship with the successor task. The executed or completed successor task will restrict the scheduled start and completion date of the current task to be postponed. Otherwise, the impact of the predecessor task, subtask and subsidiary task on the current task will not be accepted and the previous planned date will be returned. If the restriction check is passed, the change of the current task will affect the planned date change of its successor task according to the predecessor dependency relationship. Determine whether the current task is affected by the subsequent task, and change the planned date if it is affected by the subsequent task, including: After the current task is affected by the subsequent task, the change of the current task is restricted according to the type of project. The planned start date of the current task cannot be earlier than the planned start date of the sequential project, and the planned completion date cannot be later than the planned completion date of the reversed project. Detect the load of each resource and issue an early warning.

2. The advanced planning and scheduling method based on resource constraints as claimed in claim 1, characterized in that: In the Create Project, Select Project Type step: The item types include forward-order items and reverse-order items.

3. The advanced planning and scheduling method based on resource constraints as claimed in claim 1, characterized in that: When creating a task and selecting the task type: Fill in the planned start date, duration date and planned completion date according to different task types.

4. A high-level planning and scheduling system based on resource constraints, applied to the high-level planning and scheduling method based on resource constraints as claimed in claim 1, characterized in that: It includes priority setting module, project creation module, task creation module, calculation module, judgment module, load generation module, detection module and early warning module; The priority setting module is used to set the priority between tasks; The project creation module is used to create a project and select a project type; The task creation module is used to create tasks and select task types; The calculation module is used to calculate the impact of the predecessor task on the current task and form a planned date for the task after being affected by the predecessor, specifically including: After the current task is affected by the predecessor, the change of the current task is restricted according to the execution status of the subtask. If there are predecessors, executed or completed subtasks, the planned start date of the current task cannot be postponed to after the planned start date of the subtask. Otherwise, the impact of the predecessor task on the current task will not be accepted and returned to the previous planned date. If the restriction check is passed, the change of the current task will affect the change of the planned date of the subtask according to the type of subtask; The judgment module is used to judge whether the current task is affected and change the planned date if it is affected, specifically including: After the current task is affected by the subtask, the change of the current task is restricted according to the execution status of the parent task. If there is a predecessor, executed or completed parent task, the planned start date of the current task cannot be advanced to before the planned start date of the parent task. Otherwise, the impact of the predecessor task and subtask on the current task will not be accepted and returned to the previous planned date. If the restriction check is passed, the change of the current task will affect the change of the planned date of the parent task according to the type of the parent task; After the current task is affected by the parent task, the change of the current task is restricted according to the predecessor dependency relationship with the successor task. The executed or completed successor task will restrict the scheduled start and completion date of the current task to be postponed. Otherwise, the impact of the predecessor task, subtask and subsidiary task on the current task will not be accepted and the previous planned date will be returned. If the restriction check is passed, the change of the current task will affect the planned date change of its successor task according to the predecessor dependency relationship. After the current task is affected by the subsequent task, the change of the current task is restricted according to the type of project. The planned start date of the current task cannot be earlier than the planned start date of the sequential project, and the planned completion date cannot be later than the planned completion date of the reversed project. The load generation module is used to generate the load of each associated resource; The detection module is used to detect the load of each resource and determine whether the load is overloaded; The warning module is used to issue a warning prompt in the event of an overload condition.

5. The resource-constrained advanced planning and scheduling system according to claim 4, characterized in that: The judgment module includes a first sub-judgment unit, a second sub-judgment unit, a third sub-judgment unit and a fourth sub-judgment unit; The first sub-judgment unit is used to judge whether the current task is affected by the predecessor; The second sub-judgment unit is used to judge whether the current task is affected by the sub-task; The third sub-judgment unit is used to judge whether the current task is affected by the parent task; The fourth sub-judgment unit is used to judge whether the current task is affected by the subsequent task.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which includes program instructions. When the program instructions are executed by a processor, the processor executes the resource constraint-based advanced planning and scheduling method according to any one of claims 1 to 3.

Images