JP2011134190A - Directory system with organizational structure management directory, and program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a directory system that consolidates element information constituting an organization and visually represents an organizational structure from various viewpoints. <P>SOLUTION: The directory system includes a server equipped with: a means which registers definition information showing categories for classifying resources in an organization to be managed, attributes of resources belonging to the categories, hierarchy between resources in one category, and relationship between resources in different categories; a means which generates a GUI screen for inputting data on a resource; a means which registers data on the resource input on the GUI screen, in a database; and a means which visualizes an organizational structure viewed from a viewpoint selected from among a first viewpoint based on attributes, a second viewpoint based on the hierarchy, and a third viewpoint based on the relationship, on the basis of registered definition information, in a tree form or a list form. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a directory system that can visualize resources and activity states in an organization such as a department, a person, and a business from various viewpoints.

  In an enterprise, there are generally a plurality of information systems that maintain and refer to an organizational structure as information. Each information system manages the organizational structure in a form optimal for the intended business.

  With reference to FIG. 1, the conventional management method of the organization structure in a company system is demonstrated. The company system illustrated in FIG. 1 has a system A for managing organizational information of departments, a system B for managing organizational information of business projects, and organizational information of locations such as the head office and R & D center (research and development center). And a system C to be managed.

  In the case of such a database system having a configuration distributed to a plurality of systems, there is an advantage that each system can manage the organizational structure in a form optimal for the intended business and can achieve load distribution. Further, when visualizing the hierarchical structure of the organization, as shown in FIG. 1, in the A system, the organizational information viewed from the department is displayed in a tree, and in the B system, the organizational information viewed from the project is displayed in a tree. In the C system, it is possible to visualize the hierarchical structure of the organization from a unique viewpoint in each system, such as displaying the organization information viewed from the location as a tree.

  The hierarchical structure of the organization as described above can be represented by a directory tree. As a conventional information system having a function for supporting the construction of such a directory tree, for example, there is a system in which entries constituting a directory tree can be additionally registered in a query format (see, for example, Patent Document 1). Further, when the organization hierarchy is visualized, the tree is generally displayed only from the forward direction, but there is also a configuration in which the tree can be displayed from both the forward direction and the reverse direction (see, for example, Patent Document 2). In addition, an information system has been proposed in which business contents can be structurally expressed by using a business process model representing a business structure (see, for example, Patent Document 3).

JP 2007-094709 A JP 2007-257127 A JP 2006-285313 A

  As described above, in an information system for managing an organizational structure, a number of systems that can structurally represent a hierarchical structure and business contents have been proposed. However, the conventional techniques have the following problems.

Problem 1.
When trying to visually represent the structure of an organization, resources such as departments and people that make up the organization, such as a hierarchical organization perspective, a matrix organization perspective from a project, or a geographical location perspective Can be seen from various perspectives.

  In the conventional system, it is assumed that each system represents an organizational structure from a single viewpoint in accordance with the purpose of the system, and it is not assumed that the viewpoint is switched to refer to the organizational structure. However, as described above, there are various viewpoints in the organizational structure, and even if a change from one viewpoint affects another viewpoint, the change result cannot be reflected if the system is different.

Problem 2
Within an enterprise, there are a plurality of information systems that maintain and refer to the organizational structure as information. However, each information system manages the organizational structure in a form optimal for the intended business. Therefore, the result of updating the organizational structure information in one certain system is not reflected in the other systems, and each requires a maintenance operation. For example, in the system illustrated in FIG. 1, as shown in FIG. 1, for example, in System C, when Planning Department 1st Section, to which Mr. E belongs, moves to the R & D Center, System A and System B As long as maintenance operations are not performed, various troubles occur in the system A and the system B, such that the work place of Mr. E remains at the head office.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to be able to manage element information constituting an organization in an integrated manner and to change the structure of the organization in various ways. It is an object of the present invention to provide a directory system having an organizational structure management directory and a program thereof that can be visually expressed from a viewpoint. In addition, the present invention has another object to provide an external information system in various forms by a general-purpose interface including the above-described element information and relevance information representing the hierarchical relation and correlation of the element information. It is to provide a directory system and its program that can provide data.

The present invention relates to a directory system including a server having an organizational structure management directory, and a program applied to the system.
As for the system, the server determines the categories that classify the resource groups in the organization to be managed, the attributes of the resources belonging to the categories, the hierarchy between resources within the same category, and the relationships between resources in different categories. A definition information registration means for registering the definition to be defined as the definition information of the directory, and a list of resources belonging to the category selected from the list display of the category based on the definition information of the directory; A screen for generating a GUI screen for inputting resource information, attribute information, and relevance information representing a correlation with a resource belonging to a category different from the resource selected from the resource list display Generation means and data of the resource input on the GUI screen Based on the data registration means to be registered in the database and the definition information of the directory, the first viewpoint based on the attribute, the second viewpoint based on the hierarchy, and the third viewpoint based on the relationship are selected. This is achieved by including a visualization unit that visualizes the structure of the organization viewed from the viewpoint in a tree format or a list format with a desired viewpoint as a viewpoint.

Furthermore, the above object of the present invention is to
The GUI screen has a display area for displaying a list of resources belonging to the category in a tree format or a list format, and an attribute information input area for inputting attribute information of a resource selected from the resource list display And a relevance information input area for inputting relevance information representing the correlation between the resource selected from the resource list and resources belonging to other categories, and instructing addition / deletion of resources An operation button for including,
The server includes resource ID generation means for automatically generating a permanent resource ID unique in the directory system as an identifier of the resource when registering the resource information by the data registration means, and the resource ID An API for providing data in the database to an external system via a network, and associating the data in the database related to the resource ID obtained by using the API in the external system with information unique to the external system Manageable,
The server provides a GUI part including an API that can be incorporated into an external system and that can reference and update data in the database using a resource ID that specifies the resource to the external system via a network. Having a GUI parts providing means;
The server is connected via a network to an external system that operates personal information protection management that complies with privacy mark authentication standards, and the visualization means responds to a request from the external system via the API. And executing a process of visualizing the information group related to the personal information protection management distributed and managed in a plurality of databases on the external system side on the display unit on the external system side in association with the structure of the organization viewed from the viewpoint To do,
Are more effectively achieved by each.

Regarding the program, the above object of the present invention is
Definitions that represent the categories of resources in the organization to be managed by the server computer, the attributes of resources belonging to the category, the hierarchy between resources within the same category, and the relevance between resources in different categories A definition information registration means for registering as a definition information of the directory, a list of resources belonging to the category selected from the category list display based on the definition information of the directory, Screen generation means for generating a GUI screen for inputting resource information, attribute information of the resource selected from the list display, and relevance information representing a correlation with a resource belonging to a category different from the resource; The resource data entered on the GUI screen is stored in the database. Based on the data registration means to be registered in the database and the definition information of the directory, the first viewpoint based on the attribute, the second viewpoint based on the hierarchy, and the third viewpoint based on the relationship are selected. This is achieved by functioning as a visualizing means for visualizing the structure of the organization viewed from the viewpoint in a tree format or a list format from the desired viewpoint.

  According to the present invention, element information (resource group) constituting an organization can be managed in a unified manner, and the structure of the organization can be visually expressed from various viewpoints. In addition, it is possible for the user to easily register information representing resource attributes, hierarchical relationships, and correlations on the screen.

  Further, according to the invention according to claim 2, even when the constituent elements in the organization change, it is possible to change the relevant element information while confirming on the screen, personnel changes, moving, hardware resources, It becomes possible to easily cope with changes in various components such as changes in software resources.

  Further, according to the third and fourth aspects of the invention, it is possible to acquire data in various forms on the external system side, including relevance information representing the hierarchical relationship and correlation between resources in the organization. In addition, the external system can associate the organizational structure data with its own database using the resource ID, and even if the contents of the directory are updated by this system due to a change in the relationship between resources, the external system It will not be affected.

  Furthermore, according to the invention according to claim 5, it is possible to centrally manage the information group related to personal information protection management using this system, and to manage the information group related to risk management and internal control. Visualization from various viewpoints becomes possible.

