# Getting Started with TemplateOne

> **TemplateOne** is a fully customizable, flexible and re-usable starting point to develop custom **Process Mining** dashboards and KPIs based on a businesses needs. **TemplateOne** provides a set of out-of-the-box dashboards. See [TemplateOne menus and dashboards](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-menus-and-dashboards#templateone-menus-and-dashboards).

## Introduction

**TemplateOne** is a fully customizable, flexible and re-usable starting point to develop custom **Process Mining** dashboards and KPIs based on a businesses needs. **TemplateOne** provides a set of out-of-the-box dashboards. See [TemplateOne menus and dashboards](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/templateone-menus-and-dashboards#templateone-menus-and-dashboards).

**TemplateOne** offers the flexibility to add process-specific dashboards, metrics, and KPIs.

## Prerequisites

To roll out **TemplateOne** to end-users, a specific development setup is required.

It is assumed that:

* you have downloaded the **TemplateOne** release package.
* the development tools described in are installed.
* you have a Git repository for version control of the connector. See [Using a Git Repository](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/process-mining-using-a-git-repository#using-a-git-repository). For dashboard development and creating app releases, you also need to have a **UiPath Process Mining** installation with access to the Git repository.

## TemplateOne release package

The **TemplateOne** release package includes a *Basic SQL connector* that enables you to load your cases and events data for use in the **TemplateOne** dashboards. There are two available **TemplateOne** packages.

* `TemplateOne-EventLog-version.mvtag`;
* `TemplateOne-Cases-EventLog-version.mvtag`.

Based on the format of your input data, you choose the appropriate package.

| Package | To be used with when... |
| --- | --- |
| `TemplateOne-EventLog-version.mvtag` | the input data for cases and events is available in one input file. |
| `TemplateOne-Cases-EventLog-version.mvtag` | the input data for cases and events is split up into two different input files. |

In **TemplateOne**, all transformations are grouped together and are part of the SQL connector. The SQL connector together with the app dashboards form the app. See the illustration below.

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-53335-72e48321-5677413d.webp)

## From data to dashboard

| Step | Description |
| --- | --- |
| Extract | The data is extracted from the source systems and loaded into a SQL Server database without making any changes to the data. |
| Transform | The raw data is transformed in a format that is expected by the dashboards using SQL transformations. |
| Load | The transformed data is loaded into the dashboards. |

See the illustration below for an overview.

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-57289-0d5d7b18-9b8f92a2.webp)

The **TemplateOne** release package contains the dashboards definitions and covers all the steps to display the data into the dashboards.

### Next steps

[Steps to roll-out TemplateOne](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/steps-to-roll-out-templateone#steps-to-roll-out-templateone).