JPH04320560A - Role managing device for computer network system - Google Patents

Abstract

PURPOSE:To provide a computer network system role managing device capable of forming system data defining system structure in a real world and relation between a role and a substance in the system structure and smoothly advancing system activity based upon the system data. CONSTITUTION:A role editing part 52 in a role management service part 5 forms system structure in a real world and system data indicating respective roles in the system structure and stores the system data in a system data base 51. A substance restricting part 53 connects respective substances to respective roles specified by the system data. A route editing part 55 forms route data indicating a connection route amoung respective roles specified by the system data and stores the route data in a route data base 54. The system data in the data base 51 and the route data in the data base 54 are properly read out and utilized for managing resources in the system in accordance with the system structure in the real world.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a role management device for a computer network system that manages resources in a computer network system so that they can be easily used within an organization in the real world.

0002

2. Description of the Related Art It is necessary to accurately classify and manage the enormous amount of resources in a computer network system, and various management methods have been proposed for this purpose. For example, when managing information as a resource, each workstation or user has its own information, and the information is managed on a workstation or user basis. In addition, the workstation or user may also access information held by other workstations as desired.
Users were given access rights to information held by other users, and by using these access rights, it was possible to collect information within the system.

0003

[Problems to be Solved by the Invention] However, although it is possible to manage information on a workstation or user basis in conventional computer network systems, this management does not clearly reflect the organizational structure of the real world. However, this may cause inconvenience when the system is used in a real-world organizational structure. For example, if you want to access and exchange information with a role in a real-world organizational structure,
If you have prior knowledge of the user who will play this role, you will be able to access the role by accessing this user, but if you do not have such prior knowledge or the user who will play this role If changed without your knowledge, you will no longer be able to access the role.

[0004] Therefore, the present invention forms organizational data that defines the real-world organizational structure and the relationships between roles and entities in the organizational structure, and uses this organizational data to make it possible to smoothly proceed with organizational activities. The purpose is to provide a role management device for a computer network system.

[0005]

[Means for Solving the Problems] In the present invention, an organizational structure and organizational data indicating respective roles in the organizational structure are stored in an organizational database, and each role indicated by the organizational data and each role in the real world is and the entities bound by the entity binding means, and resources within the system are managed based on the organization data so that the entity plays the role of the entity bound by the entity binding means.

[0006]

[Operation] According to the present invention, each role in the organizational structure is connected to each entity in the real world,
Since resources within the system are managed so that an entity fulfills its role, for example, when a role is accessed, the entity that plays this role is accessed. Therefore, even if one does not have prior knowledge of the entity that plays this role, it is possible to proceed with organizational activities smoothly.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram showing a computer network system to which an embodiment of the role management device according to the present invention is applied. In the figure, workstation 1
The computer is comprised of a central processing unit, a storage device, a keyboard, a display device, and the like. Although only one workstation is shown here, it is more common for such a system to have a plurality of workstations.

The print service section 2 records information on recording paper in response to a request from the workstation 1, and receives, for example, a document edited at the workstation and records it on the recording paper.

The communication service unit 3 is for performing data communication between the system and another computer network system (not shown) via a communication network (not shown). The directory service section 4 stores and manages the names of a large number of files storing information, the addresses of each file, etc. as a list. These addresses may point to files stored in the storage device of the system in question, or may point to files in the storage device of another system (not shown). Therefore, the directory service section 4 can access a predetermined file based on the address and read information within this file.

The role management service section 5 is for managing each role in the real world organizational structure, and includes an organization database 51, a role editing section 52, an entity binding section 53, a route database 54, and a route editing section 55. Prepared and configured.

[0012] The organization database 51 in the role management service department 5 stores organizational data indicating an organizational structure in the real world and each role in the organizational structure. Store organization data about the organization. This organizational data is given an identifier indicating the welfare section in advance, and shows a hierarchical structure consisting of a plurality of role nodes 21, 22, 23, and 24. The role node 21 corresponds to the highest role in the organizational structure, called the head of the welfare section, and includes an identifier indicating this role. The role node 22 corresponds to a role called medical affairs section chief, which is located below the welfare section chief in the organizational structure, and includes an identifier indicating this role. The role node 23 corresponds to a role called welfare section chief, which is located below the welfare section chief in the organizational structure, and includes an identifier indicating this role. The role node 24 corresponds to a role called an insurance representative located below the welfare section chief in the organizational structure, and includes an identifier indicating this role.

