Device and method for implementing response manager for shift management

Abstract

The present invention discloses a device and method for implementing a response manager for shift management. The response manager in the device is used to define the specification of transmitting and processing user-side information, and receive data packets from the user-side and specify a processing device for data processing; the response manager includes: a response data definer, a response data encoding manager, and a response data decoding manager. According to the above technical solution, the data specification of the unified shift management can be realized, and the problem of inconsistency with the data specifications of other platforms such as existing human resource management can be solved; at the same time, the technical problem of batch input of user information and matching the user information with appropriate devices can also be solved in the case of a large number of users.

Description

Technical Field

[0001] The present invention relates to the fields of computer application and communication, and in particular to a device and method for a response manager for realizing shift management. Background Art

[0002] With the diversification of the current corporate work model, there are also many rules for employees' work and rest time, such as 9 am to 5 pm Monday to Friday, 9 am to 9 pm six days a week, 6 pm to midnight work two days and rest one day, etc. There are also multiple work and rest time coexisting in one company. Therefore, it is necessary to have a systematic scheduling management for working hours and rest time. At the same time, the entry, position, and resignation of corporate employees are all managed uniformly in the human resources management system. Therefore, the scheduling system needs to keep in touch with the corporate human resources management system.

[0003] As for the scheduling method, there are some systems that can schedule personnel, but they need to be configured in the management interface. If there are a large number of people, it will also affect the efficiency of processing. At the same time, if the human resources employee management platform and the scheduling platform cannot communicate with each other, it is necessary to manually import the information of all employees.

[0004] At the same time, with the deepening of enterprise operations, there are multiple schedules coexisting and multiple rules switching. Therefore, the schedule needs to be expanded, the types of schedules are increased, and the schedule rules are modified. The original personnel and time resources need to be reused, and there are higher requirements for the flexibility of management methods. Summary of the invention

[0005] The present invention provides a device and method for a response manager for shift management, so as to realize unified data specifications for shift management and solve the problem of inconsistency with data specifications of other platforms such as existing human resource management. At the same time, the present invention also provides a file processing method to solve the technical problem of batch input of user information and matching the user information with appropriate devices when there are a large number of users.

[0006] The present invention adopts the following technical solutions:

[0007] According to one aspect of the present invention, the present invention provides a device for a response manager for implementing shift management, the device comprising a response manager; the response manager is used to define specifications for transmitting and processing user-side information, and receive data packets from the user side and specify processing devices for data processing; the response manager comprises: a response data definer, a response data encoding manager and a response data decoding manager.

[0008] The response data definer is used to implement the user's configuration of data encapsulation rules, including the name and flag of the response subject, the operations that can be performed on the response subject, the flags corresponding to the operations, the objects on which the operations are performed, and the contents of the operations performed on the objects;

[0009] The response data encoding manager is used to uniformly receive the operation data submitted by each user end, load the configuration of the response data definer, process the operation data into a data packet that complies with the configuration, and send it to the response data decoding manager;

[0010] The response data decoding manager is used to receive data packets that meet the configuration, split the data packets according to the configuration of the response data definer for data encapsulation rules, and send instructions to the response body specified in the data packet.

[0011] The operation content includes: when the operation involves retrieval, the tag name value and / or tag content value corresponding to the search conditions involved; when the operation involves output, the tag name value and / or tag content value corresponding to the output content involved; when the operation involves retrieval, the data information specification; when the operation involves output, the data specification of the output result.

[0012] The data specifications include: json format.

[0013] The operation data submitted by the user end includes: a response body and operation data specified by the response body, wherein the data content of the specified operation data includes: the type of response operation, the operation object, and the operation content;

[0014] The type of response operation is used to mark different response subjects and corresponding operation flags, where the response subject includes: container manager, tag manager; the operation flag is used to mark the operation method, including: define, delete, assign, and bind.

[0015] Operation object, used to mark the object to be operated and the object name, including: container, module, label;

[0016] Operation content is used to retrieve and maintain data content when operating the operation object.

[0017] The operation data received by the response data encoding manager also includes: an operation data file; the operation data file includes multiple operation data.

[0018] The present invention also includes: an operation data file generator;

[0019] The operation data file generator obtains the configuration of data encapsulation rules from the response data definer; obtains the batch operation data submitted by the user from the user end, and processes it into an operation data file that meets the specifications according to the configuration;

[0020] The operation data file generator submits the operation data file to the response data encoding manager.

[0021] According to another aspect of the present invention, the present invention also provides a method for implementing a response manager for shift management, the method comprising: a method for data response management: defining specifications for transmitting and processing user-side information, defining rules for receiving data packets from the user-side and specifying processing devices for data processing; response data definition management, response data encoding management, response data decoding management, and operation data file management.

[0022] According to the present invention, the device and method of the response manager for realizing scheduling management provided by the present invention can realize intercommunication between the system manager for scheduling and the existing personnel platform data with various different data specifications, and can solve the management of large amounts of data, improve management efficiency, and enhance the management experience of managers. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 is a block diagram of the system manager structure of the embodiment of the present invention

[0024] Figure 2 is a functional schematic diagram of a container manager according to an embodiment of the present invention;

[0025] Figure 3 It is a structure and data flow diagram of the module, tag manager and binding loader in the shift manager according to the preferred embodiment of the present invention;

[0026] Figure 4 is a structural block diagram of a response manager according to an embodiment of the present invention;

[0027] Figure 5 is a timing diagram of a response manager responding to a user request according to an embodiment of the present invention;

[0028] Figure 6 is a functional schematic diagram of operating a response manager adding a data file generator according to an embodiment of the present invention;

[0029] Figure 7 is a structural block diagram of a shift management system generated according to a preferred embodiment of the present invention;

[0030] Figure 8 The figure is a flowchart of a method for implementing a response manager for shift management according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] The general idea of ​​the present invention is that in the process of shift management, the affairs that need to be managed will be elementized and then classified, managed and associated. Therefore, a systematic system device is established to establish a classification framework; another systematic device is established to manage the content of this framework; at the same time, the functions of the system device are used to improve themselves in the process of content management, and an interactive system device that interacts with the outside world and a system device that automatically handles business are established. In this way, more resources can be provided to management users, classification reuse can be achieved, and it can be used in a variety of scenarios with different requirements, making maintenance more intuitive and management more flexible.

[0032] For basic shift management, there are two important factors for shift scheduling, namely: personnel and date. Simply put, the shift management is realized by establishing a corresponding relationship between personnel and date that meets the requirements. In order to establish this connection, personnel and date are classified separately, namely personnel module and work date module. One person corresponds to one personnel module, and one work date corresponds to one work date module. For the characteristics of the personnel module, the module label is used for management. That is, a personnel module includes multiple labels. According to the at least required characteristics in the shift management, a personnel module requires at least 4 sets of labels, namely, name, number, work type and work date; the value of the work date label of a personnel module corresponds to the work date module, which completes the shift scheduling of this person in a certain period. Similarly, a work date module requires at least 5 sets of labels: name, time period, date, work type, and person list. The personnel list label in a work date module corresponds to the personnel module, which completes the work arrangement of the person on this work date.

[0033] Therefore, the shift management device involves two modules: a personnel module and a working time module. The structure of each module includes one or more groups of tags, and a group of tags includes a tag name and a tag content. Multiple modules with the same structure are included in a module container. Modules in different containers can be bound to each other to establish a corresponding relationship. Multiple personnel modules are managed by a personnel module container, and multiple working time modules are managed by a working time module container.

[0034] In the present invention, a system manager is provided, such as Figure 1 As shown, the system manager includes: 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 the containers, modules and labels in the shift management device.

[0035] The specific implementation of the present invention is further described in detail below with reference to the accompanying drawings.

[0036] 1. Container Manager

[0037] In the present invention, a device is designed to accommodate multiple transactions belonging to the same category. This device is a container. For scheduling, two basic information, personnel and working hours, are required. Therefore, these two basic information are processed into modules and installed in the container. The device for managing this container is a container manager. The container manager is mainly composed of the following parts: a content manager that manages the contents of the container and the modules under the container according to the response instructions, and a space manager that determines the size of the container and performs space management.

[0038] like Figure 2 The container manager structure diagram implemented by the present invention is shown, and the specific implementation is as follows:

[0039] Step S201: define the container. In this step, the container manager determines to generate a container, assigns a value to the container name, and determines the container size. The container name is used to uniquely identify the container, and the container size is used to determine how many modules can be accommodated in the container. The name and size are the basic characteristics of the container. At the same time, the size of the container can determine that each module in the container has a continuous serial number. This serial number can also be used to specify a module. For example, container name.[i] represents the i-th module in the container.

[0040] In addition, the container manager can add other features to the container according to needs, such as region, color, etc. For example: in the shift management scenario, use the container manager to generate two containers:

[0041] Container 1: Name = Personnel Module Container

[0042] Size = 5

[0043] Region = Beijing / / Custom Features

[0044] The size = 5, which means that this container includes 5 personnel modules, and the region = Beijing, which means that the subsidiary features of this container include regions, and the region of the personnel module is Beijing.

[0045]

[0046]

[0047] Container 2: Name = Work Time Module Container

[0048] Size = 20

[0049] No. 1 No. 2 No. 3 No. 4--19 No. 20 Modules Modules Modules Modules Modules

[0050] Step S202: The container manager manages the contents of the container, including adding contents. In this step, the contents of the container, i.e., modules, can be added. The structure of the module is as follows: Figure 3 As shown, a module includes multiple tags.

[0051] For example, in the scenario of shift management, the personnel module involved has at least 4 sets of tags, which are: name, number, work type, and work date list. Another module related to the shift management scenario is the working time module, which has at least 5 sets of tags, which are: name, time period, date, work type, and personnel list.

[0052] When adding content management to the container in step S202, a module of content is added to the container. 1. Adding a personnel module to the personnel module container: In step S201, the number of personnel modules is defined as 5.

[0053] You can add the contents of 5 personnel modules to this container and specify the size of the module.

[0054] That is, the number of tags of the module. For example, the number of tags of the personnel module is 4 groups:

[0055]

[0056] 2. Add the working time module to the working time module container:

[0057] In step S201, the size of the working time module container is defined as 20, then 20 modules are generated in the container, and the module size is 5 (5 sets of tags per module). In the following table, 20 modules are added (modules numbered 4 to 19 are ignored in the table)

[0058]

[0059]

[0060] Step S203: When the container is generated, the number of modules, that is, the size of the container, is determined. This step is the space management of the container and increases the size of the container.

[0061] Step S204: This step is for container content management. A module with a certain serial number in the container or a module with a tag name of a certain value is deleted. After deletion, the size of the container does not change, but the content of the specified module is empty.

[0062] Step S205: This step is for the space management of the container. If the specified module position of the specified space is empty, the space can be reclaimed. The module serial number after recycling is changed accordingly. For example, there are 5 modules in the container, and "container name.[i]" can be used to point to them. If "container name.[3]" deletes the content and deletes the space, the original "container name.[4]" and "container name.[5]" will automatically change to "container name.[3]" and "container name.[4]".

[0063] Step S206: This step is the space management of the container. The specified existing container is used as the source container, and a new container is created as the target container. The structure, module, module label structure, and label content of the target container are copied to the source container. Before copying, you can select the module and module label to be copied. In the copy operation, the structure of the container, module, and label needs to be copied in full, the module content to be copied can be selected, and the label content can be selected. For example:

[0064] 1) Copy "source container name.[i]-[j].[label name 1, label name 3]" to the new container, that is, copy the module structure, label quantity, and label name of the source container name to the new container, and copy the label contents of label name 1 and label name 3 in the modules with sequence numbers [i] to [j] in the source container name to the new container;

[0065] 2) Copy "source container name.[all].[all]" to the new container, that is, copy all the contents of all modules of the source container name to the new container;

[0066] 3) Copy "source container name.[0].[0]" to the new container, that is, copy the structure (label and label name) of the source container name module to the new container;

[0067] 2. Tag Manager

[0068] After defining the container in the container manager and determining the size, the specific content of the container - the module - can be managed through the tag manager.

[0069] The tag manager includes at least three functional devices: a definition module, an assignment module and a binding module.

[0070] Among them, the definition module and the assignment module can be used for the management of tag content, including definition, assignment, and deletion;

[0071] The binding module is used to extract the tag content of the tag name corresponding to the module that meets the conditions in the specified container, and send the content that meets the requirements to the binding module for further extraction and use.

[0072] Now combined Figure 3Describes the management of modules in the container by the tag manager, as well as the device by which the personnel module container and the working time module container in the shift management are managed in the tag manager.

[0073] Step S301 - Tag definition: In this step, the tag manager defines the tag name and the assignment rules of the tag content corresponding to the name in the module;

