Those specs should be absolutely fine for a small test bed setup such that you can do the things in the list above to learn where things are and some of their quirks. Not going to be enough for a real world deployment but this is not that.
Anyway big boy sysadmin it is. I try never to work for local government (or in the UK the NHS which is kind of the same thing) but sounds like they might just have their ducks in a row there. The spec is written by someone that knows of what they speak and does not appear to have been too bastardised by HR before it got to you.
"SCCM"
Have fun with that one. It is the thing used to allow some of the non windows machines/phones/whatever to all conform to what is need to speak to the relevant emails, file shares... With everybody on a new install of plain windows it is awesome, for a more real world setup then yeah.
If you want some open source tools that do something like what that list of acronyms/initalisms does then
https://oss.oetiker.ch/mrtg/
https://www.zabbix.com/features
http://davmail.sourceforge.net/
https://puppet.com/products/how-puppet-works
https://docs.chef.io/chef_overview.html
http://www.webmin.com/
https://ninite.com/pro
Cheating maybe but saying I am not so familiar with that but I have used [this open source equivalent] might get you out of a pinch.
" • Must be able to troubleshoot system issues up through the layers of the OSI model."
What an odd what of phrasing it. That said it means it wants you to be able to run and terminate wire right through to be able to do things like figure out when an email provider updates their allowed access methods. I don't know if I have met anybody that thinks about things in a strict OSI model (it is a wonderful learning and framing tool, bit abstract for real world troubleshooting). The trouble is now I would probably have to raise the grim spectre of Cisco or Juniper for if you are dealing with big boy networks it is almost certain to be one of those two involved and they are not gentle like home routers.