Detailed Description
The general idea of the invention is to classify, manage and correlate the business needing to be managed after the business is elemental in the process of managing the scheduling. Therefore, a systematic system device is established to establish a classified frame, another systematic device is established to manage the content of the frame, and meanwhile, the function of the system device is used for self-perfecting in the management process of the content, and an interactive system device which interacts with the outside and a system device which automatically processes the business are established. By the method, more resources can be provided for management users, classified reuse is realized, and the management system can be used in various scenes with different requirements, so that maintenance is more visual, and management is more flexible.
For basic scheduling management, there are two important factors for scheduling, namely, personnel and date. In short, people and dates are established to meet the corresponding relation, namely the management of the realized scheduling. To establish this connection, the person and the date are therefore classified respectively, namely a person module and a work date module. One person corresponds to one person module and one work date corresponds to one work date module. For the characteristics of the personnel module, the labels of the modules are used for management. The system comprises a plurality of personnel modules, wherein each personnel module comprises a plurality of labels, at least 4 groups of labels, namely name, number, work type and work date, are needed in one personnel module according to at least the needed characteristics in scheduling management, and the values of the work date labels of one personnel module correspond to the work date module, so that the scheduling of one personnel in a certain period is completed. Similarly, at least 5 groups of labels, namely names, time periods, dates, work types and people-in-person lists, are needed in one work date module, and the personnel list labels in one work date module correspond to the personnel modules, so that personnel work arrangement on the work date is completed.
Thus, two modules are involved in the shift management device, a personnel module and a working time module, each of which is structured to include one or more sets of tags, a set of tags including tag names and tag content. A plurality of modules of identical construction are incorporated into a module container. The modules in different containers can be mutually bound to establish a corresponding relationship. The plurality of people modules is managed by a people module container and the plurality of work time modules is managed by a work time module container.
In the invention, a system manager is provided, as shown in fig. 1, the system manager comprises a container manager, a label manager, a response manager, a binding loader and a logic flow calculator, wherein the container manager and the label manager can manage containers, modules and labels in a scheduling management device.
Specific embodiments of the present invention will be described in further detail below with reference to the drawings accompanying the specification.
1. Container manager
In the present invention, a means is devised for accommodating a plurality of transactions belonging to the same class. This device is a container, requiring two basic pieces of information, personnel and work time for a shift. The two basic information are then processed separately into modules, which are then packaged in containers. The means of managing this container is a container manager. The container manager mainly comprises a content manager for managing the contents of the container and the module under the container according to the response instruction, and a space manager for determining the size of the container and managing the space.
FIG. 2 shows a structure diagram of a container manager embodying the present invention, and is implemented as follows:
step S201, defining a container, the container manager determines to generate a container in this step, assigns a value to the name of the container, and determines the size of the container. The container name is used to uniquely determine the identity of the container, the container size, i.e., how many modules can be accommodated in the container. The name and size are the basic features of the container, and the size of the container may determine that each module within the container has a sequential number, which may also be used to designate a module, e.g., the container name i indicates the ith module in the container.
In addition, the container manager may add other features to the container, such as region, color, etc., as desired. For example, in a shift management scenario, two containers are generated with a container manager:
Container 1 name = personnel module container
Size=5
Region = beijing// custom feature
Where size = 5, i.e. 5 personnel modules are included in the present container, area = beijing indicates that the ancillary features of the present container include areas, and the areas of personnel modules are in beijing.
Container 2 name = working time module container
Size=20
Number 1 |
Number 2 |
Number 3 |
Serial No. 4-19 |
Sequence number 20 |
Module |
Module |
Module |
Module |
Module |
Step S202, the operations of the container manager for managing the content of the container, including the adding operation of the content, can add the content of the container, namely, the module. The structure of the modules, as shown in fig. 3, one module includes a plurality of tags.
For example, in a shift management scenario, the module personnel module involved has at least 4 sets of labels, the names of the 4 sets of labels being name, number, work type, work date list, respectively. The related modules in the scheduling management scene also have a working time module, and the working time module has at least 5 groups of labels, namely names, time periods, dates, working types and personnel lists.
When the addition of the content management of the container is performed in step S202, the content of one module is added even in the container. 1. Adding person modules in the person module container, at step S201, the number of person modules is defined as 5,
The contents of 5 personnel modules can be added to the present container and the size of the module specified. The size of the module is such that,
I.e. the number of labels of the modules, e.g. the number of labels of the personnel modules is 4:
2. adding a working time module in a working time module container:
At step S201, when the size of the operation time module container is defined as 20, 20 modules are generated in the container, and the size of the module is 5 (5 sets of tags per module). In the following table, the addition operation is performed on 20 modules (the modules from the number 4 to the number 19 are omitted from the table)
In step S203, the number of modules, that is, the size of the container is determined when the container is generated. This step is space management of the container, increasing the size of the container.
Step S204, the step is content management of the container, deleting a module with a certain serial number in the container or a module with a certain tag name as a certain value, wherein after deleting, the size of the container is unchanged, but the content of the designated module is empty.
Step 205, which is space management of the container, the designated module position of the designated space can recycle the space if the designated module position is empty. And correspondingly changing the serial number of the recovered module. For example, there are 5 modules in the container, and the "container name" [ i ] is used to point to, and if the "container name" [3] deletes the content and then deletes the space, the original "container name" [4], "container name" [5] is automatically changed to "container name" [3], "container name" [4] ".
Step S206, the space management of the container is that a new container is newly established as a target container by taking the appointed existing container as a source container, and the structure, the module, the label structure and the label content of the target container are copied to the source container. And before replication, the module to be replicated, the label of the module may be selected. In the duplication operation, the structure of the container, the module and the label need to be duplicated in total, the duplicated module content can be selected, and the label content can be selected. For example:
1) "Source Container name" - [ i ] - [ j ] - [ tag name 1, tag name 3] "is copied to the new container, i.e. the module structure, tag number, tag name of the Source Container name are copied to the new container, and tag contents of tag name 1and tag name 3 in the modules of sequence numbers [ i ] to [ j ] in the Source Container name are copied to the new container;
2) "source container name [ all ]" copies to the new container, i.e., copies all content of all modules of the source container name to the new container;
3) "Source Container name [0]" copies to the new container, i.e., copies the structure of the Source Container name Module (tag and tag name) to the new container;
2. label manager
After the container is defined in the container manager and the size is determined, the specific content of the container, namely the module, can be specifically managed through the label manager.
The label manager at least comprises three functional devices, namely a definition module, an assignment module and a binding module.
The definition module and the assignment module can be used for managing tag content, and the definition module and the assignment module comprise definition, assignment and deletion;
The binding module is used for extracting the label content of the label name corresponding to the module meeting the condition in the appointed container, and transmitting the content meeting the requirement to the binding module for further extraction and use.
The management of the modules in the container by the tag manager, and the means by which the personnel module container and the working time module container in the scheduling management are managed are implemented in the tag manager will now be described with reference to fig. 3.
Step S301, label definition, in which a label manager defines a label name and a value assignment rule of label content corresponding to the name in a module;
For example, in a scheduling management scenario, label definition needs to be performed on a person module in a person module container and a working time module in a working time module container, and after label definition, the person module container and the working time module container are as follows:
step S302, deleting a certain tag group in all modules in a designated container by a tag manager;
step S303, label assignment, namely, assigning label contents corresponding to label names under a designated module:
for example, in a shift management scenario, there are two shift-on time regimes, a shift and a night shift, with five people and shift, 3 (A, B, C) participating in the shift and 2 (D, E) participating in the night shift.
Firstly, basic information of a personnel module is assigned, the basic information is assigned before specific scheduling information is determined, and the assigned personnel module container is as follows:
The 10-day shift is now performed, and after assignment of the working time module, the contents of the working time module container are as follows (the lower drawing omits the numbers 4 to 18)
Step S304, binding data, wherein the binding data is a module of the label manager, and the binding module is used for realizing the function. The binding module is provided with an independent functional block, namely a binding loader, extracts corresponding tag content according to the module where the tag name of the designated tag content is located, and prepares the tag content for the next use. In the binding module, the extracted data may be selected.
For example, in a scheduling management scenario, assignment of work date labels of the personnel modules in the personnel module container is required, the assignment content is one or more work time modules meeting requirements from the work time module container, and meanwhile, assignment of personnel list labels in the work time module container is required, and the assignment content is one or more work time modules meeting requirements from the personnel module container.
1) Assignment of working date label of personnel module:
a) Selecting a personnel module needing to be assigned, and extracting the content of a work type label, for example, the label is named as a label content A corresponding to a name, and the work type of the personnel module with the label content A is a shift;
b) The transmission content comprises a work type=white shift, a container=a work time module container, an output tag=a name, and the binding loader extracts a work type=white shift module from the work time module container according to the transmission content, extracts tag content of tag name=name as the output content of the binding loader, wherein the transmission content can be additionally defined in a transmission protocol, such as limiting the quantity of the transmission content, limiting the assigned content of the tag corresponding to the output module, and the like.
C) According to the operation of step b), the output content of the binding loader is
"Work date module container" [ name= '7-1 shift' ], work date module container "[ name= '7-2 shift' ], work date module container" [ name= '7-3 shift' ] ";
d) The binding module invokes the assignment function of the assignment module to assign the output content of step c) to the personnel module container [ name= 'a' ]. Date of operation
E) The step d) is operated, and the label content of the work date module container [ name= '7-1 white shift' ], the personnel list and the work date module container [ name= '7-2 white shift' ], the label content of the personnel list is added, and the added value is the personnel module container [ name= 'A' ].
2) Personnel list label assignment of the working time module:
the active assignment is the same as the assignment of the people module container. For the case of mutually binding assignments, each assignment operation operates with respect to the labels of two containers.
In this example, 3 people (A, B, C) participate in the shift, 2 people (D, E) participate in the night shift, and after binding and assignment under no other additional conditions, the contents of the personnel module container are:
The contents of the working time module container are as follows (the following figures omit the numbers 4 to 18)
The binding loader can also extract various data from each container according to different requirements, so that in actual application, the binding loader can be applied according to the characteristics to carry out secondary processing so as to meet different requirements. For example, in the scene of scheduling management, the existing resources are processed for the second time to generate a scheduling determining module, a personnel scheduling storage module, a working time scheduling storage module and a scheduling table generator:
The scheduling determining module can use the binding loader to extract the related information of the personnel module and the working time module, and determine the corresponding relation between each personnel module and the working time module, namely, the working time of the personnel module and the personnel list of the working time module form a display mode to be displayed to a user, and can be adjusted by a manager, and after the adjustment and the submission, the label content of the related module is refreshed.
And the personnel scheduling storage module is used for storing one device of a scheduling mode according to label content corresponding to the working date label in the personnel module. When the scheduling is determined, the scheduling content according to the personnel inquiry needs to be displayed to the user, a personnel scheduling storage module can be adopted to extract the corresponding relation related to the personnel scheduling which is effective at the moment, the simple and clear display is carried out, the corresponding relation is stored in response to the instruction of an administrator, the corresponding relation can be stored in a disk in a file mode, the file mode can be a text file or a table file, and a new container and a new module can be established through a container manager and used for storing and recording a scheduling information table of a certain time period. The working scheduling table can be more easily called through the personnel scheduling storage module, so that the checking efficiency is improved, and the operation method is simplified.
And the working time scheduling storage module is used for storing the label content corresponding to the personnel list label in the working time module as another device for scheduling. When the scheduling is determined, the scheduling content queried according to the date needs to be displayed to the user, a working date scheduling storage module can be adopted to extract the corresponding relation related to the currently effective scheduling, the corresponding relation is displayed simply and clearly, the corresponding relation is stored in response to an instruction of an administrator, the corresponding relation can be stored in a disk in a file mode, the file mode can be a text file or a table file, and a new container and a new module can be established through a container manager and used for storing and recording a scheduling information table of a certain time period. Through the working date scheduling storage module, the effective scheduling table can be more easily called, the checking efficiency is improved, and the operation method is simplified.
The display mode of the corresponding relation between the personnel module container and the modules in the working time module container can be determined by a manager and forms a template. The scheduling table generated according to the template at different stages can be stored in a newly built container or in a file form on a disk.
3. Response manager
The response manager is used to define specifications for transmitting and processing client information and to receive, assign processing means and a set of means for processing packets from the client.
FIG. 4 is a block diagram of a response manager, as shown, with a portion of the devices of the response manager residing in the container manager, the response data definer and the response data decoding manager, and devices external to the container manager, such as the response data encoding manager, between the client and the container manager.
1. And the response data definer is used for carrying out data management rules on the container manager and the label manager, and carrying out the definition by a user and the implementation by the response data definer on protocols, coding and decoding methods, specifications and the like of the transmission data encapsulation. User-defined rules, specifications refer to the configuration of data types, including the name, logo of the responding subject, the operations that the responding subject can perform, the logo corresponding to the operations, the objects that the operations perform, and the content of the operations.
1) The user-configured data structure specification includes at least the following:
TABLE 1
The information in table 1 is the most basic operation that can be performed by the container manager and the tag manager.
The specification of the data information package may include json format, xml format, etc.
In the response data definer, the self-contained output identifier OUT, under which the user can also configure the output specification,
The following table shows:
TABLE 2
In addition, output of an operation result thereof is provided in response to the operation content of each user-defined data specification in the data definer.
TABLE 3 Table 3
3) The user configuration mode can be realized by adopting a management platform, an application program and the like;
The result of user configuration can adopt a database storage and file storage mode, and the corresponding relation of the operation identification, the response main body, the operation content and the operation object is reflected in the result, and the structure of the data packet containing the information before.
For example, to implement the function of adding modules to a container, a management user may define in the response data definer the following structure add-container manager-container name module name [ number of tags ], and specify the structure of the data packet, e.g., define the structure as:
Packmsg = [ { "oper": "add" }, { "obj": "container name. Module name" },
{ "Content": "[ {" LabelSize ": number of tags } ]", and
The flow of user configuration is shown as a link S401 in the response manager configuration diagram shown in fig. 4. And sending the functions to be realized, the data information to be submitted for realizing the functions and the structure for packaging the data information to a response data definer for management.
When the manager submits the data specification at the user terminal, the response data definer can provide the information to the user terminal for data preparation, and the information of the user terminal is processed by the response data coding manager to be in accordance with the data packet structure of the specification and sent to the response manager.
2. And the response data coding manager is used for uniformly receiving the operation data of each user terminal, loading the configuration data of the response data definer, processing the operation data of the user terminal into a data packet conforming to the specification and transmitting the data packet to the response manager. The device can be used for realizing functions between the data extraction of the user side and the data receiving of the container manager, and the position of the device can be arranged in the user side and the container manager or can be arranged in a separate middle layer according to the figure 4.
1) In step S402, the user terminal initiates a data request, which may be submitted through a form format of a web page of an existing system, and is submitted by an APP of an existing mobile terminal through a custom protocol or HTTP, websocket. The response data coding manager converts the data information under the original data protocol of the user side so as to meet the functions of the container manager and related managers of cross-platform and cross-protocol, and can meet the requirement of adapting to various existing environments.
2) In step S403, the response data encoding manager extracts a data specification from the response data definer, and prepares for conversion of the data acquired in step S402. The link may be that when the service is loaded, the complete data is extracted from each response data definer once, or that when the specification of the response data definer is updated, the incremental data is pushed to the response data coding manager once, or that when the user side sends the data to the response data coding manager, the response data coding manager extracts the needed data from the response data definer.
3) In step S404, the response data encoding manager transmits the converted data packet to the response data decoding manager.
3. And the response data decoding manager is used for receiving the data packet, splitting the data packet according to the configuration result of the response data definer for managing the data by the user, and sending the instruction to the response main body appointed in the data packet.
1) In step S407, the response data decoding manager extracts a data specification from the response data definer, and prepares for conversion of the data acquired in step S404. The step may be that the complete data is extracted from each response data definer once when the service is loaded, or that the incremental data is pushed to the response data decoding manager once when the response data definer generates the specification update, or that the response data decoding manager extracts the required data from the response data definer after the data is obtained from step S404.
2) And step S404, after the response data encoding manager converts the data packet, uniformly transmitting the data to the response data decoding manager, and decoding, analyzing and distributing the information by the response data decoding manager.
3) And S405, S406, judging a response subject of the processing according to the data structure specification obtained from the S407, if the response subject is a container manager, transmitting the operation to be processed and the specific content to the container manager, and if the response subject is a label manager, transmitting the operation to be processed and the specific content to the label manager.
The following describes the processing scheme of the response manager in the embodiment of shift management:
Manager makes canonical definitions in response data definer
The operation of standard definition can be defined by secondary development by a developer, and a management platform can be provided for the manager to input according to rules.
The entered specifications are shown in tables 1 and 2.
Process flow of response manager
The existing manpower management system of the unit needing scheduling management has two modes of APP and webpage end, and respectively adopts the original data protocol of webpage form submission and APP submission.
The current processing content is that a personnel module containing 4 tag groups is added in a scheduling manager:
Data portion of the form commit message:
"oper =add & obj=" people module container "& LabelSize =4"
Data portion of APP submitted information:
"param= {" oper ":" add "," obj ":" people module container "," LabelSize ":"4 "}";
(1) And the response data coding manager is used for carrying out data request with the response data definer, extracting the data contents in the table 1 and the table 2, and uniformly converting the data information under the two specifications into data packets:
packmsg = [ { "oper": "add" }, { "obj": "people module container" },
{“content”:“[{“LabelSize”:4}]”}]
After the conversion is successful, the data is submitted to a response data decoding manager of the response manager.
(2) The response data decoding manager receives the data packet of the response data encoding manager, analyzes the data packet to obtain a result:
operation subject Container manager
Operation add
Operating object is 'personnel module container'
Operation content adding a Module in a Container, wherein the number of tags of the Module is 4
After the response data decoding manager identifies the operation subject as the container manager, the result after analysis is sent to the container manager to process related operations.
Operations that the container manager can do:
in a shift management scenario, the operations executable by the container manager portion and corresponding packet information are as follows:
In the scheduling management scenario, the label manager part can execute the following operations and corresponding data packet information:
for more flexible applications, some basic operations can also be defined:
Next, with reference to fig. 5, which is a timing chart of response of the response manager in response to a user request, the steps of the response manager in the usage flow will be described in detail:
Step S501, which is an embodiment data preparation step, wherein a user terminal refers to a maintenance user, including an administrator of an enterprise, and may also include a secondarily developed programmer, and initiates a request for data configuration to a response data definer. The implementation of the step can be realized by a web and APP platform to initiate a request, or by a secondarily developed program and script, so that the user side of the step comprises a web and APP terminal, an application program side available for secondary development and the like.
Step S502, the response data definer triggers step S502 according to the request of step S501, data configuration is carried out in the server, and data preparation is carried out for the application. After this step is completed, the configuration results may be provided to the response data encoding manager and the response data decoding manager for loading. The loading mode may be pushed to the response data encoding manager and the response data decoding manager after the completion of the step, or may be pushed after the requesting party initiates the request for loading configuration, as in step S504 and step S507.
In step S503, the manager initiates the request at the client, and the data protocol of the initiated request only accords with the rules of the client. After the data information is coded and converted in the response data coding manager, the data information is transmitted to the response data decoding manager in step S505.
Step S506, through the step, the element of the content to be processed by the user and the response body of the processing operation are analyzed. And transmits the contents to be processed to the corresponding response body through the step S508 or S509.
In the above embodiments, the operation requests from the user side processed by the response manager are basic data requests, i.e. one operation is processed at a time. However, in actual management requirements, a large number of records and operations need to be handled.
For example, a 365 day shift of 100 employees is required. Therefore, the management experience and work efficiency of the manager are poor in the manner of requesting to process one person's shift at a time. In this case the response manager also provides a solution for batch processing, i.e. manipulation of data files.
In addition to manipulating the default packet specification in the data file, the user may add an extended packet specification to the response data definer. For example:
1) A plurality of operation data distinguishing rules, wherein the response data coding manager can identify a plurality of pieces of data, and distinguishing modes can be configured by an administrator and comprise a separator, an identification of a data specification and the like;
2) The size of the operation data file is that the response data coding manager defaults to process the size of the file to adapt to the waiting time when the user experiences the operation, and the management user can also define the size of the file through the response data definer;
The identification of the data can be performed in an json mode and an xml mode in the operation data file.
In a shift management scenario, the following data specifications of the operational data file may be defined:
Packmsg={"contentFilename":"filename.txt"};
The content in filename. Txt may be:
{ "oper": "LabelAssign", "obj": "PackUser" [1-5] [ name ] "," content ":" A; B; C; D; E "}
And responding to the data encoding manager to receive the operation data file, and analyzing the operation data file into 5 operation instructions:
packmsg = { "oper": "LabelAssign", "obj": "PackUser" [1] "," content ": [ {" LabelName ":" name "," LabelValue ":" a "} ] }
......
Packmsg = { "oper": "LabelAssign", "obj": "PackUser" [5] "," content ": [ {" LabelName ":" name "," LabelValue ":" E "} ] }
And the analyzed instruction is sent to a response data decoding manager to distribute a response main body and specific operations.
In order to determine the canonical accuracy of the operational data file processed by the response data encoding manager, an operational data file generator is also included in the response manager.
As shown in FIG. 6, the operational data file generator is interposed between the user side and the response data encoding manager, which may be implemented as a web page.
In S601, an operation data file generator obtains relevant data specifications from a response data definer;
in S602, a user can select an operation to be performed on a web page, input information to be operated in batches, such as a user name and a date, and process the information into an operation data file conforming to a specification by a response data definer;
In step S603, the operation data file is sent to the response data encoding manager, and the response data encoding manager splits and parses the operation data file according to the data specification obtained in step S604 from the response data definer, and sends the operation data file to the response data decoding manager in batches or piece by piece through step S605.
The apparatus shown in fig. 2 to 6 and the flow of each link are managed around each module in the container. The system manager for realizing all management comprises a container manager, a label manager, a binding loader and a response manager, wherein the binding loader realizes the function of associating each module.
A container manager for framework construction, a tag manager for data construction, a binding loader for processing data, a response manager for interaction, a logic flow calculator for business processing. And using each component of the system manager to establish a scheduling manager, and realizing scheduling of personnel and time in the scheduling manager, wherein the device structure is shown in figure 7.
Fig. 7 is a block diagram of a shift manager generated in accordance with a preferred embodiment of the present invention. As shown in FIG. 7, the device comprises, but is not limited to, a personnel module for storing basic information of a personnel, a working time module for storing basic information of a working time period, a personnel module container for preparing space for all the personnel modules and accommodating all the personnel modules, a working time module container for preparing space for all the working time modules and accommodating all the working time modules, a scheduling determining module for determining the corresponding relation between each personnel module and the working time module and the binding relation between each working time module and the personnel module, a personnel scheduling storage module for storing all the working time modules bound by the personnel modules corresponding to a first specified operation in response to the first specified operation, a working time scheduling storage module for storing all the personnel modules bound by the working time modules corresponding to the first specified operation in response to a second specified operation, and a scheduling table generator for generating a required scheduling table by combining the information of the personnel scheduling storage module and the working time scheduling storage module in response to a third specified operation.
As shown in fig. 8, the flow of the method of implementing the response manager for scheduling management includes the steps of:
Step S801, performing response data definition management, wherein the response data definition management is used for defining the configuration of a user on a data encapsulation rule, and comprises a name and a mark of a response main body, an operation which can be performed by the response main body, a mark corresponding to the operation, an object which is performed by the operation and operation content which is performed on the object;
step S802, for the operation content of the user is batch operation, the step S is entered, wherein operation data file management is carried out, namely batch operation data submitted by the user is obtained from a user side, and response data coding management is carried out after the batch operation data is processed into operation data files meeting specifications according to the configuration;
Step 803, the operation data file and a single operation instruction from the user can enter the step, namely, the operation data submitted by each user terminal is received in a unified way in response to the data coding management, the configuration of a response data definer is loaded, the operation data is processed into a data packet conforming to the configuration, and the data packet is sent to a response manager;
And step S804, the data processed in the step S803 are subjected to response data decoding management, namely, the data packets conforming to the configuration are received, the data packets are split according to the configuration of the response data definer for the data encapsulation rule, and the instruction is sent to a response main body appointed in the data packets.
In the existing enterprise management, the original management platform, the platform system supporting diversification and the smooth support of data are fused, and the invention can realize intercommunication of data under different systems and different specifications on the basis of paying less management cost. In addition, in the system management device and the system management method for scheduling management, the entry and the specification of data are unified, and a multi-user processing solution is provided, so that the management and the maintenance are more efficient and convenient.
The foregoing disclosure is merely illustrative of some embodiments of the present invention, and the present invention is not limited thereto, as modifications may be made by those skilled in the art without departing from the scope of the present invention.