Logging Incidents for Users
- Former user (Deleted)
- Mayuresh Balaji Kamble (Unlicensed)
- Chilukuri Srinivasa Reddy (Unlicensed)
The Incident Management is a process to restore normal service operations and minimize the adverse impact of the interruption on business operation, thus, ensuring that the best possible service quality and availability are maintained. An Incident is an unplanned interruption to an IT Service or a reduction in the quality of an IT service.
The Analysts may need to log Incidents for the End Users if they do not have access to the SUMMIT application or if the End Users are calling in to report their issues.
To log Incidents for End Users:
- Select Incident > User > Manage Incidents > New Incident for User.
- On the LOG INCIDENT page, provide the required details as described in the following table:
Field | Description |
|---|---|
Icons | For information about the icons, see Viewing/Updating Incident Details. |
Tenant | Select the Tenant for the Incident. |
Caller | Type in the name of the caller logging the Incident. |
Medium | Select the Medium through which you want to log Incident. You can select one of the medium from the drop-down list.
|
Source | Select the source from where Incident is created. |
CC | Select the name of the users to whom details about the Incident should be sent. |
Symptom | Type in the symptom for the Incident. |
Description | Type in the description about the Incident. |
Attachments | Upload attachments related to the Incident, for example, error messages, screen shots, logs, and so on. Note: You cannot upload attachments more than 4 MB. You can upload only those file types configured on the APPLICATION SETTINGS page by the Administrator. For more information, see Application Settings. |
Figure: LOG INCIDENT FOR USER page
Note:
The fields that are displayed on this page depend upon the configuration done by your Administrator (see: Configuring Incident Management Module). You may find some additional or different fields.
You can assign a Secondary Analyst to the Incident if configured on the Tenant page. For more information about configuring the Incident Management module, see Configuring Incident Management Module.
You can log an Incident by using the IVR functionality. The Administrators must pass a query string in the URL to log the Incident using the IVR functionality. For example, “?phonenumber=1234567890". On doing so, the user details are listed and you can log the Incident for that user.
- If the user is not added to the User list, you can add the user details from the NEW INCIDENT page. Click
to add the user details. For more information, see SUMMITAI General
Figure: NEW INCIDENT page: add User
- The IVR functionality is enabled when the check box, Enable IVR Mode to Log Incident is selected on the APPLICATION SETTINGS page. For more information, see SUMMITAI General.
3. Type in the other required fields under the GENERAL, COMMUNICATION, CHECKLIST, RELATIONSHIP, TROUBLESHOOTING, VENDOR INFORMATION, ADDITIONAL INFORMATION, and ORCHESTRATION tabs. For information about the fields under these tabs on the LOG INCIDENT page, see Field Description.
4. Click SUBMIT. A new Incident is created for the End User.
Note:
The details that you receive in the confirmation message depend upon the confirmation message configured by the Administrator.
.
Figure: Example of confirmation Message of logging Incident for Users
Field Description
The following table describes the fields and tabs on the NEW INCIDENTS FOR USER page:
You can provide the general information about the Incident, such as assigned Workgroups, assigned Analyst, Response time, Solution, and so on under the GENERAL tab.
Figure: GENERAL tab
The following table describes the fields under the GENERAL tab:
Field | Description |
|---|---|
CLASSIFICATION | |
Urgency | Select the Urgency level from the list. The Incidents should be resolved according to the Urgency. Example: Immediately, EOD, and After a Day
|
Priority | Select the Priority from the list to indicate the precedence of the Incident. Example: If the Resolution time for P1and P2 Priority are set as 120 and 180 minutes respectively, the Incidents should be Resolved within the specified time. P1 should be resolved first then P2. |
Impact | Select the Impact from the list to define the affect of the Incident on the users. Example: High, Medium, Low |
Classification | Lists the various Classifications under which the Incident can be considered for resolution. To select the Classification, click the Search icon. The Classification list page is displayed. You can use the Expand icon to view the Sub-classifications in the Classification tree. Select a Classification that you want to associate with the Incident. |
Category | Lists the various Categories under which the Incident can be considered for resolution. To select the Category, click the Search icon. The Category list page is displayed. You can use the Expand icon to view the Sub-categories in the Categories tree. Select a Category that you want to associate with the Incident. |
ASSIGNMENTS | |
Workgroup | Select the Workgroup to which you want to associate the Incident. |
Schedule Date | Click the Calendar icon to select the scheduled date and time for the Incident. |
Assigned To | Select the Analyst to whom you want to assign the Incident. Click the Analyst icon to view the workload of the Analyst. It displays the number of Incidents and Work Orders assigned to the selected Analyst along with their status. |
Service Window | Specify the Service Window details. |
Response SLA | Displays the Response SLA date and time.
|
Resolution SLA | Displays the Resolution SLA date and time.
|
Violation | Displays the SLA status for both response and resolution time as violated or not, Yes or No. If Violation is Yes, you need to provide a reason.
Figure: Violation pop-up |
EXPECTED TIME TO RESOLVE (ETR) | |
ETR | Click the Calendar icon to select the expected time to resolve the Incident. |
Remarks | Specify the Remarks. |
You can share the user log with the End User as comments under the COMMUNICATION tab. These comments are sent to the End User and to the default and specified CC e-mail members automatically via an e-mail when you click the SUBMIT button. The Private Log information is shared with the other team members or the members of other Workgroups through an e-mail. You can also log your efforts under the Private Log section if manual effort update is allowed by the Administrator (see: Configuring Incident Management Module).
Figure: COMMUNICATION tab
The following table describes the fields under the COMMUNICATION tab:
Field | Description |
|---|---|
Select Template | You can select a template from the list for user communication. |
User Communication | Type in the Incident information that you want to share with the End User through an e-mail. |
Private Log | Type in the Incident information that you want to share with other members of your team or the members of other related Workgroups. Whenever you type in information in this section, an e-mail is sent to all the team members of the Workgroup. These e-mails are not sent to End Users or Callers. When you reply to an escalation e-mail, the reply is updated here and an e-mail is sent to all the team members of the Workgroup and the Workgroup Owner. |
Attachments | You can upload communication file if available using this option. |
There may be a list of actions you need to perform before changing the status of an Incident. Under the CHECKLIST tab, you can verify these actions (if configured by the Administrator, see Configuring Checklist IM) and complete them before changing the status of the Incident. Based on what action is taken on the Task, update the Task Status, and provide your remarks in the Remarks text box. You can also drag and drop the Tasks to change the sequence of Tasks.
Figure: CHECKLIST tab
You can link related Incidents, Problem Records (PRs), Assets, CIs, Events, and so on to the Incident using the Link list under the RELATIONSHIP tab. You can also create new Incidents, PRs, SRs, and so on to link to the Incident using the Create list.
To link any module to an Incident:
Click the module name in the Link drop-down list. The RELATIONSHIP pop-up page is displayed.
Figure: Relationship pop-up page
Enter the required details and click SEARCH.
Select the appropriate entity and click LINK.
The linked entity is displayed under the RELATIONSHIP tab.
Figure: RELATIONSHIP tab
Note:
If you create a Change Record (CR) from the RELATIONSHIP tab of the Incident page, the Incident cannot be closed until the CR is in Implemented status. This is applicable, if the check box, Linked CR Implementation Prevents Incident Closure, is selected by the Administrator (see: Configuring Change Management Module). Notification e-mails are sent to the Incident Caller for each update of the CR.
If the Do Not Update Child Priority check box is selected, while Incident linking the Priority of the Child Incident is not changed to the Priority of the Parent Incident. In such a case, the configured Priority Matrix for the Parent Incident is not applicable for the linked Child Incident.
When a Child Incident is linked to a Parent Incident, the Response Time of the Child Incident is equal to the linked time.
If you link a Configuration Item for which the SOP is configured, you can view the SOP details by clicking 
. You can also view the SOP details in Incident Reports.
Figure: SOP Template
If you link a Configuration Item for which SLA is configured, the Priority and SLA of the Incident changes as per the Priority and SLA configured for the CI. However, the SLA and Priority configured for the CI cannot override the SLA and Priority configured for a User Matrix.
You can see other similar open Incidents, Knowledge Records (KR), Change Records (CRs) to better analyze and provide a quick solution to the Incident under the TROUBLESHOOTING tab. You can view the list of Incidents, which are similar to this Incident to take necessary steps to resolve it.
Figure: TROUBLESHOOTING tab
The following table describes the fields under the TROUBLESHOOTING tab:
Field | Description |
|---|---|
SIMILAR OPEN INCIDENTS | Displays the open Incidents, which have similar symptom as this Incident. |
SIMILAR CLOSED/RESOLVED INCIDENTS | Displays the closed/resolved Incidents, which have similar symptom as this Incident. |
RELATED KNOWLEDGE ARTICLES | Displays the Knowledge Records related to this Incident and which may be useful in resolving this Incident. |
POSSIBLE REMEDIATIONS | Displays the possible remedies for this Incident (from the similar resolved Incidents). |
POSSIBLE ROOT CAUSES | Displays the possible causes for this Incident. |
RELATED CHANGE RECORDS | Displays the Change Records related to the Incident. |
RELATED CONFIGURATION ITEMS | Displays the Configuration Items associated with the Incident. |
CURRENT ENVIRONMENTAL ISSUES | Displays the current environmental issues related to the environment. This information helps to determine the possible causes of the Incident. For example: If server or network is down, it is displayed here and which may be the cause for an Incident logged for No Internet Connection issue. |
You can provide details about any external Vendor who is related to the Incident under the VENDOR INFORMATION tab. You can add or view details of the external support where an external Vendor is involved. The external support details are not shared with the End User, but is added here for your reference. This tab is available if enabled by the Administrator (see: Configuring Incident Management Module).
Figure: VENDOR INFORMATION tab
The following table describes the fields under the VENDOR INFORMATION tab:
Field | Description |
|---|---|
Vendor | Lists the configured Vendor. Select the Vendor name of the list. |
Location | Type in the location of the Vendor. |
Configuration Item | Lists the mapped CIs for the Partner Incident. Select a Configuration Item from the list. |
Contact Person | Displays the name of the person who had helped to resolve or in providing the information over the customer Incident. |
Incident ID | Type in a unique identification number of the Vendor Incident, which is logged by the Vendor in relation to an Incident. After you enter the Vendor Incident ID, it is mandatory to specify the Start Date and Status details. |
Status | Select the status of the Vendor Incident. |
Urgency | Lists the configured Vendor Incident Urgency options. Select the Urgency option from the list. |
Start Date | Specify the date and time on which the Vendor Incident is initiated. Click the Calendar icon to select the start date of the Vendor Incident. |
Impact | Lists the configured Vendor Incident Impact options. Select the Impact option from the list. |
Resolution Deadline | Specify the resolution deadline provided by the Vendor for an Incident. Click the Calendar icon to select the resolution deadline date of the Vendor Incident. |
Priority | Lists the configured Vendor Incident Priority options. Select the Priority option from the list. |
End Date | Specify the date at which the Incident has been closed. Click the Calendar icon to select the end date of the Vendor Incident. |
Underpinning Contract | Lists the mapped Underpinning Contract options for the Vendor Incident. Select the Underpinning Contract from the list. The selected Underpinning Contract defines the SLA for the Incident. |
SLA Violated | Displays the SLA status for both response and resolution time as violated or not.
|
Solution | Specify the solution that is provided to resolve the Vendor Incident. |
You can document the additional information about the Incident under the ADDITIONAL INFORMATION tab. Based on the organization’s needs, the Administrator configures the information to be displayed under this tab (see: Configuring Incident Management Module). OLA details are also displayed under this tab calculating OLA and OLA violation whenever the Incident is transferred between the Workgroups (based on OLA configuration in the SLA). Both the Source Workgroup (The Workgroup from which the Incident is transferred) and Target Workgroup (The Workgroup to which the Incident is transferred) should be configured in the OLA contract to capture these details.
Figure: ADDITIONAL INFORMATION tab
You may need to perform some repetitive tasks in order to resolve an Incident. Under the ORCHESTRATION tab, specific actions can be executed automatically or with very less manual intervention. The Administrators need to configure the Orchestration Scripts and the Conditions when these Orchestration Scripts should be executed. Based on the configuration, the scripts are executed on the target machine. For more information about Orchestration, see Orchestration.
Figure: ORCHESTRATION tab
TEAM FOUNDATION SERVER (TFS) is a Microsoft product that manages the entire application life cycle and enables Development and Operations capabilities.
TFS is integrated with SUMMIT Suite to manage the development and support work simultaneously, required to fix a problem. When TFS is integrated with SUMMIT Suite, a bug is automatically logged in TFS for any Incident, logged. Any modification in the Incident is updated in the bug, and vice-versa. This facilitates a smooth resolution of the problem eliminating the hassle to update the Incident and Bug manually.
You can configure the fields under the TFS tab to create a bug in TFS for the logged Incidents. The Bug in TFS is updated based on the configuration of the fields on the TFS tab of the Incident.
Figure: Log Incident: TFS
Field Description
The following table explains the fields under the TFS tab:
Field | Description |
|---|---|
Team Project Collection | Select the Team Project Collection name in the drop-down list. For more information about configuring the Team Project Collection, see Configuring TFS Project. |
Team Project | The Team Projects created for the Team Project Collection is listed in the drop-down list. |
Work Item Type | Select the required Work Item Type. |
Note:
The following tabs are displayed on the NEW INCIDENT FOE USER and INCIDENT ID page based on the configuration on the TENANT page: Troubleshooting, Vendor Information, Orchestration , Checklist, Additional Information, and TFS.
ACTIONS
This section explains all the icons displayed on the ACTIONS panel of the NEW INCIDENT FOR USER page.
TEMPLATES
Click TEMPLATES to select a template from the TEMPLATES pop-up page. Select a Template from the list and click SUBMIT. Using the configured Templates you can quickly update the Incidents without the need to re-enter all the values. The Templates are configured based on the commonly logged issues and values are entered in the Templates. When the Analysts come across an Incident similar to the defined Template, they can select the Template and all the values defined in the Template are auto-populated. This saves time and also reduces the possibility of making mistakes.
Figure: TEMPLATES pop-up page
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