It is a schematic diagram for demonstrating the conventional management method of the organization structure in a company system. It is a block diagram which shows an example of the whole structure of the directory system concerning this invention. It is a schematic diagram for demonstrating the definition of a category and resource information which concern on this embodiment. It is a flowchart for demonstrating the construction procedure of the directory which concerns on invention, and the utilization form from an external system. It is a figure which shows the structural example of the definition part showing the structure of an structure | tissue. It is a figure which shows the specific example of a category definition. It is a class diagram of a category definition. It is a figure which shows an example of a data structure of an attribute item definition. It is a figure which shows an example of a data structure of an attribute item definition set. It is a figure which shows the specific example of the definition information of an attribute item definition. It is a class diagram of attribute definition. It is a figure which shows the example of the attribute definition and the actual thing of data. It is a figure which shows an example of a data structure of a hierarchy definition. It is a class diagram of a hierarchy definition. It is a figure which shows the example of a hierarchy definition and the actual thing of data. It is a figure which shows an example of the data structure of a relevance definition. It is a class diagram of relevance definition. It is a figure which shows the example of the actual thing of a relevance definition and data. It is a schematic diagram for demonstrating a system. It is a class diagram of a category definition and resource information. It is a schematic diagram for demonstrating an example of a data input screen, and its production | generation process. It is a flowchart for demonstrating the production | generation process of a data input screen. It is a schematic diagram for demonstrating the display method of a viewpoint. It is a figure which shows the specific example of API provided by this system. It is a schematic diagram which shows an example of the production | generation method of resource ID. It is a figure for demonstrating the GUI parts which this system provides. It is a figure for demonstrating the PDCA cycle of personal information protection management. It is a figure which shows the functional requirement of systematization of personal information protection management. It is a schematic diagram which shows the utilization image of the directory from each system in a company which performs personal information protection management. It is a schematic diagram for demonstrating the function of a regulation document management system. It is a flowchart for demonstrating the process of a regulation document management system. It is a figure which shows an example of a prescription document management table. It is a schematic diagram for demonstrating the function of a personal information handling management system. It is a figure which shows a business flow diagram and a risk analysis table. It is a schematic diagram showing an example of the type of risk assumed in business It is a flowchart for demonstrating the process of a personal information handling management system. It is a figure which shows an example of a personal information ledger table. It is a schematic diagram for demonstrating the function of an incident / accident, inquiry management system. It is a flowchart for demonstrating the process of an incident / accident, inquiry management system. It is a figure which shows an example of an incident, accident, and an inquiry data table.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. First, main features of the present invention will be described.
<< About the features of the present invention >>
A system having an organizational structure management directory according to the present invention (hereinafter referred to as a “directory system”) includes an arbitrary element information group constituting an organization, such as business, department, person, building, project, information system, and product. It is a system to be managed. And it has the feature in the point provided with the means for implement | achieving the following methods.
(I) How to build a directory with organizational structure (II) How to visualize organizational structure from various viewpoints ・ Visualization of organizational structure by relationship information ・ Visualization of organizational structure by attribute information (III) Data from external system Acquisition method, general interface method for it (IV) Coordination processing method with external system ・ Cooperation with external system by GUI (Graphical User Interface) parts that can be incorporated in external system ・ Data of permanent identifier Cooperation with external systems related to management-Cooperation with external systems using API (Application Program Interface) (V) Application to external systems for the purpose of risk management and internal control Hereinafter, the entire configuration of the directory system according to the present invention After describing the above, technical matters relating to the above (I) to (IV) will be described. As for (V), a system for the purpose of personal information protection management will be described as an example in an embodiment described later.
<< Overall structure of directory system >>
FIG. 2 is a block diagram showing an example of the overall configuration of the directory system according to the present invention. In FIG. 2, the directory system includes a directory processing server device 1 (hereinafter referred to as “directory server”), and the directory server 1 and the client terminal 3 include a network 2 (electric communication line such as the Internet). Are connected to each other through communication.

  The client terminal 3 is a terminal device used by an operator to use the functions of the directory server 1 via the network 2. The client terminal 3 includes an input unit (input device such as a keyboard and a mouse) 32 for inputting various data, a control unit 31 that performs data communication with the directory server 1 via the network 2, and an output device 33 such as a display. General-purpose information processing apparatus including, for example, general information processing such as a PC equipped with a Web browser and a mobile terminal (mobile phone, PDA (Personal Digital Assistants, mobile computer such as a portable notebook personal computer)) An apparatus can be used.

  The “directory system” in the present invention refers to a host computer system including the directory server 1 in a narrow sense, but in a broad sense, a computer network system including a client terminal 3 and an external system described later. Say that. Hereinafter, the system on the host computer side including the directory server 1 will be referred to as “directory system” or “present system”.

  The directory server 1 in the present embodiment includes, for example, an organization structure management directory construction support / management server, an organization structure visualization server, and a data processing apparatus having a function as a cooperation processing server with an external system using an API. It is comprised from one or more computers provided with the control part 11 and the data storage part 12.

  The control unit 11 performs data communication with the client terminal 3 via the network 2. Further, dialogue information with the client device 3 is stored in the data storage unit.

  The data storage unit 12 is a storage unit that stores organization structure information, the above-described dialog information, a program that causes a computer to function as a means for solving the problems according to the present invention, and the like.

Information on the organization structure is stored in the following files 12a to 12b and DBs (databases) 12c to 12g.
Category definition file 12a:
This file stores definition information for each category of resources to be managed.
-Viewpoint definition file 12b:
It is a file that stores definition information about the viewpoint to be used.
Resource DB 12c:
A database in which resource information within an organization is registered.
Attribute information DB 12d:
This is a database where resource attribute information is registered.
-Hierarchical information DB 12e:
This is a database in which hierarchical information representing hierarchical relationships between resources is registered.
Relevance information DB 12f:
A database in which correlations and dependencies between resources are registered.
・ Master DB12g:
It is a database in which master data specified as attribute values is registered.

《About category definition and resource information》
Here, “category definition” and “resource information” according to the present embodiment will be described with reference to FIG.

  FIG. 3 is a schematic diagram showing an example of category definition and resource information. The Venn diagram in FIG. 3A is a concept of a set of categories, a set of resources as actual, and a resource classified by category. A subset is shown. FIG. 3B shows definition information and resource information registered in this system.

  In the example of FIG. 3A, the actual thing (actual resource) in the organization specified by the name of the department, the name of the person, the name of the building, the name of the system, etc. is “resource”. The “resource information” in FIG. 3B is composed of a permanent identifier (resource ID) unique to each resource, the name of the resource when displayed on the screen of the client terminal side, and the like. .

In this embodiment, the concept of classifying resources such as “person”, “department”, “building”, “business”, etc., constituting an organization handled by the directory is referred to as “category”. Individual resources constituting the organization belong to one category. Existence as an actual resource is called a “resource entry” or simply “entry”. Note that the term entry may refer to the actual item registered as one record in the database, so a resource entry is used when distinction is necessary.
<How to build a directory with an organizational structure>
Next, a directory construction method according to the present invention will be described.

The operation flow when building a directory according to the present invention is as follows, as shown by arrows (1) and (2) in FIG.
(1) At the time of system introduction, the hierarchical relationship, relevance, and attributes of resources are defined for each category.
(2) According to the definition of the category to which the resource belongs, the user of this system registers resource information (hierarchy information, relevance information, attribute information).

  Each resource entry is identified by a resource ID. In this embodiment, categories are stored and managed as definition files, and resource information is stored and managed in a database.

  Next, a directory construction procedure according to the present invention and a usage form from an external system will be described with reference to the flowchart of FIG. Here, the outline will be described with the operation flow as the main subject, and then the processing of the control unit 11 of the directory server will be described in detail.

<Step S1> (directory definition)
The user defines the hierarchical relationship, relevance, and attributes of resources for each category when the system is installed. Definitions can be broadly classified as shown in steps S1.1 to S1.4 in FIG. 4, the definition of “basic elements” (S1.1), the definition of “attributes” (S1.2), and the “hierarchy”. There are four types of definitions: definition of “sex” (S1.3) and definition of “relevance” (S1.4). In the present invention, a term including “hierarchy” representing a hierarchical relationship between resources in the same category and “relationship” (correlation / subordinate relationship) of resources between different categories is referred to as “relationship”. It is called.

  The “basic element” defined in step S1.1 is the most basic classification element for classifying the nature of each resource in the organization, and corresponds to the “category” described above. In step S1.1, information on the basic element (information indicating a category) is defined. Details of the definitions in steps S1.1 to S1.4, including the definition of the basic elements, will be described later with a specific example.

  The user inputs user setting information in each definition as described above on a screen using a directory definition GUI (Graphical User Interface) as definition information registration means provided by the directory server 1, and the client terminal 3 to the directory server 1 via the network 2. In this embodiment, the directory definition information set by the user is stored in the category definition file 12a in the data storage unit 12 of the directory server 1.

<Step S2> (Definition of viewpoint)
Subsequently, the user defines a “view” as a viewpoint when visualizing a group of information representing the organizational structure. The type of “view” is based on the “attribute” defined in step S1.2, the “hierarchy” defined in step S1.3, and the “relevance” defined in step S1.4. There is a viewpoint.

  The user inputs the definition information of various viewpoints (different viewpoint groups) as described above on the screen using the viewpoint definition GUI provided by the directory server 1, and from the client terminal 3 via the network 2. Transmit to the directory server 1. The viewpoint definition information set by the user is stored in the viewpoint definition file 12 b in the data storage unit 12 of the directory server 1.

<Step S3> (Data registration)
In accordance with the directory definition set in step S1, the user inputs the data of the resources in the organization (see the resource example in FIG. 3) on the GUI screen for data input, and from the client terminal 3 via the network 2. Transmit to the directory server 1. Resource data (resource information, attribute information, hierarchy information, relevance information) input by the user is stored in the resource DB 12c, attribute information DB 12d, hierarchy information DB 12e, and relevance information DB 12f in the data storage unit 12 of the directory server 1. be registered.

  By following the above steps S1 to S3, the control unit 11 automatically creates a directory database having an organizational structure based on each definition information and resource data registered by the user using the GUI screen. Built.

<Step S4> (Use from an external system)
The directory server 1 provides GUI parts that can be incorporated into an external system as interface means for using the system from an external system. In the external system, the API included in the GUI part is used to refer to and update directory data (definition information, resource information, relationship information, etc.) managed by this system.
<< About directory server processing >>
Next, the directory server process in steps S1 to S3 described above will be described. In the following description, the description already given will be omitted or simplified.

  First, the definition of the directory in the above-described step S1 will be described sequentially with specific examples.

<About the definition of basic elements (S1.1)>
As illustrated in FIG. 3, resources to be managed are classified as, for example, “person”, “department”, “building”, “information system”, and “business” and classified as categories. Any category can be defined in this system.

  As shown in FIG. 5, the definition part of the directory representing the organizational structure is composed of a basic definition part, an attribute definition part, a hierarchy definition part, and a relationship definition part.

  As shown in the example of the basic definition unit in FIG. 5, the items of the basic definition unit include a category ID, a category identification name, a category name, and the like. The category ID is an ID (identifier) for systematically identifying the category, and is automatically given by the present system when the category is registered. The category identification name is a name for systematically identifying the category, and the category name is a name (person, department, building, etc.) for displaying the category on the GUI screen.

  FIG. 6 shows a specific example of category definition (basic definition). As a category name, a name of a category for classifying resource groups in an organization to be managed, such as “person” and “department”, is defined. The As the category identification name, an English identification name is defined in this example. For example, when the category name is registered, the category name in kanji notation is automatically translated into English notation by the system, and the English notation is set as the category identification name.

  As shown in FIG. 6, the control unit 11 of the directory server 1 automatically assigns a system-specific category ID to each defined category, and stores information of the basic definition unit in the category definition file 12a.

  FIG. 7 is a class diagram of category definition, and the basic definition part that stores the category definition is associated with the other three types of definition parts (attribute definition part, hierarchical definition part, and relationship definition part), and is a data storage part. 12 is stored. The other three types of definition parts will be described in sequence below.

<About attribute definition (S1.2)>
The attribute definition will be described with reference to FIGS.

  As an attribute definition, an attribute of a resource belonging to the category is defined. Since a category has a plurality of attributes, the attribute definition is an array of attribute items that can be held.

  In the present embodiment, the attribute definition includes “attribute item definition” (see FIGS. 8 and 10) that can be shared with other categories, and “attribute item definition having an array of attribute item definitions according to a specific category. Set "(see FIG. 9).

  As shown in FIG. 8, the attribute item definition item includes an attribute ID, an attribute identification name, an attribute name, a data type, a default value, a comment, and the like.

  The attribute ID is an ID for systematically identifying the attribute item, and the attribute identification name is a name for systematically identifying the attribute item. The attribute name is a name when the attribute item is displayed on the screen, and the data type is information representing the data type of the attribute item, such as a numerical value, a character string, and a date. The default value is the value when the attribute information is omitted, and is specified if there is an initial value. The comment is an explanatory text when the attribute item is displayed on the screen.

  As shown in FIG. 9, the attribute definition set includes an attribute set ID, an attribute set identification name, an attribute set name, an attribute definition list, and the like.

  The attribute set ID is an ID for systematically identifying the attribute set (the attribute item definition shown in FIG. 8 is one set), and the attribute set identification name is a name for systematically identifying the attribute set. The attribute set name is a name used when the attribute set is displayed on the screen, and the attribute definition list is an array of attribute IDs.

  FIG. 10 shows a specific example of the definition information of the attribute item definition. An attribute ID is assigned to each attribute item definition, such as “birth date” attribute item definition and “home address” attribute item definition. The

  FIG. 11 is a class diagram of attribute definition, and FIG. 12 is a diagram showing an example of attribute definitions and actual data corresponding to FIG. As shown in FIGS. 11 and 12, the attribute definition (attribute item definition and attribute item definition set) of the resource belonging to the category includes the category definition, the actual data (attribute information and resource information registered in step S3), And stored in the data storage unit 12. In the present embodiment, when the attribute information is updated, the “state” of the corresponding DB record is invalidated and a new record (status: valid) is added.

<About the definition of hierarchy (S1.3)>
The definition of hierarchy will be described with reference to FIGS.

  As the definition of hierarchy, it is defined that resources belonging to the category have a hierarchical relationship between resources in the category. A plurality of hierarchical definitions as shown in FIG. 13 can be assigned to one category as an array.

  As shown in FIG. 13, the items of the hierarchy definition include a hierarchy ID, a hierarchy identification name, a hierarchy name, a hierarchy rank, a role name of a higher entry, a role name of a lower entry, a multiplicity of upper entries, and a lower entry. Multiplicity, upper entry attribute value restriction, lower entry attribute value restriction, and the like.

  The hierarchical ID is an ID for systematically identifying the hierarchical information and is automatically given by the present system. The hierarchical name is a name for displaying the hierarchical property such as “parent-child relationship”, “prefectural municipality”, and the like. The hierarchical order is a numerical value n (n = 0, 1,...) Indicating the hierarchical order in the category, where 1 is the first hierarchy-second hierarchy, and 2 is the second hierarchy-third hierarchy. Show. Further, when the hierarchy order is 0, the category has the same setting in any hierarchy without distinguishing the hierarchy order.

  The role name of the upper entry is a name indicating the role of the upper resource entry (for example, parent → “prefecture”), and the role name of the lower entry is a name indicating the role of the lower resource entry (for example, child → “City”).

  The multiplicity of the upper entry indicates a restriction on the number of upper entries for one lower entry, and a value of 1 to n (n is indefinite) is set. The multiplicity of the lower entry indicates a restriction on the number of lower entries for one upper entry and is set to a value of 1 to n.

  The attribute value constraint of the upper entry is set with the attribute value of the resource that can be specified in the upper resource entry, and the attribute value constraint of the lower entry is set with the attribute value of the resource that can be specified in the lower resource entry.

  As a restriction on the attribute value of the upper entry and the lower entry, for example, as a selection value of the attribute item “organization hierarchy” in the “department” category, “business department” “department” “section” “person” In this case, the following relationships are assumed as upper-lower constraints between the layers.

1st hierarchy-2nd hierarchy: "Business Division"-"Department"
1st hierarchy-2nd hierarchy: "Business Division"-"Room"
2nd hierarchy-3rd hierarchy: "Department"-"Section"
3rd layer-4th layer: "section"-"person in charge"
Omit this when there is no hierarchy restriction. It is possible to create multiple definitions with the same hierarchical order. In addition, attribute values can be constrained at multiple levels. For example, in addition to the above example, the first hierarchy-second hierarchy: "business division"-"section" can be used.

  FIG. 14 is a class diagram of the hierarchy definition, and the hierarchy definition of resources (resource information 2) belonging to the category is stored in the data storage unit 12 in association with the hierarchy information, the category definition, and the resource information. . As the hierarchy information, a resource ID of a higher resource, a resource ID of a lower resource, a display order, and the like are set.

  FIG. 15 shows examples of hierarchical definition and actual data corresponding to FIG. 14, and when the category is a department, as shown in FIG. Are expressed by a hierarchy definition.

  The directory server 1 stores the defined hierarchy definition in the data storage unit 12 in association with the hierarchy information and the category definition.

<About definition of relevance (S1.4)>
The definition of relevance will be described with reference to FIGS. 16 to 18.

  As the definition of relevance, it is defined that a resource belonging to the category has a relevance with a resource belonging to another category. A plurality of association definitions as shown in FIG. 16 can be assigned to one category as an array.

  As shown in FIG. 16, the items of relevance definition include relevance ID, relevance identifier, relevance name, parent category ID, child category ID, relevance name, role name of parent category, and role of child category. It consists of the name, the multiplicity of the parent category, the multiplicity of the child category, and the like.

  The relevance ID is an ID for systematically identifying the relevance and is automatically given by the system. The relevance identifier is a name for systematically identifying the relevance, and the relevance name is a name for displaying the relevance on the screen. The parent category ID is the category ID of the main category of the two categories to be associated, and the child category ID is the category ID of the subordinate category of the two categories to be associated. The name of the relationship expresses how to relate, for example, “belongs to”. The role name of the parent category is the role name of the main category in the relationship, and the role name of the child category is the role name of the subordinate category in the relationship. The multiplicity of the parent category indicates the restriction on the number of entries in the parent category for one entry in the child category, and a value of 1 to n is set. The multiplicity of the child category indicates a restriction on the number of entries in the child category for one entry in the parent category, and a value of 1 to n is set. In the tree-like view, the parent and the child here are the main element as the parent and the subordinate element as the child. For example, when a person is associated with a department, the department is the parent and the person is the child.

  Note that, as shown in the items No. 10 and No. 11 in FIG. 16, it is also possible to provide attribute value constraints (parent category attribute value constraints, child category attribute value constraints). In this case, the attribute value of the resource that can be specified in the upper resource entry is set as the attribute value constraint of the parent category. The attribute value of the resource that can be specified in the child resource entry is set as the attribute value constraint of the child category.

  FIG. 17 is a class diagram of the relationship definition. The relationship definition of the resource (resource information 2) belonging to the category is stored in the data storage unit 12 in association with the relationship information, the category definition, and the resource information. . As the relevance information, a resource ID, an associated resource ID, a display order, and the like are set.

  FIG. 18 shows an example of the relationship definition and the actual data, corresponding to FIG. 17. When a department, person, or building is defined as a category, for example, a resource belonging to the first category (department) ( In this example, the relationship between the first salesperson in the business) and the resource (actual person) belonging to the second category (person), the resource belonging to the first category (department) (the first salesperson in this example) and the third category The relevance with resources (head office building etc.) belonging to (building) is expressed by the relevance definition.

  The directory server 1 stores the defined relationship definition in the data storage unit 12 in association with the relationship information and the category definition.

<About category definition and resource information>
FIG. 19 is a class diagram of category definition and resource information. As shown in FIG. 19, the category definition is associated with other definitions (attribute item definition (set), hierarchical definition, and relationship definition data). And stored in the data storage unit 12. Further, as shown in FIG. 19, the resource information is associated with each definition information (category definition information, attribute information, hierarchical information, relevance information) and stored in the data storage unit 12. As described above, the attribute item definition is a definition that can be shared with other categories, and the attribute item definition set is a definition corresponding to a specific category including an array of attribute item definitions.

<Process relating to definition of view (S2)>
The processing relating to the definition of the visual point will be described with a specific example in the description of “2.

<Processing related to data registration (S3)>
The processing related to data registration will be described with a specific example in the description of “1. Generation processing of GUI screen for data input” described later.

<Processing related to use from external system (S4)>
Processing related to use from the external system will be described with a specific example in the description of “3. API and GUI parts provided to external system” described later.
<Data input GUI screen generation process and viewing method>
Next, a process for generating a GUI screen for data input and a method for displaying a viewpoint in the directory system according to the present invention will be described in order.
<< 1. Generation process of GUI screen for data input >>
First, generation processing of a data input GUI screen will be described.

In the present embodiment, the control unit 11 automatically creates a GUI screen for data input for the category based on the category definition. At that time, if the hierarchical relationship is defined, the control unit 11 displays the entire resource in a tree shape, and if the correlation with other categories is defined, the resource selection screen of the corresponding category Is displayed. The selection screen is displayed in the following format depending on the category definition.
(Display form 1) Displayed in a tree form by hierarchical information (Display form 2) Sorted by attribute values and displayed in a tree form (Display form 3) Displayed as a flat list with no classification In addition, the control unit 11 selects a user When an operation is accepted, a selection conflict such as a hierarchical relationship or a correlation conflict between the selected resource and another is detected.

  Hereinafter, a process for generating a GUI screen for data input will be described in detail with reference to the drawings.

  FIG. 20 is a schematic diagram for explaining an example of a GUI screen for data input and generation processing thereof. In FIG. 20, symbol G10 indicates an example of a GUI screen for data input (hereinafter referred to as “data input screen”), and G10M indicates an example of a template screen that is a template of the GUI screen. Reference numeral G1 indicates an example of a system menu screen, and reference numeral G2 indicates an example of a resource management screen on which a category list is displayed.

  As shown in the template screen G10M, the screen configuration of the data input screen G10 includes a “resource list display area”, “basic information input area”, “attribute information input area”, and “relevance information input area”. Is done. In addition, the data input screen G10 is provided with a “topic path area” for indicating the current page position in the Web page and a “window title area” for displaying the title of the data input window.

  In the “Resource List Display Area”, as shown in the example of the data input screen G10, the resource names of resource entries belonging to the category (resource entries in which resource information is registered) can be scrolled in a tree format or list format It is an area displayed in a list.

  The “basic information input area” is an area for inputting basic information of a resource entry to be registered, such as the name of a resource entry for registering data, and belongs to the category (department) in the example of the data input screen G10. An example in which the name of a resource entry (business section) is entered is shown.

  The “attribute information input area” is an area for inputting attribute information of the resource entry input in the basic information input area, and the “relevance information input area” is a resource entry belonging to the resource entry and another category. This is an area for inputting relevance information representing the correlation with the. In the example of the data input screen G10 of FIG. 20, the “attribute information input area” includes attribute items (“address”, “phone number”, etc.) defined in the attribute definition of the selected category (“department”). ) Is displayed, the user inputs attribute information for each item. In the “relevance information input area”, as a relevance item defined in the relevance definition of the selected category (“department”), an item of the resource entry belonging to the category (“jurisdiction” ) And resource entry items belonging to other categories ("Members") are displayed, the user inputs information for each item.

  In the screen configuration as described above, the control unit 11 of the directory server 1 defines the category selected from the category list on the resource management screen G2 (category definition, attribute definition, hierarchy definition, relationship definition). Based on the above, a screen element is arranged in each area of the template screen G10M, and a data input screen G10 for the category is automatically created. At this time, if there is existing data, the data is expanded to a predetermined location. Of the dynamically changing areas, the topic path area is a part that changes according to the selection in the release list, and is irrelevant to the category definition.

  Next, details of the generation process of the data input screen G10 will be described with reference to the flowchart of FIG.

  When the user logs in to the system, the control unit 11 (the control unit of the directory server 1) displays, for example, the menu screen G1 illustrated in FIG. 20 on the client terminal 3 side. When the user selects a data input menu (resource management in FIG. 20) on the menu screen G1 (step S11), the control unit 11 displays the category definition definition information set in step S1.1. Obtained from the category definition file 12a (step S11a), a resource management screen G1 including an image of the category list is generated and displayed on the client terminal 3 side (step S11b), and the user is prompted to select a category.

  When a category is selected from the category list on the resource management screen G1 (step S12), the control unit 11 defines the selected category definition information (category definition, attribute definition, hierarchy definition, relationship definition). Each definition information) is acquired from the data storage unit 12 (step S12a), and it is determined whether or not there is a hierarchical relationship (step S12b).

  If it is determined in step S12b that there is a hierarchical relationship, the control unit 11 acquires hierarchical information (hierarchical data such as hierarchical name and hierarchical order included in the hierarchical definition) from the hierarchical information DB 12e ( Step S12c), resource entries are displayed in a tree format in the resource list display area of the data input screen G10. For example, the example of FIG. 20 shows an example in which “department” is selected as the category. In this case, a tree-like image showing the hierarchical structure of the department is generated based on the data of the hierarchy definition of the department. Then, the image is displayed in the resource list display area (step S12d). On the other hand, if it is determined in step S12 that there is no hierarchical relationship, the resource entry is displayed in the resource list display area in a list format (step S12e).

  When a resource entry is selected from the resource list (step S13), the control unit 11 acquires attribute information of the selected resource entry from the attribute information DB 12d based on the attribute definition (step S13a), Based on the sex definition, the relevance information of the selected resource entry is acquired from the relevance information DB 12f (step S13b). Then, an attribute value input area (code, address, telephone number, and FAX number input areas in the example of FIG. 20) is generated from the attribute definition and the image is displayed on the data input screen G10 (step S14a). Then, a relevance input area (in the example of FIG. 20, in the example of FIG. 20, each registrar's business area, each person's belonging area) is generated and its image is displayed on the data input screen G10 (step S14b).

  In this state, when the “Add” button for relevance (“Add business” button, “Add person” button in the display example of the screen G10 in FIG. 20) is pressed (step S15), the control unit 11 Displays a screen G11 for selecting the resource of the corresponding relevance category. The example of FIG. 20 shows an example when the “add business” button is pressed, and a business selection screen G11 is displayed as shown by an arrow A in FIG. At that time, the control unit 11 displays the screen so that the business to be added input in the relevance information input area (in the example of FIG. 20, the “truck transportation business” portion is displayed in the approximate center of the resource list display area. The G11 window is popped up (step S15a), and the resource entry selected from the resource list is held, and data input is awaited (step S15b).

  In step S15, the user inputs basic information (resource information), attribute information, and relevance information data of the resource entry, and presses the “Register” button (step S16).

  In step S <b> 16, when the “Register” button is pressed, the control unit 11 registers the data input by the user in the database in the data storage unit 12. In this example, resource information is registered in the resource DB 12c, attribute information is registered in the attribute information DB 12d, and relevance information is registered in the relevance information DB 12f (step S16a).

  When the user wants to newly register (add) a resource entry, the “add” button (in the example of FIG. 20) of the resource entry (the resource entry or the resource entry of the relevance category) in step S14 or step S15. Press the "Add department" button at the bottom of the resource list.

  The control unit 11 determines whether or not a resource entry has been added based on the operation information of the “add” button (step S16b). If it is determined that the resource entry has been added, it is selected by the user in step S14 or step S15. The hierarchical information with the higher resource entry is registered in the hierarchical information DB 12e, and the data registration process for the resource entry is terminated.

  When the user wants to delete a resource entry, select the resource entry to be deleted from the resource list and press the “Delete” button. In that case, the control unit 11 logically deletes the selected resource entry and ends the deletion process of the resource entry.

  As described above, the control unit 11 displays a list of categories on the display unit of the client terminal 3 based on the definition information of the directory, and displays a list of resources belonging to the category selected from the list display. In addition, “resource information” and “attribute information” of the resource selected from the list display, and “relevance information” indicating the correlation with the resource belonging to a category different from the resource are input. “Screen generation means” for generating a GUI screen is provided.

  The GUI screen is a constituent element of “data registration means” for registering data input on the screen in a corresponding database in the data storage unit 12, and the GUI screen belongs to the category as described above. It is selected from a display area for displaying a list of resources in a tree format or a list format, an attribute information input area for inputting attribute information of a resource selected from the resource list display, and a resource list display. A relevance information input area for inputting relevance information representing the correlation between the resource and a resource belonging to another category, and an operation button for instructing addition / deletion of the resource. Yes.

As a result, the user can easily register information representing the hierarchical relationship and correlation between the resources of the resource, and the contents of the resource can be easily changed and added / deleted. In other words, it is possible to easily change the related element information on the same screen even when the components in the organization change, such as personnel changes, moving, changes in hardware resources and software resources. Further, the screen generation means dynamically changes the tree-format display on the screen according to the operation of adding or deleting resources on the GUI screen. Therefore, the user can make changes while confirming the changed contents on the screen.
<< 2. Viewpoint display method >>
Next, a method for displaying the seat will be described.

  First, the definition of the viewpoint will be described with reference to the example of the viewpoint definition in FIG.

  As the definition of the viewpoint, a definition having contents as shown in FIG. 22 is performed for the viewpoint to be used. In this example, the definition of the sight is composed of a common part, a definition part of the sight based on attributes, a definition part of the sight based on hierarchy, and a definition part of the sight based on relevance.

  As shown in FIG. 22, the common part items include a seat ID (an ID for systematically identifying the seat), a seat identification name (a name for systematically identifying the seat), and a seat name (for the seat). Is displayed on the screen), display shape (list shape or tree shape), visual point type, and the like. In this embodiment, there are three types of seat types: (type 1) a seat based on attributes, (type 2) a seat based on hierarchy, and (type 3) a seat based on relevance. Note that these seat types are effective when the display shape is a tree shape.

  The item “definition part of a viewpoint based on attributes” includes a category ID (an ID of a category displayed on the viewpoint), an array of attribute IDs, and the like.

  The array of attribute IDs is classified according to attribute values in order from the first hierarchy, but the attribute IDs of attributes used for classification are designated by the array in order from the first hierarchy.

  The item “definition part of the viewpoint based on hierarchy” includes a category ID, the depth of the hierarchy (the depth of the hierarchy displayed on the viewpoint), and the like. The category ID defined here is the category ID of the subordinate category of the two categories to be associated. As the depth of the hierarchy, a numerical value m indicating the depth (for example, m = 3 in the case of 3 hierarchy) is designated. If you want to display all levels, specify "0".

  The item “definition part of sight based on relevance” includes a relevance ID, a depth of a hierarchy (a depth of a hierarchy displayed on the sight), and the like. The display of the viewpoint based on the relevance displays a plurality of categories (two different categories in this example) in association with each other, and designates a relevance ID that defines the relevance. When the parent category has a hierarchy, the depth of the hierarchy can be limited. The treatment of the “numerical value m” indicating the depth is the same as the “numerical value m” in the definition part of the viewpoint based on the hierarchy.

  Next, an operation example of the control unit 11 related to the display of the visual point will be described with reference to examples of display images VP1 to VP3 in FIG.

  In accordance with the definition of the viewpoint as described above, the control unit 11 acquires resource entries belonging to the category from the database for one or two types of categories, and displays the structure information of the organization viewed from the viewpoint as a tree (or list) Image) is generated, and as shown in the display images VP1 to VP3 in FIG. 22, an image representing the tissue structure viewed from the viewpoint is displayed on the display unit on the client terminal 3 side. .

  When generating the image data, the control unit 11 determines the configuration of the tree by referring to the corresponding definition unit (the definition unit in FIG. 22 corresponding to the specified seat type) according to the seat type specification. To do. For example, if the seat type is designated as type 1 (the seat based on the attribute), it is classified according to the attribute value and displayed in a tree shape. Specifically, in this example, the array data of the attribute ID corresponding to the category ID is obtained from the definition unit of the viewpoint, the tree structure is determined based on the array data, and the attribute name corresponding to the attribute ID is determined. They are arranged in a tree shape to generate tree format image data.

  On the other hand, if the designation of the viewpoint type is type 2 (the viewpoint based on hierarchy), hierarchy information, that is, hierarchy name, hierarchy rank, role name of upper entry, role name of lower entry, multiplicity of upper entry, A tree structure is determined based on hierarchical information such as multiplicity of lower entries (see FIG. 13), and hierarchical names, role names of upper entries, role names of lower entries are arranged in a tree shape, and an image in a tree format Generate data.

  Further, if the designation of the viewpoint type is type 3 (the viewpoint based on relevance), relevance definition information (relevance data such as relevance name, multiplicity of parent category, multiplicity of child category, etc.): The structure of the tree is determined based on the reference), the relevance name, the role name of the upper entry, and the role name of the lower entry are arranged in a tree shape to generate image data in a tree format.

