Application Operating Process/Leave request, Leader's confirmation, 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 supervises the number of days off. Therefore, leader's certain confirmations or a Business Process, which allows administration of the whole company, has come to be necessary.

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 leader submits it to the administrator of the applicant's division.
 * 5) The administrator confirms it.
 * 6) The administrator submits it to the personnel department.
 * 7) The personnel department registers the leave request to an in-house system.
 * 8) The person in charge of application confirms the request result.

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 application 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 Because the application route is very simple, usability is high.
 * Simplicity of application route

Disadvantages When a request is rejected, the applicant does it over. However, 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. Because an application once made is supposed to be always operated, the application cannot be canceled.
 * Management in the cases of rejected applications

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:Input of \nleave request information"]; PS2 [label="PS2:Result confirmation\nPermission confirmation"]; PS1->PS [dir=back,arrowtail=normal]; PS->PS2 [style=invis,weight=10]; PS2->PE [weight=10]; } subgraph clusterm { labeljust=l; label="section-parent-leader@company.com(Administrator)"; MS1 [label="MS1:Permitting operation\nLeave request \nconfirmation"]; } subgraph clusterl { labeljust=l; label="section-leader@company.com(Leader)"; LS1 [label="LS1:Permitting operation\nLeave request \nconfirmation"]; }

PS1 -> LS1 [weight=100,tailport=e]; LS1 -> MS1 [arrowtail=rcrowlvee, weight=10]; LS1 -> PS1 [arrowtail=odiamond,label="Rejected",tailport=n]; MS1 -> PS1 [arrowtail=odiamond,label="Rejected"]; MS1 -> PS2 [arrowtail=odiamond,label="Permitted", weight=10]; }

subgraph clusterPN { labeljust=l; label="personnel@company.com(Personnel)"; PN1 [label="PN1:Request\nrecord"]; PNE [label="", shape=circle, width="0.3", style=bold]; PN1 -> PNE; } MS1 -> PN1 [arrowtail=odiamond,label="Permitted"]; {rank=same;PS1,LS1,PN1} }