Management device, management method, and management program

Abstract

This management device may comprise a group setting unit that receives registration of a group, receives designation of a parent group of the group, and generates a hierarchical code of the group using a hierarchical code of the parent group in accordance with the designation of the parent group. The management device may comprise: a group setting unit that receives registration of a group; an account setting unit that receives registration of an account, and receives designation of a group and an account type of the account; and a base setting unit that receives registration of a base and receives designation of master information including the group on a per-base basis.

Description

Management device, management method, and management program

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

[0002] Patent Document 1 discloses a database management device. [Prior art documents] [Patent documents] [Patent document 1] JP 2019-219847 A General disclosure

[0003] 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 for the group in accordance with the designation of the parent group using the hierarchical code of the parent group.

[0004] In the management device, the group setting unit generates the hierarchical code of the group by placing the group code of the group after the hierarchical code of the group's parent group.

[0005] The management device 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 according to the account type, and further includes an authority role setting unit that accepts registration of authority items for the role, and accepts designation of authority for the role for each item for each group.

[0006] The management device 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.

[0007] The management device further includes a display control unit that receives a display request from a terminal, determines a hierarchy from a group linked to an account that operates the terminal, and displays information about groups at or below that hierarchy on a display device of the terminal.

[0008] A management method according to one aspect of the present invention includes 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.

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

[0010] A management device according to one aspect of the present invention includes a group setting unit that accepts registration of a group, an account setting unit that accepts registration of an account and accepts designation of a group and an account type for the account, and a base setting unit that accepts registration of a base and accepts designation of master information including the group for each base.

[0011] In the management device, the account setting unit displays candidate accounts from the group according to the account type, and associates an account selected from the candidate accounts with the designated base as a person in charge of input.

[0012] The management device further comprises an input management unit that displays common input information items for each base and receives designation of input information items for each base.

[0013] The management device further includes an input reception unit that receives a display request from a terminal operated by a person in charge of input at a base station, displays input information items specified for the base station, 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.

[0014] The management device 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, receives a location designation according to the authority of the role, and displays input field information related to the location.

[0015] The management device further includes a display control unit that receives a display request from a terminal, determines a hierarchy from a group linked to an account that operates the terminal, and displays information about locations related to groups at or below that hierarchy.

[0016] A management method according to one aspect of the present invention includes a step in which a group setting unit accepts registration of a group, an account setting unit accepts registration of an account and accepts designation of a group and an account type for the account, and a base setting unit accepts registration of a base and accepts designation of master information including the group for each base.

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

[0018] 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.

[0019] 1 is a diagram illustrating an example of the overall configuration of a management system according to a first embodiment. FIG. 1 is a diagram illustrating an example of functional blocks of a management device according to a first embodiment. FIG. 2 is a diagram illustrating an example of an operation flow of a management device according to a first embodiment. FIG. 3 is a diagram illustrating an example of a hierarchical relationship of groups according to a first embodiment. FIG. 4 is a diagram illustrating an example of a group table according to a first embodiment. FIG. 5 is a diagram illustrating an example of a hierarchical relationship of groups according to a first embodiment. FIG. 6 is a diagram illustrating an example of a group table according to a first embodiment. FIG. 7 is a diagram illustrating an example of an operation flow of a management device according to a first embodiment. FIG. 8 is a diagram illustrating an example of an account table according to a first embodiment. FIG. 9 is a diagram illustrating an example of an operation flow of a management device according to a first embodiment. FIG. 10 is a diagram illustrating an example of an authorization role setting screen according to a first embodiment. FIG. 11 is a diagram illustrating an example of an operation flow of a management device according to a first embodiment. FIG. 12 is a diagram illustrating an example of an information confirmation screen according to a first embodiment. FIG. 13 is a diagram illustrating an example of the overall configuration of a management system according to a second embodiment. FIG. 14 is a diagram illustrating an example of functional blocks of a management device according to a second embodiment. FIG. 15 is a diagram illustrating an example of an operation flow of a management device according to a second embodiment. FIG. 16 is a diagram illustrating an example of a base table according to a second embodiment. FIG. 17 is a diagram illustrating an example of an operation flow of a management device according to a second embodiment. FIG. 11 is a diagram showing an example of an information confirmation screen according to the second embodiment.

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

[0021] In recent years, there has been a growing need for companies and organizations to efficiently collect information from many related groups of organizations. As the number of groups increases, the relationships between groups become more complex, creating a need for unified management. Furthermore, those who collect information want to collect more information more accurately, while those who provide information want to provide it more easily.

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

[0023] 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.

[0024] 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. Additionally, 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, RAM, ROM, HDD, SSD, or other storage medium. The storage unit 130 may store various information as data in tables and store a database configured by associating each table.

[0025] The control unit 110 includes a group setting unit 112, an account setting unit 114, an authorized role setting 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 authorized 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.

[0026] 3 is a diagram showing an example of the operation flow of the management device 100 according to the first embodiment. The group setting unit 112 accepts the registration of a group (S100), accepts the 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).

[0027] The group setting unit 112 accepts the registration of a group (S100). The group is registered by, for example, a group creation operation using the terminal 200. Specifically, the group setting unit 112 accepts the registration of a group by, for example, creating a group name and assigning a group code to the group through 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 national or local government.

[0028] 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 (hierarchies 1, 2, 3, and 4 are shown, but are not limited to these and may include more hierarchies such as hierarchies 5, 6, 7, 8, etc.) and group names 402 indicating groups in each hierarchical level (hierarchies A, B, C, etc. and hierarchical levels J are shown, but are not limited to these and may include more groups such as hierarchical levels K, L, etc.). For example, the hierarchies may represent relationships between companies such as a holding company, headquarters, subsidiaries, sub-subsidiaries, affiliated companies, and overseas offices, or may include groups within a company, or may represent connections between any other organizations.

[0029] 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 in hierarchical level 2, groups D to H in hierarchical level 3, and groups I and J in hierarchical level 4. The lines in the figure indicate the hierarchical connections between groups. For example, because groups B and C are both connected to group A by a line, 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.

[0030] 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. The display control unit 118 may also display part or all of the group table 501 shown in Fig. 5 on a display device. The following figures relating to tables are similar, and their explanations will be omitted.

[0031] The group table 501 includes, but is not limited to, a group code, a group name, a parent group name, and a hierarchical code. Other information may be included, 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. While FIG. 5 uses numbers 1, 2, 3, . . . 10, the numbering is not limited to this, 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, parent groups represent groups in higher hierarchical levels linked to the group. For example, in FIG. 5, group A does not have a parent group, and therefore group A is at 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 at hierarchical level 2 linked to group A (hierarchical level 1).

[0032] 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's parent group after the hierarchical code of the group. However, for groups without 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 (whose parent group is group B) at hierarchical level 3 is " / 1 / 2 / 4 / ," which is the hierarchical code of the parent group " / 1 / 2 / " followed by the group code "4" of group D. In this way, by generating the hierarchical code of a group at a certain 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 the hierarchies of many groups can be represented in a unified manner.

[0033] Fig. 6 is a diagram showing an example of the hierarchical relationship of groups according to the first embodiment, showing 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 level 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.

[0034] 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.

[0035] 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 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.

[0036] Here, an example of the operation of the group setting unit 112 for changing the group and hierarchical relationship 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 at hierarchical level 1 when group C, which was its parent group, is deselected (for example, by designating it as no parent group). At this time, the group setting unit 112 deletes " / 1 / 3" from group G's hierarchical code " / 1 / 3 / 7 / " that precedes the group code "7" of group G due to the deselection of the parent group, and updates the hierarchical level code of group G to " / 7 / ." Note that, although not shown in Figures 4 and 5, if there are groups linked to group G at a lower hierarchical level, 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.

[0037] 4 and 5, group A, which was at 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, the 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 description has been given assuming that there are no groups at lower hierarchical levels linked to group A in FIGS. 4 and 5; however, at the same time that 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.

[0038] 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 parent group's hierarchical code in response to the parent group designation (S104 in FIG. 3). This allows the group and 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 established hierarchical table for hierarchical changes. The group setting unit 112 may then designate a change flag for any hierarchical changes, such as addition, replacement, or deletion, at the time of the change and record the change date / time in the table. This allows for a history of past hierarchical changes to be maintained.

[0039] Although FIGS. 4 to 7 show an example in which there is one group in layer 1, this is not limitative and layer 1 may have multiple groups.

[0040] Fig. 8 is a diagram showing an example of the operational 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.

[0041] 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 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.

[0042] 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 numbering may be performed by determining unused values ​​from the smallest number of digits, or by randomly generating numbers using a function or the like, and excluding any duplicate values.

[0043] The account setting unit 114 accepts the designation of the account group and account type (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 may be automatically designated 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.

[0044] In the account table 901 of FIG. 9 , the account type indicates the type of account and distinguishes the role and authority of each account. In FIG. 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 FIGS. 10 and 11 , etc. The account types are not limited to these and may include any other account types, 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.

[0045] Furthermore, in the account table 901 of Fig. 9, the 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 the group table 501 of Fig. 5 or the group table 701 of Fig. 7, and the 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 the group table 501 of Fig. 5 or the group table 701 of Fig. 7, and the account table 901 may reference the group table 501 of Fig. 5 or the group table 701 of Fig. 7 using the group code of group C (not shown in Fig. 9) as a foreign key.

[0046] In the account table 901 of Figure 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 tier 1 in Figures 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 them to operate on all management devices 100, or their account type is overall authority, which allows them to operate on all groups. In other embodiments, it may be necessary to associate the account table with the group table. In that case, for example, in Figure 9, the account codes 0001 and 0002 have the account type of overall management authority or overall authority, so the group name A to which they belong may be omitted.

[0047] The account setting unit 114 accepts the role designation 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 illustrates a case where role setting is possible when the account type is individual authority. This indicates that, while authority setting is individually performed for each account of the account type when the account type is individual authority, the individual authority setting is performed according to the role. Conversely, in the example illustrated in FIG. 9 , when the account type is overall management authority or overall authority, each account of the account type has overall authority and therefore does not need to be individually set for authority. Also, in the example illustrated in FIG. 9 , when the account type is input person, each account of the account type is only responsible for input and is therefore not subject to individual authority setting.

[0048] In the account table 901, the roles include "including subsidiaries," "our company only," "role 1," and "role 2." "Including subsidiaries" represents a role that also has authority over groups hierarchically lower than the group to which the account belongs. "Our company only" represents a role that has authority over only the group to which the account belongs. "Role 1" and "Role 2" represent arbitrarily set roles, and are described in detail in FIGS. 10 and 11. Note that in FIG. 9, "including subsidiaries" and "our 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 "our company only" are alternatives, constraints such as alternatives and dependency relationships (e.g., role Y cannot be specified unless role X is specified) may be imposed on the multiple roles that are specified.

[0049] FIG. 10 is a diagram showing an example of the operation flow of the management device 100 according to the first embodiment. The authority 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 described below with reference to FIG. 11. FIG. 11 is a diagram showing an example of an authority role setting screen according to the first embodiment. This 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.

[0050] 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 the information item. The authorized role setting unit 116 may accept a request to register authority items for a role and setting of the name of the item through operation of the terminal 200.

[0051] The authorized role setting unit 116 accepts the assignment of authority for each role of each item for each group (S302). In FIG. 11 , groups A, B, C, ..., and F are shown in field 1101, and for each group, field 1103 indicates either "editable," "viewable," or "no authority" 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 operation of terminal 200, and sets the authority as shown in FIG. 11. If role 1 is assigned to account 0009 belonging to group F as shown in FIG. 9 , account 0009 does not have authority for the item indicated by role 1 when operating terminal 200, and therefore cannot edit or display the item. This will be described in detail below with reference to FIG. 12.

[0052] 12 is a diagram showing an example of the 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).

[0053] 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 time 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 "my company only." The display control unit 118 displays information about the group according to the authority of the role (S404). For example, in the case of the above-mentioned role of "my 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.

[0054] 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 accepted the display request and displays information about the group according to the authority of the role, thereby enabling flexible control over each account.

[0055] FIG. 13 is a diagram showing an example of the 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 hierarchy from the group linked to the account operating the terminal 200, and displays information about groups at or below that hierarchy 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 the designation of the group for which information is to be input, a field 1402 for accepting designation of whether or not to include a hierarchy (subordinate) below that group, a field 1403 for accepting designation of narrowing down the search if a hierarchy below that group is to be included, and a field 1404 for displaying the designated information.

[0056] 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.

[0057] 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 the determined hierarchical level on the display device of the terminal 200 (S502). The hierarchical level determination may be performed 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 code of group C is " / 1 / 3 / ", and therefore the account is identified as hierarchical level 2, as also shown in Fig. 4.

[0058] The display control unit 118 then displays information about groups at or below that hierarchical level on the display device of the terminal 200. For example, if 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 Figures 4 and 5. For example, in Figure 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 the hierarchical level below group C in addition to group C. 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.

[0059] The display control unit 118 may also accept a specification to narrow down the targets for information confirmation from 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 ), which are hierarchical levels below group C. If "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 its subordinate groups F to J in field 1404 in "Narrowing down" in field 1403. If the narrowed down target information is information on multiple groups, the information may be displayed side by side, summed up, or the like. This allows for more flexible and easy-to-understand display of information on groups at or below the hierarchical level.

[0060] 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. Below, explanations of the second embodiment that are the same as those of the first embodiment will be omitted.

[0061] 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.

[0062] 16 shows an example of functional blocks of a 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 authorization role setting unit 116, a base setting unit 1512, an input management unit 1514, an input reception unit 1516, and a display control unit 118.

[0063] FIG. 17 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. As described 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 described 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.

[0064] The base setting unit 1512 accepts the registration of a base (S600). Base registration is performed, for example, by a base creation operation using the terminal 200. Specifically, the base setting unit 1512 accepts the registration of a base by, for example, 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 a group is a company, a 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.

[0065] 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, a person in charge of input, basic information, questionnaire information, electricity plan, power source information, gas plan, facility and 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.

