JP2019082802A - Attendance-leaving management system and program - Google Patents

Abstract

To register the attendance and leaving of employees easily at low cost.SOLUTION: An attendance-leaving management system S registers attendance-leaving information of inputs of attendance and leaving received by a plurality of attendance-leaving registration terminals 1 into a cloud server 2 connected to the attendance-leaving registration terminals 1a to 1c for communication. The attendance-leaving management system S includes management means for registering at least a part of the master information of each subject, whose attendance-leaving information is a registration target, into the attendance-leaving registration terminals 1a to 1c and the cloud server 2, as shared information. The management means registers authentication information to be referred to for input of attendance and leaving so that an attendance-leaving registration terminal 1 allocated to the subject who corresponds to the authentication information will be the only registration destination among the attendance and leaving registration terminals 1a to 1c when the authentication information is registered in relation to the shared information on a subject-to-subject basis as another part of the master information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a time and attendance management system and program.

  A time recorder is an instrument that measures time and time, and is often used for employee attendance management and the like. Conventionally, when using a time recorder for attendance management, a paper card called a time card has been used as a recording medium. By inserting the time card into the time recorder, the time of insertion is printed on the spot, and the time of attendance or leaving is recorded. It is called stamping that a time recorder records time like this. The time recorder is configured to record, for example, one month's worth of attendance information (time to work, time to work, etc.) of each employee with one time card.

  In recent years, time recorders using biometric authentication methods such as fingerprints and finger veins instead of time cards, and time recorders using an authentication method using IC (integrated circuit) cards and IC tags have appeared. For example, Japanese Patent Application Laid-Open Publication No. 2008-101501 is an employee who acquires identification information from an IC card of an employee by an engraving terminal and transmits the acquired identification information to a attendance information management server to identify an employee and perform certification. Management system is described.

JP, 2016-57661, A

However, in the invention described in Patent Document 1, it is assumed that the stamping terminal is communicably connected to the attendance information management server via the network, and identification information acquired by the stamping terminal is used. All employee certification is based on the attendance information management server. In such a configuration, there is a problem that attendance can not be registered at all when the connection between the stamping terminal and the attendance information management server is offline.
In order to solve this problem, a configuration is also considered in which identification information of the employee stored in the attendance information management server is also stored as shared information in the stamping terminal and authentication is performed on the stamping terminal side. Be However, in the attendance management system, one attendance information management server as described in Patent Document 1 communicates with a plurality of stamping terminals installed for each work location, and the attendance of a plurality of work locations It is known to perform management centrally. Therefore, when storing identification information in each stamping terminal, it is necessary to manage these identification information appropriately so that inconsistency does not occur between the attendance information management server and each stamping terminal.

  Then, this invention makes it a subject to manage appropriately the authentication information required at the time of attendance registration about an attendance control system and a program.

The present invention achieves the above object by
It is a time and attendance management system for registering time and attendance information for which time and work input is accepted by the local device in a cloud server communicably connected to a plurality of local devices,
The system further comprises a management unit that registers at least a part of the master information of each target person who is the registration target of the time and attendance information as shared information in the plurality of local devices and the cloud server.
When the management means registers authentication information to be referred to at the time of work-and-work input in association with the shared information for each of the target persons as another part in the master information, the plurality of local devices In the above, the authentication information is registered such that the local device assigned to the target person corresponding to the authentication information is limited as a registration destination.

  According to the present invention, it is possible to appropriately manage authentication information required at the time of attendance registration.

It is a general | schematic block diagram which shows the system of this embodiment. It is a general | schematic block diagram which shows a time-of-work registration terminal. It is a general | schematic block diagram which shows the system of this embodiment. It is a figure showing an example of an employee master. It is a figure which shows an example of an affiliation master. It is a figure which shows an example of a work attendance history information table. It is a figure which shows the login screen of a time and attendance registration terminal. It is a figure which shows the time-of-work registration screen of an offline state. It is a figure which shows the state as which "work attendance" was selected among work attendance. It is a figure which shows the external appearance of the state before an IC card is touched. It is a figure which shows the external appearance of the state after an IC card was touched. Furthermore, it is a figure which shows the state in which the IC card was touched and the time-as-you-go registration was performed. It is a figure which shows the state in which the employee number is input in the time-as-a-time registration screen. Furthermore, it is a figure which shows the state in which the PIN code is input. It is a figure which shows the state in which the PIN was correctly input and the input of the employee number was received. It is a figure which shows the state as which "work attendance" was selected among work attendance. It is a figure which shows the state in which attendance registration was performed. It is a figure which shows the state in which the same type attendance and absence registration was performed continuously. It is a figure which shows an employee selection area when "select by number" is selected. It is a figure which shows an employee selection area when "select by name" is selected. 5 is a flowchart of synchronization processing. It is a flowchart (the 1) regarding operation of a time-and-time job registration screen. It is a flowchart (part 2) regarding operation of a time and attendance registration screen. It is a flowchart (the 1) of affiliation determination processing. It is a flowchart (the 2) of affiliation determination processing. It is a flowchart of an employee information determination process. It is a flow chart of time and attendance registration processing in the online state. It is a flowchart of the attendance and leaving work registration process in the offline state. It is a figure which shows the PIN code registration screen in which the employee number is being input. It is a figure which shows the PIN code registration screen in which the PIN code is being input. It is a figure which shows a PIN code registration screen when registration is completed. It is a flow chart which shows personal identification number registration processing. It is a figure which shows the PIN code cancellation | release screen which is inputting the employee number. It is a figure which shows the PIN code cancellation | release screen which is displaying the message for confirmation. It is a figure which shows a PIN-code cancellation | release screen when complete | finishing cancellation | release. It is a flowchart which shows a PIN number cancellation | release process. It is a figure which shows the IC card registration screen which is inputting the employee number. It is a figure which shows the IC card registration screen which is displaying the warning message which urges to touch registered IC card. It is a figure which shows the IC card registration screen which is displaying the message which prompts to touch the IC card newly registered. It is a figure which shows an IC card registration screen when registration is completed. It is a flowchart which shows IC card registration processing. It is a figure which shows the IC card cancellation | release screen which is inputting the employee number. It is a figure which shows the IC card cancellation | release screen which is displaying the message of confirmation. It is a figure which shows an IC card cancellation | release screen when complete | finishing cancellation | release. It is a figure which shows an IC card cancellation | release screen when IC card is not registered. It is a flow chart which shows IC card cancellation processing. It is a figure which shows an example of the employee master of a modification. 5 is a flowchart of synchronization processing.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a schematic configuration diagram showing a time and attendance management system S of the present embodiment, which is an example of a time and attendance management system.
The time and attendance management system S operates by causing the time and attendance registration program to operate on the time and attendance registration terminal (local apparatus) 1a to 1c and mutually communicating with the cloud server 2 (server apparatus). The time-entry register terminals 1a to 1c are local devices that receive time-entry input. The plurality of time and attendance registration terminals 1 a to 1 c are communicably connected to the cloud server 2. In addition, when not distinguishing each time-of-work registration terminal 1a-1c, it only describes with the time-of-work registration terminal 1. FIG.

The attendance and registration terminal 1a is a terminal which is installed at the Kasumigaseki branch and mainly registers the attendance and leaving of the employees belonging to the Kasumigaseki branch. The on-time work registration terminal 1b is a terminal that is installed at the Toranomon branch and mainly registers the on-time and off-time of an employee who belongs to the Toranomon branch. The time and attendance registration terminal 1c is a terminal which is installed at a Kudan branch and mainly registers the attendance and departure of employees belonging to the Kudan branch. In each time-of-day registration terminal 1, it is set in advance at which branch the self has been installed. Although details will be described later, the time and attendance registration terminal 1 installed one by one in each branch not only registers the attendance and departure of the employee belonging to the branch but also the attendance and departure of an employee belonging to another branch It is also possible to register. For example, when an employee temporarily goes to work at another branch due to a business trip or the like, the employee can register for going on / off using the attendance registration terminal 1 installed at the branch. .
In the service provided by the time and attendance management system S, registered time and attendance information is displayed on the employment record screen of the cloud server 2 in a unit of affiliation. The registration of time and attendance information is performed by the time and attendance registration terminals 1a to 1c executing a time and attendance registration program.

  The cloud server 2 stores an employee master 23, an affiliation master 24, an employment basic information table 25, a time card table 26, a time and attendance registration terminal table 27, and an employment record table 28 in a storage unit (not shown). The cloud server 2 further causes the synchronization unit 21 and the time setting unit 22 to function by a CPU (Central Processing Unit) (not shown) executing a time and attendance management program.

The employee master 23 is a database that manages information on all employees belonging to each branch.
The affiliation master 24 is a database that manages information on the affiliation of all employees belonging to each branch.
The work basic information table 25 is a database for managing basic work information. Specifically, it is a database that manages information and the like for enabling the time and attendance information registered by the time and attendance registration terminals 1a to 1c to be displayed on an employment result screen of the cloud server 2 in a unit of affiliation.
The time card table 26 stores the time and attendance information transmitted from the time and attendance registration terminal 1. In the time card table 26, time-of-work information and code information of a branch office to which an employee who has performed time-of-work registration has been registered are stored in association with each other.

The time and attendance registration terminal table 27 is a database for storing information related to each time and attendance registration terminal 1. The cloud server 2 excludes registration of unauthorized attendance and attendance information by excluding access from terminals not recorded in the attendance and attendance registration terminal 1.
The work record table 28 stores work record data based on time and attendance information displayed on the work record screen. The work record screen is displayed on the display unit of the cloud server 2 or the display unit of a management terminal (not shown) connected to the cloud server 2.

The synchronization unit 21 periodically executes communication with the time and attendance registration terminal 1 to synchronize information stored in the employee master 23 and the affiliation master 24. As will be described in detail later, the synchronization unit 21 uses at least a part of master information of each employee (target person) who is to be registered for attendance information as shared information for the attendance registration terminals 1a to 1c and the cloud server 2. It functions as a management means to register. The synchronization unit 21 registers the authentication information referred to when entering and leaving work in association with the shared information for each employee (for each target person) as another part of the master information. That is, the master information includes shared information and authentication information. At that time, the synchronization unit 21 registers the authentication information in each of the time and attendance registration terminals 1 such that the time and attendance registration terminal 1 assigned to the employee corresponding to the authentication information is limited as a registration destination. Here, the time-of-work registration terminal 1 assigned to the employee corresponding to the authentication information corresponds to a time-of-work registration terminal for registering the time and work of the employee working in each branch in the present embodiment.
The time setting unit 22 stores the time and attendance data received from the time and date registration terminal 1 in the time card table 26.
As described above, since the time and attendance management system S is configured by connecting the plurality of time and day registration terminals 1a to 1c to the cloud server 2, in the organization having a plurality of branches, the time and attendance of employees belonging to each branch is registered. be able to.

FIG. 2 is a schematic block diagram showing the time and attendance registration terminal 1a. The time and attendance registration terminal 1b is also configured in the same manner as the time and attendance registration terminal 1a.
The on-time work registration terminal 1 a is a so-called tablet terminal, and includes a CPU 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, and a storage unit 19. In addition, the time and attendance registration terminal 1a is not limited to the tablet terminal, and may be, for example, a smartphone, a mobile phone, a PDA (Personal Digital Assistant), a notebook PC (Personal Computer), a desktop PC, or the like.
The CPU 11 develops in the work memory in the RAM 13 the time and attendance registration program 195 stored in the ROM 12 and the storage unit 19 and various instructions input from the touch panel display 14. The CPU 11 further executes various processes according to the program developed in the work memory according to the input instruction and the input data, stores the process result in the work memory in the RAM 13, and displays it on the touch panel display 14. Then, the CPU 11 stores the processing result stored in the work memory in the storage destination in the storage unit 19.

  The storage unit 19 is configured of, for example, a magnetic or optical storage medium such as a flash memory, or a rewritable non-volatile storage medium such as a semiconductor memory. The storage unit 19 stores a system program, a time and attendance registration program 195 corresponding to the system program, an employee submaster 191, an affiliation master 192, a time and attendance history information table 194, and the like.

The on-time work registration terminal 1 a further includes a touch panel display 14, a speaker 15, an NFC (Near Field Communication) reader 16, a short distance wireless communication unit 17, and a long distance wireless communication unit 18.
The touch panel display 14 is an input / output device configured by laminating a transparent touch panel on an upper layer such as a liquid crystal display, and displays characters and an image, and receives a user operation.
The speaker 15 converts an audio signal into audio and reports it.

  The NFC reader 16 is for transmitting and receiving information to and from an IC card or electronic device of NFC method, and here, it is used to identify a traffic IC card which is also used as electronic money, and an electronic device equipped with the function. Used to read information. As described above, since the identification information of the IC card which has already spread is used for time-of-work registration, there is an advantage that there is no need to newly distribute the IC card and there is no need to manage the IC card.

  The short distance wireless communication unit 17 is, for example, a communication means by Bluetooth (registered trademark) Low Energy or Wi-Fi (registered trademark), and can mutually communicate with the cloud server 2 via, for example, a wireless router. The long-distance wireless communication unit 18 is a communication unit that performs long-distance wireless communication by, for example, LTE (Long Term Evolution), and can mutually communicate with the cloud server 2. By communicating with the cloud server 2 by the short distance wireless communication unit 17 or the long distance wireless communication unit 18, it is possible to synchronize a database related to attendance and leaving with the cloud server 2.

The time and attendance registration program 195 is for causing the time and attendance registration terminal 1a to perform time and attendance registration processing.
Similarly to the employee master 23 of the cloud server 2, the employee sub-master 191 is a database that manages information on employees. The employee submaster 191 stores information on all employees for information with low secrecy, but stores only information relating to the employee of the branch managed by the time and attendance registration terminal 1 for information with high secrecy. ing.
The affiliation master 192 is, like the affiliation master 24 of the cloud server 2, a database that manages information on the affiliation of employees.
Time-of-work history information table 194 stores the history of time-of-work information input by the employee.

機能 Function of attendance control system S》
The functional blocks of the time and attendance management system S will be listed below.
FIG. 3 is a schematic block diagram showing the system of the present embodiment.
The time and attendance management system S can execute setting and synchronization, password registration / cancellation, IC card registration / cancellation, and login / logout. The time and attendance registration program 195 is for causing a computer to function as each means.

The log-in means 60 logs in to this work registration program 195 and ends the work registration process.
The setting unit 61 is for setting the program. It is possible to set affiliation (store where the terminal is installed), presence / absence of personal identification (input of personal identification number), setting availability of a break and a meal, and whether or not to allow the terminal to sleep while this application is displayed. Information on setting contents is managed by the time and attendance registration terminal 1.

  The personal identification number registration means 62 is for registering a personal identification number for authenticating an employee who performs time-of-day registration. Furthermore, the PIN number registration means 62 has a PIN number release function. The security code release function is a function for releasing a security code that certifies an employee who performs time and attendance registration. In the time and attendance management system S, the personal identification number is managed by the time and attendance registration terminal 1 and the cloud server 2. However, in the present embodiment, while the cloud server 2 manages the code numbers of all employees belonging to each branch, the time and attendance registration terminal 1 is a code of an employee belonging to the branch in which it is installed. Manage only numbers. This is because the password is worthy of highly confidential information. Further, the time-entry registration terminal 1 can prevent fraudulent imprinting such as spoofing by performing authentication with the registered personal identification number at the time of time-entry registration.

  Time and attendance register means 63 is for registering the time and attendance of the employee in the cloud server 2. The user can register whether or not he / she has eaten a meal in addition to work and leave of work, leave, start of break, and end of break by means of this time and attendance register means 63. Time and attendance information registered in the cloud server 2 is applied / displayed on the employment result screen (payroll / management analysis) of the cloud server 2.

  The IC card registration means 64 is for registering identification information of an IC card for selecting an employee who is going to leave work. The IC card releasing means 65 is for releasing the identification information of the IC card. The IC card authentication means 66 authenticates the identification information of the IC card. The identification information of the IC card is managed by the time and attendance registration terminal 1 and the cloud server 2. However, in the present embodiment, the cloud server 2 manages the identification information of the IC card of all employees belonging to each branch, whereas the time and attendance registration terminal 1 is an employee belonging to the branch in which it is installed. Manage only the identification information of the member's IC card. This is because the identification information of the IC card is worthy to be highly confidential information. In the time-of-day management system S, identification information of SUICA (registered trademark), KITACA (registered trademark), ICOCA (registered trademark), TOICA (registered trademark), and PASMO (registered trademark) can be used. When these IC cards are registered, time registration can be performed by touching the registered card to the terminal.

The application information display means 67 is a function of displaying information on the version, privacy policy, and terms of use regarding the program.
The help display means 68 is a function to display the help of this application.
The logout unit 69 logs out of the work registration program 195 and ends the work registration processing.

FIG. 4 is a diagram showing an example of the employee submaster 191. As shown in FIG.
The employee submaster 191 is a database including an employee number field, a name field, a personal identification number field, and an IC card identification information field. Each row of FIG. 4 shows each record of this database. The employee master 23 of the cloud server 2 is configured in the same manner. The synchronization unit 21 of the cloud server 2 periodically synchronizes a part of the employee master 23 with the employee submaster 191. Thereby, even when the time and attendance registration terminal 1 is offline, it is possible to access the information indicating the employee.

The employee number field is a field for storing a unique number (shared information) assigned to an employee in this organization.
The name field is a field for storing the employee's name (shared information).
The PIN number column stores a PIN number (authentication information) used by this employee at the time of work registration.

  The IC card identification information field stores identification information (authentication information) of the IC card used by this employee at the time of work registration. The employee submaster 191 stores the numbers and names of all the employees belonging to this organization. The employee submaster 191 stores the personal identification number and IC card identification information of the employee belonging to the branch (work place), but in principle, the personal identification number and IC card identification of the employee belonging to the other branch (work place) Information is not stored. For example, Patent Taro, Patent Jiro, Patent Atsuko, Patent Saburo, Patent Shiro, Patent Goro, and Patent Rokuro are all belonging to the Kasumigaseki branch and are subject to this work-time registration terminal 1, so the PIN number and IC card identification information are stored. It is done. The other person does not store the personal identification number and the IC card identification information, and synchronization with the cloud server 2 is not performed. As a result, the amount of communication related to the synchronization between the employee submaster 191 and the employee master 23 of the cloud server 2 can be reduced. Furthermore, since it does not have the personal identification number of the employee who belongs to the other branch and IC card identification information, it is possible to prevent the information leakage.

FIG. 5 is a diagram showing an example of the affiliation master 192. As shown in FIG.
The affiliation master 192 is a database including an employee number field, an affiliation field, and an authority field. Each row of FIG. 5 shows each record of this database. The affiliation master 24 of the cloud server 2 is configured in the same manner. The synchronization unit 21 of the cloud server 2 periodically synchronizes the affiliation master 24 and the affiliation master 192. Thereby, even when the time and attendance registration terminal 1 is offline, it is possible to access the information indicating the affiliation.

The employee number field is a field for storing a unique number assigned to an employee in this organization, and is similar to the employee number field of the employee submaster 191.
The affiliation column is a column that stores the workplace to which an employee belongs in this organization.
The authority column is a column for storing the authority that this employee has with respect to the system. There are three types of authority: manager, store manager and employee.

A person having the authority of the manager can execute setting and synchronization, password registration / cancellation, IC card registration / cancellation and logout.
A person having the authority of the store manager can execute synchronization, PIN code registration / cancellation, IC card registration / cancellation, and logout, but can not execute settings.
A person with the authority of the employee can execute synchronization and PIN registration, IC card registration and logout, but can not execute setting, PIN cancellation and IC card cancellation.

FIG. 6 is a diagram showing an example of the work time history information table 194. As shown in FIG.
The attendance and leaving history information table 194 is a database including an affiliation column, an employee number column, an attendance and leaving date column, an attendance and leaving time column, an operation column, and a registered flag column, and shows a history of registered attendance and attendance information.

The affiliation column is a column for storing the affiliation information of the employee who registered the time and attendance information.
The employee number field is a field for storing an employee number indicating the employee who registered the time and attendance information.
The work date and time field is a field for storing information on the date when the time and attendance data is registered.
The attendance / work time column is a column for storing information of the time when the attendance / working information is registered.

The operation field is a field for storing operation information of time and attendance information.
The registered flag column is a flag indicating whether or not the attendance information has been stored in the cloud server 2 by the above-described synchronization. When the registered flag column is set to “1”, this time and attendance information is stored in the cloud server 2. When the registered flag column is cleared to “0”, this time and attendance information is not stored in the cloud server 2.

FIG. 7 is a view showing a login screen 31 displayed on the time and attendance registration terminal 1.
In the login screen 31, an e-mail address / text box 311 and a password / text box 312 are displayed, and a login button 313 is further displayed. The email address and password are account information of this system.

The login screen 31 allows login by a user having the manager authority or the store manager authority. Similar to the login screen 31, the logout screen (not shown) can be logged out by a user having the manager authority or the store manager authority. Thereby, it is possible to prevent unauthorized login / logout by a user having employee authority and unauthorized use of the time and attendance registration terminal 1.
When the user logs in by the login screen 31, the account information is managed by the terminal. When the time and attendance registration program 195 is activated next time, the account information managed by the time and attendance registration terminal 1 is referred to and login is performed.

FIG. 8 is a diagram showing a time attendance registration screen 32 displayed on the time attendance registration terminal 1 in the offline state.
The time and attendance registration screen 32 has “Time Recorder” described in the title, and includes the notification area 321, the date and time area 322, the message area 323, the time and attendance registration area 5, and the employee selection area 4 below.

The notification area 321 is an area for notifying of the status of the time and attendance registration terminal 1, and in this case, "this terminal is offline" is displayed. As a result, the time and attendance registration terminal 1 can notify the user of its own state.
The date and time area 322 is an area for displaying the current date and time, and "August 1, 2017 (Tuesday) 15:00" is displayed here.

The message area 323 is an area for displaying a message regarding time and attendance registration, and in this case, “Please enter employee number or select time and attendance type” of the input promotion message 324 is displayed.
The attendance and attendance register area 5 is an area for displaying a button for registering receipt of meals for attendance and absence or attendance, and a attendance button 51, an attendance button 52, a break start button 53, a break end button 54, and a meal button 55 are displayed. .

The attendance button 51 is a button for registering the attendance of the employee.
The leave button 52 is a button for registering the leaving of the employee.
The break start button 53 is a button for registering an employee's break start.
The break end button 54 is a button for registering the end of the break of the employee.
The meal button 55 is a button for registering the receipt of the meal of the employee.
The employee selection area 4 is an area for selecting an employee, and includes a "select by number" tab 41 and a "select by name" tab 42. Note that the "select by number" tab 41 is the default.

In FIG. 8, when the time-of-day registration terminal 1 is online and the user taps the time-to-work button 51, the screen changes to the time-of-day registration screen 32a shown in FIG.
When the time and attendance registration terminal 1 is online and the user taps the ten key of the employee selection area 4, the screen changes to the time and attendance registration screen 32c shown in FIG.

FIG. 9 is a diagram showing a time-entry / registration screen 32 a in which “work-in” is selected among the time-entry and work-out.
In FIG. 8, no notification is displayed in the notification area 321 of the time and attendance registration screen 32 a. This indicates that the time and attendance registration terminal 1 is online.
Furthermore, the attendance button 51 in the selected state is displayed in the attendance register area 5 of the attendance registration screen 32a. The selected state of the attendance button 51 indicates that attendance registration relating to attendance is performed.
In the message area 323, “Please touch the IC card.” Of the input prompting message 324 is displayed. Since the attendance button 51 is in the selected state, next time the IC card is touched, the attendance registration is completed.

In FIG. 9, the user touches (holds up) the IC card 7 on the time and attendance registration terminal 1. The situation is shown in FIG. 10 and FIG.
FIG. 10 is a view showing the appearance of the IC card 7 held by the user (employee) on the right and the time and attendance registration terminal 1 in a state before the IC card 7 is touched. In FIG. 10, the time-of-work registration screen 32a shown in FIG. 9 is displayed on the time-of-work registration terminal 1, and the time-of-work button 51 is in a selected state.
Thereafter, the user (employee) touches the IC card 7 on the time and attendance registration terminal 1. The CPU 11 reads identification information from the IC card 7 by the NFC reader 16. Thereby, the CPU 11 registers the attendance of this user (employee) and displays the attendance registration screen 32 b on the touch panel display 14.
FIG. 11 is a view showing the appearance of the time and attendance register terminal 1 in a state after the IC card 7 is touched. In FIG. 11, a time attendance registration screen 32b is displayed on the time attendance registration terminal 1, and shows a state where time attendance is registered. The time and attendance registration screen 32b will be described in detail with reference to FIG. 12 described later. As described above, when the user touches the IC card 7 in the time entry / exit registration terminal 1 in FIG. 9, the transition to the time entry / exit registration screen 32b shown in FIG. 12 is made.

FIG. 12 is a diagram showing a time-entry / exit registration screen 32b in which the IC card 7 is touched and time-entry / exit registration is performed.
In the message area 323, “Kusugagaseki branch 1234: Patent Taro” of the employee information 325 and “working attendance recorded” of the registration completion message 326 are displayed. Furthermore, the attendance button 51 is displayed in the selected state in the attendance / registration section 5 even after the registration is completed. The selected state of the attendance button 51 indicates that the attendance registration relating to attendance will be performed also when the IC card 7 is touched next. This eliminates the need for the employee who comes to work next time to tap the attendance button 51 again.

  When an unregistered IC card is touched on the time entry registration terminal 1, an error message "This IC card is not registered. Please register an IC card" is displayed in the message area 323 in orange. A warning will be displayed in color or red.

FIG. 13 is a diagram showing a time-entry / exit registration screen 32c in which the employee number is partially input.
At the lower side of "enter employee number" in the employee selection area 4, the employee number is partially input like "12". At this time, each button of the time and attendance registration area 5 is in a non-selected state.
In the message area 323, “Please enter employee number” of the input prompting message 324 is displayed.

  When the input of the employee number related to the employee whose PIN is registered in the employee selection area 4 is completed, that is, the employee number is input, and the input is confirmed by selecting the “OK button”. In this case, the screen shifts to the time and attendance registration screen 32d shown in FIG. When an employee number related to an employee whose personal identification number is not registered is input in the employee selection area 4, the screen shifts to a time attendance registration screen 32e shown in FIG.

FIG. 14 is a diagram showing a time-of-work registration screen 32 d in which a personal identification number is input.
A PIN authentication pop-up 43 is displayed at the center of the time-entry registration screen 32d. In this PIN code authentication pop-up 43, the employee number and its name “1234: Patent Taro” and the message “Authenticate with PIN code. Please enter PIN code” and “* A PIN code displayed as a lower case letter is displayed.
If the user inputs a correct password in the password authentication pop-up 43, the screen changes to a time attendance registration screen 32e shown in FIG.

FIG. 15 is a diagram showing the time and attendance registration screen 32e in which the personal identification number is correctly input and the input of the employee number is accepted.
In the employee selection area 4, an employee number of "1234" is entered below the message prompting for entering an employee number. In the message area 323, “Kagushi-Seki Branch · 1234: Patent Taro” of the employee information 325 is displayed, and further “Please select time attendance type” is displayed.

  When the user taps the attendance button 51 in FIG. 15, the transition to the attendance / registration screen 32e shown in FIG. 16 is made.

FIG. 16 is a diagram showing a time entry / exit registration screen 32 f immediately after the attendance button 51 is tapped.
The attendance button 51 is selected by being tapped by the user. Thereafter, when the time-entry registration is correctly performed, the screen changes to the time-entry registration screen 32g shown in FIG.

FIG. 17 is a diagram showing a time-stamped work registration screen 32g in which time-stamped work registration is performed.
In the time-of-work registration screen 32g, in the message area 323, "registration to work has been recorded" of the registration completion message 326 is newly displayed. This allows the user to determine that the time and attendance registration has been correctly performed.

FIG. 18 is a diagram showing a time-entry / registration screen 32 h in which time-entry / registration of the same type is continuously performed.
In the message area 323 on the time-entry registration screen 32 h, “Continuously-stamped. Please check the attendance time with the store manager.” Is displayed below the registration completion message 326. As described above, when the same type is continuously stamped for one employee, for example, even improper attendance and attendance information such as stamping of attendance continuously is registered in the cloud server 2 as it is. Such continuous engraving may occur due to chattering of the NFC reader 16 when the IC card is touched.
Hereinafter, when the attendance / registration screen 32, 32a to 32h shown in FIG. 8 to FIG. 18 is not distinguished, it may be simply described as the attendance / registration screen 32.

FIG. 19 is a diagram showing the employee selection area 4 when the user selects the “select by number” tab 41.
The employee selection area 4 is displayed by selecting the "select by number" tab 41, and a message area 411, an employee number area 412, a ten key 413, and an OK button 414 are displayed. The employee selection area 4 is for selecting an employee by inputting an employee number.

The message area 411 is an area of a message prompting the user to enter an employee number.
The employee number area 412 is an area for displaying the employee number being input by the user. A ten key 413 is a button for inputting an employee number, and an OK button 414 is a button for confirming an input.

FIG. 20 shows the employee selection area 4 when the user selects the "select by name" tab 42.
The employee selection area 4 is displayed by selecting the "Select by Name" tab 42, and the combination of the header field 421a and the plural element fields 422a and the combination of the header field 421b and the plural element fields 422b are displayed. It contains. The employee selection area 4 is for selecting an employee by name.

  In the header field 421a, "store manager" is displayed, and in the lower element field 422a, the name of the store manager of the store is described. In the header field 421b, "Employee" is displayed, and in the lower element field 422a, the names of the employees of this store are described. Thus, employees can be selected by their names. The name of the employee displayed in this employee selection area 4 is only the name of the employee who belongs to the branch office where the time and attendance registration terminal 1 is installed, and the names of the employees of other branches are not displayed. .

FIG. 21 is a flowchart of synchronization processing.
In step S110, the synchronization unit 21 of the cloud server 2 synchronizes the employee numbers and names of all the records of the employee master 23 with the employee sub-master 191 on the work time registration terminal 1 side. Next, the synchronization unit 21 uses the PIN number and the IC card identification information of the employee submaster 191 pertaining to the employee targeted by the work-time registration terminal 1, that is, the employee who belongs to the branch where the work-time registration terminal 1 is installed. , And the employee master 23 of the cloud server 2 (step S111).

The synchronization unit 21 synchronizes all the records of the affiliation master 24 with the affiliation master 192 on the work time registration terminal 1 side (step S112), and ends the process of FIG.
As described above, in the synchronous processing in the present embodiment, the employee numbers and names of all the records of the employee master 23 in the employee submaster 191 are synchronized with the employee submaster 191 on the work time registration terminal 1 side. The password number of the employee submaster 191 and the IC card identification information pertaining to the employee targeted by the time and attendance registration terminal 1 are synchronized with the employee master 23 of the cloud server 2. In the present embodiment, an employee targeted by the time-entry register terminal 1 is an employee belonging to a branch (group) in which the time-entry register terminal 1 is installed.
Therefore, the employee submaster 191 is in a state in which the employee's personal identification number and IC card identification information targeted by the time-entry / work registration terminal 1 are stored, but this time-entry / work registration terminal 1 is not targeted, ie, other The personal identification number of the employee belonging to the branch (work place) and the IC card identification information are not stored. As a result, since the time and attendance registration terminal 1 does not store unnecessary employee PINs and IC card identification information, it is possible to suppress leakage of these PINs and IC card identification information.

22 and 23 are flowcharts related to the operation of the time and attendance registration screen 32. FIG.
When the CPU 11 of the time and attendance registration terminal 1 starts displaying the time and attendance registration screen 32, the operation processing of FIGS. 22 and 23 is started.
The CPU 11 waits for the user's operation input (step S10), and the user operates the touch panel display 14 or touches the IC card to proceed to the process of step S11.
In step S11, the CPU 11 determines a user operation. If the CPU 11 is an input related to an employee number or an employee name, the process proceeds to step S12. The CPU 11 proceeds to step S20 if the input is made by the user touching the IC card, and proceeds to the process of step S30 if the input related to any button of the on-time work registration area 5.

<< Input related to employee number or employee name >>
In step S12, when all the buttons in the time attendance register area 5 are in the non-selected state, the CPU 11 determines whether or not the input of the employee number or the employee name is completed (step S13). The screen displayed in step S12 is, for example, the time-of-day registration screen 32c shown in FIG.
In step S13, if the input of the employee number or the employee name is not completed (No), the CPU 11 returns to the process of step S10. If the input of the employee number or the employee name is completed (Yes), the CPU 11 performs affiliation determination processing (see FIGS. 24 and 25) (step S14). The input completion of the employee number means that the authentication of the personal identification number is also completed.

  If the affiliation determination processing has failed in step S15 (No), the CPU 11 returns to the processing of step S10. If the affiliation determination process is successful (Yes), the CPU 11 displays the affiliation, the number, and the name of the employee in the message area 411 (step S16), and returns to the process of step S10. The screen displayed in step S16 is, for example, the time registration screen 32e shown in FIG.

<< Input by touching the IC card >>
In step S20, the CPU 11 determines whether or not any button in the time and attendance registration area 5 has been selected. If none of the buttons in the time and attendance registration area 5 is selected (No), the CPU 11 displays an error message (step S22), and returns to the process of step S10.

  If one of the buttons in the time and attendance registration area 5 has been selected (Yes), the CPU 11 executes an employee determination process (see FIG. 26) (step S21). When one of the buttons in the time and attendance registration area 5 is selected, it is, for example, the time and attendance registration screen 32 a shown in FIG. 9.

  If the determination of the employee fails in step S23 (No), the CPU 11 returns to the process of step S10. If the determination of the employee is successful (Yes), the CPU 11 displays the affiliation, the number, and the name of the employee (step S24), and proceeds to the process of step S40 of FIG. The screen displayed in step S24 is, for example, the time registration screen 32b shown in FIG.

<< Input pertaining to the time-stamped button >>
In step S30, the CPU 11 sets one of the tapped time and work registration areas 5 in a selected state (step S30). The screen displayed in step S30 is, for example, the time registration screen 32a shown in FIG.

  Next, the CPU 11 determines whether the employee number or the employee name has been input (step S31). If the employee number or the employee name is not input (No), the CPU 11 returns to the process of step S10. If the employee number or the employee name has already been input (Yes), the CPU 11 proceeds to the process of step S40 in FIG.

  In step S40 of FIG. 23, the CPU 11 determines whether the time and attendance registration terminal 1 is connected to the network. If the network is connected (Yes), the CPU 11 deletes the off-line notification (step S41), executes an on-time attendance / registration process (see FIG. 27) (step S42), and proceeds to the process of step S45.

If the network is not connected (No), the CPU 11 displays an offline notification (step S43) and executes an off-time attendance / registration process (see FIG. 27) (step S44), and proceeds to the process of step S45.
In step S45, when the CPU 11 displays the registration completion message 326 (see FIG. 12) in the message area 323, the CPU 11 determines whether the registration is duplicate registration (step S46). The redundant registration means that, as described in FIG. 17, time-entry registration of the same type is continuously performed for one employee.
If the CPU 11 is duplicate registration (Yes), the CPU 11 displays a duplicate registration message (step S47), and ends the processing of FIG. The screen displayed in step S47 is, for example, the time and attendance registration screen 32h shown in FIG.
If the CPU 11 is not duplicate registration (No), the process of FIG. 23 ends.

