Mt Info

Management Information (MtInfo)

Management Information provides crucial information for process and functional administrators and business managers about the processing of requests in the Spider. It provides insight into the entire chain.

MtInfo activation

To activate MtInfo within a process this must be set via the SLA. More information and how to do this can be found at: Mt Info SLA.

MtInfo - Statuses

The statuses as they pass in the MtInfo

Status	Description
Todo	It is not directly reflected as a status, but is visible in MtInfo below the Summary heading.
Failed	The request was not processed successfully.
Failed Requests Waiting for Confirmation	Requests where there is still an action to be performed.
Success	Requests that have been processed successfully.
Requests Changed by operator	Requests that have been modified by an Operator.
Returned Requests	Requests to be rescheduled later.
NeedsOk Requests	Requests that require confirmartion from a user.

Mt Info - Request information

These images shows the daily MtInfo of requests processed yesterday.

Failed

We see that there are 2 requests in Failed which failed for whatever reason:

• The robot has encountered an error in the process or application
• The process specifies that a failed request may not be presented again if it goes wrong
• RFN and Changed Failed Process Step then have no added value for this process.
• The request is manually set to Failed by an Operator

The requests can be found in Spider in Requests > Failed.

Failed requests waiting for confirmation

The number of requests where an action is still required. These requests are in RFN and can be found in the Spider in Confirmations > RFN Requests.

To keep this number as low as possible it is necessary that an action is taken on these requests. This can be done by offering the request again or dropping it. This is a manual action which needs to be handled by an employee.

Success

These are requests that have been successfully processed by the robot. These can be found in the Spider in Requests > Success.

Requests changed by Operator

In the MtInfo you can see that an Operator has modified a request. To find this back, this can (for the time being) only be done in the Audit Logs. In the Audit Log you can also see which Operator has modified this request. This can also be found in the Spider in Requests > Changed.

Returned requests

A request is created by the robot which may be started at a later time.

NeedsOk requests

In dit geval staan er nog 2 requests welke actie vereisen. In the question column you can also ask a question to the employee who should approve or deny the NeedsOk request.

MtInfo - SLA information

This contains the daily status information of the number of requests handled within the SLA together with the status of the request.

The percentage of requests which have failed, but have been handled within the SLA. The percentage of requests which have been successfully processed within the SLA. This SLA information can also show the following information:

• The percentage of requests that failed, but were handled outside the SLA.
• The percentage of requests which are successful, but were handled outside the SLA.

MtInfo - Summary

Shows the summary of the last 24 hours:

• Total requests received: The total number of requests received.
• Total requests processed by the robot(s): The number of requests processed by the robot.
• Total requests not picked up by the robot(s):
• This should always be 0. In general, this only occurs if there has been a disturbance with the robots and applications that could not be accessed.
• Another reason may be that the robot cannot handle the number of requests in time. It is then necessary to connect multiple robots for the same process or run the process more often and possibly standalone on a robot.
• Saving time (hours): The time saved according to the SLA.
• Full-time equivalent(FTE): Savings based on FTEs.

Reports

In a process, reports can provide insight into actions, business rules, etcetra. Example:

In a process, insight is required into a number of components. These can be created as a report in the Spider. Next, the robot will trigger these reports as soon as they occur in the process.

Reports can be extended on request, to gain insight into the process and where possible improvements can be made.

Reportgroups

from version 1.8.0, it is possible to split the Report information into groups. This makes it possible to get a quicker overview of process reports. More information on how to configure this can be found in Reportgroups

In the Mtinfo, this could then look like this: