Home / Solutions / Distribution Topology and Digital Twin Display

Distribution Topology and Digital Twin Display

A distribution topology display rests on confirmed engineering documents, device codes and point mapping, not on putting up a video wall. Once the platform links cabinets, circuits, devices and live status, anomalies can be located on the topology. The capability can be presented as a lightweight digital twin or an operating topology, but it is not equivalent to electrical simulation, protection settings or equipment life analysis, and document versions and site changes must be maintained continuously.

Device-Edge-Cloud CollaborationTopology Visualization

Solution overview

The solution improves spatial and logical location in distribution systems. The focus is to establish stable relations between engineering document objects, device assets, acquisition points and alarm status, then provide a topology and fault location entry point viewable by permission.

Applicable industries

  • Multi-industry industrial sites
  • Industrial parks
  • Manufacturing plants

Primary user roles

  • Automation engineers
  • System integrators
  • O&M staff

Problems addressed

  • Graphics are disconnected from live data, so fault location is slow
  • Engineering document versions, device codes and the actual site do not match
  • Topology display permissions, maintenance ownership and update mechanisms are unclear

Recommended product combination

FEXLINK

FEXLINK IoT Platform

Maintains device, point, graphic element and alarm relationships and provides topology display and location entry points

System architecture and data flow

Distribution Topology and Digital Twin Display System TopologyFour-layer data flow across perception, edge control, platform and application for Distribution Topology and Digital Twin Display.01Perception layer
Field instruments, breakers and gateways provide circuit status, measured values and communication status
02Edge / control layer
Edge devices perform data acquisition, quality checks and necessary buffering
03Platform layer
FEXLINK binds device codes, topology nodes, raw points and alarms into a queryable relationship
04Application layer
O&M staff view device status, alarms and history from a topology node and locate the corresponding cabinet a…

Perception layer

Field instruments, breakers and gateways provide circuit status, measured values and communication status

Edge / control layer

Edge devices perform data acquisition, quality checks and necessary buffering

Platform layer

FEXLINK binds device codes, topology nodes, raw points and alarms into a queryable relationship

Application layer

O&M staff view device status, alarms and history from a topology node and locate the corresponding cabinet and circuit

Data flow

  1. Collect confirmed distribution documents, cabinet lists, device registers and point tables
  2. Establish unique codes and relationships for topology nodes, devices and acquisition points
  3. Live data enters the platform and updates node status, measured values and alarms
  4. Users open device details, historical trends and related work orders from an abnormal node
  5. When documents or devices change, publish a new version and retain the historical relationship

Integration and interfaces

  • Field status enters through project-confirmed Modbus, DI/DO, MQTT or gateway interfaces
  • Topology data can be produced from controlled document conversion, asset import or manual modeling
  • When connecting to GIS, BIM or an existing distribution monitoring system, confirm coordinates, object codes and update responsibility
  • Cross-system links should use stable object identifiers rather than layer names alone

Applicable standards

  • Applicable project standards for low-voltage distribution, engineering documents and industrial data management; the final edition is confirmed against project location, industry and project documents
  • Interfaces follow project-confirmed Modbus, MQTT or HTTP API

Acceptance and delivery boundaries

Suggested acceptance dimensions

  • Sample-check consistency between topology nodes, device codes, cabinet locations and actual points
  • Trace device details, raw data, alarms and historical records from a topology status
  • Simulate device offline, alarm and recovery, and verify that topology node status and platform records stay in sync
  • Check document version, publishing process and permission settings

Limitations and exclusions

  • The topology display in this solution does not perform short-circuit calculation, protection settings or electrical simulation
  • If documents, devices or points are not updated, the topology becomes inaccurate and maintenance ownership must be defined
  • Data quality in the display depends on field acquisition and point mapping and cannot be repaired by the graphic interface
  • Where sensitive engineering documents and network structures are involved, display only within authorized scope and do not expose the original files

Operational value

  • Links engineering document objects with live status and reduces the time spent finding a cabinet from an alarm description
  • Improves consistency between devices, points and topology through unified codes
  • Provides a spatial or logical location entry point for later asset, work order and operating analysis

Selection guidance

  • Define whether the topology scope is a single cabinet, a distribution room or multiple sites first, to avoid modeling too much at once
  • Prefer device codes and document versions that can serve as master data; a static background image is not sufficient
  • Where BIM or GIS is needed, assess data source, coordinate system and maintenance cost separately
  • A lightweight operating topology suits location and viewing; simulation, short-circuit calculation or protection settings require professional tools

Typical implementation patterns

  • Typical implementation pattern: distribution O&M starts from cabinet and circuit lists, links device codes, points and document graphics, and produces an operating topology on which duty staff can locate anomalies, with document versions retained on change. This is an anonymized typical pattern and does not represent specific customer modeling scope or simulation capability.

Before retrofit → With the solution

Before retrofit

  • Graphics and real-time data are disconnected; fault localization is slow; alarm descriptions and cabinet positions are unclear
  • Engineering documentation versions, device IDs and field actuals are inconsistent; topology is distorted
  • Topology display permissions, maintenance responsibilities and update mechanisms are unclear; post-change history is difficult to reconstruct

With the solution

  • FEXLINK binds device IDs, topology nodes, raw points and alarms, forming queryable relationships
  • CW/ESX collect field device status and update node status, measurement values and alarms
  • O&M views device status, alarms and history from topology nodes, quickly localizing to corresponding cabinets and circuits

How to evaluate the effect

01

Measurable signal

Topology Node Coverage Rate

02

Data source

The platform calculates the ratio of modeled and point-bound topology nodes to design nodes

03

Review method

By distribution room/cabinet/circuit hierarchy separately

04

Acceptance boundary

Topology display does not perform short-circuit calculation, protection coordination or electrical simulation

Based on device IDs and point mapping

Frequently asked questions

Is a digital twin just a 3D visualization wall?

No. A digital twin may include 3D, but its core is the relationship between physical objects and data. In distribution O&M, stable links between devices, topology, points and status are more practical.

Does uploading engineering documents generate the topology automatically?

Not necessarily. Documents support modeling, but object recognition, device codes and point mapping are still required, and document formats and conventions affect how much can be converted automatically.

Does the topology need real-time refresh?

Set the refresh frequency according to the business need. Switch status, alarms and measured values can run at different periods, and a very fast global refresh adds network and platform load.

Can it locate the faulty device directly?

Only to nodes that are modeled and have valid status or alarms. Uncovered devices, incorrect points or inaccurate site documents affect the location result.

What happens when engineering documents change?

Update the topology through a version publishing process and record the editor and effective time. Overwriting the old version makes historical alarms hard to reconstruct.

Request a matched product combination and project review

Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.

Contact FEXLINK