There are several things in common in the approaches taken for critical situations and ongoing work; both of which can affect our clients and other support staff. The following describes the possibilities, with guidelines about when they apply.
When dealing with an urgent problem, e.g. the failure of a service used by many people, it's important to both communicate with those affected, while at the same time maximizing the time available for the staff working to resolve the problem. This is done by said staff handing off the communication to other staff, who become the "Point of Contact" for the problem.
The kind of communication used may depend upon the problem, as some problems limit what communication can be used (e.g. failure of e-mail). In general, we have at least these possibilities:
Anything that could cause a question of the Help Centre should be reported to them. That's primarily the teaching environment, or grad student use of the general.cs environment. In principle it could be almost anything, so it's safest to always let them know of a serious problem. Calling Lori (Suess) directly works best. For planned outages, letting consultant@math.uwaterloo.ca know in advance works best (and Lori sees that too).
Depending upon the nature of the problem, it can be quite effective to let the "Administrative Officer" know, who will spread the word to other staff, e.g. the "Department Secretary", "Secretary/Receptionist", and various "Administrative Coordinators". I.e. tell Sher, Michelle, Helen, Debbie and Wendy. If the problem affects the teaching environment, then let someone in ISG know, and depending upon the severity, the (Associate) Director of Undergraduate Studies.
EMail to
scs-everybodyis useful in situations where it's expected that most of CS will want to know. Other lists also exist, e.g.
There is an Important Bulletins section in the CSCF home page. The goal is to record all CSCF service outages. Both the downtime and uptime are to be recorded. The downtime is recorded as soon as we know of the outage, the uptime is recorded when the problem is resolved.
It's updated via:The telephone extension 31100 is to be used for announcements of computing or network problems that prevent access to the bulletins in the CSCF home page. Doing this in advance for scheduled outages is a good idea.
Information needed to update the announcement is in the usual place for secure information, or check AnnouncementVoiceMailPassword. To update the message, use the temporary greeting feature (82 3) of Call Pilot and set an expiry date/time when you have finished recording the greeting. It's good to have an accurate message, so choose a generous expiry time if it's not obvious when service will be restored. In such cases, that then requires manual removal of the message shortly after restoration of the service.
In cases where electronic communication is affected, or simply when enough people show up asking about a problem, paper signs on the doors at the ends of the CSCF corridor have proven effective.
It was once suggested that such signs would be placed in the main CS office area.
The uw.cscf.fyi newsgroup is handy for letting CSCF staff know about problems. Its use isn't restricted to serious problems. While not advertised as required reading for clients, some do.
uw.cscf.system is intended to be displayed upon login to a standard environment, to relate "changes to the local computing environment that will likely affect how people do their computing". It uses the `read_system_news` command, which in practice means that only XHier'd Solaris systems see it. So while still present, it's likely not very effective.
You can post to the newsgroups via mail to uw.cscf.fyi@news.cs.uwaterloo.ca and uw.cscf.system@news.cs.uwaterloo.caI | Attachment | History | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|---|
doc | WhiteBoardStatusGeneric.doc | r1 | manage | 32.5 K | 2012-01-19 - 14:37 | LawrenceFolland | White Board sheet to indicate whereabouts |