Home / Case Studies / MES / Plant Dashboard App

MES CASE STUDY · ThingWorx + SharePoint + Databricks

Self-Service Plant Dashboards on ThingWorx with SharePoint and Databricks Data

By PSPTechHub · October 2026

Conceptual illustration of connected medical-device production equipment and manufacturing dashboards

SUMMARY

Plant teams need one screen that shows how every line is doing: output, downtime, defects, safety and quality. PSPTechHub worked on PlantApp, a ThingWorx app where each site builds its own dashboards from ready-made tiles, without code. It pulls line data every 15 minutes, reads local lists from SharePoint and loads safety and quality audit results from Databricks. Slow sources are copied into ThingWorx on a schedule (cached), so dashboards open quickly even when the source system is slow.

AT A GLANCE

Industry

Consumer goods manufacturing

Users

Plant leaders, line teams, quality and safety owners

Platform

PTC ThingWorx

Data sources

Line performance and defect systems, SharePoint lists, Databricks

Refresh

Line data every 15 minutes; audit data cached every 30 minutes for 31 days

Process area

Plant performance, daily management, safety and quality

The Problem: Plant Data Was Spread Across Too Many Systems

The information a plant team needs every morning lived in many places: line performance systems, defect tracking, SharePoint lists kept by each site, and a global audit database. Pulling it together was slow and different at every site.

Too many places to look

Downtime, alarms, quality, defects and audits each lived in a separate system.

Every site is different

Each plant tracks different KPIs and lines, so one fixed dashboard didn't fit anyone.

Slow screens

Reading SharePoint lists live every time a dashboard opened made screens slow to load.

Audit data moved

Safety and quality audits moved to a new data platform, Databricks, so the old direct database link stopped being the right way in.

Setup needed an expert

Adding a new data source or site needed someone who knew ThingWorx well.

The Solution: Dashboards Each Site Builds Itself

PlantApp lets each site design its own dashboards in three levels — main screen, dashboard, section — and fill them with tiles. PSPTechHub's work added fast SharePoint data, the Databricks audit link and a simple configuration screen.

Build dashboards without code

Pick a main screen, add dashboards, then add sections such as Action Plan, Flow, Pit Stop or Raw Data.

Ready-made tiles

Gauges, images, manual inputs and KPI tiles, each pointed at a line, a time range and a data source.

Line data every 15 minutes

Downtime, alarms, cleaning and checks, quality and all line KPIs refresh every 15 minutes per line.

Defects in view

Found, critical and open defects, plus the raw defect list, appear next to line performance.

SharePoint lists as tiles

Add a SharePoint list from the settings popup; a tile is created and its data appears on the dashboard.

Fast loading with caching

SharePoint data is copied into ThingWorx on a schedule for a set number of days, so dashboards open quickly.

Filters per tile

The same SharePoint list can feed several tiles, each with its own filter and date field.

Safety and quality audits from Databricks

Audit results by category are cached every 30 minutes for the last 31 days, and categories can be added.

Simple configuration screen

Site settings and data refreshes are managed from one screen instead of inside ThingWorx.

How It Works: From Data Source to Morning Meeting

1

Set up the site

The site name is set once on the configuration screen and the connections are switched on.

2

Design the screen

A site user creates a main screen, a dashboard and the sections they need.

3

Add tiles

They add KPI, gauge, SharePoint or audit tiles and choose the line, time range and filter.

4

Data is collected

Line data refreshes every 15 minutes; SharePoint and audit data are cached on a schedule.

5

Open and act

The team opens the dashboard in the morning meeting and sees every line in one place.

6

Keep it healthy

Each cache records when it last ran, how many rows it holds and any error, so problems are easy to spot.

For IT Teams: How It Is Built

For IT Teams: How It Is Built

ThingWorx holds the screens, settings and cached data; each source system stays the official record for its own data.

1. PlantApp screens

Main screens, dashboards, sections and tiles configured by each site

2. Configuration tables

Store each site's screens, tiles, KPIs and safety and quality triggers

3. Connection services

One set of services per source: line data, defects, SharePoint and audits

4. Caching and schedulers

Copy slow sources into ThingWorx and log the last run and any errors

5. Data sources

Line performance and defect systems, SharePoint lists, Databricks

Technology responsibilities

Service

Purpose

SharePoint tile creation

Creates a cached SharePoint source when a user adds a SharePoint tile

SharePoint cache

Caches list data on demand and on a schedule, with per-tile filters

Databricks connector

Checks and starts the cluster, runs queries and refreshes its access token

Audit connector

Reads safety and quality audits from Databricks and caches them by site

Configuration screen

Holds site settings and audit categories in one place

Design decisions

Three configuration levels — main, dashboard, section — so any site can build the screens it needs

Every data source uses REST APIs with its credentials kept in one connections area

Slow sources are cached, so dashboard speed doesn't depend on the source system

Each cache stores its last run time, row count and last error for easy support

The Databricks link closes each query session after use and refreshes its access token on a schedule

Each feature is tagged so it can be deployed from one environment to the next in one step

Outcomes

Outcomes

One screen for the plant

Line performance & defectsLists & auditsOne screen

Each site builds its own

Site lines & KPIsConfigurable tilesNo new code

Fast dashboards

Slow data sourcesScheduled cachingFast loading

Audits on the new platform

DatabricksSafety & quality auditsConnected

Easier support

Cache statusError recordsEasier support

Simple rollout

Site nameTagged deploymentSimple rollout

This solution fits if you need to…

Build configurable plant KPI dashboards in ThingWorx

Show SharePoint list data on a ThingWorx dashboard

Speed up ThingWorx dashboards by caching slow data sources

Connect ThingWorx to Databricks with REST APIs

Show safety and quality audit results on a plant dashboard

Frequently Asked Questions

Frequently Asked Questions

In PlantApp, a user adds a SharePoint list through the settings popup. This creates a dashboard tile with its own filter and date field. PSPTechHub's work added scheduled caching of SharePoint data, so local plant lists can appear alongside line performance and audit results without reading the source list every time a dashboard opens.

PSPTechHub's work used scheduled caching for slow sources, including SharePoint lists and audit data. Dashboards read copies held in ThingWorx instead of waiting for each source system to respond. Each cache records its last run, row count and errors for support; this case study does not report a measured loading-time improvement.

The connector uses REST APIs to check and start the Databricks cluster, run queries and refresh its access token. The audit connector then reads safety and quality audit results and caches them by site. This project used that connection without extra extensions and closed each query session after use.

Yes. Within PlantApp's configured dashboard structure, site users create main screens, dashboards and sections, then select ready-made KPI, gauge, image, manual-input, SharePoint or audit tiles. They choose the lines, time ranges and filters relevant to their plant without writing new code for those screens.

In this project, line performance and defect data refresh every 15 minutes per line. Audit data is cached every 30 minutes for the last 31 days; both are configurable. SharePoint lists are cached on a separate schedule. These are scheduled updates, not continuous real-time streaming.

This PlantApp dashboard displays downtime, alarms, cleaning and checks, quality and line KPIs, plus found, critical and open defects. SharePoint list data and safety and quality audit results appear alongside those measures. Each site's tiles select the relevant lines, time ranges and filters.

The app is deployed by tag to the new environment, and the site name is set on the configuration screen. Connections are switched on, then the site configures its own screens, sections and tiles. PSPTechHub's work brought site settings and data refresh controls into one configuration screen rather than requiring users to manage them inside ThingWorx.

In PlantApp, a user adds a SharePoint list through the settings popup. This creates a dashboard tile with its own filter and date field. PSPTechHub's work added scheduled caching of SharePoint data, so local plant lists can appear alongside line performance and audit results without reading the source list every time a dashboard opens.

PSPTechHub's work used scheduled caching for slow sources, including SharePoint lists and audit data. Dashboards read copies held in ThingWorx instead of waiting for each source system to respond. Each cache records its last run, row count and errors for support; this case study does not report a measured loading-time improvement.

The connector uses REST APIs to check and start the Databricks cluster, run queries and refresh its access token. The audit connector then reads safety and quality audit results and caches them by site. This project used that connection without extra extensions and closed each query session after use.

Yes. Within PlantApp's configured dashboard structure, site users create main screens, dashboards and sections, then select ready-made KPI, gauge, image, manual-input, SharePoint or audit tiles. They choose the lines, time ranges and filters relevant to their plant without writing new code for those screens.

In this project, line performance and defect data refresh every 15 minutes per line. Audit data is cached every 30 minutes for the last 31 days; both are configurable. SharePoint lists are cached on a separate schedule. These are scheduled updates, not continuous real-time streaming.

This PlantApp dashboard displays downtime, alarms, cleaning and checks, quality and line KPIs, plus found, critical and open defects. SharePoint list data and safety and quality audit results appear alongside those measures. Each site's tiles select the relevant lines, time ranges and filters.

The app is deployed by tag to the new environment, and the site name is set on the configuration screen. Connections are switched on, then the site configures its own screens, sections and tiles. PSPTechHub's work brought site settings and data refresh controls into one configuration screen rather than requiring users to manage them inside ThingWorx.

In PlantApp, a user adds a SharePoint list through the settings popup. This creates a dashboard tile with its own filter and date field. PSPTechHub's work added scheduled caching of SharePoint data, so local plant lists can appear alongside line performance and audit results without reading the source list every time a dashboard opens.

PSPTechHub's work used scheduled caching for slow sources, including SharePoint lists and audit data. Dashboards read copies held in ThingWorx instead of waiting for each source system to respond. Each cache records its last run, row count and errors for support; this case study does not report a measured loading-time improvement.

The connector uses REST APIs to check and start the Databricks cluster, run queries and refresh its access token. The audit connector then reads safety and quality audit results and caches them by site. This project used that connection without extra extensions and closed each query session after use.

Yes. Within PlantApp's configured dashboard structure, site users create main screens, dashboards and sections, then select ready-made KPI, gauge, image, manual-input, SharePoint or audit tiles. They choose the lines, time ranges and filters relevant to their plant without writing new code for those screens.

In this project, line performance and defect data refresh every 15 minutes per line. Audit data is cached every 30 minutes for the last 31 days; both are configurable. SharePoint lists are cached on a separate schedule. These are scheduled updates, not continuous real-time streaming.

This PlantApp dashboard displays downtime, alarms, cleaning and checks, quality and line KPIs, plus found, critical and open defects. SharePoint list data and safety and quality audit results appear alongside those measures. Each site's tiles select the relevant lines, time ranges and filters.

The app is deployed by tag to the new environment, and the site name is set on the configuration screen. Connections are switched on, then the site configures its own screens, sections and tiles. PSPTechHub's work brought site settings and data refresh controls into one configuration screen rather than requiring users to manage them inside ThingWorx.

Need One Dashboard for Your Plant?

PSPTechHub builds ThingWorx apps that build ThingWorx dashboards that bring line, SharePoint and Databricks data together and load fast.

Transforming manufacturing with smart tools, designed for real results.

@Copyright 2026, All rights reserved by @PSPTECH HUB Pvt Ltd.

@Copyright 2026, All rights reserved by @PSPTECH HUB Pvt Ltd.