Management device, management method, and management program

Abstract

To provide a management device, a management method, and a management program for achieving efficient group management for performing unified management, efficiently collecting information, and approving the collected information among organizations.SOLUTION: In a management device 2700, a control unit includes: a group setting unit that receives registration of groups of many related organizations in a company or an organization, receives designation of a parent group of the group, and generates a hierarchical code of the group according to the designation of the parent group by using a hierarchical code of the parent group; an account setting unit that receives registration of an account, receives designation of a group of the account and an account type, and receives designation of a role (a role of each account) according to the account type; and an approval authority setting unit that receives designation of approval authority according to the account type and the role.SELECTED DRAWING: Figure 27

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a management program. [Background technology]

[0002] Patent Document 1 discloses a database management device. [Prior art document] [Patent Documents]

[0003] [Patent Document 1] JP 2019-219847 Summary of the Invention [Means for solving the problem]

[0004] A management device according to one aspect of the present invention includes a group setting unit that accepts registration of a group, accepts designation of a parent group of the group, and generates a hierarchical code of the group in accordance with the designation of the parent group using the hierarchical code of the parent group. The management device also includes an account setting unit that accepts registration of an account, accepts designation of a group and account type of the account, and accepts designation of a role in accordance with the account type. The management device also includes an approval authority setting unit that accepts designation of approval authority in accordance with the account type and the role.

[0005] In the management device, the approval authority setting unit accepts a designation of approval authority for a child group designated with the group as a parent group.

[0006] The management device further includes a base setting unit that accepts registration of bases and accepts designation of master information including the group for each base, and the approval authority setting unit accepts designation of approval authority for bases linked to child groups designated with the group as a parent group.

[0007] The management device further includes an approval management unit that accepts a designation of a group of a plurality of bases, wherein the approval authority setting unit accepts a designation of approval authority for the plurality of grouped bases.

[0008] A management method according to one aspect of the present invention includes the steps of: accepting registration of a group; accepting designation of a parent group of the group; and generating a hierarchical code for the group using the hierarchical code of the parent group in accordance with the designation of the parent group; accepting registration of an account; accepting designation of a group and account type of the account; and accepting designation of a role in accordance with the account type; and accepting designation of approval authority in accordance with the account type and the role.

[0009] A management program according to one aspect of the present invention causes a computer to execute the above management method.

[0010] The above summary of the invention does not list all of the features of the present invention, and subcombinations of these features may also be inventions. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a management system according to a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of functional blocks of a management device according to the first embodiment. [Figure 3] FIG. 4 is a diagram illustrating an example of an operation flow of the management device according to the first embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a hierarchical relationship between groups according to the first embodiment. [Figure 5] FIG. 3 is a diagram showing an example of a group table according to the first embodiment. [Figure 6] FIG. 2 is a diagram showing an example of a hierarchical relationship between groups according to the first embodiment. [Figure 7] FIG. 3 is a diagram showing an example of a group table according to the first embodiment. [Figure 8] FIG. 4 is a diagram illustrating an example of an operation flow of the management device according to the first embodiment. [Figure 9] FIG. 3 is a diagram illustrating an example of an account table according to the first embodiment. [Figure 10] FIG. 4 is a diagram illustrating an example of an operation flow of the management device according to the first embodiment. [Figure 11] FIG. 4 is a diagram showing an example of an authorization role setting screen according to the first embodiment. [Figure 12] FIG. 4 is a diagram illustrating an example of an operation flow of the management device according to the first embodiment. [Figure 13] FIG. 4 is a diagram illustrating an example of an operation flow of the management device according to the first embodiment. [Figure 14] FIG. 10 is a diagram showing an example of an information confirmation screen according to the first embodiment. [Figure 15] FIG. 10 is a diagram illustrating an example of the overall configuration of a management system according to a second embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of functional blocks of a management device according to a second embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 18] FIG. 11 is a diagram illustrating an example of a base table according to the second embodiment. [Figure 19] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 20] FIG. 11 is a diagram illustrating an example of a setting screen for an input person according to the second embodiment. [Figure 21] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 22] FIG. 11 is a diagram showing an example of a setting screen for inputting information according to the second embodiment. [Figure 23] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 24] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 25] FIG. 10 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 26] FIG. 11 is a diagram showing an example of an information confirmation screen according to the second embodiment. [Figure 27] FIG. 11 is a diagram illustrating an example of functional blocks of a management apparatus according to a third embodiment. [Figure 28] FIG. 11 is a diagram illustrating an example of an operation flow of a management device according to the third embodiment. [Figure 29] FIG. 11 is a diagram illustrating an example of an account table according to the third embodiment. [Figure 30] FIG. 11 is a diagram illustrating an example of an operation flow of a management device according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] The present invention will be described below through embodiments of the invention, but the following embodiments do not limit the scope of the invention according to the claims. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0013] In recent years, there has been a need for companies and organizations to unify management and efficiently collect information across a group of many related organizations, and to approve the collected information among the organizations.

[0014] The management device 100 according to the first embodiment realizes efficient group management.

[0015] FIG. 1 shows an example of the overall configuration of a management system 10 according to the first embodiment. The management system 10 includes a management device 100 and a plurality of terminals 200. The management device 100 communicates with the terminals 200 via a network 50. The management device 100 may receive operations directly or through the terminals 200. In the first embodiment, an example will be described in which the management system 10 includes one management device 100. However, the management system 10 may include a management device 100 for each different company, for example. Data may be exchanged between the plurality of management devices 100.

[0016] FIG. 2 shows an example of functional blocks of the management device 100. The management device 100 may be configured as hardware by a computer. The computer may execute the management method described herein using a management program. The management device 100 includes a control unit 110, a communication unit 120, and a storage unit 130. The control unit 110 may be configured by a microprocessor such as a CPU or MPU, or a microcontroller such as an MCU. The communication unit 120 manages communication between components within the management device 100. In addition, the communication unit 120 communicates with external computers such as terminals 200 via a network 50 such as the Internet. The storage unit 130 stores information processed by the control unit 110 and information received from each terminal 200. The storage unit 130 may be configured by a memory device, a RAM, a ROM, a HDD, a SSD, or other storage media. The storage unit 130 may store various types of information as data in tables and store a database configured by associating each table.

[0017] The control unit 110 includes a group setting unit 112, an account setting unit 114, an authority role unit 116, and a display control unit 118. The group setting unit 112 accepts the registration of a group and stores information about the group in the storage unit 130. The account setting unit 114 accepts the registration of an account and stores information about the account in the storage unit 130. The authority role setting unit 116 accepts the registration of authority items for a role and stores information about the role and authority in the storage unit 130. The display control unit 118 displays each piece of information on an output device such as a display connected to the management device 100 or an output device of an external computer such as a terminal 200 with which the management device 100 communicates.

[0018] 3 is a diagram showing an example of an operation flow of the management device 100 according to the first embodiment. The group setting unit 112 accepts registration of a group (S100), accepts designation of a parent group of the group (S102), and generates a hierarchical code for the group in accordance with the designation of the parent group using the hierarchical code of the parent group (S104).

[0019] The group setting unit 112 accepts the registration of a group (S100). The registration of a group is performed, for example, by an operation to create a group using the terminal 200. Specifically, for example, the group setting unit 112 accepts the registration of a group by creating a group name and assigning a group code accordingly, using an operation using the terminal 200. The group may be a company or a group within a company (headquarters, department, etc.), or may be any organization, such as a variety of associations, national or local public bodies, or any other organization.

[0020] Here, the relationship between groups and hierarchies will be described using a specific example with reference to FIG. 4. FIG. 4 is a diagram showing an example of the hierarchical relationship between groups according to the first embodiment. FIG. 4 shows hierarchical numbers 401 indicating hierarchies (hierarchy 1, hierarchical 2, hierarchical 3, and hierarchical 4 are shown, but this is not limited to these and more hierarchies may be included, such as hierarchy 5, hierarchical 6, hierarchical 7, hierarchical 8, etc.) and group names 402 indicating groups in each hierarchical level (hierarchical levels A, B, C, . . ., and J are shown, but this is not limited to these and more hierarchical levels may be included, such as hierarchy K, hierarchical L, etc.). For example, the hierarchies may represent relationships between companies, such as a holding company, head office, subsidiaries, sub-subsidiaries, affiliated companies, and overseas offices, or may include groups within a company, or may represent connections between any other organizations.

[0021] The group with group name 402 shown under hierarchical number 401 is included in that hierarchical level. In FIG. 4, group A is included in hierarchical level 1, groups B and C are included in hierarchical level 2, groups D to H are included in hierarchical level 3, and groups I and J are included in hierarchical level 4. The lines in the figure indicate the hierarchical connections between groups. For example, groups B and C are both connected to group A by a line, so groups B and C (hierarchical level 2) are both linked to group A (hierarchical level 1). In this case, group A is defined as the "parent group" of groups B and C. Similarly, groups D and E are connected to group B by a line, and groups F to H are connected to group C by a line, so groups D and E (hierarchical level 3) are linked to group B (hierarchical level 2), and groups F to H (hierarchical level 3) are linked to group C (hierarchical level 2). Therefore, group B is the parent group of groups D and E, and group C is the parent group of groups F to H.

[0022] Fig. 5 is a diagram showing an example of a group table 501 according to the first embodiment. Fig. 5 shows the relationship between the groups and hierarchies shown in Fig. 4 in a table, and indicates that information relating to the groups and hierarchies is stored in the storage unit 130 in table format. Furthermore, the display control unit 118 may display part or all of the group table 501 shown in Fig. 5 on a display device. Below, figures relating to tables are similar, and their explanation will be omitted.

