Management device, management method, and management program

Abstract

To provide a management device, a management method, and a management program for accepting group registration.SOLUTION: In a management system in which a management device communicates with a plurality of terminals via a network, a management device 100 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 a hierarchical code of the parent group.SELECTED DRAWING: Figure 2

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] JP2019-219847 Summary of the Invention [Means for solving the problem]

[0004] A management device according to one embodiment 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.

[0005] In the above 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 a parent group of the group.

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

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

[0008] 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 below that hierarchy on a display device of the terminal.

[0009] A management method according to one embodiment 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.

[0010] A management program according to an aspect of the present invention causes a computer to execute the above-described management method.

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

[0012] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a management system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a functional block of a management device according to the first embodiment. [Diagram 3] FIG. 4 is a diagram illustrating an example of an operation flow of a 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. [Diagram 5] FIG. 4 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. 4 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 a management device according to the first embodiment. [Figure 9]FIG. 4 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 a management device according to the first embodiment. [Figure 11] FIG. 4 is a diagram showing an example of an authority role setting screen according to the first embodiment; [Figure 12] FIG. 4 is a diagram illustrating an example of an operation flow of a management device according to the first embodiment. [Figure 13] FIG. 4 is a diagram illustrating an example of an operation flow of a management device according to the first embodiment. [Figure 14] FIG. 11 is a diagram showing an example of an information confirmation screen according to the first embodiment. [Figure 15] FIG. 11 is a diagram illustrating an example of an overall configuration of a management system according to a second embodiment. [Figure 16] FIG. 11 is a diagram illustrating an example of a functional block of a management device according to a second embodiment. [Figure 17] FIG. 11 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. 11 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. 11 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. [Diagram 23] FIG. 11 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Figure 24] FIG. 11 is a diagram illustrating an example of an operation flow of a management device according to the second embodiment. [Diagram 25] FIG. 11 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

[0016] 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 10 may directly accept operations, or may accept operations via 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.

[0017] FIG. 2 shows an example of a functional block of the management device 100. The management device 100 may be configured as a computer as hardware. The computer may execute the management method described in the present specification by 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, a microcontroller such as an MCU, or the like. The communication unit 120 manages communication between each component in the management device 100. In addition, the communication unit 120 communicates with an external computer such as a terminal 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 SDD, or other storage media. The storage unit 130 may store various information as data in tables, and store a database configured by associating each table.

[0018] 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 related to the group in the storage unit 130. The account setting unit 114 accepts the registration of an account and stores information related to 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 related to 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.

[0019] 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 of the group in accordance with the designation of the parent group by using the hierarchical code of the parent group (S104).

[0020] The group setting unit 112 accepts the registration of a group (S100). The registration of a group is performed, for example, by an operation of creating 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 associated therewith, using an operation using the terminal 200. The group may be a company or an internal group of a company (headquarters, department, etc.), or may be various organizations, national or local public organizations, or any other organization.

[0021] Here, the relationship between groups and hierarchies will be described with reference to Fig. 4 using a specific example. Fig. 4 is a diagram showing an example of the hierarchical relationship of 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 are not limited to these, and may include more hierarchies such as hierarchy 5, hierarchical 6, hierarchical 7, hierarchical 8, etc.) and group names 402 indicating groups in each hierarchical level (group A, group B, group C, ... group J are shown, but are not limited to these, and may include more groups such as group K, group L, etc.). For example, the hierarchies may be relationships between companies such as a holding company, a head office, a subsidiary, a sub-subsidiary, an affiliated company, an overseas office, etc., may include groups within a company, or may show connections between any other organizations.

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

[0023] 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 table format in the storage unit 130. Furthermore, the display control unit 118 may cause a display device to display part or all of the group table 501 shown in Fig. 5. Below, the same diagrams relating to tables are used, and the description thereof will be omitted.

[0024] The group table 501 has a group code, a group name, a parent group name, and a hierarchical code, but is not limited to these, and may have other information such as creation date, deletion date, location, detailed attributes, etc. The group code is a code given to each group and constitutes a unique ID. In FIG. 5, numbers 1, 2, 3, ..., 10 are assigned, but this is not limited to these, and any code that does not overlap may be assigned. The group name indicates the name of each group. In FIG. 5, A, B, C, ..., J, which are the same as the groups shown in FIG. 4, are shown. As described with respect to FIG. 4, the parent group indicates a group in a higher hierarchical level linked to the group. For example, FIG. 5 shows that group A has no parent group, and therefore group A is in hierarchical level 1. In addition, the parent group of group B is A, and the parent group of group C is also A, and therefore group B and group C are both in hierarchical level 2 linked to group A (hierarchical level 1).

