MPE10000 FPI Monitoring & SCADA Integration

A practical operating view

The platform is described as presenting GIS maps, live network diagrams, phase-current trends, voltage-presence status and event records. Installed indicators and DCUs should be associated with verified location and feeder data. An operator can then use the alarm list and network view together to identify devices requiring investigation. The schematic shown here explains the architecture; it is not a screenshot of supplied software.

Measurements and alarms

Listed data points include phase load current, short-circuit and earth-fault events, fault current, line on/off status, indicator condition, FPI battery state, DCU battery voltage and solar charging voltage. Line temperature is mentioned in the overview but the catalogue does not define the sensor or measurement accuracy; include it only when the offered hardware and point list support it.

Maps, topology and access levels

The brochure describes device locations on an online map, user-drawn line topology, feeder/grid/circle-based login access and three user-access levels. The implementation should define who can view, acknowledge, configure and issue remote commands. Hosting responsibility, backups, user administration, network connectivity and system recovery should be documented before handover.

Event records and notifications

Fault, restoration and periodic status messaging are described, with department-specific notification routing. SMS capacities differ between catalogue sections: some passages mention five or ten numbers, while others describe unlimited user integration. A project proposal should state the actual recipient, user and gateway limits. Delivery also depends on the mobile network and messaging service.

Capacity, licensing and acceptance

The document refers to 5,000 FPI sets in one section and more than 5,000 DCUs in another, which are different quantities. It also lists a lifetime licence and two years of maintenance/updates. These are catalogue statements, not MPE contractual commitments. Confirm device count, server sizing, database requirements, support period and licensing in the offer. Validate map accuracy, event timestamps, alarm routing, user roles and SCADA exchange during acceptance testing.

Technical data and selection notes

Values below are transcribed or paraphrased from the supplied manufacturer catalogue. Entries marked for confirmation must be settled in the offered data sheet and approved project documents.

Communication architecture sketch