JPH11224356A - Working managing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a working managing system with which the reduction of load such as the input of working data is attained and consistent processing from working data input to working data approval, system management and working data collection is enabled. SOLUTION: This managing system is composed of a working data input part 8 for allowing the working data input according to work rules made into data base, working data approving part 7 simplifying the approval of working data, operating/confirming part 4 for monitoring the condition of approval or registering the approver of working data, working data collecting part 5 for collecting the registered working data so as to use them for the other system, and working data/system data storage part 3 for storing these working data or the like.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and a system for managing work data such as working hours and vacations of employees.

[0002]

2. Description of the Related Art Conventionally, as described in Japanese Patent Application Laid-Open No. 05-274508, an input device such as a bar code reader is used to convert working hours and personal information into bar codes in advance.
Data was entered, and a database storing work rules was used to determine the validity of the data.

[0003]

The prior art has a function of checking data in a database and input / stored data in order to determine the validity of input data. There is a problem in that, when inputting the work rules, the work rules cannot be entered unless the work rules are correctly understood, and even if the work data that does not conform to the work rules is input, the data cannot be checked unless the data is stored in the database.

[0004] It is an object of the present invention to provide a work management method and system that reduce the load of inputting work data and the like. It is another object of the present invention to provide an employment management system capable of performing employment data input, employment data approval, system management, and employment data collection consistently.

[0005]

In order to achieve the above-mentioned object, input of employment data according to work rules in a database is allowed.

[0006] On the other hand, in order to simplify the function of approving the input employment data, at least one of the methods for the administrator to approve the workers to be approved is considered for individual approval or for the workers and the date of approval. It has a function to approve one at a time within a specified range.

[0007] Further, the system has management functions such as registering an approver of the employment data entered by each worker to operate and manage the employment data, and monitoring the approval status. , It has a collection function for putting it together for use in other systems.

Further, in order to realize the above-mentioned object, the present invention is characterized in that each function is consistently constructed by a computer.

[0009]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 shows a configuration of an employment management system according to one embodiment of the present invention. In this embodiment, this is realized by a server 1 and a client 2 connected by a network 6, an employment data / system data storage unit 3 is allocated to the server 1, and an operation / management unit 4 and an employment data A collection unit 5, an employment data approval unit 7, and an employment data input unit 8 are assigned. In the present embodiment, an example is shown in which the elements such as the employment data storage unit are assigned to each computer of the client server system connected via the network. However, even if a plurality of elements are assigned to one computer. Often,
All of the above elements may be assigned to a stand-alone system.

FIG. 2 shows each element of the configuration shown in FIG. 1 in more detail. In an employment data input section 8, each worker inputs employment data and work content information into an employment / work time data input function 10; And input according to the instructions on the screen. The contents of the input employment data are checked by the data check function 11, and if the input employment data is correct, the approval request function 12 requests the administrator to approve the employment data.
It is stored in the system data storage unit 3.

In the employment data approval section 7, the manager checks the employment data for which approval is requested among the employment data input by each worker, and if there is no problem such as an input error in the employment data, an approval function is performed. Approve at 13. If there is a problem with the data, the approval request is rejected, and the worker is requested (corrected) to correct the employment data. At the end of the month, the end-of-month approval request function 14 requests a higher-level manager to approve the employment data for the current month. If there is no problem such as an input error in the employment data for the current month, the higher-level manager approves it using the month-end closing approval function 15. If there is a problem with the employment data this month, request (correct) the requested manager for correction.

The operation / management unit 4 monitors the input status and the approval status of the employment data by the approval status check function 16 so that the employment data can be collected smoothly. A reminder email to the person. In addition, in order to facilitate the approval work of each worker, the table of FIG. 11 is provided in the employment data / system data storage unit, and the details of FIG. 11 will be described later. There is an approval route setting function 17 for setting who performs the approval work of each worker.

In the employment data collection section 5, the system administrator checks the approval status of the entire system by the overall status check function 18, and if all approvals have been completed, the employment data collection function 19 checks all the employment data for the current month. Put together.

FIG. 3 shows a flow of input of the work data of the worker by the work data input unit 8. It is determined whether or not the worker is working normally (step 21). If the worker is not working normally, an employment pattern is selected from a menu displayed on the screen (step 22). Next, the attending time and the leaving time are selected from the menu displayed on the screen (steps 23 and 24). The system automatically calculates the overtime hours when you enter the time of attending and leaving the office, and displays them in the overtime hours column. However, because you worked outside the business hours during the overtime hours, you changed the overtime hours, such as reducing overtime hours. Judgment is made (step 25), and if there is a change, the overtime hours are directly corrected (step 2)
6). At this time, if the time after the change is not in 0.5-hour units, or if overtime hours longer than the working hours are input, an error message is output (step 35) to urge correction. The operator determines whether or not the operator is a special operator such as a special technician (step 28). If the operator is a special operator, he or she inputs the work contents (step 29). Next, it is determined whether or not to make an approval request (step 30). When an approval request is made, an approval request button is executed (step 3).
1). At this time, it is checked whether there is any omission in required input items and there is no difference in the time between the work data and the work content data. If not (step 32), the data is stored in the work data / system data storage unit 3. If there is a problem, an error message is output (step 34) and input is performed again.
Although not described in this flowchart, inputs such as the application time of the flextime system and the presence or absence of a business trip may be added.

FIG. 4 shows the flow of approval of the manager by the work data approval unit 7. The manager determines whether there is a problem such as an input error in the employment data of each worker to be approved (step 40), and if there is a problem, designates rejection on the screen (step 41) and inputs the employment data. It is stored (step 51). There is no problem in the employment data, and it is determined whether or not to approve each person on a daily basis (step 42). If approval is to be given for each person, approval is made for each worker every day (step 43).
If it is the collection date on which the data is collected, a monthly approval request is made for each worker and the work data is stored (steps 44 and 4).
5, 51). If it is not the data collection date, work data is stored (step 51).

If no approval is to be made for each person on a daily basis, it is determined whether or not to approve all the workers on a daily basis (step 46). If the date is the data collection date, a request for monthly approval of all workers is made and the employment data is stored (step 4).
8, 44, 51). If it is not the data collection date, work data is stored (step 51).

If you do not approve everyone who should be approved every day,
It is determined whether batch approval is to be made by designating a date for each person (step 49). If batch approval is to be made, a date or a period of time is specified for each person and the specified range batch approval is made for each worker (step 49). 50), if it is a data collection day, all workers are requested to approve monthly approval and work data is stored (step 44,
45, 51). If it is not the data collection date, work data is stored (step 51).

FIG. 5 shows a processing flow of the operation / confirmation unit 4. The approval status is checked for each monthly approver, and it is determined whether or not there is an unapproved person (step 60). If there is an unapproved person, if monthly approval is not completed, an e-mail for reminder is sent to the monthly approved person (steps 61 and 6).
2) If the approval is not completed every day, an e-mail for dunning is sent to the approver every day. (Steps 63 and 64) If the input of the employment data is not completed, an e-mail for dunning the worker is sent. A mail is transmitted (steps 65 and 66). The e-mail for dunning is displayed on the screen displayed by the operation confirmation section.
A predetermined item such as a reminder is input, and an e-mail transmission program is started.