[0025] The hierarchical code is a code given to each group, which constitutes a unique ID and at the same time indicates a hierarchy. The group setting unit 112 generates the hierarchical code of a group by placing the group code of the group after the hierarchical code of the parent group of the group. However, for a group without a parent group (i.e., a group in hierarchy 1), the hierarchical code is generated using the group code of the group. For example, in FIG. 5, the hierarchical code of group A (without a parent group) in hierarchy 1 is " / 1 / " using the group code "1" of the group A. The hierarchical code of group B (parent group is group A) in hierarchy 2 is " / 1 / 2 / " which is the hierarchical code of the parent group " / 1 / " followed by the group code "2" of the group B. Similarly, the hierarchical code of group C (parent group is group A) in hierarchy 2 is " / 1 / 3 / " which is the hierarchical code of the parent group " / 1 / " followed by the group code "3" of the group C. Additionally, the hierarchical code for group D (whose 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 the hierarchies of many groups can be expressed in a unified manner.

[0026] 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 is changed. Fig. 6 shows hierarchical numbers 601 indicating hierarchical levels (hierarchical levels 1, 2, 3, 4, and 5 are shown, but are not limited to these, and may include more hierarchical levels such as hierarchical levels 6, 7, 8, 9, etc.) and group names 602 indicating groups in each hierarchical level (group A, group B, group C,...group J are shown, but are not limited to these, and may include more groups such as group K, group L, etc.). Below, explanations similar to those in Fig. 4 will be omitted.

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

[0028] 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 group table 501 shown in Fig. 5 has been changed. Fig. 7 also shows in a table the relationship between groups and hierarchies shown in Fig. 6. For reference, Fig. 7 shows the hierarchical code included in group table 501 in Fig. 5 as "hierarchical code before change". Below, explanations similar to those in Fig. 5 will be omitted.

[0029] Here, an example of the operation of the group setting unit 112 that changes the relationship between groups and hierarchies shown in Figs. 4 and 5 to the relationship shown in Figs. 6 and 7 will be described. First, the group G, which was in hierarchical level 3 in Figs. 4 and 5, becomes hierarchical level 1 by canceling the designation of the group C, which was a parent group (for example, by designating the parent group as none). At this time, the group setting unit 112 deletes " / 1 / 3" that is placed before the group code "7" of the group G from the hierarchical code " / 1 / 3 / 7 / " of the group G by canceling the designation of the parent group, and updates the hierarchical code of the group G to " / 7 / ". Although not shown in Figs. 4 and 5, if there is a group in a lower hierarchical level linked to the group G, the hierarchical level of the 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 the groups in the lower hierarchical levels may also be raised by two levels.

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

[0031] 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 of the group in response to the designation of the parent group using the hierarchical code of the parent group (S104 in FIG. 3), thereby easily changing the relationship between the groups and hierarchies shown in FIG. 4 and FIG. 5 to the relationship shown in FIG. 6 and FIG. 7. This makes it possible to easily change and manage the hierarchical relationships in a unified manner by simply designating the parent group of each group, even if the relationships between many groups are complicated. In addition, although not shown in FIG. 4 to FIG. 7, a hierarchical change flag and a change date and time may be included in the group table or a separately set hierarchical table for a change in the hierarchical level. Then, the group setting unit 112 may designate the change flag for a hierarchical level that has been changed, such as added, replaced, or abolished, at the time of the change, and record the change date and time in the table. This makes it possible to keep a history of past changes to the hierarchical levels.

[0032] Although an example in which there is one group in hierarchical level 1 is shown in FIG. 4 to FIG. 7, the present invention is not limited to this, and there may be multiple groups in hierarchical level 1 .

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

[0034] The account setting unit 114 accepts the registration of an account (S200). Here, the account table 901 in Fig. 9 has an account code, an account type, a group name, and a 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 piece of information described above for the row. Note that the information held in the account table is not limited to the above, and may have other information such as the account creation date, deletion date, name, email address, detailed affiliation, etc.

[0035] Here, in the account table 901 in Fig. 9, the account code is a code assigned to each account and constitutes a unique ID. In Fig. 9, 0001, 0002, 0003...0012 are assigned, but this is not limited to this and any non-duplicate 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 non-duplicate code when registering an account. The numbering may be performed 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 and used.

[0036] 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 may be automatically designated for a specific account type. For example, when 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.

[0037] Here, in the account table 901 in 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 input 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 input person will be described in detail using Figs. 10 and 11. The account types are not limited to these and may include other arbitrary 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.

[0038] Also, in the account table 901 in 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. Information about the group may be stored in a group table such as the group table 501 in Fig. 5 and the group table 701 in Fig. 7, and the account table 901 may refer to 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, an account with an account code 0003 is associated with group C, and information about group C may be stored in the group table 501 in Fig. 5 or the group table 701 in Fig. 7, and the account table 901 may refer to the group table 501 in Fig. 5 or the group table 701 in Fig. 7 using the group code of group C (not shown in Fig. 9) as a foreign key.

[0039] In the account table 901 in Fig. 9, the group names of the account codes 0001 and 0002 are blank, but accounts that do not require management by a group do not need to be associated with a group. For example, the account codes 0001 and 0002 are actually accounts that belong to group A in hierarchical level 1 in Fig. 4 and Fig. 5, but are not associated with group A because management according to the group to which they belong is not required, such as the account type being an overall management authority that allows operations on all management devices 100, or the account type being an overall authority that allows operations on all groups. In other embodiments, the association of the account table with the group table may be essential, and in that case, for example, in Fig. 9, the display of the group name A to which the account codes 0001 and 0002 belong may be omitted because the account type is overall management authority or overall authority.

[0040] The account setting unit 114 accepts the designation of the role according to the account type (S204). Here, in the account table 901 in FIG. 9, the role indicates the role of each account, and each account is controlled 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 the role can be set when the account type is individual authority. This shows that when the account type is individual authority, authority is set individually for each account of the 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 total management authority or total authority, each account of the account type has total authority, so there is no need to set authority individually. Also, in the example shown in FIG. 9, when the account type is input person, each account of the account type is only in charge of input, so it is not subject to individual authority setting.

[0041] In the account table 901, the roles include "including subsidiaries", "my company only", "role 1" and "role 2". "including subsidiaries" represents a role that has authority over groups in a hierarchy below 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 will be described in detail in FIG. 10 and FIG. 11. Note that in FIG. 9, "including subsidiaries" and "my company only" are pre-set roles, but the names and contents of the roles may be editable. Furthermore, the roles in the account table are not limited to the above, and other arbitrary roles may be included. Although FIG. 9 shows an example in which one role is specified for each account, multiple roles may be set for each account. However, for example, in FIG. 9, "including subsidiaries" and "my company only" are alternatives, and restrictions such as alternatives, dependency, and other conditions (for example, role Y cannot be specified unless role X is specified) may be set for the multiple roles to be specified.

[0042] Fig. 10 is a diagram showing an example of an 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 of 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. The setting screen has a field 1101 indicating a group name, a field 1102 indicating authority items for the role, and a field 1103 indicating designation of authority for each item of the role for each group.

[0043] The authority 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 (greenhouse gas emission amount, activity amount of activity involving greenhouse gas emission, water usage amount, etc.) may be used as an item indicating authority for the information item. The authority role setting unit 116 may accept a registration request for authority items for a role and setting of the name of the item by operation of the terminal 200.

[0044] The authorized role setting unit 116 accepts the designation of the authority for the role of each item for each group (S302). Here, in FIG. 11, groups A, B, C,..., F are shown in a field 1101, and for each group, either "editable", "displayable" or "no authority" is shown in a field 1103 for each of the items role 1, role 2 and role 3 shown in a field 1102. For example, the authorized role setting unit 116 accepts a designation of "no authority" for role 1 for group F by the operation of the terminal 200, and sets the authority as shown in FIG. 11. Then, as shown in FIG. 9, when role 1 is designated for the account 0009 belonging to the group F, the account 0009 does not have the authority for the item shown in role 1 in the operation of the terminal 200, so the item cannot be edited and the item is not displayed. Hereinafter, a detailed description will be given with reference to FIG. 12.

[0045] 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 that operates the terminal 200 (S402), and displays information about the group according to the authority of the role (S404).

[0046] 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 that operates the terminal 200, or may be received at any timing after the authentication is completed. The display control unit 118 determines a role associated with the account that operates the terminal 200 (S402). For example, if the account that operates the terminal 200 is an account indicated as account code 0004 in the account table 901 of FIG. 9, the role is determined to be "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 role of "my company only" described above, the account has the authority to handle only information about the company, so the display control unit 118 displays only information about the group C associated with the account on the display unit of the terminal 200 operated by the account code 0004.

[0047] Similarly, for example, if the account operating the terminal 200 is an account indicated as account code 0011 in the account table 901 in Fig. 9, the display control unit 118 determines that the role is "role 2". Then, since role 2 has the authority of "editable" for the items of role 2 as shown in Fig. 11, the display control unit 118 displays the items of role 2 in an editable manner 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 related to the group according to the authority of the role, thereby enabling flexible control over each account.

[0048] 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 accepts a display request from the terminal 200 (S500), determines a hierarchy from a group linked to an account that operates the terminal 200, and displays information about groups below the 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 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 hierarchy (subordinate) of the group, a field 1403 for accepting designation of narrowing down when a lower hierarchy of the group is to be included, and a field 1404 for displaying the designated information.

[0049] The display control unit 118 accepts a display request from the terminal 200 (S500). The display request from the terminal 200 may be accepted simultaneously with authentication of an account that operates the terminal 200, or may be accepted at any timing after the authentication is completed. In particular, the display request from the terminal 200 may be accepted at the timing of information input in response to an information input request made by an account that operates one terminal 200 to an account that operates another terminal 200.

[0050] 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 below the 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 Fig. 7, and the account table 901 in Fig. 9. For example, if the account operating the terminal 200 has the 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 group is identified as hierarchical level 2, as shown in Fig. 4.

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

[0052] The display control unit 118 may also accept a designation to narrow down the targets for information confirmation among the groups below the hierarchical level, and display information on the narrowed down targets. For example, in FIG. 14, the display control unit 118 accepts a designation in field 1402 as to whether to narrow down the targets for information confirmation to include groups F to J ("under" in FIG. 14) which are hierarchical levels below group C. When "including under" is designated in the field 1402 (a check mark is displayed in FIG. 14), the display control unit 118 may display information on targets narrowed down to one or more of group C and its undergroups F to J in "narrow down" in field 1403 in field 1404. When the information on the narrowed down targets is information on a plurality of groups, each piece of information may be displayed side by side, added together, or the like. This allows information on the groups below the hierarchical level to be displayed more flexibly and easily understood.

[0053] Next, a management device 1500 according to a second embodiment will be described. The management device 1500 according to the second embodiment realizes information management that allows an information collector to collect more information more accurately and an information provider to provide information more easily, in addition to efficient group management. In the following, the same description of the second embodiment as that of the first embodiment will be omitted.

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

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

[0056] FIG. 17 is a diagram showing an example of an 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 a 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 in association with the group name and the base name.

[0057] The base setting unit 1512 accepts the registration of a base (S600). The base is registered by, for example, an operation of creating a base using the terminal 200. Specifically, for example, the base setting unit 1512 accepts the registration of a base by creating a base name by an operation using the terminal 200 and assigning a base code accordingly. A base may be a company or an internal group (headquarters, department, etc.) of a company, various organizations, national or local public organizations, 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, a factory, a branch office, an overseas local corporation, or any other organization different from the group. Also, as shown in FIG. 18, a plurality of bases may be linked to one group. For example, in FIG. 18, two bases a1 and a2 are linked to group A.

[0058] 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 have a base code for identifying the base, a group code, an account code, a person in charge of input, basic information, questionnaire information, an electricity plan, a power source information, a gas plan, facility equipment information, a business, equipment, a facility classification, a management item, an activity amount code, and other related master information in addition to the group name. The base setting unit 1512 accepts the designation of each piece of the master information for each base.

[0059] FIG. 19 is a diagram showing an example of an operation 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 links a selected account from the candidate accounts to a specified base 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 showing a list of bases to which the user is to add the account, a field 2002 showing an input person to be linked to the list of bases to which the user is to add the account, a candidate list field 2003 showing the candidate accounts to be linked, a designation field 2004 included in the candidate list field 2003 and used to narrow down the candidate accounts, and a field 2005 included in the candidate list field 2003 and showing the candidate accounts narrowed down by the designation field 2004.

[0060] 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 the group C are shown in the account table 901 of FIG. 9. Then, there are five accounts belonging to the group C, with account codes 0003 to 0007. The account setting unit 114 determines the account codes 0005 to 0007, whose account type is specified as "input person" from the group C, as candidate accounts. Then, in the field 2005, only the account code 0007, which is not yet shown in the field 2002 as the input person, is shown as "C 0007". Although omitted in FIG. 20, the designation field 2004 may display the candidate accounts by other designation methods. For example, the designation field 2004 may accept designation by an account code, a name, an email address, or other items for identifying the account to identify the candidate account.

[0061] The account setting unit 114 associates the selected account from among the candidate accounts with the designated base as the person in charge of input (S702). For example, FIG. 20 shows that the accounts 0005 and 0006 selected from the candidate accounts 0005 to 0007 are associated with the base c2 designated as the addition destination base as the person in charge of input. The account setting unit 114 may display a limited list of candidates for the addition destination base according to at least one of the hierarchy and the account type of the account that operates the terminal 200. Selection of the person in charge of input from among the candidate accounts may be performed by dragging and dropping the candidate account shown in the field 2005 into the field 2002. According to the second embodiment, the candidate accounts are displayed according to the account type from the group, and the account selected from the candidate accounts is associated with the designated base as the person in charge of input, so that the person in charge of input can be easily associated and set with each base.

[0062] FIG. 21 is a diagram showing an example of an operation flow of the management device 1500 according to the second embodiment. The input management unit 1514 displays common input information items for each base (S800) and accepts the designation of input information items for each base (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 group name to be set, a field 2202 indicating the base name to be set, a field 2203 indicating the year to be set, a field 2204 indicating the type of yearly or monthly display period to be set, 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 the fields 2201 to 2205. For example, in FIG. 22, the setting target is the base c2 of 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 in the GHG protocol). According to the content, the input information items of "kerosene" and "diesel" are set in the major item "fuel use" in the field 2206, and the value for the amount of use in 2023 in kl, the reason for the difference, comments, and attachments are set to be input. In addition, as "(add)" is shown at the bottom of the major item "fuel use", the input management unit 1514 can further receive the specification of the addition of input information items. Although not shown in FIG. 22, a field indicating whether the setting of the field 2206 is "inputting" or "already input" may be provided for each of the various information classifications shown in the field 2205. This allows even a person other than the person in charge of input to easily check whether the field 2206 of the information classification is still being input or has already been input.

[0063] The input management unit 1514 displays common input information items for each base (S800). For example, in FIG. 22, the input information items set for the base c2 are shown in the field 2206, and the input information items are displayed based on the input information items common to other bases. The common input information items are stored as templates in the storage unit 130, and are displayed for each base by the input management unit 1514. Then, the input management unit 1514 accepts the designation of the input information items for each base (S802). For example, in FIG. 22, the type of the input information item "light oil" is "amount of use" and the unit is "kl", but the input management unit 1514 accepts 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 with the changed type and unit for the base c2. By displaying common input information items at each base in this way, information can be collected from the bases in a unified manner, while certain items can be customized by accepting designation of input information items for each base, and information available at each base can be collected. Note that acceptance of designation of input information items for each base 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 makes it possible to restrict control over input information items to accounts with specific authority and maintain uniformity in information collection.

[0064] FIG. 23 is a diagram showing an example of an operation flow of the management device 1500 according to the second embodiment. The input reception unit 1516 receives 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), receives input for each item of input information from the terminal 200, executes processing according to each designation, and saves the results according to the processing (S902). Although the information input screen shown in each operation is not shown, each operation will be described with reference to a part of the setting screen in FIG. 22 that is common to the information input screen. Note that the part of the information input screen that is common to the setting screen in FIG. 22 may change depending on the account type. For example, when the account type is the overall management authority or the 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 designation of the input information items while the input reception 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 the 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 only input for input information items that have already been set, only for the linked base, and without the input management unit 1514 accepting the designation of input information items. In this case, the information input screen does not display, for example, a designation item such as "(add)" in the setting screen of FIG. 22.

