JP2002189875A - System for effectively utilizing human resource - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an employment placement system capable of matching a labor force demand of a job offering company and a demand on a job seeker side in a real time. SOLUTION: Job offer information from an employer client machine 12 is successively stored in a data base 13 of a server 11 fulfilling an employment placement function through the Internet in a figure. Also job seeker information from job seekers is successively stored in the data base 13 from portable telephones possessed by the job seekers through the Internet. The server 11 retrieves the data base 13, extracts the job seeker information corresponding to employment conditions of the job offer information and distributes the job offer information to the portable telephones by e-mail. The job seekers apply desired job offer information of the distributed job offer information by the portable telephones and await employment. Decisions on employment/ unemployment are made by the server himself or an employer.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a human resource utilization system, and more particularly to a human resource utilization system using an open network represented by the Internet and a portable terminal device represented by a portable terminal. is there.

[0002]

2. Description of the Related Art In an industry where the busy season varies greatly depending on the time of day, week, and season, especially in the service industry, it is an important issue how to secure a labor force that matches the fluctuating required labor force. I have. In the past, most recruiting activities relied on recruiting advertisements in newspapers and information magazines, but for recruiting activities by advertising, the time required to prepare a manuscript at least one week before the advertisement is posted. In order to secure a sufficient labor force, the number of required workers was predicted long beforehand and applications were made, or uncertain methods of recruiting posters etc. were displayed nearby. Was.

[0003] In recent years, instead of this, a technology that accomplishes this task under a network environment open to the outside such as the Internet has emerged. For example, when a recruiter wants to recruit human resources, register information on the job to be recruited in the server, and the recruiter registers recruitment information indicating his / her ability etc. on the Internet to perform recruiting activities. Has been put to practical use. In this way, companies can find candidates for the jobs they are looking for, and job seekers can find jobs to which they can apply.

[0004]

SUMMARY OF THE INVENTION However,
In the conventional recruiting site, the recruiting side searches for a desired human resource or a job desired by the job seeker, and a notification is made when a new human resource or job that meets the conditions registered in advance is registered. In fact, if it is possible to actually match a job with a human resource within the same day or within a few days, there is a problem in that only job recruitment and job offer information is disclosed. In other words, the function of actually matching work and human resources and realizing employment cannot be performed on the site as it is, so posters can be posted in a shorter time compared to recruitment activities using conventional media such as newspapers and magazines. Although job recruiting activities became possible in a wider area compared to the above methods, there were requests for recruitment of job recruiters that actually occurred suddenly, and jobs were recruited during the time when job seekers wanted to work now. Could not really meet the demand for security.

[0005] In view of the above problems, the present invention utilizes a network environment such as the Internet, and a technology for simultaneously distributing a large amount of e-mails to portable terminals, thereby recruiting job recruiting needs and job seeker recruitment. An object of the present invention is to provide an intermediary system that matches workable hours and maintains the level of the provided workforce at a certain level. Supermarkets and department stores. In the retail industry, such as convenience stores, the employment of temporary employees (including part-time and part-time jobs), which are only required during specific dates and times, such as weekends and holidays or the season of the year of the middle of the year, is an important part of store management. . Until now, employment adjustments for temporary employees have included contacting the dispatch company by phone,
The registrant was contacted mainly by telephone, fax, or letter to the employment agency or the worker himself. Adjustment was difficult, which sometimes hindered store management.

[0006] Therefore, a system capable of recruiting applicants for employment in real time, notifying the intermediary directly of the area and time desired by the employment without directly in front of the terminal, and receiving the will of employment. , And a system that enables workers working in each store to report work time and work contents using a portable terminal device represented by a portable terminal without stopping at an office or the like. It is in.

[0007]

SUMMARY OF THE INVENTION The present invention provides a storage device for storing job information, a registration device for registering job seeker information, job information stored in the storage device, and a registration device registered in the registration device. Selecting means for selecting job seekers matching the employment conditions of the job information by comparing the job information with the job seeker information, and a human resource utilization system connectable to a network, further comprising: The job seeker information has a unique identification code of a communication device owned by the job seeker connectable to the network, and the human resource utilization system transmits job information based on the unique identification code via the network. And automatically distributes the information to the communication device of the job applicant selected by the selection means in the form of digitized information.

[0008] Here, a job recruiter, a job seeker, an employer, and a human resource utilization system operator access the human resource utilization system from a terminal device connectable to the network, and register recruitment information and job applicant information. In addition, the operability and convenience of the human resource utilization system can be improved by allowing the job seeker to access the human resource utilization system using the communication device. In addition, by including job evaluation data in the job seeker information and information indicating the level of the job evaluation data required by the employer for the employee in the job offer information, the efficiency of job information distribution and the recruitment of job seekers can be improved. it can.

Furthermore, by employing a method of registering the working hours and transportation expenses of workers in the human resource utilization system, the salary calculation becomes easy. An extremely efficient system is constructed by using the Internet as the network and a mobile phone connectable to the Internet as the communication device, and using a configuration in which job information is distributed to the communication device by e-mail. In this case, if the link destination of the Internet homepage owned by the employer or the Internet homepage held by the human resource utilization system operator is inserted and displayed or automatically inserted into the recruitment information delivered to the communication device, Convenience increases.

[0010]

Embodiments of the present invention will be described below in detail with reference to the accompanying drawings. In the following description and the accompanying drawings, components having substantially the same function are denoted by the same reference numerals, and redundant description will be omitted.

(1) Description of Basic System Configuration and Terms FIG. 1 shows an overall configuration diagram of an embodiment of the present invention. The terms used in the following embodiments will be described with reference to FIG.

[Human Resource Utilization System] (11): Member registration, distribution of work information to a portable terminal device (hereinafter, referred to as a “mobile terminal”) represented by a mobile phone, response to job application, In order to enable registration of working hours, settlement of transportation expenses, etc., functions of providing various service pages and transmitting and receiving digitized information are provided. It is mainly composed of a server machine, an input / output device, and a database described below (hereinafter, simply referred to as “system”).

[Human resource utilization system server machine]
(111): Computer serving as the core of the system, connected to an open network represented by the Internet. (Hereinafter simply referred to as “server”).

[Human resource utilization system input / output device] (1)
12): A keyboard, which is an input / output device connected to the server.
Mouse, display, printer, scanner, digital camera, etc. The input / output device may be connected not only directly to the server but also via a local network or an open network. (Hereinafter simply referred to as “system I / O”).

[Human Resource Utilization System Database]
(113): A data storage device connected to the main server, for storing member information, storing distribution contents and distribution history, recruiting application contents, working hours, transportation expenses, salary data, and the like. (Hereinafter simply referred to as “database or DB”).

[Member client machine] (13): A computer operated by a member who wants to distribute work information (hereinafter simply referred to as a member), and is connected to an open communication network represented by the Internet. FIG.
In FIG. 1, only one is shown as a representative, but typically there are a plurality of such members (hereinafter simply referred to as “member client”).

[Employer Client Machine] (12) A computer operated by an employer that distributes work information, and is connected to an open communication network represented by the Internet or connected to a server via a local network. good. In FIG. 1, one is shown as a representative, but typically there is a plurality (hereinafter simply referred to as “business owner client”).

[Server machine for relaying data to portable terminal] (14): A computer that delivers digitized information or a service page to a portable terminal owned by a member (hereinafter, referred to as a computer).
Connected to an open network. This carrier server can receive various information registered by members from a portable terminal having a browser function and relay it to the server. In FIG. 1, one is shown as a representative, but typically there is a plurality.

[Member's portable terminal] (15): A terminal device carried by the member that can receive digitized information represented by Internet e-mail. Further, a mobile phone or a mobile terminal having a browser function capable of connecting to an open communication network and transmitting and receiving data may be used. In FIG. 1, one is shown as a representative, but typically there is a plurality. In the following embodiments, a case where a mobile phone with a browser function (hereinafter simply referred to as “mobile terminal”) is used as the mobile terminal device will be described in detail.

[Internet] (16): An open communication network is shown in FIG. 1 as a representative.

[Electronic information] (17): One of the information exchanged between the server and each of the client machines. Internet electronic mail is a typical example, but not limited thereto. May be digitized information including the information. In the following embodiment, a case where an electronic mail is used as the digitization information will be described in detail.

(2) Outline of Database The server is constructed with a database having a hierarchical structure divided into a plurality of systems as follows. FIG. 2 shows a system block diagram in the embodiment of the present invention. Hereinafter, a database used in the following embodiments will be described with reference to the drawings.

[Recruiting Company Registration Department Database] (300
0): This is a database that stores information on recruiting companies that use this system. For the storage contents, refer to the field name field in FIG. Further, the contents of this storage are not limited to the fields described in FIG. 3, and may be omitted when this system is operated by one company.

[Member Registration Department Database] (300
1): This is a database that stores the member's personal information of job seekers and employees who use this system. For the storage contents, refer to the field name section in FIG. The contents of this storage are shown in Fig. 4.
Is not limited to the fields described in
Examples other than the password and the mobile terminal e-mail address are examples.

[Job Registration Department Database] (300
2): A database that stores work information transmitted to mobile terminals using this system. For the storage contents, refer to the field name field in FIG. Further, the contents of this storage are not limited to the fields described in FIG. 5, but are shown as an example.

[Distribution Information Registration Section Database] (300
3): A database for storing distribution data to be distributed to the mobile terminal. For the storage contents, refer to the field name section in FIG. Further, the contents of this storage are not limited to the fields described in FIG.

[Distribution Result Storage Database] (300
4): This is a database that stores the results of distribution to the portable terminal. For the storage contents, refer to the field name field in FIG. Further, the contents of this storage are not limited to the fields described in FIG. 7 but show an example.

[Employer Storage Database] (300
5): A database that stores the information of the employer corresponding to the work information transmitted to the mobile terminal using this system.
For the storage contents, refer to the field name field in FIG. Also,
The contents of this storage are not limited to the fields described in FIG.

[Recruitment application storage database] (300
6): A database that stores applicant information for work information distributed to mobile terminals using this system.
For the storage contents, refer to the field name field in FIG. Also,
This storage content is not limited to the fields described in FIG. 9 but shows an example.

[Working time registration section database] (300
7): This is a database that stores the member's work time. For the stored contents, refer to the field name section in FIG. Further, the contents of this storage are not limited to the fields described in FIG. 10, but are shown as an example.

[Transportation Expense Register Database] (300
8): A database for storing member travel expenses. Refer to the field name section in FIG. 11 for storage contents. Further, the contents of this storage are not limited to the fields described in FIG. 11, but show an example.

[Employee salary data storage unit database]
(3009): A database for storing salary information of members. For the stored contents, refer to the field name field in FIG.
Further, the contents of this storage are not limited to the fields described in FIG. 12, but show an example.

(3) Member Registration from Mobile Terminal FIG. 13 shows a message when a job applicant (hereinafter referred to as “job seeker”) registers a new member in the present system using the mobile terminal. It shows a transmission / reception procedure. The same procedure can be performed not only on the mobile terminal but also on various mobile devices that can be connected to the Internet.

The job seeker issues a URL requesting the display of the member's gate form to the server from the personal portable terminal (step (5000)). The server receives the URL, develops the member's gate form in HTML, and transmits it to the portable terminal (step (5001)).

In the portable terminal, a member gate screen shown in FIG. 14 is displayed. (In the function of developing a program created in HTML language on the portable terminal screen, the browser function provided in the portable terminal is already known. All of the screen display on mobile terminals will be realized by this browser function.) When the job seeker selects "I want to register," a URL for requesting display of a member registration screen is transmitted from the portable terminal to the server (step (5002)). The server issues HTML displaying the member registration screen (step (5003)), and the member registration screen shown in FIG. 15 is displayed on the portable terminal. At this time,
HTML linking the e-mail address specified by this system as the e-mail destination to the "here" part of FIG.
Unfold it.

When the job seeker selects and clicks "here", the portable terminal displays a mail transmission screen with the mail receiving server of the present system as the destination and the e-mail address registered in the portable terminal as the sender. The e-mail is transmitted to the present system by using the e-mail transmission function attached to (step 5004). This processing is already known for a portable terminal in which a browser function and a mail transmission function are seamlessly linked. (For a model in which the browser function and the mail transmission function are not seamlessly linked, enter the URL requesting the member registration screen of the server of this system, and enter the e-mail of the mobile terminal in the member registration screen shown in FIG. 17. An area for inputting an address (hereinafter simply referred to as “e-mail address”) is provided and a mobile terminal e-mail address is obtained by directly inputting the area.

The server extracts the sender's e-mail address from the received e-mail (step 5005), secures a new record shown in FIG.
D is determined and stored together with the extracted mail address (step (5006)). Further, the e-mail shown in FIG. 16 is transmitted to the portable terminal with the extracted e-mail address as the destination and the URL requesting the member registration screen added thereto (step (5007)).

By clicking on the URL requesting the member registration screen appended to the e-mail sent to the job seeker's mobile terminal, the mobile terminal switches its operation to the browser function, and the URL is notified to the server. (Step (5
008)). The server receives the URL and transmits HTML for the member registration screen to the portable terminal (step (500)
9)).

The job seeker inputs information such as name, mobile phone number, desired job type, desired work place, password, etc. on the member registration screen shown on the mobile terminal in FIG. 17 and clicks "Send" to input. The transmitted data is transmitted to the server (step (5010)). At this time, programming is performed so that the mobile terminal e-mail address of the job seeker is attached to the HTML that performs the “transmission” process.

When the server receives the data from the portable terminal, the server searches the member registration database (FIG. 4) using the mail address as a key, and stores the received data in the corresponding record (step (5011)). Further, a registration confirmation mail shown in FIG. 18 is generated and transmitted to the registered mobile terminal mail address as a destination to notify the end of the procedure (step (5012)).

(4) Member Registration from Member Client FIG. 19 shows a message transmission / reception procedure when a job seeker uses the member client to register a new member in the present system. Job seeker requests UR from member client to server to display gate screen for member
L is issued (step (5100)). (Functions such as issuing a URL and developing a program created in the HTML language on a member client screen and transmitting / receiving data to / from a server can be realized by a browser program, which is a known technique. All of the screen display and data transmission / reception by the computer are realized by this browser function.) The server receives the URL and displays the member gate screen as HTM
L and transmits to the member client (step (5101)).

The member client has a member gate screen
FIG. 20 is displayed. When the job seeker selects "I want to register," a member registration screen display request URL is issued from the member client to the server (step (510)
2)). The server issues a member registration screen display HTML (step (5103)), and the member client displays the member registration screen (FIG. 21).

Member registration screen in which the job seeker is displayed on the member client Name, date of birth, gender, address, telephone number, FAX number, mobile phone number, mobile terminal mail address, mobile terminal model name, Enter information such as occupation type, employment period, working period, work day, work location, etc. At this time, programming is performed so that an image data file stored in the member client can be selected by clicking "Register face photograph".

By clicking "OK", the input data and the image file data are transmitted to the server (step (5104)). The server generates a member registration confirmation screen shown in FIG.
The data is developed in the ML and transmitted to the member client (step (5105)).

The member client clicks “register” on the displayed member registration confirmation screen (step (510)
6) When it is done, a URL for requesting formal registration is issued to the server. When the server receives the request for formal registration, the new I
Decide D and password, member registration department database
, A new record is secured and the received input data is stored (step (5107)). Next, a screen showing the completion of the member registration is generated from the ID, the password, and the mobile terminal mail address, FIG. 23 is developed into HTML, and transmitted to the member client (step (5108)). Further, with the registered mobile terminal mail address as the destination, FIG.
Generate and send the registration confirmation mail shown in (Step (5)
109)).

(5) Member Login from Mobile Terminal FIG. 13 and FIG. 24 show a message transmission / reception procedure when a member logs in to the present system via the mobile terminal. Members can use the mobile device to access the server,
A URL requesting display of a member gate screen is issued (step (5000)). The server receives the URL, develops the member gate screen in HTML, and transmits it to the portable terminal (step (5001)). On the mobile terminal, a member gate screen FIG. 14 is displayed.

When "member login" on the member gate screen is selected, a URL requesting display of the member login screen is issued from the portable terminal (step (5013)).
The server receives this and transmits a member login screen display HTML (step (5201)), and the member login screen FIG. 25 is displayed on the portable terminal.

Member registration screen displayed on portable terminal Member inputs ID and password on FIG. 25 and selects "Send" (step (5202)).
And a password collation request URL are transmitted. The server receives the collation request, searches the member registration unit database FIG. 4 using the ID as a key, and performs a password collation process (step (5203)).

If the password is not suitable, a login error screen (FIG. 26) display HTML for notifying the member is transmitted (step (5204)), and the login is re-executed by selecting "RETURN". (Step (5205)). If the password matches,
HT for displaying menu selection screen after login from server
The ML is transmitted (step (5207)), a menu selection screen (FIG. 27) is displayed, and it is possible to shift to a procedure for each function. FIG. 28 shows an ID / password acquisition procedure when the member forgets the password. Member log-in screen When "here" is selected and clicked on FIG. 25, the mobile terminal displays an e-mail transmission screen with the e-mail address registered in the mobile terminal as the sender and the e-mail address registered in the mobile terminal as a destination. An e-mail is transmitted to the system using the e-mail transmission function attached to the portable terminal (step 52).
11). The server extracts the sender's e-mail address from the received e-mail (step 5301), and uses the mobile e-mail address in FIG.
D, searching for the password (step 5302), and sending the e-mail FIG. 29 to the portable terminal with the ID and password attached to the extracted mail address (step (5303)).

(6) Member Login from Member Client FIGS. 19 and 30 show a message transmission / reception procedure when a member logs in to this system from a member client. The member issues a URL for requesting display of the member gate screen from the member client to the server (step (5100)). The server receives the URL, expands the member gate screen of FIG. 20 to HTML, and transmits it to the member client (step (5101)).

The member client has a member gate screen
FIG. 20 is displayed. When the member selects “member login”, a member login screen display request URL is issued from the member client to the server (step (511)
0)). The server receives this and displays the member login screen H
The TML is transmitted (step (5401)), and a member login screen (FIG. 31) is displayed on the member client.

When the member inputs the ID and password and selects "login" on FIG. 31 on the member login screen displayed on the member client, a password collation request URL is transmitted to the server (step (540)
2)). When the server receives the collation request, the server searches the member registration unit database FIG. 4 using the ID as a key, and performs password collation processing (step (5403)).

If the password is not suitable, a login error screen notifying the member to that effect is sent. The display HTML of FIG. 32 is transmitted (step (5404)), and the login is re-executed by selecting "RETURN". (Step (5405)). If the password matches,
The server transmits HTML for displaying the menu selection screen (step (5407)), and the menu selection screen is displayed.
3 is displayed (step (5407)), and it is possible to shift to the procedure for each function. (See below)

FIG. 34 shows an ID / password acquisition procedure when the member forgets the password. Member login screen In FIG. 31, when a mobile mail address is input and “ID password transmission” is selected and clicked, a mobile mail address and an ID / password notification e-mail transmission request URL are transmitted to the server. Upon receiving the transmission request, the server searches the member registration database of FIG. 4 using the mobile mail address as a key to extract the ID and password (step 5502), and adds the ID and password to the mobile mail address as a destination. The e-mail of FIG. 29 is transmitted to the portable terminal (step (550)
3)).

(7) Change of Member Registration Contents from Mobile Terminal FIG. 35 shows a procedure for changing member registration contents from the mobile terminal. When "registration change" is selected in FIG. 27, the screen display request URL and the member ID relating to the change of the member registration content are transmitted from the portable terminal to the server (step (5208)). The server searches the member registration unit database FIG. 4 using the member ID as a key and extracts the record of the corresponding member (step (6001)). Thereafter, the registration contents of the member are generated as a mobile terminal screen shown in FIG. 36, developed into HTML, and transmitted to the mobile terminal (step (6002)).

On the registration content change screen displayed on the portable terminal, the member changes any item and selects "send" (step (6003)). The change-registered data is transmitted from the portable terminal to the server. The server receives this, updates the information of the corresponding record in FIG. 4 of the member registration unit database (step (6004)), and further sets the registered mobile terminal mail address in FIG.
Then, a registration change confirmation mail is generated and transmitted to notify the end of the procedure (step (6005)).

(8) Change of Member Registration Contents from Member Client FIG. 38 shows a procedure of changing registration contents from the member client. According to (6) the login procedure from the member client, a member menu screen (FIG. 33) is displayed on the member client. "Change registration" on the screen
If you select, from the member client to the server,
The screen display request URL and ID relating to the change of the member registration content are transmitted (step (5408)). The server searches the member registration section database FIG. 4 using the ID as a key and extracts the record of the corresponding member (step (6101)).
Thereafter, the registration contents of the member are generated as a registration change screen shown in FIG. 39, expanded to HTML, and transmitted to the member client (step (6102)).

On the registration content change screen displayed on the member client, the member changes any item and clicks “Registration”.
Is selected (step (6103)). Data for change registration is transmitted from the member client to the server. The server receives this, and the member registration department database Fig. 4
Is updated (step (610)
4)) Further, the registration change confirmation mail shown in FIG. 37 is generated and transmitted to the registered mobile terminal mail address to notify the end of the procedure (step (610)).
5)).

(9) Login from Business Owner Client FIG. 40 shows a login procedure from the business owner client to the present system. The business owner issues a URL for requesting the business owner gate screen from the business owner client to the server (step (6600)). The server issues a business owner gate screen display HTML (step (6601)), and the business owner client displays the business owner gate screen FIG.

When "login" on the business owner gate screen is selected, a URL for requesting the business owner login screen is issued to the server (step (6602)). In response to this, the server transmits the business owner login screen display HTML (step (6603)), and the business owner login screen image 42 is displayed on the business owner client.

When the business owner logs in the business owner log-in screen displayed on the business owner client and clicks “login” on FIG. 42, a password verification request URL is transmitted to the server (step ( 6
604)). Upon receiving the verification request, the server searches the recruiting company registration section database FIG. 4 using the ID as a key, and performs a password verification process (step (6605)).

If the password is inappropriate, a login error screen notifying the access user of the password is transmitted. The display HTML of FIG. 43 is transmitted (step (6606)).
Selecting "return" re-executes login (step (6615)).

If the password matches, the server transmits HTML for displaying the menu screen (step (6607)), the menu selection screen shown in FIG. 44 is displayed, and it is possible to shift to the procedure for each function. .
FIG. 45 shows an ID / password acquisition procedure when the business owner forgets the password. Business owner login screen In FIG. 42, when the user inputs the mail address and selects and clicks “ID password transmission”, the mail address and the ID / password reissue electronic mail transmission request URL are transmitted to the server. When the server receives the transmission request,
Recruiting company registration section database using the email address as a key. FIG. 3 is searched to extract the ID and password (step 8003).
An e-mail with the password added is transmitted as shown in FIG. 46 (step (8004)).

(10) Member Registration from Employer Client FIG. 47 shows a procedure for registering a member from an employer client. According to (9) the log-in procedure from the business owner client, a processing menu screen FIG. 44 is displayed on the business owner client.

When "member registration" is selected on the screen, a URL requesting display of a menu screen for member registration is issued from the business owner client to the server (step (6608)). The server receives the URL, develops a menu screen for member registration in HTML, and transmits it to the employer client (step (6701)).

A member registration menu screen FIG. 48 is displayed on the business owner client. When "new registration" is selected, the business owner client issues a new member registration screen request URL to the server (step (6702)). The server issues HTML for member registration screen display (step (6703)), and a new member registration screen (FIG. 49) is displayed to the business owner client.

Member registration screen in which business owner is displayed on business owner client Name, date of birth, gender, address, telephone number, FAX number, mobile phone number, mobile terminal mail address, mobile terminal model name on FIG.・ Enter information such as occupation type, employment period, working period, working day, work location, etc. At this time, programming is performed so that an image data file stored in the business owner client can be selected by clicking “Register face photo”.

By clicking "OK", the input data and the image file data are transmitted to the server (step (6704)). The server generates a member registration confirmation screen shown in FIG.
The data is developed in the ML and transmitted to the business owner client (step (6705)).

The employer client clicks “Register” on the displayed member registration confirmation screen (step (670)
6) When it is done, a URL for requesting formal registration is issued to the server. When the server receives the request for formal registration, the new I
Decide D and password, member registration department database
, A new record is secured, and the received input data is stored (step (6707)).

Next, a screen (FIG. 51) showing the completion of the member registration is generated from the ID, the password, and the mail address of the portable terminal, developed into HTML, and transmitted to the business owner client (step (6711)). Further, a registration confirmation mail shown in FIG. 18 is generated and transmitted to the registered mobile terminal mail address (step (6708)).

When "Register next" is selected on the screen shown in FIG. 51, a member registration screen shown in FIG. 49 is displayed, and a new member can be cyclically registered.

(11) Collective Registration of Members by Employer Client FIG. 52 shows a procedure for collectively registering members from the employer client. What is collective membership registration?
The member data file stored in the prescribed format in the business owner client is uploaded to the server, the server deploys the file at once, and adds or replaces it in the database.

According to (10) the member registration procedure from the business owner client, a processing menu screen FIG. 48 is displayed on the business owner client. When the employer selects "file upload", the employer client issues a member file upload screen request URL to the server (step (6709)). The server issues HTML for displaying a member file upload screen (step (6801)), and the business owner client displays the member file upload screen FIG.

Upload screen displayed on business owner client When "File selection" in FIG. 53 is selected, programming is performed so as to display a screen for selecting an arbitrary file stored in the business owner client (this program is , And can be easily programmed with standard functions of the already known HTML language).

By selecting “select file”,
The member file selection screen shown in FIG. 54 is displayed, and the employer selects the member batch registration data stored in a prescribed format prepared in advance and selects “OK”. The selected file name is displayed on FIG. 53, and it is checked whether it is overwritten or added to the database, and by selecting "Send", the member collective registration data is sent to the server (step (6802)).

Upon receiving the member batch registration data, the server temporarily stores the data in an arbitrary memory (step (6803)),
The HTML of the screen (FIG. 55) notifying that the development to the database has been started is transmitted to the business owner client (step (6804)). In addition, the database is updated by either overwriting or adding according to the request (step (6805)). If this update process is performed during the execution of other processes in the system, it may take a certain amount of processing time. When the database update process is completed, the registered email address of the business owner client is deleted. A database update completion mail shown in FIG. 56 is generated and transmitted as the destination (step (6806)). Further, a registration confirmation mail shown in FIG. 18 is generated and transmitted to all the mobile terminal mail addresses registered collectively (step (6707)).

(12) Member Search / List / Individual Display by Employer Client FIG. 57 shows a procedure for changing member registration contents from the employer client. 48. When "Member List" is selected in the member registration menu, the UR requesting the server to display a member search screen from the employer client
L is issued (step (6710)). Server is U
RL received member search screen Figure 58 is expanded to HTML,
Send to business owner client (step (690)
1)).

A member search screen FIG. 58 is displayed on the business owner client. The business owner inputs various conditions to be searched according to the search conditions displayed on the screen. When "Send" is selected, the business owner client issues a member search condition and a URL requesting execution of the search to the server (step (6902)).

Upon receiving the member search request, the server searches the member registration section database in FIG. 4 under the specified conditions (step (6903)), develops data that matches the conditions on the member list screen in HTML, and transmits the data to the employer client. (Step (6904)). The business owner client displays a member list screen (FIG. 59).

(13) Change of Member Registration Contents by Employer Client When the employer selects an arbitrary member name from the screen of FIG. 59, a URL requesting the designated member registration change screen is transmitted from the employer client to the server. (Step (69
05)). Upon receiving this request, the server further searches the member registration database (FIG. 4), expands the designated member information on the member information screen shown in FIG. 60, and transmits it to the employer client (step (6906)).

When "change" is selected on the member information screen in FIG. 60, a registration data change screen conforming to FIG. 49 is transmitted from the server. When the business owner changes the registration data and selects "register", the data to be changed and registered is transmitted to the server (step (6907)). The server receives this, updates the information of the corresponding record in the member registration unit database in FIG. 4 (step (6910)), and generates and transmits a registration change confirmation mail shown in FIG. 18 to the registered mobile terminal mail address. Then, the end of the procedure is notified (step (6911)).

(14) Change of Information Distribution Setting of Member from Business Client FIG. 62 shows a procedure of changing the information distribution setting of a member from the business client. According to (13) the procedure for changing the registered member content from the business owner client, the business owner client is displayed with the member list screen shown in FIG. 59 (steps (7001) to (7005)).

When the business owner checks "stop" on the list screen, the business owner client sends the checked member ID and the stop request URL to the server (step (7006)), and the member registration section database shown in FIG. Data indicating that distribution is not performed is written in the distribution flag storage field of the record (step (7007)).

When the business owner releases the check of “stop” already checked on the list screen, the business owner client sends the unchecked member ID and the distribution restart request URL to the server (step (7006)). ),
Member registration unit database Data indicating that distribution is to be performed is written in the distribution flag storage field of the corresponding record in FIG. 4 (step (7007)).

(15) Deletion of Member Registration from Employer Client When the employer checks “delete” on the list screen of FIG. 59, the employer client transmits a designated member ID and a deletion request URL to the server ( Step (700
8)), Member registration section database The record of the corresponding member in FIG. 4 is deleted (step (7009)).

(16) Registration of Recruitment Information Delivered to Mobile Terminal FIG. 63 shows a procedure for registering recruitment information distributed from a business owner client to a member mobile terminal.
According to (9) the log-in procedure from the business owner client, the business owner client receives a processing menu screen.
Is displayed.

When the business owner selects “Registration of job information distribution” on the menu screen, a URL requesting display of a job information distribution screen is issued from the business owner client to the server (step (6611)). The server receives the URL, develops the distribution registration screen shown in FIG. 64 in HTML, and transmits it to the business owner client (step (7101)).

A job information distribution screen FIG. 64 is displayed on the business owner client. In the recruitment information distribution setting screen, the address, age, occupation type, whether or not to distribute to the working person of the member to be distributed, and the evaluation score described later for the distribution target person (member) are calculated and saved, It is possible to specify that this evaluation point should be sent only to people with a specific score or higher. The designated contents may include not only the contents described above, but also designations such as appearance and body type, designations such as required qualifications (ordinary license possession, bookkeeping class, etc.), gender, educational background, and the like.

Further, the contents of the work to be distributed include a work place, a work period, a work time, a work day, a salary / hourly wage,
The number of applicants can be entered. This input content may include not only the above-mentioned content but also input fields such as a break time, whether or not transportation expenses are provided, and detailed job contents. In addition, the salary / hourly wage amount is multiplied by a fixed ratio for each evaluation point described above, so that it is possible to set “evaluation point change” etc. so that salary information in distribution information can be set for each distribution member. May be.

Further, as a setting of the distribution date and time, whether or not to immediately distribute after the registration, distribution at a specific date and time, and a specification in case the distribution cannot be completed as scheduled due to congestion of the distribution route or system down, etc. It is possible to make settings such that distribution is not performed on the date and time.

After the business owner has input the necessary information and selects “distribution target list” on the registration screen shown in FIG. 64, the conditions set as the above-mentioned distribution target are transmitted from the business owner client to the server (step). (7106)), the server receives this, searches the member registration section database of all records in FIG. 4 and extracts members matching the distribution target conditions, and FIG.
It is developed on the distribution target member list screen shown in FIG. 5 and transmitted to the business owner client (step (7111)). When "Return" is selected on the screen in FIG. 65, the job information distribution screen shown in FIG. 64 is displayed again, and it becomes possible to re-enter or correct necessary items again.

Further, if "Exclusion" is checked for any member on the screen shown in FIG. 65 and "Exclusion Registration" is selected, the designated client ID is transmitted from the employer client to the server.
Is issued (step (7112)) requesting that the checked member be excluded from the distribution group of the job information to be registered this time (step (7112)), and the server distributes the corresponding data in the distribution information registration unit database in FIG. The flag is set to stop (step (7113)).

Further, when the member name shown in FIG. 65 is selected, a URL requesting the designated member ID and the member detail screen is issued from the employer client to the server (step (71)).
09)). The server receives the URL, extracts the data of the corresponding member from the member registration database (FIG. 4) using the ID as a key (step (7110)), and transmits the HTML of the member information screen shown in FIG. 60 (step (7111)). ) Is also possible.

After the business owner has input the necessary information and selects “distribution image” on the registration screen of FIG. 64, the content input as the content of the work to be distributed is transmitted from the business owner client to the server ( In step (7104), the server receives the request, generates a screen diagram 66 in accordance with the e-mail image to be transmitted to the member's portable terminal, develops it in HTML, and sends it to the employer client (step (7)).
105). A screen shown in FIG. 66 is displayed on the business owner client. When "Return" is selected on the screen in FIG. 66, the job information distribution screen shown in FIG. 64 is displayed again, and it becomes possible to re-enter or correct necessary items again.

After the business owner has input the necessary information and selects “Send” on the registration screen of FIG. 64, the input contents such as the above-mentioned distribution target, work content, distribution date and time are transmitted from the business owner client to the server. Then, the server receives this (step (7102)), secures a new record in the job registration unit database FIG. 5, and stores the received data (step (7103)).

The present system has a function of designating date and time of job offer information and transmitting it to a portable terminal of a specific distribution target person.
The urgent distribution as shown in FIGS. 67 and 68 is used when a large number of distribution registration contents are registered, distribution is to be performed prior to another distribution, or when a member wants to have a different image such as urgency. May be provided with a registration screen.

(17) Generation of Distribution Information by Distribution Information Generation Processing Unit FIG. 69 shows a procedure of generating distribution information. This processing unit generates digitized information to be actually distributed to the portable terminal based on the distribution destination conditions and the work information registered in the section (16). The data stored in the job registration unit database (FIG. 5) is periodically checked, and for items that are not generated and registered in the distribution information registration unit database (FIG. 6), the mobile terminal mail address of the delivery destination member that matches the delivery conditions With the destination as the destination, the salary amount and hourly wage are further calculated based on the evaluation points, incorporated into the body of the mail, and an e-mail in a format conforming to FIG. 66 or FIG. 68 is automatically generated for all members to be distributed. Then, the distribution information registration unit database is stored in FIG.

(18) Display of Registered Delivery Information by Business Client FIG. 70 shows a procedure for displaying a list of registered job information from a business client. In FIG. 44, when the “job information distribution registration list” is selected on the business owner menu screen, the business owner client
A URL requesting display of the job information distribution registration list screen is issued (step (6613)). The server receives the URL, obtains the distribution information from the distribution information registration unit database in FIG. 6, generates the screen shown in FIG. 71 as a distribution registration list (step (7201)), develops the screen in HTML, and transmits it to the business owner client (step (7202)).

(19) Change of setting conditions of registered distribution information by business owner client When "registration number" of any job information is clicked on the registration list screen of FIG. 71, the business owner client sends the registration number and distribution details to the server. A URL requesting a screen is issued (step (7205)). The server receives the URL, searches the job registration unit database in FIG. 5 using the registration number as a key, extracts the corresponding job information data, and transmits the HTML of the job information information registration screen shown in FIG. 64 (step (7206)). ). Subsequent processing executes the procedure of item (16) as necessary.