[0074] For example, in the scenario of shift management, you need to define labels for the personnel module in the personnel module container and the working time module in the working time module container. After the labels are defined, the personnel module container and the working time module container are as follows:

[0075]

[0076]

[0077] Step S302 - Tag deletion: In this step, the tag manager deletes a tag group in all modules in the specified container;

[0078] Step S303 - Tag assignment: assign values ​​to the tag contents corresponding to the tag names under the specified modules:

[0079] For example, in the shift management scenario, there are two working time systems, day shift and night shift. Five people are involved in the shift scheduling, of which three (A, B, C) are involved in the day shift and two (D, E) are involved in the night shift.

[0080] First, we need to assign values ​​to the basic information of the personnel module. Before determining the specific information of the shift schedule, we need to assign the basic information first. The personnel module container after assignment is as follows:

[0081]

[0082] Now schedule the shifts for 10 days. After assigning values ​​to the working time module, the contents of the working time module container are as follows (numbers 4 to 18 are omitted in the figure below)

[0083]

[0084]

[0085] Step S304 - Binding Data: Binding data is a function implemented by the module of the tag manager: the binding module. The binding module has a separate functional block: the binding loader, which extracts the corresponding tag content according to the module where the tag name of the specified tag content is located, and prepares it for the next step. In the binding module, the extracted data can be selected.

[0086] For example: In the scenario of shift management, it is necessary to assign values ​​to the working date labels of each personnel module in the personnel module container, and the assigned values ​​are one or more working time modules that meet the requirements from the working time module container; at the same time, it is necessary to assign values ​​to the personnel list labels in the working time module container, and the assigned values ​​are one or more working time modules that meet the conditions from the personnel module container.

[0087] 1) Assignment of work date tag in personnel module:

[0088] a) Select the personnel module to be assigned a value, and extract the content of the work type label. For example, the work type of the personnel module with the label name "name" and the corresponding label content "A" is the day shift;

[0089] b) The parameter content includes: work type = day shift, container = work time module container, output label = name. The binding loader extracts the "work type = day shift" module from the "work time module container" according to the parameter content, and extracts the label content with label name = "name" as the output content of the binding loader. The parameter content can also be additionally defined in the parameter protocol, such as limiting the number of contents transmitted, limiting the content assigned to the corresponding label of the output module, etc.

[0090] c) According to the operation of step b), the output of the binding loader is

[0091] "Working date module container.[name = '7-1 day shift'], working date module container.[name = '7-2 day shift'], working date module container.[name = '7-3 day shift']"

[0092] d) The binding module calls the assignment function of the assignment module and assigns the output content of step c) to the personnel module container. [Name = 'A']. Work Date

[0093] e) While the operation of step d) is in progress, the label contents of work date module container.[name='7-1 Day Shift']. Personnel list, work date module container.[name='7-2 Day Shift']. Personnel list, and work date module container.[name='7-2 Day Shift']. Personnel list are appended, and the appended value is personnel module container.[name='A'].

[0094] 2) Assignment of staff list labels in working time module:

[0095] The active assignment method is the same as the personnel module container assignment method. For the case of mutual binding assignment, each assignment operation corresponds to the labels of the two containers.

[0096] In this example, 3 people (A, B, C) work on the day shift, and 2 people (D, E) work on the night shift. After binding and assigning values ​​without any other additional conditions, the content of the personnel module container is:

[0097]

[0098] The contents of the working time module container are as follows (numbers 4 to 18 are omitted in the figure below)

[0099]

[0100] The binding loader can also extract various data from each container according to different requirements. Therefore, in actual applications, the binding loader can be applied according to this feature and processed again to meet different requirements. For example, in the scenario of shift management, the existing resources are processed again to generate a shift determination module, a personnel shift storage module, a work time shift storage module, and a shift table generator:

[0101] Scheduling determination module: This module can use the binding loader to extract relevant information of the personnel module and the working time module, and determine the correspondence between each personnel module and the working time module, that is, the working hours of the personnel module and the personnel list of the working time module are displayed to the user and can be adjusted by the management personnel. After the adjustment is submitted, the label content of the relevant modules will be refreshed.