[0065] The input reception 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 is made to the person in charge of inputting data from an account that has performed an operation to link the person in charge of inputting data to the base.

[0066] The input receiving unit 1516 displays the input information items designated for the location (S902). The operation of designating 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 designated input information items. As described above, the information input screen displayed here may also have parts common to the setting screen of Fig. 22 that change depending on, for example, the account type.

[0067] The input reception unit 1516 receives input for each item of input information from the terminal 200, executes processing according to each designation, and saves the results according to 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 reception unit 1516 may receive input of the value "xyy" (originally input as a numerical value, but described as a character string for convenience of explanation) for the item in 2023 from the terminal 200 operated by an account linked to the base c2 as the person in charge of input. Then, the input reception unit 1516 executes processing according to each designation. For example, for "CO2 (non-energy origin)", if a value exceeding a predetermined threshold or range from the value "xyx" for fiscal year 2022 is input to the value for fiscal year 2023, the input management unit 1514 may accept a designation that the input of the reason for the difference is mandatory, and if the value "xyy" for fiscal year 2023 exceeds a predetermined threshold or value from the value "xyx" for fiscal year 2022, the input acceptance unit 1516 may execute a display process indicating that the input of the reason for the difference is mandatory in accordance with the designation. In addition, the input acceptance unit 1516 may store a result corresponding to the process. For example, in accordance with a display process indicating that the input of the reason for the difference is mandatory, the input acceptance unit 1516 may display an error display in the item for the reason for the difference if the input of the reason for the difference is not accepted and store the result in the storage unit 130, or may store the value "xyy" for fiscal year 2023 and the reason for the difference in the storage unit 130 if the input to the item for the reason for the difference is accepted. This allows the information to be collected from the person in charge of input to be collected more precisely and accurately.

