JP2012203846A - Personnel information output device, personnel information output method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To appropriately change the setting of a grace period according to a system using personnel information and obtain personnel information according to the grace period of which setting has been changed.SOLUTION: A personnel information output device includes: a personnel information storage unit 104 for storing personnel information in which generation information is managed; a grace condition storage unit 114 for storing grace conditions that are setting conditions of a grace period according to a system using the personnel information; and a personnel information output unit 150 that obtains the personnel information based on the grace conditions from the personnel information storage unit 104 and outputs the obtained personnel information. Therefore, the personnel information output device can obtain personnel information based on a grace period and appropriately change the grace conditions according to a system using personnel information, thereby appropriately obtaining personnel information based on a grace period according to the system using personnel information.

Description

  The present invention relates to a personnel information output device, personnel information output method, and program for outputting personnel information associated with personnel changes.

In recent years, business information technology (IT: Information Technology, Information Technology) has progressed, and personnel information has also been digitized and managed by a personnel system.
In many companies, HR information managed by the HR system is distributed to multiple business systems used in the company, thereby unifying the information used and reducing the management cost of HR information. ing.
As a management method for personnel information, there is a method for managing only the latest personnel information.
As a management method for personnel information, there is a method for managing the transition of personnel information over the past, present, and future by managing personnel information with a validity period. By this method, past personnel information can be referred to and future personnel change information can be input in advance. (For example, refer to Patent Document 1.)
In addition, if the authority of the person to be transferred is deprived together with the personnel change, there is a problem that the business cannot be taken over in time. For this reason, a countermeasure is taken in which the authority is extended for a period set as a grace period. There is a method of automatically adding authority to the target business system. (For example, see Patent Document 2.)

JP 2010-205183 A JP 2009-129289 A

  The embodiment of the present invention is, for example, capable of appropriately changing the setting of a grace period according to a system that uses personnel information, and an object thereof is to output personnel information corresponding to the changed grace period.

The personnel information output device according to the present invention is:
Corresponding member identification information for identifying members constituting the organization, member attributes indicating attributes of the members in the organization, and valid periods of authority granted to the members according to the member attributes In addition, including a plurality of personnel information of the member in the organization, if at least one of the member identification information and the member attribute is different, a personnel information storage unit that stores as different personnel information,
In the effective period, the authority granted to the member specifies a grace period that is continuously considered valid for a predetermined period after the effective period ends, and the member attribute to be applied to the grace period A grace condition storage unit for storing the member attribute specifying conditions to be associated with each other;
Requesting acquisition of the personnel information stored in the personnel information storage unit, generating a personnel information acquisition request including a current date that is a date when requesting acquisition of the personnel information, and acquiring the generated personnel information A personnel information requesting section for outputting the request;
Input the personnel information acquisition request output by the personnel information request unit, input the grace period stored in the grace condition storage unit and the member attribute specifying condition, and the current information included in the personnel information acquisition request Calculate the grace date corresponding to the date that is backed by the grace period from the previous day of the date, the content effective period that is the effective period including the calculated grace date, and the member attribute associated with the content effective period The personnel information including the member attribute specified from the member attribute specification condition associated with the grace date is acquired from the personnel information storage unit, and the acquired personnel information is output as the grace personnel information. And a personnel information output unit.

  The personnel information output device according to the present invention can change the setting of the grace period as appropriate according to the system that uses the personnel information, for example, and can output the personnel information corresponding to the changed grace period To do.

FIG. 5 shows the first embodiment and is a diagram showing an example of the appearance of a personnel information output device. FIG. 5 shows the first embodiment and shows an example of hardware resources of the personnel information output device 100. FIG. 3 shows the first embodiment and shows a configuration of a personnel information output device 100. FIG. FIG. 5 shows the first embodiment and shows an example of supply personnel information 400; FIG. 5 shows the first embodiment and shows an example of personnel information extraction conditions 405; The figure which shows Embodiment 1 and is a figure which shows the example of the new personnel information 410x. The figure which shows Embodiment 1 and is a figure which shows the example of the existing personnel information 410y which the personnel information storage part 104 has memorize | stored. The figure which shows Embodiment 1 and is a figure which shows the example of the personnel information 410z after the update which the personnel information memory | storage part 104 has memorize | stored. 5 is a diagram showing the first embodiment, and is a flowchart showing processing when the generation personnel information registration unit 103 registers personnel information 410 in the personnel information storage unit 104. FIG. FIG. 6 shows the first embodiment, and shows a first specific example of processing of the generation personnel information registration unit 103; FIG. 10 shows the first embodiment, and shows a second specific example of processing of the generation personnel information registration unit 103. FIG. 11 shows the first embodiment, and shows a third specific example of the process of the generation personnel information registration unit 103; FIG. 10 shows the first embodiment, and shows a fourth specific example of the process of the generation personnel information registration unit 103. FIG. 10 shows the first embodiment, and shows a fifth specific example of the process of the generation personnel information registration unit 103; FIG. 10 is a diagram illustrating the first embodiment and is a diagram illustrating a sixth specific example of the process of the generation personnel information registration unit 103; FIG. 5 shows the first embodiment and shows an example of current personnel information 420; The figure which shows Embodiment 1 and is a figure which shows the example of the grace condition 421 which the grace condition memory | storage part 114 memorize | stores. FIG. 9 is a diagram illustrating the first embodiment and is a flowchart illustrating processing performed by a postponement personnel information acquisition unit 113 and a generation personnel information acquisition unit 115; FIG. 5 shows the first embodiment and shows an example of postponement personnel information 425; FIG. 5 shows the first embodiment and is a flowchart showing processing of the combined personnel information output unit 116; FIG. 5 shows the first embodiment, and shows a first example of combined personnel information 426; FIG. 10 shows the first embodiment and shows a second example of combined personnel information 426; FIG. 6 shows the first embodiment, and shows an example of distribution settings 427 stored in a distribution setting storage unit 118. FIG. 5 shows the first embodiment and shows an example of distribution personnel information 430; FIG. 5 shows the first embodiment, and shows the configuration of the personnel information output device 100 when the supply personnel information 400 is all data. The figure which shows Embodiment 1 and is a figure which shows the example of the supply personnel information 400 in the case of all the case data. The figure which shows Embodiment 1 and shows the example of the last supply personnel information 400 which the difference calculation condition memory | storage part 122 has memorize | stored. FIG. 6 shows the configuration of the personnel information output device 100 having the personnel information narrowing down condition storage unit 121 in the second embodiment. FIG. 16 shows the second embodiment and shows an example of personnel information narrowing conditions 431; FIG. 10 is a diagram illustrating the second embodiment, and illustrates an example of current personnel information 420 that matches a personnel information narrowing condition 431; The figure which shows Embodiment 2 and is a figure which shows the example of the postponement personnel information 425 which agrees with personnel information narrowing down conditions 431. FIG. FIG. 18 is a diagram illustrating the second embodiment and illustrates an example of combined personnel information 426 that matches the personnel information narrowing condition 431;

Embodiment 1 FIG.
In this embodiment, an example of a personnel information output device that outputs personnel information in which a grace period is set will be described.

  First, the outline of the personnel information output apparatus will be described with reference to FIGS.

FIG. 1 is a diagram illustrating an example of an appearance of a personnel information output apparatus according to Embodiment 1.
In FIG. 1, a personnel information output device 100 includes a system unit 910, a display device 901 having a CRT (Cathode / Ray / Tube) or LCD (liquid crystal) display screen, a keyboard 902 (Key / Board: K / B), a mouse. 903, FDD904 (Flexible / Disk / Drive), compact disk device 905 (CDD), printer device 906, scanner device 907, and the like are provided with hardware resources, and these are connected by cables and signal lines.
The system unit 910 is a computer, and is connected to the facsimile machine 932 and the telephone 931 via a cable, and is connected to the Internet 940 via a local area network 942 (LAN) and a gateway 941.

FIG. 2 is a diagram illustrating an example of hardware resources of the personnel information output device 100 according to the first embodiment.
In FIG. 2, the personnel information output device 100 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a processor) that executes a program. The CPU 911 is connected to the ROM 913, the RAM 914, the communication board 915, the display device 901, the keyboard 902, the mouse 903, the FDD 904, the CDD 905, the printer device 906, the scanner device 907, and the magnetic disk device 920 via the bus 912, and the hardware. Control the device. Instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of a storage device or a storage unit.
The communication board 915, the keyboard 902, the scanner device 907, the FDD 904, and the like are examples of an input unit and an input device.
Further, the communication board 915, the display device 901, the printer device 906, and the like are examples of an output unit and an output device.

The communication board 915 is connected to the facsimile machine 932, the telephone 931, the LAN 942, and the like. The communication board 915 is not limited to the LAN 942 and may be connected to the Internet 940, a WAN (wide area network) such as ISDN, or the like. When connected to a WAN such as the Internet 940 or ISDN, the gateway 941 is unnecessary.
The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 stores programs that execute functions described as “˜units” in the description of the embodiments described below. The program is read and executed by the CPU 911.
The file group 924 includes information, data, signal values, variable values, and parameters that are described as “determination results of”, “calculation results of”, and “processing results of” in the description of the embodiments described below. Are stored as items of “file” and “database”. The “file” and “database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.
In addition, the arrows in the flowcharts described in the following description of the embodiments mainly indicate input / output of data and signals. The data and signal values are the RAM 914 memory, the FDD 904 flexible disk, the CDD 905 compact disk, and the magnetic field. The data is recorded on a recording medium such as a magnetic disk of the disk device 920, another optical disk, a mini disk, and a DVD (Digital Versatile Disk). Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “to part” in the description of the embodiment described below may be “to circuit”, “to device”, “to device”, “means”, and “to step”. ”,“ ˜procedure ”, or“ ˜processing ”. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” described below. Alternatively, the procedure or method of “to part” described below is executed by a computer.

Here, the personnel information will be described.
The personnel information is information indicating the affiliation, position, etc. of members constituting an organization such as a company. Here, the organization may be, for example, a public organization and is not limited. However, in order to make the explanation easier to understand, the explanation will be made assuming that the organization is a company. The company members may be full-time employees, part-time employees, or temporary employees, and there are no restrictions.
An employee's affiliation, job title, and the like can be referred to as member attributes indicating attributes in the organization of the employee (member).
Employees are allowed authority according to member attributes such as affiliation and job title. For example, department managers are authorized to approve purchase requests submitted by department members, and members belonging to the general affairs department are authorized to approve applications for taking out confidential materials outside the company. To do.
In addition, the effective period during which this authority is recognized is a period in which member attributes (affiliation, job title, etc.) in which the authority of the employee is recognized are provided. (The effective period for which authority is granted is hereinafter referred to as the “effective period”.)
The personnel information first includes member identification information for identifying an employee (member). Here, the member identification information is, for example, an ID (Ididification) such as an employee name or an employee number. However, since the name may be the same name, the member identification information is preferably an ID that does not have the same number. However, if the employee can be identified only by the name, the name may be used as the member identification information. I do not care. Furthermore, the personnel information includes a member attribute and a valid period corresponding to the member attribute, and the member identification information, the member attribute, and the valid period are associated with each other.

Next, the outline of the personnel information output apparatus 100 will be described with reference to FIG.
FIG. 3 is a diagram illustrating a configuration of the personnel information output device 100.
The personnel system 200 is a device such as a server that manages personnel information outside the personnel information output device 100.
There are a plurality of personnel systems 200 such as a personnel system 200a and a personnel system 200b as shown in FIG. Hereinafter, when there is no need to distinguish between a plurality of personnel systems 200a and personnel systems 200b, they are referred to as personnel systems 200. In the description of the present embodiment, the HR system 200 will be described with two HR systems 200a and 200b, but the number of HR systems 200 is not limited.

  The business system 300 is a device such as a server that uses personnel information distributed from the personnel information output device 100. As shown in FIG. 3, a plurality of business systems 300 exist, for example, for each business content (for each business workflow) in a company, as shown in FIG. Specific examples of the business system include a take-out application system when employees take out confidential materials from the company, and a purchase application system when employees purchase consumables necessary for work. Hereinafter, when there is no need to distinguish between a plurality of business systems 300a and business systems 300b, they are referred to as business systems 300. In the description of the present embodiment, the business system 300 will be described with two business systems 300a and 300b, but the number of business systems 300 is not limited.

  The extracted personnel information output unit 160 includes a supply personnel information acquisition unit 101 and a generation personnel information registration unit 103. It can be said that the processing performed by the supply personnel information acquisition unit 101 and the generation personnel information registration unit 103 is processing performed by the extraction personnel information output unit 160.

  The supply personnel information acquisition unit 101 acquires supply personnel information supplied (output) by the personnel system 200. Here, the personnel system 200 is managed by, for example, the personnel department of the company. That is, it can be said that the supply personnel information is supplied from a company (organization). Further, the supply personnel information is personnel change information associated with an employee change in the second half of 2010, for example. Therefore, it can be said that the supply personnel information acquisition unit 101 is also a personnel change information acquisition unit.

Here, the personnel information extraction condition storage unit 102 will be described. The personnel information extraction condition storage unit 102 stores personnel information extraction conditions. The personnel information extraction condition includes target personnel system information such as the address and ID of the personnel system 200 from which supply personnel information (personnel transfer information) used by the supply personnel information acquisition unit 101 is acquired. Further, the personnel information extraction condition includes an output setting for the supply personnel information acquisition unit 101 to output the supply personnel information (personnel change information) acquired by the supply personnel information acquisition unit 101. Since the personnel information extraction condition storage unit 102 stores settings for acquiring personnel change information (for example, target personnel system information), it can also be said to be a change information acquisition setting storage unit.
Then, the supply personnel information acquisition unit 101 acquires supply personnel information based on the target personnel system information included in the personnel information extraction conditions stored in the personnel information extraction condition storage unit 102. Further, the supply personnel information acquisition unit 101 should store the supply personnel information into the personnel information storage unit 104 described later based on the output setting included in the personnel information extraction conditions stored in the personnel information extraction condition storage unit 102. HR information is extracted and the extracted HR information is output.

  The generation personnel information registration unit 103 receives the personnel information output from the supply personnel information acquisition unit 101 and outputs the input personnel information for storage in the personnel information storage unit 104 described later. Here, it can be said that the personnel information output by the generation personnel information registration unit 103 is generation personnel information. The generation personnel information will be described later. That is, it can be said that the generation personnel information registration unit 103 registers generation personnel information in the personnel information storage unit 104.

The personnel information storage unit 104 receives the personnel information output by the extracted personnel information output unit 160 (generation personnel information registration unit 103), and stores the input personnel information.
The personnel information storage unit 104 stores personnel information of a plurality of employees (members). If at least one of member identification information (for example, name and user ID) and member attributes (for example, affiliation and job title) included in the personnel information is different, it is stored as different personnel information. Examples of different personnel information are given below.
(1) “A department affiliation, general manager, Mr. T with user ID 001” and “B department affiliation, general manager with user ID 001, Mr. T”
(2) “Department A, General Manager, Mr. T with user ID 001” and “Department A, General Manager, Mr. K with user ID 002”
(3) “A department affiliation, general manager, Mr. T with user ID 001” and “A department affiliation, section manager, user ID 001 T”
The personnel information storage unit 104 stores personnel information over the past, present, and future. This past, present, and future personnel information is referred to as generation personnel information. A personnel information management method for managing generation personnel information is referred to as generation personnel information management.

The personnel information request unit 111 requests acquisition of personnel information stored in the personnel information storage unit 104 from a current personnel information acquisition unit 112 and a postponement personnel information acquisition unit 113 described later. Specifically, the personnel information request unit 111 generates a personnel information acquisition request including the current date, which is the date when requesting acquisition of personnel information, and outputs the generated personnel information acquisition request.
Further, since the personnel information request unit 111 requests the business system 300 to acquire personnel information in order to distribute personnel information, it can also be said to be a distribution execution unit.

  The personnel information output unit 150 includes a current personnel information acquisition unit 112, a postponement personnel information acquisition unit 113, and a generation personnel information acquisition unit 115. It can be said that the process performed by the current personnel information acquisition unit 112, the postponement personnel information acquisition unit 113, and the generation personnel information acquisition unit 115 is a process performed by the personnel information output unit 150.

  The generation personnel information acquisition unit 115 acquires personnel information from the personnel information storage unit 104 in response to requests from the current personnel information acquisition unit 112 and the postponement personnel information acquisition unit 113.

  The current HR information acquisition unit 112 inputs the HR information acquisition request output by the HR information request unit 111, and acquires the acquisition of HR information including the current date included in the HR information acquisition request into the generation HR information acquisition unit 115. Request. Then, according to the request, the personnel information acquired by the generation personnel information acquisition unit 115 is output as current personnel information.

Here, the postponement condition storage unit 114 will be described. The grace condition storage unit 114 stores a grace period in which the authority originally granted to the employee (member) during the effective period is considered to be valid for a predetermined period even after the effective period ends. Then, the grace condition storage unit 114 stores the grace period and the member attribute specifying condition for specifying the member attribute to be applied for the grace period in association with each other.
As described above, the grace period is, for example, a period in which the effective period of authority is extended after the personnel change without depriving the authority of the person to be transferred along with the personnel change.
Since it can be said that the grace condition storage unit 114 stores a setting for acquiring the grace personnel information used in the later-described grace personnel information acquisition unit 113, the grace condition storage unit 114 is also a grace information acquisition setting storage unit. I can say that.

The grace personnel information acquisition unit 113 inputs the personnel information acquisition request output from the personnel information request unit 111, and further inputs a grace period and member attribute specifying conditions stored in the grace condition storage unit 114. Then, the grace personnel information acquisition unit 113 calculates a grace date corresponding to a date that is back by the grace period from the day before the current date included in the personnel information acquisition request.
Here, the effective period including the calculated grace date is hereinafter referred to as “contained effective period”.
Then, the postponement personnel information acquisition unit 113 requests the generation personnel information acquisition unit 115 to acquire personnel information including an expiration date that overlaps the effective content period. Then, the personnel information including the member attribute specified from the member attribute specifying condition associated with the grace date is output as the grace personnel information from the personnel information acquired by the generation personnel information acquisition unit 115 according to the request. A specific example will be described later.

  The combined personnel information output unit 116 inputs the current personnel information output by the personnel information output unit 150 (the current personnel information acquisition unit 112 and the postponement personnel information acquisition unit 113) and the postponement personnel information, and the input current personnel information and The combined personnel information that combines the postponement personnel information is output.

  The distribution setting storage unit 118 includes a distribution information extraction condition, which is a predetermined condition to be referred to when a distribution personnel information distribution unit 117 described later extracts information from combined personnel information, and a distribution personnel information distribution unit 117 stores distribution personnel information. Address information to be referred to when distributing is stored. The distribution information extraction condition and the address information can be said to be a distribution setting that defines a distribution method to the business system 300 used by the distribution personnel information distribution unit 117.

  The distribution personnel information distribution unit 117 inputs the combined personnel information output from the combined personnel information output unit 116, extracts information from the input combined personnel information with reference to a predetermined condition (distribution information extraction condition), and extracts the information Information is distributed to a predetermined address by referring to the address information as distribution personnel information. It can be said that the distribution personnel information distribution unit 117 distributes distribution personnel information to the business system 300 in accordance with the distribution setting stored in the distribution setting storage unit 118.

  Next, with reference to FIGS. 4, 5, 6, 7, 8, 9, 10, 10, 11, 12, 13, 14, and 15, personnel information is stored in the personnel information storage unit 104. FIG. The process until it is stored will be described.

FIG. 4 is a diagram illustrating an example of supply personnel information 400.
For example, as shown in FIG. 4, the supply personnel information 400 includes a user ID 301a, a name 302a, an employee classification 303a, a hire date 304a, an organization ID 305a, an organization name 306a, an extension number 307a, a job title ID 308a, a job title 309a, a start date 310a, and an end. A day 311a, a home telephone number 312a, and a home address 313a. Here, the information constituting the supply personnel information 400 is not limited to the example shown in FIG.

Further, in the processing of the personnel information output device 100, in order to make the explanation easy to understand when the information form changes and needs to be distinguished, in FIG. 4, “user ID 301a, name 302a, employee classification 303a, hire date 304a, The organization ID 305a, organization name 306a, extension number 307a, title ID 308a, title name 309a, start date 310a, end date 311a, home phone number 312a, home address 313a are used. Name 302, employee classification 303, hire date 304, organization ID 305, organization name 306, extension number 307, job title ID 308, job title 309, start date 310, end date 311, home phone number 312 and home address 313 ”. Similarly, when “member identification information 401a, member attribute 402a, valid period 403a” need not be distinguished, “member identification information 401, member attribute 402, valid period 403” is described. The same applies to FIGS. 6 to 8 below.
In addition, the supply personnel information 400 in FIG. 4 is, for example, personnel change information from the first half of 2010 (2010/4/1 to 2010/9/30) to the second half of 2010 (2010/10/1 to 2011/3/31). Is shown. The supply personnel information 400 of FIG. 4 shows only the information of employees who have undergone personnel changes. That is, the supply personnel information 400 in FIG. 4 shows only personnel information that has changed.

In the example of the supply personnel information 400 of FIG. 4, each component will be described.
The user ID 301 is member identification information 401 of an employee (member). If it is not necessary to consider the same family name, the name 302 can be used as the member identification information 401.
The employee classification 303 is information indicating whether the employee is a regular (regular employee) or a dispatch (temporary employee).
The hire date 304 is information indicating the date when the employee joined the company.
The organization ID 305 and the organization name 306 are information indicating employee affiliation. The post ID 308 and the post name 309 are information indicating the post of the employee.
The organization ID 305, the organization name 306, the job title ID 308, and the job title 309 are member attributes 402 of employees (members). The member attribute 402 may be any one of the organization ID 305, the organization name 306, the post ID 308, and the post name 309.
The extension number 307 is an extension telephone number to which the employee belongs.

A period from the start date 310 to the end date 311 is a valid period 403.
In the example of the supply personnel information 400 in FIG. 4, only the changed portion is shown, so that either the start date 310 or the end date 311 is blank in each row of D101 to D104.
In other words, D101 of FIG. 4 indicates that “Jiro Suzuki” is at least the last time (for example, the second half of 2009 (2009/10/1 to 2010/3/31) to the first half of 2010 (2010/4/1 to 2010/9/30). In the case of personnel changes in)), it indicates that the person in charge was a member of “Sales Department Sales Section 1”. D101 in FIG. 4 indicates that “Jiro Suzuki” is no longer “in charge” belonging to “Sales Department Sales Section 1” at “2010/9/30”. In other words, D101 in FIG. 4 indicates that the effective period 403 of authority authorized in response to “Jiro Suzuki” being “in charge” belonging to “Sales Department Sales Section 1” ends.
D102 in FIG. 4 indicates that “Jiro Suzuki” becomes a “section manager” belonging to “Sales Department Sales Section 2” due to this personnel change. Since the user ID 301 (member identification information 401) of D101 and the user ID 301 (member identification information 401) of D102 are the same “user002”, it can be said that “Jiro Suzuki” is the same person. That is, in the example of the supply personnel information 400 in FIG. 4, “Jiro Suzuki” is a “person in charge” belonging to “Sales Department Sales Section 1” until “2010/9/30”, and “2010/10/1”. Indicates that the affiliation has changed from “Sales Department Sales Section 2” to “Section Manager”.
In other words, D102 in FIG. 4 shows that “Jiro Suzuki” starts from “2010/10/1” and the effective period 403 of the authority that is recognized in response to being “section manager” belonging to “sales department sales section 2”. It shows that
Then, “Jiro Suzuki” belongs to “Sales Department Sales Section 2”, and since the date of ending “Section Manager” is undecided, there is no information, and the end date 311 of D102 is blank.
Since the examples of D103 to D104 in FIG. 4 are the same, description thereof is omitted.

  The home telephone number 312 and the home address 313 are information on the employee's home contact information.

FIG. 5 is a diagram illustrating an example of the personnel information extraction condition 405.
The personnel information extraction condition 405 includes target personnel system information 406 and output settings 407.
The example of FIG. 5 uses descriptions (tags) such as “config”, “hr”, “target”, “address”, “port”, “mapping”, “attribute”, “column”, “entry”, and the like. However, this is an example of description, and the description method of the personnel information extraction condition 405 is not limited. In FIG. 5, the description surrounded by “<>” is hereinafter referred to as “tag”.
The personnel information extraction condition 405 is preset by, for example, an administrator of the personnel information output apparatus 100 and stored in the personnel information extraction condition storage unit 102. As shown in FIG. 5, the personnel information extraction condition 405 includes a description of a range (“<config>” to “</ config>”) enclosed by “config” tags.

There are a plurality of personnel systems 200, and each personnel system 200 is assigned an ID. Here, for example, the ID of the personnel system 200a shown in FIG. 4 is “1”, and the ID of the personnel system 200b is “2”.
The personnel information extraction condition 405 can set target personnel system information 406 and output settings 407 for a plurality of personnel systems 200. A range surrounded by “hr” tags (“<hr>” to “</ hr>”) indicates a setting for one personnel system 200.
For example, “<hr id =“ 1 ”>” to “</ hr>” shown in FIG. 5 is a setting for the personnel system 200a with ID = 1. Here, by describing “id =“ 1 ”” in the “hr” tag, the setting of the range enclosed by the “hr” tag is a setting for the personnel system 200a with ID = 1. To clarify.
In the example of FIG. 5, only the setting for one personnel system 200 (HR = 1200 ID system) is described. However, for example, when the setting for the personnel system 200b with ID = 2 is described together, the personnel system with ID = 2 between “</ hr>” and “</ config>” shown in FIG. It is possible to describe settings for 200b.
Here, the “hr” tag means a human resource, and is a description set by, for example, an administrator of the personnel information output apparatus 100 in order to clarify a setting range for one personnel system 200.

The target personnel system information 406 will be described with reference to the example of FIG.
The range (<target> to </ target>) enclosed by the “target” tag is the description of the target personnel system information 406. The target personnel system information 406 is information of the target personnel system 200 from which the supply personnel information acquisition unit 101 acquires the supply personnel information 400 (personnel change information).
The “address” tag sets the IP address (IP address, Internet Protocol Address) of the target personnel system 200, and the “port” tag sets the port number to which the supply personnel information acquisition unit 101 is connected.

Next, the output setting 407 will be described with reference to the example of FIG.
First. A range surrounded by “mapping” tags (<mapping> to </ mapping>) is a description of the output setting 407.
Here, it is assumed that the supply personnel information acquisition unit 101 acquires supply personnel information 400 that is, for example, a data file in CSV format.
The “attribute” tag specifies information extracted by the supply personnel information acquisition unit 101 from the supply personnel information 400. The “column” tag designates a column extracted by the supply personnel information acquisition unit 101 from the supply personnel information 400 in the CSV format. The “entry” tag designates where in the personnel information the column information designated by the “column” tag is used.
Here, the supply setting information 407 will be described together with an example of the personnel information extracted from the supply personnel information 400 by using the output setting 407 shown in FIG.

FIG. 6 is a diagram illustrating an example of new personnel information 410x.
The new personnel information 410x is information that the supply personnel information acquisition unit 101 extracts and outputs from the supply personnel information 400 based on the personnel information extraction condition 405 stored in the personnel information extraction condition storage unit 102.
The generic name of the personnel information 410 output by the supply personnel information acquisition unit 101 is hereinafter referred to as “new personnel information 410x”.
The new personnel information 410x is a general term for individual information such as personnel information 410a to personnel information 410d shown in FIG. In addition, when it is not necessary to distinguish new personnel information 410x, individual personnel information 410a to personnel information 410d, etc., it is expressed as “HR information 410”.
In addition, when it is necessary to distinguish the constituent elements of the new personnel information 410x, the constituent elements are distinguished by adding “x” to the signs of the effective periods 403x, for example.

The correspondence between the supply personnel information 400, the output setting 407, and the new personnel information 410x will be described.
The first line of the output setting 407 shown in FIG. 5 is “<attribute column =“ 1 ”entry =“ userid ”/>” ”, and the information of the column“ 1 ”of the supply personnel information 400 shown in FIG. It is set to be used for the user ID 301x of the new personnel information 410x shown in FIG. Accordingly, the supply personnel information acquisition unit 101 extracts the information in the column “1” of the supply personnel information 400 and outputs it as the user ID 301x of the new personnel information 410x.
Here, in order to make the explanation easy to understand in FIG. 4, a heading such as a user ID 301 a is attached, but in reality, the supply personnel information acquisition unit 101 has a heading of the user ID 301 a of the supply personnel information 400. The column is referred to as a column “1” of the supply personnel information 400.
Similarly, the second line of the output setting 407 shown in FIG. 5 is “<attribute column =“ 2 ”entry =“ username ”/>”, and column “2” of the supply personnel information 400 shown in FIG. Is used for the name 302x of the new personnel information 410x shown in FIG. Accordingly, the supply personnel information acquisition unit 101 extracts the information in the column “2” of the supply personnel information 400 and outputs it as the name 302x of the new personnel information 410x.
Since the description of the third to ninth lines of the output setting 407 in FIG. 5 is the same, the supply personnel information acquisition unit 101 omits the supply personnel information 400 shown in FIG. 4 to the new personnel information 410x shown in FIG. Is extracted and output.

The example of the new personnel information 410x shown in FIG. 6 includes the user ID 301x, name 302x, employee classification 303x, organization ID 305x, organization name 306x, title ID 308x, title name 309x, start date 310x, and end date 311x from the supply personnel information 400. Although it has been extracted, there is no restriction on the items to be extracted.
Similarly to the supply personnel information 400, in the new personnel information 410x, the member identification information 401x is a user ID 301x, and the member attribute 402x includes an organization ID 305x, an organization name 306x, a job title ID 308x, and a job title 309x. The period 403x is a period from the start date 310x to the end date 311x.
Then, the generation personnel information registration unit 103 inputs the new personnel information 410x output from the supply personnel information acquisition unit 101, and registers (stores) the input new personnel information 410x in the personnel information storage unit 104. Output).

The personnel information storage unit 104 stores the new personnel information 410x output by the generation personnel information registration unit 103, but previously stores the existing personnel information 410y output by the generation personnel information registration unit 103 in the past. In other words, the HR information storage unit 104 stores the existing HR information 410y before the generation HR information registration unit 103 inputs (registers) the new HR information 410x to the HR information storage unit 104, that is, the pre-update existing HR information 410y. .
The generic name of the personnel information 410 stored in advance in the personnel information storage unit 104 is distinguished as “existing personnel information 410y”.
Further, when it is necessary to distinguish the constituent elements of the existing personnel information 410y, the constituent elements are distinguished by adding “y” to the signs of the effective period 403y, for example.

