Information processing method, program, and information processing device

Abstract

To simplify the setting of recruitment details for on-call positions. [Solution] The information processing method performs the following actions: classifying each regular job posting into each job posting group based on predetermined conditions; setting the number of available positions for each regular job posting to be allocated to the job posting group based on the number of positions available for each regular job posting included in the classified job posting group; or setting the area for the available positions to be allocated to the job posting group based on the work location of each regular job posting.

Description

Technical Field

[0001] The present disclosure relates to an information processing method, a program, and an information processing apparatus.

Background Art

[0002] Conventionally, there is a system for supporting job recruitment. For example, a job-seeker and job-offer matching method that enables smooth information transmission and reception between job-seekers and job-offerers is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, for example, in a job offer platform that provides job offers for temporary work, workers often engage in spot-based work and can easily cancel, so there is a possibility of vacancies occurring. When vacancies occur, it may disrupt the operation of the business. Therefore, when sudden vacancies occur, the business operator must set job offer information each time.

[0005] Therefore, one of the objectives of the present disclosure is to provide an information processing method, a program, and an information processing apparatus that can easily set the recruitment details for job offers (also referred to as "standby job offers" for example) in case of vacancies.

Means for Solving the Problems

[0006] An information processing method according to one embodiment of the present disclosure includes classifying each regular job posting into each job posting group based on predetermined conditions, setting the number of available positions for each regular job posting to be allocated to the job posting group based on the number of positions available for each regular job posting included in the classified job posting group, or setting the area for the available positions to be allocated to the job posting group based on the work location of each regular job posting. [Effects of the Invention]

[0007] The disclosure technology makes it possible to easily set up the recruitment details for on-call positions. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows examples of the configurations of the information processing system in the embodiment. [Figure 2] This is a block diagram showing an example of an information processing device according to the embodiment. [Figure 3] This block diagram shows an example of a server according to the embodiment. [Figure 4] This figure shows an example of user information according to the embodiment. [Figure 5] This figure shows an example of regular job posting information according to the embodiment. [Figure 6] This figure shows an example of waiting list job information according to the embodiment. [Figure 7] This figure shows an example of cancellation rate information according to the embodiment. [Figure 8] This figure shows an example of matching rate information according to the embodiment. [Figure 9] This is a sequence diagram showing an example of processing related to waiting job postings according to the embodiment. [Figure 10] This figure shows an example of a job listing screen according to the embodiment. [Figure 11] This figure shows an example of a screen illustrating the details of a waiting job according to the embodiment. [Figure 12] This figure shows an example of a vacancy notification screen according to the embodiment. [Figure 13] This figure shows an example of a screen displaying details of a matched regular job posting according to the embodiment. [Figure 14] This flowchart shows an example of the processing procedure for generating waiting list job information according to the embodiment. [Figure 15] This flowchart shows an example of a procedure for handling a vacancy that occurs according to the embodiment. [Modes for carrying out the invention]

[0009] Embodiments of this disclosure will be described in detail below with reference to the drawings. The same elements are denoted by the same reference numerals, and redundant descriptions are omitted.

[0010] [Embodiment] First, let's explain the "standby job postings" used in this embodiment. Unlike general job postings, standby job postings include a type of job posting called same-day standby or standby personnel (hereinafter collectively referred to as "standby job postings"). Standby job postings involve waiting at a designated location for a designated time, and are jobs where, if a vacancy occurs at a workplace, the worker goes to that site and performs the work. In this embodiment, when a business sets up regular job postings ("regular job postings"), the job posting platform (also referred to as the "job posting platform") generates standby job postings ("standby job postings") based on the regular job postings. By recruiting standby workers in advance, when a vacancy occurs among workers in regular jobs (also referred to as "regular workers"), the vacancy can be immediately filled from standby workers (also referred to as "standby workers").

[0011] In addition, since standby job seekers do not necessarily occur, it is highly likely that it is not efficient to recruit one standby job seeker for one regular job seeker. Therefore, when generating job information for standby job seekers, the job information providing platform generates one standby job seeker for a plurality of regular job seekers, and sets the recruitment details of the standby job seeker (for example, the number of recruits and the recruitment area) based on the plurality of regular job information and the like. Thereby, when generating standby job information, it is possible to easily set the recruitment details of the standby job seeker.

[0012] In addition, standby job seekers are recruited in advance in case of vacancies in regular job seekers. However, since personnel are put on standby, even if no vacancy occurs, remuneration will be paid according to the standby time. That is, if too many standby job seekers are recruited, the cost will increase, but if there are too few standby job seekers, it will be impossible to fill the vacancies. Therefore, it is necessary to appropriately set the recruitment details of standby job seekers while considering the cost balance. In the present embodiment, by automatically or semi-automatically setting the number of recruits and the recruitment area of standby job seekers, including the final confirmation work, etc., it becomes possible to easily set the recruitment details of standby job seekers.

[0013] Hereinafter, workers may be referred to as "users on the worker side", and business operators may be referred to as "users on the business operator side". In addition, in the present embodiment, a service (hereinafter, also referred to as a "job seeking service") that enables viewing, application, etc. of job information provided on the job information providing platform is provided. In addition, when not distinguishing between regular job seekers and standby job seekers, it may also be referred to as a "job seeker", and similarly, when not distinguishing between regular job information and standby job information, it may also be referred to as "job information".

[0014] <System Configuration Example> FIG. 1 is a diagram showing each configuration example of the information processing system 1 in the embodiment. In the example shown in FIG. 1, each information processing device 10A, 10B, 10C used by each user, an information processing device or server 20 that manages the job information providing platform, for example, a database 30 that manages user information, regular job information, standby job information, cancellation rate information, matching rate information, etc. are connected via the network N. Note that for the information processing devices 10A, 10B, 10C, any number can be connected to the network N, and when not individually distinguished, they are also referred to as the information processing device 10.

[0015] The information processing device 10 is, for example, a smartphone, a computer, a tablet terminal, etc. The information processing device 10 can provide a job service to the user by installing an application (hereinafter also referred to as a "job application") that executes the job service disclosed in the embodiment. Also, when the job service is implemented on a web page, the information processing device 10 can also use the job service using a web browser.

[0016] The information processing device 20 is, for example, a server and may be composed of one or more devices. Also, the information processing device 20 manages the job information providing platform, provides job information, registers users, processes viewing, application, etc. of jobs, generates standby job information from regular job information, and sets the recruitment content of standby jobs. Hereinafter, the information processing device 20 is also referred to as the server 20.

[0017] The database 30 has a storage unit that stores or manages user information of each worker registered in the job service, regular job information of each business operator, standby job information of a predetermined business operator among each business operator, cancellation rate information, matching rate information, etc.

[0018] <An example of the configuration of the user-side device> Figure 2 is a block diagram showing an example of an information processing device 10 according to an embodiment. The information processing device 10 includes one or more processing units (CPUs) 110, one or more network or other communication interfaces 120, memory 130, user interface 150, and one or more communication buses 170 for interconnecting these components.

[0019] The user interface 150 is, for example, a user interface comprising a display 151 and an input device (such as a keyboard and / or mouse or some other pointing device) 152. The user interface 150 may also be a touch panel.

[0020] The memory 130 may be, for example, a high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory, or it may be a non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 130 may also be a computer-readable non-temporary recording medium.

[0021] Another example of memory 130 may be one or more storage devices located remotely from the CPU 110. In one embodiment, memory 130 stores programs, modules, and data structures, or subsets thereof, relating to the following job application.

[0022] The operating system 131 includes, for example, procedures for handling various basic system services and for executing tasks using hardware.

[0023] The network communication module 132 is used, for example, to connect the information processing device 10 to another computer via one or more network communication interfaces 120 and one or more communication networks such as the Internet, other wide area networks, local area networks, and metropolitan area networks.

[0024] App data 133 includes data processed when a user uses the job search service. For example, app data 133 includes user information and information obtained from server 20. Specifically, job search information related to job postings is included in app data 133.

[0025] The service processing module 134 executes various processes on the job information provision platform provided by the server 20. For example, the service processing module 134 includes an acquisition module 135, an output module 136, and a processing module 137, which will be described later. The service processing module 134 may also change its processing content depending on whether the user logged into the job information provision platform is a business operator or a worker. Furthermore, the service processing module 134 corresponds to the job application or web browser described above.

[0026] For example, information processing device 10A is a device used by users on the business side, and information processing device 10B is a device used by users on the worker side. In the following, the business side information processing device 10A will be denoted with the letter A, and the worker side information processing device 10B will be denoted with the letter B. In the following, we will describe an example of separating processing according to the logged-in user for a job application, but it is also possible to implement separate applications for businesses and workers. Note that information processing device 10C is also assumed to be a device used by workers, but since it is the same as information processing device 10B, the explanation will be omitted.

[0027] ≪Business side≫ First, let's explain the various processes in the information processing device 10A on the business side. The acquisition module 135A acquires user operations on buttons (an example of UI components) on the display screen shown on the display 151A. For example, the acquisition module 135A acquires commands corresponding to click operations on the job posting settings button on a web page or application screen via the user interface 150A. The settings button is a button that a business uses to set recruitment conditions, etc., when posting job openings.

[0028] Furthermore, the acquisition module 135A may acquire commands corresponding to click operations on the job posting settings button on a web page or application screen via the user interface 150A. The job posting settings button is used by businesses when they want to set and publish job postings.

[0029] Job postings include publicly available, regular job postings that are generally made public to users who have registered with the job posting service.

[0030] Output module 136A outputs official job posting information and official job posting configuration requests set by the user on the business side to server 20.

[0031] Processing module 137A performs the above-mentioned processing of setting up official job postings, and verifying and / or approving workers who have applied for the job postings (also referred to as "applicant workers"). For example, processing module 137A receives operations from the business operator, cooperates with server 20, and performs processing such as setting individual condition information included in the official job postings, and verifying and / or approving applicant workers.

[0032] The display control module 138A controls the display of a single screen from a job application or web page. For example, the display control module 138A controls the display to show the job settings screen, the applicant worker confirmation screen, etc., on the display 151A.

[0033] ≪Worker's perspective≫ Next, we will describe the processes in the worker-side information processing device 10B. Based on the worker's actions, the operating system 131B accesses a designated website or the like to download and install the job application program. This makes the service processing module 134B executable.

[0034] Furthermore, the service processing module 134B may be a job application as described above, but it may also be a web browser. The service processing module 134B accesses a URL that provides a job information provision platform, or obtains screen information related to the job service from the server 20 via the job application, or sends information to the server 20.

[0035] The acquisition module 135B acquires user operations on each button within the display screen shown on the display 151B. For example, the acquisition module 135B acquires registration information set by the worker's user operations on the user registration screen.

[0036] When new user registration information is set based on user operations, output module 136B sends the registration information and a new registration request to server 20. The registration information includes, for example, the user's name, address, telephone number, etc., entered by the worker. When server 20 receives the new registration request, it processes the new user registration based on the registration information.

[0037] Furthermore, if a worker performs an operation to request to view job postings, output module 136B outputs a viewing request to server 20. Also, if a worker performs an operation to apply for a job from the job posting viewing screen, output module 136B outputs an application request to server 20.

[0038] Processing module 137B performs processing related to the job posting service. For example, on the worker side, it has functions such as a notification function for favorite job postings and a messaging function with employers.

[0039] The display control module 138B controls the display of screens for job application apps and web pages. For example, the display control module 138B controls the display of user registration screens, job information viewing screens, job application screens, etc., on the display 151B.

