Versions Compared

Version Old Version 6 New Version 7
Changes made by

Jennifer Murray (Unlicensed)

Jennifer Murray (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Default is the alias for the Operator that is signed in on the specific session for the log page. If you are entering the information for an Operator that worked the entry, you can change the "Operator" field to their alias.

Group

  • This would be the "Group" responsible for the entry being made.
    • There are times when ITSMO, ITSO Incident Managers, etc., will call in outages and outage status updates for other groups due to staffing levels, or severity of the work being done. When this happens, the "Group" reflected should be the group that is actually working on the issue.
  • Make sure you are reviewing organizational charts on a regular basis as groups need to be reported as accurately as possible.
  • If you think a group needs to be added to the drop down box or a change needs to be made to an existing group, please let the supervisors know.
  • Combining log entries can have an effect on the selection that is being made here. This will be outlined in "Combining Log Entries".

Group Contact

  • This is the name of the individual you had contact with for the specific entry being made.
    • If you are calling a group's on-call number and you get voicemail and they don't identify themselves, please leave the field empty. Do not assume you know who it is.
  • Make sure you are spelling the name of the individual correctly. It would be best to verify the spelling using the Purdue Directory and NOT previous log entries.
  • Do not put the alias for an individual in this field. You need to use their name.
  • Combining log entries can have an effect on the selection that is being made here. This will be outlined in "Combining Log Entries".

Method

  • This is how the action for the specific entry being made was initiated.we were contacted or how we contacted someone about an issue. 
    • There is a drop down box for specific pre-populated "Methods". If you think a "Method" is missing, or incorrect, please let the supervisors know. Also use the "Other" option in the drop down list if group is not listed. 
  • Brief explanation of the pre-populated methods:
    • FootPrints
      • There are times when a FP Issue will get assigned to us without us being notified via phone of an issue. This would be the method to us.
      • We also generate FP Issues and assign them to other groups like AVS.
    • In Person
      • This is used when an individual notifies us in person about an issue.
    • Incoming Call
      • This is used when an individual notifies us via phone about an issue.
    • Outage Notification
      • This is used when posting outages and or status updates for outages.
    • Outgoing Call
      • This is used when placing calls about issues.
    • Received e-mail
      • This is used when we are notified about issues or updates on issues via email.
    • Sent e-mail
      • This is used when we notify groups / individuals about issues via email.
    • Shift Turnover
      • When making entries for "Shift Turnover", do not put the name or alias of the person who gave you turnover as it can be left blank.
  • Combining log entries can have an effect on the selection that is being made here. This will be outlined in "Combining Log Entries".

...

  • This is the phone number that you dialed to contact a group, or the email address of the group you sent email to regarding this specific entry.
  • Phone numbers should be entered using area code and hyphen's as ###555-###555-####5555.
  • It is not necessary to log the number for incoming calls.
  • On occasion, an Admin will notify the IOC of an alternate contact number to be used in lieu of the documented on-call number. When this happens please enter the alternate number and in the description field of the log entry state "Admin advises to use alternate contact number".
  • If you call a group and send an email to them, please enter the information in one entry as noted below.
  • Combining log entries can have an effect on the selection that is being made here. This will be outlined in "Combining Log Entries".

...

  • If the log entry is related to a Service Alert click this button and it will open a couple of fields for you to enter information.
    • Outage Number
      • This is the unique identifier for the specific Global Footprints ticket. It can be found under "Issue #" on the "Global Issues" field of Footprints .It should be entered as "XXXXXX". "GFP#" should no longer be used and has been deprecated.
    • Outage Name
      • This is the title of the Service Alert. It must match what is listed under "Title" in the "Global Issues" field.
  • Any entries that had previously been made that pertain to a Service Alert need to be identified as being related to the Alert. There are times when Alerts are not declared until several entries pertaining to it have been entered, so you must go back and associate the entries with the outage.

...