[0023] The group table 501 includes a group code, group name, parent group name, and hierarchical code, but is not limited to these. It may also include other information, such as creation date, deletion date, location, and detailed attributes. The group code is a code assigned to each group and constitutes a unique ID. In FIG. 5, the numbers 1, 2, 3, ..., 10 are used, but this is not limited to these and any unique code may be assigned. The group name represents the name of each group. In FIG. 5, the same groups A, B, C, ..., J are shown as in FIG. 4. As described with reference to FIG. 4, a parent group represents a group in a higher hierarchical level linked to the group. For example, in FIG. 5, group A does not have a parent group, and therefore group A is in hierarchical level 1. Furthermore, group B's parent group is A, and group C's parent group is also A. Therefore, both group B and group C are in hierarchical level 2 linked to group A (hierarchical level 1).

[0024] A hierarchical code is a code assigned to each group, which constitutes a unique ID and also represents a hierarchy. The group setting unit 112 generates a hierarchical code for a group by placing the group code of the group after the hierarchical code of its parent group. However, for groups that do not have a parent group (i.e., groups in hierarchy 1), the hierarchical code is generated using the group code of the group. For example, in FIG. 5, the hierarchical code for group A (without a parent group) in hierarchy 1 is " / 1 / ," using group A's group code "1." The hierarchical code for group B (whose parent group is group A) in hierarchy 2 is " / 1 / 2 / ," which is the parent group's hierarchical code " / 1 / " followed by group B's group code "2." Similarly, the hierarchical code for group C (whose parent group is group A) in hierarchy 2 is " / 1 / 3 / ," which is the parent group's hierarchical code " / 1 / " followed by group C's group code "3." Furthermore, the hierarchical code for group D (parent group is group B) in hierarchical level 3 is " / 1 / 2 / 4 / ," which is the hierarchical code of the parent group " / 1 / 2 / " followed by the group code of group D, "4." In this way, by generating the hierarchical code of a group in a certain hierarchical level by placing the group code of that group after the hierarchical code of its parent group, it is possible to generate an infinite number of hierarchies while maintaining the links between groups, excluding physical constraints, and it is possible to uniformly represent the hierarchies of many groups.

[0025] Fig. 6 is a diagram showing an example of the hierarchical relationship of groups according to the first embodiment, and shows the hierarchical relationship after the hierarchical relationship of the groups shown in Fig. 4 has been changed. As in Fig. 4, Fig. 6 shows hierarchical numbers 601 indicating the hierarchical levels (hierarchical levels 1, 2, 3, 4, and 5 are shown, but this is not limited to these and more hierarchical levels may be included, such as hierarchical levels 6, 7, 8, 9, etc.), and group names 602 indicating the groups in each hierarchical level (hierarchical levels A, B, C, etc. and hierarchical levels J are shown, but this is not limited to these and more hierarchical levels may be included, such as hierarchical levels K, L, etc.). Below, explanations similar to those in Fig. 4 will be omitted.

[0026] In Figure 6, the group in Layer 1 has changed from Group A in Figure 4 to Group G. Meanwhile, Group A is in Layer 3, and its parent group is Group C in Layer 2. The layers and parent groups of the other groups have also changed.

[0027] Fig. 7 is a diagram showing an example of a group table 701 according to the first embodiment, showing the hierarchical relationship after the hierarchical relationship of the group table 501 shown in Fig. 5 has been changed. Fig. 7 also shows the relationship between the groups and hierarchies shown in Fig. 6 in a table. For reference, Fig. 7 shows the hierarchical code included in the group table 501 of Fig. 5 as the "hierarchical code before change." Below, explanations similar to those in Fig. 5 will be omitted.

[0028] Here, an example of the operation of the group setting unit 112 that changes the relationship between groups and hierarchies shown in Figures 4 and 5 to the relationship shown in Figures 6 and 7 will be described. First, group G, which was at hierarchical level 3 in Figures 4 and 5, becomes hierarchical level 1 when group C, which was its parent group, is released (for example, by designating it as no parent group). At this time, the group setting unit 112 deletes " / 1 / 3" that was placed before the group code "7" of group G from the hierarchical code " / 1 / 3 / 7 / " of group G due to the release of the parent group designation, and updates the hierarchical code of group G to " / 7 / ". Note that, although not shown in Figures 4 and 5, if there are groups at lower hierarchical levels linked to group G, the hierarchical level of group G may be raised by two levels from hierarchical level 3 to hierarchical level 1, and at the same time, the hierarchical levels of these lower hierarchical levels may also be raised by two levels.

[0029] 4 and 5, group A, which was in hierarchical level 1, is linked to group C by designating group C as its parent group, and becomes one hierarchical level lower than group C. In FIGS. 6 and 7, group C's hierarchical level is hierarchical level 2, so group A's hierarchical level becomes hierarchical level 3. In this case, by accepting the designation of group C as group A's parent group, group setting unit 112 places group A's hierarchical level code " / 1 / " (in FIG. 5) after group C's hierarchical level code " / 7 / 3 / " (in FIG. 7), and updates group A's hierarchical level code to " / 7 / 3 / 1 / " as shown in FIG. 7. Note that, for simplicity, the above explanation has been given assuming that there are no groups in lower hierarchical levels linked to group A in FIGS. 4 and 5; however, when group A's hierarchical level is lowered by two levels from hierarchical level 1 to hierarchical level 3, the hierarchical levels of these lower hierarchical levels may also be lowered by two levels at the same time.

[0030] Similarly, the group setting unit 112 accepts the designation of a parent group of a group (S102 in FIG. 3) and generates a hierarchical code for the group using the hierarchical code of the parent group in response to the designation of the parent group (S104 in FIG. 3). This allows the group-hierarchical relationships shown in FIGS. 4 and 5 to be easily changed to those shown in FIGS. 6 and 7. This allows for uniform and easy change and management of hierarchical relationships, even when the relationships between many groups are complex, simply by designating the parent group of each group. Furthermore, although not shown in FIGS. 4 to 7, a hierarchical change flag and change date / time may be included in the group table or a separately set hierarchical table for hierarchical changes. The group setting unit 112 may then designate a change flag for a hierarchical level that has been changed, such as by adding, replacing, or deleting, and record the change date / time in the table. This allows for a history of past hierarchical changes to be kept.

[0031] Although FIGS. 4 to 7 show an example in which there is one group in layer 1, the present invention is not limited to this, and layer 1 may have multiple groups.

[0032] Fig. 8 is a diagram showing an example of the operation flow of the management device 100 according to the first embodiment. The account setting unit 114 accepts the registration of an account (S200), accepts the designation of the account group and account type (S202), and accepts the designation of a role according to the account type (S204). Each operation will be described below with reference to Fig. 9. Fig. 9 is a diagram showing an example of an account table 901 according to the first embodiment.

[0033] The account setting unit 114 accepts the registration of an account (S200). Here, the account table 901 in Fig. 9 has an account code, account type, group name, and role. The account setting unit 114 adds a new row to the account table 901 and executes the account registration process by accepting or generating the input of each of the above information for that row. Note that the information held in the account table is not limited to the above, and may also include other information such as the account creation date, deletion date, name, email address, detailed affiliation, etc.

[0034] Here, in the account table 901 of Fig. 9, the account code is a code assigned to each account and constitutes a unique ID. In Fig. 9, the numbers 0001, 0002, 0003...0012 are assigned, but this is not limited to this and any unique code may be assigned. An arbitrary code may be input as the account code by operation of the terminal 200, or the account setting unit 114 may automatically assign a unique code when registering an account. The number may be assigned by determining and using an unused value from the smallest value within a predetermined number of digits, or may be generated randomly using a function or the like, and any duplicate values ​​may be removed.

[0035] The account setting unit 114 accepts the designation of the group and account type of the account (S202). For example, Fig. 9 shows an example in which the account setting unit 114 accepts the designation of group C and individual authority for account 0003. The designation of the group and account type may be performed by an operation using the terminal 200, or a specific account type may be automatically designated for a specific group, or a specific group for a specific account type. For example, if the account type is designated as overall management authority or overall authority, the account setting unit 114 may automatically designate the hierarchical level of the group of the account as hierarchical level 1.

[0036] Here, in the account table 901 in Figure 9, the account type indicates the type of account and distinguishes the role and authority of each account. In Figure 9, there are four account types: overall management authority, overall authority, individual authority, and data entry person. The difference between overall management authority and overall authority may be, for example, that the former can add accounts and authority roles, while the latter cannot. Individual authority and data entry person will be described in detail using Figures 10 and 11, etc. The account types are not limited to these and may include any other account type, and the names are also not limited to these and may be other names such as main body administrator, main body employee, subsidiary employee, field person, etc.

[0037] Furthermore, in account table 901 of Fig. 9, group name represents the name of the group associated with each account, and may represent, for example, the name of the group to which each account belongs. Group information may be stored in a group table such as group table 501 of Fig. 5 or group table 701 of Fig. 7, and account table 901 may reference the group table using the group code of the group table as a foreign key (not shown in Fig. 9). For example, in Fig. 9, the account with account code 0003 is associated with group C, and information about group C may be stored in group table 501 of Fig. 5 or group table 701 of Fig. 7, and account table 901 may reference group table 501 of Fig. 5 or group table 701 of Fig. 7 using the group code of group C (not shown in Fig. 9) as a foreign key.

[0038] 9, the group names for account codes 0001 and 0002 are blank, but accounts that do not require group management do not need to be associated with a group. For example, account codes 0001 and 0002 are actually accounts that belong to group A in hierarchical level 1 in FIGS. 4 and 5, but are not associated with group A because they do not require management according to the group to which they belong, such as because their account type is overall management authority, which allows operations related to all management devices 100, or their account type is overall authority, which allows operations related to all groups. In other embodiments, it may be necessary to associate the account table with the group table. In that case, for example, in FIG. 9, the account codes 0001 and 0002 have the account type of overall management authority or overall authority, and therefore the group name A to which they belong may be omitted.

