Digital Energy

Relationship Between the Pre-Layer and Diagnostic Engine Hub

In the expression system of the product knowledge base there is no independent "front-end large model". The terminology note of the product knowledge base expressly states that no independent "front-end large model" naming appears in the documentation; the so-called "front-end" capability actually exists in the form of safety red-line pre-verification (L3) plus Diagnostic Engine hub unified scheduling.

2026-09-25 Digital Energy FEXLINK 8 min
Front-End Layer and Diagnostic Engine Hub: Seven-Level Pipeline L1-L3
Front-End Layer and Diagnostic Engine Hub: Seven-Level Pipeline L1-L3

Direct answer

In the expression system of the product knowledge base there is no independent "front-end large model". The terminology note of the product knowledge base expressly states that no independent "front-end large model" naming appears in the documentation; the so-called "front-end" capability actually exists in the form of safety red-line pre-verification (L3) plus Diagnostic Engine hub unified scheduling. Where the market side needs a separate name, the suggestion is to use "Diagnostic Engine hub (front-end scheduling)". That is, the "front-end layer" and the "Diagnostic Engine hub" are not two competing entities but two descriptions of the same capability: the former describes its position in the seven-level pipeline, the latter describes the scheduling duty it carries. The product knowledge base places the "front-end" duty on L1 to L3 of the seven-level pipeline and corresponds it to the early architecture's Diagnostic Engine hub (unified scheduling). This article restates only the above specification and infers no unlisted module, interface or scheduling algorithm.

1. First clarify the naming boundary

In discussing "what the relation is between the front-end layer and the Diagnostic Engine hub", the first step is not to compare functions but to confirm whether the name exists. The terminology note of the product knowledge base records that no independent "front-end large model" appears in the documentation, that the front-end capability exists in the form of safety red-line pre-verification plus Diagnostic Engine hub scheduling, and that the market expression is advised to be unified as "Diagnostic Engine hub (front-end scheduling)". The appendix of the product knowledge base gives the same specification in its known information gap entry: there is no independent "front-end large model" in the documentation, and the front-end capability equals safety red-line pre-verification (L3) plus Diagnostic Engine hub unified scheduling. The terminology note in the body and the gap entry in the appendix corroborate each other, showing that this is not an incidental wording but a naming boundary the product knowledge base deliberately clarifies. Establishing the boundary first keeps the later discussion from being led astray by a concept that does not exist.

2. Front-end duties fall on L1 to L3

The product knowledge base records that, under the current documentation system, the "front-end" duty is carried by L1 to L3 of the seven-level pipeline. The seven-level pipeline itself is L1 access, L2 cleaning, L3 standard verification, L4 Diagnostic Engine analysis, L5 Correlation Engine study, L6 fusion decision and L7 persistence. Ranging L1 to L3 as "front-end" means that the common task of these three levels is: before the analysis layer starts work, to bring the data in, wash it clean, and pass standard verification. This definition explains what the "front-end" really is: not an independent model but the set of duties in the front section of the pipeline. The processing that data undergoes before entering L4 Diagnostic Engine analysis all belongs to the front-end scope. So the question "what is the relation between the front end and the Diagnostic Engine hub" can begin with "where the front end sits in the pipeline", and then move to its correspondence with the Diagnostic Engine scheduling duty.

3. L1 access: parsing of more than 40 protocols

As the first front-end level, L1 carries data access. The product knowledge base records that the L1 access layer parses more than 40 protocols, including Modbus, MQTT, OPC-UA, 104 and BACnet. Field devices communicate in different ways, and without unified protocol parsing the later analysis cannot begin. Placing L1 within the front end shows that "bringing it in" is itself a part of ensuring analysis quality. The coverage of protocol parsing directly decides which devices' data can enter the pipeline. This layer produces no analysis conclusion, yet it decides whether the data on which conclusions rest is complete, so it is reasonable to classify it as a front-end duty.

4. L2 cleaning: G5 four-level data cleaning

The second front-end level is L2 cleaning. The product knowledge base records that L2 is G5 four-level data cleaning, including denoising, deduplication, anomaly marking and interpolation completion. The four levels each address a class of data-quality problem: denoising removes acquisition noise, deduplication eliminates duplicate records, anomaly marking identifies suspicious points, and interpolation completion handles missing values. Placing cleaning before standard verification is deliberate: only after the data has first been tidied is there reliable input for standard verification and analysis. L2 is therefore both the data-quality processing layer and the linking link in the front-end chain.

