Intermittent switching and harmonic observations become useful only when they can be traced to the same part of the electrical system. An intelligent compound switch log beside an APF should therefore preserve the controller action, stage state, measurement boundary, and operating condition rather than being treated as a result by itself.
For planning context, begin with the reactive power compensation guides. This page describes a record-review method; it does not diagnose a plant, confirm a device interaction, or promise a power-quality result.
Прямой ответ
Keep the compound-switch command, the observed capacitor-stage state, the electrical boundary, and the harmonic operating context in one dated record. Use the record to decide what needs review; do not use it as proof that an APF caused, removed, or prevented an event.
Part 1. Set the review question before reading the log
Start with one reviewable question, such as whether a named capacitor stage was commanded during a particular operating condition or whether a sequence changed after a controller setting was revised. A vague request to “check the switch and APF” gives a reviewer no way to decide which signals, time window, or comparison are relevant.
Write the question with a location and a time basis. For example, a project may want to compare a feeder record during a repeated process state, or it may want to check whether a commanded stage transition coincided with a source change. The question is not an APF acceptance criterion unless an acceptance method has separately been agreed.
| Review question | Record boundary | Evidence that answers it |
|---|---|---|
| Did a named stage receive a command? | Controller output and the identified stage | Command event, state indication, and clock reference |
| Did a transition occur under a comparable load state? | Selected feeder or bus | Operating log, electrical capture, and topology note |
| Did the record series change after a setting revision? | The same named control scope | Revision date, prior and new settings, and separate event groups |
The published intelligent compound switch basics article explains the component category. This page starts later in the decision path: it organizes evidence around a real system question.
Part 2. Mark the electrical boundary and the devices in scope
Unlike a controller screen, a record boundary states what the observation includes. Mark the meter location, CT orientation, voltage reference, bus or feeder name, capacitor-stage connection point, APF connection point, and any reactor or bypass arrangement on the one-line diagram. A stage command at one point cannot automatically describe current or voltage at another point.
Name the device roles without assuming they control one another. The compound switch may be part of a capacitor-stage sequence, while the APF is a separate item in the project scope. Their timestamps may be useful together, but a timestamp alone does not establish a causal relationship.
| Item to identify | Why the record needs it | What not to infer |
|---|---|---|
| Meter, CT, and voltage reference | Shows the electrical quantities included in the capture | That another feeder has the same load mix |
| Capacitor-stage connection point | Defines the stage under review | That every capacitor stage is identical |
| APF connection point and state source | Keeps APF records traceable | That APF state proves a switching cause |
| Reactor, bypass, or source arrangement | Discloses circuit context | That the topology stayed unchanged between events |
Важно: Harmonics in the supply can raise current through capacitors. The harmonic context and any reactor arrangement therefore belong beside a switching record, rather than being omitted from a controller export. (Руководство поэлектрооборудованию компании Schneider Electric)
Part 3. Keep command, stage state, and clock in one chronology
If a stage is commanded, retain both the command and the available indication of what happened afterward. Controller logic, feedback state, alarm state, and an electrical event export are different records; none should silently stand in for another. A chronology makes these distinctions visible to the next reviewer.
Place the clock source beside each export. If device clocks are not synchronized, disclose the known uncertainty instead of forcing the records into a false sequence. Also note shift, process condition, active drives, rectifiers, UPS loads, source transfer, maintenance, and any manual control action that could make events unlike.
| Chronology field | Preserve with the event | Стоимость просмотра |
|---|---|---|
| Command record | Stage identifier, command direction, and timestamp | Separates a requested action from an observed state |
| State indication | Available feedback or alarm state and timestamp | Shows what the controller reported afterward |
| Electrical capture | Meter configuration and capture window | Connects the event to a defined measurement method |
| Operating note | Process, major loads, and topology state | Prevents calendar time from becoming the only comparison rule |
Intelligent capacitor-bank control references show why controller information and measured-system information need to remain together. That context is not evidence that a particular site uses the same controller method.
Part 4. Compare switching records with harmonic operating context
Compare records by matched operating state rather than by two convenient dates. Group captures by similar process condition, supply arrangement, active nonlinear loads, capacitor-stage configuration, and meter setup. An apparent change can otherwise describe a different operating state instead of a change associated with switching.
Harmonic context belongs in the comparison even when the article is about a switch. The Schneider guide explains that harmonics can elevate capacitor current; its advice is system dependent, so this article does not assign a reactor, tuning point, or equipment rating. The useful action here is to disclose what the records show and what was not measured.
| Comparison check | Match or disclose | Decision that remains open |
|---|---|---|
| Measurement arrangement | Boundary, CTs, voltage reference, aggregation, and time basis | Whether the two periods are technically comparable |
| Operating condition | Process state, active load groups, source configuration | Whether a load change explains the observation |
| Harmonic evidence | Export type, event window, and relevant topology | Whether a mitigation study is needed |
| Switching configuration | Stage identifier, controller revision, bypass or reactor note | Whether product selection needs more project inputs |
For a complementary boundary discussion, see capacitor-switching resonance context. A resonance investigation needs its own engineering method and should not be collapsed into an ordinary log review.
Part 5. Keep APF evidence separate from capacitor-stage evidence
Switching chronology and APF evidence answer different questions. A stage command can document sequence and context; APF records, if available, should be labeled with their own objective, connection point, measurement setup, and acceptance method. Combining the two into a single “before and after” assertion can create a result claim without a controlled comparison.
Земля APF and capacitor coordination guide provides related planning context. It does not turn one logged sequence into a proof of harmonic mitigation, power-factor outcome, equipment compatibility, or plant acceptance.
Use separate labels in every report:
- Observed record: what was commanded, measured, or indicated at a named time and boundary.
- Working hypothesis: a question for follow-up, supported by comparable records rather than a single event.
- Project decision: a decision that requires drawings, site conditions, product documentation, protection review, and agreed acceptance criteria.
Ан AHF product context page can be relevant once a harmonic-current objective is defined. It should not be selected from a compound-switch log alone.
Part 6. Build a coordination record package for product review
Package original exports with enough context for a reviewer to reconstruct the question. For an RFQ or product review, the package should show the relationship between devices and records without presenting a site-specific conclusion that the evidence does not support.
| Send for review | What the reviewer can establish | Common gap to avoid |
|---|---|---|
| One-line diagram and nominal system description | Electrical boundary and device locations | Calling a local meter a whole-system record |
| APF and capacitor-stage locations | Which equipment is in scope | Assuming physical proximity proves coordination |
| CT and voltage-reference position | Measurement inclusion and polarity context | Exporting data without the measurement setup |
| Command, state, and alarm exports | Sequence seen by the controller | Treating a command as confirmed physical operation |
| Harmonic records and operating log | Conditions surrounding the observation | Comparing unlike shifts or load states |
| Reactor, protection, installation, and acceptance notes | Project constraints and review boundary | Requesting a product recommendation with no acceptance method |
When the record package defines the problem, use the BYFK composite-switch product context as a product-line starting point. Send a coordination record package when the exact circuit, records, and project constraints are ready for review.
Часто задаваемые вопросы
What is an intelligent compound switch record?
It is a dated record of a defined switching-control event together with the electrical location, controller command, available stage state, and operating context. It is more useful than a screen image because another reviewer can see what the record includes.
Does a command timestamp prove that a capacitor stage operated?
No. A command identifies what the controller requested. Keep available feedback, alarm information, and a separately documented electrical capture so the report distinguishes requested action from observed evidence.
Why should APF and compound-switch records be kept separately?
They may be reviewed together, but they answer different questions. A switching sequence is not a controlled APF performance comparison and cannot establish mitigation, compatibility, or an acceptance result on its own.
What harmonic information belongs with a switching log?
Retain the measurement boundary, meter setup, event window, operating state, and the circuit arrangement known at the time, including any reactor or bypass note. This lets a reviewer see whether unlike conditions are being compared.
Can a logged event identify the cause of resonance?
No. It can identify an observation and preserve the conditions around it. A resonance or root-cause conclusion needs an appropriate study and project-specific electrical review.
What should be sent for a compound-switch product review?
Provide the one-line diagram, nominal system details, stage and APF locations, measurement setup, controller exports, event times, operating log, topology notes, protection information, installation constraints, and the proposed acceptance scope.
Ссылки
