JP2024094590A - Work schedule creation device, work schedule creation method, and work schedule creation program - Google Patents

Abstract

To provide a work schedule creation device, work schedule creation method, and work schedule creation program, which enable accurate creation of a work schedule while reducing the workload of creating the work schedule.SOLUTION: A work schedule creation device according to an embodiment is configured to refer to a client calendar master, staff basic data, project basic data, project working hours data, and closed work basic data, and use an entered staff code, project number, and year/month to create work schedule data for a target period of a staff member corresponding to the staff code.SELECTED DRAWING: Figure 1

Description

The present invention relates to a work schedule creation device, a work schedule creation method, and a work schedule creation program.

Patent Document 1 discloses a technology for creating a work schedule, including work shifts, for group members such as full-time employees and non-full-time employees such as part-timers and dispatched workers.

JP 2019-144609 A

In the temporary staffing industry, operators who create work schedules manually check the work days and holidays for each client. Temporary workers work at client companies based on the work schedules created by their own company, the dispatching company.

However, because operators manually create work schedules, there are problems with mistakes and the process can become complicated, resulting in a lot of work being required.

The present invention has been made in consideration of the above, and aims to provide a work schedule creation device, a work schedule creation method, and a work schedule creation program that can reduce the burden of creating work schedules and accurately create work schedules.

In order to solve the above-mentioned problems and achieve the object, the work schedule creation device of the present invention is a work schedule creation device having a control unit, and is capable of accessing a customer calendar master in which a customer code is associated with a date and holiday classification, staff basic data in which a staff code and a name are associated, case basic data in which a case number is associated with at least a customer code and a contract period, case working hours data in which a case number is associated with at least working hours, and contract work basic data in which a case number and a staff code are associated, and is characterized in that it has a creation unit that references the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data, and creates work schedule data for the target period of the staff corresponding to the staff code based on the input staff code, case number, and year and month.

The work schedule creation method according to the present invention is a work schedule creation method executed by a work schedule creation device having a control unit, the work schedule creation device being capable of accessing a customer calendar master in which a customer code is associated with a date and holiday category, staff basic data in which a staff code and a name are associated, case basic data in which a case number is associated with at least a customer code and a contract period, case working hours data in which a case number is associated with at least working hours, and contract work basic data in which a case number and a staff code are associated, and the control unit includes a creation step of referencing the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data, and creating work schedule data for the target period of the staff corresponding to the staff code based on the input staff code, case number, and year and month, executed by the control unit.

The work schedule creation program according to the present invention is a work schedule creation program to be executed by a work schedule creation device having a control unit, the work schedule creation device being able to access a customer calendar master in which a customer code is associated with a date and holiday category, staff basic data in which a staff code and a name are associated, case basic data in which a case number is associated with at least a customer code and a contract period, case working hours data in which a case number is associated with at least working hours, and contract work basic data in which a case number and a staff code are associated, and the control unit is characterized by including a creation step of referencing the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data to be executed by the control unit, and creating work schedule data for the target period of the staff corresponding to the staff code based on the input staff code, case number, and year and month.

The present invention has the effect of reducing the burden of creating work schedules and enabling accurate creation of work schedules.

FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a work schedule creation device according to an embodiment. FIG. 2 is a diagram illustrating an example of a customer basic data table in the customer basic data stored in the storage unit of the work schedule creation device according to the embodiment. FIG. 3 is a diagram illustrating an example of a holiday master table in the holiday master in the storage unit included in the work schedule creation device according to the embodiment. FIG. 4 is a diagram illustrating an example of a customer calendar master table in the customer calendar master in the storage unit included in the work schedule creation device according to the embodiment. FIG. 5 is a diagram showing an example of a staff basic data table in the staff basic data storage unit of the work schedule creation device according to the embodiment. FIG. 6 is a diagram illustrating another example of a staff basic data table in the staff basic data in the storage unit included in the work schedule creation device according to the embodiment. FIG. 7 is a diagram illustrating an example of a case basic data table in the case basic data in the storage unit included in the work schedule creation device according to the embodiment. FIG. 8 is a diagram illustrating an example of a job working hours data table in the job working hours data stored in the storage unit included in the work schedule creation device according to the embodiment. FIG. 9 is a diagram showing an example of a contract work basic data table in the contract work basic data of the storage unit included in the work schedule creation device according to the embodiment. FIG. 10 is a flowchart showing an overview of a customer calendar creation process executed by the work schedule creation device according to the embodiment. FIG. 11 is a flowchart showing an overview of a contract information registration process executed by the work schedule creation device according to the embodiment. FIG. 12 is a flowchart showing an overview of a work schedule creation process executed by the work schedule creation device according to the embodiment. FIG. 13 is a diagram showing an example of a work schedule input screen. FIG. 14 is a diagram showing an example of a work schedule input screen after the creation unit of the work schedule creation device according to the embodiment creates a work schedule. FIG. 15 is a diagram for explaining a schematic procedure for the creation unit of the work schedule creation device according to the embodiment to create a work schedule.

Below, an embodiment of a work schedule creation device, a work schedule creation method, and a work schedule creation method according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Configuration]
An example of the configuration of a work schedule creation device according to the present embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a work schedule creation device.

The work schedule creation device 100 shown in FIG. 1 is a commercially available desktop personal computer. Note that the work schedule creation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The work schedule creation device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the work schedule creation device 100 is connected to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the work schedule creation device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the work schedule creation device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 stores customer basic data 106a, holiday master 106b, customer calendar master 106c, staff basic data 106d, case basic data 106e, case working hours data 106f, and contract work basic data 106g.

Customer basic data 106a stores customer codes in association with customer names and addresses. Figure 2 is a diagram showing an example of a customer basic data table in customer basic data 106a. The first row of customer basic data table T1 shown in Figure 2 stores customer code "T0001" in association with customer name "XX Pharmaceuticals" and address "A-B-C Kyobashi, Chuo-ku, Tokyo."

Holiday master 106b stores holiday names in association with dates. Figure 3 is a diagram showing an example of a holiday master table in holiday master 106b. In the first row of holiday master table T2 shown in Figure 3, the date "2022/1/1" is stored in association with the holiday name "New Year's Day."

The customer calendar master 106c stores customer codes in association with dates and holiday categories. FIG. 4 is a diagram showing an example of a customer calendar master table in the customer calendar master 106c. In the first row of the customer calendar master table T3 shown in FIG. 4, the customer code "T0001" is stored in association with the date "2022/11/3 (Thu)" and holiday category "Regular holiday". Note that for Culture Day on 2022/11/3 (Thu) in the customer calendar master table T3, "Regular holiday" is associated with customer codes "T0001" and "T0003", but "Working day" is associated with customer code "T0002". Details will be described later.

Staff basic data 106d stores staff codes in association with names and employment dates. Figure 5 is a diagram showing an example of a staff basic data table in staff basic data 106d. In the first row of staff basic data table T4 shown in Figure 5, staff code "10001" is stored in association with the name "Sample Taro" and employment date "2000/1/1". Note that the staff code in staff basic data table T4 may also be stored in association with "optional items" in PK item table T5 shown in Figure 6. Here, optional items may be stored in association with, for example, staff (company employees), clients (dispatch destinations), and cases (contractual items).

The case basic data 106e stores case numbers in association with customer codes, contract periods, and business details. Figure 7 is a diagram showing an example of a case basic data table in the case basic data 106e. The first row of the case basic data table T6 shown in Figure 7 stores case number "100" in association with customer code "T0001", contract period From "2022/4/1" indicating the start of the contract period, contract period To "2022/3/31" indicating the end of the contract period, and business details "pharmaceutical sales."

Case working hours data 106f stores working hours in association with case numbers. Figure 8 is a diagram showing an example of a case working hours data table in case working hours data 106f. The first row of the case working hours data table T7 shown in Figure 8 stores case number "100" in association with working time From "9:00" indicating the start time of the working hours, working time To "18:00" indicating the end time of the working hours, and a specified time "8:00" indicating the working hours of the working hours.

The contract work basic data 106g stores a staff code in association with the case number. Figure 9 is a diagram showing an example of a contract work basic data table in the contract work basic data 106g. The first row of the contract work basic data table T8 shown in Figure 9 stores the case number "100" in association with the staff code "10001".

Returning to FIG. 1, the description of the configuration of the work schedule creation device 100 will continue.
The control unit 102 is a CPU or the like that performs overall control of the work schedule creation device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 102 includes a registration unit 102a, an output control unit 102b, and a creation unit 102c.

The registration unit 102a executes a customer registration process to register customer basic data 106a in accordance with the operation contents input by the operator via the input device 112. The registration unit 102a also executes a holiday master registration process to register a holiday calendar and register holiday master 106b in accordance with the operation contents input by the operator via the input device 112. The registration unit 102a also executes a customer calendar master maintenance process to reference the holiday master 106b and generate and register customer calendar master 106c (see customer calendar master table T3 in FIG. 4) in which holiday categories are set for each customer, based on the operation contents input by the operator via the input device 112.

The output control unit 102b displays a work schedule input screen on the monitor 114. The output control unit 102b also executes an output process to output the work schedule data created by the creation unit 102c (described later) to the monitor 114.

The creation unit 102c executes a work schedule creation process in which the operator creates work schedule data for the staff corresponding to the staff code via the input device 112, by referencing the customer calendar master 106c, staff basic data 106d, case basic data 106e, case working hours data 106f, and contract work basic data 106g, and in response to the staff code cell K1, case number cell K2, year and month cell K3, and customer cell K4.

2. Processing Executed by the Work Schedule Creation Device
[2-1: Customer calendar creation process]
First, a description will be given of a customer calendar creation process executed by the work schedule creation device 100. FIG.

As shown in FIG. 10, first, the registration unit 102a executes a customer registration process to register customer basic data 106a according to the operation contents input by the operator via the input device 112 (step S1). Specifically, the registration unit 102a stores the customer basic data 106a (see customer basic data table T1 in FIG. 2) set according to the operation contents input by the operator via the input device 112 in the storage unit 106.

Then, the registration unit 102a executes a holiday master registration process to register a holiday calendar in accordance with the operation contents input by the operator via the input device 112 and to register the holiday master 106b (step S2). Specifically, the registration unit 102a stores the holiday calendar set in accordance with the operation contents input by the operator via the input device 112 as the holiday master 106b (see the holiday master table T2 in FIG. 3) in the storage unit 106.

Then, the registration unit 102a executes a customer calendar master maintenance process that refers to the holiday master 106b and generates and registers a customer calendar master 106c (see customer calendar master table T3 in FIG. 4) in which holiday categories are set for each customer based on the operation contents input by the operator via the input device 112 (step S3). Specifically, the registration unit 102a first refers to the holiday master 106b and sets the customer's holidays in a lump. Furthermore, the registration unit 102a refers to the holiday master 106b and automatically specifies the day of the week (Monday to Sunday) of the system date to set the scheduled holidays and statutory holidays for each customer. In other words, the registration unit 102a automatically generates scheduled holidays and statutory holidays for each customer using the lump-sum setting function for days of the week in the holiday master 106b, without the operator having to manually input the date, scheduled holidays, and statutory holidays via the input device 112. After step S3, the work schedule creation device 100 ends this process.

[2-2: Contract information registration process]
Next, a description will be given of the contract information registration process executed by the work schedule creation device 100. Fig. 11 is a flowchart showing an overview of the contract information registration process executed by the work schedule creation device 100.

As shown in FIG. 11, first, the registration unit 102a executes a staff registration process to register information on employees to be dispatched in response to the operation contents input by the operator via the input device 112 (step S10). Specifically, the registration unit 102a generates staff basic data 106d in which a staff code is associated with a name and joining date in response to the operation contents input by the operator via the input device 112, and stores the data in the storage unit 106.

Then, the registration unit 102a executes a customer registration process to register basic information about the dispatch destination in accordance with the operation contents input by the operator via the input device 112 (step S11). Specifically, the registration unit 102a generates case basic data 106e (see case basic data table T6 in FIG. 6 ) in which the customer code is associated with the customer name and address in accordance with the operation contents input by the operator via the input device 112, and stores the data in the storage unit 106.

Then, the registration unit 102a executes a customer calendar master maintenance process to register scheduled holidays and statutory holidays of the client's dispatch destinations, according to the operation contents input by the operator via the input device 112 (step S12). Specifically, the registration unit 102a performs maintenance on the customer calendar master 106c (see customer calendar master table T3 in FIG. 4), which associates customer codes with dates and holiday categories, and stores the results in the memory unit 106.

Then, the registration unit 102a executes a case registration process to register the contract period, working hours, etc., according to the operation contents input by the operator via the input device 112 (step S13). Specifically, the registration unit 102a generates case basic data 106e (see case basic data table T6 in FIG. 7) in which the case number is associated with the customer code, contract period, and business contents, and case working hours data 106f (see case working hours data table T7 in FIG. 8) in which the case number is associated with working hours, according to the operation contents input by the operator via the input device 112, and stores them in the storage unit 106.

Then, the registration unit 102a executes a contract work registration process to register contract work basic data 106g that associates contract information with staff, according to the operation contents input by the operator via the input device 112 (step S14). Specifically, the registration unit 102a generates contract work basic data 106g (see contract work basic data table T8 in FIG. 9) that associates a staff code with a case number, according to the operation contents input by the operator via the input device 112, and stores it in the storage unit 106. After step S14, the work schedule creation device 100 ends this process.

[2-3: Work Schedule Creation Process]
Finally, a description will be given of the work schedule creation process executed by the work schedule creation device 100. Fig. 12 is a flowchart showing an overview of the work schedule creation process executed by the work schedule creation device 100.

As shown in FIG. 12, first, the output control unit 102b displays the work schedule input screen on the monitor 114 (step S21).

Figure 13 is a diagram showing an example of a work schedule input screen. The work schedule input screen P1 shown in Figure 13 includes a staff code cell K1 for inputting a staff code, a case number cell K2 for inputting a case number, and a year and month cell K3 for inputting the year and month. In addition, the work schedule input screen P1 includes a customer cell K4 that displays the customer code corresponding to the case number cell K2, a staff work schedule W1 corresponding to the staff code, and a register button B1 for registering the contents of the work schedule W1.

Returning to FIG. 12, the description of step S22 and subsequent steps will be continued.
In step S12, the creation unit 102c executes a work schedule creation process in which the operator creates work schedule data for a staff member corresponding to the staff code based on the staff code cell K1, case number cell K2, year and month cell K3, and customer cell K4 via the input device 112.

Figure 14 is a diagram showing an example of a work schedule input screen after the creation unit 102c creates work schedule data. Figure 15 is a diagram that illustrates the procedure when the creation unit 102c creates work schedule data.

As shown in Figures 14 and 15, the creation unit 102c creates work schedule data for the staff corresponding to the staff code according to the input contents of the staff code cell K1, the case number cell K2, and the year and month cell K3 by the operator via the input device 112. In this case, as shown in Figures 14 and 15, the creation unit 102c refers to the customer calendar master 106c, staff basic data 106d, case basic data 106e, case working hours data 106f, and contract work basic data 106g, and creates a work schedule W1 corresponding to the work schedule data by automatically setting the work schedule data table T100 (see Figure 15) for the target period of the staff corresponding to the staff code "10001" based on the input staff code "10001", case number (case number) "100", and year and month "2022/11".

Specifically, as shown in FIG. 15, the creation unit 102c determines whether there are any dates in the target period that are not registered in the customer calendar master 106c, and if it determines that there are any dates that are not registered, it determines that these dates are weekdays and sets them in the work schedule data table T100, which is the work schedule data. For example, in the case shown in FIG. 15, the creation unit 102c determines whether the working date and year "2022/11/1" in the target period is registered in the customer calendar master 106c, and since there is no registration, it determines that this working date and year "2022/11/1" is a weekday, and sets "weekday" to the holiday category of the work schedule data table T100.

In addition, the creation unit 102c does not create work schedule data if the date entered in the year/month cell K3 does not correspond to the contract period in the case basic data 106e. For example, as shown in the case basic data table T6, when the contract period is "2022/4/1 to 2023/3/31", the creation unit 102c does not create work schedule data when "2023/4" is entered in the year/month cell K3. In this case, the creation unit 102c outputs a warning message to the monitor 114 to the effect that the date entered by the operator in the year/month cell K3 is outside the contract period and is incorrect. This allows the operator to intuitively grasp the input error in the year/month cell K3. Of course, the creation unit 102c may output the contract period corresponding to the case number (case number) to the monitor 114 instead of the warning message.

Furthermore, in the case of scheduled holidays and statutory holidays in the year and month entered in the year and month cell K3, staff work does not occur on these days, so the creation unit 102c sets the specified time in the work schedule data table T100 to a fixed "0:00." For example, in the third row of the work schedule data table T100, the holiday category is "scheduled holiday," so the creation unit 102c sets the specified time to "0:00."

Furthermore, the creation unit 102c creates and manages two types of data: billing attendance data D1 for calculating bills to the dispatch destination using the work schedule data, and payroll attendance data D2 for paying staff salaries.

Returning to FIG. 12, the description of step S23 and subsequent steps will be continued.
In step S23, the creation unit 102c executes a correction process according to the correction operation performed by the operator to correct the work schedule data via the input device 112. Specifically, as shown in FIG. 14, when a staff member participates in an internal conference or the like at his/her company after working at the workplace, the schedules of the billed attendance data D1 and the salary attendance data D2 differ. Therefore, as shown in FIG. 14, when the operator corrects cell H1 of the salary attendance data D2 to "20:00" via the input device 112, the creation unit 102c executes a correction process to reflect the correction content in the work schedule data. Of course, when the operator corrects the contents of each of the billed attendance data D1 and the salary attendance data D2 via the input device 112, the creation unit 102c reflects the correction content in the work schedule data. This allows the operator to register the staff member's work schedule data via the work schedule input screen P1.

The output control unit 102b then executes an output process to output the work schedule data to the monitor 114 (step S24). This allows the operator to understand the work schedule data. After step S24, the work schedule creation device 100 ends this process.

According to the embodiment described above, the creation unit 102c refers to the customer calendar master 106c, staff basic data 106d, case basic data 106e, case working hours data 106f and contract work basic data 106g, and the operator creates work schedule data for the staff corresponding to the staff code via the input device 112 according to the staff code cell K1, case number cell K2, year and month cell K3 and customer cell K4, thereby reducing the workload of creating work schedules and enabling accurate creation of work schedules.

In addition, according to the embodiment, if the input date and year are not within the contract period, the creation unit 102c does not create work schedule data and outputs a warning to the effect that the input date and year are outside the contract period, so that the operator can intuitively grasp the input error in the date and year cell K3.

In addition, according to the embodiment, in the case of scheduled holidays and statutory holidays for the year and month entered by the creation unit 102c in the year and month cell K3, staff work does not occur on those days, so the specified time in the work schedule data table T100 is automatically set to a fixed "0:00", thereby reducing the workload of creating work schedules.

