Dispatch business support system, dispatch business support method, and dispatch business support program

Abstract

To avoid losing an opportunity of price increase upon renewal of contact with a temp service company which dispatches staffs.SOLUTION: A temp service support system according to an embodiment of the present invention has case registration means for inputting a master set with reference for quantitative evaluation of staff and case data for registration, and alert output means for extracting staffs whose unit price should be increased upon renewal of contract with reference to the claimed attendance data and the variable allowance data and for outputting an alert according to the master settings.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a dispatching business support system, a dispatching business support method, and a dispatching business support program. [Background technology]

[0002] For example, in the temporary staffing industry, when staff are dispatched to client companies, excellent staff may repeatedly renew their contracts with the same company. Patent Document 1, for example, is an example of a system for evaluating the unit salary of temporary staff. [Prior art documents] [Patent documents]

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

[0004] However, there is no mention of preventing the loss of opportunities to raise unit prices when renewing contracts with dispatching companies that dispatch staff.

[0005] The present invention has been made in consideration of the above, and aims to provide a dispatching business support system, a dispatching business support method, and a dispatching business support program that can prevent the loss of an opportunity to raise unit prices when renewing a contract with a dispatching company that dispatches staff. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a dispatch business support system equipped with a memory unit and a control unit, wherein the memory unit stores a master that sets standards for quantitatively evaluating staff, project data including project number, customer, contract period, and billed hourly rate, billed attendance data including project number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and time spent late or leaving early, and variable allowance data including work number, staff, closing date, amount of variable allowance, and transaction category including bonus money, and the control unit comprises a project registration means for inputting and registering project data, and an alert output means for referencing the billed attendance data and the variable allowance data in accordance with the settings of the master, extracting staff whose unit price should be increased at the time of contract renewal, and outputting an alert.

[0007] According to another aspect of the present invention, an alert reference date is set in the master, The alert output means may output an alert for a case whose contract expiration date falls after the alert reference date of the master.

[0008] According to one aspect of the present invention, the master contains alert conditions and numerical values ​​of priority when the alert conditions are met for the number of days worked, absence, lateness, early departure, and bonus, and the alert output means may refer to the billed attendance data and the variable allowance data to determine whether each staff member meets the alert conditions for the number of days worked, absence, lateness, early departure, and bonus, calculate the sum of the numerical values ​​of priority, and output an alert for staff whose unit price should be increased when the contract is renewed if the sum exceeds a threshold value.

[0009] According to another aspect of the present invention, the master may be set for a common use or for each customer.

[0010] Furthermore, according to one aspect of the present invention, when a contract is renewed and the unit price remains unchanged despite negotiations with the dispatching client, the case registration means may register the reason for keeping the unit price unchanged in the case data in response to an operator's operation.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a dispatch work support method executed by an information processing device having a control unit and a memory unit, wherein the memory unit stores a master that sets criteria for quantitatively evaluating staff, project data including project number, customer, contract period, and billed hourly rate, billed attendance data including project number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and late / early departure hours, and variable allowance data including work number, staff, closing date, amount of variable allowance, and transaction category including bonus money, and the control unit executes a project registration process for inputting and registering project data, and an alert output process for referencing the billed attendance data and the variable allowance data in accordance with the settings of the master, extracting staff whose unit prices should be increased at the time of contract renewal, and outputting an alert.

[0012] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a dispatch work support program to be executed by an information processing device having a control unit and a memory unit, wherein the memory unit stores a master that sets criteria for quantitatively evaluating staff, project data including project number, customer, contract period, and billed hourly rate, billed attendance data including project number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and time spent late or early, and variable allowance data including work number, staff, closing date, amount of variable allowance, and transaction category including bonus money, and the control unit executes a project registration process in which project data is input and registered, and an alert output process in which, in accordance with the settings of the master, references the billed attendance data and the variable allowance data to extract staff whose unit prices should be increased at the time of contract renewal and outputs an alert. [Effects of the Invention]

[0013] According to the present invention, it is possible to prevent an opportunity loss for raising the unit price when renewing a contract with a client company that has dispatched staff. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a dispatching business support system according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the unit price alert master. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 4] FIG. 4 is a diagram illustrating a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the dispatching business support system in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of a dispatching business support system, a dispatching business support method, and a dispatching business support program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0016] [1. Overview] For example, in the temporary staffing industry, when staff are dispatched to client companies, talented staff may repeatedly renew their contracts with the same company.

