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 including a management device and a plurality of terminals, the management device 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 of 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.SELECTED DRAWING: Figure 16

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses a database management device. [Prior Art Document] [Patent Document]

[0003] [Patent Document 1] JP 2019-219847

Summary of the Invention

Means for Solving the Problems

[0004] A management device according to an aspect of the present invention includes 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 site setting unit that receives registration of a site and receives designation of master information including the group for each site.

[0005] In the management device, the account setting unit displays candidate accounts according to the account type from the group, and associates a selected account among the candidate accounts with an input person for a designated site.

[0006] The management device further includes an input management unit that displays common input information items for each site and receives designation of input information items for each site.

[0007] In the management device, the input reception unit further includes a display request from a terminal operated by an input person of a site, displays input information items designated for the site, receives input for each item of input information from the terminal, executes processing according to each designation, and stores a result according to the processing.

[0008] In the above management device, a display control unit is further provided, which receives a display request from a terminal, determines a role associated with an account that operates the terminal, receives a designation of a base according to the authority of the role, and displays input item information regarding the base.

[0009] In the above management device, a display control unit is further provided, which receives a display request from a terminal, determines a hierarchy from a group associated with an account that operates the terminal, and displays information on bases regarding groups below the hierarchy.

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

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

[0012] Note that the above summary of the invention does not enumerate all the features of the present invention. Also, sub-combinations of these feature groups can also be inventions.

Brief Description of Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Mode for Carrying Out the Invention

[0014] Hereinafter, the present invention will be described through embodiments of the invention. However, the following embodiments do not limit the invention according to the claims. Also, not all combinations of features described in the embodiments are essential for the solution means of the invention.

[0015] In recent years, in companies, organizations, etc., there has been an increasing need to efficiently collect information from groups of many related organizations, etc. As the number of groups increases, the relationships between groups become complicated, so there is a need for unified management. Also, on the side of collecting information, there is a need to collect more accurate and more information, while on the side of providing information, there is a need to provide information more easily.

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

[0017] FIG. 1 shows an example of the overall configuration of the 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 accept direct operations or may accept operations through the terminals 200. In the first embodiment, an example in which the management system 10 includes one management device 100 will be described. However, the management system 10 may include management devices 100 for different companies, for example. Data may be exchanged between a plurality of management devices 100.

[0018] FIG. 2 shows an example of the functional blocks of the management device 100. The management device 100 may be configured as a computer as hardware. Further, the computer may execute the management method described in this 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 an MPU, a microcontroller such as an MCU, or the like. The communication unit 120 manages communication between each component within the management device 100. In addition, the communication unit 120 communicates with an external computer such as the terminal 200 via a network 50 such as the Internet. The storage unit 130 stores information processed by the control unit 110, information received from each terminal 200, and the like. The storage unit 130 may be configured by a storage medium such as a memory device, a RAM, a ROM, an HDD, an SDD, or the like. The storage unit 130 may store various information as data in a table and store a database configured by associating each table.

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

[0020] FIG. 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 registration of a group (S100), accepts designation of a parent group of the group (S102), and generates a hierarchical code of the group using the hierarchical code of the parent group in accordance with the designation of the parent group (S104).

[0021] The group setting unit 112 accepts group registration (S100). The group registration is performed, for example, by an operation of creating a group using the terminal 200. Specifically, for example, the group setting unit 112 accepts group registration by creating a group name by an operation using the terminal 200 and numbering the group code associated therewith. The group may be a company and an internal group of the company (such as a head office, a department, etc.), or may be various organizations, national or local public bodies, or any other organization.

[0022] Here, with reference to FIG. 4, the relationship between the group and the hierarchy will be described with a specific example. FIG. 4 is a diagram showing an example of the hierarchical relationship of the group according to the first embodiment. In FIG. 4, a hierarchy number 401 indicating the hierarchy (hierarchy 1, hierarchy 2, hierarchy 3, and hierarchy 4 are shown, but not limited thereto, and more hierarchies such as hierarchy 5, hierarchy 6, hierarchy 7, hierarchy 8,... may be included) and a group name 402 indicating the groups in each hierarchy (group A, group B, group C,... group J are shown, but not limited thereto, and more groups such as group K, group L,... may be included) are shown. For example, the hierarchy may be the relationship between companies such as a holding company, a head office, a subsidiary, a grandchild company, an affiliated company, and an overseas office, or may include an internal group of the company, or may show the connection between any other organizations.

[0023] The group with group name 402 shown below hierarchy number 401 is included in that hierarchy. In FIG. 4, group A is in hierarchy 1, groups B and C are in hierarchy 2, groups D to H are in hierarchy 3, and groups I and J are in hierarchy 4. Also, the lines in the figure indicate the connection of the group hierarchies. For example, since both group B and group C are connected by a line to group A, both group B and group C (hierarchy 2) are linked to group A (hierarchy 1). At this time, group A is defined as the "parent group" of group B and group C. Similarly, since group D and group E are connected by a line to group B, and groups F to H are connected by a line to group C, group D and group E (hierarchy 3) are linked to group B (hierarchy 2), and groups F to 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 groups F to H.

[0024] FIG. 5 is a diagram showing an example of a group table 501 according to the first embodiment. FIG. 5 shows in a table the relationship between the groups and hierarchies shown in FIG. 4, indicating that the information regarding the groups and hierarchies is stored in the storage unit 130 in a table format. Also, the display control unit 118 may cause a part or all of the group table 501 shown in FIG. 5 to be displayed on the display device. Hereinafter, the diagrams regarding the table are the same and the description thereof is omitted.

[0025] The group table 501 has, but is not limited to, a group code, a group name, a parent group name, and a hierarchy code, and may have other information such as, for example, a creation date, a deletion date, a location, and detailed attributes. The group code is a code assigned to each group and constitutes a unique ID. In FIG. 5, 1, 2, 3 ··· 10 are numbered, but it is not limited to this, and any non-duplicate code may be assigned. The group name represents the name of each group. In FIG. 5, the same A, B, C ··· J as the groups shown in FIG. 4 are shown. The parent group represents the upper-level group associated with the group as described with respect to FIG. 4. For example, in FIG. 5, there is no parent group for group A, and thus it is shown that group A is at hierarchy 1. Also, the parent group of group B is A, and the parent group of group C is also A, and thus it is shown that both group B and group C are at hierarchy 2 associated with group A (hierarchy 1).

[0026] The hierarchical code is a code assigned to each group, which constitutes a unique ID and represents the hierarchy at the same time. The group setting unit 112 generates the hierarchical code of a group by arranging 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 at level 1), the hierarchical code is generated using the group code of the group. For example, in FIG. 5, the hierarchical code of group A at level 1 (without a parent group) is " / 1 / " using the group code "1" of group A. And the hierarchical code of group B at level 2 (parent group is group A) is " / 1 / 2 / " by arranging the group code "2" of group B after the hierarchical code " / 1 / " of the parent group. Similarly, the hierarchical code of group C at level 2 (parent group is group A) is " / 1 / 3 / " by arranging the group code "3" of group C after the hierarchical code " / 1 / " of the parent group. Also, the hierarchical code of group D at level 3 (parent group is group B) is " / 1 / 2 / 4 / " by arranging the group code "4" of group D after the hierarchical code " / 1 / 2 / " of the parent group. In this way, by generating the hierarchical code of a group at a certain level by arranging the group code of the group after the hierarchical code of the parent group of the group, the hierarchy can be generated infinitely except for physical constraints while maintaining the association between groups, and the hierarchies of many groups can be represented uniformly.

[0027] FIG. 6 is a diagram showing an example of the hierarchical relationship of groups according to the first embodiment, showing the hierarchical relationship after changing the hierarchical relationship of the groups shown in FIG. 4. In FIG. 6, similar to FIG. 4, there are shown a hierarchical number 601 indicating the hierarchy (hierarchies 1, 2, 3, 4, and 5 are shown, but not limited thereto, and more hierarchies such as hierarchies 6, 7, 8, 9,... may be included), and group names 602 indicating the groups at each hierarchy (groups A, B, C,..., J are shown, but not limited thereto, and more groups such as groups K, L,... may be included). Hereinafter, the same description as in FIG. 4 will be omitted.

[0028] In FIG. 6, the group in layer 1 has changed to group G instead of group A in FIG. 4. On the other hand, group A is in layer 3, and it is shown that the parent group is group C in layer 2. For the other groups, the layer of the group and its parent group have also changed.

[0029] FIG. 7 is a diagram showing an example of the group table 701 according to the first embodiment, and shows the hierarchical relationship after changing the hierarchical relationship of the group table 501 shown in FIG. 5. Also, FIG. 7 shows in a table the relationship between the groups and layers shown in FIG. 6. Note that in FIG. 7, the hierarchical codes included in the group table 501 of FIG. 5 are shown as "hierarchical codes before change" for reference. Hereinafter, the same description as in FIG. 5 will be omitted.

[0030] Here, an operation example of the group setting unit 112 that changes the relationship between the groups and layers shown in FIGS. 4 and 5 to the relationship shown in FIGS. 6 and 7 will be described. First, in FIGS. 4 and 5, group G, which was in layer 3, becomes layer 1 by canceling the designation of group C, which was the parent group (for example, designating without a parent group). At this time, the group setting unit 112 deletes " / 1 / 3" arranged before the group code "7" of group G in the hierarchical code " / 1 / 3 / 7 / " of group G by canceling the designation of the parent group, and updates the hierarchical code of group G to " / 7 / ". Although not shown in FIGS. 4 and 5, if there are groups in the lower layers associated with group G, the layers of these lower-layer groups may each become two levels higher at the same time as the layer of group G becomes two levels higher from layer 3 to layer 1.

[0031] Also, in FIGS. 4 and 5, Group A, which was at Hierarchy 1, is associated with Group C by designating Group C as the parent group and becomes one level lower than Group C. In FIGS. 6 and 7, since the hierarchy of Group C is Hierarchy 2, the hierarchy of Group A becomes Hierarchy 3. At this time, the group setting unit 112 receives the designation of Group C as the parent group of Group A, arranges the hierarchy code “ / 1 / ” of Group A (in FIG. 5) after the hierarchy code “ / 7 / 3 / ” of Group C (in FIG. 7), and updates the hierarchy code of Group A to “ / 7 / 3 / 1 / ” as shown in FIG. 7. In the above description, for simplicity, it was described that there is no lower-level group associated with Group A in FIGS. 4 and 5, but when the hierarchy of Group A becomes two levels lower from Hierarchy 1 to Hierarchy 3, the hierarchies of these lower-level groups may also each become two levels lower at the same time.

[0032] Similarly, the group setting unit 112 receives the designation of the parent group of the group (S102 in FIG. 3), and generates the hierarchy code of the group according to the designation of the parent group using the hierarchy code of the parent group (S104 in FIG. 3), thereby enabling the relationship between the groups and hierarchies shown in FIGS. 4 and 5 to be easily changed to the relationship shown in FIGS. 6 and 7 as intended. Thereby, even when the relationships between groups in many groups are complex, the hierarchical relationship can be uniformly and easily changed and managed simply by designating the parent group of each group. Also, although not shown in FIGS. 4 to 7, the hierarchy change flag and the change date and time may be included in the group table or a separately set hierarchy table for the hierarchy change. And the group setting unit 112 may specify the change flag at the time of the change for the hierarchy where changes such as addition, replacement, and deletion are made, and record the change date and time in the table. Thereby, the history of past changes to the hierarchy can be retained.

[0033] Note that although an example in which there is one group at Hierarchy 1 is shown in FIGS. 4 to 7, this is not limiting, and there may be a plurality of groups at Hierarchy 1.

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

[0035] The account setting unit 114 receives account registration (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 in the account table 901 and executes an account registration process by receiving or generating each of the above information for the row. Note that the information included in the account table is not limited to the above, and may include other information such as an account creation date, a deletion date, a name, an email address, and a detailed affiliation.

[0036] Here, in the account table 901 of FIG. 9, the account code is a code assigned to each account and constitutes a unique ID. In FIG. 9, 0001, 0002, 0003 ··· 0012 are numbered, but it is not limited thereto, and any non-duplicate code may be assigned. The account code may be an arbitrary code input by an operation of the terminal 200 or the like, or the account setting unit 114 may automatically assign a non-duplicate code during account registration. The numbering may determine and use an unused one from a small value in a predetermined number of digits, or may be randomly generated using a function or the like and use the one excluding duplicate values.

[0037] The account setting unit 114 receives the designation of the account group and the account type (S202). For example, FIG. 9 shows an example in which the account setting unit 114 receives the designation of group C and individual authority for account 0003. The designation of the group and the account type may be executed 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 the overall management authority or the overall authority, the account setting unit 114 may automatically designate the hierarchy of the group of the account as hierarchy 1.

[0038] Here, in the account table 901 of FIG. 9, the account type represents the type of the account and distinguishes the roles and authorities of each account. In FIG. 9, there are four account types: overall management authority, overall authority, individual authority, and input person in charge. The difference between the overall management authority and the overall authority may be, for example, that the former can add accounts and authority roles while the latter cannot. The individual authority and the input person in charge will be described in detail with reference to FIGS. 10 and 11. The account type is not limited to this, and other arbitrary account types may be included, and the names are not limited to these either. For example, they may be other names such as the main body administrator, main body employee, subsidiary employee, on-site person in charge, etc.

[0039] Also, in the account table 901 of FIG. 9, the group name represents the name of the group associated with each account, and for example, it may represent the name of the group to which each account belongs. The group information may be stored in a group table as shown in the group table 501 of FIG. 5 and the group table 701 of 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, the account with account code 0003 is associated with group C, and the information of 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 refer to 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.

[0040] Note that in the account table 901 of FIG. 9, although the group names for account codes 0001 and 0002 are blank, for accounts that do not require group management, it is not necessary to associate them with a group. For example, although account codes 0001 and 0002 actually belong to group A at level 1 in FIGS. 4 and 5, since the account type has a privilege that allows operations related to all management devices 100 as an overall management privilege, or the account type has a privilege that allows operations related to all groups as an overall privilege, etc., they are not associated with group A because they do not require management according to the belonging group. Note that in other embodiments, the association between the account table and the group table may be made mandatory. In that case, for example, in FIG. 9, since the account types of account codes 0001 and 0002 are overall management privilege or overall privilege, the display of group name A to which they belong may be omitted.

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

[0042] In the account table 901, the roles are "including subsidiaries", "only the company itself", "role 1", and "role 2". "Including subsidiaries" represents a role that also has authority over the lower-level groups of the group to which the account belongs. "Only the company itself" represents a role that has authority only over the group to which the account belongs. "Role 1" and "role 2" represent arbitrarily set roles, which will be described in detail in FIGS. 10 and 11. Note that in FIG. 9, "including subsidiaries" and "only the company itself" are pre-set roles, but the names, role contents, etc. may be editable. Also, the roles in the account table are not limited to the above, and it may have any other arbitrary roles. FIG. 9 shows an example where one role is designated for each account, but multiple roles may be set for each account. However, for example, in FIG. 9, conditions such as mutual exclusivity and dependency relationships (for example, role Y cannot be designated unless role X is designated) may be provided for the multiple designated roles, such that "including subsidiaries" and "only the company itself" are mutually exclusive.

[0043] 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 specification of authority for each item's role for each group (S302). Hereinafter, each operation will be described with reference to FIG. 11. FIG. 11 is a diagram showing an example of the setting screen for authority roles according to the first embodiment. The setting screen has a field 1101 showing the group name, a field 1102 showing the authority items for the role, and a field 1103 showing the specification of authority for each item's role for each group.

[0044] 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. Although they are named Role 1, Role 2, etc. for convenience in FIG. 11, for example, they may be the names of the information items (such as greenhouse gas emissions, activity levels of activities involving greenhouse gas emissions, water usage amounts, etc.) as items indicating authority for specific information items. The authority role setting unit 116 may accept a registration request for authority items for roles and setting of the name of the item by operating the terminal 200.

[0045] The permission role setting unit 116 receives the specification of the permission for the role of each item for each group (S302). Here, in FIG. 11, groups A, B, C... F are shown in the field 1101, and for each of these groups, in the field 1103, either "editable", "displayable", or "no permission" is shown for each of the item roles 1, 2, and 3 shown in the field 1102. For example, the permission role setting unit 116 receives, by operating the terminal 200, the specification to set the permission for role 1 for group F to "no permission", and sets the permission as shown in FIG. 11. Then, as shown in FIG. 9, when role 1 is assigned to the account 0009 belonging to the group F, since there is no permission for the items shown in role 1 in the operation of the terminal 200 by the account 0009, the items cannot be edited and are not displayed. This will be described in detail below with reference to FIG. 12.

[0046] FIG. 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 permission of the role (S404).

[0047] 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 the authentication of the account that operates the terminal 200, or may be received at an arbitrary timing after the completion of the authentication or the like. The display control unit 118 determines the role associated with the account that operates the terminal 200 (S402). For example, when the account that operates the terminal 200 is the account shown as account code 0004 in the account table 901 of FIG. 9, it is determined that the role is "only the company's". 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 "only the company's" role, since the account has the authority to handle only the company's information, the display control unit 118 displays only the information about group C associated with the account on the display unit of the terminal 200 operated by the account code 0004.

[0048] Similarly, for example, when the account that operates the terminal 200 is the account shown as account code 0011 in the account table 901 of FIG. 9, the display control unit 118 determines that the role is "role 2". And since the role 2 has the authority of "editable" for the item of role 2 as shown in FIG. 11, the display control unit 118 displays the item of role 2 in an editable manner on the display unit of the terminal 200 operated by the account code 0011. In this way, since the display control unit 118 determines the role associated with the account that operates the terminal 200 that has received the display request, and displays information about the group according to the authority of the role, flexible control can be performed for each account.

[0049] FIG. 13 is a diagram showing an example of an operation flow of the management device 100 according to the first embodiment. The display control unit 118 receives a display request from the terminal 200 (S500), determines a hierarchy from the group associated with the account operating the terminal 200, and causes information about the groups below the hierarchy to be displayed on the display device of the terminal 200 (S502). Hereinafter, each operation will be described 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 receiving a designation of a group for which information is to be input, a field 1402 for receiving a designation of whether or not to include the lower hierarchy (subordinate) of the group, a field 1403 for receiving a designation of narrowing down in the case of including the lower hierarchy of the group, and a field 1404 for displaying the designated information.

[0050] 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 the authentication of the account operating the terminal 200, or may be received at an arbitrary timing after the authentication is completed. In particular, the display request from the terminal 200 may be received at the timing of inputting information in response to an information input request after an information input request from an account operating one terminal 200 to an account operating another terminal 200 is executed.

[0051] The display control unit 118 determines a hierarchy from the group associated with the account that operates the terminal 200, and causes information about groups below the hierarchy to be displayed on the display device of the terminal 200 (S502). The determination of the hierarchy may be executed by identifying the hierarchy from the group associated with the account that operates the terminal 200 using the group table 501 in FIG. 5 or FIG. 7 or the group table 701 and the account table 901 in FIG. 9. For example, when the account that operates the terminal 200 is account code 0003 in the account table 901 in FIG. 9, the group associated with the account is C, and referring to the group table 501 in FIG. 5, the hierarchy code of group C is " / 1 / 3 / ", so it is identified as hierarchy 2 as shown in FIG. 4.

[0052] Then, the display control unit 118 causes information about groups below the hierarchy to be displayed on the display device of the terminal 200. For example, when hierarchy 2 is determined from group C associated with the above account code 0003, the display control unit 118 causes information about groups below hierarchy 2 to be displayed on the display device of the terminal 200 as shown in FIGS. 4 and 5. For example, in FIG. 14, group C associated with the account code 0003 is shown in field 1401. Here, the display control unit 118 may accept a designation from any one or a plurality of groups F to J in the lower hierarchy in addition to group C in the field 1401. In this case, groups A, which are in a higher hierarchy than group C, and other groups B to E that are not associated with group C are not displayed as designation candidates in the field 1401.

[0053] In addition, the display control unit 118 may receive a designation for narrowing down the target for information confirmation among the groups below the said hierarchy and display the information of the narrowed-down target. For example, in FIG. 14, the display control unit 118 receives a designation for whether to narrow down the target for information confirmation including groups F to J (referred to as "subordinate" in FIG. 14), which are the hierarchies below group C, in the field 1402. When "including subordinates" in the said field 1402 is designated (a check mark is displayed in FIG. 14), the display control unit 118 may display the information of the target narrowed down to any one or a plurality of group C and groups F to J, which are its subordinates, in the "narrowing down" of the field 1403 in the field 1404. When the information of the narrowed-down target is information regarding a plurality of groups, each information may be displayed by juxtaposition, summation, etc. Thereby, information regarding the groups below the hierarchy can be displayed more flexibly and understandably.

[0054] Next, the management device 1500 according to the second embodiment will be described. The management device 1500 according to the second embodiment realizes information management that, in addition to efficient group management, collects more accurate and more information for the information collection side while providing information more easily for the information providing side. Hereinafter, the same description as that in the first embodiment in the second embodiment will be omitted.

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

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

[0057] 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 group registration, and the account setting unit 114 accepts account registration and accepts designation of the group and account type of the account. Then, the site setting unit 1512 accepts site registration (S600) and accepts designation of master information including a group for each site (S602). Hereinafter, each operation will be described with reference to FIG. 18. FIG. 18 is a diagram showing an example of the site table 1801 according to the second embodiment. The site table 1801 stores the group name and the site name in association with each other in the storage unit 130.

[0058] The site setting unit 1512 accepts site registration (S600). The site registration is performed, for example, by an operation of creating a site using the terminal 200. Specifically, for example, the site setting unit 1512 accepts site registration by creating a site name by an operation using the terminal 200 and numbering the site code associated therewith. The site may be a company and an internal group of the company (such as a head office, a department, etc.), or various organizations, national and local public bodies, or any other organization, but is different from a group. For example, when the group is a company, the site may be another company, a company facility, a factory, a branch office, an overseas local corporation, or other organizations different from the group. Also, as shown in FIG. 18, a plurality of sites may be associated with one group. For example, in FIG. 18, two sites a1 and a2 are associated with group A.

[0059] The site setting unit 1512 accepts designation of master information including a group for each site (S602). Although not shown in FIG. 18, the site table 1801 may have a site code for identifying a site, a group code, an account code, an input person in charge, basic information, questionnaire information, a power plan, power source information, a gas plan, facility equipment information, a business, a facility, a facility classification, a management item, an activity amount code, and other related master information in addition to the group name. The site setting unit 1512 accepts designation for each of the master information for each site.

[0060] FIG. 19 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. The account setting unit 114 displays candidate accounts according to the account type from the group (S700), and associates the selected account among the candidate accounts as the input person in charge with the designated site (S702). Hereinafter, each operation will be described with reference to FIG. 20. FIG. 20 is a diagram showing an example of the setting screen of the input person in charge according to the second embodiment. The setting screen of the input person in charge has a field 2001 showing the list of sites to be added, a field 2002 showing the input person in charge associated with the list of sites to be added, a candidate list field 2003 showing the candidate accounts to be associated, a designation 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 showing the candidate accounts narrowed down by the designation field 2004.

[0061] The account setting unit 114 displays candidate accounts according to the account type from the group (S700). For example, in the candidate list field 2003 of FIG. 20, group C is designated in the designation field 2004. Here, it is assumed that the accounts belonging to the group C are those shown in the account table 901 of FIG. 9. Then, there are five accounts with account codes 0003 to 0007 belonging to group C. The account setting unit 114 determines the account codes 0005 to 0007 in which the account type is designated as "input person in charge" from group C as candidate accounts. And in the field 2005, only the account code 0007 of the candidate accounts that has not yet been shown in the field 2002 as the input person in charge is shown as "C 0007". Although omitted in FIG. 20, the designation field 2004 may display candidate accounts by other designation methods. For example, the designation field 2004 may accept designations with items such as account codes, names, email addresses, and other items for identifying accounts for identifying candidate accounts.

[0062] The account setting unit 114 associates the selected account among the candidate accounts as the input person with respect to the designated base (S702). For example, in FIG. 20, it shows that for the base c2 designated as the addition destination base, the selected accounts 0005 and 0006 among the candidate accounts 0005 to 0007 are associated as the input person. Note that the account setting unit 114 may limit and display candidates for the list of addition destination bases according to at least one of the hierarchy of the account operating the terminal 200 and the account type. Also, the selection as the input person from the candidate accounts may be executed by dragging and dropping from the candidate accounts shown in the field 2005 to the field 2002. According to the second embodiment, since the candidate accounts are displayed according to the account type from the group, and the selected account among the candidate accounts is associated as the input person with respect to the designated base, the input person can be easily associated and set for each base.

[0063] 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 site (S800) and accepts designation of input information items for each site (S802). Hereinafter, each operation will be described with reference to FIG. 21. FIG. 22 is a diagram showing an example of the setting screen for information input according to the second embodiment. The setting screen has a field 2201 indicating the group name to be set, a field 2202 indicating the site name to be set, a field 2203 indicating the year to be set, a field 2204 indicating the type of annual 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 specified in fields 2201 to 2205. For example, in FIG. 22, the site c2 of group C is specified as the setting target, the year is 2023, the display period is annual, and the information classification is GHG (greenhouse gas) Scope 1 (direct emissions in the GHG protocol). According to this content, in field 2206, input information items of "kerosene" and "light oil" are set in the major item of "fuel use", and for each usage amount, the value for the year 2023 in kl units, the reason for the difference, comments, and attached materials are set to be input. Also, as shown by "(Add)" at the bottom of the major item of "fuel use", the input management unit 1514 can further accept designation of addition of input information items. Although not shown in FIG. 22, a field may be provided for each of the various information classifications shown in field 2205 to indicate whether the setting of field 2206 is "being input" or "already input". Thereby, even a person other than the person in charge of input can easily confirm whether the field 2206 of the information classification is still being input or the input has already been completed.

[0064] The input management unit 1514 displays common input information items for each site (S800). For example, in FIG. 22, the input information items set for site c2 are shown in field 2206, and the input information items are displayed based on the common input information items with other sites. The common input information items are stored as templates in the storage unit 130 and are displayed by the input management unit 1514 for each site. Then, the input management unit 1514 accepts the designation of input information items for each site (S802). For example, in FIG. 22, the type of the input information item "gas oil" is "usage amount" and the unit is "kl", but the input management unit 1514 accepts an instruction to change the type to "emission amount" and the unit to "tCO2e" by operating the terminal 200, and for site c2, the input reception unit 1516 may accept information input with the changed type and unit. By thus displaying the common input information items for each site, information can be collected uniformly from the sites, while for certain items, customization can be achieved by accepting the designation of input information items for each site, and information available at each site can be collected. Note that the acceptance of the designation of input information items for each site by the input management unit 1514 may be permitted only for specific accounts according to at least one of the account type, role, and hierarchy. Thereby, control over the input information items can be restricted to accounts with specific authorities, and the uniformity of information collection can be maintained.

[0065] FIG. 23 is a diagram showing an example of the 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 input person in charge of the base (S900), displays the input information items specified for the base (S902), receives the input for each item of the input information from the terminal 200, executes the processing according to each specification, and stores the result according to the processing (S902). Although the information input screens shown in each operation are not illustrated, each operation will be described with reference to the portions common to the information input screen among the setting screens of FIG. 22 above. Note that the portion common to the setting screen of FIG. 22 of the information input screen may change according to the account type. For example, when the account type is the overall management authority or the overall authority, the setting screen of FIG. 22 and the information input screen may be common, and while the input management unit 1514 receives the specification of the input information items, the input reception unit 1516 may receive the input for each input information item. Further, when the account type is an individual authority, similarly, while the input management unit 1514 receives the specification of the input information items within the range of the group and the base according to the role, the input reception unit 1516 may receive the input for each input information item. Further, when the account type is the input person in charge, the input reception unit 1516 may receive only the input for the set input information items without the input management unit 1514 receiving the specification of the input information items, and only for the associated base. In this case, for example, the designation item “(Addition)” is not displayed on the information input screen among the setting screens of FIG. 22.

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

[0067] The input reception unit 1516 displays the input information items specified for the relevant site (S902). The operation of specifying the input information items for the site has been described as per the explanations with reference to FIGS. 21 and 22. Then, the input reception unit 1516 displays the specified input information items. As described above, for the information input screen displayed here, for example, depending on the account type, the common part with the setting screen in FIG. 22 may change.

[0068] The input reception unit 1516 receives the input for each item of the input information from the terminal 200, executes the processing according to each specification, and stores the result according to the processing (S902). For example, for the input information item "CO2 (non - energy origin)" under the major item "6.5 gases" in GHG Scope 1 set in the setting screen of FIG. 22, the input reception unit 1516 may receive the input of the value "xyy" for the year 2023 for this item (originally numerically input but described as a character string for convenience of explanation) from the terminal 200 operated by the account associated as the input person in site c2. Then, the input reception unit 1516 executes the processing according to each specification. For example, for "CO2 (non - energy origin)", assuming that the input management unit 1514 has received the specification that when a value exceeding a predetermined threshold or range is input for the value in 2023 compared to the value "xyx" in 2022, the input of the reason for the difference is required, and assuming that the value "xyy" in 2023 exceeds the predetermined threshold or value compared to the value "xyx" in 2022, the input reception unit 1516 may execute the display processing indicating that the input of the reason for the difference is required according to the above specification. Also, the input reception unit 1516 stores the result according to the processing. For example, in response to the display processing indicating that the input of the reason for the difference is required, if the input reception unit 1516 has not received the input of the reason for the difference, it may show an error display in the item for the reason for the difference and store the result in the storage unit 130, or if it has received the input to the item for the reason for the difference, it may store the value "xyy" for the year 2023 and the reason for the difference in the storage unit 130. Thereby, the information to be collected from the input person can be collected more precisely and in more detail.

[0069] FIG. 24 is a diagram showing an example of the operation flow of the management device 1500 according to the second embodiment. The display control unit 118 receives a display request from the terminal 200 (S1000), determines the role associated with the account operating the terminal (S1002), receives a designation of a base according to the authority of the role, and displays input item information regarding the base (S1004). Hereinafter, descriptions of the content overlapping with that described as an example of the operation flow of the management device 100 according to the first embodiment with reference to FIG. 12 will be omitted.

[0070] The display control unit 118 receives a designation of a base according to the authority of the role, and displays input item information regarding the base (S1004). For example, when the display control unit 118 receives a display request from the terminal 200 operated by the account with the 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 subsidiary companies", since the account has the authority to handle information of groups at lower levels in addition to its own group, the display control unit 118 receives a designation of a base as a display target from the bases associated with group C and groups F to J at lower levels thereof 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 regarding the designated base on the display device or the like of the terminal 200 operated by the above account. In this way, since the display control unit 118 determines the role associated with the account operating the terminal 200 that has received the display request, and executes receiving a designation of a base and displaying the input information items regarding the base according to the authority of the role, while flexibly controlling each account, for example, a person with individual authority of their own group closer to the site than a person with overall management authority or overall authority of the parent group can set the input information items for the base, so that information collection can be performed more appropriately.

[0071] 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 the terminal (S1100), determines the hierarchy from the group associated with the account operating the terminal, and causes the information of the bases regarding the groups below the hierarchy to be displayed (S1102). Hereinafter, the description of the content overlapping with that described as an example of the operation flow of the management device 100 according to the first embodiment with reference to FIGS. 13 and 14 will be omitted. Also, each operation will be described with reference to FIG. 26. FIG. 26 is a diagram showing an example of the information confirmation screen according to the second embodiment. The information confirmation screen has a field 2601 for receiving the designation of the group for which information is to be input, a field 2602 for receiving the designation of whether or not to include the lower hierarchy (subordinate) of the group, a field 2603 for receiving the designation of narrowing down the bases when including the lower hierarchy of the group, a field 2604 for receiving the designation of the year, a field 2605 indicating the type of annual or monthly as the display period, a field 2605 indicating various information classifications, and a field 2606 showing the confirmation screen of each information according to the content specified in the fields 2601 to 2605.

[0072] The display control unit 118 determines the hierarchy from the group associated with the account that operates the terminal 200 that has received the display request, and causes the information of the bases related to the groups below that hierarchy to be displayed (S1102). Here, the "information of the bases related to the groups below that hierarchy" means that, for example, when it is determined that the group is C and the hierarchy is 2 for the terminal 200 operated by the account with the account code 0003, the display control unit 118 causes the information related to the bases c1 to c3, f1, and f2 associated with the groups F to J below the hierarchy 2 of the group C, as shown in FIGS. 4, 5, and 18, to be displayed on the display device of the terminal 200. 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 accept a designation from any one or a plurality of the groups F to J in the lower hierarchy in addition to the group C in the field 2601. Also, in FIG. 26, the display control unit 118 designates "including the subordinates" including the groups F to J (referred to as "subordinates" in FIG. 26) that are in the lower hierarchy of the group C in the field 2602, and it is shown that in the "narrowing down of bases" in the field 2603, the narrowing down to "c1, c3, f1" is executed among the bases associated with the group C and its subordinates, the groups F to J. And each piece of information shown in the field 2607 is displayed by summing the values input for the bases c1, c3, and f1. As a result, it is possible to display the information of the bases associated with the groups below the hierarchy in a more flexible and understandable manner.

[0073] In addition to the above embodiments, the present invention is also realized in the following plurality of other embodiments.

[0074] As one of other embodiments, the management device 100 or 1500 may include a derivation unit. The derivation unit may derive the greenhouse gas emissions by multiplying the conversion data stored in the storage unit 130 by at least one of the usage amounts of electricity, water, oil, and gas. In this case, for each usage amount, the greenhouse gas emissions are derived by multiplying the original unit (conversion data) indicating the greenhouse gas emissions per unit of each usage amount. Further, when deriving the amount of waste from the above usage amounts, the amount of waste may be derived by multiplying the original unit (conversion data) indicating the amount of waste per unit of each usage amount for each usage amount. In addition, the derivation unit may convert the original unit indicating the amount per unit of each usage amount for each usage amount into conversion data and use it to derive each amount from each usage amount, such as the amount of by-products, NOx, SOx, BOD, COD, etc., the affected areas such as air pollution, air chamber pollution, harmful chemicals, ozone layer depletion, acidification, noise, global warming, photochemical oxidants, eutrophication, resource consumption, ecotoxicity, fuel consumption, land use, etc., and the protected objects such as human health, social accounting, biodiversity, primary production, etc. based on damage assessment.

[0075] Note that the above usage amounts may include the fuel consumption due to the operation of the facility. The fuel may include solid fuels (raw coal, general coal, anthracite, coke, petroleum coke, briquettes or pea coal, wood, charcoal, and other solid fuels), liquid fuels (coal tar, petroleum asphalt, condensate, crude oil (excluding condensate (NGL)), gasoline, naphtha, jet fuel, kerosene, light oil, A heavy oil, B·C heavy oil, 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). Further, the activities performed for the manufacture of the product related to the usage amount may be activities that consume at least one of heat and steam.

[0076] In another embodiment, the display control unit 118 may perform display control by regarding the information derived by the derivation unit using the conversion data as "secondary data" and regarding other input data as "primary data" (or when information regarding data quality is included in each piece of information and "primary data" or "secondary data" is identified as such information, the identified one). Further, the same conversion data may be used for all bases in a common input information item. Thereby, even after a request for information input to each base, the application of the conversion data can be optimally maintained by adding, modifying, etc. the conversion data in the common input information item.

[0077] In addition, the information managed by the management device 100 or 1500 may include at least one of greenhouse gas emissions related to production, human rights issue countermeasures, and disaster risk countermeasures. The human rights issue countermeasures 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 processing such as assembly of the product itself, but also processing such as assembly of parts constituting the product and processing of materials (including raw materials, etc.) constituting each part). The disaster risk countermeasures may indicate whether measures are taken to prevent the manufacture of products from being affected when a disaster occurs. In addition to the above, the data managed by the management device 100 may include any other things that the company desires to request input from related companies. For example, various damage calculation type environmental impact assessments, for the environment, product carbon footprint related to climate change, biodiversity, land use, raw material procurement related to natural resources, hazardous substances, waste management, packaging materials, and waste of household appliances, etc. related to waste treatment, contained chemicals, air pollutants, water quality, and soil pollution related to environmentally regulated substances, and other data related to environment technology, energy, noise, vibration, odor, etc. may be included. Also, for society, human rights related to human resources (child labor, forced labor, working hours, wages, labor rights, discrimination, etc.), labor management and safety and health, human capital, safety quality related to the safety of product services, safety of each substance, privacy and data security, relationship with the region, diversity, equity and inclusion, well-being and engagement, compliance and ethics, and other data related to society may be included. Also, for governance, ethics, law compliance related to corporate behavior, anti-corruption, risk management, disaster countermeasures, tax transparency, and other data related to governance may be included. Also, data related to due diligence for each of the above items may be included. The designation or input of input information items related to these information is shown in fields 2206 and 2607 in the classification indicated as "Questionnaire" in field 2205 of FIG. 22 and field 2606 of FIG. 26, and each designation or input etc. may be accepted.

[0078] As one of other embodiments, the management device 100 or 1500 may further include an administrator setting unit. The administrator setting unit receives settings as to whether each item is editable based on the account type or role. For example, among the environmental information of each site, for items that must be collected by those with overall management authority, it is possible to set that they are not editable (non-editable) for any account type or role. Thereby, while allowing those with individual permissions closer to the site to independently add input information items that are considered necessary in each classification, and make editable items related to, for example, whether to input or make mandatory the reason for difference and comments, whether to attach or make mandatory attached materials, setting of thresholds, association with conversion data such as specific unit prices, etc., to provide flexibility, for information items that are essential as information collectors as described above, it is possible to always require information provision, enabling flexible and unified information collection.

[0079] As one of other embodiments, among the various information classifications shown in the field 2205 of FIG. 22, in the field 2206 in Scope 2 (indirect emissions related to electricity, heat, hot water, steam, chilled heat, and chilled water of the GHG protocol), in addition to activity amounts such as the usage amounts, amounts of money, and emissions amounts of electricity, heat, hot water, steam, chilled heat, and chilled water, the amount of electricity generated by self-generation, corporate PPA, etc., the amount of surplus electricity, the amount of purchased electricity, the amount of sold electricity, and the amount of external sales of other energy may be included. Also, the amount of certificates and credits applicable to Scope 2 may be included. Further, when power generation and its supply are performed between groups to be managed, the group setting unit 112 may receive registration of a dummy group for offset between groups. Then, register the power plan of the dummy group together with the emission factor of the group that generates power, register the group that receives power supply as a tenant, and set the tenant supply amount. Thereby, the GHG emissions amount of the dummy group becomes negative, and power generation and its supply between groups can be managed.

