Organizational chart generating device

Abstract

To easily recognize a relationship with an object organization.SOLUTION: An organizational chart generating device 2 includes: a first acquisition unit 27 configured to acquire configuration information related to an organizational constitution of an object company; a second acquisition unit 28 configured to acquire relationship information indicating a relationship between the object company and a user company; an extraction unit 22 configured to extract each component included in the organizational constitution of the object company based on the configuration information; an identification unit 23 configured to identify components of the object company that are related to the user company based on the relationship information; and a generation unit 24 configured to distinguish between the identified components and unidentified components and generate an organizational chart of the object company.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to an organizational chart generation device.

Background Art

[0002] In an organization such as a company, the organizational structure may be shown by an organizational chart (for example, Patent Document 1). The organizational chart may be published, for example, on the company's homepage. A person in charge of a company who wants to conduct business, etc., with the company grasps the departments that have had contact such as business card exchanges while checking departments, etc., based on the published organizational chart. For example, strategies such as checking the contact status using the organizational chart and conducting business with departments that have not had contact have been developed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, when a person in charge compares the organizational chart with the contact status such as business card exchanges to grasp the contact status, it may take a considerable amount of effort to grasp the situation.

[0005] In view of the above problems, an object of the present disclosure is to provide an organizational chart generation device that can easily recognize the relationship with a target organization.

Means for Solving the Problems

[0006] To solve the above problems, an organizational chart generation device according to a first aspect of the present disclosure includes a first acquisition unit that acquires configuration information related to the organizational structure of a target organization, a second acquisition unit that acquires relationship information indicating the relationship between the target organization and organizations other than the target organization, an extraction unit that extracts each component included in the organizational structure of the target organization based on the configuration information, a specification unit that specifies the components of the target organization having a relationship with the organization based on the relationship information, and a generation unit that generates an organizational chart of the target organization by distinguishing between the specified components and the unspecified components.

[0007] Further, in the organizational chart generation device according to a second aspect of the present disclosure, in the first aspect, the specifying unit specifies the components of the target organization having a relationship with the organization based on whether the extracted components are included in the relationship information.

[0008] Further, in the organizational chart generation device according to a third aspect of the present disclosure, in the first aspect or the second aspect, the specifying unit compares the name of the extracted component with the name corresponding to the component included in the relationship information, and specifies the components of the target organization having a relationship with the organization.

[0009] Further, in the organizational chart generation device according to a fourth aspect of the present disclosure, in the first aspect or the second aspect, the first acquisition unit acquires image data showing the organizational structure of the target organization, and the extraction unit extracts the components based on the image data.

[0010] Further, in the organizational chart generation device according to a fifth aspect of the present disclosure, in the first aspect or the second aspect, the generation unit marks the specified components and generates the organizational chart.

[0011] Further, in the organizational chart generation device according to the sixth aspect of the present disclosure, in the third aspect, the specific unit compares the name of the component extracted with the name corresponding to the component included in the relationship information, identifies the components that match or are similar, and when there is a match in the comparison, the generation unit marks the component to generate the organizational chart, and when they are similar, the generation unit marks the component with a mark different from the mark to generate the organizational chart.

[0012] Further, in the organizational chart generation device according to the seventh aspect of the present disclosure, in the first aspect or the second aspect, the generation unit generates relationship content information indicating the content of the relationship between the organization and the component, in association with the identified component.

[0013] Further, in the organizational chart generation device according to the eighth aspect of the present disclosure, in the seventh aspect, the relationship content information is associated with at least one of the date and time related to the contact and the number of contacts between the person belonging to the organization and the person belonging to the target organization.

[0014] Further, in the organizational chart generation device according to the ninth aspect of the present disclosure, in the first aspect or the second aspect, the first acquisition unit acquires condition information related to the generation of the organizational chart, and the specific unit identifies the components that have a relationship with the organization and conform to the condition information.

[0015] Further, in the organizational chart generation device according to the tenth aspect of the present disclosure, in the ninth aspect, the condition information includes at least one of the personal information of the person belonging to the organization, the personal information of the person belonging to the target organization, the department information of the organization, and the department information of the target organization.

Advantages of the Invention

[0016] According to the organizational chart generation device according to the present disclosure, the relationship with the target organization can be easily recognized.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0018] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. For ease of understanding of the description, the same reference numerals are given to the same components and steps in each drawing as much as possible, and redundant descriptions are omitted.

[0019] <Overall Configuration> FIG. 1 is an overall configuration diagram of an organizational chart generation system 1 according to an embodiment of the present disclosure. In the present embodiment, a company is taken as an example of an organization for description, but it is not limited to a company and can be widely applied as an organization. The organizational chart generation system 1 generates an organizational chart showing the relationship with a target company (target organization) and provides it to a user. An organizational chart is a schematic diagram showing the organizational structure of a company in a diagrammatic form. In the organizational chart, the components included in the organizational structure are shown hierarchically. A component is an element that constitutes an organization, and for example, it is a department or a person.

[0020] In this embodiment, the company to which the user who uses the organizational chart generation system 1 belongs is referred to as the "user-side company" (user-side organization), and the company for which the user wants to create an organizational chart is referred to as the "target company" (target organization). That is, the user-side company is a company other than the target company. Note that the user-side company may be a company that is not the company to which the user who uses the organizational chart generation system 1 belongs.

[0021] The organizational chart generation system 1 includes an organizational chart generation device 2 and a user terminal 3. The organizational chart generation device 2 and the user terminal 3 can communicate with each other via a network NT.

[0022] The organizational chart generation device 2 is an information processing device that generates an organizational chart. The organizational chart generation device 2 is, for example, a server device, and may be of a cloud type or an on-premises type.

[0023] The user terminal 3 is a terminal device and an information processing device used by the user. The user terminal 3 is, for example, a personal computer, a smartphone, a tablet, or the like. In this embodiment, the case where the user terminal 3 is a personal computer is taken as an example.

[0024] <Hardware Configuration> FIG. 2 is a diagram schematically showing an example of the hardware configuration of the organizational chart generation device 2.

[0025] As shown in FIG. 2, the organizational chart generation device 2 includes a control device 10, a communication device 11, a storage device 12, an operation device 13, and a display device 14. The control device 10 is mainly configured to include a CPU (Central Processing Unit) 15 and a memory 16.

[0026] In the control device 10, the CPU 15 executes a predetermined program stored in the memory 16 or the storage device 12 or the like, and functions as various functional configurations described later. The memory 16 is a computer-readable storage medium, and may be composed of, for example, at least one of RAM (Random Access Memory), ROM (Read only memory), EPROM (Erasable Program ROM), EEPROM (Electrically Erasable Program ROM), etc. The memory 16 can store various data, and stores, for example, programs necessary for executing processing in the organization chart generation device 2 and the like.

[0027] The communication device 11 is composed of a communication interface or the like for communicating with an external device.

[0028] The storage device 12 is a computer-readable recording medium, and is composed of, for example, a hard disk, a solid state drive, or the like. The storage device 12 stores various programs and various information necessary for executing processing in the control device 10. In addition, other non-transitory computer-readable recording media include portable recording media such as magnetic tapes, flexible disks, optical disks, digital versatile disks, Blu-ray disks, magneto-optical disks, memory cards, and USB memories.

[0029] The operating device 13 is an input device (for example, a keyboard, a mouse, etc.) that receives an input. The operating device 13 receives a user's operation and inputs the operation to the organization chart generation device 2.

[0030] The display device 14 is a display device (for example, a display, etc.). The display device 14 outputs characters and images.

[0031] Note that the organizational chart generation device 2 can be realized by using an information processing device such as a dedicated or general-purpose computer. Also, the organizational chart generation device 2 may be composed of a single information processing device or a plurality of information processing devices. Further, FIG. 2 only shows a part of the main hardware configuration of the organizational chart generation device 2, and the organizational chart generation device 2 can be provided with other configurations. Note that the basic configuration of the user terminal 3 as an information processing device is the same as that of FIG. 2.

[0032] <Functional configuration> FIG. 3 is a block diagram showing an example of various functions in the organizational chart generation device 2. The organizational chart generation process is executed by the functions in each block. Note that in this embodiment, it is assumed that the organizational chart generation device 2 has various functions related to the organizational chart generation process, but part or all of them may be provided in the user terminal 3.

[0033] As shown in FIG. 3, the organizational chart generation device 2 mainly includes an acquisition unit 21, an extraction unit 22, a specification unit 23, a generation unit 24, and an output unit 25 as functional components.

[0034] The acquisition unit 21 includes a first acquisition unit 27 and a second acquisition unit 28.

[0035] The first acquisition unit 27 acquires configuration information related to the organizational structure of the target company. The configuration information related to the organizational structure is information in which constituent elements such as departments constituting the organization of the target company are shown. Specifically, the configuration information related to the organizational structure is data of an organizational chart. The data of the organizational chart is, for example, image data of the organizational chart.

[0036] For example, the user acquires image data of the organizational chart of the target company from the homepage or the like of the target company. Then, the user uses the user terminal 3 to transmit the image data to the organizational chart generation device 2. Thereby, the first acquisition unit 27 acquires the image data of the organizational chart. Note that the first acquisition unit 27 may directly acquire the image data of the organizational chart of the set target company from the homepage or the like.

[0037] FIG. 4 shows an example of the image data P1 of the organization chart acquired by the first acquisition unit 27. In the present embodiment, as shown in FIG. 4, in the target company, an A center, a B department, and a C department are arranged under the president. And, in the target company, a D head office is arranged under the B department, and an E head office is arranged under the C department. And, in the target company, a D1 department and a D2 department are arranged under the D head office, and an E1 department and an E2 department are arranged under the E head office.

[0038] Returning to FIG. 3, the first acquisition unit 27 outputs the image data of the organization chart to the extraction unit 22.

[0039] The second acquisition unit 28 acquires relationship information indicating the relationship between the user-side company and the target company.

[0040] The relationship information is information indicating the relationship between the user-side company and the target company, and is, for example, information (contact information) indicating the contact point between the user-side company and the target company. A contact point is a connection between the user-side company and the target company. The contact point is not limited as long as it is information indicating the connection between the user-side company and the target company, such as business card exchange, telephone, email, acquaintance such as business negotiation or visit, and participation in seminars. In addition, the contact point is not limited to those with direct interaction, and for example, relationships such as kinship or friendship may be used.

[0041] In the relationship information, a person belonging to the user-side company, a person belonging to the target company and the belonging of that person, and information related to the contact point are associated with each other. That is, the relationship information shows who in the user-side company and who in the target company have what kind of contact point. The information related to the contact point may be the presence or absence of the contact point, or the specific content of the contact point. The information related to the contact point may include the date and time when the contact point was made. Note that other information (for example, the belonging of a person belonging to the user-side company) may be associated with the relationship information.

[0042] Note that the relationship information may be information summarized as one piece of information or information composed of multiple pieces of information. For example, relationship information may be constituted by combining two pieces of information: information in which a person belonging to the user-side company, a person belonging to the target company, and information related to the contact point are associated with each other, and information in which a person belonging to the target company and the name of the affiliation are associated with each other.

[0043] The second acquisition unit 28 reads and acquires, for example, the relationship information stored in the storage device 12 of the organization chart generation device 2. Note that the second acquisition unit 28 may acquire the relationship information from another device separate from the organization chart generation device 2.

[0044] The second acquisition unit 28 outputs the relationship information to the specifying unit 23.

[0045] The extraction unit 22 extracts each component included in the organizational structure based on the configuration information related to the organizational structure of the target company. Specifically, the extraction unit 22 extracts components such as each department included in the organization chart based on the image data of the organization chart acquired by the acquisition unit 21. For example, the extraction unit 22 executes OCR on the image data and extracts the names of components such as each department name.

[0046] For example, with respect to the image data shown in FIG. 4, the extraction unit 22 extracts, as components, the president, Center A, Department B, Department C, Headquarters D, Headquarters E, Department D1, Department D2, Department E1, and Department E2, respectively.

[0047] Returning to FIG. 3, the extraction unit 22 outputs the names of the extracted components to the specifying unit 23.

[0048] The specific part 23 identifies the components of the target company related to the user-side company based on the relationship information indicating the relationship between the user-side company and the target company. That is, the specific part 23 identifies the components related to the user-side company from among the components extracted by the extraction part 22. Specifically, the specific part 23 identifies the components of the target company related to the user-side company according to whether the extracted components are included in the relationship information. The components included in the relationship information are the components related to the user-side company. For example, the specific part 23 performs the specific process by comparing the name of the extracted component with the name corresponding to the component included in the relationship information.

[0049] The specific part 23 compares the components extracted by the extraction part 22 with the affiliation (or person) of the person of the target company included in the relationship information. Specifically, the specific part 23 compares each name as a character string. And when the name of the component extracted by the extraction part 22 matches the name included in the relationship information, the specific part 23 identifies the component as a component related to the user-side company. The specific part 23 may also identify the component as a component related to the user-side company when the name of the component corresponds to (matches or is similar to) the name in the relationship information.

[0050] In this way, the specific part 23 identifies the components related to the user-side company from among the components extracted by the extraction part 22. And the specific part 23 outputs the identified components as "specific components" to the generation part 24.

[0051] For example, for a target company as shown in Figure 4, when the specific part 23 identifies the A center, the D head office, the D1 department, and the E2 department as components related to the user-side company, each is regarded as a specific component and output to the generation part 24.

[0052] The generation unit 24 generates an organizational chart of the target company. Specifically, the generation unit 24 distinguishes between the components (specific components) identified by the identification unit 23 and the components not identified by the identification unit 23 (non-specific components), and generates an organizational chart of the target company. "Distinguish" means to display in the generated organizational chart so that it is possible to identify whether it is a specific component, that is, whether it is a component related to the user-side company. In the present embodiment, the generation unit 24 marks the specific components and generates an organizational chart. Note that in the present embodiment, in the generated organizational chart, components that are not specific components are not marked. Also, regarding "generation" in the generation unit 24, it may be to newly create an organizational chart, or it may be to create an organizational chart by updating data.

[0053] The generation unit 24 marks the specific components on the image data of the organizational chart acquired by the acquisition unit 21, and generates (updates) the organizational chart. FIG. 5 is a diagram showing an example of the organizational chart generated by the generation unit 24. FIG. 5 is an example of the data P2 of the organizational chart generated when processing is performed based on the image data P1 of FIG. 4. That is, the generation unit 24 attaches a mark M1 corresponding to the specific component to the organizational chart of the image data P1 of FIG. 4. Specifically, when the A center, the D head office, the D1 department, and the E2 department are identified as specific components in the identification unit 23, a mark M1 is attached to each of the A center, the D head office, the D1 department, and the E2 department.

[0054] In this way, the generation unit 24 attaches the mark M1 to the acquired image data to update the image data of the organizational chart, and generates the organizational chart. The generation unit 24 may generate the organizational chart as image data or may generate the organizational chart in another data format.

[0055] Note that the marks added when the generation unit 24 generates the organization chart are not limited to the mark M1 in FIG. 5. For example, although the mark M1 in FIG. 5 indicates the presence or absence of a relationship (presence or absence of contact) with the user-side company, the mark may be displayed according to the degree of the relationship (intensity of contact). The degree of the relationship is set based on each contact such as the number of email exchanges and the number of face-to-face meetings, for example, and is set higher as the relationship is deeper.

[0056] Also, the generation unit 24 may use a plurality of types of marks. For example, when specifying a specific component in the specifying unit 23, different types of marks may be used depending on whether the name of the component matches or is similar to the name corresponding to the component included in the relationship information. Similarity means that although the names do not exactly match, the names are similar to each other. For example, when the similarity degree (distance) between character strings is equal to or greater than a threshold value, it is determined that they are similar. For example, when only a part of character strings such as "A Center" and "A Centre" is different, it can be determined that they are similar. Also, for example, when the relationship information has a name "Sales Department" and each of the extracted components includes "Sales Department of D Head Office" and "Sales Department of E Head Office", it can be determined that each of "Sales Department of D Head Office" and "Sales Department of E Head Office" is similar. The specifying unit 23 specifies the specific component when the names match and the specific component when the names are similar, and the generation unit 24 distinguishes the marks to be assigned depending on whether they match or are similar.

