Yes. Start with the Historian on one asset, and add the rest when a problem calls for them.

Data historian software for manufacturing

Q: Is the Singularity a data historian?

The Historian Module is one: it takes readings from your equipment and keeps them as a time series by asset. It’s one Module of the platform.

Q: Do we have to replace the historian we have?

No. Your control system keeps its own, and this one holds the record the rest of the platform reads from, taken from the same equipment.

Q: How does the data get in?

Over MQTT, on a tag path agreed for each machine type, set up with your team.

Q: Does it analyse the data?

No. The Historian keeps the readings, and the OEE Engine reads the series and works out the numbers.

Some of the people we've built with

Count by hour, Press 2 148 07:00 152 08:00 61 09:00 150 10:00

Your SCADA shows the number right now. What it was at 2 a.m. last Tuesday means a call to someone with the right login.

Every reading, kept with its time and asset.

Old way

the history sits in the control system, and getting it out is a project.

New way

readings are written to a time-series store the moment they arrive, and you ask for any window at the granularity you choose.

Availability, downtime and counts come out of the same record, for any asset and any period.

The Modules that read from the Historian

How a reading becomes a record everything reads

Each Module does one job, in this order.

1 It connects

Line PLC
SCADA

2 What runs, and what it does

HistorianWrites each reading to a time-series store the moment it arrives, filed by time and asset.
Asset RegistryHolds the site, area, line and machine every reading belongs to.
OEE EngineDerives availability, performance and quality from the history.

3 What you get

Press 2, the window you picked In count 1,204 Out count 1,192 Rejects 12

In customer plants, downtime fell 86% and shorts went from 50 a month to 12.

Real plants, real numbers, first in manufacturing.

less downtimeacross seven production facilities 86%
customer shorts a monthwithin six months 50 to 12
longer planning horizonin a customer deployment 50%
facilities on one installationrun by one customer 19

Where these numbers come from

These numbers come from customer deployments, first in manufacturing. We don’t name customers without asking them first. If you want to talk to a customer, ask us and we’ll ask them.

Press 2, last shift, 5 minute series
Reject count, last shift 12

Ask for any window of time

The Historian keeps the readings. The OEE Engine reads the series and works out the numbers. Every asset sends at least its counts and its state. mode40 was started by people who ran plants before they wrote any software.

Time-range queries at the granularity you choose
Downtime and availability history for each asset
In, out and reject counts, as a total or a series
Asset state history: running, idle, stopped, faulted
Tags arrive over MQTT on a path agreed for each machine type
A time-series database, kept separate from your order and quality records

FAQ

Is the Singularity a data historian?

Do we have to replace the historian we have?

How does the data get in?

Does it analyse the data?

Can we start small?

A data historian that keeps every reading with its time and asset.

Every reading, kept with its time and asset.

The Modules that read from the Historian

How a reading becomes a record everything reads

In customer plants, downtime fell 86% and shorts went from 50 a month to 12.

Ask for any window of time

FAQ

Bring one asset and the question your SCADA can't answer.

Connect

Social

A data historian that keeps every reading with its time and asset.

Every reading, kept with its time and asset.

The Modules that read from the Historian

How a reading becomes a record everything reads

In customer plants, downtime fell 86% and shorts went from 50 a month to 12.

Ask for any window of time

Related use cases and systems

FAQ

Bring one asset and the question your SCADA can't answer.