[0080] As one of the other embodiments, the management device 100 or 1500 may include an estimation unit (not shown). In the above-described other embodiment, an example in which the derivation unit performs a calculation process based on the conversion data stored in the storage unit 130 was shown. On the other hand, the estimation unit may execute various estimations based on the data. For example, in the fields 2205 of FIG. 22 and 2606 of FIG. 26, the classifications shown as "water" and "waste" are assumed to have various estimation source data set as input information items shown in the fields 2206 and 2607. For example, in the classification of "water", a measurement type is set as an input information item, and options such as an actual measurement value, an estimated value (calculated with a reference value), an extrapolated value (assuming that the drainage volume = the intake volume), etc. may be set as the measurement type. When the measurement type is specified as an extrapolated value, the display control unit 118 refers to a reference value based on various input information items required for the extrapolation (for example, extrapolation from the entire building, etc., extrapolation from other sites, other number of people, area, etc.), and the estimation unit may estimate each quantity related to water (intake volume, drainage volume, etc.). Similarly, in the case of "waste", options such as an actual measurement value and an estimated value (calculated with a reference value) may be set as the measurement type. The input management unit 1514 receives designation of conversion data such as a unit price and reference indicators such as production quantity, number of production personnel, production value, production cost, etc. for each site, 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). Thereby, the evaluation index between the sites can be easily displayed.

[0081] Further, the estimation unit may perform interpolation, prediction, etc. of each piece of information by performing statistical processing such as regression analysis on the data stored in the storage unit 130. Further, 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 data as teacher data. Regarding prediction, for example, the prediction of power demand is based on information such as weather, temperature, power plant outage information, power supply reserve rate, tie-line spare capacity, forward curves (including those related to power, coal, crude oil, and LNG), coal import price, crude oil import price, LNG import price, past fluctuations in the trading price of power in the power spot market, etc. It may be realized by a learning model generated based on this information or a statistical method based on these information. Regarding classification, the machine learning model or algorithm is one that solves the classification problem, and may include, for example, logistic regression (including ridge regularization and lasso regularization), random forest, support vector machine, neural network (including multi-layer perceptron), etc. Further, the evaluation of the accuracy of these classification predictions is performed by one or more of the mean squared error of the estimated conditional probability, the AUC (Area Under the Curve) quantified as the area under the ROC (Receiver Operating Characteristic) curve, the log loss in the minimization problem of the Kullback-Leibler divergence, and the calibration plot for plotting the measured value and the predicted value. Here, the classification prediction accuracy of the machine learning algorithm or model varies depending on the number of teacher data and feature quantities (for example, the number of days of acquisition of power consumption data used for learning and the additional attribute information). Therefore, the selection of the learning model may be performed by comparing the evaluation results of the classification accuracy by each machine learning algorithm or model under predetermined conditions. Also, in the selection of the learning model, those with a low computational cost required for learning and classification may be prioritized.As described above, the management device can perform display control, identification, derivation, response instruction, etc. through prediction, classification, etc. on related data different from the data received by the communication unit by the estimation unit.

