Analytics Editor

Overview

The Analytics Builder allows for creating many types of data views, called “Analyses”.

Analytics can be created using data from the following data sources:

• Apps
• Tables
• Machines

The Analyitcs Editor features four main sections to configure analyses:

• The Query panel on the left for configuring the query operations to be executed on the source data before visualization
• The top bar to select the template, the display setting and the Sharing settings
• The right side panels which can be opened using the arrow in the top right corner. These include:
  • Data Panel (Universal Template only)
  • Alerts Panel
  • Formatting Panel
  • Layers Panel
• The Query result panel on the bottom which can be opened and closed with the handle on the bottom left
  • Note: This is only available for the Universal template

The different templates are described below. Settings for the different templates are described in the Analysis Model.

Templates

The following chart templates are available as a starting point for analysis building. Most templates come with a default configuration specified per datasource for each template as applicable.

Universal

The Universal Template allows you to switch between visualization types by decoupling query and visualization of the data. The Universal Template supports all visualization types and Tulip data sources (Completions, Table data, and Machine data).

When a new analysis is created using the Universal Template the data is visualized as a table by default. The visualization can be switched to any of the following types:

• Bar
• Line
• Scatter
• Histogram
• Donut
• Gauge
• Box
• Single Value
• Slideshow
• Pareto

For most visualization types, users can freely select which fields from their query results they wish to visualize and in what manner. This selection is made in the Data panel. When switching to a different visualization for the first time, the configuration in the Data panel appears empty. Users have the option to set up their visualization either manually in the Data panel or by starting with a suggestion, which can be done by clicking the "Start with suggestion" button in the center of the screen.

The prerequisites for being able to configure a visualization include:

• Having data in the query result.
• Having the appropriate fields available for the visualization. For example, a bar chart requires at least one numeric field.

If either of these requirements is not met, the Analytics Editor will display a warning message.

One Operation

Apps

• Process Completions by Date
• Process Cycle Time by User
• Process Completions by Hour and Date

Tables

• ID by Average (number Table Field here)

Machines

• OEE by Hour
• Availability by Hour
• Performance by Hour
• Quality by Hour
• Machine Time Per State

Compare Variables

Apps

• Average Step Time by User
• Compare Number Variables
• Compare Boolean Variables

Tables

• Compare Interval Fields

Machines

• State Duration By Machine

Multiple Operations

Apps

• Users by Completions and Average Cycle Time

Table

• Empty Template

Machines

• Uptime Percentage by Machine

Results on X Axis

Apps

• Individual Process Cycle Times

Scatter Plot

Apps

• Process Cycle Time by Step Time

Single Number

Apps

• Count of Completions

Tables

• Most Recent ID

Machines

• OEE
• Availability
• Performance
• Quality

Slideshow

Apps

• Slideshow of Defect Photos

Table

Apps

• Process Cycle Time Statistics by User

Tables

• ID and (text Table Field from Table)

Machines

• Duration by Machine and State

Model/Page Connections

Analysis

Create

• A user can create a new analysis by selecting any of the chart templates
• A user can create an analysis by selecting any of the predefined options in the dropdown fields in the Analytics Builder

Edit

• A user can edit an analysis by opening the Analytics Builder from the Analysis page and then choosing any template

Close

• A user can save the analysis by clicking "Save and Close" in the analytics editor. If the Analytics Editor was opened for editing an existing analysis, this will update the existing analysis.
• A user can save the analysis as a copy by clicking "Save as Copy & Close", if the Analytics Editor was opened for editing an existing analysis. This will save the current configuration as a new analysis and keep the analyses that was selected for editing in its original state.
• A user can exit the Analytics Editor without saving by clicking "Close". If changes were made in the Analytics Editor, the user will be prompted if they want to save unsaved changed. If this is declined, changes will we discarded.

In all cases, the user will be routed back to the page they opened the Analytics Editor from.

Pages

A user can access and return to the Analytics Builder from the following Pages…

• Dashboard
• App Editor
• Analysis
• App Dashboard
• Table

User Permissions

If a user has app editing permissions for a specific app, then they can create, edit, view and delete all analyses related to that app.

Tests

Requirements