[0068] Fig. 24 is a diagram showing an example of an 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 that operates the terminal (S1002), receives a location designation according to the authority of the role, and displays input item information related to the location (S1004). Below, description of the contents that overlap with the description of an example of the operation flow of the management device 100 according to the first embodiment using Fig. 12 will be omitted.

[0069] The display control unit 118 accepts the designation of a base according to the authority of the role, and displays input item information related to the base (S1004). For example, when 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 the role associated with the account as "including subsidiaries" from the account table 901, the account has authority to handle information of its own group as well as groups at a lower level, so that the display control unit 118 accepts designation of a base as a display target from bases associated with group C and groups F to J at a lower level as shown in Figs. 4 and 5 according to the authority of the role. Then, the display control unit 118 displays the input information items related to the base for which the designation was accepted on the 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 location and displays the input information items related to that location according to the authority of that role. This allows for flexible control over each account, while allowing for more appropriate information collection by allowing, 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 of the parent group to set the input information items for that location.

[0070] Fig. 25 is a diagram showing an example of an operation flow of the management device 1500 according to the second embodiment. The display control unit 118 accepts a display request from a terminal (S1100), determines a hierarchical level from a group linked to an account that operates the terminal, and displays information on locations related to the group at or below that hierarchical level (S1102). Hereinafter, 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 designation of the group for which information is to be entered, a field 2602 for accepting designation of whether or not to include the lower levels (subordinates) of the group, a field 2603 for accepting designation of narrowing down the locations if the lower levels of the group are to be included, a field 2604 for accepting designation 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 contents specified in fields 2601 to 2605.

[0071] The display control unit 118 determines the hierarchical level from the group associated with the account that operates the terminal 200 that has received the display request, and displays information on locations related to the group at or below the hierarchical level (S1102). Here, when the "information on locations related to the group at or below the hierarchical level" is determined to be group C, hierarchical level 2 for the terminal 200 operated by the account with the account code 0003, the display control unit 118 displays information on locations c1 to c3, f1, and f2 associated with groups F to J at or below the hierarchical level 2 of the group C on the display device of the terminal 200, as shown in Figs. 4, 5, and 18. For example, in Fig. 26, the group C associated with the account code 0003 is shown in the field 2601. Here, the display control unit 118 may receive designation from one or more of the groups F to J in the lower hierarchical level in addition to the group C in the field 2601. 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) which are lower hierarchical levels of group C, and has narrowed down the locations linked to group C and its subordinate groups F to J to "c1, c3, f1" in "Location narrowing" in field 2603. Each piece of information shown in field 2607 is displayed as the sum of the values ​​input for the locations c1, c3, and f1. This makes it possible to display information on locations linked to groups lower in the hierarchy in a more flexible and easy-to-understand manner.

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

[0073] As another embodiment, the management device 100 or 1500 may include a derivation unit. The derivation unit may derive the greenhouse gas emission amount by multiplying the usage amount of at least one of electricity, water, oil, and gas by the conversion data stored in the memory unit 130. In this case, the greenhouse gas emission amount is derived by multiplying each usage amount by a basic unit (conversion data) indicating the greenhouse gas emission amount per unit of each usage amount. In addition, when deriving the waste amount from the above 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 each usage amount. 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, such as by-products, the amount of substances such as 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, as conversion data.

