NET-S007 Inventory and Hardware Management

1.0    SCOPE:  
1.1    This Standard outlines Network Service’s practices regarding inventory and hardware management.

2.0    RESPONSIBILITY:  
2.1    Director of Network Services

3.0    APPROVAL AUTHORITY:
3.1    Chief Information Officer

4.0    DEFINITIONS:
4.1    TeamDynamix: is the IT Service Management System used by OIT to manage customer requests and other forms of OIT data.

5.0    Standard:
5.1    Network Services will maintain an accurate inventory of all major network appliances that support the university core network systems. Those systems are the Perimeter Network, Firewall, Core Network, Network Access Control, Wireless Infrastructure, and Building Local Area Networks. This standard addresses NCSR ID.AM-1.
          5.1.1    Network Services currently maintains core systems inventory via Microsoft Excel. In the near future, that inventory will be transferred to TeamDynamx or an in-house MySql database with web interface.
          5.1.2    The replacement cycle for each core system is completed as a whole with the exception of Building Local Area Networks. For the purpose of replacement cycle, each building LAN is considered a complete sub-system and my have a different refresh timeline than other building LANs.
          5.1.3    Routine updates for a system’s hardware inventory will be conducted during the hardware replacement cycle. The replacement cycle is anywhere between 3 and 8 years depending on the device.
          5.1.4    In the event that a unit has to be replaced or upgraded prior to its normal refresh cycle, inventory will be updated immediately as part of the hardware replacement.
5.2    Once a network appliance has been replaced or becomes obsolete for university use, the Network services team will prepare and transport the hardware to surplus. This standard addresses NCSR PR.DS-3.
          5.2.1    In preparation for disposition, all configuration that reveals university specific network design elements will be removed from the device. This will often be done by setting the devices configuration back to the manufacturer’s default setup.
          5.2.2    Once a devise has been prepared, it will be transported to the university warehouse to be sold in a public auction.

6.0    ASSOCIATED DOCUMENTS:
6.1    NCSR POAM

7.0    RECORD RETENTION TABLE:

8.0    REVISION HISTORY:
Date:    Rev.    Description of Revision:
2/1/2024        Initial Release
      

 
***End of Standard***