In addition, according to the embodiment, the creation unit 102c can create the work schedule data separately into billing attendance data D1 for calculating billing to the dispatch destination and payroll attendance data D2 for paying the salary of the staff corresponding to the input staff code, so that billing attendance and payroll attendance can be easily managed.

In addition, according to the embodiment, when a staff member participates in an internal company meeting or the like after working at the workplace, even if the schedule in the billed attendance data D1 differs from the schedule in the paid attendance data D2, the creation unit 102d can reflect this correction in the work schedule data.

[3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

4. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

In addition, with regard to the work schedule creation device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the work schedule creation device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the work schedule creation device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the work schedule creation device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The work schedule creation device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The work schedule creation device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

This invention is useful in the staffing industry.

100 Work schedule creation device 102 Control unit 102a Registration unit 102b Output control unit 102c Creation unit 104 Communication interface unit 106 Storage unit 106a Customer basic data 106b Holiday master 106c Customer calendar master 106d Staff basic data 106e Case basic data 106f Case working hours data 106g Contract work basic data 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (8)

A work schedule creation device including a control unit,
Customer calendar master that associates customer codes with dates and holiday categories,
Basic staff data that corresponds to staff code and name,
Basic data on the project, which corresponds to at least the customer code and contract period to the project number;
Case work time data in which at least work hours are associated with case numbers;
Basic data on contract work that corresponds to the case number and staff code,
is accessible to
a creation unit that refers to the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data, and creates work schedule data for a target period for a staff member corresponding to the staff code based on an input staff code, case number, and year and month;
A work schedule creation device comprising: The work schedule creation device according to claim 1,
The creation unit is
Refer to the case basic data, and if the input date and time are not within the contract period, do not create the work schedule data, and output a warning to the effect that the input date and time are outside the contract period.
A work schedule creation device comprising: The work schedule creation device according to claim 2,
The creation unit is
Refer to the customer calendar master, and if the holiday category is a scheduled holiday, set the scheduled time to 0 to create the work schedule data.
A work schedule creation device comprising: The work schedule creation device according to claim 3,
The creation unit is
The work schedule data is created separately into billing attendance data for calculating billing to the dispatch destination and payroll attendance data for paying the salary of the staff corresponding to the input staff code.
A work schedule creation device comprising: The work schedule creation device according to claim 4,
The creation unit is
According to the input operation, the billing attendance data and the salary attendance data are corrected to generate the work schedule data.
A work schedule creation device comprising: The work schedule creation device according to claim 5,
An output control unit that outputs the work schedule data is further provided.
A work schedule creation device comprising: A roster creation method executed by a roster creation device having a control unit,
The work schedule creation device includes:
Customer calendar master that associates customer codes with dates and holiday categories,
Basic staff data that corresponds to staff code and name,
Basic data on the project, which corresponds to at least the customer code and contract period to the project number;
Case work time data in which at least work hours are associated with case numbers;
Basic data on contract work that corresponds to the case number and staff code,
is accessible to
Executed by the control unit,
a creation step of creating work schedule data for a target period for a staff member corresponding to the staff code based on the input staff code, case number, and year and month, by referring to the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data;
A method for creating a work schedule, comprising: A work schedule creation program to be executed by a work schedule creation device having a control unit,
The work schedule creation device includes:
Customer calendar master that associates customer codes with dates and holiday categories,
Basic staff data that corresponds to staff code and name,
Basic data on the project, which corresponds to at least the customer code and contract period to the project number;
Case work time data in which at least work hours are associated with case numbers;
Basic data on contract work that corresponds to the case number and staff code,
is accessible to
To cause the control unit to execute
a creation step of creating work schedule data for a target period for a staff member corresponding to the staff code based on the input staff code, case number, and year and month, by referring to the customer calendar master, the staff basic data, the case basic data, the case working hours data, and the contract work basic data;
A work schedule creation program characterized by:

Images