FIG. 7 is a diagram illustrating an example of the existing personnel information 410y stored in the personnel information storage unit 104.
The existing personnel information 410y in FIG. 7 has the same configuration as the new personnel information 410x in FIG. 6 except that the information is described in the start date 310 and the end date 311.
For example, in the case of “Taro Tanaka” of “user001” of the personnel information 410e, it has a member attribute of “section manager” of the “general affairs department general affairs section”, and authority according to the “section manager” of the “general affairs department general affairs section” The effective period 403y is “2000/4/1” to “2005/3/31”. The personnel information 410f indicates that “Taro Tanaka” of “user001” is the “General Manager” of “General Affairs Department” from “2005/4/1”. Also, the end date 311y of the personnel information 410f is “9999/12/31” because the end date 311y is not input from the generation personnel information registration unit 103, that is, the “general manager” of the “general affairs department”. Indicates that the state is continuing.
Here, at least until new personnel information 410x is input from the generation personnel information registration unit 103, it can be said that the personnel information 410e is past data and the personnel information 410f is current data. Although not shown, the personnel information storage unit 104 can also store existing personnel information 410y as information on personnel changes in the future. In this way, the personnel information storage unit 104 stores personnel information 410 in which generation personnel information is managed over the past, present, and future.

FIG. 8 is a diagram illustrating an example of the updated personnel information 410z stored in the personnel information storage unit 104.
Here, for example, when there is personnel information 410 with a valid period 403z overlapping, such as “Shiro Watanabe of user004” of personnel information 410h and personnel information 410id, personnel information 410h and personnel information 410id are “the Watanabe of user004”. "Shiro" indicates that he is concurrently serving.

The generic name of the updated personnel information 410 stored in the personnel information storage unit 104 is hereinafter referred to as “updated personnel information 410z”.
In addition, when it is necessary to distinguish that it is a component of the updated personnel information 410z, for example, “z” is also added to the symbol of the component as in the effective period 403z.
The generation personnel information registration unit 103 additionally registers the new personnel information 410x shown in FIG. 6 to the existing personnel information 410y shown in FIG. 7 stored in advance in the personnel information storage unit 104, and the updated personnel information 410z. Remember.
The generation personnel information registration unit 103 registers new personnel information 410x so as not to overlap with existing personnel information 410y when registering new personnel information 410x in the personnel information storage unit 104.

Here, a process in which the generation personnel information registration unit 103 registers the personnel information 410 in the personnel information storage unit 104 will be described with reference to FIGS.
FIG. 9 is a flowchart showing processing when the generation personnel information registration unit 103 registers the personnel information 410 in the personnel information storage unit 104.

FIG. 10 is a diagram illustrating a first specific example of the process of the generation personnel information registration unit 103, where the new personnel information 410x is the end data, and the start date 310y included in the existing personnel information 410y is a new one. It is a figure which shows personnel information 410z after an update in the case of the future from the end date 311x which personnel information 410x contains. ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)
FIG. 11 is a diagram illustrating a second specific example of the process of the generation personnel information registration unit 103, where the new personnel information 410x is the end data, and the start date 310y included in the existing personnel information 410y is a new data Updated personnel information when the end date 311x included in the personnel information 410x is earlier than the end date 311x included in the existing personnel information 410x and the end date 311y included in the new personnel information 410x is in the future. It is a figure which shows 410z. . ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)
FIG. 12 is a diagram showing a third specific example of the process of the generation personnel information registration unit 103, where the new personnel information 410x is the end data, and the start date 310y included in the existing personnel information 410y is a new data The updated personnel information when the end date 311x included in the personnel information 410x is earlier than the end date 311x included in the new personnel information 410x. It is a figure which shows 410z. ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)

FIG. 13 is a diagram illustrating a fourth specific example of the process of the generation personnel information registration unit 103, in which the new personnel information 410x is the start data, the effective period 403y included in the existing personnel information 410y, and the new personnel It is a figure which shows the personnel information 410z after an update when the effective period 403x which the information 410x contains does not overlap. ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)
FIG. 14 is a diagram illustrating a fifth specific example of the process of the generation personnel information registration unit 103, in which new personnel information 410x is start data and new personnel information is included in the effective period 403y included in the existing personnel information 410y. It is a figure which shows the personnel information 410z after an update in case the start date 310x which the information 410x contains overlaps. ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)
FIG. 15 is a diagram illustrating a sixth specific example of the process of the generation personnel information registration unit 103, in which new personnel information 410x is start data, and new personnel information is included in the effective period 403y included in the existing personnel information 410y. It is a figure which shows the personnel information 410z after an update when the end dates 311x which the information 410x includes overlap. ((A) is a diagram showing the relationship between new personnel information 410x and existing personnel information 410y, and (b) is a diagram showing updated personnel information 410z.)

  First, in ST101 of FIG. 9, the generation personnel information registration unit 103 confirms the presence / absence of data of new personnel information 410x (FIG. 6). In the example of FIG. 6, since there are four new data items from personnel information 410a to personnel information 410d, the generation personnel information registration unit 103 determines “YES” four times in the process of ST101, and “NO” at the fifth time. ”And the process is terminated.

In ST102, the generation personnel information registration unit 103 determines whether the new personnel information 410x shown in FIG. 6 is “start data” set with the start date 310x or “end data” set with the end date 311x. To do. Then, the generation personnel information registration unit 103 proceeds to ST121 in the case of “start data” and to ST114 in the case of “end data”.
Specifically, personnel information 410a shown in FIG. 6 is end data, and personnel information 410b is start data.

First, the case where the personnel information 410 is end data will be described.
In ST114, the generation personnel information registration unit 103, for example, the existing personnel information 410y in which the member identification information 401x and the member attribute 402x of the personnel information 410a which is the end data shown in FIG. Search from.
If the target existing personnel information 410y does not exist, the generation personnel information registration unit 103 determines “NO” in ST114, and determines “YES” if it exists.
On the other hand, if generation personnel information registration section 103 determines “YES” in ST114, generation personnel information registration section 103 advances the process to ST111. For example, in the case of the personnel information 410a shown in FIG. 6, the member identification information 401 and the member attribute 402 of the personnel information 410g shown in FIG. 7 match the personnel information 410a shown in FIG. In ST114, “YES” is determined. That is, the existing personnel information 410y in which the member identification information 401x of the new personnel information 410x matches the member attribute 402x is the personnel information 410 indicating the same personnel.

In ST111, the generation personnel information registration unit 103 confirms whether the start date 310y of the existing personnel information 410y is in the future from the end date 311x of the new personnel information 410x.
If the start date 310y of the existing personnel information 410y is later than the end date 311x of the new personnel information 410x, the generation personnel information registration unit 103 determines “YES” in ST111 and advances the process to ST112. If the generation personnel information registration unit 103 determines “NO” in ST111, the process proceeds to ST113.

First, the case where the process proceeds with ST111 to ST112 will be described with reference to FIG.
FIG. 10A shows the relationship between new personnel information 410x and existing personnel information 410y. In FIG. 10A, the start date 310y of the existing personnel information 410y is set to “2011/4/1” and the end date 311y is set to “9999/12/31”. That is, the effective period 403y is “2011/4/1 to 9999/12/31”. The end date 311x of the new personnel information 410x is “2010/10/5”.
In the case of FIG. 10A, the generation personnel information registration unit 103 deletes the existing personnel information 410y in ST112.
Therefore, there is no data as updated personnel information 410z as shown in FIG.
In other words, the existing personnel information 410y is information on personnel changes scheduled in the future, but can be considered as unnecessary information that has not actually undergone personnel changes. Deleted by.

Next, the case where the process proceeds with ST111 to ST113 will be described with reference to FIGS.
In FIG. 11A, the start date 310y of the existing personnel information 410y is set to “2005/4/1”, and the end date 311y is set to “9999/12/31”. The end date 311x of the new personnel information 410x is “2010/09/30”.
In the case shown in FIG. 11A, the generation personnel information registration unit 103 changes the end date 311y of the existing personnel information 410y to the end date 311x of the new personnel information 410x in ST113. That is, the start date 310z of the updated personnel information 410z is set to “2005/4/1”, and the end date 311z is set to “2010/09/30” (FIG. 11B).
6 to 8, the new personnel information 410x is the personnel information 410a in FIG. 6, the existing personnel information 410y is the personnel information 410g in FIG. 7, and the updated personnel information 410z is the figure. 8 personnel information 410ga.
When the end date 311y is set to “9999/12/31”, the information on the end date 311y is not registered originally, so the end date 311x of the new personnel information 410x is registered. However, even when the end date 311y is already set to “2009/10/30”, for example, the new personnel information 410x is given priority as being more correct data than the existing personnel information 410y. Then, the generation personnel information registration unit 103 changes the end date 311y to “2010/09/30”.

In FIG. 12A, the start date 310y of the existing personnel information 410y is set to “2005/4/1” and the end date 311y is set to “2009/09/30”. The end date 311x of the new personnel information 410x is “2010/10/05”.
Compared to FIG. 11 (a), the time positions of the end date 311x and the end date 311y are interchanged. However, as in FIG. 11, the new personnel information 410x is more than the existing personnel information 410y. Priority is given to correct data. Then, the generation personnel information registration unit 103 changes the end date 311y to “2010/10/05”. That is, the start date 310z of the updated personnel information 410z is set to “2005/4/1”, and the end date 311z is set to “2010/10/5” (FIG. 12B).

Next, the case where the personnel information 410 is start data will be described.
In ST121, the generation personnel information registration unit 103, for example, the existing personnel information in which the member identification information 401x and the member attribute 402x of the personnel information 410b which is the end data shown in FIG. The information 410y is searched from the personnel information storage unit 104. Here, the generation personnel information registration unit 103 sets the end date 311x to “9999/12/31” in the case of start data.
When the target existing personnel information 410y does not exist, the generation personnel information registration unit 103 determines “NO” in ST121. If it is determined “NO” in ST121, the generation personnel information registration unit 103 advances the process to ST126 and registers the new personnel information 410x as it is in the personnel information storage unit 104.
That is, when the member identification information 401x and the member attribute 402x of the new personnel information 410x do not match the existing personnel information 410y, the new personnel information 410x indicates a different personnel that does not exist in the existing personnel information 410y. This is personnel information 410 to be shown. Therefore, the generation personnel information registration unit 103 registers the new personnel information 410x as it is in the personnel information storage unit 104 in ST126. That is, the updated personnel information 410z and the new personnel information 410x are the same information.
6 to 8, the new personnel information 410x is the personnel information 410b in FIG. 6, and the updated personnel information 410z is the personnel information 410b in FIG.

