Power-factor logging is more useful when the report separates the phase-displacement question from waveform-distortion evidence. A single dashboard value can be a useful signal, but it does not identify the electrical boundary, the operating condition, or whether a reactive-power or harmonic-current question is being reviewed.
For broader planning context, begin with the reactive power compensation guides. This page describes a recordkeeping method; it does not promise a correction result, device size, or compliance outcome.
Direct answer
Keep displacement PF, total PF where displayed, harmonic-current evidence, and operating-state notes in one named record set. The comparison becomes reviewable when every value points back to the same electrical location and time window.
Part 1. Name the electrical question before logging PF
Write the purpose before configuring the trend. The team may be reviewing reactive-power behavior, comparing a feeder across shifts, documenting harmonic-current evidence, or preparing an inquiry. These are related but different questions, so the record must state which decision it is intended to support.
Mark the meter position, CT orientation, voltage reference, time basis, and responsible reviewer on a one-line diagram. A number from a local drive input does not automatically describe a process feeder or a supply-side boundary.
Important: Do not convert one low PF display into an equipment instruction. The electrical objective, assessment boundary, and acceptance method must be defined together (IEEE 519 reference context).
| Question being reviewed | Record to retain | Boundary note |
|---|---|---|
| Reactive-power behavior | PF trend, voltage, current, load state | Name the feeder or bus. |
| Harmonic-current behavior | Individual or aggregate harmonic record, meter settings | Keep it separate from a PF-only conclusion. |
| Combined power-quality review | Both record sets plus a one-line diagram | Explain how they relate at the selected point. |
Part 2. Keep displacement and distortion records distinct
The useful discipline is simple: label the field reported by the instrument and do not replace it with a generic phrase. If the meter provides a displacement-PF field, retain that field with its time window. Keep harmonic-current or waveform records in their own column or attachment, rather than assuming they have the same cause or mitigation path.
This does not require a long theoretical report. It requires enough metadata that an engineer can see what was measured and avoid comparing unlike values. The related power-factor and harmonic-distortion decisions guide can help frame the objective before an inquiry.
| Record field | Keep beside it | Do not infer |
|---|---|---|
| Total PF display | Instrument label, time window, and meter location | That one displayed value identifies the cause. |
| Displacement PF field | Operating condition and voltage/current reference | That it describes waveform distortion. |
| Harmonic-current export | Units, orders or summary, and capture settings | That it is a reactive-power calculation. |
| Switching state | Capacitor, filter, bypass, and transfer state | That a switching event is representative operation. |
Part 3. Log the operating state beside the values
An unlabeled trend loses much of its value when the production state changes. Log the line condition, major drives, rectifiers, UPS loads, process speed, starts, stops, bypasses, and changes in capacitors or other installed equipment. A short, consistent shift log is more useful than a large archive of screenshots with no time or load annotation.
When comparing two periods, retain the same meter configuration and boundary where practical. If the boundary changes, label the records as separate scenarios. The THD and TDD measurement context article explains why denominator and operating state must travel with a current-distortion record.
Part 4. Place the meter at the decision boundary
Locate the record at the electrical point that matches the decision. A local input can support local diagnosis, while a feeder location can show the combined effect of multiple loads.
A common boundary can support a wider assessment discussion. Because each location includes a different set of circuits, draw and name it rather than assuming it.
| Location question | Documentation to keep | Review use |
|---|---|---|
| What does one drive group contribute? | Local feeder identity, CT location, running state | Local investigation. |
| What is happening on the process feeder? | One-line location and coincident loads | Feeder comparison. |
| What is the supply-side question? | Defined common boundary and responsibility | Project-level review. |
The NEMA MG 1 resource provides general motor-system context. It does not define a site measurement boundary or certify a mitigation result.
Part 5. Link the records to an appropriate review scope
Treat the measurement set as evidence for a scope discussion, not as a direct product order. A reactive-power objective may require one set of questions, while a harmonic-current objective may require another. If both are present, keep their records separate until the project team defines how they will be assessed.
The Static Var Generator product context page is a CNBYG starting point for a defined reactive-power review. It does not guarantee a PF value, energy result, or performance outcome. A harmonic-current review may require different evidence and a different engineering path.
Part 6. Send a two-objective measurement package
Send a compact package that preserves the distinction between records. This makes a supplier or engineering review more efficient without implying that a general article has selected equipment.
| Buyer should provide | Why it matters |
|---|---|
| One-line diagram and nominal system details | Defines the selected boundary and supply context. |
| Meter, CT, and voltage-reference positions | Lets the reviewer locate each record. |
| Total and displacement PF exports where available | Preserves the instrument fields rather than a paraphrase. |
| Harmonic-current exports and meter settings | Keeps waveform evidence distinct from PF fields. |
| Operating-state log and load inventory | Connects electrical data to the plant condition. |
| Existing equipment, installation limits, and acceptance requirements | Defines integration and project boundaries. |
CNBYG can discuss product-line fit after the objective and evidence package are defined. Use the separate measurement records to begin that conversation; this guide cannot replace a network study or project acceptance process.
Frequently asked questions
What is displacement power factor?
It is a reported power-factor field that should be read with the instrument configuration, electrical location, and operating state. Keep the original meter label in the record.
What is distortion power factor?
It is a separate waveform-related consideration. Keep harmonic-current evidence and its capture settings alongside the PF record rather than treating every number as the same index.
Why should they be logged separately?
Separate logs make it clear which electrical question each record addresses. This prevents a reactive-power observation from being presented as a harmonic-current conclusion, or the reverse.
Does a low PF display identify one solution?
No. The project still needs a defined boundary, operating record, stated objective, installation scope, and acceptance method before a product discussion.
Where should the record be taken?
Take it at the electrical point that matches the decision, then mark the meter, CT, and voltage reference on the one-line diagram.
What belongs in a PF and harmonic inquiry?
Provide the one-line diagram, nominal data, measurement setup, PF fields, harmonic exports, operating log, load inventory, existing equipment, and installation constraints.
References