FIG. 6 shows a processing flow of the employment data collection unit. First, an approval status is searched (step 70). If the approval of the monthly approver has not been completed, a notification of incompleteness is sent to the monthly approver (steps 71 and 72). If completed, the search of the approval status is terminated (step 73), the employment management system is locked (input from the worker or the approver is prohibited) (step 74), and the employment data is collected (step 75). ). Thereafter, initialization such as updating of the date of the work management system is performed (step 76), and the lock of the work management system is released (step 77). Based on the work data collected in this way, the system cooperates with a salary calculation system or the like (step 78). FIG. 7 explains the input of the work data, and FIG. 7 (a) explains the work data input screen. When the worker inputs data, the data is displayed, for example, by clicking a mouse on the employment pattern input field 83, the work time input field 85, and the leaving time 87 of the date 81 to be input on the employment data input screen 80. This is done by selecting from the menu. For example, when the employment pattern input field 83 is clicked, a menu such as a regular work 91, an irregular work A92, an irregular work B93, etc. is displayed. A vacation menu such as a paid vacation may be added to this menu. FIG. 7A shows a case where the employment pattern of the irregular work A92 in which the predetermined employment time is from 15:00 to 22:00 is selected. The work start time 94 in the work time menu, the time 95 in the case of going to work 30 minutes later than the work start time, the time 96 in the case of work one hour later than the work start time, and the work end time 97 in the work time menu, 3 from work end time
The time 98 when working overtime for 0 minutes and leaving the office, and the time 99 when working overtime for 1 hour from the end time of working and leaving the office work in conjunction with the data set in the employment pattern input field 83 and the time when the worker met the employment pattern. Is displayed in a menu and data is input in a selection format, thereby reducing input errors.

When the option of the regular work 91 is removed from the menu, that is, when no employment pattern is set,
A menu item for regular work may be displayed on the menu for the clock-in and clock-out time.

Each menu displays the time and the overtime hours in the case of going and leaving the work at that time in parentheses.
When the clock-in / clock-out time is set, the time in parentheses is displayed in the overtime display column 89.

When the input of the work data is completed, the approver is notified of the completion of the data input, and the approval request button 90 is clicked for approval. At this time, it is checked whether the input employment data is correct. FIG. 7B shows an employment data input screen in which employment data is input and the approval request button 90 is clicked. The approval request button 90 also serves as a status display for inputting work data and an approval status. In FIG. 7A, the approval request button 90 is blank to indicate an unapproved state.
In (b), the input of the work data is completed, and the status becomes “approval request” indicating the status of executing the approval request.

FIG. 8 shows employment data check (step 3).
The flow of 2) is explained. When the button of the approval request is clicked (step 100), it is checked whether or not the data of the work time and the time of leaving the work, which are the work data, are inputted (step 101), and input. If not, output an error message (step 105)
And return to the beginning. If data has been entered, check if there is a difference between the working hours and the scheduled time + overtime hours (step 102), and if there is a difference, output an error message (step 105) and click on the approval request button for processing Put back. If the employment data has been correctly entered, it is checked whether the work content data has been entered (step 103). If not, an error message is output (step 105), and the processing is performed before the approval request button is clicked. Return to If the work content data has been input, the time of the work data and the time of the work content data are compared (step 104), and if they are not the same, an error message is output (step 105) and the process returns to before the approval request button was clicked. . If they are the same, the check processing ends.

FIG. 9 illustrates the monthly and daily approvals described in FIG. 4, and the employment data approval screen will be described with reference to FIG. 9 (a). In the monthly and daily approval work, when approving employment data of workers to be approved by the approver, select a specific worker or multiple workers and specify a specific date or a specific date range. Select and approve the employment data. When approving the employment data of a specific worker on a specific date, the employment data approver displays the employment data approval screen 110 and displays a list of workers to be approved by the employment data approver. The approver checks the employment data in the worker list 116, and checks the date 1
If the approval of the eleven specific workers has not been made, the operator selects the "approval" column 115 or the "working pattern / overtime hours" input column 113 for that date by clicking with a mouse or the like. The work data approver selects the “approval” column 115 or the “work pattern / overtime hours” column 113 of the specific worker on the specific date 111 to be approved,
Click the mouse and select the menu item
Approval of a specific worker on a specific date 117; rejection of employment performance data of the specific worker on a specific date 118; approval of collective employment data of each worker on a specific day basis 1
19. Display 120 for approving the specified range period of the specific worker, and select the menu item “Approve” menu 117 to approve the work pattern of the worker. FIG. 9B
Shows the approval screen after approval is completed. The symbol “O” indicating that the approval has been given is displayed in the “approval” column 115 on April 2 (Tuesday) of the person in charge of approval A.

In addition, a specific date 111 is designated,
When the "April 2 batch approval" menu 119 is selected, all the workers to be approved on the designated date are collectively approved.