[0039] The account setting unit 114 accepts the designation of a role according to the account type (S204). Here, in the account table 901 of FIG. 9, the role indicates the role of each account, and each account is subject to control according to the role. In the first embodiment, the role can be set according to the account type. Specifically, FIG. 9 shows a case where a role can be set when the account type is individual authority. This indicates that, when the account type is individual authority, authority is set individually for each account of that account type, but the individual authority setting is performed according to the role. Conversely, in the example shown in FIG. 9, when the account type is overall management authority or overall authority, each account of that account type has overall authority, and therefore individual authority setting is not required. Also, in the example shown in FIG. 9, when the account type is input person, each account of that account type is only responsible for input, and therefore is not subject to individual authority setting.

[0040] In the account table 901, the roles include "including subsidiaries," "my company only," "role 1," and "role 2." "including subsidiaries" represents a role that also has authority over groups at a lower level than the group to which the account belongs. "my company only" represents a role that has authority over only the group to which the account belongs. "Role 1" and "role 2" represent roles that are set arbitrarily, and are described in detail in FIGS. 10 and 11. Note that in FIG. 9, "including subsidiaries" and "my company only" are pre-set roles, but the names and role contents may be editable. Furthermore, the roles in the account table are not limited to the above, and other arbitrary roles may be included. While FIG. 9 shows an example in which one role is specified for each account, multiple roles may be set for each account. However, as in FIG. 9, where "including subsidiaries" and "my company only" are alternatives, constraints such as alternatives and dependency conditions (e.g., role Y cannot be specified unless role X is specified) may be set for the multiple roles that are specified.

[0041] FIG. 10 is a diagram showing an example of the operation flow of the management device 100 according to the first embodiment. The authorized role setting unit 116 accepts registration of authority items for roles (S300), and accepts designation of authority for each item for the role for each group (S302). Each operation will be explained below with reference to FIG. 11. FIG. 11 is a diagram showing an example of an authorized role setting screen according to the first embodiment. The setting screen has a field 1101 indicating the group name, a field 1102 indicating the authority items for the role, and a field 1103 indicating the designation of authority for each item for the role for each group.

[0042] The authorized role setting unit 116 accepts registration of authority items for roles (S300). Here, in Fig. 11, Role 1, Role 2, and Role 3 are shown in field 1102. For convenience, in Fig. 11, names such as Role 1 and Role 2 are used, but for example, the name of a specific information item (e.g., greenhouse gas emissions, activity volume of activities involving greenhouse gas emissions, water usage amount) may be used as an item indicating authority for that information item. The authorized role setting unit 116 may accept a request to register authority items for roles and setting of the names of those items through operation of terminal 200.

[0043] The authorized role setting unit 116 accepts the designation of the authority for each role of each item for each group (S302). Here, in FIG. 11, groups A, B, C,..., F are shown in field 1101, and for each group, one of "editable," "viewable," or "no authority" is shown in field 1103 for each of the items ROLE 1, ROLE 2, and ROLE 3 shown in field 1102. For example, the authorized role setting unit 116 accepts a designation of "no authority" for role 1 for group F through an operation of terminal 200, and sets the authority as shown in FIG. 11. Then, if role 1 is designated for account 0009 belonging to group F as shown in FIG. 9, account 0009 does not have authority for the item designated by role 1 when operating terminal 200 using account 0009, and therefore cannot edit the item, nor can the item be displayed. This will be described in detail below with reference to FIG. 12.

[0044] 12 is a diagram showing an example of an operation flow of the management device 100 according to the first embodiment. The display control unit 118 receives a display request from the terminal 200 (S400), determines the role associated with the account operating the terminal 200 (S402), and displays information about the group according to the authority of the role (S404).

[0045] The display control unit 118 receives a display request from the terminal 200 (S400). The display request from the terminal 200 may be received simultaneously with authentication of the account operating the terminal 200, or may be received at any timing after the authentication is complete. The display control unit 118 determines the role associated with the account operating the terminal 200 (S402). For example, if the account operating the terminal 200 is an account indicated by account code 0004 in the account table 901 of FIG. 9, the display control unit 118 determines that the role is "our company only." The display control unit 118 displays information about the group in accordance with the authority of the role (S404). For example, in the case of the role of "our company only," the account has the authority to handle only its own company's information, and therefore the display control unit 118 displays only information about group C associated with the account on the display unit of the terminal 200 operated by account code 0004.

[0046] Similarly, for example, if the account operating the terminal 200 is the account indicated as account code 0011 in the account table 901 of Fig. 9, the display control unit 118 determines that the role is "role 2." Then, since role 2 has the authority to "edit" for the items of role 2 as shown in Fig. 11, the display control unit 118 causes the items of role 2 to be displayed editably on the display unit of the terminal 200 operated by the account code 0011. In this way, the display control unit 118 determines the role associated with the account operating the terminal 200 that has accepted the display request, and displays information about the group according to the authority of the role, thereby enabling flexible control over each account.

[0047] FIG. 13 is a diagram showing an example of an operation flow of the management device 100 according to the first embodiment. The display control unit 118 receives a display request from the terminal 200 (S500), determines a hierarchical level from the group associated with the account operating the terminal 200, and displays information about groups at or below that hierarchical level on the display device of the terminal 200 (S502). Each operation will be described below with reference to FIG. 14. FIG. 14 is a diagram showing an example of an information confirmation screen according to the first embodiment. The information confirmation screen has a field 1401 for accepting designation of a group for which information is to be input, a field 1402 for accepting designation of whether or not to include a lower hierarchical level (subordinate) of the group, a field 1403 for accepting designation of narrowing down when a lower hierarchical level of the group is to be included, and a field 1404 for displaying the designated information.

[0048] The display control unit 118 receives a display request from the terminal 200 (S500). The display request from the terminal 200 may be received simultaneously with authentication of the account operating the terminal 200, or may be received at any timing after the authentication is completed. In particular, the display request from the terminal 200 may be received at the timing when information is input in response to an information input request after an account operating one terminal 200 has executed an information input request to an account operating another terminal 200.

[0049] The display control unit 118 determines the hierarchical level from the group linked to the account operating the terminal 200, and displays information about groups at or below that hierarchical level on the display device of the terminal 200 (S502). The hierarchical level may be determined by identifying the hierarchical level from the group linked to the account operating the terminal 200, using the group table 501 or group table 701 in Fig. 5 or 7 and the account table 901 in Fig. 9. For example, if the account operating the terminal 200 has account code 0003 in the account table 901 in Fig. 9, the group linked to the account is C, and by referring to the group table 501 in Fig. 5, the hierarchical level code of group C is " / 1 / 3 / ", and therefore it is identified as hierarchical level 2, as also shown in Fig. 4.

[0050] Then, the display control unit 118 displays information about groups at or below that hierarchical level on the display device of the terminal 200. For example, when hierarchical level 2 is determined from group C linked to account code 0003, the display control unit 118 displays information about groups at or below that hierarchical level 2 on the display device of the terminal 200, as shown in Figs. 4 and 5. For example, in Fig. 14, group C linked to account code 0003 is shown in field 1401. Here, the display control unit 118 may accept designation from one or more of groups F to J in a lower hierarchical level in addition to group C in field 1401. In this case, group A, which is a higher hierarchical level than group C, and groups B to E, which are not linked to group C, are not displayed in field 1401 as designation candidates.

[0051] Furthermore, the display control unit 118 may accept a specification to narrow down the targets for information confirmation among the groups at or below the relevant hierarchical level, and display information on the narrowed down targets. For example, in FIG. 14, the display control unit 118 accepts a specification in field 1402 as to whether to narrow down the targets for information confirmation to include groups F to J ("underlying" in FIG. 14) that are at a lower hierarchical level than group C. When "including underlying" is specified in field 1402 (a check mark is displayed in FIG. 14), the display control unit 118 may display information on targets narrowed down to group C and one or more of groups F to J under it in "Narrowing down" in field 1403 in field 1404. When the narrowed down target information is information on multiple groups, the information on each group may be displayed side by side, added together, or the like. This allows information on groups at or below the hierarchical level to be displayed more flexibly and clearly.

[0052] Next, a management device 1500 according to a second embodiment will be described. In addition to efficient group management, the management device 1500 according to the second embodiment realizes information management that allows information collectors to collect more information more accurately and allows information providers to provide information more easily. In the following, explanations of the second embodiment that are the same as those of the first embodiment will be omitted.

[0053] 15 is a diagram showing an example of the overall configuration of a management system 15 according to the second embodiment. The management system 15 includes a management device 1500 and a plurality of terminals 200.

[0054] 16 shows an example of functional blocks of the management device 1500. The management device 1500 includes a control unit 1510, a communication unit 120, and a storage unit 130. The control unit 1510 includes a group setting unit 112, an account setting unit 114, an authority role unit 116, a base setting unit 1512, an input management unit 1514, an input reception unit 1516, and a display control unit 118.

[0055] FIG. 17 is a diagram showing an example of the operational flow of the management device 1500 according to the second embodiment. As explained in the first embodiment, the group setting unit 112 accepts the registration of a group, and the account setting unit 114 accepts the registration of an account and accepts the designation of the group and account type of the account. The base setting unit 1512 then accepts the registration of a base (S600) and accepts the designation of master information including the group for each base (S602). Each operation will be explained below with reference to FIG. 18. FIG. 18 is a diagram showing an example of a base table 1801 according to the second embodiment. The base table 1801 is stored in the storage unit 130, with the group name and the base name linked together.

[0056] The base setting unit 1512 accepts the registration of a base (S600). The base is registered, for example, by a base creation operation using the terminal 200. Specifically, the base setting unit 1512 accepts the registration of a base by creating a base name and assigning a base code to the base through an operation using the terminal 200. A base may be a company or an internal group (headquarters, department, etc.) of a company, various organizations, national or local public entities, or any other organization, but is different from a group. For example, if the group is a company, the base may be another company, a company facility, factory, branch office, overseas subsidiary, or other organization different from the group. Furthermore, as shown in FIG. 18, multiple bases may be associated with one group. For example, in FIG. 18, two bases, a1 and a2, are associated with group A.

[0057] The base setting unit 1512 accepts the designation of master information including groups for each base (S602). Although not shown in Fig. 18, the base table 1801 may include, in addition to the group name, a base code that identifies the base, a group code, an account code, an input person, basic information, questionnaire information, electricity plan, power source information, gas plan, facility equipment information, business, equipment, facility classification, management item, activity amount code, and other related master information. The base setting unit 1512 accepts the designation of each piece of master information for each base.

[0058] FIG. 19 is a diagram showing an example of the operational flow of the management device 1500 according to the second embodiment. The account setting unit 114 displays candidate accounts from a group according to the account type (S700), and associates a selected account from the candidate accounts with the specified location as the person in charge of input (S702). Each operation will be described below with reference to FIG. 20. FIG. 20 is a diagram showing an example of an input person setting screen according to the second embodiment. The input person setting screen has a field 2001 indicating a list of locations to which the account will be added, a field 2002 indicating the input person to be associated with the list of locations to which the account will be added, a candidate list field 2003 indicating the candidate accounts to be associated, a specification field 2004 included in the candidate list field 2003 for narrowing down the candidate accounts, and a field 2005 included in the candidate list field 2003 indicating the candidate accounts narrowed down by the specification field 2004.

[0059] The account setting unit 114 displays candidate accounts from the group according to the account type (S700). For example, in the candidate list field 2003 of FIG. 20, group C is specified in the designation field 2004. Here, it is assumed that the accounts belonging to group C are shown in the account table 901 of FIG. 9. Then, there are five accounts belonging to group C, with account codes 0003 to 0007. The account setting unit 114 determines account codes 0005 to 0007 from group C, whose account type is specified as "input person," as candidate accounts. Then, in field 2005, only account code 0007, which has not yet been specified as an input person in field 2002, is displayed as "C 0007." Note that, although omitted in FIG. 20, the designation field 2004 may display candidate accounts using other designation methods. For example, the designation field 2004 may accept designation using an account code, name, email address, or other account-identifying items for identifying the candidate account.

[0060] The account setting unit 114 associates a selected account from the candidate accounts with the specified location as the person in charge of input (S702). For example, FIG. 20 shows that accounts 0005 and 0006, selected from candidate accounts 0005 to 0007, are associated as the person in charge of input with location c2, which is specified as the location to which the data is added. The account setting unit 114 may display a list of candidate locations to which the data is added, limited based on at least one of the account hierarchy and account type of the account operating the terminal 200. Selection of a person in charge of input from the candidate accounts may be performed by dragging and dropping the candidate account shown in field 2005 into field 2002. According to the second embodiment, candidate accounts are displayed from the group based on account type, and a selected account from the candidate accounts is associated with the specified location as the person in charge of input. This makes it easy to associate and set a person in charge of input with each location.

[0061] FIG. 21 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. The input management unit 1514 displays common input information items for each location (S800) and accepts designation of input information items for each location (S802). Each operation will be described below with reference to FIG. 21. FIG. 22 is a diagram showing an example of an information input setting screen according to the second embodiment. The setting screen has a field 2201 indicating the name of the group to be set, a field 2202 indicating the name of the location to be set, a field 2203 indicating the fiscal year to be set, a field 2204 indicating the type of display period to be set (yearly or monthly), a field 2205 indicating various information classifications, and a field 2206 indicating a screen for setting each information input according to the contents designated in fields 2201 to 2205. For example, in FIG. 22, the setting target is site c2 in Group C, the fiscal year is 2023, the display period is fiscal year, and the information classification is GHG (Greenhouse Gas) Scope 1 (direct emissions under the GHG Protocol). According to the settings, field 2206 is configured with input information items for "kerosene" and "diesel" under the "Fuel Use" major category, prompting users to enter the 2023 value for each usage amount in kl, the reason for the difference, comments, and attachments. Furthermore, as indicated by "(Add)" at the bottom of the "Fuel Use" major category, the input management unit 1514 can accept additional input information items. Although not shown in FIG. 22, a field indicating whether field 2206 is set to "in progress" or "completed" for each of the various information classifications shown in field 2205 may be provided. This allows even those other than the person responsible for input to easily check whether field 2206 for a given information classification is still being entered or has already been entered.

[0062] The input management unit 1514 displays common input information items for each base station (S800). For example, in FIG. 22, the input information items set for base station c2 are shown in field 2206, and these input information items are displayed based on input information items common to other base stations. The common input information items are stored as templates in the storage unit 130 and are displayed for each base station by the input management unit 1514. The input management unit 1514 then accepts the designation of input information items for each base station (S802). For example, in FIG. 22, the type of the input information item "diesel" is "amount used" and the unit is "kl," but the input management unit 1514 may accept an instruction to change the type to "emissions" and the unit to "tCO2e" by operating the terminal 200, and the input acceptance unit 1516 may accept information input for base station c2 using the changed type and unit. By displaying common input information items at each location in this way, information can be collected from the locations in a unified manner, while certain items can be customized by accepting designation of input information items for each location, allowing information available at each location to be collected. Note that acceptance of designation of input information items for each location by the input management unit 1514 may be permitted only for specific accounts according to at least one of account type, role, and hierarchy. This limits control over input information items to accounts with specific authority, thereby maintaining uniformity in information collection.

[0063] FIG. 23 is a diagram illustrating an example of the operational flow of the management device 1500 according to the second embodiment. The input accepting unit 1516 accepts a display request from the terminal 200 operated by the person in charge of inputting data at the base (S900), displays the input information items specified for the base (S902), accepts input for each input information item from the terminal 200, executes processing according to each specification, and saves the results of the processing (S902). Although the information input screen shown in each operation is not illustrated, each operation will be described with reference to the portions of the setting screen in FIG. 22 that are common to the information input screen. Note that the portions of the information input screen that are common to the setting screen in FIG. 22 may vary depending on the account type. For example, if the account type is overall management authority or overall authority, the setting screen in FIG. 22 and the information input screen may be common, and the input management unit 1514 may accept the specification of the input information items while the input accepting unit 1516 may accept input for each input information item. Furthermore, when the account type is individual authority, the input management unit 1514 may accept designation of input information items in the same manner within the range of groups and bases according to the role, while the input acceptance unit 1516 may accept input for each input information item. Furthermore, when the account type is input person, the input acceptance unit 1516 may accept input only for the set input information items only for the linked base, and without the input management unit 1514 accepting designation of input information items. In this case, the designation item "(Add)", for example, of the setting screen in FIG. 22 is not displayed on the information input screen.

[0064] The input receiving unit 1516 receives a display request from the terminal 200 operated by the person in charge of inputting data at the base (S900). The display request from the terminal 200 may be received simultaneously with authentication of the account operating the terminal 200, or may be received at any timing after the authentication is completed. In particular, the display request from the terminal 200 may be received at the timing when the person in charge of inputting data inputs information in response to an information input request after an information input request to the person in charge of inputting data is executed from the account that performed the operation to link the person in charge of inputting data to the base.

[0065] The input receiving unit 1516 displays the input information items specified for the location (S902). The operation of specifying the input information items for the location has been described with reference to Figs. 21 and 22. Then, the input receiving unit 1516 displays the specified input information items. As described above, the information input screen displayed here may also have parts that are common to the setting screen in Fig. 22 that change depending on, for example, the account type.

[0066] The input accepting unit 1516 accepts input for each item of input information from the terminal 200, executes processing according to each specification, and saves the results of the processing (S902). For example, for the input information item "CO2 (non-energy origin)" of the major item "6.5 gases" in GHG Scope 1 set on the setting screen of FIG. 22, the input accepting unit 1516 may accept input of the value "xyy" for fiscal year 2023 for that item (originally input as a number, but described as a character string for convenience of explanation) from the terminal 200 operated by an account linked to base c2 as the person in charge of input. Then, the input accepting unit 1516 executes processing according to each specification. For example, for "CO2 (non-energy-derived)," if the input management unit 1514 has received a specification that requires input of a reason for the difference if a value for fiscal year 2023 that exceeds a predetermined threshold or range from the fiscal year 2022 value "xyx" exceeds the predetermined threshold or value from the fiscal year 2022 value "xyx," the input acceptance unit 1516 may execute a display process indicating that input of the reason for the difference is required in accordance with the specification. The input acceptance unit 1516 also stores the result of the process. For example, in accordance with the display process indicating that input of the reason for the difference is required, the input acceptance unit 1516 may display an error message in the "reason for difference" field if it has not accepted input of the reason for the difference and store the result in the storage unit 130. Alternatively, if input into the "reason for difference" field is accepted, the input acceptance unit 1516 may store the value for fiscal year 2023 "xyy" and the reason for the difference in the storage unit 130. This allows for more detailed and accurate collection of information to be collected from the person in charge of input.

[0067] Fig. 24 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. The display control unit 118 receives a display request from the terminal 200 (S1000), determines the role associated with the account operating the terminal (S1002), receives designation of a location according to the authority of the role, and displays input item information related to the location (S1004). Below, explanations that overlap with those described as an example of the operation flow of the management device 100 according to the first embodiment using Fig. 12 will be omitted.

[0068] The display control unit 118 accepts the designation of a base in accordance with the authority of the role, and displays input item information related to the base (S1004). For example, if the display control unit 118 accepts a display request from the terminal 200 operated by an account with account code 0003 in the account table 901 of Fig. 9 and determines that the role associated with the account is "including subsidiaries" from the account table 901, the account has authority to handle information of its own group as well as groups hierarchically lower. Therefore, the display control unit 118 accepts designation of bases to be displayed from bases associated with group C and groups F to J hierarchically lower than group C, as shown in Figs. 4 and 5, in accordance with the authority of the role. Then, the display control unit 118 displays input information items related to the base whose designation was accepted on a display device or the like of the terminal 200 operated by the account. In this way, the display control unit 118 determines the role associated with the account operating the terminal 200 that has accepted the display request, and accepts the designation of the base and displays the input information items related to that base according to the authority of that role. This allows for flexible control over each account, while allowing for more appropriate information collection, for example, by allowing a person with individual authority in their own group who is closer to the site than a person with overall management authority or overall authority of the parent group to set the input information items for that base.

[0069] Fig. 25 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. The display control unit 118 receives a display request from a terminal (S1100), determines a hierarchical level from the group linked to the account operating the terminal, and displays information about locations related to groups at or below that hierarchical level (S1102). Below, explanations that overlap with those described as an example of the operation flow of the management device 100 according to the first embodiment using Figs. 13 and 14 will be omitted. Each operation will be described with reference to Fig. 26. Fig. 26 is a diagram showing an example of an information confirmation screen according to the second embodiment. The information confirmation screen has field 2601 for accepting the specification of the group for which information is to be entered, field 2602 for accepting the specification of whether or not to include lower levels (subordinates) of the group, field 2603 for accepting the specification of narrowing down the bases if lower levels of the group are to be included, field 2604 for accepting the specification of the fiscal year, field 2605 indicating whether the display period is yearly or monthly, field 2606 indicating various information classifications, and field 2607 for displaying confirmation screens for each piece of information depending on the contents specified in fields 2601 to 2606.

[0070] The display control unit 118 determines the hierarchical level from the group associated with the account operating the terminal 200 that has accepted the display request, and displays information about locations related to groups at or below that hierarchical level (S1102). Here, for example, if the "information about locations related to groups at or below that hierarchical level" is determined to be group C, hierarchical level 2 for the terminal 200 operated by the account with account code 0003, the display control unit 118 displays, on the display device of the terminal 200, information about locations c1 to c3, f1, and f2 associated with groups F to J at or below hierarchical level 2 of the group C, as shown in FIGS. 4, 5, and 18. For example, in FIG. 26, field 2601 shows group C associated with account code 0003. Here, the display control unit 118 may accept designation in field 2601 from one or more of groups F to J at a lower hierarchical level in addition to group C. 26 also shows that the display control unit 118 has specified "include subordinates" in field 2602 to include groups F to J ("subordinates" in FIG. 26) that are hierarchically lower than group C, and has narrowed down the locations linked to group C and its subordinate groups F to J to "c1, c3, f1" in "Narrowing down locations" in field 2603. Each piece of information shown in field 2607 is displayed as the sum of the values ​​entered for the locations c1, c3, and f1. This makes it possible to display information about locations linked to groups at lower levels in a more flexible and easy-to-understand manner.

[0071] Next, a management device according to a third embodiment will be described. The management device according to the third embodiment not only provides efficient group management and more accurate and simple information collection, but also realizes an approval function for collected information between groups. In the following, explanations of the third embodiment that are the same as those of the first or second embodiment will be omitted.

[0072] The management device according to the third embodiment is realized as the management device 100 in the management system 10 according to the first embodiment in FIG. 1, or as the management device 1500 in the management system 15 according to the second embodiment in FIG.

[0073] 27 shows an example of functional blocks of a management device 2700, which is a management device according to the third embodiment. The management device 2700 includes a control unit 2710, a communication unit 120, and a storage unit 130. The control unit 2710 includes a group setting unit 112, an account setting unit 114, an authority role unit 116, a base setting unit 1512, an input management unit 1514, an input receiving unit 1516, a display control unit 118, an approval authority setting unit 2712, an approval management unit 2714, and an approval processing unit 2716.

[0074] The approval authority setting unit 2712 accepts the designation of approval authority according to the account type and role. The approval authority setting unit 2712 also accepts the designation of approval authority for a child group designated as a parent group by a group. The approval authority setting unit 2712 also accepts the designation of approval authority for a location linked to a child group designated as a parent group by the group. These operations will be described in detail in the explanation of FIGS. 28 and 29 below.

[0075] The approval management unit 2714 may accept settings for operation management related to approval. The approval management unit 2714 may accept settings for the approval period. For example, the approval period may be set by fiscal year, and settings for the start and end of the approval period may be accepted using year-month or year-month-day.

[0076] The approval management unit 2714 may also accept settings for input items to be approved. The input items may be set for all groups and locations to be approved, or may be set for some groups and locations. The input items may be set uniformly for the groups and locations, or different input items may be set for some groups and locations. After accepting the settings for the input items, the approval management unit 2714 may accept a designation to make the input items public, private, or delete them. When accepting a designation to make the input items public, the approval management unit 2714 may control the display of the display unit of the terminal 200 via the display control unit 118 so that users who have account codes associated with the groups and locations to be approved can enter and confirm the input items on their terminals 200. This allows users of the groups and locations to enter and confirm the input items. The approval management unit 2714 may also record the date on which the designation to make the input items public is accepted as the location input start date and display it on the display unit of the terminal 200 via the display control unit 118.

[0077] The approval management unit 2714 may also accept a designation to make an input item private. In this case, control may be performed so that input and confirmation of the input item are disabled on the terminal 200 of a user who has an account code linked to the group and base to be approved. This makes it possible to temporarily suspend input and confirmation for all groups and bases when it becomes necessary to correct an input item that has once been made public. The approval management unit 2714 may also accept a designation to delete an input item. This makes it possible to delete an input item that is no longer necessary and thereby not subject it to approval.

[0078] The approval management unit 2714 may also accept settings for an approval flow. An approval flow may be set for all groups and locations that are subject to approval, or may be set for some groups and locations. An approval flow may be set uniformly for the groups and locations, or different approval flows may be set for some groups and locations. The approval management unit 2714 may also accept a designation for finalizing the approval flow. The approval management unit 2714 may record the date on which the designation for finalizing the approval flow is accepted as the approval start date and display it on the display unit of the terminal 200 via the display control unit 118. After accepting the designation for finalizing the approval flow, the approval management unit 2714 may perform control to prohibit the groups and locations that are subject to approval from entering or changing input items, or may perform processing to notify the groups and locations that are subject to approval of the start of approval so that they cannot enter or change input items.

[0079] The approval management unit 2714 may accept a designation of grouping of multiple locations. The grouping may be set as, for example, an "input pattern." Here, the approval management unit 2714 may accept information such as the name of the input pattern (e.g., a name representing a domestic location, an overseas location, or another specific group of locations), a description of the input pattern, target locations (e.g., a location selected as a location belonging to the input pattern from locations displayed for each group), and the input pattern of each location during the previous approval period, and this information may be displayed on the display unit of the terminal 200 operated by the user via the display control unit 118.

[0080] The input patterns set by the approval management unit 2714 may include a default input pattern that applies to all locations in advance. This saves the user the trouble of setting an input pattern that applies to all locations. The approval management unit 2714 may also accept a designation to set an arbitrary input pattern collectively for locations selected from the displayed list of locations.

[0081] When a group of multiple locations (e.g., input patterns) is accepted by the approval management unit 2714, the approval authority setting unit 2712 may accept the designation of approval authority for the grouped multiple locations. This allows, for example, locations that have a common input pattern to efficiently designate approval authority for information of the same data type.

[0082] Although the above describes a mode in which the approval management unit 2714 accepts grouping designations for multiple locations, the approval management unit 2714 may accept grouping designations for multiple groups and locations. In this case, for example, even for a group that does not include a location (especially an input location), it is possible to set grouping and specify approval authority based on the grouping.

[0083] The approval processing unit 2716 accepts an approval request for approval or rejection from an account that has been granted approval authority for specific information. When the approval processing unit 2716 accepts approval from the account, it processes the request as if it had accepted an approval request for the next approver, i.e., an account that has been granted further approval authority for the information approved by the account. When there is no next approver, i.e., when approval is accepted from the highest approver in the hierarchy, the approval processing unit 2716 performs approval completion processing. When accepting rejection, the approval processing unit 2716 notifies the account that made the approval request that it will be reconfirmed and performs processing to enable confirmation or input. If the account that received the rejection is not the person in charge of input, it performs processing to enable reconfirmation after the rejection. If the account that received the rejection is the person in charge of input, it performs processing to enable reinput after the rejection. These operations will be described in detail in the explanation of Figure 30 below.

[0084] 28 is a diagram showing an example of the operational flow of the management device 2700. The account setting unit 114 accepts the registration of an account (S2800), accepts the designation of the account group and account type (S2802), and accepts the designation of a role according to the account type (S2804). In addition, the approval authority setting unit 2712 accepts the designation of approval authority according to the designation of the account type and role (S2806).

[0085] Each operation will be described below with reference to Fig. 29. Fig. 29 is a diagram showing an example of an account table 2901 according to the third embodiment. Note that descriptions similar to those described with reference to Figs. 8 and 9 will be omitted.

[0086] The account setting unit 114 accepts the registration of an account (S2800). Here, the account table 2901 in Fig. 29 has an account code, an account type, a group name, a role, and an approval authority.

