Work schedule creation device, work schedule creation method, and work schedule creation program

The work schedule creation device automates the scheduling process by accessing customer and staff data to reduce manual effort and improve accuracy, addressing the inefficiencies of manual scheduling in the temporary staffing industry.

JP7812782B2Active Publication Date: 2026-02-10OBIC CO LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2022211227
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-12-28
Publication Date
2026-02-10
Estimated Expiration
2042-12-28

AI Technical Summary

Technical Problem

In the temporary staffing industry, creating work schedules manually leads to errors and a complex, labor-intensive process, making it difficult to efficiently and accurately manage work schedules for temporary employees.

Method used

A work schedule creation device equipped with a control unit that accesses customer calendar, staff, and contract data to automate the creation of work schedules, reducing manual effort and improving accuracy.

Benefits of technology

The device reduces the workload and enhances the accuracy of creating work schedules, enabling efficient management of staff schedules while minimizing errors and improving operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007812782000001
    Figure 0007812782000001
  • Figure 0007812782000002
    Figure 0007812782000002
  • Figure 0007812782000003
    Figure 0007812782000003
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a work schedule creation device, a work schedule creation method, and a work schedule creation program. [Background technology]

[0002] Patent Document 1 discloses a technique for creating a work schedule, such as work schedules and work shifts, for group members such as regular employees and non-regular employees such as part-time and dispatched workers. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-144609 Summary of the Invention [Problem to be solved by the invention]

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

[0005] However, because operators manually create work schedules, there are problems such as errors occurring when creating the schedules and the process being complicated, resulting in a great deal of effort being required to create the schedules.

[0006] 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. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the work schedule creation device of the present invention is a work schedule creation device equipped with a control unit, which 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 time 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 which is characterized by having a creation unit that references the customer calendar master, the staff basic data, the case basic data, the case working time data, and the contract work basic data, and creates work schedule data for the target period for the staff corresponding to the staff code based on the input staff code, case number, and year and month.

[0008] In addition, the work schedule creation method of the present invention is a work schedule creation method executed by a work schedule creation device equipped with a control unit, wherein the work schedule creation device has access to 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 time data in which a case number is associated with at least working hours, and completed work basic data in which a case number and a staff code are associated, and the method includes a creation step executed by the control unit that references the customer calendar master, the staff basic data, the case basic data, the case working time data, and the completed work basic data, and creates work schedule data for the target period for the staff corresponding to the staff code based on the input staff code, case number, and year and month.

[0009] In addition, the work schedule creation program of the present invention is a work schedule creation program to be executed by a work schedule creation device equipped with a control unit, wherein the work schedule creation device is capable of accessing a customer calendar master in which a customer code is associated with a year, month, 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 time data in which a case number is associated with at least working hours, and completed work basic data in which a case number and a staff code are associated, and is characterized in that the program includes a creation step to be executed by the control unit, which references the customer calendar master, the staff basic data, the case basic data, the case working time data, and the completed work basic data, and creates work schedule data for the target period for the staff corresponding to the staff code based on the input staff code, case number, and year and month. [Effects of the Invention]

[0010] According to the present invention, it is possible to reduce the workload of creating a work schedule and to create an accurate work schedule. [Brief explanation of the drawings]

[0011] [Figure 1] 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. [Figure 2] 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. [Figure 3] FIG. 3 is a diagram illustrating an example of a holiday master table in the holiday master stored in the storage unit of the work schedule creation device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a customer calendar master table in the customer calendar master stored in the storage unit of the work schedule creation device according to the embodiment. [Figure 5]FIG. 5 is a diagram showing an example of a staff basic data table in the staff basic data stored in the storage unit of the work schedule creation device according to the embodiment. [Figure 6] FIG. 6 is a diagram showing another example of a staff basic data table in the staff basic data stored in the storage unit included in the work schedule creation device according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a case basic data table in the case basic data stored in the storage unit of the work schedule creation device according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a job working hours data table of job working hours data stored in the storage unit included in the work schedule creation device according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a closed work basic data table in the closed work basic data stored in the storage unit of the work schedule creation device according to the embodiment. [Figure 10] FIG. 10 is a flowchart showing an outline of a customer calendar creation process executed by the work schedule creation device according to the embodiment. [Figure 11] FIG. 11 is a flowchart showing an outline of the contract information registration process executed by the work schedule creation device according to the embodiment. [Figure 12] FIG. 12 is a flowchart showing an outline of a work schedule creation process executed by the work schedule creation device according to the embodiment. [Figure 13] FIG. 13 is a diagram showing an example of the work schedule input screen. [Figure 14] FIG. 14 is a diagram illustrating 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. [Figure 15] FIG. 15 is a diagram for schematically explaining the procedure when the creation unit of the work schedule creation device according to the embodiment creates a work schedule. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments 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. However, the present invention is not limited to these embodiments.

[0013] [1. Configuration] An example of the configuration of a work schedule creation device according to this 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.

[0014] 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, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0015] The work schedule creation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the work schedule creation device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0016] 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). Note that the data stored in the memory unit 106 may also be stored in the server 200, for example.

[0017] 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 functions as a pointing device in cooperation with a mouse. 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.

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

[0019] The 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 the customer basic data 106a. The first row of the customer basic data table T1 shown in Figure 2 stores customer code "T0001" in association with customer name "XX Pharmaceutical" and address "ABC, Kyobashi, Chuo-ku, Tokyo."

[0020] 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. The first row of holiday master table T2 shown in Figure 3 stores the date "2022 / 1 / 1" in association with the holiday name "New Year's Day."

[0021] 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 the 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 the customer codes "T0001" and "T0003," but "Working day" is associated with the customer code "T0002." Details will be described later.

[0022] The staff basic data 106d stores a staff code in association with a name and a hire date. FIG. 5 is a diagram showing an example of a staff basic data table in the staff basic data 106d. In the first row of the staff basic data table T4 shown in FIG. 5, the name "Sample Taro" and hire date "2000 / 1 / 1" are stored in association with the staff code "10001." Note that the staff code in the staff basic data table T4 may also be stored in association with "optional items" in the PK item table T5 shown in FIG. 6. Here, optional items may be stored in association with, for example, staff (company employees), customers (dispatch destinations), and projects (contractual items).

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

[0024] The case working hours data 106f stores working hours in association with case numbers. Fig. 8 is a diagram showing an example of a case working hours data table in the case working hours data 106f. In the first row of the case working hours data table T7 shown in Fig. 8, the case number "100" is stored in association with a working time From "9:00" indicating the start time of the working hours, a working time To "18:00" indicating the end time of the working hours, and a predetermined time "8:00" indicating the working duration of the working hours.

[0025] The contract work basic data 106g stores staff codes in association with case numbers. 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 staff code "10001" in association with case number "100."

[0026] 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 processes based on these stored programs. The control unit 102 includes a registration unit 102a, an output control unit 102b, and a creation unit 102c.

[0027] The registration unit 102a executes a customer registration process to register customer basic data 106a in accordance with the operation details 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 details 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, based on the operation details input by the operator via the input device 112, to 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.

[0028] 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 for outputting to the monitor 114 work schedule data created by a creation unit 102c, which will be described later.

[0029] 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 executes a work schedule creation process in which the operator creates work schedule data for the staff corresponding to the staff code according to the staff code cell K1, case number cell K2, year / month cell K3, and customer cell K4 via the input device 112.

[0030] [2. Processing performed by the work schedule creation device] [2-1: Customer calendar creation process] First, a description will be given of the customer calendar creation process executed by the work schedule creation device 100. Fig. 10 is a flowchart showing an outline of the customer calendar creation process executed by the work schedule creation device 100.

[0031] 10, first, the registration unit 102a executes a customer registration process (step S1) to register customer basic data 106a in accordance with the operation content input by the operator via the input device 112. Specifically, the registration unit 102a stores in the storage unit 106 the customer basic data 106a (see customer basic data table T1 in FIG. 2) set in accordance with the operation content input by the operator via the input device 112.

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

[0033] The registration unit 102a then executes a customer calendar master maintenance process (step S3) by referencing the holiday master 106b and creating and registering a customer calendar master 106c (see customer calendar master table T3 in FIG. 4) with holiday classifications set for each customer based on the operation details entered by the operator via the input device 112. Specifically, the registration unit 102a first refers to the holiday master 106b and sets the customer's holidays in bulk. The registration unit 102a then refers to the holiday master 106b and automatically specifies the day of the week (Monday through Sunday) of the system date to set the scheduled and statutory holidays for each customer. In other words, the registration unit 102a automatically creates scheduled and statutory holidays for each customer using the batch setting function for days of the week in the holiday master 106b, without the operator having to manually enter the date, scheduled and statutory holidays via the input device 112. After step S3, the work schedule creation device 100 terminates this process.

[0034] [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 outline of the contract information registration process executed by the work schedule creation device 100.

[0035] 11, first, the registration unit 102a executes a staff registration process to register information about employees to be dispatched (step S10) in accordance with the operation content input by the operator via the input device 112. Specifically, the registration unit 102a generates staff basic data 106d in which a staff code is associated with a name and a joining date in accordance with the operation content input by the operator via the input device 112, and stores the data in the storage unit 106.

[0036] Next, the registration unit 102a executes a customer registration process to register basic information about the dispatch destination in accordance with the operation content 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 content input by the operator via the input device 112, and stores the data in the storage unit 106.

[0037] Thereafter, the registration unit 102a executes a customer calendar master maintenance process (step S12) to register the scheduled holidays and statutory holidays of the client's dispatch destination, that is, the client, in accordance with the operation content input by the operator via the input device 112. Specifically, the registration unit 102a performs maintenance on the customer calendar master 106c (see customer calendar master table T3 in FIG. 4) in which the date and holiday classification are associated with the client code, and stores the maintenance data in the storage unit 106.

[0038] Next, the registration unit 102a executes a case registration process to register the contract period, working hours, etc., in accordance with the operation content 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 content, and case working hours data 106f (see case working hours data table T7 in FIG. 8) in which the case number is associated with the working hours, in accordance with the operation content input by the operator via the input device 112, and stores these in the storage unit 106.

[0039] Thereafter, the registration unit 102a executes a contract work registration process to register contract work basic data 106g that associates contract information with staff members in accordance with the operation content 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 case numbers with staff codes in accordance with the operation content input by the operator via the input device 112, and stores the data in the storage unit 106. After step S14, the work schedule creation device 100 terminates this process.

[0040] [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 outline of the work schedule creation process executed by the work schedule creation device 100.

[0041] As shown in FIG. 12, first, the output control unit 102b causes the monitor 114 to display a work schedule input screen (step S21).

[0042] 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 for displaying the customer code corresponding to the case number cell K2, a work schedule W1 for the staff member corresponding to the staff code, and a register button B1 for registering the contents of the work schedule W1.

[0043] 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 the staff corresponding to the staff code according to the staff code cell K1, case number cell K2, year / month cell K3, and customer cell K4 via the input device 112.

[0044] Fig. 14 is a diagram showing an example of a work schedule input screen after the creation unit 102c has created work schedule data. Fig. 15 is a diagram for schematically explaining the procedure when the creation unit 102c creates work schedule data.

[0045] 14 and 15, the creation unit 102c creates work schedule data for the staff corresponding to the staff code in accordance with the input contents of the staff code cell K1, the case number cell K2, and the year and month cell K3 entered by the operator via the input device 112. In this case, as shown in FIGS. 14 and 15, the creation unit 102c references the customer calendar master 106c, the staff basic data 106d, the case basic data 106e, the case working hours data 106f, and the 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 FIG. 15) for the target period for 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."

[0046] 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 work year and month of the target period, "2022 / 11 / 1," is registered in the customer calendar master 106c, and since there is no registration, it determines that this work year and month, "2022 / 11 / 1," is a weekday, and sets "weekday" as the holiday category in the work schedule data table T100.

[0047] Furthermore, the creation unit 102c does not create work schedule data if the year and month 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 "April 1, 2022 - March 31, 2023," the creation unit 102c does not create work schedule data when "April 2023" is entered in the year / month cell K3. In this case, the creation unit 102c outputs a warning message to the monitor 114 indicating that the year and month entered by the operator in the year / month cell K3 is outside the contract period and is incorrect. This allows the operator to intuitively recognize 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.

[0048] Furthermore, the creation unit 102c sets the predetermined time in the work schedule data table T100 to a fixed "0:00" for scheduled holidays and statutory holidays in the year and month entered in the year and month cell K3, since no staff work occurs on those days. 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 predetermined time to "0:00."

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

[0050] 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 in response 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 company meeting or the like after working at their workplace, the schedules in the billed attendance data D1 and the paid attendance data D2 may differ. Therefore, as shown in FIG. 14, when the operator corrects cell H1 in the paid attendance data D2 to "20:00" via the input device 112, the creation unit 102c executes a correction process to reflect this correction in the work schedule data. Of course, when the operator corrects the contents of the billed attendance data D1 and the paid attendance data D2 via the input device 112, the creation unit 102c also reflects this correction 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.

[0051] Next, the output control unit 102b 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.

[0052] 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 according to the staff code cell K1, case number cell K2, year and month cell K3, and customer cell K4 via the input device 112, thereby reducing the workload of creating work schedules and enabling accurate creation of work schedules.

[0053] Furthermore, according to the embodiment, if the input year and month is 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 year and month is outside the contract period, so that the operator can intuitively understand that they have made an input error into the year and month cell K3.

[0054] Furthermore, according to the embodiment, in the case of scheduled holidays and statutory holidays in the year and month entered in the year and month cell K3 by the creation unit 102c, staff do not work 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.

[0055] Furthermore, according to the embodiment, the creation unit 102c can create the work schedule data by dividing it 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, thereby making it easy to manage billing attendance and payroll attendance.

[0056] Furthermore, according to the embodiment, when a staff member participates in an internal company meeting or the like after working at their workplace, even if the schedules in the billed attendance data D1 and the salary attendance data D2 differ, the creation unit 102d can reflect this correction in the work schedule data.

[0057] [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 contributing to the achievement of SDGs Goals 8 and 9.

[0058] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0059] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

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

[0061] 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 known methods.

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

[0063] Furthermore, with regard to the work schedule creation device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0064] For example, all or any part of the processing functions of the work schedule creation device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing 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 needed. That is, a computer program for issuing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0065] In addition, this computer program may 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.

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

[0067] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. 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.

[0068] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, 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.

[0069] 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 connected to any peripheral device. The work schedule creation device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

[0070] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0071] The present invention is useful in the staffing industry. [Explanation of symbols]

[0072] 100 Work schedule creation device 102 Control section 102a Registration Department 102b Output control section 102c Creation Department 104 Communication interface unit 106 Storage section 106a Customer Basic Data 106b Holiday Master 106c Customer Calendar Master 106d Staff Basic Data 106e Project Basic Data 106f Project Working Hours Data 106g Closing Work Basic Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A work schedule creation device including a control unit, Customer calendar master data that associates customer codes with customer dates and holiday categories, Staff basic data that corresponds to staff code and name, Project basic data in which at least the customer code and contract period are associated with the project number, Case working time data in which at least working hours are associated with case numbers; Basic data of the contract work that corresponds to the case number and staff code, is accessible to 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 a target period for a staff member corresponding to the staff code based on the input staff code, case number, and year and month; The creation unit Determine whether there are any dates in the customer calendar master that are not registered during the target period; If it is determined that there is a date for which no registration is made, the date for which no registration is made is determined to be a weekday, and the work schedule data is created. A work schedule creation device characterized by:

2. The work schedule creation device according to claim 1, The creation unit If the input date and time are outside the contract period, the system refers to the case basic data and does not create the work schedule data, but outputs a warning that the input date and time are outside the contract period. A work schedule creation device characterized by:

3. The work schedule creation device according to claim 2, The creation unit 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 characterized by:

4. The work schedule creation device according to claim 3, The creation unit At the time when the work schedule data is created, 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 characterized by:

5. 5. The work schedule creation device according to claim 4, The creation unit In response to the input operation, the billing attendance data and the payroll attendance data are corrected to create the work schedule data. A work schedule creation device characterized by:

6. 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 characterized by:

7. A roster creation method executed by a roster creation device including a control unit, The work schedule creation device includes: Customer calendar master data that associates customer codes with customer dates and holiday categories, Staff basic data that corresponds to staff code and name, Project basic data in which at least the customer code and contract period are associated with the project number, Case working time data in which at least working hours are associated with case numbers; Basic data of the 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 the target period of the staff 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; The creating step includes: Determine whether there are any dates in the customer calendar master that are not registered during the target period; When it is determined that there is a date for which no registration is made, the date for which no registration is made is determined to be a weekday, and the work schedule data is created accordingly. A method for creating a work schedule characterized by the above.

8. 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 data that associates customer codes with customer dates and holiday categories, Staff basic data that corresponds to staff code and name, Project basic data in which at least the customer code and contract period are associated with the project number, Case working time data in which at least working hours are associated with case numbers; Basic data of the 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 the target period of the staff 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; The creating step includes: Determine whether there are any dates in the customer calendar master that are not registered during the target period; When it is determined that there is a date for which no registration is made, the date for which no registration is made is determined to be a weekday, and the work schedule data is created accordingly. A work schedule creation program that features:

Citation Information

Patent Citations

  • Maintenance patrol job table producing device

    JP1995311803A

  • Method and device for managing license

    JP2002049435A

  • System and method for managing duty circumstances of dispatched employee, and program therefor

    JP2002324153A

  • Staff service managing method

    JP2003030387A

  • Estimated salary inquiry method, estimated salary inquiry system and program

    JP2005234799A