Network diagram help :)

[Larry R Horton]

Hello, as homework I've been tasked to create a network diagram for a company that is moving to a new HQ. They have around 100 employees spread across 5 departments Marketing, Sales, Customer Service, Human Resource and Information Technology. The company hosts a single file server locally to serve employees internally. Printing services are also done locally through each respective department printer. The networking servers they have
locally are used for DNS and DHCP purposes. All other services are accessed through the Internet hence there is a heavy reliance on the Internet.
I have created a diagram. I would love some tips on what I did and if I made any errors thanks.

[deanwebb]

Hello and welcome to the forums! OK, here's my feedback on the diagram:

1. No addressing information - without addresses, we just have a concept, not a working diagram.
2. Are the phones, PCs, scanners and Printers all connected to the UPS for each department? If so, there could be massively more UPS purchases in your future. Typically, the UPS is reserved for infrastructure and critical servers.
3. What is the Wifi for? It looks as though all the connectivity is wired.
4. Are the switches layer 2 only, or are they performing routing functions, as well? This goes back to the first comment - if each department has its own IP range, it's likely that you don't have a flat network, but a segmented one (good for security, segmented networks!) and would need routing between each network. There are many switches that offer layer 3 functions, so you can keep the switches there, just designate that they have L3 functionality.
5. Are the departments on different floors, different buildings, or different cities? Each of those have design considerations.
6. Is there a consideration for remote workers? If so, then there needs to be a VPN or SASE solution working with the firewall to permit remote access to company-wide and department-based assets.

Artistically, it's a clean drawing, which is very important to have. Well done on that area.

[Larry R Horton]

Hello, thank you for your feedback. Firstly about the UPS can I just add an UPS Enterprise instead of single UPS's for each department? Secondly, I forgot to mention employees  use either a wired or wireless connection to connect to the corporate network so I added a wireless router to each department. I'm not sure if the departments are on different floors.The problem basically stated that this company is rebuilding a new HQ and I have to create a networking solution. Here is the proposed IP address scheme:
Proposed IP Address Scheme:

Private IP Address Range: 10.0.0.0 - 10.255.255.255

Subnets- Departments:

10.0.0.0/24
10.0.1.0/24
10.0.2.0/24
10.0.3.0/24
10.0.4.0/24

Gateway: 10.0.0.1

DNS Servers: 10.0.0.2 and 10.0.0.3

DHCP Server: 10.0.0.4

File Server: 10.0.0.5

Printers: 10.0.0.10 - 10.0.0.25

Management Network: 10.0.1.0/24

Wireless Network: 10.0.2.0/24

Access Points: 10.0.2.10 - 10.0.2.25

External Access: 10.0.4.0/24

Honestly, I never thought about remote workers so I'll add that to the diagram.

[Dieselboy]

Hi OP and welcome

The key thing to think about is - what is your objective with a network diagram? Perhaps you need a detailed network diagram to show VLANs and employee positioning, subnets for routing or maybe you need a diagram to detail specific switch port connections to key network devices. This depends on what you need to achieve.
In the past when I have moved offices I have literally traced physical cables to devices and then made sure those same devices connect into the same ports and I done this on a notepad.

How I would make my way towards an objective as a new person to a network - I would start out high-level and get a good overview. Then I'd copy the visio and add more detail to drill down. I may even then copy a site to a new visio page and drill down even further. And I would keep doing this until I was satisfied that it contained enough information for me to proceed with my tasks that the diagram is there to support.

Your diagram appears to be a good high-level start. The important things are whether it's easy to read and view the content that the diagram intends to show. In my high-levels I usually use bubbles to show VLANs and dont bother with physical links. I'll just place a bunch of switches in a bubble and have VLAN bubbles hanging off that. But then I often provide these diagrams to CEOs and high-level managers where they wouldnt even know what Gi0/1/23 means

If you really want to go further than that then you it is possible to upload a series of diagrams to something like nagvis where you can have the initial high-level diagram with key components like site links showing bandwidth consumption etc, and then if you were to click on a site it could drill down into that site and show phsycial devices and switch ports etc etc.

[icecream-guy]

you really would need at least 3 diagrams,  one concept 10,000 ft view, like you already have, 2 would be a layer 2 diagram, showing VLAN's, Broadcast domains, spanning-tree, root bridge, etc. 3 would be a layer 3 diagram, where the routing takes place.