Using the OfficeAutomata Dashboard
OfficeAutomata's Dashboard shows you how to unlocks your organization's potential through data collection and visualization. It allows you to visually see your organization's digital activity and produces process maps of your workflows for automation. Ordinarily these computer-based workflows are hidden but the Activity Tracking collects data from all the users, all the time. Unlocking your organization's workflows can give you an invaluable insight into your own processes which you can then make data driven decisions to monitor, improve, standardize or automate those work processes.
There are many features that compose the OfficeAutomata's Dashboard and are specific to different roles and applications within your organization (such as time and motion studies). This guide will show and explain to you every screen in the Dashboard. There are parts of the Dashboard that are only useful to select users like managers or RPA developers. This guide will also highlight which areas different types of users should focus their attention on.
- Navigating the Dashboard
Use the left-hand navigation column to move around to different sections of the dashboard. The very first section at the top is Home.
1. Home - Dashboard
The home screen is a brief overview of all the users activities for the day, week or month.
Total: Total number of users that have agents activated on their computers.
Active: Number of users that are currently active/tracking.
Inactive: Number of users that are currently inactive/not tracking.
Daily Total: Total number of events count in a day.
Activity Rate: A function of activity and time.
2. Home - Status
This screen allows managers to access if employees are online and active. IT can also view this screen and make sure that the OfficeAutomata agents on user computers are up to date and that event data is coming into the server.
Status: Online = tracking is on. Offline = tracking is off.
Version: The OA version that the users are currently running.
Status time: The time that is last recorded on the last activity.
Status date: The date that is last recorded based on the last activity.
Events: The total number of events done by the user on the day.
The IT department can use the Status - System to access the condition of the company's or user's computers. System is a score given to devices based on average GPU, CPU, Memory and Storage usage.
This screen is more interesting than it is useful but it allows managers to view their employees as a function of their status and location around the world.
3. Home - Summary
This screen offers a brief overview of tracking hours as a function of different tasks, departments and users. This would be useful to automation or process improvement managers to see that the right data is coming in from different sources.
4. Home - Scorecard
The Scorecard is general overview of tasks. It shows which tasks are at the top of the list of being Highly Automatable or Highly Improvable. This Scorecard can guide Automation CoEs or Process Improvement mangers towards their next project. The purpose of this is to build a pipeline of tasks and processes from which to monitor, digitalize, standardize, improve or automate.
1. Tracking - Activity
Tracking - Activity allows the admin to have an overall view of the amount of activities in all the users throughout per day, week or month. IT can use this check if a user's data is coming into the server.
User: The name of the user that admin is looking at.
Dept: Department of the user
Date: Date of each activities
Time: Time of each activities
Task: A name generated by the AI
Application: The name of the application that the user has opened.
File/Webpage: The file name or webpage domain name that the user has opened.
Type: The activity type that the user has done.
UI Element: Name of the User Interface element
Frame: Excel sheet or Word page or the exact webpage URL
Location: File/application location.
Image: If a task has a high automation potential, images will be included for context.
Value: The input value that user has input in the particular cell/field.
AutoID: Framework dependent (i.e. Automation ID of Web or Windows element)
Pattern: Framework dependent (i.e. Html markers or UiAutomation Pattern Java/Windows element)
Class: Framework dependent (i.e. Html markers or UiAutomation Pattern Java/Windows element)
X-Path: UI Element Tree path of the respective framework to the UI element
Sometimes the tracking does not collect some value information such as UI Element for certain websites or applications because it is not needed.
2. Tracking - Live
Users can also view the Tracking - Live which is a live stream of data flowing from users computers into the server which happens in real time. This is an overview see what the users are doing and their current productivity.
Analytics are graphs, pie charts and other types visualizations of the data after it has been filtered and analyzed. These analytics are commonly associated with business process improvement initiatives but they can also be used to check and see if automations have been helping or not.
For more information on understanding and navigating the Dashboard's Analytics please visit the Analytics Guide.
An overview of all the processes that are trained on the processes that are done by the users.
For more information on understanding and navigating the Dashboard's Processes please visit the Processes Guide.
An overview of all the tasks that are trained on the events that are produced by the users.
For more information on understanding and navigating the Dashboard's Tasks please visit the Tasks Guide.
Allows admin to edit the users’ name, type, permission, department and cost by hourly/monthly.
Type: There are six types of users: Undefined, Admin, User, Azure, Bot and Manager.
- Undefined: Default setting when a new user is being added.
- Admin: The user is in a Dashboard administrator for their organization and they have Admin access to the Dashboard which grants them special permissions, such as access to the Admin section or editing users. Business Analysts, IT or HR may need Admin access.
- User: The users is an average employee that is being tracked. They probably have a tracker installed on their computer but do not have access to the Dashboard.
- Azure: The user is the System Admin for the end-client company with access to the azure cloud infrastructure.
- Bot: The user is apart of the digital workforce. They are RPA software and they're workflows are being tracked for by the Dashboard.
- Manager: The user is a manager who needs access to Dashboard for KPIs and BPIs but does not have editing or admin permissions.
Permission: Select either None, Read, or Write.
Cost: Select either Hourly or Monthly and then fill in value. This value can be the real cost of the user, an estimate or a government average for similar job titles.
Allow admin to save the changes
Allow admin to remove user from the dashboard.
The Admin section is used for key functions in operating and maintaining the Dashboard. The Admin section of the Dashboard is used to initiate Process Discovery session, connect systems of record to the Process mining, configure the server, add a payment system, and blacklist applications/websites.
For more information on understanding and navigating the Dashboard's Admin please visit the Admin Guide.
Process Discovery is an essential part using the dashboard to its full potential. The AI Training tab of the Dashboard's Admin is OfficeAutomata's Process Discovery.
For more information on understanding and navigating OfficeAutomata's Process Discovery please visit the Processes Discovery Guide.
For more information about using OfficeAutomata's Dashboard please contact us or visit the other training guides.
Non-Disclosure Disclaimer: This document and the information contained herein is confidential; This document is provided for information purposes only for the exclusive use of the recipients to whom it is addressed and the contents hereof are subject to change without notice. Whilst the information contained herein has been prepared in good faith, it is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Office Automata specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Any reproduction, retransmission, republication, translation, or other use of, all or part of this document is expressly prohibited, unless prior written permission has been granted by Office Automata. Office Automata, the Office Automata logo and other all other Office Automata trademarks, logos and service marks used in this document are the trademarks or service marks of Office Automata and its affiliates. All other marks contained herein are the property of their respective owners. Office Automata has intellectual property rights relating to technology that is described in this document.