Employment process/Application notification, Prospective employee upper bound condition, Forced termination

This is a business process for job offers; from recruitment of part-timers and the employees through interviews upto informal job offers.

After informal decision, a prospective employee receives a formal job offer approved by in-house circular. (Not covered in this business process.)

Summary

 * 1) The deirector of demand section registers demands for part-timers and the employee expected to be hired.
 * 2) The person in charge of recruitment confirms demands.
 * 3) The person in charge registers the application steps, and notifies the deirector of demand section the application beginning.
 * 4) The person in charge accepts the applicant, and conducts interviews.
 * 5) The person in charge registers the informally appointed worker.

(note)You repeat this process from the applicant's acceptance to the registration of the informally appointed worker of the interview until number of informally appointed workers becomes reachs the limit.

Participant

 * Demand section(any-section@company.com)
 * Director(any-section-leader@company.com)
 * Personnel(personnel@company.com)
 * Person in charge of recruitment(personnel-person@company.com)
 * Applicant(someone@general.com)

Process owner
Person in charge of personnel(personnel-person@company.com)

The person in charge of recruitment is often responsible for the process of the recruitment steps and the recruitment interview.

Advantage

 * The grasp of the application activity is easy.
 * It is easy to understand the present number of applications and the informally appointed worker because recruitment beginning is notified thoroughly.
 * Interruption when the recruitment policy is changed
 * If the director of demand section wants to change the policy at his/her own discretion', the business process can be interrupted on the way. As a result, a new requirement etc is reexamined and made a fresh start, it becomes possible to execute again.

Disadvantage

 * Delay of informal job worker decision
 * The person in charge can't start the task of the final decision until informal job workers reach the fixed number. Therefore, there is a possibility for delay of the procedure after job offers.

Process diagram and process data
digraph developing_capability { compound=true; graph [size="10,8",rankdir=LR]; node [shape=box, style=rounded]; edge [color="#444444", labelfloat=true]; //label text float OFF(=true) subgraph clusterl{ labeljust=l; label="any-section-leader@company.com(Director of demand section)"; LX [label="", shape=circle, width="0.3"]; LY [label="", shape=circle, width="0.3", style=bold]; L1 [label="L1:Recruitment demand registration"]; LM1 [label="LM1:Recruitment application beginning notification \n (E-mail)",style="dotted,rounded"]; L2 [label="L2:Interview result confirmation"]; LX -> L1 [weight=10]; L1 -> LM1 -> L2 [style=invis]; L2 -> LY [arrowtail=odiamond, label="Interruption"]; } subgraph clusterp { labeljust=l; label="personnel-person@company.com(Person in charge of personnel)\n\n\n\n"; P1 [label="P1:Recruitment demand confirmation"]; P2 [label="P2:Recruitment application steps registration"]; P3 [label="P3:Interview result registration"]; PM1 [label="PM1:Recruitment activity\nBreak notification \n (E-mail)",style="dotted,rounded"]; PY [label="", shape=circle, width="0.3",style=bold]; P1 -> P2 [arrowtail=rcrowlvee,weight=10]; P2 -> P3 [weight=10]; P3 -> PY [arrowtail=odiamond, label="Number of those who informal decision upper bound\nUpper bound achievement",weight=40]; {rank=same;PY,PM1}; } subgraph clusters { labeljust=l; style=dotted; label="someone@general.com(Applicant)"; S1 [label="S1:Interview application \n (E-mail/Web form etc)",style="dotted,rounded"]; } LX -> P1 [style=invis]; L1 -> P1 [weight=10,tailport=sw,headport=nw]; P1 -> L1 [arrowtail=odiamond, label="Requirement correction necessity",weight=10]; P2 -> LM1 [style=dotted]; S1 -> P3 [style=dotted]; P3 -> L2 [arrowtail=rcrowlvee, label="Number of those who informal decision upper bound\nUpper bound underachievement"]; L2 -> P3 [arrowtail=rcrowlvee,headport=nw,tailport=sw]; L2 -> PM1 [style=dotted,weight=80]; }


 * (note)The split achieve/underachive in P3:Intervew result registration depends on Number of demands and Number of informal decisions.


 * (note) The reason why P3-L2 of “Number of recruitment demands” is RW(Read and Write) is because this sample Process corresponds to the case in which the director changes number of recruitment.
 * (note) The reason why P3-L2 of “Number of informally appointed workers” and “Informally appointed worker's information” is RW is because this sample Process corresponds to the case in which the director changes number of recruitment.