Further, when generating the image data, the control unit 11 refers to the definition information of the visual point to determine whether or not the designation of the display shape is a tree shape, and the depth of the hierarchy displayed in the tree shape and on the screen When the specified value m of 1 is 1 or more, by generating image data with the hierarchy up to the specified value “m” as a display target, there is an entry for a hierarchy lower than the specified value (a hierarchy lower than the m hierarchy). Do not display even if there is. When the display shape is specified in a tree shape and the specified depth m = 0, the entire hierarchy is displayed on the screen by generating image data for the entire hierarchy. In addition, when an image representing an organizational structure cannot be displayed on one screen, display control is performed so that scroll display is possible according to an operation on the client terminal side.
(Specific display examples of organizational structure from different perspectives)
The example of the display image VP1 in FIG. 22 is a display example when the tissue structure is visualized from the viewpoint based on the attribute. In this example, “Information system” is the display target category, and “Operating environment”, which is one element of the attribute (operating environment, vendor, etc.) belonging to “Information system”, is viewed from the operating environment. It is the example which visualized the composition of the information system group. As shown in the example of the display image VP1, in this example, the mainframe, Web server, C / S (client / server), and the like are set as the “operating environment”. For example, when operating environments are classified into a plurality of types and managed, if they are defined in a plurality of attributes such as the first operating environment, the second operating environment, and the third operating environment, each attribute is The system configuration as a viewpoint is visualized.

  The example of the display image VP2 in FIG. 22 is a display example when the organizational structure is visualized from a viewpoint based on the hierarchy (hierarchical relationship between resources in the same category). In this example, “business” is set as a display target category, and the configuration of the business group viewed from the viewpoint using the hierarchy is visualized. As shown in the example of the display image VP2, the business hierarchy (in this example, the business configuration of each business is visualized in a tree format for each business type.

  The example of the display image VP3 in FIG. 22 is a display example when the tissue structure is visualized from a viewpoint based on relevance. In this example, “Department” is a display target category, and an organization structure viewed from a viewpoint using the relationship with the category “Person” having the category “Department” as a parent is visualized. In addition, any two categories of a predetermined category group defined by the user, such as a department, a person, a building, an information system, and a business, can be visualized in association with each other. In the visualization method of the organizational structure based on the viewpoint based on the relevance, it becomes possible to visualize the correlation and dependency between resources belonging to different categories in a tree format or a list format.

  In this example, the display images VP1 to VP3 in FIG. 22 are individually switched and displayed in response to a display request from the client terminal, but display images viewed from a plurality of different viewpoints are displayed on the screen. It is good also as a form which arrange | positions to each display window and visualizes the tissue structure seen from several viewpoints on the same screen.

As described above, based on the directory definition information (and view definition information), the control unit 11 includes a first view based on attributes, a second view based on hierarchy, and a third view based on relevance. “Visualization means” that visualizes the structure of the organization viewed from the viewpoint in a tree format or a list format with the desired viewpoint selected from the viewpoint as a viewpoint, so that the structure of the organization can be expressed from various viewpoints.
<< 3. About API and GUI parts provided to external systems >>
Next, “API” and “GUI part” provided as means for linking processing with an external system will be described. First, an API provided to an external system will be described.

(About APIs provided to external systems)
FIG. 23 is a diagram showing a specific example of an API provided by this system. In this example, 16 types of methods are prepared as methods. The type of method and the parameters and return values of each method are as shown in FIG.

  When the method is “acquire attribute definition”, the attribute item definition of the return value is included in the attribute item definition set of the corresponding category. When the method is “resource list”, basic information is returned for all resources of the corresponding category. In addition, when the method is “list of resources of the designated view”, basic information is returned for all resources of the corresponding category. When the method is “extract resource of specified view”, information of the resource having the specified resource ID at the upper level is returned. In this case, there are two types of category IDs of return values: ID of parent category and child category of relevance in view.

  The directory server 1 provides an API as illustrated in FIG. 23 as a library in Java (registered trademark) language and a Web service. Also, API definitions are published in WSDL (Web Services Description Language) on the Web site of this system.

  In the external system, definition information, resource information, and relationship information managed by this system can be acquired according to the API defined in advance.

(About data management using persistent identifiers)
Here, management of resource entry data using resource IDs will be described. This system includes “resource ID generation means” that automatically generates a resource ID that is a unique permanent identifier in the system as an identifier of each resource, and the above-described API means. The resource ID generation means generates a resource ID when registering a resource entry. The uniqueness of the resource ID assigned to the resource is guaranteed permanently.

  The resource ID can be identified from the resource ID regardless of the category. Further, the external system can access the resource information of this system by using the resource ID.

  FIG. 24 is a schematic diagram illustrating an example of a method for generating a resource ID, and the resource ID generating unit generates a resource ID when registering a resource entry, as shown in FIG. In this example, the “CREATE SEQUENCE” function supported by the DBMS (DataBase Management System) is used to generate a resource ID, but a similar sequence number generation mechanism may be implemented.

In the external system, the resource ID is acquired by the API provided by this system. Specifically, for example, each category ID is acquired by the “category list acquisition method” illustrated in FIG. 23, and each resource ID of the resource group belonging to the category is acquired by the “resource list method” using the category ID as a parameter. For each category ID. Alternatively, the resource ID of the resource selected in the resource list displayed on the screen is acquired using a GUI part described later. The information unique to the external system is managed in association with the data in the data storage unit 12 acquired by the resource ID and API. As a result, the external system can associate the organizational structure data with its own database, and even if the contents of the directory are updated by this system due to changes in the relationship between resources, the external system is not affected. It will be.
(GUI parts provided to external systems)
Next, GUI parts provided to the external system as the API means described above will be described.

  The directory server 1 can be incorporated into an external system, and can use the resource ID to refer to and update data in the data storage unit 12 (information related to the resource ID such as directory definition information and view definition information). “GUI part providing means” for providing a GUI part including a possible API to an external system via a network is provided.

In the directory server 1, GUI parts that can be used in the external system are incorporated in the HTML frame, and the resource ID of the resource selected by the system user in the resource list as shown in FIG. 25 is the server (DBMS) of the external system. To Java Script via Java Script. In the external system, information related to the resource ID is referred to, and information is input / updated.
《Examples of application to external systems for risk management and internal control》
Next, an external system using this system will be described.

Hereinafter, an information system (hereinafter referred to as a “personal information protection management system”) that uses the present system to operate personal information protection management conforming to the privacy mark certification standard (JISQ15001) will be described as an example.
[Example] Personal information protection management system using this system First, privacy mark authentication standards will be described.

  In JISQ15001: 2006 (Personal Information Protection Management System / Requirements), it is necessary to turn the PDCA cycle (Plan-Do-Check-Act cycle) as shown in Fig. 26. ), Do (Implementation), Check (Check), Act (Review), how to implement the functions required in each phase using the directory of this system. In FIG. 26, portions A) to E) are elements that can be systematized.

  FIG. 27 shows functional requirements for systematization of personal information protection management. In FIG. 27, functional requirements A to E indicate functional requirements when the elements A to E in FIG. 26 are systematized, and line items indicate portions that directly overlap with the requirements of JISQ15001. .

  Among the requirements of the P mark system based on the requirements of JISQ15001: 2006 as mentioned above, the specified document management function (functional requirement A), (2) personal information handling management function (functional requirement B), and (3) Regarding the three functions of the incident / accident and the inquiry management function (functional requirements C and D), FIG. 28 shows the usage image of the directory from each system that realizes each function.

  FIG. 28 describes a method of using directory information for each of the three functions of the P mark system. Hereinafter, how to implement the functions required in each phase of the PDCA cycle using the directory of the present system will be described using the three systems 21 to 23 shown in FIG. 28 as specific examples.

  The directory system 1 is connected via a network to external systems 21 to 23 that operate personal information protection management that complies with privacy mark authentication standards. Then, the directory system 1 collaborates with the external systems 21 to 23 via the aforementioned API or GUI parts, and in response to a request from the external system side, a plurality of the external systems 21 to 23 side. The information group related to the personal information protection management distributed and managed in the databases 21a to 23a is associated with the structure of the organization viewed from the viewpoint, and a process of visualizing the information on the display unit on the external system side is executed. In addition, on the external system 21 to 23 side, a group of information related to personal information protection management that is distributed and managed can be centrally managed using resource IDs.

  In the following description, the system 21 that realizes the regulation document management function is called “regulation document management system”, and the system 22 that realizes the personal information handling management function is called “personal information handling management system”. The system 23 for realizing the inquiry management function is referred to as “incident / accident, inquiry management system”, and the systems 21 to 23 will be sequentially described for each system.

