How to Choose an Implementer for Wind-Solar-Storage-Charging and Energy-Management Dashboards

When an energy project needs a monitoring dashboard or a multi-site view, the usual disagreement is not whether the screen can be given a green, low-carbon look. It is whether this phase is about photovoltaics, energy storage, plant or park energy use, or placing several sources on one monitoring page. Before an implementer is chosen, the objects, the metering boundary and the purpose of the data should be stated clearly. Only then can the interfaces and acceptance be compared.

Hongshan Technology carries out data integration, monitoring displays and custom systems by project, as a full-chain digital solutions provider. The boundaries below are what should be asked at selection. Meter definitions, grid-connection conditions and site procedures still follow the owner's documents and existing technical guides.

On this page5 sections

First separate single-site monitoring, multi-site control, and whether the data are for monitoring or for settlement

Pages for wind, solar, storage, charging and energy management should first be placed in one of these groups:

  1. Single-site operations monitoring: for example generation, charge and discharge, equipment status, environment and alarms at one photovoltaic plant or energy-storage plant.
  2. Multi-site or area control: viewing several plants or energy-use units in one view, and agreeing which indicators can be summarised and which can only be viewed by site.
  3. Energy use and energy-and-carbon management: load, main and submeters, unit consumption or carbon pages for a factory or park, whose definitions must first be aligned with metering and statistical methods.
  4. Multi-source coordinated monitoring: for example placing photovoltaics, storage and load on one energy-flow diagram, to view direction, power at the same sampling time, and missing measurements.

The Chinese site already has solutions and metric articles for photovoltaic-plant operations, energy-storage monitoring, and energy and carbon monitoring, and a case description of photovoltaic-storage-grid energy flow. Monitoring of wind power and charging facilities currently appears mainly in a demonstration scene on the live-demo pages. That must not automatically be treated as an existing plant solution or a delivered project.

Multi-site control is not a set of reduced single-site screens placed side by side. Summaries are possible only when object codes, metering boundaries and time definitions are consistent. If an energy-flow diagram or a worked teaching example is already labelled as teaching data, it must not be accepted as project operating data.

Metering, plans and benefit calculations must state their purpose, and must not be mixed with monitoring data

Numbers on an energy page may all look like “energy” or “power,” but their purposes can be entirely different. At selection, the implementer should be asked to write down:

Differences between main meters and submeters, and between metering periods, should be reconciled before integration, not “balanced” on the screen after launch. If a cumulative device reading suddenly becomes smaller, reset, meter replacement and abnormal data should be distinguished first, and only then should the board decide how to display it.

An implementer should be able to connect to an existing EMS, BMS or meters, not only deliver a display page

When implementers are compared, first see whether they can state which layer of an existing energy-management system, battery-management system, converter, meters or plant monitoring system will be reused, who authorizes the access, how read-only monitoring will be done, and how joint-test and data-check records will be kept. If the source cannot be stated, a promise that “a green-power map can all be built” is not yet a basis for selection.

Public materials already on the Chinese site can be compared by task: photovoltaic-plant operations and energy-storage monitoring solutions, and an energy and carbon dashboard solution, for discussing plant operations, battery and converter monitoring, and energy-use and carbon pages; metric and multi-site lists for photovoltaic operations, energy-storage dashboards, and enterprise energy-management cockpits; a live case page for a photovoltaic-storage-grid energy-flow dashboard, which explains how generation, storage and load are shown together, and whose worked examples, if labelled as teaching data, are not project operating data; an energy-storage battery monitoring solution case and a zero-carbon park operations solution case, which introduce design ideas and are not the same as delivered client projects; and a desensitized presentation of an implemented water-and-energy-storage monitoring project, whose objects are water treatment, heating and cooling, and energy-storage dispatch, and which should not be called an integrated wind-solar-storage-charging project.

The “Wind, Solar, Storage and Charging Park” scene in the Live Demos centre is a browser demonstration. It shows 3D visualization of photovoltaic, storage, charging and wind-power monitoring and dispatch, uses demonstration data, and is not connected to live energy interfaces. It can help people understand the interaction. It must not be treated as a built client project, and it must not be used to accept live integration.

Hardware supply, electrical changes, site construction and control changes are not automatically included in the software or visualization scope. The delivery process published on the homepage has seven steps: requirements discussion, solution design, prototype confirmation, development, test and acceptance, deployment and launch, and operations support. Energy projects should, in the requirements discussion, first confirm the objects, the metering boundary and the purpose of the data; in test and acceptance, keep evidence for points, time definitions, missing-measurement states and alarm records, rather than judging only whether a demonstration page is complete.

On-premises or private deployment can be assessed. That is only a deployment boundary. Permissions, audit and backup still need to be designed. Whether industry or power-sector requirements apply is for the owner and specialists to judge.

FAQ

If there is no ready-made solution page for a wind farm or charging facilities, does that mean this kind of monitoring cannot be done?

It should not be judged by whether a ready-made poster exists. First check the systems, interfaces and metering points already on site. The materials published more completely on the site today are solutions and articles for photovoltaic, storage and energy-use monitoring. If wind power and charging are to enter the same phase, they should be assessed separately against existing data sources. A live-demo scene cannot replace the integration scope.

Once a single-site page is done, is multi-site control only an added summary?

Not necessarily. Multi-site control also requires consistent object codes, metering boundaries, time definitions and summary rules. Indicators that cannot be summarised should stay at the site level, and should not be added together on the overview.

Can the energy and benefit figures on the page be used directly for settlement?

Only when the definition, source and purpose have been agreed in writing and have been checked. Data used only for monitoring must not be treated by default as a basis for settlement or benefits.

If an EMS, BMS or meter system already exists, must a new collection layer be built?

First assess whether existing authorized interfaces can cover the states and trends needed this time. Reuse what can be reused, and assess gaps separately. A new page that is developed separately is not a reason to connect the equipment again by default.

Can the wind-solar-storage-charging park in the live demos be introduced as a delivered project?

No. That scene uses demonstration data and is not connected to live energy interfaces. It is only for understanding 3D visualization and interaction. Acceptance and public descriptions should keep it separate from implemented projects and solution cases.

Related reading

This article explains selection and acceptance methods. It does not replace a site survey, and it is not a uniform protocol-support list, a benefit calculation or a delivery commitment. References to solution, case and demo pages follow the project-case, solution notes or demonstration-data statements already made on those pages. Several Chinese solution and case pages have no English counterpart; the related-reading list above includes only English pages that return HTTP 200.