Proposing my first project

[aaron.]

So I am preparing to propose a project to redesign a branch of our network at work. This isn't something I have been tasked with it comes from a personal observation of how to improve infrastructure (including alternative options) for this branch of the network. It will be my first proposal I will be sending to my manager for review so I want to make a good impression even if it does get rejected.

 

To give you an idea we have network B which is physically separated A from and with the infrastructure in place the cables run under the floor from the servers and connect straight to the devices. We have a patch panel available (in a different room with our access switch) which we use to patch the floor boxes.

 

My 1st proposal is to remove network B and run its servers virtually on A with some plans from the 2nd proposal if needed. 

 

2nd proposal is to patch B into A's Access switch with a trunk link and then we can use the patch panel, also using a different VLAN to keep it virtually separate.

 

3rd proposal if company regulations say the A and B networks need to kept physically separate then a new switch could be purchased and placed in the patch panel room.

 

So if anyone has any advice, templates and information that should be covered that would be great!

[Bombastinator]

29 minutes ago, aaron. said:

So I am preparing to propose a project to redesign a branch of our network at work. This isn't something I have been tasked with it comes from a personal observation of how to improve infrastructure (including alternative options) for this branch of the network. It will be my first proposal I will be sending to my manager for review so I want to make a good impression even if it does get rejected.

 

So if anyone has any advice, templates and information that should be covered that would be great!

You...  um...  may have forgotten to describe the actual problem you want to solve.  You said that you need to solve an issue, and why you want to solve the issue but not what the issue is.

[aaron.]

14 minutes ago, Bombastinator said:

You...  um...  may have forgotten to describe the actual problem you want to solve.  You said that you need to solve an issue, and why you want to solve the issue but not what the issue is.

Its more about presenting the information and key areas to cover,

 

To give you an idea we have network B which is physically separated A from and with the infrastructure in place the cables run under the floor from the servers and connect straight to the devices. We have a patch panel available (in a different room with our access switch) which we use to patch the floor boxes.

 

My 1st proposal is to remove network B and run its servers virtually on A with some plans from the 2nd proposal if needed. 

 

2nd proposal is to patch B into A's Access switch with a trunk link and then we can use the patch panel, also using a different VLAN to keep it virtually separate.

 

3rd proposal if company regulations say the A and B networks need to kept physically separate then a new switch could be purchased and placed in the patch panel room.

[the gamer that is bad]

It depends the size of the company/branch but I would bring it up in casual conversation and work your way into being more professional but you sound professional already 

[Overtaxed]

1 hour ago, anodos said:

I don't understand what the purpose of this is. These are major changes, with potential for catastrophe. You don't just delete or merge networks without good reason, so what is the goal you are trying to achieve? If you want to make a good impression, as you say, then you need to point to a problem with the existing setup and how your proposal fixes it.

Exactly this.  What will these proposed changes result in?  Faster speeds between the networks, less WAN traffic because they can talk directly, something else?  What's the compelling event to get your boss to OK these changes?