[0102] Personnel scheduling storage module: The label content corresponding to the work date label in the personnel module is one of the devices for storing the scheduling method. After the scheduling is determined, it is necessary to show the user the scheduling content based on the personnel query. The personnel scheduling storage module can be used to extract the corresponding relationship related to the valid personnel scheduling at that time, and display it simply and clearly. It can also be stored in response to the administrator's instructions. It can be stored on the disk in the form of a file. The file can be a text file or a table file. You can also use the container manager to create a new container and a new module to store and record the scheduling information table for a certain time period. Through the personnel scheduling storage module, it is easier to call the effective schedule, improve the viewing efficiency, and simplify the operation method.

[0103] Working time scheduling storage module: The label content corresponding to the personnel list label in the working time module is another device for storing the scheduling method. After the scheduling is determined, it is necessary to show the user the scheduling content based on the date query. The working date scheduling storage module can be used to extract the corresponding relationship related to the scheduling that is effective at that time, and display it simply and clearly. It can also be stored in response to the administrator's instructions. It can be stored on the disk in the form of a file. The file can be a text file or a table file. You can also use the container manager to create a new container and a new module to store and record the scheduling information table for a certain time period. Through the working date scheduling storage module, it is easier to call the effective schedule, improve the viewing efficiency, and simplify the operation method.

[0104] Schedule generator: The display method of the corresponding relationship between the modules in the personnel module container and the working time module container can be determined by the management personnel and formed into a template. The schedule generated according to this template at different stages can be stored in a newly created container or stored on the disk in the form of a file.

[0105] 3. Response Manager

[0106] The response manager is used to define the specifications for transmitting and processing the client information, and to receive and specify the processing device and a group of devices for processing the data packets from the client.

[0107] Attached Figure 4 This is a structural diagram of the response manager. As shown in the figure, part of the response manager's devices are located in the container manager: the response data definer and the response data decoding manager; there are also devices outside the container manager, such as the response data encoding manager between the user end and the container manager.

[0108] 1. Response data definer: The rules for data management of container managers and tag managers, the protocols for data transmission encapsulation, encoding and decoding methods, and specifications are defined by users and implemented through the response data definer. User-defined rules and specifications refer to the configuration of data types, including the name and flags of the response subject, the operations that the response subject can perform, the flags corresponding to the operations, the objects of the operations, and the contents of the operations.

[0109] 1) The data structure specification configured by the user shall include at least the following:

[0110]

[0111] Table 1

[0112] The information in Table 1 is the most basic operations that can be performed by the container manager and tag manager.

[0113] The specifications for data information encapsulation may include json format, xml format, etc.

[0114] In the response data definer, there is a built-in output identifier OUT. Under this identifier, the user can also configure the output specification.

[0115] As shown in the following table:

[0116]

[0117] Table 2

[0118] In addition, the response data definer provides output of the operation results for each user-defined data specification.

[0119]

[0120] Table 3

[0121] 3) User configuration can be implemented using management platforms, applications, etc.;

[0122] The result of user configuration can be stored in a database or a file. The result reflects the correspondence between the operation identifier, the response subject, the operation content, the operation object, and the structure of the data packet that previously contained the above information.

[0123] For example, to implement the function of adding a module to a container, the management user can define the following structure in the response data definer: add—Container Manager—Container Name.Module Name [Number of Labels], and specify the structure of the data packet. For example, the structure is defined as:

[0124] Packmsg = [{"oper":"add"},{"obj":"container name.module name"},

[0125] {"content":"[{"LabelSize":number of labels}]"}]

[0126] User-configured processes, such as Figure 4 The link S401 in the response manager structure diagram shown in the figure sends the function to be implemented, the data information to be submitted for implementing the function, and the packaged structure of the data information to the response data definer for management.

[0127] When the administrator submits data specifications on the user side, the response data definer can provide the above information to the user side for data preparation, and process the user side information into a data packet structure that complies with the specifications through the response data encoding manager and send it to the response manager.

[0128] 2. Response Data Encoding Manager: It is used to uniformly receive the operation data of each user end, load the configuration data of the response data definer, process the operation data of the user end into a data packet that meets the specifications, and send it to the response manager. The function implemented by this device is between the user end submitting data and the container manager receiving data. The location of the device can be placed in the user end, the container manager, or according to the following conditions: Figure 4 As shown, placed in an independent middle layer.

[0129] 1) In step S402, the user initiates a data request, which can be submitted through the form format of the existing system web page, or submitted by the existing mobile terminal APP through a custom protocol or HTTP, websocket. The response data encoding manager converts the data information under the original data protocol of the user to meet the cross-platform and cross-protocol functions of the container manager and related managers, and can meet its adaptation to various existing environments.

[0130] 2) In step S403, the response data encoding manager extracts data specifications from the response data definer to prepare for conversion of the data obtained in step S402. This step can be to extract complete data from each response data definer once when the service is loaded, or to push incremental data to the response data encoding manager once when the specification of the response data definer is updated, or each time the user sends data to the response data encoding manager, the response data encoding manager extracts the required data from the response data definer.

[0131] 3) In step S404, the response data encoding manager sends the converted data packet to the response data decoding manager.

[0132] 3. Response Data Decoding Manager: It is used to receive data packets, split the data packets according to the response data definer used to manage the user's configuration results for data, and send instructions to the response body specified in the data packet.

[0133] 1) In step S407, the response data decoding manager extracts data specifications from the response data definer to prepare for the conversion of the data obtained in step S404. This step can be to extract complete data from each response data definer when the service is loaded, or to push incremental data to the response data decoding manager when the response data definer generates specification updates, or to extract the required data from the response data definer after obtaining the data from step S404.

[0134] 2) Step S404: After the response data encoding manager converts the data packet, it uniformly transmits the data to the response data decoding manager, which decodes, analyzes and distributes the information.

[0135] 3) Steps S405 and S406: Based on the data structure specification obtained from step S407, determine the response subject to be processed. If the response subject is a container manager, the operation to be processed and the specific content are sent to the container manager. If the response subject is a tag manager, the operation to be processed and the specific content are sent to the tag manager.

[0136] Next, the processing scheme of the response manager is described in the embodiment of shift management:

[0137] ·Managers define specifications in the response data definer

[0138] The operations defined by the specifications can be redefined by developers through secondary development, or a management platform can be provided for managers to enter data according to the rules.

[0139] The entered specifications are shown in Tables 1 and 2.

[0140] ·Response Manager Processing Flow

[0141] Units that need shift management currently have a human resource management system that has two modes: APP and web page, which use the original data protocol submitted by web form and APP respectively.

[0142] The current processing content is to add a personnel module with 4 label groups in the shift manager:

[0143] The data part of the web form submission information:

[0144] "oper=add&obj="personnel module container"&LabelSize=4"

[0145] The data part of the information submitted by the APP:

[0146] “param={"oper":"add","obj":"personnel module container","LabelSize":"4"}”

[0147] (1) Response data encoding manager: Request data with the response data definer, extract the data content in Table 1 and Table 2, and convert the data information under the above two specifications into a unified data packet:

[0148] Packmsg = [{"oper":"add"},{"obj":"personnel module container"},

[0149] {"content":"[{"LabelSize":4}]"}]

[0150] After successful conversion, the data is submitted to the response data decoding manager of the response manager.

[0151] (2) Response Data Decoding Manager: Receives the data packet from the Response Data Encoding Manager and parses it to obtain the result:

[0152] Operation subject: Container manager

[0153] Operation: add

[0154] Operation object: "Staff module container"

[0155] Operation content: Add a module to the container, where the number of module tags is 4

[0156] After the response data decoding manager identifies the operation subject as the container manager, it sends the parsed result to the container manager to process the related operations.

[0157] Container Manager can perform the following operations:

[0158] In the shift management scenario, some of the operations that can be performed by the container manager and the corresponding data package information are as follows:

[0159]

[0160]

[0161] In the shift management scenario, some of the operations that can be performed by the tag manager and the corresponding data package information are as follows:

[0162]

[0163]

[0164] For more flexible application, some basic operations can also be defined:

[0165]

[0166]

[0167] Next, combine Figure 5 , that is, the response manager implemented by the present invention responds to the user request timing diagram, and the steps of the response manager in the use process are described:

[0168] Step S501: This step is a data preparation step of the embodiment. The user end here refers to the maintenance user, including the administrator of the enterprise, and may also include the programmer of secondary development, who initiates a data configuration request to the response data definer. This step can be implemented by initiating a request through the web or APP platform, or through a secondary development program or script. Therefore, the user end of this step includes the web and APP terminals, and also includes the application end that can be used for secondary development, etc.

