Energy & digital infrastructure

Power utilities

Energy systems are built on collection points. Which points must be read, how often, and what the thresholds are decide how trustworthy every downstream report is.

Cluster Energy
Focus Metering · alerts
Delivery Gate by gate, acceptable and operable

How we see this industry

Meters and collect

Power and energy systems do not start with an energy wall. Every number on that wall comes from a collect point: meters, tie points, inverters, environment. Which points must be collected, how often, how gaps are backfilled, how thresholds alarm—if those three are unset, later reports only paint noise more prettily. We start on site with a point list: communications, multiplier, time sync, whether history can be recalled. Station vs office isolation, protocol conversion, and bad clocks are real project work in the design, not an assumption that a curve appears once plugged in.

Alarm grades

Alarms must grade or the shift turns all push off. Limit, comms loss, power factor, harmonics—which dispatch now, which enter a daily—sit with the roster. Energy used for settlement has a read time, freeze value, and a human check, separate from monitoring-minute data, so finance and operations do not each own a number both called “energy.”

Completeness as an SLA

Energy projects often write device online rate and data completeness into acceptance. Holes, spikes, and clock drift must be found and traced to a meter. Completeness and recall success are a daily board, not a one-day brush for acceptance. Distributed PV, storage, and demand control, if in scope, split control and monitor rights—a mis-control costs more than a missing picture.

Demand and TOU

Demand, power factor, and time-of-use decide the utility bill and are not the same definition as a monitoring instantaneous. Virtual power plant or demand control, if in scope, must split command and monitor rights. Meter swaps and multiplier changes have an effective time so history energy interprets at the then multiplier, or reconciling reopens old books. PV reverse flow and storage charge/discharge, if connected, need their own settlement points.

By station or feeder

Go-live is by station or feeder: keep critical settlement points collectable and trusted, then expand monitors. Connecting existing SCADA or billing uses the point list and energy definition as source of truth. Training is shift and metering. A power system that works has answered alarms, matched energy, and explainable completeness; the wall is a display of those three, not the project goal.

Typical scenarios

Metering and reading

Electricity and water meters are read automatically on a cycle, abnormal readings are flagged for review, and manual entries record the operator.

Monitoring and alerts

Voltage, current, load, and device status raise alerts when out of range, routed by severity to the on-duty engineer.

Consumption analysis

Consumption is analysed by area, device, and time band to find abnormal growth and peak-valley patterns.

Common blockers and how we handle them

Blocker

Meter reading means walking the site, and data is a month behind

How we handle it

Devices report automatically, gaps are re-polled, and people only handle exceptions.

Blocker

There are so many alerts nobody reads them, and real problems get buried

How we handle it

Alerts are tiered with suppression rules and duplicates merged, so on-duty staff only see what needs action.

Blocker

The consumption report arrives but cannot say where the overrun is

How we handle it

Drill down by device and time band, compare consumption against output or floor area, and locate anomalies to a point.

Common system modules

Devices and points

Device register, collection points, comms configuration.

Data collection

Polling cycles, re-polling, abnormal reading flags.

Monitoring and alerts

Thresholds, tiered routing, closed-loop handling.

Consumption analysis

Consumption by area and time, peak-valley, period comparisons.

Work orders and maintenance

Defect orders, inspection plans, maintenance records.

Reports and export

Daily and monthly operation reports, compliance reports.

Delivery gates

  1. Scope

    Publish a point list: settlement points that must collect, monitors, period, and thresholds. Write who is master versus existing SCADA.

  2. Architecture

    Fix energy definitions, alarm grades, and time sync. Confirm protocol conversion, recall, and billing or finance connections.

  3. Build & integrate

    Measure collect, recall, and alarm dispatch on a station. Completeness and freeze-value checks are acceptance items, split from control rights.

  4. Launch & operate

    Batch by feeder; protect settlement points first. Train shift and metering; completeness enters daily review. Monitoring walls expand later.

Related capabilities

Related industries

Industries we ship in

Walk us through your process before anything gets built

Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.

Contact Us

Email
service@wehoope.com
Phone
+86 139-2520-6166
Address
W903, Shenzhen-Hong Kong Industry-Education-Research Base, 201 Gaoxin South 7th Road, Nanshan District, Shenzhen