Direct Answer
Once the baseline is built, how do you use it? Embed the baseline into a PDCA loop — continuously monitor performance with EnPI against the baseline, launch improvement projects when a deviation appears, and reassess and update the baseline after the improvement — forming a "monitor-improve-reassess" cycle that makes the baseline the starting point of continuous improvement rather than the end.
A scenario: A company works hard to build an energy baseline — but does not know how to use it daily — the baseline is archived after building — the investment produces no continuous output. The logic is that the baseline is not an archive file but the starting point of continuous improvement — embedded in the "monitor-improve-reassess" loop, the value of the baseline is released.
1. The Overall Framework of the Loop: Monitor, Improve, Reassess
Stage one, monitor — EnPI against the baseline: continuously monitor performance and detect deviation early; Stage two, improve — deviation triggers a project: when the deviation exceeds the threshold, launch an improvement project; Stage three, reassess — update the baseline after the improvement: after verifying the effect, reassess and update the baseline; The meaning of the cycle — continuous improvement: each cycle moves the energy level down one step.
An example: A company runs the loop for a year — 6 deviations found, 4 projects launched, the baseline reassessed twice — energy falls 8%. The loop is valuable only when it turns — each round lowers the energy level.
2. Performance Monitoring from the Baseline to EnPI
What to monitor — EnPI against the baseline: unit consumption and adjusted energy compared with the baseline; The monitoring cycle — monthly first: monthly monitoring, quarterly review and annual summary; The monitoring basis — same reference and same basis: consistent with the basis when the baseline was built; The monitoring output — the deviation report: deviation value, deviation rate and trend signal.
The correspondence table of monitoring cycles:
| Cycle | Scenario | Output |
|---|---|---|
| Monthly | Daily monitoring | Deviation report |
| Quarterly | Trend review | Quarterly summary |
| Annual | Summary and reassessment | Annual report |
The element list of the deviation report — current value: the actual EnPI; baseline value: the baseline prediction for the same period; deviation value and rate: absolute and relative; trend signal: the month-on-month direction; suggested action: investigate or launch a project — with the five elements complete, the report supports decisions directly.
An example: A factory monitors monthly — the unit EnPI deviates more than 5% for two months — an early warning triggers. Monitoring is about the deviation: how much and how long — small deviations are recorded, large ones warn — the earlier it is found, the more timely the improvement.
3. The Mechanism by Which a Deviation Triggers an Improvement Project
Trigger one, the deviation exceeds the threshold — continuous exceedance: unit consumption exceeding the baseline by 5% for two months triggers; Trigger two, the trend worsens — continuous rise: an energy trend worsening for three months triggers; Trigger three, abnormal events — sudden fluctuation: an abnormal single-month fluctuation over 10% triggers; The action after the trigger — project evaluation: confirm the cause of the deviation and evaluate the improvement potential.
The investigation path of the deviation — check the metering first: is the data accurate? Then the condition: have production, temperature and shifts changed? Then the equipment: is the equipment status abnormal? Finally the behavior: have operations and management changed? — four paths, in order.
An example: The compressed-air energy rises for three months — a project launches — a leak is found — after the improvement, the energy returns to the baseline. A deviation is the entrance of improvement — with trigger conditions, problems are handled early instead of at year-end.
4. Calculating the Saving after the Improvement
Calculation one, compare with the baseline — before and after: compare the post-retrofit energy with the baseline prediction; Calculation two, remove the condition effect — same basis: normalize production and temperature changes; Calculation three, the saving formula — baseline minus actual: saving = baseline prediction minus actual energy; Calculation four, the verification period — continuous verification: verify for at least 3-6 months after the improvement.
The four-step saving calculation — step one: use the baseline model to predict the should-be energy for the current month; step two: take the actual energy of the month; step three: subtract to get the saving; step four: convert to the saving rate (saving divided by the prediction) — the four steps are fixed and the calculation basis is unified.
The saving reference of common improvement projects — compressed-air treatment: leak treatment can save 5%-15%; motor system optimization: high-efficiency motors plus variable frequency can save 10%-25%; lighting retrofit: LED replacement can save 30%-60%; waste-heat recovery: reuse can save 5%-20% — the values are industry references and the actual measurement governs.
An example: The baseline predicts 150 ten-thousand kWh per month — after the retrofit, the actual is 138 — the saving is 12. The saving is credible only against the baseline: prediction minus measured, on a unified basis.
5. The Timing for Reassessing and Updating the Baseline
Timing one, after a major change — a large structural and equipment change: reassess after a new line or equipment replacement; Timing two, after the improvement stabilizes — the effect is consolidated: after the improvement runs stably for 3-6 months; Timing three, the data period expires — the baseline period expires: update by the cycle; Timing four, abnormal performance — the model fails: reassess when the prediction error keeps exceeding the limit.
The outputs of the reassessment — the conclusion: update or rebuild; the old-new comparison: the version difference; the effective date: the switch point; the approval signature: confirmed by the system owner — with the four outputs, the reassessment leaves a complete trace.
An example: After the improvement, the new baseline is reassessed and the energy level steps down — the following assessment uses it. The baseline follows the business — without an update, the new level is misjudged as "over the limit"; with an update, the loop is complete.
6. How the Loop Is Implemented on a Supervisory Platform
Implementation one, automatic monitoring — the platform calculates automatically: EnPI automatically compares with the baseline and generates the deviation report; Implementation two, automatic warning — the threshold triggers automatically: a deviation over the limit automatically pushes a warning; Implementation three, the project ledger — online improvement-project management: project launch, progress and effect are tracked online; Implementation four, baseline version management — the old and new baselines coexist: the switch leaves a trace and is traceable.
The correspondence table of platform capabilities and loop stages:
| Loop stage | Platform capability | TIANYAN module |
|---|---|---|
| Monitoring | Automatic deviation report | E module (energy analysis) |
| Warning | Threshold push | E module |
| Improvement | Measure-suggestion generation | C module (energy-saving measures) |
| Reassessment | Baseline version management | E module |
The milestones of platform configuration — month one: monitoring online and the deviation report automatic; month two: warning-threshold configuration and the ledger enabled; month three: the full improvement-project flow online; month four: baseline version management effective — the four-month milestones gradually run the loop.
An example: The TIANYAN E module outputs the monthly deviation report and the C module gives measure suggestions — the loop turns on the platform. The platform automates the mechanical part — monitoring, warnings and the ledger run automatically — people focus on improvement, so the loop runs long-term.
7. The Implementation Steps of the Loop
Step one, define the indicators — select EnPI: clarify which indicators to monitor; Step two, set the thresholds — define the trigger conditions: how much deviation triggers a warning and a project; Step three, build the process — define the improvement process: project launch, execution and acceptance; Step four, go online on the platform — configure the platform: monitoring, warning and ledger online; Step five, review periodically — periodic review: monthly review, quarterly summary and annual reassessment.
The milestone table of the implementation stages:
| Stage | Time | Delivery | Acceptance |
|---|---|---|---|
| Define indicators | Week 1-2 | EnPI list | Indicator and basis confirmed |
| Set thresholds | Week 3-4 | Threshold grading table | Trigger rules confirmed |
| Build the process | Week 5-8 | Launch and acceptance process | One trial round |
| Go online | Week 9-12 | Monitoring, warning, ledger | Loop runs automatically |
The reference of input and output — input: about 1-3 months of manpower for the system; output: common enterprises save 3%-8% in the first year — the saving varies by industry and baseline level, and the actual measurement governs — run the loop first, then refine it.
An example: A company completes the five steps in two months — energy falls 6% after half a year. If one of the five items is missing, the loop stalls — advance by the steps and the system is complete.
8. Common Mistakes and How to Avoid Them
Mistake one, archive without using — the baseline is not used daily: embed it in monitoring to release value; Mistake two, monitor without improving — only report deviations without projects: deviations must land on improvement projects; Mistake three, no baseline update after improvement — the old baseline misjudges the new level: reassess and update after the improvement stabilizes; Mistake four, inconsistent basis — monitoring and the baseline use different bases: keep the same basis throughout.
The self-check list of the mistakes — does the baseline enter the monthly monitoring? Do deviations land on improvement projects? Is the baseline reassessed and updated after improvement? Is the monitoring basis consistent throughout? — answer the four questions and fill the gap.
The monthly rhythm of the loop — month start: the platform outputs the deviation report of last month; mid-month: deviation analysis and improvement execution; month end: improvement effect summary; quarterly: reassess the baseline and update the ledger — a fixed rhythm keeps the loop turning.
An example: A company only monitors without projects — deviations are reported for 3 months with no action — the effect appears after adding the launch mechanism. Every stage must turn — if any stalls, the loop breaks; check which stage is broken first and fill it.
Back to the TIANYAN product match — the TIANYAN engine E module (energy analysis) automatically completes monitoring and warning, and the C module (energy-saving measures) gives improvement suggestions — the "baseline-EnPI-improvement-reassessment" loop runs automatically on the energy-carbon autonomy system 4x3x2 — enterprise energy performance management upgrades from "build and archive" to "continuous improvement".
Building the baseline is not the end but the beginning — embed it in the "monitor-improve-reassess" loop — EnPI continuously monitors against the baseline, deviation triggers improvement projects, the saving is calculated after the improvement, and the baseline is reassessed and updated after stabilization — the platform automates the mechanical stages — when the loop turns, energy drops each round — the baseline becomes the starting point of continuous improvement, not the end.
Scope and Limitations
- The conclusions in this article are intended for LV distribution and electrical-safety sites. Standard numbers (GB/T 23331) refer to their currently effective editions, and product parameters follow the latest FEXLINK 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 Tianyan engine, E track (energy analytics), C track(saving measures) 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
Once the Baseline Is Built, How to Use It? A Baseline
Embed the baseline into a PDCA loop — continuously monitor performance with EnPI against the baseline, launch improvement projects when a deviation appears