Suomeksi Contact
For batch chemical plants

Batch history and plant know-how in one place.

Seula compares each batch with the reactor's own usual batch. Known problems and what was done about them are written down, so when something similar comes up again, the earlier case is there to look at.

Contact us What it does
Seula's batch page on the demo plant: 155 batches on reactor R-201B, 21 of them unusual, standing out above the usual 6 h 10 min in the duration chart.
What it does

Uses the data the plant already has

The historian, the batch system, the lab results and the shift log. No new sensors are needed.

01

Each batch against the usual

Each batch is compared with the reactor's usual batch, phase by phase: which phase ran long, which was skipped, which batches differ. Lab results and the plant's own rules are checked as well.

02

Earlier cases alongside

A finding is compared with the problems recorded for the plant. If one matches, it shows what to check and what was done last time. In Finnish or English.

03

Questions about a batch

You can ask how a batch differed from the good ones. The assistant looks at the data, the notes, the lab results and the procedures, and shows where each answer comes from.

04

Notes and experience kept

Shift logs, work orders and manuals can be imported as they are. Engineers mark whether a suggestion was right, so the record gets better over time.

The product

What it looks like

The pictures are from Lumiranta, a fictional demo plant.

Seula's process knowledge on the demo plant: failure modes with their track record, one open with its description, its symptoms written as formulas over tags, and what to check.
Process knowledge. Failure modes with their symptoms, checks and history.
Stacked trends of K-401 vibration, discharge pressure, recycle valve demand and position during a surge.
Behind a finding. The trends and notes it is based on.
Seula's findings inbox on the demo plant: a vibration finding on air compressor K-401 open, with a suggested response naming the likely failure mode, the symptoms checked against the data, what to check and what to do.
Suggested response. What to check, and what was done last time.
BatchesFindingsProcess knowledgeLabRulesUnit comparisonDocumentsAssistantInvestigations
Getting started

Seula is new

We are looking for one or two batch plants to develop it with. Starting doesn't need a connection to the plant: the data can be sent as files.

  1. First

    A conversation

    We show the demo and hear what your process and data are like. If it doesn't look useful, that is fine to say.

  2. Then

    Data as files

    A year of historian export, the tag list and the batch log, plus notes and lab results if you have them. An NDA is signed first. The data goes on a separate server in Helsinki.

  3. Together

    Going through it

    We look at the findings with your engineer and drop what you already knew.

  4. After

    Feedback

    What was useful and what wasn't. That decides what we build next.

A separate serverOne per plant, in Hetzner's data centre in Helsinki
Files to start withNo connection to the plant network needed
Audit logEvery change and upload is recorded
Your dataExported or deleted on request
Contact

Get in touch

If you run a batch process and this sounds interesting, or you would just like to see the demo, send a message.

Riku Brandt riku@seula.io Or click through the demo plant in your browser