Distributed organization data construction method and organization data construction background
Through the decentralized organizational data construction method and organizational data construction backend, the complex and time-consuming problems of traditional methods are solved, and the rapid generation and flexible maintenance of organizational charts are realized, and the efficient sign-up process for leave requests is supported to adapt to rapidly changing organizational needs. .
Patent Information
- Application Number
- CN202411282485.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-09-13
- Filing Date
- 2024-09-13
- Publication Date
- 2025-01-03
AI Technical Summary
Traditional corporate organizational graph generation methods are complex, time-consuming and lack flexibility, difficult to adapt to rapidly changing organizational structures and globalization needs, and do not support automation tools, resulting in difficulty in data integration and maintenance.
The decentralized organizational data construction method is adopted to distribute the organizational data generation to everyone. Through the organizational data construction backend, data modules, transceiver modules and pairing modules are used to generate and integrate organizational unit data, and support the signing process of leave requests.
Reduces time and labor for organizational graph generation and maintenance, increases flexibility, enables rapid adjustment and configuration of organizational structures, and simplifies data processing with cloud computing and artificial intelligence.
Smart Images

Figure CN119250660A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a distributed organization data construction method and an organization data construction background, and in particular to a method and a background that can distribute the work of constructing organization data to multiple people and facilitate the signing and approval of leave applications. Background Art
[0002] In the previous technology, the method for a company to generate an organizational chart usually involves multiple steps and is relatively cumbersome. First, the method usually requires collecting data from various departments, and the data formats and structures of these departments may vary, which increases the complexity of integrating data. In addition, when the company's organizational structure changes, such as the establishment of new departments or the transfer of employees, the traditional method requires manual updating of this information, which often causes errors and delays.
[0003] Furthermore, the organizational structure of larger companies usually involves multiple levels, multiple departments and a large number of employees, which makes drawing and maintaining organizational charts a very time-consuming and labor-intensive task. In addition, traditional organizational charts often lack flexibility and may face difficulties when they need to be adjusted or reconfigured quickly.
[0004] Furthermore, as organizations expand and globalize, the requirements for organizational charts become more complex, making it difficult for traditional methods to meet the rapidly changing organizational needs. Finally, because traditional methods generally do not support automated or semi-automated tools and processes, they cannot fully utilize current technological developments, such as cloud computing, data analytics, and artificial intelligence, to simplify and optimize the generation and maintenance of organizational charts.
[0005] In summary, the traditional method of generating organizational charts for companies has various inconveniences and limitations, which has prompted researchers and engineers to seek more advanced and effective methods to solve these problems. Summary of the invention
[0006] The main purpose of the present invention is to provide a distributed organizational data construction method, which can distribute the work of constructing organizational data to multiple people.
[0007] Another object of the present invention is to provide a distributed organizational data construction method that can facilitate the approval of leave requests.
[0008] To achieve the above-mentioned purpose, the present invention provides a distributed organization data construction method, which is applied to an organization data construction background. The distributed organization data construction method includes:
[0009] (A) generating a plurality of organizational unit data, wherein each organizational unit data comprises at least a primary column and a secondary column;
[0010] (B) transmitting the plurality of organizational unit data to a plurality of different working devices;
[0011] (C) receiving a plurality of filled-in organizational unit data, wherein the plurality of filled-in organizational unit data is transmitted by the plurality of working devices;
[0012] (D) Matching the current level fields and the upper level fields in the plurality of filled organizational unit data to generate an organizational chart.
[0013] The present invention provides an organizational data construction background for generating an organizational chart. The organizational data construction background includes:
[0014] A data module, for generating a plurality of organizational unit data, wherein each organizational unit data includes at least a primary column and a higher column;
[0015] A transceiver module, used for transmitting the plurality of organizational unit data to different plurality of working devices, and receiving a plurality of filled-in organizational unit data, wherein the plurality of filled-in organizational unit data is transmitted by the plurality of working devices;
[0016] The matching module is used for matching the current level fields and the upper level fields in the plurality of filled organizational unit data to generate the organizational chart.
[0017] The features, advantages, or similar expressions mentioned in this specification do not mean that all features and advantages that can be achieved by the present invention should be included in any single specific embodiment of the present invention. Instead, it should be understood that the expressions related to features and advantages mean that the specific features, advantages, or characteristics described in conjunction with the specific embodiment are included in at least one specific embodiment of the present invention. Therefore, the discussion of features and advantages, and similar expressions in this specification is related to the same specific embodiment, but it is not necessary.
[0018] These features and advantages of the present invention may be more clearly understood by referring to the following description and the appended claims or by utilizing the embodiments of the present invention as set forth below. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The present invention and its features, appearance and advantages will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings. The same reference numerals indicate the same parts in all the drawings. The drawings are not drawn to scale, and emphasis is placed on illustrating the subject matter of the present invention.
[0020] Figure 1 A conceptual diagram for organizing data in traditional ways;
[0021] Figure 2 A conceptual diagram of the distributed organization data construction in the present invention;
[0022] Figure 3 A schematic diagram of the structure of the background for organizing data construction in a preferred embodiment of the present invention;
[0023] Figure 4 A method flow chart of a distributed organization data construction method in a preferred embodiment of the present invention;
[0024] Figure 5 A method flow chart of a distributed organization data construction method in another preferred embodiment of the present invention;
[0025] Among them, 30 is the organization data construction background, 40a~40n are n working devices, 301 is the data module, 302 is the transceiver module, 303 is the pairing module, 304 is the judgment module, 3011a~3011n are the organization unit data, and 401a is the leave request. DETAILED DESCRIPTION
[0026] In order to make the description of the disclosed content more detailed and complete, the following is an illustrative description of the implementation and specific embodiments of the present case; however, this is not the only form of implementing or using the specific embodiments of the present invention. The implementation covers the features of multiple specific embodiments and the method steps and sequences used to construct and operate these specific embodiments. However, other specific embodiments can also be used to achieve the same or equal functions and step sequences.
[0027] It should be noted that, unless otherwise specified, all functions described herein may be implemented in hardware or as software instructions that enable a computer to perform predetermined operations, wherein the software instructions are implemented in a computer-readable storage medium, such as RAM, a hard drive, flash memory, or other types of computer-readable storage media known to those skilled in the art. In some embodiments, the predetermined operations of the computer are performed by a processor, such as a computer, or a program code such as a computer program code, software, firmware, and in some embodiments, by an integrated circuit encoded to perform these functions. In addition, it should be understood that the various operations described herein as being performed by a user may be performed manually by the user, or may be performed automatically with or without instructions provided by the user.
[0028] The present invention proposes a distributed organization data construction method and an organization data construction background, in particular, a method and a background that can distribute the work of constructing organization data to multiple people and facilitate the signing and approval of leave applications.
[0029] Figure 1 A conceptual diagram of the traditional way of organizing data. Figure 1As shown in the figure, in a traditional organization, such as a company, there are several or even dozens of levels from the top supervisor to the bottom employee. The personnel in each level can also be composed of a few people, dozens, hundreds, or even tens of thousands of people. The most traditional and common method of constructing organizational data is to have one or more human resources department staff in the company be responsible for construction and maintenance. Figure 1 For example, the outermost box represents the scope of organizational data that one or several staff members need to maintain in the traditional method. Therefore, it is conceivable that the larger the company's organizational structure, the more levels, departments, and employees it usually involves, which makes drawing and maintaining an organizational chart a very time-consuming and labor-intensive task. In addition, traditional organizational charts often lack flexibility and may face difficulties when they need to be adjusted or reconfigured quickly.
[0030] Figure 2 FIG. 1 is a conceptual diagram of the distributed organization data construction in the present invention. Figure 2 As shown, in the present invention, the construction work of organizational data is distributed to each member of the organization in a decentralized manner, so that each member only needs to undertake a small part of the construction work to obtain all the organizational data of the entire organization. Finally, the complete organizational data is integrated through the organizational data construction background, for example, output as an organizational chart. Figure 2 In the example, each box means that each member only needs to help input their own and other related data (which will be described in detail later) to complete a small part of the workload, and finally integrate everyone's input data to construct the complete organization data. Figure 1 and Figure 2 The size of the boxes in the figure can give you a rough idea of the difference in workload between the two methods. In a large enterprise with tens of thousands of employees, the difference in data volume between the two methods is even greater for the people responsible for inputting organizational data.
[0031] Please also refer to the following instructions Figure 3 and Figure 4 ,in Figure 3 This is a schematic diagram of the structure of the background for organizing data construction in a preferred embodiment of the present invention. Figure 4 It is a method flow chart of a distributed organization data construction method in a preferred embodiment of the present invention.
[0032] In the application of the present invention, the organization data construction background 30 will be connected to each work device 40a-40n in the company, whether it is directly electrically connected or connected through a network. The work device 40a-40n can be, for example, a mobile device, a laptop, a desktop, a tablet computer or a smart phone, etc. The organization data construction background 30 includes: a data module 301, a transceiver module 302, a pairing module 303 and a judgment module 304. The functions of each module are briefly described below. Among them, the data module 301 is used to generate a plurality of organization unit data 3011a-3011n, wherein each organization unit data includes at least one level field and one upper level field. In the embodiment of the present invention, the current level field or the upper level field must include at least one data that can be used to identify the object, such as a work number or a telephone extension number, but the present invention is not limited to this. For example, in one embodiment of the present invention, the current level field includes the name and work number of a filler, and the upper level field includes the name and work number of a superior corresponding to the filler. In another embodiment, the current level field includes a name and telephone extension number of a filler, and the superior level field includes a name and telephone extension number of a superior person corresponding to the filler.
[0033] In another embodiment of the present invention, the organization data construction background 30 may not be provided with the data module 301, and the plurality of organization unit data 3011a-3011n may be generated by themselves on different plurality of working devices 40a-40n, for example, the working device 40a generates the organization unit data 3011a, the working device 40b generates the organization unit data 3011b, and the working device 40n generates the organization unit data 3011n. After the fillers of the working devices 40a-40n respectively fill in the organization unit data 3011a-3011n, the working devices 40a-40n transmit the filled organization unit data 3011a-3011n to the transceiver module 302 of the organization data construction background 30.
[0034] The transceiver module 302 is used to transmit the above-mentioned multiple organization unit data 3011a-3011n to different multiple work devices 40a-40n, and receive multiple filled-in organization unit data 3011a-3011n, wherein the multiple filled-in organization unit data 3011a-3011n are transmitted by multiple work devices 40a-40n, for example, the work device 40a transmits the organization unit data 3011a, the work device 40b transmits the organization unit data 3011b, and the work device 40n transmits the organization unit data 3011n. In another embodiment of the present invention mentioned above, since the multiple organization unit data 3011a-3011n are generated by themselves on different multiple work devices 40a-40n respectively, the transceiver module 302 does not need to transmit the above-mentioned multiple organization unit data 3011a-3011n to different multiple work devices 40a-40n, and only needs to receive the multiple filled-in organization unit data 3011a-3011n transmitted from the multiple work devices 40a-40n.
[0035] The matching module 303 is used to match the current level fields and the upper level fields in the plurality of filled-in organizational unit data 3011a-3011n to generate an organizational chart.
[0036] In other embodiments of the present invention, when a work device needs to ask for leave, the transceiver module 302 can receive a leave form 401a sent by a leave work device among the work devices 40a-40n (for example, assuming that work device 40a needs to ask for leave), and the leave form 401a includes at least the leave type and the number of days. The judgment module 304 is used to send the leave form 401a to at least one superior work device among the plurality of work devices 40a-40n (assuming that work device 40c is the superior of work device 40a) according to a leave condition, wherein the leave condition includes at least: leave type and the number of days. The judgment module 304 will determine the number of levels that need to be approved based on the leave type and the number of days. In other words, how many levels of superiors need to approve the leave form. The types of leave can include: special leave, personal leave, sick leave, bereavement leave, maternity leave, etc.; the number of days is the number of days the applicant needs to take leave for; the number of approval levels is the number of supervisors who are required to approve the leave form.
[0037] The following is a flow chart of a distributed organization data construction method used in an organization data construction backend 30 of the present invention. Step S01, generating a plurality of organization unit data 3011a-3011n, wherein each organization unit data includes at least one primary field and one upper field. In the embodiment of the present invention, the primary field or the upper field must include at least one data that can be used to identify the object, such as a work number or a telephone extension number, but the present invention is not limited thereto.
[0038] Step S02, transmitting a plurality of organization unit data 3011a-3011n to a plurality of different working devices 40a-40n, each working device will receive an organization unit data for filling, for example, transmitting the organization unit data 3011a to the working device 40a, transmitting the organization unit data 3011b to the working device 40b, and transmitting the organization unit data 3011n to the working device 40n, etc. Step S03, receiving a plurality of filled organization unit data 3011a-3011n, wherein the plurality of filled organization unit data 3011a-3011n are transmitted by a plurality of working devices 40a-40n. Step S04, matching the current level fields and the parent fields in the multiple filled-in organizational unit data 3011a-3011n to generate an organizational chart (not shown). For example, the current level fields include the name and work number of a filler, and the parent field includes the name and work number of the superior of the filler. In a company organization, each employee's work number or telephone extension number is unique, and therefore can be used as data for identifying objects.
[0039] After receiving a plurality of filled-in organizational unit data 3011a-3011n transmitted by a plurality of working devices 40a-40n, the organizational data construction backend 30 can use any organizational unit data as the starting organizational unit data in the matching process, and use the work number or telephone extension number in the upper column of the starting organizational unit data (because it is unique) to search for the second organizational unit data including the work number or telephone extension number in the current column, that is, to complete the matching of the starting organizational unit data and the second organizational unit data (it should be understood that the person who fills in the second organizational unit data is the upper column of the person who fills in the starting organizational unit data). Then, the work number or telephone extension number in the upper column of the second organizational unit data is used to search for the third organizational unit data including the work number or telephone extension number in the current column, that is, to complete the matching of the second organizational unit data and the third organizational unit data. When all the organizational unit data 3011a-3011n have gone through the matching process and the upper or current organizational unit data are found, an organizational chart can be generated.
[0040] It should be understood that in another embodiment of the present invention, the organization data construction background 30 may not be provided with the data module 301, and the plurality of organization unit data 3011a-3011n may be generated on different plurality of work devices 40a-40n and filled in by respective fillers, and then the work devices 40a-40n transmit the filled in organization unit data 3011a-3011n to the transceiver module 302 of the organization data construction background 30. Therefore, in another embodiment of the present invention in which the data module 301 is not provided, the above-mentioned distributed organization data construction method may omit step S01 and step S02.
[0041] Figure 5 This is a flow chart of a method for constructing distributed organizational data in another preferred embodiment of the present invention. Figure 5 The process also includes steps related to a work device asking for leave. Steps S01-S04 and Figure 4 The same is not repeated here. Step S05, receiving a leave application form 401a transmitted by a leave application work device (assuming that work device 40a wants to apply for leave) among the plurality of work devices 40a-40n. Step S06, transmitting the leave application form 401a to at least one superior work device (assuming that work device 40c is the superior of work device 40a) among the plurality of work devices 40a-40n according to a leave condition, wherein the leave condition at least includes: leave type and number of days. The judgment module 304 in the organization data construction background 30 will determine the number of approval levels required based on the leave type and number of days. For example, if the leave type on the leave application form is special leave and the number of days is 1 day, it is determined that the number of approval levels required is 1, so step S06 will transmit the leave application form 401a to the superior work device of the work device 40a (approve 1 level), that is, the work device 40c. For another example, if the leave type on the leave application is parental leave and the number of days is 60 days, then the number of approval levels required is determined to be 2, so step S06 will transmit the leave application 401a to the superior work device of the work device 40a, that is, the work device 40c. When the work device 40c approves it, the leave application 401a will be further transmitted to the superior work device of the work device 40c (approval of 2 levels), assuming it is the work device 40d.
[0042] Step S07, receiving a sign-off notice sent by the superior working device. As described in the above embodiment, when it is determined that the number of sign-off levels required is 1, the leave application form 401a will be sent to the superior working device of the working device 40a, that is, the working device 40c. After the working device 40c signs the leave application form of the working device 40a, the organization data construction background 30 will receive a sign-off notice sent by the superior working device (that is, the working device 40c).
[0043] Step S08, sending the approval notification to the leave application device. In order to enable the leave application device to know whether the leave application process has been completed, the organization data construction backend 30 will send the approval notification to the leave application device after receiving the approval notification sent by the superior device.
[0044] From the above description, it can be understood that the distributed organizational data construction method and organizational data construction background proposed by the present invention can distribute the work of constructing organizational data to everyone to complete, so as to avoid the traditional situation where only a few staff members within the company are responsible for construction and maintenance, which will make the completion of the organizational chart a very time-consuming and labor-intensive task. The method of the present invention also overcomes the situation that when rapid adjustment or reconfiguration is required, only a few people maintain the organizational chart and may face the situation that they cannot be adjusted quickly. In addition, the organizational unit data in the present invention includes at least one level column and one upper level column, so it is easy to know who the upper supervisor corresponding to the employee in the current level column is (that is, the data in the upper level column), so no matter how many levels of approval are required for the leave application, the upper supervisor can be quickly queried level by level, and the leave application can be approved upward level by level.
[0045] Although various examples of the disclosed technology have been described above, it should be understood that these examples have been presented by way of example and are not limiting. Similarly, various figures may depict example architectures or other configurations of the disclosed technology, which may be depicted to assist in understanding the features and functionality that may be included in the disclosed technology. The disclosed technology is not limited to the example architectures or configurations described, but the desired features may be implemented using a variety of alternative architectures and configurations. In fact, it will be apparent to those skilled in the art how alternative functionalities, logical or physical partitioning and configurations may be implemented to implement the desired features of the technology disclosed herein. In addition, with respect to flow charts, operational descriptions, and method technical solutions, the order in which the steps are presented herein should not require that the disclosed technology be implemented to perform the listed functionality in the same order, unless the context otherwise dictates.
[0046] The above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Therefore, all equivalent changes and modifications based on the shape, structure, characteristics and spirit described in the patent application scope of the present invention should be included in the patent application scope of the present invention.
Claims
1. A method for constructing distributed organizational data, characterized in that: Applied to an organization data construction background, the distributed organization data construction method includes: (A) generating a plurality of organizational unit data, wherein each organizational unit data comprises at least a primary column and a secondary column; (B) transmitting the plurality of organizational unit data to a plurality of different working devices; (C) receiving a plurality of filled-in organizational unit data, wherein the plurality of filled-in organizational unit data is transmitted by the plurality of working devices; (D) Matching the current level fields and the upper level fields in the plurality of filled organizational unit data to generate an organizational chart.
2. A distributed organization data construction method according to claim 1, characterized in that: The current level column includes the name and work number of a filler, and the superior column includes the name and work number of a superior corresponding to the filler.
3. A distributed organization data construction method according to claim 1, characterized in that: The current level column includes the name and telephone extension number of a filler, and the superior column includes the name and telephone extension number of a superior person corresponding to the filler.
4. A distributed organization data construction method according to claim 1, characterized in that: It also includes: (E) receiving a leave request form transmitted by a leave request work device among the plurality of work devices; (F) transmitting the leave request form to at least one superior work device among the plurality of work devices according to a leave request condition, wherein the leave request condition at least includes: leave type and number of days.
5. A distributed organization data construction method according to claim 4, characterized in that: It also includes: (G) receiving a sign-off notification transmitted by the superior working device; (H) Sending the approval notification to the leave request work device.
6. An organizational data construction background, characterized in that: To generate an organizational chart, the organizational data construction background includes: A data module, for generating a plurality of organizational unit data, wherein each organizational unit data includes at least a primary column and a higher column; A transceiver module, used for transmitting the plurality of organizational unit data to different plurality of working devices, and receiving a plurality of filled-in organizational unit data, wherein the plurality of filled-in organizational unit data is transmitted by the plurality of working devices; The matching module is used for matching the current level fields and the upper level fields in the plurality of filled organizational unit data to generate the organizational chart.
7. The organizational data construction background according to claim 6, characterized in that: The current level column includes the name and work number of a filler, and the superior column includes the name and work number of a superior corresponding to the filler.
8. The organizational data construction backend according to claim 6, characterized in that: The current level column includes the name and telephone extension number of a filler, and the superior column includes the name and telephone extension number of a superior person corresponding to the filler.
9. The organizational data construction backend according to claim 6, characterized in that: It also includes: The transceiver module receives a leave request form transmitted by a leave request work device among the plurality of work devices; The judgment module is used to transmit the leave request form to at least one superior work device among the plurality of work devices according to a leave request condition, wherein the leave request condition at least includes: leave type and days.