[0013] Also, each role node 2 in the organization data
1, 22, 23, and 24 are respectively linked to entities in the real world, for example, users of the network system are each linked as entities. That is, each role node 21, 22, 23, 24 includes a respective identifier V, W, X, Y, Z indicating each user.

Such organization data is created by the role editing section 52 and the entity binding section 53 and stored in the organization database 51. That is, the role editing unit 52 is called by the workstation 1, and when the workstation 1 specifies an identifier of organizational data, a position of a role node in a hierarchical structure, an identifier indicating a role of a role node, etc., the role editing unit 52 edits the specified content. The organization data corresponding to the organization data is created in the organization database 51. In addition, the entity binding section 5
3 is called by the workstation 1, and when the workstation 1 specifies the association between the identifier of the role node in the organizational data and the identifier of the entity, the identifier of the entity is given to the role node.

Note that if the communication service section 3 is used, the role management service section 5 can be accessed from the outside via a communication network (not shown) and the communication service section 3, and the role editing section 5 can be accessed from outside.
2 and the entity binding unit 53 can be activated to form organization data in the organization database 51.

On the other hand, the route database 54 in the role management service section 5 stores route data indicating the communication route between each role in an organizational structure in the real world. Store route data indicating the route. This route data is the type of document 31 that is processed by the organization called the Welfare Division, as shown in Figure 4.
If this occurs, this document 31 will be forwarded to the Welfare Section Manager through the Welfare Section Chief, and the Welfare Section Manager will make an approval.

[0017] Furthermore, since the Welfare Section Manager is the superior of the Welfare Section Chief, the manager may be entered in place of the Welfare Section Manager in the route data shown in Figure 3. In this case, the route data is It will look like the one shown.

Note that in the route data shown in FIGS. 3 and 5, the identifier of the document 31, the identifier of the welfare section chief, the identifier of the welfare section chief, and the identifier of the superior are actually used and substituted. A department identifier is added.

Such route data is created by the route editing section 55 and stored in the route database 54. That is, when the route editing section 55 is called by the workstation 1 and the route data shown in FIG. It is checked whether these roles exist in the data, and if these roles exist, the route data is stored in the route database 54.
to be memorized.

Note that if the communication service section 3 is used, the role management service section 5 can be accessed from the outside via a communication network (not shown) and the communication service section 3, and the route editing section 5 can be accessed from the outside.
5 can be activated to create route data in the route database 54.

In such a configuration, for example, if a document is generated in the directory service section 4 that has an identifier indicating the previous welfare section and an identifier indicating the role of the medical affairs section chief, the directory service section 4 will send the document to the role management service section 5. is called to confirm that the organization data given the identifier indicating the welfare division exists in the organization database 51, and that there is a role node 22 including the identifier of the medical affairs section chief among the role nodes in the organization data. Check. Then, the directory service unit 4 obtains the identifier W included in the role node 22 and provides the document to the user indicated by this identifier W. For example, in the case of a system in which file locations are managed for each user, if a file assigned to the user is managed by the directory service section 4, the document is stored in that file.

[0022] For example, if the communication service department 3 generates a document having an identifier indicating the welfare section and an identifier indicating the role of the welfare section chief as the destination, the communication service department 3 sends the organization data to which the identifier indicating the welfare section has been given. is in the organization database 51 of the role management service department 5, and furthermore, it is confirmed that there is a role node 23 that includes the identifier of the welfare section chief among the role nodes in the organization data. Then, the communication service unit 3 obtains the identifier X included in the role node 23, determines that the document is addressed to the user indicated by the identifier X, and stores this document in the storage area of the system in advance. stored in the user's mailbox.

Next, for example, when a document 31 of the type to be processed by the welfare section is generated in the directory service section 4, the directory service section 4 calls the role management service section 5 and displays the document 31 as shown in FIG. 3 or 5. Document 3 shown in
It is confirmed that the route data for 1 is in the route database 54, and based on this route data, it is determined that the document 31 should be given to the welfare section chief. Then, the directory service unit 4 obtains a role node 23 including the identifier of the welfare section chief from the organizational data in the organization database 51, further obtains an identifier W included in the role node 23, and sends a document to the user indicated by this identifier W. Give 31.