<Regulation document management system 21>
First, the regulatory document management system 21 will be described.

First, the requirements of JISQ15001 regarding the regulation document management, and the purpose and function of the system for the requirements will be explained.
(Requirements)
Establish rules for your organization based on laws, national guidelines and other standards. In accordance with the regulations, handle personal information and keep records.
(Purpose document management system purpose and function)
Manage rules documents in association with business. Therefore, if a GUI part of a viewpoint having a department-business relationship is incorporated from the directory and a business (personal information protection management) is selected from the viewpoint, a list of related regulation documents is displayed. Displays the contents of the document selected from the list.

FIG. 29 is a schematic diagram for explaining the function of the regulation document management system 21. The regulation document management system 21 incorporates a GUI part (GP) provided by the system, and uses the API (see FIG. 23) included in the GUI part (GP) to perform the following processing to cooperate with the system. It is set as the form provided with.
(1a) Job name list display function As shown in the example of the image VP1-1 in FIG. 29, jobs classified by department are displayed on the screen 21.
(1b) Regulation document list display function As shown in the database 21a in FIG. 29, the regulation documents are classified and classified into regulation texts, formats, business flow diagrams, risk analysis tables, etc. As shown in the example of the image VP1-2, the name of the regulation document is listed in a tree shape for each classification, and the list is displayed on the screen 21.
(1c) Regulation document display function When the user selects a document from the regulation document list and clicks the “document display” button, the selected document 21D is displayed on the screen 21.
(1d) Regulation document registration function Registers regulation documents and manages them in association with business operations.
(Processing flow of the regulation document management system 21)
FIG. 30 and FIG. 31 show the processing flow and main data items (specified document management table) of the part where the regulation document management system 21 uses the external interface of the directory.

  The processing related to “regulation document list display” is a flow shown in steps S21 to S24 in FIG. That is, first, display processing of the GUI part of the department-business tree is executed (step S21), and the resource ID of the selected business is acquired (step S22). Subsequently, a list of job = resource ID (document classification, document name, regulation document ID) is acquired from the regulation document table (see FIG. 31) (step S23), and the document names are sorted and displayed by document classification (listed). Step S24).

  The process relating to “regulatory document registration” has a flow shown in steps S31 to S33 in FIG. That is, the resource ID of the selected job is acquired (step S31), and the document registration screen is displayed (step S32). Then, a record is added to the regulation document table based on the input contents on the document registration screen (step S33).

<Personal information handling management system 22>
Next, the personal information handling management 22 will be described.

First, the requirements of JISQ15001 regarding personal information handling management, and the purpose and function of the system corresponding to the requirements will be described.
(Requirements)
When acquiring new personal information, clarify the contents and purpose of the acquired personal information. Also, assess the business risks associated with obtaining personal information.
(Purpose and function of personal information management system)
The person in charge of business registers necessary information and requests the approval of the person in charge of business and the person in charge of personal information protection management.