Further, a specific worker 116 is designated, a date is designated in a range, and a "collective approval of worker A" menu 12 is selected.
When 0 is selected, the range of the specified worker and the specified date are collectively approved. Although the present embodiment has been described using a mouse, an input device such as a keyboard, a trackball, and a light pen may be used.

FIG. 10 illustrates the case where the approver inputs the employment data of the worker by proxy.
The proxy input of the employment data from the 0 (a) employment data approval screen will be described. In the case of monthly approval work, if the approver has an error in entering the employment data of the worker to be approved, or has not entered the employment data on a specific date, the data may be corrected due to the absence of the worker. When additional input is not possible, an employment data input screen of the user to be approved is displayed on the approval screen used by the approver, and the employment data of the worker can be changed and input. Approvers who can perform proxy input are set in the table shown in FIG.
Daily or monthly approver.

The work data approver displays the work data approver screen 110, and displays a list 111 of workers 116 to be approved by the work data approver. The approver checks the employment pattern / overtime hours item 113 and the approval request item 115 in the list of workers, and, when the employment data is found to be incorrect or has not been input, is found. The operator clicks and selects "Working pattern / overtime hours" 113 on a date with an error or not entered by the operator. The employment data approver selects the employment data to be corrected, and then clicks the mouse to execute approval of the specific worker on the specific date in the menu available to the approver 117. In order to correct the employment data of the worker, it displays 118 to reject, 119 to approve all at once on a specific day basis, 120 to approve the specified range period of the specific worker, 121 to start the proxy input of the designated person in charge. , A menu item “Worker A substitute input” 121 is selected and input. FIG. 10B shows an employment data input screen. The employment data input screen 80 of the selected worker on the date to be corrected is displayed. Select the input items 83, 85, and 87 to be corrected, and select and input employment data in the same manner as the input on the employment data input screen. ,"approval request"
Button 90 is clicked on with a mouse, and the screen returns to approval screen 110. The employment data contents of the worker corrected by the approver are displayed on the original screen shown in FIG. The substitute work data input function can also be executed from the work data approver's own work data input screen. FIG. 10C shows an employment data approval screen after proxy input.

FIG. 11 is a table for setting who performs daily and monthly approval for each worker, and there is one record for each worker. When each approver activates the daily approver, the daily approver ID 131 in which the activated approver is set is searched, the person in charge ID 130 set for the daily approver is acquired, and a list of approval screens is created / indicate. When each approver activates the monthly approval, a search is made for the monthly approver ID 132 in which the activated approver is set, and the person in charge ID1 set as the monthly approver is searched.
30 is obtained, and a list of approval screens is created / displayed.

This table is set by the approval route setting function 17 and stored in the work data / system data storage unit. This table is used to check whether an ID entered by a worker or an approver prior to data entry or approval is valid.

FIG. 12 is a list of display labels of approval request buttons on the employment data input screen and status rules indicating the approval status of the input employment data on the display date, and indicates whether the data input by the worker has been approved. Can be confirmed by the display label of the approval request button 90. When the label of the approval request button 90 is blank 140 as shown in the employment data input screen 80 of FIG. 7A, the data input is not completed or the approval request is not made.
45 is represented. As shown in an employment data input screen 80 in FIG. 7B, when the approval request button 90 is clicked, the data input is completed, and a character string of “under approval request” 141 indicating the state 146 of requesting approval is displayed. I do. When the approver approves the employment data 147, the approval request button 90 on the employment data input screen 80 is displayed as "Approved".
142 is displayed. If the approver does not approve the employment data (requires data correction) 1
48, the approval request button 90 on the employment data input screen 80 displays a character string of "rejected" 143. Also, a character string of “collected” 144 indicating the state 149 in which the work data is collected is displayed.

FIG. 13 shows a screen display on the approval screen.
This is a list of status rules indicating the approval status of the input employment data on the display date, and it is possible to confirm whether or not the data requested by the operator has been approved by the display item 115 of the approval screen 110. Approval screen 11 in FIG.
If the item 115 of “0” is a blank 150, it indicates a state 155 in which data input has not been completed or an approval request has not been made. As shown in the approval screen 110 of FIG.
Is “△” 151, indicating that approval has been requested. Also, the approver has approved the employment data.
In the case of 7, the item 115 on the employment data input screen 110 displays “○” 152. When the approver does not approve the input employment data (requests data correction) 158, the item 115 on the employment data input screen 110 displays “×” 153. Further, a character string of “double circle” 154 representing the state 159 in which the work data is collected is displayed.

[0033]

According to the present invention, in data input relating to a system for managing working hours, a data menu according to a work pattern is displayed and data is input in a selection format, so that erroneous data input can be reduced. it can.

According to another aspect of the present invention, the input data is checked in advance after the input of the work data, so that the check at the time of approval can be reduced.

In still another embodiment of the present invention, input data can be collectively approved within at least one selected range of a plurality of persons and a plurality of days.

According to still another aspect of the present invention, it is possible to provide an employment management system which can manage employment data input, approval, and summarization as one.

[Brief description of the drawings]

FIG. 1 shows an entire configuration of an employment management system according to an embodiment of the present invention.

FIG. 2 is a more detailed diagram of each element of the configuration shown in FIG. 1;

FIG. 3 is a flowchart showing a flow of input of employment data of a worker.

FIG. 4 is a flowchart showing a flow of approval of a manager.

FIG. 5 is a flowchart illustrating a flow of a process of an operation status confirmation unit.

FIG. 6 is a flowchart showing a processing flow of an employment data collection unit.

FIG. 7 is a screen transition diagram for explaining work data input work.

FIG. 8 is a flowchart showing a flow of checking work data.

FIG. 9 is a screen transition diagram for explaining an approval operation.

FIG. 10 is a screen transition diagram for explaining a case in which an approver inputs employment data of a worker by proxy.

FIG. 11 is a table storing monthly and monthly approvers for each worker.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Computer (server) 2 Computer (client) 3 Employment data storage 4 Operation / confirmation part 5 Employment data collection part 6 Network 7 Employment data approval part 8 Employment data input part 10 Employment / work time data input function 11 Data check function 12 Approval Approval request function (daily unit) 13 Approval function (daily unit) 14 End-of-month approval request function 15 End-of-month approval function 16 Approval status check function (end of month end) 17 Approval route setting function 18 Overall status check function (whole system) 19) Data collection function

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Tomomasa Nagase 6-90 Onoe-cho, Naka-ku, Yokohama-shi, Kanagawa Prefecture Within Hitachi Business Solutions Co., Ltd. (72) Inventor Yoichi Fukuhara 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Software Development Division, Hitachi, Ltd.

Claims (7)

[Claims] 1. An employment data input unit for inputting employment data,
An employment data approval unit for approving the input employment data, an operation / confirmation unit for confirming completion of the employment data input and the employment data approval, and registering an approver for approving the employment data; and An employment management system, comprising: an employment data collection unit for collecting collected employment data. 2. The employment management system according to claim 1, further comprising means for checking the validity of the input employment data and outputting an error message when the employment data does not meet a predetermined condition. Management system. 3. The employment management system according to claim 1, further comprising means for designating at least one of the plurality of workers and the plurality of days of the input employment data and approving them collectively. . 4. The employment management system according to claim 1, further comprising means for permitting the approver to modify and / or add the input employment data. 5. The employment management system according to claim 1, wherein said employment data input unit includes means for presetting a limit value of input data, and a warning message in response to input of employment data exceeding a predetermined ratio of said limit value. Means for displaying a job management system. 6. The employment management system according to claim 1, wherein after the input of the employment data, means for notifying the approver that the input of the employment data has been completed; An employment management system comprising rejection means. 7. A menu for displaying the type of employment pattern, responding to a selection input for selecting one of the employment patterns displayed on the menu, and selecting at least a standard employment start time and employment end time in the selected employment pattern. An employment management method, comprising displaying a menu of employment start time and employment end time, which is one of the above, and selecting and inputting from the displayed employment start time and employment end time menus.