Direct Answer
When quoting a solution, how should the data points be priced per point — estimating too high or too low both lose — how is the basis defined? Use three bases: monitoring points (one real-time quantity per measurement point), data points (expanded from telemetry + digital signals + cumulative quantities), and registration points (objects + measurement points after platform modeling); quote and size capacity by the data-point basis, usually 3-5 times the monitoring points. An inconsistent point basis is the root of quoting disputes and capacity misestimation — define the basis first, then count the points, then quote — with a unified basis, the account is clear.
A scene: a project quoted 500 monitoring points and a gateway capacity of 2000 points looked sufficient — the actual expansion into data points was 2000+ — capacity insufficient, a second purchase — the cause was a basis mismatch: monitoring points do not equal data points — define the basis first, then calculate the capacity, and you will not misestimate.
1. Why Point Bases Create Disputes
The confusion of bases — "one point" means different things: some say measurement point, some say data point, some say registration point — different bases, numbers differing by multiples; The consequence of disputes — quoting by monitoring points and sizing by data points: the numbers do not match — the contract and the implementation contradict each other; The nature of the basis — one measurement point expands into multiple data: voltage/current/power, states, cumulative quantities — "a point" is not singular but an expanded set; The value of unification — define the basis before quoting: write the basis into the contract — the implementation matches the quote, with no rework.
In one sentence: basis confusion = "one point" means different things + numbers differ by multiples + contract contradictions — define the basis before quoting, and implementation matches with no rework.
A dispute example: a project quoted 500 monitoring points and signed a gateway of 2000 points — the implementation expanded to 2600 data points — capacity insufficient, and the extra cost became a dispute. Without a unified basis, quoting is "feeling an elephant in the dark" — define the three bases of monitoring point, data point and registration point first — then the contract and implementation will not clash.
2. Basis One: The Monitoring Point
The definition of the monitoring point — a monitoring point = one physical measurement point: a meter, a sensor, a switch — counted by "how many devices are installed"; The feature of the monitoring point — the most intuitive basis: count devices, count measurement points — the easiest starting point for quoting; The limitation of the monitoring point — one measurement point contains multiple data quantities: a meter contains voltage/current/power — the monitoring point does not reflect the data scale; The use of the monitoring point — quick estimation: first-round quoting, solution outline — use the monitoring point for a rough scale.
In one sentence: the monitoring point = one physical measurement point + the most intuitive device count + does not reflect data scale — use the monitoring point for a rough estimation.
A monitoring-point example: a project had 100 meters + 50 switches + 20 sensors — 170 monitoring points — a quick outline of the scale. The monitoring point is the "device count" — the most intuitive to count — but it does not reflect the expanded data scale — use it only for a rough estimate.
3. Basis Two: The Data Point
The definition of the data point — a data point = a point after data expansion: telemetry (voltage/current/power) + digital signals (states) + cumulative quantities (energy) — one point per item; The expansion of the data point — one monitoring point expands into multiple data points: a meter expands into voltage/current/power/energy/state — 3-5 times the monitoring points; The feature of the data point — the basis that really consumes collection and storage resources: gateway capacity and platform storage are counted by data points; The use of the data point — quoting and capacity: contracts are priced by data points — implementation capacity is verified by data points.
In one sentence: the data point = expanded from telemetry + digital signals + cumulative quantities + one monitoring point expands into 3-5 data points — quoting and capacity by data points — the basis that really consumes resources.
An expansion example: one meter: Ua/Ub/Uc/Ia/Ib/Ic/P/Q/S/energy/state — expands into 11 data points — one monitoring point, 11 data points. The data point is the "real workload after expansion" — one meter expands into 11 points — quote and size capacity by it, and the account is real.
4. Basis Three: The Registration Point
The definition of the registration point — a registration point = a point after platform modeling: objects (devices) + measurement points (data) — the platform-side billing and modeling basis; The composition of the registration point — the number of objects + the number of measurement points: each device is an object, each data point is a measurement point — counted after platform modeling; The feature of the registration point — the platform-side basis: capacity, licensing and billing are often by registration points — close to data points but including objects; The use of the registration point — platform-side accounting: deployment capacity, licensing scale — used in comparison with the data-point basis.
In one sentence: the registration point = objects + measurement points after platform modeling + the platform-side billing basis — close to data points but including objects — platform-side accounting uses the registration point.
A registration-point example: a platform modeled 170 device objects + 1900 expanded measurement points — 2070 registration points — the platform license was accounted by this. The registration point is "the point count after platform modeling" — objects plus measurement points — platform capacity and licensing are counted by it — compared with the data point, the bases are complete.
5. A Single-Feeder Data-Point Expansion Example
The composition of a feeder — one distribution feeder: metering + state + control — data points are expanded from these categories; The expansion of telemetry — voltage, current, power, power factor: a three-phase feeder expands into multiple items — every phase voltage and current counts as a point; The expansion of digital signals — switch states, alarm states: one point per state — few but must be counted; The expansion of cumulative quantities — energy, demand: cumulative quantities are independent data points — billing-related, must be counted.
In one sentence: a single feeder expands = telemetry (voltage/current/power) + digital signals (states) + cumulative quantities (energy/demand) — one feeder expands into 10+ data points.
A feeder example: a three-phase feeder: 3 phase voltages + 3 phase currents + total active/reactive/apparent + energy + switch state — about 10 data points. The feeder expansion is the "microscope of data points" — telemetry, digital signals and cumulative quantities expanded category by category — one feeder, 10 points, and the engineering quantity has a basis.
6. Gateway Capacity (2000 Points): By Which Basis
The basis of gateway capacity — a gateway capacity of 2000 points: does it mean data points or monitoring points? — by default, the data-point basis; Counted by data points — 2000 data points is roughly 400-600 monitoring points (3-5 times expansion) — whether the capacity is sufficient depends on the data points; The misconception of counting by monitoring points — thinking 2000 monitoring points = 2000 measurement points — after expansion the capacity is exceeded — capacity misestimated; Verifying the capacity — expand the data points first, then compare with the gateway capacity: data points below the gateway capacity, with enough margin — capacity is verified by data points.
In one sentence: gateway capacity is counted by data points = 2000 data points is roughly 400-600 monitoring points — estimating by monitoring points is a misconception — expand the data points, then compare the capacity.
A capacity example: a project had 500 monitoring points, expanding to 2400 data points — the 2000-point gateway was insufficient — replaced with a 4000-point gateway. Capacity misestimation mostly comes from "counting by monitoring points" — data points are the real consumption — expand, then compare the capacity, and you will not make a mid-project purchase.
7. The Margin Factor and Unifying the Quoting and Contract Basis
The meaning of margin — leave margin in capacity: future measurement points, feature expansion — the margin factor is generally 1.2-1.5; The calculation of margin — estimated data points × margin factor = planned capacity — without enough margin, expansion is limited; Unifying the contract — write the basis into the contract: priced by data points, capacity verified by data points — the basis written into the contract; The implementation of quoting — note the basis on the quotation: data-point unit price, expansion method — implementation matches the quote, with no dispute.
In one sentence: margin and contract = capacity with a 1.2-1.5 margin + the basis written into the contract + the quotation noting the expansion method — with a unified basis, no dispute.
A contract example: a contract stated "priced by data points, monitoring points expanded 3-5 times, capacity with a 1.3 margin" — implementation without dispute. Write the basis into the contract and the account is settled — data-point pricing, the margin factor and the expansion method in black and white — implementation without dispute.
8. Back to FEXLINK: How the ESX Gateway Is Configured by Data Points
The ESX intelligent edge gateway verifies capacity by the data-point basis: monitoring points expand into data points, with enough margin — quoting and implementation unified. The checklist: ① count the monitoring points first — devices/measurement points by physical position → ② expand the data points — telemetry + digital signals + cumulative quantities item by item → ③ verify the registration points — platform objects + measurement points in comparison → ④ compare the gateway capacity — data points + margin factor (1.2-1.5) → ⑤ write the basis into the contract — priced by data points, the expansion method noted — the three bases calculated, quoting and capacity right the first time.
One summary: the three bases of point estimation = monitoring points (counting devices) + data points (expanded telemetry/digital/cumulative) + registration points (platform objects + measurement points) — quoting and capacity by the data-point basis, usually 3-5 times the monitoring points — with a unified basis, the account is clear. A point is not "one measurement point, one number" — one measurement point expands into multiple data — distinguish the three bases, and the quote does not lose and the capacity does not squeeze.
One reminder: before quoting, do not rush to quote the unit price — define the basis first: is this order quoted by monitoring points, data points or registration points? What is the expansion factor? How much margin? — after the four questions, the basis is clear. Without a defined basis, quoting is gambling — unify monitoring points, data points and registration points first — quote accurately, install without overflow and dispute-free.
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 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
Estimating Project Point Count
When quoting a solution, how should the data points be priced per point — estimating too high or too low both lose — how is the basis defined