Fiscal Year 2009-2010 Furlough Impact on OAAIS Services
As of November 3, 2009
PRELIMINARY
Below is a chart listing OAAIS provided services, and reduced response time due to the mandatory furloughs. OAAIS has had to temporarily modify service level agreements to compensate for the enforced reduction in staff.
For questions, please contact Jane Y. Wong, Interim COO at Jane.Wong2@ucsf.edu or 415-476-1767.
For the following units:
- OAAIS Academic Research Systems (ARS)
- OAAIS Application Services (AS)
- OAAIS Customer Support Services (CSS)
- OAAIS Desktop LAN Support (DLS)
- OAAIS Enterprise Information Security (EIS)
- OAAIS Enterprise Network Services (ENS)
- OAAIS Information Technology Services (ITS)
|
Work Group |
Furlough Impact |
|---|---|
|
Academic Research Systems |
8-10% decline in response time |
|
AS Academic Admin Systems |
8-10% decline in response time |
|
AS Financials/P2P |
5-8% decline in response time |
|
AS Mainframe Systems |
8-10% decline in response time |
|
AS PeopleSoft Development |
5-10% decline in response time |
|
AS RAS |
15% decline in response time |
|
AS Weblinks |
5-15% decline in response time |
|
Customer Support Service Desk |
5-10% decline in response time |
|
DLS Workstation |
5% decline in response time |
|
EIS |
SEE BELOW for further information |
|
EIS DMCA Notice Handling |
8-10% decline in response time |
|
EIS E-Discovery |
8-10% decline in response time |
|
EIS Engineering |
Firewall changes 3-7 days, instead of 3-5 days External clients priority over OAAIS clients |
|
EIS Incident Response, Non-regulatory |
8-10% decline in response time |
|
EIS Incident Response, Regulatory |
8-10% decline in response time |
|
EIS Non-regulatory Investigation |
8-10% decline in response time |
|
EIS SSL Request |
8-10% decline in response time |
|
ENS |
SEE BELOW |
|
ITS Database Administration |
8-10% decline in response time |
|
ITS Data Center Operations |
Some shifts may not be covered Production schedules may be adjusted |
|
ITS Exchange |
8-10% decline in response time Also impacted by e-discovery requests |
|
ITS Middleware |
8-10% decline in response time |
|
ITS MyAccess |
Minimal change – two staff on visas |
|
ITS Unix Systems |
8-10% decline in response time |
|
ITS Windows Server Administration |
8-10% decline in response time |
OAAIS Enterprise Information Security (EIS)
The full impact furloughs may have on EIS DMCA Notice Handling, EIS e-Discovery and EIS Incident Response, Regulatory services cannot be predicted in part because of external factors, but includes the following possiblities:
- The ability to meet regulatory and legal time requirements;
- Timely data collection and analysis for incident response and e-discovery (delays could be at least 3-4 days).
For EIS Incident Response, Non-regulatory, data collection and analysis could be delayed by as much as 6-10 days based upon the needs of regulatory incidents.
OAAIS Enterprise Network Services (ENS)
Major Projects:
- Projects will take longer to complete. A rough magnitude of percentage is estimated to be 8-10%. Approximately 8% is due to EP staff reduction in time. An additional 2% is due to lack of overall ENS staff (In all ENS subunits) being available for overall project work coordination needs.
- Internal and external SLA's will need to be reviewed and possibly revised. For example, the ENS/CPFM MOU states that ENS has 10 days to turnaround comments on CPFM project design documents and drawings, this may need to be extended to 12-15 days.
- It is anticipated that NGMAN timeline will need to be extended by an additional 60 days.
Network Installation Services:
- Delays will occur in the fulfillment of Moves/Adds/Change requests. These requests may be delayed by one to five days depending upon the type of request. IP requests, voicemail and port activations could be delayed by one to two days. Major moves between may be delayed by three to five days.
- Expedited requests may not be easily accommodated due to the limited availability of FTE resources.
Network Operations:
It is difficult to determine how furlough days will impact Network Operations ability to provide services, however Network Operations anticipates the following:
- Response/resolution times for network issues may be delayed one business day. In some cases we may not be able to gain access to areas where work needs to be done due to the customers being unavailable to provide access to us.
- Daily Network Status Reports may be delayed by one business day due to the unavailability of staff to prepare reports and respond to network issues.
- DNS request could be delayed up to one business day due to the unavailability of staff and network emergencies.
- Network Changes (in support of projects) could be delayed and need to be rescheduled if resources become unavailable or are stretched too thin.
Technology, Architecture and Design/Quality Management:
No anticipated impact. We are able to shuffle work and pre-plan in such a way to mitigate any impact in network design or quality, except as outlined about.
