UCSD
CAMPUS NOTICE
University of California, San Diego
OFFICE OF THE SENIOR VICE CHANCELLOR -
ACADEMIC AFFAIRS
OFFICE OF THE VICE CHANCELLOR -
EXTERNAL AND BUSINESS AFFAIRS
August 5, 2009
ALL ACADEMICS AND STAFF AT UCSD (excluding UCSD Medical Center)
SUBJECT: Holiday Schedule - December 19, 2009 to January 3, 2010
During the 2009 holiday season, UC San Diego (excluding the hospitals and clinics) will officially close for 16 days between Saturday, December 19, 2009 and Sunday, January 3, 2010. This closure will result in significant energy savings from reduced operations.
The closure period includes four University paid holidays (December 24, 25 and 31, and January 1). Six days (December 21, 22, 23, 28, 29 and 30) are not paid holidays and non-represented Academics and Staff who are covered by the furlough plan will be required to use furlough days
to cover the time off. Furlough days may be used in advance of accrual.
Non-represented Academics and Staff who do not participate in the furlough plan may use accrued vacation, compensatory time off or leave without pay for the six closure days that are not paid holidays.
For exclusively represented employees, these closure days will be handled in accordance with the existing contract provisions and are subject to discussion and/or collective bargaining where applicable.
UC San Diego departments and units that need to remain open during the closure period must obtain approval from their respective vice chancellors.
The latest questions and answers regarding the Furlough/Salary Reduction Plan are available on the Office of the President budget website and on the At Your Service home page
Staff with questions regarding this closure period should contact the Employee Relations division of Human Resources at employeerelations@ucsd.edu or (858) 534-4115. Academic employees should contact Amy Rosen, Academic Personnel Services, at arosen@ucsd.edu or
(858) 822-2041. Exclusively represented employees may also contact their union representatives.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment