IPTellogo-byline-2020-dark-v2-pnd-optimised-500 (1)

Splunk Manufacturing Case Study

Apr 3, 2026

Manufacturing has some very key things that need to be measured and predictive analysis of data is important. The key thing: do not stop the production line! If we can use data to help us make the site efficient and predict any issues with the network that might stop operations, we can provide a major cost saving to the business. Let's take a look!

Splunk Manufacturing Case Study

Splunk is a data analysis engine, used to ingest data from a wide variety of inputs (there are >2000 connectors and counting, so you really can pull data from a huge variety of sources).
 
Once that data is ingested into Splunk, it allows us to do a couple of things:
  • Produce dashboards that correlate data, and
  • Search the data for useful insights and information

In this blog, we'll work through the manufacturing case study, looking at the users and the case studies, before moving onto some sample renders of dashboards.

ASSOCIATED BLOGS:


Splunk in Manufacturing: End Users

Splunk in manufacturing is about helping ensure operations don't unexpectedly halt.


That's not all though - data helps a manufacturer to really get to grips with how efficiently their processes work - all the while keeping an eye on the equipment running that process to ensure there are no issues.
 
There's a range of stakeholders in the manufacturing space:
 
Operations Manager:
The operations manager wants to know if any of the equipment running the production line has issues. This might include a range of black box / PLC type equipment that we can't get information from - but it does also include equipment that we can.
 
With the wide variety of equipment to look after, the Operations Manager relies on analysis of that data to spot issues early.
 
Splunk (Instagram Post)ICT Manager
The ICT manager needs to look after the network that supports the manufacturing process - that includes a corporate ICT network and often a SCADA network - these can be two very different things.

A SCADA network has to have the highest of uptimes and can sometimes lack visibility - making it very hard to fault find. S
 
Production Manager
The production manager wants it all to come together and ensure that the end product is manufactured and shipped out - on schedule.  The data they need is right across the whole process.

 
With the end users in mind, let's take a look at how what their use cases might be, in the next section below.
 

ASSOCIATED BLOGS:


Splunk Use Cases in 

The use cases in manufacturing are pretty unique to the space: heavy machinery, processes that require close monitoring and the ability to orchestrate across a factory floor are all requirements. 

The most common use cases for Splunk in manufacturing are: 

 1. OT Monitoring & Predictive Maintenance

  • Monitors machine, PLC, SCADA, and sensor data
  • Detects abnormal behavior and early failure indicators
  • Reduces unplanned downtime and maintenance costs

Outcome: Improved asset uptime and OEE

2. Manufacturing Operations Visibility

  • Provide real‑time dashboards across lines and plant
  • Track KPIs like throughput, downtime, yield, and scrap
  • Correlate IT, OT, MES, and ERP data

 Outcome : Faster decisions and root‑cause analysis

Splunk Healthcare Case Study (Instagram Post)

 

3. OT & ICT Monitoring

  • Detect ICT failures that impact the operations flow
  • Correlates IT and OT events
  • Support incident response - conduct network fault finding more quickly

 Outcome Reduced time to return to service 

 
 

4. Quality & Root Cause Analysis

  • Links defects to machine conditions, batches, and processes
  • Identifies patterns driving scrap and rework

 Outcome : Higher product quality and lower waste

The use cases in manufacturing tend to be in two parts: ensure the operations don't stop - and see if we can spot anywhere to be more efficient.

In the next section we'll start to look at the interesting bit: how these use cases are displayed on a dashboard.

 ASSOCIATED BLOGS:


Splunk in Manufacturing: End-End View

The thing everyone wants is simple: understand what's going on - and when there's an issue have enough up to date information to see where the problem lies and quickly resolve it.

There's a couple of options in Splunk for how we show dashboards. In the IT Service Intelligence (ITSI) module, we have two options:

  • Dashboard Studio: Excellent place to produce a wide range of dashboards for different users - that look good
  • Glass Tables: These are a rendered image that might be more of an 'exec' level dashboard

How Splunk Helps Businesses Discover Connected Devices (Instagram Post)We'll explore both the dashboard options in this blog, however typically we will default to using the Dashboard Studio.

For our end-end view though, we'll explore that exec level dashboard. We can't show an actual customer dashboard, so in this blog will illustrate the setup with some AI renders that look like the real thing.

 

The image below is an ITSI Glass Table view and in this stylised view, we can see all the important end-end information for the plant. This might be the sort of view that the CEO would like at the front desk or in the board room.

 

In this Glass Table, we're showing various parameters important to the production, which is a culmination of a range of ingested data - all displayed in one place. That ability to take that range of data and correlate it really is the power that Splunk brings - you'll get end-end visibility in a way you can't otherwise:

Manufacturing Glass Table

 Sample Render of Splunk Glass Table View 
 
The Glass Table is a useful high level view - but what about those other end users we discussed above? In the section below we'll have a quick run through the use cases we're trying to solve.

ASSOCIATED BLOGS:


Splunk Dashboard Studio

In the sections above, we mentioned there were two ways to show the data - Glass Tables and Dashboard Studio.

For most users, we want to produce the data they need in a quickly understandable way - and dashboard studio is perfect for producing these.

In the image below, we can see a sample dashboard:

  • Alert Types: We can clearly see the quantity and type of alerts and how they're impacting the network
  • Types of Equipment: Manufacturing uses a range - from standard networking equipment (albeit IOT versions) through to PLCs, sensors and cameras
  • Major issues and Parameters: This is just a sample render below, but we would typically want the key metrics and KPIs shown on these dashboards

Dashboard Studio 1
  Sample Render of a Splunk Dashboard Studio dashboard  

In our final sample render, we bring in the financial side: we can put rules on how much an outage costs, which really helps focus the mind of all operations staff.

This is also useful to senior management - if there are investment decisions to be made to improve reliability, it can easily be seen how much outages are costing and that can be used in a business case to drive investment:

Dashboard Studio 2

   Sample Render of a Splunk Dashboard Studio dashboard   

Once data is ingested, the dashboards can really be built according to those users and use cases - very specific for manufacturing.

ASSOCIATED BLOGS:


Splunk Manufacturing Case Study: Summary

This case study shows how manufacturers use Splunk to unify IT and operational data into a single, real‑time view of plant health.
 
Correlation of network, devices and operational insights allows the operations and ICT teams can detect issues earlier, resolve problems faster, and reduce unplanned downtime.
 
The result is improved operational resilience, stronger collaboration between IT and operations, and a platform foundation for predictive maintenance and continuous improvement. Exec's typically want an overview too - and Splunk excels in being able to produce a dashboard to remove all the clutter and noise for these users.
 

If you’d like to chat over all things Splunk, or have any Splunk projects we could help you with, drop us a line at sales@iptel.com.au

ASSOCIATED BLOGS: