System and method for managing work status of worker

Abstract

To support appropriate management of work situations of workers.SOLUTION: A recruitment matching service providing system 1 according to an embodiment of the present invention includes a server 10, a store terminal 20, and a worker terminal 30, and the server 10 provides a recruitment matching service for matching an employer and a worker in recruitment. In the system 1, when the worker terminal 30 of the worker acquires the tag storage information stored in the electronic tag 400 installed in the store, the validity of the electronic tag 400 is determined on the basis of the tag-side determination information included in the tag storage information, and when it is determined that the electronic tag 400 is valid, the work status of the worker in the store is updated, and further, the tag-side determination information stored in the electronic tag 400 is updated in response to the acquisition of the tag storage information, and thus, for example, an illegal operation of attendance and absence by a malicious worker or the like is suppressed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for managing the working status of workers. [Background technology]

[0002] Hitherto, there have been provided employment matching services that match workers with employers (see, for example, Patent Document 1 below). Typically, such services match workers with employers, and then manage the working status of the workers working at stores owned by the employer. For example, a two-dimensional code embedded with information that identifies the store is posted at the store, and when the worker clocks in and out, the two-dimensional code is read by a device such as a smartphone operated by the worker, thereby recognizing the worker's clock in and out at the store. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6474089 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with the above-mentioned conventional services, there is a risk of fraudulent activity that exploits the information in the two-dimensional code displayed in the store. For example, a malicious worker could obtain an image of the two-dimensional code, apply for a job at the store corresponding to that two-dimensional code, and after matching, use the obtained image to manipulate the worker's clock-in and clock-out even though the worker is not actually working there. As such, there is room for improvement in the management of worker working status at stores.

[0005] One of the objects of the embodiments of the present invention is to support appropriate management of the working conditions of workers. Other objects of the embodiments of the present invention will become apparent by referring to the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention comprises a worker terminal operated by a worker and a server, and is a system for managing the working status of the worker, wherein the worker terminal executes the following steps: acquiring tag stored information stored in an electronic tag installed in a store, the tag stored information including first determination information for determining the validity of the electronic tag; the worker terminal transmitting the tag stored information to the server; the worker terminal updating the first determination information stored in the electronic tag; the server determining the validity of the electronic tag based at least on the first determination information; and if the electronic tag is determined to be valid, the server updating the working status of the worker at the store.

[0007] A method according to one embodiment of the present invention is a method for managing the work status of a worker, which is executed by a worker terminal operated by a worker and a server, and includes the steps of: the worker terminal acquiring tag stored information stored in an electronic tag installed in a store, the tag stored information including first determination information for determining the validity of the electronic tag; the worker terminal transmitting the tag stored information to the server; the worker terminal updating the first determination information stored in the electronic tag; the server determining the validity of the electronic tag based at least on the first determination information; and if the electronic tag is determined to be valid, the server updating the work status of the worker in the store. [Effects of the Invention]

[0008] Various embodiments of the present invention support proper management of worker work situations. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating the configuration of a job matching service providing system 1 according to one embodiment of the present invention. [Figure 2] FIG. 15 is a diagram illustrating an example of information managed by an employer information table 1511. [Figure 3] FIG. 15 is a diagram illustrating an example of information managed by a store information table 1512. [Figure 4] FIG. 15 is a diagram illustrating an example of information managed by an NFC tag information table 1513. [Figure 5] FIG. 15 is a diagram illustrating information managed by a token management table 1514. [Figure 6] FIG. 15 is a diagram illustrating an example of information managed by a worker information table 1515. [Figure 7] FIG. 15 is a diagram illustrating an example of information managed by a job vacancy management table 1516. [Figure 8] FIG. 15 is a diagram illustrating an example of information managed by a work status management table 1517. [Figure 9] FIG. 5 is a diagram illustrating a job registration screen 50. [Figure 10] FIG. 6 is a diagram illustrating a store job listing screen 60. [Figure 11] FIG. 7 is a diagram illustrating an example of a job listing screen 70 for workers. [Figure 12] FIG. 10 is a diagram illustrating an example of display content in an individual display area 761. [Figure 13] FIG. 10 is a diagram illustrating a job details screen 80. [Figure 14] 4 is a sequence diagram illustrating processing executed by the worker terminal 30 and the server 10. FIG. [Figure 15] FIG. 10 is a diagram illustrating a tag reading guide screen 90. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, the same reference numerals may be used to designate the same or similar components.

[0011] FIG. 1 is a diagram illustrating the overall configuration of a job matching service providing system 1 according to one embodiment of the present invention. As illustrated, the system 1 includes a server 10, a store terminal 20, and a worker terminal 30 that are communicatively connected to the server 10 via a communication network NW such as the Internet. While FIG. 1 illustrates only one store terminal 20 and one worker terminal 30, the system 1 includes multiple store terminals 20 and multiple worker terminals 30. The server 10 provides a job matching service for matching employers and workers in job postings to store personnel who operate the store terminal 20 and workers (laborers) who operate the worker terminal 30. The job matching service has the function of managing the working status of workers at stores owned by employers.

