Application Operating Process/Leave request, Leader's approval, Administrator's confirmation

Information about employees' days off is to be shared in the whole section. Also, the unit needs such information so that it can supervise the number of days off. Therefore, a leader's certain confirmation or a Business Process which allows administration of the whole company, has come to be necessary. Also, an expected Business Process shortens the approval time, considering that an administrator's real-time confirmations is unnecessary.

Summary

 * 1) An employee fulfills a leave request form.
 * 2) The employee submits the form to the leader of her/his division.
 * 3) The leader confirms the form.
 * 4) The person in charge of application confirms the request result.
 * 5) The leader submits it to the administrator of the applicant's division.
 * 6) The administrator confirms the submitted leave request.
 * 7) The administrator submits it to the personnel department.
 * 8) The personnel department registers the leave request to an in-house system.

People In Charge Of The Process (Participants)

 * Arbitrary section (any-section@company.com)
 * Administrator (section-parent-leader@company.com)
 * Leader (section-leader@company.com)
 * Applicant (person@company.com)
 * Personnel department (personnel@company.com)

The leader sees how applicant's work progresses and s/he adjusts duties etc. The administrator is in charge of personnel management, as well as the number of applications during year, etc.

Process Owner
A leave request should be the same business process in all sections. It is very likely that request results are administered all together. Therefore, a united Business Process based on general management is necessary, and the personnel department is expected to be the Process Owner.
 * Personnel department (personnel@company.com)

Advantages/Disadvantages
Advantages
 * Simplicity of application route
 * Because the application route is very simple, usability is high.


 * Speedup of application approval
 * A leader's approval to applications shortens the route up to completion of application approval, and the time from application to approval completion is expected to be shortened.

Disadvantages
 * Management after application rejection
 * When a request is rejected, the applicant does it over, and there is no way to know whether the application is made again. Even when the administrator rejects a leave request, the leader has no way to know it.


 * Authority to reject applications
 * The administrator cannot cancel any requests.


 * Impossibility of request cancellation
 * Because an application once made is supposed to be always operated, the application cannot be canceled.

Timing for Application
The timing for application depends on the working regulation in each enterprise. Labor Standards Law does not precise how many days earlier an application should be submitted. However, it is assumed that an application on that day cannot be accepted because it is possible that the application will be rejected, and that an applicant submits the schedule several days earlier.
 * Timing for a leave request

A worker basically has the right to take vacation any time. However, in the case when letting a worker take paid vacation may disturb regular management of the business, it can be given to the worker at another time.
 * Rejection of a leave request

Diagram Example
digraph horidayG { graph [size="13,10", rankdir=LR]; node [shape=box, style=rounded]; edge [labelfloat=true];

subgraph clusterS { labeljust=l; label="any-section@company.com"; subgraph clusterp { labeljust=l; label="person@company.com(Applicant)"; PS [label="", shape=circle, width="0.3"]; PE [label="", shape=circle, width="0.3", style=bold]; PS1 [label="PS1:Entery of leave \nrequest information"]; PS2 [label="PS2:Result confirmation\nApproval confirmation"]; PS->PS1 [weight=10]; PS1->PS2 [style=invis,weigth=10]; PS2->PE [weight=10]; } subgraph clusterm { labeljust=l; label="section-parent-leader@company.com(Administrator)"; MS1 [label="MS1:Approval operation\nRequest confirmation"]; } subgraph clusterl { labeljust=l; label="section-leader@company.com(Leader)"; LS1 [label="LS1:Approval\nApproval operation"]; }

PS1 -> LS1 [weight=100,tailport=n,headport=nw]; LS1 -> MS1 [arrowtail=odiamond, label="Approved",tailport=s]; LS1 -> PS1 [arrowtail=odiamond,label="Rejected",tailport=w,headport=e]; LS1 -> PS2 [arrowtail=odiamond,label="Approved", weight=10]; {rank=same;MS1,LS1}; }

subgraph clusterPN { labeljust=l; label="personnel@company.com(Personnel)"; PN1 [label="PN1:Registration\nof the request"]; PNE [label="", shape=circle, width="0.3", style=bold]; PN1 -> PNE [weight=10]; } MS1 -> PN1 [label="Confirmation",headport=se,tailport=w]; {rank=same;MS1,PN1} }