On the other hand, the member identification information 401x and the member attribute 402x of the new personnel information 410x match the existing personnel information 410y, but the effective period 403x of the new personnel information 410x is the effective period 403y of the existing personnel information 410y. A case where there is no overlap with FIG.
In FIG. 13A, the start date 310y of the existing personnel information 410y is set to “2005/4/1”, and the end date 311y is set to “2009/09/30”. The start date 310x of the new personnel information 410x is “2010/10/05”, and the end date 311x is “9999/12/31”.
13A, the generation personnel information registration unit 103 leaves the existing personnel information 410y as it is in the personnel information storage unit 104 and adds new personnel information 410x as it is to the personnel information storage unit 104 in ST126. sign up. (FIG. 13B).
As an example of FIG. 13, for example, after an employee is originally a “general manager of the general affairs department”, for example, during the period indicated by the effective period 403 y of the existing personnel information 410 y, and changed to a “manager of the human resources department” due to personnel changes. In this case, it is assumed that the manager of the general affairs department is once again.

On the other hand, the case where the generation personnel information registration unit 103 determines “YES” in ST121 will be described. In that case, the member identification information 401x and the member attribute 402x of the new personnel information 410x match the existing personnel information 410y, and the validity period 403x of the new personnel information 410x is the validity period 403y of the existing personnel information 410y. Duplicate.
In ST122, the generation personnel information registration unit 103 confirms whether the start date 310x of the new personnel information 410x overlaps the valid period 403y of the existing personnel information 410y. The process proceeds to ST123.

A case where the process proceeds from ST122 to ST123 will be described with reference to FIG.
In FIG. 14A, the start date 310y of the existing personnel information 410y is set to “2005/4/1”, and the end date 311y is set to “9999/12/31”. The start date x of the new personnel information 410x is set to “2010/10/5”, and the end date 311x is “9999/12/31”.
In the case shown in FIG. 14A, the generation personnel information registration unit 103 changes the end date 311y of the existing personnel information 410y to the day before the start date 310x of the new personnel information 410x in ST123.
Then, in ST126, the generation personnel information registration unit 103 additionally registers the new personnel information 410x as it is in the personnel information storage unit 104 (FIG. 14B). (Note that there is ST124 between ST123 and ST126, but as will be described later, since new personnel information 410x is prioritized in ST124, the new personnel information 410x is not subject to the processing of ST124. Registered in storage unit 104.)
That is, also in this case, the new personnel information 410x is given priority over the existing personnel information 410y as being correct data, and the valid period 403y of the existing personnel information 410y that overlaps with the new personnel information 410x is deleted.

If the generation personnel information registration unit 103 determines “NO” in ST122, the process proceeds to ST124.
In ST124, the generation personnel information registration unit 103 checks whether or not the end date 311x of the new personnel information 410x overlaps with the valid period 403y of the existing personnel information 410y. Proceed to If there is no overlap, the generation personnel information registration unit 103 registers the new personnel information 410x in the personnel information storage unit 104 as it is.

A case where the process proceeds from ST124 to ST125 will be described with reference to FIG.
In FIG. 15A, the start date 310y of the existing personnel information 410y is set to “2011/4/1”, and the end date 311y is set to “9999/12/31”. The start date 310x of the new personnel information 410x is set to “2010/10/5”, and the end date 311x is “9999/12/31”.
In the case of FIG. 15A, the generation personnel information registration unit 103 deletes the existing personnel information 410y and additionally registers the new personnel information 410x as it is in the personnel information storage unit 104 in ST125 (FIG. 15). (B)).
That is, also in this case, the new personnel information 410x is prioritized as correct data over the existing personnel information 410y, and the existing personnel information 410y that overlaps the new personnel information 410x is deleted.

As described in the processing of ST101, the generation personnel information registration unit 103 performs the above-described processing for all data of the new personnel information 410x.
Then, through the above processing, the generation personnel information registration unit 103 registers new personnel information 410x so as not to overlap with existing personnel information 410y when registering new personnel information 410x in the personnel information storage unit 104. In other words, the generation personnel information registration unit 103 stores the new personnel information 410x in the personnel information storage unit 104 when the existing personnel information 410y including the validity period 403y overlapping the validity period 403x of the new personnel information 410x disappears. Register with.
The personnel information storage unit 104 stores updated personnel information 410z as shown in FIG.

The process until the personnel information 410 is stored in the personnel information storage unit 104 has been described above.
Next, the processing until the personnel information 410 stored in the personnel information storage unit 104 is distributed to the business system 300 is shown in FIG. 16, FIG. 17, FIG. 18, FIG. 23 and FIG.

The personnel information request unit 111 acquires the personnel information 410 to the personnel information output unit 150 (current personnel information acquisition unit 112 and postponement personnel information acquisition unit 113), for example, at a fixed time every day (once a day). Outputs the requested personnel information acquisition request.
Here, the personnel information request unit 111 inputs the current date (current date) from, for example, a built-in clock included in the system unit 910 of the personnel information output apparatus 100, and generates a personnel information acquisition request including the current date. .
Further, for example, when the administrator of the personnel information output device 100 wants to distribute personnel information only to a specific business system 300, information specifying the specific business system 300 (for example, ID of the business system 300) is acquired. It can also be set to be included in the request.

  The current personnel information acquisition unit 112 inputs a personnel information acquisition request including the current date. Then, the current personnel information acquisition unit 112 notifies the generation personnel information acquisition unit 115 of the updated personnel information 410z that is included in the expiration date 403z in the updated personnel information 410z stored in the personnel information storage unit 104. Requests acquisition of information 410z.

  The generation personnel information acquisition unit 115 acquires the updated personnel information 410z from the personnel information storage unit 104 in response to a request from the current personnel information acquisition unit 112, and acquires the acquired updated personnel information 410z as the current personnel information acquisition unit 112. Output for.

  The current personnel information acquisition unit 112 receives the updated personnel information 410z output from the generation personnel information acquisition unit 115, and outputs the input updated personnel information 410z as current personnel information.

FIG. 16 is a diagram illustrating an example of the current personnel information 420.
Here, the current date and time is assumed to be “2010/10/5”. In this case, the generation personnel information acquisition unit 115 acquires only the updated personnel information 410z in which “2010/10/5” is included between the start date 310z and the end date 311z of the updated personnel information 410z. Therefore, in the case of “user001” in FIG. 8, the generation personnel information acquisition unit 115 does not acquire the personnel information 410e record of “General Manager of General Affairs Department”, but only the personnel information 410f of “General Manager of General Affairs Department”. To get.
Since each component of the current personnel information 420 is the same as the updated personnel information 410z, description thereof is omitted.

FIG. 17 is a diagram illustrating an example of the grace condition 421 stored in the grace condition storage unit 114.
The postponement condition 421 includes a member attribute specifying condition 422 and a postponement period 423.
The example of FIG. 17 uses descriptions (tags) such as “config”, “system”, “condition”, “length”, etc., but is an example of the description, and the description method of the grace condition 421 is not limited. . In FIG. 17, the description surrounded by “<>” is hereinafter referred to as “tag”.
The grace condition 421 is set in advance by, for example, an administrator of the personnel information output apparatus 100 and stored in the grace condition storage unit 114. As shown in FIG. 17, the postponement condition 421 includes a description of a range (“<config>” to “</ config>”) surrounded by “config” tags.

The grace condition 421 is a setting for personnel information 410 distributed to the business system 300. There are a plurality of business systems 300, and each business system 300 is assigned an ID. Here, for example, the ID of the business system 300a shown in FIG. 4 is “1”, and the ID of the business system 300b is “2”.
The grace condition 421 can set a member attribute specifying condition 422 and a grace period 423 for a plurality of business systems 300. A range surrounded by “system” tags (“<system>” to “</ system>”) indicates a setting for one business system 300.
For example, “<system id =“ 1 ”>” to “</ system>” shown in FIG. 17 is a setting for the business system 300a with ID = 1. Here, by describing “id =“ 1 ”” in the “system” tag, the setting within the range enclosed by the “system” tag is a setting for the business system 300a with ID = 1. To clarify.
In the example of FIG. 17, settings for two business systems 300 (ID = 1 business system 300a and ID = 2 business system 300b) are described.

The member attribute specifying condition 422 specifies the member attribute 402 of the employee who is to have the grace period 423 for the business system 300 to which the grace period 423 is applied.
The member attribute specifying condition 422 is specified by a “condition” tag.
The grace period 423 is specified by a “length” tag.

For example, in the business system 300a with ID = 1, the member attribute specifying condition 422a is “userposition> = K” indicating the section manager or higher, and the grace period 423a is “6y” indicating 6 years. For example, when the administrator of the personnel information output apparatus 100 wants to set a plurality of member attribute specifying conditions 422 and a grace period 423 for one business system 300, for example, as shown in FIG. Two settings are made for the second business system 300b.
Moreover, as the member attribute specifying condition 422, only the condition for the post ID 308 is set in the example of FIG. 17, but the setting for the organization ID 305 is also possible.

Next, the processing of the postponement personnel information acquisition unit 113 will be described.
FIG. 18 is a flowchart illustrating processing performed by the postponement personnel information acquisition unit 113 and the generation personnel information acquisition unit 115.
First, the postponement personnel information acquisition unit 113 starts processing by inputting a personnel information acquisition request including the current date from the personnel information request unit 111.
In ST201, the postponement personnel information acquisition unit 113 inputs the postponement condition 421 stored in the postponement condition storage unit 114.

For example, the administrator of the personnel information output apparatus 100 may specify the ID of the business system 300 in the personnel information acquisition request so that the personnel information is distributed only to the specific business system 300. Assuming such a case, the postponement personnel information acquisition unit 113 performs the processes of ST211 to ST212.
In ST 211 to ST 212, the grace personnel information acquisition unit 113 confirms whether the ID of the business system 300 set in the grace condition 421 corresponds to the ID of the business system 300 set in the personnel information acquisition request. Since the grace condition 421 is set for a plurality of business systems 300 as shown in FIG. 17, all the settings included in the grace condition 421 are confirmed by the repeated processing of ST 211 to ST 212.
When the ID of the business system 300 set in the grace condition 421 does not correspond to the ID of the business system 300 set in the personnel information acquisition request, the grace personnel information acquisition unit 113 sets the empty personnel information 410 in ST231. Output.

If the ID of the business system 300 is not specified in the personnel information acquisition request, or if there is a corresponding grace condition 421, the grace personnel information acquisition unit 113 advances the process to ST213.
In ST213, the grace personnel information acquisition unit 113 calculates a grace date corresponding to a date that is backed by the grace period 423 from the previous day of the current date, and sets a content effective period including the calculated grace date. Then, the postponement personnel information acquisition unit 113 requests the generation personnel information acquisition unit 115 to acquire the updated personnel information 410z including the effective period 403z that overlaps the inclusion effective period.
Specifically, the case where the postponement personnel information acquisition unit 113 outputs postponement information for the setting of the business system 300a with ID = 1 in the postponement condition 421 (FIG. 17) will be described.
Assuming that the current date is “2010/10/5”, since the grace period 423 is “6 years”, the grace date is “2004/10/5”, and the effective content period is “2004/10”. / 5 to 2010/10/4 ".
In the example of the updated personnel information 410z in FIG. 8, since the validity period 403z of all cases overlaps with “2004/10/5 to 2010/10/4”, the generation personnel information acquisition unit 115 is shown in FIG. All the updated personnel information 410z is acquired and output.

The postponement personnel information acquisition unit 113 receives the personnel information 410 output by the generation personnel information acquisition unit 115 and performs the processes of ST221 to ST223.
In ST222, the postponement personnel information acquisition unit 113 confirms whether or not the member attribute 402 included in the input personnel information 410 satisfies the member attribute specifying condition 422.
Specifically, in the setting of the business system 300a with ID = 1 in the postponement condition 421 (FIG. 17), the member attribute specifying condition 422 is “section manager or higher”.
Therefore, the postponement personnel information acquisition unit 113 extracts the personnel information 410 including the member attribute 402z of “section manager or higher” and sets it as an output target (ST223).
Grace personnel information acquisition section 113 confirms whether or not member attribute specifying condition 422 is satisfied for all input personnel information 410 (ST221), and postpones personnel information 410 satisfying member attribute specifying condition 422. Output as personnel information (ST231).

FIG. 19 is a diagram illustrating an example of the postponement personnel information 425.
Since the postponement personnel information acquisition unit 113 outputs only the personnel information 410 whose title 309 is “department manager or section manager” as the postponement personnel information 425, it is as shown in FIG.
Since each component of the postponement personnel information 425 is the same as the updated personnel information 410z, description thereof is omitted.

Next, processing of the combined personnel information output unit 116 will be described with reference to FIGS. 20 and 21. FIG.
FIG. 20 is a flowchart showing the processing of the combined personnel information output unit 116.
FIG. 21 is a diagram illustrating a first example of the combined personnel information 426.
FIG. 22 is a diagram illustrating a second example of the combined personnel information 426.

Combined personnel information output section 116 receives current personnel information 420 output by current personnel information acquisition section 112 (ST301).
Further, combined personnel information output unit 116 receives postponement personnel information 425 output by postponement personnel information acquisition unit 113 (ST302).
Thereafter, the combined personnel information output unit 116 deletes information that overlaps between the current personnel information 420 and the postponement personnel information 425. More specifically, the combined personnel information output unit 116 includes the same member identification information 401 (user ID 301) and member attributes 402 (organization ID 305, post ID 308) as the postponed personnel information 425. It is confirmed whether there is current personnel information 420 having the same combination (ST312). Then, the combined personnel information output unit 116 outputs the postponement personnel information 425 in which the combination of the member identification information 401 and the member attribute 402 is different from the current personnel information 420 (ST313). The combined personnel information output unit 116 repeatedly performs processing for all of the input postponement personnel information 425 (ST311), combines the postponement personnel information 425 that is the output target and the current personnel information 420, and combines the human resources information 426. Output as.

The first example of the combined personnel information 426 shown in FIG. 21 is deleted because the internal personnel information 410f and the personnel information 410b of the postponement personnel information 425 shown in FIG. 19 overlap with the current personnel information 420. .
In the second example of the combined personnel information 426 shown in FIG. 22, the start date 310 and the end date 311 are deleted from the first example of the combined personnel information 426 shown in FIG. For example, the administrator of the personnel information output apparatus 100 regards the information on the start date 310 and the end date 311 as unnecessary in the business system 300 and deletes the start date 310 and the end date 311 in the combined personnel information output unit 116. Can be set.

Next, processing of the distribution personnel information distribution unit 117 will be described with reference to FIGS.
FIG. 23 is a diagram illustrating an example of the distribution setting 427 stored in the distribution setting storage unit 118.
FIG. 24 is a diagram illustrating an example of the distribution personnel information 430.

The distribution setting 427 includes address information 428 and distribution information extraction conditions 429.
In the example of FIG. 23, descriptions (tags) such as “config”, “system”, “path”, “mapping”, “column”, “entry”, etc. are used. There is no limitation on the description method of 427. In FIG. 23, the description surrounded by “<>” is hereinafter referred to as “tag”.
The distribution setting 427 is set in advance by, for example, an administrator of the personnel information output device 100 and stored in the distribution setting storage unit 118. As shown in FIG. 23, the delivery setting 427 includes a description of a range (“<config>” to “</ config>”) surrounded by “config” tags.

The distribution setting 427 is a setting for personnel information 410 distributed to the business system 300. As described above, there are a plurality of business systems 300, and each business system 300 is assigned an ID.
The distribution setting 427 can set address information 428 and distribution information extraction conditions 429 for a plurality of business systems 300. A range surrounded by “system” tags (“<system>” to “</ system>”) indicates a setting for one business system 300.
For example, “<system id =“ 1 ”>” to “</ system>” shown in FIG. 23 is a setting for the business system 300a with ID = 1. Here, by describing “id =“ 1 ”” in the “system” tag, the setting within the range enclosed by the “system” tag is a setting for the business system 300a with ID = 1. To clarify.
In the example of FIG. 23, settings for two business systems 300 (a business system 300a with ID = 1 and a business system 300b with ID = 2) are described.

In the present embodiment, the distribution personnel information distribution unit 117 distributes distribution personnel information 430 to a designated business system 300 in a CSV format file.
The address information 428 of the distribution destination business system 300 is specified by a “path” tag. The address information 428 includes an IP address and an output destination path (directory).
The distribution information extraction condition 429 is specified by a range (“<mapping>” to “</ mapping>”) surrounded by “mapping” tags.
Specifically, the setting for the business system 300a with ID = 1 in FIG. 23 is a setting for outputting a CSV-format file “data.csv” to “¥¥ 10.987.54 ¥ load ¥”. is there. The setting example of the distribution information extraction condition 429a in FIG. 23 is as follows: user ID 301 in the first column of “data.csv”, organization ID 305 in the second column, name 302 in the third column, organization name 306 in the fourth column It is a setting to output.

The distribution personnel information distribution unit 117 receives the combined personnel information 426 output from the combined personnel information output unit 116, generates the distribution personnel information 430 based on the distribution setting 427 stored in the distribution setting storage unit 118, Delivered to the business system 300.
FIG. 24 shows an example of the distribution personnel information 430 generated by the distribution personnel information distribution unit 117 based on the setting for the business system 300a with ID = 1 in FIG.
In the example of the distribution personnel information 430 shown in FIG. 24, items (user ID, organization ID, name, organization name) are arranged in the order set in the distribution information extraction condition 429a of FIG. It has become.
The business system 300a with ID = 1 receives the distribution personnel information 430 from the distribution personnel information distribution unit 117 via, for example, the LAN 942.

According to the present embodiment, the personnel information output device 100 can distribute not only the current personnel information 420 but also the postponed personnel information 425.
In addition, the personnel information output device 100 according to the present embodiment can distribute the postponement personnel information 425 in consideration of the postponement period 423 in accordance with the requirements of the business system 300 that is the delivery destination. That is, the personnel information output device 100 according to the present embodiment can output personnel information whose grace period is appropriately changed according to a system that uses personnel information.
The personnel information output apparatus 100 according to the present embodiment permits the duplication of the validity period 403 of authority corresponding to different organizations and positions even for the same employee. The personnel information output apparatus 100 according to the present embodiment can distribute the postponement personnel information 425 by acquiring the postponement personnel information 425 considering the postponement period 423 at the time of distribution from the personnel information storage unit 104.
In addition, the personnel information output device 100 according to the present embodiment can set a plurality of conditions other than the period when acquiring the postponement personnel information 425. The personnel information output apparatus 100 according to the present embodiment can cope with individual grace period settings in which, for example, the authority application period for one month is extended and only the manager of the section A wants to extend it for another month. .
Since the personnel information output apparatus 100 according to the present embodiment can change the grace period 423 immediately only by changing the setting of the grace condition 421, the grace period 423 can be changed with fewer steps.

Although supply personnel information 400 in FIG. 4 shows only personnel information that has changed, supply personnel information 400 may be all data including personnel information that has not changed.
FIG. 25 is a diagram showing a configuration of the personnel information output device 100 when the supply personnel information 400 is all case data.
The only difference between FIG. 25 and FIG. 3 is that the difference calculation condition storage unit 122 is added to FIG.

FIG. 26 is a diagram showing an example of supply personnel information 400 in the case of all case data. Here, the illustration of the hire date 304, the extension number 307, the home telephone number 312 and the home address 313 shown in FIG. 4 is omitted.
The personnel system 200 outputs, for example, personnel information 410 of all employees regardless of whether or not personnel changes. Here, the personnel information 410 is, for example, the latest information when the personnel system 200 is output.

FIG. 27 is a diagram illustrating an example of the previous supply personnel information 400 stored in the difference calculation condition storage unit 122.
The difference calculation condition storage unit 122 stores all data of supply personnel information 400 output from the personnel system 200 last time.
The supply personnel information acquisition unit 101 then stores all data of the supply personnel information 400 output from the personnel system 200 last time stored in the difference calculation condition storage unit 122 and the latest supply personnel information output by the personnel system 200. By performing a difference calculation with 400, it is possible to extract only the supply personnel information 400 having changed. The changed supply personnel information 400 is hereinafter referred to as “difference data”.

Specifically, first, the supply personnel information acquisition unit 101 inputs the supply personnel information 400 (FIG. 26) output from the personnel system 200. Then, the supply personnel information acquisition unit 101 performs a difference calculation on the supply personnel information 400 including the combination of the member identification information 401 (user ID 301) and the member attributes 402 (organization ID 305, job title ID 308), which is the same as D201 (FIG. 26). It is searched whether the condition storage unit 122 stores it.
Then, as a result of the search, the supply personnel information acquisition unit 101 confirms that the personnel calculation information of D301 (FIG. 27) exists in the difference calculation condition storage unit 122. Further, the supply personnel information acquisition unit 101 confirms whether the start date 310 and the end date 311 are the same in D201 (FIG. 26) and D301 (FIG. 27). If they are the same, the supply personnel information acquisition unit 101 does not output the difference data. On the other hand, if either the start date 310 or the end date 311 is different, the supply personnel information acquisition unit 101 outputs the data of the supply personnel information 400 output by the personnel information 410 as difference data.
For example, since D201 (FIG. 26) and D301 (FIG. 27) are the same information, the supply personnel information acquisition unit 101 does not output difference data. On the other hand, since the start date 310 and the end date 311 are different between D202 (FIG. 26) and D302 (FIG. 27), the supply personnel information acquisition unit 101 outputs the information of D202 (FIG. 26) as difference data.
Further, among the supply personnel information 400 (FIG. 26) output from the personnel system 200, the member identification information 401 and the member attribute 402 included in the supply personnel information 400 (FIG. 27) stored in the difference calculation condition storage unit 122. For the different combinations, the supply personnel information acquisition unit 101 outputs the difference data.
Then, the supply personnel information acquisition unit 101 outputs the latest supply personnel information 400 output from the personnel system 200 shown in FIG. 26, and the previous supply personnel information 400 stored in the difference calculation condition storage unit 122 shown in FIG. The difference calculation result is the same as the supply personnel information 400 shown in FIG.
As described above, the personnel information output device 100 can cope with data output from the personnel system 200, whether it is all-case data or differential data (only personnel information with changes).

Embodiment 2. FIG.
In the present embodiment, an example of the personnel information output device 100 having a function of narrowing down personnel information 410 to be output by the personnel information output unit 150 will be described.

FIG. 28 is a diagram illustrating a configuration of the personnel information output device 100 including the personnel information narrowing-down condition storage unit 121.
The personnel information refinement condition storage unit 121 stores personnel information refinement conditions for narrowing down the personnel information 410 to be output by the personnel information output unit 150.
Except for the personnel information narrowing-down condition storage unit 121, the description is omitted because it is the same as the first embodiment.

FIG. 29 is a diagram illustrating an example of the personnel information filtering condition 431.
The example of FIG. 29 uses descriptions (tags) such as “config”, “system”, and “condition”, but is an example of the description, and there is no limitation on the description method of the personnel information narrowing condition 431. In FIG. 29, the description surrounded by “<>” is hereinafter referred to as “tag”.
The personnel information filtering condition 431 is set in advance by, for example, the administrator of the personnel information output device 100 and stored in the personnel information filtering condition storage unit 121. As shown in FIG. 29, the personnel information filtering condition 431 includes a description of a range (“<config>” to “</ config>”) surrounded by “config” tags.

The personnel information filtering condition 431 is a setting for personnel information 410 distributed to the business system 300. As described above, there are a plurality of business systems 300, and each business system 300 is assigned an ID.
The personnel information filtering condition 431 can be set for a plurality of business systems 300. A range surrounded by “system” tags (“<system>” to “</ system>”) indicates a setting for one business system 300.
For example, “<system id =“ 1 ”>” to “</ system>” shown in FIG. 29 is a setting for the business system 300a with ID = 1. Here, by describing “id =“ 1 ”” in the “system” tag, the setting within the range enclosed by the “system” tag is a setting for the business system 300a with ID = 1. To clarify.
In the example of FIG. 29, settings for two business systems 300 (a business system 300a with ID = 1 and a business system 300b with ID = 2) are described.

Specifically, in the setting for the business system 300a with ID = 1 in FIG. 29, the “condition” tag specifies “org == G20 *”. “Org == G20 *” means that the organization ID 305 starts with “G20”.
When a plurality of conditions are specified for one business system, it can be specified by a plurality of “system” tags and “condition” tags as in the setting for the business system 300b with ID = 2.

Next, processing of the personnel information output device 100 according to the second embodiment will be described with reference to FIGS. 30, 31, and 32.
The processing until the personnel information storage unit 104 stores the personnel information 410 on which generation personnel information is managed is the same as that in the first embodiment.
Thereafter, the personnel information request unit 111 receives the personnel information narrowing condition 431 stored in the personnel information narrowing condition storage unit 121 and generates a personnel information acquisition request including the input personnel information narrowing condition 431. Then, the personnel information request unit 111 outputs a personnel information acquisition request including the generated personnel information filtering condition 431.
The personnel information output unit 150 (current personnel information acquisition unit 112 and postponement personnel information acquisition unit 113) inputs a personnel information acquisition request including the personnel information filtering condition 431 output by the personnel information request unit 111.

Then, the personnel information output unit 150 (current personnel information acquisition unit 112 and postponement personnel information acquisition unit 113) outputs the personnel information 410 that matches the personnel information filtering condition 431 included in the input personnel information acquisition request as the output personnel information. 410.
That is, the generation personnel information acquisition unit 115 acquires the personnel information 410 shown in FIG. Then, the current personnel information acquisition unit 112 includes data that matches the personnel information filtering condition 431 in the personnel information 410 (FIG. 16) acquired by the generation personnel information acquisition unit 115 (in the example of FIG. 29, the organization ID 305 is “G20”). Only those starting with "" are input, and the current personnel information 420 is output.

FIG. 30 is a diagram illustrating an example of the current personnel information 420 that matches the personnel information filtering condition 431. The example of FIG. 30 is an example of the current personnel information 420 output by the current personnel information acquisition unit 112 using the setting for the business system 300a with ID = 1 in the personnel information filtering condition 431 (FIG. 29).
As in the first embodiment, the current date is assumed to be “2010/10/5”. Since the personnel information filtering condition 431 is that the organization ID 305 starts with “G20”, the data of the personnel information 410f (data of the organization ID 305 “G100”) is lost compared to the current personnel information 420 of FIG. .

  Similarly, the generation personnel information acquisition unit 115 acquires the personnel information 410 shown in FIG. 19 from the personnel information storage unit 104 in response to a request from the postponement personnel information acquisition unit 113 as in the first embodiment. Then, the grace personnel information acquisition unit 113 includes data (in the example of FIG. 29, the organization ID 305 is “G20” that matches the personnel information filtering condition 431 in the personnel information 410 (FIG. 19) acquired by the generation personnel information acquisition unit 115. Only those that start with "" and output as postponement personnel information 425.

FIG. 31 is a diagram illustrating an example of postponement personnel information 425 that matches the personnel information filtering condition 431. The example of FIG. 31 is an example of the postponement personnel information 425 output by the postponement personnel information acquisition unit 113 using the setting for the business system 300a with ID = 1 in the personnel information narrowing condition 431 (FIG. 29).
As in the first embodiment, the current date is assumed to be “2010/10/5”. Since the personnel information filtering condition 431 is that the organization ID 305 starts with “G20”, the data of the personnel information 410e (data of the organization ID 305 “G101”) and the personnel information 410f are compared with the postponement personnel information 425 of FIG. (Data with organization ID 305 “G100”) is lost.

Hereinafter, the processing by the combined personnel information output unit 116 and the distribution personnel information distribution unit 117 is the same as that in the first embodiment, and thus the description thereof is omitted.
FIG. 32 is a diagram illustrating an example of combined personnel information 426 that matches the personnel information filtering condition 431. Since the current personnel information 420 that matches the personnel information filtering condition 431 and the postponement personnel information 425 that matches the personnel information filtering condition 431 are combined, the data is less than that in FIG. The distribution personnel information 430 also has the number of data according to the combined personnel information 426.

  In the personnel information output apparatus 100 according to the present embodiment, the distribution personnel information 430 can be narrowed down according to the requirements of the business system 300 by using the personnel information narrowing condition 431. The personnel information output device 100 according to the present embodiment can distribute the distribution personnel information 430 more adapted to the requirements of the business system 300.

In summary, in this embodiment,
Member identification information 401 for identifying members constituting the organization, member attributes 402 indicating the attributes of the members in the organization, and the validity period of the authority granted to the members according to the member attributes 402 If the member identification information 401 and the member attribute 402 are different, at least one of the member identification information 401 and the member attribute 402 is stored as different personnel information 410. A personnel information storage unit 104 for storing;
In the effective period 403, the authority granted to the members is considered to be valid for a predetermined period after the effective period 403 ends, and the configuration to which the grace period 423 is applied A grace condition storage unit 114 that stores a member attribute specifying condition 422 for specifying a member attribute in association with each other,
Requesting acquisition of the personnel information 410 stored in the personnel information storage unit 104 and generating a personnel information acquisition request including a current date that is a date at the time of requesting acquisition of the personnel information 410 A personnel information request unit 111 for outputting a personnel information acquisition request;
The personnel information acquisition request output by the personnel information request unit 111 is input, the grace period 423 and the member attribute specifying condition 422 stored by the grace condition storage unit 114 are input, and the personnel information acquisition request A grace date corresponding to a date that is backed by the grace period 423 from the previous day of the current date included is calculated, and the content effective period that is the effective period 403 including the calculated grace date is associated with the content effective period The personnel information 410 including the member attribute 402 specified by the member attribute specifying condition 422 associated with the grace date and the member attribute 402 is obtained from the personnel information storage unit 104; A personnel information output device 10 comprising a personnel information output unit 150 that outputs the acquired personnel information 410 as postponed personnel information 425. It was described.
In the present embodiment,
The personnel information output unit 150 includes:
The postponement personnel information 425 is output, and the personnel information 410 including the current date in the validity period 403 is acquired from the personnel information storage unit 104, and the acquired personnel information 410 is output as current personnel information 420. And
The personnel information output device 100 further includes:
The current personnel information 420 output from the personnel information output unit 150 and the postponement personnel information 425 are input, and the combined personnel information 426 obtained by combining the input current human resource information 420 and the postponement personnel information 425 is output. Combined personnel information output unit 116
The personnel information output device 100 characterized by comprising:
In the present embodiment,
The personnel information output device 100 further includes:
The combined personnel information output unit 116 outputs the combined personnel information 426, extracts information with reference to a predetermined condition from the input combined personnel information 426, and sets the extracted information as distribution personnel information 430 as an address. A distribution personnel information distribution unit 117 that distributes to a predetermined address by referring to the information 428;
The distribution personnel information distribution unit 117 distributes the distribution personnel information 430, and the distribution personnel information distribution unit 117 distributes the distribution personnel information 430, which is a predetermined condition to be referred to when the information is extracted from the combined personnel information 426. The personnel information output apparatus 100 including the distribution setting storage unit 118 that stores the address information 428 that is referred to when the information is stored has been described.
In the second embodiment,
The personnel information output device 100 further includes:
Personnel information filtering condition storage unit 121 that stores personnel information filtering conditions 431 for narrowing down the personnel information 410 to be output by the personnel information output unit 150.
With
The personnel information request unit 111 includes:
The personnel information refinement condition 431 stored in the personnel information refinement condition storage unit 121 is input, the personnel information acquisition request including the input personnel information refinement condition 431 is generated, and the created personnel information refinement condition 431 is included. Outputting the personnel information acquisition request;
The personnel information output unit 150 includes:
The personnel information acquisition request including the personnel information refinement condition 431 output by the personnel information request unit 111 is input, and the personnel information 410 that matches the personnel information refinement condition 431 included in the input personnel information acquisition request is obtained. The personnel information output device 100, which is characterized by being the personnel information 410 to be output, has been described.
In the present embodiment, the personnel information output device 100 further includes:
A personnel information extraction condition storage unit 102 for storing a personnel information extraction condition 405 for extracting the personnel information 410 stored in the personnel information storage unit 104 as the personnel information 410 from the supply personnel information 400 supplied by the organization;
The personnel information extraction condition 405 and the supply personnel information 400 stored in the personnel information extraction condition storage unit 102 are input, and the personnel information storage is performed based on the personnel information extraction condition 405 from the input supply personnel information 400. An extracted personnel information output unit 160 that extracts the personnel information 410 to be stored in the unit 104 and outputs the extracted personnel information 410;
The personnel information storage unit 104 includes:
The personnel information output device 100 is described in which the personnel information 410 output by the extracted personnel information output unit 160 is input and the input personnel information 410 is stored.

Furthermore, in other words, in the present embodiment, a method for distributing personnel information 410 including the following means to the business system 300 (device) has been described.
(1) A personnel information storage unit 104 (a personnel information storage unit) that manages personnel information 410 with a valid period 403.
(2) A personnel information request unit 111 (distribution process start unit) that designates the business system 300 to be distributed and starts the distribution process.
(3) A current personnel information acquisition unit 112 (current information acquisition unit) that acquires current personnel information 420 (personal information at the current time) from the personnel information storage unit 104 (personal information storage unit).
(4) A postponement personnel information acquisition unit 113 (a postponement information acquisition unit) that acquires postponement personnel information 425 (personnel information for a postponement period) from the personnel information storage unit 104 (personal information storage unit).
(5) Combined personnel information output to create combined personnel information 426 (information for distribution) by combining current personnel information 420 (personal information at the current time) and postponement personnel information 425 (personal information for the grace period) Unit 116 (distribution information generation unit).
(6) A distribution setting storage unit 118 (distribution information storage unit) that stores a distribution setting 427 (information regarding a distribution method) for the business system 300 as a distribution destination.
(7) A distribution personnel information distribution unit 117 (distribution information distribution unit) that distributes distribution personnel information 430 (distribution information) to the business system 300 according to distribution setting 427 (according to distribution information).
In the present embodiment, the system further includes the following means to centrally manage the personnel information 410 and distribute it to the business system 300 (device).
(1) A supply personnel information acquisition unit 101 (transfer information acquisition setting storage unit) that acquires supply personnel information 400 (personnel change information) from the personnel system 200.
(2) A generation personnel information registration unit 103 that registers personnel transfer information in the personnel information storage unit 104 (personal information storage unit) as personnel information 410 with a validity period 403.

As already described, the personnel information output device 100 shown in the first embodiment includes an output device such as a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and the like. The computer includes a display device, a communication board, and the like.
Then, as described above, the functions indicated as “˜units” are realized using these processing devices, storage devices, input devices, and output devices.

  100 personnel information output device, 101 supply personnel information acquisition unit, 102 personnel information extraction condition storage unit, 103 generation personnel information registration unit, 104 personnel information storage unit, 111 personnel information request unit, 112 current personnel information acquisition unit, 113 postponement personnel Information acquisition unit, 114 postponement condition storage unit, 115 generation personnel information acquisition unit, 116 combined personnel information output unit, 117 distribution personnel information distribution unit, 118 distribution setting storage unit, 121 personnel information narrowing condition storage unit, 122 difference calculation condition storage Department, 150 personnel information output section, 160 extracted personnel information output section, 200 personnel system, 300 business system, 301 user ID, 302 name, 303 employee classification, 304 hire date, 305 organization ID, 306 organization name, 307 extension number, 308 Title ID, 309 Title, 310 Start date, 311 End date, 312 Home phone number, 313 Home address, 400 Supply personnel information, 401 Member identification information, 402 Member attribute, 403 Valid period, 405 Personnel information extraction condition, 406 Target personnel system information, 407 Output setting, 410 Personnel Information, 410x New personnel information, 410y Existing personnel information, 410z Updated personnel information, 420 Current personnel information, 421 Grace conditions, 422 Member attribute specification conditions, 423 Grace period, 425 Grace personnel information, 426 Combined personnel information 427 Distribution setting, 428 Address information, 429 Distribution information extraction condition, 430 Distribution personnel information, 431 Personnel information filtering condition, 901 Display device, 902 Keyboard, 903 Mouse, 904 FDD, 905 Compact disk device, 906 Printer device, 907 CANA device, 910 system unit, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk device, 921 operating system, 922 window system, 923 program group, 924 file group, 931 telephone, 932 facsimile Machine, 940 Internet, 941 gateway, 942 local area network.

Claims (7)

Corresponding member identification information for identifying members constituting the organization, member attributes indicating attributes of the members in the organization, and valid periods of authority granted to the members according to the member attributes In addition, including a plurality of personnel information of the member in the organization, if at least one of the member identification information and the member attribute is different, a personnel information storage unit that stores as different personnel information,
In the effective period, the authority granted to the member specifies a grace period that is continuously considered valid for a predetermined period after the effective period ends, and the member attribute to be applied to the grace period A grace condition storage unit for storing the member attribute specifying conditions to be associated with each other;
Requesting acquisition of the personnel information stored in the personnel information storage unit, generating a personnel information acquisition request including a current date that is a date when requesting acquisition of the personnel information, and acquiring the generated personnel information A personnel information requesting section for outputting the request;
Input the personnel information acquisition request output by the personnel information request unit, input the grace period stored in the grace condition storage unit and the member attribute specifying condition, and the current information included in the personnel information acquisition request Calculate the grace date corresponding to the date that is backed by the grace period from the previous day of the date, the content effective period that is the effective period including the calculated grace date, and the member attribute associated with the content effective period The personnel information including the member attribute specified from the member attribute specification condition associated with the grace date is acquired from the personnel information storage unit, and the acquired personnel information is output as the grace personnel information. A personnel information output device comprising a personnel information output unit that performs the operation. The personnel information output unit
The postponement personnel information is output, and the personnel information including the current date in the validity period is acquired from the personnel information storage unit, and the acquired personnel information is output as current personnel information,
The personnel information output device further includes:
The combined personnel information output unit that inputs the current personnel information output by the personnel information output unit and the postponement personnel information, and outputs combined personnel information obtained by combining the input current personnel information and the postponement personnel information. The personnel information output device according to claim 1, further comprising: The personnel information output device further includes:
The combined personnel information output unit outputs the combined personnel information, extracts information with reference to a predetermined condition from the input combined personnel information, and refers to the address information using the extracted information as distribution personnel information A distribution personnel information distribution unit that distributes to a predetermined address,
The distribution personnel information distribution unit refers to a distribution information extraction condition that is a predetermined condition to be referred to when extracting information from the combined personnel information, and the distribution personnel information distribution unit refers to when the distribution personnel information is distributed. The personnel information output device according to claim 2, further comprising a distribution setting storage unit that stores address information. The personnel information output device further includes:
A personnel information refinement condition storage unit for storing personnel information refinement conditions for narrowing down the personnel information to be output by the personnel information output unit;
The personnel information request section
Input the personnel information filtering condition stored in the personnel information filtering condition storage unit, generate the personnel information acquisition request including the input personnel information filtering condition, and acquire the personnel information including the generated personnel information filtering condition Output the request,
The personnel information output unit
The personnel information acquisition request including the personnel information refinement condition output by the personnel information request unit is input, and the personnel information that matches the personnel information refinement condition included in the input personnel information acquisition request is output as the output target 4. The personnel information output device according to claim 2, wherein the personnel information is output as personnel information. The personnel information output device further includes:
A personnel information extraction condition storage unit for storing personnel information extraction conditions for extracting personnel information stored in the personnel information storage unit as the personnel information from the supply personnel information supplied by the organization;
The personnel information extraction condition storage unit stores the personnel information extraction condition and the supply personnel information, and should be stored in the personnel information storage unit based on the personnel information extraction condition from the input supply personnel information The personnel information is extracted, and an extracted personnel information output unit that outputs the extracted personnel information is provided.
The personnel information storage unit
5. The personnel information output device according to claim 1, wherein the personnel information output by the extracted personnel information output unit is input, and the input personnel information is stored. Corresponding member identification information for identifying members constituting the organization, member attributes indicating attributes of the members in the organization, and valid periods of authority granted to the members according to the member attributes In addition, including a plurality of personnel information of the member in the organization, if at least one of the member identification information and the member attribute is different, a personnel information storage unit that stores as different personnel information,
In the effective period, the authority granted to the member specifies a grace period that is continuously considered valid for a predetermined period after the effective period ends, and the member attribute to be applied to the grace period In the personnel information output method of the personnel information output device provided with the grace condition storage unit that stores the member attribute specifying conditions in association with each other,
The HR information request unit requests acquisition of the HR information stored in the HR information storage unit, and generates a HR information acquisition request including a current date that is a date when requesting acquisition of the HR information, A personnel information request step for outputting the generated personnel information acquisition request;
The personnel information output unit inputs the personnel information acquisition request output by the personnel information request unit, inputs the grace period and the member attribute specifying condition stored in the grace condition storage unit, and acquires the personnel information Calculating a grace date corresponding to a date that is backed by the grace period from the current date included in the request, the content valid period that is the valid period including the computed grace date, and the content valid period The personnel information that is a member attribute and includes the member attribute specified from the member attribute specifying condition associated with the grace date is acquired from the personnel information storage unit, and the acquired personnel information is postponed. A personnel information output method comprising: a personnel information output step for outputting personnel information.   A program for causing a computer to function as the personnel information output device according to any one of claims 1 to 5.

Images