[0057] FIG. 6 is a diagram showing an example of generating an organizational chart using multiple types of marks. FIG. 6 is an example of the data P3 of the organizational chart in a display format different from the data P2 in FIG. 5. In FIG. 6, in the specific part 23, the A center, the D head office, the sales department of the D head office, and the sales department of the E head office are specified as specific components. The A center and the D head office have the same relationship information and name, and the sales department of the D head office and the sales department of the E head office show a case where the relationship information and name are similar. In this case, for example, the mark M1 is attached to the A center and the D head office, and a mark M2 different from the mark M1 is attached to the sales department of the D head office and the sales department of the E head office. By changing the mark display according to the match and similarity, it becomes possible to distinguish and recognize the specific components in contact with the user-side enterprise and the specific components that may be in contact with the user-side enterprise. For the components with the mark M2 indicating similarity, it may be possible to ask the user whether to link them as specific components. For example, when the relationship information has the name "sales department" and the extracted components each contain "D head office sales department" and "E head office sales department", the user may be able to specify which (or both) of the "D head office sales department" and the "E head office sales department" to associate with the "sales department" of the relationship information.

[0058] In this way, the generation unit 24 generates an organizational chart of the target enterprise showing the relationship with the user-side enterprise, and outputs the image data of the generated organizational chart to the output unit 25.

[0059] In addition, the generation unit 24 may generate relationship content information in association with the specific components while generating the organizational chart. The relationship content information is information indicating the content of the relationship between the user-side enterprise and the specific components. Specifically, the relationship content information is associated with at least one of the date and time of contact and the number of contacts between a person belonging to the user-side enterprise and a person belonging to the specific component of the target enterprise. For example, the relationship content information shows specific relationship contents such as the date and time of sending an email and the number of emails. When the relationship content information is generated in the generation unit 24, it is output to the output unit 25.

[0060] The output unit 25 outputs the image data of the organization chart generated by the generation unit 24 to the user terminal 3. As a result, the image data showing the relationships can be displayed on the user terminal 3. The user can recognize the components such as the departments related to the user's own company by checking the organization chart.

[0061] Also, the output unit 25 outputs the relationship content information generated by the generation unit 24 to the user terminal 3. For example, when the user checks the organization chart on the user terminal 3, by selecting a department or the like as a specific component with a mark M1 or the like attached, the user can open the relationship content information associated with the specific component and check the specific relationship content.

[0062] <Flow of processing> FIG. 7 is a flowchart showing an example of the flow of the organization chart generation process according to the present embodiment. Each process of the following steps is started when the image data of the organization chart is transmitted by the user. Note that the order and content of the following steps can be changed as appropriate.

[0063] (Step SP10) The acquisition unit 21 acquires the image data of the organization chart. The acquisition unit 21 may acquire the relationship information together with the image data, or may acquire the relationship information in advance before the start of the flow. Then, the process proceeds to step SP11.

[0064] (Step SP11) The extraction unit 22 extracts the components included in the organization chart based on the image data of the organization chart. The extraction unit 22 assigns a processing order to each of the extracted components. For example, when the number of extracted components is n, for the components, numbers k are set in order from k = 1 to k = n. Then, the process proceeds to step SP12.

[0065] (Step SP12) The specific part 23 sets the component with number k = 1 as the comparison target. Then, it proceeds to step SP13.

[0066] (Step SP13) The specific part 23 compares the relationship information with the component that is the comparison target to determine whether the names match (correspond). If the names match (correspond), it proceeds to step SP14. If the names do not match (correspond), it proceeds to step SP15.

[0067] (Step SP14) The specific part 23 specifies the component that was the comparison target as a specific component. Then, it proceeds to step SP15.

[0068] (Step SP15) The specific part 23 determines whether the component that was the comparison target has the number k = n. If the component that was the comparison target does not have the number k = n, it proceeds to step SP16. If the component that was the comparison target has the number k = n, it proceeds to step SP17.

[0069] (Step SP16) The specific part 23 sets the component with the number k obtained by adding 1 to the number k of the component that was the comparison target as the comparison target. Then, it repeats the return process to step SP13.

[0070] (Step SP17) The generation part 24 attaches the mark M1 to the specific component to generate an organizational chart. Then, it proceeds to step SP18.