[0012] First, we will explain the hardware configuration of the server 10. The server 10 is configured as a general computer, and as shown in Fig. 1, includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (information storage device) 15, and these components are electrically connected via a bus or the like (not shown).

[0013] The computer processor 11 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 15 or the like into a main memory 12 and executes various instructions included in the programs. The main memory 12 is configured, for example, by a DRAM or the like.

[0014] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.

[0015] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to enable wired or wireless communication via a communication network NW or the like.

[0016] The storage 15 is configured, for example, by a magnetic disk or flash memory. The storage 15 stores various programs including an operating system, various data, and the like. For example, as shown in FIG. 1, the storage 15 has various tables 151 that manage various information for providing the job matching service. The storage 15 also stores, for example, a server-side program 40. The program 40 is a program that causes the server 10 to function as a device for providing the job matching service. At least a portion of the server-side program 40 can be configured to be executed on the store terminal 20 or the worker terminal 30 via a store terminal-side program 42 or a worker terminal-side program 44, which will be described later.

[0017] In this embodiment, the server 10 may be configured using a plurality of computers each having the above-described hardware configuration. For example, the server 10 may be configured by a plurality of server devices.

[0018] The server 10 configured in this way can be configured to function as a web server and an application server, and executes various processes in response to requests from the store terminal 20 or the worker terminal 30, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the store terminal 20 or the worker terminal 30. The store terminal 20 or the worker terminal 30 outputs a web page or other screen based on the received data.

[0019] Next, we will explain the hardware configuration of the store terminal 20. The store terminal 20 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 21, a main memory 22, an input / output I / F 23, a communication I / F 24, and a storage (storage device) 25, and these components are electrically connected via a bus or the like (not shown).

[0020] The computer processor 21 is configured as a CPU, a GPU, or the like, and loads various programs stored in the storage 25 or the like into the main memory 22 and executes various instructions included in the programs. The main memory 22 is configured, for example, by a DRAM or the like.

[0021] The input / output I / F 23 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 23 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), audio input devices such as a microphone, and image input devices such as a camera. The input / output I / F 23 also includes an image output device such as a display, and an audio output device such as a speaker.

[0022] The communication I / F 24 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to realize wired or wireless communication via a communication network NW or the like.

[0023] The storage 25 is configured, for example, by a magnetic disk or flash memory. The storage 25 stores various programs including an operating system, various data, and the like. The programs stored in the storage 25 can be downloaded and installed from an application market or the like. The storage 25 also stores the above-mentioned store terminal-side program 42. The program 42 can be configured as a web browser or other application (for example, a store application for a job matching service), and can be configured to execute at least a part of the server-side program 40, as described above.

[0024] In this embodiment, the store terminal 20 may be configured as a smartphone, a tablet terminal, a personal computer, or the like.

[0025] A user (store staff member) operating a store terminal 20 configured in this manner can use the store functions of the job matching service provided by the server 10 by communicating with the server 10 via a store terminal side program 42 installed in storage 25 or the like.

[0026] Next, the hardware configuration of the worker terminal 30 will be described. Like the above-described store terminal 20, the worker terminal 30 is configured as a general computer, and as shown in Fig. 1, includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, with each of these components being electrically connected via a bus or the like (not shown). In this embodiment, the communication I / F 34 is configured to realize wireless communication with an electronic tag 400 installed in the store where the worker works.

[0027] The storage 35 stores the worker terminal-side program 44. The program 44 is configured as a web browser or other application (for example, a worker application for a job matching service), and as described above, can be configured to execute at least a part of the server-side program 40. In this embodiment, the worker terminal 30 can be configured as a smartphone, a tablet terminal, a personal computer, or the like.

[0028] A user (worker) operating a worker terminal 30 configured in this manner can use the worker functions of the job matching service provided by the server 10 by communicating with the server 10 via a worker terminal side program 44 installed in storage 35 or the like.

[0029] Next, the functions of the job matching service providing system 1 configured as described above will be described. As shown in FIG. 1, the computer processor 11 of the server 10 is configured to function as a server-side control unit 112 by executing instructions included in a program (e.g., at least a part of the server-side program 40) loaded into the main memory 12. The server-side control unit 112 is configured to execute various processes related to the server-side control of each function of the job matching service. The functions of the job matching service include, for example, management functions (e.g., login processing (user authentication) and management of various master data), an employer-worker matching function, and a work status management function. For example, the server-side control unit 112 transmits screen data and control data of various screens for controlling these functions to the store terminal 20 or worker terminal 30, executes various processes in response to operation inputs by an operator via the screens displayed on the store terminal 20 or worker terminal 30, and transmits screen data and control data corresponding to the results of the processes to the store terminal 20 or worker terminal 30.

[0030] 1, the computer processor 21 of the store terminal 20 is configured to function as a store terminal control unit 212 by executing instructions included in a program (for example, at least a part of the store terminal program 42) loaded into the main memory 22. The store terminal control unit 212 is configured to execute various processes related to the control of the store terminal 20 side of each function of the job matching service.

[0031] 1, the computer processor 31 of the worker terminal 30 is configured to function as a worker terminal control unit 312 by executing instructions contained in a program (for example, at least a part of the worker terminal program 44) loaded into the main memory 32. The worker terminal control unit 312 is configured to execute various processes related to the control of the worker terminal 30 side of each function of the job matching service.

[0032] In this embodiment, the worker terminal control unit 312 of the worker terminal 30 is configured to acquire tag storage information stored in an electronic tag 400 installed in a store when managing work status. The tag storage information includes tag determination information for determining the validity of the corresponding electronic tag 400. The electronic tag 400 is also called an IC tag, RF tag, or wireless tag, and is a tag that can read and write information (data) contactlessly using radio waves. Such contactless reading and writing of information is achieved using RFID technology, for example.

[0033] The worker terminal control unit 312 is also configured to transmit the tag storage information acquired from the electronic tag 400 to the server 10, and to update the tag-side determination information stored in the electronic tag 400. The updated value of the tag-side determination information is provided by the server 10, for example.

[0034] Furthermore, the server-side control unit 112 of the server 10 is configured to determine the validity of the electronic tag 400 based at least on the tag-side determination information included in the tag storage information received from the worker terminal 30, and if the electronic tag 400 is determined to be valid, to update the work status of the corresponding worker (the worker who operates the worker terminal 30) in the corresponding store (the store where the electronic tag 400 is installed). The work status of the worker is managed, for example, in a specific table included in the various tables 151 that the storage 15 has.

[0035] In this way, in the job matching service providing system 1 of this embodiment, when a worker's worker terminal 30 acquires tag storage information stored in an electronic tag 400 installed in a store, the validity of the electronic tag 400 is determined based on the tag side determination information included in the tag storage information, and if the electronic tag 400 is determined to be valid, the worker's work status at the store is updated, and further, the tag side determination information stored in the electronic tag 400 is updated in response to acquisition of the tag storage information. Therefore, compared to using a two-dimensional code or the like with information embedded to identify the store, for example, fraudulent manipulation of clock-in / clock-out records by malicious workers is suppressed. In other words, the system 1 supports appropriate management of workers' work status.

[0036] In this embodiment, the tag storage information includes electronic tag identification information capable of identifying the corresponding electronic tag 400, and each of the multiple electronic tags 400 may be stored in association with server-side determination information based on the tag-side determination information stored in the corresponding electronic tag 400 in the storage 15 (e.g., a specific table included in the various tables 151). In this case, the server-side control unit 112 of the server 10 may acquire, from the storage 15, server-side determination information associated with the electronic tag 400 identified by the electronic tag identification information included in the tag storage information received from the worker terminal 30, and determine that the electronic tag 400 is valid if the value of the server-side determination information matches the value of the server-side determination information based on the value of the tag-side determination information included in the tag storage information. Furthermore, the server-side determination information stored in the storage 15 may be updated in accordance with the update of the tag-side determination information by the worker terminal control unit 312. The server-side determination information may be set as the tag-side determination information as is. This configuration makes it possible to determine the validity of the electronic tag 400 based on the tag-side determination information and the server-side determination information.

[0037] In this embodiment, the server-side control unit 112 may be configured to update the work status of a worker at a store to include at least one of a first status before coming to work, a second status during work, and a third status after leaving work. For example, when a worker whose work status at a specific store is the first status acquires tag storage information stored in an electronic tag 400 located at the specific store via the worker terminal 30, if the electronic tag 400 is determined to be valid, the worker's work status is updated to a second status of "working." The second status may be a status in which the date and time of arrival at work is registered. Similarly, for example, when a worker whose work status at a specific store is the second status acquires tag storage information stored in an electronic tag 400 located at the specific store via the worker terminal 30, if the electronic tag 400 is determined to be valid, the worker's work status is updated to a third status of "after leaving work." The third status may be a status in which the date and time of departure from work is registered. This configuration enables updating of work status in response to the worker terminal 30 acquiring tag storage information stored in the electronic tag 400.

[0038] Furthermore, when updating the work status of a corresponding worker (a worker who operates the worker terminal 30) at a corresponding store (a store where the electronic tag 400 is installed), the server-side control unit 112 can be configured to perform a predetermined error process if the work schedule of the worker at the store is not registered. This configuration makes it possible to deal with the case where the work schedule is not registered.

[0039] In this embodiment, if the update of the tag-side determination information stored in the electronic tag 400 fails, the server-side control unit 112 can be configured to transmit update failure information indicating the failure to update the tag-side determination information to the server 10. In this case, upon receiving the update failure information, the server 10 can be configured to set the corresponding electronic tag 400 as an electronic tag that does not require validity determination. Electronic tags that do not require validity determination are not subject to validity determination based on the tag-side determination information. For example, if the electronic tag 400 is set as an electronic tag that does not require validity determination, the server-side control unit 112 determines that the electronic tag 400 is valid regardless of the tag-side determination information. This configuration makes it possible to continue updating the work status using the electronic tag 400 even if the update of the tag-side determination information stored in the electronic tag 400 fails.

[0040] In this embodiment, the tag-side determination information (and the associated server-side determination information) may be updated when a predetermined condition is met, but not when the predetermined condition is not met. The predetermined condition may be a condition for changing the update frequency of the tag-side determination information. This configuration prevents the determination information from being updated unconditionally.

[0041] The predetermined condition for updating the determination information can be configured to be satisfied based on, for example, the amount of time that has elapsed since the last update of the tag-side determination information. In this case, for example, the tag storage information stored in the electronic tag 400 may include the last update of the tag-side determination information. For example, the tag-side determination information is updated when the amount of time that has elapsed since the last update is equal to or greater than a threshold, but is not updated when the amount of time that has elapsed since the last update is less than the threshold. This configuration makes it possible to control whether or not to update the determination information based on the amount of time that has elapsed since the last update.

[0042] The predetermined condition may also be satisfied based on the worker's working status. For example, the predetermined condition is satisfied when the worker's working status is a first status before coming to work, but is not satisfied when the worker's working status is not the first status (for example, a second status while working). This configuration makes it possible to control whether or not to update the determination information based on the worker's working status.

[0043] The predetermined condition may also be changed based on the number of updates (cumulative value) of the determination information in the corresponding electronic tag 400. For example, the predetermined condition is changed so that the more updates the tag-side determination information has, the lower the update frequency. For example, the predetermined condition is updated when the time elapsed since the last update date and time is equal to or greater than a first threshold while the number of updates of the tag-side determination information is less than a predetermined value, and when the number of updates reaches or exceeds the predetermined value, the predetermined condition is updated when the time elapsed since the last update date and time is equal to or greater than a second threshold that is greater than the first threshold. This configuration makes it possible to control the update timing of the determination information based on the number of updates of the tag-side determination information.

[0044] The predetermined conditions may be set for each store, which makes it possible to control the timing of updating the determination information for each store.

[0045] The predetermined conditions may also be changed based on the values ​​of parameters associated with the store (e.g., region, industry, business scale, etc.). For example, the update frequency of the tag-side determination information changes based on the values ​​of the parameters. This configuration makes it possible to control the update timing of the determination information, etc., based on the values ​​of the parameters associated with the store.

[0046] Next, a specific example of one aspect of the server 10 of this embodiment having such functions will be described. First, in this specific example, information managed by each table included in the various tables 151 will be described.

[0047] 2 illustrates information managed by employer information table 1511 in this example. In this example, employer information table 1511 manages information about employers who hire workers in the job matching service, and as shown in the figure, manages information such as "employer name" in association with an "employer ID" that identifies an individual employer. Employers include, for example, chain companies and franchisee companies.

[0048] 3 illustrates information managed by store information table 1512 in this example. Store information table 1512 in this example manages information related to stores owned by employers, and as shown in the figure, manages information such as "basic information" including store name, address, and contact information, and an "employer ID" that identifies the corresponding employer, in association with a "store ID" that identifies an individual store. In this example, each employer owns one or more stores.

[0049] 4 illustrates information managed by NFC tag information table 1513 in this example. NFC tag information table 1513 in this example manages information related to NFC tags (electronic tags) 400 installed in each store, and as shown in the figure, manages information such as a "store ID" that identifies the store where the tag is installed, and an "allocated token" (server-side determination information) that is a token assigned to this NFC tag 400, in association with a "tag ID" that identifies each individual NFC tag 400. The token, which will be described in detail later, is information for determining the validity of the NFC tag 400.

[0050] 5 illustrates information managed by the token management table 1514 in this example. The token management table 1514 in this example manages information related to the above-mentioned tokens, and as shown in the figure, manages information such as an "assigned flag" that indicates that the corresponding token has been assigned to a worker as a token for renewal, in association with each individual "token." In this example, a token is a unique numerical value such as a UUID, and multiple tokens that have been generated in advance are managed in the token management table 1514.

[0051] 6 illustrates information managed by worker information table 1515 in this example. Worker information table 1515 in this example manages information about users as workers in the job matching service, and as shown in the figure, manages information such as "basic information" including name, date of birth, address, and contact information in association with a "worker ID" that identifies an individual worker, "work performance information" that is information about work performance at each store in the job matching service, and an "update token" assigned to this worker. The update token, which will be described in more detail later, is used to update the token (tag-side determination information) stored in NFC tag 400 installed in the store when the corresponding worker clocks in and out.

[0052] 7 illustrates information managed by the job vacancy management table 1516 in this example. The job vacancy management table 1516 in this example manages job vacancy information from stores, and as shown in the figure, manages information such as a "store ID" that identifies the corresponding store, "job vacancy title," "description," "work date," "work start time," "work end time," "job posting date and time," "job application deadline date and time," "number of applicants," "hourly wage," and a "job vacancy status type" that indicates the status of the job vacancy, in association with a "job vacancy ID" that identifies an individual job vacancy. In this example, the job vacancy status type is set to a value corresponding to either "recruiting," "working," or "work completed."

[0053] 8 illustrates information managed by the work status management table 1517 in this example. The work status management table 1517 in this example manages the work status of workers for jobs matched via a job matching service, and as shown in the figure, manages information such as the "start date and time" which is the worker's actual start date and time of work, the "leave date and time" which is the worker's actual leave date and time, the "store rating" which is the worker's rating of the store, and the "worker rating" which is the worker's rating of the store, in association with a combination of a "job ID" which identifies an individual job and a "worker ID" which identifies the worker who applied for and was matched with this job, etc.

[0054] The information managed by each table in this example has been described above. Next, the processing executed by the server 10 and the like, and the screens output on the store terminal 20 and worker terminal 30 in this example will be described.

[0055] 9 illustrates a job registration screen 50 output on the store terminal 20. The screen 50 is a screen for a store employee to register job information, and as shown in the figure, has a job title input area 51 for inputting the job title, a description input area 52 for inputting the job description, a work date and time input area 53 for inputting the work date and time, a deadline input area 54 for inputting the deadline for the job posting, a number of employees to be recruited input area 57 for inputting the number of employees to be recruited, an hourly wage input area 58 for inputting the hourly wage, and a register button 59.

[0056] The work date and time input field 53 is configured so that the work date and time can be entered as the work date and time, including the work day, work start time, and work end time. In this example, the job matching service targets daily employment jobs where employment occurs on a daily basis. The closing date and time input field 54 is initially set to the work start time on the work day.

[0057] When the registration button 59 is selected, the job information entered via the job registration screen 50 is registered, specifically, a new record is inserted in the job management table 1516, and the corresponding values ​​are set for each data item. Note that the value corresponding to "Recruiting" is set for the job status type.

[0058] 10 shows an example of a store job listing screen 60 output on the store terminal 20. The screen 60 is a screen for a store employee to check a list of job listings by the store, and as shown in the figure, has a list display area 62 that displays a list of job listings by the corresponding store, and a back button 64. Job listings by a specific store are identified by referencing the store ID in the job listing management table 1516.

[0059] The list display area 62 displays information about job offers in a table format. The information about job offers specifically includes the job offer status (either recruiting, working, or completed work), title, job offer date and time (work date and time), and application status (number of applicants / number of applicants). The number of applicants for a job offer is identified by referencing the work status management table 1517.

[0060] 11 shows an example of a worker job listing screen 70 output on the worker terminal 30. The screen 70 is a screen for a user (worker) to search for jobs, and as shown in the figure, has a work location input area 72 for inputting the work location (prefecture) of the job listing to be displayed, a work date input area 74 for inputting the work date of the job listing to be displayed, and a list display area 76 for displaying a list of the job listings to be displayed. The work location input area 72 is configured so that one or more work locations can be selected and input.

[0061] The workday input area 74 has six date objects 741, each corresponding to a separate date, arranged horizontally in date order, and is configured so that one object 741 can be selected from the six objects 741. In this area 74, the date objects 741 displayed can be switched by a flick operation or a slide operation in the horizontal direction, etc.

[0062] The list display area 76 displays a list of job vacancies to be displayed, specifically, job vacancies that match the work location (store address) input via the work location input area 72 and the work dates input via the work date input area 74, and whose job vacancy status type is "Now Hiring", are displayed in a list. In the list display area 76, a plurality of individual display areas 761, each corresponding to an individual job vacancy, are arranged in two columns vertically. In this area 76, the displayed individual display areas 761 can be switched by flicking or sliding in the vertical direction, etc.

[0063] 12 shows an example of the display content of the individual display area 761. As shown in the figure, the individual display area 761 displays information about the job (image, description, work start time, work end time, work location (store address), hourly wage, etc.), and in the upper left corner is located a remaining deadline display object 762 that displays the time remaining until the job closing date and time, and in the upper right corner is located a heart-shaped favorites object 763. When a favorites object 763 is selected, the corresponding job information is added to the worker's favorites.

[0064] When the individual display area 761 is selected, a screen (not shown) for applying for the corresponding job posting is displayed, and the worker can apply for the job posting via this screen. In this example, when an application for a job posting is made, a match is made between the worker and the store on a first-come, first-served basis. When a match is made, a new record is inserted in the work status management table 1517, and the corresponding values ​​are set for each data item (job posting ID and worker ID).

[0065] After a match is made, the worker's attendance and departure times are managed on workdays. FIG. 13 illustrates a job details screen 80 output on the worker terminal 30. The screen 80 displays detailed information about a job offer for which a match has been made with the corresponding worker, and as illustrated, includes a check-in date and time display area 82 that displays the check-in date and time (date and time the worker arrives at work), a check-out date and time display area 84 that displays the check-out date and time (date and time the worker leaves work), and a check-in / check-out button 86. Check-in is an action that reads tag storage information stored in an NFC tag 400 installed at the store where the worker works when the worker arrives at work, and check-out is an action that similarly reads the tag storage information when the worker leaves work. The job details screen 80 illustrated in FIG. 13 corresponds to the state before the worker arrives at work, and in this case, the check-in date and time display area 82 and the check-out date and time display area 84 are blank.

[0066] In this example, the check-in / out button 86 becomes selectable a predetermined time (for example, 6 hours) before the start time of the corresponding job offer, and this selectable state is maintained thereafter until check-out is registered. Workers select the check-in / out button 86 when clocking in and clocking out.

[0067] 14 is a sequence diagram illustrating the processing executed by the worker terminal 30 and the server 10 in response to selection of the check-in / out button 86 on the job details screen 80. When the check-in / out button 86 is selected, the worker terminal 30 first requests an update token from the server 10 (step S100), and the server 10 sends the update token to the worker terminal 30 (step S110). Specifically, the server 10 obtains the allocated token that has been allocated in advance to the corresponding worker from the worker information table 1515, and sends the obtained allocated token to the worker terminal 30 as the current update token.

[0068] Next, the server 10 assigns a new update token to the worker (step S120). Specifically, in the worker information table 1515, the value of a new unassigned token (managed in the token management table 1514) is set to the assigned token of the corresponding worker.

[0069] 15 illustrates an example of a tag reading guidance screen 90 that is output on the worker terminal 30 in response to receiving an update token. As shown in the figure, the screen 90 displays an image and explanatory text that guides the worker terminal 30 to approach the NFC tag 400 (dedicated sheet), and has a cancel button 92.

[0070] When the worker terminal 30 is brought close to the NFC tag 400 while the tag reading guidance screen 90 is displayed, the worker terminal 30 acquires the tag storage information stored in the NFC tag 400 and updates the token stored in the NFC tag 400 (steps S130, S140). Specifically, the tag storage information stored in the NFC tag 400 is acquired via short-range wireless communication, and the token stored in the NFC tag 400 is overwritten with the update token received from the server 10. The tag storage information includes a tag ID (electronic tag identification information) that identifies the NFC tag 400, in addition to the token.

[0071] Next, the worker terminal 30 requests the server 10 to register the check-in / out (step S150). The request is made accompanied by transmission of the tag stored information acquired from the NFC tag 400.

[0072] Next, the server 10 checks the validity of the NFC tag 400 (step S160). Specifically, the NFC tag 400 is determined to be valid when the value of the token included in the tag storage information acquired from the NFC tag 400 matches the value of the token (managed in the NFC tag information table 1513) assigned to the NFC tag 400 identified by the tag ID included in the tag storage information, whereas the NFC tag 400 is determined to be invalid when these values ​​differ. Note that if the NFC tag 400 is determined to be invalid, a predetermined error process is performed and subsequent processes are skipped.

[0073] Next, the server 10 registers the check-in / out (the arrival date and time or the departure date and time) (step S170). Specifically, by referring to the NFC tag information table 1513, the store where the NFC tag 400 is installed is identified, which is identified by the tag ID included in the tag storage information acquired from the NFC tag 400. The job offer corresponding to the combination of the identified store and work day (the current day) is identified by referring to the job offer management table 1516. In the work status management table 1517, the current date and time is set as the arrival date and time or the departure date and time for the identified combination of job offer and worker (if the arrival date and time has not been set, the arrival date and time is set, and if the arrival date and time has already been set, the departure date and time is set). The registration of the arrival date and time or the departure date and time can also be considered an update of the work status (before coming to work, during work, and after leaving work).

[0074] Here, if there is no record in the work status management table 1517 corresponding to the identified combination of job offer and worker (i.e., the matching between the corresponding job offer and worker has not been established, and the worker's work schedule at the corresponding store has not been registered), a specified error handling process is performed and subsequent processing is skipped.

[0075] Next, the server 10 updates the allocated token of the NFC tag 400 (step S180). Specifically, in the NFC tag information table 1513, the allocated token of the corresponding NFC tag 400 is updated to the updated value (the value of the update token transmitted to the worker terminal 30 in step S110).

[0076] On the other hand, when the check-in / out registration result is received from the server 10, the worker terminal 30 displays the registration result (step S190). Here, an employment contract may be automatically concluded between the corresponding employer and worker upon registration of the check-in (work date and time).

[0077] In this example, the validity of the NFC tag 400 installed in the store is determined using the value of the token contained in the tag storage information stored in the NFC tag 400, and further, the value of the token is updated in response to the acquisition of the tag storage information, thereby preventing fraudulent operations such as those for clocking in and out that misuse the information stored in the NFC tag 400.

[0078] After the worker leaves work, a mutual evaluation is conducted between the worker and the store, and specifically, the evaluations entered via the screens displayed on the store terminal 20 and the worker terminal 30 are registered in the store evaluation and worker evaluation in the work status management table 1517. The evaluation is conducted, for example, on a five-point scale.

[0079] In the above example, if the worker terminal 30 fails to update the token stored in the NFC tag 400 (step S140), the NFC tag 400 may be managed as a tag that does not require validation based on the token (for example, this may be achieved by adding a "validation determination unnecessary flag" to the NFC tag information table 1513). In this case, if the NFC tag 400 installed in the store is a tag that does not require validation, the above-mentioned processes of sending an update token (step S110), allocating a new update token (step S120), updating the token (step S140), checking the validity of the NFC tag 400 (step S160), and updating the allocated token of the NFC tag 400 (step S160) are skipped, and check-in / out registration (step S170) is performed (i.e., the NFC tag 400 that is a tag that does not require validation is determined to be valid regardless of the value of the token). As a result, even if a writing error or the like occurs in the NFC tag 400, check-in / out is possible, and the job matching service can be continued.

[0080] In the above example, the NFC tag information table 1513 manages tokens assigned to the corresponding NFC tags 400, but it is also possible to manage values ​​different from tokens. For example, a calculated value obtained by applying a predetermined calculation formula to the token value may be managed, and when checking the validity of the NFC tag 400, the NFC tag 400 may be determined to be valid if the value obtained by applying the calculation formula to the token value included in the tag storage information acquired from the NFC tag 400 matches the calculated value managed in the NFC tag information table 1513.

[0081] In the above example, the token stored in the NFC tag 400 is updated when a person clocks in and out (checks in and out), but the token may be updated when a person clocks in and out and if a predetermined update condition is met. Various conditions may be applied as the update condition.

[0082] For example, the specified update condition may be a condition that is met based on the time that has elapsed since the last update date and time of the token stored in the corresponding NFC tag 400 (which may, for example, be managed in the NFC tag 400 as part of the tag storage information), or may be a condition that is met when the elapsed time is equal to or greater than a threshold value (for example, one day, one week, or one month).

[0083] Furthermore, for example, the specified update condition may be a condition that is satisfied based on the worker's working status at that time (before coming to work or at work), or, for example, a condition that is satisfied only when the working status is before coming to work (in this case, the token is updated when coming to work, but is not updated when leaving work), or a condition that is satisfied only when the working status is at work (in this case, the token is updated when leaving work, but is not updated when coming to work).

[0084] Furthermore, the predetermined update condition may be changed based on various parameters. For example, the predetermined update condition may be changed based on the number of token updates (e.g., managed in the NFC tag information table 1513) in the corresponding NFC tag 400. For example, if the number of updates is less than a threshold (e.g., 10,000), the condition may be configured as a condition that is met when the elapsed time from the last update date and time is equal to or greater than a first threshold (e.g., one day), whereas if the number of updates is equal to or greater than the threshold, the condition may be configured as a condition that is met when the elapsed time from the last update date and time is equal to or greater than a second threshold (e.g., one week) that is greater than the first threshold.

[0085] Furthermore, for example, the predetermined update condition may vary based on the value of a parameter associated with the store (for example, managed in the employee information table 1511 or the store information table 1512), and may be configured as a condition that is met when the time elapsed since the last update date and time is equal to or greater than a first threshold value (for example, one day) if the store's area is a first area, while when the store's area is a second area, the condition may be met when the time elapsed since the last update date and time is equal to or greater than a second threshold value (for example, one week) that is greater than the first threshold value. Furthermore, the predetermined update condition may be set for each store (for example, selected by the store's staff).

[0086] In the job matching service providing system 1 according to the present embodiment described above, when a worker's worker terminal 30 acquires tag storage information stored in an electronic tag 400 (e.g., an NFC tag 400) installed in a store, the validity of the electronic tag 400 is determined based on tag-side determination information (e.g., a token) included in the tag storage information. If the electronic tag 400 is determined to be valid, the worker's work status at the store is updated (e.g., check-in / out is registered). Furthermore, the tag-side determination information stored in the electronic tag 400 is updated in response to the acquisition of the tag storage information. Therefore, for example, unauthorized manipulation of clock-in / clock-out records by malicious workers is suppressed compared to when using a two-dimensional code or the like with information embedded to identify the store. In other words, the system 1 supports the appropriate management of workers' work status.

[0087] In another embodiment of the present invention, the service provided by the server 10 may be configured to have the function of managing the working status of workers in stores, but not the function of controlling the matching between employers and workers.

[0088] The processes and procedures described herein, other than those explicitly described, may be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, and magnetic disks. The processes and procedures described herein may also be implemented as computer programs corresponding to the processes and procedures and executed by various computers.

[0089] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be implemented by combining them into fewer components or breaking them down into more components. [Explanation of symbols]

[0090] 1. Job matching service provider system 10 Servers 11. Computer Processor 112 Server-side control unit 15. Storage 151 various tables 1511 Employer Information Table 1512 Store Information Table 1513 NFC tag information table 1514 Token Management Table 1515 Worker Information Table 1516 Recruitment Management Table 1517 Work Status Management Table 20 Store terminals 21 Computer Processor 212 Store terminal side control unit 30 worker terminals 31 Computer Processor 312 Worker terminal side control unit 40 Server-side programs 42 Store terminal program 44 Worker terminal side program 50 Job registration screen 60 Store job listing screen 70 Job listing screen for workers 80 Job details screen 90 Tag reading guide screen 400 Electronic tags, NFC tags

Claims

1. A system for managing the working status of a worker, comprising: a worker terminal operated by the worker; and a server, The worker terminal acquires tag stored information stored in an electronic tag installed in a store, the tag stored information including first determination information for determining the validity of the electronic tag; The worker terminal transmits the tag storage information to the server; a step of updating the first determination information stored in the electronic tag by the worker terminal; a step in which the server determines the validity of the electronic tag based at least on the first determination information; If the electronic tag is determined to be valid, the server updates the work status of the worker at the store. system.

2. the tag storage information includes electronic tag identification information that can identify the electronic tag, The step of determining the validity of the electronic tag includes acquiring the second determination information associated with the electronic tag identified by the electronic tag identification information from a storage device that stores the electronic tag in association with the second determination information based on the first determination information stored in the electronic tag, and determining that the electronic tag is valid if the value of the second determination information based on the value of the first determination information included in the tag storage information matches the value of the second determination information acquired from the storage device; The system further executes a step in which the server updates the second determination information stored in the storage device in association with the electronic tag in response to an update of the first determination information by the worker terminal. The system of claim 1.

3. The second determination information is the first determination information. The system of claim 2.

4. The step of updating the working status includes updating the working status of the worker, the working status including at least one of a first status before coming to work, a second status during work, and a third status after leaving work. The system of claim 1.

5. The step of updating the work status includes performing a predetermined error process when the work schedule of the worker at the store is not registered. The system of claim 1.

6. the step of updating the first information for determination includes, when the updating of the first information for determination fails, transmitting update failure information indicating a failure in updating the first information for determination to the server; The system further executes a step in which, when the server receives the update failure information, the server sets the electronic tag to an electronic tag that does not require validation. The system of claim 1.

7. the step of determining the validity of the electronic tag includes determining that the electronic tag is valid regardless of the first determination information when the electronic tag is set as an electronic tag that does not require a determination of validity; The system of claim 6.

8. The step of updating the first information for determination includes updating the first information for determination when a predetermined condition is satisfied. The system of claim 1.

9. the predetermined condition is satisfied based on the elapsed time since the last update date and time of the first determination information. The system of claim 8.

10. The step of updating the working status includes updating the working status of the worker, the working status including at least one of a first status before coming to work, a second status during work, and a third status after leaving work; The predetermined condition is satisfied based on the working status of the worker at the store. The system of claim 8.

11. the predetermined condition changes based on the number of updates of the first determination information. The system of claim 8.

12. The predetermined condition is set for the store. The system of claim 8.

13. the predetermined condition varies based on the value of a parameter associated with the store; The system of claim 8.

14. A method for managing the working status of a worker, the method being executed by a worker terminal operated by the worker and a server, comprising: The worker terminal acquires tag stored information stored in an electronic tag installed in a store, the tag stored information including first determination information for determining the validity of the electronic tag; The worker terminal transmits the tag storage information to the server; a step of updating the first determination information stored in the electronic tag by the worker terminal; a step in which the server determines the validity of the electronic tag based at least on the first determination information; If the electronic tag is determined to be valid, the server updates the work status of the worker at the store. method.

Images