Electric Metering & AMI
TD16
Advanced data concentrator
Collection terminal for the low-voltage network. It gathers meter data over HPLC or G3-PLC with radio, sends it to the head-end over 4G and runs its applications in separate containers.
PRODUCT DRAWING · 01/06TD16A 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.
TD16, as published.
Figures from the current product reference.
| Model | TD16 |
|---|---|
| Type | Advanced data concentrator |
| System family | Electric Metering & AMI |
| Communications |
|
| Software | Containerized application structure |
| Features | Remote collection use case |
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.
Where a data concentrator sits in the reading chain.
A concentrator gathers reads and events from the meters of one area and passes them to the head-end system. Without it, each meter needs its own link to the utility.

Data path
- Single-phase metersResidential services on the same area.

- Three-phase metersCommercial and larger services.

- This productTD16Collects and forwards reads, events and commands for its area.
- Head-end and MDMSThe head-end gathers reads; meter data management validates them for billing.
Where it is installed
- Distribution transformerA concentrator usually serves the meters fed from one transformer area.

- From the TD16Powered from the low-voltage side it reads.
Three ways reads reach the utility
The network design decides whether a concentrator is needed at all.
- This productThrough 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.
- 01Automated billing reads
- 02Loss analysis
- 03Load profiling
- 04Outage and event visibility
- 05Remote service operations where enabled
- 06Phased utility modernization
Before an offer
What Metro Power confirms before TD16 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.
- 01IDENTITY
Front, nameplate and model identity matched to the offered unit
- 02FIT
Service form, voltage, current class, wiring and installation arrangement
- 03INTERFACES
Terminal, communications, relay, optical and accessory evidence as applicable
- 04AUTHORITY
Controlled datasheet, drawing, certificates and principal confirmation
- 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.
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.
- 01Controlling terms of reference (TOR) and meter population
- 02Service type, voltage, frequency, form and class
- 03Pilot geography and communications study
- 04Billing and customer information system (CIS) integration requirements
- 05Cybersecurity and data rules
- 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.