24 and 25 are flowcharts of the affiliation determination process.
This employee affiliation determination process is called from step S14 shown in FIG. After the input of the employee number, the CPU 11 starts the process from step S50. After inputting the employee's name, the CPU 11 starts the process from step S100.
In step S50, the CPU 11 searches the affiliation master 192 by the employee number. The CPU 11 determines whether the information of any one of the employees hits the search (step S51). If the information of any employee hits the search (Yes), the CPU 11 proceeds to the process of step S52. If the information on any employee does not hit the search (No), the CPU 11 displays an input error (step S58). Then, the CPU 11 stores that the affiliation determination has failed (step S59), and ends the affiliation determination process of FIG.

  In step S100, the CPU 11 determines an employee number from the employee's name according to the employee submaster 191. When the CPU 11 further determines the affiliation from the employee number based on the affiliation master 192 (step S101), it proceeds to the process of step S52.

  In step S52, the CPU 11 determines whether the branch office to which the employee belongs is different from the branch office managed by the time and attendance registration terminal 1. If the branch office to which the employee belongs is a branch office, the CPU 11 proceeds to the process of step S53 in order to download the IC card identification information and the personal identification number of the employee from the cloud server 2. If the branch office to which the employee belongs is the branch office managed by the work-time registration terminal 1, the CPU 11 proceeds to the process of step S60 in FIG. In the process of step S52, when the process proceeds from step S101, the branch office to which the employee belongs is always the branch office managed by the time and attendance registration terminal 1. This is because when the process is started from step S100 by the input of the employee's name, it is not possible to select an employee of a different branch.

  In step S53, the CPU 11 determines whether or not the time and attendance registration terminal 1 is connected to the network. If the network is not connected (No), the CPU 11 proceeds to step S58 to execute a series of error processing. If the network is connected (Yes), the CPU 11 proceeds to the process of step S54.

In step S54, the CPU 11 instructs the cloud server 2 to search the employee master 23 by the employee number. The CPU 11 determines whether or not the employee number is hit in the search by the response of the cloud server 2 (step S55).
If the employee number does not hit the search (No), the CPU 11 proceeds to step S58 to execute a series of error processing. If the employee number hits the search (Yes), the CPU 11 receives a record of the hit employee information from the cloud server 2 (step S56).
The CPU 11 updates the employee submaster 191 with the record of the employee information received from the cloud server 2 (step S57), and proceeds to the process of step S60 in FIG.

In step S60 of FIG. 25, the CPU 11 searches the employee submaster 191 by the employee number, and determines in step S61 whether the employee has registered a personal identification number.
If the personal identification number is not registered (No), the CPU 11 proceeds to the process of step S64, records that the affiliation determination is successful, and ends the process of FIG.
If the personal identification number is registered (Yes), the CPU 11 allows the user to input the personal identification number (step S62). The CPU 11 determines whether or not the input code number matches the code number of the employee submaster 191 (step S63). If the input code number matches the code number of the employee submaster 191 (Yes), the CPU 11 proceeds to the process of step S64, records that the determination of affiliation is successful, and ends the process of FIG. .
In step S63, if the personal identification numbers do not match (No), CPU 11 displays an error indicating that the personal identification numbers do not match (step S65), and records that the affiliation determination has failed (step S65) S66), end the processing of FIG.
As described above, if the employee's work belongs to a different branch office, the time and attendance registration terminal 1 does not store the employee's IC card identification information and the personal identification number in the employee submaster 191. As a result, the time and attendance registration terminal 1 can reduce the amount of traffic at the time of synchronization with the cloud server 2. Then, when an employee of a different branch office registers time and work, the IC card identification information and the personal identification number of the employee are downloaded from the cloud server 2. Note that, when the processing in FIG. 22 and FIG. 23 is completed, the time and attendance registration terminal 1 may immediately delete the downloaded IC card identification information and password, or may delete it in the synchronization processing in FIG. 21. .

FIG. 26 is a flowchart of the employee information determination process.
This employee information determination process is called from step S21 shown in FIG.
In step S70, the CPU 11 searches the affiliation master 192 with the IC card identification information. The CPU 11 determines which employee's information hits the search (step S71). If the information on any employee hits the search (Yes), the CPU 11 proceeds to the process of step S77. If the information of any employee does not hit the search (No), the CPU 11 proceeds to the process of step S 72 to download the IC card identification information and the personal identification number of the employee from the cloud server 2. .
In step S72, the CPU 11 determines whether or not the time and attendance registration terminal 1 is connected to the network. If the network is not connected (No), the CPU 11 proceeds to step S78, stores that the determination of the employee information has failed, and ends the process of FIG.

  If the CPU 11 is connected to the network (Yes), the process proceeds to step S73. In step S73, the CPU 11 instructs the cloud server 2 to search the employee master 23 for the IC card identification information. The CPU 11 determines whether or not the IC card identification information hits the search according to the response of the cloud server 2 (step S74).

  If the IC card identification information does not hit the search (No), the CPU 11 proceeds to step S 78 to store the determination failure, and if the search hits (Yes), the record of the hit employee information is clouded It receives from the server 2 (step S75). If the search is hit, it indicates that the employee relating to the IC card identification information is an employee of a different branch.

The CPU 11 updates the employee submaster 191 with the record of the employee information received from the cloud server 2 (step S76), and proceeds to the process of step S77.
In step S77, the CPU 11 stores that the determination of the employee information is successful, and ends the process of FIG. Note that, when the processing in FIG. 22 and FIG. 23 is completed, the time and attendance registration terminal 1 may immediately delete the downloaded IC card identification information and password, or may delete it in the synchronization processing in FIG. 21. .

FIG. 27 is a flowchart of the on-time work registration process in the online state. This time and attendance registration process is called from the process of step S42 of FIG.
In step S <b> 80, the CPU 11 determines whether or not there is unregistered attendance information with respect to the cloud server 2 in the attendance history information table 194. Of the records of the time and attendance history information table 194, those for which the registered flag is cleared to "0" are time and attendance information for unregistered portions. If there is unregistered work attendance information (Yes), the CPU 11 acquires the unregistered work attendance information (step S81), and the process proceeds to step S82. If there is no unregistered work attendance information (No), the CPU 11 proceeds to the process of step S82.

  In step S <b> 82, the CPU 11 registers the latest operation minutes including the unregistered portion in the cloud server 2 for time attendance registration. Next, the CPU 11 determines whether or not the registration of the time and attendance information has succeeded from the response of the cloud server 2 (step S83). If the CPU 11 succeeds in registering the time and attendance information (Yes), it proceeds to the process of step S84, and if the registration of the time and attendance information fails (No), it proceeds to the process of step S87.

  Steps S84 to S86 are processing when registration of time and attendance information is successful. The CPU 11 deletes the unregistered work attendance information from the attendance history information table 194 (step S84). Next, the CPU 11 adds the attendance information for the latest operation to the attendance history information table 194 (step S85), sets the registered flag of the added attendance information (step S86), and ends the processing of FIG.

  Steps S87 and S88 are processing when registration of time and attendance information fails. The CPU 11 adds the attendance information for the latest operation to the attendance history information table 194 (step S87), clears the registered flag of the added attendance information (step S88), and ends the processing of FIG.

FIG. 28 is a flowchart of the time and attendance registration process in the offline state. This time and attendance registration process is called from the process of step S44 of FIG.
The CPU 11 adds the attendance information for the latest operation to the attendance history information table 194 (step S90), clears the registered flag of the added attendance information (step S91), and ends the processing of FIG.

暗 証 PIN code registration》
The password registration function will be described with reference to FIGS. 29 to 32 shown below. The password is one of authentication information to be referred to when entering and leaving work.
FIG. 29 is a diagram showing the personal identification number registration screen 33 while the employee number is being input.
When a menu (not shown) is selected on the time and day registration screen 32 (see FIGS. 8 to 18), the screen is shifted to the personal identification number registration screen 33.

The password registration screen 33 has the title "password registration" described in the title, and includes a message area 331, a back button 332, and an employee selection area 4 at the lower side.
The message area 331 is an area for displaying a message related to the registration of the personal identification number, and in this case, “Please enter the employee number to which the personal identification number is to be registered.” Is displayed.
The back button 332 is a button for returning to the time and attendance registration screen 32 (see FIGS. 8 to 18).
At the lower side of "enter employee number" in the employee selection area 4, the employee number is partially input like "12". When the input of the employee number is completed, the personal identification number registration pop-up 44 of FIG. 30 is displayed.

FIG. 30 is a diagram showing the personal identification number registration screen 33a while the personal identification number is being input.
In the employee selection area 4 of the personal identification number registration screen 33a, the input employee number "1234" is displayed. In the center of the password registration screen 33a, a password registration pop-up 44 is displayed. In the password registration pop-up 44, the entered employee number and its name “1234: Patent Taro”, the message “Please enter the password to be registered.” And “*” The displayed password is displayed.
If the user inputs a 4-digit code number in the code number registration pop-up 44, the screen changes to a code number registration screen 33b shown in FIG.

FIG. 31 shows the personal identification number registration screen 33b when the registration is completed.
In the lower central part of the message area 331, a "completion of a Kasumigaseki branch · 1234: Patent Taro" and a "PIN code has been registered" are displayed. Thus, the user can recognize that the password has been correctly registered.

