IT solution development process/RFP making,Proposal acceptance,Small scale,Approval in the section

Process to do comparatively small scale IT establishment plan.It plans from the problems of the section and the strategy, and a person in charge makes the outcomes for the plan stage.The results on the way of product is approved by a sectional director, and the IT establishment plan should not deviate from the direction of the section. The IT establishment is chiefly requested to the vender.Therefore, this process is a case to request the proposal of the IT establishment plan from the vender.

Summary

 * 1) It confers on the problem solution concerning the business in each section.A main person in charge of the problem solution is appointed by the director, and outline content/plan is settled on.
 * 2) The person in charge drafts the IT establishment plan.
 * 3) The person in charge makes Request For Proposal (RFP) to the vender according to outline content/plan.
 * 4) The person in charge submits RFP to the director, and requests approval.
 * 5) The person in charge passes RFP to the vender, and the proposal describes the preliminary cost/delivery date is accepted on meeting.
 * 6) The person in charge confirms the proposal from the vender, submits it to the director, and requests approval.

Participant

 * Arbitrary section(any-section@company.com)
 * Director(any-section-leader@company.com)
 * Person in charge(any-section-person@company.com)
 * Vender(person@vendor.com)

Process owner
Director of arbitrary section(any-section-leader@company.com)

It is a business process to establish a small scale information technology environment.However, because details of the budget etc are decided after planning, it is preferable that the director who has the role on deciding the approval timing becomes an owner in the process.

Feature
Because it is establishment of a small scale information technology environment, just one vender is supposed to make the proposal in this business process.However, it is preferable to receive the proposals from two or more companies and to select one.
 * The proposal is made for the vender of one company

Process diagram and process data
digraph obtain_estimate { compound=true; graph [size="9,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="Person in charge(any-section-person@company.com)\n\n"; SPS [label="", shape=circle, width="0.3"]; SPE [label="", shape=circle, width="0.3", style=bold]; SP1 [label="SP1:Conference\nWork draft"]; SP2 [label="SP2:RFP making"]; SP3 [label="SP3:Minutes making\nMeeting with vender"]; SP4 [label="SP4:Acceptance\nProposal"]; SP5 [label="SP5:Confirmation\nProposal approval"]; SPS -> SP1 [weight=10]; SP1 -> SP2 ; SP4 -> SP5 [style=invis,weight=10]; SP5 -> SP3 [arrowtail=odiamond,taillabel="Rejection"]; SP5 -> SPE [arrowtail=rcrowlvee,label="Approval"]; SP2 -> SP3 [style=invis]; SP4 -> SP5 [style=invis]; SP3 -> SP4 [weight=10]; {rank=same;SP1,SP2}; } subgraph clusterl{ labeljust=l; label="Director(any-section-leader@company.com)"; L0 [label="L0:Draft notification\n(e-mail)",style=dotted]; L1 [label="L1:RFP Confirmation"]; L2 [label="L2:Confirmation\nProposal"]; L0 -> L1 -> L2 [style=invis]; } L0 -> SPS [style=invis]; SP1 -> L0 [style=dotted]; SP2 -> L1 [tailport=n,headport=w,weight=10]; L1 -> SP2 [arrowtail=odiamond,label="Rejection",headport=e]; L1 -> SP3 [arrowtail=rcrowlvee,label="Approval"]; SP4 -> L2 ; L2 -> SP5 ; } subgraph clusterv{ labeljust=l; label="Vender(person@vendor.com)"; V1 [label="V1:Proposal making",style=dotted]; } SP3 -> V1 [style=dotted]; V1 -> SP4 [style=dotted,headport=s,tailport=n]; SP5 -> V1 [arrowtail=odiamond,label="Rejection",style=dotted,tailport=s,headport=ne]; SP2 -> V1 [style=invis]; }


 * (note)SP5 is a task of confirming the approval result of L2. The director's approval/rejection is confirmed, and it advances to the divergence.


 * (note)For the registered file type, the file, which can be managed easily even if it is executed two or more times and overwritten, is preferable. Example: Microsoft Excel etc.