FIG. 32 is a schematic diagram for explaining the functions of the personal information handling management system 22. The personal information handling management system 22 is configured to have the following functions by cooperating with the system using a GUI part (GP) provided by the system.
(2a) Personal Information Ledger Management Function The personal information is managed in the database 22a as a ledger 22D.
(2b) Function for registering personal information for income Referring to the business list VP2-1 in the directory, the business is associated with the personal information to be acquired on the screen VP2-2 in FIG.
(2c) Business flow diagram creation function A flow diagram of business procedures for handling personal information.
(2d) Risk analysis function Analyzes procedural risks based on a business flow diagram and creates a risk analysis table.
(2e) Creation / Storage Function of Approval Workflow The approval workflow 22D2 for obtaining approval on the system is created for the contents handling personal information.

  The business flow diagrams and risk analysis tables (2c) and (2d) will be described with reference to FIGS. 33 and 34. FIG. FIG. 33 is a schematic diagram illustrating an example of a business flow diagram (a diagram including a risk analysis table), and FIG. 34 is a schematic diagram illustrating an example of risk types assumed in business.

  As shown in FIG. 33, the business flow diagram is created by converting the procedure for handling personal information into collection, storage, use, destruction, and external work (consignment / consignment / provision).

The risk analysis table is created by selecting an assumed risk from the risk types as shown in FIG. 34 at each step of the business process indicated by the business flow. In the example of the business flow diagram of FIG. 33, the business flow and the risk analysis table are shown corresponding to each business element.
(Processing flow of personal information handling management system 22)
FIG. 35 and FIG. 36 show the processing flow of the part using the external interface of the personal information handling management system 22 directory and the main data items (personal information ledger table). The process from the acquisition of the business name to the approval application is a flow shown in steps S41 to S46 in FIG. That is, first, GUI part display processing of a business tree is executed (step S41), the resource ID and business name of the business selected on the screen VP2-1 of FIG. 32 are acquired (step S42), and the business name is changed. It is displayed on the screen VP2-2 (step S43). Subsequently, registration processing of personal information acquisition application data is executed (step S44), and after registration of the business flow diagram and risk analysis table in the regulation document table (step S45), approval application processing is executed (step S46).

<Incident / accident, inquiry management system 23>
Next, the incident / accident / inquiry management system 23 will be described.

First, the requirements of JISQ15001 regarding incident / accident and inquiry management, and the purpose and function of the system for the requirements are explained.
(Requirements)
If there are any inquiries or incidents / accidents from the person concerned about the collected personal information, the contents are registered, the response contents are recorded, the current process is checked, and corrections are made.
(Case and accident, purpose and function of inquiry management system)
The person in charge of business registers necessary information and requests the approval of the person in charge of business and the person in charge of personal information protection management.

FIG. 37 is a schematic diagram for explaining the functions of the incident / accident / inquiry management system 23. The incident / accident / inquiry management system 23 uses the GUI parts (GP) provided by the present system and performs processing in cooperation with the present system to provide the following functions.
(3a) Case / Accident / Inquiry Ledger Management Function Information related to cases / accidents / inquiries is managed in the database 23b as a ledger 23D1.
(3b) Case / Accident / Inquiry Registration Function By selecting the target personal information, information on the business, the department in charge, the person in charge, etc. associated with the personal information is acquired.
(3c) Approval workflow creation / storage function Creates an approval workflow 23D2 for obtaining approval on the system for the contents of incidents / accidents and inquiries.
(Processing flow of incident / accident, inquiry management system 23)
FIG. 38 and FIG. 39 show the processing flow and the main data items (incident / accident, inquiry data table) of the part where the incident / accident / inquiry management system uses the external interface of the directory.

  The process from the display of the personal information selection screen to the approval application is as shown in steps S51 to S57 in FIG. That is, first, display processing of the personal information selection screen is executed (step S51), the personal information ID of the personal information selected on the screen VP3-1 of FIG. 37 is acquired (step S52), and the personal information acquisition application is acquired. A corresponding record corresponding to the personal information ID is acquired from the data table (step S53). Subsequently, the business name is acquired from the business ID (step S54), and the business name is displayed on the screen VP3-2 (step S55). Then, after additionally registering a record in the incident / accident / inquiry data table (see FIG. 39) based on the data input on the screen VP3-2 (step S56), an approval application process is executed (step S57). .

DESCRIPTION OF SYMBOLS 1 Directory server 2 Network 3 Client terminal 11 Control part 12 Data storage part 12a Category definition file 12b Perspective definition file 12b
12c Resource DB 12c
12d attribute information DB 12d
12e Hierarchical information DB 12e
12f Relevance information DB12f
12g Master DB
G1 system menu screen
G2 resource management screen
G10 data entry screen
G10M template screen
VP1 Organizational structure display image (image captured from attribute-based viewpoint)
VP2 Organizational structure display image (image taken from a perspective based on hierarchy)
VP3 Display image of tissue structure (image taken from the viewpoint based on relevance)
GP GUI parts 20 External system (P mark system)
21 Regulation document management system 21a Regulation document DB
22 Personal Information Handling Management System 22a Personal Information Ledger DB
23 Incident / accident, inquiry management system 23a Incident / accident, inquiry information ledger DB

Claims (6)

A directory system comprising a server having an organizational structure management directory,
The server
The directory definition includes a category that divides a group of resources in the organization to be managed, attributes of resources belonging to the category, a hierarchy between resources within the same category, and a definition that indicates the relationship between resources in different categories. Definition information registration means for registering as information,
Based on the definition information of the directory, a list of resources belonging to the category selected from the category list display is displayed, and resource information and attribute information of the resource selected from the resource list display , And screen generation means for generating a GUI screen for inputting relevance information representing a correlation with a resource belonging to a category different from the resource,
Data registration means for registering the data of the resource input on the GUI screen in a database;
Based on the definition information of the directory, the viewpoint is a desired viewpoint selected from the first viewpoint based on the attribute, the second viewpoint based on the hierarchy, and the third viewpoint based on the relationship. Visualization means for visualizing the structure of the organization viewed from a tree format or a list format;
A directory system comprising:   The GUI screen has a display area for displaying a list of resources belonging to the category in a tree format or a list format, and an attribute information input area for inputting attribute information of a resource selected from the resource list display And a relevance information input area for inputting relevance information representing the correlation between the resource selected from the resource list and resources belonging to other categories, and instructing addition / deletion of resources A directory system comprising: an operation button for: The server
Resource ID generation means for automatically generating a permanent resource ID unique in the directory system as an identifier of the resource when registering the resource information by the data registration means, and data in the database including the resource ID An API that provides the external system via a network, and the data in the database related to the resource ID obtained by using the API in the external system and information unique to the external system can be managed in association with each other The directory system according to claim 1, wherein the directory system is a directory system.   The server provides a GUI part including an API that can be incorporated into an external system and that can reference and update data in the database using a resource ID that specifies the resource to the external system via a network. The directory system according to claim 1, further comprising a GUI part providing unit.   The server is connected via a network to an external system that operates personal information protection management that complies with privacy mark authentication standards, and the visualization means responds to a request from the external system via the API. And executing a process of visualizing the information group related to the personal information protection management distributed and managed in a plurality of databases on the external system side on the display unit on the external system side in association with the structure of the organization viewed from the viewpoint The directory system according to claim 3 or 4, characterized in that: A program applied to a directory system including a server having an organizational structure management directory,
The server computer,
The definition of the directory includes a category that divides a group of resources in an organization to be managed, attributes of resources belonging to the category, a hierarchy between resources in the same category, and a definition that indicates a relationship between resources in different categories. Definition information registration means to register as information,
Based on the directory definition information, a list of resources belonging to the category selected from the category list display is displayed, and resource information and attribute information of the resource selected from the resource list display , And screen generation means for generating a GUI screen for inputting relevance information representing a correlation with a resource belonging to a category different from the resource,
Data registration means for registering the resource data input on the GUI screen in a database; and
Based on the definition information of the directory, the viewpoint is a desired viewpoint selected from the first viewpoint based on the attribute, the second viewpoint based on the hierarchy, and the third viewpoint based on the relationship. Visualizing means for visualizing the structure of the organization viewed from a tree or list format;
Program to function as.