(20) Processing for Canceling Distribution of Registered Distribution Information by Employer Client When “Cancel” is checked for any job information on the registration list screen in FIG. 71 and “Distribution Cancel Registration” is selected, A delivery registration number of the checked job information and a delivery stop request URL are issued to the server (step (7203)). Upon receiving the request, the server sets the distribution flag to “stop” in all records of the distribution information in the distribution information registration unit database in FIG. 6 (step (7204)).

(21) Recruitment information distribution to portable terminal FIG. 72 shows the procedure of recruitment information distribution to the portable terminal. The information distribution processing unit of the server is cyclically activated. The information distribution processing unit extracts, from the calendar and clock information in the system server, data for which the registered distribution date and time has passed, from the distribution waiting information stored in the distribution information registration unit database FIG. (5701)), smtp (simple Mail
The mail is sequentially transmitted over an Internet line by a known protocol such as Transfer Protocol (Transfer Protocol). (Step (5702))

At this time, not only cases that have been successfully delivered, but also cases where mail transmission has failed, such as a delivery destination address error or a delivery server rejection of reception, the error status is added and the delivery result is added to the delivery result each time. It is stored in the storage unit database (FIG. 7). In addition, for a case in which reception of the distribution destination server is rejected, retransmission is repeated until the distribution suspension date and the distribution suspension time in the distribution information registration unit database in FIG. Regarding the case for which the series of distribution processing has been completed regardless of whether the distribution result is normal or abnormal, a completion flag is set in the distribution flag field of the distribution information registration unit database shown in FIG.

(22) Search / List / Individual Display of Delivery Completed Items by Business Owner Client FIG. 73 shows a procedure for confirming and displaying a delivery completed item from the business owner client. In FIG. 44, when the “delivery completed matter list” is selected on the business owner menu screen, the business owner client issues a URL requesting the server to display the distribution completed matter search screen (step (6615)). The server receives the URL and generates a delivery completed matter search screen shown in FIG. 74 (step (780)
1)), HTML development and transmission to the business owner client (step (7802)).

The business owner client displays a delivery completed matter search screen FIG. The business owner inputs various conditions to be searched according to the search conditions displayed on the screen. When "Send" is selected, the business owner client issues a delivery completed matter search condition and a URL requesting a search execution to the server (step (7803)).

The server receives the distribution completed matter search request,
Distribution result storage unit database FIG. 7 is searched under the designated condition (step (7804)), data matching the condition is developed on the distribution completed matter list screen in HTML, and transmitted to the business owner client (step (7805)). A delivery completed matter list screen FIG. 75 is displayed on the business owner client.

Further, in FIG. 75, when "*" for displaying detailed information on any completed matter is selected, a URL requesting the detailed information screen of the designated completed matter is transmitted from the business owner client to the server (step (step (1))). 780
6)). Upon receiving this request, the server further searches the distribution result storage unit database (FIG. 7), expands the detailed information on the distribution of the designated case on the distribution completed case detailed information screen shown in FIG. 76, and transmits it to the business owner client (step ( 780
8)).

(22) Retransmission setting of delivery time-out error matter by business owner client In FIG. 76, if “number” of “Number of items that could not be delivered due to timeout” is selected in the detailed information of the delivery completed case, the business owner client generates a timeout error. A URL requesting a list screen of members whose information could not be delivered is transmitted to the server (step (7809)). Upon receiving this request, the server searches the distribution result storage unit database (FIG. 7), extracts members whose information could not be distributed due to a timeout error in the designated distribution matter, and expands them on the distribution timeout error member list screen shown in FIG. 77. It is transmitted to the business owner client (step (7812)).

In FIG. 77, when "Name (Kanji)" is selected, the member ID specified by the employer client is transmitted, and a URL requesting the detailed member information screen is transmitted to the server (step (7810)). . Upon receiving this request, the server searches the member registration unit database of FIG.
The detailed information of the designated member is extracted, developed on the member information browsing screen shown in FIG. 60, and transmitted to the employer client (step (7813)).

On the list screen shown in FIG. 77, if “Resend” is checked for a member to be delivered again and “Resend” is selected, the member I checked by the employer client is checked.
D and the job information registration number are transmitted to the server (step (7811)), and the distribution flag storage field of the corresponding record in FIG. 6 of the distribution information registration unit database is rewritten to an undistributed state (step (7814)). In the retransmission process, the cyclically activated information distribution processing unit shown in (21) recognizes the data as having passed the registered distribution date and executes the retransmission process.

(23) Delivery Address Error Always Distribute Case Cancellation Setting FIG. 76 In the delivery completed matter detailed information, “number” of “Number of cases that could not be delivered due to unknown delivery destination e-mail address”
Is selected, the business owner client transmits a URL requesting a list screen of members whose information cannot be distributed due to unknown mail address to the server (step (781)
5)). Upon receiving this request, the server searches the distribution result storage unit database (FIG. 7), extracts members whose information cannot be distributed due to unknown e-mail addresses in the designated distribution case, and expands the distribution address error member list screen shown in FIG. 78. And sends it to the business owner client (step (781)
8)).

In FIG. 78, when "Name (Kanji)" is selected, the member ID specified by the employer client is transmitted, and a URL requesting the detailed member information screen is transmitted to the server (step (7816)). . Upon receiving this request, the server searches the member registration unit database of FIG.
The detailed information of the designated member is extracted, developed on the member information browsing screen shown in FIG. 60, and transmitted to the employer client (step (7819)).

On the list screen shown in FIG. 78, check "Cancel" for members whose distribution is to be stopped in the future, and select "Distribution stop registration". Is transmitted to the server (step (7817)), and the distribution flag storage field of the corresponding record in the member registration unit database in FIG. 4 is rewritten to the distribution suspended state (step (782)).
0)).

(24) Acceptance of Application from Portable Terminal FIG. 79 shows the procedure for accepting an application from a member portable terminal. According to (21) the procedure for distributing job information to the portable terminal, a job information mail FIG. 80 is transmitted to the portable terminal (step (5900)). At this time, an e-mail address specified as the application destination of the work information corresponding to the e-mail transmitted as the e-mail reply destination in FIG. 80 is set and transmitted. When the member requests application for the recruitment information by using the mail reply function attached to the portable terminal with the received e-mail, the e-mail is transmitted to the server (step (5901)), and the specified e-mail is stored in the server. It is stored in the area (step (5902)).

(25) Application Reception Processing Unit The job application reception processing unit of the server is cyclically activated. The recruitment application reception processing section sequentially retrieves the mail received and stored in the section (24) from the storage area (step (5903)), extracts the sender's mail address from the e-mail (step (5904)), and registers as a member. Search for the member ID that matches the relevant mail address from the department database Fig. 4 and apply for a job, along with information such as the date and time of mail reception, the area number where the mail is stored (work registration number), and reception from the member's mobile phone. A new record is secured and stored in the storage unit database FIG. 9 (step (5)
905)).

(26) Confirmation of Applicant from Employer Client FIG. 81 shows a procedure for confirming and registering the application status from the employer client. When "Applicant list" is selected in the business owner menu in FIG. 44, a URL is issued from the business owner client to the server requesting a screen for displaying a list of undecided cases (step (6612)). The server receives the URL, and from the job registration unit database FIG. 5, the case where the status of the employment decision flag field is undecided, and the distribution result storage unit database FIG. 7 and the job application storage unit database FIG.
The total number of cases to which the job registration numbers are linked is extracted (step (7401)), and the applicant confirmation screen is displayed.
Is generated, expanded in HTML, and transmitted to the business owner client (step (7402)).

[0116] The employer client has an applicant confirmation screen.
FIG. 82 is displayed. In FIG. 82, when the “number” in which the “number of applications” of each distributed case is calculated is selected, the business owner client transmits the work registration number of the selected case and the URL requesting the applicant list screen to the server. (Step 7403). The server receives this, and from the distribution result storage unit database FIG. 7 and the recruitment application storage unit database FIG.
The D number is extracted, and then the member registration database 4
The personal information of the corresponding member is extracted from, and the applicant list screen shown in FIG. 83 is generated by, for example, clearly indicating that the member who has already applied through the mobile terminal has applied (step (7404)). Step of expanding to HTML and transmitting to business owner client (7405)).

(27) Application registration agency and deletion of application registration from business owner client In the case where a member makes a request for application off-line, such as telephone or fax, check the “Application” column in FIG. 83. If you select "Apply Registration", the employer client will check the member ID, job registration number,
And a URL requesting applicant registration is issued. Upon receipt of this, the server secures and stores a new record in the application storage section database together with information such as the received member ID, job registration number, reception date and time, and registration from the business owner client.

In FIG. 83, when the "Application" column is unchecked and "Application registration" is selected, the employer client deletes the unchecked member ID, job registration number, and applicant registration. Issue a URL.
The server receives this, and searches the applicable record in the application storage unit database FIG. 9 based on the received member ID and job registration number, and performs a deletion process.

(28) Manual Recruitment Decision from Business Owner Client FIG. 85 shows a procedure for manually recruiting a job applicant from a business owner client. When "employee decision" is selected on the employer menu in FIG. 44, the employer client issues a URL to the server requesting a screen displaying a list of undecided cases (step (6616)). The server receives the URL, and from the job registration unit database in FIG. 5, the job registration status field is undecided, and the job result is registered in the distribution result storage unit database in FIG. 7 and the job application storage unit database in FIG. The total number of cases to which the numbers are linked is extracted, and an employer confirmation screen FIG. 86 is generated (step (7301)), expanded to HTML, and transmitted to the employer client (step (7302)).

In FIG. 86, when the “number” for which the “number of applications” of each distributed case is calculated is selected, the business owner client inputs the job registration number of the selected case and the URL requesting the applicant list screen. It is transmitted to the server (step (7303)). The server receives this, extracts the member ID number to which the job registration number is linked and the application is registered, from the distribution result storage unit database FIG. 7 and the job application storage unit database FIG. 9, and then extracts the member registration database unit. Then, the personal information of the member is extracted from No. 4, and a recruiting member selection screen shown in FIG. 87 is generated (step (7304)), developed into HTML, and transmitted to the employer client (step (7305)).

In FIG. 87, when the employer checks the “employee” column for the member he / she wants to adopt and selects “employ decision”, the employer client selects the I
D, a job registration number, and a URL requesting an employment registration list screen are issued (step (7306)). The server receives the information, and secures and stores new records in the employer storage unit database FIG. 8 together with the received information such as the member ID, the job registration number, and the date and time of application (step (7307)). Further, the recruiting member determination screen shown in FIG. 88 is generated (step (7310)), developed into HTML, and transmitted to the employer client (step (731)).
1)). When "return" is selected in FIG.
Is displayed again, and re-registration of the recruiter is enabled.

In FIG. 88, when “delivery image” is selected, the business owner client issues a URL requesting an employment decision mail distribution image screen together with the job registration number. The server receives the job registration number, extracts the detailed information of the job to be hired from the job registration unit database in FIG. 5 based on the received job registration number, generates an employment determination notification e-mail image screen shown in FIG. Send to

In FIG. 88, when “employment information distribution” is selected, the business owner client issues a URL requesting execution of the employment decision mail distribution together with the job registration number. The server receives this and searches the employer storage unit database (FIG. 8) based on the received job registration number, and extracts the ID of the member whose employment is determined. Further, the member registration unit database FIG. 4 is searched based on the main member ID, and the e-mail address of the member who has been determined to be employed is set as a destination. The detailed information is extracted, and a recruitment notice mail shown in FIG. 89 is created for each recruiting member.
(Step (7308)). At this time, the distribution date is registered as the same day. In the transmission processing, the cyclically activated information distribution processing unit shown in (21) recognizes the registered distribution date and time as data having the same date and executes the transmission processing (step (730)
9)).

When the transmission process is executed, the working flag field value of the member registration unit database in FIG. 4 is updated to “working” based on the member ID that has been adopted. Further, both fields of the adoption decision flag and the distribution completion flag of the job registration unit database in FIG. Also, the recruitment contact field in FIG. 8 of the recruiter storage unit database is updated to “transmitted”.

(29) Automatic Recruitment Decision from Employer Client FIG. 91 shows an automatic recruitment decision procedure for a job applicant from a business owner client. In FIG. 87, when “automatic recruitment determination” is selected, the employer client requests the job registration number and the automatic recruitment determination.
RL is issued (step (7900)). The server receives the job registration number and searches the recruitment application storage unit database FIG. 9 based on the received job registration number, extracts the member ID registered for the target job, and registers as a member based on the main member ID. Department database After searching FIG. 4 and automatically determining the hiring order in descending order of the evaluation points (step (790)
1)), the prescribed information is stored in the employer storage unit database.
New records are secured and stored (step (7902)).

Further, the recruiting member determination screen shown in FIG. 88 is generated (step (7903)), developed into HTML, and transmitted to the employer client (step (790)
4)). When "return" is selected in FIG.
Is displayed again, and re-registration of the recruiter is enabled. Furthermore, as described in the manual recruitment decision section (28), the recruiter is notified by e-mail. (Since this processing is equivalent to the processing described in (28), description thereof will be omitted (step (79)
05-7906)). As described above, the method of automatically determining a recruiter may be in the order of evaluation points, age, total working hours, or salary. This determination criterion may be programmed so that it can be selected immediately after selecting "automatic determination of recruiting members" as necessary.

(30) Registration of Working Hours from Mobile Terminal FIG. 92 shows a procedure for registering working hours from the mobile terminal. When "working time registration" is selected in FIG. 27, a screen display request URL and a member ID relating to working time registration are transmitted from the portable terminal to the server (step (5210)). The server obtains the date at the time of access from the system internal calendar, generates the working hour registration screen shown in FIG.
L and transmits to the mobile terminal (step (620)
1)).

On the work time registration screen displayed on the portable terminal, the member inputs the date, working time, etc., and then clicks "send".
The URL requesting the working hour registration is transmitted to the server (step (6202)).

Using the received member ID as a key, the server searches the employer storage unit database FIG. 8 and extracts the work registration number of the member who works. Thereafter, the work time registration unit database FIG. 10 is searched using the member ID, the work registration number, and the work time as keys. If the corresponding record does not exist in the working time registration section database, a new record is added and the registration data is stored. If there is already registered data, a screen indicating that the data has already been registered is developed in HTML and transmitted to the portable terminal (FIG. 9).
4). In FIG. 94, when “overwrite registration” is selected, the server overwrites and registers the already registered record.
When the registration is completed, a work time registration confirmation screen shown in FIG. 95 is generated and transmitted to the portable terminal. At this time, the total working hours of the current month and the current total of salary and hourly wage may be calculated each time and displayed on the confirmation screen.

(31) Working Time Registration from Member Client FIG. 96 shows a working time registration procedure from a member client. When "working time registration" is selected in FIG. 33, a screen display request URL relating to working time registration and a member ID are transmitted from the member client to the server (step (5410)). The server obtains the working month at the time of access from the internal calendar of the system, searches the recruiter storage unit database FIG. 8 using the received member ID as a key, and extracts the work registration number of the member who works. Thereafter, using the member ID, the work registration number, and the work registration month as keys, the work time registration section database 10
Search for. Based on the search result, a work time registration screen shown in FIG. 97 is generated, developed into HTML, and transmitted to the member client (step (6302)).

On the work time registration screen displayed on the member client, the member inputs the work day / work time, work place, etc., and then clicks “Register”. The registration number and the URL requesting the working time registration are transmitted to the server (step (6303)).

The server searches the working hour registration section database FIG. 10 using the received member ID, job registration number, and working month as keys. If the corresponding record does not exist in the working time registration section database, a new record is added and the registration data is stored. If there is already registered data, a screen for specifying that the data has already been registered is developed in HTML and transmitted to the member client (FIG. 9).
8). In FIG. 98, when “overwrite registration” is selected, the server overwrites the already registered record.
Further, when the registration is completed, the total working hours of the current month and the current total of salary and hourly wage are calculated each time, and the working time registration screen shown in FIG. 97 is regenerated, expanded to HTML, and transmitted to the member client.

(32) Registration of Working Hours from Business Owner Client When “Working Hours Registration” is selected in FIG. 44, the URL for requesting the server from the business owner client to the server to search for a member for registering working hours is displayed. publish. Since the main member search is the same as the procedure of the item (12), the description is omitted. In addition, the subsequent work hours registration means,
The description is omitted because it is the same as the working time registration means from the member client in the section (31).

(33) Registration of Transportation Expenses from Portable Terminal FIG. 101 shows a procedure for registering transportation expenses from a portable terminal. When "traffic expense registration" is selected in FIG. 27, a screen display request URL and a member ID relating to the travel expense registration are transmitted from the portable terminal to the server (step (5209)). The server obtains the date of the access day from the internal calendar of the system, generates the transportation expense registration screen shown in FIG.
And send it to the mobile terminal (step (640)
1)).

On the transportation expense registration screen displayed on the mobile terminal, the member inputs the date, type, boarding station, getting off station, amount, etc., and then clicks "Send". The ID and the URL requesting the transportation expense registration are transmitted to the server (step (6402)).

Using the received member ID as a key, the server searches the employer storage unit database FIG. 8 and extracts the job registration number of the member who works. Then, the transportation expense registration unit database FIG. 11 is searched using the member ID, the job registration number, and the date as keys. If the corresponding record does not exist in the transportation expense registration unit database, a new record is added and the registration data is stored. If there is already registered data, a screen indicating that the data has already been registered is developed in HTML and transmitted to the portable terminal (FIG. 103). In FIG. 103, when “overwrite registration” is selected, the server overwrites a registered record. When the registration is further completed, a transportation expense registration confirmation screen shown in FIG. 104 is generated and transmitted to the portable terminal. At this time, the total amount of the travel expense application for the month may be calculated each time and displayed on the confirmation screen.

(34) Registration of Transportation Expenses from Member Client FIG. 105 shows a procedure of registration of transportation expenses from a member client. When "traffic expense registration" is selected in FIG. 33, the screen display request URL and the member ID relating to the travel expense registration are transmitted from the member client to the server (step (5409)). The server obtains the working month at the time of access from the internal calendar of the system, searches the recruiter storage unit database FIG. 8 using the received member ID as a key, and extracts the work registration number of the relevant member to work. Then, the transportation expense registration unit database in FIG. The transportation expense registration screen shown in FIG. 106 is generated based on the search result, developed into HTML, and transmitted to the member client.

On the transportation expense registration screen displayed on the member client, the member inputs the date of occurrence, type, boarding station, getting off station, amount, etc., and then clicks "Send". The member ID, the job registration number, and the URL requesting the transportation expense registration are transmitted to the server (step (6503)).

The server searches the transportation expense registration section database FIG. 11 using the received member ID, job registration number, and work date as keys. If the corresponding record does not exist in the transportation expense registration unit database, a new record is added and the registration data is stored. If there is already registered data, a screen that clearly indicates that
TML expansion and transmission to the member client (FIG. 10)
7). In FIG. 107, when “overwrite registration” is selected, the server overwrites the already registered record. Further, when the registration is completed, the total amount of the travel expense application for this month is calculated each time, and the travel expense registration screen shown in FIG. 106 is regenerated, expanded to HTML, and transmitted to the member client.

(35) Registration of Transportation Expenses from Employer Client When “Travel Expense Registration” is selected in FIG. 44, the URL for requesting a screen for searching for members to register transportation expenses from the employer client to the server is displayed. publish. Since the main member search is the same as the procedure of the item (12), the description is omitted. Further, the transportation expense registration means thereafter is (34)
The description is omitted because it is the same as the means for registering transportation expenses from the member client in the section.

(36) Salary Calculation and Mail Transmission of Salary Details FIG. 108 shows the procedure when the employer calculates the salary of a worker. When "payroll calculation" is selected in FIG. 44, the business owner client requests the server for a screen for searching for job registration information for performing payroll.
RL is issued (step (6617)). The server receives the URL, and from the working hour registration section database FIG. 10, the transportation expense registration section database FIG. 11, the recruitment storage section database FIG. 8, and the member registration section database FIG.
The member ID, name, mobile terminal e-mail address, salary hourly salary, salary / hourly salary identification flag, transportation expense payment identification flag, total working hours in the total month, accumulated transportation expense, etc. are retrieved and totaled (step (7501)). Then, a screen for displaying a list of currently working members is generated, developed in HTML, and transmitted to the employer client (step (7502)).

The employer client displays an employee list screen (FIG. 109). The salary calculation process has the same function as the well-known salary calculation program, and if the calculation target cannot be displayed on one screen, search and narrow down can be performed before displaying the list screen May be included. The calculated salary data is
It is stored in the salary data storage unit database FIG. 12 (step (7503)). Further, the salary data may be generated and developed in an electronic mail and transmitted to the member.

(37) Calculation of Evaluation Points The cumulative hours of working hours are calculated for each member, or the evaluation values obtained by dividing the attendance information, customer evaluations, etc. into 10 levels are timely calculated and stored in the member registration database. By this, (1
6) When registering job information to be distributed to a mobile phone, it is possible to automatically change salaries and hourly wage amounts according to evaluation points, determine automatic adoption of item (29), and the like. As a calculation standard for the evaluation points, a database may be separately attached, or a table may be fixedly provided.

As described above, according to the present invention, applicants for employment are recruited in real time, and an intermediary directly informs the area and time desired by the employment without being in front of the terminal, and A system that allows employees to receive the desire to work, and reports on work hours and work contents using a portable terminal device, such as a portable terminal, that allows workers working in each store to stop at an office or the like Can be provided.

[Brief description of the drawings]

[Fig. 1] Overall configuration diagram of human resource utilization system

Fig. 2 Human resource utilization system System block diagram

FIG. 3 shows an example of a recruiting company registration department database

FIG. 4 is an example of a member registration section database

FIG. 5 shows an example of a job registration unit database

FIG. 6 is an example of a distribution information registration unit database;

FIG. 7 is an example of a distribution result storage unit database;

FIG. 8 shows an example of an employer storage unit database

FIG. 9 shows an example of a job application storage database

FIG. 10 is an example of a working hour registration section database

FIG. 11 is an example of a transportation expense registration section database

FIG. 12 is an example of a salary data storage unit database

FIG. 13 Member registration procedure from a mobile terminal

FIG. 14 is a gate screen for a member on a mobile terminal.

FIG. 15 is a member registration screen from a mobile terminal (part 1).

FIG. 16 is an example of a member registration confirmation e-mail sent to a mobile terminal.

FIG. 17 is a member registration screen from a mobile terminal (part 2)

FIG. 18 is an example of a registration confirmation mail sent to a mobile terminal.

FIG. 19: Member registration procedure from a member client

FIG. 20: Gate screen from member client

FIG. 21: Member registration screen from member client

FIG. 22: Member registration confirmation screen from member client

FIG. 23: Member registration result display screen from the member client

FIG. 24: Member login procedure from a mobile terminal

FIG. 25: Member login screen from mobile terminal

FIG. 26 is a login error screen for a portable terminal.

FIG. 27 is a menu screen after a member logs in from a mobile terminal.

FIG. 28: ID / password retransmission procedure from mobile terminal

FIG. 29 is an example of an ID / password notification e-mail sentence to a portable terminal.

FIG. 30: Member login procedure from member client

FIG. 31: Member login screen from member client

FIG. 32: Member login error screen to member client

FIG. 33: Menu screen after login from member client

FIG. 34: Procedure for resending ID / password from member client

FIG. 35: Procedure for changing member registration contents from a mobile terminal

FIG. 36: Member registration content change screen from mobile terminal

FIG. 37 is an example of a registration content change confirmation e-mail sent to a mobile terminal.

FIG. 38: Procedure for changing member registration contents from a member client

FIG. 39: Member registration content change screen from the member client

FIG. 40: Login procedure 1 from the business owner client

FIG. 41: Gate screen from business owner client

FIG. 42: Login screen from the business owner client

FIG. 43: Employer Login Error Screen to Employer Client

FIG. 44: Menu screen after login from the business owner client

FIG. 45: Password retransmission procedure at the time of login by the business owner client

FIG. 46 is an example of an e-mail text for notification of an ID / password to a business owner client.

FIG. 47: Member registration procedure from the business owner client

FIG. 48: Member registration menu screen from the business owner client

FIG. 49: Member registration screen from business owner client

FIG. 50: Member registration confirmation screen to the business owner client

FIG. 51: Member registration result display screen for business owner client

FIG. 52: Membership batch registration procedure from the business owner client

FIG. 53: Member file upload screen from the business owner client

FIG. 54: Member file selection screen from business owner client

FIG. 55: Member file upload confirmation screen from business owner client

[Fig. 56] An example of a member file upload completion notification e-mail sent from the business owner client.

[Fig. 57] Member search / list /
Individual display / change procedure

FIG. 58: Member list display search screen from the business owner client

FIG. 59: Member list search result screen from business owner client

FIG. 60: Member information browsing screen from business owner client (part 1)

FIG. 61: Member information browsing screen from business owner client (part 2)

FIG. 62 is a procedure for changing member information settings from a business owner client.

FIG. 63: Procedure for registering job information to be delivered to a mobile terminal

FIG. 64: Job information distribution screen (for normal distribution)

[Fig. 65] Distribution target member list screen

FIG. 66: Job information delivery mail image screen (for normal delivery)

FIG. 67: Job information distribution screen (for emergency distribution)

FIG. 68: Job information delivery mail image screen (for emergency delivery)

FIG. 69 is a procedure for generating distribution information.

FIG. 70: Job information list / status change procedure

FIG. 71 is a distribution list screen

FIG. 72: Procedure for distributing recruitment information to a mobile terminal

[FIG. 73] Confirmation display processing procedure 1 of delivery completed matter

FIG. 74: Delivery completed matter search screen

[FIG. 75] Delivery completed matter list screen

FIG. 76: Delivery completed matter detailed information screen

Fig. 77: Delivery timeout error member list screen

FIG. 78: Distribution address error member list screen

FIG. 79: Application acceptance procedure from a mobile terminal

FIG. 80: Job information email sent to mobile terminal

[Fig. 81] Procedure for confirming application status from business owner client

FIG. 82: Applicant confirmation screen for job information

FIG. 83: Applicant list screen for job offer information

FIG. 84: Login procedure 2 from the business owner client

FIG. 85: Manual recruitment decision procedure from the business owner client

[Fig. 86] Recruiting member confirmation screen

FIG. 87: Hiring Member Selection Screen

FIG. 88: Hiring member decision screen

[Fig. 89] Image screen of recruitment notice mail

[FIG. 90] A procedure for sending an employer decision notification mail

FIG. 91: Automatic employment decision processing procedure

FIG. 92 A work time registration procedure from a mobile terminal

FIG. 93: Working hour registration screen from a mobile terminal

FIG. 94: Work-hour re-registration confirmation screen from the mobile terminal

FIG. 95: Screen for confirming working hours registration from a mobile terminal

FIG. 96 Procedure for registering working hours from a member client

[Figure 97] Working hour registration screen from member client

[Figure 98] Screen for re-registering working hours from member client

[FIG. 99] Confirmation display processing procedure 2 of delivery completed matter

FIG. 100: Transportation expense registration processing

FIG. 101: Transportation expense registration procedure from a mobile terminal

Fig. 102: Transportation expense registration screen from mobile terminal

FIG. 103: Transportation expense re-registration confirmation screen from mobile terminal

FIG. 104: Transportation expense registration confirmation screen from mobile terminal

[Fig. 105] Transportation expense registration procedure from member client

FIG. 106: Registration screen for transportation expenses from a member client

Fig. 107: Confirmation screen of re-registration of transportation expenses from member client

FIG. 108: Payroll calculation processing

[Figure 109] Employer list screen

[Explanation of symbols]

 11. 11. Human resource utilization system Business client machine 13. Member client machine 14. 14. Server machine for data relay to mobile terminal Member mobile terminal 16. Internet 17. Electronic information 111. Human resource utilization system server machine 112. Human resource utilization system input / output device 113. Human resource utilization system database

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] November 1, 2000 (200.11.
1)

[Procedure amendment 2]

[Document name to be amended] Drawing

[Correction target item name] All figures

[Correction method] Change

[Correction contents]

FIG.

FIG. 7

FIG. 8

FIG. 9

FIG.

FIG. 2

FIG. 16

FIG. 26

FIG. 3

FIG. 4

FIG. 5

FIG. 6

FIG. 10

FIG. 11

FIG.

FIG. 13

FIG.

FIG. 14

FIG.

FIG.

FIG. 23

FIG. 27

FIG.

FIG. 54

FIG. 74

FIG. 80

FIG. 21

FIG.

FIG. 28

FIG. 29

FIG. 69

FIG. 24

FIG. 95

FIG. 103

FIG. 25

FIG. 31

FIG. 32

FIG. 33

FIG. 34

FIG.

FIG. 56

FIG. 98

FIG. 104

FIG. 35

FIG. 107

FIG. 36

FIG. 37

FIG. 41

FIG. 42

FIG. 93

FIG. 38

FIG. 39

FIG. 43

FIG. 45

FIG. 40

FIG. 46

FIG. 48

FIG. 44

FIG. 47

FIG. 49

FIG. 50

FIG. 51

FIG. 53

FIG. 52

FIG. 55

FIG. 58

FIG. 59

FIG. 60

FIG. 57

FIG. 61

FIG. 64

FIG. 65

FIG. 67

FIG. 62

FIG. 63

FIG. 66

FIG. 68

FIG. 71

FIG. 75

FIG. 70

FIG. 72

FIG. 73

FIG. 76

FIG. 77

FIG. 78

FIG. 82

FIG. 79

FIG. 81

FIG. 83

FIG. 86

FIG. 87

FIG. 88

FIG. 84

FIG. 85

FIG. 89

FIG. 94

FIG. 109

FIG. 90

FIG. 91

FIG. 92

FIG. 96

FIG. 97

FIG. 102

FIG. 106

FIG. 99

FIG. 100

FIG. 101

FIG. 105

FIG. 108

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Yuji Suzuki 2-5-18 Choja-cho, Naka-ku, Yokohama-shi, Kanagawa F-term in Nucleus Co., Ltd. 5B049 BB00 CC02 CC33 CC36 DD01 DD05 EE01 EE05 EE23 FF03 FF04 FF09 GG04 GG07

Claims (29)

[Claims] 1. A storage device for storing job information, (2) a registration device for registering job seeker information, and (3)
Job recruitment information stored in the storage device, by comparing the job recruiter information registered in the registration device, by selecting means for selecting job applicants that match the employment conditions of the job recruitment information, In a human resource utilization system connectable to a network, the job seeker information includes a unique identification code of a communication device owned by the job seeker connectable to the network, wherein the human resource utilization system comprises: Automatically in the form of digitized information via the network to the communication device of the job seeker selected by the selection means based on the unique identification code. 2. The human resource utilization system according to claim 1, wherein the recruiter can access the human resource utilization system from a terminal device connectable to the network. 3. The recruiter according to claim 2, wherein the recruiter can access the human resource utilization system from the terminal device and store the recruitment information in the storage device. Human resource utilization system. 4. The human resource utilization system according to claim 1, wherein the job seeker can access the human resource utilization system from the communication device. 5. The human resource according to claim 4, wherein the job seeker can access the human resource utilization system from the communication device and register the job seeker information in the registration device. Resource utilization system. 6. The human resource utilization system according to claim 1, wherein the job seeker can access the human resource utilization system from a terminal device connectable to the network. 7. The job seeker according to claim 6, wherein the job seeker can access the human resource utilization system from the terminal device and register the job seeker information in the registration device. Human resources utilization system. 8. The job seeker accesses the human resource utilization system and executes at least one of an operation of changing the content of the job seeker information already registered in the registration device and an operation of deleting the job seeker information. The human resource utilization system according to any one of claims 1 to 7, wherein the human resource utilization system is enabled. 9. The human resource utilization system operator can access the human resource utilization system from a terminal device of the network and register a job seeker in the registration device. The human resource utilization system according to any one of claims 1 to 8, wherein: 10. An operator of the human resource utilization system, wherein at least one of an operation of changing and deleting job recruitment information distributed to a portable terminal device of a job seeker from the terminal device. 10. The human resource utilization system according to claim 9, wherein: 11. The human resource utilization system according to claim 1, further comprising storage means for storing work evaluation data for each job seeker. 12. The human resource utilization system according to claim 11, wherein an employer can store work evaluation data in said storage means from a terminal device connectable to said network. 13. A work evaluation data generating means for generating work evaluation data based on a past work situation for each job seeker and storing the work evaluation data in the storage means, wherein the job offer information is selected with respect to work evaluation data. Has reference information,
12. The human resource according to claim 11, wherein the selection unit selects a job seeker based on the job evaluation data for each job seeker stored in the storage unit and the selection criterion information. Utilization system. 14. A system according to claim 11, further comprising: a storage unit for storing information on the employment status of the job seeker, wherein job information is distributed to the job seeker selected by the selection unit based on search data of the storage unit. 14. The human resource utilization system according to claim 1, wherein the job information distribution operation to the job seeker is automatically stopped. 15. The job recruiter can reply to the recruiting information delivered to the communication device of the job applicant by the communication device to the human resource utilization system using the communication device. 15. The human resource utilization system according to any one of 1 to 14. 16. The human resource utilization system according to claim 15, further comprising a storage device for storing applicant information created based on the application information returned to the human resource utilization system. . 17. An employer accesses a human resource utilization system from a terminal connectable to the network and browses the applicant information stored in the storage device, thereby making a decision on recruitment / non-recruitment. 17. The human resource utilization system according to claim 16, wherein the human resource utilization system is possible. 18. The system according to claim 16, further comprising: an automatic recruiting device for automatically recruiting a recruiter based on the work evaluation data from the applicant information stored in the storage device. 18. The human resource utilization system according to item 17. 19. The human resource utilization system according to claim 17, further comprising a registration unit for registering working time data of a person who has been employed and employed. 20. The apparatus according to claim 19, wherein the worker can access the human resource utilization device via the network and register working time data in the registration unit. Human resource utilization system. 21. The utilization of human resources according to claim 1, further comprising a storage unit for storing data for adjusting a transportation cost required for a worker to commute to work. system. 22. Further, it is possible for the worker to access the human resource utilization system and store data for adjusting the transportation expenses in the storage unit, thereby enabling the transportation expenses to be settled. The human resource utilization system according to claim 21, wherein: 23. The human resource utilization system according to claim 1, wherein said communication device is a terminal device of said network. 24. The communication device is portable,
24. The human resource utilization system according to claim 23, wherein the system is connectable to the network via wireless communication. 25. The human resource utilization system according to claim 1, wherein the network is the Internet. 26. The human resource utilization system according to claim 25, wherein said digitized information is an Internet electronic mail, and said unique identification code is an electronic mail address of a communication device. . 27. The human resource utilization system according to claim 25, wherein the communication device is a mobile phone connectable to the Internet. 28. The recruiting information distributed to the communication device of the job seeker includes a link destination of at least one of the Internet home page held by the employer and the Internet home page held by the human resource utilization system operator. The human resource utilization system according to any one of claims 25 to 27, wherein the system is inserted and displayed. 29. The recruiting information distributed to the communication device of the job seeker includes a link destination of at least one of the Internet homepage held by the employer and the Internet homepage held by the human resource utilization system operator. The human resource utilization system according to any one of claims 25 to 27, wherein the system is automatically inserted.