METRO POWERProduct intelligencePlan a project ↗

Electric Metering & AMI

HES + MDMS

AMI software stack

The central software of an AMI system. The head-end system (HES) collects reads and manages meters and terminals; the meter data management system (MDMS) turns those reads into billing, loss and load information.

Check if this fits my project See what must be confirmed Compare similar products
HES + MDMS, Studio view

PRODUCT DRAWING · 01/06HES + MDMSA line drawing made from the published facts, not a photograph. Confirm the exact model, ratings, dimensions and interfaces by document.

IMAGE REFERENCEPictorial drawingFor identification, not an installation. Ratings, dimensions, interfaces and compliance are confirmed from the applicable documents.

POSSIBLE USECentral meter collection, device management and utility data workflowsA starting point for discussion, not an automatic recommendation.
WHAT WE CAN CONFIRM TODAYInitial product informationUseful product information is available for early review. Final technical evidence follows requirement confirmation.
FIRST PROJECT CHECKControlling terms of reference (TOR) and meter populationIf you do not know this yet, Metro Power can help identify what is needed.
Published specifications

HES + MDMS, as published.

Figures from the current product reference.

HES + MDMS published specifications
ModelHES + MDMS
TypeAMI software stack
System familyElectric Metering & AMI
Tariffs and prepaymentTariff/prepayment support
Events and alarmsRemote control and alarms
Features
  • Collection and terminal management
  • Line-loss and load-management workflows

Evidence level: initial product information. Confirm the exact model code, option, revision and controlling TOR before using any fact in a compliance statement, offer or installation decision.

System context

The software end of the metering chain.

The head-end system talks to the field. Meter data management turns what arrives into validated reads that billing and customer service can use.

Illustrative evening scene of distribution lines and a substation above a coastal town
Illustrative scene, not a Metro Power site or installation.

Data path

  1. Smart metersMeasure, store and report reads and events.
  2. Data concentratorCollects an area where the network uses one.

  3. This product · pictorial drawing

    HES + MDMS

    Collects, validates and publishes meter data.

    HES + MDMS, pictorial drawing at full size
    A line drawing made from the published facts, not a photograph. It shows the general form of the equipment, not an exact product view.
    This productHES + MDMSCollects, validates and publishes meter data.
  4. Billing and operationsBilling, customer service, loss analysis and field work orders.
DataReal product photographDrawn: equipment Metro Power does not supplyDrawn: supplied, with no published photograph
Options and differences

Three ways reads reach the utility

The head-end must support every route the field network uses.

  • Through a data concentrator

    Meters talk over power-line carrier or radio to a concentrator for their area; one backhaul link serves many meters. Suits dense service areas.

  • Direct cellular

    Each meter carries its own cellular module and reports straight to the head-end. No field collection hardware, but a data plan per meter and signal at every service point.

  • Read on site

    An optical port read with a handheld. No network cost, and no remote reads, alarms or relay control between visits.

Application context

Where this product fits.

Typical applications for this product family. Fit still depends on the exact service, duty, operating objective and approved configuration, so treat these as starting points rather than recommendations.

  1. 01Automated billing reads
  2. 02Loss analysis
  3. 03Load profiling
  4. 04Outage and event visibility
  5. 05Remote service operations where enabled
  6. 06Phased utility modernization

Before an offer

What Metro Power confirms before HES + MDMS is offered.

Four steps, in the order they happen: the evidence that identifies the exact unit, what the public record already shows, what your project must confirm, and the controlled documents that close the loop.

01Priority meter evidence package

A credible meter decision needs more than a polished front view.

Before a meter is offered, Metro Power assembles this evidence for the exact unit, from its identity through to project release. A photograph covers only the first line.

  1. 01IDENTITY

    Front, nameplate and model identity matched to the offered unit

  2. 02FIT

    Service form, voltage, current class, wiring and installation arrangement

  3. 03INTERFACES

    Terminal, communications, relay, optical and accessory evidence as applicable

  4. 04AUTHORITY

    Controlled datasheet, drawing, certificates and principal confirmation

  5. 05PROJECT RELEASE

    TOR matrix, approved configuration, test evidence and offer revision aligned

02Professional documentation

One product identity. Five controlled evidence gates.

This schedule shows what the public record supports and what Metro Power must still match before the product becomes a technical or commercial commitment.

ControlCurrent public recordProject release requirementStatus
IdentityHES + MDMS · AMI software stackExact model code, production revision and option scheduleInitial product information
ApplicationThe central software of an AMI system. The head-end system (HES) collects reads and manages meters and terminals; the meter data management system (MDMS) turns those reads into billing, loss and load information.Approved service, duty, site and operating useApplication review
Technical factsCollection and terminal management · Remote control and alarms · Tariff/prepayment support · Line-loss and load-management workflowsControlled datasheet and requirement-by-requirement compliance matrixConfiguration check
Information to prepareControlling terms of reference (TOR) and meter population · Service type, voltage, frequency, form and class · Pilot geography and communications study · Billing and customer information system (CIS) integration requirements · Cybersecurity and data rules · Success measures and rollout gateDrawings, terminals, communications, accessories and system interfacesEvidence required
Approval and supplyNot shown on this pageCurrent certificates, test records, principal confirmation, availability and deliveryRelease before offer

03Configuration gate

What must be confirmed before an offer.

Exact form, class, voltage, current, reference frequency, relay, protocol, communications, certification and firmware are confirmed in a project compliance matrix.

Check if this fits my project Understand the complete system architecture
  1. 01Controlling terms of reference (TOR) and meter population
  2. 02Service type, voltage, frequency, form and class
  3. 03Pilot geography and communications study
  4. 04Billing and customer information system (CIS) integration requirements
  5. 05Cybersecurity and data rules
  6. 06Success measures and rollout gate

04Controlled document request

Request a controlled offer.

Need the current datasheet or compliance evidence? Metro Power will match the document revision, model and configuration to your requirement before release. Tell us the decision, TOR or application the document must support.

Send a request