Home / Solutions / Maximum Demand and Peak Shaving

Maximum Demand and Peak Shaving

Maximum demand management requires confirming the demand period used for grid settlement, the tariff rules and the adjustable load boundary first. ESA then provides electrical parameters on the relevant circuits, FECB2P and FECM2 serve as candidate control and aggregation components, and CW aggregates the data. Any remote switching must include permissions, safety interlocks and manual fallback, and must not bypass existing protection.

Energy DataStatus Visualization

Solution overview

The solution separates demand monitoring, load control and safety authority by design, and emphasizes that control actions require dedicated confirmation.

Applicable industries

  • Industrial parks

Primary user roles

  • Energy managers
  • Electrical O&M
  • Business management

Problems addressed

  • Peak demand raises costs, and load adjustment lacks a basis
  • Adjustable loads have no register or real-time status
  • Remote control authority, fallback and response results lack records

Recommended product combination

System architecture and data flow

Maximum Demand and Peak Shaving System TopologyFour-layer data flow across perception, edge control, platform and application for Maximum Demand and Peak Shaving.01Perception layer
ESA monitors the main incomer and key loads;FECB2P and FECM2 provide confirmed load status or switching capa…
02Edge / control layer
CW performs data aggregation and authorized rules. It does not carry mandatory protection by default.
03Platform layer
FEXLINK builds demand, load, control and response records.
04Application layer
Energy staff review peak-shaving strategies;O&M staff handle alarms and fallback.

Perception layer

ESA monitors the main incomer and key loads; FECB2P and FECM2 provide confirmed load status or switching capability.

Edge / control layer

CW performs data aggregation and authorized rules. It does not carry mandatory protection by default.

Platform layer

FEXLINK builds demand, load, control and response records.

Application layer

Energy staff review peak-shaving strategies; O&M staff handle alarms and fallback.

Data flow

  1. Define the demand period and the adjustable load schedule
  2. Acquire main-incomer and load status data
  3. Calculate demand trends and strategy trigger conditions
  4. Execute or prompt load adjustment after authorization
  5. Record actual changes, alarms and manual intervention

Integration and interfaces

  • Grid demand rules and settlement data are provided by the relevant project parties
  • FECB2P and FECM2 protocols, point lists and control authority must be confirmed item by item
  • When connecting to production systems, control actions must not affect critical processes or safety equipment

Applicable standards

  • Demand metering and electricity demand management rules are confirmed against local policy and project documents
  • LV protection and control circuits follow applicable electrical standards
  • Control strategies, authority and failure fallback rules are frozen before implementation

Acceptance and delivery boundaries

Suggested acceptance dimensions

  • The demand period and metering points match the project rules
  • The adjustable load register, capacity and control authority are defined
  • Control commands, execution status and manual fallback carry time records
  • Strategies do not bypass existing protection or critical equipment limits
  • Actual load changes correspond to triggering events
  • Safety interlock and anomaly fallback tests are completed during the pilot

Limitations and exclusions

  • No fixed peak-shaving volume, cost saving or revenue can be committed
  • The solution cannot bypass existing protection, fire protection or critical process interlocks
  • Automatic switching is not performed before the control and communication capability of FECB2P and FECM2 is confirmed

Operational value

  • Links maximum demand to specific load circuits
  • Establishes traceable records for manual or automatic peak shaving
  • Reduces blind control caused by unclear load status

Selection guidance

  • Screen non-critical, interruptible loads that have been authorized first
  • Select FECB2P or FECM2 by circuit current, communication and switching requirements
  • Without safety interlocks and fallback conditions, provide monitoring and prompting only

Typical implementation patterns

  • A typical implementation pattern establishes demand trends and an adjustable load register first, then selects a small number of loads with clear safety boundaries for a control pilot. The pattern contains no specific tariffs, load capacity or settlement results.

Before retrofit → With the solution

Before retrofit

  • Peak demand raises costs, and load adjustment lacks a basis
  • Adjustable loads have no register or real-time status
  • Remote control authority, fallback and response results lack records

With the solution

  • Links maximum demand to specific load circuits
  • Establishes traceable records for manual or automatic peak shaving
  • Reduces blind control caused by unclear load status

How to evaluate the effect

01

Measurable signal

ESA monitors the main incomer and key loads;FECB2P and FECM2 provide confirmed load stat…

02

Data source

ESA Smart Meter (40+ Electrical Parameters) · FECB2P Smart Circuit Breaker (Load Switching & Metering)

03

Review method

The demand period and metering points match the project rules

04

Acceptance boundary

No fixed peak-shaving volume, cost saving or revenue can be committed

Frequently asked questions

Can every load take part in peak shaving?

No. Fire protection, safety, critical process and non-interruptible loads must be excluded, and management authorization obtained.

How often is demand calculated?

According to the local grid and project rules. The platform configuration must match the settlement period.

Can circuit breakers be controlled automatically?

It requires confirmed FECB2P or FECM2 capability and an electrical design, plus permissions, interlocks and fallback. Monitoring and prompting are preferred by default.

How is the peak-shaving effect verified?

Compare the same-period baseline, actual load and control records, while excluding production changes and abnormal downtime.

What if control fails?

Local protection, manual fallback and alarm records must be retained. Platform control must not be the only safety measure.

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