[0017] However, even if the staff are excellent and need to be hired for a long period of time after contract renewal, there are cases where the unit price charged remains unchanged due to the power relations and lack of sales efforts of the client company.

[0018] Previously, even though dispatch contract data was managed in a system, it was not possible to utilize it in sales activities.

[0019] Therefore, in this embodiment, the ability of staff members, which is essentially qualitative, is quantitatively evaluated by focusing on data on attendance (lateness and absence) and bonus claims, and an alert is outputted to encourage an increase in the unit price at the time of contract renewal based on the evaluation, thereby preventing opportunity loss due to the unit price being left unchanged. Also, in this embodiment, if the unit price is left unchanged as a result of negotiations, the reason for this is managed so that it can be used in the next negotiation.

[0020] The dispatch business support system of this embodiment can be widely used, for example, in the personnel dispatch industry when negotiating unit prices at the time of contract renewal for regular dispatch, registered dispatch, engineer dispatch, and the like.

[0021] [2. Configuration] The configuration of a dispatching business support system 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the dispatching business support system 100.

[0022] The dispatching business support system 100 is, for example, a commercially available desktop personal computer or a workstation. As shown in Fig. 2, the dispatching business support system 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 dispatching business support system 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0023] The communication interface unit 104 communicatively connects the dispatching business support system 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 a communication line. Here, the network 300 has a function of communicatively connecting the dispatching business support system 100 with the server 200, sales representative terminals 400..., general affairs terminals 500..., etc., for example, the Internet or a LAN (Local Area Network). The sales representative terminals 400... are terminals used by sales representatives and are configured to be able to communicate data with the dispatching business support system 100. Furthermore, the general affairs terminals 500... are terminals used by general affairs personnel and are configured to be able to communicate data with the dispatching business support system 100.

[0024] 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 as a display unit, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0025] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. 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, an optical disk, etc.

[0026] The storage unit 106 includes a unit price alert master 106a and a data table 106b. Fig. 2 is a diagram showing an example of the configuration of the unit price alert master 106a.

[0027] The unit price alert master 106a is a master for setting the criteria for quantitative evaluation of temporary staff, and can be configured as a table or the like in which the following are associated and registered, as shown in Fig. 2: type (common or client), alert base date, priority value for number of working days, whether mandatory or not, and alert conditions for adding the priority value, priority value for absence, lateness, and leaving early, whether mandatory or not, and alert conditions for adding the priority value, and priority value for bonus, whether mandatory or not, and alert conditions for adding the priority value. The unit price alert master 106a is set by the master maintenance unit 102f.

[0028] The data table 106b is a table for storing various data such as case data, contract work data, billing attendance data, sales data, variable allowance data, etc. The sales representative terminal 400 and the general affairs representative terminal 500 can inquire about the case data, contract work data, billing attendance data, sales data, variable allowance data, etc. in the data table 106b.

[0029] The project data may include the project number, customer name, contract period (contract period From, contract period To), billed hourly rate, sales representative, general affairs representative, main business content, reason for contract price, etc.

[0030] The contracted work data may include work number, case number, staff code, dispatch period (dispatch period From, dispatch period To), billed hourly rate, etc.

[0031] The claimed attendance data may include staff code, closing date, work number, number of days worked, number of days absent, scheduled hours, overtime hours, and late / early departure times. "Scheduled hours" refers to working hours within a specified time frame set by the company (e.g., 7.5 hours from 9:00 to 17:30).

[0032] Sales data may include the case number, closing date, SEQ, unit price, quantity, amount, and transaction category (temporary staffing placement, advance payment, etc.).

[0033] The variable allowance data may include staff code, closing date, work number, sequence number, unit price, quantity, amount, transaction classification (bonus, domestic travel expenses, transportation expenses, communication expenses, expenses, etc.).

[0034] The control unit 102 is a CPU or the like that performs overall control of the dispatch business support system 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0035] The control unit 102 is configured to be able to access the unit price alert master 106a, the data table 106b, and the like stored in the memory unit 106. The unit price alert master 106a and the data table 106b may be provided in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0036] In terms of functional concept, the control unit 102 comprises a case registration unit 102a, a work schedule input unit 102b, a sales input unit 102c, a variable allowance input unit 102d, a unit price alert output unit 102e, a master maintenance unit 102f, and a screen display control unit 102g.

[0037] The case registration unit 102a provides a case registration screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs case data in response to operations on the case registration screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs terminal 500, and registers the case data in the data table 106b.

[0038] Furthermore, when a contract is renewed, the case registration unit 102a updates the case data in response to operations on the contract renewal registration screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs terminal 500, and if the unit price is kept the same after negotiations with the dispatching client, the reason for the contract unit price (reason for keeping the unit price the same) may be registered in the case data.

[0039] In addition, the case registration unit 102a provides a contract work data registration screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs contract work data in response to operations on the contract work data registration screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the data in the data table 106b.

[0040] The roster input unit 102b provides a roster input screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs billing attendance data in response to operations on the roster input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the data in the data table 106b.

[0041] The sales input unit 102c provides a sales input screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs sales data in response to operations on the sales input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the sales data in the data table 106b.

[0042] The variable allowance input unit 102d provides a variable allowance input screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs variable allowance data in response to operations on the variable allowance input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the data in the data table 106b.

[0043] The unit price alert output unit 102e references the billed attendance data and variable allowance data in the data table 106b in accordance with the settings of the unit price alert master 106a, extracts staff whose unit prices should be increased at the time of contract renewal, and outputs an alert. The alert may be output to the sales representative terminal 400 or the general affairs representative terminal 500.

[0044] In addition, an alert reference date may be set in the unit price alert master 106a, and the unit price alert output unit 102e may output an alert for cases whose contract expiration date falls after the alert reference date in the unit price alert master 106c.

[0045] In addition, the unit price alert master 106a may be configured to set alert conditions and priority values ​​when the alert conditions are met for the number of days worked, absence, lateness, early departure, and bonus, and the unit price alert output unit 102e may refer to the billed attendance data and variable allowance data to determine whether each staff member meets the alert conditions for the number of days worked, absence, lateness, early departure, and bonus, calculate the sum of the priority values, and output an alert for staff whose unit price should be increased when the contract is renewed if the sum exceeds a threshold.

[0046] The unit price alert master 106a may be common (common to all customers for which no customer is set) or may be set for each customer.

[0047] The master maintenance unit 102f is used to perform editing such as adding, deleting, and changing data in the unit price alert master 106a in response to, for example, an operator's operation on the unit price alert master screen displayed on the monitor 114.

[0048] The screen display control unit 102g controls the display and input of various screens (e.g., unit price alert master screen, case registration screen, contract renewal screen, contract work data registration screen, work schedule input screen, sales input screen, variable allowance input screen, etc.) displayed on the monitor 114.

[0049] [3. Specific Examples] Specific examples of processing by the control unit of the dispatch business support system 100 in this embodiment will be described with reference to Figures 1 to 10. Figures 3 to 10 are diagrams for explaining specific examples of processing by the control unit of the dispatch business support system 100 in this embodiment. In the following description, all monetary amounts are expressed in units of "yen," and the unit may be omitted.

[0050] (3-1. Regular billing operations) 3 to 7, a normal billing operation (registration of data that is the basis for evaluating staff) of the temporary staffing operation support system 100 in this embodiment will be described.

[0051] (Deal registration processing) A specific example of the case registration process will be described with reference to Figures 3 and 4. The case registration unit 102a executes the case registration process, and, for example, provides a case registration screen in response to access from the sales representative terminal 400 or the general affairs representative terminal 500, and inputs case data in response to operations on the case registration screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the data in the data table 106b. Basic information about the dispatch contract is registered through case registration.

[0052] Figure 3(A) is a diagram showing an example of case data. Figure 3(A) is a diagram showing an example of the case registration screen display. Case data includes fields such as case number, customer name, contract period From, contract period To, hourly rate billed, sales representative, general affairs representative, main business content, and reason for contract price. In the example shown in the figure, the first line contains case "NO100-1", customer name "●● Co., Ltd.", contract period From "20XX / 4 / 1", contract period To "20XX / 6 / 30", hourly rate billed "3,000", sales representative "U0001", and general affairs representative "U0010".

[0053] FIG. 3(B) is a diagram showing an example of the case registration screen. The case registration screen has input fields for case number, customer, billing address, individual contract period, sales representative, general affairs representative, and main business details, as well as a register button (not shown) and a contract renewal button. When data is entered in the input fields, case data corresponding to the input content is registered in data table 106b. For example, when the register button (not shown) is pressed with the input content shown in FIG. 3(B), data like the first line of the case data in FIG. 3(A) is registered.

[0054] In addition, the case registration unit 102a provides a contract work data registration screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs contract work data in response to operations on the contract work data registration screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the data in the data table 106b.

[0055] Figure 4 is a diagram showing an example of contracted work data (also called "allocation data"). Contracted work data may include the work number, case number, staff code, dispatch period From, dispatch period To, and billed hourly rate. In the example shown in the figure, the first line contains the work number "1," case number "100-1," staff code "S000001," dispatch period From "20XX / 4 / 1," dispatch period To "20XX / 6 / 30," and billed hourly rate "3,000." Since the unit price can differ depending on the staff allocated for the same case, the unit price used for billing is the unit price from the contracted work data. The work number is like a sequence, and is data used to link which staff member is allocated to which case.

[0056] (Work schedule entry processing) A specific example of the roster input process will be described with reference to Figure 5. The roster input unit 102b executes the roster input process, and for example, provides a roster input screen in response to access from the sales representative terminal 400 or the general affairs terminal 500, and inputs billed attendance data in response to operations on the roster input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs terminal 500, and registers the data in the data table 106b. In the attendance record input process, data required for billing is input.

[0057] In Figure 5, the billed attendance data has the following fields: staff code, closing date, work number, number of days worked, number of days absent, regular hours, overtime hours, and time late / early (in 1:00 units). In the example shown in the figure, the first line has the staff code "S000001," closing date "20XX / 4 / 30," work number "1," number of days worked "20," number of days absent "0," regular hours "160:00," overtime hours "20," and time late / early "0:00."

[0058] (Sales input processing) A specific example of the sales input process will be described with reference to Fig. 6. The sales input unit 102c executes the sales input process, and provides a sales input screen in response to access from, for example, the sales representative terminal 400 or the general affairs representative terminal 500, and inputs sales data in response to operations on the sales input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs representative terminal 500, and registers the sales data in the data table 106b. The sales data is used to manage sales that are not linked to people (staff), and is not directly related to this embodiment.

[0059] Sales data may include the case number, closing date, SEQ, unit price, quantity, amount, and transaction category (temporary employment, advance payment, etc.). In the example shown in the figure, the first line has the case number "100-1", closing date "20XX / 4 / 30", SEQ "1", unit price "10,000", quantity "1", amount "10,000", and transaction category "temporary employment".

[0060] (Variable allowance input processing) A specific example of the variable allowance input process will be described with reference to Fig. 7. The variable allowance input unit 102d executes the variable allowance input process, and, for example, provides a variable allowance input screen in response to access from the sales representative terminal 400 or the general affairs terminal 500, and inputs variable allowance data in response to operations on the variable allowance input screen by the sales representative at the sales representative terminal 400 or the general affairs representative at the general affairs terminal 500, and registers the variable allowance data in the data table 106b.

[0061] FIG. 7 is a diagram showing an example of variable allowance data. The variable allowance data includes the following fields: staff code, closing date, work number, SEQ, unit price, quantity, amount, and transaction category (bonus, domestic travel expenses, communication expenses, transportation expenses, expenses, etc.). The variable allowance data is used to manage sales linked to staff (people), and manages transportation expenses, communication expenses, and bonuses. In the example shown in the figure, the third line contains the staff code "S000001," closing date "20XX / 6 / 30," work number "1," SEQ "3," unit price "10,000," quantity "1," transaction category "10,000," and transaction category "bonus."

[0062] (3-2. Setting and outputting contract renewal unit price alerts) 8 and 9, the setting and output of the contract renewal unit price alert of the temporary staffing business support system 100 in this embodiment will be described.

[0063] (Unit price alert master maintenance processing) A specific example of the unit price alert master maintenance process will be described with reference to Fig. 9. The master maintenance unit 102f executes the unit price alert master maintenance process and sets data in the unit price alert master 106a in accordance with, for example, operations by an administrator on the unit price alert master screen displayed on the monitor 114. In the unit price alert master maintenance process, necessary information is set in the unit price alert master 106a.

