A method, device, electronic device and storage medium for generating a task package

Abstract

The present application provides a method, apparatus, electronic device, and storage medium for generating a task package. The method includes receiving a user's selection operation on the ship type of a project and the subprocess of the project on a task package generation interface, and displaying a task node interface; for each task node entry corresponding to a task node in the task node interface, according to the user's selection operation on the task node entry corresponding to the task node, displaying a plurality of task object entries corresponding to the data source type of the task node in a task source interface, in response to the user's selection operation on a first target control on the task package generation interface, determining the target task object of the task node according to the target task object selected by the user in the task source interface, and generating a task package for the task node according to the target task object of the task node and the preset task information of the task node.

Description

Technical Field

[0001] This application relates to the technical field of ship production management. Specifically, it relates to a method, device, electronic device, and storage medium for generating task packages. Background Art

[0002] As a complex systems engineering product, a ship involves numerous technical steps and processes in the full-process design. Due to the long ship design cycle and numerous design process steps, a lot of experienced technical personnel spend their time on management-related tasks such as plan formulation, plan arrangement, and plan tracking, and cannot fully devote their time and energy to the most valuable design technology part. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a method, device, electronic device, and storage medium for generating task packages, achieving the effect of being applicable to ship production management and assisting managers in making refined allocations for complex ship design processes.

[0004] In a first aspect, this application provides a method for generating a task package. The method includes receiving a user's selection operation on the ship type of a project and the sub-process of the project on the task package generation interface, and displaying a task node interface. The task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in this sub-process. For each task node entry corresponding to a task node in the task node interface, according to the user's selection operation on the task node entry corresponding to this task node, multiple task object entries corresponding to the data source type of this task node are displayed in the task source interface. In response to the user's selection operation on the first target control on the task package generation interface, according to the target task object entry selected by the user in the task source interface, the target task object of this task node is determined, and according to the target task object of this task node and the task information preset for this task node, a task package for this task node is generated.

[0005] Preferably, the project includes multiple majors, each major includes multiple main processes, each main process includes multiple sub-processes, each sub-process includes multiple task nodes, and each task node corresponds to a preset task information. The task nodes that need to generate task packages are determined in the following manner: Receive the user's selection operations on the ship type of the project and the target major of the project on the standard process interface, display the standard process interface, which at least includes the task node entries corresponding to each task node, and a first area corresponding to each task node. The first area is used to determine whether to enable the task package generation function of the task node, and the first area includes "Yes" and "No"; when the user edits the corresponding first editing area of the task node to "Yes", it is determined that the task node needs to generate a task package, and when the user edits the corresponding first editing area of the task node to "No", it is determined that the task node does not need to generate a task package.

[0006] Preferably, the standard process interface further includes a second editing area corresponding to each task node. The second editing area is used to determine the data source type of the task package of the task node. Multiple data source type names are pre-entered in the second editing area. The data source type of the task node is determined in the following manner: For each task node, according to the data source type name edited by the user in the second editing area corresponding to the task node, the data source type of the task node is determined.

[0007] Preferably, the task package distribution interface at least includes the task package status entries corresponding to each task node, a third editing area corresponding to each task node. The third editing area is used to edit the executing employee of the task node. All employee information is pre-entered in the third editing area and a fourth editing area corresponding to each task node. The fourth editing area is used to edit the work plan time of the task node. It also includes: Receive the user's selection operations on the ship type of the project and the target major of the project on the task package distribution interface, and display the task packages of all task nodes under the target major; For each task node with the task package status of pending assignment, in response to the user's selection operation on the second target control on the task package distribution interface, update the work plan time edited by the user in the fourth editing area corresponding to the task node to the task package of the task node, and send the updated task package to the terminal of the executing employee edited by the user in the third editing area corresponding to the task node.

[0008] Preferably, the employee information at least includes department, name, task volume, and task progress. The task package distribution interface further includes a fifth editing area, which is used to edit the department of the employee. It also includes: According to the department of the employee edited by the user in the fifth editing area, display the name, task volume, and task progress of the employees in the department in the first display area of the task package distribution interface.

[0009] Preferably, the task package distribution interface further includes a second display area and a task package name entry corresponding to each task node, and further includes: receiving a selection operation of the user on the target task package name entry in the task package distribution interface, and displaying a balance plan node in the second display area, where the balance plan node at least includes the completion time or completion status of other task nodes associated with the task object of this task node.

[0010] Preferably, the standard process interface further includes a first weight editing area corresponding to each main process, a second weight editing area corresponding to each sub-process, and a third weight editing area corresponding to each task node. The first weight editing area, the second weight editing area, and the third weight editing area are all used to edit weight values. The process node dashboard interface at least includes a main process entry corresponding to each main process, a sub-process entry corresponding to each sub-process, a task node entry corresponding to each task node, and a third display area, and further includes: calculating the task completion rate of each task node according to the number of completed task packages and the total number of task packages of each task node; in response to the user's selection operation on the target sub-process entry in the process node dashboard interface, calculating the task progress value of this sub-process according to the task completion rate of each task node corresponding to this sub-process and the weight value edited by the user in the corresponding third weight editing area in the standard process interface.