[0082] As mentioned above, the present invention has been described using embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments. It is obvious to those skilled in the art that various changes or improvements can be made to the above embodiments. It is clear from the description of the claims that forms with such changes or improvements can also be included in the technical scope of the present invention.

[0083] It should be noted that the execution order of each process such as operations, procedures, steps, and stages in the devices, systems, programs, and methods shown in the claims, the specification, and the drawings is not explicitly indicated as "before" or "preceding" etc. in particular, and can be realized in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flows in the claims, the specification, and the drawings, even if "first," "next," etc. are used for convenience of explanation, it does not mean that it is essential to implement in this order.

[0084] Also, the aspects of each embodiment can be wholly or partially embodied by a computer. As an example of the computer, a program installed in the computer can cause the computer to function as an operation associated with the device according to the embodiment of the present invention or as one or a plurality of "parts" of the device. Or, the program can cause the computer to execute the operation or the one or a plurality of "parts." The program can cause the computer to execute the process according to the embodiment of the present invention or a stage of the process. Such a program can be executed by the CPU to cause the computer to execute specific operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.

[0085] In one aspect of the present invention, a management device, a management method, and a management program for the following items are realized. (Item 1) A management device including 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 the hierarchical code of the parent group according to the designation 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 arranging the group code of the group after the hierarchical code of the parent group of the group. (Item 3) An account setting unit that receives registration of an account, receives designation of a group and an account type of the account, and receives designation of a role according to the account type; and The management device according to Item 1, further including a permission role setting unit that receives registration of items of permissions for the role and receives designation of permissions 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 receives a display request from a terminal, determines a role associated with an account operating the terminal, and displays information regarding a group according to the permissions of the role. (Item 5) The management device according to Item 1, further including a display control unit that receives a display request from a terminal, determines a hierarchy from a group associated with an account operating the terminal, and displays information regarding groups below the hierarchy on a display device of the terminal. (Item 6) A management method including a stage in which a group setting unit receives registration of a group, receives designation of a parent group of the group, and generates a hierarchical code of the group using the hierarchical code of the parent group according to the designation of the parent group. (Item 7) A management program for causing a computer to execute the management method according to Item 6.