[0064] There are two types of setting units (types): common and customer-specific. If there is no customer-specific setting, processing will be performed according to the common setting. Figure 8 shows an example of the display of the unit price alert master screen. Figure 8(A) shows an example when common is selected, and Figure 8(B) shows an example when common is selected.

[0065] As shown in Figure 8, the unit price alert master screen has a button for selecting the setting unit (type) as either common or by customer, a field for setting the alert base date, a field for setting the priority values ​​for each item of number of working days, absence, lateness, early departure, and bonus, whether or not it is required (priority is added if it is "required"), and the alert conditions for adding the priority values, and a registration button (not shown).

[0066] In the example shown in Fig. 8(A), "common" is set as the unit (type) of setting. For customers for which no customer is set, the common setting is used.

[0067] For the alert base date, an alert will be issued for the cases whose contract expiration date is in the set "number of days" after the alert. In this example, an alert will be issued for the cases whose contract expiration date is in "90" days.

[0068] Regarding the number of working days, if the number of working days is equal to or exceeds the "number of days" set in the alert conditions, the "priority value" set will be added. In this example, if the number of working days is "200" or more, the priority will be +10.

[0069] For absence, lateness, and early departure, if the number of days absent does not exceed the "number of days" set in the alert conditions, and the time of lateness or early departure does not exceed the "hours" set, the "priority" set will be increased. In this example, if the number of days absent is not "1 day" or more, and the time of lateness or early departure is not "1:00" or more, the priority will be increased by +20.

[0070] Regarding the reward, if a reward is claimed for the set "number of times," the set "priority" is added. In this example, if a reward is claimed for "1" more time, the priority is set to +30.

[0071] In the following, a case where the contents shown in FIG. 8(A) are set in the unit price alert master 106a will be described as an example.

[0072] (Unit price alert output processing) A specific example of the unit price alert output process will be described with reference to Figure 9. The unit price alert output unit 102e executes the unit price alert output process, and for example, in accordance with the settings of the unit price alert master 106a, references billing attendance data and variable allowance data, extracts staff whose unit prices should be increased at the time of contract renewal, and outputs an alert. The unit price alert output process determines which conditions are essential according to the settings of the unit price alert master 106a, and processes them. The priorities of the unit price alert master 106a are tallied from the achieved conditions, and alerts are output for those whose tallied results are above a threshold in order of priority (in order of likelihood of favorable negotiations).

[0073] In the main processing of unit price alerts, a daily batch process is used to calculate a date by adding the number of days in the unit price alert master to the system date (for example, 90 days in the example of Figure 8(A)), and then the project data (projects with contract renewals approaching) whose date matches the contract end date of the project data are extracted.

[0074] Among the staff members associated with the project, the staff members who are diligent and have made a great contribution should have their billing rate increased. The following data is compiled as the basis for this judgment.

[0075] (1) Count the number of days worked from the claimed attendance data. If the employee has worked on projects in the same industry in the past, that period will also be included in the calculation. (2) The number of days absent and the time spent arriving late or leaving early are compiled from the claimed attendance data. (3) The number and amount of bonus payments are compiled from the variable allowance data.

[0076] FIG. 9(A) is a diagram showing an example of the collected data. The collected data includes the following items: work number, case number, staff code, contract period To, number of working days, number of absent days, time of lateness / early departure, number of bonuses, bonus amount, and priority. In the example shown in the figure, the first line has work number "2," case number "100-2," staff code "S000001," contract period To "20XX / 9 / 30," number of working days "240," number of absent days "0," time of lateness / early departure "0:00," number of bonuses "1," and bonus amount "10,000." The second line has work number "4," case number "100-2," staff code "S000002," contract period To "20XX / 9 / 30," number of working days "240," number of absent days "0," time of lateness / early departure "0:00," number of bonuses "1," and bonus amount "10,000." The third line is Work No. "6", Case No. "100-2", Staff Code "S000004", Contract Period To "20XX / 9 / 30", Number of days worked "120", Number of days absent "0", Time late / early leaving "0:00", Number of times bonuses "0", Bonus amount "0".

[0077] For the aggregated data, subjects are extracted from the following perspective (in the example setting of Figure 8(A)). Specifically, the priority values ​​are summed up, and steps whose sum of priorities is equal to or greater than a threshold value (e.g., 40) are extracted.