[0074] The above usage may include the consumption of fuels by the operation of the equipment. The fuels may include solid fuels (coking coal, steam coal, anthracite, coke, petroleum coke, briquettes or charcoal briquettes, wood, charcoal, and other solid fuels), liquid fuels (coal tar, petroleum asphalt, condensate, crude oil (excluding condensate (NGL)), gasoline, naphtha, jet fuel oil, 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, city gas, and other gaseous fuels). The activity carried out in the manufacture of the product related to the usage may be an activity that consumes at least one of heat and steam.

[0075] 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 on data quality and the information is identified as "primary data" or "secondary data", the identified data). In addition, the same conversion data may be used for all bases in common input information items. This makes it possible to optimally maintain application of the conversion data by adding, correcting, etc. the conversion data in the common input information items, even after a request for information input has been made for each base.

[0076] The information managed by the management device 100 or 1500 may include at least one of greenhouse gas emissions related to production, human rights measures, and disaster risk measures. The human rights measures may indicate, for example, whether measures are 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 of the product itself, but also the assembly of parts that constitute the product, and the processing of materials (including raw materials, etc.) that constitute each part). The disaster risk measures may indicate whether measures are 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 may include anything else that the company wishes to request from related companies to input. For example, data may include various types of damage calculation-type environmental impact assessments, product carbon footprints related to climate change for the environment, biodiversity, land use, and raw material procurement for natural resources, hazardous materials, waste management, packaging materials, and waste such as home appliances for waste disposal, chemical substances contained in the environment, air pollutants, water quality, and soil pollution for environmentally regulated substances, and other data on technology, energy, noise, vibration, and odors related to the environment. In addition, regarding society, the data may include human rights (child labor, forced labor, working hours, wages, labor rights, discrimination, etc.) related to human resources, labor management and health and safety, human capital, safety and quality related to product and service safety, safety of each substance, privacy and data security, relations with the community, diversity, equity and inclusion, well-being and engagement, compliance and ethics, and other data related to society. In addition, regarding governance, the data may include ethics and compliance with laws and regulations regarding corporate behavior, anti-corruption, risk management and disaster countermeasures, tax transparency, and other data related to governance. In addition, data related to due diligence for each of the above items may be included. The designation or input of the input information items related to these information may be shown in field 2206 and field 2607 in the classification indicated as "questionnaire" in field 2205 of FIG. 22 and field 2606 of FIG. 26, and each designation or input may be accepted.

