A SCADA analog is correct only when the complete measurement chain uses the same reference, ratio, unit, sign, range and time meaning. A believable number can still be wrong by a CT/VT ratio, 1000× unit conversion, reversed power direction, Modbus word order or duplicated scaling. Deadbands then determine what changes operators and historians actually see.
This guide engineers MV current, voltage, frequency, power, power factor, demand and energy from sensor/IED through IEC 61850, gateway and IEC 104/DNP3/Modbus to the control center.
1. Document the measurement chain
- Primary current/voltage/power system quantity.
- CT/VT or sensor ratio, phase/polarity and accuracy/burden.
- IED sampling/calculation, primary/secondary setting and filtering.
- IEC 61850 data object/attribute, scale/unit and quality.
- Gateway canonical value and protocol conversion.
- Control-center raw/scaled database value, display and historian.
- Alarm/automation calculation consuming the value.
Assign scaling ownership once. If the IED publishes primary amperes, the gateway must not apply the CT ratio again.
2. Minimum analog point fields
| Field | Required definition |
|---|---|
| Quantity | Phase/residual I or V, frequency, P/Q/S, PF, energy, demand, temperature |
| Reference | Primary or secondary; phase-neutral/phase-phase; per-phase/three-phase total |
| Unit | A, kA, V, kV, Hz, kW/MW, kvar/Mvar, kWh/MWh, °C, etc. |
| Range | Engineering min/max, valid operating range, sensor/IED overload behavior |
| Encoding | Integer/normalized/scaled/float, sign, resolution, byte/word order |
| Transformation | Multiplier, offset, ratio and exact equation/location |
| Reporting | Deadband, minimum/maximum update and integrity/cyclic interval |
| Quality/time | Invalid/out-of-range/overflow/stale rules and timestamp origin |
3. Scaling equation and ownership
For a simple linear conversion, engineering value = raw value × multiplier + offset. Normalized/scaled protocol values may instead map an integer range to engineering limits. Record the exact equation, data type, rounding and overflow behavior at the one layer that owns it.
- Verify CT/VT primary and secondary settings against nameplates/drawings.
- Confirm relay values are already primary or secondary.
- Use unit metadata consistently; do not infer kV versus V from tag names.
- Avoid integer truncation before multiplying or dividing.
- Define rounding and significant digits from actual accuracy/resolution.
- Detect saturated/clipped/overflow values rather than displaying the limit as healthy.
4. Protocol representations
| Protocol/model | Engineering concern |
|---|---|
| IEC 61850 | Measured-value magnitude, units/multiplier, quality and report deadband behavior |
| IEC 104 | Normalized/scaled/short-float type choice, quality descriptor and time tag |
| DNP3 | Static/event object variations, integer/float range, flags and deadband |
| Modbus | Register address, signed/unsigned/float, byte/word order, scale and no native unit/quality model |
Select the target representation from required range/resolution and master support. A 16-bit scaled value may be adequate for temperature but inappropriate for cumulative energy or wide-range current.
5. Power, reactive power and power factor signs
- Define positive P as import/load or export/generation for every bay type.
- Define Q sign convention and inductive/capacitive meaning.
- Confirm CT/VT polarity and phase rotation before changing software signs.
- Specify three-phase total versus per-phase quantities.
- Define PF sign/quadrant behavior around zero power; avoid unstable misleading PF alarms.
- Use primary injection/known phase-angle test to prove P/Q direction.
- Ensure HMI arrows/colors and historian calculations use the same convention.
6. Deadband design
Deadband suppresses insignificant changes to control event/bandwidth load. It should exceed noise/resolution yet remain smaller than the minimum operationally meaningful change. Define absolute or percentage basis and whether comparison is from last reported value, zero or full scale.
- Use quantity-specific deadbands; frequency needs a different threshold from feeder current.
- Do not use a percentage of instantaneous value that collapses near zero unless intentionally defined.
- Apply at one known layer; cascaded IED/gateway/master deadbands add blind zones.
- Separate reporting deadband from alarm threshold/hysteresis.
- Preserve quality-change reports regardless of numeric deadband.
- Provide periodic integrity/cyclic refresh where the operational design requires it.
7. Update rate, filtering and timestamp
- State RMS/fundamental/average/demand calculation window and update rate.
- A fast display update does not mean a fast measurement if the source filter is slow.
- Use source timestamp where meaningful; identify sampled/calculated interval.
- Coordinate report buffer time, deadband and HMI scan so latency remains acceptable.
- Avoid sending protection-rate process data to supervisory SCADA without an operational need.
- For post-fault values, use disturbance records rather than relying on slow SCADA analogs.
8. Quality, stale and out-of-range handling
- Map invalid, questionable, overflow, out-of-range, bad reference, failure, old data, test and substituted states.
- Do not display a clipped maximum as healthy.
- On communication loss, retain last value for context but mark it stale/invalid.
- Define sensor reference-loss and zero-current conditions separately.
- Block control/automation that relies on invalid measurements unless a tested fallback exists.
- After restoration, revalidate with a fresh source update/interrogation.
9. Counters, demand and energy
- Use sufficient integer/float range for lifetime energy and operation counts.
- Define rollover, reset, freeze and power-loss retention.
- Record import/export and delivered/received energy separately where required.
- Specify demand interval, sliding/fixed window and reset time.
- Do not apply analog deadband blindly to cumulative counters.
- Test gateway/master restart without counter jump, double count or lost increment.
- Preserve meter/IED source authority and calibration traceability.
10. Capacity and event-storm control
- Estimate normal change reports across all bays and worst disturbance/reconnect bursts.
- Stagger periodic integrity/cyclic scans.
- Prioritize discrete protection/breaker events over non-critical analog refresh.
- Measure IED/gateway/server/report queue behavior and dropped/coalesced updates.
- Alarm buffer/queue overflow and maintain usable controls during a flood.
- Review deadbands after commissioning using measured noise and operator needs.
11. FAT/SAT test matrix
- Freeze CT/VT ratios, IED settings, point map, protocol types and master database.
- Inject zero, nominal, negative/sign, upper range and over-range values.
- Verify primary/secondary reference, units, phase, per-phase/total and resolution.
- Test Modbus word/byte order or protocol integer/float limits where applicable.
- Step just below/above deadband in both directions; verify periodic refresh.
- Change quality without value and test stale/communication/reference failure.
- Verify P/Q/PF quadrants with controlled phase angle.
- Test counter rollover/reset/retention and energy direction.
- Run all bays at worst update/event/reconnect load.
- At SAT, use traceable secondary/primary injection and compare IED, gateway, HMI and control center.
- Record applied value, expected uncertainty, every layer’s reading and final error.
12. Acceptance rule
Define total allowed error from sensor/transformer, IED, conversion, data type and test instrument. The SCADA result should agree within that budget across the required range; decimal formatting must never imply more accuracy than the chain provides.
References and further reading
- IEC 61850-7-3 consolidated edition — Measured-value and quality data classes
- IEC 61850-7-4 consolidated edition — Logical-node/data-object models
- IEC 61850-8-1 consolidated edition — MMS reporting mapping
- IEC TS 61850-80-1:2016 — Mapping to IEC 101/104
- IEC 60870-5-104 consolidated edition — Telecontrol measured values
- Modbus Organization — Official application protocol specification
Engineering note: Scale once, state the unit explicitly, prove sign and range by injection, and set deadband from measured noise plus operational need.