Direct Answer
With a limited budget, should a project start with a monitoring dashboard or go straight to the Qianzhi/Wanxiang/Tianyan three-engine stack? The dividing line is not point scale but "hazard density and decision frequency" — projects with fewer than 200 points and mainly meter-reading and alarms are served by a dashboard; projects with more than 500 points, multiple parallel circuits and safety or energy-efficiency assessments justify the three engines' alarm compression, root-cause location and early prediction. The test: how many alarms per day require a human judgment — few alarms, a dashboard suffices; more alarms than people can review, the three engines earn their value.
A scenario: One park has 120 points and 2-3 alarms a day — a dashboard is enough and the duty staff handle them one by one; one factory has 800 points, multiple parallel circuits and 30+ alarms a day — the staff cannot review them all, false and missed alarms are frequent — the Qianzhi/Wanxiang/Tianyan stack compresses the alarms into 3-5 effective events with root causes given directly. For the same "electrical digitization", point scale is not the key — "alarm density" is — when alarms exceed what people can review, the three engines are the time.
1. The Capability Gap: Threshold Alarms versus Three-Engine Diagnosis
Dashboard capability — threshold alarms: over the limit it reports, then it is done; Qianzhi engine — alarm compression and grading: 30 repeated alarms become 1 effective event; Wanxiang engine — location awareness and root-cause location: cabinet A's overheating traced to phase B's load, located directly; Tianyan engine — trend prediction: CUSUM finds abnormal trends early, before a trip; The nature of the gap — the dashboard answers "is it over the limit now"; the three engines answer "what is wrong and what happens next".
In one sentence: the dashboard is threshold alarms (report when over); the three engines are compression, location and prediction (report accurately, point clearly, see ahead) — alarm handling differs fundamentally.
A capability example: One busbar temperature alarm: the dashboard reports "cabinet 3 temperature 78 °C over limit"; the three engines report "cabinet 3 phase-B joint at 78 °C, rising for 2 hours, CUSUM early warning, suspected rising contact resistance, recommend a power-off inspection within 72 hours". The same alarm — the dashboard gives the "state", the three engines give the "action" — that is the essence of the gap.
2. Three Scale Tiers: Point and Alarm-Density Recommendations
Tier one, fewer than 200 points and fewer than 5 alarms a day — a dashboard suffices: the duty staff can handle them one by one; Tier two, 200-500 points and 5-20 alarms a day — dashboard plus Qianzhi: compress alarms first so people can review; Tier three, more than 500 points and more than 20 alarms a day — all three engines: compression, location and prediction, people handle only effective events; Scale and density — many points do not mean many alarms: dense alarms come from parallel circuits and fluctuating loads; The dividing line — not points but the "alarms per person" ratio: when people cannot review, upgrade.
In one sentence: three tiers are fewer than 200 points dashboard, 200-500 dashboard plus Qianzhi, more than 500 all three engines — the line is alarm density, not point scale.
A scale example: One school has 180 points and 3 alarms a day — a dashboard suffices; one chemical plant has 600 points and 40 alarms a day — the dashboard floods — the three engines compress it to 5 events and the staff stay orderly. Points and alarm density often diverge — dense-load sites have few points but many alarms — tier by alarm density, not by points.
3. Hazard Density: Why Some Small-Point Projects Also Need the Three Engines
High hazard density — old equipment, many bad contacts: few points but frequent alarms; Strict safety assessments — accident accountability: not one alarm can be missed; Strict energy assessments — energy indicators: trend analysis finds waste; Multiple parallel circuits — one fault reaches many circuits: root-cause location, not one-by-one handling; High decision frequency — judgments made daily: alarms become decisions and need AI support.
In one sentence: hazard density equals old equipment plus safety assessment plus energy assessment plus parallel circuits plus high decision frequency — with three of five present, even a small site deserves the three engines.
A density example: One old hospital: only 150 points, but aging equipment and bad contacts — 15 alarms a day — the dashboard cannot keep up; Qianzhi compresses them to 2-3 effective events — operating-room power safety is secured. Hazard density is a quality, not a quantity — old assets alarm frequently even with few points — invest in the three engines by hazard density, spending on the blade of the knife.
4. Alarm Compression: How Qianzhi's Value Is Measured
What Qianzhi does — merges similar alarms: repeated alarms on one circuit become 1; Qianzhi's value — fewer effective events for people: 30 becomes 3-5; Qianzhi's grading — 6 alarm levels: priority is clear at a glance; Qianzhi's boundary — compression is not elimination: you still need to know what is wrong; Qianzhi with Wanxiang — Qianzhi compresses, Wanxiang locates: effective events plus root cause, one clear view.
In one sentence: Qianzhi is alarm compression plus 6-level grading — 30 alarms become 3-5 — with Wanxiang locating, people handle only effective events.
A Qianzhi example: One factory has 20 motors alarming simultaneously: the dashboard floods with 20 entries — Qianzhi recognizes "one busbar voltage fluctuation" and merges them into 1 event — the duty staff handle it once without checking each motor. Compression's value is turning an alarm storm back into effective events — the object of human handling goes from 20 to 1 — that is the first layer of the AI hub's value.
5. Root-Cause Location: Why Wanxiang Saves Time
What Wanxiang does — location awareness: it knows where each measurement sits, on which circuit and device; Wanxiang's association — rules among measurement points: anomaly A triggers a check on B; Wanxiang's root cause — traces to the source: the load, harmonics or contact issue behind the alarm; Wanxiang's time saving — troubleshooting from hours to minutes: no cabinet-by-cabinet search; Wanxiang's boundary — needs an object model: the finer the modeling, the more accurate the location.
In one sentence: Wanxiang is location awareness, association rules and root-cause location — troubleshooting goes from "search every cabinet" to "point directly" — saving time and raising handling efficiency.
A Wanxiang example: One switch room has a harmonic alarm: previously each cabinet had to be searched for the harmonic source — Wanxiang locates "cabinet 3's frequency-converter load is heavy, 5th harmonic over limit" — troubleshooting drops from 2 hours to 10 minutes. Root-cause location's value is turning "people look for the problem" into "the system points to the problem" — on parallel-circuit projects, the time Wanxiang saves is the risk reduction.
6. Trend Prediction: Tianyan's Lead Time
What Tianyan does — trend analysis: algorithms such as CUSUM look at the trend, not the instant; Tianyan's lead — early warning: an abnormal trend is found before the trip threshold; Tianyan's scenarios — bad contacts, insulation aging, load growth: all "slowly worsening" faults; Tianyan's boundary — needs history: the more data accumulated, the more accurate the prediction; Tianyan and assessments — safety and energy assessments both benefit: early action avoids incidents, trend analysis finds waste.
In one sentence: Tianyan is trend prediction plus early warning — finding "getting worse" before a trip — for slow faults such as bad contacts and insulation aging, Tianyan has the most value.
A Tianyan example: One busbar joint temperature rises slowly: 0.5 °C per day, not yet over the threshold — Tianyan's CUSUM warns "suspected rising contact resistance" — a power-off inspection finds a loose bolt — avoiding an overheat burn-out. Trend prediction's value is turning post-trip into pre-service — the lead time on slow faults is Tianyan's return on investment.
7. Dashboard First, Upgrade Later: When This Path Is Right
Path one, dashboard first — run a monitoring dashboard for 3-6 months: use data to prove the alarm density; Path two, dashboard plus Qianzhi — add Qianzhi when alarms grow: compress first so people can review; Path three, three engines directly — high hazard density and strict assessments: one step, avoiding two rounds of work; The right or wrong standard — watch the alarm-density trend: density rising, upgrade early; density steady, the dashboard suffices; The meaning — not "saving versus spending" but "phased investment by alarm density".
In one sentence: dashboard-first is run the dashboard for data (3-6 months), add Qianzhi when alarms grow, all three when density is high — phase investment by the density trend, neither blind spending nor falling behind.
A path example: One park started with a dashboard: in 3 months it found "summer air-conditioning load alarm density doubled" — Qianzhi compression and Tianyan prediction were added — the autumn peak passed smoothly — phased investment, budget under control. "Dashboard first" is right when the density trend is measurable — let 3-6 months of data speak — upgrade when density rises, wait when it is flat — investment follows the data.
8. Taiyi Frontend: The Boundary of 100+ Visualization Components
What Taiyi is — the control hub: the command deck of the three engines, with 100+ frontend visualization components; Component capability — circuit topology, device profiles, alarm panels, trend charts: information visualized; Taiyi's fit — many points and a global view: park-level and plant-level command centers; Taiyi's boundary — too few points leave components unused: on a 100-point project, 100 components are waste; Taiyi and the three engines — the engines are the brain, Taiyi is the dashboard: when the brain computes right, the dashboard looks right.
In one sentence: Taiyi is the command deck of the three engines plus 100+ visualization components — suiting park/plant-level global views — too few points leave components unused; pick the frontend by scale.
A Taiyi example: One park-level project with 1,200 points: the Taiyi frontend shows all park circuit topology, device profiles and alarm distribution on one screen — the duty staff control "one screen for all"; an 80-point small project — most Taiyi components go unused, a dashboard suffices. Taiyi's boundary is the need for a global view — go Taiyi for "one screen of the whole area" — with few points and local views, a dashboard is more practical.
9. Landing Check: Five Questions for Three-Engine Selection
Question one, alarm density — how many alarms a day need human judgment: more than 20, go three engines; Question two, hazard density — many old devices and bad contacts: if yes, worth it; Question three, assessment requirements — safety or energy assessments: if yes, the three engines have grounds; Question four, parallel circuits — can a fault reach multiple circuits: if yes, root-cause location is needed; Question five, data foundation — does historical data exist: if yes, Tianyan can run predictions; The conclusion — with three of five answered yes, the three engines' return holds.
In one sentence: the five selection questions are alarm density, hazard density, assessments, parallel circuits and data foundation — with three or more yes, the return holds.
A five-question example: One manufacturer: 30+ alarms (Q1 yes), aging equipment (Q2 yes), energy assessment (Q3 yes) — three of five — the three engines: Qianzhi compresses, Wanxiang locates, Tianyan predicts — within one quarter, alarm handling time drops 70%. The three engines are not about "expensive or not" but "does the return hold" — three of five yes, and the return holds — decide by alarm and hazard density, and the budget is well spent.
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 Taiyi control hub V2.0 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
How Many Points Justify "Taiyi"
With a limited budget, should a project start with a monitoring dashboard or go straight to the Qianzhi/Wanxiang/Tianyan three-engine stack