WO2019091099A1 - 员工离场管控方法、应用服务器及计算机可读存储介质 - Google Patents

员工离场管控方法、应用服务器及计算机可读存储介质 Download PDF

Info

Publication number
WO2019091099A1
WO2019091099A1 PCT/CN2018/089345 CN2018089345W WO2019091099A1 WO 2019091099 A1 WO2019091099 A1 WO 2019091099A1 CN 2018089345 W CN2018089345 W CN 2018089345W WO 2019091099 A1 WO2019091099 A1 WO 2019091099A1
Authority
WO
WIPO (PCT)
Prior art keywords
employee
attendance
abnormal
management
authority
Prior art date
Application number
PCT/CN2018/089345
Other languages
English (en)
French (fr)
Inventor
李文慧
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019091099A1 publication Critical patent/WO2019091099A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C1/00—Registering, indicating or recording the time of events or elapsed time, e.g. time-recorders for work people
    • G07C1/10—Registering, indicating or recording the time of events or elapsed time, e.g. time-recorders for work people together with the recording, indicating or registering of other data, e.g. of signs of identity

Definitions

  • the present application relates to the field of data analysis technologies, and in particular, to an employee departure control method, an application server, and a computer readable storage medium.
  • the relevant permissions required for the enterprise such as UM, domain, mailbox and access control card, will be opened.
  • the outsourcer confirms the departure, his authority needs to be blocked.
  • the actual situation is often caused by the department not launching the departure process in time, resulting in the relevant authority of the outsourced personnel who have left the site is not blocked in time, resulting in information security and workplace safety risks.
  • the present application proposes an employee departure control method, an application server, and a computer readable storage medium to solve the problem of how to effectively control the authority of the departing employees.
  • the present application provides a method for employee departure control, which comprises the steps of:
  • the attendance data includes an attendance record and a leave record
  • the attendance abnormality means that the employee has neither corresponding attendance record nor leave record, and if the employee has an attendance abnormality, and the attendance abnormality reaches the time Determining the duration of the attendance management, the employee is identified as an abnormal employee;
  • the present application further provides an application server, including a memory and a processor, where the employee stores an employee departure control system operable on the processor, and the employee departure control system
  • the steps of the employee departure control method as described above are implemented when executed by the processor.
  • the present application further provides a computer readable storage medium storing an employee departure management system, the employee departure management system being executable by at least one processor, The step of causing the at least one processor to perform the employee exit control method as described above.
  • the employee departure control method, the application server, and the computer readable storage medium proposed by the present application can determine whether the employee has the possibility of leaving the field according to the employee's attendance data and the length of the management time, and automatically complete the pair.
  • the abnormal employee's authority is blocked to ensure the company's information security, and the corresponding department or the abnormal employee is notified to leave the field to confirm the abnormal employee information according to the confirmation result.
  • 1 is a schematic diagram of an optional hardware architecture of an application server of the present application
  • FIG. 2 is a schematic diagram of a program module of a first embodiment of an employee departure control system of the present application
  • FIG. 3 is a schematic diagram of a program module of a second embodiment and a third embodiment of the employee departure control system of the present application;
  • FIG. 4 is a schematic flow chart of a first embodiment of an employee departure control method of the present application.
  • FIG. 5 is a schematic flow chart of a second embodiment of an employee departure control method of the present application.
  • FIG. 6 is a schematic flow chart of a third embodiment of an employee departure control method of the present application.
  • FIG. 1 it is a schematic diagram of an optional hardware architecture of the application server 2 of the present application.
  • the application server 2 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through a system bus. It is pointed out that Figure 1 only shows the application server 2 with components 11-13, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the application server 2 may be a computing device such as a rack server, a blade server, a tower server, or a rack server.
  • the application server 2 may be an independent server or a server cluster composed of multiple servers. .
  • the memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), a random access memory (RAM), a static Random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
  • the memory 11 may be an internal storage unit of the application server 2, such as a hard disk or memory of the application server 2.
  • the memory 11 may also be an external storage device of the application server 2, such as a plug-in hard disk equipped on the application server 2, a smart memory card (SMC), and a secure digital number. (Secure Digital, SD) card, flash card, etc.
  • the memory 11 can also include both the internal storage unit of the application server 2 and its external storage device.
  • the memory 11 is generally used to store an operating system installed on the application server 2 and various types of application software, such as program codes of the employee departure control system 200. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
  • the processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 12 is typically used to control the overall operation of the application server 2.
  • the processor 12 is configured to run program code or process data stored in the memory 11, such as running the employee departure control system 200 and the like.
  • the network interface 13 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the application server 2 and other electronic devices.
  • the present application proposes an employee departure control system 200.
  • FIG. 2 it is a program module diagram of the first embodiment of the employee departure control system 200 of the present application.
  • the employee departure control system 200 includes a series of computer program instructions stored in the memory 11, and when the computer program instructions are executed by the processor 12, the employees of the embodiments of the present application can be deactivated. Control operations.
  • the employee departure control system 200 can be divided into one or more modules based on the particular operations implemented by the various portions of the computer program instructions. For example, in FIG. 2, the employee departure management system 200 can be divided into a setting module 201, an obtaining module 202, a determining module 203, and a blocking module 204. among them:
  • the setting module 201 is configured to set a management duration for the attendance of the employee.
  • the security level corresponding to each post type and the attendance management duration corresponding to each security level are set in advance, wherein the higher the security level, the shorter the corresponding attendance management duration. Then, for each employee, obtain the job type of the employee, query the security level corresponding to the job type, and query the time management and control duration corresponding to the security level. Finally, the employee's attendance management duration is set according to the queried result.
  • out-of-office management of the employee is described by taking an outsider as an example.
  • the duration of the attendance management and control is the basis for judging whether the outsourced personnel leave the field. If the time of the outsourcing staff attendance abnormality reaches the time limit of the attendance management, it is determined that the outsourced personnel may have left the field. In this embodiment, the duration of the attendance management corresponding to the outsourced personnel may be set to one week.
  • the obtaining module 202 is configured to obtain attendance data of the employee.
  • the time and attendance data of each outsourcer is obtained from the attendance device or the personnel system, and the attendance data includes the attendance record and the leave record.
  • the attendance data includes the attendance record and the leave record.
  • the outsourcer records the attendance by swiping the card
  • the card record of each outsourcer is periodically obtained from the attendance machine.
  • the credit card record of each outsourcer can be obtained at the weekend.
  • the leave record can be obtained from the corresponding personnel system.
  • the determining module 203 is configured to determine whether there is an employee whose attendance abnormality reaches the management time.
  • the attendance abnormality means that the outsourcer has neither a corresponding attendance record nor a leave record. If an outsourcer has an attendance abnormality and the time of the attendance abnormality reaches the length of the control, it is judged that the outsourcer may have left the scene. For example, for an outsourced person who has no credit card record within one week, it is automatically checked whether there is a leave record. If not, it is judged that the outsourcer's attendance is abnormal and has reached the length of control.
  • the blocking module 204 is configured to block the authority of an abnormal employee.
  • an outsourced person whose attendance abnormality reaches the management time limit it is determined as an abnormal outsourcing personnel, and the authority of the abnormal outsourced personnel in the workplace, such as a work system account, a domain account, an email address, an access card, and the like, is automatically blocked.
  • the partial authority preset by the abnormal outsourcing personnel may be temporarily blocked first, and then further confirmed whether the abnormal outsourced personnel permanently removes all rights after leaving the field, and the preset partial authority is the access control card. Permissions, etc.
  • the employee departure control system 200 includes the setting module 201, the obtaining module 202, the judging module 203, and the blocking module 204 in the first embodiment.
  • the notification module 205, the receiving module 206, and the processing module 207 are included.
  • the notification module 205 is configured to automatically notify the corresponding department to perform the departure confirmation.
  • a notification is automatically sent to the department corresponding to the abnormal outsourcer to confirm whether the abnormal outsourcer actually leaves the field.
  • the manner of issuing the notification may be a mail.
  • the email is automatically triggered to be sent to the department corresponding to the abnormal outsourcer, and the department is informed that the abnormal outsourcer has no credit card and leave record within one week, and the authority has been blocked. Please confirm whether it has left. If you have already left the field, you need to initiate the exit signing process as soon as possible.
  • the receiving module 206 is configured to receive a confirmation result of the corresponding department feedback.
  • the abnormal outsourcer needs to confirm the departure. For the confirmation of the departure personnel, it is necessary to automatically initiate the exit verification process for the personnel, and declare the departure behavior of the personnel.
  • the department's internal staff can choose the length of their vacation time (for example, 2 weeks, 1 month, 2 months) and the start and end time. The abnormal outsourcing personnel's authority will remain in the length of the selected vacation time. Blocked state, if the middle returns to work, the department can manually unlock the permission or issue an unlock request.
  • the department internal office needs to give a reasonable reason and trigger the mail to the management team for filing.
  • the confirmation result includes the abnormal outsourcing personnel confirming that the departure, the long vacation, the completion or the attendance data failure.
  • the confirmation result further includes the length of the vacation time and the start and end time.
  • the processing module 207 is configured to process the authority of the abnormal employee according to the received feedback.
  • the feedback may include five situations: confirming that the user has left the field, slenderness, absenteeism, attendance data failure, and confirmation of the failure to receive feedback (the department has not done any processing). If the abnormal outsourcer is confirmed to have left the site, then all rights of the abnormal outsourcer are blocked, and an exit signing process for the abnormal outsourcer is initiated, and the process is deleted after the exit signing process is completed. Abnormal outsourcing personnel data, the subsequent no longer need to judge whether the abnormal outsourcing personnel leave the field. If the abnormal outsourcer is in the long vacation, the length of the vacation time and the start and end time of the abnormal outsourcer are obtained, and the abnormal outsourcer is set to not need attendance during the vacation, and the authority is unlocked at the end of the vacation.
  • the correction process of the attendance data failure is initiated, and the corrected attendance data is re-acquired after the correction process of the attendance data failure is completed, and then the unlocked authority is determined according to the corrected attendance data. If the abnormal outsourcer is absent or does not receive the confirmation result of the feedback, the abnormality notification is sent to the management team corresponding to the abnormal outsourcer by mail, and the processing result fed back by the management team is received.
  • the notification module 205 is further configured to notify the abnormal employee to perform the departure confirmation.
  • the contact information of each outsourcer such as a phone number, a mailbox, etc.
  • the contact information of each outsourcer is stored in advance.
  • the method of issuing the notification may be a short message or an email, etc., in which the abnormality of the outsourced personnel is not included in the card for one week, and the permission has been blocked. Please confirm whether the user has left the site. Field signing process. If you are on vacation, you need to initiate a vacation application process and feedback the length of vacation time and start and end time. If the attendance data is faulty, the correction process of the attendance data failure needs to be initiated, and the attendance data of the abnormal outsourcer is corrected to the correct data.
  • the receiving module 206 is further configured to receive a confirmation result of the abnormal employee feedback.
  • the confirmation result includes the abnormal outsourcing personnel confirming that the departure has occurred, the vacation time, or the attendance data failure.
  • the confirmation result when the vacation is long, the confirmation result further includes the length of the vacation time and the start and end time.
  • the processing module 207 is further configured to process the authority of the abnormal employee according to the received feedback.
  • the feedback may include four cases: confirming that the user has left the field, the length of the vacation, the attendance data failure, and the confirmation result that the feedback is not received (the abnormal outsourcer has not done any processing). If the abnormal outsourcing personnel confirms that the departure has been exited, blocking all rights of the abnormal outsourcing personnel, and initiating an exit signing process for the abnormal outsourcing personnel, deleting the abnormality after the exit signing process is completed. Outsourcing personnel data, the subsequent no longer need to judge whether the abnormal outsourcing personnel leave the field. If the abnormal outsourcer is in the long vacation, the length of the vacation time and the start and end time of the abnormal outsourcer are obtained, and the abnormal outsourcer is set to not need attendance during the vacation, and the authority is unlocked at the end of the vacation.
  • the correction process of the attendance data failure is initiated, and the corrected attendance data is re-acquired after the correction process of the attendance data failure is completed, and then the unlocked authority is determined according to the corrected attendance data. If the confirmation result of the feedback is not received, the abnormality notification is sent to the management team corresponding to the abnormal outsourcer by mail, and the processing result fed back by the management team is received.
  • the present application also proposes an employee departure control method.
  • FIG. 4 it is a schematic flowchart of the first embodiment of the employee departure control method of the present application.
  • the order of execution of the steps in the flowchart shown in FIG. 4 may be changed according to different requirements, and some steps may be omitted.
  • Step S400 setting a management duration for the attendance of the employee.
  • the security level corresponding to each post type and the attendance management duration corresponding to each security level are set in advance, wherein the higher the security level, the shorter the corresponding attendance management duration. Then, for each employee, obtain the job type of the employee, query the security level corresponding to the job type, and query the duration of the attendance management and control corresponding to the security level. Finally, the employee's attendance management duration is set according to the queried result.
  • out-of-office management of the employee is described by taking an outsider as an example.
  • the duration of the attendance management and control is the basis for judging whether the outsourced personnel leave the field. If the time of the outsourcing staff attendance abnormality reaches the time limit of the attendance management, it is determined that the outsourced personnel may have left the field. In this embodiment, the duration of the attendance management corresponding to the outsourced personnel may be set to one week.
  • Step S402 obtaining attendance data of the employee.
  • the time and attendance data of each outsourcer is obtained from the attendance device or the personnel system, and the attendance data includes the attendance record and the leave record.
  • the attendance data includes the attendance record and the leave record.
  • the outsourcer records the attendance by swiping the card
  • the card record of each outsourcer is periodically obtained from the attendance machine.
  • the credit card record of each outsourcer can be obtained at the weekend.
  • the leave record can be obtained from the corresponding personnel system.
  • step S404 it is determined whether there is an employee whose attendance abnormality reaches the management time.
  • the attendance abnormality means that the outsourcer has neither a corresponding attendance record nor a leave record. If an outsourcer has an attendance abnormality and the time of the attendance abnormality reaches the length of the control, it is judged that the outsourcer may have left the scene. For example, for an outsourced person who has no credit card record within one week, it is automatically checked whether there is a leave record. If not, it is judged that the outsourcer's attendance is abnormal and has reached the length of control.
  • step S406 the authority of the abnormal employee is blocked.
  • an outsourced person whose attendance abnormality reaches the management time limit it is determined as an abnormal outsourced person, and all rights of the abnormal outsourced personnel in the workplace are automatically blocked, such as a work system account, a domain account, a mailbox, an access card, and the like.
  • the partial authority preset by the abnormal outsourcing personnel may be temporarily blocked first, and then further confirmed whether the abnormal outsourced personnel permanently removes all rights after leaving the field, and the preset partial authority is the access control card. Permissions, etc.
  • the employee departure control method proposed in this embodiment can determine whether the employee has the possibility of leaving the field according to the employee's attendance data and the length of the management time, automatically complete the authority blockade of the abnormal employee, and ensure the company information security.
  • FIG. 5 it is a schematic flowchart of a second embodiment of the employee departure control method of the present application.
  • the steps S500-S506 of the employee departure control method are similar to the steps S400-S406 of the first embodiment, except that the method further includes steps S508-S512.
  • the method includes the following steps:
  • Step S500 setting a management duration for the attendance of the employee.
  • the security level corresponding to each post type and the attendance management duration corresponding to each security level are set in advance, wherein the higher the security level, the shorter the corresponding attendance management duration. Then, for each employee, obtain the job type of the employee, query the security level corresponding to the job type, and query the time management and control duration corresponding to the security level. Finally, the employee's attendance management duration is set according to the queried result.
  • out-of-office management of the employee is described by taking an outsider as an example.
  • the duration of the attendance management and control is the basis for judging whether the outsourced personnel leave the field. If the time of the outsourcing staff attendance abnormality reaches the time limit of the attendance management, it is determined that the outsourced personnel may have left the field. In this embodiment, the duration of the attendance management corresponding to the outsourced personnel may be set to one week.
  • Step S502 obtaining attendance data of the employee.
  • the time and attendance data of each outsourcer is obtained from the attendance device or the personnel system, and the attendance data includes the attendance record and the leave record.
  • the attendance data includes the attendance record and the leave record.
  • the outsourcer records the attendance by swiping the card
  • the card record of each outsourcer is periodically obtained from the attendance machine.
  • the credit card record of each outsourcer can be obtained at the weekend.
  • the leave record can be obtained from the corresponding personnel system.
  • step S504 it is determined whether there is an employee whose attendance abnormality reaches the management time.
  • the attendance abnormality means that the outsourcer has neither a corresponding attendance record nor a leave record. If an outsourcer has an attendance abnormality and the time of the attendance abnormality reaches the length of the control, it is judged that the outsourcer may have left the scene. For example, for an outsourced person who has no credit card record within one week, it is automatically checked whether there is a leave record. If not, it is judged that the outsourcer's attendance is abnormal and has reached the length of control.
  • step S506 the authority of the abnormal employee is blocked.
  • an outsourced person whose attendance abnormality reaches the management time limit it is determined as an abnormal outsourced person, and all rights of the abnormal outsourced personnel in the workplace are automatically blocked, such as a work system account, a domain account, a mailbox, an access card, and the like.
  • the partial authority preset by the abnormal outsourcing personnel may be temporarily blocked first, and then further confirmed whether the abnormal outsourced personnel permanently removes all rights after leaving the field, and the preset partial authority is the access control card. Permissions, etc.
  • step S508 the corresponding department is automatically notified to confirm the departure.
  • a notification is automatically sent to the department corresponding to the abnormal outsourcer to confirm whether the abnormal outsourcer actually leaves the field.
  • the manner of issuing the notification may be a mail.
  • the email is automatically triggered to be sent to the department corresponding to the abnormal outsourcer, and the department is informed that the abnormal outsourcer has no credit card and leave record within one week, and the authority has been blocked. Please confirm whether it has left. If you have already left the field, you need to initiate the exit signing process as soon as possible.
  • Step S510 receiving a confirmation result corresponding to the department feedback.
  • the abnormal outsourcer needs to confirm the departure. For the confirmation of the departure personnel, it is necessary to automatically initiate the exit verification process for the personnel, and declare the departure behavior of the personnel.
  • the department's internal staff can choose the length of their vacation time (for example, 2 weeks, 1 month, 2 months) and the start and end time. The abnormal outsourcing personnel's authority will remain in the length of the selected vacation time. Blocked state, if the middle returns to work, the department can manually unlock the permission or issue an unlock request.
  • the department internal office needs to give a reasonable reason and trigger the mail to the management team for filing.
  • the confirmation result includes the abnormal outsourcing personnel confirming that the departure, the long vacation, the completion or the attendance data failure.
  • the confirmation result further includes the length of the vacation time and the start and end time.
  • Step S512 processing the authority of the abnormal employee according to the received feedback.
  • the feedback may include five situations: confirming that the user has left the field, slenderness, absenteeism, attendance data failure, and confirmation of the failure to receive feedback (the department has not done any processing). If the abnormal outsourcer is confirmed to have left the site, then all rights of the abnormal outsourcer are blocked, and an exit signing process for the abnormal outsourcer is initiated, and the process is deleted after the exit signing process is completed. Abnormal outsourcing personnel data, the subsequent no longer need to judge whether the abnormal outsourcing personnel leave the field. If the abnormal outsourcer is in the long vacation, the length of the vacation time and the start and end time of the abnormal outsourcer are obtained, and the abnormal outsourcer is set to not need attendance during the vacation, and the authority is unlocked at the end of the vacation.
  • the correction process of the attendance data failure is initiated, and the corrected attendance data is re-acquired after the correction process of the attendance data failure is completed, and then the unlocked authority is determined according to the corrected attendance data. If the abnormal outsourcer is absent or does not receive the confirmation result of the feedback, the abnormality notification is sent to the management team corresponding to the abnormal outsourcer by mail, and the processing result fed back by the management team is received.
  • the employee departure control method proposed in this embodiment can determine whether the employee has the possibility of leaving the field according to the attendance data and the length of the management time of the employee, automatically complete the authority blockade of the abnormal employee, ensure the company information security, and notify the corresponding department.
  • the abnormal employee is confirmed to leave the site, and the abnormal employee information is further processed according to the confirmation result.
  • FIG. 6 it is a schematic flowchart of a third embodiment of the employee departure control method of the present application.
  • the steps S600-S606 of the employee departure control method are similar to the steps S400-S406 of the first embodiment, except that the method further includes steps S608-S612.
  • the method includes the following steps:
  • Step S600 setting a management duration for the attendance of the employee.
  • the security level corresponding to each post type and the attendance management duration corresponding to each security level are set in advance, wherein the higher the security level, the shorter the corresponding attendance management duration. Then, for each employee, obtain the job type of the employee, query the security level corresponding to the job type, and query the time management and control duration corresponding to the security level. Finally, the employee's attendance management duration is set according to the queried result.
  • out-of-office management of the employee is described by taking an outsider as an example.
  • the duration of the attendance management is the basis for judging whether the outsourcer is out of the field. If the time of the attendance abnormality of the outsourced person reaches the duration of the attendance control, it is judged that the outsourced person may have left the field. In this embodiment, the duration of the attendance management corresponding to the outsourced personnel may be set to one week.
  • Step S602 obtaining attendance data of the employee.
  • the time and attendance data of each outsourcer is obtained from the attendance device or the personnel system, and the attendance data includes the attendance record and the leave record.
  • the attendance data includes the attendance record and the leave record.
  • the outsourcer records the attendance by swiping the card
  • the card record of each outsourcer is periodically obtained from the attendance machine.
  • the credit card record of each outsourcer can be obtained at the weekend.
  • the leave record can be obtained from the corresponding personnel system.
  • step S604 it is determined whether there is an employee whose attendance abnormality reaches the management time.
  • the attendance abnormality means that the outsourcer has neither a corresponding attendance record nor a leave record. If an outsourcer has an attendance abnormality and the time of the attendance abnormality reaches the length of the control, it is judged that the outsourcer may have left the scene. For example, for an outsourced person who has no credit card record within one week, it is automatically checked whether there is a leave record. If not, it is judged that the outsourcer's attendance is abnormal and has reached the length of control.
  • step S606 the authority of the abnormal employee is blocked.
  • an outsourced person whose attendance abnormality reaches the management time limit it is determined as an abnormal outsourced person, and all rights of the abnormal outsourced personnel in the workplace are automatically blocked, such as a work system account, a domain account, a mailbox, an access card, and the like.
  • the partial authority preset by the abnormal outsourcing personnel may be temporarily blocked first, and then further confirmed whether the abnormal outsourced personnel permanently removes all rights after leaving the field, and the preset partial authority is the access control card. Permissions, etc.
  • Step S608 notifying the abnormal employee to confirm the departure.
  • the contact information of each outsourcer such as a phone number, a mailbox, etc.
  • the contact information of each outsourcer is stored in advance.
  • the method of issuing the notification may be a short message or an email, etc., in which the abnormality of the outsourced personnel is not included in the card for one week, and the permission has been blocked. Please confirm whether the user has left the site. Field signing process. If you are on vacation, you need to initiate a vacation application process and feedback the length of vacation time and start and end time. If the attendance data is faulty, the correction process of the attendance data failure needs to be initiated, and the attendance data of the abnormal outsourcer is corrected to the correct data.
  • Step S610 receiving a confirmation result of the abnormal employee feedback.
  • the confirmation result includes the abnormal outsourcing personnel confirming that the departure has occurred, the vacation time, or the attendance data failure.
  • the confirmation result when the vacation is long, the confirmation result further includes the length of the vacation time and the start and end time.
  • Step S612 processing the authority of the abnormal employee according to the received feedback.
  • the feedback may include four cases: confirming that the user has left the field, the length of the vacation, the attendance data failure, and the confirmation result that the feedback is not received (the abnormal outsourcer has not done any processing). If the abnormal outsourcing personnel confirms that the departure has been exited, blocking all rights of the abnormal outsourcing personnel, and initiating an exit signing process for the abnormal outsourcing personnel, deleting the abnormality after the exit signing process is completed. Outsourcing personnel data, the subsequent no longer need to judge whether the abnormal outsourcing personnel leave the field. If the abnormal outsourcer is in the long vacation, the length of the vacation time and the start and end time of the abnormal outsourcer are obtained, and the abnormal outsourcer is set to not need attendance during the vacation, and the authority is unlocked at the end of the vacation.
  • the correction process of the attendance data failure is initiated, and the corrected attendance data is re-acquired after the correction process of the attendance data failure is completed, and then the unlocked authority is determined according to the corrected attendance data. If the confirmation result of the feedback is not received, the abnormality notification is sent to the management team corresponding to the abnormal outsourcer by mail, and the processing result fed back by the management team is received.
  • the employee departure control method proposed in this embodiment can determine whether the employee has the possibility of leaving the field according to the attendance data and the length of the management time of the employee, automatically complete the authority blockade of the abnormal employee, ensure the company information security, and notify the abnormality.
  • the employee confirms the departure of the employee himself and further processes the abnormal employee information based on the confirmation result.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Theoretical Computer Science (AREA)
  • Time Recorders, Dirve Recorders, Access Control (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种员工离场管控方法、应用服务器及计算机可读存储介质。该方法包括：设置针对所述员工的考勤的管控时长（S400）；获取所述员工的考勤数据（S402）；判断是否有考勤异常达到管控时长的员工（S404），若有，确定为异常员工；封锁所述异常员工的权限（S406）。该方案能够对离场员工的权限进行有效管控。

Description

员工离场管控方法、应用服务器及计算机可读存储介质
优先权申明
本申请要求于2017年11月9日提交中国专利局、申请号为201711098550.1，发明名称为“员工离场管控方法、应用服务器及计算机可读存储介质”的中国专利申请的优先权，其内容全部通过引用结合在本申请中。
技术领域
本申请涉及数据分析技术领域，尤其涉及一种员工离场管控方法、应用服务器及计算机可读存储介质。
背景技术
针对企业的外包人员，在验证通过后，会为其开通所需要的相关权限，例如UM、域、邮箱及门禁卡。在该外包人员确认离场后，需要对其权限进行封锁。但是，实际状况是经常由于部门未及时发起离场流程，导致已离场的外包人员的相关权限未及时封锁，从而产生信息安全及职场安全等风险。
发明内容
有鉴于此，本申请提出一种员工离场管控方法、应用服务器及计算机可读存储介质，以解决如何对离场员工的权限进行有效管控的问题。
首先，为实现上述目的，本申请提出一种员工离场管控方法，该方法包括步骤：
设置针对所述员工的考勤管控时长；
定时获取所述员工的考勤数据，所述考勤数据包括考勤记录和请假记录；
判断是否有考勤异常达到所述考勤管控时长的员工，所述考勤异常是指所述员工既没有对应的考勤记录，也没有请假记录，若所述员工出现考勤异常，且考勤异常的时间达到所述考勤管控时长，则将所述员工确定为异常员工；及
封锁所述异常员工的权限。
此外，为实现上述目的，本申请还提供一种应用服务器，包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的员工离场管控系统，所述员工离场管控系统被所述处理器执行时实现如上述的员工离场管控方法的步骤。
进一步地，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有员工离场管控系统，所述员工离场管控系统可被至少一个处理器执行，以使所述至少一个处理器执行如上述的员工离场管控方法的步骤。
相较于现有技术，本申请所提出的员工离场管控方法、应用服务器及计算机可读存储介质，可以根据员工的考勤数据和管控时长判断该员工是否存 在离场的可能性，自动完成对异常员工的权限封锁，保证公司信息安全，并通知对应部门或该异常员工自己进行离场确认，从而根据确认结果对该异常员工信息进行进一步处理。
附图说明
图1是本申请应用服务器一可选的硬件架构的示意图；
图2是本申请员工离场管控系统第一实施例的程序模块示意图；
图3是本申请员工离场管控系统第二实施例和第三实施例的程序模块示意图；
图4是本申请员工离场管控方法第一实施例的流程示意图；
图5是本申请员工离场管控方法第二实施例的流程示意图；
图6是本申请员工离场管控方法第三实施例的流程示意图。
附图标记：
应用服务器 2
存储器 11
处理器 12
网络接口 13
员工离场管控系统 200
设置模块 201
获取模块 202
判断模块 203
封锁模块 204
通知模块 205
接收模块 206
处理模块 207
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及 实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
需要说明的是，在本申请中涉及“第一”、“第二”等的描述仅用于描述目的，而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外，各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本申请要求的保护范围之内。
参阅图1所示，是本申请应用服务器2一可选的硬件架构的示意图。
本实施例中，所述应用服务器2可包括，但不仅限于，可通过系统总线相互通信连接存储器11、处理器12、网络接口13。需要指出的是，图1仅示出了具有组件11-13的应用服务器2，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
其中，所述应用服务器2可以是机架式服务器、刀片式服务器、塔式服务器或机柜式服务器等计算设备，该应用服务器2可以是独立的服务器，也可以是多个服务器所组成的服务器集群。
所述存储器11至少包括一种类型的可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，所述存储器11可以是所述应用服务器2的内部存储单元，例如该应用服务器2的硬盘或内存。在另一些实施例中，所述存储器11也可以是所述应用服务器2的外部存储设备，例如该应用服务器2上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，所述存储器11还可以既包括所述应用服务器2的内部存储单元也包括其外部存储设备。本实施例中，所述存储器11通常用于存储安装于所述应用服务器2的操作系统和各类应用软件，例如员工离场管控系统200的程序代码等。此外，所述存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器12在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器12通常用于控制所述应用服务器2的总体操作。本实施例中，所述处理器12用于运行所述存储器11中存储的程序代码或者处理数据，例如运行所述的员工离场管控系统200等。
所述网络接口13可包括无线网络接口或有线网络接口，该网络接口13 通常用于在所述应用服务器2与其他电子设备之间建立通信连接。
至此，己经详细介绍了本申请相关设备的硬件结构和功能。下面，将基于上述介绍提出本申请的各个实施例。
首先，本申请提出一种员工离场管控系统200。
参阅图2所示，是本申请员工离场管控系统200第一实施例的程序模块图。
本实施例中，所述员工离场管控系统200包括一系列的存储于存储器11上的计算机程序指令，当该计算机程序指令被处理器12执行时，可以实现本申请各实施例的员工离场管控操作。在一些实施例中，基于该计算机程序指令各部分所实现的特定的操作，员工离场管控系统200可以被划分为一个或多个模块。例如，在图2中，所述员工离场管控系统200可以被分割成设置模块201、获取模块202、判断模块203、封锁模块204。其中：
所述设置模块201，用于设置针对所述员工的考勤的管控时长。
具体地，预先设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短。然后，针对每个员工，获取所述员工的岗位类型，查询所述岗位类型对应的安全级别，查询所述安全级别对应的考勤管控时长。最后，根据所查询到的结果设置所述员工的考勤管控时长。
在本实施例中，以外包人员为例对所述员工的离场管控进行说明。
所述考勤管控时长是判断外包人员是否离场的依据，若外包人员考勤异常的时间达到所述考勤管控时长，则判断该外包人员可能已离场。在本实施例中，可以设置外包人员对应的所述考勤管控时长为一周。
所述获取模块202，用于获取所述员工的考勤数据。
具体地，定时从考勤装置或人事系统中获取每个外包人员的考勤数据，所述考勤数据包括考勤记录和请假记录。例如，若外包人员以刷卡的方式记录考勤，则定时从考勤机上获取每个外包人员的刷卡记录。在本实施例中，可以在每周末定时获取每个外包人员的刷卡记录。所述请假记录可以从相应的人事系统中获取。
所述判断模块203，用于判断是否有考勤异常达到管控时长的员工。
具体地，所述考勤异常是指该外包人员既没有对应的考勤记录，也没有请假记录。若某一外包人员出现考勤异常，且考勤异常的时间达到所述管控时长，则判断该外包人员可能已经离场。例如，对于一周内无刷卡记录的外包人员，自动核查其是否有请假记录，若无，则判断该外包人员考勤异常且已达到管控时长。
所述封锁模块204，用于封锁异常员工的权限。
具体地，对于考勤异常达到管控时长的外包人员，将其确定为异常外包人员，自动封锁该异常外包人员在该工作场所的权限，例如工作系统账号、域账号、邮箱、门禁卡等。在本实施例中，可以先临时封锁所述异常外包人 员预设的部分权限，后续进一步确认所述异常外包人员是否离场后再永久封锁所有权限，所述预设的部分权限为门禁卡的权限等。
参阅图3所示，是本申请员工离场管控系统200第二实施例和第三实施例的程序模块图。本第二实施例和第三实施例中，所述的员工离场管控系统200除了包括第一实施例中的所述设置模块201、获取模块202、判断模块203、封锁模块204之外，还包括通知模块205、接收模块206、处理模块207。
在第二实施例中，所述通知模块205用于自动通知对应部门进行离场确认。
具体地，在封锁该异常外包人员的权限的同时，自动向该异常外包人员对应的部门内勤发出通知，使其确认该异常外包人员是否确实离场。在本实施例中，所述发出通知的方式可以是邮件。例如，在封锁权限的同时，自动触发邮件发送至该异常外包人员对应的部门内勤，告知部门内勤该异常外包人员因一周内无任何刷卡及请假记录，权限已被封锁，请确认其是否已经离场，若已离场需尽快发起离场签核流程。
所述接收模块206用于接收对应部门反馈的确认结果。
具体地，当对应部门内勤收到该通知后，需要对该异常外包人员进行离场确认。对于确认离场人员，需要自动发起针对于该人员的离场签核流程，对该人员的离场行为进行申报。对于休长假的异常外包人员，部门内勤可以选择其休假时间长度(例如2周、1个月、2个月)和起止时间，在所选择的休假时间长度内该异常外包人员的权限仍会处于封锁状态，若其中间返回上班，部门内勤可手动解锁权限或发出解锁请求。对于休假时间长度超过预设期限(例如1个月)的外包人员，部门内勤需要给出合理的原因，并触发邮件给管理团队做备案。对于未请假(旷工)的异常外包人员，也需要触发邮件给管理团队做备案。另外，还有可能是考勤数据故障，需要发起考勤数据故障的修正流程，将该异常外包人员的考勤数据修正为正确的数据。
然后，对应部门内勤将确认结果进行反馈。所述确认结果包括该异常外包人员确认已离场、休长假中、旷工或考勤数据故障。其中，当休长假时，所述确认结果还包括休假时间长度和起止时间。
所述处理模块207用于根据收到的反馈处理该异常员工的权限。
具体地，所述反馈可能包括五种情况：确认已离场、修长假中、旷工、考勤数据故障、未收到反馈的确认结果(部门内勤未做任何处理)。若该异常外包人员被确认已离场，则封锁所述异常外包人员的所有权限，并发起对所述异常外包人员的离场签核流程，在所述离场签核流程完结后删除所述异常外包人员数据，后续不再需要对该异常外包人员进行是否离场的判断。若该异常外包人员在休长假中，则获取所述异常外包人员的休假时间长度和起止时间，设定所述异常外包人员在所述休假期间无需考勤，并在休假结束时解锁权限。若是考勤数据故障，则发起考勤数据故障的修正流程，在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的 考勤数据判断是否解锁权限。若该异常外包人员旷工或者未收到反馈的确认结果，通过邮件向所述异常外包人员对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
进一步地，在第三实施例中，所述通知模块205还用于通知所述异常员工进行离场确认。
具体地，预先保存每个外包人员的联系方式，例如电话号码、邮箱等。当判断出异常外包人员后，在封锁权限的同时，读取所述异常外包人员对应的联系方式，根据该联系方式将当前的考勤状况和权限封锁情况发送至所述异常外包人员，使所述异常外包人员确认是否离场，并根据实际情况进行相应处理。发出通知的方式可以是短信或邮件等，在该通知中告知该异常外包人员因一周内无任何刷卡及请假记录，权限已被封锁，请确认是否已经离场，若已离场需尽快发起离场签核流程。若是在休长假中，则需要发起休假申请流程，并反馈休假时间长度和起止时间。若是考勤数据故障，则需要发起考勤数据故障的修正流程，将该异常外包人员的考勤数据修正为正确的数据。
所述接收模块206还用于接收所述异常员工反馈的确认结果。
具体地，所述确认结果包括该异常外包人员确认已离场、休长假中或考勤数据故障。其中，当休长假时，所述确认结果还包括休假时间长度和起止时间。
所述处理模块207还用于根据收到的反馈处理该异常员工的权限。
具体地，所述反馈可能包括四种情况：确认已离场、修长假中、考勤数据故障、未收到反馈的确认结果(该异常外包人员未做任何处理)。若该异常外包人员确认已离场，则封锁所述异常外包人员的所有权限，并发起对所述异常外包人员的离场签核流程，在所述离场签核流程完结后删除所述异常外包人员数据，后续不再需要对该异常外包人员进行是否离场的判断。若该异常外包人员在休长假中，则获取所述异常外包人员的休假时间长度和起止时间，设定所述异常外包人员在所述休假期间无需考勤，并在休假结束时解锁权限。若是考勤数据故障，则发起考勤数据故障的修正流程，并在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的考勤数据判断是否解锁权限。若未收到反馈的确认结果，则通过邮件向所述异常外包人员对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
此外，本申请还提出一种员工离场管控方法。
参阅图4所示，是本申请员工离场管控方法第一实施例的流程示意图。在本实施例中，根据不同的需求，图4所示的流程图中的步骤的执行顺序可以改变，某些步骤可以省略。
步骤S400，设置针对所述员工的考勤的管控时长。
具体地，预先设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短。然后，针对 每个员工，获取所述员工的岗位类型，查询所述岗位类型对应的安全级别，查询所述安全级别对应的考勤管控时长。最后，根据所查询到的结果设置所述员工的考勤管控时长。
在本实施例中，以外包人员为例对所述员工的离场管控进行说明。
所述考勤管控时长是判断外包人员是否离场的依据，若外包人员考勤异常的时间达到所述考勤管控时长，则判断该外包人员可能已离场。在本实施例中，可以设置外包人员对应的所述考勤管控时长为一周。
步骤S402，获取所述员工的考勤数据。
具体地，定时从考勤装置或人事系统中获取每个外包人员的考勤数据，所述考勤数据包括考勤记录和请假记录。例如，若外包人员以刷卡的方式记录考勤，则定时从考勤机上获取每个外包人员的刷卡记录。在本实施例中，可以在每周末定时获取每个外包人员的刷卡记录。所述请假记录可以从相应的人事系统中获取。
步骤S404，判断是否有考勤异常达到管控时长的员工。
具体地，所述考勤异常是指该外包人员既没有对应的考勤记录，也没有请假记录。若某一外包人员出现考勤异常，且考勤异常的时间达到所述管控时长，则判断该外包人员可能已经离场。例如，对于一周内无刷卡记录的外包人员，自动核查其是否有请假记录，若无，则判断该外包人员考勤异常且已达到管控时长。
步骤S406，封锁异常员工的权限。
具体地，对于考勤异常达到管控时长的外包人员，将其确定为异常外包人员，自动封锁该异常外包人员在该工作场所的所有权限，例如工作系统账号、域账号、邮箱、门禁卡等。在本实施例中，可以先临时封锁所述异常外包人员预设的部分权限，后续进一步确认所述异常外包人员是否离场后再永久封锁所有权限，所述预设的部分权限为门禁卡的权限等。
本实施例所提出的员工离场管控方法，可以根据员工的考勤数据和管控时长判断该员工是否存在离场的可能性，自动完成对异常员工的权限封锁，保证公司信息安全。
如图5所示，是本申请员工离场管控方法的第二实施例的流程示意图。本实施例中，所述员工离场管控方法的步骤S500-S506与第一实施例的步骤S400-S406相类似，区别在于该方法还包括步骤S508-S512。
该方法包括以下步骤：
步骤S500，设置针对所述员工的考勤的管控时长。
具体地，预先设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短。然后，针对每个员工，获取所述员工的岗位类型，查询所述岗位类型对应的安全级别，查询所述安全级别对应的考勤管控时长。最后，根据所查询到的结果设置所述员工的考勤管控时长。
在本实施例中，以外包人员为例对所述员工的离场管控进行说明。
所述考勤管控时长是判断外包人员是否离场的依据，若外包人员考勤异常的时间达到所述考勤管控时长，则判断该外包人员可能已离场。在本实施例中，可以设置外包人员对应的所述考勤管控时长为一周。
步骤S502，获取所述员工的考勤数据。
具体地，定时从考勤装置或人事系统中获取每个外包人员的考勤数据，所述考勤数据包括考勤记录和请假记录。例如，若外包人员以刷卡的方式记录考勤，则定时从考勤机上获取每个外包人员的刷卡记录。在本实施例中，可以在每周末定时获取每个外包人员的刷卡记录。所述请假记录可以从相应的人事系统中获取。
步骤S504，判断是否有考勤异常达到管控时长的员工。
具体地，所述考勤异常是指该外包人员既没有对应的考勤记录，也没有请假记录。若某一外包人员出现考勤异常，且考勤异常的时间达到所述管控时长，则判断该外包人员可能已经离场。例如，对于一周内无刷卡记录的外包人员，自动核查其是否有请假记录，若无，则判断该外包人员考勤异常且已达到管控时长。
步骤S506，封锁异常员工的权限。
具体地，对于考勤异常达到管控时长的外包人员，将其确定为异常外包人员，自动封锁该异常外包人员在该工作场所的所有权限，例如工作系统账号、域账号、邮箱、门禁卡等。在本实施例中，可以先临时封锁所述异常外包人员预设的部分权限，后续进一步确认所述异常外包人员是否离场后再永久封锁所有权限，所述预设的部分权限为门禁卡的权限等。
步骤S508，自动通知对应部门进行离场确认。
具体地，在封锁该异常外包人员的权限的同时，自动向该异常外包人员对应的部门内勤发出通知，使其确认该异常外包人员是否确实离场。在本实施例中，所述发出通知的方式可以是邮件。例如，在封锁权限的同时，自动触发邮件发送至该异常外包人员对应的部门内勤，告知部门内勤该异常外包人员因一周内无任何刷卡及请假记录，权限已被封锁，请确认其是否已经离场，若已离场需尽快发起离场签核流程。
步骤S510，接收对应部门反馈的确认结果。
具体地，当对应部门内勤收到该通知后，需要对该异常外包人员进行离场确认。对于确认离场人员，需要自动发起针对于该人员的离场签核流程，对该人员的离场行为进行申报。对于休长假的异常外包人员，部门内勤可以选择其休假时间长度(例如2周、1个月、2个月)和起止时间，在所选择的休假时间长度内该异常外包人员的权限仍会处于封锁状态，若其中间返回上班，部门内勤可手动解锁权限或发出解锁请求。对于休假时间长度超过预设期限(例如1个月)的外包人员，部门内勤需要给出合理的原因，并触发邮件给管理团队做备案。对于未请假(旷工)的异常外包人员，也需要触发邮件给管理团队做备案。另外，还有可能是考勤数据故障，需要发起考勤数据 故障的修正流程，将该异常外包人员的考勤数据修正为正确的数据。
然后，对应部门内勤将确认结果进行反馈。所述确认结果包括该异常外包人员确认已离场、休长假中、旷工或考勤数据故障。其中，当休长假时，所述确认结果还包括休假时间长度和起止时间。
步骤S512，根据收到的反馈处理该异常员工的权限。
具体地，所述反馈可能包括五种情况：确认已离场、修长假中、旷工、考勤数据故障、未收到反馈的确认结果(部门内勤未做任何处理)。若该异常外包人员被确认已离场，则封锁所述异常外包人员的所有权限，并发起对所述异常外包人员的离场签核流程，在所述离场签核流程完结后删除所述异常外包人员数据，后续不再需要对该异常外包人员进行是否离场的判断。若该异常外包人员在休长假中，则获取所述异常外包人员的休假时间长度和起止时间，设定所述异常外包人员在所述休假期间无需考勤，并在休假结束时解锁权限。若是考勤数据故障，则发起考勤数据故障的修正流程，在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的考勤数据判断是否解锁权限。若该异常外包人员旷工或者未收到反馈的确认结果，通过邮件向所述异常外包人员对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
本实施例所提出的员工离场管控方法，可以根据员工的考勤数据和管控时长判断该员工是否存在离场的可能性，自动完成对异常员工的权限封锁，保证公司信息安全，并通知对应部门对该异常员工进行离场确认，从而根据确认结果对该异常员工信息进行进一步处理。
如图6所示，是本申请员工离场管控方法的第三实施例的流程示意图。本实施例中，所述员工离场管控方法的步骤S600-S606与第一实施例的步骤S400-S406相类似，区别在于该方法还包括步骤S608-S612。
该方法包括以下步骤：
步骤S600，设置针对所述员工的考勤的管控时长。
具体地，预先设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短。然后，针对每个员工，获取所述员工的岗位类型，查询所述岗位类型对应的安全级别，查询所述安全级别对应的考勤管控时长。最后，根据所查询到的结果设置所述员工的考勤管控时长。
在本实施例中，以外包人员为例对所述员工的离场管控进行说明。
所述考勤管控时长是判断外包人员是否离场的依据，若外包人员考勤异常的时间达到所述考勤管控时长，则判断该外包人员可能已离场。在本实施例中，可以设置外包人员对应的所述考勤管控时长为一周。
步骤S602，获取所述员工的考勤数据。
具体地，定时从考勤装置或人事系统中获取每个外包人员的考勤数据，所述考勤数据包括考勤记录和请假记录。例如，若外包人员以刷卡的方式记 录考勤，则定时从考勤机上获取每个外包人员的刷卡记录。在本实施例中，可以在每周末定时获取每个外包人员的刷卡记录。所述请假记录可以从相应的人事系统中获取。
步骤S604，判断是否有考勤异常达到管控时长的员工。
具体地，所述考勤异常是指该外包人员既没有对应的考勤记录，也没有请假记录。若某一外包人员出现考勤异常，且考勤异常的时间达到所述管控时长，则判断该外包人员可能已经离场。例如，对于一周内无刷卡记录的外包人员，自动核查其是否有请假记录，若无，则判断该外包人员考勤异常且已达到管控时长。
步骤S606，封锁异常员工的权限。
具体地，对于考勤异常达到管控时长的外包人员，将其确定为异常外包人员，自动封锁该异常外包人员在该工作场所的所有权限，例如工作系统账号、域账号、邮箱、门禁卡等。在本实施例中，可以先临时封锁所述异常外包人员预设的部分权限，后续进一步确认所述异常外包人员是否离场后再永久封锁所有权限，所述预设的部分权限为门禁卡的权限等。
步骤S608，通知所述异常员工进行离场确认。
具体地，预先保存每个外包人员的联系方式，例如电话号码、邮箱等。当判断出异常外包人员后，在封锁权限的同时，读取所述异常外包人员对应的联系方式，根据该联系方式将当前的考勤状况和权限封锁情况发送至所述异常外包人员，使所述异常外包人员确认是否离场，并根据实际情况进行相应处理。发出通知的方式可以是短信或邮件等，在该通知中告知该异常外包人员因一周内无任何刷卡及请假记录，权限已被封锁，请确认是否已经离场，若已离场需尽快发起离场签核流程。若是在休长假中，则需要发起休假申请流程，并反馈休假时间长度和起止时间。若是考勤数据故障，则需要发起考勤数据故障的修正流程，将该异常外包人员的考勤数据修正为正确的数据。
步骤S610，接收所述异常员工反馈的确认结果。
具体地，所述确认结果包括该异常外包人员确认已离场、休长假中或考勤数据故障。其中，当休长假时，所述确认结果还包括休假时间长度和起止时间。
步骤S612，根据收到的反馈处理该异常员工的权限。
具体地，所述反馈可能包括四种情况：确认已离场、修长假中、考勤数据故障、未收到反馈的确认结果(该异常外包人员未做任何处理)。若该异常外包人员确认已离场，则封锁所述异常外包人员的所有权限，并发起对所述异常外包人员的离场签核流程，在所述离场签核流程完结后删除所述异常外包人员数据，后续不再需要对该异常外包人员进行是否离场的判断。若该异常外包人员在休长假中，则获取所述异常外包人员的休假时间长度和起止时间，设定所述异常外包人员在所述休假期间无需考勤，并在休假结束时解锁权限。若是考勤数据故障，则发起考勤数据故障的修正流程，并在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的 考勤数据判断是否解锁权限。若未收到反馈的确认结果，则通过邮件向所述异常外包人员对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
本实施例所提出的员工离场管控方法，可以根据员工的考勤数据和管控时长判断该员工是否存在离场的可能性，自动完成对异常员工的权限封锁，保证公司信息安全，并通知该异常员工自己进行离场确认，从而根据确认结果对该异常员工信息进行进一步处理。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种员工离场管控方法，应用于应用服务器，其特征在于，所述方法包括步骤：
    设置针对所述员工的考勤管控时长；
    定时获取所述员工的考勤数据，所述考勤数据包括考勤记录和请假记录；
    判断是否有考勤异常达到所述考勤管控时长的员工，所述考勤异常是指所述员工既没有对应的考勤记录，也没有请假记录，若所述员工出现考勤异常，且考勤异常的时间达到所述考勤管控时长，则将所述员工确定为异常员工；及
    封锁所述异常员工的权限。
  2. 如权利要求1所述的员工离场管控方法，其特征在于，所述设置针对所述员工的考勤管控时长的步骤包括：
    设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短；
    获取所述员工的岗位类型；
    查询所述岗位类型对应的安全级别；
    查询所述安全级别对应的考勤管控时长；
    根据所查询到的结果设置所述员工的考勤管控时长。
  3. 如权利要求1所述的员工离场管控方法，其特征在于，所述封锁所述异常员工的权限的步骤包括：临时封锁所述异常员工预设的部分权限，所述预设的部分权限包括门禁卡。
  4. 如权利要求3所述的员工离场管控方法，其特征在于，所述封锁所述异常员工的权限的步骤还包括：
    通过邮件向所述异常员工的对应部门发送离场确认通知；
    接收对应部门反馈的确认结果；
    根据收到的反馈处理所述异常员工的权限。
  5. 如权利要求3所述的员工离场管控方法，其特征在于，所述封锁所述异常员工的权限的步骤还包括：
    通过邮件或短信向所述异常员工发送离场确认通知；
    接收所述异常员工反馈的确认结果；
    根据收到的反馈处理所述异常员工的权限。
  6. 如权利要求4或5所述的员工离场管控方法，其特征在于，所述确认结果包括：已离场、休长假中、旷工或考勤数据故障；
    所述根据收到的反馈处理所述异常员工的权限的步骤具体包括：
    当所述异常员工被确认已离场时，封锁所述异常员工的所有权限，并发起对所述异常员工的离场签核流程；
    当所述异常员工被确认在休长假中时，获取所述异常员工的休假时间长度和起止时间，设定所述异常员工在所述休假期间无需考勤；
    当所述异常员工被确认考勤数据故障时，发起考勤数据故障的修正流程。
  7. 如权利要求6所述的员工离场管控方法，其特征在于，所述根据收到的反馈处理所述异常外包员工的权限的步骤还包括：
    若所述异常员工被确认已离场，则在所述离场签核流程完结后删除所述异常员工数据，后续不再需要对该异常员工进行是否离场的判断；
    若所述异常员工被确认在休长假中，则在休假结束时解锁权限；
    若所述异常员工被确认考勤数据故障，则在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的考勤数据判断是否解锁权限。
  8. 如权利要求6所述的员工离场管控方法，其特征在于，所述根据收到的反馈处理所述异常外包员工的权限的步骤还包括：
    若所述异常员工被确认旷工或者未收到反馈的确认结果，通过邮件向所述异常员工对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
  9. 一种应用服务器，其特征在于，所述应用服务器包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的员工离场管控系统，所述员工离场管控系统被所述处理器执行时实现如下步骤：
    设置针对所述员工的考勤管控时长；
    定时获取所述员工的考勤数据，所述考勤数据包括考勤记录和请假记录；
    判断是否有考勤异常达到所述考勤管控时长的员工，所述考勤异常是指所述员工既没有对应的考勤记录，也没有请假记录，若所述员工出现考勤异常，且考勤异常的时间达到所述考勤管控时长，则将所述员工确定为异常员工；及
    封锁所述异常员工的权限。
  10. 如权利要求9所述的应用服务器，其特征在于，所述设置针对所述员工的考勤管控时长的步骤包括：
    设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时长，其中安全级别越高，对应的考勤管控时长越短；
    获取所述员工的岗位类型；
    查询所述岗位类型对应的安全级别；
    查询所述安全级别对应的考勤管控时长；
    根据所查询到的结果设置所述员工的考勤管控时长。
  11. 如权利要求9所述的应用服务器，其特征在于，所述封锁所述异常员工的权限的步骤包括：临时封锁所述异常员工预设的部分权限，所述预设的部分权限包括门禁卡。
  12. 如权利要求11所述的应用服务器，其特征在于，所述封锁所述异常员工的权限的步骤还包括：
    通过邮件向所述异常员工的对应部门发送离场确认通知；
    接收对应部门反馈的确认结果；
    根据收到的反馈处理所述异常员工的权限。
  13. 如权利要求11所述的应用服务器，其特征在于，所述封锁所述异常员工的权限的步骤还包括：
    通过邮件或短信向所述异常员工发送离场确认通知；
    接收所述异常员工反馈的确认结果；
    根据收到的反馈处理所述异常员工的权限。
  14. 如权利要求12或13所述的应用服务器，其特征在于，所述确认结果包括：已离场、休长假中、旷工或考勤数据故障；
    所述根据收到的反馈处理所述异常员工的权限的步骤具体包括：
    当所述异常员工被确认已离场时，封锁所述异常员工的所有权限，并发起对所述异常员工的离场签核流程；
    当所述异常员工被确认在休长假中时，获取所述异常员工的休假时间长度和起止时间，设定所述异常员工在所述休假期间无需考勤；
    当所述异常员工被确认考勤数据故障时，发起考勤数据故障的修正流程。
  15. 如权利要求14所述的应用服务器，其特征在于，所述根据收到的反馈处理所述异常外包员工的权限的步骤还包括：
    若所述异常员工被确认已离场，则在所述离场签核流程完结后删除所述异常员工数据，后续不再需要对该异常员工进行是否离场的判断；
    若所述异常员工被确认在休长假中，则在休假结束时解锁权限；
    若所述异常员工被确认考勤数据故障，则在所述考勤数据故障的修正流程完结后重新获取修正后的考勤数据，然后根据修正后的考勤数据判断是否解锁权限。
  16. 如权利要求14所述的应用服务器，其特征在于，所述根据收到的反馈处理所述异常外包员工的权限的步骤还包括：
    若所述异常员工被确认旷工或者未收到反馈的确认结果，通过邮件向所述异常员工对应的管理团队发送异常通知，并接收所述管理团队反馈的处理结果。
  17. 一种计算机可读存储介质，所述计算机可读存储介质存储有员工离场管控系统，所述员工离场管控系统可被至少一个处理器执行，以使所述至少一个处理器执行如下步骤：
    设置针对所述员工的考勤管控时长；
    定时获取所述员工的考勤数据，所述考勤数据包括考勤记录和请假记录；
    判断是否有考勤异常达到所述考勤管控时长的员工，所述考勤异常是指所述员工既没有对应的考勤记录，也没有请假记录，若所述员工出现考勤异常，且考勤异常的时间达到所述考勤管控时长，则将所述员工确定为异常员工；及
    封锁所述异常员工的权限。
  18. 如权利要求17所述的计算机可读存储介质，其特征在于，所述设置针对所述员工的考勤管控时长的步骤包括：
    设置每种岗位类型对应的安全级别和每种安全级别对应的考勤管控时 长，其中安全级别越高，对应的考勤管控时长越短；
    获取所述员工的岗位类型；
    查询所述岗位类型对应的安全级别；
    查询所述安全级别对应的考勤管控时长；
    根据所查询到的结果设置所述员工的考勤管控时长。
  19. 如权利要求17所述的计算机可读存储介质，其特征在于，所述封锁所述异常员工的权限的步骤包括：临时封锁所述异常员工预设的部分权限，所述预设的部分权限包括门禁卡。
  20. 如权利要求19所述的计算机可读存储介质，其特征在于，所述封锁所述异常员工的权限的步骤还包括：
    通过邮件向所述异常员工的对应部门发送离场确认通知；
    接收对应部门反馈的确认结果；
    根据收到的反馈处理所述异常员工的权限。
PCT/CN2018/089345 2017-11-09 2018-05-31 员工离场管控方法、应用服务器及计算机可读存储介质 WO2019091099A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711098550.1A CN108256819A (zh) 2017-11-09 2017-11-09 员工离场管控方法、应用服务器及计算机可读存储介质
CN201711098550.1 2017-11-09

Publications (1)

Publication Number Publication Date
WO2019091099A1 true WO2019091099A1 (zh) 2019-05-16

Family

ID=62722130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/089345 WO2019091099A1 (zh) 2017-11-09 2018-05-31 员工离场管控方法、应用服务器及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN108256819A (zh)
WO (1) WO2019091099A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109544091B (zh) * 2018-10-11 2023-05-30 平安科技（深圳）有限公司 基于人工智能的离场效率评定方法、装置、计算机设备
CN109636933B (zh) * 2018-11-09 2022-07-15 平安科技（深圳）有限公司 基于基架运维的智能人员管理方法、装置及计算机设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996430A (zh) * 2009-08-28 2011-03-30 中国移动通信集团公司 一种短信预约刷门禁的方法、系统及装置
CN103400235A (zh) * 2013-08-14 2013-11-20 常熟合正企业管理咨询有限公司 一种企业出勤记录系统
CN104299283A (zh) * 2014-09-24 2015-01-21 孙浩 考勤管理系统
CN104794768A (zh) * 2015-04-24 2015-07-22 凯拔（中国）科技有限公司 定时自动运行考勤计算的考勤系统及考勤方法
CN106203936A (zh) * 2016-06-23 2016-12-07 郭进标 一种考勤管理系统及方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1581180A (zh) * 2003-08-09 2005-02-16 鸿富锦精密工业（深圳）有限公司 员工出勤动态管控系统及方法
CN106940903A (zh) * 2016-01-05 2017-07-11 平安科技（深圳）有限公司 考勤方法、装置和系统
CN106548328A (zh) * 2016-11-30 2017-03-29 北京恒华伟业科技股份有限公司 考勤统计系统及方法
CN107195012A (zh) * 2017-06-26 2017-09-22 广东乐源数字技术有限公司 一种员工打卡系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996430A (zh) * 2009-08-28 2011-03-30 中国移动通信集团公司 一种短信预约刷门禁的方法、系统及装置
CN103400235A (zh) * 2013-08-14 2013-11-20 常熟合正企业管理咨询有限公司 一种企业出勤记录系统
CN104299283A (zh) * 2014-09-24 2015-01-21 孙浩 考勤管理系统
CN104794768A (zh) * 2015-04-24 2015-07-22 凯拔（中国）科技有限公司 定时自动运行考勤计算的考勤系统及考勤方法
CN106203936A (zh) * 2016-06-23 2016-12-07 郭进标 一种考勤管理系统及方法

Also Published As

Publication number Publication date
CN108256819A (zh) 2018-07-06

Similar Documents

Publication Publication Date Title
WO2019095676A1 (zh) 员工个人考勤管控方法、应用服务器及计算机可读存储介质
CN111008069B (zh) 业务处理方法、装置、计算机设备和存储介质
US20170366550A1 (en) Targeted user access control system
US9047459B2 (en) Electronic device and method for resetting unlocking password of the electronic device
WO2019141008A1 (zh) 一种基于网络通讯的身份认证方法及计算机设备
WO2019019636A1 (zh) 用户身份识别方法、电子装置及计算机可读存储介质
WO2020233356A1 (zh) 测试环境控制方法、装置、计算机可读存储介质及服务器
WO2019091099A1 (zh) 员工离场管控方法、应用服务器及计算机可读存储介质
BRPI0916193B1 (pt) METODO PARA PERMITIR UMA LOCALIZAQAO DO DISPOSITIVO DE COMPUTAQAO DO USUARIO A SER MONITORADO A PARTIR DE UMA LOCALIZAQAO REMOTA, MEIO LEGlVEL POR COMPUTADOR E SISTEMA PARA A PROTEQAO DE DADOS PRIVADOS ENQUANTO MONITORANDO UM DISPOSITIVO ELETRONICO
US11544409B2 (en) Data processing systems and methods for automatically protecting sensitive data within privacy management systems
US20170272426A1 (en) Secure document storage and retrieval
WO2014082399A1 (zh) 移动终端管理方法和系统
WO2020215687A1 (zh) 数据传输监控方法、装置、计算机设备及存储介质
US20200314109A1 (en) Time-based server access
US20150233733A1 (en) Distribution interconnection information systems and methods
WO2019169771A1 (zh) 电子装置、访问指令信息获取方法及存储介质
US20210335462A1 (en) System and Method for Providing Access to Digital Assets Upon Occurrence of a Predetermined Event
CN110516450B (zh) 数据获取权限管控方法、电子装置及计算机可读存储介质
CN106911680B (zh) 一种策略下发方法及装置
CN111008716A (zh) 基于ai的会议室分段预约方法、装置、计算机设备及存储介质
WO2019205293A1 (zh) 一种业务权限管理方法、装置、计算机设备及存储介质
EP4060530A1 (en) Data management method and device
WO2019062016A1 (zh) 电子装置、外包人员选聘方法及存储介质
JP6747178B2 (ja) プログラム及び認証装置
JP2016018352A (ja) 作業実行管理システム及び作業実行管理方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18877018

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13/08/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18877018

Country of ref document: EP

Kind code of ref document: A1