[0040] One or more processing units (CPUs) 110 may read and execute each module from the memory 130 as needed. For example, one or more processing units (CPUs) 110 may constitute a communication unit by executing a network communication module 132 stored in the memory 130. Alternatively, one or more processing units (CPUs) 110 may constitute a service processing unit, an acquisition unit, an output unit, a processing unit, and a display control unit by executing a service processing module 134, an acquisition module 135, an output module 136, a processing module 137, and a display control module 138, respectively, which are stored in the memory 130. Furthermore, the processing of each of the service processing module 134, the acquisition module 135, the output module 136, the processing module 137, and the display control module 138 may be executed by one or more processing units (CPUs) 110.

[0041] In other embodiments, the service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 may be standalone applications stored in the memory 130 of the information processing device 10. Standalone applications include, but are not limited to, acquisition applications, output applications, processing applications, and display control applications. In yet another embodiment, the service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 may be add-ons or plug-ins to other applications.

[0042] Each of the elements described above may be stored in one or more of the aforementioned storage devices. Each of the modules described above corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) described above do not need to be implemented as separate software programs, procedures, or modules, and therefore various subsets of these modules may be combined or reconfigured in various embodiments. In one embodiment, memory 130 may store a subset of the modules and data structures described above. Furthermore, memory 130 may store additional modules and data structures not described above.

[0043] As mentioned above, the application for the business operator and the application for the worker may be implemented as separate applications. In this case, the worker can use the job application by downloading and installing the worker's job application program from a designated website or the like to their information processing device 10B, and the business operator can use the business's job application program by downloading and installing the business operator's job application program from a designated website or the like to their information processing device 10A.

[0044] <Example of server-side device configuration> Figure 3 is a block diagram showing an example of a server 20 according to an embodiment. The server 20 includes one or more processing units (CPUs) 210, one or more network or other communication interfaces 220, memory 230, and one or more communication buses 270 for interconnecting these components.

[0045] The server 20 may optionally include a user interface 250, which may include a display device (not shown) and a keyboard and / or mouse (or some other pointing device or other input device; not shown).

[0046] Memory 230 may be, for example, a high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory, or it may be a non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory 230 may also be a computer-readable non-temporary recording medium.

[0047] Another example of memory 230 is one or more storage devices located remotely from the CPU 210. In one embodiment, memory 230 stores the following programs, modules, and data structures, or subsets thereof:

[0048] The operating system 231 includes, for example, procedures for handling various basic system services and for executing tasks using hardware.

[0049] The network communication module 232 is used, for example, to connect the server 20 to other computers via one or more network communication interfaces 220 and one or more communication networks such as the Internet, other wide area networks, local area networks, and metropolitan area networks.

[0050] User information 233 includes information about users who use the job posting platform. For example, user information 233 includes user information, applied job information, etc., associated with each user ID. User information 233 will be described later using Figure 4.

[0051] Regular job postings 234 include one or more regular job postings registered on a job posting platform or job service. For example, regular job postings 234 include information such as regular job ID, posting date, working hours, job type, job description, number of openings, employer, work location, hourly wage, and cancellation rate. Regular job postings 234 will be described later using Figure 5.

[0052] The standby job information 235 includes standby job information generated based on regular job information. For example, standby job information 235 includes standby job ID, regular job ID, number of standby positions available, job type, work location, work location ID, standby date and time, standby hourly wage, etc. Standby job information 235 will be described later with reference to Figure 6.

[0053] Cancellation rate information 236 includes information on cancellation rates for each job type. Cancellation rate information 236 may also include values ​​determined based on past statistical data. For example, cancellation rate information 236 may include cancellation rates by time slot, cancellation rates by job type, etc. Cancellation rate information 236 will be described later using Figure 7.

[0054] Matching rate information 237 includes information on the matching rate of regular job postings for each work location. For example, matching rate information 237 includes the matching rate of regular job postings for each work location ID. Matching refers to the process where a job posting and a worker are associated (an application is completed). Specifically, matching may occur when a worker applies for a regular job posting and the employer of the regular job posting accepts the application. Matching rate information 237 will be discussed later using Figure 8.

[0055] The service control module 238 manages the processing related to job postings and benefits on the job posting platform. For example, the service control module 238 has a classification module 239, a configuration module 240, an output module 241, and a selection module 242 for processing related to job postings.

[0056] The classification module 239 classifies each regular job posting into a job posting group based on predetermined conditions. Specifically, the classification module 239 repeatedly extracts regular job postings that meet predetermined conditions from among multiple regular job postings included in the regular job posting information 234, and classifies one or more of the extracted regular job postings into one group.

[0057] The configuration module 240 sets the number of standby positions to be assigned to each regular job in the job group, based on the number of positions available in each regular job within the job group. Specifically, the configuration module 240 sets the number of standby positions based on the total number of positions available in one or more regular job in the job group classified by the classification module 239. For example, if the total number of positions available in regular jobs is 10, and the probability of a worker canceling after applying for a regular job (hereinafter also referred to as the "cancellation rate") is 10%, then it is conceivable to set the number of standby positions to be assigned to 1. Alternatively, the configuration module 240 sets the area for standby positions to be assigned to the job group based on the work location of each regular job. Here, "work location" indicates the place where a worker would work if they applied for a regular job, for example, ABC store in Shibuya-ku, Tokyo. The "area" indicates the range within which the work locations of regular jobs exist. In other words, the area for standby positions indicates where a worker would work if a vacancy arises in a regular job. For example, if the area for a waiting list job is "Sapporo City, Hokkaido," it means that the waiting list job is to fill a vacancy in a regular job within Sapporo City, Hokkaido. For example, the setting module 240 may set the area for waiting list jobs so that it includes all of the work locations of one or more regular jobs included in the job group classified by the classification module 239. If the work location of regular job A included in the job group is Shibuya Ward, Tokyo, and the work location of regular job B included in the job group is Minato Ward, Tokyo, the setting module 240 may set the area for waiting list jobs to Shibuya Ward and Minato Ward, Tokyo.

