Roster preparation device and control program

Abstract

To prepare a highly accurate roster reflecting desires of staff members.SOLUTION: A roster preparation device 10 comprises: a roster preparation unit 112 which prepares a first roster on the basis of staff member attributes, desired conditions, and priorities of the desired conditions; a change acceptance unit 113 which accepts a change of the priority of a desired condition of a first staff member out of a plurality of staff members, from a user; an extraction unit 114 which extracts a staff member whose attribute information is the same as that of the first staff member, as a second staff member from the plurality of staff members on the basis of the staff member attributes; and a priority setting unit 115 which changes the priority of the desired condition of the first staff member the change of which is accepted by the change acceptance unit 113, by a first change amount and changes the priority of the same desired condition of the second staff member by a second change amount smaller than the first change amount. The roster preparation unit 112 prepares a second roster obtained by modifying the first roster on the basis of the desired conditions and the priorities of the desired conditions changed by the priority setting unit 115.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a roster creation device and a control program. [Background technology]

[0002] Nursing care facilities and other facilities need to create shift work schedules to provide 24-hour services. When creating these schedules, managers need to take into account and adjust the desired conditions of employees. However, there are many desired conditions for employees, and it is difficult to create a schedule that meets all of them.

[0003] In the shift determination method disclosed in Patent Document 1, essential conditions, desired conditions, and the priority of the desired conditions are set when creating a work schedule. Then, the optimal solution for shift work is searched for by repeating the process of changing the combination of shift work a predetermined number of times so as to increase the degree to which the desired conditions are satisfied while still satisfying the essential conditions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-101551 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, desired conditions for shift work differ from employee to employee, and there are many desired conditions, and setting priorities is complicated, so it takes a lot of time and effort for managers to set these.

[0006] The present invention has been made in consideration of the above circumstances, and has an object to create a highly accurate work schedule that reflects the requests of employees. [Means for solving the problem]

[0007] The above object of the present invention can be achieved by the following means.

[0008] (1) A shift schedule creation device for creating a shift schedule for a plurality of employees, comprising: An acquisition unit that acquires staff attributes of the plurality of staff members, desired conditions regarding shift work for each of the staff members, and priorities of the desired conditions; a roster creation unit that creates a first roster based on the staff attributes, the desired conditions, and the priority of the desired conditions; a change receiving unit that receives, from a user, a change to the priority of the desired conditions of a first staff member among the plurality of staff members; an extraction unit that extracts, from the plurality of staff members, a staff member having the same attribute information as the first staff member or a staff member having a part of the same attribute information as the first staff member, as a second staff member based on the staff attributes; a priority setting unit that changes the priority of the desired condition of the first staff member received by the change receiving unit by a first change amount, and changes the priority of the desired condition of the second staff member by a second change amount smaller than the first change amount, A roster creation device, wherein the roster creation unit creates a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed by the priority setting unit.

[0009] (2) A roster creation device as described in (1) above, wherein the employee attributes include job type, employment type, years of experience, and specific circumstances.

[0010] (3) The roster creation device described in (1) above, wherein the desired conditions are composed of desired types of work style, holidays, and pair work in which two or more employees work in the same shift, as well as the contents of the desired types.

[0011] (4) the change acceptance unit accepts a change to the upper and lower limits of the priority by a user; The roster creation device according to (1) above, wherein the priority can be changed by accepting the setting change, so that upper and lower limits can be changed for each of the desired conditions.

[0012] (5) the change acceptance unit accepts a setting change of the first change amount and / or the second change amount by a user; The roster creation device described in (1) above, wherein the priority setting unit changes the priority by the first change amount and / or the second change amount after the setting is changed.

[0013] (6) In the work schedule creation device described in (1) above, the priority setting unit determines whether the desired conditions of the first employee and the desired conditions of the second employee are identical by determining whether some or all of the contents of the desired conditions match.

[0014] (7) The employee is a care worker at a nursing care facility, The acquisition unit acquires essential conditions regarding shift work for the entire facility that must be met in order for the nursing care facility to receive public assistance, and which are applied in priority to the desired conditions; The roster creation device described in (1) above, wherein the roster creation unit creates the first and second roster based on the staff attributes, the required conditions, and the desired conditions and the priority of the desired conditions.

[0015] (8) A control program that operates on a shift schedule creation device that creates a shift schedule for a plurality of employees, comprising: (a) acquiring staff attributes of the plurality of staff members, and desired conditions for each of the staff members regarding shift work and priorities of the desired conditions; (b) creating a first roster based on the staff attributes, the desired conditions and the priority of the desired conditions; (c) receiving from a user a change in priority of the desired conditions of a first staff member among the plurality of staff members; (d) extracting, from among the plurality of staff members, staff members having the same attribute information as the first staff member or staff members having part of the same attribute information as the first staff member based on the staff member attributes; (e) changing the priority of the desired conditions of the first staff member received in the step (c) by a first change amount, and changing the priority of the same desired conditions of the second staff member by a second change amount smaller than the first change amount; and (f) creating a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed in step (e). Effect of the Invention

[0016] The roster creation device of the present invention comprises an acquisition unit that acquires the staff attributes of the multiple staff members, as well as the desired conditions for shift work for each staff member and the priority of the desired conditions; a roster creation unit that creates a first roster based on the staff attributes, the desired conditions and the priority of the desired conditions; a change acceptance unit that accepts a user's change to the priority of the desired conditions for a first staff member among the multiple staff members; an extraction unit that extracts, from the multiple staff members, a staff member who has the same attribute information as the first staff member or a part of the attribute information that is the same as that of the first staff member, as a second staff member based on the staff attributes; and a priority setting unit that changes the priority of the desired conditions of the first staff member accepted by the change acceptance unit by a first change amount, and changes the priority of the same desired conditions of the second staff member by a second change amount smaller than the first change amount, and the roster creation unit creates a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed by the priority setting unit. This makes it possible to create accurate work schedules that reflect staff requests. [Brief description of the drawings]

[0017] [Figure 1] 1 is a schematic diagram showing an information processing system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a block diagram showing a configuration of a roster creation device. [Figure 3A] 13 is an example of an input screen for registering data in a condition definition DB. [Figure 3B] 11 is an example of condition definition data. [Figure 4A] 13 is an example of an input screen for registering data in a condition definition DB. [Figure 4B] 11 is an example of condition definition data. [Figure 5A] 13 is an example of an input screen for registering data in a staff attribute DB. [Figure 5B] 11 is an example of staff attribute data. [Figure 6A] 13 is an example of an input screen for registering data in a desired condition DB. [Figure 6B] 13 is an example of desired condition data. [Figure 7] 13 is a flowchart showing a pre-setting process for registering data in various DBs. [Figure 8] 13 is a flowchart showing a roster creation process. [Figure 9] 11 is an example of the first roster that has been generated. [Figure 10] 9 is a subroutine flowchart showing the process of step S17 in FIG. 8. [Figure 11] 13 is an example of a screen for inputting a correction request associated with a correction process. [Figure 12] 13 is a diagram for explaining a change in priority based on a first change amount, and a determination as to whether or not desired conditions are the same. FIG. [Figure 13] FIG. 11 is a diagram for explaining the extraction process of a second staff member. [Figure 14] 13 is a diagram for explaining a change in priority based on a second change amount. FIG. [Figure 15] FIG. 13 is a diagram for explaining a change in priority. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, an embodiment of the present invention will be described with reference to the attached drawings. However, the scope of the present invention is not limited to the disclosed embodiment. In the description of the drawings, the same elements are given the same reference numerals, and duplicated descriptions are omitted. In addition, the dimensional ratios of the drawings are exaggerated for the convenience of explanation, and may differ from the actual ratios.

[0019] FIG. 1 is a schematic diagram showing an information processing system 1 according to the present embodiment. The information processing system 1 includes a roster creation device 10 and a terminal device 30, and each device is connected to communicate with each other via a network 50. The roster creation device 10 is a server or a PC (personal computer). In addition, when the roster creation device 10 is configured as a server, it may be an on-premise server provided in a nursing care facility, or may be a cloud server using a commercial cloud service. The terminal device 30 is a PC equipped with a display unit such as a display, and is operated by a user such as a nursing care staff member or an administrator of the nursing care facility. The roster creation device 10 functions as a backend, and the terminal device 30 functions as a frontend. In addition, the roster creation device 10 may be connected to devices (terminal devices 30) of multiple facilities. A nursing care facility is a facility that provides nursing care services to residents of the facility, and is, for example, a special nursing home for the elderly, a residential type paid nursing home, or a group home. In addition, a nursing care facility may be a hospital. In the roster creation device 10, staff engaged in nursing care work include care staff (both qualified and unqualified), nutritionists, nurses, and doctors.

[0020] In the following, an example will be described in which the roster creation device 10 is connected to a terminal device at one nursing care facility (facility A) and creates a roster of shift work for staff engaged in nursing care work at the facility. The roster will be described as creating a roster for 24-hour shift work for a specified period (for example, for the following January). Note that these are merely examples, and the terminal device 30 and the roster creation device 10 may be used in facilities other than nursing care facilities. The roster creation device 10 is not limited to rostering for nursing care facilities, and may also create rostering for 24-hour or specified daytime shift work for restaurants, production factories, etc.

[0021] (Roster creation device 10) FIG. 2 is a block diagram showing the configuration of the roster creation device 10. The roster creation device 10 has a control unit 110, a storage unit 120, and a communication unit 130. The control unit 110 is composed of a CPU, a RAM, a ROM, etc., and controls and performs calculation processing for each unit of the roster creation device 10 according to a program. The control unit 110 functions as an acquisition unit 111, a roster creation unit 112, a change acceptance unit 113, an extraction unit 114, a priority setting unit 115, and an output unit 116, either alone or in cooperation with the communication unit 130. The storage unit 120 stores a condition definition DB (database), a staff attribute DB, a desired condition DB, and a required condition DB. The communication unit 130 is an interface circuit (e.g., a LAN card, etc.) for communicating with other devices via the network 50.

[0022] (Acquisition part 111) The acquisition unit 111 acquires staff attributes of staff, a plurality of desired conditions related to shift work for each staff member, and the priority of the desired conditions. The acquisition unit 111 acquires this information through an input screen (FIGS. 5A, 6A, etc.) of the terminal device 30, as described below. The acquired information is stored in various DBs of the storage unit 120. The acquisition unit 111 may acquire the staff attributes, desired conditions, and their priorities from the storage unit 120.

[0023] (Roster Creation Department 112) The roster creation unit 112 creates a shift roster (hereinafter also referred to as the initial roster or the first roster) using a known algorithm such as a genetic algorithm based on the desired conditions of the staff, the priority of the desired conditions, and various other conditions. The various conditions include essential conditions. The essential conditions used in creating the shifts include the standard working hours of the staff at the facility, the number of days off for the staff, the shift frame setting (time period setting), and the number of staff for each job type in each shift frame. The roster creation unit 112 can grasp the job types of the staff from the staff attribute data (FIG. 5B described later). The number of staff for each shift frame may be set by a user such as an administrator. Or, in the case of a nursing care facility, it may be automatically determined by the control unit 110 based on other essential conditions inputted later and the number of users (residents of the facility) of the facility.

[0024] Furthermore, the roster creation unit 112 creates a revised roster (second roster) in response to a change in priority accepted by the change acceptance unit 113. This second roster is created by the roster creation unit 112 using the desired conditions of the staff, various conditions, and the revised priority set by the priority setting unit 115 described below.

[0025] (Change acceptance unit 113) The change receiving unit 113 receives a change made by the user to the priority of one or more desired conditions out of the plurality of desired conditions for one or more of the plurality of staff members (hereinafter also referred to as a first staff member).

[0026] (Extraction part 114) The extraction unit 114 extracts, from among a plurality of staff members, staff members whose attribute information is the same as or similar to that of the first staff member, i.e., staff members whose attribute information partially matches, as the second staff member, based on the staff member attributes. For example, a staff member whose job type and specific circumstances (see FIG. 5B described below) are the same as those of the first staff member may be extracted as the second staff member.

[0027] (Priority setting section 115) The priority setting unit 115 changes the priority setting in response to the change acceptance unit 113 accepting a change in the priority of a desired condition. In addition, the priority setting unit 115 automatically changes the priority setting of other desired conditions corresponding to the accepted desired condition. More specifically, the priority setting unit 115 changes the priority of the desired condition x of the first staff member accepted by the change acceptance unit by a first change amount. Furthermore, the priority setting unit 115 changes the priority of the same desired condition x of the second staff member extracted by the extraction unit, or a desired condition x2 that is similar to the desired condition x, i.e., has a part of the content that matches the desired condition x, by a second change amount that is smaller than the first change amount. In the case of the judgment condition of "partial match" (FIG. 4(b4) described later), for example, if the type of the desired condition x1 is a work style, it is a case where the availability of day shift, day shift, and night shift partially overlaps. If the type is other (holiday, pair), it is a case where the holidays partially overlap and the people working together in the pair match.

[0028] When a first employee has a change request (changing the priority of desired conditions), the second employee with the same or similar employee attributes often has the same change request. Therefore, the same change request is handled for the second employee extracted by this extraction unit, and the priority of the desired conditions is changed. However, since there is a risk in raising the priority by the same amount of change as for the first employee, the priority of the second employee's desired conditions is raised by a second amount of change that is smaller than the first amount of change.

[0029] (Output unit 116) The output unit 116 outputs the roster (first and second roster) created by the roster creation unit 112. For example, the output unit 116 transmits roster data to the terminal device 30 of the manager, or displays it.

[0030] (Data recorded in various databases) Hereinafter, with reference to Figs. 3A to 6B, the procedure for acquiring data from the condition definition DB, staff attribute DB, desired condition DB, and essential condition DB stored in the storage unit 120 and the contents thereof will be described.

[0031] (Condition definition data) FIG. 3A is an example of an input screen for registering data in a condition definition DB, which is displayed by an application (web application, etc.) running on the terminal device 30. A user, such as a facility manager, inputs (a1) condition, (a2) type, (a3) ​​lower limit priority, and (a4) upper limit priority on the input screen of FIG. 3A. For condition (a1), a required condition or a desired condition can be selected from a pull-down menu. As described above, a required condition is a condition for complying with requirements imposed by the country, etc. The user inputs requirements according to the remuneration unit price or systematic addition applied by the facility. Furthermore, for type (a2), if a desired condition is selected in condition (a1), the user inputs type (a2) according to that condition. Type (a2) includes work system and pair. The contents of work system and pair will be described later.

[0032] The lower limit (a3) ​​and the upper limit (a4) of the priority can be selected from the pull-down menu. The conditions are set so that the upper limit is greater than the lower limit, and the lower limit of the priority of the essential condition is greater than the upper limit of the priority of the desired condition. Settings other than these conditions cannot be selected. In the example of FIG. 3A, the upper limit of the priority of the desired condition is set to 10, and the lower limit is set to 0. The interval is set to 0.5 by default. FIG. 3B is an example of condition definition data registered in the condition definition DB with the settings as shown in FIG. 3A. The No. in the figure is a unique ID number automatically assigned by the system (the same applies to FIG. 4B below). In the example shown in FIG. 3A, the user can set the upper limit / lower limit setting range for each desired condition (for each type of desired condition), but a uniform setting range may be applied to all types of desired conditions by an input screen as shown in FIG. 3A.

