Procedures: Difference between revisions

From NEOSYS Technical Support Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
Here are procedures to be followed by Support Staff in respect to various technical matters in day to day operations of client issues.
Here are procedures to be followed by Support Staff in respect to various technical matters in day to day operations of client issues.


==NEOSYS Support Policies==
== NEOSYS Support Policies ==
In order to maintain good payment speed by clients NEOSYS needs to restrict support to clients that dont pay their bills on time, however the degree of restriction needs to depend on an intimate knowledge of the client which cannot be expected from all NEOSYS support staff. Therefore we will use a simple escalation policy as follows:
In order to maintain good payment speed by clients NEOSYS needs to restrict support to clients that dont pay their bills on time, however the degree of restriction needs to depend on an intimate knowledge of the client which cannot be expected from all NEOSYS support staff. Therefore we will use a simple escalation policy as follows:


Line 12: Line 12:
# Contacting the client or if the client contacts support staff regarding backup failures and to take measures to fix these failures
# Contacting the client or if the client contacts support staff regarding backup failures and to take measures to fix these failures


== Procedure for handling problems with report totals ==
Questions with regards to report totals should not be escalated to the programmers without following this procedure. If the total can be be broken down into items (as they nearly always can be in NEOSYS) then only a problem where the items dont add up to a total should be escalated, since that would be a system error.


== Backup Procedures ==
== Backup Procedures ==

Revision as of 08:12, 16 November 2009

Here are procedures to be followed by Support Staff in respect to various technical matters in day to day operations of client issues.

NEOSYS Support Policies

In order to maintain good payment speed by clients NEOSYS needs to restrict support to clients that dont pay their bills on time, however the degree of restriction needs to depend on an intimate knowledge of the client which cannot be expected from all NEOSYS support staff. Therefore we will use a simple escalation policy as follows:

NEOSYS SUPPORT MANAGERS WILL maintain an overdue/stop list on a whiteboard visible to all support staff. Generally clients will go on the list when their invoice is seven days overdue and come off only after satisfactory commitment to pay have been obtained.

NEOSYS SUPPORT STAFF WILL discretely refer any calls for support from client on the overdue/stop list to support managers for handling.

This policy excludes:

  1. Contacting the client to change the USB disk on the scheduled day, in case they haven't done so by 12 pm
  2. Contacting the client or if the client contacts support staff regarding backup failures and to take measures to fix these failures

Procedure for handling problems with report totals

Questions with regards to report totals should not be escalated to the programmers without following this procedure. If the total can be be broken down into items (as they nearly always can be in NEOSYS) then only a problem where the items dont add up to a total should be escalated, since that would be a system error.

Backup Procedures

Preparing daily backup report

  1. Note the success, failure and other error of the clients backup mail in an excel sheet and forward the same to your manager.
  2. If there is a backup failure or backup is not available, check wiki to take necessary steps.
  3. If there is any unknown error, forward the same to your manager.

Updating Nagios incase of failures

  1. If the backup failure is unsolved, schedule downtime Neosys service in Nagios till 01 am.
  2. If the backup did not happen because of server down. Call the IT person; ask him to re-boot the server and check wiki to do necessary step ahead and schedule downtime to Nagios for 2hours.
  3. If there is an error "Backup->Impossible" on Nagios check wiki and schedule downtime to Nagios for 2hours.

Interchange backup USB mail reminder

  1. Basically all the clients have different days to change their backup USB. All the notification can be seen on Nagios at 12.00 pm every day.
  2. When you see the change backup notification on Nagios at 12.00 pm, send a mail to the IT person or the person who changes the USB. As you send the mail schedule downtime for Neosys services for two hours.
  3. Check the Nagios at 2.00 pm if the backup USB is changed, don't send another mail and stop there. But if backup is still not yet changed, send a another mail and this time cc the mail to your manager. After sending the mail, schedule downtime for Neosys service for more two hours.
  4. Now at 4.00 pm if you still find the backup USB not changed. Call the IT person and ask him to change the USB ASAP and schedule downtime for Neosys services for one hour.
  5. Now at 5.00 pm check Nagios and see if the backup USB is changed and if not changed. Send the mail to everyone from the backup mail.
  6. If the backup is still not changed, escalate the issue to your manager.