The IT/OT Insider
Toggle menu

We put Litmus on our shop floor. Then opened a second site, and a third.

Five videos, one bakery empire, no cuts. Litmus’s Josh Eastburn and Dave McMorran explain where Litmus fits, the five things that actually determine whether you scale, then build it live — connectivity, context, and governance — across three sites of Sweet Harmony Treats.

Sweet Harmony Treats

Sweet Harmony Treats is the bakery we use to make these things concrete in our Academy and now also in our IT/OT Builds. Multiple sites at wildly different levels of maturity, PLCs and HMIs from a dozen brands, the legacy SCADA project bolted on wherever a plant manager needed it. No single team owns “data.” Nobody agrees who should.

By the time we started filming, Sweet Harmony Treats already had two sites running on Litmus — Riverside and Millbrook. The real test for a platform like this was never going to be the first one. It’s what happens when a third site opens, and whether you’re starting from zero again, or standing on what you already built.

That’s the problem we asked Litmus to solve in front of us.

One problem, solved once

Litmus Edge lives at each site and handles the unglamorous stuff: protocol conversion, tag browsing, naming, building a local data model. Litmus Edge Manager sits above every site and turns whatever you built at site one into a template you can push out to site two, twenty, or two hundred — device configuration, data models, asset hierarchies, all of it. Litmus Unify is their MQTT-based unified namespace option for teams standardising on that model, and the newer Litmus Data Catalog does for OT metadata what an IT data catalog does for everything else: makes it searchable, and tells you what breaks downstream before you touch a tag.

Where this sits on our Capability Map

Here’s where Litmus lands on our Industrial Data Platform Capability Map.

  • 1 – Connectivity is Litmus Edge’s device connectivity — PLCs, OPC UA, MQTT, and beyond (scales, CNC machines). It’s covered in the Real Connectivity tutorial.
  • 2 – Transform, Contextualize & Structure and 5 – Edge Compute come together in Litmus’s low-code analytics canvas, where calculations and reusable data models run locally on the edge device. Shown in the Analytics tutorial.
  • 4 – Data Broker is optionally offered through Litmus Unify, and while storage is not a key part of the Litmus platform, they do offer a temporary store to buffer data for a couple of days as well.
  • 7 – Data Sharing is also a really important part of their offering, but we didn't touch upon this yet in the videos

More about our Data Platform Capability Map

Three tutorials, follow along

These are hands-on, and the videos are uncut by design. Feel free to follow us along on your own instance.

Install

Open in YouTube →

Deploying Litmus Edge as a container from scratch, connecting it to Litmus Edge Manager, and opening up a brand-new third site for our bakery empire.

Connect

Open in YouTube →

Wiring up an OPC UA server and a Rockwell PLC — and why renaming every tag on the way in is the one step that makes everything downstream scalable.

Analytics

Open in YouTube →

Building calculations and reusable data models at the edge, deploying that model to the new site in minutes, then publishing it all up to a governed Litmus Unify namespace.

What you’d need to follow along: Litmus Edge deploys as a Docker container with a free two-hour trial, no account required to start (quick-start guide at docs.litmus.io). Everything shown is something you can do on your own machine today.

← Back to all IT/OT Builds