[0071] (Step SP18) The output part 25 provides the generated organizational chart to the user. For example, the output part 25 outputs the data of the generated organizational chart to the user terminal 3.

[0072] In this way, an organizational chart of the target company showing the relationship between the user-side company and the target company is generated and provided to the user.

[0073] For example, as shown in FIG. 5, an organizational chart in which the relationship between the user-side company and the target company is shown as mark M1 is provided to the user. By checking the organizational chart, the user can check the components such as the departments of the target company related to the user-side company. Then, for example, when a component marked with M1 is selected, the relationship content information corresponding to the selected component can be referred to. FIG. 8 is a diagram showing an example of the relationship content information. FIG. 8 shows an example when the A center in FIG. 5 is selected. In FIG. 8, the user-side company is shown as "own company". The relationship content information shows the department, the contact period, the number of contact times, the number of contact persons, the persons who had contacts in the target company, and the persons who had contacts in the own company (user-side company). In FIG. 8, each piece of information is shown in area R1. The department is the selected department (component). The contact period is the period during which contacts were made. For example, the contact period is shown as the period from the first day when contacts were made to the latest day when contacts were made. The number of contact times is the number of times contacts were made. If there are multiple means of contact, the number of contact times is shown as the sum of the contact times of each means. The number of contact persons is the number of persons who had contacts within the department (component). The persons who had contacts in the target company are the persons who had contacts within the department (component). The persons who had contacts in the own company are the persons in the own company who had contacts with the persons within the department (component).

[0074] Also, the relationship content information may include information related to the highest position reached. In FIG. 8, each piece of information is shown in area R2. Specifically, the information related to the highest position reached shows the highest position reached, the date of the most recent contact, the means of contact, and the persons who had contacts in the own company. The highest position reached is the highest-ranked position and the person in that position among those who had contacts within the department (component). The date of the most recent contact is the date of the most recent contact with the person in the highest position reached. The means of contact is the means of contact (e.g., email) with the person in the highest position reached. The persons who had contacts in the own company are the persons in the own company who had contacts with the person in the highest position reached.

[0075] In addition, the relationship content information may indicate, for the investigation period, the person with the highest number of contacts and the person with the highest contact density among the departments (components). In FIG. 8, each piece of information is shown in region R3. The person with the highest number of contacts and the person with the highest contact density may be a person of the target company or a person of the user's own company. Regarding the contact density, for example, the density may be evaluated by the contact means. For example, a face-to-face meeting is evaluated as having a higher contact density than an email.

[0076] In addition, the relationship content information may indicate the number of contacts per year, as shown in region R4 in FIG. 8. In FIG. 8, the size of mark C1 indicates the number of contacts. Mark C1 may also indicate the height of the highest position reached by color.

[0077] In this way, the user can confirm the detailed relationship content of the related departments (components) based on the relationship content information.

[0078] <Function and Effect> As described above, the organization chart generation device 2 according to the present embodiment includes a first acquisition unit 27 that acquires configuration information related to the organizational structure of the target company, a second acquisition unit 28 that acquires relationship information indicating the relationship between the target company and the user-side company, an extraction unit 22 that extracts each component included in the organizational structure of the target company based on the configuration information, a specification unit 23 that specifies the components of the target company related to the user-side company based on the relationship information, and a generation unit 24 that generates an organization chart of the target company by distinguishing between the specified components and the unspecified components.

[0079] According to this configuration, based on the relationship information, the components of the target company related to the user-side company are identified, and an organizational chart of the target company is generated. As a result, by checking the organizational chart, it becomes possible to easily recognize the components with relationships and the components without relationships. For example, when a user creates a business strategy for a target company, it becomes possible to easily check the departments that have not been contacted. That is, the organizational chart generation device 2 can refer to the components such as each department on the structured organizational chart and the contacts between the respective components, and the user can easily recognize the relationship with the target company.

[0080] Also, in the organizational chart generation device 2, the specifying unit 23 specifies the components of the target company related to the user-side company based on whether the extracted components are included in the relationship information.

[0081] According to this configuration, it becomes possible to easily specify the components of the target company related to the user-side company using the relationship information.

[0082] Also, in the organizational chart generation device 2, the specifying unit 23 compares the name of the extracted component with the name corresponding to the component included in the relationship information, and specifies the components of the target company related to the user-side company.

[0083] According to this configuration, it becomes possible to easily specify the components of the target company related to the user-side company by name comparison. Note that the components with matching names may be specified as the components of the target company related to the user-side company, or the components with similar names may be specified as the components of the target company related to the user-side company.

[0084] Also, in the organizational chart generation device 2, the first acquisition unit 27 acquires image data showing the organizational structure of the target company, and the extraction unit 22 extracts components based on the image data.

[0085] According to this configuration, it becomes possible to efficiently extract the components of the organizational structure based on the image data.

[0086] Also, in the organizational chart generation device 2, the generation unit 24 marks the specified component and generates an organizational chart.

[0087] According to this configuration, it becomes possible to easily recognize the components specified as being related in the organizational chart.

[0088] Also, in the organizational chart generation device 2, the specifying unit 23 compares the name of the extracted component with the name corresponding to the component included in the relationship information, specifies the components that match or are similar, and when they match in this comparison, the generation unit 24 marks the component and generates an organizational chart, and when they are similar, the generation unit 24 marks the component with a mark different from the mark and generates an organizational chart.

[0089] According to this configuration, it becomes possible to distinguish and recognize the matching components and the similar components respectively from the organizational chart.

[0090] Also, in the organizational chart generation device 2, the generation unit 24 generates relationship content information indicating the content of the relationship between the user-side company and the component, in association with the specified component.

[0091] According to this configuration, it becomes possible to grasp the content of the relationship related to the specified component based on the relationship content information.

[0092] Also, in the organizational chart generation device 2, the relationship content information is associated with at least one of the date and time related to the contact and the number of contacts between a person belonging to the user-side company and a person belonging to the target company.

[0093] According to this configuration, it becomes possible to specifically confirm the person of the user-side company who is related, the person of the target company, and the contact situation.

[0094] <Modification Example> Note that the present disclosure is not limited to the above-described embodiments. That is, modifications appropriately made by those skilled in the art to the above-described embodiments are also included in the scope of the present disclosure as long as they have the features of the present disclosure. In addition, each element included in the above-described embodiments and the modified examples described later can be combined as long as it is technically possible, and combinations thereof are also included in the scope of the present disclosure as long as they include the features of the present disclosure.

[0095] For example, in the above-described embodiment, each function is exemplified as being possessed by the organization chart generation device 2, but each function may be provided in the user terminal 3. Also, each function may be distributed between the organization chart generation device 2 and the user terminal 3.

[0096] In addition, in the above-described embodiment, the case where data of an organization chart is used as configuration information related to the organizational structure is exemplified, but the configuration information related to the organizational structure is not limited to the data of the organization chart.

[0097] In addition, in the above-described embodiment, the case where image data is used as the data of the organization chart is exemplified, but data other than image data may be used as long as the data shows the information of the organization chart.

[0098] In addition, in the above-described embodiment, the case where the user acquires image data of the organization chart from the homepage of the target company is exemplified, but data of the organization chart of the target company created by the user may be used.

[0099] In addition, in the above-described embodiment, the generation unit 24 is described by taking as an example the case of generating an organization chart by updating the image data of the organization chart acquired by the acquisition unit 21, but it is not limited to the case of updating the image data acquired by the acquisition unit 21, and the organization chart may be reconfigured.

[0100] Also, conditions for generating an organizational chart may be set. For example, the acquisition unit 21 acquires condition information related to the generation of an organizational chart. The condition information can be set by the user using the user terminal 3, for example. Then, the identification unit 23 identifies a component that has a relationship with the user-side company and conforms to the condition information as a specific component. And the generation unit 24 generates an organizational chart based on the specific component. The condition information is, for example, the department information of the target company (information on the type of component). By setting the condition information in this way, an organizational chart for the necessary part can be generated. The condition information is not limited to the above, and may include at least any one of the person information belonging to the user-side company, the person information belonging to the target company, the department information of the user-side company, and the department information of the target company. By setting the person information or department information belonging to the user-side company as a condition, an organizational chart of the target company related to the persons or departments of the user-side company can be generated. By setting the person information or department information belonging to the target company as a condition, an organizational chart of the target company can be generated with the scope narrowed down.

[0101] Also, in the above embodiment, the identification unit 23 has been described by taking as an example the case where the identification process is performed by comparing the name of the extracted component with the name corresponding to the component included in the relationship information. However, as long as it can be determined that the extracted component is included in the relationship information, it is not limited to name comparison. For example, comparison and identification may be performed using unique identification information associated with the component.

[0102] In addition, in the above-described embodiment, the generation unit 24 was described by taking as an example the case where an organization chart is generated by distinguishing a specific component from a component that is not a specific component by attaching a mark to the specific component. However, it is not limited to the case of attaching a mark to a specific component as long as it is possible to identify whether a component is related to the user-side company. For example, it may be possible to attach a mark only to a component that is not a specific component, or it may be possible to attach different marks to a specific component and a component that is not a specific component, respectively. Further, it may be possible to generate an organization chart showing only specific components, or to generate an organization chart showing only components that are not specific components, or to generate organization charts separately for specific components and components that are not specific components, respectively.

[0103] Also, for example, it may be possible to contact a person in a related department by selecting a person in a related department based on the generated organization chart. For example, when the person in the organization chart is clicked, an email screen for that person may be launched. At this time, it may be possible to automatically generate the name of the person on the user company side who has had contact with the person and the content of the contact, and describe it in the body of the email. For example, by describing in the email "Thank you for contacting us from ×× (person's name) of our company on ×× month ×× day", the other party can easily recognize the relationship with the company that sent the email.

[0104] Also, for example, it may be possible to contact a person (a person within the company) in the user-side company who is related to the department of the target company in question by selecting a related department based on the generated organization chart. For example, when the department (person) in the organization chart is clicked, the extension number of a person within the company who is related to the department may be displayed. As a result, it is possible to easily contact a related person within the company and confirm specific contact details and the like.

Explanation of Reference Numerals

[0105] 2: Organization Chart Generation Device 22: Extraction Unit 23: Specific part 24: Generation part 27: First acquisition part 28: Second acquisition part

Claims

1. A first acquisition unit that acquires configuration information related to the organizational structure of a target organization; A second acquisition unit that acquires relationship information indicating the relationship between the target organization and organizations other than the target organization; An extraction unit that extracts each component included in the organizational structure of the target organization based on the configuration information; A specifying unit that specifies the components of the target organization that are related to the organization based on the relationship information; A generation unit that generates an organizational chart of the target organization by distinguishing between the specified components and the unspecified components; An organizational chart generation device comprising the above.

2. The specifying unit specifies the components of the target organization that are related to the organization based on whether the extracted components are included in the relationship information. The organizational chart generation device according to Claim 1.

3. The specifying unit compares the name of the extracted component with the name corresponding to the component included in the relationship information, and specifies the components of the target organization that are related to the organization. The organizational chart generation device according to Claim 1 or 2.

4. The first acquisition unit acquires image data showing the organizational structure of the target organization, The extraction unit extracts the components based on the image data. The organizational chart generation device according to Claim 1 or 2.

5. The generation unit marks the specified components and generates the organizational chart. The organizational chart generation device according to Claim 1 or 2.

6. The specifying unit compares the name of the extracted component with the name corresponding to the component included in the relationship information, and specifies the components that match or are similar. When they match in the comparison, the generation unit marks the components and generates the organizational chart, and when they are similar, the generation unit marks the components with a mark different from the mark and generates the organizational chart. The organizational chart generation device according to Claim 3.

7. The generation unit generates relationship content information indicating the content of the relationship between the organization and the component in association with the specified component. The organizational chart generation device according to Claim 1 or 2.

8. The relationship content information is associated with at least one of the date and time of contact and the number of contacts between a person belonging to the organization and a person belonging to the target organization. The organizational chart generation device according to Claim 7.

9. The first acquisition unit acquires condition information related to the generation of the organizational chart, The specifying unit specifies the component that has a relationship with the organization and conforms to the condition information, The organizational chart generation device according to claim 1 or 2.

10. The condition information includes at least any one of person information belonging to the organization, person information belonging to the target organization, department information of the organization, and department information of the target organization, The organizational chart generation device according to claim 9.

Images