[0066] 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 account type (S700) and associates a selected account from the candidate accounts with a specified location as an input person (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 an 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.

[0067] The account setting unit 114 displays candidate accounts from the group according to account type (S700). For example, in the candidate list field 2003 of FIG. 20, group C is specified in the designation field 2004. Assume that the accounts belonging to group C are listed in the account table 901 of FIG. 9. 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." 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 of an account code, name, email address, or other account-specific items for identifying the candidate account.

[0068] The account setting unit 114 associates a selected account from the candidate accounts with the specified base as the input person (S702). For example, FIG. 20 shows that accounts 0005 and 0006, selected from candidate accounts 0005 to 0007, are associated as input persons with base c2, the base c2 designated as the addition destination base. The account setting unit 114 may display a list of candidate bases to which the terminal 200 is added, limited based on at least one of the account hierarchy and account type of the account operating the terminal 200. Selection of an input person 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 base as the input person. This allows for easy association and setting of input persons with each base.

[0069] 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 group C's base c2, 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 set to input information items for "kerosene" and "diesel" under the "fuel use" major category, prompting the user 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 further accept the specification of additional input information items. Although not shown in FIG. 22 , a field indicating whether field 2206 is set to "inputting" or "already input" 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 that information classification is still being input or has already been input.

[0070] 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, but 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 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." However, the input management unit 1514 may accept an instruction to change the type to "emissions" and the unit to "tCO2e" via operation of 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.

[0071] FIG. 23 illustrates 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 station (S900), displays the input information items specified for the base station (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 of 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 of 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 of 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 the input management unit 1514 may not accept designation of input information items. In this case, the designation item "(Add)" for example, which is on the setting screen of FIG. 22, is not displayed on the information input screen.

[0072] 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 the 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.

[0073] The input accepting unit 1516 displays the input information items specified for the base (S902). The operation of specifying the input information items for the base has been described with reference to Figures 21 and 22. The input accepting unit 1516 then 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 Figure 22 that change depending on, for example, the account type.

[0074] 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 gas" 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 input person. 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 a 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 a 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 received 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 received, 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.

[0075] 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 the designation of a base according to the authority of the role, and displays input field information related to the base (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.

[0076] 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 a terminal 200 operated by an account with account code 0003 in the account table 901 of FIG. 9 and determines from the account table 901 that the role associated with the account is "including subsidiaries," the account has authority to handle information of not only its own group but also 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 the 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 received 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 because, for example, 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 in the parent group can set the input information items for that base.

[0077] 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 a field 2601 for accepting the specification of the group for which information is to be entered, a field 2602 for accepting the specification of whether to include lower levels (subordinates) of the group, a field 2603 for accepting the specification of narrowing down the bases if lower levels of the group are to be included, a field 2604 for accepting the specification of the fiscal year, a field 2605 indicating whether the display period is yearly or monthly, a field 2605 indicating various information classifications, and a field 2606 showing a confirmation screen for each piece of information depending on the content specified in fields 2601 to 2605.

[0078] The display control unit 118 determines the hierarchical level from the group associated with the account operating the terminal 200 that 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 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 bases linked to group C and its subordinate groups F to J to "c1, c3, f1" in "Narrowing down bases" in field 2603. Each piece of information shown in field 2607 is displayed as the sum of the values ​​entered for bases c1, c3, and f1. This makes it possible to display information about bases linked to groups at lower levels in a more flexible and easy-to-understand manner.

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

[0080] In another embodiment, the management device 100 or 1500 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 waste amount from the usage amount, the waste amount may be derived by multiplying each usage amount by a basic unit (conversion data) indicating the waste amount per unit of usage. In addition, the derivation unit may derive each amount from each usage amount 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, harmful chemicals, ozone layer depletion, acidification, noise, global warming, photochemical oxidants, eutrophication, resource consumption, ecotoxicity, fuel consumption, land use, and other impact areas, human health based on damage assessment, social estimates, biodiversity, primary production, and other protected targets.

[0081] The usage may include fuel consumption for the operation of the facility. Fuels may include solid fuels (coking 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 and 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). The activity involved in the production of the product related to the usage may consume at least one of heat and steam.

[0082] 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.

[0083] The information managed by the management device 100 or 1500 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 product manufacturing (including all processes related to product manufacturing, including not only the assembly of the product itself but also the assembly of product components and the processing of materials (including raw materials) that make up each component). Disaster risk measures may indicate whether measures are being taken to prevent a disaster from affecting product manufacturing. In addition to the above, the data managed by the management device 100 may also include any other information that the company desires to request from its affiliated companies. For example, the data may include various damage calculation-based environmental impact assessments; environmental data on product carbon footprints related to climate change; natural resource data on biodiversity, land use, and raw material procurement; waste disposal data on hazardous materials, waste management, packaging materials, and home appliances; environmentally regulated substances on chemical substances, air pollutants, water quality, and soil contamination; and other environmental data on technology, energy, noise, vibration, odors, etc. Furthermore, with regard to society, data may be included regarding human resources, such as human rights (child labor, forced labor, working hours, wages, labor rights, discrimination, etc.), labor management and health and safety, human capital, safety and quality regarding product and service safety, safety of each material, privacy and data security, relations with the local community, diversity, equity, and inclusion, well-being and engagement, compliance and ethics, and other social data. With regard to governance, data may be included regarding ethics and compliance with laws and regulations regarding corporate behavior, anti-corruption, risk management and disaster prevention, tax transparency, and other governance-related data. Data regarding due diligence for each of the above items may also be included. The designation or input of the input information items regarding these pieces of information may be displayed in fields 2206 and 2607 in the category indicated as "Questionnaire" in field 2205 of FIG. 22 and field 2606 of FIG. 26, and each designation or input may be accepted.

[0084] In another embodiment, the management device 100 or 1500 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 are required, 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.

[0085] As another embodiment, among the various information categories shown in field 2205 in FIG. 22 , field 2206 for Scope 2 (GHG Protocol indirect emissions related to electricity, heat, hot water, steam, cold heat, and chilled water) 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 procurement amount of certificates and credits applicable to Scope 2. Furthermore, when power generation and supply are performed 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 of the dummy group is then registered along with the emission intensity of the power 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.

[0086] In another embodiment, the management device 100 or 1500 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 storage 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 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 (assuming that the amount of wastewater is equal to the amount of water intake) may be set as the measurement type. If the measurement type is specified 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.

[0087] 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 the like various pieces of information. The estimation unit may also perform machine learning (deep learning, reinforcement learning, and the like) based on the data stored in the memory unit 130 to perform various estimations, classifications, predictions, and the like. 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 power 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, the machine learning model or algorithm solves classification problems and may include, for example, logistic regression (including ridge regularization and lasso regularization), random forest, support vector machine, neural network (including multilayer perceptron), etc. Furthermore, the accuracy of these classification predictions may be evaluated using one or more of the following: mean square error of estimated conditional probability, AUC (Area Under the Curve) quantified as the area under the ROC (Receiver Operating Characteristic) curve, logarithmic loss in the minimization problem of Kullback-Leibler divergence, and calibration plots plotting actual measured values ​​and predicted values. Here, the accuracy of classification predictions of machine learning algorithms or models varies depending on the number of training data and feature quantities (for example, the number of days for acquiring power consumption data used for learning and attribute information added), etc. Therefore, the selection of a learning model may be performed by comparing the evaluation results of classification accuracy of each machine learning algorithm or model under predetermined conditions. In addition, in selecting a learning model, a model with low computational cost required for learning and classification may be prioritized.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.

[0088] 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.

[0089] It should be noted that the order of execution 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.

[0090] 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.

[0091] In one aspect of the present invention, the following management device, management method, and management program are realized. (Item 1) A management device including 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) 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 the parent group of the group. (Item 3) The management device according to Item 1, further including: 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; and an authority role setting unit that accepts registration of authority items for the role and accepts designation of authority for the role for each item for each group. (Item 4) The management device according to Item 3, further including a display control unit that accepts a display request from a terminal, determines a role associated with an account operating the terminal, and displays information about the group in accordance with the authority of the role. (Item 5) The management device according to item 1, further comprising 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 at or below that hierarchy on a display device of the terminal. (Item 6) A management method comprising a step in which a group setting unit receives registration of a group, receives designation of a parent group of the group, and generates a hierarchy code for the group in accordance with the designation of the parent group using the hierarchy code of the parent group. (Item 7) A management program that causes a computer to execute the management method according to item 6.

[0092] In other aspects 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 the registration of a group; an account setting unit that accepts the registration of an account and accepts designation of a group and an account type for the account; and a base setting unit that accepts the registration of a base and accepts designation of master information including the group for each base. (Item 2) The management device according to Item 1, wherein the account setting unit displays candidate accounts from the group according to the account type, and associates an account selected from the candidate accounts with the designated base as an input person. (Item 3) The management device according to Item 1, further comprising an input management unit that displays common input information items for each base and accepts designation of the input information items for each base. (Item 4) The management device according to Item 3, further comprising an input acceptance unit that accepts a display request from a terminal operated by an input person at a base, displays the input information items designated for the base, accepts input for each input information item from the terminal, executes processing according to each designation, and stores the results of the processing. (Item 5) The management device according to item 3, further comprising a display control unit that receives a display request from a terminal, determines a role associated with an account operating the terminal, accepts a base designation in accordance with the authority of the role, and displays input item information related to the base. (Item 6) The management device according to item 3, further comprising a display control unit that receives a display request from a terminal, determines a hierarchy from a group associated with the account operating the terminal, and displays base information related to groups at or below the hierarchy. (Item 7) A management method comprising: a group setting unit accepting registration of a group; an account setting unit accepting registration of an account and accepting designation of a group and an account type for the account; and a base setting unit accepting registration of a base and accepting designation of master information including the group for each base. (Item 8) A management program that causes a computer to execute the management method according to item 7.

[0093] 10, 15 Management system 50 Network 100, 1500 Management device 110, 1510 Control unit 112 Group setting unit 114 Account setting unit 116 Authorized role setting unit 118 Display control unit 120 Communication unit 130 Storage unit 200 Terminal [a1] 401, 601 Hierarchical number 402, 602 Group name 501, 701 Group table 901 Account table 1101 Group name 1102 Role 1103 Authorization 1401 Group 1402 Includes subordinates 1403 Narrowing down 1404 Field showing information 1512 Base setting unit 1514 Input management unit 1516 Input reception unit 1801 Base table 2001 List of bases to add 2002 Input person in charge 2003 Candidate list 2004 Designated field 2005 Field indicating candidate account 2201 Group 2202 Base 2203 Fiscal year 2204 Year / month 2205 Field indicating classification 2206 Field indicating input information item to be set 2601 Group 2602 Include subordinates 2603 Narrow down bases 2604 Fiscal year 2605 Year / month 2206 Field indicating classification 2207 Field indicating input information item to be checked

Claims

1. A management device having a group setting unit that accepts the 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.

2. The management device according to claim 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 the group's parent group.

3. The management device of claim 1, further comprising: 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; and an authority role setting unit that accepts registration of authority items for the role, and accepts designation of authority for the role for each item for each group.

4. The management device according to claim 3, further comprising a display control unit that receives a display request from a terminal, determines a role associated with an account operating the terminal, and displays information about the group according to the authority of the role.

5. The management device of claim 1, further comprising 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.

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.

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

8. A management device comprising: a group setting unit that accepts the registration of a group; an account setting unit that accepts the registration of an account and accepts the designation of a group and account type for the account; and a base setting unit that accepts the registration of a base and accepts the designation of master information including the group for each base.

9. The management device according to claim 8, wherein the account setting unit displays candidate accounts from the group according to the account type, and links a selected account from the candidate accounts to a specified base as the person in charge of inputting data.

10. The management device according to claim 8, further comprising an input management section that displays common input information items for each base and receives designation of input information items for each base.

11. The management device according to claim 10, further comprising an input reception unit that receives a display request from a terminal operated by a person in charge of inputting data at a base station, displays input information items specified for the base station, receives input for each item of input information from the terminal, executes processing in accordance with each specification, and stores results in accordance with the processing.

12. The management device of claim 10, further comprising 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 relating to the location.

13. The management device according to claim 10, further comprising 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.

14. A management method comprising the steps of: a group setting unit accepting registration of a group; an account setting unit accepting registration of an account and accepting designation of a group and account type for the account; and a base setting unit accepting registration of a base and accepting designation of master information including the group for each base.

15. A management program for causing a computer to execute the management method according to claim 14.

Images