Lynxby DOMINION
← Back to components

SETTINGS & SECURITY Who sees what, and who answers for it.

Giving everyone access to everything is the fastest way to make nobody trust the data.

Settings & Security, included in the Lynx core, decides who gets in and what they see: you create each account, choose which plants and lines they see and schedule the reports they receive. All from a single panel, on a platform aligned with ENS, IEC 62443 and ISO/IEC 27001, with an external pentest passed.

Request a demo →

Configure the platform →

lynxplatform.cloud/gestion/usuarios
Management · Users
Settings & Security: user list with the status of each account and the permission profile assigned to it.

WHO GETS IN, AND TO WHAT Each person sees their plant and their line. Nothing else.

You create the user, decide which plants and lines they see, and schedule the reports they receive. Each person manages their profile, their language and their time zone. The panel keeps the count of active, disabled and total.

lynxplatform.cloud/gestion/usuarios/detalle
User detail: account data, profile, language and time zone, and permissions per plant and line.
  • Accounts and states

    Creation, search and enabling or disabling of users, with control of active, disabled and total.

  • Asset permissions

    Grant access by plant and line, plus in-app permissions, user by user.

  • Scheduled reports

    Scheduling of recurring reports, with defined recipients and frequency.

External security audit Security pentest passed

Lynx has undergone a penetration test (pentesting) carried out by an independent security firm, validating the platform's robustness against real-world threats.

Audit passed

WHEN THE AUDIT COMES Auditable data, and it need not leave the plant

Lynx integrates your plant's protocols and delivers data you can audit against the standards that already apply to you. And that data need not leave the plant: besides managed hosting, Lynx runs on your own infrastructure.

Energy management & M&V

  • ISO 50001:2018Energy Management System (EnMS).
  • ISO 50006:2014EnPI definition and energy baseline.
  • ISO 50015 · IPMVPMeasurement & Verification of savings.

Emissions & reporting

  • GHG ProtocolThe reference standard to measure, manage and report greenhouse-gas emissions.
  • ISO 14001:2015Requirements for an environmental management system.
  • CSRD · ESRS E1-readyProvides auditable data to corporate sustainability platforms.

Industrial interoperability

  • Modbus TCP/RTUFieldbus protocol for PLCs and equipment.
  • OPC UA · IEC 62541Open industrial interoperability standard.
  • MQTT / Sparkplug BLightweight messaging for IIoT telemetry.
  • EtherNet/IP · CIPIndustrial protocol over Ethernet, from the CIP standard.
  • EtherCATDeterministic Ethernet for control and drives.
  • CANopenCAN bus for machinery, industrial vehicles and drives.

Power, utilities and buildings

  • IEC 61850 · MMSCommunication standard for substations and electrical equipment.
  • IEC 60870-5-101/104Telecontrol for power grids and utilities.
  • DNP3Telecontrol and data acquisition for utilities.
  • SunSpecStandardized register map for photovoltaic inverters.
  • BACnet/IP · MS/TPBuilding automation and HVAC standard.
  • KNX · KNXnet/IPStandard for building installations and control.
  • M-Bus · Wireless M-BusEN 13757, meter reading for water, gas and heat.
  • DLMS/COSEM · IEC 62056Standardized reading of electricity meters.

Native PLC protocols

  • S7 · ISO-TCPNative protocol of Siemens SIMATIC S7 PLCs. On S7-1200 and S7-1500 with optimized data blocks, the block optimization has to be turned off or the data read through the PLC's own OPC UA server.
  • Logix · CIPTag-level access to Rockwell ControlLogix and CompactLogix PLCs, over CIP.
  • FINSNative protocol of Omron PLCs.

OT / IT cybersecurity

  • ENSSpain's National Security Framework.
  • IEC 62443Security for industrial automation and control systems.
  • ISO/IEC 27001Information security management.

Trademarks and product names cited belong to their respective owners and are used solely to identify the equipment Lynx interoperates with. They imply no agreement, certification or joint programme with any of them.

Lynx by Dominion

Put a name on every permission

While everyone sees everything, nobody answers for anything. Bring your plant org chart and we leave with the roles, the per-plant and per-line permissions and the reports mapped out, plus the detail of how the platform is secured end to end.

Request a demo →

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

← Back to components