[0078] (1) The number of working days is more than 200 (priority +10). By using the number of working days instead of the contract period, it is determined that the employee has experience in the work. (2) No absences from work or lateness or early departures (priority increased by 20). Not being absent from work or lateness or early departures can be considered diligent. (3) If you have received a reward in the past (priority +30), you can be judged as having made a significant contribution.

[0079] FIG. 9B is a diagram for explaining an example in which the sum of priorities is calculated in FIG. 9A, and staff members whose sum of priorities is equal to or greater than a threshold value (for example, 40) are extracted as alert targets.

[0080] Work No. "2" is extracted as an alert target because the total priority is "60." Work No. "2" has a bonus (priority +30), has worked more than "200" days (priority +10), and has never been absent or arrived late or left early (priority +20).

[0081] Work No. "4" is excluded because the total priority is "0." Work No. "4" does not have a bonus, the number of days worked does not exceed "200," and there are absences, lateness, and early departures.

[0082] Work No. "6" is excluded because the total priority is "20." Work No. "6" has no absences or lateness or early departures, but its priority is "+20," no bonus was paid, and the number of days spent on the work is short, so it is excluded.

[0083] As a result of the above extraction, there is room for negotiation to increase the unit price for work No: 2 (case 100-2, staff code S000001) when the contract is renewed. An alert is output to the sales representative (sales representative terminal 400) and the general affairs representative (general affairs terminal 500) to encourage them to prepare for negotiation. The alert is displayed when the sales representative logs in to the dispatch business support system 100 on the sales representative terminal 400 or the general affairs representative logs in to the general affairs terminal 400. If the unit price was left unchanged in the previous negotiation, the reason for the contract unit price recorded at the time of the previous contract renewal is displayed.

[0084] (3-3. Contract Renewal) Contract renewal in the dispatch business support system 100 in this embodiment will be described with reference to Fig. 10. Fig. 10(A) is a diagram showing a display example of a job registration screen, and Fig. 10(B) is a diagram showing a display example of a contract renewal registration screen.

[0085] When renewing a contract, pressing the Contract Renew button on the Project Registration screen, as shown in FIG. 10(A), displays the Contract Renewal Registration screen, as shown in FIG. 10(B). As shown in FIG. 10(B), the Contract Renewal Registration screen includes fields for the Project No., the individual contract periods before and after contract renewal, the billed hourly rate, and an input field for the reason for the contract price. On the Contract Renewal screen, the branch number of the Project No. is counted up and automatically displayed. The data before the contract renewal is carried over, and the individual contract period and the billed hourly rate before the contract renewal are automatically displayed. The operator inputs the individual contract period and the billed hourly rate after the contract renewal. Furthermore, if the rate remains unchanged after negotiations with the client, the operator enters the reason in the input field for the contract rate reason. In this example, the operator enters, "Due to budget constraints, we cannot increase the rate for this contract renewal. We will consider the rate at the next contract renewal based on the work performed during the current contract period." Pressing the Register button (not shown) registers the data entered on the Contract Renewal screen into the project data. This reason for the contract unit price is also written in the alert that is displayed when the sales representative or the general affairs representative logs in to the dispatch business support system 100 on the sales representative terminal 400 or the general affairs representative terminal 400, so that it can be used in the next negotiation.

[0086] As explained above, this embodiment is provided with unit price alert master 106a which sets standards for quantitatively evaluating staff, and unit price alert output unit 102e which, in accordance with the settings of unit price alert master 106a, refers to billed attendance data and variable allowance data in data table 106b, extracts staff whose unit prices should be increased at the time of contract renewal, and outputs an alert, thereby making it possible to prevent the loss of opportunities to increase unit prices when renewing a contract with a client company that dispatches staff.

[0087] [4. 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.

[0088] 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.

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

[0090] 5. 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.

[0091] 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.

[0092] 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.

[0093] Furthermore, with regard to the dispatch business support system 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0094] For example, all or any part of the processing functions of the dispatch business support system 100, particularly the processing functions performed by the control unit 102, 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 an information processing device to execute the processes described in this embodiment, and is mechanically read by the dispatch business support system 100 as needed. That is, a computer program for providing 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). The computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0095] In addition, this computer program may be stored in an application program server connected to the dispatch business support system 100 via any network, and all or part of it may be downloaded as needed.

[0096] In addition, the program for executing the processes 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" 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), a Compact Disk Read-Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray Disc (Blu-ray). Therefore, a recording medium storing a program for executing the processes or processing methods described in this specification also constitutes the present invention.

[0097] 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 program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by cooperating with other programs, such as an OS. Note that well-known configurations and procedures can be used for the specific configurations and reading procedures for reading a recording medium in each device described in the embodiments, as well as installation procedures after reading.

[0098] The various databases stored in the memory unit 106 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.

[0099] The dispatch business support system 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 dispatch business support system 100 may also be realized by installing software (including programs or data) that causes the device to perform the processing described in this embodiment.

[0100] 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 functionally or physically distributed and integrated 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. [Explanation of symbols]

[0101] 100 Dispatch Business Support System 102 Control section 102a Case Registration Department 102b Work schedule input section 102c Sales input section 102d Variable allowance input section 102e Unit Price Alert Output Unit 102f Master Maintenance Department 102g Screen display control unit 104 Communication interface unit 106 Storage section 106a Unit Price Alert Master 106b Data Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 Sales representative terminal 500 General affairs terminal

Claims

1. A dispatching business support system including a storage unit and a control unit, The storage unit includes: A master who sets standards for quantitatively evaluating staff, Project data including project number, client to which the worker is dispatched, contract period, and billing hourly rate; Claimed attendance data including case number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and late / early departure times; Variable allowance data including a transaction category including a work number, a staff member, a closing date, an amount of variable allowance, and a bonus; is stored, The control unit a case registration means for inputting and registering case data; an alert output means for extracting staff whose unit prices should be increased at the time of contract renewal and outputting an alert by referring to the billing attendance data and the variable allowance data in accordance with the settings of the master; A dispatching business support system comprising:

2. The master has an alert reference date set therein, 2. The dispatch business support system according to claim 1, wherein the alert output means outputs an alert for a case whose contract expiration date comes after the alert reference date of the master.

3. The master contains alert conditions and priority values ​​for when the alert conditions are met for the number of working days, absence, lateness, early departure, and bonus. The dispatch business support system of claim 1, characterized in that the alert output means refers to the billed attendance data and the variable allowance data, determines whether each staff member meets the alert conditions for number of working days, absence, lateness, early departure, and bonus, calculates the sum of priority values, and if the sum is above a threshold, outputs an alert indicating that the staff member should have their unit price increased when their contract is renewed.

4. 2. The dispatching business support system according to claim 1, wherein the master can be set either in common or for each client.

5. The dispatch business support system described in any one of claims 1 to 4 is characterized in that, when the unit price is kept the same despite negotiations with the customer at the time of contract renewal, the case registration means registers the reason for keeping the unit price unchanged in the case data in response to an operator's operation.

6. A dispatching business support method executed by an information processing device including a control unit and a storage unit, The storage unit includes: A master who sets standards for quantitatively evaluating staff, Project data including project number, client to which the worker is dispatched, contract period, and billing hourly rate; Claimed attendance data including case number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and late / early departure times; Variable allowance data including work number, staff, closing date, amount of variable allowance, and transaction category including bonus; is stored, Executed in the control unit: A case registration process in which case data is entered and registered; an alert output process for extracting staff whose unit prices should be increased at the time of contract renewal and outputting an alert by referring to the billing attendance data and the variable allowance data in accordance with the settings of the master; A dispatching business support method comprising:

7. A dispatching business support program to be executed by an information processing device having a control unit and a storage unit, The storage unit includes: A master who sets standards for quantitatively evaluating staff, Project data including project number, client to which the worker is dispatched, contract period, and billing hourly rate; Claimed attendance data including case number, work number, staff, closing date, number of working days, number of absent days, scheduled hours, overtime hours, and late / early departure times; Variable allowance data including work number, staff, closing date, amount of variable allowance, and transaction category including bonus; is stored, In the control unit, A case registration process in which case data is entered and registered; an alert output process for extracting staff whose unit prices should be increased at the time of contract renewal and outputting an alert by referring to the billing attendance data and the variable allowance data in accordance with the settings of the master; A dispatch business support program to help you achieve this.

Images