Information Technology Lifecycle Policy

Purpose: To ensure the security of campus data and network services, as well as provide for satisfactory and efficient client IT experiences. To ensure perspectives from various areas of campus, the policy was developed by the IT Lifecycle Committee, which is made up of 10 diverse campus stakeholders.

Applies to: All members of the PSU community, including but not limited to, faculty, staff, students, and contractors whom university technology resources and network access are made available by PSU.

Policy:

IT Lifecycles

End of Life (EOL): Refers to a point in a product’s lifecycle when the vendor no longer provides support, updates, or security patches for it. This signifies the end of the product’s officially supported lifespan and can have significant implications for security and functionality. EOL products increase the IT security risk to the university.

• All systems connected to the university network must be on an operating system that has not reached EOL per the manufacturer’s definition.

• All software, including browsers, connected to the university network must be on a version that has not reached EOL per the manufacturer’s definition.

• It is understood that in rare instances there are unique IT Resources (both hardware and software) that require older operating systems and browsers. In addition, the equipment/software being used may offer a newer (more secure) version, but that campus departments cannot afford it at EOL of the operating system and/or browser. It is the IT resource owner’s responsibility to create a plan to upgrade and secure funding for these resources.

Exceptions to the above are considered in isolated circumstances. To request an exception please complete the IT Lifecycle Exception Form and send it to ITLifecycleException@pittstate.edu for consideration.

Recommended Best Practices:

• Hardware/Software Replacement Plan: It is recommended that all university departments have a written plan for updating IT resources (hardware, software, peripherals, etc.) and aligning those updates to budgeted funds. (Note: Industry standards indicate that updating computer hardware every 3-4 years is current industry best practice.)

• Waterfalling Hardware: After hardware is replaced with new hardware, the old hardware should be considered for other uses as well as for e-waste disposal. Things to consider are the age, performance, and efficiency of the hardware.

• Peripheral Devices: It is often difficult, and not fiscally responsible, to replace peripheral devices (printers, projectors, monitors, keyboards, mice, etc.) as often as computer hardware and software at EOL of the product. It is recommended to consider the replacement and maintenance of these items carefully. It may be more efficient to allow older peripherals to remain in place until they no longer function with a backup plan in place when/if the device no longer functions.

• Bulk IT Purchases: It is recommended that departments plan for purchasing carefully and pool large IT purchases at the same time to ensure price breaks. The coordination of bulk IT purchasing takes place through the Information Technology Services (ITS) in July, December, and May of each fiscal year. Additional bulk purchasing times can be arranged by contacting the Associate Vice President of Technology.