Unit Converters
For logger analysts, commissioning teams, and operations engineers, convert one ordered power channel, preserve record lineage, integrate equal-duration readings into energy, and identify threshold periods for review. Every accepted record must share the same meaning and interval duration; irregular timestamps require a different integration model.
Power records
Ordered logger conversion
Convert an ordered series of comparable power readings, preserve each record, calculate summary statistics, integrate a common reading interval into energy, and flag a declared review threshold. It is designed for logger exports and repeated test points, not mixed-unit datasets.
Input evidence: keep logger timestamps, channel identity, averaging mode, common sample duration, quality flags, and meter multiplier.
| Record | Entered power | Converted power | Interval energy | Threshold |
|---|
Energy accumulation
The cumulative trace answers a different question from the power profile: where in the ordered run the energy exposure was added.
| Scenario or component | Basis | Calculated value | Decision use |
|---|
How to use
Inspect logger metadata before pasting values. The channel must have one unit, one record meaning, and equal durations with no clock changes, duplicated rows, or missing intervals; otherwise the batch total will weight records incorrectly.
A sampled value may represent an instant, average, or demand window; the meaning controls energy integration.
The calculator assigns the same duration to every accepted row.
Energy totals use full-precision converted power.
A row count identifies exposure frequency, not severity duration beyond the entered interval.
Index position remains connected to the source export.
Result interpretation
Minimum, maximum, range, and mean describe the converted power records; they do not by themselves include time. Row and batch energy additionally assume every accepted reading is an interval-average power representing the same entered duration. The threshold count identifies records for review while the cumulative view shows where their energy contribution occurred in acquisition order.
A zero range means identical retained values on the calculation basis, not a proof that the underlying process never varied inside each interval. A high threshold count can reflect a sustained state rather than isolated spikes. If the logger values are snapshots or maxima, treat the integrated energy as invalid until the sampling meaning is resolved.
Every reading crosses the watt reference and is multiplied by the shared hours-per-row to obtain row energy.
Missing intervals must not be silently represented by the preceding reading.
A 15-minute utility demand value may already be an average and should be integrated using its exact window.
Document whether the flag belongs to operations, asset protection, energy management, or billing analysis.
Sampling semantics
Energy integration requires interval-average power or another value explicitly defined to represent the whole window. An instantaneous snapshot may miss cycling between samples, while an interval maximum deliberately overstates the average if multiplied by the full duration.
Confirm the aggregation mode in logger configuration, historian tags, or meter documentation. When only snapshots exist, use a validated reconstruction or higher-frequency data. When values are demand-window averages, multiply each by that exact window and avoid applying an additional averaging factor.
Timestamp discipline
A logger export should retain timestamps, timezone, sequence identifiers, and quality flags. Daylight-saving changes, clock drift, dropped packets, duplicated rows, communications retries, and substituted values can bias integrated energy even when unit conversion is correct.
Reconcile expected versus accepted record count and compare timestamp differences with the entered common duration. Split or repair the batch when intervals vary. Never silently fill a gap with zero or carry the preceding value forward unless the governing method explicitly authorizes that treatment.
Threshold governance
A threshold may represent an alarm, contractual limit, capacity trigger, demand-management target, or simple investigation line. The same numeric crossing can therefore imply very different actions and should not be labeled failure automatically.
Document beneficial direction, treatment of equality, whether measurement uncertainty or persistence is considered, the minimum number of consecutive crossings, and the responsible owner. Use the row ledger to identify timestamps, then apply the separate operating or conformity procedure that gives the flag meaning.
Visual reading guide
The ordered bars retain record-level converted power, mean context, and threshold crossings. The second view accumulates row energy in the same sequence. Isolated tall bars expose high-power records, while a steeper sustained staircase reveals periods contributing most to total energy.
Changing unit rescales power labels without changing relative shape; changing row duration changes energy slope but not bar height. The display assumes equal windows, so irregular timestamps, mixed aggregation modes, or reordered records make the staircase misleading even if every bar is numerically valid.
Pᵢ,t = Pᵢ,s Fs/Ft; E_batch = ΣPᵢ,t × Δh / 1000
Pᵢ is each ordered power record, F is watts per unit, Δh is hours represented by one row, and E is kWh.
| Pᵢ,t | converted row power | target unit |
| Δh | common row duration | h |
| Eᵢ | row energy | kWh |
| Nflag | rows above threshold | count |
Energy check:
Default-value audit
Defaults: 4.2, 5.1, 6.4, 5.8, 7.3 and 6.1 kW; target kW; 15 minutes per record; threshold 6.5 kW.
| Symbol | Meaning | Unit | Default role |
|---|---|---|---|
| Pᵢ,s | Source power record i | kW | Six entered values |
| Fₛ, Fₜ | Source and target watt factors | W/unit | Both 1,000 |
| Pᵢ,t | Converted record i | kW | Source × Fₛ/Fₜ |
| N | Valid record count | record | 6 |
| Δt | Duration represented per record | h | 0.25 |
| P̄ | Arithmetic mean power | kW | ΣPᵢ,t ÷ N |
| Eᵢ | Energy represented by row i | kWh | Pᵢ,tΔt |
| EΣ | Batch energy total | kWh | ΣEᵢ |
| T | Review threshold | kW | 6.5 |
Integration check: summing all row energies equals the power-record sum multiplied by 0.25 hour.
Logger evidence
Keep timestamps, channel and asset identity, unit, averaging mode, interval duration, timezone, clock-change behavior, meter multiplier, scaling revision, missing-value code, substitution method, and quality flag. Freeze the source definition before conversion.
Reconcile expected and accepted record counts, represented duration, unit factor, and final energy to the source historian or meter total when available. Investigate mismatches before interpreting thresholds. Retaining only the pasted numbers makes it impossible to distinguish genuine operation from acquisition defects.
Limits and exclusions
The model does not infer unequal durations, interpolate missing records, distinguish snapshots from averages, convert apparent power, correct power factor, remove spikes, estimate measurement uncertainty, or determine a conformity rule. Mixed channels, units, multipliers, and record definitions must be separated first.
Consequently, do not use its energy total for billing, emissions, compliance, or settlement when acquisition integrity is unresolved. Use timestamp-aware integration for irregular intervals and a governed data-quality process when substitution, clock repair, or uncertainty could change the reported quantity.
Batch-power glossary
Worked cases
Inputs: 4.2, 5.1, 6.4, 5.8, 7.3 and 6.1 kW interval averages with a common 15-minute duration and 6.5 kW review line.
Calculation: multiply each row by 0.25 hour; total energy is 8.725 kWh and two rows exceed the review line.
Decision: reconcile the final staircase to the historian’s interval-energy total and investigate the timestamps attached to 7.3 kW and any other governed crossing.
Inputs: 4, 7 and 5 kW interval averages representing 5, 20 and 40 minutes respectively.
Calculation: timestamp-aware energy is 0.333 + 2.333 + 3.333 = 6.000 kWh. Applying one incorrect 15-minute duration to all three would report only 4.000 kWh, understating energy by 33.3%.
Decision: reject the common-duration result and integrate one duration per record. Preserve the timestamps and reconciliation difference as evidence of why the batch needs a different model.
Do not integrate instantaneous samples as if they were interval averages unless the sampling and reconstruction method supports that assumption.
Frequently asked questions
Each value represents a separate ordered logger record. The calculator converts and audits every row, then summarizes the batch without pretending that the mean, threshold count, or total belongs to one individual record.
The detailed ledger contains each record's converted power, represented row energy, and threshold status. Summary cards such as mean, extrema, total energy, and count describe the entire accepted batch.
Yes, and the unit conversion and one-row energy can still be calculated. Range, variation, ordering, and threshold frequency then provide almost no evidence because only one observation exists.
Yes for this model because one entered duration is applied to every row. If timestamps differ, use a timestamp-aware integration that assigns the correct duration to each interval or segment.
No. Paste only the numeric channel in acquisition order, but retain timestamps and quality flags in the source record. Reconnect any reviewed row to its timestamp using the preserved record index.
No. Mean is a power rate. Batch energy equals the sum of row power multiplied by row duration; changing duration changes energy while leaving the converted mean power unchanged.
No. Sorting destroys the acquisition sequence and hides gaps, ramps, and event timing. Numerical ordering may be used temporarily for a statistic, but the displayed ledger and cumulative energy should retain source order.
No. It identifies a record beyond the entered review boundary. Failure requires a documented decision rule that defines direction, equality, persistence, uncertainty treatment, and the action assigned to a crossing.
Stop using the common-duration energy total. Apply timestamp-aware integration using one duration per valid interval, define how gaps and duplicate timestamps are handled, and reconcile the result to an independent source total.