[0058] The above process makes it possible to easily set up the recruitment details for standby positions. For example, when setting up regular job postings, employers do not need to set up the recruitment details for standby positions. Also, because it is based on the regular job posting information set by the employer, the recruitment details for standby positions will be set appropriately.

[0059] Furthermore, the specified conditions may include conditions regarding the work location of each regular job posting. That is, the classification module 239 may classify each regular job posting into a job group based on the conditions regarding the work location of each regular job posting. For example, the classification module 239 may group multiple regular job postings included in the regular job posting information 234 into job groups on a city / ward / town / village basis, such as a job group where the work location is in Ward A, a job group where the work location is in Ward B, and so on. Alternatively, the classification module 239 may group one or more regular job postings whose work location is within a specified range from the location information of a worker user. That is, in order to dynamically set up waiting job postings specifically for a worker user, a job group may be created based on the location information of that user.

[0060] Through the above process, by classifying regular job postings into job groups according to their work locations, it becomes possible to consolidate the work locations of standby job postings, and to set more appropriate recruitment details for standby job postings.

[0061] Furthermore, the specified conditions may also include conditions relating to the job type of each regular job posting. That is, the classification module 239 may classify each regular job posting into a job group based on the conditions relating to the job type of each regular job posting. For example, the classification module 239 may group the multiple regular job postings included in the regular job posting information 234 into job groups based on job type, such as a job group where job type is A, a job group where job type is B, and so on.

[0062] Through the above process, by classifying regular job postings into each job group according to their job type, it becomes possible to consolidate the job descriptions for pending positions, and as a result, it becomes possible to set more appropriate recruitment details for pending positions.

[0063] Furthermore, the configuration module 240 may also include setting the number of available positions for standby jobs based on the cancellation rate of each regular job included in the recruitment group. The cancellation rate may be calculated based on past statistical data. For example, suppose store A recruited 25 regular positions in a month, received 20 applications, but 2 canceled before the start of work. In this case, the cancellation rate would be 2 / 20 = 10%. For example, if the average cancellation rate B(A>B)% for each regular job included in recruitment group B is lower than the average cancellation rate A% for each regular job included in recruitment group A, the configuration module 240 may set the number of available positions for standby jobs in group A to be higher than that in group B.

[0064] Through the above process, by setting the number of positions to be filled in the waiting list based on the cancellation rate of regular job postings, it becomes possible to optimize the number of positions to be filled in the waiting list based on objective data, and as a result, it becomes possible to set the content of the waiting list job postings more appropriately.

[0065] Furthermore, the cancellation rate may be set based on at least one of the following: the working hours for each regular job, the day of the week for the workday, and the weather forecast for the workday. For example, the cancellation rate may be set separately for each working hours, separately for each day of the week, or separately for each weather. It may also be set separately for each working hour and day of the week, separately for each working hour and weather, separately for each day of the week and weather, or separately for each working hour, day of the week and weather.

[0066] For example, it is expected that the cancellation rate will be higher on rainy days than on sunny days, and that night shifts will have a higher cancellation rate than daytime shifts. By processing the above, the cancellation rate of regular job postings will be reflected more accurately, making it possible to set the number of people to recruit for standby positions based on a more accurate cancellation rate, and as a result, it will be possible to set the recruitment details for standby positions more appropriately.

[0067] Furthermore, the configuration module 240 may update the number of available positions for pending jobs whenever a predetermined update timing arrives. For example, the predetermined update timing may be set to every day or every week, but is not limited to these.

[0068] Since the number of regular job openings and the number of positions available are constantly changing, it is likely that the appropriate number of positions available for standby positions will also change accordingly. By updating the recruitment details for standby positions at predetermined intervals through the above process, it becomes possible to set standby positions based on new job information, and as a result, it becomes possible to set the recruitment details for standby positions more appropriately.

[0069] Furthermore, the configuration module 240 may set the number of people to be recruited for standby positions for each time slot based on the start time and / or working hours of each regular job included in the job group. The time slots may be divided into multiple periods, such as early morning (e.g., 3 a.m. to 7 a.m.), midday (e.g., 7 a.m. to 12 p.m.), afternoon (e.g., 12 p.m. to 8 p.m.), and late night (e.g., 8 p.m. to 3 a.m.). It is assumed that the start time and / or working hours of each regular job included in the job group will differ for each regular job. Therefore, even within the same job group, the configuration module 240 may set the number of people to be recruited for standby positions for each time slot, such as A people in the early morning and B people in the midday.

[0070] By implementing the above process, it becomes possible to reduce waiting times for on-call jobs by setting the recruitment details for each time slot, and as a result, it becomes possible to set the recruitment details for on-call jobs more appropriately.

[0071] The output module 241 in Figure 3 outputs information about available positions, including the number of positions available or the area where the positions are located, to the user terminal. For example, when a worker requests to view job information, the output module 241 outputs the available job information to the worker's information processing device 10B. The job information output to the information processing device 10B may include both regular job information and available job information.

[0072] Through the above process, workers will be able to access information on available positions. Furthermore, workers may be allowed to access information on available positions in addition to information on regular positions.

[0073] The output module 241 may output pending job information to the user terminal if the matching rate of workers applying for each regular job included in the job group is above a predetermined threshold. Here, the matching rate represents the ratio of applicants to the number of positions available for a regular job. For example, if store A has 25 regular job openings in a month and receives 20 applications, the matching rate will be 20 / 25 = 80%.

[0074] Basically, standby job postings are supplementary job postings used when vacancies arise in regular positions. Therefore, if the matching rate for standby job postings is low, it may be better to continue recruiting for regular positions and prioritize finding regular workers rather than using standby postings. Thus, by following the above procedures, it is possible to prioritize recruiting for regular positions over standby job postings.