[0086] In another aspect of the present invention, a management device, a management method, and a management program for the following items are realized. (Item 1) A management device comprising: 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 of the account; and a site setting unit that accepts registration of a site and accepts designation of master information including the group for each site. (Item 2) The management device according to Item 1, wherein the account setting unit displays candidate accounts according to the account type from the group, and associates a selected account among the candidate accounts with an input person in charge for the designated site. (Item 3) The management device according to Item 1, further comprising an input management unit that displays common input information items for each site and accepts designation of input information items for each site. (Item 4) The management device according to Item 3, further comprising an input reception unit that accepts a display request from a terminal operated by an input person in charge of a site, displays the input information items designated for the site, accepts input for each item of input information from the terminal, executes processing according to each designation, and saves the result according to the processing. (Item 5) The management device according to Item 3, further comprising a display control unit that accepts a display request from a terminal, determines a role associated with an account operating the terminal, accepts designation of a site according to the authority of the role, and displays input item information regarding the site. (Item 6) The management device according to Item 3, further comprising a display control unit that accepts a display request from a terminal, determines a hierarchy from a group associated with an account operating the terminal, and displays information on sites regarding groups below the hierarchy. (Item 7) The stage at which the group setting unit accepts registration of a group; The account setting unit receives account registration and receives designation of the group and account type of the above account; A management method comprising: a site setting unit receiving site registration and receiving designation of master information including the above group for each site. (Item 8) A management program for causing a computer to execute the management method described in Item 7.

Explanation of Signs

[0087] 10, 15 Management system 50 Network 100, 1500 Management device 110, 1510 Control unit 112 Group setting unit 114 Account setting unit 116 Authority role setting unit 118 Display control unit 120 Communication unit 130 Storage unit 200 Terminal 300 Transmission device 401, 601 Hierarchy 402, 602 Group 501, 701 Group table 901 Account table 1101 Group name 1102 Role 1103 Authority 1401 Group 1402 Including subordinates 1403 Narrow down 1404 Field indicating information 1512 Site setting unit 1514 Input management unit 1516 Input reception unit 1801 Site table 2001 List of destination sites for addition 2002 Person in charge of input 2003 List of candidates 2004 Designated field Field indicating the 2005 candidate account 2201 Group 2202 Location 2203 Year 2204 Annual / Monthly Field indicating the 2205 classification Field indicating the input information item to be set 2601 Group Including subsidiaries Narrowing down of locations 2603 Year 2604 Annual / Monthly Field indicating the 2206 classification Field indicating the input information item to be confirmed

Claims

1. A group setting unit that accepts registration of a group and stores the group in a storage unit; An account setting unit that accepts registration of an account, accepts designation of a group and an account type of the account, associates the account, the group, and the account type, and stores them in a storage unit; A site setting unit that accepts registration of a site and accepts designation of master information including the group for each site, and the account setting unit extracts candidate accounts from the storage unit according to the account type from the group, displays and outputs them, and associates the selected account among the candidate accounts as an input person in charge with the designated site and stores it in the storage unit. A management device.

2. The management device according to claim 1, further comprising an input management unit that displays and outputs common input information items for each site and accepts designation of input information items for each site.

3. The management device according to claim 2, further comprising an input reception unit that accepts a display request from a terminal operated by an input person in charge of a site, displays and outputs the input information items designated for the site, accepts input for each item of input information from the terminal, executes processing according to each designation, and saves the result according to the processing.

4. The management device according to claim 2, further comprising a display control unit that accepts a display request from a terminal, determines a role associated with an account operating the terminal, accepts designation of a site according to the authority of the role, and displays input item information regarding the site.

5. The management device according to claim 2, further comprising a display control unit that accepts a display request from a terminal, determines a hierarchy from a group associated with an account operating the terminal, and displays information on sites regarding groups below the hierarchy.

6. A management method by a computer functioning as a group setting unit, an account setting unit, and a base setting unit, comprising: a step in which the group setting unit receives registration of a group and stores the group in a storage unit; a step in which the account setting unit receives registration of an account, receives designation of a group and an account type of the account, associates the account, the group, and the account type, and stores them in a storage unit; a step in which the base setting unit receives registration of a base and receives designation of master information including the group for each base, wherein the account setting unit extracts candidate accounts from the storage unit according to the account type from the group, displays and outputs them, and associates the selected account among the candidate accounts with an input person in charge for a designated base and stores it in the storage unit management method.

7. A management program for causing a computer to function as a group setting unit, an account setting unit, and a base setting unit, comprising: a step in which the group setting unit receives registration of a group and stores the group in a storage unit; a step in which the account setting unit receives registration of an account, receives designation of a group and an account type of the account, associates the account, the group, and the account type, and stores them in a storage unit; a step in which the base setting unit receives registration of a base and receives designation of master information including the group for each base, a step in which the account setting unit extracts candidate accounts from the storage unit according to the account type from the group, displays and outputs them, and associates the selected account among the candidate accounts with an input person in charge for a designated base and stores it in the storage unit management program for causing a computer to execute the process.

Images