Every Device, One Platform

From Modbus to M-Bus, from MQTT to BACnet — Argus EMS speaks every industrial protocol used in the field.

Supported Communication Protocols

Modbus TCP

Active

The most widely used industrial protocol. The vast majority of energy analyzers, UPS units, generators and inverters support it. Poll interval 15 minutes (configurable).

Industrial energy analyzer, UPS and generator support · ready register templates

Modbus RTU

Active

Runs over an RS-485 serial line. Common for legacy meters and control panels. Integration via a USB-RS485 converter or an RS485-Ethernet gateway.

RS-485 · Baud: 9600/19200 · Parity: None/Even · Gateway-based connection

M-Bus TCP

Active

The standard protocol for water, heat and natural gas meters. Used in meters integrated with infrastructures such as İSKİ, İGDAŞ and similar utilities.

M-Bus TCP gateway support for water, heat and natural gas meters

MQTT / TLS

Active

The transport layer between the field agent and the central platform. Secure delivery with QoS 1, persistent session and TLS 1.3 encryption.

Secure MQTT connection with TLS 1.3 encryption

BACnet/IP

Coming Soon

A protocol widely used in building automation systems (BAS). Air handling units, chillers, VAV systems and DALI lighting controllers.

Building automation (BACnet/IP) support (coming soon)

OPC-UA

Coming Soon

For high-level integration with SCADA and MES systems. A bridge to machine manufacturer OEM data and ERP systems.

OPC-UA for SCADA/MES upstream integration (coming soon)
✓ ISO 50001 Compliant Reporting ✓ TLS 1.3 Encrypted MQTT ✓ Brand-Independent Integration ✓ Zero Data Loss Architecture

Upstream System Integrations

Combine your energy data with your enterprise systems. Automate cost centers, maintenance work orders and budget flows.

SAP PM/PM

Fault notifications and maintenance work orders — SAP RFC or REST bridge

Logo Tiger / Go

Türkiye-based ERP. Energy cost center and accounting integration

Microsoft Dynamics

Power BI data flow and Azure IoT Hub connection

Generic REST

JSON webhook for any system — configurable POST payload

Data Source Integrations

Combine field device measurements with distributor and enterprise data sources. All portal connections run with your official account, within the scope you authorise.

BEDAŞ OSOS

Active

The distribution company's official meter indexes flow directly into the platform. Your main-meter consumption is checked against field measurements; invoice reconciliation relies on the distributor's own data, not estimates.

Distributor meter index · invoice reconciliation · your official account, authorised scope

İGDAŞ AVE

Active

Your natural gas consumption is retrieved daily from the distributor's main-meter measurement on the AVE portal. Processed with the K coefficient and calorific value, your m³ and kWh costs are calculated correctly.

Daily gas measurement · K coefficient + calorific value · your official account, authorised scope

EPİAŞ Transparency

Active

The price components of free-consumer electricity cost (PTF, YEKDEM) are fetched automatically from the EPİAŞ Transparency Platform. Invoice verification and cost projection run on current market data.

PTF + YEKDEM price components · invoice verification · open data platform

HIS (HBYS)

Active

In hospital projects, occupancy data is read from the hospital information system and correlated with energy consumption. Occupancy becomes an input to budget forecasting: per-bed consumption and occupancy-aware targets.

Occupancy data · forecasting input · read within your authorised scope

Integration Questions

Send us your device's technical documentation and register map. We can develop a driver and add it to the system within 2–4 weeks. First review the current devices page: the verified device templates are listed there.
No. The Argus architecture is field agent based; device reading, queue management and offline buffering all run through the field agent. This structure guarantees zero data loss.
Yes. REST API and MQTT feed access are available with enterprise licenses. For OpenAPI documentation, write to info@nevacontrol.com.

Shall we add your device?

Share the register map and protocol document, and the driver will be ready within 2–4 weeks.

Request Integration →

See Argus at Your Facility

Explore the system with your own data in a demo session.