5. L3 standard verification: why the red line is pre-positioned

The third front-end level is L3 standard verification. The product knowledge base records that the standard verification of L3 includes safety red-line pre-verification, which is executed before the Diagnostic Engine sub-model computation; once a red line is triggered, the highest-level alarm is output directly and all weighting operations are skipped. This passage is the key to understanding the value of the "front-end". Usually an analysis system computes the results first and then aggregates and weights them; but the product knowledge base advances the red-line verification to before the computation, and when a red line is triggered the data does not enter weighting but is given the highest-level alarm directly. This design means that, for cases involving a non-bypassable red line, the judgment can be made without waiting for the full computation. The front end here is not only "processing the data first" but "guarding the bottom line first". This also explains why the "front-end" capability is expressed together with safety red-line pre-verification.

6. The correspondence between the front end and the early Diagnostic Engine hub

The product knowledge base records that the "front end" corresponds to the role of the "Diagnostic Engine hub (unified scheduling)" in the early architecture, with duties of model orchestration, routing and distribution, unified interface and multi-model coordination. All four are scheduling-type duties: model orchestration decides which models to use and in what order; routing and distribution send tasks to the corresponding models; the unified interface shields internal differences from the outside; and multi-model coordination lets several models complete one thing together. Comparing the four with L1 to L3, the relation between the "front end" and the "Diagnostic Engine hub" becomes visible: the former emphasises its position and front-end duties in the pipeline, the latter emphasises its function as a unified scheduling role. The two describe two sides of the same thing, not two products to be distinguished.

7. Why naming clarification matters

Putting the above together, the landing point for answering "what the relation is between the front-end layer and the Diagnostic Engine hub" can be summarised in three points. First, there is no independent "front-end large model" in the documentation, and it should not be used as a product name or a new concept. Second, the front-end capability is jointly formed by safety red-line pre-verification (L3) and Diagnostic Engine hub unified scheduling, positioned at L1 to L3 of the seven-level pipeline. Third, the external expression is advised to be unified as "Diagnostic Engine hub (front-end scheduling)", to stay consistent with the product knowledge base. Naming clarification matters because an untrue concept brings a chain of effects: if market material invents a "front-end large model", technical documentation, solution architecture and external communication may each say something different. Conversely, unifying terminology per the product knowledge base lets market, technical and solution staff discuss the same thing under the same name. All of the above is limited to the terminology note and the appendix specification listed by the product knowledge base.

Scope and limitations

First, this article restates only what the product knowledge base lists, with the factual boundary limited to the terminology note's statements that no independent "front-end large model" appears in the documentation, that the front-end capability equals safety red-line pre-verification (L3) plus Diagnostic Engine hub unified scheduling, and that the expression is advised to be "Diagnostic Engine hub (front-end scheduling)", the same-specification entry in the appendix known information gaps, the front-end duty carried by L1 to L3, the capabilities of L1 to L3, and the correspondence between the front end and the early Diagnostic Engine hub (unified scheduling).

Second, the L1 parsing of more than 40 protocols and the listed protocols, the four items of L2's G5 four-level data cleaning, and the L3 safety red-line pre-verification with its output of the highest-level alarm and skipping of weighting operations upon triggering, are cited per the product knowledge base; this article extends no unlisted protocol list, cleaning algorithm or alarm-level definition.

Third, the front end corresponds to the early architecture's Diagnostic Engine hub (unified scheduling), with duties of model orchestration, routing and distribution, unified interface and multi-model coordination; this article infers no deployment form or internal implementation of that role.

Fourth, "Diagnostic Engine hub (front-end scheduling)" is the market expression advised by the product knowledge base, and this article draws no conclusion beyond it as a mandatory name.

Fifth, this article provides no specific system integration scheme or effect conclusion; actual capability is subject to the latest product material and project solution.

FAQ

Placing L1 within the front end shows that "bringing it in" is itself a part of ensuring analysis quality. so bringing data in supports the guarantee.
L2 cleaning: G5 four-level data cleaning The second front-end level is L2 cleaning. so L2 does the cleaning. The value is confirmed against the specification record.
the specification records that L2 is G5 four-level data cleaning, including denoising, deduplication, anomaly marking and interpolation completion. so denoising and deduplication are included.
L2 is therefore both the data-quality processing layer and the linking link in the front-end chain. so L1 is the first. The value is confirmed against the specification record.
L3 standard verification: why the red line is pre-positioned The third front-end level is L3 standard verification. so four stages run.

Related Knowledge

The Purpose of the 15-Minute to 2-Hour Forecast Window
Digital Energy

The Purpose of the 15-Minute to 2-Hour Forecast Window

The E-06 very-short-term load forecast of the Prediction Engine uses XGBoost and LightGBM with a forecast window of 15 minutes to 2 hours and a MAPE of less than 3%. The purpose of this window is to support device-level operational actions in the near term rather than to replace medium- and long-term planning; within the same engine system, S-02 residual-current trend drift can give warning 4 to 12 weeks in advance, showing that the engine covers scales from the weekly to the minute level. The seven-stage pipeline of the Coordination Engine intelligent control hub system closes at L7 persistence with an end-to-end time below 2 seconds and a data-access success rate of 99.9%, providing the near-real-time data-supplying chain for this window.

2026-09-22
Why Is Weiwulian a Data-Producing Company?
Digital Energy

Why Is Weiwulian a Data-Producing Company?

"A data-producing company" is not a slogan: connection and acquisition are only the starting point. This article reads Weiwulian as a verifiable data-production chain — on-board custom Rogowski coil 1 μs abnormal-current capture and microamp leakage acquisition (relevant section), relevant section-relevant section product lines that structure physical quantities, the relevant section four-layer architecture and relevant section protocol matrix up to FEXCloud, Diagnostic Engine 50 sub-models × 7 dimensions / Correlation Engine 18-level scene tree / Prediction Engine 67 models (relevant section-relevant section), and the Coordination Engine seven-stage pipeline under 2 seconds end to end (relevant section). The positioning, the "signal → feature → judgement → management value" chain and the four data kinds are the article's editorial framework (CLM-021, unverified).

2026-09-13
Prioritizing Energy-Saving Retrofits
Digital Energy

Prioritizing Energy-Saving Retrofits

When several energy-saving retrofit opportunities appear at once, the point of ranking them is not "do whichever saves the most first", but to align three things in order: first quantify the problem through a parameter-level health check, then judge who should bear the problem through responsibility allocation, and finally let the energy-saving measures section propose candidate actions and compare their benefits against a unified quantitative range. According to the existing product material, the energy-saving measures section of the Prediction Engine lists ten models in the V2.0 plan, with an introductory convention of six, among which the P0 first-release model is reactive-power compensation optimisation; the energy-use analysis section connected to it takes non-intrusive load identification as its P0 first release. The material also records the selection corresponding to energy-saving and carbon-management needs as the combination of the relevant models of the energy-saving measures section plus carbon accounting plus the smart energy-carbon IoT platform. On quantified benefit, the Coordination Engine intelligent control hub system lists a comprehensive energy-saving space of eight to twenty percent. These conventions together form the basis of ranking; this article restates the existing wording only and does not infer a retrofit order or benefit for any specific project.

2026-10-03

Want a deeper look at FEXLINK solutions?

Contact the FEXLINK solutions team for customised solutions and technical support.

Frequently Asked Questions

Why does access count as part of analysis quality?

Placing L1 within the front end shows that "bringing it in" is itself a part of ensuring analysis quality. so bringing data in supports the guarantee.

Which level performs the four-level cleaning?

L2 cleaning: G5 four-level data cleaning The second front-end level is L2 cleaning. so L2 does the cleaning. The value is confirmed against the specification record.

Which cleaning does L2 include?

the specification records that L2 is G5 four-level data cleaning, including denoising, deduplication, anomaly marking and interpolation completion. so denoising and deduplication are included.

Which level is the first front-end level?

L2 is therefore both the data-quality processing layer and the linking link in the front-end chain. so L1 is the first. The value is confirmed against the specification record.

How many cleaning stages does L2 run?

L3 standard verification: why the red line is pre-positioned The third front-end level is L3 standard verification. so four stages run.