Software Use on Non-State Computers: Difference between revisions

From Appalachian State University Policy Manual
imported>Mcnaneym
imported>Deaskc
Line 9: Line 9:
== Policy and Procedure Statements  ==
== Policy and Procedure Statements  ==
=== Conditions of Use ===
=== Conditions of Use ===
Under certain circumstances, it will be considered appropriate for an employee of the University to own software purchased by the University on a privately-owned computer. To be eligible, the employee must obtain approval from the employee's department head stating that the software is necessary for that employee to perform the employee's job function. The software must be purchased by the department and will remain the property of the University. If the employee either leaves the University or the employee's job function changes and the employee no longer needs the software to perform job duties, then the software and documentation must be returned to the department. The employee will certify that the software has been removed from his or her computer prior to leaving the University or upon change in job function.
4.1.1 Under certain circumstances, it will be considered appropriate for an employee of the University to own software purchased by the University on a privately-owned computer. To be eligible, the employee must obtain approval from the employee's department head stating that the software is necessary for that employee to perform the employee's job function. The software must be purchased by the department and will remain the property of the University. If the employee either leaves the University or the employee's job function changes and the employee no longer needs the software to perform job duties, then the software and documentation must be returned to the department. The employee will certify that the software has been removed from his or her computer prior to leaving the University or upon change in job function.


=== Procedure to Apply/Participate ===
=== Procedure to Apply/Participate ===

Revision as of 20:49, 6 January 2012

Policy 602.4

Introduction

Scope

Definitions

Policy and Procedure Statements

Conditions of Use

4.1.1 Under certain circumstances, it will be considered appropriate for an employee of the University to own software purchased by the University on a privately-owned computer. To be eligible, the employee must obtain approval from the employee's department head stating that the software is necessary for that employee to perform the employee's job function. The software must be purchased by the department and will remain the property of the University. If the employee either leaves the University or the employee's job function changes and the employee no longer needs the software to perform job duties, then the software and documentation must be returned to the department. The employee will certify that the software has been removed from his or her computer prior to leaving the University or upon change in job function.

Procedure to Apply/Participate

The employee must complete the Department Request Form - Use of Software on Non-State Owned Personal Computers and have it approved by the department head. The form must be kept in the employee's personnel folder in the department records. The department will then follow normal procedures for purchase of the software.

Final Authority For Site Licenses

If the purchase involves taking advantage of University site licenses, the manager that is contractually responsible for the particular license agreement will have the final authority to judge the proper use of the software. In those cases where this policy does not clearly cover a particular arrangement between a University department and the employee, the responsible manager will have the discretion to determine whether the software use is appropriate.

Form Use of Software on Non-State Owned Computers

A Departmental Request Form - Use of Software on Non-State Owned Personal Computers can be obtained by contacting the Office of General Counsel.

Additional References

Authority

Contact Information

Effective Date

Revision Dates