// Industrial systems integration

From the 4–20 mA loop to the ERP that reads it.

Most plants hire a controls integrator, an MES vendor and an IT contractor, then spend years sorting out the gaps between them. We've done all three jobs, on drillships, in breweries and dairies, and in medical device plants on three continents, so one team can see your project through every layer.

See what we do
20+years writing code for plants, rigs and production linesexperience
15sites in 7 countries, from Portales to Qidongdelivered
30kI/O points on a single rig control systemlargest system
1business day until an engineer writes backresponse
// Services01

Six kinds of work, and most projects need more than one.

An OEE rollout needs PLC changes. An MES needs its ERP interface. The ERP report needs a historian that was set up properly. We take on the whole chain instead of handing it off halfway.

click any card for details
// The Full Stack02

Why we don't stop at one layer.

Projects usually go wrong at the handoffs. The controls integrator passes the job to the MES vendor, the MES vendor passes it to IT, and each one assumes someone else owns the tag names. When the same people work across all of it, those assumptions get checked before startup instead of after.

  • The people writing the PLC code also know what the MES expects from it
  • Data gets modeled once, near the machine, and reused everywhere above it
  • Designs that live within OT constraints and still pass IT's security review
click a layer to see what we do there
// Industries03

The industries we know.

Each one is here because we've done paid project work in it. The processes differ a lot; the approach doesn't. We learn how the process runs before we change how it's controlled.

click an industry to see our experience
// About04

Why “DigitalThreads”.

A digital thread is the record that follows a product through the plant: the sensor reading, the PLC step it triggered, the lot it went into, the operator who signed for it, and the ERP transaction at the end. When a link in that chain is missing, simple questions get hard, like which units came off a bad batch.

DigitalThreads grew out of more than 20 years of building those links one layer at a time: power management code for drillships in a Chinese shipyard, SCADA and CIP for breweries and dairies, and MES rollouts for medical device plants in five countries, on cloud and on-prem Kubernetes. Having done each layer ourselves, we build every piece knowing who has to use it next.

L0 · L1Offshore controls. Power management and vessel control code for DP rigs, commissioned in the shipyard and tested at sea.
L2Breweries and dairies. Ignition, AVEVA and FactoryTalk, and the historians behind them.
L3Medical device MES. Paper to eDHR in FDA-regulated plants on two continents.
L4Kubernetes and cloud. The platform, pipelines and ERP integration underneath.

Where the work was

pick a site, or a project below
SEATTLE, WA CORVALLIS, OR ESCONDIDO, CA SALT LAKE CITY, UT PORTALES, NM COLORADO FRONT RANGE MILWAUKEE, WI ALLENDALE, MI GULF OF MEXICO EL LAGO, MEXICO QIDONG, CHINA SINGAPORE MERVUE, IRELAND TREVOUX, FRANCE PORTO, PORTUGAL

// pick a site on the map or a project above to see what we did there

// Contact05

Tell us what you're working on.

A stalled MES rollout, a PLC program nobody wants to touch, a dashboard that doesn't match the floor. Send a few lines and an engineer will reply within one business day.