Question : Please help me refine this concept (eventually into a process diagram)

Based on a rough white board drawing - I need to create a process diagram.  

The process is basically about how a change is needed for a network, and how that change request is processed and eventually implemented.  

First, however, I must come up with some concepts on what I think this means.  I am told that I am allowed to make assumptions.  I have not done this before so it is pretty abstract and vague on what exactly I am supposed to do.  I am just supposed to think about stuff, and then review it with the person that assigned this to me.  It should start off on paper, not on Visio.  

Here is what I understand from the drawing:

1. An individual identifies a need for a change (this may be someone from business or IT - and it does not necessarily have to be something that is perceived to be directly related to the network, it could just be a business user that needs access to a certain application or file server).  

2. The change is then somehow reported to the business unit IT representative, who identifies if the change request requires a network change.  

3. The representative fills out a change request form (if it requires a network change?).

4. The change request form gets approved or rejected by the business unit's IT leadership.  If approved, they establish a timeline from planning to implementation.

5.  At least two weeks before it is scheduled to be implemented, it must be sent to the IT Global Change Approval Board.  Even if it is not a global network change, it must still go to this board.  The board reviews it and then either approves it, rejects it, or sends it back to the business unit IT leadership for further changes and updates.  

6.  If approved, it is officially scheduled for implementation (also it will be tested by users that are identified by the application owners).  Communication to the business should be sent out on how and when it affects them.

7.  If rejected - ?? - I guess it is either thrown out or sent back for further modification.


I'm not really sure what I am asking because I am not sure what to do in the first place.  I know I am supposed to make assumptions.  Maybe if you guys could just ask me further questions about the process so I can refine it, and make assumptions.  Here is one:  Keep in mind that this whole process is all related to network change, but the person that initially requests the change may or may not know that.  They also probably do not know who to contact in order to get this change requested (the business IT rep), or how to contact them.

Or if you guys see any flaws or communication barriers to it, then let me know because that would help as well.  

Here is some further information on the global change approval board that I found, if that helps.  

The global change approval board consists of 3 regions of the world - the 3 networks all sit on their own MPLS cloud, and they are connected through peering points.  Also there is global data-centers that connect all them, so if they require access to a certain application in another region/network, they do not have to go through them to obtain access to it.  Does that make sense?

Thanks!

Answer : Please help me refine this concept (eventually into a process diagram)

This is a very generic outline of how I see it.  Go through and see if it is what you are looking for.  You will, of course, need to add in the specifics.  Hope this helps.

1. Individual identifies a need for a network change or access.
2. The user sends an email to [email protected] which notifies the IT representative.
3. The representative fills out a request form detailing the user's need and sends it to the business unit's IT leadership.
4. The request is reviewed by the business unit's IT leadership within XX days of the request being received.  
4a. If the request is rejected it is sent back to the IT representative to inform the user or to gather further clarification.  If more clarification is needed the IT representative has XX days to fill out an andendum to the request and resubmit to the business unit's IT leadership.
4b. If the request is approved they establish a tentative timeline from planning to implementation.
5. After the plan is formed, and at least two weeks before it is scheduled to be implemented, it must be sent to the IT Global Change Approval Board.  All requests must go to this board.  The board reviews the request within XX days of receiving it.
5a. If the plan is rejected it is sent back to the business unit's IT leadership with a reason for rejection or a request for further changes and updates.  If changes are needed the business unit's IT leadership has XX days to resubmit the plan for another evaluation.
5b. If the plan is approved it will go through a testing phase by the users that are identified by the application owners.  This testing phase will last between XX-XX days.
6. Once testing is complete and the request deemed not to be a detriment to the network stability or security implementation will be scheduled.
7. Communication will be sent out to the relevant business units on how and when the request will affect them.  The communication will also state that they have XX days to notify IT with any questions or issues related to the request.  After that time they will need to go through normal support channels.