In this way, the document 31 is sent to the user indicated by the identifier W, that is, the user who plays the role of the welfare section chief.
is given, and then the document 31 is sent back to the communication service section 3 from the user indicated by the identifier W. The communication service section 3 confirms the user who sent the document 31, calls the role management service section 5, confirms the route data shown in FIG. 3 or 5, and sends the document 31 based on this route data. It is determined that the information should be given to the head of the welfare section. The communication service department 3 then has an organizational database 5.
Find the role node 21 including the identifier of the welfare section manager from the organizational data in 1, and find the identifier V included in this role node 21.
The document 31 is given to the user indicated by , that is, the user who plays the role of the welfare section manager.

[0025] Therefore, the document 31 in which the communication route indicated by the route data is predetermined is sequentially given to the Welfare Section Manager and the Welfare Section Manager based on the route data, even if the owner, addressee, etc. are not written therein. It happens.

[0026] In this way, in this embodiment, organizational data indicating the real-world organizational structure and each role in the organizational structure is defined, and each role is associated with an entity, so that access to the role is required. In some cases, it searches for the entity associated with the role,
Since this entity is accessed, organizational activities can proceed smoothly without knowing the entity responsible for the role. Furthermore, by defining route data indicating communication routes from one role to another, it is possible to support a series of tasks.

[0027]Although the above embodiment illustrates a one-to-one relationship in which one entity is linked to one role in an organization, the present invention is not limited to this. You may have multiple roles. For example, each role node 21, 22, 23, 24 in the organizational data of the welfare section shown in FIG. Four of the identifiers V, W, X, Y, and Z are role nodes 61, 62, and 63 in the organizational data of the disaster prevention team as shown in FIG.
, 64. In this case, the entity binding unit 53 uses four identifiers W, X, Y indicating four users.
, Z as each role node 22 in the organizational data of the welfare section,
23, 24, and the same identifiers W, X,
Y and Z are each role node 61 in the organizational data of the disaster prevention team.
, 62, 63, 64, and the respective identifiers W,
The four users given X, Y, and Z will play respective roles in the welfare department organization and the disaster prevention team organization.

Further, in the above embodiment, the directory service section 4 and the role management service section 5 are separated, but
As shown in FIG. 7, a role management service section 5 may be provided inside the directory service section 4.

[0029]

As explained above, according to the present invention, each role in an organizational structure is connected to each entity in the real world, and resources within the system are managed so that the entities fulfill their roles. Therefore, it is possible to provide a role management device for a computer network system that allows organizational activities to proceed smoothly.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing a computer network system to which an embodiment of a role management device according to the present invention is applied.

FIG. 2 is a diagram illustrating tissue data in this example.

FIG. 3 is a diagram illustrating route data in this embodiment.

FIG. 4 is a diagram used to explain the route data shown in FIG. 3.

FIG. 5 is a diagram showing another example of route data in this embodiment.

FIG. 6 is a diagram showing another example of tissue data in this embodiment.

FIG. 7 is a block diagram showing another example of the role management device according to the present invention.

[Explanation of symbols]

1...Workstation, 2...Print service department, 3
...Communication service department, 4...Directory service department, 5...
Role management service department, 51...Organization database, 52...
Role editing section, 53... Entity binding section, 54... Route database, 55... Route editing section.

Claims (2)

[Claims] 1. A role management device for a computer network system that manages respective roles in an organizational structure, comprising: an organizational database that stores organizational data indicating the organizational structure and each role in the organizational structure;
entity binding means that connects each role indicated by the organization data with each entity in the real world, and based on the organization data, the entity plays the role of the entity bound by the entity binding means. A role management device for a computer network system, characterized in that it manages resources within the system. 2. Further comprising a route database storing route data indicating a communication route between at least two roles out of a plurality of roles in the organization data, and based on the route data in the route database, the route data in the network system. The role management device for a computer network system according to claim 1, characterized in that the device transfers resources.