PCS & grid

Sign convention

A sign convention is the agreed rule for which direction of electrical flow counts as positive. Circuit theory offers two: generator convention, where positive power means the device is delivering energy, and load convention, where positive means it is consuming.

For most plant the choice is invisible because power only ever flows one way — a grid-scale BESS crosses zero many times a day and is, at full rating, both a generator and a load, so none of its numbers is readable until the convention is named.

Grid-scale practice, and the convention across this glossary, is generator convention at the AC boundary: positive = discharge/export, negative = charge/import, fixed plant-wide before commissioning. The same question repeats for reactive power — inject or absorb — and the answer has to be stated per interface, because the BMS, the PCS, the revenue meter and the interconnection study do not natively agree.

Reviewed August 2026 by Sergey Syrvachev

New to BESS? Start free with the 7-email fundamentals course — no cost, no account.

Two conventions, and the one machine that is both

The two conventions are bookkeeping choices, not physics. The passive sign (load) convention points the reference current arrow into the device, so positive power is power absorbed — the natural frame for anything that consumes, and the frame battery vendors think in: a BMS typically counts charge current as positive, because charging is the direction its protection limits act on and its amp-hour ledger accumulates.

The generator convention points the arrow out, so positive power is power delivered — the natural frame for anything that sells energy, and the frame the PCS, plant SCADA and market systems face the grid in. Same copper, same electrons, opposite ledger; neither is wrong.

A gas turbine never has to choose, because its flow never reverses. A BESS reverses on schedule: a 100 MW plant is a 100 MW generator in one settlement interval and roughly a 100 MW load in the next, and both frames coexist inside one container — the BMS on the DC side logs a charging half-hour as positive current while the PCS on the AC side logs the identical half-hour as negative power.

Both are internally correct in their own frame. The failure mode is numbers crossing frames without translation: an EMS summing battery-side and meter-side registers, a historian trending mixed tags, an energy model fed one export figure with the wrong sign.

The convention this glossary fixes — the one the power entry carries as a key fact — is generator convention at the AC boundary: positive = discharge/export, negative = charge/import, agreed in writing before the first point list is built. Every derived quantity inherits it. State-of-charge accounting integrates signed power, round-trip efficiency divides a discharge sum by a charge sum, and a market bid to charge is a negative-MW offer in most dispatch systems; each of those calculations is one unstated sign away from nonsense.

The reactive sign: inject or absorb, over- or under-excited

Under generator convention, positive Q is injection: the plant runs over-excited, sourcing VARs like a capacitor bank and supporting local voltage. Negative Q is absorption: under-excited, pulling voltage down. The treacherous words are leading and lagging — a lagging generator injects reactive power while a lagging load absorbs it, so the same adjective points in opposite directions depending on which convention its author was raised in. A specification should state the direction as inject/absorb or over-excited/under-excited with an explicit sign, and never lean on lead/lag alone.

The BESS consequences are immediate. A volt-var curve assumes a Q polarity; flip it and a stabilizing droop becomes positive feedback — high voltage commands more injection. And because a four-quadrant PCS can exchange reactive power at zero real power, running as a STATCOM while the battery idles, the sign of Q is the only number that says whether the idle plant is holding the feeder up or dragging it down.

The quadrant map itself — which corner of the P-Q plane is which — belongs to four-quadrant operation; what this entry owns is the polarity of the axes, which has to be fixed before that map means anything.

The same +50 MW, read three ways along one path — the convention is arbitrary, but naming it at every interface, with a signed worked example, is not.
battery rackscells→ modulesDC busenclosurePCSDC → ACunittransformerLV → MVMV collectionfeeders + busmaintransformerMV → HVHV bay +gen-tiebreaker,disconnectsPOI + meterthe boundaryinterconnection studiesgenerator convention throughout1231+ = CHARGING— BMS registers2+ = EXPORT— PCS and grid-facing SCADA3MAY invert— revenue meter

The site rule is fixed plant-wide before commissioning — generator convention: positive is discharge and export, negative is charge and import. Reactive power needs the same treatment: say inject or absorb, or over- and under-excited, never lead or lag alone, because a lagging generator injects Q while a lagging load absorbs it. A flipped sign is not a formatting defect: it reverses a frequency-response action and turns a volt-var droop into positive feedback.

Key facts
Generator convention
Positive P = delivering/export — the grid-scale default for BESS AC interfaces and the convention used across this glossary
Load (passive sign) convention
Positive P = consuming — the native frame of battery-centric BMS registers and of utility-viewpoint metering
Site rule
Positive = discharge/export, negative = charge/import — fix it plant-wide before commissioning
Reactive sign (generator convention)
Q > 0 = inject / over-excited / supports voltage; Q < 0 = absorb / under-excited
Lead/lag trap
A lagging generator injects Q; a lagging load absorbs it — specify inject/absorb or over-/under-excited, never lead/lag alone
Worked-example rule
Every register in the point list gets a signed example: "+50.0 here means 50 MW export at the POI"
Commissioning check
A known P and Q injection at the PCS terminals must match every layer up to the POI meter in magnitude and sign — in all four quadrants
Where frames collide
BMS (battery-centric) vs PCS/SCADA (grid-facing) vs revenue meter (utility-facing) vs interconnection studies (generator convention)

The interconnection-vs-metering trap

The two document families of one project are routinely written in opposite frames. On the interconnection side, power-flow and dynamic studies model the plant as a generator — export positive — and the interconnection agreement caps injection as a positive MW figure, increasingly with a separate charging-load limit beside it.

On the metering side, revenue meters are organized around delivered and received registers, and a meter programmed from the utility's point of view can count energy delivered to the plant — charging — as its positive channel. Same plant, same megawatt-hours, opposite signs, and both documents internally consistent, which is exactly why the conflict survives design review.

Where it bites is settlement and testing. A flipped sign in the loss-compensation or telemetry chain can make a plant fail a capacity test on paper while performing correctly — the reconciliation duty the energy-capacity-test entry describes. Efficiency arithmetic at least fails loudly: divide a discharge sum by a wrong-signed charge sum and the answer is negative or impossibly high. The dangerous case is the double flip — two sign errors that cancel in the discharge-only test everyone witnesses, then reappear months later in charge-side settlement or a reactive-dispatch instruction.

The fix is a document, not a debugging session: a sign-convention sheet in the project dossier that lists every interface — BMS, PCS, revenue meter, SCADA, plant controller, market gateway — states its convention, and attaches a signed worked example to every point, in the form the setpoint entry insists on: a value of +50.0 at this register means 50 MW export at the POI.

Commissioning then closes the loop end to end: a known P and Q injection at the PCS terminals must reconcile with every layer up to the POI meter in magnitude and in sign before any guarantee, settlement, or control function is trusted.

Common pitfalls

The vocabulary traps come first. Lead/lag flips meaning between conventions, as above. Import and export are written from an unstated vantage point — the utility's export is the plant's import — so a bare "import limit" in a connection offer needs the same scrutiny as a bare sign. In prose, the battery-centric words are actually the safe ones: charge and discharge are unambiguous in a way that positive and negative never are, which is why good test procedures say "discharge at 50 MW" and reserve signed numbers for registers with a stated convention.

The control traps are worse than the accounting ones. Frequency response must answer a falling frequency with more export; reverse the sign and the plant charges into an under-frequency event — an anti-service that performance scoring, and possibly protection, will punish.

And a convention verified in one operating mode proves nothing about the other three: a telemetry mapping checked during discharge testing has said nothing about the charge sign, or either reactive direction, until each is exercised. A four-quadrant machine needs its sign reconciliation witnessed in all four corners, because that is where a cancelled double flip comes back.

Common misconception

Sign convention is just notation — as long as each system is internally consistent, which direction you call positive cannot change any engineering result.

In reality: Each system alone, yes; a plant, no. A BESS project runs several internally consistent conventions at once — the BMS counts charge positive, grid-facing SCADA counts export positive, a utility-programmed meter may count delivery to the plant positive — and every result assembled across those frames depends on a translation at each boundary. A flipped sign is not a formatting defect: it reverses a frequency-response action, turns a volt-var droop into positive feedback, corrupts state-of-charge and efficiency arithmetic, and can fail a capacity test on paper for a plant performing correctly. The convention is arbitrary; naming it at every interface, with a signed worked example, is not.

Go deeper

Sign convention, in context.

The Grid-Scale BESS course covers sign convention — and the rest of the system — from the ground up, the way it actually gets deployed.

Browse the course