IT service use application process/Use charge accounting registration, Sectional prior confirmation

This is a process that the applicant applies for the in-house service use, processes it in service window and the application is approved in the section. Accounting registers the service use charge. After it is approved by sectional, the applicant applies for registration at the service use window. This business process strengthens the confirmation in the section, in order to reduce the rejection from Information systems division.

Summary

 * 1) The applicant applies for the service use.
 * 2) After Confirmation, the director requests processing from the sectional budget manager.
 * 3) The budget manager updates budget execution information and requests the registration from the person in charge of service.
 * 4) The service use application is accepted at the information system department service window based on application.
 * 5) The person in charge of service registers the service use, and notifies the user and Accounting Department.
 * 6) Accounting Department updates information on in-house dealings.
 * 7) After accounting department updates dealings information, it reports completion to applicant/service window.

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 work of 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
 * The applicant examines the estimate and applies it. But, the possibility of mistaking the estimate decreases because confirmation is made by in the section unlike IT service use application process/Use charge accounting registration, Sectional prior processing.

Process diagram and process data
digraph obtain_estimate { compound=true; graph [size="10,18",rankdir=LR]; //graph [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"]; P3 [label="P3:Forced termination confirmation",style="dotted,rounded"]; PS -> P1 [style=bold,weight=20]; P1 -> P2 [style=invis]; {rank=same;P2,P3} } subgraph clusterl{ labeljust=l; label="Director\nany-section-leader\n@company.com"; L1 [label="L1:Application confirmation"]; LE [label="", shape=circle, width="0.3",style=bold]; L1 -> LE [arrowtail=odiamond, headlabel="Forced termination"] {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 -> P1 [arrowtail=odiamond, label="Rejection",weight=10,headport=ne,tailport=se]; L1 -> A1 [arrowtail=rcrowlvee, style=bold]; A1 -> L1 [arrowtail=odiamond, label="Reexamination\nor budget overrun",headport=ne,tailport=nw] L1 -> P3 [label="Forced termination",style=dotted]; } 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 [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"]; SI3 [label="SI3:Accounting registration confirmation"]; SIE [label="", shape=circle, width="0.3",style=bold] SI1 -> SI2 [arrowtail=rcrowlvee,style=bold,weight=20]; SI2 -> SI3[style=invis,weight=20]; SI3 -> SIE; {rank=same;SI3,SIE}; } SI1 -> P1 [arrowtail=odiamond, label="Re-application"]; SI1 -> GP1 [style=invis]; A1 -> SI1 [arrowtail=rcrowlvee,style=bold]; SI2 -> P2 [style=dotted]; SI2 -> GP1 [style=bold]; GP1 -> SI2 [style=invis]; GL1 -> SI3 [arrowtail=rcrowlvee, label="Approval",style=bold]; }