IT service use application process/Use charge accounting registration, Budget confirmation rejection, Accounting prior confirmation

This is a process in which the applicant applies for usage of an in-house service use, and the service desk processes it, and then the accounting registers usage fee. After it is approved by sectional and Accounting confirms it, the applicant applies for registration at the service use window. This business process strengthens the confirmation of the budget etc in the section, in order to reduce the rejection from Information systems division, and the application is canceled if necessary.

Summary

 * 1) The applicant applies for the service use.
 * 2) The applicant requests the confirmation of service use based on application from the director of the applicant belonging division in the service window of information system department.
 * 3) The director requests processing from the sectional budget manager.
 * 4) The budget manager updates budget execution information.
 * 5) The budget manager notifies Accounting Department, and the budget execution procedure (information on in-house dealings) is done.
 * 6) After completing the procedure of Accounting Department, the person in charge of service registers the service use, and notifies the user and Accounting Department.

Participant

 * Arbitrary section(any-section@company.com)
 * Director(any-section-leader@company.com)
 * Budget manager(any-section-accounter@company.com)
 * Applicant(any-section-person@company.com)
 * Information systems division(informationSystem@company.com)
 * Information system service(informationSystem-service@company.com)
 * General accounting department(generalAccounting@company.com)
 * Director(generalAccounting-leader@company.com)
 * Member(generalAccounting-person@company.com)

Process owner
Person in charge of service information system department(informationSystem-service@company.com)

It is preferable to manage the content of the business process, because the promotion of the service use is often undertaken, and because the business flow until beginning use is efficiently done.

Feature

 * The service use application is basically accepted.
 * Each person in charge accepts the application, and processes it as long as there is no incompleteness in the content of application and processing, because the service uses have already been included in the budget. So, preparation for processing of re-submitting is kept to a minimum.
 * Efficient processing
 * Compared to IT service use application process/Use charge accounting registration, this process requires confirmation to be made in advance within the section before operations in the Information Systems Division, which is another section, and this results in little operation passing between sections, as well as enhancement of efficiency.
 * Possibility of incorrect estimate
 * Compared to IT service use application process/Use charge accounting registration, Sectional prior confirmation, this process requires confirmation to be made in advance within the section before operations in the Information Systems Division, which is another section, and this results in little operation passing between sections, as well as enhancement of efficiency.
 * Application cancellation due to budget shortfall
 * The director has authority and he/she can cancel application unlike IT service use application process/Use charge accounting registration, Sectional prior confirmation so that the applicant can re-apply after the budget procurement due to budget shortfall.
 * Service use formal registration after it follows a procedure for Accounting Department
 * Accounting Department is previously registered compared with IT service use application process/Use charge accounting registration, Sectional prior confirmation, Budget confirmation rejection. So when the budget is insufficient, processing can be prevented from advancing to formal registration in just case.

Process diagram and process data
digraph obtain_estimate { compound=true; graph [size="10,18",rankdir=LR]; node [shape=box, style=rounded]; edge [color="#444444", labelfloat=true]; //label text float OFF(=true) subgraph clusters{ labeljust=l; label="Arbitrary section(any-section@company.com)"; subgraph clustersp{ labeljust=l; label="Applicant\nany-section-person@company.com"; PS [label="", shape=circle, width="0.3"]; P1 [label="P1:Use application"]; P2 [label="P2:Application registration confirmation",style="dotted,rounded"]; PS -> P1 [style=bold,weight=20]; P1 -> P2 [style=invis]; } subgraph clusterl{ labeljust=l; label="Director\nany-section-leader\n@company.com"; LE [label="", shape=circle, width="0.3",style=bold] L1 [label="L1:Application confirmation"]; L1 -> LE [arrowtail=odiamond, label="Rejection"]; {rank=same;L1,LE}; } subgraph clusterc{ labeljust=l; label="Budget manager\nany-section-accounter\n@company.com"; A1 [label="A1:Budget execution information update"]; } PS -> L1 [style=invis,weight=10]; P1 -> L1 [style=bold,weight=10]; L1 -> A1 [arrowtail=rcrowlvee, style=bold,weight=20]; A1 -> L1 [arrowtail=odiamond, label="Reexamination",headport=ne,tailport=nw] } subgraph clusterg{ labeljust=l; label="General accounting department(generalAccounting@company.com)"; subgraph clustergp{ labeljust=l; label="Member\ngeneralAccounting-person\n@company.com"; GP1 [label="GP1:Use charge registration"]; } subgraph clustergl{ labeljust=l; label="Director\ngeneralAccounting-leader\n@company.com"; GL1 [label="GL1:Use charge registration confirmation"]; } GP1 -> GL1 [arrowtail=rcrowlvee,style=bold,weight=10]; GL1 -> GP1 [arrowtail=odiamond, label="Rejection",headport=ne,tailport=nw]; } subgraph clusterSI{ labeljust=l; label="Person in charge of service information system department\n(informationSystem-service@company.com)"; SI1 [label="SI1:Application acceptance"]; SI2 [label="SI2:Service registration"]; SI1 -> SI2 [arrowtail=rcrowlvee,style=bold,weight=20]; SIE [label="", shape=circle, width="0.3",style=bold] SI2 -> SIE [style=bold]; } SI1 -> P1 [arrowtail=odiamond, label="Re-application"]; P2 -> GP1 [style=invis]; SI2 -> P2 [style=dotted]; A1 -> GP1 [style=bold]; GP1 -> A1 [arrowtail=odiamond, label="Budget shortfall",headport=sw,tailport=nw]; //GP1 -> SI2 [style=invis]; GL1 -> SI1 [arrowtail=rcrowlvee, label="Approval",style=bold] }