Lynx is the industrial data platform of DOMINION's Digital Transformation Unit. It collects telemetry from PLCs, SCADA, inverters and meters over the core protocols —Modbus TCP/RTU, OPC UA · IEC 62541, MQTT / Sparkplug B, EtherNet/IP, BACnet, IEC 61850, DNP3 and the native protocols of Siemens, Rockwell and Omron PLCs, among others—, stores it in a single repository and exploits it with the core components, always included, and the modules each plant switches on. It runs on LYNX Cloud Edition, the managed hosting, or on-premise on your own infrastructure.

Does it replace our SCADA?

No. It uses it as a source. SCADA keeps doing its job and Lynx reads from it over OPC UA · IEC 62541, alongside what comes in from PLCs, meters and inverters.

Do we have to change our PLCs or sensors?

No. The drivers speak the plant protocols —Modbus TCP/RTU, OPC UA · IEC 62541, MQTT / Sparkplug B, EtherNet/IP, BACnet, IEC 61850, DNP3 and the native protocols of Siemens, Rockwell and Omron PLCs, among others—. A new device connects through its driver, not through a development project. And if it speaks something outside that list, it comes in through a gateway or gets integrated — and you are told before you sign.

We already have Power BI. Is one of the two redundant?

No. Lynx prepares and centralizes the industrial data and serves it to third-party software over REST and MQTT services. It does not compete with the corporate layer: it feeds it.

Does it integrate with the ERP or the MES?

Yes, and both ways. Production orders reads the manufacturing orders from the ERP, and plant data goes back to the ERP, MES, CMMS and BI over REST services and MQTT subscription, with the same permissions that apply in the platform.

Do we have to buy all seven modules?

No — and switching them all on at once is usually the worst way to start. The core is always there and modules come in one at a time. The criterion for the first one: the question that today gets answered by hand, and answered late. If that question does not exist yet, you do not need a module.

What is the difference between a component and a module?

A component is part of the core: it is always included and cannot be switched on or off. They are Settings & Security, Communication drivers, Communications, Real time, Analytics, Alarms and Multi-device. A module is switched on per plant when it is needed: Photovoltaic, Welding control, WMS · Warehouse management, Production orders, EMS · Energy management, Inventory · Tools & jobs and Satellite telemetry · Iridium. Each module works on its own on top of the same core.

Does the data have to leave the plant?

Only if you want it to. There is managed hosting with LYNX Cloud Edition and on-premise deployment on your own infrastructure.

What if this ends up as another pilot nobody looks at?

That happens when you start from the screen: a new chart on top of data that is still scattered. Here the order is the other way round — collect, store, transform, protect — and you start with one module and a question someone on the plant floor already needs answered. If nobody is going to open that screen on Monday, do not build it.

How much does it cost?

The software has a published tariff: core — with every driver inside — modules and volume bands. You can do the sum before talking to anybody. What carries no tariff is whatever depends on your installation: commissioning, field work, hosting and maintenance. That is quoted after seeing the plant.

DOMINION, if you want: site visit, audit, design, installation and commissioning, field work included. That is what Turnkey covers. Or your own integrator, through the partner programme.

How long does it take to roll out?

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 have yet: it comes from looking at your case.

How much will I save?

We do not know, and we are not going to make it up. There is no savings percentage that holds for your plant. What there is sits on each sector page: what was measured at each installation, with its unit and its period.

Where do the sector figures come from?

From installations in production and from the screens this site publishes. That is why they carry no customer, plant or country name: we publish the figure, not who it belongs to.

My plant is one line and one meter. Is this not for big groups?

It is the same platform in both cases. You start with the core and whatever module is needed, and grow when operations call for it. Size changes the number of permissions, not the product.

I run several plants. Can I compare them with each other?

Yes, and on the same platform. A steel processing group has run 17 plants in several countries on a single one since 2016. Permissions go per plant and line —each team sees its own and management sees everything— and the communications, energy and production reports come out in the same format across all of them. The plant that drifts shows up without asking anyone for a report.

Can you give me a customer reference?

We publish no customer, plant or country names on this site: that is the rule these pages are written under. If your buying committee needs a reference, we talk about it in the demo.

What gets asked before anyone says yes

