CN110766375A - Work platform task construction system and construction method - Google Patents
Work platform task construction system and construction method Download PDFInfo
- Publication number
- CN110766375A CN110766375A CN201910880679.0A CN201910880679A CN110766375A CN 110766375 A CN110766375 A CN 110766375A CN 201910880679 A CN201910880679 A CN 201910880679A CN 110766375 A CN110766375 A CN 110766375A
- Authority
- CN
- China
- Prior art keywords
- task
- project
- group
- module
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06313—Resource planning in a project environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
Abstract
The invention discloses a work platform task construction system and a construction system thereof, wherein the system comprises at least one client, at least one server and at least one storage server; a client: the system is used for a user to carry out task construction operation and comprises a task group definition module, a task type definition module, a project creation module and a task release module; the server side: the system is used for executing task description and task construction and comprises a client communication module, a storage communication module, a data description module, a project task system generation module and an entity generation module; a storage server: for storing task hierarchy metadata. Aiming at the service characteristics of the working platform, the invention adds the task mode to the task type, realizes platform-based operations such as the release, the split and the distribution of the task, and can be directly applied to the working platform.
Description
Technical Field
The invention belongs to the technical field of information management of engineering projects, and particularly relates to a work platform task construction system and a construction method.
Background
The engineering project is generally decomposed into a plurality of subtasks layer by layer according to the number scale of people participating in and the construction scale, and a task organization form with a tree structure is formed. In an information management system of engineering projects, the engineering projects are organized according to business modules, each business module comprises a plurality of tasks, and the tasks are associated according to a workflow to form a workflow software system. The traditional engineering project management informatization system directly simulates the original work management mode of an engineering project by software and aims to improve the communication efficiency of personnel and the management efficiency of affairs by utilizing an informatization technology. With the continuous development of information technology and the continuous improvement of software and hardware performance, a new-generation engineering project management system is constructed on the basis of new technologies represented by cloud computing, mobile internet, internet of things, artificial intelligence and the like, and the existing engineering project task management mode and mechanism are influenced. The working platform provides human resources in a cloud service mode, task release, distribution, completion, acceptance and management of the engineering project are achieved, the human resources are flexibly and efficiently scheduled in a larger range, the overall efficiency of the engineering project is improved, and the comprehensive cost of enterprises is reduced. However, constructing tasks on a working platform needs to meet a large number of different business scenarios and actual requirements, so how to flexibly customize the tasks and improve the efficiency of task construction are important problems and challenges to be solved by the working platform. At present, a working platform realizes the release and management and control of each type of task by developing the web application service of the type of task. With the increase of the number of task types to be supported on the platform, the workload of independently developing the application service for each task type is gradually increased, and the overall task construction efficiency of the platform is affected. One task construction idea is to use a workflow engine of a conventional office automation system (OA) for reference, define a task type in advance by a system administrator or a business administrator, set parameters related to the task type, and then describe and store the task type using a standard specification. When the platform runs, the task instance is initialized by reading the task type metadata information, so that the release and management and control of the task instance are supported. However, because of different service scenarios, such a conventional workflow engine issues and executes tasks basically through authority control, and does not consider platform-based operations such as issuing, splitting and distributing tasks, and is not suitable for being directly applied to a working platform.
Disclosure of Invention
Aiming at the defects of the background technology, the invention provides a work platform task construction system and a construction method, aiming at the service characteristics of a work platform, the platform-based operations such as the release, the split and the distribution of tasks are realized, and the system and the method can be directly applied to the work platform.
In order to achieve the purpose, the invention designs a work platform task construction system, which comprises at least one client, at least one server and at least one storage server; it is characterized in that the device is characterized in that,
the client side comprises the following steps: the system is used for a user to carry out task construction operation and comprises a task group definition module, a task type definition module, a project creation module and a task release module; the task group definition module is used for inputting basic information and organization structure information of a task group and sending the basic information and the organization structure information to the server, the task type definition module is used for inputting basic information and interface information of a task type and sending the basic information and the interface information to the server, and the project creation module is used for creating a project, setting project basic parameters and selecting the task group; the task issuing module is used for issuing tasks to the server;
the server side: used for executing task description and task construction, comprises a client communication module, a storage communication module, a data description module, a project task system generation module and an entity generation module, the client communication module is used for realizing data communication with a client, the storage communication module is used for realizing data communication with a storage server, the data description module is used for converting the task group or task type information into task system metadata according to the task system description specification, the project task system generation module is used for acquiring selected task system metadata from the storage server according to project basic parameters and a task group selected by a user, analyzing and creating a project task system, the entity generation module is used for generating task instances from task system metadata in a project task system, namely task groups and task data entities in the project task system;
the storage server: for storing task hierarchy metadata.
Furthermore, the organization structure information of the task groups refers to that the task groups are divided and classified according to the work content and related elements of the project, one task group comprises at least one sub-task group, one sub-task group is a set of a group of sub-task groups or a set of tasks, and each sub-task group and task only belong to one parent task group.
Further, the basic information of the task group includes a code, a name, a description, a tag, preset data, a parent task group, a child task group, a task, and a workflow.
Further, the basic information of the task type includes a code, a name, a description, a tag, a workload, a work mode, a task requirement, preset data, output data, a task group, a state, a precondition, and a postcondition.
Further, the interface information includes preset data, input data, and output data.
Further, the task hierarchy metadata includes task groups, task types, data entities for task input and output, and condition objects for task pre/post.
Further, the basic information of the task instance includes code, name, type, description, content, condition, value.
Based on the system, the invention also provides a construction method of the work platform task construction system, which is characterized by comprising the following steps:
1) a user defines a hierarchical task group through a client and inputs basic information and organization structure information of the task group;
2) a user inputs basic information and interface information of a task type through a client;
3) the server receives the basic information, organization structure information, task type basic information and interface information of the task group sent by the client, describes the data entity in a specified format and stores the data entity in a storage server;
4) a user creates an engineering project at a client and calls task system metadata in a storage server through the client to select a task group;
5) the server analyzes the task system metadata selected in the storage server according to the project basic parameters sent by the client and the task group selected by the user, creates a project task system and sends the project task system to the client;
6) a user issues a task to a server at a client according to a project task system;
7) and generating a task instance by using the task system metadata in the service end project task system.
Preferably, the specific steps of step 6) include:
61) acquiring a task data object corresponding to a selected task type in a project task system;
62) creating a task and a task group example according to the current task data object;
63) initializing a current task instance, and selecting a task group to set task parameters based on project basic parameters;
64) and executing the current task instance and feeding back a task execution result.
Preferably, the process of generating the task instance in step 7) includes: executing a task decomposition program: transversely decomposing the working content of the task into a plurality of subtasks according to the working mode attribute of the task type; executing a task allocation program: screening a matched packet receiver list according to task requirement attributes of the task types, and distributing decomposed subtasks to the packet receivers; executing a task management and control program: and calculating the completion deadline of the task according to the workload attribute of the task type and the start time of the task instance, reminding when the task is about to expire, checking the task state when the task expires, and executing subsequent processing.
Compared with the prior art, the method is based on a top-down task design concept, guides a project manager to define task modules and task types related to the engineering project hierarchically, describes task system information by a set of standard specifications, generates corresponding task examples by analyzing and configuring the information, and finally completes construction of all task systems of the engineering project. Aiming at the service characteristics of the working platform, the invention adds the task mode to the task type, realizes platform-based operations such as the release, the split and the distribution of the task, and can be directly applied to the working platform.
Drawings
FIG. 1 is a block diagram of a work platform task building system according to the present invention.
FIG. 2 is a definition depiction of the main task group "indes".
Fig. 3 is a definition description of the subtask groups "indexes.
Fig. 4 is a definition description of the task "indexes.
Fig. 5 is a data portion definition description of the task "indexes.
Fig. 6 is a description of the condition section definition of the task "indexes.
Detailed Description
The invention is described in further detail below with reference to the figures and specific embodiments.
As shown in fig. 1, the work platform task building system provided by the present invention includes at least one client 1, at least one server 2, and at least one storage server 3.
The client side 1: the task building system is used for a user to perform task building operation and comprises a task group defining module 11, a task type defining module 12, a project creating module 13 and a task publishing module 14.
The task group definition module 11 is configured to input basic information and organization structure information of a task group, and send the basic information and the organization structure information to the server 2. The basic information of the task group comprises codes, names, descriptions, labels, preset data, a parent task group, a child task group, tasks and workflows. The organization structure information of the task groups refers to that the task groups are divided and classified according to the work content and related elements of the project, one task group comprises at least one sub-task group, one sub-task group is a set of a group of sub-task groups or a set of tasks, and each sub-task group and task only belong to one father task group.
The task type definition module 12 is configured to input basic information and interface information of a task type, and send the basic information and the interface information to the server 2. The basic information of the task type comprises codes, names, descriptions, labels, workloads, working modes, task requirements, preset data, output data, task groups, states, preconditions and postconditions. The interface information includes preset data, input data, and output data.
The project creating module 13 is used for creating a new project, setting basic parameters of the project and selecting task groups.
The task issuing module 14 is configured to issue the task to the server 2 according to the task.
The server side 2: the system is used for performing task description and task construction and comprises a client communication module 21, a storage communication module 22, a data description module 23, a project task system generation module 24 and an entity generation module 25.
The client communication module 21 is configured to implement data communication with the client 1, receive basic information of a task group or a task type sent by the client 1, and send data related to a task system to the client 1. The storage communication module 22 is used for implementing data communication with the storage server 3, sending task groups or task metadata to the storage service, 3, and also reading specified task hierarchy related metadata from the storage server 3. The data description module 23 is used for converting the task group or task type information into task hierarchy metadata according to the task hierarchy description specification. The project task system generating module 24 is configured to obtain selected task system metadata from the storage server 3 according to the project basic parameters and the task group selected by the user, analyze the selected task system metadata, and create a project task system, and the entity generating module 25 is configured to generate task instances from the task system metadata in the project task system, that is, task groups and task data entities in the project task system; the basic information of the task instance includes code, name, type, description, content, condition, value.
The storage server 3: for storing task hierarchy metadata. The task system metadata comprises a task group, a task type, data entities for task input and output and condition objects for task preposition/postposition.
Based on the system, the invention also provides a construction method of the work platform task construction system, which comprises the following steps:
1) the user defines a hierarchical task group through the client 1, and inputs basic information and organization structure information of the task group.
The user logs in the client 1, creates task groups according to the construction content of the project type, organizes the task groups according to the affiliation, and defines the basic information of each task group.
The task groups are divided and classified according to the work content of the project and related elements, and one task group can comprise a plurality of subtask groups but only belongs to one parent task group (namely, a preorder subtask). The basic information of the task group includes:
2) the user inputs basic information and interface information of the task type through the client 1.
The user creates each task type in the task group at the client 1 according to the functional elements and the business process of each task group, and defines the basic information and the interface information of the task type.
Task types are metadata that represents a certain class of tasks and is used to describe various attributes of that class of tasks. On the working platform, the packet sending party can issue a task instance of a certain defined type, and the working platform can decompose the task according to the attribute of the type of task and then distribute the task to a proper packet receiving party. The basic information of the task type includes:
the working mode attribute of the task type determines the splitting and distribution mode of the working platform for the task, when the working mode is 'splitting according to groups/catalogues', the working platform splits according to the grouping or catalog structure of the task demand files, the working demand of each subtask comprises all the demand files in one group or catalog, and the demand files are distributed to an engineer; when the working mode is 'splitting according to files', the working platform splits according to the task requirement files, and the working requirement of each subtask comprises a requirement file and is distributed to an engineer; when the working mode is 'splitting according to page parts/file contents', the working platform splits according to the page parts or the file contents of each requirement file of the tasks, and the working requirement of each subtask comprises a certain part of one requirement file.
The interface information of the task type includes preset data, input data, and output data, and one task may have a plurality of preset, input, and output data.
3) The server 2 receives the basic information of the task group, the organization structure information, the basic information of the task type and the interface information sent by the client 1, describes the data entity in a specified format, and stores the data entity in the storage server 3.
The types of data entities include parameters, objects, files, etc., and also allow for multi-layered data structures.
The basic information of the data entity includes:
after the user finishes the task system definition, the client 1 sends the related task group and the task type information input by the user to the server 2, the server 2 describes the task system information according to a preset format specification, and the related task metadata comprises the task group, the task type, a data entity for task input and output, a condition object for task preposition/postposition and the like.
The task system information description specification is as follows:
(1) task group description specification
The task group information is located in an array defined by a "group" attribute, and the attributes of the task group data object include:
| attribute name | Data type | Description of the invention |
| id | Character(s) | Task group ID |
| name | Character(s) | Task group name |
| desc | Character(s) | Task group description |
| tag | Array of elements | Label list |
| data | Array of elements | Preset data list |
| parent | Character(s) | Belonged parent task group id |
| group | Array of elements | Subtask group object list |
| task | Array of elements | Task object list |
| work | Array of elements | Workflow link list |
(2) Task type description specification
The task type information is located in an array defined by a "task" attribute, and the attributes of the task data object include:
| attribute name | Data type | Description of the invention |
| id | Character(s) | Task ID |
| name | Character(s) | Task name |
| desc | Character(s) | Task description |
| tag | Array of elements | Label list |
| workload | Floating point number | Task standard reference workload |
| pattern | Integer number of | Operating mode options |
| requirement | Array of elements | Task requirement list |
| data | Array of elements | Task preset data list |
| in_data | Array of elements | Task input data list |
| out_data | Array of elements | Task output data list |
| parent | Character(s) | Task group id of the subject |
| status | Character(s) | Task state |
| start_cond | Array of elements | Task preconditions list |
| end_cond | Array of elements | Task post condition list |
The information such as the task group and the task type described in the above specification is recorded in the form of a file. After the task system description is completed, the server 2 sends the generated corresponding description file and metadata to the storage server 3 for storage, so that the task system information can be conveniently acquired at any time and any place.
The storage server 3 pre-analyzes the stored description file, and establishes an index for key information of data entities such as task groups and tasks, so as to improve the data retrieval efficiency.
4) The user creates an engineering project at the client 1 and selects a task group by calling the task system metadata in the storage server 3 through the client 1.
When the project is implemented, the server 2 may construct a task group and a task data object included in the project according to the defined task system. A user creates a new project through a client; a user sets basic parameters of a project at a client, wherein the basic parameters comprise a project code, a project name, a responsible person, a project owner, a project executor, project starting and ending time, a project initial state and the like, and input information is sent to a server; and the user accesses the storage server through the client, browses the task groups and the related task information, and selects a proper task group to join the project according to the project construction content.
5) The server 2 analyzes the task system metadata selected in the storage server 3 according to the project basic parameters sent by the client 1 and the task group selected by the user, and creates a corresponding task group and task data object according to the task description information, namely, creates a project task system and sends the project task system to the client 1.
6) The user issues tasks to the server 2 at the client 1 according to the project task system. The user selects a task type at the client 1 and sends a task issuing instruction of the type to the server 2. After receiving the task issuing instruction, the server 2 generates a task instance according to the data object information of the task type, performs initialization operation, and then executes the task instance. The method specifically comprises the following steps:
(1) acquiring a task data object corresponding to the selected task type;
(2) creating related tasks and task group examples according to the current task data object;
(3) initializing a current task instance, and setting task related parameters based on project information and user input data;
(4) and executing the current task instance and feeding back a task execution result.
7) And generating a task instance by the task system metadata in the service end 2 project task system.
After a user creates a task, the user selects to release the task, and respectively starts and executes the following programs according to the basic information and the task type information of the task instance:
and (3) task decomposition program: and transversely decomposing the work content of the task into a plurality of subtasks according to the work mode (pattern) attribute of the task type. If the working mode is 'work _ by _ group', the task is decomposed according to the grouping of the input content; if the working mode is 'work _ by _ file', the task is decomposed according to the input file; if the working mode is 'work _ by _ page', the task is decomposed according to the page of the input file;
and (4) a task allocation program. Screening a matched packet receiver list according to the task requirement (requirement) attribute of the task type, and then distributing the decomposed subtasks to the packet receivers;
and (5) a task management and control program. And calculating the completion deadline of the task according to the workload (workload) attribute of the task type and the start time of the task instance, reminding when the task is about to expire, checking the task state when the task expires, and executing subsequent processing.
The following is a specific implementation process of a work task in the field of industrial design based on the technical scheme:
defining the Main task A main task group "indes" is first defined, as shown in FIG. 2.
The main task group "indes" is located in the array defined by the "group" attribute, and its main information is:
id: the task group identifier is "indes".
name: the task group name is "Industry Design".
desc: the task group is described as "industrial design".
tag: a task group tag list comprising the following tags:
| serial | Label name | |
| 1 | Design of industry | |
| 2 | Production workshop |
data: presetting a data list, wherein the data entity types comprise forms, parameters, directories, files and the like
The parameters included are as follows:
| serial number | Parameter name | Type (B) | Description of the |
| 1 | workload | double | Standard reference value of workload |
The included tables are as follows:
among the options for the "standard" field are: "national standard", "American standard", "Japanese standard" and "European standard".
The files included are as follows:
| file sequence number | File name | Type (B) | Description of the | URL | |
| 1 | template | doc | Template file | Slightly less than |
The list included is as follows:
parent: the parent task group id has its parent attribute null since "indes" is the primary task group.
group: and a subtask group object list, wherein data is temporarily absent.
task: task object list, no data.
work: workflow link list, no data.
Defining the sub-task group, then, extending the "group" attribute of the "indexes" task group, and adding 2 sub-task groups "device" and "structure", as shown in fig. 3.
Device task group is located in the array defined by the group attribute of the index task group, and the main information is as follows:
(1) id: the task group identifier is "device";
(2) name: task group name "device";
(3) desc: task groups are described as "devices";
(4) tag: a task group tag list, including the tag "device";
(5) data: the method comprises the steps of presetting a data list, wherein the data list comprises a form work and parameters of code, name and work under the form work;
(6) parent: the superior task group is "indes";
(7) group: subtask group object list, no data.
(8) task: and a task object list, wherein data is temporarily absent.
(9) work: workflow link list, no data.
Defining the task type, then, expanding the task attribute of the task group of "indexes.
The "indexes.
(1) id: the task identifier is "calculated _ book";
(2) name: the task name is 'calculation book';
(3) desc: the task is described as a "computer book";
(4) tag: task tag lists, including the tags "compute book", "national standard";
(5) and (3) workload: the standard reference workload of the task is 0.5 person day;
(6) pattern: the task working mode is 'work _ by _ file', which means that the task is split according to the file;
(7) requirement: the task requirement list comprises a 'cn' standard which represents national standard and a 'ThiowRight works' tool;
(8) data: the task preset data comprises a directory, and the content of the directory is 4 pdf-formatted standard files of the files 'std _ cn', 'std _ us', 'std _ jp' and 'std _ eu';
(9) in _ data: task input data, including a form, having the fields "code", "name", "standard", and "start _ date";
(10) out _ data: task output data, including a form and a file directory, the form content is the fields "code", "name", "end _ date", "status", the directory content is 2 pdf format calculation book files;
(11) parent: device belongs to the task group of "indexes";
(12) status: the task state is null;
(13) start _ cond: a task precondition list including a condition (value of attribute "serial _ number" of the present task is 4) and a value of attribute "status" of task "indexes
(14) end _ cond: a task post-condition list including a condition (value of attribute "task _ status" of task "indexes
Other tasks defined include:
(1)“indes.device.requirement”；
(2)“indes.device.calculate_book_check”；
(3)“indes.device.calculate_book_review”。
after the description information is stored to complete the task group and the task type definition description, the description information is stored as a file "indexes. And after receiving the task description file, the storage server 3 analyzes the task description file, extracts the task system information and stores the related data entity into a metadata base. The table structure of the metadata database is as follows:
(1) t _ meta _ group: the task group metadata table comprises fields such as id, name, desc and parent;
(2) t _ meta _ task: the task metadata table comprises fields such as id, name, desc, workload, pattern, parent and the like;
(3) t _ meta _ tag: a tag metadata table including fields of name, obj _ id, obj _ type, and the like;
(4) t _ mate _ requirement: the task requires a metadata table including fields of name, obj _ id, obj _ type, obj _ value, etc
(5) t _ meta _ param: a parameter metadata table including fields of id, name, type, desc, obj _ id, obj _ type, and the like;
(6) t _ meta _ form: a form metadata table comprising fields of id, name, desc, obj _ id, obj _ type and the like;
(7) t _ meta _ form _ field: a form field metadata table, which comprises fields of name, type, desc, value, form _ id and the like;
(8) t _ meta _ file: a file metadata table including id, name, type, desc,
url, dir, etc.;
(9) t _ meta _ task _ data: the task preset metadata table comprises fields such as id, name, type and task _ id;
(10) t _ meta _ task _ in _ data: a task input metadata table comprises fields such as id, name, type and task _ id;
(11) t _ meta _ task _ out _ data: a task output metadata table comprising fields of id, name, type, task _ id and the like;
the id fields of the above tables are all primary key indexes, and other fields set as indexes include parent, obj _ id, obj _ type, form _ id, dir, task _ id, and the like.
Creation of project the project "SMP 19" is created by client 1, with the relevant basic information as follows:
(1) id: the item identifier is "SMP 19";
(2) name: the item name is "SMP 19";
(3) pm: the project responsibility is artificial "Fan-ChuanJua";
(4) owner: the project owner is Shenzhen Longhua biomedicine Limited company;
(5) a conductor: the project implementation is "Kongxin Industry Equipment company Shanghai";
(6) start _ date: the project start date is "2019-02-08";
(7) end _ date: the project expected end date is "2019-10-30";
(8) status: the initial state of the project is "1 preparation phase".
Selecting sub-task groups such as 'indexes' and 'indexes' under the 'indexes' task group from the task group list according to project construction contents;
and the generated task system sends a query instruction to the storage server 3 according to the selected task group, and queries the metadata information of each data entity of the task system related to the project. And respectively creating a task system data table related to the project at the server 2 according to the returned metadata information such as the task group, the task and the like.
Table structure of indexes, device, calculate _ book task table is as follows:
t_indes_device_calculate_book
the task table structure corresponding to other tasks is similar.
Generating task instance the user selects the "SMP 19" project at client 1, and creates a new "calculate _ book" task, the detailed information of which is:
(1) task id: 10083;
(2) task name: device a30298 computer book
(3) Task description: compiling a calculation book of the apparatus A30298 from a plan view
(4) The creator: Fan-Chuanjia;
(5) creation time: 2019-07-2008: 12: 30;
(6) standard file directory:http://doc.kongxin.com/id/standard/；
(7) a working form:
| field(s) | Value of |
| Work number | 10083 |
| Name of work | Calculation book |
| Standard of merit | National standard |
| Date of start | 2019-07-20 |
(8) Results table:
| field(s) | Value of |
| Work number | |
| Name of work | |
| End date | |
| Status of state |
(9) Delivering a file directory:http://doc.kongxin.com/id/device/；
after the information is input, the server 2 creates an index.
Example of executing task the execution process of the program after the example of the aforementioned index.
(1) The attribute content of the pattern of the task type is a work _ by _ file tool, and the task type is decomposed according to input calculation book files, wherein each file corresponds to a subtask;
(2) according to the attribute content of the 'requirement' of the task type, screening a packet connecting party with technical attribute information of 'cn' standard and 'ThiowWorks' tool and adding the technical attribute information into a candidate queue;
(3) distributing each subtask to a packet receiver in the candidate queue one by one;
(4) and after the distribution is finished, starting a timed task taskManage _10083, and calculating the timed time to be the task starting time +12 hours according to the attribute value 0.5 of the task type 'workload'.
In addition to the above embodiments, the present invention may have other embodiments. Any changes, modifications, substitutions, combinations, and simplifications which do not depart from the spirit and principles of the invention are intended to be covered by the scope of the invention which is defined by the claims which follow.
Claims (10)
1. A work platform task construction system, the system comprising at least one client (1), at least one server (2) and at least one storage server (3); the method is characterized in that:
the client (1): the task creating and publishing system is used for a user to perform task building operation and comprises a task group defining module (11), a task type defining module (12), a project creating module (13) and a task publishing module (14); the task group definition module (11) is used for inputting basic information and organization structure information of a task group and sending the basic information and the organization structure information to the server (2), the task type definition module (12) is used for inputting basic information and interface information of a task type and sending the basic information and the interface information to the server (2), and the project creation module (13) is used for creating a project, setting basic parameters of the project and selecting the task group; the task issuing module (14) is used for issuing tasks to the server (2);
the server (2): the system is used for executing task description and task construction and comprises a client communication module (21), a storage communication module (22), a data description module (23), a project task system generation module (24) and an entity generation module (25), wherein the client communication module (21) is used for realizing data communication with a client (1), the storage communication module (22) is used for realizing data communication with a storage server (3), the data description module (23) is used for converting task groups or task type information into task system metadata according to a task system description specification, the project task system generation module (24) is used for acquiring selected task system metadata from the storage server (3) according to project basic parameters and a task group selected by a user, analyzing and creating a project task system, and the entity generation module (25) is used for generating task instances from the task system metadata in the project task system, namely task groups and task data entities in a project task system;
the storage server (3): for storing task hierarchy metadata.
2. The work platform task building system of claim 1, wherein: the organization structure information of the task groups refers to that the task groups are divided and classified according to the work content and related elements of the project, one task group comprises at least one sub-task group, one sub-task group is a set of a group of sub-task groups or a set of tasks, and each sub-task group and task only belong to one father task group.
3. The work platform task building system of claim 1, wherein: the basic information of the task group comprises codes, names, descriptions, labels, preset data, a parent task group, a child task group, tasks and workflows.
4. The work platform task building system of claim 1, wherein: the basic information of the task type comprises codes, names, descriptions, labels, workloads, working modes, task requirements, preset data, output data, task groups, states, preconditions and postconditions.
5. The work platform task building system of claim 1, wherein: the interface information comprises preset data, input data and output data.
6. The work platform task building system of claim 1, wherein: the task system metadata comprises a task group, a task type, data entities for task input and output and condition objects for task preposition/postposition.
7. The work platform task building system of claim 1, wherein: the basic information of the task instance comprises codes, names, types, descriptions, contents, conditions and values.
8. A method for constructing a work platform task construction system according to any one of claims 1 to 7, characterized by: the method comprises the following steps:
1) a user defines a hierarchical task group through a client (1) and inputs basic information and organization structure information of the task group;
2) a user inputs basic information and interface information of a task type through a client (1);
3) the server (2) receives the basic information, organization structure information, task type basic information and interface information of the task group sent by the client (1), describes the data entity in a specified format and stores the data entity in the storage server (3);
4) a user creates an engineering project at a client (1), and selects a task group by calling task system metadata in a storage server (3) through the client (1);
5) the server (2) analyzes the task system metadata selected in the storage server (3) according to the project basic parameters sent by the client (1) and the task group selected by the user, creates a project task system and sends the project task system to the client (1);
6) a user issues a task to a server (2) at a client (1) according to a project task system;
7) and generating a task instance by the task system metadata in the project task system of the server (2).
9. The method of constructing a work platform task construction system according to claim 8, wherein: the specific steps of the step 6) comprise:
61) acquiring a task data object corresponding to a selected task type in a project task system;
62) creating a task and a task group example according to the current task data object;
63) initializing a current task instance, and selecting a task group to set task parameters based on project basic parameters;
64) and executing the current task instance and feeding back a task execution result.
10. The method of constructing a work platform task construction system according to claim 9, wherein: the process of generating the task instance in the step 7) comprises the following steps: executing a task decomposition program: transversely decomposing the working content of the task into a plurality of subtasks according to the working mode attribute of the task type; executing a task allocation program: screening a matched packet receiver list according to task requirement attributes of the task types, and distributing decomposed subtasks to the packet receivers; executing a task management and control program: and calculating the completion deadline of the task according to the workload attribute of the task type and the start time of the task instance, reminding when the task is about to expire, checking the task state when the task expires, and executing subsequent processing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910880679.0A CN110766375A (en) | 2019-09-18 | 2019-09-18 | Work platform task construction system and construction method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910880679.0A CN110766375A (en) | 2019-09-18 | 2019-09-18 | Work platform task construction system and construction method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110766375A true CN110766375A (en) | 2020-02-07 |
Family
ID=69330326
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910880679.0A Pending CN110766375A (en) | 2019-09-18 | 2019-09-18 | Work platform task construction system and construction method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110766375A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111552459A (en) * | 2020-04-16 | 2020-08-18 | 重庆富民银行股份有限公司 | Business arrangement process management system and method |
| CN112379921A (en) * | 2020-11-03 | 2021-02-19 | 中国直升机设计研究所 | System and method for automatic generation and self-improvement of dynamic flexible process |
| CN113283697A (en) * | 2021-04-21 | 2021-08-20 | 耐优生物技术(上海)有限公司 | Intelligent generation method of experiment system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226612A (en) * | 2007-12-29 | 2008-07-23 | 中国建设银行股份有限公司 | Data processing management system facing to process flow |
| CN103679401A (en) * | 2013-12-31 | 2014-03-26 | 浙江中控研究院有限公司 | Flow control method, server, client side and system |
| CN105046408A (en) * | 2015-06-25 | 2015-11-11 | 国网山东省电力公司 | Configurable workflow realization method and system |
| CN109144480A (en) * | 2018-07-24 | 2019-01-04 | 武汉空心科技有限公司 | Working platform method, platform and the system quickly delivered |
-
2019
- 2019-09-18 CN CN201910880679.0A patent/CN110766375A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226612A (en) * | 2007-12-29 | 2008-07-23 | 中国建设银行股份有限公司 | Data processing management system facing to process flow |
| CN103679401A (en) * | 2013-12-31 | 2014-03-26 | 浙江中控研究院有限公司 | Flow control method, server, client side and system |
| CN105046408A (en) * | 2015-06-25 | 2015-11-11 | 国网山东省电力公司 | Configurable workflow realization method and system |
| CN109144480A (en) * | 2018-07-24 | 2019-01-04 | 武汉空心科技有限公司 | Working platform method, platform and the system quickly delivered |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111552459A (en) * | 2020-04-16 | 2020-08-18 | 重庆富民银行股份有限公司 | Business arrangement process management system and method |
| CN112379921A (en) * | 2020-11-03 | 2021-02-19 | 中国直升机设计研究所 | System and method for automatic generation and self-improvement of dynamic flexible process |
| CN113283697A (en) * | 2021-04-21 | 2021-08-20 | 耐优生物技术(上海)有限公司 | Intelligent generation method of experiment system |
| CN113283697B (en) * | 2021-04-21 | 2023-11-24 | 耐优生物技术(上海)有限公司 | Intelligent generation method of experiment system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107370786B (en) | General information management system based on micro-service architecture | |
| CN107341643B (en) | Visual process display method and system | |
| CA2949955C (en) | Workload automation and data lineage analysis | |
| Fidler et al. | The PADRES Distributed Publish/Subscribe System. | |
| CN110717656A (en) | Work platform workflow construction system and construction method | |
| CN110766375A (en) | Work platform task construction system and construction method | |
| CN110119393B (en) | Code version management system and method | |
| Thanekar et al. | Big Data and MapReduce Challenges, Opportunities and Trends. | |
| CN111143391A (en) | Data sharing exchange method and system | |
| CN115169011A (en) | Editing system and application system of airplane assembly outline | |
| US20110289041A1 (en) | Systems and methods for managing assignment templates | |
| CN102567517A (en) | Device and method for issuing data of database | |
| CN116523479A (en) | Collaborative creation method for digital works, task release method and device | |
| US8869122B2 (en) | Extensible executable modeling | |
| CN111381811A (en) | Software resource integration platform suitable for integration of multiple types of information systems | |
| JP2017511946A (en) | System and method for automatic digital RFID printing and integration | |
| CN109471709B (en) | Scheduling method for flow task processing big data based on Apache Oozie framework | |
| Li et al. | Decentralized execution of event-driven scientific workflows | |
| CN113407161B (en) | Collaborative research and development management system for complex equipment | |
| CN112685010B (en) | AI application development method and system | |
| Xiuli et al. | Research on Digital Agile Information System Based on Microservice Architecture | |
| EP4354281A1 (en) | Converting an api into a graph api | |
| Ding et al. | ERP and PDM integration technology to support collaborative product development | |
| Xu et al. | A distributed computing architecture for simulation and optimization | |
| Chung et al. | A Java-Based, System for Collaborative Design and Manufacturing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200207 |
|
| WD01 | Invention patent application deemed withdrawn after publication |