Head-end system

Device communication, collection, raw records and command execution evidence.

PRODUCT OVERVIEW

Follow each reading and every execution step.

AetherHES is the head end of AetherONE for meter, concentrator and gateway communication. It owns device sessions, acquisition, command execution evidence, link telemetry and the private Raw Chronicle.

Decoded measurement events carry typed values, references and hashes to MDMS. Raw communication bytes stay in HES; execution evidence does not grant financial or field-work authority.

Who it is for

Integration and operations engineers
Communication-network and fleet operators
AMI solution architects

Concept AMI acquisition illustration: meters, concentrators, communications and head-end servers. — Concept illustration of the product responsibility. It is not a customer installation or an operational record.

Responsibilities and evaluation scope

Adapter and sessions: Approved design scopeLocal TCP adapter with newline-delimited JSON; device-bound open/closed sessions persisted in an HES-owned SQLite WAL store and resumed after restart.; Available in this editionBounded local component for evaluation; deployment conditions require project-specific acceptance.
Collection and Raw Chronicle: Approved design scopeTransactional raw frames, durable outbox, decoded measurement events and computed raw/payload hashes; separate broker spool with replay-safe delivery and persisted acknowledgement.; Available in this editionSingle-host evaluation with a bounded kW reading, not a general OBIS or load-profile model.
Read-only Fleet and Collection: Approved design scopeLoopback GET-only API with a server-side field allow-list. Explicit demo mode never substitutes for a failed live read.; Available in this editionBounded local component for evaluation; deployment conditions require project-specific acceptance.
Command Execution Queue: Approved design scopeSingle-instance request pump, idempotent consumption and session binding; separate transport ACK, device ACK and matching read-back evidence.; Available in this editionDeterministic adapter and test-mode token delivery with local evidence only; not production STS.
Operations overview and maintenance: Approved design scopeFleet dashboard, network/link quality, firmware repository, campaigns/configuration drift, events, alarms and raw-frame viewer form the intended operating picture.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.

How the work connects

The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.

HES design path from device session through private raw reference and hash, decoded event and broker to MDMS receipt. — Design workflow. The relationships shown are not a claim of running cross-product integration.

Clear responsibility across products

AetherMDMS: Receives hes.measurement.decoded.v1 references and bounded kW values. In the test-mode token flow, MDMS requests delivery and projects business completion only after matching read-back. Raw frames, private event JSON, receipt JSON and token material are excluded.
AetherGIS / AetherRevenue / AetherDispatch: GIS owns spatial truth; Revenue owns financial billing and settlement; Dispatch owns utility field work. HES supplies execution evidence and communication projections.

Utility scenarios

Trace one reading

Follow the device/session, raw reference, decoded event, outbox, broker delivery and MDMS acknowledgement without exposing the private raw record.

Separate acknowledgement from outcome

Requested → authorized → queued → dispatched → transport acknowledged → device acknowledged → read-back verified → business outcome confirmed. Device ACK alone is not final completion.

Review a communication fault

Use synthetic fleet, uplink, firmware and alarm views to review the intended operating picture; they are demonstration screens, not measured fleet performance.

Evaluation views · synthetic data

The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.

Synthetic HES Collection example with decoded-event identity and collection plans. — Evaluation interface excerpt with synthetic data. Identifiers, amounts, dates and counts are examples, not customer or performance evidence.

Synthetic HES command queue; no command or relay is operated. — Evaluation interface excerpt with synthetic data. Identifiers, amounts, dates and counts are examples, not customer or performance evidence.

Synthetic HES operations and gateway uplink overview. — Evaluation interface excerpt with synthetic data. Identifiers, amounts, dates and counts are examples, not customer or performance evidence.

Edition and evaluation conditions

Controlled single-host evaluation uses a deterministic simulated adapter. The read-only local service is not an authenticated production service.

Production DLMS, IDIS and SMGW packs, vendor certification, operator authentication/approval, high availability and live field integration are outside this edition. No throughput, latency or capacity is published; the transactional Raw Chronicle is not claimed to be tamper-proof.

The web build uses Node.js 20.19+ in the 20 line or 22.12+; the measurement service requires Node.js 24+. A command-pump evaluation needs explicitly paired broker request/status spool settings.

Document edition 2026.10 identifies the supplied documents, not a commercial release or a deployed version.

Product documents

Choose a language to download the matching document edition.

AetherHES Datasheet · English (PDF)English · PDFDocument edition 2026.10
AetherHES Catalogue · English (PDF)English · PDFDocument edition 2026.10

Discuss an evaluation ↗

EXPLORE OTHER LINES

AetherEdge™Smart Metering→

AetherLink™Communication Modules→

AetherNexus™Data Concentrators & Gateways→

AetherSol™Solar Power Electronics→