[0169] Step S502: The response data definer triggers step S502 according to the request of step S501, performs data configuration in the server, and prepares data for the application. After this step is completed, the configuration result can be provided to the response data encoding manager and the response data decoding manager for loading. The loading method can be pushed to the response data encoding manager and the response data decoding manager after this step is completed, or as in steps S504 and S507, after the demander initiates a request to load the configuration, the configuration result is pushed.

[0170] Step S503: In this step, the administrator initiates a request at the user end, and the data protocol of the request may only comply with the user end rules. After the data information is converted in the response data encoding manager, it is sent to the response data decoding manager through step S505.

[0171] Step S506: Through this step, the elements of the content to be processed by the user and the response body of the processing operation are parsed, and the content to be processed is sent to the corresponding response body through step S508 or S509.

[0172] In the above embodiments, the operation requests from the user end processed by the response manager are basic data requests, that is, one operation is processed per request. However, in actual management requirements, a large number of records and operations need to be processed.

[0173] For example, you need to schedule 100 employees for 365 days. Therefore, the management experience and work efficiency of managers are very poor if the schedule is processed one by one. In this case, the response manager also provides a batch processing solution, namely: operating data files.

[0174] In addition to the default data packet specifications in the operation data file, users can add extended data packet specifications in the response data definer. For example:

[0175] 1) Multiple operation data distinction rules: The response data encoding manager can identify multiple data, and the distinction method can be configured by the administrator, including: separators, data specification identifiers, etc.;

[0176] 2) Size of the operation data file: The response data encoding manager processes the file size by default to adapt to the waiting time of the operation user experience. The management user can also define the file size through the response data definer;

[0177] In the operation data file, data can be identified in json or xml.

[0178] In the shift management scenario, you can define the following data specifications for operation data files:

[0179] Packmsg={"contentFilename":"filename.txt"};

[0180] The content of filename.txt can be:

[0181] {"oper":"LabelAssign","obj":"PackUser.[1-5].[Name]","content":"A;B;C;D;E"}

[0182] After receiving the above operation data file, the response data encoding manager can parse it into 5 operation instructions:

[0183] Packmsg={"oper":"LabelAssign","obj":"PackUser.[1]","content":[{"LabelName":"Name","LabelValue":"A"}]}

[0184] …

[0185] Packmsg={"oper":"LabelAssign","obj":"PackUser.[5]","content":[{"LabelName":"Name","LabelValue":"E"}]}

[0186] The parsed instructions are sent to the response data decoding manager to allocate the response body and specific operations.

[0187] In order to determine the specification accuracy of the operational data files processed by the response data encoding manager, the response manager also includes an operational data file generator.

[0188] like Figure 6 As shown, the operation data file generator is placed between the user end and the response data encoding manager, and its implementation method can be a web page.

[0189] In step S601, the operation data file generator obtains relevant data specifications from the response data definer;

[0190] In step S602, the user can select the operation to be performed on the web page and batch input the information to be operated, such as user name and date, and the response data definer processes the information into an operation data file that meets the specifications;

[0191] In step S603, the operation data file is sent to the response data encoding manager, which splits and parses the operation data file according to the data specification obtained from the response data definer in step S604, and sends it to the response data decoding manager in batches or one by one through step S605.

[0192] from Figures 2 to 6 The devices and processes shown in the figure are managed around the modules in the container. The system manager that implements all management, such as Figure 1 As shown, it includes: a container manager, a tag manager, a binding loader and a response manager, wherein the binding loader realizes the function of associating various modules.

[0193] Use the container manager for framework construction, the tag manager for data construction, the binding loader for data processing, the response manager for interaction, and the logic flow calculator for business processing. And use the components of the system manager to establish a shift manager, in which the shift scheduling of personnel and time is realized. The device structure is as follows Figure 7 shown.

[0194] Figure 7 1 is a structural diagram of a shift manager generated according to a preferred embodiment of the present invention. Figure 7 As shown, the device includes 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 determination module for determining the correspondence between each of the personnel modules and the working time module and the binding relationship between each of the working time modules and the personnel module; a personnel scheduling storage module for responding to a first specified operation and storing all working time modules bound to the personnel module corresponding to the first specified operation; a working time scheduling storage module for responding to a second specified operation and storing all personnel modules bound to the working time module corresponding to the first specified operation; a scheduling table generator for responding to a third specified operation and combining the information of the personnel scheduling storage module and the working time scheduling storage module to generate the required scheduling table.

[0195] like Figure 8 As shown, the process of the method for implementing the response manager of the shift management includes the following steps:

[0196] Step S801: The first step is to perform response data definition management, which is used to define the user's configuration of data encapsulation rules, including the name and mark of the response subject, the operations that the response subject can perform, the mark corresponding to the operation, the object of the operation, and the operation content of the operation on the object;

[0197] Step S802: If the user's operation content is a batch operation, then enter this step: Operation data file management: obtain the batch operation data submitted by the user from the user end, process it into an operation data file that meets the specifications according to the configuration, and then perform response data coding management;

[0198] Step S803: Operation data files and single operation instructions from users can enter this step: response data encoding management, uniformly receiving operation data submitted by various user terminals, loading the configuration of the response data definer, processing the operation data into a data packet that conforms to the configuration, and sending it to the response manager;

[0199] Step S804: The data processed by step S803 are all subjected to response data decoding management: receiving a data packet that conforms to the configuration, splitting the data packet according to the configuration of the response data definer for data encapsulation rules, and sending instructions to the response body specified in the data packet.

[0200] In the existing enterprise management, it is necessary to integrate the original management platform, support diversified platform systems, and support data flow. Through the present invention, data under different systems and different specifications can be interoperable on the basis of paying less management cost. In addition, in the system management device and system management method for shift management, the data entry and specifications are unified, and a multi-user processing solution is provided, making management and maintenance more efficient and convenient.

[0201] The above disclosures are only several specific embodiments of the present invention; however, the present invention is not limited thereto, and any changes that can be conceived by a person skilled in the art should fall within the protection scope of the present invention.

Claims

1. A device for implementing a response manager for shift management, characterized in that: Includes Response Manager; The response manager is used to define the specifications for transmitting and processing user-side information, and receive data packets from the user-side and designate a processing device to process the data; The response manager further includes: a response data definer, a response data encoding manager and a response data decoding manager; wherein the response data definer is used to implement the user's configuration of data encapsulation rules, including the name and mark of the response subject, the operations that can be performed by the response subject, the mark corresponding to the operation, the object of the operation, and the operation content of the operation on the object; The response data encoding manager is used to uniformly receive the operation data submitted by each user terminal, load the configuration of the response data definer, process the operation data into a data packet that conforms to the configuration, and send it to the response data decoding manager; wherein the operation data submitted by the user terminal includes: a response body, and operation data specified by the response body, wherein the data content of the specified operation data includes: the type of response operation, the operation object, and the operation content; The type of the response operation is used to mark different response subjects and corresponding operation flags, wherein the response subject includes: container manager: the container manager is composed of the following parts: a content manager that manages the contents of the container and the modules under the container according to the response instructions, and a space manager that determines the size of the container and performs space management; a tag manager: a module used to perform specific management of the specific content of the container, including three functional devices: a definition module, an assignment module, and a binding module; The operation flag is used to mark the operation mode, including: define, delete, assign, and bind; The operation object is used to mark the object to be operated and the object name, including: container, module, label; The operation content is used to retrieve data content and maintain data content when operating the operation object; The response data decoding manager is used to receive a data packet that conforms to the configuration, split the data packet according to the configuration of the response data definer for data encapsulation rules, and send instructions to the response subject specified in the data packet; The operation content includes: when the operation involves retrieval, the tag name value and / or tag content value corresponding to the retrieval condition involved; The operation content also includes: when the operation involves output, the tag name value and / or tag content value corresponding to the output content involved; The operation content includes: data information specifications when the operation involves retrieval, and data specifications of output results when the operation involves output.

2. The device according to claim 1, characterized in that The data specification includes: json format.

3. The device according to claim 1, characterized in that: The operation data received by the response data encoding manager includes: an operation data file; wherein the operation data file includes a plurality of operation data.

4. The device according to claim 3, characterized in that Also includes: Operational data file generator; The operation data file generator obtains the configuration of the data encapsulation rule from the response data definer; The operation data file generator obtains batch operation data submitted by the user from the user terminal, and processes it into an operation data file that complies with the specification according to the configuration; The operation data file generator submits the operation data file to the response data encoding manager.

Images