Measures
The Measures feature allows you to capture, aggregate, and statistically analyze process measurements at scale. Rather than storing every raw sample, measurements are collected over a configurable window — by count or by duration — and summarized into a single database record that preserves key statistical properties.
How It Works
A measure is backed by a Tag UDT that collects incoming values in memory. Once the configured window is complete, the UDT computes a statistical summary and writes one aggregated record to the database.
Collection Window
You configure the window in one of two ways:
| Mode | Description |
|---|---|
| Sample count | Collect exactly N values, then aggregate |
| Duration | Collect all values over a time period (e.g. 5 minutes), then aggregate |
Aggregated Output
Each record (measure event) written to the database includes:
| Field | Description |
|---|---|
measureValue | Average of all samples in the window |
stdDev | Standard deviation of the samples |
minValue / maxValue | Observed range |
sampleCount | Number of raw values collected |
durationSecs | Seconds from the first sample to the last |
The SPC result isn't stored with the record: it's on the measure's tags (outOfControl and ruleViolations, see SPC Rules).
Use Cases
High-Frequency Sensors
A vibration or temperature sensor sampling at 100 Hz would generate millions of rows per day if stored raw. With a count-based window of 500 samples, storage is reduced 500× while retaining the statistical shape of the signal.
Shift or Batch Summaries
Use a duration-based window aligned to your shift length (e.g. 8 hours). Each shift produces one measure record capturing the process behavior for that period — suitable for OEE dashboards and trend reporting.
SPC Without Raw Data Retention
Each recorded event is one point on the measure's control chart. After every record, the UDT checks the latest events against the measure's configured control limits and sets its out-of-control flags, so you get SPC on the process without storing the raw samples.
Centerlining
Measures can be linked to a quality attribute (attributeId) from the attribute specification table. This allows a measure record to be compared against a golden-run baseline, supporting centerlining workflows where you want to know how far the current window deviates from optimal settings.
Multi-Asset Rollups
Deploy the same UDT across many assets. Because each record includes sampleCount, downstream aggregation (e.g. plant-wide averages) can be properly weighted rather than treating each window as a single data point.
Creating a Measure Definition
Measures can be defined in the Configuration/Ops/Measures page as well as via the measures api's.

Measures require a name and an asset to be linked with. Data sources for where the measurement comes from i.e. PLC, can be configured and linked. Aggregations can also be defined and linked to determine whether the measurement is an average value, sum etc.
If SPC analysis is required to be performed on the measurement (requires a quality license), an attribute containing spec limits can be linked to the measurement. This enables centerlining comparisons in downstream reporting.
Creating the Measures Tag
By enabling the 'Tag' checkbox, a measure UDT instance will be created in a measures tag folder under the asset. This provides the ability to connect the data source to the measurement value tag.
The Measure tag UDT instance has the following settings:
| Parameter | Type | Description |
|---|---|---|
measureId | int | ID returned by the addMeasure() function |
maxSampleCount | int | # of measurement to collect before storing the measurement |
maxSampleDurationSecs | int | # of seconds between samples before storing the measurement |
outOfControl | bool | Set when the SPC check finds an out-of-control condition in the latest spcPoints recorded events |
ruleViolations | array | The violated rules' keys (for example WE4_8_same_side), from the same check |
spcCheckEnabled | bool | Set to true to enable the SPC check |
spcPoints | int | How many of the latest recorded events the SPC check and the Measure SPC Analysis chart use. Default 30 |
enabled | bool | Set to true to enable this measure |
update | bool | Set to true to store this measurement value ibn the database. This is automatically enabled when either the 'maxSampleCount' or 'maxSampleDurationSecs' threshold is reached |
value | float | This is the measurement value. Wire the UDT's value input to the tag you want to measure. The UDT will begin collecting values immediately when enabled is true. |
data | dataset | The samples collected for the next record. They're averaged into the record and cleared each time it's written |
spec | folder | Contains measure specification if applicable |
spec/attributeId | int | Id of the attribute linked to this measure |
spec/itemId | int | Id of the item currently linked with this measure |
spec/refresh | int | Updates the specification based on the attributeId, itemId, and assetId |
spec/lsl | int | Attribute spec lower spec limit |
spec/lcl | int | Attribute spec lower control limit |
spec/tgt | int | Attribute spec target |
spec/ucl | int | Attribute spec upper control limit |
spec/usl | int | Attribute spec upper spec limit |
SPC Rules
Each time a measure records an event (with spcCheckEnabled set), the UDT runs spcCheck() on the latest spcPoints recorded events, with both rule sets, and writes outOfControl and ruleViolations.
The events are judged against the measure's configured control limits: spec/ucl and spec/lcl from its linked attribute, centered on spec/tgt. These are the limits the Measure SPC Analysis chart draws, so the flags and the chart always agree. Sigma for the zone rules is (UCL - LCL) / 6.
If the measure has no configured UCL/LCL, the control limits are computed from the recorded events themselves. That's only meaningful once there are enough of them (20-25 or more) from a period when the process was stable, so configure the limits wherever you can.
Points on the same side of the target are a real signal, even inside the limits: a process that sits above its target trips the "on one side" rules.
The Label column is how the rules are shown in the Measure SPC Analysis popup and the notifications widget (from getRuleInfo()).
Rule Sets
| Value | Description |
|---|---|
'western_electric' | Western Electric rules only |
'nelson' | Nelson rules only |
'both' | Both rule sets combined (default) |
Western Electric Rules
| Rule | Label | Description |
|---|---|---|
WE1 | Beyond 3σ | 1 point beyond 3σ |
WE2 | 2 of 3 beyond 2σ | 2 of 3 consecutive points beyond 2σ on the same side |
WE3 | 4 of 5 beyond 1σ | 4 of 5 consecutive points beyond 1σ on the same side |
WE4 | 8 on one side | 8 consecutive points on the same side of the center line |
WE5 | 6 trending | 6 consecutive points trending in one direction |
WE6 | 15 within 1σ | 15 consecutive points within 1σ of the center line |
Nelson Rules
| Rule | Label | Description |
|---|---|---|
N1 | Beyond 3σ | 1 point beyond 3σ |
N2 | 9 on one side | 9 consecutive points on the same side of the center line |
N3 | 6 trending | 6 consecutive points trending in one direction |
N4 | 14 alternating | 14 consecutive points alternating up/down |
N5 | 2 of 3 beyond 2σ | 2 of 3 consecutive points beyond 2σ on the same side |
N6 | 4 of 5 beyond 1σ | 4 of 5 consecutive points beyond 1σ on the same side |
N7 | 15 within 1σ | 15 consecutive points within 1σ of the center line |
N8 | 8 outside 1σ | 8 consecutive points with none within 1σ of the center line, on both sides of it |
A point beyond a control limit is also reported as Above UCL / Below LCL, and beyond a spec limit as Above USL / Below LSL.
Chart Types
| Value | Description |
|---|---|
individuals | Individuals/moving range chart. Used when each measurement is a single value. Default. |
xbar | X-bar/range chart. Used when measurements are grouped into subgroups of 2–10 samples. Requires subgroupSize. |
Use individuals for most sensor and manual entry scenarios. Use xbar when your process naturally produces batches of samples (e.g. 5 parts per cycle) and you want to track subgroup means.
Real-time SPC
A measure can check its process as it runs: each time it records an event, it judges the latest events against the SPC rules and flags the measure when they break one. Operators see the alert on their dashboard straight away, and can open the chart behind it.
Measures are part of Kanoa Ops: without an Ops license (or trial), a measure keeps its samples but records no events. The real-time SPC check uses Kanoa's SPC functions, which are part of Kanoa Quality. Without a Quality license (or trial), measures still record their events, but the check doesn't run: outOfControl and ruleViolations keep their last values, no new alerts appear, and the gateway log says why (at most once an hour).
Turning It On
On the measure's tag (see Creating the Measures Tag):
- Set
spcCheckEnabledtotrue. - Set
spcPointsto how many of the latest events to judge (30 by default). - Link the measure to an attribute with control limits (UCL and LCL) and a target, so the events are judged against the limits you set rather than limits computed from the events themselves.
Each recorded event then writes outOfControl and ruleViolations on the measure's tag.
SPC Alerts on a Dashboard
The Event Notifications widget shows SPC alerts alongside downtime, quality check and tooling notifications. It lists every measure on its asset, or on any asset below it, that is out of control, naming the rules it broke (for example "8 on one side, 6 trending"). It checks every 5 seconds, so an alert shows almost as soon as the event that caused it is recorded.

To add it:
- Open the Dashboard Editor and select the dashboard, for example the line's operator dashboard.
- Add the Event Notifications widget, from the Notifications category (see Adding Widgets to a Dashboard).
- Point it at the asset to watch: set its
assetPathparameter, or leave it empty to follow the dashboard's asset selector. A line or area shows the measures of every asset under it.
Measure SPC Analysis
Clicking an out-of-control measure in the Event Notifications widget opens the Measure SPC Analysis popup.

- Chart: the latest
spcPointsrecorded events (one point per record), against the measure's limit lines (LSL, LCL, Target, UCL, USL), with the samples still being collected for the next record drawn after them in gray. It updates each time an event is recorded, so it doesn't clear between records. - Highlighted points: every point in a violating run is marked in the color of its kind (a point in several runs takes the most serious): red for beyond a limit, orange for a shift or drift pattern, blue for too little variation.
- OUT OF CONTROL: shown when the check finds any violation.
- Violations: one pill per violated rule, colored by kind, with its readable label. Hover a pill to see what the rule means. The legend under the pills explains the colors.
The popup runs the same check as the measure's tags, on the same points and limits, so what it shows always matches outOfControl and ruleViolations.
Measures Analysis
The Measures Analysis view provides a multi-chart breakdown of aggregated measure data over a selected time range. It is designed to surface trends, distribution patterns, hourly variation, and sample count anomalies in a single screen.