[0077] As 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, items of the environmental information of each base that are required to be collected by a person with overall management authority can be set not to be editable (not editable) for any account type or role. This allows a person with individual authority closer to the site to independently add input information items that are considered necessary for each classification, and allows items related to the reason for difference, whether or not a comment can be input (is required), whether or not an attachment can be attached (is required), threshold settings, and linking to conversion data such as specific basic units to be edited, providing flexibility, while requiring information to be provided for information items that are required by an information collector as described above, thereby enabling flexible and unified information collection.

[0078] As one of other embodiments, the field 2206 in Scope 2 (indirect emissions related to electricity, heat, hot water, steam, cold heat, and cold water of the GHG protocol) among various information classifications shown in the field 2205 in FIG. 22 may include the amount of electricity, heat, hot water, steam, cold heat, and cold water used, the amount of money, and the amount of emissions, as well as the amount of power generated by private power generation, corporate PPA, etc., the amount of surplus power, the amount of power purchased, the amount of power sold, and the amount of other energy sold to the outside. It may also include the amount of certificates and credits procured that can be applied to Scope 2. In addition, when power generation and its supply are performed between groups to be managed, the group setting unit 112 may accept the registration of a dummy group for offsetting between the groups. Then, the power plan of the dummy group is registered together with the emission intensity of the group that generates power, the group that receives the supply of power is registered as a tenant, and the amount of supply for the tenant is set. As a result, the GHG emissions of the dummy group become negative, and power generation and its supply between the groups can be managed.

[0079] In another embodiment, the management device 100 or 1500 may include an estimation unit (not shown). In the above-mentioned 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. On the other hand, the estimation unit may execute various estimations based on the data. For example, for the classifications shown as "water" and "waste" in field 2205 of FIG. 22 and field 2606 of FIG. 26, the source data of various estimations is set as the input information items shown in field 2206 and field 2607. For example, in the classification of "water", the measurement type is set as the input information item, and options such as actual measurement value, estimated value (calculated with reference value), and estimated value (discharge amount = water intake amount) may be set as the measurement type. When the measurement type is designated as an estimated value, the display control unit 118 may estimate each amount related to water (water intake amount, wastewater amount, etc.) by referring to reference values ​​based on various input information items required for the estimation (for example, an estimate from the entire building, etc., an estimate from other bases, an estimate using other numbers of people, areas, etc.). Similarly, for "waste", options such as actual measured value and estimated value (calculated with reference value) may be set as the measurement type. The input management unit 1514 may accept, as input information items, conversion data such as basic unit, and reference indicators such as production quantity, number of people produced, production volume, and production cost of each base, and the display control unit 118 may display the reference indicator or a combination of the reference indicator and each input information item (for example, water usage per production volume, etc.). This makes it possible to easily display evaluation indicators between bases.

[0080] The estimation unit may perform statistical processing such as regression analysis on the data stored in the storage unit 130 to perform interpolation, prediction, etc. of each piece of information. The estimation unit may perform machine learning (deep learning, reinforcement learning, etc.) based on the data stored in the storage unit 130 to perform various estimations, classifications, predictions, etc. A learning model may be stored in the storage unit 130, and the learning model may be a learning model generated by machine learning using each piece of data as teacher data. For example, prediction of power demand may be realized by a learning model generated based on information such as weather, temperature, power plant outage information, power supply reserve rate, available capacity of interconnection lines, 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 by a statistical method based on this information. Regarding classification, the machine learning model or algorithm may be used to solve classification problems, and may include, for example, logistic regression (including ridge regularization and lasso regularization), random forest, support vector machine, and neural network (including multilayer perceptron). 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 a calibration plot that plots actual values ​​and predicted values. Here, the accuracy of classification predictions of the machine learning algorithm or model varies depending on the number of teacher data and feature amounts (for example, the number of days for acquiring data on electricity usage used in learning and attribute information to be added), etc. Therefore, the selection of a learning model may be performed by comparing the evaluation results of classification accuracy by 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 perform display control, identification, derivation, response instructions, etc. by predicting and classifying related data different from the data received by the communication unit.

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

[0082] 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 may be realized in any order unless the output of a previous process is used in a later process. Even if the operational flow in the claims, specifications, and drawings is explained using "first," "next," etc. for convenience, it does not mean that it is essential to perform the process in this order.

[0083] Also, aspects of each embodiment may be embodied in whole or in part by a computer. As an example of the computer, a program installed on the computer may cause the computer to perform operations associated with an apparatus according to an embodiment of the present invention or one or more "parts" of the apparatus. Alternatively, the program may cause the computer to execute the operations or one or more "parts". The program may 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 execute specific operations associated with some or all of the blocks of the flowcharts and block diagrams described herein.

[0084] 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 response to the designation of the parent group using the hierarchical code of the parent group. (Item 2) 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 a parent group of the group. (Item 3) 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; Item 1. The management device according to item 1, further comprising 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 comprising 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 accepts 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 response to 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 according to item 6.

[0085] 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 an account type of the account; The management device includes a base setting unit that accepts registration of bases and accepts designation of master information including the above 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 specified base 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 inputting data at the 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 stores the results of 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 the hierarchy. (Item 7) A step in which a group setting unit accepts registration of a group; an account setting unit receiving registration of an account and receiving designation of a group and an account type of the account; The management method includes a step in which a base setting unit accepts registration of a 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 according to item 7. [Explanation of symbols]

[0086] 10, 15 Management System 50 Network 100, 1500 management device 110, 1510 Control unit 112 Group setting section 114 Account Settings 116 Authorization role setting section 118 Display control section 120 Communications Department 130 Storage section 200 terminals 300 Transmitting device 401, 601 hierarchy 402, 602 Group 501, 701 Group Table 901 Account Table 1101 Group Name 1102 Roll 1103 Authority 1401 Group 1402 including subsidiaries 1403 Refine 1404 Information Field 1512 Base Setting Department 1514 Input Management Unit 1516 Input reception section 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 that indicates the input information item to be set. 2601 Group 2602 including subsidiaries 2603 Narrow down your bases 2604 year 2605 per year / month 2206 Classification field 2207 A field that indicates the input information item to be checked.

Claims

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 response to 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 a group code of the group after a hierarchical code of a parent group of the group.

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

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 that operates the terminal, and displays information about the group according to the authority of the role.

5. The management device according to 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 the steps of: a group setting unit accepting registration of a group; accepting designation of a parent group of the group; and generating a hierarchical code for the group in response to 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.

Images