Direct Answer

Why must an energy supervision platform split data into four levels — enterprise, workshop, production line and equipment — and how are the granularity and viewing scope of each level decided? The four levels map to different decision rhythms: enterprise level views hours/days (operations and assessment), workshop/building level views minutes (operational benchmarking), production line/system level views seconds (process optimization), key equipment level views milliseconds (root-cause insight) — the finer the level, the finer the granularity and the faster the response.

A scenario: A company deploys a supervision platform — the CEO wants "today's whole-plant energy use" (daily granularity) — the workshop supervisor wants "this line's current load" (minute granularity) — process wants "the current waveform at this equipment's startup moment" (millisecond granularity) — one platform, four rhythms — each takes what it needs. The logic of layering is that different roles have different decision rhythms — granularity follows the decision rhythm, not a hard split by department.

1. Why Layer by "Decision Rhythm"

What decision rhythm is — decision frequency: some view daily, some view seconds; The basis for layering — rhythm matching: granularity aligned to the decision rhythm; Why not by department — departments change: organizational structure shifts frequently; The benefit of rhythm-based layering — stable: decision rhythms are stable over time; The essence — serving decisions: each layer's data answers one decision question.

In one sentence: layer by decision rhythm — granularity follows decision frequency and stays stable.

An example: A factory reorganizes — departments merge — but the four levels stay — because the decision rhythms did not change. The logic is that departments change and rhythms do not — layering by rhythm keeps the platform effective through organizational change.

2. Enterprise Level: Hour/Day Granularity

What it views — the whole enterprise: plant consumption, total bill and total load; Time granularity — hours/days: operations and assessment compared monthly; Typical indicators — total energy, energy per unit output, electricity bill, carbon emissions; Decision questions — business questions: cost, assessment and benchmarking; Data source — aggregated from below: workshop and building data summed up.

In one sentence: the enterprise level views hours/days — answering operations and assessment questions.

An example: The CEO's monthly meeting views the enterprise level: total energy, energy per unit output and the bill — compared with last month — a basis for decisions. The logic is that the enterprise rhythm is monthly operations — hour/day granularity is enough; second-level data is unnecessary.

3. Workshop/Building Level: Minute Granularity

What it views — workshops/buildings: energy by workshop and by building; Time granularity — minutes: operational benchmarking and shift analysis; Typical indicators — workshop energy, unit consumption, load curves, peak and valley; Decision questions — operational questions: which workshop uses more, shift differences; Data source — line data aggregated plus its own metering.

In one sentence: the workshop/building level views minutes — answering operational benchmarking and shift questions.

An example: A workshop supervisor views minute-level data: workshop 3's load curve — finds night-shift idling — shifts the schedule — saves electricity. The logic is that the workshop rhythm is shift operations — minute granularity is enough — second-level data is information overload.

4. Production Line/System Level: Second Granularity

What it views — lines/systems: each line's energy use and system operation; Time granularity — seconds: process optimization and start/stop analysis; Typical indicators — line load, energy per unit product, start/stop counts; Decision questions — process questions: line efficiency and process energy; Data source — equipment data aggregated plus line metering.

In one sentence: the production line/system level views seconds — answering process optimization questions.

An example: Process views second-level data: one line's energy per unit product is high — traced to frequent starts and stops — process optimized — energy down. The logic is that the line rhythm is process control — second-level granularity captures starts, stops and fluctuations — the basis for process optimization.

5. Key Equipment Level: Millisecond Granularity

What it views — key equipment: motors, compressors and transformers; Time granularity — milliseconds: root-cause insight and fault tracing; Typical indicators — start current, transient waveforms, power factor, harmonics; Decision questions — root-cause questions: which equipment is the root of high energy; Data source — direct acquisition: edge access via ESX.

In one sentence: the key equipment level views milliseconds — answering root-cause insight questions.

An example: A factory's energy anomaly — drilled down to equipment-level millisecond data — finds abnormal start current in one motor — replaced and restored. The logic is that the root hides in milliseconds — equipment-level data is the last mile — it finds the root of high energy and faults.

6. Aggregating Bottom-Up and Drilling Down Top-Down

Bottom-up — aggregation: equipment to line to workshop to enterprise, summed level by level; Top-down — drill-down: enterprise to workshop to line to equipment, going deeper level by level; The meaning of aggregation — see the whole: the enterprise level is the business view; The meaning of drill-down — find the root: from an abnormal indicator to a specific device; The coordination — a closed loop: see the whole and trace the root.

In one sentence: data aggregates bottom-up and drills down top-down — see the whole, trace the root.

An example: A factory's energy anomaly — the enterprise level sees total consumption rise — drills down workshop, line and equipment — locates the air compressor — fixed. The logic is that aggregation and drill-down are two directions of the same data — upward is business, downward is the root.

7. The Correspondence to Sensing, Edge, Platform and Application

The sensing layer — device acquisition: sensors and meters produce data; The edge layer — ESX gateway: local aggregation and second/millisecond processing; The platform layer — data storage: four-level data aggregated; The application layer — the cockpit: enterprise-level presentation and drill-down interaction; The coordination — end to end: one chain from device to cockpit.

In one sentence: sensing, edge, platform and application are acquisition, processing, storage and presentation — an end-to-end loop.

An example: A project: ESA meters sense — ESX aggregates 2,000 points at the edge — the platform stores four levels — the cockpit presents — end to end runs. The logic is that the four levels land on the four-layer architecture — sensing produces data, edge preprocesses, platform aggregates and application presents.

8. The Value of Position Awareness

What position awareness is — data has a location: every data point knows its production line and circuit; The value of location — precise response: alarms locate directly; Faster drill-down — direct to the root: no guessing level by level, one step; Operational convenience — itemized reports: automatic itemization by location; The relation to the four levels — a base capability: position awareness makes four-level drill-down faster.

In one sentence: position awareness means data has a location — drill-down in one step, alarms located precisely.

An example: A factory alarm says "abnormal current in circuit B of line 3" — position awareness locates it directly — on site in 10 minutes. The logic is that without position awareness, an alarm only says "somewhere is abnormal" — with it, it goes straight to the line and circuit — disposal an order of magnitude faster.

9. Back to YESLON: What ESX Carries

The ESX position — the edge gateway: 30 devices/2,000 data points aggregated locally; What ESX does — carries granularity: second/millisecond data processed at the edge; Offline buffering — reliability: edge storage, no data loss offline; The relation to the four levels — the base: equipment-level data enters via ESX; The YESLON promise — four levels complete: from cockpit to millisecond data in one chain.

In one sentence: ESX is the edge base of the four levels — millisecond data carried locally.

An example: A park deploys ESX: 30 devices, 2,000 points aggregated — millisecond processing locally — offline buffering — four-level data complete. The logic is that the four levels need edge computing — ESX processes millisecond data locally, giving the four levels a data base.

10. Self-Check: Four Questions to See Whether the Layering Is Right

Question one, does the granularity match — granularity: does each level's granularity match the decision rhythm; Question two, does it flow both ways — bidirectional: are aggregation and drill-down smooth; Question three, is position there — position: does the data have position awareness; Question four, is the base stable — base: is edge capacity reliable.

In one sentence: the four questions are granularity, bidirectional, position and base — all answered, the four levels hold.

A self-check example: A platform self-checks: enterprise level daily OK, drill-down smooth, position awareness present, ESX carrying — all four pass. The four levels of an energy supervision platform are built by decision rhythm: enterprise level views hours/days (operations and assessment), workshop/building level views minutes (operational benchmarking), production line/system level views seconds (process optimization), key equipment level views milliseconds (root-cause insight) — the finer the level, the finer the granularity and the faster the response — data aggregates bottom-up and drills down top-down — it lands on the sensing, edge, platform and application architecture — position awareness makes drill-down one step.

Scope and Limitations

  • The conclusions in this article are intended for LV distribution and electrical-safety sites. Criteria are compiled from public codes and FEXLINK product documentation, and product parameters follow the latest selection handbook and product knowledge base.
  • Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving ESX intelligent edge computing gateway (30 devices / 2000 data points) should be verified against actual circuit parameters.
  • Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
  • Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
  • Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.

Frequently Asked Questions

From Executive Cockpit to Second-Level Line Data

Why must an energy supervision platform split data into four levels — enterprise, workshop