What is Lynx?: Lynx is the industrial data platform of DOMINION's Digital Transformation Unit. It collects telemetry from PLCs, SCADA, inverters and meters over the core protocols —Modbus TCP/RTU, OPC UA · IEC 62541, MQTT / Sparkplug B, EtherNet/IP, BACnet, IEC 61850, DNP3 and the native protocols of Siemens, Rockwell and Omron PLCs, among others—, stores it in a single repository and exploits it with the core components, always included, and the modules each plant switches on. It runs on LYNX Cloud Edition, the managed hosting, or on-premise on your own infrastructure.
Does it replace our SCADA?: No. It uses it as a source. SCADA keeps doing its job and Lynx reads from it over OPC UA · IEC 62541, alongside what comes in from PLCs, meters and inverters.
Do we have to change our PLCs or sensors?: No. The drivers speak the plant protocols —Modbus TCP/RTU, OPC UA · IEC 62541, MQTT / Sparkplug B, EtherNet/IP, BACnet, IEC 61850, DNP3 and the native protocols of Siemens, Rockwell and Omron PLCs, among others—. A new device connects through its driver, not through a development project. And if it speaks something outside that list, it comes in through a gateway or gets integrated — and you are told before you sign.
We already have Power BI. Is one of the two redundant?: No. Lynx prepares and centralizes the industrial data and serves it to third-party software over REST and MQTT services. It does not compete with the corporate layer: it feeds it.
Does it integrate with the ERP or the MES?: Yes, and both ways. Production orders reads the manufacturing orders from the ERP, and plant data goes back to the ERP, MES, CMMS and BI over REST services and MQTT subscription, with the same permissions that apply in the platform.
Do we have to buy all seven modules?: No — and switching them all on at once is usually the worst way to start. The core is always there and modules come in one at a time. The criterion for the first one: the question that today gets answered by hand, and answered late. If that question does not exist yet, you do not need a module.
What is the difference between a component and a module?: A component is part of the core: it is always included and cannot be switched on or off. They are Settings & Security, Communication drivers, Communications, Real time, Analytics, Alarms and Multi-device. A module is switched on per plant when it is needed: Photovoltaic, Welding control, WMS · Warehouse management, Production orders, EMS · Energy management, Inventory · Tools & jobs and Satellite telemetry · Iridium. Each module works on its own on top of the same core.
Does the data have to leave the plant?: Only if you want it to. There is managed hosting with LYNX Cloud Edition and on-premise deployment on your own infrastructure.
What if this ends up as another pilot nobody looks at?: That happens when you start from the screen: a new chart on top of data that is still scattered. Here the order is the other way round — collect, store, transform, protect — and you start with one module and a question someone on the plant floor already needs answered. If nobody is going to open that screen on Monday, do not build it.
How much does it cost?: The software has a published tariff: core — with every driver inside — modules and volume bands. You can do the sum before talking to anybody. What carries no tariff is whatever depends on your installation: commissioning, field work, hosting and maintenance. That is quoted after seeing the plant.
Who installs it?: DOMINION, if you want: site visit, audit, design, installation and commissioning, field work included. That is what Turnkey covers. Or your own integrator, through the partner programme.
How long does it take to roll out?: 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 have yet: it comes from looking at your case.
How much will I save?: We do not know, and we are not going to make it up. There is no savings percentage that holds for your plant. What there is sits on each sector page: what was measured at each installation, with its unit and its period.
Where do the sector figures come from?: From installations in production and from the screens this site publishes. That is why they carry no customer, plant or country name: we publish the figure, not who it belongs to.
My plant is one line and one meter. Is this not for big groups?: It is the same platform in both cases. You start with the core and whatever module is needed, and grow when operations call for it. Size changes the number of permissions, not the product.
I run several plants. Can I compare them with each other?: Yes, and on the same platform. A steel processing group has run 17 plants in several countries on a single one since 2016. Permissions go per plant and line —each team sees its own and management sees everything— and the communications, energy and production reports come out in the same format across all of them. The plant that drifts shows up without asking anyone for a report.
Can you give me a customer reference?: We publish no customer, plant or country names on this site: that is the rule these pages are written under. If your buying committee needs a reference, we talk about it in the demo.

Put a figure on it before you book the meeting.

Tick your plants, the modules you need and how many points you measure. The configurator tells you what you pay in the first year and what you pay from the second, on published rates and with no form in the way. If you then want to see your own measurements on screen, you ask for the demo from there, with your selection already in it.

Configure your platform →

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