Lynxby DOMINION

TURNKEY The platform is half the job.

The other half is getting to the plant, seeing what it measures and what it does not, fitting what is missing and leaving it running. Lynx is built by the Digital Transformation Unit at DOMINION. It is also installed by them: field work and installer management included.

Tell us about the project →See what changed in each sector

WHAT THE BUDGET LEAVES OUT The platform is not the part that gets stuck.

  • The budget signs off the software. The cable, the cabinet and the meter turn up in the second meeting.
  • The team that was going to use the data ends up coordinating installers.
  • Every supplier signs off its own part. Nobody answers for the data that never arrives.
  • And the question that decides the whole project — which equipment already talks and which has to be touched — is still unanswered.

None of the four is fixed by picking better software. They are fixed by going to the plant before proposing anything. That is the first of the five steps.

FROM THE VISIT TO THE FIRST SCREEN Five steps. You take none of them alone.

The scope of every project is agreed in writing, but the route is always the same: it starts by looking at the plant and ends with the platform showing data from that plant.

  • Somebody looks before anyone proposes anythingWhat equipment is there, which of it already talks, what gets measured today and what ought to be. Everything else comes out of that.
  • You come out knowing what talks and what is muteAn inventory of sources and protocols. What each device speaks, what comes in through a driver and what needs a gateway. What can be pulled from SCADA, and which meters and inverters are in place. And which systems — ERP, MES, CMMS — have to keep working exactly as they do.
  • What has to be installed, said before you signWhich modules switch on, in what order and on which deployment: managed cloud or on-premise. And what has to be installed to get there, which is the part that usually only shows up after signing.
  • One point of contact, not threeSensors, meters, communications and cabinets. DOMINION fits them and coordinates the installers: if something does not turn up, you know who to ask.
  • Handed over when the screen shows your plantPlants and lines set up, permissions by scope, scheduled reports and training for the team that will use it. It is handed over when the screen shows data from your plant, not when the server boots.

Does the data have to leave the plant? Only if you want it to.

LYNX Cloud EditionManaged cloud

Managed hosting with LYNX Cloud Edition: no servers, updates or scaling on your side.

On-premise

When data must stay inside the plant, Lynx also runs on your own infrastructure.

LIMITS What is not included.

  • The visit is not a project. It tells you what it would take; the scope is agreed afterwards and in writing, case by case.
  • Lynx does not create manufacturing orders and does not replace your ERP, MES or CMMS: it reads from them and gives the plant data back.
  • Satellite telemetry needs your own Iridium account and contract, with the cost per message on your side.

We would rather say it on this page than in the third meeting.

EVIDENCE The installations this site shows were delivered by DOMINION.

A steel processing group with 17 plants in several countries, since 2016. A coil warehouse with 2,023 coils located on the map. A hydroelectric operation with more than 225 stations transmitting by satellite. They are in the sectors section, with their figures and without names, and DOMINION delivered them, field work included. They are not third-party integrations on top of a platform we sell.

If any of that looks like your plant, the next step is a short one: show it to us.

Tell us about the project →

See what changed in each sector →

See the partner programme →

What gets asked before anyone is let into the plant.

What does it cost?
The software side is on the pricing page and you can read it today. The field side is not: it comes out of the scope, and the scope comes out of seeing the plant. That is why the first step is a visit and not a quote.
How long does it take?
It depends on how many sources have to be connected and which modules come in. We are not going to give you a number we do not know yet.
Does asking for the visit commit me to anything?
No. Ticking it commits you to nothing: it just means the first reply comes with the visit in mind. The scope of any project is agreed afterwards and in writing.
Do I have to know which modules I need?
No. That is what the visit is for. Knowing what is on the plant floor today and what you want to solve is enough to start.
Do we have to change the PLCs or sensors we already have?
No. The drivers speak the plant protocols listed under Drivers, and SCADA keeps doing its job. The audit says what already talks and what is still missing: what already talks gets used.
What if we would rather our own engineering firm fitted it?
That works. The same platform is licensed through the partner programme and rolled out by whoever you choose. What changes is who fits it, not what gets fitted.
Lynx by Dominion

Show us the plant. We will tell you what it needs.

Tell us what you have today, how many sites there are and what you want to solve. If someone needs to come and look, we come.

Tell us about the project →

Or write to us directly at support.dt@dominion-global.com