Filters
| Filter | Description |
|---|---|
| Measure | Asset-scoped measure to analyse (e.g. BDFT Kanoa Box Co\Box Plant\Packaging\Box Line 1) |
| Date range | Preset (Last Week, Last Month, etc.) or custom start/end timestamps |
| Granularity | Day / Shift / Hour — controls how rolling averages and hourly charts are bucketed |
Click Go to apply filters. Click Clear to reset to defaults.
KPI Summary Cards
Four summary cards appear at the top of the view.
| Card | Description |
|---|---|
| Avg Measure Value | Mean of all aggregated values in the selected range. Min and Max show the observed extremes across all events. |
| Total Samples | Sum of sampleCount across all events. Also shows total event count and average samples per event. |
| Avg Std Dev (within sample) | Average of the per-event standard deviation. Reflects within-window process variation. The between-event figure shows variation across events. |
| Avg Duration (secs) | Average collection window duration in seconds, with the full date span of the query shown beneath. |
Example
From the screenshot above (06/14/26 – 06/21/26, Box Line 1):
- 100.02 avg value across 532,439 total samples (5,932 events, ~89.8 samples/event)
- 8.9647 avg within-sample std dev, with a between-event std dev of 3.6711
- 100.6 s avg window duration
Charts
Measure Value with Rolling Average
A time-series scatter plot of every aggregated event value over the selected range. A rolling average line is overlaid to show the process trend.
Use this chart to:
- Identify drift or step changes in the process mean over time
- Spot isolated outlier events against the rolling trend
- Confirm process stability across shifts or days
Avg / Min / Max Value by Hour of Day
A bar + line combo chart grouping all events by hour of day (0:00–23:00). Bars show the average value per hour; lines show the min and max observed in that hour across the full date range.
Use this chart to:
- Detect time-of-day patterns (e.g. startup variation, shift changeover effects)
- Identify hours where the max consistently exceeds spec
- Compare average vs. worst-case behaviour by hour
Measure Value Distribution
A histogram bucketing all events by their aggregated value. Each bar shows the event count falling within that value range (e.g. 95–100, 100–105).
Use this chart to:
- Confirm the process is centred on the target value
- Identify skew or bimodal distributions that suggest a mixed process
- Quickly see how many events fall outside expected ranges
Sample Count Outliers by Event Time
A bar chart of sampleCount per event over time. Events where the sample count deviates significantly from the typical range are visually prominent as outliers.
Use this chart to:
- Identify events where the collection window captured an abnormal number of samples (sensor bursts, window timing issues)
- Spot gaps where sample counts drop unexpectedly (e.g. downtime, tag disconnection)
- Validate that window configuration is behaving consistently
A sudden spike in sample count (as visible in the example above around 06/16–06/17) can indicate a window that failed to flush on time and accumulated extra samples before writing. Cross-reference with the rolling average chart to see whether the value was also affected.
Outliers (z-score > 2)
A paginated table listing every event where the aggregated value deviated more than 2 standard deviations from the process mean.
| Column | Description |
|---|---|
| Timestamp | Date/time of the event |
| Value | Aggregated measure value for that event |
| Mean | Process mean across the selected range |
| Std Dev | Process standard deviation across the selected range |
| Z-Score | How many standard deviations the value is from the mean |
| Direction | High — value above the mean, Low — value below the mean |
Rows are sorted by Z-Score descending, so the most extreme outliers appear first. Rows highlighted in orange indicate events that also exceeded the USL or LSL.
Use this table to:
- Identify the most extreme process excursions and when they occurred
- Distinguish high-side from low-side outliers
- Drill into specific dates for root cause investigation
Gap Analysis
A paginated table showing the time gap between consecutive events, flagging windows where the gap was larger than expected.
| Column | Description |
|---|---|
| Timestamp | Date/time of the current event |
| Prev Timestamp | Date/time of the preceding event |
| Gap (secs) | Elapsed time between the two events |
| Status | Normal — gap within expected range, Large Gap — gap significantly exceeds the typical window duration |
Use this table to:
- Detect periods where measurement collection stopped or stalled (downtime, tag disconnection, network issues)
- Validate that the collection window is flushing consistently
- Identify missing data before using the analysis for reporting or compliance
A Large Gap alongside a spike in the Sample Count Outliers chart on the same date often indicates the window paused and then flushed a backlog of samples in a single event when collection resumed.