IT solution maintenance process/Record of failure,Superior's confirmation,The director's instruction premature termination

This business process detects any troubles in the in-house operation system, and it gives an initial, interim, and end reports on the trouble.It progresses with the　information system director’s approval. It is possible to end when receiving the false report notice.

Summary

 * 1) If the person in charge of the target system receives any troubles detection, he/she gives to the director an initial report, and obtains approval, and then, he/she reports to parties concerned.
 * 2) If the person in charge gives the interim report to the director, and if he/she obtains approval at the point in which the trouble　correspondence progresses, he/she reports to parties concerned.
 * 3) If the person in charge gives the end report to the director, and if he/she obtains approval at the point in which the trouble correspondence has been completed, he/she reports to parties concerned.
 * 4) The person in charge describes the settlement and the relapse prevention plan from the failure to completion for the trouble, does to the trouble report　director, and obtains approval, he/she reports to parties concerned.

Participant

 * Information system section(informationSystem@company.com)
 * Director(informationSystem-leader@company.com)
 * A person in charge(informationSystem-person@company.com)
 * Related sections(interested-parties@company.com)

Process owner
Director of Information system section(informationSystem-leader@company.com)

It is preferable that the person in charge of the section responsible for the in-house operation system manages the report process.

Feature

 * Sureness of trouble/measures report

The report can be expected to be done surely by failure/action report's being defined as a business process.


 * Validity of trouble report/contents of measures

The report and the close examination of the content of correspondence are surely done because the following　measures are taken after giving the report and receiving a confirmation of the director at each timing of the　trouble.


 * trouble report/Speed of correspondence

It is necessary to report again if the director's approval cannot be obtained, that is, director's correspondence and content of the report have an influence on the correspondence speed.


 * Action method when trouble false report

When the incompleteness of the trouble monitoring system and those who report the trouble misreport it, the trouble correspondence can be settled. Information about the settlement of the issue is announced by e-mail to the parties concerned including the director.

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) T0 [label="Failure notification",shape=ellipse,style=dotted]; subgraph clusterIS{ labeljust=l; label="Information system section(informationSystem@company.com)\n\n\n"; subgraph clusterp{ labeljust=l; label="The person in charge(informationSystem-person@company.com)"; P1 [label="P1:Initial report"]; P2 [label="P2:Interim report"]; P3 [label="P3:End report"]; P4 [label="P4:Trouble report"]; P1 -> P2 -> P3 -> P4 [style=invis]; } subgraph clusterl{ labeljust=l; label="Director(informationSystem-leader@company.com)\n\n\n\n"; L1 [label="L1:Initial report\nConfirmation"]; L2 [label="L2:Interim report\nConfirmation"]; L3 [label="L3:End report\nConfirmation"]; L4 [label="L4:Trouble report\nConfirmation"]; LY [label="", shape=circle, width="0.3",style=bold]; LC1 [label="", shape=circle, width="0.3",style=bold]; LC2 [label="", shape=circle, width="0.3",style=bold]; L1 -> L2 -> L3 -> L4 [style=invis,weight=10]; L4 -> LY [arrowtail=rcrowlvee, label="Approval", style=bold]; LC1 -> L1 [dir=back,arrowhead=odiamond, label="False report"]; LC2 -> L2 [dir=back,arrowhead=odiamond, label="False report"]; {rank=same;L1,LC1}; {rank=same;L2,LC2}; } P1 -> L1 [weight=10,style=bold,headport=w]; L1 -> P1 [arrowtail=odiamond, label="Rejection",headport=e]; L1 -> P2 [arrowtail=rcrowlvee, label="Approval", style=bold,weight=10]; P2 -> L1 [style=invis,weight=10,headport=w]; P2 -> L2 [style=bold]; L2 -> P2 [arrowtail=odiamond, label="Rejection",headport=e]; L2 -> P3 [arrowtail=rcrowlvee, label="Approval", style=bold]; P3 -> L3 [style=bold,headport=w]; L3 -> P3 [arrowtail=odiamond, label="Rejection",headport=e]; L3 -> P4 [arrowtail=rcrowlvee, label="Approval", style=bold]; P4 -> L4 [style=bold,headport=w]; L4 -> P4 [arrowtail=odiamond, label="Rejection",headport=e,tailport=n]; } subgraph clusteri { labeljust=l; style=dotted; label="Related section(interested-parties@company.com) "; I1 [label="I1:Initial report reception \n (Email)",style="dotted,rounded"]; I2 [label="I1:Interim report reception \n (Email)",style="dotted,rounded"]; I3 [label="I1:End report reception \n (Email)",style="dotted,rounded"]; I4 [label="I1:Trouble report confirmation \n (Email)",style="dotted,rounded"]; I1 -> I2 -> I3 -> I4 [style=invis]; } T0 -> P1 [style=dotted,label="Email"]; P1 -> T0 [style=invis,wight=10]; L1 -> I1 [style=dotted]; T0 -> I1 [style=invis,weight=10]; L2 -> I2 [style=dotted]; L3 -> I3 [style=dotted]; L4 -> I4 [style=dotted]; }
 * (note)Timing in which the interim report task is executed assumes execution by the date described in the correspondence schedule in an initial report.


 * (note)False report information is a selection only of the presence of the check. The check is not in an initial value.
 * (note)False report information changes the result of the check of the person in charge by the director once and can reject the report.