[0087] The account setting unit 114 receives the designation of the account group and account type (S2802) and also receives the designation of the role according to the account type (S2804).

[0088] The approval authority setting unit 2712 accepts the designation of approval authority according to the designation of the account type and role (S2806). Here, in the account table 2901 of FIG. 29, the approval authority is designated as "overall" for the account code 0001 or 0002, whose account type is "overall management authority" or "overall authority." The approval authority "overall" includes the authority to approve approval requests from groups at all hierarchical levels. For example, the approval authority "overall" may include the authority to give final approval after approvals have been given at all lower hierarchical levels, or the authority to approve approval requests at all lower hierarchical levels at any timing. The target of approval may be specific information, such as by data type. Furthermore, the approval authority "overall" includes not only the authority to give approval, but also the authority to cancel approval and send back information that has already been approved.

[0089] The designation of the approval authority as "all" for account code 0001 or 0002, whose account type is "overall management authority" or "overall authority," may be automatically specified when the account type is specified as "overall management authority" or "overall authority." In this case, the user can specify the approval authority simply by specifying the account type, making it easier to set the approval authority. Furthermore, the above designation may be specified by accepting a selection of the approval authority as "all" by a user operating terminal 200 for an account whose account type is "overall management authority" or "overall authority." In this case, the user can select the approval authority as "all" only for any of the accounts whose account type is "overall management authority" or "overall authority," making it possible to set the approval authority more flexibly.

[0090] The approval authority setting unit 2712 may also accept a designation of approval authority for a child group that has a group designated as a parent group. In the account table 2901 of FIG. 29, the approval authority for account code 0003 or 0008, whose account type is "individual authority" and whose role is "including subsidiaries," is designated as "yes" or "no." The approval authority "yes" includes the authority to approve approval requests submitted by groups at a lower level. The target of approval may be specific information, such as by data type. The approval authority setting unit 2712 may also accept a designation of approval authority for a base associated with a child group that has a group designated as a parent group. In the account table 2901 of FIG. 29, the approval authority for account code 0003, whose account type is "individual authority" and whose role is "including subsidiaries," is designated as "yes," thereby setting approval authority for bases to which users with account codes 0005 to 0007, whose account type is "input person," belong. The approval authority may be set to all input locations "under" the group of the user with the approval authority, or may be selectively set by operating the terminal 200 for some of the groups or locations under the group. Furthermore, the "yes" approval authority may include, in addition to the authority to approve, the authority to cancel and return approval of already approved information. In this case, if corrections are required after approval, a user of an account with "yes" approval authority under "individual authority" can make post-approval corrections by operating the terminal 200. On the other hand, the "yes" approval authority may not include, in addition to the authority to approve, the authority to cancel and return approval of already approved information. In this case, post-approval corrections cannot be made by operating the terminal 200 of a user of an account with "yes" approval authority under "individual authority," but can only be made by operating the terminal 200 of a user of an account with "overall management authority" or "overall authority" approval authority set to "overall." This controls the approval process and promotes more careful approval work. The "no" approval authority indicates that approval authority is not set for the account.

[0091] The approval authority for account code 0003 or 0008, whose account type is "individual authority" and whose role is "including subsidiaries," may be automatically set to "yes" or "no" according to predetermined conditions. For example, the approval authority may be set to "yes" for the smallest account code or any number of account codes in a group whose account type is "individual authority" and whose role is "including subsidiaries," and "no" for the remaining account codes. In this case, the user can specify the approval authority simply by specifying the account type and role, making it easier to set the approval authority. Furthermore, the above designation may be made by accepting a selection of "yes" or "no" for the approval authority by operating terminal 200 by a user of an account code whose account type is "overall management authority" or "overall authority," or whose account type is "individual authority" for the corresponding group. In this case, the user can assign approval authority to any person in the corresponding group, making it easier to set the approval authority.

[0092] Furthermore, although not shown in the account table 2901 of FIG. 29 , an account type for users who do not belong to a group constituting a hierarchy, such as an "external" account type, may be set. Then, for the "external" account type, a role that grants authority to the "external" account type, such as "third-party assurance" or "auditor," may be set as a role. For example, for a terminal 200 operated by a user with an account code set as the "third-party assurance" or "auditor" role, the display control unit 118 may control the display so that only specific information, such as approved information, can be viewed. Furthermore, the control unit 2710 may perform processing to output audit information in a data format such as CSV in a lump sum in response to a user's operation of the terminal 200. Furthermore, the control unit 2710 may perform processing to output all approval target information in a lump sum after an audit in response to a user's operation of the terminal 200.

[0093] FIG. 30 is a diagram illustrating an example of an operation flow of the management device 2700 according to the third embodiment. The approval processing unit 2716 accepts an approval request (S3000). Here, the approval request may be executed on the terminal 200 operated by a user having an account code associated with a group for which approval authority has been set by the approval authority setting unit 2712. For example, the approval request may be executed by the user confirming the information displayed in field 1404 or field 2607 on the information confirmation screen shown in FIG. 14 or FIG. 26 and submitting the information to the approver of the group above. This process may be executed by, for example, changing the “status” on the information confirmation screen from “checking” to “submitted” (not shown). Alternatively, the approval request may be executed by a person in charge of inputting information on the information input screen shown in FIG. 22 and submitting the information to the administrator of the group (for example, a user having an account code whose account type is “individual authority,” “overall management authority,” or “overall authority”). This processing may be performed, for example, by changing the "status" on the information input screen from "inputting" to "submitted" (not shown). The approval processing unit 2716 may also accept, along with the above information, information to be handed over when submitting an approval request. The approval processing unit 2716 may also accept, along with the above information, comment information that has been accepted simultaneously with or in advance for the approval request. The approval processing unit 2716 may also notify the approver of the approval request via email or other communication means at the same time as accepting the approval request. The notification may be made immediately, or may be made by batch processing at intervals of 10 minutes, 30 minutes, 1 hour, or any other desired time interval. The approval processing unit 2716 may also accept, in addition to accepting approval requests, notifications prompting input, such as input request notifications and reminder notifications.

[0094] The approval processing unit 2716 displays the information to be approved (S3002). That is, after accepting the approval request in S3000, the approval processing unit 2716 performs processing to display the information to be approved on the display unit (not shown) of the terminal 200 operated by a user who has an account code that is set with authority to approve the approval request, via the display control unit 118. The information to be approved is information displayed in field 1404 or field 2607 on the information confirmation screen shown in FIG. 14 or FIG. 26 that was displayed on the display unit (not shown) of the terminal 200 operated by the user who made the approval request at the time the approval request was completed, or information entered by a person in charge of inputting information on the information input screen shown in FIG. 22. In addition, the approval processing unit 2716 may accept narrowing conditions for the information to be approved, and display only information that satisfies the conditions on the display unit of the terminal 200 operated by the user, via the display control unit 118.

[0095] The approval processing unit 2716 accepts a designation of approval or rejection (S3004). That is, after displaying the information to be approved in S3002, the approval processing unit 2716 accepts a designation of whether to approve the information to be approved or to reject the approval request, through an operation of the terminal 200 operated by a user having an account code that is set with authority to approve the approval request. The approval processing unit 2716 may accept a designation of approval or rejection for all information to be approved. Furthermore, the approval processing unit 2716 may accept a designation of approval or rejection for each specific piece of information to be approved. For example, the approval processing unit 2716 may accept a designation of approval or rejection for each type of data to be approved. In this case, the operation flow described below may be performed for each piece of information to be approved. In this case, the approval processing unit 2716 may display, via the display control unit 118, on the display unit of the terminal 200 operated by the user, the type or classification of the information to be approved, the number of input locations, a status indicating the approval status (e.g., under review, confirmed, approved, and returned), and a comment indicating completion for each piece of information to be approved. If the number of input locations is large, the display control unit 118 may display the ratio of the number of input locations to the total number of locations in a graph such as a bar graph or pie chart to enable high-visibility understanding of the current situation. The approval processing unit 2716 may further display the type or classification of the information for each group and location, and various information such as the status and a comment indicating completion. The approval processing unit 2716 may record information such as the date and time of each approval and the person who carried out the approval as a history in the memory unit 130 or another storage device. The display control unit 118 may display the history as a list of a series of approvals for the same piece of approval information on the display unit of the terminal 200.

[0096] When approval is received in S3004 ("Approved" in FIG. 30), the approval processing unit 2716 determines whether there is a next approver (S3006). That is, the approval processing unit 2716 determines whether there is an account code for which approval authority has been set in a group one level higher than the group linked to the account code of the user who selected approval, or whether there is an account code for which approval authority has been set as "all." If there is such an account code ("Yes" in FIG. 30), it executes processing to accept the approval request in S3000, assuming that an approval request has been made for that account code. On the other hand, if there is no such account code ("No" in FIG. 30), it completes the approval processing (S3008). That is, it executes processing to assume that approval has been completed for all information entered and confirmed during the period set as the approval target period. In this case, the approval processing unit 2716 may not accept any corrections, additions, deletions, etc. to approved information. This makes it possible to systematically prove that no subsequent corrections, additions, deletions, etc. have been made to approved information through third-party assurance, audits, etc. Furthermore, when the above approval process is completed, the approval processing unit 2716 may further accept a post-approval correction request (not shown). This makes it possible to systematically prove that information after approval has not been corrected, added to, deleted, etc., unless a special procedure is followed, and to identify information that has been corrected, added to, deleted, etc., after approval through the special procedure.

[0097] When the approval processing unit 2716 receives a send-back in S3004 ("Return" in FIG. 30), it executes the send-back process (S3010). That is, the approval processing unit 2716 displays "Return" as the "Status" of the sent-back information on the display unit of the terminal 200 of the user who selected the send-back, while displaying "Return" as the result of the approval request on the display unit of the terminal 200 of the user who made the approval request, and simultaneously performs processing to resume accepting confirmation or input for the information (not shown). Furthermore, the approval processing unit 2716 may receive a send-back designation by user operation for "subordinate" groups and bases belonging to the groups all at once, or may receive a selective designation only for groups or bases directly below.

[0098] As described above, the management device according to the third embodiment can realize efficient group management, more accurate and simple information collection, and also an approval function for collected information between groups.

[0099] In addition to the above-described embodiment, the present invention can also be realized in the following multiple other embodiments.

[0100] In another embodiment, the management device 100, 1500, or 2700 may include a derivation unit. The derivation unit may derive the greenhouse gas emissions by multiplying the usage amount of at least one of electricity, water, oil, and gas by conversion data stored in the memory unit 130. In this case, the greenhouse gas emissions are derived by multiplying each usage amount by a basic unit (conversion data) indicating the greenhouse gas emissions per unit of usage. Furthermore, when deriving the amount of waste from the above usage amounts, the amount of waste may be derived by multiplying each usage amount by a basic unit (conversion data) indicating the amount of waste per unit of usage. In addition, the derivation unit may derive each amount from each usage amount by using a basic unit indicating the amount per unit of each usage amount for each secondary output as conversion data, such as the amount of substances such as by-products, NOx, SOx, BOD, COD, etc., air pollution, indoor air pollution, hazardous chemicals, ozone layer depletion, acidification, noise, global warming, photochemical oxidants, eutrophication, resource consumption, ecotoxicity, fuel consumption, land use, etc., impact areas, human health based on damage assessment, social estimates, biodiversity, primary production, etc., protected targets, etc.

[0101] The above usage may include fuel consumption for the operation of facilities. Fuels may include solid fuels (metallurgical coal, steam coal, anthracite, coke, petroleum coke, briquettes or briquettes, wood, charcoal, and other solid fuels), liquid fuels (coal tar, petroleum asphalt, condensate, crude oil (excluding condensate (NGL)), gasoline, naphtha, jet fuel, kerosene, diesel, heavy oil A, heavy oil B, heavy oil C, lubricating oil, and other liquid fuels), and gaseous fuels (liquefied petroleum gas (LPG), petroleum hydrocarbon gas, liquefied natural gas (LNG), natural gas (excluding liquefied natural gas (LNG)), coke oven gas, blast furnace gas, converter gas, town gas, and other gaseous fuels). Activities related to the production of products related to the usage may consume at least one of heat and steam.

[0102] In another embodiment, the display control unit 118 may control the display of information derived by the derivation unit using the conversion data as "secondary data" and other input data as "primary data" (or, if each piece of information includes information about data quality and the information is identified as "primary data" or "secondary data," the identified data). Furthermore, the same conversion data may be used for all bases in common input information fields. This allows the application of the conversion data to be optimally maintained by adding, modifying, etc. the conversion data in the common input information fields, even after information input requests have been made to each base.

[0103] The information managed by the management device 100, 1500, or 2700 may also include at least one of greenhouse gas emissions related to production, human rights measures, and disaster risk measures. Human rights measures may indicate, for example, whether measures are being taken to prevent child labor in the manufacture of products (including all processes related to the manufacture of products, such as not only the assembly and processing of the product itself, but also the assembly and processing of the parts that make up the product, and the processing of the materials (including raw materials) that make up each part). Disaster risk measures may indicate whether measures are being taken to prevent the manufacture of products from being affected in the event of a disaster. In addition to the above, the data managed by the management device 100, 1500, or 2700 may also include any other information that the company wishes to request its affiliated companies to input. For example, data on environmental impact assessments (e.g., damage assessments), product carbon footprints (related to climate change), biodiversity, land use, and raw material procurement (related to natural resources), hazardous substances, waste management, packaging materials, and home appliances (related to waste disposal), chemical substances, air pollutants, water quality, and soil contamination (related to environmentally regulated substances), and other environmental technologies, energy, noise, vibration, and odors. Social data on human rights (e.g., child labor, forced labor, working hours, wages, labor rights, and discrimination), labor management and health and safety, and human capital, safety and quality (related to product and service safety), safety of each substance, privacy and data security, community relations, diversity, equity, and inclusion, well-being and engagement, compliance and ethics, and other social data may also be included. Governance data on corporate ethics, compliance with laws and regulations, anti-corruption, risk management, disaster prevention, tax transparency, and other governance-related data may also be included. Due diligence data on each of the above items may also be included. The specification or input of the input information items relating to these pieces of information is shown in field 2206 and field 2607 in the category indicated as "Questionnaire" in field 2205 of FIG. 22 and field 2606 of FIG. 26, and each specification or input may be accepted.

[0104] In another embodiment, the management device 100, 1500, or 2700 may further include an administrator setting unit. The administrator setting unit accepts settings for whether each item is editable based on the account type or role. For example, among the environmental information for each site, items that are required to be collected by an individual with overall management authority can be set to be non-editable (uneditable) for any account type or role. This allows individuals with individual authority closer to the site to independently add input information items deemed necessary for each classification, and allows editing of items related to reasons for discrepancies, whether or not comments can be entered, whether or not attachments are required, threshold settings, linking to conversion data such as specific basic units, etc., providing flexibility. Meanwhile, by requiring information collectors to provide information on the information items required as described above, flexible and consistent information collection can be achieved.

[0105] As another embodiment, field 2206 for Scope 2 (GHG Protocol indirect emissions related to electricity, heat, hot water, steam, cold heat, and chilled water) among the various information categories shown in field 2205 in FIG. 22 may include activity data such as the amount of electricity, heat, hot water, steam, cold heat, and chilled water used, the amount of electricity generated through self-generation and corporate PPAs, surplus electricity, purchased electricity, sold electricity, and the amount of other energy sold to external parties. It may also include the amount of certificates and credits procured that are applicable to Scope 2. Furthermore, when power generation and supply are conducted between groups to be managed, the group setting unit 112 may accept the registration of a dummy group for offsetting between groups. The power plan for the dummy group is then registered along with the emissions intensity of the generating group, and the group receiving the power is registered as a tenant, and the tenant supply amount is set. This results in a negative GHG emission for the dummy group, enabling management of power generation and supply between groups.

[0106] In another embodiment, the management device 100, 1500, or 2700 may include an estimation unit (not shown). In the above-described other embodiment, an example was shown in which the derivation unit performs calculation processing based on the converted data stored in the memory unit 130. Meanwhile, the estimation unit may perform various estimations based on the data. For example, for the categories indicated as "water" and "waste" in field 2205 of FIG. 22 and field 2606 of FIG. 26, source data for various estimations is set as the input information items indicated in fields 2206 and 2607. For example, for the "water" category, a measurement type is set as the input information item, and options such as an actual measurement value, an estimated value (calculated using a reference value), and an estimated value (where wastewater volume = water intake volume) may be set as the measurement type. If the measurement type is designated as an estimated value, the display control unit 118 may estimate each water-related quantity (water intake, wastewater discharge, etc.) by referencing reference values ​​based on various input information items required for the estimation (e.g., estimates from the entire building, etc., estimates from other locations, estimates using other numbers of people, area, etc.). Similarly, for "waste," options such as actual measured value or estimated value (calculated using reference value) may be set as the measurement type. Note that the input management unit 1514 may accept, as input information items, conversion data such as unit consumption, and reference indicators such as production quantity, number of people produced, production volume, and production cost for each location, and the display control unit 118 may display the reference indicator or a combination of the reference indicator and each input information item (e.g., water usage per production volume). This makes it possible to easily display evaluation indicators between locations.

[0107] The estimation unit may also perform statistical processing such as regression analysis on the data stored in the memory unit 130 to interpolate, predict, and so on each piece of information. The estimation unit may also perform machine learning (deep learning, reinforcement learning, and so on) based on the data stored in the memory unit 130 to perform various estimations, classifications, predictions, and so on. A learning model may be stored in the memory unit 130, and the learning model may be a learning model generated by machine learning using each piece of data as training data. For example, a prediction of electricity demand may be realized using a learning model generated based on information such as weather, temperature, power plant shutdown information, power supply reserve margin, available interconnection capacity, forward curves (including those related to electricity, coal, crude oil, and LNG), coal import prices, crude oil import prices, LNG import prices, and past fluctuations in electricity trading prices in the electricity spot market, or a statistical method based on this information. Regarding classification, machine learning models or algorithms may solve classification problems and may include, for example, logistic regression (including ridge regularization and lasso regularization), random forests, support vector machines, and neural networks (including multilayer perceptrons). The accuracy of these classification predictions may be evaluated using one or more of the following: the mean square error of the estimated conditional probability; the area under the ROC (Receiver Operating Characteristic) curve (AUC), which is quantified as the area under the curve; the logarithmic loss in the Kullback-Leibler divergence minimization problem; and a calibration plot that plots actual values ​​and predicted values. The accuracy of classification predictions by machine learning algorithms or models varies depending on the number of training data and feature quantities (e.g., the number of days for acquiring the electricity usage data used for learning and the attribute information added). Therefore, a learning model may be selected by comparing the evaluation results of the classification accuracy of each machine learning algorithm or model under predetermined conditions. In selecting a learning model, priority may be given to models with low computational costs for learning and classification.As described above, the estimation unit enables the management device to predict, classify, and otherwise control the display of related data that is different from the data received by the communication unit, as well as to identify, derive, and provide instructions for dealing with the data.

[0108] In another embodiment, the display control unit 118 may perform aggregation for a specific item for the entire hierarchy and control display of the graph on the display unit of the terminal 200. The aggregation may be performed by accepting designation of aggregation items, items to be displayed on the vertical axis, and items to be displayed on the horizontal axis for a specific aggregation setting target. For example, the specific aggregation setting target may be greenhouse gases, electricity, or other information. Furthermore, if the aggregation setting target is greenhouse gases, the aggregation items may include emissions (which may be greenhouse gas emissions or more detailed emissions such as greenhouse gas emissions after offsetting), the monetary value of related activities, activity volume, and other quantities. Here, activity volume may be controlled so that it can be specified only if an emission intensity is specified for the item to be displayed on the vertical axis below. This allows the relationship between emissions and activity volume to be displayed with high visibility by using the emission intensity. Furthermore, the items to be displayed on the vertical axis may be designated by designating the information classifications shown in field 2606 in FIG. 26 or their detailed classifications as major, medium, and minor categories, as well as designating a comparison target and a base year. The items to be displayed on the horizontal axis may include the display period, which may be set as any period such as year, month, day, etc. The above aggregation may be performed by accepting the specification of items to be displayed on a total of three or more axes in addition to the vertical and horizontal axes.

[0109] The display control unit 118 may also control the display of the data as a graph on the display unit of the terminal 200 according to the filtering conditions received in the aggregation of a specific item for the entire hierarchy. The filtering conditions may include, for example, a group, whether or not it includes a group under the group, a company, a location, a business, an organization, a facility classification, a greenhouse gas scope, and a Scope 3 category.

[0110] The display control unit 118 controls the display of the counted quantity as a graph on the display unit of the terminal 200. The display control unit 118 displays the graph according to the above counting settings and, if applicable, the quantities of the counted items to which the filtering conditions have been applied, the items specified on the vertical and horizontal axes, and, if applicable, the items specified as additional axes. The display control unit 118 may also display a screen that accepts designation of major, medium, and minor categories near the graph. Here, when the display control unit 118 accepts designation for each category, it may display a graph that targets all items for the category one level below the category. This takes into account all items for the specified category, making it possible to improve the visibility of the graph with simple operations.

[0111] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications and improvements can be made to the above embodiments. It is clear from the claims that such modifications and improvements can also be included within the technical scope of the present invention.

[0112] It should be noted that the execution order of each process, such as operations, procedures, steps, and stages, in the devices, systems, programs, and methods shown in the claims, specifications, and drawings is not specifically stated as "before," "prior to," etc., and that the processes can be performed in any order unless the output of a previous process is used in a subsequent process. Even if the operational flow in the claims, specifications, and drawings is described using "first," "next," etc. for convenience, this does not mean that the processes must be performed in this order.

[0113] Furthermore, aspects of each embodiment may be embodied in whole or in part by a computer. As an example of such a computer, a program installed on the computer can cause the computer to perform operations associated with an apparatus according to an embodiment of the present invention or to function as one or more "parts" of the apparatus. Alternatively, the program can cause the computer to execute the operations or one or more "parts." The program can cause the computer to execute a process or steps of the process according to an embodiment of the present invention. Such a program may be executed by a CPU to cause the computer to perform specific operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.

[0114] In one aspect of the present invention, the following management device, management method, and management program are realized. (Item 1) A management device comprising a group setting unit that accepts registration of a group, accepts designation of a parent group of the group, and generates a hierarchical code for the group in accordance with the designation of the parent group using the hierarchical code of the parent group. (Item 2) Item 1. The management device according to item 1, wherein the group setting unit generates the hierarchical code of the group by placing the group code of the group after the hierarchical code of a parent group of the group. (Item 3) an account setting unit that accepts registration of an account, accepts designation of a group and account type of the account, and accepts designation of a role according to the account type; Item 1. The management device according to item 1, further comprising: an authority role setting unit that accepts registration of authority items for the roles and accepts designation of authority for the roles for each item for each of the groups. (Item 4) The management device described in item 3 further includes a display control unit that receives a display request from a terminal, determines a role associated with an account that operates the terminal, and displays information about the group according to the authority of the role. (Item 5) The management device described in item 1 further includes a display control unit that receives a display request from a terminal, determines a hierarchy from a group linked to an account operating the terminal, and displays information about groups below that hierarchy on a display device of the terminal. (Item 6) A management method comprising a step in which a group setting unit accepts registration of a group, accepts designation of a parent group of the group, and generates a hierarchical code for the group in accordance with the designation of the parent group using the hierarchical code of the parent group. (Item 7) A management program for causing a computer to execute the management method described in item 6.

[0115] In another aspect of the present invention, the following management device, management method, and management program are realized. (Item 1) a group setting unit that accepts group registration; an account setting unit that accepts registration of an account and accepts designation of a group and account type of the account; a base setting unit that accepts registration of bases and accepts designation of master information including the group for each base; (Item 2) The management device described in item 1, wherein the account setting unit displays candidate accounts from the group according to the account type, and associates a selected account from the candidate accounts with the specified location as the person in charge of input. (Item 3) Item 1. The management device according to item 1, further comprising an input management unit that displays common input information items for each location and accepts designation of input information items for each location. (Item 4) The management device described in item 3 further includes an input receiving unit that receives a display request from a terminal operated by a person in charge of input at a base, displays input information items specified for the base, receives input for each item of input information from the terminal, executes processing according to each specification, and saves the results according to the processing. (Item 5) The management device described in item 3 further includes a display control unit that receives a display request from a terminal, determines a role associated with an account operating the terminal, receives a location designation according to the authority of the role, and displays input field information related to the location. (Item 6) The management device described in item 3 further includes a display control unit that receives a display request from a terminal, determines a hierarchy from a group linked to an account operating the terminal, and displays information about locations related to groups at or below that hierarchy. (Item 7) a step in which a group setting unit accepts registration of a group; an account setting unit accepting registration of an account and accepting designation of a group and an account type of the account; a step in which the base setting unit accepts registration of the base and accepts designation of master information including the group for each base. (Item 8) A management program for causing a computer to execute the management method described in item 7.

[0116] In another aspect of the present invention, the following management device, management method, and management program are realized. (Item 1) a group setting unit that accepts registration of a group, accepts designation of a parent group of the group, and generates a hierarchical code of the group in accordance with the designation of the parent group using the hierarchical code of the parent group; an account setting unit that accepts registration of an account, accepts designation of a group and account type of the account, and accepts designation of a role according to the account type; an approval authority setting unit that accepts designation of approval authority according to the account type and the role. (Item 2) 2. The management device according to claim 1, wherein the approval authority setting unit accepts a designation of approval authority for a child group designated with the group as a parent group. (Item 3) a base setting unit that accepts registration of bases and accepts designation of master information including the group for each base; 2. The management device according to claim 1, wherein the approval authority setting unit accepts a designation of approval authority for a base linked to a child group designated with the group as a parent group. (Item 4) further comprising an approval management unit that accepts grouping designations for a plurality of bases; 4. The management device according to claim 3, wherein the approval authority setting unit accepts a designation of approval authority for the plurality of bases that have been grouped. (Item 5) a step of accepting a registration of a group, accepting a designation of a parent group of the group, and generating a hierarchical code of the group in accordance with the designation of the parent group using the hierarchical code of the parent group; accepting registration of an account, accepting designation of a group and account type of the account, and accepting designation of a role according to the account type; and receiving a designation of approval authority according to the account type and the role. (Item 6) A management program for causing a computer to execute the management method according to claim 5. [Explanation of symbols]

[0117] 10, 15 Management System 50 Network 100, 1500, 2700 management devices 110, 1510, 2710 Control unit 112 Group setting section 114 Account Settings 116 Authorization role setting section 118 Display control unit 120 Communications Department 130 Storage section 200 devices 300 Transmitting device 401, 601 hierarchy 402, 602 groups 501, 701 Group Table 901, 2901 Account Table 1101 Group Name 1102 Roll 1103 Authority 1401 Group 1402 including subsidiaries 1403 Filter 1404 Information Field 1512 Base Setting Department 1514 Input Management Unit 1516 Input reception unit 1801 Location Table 2001 List of additional locations 2002 Data entry staff 2003 Candidate List 2004 Designated Field 2005 Field indicating candidate account 2201 Group 2202 bases 2203 fiscal year 2204 per year / month 2205 Classification field 2206 A field indicating the input information item to be set 2601 Group 2602 including subsidiaries 2603 Narrow down your bases 2604 year 2605 per year / month 2606 Classification field 2607 Field indicating the input information item to be checked 2712 Approval Authority Setting Unit 2714 Approval Management Department 2716 Approval Processing Unit

Claims

1. a group setting unit that accepts registration of a group, accepts designation of a parent group of the group, and generates a hierarchical code of the group in accordance with the designation of the parent group using the hierarchical code of the parent group; an account setting unit that accepts registration of an account, accepts designation of a group and an account type of the account, and accepts designation of a role according to the account type; an approval authority setting unit that accepts designation of approval authority according to the account type and the role.

2. The management device according to claim 1 , wherein the approval authority setting unit accepts a designation of approval authority for a child group designated with the group as a parent group.

3. a base setting unit that accepts registration of a base and accepts designation of master information including the group for each base; The management device according to claim 1 , wherein the approval authority setting unit accepts a designation of approval authority for a base linked to a child group designated with the group as a parent group.

4. further comprising an approval management unit that accepts grouping designations for a plurality of bases; The management device according to claim 3 , wherein the approval authority setting unit accepts a designation of approval authority for the plurality of bases grouped together.

5. a step of accepting registration of a group, accepting designation of a parent group of the group, and generating a hierarchical code of the group in response to the designation of the parent group using the hierarchical code of the parent group; accepting registration of an account, accepting designation of a group and an account type of the account, and accepting designation of a role according to the account type; and receiving a designation of approval authority according to the account type and the role.

6. A management program for causing a computer to execute the management method according to claim 5.

Images