FIG. 32 is a flowchart showing personal identification number registration processing.
First, the user inputs an employee number and a personal identification number from the time and attendance registration terminal 1 (step S120). The CPU 11 of the time and attendance registration terminal 1 receives the input of the employee number and the personal identification number. The input employee number and password are transmitted to the cloud server 2 (step S121). That is, the time and attendance registration terminal 1 transmits the input employee number and the personal identification number to the cloud server 2.
If the registration to the cloud server 2 has not been completed (No), the CPU 11 repeats the determination of step S122. If the registration to the cloud server 2 is completed (Yes), the CPU 11 proceeds to step S123 and displays a registration completion message 334 of the personal identification number registration screen 33b shown in FIG.
If an error is detected in registration in the cloud server 2 in step S122, the CPU 11 proceeds to step S124, displays an error, and abnormally ends.
Then, at the timing at which the time entry / exit registration terminal 1 performs such a PIN number registration process, the cloud server 2 performs the synchronization process described in FIG. 21 to register the PIN number in the employee sub-master 191. Can.
The password registration process may be performed mainly by the cloud server 2 and is not limited.

"PIN code release"
The security function release function will be described with reference to FIGS. 33 to 37 shown below. The password is one of authentication information to be referred to when entering and leaving work.
FIG. 33 is a diagram showing the personal identification number cancellation screen 34 while the employee number is being input.
When a menu (not shown) is selected on the time and attendance registration screen 32 (see FIGS. 8 to 18), the screen is shifted to the personal identification number cancellation screen 34.

The password release screen 34 has the title "Password release" described in the title, and includes a message area 341, a return button 342, and an employee selection area 4 below it.
The message area 341 is an area for displaying a message regarding the release of the personal identification number, in which "Please enter the employee number to release the personal identification number." Is displayed.
The back button 342 is a button for returning to the time and attendance registration screen 32 (see FIGS. 8 to 18).
At the lower side of "enter employee number" in the employee selection area 4, the employee number is partially input like "12". When the input of the employee number is completed, a release message box 343 of FIG. 34 is displayed.

FIG. 34 is a view showing the personal identification number release screen 34 a while the message for confirmation is displayed.
In the employee selection area 4 of the password release screen 34a, the entered employee number "1234" is displayed. A cancellation message box 343 is displayed at the center of the password cancellation screen 34a. In the cancellation message box 343, the entered employee number and its name “1234: Patent Taro”, the message “Are you sure you want to cancel the PIN?”, OK button and Cancel button It is displayed.
When the user taps the OK button, the password is released, and the screen changes to a password release screen 34b shown in FIG.

FIG. 35 is a diagram showing the personal identification number release screen 34b when the cancellation is completed.
In the lower central part of the message area 341, a "completion of the Kasumigaseki branch · 1234: Patent Taro" and "PIN code released" are displayed. This allows the user to recognize that the password has been correctly released.

FIG. 36 is a flowchart showing the PIN number release process.
First, the user inputs an employee number from the time and attendance registration terminal 1 (step S130). The CPU 11 of the time and attendance registration terminal 1 receives an input of an employee number. The input employee number and name are displayed in the cancellation message box 343 (see FIG. 34) for confirmation (step S131). When the user taps the button of the release message box 343 (step S132), the CPU 11 determines the operated button (step S133). If the cancel button is tapped, the CPU 11 ends the process of FIG. 36, and if the OK button is tapped, the process proceeds to step S134.
In step S134, the input employee number is transmitted to the cloud server 2 (step S121). That is, the time and attendance registration terminal 1 transmits the input employee number to the cloud server 2. Thereby, the cloud server 2 deletes the password associated with the employee number.
The CPU 11 determines whether deletion of the personal identification number in the cloud server 2 is completed (step S135). If the deletion of the personal identification number in the cloud server 2 is not completed (No), the CPU 11 repeats the determination of step S135. If deletion of the personal identification number in the cloud server 2 is completed (Yes), the CPU 11 proceeds to step S136 and displays a cancellation completion message 344 of the personal identification number cancellation screen 34b shown in FIG.
If an error is detected in the deletion in the cloud server 2 in step S135, the CPU 11 proceeds to step S137, displays an error, and abnormally ends.
Then, at the timing at which the time and attendance registration terminal 1 performs such a PIN number release process, the cloud server 2 performs the synchronization process described in FIG. 21 to release the PIN number from the employee sub-master 191. Can.
In addition, the cloud server 2 may be mainly used for this PIN number release process, and it is not limited.

<< IC card registration >>
The IC card registration function will be described with reference to FIGS. 37 to 41 shown below. The identification information of the IC card is one of the authentication information to be referred to when entering and leaving work.
FIG. 37 is a diagram showing the IC card registration screen 35 while the employee number is being input.
If a menu (not shown) is selected on the time and attendance registration screen 32 (see FIGS. 8 to 18), the IC card registration screen 35 is displayed.

The IC card registration screen 35 describes “IC card registration” in the title, and includes a message area 351, a return button 352, and an employee selection area 4 at the lower side.
The message area 351 is an area for displaying a message regarding the registration of the IC card. Here, "Please enter the number of the employee registering the IC card. When changing the registered IC card, the IC before the change is necessary. "Please touch the card." And "When the IC card is registered, the registered card can be touched on the terminal to register for attendance and leaving." Is displayed.

The back button 352 is a button for returning to the time and attendance registration screen 32 (see FIGS. 8 to 18).
At the lower side of "enter employee number" in the employee selection area 4, the employee number is partially input like "12". When the input of the employee number is completed, a transition is made to the IC card registration screen 35b of FIG. Even if the registered IC card is touched, the screen changes to the IC card registration screen 35b of FIG.
When the employee who has registered the IC card touches another IC card other than the registered IC card, the screen changes to the IC card registration screen 35a of FIG.

FIG. 38 is a diagram showing the IC card registration screen 35a while displaying a warning message.
In the employee selection area 4 of the IC card registration screen 35a, the entered employee number "1234" is displayed. A message box 353 is displayed at the center of the IC card registration screen 35a. In this message box 353, the entered employee number and its name “1234: Patent Taro”, the message “IC card is already registered”, and “registered if changing IC card” If you do not have a registered IC card, you will need to release it. Please contact the store manager. ”And the OK button is displayed.
When the user taps the OK button, the screen returns to the IC card registration screen 35 shown in FIG.

FIG. 39 is a diagram showing the IC card registration screen 35b displaying a message prompting the user to touch the IC card to be newly registered.
At the lower center of the message area 361, the entered employee number and its name "1234: Patent Taro" are displayed. In this state, when the user touches the IC card on the time and date registration terminal 1, the IC card is registered, and the screen changes to the IC card registration screen 35c of FIG.

FIG. 40 is a diagram showing the IC card registration screen 35c when the registration is completed.
In the lower center of the message area 351, “Kagyu Seki branch · 1234: Patent Taro” and “IC card registered.” Are displayed. Thus, the user can recognize that the IC card has been correctly registered.

FIG. 41 is a flowchart showing an IC card registration process.
The IC card registration process starts with the input of the employee number or the touch of the registered IC card.
In step S140, the user inputs an employee number from the time and attendance registration terminal 1. When receiving the input of the employee number, the CPU 11 of the work-time registration terminal 1 determines whether the IC card relating to the employee number has been registered (step S141). If the IC card relating to this employee number has been registered (Yes), the CPU 11 displays a warning message of the message box 353 (see FIG. 38) (step S142). Then, when the user taps the OK button of the message box 353 (step S143), the process of FIG. 41 ends.
If the IC card relating to the employee number is not registered (No), the CPU 11 proceeds to step S149 and executes IC card registration.

In step S144, the user touches the registered IC card on the time-of-day registration terminal 1. The CPU 11 of the on-time work registration terminal 1 reads the identification information of the IC card by the NFC reader 16. The CPU 11 of the work-time registration terminal 1 specifies the employee number from the input identification information of the IC card (step S145), and determines whether the identification information of the IC card has been registered (step S146). . If the identification information of the IC card is not registered (No), the CPU 11 displays a warning message indicating that the IC card is an unregistered IC card (step S147). Then, when the user taps the OK button or the like of the message box (step S148), the process of FIG. 41 is ended.
If the IC card relating to the employee has been registered (Yes), the CPU 11 proceeds to step S149 and executes IC card registration.

In step S149, the user touches the newly registered IC card on the time of day registration terminal 1. The CPU 11 of the on-time work registration terminal 1 reads the identification information of the IC card by the NFC reader 16.
The employee number and the newly input identification information of the IC card are transmitted to the cloud server 2 (step S150). That is, the time and attendance registration terminal 1 transmits the employee number and the newly input identification information of the IC card to the cloud server 2. Thereby, the cloud server 2 registers the identification information of the IC card in the record of the employee number.
In step S151, if the registration to the cloud server 2 is not completed (No), the CPU 11 repeats the determination of this step S151. If the registration to the cloud server 2 is completed (Yes), the CPU 11 proceeds to step S152, and a registration completion message 354 of the IC card registration screen 35c shown in FIG. 40 is displayed.
If an error is detected in the registration in the cloud server 2 in step S151, the CPU 11 proceeds to step S153, displays an error, and abnormally ends.
Then, at the timing when the work / time registration terminal 1 performs such an IC card registration process, the cloud server 2 performs the synchronization process described in FIG. 21 to register the identification information of the IC card in the employee submaster 191. it can.
The IC card registration process may be performed mainly by the cloud server 2 and is not limited.
By processing in this manner, for an employee who has already registered an IC card, the registration can not be changed to another IC card without the registered IC card. That is, even if the employee number and the password are leaked, the IC card registration can not be changed. In this way, it is possible to prevent another person from changing the registration to another IC card instead of the IC card registered by the user and registering for subsequent attendance and leaving.

"Release IC card"
The IC card release function will be described with reference to FIGS. 42 to 46 shown below. The identification information of the IC card is one of the authentication information to be referred to when entering and leaving work.
FIG. 42 is a diagram showing the IC card release screen 36 while the employee number is being input.
When a menu (not shown) is selected on the time and attendance registration screen 32 (see FIGS. 8 to 18), the IC card cancellation screen 36 is displayed.

The IC card release screen 36 describes “IC card release” in the title, and includes a message area 361, a back button 362, and an employee selection area 4 at the lower side.
The message area 361 is an area for displaying a message regarding the release of the IC card number, and in this case, “Please enter the employee number to release the IC card or touch the IC card.” Is displayed. .
The back button 362 is a button for returning to the time and attendance registration screen 32 (see FIGS. 8 to 18).
At the lower side of "enter employee number" in the employee selection area 4, the employee number is partially input like "12". When the input of the employee number is completed, a release message box 363 of FIG. 43 is displayed.

FIG. 43 is a diagram showing the IC card release screen 36a while displaying a confirmation message.
In the employee selection area 4 of the IC card release screen 36a, the entered employee number "1234" is displayed. A release message box 363 is displayed at the center of the IC card release screen 36a. The cancellation message box 363 displays the entered employee number and its name "1234: Patent Taro", a message "cancel IC card?", An OK button and a cancel button. There is.
When the user taps the OK button, the IC card is released, and a transition is made to an IC card release screen 36b shown in FIG.

FIG. 44 shows the IC card release screen 36b when the release is completed.
In the lower central part of the message area 361, a "completion of the Kasumigaseki branch · 1234: Patent Taro" and "the IC card has been released" is displayed. This allows the user to recognize that the IC card has been correctly released.

FIG. 45 is a diagram showing an IC card release screen 36c when the IC card is not registered.
A message box 365 is displayed at the center of the IC card release screen 36c. The cancellation message box 363 displays the message "1234: Patent Taro", which is the entered employee number and its name, a message "IC card is not registered", and an OK button.

FIG. 46 is a flowchart showing the IC card release process.
The IC card release process starts with the input of the employee number or the touch of the registered IC card.
In step S160, the user inputs an employee number from the time and attendance registration terminal 1. When receiving the input of the employee number, the CPU 11 of the work-time registration terminal 1 determines whether the IC card relating to the employee number has been registered (step S161). If the IC card relating to this employee number is not registered (No), the CPU 11 displays a warning message of the message box 365 (step S162). Then, when the user taps the OK button of the message box 365 (step S163), the processing of FIG. 46 is ended.
If the IC card relating to the employee number is registered (Yes), the CPU 11 proceeds to step S167 and executes the IC card registration.

In step S164, the user touches the registered IC card on the time-of-day registration terminal 1. The CPU 11 of the on-time work registration terminal 1 reads the identification information of the IC card by the NFC reader 16. The CPU 11 of the work-time registration terminal 1 specifies the employee number from the input identification information of the IC card (step S165), and determines whether the identification information of the IC card is already registered (step S166). . If the identification information of the IC card is not registered (No), the CPU 11 proceeds to the process of step S162, displays a warning message, and ends the process of FIG.
If the identification information of the IC card has been registered (Yes), the CPU 11 proceeds to step S167 and executes IC card registration.

  In step S167, the employee number and the name are displayed in the cancellation message box 363 (see FIG. 43). When the user taps the button of the release message box 363 (see FIG. 43) (step S168), the CPU 11 determines the operated button (step S169). If the cancel button is tapped, the CPU 11 ends the process of FIG. 46, and if the OK button is tapped, the process proceeds to step S170.

This employee number is transmitted to the cloud server 2 (step S170). That is, the time and attendance registration terminal 1 transmits the entered employee number or the employee number specified from the input identification information of the IC card to the cloud server 2. Thereby, the cloud server 2 deletes the identification information of the IC card from the record of the employee number.
In step S171, if the deletion from the cloud server 2 is not completed (No), the CPU 11 repeats the determination of this step S171. If the deletion from the cloud server 2 is completed (Yes), the CPU 11 proceeds to step S172 and displays a cancellation completion message 364 of the IC card cancellation screen 36b shown in FIG. The CPU 11 ends the process of FIG. 46 with the end of the process of step S172.
If an error is detected in the registration in the cloud server 2 in step S171, the CPU 11 proceeds to step S173, displays an error, and abnormally ends.
Then, at the timing when the work / time registration terminal 1 performs such an IC card release process, the cloud server 2 performs the synchronization process described in FIG. 21 to release the IC card identification information from the employee submaster 191. It can be carried out.
The IC card releasing process may be performed mainly by the cloud server 2 and is not limited.

<< Modification >>
In the above embodiment, the employees of the branch managed by the time and attendance registration device 1 are only the employees whose affiliation is the branch. In a modification, the employee of the branch managed by the time and attendance registration device 1 refers to an employee whose affiliation is the branch and an employee who has once registered for attendance and leaving at the branch.
FIG. 47 is a diagram showing an example of the employee sub-master 191A in the modification.
The employee submaster 191A is a database including an employee number column, a name column, a personal identification number column, and an IC card identification information column, and is configured in the same manner as the employee submaster 191 shown in FIG. The synchronization unit 21 of the cloud server 2 periodically synchronizes a part of the employee master 23 with the employee submaster 191A. Thereby, even when the time and attendance registration terminal 1 is offline, it is possible to access the information indicating the employee.

  The employee submaster 191A stores the numbers and names of all the employees belonging to this organization. The employee submaster 191A stores the PINs and IC card identification information of the employees belonging to the branch (work place) and the employees who have registered in and out of the work by the time registration terminal 1 in the past. Patent Taro, Patent Jiro, Patent Atsuko, Patent Saburo, Patent Shiro, Patent Goro, and Patent Rokuro are all belonging to the Kasumigaseki branch and are the same as the affiliation to which this work-time registration terminal 1 was installed, so the PIN number and IC Card identification information is stored. Since the design Jiro is an employee who has registered time and work by the time and work registration terminal 1 in the past, a password number and IC card identification information are stored. This is the design belonging to the other branch Toranomon branch by registering the updated record of the employee submaster 191A as it is in step S57 of FIG. 24 and step S76 of FIG. 26 in the above embodiment. It is in the state where the PIN code of Jiro and the IC card identification information are stored. And since the other employees have not registered the time and work by this time and work registration terminal 1 in the past, the personal identification number and the IC card identification information are not stored. As a result, it is possible to reduce the amount of communication related to the synchronization between the employee sub-master 191A and the employee master 23 of the cloud server 2.

FIG. 48 is a flowchart of synchronization processing.
In step S180, the synchronization unit 21 of the cloud server 2 synchronizes the employee numbers and names of all the records of the employee master 23 with the employee sub-master 191A on the time entry / exit registration terminal 1 side. Next, the synchronization unit 21 creates a cloud of the PIN of the employee submaster 191A and the IC card identification information pertaining to the employee of the branch office in which the on-time work registration terminal 1 is installed and the employee who registered on-time work on the on-time work registration terminal 1 It synchronizes with the employee master 23 of the server 2 (step S181). The employee who has registered the time of arrival and withdrawal with the time and attendance registration terminal 1 has authentication information registered as an employee of the time and attendance registration terminal 1. After this, this employee can register attendance and absence even if the attendance and attendance registration terminal 1 is offline.

The synchronization unit 21 synchronizes all the records of the affiliation master 24 with the affiliation master 192 on the work time registration terminal 1 side (step S182), and ends the process of FIG.
As described above, the synchronous processing in the present embodiment synchronizes the employee numbers and names of all the records of the employee master 23 among the employee submaster 191A with the employee submaster 191 on the work time registration terminal 1 side. The password number of the employee submaster 191 and the IC card identification information pertaining to the employee targeted by the time and attendance registration terminal 1 are synchronized with the employee master 23 of the cloud server 2. In this modification, the employee targeted by the attendance and registration terminal 1 has registered employees who belong to the branch (group) in which the attendance and registration terminal 1 is installed and the attendance and departure using the attendance and registration terminal 1 in the past Be both an employee.
Therefore, although the employee submaster 191 stores the employee's personal identification number and IC card identification information targeted by the time-entry / work registration terminal 1, the time-entry / work registration terminal 1 does not target it, ie, other branch offices The employee's personal identification number and IC card identification information belonging to the employee who have not been registered in the past by the attendance / registration terminal 1 in the past are not stored. As a result, since the time and attendance registration terminal does not store unnecessary employee PINs and IC card identification information, it is possible to suppress leakage of the PINs and the IC card identification information.

(Other modifications)
The present invention is not limited to the above embodiment, and modifications can be made without departing from the spirit of the present invention, and there are, for example, the following (a) to (e).

(A) The IC card or device registered by the user to the time and work registration terminal may be one that can be read by an NFC reader, and it may be an IC card driver's license or my number card, or a mobile phone or smartphone equipped with the FELICA (registered trademark) function Or the like.
(B) The IC card or device that the user registers with the time and attendance registration terminal is not limited to one that can be read by an NFC reader, and may be a device or wireless tag that can communicate using Bluetooth (registered trademark) Low Energy.
(C) The communication means for the on-time work registration terminal to communicate with the cloud server is not limited to the wireless communication means, and may be a wired communication means.
(D) The type of attendance and absence is not limited to attendance, leaving, start of rest, end of rest, and may be arbitrary, for example, may be a private outing. In addition, the records of supplies are not limited to meals.
(E) The time and attendance registration terminal is not limited to a configuration in which one branch terminal is installed for each branch, and for example, a plurality of terminals may be installed in the same store. At that time, for example, one time attendance register terminal may be installed for each floor, or one time installation terminal may be installed for each department. That is, the affiliation associated with one time-of-work registration terminal is not particularly limited, and may be a predetermined group or the like.

In the following, the invention described in the claims initially attached to the request for this application is appended. The item numbers of the claims described in the appendix are as in the claims attached at the beginning of the application for this application.
[Supplementary Note]

<< Claim 1 >>
It is a time and attendance management system for registering time and attendance information for which time and work input is accepted by the local device in a cloud server communicably connected to a plurality of local devices,
The system further comprises a management unit that registers at least a part of the master information of each target person who is the registration target of the time and attendance information as shared information in the plurality of local devices and the cloud server.
When the management means registers authentication information to be referred to at the time of work-and-work input in association with the shared information for each of the target persons as another part in the master information, the plurality of local devices The time and attendance management system, wherein the authentication information is registered such that the local device assigned to the subject corresponding to the authentication information is limited as a registration destination.
<< Claim 2 >>
The cloud server and the cloud server are generated by updating the shared information registered in the local device, or by updating the shared information registered in the cloud server. The time and attendance management system according to claim 1, wherein the inconsistency of the shared information with a plurality of local devices is matched at a predetermined timing so as to correspond to the update.
<< Claim 3 >>
The time and attendance management system according to claim 2, wherein the management means registers the authentication information also in the cloud server.
<< Claim 4 >>
The cloud server and the cloud server are generated by updating the authentication information registered in the local device, or by updating the authentication information registered in the cloud server. 4. The time and attendance management system according to claim 3, wherein the incompatibility of the authentication information with a plurality of local devices is matched to correspond to the update at the predetermined timing.
<< Claim 5 >>
The management means is limited to the local device associated with the affiliation information that matches the affiliation information of the target person among the plurality of local devices as the local device assigned to the target person as the registration destination 5. The time and attendance management system according to claim 4, wherein the authentication information is registered to be registered.
<< Claim 6 >>
The management means, as the local device assigned to the subject, among the plurality of local devices, a local device associated with affiliation information that matches the affiliation information of the subject, and the subject 5. The time and attendance management system according to claim 4, wherein the authentication information is registered such that a local device that has received time and attendance input pertaining to a person is limited as a registration destination.
<< Claim 7 >>
The authentication information may be a personal identification number input to the local device when the local device receives a time input / output, or identification information of a recording medium read by the local device when the local device receives the time input / output. The time and attendance management system according to any one of claims 1 to 6, characterized in that
<< Claim 8 >>
The time and attendance management system according to any one of claims 1 to 7, wherein the shared information includes the affiliation information of the object person in addition to the name information of the object person.
<< Claim 9 >>
The time and attendance management system according to claim 8, wherein the affiliation information is associated with each of the plurality of local devices.
<< Claim 10 >>
A computer in a time and attendance management system for registering time and attendance information for which time and work input is accepted by the local device in a cloud server communicably connected to a plurality of local devices;
It functions as a management unit that registers at least a part of the master information of each target person who is the registration target of the time and attendance information as shared information in the plurality of local devices and the cloud server,
When the management means registers authentication information to be referred to at the time of work-and-work input in association with the shared information for each of the target persons as another part in the master information, the plurality of local devices The program is characterized in that the authentication information is registered such that the local device assigned to the subject corresponding to the authentication information is limited as a registration destination.

1, 1a, 1b, 1c Attendance registration terminal (local device)
11 CPU (management means)
12 ROM
13 RAM
14 touch panel display 15 speaker 16 NFC reader 17 short distance wireless communication unit 18 long distance wireless communication unit 19 storage unit 191 employee sub master (a part of master information)
192 Affiliation master (part of master information)
194 Time and attendance history information table 195 time and attendance registration program 2 Cloud server (server device)
21 synchronization unit 22 time setting unit 23 employee master (part of master information)
24 Affiliation master (part of master information)
25 work basic information table 26 time card table 27 time attendance registered terminal table 28 work results table 31 login screen 311 mail address · text box 312 password · text box 313 login button 32, 32a ~ 32h time attendance registration screen 321 notification area 322 date and time area 323 Message area 324 Input prompting message 325 Employee information 326 Registration complete message 33, 33a, 33b Security code registration screen 331 Message area 332 Back button 334 Registration completion message 34, 34a, 34b Security code release screen 341 Message area 342 Back button 343 Cancel Message box 344 Cancel complete message 35, 35a to 35c IC card registration screen 351 Message area 352 Back button 353 Message box 354 Registration complete message 36, 36a to 36c IC card release screen 361 Message area 362 Back button 363 Release message box 364 Release completion message 365 Message box 4 Employee selection area 41 "Select by number" tab 42 "Select by name" Tab 43 PIN authentication pop-up 44 PIN registration pop-up 5 Attendance registration area 51 Attendance button 52 Attendance button 53 Rest start button 54 Rest end button 55 Meal button 7 IC card

Claims (10)

It is a time and attendance management system for registering time and attendance information for which time and work input is accepted by the local device in a cloud server communicably connected to a plurality of local devices,
The system further comprises a management unit that registers at least a part of the master information of each target person who is the registration target of the time and attendance information as shared information in the plurality of local devices and the cloud server.
When the management means registers authentication information to be referred to at the time of work-and-work input in association with the shared information for each of the target persons as another part in the master information, the plurality of local devices The time and attendance management system, wherein the authentication information is registered such that the local device assigned to the subject corresponding to the authentication information is limited as a registration destination.   The cloud server and the cloud server are generated by updating the shared information registered in the local device, or by updating the shared information registered in the cloud server. The time and attendance management system according to claim 1, wherein the inconsistency of the shared information with a plurality of local devices is matched at a predetermined timing so as to correspond to the update.   The time and attendance management system according to claim 2, wherein the management means registers the authentication information also in the cloud server.   The cloud server and the cloud server are generated by updating the authentication information registered in the local device, or by updating the authentication information registered in the cloud server. 4. The time and attendance management system according to claim 3, wherein the incompatibility of the authentication information with a plurality of local devices is matched to correspond to the update at the predetermined timing.   The management means is limited to the local device associated with the affiliation information that matches the affiliation information of the target person among the plurality of local devices as the local device assigned to the target person as the registration destination 5. The time and attendance management system according to claim 4, wherein the authentication information is registered to be registered.   The management means, as the local device assigned to the subject, among the plurality of local devices, a local device associated with affiliation information that matches the affiliation information of the subject, and the subject 5. The time and attendance management system according to claim 4, wherein the authentication information is registered such that a local device that has received time and attendance input pertaining to a person is limited as a registration destination.   The authentication information may be a personal identification number input to the local device when the local device receives a time input / output, or identification information of a recording medium read by the local device when the local device receives the time input / output. The time and attendance management system according to any one of claims 1 to 6, characterized in that   The time and attendance management system according to any one of claims 1 to 7, wherein the shared information includes the affiliation information of the object person in addition to the name information of the object person.   The time and attendance management system according to claim 8, wherein the affiliation information is associated with each of the plurality of local devices. A computer in a time and attendance management system for registering time and attendance information for which time and work input is accepted by the local device in a cloud server communicably connected to a plurality of local devices;
It functions as a management unit that registers at least a part of the master information of each target person who is the registration target of the time and attendance information as shared information in the plurality of local devices and the cloud server,
When the management means registers authentication information to be referred to at the time of work-and-work input in association with the shared information for each of the target persons as another part in the master information, the plurality of local devices The program is characterized in that the authentication information is registered such that the local device assigned to the subject corresponding to the authentication information is limited as a registration destination.

Images