Weekend On-call Supervisors
Sometimes the operator in TEL/IOC needs help with an issue and their supervisor is not on duty. Here are the steps that should be followed.
- If this happens during the weekend, the weekend on-call supervisor should be called. If you can not reach the on-call in a timely manner then try the next supervisor in line.
- Monday - Friday the on-call is the person who is scheduled to be on-call that weekend. ( So Mon - Sun is the same person. )
- The on-call supervisor can be contacted at any time at 765-496-4272.
- For each incident send an email to csc leadership (cscleadership@purdue.edu) stating who was called (and if they were reached,) and what the issue was. This is similar to sending email when contacting an admin. Log it as well.
...
If the bridge is opened when there is no supervisor on duty, the IOC should contact the CSC/IOC Manager. The manager will join the bridge; the shift or weekend on-call supervisor will not join the bridge, and will be available to communicate with staff working in B22. The Slack/Skype application may be used to facilitate communication with the manager and supervisor. As well as a direct phone call.
The phone bridge is currently used as a back up, in case Teams is down.
Remote Monitoring
In the event remote monitoring of the IOC is necessary (i.e services have moved off campus/off site, limited IOC services are offered, etc.), calls to the IOC Reporting Line can be forwarded to an alternative number, temporarily.
...
PUPD Calls
Sometimes PUPD will call requesting information from ITaPPurdue IT, e.g. computer session data for a missing student. They may have already sent email to ITSP, but they are calling us so that we can contact ITSP immediately. Call Security Operations when this happens, and send email to itsp-services@purdue.eduCall and follow up email to: enterprisesec@purdue.edu Primary: Steve Medel 737-229-0150 Secondary: Justin Greer 765-444-2994. Although security@purdue.edu may be listed as a follow-up email on some sources, emails to this address will generate a FootPrints ticket for each new email or keep reopening tickets if cc'd (like when itap@purdue.edu is cc'd). For now, enterprisesec@purdue.edu is the preferred follow-up address. If PUPD is asking for something else, consult the on-call supervisor as needed.