[0011] In a second aspect, the present application provides a task package generation device, where the device includes:

[0012] A receiving module, configured to receive a selection operation of the user on the ship type of the project and the sub-process of the project in the task package generation interface, and display a task node interface, where the task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in this sub-process;

[0013] A task package generation module, configured to, for each task node entry corresponding to each task node in the task node interface, display multiple task object entries corresponding to the data source type of this task node in the task source interface according to the user's selection operation on the task node entry corresponding to this task node, in response to the user's selection operation on the first target control in the task package generation interface, determine the target task object of this task node according to the target task object selected by the user in the task source interface, and generate a task package for this task node according to the target task object of this task node and the preset task information of this task node.

[0014] In a third aspect, the present application further provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. When the machine-readable instructions are executed by the processor, the steps of the task package generation method as described above are executed.

[0015] Fourthly, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it executes the steps of the method for generating a task package as described above.

[0016] The method, device, electronic device and storage medium for generating a task package provided by the present application receive the selection operations of the ship type of a project and the sub-process of the project by the user on the task package generation interface, and display the task node interface. The task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in the sub-process. For each task node entry corresponding to a task node in the task node interface, according to the selection operation of the user on the task node entry corresponding to the task node, multiple task object entries corresponding to the data source type of the task node are displayed in the task source interface. In response to the selection operation of the user on the first target control on the task package generation interface, according to the target task object entry selected by the user in the task source interface, the target task object of the task node is determined. According to the target task object of the task node and the preset task information of the task node, a task package of the task node is generated. It can generate task packages for the task nodes of the ship in a refined manner, with a simple process, and does not require managers to spend too much time and experience on management work such as task planning and arrangement, reducing the work burden of managers.

[0017] To make the above objects, features and advantages of the present application more obvious and understandable, the following specifically gives preferred embodiments and, in conjunction with the accompanying drawings, makes the following detailed description. Description of the Drawings

[0018] To more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required to be used in the embodiments. It should be understood that the following drawings only show some embodiments of the present application and should not be regarded as limiting the scope. For those of ordinary skill in the art, other relevant drawings can be obtained based on these drawings without creative efforts.

[0019] Figure 1 It is a flowchart of a method for generating a task package provided by an embodiment of the present application;

[0020] Figure 2 It is a flowchart of the steps for determining the task nodes that need to generate task packages provided by an embodiment of the present application;

[0021] Figure 3 It is a flowchart of a method for distributing task packages provided by an embodiment of the present application;

[0022] Figure 4 It is a flowchart of the steps for calculating the task progress value provided by an embodiment of the present application;

[0023] Figure 5 A flowchart of ship full - professional design management provided by an embodiment of the present application;

[0024] Figure 6 A schematic diagram of a task package generation interface provided by an embodiment of the present application;

[0025] Figure 7 A schematic diagram of a task package distribution interface provided by an embodiment of the present application;

[0026] Figure 8 A schematic structural diagram of a task package generation device provided by an embodiment of the present application;

[0027] Figure 9 A schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0028] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and illustrated herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the present application claimed, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, every other embodiment obtained by those skilled in the art without creative efforts belongs to the scope of protection of the present application.

[0029] First, the applicable application scenarios of the present application are introduced. The present application can be applied to ship standardization process management.

[0030] As a complex system engineering product, a ship involves numerous technical steps and processes in the full - process design. There are logical relationship constraints and process outputs between each process step, and the outputs of each process node will serve as the input conditions for subsequent work. Ship designers often carry out design work based on technical documents, operation manuals, standard specifications, review manuals, etc. within the profession and complete relevant work content within the planned period. At the same time, to meet the requirements of design plan management, designers need to regularly submit their completion status in the form of Excel sheets, weekly reports, monthly reports, etc., and the superior supervisor / group leader will statistically summarize to form the completion status of the entire project.

[0031] Meanwhile, considering the characteristics of long ship design cycle and numerous design process steps, there has been a lack of a mature solution to meet the software platform for scheduling based on standardized processes so far. This has caused many experienced technicians to spend time on management-related tasks such as plan formulation, scheduling, and plan tracking, and they cannot fully devote their time and energy to the most valuable design technology part. Although there is no shortage of plan management software on the market, most of the relevant management software can only meet general needs and cannot be implemented according to the characteristics of ship products. Therefore, there is an urgent need for a management system that fits the standardized design business process of ships to carry out refined management of design tasks.

[0032] Based on this, the embodiment of the present application provides a ship digital management platform. Based on the design business of ship products, the ship digital management platform proposes a standard process node management method, and the scope includes all specialties in ship design (structure, piping, air duct, iron outfitting, electric, interior fitting). Taking the production design of piping as an example, first, sort out the full-process work tasks of the piping specialty. Based on the concept of standardized operation, gradually divide the work tasks of each specialty from coarse to fine into process nodes, and clarify the process node inputs, business processes, process node outputs, participating roles, man-hour quotas, corresponding work manuals, technical materials, etc. of each process node, and construct a professional standard process management system. Based on this system, a standard work guidance and technical reference can be provided for all designers, enabling designers to find all the operation guides, technical materials, and man-hour quotas required to complete the work based on the standard process nodes, and improving the standardized work efficiency.

[0033] On the basis of the professional standard process management system, a design task package management method based on standard process nodes is further proposed. This method standardly divides the work tasks of the project according to the standard process nodes, forming work task packages that can be assigned to individual designers. These task packages are combined with the standard process rhythm system and come with all the management information and business information of this process rhythm point, including process node inputs, business processes, process node outputs, participating roles, man-hour quotas, corresponding work manuals, technical materials, plan information, etc. After receiving the task package, designers can carry out their work based on the data attached to the task package and give daily feedback on the task package according to the work progress. This feedback will form the overall progress of the project through bottom-up convolution in combination with the weights of the process nodes. By this method, the additional man-hour reporting and feedback of designers are reduced, enabling each designer to focus on the design work itself.

[0034] Here, based on the concept of standardized operation, each specialty in the ship design process is gradually decomposed from top to bottom and divided into three levels, namely the main process, sub-process, and task node. The corresponding weight needs to be determined for each level, and a unique number is configured.

[0035] The ship digital management platform here at least includes a project management system, a knowledge management system, and a design system. Among them, the project management system integrates various target status data and change data of ship drawings through interfaces, and better controls the generation of task packages; the knowledge management system integrates various standard technical materials, operation manuals, etc., to provide data support for task information; the design system integrates material quantity data and modeling status data to provide data support for the progress feedback of task packages.

[0036] The ship digital management platform at least includes a public basic module column, an engineering project definition column, a design task package management column, etc. The engineering project definition column at least includes a ship number list sub-column, a partition and section configuration sub-column, a ship number section element sub-column, a standard process beat sub-column, a standard process beat details sub-column, a drawing list definition sub-column, a relationship basic definition sub-column, a structure basic definition sub-column, an electrical and outfitting basic definition sub-column, etc. The design task package management column at least includes a task package configuration sub-column, a personnel information management sub-column, a whole ship area information sub-column, a procurement project list sub-column, a comprehensive layout sub-column, a task package generation sub-column, and a task package distribution sub-column.

[0037] The project includes multiple specialties, each specialty includes multiple main processes, each main process includes multiple sub-processes, each sub-process includes multiple task nodes, and each task node corresponds to a preset task information.

[0038] As Figure 5 shown, Figure 5It is a flowchart of the full - professional design management of a ship provided by an embodiment of this application. Taking a passenger ship project as an example, first, professional process nodes need to be created. In the standard process interface corresponding to the standard process beat sub - column, select the ship type as a cruise ship and the specialty as piping system respectively for query. All main processes, sub - processes, and task nodes under the piping system will be displayed in the standard process interface. For example, the specialties under a cruise ship project include structure, piping system, air duct, iron outfitting, electric, and interior decoration. The piping system includes main processes P1 - Design Preparation, P3 - Modeling, P4 - Drawing Issue, P5 - Fitting Out, P6 - Design Summary. The main process P1 - Design Preparation includes sub - processes P1 - 1 Specification Digest, P1 - 2 Design Planning, P1 - 3 Technical Agreement, P1 - 4 General Arrangement. Among them, the sub - process P1 - 1 Specification Digest includes task nodes P1 - 1 - 1 Specification Decomposition, P1 - 1 - 2 Specification Digest. Here, the process nodes corresponding to each ship type and ship number are preset. Designers need to configure weights for each main process, sub - process, and task node according to actual needs. And configure the data source type of each task node and whether to enable the function of generating task packages. The definition of process beat is the basis of task packages. Different management granularities have different degrees of fineness of process beats, and the task package beats to be generated can be customized according to the business needs of professional rooms. That is, a project process can be newly created, imported, or modified for the selected project process in the standard process interface to meet actual needs.

[0039] Next, it is necessary to further define task information such as business guidance and operation guidance for each task node in the standard process beat details sub - column. Specifically, the task information includes node input conditions, task processes, input standards, technical documents, guidance documents, etc., which are used to provide technical references for the designers who execute this task node.

[0040] Taking the task node P3 - 1 - 1 Modeling According to Schematic Diagram as an example, in the details configuration interface corresponding to the standard process beat details sub - column, the input conditions of this task node can be configured as "1. Relevant schematic diagrams and layout diagrams, etc. 2. Corresponding equipment data 3. Other professional backgrounds 4. Basic component library 5. Piping system specification 6. S3D software path configuration completed". The business process of this task node is configured as "1. Start the modeling work of the piping system in the area according to the schematic diagram 2. Check the size and position of the equipment interface according to the equipment data 3. Check for interference, adjust, modify, and eliminate interference 4. Adjust the pipes to facilitate the addition of brackets later". The output standard / requirement of this task node is configured as "Pipeline model". The participating roles of this task node are configured as "Designer", etc. and saved. And configure the document links corresponding to this task node, such as operation manuals, reports, etc. Here, the operation manuals and reports can be selected from the knowledge management system. Similarly, the detailed information corresponding to this task node can be preset, and managers can modify it or import it by themselves.

[0041] Before generating the task package, it is also necessary to configure the personnel information and the whole-ship area information. Through the personnel information management interface corresponding to the personnel information management sub-column, the executing personnel participating in this project can be configured. It can be understood that all organizational structures of the design department are preset in the system. Exemplarily, the design department includes multiple project teams. For example, Design Department 1 includes multiple project teams such as IT, Machinery Installation Room, Electrical Installation Room, Air Conditioning Refrigeration Room, Structure Room, Shipfitting Room, and Hotel Engineering Room. Among them, the Electrical Installation Room project team includes Production Design Group 1, Production Design Group 2, Production Design Group 3, Detailed Design, and Cruise Supervisor. Production Design Group 1 includes Team Leader A, Team Member B, Team Member C, etc. Managers can select the required personnel based on the preset organizational structure and display the selected employee information in the display area of the personnel information management interface in the form of a list.

[0042] At the same time, it is also necessary to configure the whole-ship area information. Through the whole-ship area information interface corresponding to the whole-ship area information sub-column, the corresponding area division table can be queried according to the ship type and ship number, and a custom area division table can also be imported. The area division table here includes at least large areas, sub-areas, general sections, sections, units, and balance plan nodes, etc. The balance plan nodes here are used to indicate the planned completion time.

[0043] In addition, the procurement project list and the general layout can also be configured. The configuration steps here are similar to those of the whole-ship area information or personnel information configuration steps and will not be elaborated.

[0044] After configuring the basic information of the project, the task package can be generated.

[0045] Please refer to Figure 1 and Figure 6 , Figure 1 which is the flowchart of a method for generating a task package provided by an embodiment of the present application, Figure 6 and Figure 1 which is the schematic diagram of a task package generation interface provided by an embodiment of the present application. As shown in

[0046] S101. Receive the selection operation of the ship type of the project and the sub-process of the project by the user on the task package generation interface, and display the task node interface. The task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in this sub-process.

[0047] In this step, first, in the task package generation interface corresponding to the task package generation sub-column, select the corresponding ship type, ship number, specialty, main process, and sub-process according to the project. After querying, the task node interface will display the task node entries corresponding to all task nodes that need to generate task packages under this sub-process.

[0048] S102. For each task node entry corresponding to a task node in the task node interface, according to the user's selection operation on the task node entry corresponding to the task node, display multiple task object entries corresponding to the data source type of the task node in the task source interface. In response to the user's selection operation on the first target control in the task package generation interface, determine the target task object of the task node according to the target task object entry selected by the user in the task source interface. Generate a task package for the task node according to the target task object of the task node and the preset task information of the task node.

[0049] In this step, after the user clicks on the task node entry corresponding to a certain task node, multiple task object entries will be displayed in the task source interface. Here, the task object entries are determined according to the data type of the task node. Exemplarily, if the data source type corresponding to a certain task node is a region, a pre-configured region division table will be displayed in the task source interface. If the data source type corresponding to a certain task node is a procurement project list, a pre-configured procurement project list corresponding to the project will be displayed in the task source interface. As Figure 6 shown, the arrow marks in the figure are used for paging. Among them, the hollow circle mark indicates not selected, while the solid circle mark indicates selected.

[0050] Here, the task object indicates the object to be executed by the task node, such as a certain region, a certain unit of a ship, or a certain procurement project list.

[0051] The task package here includes the task object and task information of the task node. The task information includes pre-configured management information and business information such as the task node name, process node input of the task node, business process, process node output, participating roles, man-hour quota, corresponding work manual, technical materials, plan information, etc. The task package generation method provided by the embodiments of the present application enables managers to only need to pre-select the process nodes, personnel information, whole-ship area information, procurement project list, and general arrangement of the project in the platform for configuration, and then configure the task object of each task node, and then a task package corresponding to the task node can be generated. The operation is simple and efficient. Compared with the prior art in which tasks are allocated manually, it can reduce the task planning time of managers.

[0052] Please refer to Figure 2 , Figure 2 which is a flowchart of the steps for determining the task nodes that need to generate task packages provided by the embodiments of the present application. As Figure 2 shown, multiple task nodes that need to generate task packages are determined in the following manner:

[0053] S201. Receive the user's selection operations for the ship type of the project and the target specialty of the project on the standard process interface, and display the standard process interface. The standard process interface includes at least task node entries corresponding to each task node, and a first area corresponding to each task node. The first area is used to determine whether to enable the task package generation function for the task node, and the first area includes "Yes" and "No".

[0054] S202. When the user edits the first editing area corresponding to the task node to "Yes", it is determined that the task node needs to generate a task package. When the user edits the first editing area corresponding to the task node to "No", it is determined that the task node does not need to generate a task package.

[0055] Before creating a task package, when creating a professional process node, the first area corresponding to the task node can be configured through the standard process interface. Edit the first area corresponding to the task node that needs to generate a task package to "Yes".

[0056] Specifically, the standard process interface further includes a second editing area corresponding to each task node. The second editing area is used to determine the data source type of the task package of the task node. Multiple data source type names are pre-entered in the second editing area. The data source type of the task node is determined through the following method;

[0057] For each task node, determine the data source type of the task node according to the data source type name edited by the user in the second editing area corresponding to the task node.

[0058] The data source types here include regions, procurement project lists, POR lists, equipment drawing lists, integrated layout topics, etc.

[0059] The configuration of the data source type needs to consider the specific characteristics of different types of projects, such as the regional division of the project, drawing catalogs, modeling regions, equipment lists, etc.

[0060] Please refer to Figure 3 and 7 , Figure 3 is a flowchart of a method for issuing task packages provided by an embodiment of the present application, Figure 7 is a schematic diagram of a task package issuing interface provided by an embodiment of the present application. As shown in Figure 3 , the task package issuing interface includes at least task package status entries corresponding to each task node, a third editing area corresponding to each task node. The third editing area is used to edit the executing employees of the task node. All employee information of all employees is pre-entered in the third editing area, and a fourth editing area corresponding to each task node. The fourth editing area is used to edit the work plan time of the task node, and further includes:

[0061] S301. Receive the user's selection operations on the ship type of the project and the target specialty of the project at the task package distribution interface, and display the task packages of all task nodes under the target specialty.

[0062] S302. For each task node with the task package status being the to-be-assigned status, in response to the user's selection operation on the second target control at the task package distribution interface, update the work plan time edited by the user in the fourth editing area corresponding to this task node to the task package of this task node, and send the updated task package to the terminal of the executing employee edited by the user in the third editing area corresponding to this task node.

[0063] Through the task package distribution interface, task packages can be dispatched. The task package status can be to-be-assigned, in progress, dispatched, postponed, etc. For each task node, the executing employee can be edited in the corresponding third editing area. This executing employee is used to execute the work of this task node, and the work plan time such as the planned start time, planned completion time, man-hours, etc. of the task node can be edited in the corresponding fourth editing area.

[0064] The updated task package is sent to the terminal of the corresponding executing employee. The executing employee can also view the task packages of all task nodes assigned to himself in the personal task package viewing interface. The completion status of the task packages of each task node can also be fed back daily, such as the completion time, daily man-hours, completion percentage, etc. The task information in the task package, such as the operation manual, etc., can also be viewed.

[0065] In an embodiment of the present application, the dispatching administrator can view the task packages generated by himself and perform dispatching operations. Add personnel and time information to the task packages generated in the previous step on this interface. Two modes are provided here. In Mode 1, multiple data can be selected and exported to Excel, and after editing in Excel, it can be imported again; in Mode 2, the selected data can be directly edited on the page. Select the department / group to be dispatched according to the organizational structure, and after clicking on the name of the employee, the responsible person can be directly filled in. After the planned start time, planned completion, and man-hour quota data are all filled in completely, click the button to dispatch the task package to complete the task package dispatch.

[0066] Specifically, the professional supervisor selects the sub - process for which the task package is to be generated on the task package generation interface and selects the corresponding data sources (modeling area, partition, section, drawing list, etc.). The platform will generate the corresponding number of task packages according to the selected data. At this time, the task package only contains the relevant information of the process nodes. Next, on the task package distribution interface, the supervisor needs to assign information such as the responsible person, planned start time, planned completion time, man - hours, etc. for the generated task package. The platform will provide the supervisor with corresponding auxiliary task assignment functions, such as the overall planned node information of the area where the task is located, the load situation of the current task package of the personnel to be assigned, and the function of obtaining the drawing plan information with one key. After filling in and confirming the relevant information, the operation of distributing the task package is executed. This task package will be pushed to the corresponding designer, and an instant message will be sent in the office management system (OA) to remind the designer.

[0067] The designer logs in to the personal task package viewing interface. After selecting the corresponding project and specialty, the designer can view their personal task packages. The information included in the task package includes: task package name, the task node it belongs to, the area it belongs to, task package status, planned start time, planned completion time, man - hour quota, actual start time, actual completion time, completion percentage, actual man - hours already incurred, etc. In addition to the task - related planned information, the designer can view the standardized operation technical guidance corresponding to this task package by clicking on the task package name, such as input conditions, business processes, output standards, corresponding work manuals, technical materials, etc., and can carry out work based on the relevant guidance. For the task package of the already dispatched task node, information including the responsible person, planned start time, planned completion time, and man - hour quota can be changed. At the same time, if additional personnel are needed to cooperate in completing the same task package during the execution of the task package, the function of adding personnel can be used for operation on this interface.

[0068] Furthermore, the employee information includes at least the department, name, task volume, and task progress. The task package distribution interface also includes a fifth editing area, which is used to edit the department of the employee, and also includes:

[0069] According to the department of the employee edited by the user in the fifth editing area, the names, task volumes, and task progress of the employees in this department are displayed in the first display area of the task package distribution interface.

[0070] When distributing the task package, information such as the names, task volumes, and task progress of the employees will also be displayed on the task distribution interface to assist the management in distributing the task package.

[0071] The task package distribution interface also includes a second display area and the task package name entries corresponding to each task node, and also includes:

[0072] Receive the user's selection operation on the target task package name entry in the task package distribution interface, and display the balance plan nodes in the second display area. The balance plan nodes at least include the completion time or completion status of other task nodes associated with the task object of this task node.

[0073] The balance plan nodes of the task nodes can also be displayed on the task package distribution interface to assist the management personnel in allocating task packages and determining the work plan time of the task nodes.

[0074] In an embodiment of the present application, the designer feedbacks the execution situation of the personal task package according to the actual work situation. The feedback method is daily filling, that is, filling in the actual working hours and actual completion percentage that occurred on the day of a certain task package every day. The design task package management system will record the feedback records of all task packages, and form different dimension dashboards of the project by processing the feedback working hour data, mainly including three dimensions, namely, the process node dashboard, the personnel load dashboard, and the regional progress dashboard. The process rhythm dashboard is used to display the completion situation of all task packages under different process rhythms of a certain specialty; the personnel load dashboard is used to display the work load and execution situation of personnel under different departments and groups from the dimension of the organizational structure; the regional progress dashboard is used to display the execution situation of task packages in different regions of the whole ship.

[0075] Further, as Figure 4 shown, it is a flowchart of the calculation steps of a task progress value provided by the embodiment of the present application. The standard process interface also includes a first weight editing area corresponding to each main process, a second weight editing area corresponding to each sub-process, and a third weight editing area corresponding to each task node. The first weight editing area, the second weight editing area, and the third weight editing area are all used to edit weight values. The process node dashboard interface at least includes a main process entry corresponding to each main process, a sub-process entry corresponding to each sub-process, a task node entry corresponding to each task node, and a third display area, and further includes:

[0076] S401. Calculate the task completion rate of each task node according to the number of completed task packages and the total number of task packages of each task node.

[0077] S402. Respond to the user's selection operation on the target sub-process entry in the process node dashboard interface, and calculate the task progress value of this sub-process according to the task completion rate of each task node corresponding to this sub-process and the weight value edited by the user in the corresponding third weight editing area in the standard process interface.

[0078] Here, the completion status of task packages of different process nodes is displayed in the dimension of process nodes. The task completion rate indicates the completion status of the task package under this node. The task progress value is the progress of the process node in the entire major calculated based on its own weight. Click the main process, sub-process, or task node to view the completion status of the node.

[0079] It also includes the regional progress dashboard interface and the personnel load dashboard interface. In the personnel load dashboard interface, managers can select the ship number, ship type and organizational structure to view the employee information and load status of all employees under the selected organizational structure. The employee information here includes at least the employee number, name, department and section. The load status includes at least the number of unexpired task packages, the number of due but unstarted task packages, the number of task packages completed ahead of schedule, the number of task packages completed on schedule, the number of delayed task packages, the number of ongoing task packages, the number of assigned tasks, the number of custom tasks and the completion rate. The organizational structure here can be displayed in a tree structure, which is used to select the personnel you want to view.

[0080] Here you can filter employees by planned date. The staff load dashboard interface also includes a chart area, which displays the load of the design department or section in the form of a chart.

[0081] The regional progress dashboard interface displays the completion status of the number of task packages from the perspective of ship area division in the form of a chart. This includes the number of completed task packages, the number of ongoing task packages, and the number of unstarted task packages corresponding to each area. Different colors are used to distinguish the corresponding logos of the number of completed task packages, the number of ongoing task packages, and the number of unstarted task packages. This application is based on the full professional design business of ships. Through the sorting, analysis, and evaluation of the full professional design business process, a set of standardized business processes have been formed. Based on the standard process, a complete set of task package management processes, data architecture, software design methods, etc. have been established to solve the problems of difficult progress tracking and business management in complex design business processes. At the same time, a standard operating guidance system for the execution of task packages has been established to provide users with a faster and more efficient task execution experience.

[0082] Among them, the following features are included:

[0083] (I) Business process standardization. In view of the complex ship design process, a set of standard process beats has been established with the concept of standardized operations to make the design business process more standardized and efficient. At the same time, multi-dimensional guidance methods such as input, processing, and output are provided for each process beat point, so that users can quickly obtain the technical essentials of the beat and facilitate their work.

[0084] (2) Establish a process rhythm business guidance system. Based on the basic information of each process rhythm point, further explore business applications, establish a business guidance system for each rhythm point, including review manuals, technical materials (specifications, standards, etc.), and ensure scalability. Provide users with standard, unified, and standardized technical document materials, reducing efficiency losses caused by inconsistent document versions and technical data differences.

[0085] (3) Push in the form of task packages. Based on the standardization of business processes and the business guidance system, the concept of task packages is innovatively proposed. The task package aims to provide users with more comprehensive, richer, and more perfect information. On the basis of basic plan information, the business guidance system corresponding to each rhythm point will be pushed to users, enabling designers to obtain accurate and up-to-date document materials at any time.

[0086] (4) Unify business data sources. The design task package management system proposed in the present invention integrates the underlying data sources. In terms of the project management system, various drawing catalog status data and change data are integrated through interfaces to better control the generation of task packages; in terms of the knowledge management system, various standard technical materials, operation manuals, etc. are integrated to ensure version consistency; in terms of the design platform, quantity data and modeling status data are integrated to support the progress feedback of task packages.

[0087] Based on the same inventive concept, an embodiment of the present application also provides a task package generation device corresponding to the task package generation method. Since the principle of solving problems by the device in the embodiment of the present application is similar to the above-mentioned task package generation method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be elaborated.

[0088] Please refer to Figure 8 , Figure 8 , which is a schematic structural diagram of a task package generation device provided by an embodiment of the present application. As shown in Figure 8 , the task package generation device 800 includes:

[0089] A first receiving module 810, configured to receive a user's selection operation of the ship type of the project and the sub-process of the project on the task package generation interface, and display a task node interface, where the task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in the sub-process;

[0090] The task package generation module 820 is configured to, for each task node entry corresponding to a task node in the task node interface, display multiple task object entries corresponding to the data source type of the task node in the task source interface according to the user's selection operation on the task node entry corresponding to the task node. In response to the user's selection operation on the first target control in the task package generation interface, determine the target task object of the task node according to the target task object entry selected by the user in the task source interface, and generate a task package for the task node according to the target task object of the task node and the task information preset for the task node.

[0091] In a preferred embodiment, a project includes multiple specialties, each specialty includes multiple main processes, each main process includes multiple sub-processes, each sub-process includes multiple task nodes, each task node corresponds to a preset task information, and further includes a second receiving module for determining each task node that needs to generate a task package in the following manner: receiving the user's selection operations on the ship type of the project and the target specialty of the project in the standard process interface, and displaying the standard process interface, which at least includes the task node entry corresponding to each task node and a first area corresponding to each task node, where the first area is used to determine whether to enable the task package generation function of the task node, and the first area includes "yes" and "no"; when the user edits the first editing area corresponding to the task node to be "yes", it is determined that the task node needs to generate a task package, and when the user edits the first editing area corresponding to the task node to be "no", it is determined that the task node does not need to generate a task package.

[0092] In a preferred embodiment, the standard process interface further includes a second editing area corresponding to each task node, where the second editing area is used to determine the data source type of the task package of the task node, and multiple data source type names are pre-entered in the second editing area. It further includes a determination module for determining the data source type of the task node in the following manner: for each task node, determine the data source type of the task node according to the data source type name edited by the user in the second editing area corresponding to the task node.

[0093] In a preferred embodiment, the task package distribution interface at least includes task package status entries corresponding to each task node, a third editing area corresponding to each task node for editing the executing employee of the task node, all employee information of all employees is pre - entered in the third editing area, and a fourth editing area corresponding to each task node for editing the work plan time of the task node. It further includes a third receiving module for receiving the user's selection operations on the ship type of the project and the target specialty of the project on the task package distribution interface, and displaying the task packages of all task nodes under the target specialty; for each task node with the task package status being the to - be - dispatched state, in response to the user's selection operation on the second target control on the task package distribution interface, the work plan time edited by the user in the fourth editing area corresponding to this task node is updated to the task package of this task node, and the updated task package is sent to the terminal of the executing employee edited by the user in the third editing area corresponding to this task node.

[0094] In a preferred embodiment, the employee information at least includes department, name, task volume, and task progress. The task package distribution interface further includes a fifth editing area for editing the department of the employee, and a fourth receiving module for displaying the name, task volume, and task progress of the employees in this department in the first display area of the task package distribution interface according to the department of the employee edited by the user in the fifth editing area.

[0095] In a preferred embodiment, the task package distribution interface further includes a second display area and task package name entries corresponding to each task node, and a fifth receiving module for receiving the user's selection operation on the target task package name entry on the task package distribution interface, and displaying balance plan nodes in the second display area. The balance plan nodes at least include the completion time or completion status of other task nodes associated with the task object of this task node.

[0096] In a preferred embodiment, the standard process interface further includes a first weight editing area corresponding to each main process, a second weight editing area corresponding to each sub - process, and a third weight editing area corresponding to each task node. The first weight editing area, the second weight editing area, and the third weight editing area are all used for editing weight values. The process node dashboard interface at least includes main process entries corresponding to each main process, sub - process entries corresponding to each sub - process, task node entries corresponding to each task node, and a third display area. It further includes an analysis module for calculating the task completion rate of each task node according to the number of completed task packages and the total number of task packages of each task node; in response to the user's selection operation on the target sub - process entry on the process node dashboard interface, calculating the task progress value of this sub - process according to the task completion rate of each task node corresponding to this sub - process and the weight value edited by the user in the corresponding third weight editing area in the standard process interface.

[0097] Please refer to Figure 9 , Figure 9 , which is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As Figure 9 shown in

[0098] The memory 920 stores machine-readable instructions executable by the processor 910. When the electronic device 900 runs, the processor 910 communicates with the memory 920 through the bus 930. When the machine-readable instructions are executed by the processor 910, the steps of the method for generating a task package in the above embodiment can be executed. For specific implementation manners, reference can be made to the method embodiment, which will not be elaborated herein.

[0099] An embodiment of the present application further provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is run by a processor, the steps of the method for generating a task package in the above embodiment can be executed. For specific implementation manners, reference can be made to the method embodiment, which will not be elaborated herein.

[0100] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, which will not be elaborated herein.

[0101] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For another example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some communication interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0103] In addition, in each embodiment of the present application, the functional units can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0104] When the above-mentioned functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of this application, in essence, or the part that contributes to the prior art or part of this technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media that can store program codes such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs.

[0105] Finally, it should be noted that: the above-mentioned embodiments are only specific implementation manners of this application, used to illustrate the technical solutions of this application, rather than limiting it. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: any person skilled in the art within the technical scope disclosed in this application can still modify the technical solutions recorded in the foregoing embodiments, or can easily think of changes, or perform equivalent replacements for some of the technical features; and these modifications, changes, or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

1. A method for generating a task package, characterized in that, The method includes: Receiving a user's selection operation on the ship type of the project and the sub-process of the project in the task package generation interface, and displaying a task node interface, where the task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in the sub-process; For each task node entry corresponding to a task node in the task node interface, according to the user's selection operation on the task node entry corresponding to the task node, displaying multiple task object entries corresponding to the data source type of the task node in the task source interface, responding to the user's selection operation on the first target control in the task package generation interface, determining the target task object of the task node according to the target task object entry selected by the user in the task source interface, and generating a task package for the task node according to the target task object of the task node and the task information preset for the task node; The project includes multiple specialties, each specialty includes multiple main processes, each main process includes multiple sub-processes, each sub-process includes multiple task nodes, and each task node corresponds to a preset task information. The task nodes that need to generate task packages are determined in the following way: Receiving a user's selection operation on the ship type of the project and the target specialty of the project in the standard process interface, and displaying the standard process interface, where the standard process interface at least includes task node entries corresponding to each task node, and a first area corresponding to each task node, and the first area is used to determine whether to enable the task package generation function of the task node, and the first area includes "Yes" and "No"; When the user edits the first editing area corresponding to the task node to be "Yes", it is determined that the task node needs to generate a task package. When the user edits the first editing area corresponding to the task node to be "No", it is determined that the task node does not need to generate a task package; The standard process interface further includes a second editing area corresponding to each task node, and the second editing area is used to determine the data source type of the task package of the task node. Multiple data source type names are pre-entered in the second editing area. The data source type of the task node is determined in the following way: For each task node, determining the data source type of the task node according to the data source type name edited by the user in the second editing area corresponding to the task node; The task package distribution interface at least includes task package status entries corresponding to each task node, a third editing area corresponding to each task node, and the third editing area is used to edit the executing employee of the task node. All employee information of all employees and a fourth editing area corresponding to each task node are pre-entered in the third editing area, and the fourth editing area is used to edit the work plan time of the task node. It further includes: Receiving a user's selection operation on the ship type of the project and the target specialty of the project in the task package distribution interface, and displaying the task packages of all task nodes under the target specialty; For each task node whose task package status is to be assigned, in response to the user's selection operation on the second target control in the task package distribution interface, update the work plan time edited by the user in the fourth editing area corresponding to this task node to the task package of this task node, and send the updated task package to the terminal of the executing employee edited by the user in the third editing area corresponding to this task node; The employee information at least includes department, name, task volume, and task progress. The task package distribution interface further includes a fifth editing area for editing the department of the employee, and further includes: According to the department of the employee edited by the user in the fifth editing area, display the names, task volumes, and task progress of the employees in this department in the first display area of the task package distribution interface.

2. The method according to claim 1, wherein The task package distribution interface further includes a second display area and a task package name entry corresponding to each task node, and further includes: Receive the user's selection operation on the target task package name entry in the task package distribution interface, and display a balance plan node in the second display area. The balance plan node at least includes the completion time or completion status of other task nodes associated with the task object of this task node.

3. The method according to claim 2, wherein The standard process interface further includes a first weight editing area corresponding to each main process, a second weight editing area corresponding to each sub-process, and a third weight editing area corresponding to each task node. The first weight editing area, the second weight editing area, and the third weight editing area are all used to edit weight values. The process node dashboard interface at least includes a main process entry corresponding to each main process, a sub-process entry corresponding to each sub-process, a task node entry corresponding to each task node, and a third display area, and further includes: Calculate the task completion rate of each task node based on the number of completed task packages and the total number of task packages of each task node. In response to the user's selection operation on the target sub-process entry in the process node dashboard interface, calculate the task progress value of this sub-process according to the task completion rate of each task node corresponding to this sub-process and the weight value edited by the user in the corresponding third weight editing area in the standard process interface.

4. An apparatus for generating a task package, characterized in that, Applicable to the task package generation method described in claim 1, the device includes: A receiving module for receiving the user's selection operations on the ship type of the project and the sub-process of the project in the task package generation interface, and displaying a task node interface. The task node interface includes task node entries corresponding to multiple task nodes that need to generate task packages in this sub-process. A task package generation module is configured to, for each task node entry corresponding to a task node in the task node interface, display a plurality of task object entries corresponding to the data source type of the task node in the task source interface according to the selection operation of the user on the task node entry corresponding to the task node. In response to the selection operation of the user on the first target control in the task package generation interface, determine the target task object of the task node according to the target task object entry selected by the user in the task source interface, and generate a task package for the task node according to the target task object of the task node and the preset task information of the task node.

5. An electronic device, characterized in that, Comprising: A processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. The processor executes the machine-readable instructions to perform the steps of the task package generation method according to any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium. When the computer program is run by the processor, it performs the steps of the task package generation method according to any one of claims 1 to 3.

Images