[0033] Fig. 4A is an example of an input screen for registering data in a condition definition DB. On the input screen in Fig. 4A, conditions related to changing the priority of desired conditions are defined.

[0034] A user such as a facility manager selects (b1) first change amount, (b2) second change amount, (b3) staff attribute match, or (b4) desired condition match from the pull-down menu on the input screen of FIG. 4A. The first change amount (b1) and second change amount (b2) will be described later. These change amounts determine the degree of increase in priority. They are set so that the first change amount is greater than the second change amount (i.e., they can only be selected under the user's condition of this magnitude relationship). Staff attribute match (b3) is a match determination condition for staff attributes, which will be described later, and the user can select "complete match" or "type match" from the pull-down menu. Desired condition match (b4) is a match determination condition for desired conditions, which will be described later, and the user can select "complete match," "type match," or "partial match" from the pull-down menu.

[0035] FIG. 4B shows an example of condition definition data registered in the condition definition DB with the settings shown in FIG. 4A.

[0036] (Staff attribute data) A user such as a facility manager selects (c1) staff name, (c2) job type, (c3) employment type, (c4) years of experience, and (c5) specific circumstances from the pull-down menus on the input screen of FIG. 5A. Job type (c2) includes care workers, nutritionists, nurses, doctors, etc. Care workers may also be classified according to whether they have qualifications in care welfare or the like. Employment type (c3) can be selected as non-regular or regular. Years of experience (c4) is selected based on the number of years of experience the staff member has in the relevant job type. Specific circumstances can be selected from multiple circumstances set in advance. For example, selectable specific circumstances include "has children," "has a care recipient at home," and "no specific circumstances." Furthermore, "has children" can be further subdivided according to the child's age, such as infant, toddler, elementary school student, middle school student, etc.

[0037] FIG. 5B is an example of staff attribute data registered in the staff attribute DB through an input screen such as that of FIG. 5A.

[0038] (Desired conditions data) A user such as a facility manager inputs desired conditions based on requests from each staff member on the input screen of FIG. 6A. On the input screen of FIG. 6A, the user selects and inputs (d1) conditions, (d2) staff member, (d3) condition type, (d4) condition content, and (d5) priority from the pull-down menus. d2 to d5 are menus that are displayed when the desired conditions are selected in the condition (d1). In the condition type (d3), the user can select either "work style," "holiday," or "pair." In the condition content (d4), if "work style" is selected in the condition type (d3), the user can select "no night shifts" or "only day shifts available." In the case where "holiday" is selected, the user can select the day of the week and the date. In addition, in the condition content (d4), if "pair" is selected in the condition type (d3), the user can select the target pair partner. The priority (d5) is a value that is set initially, and "0 (zero)" is usually selected.

[0039] FIG. 6B shows an example of desired condition data registered in the desired condition DB through an input screen such as that shown in FIG. 6A.

[0040] (Required data) The required conditions DB has registered therein the required conditions for creating a work schedule. For example, nursing care facilities must meet requirements imposed by the national government or local government (hereafter referred to as the national government, etc.) when determining various unit prices of remuneration or systematic surcharges as subsidies paid by the national government, etc. For example, requirements include the number of qualified nursing care welfare workers or nurses, the number of staff working the night shift (allocation ratio to care recipients), etc. The required conditions registered in the required conditions DB are those requirements stipulated for each facility.

[0041] (Pre-setting process) FIG. 7 is a flowchart showing a pre-setting process for registering data in various DBs.

[0042] (Steps S01 to S03) A user such as a facility manager inputs condition definitions, staff attribute information, essential conditions, and desired conditions. For example, the user inputs condition definitions, staff attribute information, essential conditions, and desired conditions through input screens such as those shown in the above-mentioned Figures 3A, 4A, 5A, and 6A. The input information is recorded in various DBs in the storage unit 120 as registration data such as those shown in Figures 3B, 4B, 5B, and 6B.

[0043] (Route creation process) Next, the roster creation process according to this embodiment will be described with reference to Fig. 8 to Fig. 13. Fig. 8 is a flowchart showing the roster creation process executed mainly by the roster creation device 10. In the following, it is assumed that the manager of a nursing care facility creates a roster of 24-hour shift work for care staff engaged in nursing care work at the facility for each calendar month.

[0044] (Step S11) If it is a predetermined timing, for example, the end of the previous month when creating a roster for the next month, the control unit 110 advances the process to the next step S12.

[0045] (Steps S12 and S13) The acquisition unit 111 acquires condition definition data, staff attribute data, essential conditions, and staff desired conditions for the target facility from various DBs in the storage unit 120. Priority is set for each desired condition (see FIG. 6B) within the upper and lower limits (see FIG. 3A) defined in the condition definition data, and the priority of the essential conditions is set higher than the upper limit of the priority of the desired conditions.

[0046] (Step S14) The roster creation unit 112 of the control unit 110 creates a first roster for shift work based on the essential conditions, the staff's desired conditions, and the priority of the desired conditions.

[0047] (Step S15) The output unit 116 outputs the created first roster to the terminal device 30 used by a user such as a manager. Fig. 9 is an example of output of the created first roster.

[0048] (Step S16) A user such as an administrator and each staff member of the facility check the shift details in the output first roster. If no revisions to the roster are required, the contents of the first roster are confirmed and the process ends (END). On the other hand, if a staff member requests revisions to the roster, revisions to the roster are required (YES), and the process proceeds to step S17.

[0049] (Step S17) Here, the priority change process is performed by change acceptance section 113, extraction section 114, and priority setting section 115. Fig. 10 is a subroutine flowchart showing the process of step S17 here.

[0050] (Step S201) The change reception unit 113 receives the correction request and its desired conditions. FIG. 11 is an example of an input screen for a correction request associated with a correction response, which is displayed on the terminal device 30. A user such as an administrator inputs the name of the employee for whom a correction is requested, the type of desired condition, and the content of the desired condition through an input screen such as that shown in FIG. 11. In the example shown in FIG. 11, as correction request 1, employee A has requested a correction because his desired condition of "no night shifts allowed in the work style" was not reflected in the first work schedule. Also, as correction request 2, employee B has requested a correction because his desired condition of "pair work, working the same shift as employee D" was not reflected in the first work schedule.

[0051] (Step S202) In the following, first (first round), the explanation will be given with employee A relating to revision request 1 as the first employee, and his desired condition (work style: no night shifts) as desired condition x. The priority setting unit 115 changes the priority of desired condition x by a first change amount. The first change amount is stored in the condition definition DB (FIG. 4B), and is "1" here. FIG. 12 is a list of desired condition data stored in the desired condition DB. As shown in FIG. 12, in accordance with revision request 1, the priority of "COE-001", which is employee A's desired condition x, is changed from 0 to 1 (raised).

[0052] (Step S203) The extraction unit 114 refers to the staff attribute data (staff list) in the staff attribute DB, and extracts staff members who have the same staff attribute items in all items, or staff members who have the same staff attribute items in some items, as the second staff member. FIG. 13 is a diagram for explaining the extraction process of the second staff member. In the example of FIG. 13, the extraction unit 114 extracts staff members B and E who have the same staff attribute items in all items as the first staff member (staff member A) as the second staff member. As another example, the extraction unit 114 may extract staff members who have the same staff attribute items in some items, such as job type and specific circumstances, as the second staff member.

[0053] (Step S204) The priority setting unit 115 determines whether or not there is a desired condition that is the same as the desired condition x (COE-001) among one or more desired conditions of the second staff members (staff members B and E) extracted by the extraction unit 114. In the example shown in FIG. 12, the desired condition (COE-005) of staff member B and the desired condition (COE-011) of staff member E are the same desired condition x (YES), so the process proceeds to step S205. On the other hand, if none of the second staff members have the same desired condition x (NO), the process proceeds to step S206.

[0054] (Step S205) The priority setting unit 115 changes the priority of the desired condition x (COE-005, 011) of each of the second staff members (staff members B and E) by a second change amount that is smaller than the first change amount. The second change amount is stored in the condition definition DB (FIG. 4B) and is "0.5" in this example. As shown in FIG. 14, in response to modification request 1, the priority of "COE-005, 011", which is the desired condition x of staff members B and E, is changed (raised) from 0 to 0.5.

[0055] (Step S206) If the priority change process has not been performed for all the revision requests (NO), the control unit 110 returns the process to step S202. For example, in response to revision request 2 (FIG. 11), in the second round, the process from step S202 onwards is performed with staff B related to revision request 2 as the first staff member and its desired condition (pair, together with D) as desired condition x. FIG. 15 is a diagram for explaining the change of priority by the process from steps S02 to S205 in the second round. As shown in FIG. 15, the priority of the condition x (COE-006) of the first staff member (staff member B) is changed by the first change amount, and the priority of the condition x (COE-020) of the second staff member (staff member X) is changed by the second change amount. On the other hand, if the priority change process has been performed for all the revision requests (YES), the control unit 110 ends the subroutine process in FIG. 10, returns to FIG. 8, and executes the process from step S18 onwards.

[0056] (Steps S18 and S19) The roster creation unit 112 creates a second roster for shift work based on the essential conditions, the desired conditions of the staff, and the changed priority of the desired conditions. The priority used here is the changed priority changed by the process of step S17 (see FIG. 15).

[0057] The output unit 116 also outputs the created second roster to the terminal device 30 used by a user such as a manager. For example, as in FIG. 9, the created second roster is displayed on the display unit of the terminal device 30. Thereafter, the process returns to step S16, and the user such as the manager and each staff member of the facility reconfirm the shift details in the output second roster. If no corrections to the roster are required, the process ends (END). At this time, if a user such as a manager requests manual corrections, the corrections may be accepted from the terminal device 30, and the roster reflecting the corrections (third roster) may be made the final roster.

[0058] Thus, the roster creation device according to the present embodiment includes an acquisition unit that acquires the staff attributes of the plurality of staff members, and a plurality of desired conditions related to shift work for each staff member and the priority of the desired conditions, and a roster creation unit that creates a first roster based on the staff attributes, the desired conditions, and the priority of the desired conditions. Also includes a change acceptance unit that accepts a change by a user to the priority of one or more of the desired conditions of a first staff member among the plurality of staff members, an extraction unit that extracts, from the plurality of staff members, a staff member having the same attribute information as the first staff member or a staff member having part of the same attribute information as the first staff member, as a second staff member, based on the staff attributes, and a priority setting unit that changes the priority of the desired conditions of the first staff member accepted by the change acceptance unit by a first change amount, and changes the priority of the same desired conditions of the second staff member by a second change amount smaller than the first change amount. Then, the roster creation unit creates a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed by the priority setting unit. This allows users, such as administrators, to easily change priority settings and create accurate work schedules that reflect the needs of staff.

[0059] The above-described configuration of the roster creation device 10 is a main configuration described in order to explain the features of the above-described embodiment, but is not limited to the above-described configuration and may be modified in various ways within the scope of the claims. In addition, the configuration of a general roster creation device 10 is not excluded.

[0060] For example, the priority of the desired conditions changed in the process of step S17 may be used as is when creating a roster for the month after next, which is executed in the following month, or may be reset to a default value (FIG. 3B) and then used. Also, in step S205 of FIG. 10, a process may be added to confirm with a user, such as a manager, whether or not to change the priority of the desired conditions x of the second staff member by the second change amount. For example, immediately before step S205, an operation screen is displayed on the terminal device 30 to request the user's confirmation when changing by the second change amount.

[0061] The means and methods for performing various processes in the roster creation device 10 according to the above-described embodiment can be realized by either a dedicated hardware circuit or a programmed computer. The above-mentioned program may be provided by a computer-readable recording medium such as a USB memory or a DVD (Digital Versatile Disc)-ROM, or may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is usually transferred to and stored in a storage unit such as a hard disk. The above-mentioned program may be provided as a standalone application software, or may be incorporated into the software of the device as one of its functions. [Explanation of symbols]

[0062] 1. Information Processing Systems 10. Work Schedule Creation Device 110 Control section 111 Acquisition Department 112 Schedule Creation Department 113 Change Reception Department 114 Extraction part 115 Priority setting section 116 Output section 120 Storage section 130 Communications Department

Claims

1. A shift schedule creation device that creates a shift schedule for a plurality of employees, An acquisition unit that acquires staff attributes of the plurality of staff members, desired conditions regarding shift work for each of the staff members, and priorities of the desired conditions; a roster creation unit that creates a first roster based on the staff attributes, the desired conditions, and the priority of the desired conditions; a change receiving unit that receives a change in priority of the desired conditions of a first staff member among the plurality of staff members from a user; an extraction unit that extracts, from the plurality of staff members, a staff member having the same attribute information as the first staff member or a staff member having a part of the same attribute information as the first staff member, as a second staff member based on the staff attributes; a priority setting unit that changes the priority of the desired condition of the first staff member accepted by the change acceptance unit by a first change amount, and changes the priority of the same desired condition of the second staff member by a second change amount smaller than the first change amount, A roster creation device, wherein the roster creation unit creates a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed by the priority setting unit.

2. The roster creation device according to claim 1 , wherein the employee attributes include job type, employment type, years of experience, and specific circumstances.

3. The roster creation device according to claim 1 , wherein the desired conditions are configured with a work style, holidays, and pair work in which two or more staff members work in the same shift as desired types, and the contents of the desired types.

4. the change acceptance unit accepts a change to the upper and lower limits of the priority by a user; The roster creation device according to claim 1 , wherein the priority is changeable by accepting the setting change, so that an upper limit and a lower limit of the priority are changeable for each of the desired conditions.

5. the change acceptance unit accepts a setting change of the first change amount and / or the second change amount by a user; The roster creation device according to claim 1 , wherein the priority setting unit changes the priority by the first change amount and / or the second change amount after the setting change.

6. The roster creation device of claim 1, wherein the priority setting unit determines whether the desired conditions of the first employee and the desired conditions of the second employee are identical based on whether some or all of the contents of the desired conditions match.

7. The staff member is a care worker at a care facility, The acquisition unit acquires essential conditions regarding shift work for the entire facility that must be met in order for the nursing care facility to receive public assistance, and which are applied in priority to the desired conditions; The roster creation device according to claim 1 , wherein the roster creation unit creates the first and second roster based on the staff attributes, the essential conditions, the desired conditions, and the priority of the desired conditions.

8. A control program that operates on a shift schedule creation device that creates a shift schedule for a plurality of employees, (a) acquiring staff attributes of the plurality of staff members, and desired conditions for each of the staff members regarding shift work and priorities of the desired conditions; (b) creating a first roster based on the staff attributes, the desired conditions, and the priority of the desired conditions; (c) receiving, from a user, a change in priority of the desired conditions of a first staff member among the plurality of staff members; (d) extracting, from among the plurality of staff members, staff members having the same attribute information as the first staff member or staff members having a part of the same attribute information as the first staff member, based on the staff member attributes; a step (e) of changing the priority of the desired condition of the first staff member received in the step (c) by a first change amount, and changing the priority of the same desired condition of the second staff member by a second change amount smaller than the first change amount; A control program for causing a computer to execute a process including a step (f) of creating a second roster by modifying the first roster based on the desired conditions and the priority of the desired conditions changed in step (e).

Images