[0075] The selection module 242 selects a worker from among the one or more workers who applied for the standby job to be assigned to the first regular job if a cancellation occurs in the first regular job included in the job group. For example, if there are multiple workers who applied for the standby job, the selection module 242 may select any one of them.

[0076] Through the above process, when a vacancy arises in a regular job, it becomes possible to apply for a standby position and quickly assign a standby worker to that position.

[0077] The selection module 242 may select workers to be dispatched to the first regular job based on at least one of the following: the past work experience of one or more workers, the travel time to the company of the first regular job that was canceled, and the waiting time until the cancellation of the first regular job occurred. If there are multiple workers who have applied for a waiting job, for example, workers who are closer to the work location are more likely to be able to start work immediately. Alternatively, workers who have previous work experience at the same or similar work location are more likely to be able to start work smoothly. Alternatively, it may be possible to prioritize selecting workers with longer waiting times over workers with shorter waiting times.

[0078] Through the above process, if a vacancy arises in a regular job, it becomes possible to apply for a standby position and assign a more suitable worker from among the standby workers.

[0079] Each of the elements described above may be stored in one or more of the aforementioned storage devices. Each of the modules described above corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) described above do not need to be implemented as separate software programs, procedures, or modules, and therefore various subsets of these modules can be combined or reconfigured in various embodiments. In one embodiment, memory 230 may store a subset of the modules and data structures described above. Furthermore, memory 230 may store additional modules and data structures not described above.

[0080] One or more processing units (CPUs) 210 may read and execute each module from the memory 230 as needed. For example, one or more processing units (CPUs) 210 may constitute a communication unit by executing a network communication module 232 stored in the memory 230. Alternatively, one or more processing units (CPUs) 210 may constitute a service control unit, a classification unit, a configuration unit, an output unit, and a selection unit by executing a service control module 238, a classification module 239, a setting module 240, an output module 241, and a selection module 242, respectively, all stored in the memory 230. Furthermore, the processing of each of the service control module 238, the classification module 239, the setting module 240, the output module 241, and the selection module 242 may be executed by one or more processing units (CPUs) 210.

[0081] Figure 3 shows a “server,” but it is intended to illustrate the various features that may exist in a set of servers rather than to provide a structural overview of the embodiments described herein. In practice, as will be apparent to those skilled in the art, the items shown separately may be combined, and some items may be configured separately. For example, the items shown separately in Figure 3 may be implemented on a single server, and a single item may be implemented by one or more servers.

[0082] The database 30 may have a configuration similar to that shown in Figure 3. At least one of the user information 233, regular job information 234, waiting job information 235, cancellation rate information 236, and matching rate information 237 shown in Figure 3 may be stored in the storage unit of the database 30.

[0083] <Example of data structure> Figure 4 shows an example of user information 233 according to the embodiment. User information 233 manages information about each member user created by a user using the job recruitment service. "User ID" includes user identification information (User ID: Identifier) ​​that the server 20 uses to uniquely identify the user. "User information" is associated with the User ID. "Applied Jobs" includes job IDs (regular job IDs or waiting job IDs) of jobs that the user has applied for in the past.

[0084] "User information" includes personal information of the user (e.g., worker), such as "name," "address," "telephone number," and "email address." The user ID may also be included as part of the user information. Furthermore, user information may also include email address and password.

[0085] Figure 5 shows an example of regular job information according to the embodiment. The "Regular Job ID" includes identification information for the regular job information. The regular job information includes various pieces of information associated with the Regular Job ID, such as "Working days," "Working hours," "Job type," "Job description," "Number of openings," "Employer," "Work location," "Hourly wage," and "Cancellation rate." In the example shown in Figure 5, "Hourly wage" is used, but "Salary" calculated as hourly wage × working hours may also be used.

[0086] "Working days" includes the days (or periods) on which the employer needs workers. "Working hours" includes the start and end times of the worker's work on working days. "Job type: Job description" includes the job type and job description. Examples of job types include delivery, customer service, warehouse (sorting), cooking, etc. "Number of openings" includes the number of openings for the regular job posting. "Employer" includes the name of the employer who has set up the job posting and is seeking workers. "Work location" includes at least one of the following: store name, location, place name, facility name, etc., where the worker will be working. "Work location ID" includes an ID that uniquely identifies the work location. Note that the same work location (store, warehouse, etc.) will be assigned the same work location ID. "Hourly wage" includes the hourly wage for the job posting. "Cancellation rate" includes the cancellation rate for regular job postings. Note that the cancellation rate may be automatically calculated from past statistical data, or it may be set by the employer when registering the regular job posting.

[0087] Figure 6 shows an example of standby job information according to the embodiment. The "Standby Job ID" includes identification information for the standby job information. The "Regular Job ID" includes identification information for the regular job information associated with the standby job information. The standby job information includes various pieces of information such as "Number of standby positions available," "Job type," "Area," "Standby date and time," and "Standby hourly wage," associated with the standby job ID. In the example shown in Figure 6, "Standby hourly wage" is used, but "Standby pay," which is the standby hourly wage multiplied by the standby time, may also be used.

[0088] The "Regular Job ID" includes regular job postings associated with the standby job posting, i.e., regular job postings classified into the same job group in classification module 239. The "Number of Standby Workers" includes the number of standby workers set in setting module 240. The "Area" includes the area of ​​the standby job posting. The "Standby Date and Time" includes the standby start date and time, and the standby end date and time for the standby worker to be on standby. The standby start time may be set according to the start times of one or more regular job postings associated with the standby job posting, for example, a predetermined time before the earliest start time of each regular job posting (e.g., one hour before). The standby end time may be set according to the start times of one or more regular job postings associated with the standby job posting, or a predetermined time after the latest start time of one or more regular job postings associated with the standby job posting (e.g., one hour after). The "Standby Hourly Wage" includes the standby worker's hourly wage. "Waiting time pay" may be calculated, for example, the same as the hourly wage for regular employment, or by subtracting or adding an offset value to the hourly wage for regular employment.

[0089] Figure 7 shows an example of cancellation rate information according to the embodiment. "Time zone" includes the time zone corresponding to the cancellation rate. For example, the time zone may be divided into four parts: 0-6am, 6am-12am, 12am-6pm, and 6pm-24am. However, it is not limited to these, and may also be divided into early morning (e.g., 3am-7am), midday (e.g., 7am-12pm), afternoon (e.g., 12pm-8pm), and late night (e.g., 8pm-3am). Furthermore, it is not limited to these, and the time zone may be divided into different time lengths. "Job type" may be divided into categories such as cooking, warehouse work, delivery, customer service, etc. The cancellation rate may be determined based on, for example, past statistical data.

[0090] Figure 8 shows an example of matching rate information according to the embodiment. "Workplace ID" includes an ID that uniquely identifies the workplace. Note that the Workplace ID is the same as the Workplace ID described in Figure 5. "Regular Job Matching Rate" includes the matching rate for the workplace corresponding to the Workplace ID. The matching rate may be calculated based on, for example, past statistical data for the workplace (e.g., data showing how many applicants there were for how many positions were advertised).

[0091] <Operation Description> Next, the operation of the information processing system 1 according to the embodiment will be described. Figure 9 is a sequence diagram showing an example of processing related to waiting job postings according to the embodiment. In the example shown in Figure 9, the information processing device 10A is a device used by the business operator, and the information processing devices 10B and 10C are devices used by waiting workers.

[0092] In step S10, the information processing device 10A of the business operator sends various setting information for the regular job posting to the server 20 in response to the business operator's operation on the job posting screen. The setting information for the regular job posting includes working days, working hours, work location, number of positions available, hourly wage, etc. (see, for example, Figure 5). At this time, the server 20 may set an expected cancellation rate based on the cancellation rate of similar job postings in the past, based on the set job type, working hours, etc.

[0093] In step S11, the configuration module 240 of the server 20 obtains configuration information about regular job postings from the information processing device 10A and configures the regular job postings 234 based on this configuration information.

[0094] In step S12, the classification module 239 and configuration module 240 of the server 20 generate waiting job information 235 based on the regular job information 234. Details of the processing procedure in step S12 will be described later with reference to Figure 14.

[0095] In step S13, the output module 241 of the server 20 obtains regular job postings and pending job postings to be made public to the information processing device 10B and the information processing device 10C based on a request to view job postings from the information processing device 10B or the information processing device 10C, from the regular job posting information 234 and the pending job posting information 235.

[0096] Furthermore, the output module 241 of server 20 may change the publication timing of standby job postings based on the application status of regular job postings, rather than publishing them immediately after generating them. For example, the output module 241 may publish standby job postings only when the matching rate (application rate) of each regular job posting associated with the standby job posting reaches a predetermined rate or higher. For example, if the predetermined rate is set to 90%, the output module 241 may publish the standby job postings when the matching rate of all or part of each regular job posting associated with the standby job posting reaches 90%. In addition, the output module 241 of server 20 may extract regular job postings from the job group that have a matching rate (application rate) of a predetermined rate or higher, and recalculate the number of people to be recruited for standby job postings based on the extracted regular job postings that have a matching rate of a predetermined rate or higher (i.e., regular job postings with low matching rates may be excluded from the standby job postings).

[0097] The timing for publishing idle job postings may be later than the publishing of regular job postings. Output module 241 may publish idle job postings for job group A, which includes regular job postings with many last-minute cancellations, at an earlier time than idle job postings for job group B, which includes regular job postings with fewer last-minute cancellations than job group A.

[0098] In step S14, the output module 241 of the server 20 outputs job information, including regular and pending job openings, to the screen of the information processing device 10B.

[0099] In step S15, the output module 241 of the server 20 outputs job information, including regular and pending job openings, to the screen of the information processing device 10C.

[0100] Figure 10 shows an example of a job listing screen according to the embodiment. Figure 10 shows an example where a list of regular job postings also includes idle job postings. The upper right of Figure 10 shows idle job postings, and the other postings are regular job postings. When an idle job posting is selected on the screen in Figure 10, the screen transitions to the screen showing the details of the idle job posting, as shown in Figure 11.

[0101] Figure 11 shows an example of a screen displaying details of a standby job according to the embodiment. In Figure 11, "Shibuya Ward, Tokyo" is displayed as the area for the standby job set in step S125 of Figure 14. It also shows that the standby date and time is 5 hours from 13:00 to 18:00 on June 20th, and the compensation is 1,100 yen per hour. The display "Number of openings: 2 / 5" indicates that there are 5 openings, and 2 people have already applied. Users can apply to be standby workers by clicking "Apply" displayed at the bottom of the screen in Figure 11.

[0102] Returning to Figure 9, in step S16, when a user applies for a waiting job, the information processing device 10B notifies the server 20 that the user has applied for a waiting job.

[0103] In step S20, if a vacancy occurs in a regular job posting, the information processing device 10A sends a vacancy notification to the server 20 based on the operator's actions. The vacancy notification includes the regular job posting ID and the number of people whose positions are vacant.

[0104] In step S21, the selection module 242 selects a standby worker to match (assign) to a regular job opening if a vacancy arises in that regular job. The selection method will be described later using Figure 15. Here, it is assumed that a standby worker from the information processing device 10B has been selected.

[0105] In step S22, the output module 241 of the server 20 outputs information to the information processing device 10B of the standby worker indicating that it has been matched with a regular job and should report to work. The information processing device 10B displays this information on the screen. Figure 12 shows an example of a vacancy notification screen according to the embodiment. Figure 12 is a screen displayed on the standby worker information processing device 10, which notifies the standby worker that they have been matched with a regular job opening that has become vacant. A standby worker who receives notification that a vacancy has become vacant must travel to the workplace and start work by the start time of the regular job opening, or by a predetermined time (for example, within 30 minutes or within 1 hour) after receiving the notification, whichever is later.

[0106] Returning to Figure 9, in step S23, the information processing device 10B requests detailed information about the matched regular job openings (i.e., regular job openings with vacancies) from the server 20.

[0107] In step S24, the server 20 outputs detailed information about the matched regular job to the information processing device 10B.

[0108] Figure 13 is a diagram showing an example of a screen displaying the details of a matched regular job according to the embodiment. Figure 13 displays the details of a regular job matched with a waiting worker. Note that, since waiting workers who are matched with a regular job must, in principle, start working, a cancel button does not need to be displayed on this screen.

[0109] Figure 14 is a flowchart showing an example of the processing procedure for generating waiting job information according to the embodiment. Using Figure 14, the details of the processing procedure in step S12 of Figure 9 will be explained.

[0110] In step S120, the classification module 239 of the server 20 refers to the regular job information 234 and obtains the specified conditions (work location and / or job type) for each regular job.

[0111] In step S121, the classification module 239 of the server 20 classifies one or more regular job postings included in the regular job posting information 234 into multiple job posting groups based on predetermined conditions. The classification module 239 may also set up job posting groups based on the work location of the regular job postings. For example, the classification module 239 may classify regular job postings by area where the work location is located, thereby classifying the job posting groups into job posting groups for each area. The area may be, for example, a prefecture, a city or town, or a predetermined mesh unit. For example, the classification module 239 may divide Japan into multiple meshes by dividing the map at regular intervals, and classify regular job postings located in the same mesh into the same job posting group, thereby classifying the job posting groups into job posting groups for each mesh. The mesh size may be equal intervals, or it may be predetermined based on the travel time of the main mode of transportation used in that area (e.g., train, bus, taxi, etc.).

[0112] The classification module 239 may also set up job groups based on the job type of the regular job posting. For example, the classification module 239 may classify regular job postings into job groups based on units such as cooking, warehouse work, delivery, and customer service. Alternatively, the classification module 239 may classify regular job postings into job groups based on units that group together multiple job types whose cancellation rates are within a predetermined range. For example, if the cancellation rates for warehouse work and delivery are within a predetermined range (e.g., similar), the classification module 239 may group regular warehouse work postings and regular delivery postings together into a single job group.

[0113] Furthermore, classification module 239 may set up job groups based on both the location and job type of regular job postings. For example, classification module 239 may classify job groups by municipality (or grid) based on the location of regular job postings, and then further classify regular job postings by units such as cooking, warehouse work, delivery, and customer service. For example, classification module 239 may set up job groups by units such as customer service in Shibuya Ward, Tokyo, and delivery in Shibuya Ward, Tokyo.

[0114] Regular job postings may include a flag indicating whether or not they are subject to the standby job posting program. This flag may be set by the employer. Classification module 239 may classify regular job postings that are subject to the standby job posting program according to this flag into one of the job posting groups, and may not classify regular job postings that are not subject to the standby job posting program according to this flag into any job posting group.

[0115] In step S122, the configuration module 240 obtains the number of applicants for each regular job by referring to the regular job information 234 of each regular job included in the job group.

[0116] In step S123, the configuration module 240 of the server 20 sets the number of people to be recruited for the standby recruitment based on the total number of people to be recruited for each regular job in each recruitment group. The configuration module 240 may also set the number of people to be recruited for the standby recruitment as a value obtained by multiplying the total number of people to be recruited for each regular job by a predetermined coefficient. The predetermined coefficient may be a fixed value set in advance (e.g., 10%) or the cancellation rate. For example, if the total number of people to be recruited for each regular job is 15 and the cancellation rate is 5%, then 15 × 0.05 = 0.75. In this case, the configuration module 240 may set the number of people to be recruited for the standby recruitment to 1.

[0117] The cancellation rate may also be the cancellation rate for regular job postings included in the job group. For example, the configuration module 240 may obtain the cancellation rate for regular job postings of a specific company included in the job group from the regular job posting information 234, and use the obtained cancellation rate as the cancellation rate for regular job postings included in the job group.

[0118] Alternatively, the overall cancellation rate for a recruitment group may be estimated based on the number of applicants and cancellation rates for each regular job within the recruitment group. For example, if a regular job with 20 applicants in the recruitment group has a cancellation rate of 10%, and a regular job with 5 applicants in the recruitment group has a cancellation rate of 5%, the overall cancellation rate for the recruitment group may be estimated as (20 people × 10% + 10 people × 5%) ÷ (20 people + 10 people) = 8.3%.

[0119] The configuration module 240 may also obtain the matching rate for each regular job within the job group by comparing the matching rate information 237 with the regular job information 234. For example, in the case of a job posting with regular job ID J001, since the job type is delivery, it can be seen that the cancellation rate for the time period from 12:00 to 18:00 is 3%.

[0120] Furthermore, the configuration module 240 may vary the cancellation rate based on at least one of the following factors for each regular job posting: the working hours, the day of the week, and the weather forecast for the working day. For example, the cancellation rate may be increased by 2% on rainy days, by 10% on snowy days, and by 4% during the busy holiday season around the New Year.

[0121] In step S124, the configuration module 240 obtains the work location for each regular job by referring to the regular job information 234 for each regular job included in the job group.

[0122] In step S125, the configuration module 240 sets the area for standby jobs to be assigned to the job group based on the work location of each regular job obtained in step S124. The configuration module 240 may set the area for standby jobs so that it includes all of the work locations of each regular job. For example, if the job groups were classified by municipality in the processing procedure of step S121, the work locations of each regular job included in one job group will be in the same municipality. In this case, the configuration module 240 may set that same municipality as the area for standby jobs. For example, if the work locations of all regular jobs included in one job group are "Shibuya-ku, Tokyo", the configuration module 240 may set Shibuya-ku, Tokyo as the area for standby jobs.

[0123] Server 20 calculates the number of recruits and sets the area for all recruitment groups by repeating the processing procedures from steps S122 to S125.

[0124] Figure 15 is a flowchart showing an example of a procedure for handling a vacancy according to the embodiment. The details of the procedure in step S21 of Figure 9 will be explained using Figure 15.

[0125] In step S200, the selection module 242 identifies the idle job openings associated with the regular job openings that have become vacant by referring to the idle job opening information 235.

[0126] In step S201, the selection module 242 identifies the waiting workers who have applied for the identified waiting jobs by referring to the "applied jobs" in the user information 233.

[0127] In step S202, the selection module 242 selects a standby worker from the identified standby workers to match (assign) to the regular job opening that has become vacant. For example, the selection module 242 may select a standby worker whose address is closest to the location of the regular job opening. Alternatively, the selection module 242 may select a standby worker who has work experience in the same job category as the regular job opening. Alternatively, the selection module 242 may select a standby worker whose travel time from their address to the location of the regular job opening is the shortest. Alternatively, the selection module 242 may select a standby worker who has previously worked at the location of the regular job opening. For example, if the regular job opening that has become vacant is at convenience store X, store AA, the selection module 242 may select a standby worker who has previously worked at convenience store X, store AA.

[0128] ≪Additional information≫ The compensation set for standby jobs may be paid by multiplying the hourly wage by the length of time the standby worker is on standby. For example, if a standby job is from 9 am to 12 pm and the hourly wage is 1100 yen, 3300 yen will be paid if there are no vacancies. If a vacancy occurs, the worker will be paid both the standby job wage and the regular job wage. The hourly wage for standby jobs may also vary depending on the day of the week, weather, season, time of day, and / or job type.

[0129] Furthermore, the disclosed technology is not limited to the embodiments described above, and can be implemented in various other forms without departing from the gist of the disclosed technology. For this reason, the above embodiments are merely illustrative in all respects and should not be interpreted restrictively. For example, the order of each processing step described above can be arbitrarily changed or executed in parallel, as long as there is no inconsistency in the processing content.

[0130] The programs of embodiments of this disclosure may be provided stored on a computer-readable storage medium. The storage medium is a “tangible medium that is not temporary” on which the program can be stored. The program includes, but is not limited to, software programs and computer programs. [Explanation of Symbols]

[0131] 1. Information Processing System 10, 10A, 10B Information Processing Devices 20. Information Processing Equipment (Server) 110, 210 Processing Units (CPUs) 120, 220 Network Communication Interfaces 130, 230 memory 131, 231 Operating Systems 132, 232 Network Communication Modules 133 App Data 134 Service Processing Module 135 Acquisition Module 136 Output Modules 137 Processing Modules 138 Display Control Module 150 User Interfaces 170, 270 Communications Bus 233 User Information 234 Regular Job Postings 235 Job postings for those on standby 236 Cancellation Rate Information 237 Matching Rate Information 238 Service Control Module 239 Classification Modules 240 Configuration Modules 241 Output Module 242 Selection Modules

Claims

1. Information processing device, Classify each regular job posting into a job posting group based on predetermined conditions. Based on the number of openings for each regular job included in the classified job group, set the number of available positions for each regular job to be allocated to the job group, or, based on the work location of each regular job, set the area for the available positions to be allocated to the job group. An information processing method that performs the following.

2. The aforementioned predetermined conditions are: Including the conditions relating to the work location of each of the aforementioned regular job postings, The information processing method according to claim 1.

3. The aforementioned predetermined conditions are: Including the conditions for each of the aforementioned regular job postings, The information processing method according to claim 1.

4. The above setting means, This includes setting the number of available positions for the pending positions based on the cancellation rate of each regular job included in the aforementioned job group, The information processing method according to claim 1.

5. The aforementioned cancellation rate is, The working hours, working days, and weather forecast for each of the aforementioned regular job postings are determined based on at least one of these factors. The information processing method according to claim 4.

6. The above setting means, Each time a predetermined time for updating arrives, the number of applicants for the aforementioned pending positions will be updated, The information processing method according to claim 1.

7. The above setting means, This includes setting the number of available positions for each time slot based on the start time and / or working hours of each regular position included in the aforementioned job group, The information processing method according to claim 1.

8. The aforementioned information processing device The system outputs information relating to the aforementioned waiting job postings, including the number of applicants for the waiting job postings or the area where the waiting job postings are located, to the user's information processing device. The information processing method according to claim 1.

9. The output mentioned above is, If the matching rate of users applying for each of the regular job postings included in the job posting group is above a predetermined threshold, the pending job posting information is output to the user's information processing device. The information processing method according to claim 8.

10. The aforementioned information processing device If a cancellation occurs in the first regular job posting included in the aforementioned job posting group, select a user from among the one or more users who applied for the pending job posting to be dispatched to the first regular job posting. The information processing method according to claim 1, which performs the following.

11. The aforementioned selection means, This includes selecting a user to be dispatched to the first regular job based on at least one of the following: the past work experience of one or more users, the travel time to the company of the first regular job, and the waiting time until the cancellation of the first regular job occurs. The information processing method according to claim 10.

12. A classification unit that classifies each regular job posting into each job posting group based on predetermined conditions, A setting unit that sets the number of available positions for each regular job that is included in the classified job group, to be allocated to the job group, or sets the area for the available positions to be allocated to the job group, based on the work location of each regular job. An information processing device having

13. On the computer, Classify each regular job posting into a job posting group based on predetermined conditions. Based on the number of openings for each regular job included in the classified job group, set the number of available positions for each regular job to be allocated to the job group, or set the area for the available positions to be allocated to the job group based on the work location of each regular job. A program to execute.

Images