EPSILONOperations Intelligence

Resources

Documents & downloads

Everything you need to evaluate EPSILON — no form required.

EPSILON PIMS executive summary

The platform on three pages — what it is, the six modules, and the architecture that ties them together.

PDF · 3 pages · 2 MB

Download

EPSILON Data Historian white paper

The digital-twin approach, the on-premise / cloud architecture, and where the value comes from.

PDF · White paper · 15 MB

Download

Read online

Practical use cases

FAQ

Common questions

What data sources can EPSILON connect to?

Native drivers cover DCS, SCADA, PLC and IoT protocols including OPC UA/DA, MQTT Sparkplug B, SQL and CSV, plus manual import. Collection happens local to the source, with store-and-forward buffering so an outage never loses data.

Where does my data live?

Data is collected and stored on-premise first — on the data ingestion server and immutable database inside your network — then synchronised through your firewall to the EPSILON AI Cloud for analysis, reporting and remote access.

Do I need to write code to use NexusTM or SimTwinTM?

No. NexusTM formulas are composed in a text or visual editor with built-in functions, and SimTwinTM models can be imported from DWSIM flowsheets, Excel workbooks or pasted equations. Inputs are bound to live tags with a searchable picker.

How is the simulation kept honest?

SimTwinTM reconciles its results against real-time historian data continuously, so the model fit is always known and reported. What-if studies therefore run against today's plant conditions rather than a design case.

Can it scale across several plants?

Yes. Each site collects locally and synchronises to the same cloud, so multi-site organisations get one asset model, one login and one set of dashboards across every plant.

Is EPSILON a one-off licence or a subscription?

EPSILON is evergreen subscription software: you are always on the latest release, with no upgrade projects.

Next step

Let's build your Operational Intelligence together.

See EPSILON running on your own process data — one historian, six modules, every stakeholder.